Wikibooks:Requests for deletion

<mediawiki xmlns="http://www.mediawiki.org/xml/export-0.11/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.mediawiki.org/xml/export-0.11/ http://www.mediawiki.org/xml/export-0.11.xsd" version="0.11" xml:lang="en">
  <siteinfo>
    <sitename>Wikibooks</sitename>
    <dbname>enwikibooks</dbname>
    <base>https://en.wikibooks.org/wiki/Main_Page</base>
    <generator>MediaWiki 1.47.0-wmf.23</generator>
    <case>first-letter</case>
    <namespaces>
      <namespace key="-2" case="first-letter">Media</namespace>
      <namespace key="-1" case="first-letter">Special</namespace>
      <namespace key="0" case="first-letter" />
      <namespace key="1" case="first-letter">Talk</namespace>
      <namespace key="2" case="first-letter">User</namespace>
      <namespace key="3" case="first-letter">User talk</namespace>
      <namespace key="4" case="first-letter">Wikibooks</namespace>
      <namespace key="5" case="first-letter">Wikibooks talk</namespace>
      <namespace key="6" case="first-letter">File</namespace>
      <namespace key="7" case="first-letter">File talk</namespace>
      <namespace key="8" case="first-letter">MediaWiki</namespace>
      <namespace key="9" case="first-letter">MediaWiki talk</namespace>
      <namespace key="10" case="first-letter">Template</namespace>
      <namespace key="11" case="first-letter">Template talk</namespace>
      <namespace key="12" case="first-letter">Help</namespace>
      <namespace key="13" case="first-letter">Help talk</namespace>
      <namespace key="14" case="first-letter">Category</namespace>
      <namespace key="15" case="first-letter">Category talk</namespace>
      <namespace key="102" case="first-letter">Cookbook</namespace>
      <namespace key="103" case="first-letter">Cookbook talk</namespace>
      <namespace key="108" case="first-letter">Transwiki</namespace>
      <namespace key="109" case="first-letter">Transwiki talk</namespace>
      <namespace key="110" case="first-letter">Wikijunior</namespace>
      <namespace key="111" case="first-letter">Wikijunior talk</namespace>
      <namespace key="112" case="first-letter">Subject</namespace>
      <namespace key="113" case="first-letter">Subject talk</namespace>
      <namespace key="710" case="first-letter">TimedText</namespace>
      <namespace key="711" case="first-letter">TimedText talk</namespace>
      <namespace key="828" case="first-letter">Module</namespace>
      <namespace key="829" case="first-letter">Module talk</namespace>
      <namespace key="1728" case="first-letter">Event</namespace>
      <namespace key="1729" case="first-letter">Event talk</namespace>
    </namespaces>
  </siteinfo>
  <page>
    <title>Wikibooks:Requests for deletion</title>
    <ns>4</ns>
    <id>385</id>
    <revision>
      <id>4675742</id>
      <parentid>4675523</parentid>
      <timestamp>2026-10-12T14:20:11Z</timestamp>
      <contributor>
        <username>Kittycataclysm</username>
        <id>3371989</id>
      </contributor>
      <comment>Adding deletion request for [[Digital Synthora]]</comment>
      <origin>4675742</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="39540" sha1="n6kryp9comejkl3gna8k6xha6jr3mfs" xml:space="preserve">__NEWSECTIONLINK__
[[Category:Wikibooks deletion|{{PAGENAME}}]]
{{Discussion Rooms}}
{{TOCleft}}
{{shortcut|WB:RFD}}
{{Requests for deletion/New deletion}}
{{Requests for deletion/Deletion intro}}
&lt;!-- New deletion nominations go at the bottom of page. --&gt;

== [[Salute, Jonathan!]] and its translations ==

&lt;div style=&quot;column-count: 7;&quot;&gt;
* [[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]])
&lt;/div&gt;

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|&lt;small&gt;|}}'''Done'''{{#ifeq:|small|&lt;/small&gt;|}} — [[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)

:{{keep}} 100% keep. These books are a core part of language textbooks on Wikibooks and have been for years. Not sure why this is even being debated.--[[User:Xania|Xania]] [[Image:Flag_of_Estonia.svg|15px]]  [[Image:Flag_of_Ukraine.svg|15px]] [[User talk:Xania|&lt;sup&gt;talk&lt;/sup&gt;]] 17:55, 16 May 2026 (UTC)

::With all due respect, some of the books included in this nomination (like [[Sin Chao, Jonathan!]]) are written in constructed languages which are not substantially attested anywhere else. I struggle to imagine any educational purpose for such a book. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 00:12, 17 May 2026 (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&amp;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 (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''vf&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 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 ''&quot;Using the Finnish Language&quot;'' or ''&quot;Put Finnish Language into Use&quot;'' for a direct translation.   [[User:Zache|Zache]] ([[User talk:Zache|discuss]] • [[Special:Contributions/Zache|contribs]]) 11:57, 14 November 2024 (UTC)

== [[AT&amp;T Mobility FAQ]] ==

* [[AT&amp;T Mobility FAQ]]
* [[AT&amp;T Mobility FAQ/MEdia Net Configuration]]
* [[AT&amp;T Mobility FAQ/Data Connect Configuration]]
An ''extremely'' outdated FAQ on AT&amp;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 &quot;tethering&quot; 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]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[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 &quot;Archive:&quot;) 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]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[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]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[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)

== [[A-level Computing AQA Paper 1 Skeleton program 2027]] ==
This was proposed for speedy deletion by [[User:Omphalographer]] as 'not being a book'. However, I think this page's future requires further discussion from the community. Maybe some input would be appreciated?[[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 23:51, 21 September 2026 (UTC)

:As best I can tell, this is a page students are using to collaborate on solutions for a standardized test. There are a number of similar pages for other years linked from [[A-level Computing/AQA/Paper 1/Skeleton program]].
:This is not a good fit for Wikibooks. If these students are interested in this kind of collaboration, it should take place elsewhere. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 00:14, 22 September 2026 (UTC)
::The project can be moved to Wikiversity, I think. If the students can contribute it and make sure it complies with Wikibooks' guidelines, it can stay here. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:17, 22 September 2026 (UTC)
:::@[[User:Omphalographer|Omphalographer]] @[[User:TechVindicator|TechVindicator]]
:::There's been a Wikibook on this every single year, as I mentioned in my comment on the deletion notice. That doesn't mean that this shouldn't be on Wikiversity, just that there is ample precedent of it being a Wikibook.  Dunno if this matter to those kind of editorial decisions, though. [[Special:Contributions/~2026-51010-27|~2026-51010-27]] ([[User talk:~2026-51010-27|talk]]) 13:39, 22 September 2026 (UTC)
::::@[[User:~2026-51010-27|~2026-51010-27]]: How would the page comply with [[WB:What is Wikibooks?|Wikibooks' mission]]?. Could you provide an explanation of what the project is?  If it's a collaborative project to work on solutions for a standardized test (like @[[User:Omphalographer|Omphalographer]] said), it would be more suitable for Wikiversity. If it's a textbook about A-level computing, then it would be suitable here. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 13:58, 22 September 2026 (UTC)
:::::Hi,
:::::This is definitely the former, not the latter. As I said, I don't particularly think this should be on Wikibooks, it just happens the previous years had been, and clearly they weren't subject to this degree of scrutiny 😅
:::::I have created https://en.wikiversity.org/wiki/A-level_Computer_Science_AQA_Paper_1_Skeleton_program_2027 - I'll delete the content of the page and put the link at the top. If there is a more appropriate banner to indicate the migration, please make it look how it should :D [[User:MrBerard|MrBerard]] ([[User talk:MrBerard|discuss]] • [[Special:Contributions/MrBerard|contribs]]) 10:23, 29 September 2026 (UTC)
::::::I can't seem to put a link without the edit being deemed destructive, so I'll let you trusted people do what's needed. [[User:MrBerard|MrBerard]] ([[User talk:MrBerard|discuss]] • [[Special:Contributions/MrBerard|contribs]]) 10:27, 29 September 2026 (UTC)

== [[Talmudic aramic]] ==
Per the user's other mass-created pages, I concur with the AI flagging that Kittycataclysm placed on the page. I believe this to be LLM-generated, and it should thus be deleted. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 03:29, 30 September 2026 (UTC)

:{{vd}}, LLM spam. [[User:Ternera|Ternera]] ([[User talk:Ternera|discuss]] • [[Special:Contributions/Ternera|contribs]]) 13:22, 30 September 2026 (UTC)
:{{vd}} - like most LLM-generated books, this is heavy on structure and light on substance. Most of the content amounts to a poorly organized glossary, and there are a lot of pieces missing. (For instance, there is no discussion of the grammar of the language beyond a couple of fixed expressions.) [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 19:11, 1 October 2026 (UTC)

== [[Job Search]] ==
* as well as [[Job Search Automation for College Students]].

Neither of these books contains any useful information. The first book seems to be written primarily to funnel users to the second, and the second to funnel users to [[PlanoTse Handbook for Job Search Automation]], which was deleted last year. (The deletion request doesn't seem to have been archived.)

The sum total of information in these two books is, essentially, &quot;you can search for jobs online&quot;, which is insultingly trivial. The second book's suggestion that users automate the job search process is of no practical value; most web search engines and job search sites nowadays will detect and block automated access.

[[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:36, 1 October 2026 (UTC)
: {{vd}} and redirect to [[Find Employment]]. ‑‑[[User:Kai Burghardt|Kai Burghardt]] ([[User talk:Kai Burghardt|discuss]] • [[Special:Contributions/Kai Burghardt|contribs]]) 05:14, 2 October 2026 (UTC)

== [[Wikipage]] ==
Like a few other books created by this user, the purpose of this book appears to have been to promote a piece of software written by the author ([[User:Planotse]]). The software is no longer available, and there is no actual content in the book.

[[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:40, 1 October 2026 (UTC)

== [[Becoming a Linguistic Mastermind]] ==
Old book (created 2007) with no substantial content. The intent of this book appears to have been to create a single textbook encompassing ''all'' languages, with sub-courses for each language at [[Becoming a Linguistic Mastermind/The courses]], but no such courses were ever created. An analogous project on dewikibooks [[:b:de:Wikibooks:Löschkandidaten/ 2011-04#Der einfache Weg zum Sprachgenie|was deleted in 2011 for similar reasons]]. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 21:20, 7 October 2026 (UTC)
== [[The Permanent Advantage]] ==
Probably LLM-generated, given broken templates, references to Claude, and section identifiers. This could probably be speedied, but not 100% sure so throwing it to RfD. Even regardless of whether it's LLM-generated or not, I can't see any way it's really suitable for the project. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 07:49, 10 October 2026 (UTC)

:{{vd}} - a book ''about'' chess problems isn't necessarily out of scope, but there needs to be some written content to accompany the problems. And I'm not sure these are even meaningful problems - the few problems with viewable Lichess links appear to be in the early game, so there aren't necessarily objective &quot;solutions&quot; to them. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 19:51, 10 October 2026 (UTC)
:{{vd}}, the Claude references throughout the book support that it's LLM-generated. [[User:Ternera|Ternera]] ([[User talk:Ternera|discuss]] • [[Special:Contributions/Ternera|contribs]]) 14:55, 11 October 2026 (UTC)
== [[Digital Synthora]] ==
Not within WB scope since it seems to be entirely fabricated by the editor. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 14:20, 12 October 2026 (UTC)</text>
      <sha1>n6kryp9comejkl3gna8k6xha6jr3mfs</sha1>
    </revision>
    <revision>
      <id>4675744</id>
      <parentid>4675742</parentid>
      <timestamp>2026-10-12T14:43:56Z</timestamp>
      <contributor>
        <username>Kittycataclysm</username>
        <id>3371989</id>
      </contributor>
      <comment>/* Talmudic aramic */ Reply</comment>
      <origin>4675744</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="39734" sha1="e966zv7kw9w3k9eh0ykpoxxxd6kgpi2" xml:space="preserve">__NEWSECTIONLINK__
[[Category:Wikibooks deletion|{{PAGENAME}}]]
{{Discussion Rooms}}
{{TOCleft}}
{{shortcut|WB:RFD}}
{{Requests for deletion/New deletion}}
{{Requests for deletion/Deletion intro}}
&lt;!-- New deletion nominations go at the bottom of page. --&gt;

== [[Salute, Jonathan!]] and its translations ==

&lt;div style=&quot;column-count: 7;&quot;&gt;
* [[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]])
&lt;/div&gt;

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|&lt;small&gt;|}}'''Done'''{{#ifeq:|small|&lt;/small&gt;|}} — [[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)

:{{keep}} 100% keep. These books are a core part of language textbooks on Wikibooks and have been for years. Not sure why this is even being debated.--[[User:Xania|Xania]] [[Image:Flag_of_Estonia.svg|15px]]  [[Image:Flag_of_Ukraine.svg|15px]] [[User talk:Xania|&lt;sup&gt;talk&lt;/sup&gt;]] 17:55, 16 May 2026 (UTC)

::With all due respect, some of the books included in this nomination (like [[Sin Chao, Jonathan!]]) are written in constructed languages which are not substantially attested anywhere else. I struggle to imagine any educational purpose for such a book. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 00:12, 17 May 2026 (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&amp;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 (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''vf&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 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 ''&quot;Using the Finnish Language&quot;'' or ''&quot;Put Finnish Language into Use&quot;'' for a direct translation.   [[User:Zache|Zache]] ([[User talk:Zache|discuss]] • [[Special:Contributions/Zache|contribs]]) 11:57, 14 November 2024 (UTC)

== [[AT&amp;T Mobility FAQ]] ==

* [[AT&amp;T Mobility FAQ]]
* [[AT&amp;T Mobility FAQ/MEdia Net Configuration]]
* [[AT&amp;T Mobility FAQ/Data Connect Configuration]]
An ''extremely'' outdated FAQ on AT&amp;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 &quot;tethering&quot; 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]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[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 &quot;Archive:&quot;) 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]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[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]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[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)

== [[A-level Computing AQA Paper 1 Skeleton program 2027]] ==
This was proposed for speedy deletion by [[User:Omphalographer]] as 'not being a book'. However, I think this page's future requires further discussion from the community. Maybe some input would be appreciated?[[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 23:51, 21 September 2026 (UTC)

:As best I can tell, this is a page students are using to collaborate on solutions for a standardized test. There are a number of similar pages for other years linked from [[A-level Computing/AQA/Paper 1/Skeleton program]].
:This is not a good fit for Wikibooks. If these students are interested in this kind of collaboration, it should take place elsewhere. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 00:14, 22 September 2026 (UTC)
::The project can be moved to Wikiversity, I think. If the students can contribute it and make sure it complies with Wikibooks' guidelines, it can stay here. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:17, 22 September 2026 (UTC)
:::@[[User:Omphalographer|Omphalographer]] @[[User:TechVindicator|TechVindicator]]
:::There's been a Wikibook on this every single year, as I mentioned in my comment on the deletion notice. That doesn't mean that this shouldn't be on Wikiversity, just that there is ample precedent of it being a Wikibook.  Dunno if this matter to those kind of editorial decisions, though. [[Special:Contributions/~2026-51010-27|~2026-51010-27]] ([[User talk:~2026-51010-27|talk]]) 13:39, 22 September 2026 (UTC)
::::@[[User:~2026-51010-27|~2026-51010-27]]: How would the page comply with [[WB:What is Wikibooks?|Wikibooks' mission]]?. Could you provide an explanation of what the project is?  If it's a collaborative project to work on solutions for a standardized test (like @[[User:Omphalographer|Omphalographer]] said), it would be more suitable for Wikiversity. If it's a textbook about A-level computing, then it would be suitable here. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 13:58, 22 September 2026 (UTC)
:::::Hi,
:::::This is definitely the former, not the latter. As I said, I don't particularly think this should be on Wikibooks, it just happens the previous years had been, and clearly they weren't subject to this degree of scrutiny 😅
:::::I have created https://en.wikiversity.org/wiki/A-level_Computer_Science_AQA_Paper_1_Skeleton_program_2027 - I'll delete the content of the page and put the link at the top. If there is a more appropriate banner to indicate the migration, please make it look how it should :D [[User:MrBerard|MrBerard]] ([[User talk:MrBerard|discuss]] • [[Special:Contributions/MrBerard|contribs]]) 10:23, 29 September 2026 (UTC)
::::::I can't seem to put a link without the edit being deemed destructive, so I'll let you trusted people do what's needed. [[User:MrBerard|MrBerard]] ([[User talk:MrBerard|discuss]] • [[Special:Contributions/MrBerard|contribs]]) 10:27, 29 September 2026 (UTC)

== [[Talmudic aramic]] ==
Per the user's other mass-created pages, I concur with the AI flagging that Kittycataclysm placed on the page. I believe this to be LLM-generated, and it should thus be deleted. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 03:29, 30 September 2026 (UTC)

:{{vd}}, LLM spam. [[User:Ternera|Ternera]] ([[User talk:Ternera|discuss]] • [[Special:Contributions/Ternera|contribs]]) 13:22, 30 September 2026 (UTC)
:{{vd}} - like most LLM-generated books, this is heavy on structure and light on substance. Most of the content amounts to a poorly organized glossary, and there are a lot of pieces missing. (For instance, there is no discussion of the grammar of the language beyond a couple of fixed expressions.) [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 19:11, 1 October 2026 (UTC)
:{{vd}} per stated reasoning. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 14:43, 12 October 2026 (UTC)

== [[Job Search]] ==
* as well as [[Job Search Automation for College Students]].

Neither of these books contains any useful information. The first book seems to be written primarily to funnel users to the second, and the second to funnel users to [[PlanoTse Handbook for Job Search Automation]], which was deleted last year. (The deletion request doesn't seem to have been archived.)

The sum total of information in these two books is, essentially, &quot;you can search for jobs online&quot;, which is insultingly trivial. The second book's suggestion that users automate the job search process is of no practical value; most web search engines and job search sites nowadays will detect and block automated access.

[[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:36, 1 October 2026 (UTC)
: {{vd}} and redirect to [[Find Employment]]. ‑‑[[User:Kai Burghardt|Kai Burghardt]] ([[User talk:Kai Burghardt|discuss]] • [[Special:Contributions/Kai Burghardt|contribs]]) 05:14, 2 October 2026 (UTC)

== [[Wikipage]] ==
Like a few other books created by this user, the purpose of this book appears to have been to promote a piece of software written by the author ([[User:Planotse]]). The software is no longer available, and there is no actual content in the book.

[[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:40, 1 October 2026 (UTC)

== [[Becoming a Linguistic Mastermind]] ==
Old book (created 2007) with no substantial content. The intent of this book appears to have been to create a single textbook encompassing ''all'' languages, with sub-courses for each language at [[Becoming a Linguistic Mastermind/The courses]], but no such courses were ever created. An analogous project on dewikibooks [[:b:de:Wikibooks:Löschkandidaten/ 2011-04#Der einfache Weg zum Sprachgenie|was deleted in 2011 for similar reasons]]. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 21:20, 7 October 2026 (UTC)
== [[The Permanent Advantage]] ==
Probably LLM-generated, given broken templates, references to Claude, and section identifiers. This could probably be speedied, but not 100% sure so throwing it to RfD. Even regardless of whether it's LLM-generated or not, I can't see any way it's really suitable for the project. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 07:49, 10 October 2026 (UTC)

:{{vd}} - a book ''about'' chess problems isn't necessarily out of scope, but there needs to be some written content to accompany the problems. And I'm not sure these are even meaningful problems - the few problems with viewable Lichess links appear to be in the early game, so there aren't necessarily objective &quot;solutions&quot; to them. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 19:51, 10 October 2026 (UTC)
:{{vd}}, the Claude references throughout the book support that it's LLM-generated. [[User:Ternera|Ternera]] ([[User talk:Ternera|discuss]] • [[Special:Contributions/Ternera|contribs]]) 14:55, 11 October 2026 (UTC)
== [[Digital Synthora]] ==
Not within WB scope since it seems to be entirely fabricated by the editor. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 14:20, 12 October 2026 (UTC)</text>
      <sha1>e966zv7kw9w3k9eh0ykpoxxxd6kgpi2</sha1>
    </revision>
    <revision>
      <id>4675746</id>
      <parentid>4675744</parentid>
      <timestamp>2026-10-12T15:30:32Z</timestamp>
      <contributor>
        <username>Koavf</username>
        <id>16549</id>
      </contributor>
      <comment>/* Digital Synthora */ Reply</comment>
      <origin>4675746</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="40166" sha1="sxqt2fm96z448wif6k2zlkih2cxthau" xml:space="preserve">__NEWSECTIONLINK__
[[Category:Wikibooks deletion|{{PAGENAME}}]]
{{Discussion Rooms}}
{{TOCleft}}
{{shortcut|WB:RFD}}
{{Requests for deletion/New deletion}}
{{Requests for deletion/Deletion intro}}
&lt;!-- New deletion nominations go at the bottom of page. --&gt;

== [[Salute, Jonathan!]] and its translations ==

&lt;div style=&quot;column-count: 7;&quot;&gt;
* [[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]])
&lt;/div&gt;

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|&lt;small&gt;|}}'''Done'''{{#ifeq:|small|&lt;/small&gt;|}} — [[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)

:{{keep}} 100% keep. These books are a core part of language textbooks on Wikibooks and have been for years. Not sure why this is even being debated.--[[User:Xania|Xania]] [[Image:Flag_of_Estonia.svg|15px]]  [[Image:Flag_of_Ukraine.svg|15px]] [[User talk:Xania|&lt;sup&gt;talk&lt;/sup&gt;]] 17:55, 16 May 2026 (UTC)

::With all due respect, some of the books included in this nomination (like [[Sin Chao, Jonathan!]]) are written in constructed languages which are not substantially attested anywhere else. I struggle to imagine any educational purpose for such a book. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 00:12, 17 May 2026 (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&amp;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 (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''vf&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 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 ''&quot;Using the Finnish Language&quot;'' or ''&quot;Put Finnish Language into Use&quot;'' for a direct translation.   [[User:Zache|Zache]] ([[User talk:Zache|discuss]] • [[Special:Contributions/Zache|contribs]]) 11:57, 14 November 2024 (UTC)

== [[AT&amp;T Mobility FAQ]] ==

* [[AT&amp;T Mobility FAQ]]
* [[AT&amp;T Mobility FAQ/MEdia Net Configuration]]
* [[AT&amp;T Mobility FAQ/Data Connect Configuration]]
An ''extremely'' outdated FAQ on AT&amp;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 &quot;tethering&quot; 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]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[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 &quot;Archive:&quot;) 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]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[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]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[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)

== [[A-level Computing AQA Paper 1 Skeleton program 2027]] ==
This was proposed for speedy deletion by [[User:Omphalographer]] as 'not being a book'. However, I think this page's future requires further discussion from the community. Maybe some input would be appreciated?[[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 23:51, 21 September 2026 (UTC)

:As best I can tell, this is a page students are using to collaborate on solutions for a standardized test. There are a number of similar pages for other years linked from [[A-level Computing/AQA/Paper 1/Skeleton program]].
:This is not a good fit for Wikibooks. If these students are interested in this kind of collaboration, it should take place elsewhere. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 00:14, 22 September 2026 (UTC)
::The project can be moved to Wikiversity, I think. If the students can contribute it and make sure it complies with Wikibooks' guidelines, it can stay here. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:17, 22 September 2026 (UTC)
:::@[[User:Omphalographer|Omphalographer]] @[[User:TechVindicator|TechVindicator]]
:::There's been a Wikibook on this every single year, as I mentioned in my comment on the deletion notice. That doesn't mean that this shouldn't be on Wikiversity, just that there is ample precedent of it being a Wikibook.  Dunno if this matter to those kind of editorial decisions, though. [[Special:Contributions/~2026-51010-27|~2026-51010-27]] ([[User talk:~2026-51010-27|talk]]) 13:39, 22 September 2026 (UTC)
::::@[[User:~2026-51010-27|~2026-51010-27]]: How would the page comply with [[WB:What is Wikibooks?|Wikibooks' mission]]?. Could you provide an explanation of what the project is?  If it's a collaborative project to work on solutions for a standardized test (like @[[User:Omphalographer|Omphalographer]] said), it would be more suitable for Wikiversity. If it's a textbook about A-level computing, then it would be suitable here. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 13:58, 22 September 2026 (UTC)
:::::Hi,
:::::This is definitely the former, not the latter. As I said, I don't particularly think this should be on Wikibooks, it just happens the previous years had been, and clearly they weren't subject to this degree of scrutiny 😅
:::::I have created https://en.wikiversity.org/wiki/A-level_Computer_Science_AQA_Paper_1_Skeleton_program_2027 - I'll delete the content of the page and put the link at the top. If there is a more appropriate banner to indicate the migration, please make it look how it should :D [[User:MrBerard|MrBerard]] ([[User talk:MrBerard|discuss]] • [[Special:Contributions/MrBerard|contribs]]) 10:23, 29 September 2026 (UTC)
::::::I can't seem to put a link without the edit being deemed destructive, so I'll let you trusted people do what's needed. [[User:MrBerard|MrBerard]] ([[User talk:MrBerard|discuss]] • [[Special:Contributions/MrBerard|contribs]]) 10:27, 29 September 2026 (UTC)

== [[Talmudic aramic]] ==
Per the user's other mass-created pages, I concur with the AI flagging that Kittycataclysm placed on the page. I believe this to be LLM-generated, and it should thus be deleted. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 03:29, 30 September 2026 (UTC)

:{{vd}}, LLM spam. [[User:Ternera|Ternera]] ([[User talk:Ternera|discuss]] • [[Special:Contributions/Ternera|contribs]]) 13:22, 30 September 2026 (UTC)
:{{vd}} - like most LLM-generated books, this is heavy on structure and light on substance. Most of the content amounts to a poorly organized glossary, and there are a lot of pieces missing. (For instance, there is no discussion of the grammar of the language beyond a couple of fixed expressions.) [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 19:11, 1 October 2026 (UTC)
:{{vd}} per stated reasoning. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 14:43, 12 October 2026 (UTC)

== [[Job Search]] ==
* as well as [[Job Search Automation for College Students]].

Neither of these books contains any useful information. The first book seems to be written primarily to funnel users to the second, and the second to funnel users to [[PlanoTse Handbook for Job Search Automation]], which was deleted last year. (The deletion request doesn't seem to have been archived.)

The sum total of information in these two books is, essentially, &quot;you can search for jobs online&quot;, which is insultingly trivial. The second book's suggestion that users automate the job search process is of no practical value; most web search engines and job search sites nowadays will detect and block automated access.

[[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:36, 1 October 2026 (UTC)
: {{vd}} and redirect to [[Find Employment]]. ‑‑[[User:Kai Burghardt|Kai Burghardt]] ([[User talk:Kai Burghardt|discuss]] • [[Special:Contributions/Kai Burghardt|contribs]]) 05:14, 2 October 2026 (UTC)

== [[Wikipage]] ==
Like a few other books created by this user, the purpose of this book appears to have been to promote a piece of software written by the author ([[User:Planotse]]). The software is no longer available, and there is no actual content in the book.

[[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:40, 1 October 2026 (UTC)

== [[Becoming a Linguistic Mastermind]] ==
Old book (created 2007) with no substantial content. The intent of this book appears to have been to create a single textbook encompassing ''all'' languages, with sub-courses for each language at [[Becoming a Linguistic Mastermind/The courses]], but no such courses were ever created. An analogous project on dewikibooks [[:b:de:Wikibooks:Löschkandidaten/ 2011-04#Der einfache Weg zum Sprachgenie|was deleted in 2011 for similar reasons]]. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 21:20, 7 October 2026 (UTC)
== [[The Permanent Advantage]] ==
Probably LLM-generated, given broken templates, references to Claude, and section identifiers. This could probably be speedied, but not 100% sure so throwing it to RfD. Even regardless of whether it's LLM-generated or not, I can't see any way it's really suitable for the project. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 07:49, 10 October 2026 (UTC)

:{{vd}} - a book ''about'' chess problems isn't necessarily out of scope, but there needs to be some written content to accompany the problems. And I'm not sure these are even meaningful problems - the few problems with viewable Lichess links appear to be in the early game, so there aren't necessarily objective &quot;solutions&quot; to them. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 19:51, 10 October 2026 (UTC)
:{{vd}}, the Claude references throughout the book support that it's LLM-generated. [[User:Ternera|Ternera]] ([[User talk:Ternera|discuss]] • [[Special:Contributions/Ternera|contribs]]) 14:55, 11 October 2026 (UTC)
== [[Digital Synthora]] ==
Not within WB scope since it seems to be entirely fabricated by the editor. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 14:20, 12 October 2026 (UTC)

:{{vd}} While some amount of original research is allowed here, completely fabricated topics aren't. This is just fiction writing, which is nice, but not within our scope. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 15:30, 12 October 2026 (UTC)</text>
      <sha1>sxqt2fm96z448wif6k2zlkih2cxthau</sha1>
    </revision>
    <revision>
      <id>4675747</id>
      <parentid>4675746</parentid>
      <timestamp>2026-10-12T15:30:52Z</timestamp>
      <contributor>
        <username>Koavf</username>
        <id>16549</id>
      </contributor>
      <comment>/* Wikipage */ Reply</comment>
      <origin>4675747</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="40434" sha1="1ipij5u73kiklzqb25sgusku8lgkqgm" xml:space="preserve">__NEWSECTIONLINK__
[[Category:Wikibooks deletion|{{PAGENAME}}]]
{{Discussion Rooms}}
{{TOCleft}}
{{shortcut|WB:RFD}}
{{Requests for deletion/New deletion}}
{{Requests for deletion/Deletion intro}}
&lt;!-- New deletion nominations go at the bottom of page. --&gt;

== [[Salute, Jonathan!]] and its translations ==

&lt;div style=&quot;column-count: 7;&quot;&gt;
* [[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]])
&lt;/div&gt;

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|&lt;small&gt;|}}'''Done'''{{#ifeq:|small|&lt;/small&gt;|}} — [[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)

:{{keep}} 100% keep. These books are a core part of language textbooks on Wikibooks and have been for years. Not sure why this is even being debated.--[[User:Xania|Xania]] [[Image:Flag_of_Estonia.svg|15px]]  [[Image:Flag_of_Ukraine.svg|15px]] [[User talk:Xania|&lt;sup&gt;talk&lt;/sup&gt;]] 17:55, 16 May 2026 (UTC)

::With all due respect, some of the books included in this nomination (like [[Sin Chao, Jonathan!]]) are written in constructed languages which are not substantially attested anywhere else. I struggle to imagine any educational purpose for such a book. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 00:12, 17 May 2026 (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&amp;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 (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''vf&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 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 ''&quot;Using the Finnish Language&quot;'' or ''&quot;Put Finnish Language into Use&quot;'' for a direct translation.   [[User:Zache|Zache]] ([[User talk:Zache|discuss]] • [[Special:Contributions/Zache|contribs]]) 11:57, 14 November 2024 (UTC)

== [[AT&amp;T Mobility FAQ]] ==

* [[AT&amp;T Mobility FAQ]]
* [[AT&amp;T Mobility FAQ/MEdia Net Configuration]]
* [[AT&amp;T Mobility FAQ/Data Connect Configuration]]
An ''extremely'' outdated FAQ on AT&amp;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 &quot;tethering&quot; 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]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[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 &quot;Archive:&quot;) 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]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[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]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[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)

== [[A-level Computing AQA Paper 1 Skeleton program 2027]] ==
This was proposed for speedy deletion by [[User:Omphalographer]] as 'not being a book'. However, I think this page's future requires further discussion from the community. Maybe some input would be appreciated?[[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 23:51, 21 September 2026 (UTC)

:As best I can tell, this is a page students are using to collaborate on solutions for a standardized test. There are a number of similar pages for other years linked from [[A-level Computing/AQA/Paper 1/Skeleton program]].
:This is not a good fit for Wikibooks. If these students are interested in this kind of collaboration, it should take place elsewhere. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 00:14, 22 September 2026 (UTC)
::The project can be moved to Wikiversity, I think. If the students can contribute it and make sure it complies with Wikibooks' guidelines, it can stay here. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:17, 22 September 2026 (UTC)
:::@[[User:Omphalographer|Omphalographer]] @[[User:TechVindicator|TechVindicator]]
:::There's been a Wikibook on this every single year, as I mentioned in my comment on the deletion notice. That doesn't mean that this shouldn't be on Wikiversity, just that there is ample precedent of it being a Wikibook.  Dunno if this matter to those kind of editorial decisions, though. [[Special:Contributions/~2026-51010-27|~2026-51010-27]] ([[User talk:~2026-51010-27|talk]]) 13:39, 22 September 2026 (UTC)
::::@[[User:~2026-51010-27|~2026-51010-27]]: How would the page comply with [[WB:What is Wikibooks?|Wikibooks' mission]]?. Could you provide an explanation of what the project is?  If it's a collaborative project to work on solutions for a standardized test (like @[[User:Omphalographer|Omphalographer]] said), it would be more suitable for Wikiversity. If it's a textbook about A-level computing, then it would be suitable here. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 13:58, 22 September 2026 (UTC)
:::::Hi,
:::::This is definitely the former, not the latter. As I said, I don't particularly think this should be on Wikibooks, it just happens the previous years had been, and clearly they weren't subject to this degree of scrutiny 😅
:::::I have created https://en.wikiversity.org/wiki/A-level_Computer_Science_AQA_Paper_1_Skeleton_program_2027 - I'll delete the content of the page and put the link at the top. If there is a more appropriate banner to indicate the migration, please make it look how it should :D [[User:MrBerard|MrBerard]] ([[User talk:MrBerard|discuss]] • [[Special:Contributions/MrBerard|contribs]]) 10:23, 29 September 2026 (UTC)
::::::I can't seem to put a link without the edit being deemed destructive, so I'll let you trusted people do what's needed. [[User:MrBerard|MrBerard]] ([[User talk:MrBerard|discuss]] • [[Special:Contributions/MrBerard|contribs]]) 10:27, 29 September 2026 (UTC)

== [[Talmudic aramic]] ==
Per the user's other mass-created pages, I concur with the AI flagging that Kittycataclysm placed on the page. I believe this to be LLM-generated, and it should thus be deleted. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 03:29, 30 September 2026 (UTC)

:{{vd}}, LLM spam. [[User:Ternera|Ternera]] ([[User talk:Ternera|discuss]] • [[Special:Contributions/Ternera|contribs]]) 13:22, 30 September 2026 (UTC)
:{{vd}} - like most LLM-generated books, this is heavy on structure and light on substance. Most of the content amounts to a poorly organized glossary, and there are a lot of pieces missing. (For instance, there is no discussion of the grammar of the language beyond a couple of fixed expressions.) [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 19:11, 1 October 2026 (UTC)
:{{vd}} per stated reasoning. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 14:43, 12 October 2026 (UTC)

== [[Job Search]] ==
* as well as [[Job Search Automation for College Students]].

Neither of these books contains any useful information. The first book seems to be written primarily to funnel users to the second, and the second to funnel users to [[PlanoTse Handbook for Job Search Automation]], which was deleted last year. (The deletion request doesn't seem to have been archived.)

The sum total of information in these two books is, essentially, &quot;you can search for jobs online&quot;, which is insultingly trivial. The second book's suggestion that users automate the job search process is of no practical value; most web search engines and job search sites nowadays will detect and block automated access.

[[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:36, 1 October 2026 (UTC)
: {{vd}} and redirect to [[Find Employment]]. ‑‑[[User:Kai Burghardt|Kai Burghardt]] ([[User talk:Kai Burghardt|discuss]] • [[Special:Contributions/Kai Burghardt|contribs]]) 05:14, 2 October 2026 (UTC)

== [[Wikipage]] ==
Like a few other books created by this user, the purpose of this book appears to have been to promote a piece of software written by the author ([[User:Planotse]]). The software is no longer available, and there is no actual content in the book.

[[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:40, 1 October 2026 (UTC)

:{{Vd}} ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 15:30, 12 October 2026 (UTC)

== [[Becoming a Linguistic Mastermind]] ==
Old book (created 2007) with no substantial content. The intent of this book appears to have been to create a single textbook encompassing ''all'' languages, with sub-courses for each language at [[Becoming a Linguistic Mastermind/The courses]], but no such courses were ever created. An analogous project on dewikibooks [[:b:de:Wikibooks:Löschkandidaten/ 2011-04#Der einfache Weg zum Sprachgenie|was deleted in 2011 for similar reasons]]. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 21:20, 7 October 2026 (UTC)
== [[The Permanent Advantage]] ==
Probably LLM-generated, given broken templates, references to Claude, and section identifiers. This could probably be speedied, but not 100% sure so throwing it to RfD. Even regardless of whether it's LLM-generated or not, I can't see any way it's really suitable for the project. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 07:49, 10 October 2026 (UTC)

:{{vd}} - a book ''about'' chess problems isn't necessarily out of scope, but there needs to be some written content to accompany the problems. And I'm not sure these are even meaningful problems - the few problems with viewable Lichess links appear to be in the early game, so there aren't necessarily objective &quot;solutions&quot; to them. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 19:51, 10 October 2026 (UTC)
:{{vd}}, the Claude references throughout the book support that it's LLM-generated. [[User:Ternera|Ternera]] ([[User talk:Ternera|discuss]] • [[Special:Contributions/Ternera|contribs]]) 14:55, 11 October 2026 (UTC)
== [[Digital Synthora]] ==
Not within WB scope since it seems to be entirely fabricated by the editor. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 14:20, 12 October 2026 (UTC)

:{{vd}} While some amount of original research is allowed here, completely fabricated topics aren't. This is just fiction writing, which is nice, but not within our scope. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 15:30, 12 October 2026 (UTC)</text>
      <sha1>1ipij5u73kiklzqb25sgusku8lgkqgm</sha1>
    </revision>
    <revision>
      <id>4675748</id>
      <parentid>4675747</parentid>
      <timestamp>2026-10-12T15:30:59Z</timestamp>
      <contributor>
        <username>Koavf</username>
        <id>16549</id>
      </contributor>
      <comment>/* Becoming a Linguistic Mastermind */ Reply</comment>
      <origin>4675748</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="40703" sha1="6dtirtvzczmwkb5e7rjbhyu48ro24ss" xml:space="preserve">__NEWSECTIONLINK__
[[Category:Wikibooks deletion|{{PAGENAME}}]]
{{Discussion Rooms}}
{{TOCleft}}
{{shortcut|WB:RFD}}
{{Requests for deletion/New deletion}}
{{Requests for deletion/Deletion intro}}
&lt;!-- New deletion nominations go at the bottom of page. --&gt;

== [[Salute, Jonathan!]] and its translations ==

&lt;div style=&quot;column-count: 7;&quot;&gt;
* [[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]])
&lt;/div&gt;

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|&lt;small&gt;|}}'''Done'''{{#ifeq:|small|&lt;/small&gt;|}} — [[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)

:{{keep}} 100% keep. These books are a core part of language textbooks on Wikibooks and have been for years. Not sure why this is even being debated.--[[User:Xania|Xania]] [[Image:Flag_of_Estonia.svg|15px]]  [[Image:Flag_of_Ukraine.svg|15px]] [[User talk:Xania|&lt;sup&gt;talk&lt;/sup&gt;]] 17:55, 16 May 2026 (UTC)

::With all due respect, some of the books included in this nomination (like [[Sin Chao, Jonathan!]]) are written in constructed languages which are not substantially attested anywhere else. I struggle to imagine any educational purpose for such a book. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 00:12, 17 May 2026 (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&amp;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 (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''vf&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 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 ''&quot;Using the Finnish Language&quot;'' or ''&quot;Put Finnish Language into Use&quot;'' for a direct translation.   [[User:Zache|Zache]] ([[User talk:Zache|discuss]] • [[Special:Contributions/Zache|contribs]]) 11:57, 14 November 2024 (UTC)

== [[AT&amp;T Mobility FAQ]] ==

* [[AT&amp;T Mobility FAQ]]
* [[AT&amp;T Mobility FAQ/MEdia Net Configuration]]
* [[AT&amp;T Mobility FAQ/Data Connect Configuration]]
An ''extremely'' outdated FAQ on AT&amp;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 &quot;tethering&quot; 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]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[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 &quot;Archive:&quot;) 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]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[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]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[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)

== [[A-level Computing AQA Paper 1 Skeleton program 2027]] ==
This was proposed for speedy deletion by [[User:Omphalographer]] as 'not being a book'. However, I think this page's future requires further discussion from the community. Maybe some input would be appreciated?[[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 23:51, 21 September 2026 (UTC)

:As best I can tell, this is a page students are using to collaborate on solutions for a standardized test. There are a number of similar pages for other years linked from [[A-level Computing/AQA/Paper 1/Skeleton program]].
:This is not a good fit for Wikibooks. If these students are interested in this kind of collaboration, it should take place elsewhere. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 00:14, 22 September 2026 (UTC)
::The project can be moved to Wikiversity, I think. If the students can contribute it and make sure it complies with Wikibooks' guidelines, it can stay here. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:17, 22 September 2026 (UTC)
:::@[[User:Omphalographer|Omphalographer]] @[[User:TechVindicator|TechVindicator]]
:::There's been a Wikibook on this every single year, as I mentioned in my comment on the deletion notice. That doesn't mean that this shouldn't be on Wikiversity, just that there is ample precedent of it being a Wikibook.  Dunno if this matter to those kind of editorial decisions, though. [[Special:Contributions/~2026-51010-27|~2026-51010-27]] ([[User talk:~2026-51010-27|talk]]) 13:39, 22 September 2026 (UTC)
::::@[[User:~2026-51010-27|~2026-51010-27]]: How would the page comply with [[WB:What is Wikibooks?|Wikibooks' mission]]?. Could you provide an explanation of what the project is?  If it's a collaborative project to work on solutions for a standardized test (like @[[User:Omphalographer|Omphalographer]] said), it would be more suitable for Wikiversity. If it's a textbook about A-level computing, then it would be suitable here. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 13:58, 22 September 2026 (UTC)
:::::Hi,
:::::This is definitely the former, not the latter. As I said, I don't particularly think this should be on Wikibooks, it just happens the previous years had been, and clearly they weren't subject to this degree of scrutiny 😅
:::::I have created https://en.wikiversity.org/wiki/A-level_Computer_Science_AQA_Paper_1_Skeleton_program_2027 - I'll delete the content of the page and put the link at the top. If there is a more appropriate banner to indicate the migration, please make it look how it should :D [[User:MrBerard|MrBerard]] ([[User talk:MrBerard|discuss]] • [[Special:Contributions/MrBerard|contribs]]) 10:23, 29 September 2026 (UTC)
::::::I can't seem to put a link without the edit being deemed destructive, so I'll let you trusted people do what's needed. [[User:MrBerard|MrBerard]] ([[User talk:MrBerard|discuss]] • [[Special:Contributions/MrBerard|contribs]]) 10:27, 29 September 2026 (UTC)

== [[Talmudic aramic]] ==
Per the user's other mass-created pages, I concur with the AI flagging that Kittycataclysm placed on the page. I believe this to be LLM-generated, and it should thus be deleted. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 03:29, 30 September 2026 (UTC)

:{{vd}}, LLM spam. [[User:Ternera|Ternera]] ([[User talk:Ternera|discuss]] • [[Special:Contributions/Ternera|contribs]]) 13:22, 30 September 2026 (UTC)
:{{vd}} - like most LLM-generated books, this is heavy on structure and light on substance. Most of the content amounts to a poorly organized glossary, and there are a lot of pieces missing. (For instance, there is no discussion of the grammar of the language beyond a couple of fixed expressions.) [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 19:11, 1 October 2026 (UTC)
:{{vd}} per stated reasoning. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 14:43, 12 October 2026 (UTC)

== [[Job Search]] ==
* as well as [[Job Search Automation for College Students]].

Neither of these books contains any useful information. The first book seems to be written primarily to funnel users to the second, and the second to funnel users to [[PlanoTse Handbook for Job Search Automation]], which was deleted last year. (The deletion request doesn't seem to have been archived.)

The sum total of information in these two books is, essentially, &quot;you can search for jobs online&quot;, which is insultingly trivial. The second book's suggestion that users automate the job search process is of no practical value; most web search engines and job search sites nowadays will detect and block automated access.

[[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:36, 1 October 2026 (UTC)
: {{vd}} and redirect to [[Find Employment]]. ‑‑[[User:Kai Burghardt|Kai Burghardt]] ([[User talk:Kai Burghardt|discuss]] • [[Special:Contributions/Kai Burghardt|contribs]]) 05:14, 2 October 2026 (UTC)

== [[Wikipage]] ==
Like a few other books created by this user, the purpose of this book appears to have been to promote a piece of software written by the author ([[User:Planotse]]). The software is no longer available, and there is no actual content in the book.

[[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:40, 1 October 2026 (UTC)

:{{Vd}} ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 15:30, 12 October 2026 (UTC)

== [[Becoming a Linguistic Mastermind]] ==
Old book (created 2007) with no substantial content. The intent of this book appears to have been to create a single textbook encompassing ''all'' languages, with sub-courses for each language at [[Becoming a Linguistic Mastermind/The courses]], but no such courses were ever created. An analogous project on dewikibooks [[:b:de:Wikibooks:Löschkandidaten/ 2011-04#Der einfache Weg zum Sprachgenie|was deleted in 2011 for similar reasons]]. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 21:20, 7 October 2026 (UTC)

:{{Vd}} ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 15:30, 12 October 2026 (UTC)

== [[The Permanent Advantage]] ==
Probably LLM-generated, given broken templates, references to Claude, and section identifiers. This could probably be speedied, but not 100% sure so throwing it to RfD. Even regardless of whether it's LLM-generated or not, I can't see any way it's really suitable for the project. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 07:49, 10 October 2026 (UTC)

:{{vd}} - a book ''about'' chess problems isn't necessarily out of scope, but there needs to be some written content to accompany the problems. And I'm not sure these are even meaningful problems - the few problems with viewable Lichess links appear to be in the early game, so there aren't necessarily objective &quot;solutions&quot; to them. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 19:51, 10 October 2026 (UTC)
:{{vd}}, the Claude references throughout the book support that it's LLM-generated. [[User:Ternera|Ternera]] ([[User talk:Ternera|discuss]] • [[Special:Contributions/Ternera|contribs]]) 14:55, 11 October 2026 (UTC)
== [[Digital Synthora]] ==
Not within WB scope since it seems to be entirely fabricated by the editor. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 14:20, 12 October 2026 (UTC)

:{{vd}} While some amount of original research is allowed here, completely fabricated topics aren't. This is just fiction writing, which is nice, but not within our scope. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 15:30, 12 October 2026 (UTC)</text>
      <sha1>6dtirtvzczmwkb5e7rjbhyu48ro24ss</sha1>
    </revision>
    <revision>
      <id>4675774</id>
      <parentid>4675748</parentid>
      <timestamp>2026-10-13T01:32:16Z</timestamp>
      <contributor>
        <username>Omphalographer</username>
        <id>3427146</id>
      </contributor>
      <comment>/* Digital Synthora */ Reply</comment>
      <origin>4675774</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="41040" sha1="eo87984msz87jmd5eii6v3shhn2wjpx" xml:space="preserve">__NEWSECTIONLINK__
[[Category:Wikibooks deletion|{{PAGENAME}}]]
{{Discussion Rooms}}
{{TOCleft}}
{{shortcut|WB:RFD}}
{{Requests for deletion/New deletion}}
{{Requests for deletion/Deletion intro}}
&lt;!-- New deletion nominations go at the bottom of page. --&gt;

== [[Salute, Jonathan!]] and its translations ==

&lt;div style=&quot;column-count: 7;&quot;&gt;
* [[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]])
&lt;/div&gt;

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|&lt;small&gt;|}}'''Done'''{{#ifeq:|small|&lt;/small&gt;|}} — [[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)

:{{keep}} 100% keep. These books are a core part of language textbooks on Wikibooks and have been for years. Not sure why this is even being debated.--[[User:Xania|Xania]] [[Image:Flag_of_Estonia.svg|15px]]  [[Image:Flag_of_Ukraine.svg|15px]] [[User talk:Xania|&lt;sup&gt;talk&lt;/sup&gt;]] 17:55, 16 May 2026 (UTC)

::With all due respect, some of the books included in this nomination (like [[Sin Chao, Jonathan!]]) are written in constructed languages which are not substantially attested anywhere else. I struggle to imagine any educational purpose for such a book. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 00:12, 17 May 2026 (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&amp;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 (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''vf&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 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 ''&quot;Using the Finnish Language&quot;'' or ''&quot;Put Finnish Language into Use&quot;'' for a direct translation.   [[User:Zache|Zache]] ([[User talk:Zache|discuss]] • [[Special:Contributions/Zache|contribs]]) 11:57, 14 November 2024 (UTC)

== [[AT&amp;T Mobility FAQ]] ==

* [[AT&amp;T Mobility FAQ]]
* [[AT&amp;T Mobility FAQ/MEdia Net Configuration]]
* [[AT&amp;T Mobility FAQ/Data Connect Configuration]]
An ''extremely'' outdated FAQ on AT&amp;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 &quot;tethering&quot; 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]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[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 &quot;Archive:&quot;) 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]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[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]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[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)

== [[A-level Computing AQA Paper 1 Skeleton program 2027]] ==
This was proposed for speedy deletion by [[User:Omphalographer]] as 'not being a book'. However, I think this page's future requires further discussion from the community. Maybe some input would be appreciated?[[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 23:51, 21 September 2026 (UTC)

:As best I can tell, this is a page students are using to collaborate on solutions for a standardized test. There are a number of similar pages for other years linked from [[A-level Computing/AQA/Paper 1/Skeleton program]].
:This is not a good fit for Wikibooks. If these students are interested in this kind of collaboration, it should take place elsewhere. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 00:14, 22 September 2026 (UTC)
::The project can be moved to Wikiversity, I think. If the students can contribute it and make sure it complies with Wikibooks' guidelines, it can stay here. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:17, 22 September 2026 (UTC)
:::@[[User:Omphalographer|Omphalographer]] @[[User:TechVindicator|TechVindicator]]
:::There's been a Wikibook on this every single year, as I mentioned in my comment on the deletion notice. That doesn't mean that this shouldn't be on Wikiversity, just that there is ample precedent of it being a Wikibook.  Dunno if this matter to those kind of editorial decisions, though. [[Special:Contributions/~2026-51010-27|~2026-51010-27]] ([[User talk:~2026-51010-27|talk]]) 13:39, 22 September 2026 (UTC)
::::@[[User:~2026-51010-27|~2026-51010-27]]: How would the page comply with [[WB:What is Wikibooks?|Wikibooks' mission]]?. Could you provide an explanation of what the project is?  If it's a collaborative project to work on solutions for a standardized test (like @[[User:Omphalographer|Omphalographer]] said), it would be more suitable for Wikiversity. If it's a textbook about A-level computing, then it would be suitable here. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 13:58, 22 September 2026 (UTC)
:::::Hi,
:::::This is definitely the former, not the latter. As I said, I don't particularly think this should be on Wikibooks, it just happens the previous years had been, and clearly they weren't subject to this degree of scrutiny 😅
:::::I have created https://en.wikiversity.org/wiki/A-level_Computer_Science_AQA_Paper_1_Skeleton_program_2027 - I'll delete the content of the page and put the link at the top. If there is a more appropriate banner to indicate the migration, please make it look how it should :D [[User:MrBerard|MrBerard]] ([[User talk:MrBerard|discuss]] • [[Special:Contributions/MrBerard|contribs]]) 10:23, 29 September 2026 (UTC)
::::::I can't seem to put a link without the edit being deemed destructive, so I'll let you trusted people do what's needed. [[User:MrBerard|MrBerard]] ([[User talk:MrBerard|discuss]] • [[Special:Contributions/MrBerard|contribs]]) 10:27, 29 September 2026 (UTC)

== [[Talmudic aramic]] ==
Per the user's other mass-created pages, I concur with the AI flagging that Kittycataclysm placed on the page. I believe this to be LLM-generated, and it should thus be deleted. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 03:29, 30 September 2026 (UTC)

:{{vd}}, LLM spam. [[User:Ternera|Ternera]] ([[User talk:Ternera|discuss]] • [[Special:Contributions/Ternera|contribs]]) 13:22, 30 September 2026 (UTC)
:{{vd}} - like most LLM-generated books, this is heavy on structure and light on substance. Most of the content amounts to a poorly organized glossary, and there are a lot of pieces missing. (For instance, there is no discussion of the grammar of the language beyond a couple of fixed expressions.) [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 19:11, 1 October 2026 (UTC)
:{{vd}} per stated reasoning. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 14:43, 12 October 2026 (UTC)

== [[Job Search]] ==
* as well as [[Job Search Automation for College Students]].

Neither of these books contains any useful information. The first book seems to be written primarily to funnel users to the second, and the second to funnel users to [[PlanoTse Handbook for Job Search Automation]], which was deleted last year. (The deletion request doesn't seem to have been archived.)

The sum total of information in these two books is, essentially, &quot;you can search for jobs online&quot;, which is insultingly trivial. The second book's suggestion that users automate the job search process is of no practical value; most web search engines and job search sites nowadays will detect and block automated access.

[[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:36, 1 October 2026 (UTC)
: {{vd}} and redirect to [[Find Employment]]. ‑‑[[User:Kai Burghardt|Kai Burghardt]] ([[User talk:Kai Burghardt|discuss]] • [[Special:Contributions/Kai Burghardt|contribs]]) 05:14, 2 October 2026 (UTC)

== [[Wikipage]] ==
Like a few other books created by this user, the purpose of this book appears to have been to promote a piece of software written by the author ([[User:Planotse]]). The software is no longer available, and there is no actual content in the book.

[[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:40, 1 October 2026 (UTC)

:{{Vd}} ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 15:30, 12 October 2026 (UTC)

== [[Becoming a Linguistic Mastermind]] ==
Old book (created 2007) with no substantial content. The intent of this book appears to have been to create a single textbook encompassing ''all'' languages, with sub-courses for each language at [[Becoming a Linguistic Mastermind/The courses]], but no such courses were ever created. An analogous project on dewikibooks [[:b:de:Wikibooks:Löschkandidaten/ 2011-04#Der einfache Weg zum Sprachgenie|was deleted in 2011 for similar reasons]]. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 21:20, 7 October 2026 (UTC)

:{{Vd}} ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 15:30, 12 October 2026 (UTC)

== [[The Permanent Advantage]] ==
Probably LLM-generated, given broken templates, references to Claude, and section identifiers. This could probably be speedied, but not 100% sure so throwing it to RfD. Even regardless of whether it's LLM-generated or not, I can't see any way it's really suitable for the project. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 07:49, 10 October 2026 (UTC)

:{{vd}} - a book ''about'' chess problems isn't necessarily out of scope, but there needs to be some written content to accompany the problems. And I'm not sure these are even meaningful problems - the few problems with viewable Lichess links appear to be in the early game, so there aren't necessarily objective &quot;solutions&quot; to them. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 19:51, 10 October 2026 (UTC)
:{{vd}}, the Claude references throughout the book support that it's LLM-generated. [[User:Ternera|Ternera]] ([[User talk:Ternera|discuss]] • [[Special:Contributions/Ternera|contribs]]) 14:55, 11 October 2026 (UTC)
== [[Digital Synthora]] ==
Not within WB scope since it seems to be entirely fabricated by the editor. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 14:20, 12 October 2026 (UTC)

:{{vd}} While some amount of original research is allowed here, completely fabricated topics aren't. This is just fiction writing, which is nice, but not within our scope. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 15:30, 12 October 2026 (UTC)
:{{vd}} - per my initial tag, this appears to be an invention of the page creator; I can't find anything relevant online beyond the empty https://synthoraactstuff.fandom.com/. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 01:32, 13 October 2026 (UTC)</text>
      <sha1>eo87984msz87jmd5eii6v3shhn2wjpx</sha1>
    </revision>
    <revision>
      <id>4675777</id>
      <parentid>4675774</parentid>
      <timestamp>2026-10-13T02:05:19Z</timestamp>
      <contributor>
        <username>~2026-40500-29</username>
        <id>3615407</id>
      </contributor>
      <comment>/* International Baccalaureate */ Reply comment</comment>
      <origin>4675777</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="41759" sha1="emhf4lffxeitcj9c0h3oudlhv57npr0" xml:space="preserve">__NEWSECTIONLINK__
[[Category:Wikibooks deletion|{{PAGENAME}}]]
{{Discussion Rooms}}
{{TOCleft}}
{{shortcut|WB:RFD}}
{{Requests for deletion/New deletion}}
{{Requests for deletion/Deletion intro}}
&lt;!-- New deletion nominations go at the bottom of page. --&gt;

== [[Salute, Jonathan!]] and its translations ==

&lt;div style=&quot;column-count: 7;&quot;&gt;
* [[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]])
&lt;/div&gt;

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|&lt;small&gt;|}}'''Done'''{{#ifeq:|small|&lt;/small&gt;|}} — [[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)

:{{keep}} 100% keep. These books are a core part of language textbooks on Wikibooks and have been for years. Not sure why this is even being debated.--[[User:Xania|Xania]] [[Image:Flag_of_Estonia.svg|15px]]  [[Image:Flag_of_Ukraine.svg|15px]] [[User talk:Xania|&lt;sup&gt;talk&lt;/sup&gt;]] 17:55, 16 May 2026 (UTC)

::With all due respect, some of the books included in this nomination (like [[Sin Chao, Jonathan!]]) are written in constructed languages which are not substantially attested anywhere else. I struggle to imagine any educational purpose for such a book. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 00:12, 17 May 2026 (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)
:I  would be interested in a book that explains what an [[International Baccalaureate]] is. They may be books about it in the real world, but they are not free and with the online world becoming a fortress of paywalls I wonder how much longer one would be able to find such information on the web. This is what the  wikipedia article says:
:* This article '''is missing information''' about the educational programs and curricula. Please expand the article to include this information. Further details may exist on the [[wikipedia:Talk:International_Baccalaureate#|talk page]].  ''(March 2025)''
:[[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 02:05, 13 October 2026 (UTC)

== [[Character List for Baxter&amp;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 (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''vf&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 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 ''&quot;Using the Finnish Language&quot;'' or ''&quot;Put Finnish Language into Use&quot;'' for a direct translation.   [[User:Zache|Zache]] ([[User talk:Zache|discuss]] • [[Special:Contributions/Zache|contribs]]) 11:57, 14 November 2024 (UTC)

== [[AT&amp;T Mobility FAQ]] ==

* [[AT&amp;T Mobility FAQ]]
* [[AT&amp;T Mobility FAQ/MEdia Net Configuration]]
* [[AT&amp;T Mobility FAQ/Data Connect Configuration]]
An ''extremely'' outdated FAQ on AT&amp;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 &quot;tethering&quot; 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]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[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 &quot;Archive:&quot;) 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]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[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]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[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)

== [[A-level Computing AQA Paper 1 Skeleton program 2027]] ==
This was proposed for speedy deletion by [[User:Omphalographer]] as 'not being a book'. However, I think this page's future requires further discussion from the community. Maybe some input would be appreciated?[[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 23:51, 21 September 2026 (UTC)

:As best I can tell, this is a page students are using to collaborate on solutions for a standardized test. There are a number of similar pages for other years linked from [[A-level Computing/AQA/Paper 1/Skeleton program]].
:This is not a good fit for Wikibooks. If these students are interested in this kind of collaboration, it should take place elsewhere. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 00:14, 22 September 2026 (UTC)
::The project can be moved to Wikiversity, I think. If the students can contribute it and make sure it complies with Wikibooks' guidelines, it can stay here. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:17, 22 September 2026 (UTC)
:::@[[User:Omphalographer|Omphalographer]] @[[User:TechVindicator|TechVindicator]]
:::There's been a Wikibook on this every single year, as I mentioned in my comment on the deletion notice. That doesn't mean that this shouldn't be on Wikiversity, just that there is ample precedent of it being a Wikibook.  Dunno if this matter to those kind of editorial decisions, though. [[Special:Contributions/~2026-51010-27|~2026-51010-27]] ([[User talk:~2026-51010-27|talk]]) 13:39, 22 September 2026 (UTC)
::::@[[User:~2026-51010-27|~2026-51010-27]]: How would the page comply with [[WB:What is Wikibooks?|Wikibooks' mission]]?. Could you provide an explanation of what the project is?  If it's a collaborative project to work on solutions for a standardized test (like @[[User:Omphalographer|Omphalographer]] said), it would be more suitable for Wikiversity. If it's a textbook about A-level computing, then it would be suitable here. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 13:58, 22 September 2026 (UTC)
:::::Hi,
:::::This is definitely the former, not the latter. As I said, I don't particularly think this should be on Wikibooks, it just happens the previous years had been, and clearly they weren't subject to this degree of scrutiny 😅
:::::I have created https://en.wikiversity.org/wiki/A-level_Computer_Science_AQA_Paper_1_Skeleton_program_2027 - I'll delete the content of the page and put the link at the top. If there is a more appropriate banner to indicate the migration, please make it look how it should :D [[User:MrBerard|MrBerard]] ([[User talk:MrBerard|discuss]] • [[Special:Contributions/MrBerard|contribs]]) 10:23, 29 September 2026 (UTC)
::::::I can't seem to put a link without the edit being deemed destructive, so I'll let you trusted people do what's needed. [[User:MrBerard|MrBerard]] ([[User talk:MrBerard|discuss]] • [[Special:Contributions/MrBerard|contribs]]) 10:27, 29 September 2026 (UTC)

== [[Talmudic aramic]] ==
Per the user's other mass-created pages, I concur with the AI flagging that Kittycataclysm placed on the page. I believe this to be LLM-generated, and it should thus be deleted. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 03:29, 30 September 2026 (UTC)

:{{vd}}, LLM spam. [[User:Ternera|Ternera]] ([[User talk:Ternera|discuss]] • [[Special:Contributions/Ternera|contribs]]) 13:22, 30 September 2026 (UTC)
:{{vd}} - like most LLM-generated books, this is heavy on structure and light on substance. Most of the content amounts to a poorly organized glossary, and there are a lot of pieces missing. (For instance, there is no discussion of the grammar of the language beyond a couple of fixed expressions.) [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 19:11, 1 October 2026 (UTC)
:{{vd}} per stated reasoning. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 14:43, 12 October 2026 (UTC)

== [[Job Search]] ==
* as well as [[Job Search Automation for College Students]].

Neither of these books contains any useful information. The first book seems to be written primarily to funnel users to the second, and the second to funnel users to [[PlanoTse Handbook for Job Search Automation]], which was deleted last year. (The deletion request doesn't seem to have been archived.)

The sum total of information in these two books is, essentially, &quot;you can search for jobs online&quot;, which is insultingly trivial. The second book's suggestion that users automate the job search process is of no practical value; most web search engines and job search sites nowadays will detect and block automated access.

[[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:36, 1 October 2026 (UTC)
: {{vd}} and redirect to [[Find Employment]]. ‑‑[[User:Kai Burghardt|Kai Burghardt]] ([[User talk:Kai Burghardt|discuss]] • [[Special:Contributions/Kai Burghardt|contribs]]) 05:14, 2 October 2026 (UTC)

== [[Wikipage]] ==
Like a few other books created by this user, the purpose of this book appears to have been to promote a piece of software written by the author ([[User:Planotse]]). The software is no longer available, and there is no actual content in the book.

[[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:40, 1 October 2026 (UTC)

:{{Vd}} ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 15:30, 12 October 2026 (UTC)

== [[Becoming a Linguistic Mastermind]] ==
Old book (created 2007) with no substantial content. The intent of this book appears to have been to create a single textbook encompassing ''all'' languages, with sub-courses for each language at [[Becoming a Linguistic Mastermind/The courses]], but no such courses were ever created. An analogous project on dewikibooks [[:b:de:Wikibooks:Löschkandidaten/ 2011-04#Der einfache Weg zum Sprachgenie|was deleted in 2011 for similar reasons]]. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 21:20, 7 October 2026 (UTC)

:{{Vd}} ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 15:30, 12 October 2026 (UTC)

== [[The Permanent Advantage]] ==
Probably LLM-generated, given broken templates, references to Claude, and section identifiers. This could probably be speedied, but not 100% sure so throwing it to RfD. Even regardless of whether it's LLM-generated or not, I can't see any way it's really suitable for the project. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 07:49, 10 October 2026 (UTC)

:{{vd}} - a book ''about'' chess problems isn't necessarily out of scope, but there needs to be some written content to accompany the problems. And I'm not sure these are even meaningful problems - the few problems with viewable Lichess links appear to be in the early game, so there aren't necessarily objective &quot;solutions&quot; to them. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 19:51, 10 October 2026 (UTC)
:{{vd}}, the Claude references throughout the book support that it's LLM-generated. [[User:Ternera|Ternera]] ([[User talk:Ternera|discuss]] • [[Special:Contributions/Ternera|contribs]]) 14:55, 11 October 2026 (UTC)
== [[Digital Synthora]] ==
Not within WB scope since it seems to be entirely fabricated by the editor. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 14:20, 12 October 2026 (UTC)

:{{vd}} While some amount of original research is allowed here, completely fabricated topics aren't. This is just fiction writing, which is nice, but not within our scope. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 15:30, 12 October 2026 (UTC)
:{{vd}} - per my initial tag, this appears to be an invention of the page creator; I can't find anything relevant online beyond the empty https://synthoraactstuff.fandom.com/. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 01:32, 13 October 2026 (UTC)</text>
      <sha1>emhf4lffxeitcj9c0h3oudlhv57npr0</sha1>
    </revision>
  </page>
  <page>
    <title>Wikibooks:Requests for undeletion</title>
    <ns>4</ns>
    <id>387</id>
    <revision>
      <id>4675749</id>
      <parentid>4675574</parentid>
      <timestamp>2026-10-12T15:36:11Z</timestamp>
      <contributor>
        <username>Codename Noreste</username>
        <id>3441010</id>
      </contributor>
      <comment>/* User:Ottawahitech/American politics */ reply ([[mw:c:Special:MyLanguage/User:JWBTH/CD|CD]])</comment>
      <origin>4675749</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="20470" sha1="epm7037rptsxke5abnog2005z9mv546" xml:space="preserve">__NEWSECTIONLINK__
[[Category:Wikibooks deletion|{{PAGENAME}}]]
{{Discussion Rooms}}
{{TOCleft}}
{{shortcut|WB:RFU}}
{{Requests for deletion/New undeletion}}
{{Requests for deletion/Undeletion intro}}
&lt;!-- New undeletion requests go at the bottom of this page. --&gt;

== [[Character Encodings]] ==
*I didn't see the deletion discussion, as the latest author of this wikibook. &lt;s&gt;I want to know what work could be done to fix this, if it was restored.&lt;/s&gt; I see that it needs content outside of code tables for it to be valid- if restored, I will add pages for MS-DOS, HP, and EBCDIC. What else needs to be done? If restoring is impossible, I at least want to view it.[[User:Alexlatham96|Alexlatham96]] ([[User talk:Alexlatham96|discuss]] • [[Special:Contributions/Alexlatham96|contribs]]) 21:37, 9 March 2026 (UTC)

**Maybe this can be merged into [[Introduction to Computer Information Systems]] or something similar. [[User:Alexlatham96|Alexlatham96]] ([[User talk:Alexlatham96|discuss]] • [[Special:Contributions/Alexlatham96|contribs]]) 21:44, 9 March 2026 (UTC)
**:Hi, [[User:Alexlatham96|Alexlatham96]]. I closed a [[Special:Diff/4622001|recent deletion discussion]] about the book, because: {{tq|Was never fleshed out into a proper book and consists only of code tables}}. I'll ping @[[User:Kittycataclysm|Kittycataclysm]] here if they have a second opinion, and because they created the discussion (that never had any participation). There were hundreds of pages in this book that will take some time to restore. [[User:Codename Noreste|&lt;span style=&quot;color:#0024FF&quot;&gt;Codename Noreste&lt;/span&gt;]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 00:32, 10 March 2026 (UTC)
**::Chiming in here to elaborate on my reasoning! Per [[WB:WIW]], {{tq|as a general rule, only instructional books are suitable for inclusion. Non-fictional books (as well as fictional ones) that aren't instructional aren't allowed on Wikibooks}}. Examples of nonfictional books that aren't instructional/allowed include reference works like dictionaries, which are only really allowed as part of larger instructional books and not on their own. Based on the contents I saw here, the content was solely reference materials and not instructional materials. I see no problem with consolidating and migrating the content to something like a useful appendix as part of another book. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:15, 11 March 2026 (UTC)
**:::Note that these pages were created as transwiki back in late 2024 from Wikipedia (and they were deleted afterwards), and since these were deleted now from WikiBooks, they're no longer visible (also, they're still deleted from Wikipedia). However, &quot;Wayback Machine&quot; seems to have a copy of it, but it may not be complete.
**:::If a restoration here isn't possible, what should be done instead?
**:::[[Special:Contributions/&amp;#126;2026-15548-70|&amp;#126;2026-15548-70]] ([[User talk:&amp;#126;2026-15548-70|talk]]) 19:03, 11 March 2026 (UTC)
**::::This was actually created in an earlier transwiki from Wikipedia (there were two)&lt;s&gt;-&lt;/s&gt; the first being in July 2020. I support the proposal to make it an appendix to Introduction to Computer Information Systems or something similar.[[User:Alexlatham96|Alexlatham96]] ([[User talk:Alexlatham96|discuss]] • [[Special:Contributions/Alexlatham96|contribs]]) 20:15, 11 March 2026 (UTC)
**:::::{{ping|Alexlatham96}} which pages would you want to be undeleted? I can help. [[User:Codename Noreste|&lt;span style=&quot;color:#0024FF&quot;&gt;Codename Noreste&lt;/span&gt;]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 22:19, 11 March 2026 (UTC)
**::::::Let's start with the MS-DOS (code page numbers 3846 and lower) and HP code tables section, because these were the most recently transwikied (people will be especially looking for code pages 775, 852, 855, 857, and 860). Once this is done, we can do the EBCDIC code tables, which were also transwikied (and I finished adding what was planned for Wikipedia).[[User:Alexlatham96|Alexlatham96]] ([[User talk:Alexlatham96|discuss]] • [[Special:Contributions/Alexlatham96|contribs]]) 00:17, 12 March 2026 (UTC)
**:::::::I've undeleted all HP code table sections, and to clarify, do you want ALL MS-DOS sections lower than 3846 (including undeleting those in the 100-700 range) to be undeleted? [[User:Codename Noreste|&lt;span style=&quot;color:#0024FF&quot;&gt;Codename Noreste&lt;/span&gt;]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 00:31, 12 March 2026 (UTC)
**::::::::Yes, including 3846. [[User:Alexlatham96|Alexlatham96]] ([[User talk:Alexlatham96|discuss]] • [[Special:Contributions/Alexlatham96|contribs]]) 00:55, 12 March 2026 (UTC)
**:::::::::{{done|All done}}. [[User:Codename Noreste|&lt;span style=&quot;color:#0024FF&quot;&gt;Codename Noreste&lt;/span&gt;]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 02:29, 12 March 2026 (UTC)
**::::::::::Great. Let me know when you have time to undelete the EBCDIC section- people will be looking for code pages 37, 500, 875, and 1026 especially.[[User:Alexlatham96|Alexlatham96]] ([[User talk:Alexlatham96|discuss]] • [[Special:Contributions/Alexlatham96|contribs]]) 22:10, 12 March 2026 (UTC)
**::::::::::Update: also the two in the ISO section- these are standards.[[User:Alexlatham96|Alexlatham96]] ([[User talk:Alexlatham96|discuss]] • [[Special:Contributions/Alexlatham96|contribs]]) 06:29, 14 March 2026 (UTC)
***Thank you. I also see that the old administrator is inactive, and never found out about this. There &lt;s&gt;will&lt;/s&gt; may have to be a new administrator other than me, since I am not one on Wikipedia or Wikibooks. &lt;s&gt;Does another user with knowledge of the topic like Drmccreedy or HarJIT have admin powers?&lt;/s&gt;[[User:Alexlatham96|Alexlatham96]] ([[User talk:Alexlatham96|discuss]] • [[Special:Contributions/Alexlatham96|contribs]]) 03:34, 10 March 2026 (UTC)
***Update: I found out they do not have admin rights, but can still do non-admin tasks. The authors of Unicode's legacy encoding proposals (latest being L2-26/077) could also help out if they're active here.[[User:Alexlatham96|Alexlatham96]] ([[User talk:Alexlatham96|discuss]] • [[Special:Contributions/Alexlatham96|contribs]]) 03:55, 10 March 2026 (UTC)
* @[[User:Alexlatham96|Alexlatham96]], [[Character Encodings]] and its subpages are all now restored. I apologize for the huge delay; thank you for your patience. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:56, 2 October 2026 (UTC)
** Thank you!!! Adding descriptions to pages.[[User:Alexlatham96|Alexlatham96]] ([[User talk:Alexlatham96|discuss]] • [[Special:Contributions/Alexlatham96|contribs]]) 01:45, 5 October 2026 (UTC)
***Started the Glossary. [[Talk:Character Encodings/Code Tables]] has still not been restored yet. [[User:Alexlatham96|Alexlatham96]] ([[User talk:Alexlatham96|discuss]] • [[Special:Contributions/Alexlatham96|contribs]]) 02:05, 5 October 2026 (UTC)
***:{{done}} ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 02:11, 5 October 2026 (UTC)
****Two more missing: [[Talk:Character Encodings/Code Tables/EBCDIC]] and [[Talk:Character Encodings/Code Tables/ISO]]. [[User:Alexlatham96|Alexlatham96]] ([[User talk:Alexlatham96|discuss]] • [[Special:Contributions/Alexlatham96|contribs]]) 15:53, 11 October 2026 (UTC)
****: {{done|Restored}}. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 16:01, 11 October 2026 (UTC)

== Markdown ==
The page [[Markdown]] was short but pretty sweet. It showed Markdown features by example and contained decent external links. He who would want to expand the page had the option. I find the page to be a minimum useful product/artifact, to be ideally restored. For reference, [https://web.archive.org/web/20250427011600/https://en.wikibooks.org/wiki/Markdown the page in Wayback Machine]. --[[User:Dan Polansky|Dan Polansky]] ([[User talk:Dan Polansky|discuss]] • [[Special:Contributions/Dan Polansky|contribs]]) 15:36, 5 May 2026 (UTC)
: {{courtesy ping}} to [[User:Kittycataclysm|Kittycataclysm]] who marked the page for speedy deletion. [[User:Codename Noreste|&lt;span style=&quot;color:#0024FF&quot;&gt;Codename Noreste&lt;/span&gt;]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 19:00, 5 May 2026 (UTC)
::@[[User:Codename Noreste|Codename Noreste]] thank you! I think for me this relates to recent on-wiki discussions we've been having in the sense that I don't think it makes sense to host any content that could theoretically be improved by someone at some time in the future. Even if the content is valid (which it seems to be!), the work is not set up to be book-like, I don't think it's in scope here, and I can't see someone coming around and turning it into a book within a reasonable time frame. Does this help? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 12:42, 8 May 2026 (UTC)
::: {{courtesy ping}} to [[User:Dan Polansky|Dan Polansky]]. [[User:Codename Noreste|&lt;span style=&quot;color:#0024FF&quot;&gt;Codename Noreste&lt;/span&gt;]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 16:28, 8 May 2026 (UTC)
::: {{Ping|Kittycataclysm}} The content is not book-like, but I do not recall this having been a requirement in Wikibooks (despite the name). If there is a requirement that the content should be book-like, it should be made into a policy. I created other pages that were instructional with no chance of being book-like in the past. Some examples of non-book-like pages include [[less]], [[grep]] and [[sed]].
::: The content is minimum useful artifact for the head and is instructional.
::: Either way, can you please at least restore the content in my user space? --[[User:Dan Polansky|Dan Polansky]] ([[User talk:Dan Polansky|discuss]] • [[Special:Contributions/Dan Polansky|contribs]]) 06:15, 18 May 2026 (UTC)
::::@[[User:Dan Polansky|Dan Polansky]] language in policy does refer to Wikibooks content as book-like. For example, per [[WB:WIW]]:
::::* {{tq|&quot;The site should primarily be used for developing textbooks, textbook-like books, and supporting book-based instructional materials&quot;}}
::::* {{tq|&quot;As a general rule, only instructional books are suitable for inclusion&quot;}}
::::* {{tq|&quot;Wikibooks includes both minor and major book-like projects&quot;}}
::::For other admins: if I am missing something obvious, please let me know. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:43, 20 May 2026 (UTC)
::::: {{Ping|Kittycataclysm}} Thank you. I note: 1) it says &quot;primarily&quot;, which means &quot;not exclusively&quot;; 2) &quot;instructional materials&quot; is much broader than books.
::::: Moreover, I checked [https://en.wikibooks.org/w/index.php?title=Wikibooks:What_is_Wikibooks%3F&amp;oldid=3797401 2021 version] of the policy and did not find the text you are quoting. When was the text introduced, by what process and who approved the text? --[[User:Dan Polansky|Dan Polansky]] ([[User talk:Dan Polansky|discuss]] • [[Special:Contributions/Dan Polansky|contribs]]) 04:25, 20 May 2026 (UTC)
::::: Part of the answer lies in [https://en.wikibooks.org/w/index.php?title=Wikibooks:What_is_Wikibooks%3F&amp;diff=prev&amp;oldid=4377929 this edit] of yours from 9 March 2024, which does not trace to a discussion or a vote, but traces to [[Wikibooks:Policies and guidelines]]. However, [[Wikibooks:Policies and guidelines]] is not marked as a policy.
::::: Be it as it may, it does not answer my question: where is the evidence of consensus for the changes, minimally in the form of a discussion, and ideally in the form of a request for comments or a vote?
::::: Let me also ask from the point of view of examining other examples that I already brought up: is it your view that [[less]], [[sed]] and [[grep]] should be deleted as non-books, too short to be considered books?
::::: Let me also ask about the ''process'': why was RFD not used and instead speedy was used? From what I recall, Wikibooks used to delete subpar content via RFD, including all those outlines with no content proper. --[[User:Dan Polansky|Dan Polansky]] ([[User talk:Dan Polansky|discuss]] • [[Special:Contributions/Dan Polansky|contribs]]) 04:41, 20 May 2026 (UTC)
::::::@[[User:Dan Polansky|Dan Polansky]]
::::::# That's a good catch about the March 9 edit—I can't recall why I made that decision, but I think you're right that moving text from a non-policy page to a policy page without discussion is not appropriate. My understanding is that the general sentiment is still correct, but we'll need more community discussion to officially integrate it into policy.
::::::# Regarding the other examples you listed: assuming the book-like requirement is the community consensus, I don't think they can stand on their own, but it might be possible to turn them into a more cohesive book.
::::::# Regarding the process, I flagged for speedy deletion because I was on the fence about whether it was a speedy or an RFD—in these cases, I usually flag for another admin to review instead of making the deletion myself.
::::::Since this is getting more into community consensus territory, I am looping in other active users and admins to weigh in @[[User:Atcovi|Atcovi]] @[[User:Leaderboard|Leaderboard]] @[[User:Xania|Xania]] @[[User:MarcGarver|MarcGarver]] @[[User:SHB2000|SHB2000]] @[[User:Omphalographer|Omphalographer]] @[[User:JJPMaster|JJPMaster]]. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 13:04, 20 May 2026 (UTC)
::::::: @Kittycataclysm: Thank you for this response. And let me also thank you for your clean-up effort at Wikibooks; hardly anyone wants to do that and you seem to be doing quite a lot of it. --[[User:Dan Polansky|Dan Polansky]] ([[User talk:Dan Polansky|discuss]] • [[Special:Contributions/Dan Polansky|contribs]]) 13:56, 20 May 2026 (UTC)
:::::::Wikibooks has never been heavy on written policies and tends to operate in line with what the current active community thinks is right. This isn't unusual, many small projects work like that. So getting hung up on who edited a policy and whether it was approved isn't really important - there have been many proposals put forward to amend WIW, and you need to search to find them as they are buried in different talk pages and project pages - what's important is what the community wants to do now. For what it is worth it is pretty clear from its very inception that the intention of Wikibooks was to host textbooks (see [[m:Talk:Science_Hypertextbook_project]]). That doesn't preclude the community from changing its mind, now or in the future. [[User:MarcGarver|MarcGarver]] ([[User talk:MarcGarver|discuss]] • [[Special:Contributions/MarcGarver|contribs]]) 15:23, 20 May 2026 (UTC)
:::::::: 1) This use of the word &quot;community&quot; (instead of e.g. &quot;editors&quot;) is a huge red flag. 2) The above attitude allows for a manipulation of the project, especially by people who are more interested in exercising their power than contributing any useful content. If there really is a consensus of the &quot;current active community&quot; (whatever that is supposed to mean), that current community should not have any difficulty passing it through a request for comment or a vote. From my experience, projects that disregard policies start to get controlled by bad actors, often actors who do not have the skill to do any content work so they natually tend toward mere administrators (also known by Steve Jobs as bozos). --[[User:Dan Polansky|Dan Polansky]] ([[User talk:Dan Polansky|discuss]] • [[Special:Contributions/Dan Polansky|contribs]]) 07:06, 23 May 2026 (UTC)
:::::::My thoughts are mostly with Marc's and Leaderboard's here. --[[User:SHB2000|SHB2000]] ([[User talk:SHB2000|discuss]] • [[Special:Contributions/SHB2000|contribs]]) 22:57, 20 May 2026 (UTC)
::::::::+1 —[[User:Atcovi|Atcovi]] [[User talk:Atcovi|(Talk]] - [[Special:Contributions/Atcovi|Contribs)]] 17:32, 23 May 2026 (UTC)
:I think the book does not qualify in its current state (but as a draft, wouldn't have qualified for deletion either). Markdown is indeed a language without a lot to write; however, I think the book is too small as written. The fact that it's only a single page is fine. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 13:08, 20 May 2026 (UTC)
:: But ''why'' does it not qualify, given it shows the most important features of Markup by example? (It is not a book and probably never will be. It is too short for that and will be too short, even if expanded.) --[[User:Dan Polansky|Dan Polansky]] ([[User talk:Dan Polansky|discuss]] • [[Special:Contributions/Dan Polansky|contribs]]) 13:14, 20 May 2026 (UTC)
:::It's too brief in my opinion. A Wikibook tends to have significantly more detail, even if it's just one page. I think the book can absolutely be expanded in a form that will allow it to stay here. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 14:15, 20 May 2026 (UTC)
:::: Brief for what purpose or objective? As a user of Markdown, I want to know the answer to the following questions: 1) What is the core syntax of Markdown (so that I can use it productively)? 2) What are some of the best external sources about Markdown? I provided an answer to both questions. --[[User:Dan Polansky|Dan Polansky]] ([[User talk:Dan Polansky|discuss]] • [[Special:Contributions/Dan Polansky|contribs]]) 07:21, 23 May 2026 (UTC)

== [[Template:Message box]] ==
There are currently [[Special:WhatLinksHere/Template:Message box|128 pages linking to this template]] which are currently displaying error messages instead of the intended text. Even if there is a module which implements some of the technical functionality previously used by this template, a template is still needed to simplfiy the process of invoking that module - even if it just expands to &lt;code&gt;&lt;nowiki&gt;{{#invoke:Message box}}&lt;/nowiki&gt;&lt;/code&gt;. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 19:09, 9 October 2026 (UTC)

== Pages related to citations ==
* [[Doi (identifier)]]
* [[PMID (identifier)]]
* [[ISSN (identifier)]]
* [[PMC (identifier)]]

These pages are all linked automatically by citation templates like {{tl|Cite journal}}. I understand that their content is out of scope for Wikibooks, but we're still linking to them - either they should exist, or we should modify the citation module to not link to them. Having them exist as soft redirects seems like the easier solution. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 19:14, 9 October 2026 (UTC)

:Immediate solution is soft redirects, longer-term solution is removal from the template or at the very least, turning them into links to Wikipedia articles directly. I actually tried to resolve this when I first became an admin, but deciphering how to get these links out of the modules was too tricky for my smooth brain. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 20:33, 9 October 2026 (UTC)

== [[User:Ottawahitech/American politics]] ==
Please undelete. Thanks in advance, [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 19:00, 11 October 2026 (UTC)
: I do not see any reasoning on why this user subpage should be undeleted. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 15:36, 12 October 2026 (UTC)</text>
      <sha1>epm7037rptsxke5abnog2005z9mv546</sha1>
    </revision>
  </page>
  <page>
    <title>Aros/User/Docs</title>
    <ns>0</ns>
    <id>13106</id>
    <revision>
      <id>4675760</id>
      <parentid>4675563</parentid>
      <timestamp>2026-10-12T19:06:20Z</timestamp>
      <contributor>
        <username>Jeff1138</username>
        <id>301139</id>
      </contributor>
      <minor />
      <origin>4675760</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="139482" sha1="6yov58guq6lc3c6u4d76nwj9fhew2cy" xml:space="preserve">{{ArosNav}}

==What is AROS==

Google translation 
[http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=de&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fw%2Findex.php%3Ftitle%3DAros%2FUser%2FDocs German], [http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=nl&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fw%2Findex.php%3Ftitle%3DAros%2FUser%2FDocs Dutch], [http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=fr&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fw%2Findex.php%3Ftitle%3DAros%2FUser%2FDocs French], [http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=it&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fw%2Findex.php%3Ftitle%3DAros%2FUser%2FDocs Italian], 
[http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=da&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fw%2Findex.php%3Ftitle%3DAros%2FUser%2FDocs Danish], 
[http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=es&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fw%2Findex.php%3Ftitle%3DAros%2FUser%2FDocs Spanish], [http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=hi&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fw%2Findex.php%3Ftitle%3DAros%2FUser%2FDocs Hindi], [http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=zh-CN&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fw%2Findex.php%3Ftitle%3DAros%2FUser%2FDocs Chinese], 
[http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=ru&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fw%2Findex.php%3Ftitle%3DAros%2FUser%2FDocs Russian], 
[http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=pl&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fw%2Findex.php%3Ftitle%3DAros%2FUser%2FDocs Polish], [http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=ja&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fw%2Findex.php%3Ftitle%3DAros%2FUser%2FDocs Japanese], [http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=ko&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fw%2Findex.php%3Ftitle%3DAros%2FUser%2FDocs Korean], 
[http://translate.google.com/translate?hl=en&amp;sl=auto&amp;tl=pt&amp;u=http%3A%2F%2Fen.wikibooks.org%2Fw%2Findex.php%3Ftitle%3DAros%2FUser%2FDocs Portuguese], 


*Computer Hardware
*AROS (operating system)
*Applications and Games
*User


[http://www.osnews.com/story/15819 AROS] is one of the intermediate levels between the computer hardware and the user. It is an open-source, clean-room implementation of AmigaOS 3.x that can be run on many different computer architectures. It runs primarily on PC x86 32bit and 64bit but also on amiga motorola 68k and compatibles, some ARM like the Pi and Apple Silicon, RISC-V and some old PowerPC. 

This page will cover enough to be able to write the downloaded image to your preferred media, to run a LiveUSB, LiveCD or LiveDVD on your office/home PC (Live meaning you can test without changing your existing setup) and, ultimately, to use it.  

Intel / AMD PC hardware support mostly covers the years 2000 to 2024. At the moment, AROS is '''not''' recommended to be '''installed''' on a working vital data holding machine. Instead, writing to and booting from a '''USB stick''' could be a much better option. 

AROS is an hobby OS and can co-exist with Windows(TM), MacOSX(TM), Android(TM) or Linux(TM) and act as an alternative. 
Unfortunately, Aros has few developers so upgrades and improvements can take [https://sourceforge.net/p/aros/mailman/aros-cvs/ time to appear]. 

AROS core is now [http://en.wikibooks.org/wiki/Aros/Developer/IncompleteAPIs ~80%] finished and is usable, so keep in mind that the software is still considered ALPHA/BETA and in constant development. Currently AROS is fun to play with on a curiosity level, but it is also interesting to program. AROS has some multimedia features and has internet access.  

Most importantly, use AROS to its maximum potential as it stands now, find ways to have fun with it and share your experiences. 


Good Sites to visit 

: [https://www.arosworld.org/home.php Aros World User forum] 
: [https://arosnews.github.io/ AROS News]
: [https://www.facebook.com/ArosWorkshop/ Aros Workshop], 
: [https://www.osnews.com/topic/amiga-aros/ OSNews] 
: [https://www.reddit.com/r/aros/ Reddit]


: [https://archives.arosworld.org Aros Archives] 
: [https://aminet.net/ Aminet]
: [http://www.amiga-news.de/en/ English translation of German site]


: [https://aros.sourceforge.io AROS] with [https://aros.sourceforge.io/download.html ABIv1 downloads] 
: [https://github.com/aros-development-team/AROS Aros ABIv1 Codebase]
: [https://github.com/aros-development-team/AROS/issues register ABIv1 issues] and [https://sourceforge.net/p/aros/bugs/ old defunct bugs notification site] 


: [https://sites.google.com/view/arosone Aros One x86, x64] 
: [https://tinyarosdistro.flazio.com/ Tiny Aros x86 and x64]
: [https://arosnews.github.io/aros-portable/ AROS portable USB3 stick images of hosted Aros One x86 and x64 on debian] 
: [http://vmwaros.blogspot.com Icaros Desktop x86 now on sabbatical, very old edition] 
: [https://sites.google.com/site/arosaspireone AspireOS, of the netbook Aspire One, very old edition] 
: [https://github.com/deadwood2 Deadwood's builds], [https://www.axrt.org/download/aros/v11/ v11 64bit PC builds], [https://axrt.org/downloads-aros Updated i386 32bit PC builds], 
: [https://github.com/ezrec Ezrec x86 m68k mirror of old svn version]


: [http://arosalive.blogspot.co.uk/p/10-basic-aros-how-tos-tutorials.html Basic How To guides] 
: [http://arosgamer.blogspot.co.uk/ AROS Playground], [http://thewetmachine.net/tag/aros/ Jess Wet Machine], [https://aroshacking.wordpress.com/ Jon Robertson's AROS Experiences and FPC Free Pascal], [], 
:[http://www.apollo-accelerators.com/ Apollo Accelerators m68k], [http://www.amigablogs.net/ Amiga Blogs], [http://blog.a-eon.biz/blog/ Trevor Dickinson blog], 


: [https://forum.amiga.org/ Amiga OS AOS 3.x forum] 
: [http://eab.abime.net/ EAB Amiga] 
: [http://www.amigaworld.net/ AmigaWorld] 
: [http://www.ppa.pl/ Polish Amiga Like News] 
: [http://www.apollo-core.com/ Apollo Forum] 
: [https://amigaalive.blogspot.com/ AmigaAlive]
: [https://www.amigalove.com/software Disk Mags]
: [https://amigachristmastree.ultimateamiga.com/ Xmas Amiga Game Jam]
: [https://www.reddit.com/r/amiga/ Amiga]


== Distributions aka Distros ==

For end users there are distributions (ready made with selected apps aiming to be easy to use), mostly created and maintained by one person in their own workflow/style. They reuse the nightly boot compiles to suit their needs and possibly other end users. You are free to create your own if required. 

* For native 64bit Intel/AMD: [https://sites.google.com/view/arosone Aros One x64], [https://tinyarosdistro.flazio.com/ Tiny Aros],
* For native 32bit Intel/AMD which will run on 64bit machines: [https://sites.google.com/view/arosone Aros One x86], [https://www.tinyaros.it/ Tiny Aros], 
* For native 68k [https://sites.google.com/view/arosone Aros One m68k], [http://www.aros-platform.de/ AROS Vision], 

'''Please, keep in mind that the distros listed above use a different ABI (abi v11) , which is NOT binary compatible with the official ABI V1.'''
* For hosted Linux usb drive image [https://arosnews.github.io/aros-portable/ x64 Debian hosted version of Aros One], 
* For hosted ARM there is [https://github.com/jonx/AROS-AArch64/releases alpha for Apple Silicon] and [https://aros.sourceforge.io/nightly1.html RaspberryPi Pi3, Pi4, Pi400, Pi5, 500+ raspi-aarch64-system native 64bit] 


AROS was originally developed on Linux but can run on an Intel-based Linux distro as an app. As time has gone on, it can be run as an app on many more operating systems (Windows, FreeBSD, Linux and limited on MacOS). This may sound strange: an OS running on top of another OS. 
Basically, this is to take advantage of drivers (audio, internet, graphics, etc.) and compiler environments, in the existing OS, with which people may be already familiar. The term we use for what AROS does is &quot;Hosted&quot;. 

AROS Native is the term coined to describe AROS being run without any OS underneath it. It runs alone just like AmigaOS(TM) did. As this version does not benefit from &quot;Hosted&quot; drivers, dedicated ones have to be ported/written. Hence the smaller range of supported hardware / peripherals. We have other pages highlighting this support 


AROS is open source so basically everyone can take part. The source is public on github and there are new commits most days. AROS is automatically compiled daily, result are the nightly builds hosted on Sourceforge. The nightly builds are only used for testing changes, testing software and the starting point for distribution maintainers or even your own distribution. They are very basic, miss some functionality and apps like web browsers and generic general appearance which can be changed. 

* The [https://sourceforge.net/projects/aros/files/nightly2/ Nightly2], [http://aros.sourceforge.net/download.php nightly builds File Release Service] or [http://aros.sourceforge.net/downloads/ Sourceforge Project Web builds] are made automatically every night directly from the Github and in the past, SVN (Subversion) tree and contain the latest code for the AROS operating system. It should be noted that the builds have not been tested in any way and can be horribly broken but usually are not. 

*ABIv1 standard for most nightly builds, it is where the most work is done by developers 
*ABIv11 offspring aka fork of 64bit PC ABIv1 i.e. another PC 64bit build 
*ABIv0 standard for PC 32bit intel / amd PC distributions for historic reasons 


==Media==

AROS media tends to boot in this tier list of media types, first internal HDD SSD, CD DVD drive, and finally usb drive (last two can depend on bios boot order) 

* USB .VHD 

[https://sites.google.com/view/arosone Aros One x86 and x64], with md5 below 

&lt;pre&gt;
0a656d53a9c902e9934000d8392e30ec *ArosOne-USB-1.3-64Bit.zip
7dd7119ab3e56d75ee852c137226b4d7 *ArosOne-USB-v1.2-x86_64-v11.zip
cf906eeaad4a83b3520b1896bdc6b0d3 *ArosOne-USB-v1.1-x86_64-v11.zip

e2eb8fe8cfd61c567b0152a61cf85251 *ArosOne-x86-v2.8-USB-IMG.zip
559909c75c2f56472c74267a7d075355 *ArosOne-x86-v2.7-USB-IMG.zip
93da5898508c1a8c05bb8991ab7bd117 *AROS One Image-USB-2.4.zip
59fcabd7090e47f12d54f7eb78cf0f45 *ArosOne-x86-v2.2-USB-Image.zip
24fb8de726ae8fc5fe5bac6d30f03dc5  ArosOne-x86-v2.0-USB-Image.zip
f3d725e990072edce633b59747911b6b  ArosOne-x86-v1.8-USB-IMG.zip
e089a24ae310e92fcc407a0125602ce8  Aros-One x86-IMG-USB-v1.6.zip
&lt;/pre&gt; 


[https://tinyaros.flazio.com/ Tiny AROS]

22bc993625b7c75b17263c0cc7e7baaa *Tiny Aros_copy.vhd (March 2024) 


There is usually a vhd image inside the zip that can be written to USB sticks which is so much faster than the old ISO written to physical CD DVD method. This .vhd can be written to an USB stick / ssd with these pieces of software below but it will erase the previous contents from the usb 

Windows - [https://www.raspberrypi.com/software/ RPi Raspberry Imager, use custom and see all files], [https://hddguru.com/software/HDD-Raw-Copy-Tool/ HDD-Raw-Copy-Tool], [https://rufus.ie/ Rufus up to version 3.20 may work with VirtualBox HD vhd images with Win7 but not some Rufus 4.x versions], [https://etcher.balena.io/ Balena Etcher but may spy on you], 

Linux   - [https://www.raspberrypi.com/software/ Raspberry Imager Ubuntu], Suse Image / Multi writer, dd, 

Mac     - 


* Virtual Machine .ISO or CDs DVDs 

 The native iso images are currently not compatible with Ventoy, Yumi, MultiBootUSB, Easy2Boot E2B, or similar 

&lt;pre&gt;
617a905b1665128c5e05f94dcc48e7f1 *AROS-One-v1.3-64Bit-v11.zip
11c8a147fcad7ecf52ae3a43e1934b69 *ArosOne-DVD-v1.2-x86_64-v11.zip
f93053d3b9ccf304d7e6ac3389e1987b *ArosOne-DVD-v1.1-x86_64-v11.zip

86d808a40dc7be389a758799a9b4f595 *ArosOne-x86-v2.0-ISO-DVD.zip
f1fc8599ef6a39e5df394e0f41d55526 *AROS-One-x86-ISO-DVD-v1.6.zip
&lt;/pre&gt;


You can use a virtual emulator like VirtualBox, VMWare to mount the iso image which can then be used to boot and/or install to USB. 

No current software can write an AROS ISO to a Pendrive. The author of ‘Rufus’ (who used an Amiga 500 as a child) once tried, but when he saw the system composition, he said he was unable to do it.

The solution is to boot the ISO from a VM (WMware, VBox), then install the AROS build on the Pendrive, which will eventually become a Live Pendrive that can be booted on a PC.

The only precaution is that in some cases it is necessary to thoroughly clean the Pendrive of any partitions and remove any bootloader that is not AROS. The Pendrive must remain raw without any partitions.

You can clean the USB stick on a PC with a program that manages hard disks. You need to do a partition wipe. On some USB sticks, you can clean it with InstallAROS.
For some USB pendrives, please use a reputable partition editor to remove any and all partitions from a usb pendrive as HDToolbox cannot do this task sometimes with a wipe all option. 


Previously the only installation option was CD-RW or DVD-RW, since the whole system can be burnt onto a single disk and can be reused when the next version is released. Good branded discs like Taiyo Yuden (later JVC) or Verbatim should be used to reduce frustration later. The days for this media is gone but kept here for information 

Since nobody currently sells AROS on any other media, you will need access to a CD/DVD burner to create the installation disk yourself. After it is on a CD or DVD, then access and writing to USB pendrives becomes available (this should be viewed as an outdated or last resort alternative method now), as well as using good USB manufacturers like Sandisk, Kingston, etc. rather than some other no-names. 

Try burning it to a CD-RW or DVD-RW using your CD/DVD burning program (most burning software have a burn iso option). The ideal writing speed is 2x or 4x, higher speeds can give errors and problems.  Check the writing integrity of your CD or DVD if your software has an option to do so before going any further. 

Standalone portable usb cd dvd drives do not boot physical burnt discs, please use an internal ide sata drive instead. 


* SD-card
For [https://aros.sourceforge.io/nightly1.html ARM Pi Aros 64bit], copy the files onto a FAT32 formatted micro SD card. 


==Booting==

The LiveUSB, and in the past LiveCD LiveDVD, is designed to trial (test drive) various operating systems without having to install them to your working system. 

Since 2011, UEFI was introduced to replace the original PC BIOS which made booting media more confusing. Some changes in the UEFI/bios may be needed 

*go into the bios using esc, f2 or f? and disable the Security -&gt; Secure Boot and maybe apply option for Legacy IDE mode 
*you may have to press F9, F10 or F12 or p on boot up to present a device boot options like USB or CD/DVD 
*disable the Fast Boot config so it would recognize portable DVD-drive and changed the Boot-sequence

Secure boot was introduced by Microsoft and later consortium, control what operating systems work with Secure Boot via shims. 
For Aros, it is best to disable and save the turn off change to Secure Boot (if you dual boot with Windows this will cause issues with further Window boots) 

 For the best experience, it is advised to install to another SSD than the one Windows resides on. 

The grub part of the boot should be fully automatic, and you should see a multiple choice graphic card screen after 10 seconds for USB or 40 seconds CDs and DVDs. 
If boot does not occur within a minute, please reboot and choose the VGA boot option as it relays a message stream so you can see where the issue lies. 

After the grub graphics choice, AROS takes over the booting and any issues can arise here 

If possible please use a branded usb pen drive as most of the time when we get reports of &quot;crashes right after grub boot selection&quot; it is mostly due to the recorded pendrive as they are made, notoriously on a will it work / will it fail nature, every time it is used. 
&lt;pre&gt;
So one usb drive written may stop at a System halted. Reset the machine. 
Or another pendrive will show give errors Smart Filesystem request - Volume 'Aros Live Drive' (DU0: usbscsi.device unit 0) There was an error while accessing this volume: 
Or if a FAT32 partition present - FAT filesystem - Device USBSCSI0P1 has a read error on block xxxxxxxx - 
&lt;/pre&gt;
Sadly, no drive even branded are resistant or totally reliable, so the only solution is to try another pendrive, and possibly to repeat, until no errors. 
It will give an indication on how reliable the usb drive could be. 


=====Advice for various machines=====

Some of the stages involved and shown on the display in a typical AROS boot start up 

&lt;pre&gt;
[MultiLoader]
[ELF Loader]
[Boot]

[HPET] 
[Kernel:ACPI]
[Kernel:APIC-IA32]
[Kernel:SMP APIC]
[HiddStorage]

ACPI: ????
ACPI Error 
[ACPI]AcpiOs????
[BattClock] Got RTC century offset 0x32 from ACPI 

[PCI] Scanning bus ? 
[AHCI] Sata 
[Vesa]  only if vesa is chosen as graphics option 

[ATA] detect hd &amp; cd drives 
[ATA0?] ata-identity 
[packet] fat.handler be.handler, etc. 
[DOS] 
[Storage:Bus]
[Storage:Controller]

[MSS] USB setup
[ehciInit] Port ? maps to controller ? 

[I2C] 
[ATI]
[drm] nouveau 
[AROSTCP]   if you have network driver prefs set up to start when booting 


&lt;/pre&gt;

; If boot fails, please give us some indication (pictures or videos) where the boot stops and the message(s) on screen. 


AROS's native SATA/AHCI driver doesn't always work. If you get errors related to ahci.device, try disabling it. At your chosen boot entry in the GRUB menu, Press E, scroll down to the ahci.device entry, and add a # or ; at the start of that line or delete it with Ctrl-K. Then press Ctrl-X or F10 to boot. 

If your disk isn't accessible at all with this change, you might need to change the SATA controller to IDE legacy mode in the BIOS: however, making this change will likely cause problems booting Windows on the same machine (if it's already installed). To disable ahci.device permanently, edit the text file &quot;SYS:Arch/pc/grub/grub.cfg&quot;, and remove the ahci.device line from all boot entries you intend to use.

SATA AHCI Timeout while waiting for device to complete operations with BIOS SATA entry set to AHCI mode stops at &quot;waiting for bootable media&quot; screen, changing BIOS SATA setting back to IDE mode may allow it to continue booting 

The ATA driver doesn't always work. If you get errors related to ata.device, try using the alternative in sys:devs/alt which is an older version.  Press E when your chosen boot entry is highlighted in the GRUB menu, scroll down to the ata.device entry, and change it to read &quot;module /Devs/Alt/ata.device&quot;. Then press Ctrl-X to boot. To make this change permanent, edit the text file &quot;SYS:Arch/pc/grub/grub.cfg&quot;, and change the path to ata.device in all boot entries you intend to use.


Further options (removing the &quot; &quot;) to add to the GRUB menus to disable certain other components for debugging:

&lt;pre&gt;
Disable AHCI                        &quot;AHCI=disable&quot;
Disable NVME                        &quot;NVME=disable&quot;

Disable ATA:                        &quot;ATA=disable&quot;
Disable ATA:                        &quot;ATA=nopci,nolegacy&quot;
ATA safe mode:                      &quot;ATA=nodma,32bit&quot;
Disable IDE from SATA:              &quot;ATA=32bit,nosata2pata&quot;
VIA / SIS with cdrom read io errors &quot;ATA=nodma,nopoll&quot; 

noacpi                   all [PCI] devices to be invisible to AROS. disk drives work but network, sound won't 
acpi=strict              if there are issues with sound after boot 

noioapic                 alternative to no acpi 

Set AHCI                            &quot;AHCI=force150/force300/force600&quot;
Disable AHCI/SATA:       comment out with a # ; or remove ahci.device line with Ctrl-K

Disable USB:             comment out # ; or remove pciusb.device and poseidon.library lines with Ctrl-K
Disable native graphics: &quot;nomonitors&quot;
USB3                     &quot;USB=xhci&quot; 
&lt;/pre&gt; 

Other useful grub command line options - nomonitors, noacpi, vesahack, nopoll 

Press Ctrl and X together (or F10) to exit and boot with the new options. Just experiment with different variations until successful. Those working options will need to be reused with every reboot of AROS until you can edit the grub.cfg and make it permanent i.e. install to hard disk or USB. 


* If you use VESA mode, you can see the debug log if you add 'vesahack' to the command  line.  This  will set up split-screen mode. In the upper half you'll see AROS screen, in the bottom - debug log. 
* ACPI ie. PCI hardware - If  you  get  crashes  at  early boot, try adding 'NOACPI' to the command line 


If you're having boot issues and have a null modem cable and a spare pc, a boot log is always useful. Edit your grub line to include debug=serial but would try with an with sysdebug=all in the line later as it can cause issues booting on machines with sysdebug=all enabled (corrupts the cpu initialization). 

However, if you feel you have found a genuine bug/fault in AROS that needs attention, please use the [http://sourceforge.net/tracker/?atid=439463&amp;group_id=43586&amp;func=browse bug submission form] to record as much information about what happened, why, and what hardware etc. you have so that people may try to assist you 


For Virtual machines VMWare VirtualBox, etc., attach and press play to start the ISO image 

If booting hasn't worked then it could be down to Bios/UEFI settings  


=====nvme.device=====

 Since 2018, nvme drives are standard on most machines 

The requirement is that a PC can boot with legacy mode/BIOS at the moment - Now as far as hardware goes on a newer machine with an NVME drive you may need to add NVME=disable as the NVME driver could potentially cause lockups. 

 This is still in testing and its' use should not be on or near precious own data 


=====AHCI=====

 Starting taking over since 2011 on a lot of machines 

* Check that UEFI (replacement for PC BIOS) has options set to remove UEFI SecureBoot option and apply CSM 
* SATA drive is set for Legacy or a mixture AHCI/IDE and not AHCI 


 AHCI sata can be very difficult to get working

Most Windows installs are already set to AHCI sata, changing this to a legacy IDE mode setting can help but please check if Windows will still boot. Some hardware like Lenovo laptops do not always like being set in legacy mode so only use as a last resort and aware of issues that can be caused. 

Now as far as hardware goes on a newer machine with an NVME drive you may need to add NVME=disable as the NVME driver could potentially cause lockups. 

With a 16C/32T chip machine, disable SMT and it should boot. 


=====ata.device for old BIOS's =====

 Pre 2010 this was the de facto standard method of providing settings to the computer at a lower level 

Some adjustments to the BIOS setup options are necessary (usually by pressing a key like DEL, F1, F2, F12 or ESC, p on the very early boot up of the computer). 

*Adjust booting options like moving USB hdd, CDROM higher as it is quite often disabled or placed lower by default, i.e. USB hdd, CD/DVD are placed at the top above the hard drive. Try looking here [http://www.windowsreinstall.com/articles/bios/ Windows] or [http://www.hiren.info/pages/bios-boot-cdrom Bios] or [http://www.wikihow.com/Set-Bios-to-Boot-from-a-CD-ROM Boot] or web search &quot;BIOS BOOT CDROM&quot;

* At the '''SAME''' time, check if the SATA/AHCI option is set to Emulate or IDE Legacy, though this can have '''issues''' with any OS already on the hard disk. If in doubt, do nothing and seek advice. 

* check that under BIOS settings you '''DO NOT''' have plug&amp;play OS selected as Aros at this point is unable to route interrupts on its own and needs the BIOS to do that. 

'''Save''' options changed at the end. 

PCITool can show if the motherboard chipset is in IDE mode. 
Class = 0x01 means STORAGE, Subclass = 0x01 means IDE. Also ProductID 0x3a20 resolves to non-AHCI mode in Intel ICH10 documentation.


==Installing==

We have a separate section [https://en.wikibooks.org/wiki/Aros/Platforms/x86_installing here]

We have a specific section for each CPU platform under the Specific platforms in the NavBar navigation bar on the right hand side menu 

error code (-6) when using the ahci.device (has writing to disk problem but not reading) is enabled. change this line in your grub and reboot 

&lt;pre&gt;
#module /Devs/ahci.device      &lt;&lt; disable
module /Devs/Alt/ata.device    &lt;&lt; add this line instead
&lt;/pre&gt;


==File structure overview==

AROS' directory structure is mostly identical to AmigaOS directory structure, with some additions.

AROS: or SYS: also known as DH0: (i.e. the drive partition with AROS system) has the following simplified list of the main drawers (Amigas term for directories/folders). 


{| class=&quot;wikitable&quot;
|boot:
| grub bootloader 
|----
|C:
| small apps, where AROS looks first for applications/games but will look at Tools, System afterwards
|----
|Classes:
| .class as well as datatypes 
|----
|Devs:
| .device .resource and in their own drawers (folders) .audio, .hidd, network, graphics 
|----
|L:
| where .handler files go 
|----
|Libs:
| where .library files go 
|----
|Locale:
| where help guide txt readme files go 
|----
|Prefs:
| applications that adjust or setup AROS functions and capabilities 
|----
|S:
| startup scripts (for the aros boot process '''not''' grub) are stored here
|----
|Storage:
| place to keep old or alternative device drivers
|----
|System:
| applications associated with AROS operating system
|----
|Tools:
| extra applications
|----
|Utilities:
| extra applications
|----
|WBStartup:
| copy applications here to autostart with needed icons, drawers, data etc
|----
|}

See [[Aros/User/DOS#Drives.2C_Files.2C_Assigns.2C_Directories|DOS manual: Drives, Files, Assigns, Directories]]


=== Filesystem ===

Whilst the kernel is the heart, the filesystem is the blood of the system they are split into two categories (only a few are supported) 
&lt;pre&gt;
Journalling     - SFS PFS3 but also NTFS ZFS XFS ext4 
Non-journaling  - FFS FAT32(VFAT) but also exFAT BtrFS ext2  
&lt;/pre&gt;

Filesystem options for AROS to install 
* SFS default 
* Professional File System PFS3 [http://eab.abime.net/showthread.php?t=52234&amp;highlight=pfs3+free&amp;page=13 only on motorola 68k at the moment] 
* FFS very old now but left in for legacy usage 

Other [https://archives.arosworld.org/index.php?function=browse&amp;cat=driver/filesystem filesystems] for storage purposes 
* FAT32 favorite as most OSs support 
* NTFS (can lock AROS) 
* exFAT 

The only filesystems that really NEED defragging (i.e. disk tidy up) are from Microsoft(TM) - exFAT/VFAT/NTFS
*SFS tries to do exactly the same thing, but in certain cases it doesn't do as well as PFS. But you can defrag SFS 
*PFS *minimises* the amount of fragmentation, but does not automatically defrags as it saves files to the drive 

The setup of the below filesystems is usually done by the distro maintainer but if not....
&lt;pre&gt;
Copy L/exfat-handler L:

DOSDriver or Mountlist entry for an exFAT partition make sure that the FileSystem and Handler are set as follows:

FileSystem     = exfat-handler
DosType        = 0x46415458
&lt;/pre&gt;

&lt;pre&gt;
Copy L/ntfs3g-handler L:

DOSDriver or Mountlist entry for an NTFS partition make sure that the FileSystem and Handler are set as follows:

FileSystem     = ntfs3g-handler
DosType        = 0x4e544653

Also to make a read-only mount you can set:

Control        = ro
&lt;/pre&gt;


The Smart File System (SFS) is a journaling filesystem used on Amiga computers and AmigaOS-derived operating systems. It is designed for performance, scalability and integrity, offering improvements over standard Amiga filesystems as well as some special or unique features.  

SFS is written in C and was originally created and released as freeware in 1998 by John Hendrikx. After the original author left the Amiga scene in 2000, the source code to SFS was released and its development continued by Ralph Schmidt in MorphOS. 

Its development has now forked; as well as the original Amiga version, there are now versions for MorphOS, AROS, AmigaOS 3, and a version for AmigaOS 4, which have different feature sets but remain compatible to each other.  Versions for AROS, AmigaOS and MorphOS are based on different branches.  

In addition, there is a driver for Linux to read Amiga SFS volumes, GRUB natively supports it and there are free drivers to use it from UEFI.  The Linux version is [http://home.elka.pw.edu.pl/~mszyprow/programy/asfs/ independent code].  

SFS (Smart File System) partially defragments itself while the filesystem is in use. The defragmentation process is almost completely stateless 

AROS SFS version has a 120GB partition size limit on hard disks and DVDs current 4gig size limit. 
The sources for the MorphOS 64-bit version of SFS were available but no porting to AROS has happened so far due to endian issues, etc. 

SFS Tools 
* GUI - arSFSDoctor, 
* CLI - sfscheck , [http://www.portacall.org/ sfsundelete], sfsformat, setcache hits a usability ceiling around the 10GB / 100,000 file mark, 

 sfscheck dh0: seek purge fraglist defragment

If there are two simultaneous file writes in progress and you reboot machine (or it locks up or crashes) you may end up with a corrupted filesystem. Although arSFSDoctor may help, you might have to copy the files to another partition, format the partition with the errors on and copy the files back. 


PFS / SFS are way more advanced and much much faster than the FFS. FFS is supported for legacy reasons only. 
The Professional File System (PFS) is a filesystem originally developed commercially for the Amiga and now distributed on Aminet with a 4-clause BSD license. It is a compatible successor of AmiFileSafe (AFS), with an emphasis on added reliability and speed compared to standard Amiga filesystems.  It also features multi-user abilities like the older MuFS. 

PFS has so many advantages including the important things, speed, the ability to recover all deleted files even simply same name by typing the command &quot;. Deldir&quot; convenient if done in Directory Opus, virtually deleted files are copied normally as if they had never been deleted, other convenience is to not ever invalidate the filesystem, just put it on top of the startup-sequence command &quot;diskvalid&quot;, which automatically corrects any irregularities in the system startup; PFS also provides a device for floppy which makes them very fast and takes advantage of the full capacity of the floppy including the area dedicated to the bootloader.

The device is split into two main areas. At the beginning of the device is the metadata section, which consists of a root block, and a generic array of blocks that can be allocated to store metadata. The rest of the device is another contiguous generic array of blocks that can be allocated to store data. The metadata section usually uses a few percent of the device, depending on the size of the device.

The metadata is stored as a tree of single blocks in the metadata section. The entire directory structure is recorded in the metadata, so the data section purely contains data from files. The metadata describes the location of data in files with extents of blocks, which makes the metadata quite compact.   

When a metadata update occurs, the system looks at the block containing the metadata to be changed, and copies it to a newly allocated block from the metadata section, with the change made, then it recursively changes the metadata in the block that points to that block in the same way. This way, eventually the root block needs to be changed, which causes the atomic metadata update.   

The filesystem is reasonably good at keeping files unfragmented, although there is a defragmentation tool available which will work on an online filesystem ie whilst being used. 

It was the first filesystem to introduce the concept of the Recycle Bin natively at filesystem-level to the Amiga, holding the last few deleted files in a hidden directory on the disk root.  

PFS version 5.3 was developed in C and a small portion of assembly code by Michiel Pelt.  There are endian issues to be overcome and adapting the small amount of m68k to C before use on intel based machines, etc.  


Autoupdate of files in a directory is already implemented in Wanderer, but not all file systems handle dos.library/StartNotify() in its full extent. It seems to work correctly in Ram Disk (thanks to AmberRAM handler), and it also works on SFS formatted devices. Other file systems might not yet have it implemented correctly though. 

The PC equivalent of the Amiga's RDB is the master boot record (MBR).


===Installing Applications===

The typical means to install applications under AROS/AmigaOS involves simply copying/extracting the archive (.zip .lha .rar .tar.gz) file containing the applications files to your own desired location i.e. drawer/folder. Once extracted, launching it by double clicking on an icon (recommended) or using the shell (alternative). Generally, this is on a separate partition from your AROS system files, however in reality it can be any location - including RAM: if you don't want it staying around too long especially when you switch off. 

At some time in the future it may be desirable for AROS to have a package-manager like subsystem able to retrieve information online about packages available for AROS and whether they update anything you currently have installed, however at the moment no such ability exists.


===User Data files===

AmigaOS has no notion of a default location to store user data files, and presently neither does AROS - though it may be desirable at some time to provide a common start location.

Some people, have extra small FAT32 partition(s) using HDToolbox, and not Qparted, to store data especially if a reinstall is ever needed. And then setup the usual Sys: (DH0:) and maybe Work: (DH1:) / Live USB (DU0:) and maybe Briefcase (DU1:) partitions. 


===User Environment configuration files===

AmigaOS/AROS stores persistent system configuration data in directory assigned to ENVARC:.  This, by default, points to SYS:Prefs/EnvArc.

During boot a copy is made to another assign, ENV:, which is for runtime usage.  Changes to the files here will not survive a reboot.

Setting the env variables is generally done by applications themselves, or when necessary by the user using the SetEnv command. SetEnv has a SAVE switch to force the persistent copy in ENVARC: to be written also for when you are sure the change should be permanent.

Under the standard installation of AmigaOS style OSs, ENVARC: is copied to ENV: upon startup, which, if you have a hard drive installation, is in RAM:, hence, ENV: ends up being RAM:Env.

ENVARC: is the Environment Archive, which is the permanent copy of ENV:, which is the Environment.  It's roughly like the Registry in Windoze. 

Most programs do (and all should) store their settings in ENVARC: somewhere, and load them from ENV:.  The effect of this can be seen in the Preference editors.  If you Save your preferences, they go in ENVARC: and ENV:.  If you click Use, they only go in ENV:.  If you reboot, normally, anything saved to ENV: is lost, and is replaced with a copy of what is in ENVARC:.

you can set the default public screen for any tool started from a cli with the PUBSCREEN variable. So open the pubscreen, set PUBSCREEN to the name and start newcli for example, then the new cli window (and all following windows opened from that window) will appear on that public screen.


===Drivers===

For certain hardware, e.g audio, networking and , there is no auto setup. Just like the original Amiga OS. 
For audio, use AHI in the Prefs folder to set Music and at least Unit 0 with the appropriate driver and press Save. For ethernet and wifi, please use SYS:Prefs/Network 

All hardware support is placed in the Devs drawer (folder/directory). The network drivers &lt;something.device&gt; go in the Networks sub-drawer. Audio drivers &lt;something.audio&gt; are put in the AHI sub-drawer. Graphics drivers &lt;something.hidd&gt; are put in the Drivers sub-drawer. 


==Configuring==

AROS has mainly decided on a MUI-like requester&amp;menu clone called Zune so changing the background, icons, font, menus can be done with SYS:Prefs/Zune 

AROS has several desktop GUI front ends like 
* DOpus5 Magellan II, Wanderer and Scalos (medium) 
* AROS Workbench, Workbook (smaller) 

File / Directory managers like Dopus4, MCAmiga, 

App Launch Shortcuts like FKey, BoingIconBar, right mouse click on magellan, wanderer desktop, Amistart, etc. 

General usability decisions - Prefs/IControl, Prefs/Locale, Prefs/Input, Prefs/Fonts, 


Select an icon with left mouse button and then right click the mouse button and selecting Icon -&gt; Information gains access to the tooltypes tab where information can be edited 

CLI in icon's tooltypes means 'run it as if it was run from shell'
If, on the other hand, the WB parameter (or no parameter) is present in Tooltypes, Wanderer will execute the binary and, if provided, the options included in Tooltypes. 

WBxCLI is very useful for adding options to DOS Commands.

Important: AROS has a different way of managing icons. If you have an executable file, you will never be able to add a project icon. AROS will automatically recognise that it is an executable file and will transform the icon into a tool icon.


Icons are typically now .png pictures renamed as .info e.g. so Office application name would have a Office.png renamed as Office.info or MyApp.png as MyApp.info, etc.  

Leave Out menu option to leave app icon on desktop 

To select multiple icons and save their positions, click on the first icon and after while you hold the Shift key down select further icons and don't release it before SnapShot is finished.  You can also select a whole group of icons by pressing the LMB at the top left of the icons and while keeping the LMB down moving the power towards the bottom right. A expanding bounding box will appear and all the icons within it will be selected.  

Clean Up menu option (right mouse button -&gt; Icons) rearranges icons in a drawer or disk window into a neater condition. To use, open the window to rearrange and select Clean Up. To keep the icons in the new positions, select all the icons (shift key or mouse selection) and select 'Snapshot' and then Window and then again with All.  

In DOpus5, Scalos, wanderer, most files have an icon file associated with it. To change the default tool, select Icon menu, Information, and change the default tool string. For example, you could use Multiview, Editor and so on for most text, graphics and some sound files as long as the appropriate Datatype classes are installed. For scripts, set the tool to C:IconX 


We have new Icon edit tools in progress but if you need to...
 C:Join Image1.png Image2.png TO MyFile.info
is enough to make a dual state icon from two png images. You can then use Wanderer's menu Icon/Information on it to edit its fields and tooltypes.

[https://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/icon AISS toolbar images] unpack unarc them into RAM: and copy Images directory to SYS:Prefs/Presets/  AISS icons are looked for in PROGDIR:, PROGDIR:Images, SYS:Prefs/Presets/Images and then in TBImages: according to Open Amiga guidelines.  

there is Demos/iconscale which could be launched from S:User-Startup with two arguments, telling it the horizontal and vertical size. IE something like 
 Demos/iconscale 40 40
It will shrink icons... not sure if it will be very nice though. it doesn't work for the icons on the main desktop. 

there is an option to scale an icon to a bounding box afair, try iconsize followed by two numbers, like:
 iconsize 32 32

Is there any way in AROS to change an icon type from Project to Tool or vice versa?
Either the SIT option of [ ProcessIcon], or the TYPE option of HandleInfo (not sure if this one works at all, please test with care).
 processicon sys:pathoftheicon SIT=Project 

SIT Set type of ICON. Allowed types are: &quot;Disk&quot;, &quot;Drawer&quot;, &quot;Tool&quot;,  &quot;Project&quot;, &quot;Garbage&quot;, &quot;Device&quot;, &quot;Kick&quot; and &quot;AppIcon&quot;.

Btw, are your icons, the #?.info files, writable, is the W flag set ?


'''Decoration''' is Aros' way to provides a way to hide the old Workbench 3.1 style of windows and screens. In Prefs/Appearance some decorative theming elements need work 

Themes - SYS:Prefs -&gt; Appearance 
The default content of Prefs/Env-Archive/SYS/themes.var should be &quot;themes:ice&quot; but can be changed via the Appearance prefs, please do NOT click the Use button. Its useless. As you know, it will ask for the theme volume. Just pick the theme you want, click on Save, then reboot. 

* Decoration is on. Any time trying to change theme, you get: &quot;Please insert volume Theme: in any drive&quot;? 
You could check if you find SYS:System/Themes or if it is missing. Then you could open startup-sequence which you can find in drawer &quot;S&quot;. There should be a line: 
 Assign THEMES: SYS:SYSTEM/THEMES &gt;Nil: 
This does the trick. 
Open a shell and run: 
 Assign THEMES: SYS:SYSTEM/THEMES 
Than start the Theme prefs again... this should work 

* The theme is the only thing that could slow the system a bit, but it's not that performance impacting on most uses, and you can switch it off completely. Remove C:Decoration from the bottom of the file sys:s/startup-sequence. 

In each theme directory is 
*Env-Archive -&gt; Zune -&gt; global.prefs
*images -&gt; Gadgets -&gt; 20x20 pngs for Down etc 
*menu -AmigaKey - Background - Checkmark - SubMenu and config
*system - Arrowdown, Arrowleft, Arrowright, Arrowup, etc 


There is an [https://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/theme ALua/Zulu script] built for faster Wanderer skin management. You can modify config files, install new (wdz format/zipped skin files) and delete skins via the Theme Manager. This has not been updated in a long time and may not work. 


Certain features are added if from Tools/Commodities like Blanker screensaver, ClickToFront and DepthMenu with .info icons are selected and dragged to /WBStartup folder 

Most apps can be autostarted by copying into SYS:WBStartup directory folder 
e.g. WeatherBar.zip can be downloaded, unzip and the contents of the zip copied to wbstartup folder 
 ClicktoFront and .info to SYS:WBStartup so always be activated when turning on the computer 

or add a text line to user-startup is SYS:S (scripts version of wbstartup) 

e.g. standard Amiga / AROS does not allow clicking of background windows to come to the front to make it easy to get to the window you need but it has the ability if these apps are copied again to WBStartUp or are added to SYS:S/user-startup script 

 run QUIET sys:Tools/Commodities/ClickToFront &gt;Nil: 
 run QUIET sys:Tools/Commodities/DepthMenu &gt;Nil: 
 run QUIET sys:Tools/Commodities/Blanker seconds=300 &gt;Nil: 


Exchange controls Commodities and can be opened with alt, ctrl, h 

*AltKeyQ uses left Alt key to add strange letters 
*AutoPoint 
*Blanker screensaver 
*ClickToFront allows windows to be easily brought to the front 
*DepthMenu adds menu to select window easily 
*NoCapsKey
*Opaque 
*FKey - Although there are heaps of docks, menus and other launcher programs on the Amiga like OSs, FKey has got to be one of the quickest once learnt ways to launch programs, and it comes with the OS. In SYS:Tools/Commodities, the FKey commodity (Ctrl Alt F) allows you to make actions assigned to some combinations of keys 

&lt;pre&gt;
ALT TAB       Cycle Windows
              Cycle Screens
              Enlarge Window
              Shrink Window
              Toggle Window Size
              Insert Text
              Run Program
              Run Arexx Script
&lt;/pre&gt;

e.g.
&lt;pre&gt;
LAmiga F1               = Avail Flush
LAmiga F2               = Open Prefs
LAmiga F3               = Finder
Alt Tab                 = Cycle Windows
LAmiga Tab or M         = Cycle Screens
Alt Up arrow            = Enlarge Window 
Alt Down arrow          = Shrink Window
Alt Home                = Toggle Window Size 
                        = Insert Text             
LAmiga e                = Run Program             
                        = Run Arexx Script        
&lt;/pre&gt;

If your FKey GUI pops up when you start your Workbench up and you don't want it to, click once on the icon, go to the Icons-Information in the menu and make sure it has the tooltype set &quot;CX_POPUP=NO&quot;. 

Now let's launch it and assign the locale switching. After you double-click on FKey icon, launch the Exchange, choose the FKey from list and click the Show button. This will invoke the FKey window. You can see the ALT TAB in list assigned to window switching. Now enter the first key combination, say, ALT Z and go to the right panel. Choose Launch the program from pulldown menu and enter SYS:Prefs/Input as an argument. Append the USE switch and english preset name to the string as shown:

SYS:Prefs/Input USE SYS:Prefs/Presets/english

Click on the New Button to add the another combination. Now set the combination for your locale as shown above, replacing English name with your preset name. Click New button again and then Save Settings. Now you can use defined combinations to switch the layouts.


There is a system wide ARexx script capability (based on regina) that can manage many file manipulation task(s) but this would work only with those program that support [https://en.wikibooks.org/wiki/Aros/Developer/Docs/Rexx ARexx] like 

*Desktop - DOpus5, Scalos 
*Dock - FKey, 
*Files - Multiview, DOpus4, 
*Internet Apps - Odyssey, WookieChat, 
*General Apps - 


the shell can be modified with escape strings but not needed in most cases 


 Common Keyboard Shortcuts

&lt;pre&gt;
RAlt Right Alt Key 
LAlt Left Alt Key 
RWinKey Right Windows Key 
LWinKey Left Windows Key 
RAmiga Right Amiga Key (if one)
LAmiga Left Amiga Key (if one)
&lt;/pre&gt;

;Bootup Options 
:Spacebar during boot, enters the bootmenu which allows a boot without startup sequence, etc  

;Left Click 
:LAmiga = LWinKey = F11 

;Right Click 
:RAmiga = Help = F12 

;Mark 
:RAmiga and B 

;Cut 
:RAmiga and X 

;Copy 
:RAmiga and C 

;Paste 
:RAmiga and V 

;Search 
:RAmiga and S 

;Mouse Movement 
LAmiga and together with arrow keys - shift as well at the same time as well to move faster 

;Mouse Selection 
LAmiga and LAlt to select 

;Screen Switching 
LAmiga and M or N 

;HELP key 
Can sometimes be mapped to F11 but can be changed via FKey 


ComKeyRemapper or AmigaKeyremapper could swap RAmiga to another key press 


===DOpus 5 Directory Opus Magellan II===

Dopus 5.x is a whole desktop replacement on the Amiga Workbench (Desktop) 

DirectoryOpus app will assign DOpus5: to it's PROGDIR: automatically but if not add the below (edit SYS:System to suit where Dopus5 was installed) to your startup-sequence 

&lt;pre&gt;
Assign DOpus5: SYS:System/DOpus5 
DOpus5:DirectoryOpus 
;DOpus5:C/LoadDB
&lt;/pre&gt;

Left mouse button clicked twice on the desktop background brings up the Device List window. 
Green strip notifies SRCE (source) and if another is open it will be red for DEST (destination). clicking on the red strip changes to green 

Word list of actions with a left mouse click on the DOWN Arrow and directory stuff with &lt; button which mirrors the icons at the top of each lister 

single-key hotkeys? exactly the same as in dopus4, edit your functions (button bank, toolbar, menus etc.) and under the flags gadget is a key gadget, just click in it and press the key you want to use.

As for the extra text field... try turning off Extended lister key selection in environment / miscellaneous.

Shift and click on the icon - runs the icon 


DOpus5 Magellan 2 Directory folder drawer structure 
&lt;pre&gt;
ARexx       - Arexx scripts .rexx and .dopus5 to perform tasks 
Buttons     - 
Commands    - 
Desktop     - 
Environment - two environment files bundled:
 default gets loaded if you run DOpus as a normal app
 workbench gets loaded if you run DOpus as a WB Replacement (with LoadDB on startup)
Filetypes   - 
Groups      - 
Icons       - 
Images      - 
Modules     - compiled tasks 
Settings    - 
Sounds      - 
Themes      - 
WBStartup   - Use this if standard SYS:WBStartup gives cannot wait error messages 
&lt;/pre&gt;


Settings -&gt; Environment -&gt; Display -&gt; Workbench (Use) 


*Settings -&gt; Clock (add to title bar as well as the date) 

*Toolbar  -&gt; Editor (Right Win Key together with 1) for Copy, Move, Delete, etc above the Device List 
*Menu     -&gt;  (Right Win Key together with 2) 
*Buttons  -&gt; Editor (Right Win Key together with 3) 

*Settings         -&gt; Environment (Right Win key together with 4) for Backgrounds, etc 
*File Types       -&gt;  (Right Win key together with 5)
*User Menus       -&gt;  (Right Win key together with 6)
*Hotkeys          -&gt; Setup for quick shortcut keypresses (Right Win Key together with 7) 
*Scripts          -&gt;  (Right Win key together with 8)
*Icon Positioning -&gt;   (Right Win key together with 9)


Each Dopus5 theme are stored in a separate directory, named appropriately, which contains further sub directories 

* Font (amiga bitmap fonts)
* Screens (jpg or any picture supported by datatypes but not animations) 
* Sounds (wav but not iff 8svx ) 
* Icons (png newicons glowicons ) 
* Patterns (iff jpg png ) 


Just use wildcards in background filenames and you get a different picture every reboot 

For example, configure in Environment -&gt; Backgrounds -&gt; Desktop something like this:
&lt;pre&gt;
Work:Pictures/Backgrounds/#?
...or 
Work:Pictures/back#?.iff
...etc...
&lt;/pre&gt;


[https://aminet.net/util/dopus arcdir and themes]  


If you want to change the backdrop pic after a period of time, paste below into a text file called dopusrandbg.rexx and place in DOPus5:ARexx 

&lt;pre&gt;
/* Changes DOpus background image forever

   Start with:
   Run &gt;NIL: RX dopusrandbg.rexx 
*/

if ~show(&quot;L&quot;, &quot;rexxsupport.library&quot;) then do
	if ~addlib(&quot;rexxsupport.library&quot;, 0, -30,0) then exit 10
end

/* Configure these two lines for your needs: */
minutes=1
picpath=&quot;Work:Pics/#?.iff&quot;

address DOPUS.1

do forever
	call delay 3000*minutes
	dopus set background '&quot;'picpath'&quot;' desktop center custom
	dopus refresh background custom
end
&lt;/pre&gt;


If you don't want to use/open rexxsupport.library just for DELAY() then use the DOS Wait command

&lt;pre&gt;
/* random diropus backdrop changer */
/* by paul trauth, 1999 */
/* to do: non-repeatable randomness? */

options results

parse arg path

address DOPUS.1

/* get current backdrop pattern so it actually changes */

dopus query background desktop custom
currentpatt=result
lastslash=lastpos('/',currentpatt)
currentpatt=substr(currentpatt,lastslash+1,(pos('&quot;',currentpatt,2)-lastslash-1))

dir=showdir(path,'FILE','/')
num=0
do while dir~=''
    where=pos('/',dir)
    if where&gt;0 then do
        file=left(dir,where-1)
        dir=right(dir,length(dir)-where)
    end
    else do
        file=dir
        dir=''
    end

    if left(file,1) ~='.' &amp; file~=currentpatt then
        do
            pics.num=file
            num=num+1
        end
end

which=random(0,num-1,time(s))
newbg='&quot;'||path||'/'||pics.which||'&quot;'

dopus set background newbg desktop tile precision exact
dopus set background on
dopus refresh background
&lt;/pre&gt;


Clock format commands available are defined by locale. They are:
&lt;pre&gt;
 %a - abbreviated weekday name
 %A - weekday name
 %b - abbreviated month name
 %B - month name
 %c - same as &quot;%a %b %d %H:%M:%S %Y&quot;
 %d - day number with leading 0s
 %D - same as &quot;%m/%d/%y&quot;
 %e - day number with leading spaces
 %h - abbreviated month name
 %H - hour using 24-hour style with leading 0s
 %I - hour using 12-hour style with leading 0s
 %j - julian date
 %m - month number with leading 0s
 %M - the number of minutes with leading 0s
 %p - AM or PM strings
 %q - hour using 24-hour style
 %Q - hour using 12-hour style
 %r - same as &quot;%I:%M:%S %p&quot;
 %R - same as &quot;%H:%M&quot;
 %S - number of seconds with leadings 0s
 %T - same as &quot;%H:%M:%S&quot;
 %U - week number, taking Sunday as first day of week
 %w - weekday number
 %W - week number, taking Monday as first day of week
 %x - same as &quot;%m/%d/%y&quot;
 %X - same as &quot;%H:%M:%S&quot;
 %y - year using two digits with leading 0s
 %Y - year using four digits with leading 0s
&lt;/pre&gt;
like %a %d-%b-%y %H:%M or 


A WB ARexx interface, you could enter a cli command as a menu item to open a WB drawer like this...
 RX &quot;address WORKBENCH;WINDOW 'device:drawer' OPEN&quot;
Where device:drawer is replaced by the path of the drawer to open. 

The ARexx script would be capable to manage such a task but this would work only with those program that support ARexx 

&lt;pre&gt;
dopus addappicon
dopus addtrap
dopus back
dopus checkdesktop
dopus clear
dopus command
dopus desktoppopup
dopus error
dopus front
dopus getdesktop
dopus getfiletype
dopus getstring
dopus matchdesktop
dopus progress
dopus query background, font, palette, pens
dopus read
dopus refresh all, background, icons, lister
dopus remappicon
dopus remtrap
dopus request
dopus script
dopus screen
dopus send
dopus set background, font, palette, pens
dopus setappicon
dopus version
&lt;/pre&gt;

&lt;pre&gt;
lister add
lister addstem
lister copy
lister clear value
lister clearcaches
lister close
lister empty
lister findcache
lister getstring
lister iconify
lister new
lister query active all, dest source
lister query abort, busy, case, dirs, display, entries, entry, files, flags, handler, header, hide 
lister query label, lock, mode, namelength, numdirs, numentries, numfiles, numseldirs, numselfiles
lister query path, proc, position, seldirs, selentries, selfiles, separate, show, sort, 
lister query title, toolbar, value, visible, window
lister read
lister refresh
lister reload
lister remove
lister request
lister set busy, case, dest, display, field, flags, handler, header, hide, label, lock, mode
lister set namelength, newprogress, off, path, position, progress, separate, show, sort, source
lister set title, toolbar, value, variable
lister select
lister wait
&lt;/pre&gt;

The '''command''' allows you to call internal DOpus commands from an ARexx script

&lt;pre&gt;
command all
command wait copy
command read s:startup-sequence
command source 12345 makedir name noicon
&lt;/pre&gt;


*SFTP secure encrypted comms over internet using libssh2 and zlib (different protocol to the two below) on port 22 
*FTPS secured with https like security on port 21 
*FTP not secure and unencrypted protocol over internet on port 21 (should not be used today on the internet but for your own server) 


===Wanderer ===


Wanderer prefs in the prefs drawer - Appearance tab and Workbench icon allows backgrounds (wallpapers) icon text sizes, colors, etc but cannot use #? or *.* in the backgrounds file entry to randomly choose pictures - [https://developers.google.com/speed/webp/docs/riff_container webp riff container] issues with this format but Multiview has none. 

Enable the bar, you need to edit the text file ‘statusbar.prefs’. The change is simple: just change “False” to ‘True’.

Prefs/Env-Archive/SYS/Wanderer/statusbar.prefs 


===Scalos===

[https://web.archive.org/web/20180922220139/http://scalos.noname.fr/ Scalos] is not an OS replacement, it's a Workbench replacement. It replaces the desktop and graphical file management components. 

Scalos is 100% Workbench replacement with most functions working like the original Workbench ones. Undo and Redo available for most window and icon operations. Fully multitasking so every window has its own task. While loading icons, any window function (e.g. Drag&amp;Drop) is available. 

24bit color support with window patterns - Unlimited and easily configurable via tooltypes. Optimised backgroundpatterns routine so patterns can be tiled, centred or even scaled to fit into the windows. Live updating window scrolling - Supports middle mouse button panning and drawer (folder) windows can be iconified on the desktop. 

Icon imagetypes with all types are supported such as backfill or complement. Configurable surrounding iconborder. Icon support also visually highlights files which are soft-links in the file system. Icon dragging is more stable and far less flickery on graphics cards. Whilst dragging, icons are displayed with text and they can become transparent over anything where they can be dropped. 

Single-window lasso mode, with scrolling window contents invoked by dragging mouse with configurable qualifier key. Text icon lasso selection used to ignore &quot;Name column selects text icons&quot; flag. Support for backfilled thumbnail icons, with selectable color and transparency. Added option to always generate square thumbnail icons with preview icons for images - Thumbnails can be permanently saved in icons. 

Supports PNG icons with alpha channel and real transparency and displays OS3.5 GlowIcons and are all scalable. Iconborders with variations (normal, shadowed, outlined). 

Completely configurable, filetype-specific user-definable popup menus and tooltips. Plugin system to exchange or add features and can enhance the Workbench and make it more configurable. 

Filetype plugins to display filetype-specific information. - Currently, EXIF information viewer for JPEG images is included. Plugin included for 100% support of OS3.9 Workbench features. Plugin included for AREXX API compatible to OS3.9 Workbench. 

Online update with updater.module


Scalos works also as a Workbench replacement. In this case the 'emulation mode' has to be set by using Scalos' own version of LoadWB and offers 
* Scalos uses the Workbench Screen for its windows instead opening a new one 
* AppIcon, AppMenuItem, AppWindow functions are redirected to Scalos
* all Programs placed in &quot;WBStartup&quot; should start 
* The Screen will be reopened in case of changes in ScreenMode and Palette settings


&lt;pre&gt;
v1.0 (V39.201) - November 1999
v1.1 (V39.212) - December 1999
v1.2b (39.220) - June 6, 2000
v1.2d (39.222) - 2000 (latest public beta executable)
v1.3 (40.7) (beta) - August 2, 2001
v1.3 (40.22) - September 25, 2002
v1.4 (40.32) (beta) March 31, 2005
v1.6 (41.4) - March 27, 2007
v1.7 (41.5) - August 12, 2007
v1.8 (41.6) - March 12, 2009
v1.9 (41.7) (beta) - March 15, 2010
v1.9 (41.8) (RC1) - August 25, 2012 open source 
v1.9.2 (41.10) Deadwoods' AROS late 2022 32bit and 64bit build unifying the code base of ` for AROS x86 ABIv0, AROS x86_64 ABIv11 and AROS m68k  
&lt;/pre&gt;


Distros may have Scalos files under SYS:System/Scalos or Extras:Scalos. Known [https://github.com/deadwood2/AROS/issues/75 bug list], 


 Certain files like Menu13.prefs, Palette13.prefs, Pattern.prefs and scalos.prefs need to be in SYS:Prefs/Env-Archive/Scalos they can be found in Scalos:Storage/envarc and country drawer 

or run the &quot;Scalos Menu&quot; preferences program. Note if already setup with sub-menu entries and then re-save your menu prefs as it will now generate a new/overwrite prefs file called &quot;Menu13.prefs&quot; in &quot;envarc:scalos/&quot;. The same is also required for the new Palette prefs update, click 'Save' and a &quot;Palette13.prefs&quot; file will be saved in to &quot;envarc:scalos/&quot; directory. 


&lt;pre&gt;
ASSIGN Scalos:             SYS:xxx/xxx DEFER   
ASSIGN Libs:               Scalos:Libs add    
;ASSIGN SYS:Devs/Datatypes  Scalos:Devs/Datatypes   add  
Assign Theme:              Scalos:Themes/Default_Theme add 
Assign Locale:             Scalos:Locale add 

Protect Scalos:Tools/browse.script s add quiet 
Protect Scalos:Tools/OpenShell s add quiet 
Protect Scalos:Tools/run.script s add quiet 

run Scalos:Tools/LoadWB 
;Scalos:Scalos
&lt;/pre&gt;

Add the above to SYS:S/startup-sequence or SYS:S/user-startup '''before any Wanderer entries''' 


In the prefs drawer (folder) is the big prefs app Scalos_Prefs which covers these user setup areas 
&lt;pre&gt;
About Scalos
Paths               - should be preset 
Startup             - WBStartup drawer contents should auto run on each startup 
Desktop             - edit titlebar, icon layout and in misc, auto leave-out (drag icon to desktop) 
Icons               - 
Drag and Drop       - 
Windows             -
Text Windows        -   in misc, drawer sorting at start of listing if needed 
TrueType Fonts      - use Truetype fonts rather than system ones 
Miscellaneous       - 

Plugins             - after adding oop/title_clock.plugin %ti %da does not work, maybe needs ASCII .prefs added 
Modules             - ??
Menu                - setup for MainMenu and PopupsMenu with New Menu, RE Name, Key: shortcut, Command Properties 
FileTypes           - already added def_Project icons and def_Disk (hdd sdd cd dvd etc) support 
PopupMenu           - tweak how popups appear 
Pattern             - Wallpaper backgrounds with Type DE, each pattern in the list can be edited, Save as Pattern.pre 
Palette             - change the color of things , Save as Palette.pre 
&lt;/pre&gt;


Scalos_Prefs - Pattern - Minimum options to be changed are 
*DE Desktop/Background 
*SC Screen 
*TW Window/TextBackground ie Text listing showing if icon type not recognised 
*IW Window/Background ie Icons showing 

 Workflow - In &quot;Pattern List&quot; tab, select New - choose a picture, highlight in list, click in number box under New button and slide to another number, click on &quot;Defaults&quot; tab and adjust Pattern numbers slider to choose right picture for each of the above options - Click &quot;Pattern List&quot; tab to check eveything is OK and click Save 

Pattern List tab on Patterns Page - Allows you to compile a list of pictures (one at a time rather than a whole folder e.g. with #? or *.*), assigning a number Nr to one or more of them for easy reference. Using this number you will be able to assign the pictures to specific windows on the Defaults tab Page. If multiple pictures have the same number, one of the pictures will be chosen randomly. This will allow you to have random desktop pictures, random window backdrops etc. 

Defaults tab on Patterns Page - Here you can set the defaults for the background pictures for the Desktop, Screen, Window and/or Text Mode throughout Scalos. 
Randomize every time [check box] - Usually Pictures with the same number will be randomly selected as soon as the configuration loads. If this option is set, the picture will be selected as soon as a window with the same number assignment is opened. 

*Fit size: The picture will be resized to the dimension of the new window.You *MUST* have set GUIGfx on. asyncron layout: Pictures will be loaded and rendered while the windows opens (Like original Workbench). If this function is 'off', pictures will always be loaded before opening the windows. 
*Use friendbitmap : The picture is present twice in memory for best speed. This option has no effect if V43 picture.datatype or GUIGfx are used. Always relayout: If &quot;Fit size&quot; is set, the picture will be scaled everytime the window's dimensions change.
*Randomize everytime: Usually Pictures with the same number will be randomly selected as soon as the If more pictures have the same number, one of them will be chosen randomly. 

Patternlist New/Delete : Add a new picture. After that you should assign a number to it. The picture will be rendered as tiles. configuration loads. If this option is set, the picture

Asyncron-Task priority: You can set the CPU priority for the Task if &quot;asyncron layout&quot; is set. 
&lt;pre&gt;
Desktop: Number of the Picture for the main window.
Screen: Number of the picture for the Scalos-Screen.
Window: Number of the picture for the Scalos-windows.
TextMode: Number of the picture for the Scalos-windows in Text Mode.
&lt;/pre&gt;


Popup Menu preferences fully configurable menus (includes ToolsDaemon and ParM launch apps import), including support for context-sensitive Popup menus configs for top pull down menus for apps, etc. 

 Workflow - Scalos_Prefs then Menu, New Item, New Command add name at top then in Command Properties e.g. add Workbench and location e.g. DOpus:DOpus4 for apps  Command for c apps or Rexx for scripts or Plugin for  or AmigaDos for modules 

&lt;pre&gt;
DESCRIPTION	NAME/A      This is the title that is displayed in the top line of any popup menu  
INCLUDE NAME/A          Name of file to be included. Path can be relative to &quot;Scalos:FileTypes&quot; 

POPUPMENU      Starts the popup menu description section for this filetype.
&lt;/pre&gt;

The following Subcommands are allowed inside popup menus:
&lt;pre&gt;
SUBMENU &quot;NAME/A&quot;
ENDSUBMENU 


MENUENTRY &quot;NAME/A,KEY/K,DEFAULTACTION/S&quot;
ENDMENUENTRY 

INTERNALCMD	&quot;NAME/A&quot;
WBCMD &quot;NAME/A,STACK/K/N,WBARGS/S,PRI=PRIORITY/K/N&quot;
AREXXCMD &quot;NAME/A,STACK/K/N,WBARGS/S,P=PRIORITY/K/N&quot;
CLICMD &quot;NAME/A,STACK/K/N,WBARGS/S,P=PRIORITY/K/N&quot;

ICONWINDOWCMD &quot;NAME/A&quot;

PLUGINCMD
MENUSEPARATOR

ENDPOPUPMENU

TOOLTIP 
ENDTOOLTIP
&lt;/pre&gt;

&lt;pre&gt;
Starts the tooltip description section for this filetype. The following Subcommands are allowed inside popup menus:

GROUP &quot;ORIENTATION/K&quot;
ENDGROUP  
MEMBER &quot;HIDE/K&quot;
ENDMEMBER  

HBAR 
STRING &quot;ID/K,TEXT/K,SRC/K,TEXTPEN/K,HALIGN/K,STYLE/K,FONT/K,VALIGN/K&quot;
SPACE &quot;SIZE/N/A&quot;

DTIMAGE &quot;FILENAME/A&quot;
&lt;/pre&gt;


Each theme drawer (folder) has these further folders 
&lt;pre&gt;
About            - 
Desktop          - 
FileTrans        - 
FileType         - 
Icons            - 
Menu             - 
Modules          - 
PointerIcons     - 
Prefs            - 
Sound            - 
Window           - 
&lt;/pre&gt;


*Plugins
&lt;pre&gt;
devicefilter.plugin       
persist.plugin            should a crash or reboot occur - next time Scalos started, all windows re-opened 
title_clock.plugin        add digital clock to title see more below 
title_envvar.plugin       %ev, which can be used to display the value (a string) of the variable in the titlebar 
title_freepens.plugin     
volumegauge.plugin        
wb39.plugin               
wbrexx.plugin             plugin adds a Workbench 3.5+ compatible AREXX interface to Scalos internals 
xtwindows.plugin          left or right ALT or left or right SHIFT keys when open/close windows 
filetype.plugin           then run FileTypes-prefs and customize the filetypes (eg import from a DefIcons-brainfile) 
menu.plugin               
&lt;/pre&gt;


*Modules - delete, empty_trashcan, execute, find, format_disk, information, iconproperties, newdrawer, reboot, rename, systeminfo, windowproperties 


*Tools - scripts like LoadWB, quit.rexx, open_volume.rexx, 


In Scalos_Prefs-&gt;Filetype-&gt;Recognition  you can define the filetypes and on &quot;Action&quot; you define specific context menu for all filetypes defined in recognition (similar to magellan)
there is the same you must show all first (list is only limited) so you created a file type AAABBB, you need to have def_AAABBB icon 

Associating files with &quot;Scalos_FileTypes&quot; is very simple, practically it is very similar to Dopus4, first you create the Def_icons to assign to the file type (will be seen automatically ), then run &quot;Scalos_FileTypes&quot; you add the extension, fill in the descriptor (MATCH or PATTERN etc..) and save 

then you create an appropriate entry in the list and rename it, if def icon exists it is shown. Below you can define how files are identified. Use &quot;pattern&quot;, similar to magellan to identify file by ending. Then you click on the shown icon and define in it what program is used when you double-klick on it and save it. On the tab action you can define popup menu for it. 

defined all archive types from XAD in &quot;filetypes&quot;. If you change to &quot;action&quot; and click on &quot;archive&quot; you can define the context menu that is shown if you do not define a specific context menu for a filetype


Reset to Default in Scalos_Prefs resets all settings so '''BEWARE''' 


&lt;pre&gt;
The Scalos desktop screen titlebar may be configured using the main Scalos Preference program. This oop/time_clock plugin adds some additional placeholders:

    %ti, displays the current time in the default Locale format. e.g. &quot;10:43:37&quot;
    %da, displays the date in the default Locale format. e.g. &quot;Saturday 14 July 2001&quot;

Using the supplied prefs program for the plugin, or editing the ASCII file ENVARC:Scalos/title_clock.prefs you can use the following standard Amiga Locale values to change the formatting 

    %a - abbreviated weekday name
    %A - weekday name
    %b - abbreviated month name
    %B - month name
    %c - same as &quot;%a %b %d %H:%M:%S %Y&quot;
    %C - same as &quot;%a %b %e %T %Z %Y&quot;
    %d - day number with leading 0s
    %D - same as &quot;%m/%d/%y&quot;
    %e - day number with leading spaces
    %h - abbreviated month name
    %H - hour using 24-hour style with leading 0s
    %I - hour using 12-hour style with leading 0s
    %j - julian date
    %m - month number with leading 0s
    %M - the number of minutes with leading 0s
    %n - insert a linefeed
    %p - AM or PM strings
    %q - hour using 24-hour style
    %Q - hour using 12-hour style
    %r - same as &quot;%I:%M:%S %p&quot;
    %R - same as &quot;%H:%M&quot;
    %S - number of seconds with leadings 0s
    %t - insert a tab character
    %T - same as &quot;%H:%M:%S&quot;
    %U - week number, taking Sunday as first day of week
    %w - weekday number
    %W - week number, taking Monday as first day of week
    %x - same as &quot;%m/%d/%y&quot;
    %X - same as &quot;%H:%M:%S&quot;
    %y - year using two digits with leading 0s
    %Y - year using four digits with leading 0s

 like %d %m %y or %a %d %B %Y %p
&lt;/pre&gt;


Shutdown -&gt; right mouse button Scalos, About, Reboot, Shutdown 


ToolTypes can be added to the Scalos.info icon like 
*SCALOS_PATTERNNO=&lt;number&gt; : background image matching the number 
*SCALOS_NOTEXT : The Icon will be drawn without Text.
*SCALOS_NODRAG : The Icon will not be draggable. Its position will be fixed.
*Module iconproperties - Added SCALOS_BROWSERMODE tooltype support

runcommand parameters... in which case:
&lt;pre&gt;
%p = parameters
%w = directory path
%d = device-name
%% = literal percentage token
&lt;/pre&gt;


With the help of the wbrexx.plugin Scalos gains support for more of the compatible arexx API 

If an arexx command produces an error you will find the error code placed in the WORKBENCH.LASTERROR variable.

ACTIVATEWINDOW
&lt;pre&gt;
/* Activate the root window */
ADDRESS workbench
ACTIVATEWINDOW root

/* Activate the &quot;Work:&quot; partition's window if already open*/
ACTIVATEWINDOW &quot;Work:&quot;
&lt;/pre&gt;

CHANGEWINDOW
&lt;pre&gt;
/* Change the root window; move it to position 10,30. * and change its size to 200100 pixels */
ADDRESS workbench
CHANGEWINDOW root LEFTEDGE 10 TOPEDGE 30 WIDTH 200 HEIGHT 100

/* Change the currently active window */
CHANGEWINDOW active 20 40 200 100
&lt;/pre&gt;


Most of Scalos' issue are due to the flexibility of its' user configuring nature but if 


The sort menu plugin needs to be ported from ASM to C.

IIRC Scalos has a command line option to fully replace Workbench/Wanderer.

The Theme: assign is used by both Wanderer and Scalos but I didn't have any problems using both at the same time.


The Program will be started from the Shell.
If &quot;WB Args&quot; is set, with the Argument &quot;%p&quot; will be replaced by the path of the activated Icons. The Program will started with the specified Stack value.
IconWindow: Scalos opens the window of the specified path.


PlugIn: Starts a Scalos Menu-PlugIn.
If a Menu Item with empty name is specified, Scalos displays a separator line.
It's possible to Drag&amp;Drop an Icon in the Configuration Window. All values will be set accordingly. Entries may be dragged across the list.


Mac-like selection : This function activates a multiselection method used on MacOS or Win95. Don't have to hold down shift to drag them. Clicking on an already activated icon will
not deselect all other icons. 

MMB move: The window contents may be moved using the middle mouse button. 

WindowPopup title only: PopupMenu for windows can be opened only on window's title bars. 

FullBench: Screen-Titles removed and Main Window set Full Size. 
Scalos Prefs. Go to Settings-&gt;Scalos-&gt;Prefs and then the Misc section. Remove the tick against Full Bench. If you've enabled it, the titlebar will disappear when you select backdrop.


Default Icons saveable : The icons which Scalos generates if &quot;show all files&quot; is enabled, can now be saved
using &quot;snapshot&quot; menu option. load DefDisk first : Try to read the icons first from the DefIcons Path before using disk info. 


Hide hidden files : If this function is activated all files or directories where the &quot;hide&quot; flag is set will not be shown.

Many of my Icons display more than once on the screen, while on the workbench all seems ok.
The Workbench filters double displayed icons, Scalos does not. Solution: please edit the &quot;.backdrop&quot; file and clear double lines.

Background images not scaled. GUIGfx option not set or guigfx.library and/or render.library not installed.

If working with CD's causes crashs or Scalos doesn't work correctly.
Most Filesystems doesn't support the ExAll function correctly. Disable &quot;Use ExAll&quot; in Scalos prefs.

Scalos doesn't start any program in the WBStartup. WBStartup Path may be set wrongly or Scalos was not started in Emulation Mode (LoadWB etc) 
Some programs will not startup with error message &quot;has not returned, wait some more&quot;? and &quot;unable to open your tool&quot; 


need a def_icon with the same name predefined, then create an appropriate entry in the list and rename it, if def icon exists it is shown. Below this can define how files are identified. 
* either &quot;pattern&quot;, similar to magellan to identify file by ending
* or 
Then click on the shown icon and define in it what program is used when you double-click on it and save it. On the tab action you can define popup menu for it. All in all handling is of course different to magellan but can do similar 

For the RAM Icon, to obtain this you have only to copy the icon in the Icon Path as &quot;RAM.info&quot; or &quot;Ram Disk.info&quot;. All functions will automatically be performed 

sometimes cut into half or quarters when scrolled off screen or drawers moved - settings issue probably  

Sometimes leaves initial drawer window imprint on desktop when moved - settings issue 


Scalos AROS released a [https://github.com/deadwood2/contrib/tree/master/scalos new build V2022-07-21] with the following changes noted:
&lt;pre&gt;
Fixed:
    Numerous crashes when working on 64-bit with 64-bit heap
    Wrong background color of Scalos logo on Scalos splash window
    Backgroung image of Scalos splash window and Scalos About window is not visible
    Icon labels on desktop and in drawer windows are displayed using Topaz instead of Arial font
    Font.prefs are not being loaded on 64-bit
    Font.prefs are being wrongly saved on 64-bit
    scalos.prefs are not being loaded on x86 and x86_64, scalos is using always default preference
    scalos.prefs are being saved on x86 and x86_64 in format not compatible with m68k 
    NewPopupmenu.prefs is wrongly written
    Plugins are not loading at Scalos startup
    wbrexx.plugin is crashing at startup on 64-bit
    Multiple controls missing on Scalos Prefs/Icons page
    System crash when clicking on def icon image on FileTypes Prefs/Recognition page
    Status bar, control bar, buttons sometimes don't have images displayed
    Buttons in Scalos About window have white corners rendered where they should be transparent
    Crash when leaving out an icon
    Crash when adding a User-defined Button to Control bar without setting it's properties in Scalos Prefs
    Crash when removing any button from Control bar in Scalos Prefs
    Scalos Prefs allows editing TTEngine font properties when TTEngine is not present causing crash in Icons/Labels and Text Windows/Fonts pages
    deficons.prefs are not being loaded on x86 and x86_64
    Reset to default in FileType Prefs and Save does not save preferences

Won't fix:
    Scrollbars visible on titles of TrueType Fonts, PopupMenu, Menu, FileTypes, Pallette and Pattern pages of Scalos Preferences

Not fixed:
    Wrong rendering on DualPNG icons 
    Refreshing drawer windows is slow 
    Starting Prefs/Locale or Prefs/Input from Scalos causes other preferences to fail 
    Desktop wallpaper is damaged where Splay window was displayed 
    When started from Wanderer, after saving Scalos Prefs, reload does not re-open main Scalos window
    Difference in behavior between Cleanup from popup menu and Cleanup from top menu - possibly due to missing plugin, check Cleanup association in Menu Prefs
&lt;/pre&gt;


===DOpus 4 Directory Opus===

Copy DOpus4 app to WBStartup directory folder so it starts on boot up each time 

Another method is add the below to the bottom of the user-startup script in SYS:S drawer/directory 
&lt;pre&gt;
run DOPUS:DirectoryOpus -i &gt;NIL
&lt;/pre&gt;
makes DOpus starts up in Iconified state at the top of Wanderer's screen. Left click on this to highlight and right mouse click to open. 


Just click on the sides of either outer edges of DOpus windows and it will display the parent device/volume list. 


DOpus4 saves it features in a PROGDIR:s/DirectoryOpus.CFG file which can be edited to suit anyones' needs, '''C''' bottom right button in DOpus4 and by reading the [https://arosarchives.os4depot.net/index.php?function=browse&amp;cat=utility/filetool Dopus4 guide Manual and Arexx calls].

*[https://www.youtube.com/watch?v=DCyXDs8baSE Pt1 Introduction] 
*[https://www.youtube.com/watch?v=7fiVmopiK9I Pt2 Dopus Config] 
*[] 
*[] 


*Button little rectangle with name inside
*Bank vertical stack of buttons 

 Buttons 
*Workbench app {f} i.e. first  use {F} for all selected items with app 
*AmigaDos  c type apps with arguments after 
*Arexx     
*Command   c type apps with no arguments after 

 Flags (most used)
*CD Destination to extract etc 
*Do all files
*Output window 
*Run asynchronously
*Workbench to front

*Buffer above 100000 for 64bit 


 Filetypes
Defines how certain files are handled like '''default tool''' 


 Screen
Fonts, set each element to any font 
Screenmode, Workbench Use (same screen like Windows), Workbench clone (like Linux workspaces) 

 System 
Shell startup, set to SYS:s/shell-startup 


===BoingIconBar===

User chooses the apps to add to the dock at the centre bottom of the screen but has to be done manually, please use Save afterwards 

Or easier edit the text file of SYS:Prefs/Env-Archive/iconbar.prefs and save 

&lt;pre&gt;
SYS:System/Shell 
SYS:Tools/DOpus4/DOpus4
SYS:Utilities/Editor
SYS:System/SysMon
SYS:System/Scout
Work:Extras/Internet/OWB/OWB
Work:Extras/Graphics/Lunapaint
Work:Extras/Graphics/ZunePaint
AROS:Tools/MPlayer/MPlayer
Extras:Internet/AmiFox/AmiFox
&lt;/pre&gt;

right mouse click on bottom edge of screen where boingiconbar shows - select settings which opens BoingIconBar Preferences to add apps 

If no dock showing Add, to add apps click Add Program and search for the executable 

another method is to drag icons to ends of the bar and move them on the Bar using the Prefs/BoingIconBar 


===AmiStart===

On 32bit PCs only - auto generates the apps menu but scans the drive each time - AmiStart can choose apps you are not interested 

* how to disable annoying zune/mui 'bubbles'? 
try a right-click on AmiStart and release on Global settings. Then click on the bubbles gadget. Move the Show Bubbles slider all the way to the left.


===Fonts===

Install the #?.ttf files to SYS:Fonts/TrueType. Use SYS:System/FTManager to &quot;Install Font&quot; each #?.ttf file which will generate associated #?.otag and #?.font in SYS:Fonts. Use SYS:Prefs/Fonts to change system fonts and SYS:Prefs/Zune to change others. 

To achieve our goal we will use the Setup Locale, Input, Zune and Fonts, as well as The FTManager.

Begin

The first step you should do is to get the system to know that we speak and write in another language. What you need to do is to open the setup program and choose Locale country, and list &quot;preferred languages&quot; to put it first and then English. If you want the tab &quot;Time Zone&quot; and select city of residence to set the clock correctly. Of course we save our changes and continue opening the setup program Input. This sets the keyboard language as our beginning. When the language layout was created there was no option to switch to Aros keyboard (layout switching), so to write in the language you had to hold down Alt, something you encounter in other functions. This time working with the team of Aros to create a new keyboard layout to replace the old so we can get rid of the button Alt. For now though let only selected this layout and do not turn the switch on the keyboard.


Custom Keyboard Layout

[http://repo.or.cz/w/AROS.git/tree/HEAD:/workbench/devs/keymaps keymaps are in place but unfortunately when they are not, then indeed things become a bit 'low-level' as it involves redefining some tables with values that match your keyboards] 

only need to add your compiled table as new keymap. 

So taking a little peek here shows that it should be possible to compile using
 gcc -opc105_tr pc_105.c -nostdlib
where the pc105_gr/pc_105.c needs to be replaced with your own adjusted keymapname/c-file

[https://en.wikiversity.org/wiki/Enabling_Greek_Characters_on_Your_Keyboard General overview of Greek letters on keyboards] 


Installing fonts

*[http://aminet.net/package/util/wb/EPAGrWb System jaggy] 
*Outline resizable .font .otag 
In this step you need to download some fonts that can support the encoding in our system. The easiest way is to run the script &quot;Download Fonts&quot; you'll find in the folder OWB. This script downloads from the Internet, and unpacks some fonts for OWB web browser, which is placed under the folder Fonts:TrueType. But as these can only be used by OWB and not the system, which unfortunately does not see. To make them available to the rest of the system, open the program FTManager, you will find the folder AROS: System /. From there select the field &quot;Codepage&quot; option &quot;ISO-8859-7&quot; and list the font &quot;Arial&quot; and &quot;Regular&quot; form in which you must double-click with the mouse. In the window that appears, select the bottom right the checkbox &quot;Anti-aliasing&quot; button and then &quot;Install&quot;. Immediately folder Fonts: created files &quot;arialregular.font&quot; and &quot;arialregular.otag&quot;, which are necessary in order to see the system font. Do the same steps if you wish for other fonts.


Final stages 

After completing the above, open the folder AROS: Prefs / and run the program settings Fonts. In the new window, select the fields &quot;Icons&quot; and &quot;Screen&quot; as the font &quot;ArialRegular&quot; to the size you want. In the field &quot;System&quot; to give &quot;s_courier&quot;, which, however, because it is not True Type Font support Antialising, and may seem a little broken. You can also use the CourierNew, if you have installed the above procedure. After you save the changes and open the Zune program settings. In this set the &quot;ArialRegular&quot; font fields in tabs &quot;Windows&quot; and &quot;Groups&quot;, and save the changes. Reboot the system. To make sure that the above worked properly run NoWinED, which you will find under the folder AROS: Tools /. If that everything is working correctly you will see the menu and the settings window with Greek letters. You can also write in the language using the button Alt. Second program that you can try, which is fully localized, is WookieChat, which you will find in the folder AROS: Extras / Networking. And in this place all the menu and settings window works. 


===Windows===

*Intuition
The window you position and resize, you right click on that windows title bar and in the dropdown menu you snapshot from there.  Right click to show menu -&gt; Window -&gt; Snapshot Windows or All but it will NOT work if that folder has no icon (e.g. Disk.nfo) attached to it. You need a folder icon. The window information gets saved in it.  

As for maximising the window using a shortcut key - Alt and up arrow key 

The AROS-Shell windows can be moved, resized by editing sys:s/startup-sequence 

&lt;pre&gt;
; run shell
run QUIET c:newshell &gt;NIL:
&lt;/pre&gt;

; slimmer right aros the screen 
run QUIET c:newshell con:0/150//300/ &gt;NIL:

; top right corner scr-x scr-y win-x win-y
run QUIET c:newshell con:600/150//300/ &gt;NIL:


*EdgeSnap 

Commodity EdgeSnap allows resize and position windows on your screen by dragging them to the edges but not corners of the screen and/or other windows 

EdgeSnap Prefs (once pressed Use button) lets you arrange windows but not different applications in layouts half (left or right) or full size (top) and choose to adjust the border padding 

There is outline to show shape taken to aid placement and space available 


*Zune - AROS version of MUI
Magic Menu type functionality is implemented in IControl preferences editor: in the frame called Menus, switch type from Pull-Down to Pop-Up and/or iControl just tick the sticky menu option. 


Windows outside screens causing a problem either uncheck &quot;Offscreen move&quot; for windows in IControl prefs editor. Or use FKey commodity and define two key shortcuts: 

* the first using the command &quot;cycle windows&quot; (for example ALT TAB); 
* the second using the command &quot;rescue window&quot; (for example ALT F5). 

Now you can cycle windows until the one you want to rescue, and then &quot;rescue&quot; it: it will move back inside your screen. 


How to save the window size on wanderer (snapshot all, snapshot windows)

Same for icon position on wanderer, can't save the position. Icon position cannot be saved yet, but you should be able to save the window position and size. sys:prefs - wanderer icon has option to save window size on exit but just for dh0. To get saving working on (DH1: Extras:) partitions try deleting the dh1 disk.info file, then reboot. The system should create a new dh1 icon. 


* how to set up permanently 'view all files'?
As for viewing all files, removing disk.info for that disk did the job 

* how to list and kill processes (xkill would be useful) ? 
sys:Extras/System/Scout can kill apps 

sys:Tools/Commodities/Exchange can remove available commodities


* how to restore 'go up' button in wanderer window? (it doesn't show up anymore).
If you're using Icaros, go to the theme prefs and make sure that decoration is checked. Also, some themes do not use a parent button, so try another theme. You may have to restart Aros before the theme will change.

* Is it really safe to turn off (hardware button) computer at any time (worried about USB hard disk)
yes you can turn off the computer IF none of the drives are in progress (i.e. writing). Best to use Wanderer menu option Quit otherwise 


===Say narrator===

Say &quot;Hello World&quot; for a simple robotic voice 

SPEAK: is a write-only DOS device for text-to-speech abbreviated as tts. 
To check if available, type assign into the shell and at the bottom in the Devices: section should be SPEAK 

Examples of use 
&lt;pre&gt;
Copy S:Startup-Sequence SPEAK:
Echo &quot;Hello&quot; &gt;SPEAK:M/R/S150/P110
Echo &quot;DH1 EH0 L OW1&quot; &gt;SPEAK:A1
&lt;/pre&gt;

Classic options are M/F, R/N, S&lt;rate&gt;, P&lt;pitch&gt;, O0/O1, A0/A1, and D0/D1. O1 recognizes lines beginning with OPT/ as option changes. A1 treats input as narrator phonemes.

Long options select a speech engine:

Echo &quot;Hello&quot; &gt;SPEAK:ENGINE=narrator/VOICE=female/STYLE=natural/LANGUAGE=en-US

Supported selectors are ENGINE=, VOICE=, STYLE=, and LANGUAGE=. Values are case-sensitive backend identifiers. ENGINE=DEFAULT selects the system default. Narrator-compatible selectors continue through the classic translator/narrator pair. Other engines use speech.device. Direct phonemes require a narrator-compatible selection.


===Printing===

This needs further [http://www.aminet.net/package/docs/help/PrinterGuide drivers written], we have postscript and write to file support only 

;There are no individual drivers yet for HP's Photosmart, EPSON's EPL, CANON's, Lexmark, CUPS PPD, etc. 


*Postscript

Best to set Printer Prefs in the Prefs drawer to print-to-file or parallel/USB port 


Save document in postscript or convert picture/text to postscript 

Print using compatible Postscript printer 


*printer is simply not accepting IPP connections at the moment.

Please try the following steps:

Open the printer web interface in a browser:

 http://192.168.1.x/

Look for the network or protocol settings.

Enable IPP / Internet Printing Protocol.

Make sure TCP port 631 is open/enabled.

Save the settings and reboot the printer if the web interface asks for it.

 ipp://192.168.1.xx:631/ipp/print

 ipp://192.168.1.xxx:631/ipp/


===Files===

====File endings and datatypes====

* Check if the file has his own .info icon file with a tool set to open it. IIRC this has higher priority over the def_XYZ.info file association. 
* In ENVARC:SYS/def_Text.info or whatever def_ file needs changing, use Wanderer's menu Icon -&gt; Information and change the def_XYZ.info there. If you're on ABIv0 and want it to be applied immediately, you might have to copy it to ENV:SYS/ (or to reboot). 
* Identifying file types by file ending is only a fallback. Far better it is to search for magic words, for flac files this would be &quot;flaC&quot; according to this [http://flac.sourceforge.net/documentation_format_overview.html documentation]. 

For instance, to open PDFs with arospdf not localised in the default drawer of Icaros (Work:Extras/Applications/arospdf) but localised in a custom drawer in AROS. The default tools are defined in the icons in sys:prefs/env-archive/sys e.g. def_PDF. 


File type identification is done by datatype descriptors which you can find in Devs/Datatypes. The AROS build system has a tool which creates such datatype descriptors. 


'''Changing of default tools of existing icons is easy as shown above. Adding of new file types is not hard, but needs knowledge of the AROS build system.'''


The enduser way would be to download the attached file, which contained two executables:
1) createdtdesc, to make a new datatype description
2) examinedtdesc, to read/show existing datatype descriptions

use 2 to get an idea on how it things are currently done in aros by providing this executable a file from the drawer sys:devs/datatypes/ (alternatively you can find the original .dtd files here).

use 1 to make your new datatype. Use the accompanied FORMAT file (also here) to read how to make your own datatype descriptor. use 2 to get hints from other datatype descriptors.

Note:
When creating a new descriptor would advise against using the pattern property, but instead use the default pattern of #? and create a Mask that matches your filetype. This requires some research in order to discover how your filetype can be recognized properly. Of course with making something like a descriptor for an ascii textfile, you would fallback to using the pattern (e.g. #?.text as the filetype cannot be determined easily otherwise). 

&lt;pre &gt;
# name - choose wisely and informative. also used for icon's name.
# version - choose as you like as long as it complies with version rules
# basename - the 'root' datatype class. be aware that e.g. it can influence behaviour. for example when choosing binary and using tool multiview in project icon, the file will be viewed as binary file (choosing sound would tell mulitview to view the file as a soundfile). So this can influence the underlying tool being used. Could become messy if users started to modify the tool manually. 
# pattern - This is the file pattern match e.g. #?.text
# Mask - A mask to identify the file. Requires knowledge of the actual file structure. For example 'M' 'Z' for an msdos executable.
# GroupdID - not supported (AROS native) files - use syst as that would be the least intrusive in case an AROS tool/program tries to load such datatyped file.
# ID - In your case, the first four characters of the name at subchapter 1 (in lower case) (or less if name is shorter).
# flags - How the mask needs to be interpreted. In your case would be mostly DTF_BINARY in combination with (wanted or not) DTF_CASE (to tell if mask used letters are case sensitive or not)
# priority - the priority of how the type is handled so that on datatype could have precedence over another? In any case, document tells it to be mostly 0. 
&lt;/pre &gt; 

Now that you know each field and what it does (more or less), you write this fields in a text file for your own invented datatype, save it and create the actual dt with the tool in 1. in the end the created dt must reside in sys:devs/datatypes/ drawer.

Then you would create a default icon in sys:prefs/Env-archive/SYS drawer. Don't forget to reboot or copy .info file to ram:env/sys in order to test. also don't forget to set which tool to start f.e. c:lx or dh4:emulators/mycoolemulator

To test, open Wanderer then show all files and doubleclick on a file of type you just created. Alternatively you could use the 'open' command from shell (with file of datatype you just created as parameter).

And as a last note. it would perhaps be welcome to have a program like xicon and/or runprglist for AROS (unfortunately both without source, but something similar could be created for AROS).

Sounds complicated ?

Perhaps... but OS like windows needs a complete registry to be able to do things like this. And yes, i am aware windows has gui tools that does it (more or less) for you (by manipulating the registry). Same could be done for AROS (without integrating a registry in AROS that is ).

Would that suffice ?

red1+2: typos, reformatting.

disclaimer: please note that using these tools can screw up your currently installed support for datatypes when used incorrectly. Do not use if you do not understand what you are doing. Use at own risk.


==Network Connection==

AROS currently only has one real choice for TCP/IP networking - AROSTCP.  This is a port of the AmiTCP package from AmigaOS (TM), with a number of enhancements/fixes from AROS developers. 


===Wired===

Use Network Prefs to setup 


=====IPv6=====

Some support 


128bit IPv6 address packet 
&lt;pre&gt;
Local FD::/8
Global 2000::/3
64:ff9b::/96
&lt;/pre&gt;
NAT64 translates IPv6 to IPv4 
DNS64 


OS routing works with 
&lt;pre&gt;
MacOS Ventura 
Windows 11 with cloud account 
Ubuntu Jammy Jellyfish 
Android 10 (block google dns) 
&lt;/pre&gt;


====IPv4====

The top half of the IPv4 Configuration tab on the Network Prefs deals with the network card/USB and the lower half the router part. 

[[File:AROS Wanderer Network Prefs DHCP.png|thumb|DHCP Settings]]

'''Upper part of IPv4 tab''' 
* Click Add on the top right of the Prefs which opens a window called '''Interface''' 
* Enter Name as net0 (but can be anything as long as it is consistently used in other sections) 
* check mark on Active
* select device to be used using the '''right hand-side gadget''' of the box where the device name will go 
* set Unit to 0 
* IP Mode is default set to '''Get address from DHCP''' 


* IP Mode set to Manual if DHCP does not work automatically 

From the shell CLI,  ifconfig -a

Under net0: section, inet starting 192.168.x.xxx

* inet or '''Address''' of network card 
* netmask convert to decimal so 0x'''ffffff7f''' becomes 255.255.255.247 which is used to adjust the above '''Address''' into 
* broadcast 192.168.xxx.xxx

click OK


[[File:AROS Wanderer Network Prefs Manual.png|thumb|Manual Settings]]

'''Lower part of IPv4 tab''' 
* IP Mode Get address from DHCP (default) 


* or changing to Manual if automatic DHCP set up does not work 
* '''Gateway''' (Router Internal LAN-IP) (Default Route) = 192.168.0.1 (D-Link Netgear), 192.168.1.1 (Linksys 3com), 192.168.2.1 (SMC Microsoft), 192.168.1.254 (Belkin), 192.168.123.254 (USRobotics) else check with your router manual 
* first DNS = use 208.67.222.222 (opendns) or Gateway number above (to test web browser access to router) or 212.50.160.100 (google)  i.e. or whatever your ISP needs you to set 
* second DNS = use 208.67.220.220 (opendns) or Gateway number above (to test web browser access to router) or 213.249.130.100 (google) i.e. or whatever your ISP needs you to set 


* At the bottom of IPv4 tab, check mark the '''Start networking during system boot''' option 
* Save and reboot (sometimes Network restart fails, so reboot every time to be sure) 


'''an alternative way''' to AROS ifconfig -a, other OSs have similar for the same internet connection. Another connection will have different settings. 

e.g. From [http://www.ncsu.edu/resnet/windows/ipconfig/ Windows], '''ipconfig /all''' 
and note down the IP, subnet mask, default gateway, and DNS servers values and put these values in &quot;manually&quot; into AROS Network prefs. 

e.g. From Linux via dhcp router have a look at etc./dhcpc/dhcpcd-eth0.info 
* for manual input look at /etc/networks (IP or Gateway) and /etc/resolv.conf (DNS) 

 Please note that all in one routers (wired+wireless) or separate routers may need different settings 

IPv4 involves routing (192,168.x.x), firewall, NAT 


===Wireless===

 You may have a Wifi Prefs to use for wireless setup 

[[File:MyArosWirelessSetup.png|thumb|Setting up]]

[[File:MyArosWirelessTCP.png|thumb|Shell commands to work out what is happening]]

We must first make certain you have a Atheros 5k chip inside acting as the wireless wifi option. Open PCITool in Tools directory. Down left hand side are a series of numbers 0.00.0 etc. Click on some at the bottom and hopefully one of them will say Atheros AR5??? or AR242?. 

or a Realtek RTL8187B, we can check using Prefs/Trident as this one is USB based 


There are many similarities with the above Wired set up so please read the above section as well 


* open Network/Prefs
* In '''IPv4 Configuration''' tab - click Add - enter net0 / active tick / #?.device / Unit 0 / IP Mode = manual (important if default DHCP does not work automatically) 

Make sure that any extra network names (e.g. eth1 or net1) should be deleted. If net0 already st previously, change net0 so that it shows associated with the appropriate device name like atheros5000.device or realtek8180.device. Having two entries here will cause sub-net problems. 

* Go to '''Wireless''' tab and click on &quot;Add&quot; button. 
* Insert network name (SSID your wireless network name use wirelessmanager to get it), select right &quot;encyption&quot; that is most likely &quot;WPA&quot;. 
* Key Type set as &quot;Passphrase&quot;. i.e. type in your password for your router (aka access key). 
* Unselect (no tick) &quot;hidden&quot; if it is selected, then apply. You may have to tick it if wireless does not work. 
* Finally, Save and '''reboot'''. 

For the best chance of success, set networking to start at boot, and then reboot with the USB adapter plugged in. 


===USB Ethernet===

Open SYS:Prefs/Network and in the IPv4 Configuration tag (top table covers your usb stick) 

* click Add button
* set Name as net0
* Tick Active box
* enter the usb-ethernet.device e.g. dm9601eth.device, usbpegasus.device or usbasixeth.device use SYS:c/devlist, '''Scout''' or trident prefs to get the correct spelling 
* set Unit to 0 (which is usual but check the messages from the bottom of the Trident prefs whilst plugging the device in to determine the unit number otherwise) 
* IP Mode is set to Get address from DHCP (make sure your router is set right for that) 
'''or manual'''
* IP Address of network card, i.e. 192.168.0.xx or 192.168.1.xx (xx being greater than 1) 
* Subnet netmask = 255.255.255.0 
* click OK

There can be sometimes be boot failures when using USB ethernet - plug the USB device in after boot and save the network prefs to make it work again. 


Lower part of IPv4 tab covers the router information 

* IP Mode Get address from DHCP 
'''or if manual settings'''
* Gateway (IP Address of router) = usually 192.168.0.1 or 192.168.1.1 but see router manual to make sure. 
* first DNS = use 8.8.8.8, 208.67.222.222 (opendns) or 212.50.160.100 
* second DNS = use 8.8.4.4, 208.67.220.220 (opendns) or 213.249.130.100 


===USB Tethering via Android smartphone===


Go to AROS Network Prefs (IPv4 configuration tab) and write type in &quot;usbrndis.device&quot; in the &quot;device&quot; textfield of &quot;Interface&quot; sub-window, which appears when you add a new device (or modify an existing one). Select &quot;Start Network during system boot&quot; and saved the configuration, the Connection is immediate no reboot is needed.&lt;br&gt;

usbrndis.device is a resident device (virtually always there) in fact, a driver is not present in DEVS:Networks &lt;br&gt;&lt;br&gt;

Plug in USB cable, go to Android settings and enable &quot;USB Tethering&quot; &lt;br&gt;

A reboot should not be necessary.

When restarting AROS, the Smartphone deactivates the connection and to access the network again have to reactivate it before starting the browser. 


===Solving Issues===

[[File:MyArosTCP.png|thumb|Aros network setup diagnostics - why does it not work?]]

* In Network Preferences, have '''only one''' item in the IPv4 Configuration tab 
* If using manual settings, make sure all numbers are correct, especially for IP address of the card/usb (changing the last number in chain of four) 
* For any USB based networking, it is often necessary to save in Prefs/Network, reboot AROS and network support can begin 


* For wired, make sure that the LAN-cable is plugged in before starting the computer 


* If wireless, try getting closer to the router. 
* Switch off the encryption option from your router then try wifi, if successful then your ip/dns is ok. If not then your ip/dns settings are most probably wrong or need to use one or more opendns numbers 
* Replace detachable wireless antenna (best wireless option to buy if you can) with a stronger antenna ie. 5&amp;nbsp;dBi or 7&amp;nbsp;dBi 
* Try with another computer/laptop/machine 

Program Error  C:WirelessManager 

* Test with another OS 
* Check that Wifi works before changeover (if possible) 
* Check that socket and card are working 
* Check if card is too new for laptop (date code on card MMYY blue askey date 2005-2007 etc)   


Are you connecting with the Router ? 

Check with protection off e.g. wps and wep to see if it makes a difference. 


For USB wireless - stopping and starting may be needed...

&lt;pre&gt;

; $VER: AROSTCP-startnet 1.0 (01/08/06)
; AROSTCP-startnet (c) The AROS Dev Team.
;
Run &lt;NIL: &gt;NIL: AROSTCP
WaitForPort AROSTCP
If NOT Warn
  ; echo &quot;Stack online&quot;
Else
  echo &quot;Wait for Stack Failed&quot;
EndIf

; stop and restart
execute &quot;sys:system/network/AROSTCP/s/stopnet&quot;

Run &lt;NIL: &gt;NIL: AROSTCP
WaitForPort AROSTCP
If NOT Warn
  ; echo &quot;Stack online&quot;
Else
  echo &quot;Wait for Stack Failed&quot;
EndIf

run &lt;NIL: &gt;NIL: wirelessmanager realtek8180.device

&lt;/pre&gt;


What IRQ number is assigned to the device? You can check with Tools/PCITool? 
It's possible the BIOS hasn't set the right IRQ number. If you have a Linux CD/DVD handy, could you check if it boots with the options &quot;acpi=off noapic nolapic&quot;? 


If the following does nothing, this will help us figure out why networking doesn't start automatically at boot

open a shell and run the following commands:

&lt;pre&gt;
echo ${AROSTCP/AutoRun}
echo ${AROSTCP/WirelessAutoRun}
echo ${AROSTCP/WirelessDevice}
&lt;/pre&gt;

Please report the output, typically it will look like this  

# True  (explanation this variable is related to the &quot;Start networking during system boot&quot; checkbox in network prefs) 
# True  ()
# Devs:networks/atheros5000.device unit 0


If there's a problem with the AROSTCP package. What's the output of this?

 ENV:sys/packages/AROSTCP 

should return a string = Sys:System/Network/AROSTCP


By the way, a quicker way to check networking is working would be to run some shell commands such as:


&lt;pre&gt;
ping www.google.com
ifconfig net0
&lt;/pre&gt;


The best way to list the available networks and diagnose / troubleshoot problems with connecting to a wireless network is to run WirelessManager manually. First uncheck the &quot;Start networking during system boot&quot; box in the Network prefs app, then save and reboot. Then run this in a shell:

 C:wirelessmanager atheros5000.device verbose 

or 

 C:wirelessmanager realtek8180.device verbose 

and capture the output 


If the above does not help, could you edit the file SYS:System/Network/AROSTCP/S/Package-Startup, and change &quot;&gt;NIL:&quot; to &quot;&gt;T:wifi.log&quot; on the WirelessManager line and add this as well Wait 5?

&lt;pre&gt;
if ${AROSTCP/WirelessAutoRun} eq &quot;True&quot;
Run QUIET &quot;C:WirelessManager ${AROSTCP/WirelessDevice} &gt;T:wifi.log&quot;
wait 5
EndIf
&lt;/pre&gt;

Then save, reboot and post the log file (T:wifi.log) here.


&lt;pre&gt;

c:wirelessmanager atheros5000.device verbose
Initializing interface 'atheros5000.device:0' conf 'ENV:Wireless.prefs' driver 'default' ctrl_interface 'N/A' bridge 'N/A'
Configuration file 'ENV:Wireless.prefs' -&gt; 'ENV:Wireless.prefs'
Reading configuration file 'ENV:Wireless.prefs'
Line: 1 - start of a new network block
ssid - hexdump_ascii(len=7)
65 63 68 65 6c 6f 6e echelon
PSK (ASCII passphrase) - hexdump_ascii(len=14): [REMOVED]
key_mgmt: 0x2
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 0
id=0 ssid='echelon'


Then it just sits there. Not sure what a normal dump looks like, I don't see anything that looks wrong in the configuration.
&lt;/pre&gt;

looks like the driver isn't working with that card. Has anyone else successfully used that exact model number (AR2413)?


&lt;pre&gt;

Initializing interface 'atheros5000.device:0' conf 'ENV:Wireless.prefs' driver 'default' ctrl_interface 'N/A' bridge 'N/A'
Configuration file 'ENV:Wireless.prefs' -&gt; 'ENV:Wireless.prefs'
Line: 1 - start of a new network block
ssid - hexdump_ascii(len=7):
65 63 68 65 6c 6f 6e echelon
PSK (ASCII passphrase) - hexdump_ascii(len=14): [REMOVED]
key_mgmt: 0x2
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 0
id=0 ssid='echelon'
*** [wpa_sm_init] sm-&gt;pmksa=02c66fd4 ***
Own MAC address: 00:01:36:15:ae:0c
RSN: flushing PMKID list in the driver
Setting scan request: 0 sec 100000 usec
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: Supplicant port status: Unauthorized
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: Supplicant port status: Unauthorized
EAPOL: Supplicant port status: Unauthorized
Added interface atheros5000.device:0
State: DISCONNECTED -&gt; SCANNING
Started AP scan for wildcard SSID
MLME: starting scan
MLME: scan channel 1 (2412 MHz)
sana2: sending MLME frame


Then it stops. Does this mean the router is not authorizing this NIC?

IRQ 4 (A)

&lt;/pre&gt;

apparently locking up when the first frame is sent (a scan request).


&lt;pre&gt;

Devs/Networks/atheros5000.device:0
Initializing interface 'Devs/Networks/atheros5000.device:0' conf 'ENV:Wireless.prefs' driver 'default' ctrl_interface 'N/A' bridge 'N/A'
Configuration file 'ENV:Wireless.prefs' -&gt; 'ENV:Wireless.prefs'
Reading configuration file 'ENV:Wireless.prefs'
Line: 1 - start of a new network block
ssid - hexdump_ascii(len=12):
41 69 72 4c 69 6e 6b 35 39 33 30 30 AirLink59300
PSK (ASCII passphrase) - hexdump_ascii(len=8): [REMOVED]
key_mgmt: 0x2
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 0
id=0 ssid='AirLink59300'
*** [wpa_sm_init] sm-&gt;pmksa=0224e444 ***
Own MAC address: 00:1f:e1:42:e3:7a
RSN: flushing PMKID list in the driver
Setting scan request: 0 sec 100000 usec
[eloop_reg_timeout] Timeout is at 1317686594.160000
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: Supplicant port status: Unauthorized
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: Supplicant port status: Unauthorized
EAPOL: Supplicant port status: Unauthorized
[eloop_reg_timeout] Timeout is at 1317686595.060000
[eloop_reg_timeout] Timeout is at 1317686604.060000
Added interface Devs/Networks/atheros5000.device:0
[eloop_run] Starting
State: DISCONNECTED -&gt; SCANNING
Starting AP scan for wildcard SSID
MLME: starting scan
[eloop_reg_timeout] Timeout is at 1317686594.160001
MLME: scan channel 1 (2412 MHz)
[eloop_reg_timeout] Timeout is at 1317686594.193000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686594.233000
MLME: scan channel 2 (2417 MHz)
[eloop_reg_timeout] Timeout is at 1317686594.253000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686594.293000
MLME: scan channel 3 (2422 MHz)
[eloop_reg_timeout] Timeout is at 1317686594.333000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686594.373000
MLME: scan channel 4 (2427 MHz)
[eloop_reg_timeout] Timeout is at 1317686594.393000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686594.433000
MLME: scan channel 5 (2432 MHz)
[eloop_reg_timeout] Timeout is at 1317686594.473000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686594.513000
MLME: scan channel 6 (2437 MHz)
[eloop_reg_timeout] Timeout is at 1317686594.553000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686594.573000
MLME: scan channel 7 (2442 MHz)
[eloop_reg_timeout] Timeout is at 1317686594.613000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686594.653000
MLME: scan channel 8 (2447 MHz)
[eloop_reg_timeout] Timeout is at 1317686594.693000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686594.713000
MLME: scan channel 9 (2452 MHz)
[eloop_reg_timeout] Timeout is at 1317686594.753000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686594.793000
MLME: scan channel 10 (2457 MHz)
[eloop_reg_timeout] Timeout is at 1317686594.833000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686594.853000
MLME: scan channel 11 (2462 MHz)
[eloop_reg_timeout] Timeout is at 1317686594.893000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686594.933000
MLME: scan channel 12 (2467 MHz)
[eloop_reg_timeout] Timeout is at 1317686594.973000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686595.013000
MLME: scan channel 13 (2472 MHz)
[eloop_reg_timeout] Timeout is at 1317686595.033000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686595.073000
EAPOL: disable timer tick
EAPOL: Supplicant port status: Unauthorized
MLME: scan channel 14 (2484 MHz)
[eloop_reg_timeout] Timeout is at 1317686595.113000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686595.153000
MLME: scan channel 1 (2412 MHz)
[eloop_reg_timeout] Timeout is at 1317686595.193000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686595.213000
MLME: scan channel 2 (2417 MHz)
[eloop_reg_timeout] Timeout is at 1317686595.253000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686595.293000
MLME: scan channel 3 (2422 MHz)
[eloop_reg_timeout] Timeout is at 1317686595.333000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686595.353000
MLME: scan channel 4 (2427 MHz)
[eloop_reg_timeout] Timeout is at 1317686595.393000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686595.433000
MLME: scan channel 5 (2432 MHz)
[eloop_reg_timeout] Timeout is at 1317686595.473000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686595.493000
MLME: scan channel 6 (2437 MHz)
[eloop_reg_timeout] Timeout is at 1317686595.533000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686595.573000
MLME: scan channel 7 (2442 MHz)
[eloop_reg_timeout] Timeout is at 1317686595.613000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686595.653000
MLME: scan channel 8 (2447 MHz)
[eloop_reg_timeout] Timeout is at 1317686595.673000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686595.713000
MLME: scan channel 9 (2452 MHz)
[eloop_reg_timeout] Timeout is at 1317686595.753000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686595.793000
MLME: scan channel 10 (2457 MHz)
[eloop_reg_timeout] Timeout is at 1317686595.833000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686595.853000
MLME: scan channel 11 (2462 MHz)
[eloop_reg_timeout] Timeout is at 1317686595.893000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686595.933000
MLME: scan channel 12 (2467 MHz)
[eloop_reg_timeout] Timeout is at 1317686595.973000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686595.993000
MLME: scan channel 13 (2472 MHz)
[eloop_reg_timeout] Timeout is at 1317686596.033000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686596.073000
MLME: scan completed

&lt;/pre&gt;

Is your network hidden? If so, did you enable the 'Hidden' checkbox in the network prefs? What distro version are you using? 


&lt;pre&gt;
&quot;ENV:sys/wireless.prefs&quot; looks like this:
network={
ssid=&quot;testadhoc&quot;
key_mgmt=NONE
wep_key0=&quot;12345&quot;
wep_tx_keyidx=0
}
&lt;/pre&gt; 


If your router doesn't broadcast its SSID (hidden), you need to add this option to the network block of the wpa_supplicant.conf on your aros machine and make changes after  # Example blocks: 

 scan_ssid=1

Here's a full description of all the [http://hostap.epitest.fi/gitweb/gitweb.cgi?p=hostap.git;a=blob_plain;f=wpa_supplicant/wpa_supplicant.conf config file options]. 

&lt;pre&gt;
ap_scan=1

network={
ssid=&quot;YOURESSID&quot;
scan_ssid=1
proto=RSN
key_mgmt=WPA-PSK
pairwise=CCMP
group=CCMP
psk=YOURPASSWORD
}
&lt;/pre&gt;

&lt;pre&gt;
filter_ssids=1
ap_scan=2

network={
ssid=&quot;REMOVED&quot;
scan_ssid=1
bssid=REMOVED
priority=100
mode=0
proto=RSN
key_mgmt=WPA-PSK
auth_alg=OPEN
pairwise=CCMP
group=CCMP
psk=REMOVED
}
&lt;/pre&gt;


Error 6: Couldn't resolve host name.

Check Scout -&gt; Devices and look at the device that you are using, in the OCnt column it should state 2 which means AROSTCP and Wirelessmanager are both accessing this driver. If 0 or 1, then uncheck the checkbox in Network prefs for starting networking at boot, save and reboot. Then run this is the shell:

C:WirelessManager realtek8180.device unit 0


some quirks setting up the wireless network as well 

1) it's far better setting up either the wired OR the wireless network adapter as net0:, or weird things happen

2) it's better using fixed IP on the local network instead of DHCP

3) network setting must be placed in network setting panel in /prefs, using the wirelessmanager helped me finding available SSIDs, but not actually connecting to them

once done, reboot.


If previous setup is proving problematic 

&lt;pre &gt;

SYS:Prefs/Env-Archive/Wireless.prefs
SYS:Prefs/Env-Archive/Zune/OWB.config
SYS:Prefs/Env-Archive/Zune/global.config
SYS:Prefs/Env-Archive/AROSTCP/WirelessDevice
SYS:Prefs/Env-Archive/AROSTCP/db/Interfaces
&lt;/pre &gt; 

Make a copy of these files and restore in case of problems. 


Please try this test to check if you can connect to your router, ie established that the WiFi layer is working 

̊̊̊̊Boot with networking disabled, by make sure that &quot;Start networking at boot&quot; in Network Prefs is unchecked (no tick).  
̊ Run this in a shell: C:WirelessManager atheros5000.device VERBOSE
̊If the output of that command is too long to summarise here, you can redirect it to a file by adding &gt;RAM:wifi.log to the end, then attach or paste that file here.


try running &quot;status&quot; in the shell and check that AROSTCP is listed/running
If AROStcp is not showing, then AROSTCP is not running. attempted to start it by clicking Use or Save in network prefs, or checking the &quot;start networking at boot&quot; box or typing into a shell. 

 Execute SYS:System/Network/AROSTCP/s/startnet

(run Status again afterwards).


The &quot;cannot resolve hostname&quot; will appear if you are blocked on the wifi network by the router as well as aros not being able to assign correct network address.

One way of testing this might be to disable the firewall in the router. you might also check the router how it sees the attempts aros do to speak to it. The easiest way to do that would be to manually give aros an IP number in the routers accepted range. and see if it shows up at all within the router.


Tests that can be undertaken to determine correct settings and functions 

 pciinfo
 sanautil -d broadcom4400.device status

&lt;pre &gt;
 ping &lt;router-address&gt; e.g. 192.168.0.1 (aka inet) or 80.237.146.33 (www.amiganews.de) 
 ifconfig net0
 ifconfig net0 up
 extras:networking/utils/sanautil/sanautil -d atheros5000.device status
 WirelessManager atheros5000.device verbose &gt;RAM:wifi.log
 ;to send the log to RAM disk to be read easier or if detected, 
 Run WirelessManager atheros5000.device &gt;NIL:
 Run WirelessManager atheros5000.device ssid=&quot;mynet1&quot; &gt;NIL: 
 C:WirelessManager realtek8180.device unit 0 
&lt;/pre &gt; 

Please look at the task list in Scout, and check if WirelessManager and AROSTCP are running. Also look at the device list in Scout to check if realtek8180.device is open. 


start tools/debug/sashimi, maybe it shows some debug messages when disconnection happens.


Firstly, let's take a look at what your setup most likely looks like, assuming you use a router. See diagram below: 

&lt;pre&gt;
Internet &lt;---------&gt; home router &lt;---------&gt; computer 
-----------external IP------------------internal IP-------------
&lt;/pre&gt;

Okay, so what am I trying to show you with that diagram. A few things. Firstly, the IP address that connects you to the Internet is not the same one that connects you to your router. What happens is that your computer doesn't have a direct connection to the Internet, instead your router connects to the Internet, and your computer connects to the router.

You can see the external and internal IP addresses in these example settings...

* Default Gateway : 76.91.64.1 (external IP for ISP/Internet host)
* IP Address : 76.91.71.184 (external IP for home router)

* IP Address : 192.168.0.1 (internal IP for home router)
* Address = 192.168.0.161 (internal IP for computer)

As you can see, there are two internal IP addresses and two external IP addresses. This is because there is a client/server relationship, effectively one address is for the service (server) and one address is for the device trying to access that service (client).

The server addresses in your case are 76.91.64.1 (your ISP's address, serving the Internet), and 192.168.0.1 (your home router's address, serving your home network). The term gateway applies here, they are your gateway to those services.

Subnet masks are used along with IP addresses to determine which IP addresses are allowed access to a network. I did learn the more in-depth rules about subnet masks once (watched a CCNA vid), but I've forgotten about it. The basic level of understanding you'll need is easy to remember though. A subnet mask value of 255 means that portion of the IP address must stay constant, whereas a subnet value of 0 means any unassigned value up to 255 is allowed in the IP address.

By far the most common subnet value is 255.255.255.0. What this means is that the first three parts of the IP address you use to connect to a service must stay the same as the server/gateway address, and only the last section can change.

So if your router's internal IP address is 192.168.0.1, and the subnet mask is 255.255.255.0, the only addresses that will be allowed to be used on that network are between 192.168.0.2 and 192.168.0.255 (I think 192.168.0.0 is reserved for other uses).

Final point to make is about DHCP (a.k.a. dynamic IP) vs static IP. A server/router using DHCP gives a device that connects to it an address within the acceptable range. It usually starts with the lowest numbered free address, so with your router it'll give the first device that connects to it 192.168.0.2, the next device 192.168.0.3, and so on. Static IP addresses are where you set the IP address you want to connect with in advance. 

When using static IP addresses on a router where DHCP is active, it's good to use a high number to avoid conflicts with other devices that are connected to your network, to reduce the risk that both devices will try using the same IP. That's why your current choice of 192.168.0.161 is good, unless you have over 159 devices connected on your current network!


Okay, so what's the next step. Well, if you can use ping, I'd suggest pinging 192.168.0.1. If you get a positive response it means you're connected to your router, if you don't get a response it means the connection between your router and your computer is at fault.

Documentation on configuring the AROSTCP environment further can be found [http://en.wikibooks.org/wiki/Aros/User/Networking here] 


===File Sharing===

As AROS knows only a few filesystems (FFS, OFS, SFS, PFS (amiga only), FAT12, 16, 32, Microsoft NTFS (windows), UDF (Blu-ray)). 
The others in regular use like MacOSX hfs+, Linux ext2/ext3 and ext4, Haiku BeFS provide a problem in transferring files. 

Linux can access SFS partitions but it needs to be compiled. The latest full source are [http://home.elka.pw.edu.pl/~mszyprow/programy/asfs/ here]. It compiled fine with a 2.6.30 kernel in Puppy Linux 4.31. 

An alternative, is to use a FAT32 partition to share. Setup a 4G FAT32 partition using HDToolbox for sharing, and the rest of the space as SFS for an Aros install. It works very well. 

Files could be transferred via TCP internet network. 


====SMB2/3====

With Windows you can share one folder or all folders of the &quot;Public&quot; user.

On Windows what is important is to enable sharing (Network and Sharing Center).

AROS Mountlist should look lke this 
&lt;pre&gt;
Handler = L:smb2-handler
StackSize = 65536
Priority = 5
GlobVec = -1
ACTIVATE=1
Startup = &quot;smb://UserAcc:password@PCShare/Sharefolder&quot;
&lt;/pre&gt;

which could also be
&quot;smb://UserPC:password@192.168.x.x/Public&quot;
or
&quot;smb://UserPC:password@Name-PC/Public&quot;

so
&quot;smb://UserPC:password@192.168.1.158/Folder&quot;
or
&quot;smb://UserPC:password@Name-PC/Folder&quot;


After you have configured a share generates a DOSDrivers it is named &quot;SMB0&quot; which includes the setting, and at each reboot it is Mounted. You can still delete the DOSDriver by hand, is located in Storage/DOSDrivers, the file &quot;ServerAutoMounts&quot;, in ENV:AROSTCP which indicates the DOSDriver to be mounted, should also be deleted. 
The per-mount files are written to ENV:SMB or SYS:Storage/DOSDrivers. There is also additional file ENV:AROSTCP/ServerAutoMounts which states what will be presented to the end user. 


====Old SMBFS====

e.g. to connect to a NAS share such as \\NASBOX\Shared use -:

SMBFS WORKGROUP=&lt;YOUR WORKGROUP NAME&gt; VOLUME=&lt;AROS volume name to use&gt;: SERVICE=&lt;UNC Path to connect to&gt;

SMBFS WORKGROUP=MYNET VOLUME=Shared: SERVICE=//NASBOX/Shared

And you will then have an icon appear on your desktop for the volume name you have chosen. 


You can put the above script into wbstartup or  

give it an icon, change it to a 'project' and give it the default tool c:iconx 

Open a shell and type copy sys:script.info &quot;sys:wbstartup/YOURSCRIPTNAME.info&quot;

This should create an icon for your script file.

Now right-click on your script and select 'information'.

Change 'tool' to 'project', put 'c:iconx' into the 'default tool' box, click save 

The reason being that scripts need to be opened with 'execute SCRIPTNAME' (or 'iconx') whereas the programs started from wbstartup are opened using 'run PROGRAMNAME'. It's the same as trying to start a command-line tool from the workbench by double-clicking it.


====Setup ISO images within AROS====

Use [http://archives.aros-exec.org/index.php?function=browse&amp;cat=driver/storage DiskImage] which supports many cd image formats ISO, CCD, MDF/MDS, CUE/BIN, NRG and UIF. To mount CD or DVD images use below....

&lt;pre &gt;
# Rename your iso 'Unit0' (note no extension).
# Do 'View/All files' on you Aros partition. You should now see a folder called 'Diskimages'. Copy your renamed iso to there. 
(Alternatively, you could type at the shell 'assign FDSK: xxx', where xxx is the location of your iso.) 
# From the shell, type 'mount CD0:' and the iso should appear on the Wanderer desktop. You can now access it like a real disk.
&lt;/pre &gt; 

 assign devname: dismount 
 Assign DOSVOLUME: remove
 [http://aminet.net/package/disk/misc/unmount-0.1 unmount] most filesystems work but SFS lacks support for ACTION_DIE packet 

If you are using an IcAros install, the startup scripts are set up to wipe the Diskimages directory on boot, so its worth keeping a second copy of the iso somewhere else. Alternatively, you could set up extra mountlists for additional iso images. I've made a file called iso1 in the Aros:devs directory that contains the following text:

&lt;pre&gt;
/* Entry for ISO image */

ISO1:
FileSystem = cdrom.handler
Device = fdsk.device
Unit = 1
LowCyl = 0
HighCyl = 0
Surfaces = 1
BlocksPerTrack = 1
DOSType = 0x41434400
Activate = 1
#
&lt;/pre&gt;

Then I just need an iso called 'Unit1' (corresponding to the 'Unit = 1' entry in the mountlist) in Diskimages (or wherever I assign FDSK: to) and to mount I type in at the shell:

 Mount iso1: from devs:iso1

Of course, if you create mountlists for ISO2, ISO3:, etc. (with the corresponding change to the 'Unit = ' line) you can have as many isos mounted as you wish. I just call mine ISO1: etc. to distinguish them from the real CD drives 


==Video Guides==


Video demonstrations and tutorials covering:

:00. '''Introduction''' 
::[https://www.youtube.com/@jamesmattson6813/videos Various Aros Installs], 
::[https://www.youtube.com/embed/j8EmSEby0Rg AROS repo in gource, view of AROS dev commits from 1997 to 2025], [http://www.youtube.com/watch?v=Vx_zqlBow40&amp;feature=related Gource view of AROS 1997 up to 2009], 
::[http://www.youtube.com/watch?v=s1RsvEm7UrU Why an Amiga OS in 2011], 
::[https://www.youtube.com/watch?v=1W886mheV74&amp;pp=ygUPYW1pZ2EgYXJvcyAyMDI2 Johan Grip on early days of AROS x86], [https://www.youtube.com/watch?v=mXaKDhtTTqQ&amp;t=14s&amp;pp=ygUPYW1pZ2EgYXJvcyAyMDI2 Michel Schulz on Aros and PiStorm], 

:01. '''Installation'''
::[https://www.youtube.com/watch?v=M7YjufrJqDs Aros One install], [https://www.youtube.com/watch?v=iIMguHTdC5E Aros One USB install], [https://www.youtube.com/watch?v=ZNXauy5m5Wc Aros One install], [http://vimeo.com/11013489 Modify Grub boot], 
::[http://www.youtube.com/watch?v=wyQVeyXIywc&amp;feature=channel iMica Silent Pt3], [http://www.youtube.com/watch?v=o2AnkoflY14 Wipe whole drive and Install - warning loss of data on drive], 
::[http://www.youtube.com/watch?v=OVXm6_-witQ VirtualBox install], [ VMware install], 
::[http://www.youtube.com/watch?v=0k2PEmT8I14 Broadway AROS Install], 
::[https://www.youtube.com/watch?v=PtDiXhjSIfs Is Aros Icaros a choice?], 
::[ driver install], 
::[http://www.vimeo.com/10491104 HDAudio install but needs account], [], 

:02. '''Amiga Basics'''
::[http://www.youtube.com/watch?v=TY8mWxwzH5o Screens tutorial], 
::[https://m.youtube.com/user/AMIGASYSTEM/videos General], [ Dos Scripts tutorial], [http://www.youtube.com/watch?v=hPT7SmVEpjc OS 1.2], [http://www.youtube.com/watch?v=n6kX3FqH8Ww&amp;feature=related OS 1.3], 

:03. '''Customisation demos'''
::[https://www.youtube.com/@AMIGASYSTEM/videos Prefs tutorial], [ Decoration tutorial], [http://www.youtube.com/watch?v=Dn5C8G3aDXU Scalos], 

:04. '''Setting up''' internet access and surfing the web, FTP, IRC and Mail apps 
::[ Network Prefs], [ AirCOS tutorial], [ jabberwocky tutorial], 

:05. '''Native bundled Games and Applications''' 
::[http://www.youtube.com/watch?v=aYlFv2B-VXc 3D Games], [http://www.youtube.com/watch?v=MXK7wwhd-R0 Latest Games], [http://www.youtube.com/watch?v=RUgiVThv23Q&amp;feature=mfu_in_order&amp;list=UL PrBoom GL], [http://www.youtube.com/watch?v=0s7u8TPy7V4 Assault Cubes], [http://www.youtube.com/watch?v=fih6aCXKeqs Cube 2], [http://www.youtube.com/watch?v=-X0ay0MGOms DosBox on Aros], [http://www.youtube.com/watch?v=7nKduDjf14k Oct 2010], 

::[http://www.youtube.com/watch?v=FziV2z_uxnQ Apps Pt 1], [http://www.youtube.com/watch?v=xs37_nfa5CI Apps Pt 2], [http://www.youtube.com/watch?v=Bn59_VvbQR0&amp;feature=related Apps Pt 3], 
::DOpus4 [http://www.youtube.com/watch?v=aSRybWjrrME DOpus 4], 
::Milkytracker [http://www.youtube.com/watch?v=VxBOEPzpdKg&amp;feature=related Laying Down Base Tracks], 
::[http://www.youtube.com/watch?v=k2uKQ0-ieOE Audio Evolution 4 in action], [http://www.youtube.com/watch?v=Zq4r9k0_jZI Quick Videos], 
::[http://www.youtube.com/watch?v=gGKCFZcIc0I&amp;feature=related ScreenRecorder], [http://www.youtube.com/watch?v=974c2e-Fqak&amp;feature=related TV out Tests], 
::[http://www.youtube.com/watch?v=fjq8ct5d5IY AmiFIG], [http://www.youtube.com/watch?v=h0rHvPhYJo4&amp;feature=youtu.be ZuneFIG], 
::[http://wiki.povray.org/content/Documentation:Tutorial_Section_1 POVray Tutorial 1], 
::[http://www.youtube.com/watch?v=Jk-ZNLfJsvQ pt 1, jan. 2008], [http://www.youtube.com/watch?v=nWRy33g1R7Y pt 2, feb. 2009], [http://www.youtube.com/watch?v=r5PbhCtm4vE pt 3, feb. 2010], 

::[https://www.youtube.com/watch?v=G7_FJUoQ89o Hollywood programming], [], [], [],

::[], [], [], 
::[], [], [], 
::[], [], [], 


:06. '''Commercial software available'''
::[http://www.youtube.com/watch?v=fKXY9B4R43s AntiryadGX 3D Game Editor], 
::[http://www.youtube.com/watch?v=TMS9NDzwm5U BOH indie Game], 

:07. '''Running classic amiga apps and games''' 
:: Amiberry [], [], 
::[http://vmwaros.blogspot.com/2008/11/introducing-amibridge.html Intro Amibridge], [http://www.youtube.com/watch?v=ee2PWvCZeLo Old Amiga Apps], [http://www.youtube.com/watch?v=ee2PWvCZeLo Why Janus UAE is good], 
::[https://www.youtube.com/watch?v=VhlsNSYSuDg DPaint tutorial]

::[http://vmwaros.blogspot.com/2009/11/can-icaros-play-my-amiga-games-and-why.html Play Amiga Games], [https://www.youtube.com/watch?v=XTaZCNOvCnE], 
::[http://www.youtube.com/watch?v=tMehS77LXQ4 Pagestream Introduction], [http://www.youtube.com/watch?v=284-w3hTzII Pagestream Tutorial 1], [http://www.youtube.com/watch?v=mlwEGwhZzl4 Pagestream Tutorial 2], 
::[http://www.youtube.com/watch?v=iIcrIjPOctc Catweasel Mk4 PCI Part 1] and [http://www.youtube.com/watch?v=BaitHeL6bEA Part 2], 

:08. '''Misc and History'''

::[http://www.youtube.com/watch?v=d6mDXKU29w0 Mum uses old AmigaOS Workbench 1.1 (1986)], [http://www.youtube.com/watch?v=DaRkacQ-YMg Why an Amiga 500 (1987)], [http://www.youtube.com/watch?v=k5CYsgVCzYY an Amiga 2000 (1987)], 

:09. '''Misc Shows and Events'''
::[http://www.youtube.com/watch?v=klgVSWKs4kE VCF 2010], [https://www.youtube.com/watch?v=eQ3d5qR-Hv8 24:06 Jason McMullan at amiwest 2012 about AROS], [https://www.youtube.com/watch?v=jpQO7XSfAv4 Aros SMP multi core amiwest 2013], [], [https://www.youtube.com/watch?v=gFRtAAmiFbE], [https://www.youtube.com/watch?v=DjdUEyjx8GM], [https://www.youtube.com/watch?v=ydYDqZQpim8], [], [https://www.youtube.com/@uminekoshouten/featured], [https://www.youtube.com/shorts/NfoY023w-vE], 

:10. 
::[https://www.youtube.com/shorts/6qJTNW4-6GY]


===History===

The project was originally started by a small group of Amiga [http://www.amigahistory.co.uk/aros.html enthusiasts] in 1995. These individuals were mainly computer-based college university students at the start, though that student trend has diminished since. An interview with Aaron Digulla [http://arosshow.blogspot.com/2006/12/interview-with-aaron-digulla-who.html here] 

* 1992 Commodore folds 
* 1996-1998 much of the early years was concerned with exec, dos and intuition libraries. 
* Early 1999, Haage &amp; Partner used parts of the AROS code in AmigaOS 3.9. 
* March 2001, floppy disk images of AROS became available. 
* Early 2002, AROS changed its name from Amiga Replacement Operating System to Amiga Research Operating System 
* June 2002, AROS devs decided to use Zune (MUI 3.8 rewrite) as the GUI system. 
* November 2002, Eric Schwartz drew Kitty for AROS usage. 
* Early 2003, AROS.org underwent a graphics facelift. 
* Late 2003, GCC C compiler arrived. 
* Early 2004, Aros-Exec opened. 
* Early 2005, Aros Max bootable CD arrived. 
* Late 2005, SFS filesystem ported and allowed fast access to apps and network support arrived 
* Early 2007, AROS.org underwent another graphics facelift. 
* Mid-2007, AROS changed to AROS Research Operating System after A.Inc. sued Hyperion with a trademark violation. 
* Late 2007, the hard disk installer added and VmwAROS (later called Icaros Desktop) distro launched. 
* Early 2009, Our first usable web browser (OWB)
* September 2010, first wireless support appears and AspireOS started as a distro 


* Early 2012, the first paper-cut bugfix and Fab's Odyssey Web Browser ported 
* Early 2017, work started on utilising the addition cores on modern CPUs starting with the 64bit x86 PC version  
* Mid-2017, m68k port optimized for the Vampire 2 / Apollo accelerators (68080 AMMX FPGA) 
* 2018 The old AROS Exec website closed and a new one opened 
* 2019 AROS One x86 32bit distribution started and now with USB install version 
* Early 2021, backport of more features of 32bit PC ABIv1 into 32bit PC ABIv0 (Aros One 1.5 and above) 
* 2025 year of 64bit pc builds and porting 32bit applications to 64bit ABIv11
* 2026 update of [https://www.youtube.com/watch?v=6FKTL068ULM&amp;pp=ygUPYXJvcyBhbWlnYSAyMDI2 nvidia nouveau driver for 64bit PC] 


===Bounties===

To help inspire developers with both ideas and monetary incentives, rewards are offered for the successful completion of &quot;bounties&quot; (requests for missing/new functionality) chosen by the community and handled by [http://power2people.org power2people] (formerly done by TeamAROS). A monthly option is [http://www.power2people.org/funds/aros/ here].


Future goals for AROS include expanding its underlying retargetability to support even more diverse architectures, provide memory protection features and user level file security, SMP and many other wonderful features missing from AmigaOS &amp;mdash; while still providing as much source level compatibility as is possible (however it is accepted that to achieve some goals code certain things may require a little recoding).


[http://www.ohloh.net/p/aros/contributors Developers] come and go as with any open source effort and we would like to thank them for their efforts... 

;1996-2000:In DigullaA (coordinator), GripJ, TempletonI (BSD), SchulzM, RittauS, voordenDagL, HolmM, JohanssonT, VanIngelgomH, SteigerwaldM, BortasP, deJongK, AlfredssonJ, InnocentiB, 

;2001-2005:In [http://chodorowski.com/adam/aros.html ChodorowskiA], StegerG, BergerS, HeutlingS, AlemagnaF (gcc), VerhaegenS (rexx), KielH, MatheussenKS (CAMD), SzczygielskiP, ErikssonP, LeCorfecD (Zune), BauerS (Zune), FurlongW, GustafssonJ, AndrewsN, CafferkeyN, GierichM (jpeg), PattonJ, ParsonsM, DietrichJ, SeilerT, BischoffL, LorentzenNH, AdamO, BerglundH, SmithP, HolmenD, BlomM, 

;2006-2010:In FedinP, RusslerM, SzymczykS (owb), SmiechowiczK (openGL), WeissM, NorrisR, BrunnerO, WiszkowskiT, GreppinA, [http://www.fukt.bsnet.se/~bearsoft/ Bearsoft Björn Screwelius], ErbY, CharletF, HodgesC, [http://aros-exec.org/modules/newbb/viewtopic.php?topic_id=4819&amp;forum=18&amp;post_id=43103#forumpost43103 HokstadV], McMullanJ (m68k), WilenT (m68k), 

;2011- :In MuijzenbergPHvanden, ALB42, JonesEM, weiju, DizzyofCRN, wawa, miker, 


* 1996 - The linux hosted version for i386 was the first to arrive 
* 1998 - i386, The native version for i386-based PC AT computers and compatibles.
* 2004 - x86/64, The native version for 64-bit (x86_64, amd64) PC computers.
* 2008 - sam440/ppc, The native version for Sam440EP, Sam440EP Flex and Sam460ex computers.
* 2009 - efika, The native version for PowerPC Efika computers.
* 2010 - m68k, The native version for m68k Amigas or WinUAE
* 2013 - raspi/armfh, early native version for ARMv6 based Raspberry Pi computers.
* 2017 - x86/64bit smp 


Debugging capture serial debug at all (especially with sysdebug=all or --sysdebug=all) to see it displayed on screen 

* yes, usb -&gt; rs232 adapters can work most of the time, some of the cheapest ones are not fully compatible with all rs232 devices to capture to another device 
* you will need a null modem cable (or a null modem adapter usually female to female) in addition to the usb -&gt; rs232 adapter (usb adapter is a normal modem ie. the pins are not crossed over) 

Normal modem cable - straight connection DCE 
&lt;pre&gt;
Pin 2 -&gt; Pin 2  RXD
Pin 3 -&gt; Pin 3  TXD 
Pin 5 -&gt; Pin 5  GND
&lt;/pre&gt;

Null modem cable connections DTE 
&lt;pre&gt;
Pin 2 -&gt; Pin 3
Pin 3 -&gt; Pin 2
Pin 5 -&gt; Pin 5
&lt;/pre&gt;
(9pole SUB-D)


&lt;pre&gt;
serial  ser: (amiga/aros)  tty2 tty1USB0 (linux)  COM1 (windows)  (depends on the os being used) 
speed baud transfer rate 9600 38400     lower baud might be more successful 
data bits 8
stop bits 1
parity none
handshaking flow control - none xon/xoff (most likely)  rts/cts  dsr/dtr (pins not connected so should not work) 
&lt;/pre&gt;


*You cannot use compiled aros X86-64 bit software (when ready) on aros X86 32bit. PPC compiled software on X86 and so on. 
*68k is tested with the UAE emulator (WinUAE) but some tests are done on native 68000 based Amigas and others. 
*PPC support is very limited to certain devices. 


If you use the WBStartup, you have to delete the other icons in the folder (readme etc..) and you have to add in the Icon Tooltype the parameter DONOTWAIT

If you use user-startup instead, you need to add the attached command &quot;after assignment to LUA&quot;
C:WBRun DH1:Extras/Utility/WeatherBar/WeatherBar &gt;NIL:
Change the command to match your WeatherBar path.

&lt;pre&gt;
PATH sys:Utilities/WeatherBar ADD
run &gt;nil: lua:amilua weatherforecast.lua
&lt;/pre&gt;

To enter data your Country or City, ist with city_id numbers can be found [http://bulk.openweathermap.org/sample/city.list.json.gz here] or you need to go to [https://www.bbc.com/weather BBC Weather], once you type the name of your city or town in the appropriate tab, and press enter, the 7 numbers to be added in the &quot;WeatherBar&quot; will appear on the Browser url address bar above 


Unicode v16.0 emojis are not supported but [https://github.com/jens-maus/libcodesets codesets.library] provides 

&lt;pre&gt;
internally supported (hardcoded) charsets/codesets are: (conversions are possible from and to each codeset):

    AmigaPL – Polish (Amiga)
    Amiga-1251 – Cyrillic (Amiga)
    ISO-8859-1 – Western European
    ISO-8859-1+Euro – West European (with EURO)
    ISO-8859-2 – Central/East European
    ISO-8859-3 – South European
    ISO-8859-4 – North European
    ISO-8859-5 – Slavic languages
    ISO-8859-9 – Turkish
    ISO-8859-15 – West European II
    ISO-8859-16 – South-Eastern European
    KOI8-R – Russian
    UTF-8 – Unicode

In addition, external charset table files can be stored in LIBS:Charsets or loaded by an application from PROGDIR:Charsets. The charset files included with this distributions are:

    IBM866 – Cyrillic (cp866)
    ISO-8859-7 – Greek (LatinGreek)
    ISO-8859-10 – Nordic (Latin 6)
    windows-1250 – Central/East Europe (Windows)
    windows-1251 – Cyrillic (Windows)
    windows-1252 – West European (Windows)
&lt;/pre&gt;


Icaros 2.3 USB image needs a header stripped so it can work correctly 
 dd bs=512 skip=1 status=progress if=icaros_light_2-3-0_pendrive.bin of=/dev/sdxy &amp;&amp; sync


Scalos 
&lt;pre&gt;
-------------------------------
{ &quot;STRING&quot;,		&quot;ID/K,TEXT/K,SRC/K,TEXTPEN/K,HALIGN/K,STYLE/K,FONT/K,VALIGN/K&quot;,

HALIGN		LEFT | CENTER | RIGHT

VALIGN		TOP | CENTER | BOTTOM

STYLE		NORMAL | BOLD | ITALIC | BOLDITALIC

FONT		// font specification - format: &quot;fontname.font/size&quot;

-------------------------------
arguments for STRING SRC

&quot;diskstate&quot;,		
&quot;diskusage&quot;,		
&quot;diskusagefree&quot;,	
&quot;diskusageinuse&quot;,	
&quot;diskusagepercent&quot;,	
&quot;fibfilename&quot;,	
&quot;filecomment&quot;,	
&quot;filedate&quot;,		
&quot;fileprotection&quot;,	
&quot;filesize&quot;,		
&quot;filetime&quot;,		
&quot;filetypestring&quot;,	
&quot;iconname&quot;,		
&quot;linktarget&quot;,		
&quot;plugin&quot;	pluginname &lt;optional plugin arguments&gt;
&quot;versionstring&quot;,	
&quot;volumecreateddate&quot;,	
&quot;volumecreatedtime&quot;,	
&quot;volumeordevicename&quot;,	

-------------------------------

arguments for HIDE

&quot;novolumenode&quot;,	
&quot;isempty&quot; (some STRING)	

-------------------------------

all internal commands:

&quot;about&quot;,		
&quot;backdrop&quot;,		
&quot;cleanup&quot;,		
&quot;cleanupbyname&quot;,	
&quot;cleanupbydate&quot;,	
&quot;cleanupbysize&quot;,	
&quot;cleanupbytype&quot;,	
&quot;clearselection&quot;,	
&quot;clone&quot;,		
&quot;close&quot;,		
&quot;copy&quot;,		
&quot;cut&quot;,		
&quot;delete&quot;,		
&quot;emptytrashcan&quot;,	
&quot;executecommand&quot;,	
&quot;formatdisk&quot;,		
&quot;iconify&quot;,		
&quot;iconinfo&quot;,		
&quot;lastmsg&quot;,		
&quot;leaveout&quot;,		
&quot;makedir&quot;,		
&quot;open&quot;,		
&quot;parent&quot;,		
&quot;paste&quot;,		
&quot;putaway&quot;,		
&quot;quit&quot;,		
&quot;redraw&quot;,		
&quot;redrawall&quot;,		
&quot;rename&quot;,		
&quot;reset&quot;,		
&quot;selectall&quot;,		
&quot;showallfiles&quot;,	
&quot;showonlyicons&quot;,	
&quot;shutdown&quot;,		
&quot;sizetofit&quot;,		
&quot;snapshot&quot;,		
&quot;snapshotall&quot;,	
&quot;snapshotwindow&quot;,	
&quot;unsnapshot&quot;,		
&quot;update&quot;,		
&quot;updateall&quot;,		
&quot;viewbydate&quot;,		
&quot;viewbyicon&quot;,		
&quot;viewbysize&quot;,		
&quot;viewbytype&quot;,		
&quot;viewbytext&quot;,		
&lt;/pre&gt;


{{status|50%}}
{{BookCat}}</text>
      <sha1>6yov58guq6lc3c6u4d76nwj9fhew2cy</sha1>
    </revision>
  </page>
  <page>
    <title>Italian/Grammar/Nouns</title>
    <ns>0</ns>
    <id>14785</id>
    <revision>
      <id>4675731</id>
      <parentid>4369681</parentid>
      <timestamp>2026-10-12T13:27:19Z</timestamp>
      <contributor>
        <username>Luciérnaga de conocimiento</username>
        <id>3401314</id>
      </contributor>
      <origin>4675731</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="6005" sha1="ttpxmrzc6f8k5k5kerijbqkok7yonea" xml:space="preserve">== Gender ==
Italian nouns are either masculine or feminine.

As a general rule (with a few exceptions), male human beings are associated to masculine nouns; female human beings are associated to feminine nouns. Collective nouns, referring to a group of human beings of both genders, are usually masculine.

&lt;b&gt;Examples:&lt;/b&gt;
 Attore (''actor'') is masculine. (è maschile)
 Attrice (''actress'') is feminine. (è femminile)
 Maestro (male ''teacher'') is masculine.
 Maestra (female ''teacher'') is feminine.
 Bambini (''children'', a group of little boys) is masculine
 Bambini (''children'', a mixed group of little boys and girls) is masculine
 Bambine (''children'', a group of little girls) is feminine

&lt;b&gt;Exceptions (example):&lt;/b&gt;
 Persona (''person'' - man or woman) is feminine

Animals and things may be masculine or feminine, but there is no clear rule for this association. When you learn a new word, you should learn whether it is masculine or feminine.

&lt;b&gt;Examples:&lt;/b&gt;
 Pietra (''stone'') is feminine.
 Sasso (also ''stone'') is masculine.
 Topo (''mouse'') is masculine.
 Volpe (''fox'') is feminine.

The basic rule is that masculine singular nouns end with -o, feminine singular nouns end with -a. Most words follow this form, but this is not always the case.

*Masculine singular nouns can end in -a (rare)
*Feminine singular nouns can end in -o (rare)
*Both masculine and feminine nouns can end with -e
*Nouns ending in -à are always feminine
*Nouns ending in -è are always masculine
*Nouns ending in -i and in -ù are usually feminine
*Nouns ending in -ione are usually feminine
*Nouns ending in -mma are usually Greek in origin and masculine

&lt;b&gt;Examples&lt;/b&gt;
 Uomo (''man'') is masculine.
 Donna (''woman'') is feminine.
 Mano (''hand'') is feminine.
 Programma (''program'') is masculine.
 Cane (''dog'') is masculine.
 Pace (''peace'') is feminine.
 Città (''town'') is feminine.
 Crisi (''crisis'') is feminine.
 Virtù (''virtue'') is feminine.

==Plural==
In Italian, nouns are pluralized by a change in the last vowel.

In short:
* Nouns ending with -a are pluralized with -e if feminine (most common) or with -i if masculine.
* Nouns ending with -e or -o are pluralized with -i.
* Nouns ending with a stressed vowel, with -i or -u or with a consonant are invariant, the plural is the same as the singular.

Every case:
* Feminine in -a, plural in -e
* Feminine in -e, plural in -i
* Feminine in -o, plural in -i
* Feminine in -ie, plural in -ie
* Feminine in -i, plural also in -i
* Masculine in -a, plural in -i
* Masculine in -o, plural in -i (rarely, plural in -a; see Special Plurals below)
* Masculine in -e, plural in -i

&lt;b&gt;A basic example&lt;/b&gt;:
 [Il] ragazzo (''boy'') is masculine singular.
 - [I] ragazzi is the plural form.
 [La] ragazza (''girl'') is feminine singular.
 - [Le] ragazze is the plural form.

&lt;b&gt;Other examples&lt;/b&gt;:
 [Il] programma (''program'', masculine).  Plural: [i] programmi.
 [La] mano (''hand'', feminine).  Plural: [le] mani.
 [Il] cane (''dog'', masculine). Plural: [i] cani.
 [La] canzone (''song'', feminine). Plural: [le] canzoni.
 [La] crisi (''crisis'', feminine). Plural: [le] crisi.
 [La] città (''town'', feminine). Plural: [le] città.
 [Il] caffè (''coffee'', masculine). Plural: [i] caffè.
 [La] virtù (''virtue'', feminine). Plural: [le] virtù.
 [Il] gas (''gas''). Plural: [i] gas.

'''''Warning'''''.&lt;br&gt;
In some cases, plural feminine forms can be mistaken for singular masculine forms.

&lt;b&gt;Example of confusing forms.&lt;/b&gt;
 [Il] signore (''mister'') is masculine singular.
 - [I] signori is the plural form.
 [La] signora (''mrs'') is feminine singular.
 - [Le] signore is the plural form.

The problem here is that &quot;signore&quot; can refer to both one man or two (or more) women.  This problem is usually solved by taking the article into account.

==Special plurals==
A number of masculine nouns ending in -o have special plurals ending in -a; these special plurals switch to feminine gender. They are a remnant of the old Latin neutral gender.

&lt;b&gt;Examples of plurals in -a:&lt;/b&gt;
 [Il] braccio (''arm'', masculine). Plural: [le] braccia (feminine)
 [L'] uovo (''egg'', masculine). Plural: [le] uova (feminine)

Very few nouns have irregular plurals.

&lt;b&gt;Irregular plurals (example):&lt;/b&gt;
 Uomo (''man''), plural: uomini

Some nouns are invariant (the plural is the same as the singular) even if they end in -a, -e or -o. These nouns are usually originated by a shortening of longer names.

&lt;b&gt; Invariant plurals i -a, -e or -o (example):&lt;/b&gt;
 [La] moto (short for motocicletta) (''motorcycle''). Plural: [le] moto

Nouns ending with i+vowel in some cases miss one i in the plural (a rule for masculine nouns).

&lt;b&gt;Examples of plurals for nouns in -ia, -io:&lt;/b&gt;
 Camicia (''shirt'', fem.). Plural: camicie
 Doccia (''shower'', fem.). Plural: docce
 Arancia (''orange'', fem.). Plural: arance
 Inizio (''start'', masc.). Plural: inizi
 Negozio (''shop'', masc.). Plural: negozi
 Raggio (''ray'', masc.). Plural: raggi

Masculine nouns ending with -co, -go can have plurals ending with -chi, -ghi or -ci, -gi. Feminine nouns ending with -ca, -ga usually have plurals ending with -che, -ghe.

&lt;b&gt;Examples of plurals for nouns in -co, -go, -ca, -ga:&lt;/b&gt;
 Amico (''friend'', masc.). Plural: amici
 Arco (''arch'', masc.). Plural: archi
 Lago (''lake'', masc.). Plural: laghi
 Medico (''physician'', masc.). Plural: medici
 Amica (''friend'', fem.). Plural: amiche
 Barca (''boat'', fem.). Plural: barche
 Targa (''plate'', fem.). Plural: targhe

&lt;b&gt;Particular cases -cia and -gia&lt;/b&gt;&lt;br&gt;
Words ending with either -cia and -gia respect the following rule.

 Plural ends with -cie/-gie if the final letter before the suffix(cia/gia) is a vowel
 Plural ends with -ce/-ge if the final letter before the suffix is a consonant

If the stress falls on the i, the i always remains so, for instance, -cia makes the plural with -cie.

{{BookCat}}

[[de:Italienisch/Substantiv]]
[[es:Italiano/Gramática/Sustantivos]]
[[it:Italiano/Nome]]</text>
      <sha1>ttpxmrzc6f8k5k5kerijbqkok7yonea</sha1>
    </revision>
  </page>
  <page>
    <title>Italian/Grammar/Pronouns</title>
    <ns>0</ns>
    <id>14976</id>
    <revision>
      <id>4675734</id>
      <parentid>4660628</parentid>
      <timestamp>2026-10-12T13:36:50Z</timestamp>
      <contributor>
        <username>Luciérnaga de conocimiento</username>
        <id>3401314</id>
      </contributor>
      <origin>4675734</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="13404" sha1="pz6qom1vzmog6mwuion16p3h88zphi6" xml:space="preserve">== General ==

'''Personal pronouns''' are short words that replace persons or things: he, she, they, it, me, her etc.

Personal pronouns can play various roles. For instance, in the sentence ''I eat cake'', the word 'I' is a subject, but in the sentence ''That lion wants to eat me'', the word 'me' is the object.

Other pronouns (not personal) also replace nouns, with a more specific usage. For instance, ''this'' can replace a noun, with a meaning similar to ''it'' (or ''he''/''she''), e.g. in the sentence ''this is good for you''.

More information about pronouns, subjects etc. in English can be found in a different place. Here it is assumed that sufficient knowledge is available.

== Subject Personal Pronouns / Pronomi personali soggetto ==

&lt;b&gt;List of Subject Personal Pronouns:&lt;/b&gt;

Singular:
 io   - ''I''    - Note: no capital letter required
 tu   - ''you''  - Note: used to address one person
 egli - ''he''   - Note: not used in common talk
 lui  - ''he''   - Note: colloquial, normally it replaces ''egli''
 ella - ''she''  - Note: not used in common talk
 lei  - ''she''  - Note: colloquial, normally it replaces ''ella''
 esso - ''it''   - Note: masculine, little used in common speech
 essa - ''it''   - Note: feminine, little used in common speech
 lei  - ''you''  - Note: special use; sometimes with capital initial

Plural:
 noi  - ''we''
 voi  - ''you''  - Note: used to address two or more people
 Voi  - ''you''  - Note: same as 'voi' with lower case initial, but more formal (compare to 'Lei' in the singular)
 essi - ''they'' - Note: masculine
 esse - ''they'' - Note: feminine
 loro - ''they'' - Note: both masculine and feminine, colloquial, normally it replaces ''essi'' and ''esse''
 Loro - ''you''  - Note: special use, very uncommon, capital initial

The pronouns for the 1st person (singular: io, plural: noi) do not need special explanations.

The pronouns for the 2nd person (in English ''you'' both singular and plural) have a usage far more varied than in English.

'''Tu''' is addressed to one person only (singular) and is related to the older English ''thou''. It is felt to be informal. It is used with members of the same family (e.g. father, mother), with relatives (e.g. uncles), with children, with friends, and, in modern usage, with work colleagues. It is often used with boys and girls, and sometimes it is used with other persons in order to create a friendly atmosphere.

In the other cases (especially with grown-up people that are not friends or relatives) it is replaced by the pronoun '''lei''' (sometimes written with a capital letter). This pronoun literally means ''she'' and its usage is similar to English sentences including ''His/Her Majesty''.

For the same purpose the pronoun '''Ella''' can also be used. This is felt today as obsolete and is used rarely only in writing.

When two or more people are addressed, '''voi''' is used both in formal and informal language - that is with relatives, friends and other people. The plural for ''Lei'' does exist, it is '''Loro''' (capital initial), but it is nowadays little used. Instead of '''Loro''', '''Voi''' is used, which is the same as '''voi''' but with a capital letter. 

The pronouns for the singular 3rd person (in English ''he''/''she''/''it'') take into account the gender of the replaced noun, which in Italian can only be masculine or feminine.

When referring to a person, ''he'' is translated as '''egli''' (proper language, rarely used in speech) or '''lui''' (colloquial), ''she'' as '''ella''' (rare in speech) or '''lei''' (colloquial).

For animals or things, ''it'' is translated as '''esso''' when the noun is masculine (e.g. ''lago'', lake) and as '''essa''' when it is feminine (e.g. ''barca'', boat).

Plural also takes into account the gender, so ''they'' is translated as '''essi''' (masc.) or '''esse''' (fem.). In colloquial talk ''they'' is usually translated as '''loro'''.

It should also be remembered that pronouns are required less often than in English because verb forms change for every person.  It's usually better to say ''Sono felice'' ([I] am happy) than ''Io sono felice'' (I am happy).

== Missing subject pronouns ==
In many languages, including English, French and German, the subject of the verb must be expressed. Pronouns are widely used to avoid repeating nouns for this purpose.

In Italian the subject is often omitted, as the verb can give sufficient information. Personal subject pronouns are far less used than in English. They are used only when there is a need for clarity or a wish to emphasize the pronoun itself.

&lt;b&gt;Examples of missing subjects:&lt;/b&gt;
 Piove. ''It is raining.'' No need to mention ''it''.
 Vengo subito. ''I come soon''. No need to mention ''I''.
 Dove vai? ''Where are you going?'' No need to mention ''you''.
 Dove andiamo? ''Where are we going?'' No need to mention ''we''.

&lt;b&gt;Example of special uses:&lt;/b&gt;
 Credo di sì. ''I think so''.
 Io credo di sì. ''I do think so''. The pronoun makes the assertion more emphatic.

== Object Pronouns ==

{| cellspacing=&quot;10&quot; cellpadding=&quot;1&quot;
|- style=&quot;background: #DDD;{{Text default color}};&quot;
| valign=&quot;top&quot; |
{|
|-
| colspan=&quot;2&quot; align=&quot;center&quot; style=&quot;background: #CCC;{{Text default color}}; font-weight: bold;&quot; | Direct       
|-
| '''mi''' || me
|-
| '''ti''' || you
|-
| '''lo''' || him/it
|-
| '''la/La''' || her/it/you
|-
| '''si''' || himself/herself/itself/themselves
|-
| '''ci''' || us
|-
| '''vi/Vi''' || you
|-
| '''li/le''' || them
|}
| valign=&quot;top&quot; |
{|
|-
| colspan=&quot;2&quot; align=&quot;center&quot; style=&quot;background: #CCC;{{Text default color}}; font-weight: bold;&quot; | Indirect
|-
| '''mi''' || to me
|-
| '''ti''' || to you
|-
| '''gli''' || to him/it
|-
| '''le/Le''' || to her/it/you (formal)
|-
| '''si''' || to himself/herself/itself/themselves
|-
| '''ci''' || to us
|-
| '''vi/Vi''' || to you
|-
| '''loro''' || to them/you (formal)
|}
| valign=&quot;top&quot; |
{|
|-
| colspan=&quot;2&quot; align=&quot;center&quot; style=&quot;background: #CCC;{{Text default color}}; font-weight: bold;&quot; | Prepositional
|-
| '''me''' || me
|-
| '''te''' || you
|-
| '''lui/egli''' || him
|-
| '''esso''' || it
|-
| '''lei/ella''' || her
|-
| '''Lei/Ella''' || you (Formal)
|-
| '''essa''' || it
|-
| '''se''' || himself/herself/itself/themselves
|-
| '''noi''' || us
|-
| '''voi/Voi''' || you
|-
| '''loro/essi/esse''' || them
|}
|}
'''1) '''In most cases the direct and indirect object pronouns are placed before the verb: '''''Ti''' vedo. ''I see you. One exception: ''loro'' as an indirect object is placed after the verb. Additionally, a few forms of the verb always have pronouns after them, but then they are postfixed (ie. written onto it as one word). These forms are the infinitive (dropping the final 'e', eg. ''vederlo''), the gerund and the past participle (but only when used alone, not as part of a perfect tense). For example 'I want to see him' is ''Voglio veder'''lo''''' and not ''voglio lo vedere''. Note that stress does not change when pronouns are appended, ie. ''&lt;u&gt;scri&lt;/u&gt;vere'' =&gt; ''&lt;u&gt;scri&lt;/u&gt;verlo'' and not ''scri&lt;u&gt;ver&lt;/u&gt;lo''

'''2) '''Note that 'Lei' and 'Voi' when indicating formal 'you' are capitalised, regardless of inflection (eg. ''Perché non '''Le''' piace questo film?. ''Why don't you like this movie? ). This rule also applies to postfixed 'Lei' and 'Voi', but there they may also occur in lower case (eg. I can see you. ''Posso veder'''La'''. ''or ''Posso veder'''la'''. '')

'''3) '''When two pronouns (or a pronoun and ''ci'' (there) or ''ne'' (form there/it)) are combined, the order is ''indirect + direct + ci/ne''. You will never encounter all three together, but for example if you have an indirect and a direct object, then the indirect will precede the direct. Additionally the preceding form changes: 
{| cellspacing=&quot;10&quot; cellpadding=&quot;1&quot;
|- style=&quot;background: #DDD;{{Text default color}};&quot;
| valign=&quot;middle&quot; |
{|
|-
| colspan=&quot;2&quot; align=&quot;center&quot; style=&quot;background: #CCC;{{Text default color}}; font-weight: bold;&quot; | Direct       
|-
| mi =&gt; || '''me'''
|-
| ti =&gt; || '''te'''
|-
| si =&gt; || '''se'''
|-
| lo =&gt; || lo
|-
| gli =&gt; || '''glie'''
|-
| la/La =&gt; || la/La
|-
| le/Le =&gt; || le/Le
|-
| ci =&gt; || '''ce'''
|-
| vi/Vi =&gt; || '''ve/Ve'''
|-
| li =&gt; || li
|-
| le =&gt; || le
|-
| gli =&gt; || '''glie'''
|}
|}
For example, 'He gives it to us' is '''''Ce''' lo dà''. ''Glie'' is affixed to the next word, so 'I give it to him/them' becomes '''''Glie'''lo do. ''

Another example is the verb ''andarsene'', which means to go away (''andare-si-ne'', lit. to go (oneself) from the place). It is conjugated ''me ne vado, te ne vai, se ne và, etc.''

As you can see in ''andarsene'' the postfixed pronouns are all written as one word. This is the rule for all such combinations, ie. ''Voglio dartelo. ''I want to give it to you. (=''dare-ti-lo'')


'''4) '''The prepositional forms are obligatory after prepositions: ''Vado '''da lui''' stasera. ''I'm going to his place tonight. 

They are also placed after the verb instead of the direct object to emphasize the pronoun (eg. ''Ho visto '''te'''. ''It is you I saw. - This is somewhat uncommon). 

They can replace the indirect object in a similar fashion, which is much more common, but these pronouns require the preposition ''a'' when indicating the indirect object (eg. ''Lo dirò '''a te''' prima che lo dica '''agli altri'''. ''I'll tell you before I tell any of the others. - As you can see in this sentence, nouns such as ''gli altri'' also need the preposition ''a'')

== Possessive Pronouns ==
Possessives, like articles, must agree with the gender and number of the noun they modify.  Hence, ''mio zio'', my uncle, but ''mia zia'', my aunt.  So depending on what is being modified, the possessive pronouns are:

* Masc. sing.: mio, tuo, suo, nostro, vostro, loro
* Fem. sing.: mia, tua, sua, nostra, vostra, loro
* Masc. pl.: miei, tuoi, suoi, nostri, vostri, loro
* Fem. pl.: mie, tue, sue, nostre, vostre, loro

In most cases the possessive adjective must be used ''with'' the definite article:

* Ho perso '''la mia''' penna. (I've lost my pen.)
* Mi piace '''il mio''' lavoro. (I like my job.)
* Hanno rubato '''la mia''' automobile! (They've stolen my car!)

The only exception is when the possessive refers to a family member in the singular:

* Sara è '''mia''' sorella (Sarah is my sister.)
* Questa penna è di '''mia''' zia. (This pen is my aunt's.)

But in the plural:

* '''Le mie''' zie sono vecchie (My aunts are old)

However, 'loro' always takes the definite article (also note that 'loro' does not change, for example the female form is 'loro', not 'lora' or something like that):

* '''La loro''' sorella è malata (Their sister is ill)

Personal pronouns can also be used on their own: 

* Questa macchina è '''la mia'''. (This car is mine)

To say 'one of my', 'one of your' etc. you use a personal pronoun with the indefinite article: 

* '''Un mio''' figlio è malato (One of my sons is ill)

And finally, possessives may be placed behind the noun it refers to in poetical language and specific expressions. If the definite article is used at all, it remains before the noun. 

* '''(Gli)''' affari '''tuoi''' (Your (own) business)
* Fatti gli affari '''tuoi'''! (Mind you own business!)

== Relative Pronouns ==
Relative pronouns are just pronouns, like those before this section but they refer to something relative to the context of
the sentence or the situation. the pronoun &quot;I&quot; will always refer to myself while the pronoun &quot;she&quot; will always refer to some &quot;her&quot;. A Relative pronoun can refer to a person, a thing or a situation. In English these pronouns are who, which, that, whom, where.

* Pronoun &lt;b&gt;che&lt;/b&gt;: this pronoun is used when you use which, who, and that.

* Pronouns &lt;b&gt;il quale, la quale, i quali, le quali&lt;/b&gt;: this pronoun &quot;quale&quot; is like the previous one but it also indicates the gender and number:
** il quale: masculine singular
** la quale: feminine singular
** i quali: masculine plural
** le quali: feminine plural

* Pronoun &lt;b&gt;cui&lt;/b&gt;: this pronouns introduces indirect objects (this means all those objects that need a preposition before it): “Headphone is the instrument (with) which you can hear music with” this pronoun needs “with” to work.

* Extra pronouns: &lt;b&gt;chi, colui, colei, coloro, ciò, chiunque, quanto,&lt;/b&gt; etc... words that serve the purpose of a pronoun.

== Demonstrative Pronouns ==
There are only two demonstrative pronouns: &lt;b&gt;questo&lt;/b&gt; and &lt;b&gt;quello&lt;/b&gt;. Pay attention to how these pronouns change in gender and number.

* &lt;b&gt;questo, questa, questi, queste&lt;/b&gt;=this, these
* &lt;b&gt;quello, quella, quelli, quelle&lt;/b&gt;=that, those

'Questo' and related forms always use their full form. 'Quello' uses the full form as described above when on their own (for example, ''Questo è rotto.'' This one is broken.), but has a shorter form when used with a noun (''Quel problema non si può risolvere.'' That problem can't be solved.)

The form is dependent on the article you would use with the noun: 
* ''il'' =&gt; '''que''l'''''
* ''lo'' =&gt; '''quel''lo'''''
* ''la'' =&gt; '''quel''la'''''
* ''l''' =&gt; '''quel''l''''''
* ''i'' =&gt; '''que''i'''''
* ''le'' =&gt; '''quel''le'''''
* ''gli'' =&gt; '''que''gli'''''
For example, you would say ''gli uomini'', so you say ''quegli uomini''. These forms are also used when followed by a relative pronoun: ''Quel che voglio'' = What I want / The one that I want / That which I want. 

{{BookCat}}</text>
      <sha1>pz6qom1vzmog6mwuion16p3h88zphi6</sha1>
    </revision>
  </page>
  <page>
    <title>Koine Greek</title>
    <ns>0</ns>
    <id>16226</id>
    <revision>
      <id>4675761</id>
      <parentid>4675634</parentid>
      <timestamp>2026-10-12T19:08:49Z</timestamp>
      <contributor>
        <username>It-is-Truly-Meet</username>
        <id>3624460</id>
      </contributor>
      <minor />
      <comment>I would like to include examples such as &quot;ἡμεῖς ἀγαπῶμεν ὅτι αὐτὸς πρῶτος ἠγάπησεν ἡμᾶς&quot; in the adjectives section; readers won't understand the use of pronouns in said lesson if they are introduced afterwards.</comment>
      <origin>4675761</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="5897" sha1="l8ors6vb3so6qu4wotsidkhgu9m2cs8" xml:space="preserve">{{print version}}
{{Category 4 Language}}
&lt;br clear=&quot;all&quot;&gt;
[[File:Alexander and Bucephalus - Battle of Issus mosaic - Museo Archeologico Nazionale - Naples BW.jpg|center|300px|Naples, National Archaeological Museum, Alexander Mosaic, Battle of Isus]]
{{Book title|{{BOOKNAME}}|An introduction to the Koine Greek language.}}
:''Χαίρειν ἐπὶ τῇ εἰσόδῳ εἰς τὸν τῆς Κοινῆς Ἑλληνικῆς λόγον παιδευτικόν!''
This text serves as an introduction to '''Koine Greek''', also known as '''Biblical Greek''', appropriate for a two year course. A fluent knowledge of English is presumed.
:''For other Greek languages, click [[Subject:Greek language|here]].''

==Preface==

:[[/A Historical Setting for Koine Greek/]]

==Pronunciation==
:[[/Alphabet, Pronunciation, and Punctuation/]]
:[[/Additional Information: Accents/]]
:[[/Exercise in Pronunciation: John 1:1-5/]]

==Nouns, Pronouns, and Adjectives==
:[[/Introduction to Nouns/]]
:[[/Declining 1st and 2nd Declension Nouns/]]
:[[/Declining 3rd Declension Nouns/]]
:[[/Prepositions and εἰμί/]]
:[[/Pronouns/]]
:[[/Adjectives/]]

==Finite Indicative Verb Forms==
:[[/Accents and Morae/]]
:[[/Introduction to Finite Indicative Verbs/]]
:[[/Contract Verbs/]]

===The Future Tense=== 
:[[/Future Active Indicative/]]
:[[/Future Middle Indicative/]]
:[[/Future Passive Indicative/]]

===The Imperfect Tense=== 
:[[/Imperfect Active/Mediopassive Indicative/]]

===The Aorist Tense===
:[[/2nd Aorist Active Indicative/]]
:[[/2nd Aorist Middle Indicative/]]
:[[/1st Aorist Active Indicative/]]
:[[/1st Aorist Middle Indicative/]]
:[[/Aorist Passive Indicative/]]

===The Perfect Tense===
:[[/Perfect Active Indicative/]]
:[[/Perfect Middle/Passive Indicative/]]

==Finite Non-Indicative Verb Forms==
===The Subjunctive===
:[[/Introduction to the Subjunctive Mood/]]
:[[/Present Active Subjunctive/]]
:[[/Present Middle/Passive Subjunctive/]]
:[[/1st Aorist Active Subjunctive/]]
:[[/1st Aorist Middle Subjunctive/]]
:[[/1st Aorist Passive Subjunctive/]]
:[[/2nd Aorist Active Subjunctive/]]
:[[/2nd Aorist Middle Subjunctive/]]
:[[/2nd Aorist Passive Subjunctive/]]
:[[/Perfect Active Subjunctive/]]
:[[/Perfect Middle Subjunctive/]]
:[[/Perfect Passive Subjunctive/]]

===The Imperative===
:[[/Introduction to the Imperative Mood/]]
:[[/Present Active Imperative (ω conjugation)/]]
:[[/Present Middle/Passive Imperative (ω conjugation)/]]
:[[/1st Aorist Active Imperative (ω conjugation)/]]
:[[/1st Aorist Middle Imperative (ω conjugation)/]]
:[[/2nd Aorist Active Imperative (ω conjugation)/]]
:[[/2nd Aorist Middle Imperative (ω conjugation)/]]
:[[/2nd Aorist Passive Imperative (ω conjugation)/]]
:[[/Perfect Active Imperative (ω conjugation)/]]
:[[/Perfect Middle Imperative (ω conjugation)/]]
:[[/Perfect Passive Imperative (ω conjugation)/]]
:[[/Ἡ Κυριακὴ Προσευχή/]]

===The Optative===
:[[/Introduction to the Optative Mood/]]
:[[/Present Active Optative (ω conjugation)/]]
:[[/Present Middle/Passive Optative (ω conjugation)/]]
:[[/1st Aorist Active Optative (ω conjugation)/]]
:[[/1st Middle Optative (ω conjugation)/]]
:[[/2nd Aorist Active Optative (ω conjugation)/]]
:[[/2nd Aorist Middle Optative (ω conjugation)/]]
:[[/2nd Aorist Passive Optative (ω conjugation)/]]
:[[/Future Active Optative (ω conjugation)/]]
:[[/Future Middle Optative (ω conjugation)/]]
:[[/Future Passive Optative (ω conjugation)/]]
:[[/Perfect Active Optative (ω conjugation)/]]
:[[/Perfect Middle Optative (ω conjugation)/]]
:[[/Perfect Passive Optative (ω conjugation)/]]
:[[/Πράξεις ΙΖ/]]

==The -μι Conjugation==
:[[/Present Active Imperative (μι conjugation)/]]
:[[/Present Middle/Passive Imperative (μι conjugation)/]]
:[[/1st Aorist Active Imperative (μι conjugation)/]]
:[[/1st Aorist Middle Imperative (μι conjugation)/]]
:[[/2nd Aorist Active Imperative(μι conjugation)/]]
:[[/2nd Aorist Passive Imperative (μι conjugation)/]]
:[[/Present Active Optative (μι conjugation)/]]
:[[/Present Middle/Passive Optative (μι conjugation)/]]
:[[/1st Aorist Active Optative (μι conjugation)/]]
:[[/1st Aorist Middle Optative (μι conjugation)/]]
:[[/2nd Aorist Active Optative (μι conjugation)/]]
:[[/2nd Aorist Passive Optative (μι conjugation)/]]

==Non-finite Verbal Forms==
===The Participle===
:[[/Introduction to Participles/]]
:[[/Present Participle/]]
:[[/Aorist Participle/]]
:[[/Perfect Participle/]]
:[[/Future Participle/]]
===The Infinitive===
:[[/Introduction to Infinitives/]]
:[[/Present Infinitive/]]
:[[/Aorist Infinitive/]]
:[[/Perfect Infinitive/]]

==Advanced Syntax==
===Adverbs===
:[[/Overview of Adverbs/]]

===Particles===
:[[/Overview of Particles/]]

===Conjunctions===
:[[/Coordinating (Paratactic) Conjunctions/]]
:[[/Subordinating (Hypotactic) Conjunctions/]]
:[[/Conditional Clauses/]]

===The Genitive Absolute===
:[[/The Genitive Absolute/]]

== About this Book ==
:[[Koine Greek/Authors|Authors]]

== External Links ==
{{Wikipedia}}
{{Wiktionary|Category:Ancient Greek language}}
{{Wikivoyage|Ancient Greece}}

* For more free language-learning information on Koine Greek (used in the New Testament and by the army of Alexander the Great), go to Textkit's website at http://www.textkit.com.
* Other great sources are http://ntgateway.com/ and https://pressbooks.pub/ancientgreek/front-matter/introduction/.
* For a comprehensive overview of Ancient Greek grammar, see [https://dcc.dickinson.edu/grammar/goodell/ Dickinson College Commentaries].
* [http://www.wikichristian.org/Koine_Greek Koine Greek] plus [http://www.wikichristian.org/Koine_Greek:_Dictionary Dictionary] at [http://www.wikichristian.org/Main_Page WikiChristian]
* [https://www.textkit.com/t/typing-ancient-greek/20575/ Typing Ancient Greek]

{{Shelves|Greek language}}
{{alphabetical|K}}
{{status|25%}}
__NOTOC__ __NOEDITSECTION__</text>
      <sha1>l8ors6vb3so6qu4wotsidkhgu9m2cs8</sha1>
    </revision>
    <revision>
      <id>4675769</id>
      <parentid>4675761</parentid>
      <timestamp>2026-10-13T00:59:01Z</timestamp>
      <contributor>
        <username>It-is-Truly-Meet</username>
        <id>3624460</id>
      </contributor>
      <minor />
      <origin>4675769</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="6227" sha1="rqs0klsgaggh75qln361qzfc44o35pp" xml:space="preserve">{{print version}}
{{Category 4 Language}}
&lt;br clear=&quot;all&quot;&gt;
[[File:Alexander and Bucephalus - Battle of Issus mosaic - Museo Archeologico Nazionale - Naples BW.jpg|center|300px|Naples, National Archaeological Museum, Alexander Mosaic, Battle of Isus]]
{{Book title|{{BOOKNAME}}|An introduction to the Koine Greek language.}}
:''Χαίρειν ἐπὶ τῇ εἰσόδῳ εἰς τὸν τῆς Κοινῆς Ἑλληνικῆς λόγον παιδευτικόν!''
This text serves as an introduction to '''Koine Greek''', also known as '''Biblical Greek''', appropriate for a two year course. A fluent knowledge of English is presumed.
:''For other Greek languages, click [[Subject:Greek language|here]].''

==Preface==

:[[/A Historical Setting for Koine Greek/]]

==Pronunciation==
:[[/Alphabet, Pronunciation, and Punctuation/]]
:[[/Additional Information: Accents/]]
:[[/Exercise in Pronunciation: John 1:1-5/]]

==Nouns, Pronouns, and Adjectives==
:[[/Introduction to Nouns/]]
:[[/Declining 1st and 2nd Declension Nouns/]]
:[[/Declining 3rd Declension Nouns/]]
:[[/Prepositions and εἰμί/]]
:[[/Pronouns/]]
:[[/Adjectives/]]

==Finite Indicative Verb Forms==
:[[/Accents and Morae/]]
:[[/Introduction to Finite Indicative Verbs/]]
:[[/Contract Verbs/]]

===The Future Tense=== 
:[[/Future Active Indicative/]]
:[[/Future Middle Indicative/]]
:[[/Future Passive Indicative/]]

===The Imperfect Tense=== 
:[[/Imperfect Active/Mediopassive Indicative/]]

===The Aorist Tense===
:[[/2nd Aorist Active Indicative/]]
:[[/2nd Aorist Middle Indicative/]]
:[[/1st Aorist Active Indicative/]]
:[[/1st Aorist Middle Indicative/]]
:[[/Aorist Passive Indicative/]]

===The Perfect Tense===
:[[/Perfect Active Indicative/]]
:[[/Perfect Middle/Passive Indicative/]]

==Finite Non-Indicative Verb Forms==
===The Subjunctive===
:[[/Introduction to the Subjunctive Mood/]]
:[[/Present Active Subjunctive/]]
:[[/Present Middle/Passive Subjunctive/]]
:[[/1st Aorist Active Subjunctive/]]
:[[/1st Aorist Middle Subjunctive/]]
:[[/1st Aorist Passive Subjunctive/]]
:[[/2nd Aorist Active Subjunctive/]]
:[[/2nd Aorist Middle Subjunctive/]]
:[[/2nd Aorist Passive Subjunctive/]]
:[[/Perfect Active Subjunctive/]]
:[[/Perfect Middle Subjunctive/]]
:[[/Perfect Passive Subjunctive/]]

===The Imperative===
:[[/Introduction to the Imperative Mood/]]
:[[/Present Active Imperative (ω conjugation)/]]
:[[/Present Middle/Passive Imperative (ω conjugation)/]]
:[[/1st Aorist Active Imperative (ω conjugation)/]]
:[[/1st Aorist Middle Imperative (ω conjugation)/]]
:[[/2nd Aorist Active Imperative (ω conjugation)/]]
:[[/2nd Aorist Middle Imperative (ω conjugation)/]]
:[[/2nd Aorist Passive Imperative (ω conjugation)/]]
:[[/Perfect Active Imperative (ω conjugation)/]]
:[[/Perfect Middle Imperative (ω conjugation)/]]
:[[/Perfect Passive Imperative (ω conjugation)/]]
:[[/Ἡ Κυριακὴ Προσευχή/]]

===The Optative===
:[[/Introduction to the Optative Mood/]]
:[[/Present Active Optative (ω conjugation)/]]
:[[/Present Middle/Passive Optative (ω conjugation)/]]
:[[/1st Aorist Active Optative (ω conjugation)/]]
:[[/1st Middle Optative (ω conjugation)/]]
:[[/2nd Aorist Active Optative (ω conjugation)/]]
:[[/2nd Aorist Middle Optative (ω conjugation)/]]
:[[/2nd Aorist Passive Optative (ω conjugation)/]]
:[[/Future Active Optative (ω conjugation)/]]
:[[/Future Middle Optative (ω conjugation)/]]
:[[/Future Passive Optative (ω conjugation)/]]
:[[/Perfect Active Optative (ω conjugation)/]]
:[[/Perfect Middle Optative (ω conjugation)/]]
:[[/Perfect Passive Optative (ω conjugation)/]]
:[[/Πράξεις ΙΖ/]]

==The -μι Conjugation==
:[[/Present Active Imperative (μι conjugation)/]]
:[[/Present Middle/Passive Imperative (μι conjugation)/]]
:[[/1st Aorist Active Imperative (μι conjugation)/]]
:[[/1st Aorist Middle Imperative (μι conjugation)/]]
:[[/2nd Aorist Active Imperative(μι conjugation)/]]
:[[/2nd Aorist Passive Imperative (μι conjugation)/]]
:[[/Present Active Optative (μι conjugation)/]]
:[[/Present Middle/Passive Optative (μι conjugation)/]]
:[[/1st Aorist Active Optative (μι conjugation)/]]
:[[/1st Aorist Middle Optative (μι conjugation)/]]
:[[/2nd Aorist Active Optative (μι conjugation)/]]
:[[/2nd Aorist Passive Optative (μι conjugation)/]]

==Non-finite Verbal Forms==
===The Participle===
:[[/Introduction to Participles/]]
:[[/Present Participle/]]
:[[/Aorist Participle/]]
:[[/Perfect Participle/]]
:[[/Future Participle/]]
===The Infinitive===
:[[/Introduction to Infinitives/]]
:[[/Present Infinitive/]]
:[[/Aorist Infinitive/]]
:[[/Perfect Infinitive/]]

==Advanced Syntax==
===Adverbs===
:[[/Overview of Adverbs/]]

===Particles===
:[[/Overview of Particles/]]

===Conjunctions===
:[[/Coordinating (Paratactic) Conjunctions/]]
:[[/Subordinating (Hypotactic) Conjunctions/]]
:[[/Conditional Clauses/]]

===The Genitive Absolute===
:[[/The Genitive Absolute/]]

== About this Book ==
:[[Koine Greek/Authors|Authors]]

== External Links ==
{{Wikipedia}}
{{Wiktionary|Category:Ancient Greek language}}
{{Wikivoyage|Ancient Greece}}

* For more free language-learning information on Koine Greek (used in the New Testament and by the army of Alexander the Great), go to Textkit's website at http://www.textkit.com.
* Other great sources are http://ntgateway.com/ and https://pressbooks.pub/ancientgreek/front-matter/introduction/.
* For a comprehensive overview of Ancient Greek grammar, see [https://dcc.dickinson.edu/grammar/goodell/ Dickinson College Commentaries].
* [http://www.wikichristian.org/Koine_Greek Koine Greek] plus [http://www.wikichristian.org/Koine_Greek:_Dictionary Dictionary] at [http://www.wikichristian.org/Main_Page WikiChristian]
* [https://www.textkit.com/t/typing-ancient-greek/20575/ Typing Ancient Greek]

===Literature===
* [https://archive.org/details/newtestamentino00west/page/6/mode/2up/ The Greek New Testament]
* [https://archive.org/details/septuagintversio1879bren/page/n15/mode/2up/ The Septuagint]
*[https://www.perseus.tufts.edu/hopper/text?doc=Perseus%3Atext%3A2008.01.0641%3Abook%3D1/ The Meditations by Marcus Aurelius]

{{Shelves|Greek language}}
{{alphabetical|K}}
{{status|25%}}
__NOTOC__ __NOEDITSECTION__</text>
      <sha1>rqs0klsgaggh75qln361qzfc44o35pp</sha1>
    </revision>
    <revision>
      <id>4675770</id>
      <parentid>4675769</parentid>
      <timestamp>2026-10-13T01:02:08Z</timestamp>
      <contributor>
        <username>It-is-Truly-Meet</username>
        <id>3624460</id>
      </contributor>
      <minor />
      <comment>Broken links were fixed.</comment>
      <origin>4675770</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="6223" sha1="dwv0tkf2m83wn2gdsupustjcyodgxmr" xml:space="preserve">{{print version}}
{{Category 4 Language}}
&lt;br clear=&quot;all&quot;&gt;
[[File:Alexander and Bucephalus - Battle of Issus mosaic - Museo Archeologico Nazionale - Naples BW.jpg|center|300px|Naples, National Archaeological Museum, Alexander Mosaic, Battle of Isus]]
{{Book title|{{BOOKNAME}}|An introduction to the Koine Greek language.}}
:''Χαίρειν ἐπὶ τῇ εἰσόδῳ εἰς τὸν τῆς Κοινῆς Ἑλληνικῆς λόγον παιδευτικόν!''
This text serves as an introduction to '''Koine Greek''', also known as '''Biblical Greek''', appropriate for a two year course. A fluent knowledge of English is presumed.
:''For other Greek languages, click [[Subject:Greek language|here]].''

==Preface==

:[[/A Historical Setting for Koine Greek/]]

==Pronunciation==
:[[/Alphabet, Pronunciation, and Punctuation/]]
:[[/Additional Information: Accents/]]
:[[/Exercise in Pronunciation: John 1:1-5/]]

==Nouns, Pronouns, and Adjectives==
:[[/Introduction to Nouns/]]
:[[/Declining 1st and 2nd Declension Nouns/]]
:[[/Declining 3rd Declension Nouns/]]
:[[/Prepositions and εἰμί/]]
:[[/Pronouns/]]
:[[/Adjectives/]]

==Finite Indicative Verb Forms==
:[[/Accents and Morae/]]
:[[/Introduction to Finite Indicative Verbs/]]
:[[/Contract Verbs/]]

===The Future Tense=== 
:[[/Future Active Indicative/]]
:[[/Future Middle Indicative/]]
:[[/Future Passive Indicative/]]

===The Imperfect Tense=== 
:[[/Imperfect Active/Mediopassive Indicative/]]

===The Aorist Tense===
:[[/2nd Aorist Active Indicative/]]
:[[/2nd Aorist Middle Indicative/]]
:[[/1st Aorist Active Indicative/]]
:[[/1st Aorist Middle Indicative/]]
:[[/Aorist Passive Indicative/]]

===The Perfect Tense===
:[[/Perfect Active Indicative/]]
:[[/Perfect Middle/Passive Indicative/]]

==Finite Non-Indicative Verb Forms==
===The Subjunctive===
:[[/Introduction to the Subjunctive Mood/]]
:[[/Present Active Subjunctive/]]
:[[/Present Middle/Passive Subjunctive/]]
:[[/1st Aorist Active Subjunctive/]]
:[[/1st Aorist Middle Subjunctive/]]
:[[/1st Aorist Passive Subjunctive/]]
:[[/2nd Aorist Active Subjunctive/]]
:[[/2nd Aorist Middle Subjunctive/]]
:[[/2nd Aorist Passive Subjunctive/]]
:[[/Perfect Active Subjunctive/]]
:[[/Perfect Middle Subjunctive/]]
:[[/Perfect Passive Subjunctive/]]

===The Imperative===
:[[/Introduction to the Imperative Mood/]]
:[[/Present Active Imperative (ω conjugation)/]]
:[[/Present Middle/Passive Imperative (ω conjugation)/]]
:[[/1st Aorist Active Imperative (ω conjugation)/]]
:[[/1st Aorist Middle Imperative (ω conjugation)/]]
:[[/2nd Aorist Active Imperative (ω conjugation)/]]
:[[/2nd Aorist Middle Imperative (ω conjugation)/]]
:[[/2nd Aorist Passive Imperative (ω conjugation)/]]
:[[/Perfect Active Imperative (ω conjugation)/]]
:[[/Perfect Middle Imperative (ω conjugation)/]]
:[[/Perfect Passive Imperative (ω conjugation)/]]
:[[/Ἡ Κυριακὴ Προσευχή/]]

===The Optative===
:[[/Introduction to the Optative Mood/]]
:[[/Present Active Optative (ω conjugation)/]]
:[[/Present Middle/Passive Optative (ω conjugation)/]]
:[[/1st Aorist Active Optative (ω conjugation)/]]
:[[/1st Middle Optative (ω conjugation)/]]
:[[/2nd Aorist Active Optative (ω conjugation)/]]
:[[/2nd Aorist Middle Optative (ω conjugation)/]]
:[[/2nd Aorist Passive Optative (ω conjugation)/]]
:[[/Future Active Optative (ω conjugation)/]]
:[[/Future Middle Optative (ω conjugation)/]]
:[[/Future Passive Optative (ω conjugation)/]]
:[[/Perfect Active Optative (ω conjugation)/]]
:[[/Perfect Middle Optative (ω conjugation)/]]
:[[/Perfect Passive Optative (ω conjugation)/]]
:[[/Πράξεις ΙΖ/]]

==The -μι Conjugation==
:[[/Present Active Imperative (μι conjugation)/]]
:[[/Present Middle/Passive Imperative (μι conjugation)/]]
:[[/1st Aorist Active Imperative (μι conjugation)/]]
:[[/1st Aorist Middle Imperative (μι conjugation)/]]
:[[/2nd Aorist Active Imperative(μι conjugation)/]]
:[[/2nd Aorist Passive Imperative (μι conjugation)/]]
:[[/Present Active Optative (μι conjugation)/]]
:[[/Present Middle/Passive Optative (μι conjugation)/]]
:[[/1st Aorist Active Optative (μι conjugation)/]]
:[[/1st Aorist Middle Optative (μι conjugation)/]]
:[[/2nd Aorist Active Optative (μι conjugation)/]]
:[[/2nd Aorist Passive Optative (μι conjugation)/]]

==Non-finite Verbal Forms==
===The Participle===
:[[/Introduction to Participles/]]
:[[/Present Participle/]]
:[[/Aorist Participle/]]
:[[/Perfect Participle/]]
:[[/Future Participle/]]
===The Infinitive===
:[[/Introduction to Infinitives/]]
:[[/Present Infinitive/]]
:[[/Aorist Infinitive/]]
:[[/Perfect Infinitive/]]

==Advanced Syntax==
===Adverbs===
:[[/Overview of Adverbs/]]

===Particles===
:[[/Overview of Particles/]]

===Conjunctions===
:[[/Coordinating (Paratactic) Conjunctions/]]
:[[/Subordinating (Hypotactic) Conjunctions/]]
:[[/Conditional Clauses/]]

===The Genitive Absolute===
:[[/The Genitive Absolute/]]

== About this Book ==
:[[Koine Greek/Authors|Authors]]

== External Links ==
{{Wikipedia}}
{{Wiktionary|Category:Ancient Greek language}}
{{Wikivoyage|Ancient Greece}}

* For more free language-learning information on Koine Greek (used in the New Testament and by the army of Alexander the Great), go to Textkit's website at http://www.textkit.com.
* Other great sources are http://ntgateway.com/ and https://pressbooks.pub/ancientgreek/front-matter/introduction/.
* For a comprehensive overview of Ancient Greek grammar, see [https://dcc.dickinson.edu/grammar/goodell/ Dickinson College Commentaries].
* [http://www.wikichristian.org/Koine_Greek Koine Greek] plus [http://www.wikichristian.org/Koine_Greek:_Dictionary Dictionary] at [http://www.wikichristian.org/Main_Page WikiChristian]
* [https://www.textkit.com/t/typing-ancient-greek/20575/ Typing Ancient Greek]

===Literature===
* [https://archive.org/details/newtestamentino00west/page/6/mode/2up The Greek New Testament]
* [https://archive.org/details/septuagintversio1879bren/page/n15/mode/2up The Septuagint]
*[http://www.perseus.tufts.edu/hopper/text?doc=Perseus%3Atext%3A2008.01.0641%3Abook%3D1 The Meditations by Marcus Aurelius]

{{Shelves|Greek language}}
{{alphabetical|K}}
{{status|25%}}
__NOTOC__ __NOEDITSECTION__</text>
      <sha1>dwv0tkf2m83wn2gdsupustjcyodgxmr</sha1>
    </revision>
  </page>
  <page>
    <title>Talk:Koine Greek</title>
    <ns>1</ns>
    <id>17299</id>
    <revision>
      <id>4675768</id>
      <parentid>4672497</parentid>
      <timestamp>2026-10-13T00:28:31Z</timestamp>
      <contributor>
        <username>It-is-Truly-Meet</username>
        <id>3624460</id>
      </contributor>
      <comment>/* Quotations from the GNT */ new section</comment>
      <origin>4675768</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2403" sha1="9pztibsuu328sncg1bexgizx41e5r3h" xml:space="preserve">{{WikiProject Languages|priority=low}}

[http://www.perseus.tufts.edu/cgi-bin/ptext?doc=Perseus%3Atext%3A1999.04.0007;layout=;loc=1;query=toc Text of Greek Grammar]

==Untitled==
Can you give a little framework of how you want the rest to be structured?

== Pronounciation ==

I must refer to the wikipedia article regarding the pronounciation. The wikipedia article stresses that the changes in pronounciation have affected Koinè strongly, as one can find in the corresponding literature. What you describe here, is the classical pronounciation. Maybe you should review this chapter.[[Special:Contributions/2A02:587:C208:FEC2:CFC:F5F6:78B1:8F69|2A02:587:C208:FEC2:CFC:F5F6:78B1:8F69]] ([[User talk:2A02:587:C208:FEC2:CFC:F5F6:78B1:8F69|discuss]]) 09:40, 8 July 2022 (UTC)

== The Optative in Koine ==
The following text is from Wikipedia:
 Later, as [[wikipedia:Koine_Greek|Koine Greek]] emerged following the conquests of [[wikipedia:Alexander_the_Great|Alexander the Great]] c. 333 BC, the use of the optative began to wane among many Greek writers.&lt;br&gt;&lt;br&gt;In the New Testament, the optative still occurs (mainly in Luke, Acts, and Paul), but it is rare. There are about 68 optatives among the 28,121 verbs in the New Testament – about 0.24%. Fifteen of these are the stereotyped phrase {{lang|grc|μὴ γένοιτο}} &quot;may it not happen!&quot; (or &quot;God forbid!&quot;). It has been suggested that the frequent use of the optative in benedictions in the New Testament was due to a desire to make the language of such benedictions formal and thus appropriate for religious purposes.&lt;br&gt;&lt;br&gt;In modern Greek the optative mood has entirely disappeared, leaving only the indicative, subjunctive and imperative moods.
Why should there be a whole section dedicated to the optative if it was mostly fossilized in certain expressions? The optative could be briefly covered in one lesson, though a full description of the optative should be reversed for the [[Ancient Greek]] Wikibook. [[User:It-is-Truly-Meet|It-is-Truly-Meet]] ([[User talk:It-is-Truly-Meet|discuss]] • [[Special:Contributions/It-is-Truly-Meet|contribs]]) 21:49, 26 September 2026 (UTC)

== Quotations from the GNT ==
This book should use KJV translations only for consistency. [[User:It-is-Truly-Meet|It-is-Truly-Meet]] ([[User talk:It-is-Truly-Meet|discuss]] • [[Special:Contributions/It-is-Truly-Meet|contribs]]) 00:28, 13 October 2026 (UTC)</text>
      <sha1>9pztibsuu328sncg1bexgizx41e5r3h</sha1>
    </revision>
  </page>
  <page>
    <title>Robotics/Design Basics/Electronic Components</title>
    <ns>0</ns>
    <id>19247</id>
    <revision>
      <id>4675811</id>
      <parentid>3142733</parentid>
      <timestamp>2026-10-13T09:23:54Z</timestamp>
      <contributor>
        <username>LokiZhan</username>
        <id>3628315</id>
      </contributor>
      <minor />
      <comment>Expanded the chapter with detailed explanations of electronic components, power systems, motor control and thermal management.</comment>
      <origin>4675811</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="12628" sha1="jxlyvsy0757bqbg7r9d5i8qrdvhbh4g" xml:space="preserve">
Electronic components in a robot perform three main tasks: supplying electrical power, processing information, and controlling physical movement. The selection of these components depends on the robot's operating voltage, current requirements, control method, size, and working environment.

Unlike a simple electronic circuit, a robot often combines low-power digital electronics with motors and other loads that draw relatively large or rapidly changing currents. These different requirements must be considered when designing the electronic system.

== Basic Electronics ==

A basic understanding of voltage, current, resistance, and electrical power is necessary before selecting components for a robot.

Voltage is the electrical potential difference between two points, while current describes the flow of electric charge. Resistance limits current flow, and electrical power describes the rate at which electrical energy is transferred or converted.

For a resistive load, Ohm's law is expressed as:

:&lt;math&gt;V=IR&lt;/math&gt;

where &lt;math&gt;V&lt;/math&gt; is voltage in volts, &lt;math&gt;I&lt;/math&gt; is current in amperes, and &lt;math&gt;R&lt;/math&gt; is resistance in ohms.

Electrical power can be calculated as:

:&lt;math&gt;P=VI&lt;/math&gt;

These relationships are useful when selecting resistors, estimating electrical loads, and evaluating power dissipation. However, motors and switching circuits do not always behave as simple resistive loads.

=== Resistors and Capacitors ===

Resistors are used for current limiting, voltage division, signal biasing, and setting operating conditions for electronic devices.

For example, a resistor connected in series with an indicator LED limits the current through the LED. Its value is selected according to the supply voltage, the LED's forward voltage, and the intended current.

Capacitors store electrical charge and are commonly used for filtering, decoupling, and temporary energy storage.

Decoupling capacitors help maintain a stable supply voltage when integrated circuits draw rapidly changing currents. They should generally be placed close to the relevant power pins, with short connections to the supply and ground paths.

Larger capacitors may be used near motor drivers or power inputs to help manage variations in supply current. Their capacitance, voltage rating, equivalent series resistance, and ripple-current capability should be considered according to the application.

=== Diodes and Transistors ===

Diodes conduct current primarily in one direction and are used for rectification, reverse-polarity protection, and voltage clamping.

When an inductive load is switched off, the interruption of current can produce a substantial voltage transient. Depending on the circuit, a suitable flyback diode or other suppression network is required to provide a controlled path for the inductive current.

Transistors are used for electronic switching and amplification. Metal-oxide-semiconductor field-effect transistors (MOSFETs) are particularly common in motor control and power-switching circuits.

MOSFET selection should account for maximum voltage, current, on-state resistance, gate-drive requirements, and thermal performance.

== Power Supply Components ==

A robot may require several supply voltages. Motors, controllers, sensors, and communication modules often have different electrical requirements.

For example, a mobile robot may use a battery to supply its drive motors while a voltage regulator provides a lower, controlled voltage for the microcontroller and sensors.

=== Voltage Regulators ===

Voltage regulators maintain an output voltage within specified limits despite changes in input voltage or load current.

Linear regulators are relatively simple and can provide low-noise outputs, but the voltage difference between input and output is dissipated as heat.

For a conventional linear regulator, power loss can be estimated by:

:&lt;math&gt;P_{\mathrm{loss}}=(V_{\mathrm{in}}-V_{\mathrm{out}})I_{\mathrm{load}}&lt;/math&gt;

This relationship assumes that the regulator's own current consumption is small compared with the load current.

Switching regulators transfer energy through controlled switching elements and usually achieve higher efficiency when a substantial voltage conversion is required. Their design must account for switching noise, inductor selection, output filtering, and PCB layout.

=== Battery Selection and Protection ===

Battery selection involves more than choosing a voltage and nominal capacity.

Important characteristics include:

* Nominal and operating voltage range
* Continuous and peak discharge current
* Capacity and expected operating time
* Battery chemistry and charging requirements
* Physical dimensions and weight
* Protection against overcurrent, overdischarge, and other hazardous conditions

Motor startup and stall currents can be considerably higher than normal operating currents. The battery and associated wiring must therefore be evaluated for expected peak loads, not only average consumption.

Rechargeable lithium-based batteries require appropriate charging and protection systems. A battery pack should be used within the limits specified by its manufacturer.

== Microcontrollers and Interfaces ==

A microcontroller is commonly used to coordinate a robot's sensors, actuators, and control logic. It receives input signals, executes programmed instructions, and generates outputs for other electronic devices.

Microcontrollers typically provide general-purpose input/output (GPIO) pins, timers, communication interfaces, and sometimes analog-to-digital converters (ADCs).

=== Digital and Analog Signals ===

Digital inputs detect logic states, such as whether a switch is open or closed.

Analog inputs measure continuously varying voltages through an ADC. A sensor's output must remain within the permitted voltage range of the receiving device.

Pulse-width modulation (PWM) is commonly generated using microcontroller timers. It is used to control motor drivers, LED brightness, and other devices that respond to a controlled switching signal.

PWM changes the proportion of time that a signal remains active during each cycle. The switching frequency and duty cycle must be compatible with the connected circuit.

=== Communication Interfaces ===

Robots often contain multiple electronic modules that need to exchange information.

Common interfaces include:

* '''UART:''' Asynchronous serial communication, often used for debugging and communication between modules.
* '''I²C:''' A shared synchronous bus commonly used for sensors and peripheral integrated circuits.
* '''SPI:''' A synchronous interface used where comparatively high data rates or direct peripheral control are required.
* '''CAN:''' A communication system used in many automotive and industrial control applications.

Interface selection depends on the required data rate, wiring distance, electrical environment, and the number of connected devices.

Devices using different voltage levels may require level shifting or an interface transceiver.

== Motor Drivers and Power Switching ==

Microcontroller outputs generally cannot supply the current required by a motor. A motor driver therefore acts as the electrical interface between the control circuit and the actuator.

The driver must be selected for the motor type, operating voltage, continuous current, peak current, and required control functions.

=== Brushed DC Motors ===

A brushed DC motor can be controlled using a switching transistor when only one direction of rotation is required.

An H-bridge allows the direction of current through the motor to be reversed, providing forward and reverse operation. Integrated H-bridge drivers may also include current regulation, overcurrent protection, and thermal shutdown.

Texas Instruments describes H-bridge operation and motor-control methods in its educational material on brushed DC motors.&lt;ref&gt;[https://www.ti.com/video/series/precision-labs/ti-precision-labs-brushed-dc-motors.html Texas Instruments: Precision Labs – Brushed-DC Motors]&lt;/ref&gt;

PWM is frequently used to control the effective voltage applied to a motor. The relationship between PWM duty cycle and rotational speed depends on the motor, load, supply voltage, and driver behavior.

=== Stepper and Brushless Motors ===

Stepper motors move according to controlled sequences of electrical excitation. Their drivers regulate winding currents and may support microstepping to produce smaller incremental movements.

Brushless DC motors require electronic commutation. Their controllers switch current between motor phases according to rotor position or a sensorless estimation method.

A driver designed for a brushed DC motor should not automatically be assumed suitable for a stepper or brushless motor.

=== Motor Protection ===

Motor drivers may be exposed to high startup currents, stalled rotors, switching transients, and substantial power dissipation.

Protective features can include:

* Overcurrent detection or current limiting
* Overtemperature protection
* Undervoltage lockout
* Short-circuit protection
* Controlled current recirculation during switching

The protection requirements depend on the motor and operating conditions. Texas Instruments provides examples of driver architectures and current-control methods for brushed DC and stepper motors.&lt;ref&gt;[https://www.ti.com/document-viewer/lit/html/SLAAE97A Optimized H-Bridge Driver Control for Stepper and Brushed-DC Motors | Texas Instruments]&lt;/ref&gt;

== Sensors and Signal Conditioning ==

Sensors convert physical quantities into electrical signals that can be processed by a controller.

Robots may use encoders for motion feedback, inertial sensors for acceleration and angular velocity, distance sensors for obstacle detection, and current sensors for monitoring electrical loads.

The interface circuit depends on the sensor's output type and measurement characteristics.

Analog sensors may require amplification, filtering, or voltage scaling before their signals can be measured by an ADC.

Digital sensors may use serial communication interfaces and provide internally processed measurements.

Measurement accuracy can be affected by electrical noise, supply voltage variations, sensor placement, and calibration errors.

For example, a current-sense resistor produces a voltage proportional to the current flowing through it:

:&lt;math&gt;V_{\mathrm{sense}}=IR_{\mathrm{sense}}&lt;/math&gt;

The resistor must be selected to provide a measurable voltage without introducing excessive power dissipation or voltage drop.

Signal conditioning and software processing should be designed around the accuracy and response time required by the robot.

== Thermal Management ==

Electronic components generate heat as electrical energy is dissipated during operation.

The temperature of a device depends on its power loss, thermal resistance, ambient conditions, and available cooling paths.

A simplified estimate of junction temperature is:

:&lt;math&gt;T_J=T_A+P_D\theta_{JA}&lt;/math&gt;

where:

* &lt;math&gt;T_J&lt;/math&gt; is junction temperature.
* &lt;math&gt;T_A&lt;/math&gt; is ambient temperature.
* &lt;math&gt;P_D&lt;/math&gt; is device power dissipation.
* &lt;math&gt;\theta_{JA}&lt;/math&gt; is junction-to-ambient thermal resistance.

This approximation applies when the thermal-resistance value represents the relevant operating conditions. Published thermal values may not accurately represent every PCB layout or enclosure.

=== Heat Sinks ===

Power transistors, voltage regulators, and motor drivers may require additional cooling, but a heat sink is not necessary for every high-current component.

Some devices can dissipate sufficient heat through their package, PCB copper, and thermal vias.

Likewise, a microcontroller or processor does not automatically require a heat sink. Its cooling requirements depend on power consumption, package construction, ambient temperature, and the surrounding enclosure.

Motor-driver thermal design should account for conduction losses, switching losses, and operating conditions. Manufacturers often provide device-specific guidance for estimating these losses.&lt;ref&gt;[https://www.ti.com/product/DRV8870 DRV8870 Motor Driver Documentation and Design Resources | Texas Instruments]&lt;/ref&gt;

A thermal review should establish whether the expected junction temperature remains within the device's specified limits.

== Further Reading ==

* [[Electronics]] – General electronic components and circuit principles.
* [[Microcontroller]] – Microcontroller architecture and embedded control.
* [[Robotics]] – Additional topics in robot design and construction.

== References ==

&lt;references/&gt;</text>
      <sha1>jxlyvsy0757bqbg7r9d5i8qrdvhbh4g</sha1>
    </revision>
  </page>
  <page>
    <title>Italian/Grammar/Prepositions</title>
    <ns>0</ns>
    <id>24367</id>
    <revision>
      <id>4675735</id>
      <parentid>4437393</parentid>
      <timestamp>2026-10-12T13:40:00Z</timestamp>
      <contributor>
        <username>Luciérnaga de conocimiento</username>
        <id>3401314</id>
      </contributor>
      <origin>4675735</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3146" sha1="ravit2u7q9ks7txn0qi604jfg418zlu" xml:space="preserve">== Prepositions / Preposizioni ==
The &quot;standard&quot; prepositions that are taught at school are
* ''di'' ('of', 'belonging to'; used in place of the English genitive)
* ''a'' ('to')
* ''da'' ('from', 'by')
* ''in'' ('in', 'on' with abstract nouns)
* ''con'' ('with')
* ''su'' ('on')
* ''per'' ('for', 'in order to')
* ''tra'' ('among', 'between')
* ''fra'' ('among', 'between')

Remember that the above translations into English are only approximate.  ''bravo in matematica'' obviously translates into English as ''good at mathematics'' and not ''good in mathematics''.

When prepositions are used together with definite articles, the preposition and the article are sometimes condensed into a single word.  For example, &quot;of the student&quot; becomes &quot;dello studente&quot; and '''not''' &quot;di lo studente&quot;.

More specifically, the following table lists all the possible combinations (except those not in common use today).
{| border=&quot;1&quot;
! !! il !! lo !! la !! i !! gli !! le
|-
! di
| del || dello || della || dei || degli || delle
|-
! a
| al || allo || alla || ai || agli || alle
|-
! da
| dal || dallo || dalla || dai || dagli || dalle
|-
! in
| nel || nello || nella || nei || negli || nelle
|-
! su
| sul || sullo || sulla || sui || sugli || sulle
|-
! con
| col || collo || colla || coi || cogli || colle
|}

Please note that using these combinations (except those with ''con'') is '''mandatory''': you cannot choose to use plain preposition + article instead. With ''con'', it's possible to use both the combination or the separated words: ''col'' or ''con il'' and so on. ''Per'', ''tra/fra'' and all other prepositions don't have contracted forms, they simply use preposition + article. Originally ''con'' and ''per'' also had contracted forms (''col, collo, etc.'' and ''pel, pella, etc.'') but these are never used anymore (with the exceptions ''col'' (= con + il) and ''coi'' (= con + i) which are still occasionally found). 

With indefinite articles, there is no condensed form, hence ''in un'', and so on. 

The prepositions ''di'' and ''da'' '''may''' take an apostrophe and become '' d' '' before a vowel.  Examples where this is the rule, and not simply a matter of personal preference, are
* ''d'altra parte'', lit. &quot;from other side&quot;, meaning &quot;on the other hand&quot;
* ''d'altro canto'', lit. &quot;from other place&quot;, as above
* ''d'altri'', &quot;of others&quot; (but ''di altri'' is acceptable)
* ''d'oro'', &quot;made of gold&quot;, &quot;golden&quot;
* ''d'argento'', &quot;made of silver&quot;
* ''d'oltreoceano'', ''d'oltralpe'', etc.
* the name of a country: ''d'Italia''

For euphonic reasons, the proposition ''a'' can become ''ad'' before a vowel, though this is not mandatory. When the vowel following the preposition is another 'a', using ''ad'' can probably be considered mandatory. Examples: ''ad altri'' (to others), ''ad essere'' or ''a essere'' (to be), ''ad oltranza'' or ''a oltranza'' (ad libitum).

Historically, ''per'' has been a combinable preposition (with combined forms ''pel'', ''pello'', ''pella'', ''pei'', ''pegli'',  ''pelle''), but this usage is never encountered in contemporary prose, even though it is still present in the dialects of Tuscany.

{{BookCat}}</text>
      <sha1>ravit2u7q9ks7txn0qi604jfg418zlu</sha1>
    </revision>
  </page>
  <page>
    <title>Radiation Oncology/Prostate/Prostate Overview</title>
    <ns>0</ns>
    <id>30081</id>
    <revision>
      <id>4675711</id>
      <parentid>4585786</parentid>
      <timestamp>2026-10-12T12:01:10Z</timestamp>
      <contributor>
        <username>Jcb</username>
        <id>90773</id>
      </contributor>
      <origin>4675711</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="21023" sha1="fkctnc95gsxww2zrm3kjucgr1880me7" xml:space="preserve">{{:Radiation Oncology/Prostate:TOC}}


&lt;big&gt;'''Prostate Cancer Overview'''&lt;/big&gt;


==Anatomy==
*Please see the [[Radiation_Oncology/Anatomy#Prostate|anatomy]] page

==PSA==
*Please see the [[Radiation_Oncology/Prostate/PSA|PSA]] page

==Gleason score==
The Gleason grading system, originally developed in 1966, was modified in 2005 at the International Society of Urological Pathology Consensus Conference.  In general, the changes resulted in a more narrow scope of grade 3 and an expanded scope of grade 4, thus shifting a number of previously diagnos

*'''1966''' {{PMID|5948714}} -- &quot;Classification of prostatic carcinomas.&quot; (Gleason DF, Cancer Chemother Rep. 1966 Mar;50(3):125-8.)
*'''2005''' {{PMID|16096414}} -- &quot;The 2005 International Society of Urological Pathology (ISUP) Consensus Conference on Gleason Grading of Prostatic Carcinoma.&quot;
*'''2006''' (Web article, non peer reviewed) [http://prostate-cancer.org/gleason-grade-migration-changes-in-prostate-cancer-grade-in-the-contemporary-era/ PCRI Insights] &quot;Gleason Grade Migration: Changes in Prostate Cancer Grade in the Contemporary Era&quot; (August 2006, 9(3))
*'''2009''' {{PMID|19886716}} [http://www.archivesofpathology.org/doi/pdf/10.1043/1543-2165-133.11.1810 Full text] -- &quot;Current perspectives on the Gleason grading of prostate cancer.&quot;
*'''2010''' {{PMID|20157302}} -- &quot;Clinical implications of changing definitions within the Gleason grading system.


===Clinical correlates===

*'''Colorado/SEER; 2014''' (2004-2006) {{PMID|25151595}} -- &quot;Gleason stratifications prognostic for survival in men receiving definitive external beam radiation therapy for localized prostate cancer.&quot; (Rusthoven CG, Urol Oncol. 2015 Feb;33(2):71.e11-9)
**Retrospective. 26,885 men with Gleason 6-10 PCa, 2004-2006, managed with definitive external beam radiation alone.
**For Gleason 6, 3+4, 4+3, 4+4, 8 with pattern 5 (3+5 or 5+3), 9, and 10 the 7.5-year PCSS rates were 99%, 97%, 95%, 91%, 86%, 81%, and 78% and 7.5-year OS rates were 83%, 76%, 72%, 67%, 66%, 58%, and 54%, respectively.
*CONCLUSION: &quot;In the largest reported survival analysis of Gleason stratifications, biopsy-assigned GS 6, 3+4, 4+3, 4+4, 8 w/P5, 9, and 10 represented sequential prognostic factors for survival in patients managed with definitive EBRT.&quot;


*'''Johns Hopkins; 2013''' {{PMID|23464824}} -- &quot;Prognostic Gleason grade grouping: data based on the modified Gleason scoring system&quot; (Pierorazio PM, BJU Int. 2013. May;111(5):753-60)
**Retrospective. 7,869 men with PCa, diagnosed 2004 or later, managed with prostatectomy. Biochemical recurrence-free (BFS) survival evaluated as the primary endpoint.
**5-year BFS rates for men with Gleason grade ≤ 6, 3 + 4, 4 + 3, 8 and 9-10 tumours at biopsy were 94.6, 82.7, 65.1, 63.1 and 34.5%, respectively (P &lt; 0.001 for trend); and 96.6, 88.1, 69.7, 63.7 and 34.5%, respectively (P &lt; 0.001), based on RP pathology
*Conclusion: &quot;There is a need for a change in (Gleason) reporting to more closely reflect tumour behaviour.&quot; Authors propose reporting Gleason score ≤ 6 (prognostic grade group I); Gleason score 3+4=7 (prognostic grade group II); Gleason score 4+3=7 (prognostic grade group III); Gleason score 4+4=8 (prognostic grade group (IV); and Gleason score 9-10 (prognostic grade group (V).


*'''Harvard; 2009''' (1984-2004) {{PMID|19433685}} -- &quot;Gleason score and lethal prostate cancer: does 3 + 4 = 4 + 3?&quot; (Stark JR, J Clin Oncol. 2009 Jul 20;27(21):3459-64. Epub 2009 May 11.)
**Retrospective. 812 patients with GS 7 (prostatectomy 693, biopsy 119) on Physicians Health Study and Health Professionals Followup Study. Blinded review by 3 pathologists. Lethal PCA defined as bony mets or PCA death
**Gleason score: Striking upgrading in GS score. Initial GS 2-5 in 25%, on review in &lt;1%
**Outcome: No leathal PCA in GS 2-6; reference 3+4; hazard ratios for lethal cancer GS 4+3 HR 3.1 (SS), GS 8 HR 7.4 (SS), GS 9-10 HR 19 (SS)
*Conclusion: Ignoring pattern 4 in GS 7 may conceal important prognostic information


*'''MSKCC; 2012''' (1989-2011) {{PMID|23182392}} -- &quot;Prognostic Importance of Gleason 7 Disease Among Patients Treated With External Beam Radiation Therapy for Prostate Cancer: Results of a Detailed Biopsy Core Analysis&quot; (Spratt DE, IJROBP. 2012 Nov 20;S0360-3016(12)03663-2)
**Retrospective. 613 patients with GS 7 (all solely with EBRT). Required complete core biopsy information (location of each biopsy core, positive core percentage, individual core involvement, PIN, and PNI). First EBRT study to assess bRFS, DM, and PCSM between GS 3+4 vs 4+3.
**Outcome: The 8-year bRFS rate for pG3 versus pG4 was 77.6% versus 61.3% (P&lt;.0001), DMFS was 96.8% versus 84.3% (P&lt;.0001), and PCSM was 3.7% versus 8.1% (P=.002). On multivariate analysis, pG4 predicted for significantly worse outcome in all parameters. Excellent review of all studies on the subject of GS 3+4 vs 4+3.
**Conclusion: Primary Gleason grade 4 independently predicts for worse bRFS, DMFS, and PCSM among Gleason 7 patients even in the setting of biopsy information.

==Workup==
*Use of bone scan and CT scan: Use of routine scans in early stage prostate cancer questioned. Bone scan + in &lt;5% and CT scan + in &lt;12% for those with PSA &lt; 20, and &lt;2% and 9% for those with PSA &lt; 20 and Gleason 6 or less. For PSA &gt; 50, positive in 10%; for Gleason 8-10 with PSA &gt;20, positive in 20%.  &amp;mdash; (SEER data, Prostate Cancer Outcomes Study - Albertsen et al. {{PMID|10737483}} J Urol. 2000 Apr;163(4):1138-43.)
* {{PMID|15126770}} reviews 48 articles and finds
**Bone scan + in 2.3% if PSA &lt; 10, in 5.3% with PSA 10-20 and 16.2% with PSA 20-50.
**Bone scan + in 5.6% if Gleason 7 or less vs 29.9% if Gleason 8-10
**Bone Scan + in 6.4% if stage T2 or less vs 49.5% if T3-4 
**CT + in 0% if PSA &lt; 20 and 1.1% if PSA &gt; 20
**CT + in 1.2% Gleason 7 or less vs 12.5% Gleason 8-10
**CT + in 0.7% T2 or less vs 25.8% of T3-4s


==Pattern of spread to lymph nodes==
Prostate lymphatic drainage is to hypogastric (primary), obturator (secondary), external iliac (tertiary), and presacral (quarternary). 
For radical prostatectomy, lymph node dissection includes only the obturator and external iliac LNs, and is recommended for PSA &gt; 10 and Gleason &gt; 6. 
Heidenreich et al ({{PMID|11912387}}) reported that with extended lymphadenectomy (including all four drainage regions), LN mets were detected in 26% vs 12%, and that 2/3 of patients had LN mets outside of the fields of standard lymphadectomy.  Recommended extended lymphadenectomy of external and internal iliacs and obturator for pts with PSA &gt; 10 and Gleason 7 or above (only 2% LN+). Do not recommend dissection of presacral region or common iliac.

==Predictors of pathologic stage==

===Partin tables===
*'''Online tool:''' [http://urology.jhu.edu/prostate/partintables.php Partin tables (Johns Hopkins)] 
*'''Original; 1993''': {{PMID|7685418}} &amp;mdash; &quot;The use of prostate specific antigen, clinical stage and Gleason score to predict pathological stage in men with localized prostate cancer.&quot; Partin AW et al. J Urol. 1993 Jul;150(1):110-4. 
*'''Update; 1997''': {{PMID|9145716}} &amp;mdash; &quot;Combination of prostate-specific antigen, clinical stage, and Gleason score to predict pathological stage of localized prostate cancer. A multi-institutional update.&quot; Partin AW et al. JAMA. 1997 May 14;277(18):1445-51.
*'''Update; 2001''': {{PMID|11744442}} &amp;mdash; &quot;Contemporary update of prostate cancer staging nomograms (Partin Tables) for the new millennium.&quot; Partin AW et al. Urology. 2001 Dec;58(6):843-8.
*'''2007''' (2000-2005) {{PMID|17572194}} -- &quot;Updated nomogram to predict pathologic stage of prostate cancer given prostate-specific antigen level, clinical stage, and biopsy Gleason score (Partin tables) based on cases from 2000 to 2005.&quot; (Makarov DV, Urology. 2007 Jun;69(6):1095-101.)
**Retrospective. 5730 men, prostatectomy, no neoadjuvant therapy. Variables used PSA (80% &lt;10), clinical stage (77% T1c), biopsy Gleason (76% GS 5-6)
**Outcome: Nomogram developed
**Conclusion: Updated &quot;Partin tables&quot; reflect trends in presentation
*'''2012''' (2006-2011) {{PMID|22834909}} [http://onlinelibrary.wiley.com/doi/10.1111/j.1464-410X.2012.11324.x/abstract;jsessionid=45EC7B35C58C48ACFFCAD76AAE500AA3.d02t03 Full text] -- &quot;An updated prostate cancer staging nomogram (Partin tables) based on cases from 2006 to 2011.&quot; (Eifler JB, BJU Int. 2012 Jul 26. -- Epub ahead of print)
**5629 men. Median PSA 4.9; Gleason 6 in 63%; T1c in 78%. 
**OC (organ confined) in 73%, EPE 23%, SV+ 3%, LN+ 1.
**Compared to prior cohort (2000-2005), more likely to have PSA &lt;= 4 (30% vs 25%), Gleason score &gt;= 7 on biopsy (37% vs 23%) and prostatectomy (50% vs 36%), but were similar in clinical and pathologic stage.
**Conclusion: &quot;The distribution of pathologic stages did not change at our institution between 2000-2005 and 2006-2011. The updated Partin nomogram takes into account the updated Gleason scoring system and may be more accurate for contemporary patients diagnosed with prostate cancer.&quot;
*'''2017''' (2010-2015) {{PMID|27367645}} -- &quot;Prediction of pathological stage based on clinical stage, serum prostate-specific antigen, and biopsy Gleason score: Partin Tables in the contemporary era.&quot; (Tosoian JJ, BJU Int. 2017 May;119(5):676-683. )
**Median PSA 4.9; Gleason 6 in 47%
**OC in 74%, EPE 20%, SV+ 4%, LV+ 2%. 
*&lt;U&gt;Caution:&lt;/U&gt; The Partin tables assign the &quot;worst-case&quot; pathologic stage for each case; the categories are mutually exclusive. (E.g., those included as &quot;capsular penetration&quot; had to have no seminal vesicle involvement or lymph node involvement, and those included as &quot;positive seminal vesicle&quot; had to have no lymph node involvement. The categories sum to 100%.) This method gives an underestimation of the true rate of extracapsular extension and seminal vesicle involvement.

===Roach equations===
*'''Seminal vesicle involvement''' - PSA +([Gleason -6] x 10) &amp;mdash; {{PMID|7523343}}
**Cutoff is 13%.  If &lt;13%, risk 7%; if &gt;=13%, risk 37%.
*'''Lymph node involvement''' - 2/3 x PSA + ([Gleason-6] x 10) &amp;mdash; {{PMID|7505775}}
**Cutoff is 15%. If calculated risk is &lt;15%, actual risk 6%; if &gt;=15%, actual risk 40%.
*'''Extracapsular extension''' - 1.5 x PSA + ([Gleason-3) x 10) &amp;mdash; {{PMID|10875450}}
**Approximates actual risk.

===Kattan nomogram===
:see also page at [[Radiation_Oncology/Prostate/Localized_Prostate_Cancer#Outcome Prediction|Localized Prostate Cancer#Outcome Prediction]] for other nomograms
&lt;br&gt;
*'''Metagram; 2009''' {{PMID|19544545}} -- &quot;Development of a prostate cancer metagram: a solution to the dilemma of which prediction tool to use in patient counseling.&quot; (Nguyen CT, Cancer. 2009 Jul 1;115(13 Suppl):3039-45.)

*'''Preoperative nomogram; 1998''' - {{PMID|9605647}} &amp;mdash; &quot;A preoperative nomogram for disease recurrence following radical prostatectomy for prostate cancer.&quot; Kattan MW et al. J Natl Cancer Inst. 1998 May 20;90(10):766-71.

===LN involvement===
*'''Harvard; 2009''' (2004) {{PMID|19286330}} -- &quot;Predicting the risk of pelvic node involvement among men with prostate cancer in the contemporary era.&quot; (Nguyen PL, Int J Radiat Oncol Biol Phys. 2009 May 1;74(1):104-9. Epub 2009 Mar 13.)
**SEER analysis. 9,387 men with cT1c-T4 PCA, surgical LN evaluation, GS and PSA. 98% were cT1c/T2
**Patient characteristics: PSA &lt;4 in 16%, 4-10 in 62%, 10-20 in 14%, &gt;20 in 6%. Gleason &lt;=6 in 39%, 7 in 46%, and 8-10 in 13%. Clinical T1c in 51%, T2 in 46%, T3-T4 in 2.5%. Median 5 LN evaluated.
**Outcome: LN+ in 3.3%. Roach scores overestimated actual rates by 16x if score &lt;10%, by 7x if score 10-20%, and by 2.5x if score &gt;20%. Adjusted expected risk of LN+ is 0.2% for Roach scores &lt;=10%, 2.0% for Roach scores 10-20%, 9.7% (with observed risk 6.5%) for Roach scores 20-30%, and 13.9% for Roach scores 30-40%. Note: adjustment factors should not be applied for T3-T4 disease.
**Provides table of LN risk by clinical T stage, PSA, and Gleason score (similar to Partin table).
**Comment: Synopsis of data from table: &gt;15% risk of +LN for: T1c with G 8-10 and PSA &gt;20; T2 with G 8-10 and PSA &gt;10; T3 overall risk 15%; T4 overall risk 41%.
**Conclusion: Roach formula appears to overestimate contemporary patients with mainly T1c/T2 disease

*'''Yale formula; 2011''' (2004-2006) {{PMID|20594769}} -- &quot;A new formula for prostate cancer lymph node risk.&quot; (Yu JB, Int J Radiat Oncol Biol Phys. 2011 May 1;80(1):69-75.)
**Based on SEER database for cT1-T2, PSA &lt; 26. In contrast to Roach equation and Harvard (Nguyen formula), includes T-stage.
**%LN+ risk is [GS - 5] × [PSA/3 + 1.5 × T], where T = 0, 1, and 2 for cT1c, cT2a, and cT2b/cT2c. 

===SV invasion===
'''''Seminal vesicle invasion:'''''
*'''Mayo''' (1988-93) - {{PMID|8948342}}, '''1996''' &amp;mdash; &quot;Correlation of pretherapy prostate cancer characteristics with seminal vesicle invasion in radical prostatectomy specimens.&quot; Pisansky TM et al. Int J Radiat Oncol Biol Phys. 1996 Oct 1;36(3):585-91.
**T-stage (T2a or less vs. T2b-c vs. T3a-b), primary Gleason grade (1-2, vs. 3, vs 4+), and PSA predict for SVI on multivariate analysis.

==Definitions of Risk Groups==
*'''NCCN''' (v1.2011)
**Very low risk: T1c,  GS 2- 6, PSA &lt; 10, Fewer than 3 prostate biopsy cores positive, &lt; 50% cancer in each core, PSA density &lt; 0.15 ng/mL/g
**Low risk: T1-T2a and GS 2-6 and PSA &lt;10
**Intermediate risk: T2b-T2c or GS 7 or PSA 10-20
**High risk: T3a or GS 8-10 or PSA &gt;20
**Locally advanced (Very High): T3b-T4
**Metastatic: N1
**Metastatic: M1

*'''RTOG risk group classification''' - {{PMID|10837943}} (Roach) - does not include PSA information. Used in RTOG Meta-Analysis
**Group 1 / low risk (T1-2,G&lt;=6)
**Group 2 / int (T1-2,G7; T3 or N1, G&lt;=6) 
**Group 3 / high (T1-2,G&gt;=8; T3 or N1, G7)
**Group 4 / very high (T3 or N1, G&gt;=8) 

*'''D'Amico''', 1998 (1989-97) - {{PMID|9749478}} &amp;mdash; &quot;Biochemical outcome after radical prostatectomy, external beam radiation therapy, or interstitial radiation therapy for clinically localized prostate cancer.&quot; D'Amico AV et al. JAMA. 1998 Sep 16;280(11):969-74. 
**1872 pts treated by RP, implant, or EBRT. Defined risk groups:
***Low risk: T1c-T2a, PSA 10 or less, &lt;u&gt;and&lt;/u&gt; Gleason 6 or less - PSA failure risk &lt;25% at 5 years.
***Intermediate risk: T2b, &lt;u&gt;or&lt;/u&gt; PSA &gt;10 and &lt;= 20, &lt;u&gt;or&lt;/u&gt; Gleason 7 - 25-50% risk.
***High risk: T2c &lt;u&gt;or&lt;/u&gt; PSA &gt; 20 &lt;u&gt;or&lt;/u&gt; Gleason 8 or more - &gt; 50% risk.
**See also update of trial under [[#Retrospective|Comparison of Primary Treatments section]] (D'Amico, Cancer 2002)

*'''Shipley''' (Multi-institutional), 1999 (1988-1995) - {{PMID|10235152}} &amp;mdash; &quot;Radiation therapy for clinically localized prostate cancer: a multi-institutional pooled analysis.&quot; Shipley WU et al. JAMA. 1999 May 5;281(17):1598-604.
**1765 pts, T1-2N0M0 with available pretreatment PSA levels were treated with RT alone (median dose 63-79 Gy, 51% 3-D Conformal, various field sizes).   Mean pretreatment PSA was 18.9 and median was 10.1 with 74% T2 and ~25% with PSA &gt; 20.  
**Median f/u 4.1 years
***RPA used with pretreatment PSA a continuous variable to find specific risk/cutoff points.  
***Group 1: PSA &lt;~10 bPFS = 81%
***Group 2: ~10 &gt; PSA &lt; ~20 bPFS = 69%
***Group 3: PSA &gt; ~20 and Gleason &lt;=6 bPFS = 47%
***Group 4: PSA &gt; ~20 and Gleason &gt;= 7 bPFS = 29%
**''See also:'' at page [[Radiation_Oncology/Prostate/Localized_Prostate_Cancer#EBRT_Outcomes | Localized Prostate Cancer]]

*'''Pisansky''' (Mayo), 1997 (1987-93) - {{PMID|9179062}} &amp;mdash; &quot;An enhanced prognostic system for clinically localized carcinoma of the prostate.&quot; Pisansky TM et al. Cancer. 1997 Jun 1;79(11):2154-61.
**500 pts, T1-4N0M0 treated with RT alone (median dose 64-66 Gy). Elective nodal RT in 30%. 
**Median f/u 43 mos. 
***Risk groups (and 5-yr relapse-free survival): Low - 92, Intermediate - 67, High - 24.

===Subclassification===
'''''Subclassification of Intermediate Risk into Unfavorable and Favorable:'''''
*'''Zumsteg; 2013''' (1992-2007) {{PMID|23541457}} [http://www.europeanurology.com/article/S0302-2838(13)00257-1/fulltext/a-new-risk-classification-system-for-therapeutic-decision-making-with-intermediate-risk-prostate-cancer-patients-undergoing-dose-escalated-external-beam-radiation-therapy-img-src-manager-uploads-els-articles-s0302-2838-13-00257-1-assets-eulogo1-jpg-alt-eulogo1 Full text] -- &quot;A new risk classification system for therapeutic decision making with intermediate-risk prostate cancer patients undergoing dose-escalated external-beam radiation therapy.&quot;
**Based on pts treated with EBRT to ≥ 81 Gy +/- ADT. Using NCCN risk classification.
**&lt;U&gt;Unfavorable intermediate risk&lt;/u&gt;: primary Gleason 4 (G 4+3) pattern, percentage of positive biopsies (ppb) ≥ 50%, or ≥ 2 intermediate-risk factors (using NCCN, i.e. T2b-T2c, PSA 10-20, Gleason 7).
**&lt;U&gt;Favorable intermediate risk&lt;/u&gt;: a single NCCN intermediate risk factor, Gleason ≤ 3+4=7, and &lt; 50% positive biopsy cores.

===Other prognostic factors===
*'''Percent positive prostate cores:''' D'Amico 2004 (1988-2002) - retrospective
**{{PMID|15365069}} &amp;mdash; &quot;Impact of the percentage of positive prostate cores on prostate cancer-specific mortality for patients with low or favorable intermediate-risk disease.&quot; D'Amico AV et al. J Clin Oncol. 2004 Sep 15;22(18):3726-32. 
**421 pts, low or &quot;favorable intermediate risk&quot;, treated with RT alone. 
**Median f/u 4.5 yrs. Percentage of positive prostate cores (&gt;=50 vs &lt;50%) was the only significant predictor of disease-specific mortality, with a RR between 6 and 12.

==Utilization==
*''Please also see [[Radiation_Oncology/Prostate/Protons]] for Proton Therapy utilization''


*'''Center for Disease Control (CDC), Atlanta; 2007''' {{PMID|17469027}} -- &quot;Use of additional treatment for prostate cancer after radical prostatectomy, radiation therapy, androgen deprivation, or watchful waiting.&quot; (Berge V, Scand J Urol Nephrol. 2007;41(3):198-203.)
**SEER + Medicare claims data. 12,711 patients. Initial RP 31%, initial RT 31%, initial ADT 9%, initial WW 28%
**Outcome: Initial RP: 8% additional RT, 12% additional ADT. Initial RT: 23% additional ADT. Initial WW: 22% additional ADT
**Conclusion: If initially treated with RT or observation, more likely to receive ADT as follow-up treatment than if initially treated with RP

*'''American College of Radiology; 2002''' (1992-1993) {{PMID|12065564}} -- &quot;Comparing the costs of radiation therapy and radical prostatectomy for the initial treatment of early-stage prostate cancer.&quot; (Burkhardt JH, J Clin Oncol. 2002 Jun 15;20(12):2869-75.)
**Linked SEER-Medicare analysis. 
**Outcome: Costs RT $14,048 vs. RP $17,226 (SS)
**Conclusion: For early-stage PCA, average costs were at least 23% greater for RP

*'''UCLA; 2000''' (1993-1996) {{PMID|11042575}} -- &quot;A nationwide charge comparison of the principal treatments for early stage prostate carcinoma.&quot; (Brandeis J, Cancer. 2000 Oct 15;89(8):1792-9.)
**HCFA claims data for inpatient, outpatient and Part B claims. 10,107 men with initial diagnosis of prostate cancer, treatment, +6 months of follow-up. RT 58%, brachy 7%, RP 35%. During the 4 years, RT decreased by 20%, brachy increased by 21%
**Cost: RP + adjuvant RT $31,329 vs. RT + brachy boost $24,407 vs. RP $19,019 vs RT $15,937 vs brachy $15,301 (SS). Utilization varied with age, race, and geographic region
**Outcome: Without clear survival advantage, costs, QoL and patient preference take on paramount importance


==Other Resources==
*[https://astro.webex.com/ec0606l/eventcenter/recording/recordAction.do?theAction=poprecord&amp;AT=pb&amp;renewticket=0&amp;isurlact=true&amp;recordID=21923257&amp;apiname=lsr.php&amp;rKey=c678dca6d7f44059&amp;format=short&amp;needFilter=false&amp;&amp;SP=EC&amp;rID=21923257&amp;siteurl=astro&amp;actappname=ec0606l&amp;actname=%2Feventcenter%2Fframe%2Fg.do&amp;rnd=9585351976&amp;entappname=url0108l&amp;entactname=%2FnbrRecordingURL.do eContouring Webinar - Prostate Cancer with Michael Zelefsky, M.D.]
*[https://astro.webex.com/ec0606l/eventcenter/recording/recordAction.do?theAction=poprecord&amp;AT=pb&amp;renewticket=0&amp;isurlact=true&amp;recordID=19810057&amp;apiname=lsr.php&amp;rKey=b03dff525247e51e%20&amp;format=short&amp;needFilter=false&amp;&amp;SP=EC&amp;rID=19810057&amp;siteurl=astro&amp;actappname=ec0606l&amp;actname=%2Feventcenter%2Fframe%2Fg.do&amp;rnd=6598251926&amp;entappname=url0108l&amp;entactname=%2FnbrRecordingURL.do ASTRO/ARRO Journal Club Webinar 2012 - &quot;Surrogate endpoints for prostate cancer-specific mortality after radiotherapy and androgen suppression therapy in men with localised or locally advanced prostate cancer: an analysis of two randomised trials&quot; with Anthony D'Amico, MD, PhD, FASTRO]
*[https://astro.webex.com/ec0606l/eventcenter/recording/recordAction.do?theAction=poprecord&amp;AT=pb&amp;renewticket=0&amp;isurlact=true&amp;recordID=18703297&amp;apiname=lsr.php&amp;rKey=e5576f9b0d714c53&amp;format=short&amp;needFilter=false&amp;&amp;SP=EC&amp;rID=18703297&amp;siteurl=astro&amp;actappname=ec0606l&amp;actname=%2Feventcenter%2Fframe%2Fg.do&amp;rnd=7804687264&amp;entappname=url0108l&amp;entactname=%2FnbrRecordingURL.do ASTRO/ARRO Journal Club Webinar 2011 - &quot;Radiotherapy and short-term androgen deprivation for localized prostate cancer&quot; with Anthony Zietman, MD]</text>
      <sha1>fkctnc95gsxww2zrm3kjucgr1880me7</sha1>
    </revision>
  </page>
  <page>
    <title>Radiation Oncology/Prostate/Prostatectomy</title>
    <ns>0</ns>
    <id>30087</id>
    <revision>
      <id>4675712</id>
      <parentid>4584029</parentid>
      <timestamp>2026-10-12T12:02:52Z</timestamp>
      <contributor>
        <username>Jcb</username>
        <id>90773</id>
      </contributor>
      <origin>4675712</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="14043" sha1="i2i2f3qxrdslvk9dt42maw5u2jgcm1i" xml:space="preserve">{{:Radiation Oncology/Prostate:TOC}}

==Prostatectomy vs. Watchful waiting==
''Please see the [[Radiation Oncology/Prostate:Natural_History#Watchful_Waiting|Watchful waiting]] chapter''

==Role of surgical staging==
*Rate of lymphedema is 25-30% in pts undergoing limited dissection, 66% if complete (therapeutic) dissection in pts receiving XRT.
**[http://www.ncbi.nlm.nih.gov/entrez/query.fcgi?cmd=Retrieve&amp;db=pubmed&amp;dopt=Abstract&amp;list_uids=6483687 Abstract] Pilepich, from RTOG 75-06 and 77-06

*[http://www.ncbi.nlm.nih.gov/entrez/query.fcgi?cmd=Retrieve&amp;db=pubmed&amp;dopt=Abstract&amp;list_uids=9531360 Abstract] &amp;mdash; &quot;Impact of surgical staging in evaluating the radiotherapeutic outcome in RTOG #77-06, a phase III study for T1BN0M0 (A2) and T2N0M0 (B) prostate carcinoma.&quot; Asbell et al. 
*:Not randomized. 12-year OS 48% (staging laparotomy) vs 38% (lymphangiogram), DFS 38% vs 26%, decreased bone mets. Indicates that lymphangiogram group was understaged compared with surgical group.

==Natural history after RP==
*'''Multi-Institutional; 2009''' (1987-2005) {{PMID|19636023}} -- &quot;Prostate cancer-specific mortality after radical prostatectomy for patients treated in the prostate-specific antigen era.&quot; (Stephenson AJ, J Clin Oncol. 2009 Sep 10;27(26):4300-5. Epub 2009 Jul 27.)
**Retrospective; Memorial Sloan Kettering and Baylor patients to develop a nomogram, validation on Cleveland Clinic and University of Michigan data. 12,677 patients treated with RP. Primary outcome PCA-specific mortality. Median F/U 4 years
**Outcome: 15-year PCSM 12%, all-cause mortality 38%. Only 4% of contemporary patients had predicted 15-year PCSM &gt;5%. Using D'Amico risk groups, 15-year PCSM good risk 2% vs. intermediate risk 10% vs. high risk 19% (good risk comprised 46% of patients)
**Conclusion: Few patients will die from prostate cancer within 15 years after radical prostatectomy, despite presence of adverse clinical features


Natural history of biochemical failure:
*Pound, 1999 - {{PMID|10235151}} &amp;mdash; &quot;Natural history of progression after PSA elevation following radical prostatectomy.&quot; Pound CR et al. JAMA. 1999 May 5;281(17):1591-7.
**315 of 1997 men developed biochemical failure. 34% developed mets in median time to mets 8 years after PSA elevation. Median time to death 5 years after mets. Predictive of mets: Gleason 8-10, PSA recurrence &lt; 2 yrs after surgery, PSA doubling time &lt; 10 months. 

'''Factors predicting local recurrence:'''
:''See section:'' [[Radiation_Oncology/Prostate/Adjuvant_RT#Clinical and Pathologic Factors predicting recurrence|Clinical and Pathologic Factors predicting recurrence]] at [[../Adjuvant RT|Adjuvant RT after Prostatectomy]].

'''Factors predicting biochemical failure:'''
*'''Harvard''' 2005 (1989-2002) - {{PMID|16051949}} &amp;mdash; &quot;Identifying patients at risk for significant versus clinically insignificant postoperative prostate-specific antigen failure.&quot; D'Amico AV et al.  J Clin Oncol. 2005 Aug 1;23(22):4975-9.
**1011 pts. Looked for factors identifying post-op PSA doubling time &lt; 3 months (&quot;clinically significant&quot;) or PSA DT &gt; 12 months or no failure (&quot;clinically insignificant&quot;)
**Predictive of clinically significant failure: 1) preoperative PSA velocity &gt; 2 ng/mL/yr, and 2) Gleason 7 or above.  
**Predictive of clinically ''in''significant or no failure: 1) PSA &lt; 10, 2) nonpalpable cancer with Gleason 6 or less, and 3)preoperative PSA velocity &lt; 2

'''Factors predicting metastatic disease:''' 

*PSA doubling time &lt; 10 months (from Pound)
*Extracapsular extension, SV invasion, Gleason 8-10, higher PSA at time of biochemical failure &amp;mdash; (Dotan ZA et al - Abstract 162, 2005 Multidisciplinary Prostate Cancer Symposium) - nomogram

'''Factors predicting survival:'''
*Post-Prostatectomy PSA Velocity Linked to Increased Mortality
*:Anthony D'Amico.  NEJM, 8 July 2004, 351:125-135

*D'Amico - (Abstract) American Urological Association, 2005, Abstract 1678
**1011 pts. Evaluated factors predictive of mortality - included 1-year PSA velocity prior to diagnosis, baseline PSA, Gleason score, clinical stage.  Correlated with post-operative PSA doubling time, and correlated PSA doubling time with mortality.
**Short postoperative PSA doubling time (&lt;3 months) predicted death due to cancer and overall deaths.  Short PSA DT more likely in pts with preoperative PSA velocity &gt; 2 per year and a Gleason of 7 or higher.  Factors predictive of long PSA doubling time (&gt;12 months) or no PSA failure were baseline PSA &lt; 10, clinical stage T1c or less, Gleason 6 or less, and PSA velocity &lt; 0.5 / yr.
**Conclusion: pts with protracted PSA after surgery may not need salvage treatment.

*'''Johns Hopkins''' (1982-2000)
**379 pts with biochemical recurrences after RP. PSA-DT groups of &lt;3 (6%), 3-9 (31%), 9-15 (21%), &gt;15 (42%) months
**'''2005''' {{PMID|16046649}} &amp;mdash; &quot;Risk of prostate cancer-specific mortality following biochemical recurrence after radical prostatectomy.&quot; Freedland SJ et al. JAMA. 2005 Jul 27;294(4):433-9. Median f/u 10 yrs after surgery.
***Prostate-cancer specific survival is predicted by: PSA doubling time, Gleason score, and interval from surgery to biochemical failure.
**'''2007''' {{PMID|17470867}} -- &quot;Death in patients with recurrent prostate cancer after radical prostatectomy: prostate-specific antigen doubling time subgroups and their associated contributions to all-cause mortality.&quot; (Freedland SJ, J Clin Oncol. 2007 May 1;25(13):1765-71.) Median F/U 11.4 years
***Outcome: PSA-DT &lt;3 deaths account for only 13% due to low number; they die quickly, but with longer follow-up, slower PSA-DT patients start to die too. Intermediate PSA-DT 3-9 months account for 60% of PCA-related deaths
***In PSA-DT &lt;15 months, 90% will die *of* prostate cancer, not *with* prostate cancer at 15 years. Only if PSA-DT &gt;15 months, competing-cause mortality greater
***Conclusion: Even intermediate PSA-DT leads to prostate-cancer death

==Prostatectomy vs RT==
:''Also see:'' [[Radiation Oncology/Prostate/Localized Prostate Cancer]] (for comparisons of treatment modalities)
*'''Cleveland Clinic''', 2002 (1990-98) - {{PMID|12177097}} &amp;mdash; &quot;Comparison of the efficacy of local therapies for localized prostate cancer in the prostate-specific antigen era: a large single-institution experience with radical prostatectomy and external-beam radiotherapy.&quot; Kupelian PA et al. J Clin Oncol. 2002 Aug 15;20(16):3376-85. 
**Retrospective, single-institution. 1682 pts with clinical stage T1-T2, treated during the PSA era. Treated with prostatectomy or RT to 68-78 Gy (median 70.2 Gy). Excluded pts with adjuvant androgen deprivation. Allowed neoadjuvant androgen deprivation if less than 6 months (19%). End-point was biochemical relapse free survival. Used ASTRO definition for PSA failure after RT. For RP failure was two consecutive PSA &gt; 0.2; defined failure at time of first detectable level. 
**bRFS increased for prostatectomy arm 80% vs 73% at 5-years and 72% vs 70% at 8-years. On multivariate analysis, treatment modality was not an independent predictor of relapse. For favorable tumors, no difference between RP and RT: 8-year bRFS 86% vs 90%. For unfavorable tumors, 8-year bRFS 62% vs 59% (N.S.).  For unfavorable pts treated with RT to &gt;= 72 Gy, there was an improved bRFS 82% vs 70% at 5 years compared to RP. For dose &lt; 72 Gy, it was worse compared to RP: 50% vs 70%.
**Conclusion: &quot;Eight-year biochemical failure rates were identical between RT and RP in any subgroup. Outcome is determined mainly by pretreatment PSA levels, bGS, clinical T stage, and, for RT patients, radiation dose.&quot;

* '''M. D. Anderson Cancer Center Orlando''', 2004 (1990-98) - {{PMID|14697417}} &amp;mdash; &quot;Radical prostatectomy, external beam radiotherapy &lt;72 Gy, external beam radiotherapy &gt; or =72 Gy, permanent seed implantation, or combined seeds/external beam radiotherapy for stage T1-T2 prostate cancer.&quot; Int J Radiat Oncol Biol Phys. 2004 Jan 1;58(1):25-33 Kupelian et al.
**Retrospective. Comparison of biochemical relapse-free survival (bRFS) for various methods.
**CONCLUSION: The biochemical failure rates were similar among PI, high-dose (&gt; or =72 Gy) EBRT, COMB, and RP for localized prostate cancer. The outcomes were significantly worse for low-dose (&lt;72 Gy) EBRT.

* '''Memorial Sloan Kettering Cancer Center at Mercy Medical Center''', 2004 (1992-98) - {{PMID|15066293}} &amp;mdash; &quot;Monotherapy for stage T1-T2 prostate cancer: radical prostatectomy, external beam radiotherapy, or permanent seed implantation&quot; Radiother Oncol. 2004 Apr;71(1):29-33 Potters L et Al.
**Retrospective. 1819 pts, clinical stage T1-T2 (AJCC 1997). Compared freedom from biochemical recurrence (FBR) for various methods. EBRT dose was &gt;= 70 Gy. All received monotherapy without adjuvant therapy. 
**7-year FBR for PPB vs EBRT vs RP were 74, 77, and 79%, respectively. Multivariate analysis identified iPSA and bGS as prognostic factors of relapse. Treatment modality, age, clinical T-stage, and race were not independent predictors of failure. 
** CONCLUSIONS: Pretreatment PSA levels, and biopsy Gleason score determined outcome in this study cohort. Biochemical failure rates in this study cohort are similar between PPB, RT, and RP as monotherapy for clinically localized prostate cancer.

== Prostatectomy vs RT and Expected Patient survival ==
Although treatment outcomes after radical prostatectomy seem to be independent of the age of the patient, at least one study has found a higher PSA failure rate in patients younger than 60 years treated with conventional dose levels external-beam radiotherapy. Men with prostate cancer 60 years or younger treated with high dose conformal external beam radiotherapy seem to have an excellent biochemical outcome and to fare as well as older patients.

* {{PMID|12131302}}, 2002 - &quot;Competing risk analysis after radical prostatectomy for clinically nonmetastatic prostate adenocarcinoma according to clinical Gleason score and patient age.&quot; Sweat et Al. J Urol 2002; 168: 525–29.
** Conclusions: This study shows that for any given Gleason score the prostate cancer death rate is similar in older and younger patients with few to no co-morbidities. Men with a score of 7 to 10 were at 29% to 43% risk of death from prostate cancer even when cancer was diagnosed as late as age 74 years and treated surgically.

* {{PMID|12131304}} - &quot;Biochemical disease-free survival in men younger than 60 years with prostate cancer treated with external beam radiation.&quot; Rosser CJ et al. J Urol. 2002 Aug;168(2):536-41
**964 pts treated with RT alone. Biochemical failure defined per ASTRO consensus statement. 
**Median f/u 48 months. Of the 98 men &lt; 60 y.o. 46 (47%) had biochemical failure, whereas 261 (30%) of the 866 older men had biochemical failure.  5 and 7-year bDFS was 55% and 47% in younger men and 65% and 59% in older men (S.S.) In men &gt; 60 yo, PSA, Gleason score, and lower radiation doses were predictive of biochemical failure. 
** CONCLUSIONS: Men with prostate cancer who are 60 years or younger and treated with radiotherapy may be at significant risk for long-term biochemical failure.

*{{PMID|14532785}} - &quot;Improved biochemical disease-free survival of men younger than 60 years with prostate cancer treated with high dose conformal external beam radiotherapy.&quot; Zelefsky MJ et Al. J Urol. 2003 Nov;170(5):1828-32.
**Retrospective. 740 pts treated with 3D-CRT or IMRT to median dose of 75.6 Gy.  Biochemical failure per ASTRo consensus statement.
**Median f/u 88 months. Biochemical failure in 21%-22%; 5 and 7 year bDFS in 79-82% and 78-79%. No difference between young men (&lt; age 60) and older men. For young men who received &gt;= 81 Gy, 7-year relapse free survival 96%, 87% and 50^ for favorable, intermediate, and unfavorable risk pts. For young pts, most important predictor of biochemical relapse was dose &lt; 75.6 Gy followed by Gleason score &gt; 7. 
**Conclusions: Men &lt; 60 yrs old treated with high dose XRT have excellent outcome and do as well as older pts. Treating younger pts with conventional RT doses led to 8-fold increase in relapse rate.

==Prostatectomy after neoadjuvant hormones==
Hormones decrease the incidence of extracapsular extension and positive surgical margins.  However, this does not lead to improved freedom from biochemical failure or survival (unlike hormones combined with RT).
*{{PMID|11743286}} (Soloway), {{PMID|12230618}} (Aus)

*'''SWOG 9109''' - {{PMID|12394698}} &amp;mdash; &quot;Neoadjuvant therapy before radical prostatectomy for clinical T3/T4 carcinoma of the prostate: 5-year followup, Phase II Southwest Oncology Group Study 9109.&quot; Powell IJ et al. 
**61 pts. Phase II. T3-4N0
**PFS 70%. OS 90%.

==Adjuvant Chemotherapy==
:''For adjuvant hormonal therapy after RP, See also:'' [[Radiation_Oncology/Prostate/Hormones/Adjuvant_ADT#Adjuvant_androgen_deprivation]]
*'''SWOG 9921 / Intergroup''' (2000-2007) -- ADT vs. ADT + mitoxantrone
**Randomized. ''Closed prematurely after AML toxicity.'' 983 patients, radical prostatectomy, high risk features (GS &gt;=8, or pT3b-T4, or N1, or GS 7 and SM+, or PSA &gt;15 ng/ml. Had to have undetectable post-op PSA). Arm 1) ADT x2 years (bicalutamide 50mg QD + goserelin 10.8 mg SC q3 months) vs. Arm 2) ADT x2 years + mitoxantrone 12 mg/m2 q3W x6 cycles
**'''2008''' {{PMID|18349405}} -- &quot;Randomization reveals unexpected acute leukemias in Southwest Oncology Group prostate cancer trial.&quot; (Flaig TW, J Clin Oncol. 2008 Mar 20;26(9):1532-6.)
***Outcome: 3 cases of AML reported in 487 patients in mitoxantrone arm. Time-to-detection 13, 48, and 72 months. Trial stopped
***Conclusion: Highlights importantce of controlled trials to define safety and efficacy
**'''2011''' {{PMID|21502546}} -- &quot;Adjuvant Androgen Deprivation for High-Risk Prostate Cancer After Radical Prostatectomy: SWOG S9921 Study.&quot; (Dorff TB, J Clin Oncol. 2011 May 20;29(15):2040-5.)
***Final endpoints not yet available. In the ADT-alone control arm, 5-yr bFFS 92.5% and OS 95.9%. 
***Conclusion: consider use of adjuvant ADT in men with high risk prostate cancer</text>
      <sha1>i2i2f3qxrdslvk9dt42maw5u2jgcm1i</sha1>
    </revision>
  </page>
  <page>
    <title>Radiation Oncology/Prostate/Salvage RT</title>
    <ns>0</ns>
    <id>31199</id>
    <revision>
      <id>4675798</id>
      <parentid>3651696</parentid>
      <timestamp>2026-10-13T07:56:11Z</timestamp>
      <contributor>
        <username>Jcb</username>
        <id>90773</id>
      </contributor>
      <origin>4675798</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="18714" sha1="1ys620xgfo10ubvj4o4le1g93v7oz61" xml:space="preserve">{{:Radiation Oncology/Prostate:TOC}}
:''See also:'' [[Radiation Oncology/Prostate/Prostatectomy#Natural history after RP|Natural history of PSA after RP]] in [[Radiation Oncology/Prostate/Prostatectomy|Prostatectomy]]
:''See also:'' [[Radiation Oncology/Prostate/Adjuvant RT#Clinical and Pathologic Factors predicting recurrence|Clinical and Pathologic Factors predicting recurrence]] in [[Radiation Oncology/Prostate/Adjuvant RT|Adjuvant RT]]


== PSA Failure post-Radical Prostatectomy ==
* See [[Radiation Oncology/Prostate/PSA|PSA Failure]]

'''''Probability of positive bone scan with rising PSA:'''''
*'''MSKCC''', 2005 - {{PMID|15774789}} &amp;mdash; &quot;Pattern of prostate-specific antigen (PSA) failure dictates the probability of a positive bone scan in patients with an increasing PSA after radical prostatectomy.&quot; Dotan ZA et al. J Clin Oncol. 2005 Mar 20;23(9):1962-8.
**Article provides a handy nomogram.

==  Workup   ==

Bone scan: not recommended. Chance of positive bone scan is &lt;5% until PSA reaches 30-40. ({{PMID|9751361}})

Prostate re-biopsy is not necessary and The PSA level or threshold seemed to be 1.5 ng/mL.
* '''ASTRO consensus panel''' - {{PMID|10561174}} &amp;mdash; &quot;Consensus statements on radiation therapy of prostate cancer: guidelines for prostate re-biopsy after radiation and for radiation therapy with rising prostate-specific antigen levels after radical prostatectomy. American Society for Therapeutic Radiology and Oncology Consensus Panel.&quot; Cox et al. J Clin Oncol 1999 17:1155-1163.
** The panel judged that prostate re-biopsy is not necessary as standard follow-up care and that the absence of a rising PSA level after radiation therapy is the most rigorous end point of total tumor eradication.
** The panel noted that most data indicate the PSA level at time of salvage radiation may make a prognostic difference in outcome. The PSA level or threshold, based on the data presented, seemed to be 1.5 ng/mL.
** Based on the data presented at this conference, the dose should be 64 Gy or slightly higher with standard fractionation (1.8 or 2.0 Gy per fraction).
** There is no standard role for androgen suppression therapy in patients with or without radiation therapy for rising PSA values after prostatectomy.

'''''ProstaScint:''''' (indium 111-capromab pendetide)
*'''ProstaScint study group''' (1987-95)
**{{PMID|11920467}}, 2002 &amp;mdash; &quot;Clinical utility of indium 111-capromab pendetide immunoscintigraphy in the detection of early, recurrent prostate carcinoma after radical prostatectomy.&quot; Raj GV et al. Cancer. 2002 Feb 15;94(4):987-96.
**255 pts with rising PSA (but &lt; 4 ng/mL) after prostatectomy, who had negative bone scans and negative nodes, underwent ProstaScint scan. 
**Uptake in 72%; 31% in prostatic fossa only. Avg PSA 1.1 (all pts). Serum PSA did not correlate with pattern of positive scan.

== Outcome ==

Predictors of progression after salvage RT include Gleason Score 8-10, pre-RT PSA &gt;2, negative surgical margins, PSA-DT &lt;10 months and seminal vesicle invasion.


*'''Duke/Harvard; 2011''' (1988-2008) {{PMID|21437885}} -- &quot;Salvage radiation in men after prostate-specific antigen failure and the risk of death.&quot; (Cotter SE, Cancer. 2011 Mar 22. doi: 10.1002/cncr.25993. [Epub ahead of print])
**Retrospective. 519 men treated with RP at Duke, with PSA failure. Median F/U 11.3 years
**Outcome: Salvage RT reduction in all-cause mortality (HR 0.5, SS)
**Conclusion: Salvage RT is associated with a decreased risk in mortality
    
*'''Johns Hopkins; 2008''' (1982-2004) {{PMID|18560003}} -- &quot;Prostate cancer-specific survival following salvage radiotherapy vs observation in men with biochemical recurrence after radical prostatectomy.&quot; (Trock BJ, JAMA. 2008 Jun 18;299(23):2760-9.)
**Retrospective. Compared cohorts of pts who had biochemical failure after RP (n=635) from those who had 1) no salvage treatment (397 pts), 2) salvage RT alone (160), or 3) salvage RT + hormones (78). 
**Median f/u 6 yrs after recurrence. Death from prostate cancer in 18% (116 pts). Risk of death with observation, 22% (89 deaths); following salvage RT, 11% (18 deaths); following RT + hormones, 12% (9 deaths). Salvage RT with 3-fold increase in PC-specific survival (HR=0.32) and OS. Addition of hormonal therapy not associated with additional increase in survival. 
**Increase in survival with RT was limited to pts with PSA doubling time &lt; 6 months. Salvage RT after 2 yrs provided no survival advantage. Men who did not achieve bNED after salvage RT did not experience an increase in survival. 

*'''Multi-institutional''' 
**'''2004''' {{PMID|15026399}} -- ''Salvage radiotherapy for recurrent prostate cancer after radical prostatectomy.'' ('''2004 Stephenson AJ''', JAMA)
**Retrospective review of 501 patients at 5 US academic tertiary centers who received salvage RT; median follow-up 45 months
**4-year PFS was 45%
**No risk factors 4-year PFP was 77%
**Multivariate predictors of progression: 
***Gleason Score 8-10 (HR 2.6)
***Pre-RT post-relapse PSA &gt;2.0 (HR 2.3)
***Negative surgical margins (HR 1.9)
***PSA-DT &lt;10 months (HR 1.7)
***Seminal vesicle invasion (HR 1.4)
**&lt;u&gt;Conclusion&lt;/u&gt;: &quot;The Authors conducted a multicenter analysis of 501 patients undergoing salvage radiotherapy for an increasing PSA level after radical prostatectomy in order to reliably identify prognostic variables associated with a durable response. 
*** In this cohort, a Gleason score of 8 to 10, preradiotherapy PSA level greater than 2.0 ng/mL, negative surgical margins, PSADT of 10 months or less, and seminal vesicle invasion were significant predictors of disease progression despite salvage radiotherapy.
*** In their multivariable analysis, only preradiotherapy PSA level greater than 2.0 ng/mL had a significant association with progression after salvage radiotherapy. However, patients receiving treatment at very low PSA levels (&lt;0.6 ng/mL) had an improved outcome compared with patients with a preradiotherapy PSA level between 0.61 and 2.0 ng/mL. But the use of very low PSA thresholds risks overtreating patients whose PSA level is detectable due to residual benign prostatic tissue.
*** A patient with positive margins who relapses is more likely to benefit from salvage radiotherapy than a patient with negative margins, whose PSA level is more likely to represent distant disease.
**** patients with Gleason scores of 4 to 7 and a rapid PSADT, 67% will have a durable response to early salvage radiotherapy if they have '''positive surgical margins''', 
**** compared with 22% for those having '''negative margins'''.
*** Patients with a Gleason score of 4 to 7 and a slow PSADT (&gt;10 months) had a 4-year PFP greater than 70% when radiation was delivered early, when the PSA level was lower.
**Gives flowchart to predict progression-free probability after salvage RT based on Gleason score, Pre-RT PSA, Surgical margins, and PSADT.
**'''2007 Update''' {{PMID|17513807}} -- &quot;Predicting the outcome of salvage radiation therapy for recurrent prostate cancer after radical prostatectomy.&quot; (Stephenson AJ, J Clin Oncol. 2007 May 20;25(15):2035-41.)
***Updates previous report with larger cohort and longer follow up; 1540 pts from 17 centers, median f/u 53 months.
***Median pre-RT PSA 1.1, median doubling time 6.9 months.  Median 64.8 Gy.
***6-yr PFP 32%. By pre-RT PSA: 6-yr PFP 48% for PSA &lt;0.50, 40% 0.51-1.00, 28% 1.01-1.5, 18% &gt;1.5. 
***PSA response: nadir of &amp;le;0.10 achieved in 59% following RT
***Nomogram and flowchart to predict PFP.
**'''2016: New Contemporary Update''' {{PMID|27528718}} -- &quot;Contemporary Update of a Multi-Institutional Predictive Nomogram for Salvage Radiotherapy After Radical Prostatectomy.&quot; (Tendulkar RD, J Clin Oncol. 2016 Aug 15. [Epub ahead of print])
***New cohort, including 2460 pts from 10 centers. Median f/u 5 yrs. Median pre-SRT PSA 0.5
***Includes pts with lower pre-SRT PSA values &lt;= 0.20 (18% of pts) who were excluded from the previous cohorts.
***On multivariable analysis, pre-SRT PSA, GS, EPE, SVI, surgical margins, ADT use, and SRT dose were associated with FFBF. Pre-SRT PSA, GS, SVI, surgical margins, and ADT use were associated with DM, whereas EPE and SRT dose were not.
***Conclusion: &quot;Early SRT at low PSA levels after RP is associated with improved FFBF and DM rates. Contemporary nomograms can estimate individual patient outcomes after SRT in the modern era.&quot;


*{{PMID|7513108}} - &quot;Evaluation of serum prostate-specific antigen velocity after radical prostatectomy to distinguish local recurrence from distant metastases.&quot; Partin et al. Urology. 1994 May;43(5):649-59. 
**Proposed criteria to distinguish local recurrence from distant metastases for patients with an increasing PSA level after radical prostatectomy. A Gleason score of 8 to 10, seminal vesicle invasion, positive lymph nodes, and a rapid PSA velocity were associated with distant metastases. Local recurrence was more frequently observed in patients with low-grade and organ-confined disease, a slow PSA velocity, and a disease free interval greater than 3 years, suggesting that isolated local recurrence has a low metastatic potential.


*'''Virginia Commonwealth University and University of Florida''' -  {{PMID|15145145}} &amp;mdash; ''Comparison Of Adjuvant Versus Salvage Radiotherapy Policies For Postprostatectomy Radiotherapy''. Hagan et al. Int. J. Radiation Oncology Biol. Phys., Vol. 59, No. 2, pp. 329–340,''' 2004'''
** The Authors compared the long-term results of postprostatectomy radiotherapy (RT) from two institutions, one adapting a prospective policy of adjuvant RT (69 patients) and the other salvage RT (88 patients). The salvage group underwent RT after longer postoperative intervals (median, 40.3 vs. 2.9 months; p &lt;0.0001) and had higher prostate-specific antigen (PSA) values before starting RT (4.5 vs. 0.86 ng/mL; p = 0.003). Both groups were routinely treated to a minimal total dose of 60 Gy. 
** &lt;u&gt;Results: &lt;/u&gt; Of the 69 patients referred for adjuvant RT, 22 (32%) had nonzero PSA values before RT. Multivariable modeling of BRFS found '''only the PSA value before RT to be statistically significant (p &lt;0.0001)'''. RT after prostatectomy was equally effective in either setting when the pre-RT PSA level was &lt;1 ng/mL. '''When the PSA value before RT was &gt;1 ng/mL, the 5-year BRFS for each group was inferior.'''
**&lt;u&gt;Conclusion&lt;/u&gt;:  Durable biochemical control is re-established in approximately 50% of patients who undergo salvage treatment, and 70–80% of patients in adjuvant series have disease control. Although the adjuvant treatment policy was associated with significantly improved BRFS, this was attributable to low pre-RT PSA values. When the treatment groups were stratified for pre-RT PSA level, the differences in BRFS were not statistically significant. Patients with a rising PSA level after prostatectomy, regardless of their initial risk, should receive prompt referral for RT.

*'''University of Heidelberg (Germany)''', 2007 (1991-2004)
**{{PMID|17275204}} &amp;mdash; &quot;Long-term results and predictive factors of three-dimensional conformal salvage radiotherapy for biochemical relapse after prostatectomy.&quot; Neuhof D et al.  Int J Radiat Oncol Biol Phys. 2007 Jan 31. [Epub ahead of print]
**171 pts. Median f/u 39 mos. 
**PSA decreased after RT in 82.5%. 5-yr bRFS 35.1%. On multivar. analysis, only Gleason score and pre-RT PSA level were predictive of PSA recurrence.

*'''Mayo''', 2000 (1987-96)
**{{PMID|10687990}} &amp;mdash; &quot;Radiotherapy for isolated serum prostate specific antigen elevation after prostatectomy for prostate cancer.&quot; Pisansky TM et al. J Urol. 2000 Mar;163(3):845-50. 
**166 pts. Median f/u 52 mos. 
**5-yr bRFS 46%. Predictors for relapse: SV invasion, tumor grade, pre-RT PSA.

'''''Use of ProstaScint imaging:'''''
*'''University of Chicago, 2008''' (1988-2005) 
**{{PMID|18234446}} &amp;mdash; &quot;Salvage radiotherapy after postprostatectomy biochemical failure: does pretreatment radioimmunoscintigraphy help select patients with locally confined disease?&quot; (Liawu SL, Int J Radiat Oncol Biol Phys. 2008 Aug 1;71(5):1316-21.)
**Retrospective, 82 pts. Compared outcomes for patients undergoing salvage RT with or without the use of pre-RT ProstaScint (RIS) scans. All pts had persistently elevated or increasing post-op PSA &gt;0.1. Median pre-RT PSA 0.637.  3% had negative CT scan and/or bone scan. 47 pts had pre-RT ProstaScint scan. Pts were not included on the study if they had a RIS scan showing distant disease. RT was to median dose 66 Gy and included prostate bed (91% with RIS, 83% without) or pelvis + prostate bed (6% and 17%).
**Patients who had prostate bed-only uptake on RIS did not have improved outcomes, with biochemical control of 40% at 5 years. Positive margins were associated with improved control.
**Patients

==RT + Hormonal Therapy==
'''''Preliminary Trials:'''''
*'''[[Radiation Oncology/RTOG Trials/9601|RTOG 96-01]]''' (1998-2003) -- Post-op RT +/- Casodex 150 mg x 2 years for pT3 with PSA elevation.
**pT3N0 (or pT2N0 with positive surgical margin) with post-op PSA 0.2-4.0. Randomized to prostate bed RT 64.8 Gy +/- casodex beginning concurrent with RT.
*ASTRO 2010 Report with 7.1 years of follow up:
**Freedom from PSA progression at 7 yrs: 57% vs. 40% (p&lt;0.01)
***True across all Gleason scores
**Cumulative incidence of metastatic disease at 7 years: 7.4% vs. 12.6% (p&lt;0.04)
**Not reporting survival yet given too few events
**Grade 3/4 Toxicity:
***GI: 2.3% vs. 1.4%
***Bladder: 5.9% vs 5.0%
***Gynecomastia (predominantly grades 1/2): 89% vs. 15%

==Radiation Volume==
'''''Whole Pelvis vs Prostate Bed Only:'''''
*'''Stanford, 2007''' (1985-2005) {{PMID|17459606}} -- &quot;Radiotherapy after prostatectomy: improved biochemical relapse-free survival with whole pelvic compared with prostate bed only for high-risk patients.&quot; (Spiotto MT, Int J Radiat Oncol Biol Phys. 2007 Sep 1;69(1):54-61.)
**Retrospective. 160 pts, treated with adjuvant (21 pts) or salvage RT (139). Androgen suppression in 87. 114 pts considered 'high risk' for LN+ based on: GS &gt;= 8, PSA &gt; 20, SV+, prostate capsule involvement, or pN+. Of the high risk group, 72 treated with WPRT and 42 with RT to prostate bed only.
**Benefit of WPRT limited to high risk pts: 5-yr BRFS 47% (WPRT) vs 21% (PO). Benefit for androgen suppression when given concurrently with RT.
**Conclusion: WPRT confers superior bRFS compared with PBRT for high-risk patients receiving adjuvant or salvage RT after radical prostatectomy. This advantage was observed only with concurrent TAS.


==Timing of Salvage RT==
'''''Systematic Reviews:'''''
*'''2012: UCLA''' {{PMID|22795730}} -- &quot;The timing of salvage radiotherapy after radical prostatectomy: a systematic review.&quot; (King CR, Int J Radiat Oncol Biol Phys. 2012 Sep 1;84(1):104-11.)
**Review of 41 studies (published 1995-2012) including 5597 patients.
**PSA level before SRT and RT dose associated with RFS. Average 2.6% loss of RFS for each incremental 0.1 PSA at the time of SRT. 
**Conclusion: &quot;This study provides Level 2a evidence for initiating SRT at the lowest possible PSA. Dose escalation is also suggested by the data.&quot;

==High Dose Salvage RT==
''high dose in this context refers to a dose &gt;= 66 Gy''

*'''2012: MSKCC''' (1988-2007) {{PMID|22300563}} -- &quot;Long-term outcomes after high-dose postprostatectomy salvage radiation treatment.&quot; (Goenka A, Int J Radiat Oncol Biol Phys. 2012 Sep 1;84(1):112-8.)
**285 pts treated with salvage RT. Median PSA before SRT 0.4. 60 pts (21%) had MRI-detected local recurrence. 42 pts had pathologic confirmation of local recurrence.
**95% were treated to a dose &gt;= 66 Gy; 72% received &gt;= 70 Gy. ADT used in 31%.
**Median f/u 60 mo. 7-yr bRFS 37%, DMFS 77%. Predictors of recurrence: vascular invasion, negative margins, presalvage PSA &gt; 0.4, no use of ADT, Gleason &gt;= 7, and +SV. RT dose &gt;= 70 Gy was not associated with improved biochemical control. PSA-DT &lt; 3 months was the only indep. predictor of DM. Trend toward benefit of dose &gt;= 70 Gy in decreasing clinical local failure in pts who had radiographically visible local disease at the time of SRT.
**Conclusion: &quot;Salvage RT provides effective long-term biochemical control and freedom from metastasis in selected patients presenting with detectable PSA after prostatectomy. Androgen-deprivation therapy was associated with improvement in biochemical progression-free survival. Clinical local failures were rare but occurred most commonly in patients with greater burden of disease at time of SRT as reflected by either radiographic imaging or a greater PSA level. Salvage radiation doses ≥70 Gy may ultimately be most beneficial in these patients, but this needs to be further studied.&quot;

==PSA measurements during RT==
*{{PMID|12240547}} &amp;mdash; &quot;The value of PSA measurements at 30 Gy, 50 Gy and 60 Gy for dose limitation in patients with radiotherapy for PSA increase after radical prostatectomy.&quot; Wiegel T et al. Strahlenther Onkol. 2002 Aug;178(8):422-5.
**41 pts treated to 66.6 Gy. At 30 Gy, 26% of those who would eventually respond still had a rising PSA, but at 50 and 60 Gy, 93% had decreasing PSA. In those who would fail, 75% and 88% had rising PSA at 50 and 60 Gy.

*{{PMID|11483332}}  &amp;mdash; &quot;Serum PSA evaluations during salvage radiotherapy for post-prostatectomy biochemical failures as prognosticators for treatment outcomes.&quot; Do T et al.  Int J Radiat Oncol Biol Phys. 2001 Aug 1;50(5):1220-5.
**41 patients with biochemical failure after RP had PSA were treated to 59.4-66.6 Gy without hormone therapy. PSA checked at 30 Gy and 45 Gy.  
**Rising PSA at 45 Gy significantly predicted for poor outcome.  PSA at 30 Gy did not significantly predict for disease outcome.

==Toxicity==
*'''Mayo, 2009''' (1987-2003) {{PMID|19766337}} -- &quot;Late toxicity after postprostatectomy salvage radiation therapy.&quot; (Peterson JL, Radiother Oncol. 2009 Nov;93(2):203-6.)
**Retrospective. 308 pts treated at Mayo-Rochester or Mayo-Jacksonville. Median RT dose 64.8 Gy; no IMRT. Hormonal therapy in 19%.
**Late complication (any grade) in 14% by 5 yrs. Grade 3-4 complication: 4 pts (0.7%). GU toxicity: 3.9% gr 2 urethral strictures, 3 pts with gr 3 cystitis.  GI: 1 pt with gr 4 rectal complication.

==Radiation Injury==
*'''Toronto Sunnybrook''' {{PMID|15936551}} -- ''Effect of androgen suppression on hemoglobin in prostate cancer patients undergoing salvage radiotherapy plus 2-year buserelin acetate for rising PSA after surgery.'' (''' 2005 Chander S''', Int J Radiat Oncol Biol Phys.)
**&lt;u&gt;Conclusion&lt;/u&gt;: &quot;Two-year AS resulted in a statistically significant drop in the mean Hb, but had no clinically apparent adverse effect. The pattern of Hb change was similar to that of testosterone change.&quot;</text>
      <sha1>1ys620xgfo10ubvj4o4le1g93v7oz61</sha1>
    </revision>
  </page>
  <page>
    <title>TI-Basic Z80 Programming</title>
    <ns>0</ns>
    <id>48374</id>
    <revision>
      <id>4675789</id>
      <parentid>4057816</parentid>
      <timestamp>2026-10-13T06:27:56Z</timestamp>
      <contributor>
        <username>Rex Valerio</username>
        <id>3628187</id>
      </contributor>
      <comment>Add missing word in Programming Games contents description</comment>
      <origin>4675789</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="4694" sha1="cehp7trze0na6wicz7ty7ua3yri9dcv" xml:space="preserve">[[File:TI-84 Plus.svg|150px|right|Illustration of a TI-84 Plus]]
{{see also|TI-Basic 84 Programming|TI-Basic 89 Programming}}
This book covers the Z80 processor's version of '''TI-BASIC'''.

== Overview ==
TI-BASIC is a simple programming language used on Texas Instruments (TI) graphing calculators. The language is quite simple, and integrates many normal graphing calculator commands (such as storing variables or graphing) into its code.

TI-BASIC is very easy to program, especially when compared to assembly, which is the other main language that can be used to program TI graphing calculators. Also, programs written in TI-BASIC can have small file sizes, since common functions can be programmed with just one character (1-2 bytes), such as &lt;code&gt;If&lt;/code&gt; or &lt;code&gt;Menu(&lt;/code&gt;. However, this makes execution of TI-BASIC programs very slow, since each line of code must be read and parsed before execution. Despite the crawling speed of TI-BASIC, it's appropriate for many simple programs.

== Versions of TI-BASIC ==
There are two main versions of TI-BASIC in use today:

*The TI-BASIC that comes with the TI-89, TI 89 Titanium, TI-92, TI-92 Plus and Voyage 200 calculators. This is the more powerful version of TI-BASIC.

*The TI-BASIC that comes with the TI-83, TI-83+, TI-83+ Silver Edition, TI-84+ and TI-84+ Silver Edition calculators. This is a less powerful version of TI-BASIC, but is still fairly versatile. '''This Wikibook covers this version.'''

Please note that within these two versions of TI-BASIC, there are slight variations.

== Table of Contents ==
{{Book search}}
{{Print version}}
{{Wikipedia|TI-Basic}}
This table of contents arranges the sections in the best order possible for those who are trying to learn the language. However, if you are already familiar with TI-BASIC, you may decide to skip certain sections.

{{TI-Basic/CLink|Introduction|What this book covers and how to read it}}{{stage short|75%}}
{{TI-Basic/CLink|Necessary Items|What you need to begin programming}}{{stage short|75%}}
{{TI-Basic/CLink|Hello, World!|How to write your first program}}{{stage short|100%}}
{{TI-Basic/CLink|Basic Variables|How to use reals, strings, and lists}}{{stage short|100%}}
{{TI-Basic/CLink|Output|How to display values and strings to the screen}}{{stage short|100%}}
{{TI-Basic/CLink|Input|How to get and use user input}}{{stage short|100%}}
{{TI-Basic/CLink|Conditional Statements|How to dynamically change the program}}{{stage short|100%}}
{{TI-Basic/CLink|Loops|How to repeat sections of code}}{{stage short|100%}}
{{TI-Basic/CLink|Advanced Variables|How to use other variable types}}{{stage short|100%}}
{{TI-Basic/CLink|GetKey|How to use precise user input via keypresses}}{{stage short|100%}}
{{TI-Basic/CLink|Goto and Lbl|How to jump to different sections in code}}{{stage short|100%}}
{{TI-Basic/CLink|Menus|Display several options for user selection}}{{stage short|100%}}
{{TI-Basic/CLink|Errors|How to handle when a program encounters an error}}{{stage short|75%}}
{{TI-Basic/CLink|Tips, Tricks and Optimizations|Use these tricks to reduce your code's footprint}}{{stage short|75%}}
{{TI-Basic/CLink|Advanced Programming|How to apply advanced tricks to your program}}{{stage short|75%}}
{{TI-Basic/CLink|Programming Games|How to program simple games}}{{stage short|50%}}
#[[/List of Commands|Appendix A: List of Commands]] {{stage short|50%}}

== External Links ==

=== Learning and Programming TI-BASIC ===
Here are the manuals that come with TI calculators from the Texas Instruments website, which can be used to learn TI-BASIC.

*[http://education.ti.com/us/product/tech/83/guide/83guideus.html TI 83] (See Chapter 16)
*[http://education.ti.com/us/product/tech/83p/guide/83pguideus.html TI 83 Plus] (See Chapter 16)
*[http://education.ti.com/educationportal/sites/US/productDetail/us_ti84pse.html?bid=6 TI 83 Plus Silver Edition] (See Chapter 16)
*[http://education.ti.com/us/product/tech/84pse/guide/84pseguideus.html TI 84 Plus] (See Chapter 16)
*[http://education.ti.com/us/product/tech/84pse/guide/84pseguideus.html TI 84 Plus Silver Edition] (See Chapter 16)
*[http://education.ti.com/us/product/tech/89/guide/89guideus.html TI 89] (See Chapter 17)
*[http://education.ti.com/educationportal/sites/US/productDetail/us_ti89ti.html?bid=6 TI 89 Titanium] (See Chapter 18)
*[http://education.ti.com/educationportal/sites/US/productDetail/us_ti92p.html?bid=6 TI 92 Plus] (See Chapter 17)
*[http://education.ti.com/educationportal/sites/US/productDetail/us_v200.html?bid=6 Voyage 200] (See Chapter 18)

{{shelves|Calculators|BASIC programming language}}
{{alphabetical|T}}
{{status|75%}}
__NOTOC__ __NOEDITSECTION__
[[nl:Programmeren in TI-Basic]]</text>
      <sha1>cehp7trze0na6wicz7ty7ua3yri9dcv</sha1>
    </revision>
  </page>
  <page>
    <title>OpenSSH/Cookbook/Public Key Authentication</title>
    <ns>0</ns>
    <id>51866</id>
    <revision>
      <id>4675736</id>
      <parentid>4674771</parentid>
      <timestamp>2026-10-12T13:47:34Z</timestamp>
      <contributor>
        <username>Larsnooden</username>
        <id>430753</id>
      </contributor>
      <minor />
      <comment>typo</comment>
      <origin>4675736</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="78902" sha1="nf41g6dj9jxix31heft71tm9mr9r1t3" xml:space="preserve">&lt;noinclude&gt;{{simple chapter navigation|previous=File Transfer with SFTP|next=Certificate-based Authentication}}&lt;/noinclude&gt;
&amp;nbsp;

Authentication keys can improve efficiency, if done properly.  As a bonus advantage, the passphrase and private key never leave the client&lt;ref name=&quot;RFC4252§7&quot;&gt;{{cite web |url=https://tools.ietf.org/html/rfc4252#section-7 |title=The Secure Shell (SSH) Authentication Protocol |publisher=IETF |year=2006| accessdate=2015-05-06}}&lt;/ref&gt;.  Key-based authentication is generally recommended for outward facing systems so that password authentication can be turned off.  


==Key-based authentication==

OpenSSH can use public key cryptography for authentication.  In public key cryptography, encryption and decryption are asymmetric.  The keys are used in pairs, a public key to encrypt and a private key to decrypt.  The [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)] utility can make RSA, Ed25519, MLDSA44-Ed25519, ECDSA, Ed25519-SK, or ECDSA-SK keys for authenticating.  Even though DSA keys can still be made, being exactly 1024 bits in size, they are no longer recommended and should be avoided.  RSA keys are allowed to vary from 1024 bits on up.  The default is now 3072.  However, there is only limited benefit after 2048 bits and that makes elliptic curve algorithms preferable.  ECDSA can be 256, 384 or 521 bits in size.  Ed25519, Ed25519-SK, and ECDSA-SK keys each have a fixed length of 256 bits.  Shorter keys are faster, but less secure.  Longer keys are much slower to work with but provide better protection, up to a point.  

Keys can be named to help remember what they are for.  Because the key files can be named anything it is possible to have many keys each named for different services or tasks.  The comment field at the end of the public key can also be useful in helping to keep the keys sorted, if you have many of them or use them infrequently.  

The process of key-based authentication uses these keys to make a couple of exchanges using the keys to encrypt and decrypt some short message.  At the start, a copy of the client's public key is stored on the server and the client's private key is on the client, both stay where they are.  The private key never leaves the client.  As the client first contacts the server, the server responds by using the client's public key to encrypt a random number and return that encrypted random number as a challenge to the client.  The client responds to the challenge by using the matching private key to decrypt the message and extract the random number.  The client then makes an MD5 hash of the session ID along with the random number from the challenge and returns that hash to the server.  The server then makes its own hash of the session ID and the random number and compares that to the hash returned by the client.  If there is a match, the login is allowed.  If there is not a match, then the next of any public keys on the server registered as belonging to the same account is tried until either a match is found or all the keys have been tried or the maximum number of failures has been reached. &lt;ref name=&quot;How Key Challenges Work&quot;&gt;{{cite web | url=http://www.unixwiz.net/techtips/ssh-agent-forwarding.html#chal | title=An Illustrated Guide to SSH Agent Forwarding | author=Steve Friedl | date=2006-02-22 | accessdate=2013-04-27 | publisher=Unixwiz.net }}&lt;/ref&gt;

When an agent is used on the client side to manage authentication, the process is similar.  The difference is that [http://man.openbsd.org/ssh.1 ssh(1)] passes the challenge off to the agent which then calculates the response and passes it back to [http://man.openbsd.org/ssh.1 ssh(1)] which then passes the agent's response back to the server.  

===Basics of Public Key Authentication===

A matching pair of SSH keys, one public and one private, is needed for public key authentication.  The [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)] utility is used to make such a key pair.  Out of that pair the public key must be properly stored on the remote host before using key-based authentication.  The default location for it is the designated '''authorized_keys''' file, usually one such file resides inside each remote user account.  The private key stays stored safely on the client.  

Once the keys have been prepared and the remote account configured, they can be used for login.  Before starting, there must already be an account on the remote system.  The details of doing that are outside of the scope of this book.  However, once you have a remote account, there are four steps to set up key-based authentication for it:

'''1''') Prepare a directory on the client (say a laptop or a desktop) where the keys will stay, if there isn't one already.  For example, if the '''.ssh''' directory is not on the client machine, create it and set the permissions correctly.  It is important that it not be writable by any account except its owner:
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ mkdir ~/.ssh/
$ chmod 0700 ~/.ssh/
&lt;/syntaxhighlight&gt;

'''2''') Create a key pair inside the designated directory.  The example here creates an Ed25519 key pair in the directory '''~/.ssh'''.  The option '''-t''' decides the key type and the option '''-f''' assigns the key file a name.  It is good to give key files descriptive names, especially if larger numbers of keys are managed.  Below, the public key will be named '''fred_example_org_ed25519.pub''' and the private key will be called '''fred_example_org_ed25519'''.  Lastly, the '''-C''' option is used to embed a descriptive comment inside the private key itself.  The comment is useful for figuring out later what the key is for when one has many keys or a lot of time has passed or both.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -t ed25519 -f ~/.ssh/fred_example_org_ed25519 \
        -C &quot;from fred's laptop to server.example.org&quot;
&lt;/syntaxhighlight&gt;

Be sure to enter a solid passphrase so that the private key gets encrypted using 128-bit AES.  That way the private key can only be read or used when the passphrase is given.  

Ed25519, Ed25519-SK, and ECDSA-SK keys have fixed lengths.  For RSA and ECDSA keys, the '''-b''' option sets the number of bits used for those kinds of keys.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -o -b 4096 -t rsa -f ~/.ssh/fred_example_org_rsa \
        -C &quot;from fred's laptop to server.example.org&quot;
&lt;/syntaxhighlight&gt;

Since 6.5 a new private key format is available using a [http://man.openbsd.org/bcrypt.3 bcrypt(3)] key derivative function (KDF) to better protect keys at rest.  This new format is always used for Ed25519 keys, and sometime in the future will be the default for all keys.  But for right now it may be requested when generating or saving existing keys of other types via the '''-o''' option in [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)].  

Details of the new format are found in the source code in the file '''PROTOCOL.key'''.

'''3''') Get the keys to the right places.  Transfer only the public key to remote machine.  The following assume the default locations for the authorized keys as specified in the server's configuration file by the '''AuthorizedKeysFile''' directive.  

'''3a''') If the utility &lt;code&gt;ssh-copy-id&lt;/code&gt; exists, and if password authentication is allowed, then it can be used to put the public key into place on the remote system.  The ''.pub'' is optional here, the script will figure it out if omitted. 
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-copy-id -i ~/.ssh/fred_example_org_ed25519 fred@server.example.org
&lt;/syntaxhighlight&gt;

If that script was successful in transferring the public key, then go on to step 4 below and test the key.  If not, then try transferring the public key manually as described in step 3b next.

'''3b''') Or the public key can be put in place manually on the remote machine.  For that the remote '''.ssh''' directory is needed, and within that a special file to store the public keys, the default file name is '''authorized_keys'''.  If either the '''authorized_keys''' file or '''.ssh''' directory do not exist on the remote machine, they need to be created.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ mkdir -m 700 ~/.ssh/
$ touch ~/.ssh/authorized_keys
$ chmod 0600 ~/.ssh/authorized_keys
$ nano -w ~/.ssh/authorized_keys
&lt;/syntaxhighlight&gt;

Then any editor which does not wrap long lines can be used to add the public key.  However the '''authorized_keys''' file is edited to add the key, the key itself must be in the file whole and unbroken on a single  line.  For example, [http://linux.die.net/man/1/nano nano(1)] can be started with the '''-w''' option to prevent wrapping of long lines.  (Another way to set line wrapping permanently in [http://linux.die.net/man/1/nano nano(1)] is by editing [http://linux.die.net/man/5/nanorc nanorc(5)].)  

If the key pair is not already on the client, transfer both the public and private keys there.  It is usually best to keep both the public and private keys together in the directory '''~/.ssh/''', though the public key is not always needed on the client after this step and could even be regenerated if it is ever needed again.  

'''4''') Test the keys

While remaining logged in via the first terminal, use the client system to open another window and in it start another SSH session and try authenticating to the remote machine from the client using the private key.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -i ~/.ssh/fred_example_org_ed25519 -l fred server.example.org
&lt;/syntaxhighlight&gt;

The option '''-i''' tells [http://man.openbsd.org/ssh.1 ssh(1)] which private key to try.  
Only after verifying that the key-based authentication works should you close the original window.  

It is possible to make permanent shortcuts on the client using [http://man.openbsd.org/ssh_config.5 ssh_config(5)], explained further below, once key-based authentication is working.  In particular, see the '''IdentityFile''',  '''IdentitiesOnly''', and '''AddKeysToAgent''' configuration directives, to name three.  

It is also a good idea to turn off password authentication, if and only if key-based authentication is setup for all the necessary remote accounts.  

➥ '''Troubleshooting of Key-based Authentication''':

If the server refuses to accept the key and fails over to the next authentication method (e.g.: &quot;Server refused our key&quot;), then there are several possible mistakes to look for on the server side.  

One of the most common errors is that the file and directory permissions are wrong.  The authorized keys file must be owned by the user in question and not be group writable.  Nor may the key file's directory be group or world writable.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ chmod u=rwx,g=rx,o= ~/.ssh
$ chmod u=rw,g=,o=  ~/.ssh/authorized_keys 
&lt;/syntaxhighlight&gt;

Another mistake that can happen is if the key inside the '''authorized_keys''' file on the remote host is broken by line breaks or has other whitespace in the middle.  That can be fixed by joining up the lines and removing the spaces or by recopying the key more carefully.  

And, though it should go without saying, the halves of the key pair need to match.  The public key on the server needs to match the private key held on the client.  If the public key is lost, then a new one can be generated with the '''-y''' option, but not the other way around.  If the private key is lost, then the public key should be erased as it is no longer of any use.  If many keys are in use for an account, it might be a good idea to add comments to them.  On the client, it can be a good idea to know which server the key is for, either through the file name itself or through the comment field.  A comment can be added using the '''-C''' option.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -t ed25519 -f ~/.ssh/fred_example_org_ed25519 -C &quot;web server mirror&quot;
&lt;/syntaxhighlight&gt;

On the server, it can be important to annotate which client they key is from if there is more than one public key there in an account.  There the comment can be added to the authorized keys file on the server in the last column if a comment does not already exist.  Again, the format of the authorized keys file is given in the manual page for [http://man.openbsd.org/sshd.8 sshd(8)] in the section &quot;AUTHORIZED_KEYS FILE FORMAT&quot;.  If the keys are not labeled they can be hard to match, which might or might not be what you want.  

====Associating Keys Permanently with a Server====

A key can be specified at run time, but to save retyping the same paths again and again, the '''Host''' directive in [http://man.openbsd.org/ssh_config.5 ssh_config(5)] can apply specific settings to a target host.  In this case, by changing '''~/.ssh/config''' it is possible to assign particular keys to be tried automatically whenever making a connection to that specific host.  After adding the following lines to '''~/.ssh/config''', all that's needed is to type &lt;code&gt;ssh ''web1''&lt;/code&gt; to connect with the key for that server.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Host web1
	Hostname 198.51.100.32
	IdentitiesOnly yes
	IdentityFile /home/fred/.ssh/web_key_ed25519
&lt;/syntaxhighlight&gt;

The '''~/.ssh/config''' below uses different keys for ''server'' versus ''server.example.org'',  regardless whether they resolve to the same machine.   This is possible because the host name argument given to [http://man.openbsd.org/ssh.1 ssh(1)] is not converted to a canonicalized host name before matching.

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Host server
	IdentitiesOnly yes
	IdentityFile /home/fred/.ssh/key_a_rsa

Host server.example.org
	IdentitiesOnly yes
	IdentityFile /home/fred/.ssh/key_b_rsa  
&lt;/syntaxhighlight&gt;

In this example the shorter name is tried first, but of course less ambiguous shortcuts can be made instead.  The configuration file gets parsed on a first-match basis.  So the most specific rules go at the beginning and the most general rules go at the end.  

====Encrypted Home Directories====

When using encrypted home directories the keys must be stored in an unencrypted directory.  That means somewhere outside the actual home directory which means [http://man.openbsd.org/sshd.8 sshd(8)] needs to be configured appropriately to find the keys in that special location.  

Here is one method for solving the access problem.  Each user is given a subdirectory under '''/etc/ssh/keys/''' which they can then use for storing their '''authorized_keys''' file.  This is set in the server's configuration file '''/etc/ssh/sshd_config'''

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
AuthorizedKeysFile      /etc/ssh/keys/%u/authorized_keys
&lt;/syntaxhighlight&gt;

Setting a special location for the keys opens up more possibilities as to how the keys can be managed and multiple key file locations can be specified if they are separated by whitespace.  The user does not have to have write permissions for the '''authorized_keys''' file.  Only read permission is needed to be able to log in.  But if the user is allowed to add, remove, or change their keys, then they will need write access to the file to do that.  

One symptom of having an encrypted home directory is that key-based authentication only works when you are already logged into the same account, but fails when trying to make the first connection and log in for the first time.

Sometimes it is also necessary to add a script or call a program from '''/etc/ssh/sshrc''' immediately after authentication to decrypt the home directory.

====Passwordless Login====

One solution for passwordless logins is to still have a passphrase and work with an authentication agent in conjunction with a single-purpose key.  Most desktop environments launch an SSH agent automatically these days.  It will be visible in the '''SSH_AUTH_SOCK''' environment variable if it is.  On accounts with an agent, [http://man.openbsd.org/ssh-add.1 ssh-add(1)] can load private keys into an available agent.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-add ~/.ssh/fred_example_org_ed25519
&lt;/syntaxhighlight&gt;

Thereafter, the client will automatically check the agent for the key when appropriate.  If there are many keys in the agent, it will become necessary to set '''IdentitiesOnly'''.  See the above section on using '''~/.ssh/config''' for that.  See [[OpenSSH/Cookbook/Public_Key_Authentication#Key-based_Authentication_Using_an_Agent|Key-based Authentication Using an Agent]] below.  

Another, riskier, way of allowing passwordless logins is to follow the steps above, but simply do not enter a passphrase when asked for one while creating the key.  Note that using keys that lack a passphrase is very risky, so the key files should be very well protected and kept track of, and ideally locked down with a '''command=''' option or '''ForceCommand''' directive on the server.  That includes those keys which will only be used as single-purpose keys as described below.  

Timely key rotation becomes especially important.  In general, it is not a good idea to make a key without a passphrase.

====Requiring Both Keys and a Password====

While users should have strong passphrases for their keys, there is no way to enforce or verify that.  Indeed, since neither the private key nor its the passphrase ever leave the client machine there is nothing that the server can do to have any influence over that.  Instead, it is possible to require both a key and a password.  Starting with OpenSSH 6.2, it is possible for the server to require multiple authentication methods for login using the '''AuthenticationMethods''' directive.   
&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
AuthenticationMethods publickey,password
&lt;/syntaxhighlight&gt;

This example from [http://man.openbsd.org/sshd_config.5 sshd_config(5)] requires that users first authenticate using a key and it only queries for a password if the key succeeds.  Thus with that configuration it is not possible to get to the system password prompt without first authenticating with a valid key.  Changing the order of the arguments changes the order of the authentication methods.

====Requiring Two or More Keys====

Since OpenSSH 6.8, the server now remembers which public keys have been used for authentication and refuses to accept previously-used keys.  This allows a set up requiring that users authenticate using two different public keys, maybe one in the file system and the other in a hardware token. 

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
AuthenticationMethods publickey,publickey
&lt;/syntaxhighlight&gt;

The '''AuthenticationMethods''' directive, whether for keys or passwords, can also be set on the server under a '''Match''' directive to apply only to certain groups or situations.

====Requiring Certain Key Types For Authentication====

Also since OpenSSH 6.8, the '''PubkeyAcceptedKeyTypes''' directive, later changed to '''PubkeyAcceptedAlgorithms''', can specify which key algorithms are accepted for authentication.  Those not in the comma-separated pattern list are not allowed.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
PubkeyAcceptedAlgorithms ssh-ed25519*,ssh-rsa*,ecdsa-sha2*,sk-ssh-ed25519*,sk-ecdsa-sha2*
&lt;/syntaxhighlight&gt;

Either the actual key types or a pattern can be in the list.  Spaces are not allowed in the pattern list.  The exact list of key types supported for authentication can be found by the '''-Q''' option using the client.  The following two lines are equivalent.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -Q key-sig | sort

$ ssh -Q PubkeyAcceptedAlgorithms | sort
&lt;/syntaxhighlight&gt;

For host-based authentication, it is the '''HostbasedAcceptedAlgorithms''' directive which determines the key types which are allowed for authentication.

===Key-based Authentication Using the AuthorizedKeysCommand Directive===

It is possible to use a program or script to look up public keys rather than keeping them in a static file or files.  Any command called by the '''AuthorizedKeysCommand''' directive needs to either produce a syntactically correct public key while returning the exit code for a successful run or else return the exit code for failure.  The string sent to '''stdout''' will then be processed as part of the authentication work flow.  

Here is a shell script&lt;ref name=&quot;janpietmens&quot;&gt;{{cite web |url=https://jpmens.net/2025/03/25/authorizedkeyscommand-in-sshd/ |title=SSH keys from a command: sshd's AuthorizedKeysCommand directive |accessdate=2025-04-04 |date=2025-03-25 | author=Jan-Piet Mens }}&lt;/ref&gt; at its simplest, without constraints, demonstrating a public key lookup:

&lt;syntaxhighlight lang=&quot;shell&quot;&gt;
#!/bin/sh

echo &quot;ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIKs/UouletvojgB1YeRZ4MY6iRblQ2ERDuNhQO4tOvdL&quot;

exit 0
&lt;/syntaxhighlight&gt;

For authentication to succeed, the script must return exit code 0  (success) after sending the syntactically correct matching public key to '''stdout'''.  For the SSH daemon to even run the script in the first place, the script must have the correct file and directory permissions.

Both the '''AuthorizedKeysCommandUser''' directive and '''AuthorizedKeysCommand''' must be used together.  The former designates which account the script or program use when run.  If set to ''none'' or if it does not refer to a valid account then [http://man.openbsd.org/sshd sshd(8)] will just ignore the command.  If '''AuthorizedKeysCommand''' is set, and '''AuthorizedKeysCommandUser''' is left empty or missing, then [http://man.openbsd.org/sshd sshd(8)] won't even run when invoked.  The error will be:

&lt;syntaxhighlight lang=&quot;text&quot;&gt;
AuthorizedKeysCommand set without AuthorizedKeysCommandUser
&lt;/syntaxhighlight&gt;

The '''AuthorizedKeysFile''' is always tried first when it is present in the server configuration.  The '''AuthorizedKeysCommand''' directive will not even be tried when the authorized keys file can provide a relevant key first.  

====A More Detailed Example Using the AuthorizedKeysCommand Directive====

By default the user name trying to log in is passed to the script when no tokens or arguments are provided.  Whether or how that information is used is up to the script.  The SSH daemon can also pass any combination of the tokens described in the TOKENS section of [http://man.openbsd.org/sshd_config sshd_config(5)] into the program or script being called.  Furthermore, the program or script can even be a front end for a database, such as OpenLDAP, or any similar system, as long as '''stdout''' produces a public key.  

Below is a more detailed example which uses a local script named '''keyfinder''' run with the account '''keys''' to look up the a public key for certain accounts.  First in [http://man.openbsd.org/sshd_config sshd_config(5)] the two directives:

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
AuthorizedKeysCommand /usr/local/sbin/keyfinder %U
AuthorizedKeysCommandUser keys
&lt;/syntaxhighlight&gt;

The script below is only a demonstration and a more complex program can call databases or do advanced lookups or heuristics:  

&lt;syntaxhighlight lang=&quot;shell&quot;&gt;
#!/bin/sh

set -e

case $1 in
        &quot;1000&quot;)
                echo &quot;ssh-ed25519 AAAAC3NzaC1lZDIE5AAAAIK89...UT9hz&quot;
                ;;

        &quot;1001&quot;)
                echo &quot;restrict ssh-ed25519 AAAAC3NzaC1lZDI1NTAAIBvGx...Y0zxV&quot;
                ;;

        &quot;1002&quot;)
                echo &quot;command=\&quot;/usr/libexec/sftp-server\&quot; ssh-ed25519 AAAAC3NzaC1lZDI1TE5AIPSyY...cPTg3&quot;
                ;;

        *)
                exit 1
                ;;
   
esac

exit 0
&lt;/syntaxhighlight&gt;

The '''AuthorizedKeysCommand''' scripts or programs can return any correctly formatted public key to '''stdout''' for consideration in the authentication process.  That includes adding constraints to the keys.  Above, the account with the UID 1000 has no constraints, while the account with UID 1001 is quite constrained.  Finally, the account with the UID 1002 can only access the SFTP service.  See the section &quot;AUTHORIZED_KEYS FILE FORMAT&quot; in [http://man.openbsd.org/sshd sshd(8)] for the full set of possibilities.

===Key-based Authentication Using an Agent===

When an authentication agent, such as [http://man.openbsd.org/ssh-agent.1 ssh-agent(1)], is going to be used, it should generally be started at the beginning of a session and used to launch the login session or X-session so that the environment variables pointing to the agent and its UNIX-domain socket are passed to each subsequent shell and process.  Many desktop distros do this automatically upon login or startup.  

Starting an agent entails setting a pair of environment variables:

* SSH_AGENT_PID : the process id of the agent
* SSH_AUTH_SOCK : the filename and full path to the UNIX-domain socket

The various SSH and SFTP clients find these variables automatically and use them to contact the agent and try when authentication is needed.   However, it is mainly SSH_AUTH_SOCK which is ever used.  If the shell or desktop session was launched using [http://man.openbsd.org/ssh-agent.1 ssh-agent(1)], then these variables are already set and available.  If they are not available, then it is necessary to either set the variables manually inside each shell or for each application in order to use the agent or else to point to the agent's socket using the directive '''IdentityAgent''' in the client's configuration file.  

Once an agent is available, a relevant private key needs to be loaded before the agent can be used.  Once in the agent the private key can then be used many times.  Private keys are loaded into an agent with [http://man.openbsd.org/ssh-add.1 ssh-add(1)].
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-add /home/fred/.ssh/mykey_ed25519
Identity added: /home/fred/.ssh/mykey_ed25519 (/home/fred/.ssh/mykey_ed25519)
&lt;/syntaxhighlight&gt;

Keys stay in the agent for as long as it is running unless specified otherwise.  A timeout can be set either with the '''-t''' option when starting the agent itself or when actually loading the key using [http://man.openbsd.org/ssh-add.1 ssh-add(1)].  In either case, the '''-t''' option will set a timeout interval, after which the key will be purged from the agent.
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-add -t 1h30m /home/fred/.ssh/mykey_ed25519
Identity added: /home/fred/.ssh/mykey_ed25519 (/home/fred/.ssh/mykey_ed25519)
Lifetime set to 5400 seconds
&lt;/syntaxhighlight&gt;

The option '''-l''' will list the fingerprints of all of the identities in the agent.  
&lt;syntaxhighlight lang=&quot;bash&quot;&gt;
$ ssh-add -l                                    
256 SHA256:77mfUupj364g1WQ+O8NM1ELj0G1QRx/pHtvzvDvDlOk mykey for task x (ED25519)
3072 SHA256:7unq90B/XjrRbucm/fqTOJu0I1vPygVkN9FgzsJdXbk myotherkey rsa for task y (RSA)
&lt;/syntaxhighlight&gt;

It is also possible to remove individual identities from the agent using '''-d''' which will remove them one at a time if identified by file name, but only if the file name is given and without the file name of the private key to be remove, '''-d''' will fail silently.  Using '''-D''' instead will remove all of them at once without needing to specify any by name.  

By default [http://man.openbsd.org/ssh-add.1 ssh-add(1)] uses the agent connected via the socket named in the environment variable '''SSH_AUTH_SOCK''', if it is set.  Currently, that is its only option.  However, for [http://man.openbsd.org/ssh.1 ssh(1)] an alternative to using the environment variable is the client configuration directive '''IdentityAgent''' which tells the SSH clients which socket to use to communicate with the agent.  If both the environment variable and the configuration directive are available at the same time, then the value in '''IdentityAgent''' takes precedence over what's in the environment variable.  '''IdentityAgent''' can also be set to ''none'' to prevent the connection from trying to use any agent at all.  

The client configuration directive '''AddKeysToAgent''' can also be useful in getting keys into an agent as needed.  When set, it automatically loads a key into a running agent the first time the key is called for if it is not already loaded.  Likewise the '''IdentitiesOnly''' directive can ensure that the relevant key is offered on the first try.  Rather than typing these out whenever the client is run, they can be added to '''~/.ssh/config''' and thereby added automatically for designated host connections.  

====Agent Forwarding====

Agent forwarding is one means of passing through one or more intermediate hosts.  However, the '''-J''' option for '''ProxyJump''' would be a safer option.  See [[OpenSSH/Cookbook/Proxies_and_Jump_Hosts#Jump_Hosts_--_Passing_Through_a_Gateway_or_Two | Passing Through a Gateway or Two]] in the section on jump hosts about that.  With agent forwarding, intermediate machines forward challenges and responses back and forth between the client and the final destination.  This comes with some risks but eliminates the need for using passwords or holding keys on any of these intermediate machines.  

A main advantage of agent forwarding is that the private key itself is not needed on any remote machine, thus hindering unwanted file system access to it. &lt;ref name=&quot;OpenSSH key management, Part 3&quot;&gt;{{cite web | url=http://www.ibm.com/developerworks/library/l-keyc3/ | title=Common threads: OpenSSH key management, Part 3 | author=Daniel Robbins | publisher=IBM | date=2002-02-01 | accessdate=2013-04-27}}&lt;/ref&gt;  Another advantage is that the actual agent to which the user has authenticated does not go anywhere and is thus less susceptible to analysis.  

One risk with agents is that they can be re-used to tailgate in if the permissions allow it.  Keys cannot be copied this way, but authentication is possible when there are incorrect permissions.  Note that disabling agent forwarding does not improve security unless users are also denied shell access, as they can always install their own forwarders.

The risks of agent forwarding can be mitigated by confirming each use of a key by adding the '''-c''' option when adding the key to the agent.  This requires the SSH_ASKPASS variable be set and available to the agent process, but will generate a prompt on the host running the agent upon each use of the key by a remote system.  So if passing through one or more intermediate hosts, it is usually better to instead have the SSH client use stdio forwarding with '''-W''' or '''-J'''.

On the client side agent forwarding is disabled by default and so if it is to be used it must be enabled explicitly.  Put the following line in  [http://man.openbsd.org/ssh_config.5 ssh_config(5)] to enable agent forwarding for a particular server:
&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
        Host gateway.example.org
        ForwardAgent yes
&lt;/syntaxhighlight&gt;

On the server side the default configuration files allow authentication agent forwarding, so to use it, nothing needs to be done there, just on the client side.  However, again, it would be preferable to take a look at '''ProxyJump''' instead.  

=====Old Style, Somewhat Safer SSH Agent Forwarding=====

The best way to pass through one or more intermediate hosts is to use the '''ProxyJump''' option instead of authentication agent forwarding and thereby not risk exposing any private keys.  If authentication agent forwarding must be used, then it would be advisable in the interest of following the principle of least privilege to forward an agent containing the minimum necessary number of keys.  There are several ways to solve that.  

In version 8.8 and earlier a partial solution is to make a one-off, ephemeral agent to hold just the one key or keys needed for the task at hand.  Another partial solution would be to set up a user-accessible service at the operating system level and then use [http://man.openbsd.org/ssh_config.5 ssh_config] for the rest.  

Automatically launching an ephemeral agent unique to each session can be done by crafting either a special shell alias or function to launch a single-use agent.  Either the function or the alias can be written to require confirmation for each requested signature.  The following example is an alias is based on an updated blog post by Vincent Bernat&lt;ref name=&quot;safer-agent-forwarding&quot;&gt;{{cite web |url=https://vincent.bernat.ch/en/blog/2020-safer-ssh-agent-forwarding |title=Safer SSH agent forwarding |author=Vincent Bernat|date=2020-04-05 |accessdate=2020-10-04}}&lt;/ref&gt; on SSH agent forwarding:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ alias assh=&quot;ssh-agent ssh -o AddKeysToAgent=confirm -o ForwardAgent=yes&quot;
&lt;/syntaxhighlight&gt;

Note the use of [http://man.openbsd.org/ssh-agent.1 ssh-agent(1)].  When invoking that alias, the SSH client will be launched with a unique, ephemeral supporting key agent.  The alias sets up a new agent, including setting the two environment variables, and then sets two client options while calling the client.  This arrangement still checks with [http://man.openbsd.org/ssh_config.5 ssh_config(5)] for other options and settings.  When the SSH session is finished the agent which launched it ends and goes away, thus cleaning up after itself automatically.  

Another way is to rely on the client's configuration file for some of the settings.  Such methods rely mostly on [http://man.openbsd.org/ssh_config.5 ssh_config(5)] but still require an independent method to launch an ephemeral agent because the OpenSSH client is already running by the time it reads the configuration file and is thus not affected by any changes to environment variables caused by the configuration file and it is through the environment variables that contain information about the agent.  However, when the path to the UNIX-domain socket used to communicate with the authentication agent is decided in advance then the '''IdentityAgent''' option can point to it once the one-off agent&lt;ref name=&quot;wikimedia_ssh_agents&quot;&gt;{{cite web |url=https://wikitech.wikimedia.org/wiki/Managing_multiple_SSH_agents#Linux_solutions |title=Managing multiple SSH agents |publisher=Wikimedia|accessdate=2020-04-07}}&lt;/ref&gt; is actually launched.  The following uses a specific agent's pre-defined socket whenever connecting to either of two particular domains:

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Host *.wikimedia.org *.wmflabs.org
        User fred
        IdentitiesOnly yes
        IdentityFile %d/.ssh/id_cloud_01
        IdentityAgent /run/user/%i/ssh-cloud-01.socket
        ForwardAgent yes
        AddKeysToAgent yes
&lt;/syntaxhighlight&gt;

The '''%d''' stands for the path to the home directory and the '''%i''' stands for the user id (UID) for the current account.  In some cases the '''%i''' token might also come in handy when setting the '''IdentityAgent''' option inside the configuration file.  Again, be careful when forwarding agents with which keys are in the forwarded agent.  See the section &quot;TOKENS&quot; in [http://man.openbsd.org/ssh_config.5 ssh_config(5)] for more such abbreviations.  

With those configuration settings, the authentication agent must already be up and running and point to the designated socket prior to starting the SSH client for that configuration to work.  Additionally, it should place the socket in a directory which is inaccessible to any other accounts.  [http://man.openbsd.org/ssh-agent.1 ssh-agent(1)] must use the '''-a''' option to name the socket:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-agent -a /run/user/${UID}/ssh-cloud-01.socket
&lt;/syntaxhighlight&gt;

That agent configuration can be launched manually or via a script or service manager.  However, in the interests of privacy and security in general, agent forwarding is to be avoided.  The configuration directive '''ProxyJump''' is the best alternative and, on older systems, host traversal using '''ProxyCommand''' with [http://man.openbsd.org/nc.1 netcat] are preferable.  Again, see the section on [[OpenSSH/Cookbook/Proxies and Jump Hosts|Proxies and Jump Hosts]] for how those methods are used.

=====New Style SSH Agent Destination Constraints=====

From 8.9 onward, [http://man.openbsd.org/ssh-agent.1 ssh-agent(1)] will allow the agent to limit which hosts they will use for authentication as specified by [http://man.openbsd.org/ssh-add.1 ssh-add(1)] using the '''-h''' option.  These constraints have been added through two agent protocol extensions and a modification to the public key authentication protocol.  This feature may evolve, but for now the result is such that keys for account authentication can be loaded into the agent in four ways:

* no limits on forwarding (not recommended)
* local use only, these will not get forwarded
* forwarding, but only to specific remote hosts
* forwarding to specific remote hosts via specified routes

The intent is that the restrictions fail safely so that they do not allow authentication when one or more hosts in the route lack the needed protocol features.  The destinations and routes cannot be modified once the keys are loaded, but multiple routes to the same destination can be loaded and the routes can be any number of hops.  If the routes need changing, then the key must be reloaded into the agent with the new route or routes.  

The general default for the client is to keep keys in the agent for local use only.  However, that can be enforced explicitly by adding the '''-a''' option when starting the client or else setting the '''ForwardAgent''' directive in [http://man.openbsd.org/ssh_config.5 ssh_config(5)] to 'no' in the relevant configuration block.  

In order to load keys for unlimited forwarding, which is not the best idea, just add them using [http://man.openbsd.org/ssh-add.1 ssh-add(1)] as normal.  Then use the '''-A''' option with the client or set the '''ForwardAgent''' directive in [http://man.openbsd.org/ssh_config.5 ssh_config(5)] to 'yes' in the relevant configuration block.  

In order to limit keys for connection only to a specific remote host, or to load keys for connection to a specific remote host with forwarding via one or more intermediate hosts, use the '''-h''' option when loading keys into the agent.  Here the one key may be used only to connect to the specific destination:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-agent -h server.example.org server.key.ed25519
&lt;/syntaxhighlight&gt;

If an intermediate system is passed through, the best way is to use '''ProxyJump''' which is the '''-J''' option for the SSH Client.  If agent forwarding must be allowed then the tightest way is to constrain which systems may use the keys, again using the '''-h''' option.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-agent -h middle.example.org -h &quot;middle.example.org&gt;server.example.org&quot; server.key.ed25519
&lt;/syntaxhighlight&gt;

Multiple steps can be included, even multiple routes.  They just have to be enumerated explicitly, though patterns may still be used for the destination hosts as well as specific names.  Each host in the chain must support these protocol extensions for the connection to complete.  

Any keys designated for forwarding are unusable for authentication on any other hosts than those which have been explicitly identified for forwarding.  These permitted hosts are identified by host key or host certificate from the '''known_hosts''' file or another file designated by the '''-H''' option when loading the key with [http://man.openbsd.org/ssh-add.1 ssh-add(1)].  If '''-H''' is not used at the time the keys are loaded into the agent, then the default known hosts file(s) will be used: '''~/.ssh/known_hosts''', '''/etc/ssh/ssh_known_hosts''', '''~/.ssh/known_hosts2''', and '''/etc/ssh/ssh_known_hosts2'''.

In the case of keys, the '''known_hosts''' list must be maintained conscientiously &lt;ref name=&quot;ssh-agent-restrictions&quot;&gt;{{ cite web | author=Damien Miller|url=https://www.openssh.org/agent-restrict.html | title=SSH agent restriction | publisher=OpenSSH | date=2021-12-16|accessdate=2022-03-06}}&lt;/ref&gt;, perhaps with the help of the '''UpdateHostkeys''' and '''CanonicalizeHostname''' client configuration directives.  Use of certificates requires the agent to only need to be aware of the Certificate Authority (CA).

Again, see [[OpenSSH/Cookbook/Proxies_and_Jump_Hosts#Jump_Hosts_--_Passing_Through_a_Gateway_or_Two | Passing Through a Gateway or Two]] in the section on jump hosts about a way to pass through one or more intermediate machines without needing to forward an SSH agent.

====Checking the Agent for Specific Keys====

The [http://man.openbsd.org/ssh_add ssh_add(1)] utility's '''-T''' option can test whether a specific private key is available in the agent or not by looking up the matching public key.  That can be useful in a shell script.

&lt;syntaxhighlight lang=&quot;shell&quot;&gt;
#!/bin/sh

key=/home/fred/.ssh/some.key.ed25519.pub

if ssh-add -T ${key}; then
        echo &quot;Key ${key} Found&quot;
else
        echo &quot;Key ${key} missing&quot;
fi
&lt;/syntaxhighlight&gt;

Or it could be done with an alternate syntax just as well either in a script or in an interactive shell sessions,

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ key=/home/fred/.ssh/some.key.ed25519.pub
$ ssh-add -T ${key} &amp;&amp; echo &quot;Key found&quot; || echo &quot;Key missing&quot;
&lt;/syntaxhighlight&gt;

However, if the desired result would be to add key to the agent then the '''AddKeysToAgent''' client configuration option can ensure that a specific key is added to the SSH agent upon first use during any given login session.  That can be done using '''-o AddKeysToAgent=yes''' as a run-time argument, or by modifying [http://man.openbsd.org/ssh_config ssh_config(5)] as appropriate:

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Host www
        HostName www.example.com
        IdentityFile %d/.ssh/www.ed25519
        IdentitiesOnly yes
        AddKeysToAgent yes
&lt;/syntaxhighlight&gt;

With those options in the configuration file, the first time &lt;code&gt;ssh www&lt;/code&gt; is run the specified key will get added to the agent and remain available.

===Key-based Authentication Using A Hardware Security Token===

While stand-alone keys have been around for a long time, it has been possible since version 8.2 to use keys backed by hardware security tokens, such as OnlyKey, Yubikey, or many others, though the FIDO2 protocol.  The Universal 2nd Factor (U2F) authentication is supported directly in OpenSSH through FIDO2 and does not need third party software.  At the moment there are two types of hardware backed keys, ECDSA-SK and Ed25519-SK, but only the latest hardware tokens support the latter.  If the key Ed25519-SK format is not supported by the token's firmware, then the following error message will be presented when attempts to use that key type are made:

&lt;syntaxhighlight lang=&quot;text&quot;&gt;
Key enrollment failed: invalid format
&lt;/syntaxhighlight&gt; 

If supported, either key type can be created with [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)].  The steps are almost identical to creating normal keys but the token must be available to the system (plugged in) first.  Then if called for, the token's PIN must be entered and the token touched or otherwise activated.  After that, the key creation proceeds as normal.  Mind the key type as specified by the '''-t''' option.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -t ed25519-sk -f /home/fred/.ssh/server.ed25519-sk -C &quot;web server for fred&quot;
Generating public/private ed25519-sk key pair.
You may need to touch your authenticator to authorize key generation.
Enter passphrase (empty for no passphrase): 
Enter same passphrase again: 
Your identification has been saved in /home/fred/.ssh/server.ed25519-sk
Your public key has been saved in /home/fred/.ssh/server.ed25519-sk.pub
The key fingerprint is:
SHA256:41wVVDnKJ9gKr2Sj4CFuYMhcNvYebZ6zq0PWyP4rRDo web server
The key's randomart image is:
+[ED25519-SK 256]-+
|           .o... |
|             .o  |
|           +.. . |
|   = .  . ..= .  |
|+ + * + So.. o   |
|o+.EoO *+oo      |
|.o oBo+++o       |
|  o .=.+.        |
| .   .===        |
+----[SHA256]-----+
&lt;/syntaxhighlight&gt;

Once created, the public and private key files get handled like with any other type of key.  But when authenticating, the hardware token must be present and activated when called for.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -i /home/fred/.ssh/server.ed25519-sk server.example.org
Enter passphrase for key '/home/fred/.ssh/server.ed25519-sk': 
Confirm user presence for key ED25519-SK SHA256:41wVVDnKJ9gKr2Sj4CFuYMhcNvYebZ6zq0PWyP4rRDo
&lt;/syntaxhighlight&gt;

The resulting private key file is not actually the key itself but instead a &quot;key handle&quot; which is used by the hardware security token to derive the real private key on demand at the time it is actually used&lt;ref name=&quot;OpenBSD_tech_U2F_FIDO&quot;&gt;{{cite web |url=https://marc.info/?l=openbsd-tech&amp;m=157376801917387&amp;w=2 |title=OpenSSH U2F/FIDO support in base 
|publisher=OpenBSD-Tech Mailing List | date=2019-11-14
|accessdate=2021-03-24}}&lt;/ref&gt;.  As a result, the hardware-backed private key file is useless without the accompanying hardware token.  This also means that these key files are not portable across hardware tokens, say when having multiple tokens in reserve or as backup, even when used by the same account.  So when multiple hardware tokens are in use, different key pairs must be generated for each token.

====Hardware Security Token Resident Private Key====

It is possible to store the private key within the token itself, but for the moment it cannot be used directly from inside the token and must first be saved as a file.  Also, the key can only be loaded into the FIDO authenticator at the time of creation  using the '''-O resident''' option with [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)].  Otherwise, the process is the same as above.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -O resident -t ed25519-sk -f /home/fred/.ssh/server.ed25519-sk -C &quot;web server for fred&quot;
. . .
&lt;/syntaxhighlight&gt;

When needed, the resident key can be extracted from the FIDO2 hardware token and saved into a file using the '''-K''' option.  At this stage a passphrase can be added to the file, but no passphrase is kept within the token itself, only an optional PIN protects the key there.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -K
Enter PIN for authenticator: 
Enter passphrase (empty for no passphrase): 
Enter same passphrase again: 
Saved ED25519-SK key to id_ed25519_sk_rk

$ mv -i id_ed25519_sk_rk /home/fred/.ssh/server.ed25519-sk
&lt;/syntaxhighlight&gt;

Since the output file name is fixed, any pre-existing file with that name can get overwritten but there will be a warning first.  However, it is not recommended to keep the key on the hardware token because it provides more protection when kept separately.

==Single-purpose Keys==

Tailored single-purpose keys can eliminate use of remote root logins for many administrative activities.  A  finely tailored '''sudoers''' is needed along with an unprivileged account.  When done right, it gives just enough access to get the job done, following the security principle of Least Privilege.  

Single-purpose keys are accompanied by use of either the '''ForceCommand''' directive in [http://man.openbsd.org/ssh_config.5 sshd_config(5)] or the '''command=&quot;...&quot;''' directive inside the '''authorized_keys''' file.  The method is to generate a new key pair, transfer the public key to '''authorized-keys''' on the remote system, and then prepend the appropriate command or script there to the line with the key.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ grep '^command' ~/.ssh/authorized_keys
command=&quot;/usr/local/bin/somescript.sh&quot; ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIEcgdzDvSebOEjuegEx4W1I/aA7MM3owHfMr9yg2WH8H
&lt;/syntaxhighlight&gt;

The '''command=&quot;...&quot;''' directive inserted there overrides everything else and ensures that when logging in with just that key only the script '''/usr/local/bin/somescript.sh''' is run.  If it is necessary to pass parameters to the script, have a look at the contents of the '''SSH_ORIGINAL_COMMAND''' environment variable and use it in a case statement.  Do not ever trust the contents of that variable nor use the contents directly, always indirectly.  

Single-purpose keys are useful for allowing only a tunnel and nothing more.  The following key will only echo some text and then exit, unless used non-interactively with the '''-N''' option.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ grep '^command' ~/.ssh/authorized_keys
command=&quot;/bin/echo do-not-send-commands&quot; ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIBzTIWCaILN3tHx5WW+PMVDc7DfPM9xYNY61JgFmBGrA 
&lt;/syntaxhighlight&gt; 

No matter what the user tries while logging in with that key, the session will only echo the given text and then exits.  Using the '''-N''' option disables running the remote program, allowing the connection to stay open, allowing a tunnel. 

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -L 3306:localhost:3306 \
	-i ~/.ssh/tunnel_ed25519 \
	-N \
	-l fred \
	server.example.com
&lt;/syntaxhighlight&gt;

That creates a tunnel and stays connected despite a key configuration which would close an interactive session.  See also the '''-n''' or '''-f''' option for [http://man.openbsd.org/ssh.1 ssh(1)].  

===Single-purpose Keys to Avoid Remote Root Access===

The easy way is to write a short shell script, place it '''/usr/local/bin/''', and then configure '''sudoers''' to allow the otherwise unprivileged account to run just that script and only that script.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
%wheel  ALL=(root:root) NOPASSWD: /usr/sbin/service httpd stop
%wheel  ALL=(root:root) NOPASSWD: /usr/sbin/service httpd start
&lt;/syntaxhighlight&gt;

Then the key calls the script using '''command=&quot;...&quot;''' inside '''authorized_keys'''.  Here the one key starts the web server, the other stops the web server.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ grep '^command' ~/.ssh/authorized_keys
command=&quot;/usr/bin/sudo /usr/sbin/service httpd stop&quot; ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIEcgdzDvSebOEjuegEx4W1I/aA7MM3owHfMr9yg2WH8H
command=&quot;/usr/bin/sudo /usr/sbin/service httpd start&quot; ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMidyqZ6OCvbWqA8Zn+FjhpYE6NoWSxVjFnFUk6MrNZ4
&lt;/syntaxhighlight&gt;

Complicated programs like [http://linux.die.net/man/1/rsync rsync(1)], [http://man.openbsd.org/tar.1 tar(1)], [http://linux.die.net/man/1/mysqldump mysqldump(1)], and so on require an advanced approach when building a single-purpose key.  For them, the '''-v''' option can show exactly what is being passed to the server so that '''sudoers''' can be set up correctly.  That way they can be restricted to only access designated parts of the file system.  For example, here is what &lt;code&gt;ssh -v&lt;/code&gt; shows from one particular usage of [http://linux.die.net/man/1/rsync rsync(1)], note the &quot;Sending command&quot; line:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ rsync -e 'ssh -v' fred@server.example.org:/etc/ ./backup/etc/
. . .
debug1: Sending command: rsync --server --sender -e.LsfxC . /etc/
. . .
&lt;/syntaxhighlight&gt;

That output can then be added to '''sudoers''' so that the key can do only that function.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
%backup ALL=(root:root) NOPASSWD: /usr/bin/rsync --server --sender -e.LsfxC . /etc/
&lt;/syntaxhighlight&gt;

Then to tie it all together, the account &quot;backup&quot; needs a key:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ grep '^command' ~/.ssh/authorized_keys
command=&quot;/usr/bin/rsync --server --sender -e.LsfxC . /etc/&quot; ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMm0rs4eY8djqBb3dIEgbQ8lmdlxb9IAEuX/qFCTxFgb 
&lt;/syntaxhighlight&gt;

Many of these programs have a '''--dry-run''' or equivalent option.  Remember to use it when figuring out the right settings.

===Read-only Access to Keys===

In some cases it is necessary to prevent accounts from being able to changing their own authentication keys.  However, such situations may be a better case for using certificates.  However, if done with keys it is accomplished by putting the key file in an external directory where the user has read-only access, both to the directory and to the key file.  Then the '''AuthorizedKeysFile''' directive assigns where [http://man.openbsd.org/sshd.8 sshd(8)] looks for the keys and can point to a secured location for the keys instead of the default location.

A good alternate location could be a new directory '''/etc/ssh/authorized_keys''' which could store the selected accounts' key files there.  The change can be made to apply to only a group of accounts by putting the settings under a '''Match''' directive.  The default location for keys on most systems is usually '''~/.ssh/authorized_keys'''.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Match Group sftpusers
	AuthorizedKeysFile /etc/ssh/authorized_keys/%u
&lt;/syntaxhighlight&gt;

Then the permissions there would allow the keys to be read but not written:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ls -dhln /etc/ssh/
drwxr-x--x 3 0 0 4.0K Mar 30 22:16 /etc/ssh/authorized_keys/

$ ls -dhln /etc/ssh/*.pub
-rw-r--r-- 1 0 0 173 Mar 23 13:34 /etc/ssh/fred
-rw-r--r-- 1 0 0  93 Mar 23 13:34 /etc/ssh/user1
-rw-r--r-- 1 0 0 565 Mar 23 13:34 /etc/ssh/user2
. . .
&lt;/syntaxhighlight&gt;

The keys could even be within subdirectories, though the same restrictions apply regarding permissions and ownership.  

For chrooted SFTP, the method is the same to keep the key files out of reach of the accounts:  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Match Group sftpusers
	ChrootDirectory /home
	ForceCommand internal-sftp -d %u
	AuthorizedKeysFile /etc/ssh/authorized_keys/%u
&lt;/syntaxhighlight&gt;

Of course a '''Match''' directive is not essential.  The settings could be made to apply to all accounts by putting the directive in the main part of the server configuration file instead.

==Mark Public Keys as Revoked==

Keys can be revoked.  Keys that have been revoked can be stored in '''/etc/ssh/revoked_keys''', a file specified in [http://man.openbsd.org/ssh_config.5 sshd_config(5)]  using the directive '''RevokedKeys''', so that [http://man.openbsd.org/sshd.8 sshd(8)] will prevent attempts to log in with them.  No warning or error on the client side will be given if a revoked key is tried.  Authentication will simply progress to the next key or method.

The revoked keys file should contain a list of public keys, one per line, that have been revoked and can no longer be used to connect to the server.  The key cannot contain any extras, such as [[OpenSSH/Client_Configuration_Files#Available_key_login_options | login options]] or it will be ignored. If one of the revoked keys is tried during a login attempt, the server will simply ignore it and move on to the next authentication method.  An entry will be made in the logs of the attempt, including the key's fingerprint.  See the section on [[OpenSSH/Logging_and_Troubleshooting | logging]] for a little more on that.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
RevokedKeys /etc/ssh/revoked_keys
&lt;/syntaxhighlight&gt;

The '''RevokedKeys''' configuration directive is not set in [http://man.openbsd.org/ssh_config.5 sshd_config(5)] by default.  It must be set explicitly if it is to be used.  This is another situation that might be better fulfilled through using certificate since a validity interval can be set in any combination of seconds, minutes, hours, days, or weeks can be set for certificates while keys are valid indefinitely.  

===Key Revocation Lists===

A Key Revocation List (KRL) is a compact, binary form of representing revoked keys and certificates.  In order to use a KRL, the server's configuration file must point to a valid list using the '''RevokedKeys''' directive.  KRLs themselves are generated with [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)] and can be created from scratch or edited in place.  Here a new one is made, populated with a single public key: 

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -kf  /etc/ssh/revoked_keys -z 1 ~/.ssh/old_key_rsa.pub
&lt;/syntaxhighlight&gt;

Here an existing KRL is updated by adding the '''-u''' option:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -ukf /etc/ssh/revoked_keys -z 2 ~/.ssh/old_key_dsa.pub
&lt;/syntaxhighlight&gt;

Once a KRL is in place, it is possible to test if a specific key or certificate is in the revocation list.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -Qf  /etc/ssh/revoked_keys ~/.ssh/old_key_rsa.pub
&lt;/syntaxhighlight&gt;

Only public keys and certificates will be loaded into the KRL.  Corrupt or broken keys will not be loaded and will produce an error message if tried.  Like with the regular '''RevokedKeys''' list, the public key destined for the KRL cannot contain any extras like login options or it will produce an error when an attempt is made to load it into the KRL or search the KRL for it.

==Verify a Host Key by Fingerprint==

The above examples have been about using keys to authenticate the client to the server.  A different context in which keys are used is when the server identifies itself to the client, which happens automatically at the beginning of each non-multiplexed session.  In order for that identification to happen the client acquires a public key from the server, usually on or prior to first contact, which it can subsequently use to ensure that it is connecting to the same server again and not an impostor.  The default locations for storing these acquired host keys on the client are in '''/etc/ssh/ssh_known_hosts''', if managed by the system administrator, or in '''~/.ssh/known_hosts''' if managed by the client's own account.  The format of the contents is a line with a host address and its matching public key.  The file is described in detail in the [http://man.openbsd.org/sshd.8 sshd(8)] manual page in the section &quot;SSH_KNOWN_HOSTS FILE FORMAT&quot;.

When connecting for the first time to a remote host, the server's host key should be verified in order to ensure that the client is connecting to the right machine and not an impostor or anything else.  Usually this verification is done by comparing the fingerprint of the server's host key rather than trying to compare the whole key itself.  By default the client will show the fingerprint if the key is not already found in the '''known_hosts''' register.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -l fred server.example.org
The authenticity of host 'server.example.org (192.0.32.10)' can't be established.
ECDSA key fingerprint is SHA256:LPFiMYrrCYQVsVUPzjOHv+ZjyxCHlVYJMBVFerVCP7k.
Are you sure you want to continue connecting (yes/no)? 
&lt;/syntaxhighlight&gt;

That can be compared to a fingerprint received out of band, say by post, e-mail, SMS, courier, and so on.  Specifically, the example represents the key's fingerprint as a base64 encoded SHA256 checksum.  That is the default style.  The fingerprint can also be displayed as an MD5 hash in hexadecimal instead by passing the client's '''FingerprintHash''' configuration directive as a runtime argument or setting it in [http://man.openbsd.org/ssh_config.5 ssh_config(5)].  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -o FingerprintHash=md5 host.example.org
The authenticity of host 'host.example.org (192.0.32.203)' can't be established.
RSA key fingerprint is MD5:10:4a:ec:d2:f1:38:f7:ea:0a:a0:0f:17:57:ea:a6:16.
Are you sure you want to continue connecting (yes/no)?
&lt;/syntaxhighlight&gt;

But the default in new versions is SHA256 in base64 has a lower chance of collision.

In OpenSSH 6.7 and earlier, the client showed fingerprints as a hexadecimal MD5 checksum instead a of the base64-encoded SHA256 checksum currently used:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -l fred server.example.org
The authenticity of host 'server.example.org (192.0.32.10)' can't be established. 
RSA key fingerprint is 4a:11:ef:d3:f2:48:f8:ea:1a:a2:0d:17:57:ea:a6:16. 
Are you sure you want to continue connecting (yes/no)? 
&lt;/syntaxhighlight&gt;

Another way of comparing keys is to use the ASCII art visual host key.  See further below about that.  

===Downloading keys===

Even though a host’s key is usually displayed for review the first time the SSH client tries to connect, it can also be fetched on demand at any time using [http://man.openbsd.org/ssh-keyscan.1 ssh-keyscan(1)]:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keyscan host.example.org  
# host.example.org SSH-2.0-OpenSSH_8.2
host.example.org ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBLC2PpBnFrbXh2YoK030Y5JdglqCWfozNiSMjsbWQt1QS09TcINqWK1aLOsNLByBE2WBymtLJEppiUVOFFPze+I=
# host.example.org SSH-2.0-OpenSSH_8.2
host.example.org ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQC9iViojCZkcpdLju7/3+OaxKs/11TAU4SuvIPTvVYvQO32o4KOdw54fQmd8f4qUWU59EUks9VQNdqf1uT1LXZN+3zXU51mCwzMzIsJuEH0nXECtUrlpEOMlhqYh5UVkOvm0pqx1jbBV0QaTyDBOhvZsNmzp2o8ZKRSLCt9kMsEgzJmexM0Ho7v3/zHeHSD7elP7TKOJOATwqi4f6R5nNWaR6v/oNdGDtFYJnQfKUn2pdD30VtOKgUl2Wz9xDNMKrIkiM8Vsg8ly35WEuFQ1xLKjVlWSS6Frl5wLqmU1oIgowwWv+3kJS2/CRlopECy726oBgKzNoYfDOBAAbahSK8R
# host.example.org SSH-2.0-OpenSSH_8.2
host.example.org ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIDDOmBOknpyJ61Qnaeq2s+pHOH6rdMn09iREz2A/yO2m
&lt;/syntaxhighlight&gt;

Once a key is acquired, its fingerprint can be shown using [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)].  This can be done directly with a pipe.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keyscan host.example.org | ssh-keygen -lf - 
# host.example.org SSH-2.0-OpenSSH_8.2
# host.example.org SSH-2.0-OpenSSH_8.2
# host.example.org SSH-2.0-OpenSSH_8.2
256 SHA256:sxh5i6KjXZd8c34mVTBfWk6/q5cC6BzR6Qxep5nBMVo host.example.org (ECDSA)
3072 SHA256:hlPei3IXhkZmo+GBLamiiIaWbeGZMqeTXg15R42yCC0 host.example.org (RSA)
256 SHA256:ZmS+IoHh31CmQZ4NJjv3z58Pfa0zMaOgxu8yAcpuwuw host.example.org (ED25519)
&lt;/syntaxhighlight&gt;

If there is more than one public key type is available from the server on the port polled, then [http://man.openbsd.org/ssh-keyscan.1 ssh-keyscan(1)] will fetch each of them.  If there is more than one key fed via '''stdin''' or a file, then [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)] will process them in order.  Prior to OpenSSH 7.2 manual fingerprinting was a two step process, the key was read to a file and then processed for its fingerprint.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keyscan -t ed25519 host.example.org &gt; key.pub
# host.example.org SSH-2.0-OpenSSH_6.8
$ ssh-keygen -lf key.pub                       
256 SHA256:ZmS+IoHh31CmQZ4NJjv3z58Pfa0zMaOgxu8yAcpuwuw host.example.org (ED25519)
&lt;/syntaxhighlight&gt;

Note that some output from [http://man.openbsd.org/ssh-keyscan.1 ssh-keyscan(1)] is sent to '''stderr''' instead of '''stdout'''.  

A hash, or fingerprint, can be generated manually with [http://linux.die.net/man/1/awk awk(1)], [http://linux.die.net/man/1/sed sed(1)] and [http://linux.die.net/man/1/xxd xxd(1)], on systems where they are found.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ awk '{print $2}' key.pub | base64 -d | md5sum -b | sed 's/../&amp;:/g; s/: .*$//'
$ awk '{print $2}' key.pub | base64 -d | sha256sum -b | sed 's/ .*$//' | xxd -r -p | base64 
&lt;/syntaxhighlight&gt;

It is possible to find all hosts from a file which have new or different keys from those in '''known_hosts''', if the host names are in clear text and not stored as hashes.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keyscan -t rsa,ecdsa -f ssh_hosts | \
  sort -u - ~/.ssh/known_hosts | \
  diff ~/.ssh/known_hosts -
&lt;/syntaxhighlight&gt;

====Using ssh-keyscan(1) with ssh_config(5)====

The utility [http://man.openbsd.org/ssh-keyscan.1 ssh-keyscan(1)] does not parse [http://man.openbsd.org/ssh_config.5 ssh_config(5)].  That is in part to keep the code base simple.  There are a lot of configuration options which would be complicated to implement, including but not limited to '''ProxyJump''', '''ProxyCommand''', '''Match''', '''BindInterface''', and '''CanonicalizeHostname'''&lt;ref name=&quot;keyscan&quot;&gt;{{cite mailing list |url=https://lists.mindrot.org/pipermail/openssh-unix-dev/2023-March/040605.html | title=Why does ssh-keyscan not use .ssh/config? |publisher=mindrot.org | access-date=2023-03-01 | date=2023-03-01 | mailing-list=OpenSSH UNIX-dev | first=Damien | last=Miller }}&lt;/ref&gt; .  Resolving host names via the client configuration file can be done by wrapping the utility in a short shell function:

&lt;syntaxhighlight lang=&quot;shell&quot;&gt;
my-ssh-keyscan() {
	for host in &quot;$@&quot; ; do
		ssh-keyscan $(ssh -G &quot;$host&quot; | awk '/^hostname/ {print $2}')
	done
}
&lt;/syntaxhighlight&gt;

That shell function uses the '''-G''' option of [http://man.openbsd.org/ssh.1 ssh(1)] to resolve each host name using [http://man.openbsd.org/ssh_config.5 ssh_config(5)] and then check the resulting host name for SSH keys.

===ASCII Art Visual Host Key===

An ASCII art representation of the key can be displayed along with the SHA256 base64 fingerprint: 

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -lvf key 
256 SHA256:BClQBFAGuz55+tgHM1aazI8FUo8eJiwmMcqg2U3UgWU www.example.org (ED25519)
+--[ED25519 256]--+
|o+=*++Eo         |
|+o .+.o.         |
|B=.oo.  .        |
|*B.=.o .         |
|= B *   S        |
|. .@ .           |
| +..B            |
|  *. o           |
| o.o.            |
+----[SHA256]-----+
&lt;/syntaxhighlight&gt;

In OpenSSH 6.7 and earlier the fingerprint is in MD5 hexadecimal form.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -lvf key 
2048 37:af:05:99:e7:fb:86:6c:98:ee:14:a6:30:06:bc:f0 www.example.net (RSA) 
+--[ RSA 2048]----+ 
|          o      | 
|         o .     | 
|        o o      | 
|       o +       | 
|   .  . S        | 
|    E ..         | 
|  .o.* ..        | 
|  .*=.+o         | 
|  ..==+.         | 
+-----------------+ 
&lt;/syntaxhighlight&gt;

==More on Verifying SSH Keys==

Keys on the client or the server can be verified against known good keys by comparing the base64-encoded SHA256 fingerprints.  

===Verifying Stray Client Keys===

Sometimes is is necessary to compare two uncertain key files to check if they are part of the same key pair.  However, public keys are more or less disposable.  So the easy way in such situations on the client machine is to just rename or erase the old, problematic, public key and replace it with a new one generated from the existing private key.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -y -f ~/.ssh/my_key_rsa
&lt;/syntaxhighlight&gt;

But if the two parts must really be compared, it is done in two steps using [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)].  First, a new public key is re-generated from the known private key and used to make a fingerprint to '''stdout'''.  Next, the fingerprint of the unknown public key is generated for comparison.  In this example, the private key '''my_key_a_rsa''' and the public key '''my_key_b_rsa.pub''' are compared:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -y -f my_key_a_rsa | ssh-keygen -l -f -
$ ssh-keygen -l -f my_key_b_rsa.pub
&lt;/syntaxhighlight&gt;

The result is a base64-encoded SHA256 checksum for each key with the one fingerprint displayed right below the other for easy visual comparison.  Older versions don't support reading from '''stdin''' so an intermediate file will be needed then.  Even older versions will only show an MD5 checksum for each key.  Either way, automation with a shell script is simple enough to accomplish but outside the scope of this book.

===Verifying Server Keys===

Reliable verification of a server's host key must be done when first connecting.  It can be necessary to contact the system administrator who can provide it out of band so as to know the fingerprint in advance and have it ready to verify the first connection.  

Here is an example of the server's RSA key being read and its fingerprint shown as SHA256 base64:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -lf /etc/ssh/ssh_host_rsa_key.pub     
3072 SHA256:hlPei3IXhkZmo+GBLamiiIaWbeGZMqeTXg15R42yCC0 root@server.example.net (RSA)
&lt;/syntaxhighlight&gt;

And here the corresponding ECDSA key is read, but shown as an MD5 hexadecimal hash:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -E md5 -lf /etc/ssh/ssh_host_ecdsa_key.pub
256 MD5:ed:d2:34:b4:93:fd:0e:eb:08:ee:b3:c4:b3:4f:28:e4 root@server.example.net (ECDSA)
&lt;/syntaxhighlight&gt;

Prior to 6.8, the fingerprint was expressed as an MD5 hexadecimal hash:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -lf /etc/ssh/ssh_host_rsa_key.pub 
2048 MD5:e4:a0:f4:19:46:d7:a4:cc:be:ea:9b:65:a7:62:db:2c root@server.example.net (RSA)
&lt;/syntaxhighlight&gt;

It is also possible to use [http://man.openbsd.org/ssh-keyscan.1 ssh-keyscan(1)] to get keys from an active SSH server.  However, the fingerprints still needs to be verified out of band.  

====Warning: Remote Host Identification Has Changed!====

If a server's key does not match what the client finds has been recorded in either the system's or the local account's '''authorized_keys''' files, then the client will issue a warning along with the fingerprint of the suspicious key.  

&lt;pre&gt;
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
SHA256:GkoIDP/d0I6KA9IQyOB9iqL+Rzpxx9LhlSJPCEfjVQ4.
Please contact your system administrator.
Add correct host key in /home/fred/.ssh/known_hosts to get rid of this message.
Offending RSA key in /home/fred/.ssh/known_hosts:19
  remove with:
  ssh-keygen -f &quot;/home/fred/.ssh/known_hosts&quot; -R &quot;server.example.com&quot;
RSA host key for server.example.com has changed and you have requested strict checking.
Host key verification failed.
&lt;/pre&gt;

Three reasons for the warning are common.  

One reason is that the server's keys were replaced, often because the server's operating system was reinstalled without backing up the old keys.  Another reason can be when the system administrator has phased out deprecated or compromised keys.  However that can be planned better and if there is time to plan the migration, new keys can just be added to the server and have the clients use the '''UpdateHostKeys''' option so that the new keys are accepted if the old keys match.  A third situation is when the connection is made to the wrong machine, such as when the remote system changes IP addresses because of dynamic address allocation.  

In all three cases where the key has changed there is only one thing to do: contact the system administrator and verify the key.   Ask if the OpenSSH-server was recently reinstalled, or was the machine restored from an old backup?  Keep in mind that the system administrator may be you yourself in some cases. 

The case which is rather rare but serious enough that it should be ruled out for sure is that the wrong machine is part of a man-in-the-middle attack.

In all four cases, an authentic key fingerprint can be acquired by any method where it is possible to verify the integrity and origin of the message, for example via PGP-signed e-mail.  If physical access is possible, then use the console to get the right fingerprint.  Once the authentic key fingerprint is available, return to the client machine where you got the error and remove the old key from '''~/.ssh/known_hosts'''

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -R server.example.org
&lt;/syntaxhighlight&gt;

Then try logging in, but compare the key fingerprints first and proceed if and '''only''' if the key fingerprint matches what you received out of band.  If the key fingerprint matches, then go through with the login process and the key will be automatically added.  If the key fingerprint does not match, stop immediately and figure out what you are connecting to.  It would be a good idea to get on the phone, a real phone not a computer phone, to the remote machine's system administrator or the network administrator.

===Multiple Keys for a Host, Multiple Hosts for a Key in known_hosts===
 
Multiple host names or IP addresses can use the same key in the '''known_hosts''' file by using pattern matching or simply by listing multiple systems for the same key.  That can be done in either the global list of keys in '''/etc/ssh/ssh_known_hosts''' and the local, account-specific lists of keys in each account's '''~/.ssh/known_hosts''' file.  Labs, computational clusters, and similar pools of machines can make use of keys in that way.  Here is a key shared by three specific hosts, identified by name:
&lt;pre&gt;
server1,server2,server3 ssh-rsa AAAAB097y0yiblo97gvl...jhvlhjgluibp7y807t08mmniKjug...==
&lt;/pre&gt;
Or a range can be specified by using globbing to a limited extent in either '''/etc/ssh/ssh_known_hosts''' or '''~/.ssh/known_hosts'''.
&lt;pre&gt;
172.19.40.* ssh-rsa AAAAB097y0yiblo97gvl...jhvlhjgluibp7y807t08mmniKjug...==
&lt;/pre&gt;
Conversely, for multiple keys for the same address, it is necessary to make multiple entries in either '''/etc/ssh/ssh_known_hosts''' or '''~/.ssh/known_hosts''' for each key.
&lt;pre&gt;
server1 ssh-rsa AAAAB097y0yiblo97gvljh...vlhjgluibp7y807t08mmniKjug...==
server1 ssh-rsa AAAAB0liuouibl kuhlhlu...qerf1dcw16twc61c6cw1ryer4t...==
server1 ssh-rsa AAAAB568ijh68uhg63wedx...aq14rdfcvbhu865rfgbvcfrt65...==
&lt;/pre&gt;
Thus in order to get a pool of servers to share a pool of keys, each server-key combination must be added manually to the '''known_hosts''' file:
&lt;pre&gt;
server1 ssh-rsa AAAAB097y0yiblo97gvljh...07t8mmniKjug...==
server1 ssh-rsa AAAAB0liuouibl kuhlhlu...qerfw1ryer4t...==
server1 ssh-rsa AAAAB568ijh68uhg63wedx...aq14rvcfrt65...==

server2 ssh-rsa AAAAB097y0yiblo97gvljh...07t8mmniKjug...==
server2 ssh-rsa AAAAB0liuouibl kuhlhlu...qerfw1ryer4t...==
server2 ssh-rsa AAAAB568ijh68uhg63wedx...aq14rvcfrt65...==
&lt;/pre&gt;

Though upgrading to certificates might be a more appropriate approach that manually updating lots of keys.

===Another way of Dealing with Dynamic (roaming) IP Addresses===
It is possible to manually point to the right key using '''HostKeyAlias''' either as part of [http://man.openbsd.org/ssh_config.5 ssh_config(5)]  or as a runtime parameter.  Here the key for machine ''Foobar'' is used to connect to host 192.168.11.15

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -o StrictHostKeyChecking=accept-new \
      -o HostKeyAlias=foobar   \
      192.168.11.15
&lt;/syntaxhighlight&gt;
This is useful when DHCP is not configured to try to keep the same addresses for the same machines over time or when using certain stdio forwarding methods to pass through intermediate hosts.

===Host Key Update and Rotation in known_hosts===

A protocol extension to rotate weak public keys out of '''known_hosts''' has been in OpenSSH from version 6.8&lt;ref name=&quot;djm_rotation&quot;&gt;
{{cite web
| title=Key rotation in OpenSSH 6.8+ 
| author=Damien Miller
| url=http://blog.djm.net.au/2015/02/key-rotation-in-openssh-68.html
| date=2015-02-01
| publisher=DJM's Personal Weblog
| accessdate=2016-03-05
}}
&lt;/ref&gt; and later.  With it the server is able to inform the client of all its host keys and update '''known_hosts''' with new ones when at least one trusted key already known.  This method still requires the private keys be available to the server &lt;ref name=&quot;djm_rotation_redux&quot;&gt;
{{cite web
| title=Hostkey rotation, redux 
| author=Damien Miller
| url=http://blog.djm.net.au/2015/02/hostkey-rotation-redux.html
| date=2015-02-17
| publisher=DJM's Personal Weblog
| accessdate=2016-03-05
}}
&lt;/ref&gt; so that proofs can be completed.  In [http://man.openbsd.org/ssh_config.5 ssh_config(5)], the directive '''UpdateHostKeys''' specifies whether the client should accept updates of additional host keys from the server after authentication is completed and add them to '''known_hosts'''.  A server can offer multiple keys of the same type for a period before removing the deprecated key from those offered, thus allowing an automated option for rotating keys as well as for upgrading from weaker algorithms to stronger ones.  See also [https://datatracker.ietf.org/doc/html/rfc4819 RFC 4819: Secure Shell Public Key Subsystem] about key management standards.

==Converting Between SSH Key Formats==

OpenSSH has its own format for keys which it uses by default when new keys are made.  However, other SSH clients and servers may use other formats such as [https://www.rfc-editor.org/rfc/rfc4716 RFC4716], [https://www.rfc-editor.org/rfc/rfc5958 PKCS8], or [https://www.rfc-editor.org/rfc/rfc1421 PEM].  Any of these can be converted to the default OpenSSH format by [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)].  The default to format to try to convert from is RFC4716.  The utility [https://linux.die.net/man/1/puttygen puttygen(1)] makes keys in that format for [https://linux.die.net/man/1/putty putty(1)] and they need conversion when used with OpenSSH's server.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -i -f /var/tmp/key_public.ppk
&lt;/syntaxhighlight&gt;

However, you can use the '''-m''' option to specify either that format explicitly or else choose another one to convert from.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -i -m RFC4716 -f /var/tmp/key_public.ppk
$ ssh-keygen -i -m PKCS8 -f /var/tmp/key_public.ppk
&lt;/syntaxhighlight&gt;

Both examples above are for importing public keys into OpenSSH's own format.  

By default OpenSSH will write newly-generated keys in its own format, so the '''-m''' option is obligatory to produce public keys in another format.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -e -m PKCS8 -f ~/.ssh/key.pub
&lt;/syntaxhighlight&gt;

It is not yet possible to export private keys from the OpenSSH format to one of the other formats using the '''-e''' option.  Even if a private key is specified as input, a public key is produced:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -e -m RFC4716 -f ~/.ssh/key
&lt;/syntaxhighlight&gt;

Not all key types are supported by all key formats.  

It is also possible to use export to display the key pair as a traditional hex dump.
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -e -m hexdump -f ~/.ssh/key
Enter passphrase for &quot;key&quot;: 
Public ED25519 key:
buffer len = 51
0000: 00 00 00 0b 73 73 68 2d 65 64 32 35 35 31 39 00  ....ssh-ed25519.
0016: 00 00 20 b0 c5 cc 2c cb d8 8b 8d 75 80 eb e6 e9  .. ...,....u....
0032: 2c f4 36 08 7b 5b ad ad 0b 54 4f 7f 21 9d 1b e8  ,.6.{[...TO.!...
0048: 9e e0 32                                         ..2

Private ED25519 key:
buffer len = 119
0000: 00 00 00 0b 73 73 68 2d 65 64 32 35 35 31 39 00  ....ssh-ed25519.
0016: 00 00 20 b0 c5 cc 2c cb d8 8b 8d 75 80 eb e6 e9  .. ...,....u....
0032: 2c f4 36 08 7b 5b ad ad 0b 54 4f 7f 21 9d 1b e8  ,.6.{[...TO.!...
0048: 9e e0 32 00 00 00 40 e1 c3 a2 4d d9 89 49 72 9b  ..2...@...M..Ir.
0064: 86 72 6c 07 17 1b 40 4f 62 50 62 45 4f 4c cf cf  .rl...@ObPbEOL..
0080: 57 8b 9d c0 04 8f 9b b0 c5 cc 2c cb d8 8b 8d 75  W.........,....u
0096: 80 eb e6 e9 2c f4 36 08 7b 5b ad ad 0b 54 4f 7f  ....,.6.{[...TO.
0112: 21 9d 1b e8 9e e0 32                             !.....2
&lt;/syntaxhighlight&gt;

&lt;noinclude&gt;

== References ==
{{reflist}}
{{OpenSSH/TOC|mini}}
&lt;/noinclude&gt;
{{BookCat}}
{{status|100%}}</text>
      <sha1>nf41g6dj9jxix31heft71tm9mr9r1t3</sha1>
    </revision>
    <revision>
      <id>4675779</id>
      <parentid>4675736</parentid>
      <timestamp>2026-10-13T04:24:40Z</timestamp>
      <contributor>
        <username>Larsnooden</username>
        <id>430753</id>
      </contributor>
      <comment>use Ed25519 in examples instead of RSA, plus refinements and updates</comment>
      <origin>4675779</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="81877" sha1="6pcvt51799ruz674v8dwfe5i3yyv0pg" xml:space="preserve">&lt;noinclude&gt;{{simple chapter navigation|previous=File Transfer with SFTP|next=Certificate-based Authentication}}&lt;/noinclude&gt;
&amp;nbsp;

Authentication keys can improve efficiency, if done properly.  As a bonus advantage, the passphrase and private key never leave the client&lt;ref name=&quot;RFC4252§7&quot;&gt;{{cite web |url=https://tools.ietf.org/html/rfc4252#section-7 |title=The Secure Shell (SSH) Authentication Protocol |publisher=IETF |year=2006| accessdate=2015-05-06}}&lt;/ref&gt;.  Key-based authentication is generally recommended for outward facing systems so that password authentication can be turned off.  

==Key-based authentication==

OpenSSH can use public key cryptography for authentication.  In public key cryptography, encryption and decryption are asymmetric.  The keys are used in pairs, a public key to encrypt and a private key to decrypt.  The [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)] utility can make RSA, Ed25519, MLDSA44-Ed25519, ECDSA, Ed25519-SK, or ECDSA-SK keys for authenticating.  Even though DSA keys can still be made, being exactly 1024 bits in size, they are no longer recommended and should be avoided.  RSA keys are allowed to vary from 1024 bits on up.  The default is now 3072.  However, there is only limited benefit after 2048 bits and that makes elliptic curve algorithms preferable.  ECDSA can be 256, 384 or 521 bits in size.  Ed25519, Ed25519-SK, and ECDSA-SK keys each have a fixed length of 256 bits.  Shorter keys are faster, but less secure.  Longer keys are much slower to work with but provide better protection, up to a point.  

Keys can be named to help remember what they are for.  Because the key files can be named anything it is possible to have many keys each named for different services or tasks.  The comment field at the end of the public key can also be useful in helping to keep the keys sorted, if you have many of them or use them infrequently.  

The process of key-based authentication uses these keys to make a couple of exchanges using the keys to encrypt and decrypt some short message.  At the start, a copy of the client's public key is stored on the server and the client's private key is on the client, both stay where they are.  The private key never leaves the client.  As the client first contacts the server, the server responds by using the client's public key to encrypt a random number and return that encrypted random number as a challenge to the client.  The client responds to the challenge by using the matching private key to decrypt the message and extract the random number.  The client then makes an MD5 hash of the session ID along with the random number from the challenge and returns that hash to the server.  The server then makes its own hash of the session ID and the random number and compares that to the hash returned by the client.  If there is a match, the login is allowed.  If there is not a match, then the next of any public keys on the server registered as belonging to the same account is tried until either a match is found or all the keys have been tried or the maximum number of failures has been reached. &lt;ref name=&quot;How Key Challenges Work&quot;&gt;{{cite web | url=http://www.unixwiz.net/techtips/ssh-agent-forwarding.html#chal | title=An Illustrated Guide to SSH Agent Forwarding | author=Steve Friedl | date=2006-02-22 | accessdate=2013-04-27 | publisher=Unixwiz.net }}&lt;/ref&gt;

When an agent is used on the client side to manage authentication, the process is similar.  The difference is that [http://man.openbsd.org/ssh.1 ssh(1)] passes the challenge off to the agent which then calculates the response and passes it back to [http://man.openbsd.org/ssh.1 ssh(1)] which then passes the agent's response back to the server.  

===Basics of Public Key Authentication===

A matching pair of SSH keys, one public and one private, is needed for public key authentication.  The [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)] utility is used to make such a key pair.  Out of that pair the public key must be properly stored on the remote host before using key-based authentication.  The default location for it is the designated '''authorized_keys''' file, usually one such file resides inside each remote user account.  The private key stays stored safely on the client.  

Once the keys have been prepared and the remote account configured, they can be used for login.  Before starting, there must already be an account on the remote system.  The details of doing that are outside of the scope of this book.  However, once you have a remote account, there are four steps to set up key-based authentication for it:

'''1''') Prepare a directory on the client (say a laptop or a desktop) where the keys will stay, if there isn't one already.  For example, if the '''.ssh''' directory is not on the client machine, create it and set the permissions correctly.  It is important that it not be writable by any account except its owner:
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ mkdir ~/.ssh/
$ chmod 0700 ~/.ssh/
&lt;/syntaxhighlight&gt;

'''2''') Create a key pair inside the designated directory.  The example here creates an Ed25519 key pair in the directory '''~/.ssh'''.  The option '''-t''' decides the key type and the option '''-f''' assigns the key file a name.  It is good to give key files descriptive names, especially if larger numbers of keys are managed.  Below, the public key will be named '''fred_example_org_ed25519.pub''' and the private key will be called '''fred_example_org_ed25519'''.  Lastly, the '''-C''' option is used to embed a descriptive comment inside the private key itself.  The comment is useful for figuring out later what the key is for when one has many keys or a lot of time has passed or both.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -t ed25519 -f ~/.ssh/fred_example_org_ed25519 \
        -C &quot;from fred's laptop to server.example.org&quot;
&lt;/syntaxhighlight&gt;

Be sure to enter a solid passphrase so that the private key gets encrypted using 128-bit AES.  That way the private key can only be read or used when the passphrase is given.  

Ed25519, Ed25519-SK, and ECDSA-SK keys have fixed lengths.  For RSA and ECDSA keys, the '''-b''' option sets the number of bits used for those kinds of keys.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -o -b 4096 -t rsa -f ~/.ssh/fred_example_org_rsa \
        -C &quot;from fred's laptop to server.example.org&quot;
&lt;/syntaxhighlight&gt;

Since 6.5 a new private key format is available using a [http://man.openbsd.org/bcrypt.3 bcrypt(3)] key derivative function (KDF) to better protect keys at rest.  This new format is always used for Ed25519 keys, and sometime in the future will be the default for all keys.  But for right now it may be requested when generating or saving existing keys of other types via the '''-o''' option in [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)].  

Details of the new format are found in the source code in the file '''PROTOCOL.key'''.

'''3''') Get the keys to the right places.  Transfer only the public key to remote machine.  The following assume the default locations for the authorized keys as specified in the server's configuration file by the '''AuthorizedKeysFile''' directive.  

'''3a''') If the utility &lt;code&gt;ssh-copy-id&lt;/code&gt; exists, and if password authentication is allowed, then it can be used to put the public key into place on the remote system.  The ''.pub'' is optional here, the script will figure it out if omitted. 
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-copy-id -i ~/.ssh/fred_example_org_ed25519 fred@server.example.org
&lt;/syntaxhighlight&gt;

If that script was successful in transferring the public key, then go on to step 4 below and test the key.  If not, then try transferring the public key manually as described in step 3b next.

'''3b''') Or the public key can be put in place manually on the remote machine.  For that the remote '''.ssh''' directory is needed, and within that a special file to store the public keys, the default file name is '''authorized_keys'''.  If either the '''authorized_keys''' file or '''.ssh''' directory do not exist on the remote machine, they need to be created.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ mkdir -m 700 ~/.ssh/
$ touch ~/.ssh/authorized_keys
$ chmod 0600 ~/.ssh/authorized_keys
$ nano -w ~/.ssh/authorized_keys
&lt;/syntaxhighlight&gt;

Then any editor which does not wrap long lines can be used to add the public key.  However the '''authorized_keys''' file is edited to add the key, the key itself must be in the file whole and unbroken on a single  line.  For example, [http://linux.die.net/man/1/nano nano(1)] can be started with the '''-w''' option to prevent wrapping of long lines.  (Another way to set line wrapping permanently in [http://linux.die.net/man/1/nano nano(1)] is by editing [http://linux.die.net/man/5/nanorc nanorc(5)].)  

If the key pair is not already on the client, transfer both the public and private keys there.  It is usually best to keep both the public and private keys together in the directory '''~/.ssh/''', though the public key is not always needed on the client after this step and could even be regenerated if it is ever needed again.  

'''4''') Test the keys

While remaining logged in via the first terminal, use the client system to open another window and in it start another SSH session and try authenticating to the remote machine from the client using the private key.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -i ~/.ssh/fred_example_org_ed25519 -l fred server.example.org
&lt;/syntaxhighlight&gt;

The option '''-i''' tells [http://man.openbsd.org/ssh.1 ssh(1)] which private key to try.  
Only after verifying that the key-based authentication works should you close the original window.  

It is possible to make permanent shortcuts on the client using [http://man.openbsd.org/ssh_config.5 ssh_config(5)], explained further below, once key-based authentication is working.  In particular, see the '''IdentityFile''',  '''IdentitiesOnly''', and '''AddKeysToAgent''' configuration directives, to name three.  

It is also a good idea to turn off password authentication, if and only if key-based authentication is setup for all the necessary remote accounts.  

➥ '''Troubleshooting of Key-based Authentication''':

If the server refuses to accept the key and fails over to the next authentication method (e.g.: &quot;Server refused our key&quot;), then there are several possible mistakes to look for on the server side.  

One of the most common errors is that the file and directory permissions are wrong.  The authorized keys file must be owned by the user in question and not be group writable.  Nor may the key file's directory be group or world writable.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ chmod u=rwx,g=rx,o= ~/.ssh
$ chmod u=rw,g=,o=  ~/.ssh/authorized_keys 
&lt;/syntaxhighlight&gt;

Another mistake that can happen is if the key inside the '''authorized_keys''' file on the remote host is broken by line breaks or has other whitespace in the middle.  That can be fixed by joining up the lines and removing the spaces or by recopying the key more carefully.  

And, though it should go without saying, the halves of the key pair need to match.  The public key on the server needs to match the private key held on the client.  If the public key is lost, then a new one can be generated with the '''-y''' option, but not the other way around.  If the private key is lost, then the public key should be erased as it is no longer of any use.  If many keys are in use for an account, it might be a good idea to add comments to them.  On the client, it can be a good idea to know which server the key is for, either through the file name itself or through the comment field.  A comment can be added using the '''-C''' option.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -t ed25519 -f ~/.ssh/fred_example_org_ed25519 -C &quot;web server mirror&quot;
&lt;/syntaxhighlight&gt;

On the server, it can be important to annotate which client they key is from if there is more than one public key there in an account.  There the comment can be added to the authorized keys file on the server in the last column if a comment does not already exist.  Again, the format of the authorized keys file is given in the manual page for [http://man.openbsd.org/sshd.8 sshd(8)] in the section &quot;AUTHORIZED_KEYS FILE FORMAT&quot;.  If the keys are not labeled they can be hard to match, which might or might not be what you want.  

====Associating Keys Permanently with a Server====

A key can be specified at run time, but to save retyping the same paths again and again, the '''Host''' directive in [http://man.openbsd.org/ssh_config.5 ssh_config(5)] can apply specific settings to a target host.  In this case, by changing '''~/.ssh/config''' it is possible to assign particular keys to be tried automatically whenever making a connection to that specific host.  After adding the following lines to '''~/.ssh/config''', all that's needed is to type &lt;code&gt;ssh ''web1''&lt;/code&gt; to connect with the key for that server.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Host web1
	Hostname 198.51.100.32
	IdentitiesOnly yes
	IdentityFile /home/fred/.ssh/web_key_ed25519
&lt;/syntaxhighlight&gt;

The '''~/.ssh/config''' below uses different keys for ''server'' versus ''server.example.org'',  regardless whether they resolve to the same machine.   This is possible because the host name argument given to [http://man.openbsd.org/ssh.1 ssh(1)] is not converted to a canonicalized host name before matching.

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Host server
	IdentitiesOnly yes
	IdentityFile /home/fred/.ssh/key_a_ed25519

Host server.example.org
	IdentitiesOnly yes
	IdentityFile /home/fred/.ssh/key_b_ed25519
&lt;/syntaxhighlight&gt;

In this example the shorter name is tried first, but of course less ambiguous shortcuts can be made instead.  The configuration file gets parsed on a first-match basis.  So the most specific rules go at the beginning and the most general rules go at the end.  

====Encrypted Home Directories====

When using encrypted home directories the keys must be stored in an unencrypted directory.  That means somewhere outside the actual home directory which means [http://man.openbsd.org/sshd.8 sshd(8)] needs to be configured appropriately to find the keys in that special location.  

Here is one method for solving the access problem.  Each user is given a subdirectory under '''/etc/ssh/keys/''' which they can then use for storing their '''authorized_keys''' file.  This is set in the server's configuration file '''/etc/ssh/sshd_config'''

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
AuthorizedKeysFile      /etc/ssh/keys/%u/authorized_keys
&lt;/syntaxhighlight&gt;

Setting a special location for the keys opens up more possibilities as to how the keys can be managed and multiple key file locations can be specified if they are separated by whitespace.  The user does not have to have write permissions for the '''authorized_keys''' file.  Only read permission is needed to be able to log in.  But if the user is allowed to add, remove, or change their keys, then they will need write access to the file to do that.  

One symptom of having an encrypted home directory is that key-based authentication only works when you are already logged into the same account, but fails when trying to make the first connection and log in for the first time.

Sometimes it is also necessary to add a script or call a program from '''/etc/ssh/sshrc''' immediately after authentication to decrypt the home directory.

====Passwordless Login====

One solution for passwordless logins is to still have a passphrase and work with an authentication agent in conjunction with a single-purpose key.  Most desktop environments launch an SSH agent automatically these days.  It will be visible in the '''SSH_AUTH_SOCK''' environment variable if it is.  On accounts with an agent, [http://man.openbsd.org/ssh-add.1 ssh-add(1)] can load private keys into an available agent.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-add ~/.ssh/fred_example_org_ed25519
&lt;/syntaxhighlight&gt;

Thereafter, the client will automatically check the agent for the key when appropriate.  If there are many keys in the agent, it will become necessary to set '''IdentitiesOnly'''.  See the above section on using '''~/.ssh/config''' for that.  See [[OpenSSH/Cookbook/Public_Key_Authentication#Key-based_Authentication_Using_an_Agent|Key-based Authentication Using an Agent]] below.  

Another, riskier, way of allowing passwordless logins is to follow the steps above, but simply do not enter a passphrase when asked for one while creating the key.  Note that using keys that lack a passphrase is very risky, so the key files should be very well protected and kept track of, and ideally locked down with a '''command=''' option or '''ForceCommand''' directive on the server.  That includes those keys which will only be used as single-purpose keys as described below.  

Timely key rotation becomes especially important.  In general, it is not a good idea to make a key without a passphrase.

====Requiring Both Keys and a Password====

While users should have strong passphrases for their keys, there is no way to enforce or verify that.  Indeed, since neither the private key nor its the passphrase ever leave the client machine there is nothing that the server can do to have any influence over that.  Instead, it is possible to require both a key and a password.  Starting with OpenSSH 6.2, it is possible for the server to require multiple authentication methods for login using the '''AuthenticationMethods''' directive.   
&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
AuthenticationMethods publickey,password
&lt;/syntaxhighlight&gt;

This example from [http://man.openbsd.org/sshd_config.5 sshd_config(5)] requires that users first authenticate using a key and it only queries for a password if the key succeeds.  Thus with that configuration it is not possible to get to the system password prompt without first authenticating with a valid key.  Changing the order of the arguments changes the order of the authentication methods.

====Requiring Two or More Keys====

Since OpenSSH 6.8, the server now remembers which public keys have been used for authentication and refuses to accept previously-used keys.  This allows a set up requiring that users authenticate using two different public keys, maybe one in the file system and the other in a hardware token. 

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
AuthenticationMethods publickey,publickey
&lt;/syntaxhighlight&gt;

The '''AuthenticationMethods''' directive, whether for keys or passwords, can also be set on the server under a '''Match''' directive to apply only to certain groups or situations.

====Requiring Certain Key Types For Authentication====

Also since OpenSSH 6.8, the '''PubkeyAcceptedKeyTypes''' directive, later changed to '''PubkeyAcceptedAlgorithms''', can specify which key algorithms are accepted for authentication.  Those not in the comma-separated pattern list are not allowed.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
PubkeyAcceptedAlgorithms ssh-ed25519*,ssh-rsa*,ecdsa-sha2*,sk-ssh-ed25519*,sk-ecdsa-sha2*
&lt;/syntaxhighlight&gt;

Either the actual key types or a pattern can be in the list.  Spaces are not allowed in the pattern list.  The exact list of key types supported for authentication can be found by the '''-Q''' option using the client.  The following two lines are equivalent.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -Q key-sig | sort

$ ssh -Q PubkeyAcceptedAlgorithms | sort
&lt;/syntaxhighlight&gt;

For host-based authentication, it is the '''HostbasedAcceptedAlgorithms''' directive which determines the key types which are allowed for authentication.

===Key-based Authentication Using the AuthorizedKeysCommand Directive===

It is possible to use a program or script to look up public keys rather than keeping them in a static file or files.  Any command called by the '''AuthorizedKeysCommand''' directive needs to either produce a syntactically correct public key while returning the exit code for a successful run or else return the exit code for failure.  The string sent to '''stdout''' will then be processed as part of the authentication work flow.  

Here is a shell script&lt;ref name=&quot;janpietmens&quot;&gt;{{cite web |url=https://jpmens.net/2025/03/25/authorizedkeyscommand-in-sshd/ |title=SSH keys from a command: sshd's AuthorizedKeysCommand directive |accessdate=2025-04-04 |date=2025-03-25 | author=Jan-Piet Mens }}&lt;/ref&gt; at its simplest, without constraints, demonstrating a public key lookup:

&lt;syntaxhighlight lang=&quot;shell&quot;&gt;
#!/bin/sh

echo &quot;ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIKs/UouletvojgB1YeRZ4MY6iRblQ2ERDuNhQO4tOvdL&quot;

exit 0
&lt;/syntaxhighlight&gt;

For authentication to succeed, the script must return exit code 0  (success) after sending the syntactically correct matching public key to '''stdout'''.  For the SSH daemon to even run the script in the first place, the script must have the correct file and directory permissions.

Both the '''AuthorizedKeysCommandUser''' directive and '''AuthorizedKeysCommand''' must be used together.  The former designates which account the script or program use when run.  If set to ''none'' or if it does not refer to a valid account then [http://man.openbsd.org/sshd sshd(8)] will just ignore the command.  If '''AuthorizedKeysCommand''' is set, and '''AuthorizedKeysCommandUser''' is left empty or missing, then [http://man.openbsd.org/sshd sshd(8)] won't even run when invoked.  The error will be:

&lt;syntaxhighlight lang=&quot;text&quot;&gt;
AuthorizedKeysCommand set without AuthorizedKeysCommandUser
&lt;/syntaxhighlight&gt;

The '''AuthorizedKeysFile''' is always tried first when it is present in the server configuration.  The '''AuthorizedKeysCommand''' directive will not even be tried when the authorized keys file can provide a relevant key first.  

====A More Detailed Example Using the AuthorizedKeysCommand Directive====

By default the user name trying to log in is passed to the script when no tokens or arguments are provided.  Whether or how that information is used is up to the script.  The SSH daemon can also pass any combination of the tokens described in the TOKENS section of [http://man.openbsd.org/sshd_config sshd_config(5)] into the program or script being called.  Furthermore, the program or script can even be a front end for a database, such as OpenLDAP, or any similar system, as long as '''stdout''' produces a public key.  

Below is a more detailed example which uses a local script named '''keyfinder''' run with the account '''keys''' to look up the a public key for certain accounts.  First in [http://man.openbsd.org/sshd_config sshd_config(5)] the two directives:

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
AuthorizedKeysCommand /usr/local/sbin/keyfinder %U
AuthorizedKeysCommandUser keys
&lt;/syntaxhighlight&gt;

The script below is only a demonstration and a more complex program can call databases or do advanced lookups or heuristics:  

&lt;syntaxhighlight lang=&quot;shell&quot;&gt;
#!/bin/sh

set -e

case $1 in
        &quot;1000&quot;)
                echo &quot;ssh-ed25519 AAAAC3NzaC1lZDIE5AAAAIK89...UT9hz&quot;
                ;;

        &quot;1001&quot;)
                echo &quot;restrict ssh-ed25519 AAAAC3NzaC1lZDI1NTAAIBvGx...Y0zxV&quot;
                ;;

        &quot;1002&quot;)
                echo &quot;command=\&quot;/usr/libexec/sftp-server\&quot; ssh-ed25519 AAAAC3NzaC1lZDI1TE5AIPSyY...cPTg3&quot;
                ;;

        *)
                exit 1
                ;;
   
esac

exit 0
&lt;/syntaxhighlight&gt;

The '''AuthorizedKeysCommand''' scripts or programs can return any correctly formatted public key to '''stdout''' for consideration in the authentication process.  That includes adding constraints to the keys.  Above, the account with the UID 1000 has no constraints, while the account with UID 1001 is quite constrained.  Finally, the account with the UID 1002 can only access the SFTP service.  See the section &quot;AUTHORIZED_KEYS FILE FORMAT&quot; in [http://man.openbsd.org/sshd sshd(8)] for the full set of possibilities.

===Key-based Authentication Using an Agent===

When an authentication agent, such as [http://man.openbsd.org/ssh-agent.1 ssh-agent(1)], is going to be used, it should generally be started at the beginning of a session and used to launch the login session or X-session so that the environment variables pointing to the agent and its UNIX-domain socket are passed to each subsequent shell and process.  Many desktop distros do this automatically upon login or startup.  

Starting an agent entails setting a pair of environment variables:

* SSH_AGENT_PID : the process id of the agent
* SSH_AUTH_SOCK : the filename and full path to the UNIX-domain socket

The various SSH and SFTP clients find these variables automatically and use them to contact the agent and try when authentication is needed.   However, it is mainly SSH_AUTH_SOCK which is ever used.  If the shell or desktop session was launched using [http://man.openbsd.org/ssh-agent.1 ssh-agent(1)], then these variables are already set and available.  If they are not available, then it is necessary to either set the variables manually inside each shell or for each application in order to use the agent or else to point to the agent's socket using the directive '''IdentityAgent''' in the client's configuration file.  

Once an agent is available, a relevant private key needs to be loaded before the agent can be used.  Once in the agent the private key can then be used many times.  Private keys are loaded into an agent with [http://man.openbsd.org/ssh-add.1 ssh-add(1)].
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-add /home/fred/.ssh/mykey_ed25519
Identity added: /home/fred/.ssh/mykey_ed25519 (/home/fred/.ssh/mykey_ed25519)
&lt;/syntaxhighlight&gt;

Keys stay in the agent for as long as it is running unless specified otherwise.  A timeout can be set either with the '''-t''' option when starting the agent itself or when actually loading the key using [http://man.openbsd.org/ssh-add.1 ssh-add(1)].  In either case, the '''-t''' option will set a timeout interval, after which the key will be purged from the agent.
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-add -t 1h30m /home/fred/.ssh/mykey_ed25519
Identity added: /home/fred/.ssh/mykey_ed25519 (/home/fred/.ssh/mykey_ed25519)
Lifetime set to 5400 seconds
&lt;/syntaxhighlight&gt;

The option '''-l''' will list the fingerprints of all of the identities in the agent.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-add -l                                    
256 SHA256:77mfUupj364g1WQ+O8NM1ELj0G1QRx/pHtvzvDvDlOk mykey for task x (ED25519)
3072 SHA256:7unq90B/XjrRbucm/fqTOJu0I1vPygVkN9FgzsJdXbk myotherkey rsa for task y (RSA)
&lt;/syntaxhighlight&gt;

It is also possible to remove individual identities from the agent using '''-d''' which will remove them one at a time if identified by file name, but only if the file name is given and without the file name of the private key to be remove, '''-d''' will fail silently.  Using '''-D''' instead will remove all of them at once without needing to specify any by name.  

By default [http://man.openbsd.org/ssh-add.1 ssh-add(1)] uses the agent connected via the socket named in the environment variable '''SSH_AUTH_SOCK''', if it is set.  Currently, that is its only option.  However, for [http://man.openbsd.org/ssh.1 ssh(1)] an alternative to using the environment variable is the client configuration directive '''IdentityAgent''' which tells the SSH clients which socket to use to communicate with the agent.  If both the environment variable and the configuration directive are available at the same time, then the value in '''IdentityAgent''' takes precedence over what's in the environment variable.  '''IdentityAgent''' can also be set to ''none'' to prevent the connection from trying to use any agent at all.  

The client configuration directive '''AddKeysToAgent''' can also be useful in getting keys into an agent as needed.  When set, it automatically loads a key into a running agent the first time the key is called for if it is not already loaded.  Likewise the '''IdentitiesOnly''' directive can ensure that the relevant key is offered on the first try.  Rather than typing these out whenever the client is run, they can be added to '''~/.ssh/config''' and thereby added automatically for designated host connections.  

====Agent Forwarding====

Agent forwarding is one means of passing through one or more intermediate hosts.  However, the '''-J''' option for '''ProxyJump''' would be a safer option.  See [[OpenSSH/Cookbook/Proxies_and_Jump_Hosts#Jump_Hosts_--_Passing_Through_a_Gateway_or_Two | Passing Through a Gateway or Two]] in the section on jump hosts about that.  With agent forwarding, intermediate machines forward challenges and responses back and forth between the client and the final destination.  This comes with some risks but eliminates the need for using passwords or holding keys on any of these intermediate machines.  

A main advantage of agent forwarding is that the private key itself is not needed on any remote machine, thus hindering unwanted file system access to it. &lt;ref name=&quot;OpenSSH key management, Part 3&quot;&gt;{{cite web | url=http://www.ibm.com/developerworks/library/l-keyc3/ | title=Common threads: OpenSSH key management, Part 3 | author=Daniel Robbins | publisher=IBM | date=2002-02-01 | accessdate=2013-04-27}}&lt;/ref&gt;  Another advantage is that the actual agent to which the user has authenticated does not go anywhere and is thus less susceptible to analysis.  

One risk with agents is that they can be re-used to tailgate in if the permissions allow it.  Keys cannot be copied this way, but authentication is possible when there are incorrect permissions.  Note that disabling agent forwarding does not improve security unless users are also denied shell access, as they can always install their own forwarders.

The risks of agent forwarding can be mitigated by confirming each use of a key by adding the '''-c''' option when adding the key to the agent.  This requires the SSH_ASKPASS variable be set and available to the agent process, but will generate a prompt on the host running the agent upon each use of the key by a remote system.  So if passing through one or more intermediate hosts, it is usually better to instead have the SSH client use stdio forwarding with '''-W''' or '''-J'''.

On the client side agent forwarding is disabled by default and so if it is to be used it must be enabled explicitly.  Put the following line in  [http://man.openbsd.org/ssh_config.5 ssh_config(5)] to enable agent forwarding for a particular server:
&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
        Host gateway.example.org
        ForwardAgent yes
&lt;/syntaxhighlight&gt;

On the server side the default configuration files allow authentication agent forwarding, so to use it, nothing needs to be done there, just on the client side.  However, again, it would be preferable to take a look at '''ProxyJump''' instead.  

=====Old Style, Somewhat Safer SSH Agent Forwarding=====

The best way to pass through one or more intermediate hosts is to use the '''ProxyJump''' option instead of authentication agent forwarding and thereby not risk exposing any private keys.  If authentication agent forwarding must be used, then it would be advisable in the interest of following the principle of least privilege to forward an agent containing the minimum necessary number of keys.  There are several ways to solve that.  

In version 8.8 and earlier a partial solution is to make a one-off, ephemeral agent to hold just the one key or keys needed for the task at hand.  Another partial solution would be to set up a user-accessible service at the operating system level and then use [http://man.openbsd.org/ssh_config.5 ssh_config] for the rest.  

Automatically launching an ephemeral agent unique to each session can be done by crafting either a special shell alias or function to launch a single-use agent.  Either the function or the alias can be written to require confirmation for each requested signature.  The following example is an alias is based on an updated blog post by Vincent Bernat&lt;ref name=&quot;safer-agent-forwarding&quot;&gt;{{cite web |url=https://vincent.bernat.ch/en/blog/2020-safer-ssh-agent-forwarding |title=Safer SSH agent forwarding |author=Vincent Bernat|date=2020-04-05 |accessdate=2020-10-04}}&lt;/ref&gt; on SSH agent forwarding:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ alias agentssh=&quot;ssh-agent ssh -o AddKeysToAgent=confirm -o ForwardAgent=yes&quot;
&lt;/syntaxhighlight&gt;

Note the use of [http://man.openbsd.org/ssh-agent.1 ssh-agent(1)].  When invoking that alias, the SSH client will be launched with a unique, ephemeral supporting key agent.  The alias sets up a new agent, including setting the two environment variables, and then sets two client options while calling the client.  This arrangement still checks with [http://man.openbsd.org/ssh_config.5 ssh_config(5)] for other options and settings.  When the SSH session is finished the agent which launched it ends and goes away, thus cleaning up after itself automatically.  

Another way is to rely on the client's configuration file for some of the settings.  Such methods rely mostly on [http://man.openbsd.org/ssh_config.5 ssh_config(5)] but still require an independent method to launch an ephemeral agent because the OpenSSH client is already running by the time it reads the configuration file and is thus not affected by any changes to environment variables caused by the configuration file and it is through the environment variables that contain information about the agent.  However, when the path to the UNIX-domain socket used to communicate with the authentication agent is decided in advance then the '''IdentityAgent''' option can point to it once the one-off agent&lt;ref name=&quot;wikimedia_ssh_agents&quot;&gt;{{cite web |url=https://wikitech.wikimedia.org/wiki/Managing_multiple_SSH_agents#Linux_solutions |title=Managing multiple SSH agents |publisher=Wikimedia|accessdate=2020-04-07}}&lt;/ref&gt; is actually launched.  The following uses a specific agent's pre-defined socket whenever connecting to either of two particular domains:

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Host *.wikimedia.org *.wmflabs.org
        User fred
        IdentitiesOnly yes
        IdentityFile %d/.ssh/id_cloud_01
        IdentityAgent /run/user/%i/ssh-cloud-01.socket
        ForwardAgent yes
        AddKeysToAgent yes
&lt;/syntaxhighlight&gt;

The '''%d''' stands for the path to the home directory and the '''%i''' stands for the user id (UID) for the current account.  In some cases the '''%i''' token might also come in handy when setting the '''IdentityAgent''' option inside the configuration file.  Again, be careful when forwarding agents with which keys are in the forwarded agent.  See the section &quot;TOKENS&quot; in [http://man.openbsd.org/ssh_config.5 ssh_config(5)] for more such abbreviations.  

With those configuration settings, the authentication agent must already be up and running and point to the designated socket prior to starting the SSH client for that configuration to work.  Additionally, it should place the socket in a directory which is inaccessible to any other accounts.  [http://man.openbsd.org/ssh-agent.1 ssh-agent(1)] must use the '''-a''' option to name the socket:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-agent -a /run/user/${UID}/ssh-cloud-01.socket
&lt;/syntaxhighlight&gt;

That agent configuration can be launched manually or via a script or service manager.  However, in the interests of privacy and security in general, agent forwarding is to be avoided.  The configuration directive '''ProxyJump''' is the best alternative and, on older systems, host traversal using '''ProxyCommand''' with [http://man.openbsd.org/nc.1 netcat] are preferable.  Again, see the section on [[OpenSSH/Cookbook/Proxies and Jump Hosts|Proxies and Jump Hosts]] for how those methods are used.

=====New Style SSH Agent Destination Constraints=====

From 8.9 onward, [http://man.openbsd.org/ssh-agent.1 ssh-agent(1)] will allow the agent to limit which hosts they will use for authentication as specified by [http://man.openbsd.org/ssh-add.1 ssh-add(1)] using the '''-h''' option.  These constraints have been added through two agent protocol extensions and a modification to the public key authentication protocol.  This feature may evolve, but for now the result is such that keys for account authentication can be loaded into the agent in four ways:

* no limits on forwarding (not recommended)
* local use only, these will not get forwarded
* forwarding, but only to specific remote hosts
* forwarding to specific remote hosts via specified routes

The intent is that the restrictions fail safely so that they do not allow authentication when one or more hosts in the route lack the needed protocol features.  The destinations and routes cannot be modified once the keys are loaded, but multiple routes to the same destination can be loaded and the routes can be any number of hops.  If the routes need changing, then the key must be reloaded into the agent with the new route or routes.  

The general default for the client is to keep keys in the agent for local use only.  However, that can be enforced explicitly by adding the '''-a''' option when starting the client or else setting the '''ForwardAgent''' directive in [http://man.openbsd.org/ssh_config.5 ssh_config(5)] to 'no' in the relevant configuration block.  

In order to load keys for unlimited forwarding, which is not the best idea, just add them using [http://man.openbsd.org/ssh-add.1 ssh-add(1)] as normal.  Then use the '''-A''' option with the client or set the '''ForwardAgent''' directive in [http://man.openbsd.org/ssh_config.5 ssh_config(5)] to 'yes' in the relevant configuration block.  

In order to limit keys for connection only to a specific remote host, or to load keys for connection to a specific remote host with forwarding via one or more intermediate hosts, use the '''-h''' option when loading keys into the agent.  Here the one key may be used only to connect to the specific destination:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-agent -h server.example.org server.key.ed25519
&lt;/syntaxhighlight&gt;

If an intermediate system is passed through, the best way is to use '''ProxyJump''' which is the '''-J''' option for the SSH Client.  If agent forwarding must be allowed then the tightest way is to constrain which systems may use the keys, again using the '''-h''' option.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-agent -h middle.example.org -h &quot;middle.example.org&gt;server.example.org&quot; server.key.ed25519
&lt;/syntaxhighlight&gt;

Multiple steps can be included, even multiple routes.  They just have to be enumerated explicitly, though patterns may still be used for the destination hosts as well as specific names.  Each host in the chain must support these protocol extensions for the connection to complete.  

Any keys designated for forwarding are unusable for authentication on any other hosts than those which have been explicitly identified for forwarding.  These permitted hosts are identified by host key or host certificate from the '''known_hosts''' file or another file designated by the '''-H''' option when loading the key with [http://man.openbsd.org/ssh-add.1 ssh-add(1)].  If '''-H''' is not used at the time the keys are loaded into the agent, then the default known hosts file(s) will be used: '''~/.ssh/known_hosts''', '''/etc/ssh/ssh_known_hosts''', '''~/.ssh/known_hosts2''', and '''/etc/ssh/ssh_known_hosts2'''.

In the case of keys, the '''known_hosts''' list must be maintained conscientiously &lt;ref name=&quot;ssh-agent-restrictions&quot;&gt;{{ cite web | author=Damien Miller|url=https://www.openssh.org/agent-restrict.html | title=SSH agent restriction | publisher=OpenSSH | date=2021-12-16|accessdate=2022-03-06}}&lt;/ref&gt;, perhaps with the help of the '''UpdateHostkeys''' and '''CanonicalizeHostname''' client configuration directives.  Use of certificates requires the agent to only need to be aware of the Certificate Authority (CA).

Again, see [[OpenSSH/Cookbook/Proxies_and_Jump_Hosts#Jump_Hosts_--_Passing_Through_a_Gateway_or_Two | Passing Through a Gateway or Two]] in the section on jump hosts about a way to pass through one or more intermediate machines without needing to forward an SSH agent.

====Checking the Agent for Specific Keys====

The [http://man.openbsd.org/ssh_add ssh_add(1)] utility's '''-T''' option can test whether a specific private key is available in the agent or not by looking up the matching public key.  That can be useful in a shell script.

&lt;syntaxhighlight lang=&quot;shell&quot;&gt;
#!/bin/sh

key=/home/fred/.ssh/some.key.ed25519.pub

if ssh-add -T ${key}; then
        echo &quot;Key ${key} Found&quot;
else
        echo &quot;Key ${key} missing&quot;
fi
&lt;/syntaxhighlight&gt;

Or it could be done with an alternate syntax just as well either in a script or in an interactive shell sessions,

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ key=/home/fred/.ssh/some.key.ed25519.pub
$ ssh-add -T ${key} &amp;&amp; echo &quot;Key found&quot; || echo &quot;Key missing&quot;
&lt;/syntaxhighlight&gt;

However, if the desired result would be to add key to the agent then the '''AddKeysToAgent''' client configuration option can ensure that a specific key is added to the SSH agent upon first use during any given login session.  That can be done using '''-o AddKeysToAgent=yes''' as a run-time argument, or by modifying [http://man.openbsd.org/ssh_config ssh_config(5)] as appropriate:

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Host www
        HostName www.example.com
        IdentityFile %d/.ssh/www.ed25519
        IdentitiesOnly yes
        AddKeysToAgent yes
&lt;/syntaxhighlight&gt;

With those options in the configuration file, the first time &lt;code&gt;ssh www&lt;/code&gt; is run the specified key will get added to the agent and remain available.

===Key-based Authentication Using A Hardware Security Token===

While stand-alone keys have been around for a long time, it has been possible since version 8.2 to use keys backed by hardware security tokens, such as OnlyKey, Yubikey, or many others, though the FIDO2 protocol.  The Universal 2nd Factor (U2F) authentication is supported directly in OpenSSH through FIDO2 and does not need third party software.  At the moment there are two types of hardware backed keys, ECDSA-SK and Ed25519-SK, but only the latest hardware tokens support the latter.  If the key Ed25519-SK format is not supported by the token's firmware, then the following error message will be presented when attempts to use that key type are made:

&lt;syntaxhighlight lang=&quot;text&quot;&gt;
Key enrollment failed: invalid format
&lt;/syntaxhighlight&gt; 

If supported, either key type can be created with [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)].  The steps are almost identical to creating normal keys but the token must be available to the system (plugged in) first.  Then if called for, the token's PIN must be entered and the token touched or otherwise activated.  After that, the key creation proceeds as normal.  Mind the key type as specified by the '''-t''' option.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -t ed25519-sk -f /home/fred/.ssh/server.ed25519-sk -C &quot;web server for fred&quot;
Generating public/private ed25519-sk key pair.
You may need to touch your authenticator to authorize key generation.
Enter passphrase (empty for no passphrase): 
Enter same passphrase again: 
Your identification has been saved in /home/fred/.ssh/server.ed25519-sk
Your public key has been saved in /home/fred/.ssh/server.ed25519-sk.pub
The key fingerprint is:
SHA256:41wVVDnKJ9gKr2Sj4CFuYMhcNvYebZ6zq0PWyP4rRDo web server
The key's randomart image is:
+[ED25519-SK 256]-+
|           .o... |
|             .o  |
|           +.. . |
|   = .  . ..= .  |
|+ + * + So.. o   |
|o+.EoO *+oo      |
|.o oBo+++o       |
|  o .=.+.        |
| .   .===        |
+----[SHA256]-----+
&lt;/syntaxhighlight&gt;

Once created, the public and private key files get handled like with any other type of key.  But when authenticating, the hardware token must be present and activated when called for.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -i /home/fred/.ssh/server.ed25519-sk server.example.org
Enter passphrase for key '/home/fred/.ssh/server.ed25519-sk': 
Confirm user presence for key ED25519-SK SHA256:41wVVDnKJ9gKr2Sj4CFuYMhcNvYebZ6zq0PWyP4rRDo
&lt;/syntaxhighlight&gt;

The resulting private key file is not actually the key itself but instead a &quot;key handle&quot; which is used by the hardware security token to derive the real private key on demand at the time it is actually used&lt;ref name=&quot;OpenBSD_tech_U2F_FIDO&quot;&gt;{{cite web |url=https://marc.info/?l=openbsd-tech&amp;m=157376801917387&amp;w=2 |title=OpenSSH U2F/FIDO support in base 
|publisher=OpenBSD-Tech Mailing List | date=2019-11-14
|accessdate=2021-03-24}}&lt;/ref&gt;.  As a result, the hardware-backed private key file is useless without the accompanying hardware token.  This also means that these key files are not portable across hardware tokens, say when having multiple tokens in reserve or as backup, even when used by the same account.  So when multiple hardware tokens are in use, different key pairs must be generated for each token.

====Hardware Security Token Resident Private Key====

It is possible to store the private key within the token itself, but for the moment it cannot be used directly from inside the token and must first be saved as a file.  Also, the key can only be loaded into the FIDO authenticator at the time of creation  using the '''-O resident''' option with [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)].  Otherwise, the process is the same as above.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -O resident -t ed25519-sk -f /home/fred/.ssh/server.ed25519-sk -C &quot;web server for fred&quot;
. . .
&lt;/syntaxhighlight&gt;

When needed, the resident key can be extracted from the FIDO2 hardware token and saved into a file using the '''-K''' option.  At this stage a passphrase can be added to the file, but no passphrase is kept within the token itself, only an optional PIN protects the key there.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -K
Enter PIN for authenticator: 
Enter passphrase (empty for no passphrase): 
Enter same passphrase again: 
Saved ED25519-SK key to id_ed25519_sk_rk

$ mv -i id_ed25519_sk_rk /home/fred/.ssh/server.ed25519-sk
&lt;/syntaxhighlight&gt;

Since the output file name is fixed, any pre-existing file with that name can get overwritten but there will be a warning first.  However, it is not recommended to keep the key on the hardware token because it provides more protection when kept separately.

==Single-purpose Keys==

Tailored single-purpose keys can eliminate use of remote root logins for many administrative activities.  A  finely tailored '''sudoers''' is needed along with an unprivileged account.  When done right, it gives just enough access to get the job done, following the security principle of Least Privilege.  

Single-purpose keys are accompanied by use of either the '''ForceCommand''' directive in [http://man.openbsd.org/ssh_config.5 sshd_config(5)] or the '''command=&quot;...&quot;''' directive inside the '''authorized_keys''' file.  The method is to generate a new key pair, transfer the public key to '''authorized-keys''' on the remote system, and then prepend the appropriate command or script there to the line with the key.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ grep '^command' ~/.ssh/authorized_keys
command=&quot;/usr/local/bin/somescript.sh&quot; ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIEcgdzDvSebOEjuegEx4W1I/aA7MM3owHfMr9yg2WH8H
&lt;/syntaxhighlight&gt;

The '''command=&quot;...&quot;''' directive inserted there overrides everything else and ensures that when logging in with just that key only the script '''/usr/local/bin/somescript.sh''' is run.  If it is necessary to pass parameters to the script, have a look at the contents of the '''SSH_ORIGINAL_COMMAND''' environment variable and use it in a case statement.  Do not ever trust the contents of that variable nor use the contents directly, always indirectly.  

Single-purpose keys are useful for allowing only a tunnel and nothing more.  The following key will only echo some text and then exit, unless used non-interactively with the '''-N''' option.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ grep '^command' ~/.ssh/authorized_keys
command=&quot;/bin/echo do-not-send-commands&quot; ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIBzTIWCaILN3tHx5WW+PMVDc7DfPM9xYNY61JgFmBGrA 
&lt;/syntaxhighlight&gt; 

No matter what the user tries while logging in with that key, the session will only echo the given text and then exits.  Using the '''-N''' option disables running the remote program, allowing the connection to stay open, allowing a tunnel. 

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -L 3306:localhost:3306 \
	-i ~/.ssh/tunnel_ed25519 \
	-N \
	-l fred \
	server.example.com
&lt;/syntaxhighlight&gt;

That creates a tunnel and stays connected despite a key configuration which would close an interactive session.  See also the '''-n''' or '''-f''' option for [http://man.openbsd.org/ssh.1 ssh(1)].  

===Single-purpose Keys to Avoid Remote Root Access===

The easy way is to write a short shell script, place it '''/usr/local/bin/''', and then configure '''sudoers''' to allow the otherwise unprivileged account to run just that script and only that script.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
%wheel  ALL=(root:root) NOPASSWD: /usr/sbin/service httpd stop
%wheel  ALL=(root:root) NOPASSWD: /usr/sbin/service httpd start
&lt;/syntaxhighlight&gt;

Then the key calls the script using '''command=&quot;...&quot;''' inside '''authorized_keys'''.  Here the one key starts the web server, the other stops the web server.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ grep '^command' ~/.ssh/authorized_keys
command=&quot;/usr/bin/sudo /usr/sbin/service httpd stop&quot; ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIEcgdzDvSebOEjuegEx4W1I/aA7MM3owHfMr9yg2WH8H
command=&quot;/usr/bin/sudo /usr/sbin/service httpd start&quot; ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMidyqZ6OCvbWqA8Zn+FjhpYE6NoWSxVjFnFUk6MrNZ4
&lt;/syntaxhighlight&gt;

Complicated programs like [http://linux.die.net/man/1/rsync rsync(1)], [http://man.openbsd.org/tar.1 tar(1)], [http://linux.die.net/man/1/mysqldump mysqldump(1)], and so on require an advanced approach when building a single-purpose key.  For them, the '''-v''' option can show exactly what is being passed to the server so that '''sudoers''' can be set up correctly.  That way they can be restricted to only access designated parts of the file system.  For example, here is what &lt;code&gt;ssh -v&lt;/code&gt; shows from one particular usage of [http://linux.die.net/man/1/rsync rsync(1)], note the &quot;Sending command&quot; line:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ rsync -e 'ssh -v' fred@server.example.org:/etc/ ./backup/etc/
. . .
debug1: Sending command: rsync --server --sender -e.LsfxC . /etc/
. . .
&lt;/syntaxhighlight&gt;

That output can then be added to '''sudoers''' so that the key can do only that function.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
%backup ALL=(root:root) NOPASSWD: /usr/bin/rsync --server --sender -e.LsfxC . /etc/
&lt;/syntaxhighlight&gt;

Then to tie it all together, the account &quot;backup&quot; needs a key:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ grep '^command' ~/.ssh/authorized_keys
command=&quot;/usr/bin/rsync --server --sender -e.LsfxC . /etc/&quot; ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMm0rs4eY8djqBb3dIEgbQ8lmdlxb9IAEuX/qFCTxFgb 
&lt;/syntaxhighlight&gt;

Many of these programs have a '''--dry-run''' or equivalent option.  Remember to use it when figuring out the right settings.

===Read-only Access to Keys===

In some cases it is necessary to prevent accounts from being able to changing their own authentication keys.  However, such situations may be a better case for using certificates.  However, if done with keys it is accomplished by putting the key file in an external directory where the user has read-only access, both to the directory and to the key file.  Then the '''AuthorizedKeysFile''' directive assigns where [http://man.openbsd.org/sshd.8 sshd(8)] looks for the keys and can point to a secured location for the keys instead of the default location.

A good alternate location could be a new directory '''/etc/ssh/authorized_keys''' which could store the selected accounts' key files there.  The change can be made to apply to only a group of accounts by putting the settings under a '''Match''' directive.  The default location for keys on most systems is usually '''~/.ssh/authorized_keys'''.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Match Group sftpusers
	AuthorizedKeysFile /etc/ssh/authorized_keys/%u
&lt;/syntaxhighlight&gt;

Then the permissions there would allow the keys to be read but not written:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ls -dhln /etc/ssh/
drwxr-x--x 3 0 0 4.0K Mar 30 22:16 /etc/ssh/authorized_keys/

$ ls -dhln /etc/ssh/*.pub
-rw-r--r-- 1 0 0 173 Mar 23 13:34 /etc/ssh/fred
-rw-r--r-- 1 0 0  93 Mar 23 13:34 /etc/ssh/user1
-rw-r--r-- 1 0 0 565 Mar 23 13:34 /etc/ssh/user2
. . .
&lt;/syntaxhighlight&gt;

The keys could even be within subdirectories, though the same restrictions apply regarding permissions and ownership.  

For chrooted SFTP, the method is the same to keep the key files out of reach of the accounts:  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Match Group sftpusers
	ChrootDirectory /home
	ForceCommand internal-sftp -d %u
	AuthorizedKeysFile /etc/ssh/authorized_keys/%u
&lt;/syntaxhighlight&gt;

Of course a '''Match''' directive is not essential.  The settings could be made to apply to all accounts by putting the directive in the main part of the server configuration file instead.

==Mark Public Keys as Revoked==

Keys can be revoked.  Keys that have been revoked can be stored in '''/etc/ssh/revoked_keys''', a file specified in [http://man.openbsd.org/ssh_config.5 sshd_config(5)]  using the directive '''RevokedKeys''', so that [http://man.openbsd.org/sshd.8 sshd(8)] will prevent attempts to log in with them.  No warning or error on the client side will be given if a revoked key is tried.  Authentication will simply progress to the next key or method.

The revoked keys file should contain a list of public keys, one per line, that have been revoked and can no longer be used to connect to the server.  The key cannot contain any extras, such as [[OpenSSH/Client_Configuration_Files#Available_key_login_options | login options]] or it will be ignored. If one of the revoked keys is tried during a login attempt, the server will simply ignore it and move on to the next authentication method.  An entry will be made in the logs of the attempt, including the key's fingerprint.  See the section on [[OpenSSH/Logging_and_Troubleshooting | logging]] for a little more on that.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
RevokedKeys /etc/ssh/revoked_keys
&lt;/syntaxhighlight&gt;

The '''RevokedKeys''' configuration directive is not set in [http://man.openbsd.org/ssh_config.5 sshd_config(5)] by default.  It must be set explicitly if it is to be used.  This is another situation that might be better fulfilled through using certificate since a validity interval can be set in any combination of seconds, minutes, hours, days, or weeks can be set for certificates while keys are valid indefinitely.  

===Key Revocation Lists===

A Key Revocation List (KRL) is a compact, binary form of representing revoked keys and certificates.  In order to use a KRL, the server's configuration file must point to a valid list using the '''RevokedKeys''' directive.  KRLs themselves are generated with [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)] and can be created from scratch or edited in place.  Here a new one is made, populated with a single public key: 

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -k -f /etc/ssh/revoked_keys -z 1 ~/.ssh/old_key_rsa.pub
&lt;/syntaxhighlight&gt;

Here an existing KRL is updated by adding the '''-u''' option:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -u -k -f /etc/ssh/revoked_keys -z 2 ~/.ssh/old_key_dsa.pub
&lt;/syntaxhighlight&gt;

Once a KRL is in place, it is possible to test if a specific key or certificate is in the revocation list.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -Q -f /etc/ssh/revoked_keys ~/.ssh/old_key_rsa.pub
&lt;/syntaxhighlight&gt;

Only public keys and certificates will be loaded into the KRL.  Corrupt or broken keys will not be loaded and will produce an error message if tried.  Like with the regular '''RevokedKeys''' list, the public key destined for the KRL cannot contain any extras like login options or it will produce an error when an attempt is made to load it into the KRL or search the KRL for it.

==Verify a Host Key by Fingerprint==

The above examples have been about using keys to authenticate the client to the server.  A different context in which keys are used is when the server identifies itself to the client, which happens automatically at the beginning of each non-multiplexed session.  In order for that identification to happen the client acquires a public key from the server, usually on or prior to first contact, which it can subsequently use to ensure that it is connecting to the same server again and not an impostor.  The default locations for storing these acquired host keys on the client are in '''/etc/ssh/ssh_known_hosts''', if managed by the system administrator, or in '''~/.ssh/known_hosts''' if managed by the client's own account.  The format of the contents is a line with a host address and its matching public key.  The file is described in detail in the [http://man.openbsd.org/sshd.8 sshd(8)] manual page in the section &quot;SSH_KNOWN_HOSTS FILE FORMAT&quot;.

When connecting for the first time to a remote host, the server's host key should be verified in order to ensure that the client is connecting to the right machine and not an impostor or anything else.  Usually this verification is done by comparing the fingerprint of the server's host key rather than trying to compare the whole key itself.  By default the client will show the fingerprint if the key is not already found in the '''known_hosts''' register.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -l fred server.example.org
The authenticity of host 'server.example.org (192.0.32.10)' can't be established.
ECDSA key fingerprint is SHA256:LPFiMYrrCYQVsVUPzjOHv+ZjyxCHlVYJMBVFerVCP7k.
Are you sure you want to continue connecting (yes/no)? 
&lt;/syntaxhighlight&gt;

That can be compared to a fingerprint received out of band, say by post, e-mail, SMS, courier, and so on.  Specifically, the example represents the key's fingerprint as a base64 encoded SHA256 checksum.  That is the default style.  The fingerprint can also be displayed as an MD5 hash in hexadecimal instead by passing the client's '''FingerprintHash''' configuration directive as a runtime argument or setting it in [http://man.openbsd.org/ssh_config.5 ssh_config(5)].  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -o FingerprintHash=md5 host.example.org
The authenticity of host 'host.example.org (192.0.32.203)' can't be established.
RSA key fingerprint is MD5:10:4a:ec:d2:f1:38:f7:ea:0a:a0:0f:17:57:ea:a6:16.
Are you sure you want to continue connecting (yes/no)?
&lt;/syntaxhighlight&gt;

But the default in new versions is SHA256 in base64 has a lower chance of collision.

In OpenSSH 6.7 and earlier, the client showed fingerprints as a hexadecimal MD5 checksum instead a of the base64-encoded SHA256 checksum currently used:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -l fred server.example.org
The authenticity of host 'server.example.org (192.0.32.10)' can't be established. 
RSA key fingerprint is 4a:11:ef:d3:f2:48:f8:ea:1a:a2:0d:17:57:ea:a6:16. 
Are you sure you want to continue connecting (yes/no)? 
&lt;/syntaxhighlight&gt;

Another way of comparing keys is to use the ASCII art visual host key.  See further below about that.  

===Downloading keys===

Even though a host’s key is usually displayed for review the first time the SSH client tries to connect, it can also be fetched on demand at any time using [http://man.openbsd.org/ssh-keyscan.1 ssh-keyscan(1)]:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keyscan server.example.org
# server.example.org:22 SSH-2.0-OpenSSH_10.6
server.example.org ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBEWKepJgkC2XTG5cAr2Nyew6hOp5AjG7vi2RYFtPWqN3bo5XGuCX2d2YVyn++/2PtyMYBaKWyFpCNTT9X0F1Epg=
# server.example.org:22 SSH-2.0-OpenSSH_10.6
server.example.org ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQDKyERe8k+fnsrt4JrcLD3AW0kXj90r9ybrEZuY/CTrXIqYSizO335SxGJoWrKijaRy8htuueMkmNfxxhnBPoAjul/4T/FCRGKaV0jC96xYNnKcXbnXxSLVQ0OW2EIPvQhw/TU/G3vEqtiRYGyaNcZS6xrnVv3xuPuvVC1VRKspNLEq7zfvToC0OB89X5DIbvBbHY13PjJ0NrDdX3sSA8lxPsYagBuDIvyxH0S4Z5fQHeYrdvENS5zX6LwJeMeGSOqDuD0Zb4hpKxhaGVwP5e435VcFuImbFaDPM4w71PzaSUEj+tnUA0mGDoLiCrpW3txkJszog9lN3C/nLGghFaT7ajrfH55qut81JnvdhMju9+SzxrKPJmtQZfKVLIc4whEbtFsPCdm2bstz7ROWxTJ3t/Vr8/QVm2G2aY4FHuPwo2jUQDbQA7mCV+fe1sADy2jLzGhn1TCeYvWSv5PNJAT97IrLfD3+0Uo+qJD/6CU7F8oabj1Ql2H8fPN5kGSWfkM=
# server.example.org:22 SSH-2.0-OpenSSH_10.6
server.example.org ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIJo5gc4VrxVQ5apAOd7qK6UqGlLMpWOPuunjB53JBN2s
# server.example.org:22 SSH-2.0-OpenSSH_10.6
# server.example.org:22 SSH-2.0-OpenSSH_10.6
# server.example.org:22 SSH-2.0-OpenSSH_10.6
server.example.org ssh-mldsa44-ed25519 AAAAE3NzaC1tbGRzYTQ0LWVkMjU1MTkAAAVAyIw5r9FaniSYqBX0yd9vgBz5nCkebaQlMQN9N0p//Ukfn/CnZ3YtZWn6pUGjDM85/bqdL1gqah1OLfnl1eHk0qvTACrym07uKaMLoEHuakIXHbTi/ELPRoRP3F+DpEgjtYSjLc/fJiobRMgSvmLJxTUzZTStsqWAL1L9/1zuwHEngR+THpUcCSTi6KKkYcQiWGOFwpO22VdiuOg+zdQSH+9jW6eXYk1z81KU6UlHZps8zVrlqCd3FDDghgbH5U8DcGN2t6GvVfn6jFjpEk0ouj0of3/7010eRXjnv3QSbprCpMq73lAemQM+3LvTtrMBhFWNhCXhyOHfO1Yq7c8xaOwlFK78PlERjdHTvVJaCaDFDy7Pg9I+wxv+uC+W0wtzJ2S1y9XCYUgJo9yEiIGuSZdhMkYUwMnXLzQMm44hQOW153pdlHWze3kESCLg/LJf9RbUoSB43t6rghSHEiUkIi5TtCtFZ4nAGeH+wVwlB9Fwog5uZuJN1FYuuY5sSrLHJAQDUwudkdak0ifOhtPtsM/ClYr3baolQ/qi0ABYUVLKSV5b+A5DlTXa23zc7JAXm2YVfkWpOfVJG4TY81wrJoDumsd1y3XaH28/4QbADsZCE3wYsBou8ff0xKgPu8xm2K+sYSmzUbBGprArAQA0LtIDGNGqrb4JsZ1ru+viwzfSlxV7Nz7ZrSw6h+Ddq4J9A6oKXy6YS3uf1GFOtBQm6JfuyMHQEEUtYZrU4UK3C/fKHx9vjuw7YdhsL8JRgxbF14qJLFizkmVbK2e6aWEE4iCqLLLlZ0dC2peYUUqyGb9PsW7sewYzGbipzPpQ/GobRT3Obc3Gmu8P386pDGR7hmkOpFmVwIcfc431cUmZixK7CkPxzUvfaAAQkmNs/p4eNNoP0gq/xPGsV14/heULbWp/njGWk1ysjjGxP6YMwHcEZpUdSGbD05zbL0KkMtmKsr8yuJYjdVAgtH2bVAvrxXRXLgavmm97VYYq1A9rOYiQFlMrKRg6yZhT10Xt8Hukf6ySLk+fieFc3nH99YeysoA5rsfp9kdXr65GpwrBerZlf/20ZLJ7s4xaYb9SukR/8tiPt9iAVQjqPdb0MseZVrzhKo/jK44JHbHejHMoMMs7etPAS5TIjHxcJTP66B3eO9A0l2fAage2ka7ehTnHivxD3EE9KnqYBjIHDU7o6dTrX7UyQsdhax9bPKEL7OEtm6hXXfwzy4GdqGi124BclFAF0LeBSvBUgmSKIn3wfzJx/XXbt512eOn3WZk2v0TsiteH9kPEgDxVkUykawg2tleak9rTFMzYpDZRHvZD7uHWUZ8ktr2FEKWgq7/1Q2c80Z6H75VK9l1d3KZuoiWoF1s73R7ZAM+CWSrR+S5h+3AhYubDKPa/af+Lnlqe6ocVTqQPYaaRz25/cLBg6pgbdh18Ru6h3ljG2KiysyXeuoEoM5xVYtdIW7l9NeKDpGbZPAOqywXUpK+UCGjumIl7c48KCTIYcdtolnEbfVNBh0LRuftcVI+uF9cvQ0XacaNbgkYJYCjv4VR/n58EJ1b0c7tQBrVqMjDjIUKGhCMQqAeD3g75jeD60bBmVNPrq8RK+zH5VIa5eaBs3eitN98eVzd4b6UYTQd1QxLQZMrhQf4InRj39TZfGvQR5SXlLZQlweVHYkMps3IKbs3B3DCqlWCPUAnTAJBAG7HqWEYr5uEaKBawBSAx9jCQz00T+bp8KXpkOPzZCD6dfEfpHY6Rv6kmGJkiPUCb2hoX145HrS357G12+wDxKLN833oPVC0z
&lt;/syntaxhighlight&gt;

Once a key is acquired, its fingerprint can be shown using [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)] to read from '''stdin'''.  This can be done directly with a pipe.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keyscan server.example.org | ssh-keygen -l -f -
3072 SHA256:tQlw3vy325KrQibndP3gLS/YXUZjTLVA5yDFpg/Bb6I server.example.org (RSA)
256 SHA256:snnAtb/9csdy0BGhPjdg+VNWqN5bxCa/ge4C6zZ8muk server.example.org (ECDSA)
256 SHA256:agRZDZn8awhQ+tc19Ip/whkHoV33Ln2REO7v1kcYbdU server.example.org (ED25519)
512 SHA256:3Wdc6GbLIcc5mbuF2mhhokhARdMLuMK+ESRfJ+sM0QE server.example.org (MLDSA44-ED25519)
&lt;/syntaxhighlight&gt;

If there is more than one public key type is available from the server on the port polled, then [http://man.openbsd.org/ssh-keyscan.1 ssh-keyscan(1)] will fetch each of them.  If there is more than one key fed via '''stdin''' or a file, then [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)] will process them in order.  Prior to OpenSSH 7.2 manual fingerprinting was a two step process, the key was read to a file and then processed for its fingerprint.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keyscan -t ed25519 host.example.org &gt; key.pub
# host.example.org SSH-2.0-OpenSSH_6.8
$ ssh-keygen -lf key.pub                       
256 SHA256:ZmS+IoHh31CmQZ4NJjv3z58Pfa0zMaOgxu8yAcpuwuw host.example.org (ED25519)
&lt;/syntaxhighlight&gt;

Note that some output from [http://man.openbsd.org/ssh-keyscan.1 ssh-keyscan(1)] is sent to '''stderr''' instead of '''stdout'''.  

A hash, or fingerprint, can be generated manually with [http://linux.die.net/man/1/awk awk(1)], [http://linux.die.net/man/1/sed sed(1)] and [http://linux.die.net/man/1/xxd xxd(1)], on systems where they are found.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ awk '{print $2}' key.pub | base64 -d | md5sum -b | sed 's/../&amp;:/g; s/: .*$//'
$ awk '{print $2}' key.pub | base64 -d | sha256sum -b | sed 's/ .*$//' | xxd -r -p | base64 
&lt;/syntaxhighlight&gt;

It is possible to find all hosts from a file which have new or different keys from those in '''known_hosts''', if the host names are in clear text and not stored as hashes.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keyscan -t ed25519,mldsa44-ed25519 -f ssh_hosts | \
  sort -u - ~/.ssh/known_hosts | \
  diff ~/.ssh/known_hosts -
&lt;/syntaxhighlight&gt;

====Using ssh-keyscan(1) with ssh_config(5)====

The utility [http://man.openbsd.org/ssh-keyscan.1 ssh-keyscan(1)] does not parse [http://man.openbsd.org/ssh_config.5 ssh_config(5)].  That is in part to keep the code base simple.  There are a lot of configuration options which would be complicated to implement, including but not limited to '''ProxyJump''', '''ProxyCommand''', '''Match''', '''BindInterface''', and '''CanonicalizeHostname'''&lt;ref name=&quot;keyscan&quot;&gt;{{cite mailing list |url=https://lists.mindrot.org/pipermail/openssh-unix-dev/2023-March/040605.html | title=Why does ssh-keyscan not use .ssh/config? |publisher=mindrot.org | access-date=2023-03-01 | date=2023-03-01 | mailing-list=OpenSSH UNIX-dev | first=Damien | last=Miller }}&lt;/ref&gt; .  Resolving host names via the client configuration file can be done by wrapping the utility in a short shell function:

&lt;syntaxhighlight lang=&quot;shell&quot;&gt;
my-ssh-keyscan() {
	for host in &quot;$@&quot; ; do
		ssh-keyscan $(ssh -G &quot;$host&quot; | awk '/^hostname/ {print $2}')
	done
}
&lt;/syntaxhighlight&gt;

That shell function uses the '''-G''' option of [http://man.openbsd.org/ssh.1 ssh(1)] to resolve each host name using [http://man.openbsd.org/ssh_config.5 ssh_config(5)] and then check the resulting host name for SSH keys.

===ASCII Art Visual Host Key===

An ASCII art representation of the key can be displayed along with the SHA256 base64 fingerprint: 

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -l -v -f key 
256 SHA256:BClQBFAGuz55+tgHM1aazI8FUo8eJiwmMcqg2U3UgWU www.example.org (ED25519)
+--[ED25519 256]--+
|o+=*++Eo         |
|+o .+.o.         |
|B=.oo.  .        |
|*B.=.o .         |
|= B *   S        |
|. .@ .           |
| +..B            |
|  *. o           |
| o.o.            |
+----[SHA256]-----+
&lt;/syntaxhighlight&gt;

In OpenSSH 6.7 and earlier the fingerprint is in MD5 hexadecimal form.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -l -v -f key 
2048 37:af:05:99:e7:fb:86:6c:98:ee:14:a6:30:06:bc:f0 www.example.net (RSA) 
+--[ RSA 2048]----+ 
|          o      | 
|         o .     | 
|        o o      | 
|       o +       | 
|   .  . S        | 
|    E ..         | 
|  .o.* ..        | 
|  .*=.+o         | 
|  ..==+.         | 
+-----------------+ 
&lt;/syntaxhighlight&gt;

==More on Verifying SSH Keys==

Keys on the client or the server can be verified against known good keys by comparing the base64-encoded SHA256 fingerprints.  

===Verifying Stray Client Keys===

Sometimes is is necessary to compare two uncertain key files to check if they are part of the same key pair.  However, public keys are more or less disposable.  So the easy way in such situations on the client machine is to just rename or erase the old, problematic, public key and replace it with a new one generated from the existing private key.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -y -f ~/.ssh/my_key_ed25519
&lt;/syntaxhighlight&gt;

But if the two parts must really be compared, it is done in two steps using [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)].  First, a new public key is re-generated from the known private key and used to make a fingerprint to '''stdout'''.  Next, the fingerprint of the unknown public key is generated for comparison.  In this example, the private key '''my_key_a_ed25519''' and the public key '''my_key_b_ed25519.pub''' are compared:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -y -f my_key_a_ed25519 | ssh-keygen -l -f -
$ ssh-keygen -l -f my_key_b_ed25519.pub
&lt;/syntaxhighlight&gt;

The result is a base64-encoded SHA256 checksum for each key with the one fingerprint displayed right below the other for easy visual comparison.  Older versions don't support reading from '''stdin''' so an intermediate file will be needed then.  Even older versions will only show an MD5 checksum for each key.  Either way, automation with a shell script is simple enough to accomplish but outside the scope of this book.

===Verifying Server Keys===

Reliable verification of a server's host key must be done when first connecting.  It can be necessary to contact the system administrator who can provide it out of band so as to know the fingerprint in advance and have it ready to verify the first connection.  

Here is an example of the server's Ed25519 key being read and its fingerprint shown as SHA256 base64:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -l -f /etc/ssh/ssh_host_ed25519_key.pub 
256 SHA256:bFzzouaWmE5HuZIv+YnGUYI2q06i6M43V+6jMU3LHpA root@server.example.org (ED25519)
&lt;/syntaxhighlight&gt;

And here the corresponding ECDSA key is read, but shown as an MD5 hexadecimal hash:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -E md5 -l -f /etc/ssh/ssh_host_ecdsa_key.pub
256 MD5:ed:d2:34:b4:93:fd:0e:eb:08:ee:b3:c4:b3:4f:28:e4 root@server.example.net (ECDSA)
&lt;/syntaxhighlight&gt;

Prior to 6.8, the fingerprint was expressed as an MD5 hexadecimal hash:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -l -f /etc/ssh/ssh_host_rsa_key.pub 
2048 MD5:e4:a0:f4:19:46:d7:a4:cc:be:ea:9b:65:a7:62:db:2c root@server.example.net (RSA)
&lt;/syntaxhighlight&gt;

It is also possible to use [http://man.openbsd.org/ssh-keyscan.1 ssh-keyscan(1)] to get keys from an active SSH server.  However, the fingerprints still needs to be verified out of band.  

====Warning: Remote Host Identification Has Changed!====

If a server's key does not match what the client finds has been recorded in either the system's or the local account's '''authorized_keys''' files, then the client will issue a warning along with the fingerprint of the suspicious key.  

&lt;pre&gt;
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the ED25519 key sent by the remote host is
SHA256:bFzzouaWmE5HuZIv+YnGUYI2q06i6M43V+6jMU3LHpA.
Please contact your system administrator.
Add correct host key in /home/fred/.ssh/known_hosts to get rid of this message.
Offending ED25519 key in /home/fred/.ssh/known_hosts:11
Host key for server.example.org has changed and you have requested strict checking.
Host key verification failed.
&lt;/pre&gt;

Three reasons for the warning are common.  

One reason is that the server's keys were replaced, often because the server's operating system was reinstalled without backing up the old keys.  Another reason can be when the system administrator has phased out deprecated or compromised keys.  However that can be planned better and if there is time to plan the migration, new keys can just be added to the server and have the clients use the '''UpdateHostKeys''' option so that the new keys are accepted if the old keys match.  A third situation is when the connection is made to the wrong machine, such as when the remote system changes IP addresses because of dynamic address allocation.  

In all three cases where the key has changed there is only one thing to do: contact the system administrator and verify the key.   Ask if the OpenSSH-server was recently reinstalled, or was the machine restored from an old backup?  Keep in mind that the system administrator may be you yourself in some cases. 

The case which is rather rare but serious enough that it should be ruled out for sure is that the wrong machine is part of a man-in-the-middle attack.

In all four cases, an authentic key fingerprint can be acquired by any method where it is possible to verify the integrity and origin of the message, for example via PGP-signed e-mail.  If physical access is possible, then use the console to get the right fingerprint.  Once the authentic key fingerprint is available, return to the client machine where you got the error and remove the old key from '''~/.ssh/known_hosts'''

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -R server.example.org
&lt;/syntaxhighlight&gt;

Then try logging in, but compare the key fingerprints first and proceed if and '''only''' if the key fingerprint matches what you received out of band.  If the key fingerprint matches, then go through with the login process and the key will be automatically added.  If the key fingerprint does not match, stop immediately and figure out what you are connecting to.  It would be a good idea to get on the phone, a real phone not a computer phone, to the remote machine's system administrator or the network administrator.

===Multiple Keys for a Host, Multiple Hosts for a Key in known_hosts===
 
Multiple host names or IP addresses can use the same key in the '''known_hosts''' file by using pattern matching or simply by listing multiple systems for the same key.  That can be done in either the global list of keys in '''/etc/ssh/ssh_known_hosts''' and the local, account-specific lists of keys in each account's '''~/.ssh/known_hosts''' file.  Labs, computational clusters, and similar pools of machines can make use of keys in that way.  Here is a key shared by three specific hosts, identified by name, one host per line:
&lt;pre&gt;
server1 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMIId09yQEh9634wNXR+y7L79th2M4awBgCwqWJobJuQ fred@desk.example.org
server2 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMIId09yQEh9634wNXR+y7L79th2M4awBgCwqWJobJuQ fred@desk.example.org
server3 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMIId09yQEh9634wNXR+y7L79th2M4awBgCwqWJobJuQ fred@desk.example.org
&lt;/pre&gt;
Or a range can be specified by using globbing to a limited extent in either '''/etc/ssh/ssh_known_hosts''' or '''~/.ssh/known_hosts'''.
&lt;pre&gt;
172.19.40.* ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMIId09yQEh9634wNXR+y7L79th2M4awBgCwqWJobJuQ fred@desk.example.org
&lt;/pre&gt;
Conversely, a pool of servers might have multiple keys for the same address.  In that case, it is necessary to make multiple entries in either '''/etc/ssh/ssh_known_hosts''' or '''~/.ssh/known_hosts''' for each key.
&lt;pre&gt;
server1 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMIId09yQEh9634wNXR+y7L79th2M4awBgCwqWJobJuQ fred@desk.example.org
server1 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIBrsIIaDl/bJ40vyprvF+HYAq+kE2jWUsOt+WqIheaBw fred@desk.example.org
server1 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIC2CgwWTPH/qZDeHmW7ZUea18wa9As7Txq3P5dXCfoXj fred@desk.example.org 
&lt;/pre&gt;
Thus in order to get a pool of servers to share a pool of keys, each server-key combination must be added manually to the '''known_hosts''' file:
&lt;pre&gt;
server1 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMIId09yQEh9634wNXR+y7L79th2M4awBgCwqWJobJuQ fred@desk.example.org
server1 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIBrsIIaDl/bJ40vyprvF+HYAq+kE2jWUsOt+WqIheaBw fred@desk.example.org
server1 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIC2CgwWTPH/qZDeHmW7ZUea18wa9As7Txq3P5dXCfoXj fred@desk.example.org 

server2 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAICPSs4OR2LT89mv2tM4TKqeVhh4XvoLQ77MSBmjyrMGm fred@desk.example.org
server2 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIHChTzAoJr53A7VP1BdMHqLTFK5cz/2Vc065+VcpP4VA fred@desk.example.org
server2 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIHP+4BvU4DzwYQgznARxx/qyBWmu49PAywHwDRgslRaM fred@desk.example.org
&lt;/pre&gt;

Though upgrading to certificates might be a more appropriate approach that manually updating lots of keys.

===Another way of Dealing with Dynamic (roaming) IP Addresses===
It is possible to manually point to the right key using '''HostKeyAlias''' either as part of [http://man.openbsd.org/ssh_config.5 ssh_config(5)]  or as a runtime parameter.  Here the key for machine ''Foobar'' is used to connect to host 192.168.11.15

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -o StrictHostKeyChecking=accept-new \
      -o HostKeyAlias=foobar   \
      192.168.11.15
&lt;/syntaxhighlight&gt;
This is useful when DHCP is not configured to try to keep the same addresses for the same machines over time or when using certain stdio forwarding methods to pass through intermediate hosts.

===Host Key Update and Rotation in known_hosts===

A protocol extension to rotate weak public keys out of '''known_hosts''' has been in OpenSSH from version 6.8&lt;ref name=&quot;djm_rotation&quot;&gt;
{{cite web
| title=Key rotation in OpenSSH 6.8+ 
| author=Damien Miller
| url=http://blog.djm.net.au/2015/02/key-rotation-in-openssh-68.html
| date=2015-02-01
| publisher=DJM's Personal Weblog
| accessdate=2016-03-05
}}
&lt;/ref&gt; and later.  With it the server is able to inform the client of all its host keys and update '''known_hosts''' with new ones when at least one trusted key already known.  This method still requires the private keys be available to the server &lt;ref name=&quot;djm_rotation_redux&quot;&gt;
{{cite web
| title=Hostkey rotation, redux 
| author=Damien Miller
| url=http://blog.djm.net.au/2015/02/hostkey-rotation-redux.html
| date=2015-02-17
| publisher=DJM's Personal Weblog
| accessdate=2016-03-05
}}
&lt;/ref&gt; so that proofs can be completed.  In [http://man.openbsd.org/ssh_config.5 ssh_config(5)], the directive '''UpdateHostKeys''' specifies whether the client should accept updates of additional host keys from the server after authentication is completed and add them to '''known_hosts'''.  A server can offer multiple keys of the same type for a period before removing the deprecated key from those offered, thus allowing an automated option for rotating keys as well as for upgrading from weaker algorithms to stronger ones.  See also [https://datatracker.ietf.org/doc/html/rfc4819 RFC 4819: Secure Shell Public Key Subsystem] about key management standards.

==Converting Between SSH Key Formats==

OpenSSH has its own format for keys which it uses by default when new keys are made.  However, other SSH clients and servers may use other formats such as [https://www.rfc-editor.org/rfc/rfc4716 RFC4716], [https://www.rfc-editor.org/rfc/rfc5958 PKCS8], or [https://www.rfc-editor.org/rfc/rfc1421 PEM].  Any of these can be converted to the default OpenSSH format by [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)].  The default to format to try to convert from is RFC4716.  The utility [https://linux.die.net/man/1/puttygen puttygen(1)] makes keys in that format for [https://linux.die.net/man/1/putty putty(1)] and they need conversion when used with OpenSSH's server.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -i -f /var/tmp/key_public.ppk
&lt;/syntaxhighlight&gt;

However, you can use the '''-m''' option to specify either that format explicitly or else choose another one to convert from.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -i -m RFC4716 -f /var/tmp/key_public.ppk
$ ssh-keygen -i -m PKCS8 -f /var/tmp/key_public.ppk
&lt;/syntaxhighlight&gt;

Both examples above are for importing public keys into OpenSSH's own format.  

By default OpenSSH will write newly-generated keys in its own format, so the '''-m''' option is obligatory to produce public keys in another format.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -e -m PKCS8 -f ~/.ssh/key.pub
&lt;/syntaxhighlight&gt;

It is not yet possible to export private keys from the OpenSSH format to one of the other formats using the '''-e''' option.  Even if a private key is specified as input, a public key is produced:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -e -m RFC4716 -f ~/.ssh/key
&lt;/syntaxhighlight&gt;

Not all key types are supported by all key formats.  

It is also possible to use export to display the key pair as a traditional hex dump.
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -e -m hexdump -f ~/.ssh/key
Enter passphrase for &quot;key&quot;: 
Public ED25519 key:
buffer len = 51
0000: 00 00 00 0b 73 73 68 2d 65 64 32 35 35 31 39 00  ....ssh-ed25519.
0016: 00 00 20 b0 c5 cc 2c cb d8 8b 8d 75 80 eb e6 e9  .. ...,....u....
0032: 2c f4 36 08 7b 5b ad ad 0b 54 4f 7f 21 9d 1b e8  ,.6.{[...TO.!...
0048: 9e e0 32                                         ..2

Private ED25519 key:
buffer len = 119
0000: 00 00 00 0b 73 73 68 2d 65 64 32 35 35 31 39 00  ....ssh-ed25519.
0016: 00 00 20 b0 c5 cc 2c cb d8 8b 8d 75 80 eb e6 e9  .. ...,....u....
0032: 2c f4 36 08 7b 5b ad ad 0b 54 4f 7f 21 9d 1b e8  ,.6.{[...TO.!...
0048: 9e e0 32 00 00 00 40 e1 c3 a2 4d d9 89 49 72 9b  ..2...@...M..Ir.
0064: 86 72 6c 07 17 1b 40 4f 62 50 62 45 4f 4c cf cf  .rl...@ObPbEOL..
0080: 57 8b 9d c0 04 8f 9b b0 c5 cc 2c cb d8 8b 8d 75  W.........,....u
0096: 80 eb e6 e9 2c f4 36 08 7b 5b ad ad 0b 54 4f 7f  ....,.6.{[...TO.
0112: 21 9d 1b e8 9e e0 32                             !.....2
&lt;/syntaxhighlight&gt;

&lt;noinclude&gt;

== References ==
{{reflist}}
{{OpenSSH/TOC|mini}}
&lt;/noinclude&gt;
{{BookCat}}
{{status|100%}}</text>
      <sha1>6pcvt51799ruz674v8dwfe5i3yyv0pg</sha1>
    </revision>
    <revision>
      <id>4675780</id>
      <parentid>4675779</parentid>
      <timestamp>2026-10-13T04:32:57Z</timestamp>
      <contributor>
        <username>Larsnooden</username>
        <id>430753</id>
      </contributor>
      <comment>convert alias to function in ephemeral agent example</comment>
      <origin>4675780</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="81888" sha1="mjiflb4q6snp69thbzcxfdr56gr7xzn" xml:space="preserve">&lt;noinclude&gt;{{simple chapter navigation|previous=File Transfer with SFTP|next=Certificate-based Authentication}}&lt;/noinclude&gt;
&amp;nbsp;

Authentication keys can improve efficiency, if done properly.  As a bonus advantage, the passphrase and private key never leave the client&lt;ref name=&quot;RFC4252§7&quot;&gt;{{cite web |url=https://tools.ietf.org/html/rfc4252#section-7 |title=The Secure Shell (SSH) Authentication Protocol |publisher=IETF |year=2006| accessdate=2015-05-06}}&lt;/ref&gt;.  Key-based authentication is generally recommended for outward facing systems so that password authentication can be turned off.  

==Key-based authentication==

OpenSSH can use public key cryptography for authentication.  In public key cryptography, encryption and decryption are asymmetric.  The keys are used in pairs, a public key to encrypt and a private key to decrypt.  The [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)] utility can make RSA, Ed25519, MLDSA44-Ed25519, ECDSA, Ed25519-SK, or ECDSA-SK keys for authenticating.  Even though DSA keys can still be made, being exactly 1024 bits in size, they are no longer recommended and should be avoided.  RSA keys are allowed to vary from 1024 bits on up.  The default is now 3072.  However, there is only limited benefit after 2048 bits and that makes elliptic curve algorithms preferable.  ECDSA can be 256, 384 or 521 bits in size.  Ed25519, Ed25519-SK, and ECDSA-SK keys each have a fixed length of 256 bits.  Shorter keys are faster, but less secure.  Longer keys are much slower to work with but provide better protection, up to a point.  

Keys can be named to help remember what they are for.  Because the key files can be named anything it is possible to have many keys each named for different services or tasks.  The comment field at the end of the public key can also be useful in helping to keep the keys sorted, if you have many of them or use them infrequently.  

The process of key-based authentication uses these keys to make a couple of exchanges using the keys to encrypt and decrypt some short message.  At the start, a copy of the client's public key is stored on the server and the client's private key is on the client, both stay where they are.  The private key never leaves the client.  As the client first contacts the server, the server responds by using the client's public key to encrypt a random number and return that encrypted random number as a challenge to the client.  The client responds to the challenge by using the matching private key to decrypt the message and extract the random number.  The client then makes an MD5 hash of the session ID along with the random number from the challenge and returns that hash to the server.  The server then makes its own hash of the session ID and the random number and compares that to the hash returned by the client.  If there is a match, the login is allowed.  If there is not a match, then the next of any public keys on the server registered as belonging to the same account is tried until either a match is found or all the keys have been tried or the maximum number of failures has been reached. &lt;ref name=&quot;How Key Challenges Work&quot;&gt;{{cite web | url=http://www.unixwiz.net/techtips/ssh-agent-forwarding.html#chal | title=An Illustrated Guide to SSH Agent Forwarding | author=Steve Friedl | date=2006-02-22 | accessdate=2013-04-27 | publisher=Unixwiz.net }}&lt;/ref&gt;

When an agent is used on the client side to manage authentication, the process is similar.  The difference is that [http://man.openbsd.org/ssh.1 ssh(1)] passes the challenge off to the agent which then calculates the response and passes it back to [http://man.openbsd.org/ssh.1 ssh(1)] which then passes the agent's response back to the server.  

===Basics of Public Key Authentication===

A matching pair of SSH keys, one public and one private, is needed for public key authentication.  The [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)] utility is used to make such a key pair.  Out of that pair the public key must be properly stored on the remote host before using key-based authentication.  The default location for it is the designated '''authorized_keys''' file, usually one such file resides inside each remote user account.  The private key stays stored safely on the client.  

Once the keys have been prepared and the remote account configured, they can be used for login.  Before starting, there must already be an account on the remote system.  The details of doing that are outside of the scope of this book.  However, once you have a remote account, there are four steps to set up key-based authentication for it:

'''1''') Prepare a directory on the client (say a laptop or a desktop) where the keys will stay, if there isn't one already.  For example, if the '''.ssh''' directory is not on the client machine, create it and set the permissions correctly.  It is important that it not be writable by any account except its owner:
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ mkdir ~/.ssh/
$ chmod 0700 ~/.ssh/
&lt;/syntaxhighlight&gt;

'''2''') Create a key pair inside the designated directory.  The example here creates an Ed25519 key pair in the directory '''~/.ssh'''.  The option '''-t''' decides the key type and the option '''-f''' assigns the key file a name.  It is good to give key files descriptive names, especially if larger numbers of keys are managed.  Below, the public key will be named '''fred_example_org_ed25519.pub''' and the private key will be called '''fred_example_org_ed25519'''.  Lastly, the '''-C''' option is used to embed a descriptive comment inside the private key itself.  The comment is useful for figuring out later what the key is for when one has many keys or a lot of time has passed or both.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -t ed25519 -f ~/.ssh/fred_example_org_ed25519 \
        -C &quot;from fred's laptop to server.example.org&quot;
&lt;/syntaxhighlight&gt;

Be sure to enter a solid passphrase so that the private key gets encrypted using 128-bit AES.  That way the private key can only be read or used when the passphrase is given.  

Ed25519, Ed25519-SK, and ECDSA-SK keys have fixed lengths.  For RSA and ECDSA keys, the '''-b''' option sets the number of bits used for those kinds of keys.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -o -b 4096 -t rsa -f ~/.ssh/fred_example_org_rsa \
        -C &quot;from fred's laptop to server.example.org&quot;
&lt;/syntaxhighlight&gt;

Since 6.5 a new private key format is available using a [http://man.openbsd.org/bcrypt.3 bcrypt(3)] key derivative function (KDF) to better protect keys at rest.  This new format is always used for Ed25519 keys, and sometime in the future will be the default for all keys.  But for right now it may be requested when generating or saving existing keys of other types via the '''-o''' option in [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)].  

Details of the new format are found in the source code in the file '''PROTOCOL.key'''.

'''3''') Get the keys to the right places.  Transfer only the public key to remote machine.  The following assume the default locations for the authorized keys as specified in the server's configuration file by the '''AuthorizedKeysFile''' directive.  

'''3a''') If the utility &lt;code&gt;ssh-copy-id&lt;/code&gt; exists, and if password authentication is allowed, then it can be used to put the public key into place on the remote system.  The ''.pub'' is optional here, the script will figure it out if omitted. 
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-copy-id -i ~/.ssh/fred_example_org_ed25519 fred@server.example.org
&lt;/syntaxhighlight&gt;

If that script was successful in transferring the public key, then go on to step 4 below and test the key.  If not, then try transferring the public key manually as described in step 3b next.

'''3b''') Or the public key can be put in place manually on the remote machine.  For that the remote '''.ssh''' directory is needed, and within that a special file to store the public keys, the default file name is '''authorized_keys'''.  If either the '''authorized_keys''' file or '''.ssh''' directory do not exist on the remote machine, they need to be created.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ mkdir -m 700 ~/.ssh/
$ touch ~/.ssh/authorized_keys
$ chmod 0600 ~/.ssh/authorized_keys
$ nano -w ~/.ssh/authorized_keys
&lt;/syntaxhighlight&gt;

Then any editor which does not wrap long lines can be used to add the public key.  However the '''authorized_keys''' file is edited to add the key, the key itself must be in the file whole and unbroken on a single  line.  For example, [http://linux.die.net/man/1/nano nano(1)] can be started with the '''-w''' option to prevent wrapping of long lines.  (Another way to set line wrapping permanently in [http://linux.die.net/man/1/nano nano(1)] is by editing [http://linux.die.net/man/5/nanorc nanorc(5)].)  

If the key pair is not already on the client, transfer both the public and private keys there.  It is usually best to keep both the public and private keys together in the directory '''~/.ssh/''', though the public key is not always needed on the client after this step and could even be regenerated if it is ever needed again.  

'''4''') Test the keys

While remaining logged in via the first terminal, use the client system to open another window and in it start another SSH session and try authenticating to the remote machine from the client using the private key.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -i ~/.ssh/fred_example_org_ed25519 -l fred server.example.org
&lt;/syntaxhighlight&gt;

The option '''-i''' tells [http://man.openbsd.org/ssh.1 ssh(1)] which private key to try.  
Only after verifying that the key-based authentication works should you close the original window.  

It is possible to make permanent shortcuts on the client using [http://man.openbsd.org/ssh_config.5 ssh_config(5)], explained further below, once key-based authentication is working.  In particular, see the '''IdentityFile''',  '''IdentitiesOnly''', and '''AddKeysToAgent''' configuration directives, to name three.  

It is also a good idea to turn off password authentication, if and only if key-based authentication is setup for all the necessary remote accounts.  

➥ '''Troubleshooting of Key-based Authentication''':

If the server refuses to accept the key and fails over to the next authentication method (e.g.: &quot;Server refused our key&quot;), then there are several possible mistakes to look for on the server side.  

One of the most common errors is that the file and directory permissions are wrong.  The authorized keys file must be owned by the user in question and not be group writable.  Nor may the key file's directory be group or world writable.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ chmod u=rwx,g=rx,o= ~/.ssh
$ chmod u=rw,g=,o=  ~/.ssh/authorized_keys 
&lt;/syntaxhighlight&gt;

Another mistake that can happen is if the key inside the '''authorized_keys''' file on the remote host is broken by line breaks or has other whitespace in the middle.  That can be fixed by joining up the lines and removing the spaces or by recopying the key more carefully.  

And, though it should go without saying, the halves of the key pair need to match.  The public key on the server needs to match the private key held on the client.  If the public key is lost, then a new one can be generated with the '''-y''' option, but not the other way around.  If the private key is lost, then the public key should be erased as it is no longer of any use.  If many keys are in use for an account, it might be a good idea to add comments to them.  On the client, it can be a good idea to know which server the key is for, either through the file name itself or through the comment field.  A comment can be added using the '''-C''' option.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -t ed25519 -f ~/.ssh/fred_example_org_ed25519 -C &quot;web server mirror&quot;
&lt;/syntaxhighlight&gt;

On the server, it can be important to annotate which client they key is from if there is more than one public key there in an account.  There the comment can be added to the authorized keys file on the server in the last column if a comment does not already exist.  Again, the format of the authorized keys file is given in the manual page for [http://man.openbsd.org/sshd.8 sshd(8)] in the section &quot;AUTHORIZED_KEYS FILE FORMAT&quot;.  If the keys are not labeled they can be hard to match, which might or might not be what you want.  

====Associating Keys Permanently with a Server====

A key can be specified at run time, but to save retyping the same paths again and again, the '''Host''' directive in [http://man.openbsd.org/ssh_config.5 ssh_config(5)] can apply specific settings to a target host.  In this case, by changing '''~/.ssh/config''' it is possible to assign particular keys to be tried automatically whenever making a connection to that specific host.  After adding the following lines to '''~/.ssh/config''', all that's needed is to type &lt;code&gt;ssh ''web1''&lt;/code&gt; to connect with the key for that server.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Host web1
	Hostname 198.51.100.32
	IdentitiesOnly yes
	IdentityFile /home/fred/.ssh/web_key_ed25519
&lt;/syntaxhighlight&gt;

The '''~/.ssh/config''' below uses different keys for ''server'' versus ''server.example.org'',  regardless whether they resolve to the same machine.   This is possible because the host name argument given to [http://man.openbsd.org/ssh.1 ssh(1)] is not converted to a canonicalized host name before matching.

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Host server
	IdentitiesOnly yes
	IdentityFile /home/fred/.ssh/key_a_ed25519

Host server.example.org
	IdentitiesOnly yes
	IdentityFile /home/fred/.ssh/key_b_ed25519
&lt;/syntaxhighlight&gt;

In this example the shorter name is tried first, but of course less ambiguous shortcuts can be made instead.  The configuration file gets parsed on a first-match basis.  So the most specific rules go at the beginning and the most general rules go at the end.  

====Encrypted Home Directories====

When using encrypted home directories the keys must be stored in an unencrypted directory.  That means somewhere outside the actual home directory which means [http://man.openbsd.org/sshd.8 sshd(8)] needs to be configured appropriately to find the keys in that special location.  

Here is one method for solving the access problem.  Each user is given a subdirectory under '''/etc/ssh/keys/''' which they can then use for storing their '''authorized_keys''' file.  This is set in the server's configuration file '''/etc/ssh/sshd_config'''

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
AuthorizedKeysFile      /etc/ssh/keys/%u/authorized_keys
&lt;/syntaxhighlight&gt;

Setting a special location for the keys opens up more possibilities as to how the keys can be managed and multiple key file locations can be specified if they are separated by whitespace.  The user does not have to have write permissions for the '''authorized_keys''' file.  Only read permission is needed to be able to log in.  But if the user is allowed to add, remove, or change their keys, then they will need write access to the file to do that.  

One symptom of having an encrypted home directory is that key-based authentication only works when you are already logged into the same account, but fails when trying to make the first connection and log in for the first time.

Sometimes it is also necessary to add a script or call a program from '''/etc/ssh/sshrc''' immediately after authentication to decrypt the home directory.

====Passwordless Login====

One solution for passwordless logins is to still have a passphrase and work with an authentication agent in conjunction with a single-purpose key.  Most desktop environments launch an SSH agent automatically these days.  It will be visible in the '''SSH_AUTH_SOCK''' environment variable if it is.  On accounts with an agent, [http://man.openbsd.org/ssh-add.1 ssh-add(1)] can load private keys into an available agent.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-add ~/.ssh/fred_example_org_ed25519
&lt;/syntaxhighlight&gt;

Thereafter, the client will automatically check the agent for the key when appropriate.  If there are many keys in the agent, it will become necessary to set '''IdentitiesOnly'''.  See the above section on using '''~/.ssh/config''' for that.  See [[OpenSSH/Cookbook/Public_Key_Authentication#Key-based_Authentication_Using_an_Agent|Key-based Authentication Using an Agent]] below.  

Another, riskier, way of allowing passwordless logins is to follow the steps above, but simply do not enter a passphrase when asked for one while creating the key.  Note that using keys that lack a passphrase is very risky, so the key files should be very well protected and kept track of, and ideally locked down with a '''command=''' option or '''ForceCommand''' directive on the server.  That includes those keys which will only be used as single-purpose keys as described below.  

Timely key rotation becomes especially important.  In general, it is not a good idea to make a key without a passphrase.

====Requiring Both Keys and a Password====

While users should have strong passphrases for their keys, there is no way to enforce or verify that.  Indeed, since neither the private key nor its the passphrase ever leave the client machine there is nothing that the server can do to have any influence over that.  Instead, it is possible to require both a key and a password.  Starting with OpenSSH 6.2, it is possible for the server to require multiple authentication methods for login using the '''AuthenticationMethods''' directive.   
&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
AuthenticationMethods publickey,password
&lt;/syntaxhighlight&gt;

This example from [http://man.openbsd.org/sshd_config.5 sshd_config(5)] requires that users first authenticate using a key and it only queries for a password if the key succeeds.  Thus with that configuration it is not possible to get to the system password prompt without first authenticating with a valid key.  Changing the order of the arguments changes the order of the authentication methods.

====Requiring Two or More Keys====

Since OpenSSH 6.8, the server now remembers which public keys have been used for authentication and refuses to accept previously-used keys.  This allows a set up requiring that users authenticate using two different public keys, maybe one in the file system and the other in a hardware token. 

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
AuthenticationMethods publickey,publickey
&lt;/syntaxhighlight&gt;

The '''AuthenticationMethods''' directive, whether for keys or passwords, can also be set on the server under a '''Match''' directive to apply only to certain groups or situations.

====Requiring Certain Key Types For Authentication====

Also since OpenSSH 6.8, the '''PubkeyAcceptedKeyTypes''' directive, later changed to '''PubkeyAcceptedAlgorithms''', can specify which key algorithms are accepted for authentication.  Those not in the comma-separated pattern list are not allowed.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
PubkeyAcceptedAlgorithms ssh-ed25519*,ssh-rsa*,ecdsa-sha2*,sk-ssh-ed25519*,sk-ecdsa-sha2*
&lt;/syntaxhighlight&gt;

Either the actual key types or a pattern can be in the list.  Spaces are not allowed in the pattern list.  The exact list of key types supported for authentication can be found by the '''-Q''' option using the client.  The following two lines are equivalent.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -Q key-sig | sort

$ ssh -Q PubkeyAcceptedAlgorithms | sort
&lt;/syntaxhighlight&gt;

For host-based authentication, it is the '''HostbasedAcceptedAlgorithms''' directive which determines the key types which are allowed for authentication.

===Key-based Authentication Using the AuthorizedKeysCommand Directive===

It is possible to use a program or script to look up public keys rather than keeping them in a static file or files.  Any command called by the '''AuthorizedKeysCommand''' directive needs to either produce a syntactically correct public key while returning the exit code for a successful run or else return the exit code for failure.  The string sent to '''stdout''' will then be processed as part of the authentication work flow.  

Here is a shell script&lt;ref name=&quot;janpietmens&quot;&gt;{{cite web |url=https://jpmens.net/2025/03/25/authorizedkeyscommand-in-sshd/ |title=SSH keys from a command: sshd's AuthorizedKeysCommand directive |accessdate=2025-04-04 |date=2025-03-25 | author=Jan-Piet Mens }}&lt;/ref&gt; at its simplest, without constraints, demonstrating a public key lookup:

&lt;syntaxhighlight lang=&quot;shell&quot;&gt;
#!/bin/sh

echo &quot;ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIKs/UouletvojgB1YeRZ4MY6iRblQ2ERDuNhQO4tOvdL&quot;

exit 0
&lt;/syntaxhighlight&gt;

For authentication to succeed, the script must return exit code 0  (success) after sending the syntactically correct matching public key to '''stdout'''.  For the SSH daemon to even run the script in the first place, the script must have the correct file and directory permissions.

Both the '''AuthorizedKeysCommandUser''' directive and '''AuthorizedKeysCommand''' must be used together.  The former designates which account the script or program use when run.  If set to ''none'' or if it does not refer to a valid account then [http://man.openbsd.org/sshd sshd(8)] will just ignore the command.  If '''AuthorizedKeysCommand''' is set, and '''AuthorizedKeysCommandUser''' is left empty or missing, then [http://man.openbsd.org/sshd sshd(8)] won't even run when invoked.  The error will be:

&lt;syntaxhighlight lang=&quot;text&quot;&gt;
AuthorizedKeysCommand set without AuthorizedKeysCommandUser
&lt;/syntaxhighlight&gt;

The '''AuthorizedKeysFile''' is always tried first when it is present in the server configuration.  The '''AuthorizedKeysCommand''' directive will not even be tried when the authorized keys file can provide a relevant key first.  

====A More Detailed Example Using the AuthorizedKeysCommand Directive====

By default the user name trying to log in is passed to the script when no tokens or arguments are provided.  Whether or how that information is used is up to the script.  The SSH daemon can also pass any combination of the tokens described in the TOKENS section of [http://man.openbsd.org/sshd_config sshd_config(5)] into the program or script being called.  Furthermore, the program or script can even be a front end for a database, such as OpenLDAP, or any similar system, as long as '''stdout''' produces a public key.  

Below is a more detailed example which uses a local script named '''keyfinder''' run with the account '''keys''' to look up the a public key for certain accounts.  First in [http://man.openbsd.org/sshd_config sshd_config(5)] the two directives:

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
AuthorizedKeysCommand /usr/local/sbin/keyfinder %U
AuthorizedKeysCommandUser keys
&lt;/syntaxhighlight&gt;

The script below is only a demonstration and a more complex program can call databases or do advanced lookups or heuristics:  

&lt;syntaxhighlight lang=&quot;shell&quot;&gt;
#!/bin/sh

set -e

case $1 in
        &quot;1000&quot;)
                echo &quot;ssh-ed25519 AAAAC3NzaC1lZDIE5AAAAIK89...UT9hz&quot;
                ;;

        &quot;1001&quot;)
                echo &quot;restrict ssh-ed25519 AAAAC3NzaC1lZDI1NTAAIBvGx...Y0zxV&quot;
                ;;

        &quot;1002&quot;)
                echo &quot;command=\&quot;/usr/libexec/sftp-server\&quot; ssh-ed25519 AAAAC3NzaC1lZDI1TE5AIPSyY...cPTg3&quot;
                ;;

        *)
                exit 1
                ;;
   
esac

exit 0
&lt;/syntaxhighlight&gt;

The '''AuthorizedKeysCommand''' scripts or programs can return any correctly formatted public key to '''stdout''' for consideration in the authentication process.  That includes adding constraints to the keys.  Above, the account with the UID 1000 has no constraints, while the account with UID 1001 is quite constrained.  Finally, the account with the UID 1002 can only access the SFTP service.  See the section &quot;AUTHORIZED_KEYS FILE FORMAT&quot; in [http://man.openbsd.org/sshd sshd(8)] for the full set of possibilities.

===Key-based Authentication Using an Agent===

When an authentication agent, such as [http://man.openbsd.org/ssh-agent.1 ssh-agent(1)], is going to be used, it should generally be started at the beginning of a session and used to launch the login session or X-session so that the environment variables pointing to the agent and its UNIX-domain socket are passed to each subsequent shell and process.  Many desktop distros do this automatically upon login or startup.  

Starting an agent entails setting a pair of environment variables:

* SSH_AGENT_PID : the process id of the agent
* SSH_AUTH_SOCK : the filename and full path to the UNIX-domain socket

The various SSH and SFTP clients find these variables automatically and use them to contact the agent and try when authentication is needed.   However, it is mainly SSH_AUTH_SOCK which is ever used.  If the shell or desktop session was launched using [http://man.openbsd.org/ssh-agent.1 ssh-agent(1)], then these variables are already set and available.  If they are not available, then it is necessary to either set the variables manually inside each shell or for each application in order to use the agent or else to point to the agent's socket using the directive '''IdentityAgent''' in the client's configuration file.  

Once an agent is available, a relevant private key needs to be loaded before the agent can be used.  Once in the agent the private key can then be used many times.  Private keys are loaded into an agent with [http://man.openbsd.org/ssh-add.1 ssh-add(1)].
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-add /home/fred/.ssh/mykey_ed25519
Identity added: /home/fred/.ssh/mykey_ed25519 (/home/fred/.ssh/mykey_ed25519)
&lt;/syntaxhighlight&gt;

Keys stay in the agent for as long as it is running unless specified otherwise.  A timeout can be set either with the '''-t''' option when starting the agent itself or when actually loading the key using [http://man.openbsd.org/ssh-add.1 ssh-add(1)].  In either case, the '''-t''' option will set a timeout interval, after which the key will be purged from the agent.
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-add -t 1h30m /home/fred/.ssh/mykey_ed25519
Identity added: /home/fred/.ssh/mykey_ed25519 (/home/fred/.ssh/mykey_ed25519)
Lifetime set to 5400 seconds
&lt;/syntaxhighlight&gt;

The option '''-l''' will list the fingerprints of all of the identities in the agent.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-add -l                                    
256 SHA256:77mfUupj364g1WQ+O8NM1ELj0G1QRx/pHtvzvDvDlOk mykey for task x (ED25519)
3072 SHA256:7unq90B/XjrRbucm/fqTOJu0I1vPygVkN9FgzsJdXbk myotherkey rsa for task y (RSA)
&lt;/syntaxhighlight&gt;

It is also possible to remove individual identities from the agent using '''-d''' which will remove them one at a time if identified by file name, but only if the file name is given and without the file name of the private key to be remove, '''-d''' will fail silently.  Using '''-D''' instead will remove all of them at once without needing to specify any by name.  

By default [http://man.openbsd.org/ssh-add.1 ssh-add(1)] uses the agent connected via the socket named in the environment variable '''SSH_AUTH_SOCK''', if it is set.  Currently, that is its only option.  However, for [http://man.openbsd.org/ssh.1 ssh(1)] an alternative to using the environment variable is the client configuration directive '''IdentityAgent''' which tells the SSH clients which socket to use to communicate with the agent.  If both the environment variable and the configuration directive are available at the same time, then the value in '''IdentityAgent''' takes precedence over what's in the environment variable.  '''IdentityAgent''' can also be set to ''none'' to prevent the connection from trying to use any agent at all.  

The client configuration directive '''AddKeysToAgent''' can also be useful in getting keys into an agent as needed.  When set, it automatically loads a key into a running agent the first time the key is called for if it is not already loaded.  Likewise the '''IdentitiesOnly''' directive can ensure that the relevant key is offered on the first try.  Rather than typing these out whenever the client is run, they can be added to '''~/.ssh/config''' and thereby added automatically for designated host connections.  

====Agent Forwarding====

Agent forwarding is one means of passing through one or more intermediate hosts.  However, the '''-J''' option for '''ProxyJump''' would be a safer option.  See [[OpenSSH/Cookbook/Proxies_and_Jump_Hosts#Jump_Hosts_--_Passing_Through_a_Gateway_or_Two | Passing Through a Gateway or Two]] in the section on jump hosts about that.  With agent forwarding, intermediate machines forward challenges and responses back and forth between the client and the final destination.  This comes with some risks but eliminates the need for using passwords or holding keys on any of these intermediate machines.  

A main advantage of agent forwarding is that the private key itself is not needed on any remote machine, thus hindering unwanted file system access to it. &lt;ref name=&quot;OpenSSH key management, Part 3&quot;&gt;{{cite web | url=http://www.ibm.com/developerworks/library/l-keyc3/ | title=Common threads: OpenSSH key management, Part 3 | author=Daniel Robbins | publisher=IBM | date=2002-02-01 | accessdate=2013-04-27}}&lt;/ref&gt;  Another advantage is that the actual agent to which the user has authenticated does not go anywhere and is thus less susceptible to analysis.  

One risk with agents is that they can be re-used to tailgate in if the permissions allow it.  Keys cannot be copied this way, but authentication is possible when there are incorrect permissions.  Note that disabling agent forwarding does not improve security unless users are also denied shell access, as they can always install their own forwarders.

The risks of agent forwarding can be mitigated by confirming each use of a key by adding the '''-c''' option when adding the key to the agent.  This requires the SSH_ASKPASS variable be set and available to the agent process, but will generate a prompt on the host running the agent upon each use of the key by a remote system.  So if passing through one or more intermediate hosts, it is usually better to instead have the SSH client use stdio forwarding with '''-W''' or '''-J'''.

On the client side agent forwarding is disabled by default and so if it is to be used it must be enabled explicitly.  Put the following line in  [http://man.openbsd.org/ssh_config.5 ssh_config(5)] to enable agent forwarding for a particular server:
&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
        Host gateway.example.org
        ForwardAgent yes
&lt;/syntaxhighlight&gt;

On the server side the default configuration files allow authentication agent forwarding, so to use it, nothing needs to be done there, just on the client side.  However, again, it would be preferable to take a look at '''ProxyJump''' instead.  

=====Old Style, Somewhat Safer SSH Agent Forwarding=====

The best way to pass through one or more intermediate hosts is to use the '''ProxyJump''' option instead of authentication agent forwarding and thereby not risk exposing any private keys.  If authentication agent forwarding must be used, then it would be advisable in the interest of following the principle of least privilege to forward an agent containing the minimum necessary number of keys.  There are several ways to solve that.  

In version 8.8 and earlier a partial solution is to make a one-off, ephemeral agent to hold just the one key or keys needed for the task at hand.  Another partial solution would be to set up a user-accessible service at the operating system level and then use [http://man.openbsd.org/ssh_config.5 ssh_config] for the rest.  

Automatically launching an ephemeral agent unique to each session can be done by crafting either a special shell alias or function to launch a single-use agent.  Either the function or the alias can be written to require confirmation for each requested signature.  The following example is a function is inspired by an updated blog post by Vincent Bernat&lt;ref name=&quot;safer-agent-forwarding&quot;&gt;{{cite web |url=https://vincent.bernat.ch/en/blog/2020-safer-ssh-agent-forwarding |title=Safer SSH agent forwarding |author=Vincent Bernat|date=2020-04-05 |accessdate=2020-10-04}}&lt;/ref&gt; on SSH agent forwarding:
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ agentssh() {
        ssh-agent ssh -o AddKeysToAgent=confirm -o ForwardAgent=yes&quot;
}
&lt;/syntaxhighlight&gt;

Note the use of [http://man.openbsd.org/ssh-agent.1 ssh-agent(1)].  When invoking that alias, the SSH client will be launched with a unique, ephemeral supporting key agent.  The alias sets up a new agent, including setting the two environment variables, and then sets two client options while calling the client.  This arrangement still checks with [http://man.openbsd.org/ssh_config.5 ssh_config(5)] for other options and settings.  When the SSH session is finished the agent which launched it ends and goes away, thus cleaning up after itself automatically.  

Another way is to rely on the client's configuration file for some of the settings.  Such methods rely mostly on [http://man.openbsd.org/ssh_config.5 ssh_config(5)] but still require an independent method to launch an ephemeral agent because the OpenSSH client is already running by the time it reads the configuration file and is thus not affected by any changes to environment variables caused by the configuration file and it is through the environment variables that contain information about the agent.  However, when the path to the UNIX-domain socket used to communicate with the authentication agent is decided in advance then the '''IdentityAgent''' option can point to it once the one-off agent&lt;ref name=&quot;wikimedia_ssh_agents&quot;&gt;{{cite web |url=https://wikitech.wikimedia.org/wiki/Managing_multiple_SSH_agents#Linux_solutions |title=Managing multiple SSH agents |publisher=Wikimedia|accessdate=2020-04-07}}&lt;/ref&gt; is actually launched.  The following uses a specific agent's pre-defined socket whenever connecting to either of two particular domains:

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Host *.wikimedia.org *.wmflabs.org
        User fred
        IdentitiesOnly yes
        IdentityFile %d/.ssh/id_cloud_01
        IdentityAgent /run/user/%i/ssh-cloud-01.socket
        ForwardAgent yes
        AddKeysToAgent yes
&lt;/syntaxhighlight&gt;

The '''%d''' stands for the path to the home directory and the '''%i''' stands for the user id (UID) for the current account.  In some cases the '''%i''' token might also come in handy when setting the '''IdentityAgent''' option inside the configuration file.  Again, be careful when forwarding agents with which keys are in the forwarded agent.  See the section &quot;TOKENS&quot; in [http://man.openbsd.org/ssh_config.5 ssh_config(5)] for more such abbreviations.  

With those configuration settings, the authentication agent must already be up and running and point to the designated socket prior to starting the SSH client for that configuration to work.  Additionally, it should place the socket in a directory which is inaccessible to any other accounts.  [http://man.openbsd.org/ssh-agent.1 ssh-agent(1)] must use the '''-a''' option to name the socket:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-agent -a /run/user/${UID}/ssh-cloud-01.socket
&lt;/syntaxhighlight&gt;

That agent configuration can be launched manually or via a script or service manager.  However, in the interests of privacy and security in general, agent forwarding is to be avoided.  The configuration directive '''ProxyJump''' is the best alternative and, on older systems, host traversal using '''ProxyCommand''' with [http://man.openbsd.org/nc.1 netcat] are preferable.  Again, see the section on [[OpenSSH/Cookbook/Proxies and Jump Hosts|Proxies and Jump Hosts]] for how those methods are used.

=====New Style SSH Agent Destination Constraints=====

From 8.9 onward, [http://man.openbsd.org/ssh-agent.1 ssh-agent(1)] will allow the agent to limit which hosts they will use for authentication as specified by [http://man.openbsd.org/ssh-add.1 ssh-add(1)] using the '''-h''' option.  These constraints have been added through two agent protocol extensions and a modification to the public key authentication protocol.  This feature may evolve, but for now the result is such that keys for account authentication can be loaded into the agent in four ways:

* no limits on forwarding (not recommended)
* local use only, these will not get forwarded
* forwarding, but only to specific remote hosts
* forwarding to specific remote hosts via specified routes

The intent is that the restrictions fail safely so that they do not allow authentication when one or more hosts in the route lack the needed protocol features.  The destinations and routes cannot be modified once the keys are loaded, but multiple routes to the same destination can be loaded and the routes can be any number of hops.  If the routes need changing, then the key must be reloaded into the agent with the new route or routes.  

The general default for the client is to keep keys in the agent for local use only.  However, that can be enforced explicitly by adding the '''-a''' option when starting the client or else setting the '''ForwardAgent''' directive in [http://man.openbsd.org/ssh_config.5 ssh_config(5)] to 'no' in the relevant configuration block.  

In order to load keys for unlimited forwarding, which is not the best idea, just add them using [http://man.openbsd.org/ssh-add.1 ssh-add(1)] as normal.  Then use the '''-A''' option with the client or set the '''ForwardAgent''' directive in [http://man.openbsd.org/ssh_config.5 ssh_config(5)] to 'yes' in the relevant configuration block.  

In order to limit keys for connection only to a specific remote host, or to load keys for connection to a specific remote host with forwarding via one or more intermediate hosts, use the '''-h''' option when loading keys into the agent.  Here the one key may be used only to connect to the specific destination:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-agent -h server.example.org server.key.ed25519
&lt;/syntaxhighlight&gt;

If an intermediate system is passed through, the best way is to use '''ProxyJump''' which is the '''-J''' option for the SSH Client.  If agent forwarding must be allowed then the tightest way is to constrain which systems may use the keys, again using the '''-h''' option.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-agent -h middle.example.org -h &quot;middle.example.org&gt;server.example.org&quot; server.key.ed25519
&lt;/syntaxhighlight&gt;

Multiple steps can be included, even multiple routes.  They just have to be enumerated explicitly, though patterns may still be used for the destination hosts as well as specific names.  Each host in the chain must support these protocol extensions for the connection to complete.  

Any keys designated for forwarding are unusable for authentication on any other hosts than those which have been explicitly identified for forwarding.  These permitted hosts are identified by host key or host certificate from the '''known_hosts''' file or another file designated by the '''-H''' option when loading the key with [http://man.openbsd.org/ssh-add.1 ssh-add(1)].  If '''-H''' is not used at the time the keys are loaded into the agent, then the default known hosts file(s) will be used: '''~/.ssh/known_hosts''', '''/etc/ssh/ssh_known_hosts''', '''~/.ssh/known_hosts2''', and '''/etc/ssh/ssh_known_hosts2'''.

In the case of keys, the '''known_hosts''' list must be maintained conscientiously &lt;ref name=&quot;ssh-agent-restrictions&quot;&gt;{{ cite web | author=Damien Miller|url=https://www.openssh.org/agent-restrict.html | title=SSH agent restriction | publisher=OpenSSH | date=2021-12-16|accessdate=2022-03-06}}&lt;/ref&gt;, perhaps with the help of the '''UpdateHostkeys''' and '''CanonicalizeHostname''' client configuration directives.  Use of certificates requires the agent to only need to be aware of the Certificate Authority (CA).

Again, see [[OpenSSH/Cookbook/Proxies_and_Jump_Hosts#Jump_Hosts_--_Passing_Through_a_Gateway_or_Two | Passing Through a Gateway or Two]] in the section on jump hosts about a way to pass through one or more intermediate machines without needing to forward an SSH agent.

====Checking the Agent for Specific Keys====

The [http://man.openbsd.org/ssh_add ssh_add(1)] utility's '''-T''' option can test whether a specific private key is available in the agent or not by looking up the matching public key.  That can be useful in a shell script.

&lt;syntaxhighlight lang=&quot;shell&quot;&gt;
#!/bin/sh

key=/home/fred/.ssh/some.key.ed25519.pub

if ssh-add -T ${key}; then
        echo &quot;Key ${key} Found&quot;
else
        echo &quot;Key ${key} missing&quot;
fi
&lt;/syntaxhighlight&gt;

Or it could be done with an alternate syntax just as well either in a script or in an interactive shell sessions,

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ key=/home/fred/.ssh/some.key.ed25519.pub
$ ssh-add -T ${key} &amp;&amp; echo &quot;Key found&quot; || echo &quot;Key missing&quot;
&lt;/syntaxhighlight&gt;

However, if the desired result would be to add key to the agent then the '''AddKeysToAgent''' client configuration option can ensure that a specific key is added to the SSH agent upon first use during any given login session.  That can be done using '''-o AddKeysToAgent=yes''' as a run-time argument, or by modifying [http://man.openbsd.org/ssh_config ssh_config(5)] as appropriate:

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Host www
        HostName www.example.com
        IdentityFile %d/.ssh/www.ed25519
        IdentitiesOnly yes
        AddKeysToAgent yes
&lt;/syntaxhighlight&gt;

With those options in the configuration file, the first time &lt;code&gt;ssh www&lt;/code&gt; is run the specified key will get added to the agent and remain available.

===Key-based Authentication Using A Hardware Security Token===

While stand-alone keys have been around for a long time, it has been possible since version 8.2 to use keys backed by hardware security tokens, such as OnlyKey, Yubikey, or many others, though the FIDO2 protocol.  The Universal 2nd Factor (U2F) authentication is supported directly in OpenSSH through FIDO2 and does not need third party software.  At the moment there are two types of hardware backed keys, ECDSA-SK and Ed25519-SK, but only the latest hardware tokens support the latter.  If the key Ed25519-SK format is not supported by the token's firmware, then the following error message will be presented when attempts to use that key type are made:

&lt;syntaxhighlight lang=&quot;text&quot;&gt;
Key enrollment failed: invalid format
&lt;/syntaxhighlight&gt; 

If supported, either key type can be created with [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)].  The steps are almost identical to creating normal keys but the token must be available to the system (plugged in) first.  Then if called for, the token's PIN must be entered and the token touched or otherwise activated.  After that, the key creation proceeds as normal.  Mind the key type as specified by the '''-t''' option.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -t ed25519-sk -f /home/fred/.ssh/server.ed25519-sk -C &quot;web server for fred&quot;
Generating public/private ed25519-sk key pair.
You may need to touch your authenticator to authorize key generation.
Enter passphrase (empty for no passphrase): 
Enter same passphrase again: 
Your identification has been saved in /home/fred/.ssh/server.ed25519-sk
Your public key has been saved in /home/fred/.ssh/server.ed25519-sk.pub
The key fingerprint is:
SHA256:41wVVDnKJ9gKr2Sj4CFuYMhcNvYebZ6zq0PWyP4rRDo web server
The key's randomart image is:
+[ED25519-SK 256]-+
|           .o... |
|             .o  |
|           +.. . |
|   = .  . ..= .  |
|+ + * + So.. o   |
|o+.EoO *+oo      |
|.o oBo+++o       |
|  o .=.+.        |
| .   .===        |
+----[SHA256]-----+
&lt;/syntaxhighlight&gt;

Once created, the public and private key files get handled like with any other type of key.  But when authenticating, the hardware token must be present and activated when called for.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -i /home/fred/.ssh/server.ed25519-sk server.example.org
Enter passphrase for key '/home/fred/.ssh/server.ed25519-sk': 
Confirm user presence for key ED25519-SK SHA256:41wVVDnKJ9gKr2Sj4CFuYMhcNvYebZ6zq0PWyP4rRDo
&lt;/syntaxhighlight&gt;

The resulting private key file is not actually the key itself but instead a &quot;key handle&quot; which is used by the hardware security token to derive the real private key on demand at the time it is actually used&lt;ref name=&quot;OpenBSD_tech_U2F_FIDO&quot;&gt;{{cite web |url=https://marc.info/?l=openbsd-tech&amp;m=157376801917387&amp;w=2 |title=OpenSSH U2F/FIDO support in base 
|publisher=OpenBSD-Tech Mailing List | date=2019-11-14
|accessdate=2021-03-24}}&lt;/ref&gt;.  As a result, the hardware-backed private key file is useless without the accompanying hardware token.  This also means that these key files are not portable across hardware tokens, say when having multiple tokens in reserve or as backup, even when used by the same account.  So when multiple hardware tokens are in use, different key pairs must be generated for each token.

====Hardware Security Token Resident Private Key====

It is possible to store the private key within the token itself, but for the moment it cannot be used directly from inside the token and must first be saved as a file.  Also, the key can only be loaded into the FIDO authenticator at the time of creation  using the '''-O resident''' option with [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)].  Otherwise, the process is the same as above.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -O resident -t ed25519-sk -f /home/fred/.ssh/server.ed25519-sk -C &quot;web server for fred&quot;
. . .
&lt;/syntaxhighlight&gt;

When needed, the resident key can be extracted from the FIDO2 hardware token and saved into a file using the '''-K''' option.  At this stage a passphrase can be added to the file, but no passphrase is kept within the token itself, only an optional PIN protects the key there.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -K
Enter PIN for authenticator: 
Enter passphrase (empty for no passphrase): 
Enter same passphrase again: 
Saved ED25519-SK key to id_ed25519_sk_rk

$ mv -i id_ed25519_sk_rk /home/fred/.ssh/server.ed25519-sk
&lt;/syntaxhighlight&gt;

Since the output file name is fixed, any pre-existing file with that name can get overwritten but there will be a warning first.  However, it is not recommended to keep the key on the hardware token because it provides more protection when kept separately.

==Single-purpose Keys==

Tailored single-purpose keys can eliminate use of remote root logins for many administrative activities.  A  finely tailored '''sudoers''' is needed along with an unprivileged account.  When done right, it gives just enough access to get the job done, following the security principle of Least Privilege.  

Single-purpose keys are accompanied by use of either the '''ForceCommand''' directive in [http://man.openbsd.org/ssh_config.5 sshd_config(5)] or the '''command=&quot;...&quot;''' directive inside the '''authorized_keys''' file.  The method is to generate a new key pair, transfer the public key to '''authorized-keys''' on the remote system, and then prepend the appropriate command or script there to the line with the key.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ grep '^command' ~/.ssh/authorized_keys
command=&quot;/usr/local/bin/somescript.sh&quot; ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIEcgdzDvSebOEjuegEx4W1I/aA7MM3owHfMr9yg2WH8H
&lt;/syntaxhighlight&gt;

The '''command=&quot;...&quot;''' directive inserted there overrides everything else and ensures that when logging in with just that key only the script '''/usr/local/bin/somescript.sh''' is run.  If it is necessary to pass parameters to the script, have a look at the contents of the '''SSH_ORIGINAL_COMMAND''' environment variable and use it in a case statement.  Do not ever trust the contents of that variable nor use the contents directly, always indirectly.  

Single-purpose keys are useful for allowing only a tunnel and nothing more.  The following key will only echo some text and then exit, unless used non-interactively with the '''-N''' option.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ grep '^command' ~/.ssh/authorized_keys
command=&quot;/bin/echo do-not-send-commands&quot; ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIBzTIWCaILN3tHx5WW+PMVDc7DfPM9xYNY61JgFmBGrA 
&lt;/syntaxhighlight&gt; 

No matter what the user tries while logging in with that key, the session will only echo the given text and then exits.  Using the '''-N''' option disables running the remote program, allowing the connection to stay open, allowing a tunnel. 

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -L 3306:localhost:3306 \
	-i ~/.ssh/tunnel_ed25519 \
	-N \
	-l fred \
	server.example.com
&lt;/syntaxhighlight&gt;

That creates a tunnel and stays connected despite a key configuration which would close an interactive session.  See also the '''-n''' or '''-f''' option for [http://man.openbsd.org/ssh.1 ssh(1)].  

===Single-purpose Keys to Avoid Remote Root Access===

The easy way is to write a short shell script, place it '''/usr/local/bin/''', and then configure '''sudoers''' to allow the otherwise unprivileged account to run just that script and only that script.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
%wheel  ALL=(root:root) NOPASSWD: /usr/sbin/service httpd stop
%wheel  ALL=(root:root) NOPASSWD: /usr/sbin/service httpd start
&lt;/syntaxhighlight&gt;

Then the key calls the script using '''command=&quot;...&quot;''' inside '''authorized_keys'''.  Here the one key starts the web server, the other stops the web server.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ grep '^command' ~/.ssh/authorized_keys
command=&quot;/usr/bin/sudo /usr/sbin/service httpd stop&quot; ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIEcgdzDvSebOEjuegEx4W1I/aA7MM3owHfMr9yg2WH8H
command=&quot;/usr/bin/sudo /usr/sbin/service httpd start&quot; ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMidyqZ6OCvbWqA8Zn+FjhpYE6NoWSxVjFnFUk6MrNZ4
&lt;/syntaxhighlight&gt;

Complicated programs like [http://linux.die.net/man/1/rsync rsync(1)], [http://man.openbsd.org/tar.1 tar(1)], [http://linux.die.net/man/1/mysqldump mysqldump(1)], and so on require an advanced approach when building a single-purpose key.  For them, the '''-v''' option can show exactly what is being passed to the server so that '''sudoers''' can be set up correctly.  That way they can be restricted to only access designated parts of the file system.  For example, here is what &lt;code&gt;ssh -v&lt;/code&gt; shows from one particular usage of [http://linux.die.net/man/1/rsync rsync(1)], note the &quot;Sending command&quot; line:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ rsync -e 'ssh -v' fred@server.example.org:/etc/ ./backup/etc/
. . .
debug1: Sending command: rsync --server --sender -e.LsfxC . /etc/
. . .
&lt;/syntaxhighlight&gt;

That output can then be added to '''sudoers''' so that the key can do only that function.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
%backup ALL=(root:root) NOPASSWD: /usr/bin/rsync --server --sender -e.LsfxC . /etc/
&lt;/syntaxhighlight&gt;

Then to tie it all together, the account &quot;backup&quot; needs a key:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ grep '^command' ~/.ssh/authorized_keys
command=&quot;/usr/bin/rsync --server --sender -e.LsfxC . /etc/&quot; ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMm0rs4eY8djqBb3dIEgbQ8lmdlxb9IAEuX/qFCTxFgb 
&lt;/syntaxhighlight&gt;

Many of these programs have a '''--dry-run''' or equivalent option.  Remember to use it when figuring out the right settings.

===Read-only Access to Keys===

In some cases it is necessary to prevent accounts from being able to changing their own authentication keys.  However, such situations may be a better case for using certificates.  However, if done with keys it is accomplished by putting the key file in an external directory where the user has read-only access, both to the directory and to the key file.  Then the '''AuthorizedKeysFile''' directive assigns where [http://man.openbsd.org/sshd.8 sshd(8)] looks for the keys and can point to a secured location for the keys instead of the default location.

A good alternate location could be a new directory '''/etc/ssh/authorized_keys''' which could store the selected accounts' key files there.  The change can be made to apply to only a group of accounts by putting the settings under a '''Match''' directive.  The default location for keys on most systems is usually '''~/.ssh/authorized_keys'''.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Match Group sftpusers
	AuthorizedKeysFile /etc/ssh/authorized_keys/%u
&lt;/syntaxhighlight&gt;

Then the permissions there would allow the keys to be read but not written:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ls -dhln /etc/ssh/
drwxr-x--x 3 0 0 4.0K Mar 30 22:16 /etc/ssh/authorized_keys/

$ ls -dhln /etc/ssh/*.pub
-rw-r--r-- 1 0 0 173 Mar 23 13:34 /etc/ssh/fred
-rw-r--r-- 1 0 0  93 Mar 23 13:34 /etc/ssh/user1
-rw-r--r-- 1 0 0 565 Mar 23 13:34 /etc/ssh/user2
. . .
&lt;/syntaxhighlight&gt;

The keys could even be within subdirectories, though the same restrictions apply regarding permissions and ownership.  

For chrooted SFTP, the method is the same to keep the key files out of reach of the accounts:  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Match Group sftpusers
	ChrootDirectory /home
	ForceCommand internal-sftp -d %u
	AuthorizedKeysFile /etc/ssh/authorized_keys/%u
&lt;/syntaxhighlight&gt;

Of course a '''Match''' directive is not essential.  The settings could be made to apply to all accounts by putting the directive in the main part of the server configuration file instead.

==Mark Public Keys as Revoked==

Keys can be revoked.  Keys that have been revoked can be stored in '''/etc/ssh/revoked_keys''', a file specified in [http://man.openbsd.org/ssh_config.5 sshd_config(5)]  using the directive '''RevokedKeys''', so that [http://man.openbsd.org/sshd.8 sshd(8)] will prevent attempts to log in with them.  No warning or error on the client side will be given if a revoked key is tried.  Authentication will simply progress to the next key or method.

The revoked keys file should contain a list of public keys, one per line, that have been revoked and can no longer be used to connect to the server.  The key cannot contain any extras, such as [[OpenSSH/Client_Configuration_Files#Available_key_login_options | login options]] or it will be ignored. If one of the revoked keys is tried during a login attempt, the server will simply ignore it and move on to the next authentication method.  An entry will be made in the logs of the attempt, including the key's fingerprint.  See the section on [[OpenSSH/Logging_and_Troubleshooting | logging]] for a little more on that.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
RevokedKeys /etc/ssh/revoked_keys
&lt;/syntaxhighlight&gt;

The '''RevokedKeys''' configuration directive is not set in [http://man.openbsd.org/ssh_config.5 sshd_config(5)] by default.  It must be set explicitly if it is to be used.  This is another situation that might be better fulfilled through using certificate since a validity interval can be set in any combination of seconds, minutes, hours, days, or weeks can be set for certificates while keys are valid indefinitely.  

===Key Revocation Lists===

A Key Revocation List (KRL) is a compact, binary form of representing revoked keys and certificates.  In order to use a KRL, the server's configuration file must point to a valid list using the '''RevokedKeys''' directive.  KRLs themselves are generated with [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)] and can be created from scratch or edited in place.  Here a new one is made, populated with a single public key: 

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -k -f /etc/ssh/revoked_keys -z 1 ~/.ssh/old_key_rsa.pub
&lt;/syntaxhighlight&gt;

Here an existing KRL is updated by adding the '''-u''' option:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -u -k -f /etc/ssh/revoked_keys -z 2 ~/.ssh/old_key_dsa.pub
&lt;/syntaxhighlight&gt;

Once a KRL is in place, it is possible to test if a specific key or certificate is in the revocation list.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -Q -f /etc/ssh/revoked_keys ~/.ssh/old_key_rsa.pub
&lt;/syntaxhighlight&gt;

Only public keys and certificates will be loaded into the KRL.  Corrupt or broken keys will not be loaded and will produce an error message if tried.  Like with the regular '''RevokedKeys''' list, the public key destined for the KRL cannot contain any extras like login options or it will produce an error when an attempt is made to load it into the KRL or search the KRL for it.

==Verify a Host Key by Fingerprint==

The above examples have been about using keys to authenticate the client to the server.  A different context in which keys are used is when the server identifies itself to the client, which happens automatically at the beginning of each non-multiplexed session.  In order for that identification to happen the client acquires a public key from the server, usually on or prior to first contact, which it can subsequently use to ensure that it is connecting to the same server again and not an impostor.  The default locations for storing these acquired host keys on the client are in '''/etc/ssh/ssh_known_hosts''', if managed by the system administrator, or in '''~/.ssh/known_hosts''' if managed by the client's own account.  The format of the contents is a line with a host address and its matching public key.  The file is described in detail in the [http://man.openbsd.org/sshd.8 sshd(8)] manual page in the section &quot;SSH_KNOWN_HOSTS FILE FORMAT&quot;.

When connecting for the first time to a remote host, the server's host key should be verified in order to ensure that the client is connecting to the right machine and not an impostor or anything else.  Usually this verification is done by comparing the fingerprint of the server's host key rather than trying to compare the whole key itself.  By default the client will show the fingerprint if the key is not already found in the '''known_hosts''' register.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -l fred server.example.org
The authenticity of host 'server.example.org (192.0.32.10)' can't be established.
ECDSA key fingerprint is SHA256:LPFiMYrrCYQVsVUPzjOHv+ZjyxCHlVYJMBVFerVCP7k.
Are you sure you want to continue connecting (yes/no)? 
&lt;/syntaxhighlight&gt;

That can be compared to a fingerprint received out of band, say by post, e-mail, SMS, courier, and so on.  Specifically, the example represents the key's fingerprint as a base64 encoded SHA256 checksum.  That is the default style.  The fingerprint can also be displayed as an MD5 hash in hexadecimal instead by passing the client's '''FingerprintHash''' configuration directive as a runtime argument or setting it in [http://man.openbsd.org/ssh_config.5 ssh_config(5)].  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -o FingerprintHash=md5 host.example.org
The authenticity of host 'host.example.org (192.0.32.203)' can't be established.
RSA key fingerprint is MD5:10:4a:ec:d2:f1:38:f7:ea:0a:a0:0f:17:57:ea:a6:16.
Are you sure you want to continue connecting (yes/no)?
&lt;/syntaxhighlight&gt;

But the default in new versions is SHA256 in base64 has a lower chance of collision.

In OpenSSH 6.7 and earlier, the client showed fingerprints as a hexadecimal MD5 checksum instead a of the base64-encoded SHA256 checksum currently used:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -l fred server.example.org
The authenticity of host 'server.example.org (192.0.32.10)' can't be established. 
RSA key fingerprint is 4a:11:ef:d3:f2:48:f8:ea:1a:a2:0d:17:57:ea:a6:16. 
Are you sure you want to continue connecting (yes/no)? 
&lt;/syntaxhighlight&gt;

Another way of comparing keys is to use the ASCII art visual host key.  See further below about that.  

===Downloading keys===

Even though a host’s key is usually displayed for review the first time the SSH client tries to connect, it can also be fetched on demand at any time using [http://man.openbsd.org/ssh-keyscan.1 ssh-keyscan(1)]:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keyscan server.example.org
# server.example.org:22 SSH-2.0-OpenSSH_10.6
server.example.org ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBEWKepJgkC2XTG5cAr2Nyew6hOp5AjG7vi2RYFtPWqN3bo5XGuCX2d2YVyn++/2PtyMYBaKWyFpCNTT9X0F1Epg=
# server.example.org:22 SSH-2.0-OpenSSH_10.6
server.example.org ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQDKyERe8k+fnsrt4JrcLD3AW0kXj90r9ybrEZuY/CTrXIqYSizO335SxGJoWrKijaRy8htuueMkmNfxxhnBPoAjul/4T/FCRGKaV0jC96xYNnKcXbnXxSLVQ0OW2EIPvQhw/TU/G3vEqtiRYGyaNcZS6xrnVv3xuPuvVC1VRKspNLEq7zfvToC0OB89X5DIbvBbHY13PjJ0NrDdX3sSA8lxPsYagBuDIvyxH0S4Z5fQHeYrdvENS5zX6LwJeMeGSOqDuD0Zb4hpKxhaGVwP5e435VcFuImbFaDPM4w71PzaSUEj+tnUA0mGDoLiCrpW3txkJszog9lN3C/nLGghFaT7ajrfH55qut81JnvdhMju9+SzxrKPJmtQZfKVLIc4whEbtFsPCdm2bstz7ROWxTJ3t/Vr8/QVm2G2aY4FHuPwo2jUQDbQA7mCV+fe1sADy2jLzGhn1TCeYvWSv5PNJAT97IrLfD3+0Uo+qJD/6CU7F8oabj1Ql2H8fPN5kGSWfkM=
# server.example.org:22 SSH-2.0-OpenSSH_10.6
server.example.org ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIJo5gc4VrxVQ5apAOd7qK6UqGlLMpWOPuunjB53JBN2s
# server.example.org:22 SSH-2.0-OpenSSH_10.6
# server.example.org:22 SSH-2.0-OpenSSH_10.6
# server.example.org:22 SSH-2.0-OpenSSH_10.6
server.example.org ssh-mldsa44-ed25519 AAAAE3NzaC1tbGRzYTQ0LWVkMjU1MTkAAAVAyIw5r9FaniSYqBX0yd9vgBz5nCkebaQlMQN9N0p//Ukfn/CnZ3YtZWn6pUGjDM85/bqdL1gqah1OLfnl1eHk0qvTACrym07uKaMLoEHuakIXHbTi/ELPRoRP3F+DpEgjtYSjLc/fJiobRMgSvmLJxTUzZTStsqWAL1L9/1zuwHEngR+THpUcCSTi6KKkYcQiWGOFwpO22VdiuOg+zdQSH+9jW6eXYk1z81KU6UlHZps8zVrlqCd3FDDghgbH5U8DcGN2t6GvVfn6jFjpEk0ouj0of3/7010eRXjnv3QSbprCpMq73lAemQM+3LvTtrMBhFWNhCXhyOHfO1Yq7c8xaOwlFK78PlERjdHTvVJaCaDFDy7Pg9I+wxv+uC+W0wtzJ2S1y9XCYUgJo9yEiIGuSZdhMkYUwMnXLzQMm44hQOW153pdlHWze3kESCLg/LJf9RbUoSB43t6rghSHEiUkIi5TtCtFZ4nAGeH+wVwlB9Fwog5uZuJN1FYuuY5sSrLHJAQDUwudkdak0ifOhtPtsM/ClYr3baolQ/qi0ABYUVLKSV5b+A5DlTXa23zc7JAXm2YVfkWpOfVJG4TY81wrJoDumsd1y3XaH28/4QbADsZCE3wYsBou8ff0xKgPu8xm2K+sYSmzUbBGprArAQA0LtIDGNGqrb4JsZ1ru+viwzfSlxV7Nz7ZrSw6h+Ddq4J9A6oKXy6YS3uf1GFOtBQm6JfuyMHQEEUtYZrU4UK3C/fKHx9vjuw7YdhsL8JRgxbF14qJLFizkmVbK2e6aWEE4iCqLLLlZ0dC2peYUUqyGb9PsW7sewYzGbipzPpQ/GobRT3Obc3Gmu8P386pDGR7hmkOpFmVwIcfc431cUmZixK7CkPxzUvfaAAQkmNs/p4eNNoP0gq/xPGsV14/heULbWp/njGWk1ysjjGxP6YMwHcEZpUdSGbD05zbL0KkMtmKsr8yuJYjdVAgtH2bVAvrxXRXLgavmm97VYYq1A9rOYiQFlMrKRg6yZhT10Xt8Hukf6ySLk+fieFc3nH99YeysoA5rsfp9kdXr65GpwrBerZlf/20ZLJ7s4xaYb9SukR/8tiPt9iAVQjqPdb0MseZVrzhKo/jK44JHbHejHMoMMs7etPAS5TIjHxcJTP66B3eO9A0l2fAage2ka7ehTnHivxD3EE9KnqYBjIHDU7o6dTrX7UyQsdhax9bPKEL7OEtm6hXXfwzy4GdqGi124BclFAF0LeBSvBUgmSKIn3wfzJx/XXbt512eOn3WZk2v0TsiteH9kPEgDxVkUykawg2tleak9rTFMzYpDZRHvZD7uHWUZ8ktr2FEKWgq7/1Q2c80Z6H75VK9l1d3KZuoiWoF1s73R7ZAM+CWSrR+S5h+3AhYubDKPa/af+Lnlqe6ocVTqQPYaaRz25/cLBg6pgbdh18Ru6h3ljG2KiysyXeuoEoM5xVYtdIW7l9NeKDpGbZPAOqywXUpK+UCGjumIl7c48KCTIYcdtolnEbfVNBh0LRuftcVI+uF9cvQ0XacaNbgkYJYCjv4VR/n58EJ1b0c7tQBrVqMjDjIUKGhCMQqAeD3g75jeD60bBmVNPrq8RK+zH5VIa5eaBs3eitN98eVzd4b6UYTQd1QxLQZMrhQf4InRj39TZfGvQR5SXlLZQlweVHYkMps3IKbs3B3DCqlWCPUAnTAJBAG7HqWEYr5uEaKBawBSAx9jCQz00T+bp8KXpkOPzZCD6dfEfpHY6Rv6kmGJkiPUCb2hoX145HrS357G12+wDxKLN833oPVC0z
&lt;/syntaxhighlight&gt;

Once a key is acquired, its fingerprint can be shown using [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)] to read from '''stdin'''.  This can be done directly with a pipe.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keyscan server.example.org | ssh-keygen -l -f -
3072 SHA256:tQlw3vy325KrQibndP3gLS/YXUZjTLVA5yDFpg/Bb6I server.example.org (RSA)
256 SHA256:snnAtb/9csdy0BGhPjdg+VNWqN5bxCa/ge4C6zZ8muk server.example.org (ECDSA)
256 SHA256:agRZDZn8awhQ+tc19Ip/whkHoV33Ln2REO7v1kcYbdU server.example.org (ED25519)
512 SHA256:3Wdc6GbLIcc5mbuF2mhhokhARdMLuMK+ESRfJ+sM0QE server.example.org (MLDSA44-ED25519)
&lt;/syntaxhighlight&gt;

If there is more than one public key type is available from the server on the port polled, then [http://man.openbsd.org/ssh-keyscan.1 ssh-keyscan(1)] will fetch each of them.  If there is more than one key fed via '''stdin''' or a file, then [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)] will process them in order.  Prior to OpenSSH 7.2 manual fingerprinting was a two step process, the key was read to a file and then processed for its fingerprint.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keyscan -t ed25519 host.example.org &gt; key.pub
# host.example.org SSH-2.0-OpenSSH_6.8
$ ssh-keygen -lf key.pub                       
256 SHA256:ZmS+IoHh31CmQZ4NJjv3z58Pfa0zMaOgxu8yAcpuwuw host.example.org (ED25519)
&lt;/syntaxhighlight&gt;

Note that some output from [http://man.openbsd.org/ssh-keyscan.1 ssh-keyscan(1)] is sent to '''stderr''' instead of '''stdout'''.  

A hash, or fingerprint, can be generated manually with [http://linux.die.net/man/1/awk awk(1)], [http://linux.die.net/man/1/sed sed(1)] and [http://linux.die.net/man/1/xxd xxd(1)], on systems where they are found.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ awk '{print $2}' key.pub | base64 -d | md5sum -b | sed 's/../&amp;:/g; s/: .*$//'
$ awk '{print $2}' key.pub | base64 -d | sha256sum -b | sed 's/ .*$//' | xxd -r -p | base64 
&lt;/syntaxhighlight&gt;

It is possible to find all hosts from a file which have new or different keys from those in '''known_hosts''', if the host names are in clear text and not stored as hashes.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keyscan -t ed25519,mldsa44-ed25519 -f ssh_hosts | \
  sort -u - ~/.ssh/known_hosts | \
  diff ~/.ssh/known_hosts -
&lt;/syntaxhighlight&gt;

====Using ssh-keyscan(1) with ssh_config(5)====

The utility [http://man.openbsd.org/ssh-keyscan.1 ssh-keyscan(1)] does not parse [http://man.openbsd.org/ssh_config.5 ssh_config(5)].  That is in part to keep the code base simple.  There are a lot of configuration options which would be complicated to implement, including but not limited to '''ProxyJump''', '''ProxyCommand''', '''Match''', '''BindInterface''', and '''CanonicalizeHostname'''&lt;ref name=&quot;keyscan&quot;&gt;{{cite mailing list |url=https://lists.mindrot.org/pipermail/openssh-unix-dev/2023-March/040605.html | title=Why does ssh-keyscan not use .ssh/config? |publisher=mindrot.org | access-date=2023-03-01 | date=2023-03-01 | mailing-list=OpenSSH UNIX-dev | first=Damien | last=Miller }}&lt;/ref&gt; .  Resolving host names via the client configuration file can be done by wrapping the utility in a short shell function:

&lt;syntaxhighlight lang=&quot;shell&quot;&gt;
my-ssh-keyscan() {
	for host in &quot;$@&quot; ; do
		ssh-keyscan $(ssh -G &quot;$host&quot; | awk '/^hostname/ {print $2}')
	done
}
&lt;/syntaxhighlight&gt;

That shell function uses the '''-G''' option of [http://man.openbsd.org/ssh.1 ssh(1)] to resolve each host name using [http://man.openbsd.org/ssh_config.5 ssh_config(5)] and then check the resulting host name for SSH keys.

===ASCII Art Visual Host Key===

An ASCII art representation of the key can be displayed along with the SHA256 base64 fingerprint: 

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -l -v -f key 
256 SHA256:BClQBFAGuz55+tgHM1aazI8FUo8eJiwmMcqg2U3UgWU www.example.org (ED25519)
+--[ED25519 256]--+
|o+=*++Eo         |
|+o .+.o.         |
|B=.oo.  .        |
|*B.=.o .         |
|= B *   S        |
|. .@ .           |
| +..B            |
|  *. o           |
| o.o.            |
+----[SHA256]-----+
&lt;/syntaxhighlight&gt;

In OpenSSH 6.7 and earlier the fingerprint is in MD5 hexadecimal form.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -l -v -f key 
2048 37:af:05:99:e7:fb:86:6c:98:ee:14:a6:30:06:bc:f0 www.example.net (RSA) 
+--[ RSA 2048]----+ 
|          o      | 
|         o .     | 
|        o o      | 
|       o +       | 
|   .  . S        | 
|    E ..         | 
|  .o.* ..        | 
|  .*=.+o         | 
|  ..==+.         | 
+-----------------+ 
&lt;/syntaxhighlight&gt;

==More on Verifying SSH Keys==

Keys on the client or the server can be verified against known good keys by comparing the base64-encoded SHA256 fingerprints.  

===Verifying Stray Client Keys===

Sometimes is is necessary to compare two uncertain key files to check if they are part of the same key pair.  However, public keys are more or less disposable.  So the easy way in such situations on the client machine is to just rename or erase the old, problematic, public key and replace it with a new one generated from the existing private key.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -y -f ~/.ssh/my_key_ed25519
&lt;/syntaxhighlight&gt;

But if the two parts must really be compared, it is done in two steps using [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)].  First, a new public key is re-generated from the known private key and used to make a fingerprint to '''stdout'''.  Next, the fingerprint of the unknown public key is generated for comparison.  In this example, the private key '''my_key_a_ed25519''' and the public key '''my_key_b_ed25519.pub''' are compared:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -y -f my_key_a_ed25519 | ssh-keygen -l -f -
$ ssh-keygen -l -f my_key_b_ed25519.pub
&lt;/syntaxhighlight&gt;

The result is a base64-encoded SHA256 checksum for each key with the one fingerprint displayed right below the other for easy visual comparison.  Older versions don't support reading from '''stdin''' so an intermediate file will be needed then.  Even older versions will only show an MD5 checksum for each key.  Either way, automation with a shell script is simple enough to accomplish but outside the scope of this book.

===Verifying Server Keys===

Reliable verification of a server's host key must be done when first connecting.  It can be necessary to contact the system administrator who can provide it out of band so as to know the fingerprint in advance and have it ready to verify the first connection.  

Here is an example of the server's Ed25519 key being read and its fingerprint shown as SHA256 base64:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -l -f /etc/ssh/ssh_host_ed25519_key.pub 
256 SHA256:bFzzouaWmE5HuZIv+YnGUYI2q06i6M43V+6jMU3LHpA root@server.example.org (ED25519)
&lt;/syntaxhighlight&gt;

And here the corresponding ECDSA key is read, but shown as an MD5 hexadecimal hash:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -E md5 -l -f /etc/ssh/ssh_host_ecdsa_key.pub
256 MD5:ed:d2:34:b4:93:fd:0e:eb:08:ee:b3:c4:b3:4f:28:e4 root@server.example.net (ECDSA)
&lt;/syntaxhighlight&gt;

Prior to 6.8, the fingerprint was expressed as an MD5 hexadecimal hash:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -l -f /etc/ssh/ssh_host_rsa_key.pub 
2048 MD5:e4:a0:f4:19:46:d7:a4:cc:be:ea:9b:65:a7:62:db:2c root@server.example.net (RSA)
&lt;/syntaxhighlight&gt;

It is also possible to use [http://man.openbsd.org/ssh-keyscan.1 ssh-keyscan(1)] to get keys from an active SSH server.  However, the fingerprints still needs to be verified out of band.  

====Warning: Remote Host Identification Has Changed!====

If a server's key does not match what the client finds has been recorded in either the system's or the local account's '''authorized_keys''' files, then the client will issue a warning along with the fingerprint of the suspicious key.  

&lt;pre&gt;
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the ED25519 key sent by the remote host is
SHA256:bFzzouaWmE5HuZIv+YnGUYI2q06i6M43V+6jMU3LHpA.
Please contact your system administrator.
Add correct host key in /home/fred/.ssh/known_hosts to get rid of this message.
Offending ED25519 key in /home/fred/.ssh/known_hosts:11
Host key for server.example.org has changed and you have requested strict checking.
Host key verification failed.
&lt;/pre&gt;

Three reasons for the warning are common.  

One reason is that the server's keys were replaced, often because the server's operating system was reinstalled without backing up the old keys.  Another reason can be when the system administrator has phased out deprecated or compromised keys.  However that can be planned better and if there is time to plan the migration, new keys can just be added to the server and have the clients use the '''UpdateHostKeys''' option so that the new keys are accepted if the old keys match.  A third situation is when the connection is made to the wrong machine, such as when the remote system changes IP addresses because of dynamic address allocation.  

In all three cases where the key has changed there is only one thing to do: contact the system administrator and verify the key.   Ask if the OpenSSH-server was recently reinstalled, or was the machine restored from an old backup?  Keep in mind that the system administrator may be you yourself in some cases. 

The case which is rather rare but serious enough that it should be ruled out for sure is that the wrong machine is part of a man-in-the-middle attack.

In all four cases, an authentic key fingerprint can be acquired by any method where it is possible to verify the integrity and origin of the message, for example via PGP-signed e-mail.  If physical access is possible, then use the console to get the right fingerprint.  Once the authentic key fingerprint is available, return to the client machine where you got the error and remove the old key from '''~/.ssh/known_hosts'''

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -R server.example.org
&lt;/syntaxhighlight&gt;

Then try logging in, but compare the key fingerprints first and proceed if and '''only''' if the key fingerprint matches what you received out of band.  If the key fingerprint matches, then go through with the login process and the key will be automatically added.  If the key fingerprint does not match, stop immediately and figure out what you are connecting to.  It would be a good idea to get on the phone, a real phone not a computer phone, to the remote machine's system administrator or the network administrator.

===Multiple Keys for a Host, Multiple Hosts for a Key in known_hosts===
 
Multiple host names or IP addresses can use the same key in the '''known_hosts''' file by using pattern matching or simply by listing multiple systems for the same key.  That can be done in either the global list of keys in '''/etc/ssh/ssh_known_hosts''' and the local, account-specific lists of keys in each account's '''~/.ssh/known_hosts''' file.  Labs, computational clusters, and similar pools of machines can make use of keys in that way.  Here is a key shared by three specific hosts, identified by name, one host per line:
&lt;pre&gt;
server1 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMIId09yQEh9634wNXR+y7L79th2M4awBgCwqWJobJuQ fred@desk.example.org
server2 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMIId09yQEh9634wNXR+y7L79th2M4awBgCwqWJobJuQ fred@desk.example.org
server3 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMIId09yQEh9634wNXR+y7L79th2M4awBgCwqWJobJuQ fred@desk.example.org
&lt;/pre&gt;
Or a range can be specified by using globbing to a limited extent in either '''/etc/ssh/ssh_known_hosts''' or '''~/.ssh/known_hosts'''.
&lt;pre&gt;
172.19.40.* ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMIId09yQEh9634wNXR+y7L79th2M4awBgCwqWJobJuQ fred@desk.example.org
&lt;/pre&gt;
Conversely, a pool of servers might have multiple keys for the same address.  In that case, it is necessary to make multiple entries in either '''/etc/ssh/ssh_known_hosts''' or '''~/.ssh/known_hosts''' for each key.
&lt;pre&gt;
server1 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMIId09yQEh9634wNXR+y7L79th2M4awBgCwqWJobJuQ fred@desk.example.org
server1 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIBrsIIaDl/bJ40vyprvF+HYAq+kE2jWUsOt+WqIheaBw fred@desk.example.org
server1 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIC2CgwWTPH/qZDeHmW7ZUea18wa9As7Txq3P5dXCfoXj fred@desk.example.org 
&lt;/pre&gt;
Thus in order to get a pool of servers to share a pool of keys, each server-key combination must be added manually to the '''known_hosts''' file:
&lt;pre&gt;
server1 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMIId09yQEh9634wNXR+y7L79th2M4awBgCwqWJobJuQ fred@desk.example.org
server1 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIBrsIIaDl/bJ40vyprvF+HYAq+kE2jWUsOt+WqIheaBw fred@desk.example.org
server1 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIC2CgwWTPH/qZDeHmW7ZUea18wa9As7Txq3P5dXCfoXj fred@desk.example.org 

server2 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAICPSs4OR2LT89mv2tM4TKqeVhh4XvoLQ77MSBmjyrMGm fred@desk.example.org
server2 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIHChTzAoJr53A7VP1BdMHqLTFK5cz/2Vc065+VcpP4VA fred@desk.example.org
server2 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIHP+4BvU4DzwYQgznARxx/qyBWmu49PAywHwDRgslRaM fred@desk.example.org
&lt;/pre&gt;

Though upgrading to certificates might be a more appropriate approach that manually updating lots of keys.

===Another way of Dealing with Dynamic (roaming) IP Addresses===
It is possible to manually point to the right key using '''HostKeyAlias''' either as part of [http://man.openbsd.org/ssh_config.5 ssh_config(5)]  or as a runtime parameter.  Here the key for machine ''Foobar'' is used to connect to host 192.168.11.15

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -o StrictHostKeyChecking=accept-new \
      -o HostKeyAlias=foobar   \
      192.168.11.15
&lt;/syntaxhighlight&gt;
This is useful when DHCP is not configured to try to keep the same addresses for the same machines over time or when using certain stdio forwarding methods to pass through intermediate hosts.

===Host Key Update and Rotation in known_hosts===

A protocol extension to rotate weak public keys out of '''known_hosts''' has been in OpenSSH from version 6.8&lt;ref name=&quot;djm_rotation&quot;&gt;
{{cite web
| title=Key rotation in OpenSSH 6.8+ 
| author=Damien Miller
| url=http://blog.djm.net.au/2015/02/key-rotation-in-openssh-68.html
| date=2015-02-01
| publisher=DJM's Personal Weblog
| accessdate=2016-03-05
}}
&lt;/ref&gt; and later.  With it the server is able to inform the client of all its host keys and update '''known_hosts''' with new ones when at least one trusted key already known.  This method still requires the private keys be available to the server &lt;ref name=&quot;djm_rotation_redux&quot;&gt;
{{cite web
| title=Hostkey rotation, redux 
| author=Damien Miller
| url=http://blog.djm.net.au/2015/02/hostkey-rotation-redux.html
| date=2015-02-17
| publisher=DJM's Personal Weblog
| accessdate=2016-03-05
}}
&lt;/ref&gt; so that proofs can be completed.  In [http://man.openbsd.org/ssh_config.5 ssh_config(5)], the directive '''UpdateHostKeys''' specifies whether the client should accept updates of additional host keys from the server after authentication is completed and add them to '''known_hosts'''.  A server can offer multiple keys of the same type for a period before removing the deprecated key from those offered, thus allowing an automated option for rotating keys as well as for upgrading from weaker algorithms to stronger ones.  See also [https://datatracker.ietf.org/doc/html/rfc4819 RFC 4819: Secure Shell Public Key Subsystem] about key management standards.

==Converting Between SSH Key Formats==

OpenSSH has its own format for keys which it uses by default when new keys are made.  However, other SSH clients and servers may use other formats such as [https://www.rfc-editor.org/rfc/rfc4716 RFC4716], [https://www.rfc-editor.org/rfc/rfc5958 PKCS8], or [https://www.rfc-editor.org/rfc/rfc1421 PEM].  Any of these can be converted to the default OpenSSH format by [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)].  The default to format to try to convert from is RFC4716.  The utility [https://linux.die.net/man/1/puttygen puttygen(1)] makes keys in that format for [https://linux.die.net/man/1/putty putty(1)] and they need conversion when used with OpenSSH's server.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -i -f /var/tmp/key_public.ppk
&lt;/syntaxhighlight&gt;

However, you can use the '''-m''' option to specify either that format explicitly or else choose another one to convert from.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -i -m RFC4716 -f /var/tmp/key_public.ppk
$ ssh-keygen -i -m PKCS8 -f /var/tmp/key_public.ppk
&lt;/syntaxhighlight&gt;

Both examples above are for importing public keys into OpenSSH's own format.  

By default OpenSSH will write newly-generated keys in its own format, so the '''-m''' option is obligatory to produce public keys in another format.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -e -m PKCS8 -f ~/.ssh/key.pub
&lt;/syntaxhighlight&gt;

It is not yet possible to export private keys from the OpenSSH format to one of the other formats using the '''-e''' option.  Even if a private key is specified as input, a public key is produced:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -e -m RFC4716 -f ~/.ssh/key
&lt;/syntaxhighlight&gt;

Not all key types are supported by all key formats.  

It is also possible to use export to display the key pair as a traditional hex dump.
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -e -m hexdump -f ~/.ssh/key
Enter passphrase for &quot;key&quot;: 
Public ED25519 key:
buffer len = 51
0000: 00 00 00 0b 73 73 68 2d 65 64 32 35 35 31 39 00  ....ssh-ed25519.
0016: 00 00 20 b0 c5 cc 2c cb d8 8b 8d 75 80 eb e6 e9  .. ...,....u....
0032: 2c f4 36 08 7b 5b ad ad 0b 54 4f 7f 21 9d 1b e8  ,.6.{[...TO.!...
0048: 9e e0 32                                         ..2

Private ED25519 key:
buffer len = 119
0000: 00 00 00 0b 73 73 68 2d 65 64 32 35 35 31 39 00  ....ssh-ed25519.
0016: 00 00 20 b0 c5 cc 2c cb d8 8b 8d 75 80 eb e6 e9  .. ...,....u....
0032: 2c f4 36 08 7b 5b ad ad 0b 54 4f 7f 21 9d 1b e8  ,.6.{[...TO.!...
0048: 9e e0 32 00 00 00 40 e1 c3 a2 4d d9 89 49 72 9b  ..2...@...M..Ir.
0064: 86 72 6c 07 17 1b 40 4f 62 50 62 45 4f 4c cf cf  .rl...@ObPbEOL..
0080: 57 8b 9d c0 04 8f 9b b0 c5 cc 2c cb d8 8b 8d 75  W.........,....u
0096: 80 eb e6 e9 2c f4 36 08 7b 5b ad ad 0b 54 4f 7f  ....,.6.{[...TO.
0112: 21 9d 1b e8 9e e0 32                             !.....2
&lt;/syntaxhighlight&gt;

&lt;noinclude&gt;

== References ==
{{reflist}}
{{OpenSSH/TOC|mini}}
&lt;/noinclude&gt;
{{BookCat}}
{{status|100%}}</text>
      <sha1>mjiflb4q6snp69thbzcxfdr56gr7xzn</sha1>
    </revision>
    <revision>
      <id>4675781</id>
      <parentid>4675780</parentid>
      <timestamp>2026-10-13T04:33:25Z</timestamp>
      <contributor>
        <username>Larsnooden</username>
        <id>430753</id>
      </contributor>
      <comment>convert alias to function in ephemeral agent example</comment>
      <origin>4675781</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="81887" sha1="lo1bfmh4qqrrwfpwj3zkdoy4ewapbvt" xml:space="preserve">&lt;noinclude&gt;{{simple chapter navigation|previous=File Transfer with SFTP|next=Certificate-based Authentication}}&lt;/noinclude&gt;
&amp;nbsp;

Authentication keys can improve efficiency, if done properly.  As a bonus advantage, the passphrase and private key never leave the client&lt;ref name=&quot;RFC4252§7&quot;&gt;{{cite web |url=https://tools.ietf.org/html/rfc4252#section-7 |title=The Secure Shell (SSH) Authentication Protocol |publisher=IETF |year=2006| accessdate=2015-05-06}}&lt;/ref&gt;.  Key-based authentication is generally recommended for outward facing systems so that password authentication can be turned off.  

==Key-based authentication==

OpenSSH can use public key cryptography for authentication.  In public key cryptography, encryption and decryption are asymmetric.  The keys are used in pairs, a public key to encrypt and a private key to decrypt.  The [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)] utility can make RSA, Ed25519, MLDSA44-Ed25519, ECDSA, Ed25519-SK, or ECDSA-SK keys for authenticating.  Even though DSA keys can still be made, being exactly 1024 bits in size, they are no longer recommended and should be avoided.  RSA keys are allowed to vary from 1024 bits on up.  The default is now 3072.  However, there is only limited benefit after 2048 bits and that makes elliptic curve algorithms preferable.  ECDSA can be 256, 384 or 521 bits in size.  Ed25519, Ed25519-SK, and ECDSA-SK keys each have a fixed length of 256 bits.  Shorter keys are faster, but less secure.  Longer keys are much slower to work with but provide better protection, up to a point.  

Keys can be named to help remember what they are for.  Because the key files can be named anything it is possible to have many keys each named for different services or tasks.  The comment field at the end of the public key can also be useful in helping to keep the keys sorted, if you have many of them or use them infrequently.  

The process of key-based authentication uses these keys to make a couple of exchanges using the keys to encrypt and decrypt some short message.  At the start, a copy of the client's public key is stored on the server and the client's private key is on the client, both stay where they are.  The private key never leaves the client.  As the client first contacts the server, the server responds by using the client's public key to encrypt a random number and return that encrypted random number as a challenge to the client.  The client responds to the challenge by using the matching private key to decrypt the message and extract the random number.  The client then makes an MD5 hash of the session ID along with the random number from the challenge and returns that hash to the server.  The server then makes its own hash of the session ID and the random number and compares that to the hash returned by the client.  If there is a match, the login is allowed.  If there is not a match, then the next of any public keys on the server registered as belonging to the same account is tried until either a match is found or all the keys have been tried or the maximum number of failures has been reached. &lt;ref name=&quot;How Key Challenges Work&quot;&gt;{{cite web | url=http://www.unixwiz.net/techtips/ssh-agent-forwarding.html#chal | title=An Illustrated Guide to SSH Agent Forwarding | author=Steve Friedl | date=2006-02-22 | accessdate=2013-04-27 | publisher=Unixwiz.net }}&lt;/ref&gt;

When an agent is used on the client side to manage authentication, the process is similar.  The difference is that [http://man.openbsd.org/ssh.1 ssh(1)] passes the challenge off to the agent which then calculates the response and passes it back to [http://man.openbsd.org/ssh.1 ssh(1)] which then passes the agent's response back to the server.  

===Basics of Public Key Authentication===

A matching pair of SSH keys, one public and one private, is needed for public key authentication.  The [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)] utility is used to make such a key pair.  Out of that pair the public key must be properly stored on the remote host before using key-based authentication.  The default location for it is the designated '''authorized_keys''' file, usually one such file resides inside each remote user account.  The private key stays stored safely on the client.  

Once the keys have been prepared and the remote account configured, they can be used for login.  Before starting, there must already be an account on the remote system.  The details of doing that are outside of the scope of this book.  However, once you have a remote account, there are four steps to set up key-based authentication for it:

'''1''') Prepare a directory on the client (say a laptop or a desktop) where the keys will stay, if there isn't one already.  For example, if the '''.ssh''' directory is not on the client machine, create it and set the permissions correctly.  It is important that it not be writable by any account except its owner:
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ mkdir ~/.ssh/
$ chmod 0700 ~/.ssh/
&lt;/syntaxhighlight&gt;

'''2''') Create a key pair inside the designated directory.  The example here creates an Ed25519 key pair in the directory '''~/.ssh'''.  The option '''-t''' decides the key type and the option '''-f''' assigns the key file a name.  It is good to give key files descriptive names, especially if larger numbers of keys are managed.  Below, the public key will be named '''fred_example_org_ed25519.pub''' and the private key will be called '''fred_example_org_ed25519'''.  Lastly, the '''-C''' option is used to embed a descriptive comment inside the private key itself.  The comment is useful for figuring out later what the key is for when one has many keys or a lot of time has passed or both.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -t ed25519 -f ~/.ssh/fred_example_org_ed25519 \
        -C &quot;from fred's laptop to server.example.org&quot;
&lt;/syntaxhighlight&gt;

Be sure to enter a solid passphrase so that the private key gets encrypted using 128-bit AES.  That way the private key can only be read or used when the passphrase is given.  

Ed25519, Ed25519-SK, and ECDSA-SK keys have fixed lengths.  For RSA and ECDSA keys, the '''-b''' option sets the number of bits used for those kinds of keys.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -o -b 4096 -t rsa -f ~/.ssh/fred_example_org_rsa \
        -C &quot;from fred's laptop to server.example.org&quot;
&lt;/syntaxhighlight&gt;

Since 6.5 a new private key format is available using a [http://man.openbsd.org/bcrypt.3 bcrypt(3)] key derivative function (KDF) to better protect keys at rest.  This new format is always used for Ed25519 keys, and sometime in the future will be the default for all keys.  But for right now it may be requested when generating or saving existing keys of other types via the '''-o''' option in [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)].  

Details of the new format are found in the source code in the file '''PROTOCOL.key'''.

'''3''') Get the keys to the right places.  Transfer only the public key to remote machine.  The following assume the default locations for the authorized keys as specified in the server's configuration file by the '''AuthorizedKeysFile''' directive.  

'''3a''') If the utility &lt;code&gt;ssh-copy-id&lt;/code&gt; exists, and if password authentication is allowed, then it can be used to put the public key into place on the remote system.  The ''.pub'' is optional here, the script will figure it out if omitted. 
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-copy-id -i ~/.ssh/fred_example_org_ed25519 fred@server.example.org
&lt;/syntaxhighlight&gt;

If that script was successful in transferring the public key, then go on to step 4 below and test the key.  If not, then try transferring the public key manually as described in step 3b next.

'''3b''') Or the public key can be put in place manually on the remote machine.  For that the remote '''.ssh''' directory is needed, and within that a special file to store the public keys, the default file name is '''authorized_keys'''.  If either the '''authorized_keys''' file or '''.ssh''' directory do not exist on the remote machine, they need to be created.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ mkdir -m 700 ~/.ssh/
$ touch ~/.ssh/authorized_keys
$ chmod 0600 ~/.ssh/authorized_keys
$ nano -w ~/.ssh/authorized_keys
&lt;/syntaxhighlight&gt;

Then any editor which does not wrap long lines can be used to add the public key.  However the '''authorized_keys''' file is edited to add the key, the key itself must be in the file whole and unbroken on a single  line.  For example, [http://linux.die.net/man/1/nano nano(1)] can be started with the '''-w''' option to prevent wrapping of long lines.  (Another way to set line wrapping permanently in [http://linux.die.net/man/1/nano nano(1)] is by editing [http://linux.die.net/man/5/nanorc nanorc(5)].)  

If the key pair is not already on the client, transfer both the public and private keys there.  It is usually best to keep both the public and private keys together in the directory '''~/.ssh/''', though the public key is not always needed on the client after this step and could even be regenerated if it is ever needed again.  

'''4''') Test the keys

While remaining logged in via the first terminal, use the client system to open another window and in it start another SSH session and try authenticating to the remote machine from the client using the private key.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -i ~/.ssh/fred_example_org_ed25519 -l fred server.example.org
&lt;/syntaxhighlight&gt;

The option '''-i''' tells [http://man.openbsd.org/ssh.1 ssh(1)] which private key to try.  
Only after verifying that the key-based authentication works should you close the original window.  

It is possible to make permanent shortcuts on the client using [http://man.openbsd.org/ssh_config.5 ssh_config(5)], explained further below, once key-based authentication is working.  In particular, see the '''IdentityFile''',  '''IdentitiesOnly''', and '''AddKeysToAgent''' configuration directives, to name three.  

It is also a good idea to turn off password authentication, if and only if key-based authentication is setup for all the necessary remote accounts.  

➥ '''Troubleshooting of Key-based Authentication''':

If the server refuses to accept the key and fails over to the next authentication method (e.g.: &quot;Server refused our key&quot;), then there are several possible mistakes to look for on the server side.  

One of the most common errors is that the file and directory permissions are wrong.  The authorized keys file must be owned by the user in question and not be group writable.  Nor may the key file's directory be group or world writable.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ chmod u=rwx,g=rx,o= ~/.ssh
$ chmod u=rw,g=,o=  ~/.ssh/authorized_keys 
&lt;/syntaxhighlight&gt;

Another mistake that can happen is if the key inside the '''authorized_keys''' file on the remote host is broken by line breaks or has other whitespace in the middle.  That can be fixed by joining up the lines and removing the spaces or by recopying the key more carefully.  

And, though it should go without saying, the halves of the key pair need to match.  The public key on the server needs to match the private key held on the client.  If the public key is lost, then a new one can be generated with the '''-y''' option, but not the other way around.  If the private key is lost, then the public key should be erased as it is no longer of any use.  If many keys are in use for an account, it might be a good idea to add comments to them.  On the client, it can be a good idea to know which server the key is for, either through the file name itself or through the comment field.  A comment can be added using the '''-C''' option.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -t ed25519 -f ~/.ssh/fred_example_org_ed25519 -C &quot;web server mirror&quot;
&lt;/syntaxhighlight&gt;

On the server, it can be important to annotate which client they key is from if there is more than one public key there in an account.  There the comment can be added to the authorized keys file on the server in the last column if a comment does not already exist.  Again, the format of the authorized keys file is given in the manual page for [http://man.openbsd.org/sshd.8 sshd(8)] in the section &quot;AUTHORIZED_KEYS FILE FORMAT&quot;.  If the keys are not labeled they can be hard to match, which might or might not be what you want.  

====Associating Keys Permanently with a Server====

A key can be specified at run time, but to save retyping the same paths again and again, the '''Host''' directive in [http://man.openbsd.org/ssh_config.5 ssh_config(5)] can apply specific settings to a target host.  In this case, by changing '''~/.ssh/config''' it is possible to assign particular keys to be tried automatically whenever making a connection to that specific host.  After adding the following lines to '''~/.ssh/config''', all that's needed is to type &lt;code&gt;ssh ''web1''&lt;/code&gt; to connect with the key for that server.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Host web1
	Hostname 198.51.100.32
	IdentitiesOnly yes
	IdentityFile /home/fred/.ssh/web_key_ed25519
&lt;/syntaxhighlight&gt;

The '''~/.ssh/config''' below uses different keys for ''server'' versus ''server.example.org'',  regardless whether they resolve to the same machine.   This is possible because the host name argument given to [http://man.openbsd.org/ssh.1 ssh(1)] is not converted to a canonicalized host name before matching.

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Host server
	IdentitiesOnly yes
	IdentityFile /home/fred/.ssh/key_a_ed25519

Host server.example.org
	IdentitiesOnly yes
	IdentityFile /home/fred/.ssh/key_b_ed25519
&lt;/syntaxhighlight&gt;

In this example the shorter name is tried first, but of course less ambiguous shortcuts can be made instead.  The configuration file gets parsed on a first-match basis.  So the most specific rules go at the beginning and the most general rules go at the end.  

====Encrypted Home Directories====

When using encrypted home directories the keys must be stored in an unencrypted directory.  That means somewhere outside the actual home directory which means [http://man.openbsd.org/sshd.8 sshd(8)] needs to be configured appropriately to find the keys in that special location.  

Here is one method for solving the access problem.  Each user is given a subdirectory under '''/etc/ssh/keys/''' which they can then use for storing their '''authorized_keys''' file.  This is set in the server's configuration file '''/etc/ssh/sshd_config'''

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
AuthorizedKeysFile      /etc/ssh/keys/%u/authorized_keys
&lt;/syntaxhighlight&gt;

Setting a special location for the keys opens up more possibilities as to how the keys can be managed and multiple key file locations can be specified if they are separated by whitespace.  The user does not have to have write permissions for the '''authorized_keys''' file.  Only read permission is needed to be able to log in.  But if the user is allowed to add, remove, or change their keys, then they will need write access to the file to do that.  

One symptom of having an encrypted home directory is that key-based authentication only works when you are already logged into the same account, but fails when trying to make the first connection and log in for the first time.

Sometimes it is also necessary to add a script or call a program from '''/etc/ssh/sshrc''' immediately after authentication to decrypt the home directory.

====Passwordless Login====

One solution for passwordless logins is to still have a passphrase and work with an authentication agent in conjunction with a single-purpose key.  Most desktop environments launch an SSH agent automatically these days.  It will be visible in the '''SSH_AUTH_SOCK''' environment variable if it is.  On accounts with an agent, [http://man.openbsd.org/ssh-add.1 ssh-add(1)] can load private keys into an available agent.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-add ~/.ssh/fred_example_org_ed25519
&lt;/syntaxhighlight&gt;

Thereafter, the client will automatically check the agent for the key when appropriate.  If there are many keys in the agent, it will become necessary to set '''IdentitiesOnly'''.  See the above section on using '''~/.ssh/config''' for that.  See [[OpenSSH/Cookbook/Public_Key_Authentication#Key-based_Authentication_Using_an_Agent|Key-based Authentication Using an Agent]] below.  

Another, riskier, way of allowing passwordless logins is to follow the steps above, but simply do not enter a passphrase when asked for one while creating the key.  Note that using keys that lack a passphrase is very risky, so the key files should be very well protected and kept track of, and ideally locked down with a '''command=''' option or '''ForceCommand''' directive on the server.  That includes those keys which will only be used as single-purpose keys as described below.  

Timely key rotation becomes especially important.  In general, it is not a good idea to make a key without a passphrase.

====Requiring Both Keys and a Password====

While users should have strong passphrases for their keys, there is no way to enforce or verify that.  Indeed, since neither the private key nor its the passphrase ever leave the client machine there is nothing that the server can do to have any influence over that.  Instead, it is possible to require both a key and a password.  Starting with OpenSSH 6.2, it is possible for the server to require multiple authentication methods for login using the '''AuthenticationMethods''' directive.   
&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
AuthenticationMethods publickey,password
&lt;/syntaxhighlight&gt;

This example from [http://man.openbsd.org/sshd_config.5 sshd_config(5)] requires that users first authenticate using a key and it only queries for a password if the key succeeds.  Thus with that configuration it is not possible to get to the system password prompt without first authenticating with a valid key.  Changing the order of the arguments changes the order of the authentication methods.

====Requiring Two or More Keys====

Since OpenSSH 6.8, the server now remembers which public keys have been used for authentication and refuses to accept previously-used keys.  This allows a set up requiring that users authenticate using two different public keys, maybe one in the file system and the other in a hardware token. 

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
AuthenticationMethods publickey,publickey
&lt;/syntaxhighlight&gt;

The '''AuthenticationMethods''' directive, whether for keys or passwords, can also be set on the server under a '''Match''' directive to apply only to certain groups or situations.

====Requiring Certain Key Types For Authentication====

Also since OpenSSH 6.8, the '''PubkeyAcceptedKeyTypes''' directive, later changed to '''PubkeyAcceptedAlgorithms''', can specify which key algorithms are accepted for authentication.  Those not in the comma-separated pattern list are not allowed.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
PubkeyAcceptedAlgorithms ssh-ed25519*,ssh-rsa*,ecdsa-sha2*,sk-ssh-ed25519*,sk-ecdsa-sha2*
&lt;/syntaxhighlight&gt;

Either the actual key types or a pattern can be in the list.  Spaces are not allowed in the pattern list.  The exact list of key types supported for authentication can be found by the '''-Q''' option using the client.  The following two lines are equivalent.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -Q key-sig | sort

$ ssh -Q PubkeyAcceptedAlgorithms | sort
&lt;/syntaxhighlight&gt;

For host-based authentication, it is the '''HostbasedAcceptedAlgorithms''' directive which determines the key types which are allowed for authentication.

===Key-based Authentication Using the AuthorizedKeysCommand Directive===

It is possible to use a program or script to look up public keys rather than keeping them in a static file or files.  Any command called by the '''AuthorizedKeysCommand''' directive needs to either produce a syntactically correct public key while returning the exit code for a successful run or else return the exit code for failure.  The string sent to '''stdout''' will then be processed as part of the authentication work flow.  

Here is a shell script&lt;ref name=&quot;janpietmens&quot;&gt;{{cite web |url=https://jpmens.net/2025/03/25/authorizedkeyscommand-in-sshd/ |title=SSH keys from a command: sshd's AuthorizedKeysCommand directive |accessdate=2025-04-04 |date=2025-03-25 | author=Jan-Piet Mens }}&lt;/ref&gt; at its simplest, without constraints, demonstrating a public key lookup:

&lt;syntaxhighlight lang=&quot;shell&quot;&gt;
#!/bin/sh

echo &quot;ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIKs/UouletvojgB1YeRZ4MY6iRblQ2ERDuNhQO4tOvdL&quot;

exit 0
&lt;/syntaxhighlight&gt;

For authentication to succeed, the script must return exit code 0  (success) after sending the syntactically correct matching public key to '''stdout'''.  For the SSH daemon to even run the script in the first place, the script must have the correct file and directory permissions.

Both the '''AuthorizedKeysCommandUser''' directive and '''AuthorizedKeysCommand''' must be used together.  The former designates which account the script or program use when run.  If set to ''none'' or if it does not refer to a valid account then [http://man.openbsd.org/sshd sshd(8)] will just ignore the command.  If '''AuthorizedKeysCommand''' is set, and '''AuthorizedKeysCommandUser''' is left empty or missing, then [http://man.openbsd.org/sshd sshd(8)] won't even run when invoked.  The error will be:

&lt;syntaxhighlight lang=&quot;text&quot;&gt;
AuthorizedKeysCommand set without AuthorizedKeysCommandUser
&lt;/syntaxhighlight&gt;

The '''AuthorizedKeysFile''' is always tried first when it is present in the server configuration.  The '''AuthorizedKeysCommand''' directive will not even be tried when the authorized keys file can provide a relevant key first.  

====A More Detailed Example Using the AuthorizedKeysCommand Directive====

By default the user name trying to log in is passed to the script when no tokens or arguments are provided.  Whether or how that information is used is up to the script.  The SSH daemon can also pass any combination of the tokens described in the TOKENS section of [http://man.openbsd.org/sshd_config sshd_config(5)] into the program or script being called.  Furthermore, the program or script can even be a front end for a database, such as OpenLDAP, or any similar system, as long as '''stdout''' produces a public key.  

Below is a more detailed example which uses a local script named '''keyfinder''' run with the account '''keys''' to look up the a public key for certain accounts.  First in [http://man.openbsd.org/sshd_config sshd_config(5)] the two directives:

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
AuthorizedKeysCommand /usr/local/sbin/keyfinder %U
AuthorizedKeysCommandUser keys
&lt;/syntaxhighlight&gt;

The script below is only a demonstration and a more complex program can call databases or do advanced lookups or heuristics:  

&lt;syntaxhighlight lang=&quot;shell&quot;&gt;
#!/bin/sh

set -e

case $1 in
        &quot;1000&quot;)
                echo &quot;ssh-ed25519 AAAAC3NzaC1lZDIE5AAAAIK89...UT9hz&quot;
                ;;

        &quot;1001&quot;)
                echo &quot;restrict ssh-ed25519 AAAAC3NzaC1lZDI1NTAAIBvGx...Y0zxV&quot;
                ;;

        &quot;1002&quot;)
                echo &quot;command=\&quot;/usr/libexec/sftp-server\&quot; ssh-ed25519 AAAAC3NzaC1lZDI1TE5AIPSyY...cPTg3&quot;
                ;;

        *)
                exit 1
                ;;
   
esac

exit 0
&lt;/syntaxhighlight&gt;

The '''AuthorizedKeysCommand''' scripts or programs can return any correctly formatted public key to '''stdout''' for consideration in the authentication process.  That includes adding constraints to the keys.  Above, the account with the UID 1000 has no constraints, while the account with UID 1001 is quite constrained.  Finally, the account with the UID 1002 can only access the SFTP service.  See the section &quot;AUTHORIZED_KEYS FILE FORMAT&quot; in [http://man.openbsd.org/sshd sshd(8)] for the full set of possibilities.

===Key-based Authentication Using an Agent===

When an authentication agent, such as [http://man.openbsd.org/ssh-agent.1 ssh-agent(1)], is going to be used, it should generally be started at the beginning of a session and used to launch the login session or X-session so that the environment variables pointing to the agent and its UNIX-domain socket are passed to each subsequent shell and process.  Many desktop distros do this automatically upon login or startup.  

Starting an agent entails setting a pair of environment variables:

* SSH_AGENT_PID : the process id of the agent
* SSH_AUTH_SOCK : the filename and full path to the UNIX-domain socket

The various SSH and SFTP clients find these variables automatically and use them to contact the agent and try when authentication is needed.   However, it is mainly SSH_AUTH_SOCK which is ever used.  If the shell or desktop session was launched using [http://man.openbsd.org/ssh-agent.1 ssh-agent(1)], then these variables are already set and available.  If they are not available, then it is necessary to either set the variables manually inside each shell or for each application in order to use the agent or else to point to the agent's socket using the directive '''IdentityAgent''' in the client's configuration file.  

Once an agent is available, a relevant private key needs to be loaded before the agent can be used.  Once in the agent the private key can then be used many times.  Private keys are loaded into an agent with [http://man.openbsd.org/ssh-add.1 ssh-add(1)].
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-add /home/fred/.ssh/mykey_ed25519
Identity added: /home/fred/.ssh/mykey_ed25519 (/home/fred/.ssh/mykey_ed25519)
&lt;/syntaxhighlight&gt;

Keys stay in the agent for as long as it is running unless specified otherwise.  A timeout can be set either with the '''-t''' option when starting the agent itself or when actually loading the key using [http://man.openbsd.org/ssh-add.1 ssh-add(1)].  In either case, the '''-t''' option will set a timeout interval, after which the key will be purged from the agent.
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-add -t 1h30m /home/fred/.ssh/mykey_ed25519
Identity added: /home/fred/.ssh/mykey_ed25519 (/home/fred/.ssh/mykey_ed25519)
Lifetime set to 5400 seconds
&lt;/syntaxhighlight&gt;

The option '''-l''' will list the fingerprints of all of the identities in the agent.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-add -l                                    
256 SHA256:77mfUupj364g1WQ+O8NM1ELj0G1QRx/pHtvzvDvDlOk mykey for task x (ED25519)
3072 SHA256:7unq90B/XjrRbucm/fqTOJu0I1vPygVkN9FgzsJdXbk myotherkey rsa for task y (RSA)
&lt;/syntaxhighlight&gt;

It is also possible to remove individual identities from the agent using '''-d''' which will remove them one at a time if identified by file name, but only if the file name is given and without the file name of the private key to be remove, '''-d''' will fail silently.  Using '''-D''' instead will remove all of them at once without needing to specify any by name.  

By default [http://man.openbsd.org/ssh-add.1 ssh-add(1)] uses the agent connected via the socket named in the environment variable '''SSH_AUTH_SOCK''', if it is set.  Currently, that is its only option.  However, for [http://man.openbsd.org/ssh.1 ssh(1)] an alternative to using the environment variable is the client configuration directive '''IdentityAgent''' which tells the SSH clients which socket to use to communicate with the agent.  If both the environment variable and the configuration directive are available at the same time, then the value in '''IdentityAgent''' takes precedence over what's in the environment variable.  '''IdentityAgent''' can also be set to ''none'' to prevent the connection from trying to use any agent at all.  

The client configuration directive '''AddKeysToAgent''' can also be useful in getting keys into an agent as needed.  When set, it automatically loads a key into a running agent the first time the key is called for if it is not already loaded.  Likewise the '''IdentitiesOnly''' directive can ensure that the relevant key is offered on the first try.  Rather than typing these out whenever the client is run, they can be added to '''~/.ssh/config''' and thereby added automatically for designated host connections.  

====Agent Forwarding====

Agent forwarding is one means of passing through one or more intermediate hosts.  However, the '''-J''' option for '''ProxyJump''' would be a safer option.  See [[OpenSSH/Cookbook/Proxies_and_Jump_Hosts#Jump_Hosts_--_Passing_Through_a_Gateway_or_Two | Passing Through a Gateway or Two]] in the section on jump hosts about that.  With agent forwarding, intermediate machines forward challenges and responses back and forth between the client and the final destination.  This comes with some risks but eliminates the need for using passwords or holding keys on any of these intermediate machines.  

A main advantage of agent forwarding is that the private key itself is not needed on any remote machine, thus hindering unwanted file system access to it. &lt;ref name=&quot;OpenSSH key management, Part 3&quot;&gt;{{cite web | url=http://www.ibm.com/developerworks/library/l-keyc3/ | title=Common threads: OpenSSH key management, Part 3 | author=Daniel Robbins | publisher=IBM | date=2002-02-01 | accessdate=2013-04-27}}&lt;/ref&gt;  Another advantage is that the actual agent to which the user has authenticated does not go anywhere and is thus less susceptible to analysis.  

One risk with agents is that they can be re-used to tailgate in if the permissions allow it.  Keys cannot be copied this way, but authentication is possible when there are incorrect permissions.  Note that disabling agent forwarding does not improve security unless users are also denied shell access, as they can always install their own forwarders.

The risks of agent forwarding can be mitigated by confirming each use of a key by adding the '''-c''' option when adding the key to the agent.  This requires the SSH_ASKPASS variable be set and available to the agent process, but will generate a prompt on the host running the agent upon each use of the key by a remote system.  So if passing through one or more intermediate hosts, it is usually better to instead have the SSH client use stdio forwarding with '''-W''' or '''-J'''.

On the client side agent forwarding is disabled by default and so if it is to be used it must be enabled explicitly.  Put the following line in  [http://man.openbsd.org/ssh_config.5 ssh_config(5)] to enable agent forwarding for a particular server:
&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
        Host gateway.example.org
        ForwardAgent yes
&lt;/syntaxhighlight&gt;

On the server side the default configuration files allow authentication agent forwarding, so to use it, nothing needs to be done there, just on the client side.  However, again, it would be preferable to take a look at '''ProxyJump''' instead.  

=====Old Style, Somewhat Safer SSH Agent Forwarding=====

The best way to pass through one or more intermediate hosts is to use the '''ProxyJump''' option instead of authentication agent forwarding and thereby not risk exposing any private keys.  If authentication agent forwarding must be used, then it would be advisable in the interest of following the principle of least privilege to forward an agent containing the minimum necessary number of keys.  There are several ways to solve that.  

In version 8.8 and earlier a partial solution is to make a one-off, ephemeral agent to hold just the one key or keys needed for the task at hand.  Another partial solution would be to set up a user-accessible service at the operating system level and then use [http://man.openbsd.org/ssh_config.5 ssh_config] for the rest.  

Automatically launching an ephemeral agent unique to each session can be done by crafting either a special shell alias or function to launch a single-use agent.  Either the function or the alias can be written to require confirmation for each requested signature.  The following example is a function is inspired by an updated blog post by Vincent Bernat&lt;ref name=&quot;safer-agent-forwarding&quot;&gt;{{cite web |url=https://vincent.bernat.ch/en/blog/2020-safer-ssh-agent-forwarding |title=Safer SSH agent forwarding |author=Vincent Bernat|date=2020-04-05 |accessdate=2020-10-04}}&lt;/ref&gt; on SSH agent forwarding:
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ agentssh() {
        ssh-agent ssh -o AddKeysToAgent=confirm -o ForwardAgent=yes
}
&lt;/syntaxhighlight&gt;

Note the use of [http://man.openbsd.org/ssh-agent.1 ssh-agent(1)].  When invoking that alias, the SSH client will be launched with a unique, ephemeral supporting key agent.  The alias sets up a new agent, including setting the two environment variables, and then sets two client options while calling the client.  This arrangement still checks with [http://man.openbsd.org/ssh_config.5 ssh_config(5)] for other options and settings.  When the SSH session is finished the agent which launched it ends and goes away, thus cleaning up after itself automatically.  

Another way is to rely on the client's configuration file for some of the settings.  Such methods rely mostly on [http://man.openbsd.org/ssh_config.5 ssh_config(5)] but still require an independent method to launch an ephemeral agent because the OpenSSH client is already running by the time it reads the configuration file and is thus not affected by any changes to environment variables caused by the configuration file and it is through the environment variables that contain information about the agent.  However, when the path to the UNIX-domain socket used to communicate with the authentication agent is decided in advance then the '''IdentityAgent''' option can point to it once the one-off agent&lt;ref name=&quot;wikimedia_ssh_agents&quot;&gt;{{cite web |url=https://wikitech.wikimedia.org/wiki/Managing_multiple_SSH_agents#Linux_solutions |title=Managing multiple SSH agents |publisher=Wikimedia|accessdate=2020-04-07}}&lt;/ref&gt; is actually launched.  The following uses a specific agent's pre-defined socket whenever connecting to either of two particular domains:

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Host *.wikimedia.org *.wmflabs.org
        User fred
        IdentitiesOnly yes
        IdentityFile %d/.ssh/id_cloud_01
        IdentityAgent /run/user/%i/ssh-cloud-01.socket
        ForwardAgent yes
        AddKeysToAgent yes
&lt;/syntaxhighlight&gt;

The '''%d''' stands for the path to the home directory and the '''%i''' stands for the user id (UID) for the current account.  In some cases the '''%i''' token might also come in handy when setting the '''IdentityAgent''' option inside the configuration file.  Again, be careful when forwarding agents with which keys are in the forwarded agent.  See the section &quot;TOKENS&quot; in [http://man.openbsd.org/ssh_config.5 ssh_config(5)] for more such abbreviations.  

With those configuration settings, the authentication agent must already be up and running and point to the designated socket prior to starting the SSH client for that configuration to work.  Additionally, it should place the socket in a directory which is inaccessible to any other accounts.  [http://man.openbsd.org/ssh-agent.1 ssh-agent(1)] must use the '''-a''' option to name the socket:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-agent -a /run/user/${UID}/ssh-cloud-01.socket
&lt;/syntaxhighlight&gt;

That agent configuration can be launched manually or via a script or service manager.  However, in the interests of privacy and security in general, agent forwarding is to be avoided.  The configuration directive '''ProxyJump''' is the best alternative and, on older systems, host traversal using '''ProxyCommand''' with [http://man.openbsd.org/nc.1 netcat] are preferable.  Again, see the section on [[OpenSSH/Cookbook/Proxies and Jump Hosts|Proxies and Jump Hosts]] for how those methods are used.

=====New Style SSH Agent Destination Constraints=====

From 8.9 onward, [http://man.openbsd.org/ssh-agent.1 ssh-agent(1)] will allow the agent to limit which hosts they will use for authentication as specified by [http://man.openbsd.org/ssh-add.1 ssh-add(1)] using the '''-h''' option.  These constraints have been added through two agent protocol extensions and a modification to the public key authentication protocol.  This feature may evolve, but for now the result is such that keys for account authentication can be loaded into the agent in four ways:

* no limits on forwarding (not recommended)
* local use only, these will not get forwarded
* forwarding, but only to specific remote hosts
* forwarding to specific remote hosts via specified routes

The intent is that the restrictions fail safely so that they do not allow authentication when one or more hosts in the route lack the needed protocol features.  The destinations and routes cannot be modified once the keys are loaded, but multiple routes to the same destination can be loaded and the routes can be any number of hops.  If the routes need changing, then the key must be reloaded into the agent with the new route or routes.  

The general default for the client is to keep keys in the agent for local use only.  However, that can be enforced explicitly by adding the '''-a''' option when starting the client or else setting the '''ForwardAgent''' directive in [http://man.openbsd.org/ssh_config.5 ssh_config(5)] to 'no' in the relevant configuration block.  

In order to load keys for unlimited forwarding, which is not the best idea, just add them using [http://man.openbsd.org/ssh-add.1 ssh-add(1)] as normal.  Then use the '''-A''' option with the client or set the '''ForwardAgent''' directive in [http://man.openbsd.org/ssh_config.5 ssh_config(5)] to 'yes' in the relevant configuration block.  

In order to limit keys for connection only to a specific remote host, or to load keys for connection to a specific remote host with forwarding via one or more intermediate hosts, use the '''-h''' option when loading keys into the agent.  Here the one key may be used only to connect to the specific destination:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-agent -h server.example.org server.key.ed25519
&lt;/syntaxhighlight&gt;

If an intermediate system is passed through, the best way is to use '''ProxyJump''' which is the '''-J''' option for the SSH Client.  If agent forwarding must be allowed then the tightest way is to constrain which systems may use the keys, again using the '''-h''' option.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-agent -h middle.example.org -h &quot;middle.example.org&gt;server.example.org&quot; server.key.ed25519
&lt;/syntaxhighlight&gt;

Multiple steps can be included, even multiple routes.  They just have to be enumerated explicitly, though patterns may still be used for the destination hosts as well as specific names.  Each host in the chain must support these protocol extensions for the connection to complete.  

Any keys designated for forwarding are unusable for authentication on any other hosts than those which have been explicitly identified for forwarding.  These permitted hosts are identified by host key or host certificate from the '''known_hosts''' file or another file designated by the '''-H''' option when loading the key with [http://man.openbsd.org/ssh-add.1 ssh-add(1)].  If '''-H''' is not used at the time the keys are loaded into the agent, then the default known hosts file(s) will be used: '''~/.ssh/known_hosts''', '''/etc/ssh/ssh_known_hosts''', '''~/.ssh/known_hosts2''', and '''/etc/ssh/ssh_known_hosts2'''.

In the case of keys, the '''known_hosts''' list must be maintained conscientiously &lt;ref name=&quot;ssh-agent-restrictions&quot;&gt;{{ cite web | author=Damien Miller|url=https://www.openssh.org/agent-restrict.html | title=SSH agent restriction | publisher=OpenSSH | date=2021-12-16|accessdate=2022-03-06}}&lt;/ref&gt;, perhaps with the help of the '''UpdateHostkeys''' and '''CanonicalizeHostname''' client configuration directives.  Use of certificates requires the agent to only need to be aware of the Certificate Authority (CA).

Again, see [[OpenSSH/Cookbook/Proxies_and_Jump_Hosts#Jump_Hosts_--_Passing_Through_a_Gateway_or_Two | Passing Through a Gateway or Two]] in the section on jump hosts about a way to pass through one or more intermediate machines without needing to forward an SSH agent.

====Checking the Agent for Specific Keys====

The [http://man.openbsd.org/ssh_add ssh_add(1)] utility's '''-T''' option can test whether a specific private key is available in the agent or not by looking up the matching public key.  That can be useful in a shell script.

&lt;syntaxhighlight lang=&quot;shell&quot;&gt;
#!/bin/sh

key=/home/fred/.ssh/some.key.ed25519.pub

if ssh-add -T ${key}; then
        echo &quot;Key ${key} Found&quot;
else
        echo &quot;Key ${key} missing&quot;
fi
&lt;/syntaxhighlight&gt;

Or it could be done with an alternate syntax just as well either in a script or in an interactive shell sessions,

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ key=/home/fred/.ssh/some.key.ed25519.pub
$ ssh-add -T ${key} &amp;&amp; echo &quot;Key found&quot; || echo &quot;Key missing&quot;
&lt;/syntaxhighlight&gt;

However, if the desired result would be to add key to the agent then the '''AddKeysToAgent''' client configuration option can ensure that a specific key is added to the SSH agent upon first use during any given login session.  That can be done using '''-o AddKeysToAgent=yes''' as a run-time argument, or by modifying [http://man.openbsd.org/ssh_config ssh_config(5)] as appropriate:

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Host www
        HostName www.example.com
        IdentityFile %d/.ssh/www.ed25519
        IdentitiesOnly yes
        AddKeysToAgent yes
&lt;/syntaxhighlight&gt;

With those options in the configuration file, the first time &lt;code&gt;ssh www&lt;/code&gt; is run the specified key will get added to the agent and remain available.

===Key-based Authentication Using A Hardware Security Token===

While stand-alone keys have been around for a long time, it has been possible since version 8.2 to use keys backed by hardware security tokens, such as OnlyKey, Yubikey, or many others, though the FIDO2 protocol.  The Universal 2nd Factor (U2F) authentication is supported directly in OpenSSH through FIDO2 and does not need third party software.  At the moment there are two types of hardware backed keys, ECDSA-SK and Ed25519-SK, but only the latest hardware tokens support the latter.  If the key Ed25519-SK format is not supported by the token's firmware, then the following error message will be presented when attempts to use that key type are made:

&lt;syntaxhighlight lang=&quot;text&quot;&gt;
Key enrollment failed: invalid format
&lt;/syntaxhighlight&gt; 

If supported, either key type can be created with [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)].  The steps are almost identical to creating normal keys but the token must be available to the system (plugged in) first.  Then if called for, the token's PIN must be entered and the token touched or otherwise activated.  After that, the key creation proceeds as normal.  Mind the key type as specified by the '''-t''' option.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -t ed25519-sk -f /home/fred/.ssh/server.ed25519-sk -C &quot;web server for fred&quot;
Generating public/private ed25519-sk key pair.
You may need to touch your authenticator to authorize key generation.
Enter passphrase (empty for no passphrase): 
Enter same passphrase again: 
Your identification has been saved in /home/fred/.ssh/server.ed25519-sk
Your public key has been saved in /home/fred/.ssh/server.ed25519-sk.pub
The key fingerprint is:
SHA256:41wVVDnKJ9gKr2Sj4CFuYMhcNvYebZ6zq0PWyP4rRDo web server
The key's randomart image is:
+[ED25519-SK 256]-+
|           .o... |
|             .o  |
|           +.. . |
|   = .  . ..= .  |
|+ + * + So.. o   |
|o+.EoO *+oo      |
|.o oBo+++o       |
|  o .=.+.        |
| .   .===        |
+----[SHA256]-----+
&lt;/syntaxhighlight&gt;

Once created, the public and private key files get handled like with any other type of key.  But when authenticating, the hardware token must be present and activated when called for.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -i /home/fred/.ssh/server.ed25519-sk server.example.org
Enter passphrase for key '/home/fred/.ssh/server.ed25519-sk': 
Confirm user presence for key ED25519-SK SHA256:41wVVDnKJ9gKr2Sj4CFuYMhcNvYebZ6zq0PWyP4rRDo
&lt;/syntaxhighlight&gt;

The resulting private key file is not actually the key itself but instead a &quot;key handle&quot; which is used by the hardware security token to derive the real private key on demand at the time it is actually used&lt;ref name=&quot;OpenBSD_tech_U2F_FIDO&quot;&gt;{{cite web |url=https://marc.info/?l=openbsd-tech&amp;m=157376801917387&amp;w=2 |title=OpenSSH U2F/FIDO support in base 
|publisher=OpenBSD-Tech Mailing List | date=2019-11-14
|accessdate=2021-03-24}}&lt;/ref&gt;.  As a result, the hardware-backed private key file is useless without the accompanying hardware token.  This also means that these key files are not portable across hardware tokens, say when having multiple tokens in reserve or as backup, even when used by the same account.  So when multiple hardware tokens are in use, different key pairs must be generated for each token.

====Hardware Security Token Resident Private Key====

It is possible to store the private key within the token itself, but for the moment it cannot be used directly from inside the token and must first be saved as a file.  Also, the key can only be loaded into the FIDO authenticator at the time of creation  using the '''-O resident''' option with [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)].  Otherwise, the process is the same as above.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -O resident -t ed25519-sk -f /home/fred/.ssh/server.ed25519-sk -C &quot;web server for fred&quot;
. . .
&lt;/syntaxhighlight&gt;

When needed, the resident key can be extracted from the FIDO2 hardware token and saved into a file using the '''-K''' option.  At this stage a passphrase can be added to the file, but no passphrase is kept within the token itself, only an optional PIN protects the key there.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -K
Enter PIN for authenticator: 
Enter passphrase (empty for no passphrase): 
Enter same passphrase again: 
Saved ED25519-SK key to id_ed25519_sk_rk

$ mv -i id_ed25519_sk_rk /home/fred/.ssh/server.ed25519-sk
&lt;/syntaxhighlight&gt;

Since the output file name is fixed, any pre-existing file with that name can get overwritten but there will be a warning first.  However, it is not recommended to keep the key on the hardware token because it provides more protection when kept separately.

==Single-purpose Keys==

Tailored single-purpose keys can eliminate use of remote root logins for many administrative activities.  A  finely tailored '''sudoers''' is needed along with an unprivileged account.  When done right, it gives just enough access to get the job done, following the security principle of Least Privilege.  

Single-purpose keys are accompanied by use of either the '''ForceCommand''' directive in [http://man.openbsd.org/ssh_config.5 sshd_config(5)] or the '''command=&quot;...&quot;''' directive inside the '''authorized_keys''' file.  The method is to generate a new key pair, transfer the public key to '''authorized-keys''' on the remote system, and then prepend the appropriate command or script there to the line with the key.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ grep '^command' ~/.ssh/authorized_keys
command=&quot;/usr/local/bin/somescript.sh&quot; ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIEcgdzDvSebOEjuegEx4W1I/aA7MM3owHfMr9yg2WH8H
&lt;/syntaxhighlight&gt;

The '''command=&quot;...&quot;''' directive inserted there overrides everything else and ensures that when logging in with just that key only the script '''/usr/local/bin/somescript.sh''' is run.  If it is necessary to pass parameters to the script, have a look at the contents of the '''SSH_ORIGINAL_COMMAND''' environment variable and use it in a case statement.  Do not ever trust the contents of that variable nor use the contents directly, always indirectly.  

Single-purpose keys are useful for allowing only a tunnel and nothing more.  The following key will only echo some text and then exit, unless used non-interactively with the '''-N''' option.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ grep '^command' ~/.ssh/authorized_keys
command=&quot;/bin/echo do-not-send-commands&quot; ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIBzTIWCaILN3tHx5WW+PMVDc7DfPM9xYNY61JgFmBGrA 
&lt;/syntaxhighlight&gt; 

No matter what the user tries while logging in with that key, the session will only echo the given text and then exits.  Using the '''-N''' option disables running the remote program, allowing the connection to stay open, allowing a tunnel. 

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -L 3306:localhost:3306 \
	-i ~/.ssh/tunnel_ed25519 \
	-N \
	-l fred \
	server.example.com
&lt;/syntaxhighlight&gt;

That creates a tunnel and stays connected despite a key configuration which would close an interactive session.  See also the '''-n''' or '''-f''' option for [http://man.openbsd.org/ssh.1 ssh(1)].  

===Single-purpose Keys to Avoid Remote Root Access===

The easy way is to write a short shell script, place it '''/usr/local/bin/''', and then configure '''sudoers''' to allow the otherwise unprivileged account to run just that script and only that script.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
%wheel  ALL=(root:root) NOPASSWD: /usr/sbin/service httpd stop
%wheel  ALL=(root:root) NOPASSWD: /usr/sbin/service httpd start
&lt;/syntaxhighlight&gt;

Then the key calls the script using '''command=&quot;...&quot;''' inside '''authorized_keys'''.  Here the one key starts the web server, the other stops the web server.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ grep '^command' ~/.ssh/authorized_keys
command=&quot;/usr/bin/sudo /usr/sbin/service httpd stop&quot; ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIEcgdzDvSebOEjuegEx4W1I/aA7MM3owHfMr9yg2WH8H
command=&quot;/usr/bin/sudo /usr/sbin/service httpd start&quot; ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMidyqZ6OCvbWqA8Zn+FjhpYE6NoWSxVjFnFUk6MrNZ4
&lt;/syntaxhighlight&gt;

Complicated programs like [http://linux.die.net/man/1/rsync rsync(1)], [http://man.openbsd.org/tar.1 tar(1)], [http://linux.die.net/man/1/mysqldump mysqldump(1)], and so on require an advanced approach when building a single-purpose key.  For them, the '''-v''' option can show exactly what is being passed to the server so that '''sudoers''' can be set up correctly.  That way they can be restricted to only access designated parts of the file system.  For example, here is what &lt;code&gt;ssh -v&lt;/code&gt; shows from one particular usage of [http://linux.die.net/man/1/rsync rsync(1)], note the &quot;Sending command&quot; line:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ rsync -e 'ssh -v' fred@server.example.org:/etc/ ./backup/etc/
. . .
debug1: Sending command: rsync --server --sender -e.LsfxC . /etc/
. . .
&lt;/syntaxhighlight&gt;

That output can then be added to '''sudoers''' so that the key can do only that function.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
%backup ALL=(root:root) NOPASSWD: /usr/bin/rsync --server --sender -e.LsfxC . /etc/
&lt;/syntaxhighlight&gt;

Then to tie it all together, the account &quot;backup&quot; needs a key:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ grep '^command' ~/.ssh/authorized_keys
command=&quot;/usr/bin/rsync --server --sender -e.LsfxC . /etc/&quot; ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMm0rs4eY8djqBb3dIEgbQ8lmdlxb9IAEuX/qFCTxFgb 
&lt;/syntaxhighlight&gt;

Many of these programs have a '''--dry-run''' or equivalent option.  Remember to use it when figuring out the right settings.

===Read-only Access to Keys===

In some cases it is necessary to prevent accounts from being able to changing their own authentication keys.  However, such situations may be a better case for using certificates.  However, if done with keys it is accomplished by putting the key file in an external directory where the user has read-only access, both to the directory and to the key file.  Then the '''AuthorizedKeysFile''' directive assigns where [http://man.openbsd.org/sshd.8 sshd(8)] looks for the keys and can point to a secured location for the keys instead of the default location.

A good alternate location could be a new directory '''/etc/ssh/authorized_keys''' which could store the selected accounts' key files there.  The change can be made to apply to only a group of accounts by putting the settings under a '''Match''' directive.  The default location for keys on most systems is usually '''~/.ssh/authorized_keys'''.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Match Group sftpusers
	AuthorizedKeysFile /etc/ssh/authorized_keys/%u
&lt;/syntaxhighlight&gt;

Then the permissions there would allow the keys to be read but not written:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ls -dhln /etc/ssh/
drwxr-x--x 3 0 0 4.0K Mar 30 22:16 /etc/ssh/authorized_keys/

$ ls -dhln /etc/ssh/*.pub
-rw-r--r-- 1 0 0 173 Mar 23 13:34 /etc/ssh/fred
-rw-r--r-- 1 0 0  93 Mar 23 13:34 /etc/ssh/user1
-rw-r--r-- 1 0 0 565 Mar 23 13:34 /etc/ssh/user2
. . .
&lt;/syntaxhighlight&gt;

The keys could even be within subdirectories, though the same restrictions apply regarding permissions and ownership.  

For chrooted SFTP, the method is the same to keep the key files out of reach of the accounts:  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Match Group sftpusers
	ChrootDirectory /home
	ForceCommand internal-sftp -d %u
	AuthorizedKeysFile /etc/ssh/authorized_keys/%u
&lt;/syntaxhighlight&gt;

Of course a '''Match''' directive is not essential.  The settings could be made to apply to all accounts by putting the directive in the main part of the server configuration file instead.

==Mark Public Keys as Revoked==

Keys can be revoked.  Keys that have been revoked can be stored in '''/etc/ssh/revoked_keys''', a file specified in [http://man.openbsd.org/ssh_config.5 sshd_config(5)]  using the directive '''RevokedKeys''', so that [http://man.openbsd.org/sshd.8 sshd(8)] will prevent attempts to log in with them.  No warning or error on the client side will be given if a revoked key is tried.  Authentication will simply progress to the next key or method.

The revoked keys file should contain a list of public keys, one per line, that have been revoked and can no longer be used to connect to the server.  The key cannot contain any extras, such as [[OpenSSH/Client_Configuration_Files#Available_key_login_options | login options]] or it will be ignored. If one of the revoked keys is tried during a login attempt, the server will simply ignore it and move on to the next authentication method.  An entry will be made in the logs of the attempt, including the key's fingerprint.  See the section on [[OpenSSH/Logging_and_Troubleshooting | logging]] for a little more on that.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
RevokedKeys /etc/ssh/revoked_keys
&lt;/syntaxhighlight&gt;

The '''RevokedKeys''' configuration directive is not set in [http://man.openbsd.org/ssh_config.5 sshd_config(5)] by default.  It must be set explicitly if it is to be used.  This is another situation that might be better fulfilled through using certificate since a validity interval can be set in any combination of seconds, minutes, hours, days, or weeks can be set for certificates while keys are valid indefinitely.  

===Key Revocation Lists===

A Key Revocation List (KRL) is a compact, binary form of representing revoked keys and certificates.  In order to use a KRL, the server's configuration file must point to a valid list using the '''RevokedKeys''' directive.  KRLs themselves are generated with [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)] and can be created from scratch or edited in place.  Here a new one is made, populated with a single public key: 

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -k -f /etc/ssh/revoked_keys -z 1 ~/.ssh/old_key_rsa.pub
&lt;/syntaxhighlight&gt;

Here an existing KRL is updated by adding the '''-u''' option:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -u -k -f /etc/ssh/revoked_keys -z 2 ~/.ssh/old_key_dsa.pub
&lt;/syntaxhighlight&gt;

Once a KRL is in place, it is possible to test if a specific key or certificate is in the revocation list.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -Q -f /etc/ssh/revoked_keys ~/.ssh/old_key_rsa.pub
&lt;/syntaxhighlight&gt;

Only public keys and certificates will be loaded into the KRL.  Corrupt or broken keys will not be loaded and will produce an error message if tried.  Like with the regular '''RevokedKeys''' list, the public key destined for the KRL cannot contain any extras like login options or it will produce an error when an attempt is made to load it into the KRL or search the KRL for it.

==Verify a Host Key by Fingerprint==

The above examples have been about using keys to authenticate the client to the server.  A different context in which keys are used is when the server identifies itself to the client, which happens automatically at the beginning of each non-multiplexed session.  In order for that identification to happen the client acquires a public key from the server, usually on or prior to first contact, which it can subsequently use to ensure that it is connecting to the same server again and not an impostor.  The default locations for storing these acquired host keys on the client are in '''/etc/ssh/ssh_known_hosts''', if managed by the system administrator, or in '''~/.ssh/known_hosts''' if managed by the client's own account.  The format of the contents is a line with a host address and its matching public key.  The file is described in detail in the [http://man.openbsd.org/sshd.8 sshd(8)] manual page in the section &quot;SSH_KNOWN_HOSTS FILE FORMAT&quot;.

When connecting for the first time to a remote host, the server's host key should be verified in order to ensure that the client is connecting to the right machine and not an impostor or anything else.  Usually this verification is done by comparing the fingerprint of the server's host key rather than trying to compare the whole key itself.  By default the client will show the fingerprint if the key is not already found in the '''known_hosts''' register.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -l fred server.example.org
The authenticity of host 'server.example.org (192.0.32.10)' can't be established.
ECDSA key fingerprint is SHA256:LPFiMYrrCYQVsVUPzjOHv+ZjyxCHlVYJMBVFerVCP7k.
Are you sure you want to continue connecting (yes/no)? 
&lt;/syntaxhighlight&gt;

That can be compared to a fingerprint received out of band, say by post, e-mail, SMS, courier, and so on.  Specifically, the example represents the key's fingerprint as a base64 encoded SHA256 checksum.  That is the default style.  The fingerprint can also be displayed as an MD5 hash in hexadecimal instead by passing the client's '''FingerprintHash''' configuration directive as a runtime argument or setting it in [http://man.openbsd.org/ssh_config.5 ssh_config(5)].  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -o FingerprintHash=md5 host.example.org
The authenticity of host 'host.example.org (192.0.32.203)' can't be established.
RSA key fingerprint is MD5:10:4a:ec:d2:f1:38:f7:ea:0a:a0:0f:17:57:ea:a6:16.
Are you sure you want to continue connecting (yes/no)?
&lt;/syntaxhighlight&gt;

But the default in new versions is SHA256 in base64 has a lower chance of collision.

In OpenSSH 6.7 and earlier, the client showed fingerprints as a hexadecimal MD5 checksum instead a of the base64-encoded SHA256 checksum currently used:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -l fred server.example.org
The authenticity of host 'server.example.org (192.0.32.10)' can't be established. 
RSA key fingerprint is 4a:11:ef:d3:f2:48:f8:ea:1a:a2:0d:17:57:ea:a6:16. 
Are you sure you want to continue connecting (yes/no)? 
&lt;/syntaxhighlight&gt;

Another way of comparing keys is to use the ASCII art visual host key.  See further below about that.  

===Downloading keys===

Even though a host’s key is usually displayed for review the first time the SSH client tries to connect, it can also be fetched on demand at any time using [http://man.openbsd.org/ssh-keyscan.1 ssh-keyscan(1)]:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keyscan server.example.org
# server.example.org:22 SSH-2.0-OpenSSH_10.6
server.example.org ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBEWKepJgkC2XTG5cAr2Nyew6hOp5AjG7vi2RYFtPWqN3bo5XGuCX2d2YVyn++/2PtyMYBaKWyFpCNTT9X0F1Epg=
# server.example.org:22 SSH-2.0-OpenSSH_10.6
server.example.org ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQDKyERe8k+fnsrt4JrcLD3AW0kXj90r9ybrEZuY/CTrXIqYSizO335SxGJoWrKijaRy8htuueMkmNfxxhnBPoAjul/4T/FCRGKaV0jC96xYNnKcXbnXxSLVQ0OW2EIPvQhw/TU/G3vEqtiRYGyaNcZS6xrnVv3xuPuvVC1VRKspNLEq7zfvToC0OB89X5DIbvBbHY13PjJ0NrDdX3sSA8lxPsYagBuDIvyxH0S4Z5fQHeYrdvENS5zX6LwJeMeGSOqDuD0Zb4hpKxhaGVwP5e435VcFuImbFaDPM4w71PzaSUEj+tnUA0mGDoLiCrpW3txkJszog9lN3C/nLGghFaT7ajrfH55qut81JnvdhMju9+SzxrKPJmtQZfKVLIc4whEbtFsPCdm2bstz7ROWxTJ3t/Vr8/QVm2G2aY4FHuPwo2jUQDbQA7mCV+fe1sADy2jLzGhn1TCeYvWSv5PNJAT97IrLfD3+0Uo+qJD/6CU7F8oabj1Ql2H8fPN5kGSWfkM=
# server.example.org:22 SSH-2.0-OpenSSH_10.6
server.example.org ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIJo5gc4VrxVQ5apAOd7qK6UqGlLMpWOPuunjB53JBN2s
# server.example.org:22 SSH-2.0-OpenSSH_10.6
# server.example.org:22 SSH-2.0-OpenSSH_10.6
# server.example.org:22 SSH-2.0-OpenSSH_10.6
server.example.org ssh-mldsa44-ed25519 AAAAE3NzaC1tbGRzYTQ0LWVkMjU1MTkAAAVAyIw5r9FaniSYqBX0yd9vgBz5nCkebaQlMQN9N0p//Ukfn/CnZ3YtZWn6pUGjDM85/bqdL1gqah1OLfnl1eHk0qvTACrym07uKaMLoEHuakIXHbTi/ELPRoRP3F+DpEgjtYSjLc/fJiobRMgSvmLJxTUzZTStsqWAL1L9/1zuwHEngR+THpUcCSTi6KKkYcQiWGOFwpO22VdiuOg+zdQSH+9jW6eXYk1z81KU6UlHZps8zVrlqCd3FDDghgbH5U8DcGN2t6GvVfn6jFjpEk0ouj0of3/7010eRXjnv3QSbprCpMq73lAemQM+3LvTtrMBhFWNhCXhyOHfO1Yq7c8xaOwlFK78PlERjdHTvVJaCaDFDy7Pg9I+wxv+uC+W0wtzJ2S1y9XCYUgJo9yEiIGuSZdhMkYUwMnXLzQMm44hQOW153pdlHWze3kESCLg/LJf9RbUoSB43t6rghSHEiUkIi5TtCtFZ4nAGeH+wVwlB9Fwog5uZuJN1FYuuY5sSrLHJAQDUwudkdak0ifOhtPtsM/ClYr3baolQ/qi0ABYUVLKSV5b+A5DlTXa23zc7JAXm2YVfkWpOfVJG4TY81wrJoDumsd1y3XaH28/4QbADsZCE3wYsBou8ff0xKgPu8xm2K+sYSmzUbBGprArAQA0LtIDGNGqrb4JsZ1ru+viwzfSlxV7Nz7ZrSw6h+Ddq4J9A6oKXy6YS3uf1GFOtBQm6JfuyMHQEEUtYZrU4UK3C/fKHx9vjuw7YdhsL8JRgxbF14qJLFizkmVbK2e6aWEE4iCqLLLlZ0dC2peYUUqyGb9PsW7sewYzGbipzPpQ/GobRT3Obc3Gmu8P386pDGR7hmkOpFmVwIcfc431cUmZixK7CkPxzUvfaAAQkmNs/p4eNNoP0gq/xPGsV14/heULbWp/njGWk1ysjjGxP6YMwHcEZpUdSGbD05zbL0KkMtmKsr8yuJYjdVAgtH2bVAvrxXRXLgavmm97VYYq1A9rOYiQFlMrKRg6yZhT10Xt8Hukf6ySLk+fieFc3nH99YeysoA5rsfp9kdXr65GpwrBerZlf/20ZLJ7s4xaYb9SukR/8tiPt9iAVQjqPdb0MseZVrzhKo/jK44JHbHejHMoMMs7etPAS5TIjHxcJTP66B3eO9A0l2fAage2ka7ehTnHivxD3EE9KnqYBjIHDU7o6dTrX7UyQsdhax9bPKEL7OEtm6hXXfwzy4GdqGi124BclFAF0LeBSvBUgmSKIn3wfzJx/XXbt512eOn3WZk2v0TsiteH9kPEgDxVkUykawg2tleak9rTFMzYpDZRHvZD7uHWUZ8ktr2FEKWgq7/1Q2c80Z6H75VK9l1d3KZuoiWoF1s73R7ZAM+CWSrR+S5h+3AhYubDKPa/af+Lnlqe6ocVTqQPYaaRz25/cLBg6pgbdh18Ru6h3ljG2KiysyXeuoEoM5xVYtdIW7l9NeKDpGbZPAOqywXUpK+UCGjumIl7c48KCTIYcdtolnEbfVNBh0LRuftcVI+uF9cvQ0XacaNbgkYJYCjv4VR/n58EJ1b0c7tQBrVqMjDjIUKGhCMQqAeD3g75jeD60bBmVNPrq8RK+zH5VIa5eaBs3eitN98eVzd4b6UYTQd1QxLQZMrhQf4InRj39TZfGvQR5SXlLZQlweVHYkMps3IKbs3B3DCqlWCPUAnTAJBAG7HqWEYr5uEaKBawBSAx9jCQz00T+bp8KXpkOPzZCD6dfEfpHY6Rv6kmGJkiPUCb2hoX145HrS357G12+wDxKLN833oPVC0z
&lt;/syntaxhighlight&gt;

Once a key is acquired, its fingerprint can be shown using [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)] to read from '''stdin'''.  This can be done directly with a pipe.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keyscan server.example.org | ssh-keygen -l -f -
3072 SHA256:tQlw3vy325KrQibndP3gLS/YXUZjTLVA5yDFpg/Bb6I server.example.org (RSA)
256 SHA256:snnAtb/9csdy0BGhPjdg+VNWqN5bxCa/ge4C6zZ8muk server.example.org (ECDSA)
256 SHA256:agRZDZn8awhQ+tc19Ip/whkHoV33Ln2REO7v1kcYbdU server.example.org (ED25519)
512 SHA256:3Wdc6GbLIcc5mbuF2mhhokhARdMLuMK+ESRfJ+sM0QE server.example.org (MLDSA44-ED25519)
&lt;/syntaxhighlight&gt;

If there is more than one public key type is available from the server on the port polled, then [http://man.openbsd.org/ssh-keyscan.1 ssh-keyscan(1)] will fetch each of them.  If there is more than one key fed via '''stdin''' or a file, then [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)] will process them in order.  Prior to OpenSSH 7.2 manual fingerprinting was a two step process, the key was read to a file and then processed for its fingerprint.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keyscan -t ed25519 host.example.org &gt; key.pub
# host.example.org SSH-2.0-OpenSSH_6.8
$ ssh-keygen -lf key.pub                       
256 SHA256:ZmS+IoHh31CmQZ4NJjv3z58Pfa0zMaOgxu8yAcpuwuw host.example.org (ED25519)
&lt;/syntaxhighlight&gt;

Note that some output from [http://man.openbsd.org/ssh-keyscan.1 ssh-keyscan(1)] is sent to '''stderr''' instead of '''stdout'''.  

A hash, or fingerprint, can be generated manually with [http://linux.die.net/man/1/awk awk(1)], [http://linux.die.net/man/1/sed sed(1)] and [http://linux.die.net/man/1/xxd xxd(1)], on systems where they are found.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ awk '{print $2}' key.pub | base64 -d | md5sum -b | sed 's/../&amp;:/g; s/: .*$//'
$ awk '{print $2}' key.pub | base64 -d | sha256sum -b | sed 's/ .*$//' | xxd -r -p | base64 
&lt;/syntaxhighlight&gt;

It is possible to find all hosts from a file which have new or different keys from those in '''known_hosts''', if the host names are in clear text and not stored as hashes.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keyscan -t ed25519,mldsa44-ed25519 -f ssh_hosts | \
  sort -u - ~/.ssh/known_hosts | \
  diff ~/.ssh/known_hosts -
&lt;/syntaxhighlight&gt;

====Using ssh-keyscan(1) with ssh_config(5)====

The utility [http://man.openbsd.org/ssh-keyscan.1 ssh-keyscan(1)] does not parse [http://man.openbsd.org/ssh_config.5 ssh_config(5)].  That is in part to keep the code base simple.  There are a lot of configuration options which would be complicated to implement, including but not limited to '''ProxyJump''', '''ProxyCommand''', '''Match''', '''BindInterface''', and '''CanonicalizeHostname'''&lt;ref name=&quot;keyscan&quot;&gt;{{cite mailing list |url=https://lists.mindrot.org/pipermail/openssh-unix-dev/2023-March/040605.html | title=Why does ssh-keyscan not use .ssh/config? |publisher=mindrot.org | access-date=2023-03-01 | date=2023-03-01 | mailing-list=OpenSSH UNIX-dev | first=Damien | last=Miller }}&lt;/ref&gt; .  Resolving host names via the client configuration file can be done by wrapping the utility in a short shell function:

&lt;syntaxhighlight lang=&quot;shell&quot;&gt;
my-ssh-keyscan() {
	for host in &quot;$@&quot; ; do
		ssh-keyscan $(ssh -G &quot;$host&quot; | awk '/^hostname/ {print $2}')
	done
}
&lt;/syntaxhighlight&gt;

That shell function uses the '''-G''' option of [http://man.openbsd.org/ssh.1 ssh(1)] to resolve each host name using [http://man.openbsd.org/ssh_config.5 ssh_config(5)] and then check the resulting host name for SSH keys.

===ASCII Art Visual Host Key===

An ASCII art representation of the key can be displayed along with the SHA256 base64 fingerprint: 

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -l -v -f key 
256 SHA256:BClQBFAGuz55+tgHM1aazI8FUo8eJiwmMcqg2U3UgWU www.example.org (ED25519)
+--[ED25519 256]--+
|o+=*++Eo         |
|+o .+.o.         |
|B=.oo.  .        |
|*B.=.o .         |
|= B *   S        |
|. .@ .           |
| +..B            |
|  *. o           |
| o.o.            |
+----[SHA256]-----+
&lt;/syntaxhighlight&gt;

In OpenSSH 6.7 and earlier the fingerprint is in MD5 hexadecimal form.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -l -v -f key 
2048 37:af:05:99:e7:fb:86:6c:98:ee:14:a6:30:06:bc:f0 www.example.net (RSA) 
+--[ RSA 2048]----+ 
|          o      | 
|         o .     | 
|        o o      | 
|       o +       | 
|   .  . S        | 
|    E ..         | 
|  .o.* ..        | 
|  .*=.+o         | 
|  ..==+.         | 
+-----------------+ 
&lt;/syntaxhighlight&gt;

==More on Verifying SSH Keys==

Keys on the client or the server can be verified against known good keys by comparing the base64-encoded SHA256 fingerprints.  

===Verifying Stray Client Keys===

Sometimes is is necessary to compare two uncertain key files to check if they are part of the same key pair.  However, public keys are more or less disposable.  So the easy way in such situations on the client machine is to just rename or erase the old, problematic, public key and replace it with a new one generated from the existing private key.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -y -f ~/.ssh/my_key_ed25519
&lt;/syntaxhighlight&gt;

But if the two parts must really be compared, it is done in two steps using [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)].  First, a new public key is re-generated from the known private key and used to make a fingerprint to '''stdout'''.  Next, the fingerprint of the unknown public key is generated for comparison.  In this example, the private key '''my_key_a_ed25519''' and the public key '''my_key_b_ed25519.pub''' are compared:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -y -f my_key_a_ed25519 | ssh-keygen -l -f -
$ ssh-keygen -l -f my_key_b_ed25519.pub
&lt;/syntaxhighlight&gt;

The result is a base64-encoded SHA256 checksum for each key with the one fingerprint displayed right below the other for easy visual comparison.  Older versions don't support reading from '''stdin''' so an intermediate file will be needed then.  Even older versions will only show an MD5 checksum for each key.  Either way, automation with a shell script is simple enough to accomplish but outside the scope of this book.

===Verifying Server Keys===

Reliable verification of a server's host key must be done when first connecting.  It can be necessary to contact the system administrator who can provide it out of band so as to know the fingerprint in advance and have it ready to verify the first connection.  

Here is an example of the server's Ed25519 key being read and its fingerprint shown as SHA256 base64:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -l -f /etc/ssh/ssh_host_ed25519_key.pub 
256 SHA256:bFzzouaWmE5HuZIv+YnGUYI2q06i6M43V+6jMU3LHpA root@server.example.org (ED25519)
&lt;/syntaxhighlight&gt;

And here the corresponding ECDSA key is read, but shown as an MD5 hexadecimal hash:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -E md5 -l -f /etc/ssh/ssh_host_ecdsa_key.pub
256 MD5:ed:d2:34:b4:93:fd:0e:eb:08:ee:b3:c4:b3:4f:28:e4 root@server.example.net (ECDSA)
&lt;/syntaxhighlight&gt;

Prior to 6.8, the fingerprint was expressed as an MD5 hexadecimal hash:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -l -f /etc/ssh/ssh_host_rsa_key.pub 
2048 MD5:e4:a0:f4:19:46:d7:a4:cc:be:ea:9b:65:a7:62:db:2c root@server.example.net (RSA)
&lt;/syntaxhighlight&gt;

It is also possible to use [http://man.openbsd.org/ssh-keyscan.1 ssh-keyscan(1)] to get keys from an active SSH server.  However, the fingerprints still needs to be verified out of band.  

====Warning: Remote Host Identification Has Changed!====

If a server's key does not match what the client finds has been recorded in either the system's or the local account's '''authorized_keys''' files, then the client will issue a warning along with the fingerprint of the suspicious key.  

&lt;pre&gt;
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the ED25519 key sent by the remote host is
SHA256:bFzzouaWmE5HuZIv+YnGUYI2q06i6M43V+6jMU3LHpA.
Please contact your system administrator.
Add correct host key in /home/fred/.ssh/known_hosts to get rid of this message.
Offending ED25519 key in /home/fred/.ssh/known_hosts:11
Host key for server.example.org has changed and you have requested strict checking.
Host key verification failed.
&lt;/pre&gt;

Three reasons for the warning are common.  

One reason is that the server's keys were replaced, often because the server's operating system was reinstalled without backing up the old keys.  Another reason can be when the system administrator has phased out deprecated or compromised keys.  However that can be planned better and if there is time to plan the migration, new keys can just be added to the server and have the clients use the '''UpdateHostKeys''' option so that the new keys are accepted if the old keys match.  A third situation is when the connection is made to the wrong machine, such as when the remote system changes IP addresses because of dynamic address allocation.  

In all three cases where the key has changed there is only one thing to do: contact the system administrator and verify the key.   Ask if the OpenSSH-server was recently reinstalled, or was the machine restored from an old backup?  Keep in mind that the system administrator may be you yourself in some cases. 

The case which is rather rare but serious enough that it should be ruled out for sure is that the wrong machine is part of a man-in-the-middle attack.

In all four cases, an authentic key fingerprint can be acquired by any method where it is possible to verify the integrity and origin of the message, for example via PGP-signed e-mail.  If physical access is possible, then use the console to get the right fingerprint.  Once the authentic key fingerprint is available, return to the client machine where you got the error and remove the old key from '''~/.ssh/known_hosts'''

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -R server.example.org
&lt;/syntaxhighlight&gt;

Then try logging in, but compare the key fingerprints first and proceed if and '''only''' if the key fingerprint matches what you received out of band.  If the key fingerprint matches, then go through with the login process and the key will be automatically added.  If the key fingerprint does not match, stop immediately and figure out what you are connecting to.  It would be a good idea to get on the phone, a real phone not a computer phone, to the remote machine's system administrator or the network administrator.

===Multiple Keys for a Host, Multiple Hosts for a Key in known_hosts===
 
Multiple host names or IP addresses can use the same key in the '''known_hosts''' file by using pattern matching or simply by listing multiple systems for the same key.  That can be done in either the global list of keys in '''/etc/ssh/ssh_known_hosts''' and the local, account-specific lists of keys in each account's '''~/.ssh/known_hosts''' file.  Labs, computational clusters, and similar pools of machines can make use of keys in that way.  Here is a key shared by three specific hosts, identified by name, one host per line:
&lt;pre&gt;
server1 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMIId09yQEh9634wNXR+y7L79th2M4awBgCwqWJobJuQ fred@desk.example.org
server2 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMIId09yQEh9634wNXR+y7L79th2M4awBgCwqWJobJuQ fred@desk.example.org
server3 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMIId09yQEh9634wNXR+y7L79th2M4awBgCwqWJobJuQ fred@desk.example.org
&lt;/pre&gt;
Or a range can be specified by using globbing to a limited extent in either '''/etc/ssh/ssh_known_hosts''' or '''~/.ssh/known_hosts'''.
&lt;pre&gt;
172.19.40.* ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMIId09yQEh9634wNXR+y7L79th2M4awBgCwqWJobJuQ fred@desk.example.org
&lt;/pre&gt;
Conversely, a pool of servers might have multiple keys for the same address.  In that case, it is necessary to make multiple entries in either '''/etc/ssh/ssh_known_hosts''' or '''~/.ssh/known_hosts''' for each key.
&lt;pre&gt;
server1 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMIId09yQEh9634wNXR+y7L79th2M4awBgCwqWJobJuQ fred@desk.example.org
server1 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIBrsIIaDl/bJ40vyprvF+HYAq+kE2jWUsOt+WqIheaBw fred@desk.example.org
server1 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIC2CgwWTPH/qZDeHmW7ZUea18wa9As7Txq3P5dXCfoXj fred@desk.example.org 
&lt;/pre&gt;
Thus in order to get a pool of servers to share a pool of keys, each server-key combination must be added manually to the '''known_hosts''' file:
&lt;pre&gt;
server1 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMIId09yQEh9634wNXR+y7L79th2M4awBgCwqWJobJuQ fred@desk.example.org
server1 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIBrsIIaDl/bJ40vyprvF+HYAq+kE2jWUsOt+WqIheaBw fred@desk.example.org
server1 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIC2CgwWTPH/qZDeHmW7ZUea18wa9As7Txq3P5dXCfoXj fred@desk.example.org 

server2 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAICPSs4OR2LT89mv2tM4TKqeVhh4XvoLQ77MSBmjyrMGm fred@desk.example.org
server2 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIHChTzAoJr53A7VP1BdMHqLTFK5cz/2Vc065+VcpP4VA fred@desk.example.org
server2 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIHP+4BvU4DzwYQgznARxx/qyBWmu49PAywHwDRgslRaM fred@desk.example.org
&lt;/pre&gt;

Though upgrading to certificates might be a more appropriate approach that manually updating lots of keys.

===Another way of Dealing with Dynamic (roaming) IP Addresses===
It is possible to manually point to the right key using '''HostKeyAlias''' either as part of [http://man.openbsd.org/ssh_config.5 ssh_config(5)]  or as a runtime parameter.  Here the key for machine ''Foobar'' is used to connect to host 192.168.11.15

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -o StrictHostKeyChecking=accept-new \
      -o HostKeyAlias=foobar   \
      192.168.11.15
&lt;/syntaxhighlight&gt;
This is useful when DHCP is not configured to try to keep the same addresses for the same machines over time or when using certain stdio forwarding methods to pass through intermediate hosts.

===Host Key Update and Rotation in known_hosts===

A protocol extension to rotate weak public keys out of '''known_hosts''' has been in OpenSSH from version 6.8&lt;ref name=&quot;djm_rotation&quot;&gt;
{{cite web
| title=Key rotation in OpenSSH 6.8+ 
| author=Damien Miller
| url=http://blog.djm.net.au/2015/02/key-rotation-in-openssh-68.html
| date=2015-02-01
| publisher=DJM's Personal Weblog
| accessdate=2016-03-05
}}
&lt;/ref&gt; and later.  With it the server is able to inform the client of all its host keys and update '''known_hosts''' with new ones when at least one trusted key already known.  This method still requires the private keys be available to the server &lt;ref name=&quot;djm_rotation_redux&quot;&gt;
{{cite web
| title=Hostkey rotation, redux 
| author=Damien Miller
| url=http://blog.djm.net.au/2015/02/hostkey-rotation-redux.html
| date=2015-02-17
| publisher=DJM's Personal Weblog
| accessdate=2016-03-05
}}
&lt;/ref&gt; so that proofs can be completed.  In [http://man.openbsd.org/ssh_config.5 ssh_config(5)], the directive '''UpdateHostKeys''' specifies whether the client should accept updates of additional host keys from the server after authentication is completed and add them to '''known_hosts'''.  A server can offer multiple keys of the same type for a period before removing the deprecated key from those offered, thus allowing an automated option for rotating keys as well as for upgrading from weaker algorithms to stronger ones.  See also [https://datatracker.ietf.org/doc/html/rfc4819 RFC 4819: Secure Shell Public Key Subsystem] about key management standards.

==Converting Between SSH Key Formats==

OpenSSH has its own format for keys which it uses by default when new keys are made.  However, other SSH clients and servers may use other formats such as [https://www.rfc-editor.org/rfc/rfc4716 RFC4716], [https://www.rfc-editor.org/rfc/rfc5958 PKCS8], or [https://www.rfc-editor.org/rfc/rfc1421 PEM].  Any of these can be converted to the default OpenSSH format by [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)].  The default to format to try to convert from is RFC4716.  The utility [https://linux.die.net/man/1/puttygen puttygen(1)] makes keys in that format for [https://linux.die.net/man/1/putty putty(1)] and they need conversion when used with OpenSSH's server.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -i -f /var/tmp/key_public.ppk
&lt;/syntaxhighlight&gt;

However, you can use the '''-m''' option to specify either that format explicitly or else choose another one to convert from.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -i -m RFC4716 -f /var/tmp/key_public.ppk
$ ssh-keygen -i -m PKCS8 -f /var/tmp/key_public.ppk
&lt;/syntaxhighlight&gt;

Both examples above are for importing public keys into OpenSSH's own format.  

By default OpenSSH will write newly-generated keys in its own format, so the '''-m''' option is obligatory to produce public keys in another format.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -e -m PKCS8 -f ~/.ssh/key.pub
&lt;/syntaxhighlight&gt;

It is not yet possible to export private keys from the OpenSSH format to one of the other formats using the '''-e''' option.  Even if a private key is specified as input, a public key is produced:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -e -m RFC4716 -f ~/.ssh/key
&lt;/syntaxhighlight&gt;

Not all key types are supported by all key formats.  

It is also possible to use export to display the key pair as a traditional hex dump.
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -e -m hexdump -f ~/.ssh/key
Enter passphrase for &quot;key&quot;: 
Public ED25519 key:
buffer len = 51
0000: 00 00 00 0b 73 73 68 2d 65 64 32 35 35 31 39 00  ....ssh-ed25519.
0016: 00 00 20 b0 c5 cc 2c cb d8 8b 8d 75 80 eb e6 e9  .. ...,....u....
0032: 2c f4 36 08 7b 5b ad ad 0b 54 4f 7f 21 9d 1b e8  ,.6.{[...TO.!...
0048: 9e e0 32                                         ..2

Private ED25519 key:
buffer len = 119
0000: 00 00 00 0b 73 73 68 2d 65 64 32 35 35 31 39 00  ....ssh-ed25519.
0016: 00 00 20 b0 c5 cc 2c cb d8 8b 8d 75 80 eb e6 e9  .. ...,....u....
0032: 2c f4 36 08 7b 5b ad ad 0b 54 4f 7f 21 9d 1b e8  ,.6.{[...TO.!...
0048: 9e e0 32 00 00 00 40 e1 c3 a2 4d d9 89 49 72 9b  ..2...@...M..Ir.
0064: 86 72 6c 07 17 1b 40 4f 62 50 62 45 4f 4c cf cf  .rl...@ObPbEOL..
0080: 57 8b 9d c0 04 8f 9b b0 c5 cc 2c cb d8 8b 8d 75  W.........,....u
0096: 80 eb e6 e9 2c f4 36 08 7b 5b ad ad 0b 54 4f 7f  ....,.6.{[...TO.
0112: 21 9d 1b e8 9e e0 32                             !.....2
&lt;/syntaxhighlight&gt;

&lt;noinclude&gt;

== References ==
{{reflist}}
{{OpenSSH/TOC|mini}}
&lt;/noinclude&gt;
{{BookCat}}
{{status|100%}}</text>
      <sha1>lo1bfmh4qqrrwfpwj3zkdoy4ewapbvt</sha1>
    </revision>
  </page>
  <page>
    <title>Radiation Oncology/Prostate/Workup</title>
    <ns>0</ns>
    <id>68119</id>
    <revision>
      <id>4675801</id>
      <parentid>1883899</parentid>
      <timestamp>2026-10-13T07:58:06Z</timestamp>
      <contributor>
        <username>Jcb</username>
        <id>90773</id>
      </contributor>
      <origin>4675801</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2345" sha1="cn45te1bcdxxpwt99xn8ppf1jluhymr" xml:space="preserve">{{:Radiation Oncology/Prostate:TOC}}

==Endorectal Magnetic Resonance Imaging==
* On axial T1 gland appears homogeneous and the zonal anatomy is not well appreciated 
* Postbiopsy hemorrhage is evident on T1-weighted images as high T1 signal intensity (important because hemorrhage may mimic tumor on T2 and greatly interferes with assessment of ECE)
* zonal anatomy is best seen on axial and coronal T2 as are the vas deferens and SV
* neurovascular bundles best seen on axials 
* penile root is better imaged on T2 coronals
* peripheral zone is hyperintense whereas tumor appears is HYPOINTENSE (other causes of low T2: hemorrhage, prostatitis, hormone treatment, and RT)
* Hemorrhage: high T1, low T2 


==Bone Metastases Detection==
*'''Brussels, 2007''' (Belgium) {{PMID|17664475}} -- &quot;Magnetic resonance imaging of the axial skeleton for detecting bone metastases in patients with high-risk prostate cancer: diagnostic and cost-effectiveness and comparison with current detection strategies.&quot; (Lecouvet FE, J Clin Oncol. 2007 Aug 1;25(22):3281-7.)
**Prospective. 66 patients with high-risk PCA (newly diagnosed PCA with GS &gt;=8 and PSA &gt;=20; PSA recurrence after RP with PSADT &lt;12 months; on ADT and PSADT &lt;12 months). Evaluated by bone scan + targetedplain films (BS/TXR) vs. bone scan + targeted plain films + MRI-on request (BS/TXR/MRIor) vs. axial MRI (MRIas)
**Outcome: 62% bone mets. MRIas more sensitive than current sequence of sequential workup (bone scan, targeted XR, MRI of area at risk)

==Role of Bone Scan==
*&quot;&quot;Columbia University, 2000&quot;&quot; {{PMID|11121646}} -- &quot;Which patients with newly diagnosed prostate cancer need a radionuclide bone scan? An analysis based on 631 patients&quot; (Lee, N, Int J Radiat Oncol Biol Phys. 2000 vol. 48 (5) pp. 1443-6)
**Retrospective review of 631 consecutive patients treated at Columbia Presbyterian Medical Center between 1990-1996 who had both a Gleason score and a bone scan.  Reviewed clinical factors associated with positive bone scan.
**Results: 14% with positive bone scan. Multivariate analysis: only Gleason 8-10, PSA&gt;50, and clinical T-category &gt;T2b predicted positive bone scan. All 237 patients with Gleason 2-7, PSA&lt;15 and T-category&lt;T2b had negative scans.  1% of those with Gleason 2-7, PSA&lt;=50, &lt;=T2b had positive bone scan. In those with PSA&gt;50, 49.5% had positive bone scan.</text>
      <sha1>cn45te1bcdxxpwt99xn8ppf1jluhymr</sha1>
    </revision>
  </page>
  <page>
    <title>Macedonian/Numbers</title>
    <ns>0</ns>
    <id>78284</id>
    <revision>
      <id>4675756</id>
      <parentid>3332571</parentid>
      <timestamp>2026-10-12T17:52:06Z</timestamp>
      <contributor>
        <username>WereSpielChequers</username>
        <id>248949</id>
      </contributor>
      <comment>typo</comment>
      <origin>4675756</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1605" sha1="atqtxmom0mxjr6oe3ecdx2c7jp9vtgr" xml:space="preserve">The numbers in the macedonian language form one to ten are:

1 - еден   - Eden&lt;br&gt; 
2 - два    - Dva&lt;br&gt;
3 - три    - Tri&lt;br&gt;
4 - четири - Chetiri&lt;br&gt;
5 - пет    - Pet&lt;br&gt;
6 - шест   - Shest&lt;br&gt;
7 - седум  - Sedum&lt;br&gt;
8 - осум   - Osum&lt;br&gt;
9 - девет  - Devet&lt;br&gt;
10 - десет - Deset&lt;br&gt;

Followed by:&lt;br&gt;
&lt;br&gt;
11 - единаесет    - Edinaeset&lt;br&gt;
12 - дванаесет    - Dvanaeset&lt;br&gt;
13 - тринаесет    - Trinaeset&lt;br&gt;
14 - четиринаесет - Chetirinaeset&lt;br&gt;
15 - петнаесет    - Petnaeset&lt;br&gt;
16 - шеснаесет    - Shesnaeset&lt;br&gt;
17 - седумнаесет  - Sedumnaeset&lt;br&gt;
18 - осумнаесет   - Osumnaeset&lt;br&gt;
19 - деветнаесет  - Devetnaeset&lt;br&gt;
20 - дваесет      - Dvaeset&lt;br&gt;
&lt;br&gt;
To form the numbers after twenty you should use the following formula: дваесет + и (which means ''and'' in macedonian ) + the number you want to add e.g. five&lt;br&gt;
That would be:
дваесет+и+пет which correctly written and read will be&lt;br&gt;
дваесет и пет&lt;br&gt;
This formula is used to form the rest of the numbers:&lt;br&gt;

30 - триесет    - Trieset&lt;br&gt;
40 - четириесет - Chetirieset&lt;br&gt;
50 - педесет    - Pedeset&lt;br&gt;
60 - шеесет     - Sheeset&lt;br&gt;
70 - седумдесет - Sedumdeset&lt;br&gt;
80 - осумдесет  - Osumdeset&lt;br&gt;
90 - деведесет  - Devedeset&lt;br&gt;

And then:&lt;br&gt;
100 - сто - Sto&lt;br&gt;
1 000 - илјада - Ilyada&lt;br&gt;
1 000 000 - милион - Milion&lt;br&gt;
1 000 000 000 - милијарда - Miliyarda&lt;br&gt;

[[{{BOOKCATEGORY}}]]</text>
      <sha1>atqtxmom0mxjr6oe3ecdx2c7jp9vtgr</sha1>
    </revision>
  </page>
  <page>
    <title>Category:Templates</title>
    <ns>14</ns>
    <id>78328</id>
    <revision>
      <id>4675715</id>
      <parentid>3694527</parentid>
      <timestamp>2026-10-12T12:16:42Z</timestamp>
      <contributor>
        <username>Luciérnaga de conocimiento</username>
        <id>3401314</id>
      </contributor>
      <origin>4675715</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="210" sha1="jillkn6sj9o2u7292ph1jbpe96emem1" xml:space="preserve">{{template category}}

Useful links:
* [[Wikibooks:Templates]] - List of useful templates, sorted by usage
* [[Help:Templates]] - Help on using templates

{{Wikibooks editor navigation}}
[[Category:Categories]]</text>
      <sha1>jillkn6sj9o2u7292ph1jbpe96emem1</sha1>
    </revision>
    <revision>
      <id>4675716</id>
      <parentid>4675715</parentid>
      <timestamp>2026-10-12T12:18:35Z</timestamp>
      <contributor>
        <username>MarcGarver</username>
        <id>134830</id>
      </contributor>
      <minor />
      <comment>[[WB:REVERT|Reverted]] edit by [[Special:Contributions/Luciérnaga de conocimiento|Luciérnaga de conocimiento]] ([[User talk:Luciérnaga de conocimiento|talk]]) to last version by Mrjulesd</comment>
      <origin>3694527</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1341" sha1="awgh99png1i34cejvjlqp96vlnheu9m" xml:space="preserve">{{template category}}

Useful links:
* [[Wikibooks:Templates]] - List of useful templates, sorted by usage
* [[Help:Templates]] - Help on using templates

{{Wikibooks editor navigation}}
[[Category:Categories]]

[[af:Kategorie:Sjablone]]
[[az:Kateqoriya:Şablonlar]]
[[bg:Категория:Шаблони]]
[[bs:Kategorija:Šabloni]]
[[ca:Categoria:Plantilles]]
[[da:Kategori:Skabeloner]]
[[de:Kategorie:Vorlage]]
[[es:Categoría:Plantillas]]
[[eo:Kategorio:Vikilibroj:Ŝablonoj]]
[[fa:رده:الگوها]]
[[fr:Catégorie:Modèles]]
[[gl:Categoría:Marcadores]]
[[hy:Կատեգորիա:Կաղապարներ]]
[[id:Kategori:Templat]]
[[ia:Categoria:Patronos]]
[[is:Flokkur:Snið]]
[[it:Categoria:Template]]
[[he:קטגוריה:תבניות]]
[[ka:კატეგორია:თარგები]]
[[ku:Kategorî:Şablon]]
[[la:Categoria:Formulae]]
[[lt:Kategorija:Šablonai]]
[[hu:Kategória:Sablonok]]
[[ml:വർഗ്ഗം:ഫലകങ്ങൾ]]
[[ne:श्रेणी:Templates]]
[[ja:カテゴリ:ウィキブックスのテンプレート]]
[[no:Kategori:Maler]]
[[pl:Kategoria:Szablony]]
[[ro:Categorie:Formate Wikipedia]]
[[ru:Категория:Викиучебник:Шаблоны]]
[[sq:Kategoria:Stampa]]
[[sr:Категорија:Шаблони]]
[[fi:Luokka:Mallineet]]
[[sv:Kategori:Mallar]]
[[tr:Kategori:Şablonlar]]</text>
      <sha1>awgh99png1i34cejvjlqp96vlnheu9m</sha1>
    </revision>
    <revision>
      <id>4675717</id>
      <parentid>4675716</parentid>
      <timestamp>2026-10-12T12:19:16Z</timestamp>
      <contributor>
        <username>Luciérnaga de conocimiento</username>
        <id>3401314</id>
      </contributor>
      <origin>4675717</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="210" sha1="jillkn6sj9o2u7292ph1jbpe96emem1" xml:space="preserve">{{template category}}

Useful links:
* [[Wikibooks:Templates]] - List of useful templates, sorted by usage
* [[Help:Templates]] - Help on using templates

{{Wikibooks editor navigation}}
[[Category:Categories]]</text>
      <sha1>jillkn6sj9o2u7292ph1jbpe96emem1</sha1>
    </revision>
    <revision>
      <id>4675719</id>
      <parentid>4675717</parentid>
      <timestamp>2026-10-12T12:19:28Z</timestamp>
      <contributor>
        <username>MarcGarver</username>
        <id>134830</id>
      </contributor>
      <minor />
      <comment>[[WB:REVERT|Reverted]] edit by [[Special:Contributions/Luciérnaga de conocimiento|Luciérnaga de conocimiento]] ([[User talk:Luciérnaga de conocimiento|talk]]) to last version by MarcGarver</comment>
      <origin>3694527</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1341" sha1="awgh99png1i34cejvjlqp96vlnheu9m" xml:space="preserve">{{template category}}

Useful links:
* [[Wikibooks:Templates]] - List of useful templates, sorted by usage
* [[Help:Templates]] - Help on using templates

{{Wikibooks editor navigation}}
[[Category:Categories]]

[[af:Kategorie:Sjablone]]
[[az:Kateqoriya:Şablonlar]]
[[bg:Категория:Шаблони]]
[[bs:Kategorija:Šabloni]]
[[ca:Categoria:Plantilles]]
[[da:Kategori:Skabeloner]]
[[de:Kategorie:Vorlage]]
[[es:Categoría:Plantillas]]
[[eo:Kategorio:Vikilibroj:Ŝablonoj]]
[[fa:رده:الگوها]]
[[fr:Catégorie:Modèles]]
[[gl:Categoría:Marcadores]]
[[hy:Կատեգորիա:Կաղապարներ]]
[[id:Kategori:Templat]]
[[ia:Categoria:Patronos]]
[[is:Flokkur:Snið]]
[[it:Categoria:Template]]
[[he:קטגוריה:תבניות]]
[[ka:კატეგორია:თარგები]]
[[ku:Kategorî:Şablon]]
[[la:Categoria:Formulae]]
[[lt:Kategorija:Šablonai]]
[[hu:Kategória:Sablonok]]
[[ml:വർഗ്ഗം:ഫലകങ്ങൾ]]
[[ne:श्रेणी:Templates]]
[[ja:カテゴリ:ウィキブックスのテンプレート]]
[[no:Kategori:Maler]]
[[pl:Kategoria:Szablony]]
[[ro:Categorie:Formate Wikipedia]]
[[ru:Категория:Викиучебник:Шаблоны]]
[[sq:Kategoria:Stampa]]
[[sr:Категорија:Шаблони]]
[[fi:Luokka:Mallineet]]
[[sv:Kategori:Mallar]]
[[tr:Kategori:Şablonlar]]</text>
      <sha1>awgh99png1i34cejvjlqp96vlnheu9m</sha1>
    </revision>
    <revision>
      <id>4675720</id>
      <parentid>4675719</parentid>
      <timestamp>2026-10-12T12:26:19Z</timestamp>
      <contributor>
        <username>Luciérnaga de conocimiento</username>
        <id>3401314</id>
      </contributor>
      <origin>4675720</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1352" sha1="6nqh2osths4gi1v00rf9bpaazqajq68" xml:space="preserve">{{template category}}

Useful links:
* [[Wikibooks:Templates]] - List of useful templates, sorted by usage
* [[Help:Templates]] - Help on using templates

{{Wikibooks editor navigation}}
[[Category:Categories]]

[[af:Kategorie:Sjablone]]
[[az:Kateqoriya:Şablonlar]]
[[bg:Категория:Шаблони]]
[[bs:Kategorija:Šabloni]]
[[ca:Categoria:Plantilles]]
[[da:Kategori:Skabeloner]]
[[de:Kategorie:Vorlage]]
[[es:Categoría:Wikilibros:Plantillas]]
[[eo:Kategorio:Vikilibroj:Ŝablonoj]]
[[fa:رده:الگوها]]
[[fr:Catégorie:Modèles]]
[[gl:Categoría:Marcadores]]
[[hy:Կատեգորիա:Կաղապարներ]]
[[id:Kategori:Templat]]
[[ia:Categoria:Patronos]]
[[is:Flokkur:Snið]]
[[it:Categoria:Template]]
[[he:קטגוריה:תבניות]]
[[ka:კატეგორია:თარგები]]
[[ku:Kategorî:Şablon]]
[[la:Categoria:Formulae]]
[[lt:Kategorija:Šablonai]]
[[hu:Kategória:Sablonok]]
[[ml:വർഗ്ഗം:ഫലകങ്ങൾ]]
[[ne:श्रेणी:Templates]]
[[ja:カテゴリ:ウィキブックスのテンプレート]]
[[no:Kategori:Maler]]
[[pl:Kategoria:Szablony]]
[[ro:Categorie:Formate Wikipedia]]
[[ru:Категория:Викиучебник:Шаблоны]]
[[sq:Kategoria:Stampa]]
[[sr:Категорија:Шаблони]]
[[fi:Luokka:Mallineet]]
[[sv:Kategori:Mallar]]
[[tr:Kategori:Şablonlar]]</text>
      <sha1>6nqh2osths4gi1v00rf9bpaazqajq68</sha1>
    </revision>
  </page>
  <page>
    <title>Haskell/Variables and functions</title>
    <ns>0</ns>
    <id>80256</id>
    <revision>
      <id>4675766</id>
      <parentid>4675614</parentid>
      <timestamp>2026-10-12T22:49:39Z</timestamp>
      <contributor>
        <username>Luciérnaga de conocimiento</username>
        <id>3401314</id>
      </contributor>
      <comment>/* Local definitions */</comment>
      <origin>4675766</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="20906" sha1="a4ol2xi9iq3zp4gs6mhphzu7kuiaweq" xml:space="preserve">{{clear}}
{{Haskell minitoc|chapter=Haskell Basics}}

''All the examples in this chapter can be saved into a Haskell source file and then evaluated by loading that file into GHCi. Do not include the &quot;Prelude&gt;&quot; prompts part of any example. When that prompt is shown, it means you can type the following code into an environment like GHCi. Otherwise, you should put the code in a file and run it.''

== Variables ==

In the last chapter, we used GHCi as a calculator. Of course, that's only practical for short calculations. For longer calculations and for writing Haskell programs, we want to keep track of intermediate results.

We can store intermediate results by assigning them names. These names are called ''variables''. When a program runs, each variable is substituted for the ''value'' to which it refers. For instance, consider the following calculation:

{{Haskell/GHCi|1=
Prelude&gt; 3.141592653 * 5^2
78.539816325
}}

That is the approximate area of a circle with radius &lt;code&gt;5&lt;/code&gt;, according to the formula &lt;math&gt;A = \pi r^2&lt;/math&gt;. Of course, it is cumbersome to type in the digits of &lt;math&gt;\pi \approx 3.141592653&lt;/math&gt;, or even to remember more than the first few. Programming helps us avoid mindless repetition and rote memorization by delegating these tasks to a machine. That way, our minds stay free to deal with more interesting ideas. For the present case, Haskell already includes a variable named &lt;code&gt;pi&lt;/code&gt; that stores over a dozen digits of &lt;math&gt;\pi&lt;/math&gt; for us. This allows for not just clearer code, but also greater precision:

{{Haskell/GHCi|1=
Prelude&gt; pi
3.141592653589793
Prelude&gt; pi * 5^2
78.53981633974483
}}

Note that the variable &lt;code&gt;pi&lt;/code&gt; and its value, &lt;code&gt;3.141592653589793&lt;/code&gt;, can be used interchangeably in calculations.

== Haskell source files ==

Beyond momentary operations in GHCi, you will save your code in Haskell source files (basically plain text) with the extension &lt;code&gt;.hs&lt;/code&gt;. Work with these files using a text editor appropriate for coding (see the [[w:text editor|Wikipedia article on text editors]]). Proper source code editors will provide ''syntax highlighting'', which colors the code in relevant ways to make reading and understanding easier. Vim and Emacs are popular choices among Haskell programmers, but have a bit of a learning curve to be able to fully benefit from their features. Visual Studio Code is also popular among Haskell programmers and is easier for beginners to use.

To keep things tidy, create a directory (i.e. a folder) in your computer to save the Haskell files you will create while doing the exercises in this book. Call the directory something like &lt;code&gt;HaskellWikibook&lt;/code&gt;. Then, create a new file in that directory called &lt;code&gt;Varfun.hs&lt;/code&gt; with the following code:

&lt;syntaxhighlight lang = &quot;haskell&quot;&gt;
r = 5.0
&lt;/syntaxhighlight&gt;

That code defines the variable &lt;code&gt;r&lt;/code&gt; as the value &lt;code&gt;5.0&lt;/code&gt;.

Note: make sure that there are no spaces at the beginning of the line because Haskell is sensitive to whitespace.

Next, with your terminal at the &lt;code&gt;HaskellWikibook&lt;/code&gt; directory, start GHCi and load the &lt;code&gt;Varfun.hs&lt;/code&gt; file using the &lt;code&gt;:load&lt;/code&gt; command:

{{Haskell/GHCi|1=
Prelude&gt; :load Varfun.hs
[1 of 1] Compiling Main             ( Varfun.hs, interpreted )
Ok, modules loaded: Main.
}}

Note that &lt;code&gt;:load&lt;/code&gt; can be abbreviated as &lt;code&gt;:l&lt;/code&gt; (as in &lt;code&gt;:l Varfun.hs&lt;/code&gt;).

If GHCi gives an error like &lt;code&gt;Could not find module 'Varfun.hs'&lt;/code&gt;, you are probably running GHCi in the wrong directory or saved your file in the wrong directory. You can use the &lt;code&gt;:cd&lt;/code&gt; command to change directories within GHCi (for instance, &lt;code&gt;:cd HaskellWikibook&lt;/code&gt;).

With the file loaded, GHCi's prompt changes from &quot;Prelude&quot; to &quot;*Main&quot;. You can now use the newly defined variable &lt;code&gt;r&lt;/code&gt; in your calculations:

{{Haskell/GHCi|1=
*Main&gt; r
5.0
*Main&gt; pi * r^2
78.53981633974483
}}

So, we calculated the area of a circle with radius of 5.0 using the well-known formula &lt;math&gt;\pi r^2&lt;/math&gt;. This worked because we defined &lt;code&gt;r&lt;/code&gt; in our Varfun.hs file and &lt;code&gt;pi&lt;/code&gt; comes from the standard Haskell libraries.

Next, we'll make the area formula easier to quickly access by defining a variable name for it. Change the contents of the source file to:

&lt;syntaxhighlight lang = &quot;haskell&quot;&gt;
r = 5.0
area = pi * r ^ 2
&lt;/syntaxhighlight&gt;

Save the file. Then, assuming you kept GHCi running with the file still loaded, type &lt;code&gt;:reload&lt;/code&gt; (or abbreviate version &lt;code&gt;:r&lt;/code&gt;):

{{Haskell/GHCi|1=
*Main&gt; :reload
Compiling Main             ( Varfun.hs, interpreted )
Ok, modules loaded: Main.
*Main&gt;
}}

Now we have two variables &lt;code&gt;r&lt;/code&gt; and &lt;code&gt;area&lt;/code&gt;:

{{Haskell/GHCi|1=
*Main&gt; area
78.53981633974483
*Main&gt; area / r
15.707963267948966
}}

{{body note|The &lt;code&gt;let&lt;/code&gt; ''keyword'' (a word with a special meaning) lets us define variables directly at the GHCi prompt without a source file. This looks like:
 &lt;nowiki&gt;Prelude&gt; let area = pi * 5 ^ 2&lt;/nowiki&gt;
Although sometimes convenient, assigning variables entirely in GHCi this way is impractical for any complex tasks. We will usually want to use saved source files.
}}

== Comments ==
Besides the working code itself, source files may contain text ''comments''. In Haskell there are two types of comment. The first starts with &lt;code&gt;--&lt;/code&gt; and continues until the end of the line:

&lt;syntaxhighlight lang = &quot;haskell&quot;&gt;
x = 5     -- x is 5.
y = 6     -- y is 6.
-- z = 7  -- z is not defined.
&lt;/syntaxhighlight&gt;

In this case, &lt;code&gt;x&lt;/code&gt; and &lt;code&gt;y&lt;/code&gt; are defined in actual Haskell code, but &lt;code&gt;z&lt;/code&gt; is not.

The second type of comment is denoted by an enclosing &lt;code&gt;{- ... -}&lt;/code&gt; and can span multiple lines:
&lt;syntaxhighlight lang = &quot;haskell&quot;&gt;
answer = 2 * {-
  block comment, crossing lines and...
  -} 3 {- inline comment. -} * 7
&lt;/syntaxhighlight&gt;

By combining single- and multi-line commenting, it is possible to toggle between executed and commented-out code by adding or removing a single &lt;code&gt;}&lt;/code&gt; character, respectively:
&lt;syntaxhighlight lang = &quot;haskell&quot;&gt;
{--
foo :: String
foo = &quot;bar&quot;
--}
&lt;/syntaxhighlight&gt;
vs.
&lt;syntaxhighlight lang = &quot;haskell&quot;&gt;
{--}
foo :: String
foo = &quot;bar&quot;
--}
&lt;/syntaxhighlight&gt;

We use comments for explaining parts of a program or making other notes in context. Beware of comment overuse as too many comments can make programs harder to read. Also, we must carefully update comments whenever we change the corresponding code. Outdated comments can cause significant confusion.

== Variables in imperative languages ==
Readers familiar with imperative programming will notice that variables in Haskell seem quite different from variables in languages like C.
If you have no programming experience, you could skip this section, but it will help you understand the general situation when encountering the many cases (most Haskell textbooks, for example) where people discuss Haskell in reference to other programming languages.

''Imperative programming'' treats variables as changeable locations in a computer's memory. That approach connects to the basic operating principles of computers. Imperative programs explicitly tell the computer what to do. Higher-level imperative languages are quite removed from direct computer assembly code instructions, but they retain the same step-by-step way of thinking. In contrast, ''functional programming'' offers a way to think in higher-level mathematical terms, defining how variables relate to one another, leaving the compiler to translate these to the step-by-step instructions that the computer can process.

Let's look at an example. The following code does not work in Haskell:

&lt;syntaxhighlight lang = &quot;haskell&quot;&gt;
r = 5
r = 2
&lt;/syntaxhighlight&gt;

An imperative programmer may read this as first setting &lt;code&gt;r = 5&lt;/code&gt; and then changing it to &lt;code&gt;r = 2&lt;/code&gt;. In Haskell, however, the compiler will respond to the code above with an error: &quot;multiple declarations of &lt;code&gt;r&lt;/code&gt;&quot;. Within a given scope, a variable in Haskell gets defined only once and cannot change.

The variables in Haskell seem almost ''invariable'', but they work like variables in mathematics. In a math classroom, you never see a variable change its value within a single problem.

In precise terms, Haskell variables are ''immutable''. They vary only based on the data we enter into a program. We can't define &lt;code&gt;r&lt;/code&gt; two ways in the same code, but we could change the value by changing the file. Let's update our code from above:

&lt;syntaxhighlight lang = &quot;haskell&quot;&gt;
r = 2.0
area = pi * r ^ 2
&lt;/syntaxhighlight&gt; 

Of course, that works just fine. We can change &lt;code&gt;r&lt;/code&gt; in the one place where it is defined, and that will automatically update the value of all the rest of the code that uses the &lt;code&gt;r&lt;/code&gt; variable.

Real-world Haskell programs work by leaving ''some'' variables unspecified in the code. The values then get defined when the program gets data from an external file, a database, or user input. For now, however, we will stick to defining variables internally. We will cover interaction with external data in later chapters.

Here's one more example of a major difference from imperative languages:

&lt;syntaxhighlight lang = &quot;haskell&quot;&gt;
r = r + 1
&lt;/syntaxhighlight&gt;

Instead of &quot;incrementing the variable &lt;code&gt;r&lt;/code&gt;&quot; (i.e. updating the value in memory), this Haskell code is a recursive definition of &lt;code&gt;r&lt;/code&gt; (i.e. defining it in terms of itself). We will explain [[Haskell/Recursion|recursion]] in detail later on. For this specific case, if &lt;code&gt;r&lt;/code&gt; had been defined with any value beforehand, then &lt;code&gt; r = r + 1 &lt;/code&gt; in Haskell would bring an error message. &lt;code&gt; r = r + 1 &lt;/code&gt; is akin to saying, in a mathematical context, that &lt;math&gt;5 = 5 + 1&lt;/math&gt;, which is plainly wrong.

Because their values do not change within a program, variables can be defined in any order. For example, the following fragments of code do exactly the same thing:

{|border=&quot;0&quot;
|-
||&lt;syntaxhighlight lang = &quot;haskell&quot;&gt;
 y = x * 2
 x = 3
&lt;/syntaxhighlight&gt;
||&lt;syntaxhighlight lang = &quot;haskell&quot;&gt;
 x = 3
 y = x * 2
&lt;/syntaxhighlight&gt;
|}

In Haskell, there is no notion of &quot;&lt;code&gt;x&lt;/code&gt; being declared before &lt;code&gt;y&lt;/code&gt;&quot; or the other way around. Of course, using &lt;code&gt;y&lt;/code&gt; will still require a value for &lt;code&gt;x&lt;/code&gt;, but this is unimportant until you need a specific numeric value.

== Functions ==
Changing our program every time we want to calculate the area of new circle is both tedious and limited to one circle at a time. We could calculate two circles by duplicating all the code using new variables &lt;code&gt;r2&lt;/code&gt; and &lt;code&gt;area2&lt;/code&gt; for the second circle:&lt;ref&gt;As this example shows, the names of variables may contain numbers as well as letters. Variables in Haskell ''must'' begin with a lowercase letter but may then have any string consisting of letter, numbers, underscore (_) or tick (').&lt;/ref&gt;

&lt;syntaxhighlight lang = &quot;haskell&quot;&gt;
r  = 5
area  = pi * r ^ 2
r2 = 3
area2 = pi * r2 ^ 2
&lt;/syntaxhighlight&gt;

Of course, to eliminate this mindless repetition, we would prefer to have simply one ''function'' for area and then apply it to different radii.

A ''function'' takes an ''argument'' value (or ''parameter'') and gives a result value (essentially the same as in mathematical functions). Defining functions in Haskell is like defining a variable, except that we take note of the function argument that we put on the left hand side of the equals sign. For instance, the following defines a function &lt;code&gt;area&lt;/code&gt; which depends on an argument named &lt;code&gt;r&lt;/code&gt;:

&lt;syntaxhighlight lang = &quot;haskell&quot;&gt;
area r = pi * r ^ 2
&lt;/syntaxhighlight&gt;

Look closely at the syntax: the function name comes first (&lt;code&gt;area&lt;/code&gt; in our example), followed by a space and then the argument (&lt;code&gt;r&lt;/code&gt; in the example). Following the &lt;code&gt;=&lt;/code&gt; sign, the ''function definition'' is a formula that uses the argument in context with other already defined terms.

Now, we can plug in different values for the argument in a ''call'' to the function. Save the code above in a file, load it into GHCi, and try the following:

{{Haskell/GHCi|1=
*Main&gt; area 5
78.53981633974483
*Main&gt; area 3
28.274333882308138
*Main&gt; area 17
907.9202768874502
}}

Thus, we can ''call'' this function with different radii to calculate the area of any circle.

Our function here is defined mathematically as
:&lt;math&gt;A(r) = \pi \cdot r^2&lt;/math&gt;
In mathematics, the argument is enclosed between parentheses, as in &lt;math&gt;A(5) = 78.54&lt;/math&gt; or &lt;math&gt;A(3) = 28.27&lt;/math&gt;. Many programming languages likewise surround arguments with parentheses, as in &lt;code&gt;max(2, 3)&lt;/code&gt;. But Haskell omits parentheses around a list of arguments (as well as commas between them): &lt;code&gt;max 2 3&lt;/code&gt;.

We still use parentheses for grouping ''expressions'' (any code that gives a value) that must be evaluated together. Note how the following expressions are parsed differently:

&lt;syntaxhighlight lang = &quot;haskell&quot;&gt;
5 * 3 + 2       -- 15 + 2 = 17 (multiplication is done before addition)
5 * (3 + 2)     -- 5 * 5 = 25 (thanks to the parentheses)
area 5 * 3      -- (area 5) * 3
area (5 * 3)    -- area 15
&lt;/syntaxhighlight&gt;

Note that Haskell functions take ''precedence'' over all other operators such as &lt;code&gt;+&lt;/code&gt; and &lt;code&gt;*&lt;/code&gt;, in the same way that, for instance, multiplication is done before addition in mathematics.

=== Evaluation ===
What exactly happens when you enter an expression into GHCi? After you press the enter key, GHCi will ''evaluate'' the expression you have given. That means it will replace each function with its definition and calculate the results until a single value remains. For example, the evaluation of &lt;code&gt;area 5&lt;/code&gt; proceeds as follows:

    area 5
 =&gt;    { replace the left-hand side  area r = ...  by the right-hand side  ... = pi * r^2 }
    pi * 5 ^ 2
 =&gt;    { replace  pi  by its numerical value }
    3.141592653589793 * 5 ^ 2
 =&gt;    { apply exponentiation (^) }
    3.141592653589793 * 25
 =&gt;    { apply multiplication (*) }
    78.53981633974483

As this shows, to ''apply'' or ''call'' a function means to replace the left-hand side of its definition by its right-hand side. When using GHCi, the results of a function call will then show on the screen.

Some more functions:

&lt;syntaxhighlight lang = &quot;haskell&quot;&gt;
double x    = 2 * x
quadruple x = double (double x)
square x    = x * x
half   x    = x / 2
&lt;/syntaxhighlight&gt;

{{Exercises|1=
* Explain how GHCi evaluates &lt;code&gt;quadruple 5&lt;/code&gt;.
* Define a function that subtracts 12 from half its argument.}}

=== Multiple parameters ===

Functions can also take more than one argument. For example, a function for calculating the area of a rectangle given its length and width:

&lt;syntaxhighlight lang = &quot;haskell&quot;&gt;
areaRect l w = l * w
&lt;/syntaxhighlight&gt;

{{Haskell/GHCi|1=
*Main&gt; areaRect 5 10
50
}}

Another example that calculates the area of a triangle &lt;math&gt;\left(A = \frac{bh}{2}\right)&lt;/math&gt;:

&lt;syntaxhighlight lang=&quot;haskell&quot;&gt;
areaTriangle b h = (b * h) / 2
&lt;/syntaxhighlight&gt;

{{Haskell/GHCi|1=
*Main&gt; areaTriangle 3 9
13.5
}}

As you can see, multiple arguments are separated by spaces. That's also why you sometimes have to use parentheses to group expressions. For instance, to quadruple a value &lt;code&gt;x&lt;/code&gt;, you can't write:

&lt;syntaxhighlight lang = &quot;haskell&quot;&gt;
quadruple x = double double x     -- error
&lt;/syntaxhighlight&gt;

That would apply a function named &lt;code&gt;double&lt;/code&gt; to the two arguments &lt;code&gt;double&lt;/code&gt; and &lt;code&gt;x&lt;/code&gt;. Note that ''functions can be arguments to other functions'' (you will see why later). To make this example work, we need to put parentheses around the argument:

&lt;syntaxhighlight lang = &quot;haskell&quot;&gt;
quadruple x = double (double x)
&lt;/syntaxhighlight&gt;

Arguments are always passed in the order given. For example:

&lt;syntaxhighlight lang = &quot;haskell&quot;&gt;
minus x y = x - y
&lt;/syntaxhighlight&gt;

{{Haskell/GHCi|1=
*Main&gt; minus 10 5
5
*Main&gt; minus 5 10
-5
}}

Here, &lt;code&gt;minus 10 5&lt;/code&gt; evaluates to &lt;code&gt;10 - 5&lt;/code&gt;, but &lt;code&gt;minus 5 10&lt;/code&gt; evaluates to &lt;code&gt;5 - 10&lt;/code&gt; because the order changes.

{{Exercises|1=
* Write a function to calculate the volume of a box.
* Approximately how many stones are the famous pyramids at Giza made up of? Hint: you will need estimates for the volume of the pyramids and the volume of each block.
}}

=== On combining functions ===

Of course, you can use functions that you have already defined to define new functions, just like you can use the predefined functions like addition &lt;code&gt;(+)&lt;/code&gt; or multiplication &lt;code&gt;(*)&lt;/code&gt; (operators are defined as functions in Haskell). For example, to calculate the area of a square, we can reuse our function that calculates the area of a rectangle:

&lt;syntaxhighlight lang = &quot;haskell&quot;&gt;
areaRect l w = l * w
areaSquare s = areaRect s s
&lt;/syntaxhighlight&gt;

{{Haskell/GHCi|1=
*Main&gt; areaSquare 5
25
}}

After all, a square is just a rectangle with equal sides.

{{Exercises|1=
* Write a function to calculate the volume of a cylinder.  The volume of a cylinder is the area of the base, which is a circle (you already programmed this function in this chapter, so reuse it) multiplied by the height.
}}

== Local definitions ==
=== &lt;code&gt;where&lt;/code&gt; clauses ===
When defining a function, we sometimes want to define intermediate results that are ''local'' to the function. For instance, consider [[w:Heron's formula|Heron's formula]] &lt;math&gt;A = \sqrt{s(s-a)(s-b)(s-c)}&lt;/math&gt; for calculating the area of a triangle with sides &lt;code&gt;a&lt;/code&gt;, &lt;code&gt;b&lt;/code&gt;, and &lt;code&gt;c&lt;/code&gt;:

&lt;syntaxhighlight lang = &quot;haskell&quot;&gt;
heron a b c = sqrt (s * (s - a) * (s - b) * (s - c))
    where
    s = (a + b + c) / 2
&lt;/syntaxhighlight&gt;

The variable &lt;code&gt;s&lt;/code&gt; is half the perimeter of the triangle and it would be tedious to write it out four times in the argument of the square root function &lt;code&gt;sqrt&lt;/code&gt;.

Simply writing the definitions in sequence does not work...

&lt;syntaxhighlight lang = &quot;haskell&quot;&gt;
heron a b c = sqrt (s * (s - a) * (s - b) * (s - c))
s = (a + b + c) / 2                                   -- a, b, and c are not defined here
&lt;/syntaxhighlight&gt;

... because the variables &lt;code&gt;a&lt;/code&gt;, &lt;code&gt;b&lt;/code&gt;, &lt;code&gt;c&lt;/code&gt; are only available in the right-hand side of the function &lt;code&gt;heron&lt;/code&gt;, but the definition of &lt;code&gt;s&lt;/code&gt; as written here is not part of the right-hand side of &lt;code&gt;heron&lt;/code&gt;. To make it part of the right-hand side, we use the &lt;code&gt;where&lt;/code&gt; keyword.

Note that both the &lt;code&gt;where&lt;/code&gt; and the local definitions are ''indented'' by 4 spaces, to distinguish them from subsequent definitions. Here is another example that shows a mix of local and top-level definitions:

&lt;syntaxhighlight lang = &quot;haskell&quot;&gt;
areaTriangleTrig  a b c = c * height / 2   -- use trigonometry
    where
    cosAlfa   = (b ^ 2 + c ^ 2 - a ^ 2) / (2 * b * c)
    sinAlfa   = sqrt (1 - cosAlfa ^ 2)
    height    = b * sinAlfa
areaTriangleHeron a b c = result           -- use Heron's formula
    where
    result = sqrt (s * (s - a) * (s - b) * (s - c))
    s      = (a + b + c) / 2
&lt;/syntaxhighlight&gt;

=== Scope ===
If you look closely at the previous example, you'll notice that we have used the variable names &lt;code&gt;a&lt;/code&gt;, &lt;code&gt;b&lt;/code&gt;, &lt;code&gt;c&lt;/code&gt; twice, once for each of the two area functions. How does that work?

Consider the following GHCi sequence:

{{Haskell/GHCi|1=
Prelude&gt; let r = 0
Prelude&gt; let area r = pi * r ^ 2
Prelude&gt; area 5
78.53981633974483
}}

It would have been an unpleasant surprise to return &lt;code&gt;0&lt;/code&gt; for the area because of the earlier &lt;code&gt;let r = 0&lt;/code&gt; definition getting in the way. That does not happen because when you defined &lt;code&gt;r&lt;/code&gt; the second time you are talking about a ''different'' &lt;code&gt;r&lt;/code&gt;. This may seem confusing, but consider how many people have the name John, and yet for any context with only one John, we can talk about &quot;John&quot; with no confusion. Programming has a notion similar to context, called ''[[Wikipedia:Scope (programming)|scope]]''.

We will not explain the technicalities behind scope right now. Just keep in mind that the value of a parameter is strictly what you pass in when you call the function, regardless of what the variable was called in the function's definition. That said, appropriately unique names for variables do make the code easier for human readers to understand.

== Summary ==

# Variables store values (which can be any arbitrary Haskell expression).
# Variables do not change within a scope.
# Functions help you write reusable code.
# Functions can accept more than one parameter.

We also learned about non-code text comments  within a source file.

{{Haskell/NotesSection}}

{{Haskell navigation|chapter=Haskell Basics}}

{{Auto category}}</text>
      <sha1>a4ol2xi9iq3zp4gs6mhphzu7kuiaweq</sha1>
    </revision>
  </page>
  <page>
    <title>Italian/Grammar/Articles</title>
    <ns>0</ns>
    <id>80367</id>
    <revision>
      <id>4675733</id>
      <parentid>4369671</parentid>
      <timestamp>2026-10-12T13:34:32Z</timestamp>
      <contributor>
        <username>Luciérnaga de conocimiento</username>
        <id>3401314</id>
      </contributor>
      <origin>4675733</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2176" sha1="eb8xkn42r2u9s32ub5c8lvs2we3zdv3" xml:space="preserve">==Determinative article (the) / L'articolo determinativo ==

The English article ''the'' has several translations into Italian, according to:
* gender: masculine or feminine
* number: singular or plural
* initial of the following word

&lt;b&gt;Basic articles:&lt;/b&gt;
 Masculine singular: il
 Masculine plural: i
 Feminine singular: la
 Feminine plural: le

Articles must have the same gender and number of the referred noun.

&lt;b&gt;Examples:&lt;/b&gt;
 Il ragazzo (''the boy'')
 La ragazza (''the girl'')
 I ragazzi (''the boys'')
 Le ragazze (''the girls'')

When the following word begins with z, s+consonant, gn, pn, ps or x, the masculine article is changed as follows:

&lt;b&gt;Masculine articles before impure consonant sounds:&lt;/b&gt;
 Masculine singular: lo
 Masculine plural: gli

&lt;b&gt;Examples:&lt;/b&gt;
 Lo zio (''the uncle'')
 Gli zii (''the uncles'')

When the following word begins with a vowel, articles are changed as follows:

&lt;b&gt;Articles before a vowel:&lt;/b&gt;
 Masculine singular: l' (lo)
 Masculine plural: gli
 Feminine singular: l' (la)
 Feminine plural: le

The form l' is not colloquial, it is the normal form even in very polite and refined speech.

&lt;b&gt;Examples:&lt;/b&gt;
 L'orso (''the bear'')
 - plural: gli orsi (''the bears'')
 L'arma (''the weapon'')
 - plural: le armi (''the weapons'')

Note that when the vowel is an i pronounced as a semi-vowel, lo and la are used, eg lo iodio, la iarda.
== Indeterminate and Partitive Articles (a/an) / Gli articoli partitivi e indeterminativi (un/uno/una) ==

&lt;b&gt;Basic indeterminate articles:&lt;/b&gt;
 Masculine singular: un
 Masculine singular: uno (For impure consonants z, s+consonant, gn, pn, ps, x)
 Feminine singular: una (un' is written when the following word starts with vowel, do not confuse with masculine un!)

These articles do not have any plural but instead the &lt;b&gt;Partitive Article&lt;/b&gt; can be used. These articles all have the meaning of &quot;some&quot; and they are similar to some prepositions but they are not prepositions, they work like articles.

&lt;b&gt;Partitive articles or plural indeterminative:&lt;/b&gt;
 Masculine plural: dei
 Masculine plural: degli (For impure consonants z, s+consonant, gn, pn, ps, x)
 Feminine plural: delle

{{BookCat}}</text>
      <sha1>eb8xkn42r2u9s32ub5c8lvs2we3zdv3</sha1>
    </revision>
  </page>
  <page>
    <title>TI-Basic Z80 Programming/Errors</title>
    <ns>0</ns>
    <id>98338</id>
    <revision>
      <id>4675793</id>
      <parentid>4665872</parentid>
      <timestamp>2026-10-13T06:34:35Z</timestamp>
      <contributor>
        <username>Rex Valerio</username>
        <id>3628187</id>
      </contributor>
      <comment>Fix typos and grammar in error explanations</comment>
      <origin>4675793</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3554" sha1="tlyfedjn7bcbi16j4zom4d8aj8hyf2g" xml:space="preserve">When programming on the TI-84, the calculator will assume the written code is valid. If, as it executes the code, it finds an unexpected token, or encounters an otherwise invalid statement, the TI-84 will throw an '''error'''. The calculator will stop executing the code in the program and display the type of error on the screen. There are two types of errors: ''syntax errors'' and ''runtime errors''.

Consider the following example:

{{Bcode:Example
|:Output(1,&quot;TI84&quot;)
}}

The syntax for the &lt;code&gt;Output(&lt;/code&gt; command expects two integers, then a string. In this example, the second argument is a string, which the calculator does not know how to interpret. In this case, the calculator throws an error:

{{Bcode:Output
|ERR:ARGUMENT
1:Quit
2:Goto
}}

Code execution halts and a menu is displayed. The first option quits the program and returns to the home screen. The second option will open the code editor and scroll to the line in the code where the error occurred.

The second type of error is a runtime error. These errors can't necessarily be detected by the appearance of code. Consider the following example that displays the reciprocal of the entered value:

{{Bcode:Example
|:Prompt A
:Disp A&lt;sup&gt;-1&lt;/sup&gt;
}}

The code works fine in most scenarios:

{{Bcode:Output|
&lt;nowiki&gt;A=?4&lt;/nowiki&gt;
             .25
}}

However, consider when the user inputs &lt;code&gt;0&lt;/code&gt;:

{{Bcode:Output|
&lt;nowiki&gt;A=?0
             
ERR:DIVIDE BY 0
1:Quit
2:Goto&lt;/nowiki&gt;
}}

This behavior can be unwanted, since the code halts and does not continue executing if an error occurs. Therefore, it is important to consider all edge cases for calculations and statements. In this case, the line &lt;code&gt;:If A≠0&lt;/code&gt; before &lt;code&gt;Disp&lt;/code&gt; would prevent an error.

Runtime errors do not necessarily have to display an error to be an ''error''. For example, a program that is expected to display the even letters of the alphabet, but instead displays the odd letters of the alphabet, would have a runtime error since the program does not function as expected. These can be the hardest and easiest errors to fix!

== You try it! ==
Examine the following examples, identify which kind of error is presented, and a fix to resolve the error(s).

&lt;!-- Syntax error --&gt; 
The following program should store 10 random numbers in &lt;code&gt;L&lt;small&gt;1&lt;/small&gt;&lt;/code&gt;, but contains an error. Find, identify, and fix the error.

{{Bcode:Example|
:0→dim(L&lt;small&gt;1&lt;/small&gt;
:For(I,1,10
:rand→L&lt;small&gt;1&lt;/small&gt;[I]
:End
}}

{{Collapse top|title=Solution}}
The error is on line 3. The given program uses square brackets (&lt;code&gt;[&lt;/code&gt; and &lt;code&gt;]&lt;/code&gt;) instead of parentheses. The same program with the error fixed:
{{Bcode:Example|
:0→dim(L&lt;small&gt;1&lt;/small&gt;
:For(I,1,10
:rand→L&lt;small&gt;1&lt;/small&gt;(I)
:End
}}
{{Collapse bottom}}

&lt;!-- Runtime error --&gt; 
In this example, the program should output the largest number in &lt;code&gt;L&lt;small&gt;1&lt;/small&gt;&lt;/code&gt; (this program assumes there is at least one value in &lt;code&gt;L&lt;small&gt;1&lt;/small&gt;&lt;/code&gt;).

{{Bcode:Example|
:-9E99→L
:For(A,1,dim(L&lt;small&gt;1&lt;/small&gt;
:If L&lt;small&gt;1&lt;/small&gt;(A)&gt;L
:A→L
:End
:Disp L
}}

{{Collapse top|title=Solution}}
The error is on line 4. The given program stores the index of the largest number to &lt;code&gt;L&lt;/code&gt;, where it should store the value itself. The fixed program:
{{Bcode:Example|
:-9E99→L
:For(A,1,dim(L&lt;small&gt;1&lt;/small&gt;
:If L&lt;small&gt;1&lt;/small&gt;(A)&gt;L
:L&lt;small&gt;1&lt;/small&gt;(A)→L
:End
:Disp L
}}
In the future, just use &lt;code&gt;max(&lt;/code&gt;.
{{Collapse bottom}}

{{BottomNav|Menus|Tips, Tricks and Optimizations}}</text>
      <sha1>tlyfedjn7bcbi16j4zom4d8aj8hyf2g</sha1>
    </revision>
  </page>
  <page>
    <title>Radiation Oncology/Prostate/Recurrence after RT</title>
    <ns>0</ns>
    <id>109886</id>
    <revision>
      <id>4675787</id>
      <parentid>3263375</parentid>
      <timestamp>2026-10-13T06:18:35Z</timestamp>
      <contributor>
        <username>Jcb</username>
        <id>90773</id>
      </contributor>
      <origin>4675787</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="5681" sha1="julas1n3do561e92kxzh8v8q37wcgr5" xml:space="preserve">{{Radiation Oncology/Prostate:TOC}}

'''Salvage treatments for biochemical failure after definitive radiotherapy.'''

&lt;br&gt;
See also: [[Radiation Oncology/Prostate/Advanced disease#PSA-only recurrence|Advanced disease]] for PSA-only recurrence.

== Androgen ablation ==
'''''Timing of Salvage HT:'''''
* '''ICORG 97-01''' (Irish Clinical Oncology Research Group) (1997-2001) -- early vs late salvage HT
** Secondary (retrospective) analysis of a randomized trial. ICORG 97-01 compared short (4 months) vs long (8 months) neoadjuvant HT before RT. RT following HRT, 70 Gy. See also: [[Radiation Oncology/Prostate/Hormones/Adjuvant ADT#Androgen suppression duration|Adjuvant ADT]] for trial details.
** Purpose: compare survival outcomes of early vs late salvage HT. Treatment of biochemical failure was not specified per protocol.
*** Group 1 (early salvage): biochemical failure, started on HT with PSA &lt;= 10, no distant mets. Group 2 (late salvage): BF, started on HT with PSA &gt; 10, no distant mets. Group 3 (late salvage with DM): distant mets.
** '''2013''' {{PMID|22658512}} -- &quot;Early salvage hormonal therapy for biochemical failure improved survival in prostate cancer patients after neoadjuvant hormonal therapy plus radiation therapy-a secondary analysis of irish clinical oncology research group 97-01.&quot; (Mydin AR, Int J Radiat Oncol Biol Phys. 2013 Jan 1;85(1):101-8.)
** Conclusion: overall survival was improved for pts with BF treated with early salvage HT.

* '''RTOG 85-31''' (1987-92)
** &quot;Non-bulky&quot; trial. Long term (indefinite) HT vs none. See also: [[Radiation Oncology/Prostate/Hormones/Adjuvant ADT#Adjuvant androgen deprivation|Adjuvant ADT]] for trial details.
** '''2010''' {{PMID|20356687}} -- &quot;Timing of Salvage Hormonal Therapy in Prostate Cancer Patients With Unfavorable Prognosis Treated With Radiotherapy: A Secondary Analysis of Radiation Therapy Oncology Group 85-31.&quot; (Souhami L, Int J Radiat Oncol Biol Phys. 2010 Mar 29. [Epub ahead of print])
*** Subset analysis, relapsing patients in RT alone arm. Defined early salvage as initiated with PSA &lt;10 and late-salvage as &gt;10. Median F/U 11 and 13 years
*** Outcome: Early salvage significantly improved OS (HR 1.5, SS), no difference in local failure or cancer-specific mortality
*** Conclusion: Early introduction of salvage hormonal therapy improved OS but not CSS. Randomized trial is warranted


'''''Intermittent androgen ablation:'''''
* '''Canadian trial''' - phase II
** {{PMID|16783817}}, 2006 &amp;mdash; &quot;Final results of the Canadian prospective phase II trial of intermittent androgen suppression for men in biochemical recurrence after radiotherapy for locally advanced prostate cancer: clinical parameters.&quot; Bruchovsky N et al. Cancer. 2006 Jul 15;107(2):389-95.
** 103 pts. Each cycle consisted of cyproterone acetate (CA) x 4 wks then Lupron plus CA for a total of 36 wks.
** Median f/u 4.2 yrs. Time off treatment averaged 53% of total cycle time.

== Brachytherapy ==
* '''U.Wisconsin, 2007''' (Review) {{PMID|17685384}} -- &quot;Management of prostate cancer recurrences after radiation therapy-brachytherapy as a salvage option.&quot; (Allen GW, Cancer. 2007 Oct 1;110(7):1405-16.)
** Review. Summarizes treatment of 226 pts reported in literature, including 12 pts from this institution not previously reported.
** Wisconsin experience: 12 pts, treated with brachy (I or Pd) + 3 mo neoadjuvant AA. Median f/u of 45 months after implant.
** Conclusion: salvage brachytherapy success rates are likely similar to salvage with surgery or cryotherapy.

'''''HDR:'''''
* '''UCSF''' (1998-2005)
** {{PMID|17197119}}, 2006 &amp;mdash; &quot;Feasibility of High-Dose-Rate Brachytherapy Salvage for Local Prostate Cancer Recurrence After Radiotherapy: The University of California-San Francisco Experience.&quot; Lee B et al. Int J Radiat Oncol Biol Phys. 2006 Dec 28.
** 21 pts. 36 Gy in 6 fractions.
** Conclusion: &quot;feasible and effective&quot;

== Prostatectomy ==
'''''Salvage Prostatectomy:'''''
* '''Memorial Sloan-Kettering'''
** {{PMID|12756084}}, 2003 &amp;mdash; &quot;Salvage radical prostatectomy for recurrence of prostate cancer after radiation therapy.&quot; Eastham et al. Curr Urol Rep. 2003 June.
** Incontinence rates are similar to incontinence rates after up front prostatectomy
*** Note: Most other series report higher incontinence rates in the range of 50%

* '''UCSF, 2001''' (Review) {{PMID|11590813}} -- &quot;Salvage radical prostatectomy.&quot; (Shekarriz B, Urol Clin North Am. 2001 Aug;28(3):545-53.)
** Review.

* '''Baylor, 1995''' {{PMID|7526002}} -- &quot;Salvage radical prostatectomy: outcome measured by serum prostate specific antigen levels.&quot; (Rogers E, J Urol. 1995 Jan;153(1):104-10.)
** 40 pts.
** pT3 or pN+ in 54% (more likely if PSA &gt; 10).
** Mean 39 months f/u. 2 pts died from PCA, 5 developed DM; none had local recurrence. 5-yr PSA control 55%. (more likely if pre-surgery PSA &lt; 10). In pts with pathologically localized disease (minimal T3), 82% had PSA control.
** Toxicity: 15% rectal injury (colostomy - 2 pts). Persistent urinary incontinence 58% (corrected with artificial sphincter in 9 of 18).
** Conclusion: salvage prostatectomy provides excellent control of recurrence cancer; best performed before PSA increases greater than 10-20.

== Cryotherapy ==
* '''UK, 2007''' (2000-5) {{PMID|17662081}} -- &quot;Salvage cryotherapy for recurrent prostate cancer after radiation failure: a prospective case series of the first 100 patients.&quot; (Ismail M, BJU Int. 2007 Oct;100(4):760-4. )
** 100 pts. Mean f/u 33 mo. 5-yr bRFS 73% (low risk pts), 45% (int), 11% (high)
** Toxicity: incontinence 13%, erectile dysfunction 86%, recto-urethral fistula 1%.
** Conclusion: salvage cryo is safe and effective</text>
      <sha1>julas1n3do561e92kxzh8v8q37wcgr5</sha1>
    </revision>
  </page>
  <page>
    <title>Wikibooks:Reading room/General</title>
    <ns>4</ns>
    <id>112405</id>
    <revision>
      <id>4675805</id>
      <parentid>4675480</parentid>
      <timestamp>2026-10-13T08:29:54Z</timestamp>
      <contributor>
        <username>MarcGarver</username>
        <id>134830</id>
      </contributor>
      <comment>/* Who is allowed to delete pages here? */ Reply</comment>
      <origin>4675805</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="22185" sha1="1wf96uab4qrgmmmubxwygklvov6drsn" xml:space="preserve">__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]]

== Call for administrators ==

Any experienced editor who has a good understanding of Wikibooks' policies should consider applying for administrator permissions at [[Wikibooks:Requests for permissions]]. Thank you. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 22:10, 5 August 2026 (UTC)

:Is there a page here that describes what admins do? I am curious because I checked [https://en.wikibooks.org/wiki/Special:ListUsers?username=&amp;group=sysop&amp;wpsubmit=&amp;wpFormIdentifier=mw-listusers-form&amp;limit=50 List of admins] and I see that there are already quite a few admins here and wonder which areas have a shortage.
:Just curious. [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 00:56, 16 September 2026 (UTC)
::[[Wikibooks:Administrators]]. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 01:09, 16 September 2026 (UTC)

== August 2026 Wikimedia Café meetups regarding [https://meta.wikimedia.org/wiki/Next_25 Next 25] ==

&lt;div class=&quot;border-box&quot; style=&quot;background-color: var(--background-color-warning-subtle, #f8eaba); max-width: 875px; padding: 5px; border: 1px solid black; margin: 5px; color: var(--clr-dark)&quot;&gt;
&lt;div class=&quot;box&quot; style=&quot;float:left; padding-top: 10px; padding-right: 10px; padding-left: 10px; padding-bottom: 10px;&quot;&gt;[[File:Wikimedia Café logo in plain SVG format.svg|60px|alt=The logo for the Wikimedia Café]]&lt;/div&gt;
Hello! There will be two '''[https://meta.wikimedia.org/wiki/Wikimedia_Caf%C3%A9 Wikimedia Café]''' discussion opportunities in August. Both sessions will focus on [https://meta.wikimedia.org/wiki/Next_25 the Next 25 initiative], including [https://meta.wikimedia.org/wiki/Next_25/A_proposal_to_frame_Next_25 framing the initiative]. Participants may attend either or both Café sessions. 


#'''29 August 2026 15:00 UTC''' ([https://zonestamp.toolforge.org/1788015600 timestamp converter]), at a time friendly to the Americas, Africa, and Europe
#'''30 August 2026 03:00 UTC''' ([https://zonestamp.toolforge.org/1788058800 timestamp converter]), at a time friendly to Asia and the Pacific

Please see the [https://meta.wikimedia.org/wiki/Wikimedia_Caf%C3%A9 Café] page for more information, including [https://meta.wikimedia.org/wiki/Wikimedia_Caf%C3%A9#Agenda._This_will_be_an_approximately_1_hour_Caf%C3%A9_session agenda details] and [https://meta.wikimedia.org/wiki/Wikimedia_Caf%C3%A9#How_to_attend_the_session how to register]!

To subscribe or unsubscribe for Café notices on your talk page please [https://meta.wikimedia.org/wiki/Global_message_delivery/Targets/Wikimedia_Caf%C3%A9 go here].
&lt;br /&gt;
[[File:Buntstifte Eberhard Faber crop 64h.jpg|860px|alt=cropped image of colored pencils]]&lt;/div&gt;
&lt;span style=&quot;white-space:nowrap;&quot;&gt;[[User:Pine|&lt;span style=&quot;color:#01796f; text-shadow:#00BFFF 0 0 1.0em&quot;&gt;༄ᨒ𖠰 Pine&lt;/span&gt;]] [[User talk:Pine|&lt;span style=&quot;color:DeepSkyBlue&quot;&gt;(&lt;b style=&quot;color:#FFDF00;text-shadow:#FFDF00 0 0 1.0em&quot;&gt;✉&lt;/b&gt;)&lt;/span&gt;]]&lt;/span&gt; 01:32, 17 August 2026 (UTC)

== Wikibooks project is not defined by goal ==

If it is for texbooks why is it called Wikibooks? It should be called Wikitextbooks! If it is for textbooks why does it contain cookbooks? For textbooks it's not supposed to have a [[Wikibooks:Featured books]]. [[User:Vivairan2|Vivairan2]] ([[User talk:Vivairan2|discuss]] • [[Special:Contributions/Vivairan2|contribs]]) 09:20, 1 September 2026 (UTC)

:It's &quot;textbooks&quot; broadly construed: guides, manuals, how-tos, etc. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 11:15, 1 September 2026 (UTC)
::So we should change &quot;Wikibooks:Featured books&quot; to &quot;Wikibooks:Featured texts&quot;. [[User:Vivairan2|Vivairan2]] ([[User talk:Vivairan2|discuss]] • [[Special:Contributions/Vivairan2|contribs]]) 11:17, 1 September 2026 (UTC)
:::I disagree and even if I agreed, it would be priority #49,389. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 11:20, 1 September 2026 (UTC)
::::It's according to community consensus that says this website contains textbooks not books. [[User:Vivairan2|Vivairan2]] ([[User talk:Vivairan2|discuss]] • [[Special:Contributions/Vivairan2|contribs]]) 11:23, 1 September 2026 (UTC)
:::::&quot;[[wb:WIW|Simply, Wikibooks is a collection of open-content textbooks.]]&quot; [[User:Vivairan2|Vivairan2]] ([[User talk:Vivairan2|discuss]] • [[Special:Contributions/Vivairan2|contribs]]) 11:26, 1 September 2026 (UTC)
:Most textbooks are made by collaboration of some authors, co-authors and editors. Wikibooks help pages and guidelines remain silent when it comes to stages of writing a new texbooks. Even [[Using Wikibooks]] is not complete emough for enthusiasts. --[[User:Vivairan2|Vivairan2]] ([[User talk:Vivairan2|discuss]] • [[Special:Contributions/Vivairan2|contribs]]) 18:13, 3 September 2026 (UTC)
:@[[User:Vivairan2|Vivairan2]], In my opinion this is a good question. I wish more users would chime in. [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 16:10, 19 September 2026 (UTC)

== Wishlist 2027, invitation to share feedback ==

Hi, I’m [[m:User:SPerry-WMF|Sonja]] and I lead some of the [[mw:Contributors|teams]] at the Foundation who will be responsible for picking up wish work under the new wishlist process.

As you may know, the [[m:Community_Wishlist|Community Wishlist]] started out as an annual process through which Wikimedia contributors submit and vote on technical improvements they would like the Wikimedia Foundation to work on. The main goal of it is and has been to improve the editing experience by making changes and features the community asks for specifically.

In recent years, the process behind the wishlist has changed, and we’ve heard from many of you that it no longer meets many community members’ needs. So now, the Foundation is designing a new process with the community to improve how wishes are triaged, voted on, and prioritized in a way that is transparent, balanced across project families and language editions, and takes into account what the Foundation can deliver.

I would like to get community input specifically on these three stages of the Wishlist process:

* The [[m:Special:MyLanguage/Community_Wishlist/Community_Wishlist_2027#triage|'''triage stage''']], meaning how wishes are fleshed out, organized and filtered prior to voting
** We recommend to have a working group, including volunteers from various wikis and Wikimedia Foundation staff to work through this together
* The [[m:Special:MyLanguage/Community_Wishlist/Community_Wishlist_2027#vote|'''voting stage''']], including who may vote and how votes are structured
* The [[m:Special:MyLanguage/Community_Wishlist/Community_Wishlist_2027#postvote|'''post-vote stage''']], including how to bring equity into what work is prioritized
** One way to do this is to rank wishes within 3 categories: Large Wikipedias or covering all wikis, small and medium-sized Wikipedias, and '''sister projects''', so that top-voted wishes from smaller projects also get attention

This message is an abstract of the full proposed process. As you [[m:Special:MyLanguage/Community_Wishlist/Community_Wishlist_2027|read the proposed ideas on Meta]] (available in your language), please speak up about whether you think this will work well or if there are ways to make it stronger.

Regarding the timeline, this consultation is open for two weeks. You can post your feedback on Meta (in your preferred language) or in response below.

For this year’s cycle, [[m:Special:MyLanguage/Community_Wishlist/Community_Wishlist_2027#timeline|we plan]] to have the wish submission period in late October/early November and the triage process completed by late November. To respect the end-of-year holiday season, voting would happen in early to mid January. This first voting cycle is meant as a first step to try out a new process, and there will be more opportunities to provide feedback along the way, so that we can figure out the best process for future years together.

[[oldwikisource:M:User:SPerry-WMF|SPerry-WMF]], delivered by [[User:Trizek (WMF)|Trizek (WMF)]] ([[User talk:Trizek (WMF)|discuss]] • [[Special:Contributions/Trizek (WMF)|contribs]]) 13:52, 1 September 2026 (UTC)

:Thank you to everyone who engaged in the discussion around [[m:Talk:Community_Wishlist/Community_Wishlist_2027|the proposal from August 26]]. We've processed your feedback and [https://meta.wikimedia.org/w/index.php?title=Community_Wishlist/Community_Wishlist_2027&amp;diff=prev&amp;oldid=31041090 made changes] accordingly. Note that we weren’t able to implement all of it for this cycle, mostly for logistical reasons, but this is merely meant to be a first step and we will continue to improve this process with you all before we run through the next cycle. We plan to use [[m:Community_Wishlist/Community_Wishlist_2027#Updated_Community_Wishlist_Process_2027/2028|this updated version]] for the Wishlist 2027, and we look forward to hearing from you all during the submission and voting periods.
:[[:M:User:SPerry-WMF|SPerry-WMF]], delivered by [[User:Trizek (WMF)|Trizek (WMF)]] ([[User talk:Trizek (WMF)|discuss]] • [[Special:Contributions/Trizek (WMF)|contribs]]) 14:49, 17 September 2026 (UTC)
::@[[User:SPerry-WMF|User:SPerry-WMF]],@[[User:Trizek (WMF)|Trizek (WMF)]]: Thank you for posting info regarding the wishlist to the English Wikibooks. I am sure there are many new users here who can benefit.
::I used to participate in those discussions years ago and I know a lot of effort goes into making discussions useful not only for users of wikipedia, but also for the many language versions of the smaller wikimedia projects such as Wikibooks. [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 16:28, 19 September 2026 (UTC)

== How Do I Get My Book On A Shelf? ==

Help, I don't know how shelves work. I don't know how to put my book on a shelf. Can anyone help?
The book is called''' Art And AI''' [[User:3MMPEYTON|3MMPEYTON]] ([[User talk:3MMPEYTON|discuss]] • [[Special:Contributions/3MMPEYTON|contribs]]) 23:00, 8 September 2026 (UTC)
: Which shelf are you referring? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:45, 10 September 2026 (UTC)

== Who is allowed to delete pages here? ==

On Aug 14, 2026 a user by the name of Max deleted a page I created in my user space. I don't see max in the list of admins here. Do they have the right to delete pages? Is there any documentation here I can consult?

Thanks in advance, [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 22:38, 15 September 2026 (UTC)

:We have local admins who have the technical ability to delete pages and virtually all material deleted here would be done by us (I'm one of them). A fairly small amount of users have global rights across all Wikimedia Foundation wikis and they will very rarely make deletions (e.g. if there are some kind of legal implications to material). [[User:Ottawahitech/American politics]] was deleted by [[User:Max]], who has [[Special:UserRights/Max|no special rights here]] but is one of the [[:m:Global sysops|global sysops]] I mentioned earlier. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 22:55, 15 September 2026 (UTC)
: Probably unrelated to the above, but Ottawahitech should do that with their account, unless if they are blocked. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 23:33, 15 September 2026 (UTC)
::Agreed and [[User:Ottawahitech]] is not blocked here, so no idea why he's using a temp account. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 23:43, 15 September 2026 (UTC)
:::There may be many reasons registered users are &quot;editing&quot; without logging in. Is it possible that they want to go about peacefully without attracting too much attention? [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 15:01, 16 September 2026 (UTC)
:::: We neither have a policy nor a guideline about this, probably. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:12, 20 September 2026 (UTC)
::::Notwithstanding a claim that the temp account is actually User:Ottawahitech, we have no idea that they are the same person. If the temp account is the same person, and they want to have a user space page, they can create temp account ones. The registered user account pages and intended for that registered user account and not as a dumping ground for anyone to create pages. [[User:MarcGarver|MarcGarver]] ([[User talk:MarcGarver|discuss]] • [[Special:Contributions/MarcGarver|contribs]]) 08:29, 13 October 2026 (UTC)

== Assistance to get page reviewed ==

My page is a translation page: [[Baiyi Zhuan]] 

It is a single page, it is translated according to my own ability and familiarity with the language with a disclosure on external tools. I would like it to get reviewed if possible as I do not have the rights.  [[User:Taitesena|Taitesena]] ([[User talk:Taitesena|discuss]] • [[Special:Contributions/Taitesena|contribs]]) 11:19, 18 September 2026 (UTC)

== Translation of books ==

Hello,
I would like to translate books from other Wikibooks into English. Are there any guidelines regarding how to do this? [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:34, 20 September 2026 (UTC)
: This has yet to be expanded, but you might want to take a look at [[Wikibooks:Content translation]]. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:13, 20 September 2026 (UTC)

== Feedback on Wikibooks redirect ==

I would like your feedback on my proposal to make [[Wikibooks:Username|this page]] redirect to [[Using Wikibooks/Setting Up A User Account#Choosing a Username|this page]]? I would do it myself, but it is not possible due to the fact that [[Wikibooks:Username]] can only be made by admins. This is because [[Wikibooks:Username policy]] also links to [[Using Wikibooks/Setting Up A User Account#Choosing a Username|this page]]. Regards, [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 04:37, 21 September 2026 (UTC)

:{{support}} ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 00:00, 22 September 2026 (UTC)

This seems like a good idea to me. [[User:Alextejthompson|''Alextejthompson'']] (''Ping me or leave a message on my [[User talk:Alextejthompson|talk page]]'') 17:49, 21 September 2026 (UTC)

== Pages created by [[User:Sisterian]] ==

I have checked with AI checkers (GPTZero, ZeroGPT) and they claim that these pages have been made with the use of GenAI. I do not know whether this is correct or not; because yes, AI checkers can and do make mistakes. I have tried reaching out to the person via talk page, to no response. I am asking for input just to see what the future of these pages are. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 12:00, 22 September 2026 (UTC)

:Thank you for flagging this @[[User:TechVindicator|TechVindicator]]. I have looked at these pages personally, and there is fairly conclusive evidence that this user has been using genAI/LLMs for their contributions. I have warned them accordingly. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 20:50, 22 September 2026 (UTC)

== I'm in the process of creating a separate page describing the removal of admin permissions ==
As the section title says, please see [[User:Codename Noreste/sandbox]] and feel free to make any adjustments. We might consider moving this to [[Wikibooks:Administrators/De-adminship]] someday. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:05, 24 September 2026 (UTC)

== Your feedback wanted: Remove ''(Language link added:) and similar'' edits from Special:RecentChanges ==
''(Apologies for posting in English. You can help by translating it)''

Hello, I’m Danny from [[:en:w:Wikimedia_Deutschland|Wikimedia Deutschland’s]] [[m:Wikidata_For_Wikimedia_Projects|Wikidata For Wikimedia Projects]] team.&lt;br/&gt;
We have been investigating and examining how Wikidata’s use in the [[Special:RecentChanges]] and [[Special:Watchlist]] pages can be made to be more useful, or less ‘noisy’ (fewer edits that have little value to the reader).

We are currently exploring to make a change in the volume and the type of Wikidata edits that appear in these pages, and '''we need your feedback''' to help us ensure this is a positive change for the Wikis and won’t disrupt your workflows.&lt;br/&gt;
Language links are also known as sitelinks or interlanguage links and describe when a Wikidata item is connected to a Wiki, adding it to the language dropdown tool for other connected Wikis.
[[File:Types of Lang Link changes.png|x350px|frame|A variety of &quot;Language Link&quot; edits as seen in the Recent Changes feed]]

The request for feedback is whether you support the removal of these language link edits from the Recent Changes and Watchlist feed, or would you oppose such a change and if so, why?
Please share you thoughts on the dedicated '''[[m:Talk:Wikidata_For_Wikimedia_Projects/Clearer_Wikidata_Edit_Summaries/Hide_Language_Link_edits|metawiki Talk page]]'''. 

Further information about this change: [[m:Wikidata_For_Wikimedia_Projects/Clearer_Wikidata_Edit_Summaries/Hide_Language_Link_edits|m:Wikidata_For_Wikimedia_Projects/Hide_Language_Link_edits]]

Thank you for any participation or feedback you give, -- [[m:User:Danny_Benjafield_(WMDE)|User:Danny Benjafield (WMDE)]] 11:46, 25 September 2026 (UTC)
&lt;!-- Message sent by User:Danny Benjafield (WMDE)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=User:Danny_Benjafield_(WMDE)/MassMessage_test_list&amp;oldid=31080832 --&gt;

== FlaggedRevs again ==
&lt;div class=&quot;cd-moveMark&quot;&gt;''Moved to [[Wikibooks:Reading room/Proposals#FlaggedRevs again]].  [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:01, 1 October 2026 (UTC)''&lt;/div&gt;

== Wikidata Sitelink changes in Recent Changes and Watchlist ==
''(Apologies for cross-posting in English, translating it will help spread the message)''

Editors on group 1 wikis, including Wikiquote, Wikibooks, Wikiversity, Wikivoyage, and Wikisource, will no longer see notifications on [[Special:RecentChanges|Recent Changes]] and [[Special:Watchlist|Watchlist]] when a link to ''another'' language version of a page is added, removed, or changed in its Wikidata item. This change will begin on '''October 5 at 07:00 UTC''' as a two-week trial to reduce high-volume, low-value notifications and make higher-value changes easier to identify. Editors who rely on these notifications should be aware of the change and can share feedback or concerns on the [[m:Wikidata For Wikimedia Projects/Clearer Wikidata Edit Summaries/Hide Language Link edits|project]] or [[m:Talk:Wikidata_For_Wikimedia_Projects/Clearer_Wikidata_Edit_Summaries/Hide_Language_Link_edits|talk page]].&lt;br/&gt;Please reach out if you have any questions, thank you! -- [[User:Danny_Benjafield_(WMDE)|Danny Benjafield (WMDE)]] ([[User_talk:Danny_Benjafield_(WMDE)|talk]])  sent via [[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 12:42, 1 October 2026 (UTC)
&lt;!-- Message sent by User:Danny Benjafield (WMDE)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=User:Danny_Benjafield_(WMDE)/MassMessage_test_list&amp;oldid=31106967 --&gt;

== Approved Revs extension ==
If we were to have this extension, we should only limit this to the Wikijunior namespace, since we will eventually stop using FlaggedRevs, unless if we want Approved Revs to work in another namespace.

Remember, this is not a vote, but an overall discussion. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 01:17, 11 October 2026 (UTC)</text>
      <sha1>1wf96uab4qrgmmmubxwygklvov6drsn</sha1>
    </revision>
    <revision>
      <id>4675806</id>
      <parentid>4675805</parentid>
      <timestamp>2026-10-13T08:30:19Z</timestamp>
      <contributor>
        <username>MarcGarver</username>
        <id>134830</id>
      </contributor>
      <minor />
      <comment>/* Who is allowed to delete pages here? */</comment>
      <origin>4675806</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="22185" sha1="k1o8wytplel4x25txd148xmweur100v" xml:space="preserve">__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]]

== Call for administrators ==

Any experienced editor who has a good understanding of Wikibooks' policies should consider applying for administrator permissions at [[Wikibooks:Requests for permissions]]. Thank you. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 22:10, 5 August 2026 (UTC)

:Is there a page here that describes what admins do? I am curious because I checked [https://en.wikibooks.org/wiki/Special:ListUsers?username=&amp;group=sysop&amp;wpsubmit=&amp;wpFormIdentifier=mw-listusers-form&amp;limit=50 List of admins] and I see that there are already quite a few admins here and wonder which areas have a shortage.
:Just curious. [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 00:56, 16 September 2026 (UTC)
::[[Wikibooks:Administrators]]. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 01:09, 16 September 2026 (UTC)

== August 2026 Wikimedia Café meetups regarding [https://meta.wikimedia.org/wiki/Next_25 Next 25] ==

&lt;div class=&quot;border-box&quot; style=&quot;background-color: var(--background-color-warning-subtle, #f8eaba); max-width: 875px; padding: 5px; border: 1px solid black; margin: 5px; color: var(--clr-dark)&quot;&gt;
&lt;div class=&quot;box&quot; style=&quot;float:left; padding-top: 10px; padding-right: 10px; padding-left: 10px; padding-bottom: 10px;&quot;&gt;[[File:Wikimedia Café logo in plain SVG format.svg|60px|alt=The logo for the Wikimedia Café]]&lt;/div&gt;
Hello! There will be two '''[https://meta.wikimedia.org/wiki/Wikimedia_Caf%C3%A9 Wikimedia Café]''' discussion opportunities in August. Both sessions will focus on [https://meta.wikimedia.org/wiki/Next_25 the Next 25 initiative], including [https://meta.wikimedia.org/wiki/Next_25/A_proposal_to_frame_Next_25 framing the initiative]. Participants may attend either or both Café sessions. 


#'''29 August 2026 15:00 UTC''' ([https://zonestamp.toolforge.org/1788015600 timestamp converter]), at a time friendly to the Americas, Africa, and Europe
#'''30 August 2026 03:00 UTC''' ([https://zonestamp.toolforge.org/1788058800 timestamp converter]), at a time friendly to Asia and the Pacific

Please see the [https://meta.wikimedia.org/wiki/Wikimedia_Caf%C3%A9 Café] page for more information, including [https://meta.wikimedia.org/wiki/Wikimedia_Caf%C3%A9#Agenda._This_will_be_an_approximately_1_hour_Caf%C3%A9_session agenda details] and [https://meta.wikimedia.org/wiki/Wikimedia_Caf%C3%A9#How_to_attend_the_session how to register]!

To subscribe or unsubscribe for Café notices on your talk page please [https://meta.wikimedia.org/wiki/Global_message_delivery/Targets/Wikimedia_Caf%C3%A9 go here].
&lt;br /&gt;
[[File:Buntstifte Eberhard Faber crop 64h.jpg|860px|alt=cropped image of colored pencils]]&lt;/div&gt;
&lt;span style=&quot;white-space:nowrap;&quot;&gt;[[User:Pine|&lt;span style=&quot;color:#01796f; text-shadow:#00BFFF 0 0 1.0em&quot;&gt;༄ᨒ𖠰 Pine&lt;/span&gt;]] [[User talk:Pine|&lt;span style=&quot;color:DeepSkyBlue&quot;&gt;(&lt;b style=&quot;color:#FFDF00;text-shadow:#FFDF00 0 0 1.0em&quot;&gt;✉&lt;/b&gt;)&lt;/span&gt;]]&lt;/span&gt; 01:32, 17 August 2026 (UTC)

== Wikibooks project is not defined by goal ==

If it is for texbooks why is it called Wikibooks? It should be called Wikitextbooks! If it is for textbooks why does it contain cookbooks? For textbooks it's not supposed to have a [[Wikibooks:Featured books]]. [[User:Vivairan2|Vivairan2]] ([[User talk:Vivairan2|discuss]] • [[Special:Contributions/Vivairan2|contribs]]) 09:20, 1 September 2026 (UTC)

:It's &quot;textbooks&quot; broadly construed: guides, manuals, how-tos, etc. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 11:15, 1 September 2026 (UTC)
::So we should change &quot;Wikibooks:Featured books&quot; to &quot;Wikibooks:Featured texts&quot;. [[User:Vivairan2|Vivairan2]] ([[User talk:Vivairan2|discuss]] • [[Special:Contributions/Vivairan2|contribs]]) 11:17, 1 September 2026 (UTC)
:::I disagree and even if I agreed, it would be priority #49,389. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 11:20, 1 September 2026 (UTC)
::::It's according to community consensus that says this website contains textbooks not books. [[User:Vivairan2|Vivairan2]] ([[User talk:Vivairan2|discuss]] • [[Special:Contributions/Vivairan2|contribs]]) 11:23, 1 September 2026 (UTC)
:::::&quot;[[wb:WIW|Simply, Wikibooks is a collection of open-content textbooks.]]&quot; [[User:Vivairan2|Vivairan2]] ([[User talk:Vivairan2|discuss]] • [[Special:Contributions/Vivairan2|contribs]]) 11:26, 1 September 2026 (UTC)
:Most textbooks are made by collaboration of some authors, co-authors and editors. Wikibooks help pages and guidelines remain silent when it comes to stages of writing a new texbooks. Even [[Using Wikibooks]] is not complete emough for enthusiasts. --[[User:Vivairan2|Vivairan2]] ([[User talk:Vivairan2|discuss]] • [[Special:Contributions/Vivairan2|contribs]]) 18:13, 3 September 2026 (UTC)
:@[[User:Vivairan2|Vivairan2]], In my opinion this is a good question. I wish more users would chime in. [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 16:10, 19 September 2026 (UTC)

== Wishlist 2027, invitation to share feedback ==

Hi, I’m [[m:User:SPerry-WMF|Sonja]] and I lead some of the [[mw:Contributors|teams]] at the Foundation who will be responsible for picking up wish work under the new wishlist process.

As you may know, the [[m:Community_Wishlist|Community Wishlist]] started out as an annual process through which Wikimedia contributors submit and vote on technical improvements they would like the Wikimedia Foundation to work on. The main goal of it is and has been to improve the editing experience by making changes and features the community asks for specifically.

In recent years, the process behind the wishlist has changed, and we’ve heard from many of you that it no longer meets many community members’ needs. So now, the Foundation is designing a new process with the community to improve how wishes are triaged, voted on, and prioritized in a way that is transparent, balanced across project families and language editions, and takes into account what the Foundation can deliver.

I would like to get community input specifically on these three stages of the Wishlist process:

* The [[m:Special:MyLanguage/Community_Wishlist/Community_Wishlist_2027#triage|'''triage stage''']], meaning how wishes are fleshed out, organized and filtered prior to voting
** We recommend to have a working group, including volunteers from various wikis and Wikimedia Foundation staff to work through this together
* The [[m:Special:MyLanguage/Community_Wishlist/Community_Wishlist_2027#vote|'''voting stage''']], including who may vote and how votes are structured
* The [[m:Special:MyLanguage/Community_Wishlist/Community_Wishlist_2027#postvote|'''post-vote stage''']], including how to bring equity into what work is prioritized
** One way to do this is to rank wishes within 3 categories: Large Wikipedias or covering all wikis, small and medium-sized Wikipedias, and '''sister projects''', so that top-voted wishes from smaller projects also get attention

This message is an abstract of the full proposed process. As you [[m:Special:MyLanguage/Community_Wishlist/Community_Wishlist_2027|read the proposed ideas on Meta]] (available in your language), please speak up about whether you think this will work well or if there are ways to make it stronger.

Regarding the timeline, this consultation is open for two weeks. You can post your feedback on Meta (in your preferred language) or in response below.

For this year’s cycle, [[m:Special:MyLanguage/Community_Wishlist/Community_Wishlist_2027#timeline|we plan]] to have the wish submission period in late October/early November and the triage process completed by late November. To respect the end-of-year holiday season, voting would happen in early to mid January. This first voting cycle is meant as a first step to try out a new process, and there will be more opportunities to provide feedback along the way, so that we can figure out the best process for future years together.

[[oldwikisource:M:User:SPerry-WMF|SPerry-WMF]], delivered by [[User:Trizek (WMF)|Trizek (WMF)]] ([[User talk:Trizek (WMF)|discuss]] • [[Special:Contributions/Trizek (WMF)|contribs]]) 13:52, 1 September 2026 (UTC)

:Thank you to everyone who engaged in the discussion around [[m:Talk:Community_Wishlist/Community_Wishlist_2027|the proposal from August 26]]. We've processed your feedback and [https://meta.wikimedia.org/w/index.php?title=Community_Wishlist/Community_Wishlist_2027&amp;diff=prev&amp;oldid=31041090 made changes] accordingly. Note that we weren’t able to implement all of it for this cycle, mostly for logistical reasons, but this is merely meant to be a first step and we will continue to improve this process with you all before we run through the next cycle. We plan to use [[m:Community_Wishlist/Community_Wishlist_2027#Updated_Community_Wishlist_Process_2027/2028|this updated version]] for the Wishlist 2027, and we look forward to hearing from you all during the submission and voting periods.
:[[:M:User:SPerry-WMF|SPerry-WMF]], delivered by [[User:Trizek (WMF)|Trizek (WMF)]] ([[User talk:Trizek (WMF)|discuss]] • [[Special:Contributions/Trizek (WMF)|contribs]]) 14:49, 17 September 2026 (UTC)
::@[[User:SPerry-WMF|User:SPerry-WMF]],@[[User:Trizek (WMF)|Trizek (WMF)]]: Thank you for posting info regarding the wishlist to the English Wikibooks. I am sure there are many new users here who can benefit.
::I used to participate in those discussions years ago and I know a lot of effort goes into making discussions useful not only for users of wikipedia, but also for the many language versions of the smaller wikimedia projects such as Wikibooks. [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 16:28, 19 September 2026 (UTC)

== How Do I Get My Book On A Shelf? ==

Help, I don't know how shelves work. I don't know how to put my book on a shelf. Can anyone help?
The book is called''' Art And AI''' [[User:3MMPEYTON|3MMPEYTON]] ([[User talk:3MMPEYTON|discuss]] • [[Special:Contributions/3MMPEYTON|contribs]]) 23:00, 8 September 2026 (UTC)
: Which shelf are you referring? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:45, 10 September 2026 (UTC)

== Who is allowed to delete pages here? ==

On Aug 14, 2026 a user by the name of Max deleted a page I created in my user space. I don't see max in the list of admins here. Do they have the right to delete pages? Is there any documentation here I can consult?

Thanks in advance, [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 22:38, 15 September 2026 (UTC)

:We have local admins who have the technical ability to delete pages and virtually all material deleted here would be done by us (I'm one of them). A fairly small amount of users have global rights across all Wikimedia Foundation wikis and they will very rarely make deletions (e.g. if there are some kind of legal implications to material). [[User:Ottawahitech/American politics]] was deleted by [[User:Max]], who has [[Special:UserRights/Max|no special rights here]] but is one of the [[:m:Global sysops|global sysops]] I mentioned earlier. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 22:55, 15 September 2026 (UTC)
: Probably unrelated to the above, but Ottawahitech should do that with their account, unless if they are blocked. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 23:33, 15 September 2026 (UTC)
::Agreed and [[User:Ottawahitech]] is not blocked here, so no idea why he's using a temp account. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 23:43, 15 September 2026 (UTC)
:::There may be many reasons registered users are &quot;editing&quot; without logging in. Is it possible that they want to go about peacefully without attracting too much attention? [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 15:01, 16 September 2026 (UTC)
:::: We neither have a policy nor a guideline about this, probably. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:12, 20 September 2026 (UTC)
::::Notwithstanding a claim that the temp account is actually User:Ottawahitech, we have no idea that they are the same person. If the temp account is the same person, and they want to have a user space page, they can create temp account ones. The registered user account pages are intended for that registered user account and not as a dumping ground for anyone to create pages. [[User:MarcGarver|MarcGarver]] ([[User talk:MarcGarver|discuss]] • [[Special:Contributions/MarcGarver|contribs]]) 08:29, 13 October 2026 (UTC)

== Assistance to get page reviewed ==

My page is a translation page: [[Baiyi Zhuan]] 

It is a single page, it is translated according to my own ability and familiarity with the language with a disclosure on external tools. I would like it to get reviewed if possible as I do not have the rights.  [[User:Taitesena|Taitesena]] ([[User talk:Taitesena|discuss]] • [[Special:Contributions/Taitesena|contribs]]) 11:19, 18 September 2026 (UTC)

== Translation of books ==

Hello,
I would like to translate books from other Wikibooks into English. Are there any guidelines regarding how to do this? [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:34, 20 September 2026 (UTC)
: This has yet to be expanded, but you might want to take a look at [[Wikibooks:Content translation]]. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:13, 20 September 2026 (UTC)

== Feedback on Wikibooks redirect ==

I would like your feedback on my proposal to make [[Wikibooks:Username|this page]] redirect to [[Using Wikibooks/Setting Up A User Account#Choosing a Username|this page]]? I would do it myself, but it is not possible due to the fact that [[Wikibooks:Username]] can only be made by admins. This is because [[Wikibooks:Username policy]] also links to [[Using Wikibooks/Setting Up A User Account#Choosing a Username|this page]]. Regards, [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 04:37, 21 September 2026 (UTC)

:{{support}} ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 00:00, 22 September 2026 (UTC)

This seems like a good idea to me. [[User:Alextejthompson|''Alextejthompson'']] (''Ping me or leave a message on my [[User talk:Alextejthompson|talk page]]'') 17:49, 21 September 2026 (UTC)

== Pages created by [[User:Sisterian]] ==

I have checked with AI checkers (GPTZero, ZeroGPT) and they claim that these pages have been made with the use of GenAI. I do not know whether this is correct or not; because yes, AI checkers can and do make mistakes. I have tried reaching out to the person via talk page, to no response. I am asking for input just to see what the future of these pages are. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 12:00, 22 September 2026 (UTC)

:Thank you for flagging this @[[User:TechVindicator|TechVindicator]]. I have looked at these pages personally, and there is fairly conclusive evidence that this user has been using genAI/LLMs for their contributions. I have warned them accordingly. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 20:50, 22 September 2026 (UTC)

== I'm in the process of creating a separate page describing the removal of admin permissions ==
As the section title says, please see [[User:Codename Noreste/sandbox]] and feel free to make any adjustments. We might consider moving this to [[Wikibooks:Administrators/De-adminship]] someday. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:05, 24 September 2026 (UTC)

== Your feedback wanted: Remove ''(Language link added:) and similar'' edits from Special:RecentChanges ==
''(Apologies for posting in English. You can help by translating it)''

Hello, I’m Danny from [[:en:w:Wikimedia_Deutschland|Wikimedia Deutschland’s]] [[m:Wikidata_For_Wikimedia_Projects|Wikidata For Wikimedia Projects]] team.&lt;br/&gt;
We have been investigating and examining how Wikidata’s use in the [[Special:RecentChanges]] and [[Special:Watchlist]] pages can be made to be more useful, or less ‘noisy’ (fewer edits that have little value to the reader).

We are currently exploring to make a change in the volume and the type of Wikidata edits that appear in these pages, and '''we need your feedback''' to help us ensure this is a positive change for the Wikis and won’t disrupt your workflows.&lt;br/&gt;
Language links are also known as sitelinks or interlanguage links and describe when a Wikidata item is connected to a Wiki, adding it to the language dropdown tool for other connected Wikis.
[[File:Types of Lang Link changes.png|x350px|frame|A variety of &quot;Language Link&quot; edits as seen in the Recent Changes feed]]

The request for feedback is whether you support the removal of these language link edits from the Recent Changes and Watchlist feed, or would you oppose such a change and if so, why?
Please share you thoughts on the dedicated '''[[m:Talk:Wikidata_For_Wikimedia_Projects/Clearer_Wikidata_Edit_Summaries/Hide_Language_Link_edits|metawiki Talk page]]'''. 

Further information about this change: [[m:Wikidata_For_Wikimedia_Projects/Clearer_Wikidata_Edit_Summaries/Hide_Language_Link_edits|m:Wikidata_For_Wikimedia_Projects/Hide_Language_Link_edits]]

Thank you for any participation or feedback you give, -- [[m:User:Danny_Benjafield_(WMDE)|User:Danny Benjafield (WMDE)]] 11:46, 25 September 2026 (UTC)
&lt;!-- Message sent by User:Danny Benjafield (WMDE)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=User:Danny_Benjafield_(WMDE)/MassMessage_test_list&amp;oldid=31080832 --&gt;

== FlaggedRevs again ==
&lt;div class=&quot;cd-moveMark&quot;&gt;''Moved to [[Wikibooks:Reading room/Proposals#FlaggedRevs again]].  [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:01, 1 October 2026 (UTC)''&lt;/div&gt;

== Wikidata Sitelink changes in Recent Changes and Watchlist ==
''(Apologies for cross-posting in English, translating it will help spread the message)''

Editors on group 1 wikis, including Wikiquote, Wikibooks, Wikiversity, Wikivoyage, and Wikisource, will no longer see notifications on [[Special:RecentChanges|Recent Changes]] and [[Special:Watchlist|Watchlist]] when a link to ''another'' language version of a page is added, removed, or changed in its Wikidata item. This change will begin on '''October 5 at 07:00 UTC''' as a two-week trial to reduce high-volume, low-value notifications and make higher-value changes easier to identify. Editors who rely on these notifications should be aware of the change and can share feedback or concerns on the [[m:Wikidata For Wikimedia Projects/Clearer Wikidata Edit Summaries/Hide Language Link edits|project]] or [[m:Talk:Wikidata_For_Wikimedia_Projects/Clearer_Wikidata_Edit_Summaries/Hide_Language_Link_edits|talk page]].&lt;br/&gt;Please reach out if you have any questions, thank you! -- [[User:Danny_Benjafield_(WMDE)|Danny Benjafield (WMDE)]] ([[User_talk:Danny_Benjafield_(WMDE)|talk]])  sent via [[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 12:42, 1 October 2026 (UTC)
&lt;!-- Message sent by User:Danny Benjafield (WMDE)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=User:Danny_Benjafield_(WMDE)/MassMessage_test_list&amp;oldid=31106967 --&gt;

== Approved Revs extension ==
If we were to have this extension, we should only limit this to the Wikijunior namespace, since we will eventually stop using FlaggedRevs, unless if we want Approved Revs to work in another namespace.

Remember, this is not a vote, but an overall discussion. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 01:17, 11 October 2026 (UTC)</text>
      <sha1>k1o8wytplel4x25txd148xmweur100v</sha1>
    </revision>
  </page>
  <page>
    <title>TI-Basic Z80 Programming/Conditional Statements</title>
    <ns>0</ns>
    <id>117737</id>
    <revision>
      <id>4675792</id>
      <parentid>4675581</parentid>
      <timestamp>2026-10-13T06:33:10Z</timestamp>
      <contributor>
        <username>Rex Valerio</username>
        <id>3628187</id>
      </contributor>
      <comment>Grammar fixes in conditional statements sections</comment>
      <origin>4675792</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="10632" sha1="q7bjj59z39yqp5x8amdv09mj99jf6c2" xml:space="preserve">__FORCETOC__
'''Conditional statements''' allow a program to take a different path depending on some condition(s). These allow a program to perform a test and then take action based on the result of that test.
== Conditions ==
''Conditions'' are used to control the path of a program. Conditions perform comparisons between different values through the use of ''relational operators''. These include &lt;code&gt;=&lt;/code&gt;, &lt;code&gt;≠&lt;/code&gt;, &lt;code&gt;&gt;&lt;/code&gt;, &lt;code&gt;≥&lt;/code&gt;, &lt;code&gt;&lt;&lt;/code&gt;, &lt;code&gt;≤&lt;/code&gt;. Relational operators always return a true or false result (known as a ''boolean''). To use them, type the values to compare against on either side of the operator:
{{bcode:Example|&lt;nowiki&gt;
X=5
F≥3X+2&lt;/nowiki&gt;
| Where the first line will return true if the value of &lt;code&gt;X&lt;/code&gt; is equal to &lt;code&gt;5&lt;/code&gt;, and where the second line will return true if the value of &lt;code&gt;3X+2&lt;/code&gt; is greater than or equal to &lt;code&gt;F&lt;/code&gt;}}
To type relational operators, press {{TI-Basic/Key|2ND}}&lt;code&gt; '''[TEST]'''&lt;/code&gt;.
You may also want to test two different conditions at the same time and join them using a ''logical operator''. These include &lt;code&gt;and&lt;/code&gt;, &lt;code&gt;or&lt;/code&gt;, &lt;code&gt;xor&lt;/code&gt;, and &lt;code&gt;not&lt;/code&gt;. The basic syntax is similar to that of relational operators.
{{bcode:Example|&lt;nowiki&gt;
X&gt;5 and X&lt;9
F=3 or N=3&lt;/nowiki&gt;
}}
To type logical operators, press {{TI-Basic/Key|2ND}}&lt;code&gt; '''[TEST] ''LOGIC'''''&lt;/code&gt;.
For the following list, consider the format &lt;code&gt;A op B&lt;/code&gt;, where &lt;code&gt;A&lt;/code&gt; and &lt;code&gt;B&lt;/code&gt; are conditions, and &lt;code&gt;op&lt;/code&gt; is a logical operator. Where &lt;code&gt;op&lt;/code&gt; equals...
* &lt;code&gt;and&lt;/code&gt;, the entire condition returns true only if &lt;code&gt;A&lt;/code&gt; and &lt;code&gt;B&lt;/code&gt; are both true.
* &lt;code&gt;or&lt;/code&gt;, the entire condition returns true if at least one of &lt;code&gt;A&lt;/code&gt; and &lt;code&gt;B&lt;/code&gt; is true.
* &lt;code&gt;xor&lt;/code&gt;, the entire condition returns true only if one of &lt;code&gt;A&lt;/code&gt; or &lt;code&gt;B&lt;/code&gt; is true.
The &lt;code&gt;not&lt;/code&gt; operator is special because it does not directly compare two conditions. Instead, it negates the condition(s) that are nested inside. For example:
{{bcode:Example|&lt;nowiki&gt;
not(X=5)&lt;/nowiki&gt;| This will return true if &lt;code&gt;X&lt;/code&gt; does not equal 5.
}}
To use conditional statements, they must be placed into a ''conditional block''. Conditional blocks contain the condition to test and the code to execute. The following sections describe the various types of conditional blocks available in TI-Basic.
== If ==
&lt;code&gt;'''[[../List of Commands/If|If]]'''&lt;/code&gt; ({{TI-Basic/Key|PRGM}}&lt;code&gt; '''''CTL'' 1'''&lt;/code&gt;) requires a criteria argument (condition) to be stated which determines whether the following instruction is to be executed. '''A standard &lt;code&gt;If&lt;/code&gt; block can only run one line of code dependent on the condition. For example, if you needed to execute two or more instructions dependent on the condition, you must use an &lt;code&gt;If Then End&lt;/code&gt; block'''. The argument or arguments is a boolean result, meaning that they will be true or false. If an expression is used as the condition, 0 will represent false and non-0 values will represent true.
=== Syntax ===
{{bcode:Syntax|
If ''condition''
''statement''
}}
* Where &lt;code&gt;''condition''&lt;/code&gt; is any statement resulting in a zero or non zero result, or a conditional operator returning true or false
** If &lt;code&gt;''condition''&lt;/code&gt; returns true or non-zero, &lt;code&gt;''statement''&lt;/code&gt; is executed
** If &lt;code&gt;''condition''&lt;/code&gt; returns false or zero, &lt;code&gt;''statement''&lt;/code&gt; is not executed
=== Examples ===
The following example demonstrates a very basic &lt;code&gt;If&lt;/code&gt; statement:
{{bcode:Example|
:6&amp;rarr;X
:If X&gt;5
:Disp &quot;X &gt; FIVE!&quot;
}}
It will display &lt;code&gt;X &gt; FIVE!&lt;/code&gt; because the condition &lt;code&gt;X&gt;5&lt;/code&gt; returns true (6 is greater than 5). If &lt;code&gt;X&lt;/code&gt; had been 3, the condition would return false (3 is not greater than 5), and nothing would display.
----
The following program will always display &lt;code&gt;Hello World&lt;/code&gt; because the condition 1 will always return 1 (which is non-zero) and therefore the condition is always true:
{{bcode:Example|
:If 1
:Disp &quot;Hello World&quot;
}}
and likewise the following will never display &lt;code&gt;Goodbye World&lt;/code&gt; because it always returns 0.
{{bcode:Example|
:If 0
:Disp &quot;Goodbye World&quot;
}}
== If Then End ==
&lt;code&gt;'''[[../List of Commands/If|If]]'''&lt;/code&gt; &lt;code&gt;'''[[../List of Commands/Then|Then]]'''&lt;/code&gt; &lt;code&gt;'''[[../List of Commands/End|End]]'''&lt;/code&gt; ({{TI-Basic/Key|PRGM}}&lt;code&gt; '''''CTL'' {1,2,7}'''&lt;/code&gt;) conditional statements are used when more than one statement must be executed if a condition returns true. It is very much like the simple &lt;code&gt;If&lt;/code&gt; statement, with the difference that multiple statements are executed instead of one.
=== Syntax ===
The &lt;code&gt;If&lt;/code&gt; statement requires a condition, then a &lt;code&gt;Then&lt;/code&gt; command must follow on the next line, followed by one or more statements which will execute if the condition returns true.  The &lt;code&gt;If&lt;/code&gt; block is ended by a &lt;code&gt;End&lt;/code&gt; statement which tells the calculator that all following statements are to be executed as normal.
{{bcode:Syntax|
:If ''condition''
:Then
:''statement1''
:''statement2''
:''statementn''
:End
}}
*Where &lt;code&gt;condition&lt;/code&gt; is any statement resulting in a true or false result.
**If &lt;code&gt;condition&lt;/code&gt; returns true, &lt;code&gt;statement1, statement2... statementn&lt;/code&gt; (all statements between &lt;code&gt;Then&lt;/code&gt; and &lt;code&gt;End&lt;/code&gt;) will execute
**If &lt;code&gt;condition&lt;/code&gt; returns false, the statements between &lt;code&gt;Then&lt;/code&gt; and &lt;code&gt;End&lt;/code&gt; are not executed, and the program continues with the first statement after &lt;code&gt;End&lt;/code&gt;
It is also common to manually insert a colon directly after the condition of the &lt;code&gt;If&lt;/code&gt;, then type &lt;code&gt;Then&lt;/code&gt;. As an example:
{{bcode:Example|&lt;nowiki&gt;
:If X=5:Then
:&lt;/nowiki&gt;''statements''&lt;nowiki&gt;
:End&lt;/nowiki&gt;
}}
=== Example ===
{{bcode:Example|
:Prompt X
:If X≥5
:Then
:Disp &quot;You entered&quot;,X
:Disp &quot;X ≥ 5&quot;
:End
}}When the program is run, it will be displayed as:

{{Bcode:Output|&lt;nowiki&gt;
X=?5
You entered
               5

X ≥ 5&lt;/nowiki&gt;}}

==If Then Else End==
&lt;code&gt;If Else&lt;/code&gt;s are used when the programmer needs to make a choice where if the condition returns non-zero, statements are executed, but if the condition returns zero, other statements are executed. Either way, only one set of instructions are executed.
===Syntax===
{{bcode:Syntax|
:If ''condition''
:Then
:''trueStatements''
:Else
:''falseStatements''
:End
}}
* Where &lt;code&gt;condition&lt;/code&gt; is any statement resulting in a zero or non zero result.
** If &lt;code&gt;condition&lt;/code&gt; returns nonzero, &lt;code&gt;trueStatements&lt;/code&gt; (instructions between &lt;code&gt;Then&lt;/code&gt; and &lt;code&gt;Else&lt;/code&gt;) will execute, then the instruction after &lt;code&gt;End&lt;/code&gt; is executed
** If &lt;code&gt;condition&lt;/code&gt; returns zero, &lt;code&gt;falseStatements&lt;/code&gt; (instructions between &lt;code&gt;Else&lt;/code&gt; and &lt;code&gt;End&lt;/code&gt;) are executed, then the instruction after &lt;code&gt;End&lt;/code&gt; is executed

=== Examples ===
{{bcode:Example|
:If X≥5
:Then
:Disp &quot;Hello World I'm&quot;
:Disp &quot;Big like five&quot;
:Else
:Disp &quot;Goodbye World&quot;
:Disp &quot;I'm small like four&quot;
:End
}}
Would display
{{bcode:Output|
Hello World I'm
Big like Five
}}
If &lt;code&gt;X&lt;/code&gt; were greater than or equal to five, but would display the following if &lt;code&gt;X&lt;/code&gt; were less than five:
{{bcode:Output|
Goodbye World
I'm small like four
}}
== Else If Workaround ==
It should be noted, TI-Basic does not support else if statements. However, to work around this, nest the conditional blocks in the &lt;code&gt;Else&lt;/code&gt; portion of the block. For example, in a traditional programming language, the following...
{{bcode:Example|
if (condition1) {
    ''statements1''
} else if (condition2) {
    ''statements2''
} else if (condition3) {
    ''statements3''
} else {
    ''statements4''
}
}}
would be notated as, in TI-Basic:
{{bcode:Example|
:If condition1
:Then
:''statements1''
:Else
:If condition2
:Then
:''statements2''
:Else
:If condition3
:Then
:''statements3''
:Else
:''statements4''
:End
:End
:End
}}
However, this is hard to read, so for this example, we will add spaces to make it more clear ('''You cannot add extra white space in practice. You will receive syntax errors.'''):
{{bcode:Example|
:If condition1
:Then
    :''statements1''
:Else
    :If condition2
    :Then
        :''statements2''
    :Else
        :If condition3
        :Then
              :''statements3''
        :Else
              :''statements4''
        :End
    :End
:End
}}

== You try it! ==
Try these examples to practice using conditional statements.
=== Even or Odd ===
Write a program that, when given a number, determines if the number is even or odd and prints the result to the screen.

To help you write this program, you can use &lt;code&gt;'''remainder('''&lt;/code&gt; ({{TI-Basic/Key|MATH}}&lt;code&gt; '''''NUM'' 0'''&lt;/code&gt;). It returns the remainder after dividing a dividend by a divisor. The syntax for &lt;code&gt;remainder(&lt;/code&gt; is:
{{bcode:Syntax|
remainder(dividend,divisor)
}}
Older versions of the TI-84 Plus and the TI-83s do not have a function for calculating the remainder. However, this is still calculatable via an alternate solution:
{{bcode:Syntax|
fPart(A/B)*B
|* &lt;small&gt;Where &lt;code&gt;A&lt;/code&gt; is the dividend and &lt;code&gt;B&lt;/code&gt; is the divisor.}}&lt;/small&gt;
{{Collapse top|title=Solution}}
{{Bcode:Example|
:Prompt N            // Ask user for N
:If remainder(N,2)≠0 // If the remainder of N and 2 does not equal 0,
:Then                // Then,
:Disp &quot;ODD&quot;          // Display &quot;ODD&quot;.
:Else                // Otherwise,
:Disp &quot;EVEN&quot;         // Display &quot;EVEN&quot;.
:End                 // End if block
}}
{{Collapse bottom}}
=== BMI ===
Body mass index (BMI) is a value derived from the mass and height of a person. A person's BMI is calculated with the following formula: &lt;math&gt;\frac{\text{weight}_\text{kg}}{\text{height}_\text{m}^2}&lt;/math&gt;. The value of a person's BMI can be categorized by the following table:
{| class=&quot;wikitable&quot;
|-
! BMI !! Category
|-
| &lt; 18.5 || Underweight
|-
| 18.5-24.9 || Healthy
|-
| 25-29.9|| Overweight
|-
| 30+ || Obese
|}
Write a program that accepts user input for the person's weight in kilograms and their height in meters, and display their BMI and their category.
{{Collapse top|title=Solution}}
{{bcode:Example|&lt;nowiki&gt;
:ClrHome
:Input &quot;HEIGHT = &quot;,H
:Input &quot;WEIGHT = &quot;,W
:W/H^2→X
:Disp &quot;BMI = &quot;,X
:If X&lt;18.5
:Disp &quot;UNDERWEIGHT&quot;
:If X≥18.5 and X≤24.9
:Disp &quot;HEALTHY&quot;
:If X≥25 and X≤29.9
:Disp &quot;OVERWEIGHT&quot;
:If X≥30
:Disp &quot;OBESE&quot;&lt;/nowiki&gt;
}}
{{Collapse bottom}}
{{BottomNav|Input|Loops}}</text>
      <sha1>q7bjj59z39yqp5x8amdv09mj99jf6c2</sha1>
    </revision>
  </page>
  <page>
    <title>Radiation Oncology/Prostate/Screening and Prevention</title>
    <ns>0</ns>
    <id>123555</id>
    <revision>
      <id>4675799</id>
      <parentid>2480252</parentid>
      <timestamp>2026-10-13T07:56:58Z</timestamp>
      <contributor>
        <username>Jcb</username>
        <id>90773</id>
      </contributor>
      <origin>4675799</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="10048" sha1="lb7yg6eoy0px88sqpjcwaxuazb6e7dw" xml:space="preserve">{{Radiation Oncology:TOC}}


&lt;big&gt;'''Prostate Cancer Screening and Prevention'''&lt;/big&gt;


==Screening==
'''''ASCO Clinical Opinion'''''
*'''2012''' {{PMID|22802323}}) -- &quot;Screening for prostate cancer with prostate-specific antigen testing: american society of clinical oncology provisional clinical opinion.&quot; (Basch E, J Clin Oncol. 2012 Aug 20;30(24):3020-5. Epub 2012 Jul 16.)
**In men with a life expectancy &amp;le; 10 years ([http://www.socialsecurity.gov/OACT/population/longevity.html Social Security Calculator]), it is recommended that general screening for prostate cancer with toalPSA be discouraged, because harms seem to outweigh potential benefits
**In men with a life expectancy &gt;10 years, it is recommended that physicians discuss with their patients whether PSA testing for prostate cancer screening is appropriate for them. PSA testing may save lives but is associated with harms, including complications from unnecessary biopsy, surgery or radiation treatment
**It is recommended that information written in lay language be available to clinicians and their patients to facilitate the discussion of the benefits and harms associated with PSA testing before the routine ordering of a PSA test


'''''Randomized'''''
*'''Prostate, Lung, Colorectal, and Ovarian (PLCO) Screening Trial''' (1993-2001) -- screening vs usual care
**Randomized. 76,693 men at 10 U.S. centers. Arm 1) Annual PSA screening x6 years and DRE x4 years vs. Arm 2) usual care. Compliance in Arm 1 85% for PSA and 86% for DRE. Rate of control group screening (&quot;contamination&quot;): PSA screening 40-52% and DRE screening 41-46% by year
**'''2009''' {{PMID|19297565}} -- &quot;Mortality results from a randomized prostate-cancer screening trial.&quot; (Andriole GL, N Engl J Med. 2009 Mar 26;360(13):1310-9. Epub 2009 Mar 18.)Median F/U 7 years
***Outcome: PCA incidence screening group 116/10,000 vs control group 95/10,000 (RR 1.1, SS). Death from PCA 2/10,000 vs 1.7/10,000 (RR 1.13, NS)
***Conclusion: After 7 years, rate of death from PCA is very low, and not different between groups
**'''2011''' {{PMID|21041707}} -- &quot;Comorbidity and Mortality Results From a Randomized Prostate Cancer Screening Trial.&quot; (Crawford ED, J Clin Oncol.  2011 Feb 1;29(4):355-361 .)
***f/u 10 yrs. 9565 deaths, 164 from PCA. In men with no or minimal comorbidity, the decrease in PCA-specific mortality associated with screening was significant (22 v 38 deaths)(NNTT = 5 pts to prevent 1 death at 10 years). In men with at least 1 significant comorbidity, no decrease in PCSM with screening. (62 v 42 deaths; AHR=1.43; p=0.08).
***Conclusion: selective use of PSA screening in men with good health appears to reduce the risk of PCSM with minimal overtreatment.

*'''European Randomized Study of Screening for Prostate Cancer (ERSPC)''' (1991-2003) -- screening vs no screening
**Randomized. 162,387 men, different enrollment strategies in different countries. Age 55-69. Arm 1) PSA screening (DRE and other studies per country; interval per country) vs. Arm 2) no screening. Treated with watchful waiting (15%), surgery (28%), RT (17%), RT+ADT (10%), ADT alone (10%)
**'''Lead Time Bias; 2003''' {{PMID|12813170}} -- &quot;Lead times and overdetection due to prostate-specific antigen screening:estimates from the European Randomized Study of Screening for Prostate Cancer. (Draisma G, J Natl Cancer Inst. 2003 Jun 18;95(12):868-78.)
***Model. 42,376 men enrolled at Rotterdam for ERSPC, with 1498 cases of PCA. 
***Outcome: Mean lead time bias depends on age at screening. At 55, mean lead time bias 12.3 years and overdetection rate of 27%. At 75, mean lead time bias 6.0 years and 56%. For a screening program with 4-year interval from age 55-67, estimated mean lead time 11.2 years with overdetection rate 48%. Lifetime prostate risk raised from 6% to 11% 
***Conclusion: Model-based lead-time estimates supports screening interval &gt;1 year
**'''9-years; 2009''' {{PMID|19297566}} -- &quot;Screening and prostate-cancer mortality in a randomized European study.&quot; (Schroder FH, N Engl J Med. 2009 Mar 26;360(13):1320-8. Epub 2009 Mar 18.) Median F/U 9 years
***Outcome: PCA incidence screening 8% vs control 5%. Death from PCA 3.5/10,000 vs 4.1/10,000 (RR 0.8, SS), rates began to diverge after 8 years; absolute difference 0.07%. NNS 1410:1, NNT 48:1
***Conclusion: PSA-based screening reduced PCA death by 20%, but was associated with a high risk of overdiagnosis
**'''12-years; 2012''' '''(metastatic disease)''' {{PMID|22704366}} [http://www.europeanurology.com/article/S0302-2838(12)00687-2/pdf/Screening+for+Prostate+Cancer+Decreases+the+Risk+of+Developing+Metastatic+Disease%3A+Findings+from+the+European+Randomized+Study+of+Screening+for+Prostate+Cancer+%28ERSPC%29 PDF] -- &quot;Screening for prostate cancer decreases the risk of developing metastatic disease: findings from the European Randomized Study of Screening for Prostate Cancer (ERSPC).&quot; (Schröder FH, Eur Urol. 2012 Nov;62(5):745-52.)
***M+ prostate cancer detected in 256 men screening group vs 410 controls; cumulative incidence of 0.67% vs 0.87% per 1000 men; relative reduction of 30% (intention to screen; 42% for those actually screened). Absolute risk reduction 3.1 per 1000 men screened (0.31%)
***Conclusion: &quot;PSA screening significantly reduces the risk of developing metastatic PCa.&quot;

*'''Quebec LUPCSP''' (1988) -- Screening vs control
**Randomized, 2:1. 46,486 men randomized, true screened 7,348 vs true unscreened 14,2341. Arm 1) annual screening (PSA and DRE) vs Arm 2) control
**'''2004''' {{PMID|15042607}} -- &quot;Screening decreases prostate cancer mortality: 11-year follow-up of the 1988 Quebec prospective randomized controlled trial.&quot; (Labrie F, Prostate, 2004 May 15;59(3):311-8.). Median F/U 7.9 years
***Outcome: PCA death screened 0.1% vs. unscreened 0.5% (RR 0.4, SS)
***Conclusion: Screening showed a 62% reduction in cause-specific mortality, but the absolute benefit was small

'''''Case-control'''''

*'''Veterans Affairs; 2006''' {{PMID|16401808}} &amp;mdash; &quot;The effectiveness of screening for prostate cancer: a nested case-control study.&quot; Concato J et al. Arch Intern Med. 2006 Jan 9;166(1):38-43.
**Case control study. 71,000 men in 10 VA hospitals. 501 pts dx with prostate cancer between 1991-95 and died by 1999. Compared with controls.
**No difference in rate of a screening PSA +/- DRE between cases (14%) and controls (13%)
**Conclusion: screen does not reduce mortality

==Prevention==
*'''REDUCE Trial''' -- dutasteride vs placebo
**Randomized. 6729 men, at increased risk for prostate cancer (50-75 years old, PSA 2.5-10.0, one negative biopsy within 6 months). Arm 1) dutasteride 0.5 mg vs Arm 2) placebo. Primary endpoint: PCA on biopsy at 2 and 4 years
**'''2010''' {{PMID|20357281}} -- &quot;Effect of dutasteride on the risk of prostate cancer.&quot; (Andriole GL,N Engl J Med. 2010 Apr 1;362(13):1192-202.)
***Outcome: incidence of cancer dutasteride 20% vs placebo 25% (SS, risk reduction 28%). No difference in GS 7-10; less GS 8-10 in dutasteride group. But during years 3 &amp; 4, 12 tumors GS 8-10 the dutasteride group, only 1 in placebo group (SS).
***Toxicity: dutasteride improved acute urinary retention (2% vs 7%, SS), but had higher cardiac failure (0.7% vs 0.4%, SS)
***Conclusion: Dutasteride reduced risk of prostate cancer and improved BPH symptoms

*'''SELECT Trial''' (2001-4) - Selenium and Vitamin E Cancer Prevention Trial
**35,533 men, multinational North American (US, Canada, Puerto Rico) - enrolled men 55 yrs or older (or 50 if African American), no prior prostate cancer, PSA &lt; 4, negative DRE. Randomized to selenium (200 µg/d from L-selenomethionine), vs vitamin E (400 IU/d), or both; placebo-controlled. F/U every 6 months; recommended annual PSA and DRE. Pt self-reported prostate cancer events.
**Median age 62. 
**{{PMID|19066370}}, 2009 -- &quot;Effect of selenium and vitamin E on risk of prostate cancer and other cancers: the Selenium and Vitamin E Cancer Prevention Trial (SELECT).&quot; (Lippman SM, JAMA. 2009 Jan 7;301(1):39-51.)
***Median f/u 5.5 yrs. No difference in rate of prostate cancer: 5 yr rate 4.43% (placebo), 4.56% (Se), 4.93% (E), 4.56% (Se+E).
**Conclusion: Selenium,  vitamin E, or both (at the tested doses and formulations) did not prevent prostate cancer

*'''Prostate Cancer Prevention Trial''' (1994-1997)
**18,882 men, multicenter - enrolled men age 55 or older with normal DRE, PSA &lt; 3.0, no medical comorbidities, and AUA score &lt; 20. Randomized to finasteride 5 mg/day vs placebo x 7 yrs (planned). Pts followed with annual DRE and annual PSA. Planned end of study biopsy (min. 6 cores). Biopsy also recommended if abnormal DRE or PSA &gt; 4.
**PSA values were adjusted for men in finasteride group (initially, adjusted PSA = 2.0 x PSA, but changed to 2.3 at man's fourth year); this was done to ensure a biopsy rate that is approximately equal between the groups.
**{{PMID|12824459}}, 2003 &amp;mdash; &quot;The influence of finasteride on the development of prostate cancer.&quot; Thompson IM et al. N Engl J Med. 2003 Jul 17;349(3):215-24.
***Study terminated early in 2003, 15 months before planned end of trial, due to study objective being met. 
***Analysis based on 86.3% of pts who completed 7 yrs by the termination date. Prostate cancer status known (i.e. end of study biopsy completed or interval prostate cancer diagnosis) in 9989 pts (59.6% fin, 63.0% placebo). 9060 pts included in final analysis (excluding pts who had end of study biopsy performed late).  
***Rate of prostate cancer diagnosis: 803(18.4%) F vs 1147(24.4%) P; risk reduction of 24.8%. 45-50% of prostate cancer was diagnosed at end of study biopsy rather than for increased PSA. High grade (Gleason score 7-10) in 280 of 757 graded tumors (37%) of F vs 237 of 1068 (22.2%) of P; RR = 1.67 for high grade. 
***Treatment temporarily discontinued due to side effects in 18.3% of men in F group (vs 9.9% for P).
**Conclusion: Lowers the risk of prostate cancer by 24.8%. However, the finasteride group developed an increased proportion of patients with high grade tumors (Gleason 7-10).</text>
      <sha1>lb7yg6eoy0px88sqpjcwaxuazb6e7dw</sha1>
    </revision>
  </page>
  <page>
    <title>Radiation Oncology/Prostate/Randomized</title>
    <ns>0</ns>
    <id>126115</id>
    <revision>
      <id>4675784</id>
      <parentid>4110875</parentid>
      <timestamp>2026-10-13T05:40:00Z</timestamp>
      <contributor>
        <username>Jcb</username>
        <id>90773</id>
      </contributor>
      <origin>4675784</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="78314" sha1="j6p1hyr800r69r6l5nkwl55aakljmql" xml:space="preserve">{{:Radiation Oncology/Prostate:TOC}}


&lt;big&gt;'''Prostate Cancer: Randomized Evidence'''&lt;/big&gt;


In progress of being cross-linked from the chapter...


==Screening==
*'''Prostate, Lung, Colorectal, and Ovarian (PLCO) Screening Trial''' (1993-2001) -- screening vs usual care
**Randomized. 76,693 men at 10 U.S. centers. Arm 1) Annual PSA screening x6 years and DRE x4 years vs. Arm 2) usual care. Compliance in Arm 1 85% for PSA and 86% for DRE. Rate of control group PSA screening 40-52% and DRE screening 41-46% by year
**'''2009''' {{PMID|19297565}} -- &quot;Mortality results from a randomized prostate-cancer screening trial.&quot; (Andriole GL, N Engl J Med. 2009 Mar 26;360(13):1310-9. Epub 2009 Mar 18.) Median F/U 7 years
***Outcome: PCA incidence screening group 116/10,000 vs control group 95/10,000 (RR 1.1, SS). Death from PCA 2/10,000 vs 1.7/10,000 (RR 1.13, NS)
***Conclusion: After 7 years, rate of death from PCA is very low, and not different between groups
**'''2011''' {{PMID|21041707}} -- &quot;Comorbidity and Mortality Results From a Randomized Prostate Cancer Screening Trial.&quot; (Crawford ED, J Clin Oncol.  2011 Feb 1;29(4):355-361 .)
***f/u 10 yrs. 9565 deaths, 164 from PCA. In men with no or minimal comorbidity, the decrease in PCA-specific mortality associated with screening was significant (22 v 38 deaths)(NNTT = 5 pts to prevent 1 death at 10 years). In men with at least 1 significant comorbidity, no decrease in PCSM with screening. (62 v 42 deaths; AHR=1.43; p=0.08).
***Conclusion: selective use of PSA screening in men with good health appears to reduce the risk of PCSM with minimal overtreatment.

*'''European Randomized Study of Screening for Prostate Cancer (ERSPC)''' (1991-2003) -- screening vs no screening
**Randomized. 162,387 men, different enrollment strategies in different countries. Arm 1) PSA screening (DRE and other studies per country; interval per country) vs. Arm 2) no screening. Treated with watchful waiting (15%), surgery (28%), RT (17%), RT+ADT (10%), ADT alone (10%)
**'''2009''' {{PMID|19297566}} -- &quot;Screening and prostate-cancer mortality in a randomized European study.&quot; (Schroder FH, N Engl J Med. 2009 Mar 26;360(13):1320-8. Epub 2009 Mar 18.) Median F/U 9 years
***Outcome: PCA incidence screening 8% vs control 5%. Death from PCA 3.5/10,000 vs 4.1/10,000 (RR 0.8, SS), rates began to diverge after 8 years. NNS 1410:1, NNT 48:1
***Conclusion: PSA-based screening reduced PCA death by 20%, but was associated with a high risk of overdiagnosis

*'''Quebec LUPCSP''' (1988) -- Screening vs control
**Randomized, 2:1. 46,486 men randomized, true screened 7,348 vs true unscreened 14,2341. Arm 1) annual screening (PSA and DRE) vs Arm 2) control
**'''2004''' {{PMID|15042607}} -- &quot;Screening decreases prostate cancer mortality: 11-year follow-up of the 1988 Quebec prospective randomized controlled trial.&quot; (Labrie F, Prostate, 2004 May 15;59(3):311-8.). Median F/U 7.9 years
***Outcome: PCA death screened 0.1% vs. unscreened 0.5% (RR 0.4, SS)
***Conclusion: Screening showed a 62% reduction in cause-specific mortality, but the absolute benefit was small

==Prevention==
*'''REDUCE Trial''' -- dutasteride vs placebo
**Randomized. 6729 men, at increased risk for prostate cancer (50-75 years old, PSA 2.5-10.0, one negative biopsy within 6 months). Arm 1) dutasteride 0.5 mg vs Arm 2) placebo. Primary endpoint: PCA on biopsy at 2 and 4 years
**'''2010''' {{PMID|20357281}} -- &quot;Effect of dutasteride on the risk of prostate cancer.&quot; (Andriole GL,N Engl J Med. 2010 Apr 1;362(13):1192-202.)
***Outcome: incidence of cancer dutasteride 20% vs placebo 25% (SS, risk reduction 28%). No difference in GS 7-10; less GS 8-10 in dutasteride group
***Toxicity: dutasteride improved acute urinary retention (2% vs 7%, SS), but had higher cardiac failure (0.7% vs 0.4%, SS)
***Conclusion: Dutasteride reduced risk of prostate cancer and improved BPH symptoms

==Patient Decision-Making==
*'''US Multi-Institutional''' -- Patient intervention vs Patient + Support intervention vs Control
**Randomized, 3 arms. 6 US sites. 256 patients with T1-T2b, GS &lt;10, PSA &lt;20. Arm 1) treatment direct (patient receives intervention) vs. Arm 2) treatment supplemented (patient and primary support person receive intervention) vs. Arm 3) control. Intervention was designed to improve communication strategies when meeting with their physician.
**'''2009''' {{PMID|19819096}} -- &quot;Managing uncertainty about treatment decision making in early stage prostate cancer: a randomized clinical trial.&quot; (Mishel MH, Patient Educ Couns. 2009 Dec;77(3):349-59. Epub 2009 Oct 9.)
***Outcome: Improvement in cancer knowledge at 4 weeks and 3 months in both intervention arms; significantly lower rate of decision regret
***Conclusion: Intervention was effective in preparing patients for uncertainty management in prostate cancer

==Primary Treatment Comparisons==
===[[Radiation_Oncology/Prostate/Natural_History#Watchful_Waiting_vs._Prostatectomy|Watchful Waiting vs. Prostatectomy]]===
*'''Scandinavian SPCG-4''' (1989-99) - prostatectomy vs watchful waiting
**Randomized. 695 men, early prostate cancer (T1-T2), biopsy proven. No adjuvant treatment. If symptomatic local progression, treated with orchidectomy or GnRH analog. Clinical follow-up with PSA, exam. Cause of death scored as due to prostate cancer (if progressive distant mets) or due to other causes. 75% had T2 tumors. 
**'''8-years; 2005''' {{PMID|15888698}}  &amp;mdash; &quot;Radical Prostatectomy versus Watchful Waiting in Early Prostate Cancer&quot; Bill-Axelson A et al. N Engl J Med. 2005 May 12;Volume 352(19):1977-1984.
***Median 8.2 yrs f/u. Death due to prostate cancer: 14.4% (WW) vs 8.6%, difference of 5.3% at 10 years.  Difference in overall survival after 10 years: 5% difference (RR=0.74). 
***Conclusion: Treatment of prostate cancer results in fewer cancer related deaths and fewer overall deaths. May not apply to modern era with PSA screening due to lag time and stage migration.

*'''VACURG''' (1967-1975) -- prostatectomy vs. watchful waiting
**Randomized. 111/142 patients, prostate cancer Tis-T2, no palpable tumor, no pelvic staging prior to randomization. Arm 1) Radical prostatectomy vs. Arm 2) Placebo
**'''1988''' {{PMID|3187435}} -- &quot;Treatment of localized prostatic cancer. Radical prostatectomy versus placebo. A 15-year follow-up.&quot; (Madsen PO, Scand J Urol Nephrol Suppl. 1988;110:95-100.)
***Outcome: 
****Stage I: 5-year OS RP 87% vs. placebo 67%, 10-years 48% vs. 43%, 15-years 23% vs. 13%
****Stage II: 5-year RP 92% vs. placebo 90% , 10-years 37% vs 55%, 15-years 17% vs. 20%
***Conclusion: No significant difference in cummulative survival, either by Stage or overall

===Androgen Deprivation vs Radiation Therapy + Androgen Deprivation===
*'''SPCG-7/SFUO-3''' (1996-2002) -- ADT +/- RT
**Randomized. 875 with locally advanced prostate cancer T1b-T2 G2-G3 or T3 (78%) and PSA &lt;70 and N0 (if PSA &gt;11, then PLND). Arm 1) ADT (total androgen blockade x3 months, then continuous flutamide 250 mg) vs. Arm 2) Same ADT + RT 70 Gy to prostate/SV. Breast RT in 80% to prevent gynecomastia
**'''Outcome; 2008''' {{PMID|19091394}} -- &quot;Endocrine treatment, with or without radiotherapy, in locally advanced prostate cancer (SPCG-7/SFUO-3): an open randomised phase III trial.&quot; (Widmark A, Lancet. 2008 Dec 15. [Epub ahead of print]). Median F/U 7.6 years
***Outcome: 10-year CSS ADT 76% vs. ADT + RT 88% (SS); 10-year OS 61% vs. 70% (SS); 10-year bPFS 25% vs. 74% (SS)
***Toxicity: Urethral stricture ADT 0% vs. ADT + RT 2% (SS), urgency 8% vs 14% (SS), urinary incontinence 3% vs. 7% (SS), erectile dysfunction 81% vs. 89% (SS)
***Conclusion: In patients with high risk or locally advance PCA, addition of RT to ADT improved survival, with acceptable side effects

===[[Radiation_Oncology/Prostate/Localized_Prostate_Cancer|Surgery vs Radiation Therapy]]===
*'''Japanese Study Group for Locally Advanced Prostate Cancer''' (1989-1993) -- RP vs EBRT
**Randomized. 95 patients. T2b-T3N0M0. Arm 1) radical prostatectomy + pelvic LN dissection + endocrine therapy vs. Arm 2) Pelvic RT 40-50 Gy + 20 Gy prostate boost  + endocrine therapy. Hormones initiated 8 wks prior to primary therapy (using DES) then continued indefinitely (LHRH agonist +/- antiandrogen, or estrogen).
**'''2006''' {{PMID|17082219}} &amp;mdash; &quot;A randomized trial comparing radical prostatectomy plus endocrine therapy versus external beam radiotherapy plus endocrine therapy for locally advanced prostate cancer: results at median follow-up of 102 months.&quot; (Akakura K et al. Jpn J Clin Oncol. 2006 Dec;36(12):789-93.) Median F/U 8.5 years
***Outcome: 10-year bPFS RP 76% vs. RT 71% (NS); cPFS 83% vs. 66% (p=0.06); DSS 86% vs. 77% (SS); OS 68% vs. 61% (NS)
***Toxicity: Incontinence worse in surgical arm; erectile dysfunction in almost all patients due to ADT
***Conclusion: For locally advanced patients, either RP or EBRT demonstrated favorable outcomes. DSS better with surgery. RT dose 60-70 Gy may not be enough

*'''Uro-Oncology Research Group''' -- radical surgery vs. radiation
**Randomized. 97 patients. cT1-2N0M0. Arm 1) radical prostatectomy vs. Arm 2) megavoltage RT (using Co-60 or betatron) to pelvic field 45-50 Gy + prostate 20 Gy boost. Primary outcome development of metastatic disease by prostatic acid phosphatase, bone scan, and/or pelvic lymphadenectomy
**'''1982''' {{PMID|6811766}} -- &quot;Radical surgery versus radiotherapy for adenocarcinoma of the prostate.&quot; (Paulson DF, J Urol. 1982 Sep;128(3):502-4.)
***Outcome: Actuarial development of mets RP 8% vs. RT 31% (SS)
***Conclusion: Radical surgery more effective than RT

===Surgery vs Radiation Therapy===
*'''Japanese Study Group for Locally Advanced Prostate Cancer''' (1989-1993) -- RP vs EBRT
**Randomized. 95 patients. T2b-T3N0M0. Arm 1) radical prostatectomy + pelvic LN dissection + endocrine therapy vs. Arm 2) Pelvic RT 40-50 Gy + 20 Gy prostate boost  + endocrine therapy. Hormones initiated 8 wks prior to primary therapy (using DES) then continued indefinitely (LHRH agonist +/- antiandrogen, or estrogen).
**'''2006''' {{PMID|17082219}} &amp;mdash; &quot;A randomized trial comparing radical prostatectomy plus endocrine therapy versus external beam radiotherapy plus endocrine therapy for locally advanced prostate cancer: results at median follow-up of 102 months.&quot; (Akakura K et al. Jpn J Clin Oncol. 2006 Dec;36(12):789-93.) Median F/U 8.5 years
***Outcome: 10-year bPFS RP 76% vs. RT 71% (NS); cPFS 83% vs. 66% (p=0.06); DSS 86% vs. 77% (SS); OS 68% vs. 61% (NS)
***Toxicity: Incontinence worse in surgical arm; erectile dysfunction in almost all patients due to ADT
***Conclusion: For locally advanced patients, either RP or EBRT demonstrated favorable outcomes. DSS better with surgery. RT dose 60-70 Gy may not be enough

*'''Uro-Oncology Research Group''' -- radical surgery vs. radiation
**Randomized. 97 patients. cT1-2N0M0. Arm 1) radical prostatectomy vs. Arm 2) megavoltage RT (using Co-60 or betatron) to pelvic field 45-50 Gy + prostate 20 Gy boost. Primary outcome development of metastatic disease by prostatic acid phosphatase, bone scan, and/or pelvic lymphadenectomy
**'''1982''' {{PMID|6811766}} -- &quot;Radical surgery versus radiotherapy for adenocarcinoma of the prostate.&quot; (Paulson DF, J Urol. 1982 Sep;128(3):502-4.)
***Outcome: Actuarial development of mets RP 8% vs. RT 31% (SS)
***Conclusion: Radical surgery more effective than RT

===Radiation Therapy vs Cryotherapy===
*'''University of Calgary''' (1997-2003) -- EBRT vs Cryotherapy
**Randomized. ''Trial closed prematurely due to slowing patient accrual.'' 244 patients of 240 planned, localized prostate cancer (T2-T3N0, PSA &lt;=20 ng/ml, volume &lt;=60 ml), PLND if GS 8+. Excluded clinically bulky patients. Neoadjuvant ADT 3 or 6 months. Arm 1) EBRT (median dose 68 Gy, max 73.5 Gy) using 4F box vs Arm 2) cryoablation using argon/helium and 2 freeze/thaw cycles. Early cryotherapy failures (within 6 months) were not scored as protocol failure, and underwent salvage cryotherapy. QoL assessment. Primary endpoint was failure rate at 3 years
**'''2009''' {{PMID|19937954}} -- &quot;A Randomized Trial of External Beam Radiotherapy Versus Cryoablation in Patients With Localized Prostate Cancer&quot; (Donnelly BJ, Cancer. 2010, Epublished) Median F/U of surviving patients 8.3 years
***Outcome: 3-year failure rate (using nadir+2) cryo 17% vs. EBRT 13% (NS); 5-year rate 25% vs. 25% (NS); 7-year rate 27% vs. 32% (NS); 5-year DSS 96% vs. 96% (NS); 5-year OS 90% vs 88% (NS). Biopsy (+) cryo 8% vs EBRT 29%
***Toxicity: GI Grade 3-4 cryo 3% vs. EBRT 7%; GU Grade 3-4 cryo 9% vs. EBRT 6%; intercourse 4% vs. 26%
***Conclusion: Essentially no difference, but with long-term follow up, trend favors cryotherapy
**'''2009''' {{PMID|19691092}} -- &quot;A randomized trial of external beam radiotherapy versus cryoablation in patients with localized prostate cancer: quality of life outcomes.&quot; (Robinson JW, Cancer. 2009 Oct 15;115(20):4695-704.)
***Outcome: Cryotherapy more acute GU dysfunction (SS), no difference in late GU dysfunction. Cryotherapy worse sexual function at 3 months (SS) and 3 years (SS)
***Conclusion: No long term QoL difference, except worse sexual function after cryoablation

*'''University of Western Ontario''' -- EBRT vs cryotherapy
**Randomized. ''Trial stopped prematurely due to slow accrual.'' 64 of planned 150 patients, cT2c-T3b. Neoadjuvant ADT for 6 months. Arm 1) EBRT vs. Arm 2) cryotherapy
**'''2008''' {{PMID|17579613}} -- &quot;Randomized trial comparing cryoablation and external beam radiotherapy for T2C-T3B prostate cancer.&quot; (Chin JL, Prostate Cancer Prostatic Dis. 2008;11(1):40-5. Epub 2007 Jun 19.)
***Outcome: Treatment failure EBRT 45% vs. cryotherapy 64%. 4-year bPFS 47% vs. 13%. Mean bPFS 41 months vs 28 months. No difference in DSS and OS
***Toxicity: Serious complications uncommon; EBRT more frequent GI toxicity
***Conclusion: Low numbers, but cryotherapy is suboptimal primary therapy for locally advanced prostate cancer

==[[Radiation_Oncology/Prostate/External_Beam_RT#Field_Size|EBRT Technique]]==
===Para-aortic Field===
*'''[[Radiation Oncology/RTOG Trials/7506|RTOG 75-06]]''' (1976-1983)
**Randomized. 523 patients with clinical Stage A2-B N+ or Stage C. Arm 1) Pelvic RT 40-45 Gy + prostate boost 20-25 Gy (minimum 65 Gy) vs. Arm 2) Pelvic + PA RT 40-45 Gy + prostate boost (minimum 65 Gy)
**'''1986''' {{PMID|3514555}} -- &quot;Extended field (periaortic) irradiation in carcinoma of the prostate--analysis of RTOG 75-06.&quot; (Pilepich MV, Int J Radiat Oncol Biol Phys. 1986 Mar;12(3):345-51.). Median F/U 4.2 years
***Outcome: No difference between arms for DFS, DM, OS
***Toxicity: Periaortic RT does not increase bowel injury. Prostate doses &gt;70Gy result in increased bowel injury (20% vs 10% rectal bleed) but not bladder injury
***Conclusion: No benefit to elective peri-aortic irradiation


===Pelvic Field===
*'''GETUG-01''' (French)(1998-2004) -- whole pelvis vs prostate only
**Randomized. 444 patients, T1b-T3 N0 pNx. Randomized to Arm 1) prostate + pelvis vs. Arm 2) prostate only. RT dose pelvis 46 Gy and prostate 66-70 Gy. Stratified into low (T1-2 and GS &lt;=6 and PSA &lt;=12), intermediate, and high risk (T3 or GS &gt;=7 or PSA &gt;=12 ng/ml; 79%) groups. Short term hormonal therapy (6 mos) allowed only for high risk group.
**'''5-years; 2007''' {{PMID|18048817}}  &amp;mdash; &quot;Is There a Role for Pelvic Irradiation in Localized Prostate Adenocarcinoma? Preliminary Results of GETUG-01.&quot; Pommier P et al. J Clin Oncol. 2007 Dec 1;25(34):5366-5373. Median F/U 3.5 years
***5-year outcome: PFS 66% vs. 65% (NS); high risk PFS 63% vs. 60% (NS); low risk PFS 75% vs. 84% (NS)
***Toxicity: Pelvic arm small but nonsignificant late GI toxicity
***Conclusion: no benefit to pelvic radiotherapy

*'''[[Radiation Oncology/RTOG Trials/9413|RTOG 94-13]]''' (1995-99) -- whole pelvis vs prostate only, also 2x2 ADT
**Randomized. 1323 patients. High risk patients with estimated risk of LN involvement of 15% or more by the Roach equation and PSA &lt; 100. Pts with T2c-T4 tumors and Gleason &gt;=6 were allowed regardless of LN risk. 2x2 randomization. Randomized to whole-pelvic (WP) vs prostate-only (PO) RT, and combined neoadjuvant + concurrent hormonal therapy (NCHT) vs adjuvant hormonal therapy (AHT). 
**''RT:'' Dose 70.2 Gy to prostate. For WP RT, 50.4 Gy to pelvis (16x16 field), followed by boost to prostate only.  PO RT was to prostate + SV only. ''Hormones:'' For NCHT, total of 4 months - 2 months before and 2 months during RT. For AHT, began following RT for total of 4 months. 
**'''7-years; 2007''' {{PMID|17531401}} -- &quot;An Update of the Phase III Trial Comparing Whole Pelvic to Prostate Only Radiotherapy and Neoadjuvant to Adjuvant Total Androgen Suppression: Updated Analysis of RTOG 94-13, With Emphasis on Unexpected Hormone/Radiation Interactions.&quot; (Lawton CA, Int J Radiat Oncol Biol Phys. 2007 Nov 1;69(3):646-55.) Median F/U for alive patients 7.0 years
***Outcome: PFS WPRT+NHT 62% vs. PORT+NHT 66% vs. WPRT+AHT 69% vs. PORT+AHT 62% (NS); also no difference in OS. By pairs (as designed), no difference between WPRT and PORT, and no difference between NHT and AHT. No difference in LF or DM
***Toxicity: No difference in RT Grade 3+ toxicity among the 4 arms
***Conclusion: No benefit for NHT + WPRT compared with PORT + AHT

*'''[[Radiation Oncology/RTOG Trials/7706|RTOG 77-06]]''' (1978-1983) - Whole pelvis vs prostate only 
**Randomized. 445 patients. Prostate cancer, Stage A2 (disease on TRUP, poorly differentiated) and Stage B (N0 by lymphangiogram or biopsy). Arm 1) Prostate only 65 Gy vs. Arm 2) Pelvis 45 Gy + prostate boost 20 Gy.
**'''1988''' {{PMID|3058656}} -- &quot;Elective pelvic irradiation in stage A2, B carcinoma of the prostate: analysis of RTOG 77-06.&quot; (Asbell SO, Int J Radiat Oncol Biol Phys. 1988 Dec;15(6):1307-16.) Median F/U 7 years
***Outcome: No difference in terms of LC, DM, DFS, OS.
***Conclusion: No significant benefit for elective pelvic irradiation
***Critique: included pts at low risk for LN involvement

===Dose Escalation===
*'''MRC RT01''' (1998-2002) -- 3D-CRT 64 Gy vs. 74 Gy
**Randomized. 843 men, T1b-T3a (T3 in &lt;20%), PSA &lt;50 ng/mL. . Neoadjuvant AST 3-6 months, then RT Arm 1) 64/32 Gy vs. 74/37 Gy. GTV = prostate +/- SV (depending on risk). CTV = GTV + 0.5 cm. PTV = CTV + 0.5-1.0 cm 
**'''5-years; 2007''' {{PMID|17482880}} -- &quot;Escalated-dose versus standard-dose conformal radiotherapy in prostate cancer: first results from the MRC RT01 randomised controlled trial.&quot; (Dearnaley DP, Lancet Oncol. 2007 Jun;8(6):475-87.) Median F/U 5.2 years
***Outcome: PFS high dose 71% vs. standard dose 60% (SS); clinical PFS 90% vs. 87% (NS)
***By risk group: low-risk 85% vs. 79%, intermediate-risk 79% vs. 70%, high-risk 57% vs. 43%; benefit across all groups
***Toxicity: GI Grade 2+ high dose 33% vs. standard dose 24% (SS); GU Grade 2+ 11% vs. 8% (NS); sexual dysfunction prevalent
***Conclusion: Escalated dose with neoadjuvant AST seems clinically worthwhile, but increased incidence of long-term adverse events

*'''Dutch CKVO96-10''' (1997-2003) -- 3D-CRT 68 Gy vs. 78 Gy
**Randomized. 664 patients, T1b-T4, with PSA &lt; 60 (excluded low risk: T1a, T1b-c with GS&lt;5 and PSA &lt;=4; excluded pN+). Arm 1) 68 Gy vs. Arm 2) 78 Gy. CTV = prostate +/- SV (depending on risk group); PTV = 1.0 cm margin to 68 Gy, then 0.5 mm and 0 mm posteriorly. Prescription dose was to the isocenter. Stratified by risk group. Hormonal therapy in 22%
**'''Toxicity, 2005''' {{PMID|15752881}}  &amp;mdash; &quot;Acute and late complications after radiotherapy for prostate cancer: results of a multicenter randomized trial comparing 68 Gy to 78 Gy.&quot; (Peeters ST, Int J Radiat Oncol Biol Phys. 2005 Mar 15;61(4):1019-34.) 
***No acute toxicity differences (p=NS)
***No late GI and GU toxicity difference (p=NS), except for rectal bleeding requiring laser treatment or transfusion (p = 0.007) and nocturia (p = 0.05)
***Conclusion: Acute and late toxicity higher, but not NS except late rectal bleeding and late nocturia
**'''5-years, 2006''' {{PMID|16648499}} &amp;mdash; &quot;Dose-response in radiotherapy for localized prostate cancer: results of the Dutch multicenter randomized phase III trial comparing 68 Gy of radiotherapy with 78 Gy.&quot; (Peeters ST, J Clin Oncol. 2006 May 1;24(13):1990-6.). Median F/U 4.2 years 
***Outcome: 5-year FFS high-dose 64% vs low-dose 54% (SS). Clinical failure both groups 76% (NS), OS 82% vs. 83% (NS)
***Toxicity: GI Grade 2+ high-dose 32% vs. low-dose 27% (NS), GI Grade 3+ 5% vs. 4% (NS). GU Grade 2+ 39% vs. 41% (NS), GU Grade 3+ 13% vs. 12% (NS).
***Conclusion: Significantly improved FFS, with comparable toxicity

*'''PROG 95-09''' (1996-1999) -- Proton/photon 70.2 Gy vs. 79.2 Gy
**Randomized. 2 institutions (Harvard and Loma Linda). 392 patients, stage T1b-T2b, PSA &lt;15 ng/mL (median PSA 6.3); 75% GS &lt;7. Arm 1) proton boost 19.8/11 GyE followed by photons 50.4/28 vs. Arm 2) proton boost 28.8/16 followed by photons 50.4/28. Proton CTV = prostate + 5 mm margin. PTV = CTV + 7-10 mm. Loma Linda used opposed lateral beams, 250 MeV protons; Harvard used perineal boost, 160 MeV protons. Rectal Lucite probe, inflated with 25-50 mL saline. Photons were 4F plan, photon CTV = prostate/SV + 10 mm margin. No hormones 
**'''5-years; 2005''' {{PMID|16160131}} -- &quot;Comparison of conventional-dose vs high-dose conformal radiation therapy in clinically localized adenocarcinoma of the prostate: a randomized controlled trial.&quot; (Zietman AL, JAMA. 2005 Sep 14;294(10):1233-9.) Median F/U 5.5 years
***Outcome: 5-year bNED 70.2 Gy 61% vs. 79.2 Gy 80% (SS), 50% reduction in risk of failure. LC 48% vs. 67% (SS) No difference in OS 97% vs 96% (NS)
***Risk stratification: low risk (PSA &lt;10, stage &lt;=T2a, GS &lt;7) 60% vs. 80% (SS); high risk 63% vs. 79% (SS). Contemporary intermediate risk 63% vs. 81% (SS), but contemporary high risk (NS, but small number) 
***Late toxicity: Grade 3+ 70.2 Gy 1% vs. 79.2 2%; GU Grade 2 18% vs. 20% (NS), GI Grade 2 8% vs. 17% (SS). Most GI toxicity by 3 years; GU toxicity continuous
***Conclusion: Men with intermediate-risk clinically localized PCA have better bNED with high dose, without worse severe toxicity and with only small increase in G2 GI toxicity
**'''10-years; 2010''' {{PMID|20124169}} -- &quot;Randomized Trial Comparing Conventional-Dose With High-Dose Conformal Radiation Therapy in Early-Stage Adenocarcinoma of the Prostate: Long-Term Results From Proton Radiation Oncology Group/American College of Radiology 95-09.&quot; (Zietman AL, J Clin Oncol. 2010 Mar 1;28(7):1106-11.) Median F/U 8.9 years
***Outcome: 10-year ASTRO (backdating) bPFS low-dose 68% vs. high-dose 83% (SS). For low-risk disease 72% vs 93% (SS); for intermediate-risk 58% vs. 70% (p=0.06). No difference in OS (78% vs 83%)
***Toxicity: Late Grade 2+ low-dose 29% vs. high-dose 39% (SS); Grade 3+ 2% in both arms (NS)
***Conclusion: Long-term advantage for high dose in low/intermediate risk PCA patients, with comparable Grade 3 toxicity


*'''MD Anderson''' (1993-1998) -- 4F 70 Gy vs. 3D-CRT 78 Gy
**Randomized. 301 T1-T3 patients, stratified by PSA &lt;10 (65%), 10-20 (35%), &gt;20 (few). Arm 1) 70 Gy vs. Arm 2) 78 Gy. Technique 4F 46/23, Arm 1) 4F RF 24/12, Arm 2) 3D-CRT 6 fields 32/16. CTV = prostate/SV, margin 1.5 cm anterior/inferior, 1.0 cm posterior/superior. No hormones
**'''8-years; 2008''' {{PMID|17765406}} -- &quot;Long-term results of the M. D. Anderson randomized dose-escalation trial for prostate cancer.&quot; (Kuban DA, Int J Radiat Oncol Biol Phys. 2008 Jan 1;70(1):67-74. Epub 2007 Aug 31.) Median F/U 8.7 years
***8-year outcome: FFF 78 Gy 78% vs. 70 Gy 59% (SS); if PSA &gt;10 78% vs. 39% (SS), clinical failure 7% vs. 15% (SS); if PSA &lt;10 78% vs. 66% (NS)
***By risk group: low risk 88% vs. 63% (SS); intermediate risk 86% vs. 76% (NS); high risk 63% vs. 26% (SS). OS 78% vs. 79% (NS)
***10-year toxicity: GI Grade 3 7% vs. 1% (SS); GI Grade 2+ 26% vs. 13% (SS); GU Grade 3 5% vs. 4% (NS), GU Grade 2+ 13% vs. 8% (NS)
***Conclusion: Dose escalation improved PSA and clinical control, particularly if PSA &gt;10 ng/ml
**'''10-years; 2011''' {{PMID|20493642}} -- &quot;Long-term failure patterns and survival in a randomized dose-escalation trial for prostate cancer. Who dies of disease?&quot; (Kuban DA, Int J Radiat Oncol Biol Phys. 2011 Apr 1;79(5):1310-7. Epub 2010 May 20.) 
***10-year outcome: bDFS of PSA &gt; 10 subset 91% vs. 80% (p=SS). 
***Conclusion: Patients age 70 or older treated to 70 Gy died of prostate cancer as often as other causes, and those receiving 78 Gy never died of prostate cancer within 10 years of follow-up

*'''Ontario EBRT/LDR''' (1992-1997) -- EBRT 66/30 vs. EBRT/LDR 75 (LDR 35 + EBRT 40/20)
**Randomized. 104 patients, locally advanced T2-T3. All underwent staging pelvic lymphadenectomy. Arm 1) EBRT 66/33 vs. Arm 2) LDR 35 Gy (delivered via 18 needles over 48 hours) + EBRT 40/20 for total 75 Gy (&gt;80% of prostate received 80 Gy)
**'''5-years; 2005''' {{PMID|15718316}} -- &quot;Randomized trial comparing iridium implant plus external-beam radiation therapy with external-beam radiation therapy alone in node-negative locally advanced cancer of the prostate.&quot; (Sathya JR, J Clin Oncol. 2005 Feb 20;23(6):1192-9.). Median F/U 8.2 years
***Outcome: 5-year FFP high dose 71% vs. standard dose 39% (SS); positive biopsy 24% vs. 51% (SS). OS 94% vs. 92% (NS)
***Conclusion: Higher doses of radiation over shorter duration results in better control

*'''Harvard''' (1982-1992) -- Photon boost 67.2 Gy vs. proton boost 75.6 Gy
**Randomized. Stage T3-T4N0-2. Standard photons 50.4 Gy four-field, then Arm 1) Conformal protons 25.2 CGE (total 75.6 CGE) vs. Arm 2) Photons 16.8 Gy (total 67.2 Gy). Median F/U 5.1 years
**'''5-years; 1995''' {{PMID|7721636}} -- &quot;Advanced prostate cancer: the results of a randomized comparative trial of high dose irradiation boosting with conformal protons compared with conventional dose irradiation using photons alone.&quot; (Shipley WU, Int J Radiat Oncol Biol Phys. 1995 Apr 30;32(1):3-12.)
***Outcome: 5-year LC photon+proton 92% vs. photons 80% (NS), no difference in OS, DSS, TRFS. GS 4/5 patients 94% vs. 64% (SS)
***Toxicity: Rectal bleeding photon+proton 32% vs. photons 12% (SS), urethral stricture 19% vs. 8% (p=0.07)
***Conclusion: Boosting dose with protons increased LC in poorly differentiated tumors, and also worsened late toxicity

===Altered Fractionation===
*'''Regina Elena NCI Rome, Italy''' (2003-2007) -- 80/40 (2 Gy/fx) vs 62/20 (3.1 Gy/fx)
**Randomized. 168 patients, high-risk (GS 8-10, PSA &gt;20 ng/ml, or 2+ of PSA 10-20, T &amp;ge; T2c, GS7), but PSA &amp;le; 100. All patients neoadjuvant/concurrent/adjuvat ADT x9 months. Arm 1) 3D-CRT 80/40 vs Arm 2) 3D-CRT 62/20, CTV = prostate + SV.
**'''2010''' {{PMID|20047800}} -- &quot;A Prospective Phase III Randomized Trial of Hypofractionation Versus Conventional Fractionation in Patients with High-Risk Prostate Cancer.&quot; (Arcangeli G, Int J Radiat Oncol Biol Phys. 2010 Jan 2. [Epub ahead of print]). Median F/U 2.7 years
***Outcome: 3-year bPFS conventional 79% vs hypofx 87% (SS); very high risk subset (GS 8-10, PSA &amp;ge; 20, or &amp;ge; T2c) 76% vs 88% (SS)
***Toxicity: 3-year late GI G2 conventional 16% vs hypofx 17%, GU G2 11% vs 14%
***Conclusion: Hypofractionated schedule superior for biochemical control, comparable for late toxicity

*'''Vilnius University, Lituania''' (2004-ongoing) -- 74/37 (2 Gy/fx) vs. 57/17 (3 Gy/fx + 4.5 Gy/fx)
**Randomized. 91 patients, clinically localized prostate cancer, risk of SV/LN involvement &lt;15%. No neoadjuvant ADT. Arm 1) 74/37 vs. Arm 2) 57/17 (39/13 + 18/4). CTV = prostate + base SV. PTV margin 8-10 mm. 3D-CRT using 5 fields
**'''2009''' {{PMID|19605967}} -- &quot;A randomized trial comparing hypofractionated and conventionally fractionated three-dimensional conformal external-beam radiotherapy for localized prostate adenocarcinoma: a report on the first-year biochemical response.&quot; (Norkus D, Medicina (Kaunas). 2009;45(6):469-75.)
***Outcome: 1-year PSA nadir &lt;1.0 HFRT54% vs. CFRT 50% (NS); 1-year PSA nadir &lt;0.5 18% vs. 25% (NS)
***Conclusion: Preliminary results suggest comparable biochemical response

*'''Fox Chase''' -- 76/38 (2 Gy/fx) vs. 70.2/26 (2.7 Gy/fx)
**Randomized. First 100 men reported. Intermediate-high risk. Neoadjuvant ADH x4 months permitted. Arm 1) conventional 76/38 (@ 2 Gy/fx) vs. Arm 2) hypofractionated 70.2/26 @ 2.7 Gy/fx)
**'''2006''' {{PMID|16242256}} -- &quot;Dosimetry and preliminary acute toxicity in the first 100 men treated for prostate cancer on a randomized hypofractionation dose escalation trial.&quot; (Pollack A, Int J Radiat Oncol Biol Phys. 2006 Feb 1;64(2):518-26. Epub 2005 Oct 19.)
***Toxicity: Slight increase in acute GI toxicity, no difference in GU toxicity
***Conclusion: Hypofractionation well tolerated acutely
**'''2013''' {{PMID|24101042}} --

*'''Mount Vernon, UK''' (1997-2005) -- 55/20 vs 35.75/13 + 17/2
**Randomized. 220 patients, prostate cancer T1-T3M0 (T3 26%), PSA &lt;50. Arm 1) EBRT 55/20 vs Arm 2) EBRT 35.75/13 + HDR 17/2. ADT 76%.
**'''Initial; 2007''' {{PMID|17531335}} -- &quot;High dose rate brachytherapy in combination with external beam radiotherapy in the radical treatment of prostate cancer: initial results of a randomised phase three trial.&quot; (Hoskin PJ, Radiother Oncol. 2007 Aug;84(2):114-20. Epub 2007 May 24.) Median F/U 1.25
***Outcome: Mean bRFS combined modality 5.1 years vs EBRT 4.3 years (SS). Improvement seen in all risk groups
***Toxicity: Acute GI toxicity better in combined group, other acute and late toxicities comparable. QoL FACT-P score better in combined group
***Conclusion: HDR brachytherapy + EBRT results in improved outcome with less acute toxicity and improved QoL

*'''Adelaide''' (Australia)(1996-2003) -- 64/32 (2 Gy/fx) vs. 55/20 (2.75 Gy/fx)
**Randomized. 217 patients, T1-2N0 PCA. No ADT. Arm 1) conventional 64/32 vs. Arm 2) hypofractionated 55/20. 
**'''4-years; 2006''' {{PMID|16965866}} -- &quot;Hypofractionated versus conventionally fractionated radiation therapy for prostate carcinoma: updated results of a phase III randomized trial. (Yeoh EE, Int J Radiat Oncol Biol Phys. 2006 Nov 15;66(4):1072-83. Epub 2006 Sep 11.) Median F/U 4 years
***Outcome: 5-year biochemical/clinical PFS conventional 55% vs. hypofractionated 57% (NS), OS 84% vs 86% (NS)
***Toxicity: GI urgency worse with hypofractionation, otherwise (NS). GU significantly worse with hypofractionation
***Conclusion: Hypofractionated schedule equivalent in efficacy, toxicity somewhat worse

*'''NCI Canada''' (1995-1998) -- 66/33 (2 Gy/fx) vs. 52.5/20 (2.62 Gy/fx)
**Randomized. 936 men, T1-T2, PSA &lt;40, no AST. Technique 3D-CRT
**'''5-years; 2005''' {{PMID|16135479}} -- &quot;Randomized trial comparing two fractionation schedules for patients with localized prostate cancer.&quot; (Lukka H, J Clin Oncol. 2005 Sep 1;23(25):6132-8.). Median F/U 5.7 years
***Outcome: 5-year FFP standard 47% vs. hypofractionated 40% (NS); no difference in post-RT biopsy rate or OS
***Toxicity: Grade 3 late toxicity 3.2% both arms (NS)
***Conclusion: Current hypofractionated regimen may be inferior to standard fractionation

===Prostate Localization===
*'''Princess Margaret; 2008''' {{PMID|18279985}} -- &quot;A randomized comparison of interfraction and intrafraction prostate motion with and without abdominal compression.&quot; (Rosewall T, Radiother Oncol. 2008 Feb 13 [Epub ahead of print])
**Randomized. 32 patients. Arm 1) VacLok immobilization vs. Arm 2) BodyFix abdominal compression. Interfraction motion &gt;3 mm corrected pre-treatment.
**Outcome: No difference in interfraction or intrafraction motion with or without abdominal{{typo help inline|reason=similar to adnominal|date=September 2022}} compression
**Conclusion: Addition of abdominal compression didn't influence interfraction or intrafraction prostate motion

===Endorectal balloon===
*'''Nijmegen, The Netherlands''' -- 3D-CRT +/- endorectal balloon
**Randomized. 48 patients, treated with 3D-CRT to 67.5 Gy. Arm 1) No endorectal balloon (ERB-) vs. Arm 2) with endorectal balloon (ERB+). Rectosigmoidoscopy at 3 months, 6 months, 1 year, 2 years. 146 endoscopies and 2,336 mucosal areas analyzed
**'''2007''' {{PMID|17161552}} -- &quot;Reduced late rectal mucosal changes after prostate three-dimensional conformal radiotherapy with endorectal balloon as observed in repeated endoscopy.&quot; (van Lin EN, Int J Radiat Oncol Biol Phys. 2007 Mar 1;67(3):799-811. Epub 2006 Dec 8.) Median F/U 2.5 years
***Outcome: ERB group significantly lower rectal wall volume exposed to high doses. Late rectal toxicity G1: ERB- 58% vs. ERB+ 21%; G2 4% vs. 0%; G3 4% vs. 0%. Overall G1+ rectal toxicity 67% vs. 21% (SS)
***Endoscopy: Telangiectasia ERB- vs ERB+ @ 6 months 16% vs. 24%; 1 year 45% vs. 28%; 2 years 39% vs. 24% (SS). High grade telangiectasia @ 1 years 20% vs. 10%; 2 years 19% vs. 9% (SS). Significantly less high grade telangiectasia at lateral and posterior part of Rwall
***Conclusion: ERB reduced rectal wall volume exposed to &gt;40 Gy, resulting in reduction of late mucosal changes and reduced late rectal toxicity

===2D RT vs 3D-CRT===
*'''Rotterdam, Netherlands''' (1994-1996) -- conformal RT vs conventional RT
**Randomized. 266 patients, prostate cancer Stage T1-4N0. RT 66/33. PTV expansion 15 mm. Arm 1) conventional RT (rectangular, open fields) vs. Arm 2) conformal RT (conformally shaped fields with MLC). PTV = GTV + 1.5 cm
**'''1999''' {{PMID|10098427}} -- &quot;Acute morbidity reduction using 3DCRT for prostate carcinoma: a randomized study.&quot; (Koper PC, Int J Radiat Oncol Biol Phys. 1999 Mar 1;43(4):727-34.)
***Outcome: Acute GI Grade 2 conventional 32% vs. conformal 19% (SS); Acute GU Grade 2 in 17% vs. 18% (NS). Further GI analysis: rectal symptoms 18% vs. 14% (NS) but anal symptoms 16% vs. 8% (SS)
***Conclusion: Significant reduction in GI toxicity, driven by anal symptoms. No difference between rectum/sigmoid and bladder toxicity
**'''2004''' {{PMID|15465140}} -- &quot;Gastro-intestinal and genito-urinary morbidity after 3D conformal radiotherapy of prostate cancer: observations of a randomized trial.&quot; (Koper PC, Radiother Oncol. 2004 Oct;73(1):1-9.) F/U 2 years
***Toxicity: Grade 2 conventional 10% vs 3D-CRT 7% (NS), Grade 1 47% vs. 40% (NS). Most bothersome symptoms: urgency, soiling, and fecal loss
***Predictors: Anal/rectal V90% for rectal toxicity. Acute anal/rectal toxicity for late rectal toxicity. Pretreatment urgency for later bladder toxicity
***Conclusion: Conformal RT at 66 Gy doesn't significantly decrease incidence of rectal, anal, and bladder toxicity compared with conventional RT

*'''Royal Marsden''' (1988-1995) -- conformal RT vs conventional RT
**Randomized. 225 men with prostate CA, T1-T4N0. NACHT in 68%. RT 64/31. Arm 1) conformal RT vs. Arm 2) conventional RT
**'''1999''' {{PMID|9929018}} -- &quot;Comparison of radiation side-effects of conformal and conventional radiotherapy in prostate cancer: a randomised trial.&quot; (Dearnaley DP, Lancet. 1999 Jan 23;353(9149):267-72.) Median F/U 3.6 years
***Outcome: Radiation-induced proctitis G1+ conformal RT 37% vs. conventional RT 56% (SS), G2+ 5% vs. 15% (SS). No difference in bladder toxicity. No difference in bPFS (78% vs 83%, NS) 
***Conclusion: Conformal RT significantly reduced risk of late proctitis

===Contouring Intervention===
*'''Princess Margaret''' (2007) -- interactive prostate MRI/CT vs general anatomy CT contouring
**Randomized. 31 trainees. Pretest contouring of prostate and rectum. Then randomized Arm 1) interactive session on prostate volumes using fused CT/MRI vs Arm 2) interactive session on general contouring using CT. Then retested
**'''2010''' {{PMID|19467804}} -- &quot;Effectiveness of educational intervention on the congruence of prostate and rectal contouring as compared with a gold standard in three-dimensional radiotherapy for prostate.&quot; (Szumacher E, Int J Radiat Oncol Biol Phys. 2010 Feb 1;76(2):379-85. Epub 2009 May 19.)
***Outcome: No difference in score gains between groups. No difference in prostate contour, but improved rectal contour
***Conclusion: Similar improvement in technical performance; participants in both groups satisfied

==Brachytherapy==
===Isotope===
*'''Seattle''' (1999 - 2006) -- I-125 vs. Pd-103
**Randomized. 602 patients, Stage T1c-T2a, GS 2-6, PSA 4-10 ng/ml. Arm 1) I-125 at 144 Gy vs. Arm 2) Pd-103 at 125 Gy. Modified peripheral loading pattern. Postimplant CT 2-4 hours later
**'''Dosimetry; 2008''' {{PMID|18376221}} -- &quot;There is a wide range of predictive dosimetric factors for I-125 and pd-103 prostate brachytherapy.&quot; (Herstein A, Am J Clin Oncol. 2008 Feb;31(1):6-10.)
***265 of 602 patients with CT-dosimetry. V50, V75, V100, V150, V200, V300; D50, D75, D90, D200 evaluated
***Outcome: bPFS I-125 85% vs. Pd-103 89%. Almost all parameters (not just D90 and V100) showed improvement with higher values. 
***D90 and V100 dosimetry: Highly correlated (r=0.7-0.8). V100 (I-125) 3-year bPFS &gt;90% 91% vs. &lt;90% 86% (NS); V100 (Pd-103) 100% vs. 89% (SS); D90 (I-125) &gt;100% 91% vs. &lt;100% 85% (NS); D90 (Pd-103) 100% vs. 87% (SS)
***Conclusion: Most dosimetric parameters have predictive value, in addition to D90 and V100

===Strand vs loose seeds===
*'''Seattle''' (2003-2004) -- Stranded seeds vs loose seeds
**Randomized. 62 patients with cT1c-T2a. Brachytherapy, 144 Gy, treatment plan devised prior to randomization. Arm 1) Strand seeds via Mick needles (however, 1/3 of seeds were loose to accommodate standard implant pattern) vs. Arm 2) Loose seeds via Mick applicator. Post-implant dosimetry at day 0 and day 30. Primary outcome seed loss and dosimetric parameters
**'''2007''' {{PMID|17434106}} -- &quot;A prospective randomized comparison of stranded vs. loose 125I seeds for prostate brachytherapy.&quot; (Reed DR, Brachytherapy. 2007 Apr-Jun;6(2):129-34.)
***Outcome: Seed loss strand 23% vs. loose 47% (p=0.053). Mean seeds lost 0.4 vs. 1.1 (p=0.06). Multiple seed loss in 10% vs. 25% patients. Strand seeds trend to worse V100 and D90
***Conclusion: Strong trend to lower seed loss with standed seeds

===Hialuronic acid injection===
*'''Oviedo, Spain''' -- transperineal perirectal HA injection vs. nothing
**'''2009''' (2005-2006) {{PMID|19213607}} -- &quot;Transperineal injection of hyaluronic acid in the anterior perirectal fat to decrease rectal toxicity from radiation delivered with low-dose-rate brachytherapy for prostate cancer patients.&quot; (Prada PJ, Brachytherapy. 2009 Apr-Jun;8(2):210-7. Epub 2009 Feb 12.)
***Randomized. 69 patients with low/intermediate PCA, treated with I-125 brachytherapy to 145 Gy. Median prostate volume 35 cc. Arm 1) control vs Arm 2) transperineal perirectal fat injection. Endoscopic follow up. Median F/U 1.5 years
***Outcome: Endoscopic mucosal damage control 36% vs. HA injection 5% (SS), rectal bleeding 12% vs 0% (SS)
***Conclusion: Increased distance resulted in smaller rectal dose, less mucosal damage, and no rectal bleeding

===Timing of NSAIDs===
*'''Toronto''' (2004-2008) -- Meloxicam 1 week prior to implant vs day of implant
**Randomized. 300 patients, treated with brachytherapy. Arm 1) meloxicam 7.5 mg BID started 1 weeks prior to implant x4 weeks vs Arm 2) started day of implant x4 weeks. Primary outcome: MRI prostate volume at 1 month, IPSS at 1 and 3 months, catheterization
**'''2010''' {{PMID|20350785}} -- &quot;A Phase III Randomized Trial of the Timing of Meloxicam with Iodine-125 Prostate Brachytherapy.&quot; (Crook J, Int J Radiat Oncol Biol Phys. 2010 Mar 27. [Epub ahead of print])
***Outcome: No difference in edema, catheterization (8% vs 6%, NS), or IPSS 
***Conclusion: Starting meloxicam 1 week prior to BT did not impact edema and urinary symptoms

===Supplemental EBRT dose===
*'''Seattle''' (2000-2004) -- (EBRT 44 Gy + BT 90 Gy) vs. (EBRT 20 Gy + BT 115 Gy)
**Randomized. ''Closed prematurely due to slowing accrual.'' 568 of planned 600 patients, clinical T1c-T2a, Glease 7-10 and/or PSA 10-20 ng/ml. Arm 1) EBRT 44 Gy + Pd-103 implant 90 Gy vs. Arm 2) EBRT 20 Gy + Pd-103 implant 115 Gy
**'''2005''' {{PMID|16086912}} -- &quot;20 Gy versus 44 Gy supplemental beam radiation with Pd-103 prostate brachytherapy: preliminary biochemical outcomes from a prospective randomized multi-center trial.&quot; (Wallner K, Radiother Oncol. 2005 Jun;75(3):307-10.)
***165 patients reported
***Outcome: 3-year bPFS 44 Gy 88% vs. 20 Gy 83% (NS)
***Conclusion: Likelihood of cure similar with standard or lower dose, in the setting of high prostate coverage by brachytherapy

==[[Radiation_Oncology/Prostate/Hormones|Androgen Deprivation Therapy]]==
===Primary ADT===
*'''EORTC 30891''' (1990-1999) -- Immediate ADT vs. Deferred ADT
**Randomized. 985 with clinical T0-4 N0-2 M0, refused or were not suitable for local definitive treatment. Excluded if &gt;80 years, pain from prostate, ureteric obstruction. Arm 1) Immediate androgen deprivation vs. Arm 2) Deferred androgen deprivation at symptomatic progression.
**'''2006''' {{PMID|16622261}} -- &quot;Immediate or deferred androgen deprivation for patients with prostate cancer not suitable for local treatment with curative intent: European Organisation for Research and Treatment of Cancer (EORTC) Trial 30891.&quot; (Studer UE, J Clin Oncol. 2006 Apr 20;24(12):1868-76.) Median F/U 7.8 years
***Outcome: Median OS immediate ADT 7.4 years vs deferred ADT 6.5 years (HR 1.25, SS). Most deaths due to prostate cancer (36%) or cardiovascular disease (34%). No difference in prostate cancer-specific deaths. Median time-to-start deferred ADT 7 years; 44% of patients who died never needed ADT
***Conclusion: Immediate ADT provides modest but statistically significant increase in overall survival, but no difference prostate cancer survival

===Primary ADT +/- RT===
*'''SPCG-7/SFUO-3''' (1996-2002) -- ADT +/- RT
**Randomized. 875 with locally advanced prostate cancer T1b G2-G3 or T3 (78%) and PSA &lt;70 and N0 (if PSA &gt;11, then PLND). Arm 1) ADT (total androgen blockade x3 months, then continuous flutamide 250 mg) vs. Arm 2) Same ADT + RT 70 Gy to prostate/SV. Breast RT in 80% to prevent gynecomastia
**'''7-years; 2008''' {{PMID|19091394}} -- &quot;Endocrine treatment, with or without radiotherapy, in locally advanced prostate cancer (SPCG-7/SFUO-3): an open randomised phase III trial.&quot; (Widmark A, Lancet. 2008 Dec 15. [Epub ahead of print]). Median F/U 7.6 years
***Outcome: 10-year CSS ADT 76% vs. ADT + RT 88% (SS); 10-year OS 61% vs. 70% (SS); 10-year bPFS 25% vs. 74% (SS)
***Toxicity: Urethral stricture ADT 0% vs. ADT + RT 2% (SS), urgency 8% vs 14% (SS), urinary incontinence 3% vs. 7% (SS), erectile dysfunction 81% vs. 89% (SS)
***Conclusion: In patients with high risk or locally advance PCA, addition of RT to ADT improved survival, with acceptable side effects

===RT +/- Long-Term ADT===
*'''Casodex Early Prostate Cancer Program (EPC)''' (1995-1998) -- Casodex vs. placebo
**Randomized, double blind, placebo. 8113 patients. Comprised of 3 separate trials: North America (Trial 23), Europe (Trial 24), and Scandinavia (SPCG-6, Trial 25). Pts with non-metastatic disease on bone scan, stages T1-4. Primary treatment with RT, surgery, or watchful waiting. Randomized to +/- adjuvant bicalutamide (Casodex) 150 mg. For 2 yrs (North America) or until progression (other 2 trials). Localized defined as clinical or pathological T1-T2N0-Nx, locally advanced defined as T3-T4 any N or any TN+. Surgical procedures, RT techniques, and dose-fractionation schedules not specified. Neoadjuvant hormonal therapy permitted in Trials 23-24
**'''RT 7-years; 2006''' {{PMID|16896884}} -- &quot;The addition of bicalutamide 150 mg to radiotherapy significantly improves overall survival in men with locally advanced prostate cancer.&quot; (See WA, J Cancer Res Clin Oncol. 2006 Aug;132 Suppl 1:S7-16.) Median F/U 7.2 years
***RT subset (n=1370); locally advanced 22%, localized 78%. EBRT 93%, EBRT + BT 6%. Median EBRT dose 64 Gy
***Outcome: Overall events bPFS 57% vs. 47% (SS), cPFS 67% vs. 61% (SS), OS 74% vs. 69% (NS)
****Locally advanced: bicalutamide improved bPFS by 59% (SS), cPFS by 44% (SS), DSS by 24% (SS), and OS by 35% (SS).  
****Localized: no difference in cPFS or OS, benefit for bPFS 59% vs 53% (SS)
***Conclusion: In patients with locally advanced disease, survival benefit for adjuvant Casodex, but no benefit in localized prostate cancer

*'''EORTC 22863''' (1987-1995) -- RT +/- concurrent/adjuvant ADT
**Randomized. 415 patients with T1-2 WHO grade 3 or T3-4 any grade, N0-1. RT alone vs RT + concurrent/adjuvant goserelin. Goserelin monthly starting on first day of RT, total of 3 years. RT pelvis 50/25 + boost 20/10 
**'''5-years; 2002'''  {{PMID|12126818}} &amp;mdash; &quot;Long-term results with immediate androgen suppression and external irradiation in patients with locally advanced prostate cancer (an EORTC study): a phase III randomised trial.&quot; Bolla M et al. Lancet. 2002 Jul 13;360(9327):103-6. Median F/U 5.5 years
***Outcome: 5-yr OS RT+ADT 78% vs RT alone 62% (SS), disease-specific survival 94% vs 79%, DFS 74% vs 40% (SS).
***Conclusion: AST during and 3 years after EBRT improves DFS and OS

*'''[[Radiation_Oncology/RTOG_Trials/8531|RTOG 85-31]]''' &quot;High Risk Non-Bulky Trial&quot; (1987-92) - long term (indefinite) hormones
**Randomized. 977 patients. ''Scheme:'' XRT alone vs XRT + long-term adjuvant goserelin (Zoladex). ''Eligibility:'' cT3 or pT3 (after prostatectomy) or N+ regional nodes (including common iliac or paraaortics). Bulky patients (primary tumor volume &gt; 25 cm by product of two dimensions) not allowed unless they had +LN outside of the pelvis (i.e. common iliac or paraaortic). (Bulky pts were enrolled on parallel study 86-10.) ''Hormones:'' Goserelin started during last week of XRT and continued monthly until progression. ''Radiation technique:'' For patients with LN+ disease within the pelvis: upper border at L5/S1 interspace, lower border 5-6 cm below pubic symphysis, lateral borders for AP/PA 2cm lateral to pelvic brim.  For positive common iliac nodes, extended up to L2/L3 interspace to include paraaortic nodes.  For positive periaortic LN, extend to body of T11.  ''Dose:'' 65-70 Gy definitive. 60 Gy for post-op. 44-46 Gy to pelvic field followed by boost.  
**'''10-years; 2005''' {{PMID|15817329}} &amp;mdash; &quot;Androgen suppression adjuvant to definitive radiotherapy in prostate carcinoma--long-term results of phase III RTOG 85-31.&quot; (Pilepich MV, Int J Radiat Oncol Biol Phys. 2005 Apr 1;61(5):1285-90.). Median F/U 7.6 years (11 for living patients)
***10-year outcome: OS 49% vs. 39% (SS); LF 23% vs. 38% (SS); DM 24% vs. 39% (SS); disease-specific mortality 16% vs. 22% (SS)
***Conclusion: In unfavorable prognosis patients, long-term adjuvant AST improves survival

===RT +/- Short-Term ADT===
*'''Harvard''' (1995-2001) - 6 months vs. no AST  
**Randomized. 206 men. Intermediate/High Risk: T1b-T2b (1992 staging), PSA &gt;= 10, Gleason &gt;= 7, radiographic ECE, or low risk pts with T3 based on endorectal MRI. Arm 1) 70 Gy 3D XRT (did not treat the pelvis) vs. Arm 2) 6 months androgen suppression (leuprolide/goserelin + flutamide) beginning 2 months prior to RT.
**'''5-years; 2004''' {{PMID|15315996}} &amp;mdash; &quot;6-month androgen suppression plus radiation therapy vs radiation therapy alone for patients with clinically localized prostate cancer: a randomized controlled trial.&quot; (D'Amico et al. JAMA. 2004 Aug 18;292(7):821-7.) Median F/U 4.5 years
***Outcome: 5-year OS RT+AST 88% vs RT alone 78% (SS). 5-year survival free of salvage androgen suppression 82% vs 57% (SS). Decreased cancer-specific mortality.
***Conclusion: Addition of 6 months of AST confers survival benefit
**'''8-years; 2008''' {{PMID|18212313}} -- &quot;Androgen suppression and radiation vs radiation alone for prostate cancer: a randomized trial.&quot; (D'Amico AV, JAMA. 2008 Jan 23;299(3):289-95.)
***Postrandomization evaluation of comorbidity impact via ACE-27. Comorbidity none 66%, minimal 11%, moderate 22%, severe 12%.  Median F/U 7.6 years
***Outcome: 8-year OS RT+AST 74% vs. RT alone 61% (SS); PCA-specific mortality significantly better (HR 4.1)
***Comorbidity: None/minimal OS 90% vs. 64% (SS); moderate/severe OS 25% vs. 54% (NS)
***Conclusion: Addition of 6 months AST increases OS, though possibly only in men with no/minimal comorbidities
**Comment: Showed a survival benefit after only 6 months of hormones, so long-term AST may not be needed. However, trend to worse survival in men with significant comorbidities

*'''Quebec L-101''' (1991-94) -- no ADT vs 3 months neoadjuvant vs. neoadjuvant/concurrent/adjuvant 10 months
**Randomized. 120 patients. T2a-T4. Arm 1) RT 64/32 alone, 2) 3 months neoadjuvant combination hormonal therapy (flutamide + LHRH agonist) + RT, or 3) hormonal therapy 3 months before, during, and 6 months after RT. Endpoint: Biopsy recurrence at 1 year and 2 years. 1-year biopsy compliance 77%, 2-year 57%
**'''2004''' {{PMID|14767287}} &amp;mdash; &quot;The efficacy and sequencing of a short course of androgen suppression on freedom from biochemical failure when administered with radiation therapy for T2-T3 prostate cancer.&quot; (Laverdiere J et al. J Urol. 2004 Mar;171(3):1137-40.) Median F/U 5 years
***Outcome: 7-year bNED RT 42% vs. RT + 3 months 66% (SS) vs. RT + 10 months 69% (SS, NS)
***Conclusion: Adding short course (6 months) of adjuvant ADT after neoadjuvant/concurrent ADT provided no further advantage

*'''[[Radiation_Oncology/RTOG_Trials/8610|RTOG 86-10]]''' &quot;Bulky Trial&quot; (1987-91) - short term androgen deprivation in addition to RT
**Randomized. 471 patients. Bulky primary tumors (T2-T4), palpable tumor 25 cm (by product of two dimensions). Allowed LN+ if below common iliac. Allowed bulky disease (unlike 85-31). Randomized to goserelin + flutamide 2 months before and 2 months during XRT, versus no AD. XRT to 45 Gy to pelvis, with boost to 65-70 Gy. RT fields to L5/S1 level if LN- but extend to L2-L3 if LN+. 
**'''8-years; 2001''' {{PMID|11483335}} &amp;mdash; &quot;Phase III radiation therapy oncology group (RTOG) trial 86-10 of androgen deprivation adjuvant to definitive radiotherapy in locally advanced carcinoma of the prostate.&quot; Pilepich MV et al. Int J Radiat Oncol Biol Phys. 2001 Aug 1;50(5):1243-52. 
***8-year LC 42% vs 30% (p=0.02), DM 34% vs 45% (p=0.04), DFS 33% vs 21% (p=0.004), bDFS 24% vs 10% (p&lt;0.0001), cause-specific mortality 23% vs 31% (p=0.05), overall survival 53% vs 44% (p=0.10)
***Conclusion: Beneficial effect in Gleason 2-6, with improved overall survival 70% vs 52% (p=0.015); For Gleason 7-10, no improvement in LRC or OS.
**'''10-years; 2008''' {{PMID|18172188}}  &amp;mdash; &quot;Short-Term Neoadjuvant Androgen Deprivation Therapy and External-Beam Radiotherapy for Locally Advanced Prostate Cancer: Long-Term Results of RTOG 8610.&quot; Roach M et al. J Clin Oncol 2008 (ahead of print).
***Outcome: 10-yr OS AST 43% vs control 34% (NS), median OS 8.7 vs 7.3 yrs (NS, p=0.12). Improved DSM (23% vs 36%, SS), DM (35% vs 47%, SS), DFS (11% vs 3%, SS), and BF (65% vs 80%, SS). No difference in fatal cardiac events.
***Conclusion: &quot;The addition of 4 months of ADT to EBRT appears to have a dramatic impact on clinically meaningful end points in men with locally advanced disease, with no statistically significant impact on the risk of fatal cardiac events.&quot;

===RT + ADT: Duration of Therapy===
*'''EORTC 22961''' (1997-2002) -- AST 6 months vs. AST 3 years
**Randomized. 970 men. Locally advanced prostate cancer (T1c-T2b pN1-N2 M0 or cT2c-T4 N0-N2 M0), PSA up to 40x normal, Hb &gt;10. 3D-CRT pelvis + prostate boost 70 Gy. AST 6 months (complete androgen blockade) initiated 1st day of RT. If no progression, Arm 1) observation vs Arm 2) AST 2.5 years (LHRH triptorelin). 72% completed full 3 years.  Median F/U 6.4 year
**'''2009''' {{PMID|19516032}} -- &quot;Duration of Androgen Suppression in the Treatment of Prostate Cancer&quot; (Bolla M, N Engl J Med. 2009 Jun 11;360(24):2516-2517.)
***Outcome: 5-year OS 6-months 81% vs. 3-years 85% (HR 1.4, SS); 5-year CSS 95% vs. 97% (HR 1.7, SS).
***Toxicity: 6 month AST hot flashes 29%, gynecomastia 7%, incontinence 10%. 3 year AST hot flashes 39%, gynecomastia 18%. Quality of life comparable between arms. No difference in fatal cardiac events (4% vs. 3%)
***Conclusion: Combination of RT + 3 years AST provides superior survival to 6 month AST in locally advanced cancer

*'''TROG 96.01''' (Australia)(1996-2000) -- ADT None vs 3 months vs 6 months
**Randomized. 802 men with locally advanced PCA (T2b-T4N0). Treatetd with 1) RT alone 66/33 vs. RT + 3 month AST (goserelin+flutamide starting 2 months prior to RT) vs. RT + 6 months AST (starting 5 months prior to RT). 
**'''2005''' {{PMID|16257791}} -- &quot;Short-term androgen deprivation and radiotherapy for locally advanced prostate cancer: results from the Trans-Tasman Radiation Oncology Group 96.01 randomised controlled trial.&quot; (Denham JW, Lancet Oncol. 2005 Nov;6(11):841-50.) Median F/U 5.9 years
***5-year outcomes: bF 0 mo 14% vs. 3 mo 20% (SS) vs. 6 mo 21% (SS, NS) Local failure: 10% vs. 6% (SS) vs. 4% (SS, NS); distant failure 7% vs. 8% (NS) vs. 5% (SS, SS); PCA-specific survival: 34% vs. 35% (NS) vs. 35% (NS)
***Conclusion: 6 months AST before/during improves outlook of patients with locally advanced PCA. 3 months and 6 months comparable with local control, 6 months benefit for distant mets and freedom from salvage

*'''Canada multicenter''' (1995-2001) -- ADT 3 vs 8 months prior to RT
**Randomized. 378 patients. Clinically localized cT1-T4 (low 26%, intermediate 43%, high risk 31%). Median PSA 9.7 ng/ml Arm 1) Flutamide + goserelin x3 months vs. Arm 2) Same x8 months. Subsequently prostate RT 66 Gy. If LN+ risk &gt;10-15%, treated pelvis. No concurrent ADT
**'''2009''' {{PMID|18707821}} -- &quot;Final report of multicenter Canadian Phase III randomized trial of 3 versus 8 months of neoadjuvant androgen deprivation therapy before conventional-dose radiotherapy for clinically localized prostate cancer.&quot; (Crook J, Int J Radiat Oncol Biol Phys. 2009 Feb 1;73(2):327-33. Epub 2008 Aug 15.) Median F/U 6.6 years
***Outcome: 5-year bPFS 3 months 72% vs. 8 months 75% (NS); OS 81% vs. 79% (NS). Improved DFS for high-risk patients with 8 months (71% vs. 42%, SS)
***Conclusion: Longer neoadjuvant HT before standard RT didn't alter patterns of failure

*'''Quebec L-200''' (1994-1999) -- Neoadjuvant/concurrent (5 months) vs neoadjuvant/concurrent/adjuvant (10 months) ADT
**Randomized. 325 patients, cT2-T3 prostate cancer. Arm 1) RT + eoadjuvant/concurrent ADT (5 months) using LHRH agonist + antiandrogen vs. Arm 2) RT + neoadjuvant/concurrent/adjuvant (10 months) ADT. Endpoint bNED by Vancouver definition
**'''2004''' {{PMID|14767287}} &amp;mdash; &quot;The efficacy and sequencing of a short course of androgen suppression on freedom from biochemical failure when administered with radiation therapy for T2-T3 prostate cancer.&quot; (Laverdiere J et al. J Urol. 2004 Mar;171(3):1137-40.) 
***Outcome: 4-year bNED 65%, no difference between arms
***Conclusion: Adding short course (5 months) of adjuvant ADT after neoadjuvant/concurrent ADT provided no further advantage

*'''[[Radiation Oncology/RTOG Trials/9202|RTOG 92-02]]''' (1992-95) -- 4 months versus 2 years ADT
**Randomized. 1554 patients with locally advanced PCA. T2c-T4 (T2 45%, T3 50%); PSA &lt;150 (PSA &lt;=30 in 67%), allowed N+ (N+ 4%, Nx 87%) but excluded LN+ at common iliac or higher chains. Goserelin 3.6 mg SC qM + flutamide 250 mg TID for 2 months before and 2 months during XRT. Then Arm 1) observation (ST-ADT) vs. Arm 2) 2 years of goserelin (LT-ADT). XRT pelvis 45 Gy, followed by a boost to 65-70 Gy. 
**'''10-years; 2008''' {{PMID|18413638}} -- &quot;Ten-Year Follow-Up of Radiation Therapy Oncology Group Protocol 92-02: A Phase III Trial of the Duration of Elective Androgen Deprivation in Locally Advanced Prostate Cancer.&quot; (Horwitz EM, J Clin Oncol. 2008 Apr 14 [Epub ahead of print]). Median F/U 11.3 years
***Outcome: 10-year DFS ST-ADT 13% vs. LT-ADT 22% (SS), DSS 84% vs. 89% (SS), LR 22% vs. 12% (SS); OS 52% vs. 54% (NS)
***Subset analysis (GS 8-10): OS ST-AST 32% vs. LT-AST 45%; all other points also SS
***Conclusion: LT-ADT is superior to ST-ADT; no impact on survival but trial not powered for it. On subgroup analysis, GS 8-10 gains survival advantage


===RT + ADT +/- Chemotherapy===
*'''Nihon University, Japan''' (2003-2006) -- RT + ADT +/- estramustine 
**Randomized. 39 patients, intermediate/high risk PCA by NCCN guidelines. Arm 1) Neoadjuvant/concurrent LHRH agonist + estramustine x6 months vs Arm 2) NCAHT x 6 months. Both groups 3D-CRT 70/35
**'''2010''' {{PMID|19449118}} -- &quot;Neoadjuvant LHRH analog plus estramustine phosphate combined with three-dimensional conformal radiotherapy for intermediate- to high-risk prostate cancer: a randomized study.&quot; (Hirano D, Int Urol Nephrol. 2010 Mar;42(1):81-8. Epub 2009 May 16.) Median F/U 2.3 years
***Outcome: 4-year bRFS ADT+EMP 61% vs ADT alone 49% (SS)
***Toxicity: No severe toxicities
***Conclusion: ADT + EMP better than ADT alone, but either arm insufficient and dose escalation or adjuvant ADT needed

*'''RTOG 99-02''' (2000-2004) -- RT + ADT +/- TEE (taxol, estramustine, etoposide)
**Randomized. ''Closed early due to thromobembolic events.'' 397 patients.  High risk CaP (PSA 20-100 and GS &gt;=7, or T2+, GS8, PSA &lt;100). Neoadjuvant/concurrent and adjuvant AS + RT (2/2/2 TAA) +/- TEE Chemotherapy (taxol, estramustine, etoposide) x 4 cycles.
**'''2009''' {{PMID|18990504}} -- &quot;Phase III multi-institutional trial of adjuvant chemotherapy with paclitaxel, estramustine, and oral etoposide combined with long-term androgen suppression therapy and radiotherapy versus long-term androgen suppression plus radiotherapy alone for high-risk prostate cancer: preliminary toxicity analysis of RTOG 99-02.&quot; (Rosenthal SA, Int J Radiat Oncol Biol Phys. 2009 Mar 1;73(3):672-8. Epub 2008 Nov 5.)
***Toxicity: AS 37% vs. AS + TEE 715 (SS), for hematological (SS), GI (SS), and trend GU (p=0.07). Three cases of MDS/AML in TEE arm
***Conclusion: TEE associated with significantly increased toxicity during treatment


===Lipid Profile===
*'''Toremifene Trial''' (2003-2005)
**Randomized. 1389 men, prostate cancer, receiving long-term ADT (&gt;6 months, or intermittently for &gt;12 months, or bilateral orchiectomy). Arm 1) Toremifene 80 mg/d (second generation SERM) vs. Arm 2) placebo
**'''Lipid effect; 2008''' {{PMID|18398147}} -- &quot;Toremifene improves lipid profiles in men receiving androgen-deprivation therapy for prostate cancer: interim analysis of a multicenter phase III study.&quot; (Smith MR&lt; J Clin Oncol. 2008 Apr 10;26(11):1824-9.)
***Interim analysis of 188 patients. Fasting serum lipids compared at baseline and 1 year later
***Outcome: total cholesterol toremifene -8% vs. placebo -1% (SS); LDL -8% vs. +1% (SS); HDL +0.5% vs. -5% (SS); triglycirides -13% vs. +7% (SS)
***Conclusion: Tofemifene significantly improved lipid profile

===Gynecomastia===
*'''Italy''' (2002-2004) -- observation vs. tamoxifen vs RT
**Randomized, 3 arms. 5 centers. 151 patients with prostate cancer, any TN, M0, no gynecomastia/breast pain. Arm 1) bicalutamide 150 mg alone vs. Arm 2) bicalutamide 150 mg + tamoxifen 10 mg x24 weeks vs. Arm 3) bicalutamide 150 mg + RT 12/1. RT given as electrons to 5cm diameter of tissue around each nipple, 6-12 MeV to deliver 90% between skin and chest wall. In observation patients who developed gynecomastia (35/50), subsequently randomized to TAM or RT 
**'''2005''' {{PMID|15863377}} -- &quot;Efficacy of tamoxifen and radiotherapy for prevention and treatment of gynaecomastia and breast pain caused by bicalutamide in prostate cancer: a randomised controlled trial.&quot; (Perdona S, Lancet Oncol. 2005 May;6(5):295-300.)
***Outcome: Gynecomastia observation 69% vs. TAM 8% (SS) vs. RT 34% (SS). Breast pain observation 57% vs. TAM 6% (SS) vs. RT 30% (SS). In observation patients randomized secondarily, gynecomastia TAM 12% vs. RT 56% (SS)
***Toxicity: both TAM and RT well tolerated
***Conclusion: Antiestrogen treatment with TAM appears superior to RT

*'''Italy''' (2002-2004) -- observation vs. tamoxifen vs RT
**Randomized. 102 patients, treated with RP for localized or locally advanced PCA. Treated with adjuvant bicalutamide and Arm 1) observation vs. Arm 2) tamoxifen 10 mg vs. Arm 3) RT. Arm 1 failures subsequently randomized to TAM vs. RT
**'''2005''' {{PMID|16280763}} -- &quot;Gynecomastia and breast pain induced by adjuvant therapy with bicalutamide after radical prostatectomy in patients with prostate cancer: the role of tamoxifen and radiotherapy.&quot; (DiLorenzo G, J Urol. 2005 Dec;174(6):2197-203.)
***Outcome: Gynecomastia observation 67% vs. TAM 8% (SS) vs. RT 34% (SS). Breast pain 58% vs. 7% vs. 30%
***Toxicity: No difference in QoL between TAM and RT
***Conclusion: Gynecomastia and breast pain induced by bicalutamide after RP can be prevented. Tamoxifen more effective than RT

*'''Italy''' (2000-2002) -- observation vs. tamoxifen vs. anastrozole
**Randomized. 114 patients with localized, locally advanced, or recurrent prostate cancer. Treated with bicalutamide 150 mg. Arm 1) placebo vs. Arm 2) tamoxifen 20 mg/d vs. Arm 3) anastrozole 1 mg/d x 48 weeks
**'''2005''' {{PMID|15681525}} -- &quot;Evaluation of tamoxifen and anastrozole in the prevention of gynecomastia and breast pain induced by bicalutamide monotherapy of prostate cancer.&quot; (Boccardo F, J Clin Oncol. 2005 Feb 1;23(4):808-15.)
***Outcome: Gynecomastia observation 73% vs TAM 10% vs. anastrozole 51% (SS). Breast pain 39% vs. 6% vs. 27% (SS). 
***Toxicity: No difference in PSA response. Adverse events 37% vs. 35% vs. 69% (SS). No difference in sexual function
***Conclusion: Tamoxifen was effective, no significant benefit for anastrozole

*'''US Multi-institutional''' -- placebo vs. tamoxifen vs. anastrozole
**Randomized, 3 arms. 107 patients with prostate cancer, T1-4 any NM0 (T2-3 in 92%), on bicalutamide 150 mg/d. Arm 1) observation vs. Arm 2) tamoxifen 20 mg/d vs. Arm 3) anastrozole 1 mg/d x3 months. Excluded if gynecomastia &gt;2cm or breast discomfort
**'''2005''' {{PMID|15685254}} -- &quot;Prevention and management of bicalutamide-induced gynecomastia and breast pain: randomized endocrinologic and clinical studies with tamoxifen and anastrozole.&quot; (Saltzstein D, Prostate Cancer Prostatic Dis. 2005;8(1):75-83.)
***Outcome: 3-month gynecomastia TAM 12% (SS) vs. anastrozole 64% (NS) vs. placebo 69%
***Toxicity: PSA decreased in all groups
***Conclusion: Incidence of gynecomastia reduced by tamoxifen; anastrozole 1mg/d not a viable option

*'''European''' (1999-2001) -- RT 10/1 vs. sham
**Randomized. 106 patients, prostate cancer (T1b-T4NxM0), Casodex 150 mg/d x1 year. Arm 1) RT 10/1 electrons vs. Arm 2) sham RT.
**'''2004''' {{PMID|15380582}} -- &quot;Prophylactic breast irradiation with a single dose of electron beam radiotherapy (10 Gy) significantly reduces the incidence of bicalutamide-induced gynecomastia.&quot; (Tyrrell CJ, Int J Radiat Oncol Biol Phys. 2004 Oct 1;60(2):476-83.)
***Outcome: Gynecomastia RT 52% vs. sham 85% (SS), fewer were &gt;5 cm (11% vs. 50%) and fewer were moderate/severe (21% vs 48%). Breast pain 83% vs. 91% (NS)
***Conclusion: Prophylactic breast RT is effective and well tolerated for prevention of gynecomastia

==[[Radiation_Oncology/Prostate/Adjuvant_RT|Surgery +/- RT]]==
*'''German ARO 96-02 / AUO AP 09/95''' (1997-2004) -- Adjuvant RT vs. observation 
**Randomized. 385 men, radical prostatectomy pT3 pN0, undetectable post-op PSA (80%). Arm 1) RT 60/30 Gy vs Arm 2) observation. RT 3D plan prostatic fossa + SV + 1cm. Start 8-12 weeks after RP. Primary endpoint PSA control (PSA relapse defined as undetectable to detectable, followed by another increase). Patients not reaching undetectable PSA (20%) treated with 66.6 Gy. Arm 1 21% patients didn't receive RT
**'''2009''' {{PMID|19433689}} -- &quot;Phase III Postoperative Adjuvant Radiotherapy After Radical Prostatectomy Compared With Radical Prostatectomy Alone in pT3 Prostate Cancer With Postoperative Undetectable Prostate-Specific Antigen: ARO 96-02/AUO AP 09/95.&quot; (Wiegel T, J Clin Oncol. 2009 May 26.) Median F/U 4.5 years
***Outcome: 5-year bPFS observation 54% vs. RT 72% (HR 0.53, SS). DM 3% vs. 2%. Negative predictors preop PSA &gt;10, stage pT3c
***Toxicity: No Grade 4, 1 patient with Grade 3 bladder, Grade 2 in 3%
***Conclusion: Patients with pT3 PCA who achieve undetectable PSA after surgery benefit from adjuvant RT

*'''EORTC 22911''' (1992-2001) [http://www.cancer.gov/clinicaltrials/EORTC-22911#PublishedResults_CDR0000078080 Protocol] -- Adjuvant RT vs. observation
**Randomized. 1005 patients. Radical prostatectomy pT2-3N0, ilio-obturator LND, with extracapsular disease (ECE, SV+, SM+). Arm 1) observation vs. Arm 2) RT 60/30, start within 16 weeks of RP. RT technique conventional (non-3D), 50/25 + 10/5 boost with smaller margins. Borders surgical limits SV to apex. No Gleason scoring (used WHO grade). Biochemical failure increase of 0.2 from postop nadir measured on 3 occasions at least 2 weeks apart and is dated from first day of rise. After biochemical or clinical failure, could get salvage RT. By risk: 43% had one RF only, 43% had two RFs, 12% had all three RFs. Primary endpoint clinical PFS, amended to bNED in 2003
**'''5-years; 2005''' {{PMID|16099293}}, 2005 &amp;mdash; &quot;Postoperative radiotherapy after radical prostatectomy: a randomised controlled trial (EORTC trial 22911).&quot; (Bolla M, Lancet. 2005 Aug 13-19;366(9485):572-8.) Median F/U 5 years
***Outcome: 5-year bNED RT 74% vs observation 53% (SS), regardless of risk factors. Most failures loco-regional. Clinical PFS 85% vs. 78% (SS). OS 91-92% (NS).
***Late toxicity:  Grade 3 RT 4% vs. observation 3% (p=0.07)
***Conclusion: Post-operative radiotherapy results in improved biochemical and clinical PFS, but its benefit should be weighed against the risk of increased toxicity.
**'''Subset analysis; 2007''' {{PMID|17878474}} -- &quot;Identification of patients with prostate cancer who benefit from immediate postoperative radiotherapy: EORTC 22911.&quot; (Van der Kwast TH, J Clin Oncol. 2007 Sep 20;25(27):4178-86.)
***Pathology data review. 552 patients
***Surgical margin impact: if SM+, RT prevents 291 events/1000 patients (SS); need to treat 3 patients to prevent 1 recurrence. If SM-, RT prevents 88 events/1000 patients (NS).  
***Conclusion: After careful central path review, RT beneficial only for patients with positive margins (this effect was not seen when using the local pathology data), no benefit if negative margins

*'''SWOG-8794 / [[Radiation_Oncology/RTOG_Trials/9019|RTOG 90-19]] / INT-0086''' (1988-95) -- prostatic fossa RT vs. observation
**Randomized. 473 patients, radical prostatectomy with extraprostatic disease (ECE, SV+, or SM+). Pelvic LND required until 1995, when very low risk patients (T1a or T2a GS2-6 PSA &lt;10, T1b-c GS2-5 PSA &lt;10, T2b GS2-6 PSA &lt;6, T2c GS2-6 PSA &lt;4) were exempt. Arm 1) Prostatic fossa RT 60-64 Gy vs Arm 2) observation, within 18 weeks from RP. No concurrent hormones . RT field  non-3D, 4-field, 9x9 or 10x10 cm. Primary endpoint mets-free survival
**'''10-years; 2006''' {{PMID|17105795}} &amp;mdash; &quot;Adjuvant radiotherapy for pathologically advanced prostate cancer: a randomized clinical trial.&quot; (Thompson IM Jr, JAMA. 2006 Nov 15;296(19):2329-35.) Median F/U 10.6 years
***Outcome: Mets-free survival RT 65% vs. observation 57% (p=0.06), median 14.7 years vs. 13.2 years. However, 33% of observation group received salvage RT for disease relapse instead of observation alone. PSA relapse (defined as &gt;0.4) RT 36% vs. 65% (SS), median 10.3 yrs vs observation 3.1 yrs (SS). Recurrence free survival 61% vs. 47% (SS). Hormones initiated in 10% vs 21%. No difference in OS.  
***Rectal complications 3% vs 0%, urethral strictures 18% vs 9%, total urinary incontinence 6% vs 3%.
***Conclusion: Adjuvant RT significantly decreases PSA and clinical recurrence
**'''15 year update; 2009''' {{PMID|19167731}} -- &quot;Adjuvant radiotherapy for pathological T3N0M0 prostate cancer significantly reduces risk of metastases and improves survival: long-term followup of a randomized clinical trial.&quot; (Thompson, J Urol 2009)
***RT improved metastasis free survival (HR 0.71, 93/214 vs. 114/211)
***RT improved overall survival: HR 0.72, 57% vs 48%, p=0.023. # of Deaths 88/214 vs 110/211.
***Median f/u of ~12.5y in both arms
***70 of 211 pts on observation arm ultimately received RT.
**For more updated information on the SWOG trial check the [[Radiation_Oncology/Prostate/Adjuvant_RT#Radical Prostatectomy +/- Adjuvant RT|Radical Prostatectomy &amp;plusmn; Adjuvant RT section]]

==[[Radiation_Oncology/Prostate/Prostatectomy|Surgery +/- Chemotherapy]]==
*'''SWOG 9921 / Intergroup''' (2000-2007) -- ADT vs. ADT + mitoxantrone
**Randomized. ''Closed prematurely after AML toxicity.'' 983 patients patients, radical prostatectomy, high risk features (GS &gt;=8, or pT3b-T4, or N1, or GS 7 and SM+, or PSA &gt;15 ng/ml. Had to have undetectable post-op PSA). Arm 1) ADT x2 years (bicalutamide 50mg QD + goserelin 10.8 mg SC q3 months) vs. Arm 2) ADT x2 years + mitoxantrone 12 mg/m2 q3W x6 cycles
**'''2008''' {{PMID|18349405}} -- &quot;Randomization reveals unexpected acute leukemias in Southwest Oncology Group prostate cancer trial.&quot; (Flaig TW, J Clin Oncol. 2008 Mar 20;26(9):1532-6.)
***Outcome: 3 cases of AML reported in 487 patients in mitoxantrone arm. Time-to-detection 13, 48, and 72 months. Trial stopped
***Conclusion: Highlights importantce of controlled trials to define safety and efficacy


==Metastatic==
*'''Atrasentan''' - endothelin-A receptor antagonist
**Randomized. 809 men with HRPC. Arm 1) atrasentan 10 mg vs. Arm 2) placebo. Endpoint TTP
**'''2007''' {{PMID|17886253}} -- &quot;A phase 3 randomized controlled trial of the efficacy and safety of atrasentan in men with metastatic hormone-refractory prostate cancer.&quot; (Carducci MA, Cancer. 2007 Nov 1;110(9):1959-66.)
***Outcome: No difference in time-to-progression; most progressed radiographically within 12 weeks; no difference in PSA progression
***Toxicity: Well tolerated 
***Conclusion: No difference in delay of disease progression

*'''TAX 327''' (2000-2002) -- Docetaxel + prednisone vs. mitoxantrone + prednisone
**Randomized. 1006 patients with HRPC. Arm 1) docetaxel q3 weeks + prednisone (D3P) vs. Arm 2) docetaxel q1 week + prednisone (D1P) vs. Arm 3) mitoxantrone + prednisone (MP).
**'''2004''' {{PMID|15470213}} -- &quot;Docetaxel plus prednisone or mitoxantrone plus prednisone for advanced prostate cancer.&quot; (Tannock IF, N Engl J Med. 2004 Oct 7;351(15):1502-12.)
***Outcome: median OS D3P 18.9 months vs. D1P 17.4 months vs. MP 16.5 months (SS). Improved QoL: 23% vs. 22% vs. 13% (SS)
***Conclusion: Docetaxel q3 weeks + prednisone led to improved survival and quality of life
**'''2008''' {{PMID|18182665}} -- &quot;Docetaxel plus prednisone or mitoxantrone plus prednisone for advanced prostate cancer: updated survival in the TAX 327 study.&quot; (Berthold DR, J Clin Oncol. 2008 Jan 10;26(2):242-5.)
***Outcome: median OS: D3P 19.2 months vs. D1P 17.8 months vs. MP 16.3 months (SS); 3-year OS 18.6% vs. 16.6% vs. 13.5%. Similar outcome regardless of age, pain, or baseline PSA
***Conclusion: Survival longer after docetaxel q3 weeks with prednisone

*'''SWOG 9916''' (1999-2003) -- Docetaxel + estramustine + dexamethasone vs. mitoxantrone + prednisone
**Randomized. 674 men with HRPC. Arm 1) docetaxel + estramustine + dexamethasone q3 weeks vs. Arm 2) mitoxantrone + prednisone q3 weeks
**'''2004''' {{PMID|15470214}} -- &quot;Docetaxel and estramustine compared with mitoxantrone and prednisone for advanced refractory prostate cancer.&quot; (Petrylak DP, N Engl J Med. 2004 Oct 7;351(15):1513-20.)
***Outcome: median OS DED 17.5 months vs. MP 15.6 months (SS). Median TTP 6.3 months vs. 3.2 months (SS). Pain relief comparable
***Toxicity: Grade 3-4 neutropenic fever, N/V, and CV events more common in docetaxel group
***Outcome: Improved median survival with docetaxel + estramustine

*'''CALGB 9182''' -- Mitoxantrone + hydrocortisone vs. hydrocortisone alone
**Randomized. 242 patients with HRPC. Arm 1) mitoxantrone + hydrocortisone (MH) vs. Arm 2) hydrocortisone alone (H).
**'''1999''' {{PMID|10561316}} -- &quot;Hydrocortisone with or without mitoxantrone in men with hormone-refractory prostate cancer: results of the cancer and leukemia group B 9182 study.&quot; (Kantoff PW, J Clin Oncol. 1999 Aug;17(8):2506-13.)
***Outcome: MH better in TTTF, response rate, pain control, and QoL. No difference in survival (12.3 months vs. 12.6 months, NS)
***Conclusion: Mitoxantrone with hydrocortisone had more frequent response, delay to progression, and pain control than hydrocortisone alone

*'''Scandinavian SPCG-5''' (1992-1997) -- parenteral estrogen vs. total androgen blockade
**Randomized. 910 patients, metastatic prostate cancer. Arm 1) parenteral estrogen 240 mg/month vs. Arm 2) flutamide 250 mg TID + triptorelin 3.75 mg or bilateral orchidectomy
**'''2008''' {{PMID|18432528}} -- &quot;Parenteral estrogen versus combined androgen deprivation in the treatment of metastatic prostatic cancer: part 2. Final evaluation of the Scandinavian Prostatic Cancer Group (SPCG) Study No. 5.&quot; (Hedlund PO, Scand J Urol Nephrol. 2008;42(3):220-9.
***Outcome: No difference in bPFS, cPFS, DSS, or OS
***Toxicity: No difference in CV mortality, but increased cardiovascular events in parenteral estrogen arm. Increased skeletal events/osteoporosis in androgen arm
***Conclusion: No difference in outcome. Toxicity profiles different

*'''CALGB 9181''' (1992-1994) -- low-dose vs. high-dose Megace
**Randomized. 149 ment with HRPC, with progressive metastatic or LN carcinoma; only 1 prior hormonal therapy allowed. Arm 1) oral megestrol acetate 160 mg/day (low dose) vs. Arm 2) oral megestrol acetate 640 mg/day (high dose). Primary endpoint tumor response
**'''2000''' {{PMID|10679652}} -- &quot;A randomized study comparing standard versus moderately high dose megestrol acetate for patients with advanced prostate carcinoma: cancer and leukemia group B study 9181.&quot; (Dawson NA, Cancer. 2000 Feb 15;88(4):825-34.)
***Outcome: Tumor response comparable. Median OS low dose 11.2 months vs. high dose 12.1 months (NS). Most (91%) died of prostate cancer
***Toxicity: comparable, but 7% had acute pain flare
***Conclusion: Megestrol acetate has limited activity in HRPC; there is no apparent dose-response correlation

*'''Canada''' -- Mitoxantrone + prednisone vs. prednisone alone
**Randomized. 161 HRPC with pain. Arm 1) mitoxantrone + prednisone vs. Arm 2) prednisone alone. Primary end point palliative response (1/3 pain decrease)
**'''1996''' {{PMID|8656243}} -- &quot;Chemotherapy with mitoxantrone plus prednisone or prednisone alone for symptomatic hormone-resistant prostate cancer: a Canadian randomized trial with palliative end points.&quot; (Tannock IF, J Clin Oncol. 1996 Jun;14(6):1756-64.)
***Outcome: Palliative response MP 29% vs. P 12% (SS). Duration of palliation MP 9.9 months vs. P 4.1 months (SS)
***Conclusion: Chemotherapy with mitoxantrone and prednisone provides palliation for some patients with symptomatic HRPC

*'''Scandinavian SPCG-2''' (1984-1989) -- bilateral orchiectomy +/- cyproterone
**Randomized. 294 patients, metastatic PCA, Grade 1-2. Arm 1) bilateral orchiectomy vs. Arm 2) bilateral orchiectomy + cyproterone
**'''1993''' {{PMID|8287887}} -- &quot;Total androgen suppression: experience from the Scandinavian Prostatic Cancer Group Study No. 2.&quot; (Jorgensen T, Eur Urol. 1993;24(4):466-70.)
***Outcome: No difference in disease progression, or overall survival
***Conclusion: Total androgen blockade with cyproterone not superior to orchiectomy

*'''Scandinavian SPCG-1''' (1984-1989) -- DES vs. estramustine
**Randomized. 197 patients with high grade metastatic PCA (M1, G2-3). Arm 1) estramustine 560 mg vs Arm 2) diethylstilbestrol (DES) 3 mg
**'''1997''' {{PMID|9165581}} -- &quot;Treatment of high-grade, high-stage prostate cancer with estramustine phosphate or diethylstilbestrol. A double-blind study. The SPCG-1 Study Group. Scandinavian Prostate Cancer Group.&quot; (Hedlund PO, Scand J Urol Nephrol. 1997 Apr;31(2):167-72.)
***Outcome: DES better for time-to-progression (p=0.05), treatment failure (SS), CSS (p=0.07), and OS (SS)
***Conclusion: Treatment with DES had relatively good effect

==Exercise==
===Exercise===
*'''Perth, Australia''' (2007-2008) -- exercise x12 weeks vs control
**Randomized. 57 patients with CaP, undergoing AST. Arm 1) resistance and aerobic exercise x12 weeks vs. Arm 2) usual care. Primary endpoint lean mass
**'''2010''' {{PMID|19949016}} -- &quot;Combined resistance and aerobic exercise program reverses muscle loss in men undergoing androgen suppression therapy for prostate cancer without bone metastases: a randomized controlled trial.&quot; (Galvao DA, J Clin Oncol. 2010 Jan 10;28(2):340-7. Epub 2009 Nov 30.)
***Outcome: Patients undergoing exercise improved lean mass (SS), muscle strength (SS), improved walk time (SS), QoL (SS), fatigue (SS), and CRP levels (SS)
***Conclusion: Relatively brief exposure to exercise significantly improved AST-related adverse effects

*'''Rochester''' -- exercise x4 weeks vs. control
**Randomized. 38 breast or prostate cancer patients. Arm 1) Home-based aerobic and progressive resistance exercise x4 weeks at start of RT vs. Arm 2) control.
**'''2009''' {{PMID|19831159}} -- &quot;A 4-week home-based aerobic and resistance exercise program during radiation therapy: a pilot randomized clinical trial.&quot; (Mustian KM, J Support Oncol. 2009 Sep-Oct;7(5):158-67.)
***Outcome: Good adherence to intervention. At 3 months, significantly more daily steps walked, daily minutes of resistance exercise, number of resistance exercise days. Also significantly higher QoL and significantly lower cancer-related fatigue
***Conclusion: Exercise during RT may be beneficial for cancer patients

*'''Houston VA''' -- exercise x8 weeks vs. control
***Randomized. 21 patients with localized PCA, undergoing therapy. Arm 1) RT + aerobic exercise 3x/week x8 weeks vs. Arm 2) RT only
**'''2007''' {{PMID|17964881}} -- &quot;Exercise prevents fatigue and improves quality of life in prostate cancer patients undergoing radiotherapy.&quot; (Monga U, Arch Phys Med Rehabil. 2007 Nov;88(11):1416-22.)
***Outcome: Significant benefit in fatigue, cardiac fitness, strength, flexibility, FACT-P, physical well-being, social well-being, and functional well-being
***Conclusion: 8-week cardiovascular program during RT improves fatigues, well-being, and fitness</text>
      <sha1>j6p1hyr800r69r6l5nkwl55aakljmql</sha1>
    </revision>
  </page>
  <page>
    <title>Vehicle Identification Numbers (VIN codes)/World Manufacturer Identifier (WMI)</title>
    <ns>0</ns>
    <id>142006</id>
    <revision>
      <id>4675752</id>
      <parentid>4672643</parentid>
      <timestamp>2026-10-12T16:10:16Z</timestamp>
      <contributor>
        <username>JustTheFacts33</username>
        <id>3434282</id>
      </contributor>
      <comment>/* List of Many WMIs */</comment>
      <origin>4675752</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="137708" sha1="f33zf31u4qk94cya9ad5r7kdkx7h5b0" xml:space="preserve">==World Manufacturer Identifier==
The first three characters uniquely identify the manufacturer of the vehicle using the '''World Manufacturer Identifier''' or '''WMI''' code. A manufacturer that builds fewer than 1000 vehicles per year uses a 9 as the third digit and the 12th, 13th and 14th position of the VIN for a second part of the identification. Some manufacturers use the third character as a code for a vehicle category (e.g., bus or truck), a division within a manufacturer, or both. For example, within 1G (assigned to General Motors in the United States), 1G1 represents Chevrolet passenger cars; 1G2, Pontiac passenger cars; and 1GC, Chevrolet trucks. 

===WMI Regions===
The first character of the WMI is the region in which the manufacturer is located. In practice, each is assigned to a country of manufacture. Common auto-manufacturing countries are noted. &lt;ref&gt;{{cite web
| url=https://standards.iso.org/iso/3780/
| title=ISO Standards Maintenance Portal: ISO 3780
| publisher=[[wikipedia:International Organization for Standardization]]}}&lt;/ref&gt;

{| class=&quot;wikitable&quot; style=&quot;text-align:center&quot;
|-
! WMI
! Region
! Notes
|-
| A-C
| Africa
| AA-AH = South Africa&lt;br /&gt;BF-BG = Kenya&lt;br /&gt;BU = Uganda&lt;br /&gt;CA-CB = Egypt&lt;br /&gt;DF-DK = Morocco
|-
| E, H-R
| Asia
| E=Russia&lt;br /&gt;H = China&lt;br /&gt;J = Japan&lt;br /&gt;KF-KH = Israel&lt;br /&gt;KL-KR = South Korea&lt;br /&gt;L = China&lt;br /&gt;MA-ME = India&lt;br /&gt;MF-MK = Indonesia&lt;br /&gt;ML-MR = Thailand&lt;br /&gt;MS = Myanmar&lt;br /&gt;MX = Kazakhstan&lt;br /&gt;MY-M0 = India&lt;br /&gt;NF-NG = Pakistan&lt;br /&gt;NL-NR = Turkey&lt;br /&gt;NS-NT = Uzbekistan&lt;br /&gt;PA-PC = Philippines&lt;br /&gt;PF-PG = Singapore&lt;br /&gt;PL-PR = Malaysia&lt;br /&gt;PS-PT = Bangladesh&lt;br /&gt;PV=Cambodia&lt;br /&gt;RA-RB = United Arab Emirates&lt;br /&gt;RF-RK = Taiwan&lt;br /&gt;RL-RN = Vietnam&lt;br /&gt;RS-RT = Saudi Arabia&lt;br /&gt;RU-RW = Russia&lt;br /&gt;R1-R7 = Hong Kong

|-
| S-Z
| Europe
| SA-SM = United Kingdom&lt;br /&gt;SN-ST = Germany (formerly East Germany)&lt;br /&gt;SU-SZ = Poland&lt;br /&gt;TA-TH = Switzerland&lt;br /&gt;TJ-TP = Czech Republic&lt;br /&gt;TR-TV = Hungary&lt;br /&gt;TW-T2 = Portugal&lt;br /&gt;UH-UM = Denmark&lt;br /&gt;UN-UR = Ireland&lt;br /&gt;UU-UX = Romania&lt;br /&gt;U1-U2 = North Macedonia&lt;br /&gt;U5-U7 = Slovakia&lt;br /&gt;VA-VE = Austria&lt;br /&gt;VF-VR = France&lt;br /&gt;VS-VW = Spain&lt;br /&gt;VX-V2 = France (formerly Serbia/Yugoslavia)&lt;br /&gt;V3-V5 = Croatia&lt;br /&gt;V6-V8 = Estonia&lt;br /&gt; W = Germany (formerly West Germany)&lt;br /&gt;XA-XC = Bulgaria&lt;br /&gt;XF-XH = Greece&lt;br /&gt;XL-XR = The Netherlands&lt;br /&gt;XS-XW = Russia (formerly USSR)&lt;br /&gt;XX-XY = Luxembourg&lt;br /&gt;XZ-X0 = Russia&lt;br /&gt;YA-YE = Belgium&lt;br /&gt;YF-YK = Finland&lt;br /&gt;YS-YW = Sweden&lt;br /&gt;YX-Y2 = Norway&lt;br /&gt;Y3-Y5 = Belarus&lt;br /&gt;Y6-Y8 = Ukraine&lt;br /&gt;ZA-ZU = Italy&lt;br /&gt;ZX-ZZ = Slovenia&lt;br /&gt;Z3-Z5 = Lithuania&lt;br /&gt;Z6-Z0 = Russia
|-
| 1-5
| North America
| 1, 4, 5 = United States&lt;br /&gt;2 = Canada&lt;br /&gt;3 = Mexico&lt;br /&gt;7F-70 = United States
|-
| 6-7
| Oceania
| 6A-6W = Australia&lt;br /&gt;7A-7E = New Zealand&lt;br /&gt;Revised: 6A-6X = Australia&lt;br /&gt;6Y-61 = New Zealand
|-
| 8-9
| South America
| 8A-8E = Argentina&lt;br /&gt;8F-8G = Chile&lt;br /&gt;8L-8N = Ecuador&lt;br /&gt;8S-8T = Peru&lt;br /&gt;8X-8Z = Venezuela&lt;br /&gt;82 = Bolivia&lt;br /&gt;84 = Costa Rica&lt;br /&gt;9A-9E, 91-90 = Brazil&lt;br /&gt;9F-9G = Colombia&lt;br /&gt;9S-9V = Uruguay
|}

{| class=&quot;wikitable&quot; style=&quot;text-align:center&quot;
|-
! &amp;nbsp;
! A
! B
! C
! D
! E
! F
! G
! H
! J
! K
! L
! M
! N
! P
! R
! S
! T
! U
! V
! W
! X
! Y
! Z
! 1
! 2
! 3

! 4
! 5
! 6
! 7
! 8
! 9
! 0
|-
| '''A''' || colspan=&quot;8&quot; | South Africa || colspan=&quot;2&quot; | Ivory Coast || colspan=&quot;2&quot; | Lesotho || colspan=&quot;2&quot; | Botswana || colspan=&quot;2&quot; | Namibia || colspan=&quot;2&quot; | Madagascar || colspan=&quot;2&quot; | Mauritius || colspan=&quot;2&quot; | Tunisia || colspan=&quot;2&quot; | Cyprus || colspan=&quot;2&quot; | Zimbabwe || colspan=&quot;2&quot; | Mozambique || colspan=&quot;5&quot; | ''Africa''
|-
| '''B''' || colspan=&quot;2&quot; | Angola || colspan=&quot;1&quot; | Ethiopia || colspan=&quot;2&quot; | ''Africa'' || colspan=&quot;2&quot; | Kenya || colspan=&quot;1&quot; | Rwanda || colspan=&quot;2&quot; | ''Africa'' || colspan=&quot;1&quot; | Nigeria || colspan=&quot;3&quot; | ''Africa'' || colspan=&quot;1&quot; | Algeria || colspan=&quot;1&quot; | ''Africa'' || colspan=&quot;1&quot; | Swaziland || colspan=&quot;1&quot; | Uganda || colspan=&quot;7&quot; | ''Africa''|| colspan=&quot;2&quot; | Libya || colspan=&quot;6&quot; | ''Africa''
|-
| '''C''' || colspan=&quot;2&quot; | Egypt || colspan=&quot;3&quot; | ''Africa'' || colspan=&quot;2&quot; | Morocco || colspan=&quot;3&quot; | ''Africa'' || colspan=&quot;2&quot; | Zambia || colspan=&quot;21&quot; | ''Africa''
|-
| '''D''' || colspan=&quot;33&quot; rowspan=&quot;1&quot; | 
|-
| '''E''' || colspan=&quot;33&quot; | Russia
|-
| '''F''' || colspan=&quot;33&quot; rowspan=&quot;2&quot; | 
|-
| '''G'''
|-
| '''H''' || colspan=&quot;33&quot; | China
|-
| '''J''' || colspan=&quot;33&quot; | Japan
|-
| '''K''' || colspan=&quot;5&quot; | ''Asia'' || colspan=&quot;3&quot; | Israel || colspan=&quot;2&quot; | ''Asia'' || colspan=&quot;5&quot; | South Korea || colspan=&quot;2&quot; | Jordan || colspan=&quot;6&quot; | ''Asia'' || colspan=&quot;3&quot; | South Korea || colspan=&quot;1&quot; | ''Asia'' || colspan=&quot;1&quot; | Kyrgyzstan || colspan=&quot;5&quot; | ''Asia'' 
|-
| '''L''' || colspan=&quot;33&quot; | China
|-
| '''M''' || colspan=&quot;5&quot; | India || colspan=&quot;5&quot; | Indonesia || colspan=&quot;5&quot; | Thailand || colspan=&quot;1&quot; | Myanmar || colspan=&quot;1&quot; | ''Asia'' || colspan=&quot;1&quot; | Mongolia || colspan=&quot;2&quot; | ''Asia'' || colspan=&quot;1&quot; | Kazakhstan || colspan=&quot;12&quot; | India
|-
| '''N''' || colspan=&quot;5&quot; | Iran || colspan=&quot;2&quot; | Pakistan || colspan=&quot;1&quot; | ''Asia'' || colspan=&quot;1&quot; | Iraq || colspan=&quot;1&quot; | ''Asia'' || colspan=&quot;5&quot; | Turkey || colspan=&quot;2&quot; | Uzbekistan || colspan=&quot;1&quot; | ''Asia'' || colspan=&quot;1&quot; | Azerbaijan || colspan=&quot;1&quot; | ''Asia'' || colspan=&quot;1&quot; | Tajikistan || colspan=&quot;1&quot; | Armenia || colspan=&quot;1&quot; | ''Asia'' || colspan=&quot;5&quot; | Iran || colspan=&quot;1&quot; | ''Asia'' || colspan=&quot;2&quot; | Turkey || colspan=&quot;2&quot; | ''Asia''
|-
| '''P''' || colspan=&quot;3&quot; | Philippines || colspan=&quot;2&quot; | ''Asia'' || colspan=&quot;2&quot; | Singapore || colspan=&quot;3&quot; | ''Asia'' || colspan=&quot;5&quot; | Malaysia || colspan=&quot;2&quot; | Bangladesh || colspan=&quot;10&quot; | ''Asia'' || colspan=&quot;6&quot; | India 
|-
| '''R''' || colspan=&quot;2&quot; | UAE || colspan=&quot;3&quot; | ''Asia'' || colspan=&quot;5&quot; | Taiwan || colspan=&quot;3&quot; | Vietnam || colspan=&quot;1&quot; | Laos || colspan=&quot;1&quot; | ''Asia'' || colspan=&quot;2&quot; | Saudi Arabia || colspan=&quot;3&quot; | Russia || colspan=&quot;3&quot; | ''Asia'' || colspan=&quot;7&quot; | Hong Kong || colspan=&quot;3&quot; | ''Asia''
|-
! &amp;nbsp;
! A
! B
! C
! D
! E
! F
! G
! H
! J
! K
! L
! M
! N
! P
! R
! S
! T
! U
! V
! W
! X
! Y
! Z
! 1
! 2
! 3
! 4
! 5
! 6
! 7
! 8
! 9
! 0
|-
| '''S''' || colspan=&quot;12&quot; | United Kingdom || colspan=&quot;5&quot; | Germany &lt;small&gt;(formerly East Germany)&lt;/small&gt; || colspan=&quot;6&quot; | Poland || colspan=&quot;2&quot; | Latvia || colspan=&quot;1&quot; | Georgia || colspan=&quot;1&quot; | Iceland || colspan=&quot;6&quot; | ''Europe''
|-
| '''T''' || colspan=&quot;8&quot; | Switzerland || colspan=&quot;6&quot; | Czech Republic || colspan=&quot;5&quot; | Hungary || colspan=&quot;6&quot; | Portugal || colspan=&quot;3&quot; | Serbia || colspan=&quot;1&quot; | Andorra || colspan=&quot;2&quot; | Netherlands || colspan=&quot;2&quot; | ''Europe''
|-
| '''U''' || colspan=&quot;3&quot; | Spain || colspan=&quot;4&quot; | ''Europe'' || colspan=&quot;5&quot; | Denmark || colspan=&quot;3&quot; | Ireland || colspan=&quot;2&quot; | ''Europe'' || colspan=&quot;4&quot; | Romania || colspan=&quot;2&quot; | ''Europe'' || colspan=&quot;2&quot; | North Macedonia || colspan=&quot;2&quot; | ''Europe'' || colspan=&quot;3&quot; | Slovakia || colspan=&quot;3&quot; | Bosnia &amp; Herzogovina
|-
| '''V''' || colspan=&quot;5&quot; | Austria || colspan=&quot;10&quot; | France || colspan=&quot;5&quot; | Spain || colspan=&quot;5&quot; | France &lt;small&gt;(formerly Yugoslavia &amp; Serbia)&lt;/small&gt; || colspan=&quot;3&quot; | Croatia || colspan=&quot;3&quot; | Estonia || colspan=&quot;2&quot; | ''Europe''
|-
| '''W''' || colspan=&quot;33&quot; | Germany
|-
| '''X''' || colspan=&quot;3&quot; | Bulgaria || colspan=&quot;2&quot; | Russia || colspan=&quot;3&quot; | Greece || colspan=&quot;2&quot; | Russia || colspan=&quot;5&quot; | Netherlands || colspan=&quot;5&quot; | Russia &lt;small&gt;(formerly USSR)&lt;/small&gt; || colspan=&quot;2&quot; | Luxembourg || colspan=&quot;11&quot; | Russia
|-
| '''Y''' || colspan=&quot;5&quot; | Belgium || colspan=&quot;5&quot; | Finland || colspan=&quot;2&quot; | ''Europe'' || colspan=&quot;1&quot; | Malta || colspan=&quot;2&quot; | ''Europe'' || colspan=&quot;5&quot; | Sweden || colspan=&quot;5&quot; | Norway || colspan=&quot;3&quot; | Belarus || colspan=&quot;3&quot; | Ukraine || colspan=&quot;2&quot; | ''Europe''
|-
| '''Z''' || colspan=&quot;18&quot; | Italy || colspan=&quot;2&quot; | ''Europe'' || colspan=&quot;3&quot; | Slovenia || colspan=&quot;1&quot; | San Marino|| colspan=&quot;1&quot; | ''Europe''|| colspan=&quot;3&quot; | Lithuania || colspan=&quot;5&quot; | Russia
|-
| '''1''' || colspan=&quot;33&quot; | United States
|-
| '''2''' || colspan=&quot;28&quot; | Canada || colspan=&quot;5&quot; | ''North America'' 
|-
| '''3''' || colspan=&quot;21&quot; | Mexico || colspan=&quot;5&quot; | ''North America'' || colspan=&quot;1&quot; | Nicaragua || colspan=&quot;1&quot; | Dom. Rep. || colspan=&quot;1&quot; | Honduras || colspan=&quot;1&quot; | Panama || colspan=&quot;2&quot; | Puerto Rico || colspan=&quot;1&quot; | ''North America'' 
|-
| '''4''' || colspan=&quot;33&quot; rowspan=&quot;2&quot; | United States
|-
| '''5''' 
|-
| '''6''' || colspan=&quot;21&quot; | Australia || colspan=&quot;3&quot; | New Zealand || colspan=&quot;9&quot; | ''Oceania''
|-
| '''7''' || colspan=&quot;5&quot; | New Zealand || colspan=&quot;28&quot; | United States
|-
| '''8''' || colspan=&quot;5&quot; | Argentina || colspan=2 | Chile || colspan=&quot;3&quot; | ''South America'' || colspan=&quot;3&quot; | Ecuador || colspan=&quot;2&quot; | ''South America'' || colspan=&quot;2&quot; | Peru || colspan=&quot;3&quot; | ''South America'' || colspan=&quot;3&quot; | Venezuela || colspan=&quot;1&quot; | ''SA'' || colspan=&quot;1&quot; | Bolivia || colspan=&quot;1&quot; | ''SA'' || colspan=&quot;1&quot; | Costa Rica || colspan=&quot;6&quot; | ''South America'' 
|-
| '''9''' || colspan=&quot;5&quot; | Brazil || colspan=&quot;2&quot; | Colombia || colspan=&quot;8&quot; | ''South America''  || colspan=&quot;4&quot; | Uruguay || colspan=&quot;4&quot; | ''South America'' || colspan=&quot;10&quot; | Brazil 
|-
| '''0''' || colspan=&quot;33&quot; rowspan=&quot;1&quot; | 
|}

===List of Many WMIs===
The [[w:Society of Automotive Engineers|Society of Automotive Engineers]] (SAE) in the US assigns WMIs to countries and manufacturers.&lt;ref&gt;{{cite web
| url=https://www.iso.org/standard/45844.html
| title=ISO 3780:2009 - Road vehicles — World manufacturer identifier (WMI) code
| date=October 2009
| publisher=International Organization for Standardization}}&lt;/ref&gt; The following table contains a list of mainly commonly used WMIs, although there are many others assigned.

{| class=&quot;wikitable x&quot; style=&quot;text-align:center&quot;
|-
! WMI !! Manufacturer
|-
| AAA|| Audi South Africa made by Volkswagen of South Africa
|-
| AAK|| FAW Vehicle Manufacturers SA (PTY) Ltd.
|-
| AAM|| MAN Automotive (South Africa) (Pty) Ltd. (includes VW Truck &amp; Bus)
|-
|AAP || VIN restamped by South African Police Service (so-called SAPVIN or AAPV number)
|-
| AAV || Volkswagen South Africa
|-
| AAW || Challenger Trailer Pty Ltd. (South Africa)
|-
| AA9/CN1 || TR-Tec Pty Ltd. (South Africa)
|-
| ABJ || Mitsubishi Colt &amp; Triton pickups made by Mercedes-Benz South Africa 1994–2011
|-
| ABJ || Mitsubishi Fuso made by Daimler Trucks &amp; Buses Southern Africa
|-
| ABM || BMW Southern Africa
|-
| ACV || Isuzu Motors South Africa 2018-
|-
| AC5 || [[../Hyundai/VIN Codes|Hyundai]] Automotive South Africa 
|-
| AC9/BM1 || Beamish Beach Buggies (South Africa)
|-
| ADB || Mercedes-Benz South Africa car
|-
| ADD || UD Trucks Southern Africa (Pty) Ltd.
|-
| ADM || General Motors South Africa (includes Isuzu through 2018)
|-
| ADN || Nissan South Africa (Pty) Ltd.
|-
| ADR || Renault Sandero made by Nissan South Africa (Pty) Ltd.
|-
| ADX || Tata Automobile Corporation (SA) Ltd.
|-
| AE9/MT1 || Backdraft Racing (South Africa)
|-
| AFA || Ford Motor Company of Southern Africa &amp; Samcor
|-
| AFB || Mazda BT-50 made by Ford Motor Company of Southern Africa
|-
| AFD || BAIC Automotive South Africa
|-
| AFZ || Fiat Auto South Africa
|-
| AHH || Hino South Africa
|-
| AHM || Honda Ballade made by Mercedes-Benz South Africa 1982–2000
|-
| AHT || Toyota South Africa Motors (Pty.) Ltd.
|-
| BF9/|| KIBO Motorcycles, Kenya
|-
| BUK || Kiira Motors Corporation, Uganda
|-
| BR1 || Mercedes-Benz Algeria (SAFAV MB)
|-
| BRY || FIAT Algeria
|-
| CA3 || MCV bus (Egypt)
|-
| DDY || Geyushi Motors (bus) (Egypt)
|-
| DF9/|| Laraki (Morocco)
|-
| EAA || Aurus Motors (Russia)
|-
| EAN || Evolute (Russia)
|-
| EAU || Elektromobili Manufacturing Rus - EVM (Russia)
|-
| EBE || Sollers-Auto (Russia)
|-
| EBZ || Nizhekotrans bus (Russia)
|-
| ECE || XCITE (Russia)
|-
| ECW || Trans-Alfa bus (Russia)
|-
| EDE || Tenet (Russia)
|-
| HAC || GAC Motor (Aion)
|-
| HA0 || Wuxi Sundiro Electric Vehicle Co., Ltd. (Palla, Parray)
|-
| HA6 || Jiangsu Niu Electric Technology Co., Ltd. (Niu)
|-
| HA7 || Jinan Qingqi KR Motors Co., Ltd.
|-
| HES || smart Automobile Co., Ltd. (Mercedes-Geely joint venture) 
|-
| HGL ||  Farizon Auto van (Geely)
|-
| HGX ||  Wuling Motors commercial vehicle (Geely)
|-
| HHZ || Huazi Automobile
|-
| HJN || Nio, Firefly 
|-
| HJR || Chery Commercial Vehicle (Anhui) Co., Ltd. Jetour made by Chery Commercial Vehicle
|-
| HJZ || Juzhen Chengshi van
|-
| HJ4 || BAW car
|-
| HLX || Li Auto
|-
| HL4 || Zhejiang Morini Vehicle Co., Ltd. &lt;br /&gt;(Moto Morini subsidiary of Taizhou Zhongneng Motorcycle Co., Ltd.)
|-
| HM2 || Shandong Bentu New Energy Vehicle Industry Co.,Ltd.
|-
| HRV || Beijing Henrey Automobile Technology Co., Ltd.
|-
| HT5 || Zhejiang Jianying Locomotive Co., Ltd. (motorcycle)
|-
| HVW || Volkswagen Anhui
|-
| HWM || WM Motor Technology Co., Ltd. (Weltmeister)
|-
| HXM || Xiaomi
|-
| HZ2 || Taizhou Zhilong Technology Co., Ltd (motorcycle)
|-
| H0D || Taizhou Qianxin Vehicle Co., Ltd. (motorcycle)
|-
| H0G || Wisdom (Fujian) Motor Co., Ltd. (bus)
|-
| JAA || Isuzu truck, Holden Rodeo TF, Opel Campo, Bedford/Vauxhall Brava pickup made by Isuzu in Japan
|-
| JAB || Isuzu car
|-
| JAC || Isuzu SUV, Opel/Vauxhall Monterey &amp; Holden Jackaroo/Monterey made by Isuzu in Japan
|-
| JAE || Acura SLX made by Isuzu
|-
| JAL || Isuzu commercial trucks &amp; &lt;br /&gt; Chevrolet commercial trucks made by Isuzu 2016+ &amp; &lt;br /&gt; Hino S-series truck made by Isuzu (Incomplete Vehicle - medium duty)
|-
| JAM || Isuzu commercial trucks (Incomplete Vehicle - light duty)
|-
| JA3 || Mitsubishi car (for North America)
|-
| JA4 || Mitsubishi MPV/SUV (for North America) &amp; Nissan Rogue PHEV '26 made by Mitsubishi
|-
| JA7 || Mitsubishi truck (for North America)
|-
| JB3 || Dodge car made by Mitsubishi Motors
|-
| JB4 || Dodge MPV/SUV made by Mitsubishi Motors
|-
| JB7 || Dodge truck made by Mitsubishi Motors
|-
| JC0 || Ford brand cars made by Mazda
|-
| JC1 || Fiat 124 Spider made by Mazda
|-
| JC2 || Ford Courier made by Mazda
|-
| JDA || Daihatsu, Subaru Justy made by Daihatsu
|-
| JD1 || Daihatsu car
|-
| JD2 || Daihatsu SUV
|-
| JD4 || Daihatsu truck
|-
| JE3 || Eagle car made by Mitsubishi Motors
|-
| JE4 || Mitsubishi Motors
|-
| JF1 || [[../Subaru/VIN Codes|Subaru]] car &amp; Scion FR-S/Toyota 86/Toyota GR86 made by Subaru
|-
| JF2 || [[../Subaru/VIN Codes|Subaru]] SUV
|-
| JF3 || [[../Subaru/VIN Codes|Subaru]] truck
|-
| JF4 || Saab 9-2X made by Subaru
|-
| JG1 || Chevrolet/Geo car made by Suzuki
|-
| JG2 || Pontiac car made by Suzuki
|-
| JG7 || Pontiac/Asuna car made by Suzuki for GM Canada
|-
| JGC || Chevrolet/Geo SUV made by Suzuki (classified as a truck)
|-
| JGT || GMC SUV made by Suzuki for GM Canada (classified as a truck)
|-
| JHA || Hino truck
|-
| JHB || Hino incomplete vehicle
|-
| JHD || Hino
|-
| JHF || Hino
|-
| JHH || Hino incomplete vehicle
|-
| JHF-JHG, JHL-JHN, JHZ,&lt;br/&gt;JH1-JH5 || [[../Honda/VIN Codes|Honda]]
|-
| JHL || [[../Honda/VIN Codes|Honda]] MPV/SUV
|-
| JHM || [[../Honda/VIN Codes|Honda]] car
|-
| JH1 || [[../Honda/VIN Codes|Honda]] truck
|-
| JH2 || [[../Honda/VIN Codes|Honda]] motorcycle/ATV
|-
| JH3 || [[../Honda/VIN Codes|Honda]] ATV
|-
| JH4 || Acura car
|-
| JH6 || Hino incomplete vehicle
|-
| JJ3 || Chrysler brand car made by Mitsubishi Motors
|-
| JKA || Kawasaki (motorcycles)
|-
| JKB || Kawasaki (motorcycles)
|-
| JKM || Mitsuoka
|-
| JKS || Suzuki Marauder 1600/Boulevard M95 motorcycle made by Kawasaki
|-
| JK8 || Suzuki QUV620F UTV made by Kawasaki
|-
| JLB || Mitsubishi Fuso Truck &amp; Bus Corp.
|-
| JLF || Mitsubishi Fuso Truck &amp; Bus Corp.
|-
| JLS || Sterling Truck 360 made by Mitsubishi Fuso Truck &amp; Bus Corp.
|-
| JL5 || Mitsubishi Fuso Truck &amp; Bus Corp.
|-
| JL6 || Mitsubishi Fuso Truck &amp; Bus Corp.
|-
| JL7 || Mitsubishi Fuso Truck &amp; Bus Corp.
|-
| JMA || Mitsubishi Motors (right-hand drive) for Europe
|-
| JMB || Mitsubishi Motors (left-hand drive) for Europe
|-
| JMF || Mitsubishi Motors for Australia (including Mitsubishi Express made by Renault)
|-
| JMP || Mitsubishi Motors (left-hand drive)
|-
| JMR || Mitsubishi Motors (right-hand drive)
|-
| JMY || Mitsubishi Motors (left-hand drive) for South America &amp; Middle East
|-
| JMZ || Mazda for Europe export &amp; Mazda 2 made by Ford Spain &amp; Mazda 2 Hybrid made by Toyota Motor Manufacturing France
|-
| JM0 || Mazda for Oceania export
|-
| JM1 || Mazda car
|-
| JM2 || Mazda truck
|-
| JM3 || Mazda MPV/SUV
|-
| JM4 || Mazda
|-
| JM6 || Mazda
|-
| JM7 || Mazda
|-
| JNA || Nissan Diesel/UD Trucks (incomplete vehicle)
|-
| JNC || Nissan Diesel/UD Trucks
|-
| JNE || Nissan Diesel/UD Trucks (truck)
|-
| JNK || Infiniti car
|-
| JNR || Infiniti SUV
|-
| JNX || Infiniti incomplete vehicle
|-
| JN1 || Nissan car &amp; Infiniti car
|-
| JN3 || Nissan incomplete vehicle
|-
| JN6 || Nissan truck/van &amp; Mitsubishi Fuso Canter Van
|-
| JN8 || Nissan MPV/SUV &amp; Infiniti SUV
|-
| JPA || International Trucks made by Nissan Diesel (incomplete vehicle)
|-
| JPB || International Trucks made by Nissan Diesel (tractor truck)
|-
| JPC || Nissan Diesel/UD Trucks
|-
| JPE || International Trucks made by Nissan Diesel (truck)
|-
| JP3 || Plymouth car made by Mitsubishi Motors
|-
| JP4 || Plymouth MPV/SUV made by Mitsubishi Motors
|-
| JP7 || Plymouth truck made by Mitsubishi Motors
|-
| JR2 || Isuzu Oasis made by Honda
|-
| JSA || Suzuki ATV &amp; '03 Kawasaki KFX400 ATV made by Suzuki, Suzuki car/SUV (outside N. America), Holden Cruze YG made by Suzuki
|-
| JSK || Kawasaki KLX125/KLX125L motorcycle made by Suzuki
|-
| JSL || '04-'06 Kawasaki KFX400 ATV made by Suzuki
|-
| JST || Suzuki Across SUV made by Toyota
|-
| JS1 || Suzuki motorcycle &amp; Kawasaki KLX400S/KLX400SR motorcycle made by Suzuki
|-
| JS2 || Suzuki car
|-
| JS3 || Suzuki SUV
|-
| JS4 || Suzuki truck
|-
| JTB || Toyota bus
|-
| JTD || Toyota car
|-
| JTE || Toyota MPV/SUV
|-
| JTF || Toyota van/truck
|-
| JTG || Toyota MPV/bus
|-
| JTH || Lexus car
|-
| JTJ || Lexus SUV
|-
| JTK || Toyota car
|-
| JTL || Toyota SUV
|-
| JTM || Toyota SUV, Subaru Uncharted, Solterra, and Trailseeker made by Toyota
|-
| JTN || Toyota car
|-
| JTP || Toyota SUV
|-
| JT1 || [[../Toyota/VIN Codes|Toyota]] van
|-
| JT2 || Toyota car
|-
| JT3 || Toyota MPV/SUV
|-
| JT4 || Toyota truck/van
|-
| JT5 || Toyota incomplete vehicle
|-
| JT6 || Lexus SUV
|-
| JT7 || Toyota bus/van
|-
| JT8 || Lexus car
|-
| JW6 || Mitsubishi Fuso division of Mitsubishi Motors (through mid-2003)
|-
| JYA || Yamaha motorcycles
|-
| JYE || Yamaha snowmobile
|-
| JY3 || Yamaha 3-wheel ATV
|-
| JY4 || Yamaha 4-wheel ATV
|-
| J81 || Chevrolet/Geo car made by Isuzu
|-
| J87 || Pontiac/Asüna car made by Isuzu for GM Canada
|-
| J8B || Chevrolet commercial trucks made by Isuzu (incomplete vehicle - medium duty)
|-
| J8C || Chevrolet commercial trucks made by Isuzu (truck)
|-
| J8D || GMC commercial trucks made by Isuzu (incomplete vehicle - medium duty)
|-
| J8T || GMC commercial trucks made by Isuzu (truck)
|-
| J8Z || Chevrolet LUV pickup truck made by Isuzu (truck)
|-
| KF3 || Merkavim (Israel)
|-
| KF6 || Automotive Industries, Ltd. (Israel)
|-
| KF9/004 || Tomcar (Israel)
|-
| KG9/002 || Charash Ashdod (truck trailer) (Israel)
|-
| KG9/004 || H. Klein (truck trailer) (Israel)
|-
| KG9/007 || Agam Trailers (truck trailer) (Israel)
|-
| KG9/009 || Merkavey Noa (trailer) (Israel)
|-
| KG9/010 || Weingold Trailers (trailer) (Israel)
|-
| KG9/011 || Netzer Sereni (truck trailer) (Israel)
|-
| KG9/015 || Merkaz Hagrorim (trailer) (Israel)
|-
| KG9/035 || BEL Technologies (truck trailer) (Israel)
|-
| KG9/091 || Jansteel (truck trailer) (Israel)
|-
| KG9/101 || Bassamco (truck trailer) (Israel)
|-
| KG9/104 || Global Handasa (truck trailer) (Israel)
|-
| KL || Daewoo [[../GM/VIN Codes|General Motors]] South Korea
|-
| KLA || Daewoo/GM Daewoo/GM Korea (Chevrolet/Alpheon)&lt;br /&gt; from Bupyeong &amp; Kunsan plants
|-
| KLP || CT&amp;T United (battery electric low-speed vehicles)
|-
| KLT || Tata Daewoo
|-
| KLU || Tata Daewoo
|-
| KLY || Daewoo/GM Daewoo/GM Korea (Chevrolet) from Changwon plant (Tico/Matiz/Matiz Creative/Spark/Damas/Labo)
|-
| KL1 || GM Daewoo/GM Korea (Chevrolet car)
|-
| KL2 || Daewoo/GM Daewoo (Pontiac car)
|-
| KL3 || GM Daewoo/GM Korea (Holden)
|-
| KL4 || GM Korea (Buick MPV/SUV)
|-
| KL5 || GM Daewoo (Suzuki car) US: 2004-2008, Canada: 2004-2011
|-
| KL5 || Daewoo Bus Corp./Zyle Daewoo Bus 2004-2017
|-
| KL6 || GM Daewoo (GMC MPV/SUV)
|-
| KL7 || Daewoo (GM Canada brands: Passport car, Asuna car (Pre-2000))
|-
| KL7 || GM Daewoo/GM Korea (Chevrolet MPV/SUV (Post-2000))
|-
| KL8 || GM Daewoo/GM Korea (Chevrolet car from Changwon plant (Spark))
|-
| KM || [[../Hyundai/VIN Codes|Hyundai]]
|-
| KMC || Hyundai commercial truck
|-
| KME || Hyundai commercial truck (semi-tractor)
|-
| KMF || Hyundai van &amp; commercial truck &amp; Bering Truck
|-
| KMH || Hyundai car &amp; Mitsubishi Precis ('87 - 3/10/88) &amp; Mexican market Dodges made by Hyundai
|-
| KMJ || Hyundai minibus/bus
|-
| KMT || Genesis Motor car
|-
| KMU || Genesis Motor SUV
|-
| KMX || Hyundai Galloper SUV
|-
| KMY || Daelim Motor Company, Ltd/DNA Motors Co., Ltd. (motorcycles)
|-
| KM1 || Hyosung Motors (motorcycles)
|-
| KM4 || Hyosung Motors/S&amp;T Motors/KR Motors (motorcycles)
|-
| KM8 || Hyundai SUV
|-
| KNA || Kia car
|-
| KNC || Kia truck
|-
| KND || Kia MPV/SUV &amp; Hyundai Entourage
|-
| KNE || Kia for Europe export
|-
| KNF || Kia, special vehicles
|-
| KNG || Kia minibus/bus
|-
| KNJ || Ford Festiva &amp; Aspire made by Kia
|-
| KNL || Kia Elan/Vigato made by Kia Motech
|-
| KNM || Renault Samsung Motors, Nissan Rogue made by Renault Samsung, Nissan Sunny made by Renault Samsung
|-
| KNM || Renault Korea Co., Ltd.
|-
| KN1 || Asia Motors
|-
| KN2 || Asia Motors
|-
| KPA || SsangYong/KG Mobility (KGM) pickup
|-
| KPB || SsangYong car or For S. Korea domestic market: SsangYong/KG Mobility (KGM) SUV/MPV 
|-
| KPD || SsangYong bus (TransStar, Istana minibus, Rodius/Korando Turismo 11-seater)
|-
| KPH || Mitsubishi Precis (3/11/88 - '94)
|-
| KPT || SsangYong/KG Mobility (KGM) SUV/MPV (For export)
|-
| LAA || Shanghai Jialing Vehicle Co., Ltd. (motorcycle)
|-
| LAE || Jinan Qingqi Motorcycle
|-
| LAL || Sundiro [[../Honda/VIN Codes|Honda]] Motorcycle
|-
| LAN || Changzhou Yamasaki Motorcycle
|-
| LAP || Chongqing Jianshe Motorcycle Co., Ltd.
|-
| LAP || Zhuzhou Nanfang Motorcycle Co., Ltd.
|-
| LAT || Luoyang Northern Ek Chor Motorcycle Co., Ltd. (Dayang)
|-
| LA6 || Xiamen King Long United Automotive Industry Co., Ltd. (bus)
|-
| LA7 || Radar Auto, Farizon Auto (Geely) made by Shandong Tangjun Ouling Automobile Manufacture Co,. Ltd.
|-
| LA8 || Anhui Ankai
|-
| LA9/AYS || Jiangsu Alfa Bus Co., Ltd. (bus)
|-
| LA9/BFC || Beijing North Huade Neoplan Bus Co., Ltd.
|-
| LA9/FBC || Xiamen Fengtai Bus &amp; Coach International Co., Ltd. (FTBCI) (bus)
|-
| LA9/HFF || Anhui Huaxia Vehicle Manufacturing Co., Ltd. (bus)
|-
| LA9/JXK || CHTC Bonluck Bus Co., Ltd.
|-
| LA9/LC0 || BYD
|-
| LA9/LFJ || Xinlongma Automobile
|-
| LA9/LM6 || SRM Shineray
|-
| LBB || Zhejiang Qianjiang Motorcycle (QJ Motor/Keeway/Benelli)
|-
| LBE || Beijing [[../Hyundai/VIN Codes|Hyundai]] (Hyundai, Shouwang)
|-
| LBM || Zongshen Piaggio
|-
| LBP || Chongqing Jianshe Yamaha Motor Co. Ltd. (motorcycles)
|-
| LBV || BMW Brilliance (BMW, Zinoro)
|-
| LBX || Jiangsu Kinroad Xintian Motorcycle Manufacture Co. Ltd. (motorcycles)
|-
| LBZ || Yantai Shuchi Vehicle Co., Ltd. (bus)
|-
| LB1 || Fujian Benz
|-
| LB2 || Geely Motorcycles
|-
| LB3 || Zhejiang Geely Holding Group (Geely, Galaxy, Geometry, Kandi)
|-
| LB4 || Chongqing Yinxiang Motorcycle Group Co., Ltd.
|-
| LB5 || Foshan City Fosti Motorcycle Co., Ltd.
|-
| LB7 || Tibet New Summit Motorcycle Co., Ltd.
|-
| LCE || Hangzhou Chunfeng Motorcycles (CFMOTO)
|-
| LCR || Gonow
|-
| LC0 || BYD Auto (BYD, Denza)
|-
| LC2 || Changzhou Kwang Yang Motor Co., Ltd. (Kymco)
|-
| LC6 || Changzhou Haojue Suzuki Motorcycle Co. Ltd.
|-
| LDB || Dadi Auto
|-
| LDC || Dongfeng Peugeot Citroen Automobile Co., Ltd. (DPCA), Dongfeng Fengshen (Aeolus) L60
|-
| LDD || Dandong Huanghai Automobile
|-
| LDF || Dezhou Fulu Vehicle Co., Ltd. (motorcycles), BAW Yuanbao electric car (Ace P1 in Norway)
|-
| LDK || FAW Bus (Dalian) Co., Ltd.
|-
| LDN || Soueast (South East (Fujian) Motor Co., Ltd.) including Mitsubishi made by Soueast
|-
| LDP || Dongfeng, Dongfeng Fengshen (Aeolus), Voyah, Renault City K-ZE/Venucia e30 made by eGT New Energy Automotive
|-
| LDY || Zhongtong Bus Holding Co. Ltd.
|-
| LD3 || Guangdong Tayo Motorcycle Technology Co. (Zontes) (motorcycle)
|-
| LD5 || Benzhou Vehicle Industry Group Ltd. (motorcycle)
|-
| LD9/L3A || SiTech (FAW)
|-
| LEC || Tianjin Qingyuan Electric Vehicle Co., Ltd.
|-
| LEF || Jiangling Motors Corporation Ltd. (JMC)
|-
| LEH || Zhejiang Riya Motorcycle Co. Ltd.
|-
| LET || Jiangling-Isuzu Motors, China
|- 
| LEW || Dongfeng commercial vehicle
|- 
| LE4 || Beijing Benz &amp; Beijing Benz-Daimler Chrysler Automotive Co. (Chrysler, Jeep, Mitsubishi, Mercedes-Benz) &amp; Beijing Jeep Corp.
|-
| LE8 || Guangzhou Huaye Electric Vehicle Technology Co., Ltd. (Formerly Guangzhou Panyu Huanan Motors Group Co., Ltd.) (motorcycles)
|-
| LFB || FAW Group (Bestune, Hongqi) &amp; Mazda made under license by FAW (Mazda 8, CX-7)
|-
| LFF || Zhejiang Taizhou Wangye Power Co., Ltd.
|-
| LFG || Taizhou Chuanl Motorcycle Manufacturing
|-
| LFJ || Fujian Motors Group (Keyton)
|-
| LFM || FAW Toyota Motor (Toyota, Ranz)
|-
| LFN || FAW Bus (Wuxi) Co., Ltd. (truck, bus)
|-
| LFP || FAW Car, Bestune, Hongqi (passenger vehicles) &amp; Mazda made under license by FAW (Mazda 6, CX-4)
|-
| LFT || FAW (trailers)
|-
| LFU || Lifeng Group Co., Ltd. (motorcycles)
|-
| LFV || FAW-Volkswagen (VW, Audi, Jetta, Kaili)
|-
| LFW || FAW JieFang (truck)
|-
| LFX || Sany Heavy Industry (truck)
|-
| LFY || Changshu Light Motorcycle Factory
|-
| LFZ || Leapmotor
|-
| LF3 || Lifan Motorcycle 
|-
| LGA || Dongfeng Commercial Vehicle Co., Ltd. trucks
|-
| LGB || Dongfeng Nissan (Nissan, Infiniti, Venucia)
|-
| LGB || Dongfeng Commercial Vehicle Co., Ltd. 
|-
| LGC || Dongfeng Commercial Vehicle Co., Ltd. bus chassis
|-
| LGD || Dongfeng Commercial Vehicle Co., Ltd. 
|-
| LGF || Dongfeng Commercial Vehicle Co., Ltd. bus chassis
|-
| LGG || Dongfeng Liuzhou Motor (Forthing/Fengxing)
|-
| LGJ || Dongfeng Fengshen (Aeolus)
|-
| LGL || Guilin Daewoo
|-
| LGV || Heshan Guoji Nanlian Motorcycle Industry Co., Ltd.
|-
| LGW || Great Wall Motor (GWM, Haval, Ora, Tank, Wey)
|-
| LGX || BYD Auto (BYD, Fangchengbao)
|-
| LGZ || Guangzhou Denway Bus
|-
| LG6 || Dayun Group
|-
| LHA || Shuanghuan Auto
|-
| LHB || Beijing Automotive Industry Holding
|-
| LHG || GAC Honda (Honda, Everus, Acura)
|-
| LHJ || Chongqing Astronautic Bashan Motorcycle Manufacturing Co., Ltd.
|-
| LHM || Dongfeng Renault Automobile Co.
|-
| LHW || CRRC Electric Vehicle Co., Ltd. (bus)
|-
| LH0 || WM Motor Technology Co., Ltd. (Weltmeister)
|-
| LH1 || FAW-Haima, China
|-
| LJC || Jincheng Corporation
|-
| LJD || Yueda Kia (previously Dongfeng Yueda Kia) (Kia, Horki) &amp; Human Horizons - HiPhi (made under contract by Yueda Kia)
|-
| LJM || Sunlong (bus)
|-
| LJN || Zhengzhou Nissan
|-
| LJR || CIMC Vehicles Group (truck trailer)
|-
| LJS || Yaxing Coach, Asiastar Bus
|-
| LJU || Shanghai Maple Automobile &amp; Kandi &amp; Zhidou
|-
| LJU || Lotus Technology (Wuhan Lotus Cars Co., Ltd.)
|-
| LJV || Sinotruk Chengdu Wangpai Commercial Vehicle Co., Ltd.
|-
| LJW || JMC Landwind
|-
| LJX || JMC Ford
|-
| LJ1 || JAC (JAC, Sehol)
|-
| LJ1 || Nio, Inc.
|-
| LJ4 || Shanghai Jmstar Motorcycle Co., Ltd.
|-
| LJ5 || Cixi Kingring Motorcycle Co., Ltd. (Jinlun)
|-
| LJ8 || Zotye Auto made by Jiangnan Automobile
|-
| LKC || BAIC commercial vehicles, previously Changhe
|-
| LKG || Youngman Lotus Automobile Co., Ltd.
|-
| LKH || Hafei Motor
|-
| LKL || Higer Bus
|-
| LKT || Yunnan Lifan Junma Vehicle Co., Ltd. commercial vehicles
|-
| LK2 || Anhui JAC Bus
|-
| LK6 || SAIC-GM-Wuling (Wuling, Baojun) microcars and other vehicles
|-
| LK8 || Zhejiang Yule New Energy Automobile Technology Co., Ltd. (ATV)
|-
| LLC || Loncin Motor Co., Ltd. (motorcycle)
|-
| LLJ || Jiangsu Xinling Motorcycle Fabricate Co., Ltd.
|-
| LLN || Qoros 
|-
| LLP || Zhejiang Jiajue Motorcycle Manufacturing Co., Ltd.
|-
| LLU || Dongfeng Fengxing Jingyi
|-
| LLV || Lifan, Maple (owned by Geely), Livan Automotive
|-
| LLX || Yudo Auto
|-
| LL0 || Sanmen County Yongfu Machine Co., Ltd. (motorcycles)
|-
| LL2 || WM Motor Technology Co., Ltd. (Weltmeister)
|-
| LL3 || Xiamen Golden Dragon Bus Co. Ltd.
|-
| LL6 || GAC Mitsubishi Motors Co., Ltd. (formerly Hunan Changfeng)
|-
| LL8 || Jiangsu Linhai Yamaha Motor Co., Ltd.
|-
| LMC || Suzuki Hong Kong (motorcycles)
|-
| LME || Skyworth (formerly Skywell), Elaris Beo
|-
| LMF || Jiangmen Zhongyu Motor Co., Ltd.
|-
| LMG || GAC Motor, Trumpchi, [[w:Dodge Attitude#Fourth generation (2025)|Dodge Attitude made by GAC]]
|-
| LMH || Jiangsu Guowei Motor Co., Ltd. (Motoleader)
|-
| LMP || Farizon Auto (Geely Sichuan Commercial Vehicle Co., Ltd.) 
|-
| LMV || Haima Car Co., Ltd.
|-
| LMV || XPeng Motors G3 (not G3i) made by Haima
|-
| LMW || GAC Group, [[w:Trumpchi GS5#Dodge Journey|Dodge Journey made by GAC]]
|-
| LMX || Forthing (Dongfeng Fengxing)
|-
| LM0 || Wangye Holdings Co., Ltd. (motorcycles)
|-
| LM6 || SWM (automobiles)
|-
| LM8 || Seres (formerly SF Motors), AITO
|-
| LNA || GAC Aion New Energy Automobile Co., Ltd., Hycan
|-
| LNB || BAIC Motor (Senova, Weiwang, Huansu) &amp; Arcfox &amp; Xiaomi SU7 built by BAIC
|-
| LND || JMEV (Jiangxi Jiangling Group New Energy Vehicle Co., Ltd.), Eveasy/Mobilize Limo
|-
| LNE || Zhejiang CRRC Electric Vehicle Co., Ltd. (bus)
|-
| LNP || NAC MG UK Limited &amp; Nanjing Fiat Automobile
|-
| LNN || Chery Automobile, Omoda, Jaecoo
|-
| LNV || Naveco (Nanjing Iveco Automobile Co. Ltd.)
|-
| LNX || Dongfeng Liuzhou Motor (Chenglong trucks)
|-
| LNY || Yuejin
|-
| LPA || Changan PSA (DS Automobiles)
|-
| LPE || BYD Auto
|-
| LPS || Polestar
|-
| LP6 || Guangzhou Panyu Haojian Motorcycle Industry Co., Ltd.
|-
| LRB || SAIC-General Motors (Buick for export)
|-
| LRD || Beijing Foton Daimler Automotive Co., Ltd. Auman trucks
|-
| LRE || SAIC-General Motors (Cadillac for export)
|-
| LRP || Chongqing Rato Power Co. Ltd. (Asus)
|-
| LRR || Ningbo Longjia Power Technology Co., Ltd. (motorcycles)
|-
| LRW || Tesla, Inc. (Gigafactory Shanghai)
|-
| LR4 || Yadi Technology Group
|-
| LR6 || Guangzhou Dayun Vehicle Co., Ltd.
|-
| LSC || Changan Automobile (light truck)
|-
| LSF || SAIC Maxus or LDV pickup/SUV &amp; Chevrolet S10 Max &amp; Shanghai Sunwin Bus Corporation
|-
| LSG || SAIC-General Motors (For China: Chevrolet, Buick, Cadillac, Sail Springo, For export: Chevrolet)
|-
| LSH || SAIC Maxus van or LDV van &amp; Chevrolet Express Max
|-
| LSJ || SAIC MG &amp; SAIC Roewe &amp; IM Motors &amp; Rising Auto
|-
| LSK || SAIC Maxus or LDV van
|-
| LSV || SAIC-Volkswagen (VW, Skoda, Audi, Tantus)
|-
| LSY || Brilliance (Jinbei, Zhonghua) &amp; Jinbei GM
|-
| LS3 || Hejia New Energy Vehicle Co., Ltd
|-
| LS4 || Changan Automobile (MPV/SUV)
|-
| LS5 || Changan Automobile (car) &amp; Changan Suzuki
|-
| LS6 || Changan Automobile &amp; Deepal Automobile &amp; Avatr
|-
| LS7 || JMC Heavy Duty Truck Co., Ltd.
|-
| LS8 ||Henan Shaolin Auto Co., Ltd. (bus)
|-
| LTA || ZX Auto
|-
| LTN || Soueast-built Chrysler &amp; Dodge vehicles
|-
| LTP || National Electric Vehicle Sweden AB (NEVS)
|-
| LTV || FAW [[../Toyota/VIN Codes|Toyota]] (Tianjin)
|-
| LTW || Zhejiang Dianka Automobile Technology Co. Ltd. (Enovate) 
|-
| LT1 || Yangzhou Tonghua Semi-Trailer Co., Ltd. (truck trailer)
|-
| LUC || [[../Honda/VIN Codes|Honda]] Automobile (China)
|-
| LUD || Dongfeng Nissan Diesel Motor Co Ltd.
|-
| LUG || Qiantu Motor
|-
| LUJ || Zhejiang Shanqi Tianying Vehicle Industry Co., Ltd. (motorcycles)
|-
| LUR || Chery Automobile, iCar
|-
| LUX || Dongfeng Yulon Motor Co. Ltd.
|-
| LUZ || Hozon Auto New Energy Automobile Co., Ltd. (Neta)
|-
| LVA || Foton Motor
|-
| LVB || Foton Motor truck
|-
| LVC || Foton Motor bus
|-
| LVF || Changhe Suzuki
|-
| LVG || GAC Toyota (Toyota, Leahead)
|-
| LVH || Dongfeng Honda (Honda, Ciimo)
|-
| LVM || Chery Commercial Vehicle
|-
| LVP || Dongfeng Sokon Motor Company (DFSK)
|-
| LVR || Changan Mazda
|-
| LVS || Changan [[../Ford/VIN Codes|Ford]] (Ford, Lincoln) &amp; Changan Ford Mazda &amp; Volvo S40 and S80L made by Changan Ford Mazda
|-
| LVT || Chery Automobile, Exeed, Jetour, Soueast
|-
| LVU || Chery Automobile, Jetour, Jaecoo
|-
| LVV || Chery Automobile, Omoda, Jaecoo
|-
| LVX || Landwind, JMC (discontinued in 2021)
|-
| LVX || Aiways Automobiles Company Ltd
|-
| LVY || Volvo Cars Daqing factory
|-
| LVZ || Dongfeng Sokon Motor Company (DFSK)
|-
| LV3 || Hengchi Automobile (Evergrande Group)
|-
| LV7 || Jinan Qingqi Motorcycle
|-
| LWB || Wuyang Honda Motorcycle (Guangzhou) Co., Ltd.
|-
| LWE || Yangtse Motor Group (bus)
|-
| LWG || Chongqing Huansong Industries (Group) Co., Ltd.
|-
| LWL || Qingling Isuzu
|-
| LWM || Chongqing Wonjan Motorcycle Co., Ltd.
|-
| LWV || GAC Fiat Chrysler Automobiles (Fiat, Jeep)
|-
| LWX || Shanghai Wanxiang Automobile Manufacturing Co., Ltd. (bus)
|-
| LW4 || Li Auto
|-
| LXA || Jiangmen Qipai Motorcycle Co., Ltd.
|-
| LXD || Ningbo Dongfang Lingyun Vehicle Made Co., Ltd. (motorcycle)
|-
| LXG || Xuzhou Construction Machinery Group Co., Ltd. (XCMG)
|-
| LXK || Shanghai Meitian Motorcycle Co., Ltd.
|-
| LXM || Xiamen Xiashing Motorcycle Co., Ltd. (SYM)
|-
| LXN || Link Tour
|-
| LXV || Beijing Borgward Automotive Co., Ltd.
|-
| LXW || JMC - Ford
|-
| LXY || Chongqing Shineray Motorcycle Co., Ltd.
|-
| LX6 || Jiangmen City Huari Group Co. Ltd. (motorcycle)
|-
| LX8 || Chongqing Xgjao (Xinganjue) Motorcycle Co Ltd.
|-
| LYB || Weichai (Yangzhou) Yaxing Automobile Co., Ltd.
|-
| LYD || Taizhou City Kaitong Motorcycle Co., Ltd. (motorcycle)
|-
| LYJ || Beijing ZhongdaYanjing Auto Co., Ltd. (bus)
|-
| LYM || Zhuzhou Jianshe Yamaha Motorcycle Co., Ltd.
|-
| LYS || Nanjing Vmoto Manufacturing Co. Ltd. (motorcycle)
|-
| LYU || Huansu (BAIC Motor &amp; Yinxiang Group)
|-
| LYV || Volvo Cars Chengdu factory &amp; Taizhou, Luqiao District factory
|-
| LY4 || Chongqing Yingang Science &amp; Technology Group Co., Ltd. (motorcycle)
|-
| LZE || Isuzu Guangzhou, China
|-
| LZF || SAIC Iveco Hongyan (-2021), SAIC Hongyan (2021-)
|-
| LZG || Shaanxi Automobile Group (Shacman)
|-
| LZK || Sinotruk (CNHTC) Huanghe bus
|-
| LZL || Zengcheng Haili Motorcycle Ltd.
|-
| LZM || MAN China
|-
| LZP || Zhongshan Guochi Motorcycle (Baotian)
|-
| LZS || Zongshen, Electra Meccanica Vehicles Corp. (Solo) made by Zongshen
|-
| LZU || Guangzhou Isuzu Bus
|-
| LZW || SAIC-GM-Wuling (Wuling, Baojun, Chevrolet [for export])
|-
| LZY || Yutong Bus Co., Ltd.
|-
| LZZ || Sinotruk (CNHTC) (Howo, Sitrak)
|-
| LZ0 || Shandong Wuzheng Group Co., Ltd.
|-
| LZ4 || Jiangsu Linzhi Shangyang Group Co Ltd.
|-
| LZ9/LZX || Raysince
|-
| L0N || Ezytrail (camper trailers)
|-
| L08 || Zhejiang Apollo Sports Technology Co., Ltd. (motorcycles)
|-
| L1K || Chongqing Hengtong Bus Co., Ltd.
|-
| L1N || XPeng Motors
|-
| L10 || Geely Emgrand
|-
| L2B || Jiangsu Baodiao Locomotive Co., Ltd. (motorcycles)
|-
| L2C || Chery Jaguar Land Rover
|-
| L3H || Shanxi Victory Automobile Manufacturing Co., Ltd.
|-
| L37 || Huzhou Daixi Zhenhua Technology Trade Co., Ltd. (motorcycles)
|-
| L4B || Xingyue Group (motorcycles)
|-
| L4F || Suzhou Eagle Electric Vehicle Manufacturing Co., Ltd.
|-
| L4H || Ningbo Longjia Motorcycle Co., Ltd.
|-
| L4S || Zhejiang Xingyue Vehicle Co Ltd. (motorcycles)
|-
| L4Y || Qingqi Group Ningbo Rhon Motorcycle / Ningbo Dalong Smooth Locomotive Industry Co., Ltd.
|-
| L5C || Zhejiang Kangdi Vehicles Co., Ltd. (motorcycles, ATVs)
|-
| L5E || Zoomlion Heavy Industry Science &amp; Technology Co., Ltd.
|-
| L5K || Zhejiang Yongkang Easy Vehicle
|-
| L5N || Zhejiang Taotao (ATV &amp; motorcycles)
|-
| L5R || Jiangsu Dafier Motorcycle Co., Ltd. (motorcycles)
|-
| L5Y || Taizhou Zhongneng Motorcycle Co. Ltd. (Znen)
|-
| L6F || Shandong Liangzi Power Co. Ltd.
|-
| L6J || Zhejiang Kayo Motor Co. Ltd. (ATV)
|-
| L6K || Shanghai Howhit Machinery Manufacture Co. Ltd.
|-
| L6T || Geely, Lynk &amp; Co, Zeekr
|-
| L66 || Zhuhai Granton Bus and Coach Co. Ltd. 
|-
| L82 || Baotian
|-
| L85 || Zhejiang Yongkang Huabao Electric Appliance
|-
| L8A || Jinhua Youngman Automobile Manufacturing Co., Ltd.
|-
| L8X || Zhejiang Summit Huawin Motorcycle
|-
| L8Y || Zhejiang Jonway Motorcycle Manufacturing Co., Ltd.
|-
| L9G || Zhuhai Guangtong Automobile Co., Ltd. (bus)
|-
| L9N || Zhejiang Taotao Vehicles Co., Ltd.
|-
| MAA || India Kawasaki Motors Pvt. Ltd.
|-
| MAB || Mahindra &amp; Mahindra
|-
| MAC || Mahindra &amp; Mahindra
|-
| MAH || Fiat India Automobiles Pvt. Ltd
|-
| MAJ || [[../Ford/VIN Codes|Ford]] India
|-
| MAK || [[../Honda/VIN Codes|Honda]] Cars India
|-
| MAL || Hyundai Motor India
|- 
| MAN || Eicher Polaris Multix
|- 
| MAT || Tata Motors, Rover CityRover
|-
| MA1 || Mahindra &amp; Mahindra
|-
| MA3 || Maruti Suzuki India (domestic &amp; export)
|-
| MA6 || GM India
|-
| MA7 || Hindustan Motors Ltd. &amp; Mitsubishi Motors &amp; Isuzu models made by Hindustan Motors
|-
| MA8 || Daewoo Motor India
|-
| MBF || Royal Enfield
|- 
| MBH || Suzuki (for export) &amp; Nissan Pixo made by Maruti Suzuki India Limited
|-
| MBJ || [[../Toyota/VIN Codes|Toyota]] Kirloskar Motor Pvt. Ltd.
|-
| MBK || MAN Trucks India Pvt. Ltd.
|-
| MBL || Hero MotoCorp
|-
| MBR || Mercedes-Benz India
|-
| MBU || Swaraj Vehicles Limited
|-
| MBV || Premier Automobiles Ltd.
|-
| MBX || Piaggio India (Piaggio Ape)
|-
| MBY || Asia Motor Works Ltd.
|-
| MB1 || Ashok Leyland
|-
| MB2 || Hyundai Motor India (SUV)
|-
| MB7 || Reva Electric Car Company/Mahindra Reva Electric Vehicles Pvt. Ltd.
|-
| MB8 || Suzuki Motorcycle India Limited
|-
| MCA || FCA India Automobiles Pvt. Ltd. (Fiat, Jeep)
|-
| MCB || GM India
|-
| MCD || Mahindra Two Wheelers
|-
| MCG || Atul Auto Ltd.
|-
| MCL || International Cars And Motors Ltd.
|-
| MC1 || Force Motors Ltd.
|-
| MC2 || Eicher Motors Ltd./Volvo Eicher Commercial Vehicles Ltd.
|-
| MC4 || Dilip Chhabria Design Pvt Ltd.
|-
| MC9/RE1 || Reva Electric Car Company (Reva G-Wiz)
|-
| MDE || Kinetic Engineering Limited
|-
| MDH || Nissan Motor India Pvt Ltd. (including Datsun)
|-
| MDT || Kerala Automobiles Limited
|-
| MD2 || Bajaj Auto Ltd. &amp; KTM and Husqvarna motorcycles built by Bajaj &amp; Indian-market Triumph motorcycles built by Bajaj
|-
| MD6 || TVS Motor Company
|-
| MD7 || LML Ltd including Genuine Scooter Company Stella
|-
| MD9 || Shuttle Cars India
|-
| MEC || Daimler India Commercial Vehicles (BharatBenz)
|-
| MEE || Renault India Private Limited
|-
| MEG || Harley-Davidson India
|-
| MER || Benelli India
|-
| MES || Mahindra Navistar
|-
| MET || Piaggio India (Vespa, Indian-market Aprilia)
|-
| MEX || Škoda Auto Volkswagen India Pvt. Ltd. 2015 on
|-
| ME1 || India Yamaha Motor Pvt. Ltd.
|-
| ME3 || Royal Enfield
|-
| ME4 || Honda Motorcycle and Scooter India
|-
| MYH || Ather Energy
|-
| MZB || Kia India Pvt. Ltd.
|-
| MZD || Classic Legends Private Limited – Jawa
|-
| MZZ || Citroen India (PCA Automobiles India Private Limited)
|-
| MZ7 || MG Motor India Pvt. Ltd.
|-
| M3G || Isuzu Motors India
|-
| M6F || UM Lohia Two Wheelers Private Limited
|-
| ME9/ || BUYMYEV TECHNOLOGY PVT. LTD. (Indibike)
|-
| MF3 || PT Hyundai Motor Manufacturing Indonesia
|-
| MHB || PT Nissan Motor Indonesia
|-
| MHD || PT Indomobil Suzuki International
|-
| MHF || PT [[../Toyota/VIN Codes|Toyota]] Motor Manufacturing Indonesia
|-
| MHK || PT Astra Daihatsu Motor (includes Toyotas made by Astra Daihatsu)
|-
| MHL || PT Mercedes-Benz Indonesia
|-
| MHR || [[../Honda/VIN Codes|Honda]] Indonesia (PT Honda Prospect Motor) (car)
|-
| MHY || PT Suzuki Indomobil Motor (car, MPV, van)
|-
| MH1 || PT Astra Honda Motor (motorcycle)
|-
| MH3 || PT Yamaha Indonesia Motor Mfg.
|-
| MH4 || PT Kawasaki Motor Indonesia
|-
| MH8 || PT Suzuki Indomobil Motor (motorcycle)
|-
| MJB || GM Indonesia
|-
| MKF || PT Sokonindo Automobile (DFSK)
|-
| MK2 || PT Mitsubishi Motors Krama Yudha Indonesia
|-
| MK3 || PT SGMW Motor Indonesia (Wuling)
|-
| MLB || Siam Yamaha Co Ltd.
|-
| MLC || Thai Suzuki Motor Co., Ltd. (motorcycle)
|-
| MLE || Thai Yamaha Motor Co., Ltd.
|-
| MLH || Thai [[../Honda/VIN Codes|Honda]] Manufacturing Co., Ltd. (motorcycle)
|-
| MLW || Sco Motor Co., Ltd. (motorcycle)
|-
| MLY || Harley-Davidson Thailand
|-
| ML0 || Ducati Motor (Thailand) Co., Ltd.
|-
| ML3 || Mitsubishi Motors, Dodge Colt 100 [Canada], [[w:Dodge Attitude#Third generation (A10; 2015)|Dodge Attitude]] [Mexico] made by Mitsubishi (Thailand)
|-
| ML5 || Kawasaki Motors Enterprise Co. Ltd. (Thailand)
|-
| MMA || Mitsubishi Motors (Thailand) &amp; Nissan Navara D27 made by Mitsubishi Motors (Thailand)
|-
| MMB || Mitsubishi Motors (Thailand)
|-
| MMC || Mitsubishi Motors (Thailand)
|-
| MMD || Mitsubishi Motors (Thailand)
|-
| MME || Mitsubishi Motors (Thailand)
|-
| MMF || BMW Manufacturing (Thailand) Co., Ltd.
|-
| MML || MG Thailand (SAIC-CP)
|-
| MMM || Chevrolet Thailand, Holden Colorado RC pickup
|-
| MMR || Subaru/Tan Chong Subaru Automotive (Thailand) Co. Ltd.
|-
| MMS || Suzuki Motor (Thailand) Co., Ltd. (passenger car)
|-
| MMT || Mitsubishi Motors (Thailand)
|-
| MMU || Holden Thailand (Colorado RG, Colorado 7, &amp; Trailblazer)
|-
| MM0, MM6, MM7, MM8 || Mazda Thailand (Ford-Mazda AutoAlliance Thailand plant)
|-
| MNA || [[../Ford/VIN Codes|Ford]] Thailand (Ford-Mazda AutoAlliance Thailand plant) for Australia/New Zealand export
|-
| MNB || [[../Ford/VIN Codes|Ford]] Thailand (Ford-Mazda AutoAlliance Thailand plant) for other right-hand drive markets
|-
| MNC || [[../Ford/VIN Codes|Ford]] Thailand (Ford-Mazda AutoAlliance Thailand plant) for left-hand drive markets
|-
| MNK || Hino Motors Manufacturing Thailand Co Ltd.
|-
| MNT || Nissan Motor (Thailand) Co., Ltd.
|-
| MNU || Great Wall Motor Manufacturing (Thailand) Co., Ltd.
|-
| MN3 || Eagle Vista [Canada] made by Mitsubishi (Thailand)
|-
| MPA || Isuzu Motors (Thailand) Co., Ltd. &amp; Holden Rodeo RA pickup made by Isuzu in Thailand
|-
| MPB || [[../Ford/VIN Codes|Ford]] Thailand (Ford Thailand Manufacturing plant)
|-
| MP1 || Isuzu Motors (Thailand) Co., Ltd.
|-
| MP2 || Mazda BT-50 pickup built by Isuzu Motors (Thailand) Co., Ltd.
|-
| MP3 || Plymouth Colt 100 [Canada] made by Mitsubishi (Thailand)
|-
| MP5 || Foton Motor Thailand
|-
| MRH || [[../Honda/VIN Codes|Honda]] Thailand (car)
|-
| MRT || Neta (Hozon Auto) made by Bangchan General Assembly Co., Ltd. 
|-
| MR0 || [[../Toyota/VIN Codes|Toyota]] Thailand (pickups &amp; Fortuner SUV)
|-
| MR1 || [[../Toyota/VIN Codes|Toyota]] Thailand
|-
| MR2 || [[../Toyota/VIN Codes|Toyota]] Thailand (Gateway plant) (passenger cars &amp; CUVs)
|-
| MR3 || [[../Toyota/VIN Codes|Toyota]] Thailand (Hilux Champ chassis cab)
|-
| MS0 || [[../SUPER SEVEN STARS MOTORS INDUSTRY CO.,LTD/VIN Codes|Super Seven Stars Motors]] Myanmar
|-
| MS1 || [[../SUPER SEVEN STARS AUTOMOTIVE CO.,LTD/VIN Codes|Super Seven Stars Automotive]] Myanmar
|-
| MS3 || Suzuki Myanmar Motor Co., Ltd.
|-
| MXB || Saryarka AvtoProm bus (Kazakhstan)
|-
| MXL || Yutong bus made by Qaz Tehna (Kazakhstan)
|-
| MXV || IMZ-Ural Ural Motorcycles (Kazakhstan)
|-
| MX3 || Hyundai Trans Auto (Kazakhstan)
|-
| NAA || Iran Khodro (Peugeot Iran)
|-
| NAC || Mammut (truck trailers)
|-
| NAD || Škoda
|-
| NAL || Maral Sanat Jarvid (truck trailers)
|-
| NAP || Pars Khodro
|-
| NAS || SAIPA
|-
| NC0 || Oghab Afshan (bus)
|-
| NC9/ || VIRA Diesel
|-
| ND9/345 || Oghab Afshan (bus)
|-
| NFB || Honda Atlas Cars Pakistan Ltd.
|-
| NG3 || Lucky Motor Corporation
|-
| NLA || Honda Turkiye A.S. cars
|-
| NLC || Askam Kamyon Imalat Ve Ticaret A.S.
|-
| NLE || Mercedes-Benz Türk A.S. Truck
|-
| NLF || Koluman Otomotiv Endustri A.S. (truck trailer)
|-
| NLH || [[../Hyundai/VIN Codes|Hyundai]] Assan Otomotiv car/SUV
|-
| NLJ || [[../Hyundai/VIN Codes|Hyundai]] Assan Otomotiv van
|-
| NLN || Karsan
|-
| NLR || Otokar
|-
| NLT || Temsa
|-
| NLZ || Tezeller
|-
| NL1 || TOGG
|-
| NL2 || HABAS/HBS (bus)
|-
| NMA || MAN Türkiye A.Ş.
|-
| NMB || Mercedes-Benz Türk A.S. Buses
|-
| NMC || BMC Otomotiv Sanayi ve Ticaret A.Ş.
|-
| NMH || Honda Anadolu motorcycle
|-
| NMS || Otoyol San. A.Ş.
|-
| NMT || [[../Toyota/VIN Codes|Toyota]] Motor Manufacturing Turkey
|-
| NM0 || Ford Otosan
|-
| NM1 || Oyak Renault Otomobil Fabrikaları A.Ş.
|-
| NM4 || Tofaş (Turk Otomobil Fabrikasi AS)
|-
| NNA || Anadolu Isuzu
|-
| NNN || Gépébus Oréos 4X (based on Otokar Vectio)
|-
| NNY || Yeksan (truck trailer)
|-
| NPM || Seyit Usta Treyler (truck trailer)
|-
| NPR || Oztreyler (truck trailer)
|-
| NPS || Nursan (truck trailer)
|-
| NP8|| ÖZGÜL TREYLER (truck trailer) 
|-
| NP9/002 || OKT Trailer (truck trailer) 
|-
| NP9/003 || Aksoylu Trailer (truck trailer) 
|-
| NP9/011 || Güleryüz (bus)
|-
| NP9/021 || Dogumak (truck trailer) 
|-
| NP9/022 || Alim (truck trailer) 
|-
| NP9/042 || Ali Rıza Usta (truck trailer) 
|-
| NP9/066 || Makinsan (truck trailer) 
|-
| NP9/093 || BRF Trailer (truck trailer) 
|-
| NP9/103 || Türkkar (bus)
|-
| NP9/106 || Çarsan Treyler (truck trailer) 
|-
| NP9/107 || Arbus Perfect (bus)
|-
| NP9/108 || Guven Makina (truck trailer) 
|-
| NP9/117 || Katmerciler (truck trailer) 
|-
| NP9/300 || TCV (bus) 
|-
| NP9/258 || Ceytrayler (truck trailer) 
|-
| NP9/306 || Cryocan (truck trailer) 
|-
| NRE || Bozankaya
|-
| NRX || Musoshi
|-
| NRY || Pilotcar Otomotiv
|-
| NR9/012 || Doğan Yıldız (truck trailer)
|-
| NR9/028 || Micansan (truck trailer)
|-
| NR9/029 || Yilteks (truck trailer)
|-
| NR9/034 || Akia (bus)
|-
| NR9/084 || Harsan (truck trailer)
|-
| NR9/257 || Vega Trailer (truck trailer)
|-
| NSA || SamAvto / SAZ (Uzbekistan)
|-
| NS2 || JV MAN Auto - Uzbekistan
|-
| NVA || Khazar (IKCO Dena made in Azerbaijan)
|- 
| PAB || Isuzu Philippines Corporation
|-
| PAD || Honda Cars Philippines
|-
| PE1 || Ford Motor Company Philippines
|-
| PE3 || Mazda Philippines made by Ford Motor Company Philippines
|-
| PFD || Hyundai Motor Group Innovation Center in Singapore (HMGICS)
|-
| PL1 || Proton, Malaysia
|-
| PL8 || Inokom-Hyundai
|-
| PLP || Subaru/Tan Chong Motor Assemblies, Malaysia
|-
| PLZ || Isuzu Malaysia
|-
| PMA || MAN Truck &amp; Bus Malaysia
|-
| PMH || Honda Malaysia (car)
|-
| PMK || Honda Boon Siew (motorcycle)
|-
| PML || Hicom 
|-
| PMN || Modenas
|-
| PMS || Suzuki Assemblers Malaysia (motorcycle)
|-
| PMV || Hong Leong Yamaha Motor Sdn. Bhd.
|-
| PMY || Hong Leong Yamaha Motor Sdn. Bhd.
|-
| PM1 || BMW &amp; Mini/Inokom
|-
| PM2 || Perodua
|-
| PM9/ || Bufori
|-
| PNA || Naza/Kia/Peugeot
|-
| PNA || Stellantis Gurun (Malaysia) Sdn. Bhd. (Peugeot)
|-
| PNS || SKSBUS Malaysia (bus)
|-
| PNS || TMSBUS Malaysia (bus)
|-
| PNV || Volvo Car Manufacturing Malaysia
|-
| PN1 || UMW Toyota Motor - Assembly Services Sdn. Bhd. (ASSB)
|-
| PN2 || UMW Toyota Motor - Assembly Services Sdn. Bhd. (ASSB)
|-
| PN8 || Nissan/Tan Chong Motor Assemblies, Malaysia
|-
| PPP || Suzuki
|-
| PPV || Volkswagen/HICOM Automotive Manufacturers (Malaysia)
|-
| PP1 || Mazda/Inokom
|-
| PP3 || Hyundai/Inokom
|-
| PRA || Sinotruk
|-
| PRH || Chery (by Chery Alado Holdings [joint venture] at Oriental Assemblers plant)
|-
| PRX || Kia/Inokom
|-
| PR8 || Ford
|-
| PRN || GAC Trumpchi made by Warisan Tan Chong Automotif Malaysia
|-
| PV3 || Ford made by RMA Automotive Cambodia
|-
| RA1 || Steyr Trucks International FZE, UAE
|-
| RA9/015 || Al-Assri Industries (Trailers), UAE
|-
| LES || Isuzu MPV made by Sanfu Motor Industrial Co., Ltd. (Trooper '87-'91) (Taiwan)
|-
| LFA || Ford Lio Ho Motor Co Ltd. old designation (Taiwan)
|-
| LM1 || Tai Ling Motor Co Ltd. old designation (Suzuki motorcycle made by Tai Ling) (Taiwan)
|-
| LM4 || Tai Ling Motor Co Ltd. old designation (Suzuki ATV made by Tai Ling) (Taiwan)
|-
| LM5 || Isuzu Truck (Light Duty) made by Sanfu Motor Industrial Co., Ltd. (Trooper '87-'88) (Taiwan)
|-
| LN1 || Tai Ling Motor Co Ltd. old designation (Suzuki motorcycle made by Tai Ling) (Taiwan)
|-
| LPR || Yamaha Motor Taiwan Co. Ltd. old designation (Taiwan)
|-
| RFB || Kwang Yang Motor Co., Ltd. (Kymco), Taiwan
|-
| RFC || Taiwan Golden Bee
|-
| RFD || Tai Ling Motor Co Ltd. new designation (Taiwan)
|-
| RFG || Sanyang Motor Co., Ltd. (SYM) Taiwan
|-
| RFL || Her Chee Industrial Co., Ltd. (Adly), Taiwan
|-
| RFT || CPI Motor Company, Taiwan
|-
| RFV || Motive Power Industry Co., Ltd. (PGO Scooters including Genuine Scooter Company models made by PGO) (Taiwan)
|-
| RF3 || Aeon Motor Co., Ltd., Taiwan
|-
| RF5 || Yulon Motor Co. Ltd., Taiwan (Luxgen)
|-
| RF8 || EVT Technology Co., Ltd (motorcycle)
|-
| RGS || Kawasaki made by Kymco (Taiwan)
|-
| RHA || Ford Lio Ho Motor Co Ltd. new designation (Taiwan)
|-
| RKJ || Prince Motors Taiwan
|-
| RKL || Kuozui Motors (Toyota) (Taiwan)
|-
| RKM || China Motor Corporation (Taiwan)
|-
| RKR || Yamaha Motor Taiwan Co. Ltd. new designation
|-
| RKT || Access Motor Co., Ltd. (Taiwan)
|-
| RK3 || E-Ton Power Tech Co., Ltd. (motorcycle) (Taiwan)
|-
| RK3 || Honda Taiwan
|-
| RK7 || Kawasaki ATV made by Tai Ling Motor Co Ltd (rebadged Suzuki ATV) new designation (Taiwan)
|-
| RLA || Vina Star Motors Corp. – Mitsubishi (Vietnam)
|-
| RLC || Yamaha Motor Vietnam Co. Ltd.
|-
| RLE || Isuzu Vietnam Co.
|-
| RLH || Honda Vietnam Co. Ltd.
|-
| RLL || VinFast SUV
|-
| RLM || Mercedes-Benz Vietnam
|-
| RLN || VinFast
|-
| RLV || Vietnam Precision Industrial CO., Ltd. (Can-Am DS 70 &amp; DS 90)
|-
| RL0 || Ford Vietnam
|-
| RL4 || Toyota Motor Vietnam
|-
| RP8 || Piaggio Vietnam Co. Ltd.
|-
| RUN || Sollets-Auto ST6 (Russia)
|-
| R1J || Jiayuan Power (Hong Kong) Ltd. (Electric Low-Speed Vehicles) (Hong Kong)
|-
| R1N || Niu Technologies Group Ltd. (Hong Kong)
|-
| R10 || ZAP (HK) Co. Ltd.
|-
| R19/003 || GMI (bus) (Hong Kong)
|-
| R2P || Evoke Electric Motorcycles (Hong Kong)
|-
| R3M || Mangosteen Technology Co., Ltd. (Hong Kong)
|-
| R3W || Hong Kong Runhorse Holding Co., Ltd. (Hong Kong)
|-
| R36 || HK Shansu Technology Co., Ltd. (Hong Kong)
|-
| R4N || Elyx Smart Technology Holdings (Hong Kong) Ltd.
|-
| R82 || Hangzhou Lantu Technology Co., Ltd. (Hong Kong)
|-
| SAA || Austin
|-
| SAB || Optare (1985-2020), Switch Mobility (2021-)
|-
| SAD || Daimler Company Limited (until April 1987)
|-
| SAD || Jaguar SUV (E-Pace, F-Pace, I-Pace)
|-
| SAF || ERF trucks
|-
| SAH || Honda made by Austin Rover Group
|-
| SAJ || Jaguar passenger car &amp; Daimler passenger car (after April 1987)
|-
| SAL || [[../Land Rover/VIN Codes|Land Rover]]
|-
| SAM || Morris
|-
| SAR || Rover &amp; MG Rover Group
|-
| SAT || Triumph car
|-
| SAX || Austin-Rover Group including Sterling Cars
|-
| SAY || Norton Motorcycles (UK) Ltd. (Donington Park/Donington Hall)
|-
| SAZ || Freight Rover
|-
| SA3 || Ginetta Cars
|-
| SA9/ || OX Global
|-
| SA9/A11 || Morgan Roadster (V6) (USA)
|-
| SA9/J00 || Morgan Aero 8 (USA)
|-
| SA9/004 || Morgan (4-wheel passenger cars)
|-
| SA9/005 || Panther
|-
| SA9/010 || Invicta S1
|-
| SA9/011 || Midas Cars
|-
| SA9/019 || TVR
|-
| SA9/022 || Triking Sports Cars
|-
| SA9/026 || Fleur de Lys
|-
| SA9/036 || Ginetta Cars
|-
| SA9/038 || DAX Cars
|-
| SA9/039 || Westfield Sportscars
|-
| SA9/048 || McLaren F1
|-
| SA9/050 || Marcos Engineering
|-
| SA9/062 || AC Cars (Brooklands Ace)
|-
| SA9/068 || Johnston Sweepers
|-
| SA9/073 || Tomita Auto UK (Tommykaira ZZ)
|-
| SA9/074 || Ascari 
|-
| SA9/088 || Spectre Angel 
|-
| SA9/105 || Mosler Europe Ltd.
|-
| SA9/113 || Noble
|-
| SA9/130 || MG Sport and Racing
|-
| SA9/141 || Wrightbus
|-
| SA9/202 || Morgan 3-Wheeler, Super 3
|-
| SA9/207 || Radical Sportscars
|-
| SA9/211 || BAC (Briggs Automotive Company Ltd.)
|-
| SA9/225 || Paneltex (truck trailer)
|-
| SA9/231 || Peel Engineering
|-
| SA9/337 || Ariel
|-
| SA9/341 || Zenos
|-
| SA9/438 || Charge Cars
|-
| SA9/458 || Gordon Murray Automotive
|-
| SA9/474 || Mellor (bus)
|-
| SA9/612 || Tiger Racing (kit car)
|-
| SA9/621 || AC Cars (Ace)
|-
| SBB || Leyland Vehicles
|-
| SBC || Iveco Ford Truck
|-
| SBF || Nugent (trailer)
|-
| SBJ || Leyland Bus
|-
| SBL || Leyland Motors &amp; Leyland DAF
|-
| SBM || McLaren
|-
| SBS || Scammell
|-
| SBU || United Trailers (truck trailer)
|-
| SBV || Kenworth &amp; Peterbilt [incomplete vehicle] made by Leyland Trucks
|-
| SBW || Weightlifter Bodies (truck trailer)
|-
| SB1 || [[../Toyota/VIN Codes|Toyota]] Motor Manufacturing UK
|-
| SCA || Rolls Royce passenger car
|-
| SCB || Bentley passenger car
|-
| SCC || Lotus Cars &amp; Opel Lotus Omega/Vauxhall Lotus Carlton
|-
| SCD || Reliant Motors
|-
| SCE || DeLorean Motor Cars N. Ireland (UK)
|-
| SCF || Aston Martin Lagonda Ltd. passenger car &amp; '21 DBX SUV
|-
| SCG || Triumph Engineering Co. Ltd. (original Triumph Motorcycle company)
|-
| SCK || Ifor Williams Trailers
|-
| SCM || Manitowoc Cranes - Grove
|-
| SCR || London Electric Vehicle Company &amp; London Taxi Company &amp; London Taxis International
|-
| SCV || Volvo Truck &amp; Bus Scotland
|-
| SC5 || Wrightbus (from ~2020)
|-
| SC6 || INEOS Automotive SUV
|-
| SDB || Talbot
|-
| SDC || SDC Trailers Ltd. (truck trailer)
|-
| SDF || Dodge Trucks – UK 1981–1984
|-
| SDG || Renault Trucks Industries 1985–1992
|-
| SDK || Caterham Cars
|-
| SDL || TVR
|-
| SDP || NAC MG UK &amp; MG Motor UK Ltd.
|-
| SDU || Utility (truck trailer)
|-
| SD7 || Aston Martin SUV
|-
| SD8 || Moke International Ltd.
|-
| SED || IBC Vehicles (General Motors Luton Plant) (Opel/Vauxhall, 1st gen. Holden Frontera, Isuzu Midi)
|-
| SEG || Dennis Eagle Ltd., including Renault Trucks Access and D Access
|-
| SEP || Don-Bur (truck trailer)
|-
| SEY || LDV Group Ltd.
|-
| SFA || [[../Ford/VIN Codes|Ford]] UK
|-
| SFD || Dennis UK / Alexander Dennis
|-
| SFE || Alexander Dennis UK
|-
| SFR || Fruehauf (truck trailer)
|-
| SFN || Foden Trucks &amp; Kenworth [truck] made by Foden Trucks
|-
| SFZ || Tesla Roadster made by Lotus
|-
| SGA || Avondale (caravans)
|-
| SGB || Bailey (caravans)
|-
| SGD || Swift Group Ltd. (caravans)
|-
| SGE || Elddis (caravans)
|-
| SGL || Lunar Caravans Ltd.
|-
| SG4 || Coachman Caravan Co. Ltd.
|-
| SG7 || ABI Caravans Ltd.
|-
| SHH || [[../Honda/VIN Codes|Honda]] UK passenger car
|-
| SHS || [[../Honda/VIN Codes|Honda]] UK SUV
|-
| SH2 || The Norton Motorcycle Co., Ltd. (TVS Motor Co. subsidiary)
|-
| SH7 || INEOS Automotive truck
|-
| SJA || Bentley SUV
|-
| SJB || Brian James Trailers Ltd
|-
| SJK || Nissan Motor Manufacturing UK - Infiniti
|-
| SJN || Nissan Motor Manufacturing UK - Nissan
|-
| SJ1 || Ree Automotive
|-
| SKA || Vauxhall
|-
| SKB || Kel-Berg Trailers &amp; Trucks
|-
| SKF || Bedford Vehicles
|-
| SKL || Anaig (UK) Technology Ltd
|-
| SKM || King Military Engineering Ltd.
|-
| SLA || Rolls Royce SUV
|-
| SLC || Thwaites Dumpers
|-
| SLG || McMurtry Automotive
|-
| SLN || Niftylift
|-
| SLP || JC Bamford Excavators Ltd.
|-
| SLV || Volvo bus
|-
| SMR || Montracon (truck trailer)
|-
| SMT || Triumph Motorcycles Ltd. (current Triumph Motorcycle company)
|-
| SMW || Cartwright (truck trailer)
|-
| SMX || Gray &amp; Adams (truck trailer)
|-
| SNE || Barkas (East Germany)
|-
| SNE || Wartburg (East Germany)
|-
| SNT || Trabant (East Germany)
|-
| SNZ || MZ (motorcycle) (Germany)
|-
| SPE || B-ON GmbH (Germany)
|-
| ST3 || Calabrese (truck trailer)
|-
| SUA || Autosan (bus)
|-
| SUB || Tramp Trail (trailer)
|-
| SUC || Wiola (trailer)
|-
| SUD || Wielton (truck trailers)
|-
| SUF || FSM/Fiat Auto Poland (Polski Fiat)
|-
| SUG || Mega Trailers (truck trailer) (Poland)
|-
| SUJ || Jelcz (Poland)
|-
| SUL || FSC (Poland)
|-
| SUM || Novatrail (truck trailers)
|-
| SUP || FSO/Daewoo-FSO (Poland)
|-
| SUU || Solaris Bus &amp; Coach (Poland)
|-
| SU9/AR1 || Emtech (truck trailer)
|-
| SU9/BU1 || BODEX (truck trailer)
|-
| SU9/DE2 || Demarco (truck trailer)
|-
| SU9/EB1 || Elbo (truck trailer)
|-
| SU9/EZ1 || Enerco (truck trailer)
|-
| SU9/NC5 || Zasta (truck trailer)
|-
| SU9/NJ1 || Janmil (truck trailer)
|-
| SU9/PL1 || Plandex (truck trailer)
|-
| SU9/PN1 || Solaris Bus &amp; Coach (Poland) - until 2004
|-
| SU9/RE1 || Redos (truck trailer)
|-
| SU9/RE2 || Gromex (trailer)
|-
| SU9/TR1 || Plavec (truck trailer)
|-
| SU9/YV1 || Pilea bus/ARP E-Vehicles (Poland)
|-
| SU9/ZC1 || Wolf (truck trailer)
|-
| SVH || ZASŁAW (truck trailer)
|-
| SVM || Inter Cars (truck trailer)
|-
| SVS || BODEX (truck trailer)
|-
| SV9/BC2 || BC-LDS (truck trailer)
|-
| SV9/DR1 || Dromech (truck trailer)
|-
| SV9/RN1 || Prod-Rent (truck trailer)
|-
| SWH || Temared (trailers)
|-
| SWR || Weekend Trailers (trailers)
|-
| SWV || TA-NO (Poland)
|-
| SWZ || Zremb (trailers)
|-
| SW9/BA1 || Solbus
|-
| SW9/WG3 || Grew / Opalenica (trailer)
|-
| SXE || Neptun Trailers
|-
| SXK || Konar (truck trailer)
|-
| SXM || MELEX Sp. z o.o.
|-
| SXY || Wecon (truck trailer)
|-
| SXX || Martz (trailer)
|-
| SX7 || Arthur Bus
|-
| SX9/GR0 || GRAS (truck trailer)
|-
| SX9/KT1 || AMZ - Kutno (bus)
|-
| SX9/PN1 || Polkon (truck trailer)
|-
| SX9/SP1 || SOMMER Polska (truck trailer)
|-
| SYB || Rydwan (trailer)
|-
| SYG || Gniotpol, GT Trailers Sp. z o. o. (truck trailer)
|-
| SY1 || Neso Bus (PAK-PCE Polski Autobus Wodorowy)
|-
| SY9/FR1 || Feber (truck trailer)
|-
| SY9/PF1 || KEMPF (truck trailer)
|-
| SZA || Scania Poland
|-
| SZC || Vectrix (motorcycle)
|-
| SZL || Boro Trailers
|-
| SZN || Przyczepy Głowacz (trailer) 
|-
| SZR || Niewiadów (trailer) 
|-
| SZ9/AE6 || Gewe (trailer) 
|-
| SZ9/BG1 || GALA Syriusz (trailer) 
|-
| SZ9/PW1 || PRO-WAM (truck trailer)
|-
| SZ9/TU1 || Ovibos (truck trailer)
|-
| S19/AM0 || AMO Plant (bus) (Latvia)
|-
| S19/EF1 || Electrify (minibus) (Latvia)
|-
| S19/MT0 || Mono-Transserviss (truck trailer) (Latvia)
|-
| TAW || NAW Nutzfahrzeuggesellschaft Arbon &amp; Wetzikon AG (Switzerland)
|-
| TBS || Boschung AG (Switzerland)
|-
| TCC || Micro Compact Car AG (smart 1998-1999) (Switzerland)
|-
| TDM || QUANTYA Swiss Electric Movement (Switzerland)
|-
| TEB || Bucher Municipal AG (includes Johnston Sweepers) (Switzerland)
|-
| TEM || Twike (SwissLEM AG) (Switzerland)
|-
| TFH || FHS Frech-Hoch AG (truck trailer) (Switzerland)
|-
| TH9/512 || Hess AG (bus, trolleybus) (Switzerland)
|-
| TJ5 || Vezeko (trailer) (Czech Republic)
|-
| TKP || Panav a.s.  (truck trailer) (Czech Republic)
|-
| TKX || Agados s.r.o. (trailer) (Czech Republic)
|-
| TKY || Metaco (truck trailer) (Czech Republic)
|-
| TK9/AH3 || Atmos Chrást s.r.o. (Czech Republic)
|-
| TK9/AP3 || Agados, spol. s.r.o. (trailer) (Czech Republic)
|-
| TK9/HP1 || Hipocar (truck trailer) (Czech Republic)
|-
| TK9/PP7 || Paragan Trucks (truck trailer) (Czech Republic)
|-
| TK9/SL5 || SOR Libchavy buses (Czech Republic)
|-
| TK9/SS5 || SVAN Chrudim (truck trailer) (Czech Republic)
|-
| TLJ || Jawa Moto (Czech Republic)
|-
| TMA || [[../Hyundai/VIN Codes|Hyundai]] Motor Manufacturing Czech
|-
| TMB || Škoda Auto|Škoda (Czech Republic)
|-
| TMC || [[../Hyundai/VIN Codes|Hyundai]] Motor Manufacturing Czech (SUV)
|-
| TMK || Karosa (Czech Republic)
|-
| TMP || Škoda trolleybuses (Czech Republic)
|-
| TMT || Tatra passenger car (Czech Republic)
|-
| TM9/CA2 || Oasa bus (Oprava a stavba automobilů) (Czech Republic)
|-
| TM9/SE3 || Škoda Transportation trolleybuses (Czech Republic)
|-
| TM9/SE4 || Škoda Transportation trolleybuses (Czech Republic)
|-
| TM9/TE6 || TEDOM bus (Czech Republic)
|-
| TNA || Avia/Daewoo Avia
|-
| TNE || TAZ
|-
| TNG || LIAZ (Liberecké Automobilové Závody)
|-
| TNT || Tatra trucks
|-
| TNU || Tatra trucks
|-
| TN9/EE7 || Ekova (bus) (Czech Republic)
|-
| TN9/VP5 || VPS (truck trailer)
|-
| TRA || Ikarus Bus
|-
| TRC || Csepel bus
|-
| TRE || Rákos bus
|-
| TRK || Credo bus/Kravtex (Hungary)
|-
| TRR || Rába Bus (Hungary)
|-
| TRU || Audi Hungary (TT/TTS, '12-'13 TT RS)
|-
| TSB || Ikarus Bus
|-
| TSC || VIN assigned by the National Transport Authority of Hungary
|-
| TSE || Ikarus Egyedi Autobuszgyar (EAG) (Hungary)
|-
| TSF || Alfabusz (Hungary)
|-
| TSM || Suzuki Hungary (Magyar Suzuki),&lt;br&gt; Fiat Sedici made by Suzuki, Subaru Justy G3X made by Suzuki, Suzuki Swace made by Toyota UK (TMUK)
|-
| TSY || Keeway Motorcycles (Hungary)
|-
| TS9/102 || Evopro Holding Zrt. (bus) (Hungary)
|-
| TS9/111 || NABI Autóbuszipari (bus) (Hungary)
|-
| TS9/130 || Enterprise Bus (Hungary)
|-
| TS9/131 || MJT bus (Hungary)
|-
| TS9/156 || Ikarus / ARC (Auto Rad Controlle Kft.) &amp;  Magyar Autóbuszgyártó Kft. bus (Hungary)
|-
| TS9/167 || Hungarian Bus Kft. (Hungary)
|-
| TS9/170 || Csaba Metál bus (Hungary)
|-
| TT9/117 || Ikarus Egyedi Autobusz Gyarto Kft. / Magyar Autóbuszgyártó Kft. / MABI bus (Hungary)
|-
| TT9/123 || Ikarus Global Zrt. (Hungary)
|-
| TWG || CaetanoBus (Portugal)
|-
| TW0 || CaetanoBus (Portugal)
|-
| TW1 || Toyota Caetano Portugal, S.A. (Toyota Coaster, Dyna, Optimo, Land Cruiser 70 Series)
|-
| TW2 || [[../Ford/VIN Codes|Ford]] Lusitana (Portugal)
|-
| TW4 || UMM (Portugal)
|-
| TW6 || Citroën (Portugal)
|-
| TW7 || Mini Moke made by British Leyland &amp; Austin Rover Portugal
|-
| TX5 || Mini Moke made by Cagiva (Moke Automobili)
|-
| TX9/046 || Riotrailer (truck trailer) (Portugal)
|-
| TYA || Mitsubishi Fuso Truck and Bus Corp. Portugal (right-hand drive)
|-
| TYB || Mitsubishi Fuso Truck and Bus Corp. Portugal (left-hand drive)
|-
| T3C || Lohr Backa Topola (truck trailer) (Serbia)
|-
| T49/BG7 || FAP (Serbia)
|-
| T49/BH8 || Megabus (bus) (Serbia)
|-
| T49/BM2 || Feniksbus (minibus) (Serbia)
|-
| T49/V16 || MAZ made by BIK (bus) (Serbia)
|-
| T7A || Ebusco (Netherlands)
|-
| UA1 || AUSA Center (Spain)
|-
| UA2 || Iveco Massif &amp; Campagnola made by Santana Motors in Spain
|-
| UA4 || Irizar e-mobility (Spain)
|-
| UCY || Silence Urban Ecomobility (Spain)
|-
| UD3 || Granalu truck trailers (Belgium)
|-
| UHE || Scanvogn (trailer) (Denmark)
|-
| UHL || Camp-let (recreational vehicle) (Denmark)
|-
| UH2 || Brenderup (trailer) (Denmark)
|-
| UH2 || De Forenede Trailerfabrikke (trailer) (Denmark)
|-
| UH9/DA3 || DAB - Danish Automobile Building (acquired by Scania) (Denmark)
|-
| UH9/EM1 || Egholm (Denmark)
|-
| UH9/FK1 || Dapa Trailer (truck trailer) (Denmark)
|-
| UH9/HF1 || HFR Trailer A/S (truck trailer) (Denmark)
|-
| UH9/HM1 || HMK Bilcon A/S (truck trailer) (Denmark)
|-
| UH9/NS1 || Nopa (truck trailer) (Denmark)
|-
| UH9/NT1 || Nordic Trailer (truck trailer) (Denmark)
|-
| UH9/VM2 || VM Tarm a/s (truck trailer) (Denmark)
|-
| UJG || Garia ApS - Club Car (Denmark)
|-
| UKR || Hero Camper (Denmark)
|-
| UMT || MTDK a/s (truck trailer) (Denmark)
|-
| UN1 || [[../Ford/VIN Codes|Ford]] Ireland
|-
| UN9/012 || Duffy Coachbodies (Ireland)
|-
| UN9/089 || Brian Noone Ltd. bus (Ireland)
|-
| UU1 || Dacia (Romania)
|-
| UU2 || Oltcit
|-
| UU3 || ARO
|-
| UU4 || Roman/Grivbuz
|-
| UU5 || Rocar
|-
| UU6 || Daewoo Romania
|-
| UU7 || Euro Bus Diamond
|-
| UU9 || Astra Bus
|-
| UVW || UMM (truck trailer)
|-
| UV9/AT1 || ATP Trucks, ATP Bus
|-
| UWR || Robus Reșița
|-
| UZT || UTB (Uzina de Tractoare Brașov)
|-
| U1A || Sanos (North Macedonia)
|-
| U1V || VDL Van Hool Macedonia (North Macedonia)
|-
| U5Y || Kia Motors Slovakia
|-
| U59/AS0 || ASKO (truck trailer)
|-
| U6A || Granus (bus) (Slovakia)
|-
| U6Y || Kia Motors Slovakia
|-
| U69/M11 ||  Mobility &amp; Innovation Production (bus) (Slovakia)
|-
| U69/NL1 || Novoplan (bus) (Slovakia)
|-
| U69/SB1 || SlovBus (bus) (Slovakia)
|-
| U69/TR8 || Troliga Bus (Slovakia)
|-
| VAG || Steyr-Daimler-Puch Puch G &amp; Steyr-Puch Pinzgauer
|-
| VAH || Hangler (truck trailer)
|-
| VAK || Kässbohrer Transport Technik
|-
| VAN || MAN Austria/Steyr-Daimler-Puch Steyr Trucks
|-
| VAV || Schwarzmüller
|-
| VAX || Schwingenschlogel (truck trailer)
|-
| VA0 || ÖAF, Gräf &amp; Stift
|-
| VA4 || KSR Group (motorcycle)
|-
| VA9/GS0 || Gsodam Fahrzeugbau (truck trailer)
|-
| VA9/RB1 || Rosenbauer International AG (truck)
|-
| VA9/ZT0 || Berger Fahrzeugtechnik (truck trailer)
|-
| VBF || Fit-Zel (trailer)
|-
| VBK || KTM 
|-
| VBK || Husqvarna Motorcycles &amp; Gas Gas under KTM ownership
|-
| VCF || Fisker Inc. (Fisker Ocean) made by Magna Steyr
|-
| VFA || Alpine (A310, A610, A110, A390), Renault Alpine GTA
|-
| VFG || Caravelair (caravans)
|-
| VFK || Fruehauf (truck trailers)
|-
| VFN || Trailor, General Trailers (truck trailers)
|-
| VF1 || Renault, Renault GTA '87-'90 (UK market Alpine GTA), Mobilize Duo, Eagle Medallion made by Renault,&lt;br&gt; Opel/Vauxhall Arena made by Renault, Mitsubishi ASX, Colt, Grandis, &amp; Eclipse Cross EV made by Renault
|-
| VF2 || Renault Trucks
|-
| VF3 || Peugeot
|-
| VF4 || Talbot
|-
| VF5 || Iveco Unic
|-
| VF6 || Renault Trucks including vans made by Renault S.A. &amp; Maxity truck made by Nissan Motor Ibérica S.A.
|-
| VF7 || Citroën
|-
| VF8 || Matra Automobiles (Talbot-Matra Murena, Rancho made by Matra, Renault Espace I/II/III, Avantime made by Matra)
|-
| VF9/024 || Legras Industries (truck trailer)
|-
| VF9/045 || Nardeau SAS (truck trailer)
|-
| VF9/049 || G. Magyar (truck trailer)
|-
| VF9/063 || Maisonneuve (truck trailer)
|-
| VF9/132 || Jean CHEREAU S.A.S. (truck trailer)
|-
| VF9/300 || EvoBus France
|-
| VF9/435 || Merceron (truck trailer)
|-
| VF9/519 || Hommell 
|-
| VF9/607 || Mathieu (sweeper)
|-
| VF9/673 || Venturi Automobiles
|-
| VF9/795 || [[../Bugatti/VIN Codes|Bugatti Automobiles S.A.S.]]
|-
| VF9/848 || G. Magyar (truck trailer)
|-
| VF9/880 || Bolloré Bluebus
|-
| VF9/938 || SAFRA (bus)
|-
| VGA || Peugeot Motocycles
|-
| VGT || ASCA (truck trailers)
|-
| VGU || Trouillet (truck trailers)
|-
| VGW || BSLT (truck trailers)
|-
| VGX || Coder (truck trailers)
|-
| VGY || Lohr (truck trailers)
|-
| VG5 || MBK (motorcycles) &amp; Yamaha Motor
|-
| VG6 || Renault Trucks &amp; Mack Trucks medium duty trucks made by Renault Trucks
|-
| VG7 || Renault Trucks
|-
| VG8 || Renault Trucks
|-
| VG9/019 || Naya (autonomous vehicle)
|-
| VG9/061 || Alstom-NTL Aptis (bus)
|-
| VHR || Robuste (truck trailer)
|-
| VHX || Manitowoc Cranes - Potain
|-
| VH1 || Benalu SAS (truck trailer)
|-
| VH8 || Microcar
|-
| VJR || Ligier
|-
| VJY || Gruau
|-
| VJ1 || Heuliez Bus
|-
| VJ2 || Mia Electric
|-
| VJ4 || Gruau
|-
| VKD || Cheval Liberté (horse trailer)
|-
| VK1 || SEG (truck trailer)
|-
| VK2 || Grandin Automobiles
|-
| VK8 || Venturi Automobiles
|-
| VLG || Aixam-Mega
|-
| VLU || Scania France
|-
| VL4 || Bluecar, Citroen E-Mehari
|-
| VMK || Renault Sport Spider
|-
| VMS || Automobiles Chatenet
|-
| VMT || SECMA
|-
| VMW || Gépébus Oréos 55
|-
| VM3 || Lamberet (trailer)
|-
| VM3 || Chereau (truck trailer)
|-
| VN1 || Renault SOVAB (France), Opel/Vauxhall Movano A made at SOVAB
|-
| VN4 || Voxan
|-
| VNB || Sherco Motorcycles SARL
|-
| VNE || Iveco Bus/Irisbus (France)
|-
| VNK || [[../Toyota/VIN Codes|Toyota]] Motor Manufacturing France &amp; '11-'13 Daihatsu Charade (XP90) made by TMMF
|-
| VNV || Nissan made in France by Renault
|-
| VPG || MPM Motors 
|-
| VPL || Nosmoke S.A.S
|-
| VP3 || G. Magyar (truck trailers)
|-
| VRW || Goupil
|-
| VR1 || DS Automobiles
|-
| VR3 || Peugeot (under Stellantis)
|-
| VR7 || Citroën (under Stellantis)
|-
| VSA || Mercedes-Benz Spain
|-
| VSC || Talbot
|-
| VSE || Santana Motors (Land Rover Series-based models) &amp; Suzuki SJ/Samurai, Jimny, &amp; Vitara made by Santana Motors in Spain
|-
| VSF || Santana Motors (Anibal/PS-10, 300/350)
|-
| VSK || Nissan Motor Iberica SA, Nissan passenger car/MPV/van/SUV/pickup &amp; Ford Maverick 1993–1999
|-
| VSR || Leciñena (truck trailers)
|-
| VSS || SEAT/Cupra
|-
| VSX || Opel Spain
|-
| VSY || Renault V.I. Spain (bus)
|-
| VS1 || Pegaso
|-
| VS5 || Renault Spain
|-
| VS6 || [[../Ford/VIN Codes|Ford]] Spain
|-
| VS7 || Citroën Spain
|-
| VS8 || Peugeot Spain
|-
| VS9/001 || Setra Seida (Spain)
|-
| VS9/011 || Advanced Design Tramontana
|-
| VS9/013 || Mirofret (truck trailer) (Spain)
|-
| VS9/016 || Irizar bus (Spain)
|-
| VS9/019 || Cobos Hermanos (truck trailer) (Spain)
|-
| VS9/031 || Carrocerias Ayats (Spain)
|-
| VS9/032 || Parcisa (truck trailer) (Spain)
|-
| VS9/044 || Beulas bus (Spain) (Spain)
|-
| VS9/047 || Indox (truck trailers) (Spain)
|-
| VS9/052 || Montull (truck trailer) (Spain)
|-
| VS9/057 || SOR Ibérica (truck trailers) (Spain)
|-
| VS9/072 || Mecanicas Silva (truck trailer) (Spain)
|-
| VS9/098 || Sunsundegui bus (Spain)
|-
| VS9/172 || EvoBus Iberica 
|-
| VS9/917 || Nogebus (Spain)
|-
| VTD || Montesa Honda (Honda Montesa motorcycle models)
|-
| VTH || Derbi (motorcycles)
|-
| VTL || Yamaha Spain (motorcycles)
|-
| VTM || Montesa Honda (Honda motorcycle models)
|-
| VTP || Rieju S.A. (motorcycles)
|-
| VTR || Gas Gas
|-
| VTT || Suzuki Spain (motorcycles)
|-
| VVC || SOR Ibérica (truck trailers)
|-
| VVG || Tisvol (truck trailers)
|-
| VV1 || Lecitrailer Group (truck trailers)
|-
| VV5 || Prim-Ball (truck trailers)
|-
| VV9/ || [[wikipedia:Tauro Sport Auto|TAURO]] Sport Auto Spain
|-
| VV9/010 || Castrosúa bus (Spain)
|-
| VV9/125 || Indetruck (truck trailers)
|-
| VV9/130 || Vectia Mobility bus (Spain)
|-
| VV9/130 || UNVI bus (Spain)
|-
| VV9/359|| Hispano-Suiza
|-
| VWA || Nissan Vehiculos Industriales SA, Nissan Commercial Vehicles
|-
| VWF || Guillén Group (truck trailers)
|-
| VWL || Indox (truck trailers)
|-
| VWV || Volkswagen Spain
|-
| VXE || Opel Automobile Gmbh/Vauxhall van
|-
| VXF || Fiat van (Fiat Scudo, Ulysse '22-)
|-
| VXK || Opel Automobile Gmbh/Vauxhall car/SUV
|-
| VXY || Neobus a.d. (Serbia)
|-
| VX1 || [[w:Zastava Automobiles|Zastava Automobiles]] / [[w:Yugo|Yugo]] (Yugoslavia/Serbia)
|-
| VYC || Lancia Ypsilon (4th gen.)
|-
| VYE || Jeep Compass (3rd gen. - EU market '26-)
|-
| VYF || Fiat Doblo '23- &amp; Fiat Topolino '23- &amp; Fiat Grande Panda '25-
|-
| VYJ || Ram 1200 '25- (sold in Mexico)
|-
| VYS || Renault &amp; Alpine made by Ampere (Renault 5 E-Tech, Renault 4 E-Tech, Alpine A290)
|-
| VZ2 || Avtomontaža (bus) (Slovenia)
|-
| V1Y || FAS Sanos bus (Yugoslavia/North Macedonia)
|-
| V2X || Ikarbus a.d. (Serbia)
|-
| V31 || Tvornica Autobusa Zagreb (TAZ) (Croatia)
|-
| V34 || Crobus bus (Croatia)
|-
| V39/AB8 || Rimac Automobili (Croatia)
|-
| V39/CB3 || Eurobus (Croatia)
|-
| V39/WB4 || Rasco (machinery) (Croatia)
|-
| V6A || Bestnet AS; Tiki trailers (Estonia)
|-
| V6B || Brentex-Trailer (Estonia)
|-
| V6T || Verge Motorcycles (Estonia)
|-
| V61 || Respo Trailers (Estonia)
|-
| WAC || Arge Audi Porsche (Audi/Porsche RS2 Avant)
|-
| WAF || Ackermann (truck trailer)
|-
| WAG || Neoplan
|-
| WAP || Alpina
|-
| WAU || Audi car
|-
| WA1 || Audi SUV
|-
| WBA || BMW car
|-
| WBC || Boom Trikes
|-
| WBJ || Bitter Cars
|-
| WBK || Böcker Maschinenwerke GmbH 
|-
| WBL || Blumhardt (truck trailers)
|-
| WBS || BMW M car
|-
| WBU || Bürstner (caravans)
|-
| WBX || BMW SUV
|-
| WBY || BMW i car
|-
| WB0 || Böckmann Fahrzeugwerke GmbH (trailers)
|-
| WB1 || BMW Motorrad 
|-
| WB2 || Blyss (trailer)
|-
| WB3 || BMW Motorrad Motorcycles made in India by TVS
|-
| WB4 || BMW Motorrad Motorscooters made in China by Loncin
|-
| WB5 || BMW i SUV
|-
| WCD || Freightliner Sprinter &quot;bus&quot; (van with more than 3 rows of seats) 2008–2019
|-
| WCM || Wilcox (truck trailer)
|-
| WDA || Mercedes-Benz incomplete vehicle (North America)
|-
| WDB || [[../Mercedes-Benz/VIN Codes|Mercedes-Benz]] &amp; Maybach
|-
| WDC || Mercedes-Benz SUV
|-
| WDD || [[../Mercedes-Benz/VIN Codes|Mercedes-Benz]] car
|-
| WDF || [[../Mercedes-Benz/VIN Codes|Mercedes-Benz]] van/pickup (French &amp; Spanish built models – Citan &amp; Vito &amp; X-Class)
|-
| WDP || Freightliner Sprinter incomplete vehicle 2005–2019
|-
| WDR || Freightliner Sprinter MPV (van with 2 or 3 rows of seats) 2005–2019
|-
| WDT || Dethleffs (caravans)
|-
| WDW || Dodge Sprinter &quot;bus&quot; (van with more than 3 rows of seats) 2008–2009
|-
| WDX || Dodge Sprinter incomplete vehicle 2005–2009
|-
| WDY || Freightliner Sprinter truck (cargo van with 1 row of seats) 2005–2019
|-
| WDZ || Mercedes-Benz &quot;bus&quot; (van with more than 3 rows of seats) (North America)
|-
| WD0 || Dodge Sprinter truck (cargo van with 1 row of seats) 2005–2009
|-
| WD1 || Freightliner Sprinter 2002 &amp; Sprinter (Dodge or Freightliner) 2003–2005 incomplete vehicle
|-
| WD2 || Freightliner Sprinter 2002 &amp; Sprinter (Dodge or Freightliner) 2003–2005 truck (cargo van with 1 row of seats)
|-
| WD3 || Mercedes-Benz truck (cargo van with 1 row of seats) (North America)
|-
| WD4 || Mercedes-Benz MPV (van with 2 or 3 rows of seats) (North America)
|-
| WD5 || Freightliner Sprinter 2002 &amp; Sprinter (Dodge or Freightliner) 2003–2005 MPV (van with 2 or 3 rows of seats)
|-
| WD6 || Freightliner Unimog truck
|-
| WD7 || Freightliner Unimog incomplete vehicle
|-
| WD8 || Dodge Sprinter MPV (van with 2 or 3 rows of seats) 2005–2009
|-
| WEB || Evobus GmbH (Mercedes-Benz buses)
|-
| WEG || Ablinger  (trailer)
|-
| WEL || e.GO Mobile AG
|-
| WFB || Feldbinder Spezialfahrzeugwerke GmbH
|-
| WFC || Fendt (caravans)
|-
| WFD || Fliegl Trailer
|-
| WFN || Tadano Faun GmbH
|-
| WF0 || [[../Ford/VIN Codes|Ford]] Germany
|-
| WF1 || Merkur
|-
| WGB || Göppel Bus GmbH
|-
| WG0 || Goldhofer AG (truck trailer)
|-
| WHB || Hobby - Wohnwagenwerk, Ing. H. Striewski GmbH (recreational vehicles)
|-
| WHD || Humbaur GmbH (truck trailer)
|-
| WHL || Hulco (trailer)
|-
| WHW || Hako GmbH
|-
| WHY || Hymer GmbH &amp; Co. KG (recreational vehicles)
|-
| WH7 || Hüfferman (truck trailer)
|-
| WJM || Iveco/Iveco Magirus
|-
| WJR || Irmscher
|-
| WKE || Krone (truck trailers)
|-
| WKK || Setra (Evobus GmbH; formerly Kässbohrer)
|-
| WKN || Knaus, Weinsberg (caravans)
|-
| WKV || Kässbohrer Fahrzeugwerke Gmbh (truck trailers)
|-
| WK0 || Kögel (truck trailers)
|-
| WLA || Langendorf semi-trailers
|-
| WLF || Liebherr (mobile crane)
|-
| WMA || MAN Truck &amp; Bus 
|-
| WME || smart (from 5/99)
|-
| WMG || Demag Cranes
|-
| WMM || Karl Müller GmbH &amp; Co. KG (truck trailers)
|-
| WMP || M &amp; V GmbH (truck trailers)
|-
| WMU || Hako GmbH (Multicar)
|-
| WMW || MINI car
|-
| WMX || Mercedes-AMG used for Mercedes-Benz SLS AMG &amp; Mercedes-AMG GT &amp; Mercedes-AMG One (not used in North America)
|-
| WMZ || MINI SUV
|-
| WNA || Next.e.GO Mobile SE
|-
| WP0 || Porsche car
|-
| WP1 || Porsche SUV
|-
| WRA || Renders (truck trailers)
|-
| WRJ || Riese &amp; Müller (bicycle)
|-
| WSE || STEMA Metalleichtbau GmbH (trailers)
|-
| WSJ || STERK Trailers (truck trailers)
|-
| WSK || Schmitz-Cargobull Gotha (truck trailers)
|-
| WSM || Schmitz-Cargobull (truck trailers)
|-
| WSP || Spitzer (truck trailers)
|-
| WSV || Aebi Schmidt Group
|-
| WS5 || StreetScooter
|-
| WS7 || Sono Motors
|-
| WTA || Tabbert (caravans)
|-
| WUA || Audi Sport GmbH (formerly quattro GmbH) car &lt;br&gt; (includes '04-'09 S4 Cabriolet &amp; '06 S4 25quattro Special Edition sedan &amp; '16-'18 S8 Plus &amp; non-North American mkt. Q7 V12 TDI)
|-
| WU1 || Audi Sport GmbH (formerly quattro GmbH) SUV
|-
| WVG || Volkswagen SUV &amp; Touran &amp; N. American mkt. ID Buzz '25
|-
| WVM || Arbeitsgemeinschaft VW-MAN
|-
| WVP || Viseon Bus
|-
| WVW || Volkswagen passenger car, Sharan, Golf Plus, Golf Sportsvan
|-
| WV1 || Volkswagen Commercial Vehicles (cargo van or 1st gen. Amarok)
|-
| WV2 || Volkswagen Commercial Vehicles (passenger van or minibus)
|-
| WV3 || Volkswagen Commercial Vehicles (incomplete vehicle: chassis cab/cutaway)&lt;br&gt; [includes Winnebago Rialta ('97-'04), Winnebago Vista ('02-'04), Itasca Sunstar ('02-'04)]
|-
| WV4 || Volkswagen Commercial Vehicles (2nd gen. Amarok &amp; T7 Transporter made by Ford)
|-
| WV5 || Volkswagen Commercial Vehicles (T7 Caravelle made by Ford)
|-
| WWA || Wachenhut (truck trailer)
|-
| WWC || WM Meyer (truck trailer)
|-
| WZ1 || Toyota Supra (Fifth generation for North America)
|-
| W0D || Obermaier (truck trailer)
|-
| W0L || Adam Opel AG/Vauxhall &amp; Holden
|-
| W0L || Holden Zafira &amp; Subaru Traviq made by GM Thailand
|-
| W0V || Opel Automobile Gmbh/Vauxhall &amp; Holden (since 2017)
|-
| W04 || Buick Regal &amp; Buick Cascada
|-
| W06 || Cadillac Catera
|-
| W08 || Saturn Astra
|-
| W09/A55 || Artega Automobile
|-
| W09/A71 || Apollo
|-
| W09/B09 || Bitter Cars
|-
| W09/B16 || Brabus
|-
| W09/B48 || Bultmann (trailer)
|-
| W09/B91 || Boerner (truck trailer)
|-
| W09/C09 || Carnehl Fahrzeugbau (truck trailer)
|-
| W09/D04 || DOLL (truck trailer)
|-
| W09/D05 || Drögmöller (bus)
|-
| W09/D17 || Dinkel (truck trailer)
|-
| W09/E04 || Eder (trailer)
|-
| W09/E27 || Esterer (truck trailer)
|-
| W09/E32 || ES-GE (truck trailer)
|-
| W09/E45 || Eurotank (truck trailer)
|-
| W09/F46 || FSN Fahrzeugbau (truck trailer)
|-
| W09/F57 || Twike
|-
| W09/G10 || GOFA (truck trailer)
|-
| W09/G64 || Gumpert
|-
| W09/H10 || Heitling Fahrzeugbau
|-
| W09/H21|| Dietrich Hisle GmbH (truck trailer)
|-
| W09/H46 || Hendricks (truck trailer)
|-
| W09/H49 || H&amp;W Nutzfahrzeugtechnik GmbH (truck trailer)
|-
| W09/J02 || Isdera
|-
| W09/K27 || Krupp
|-
| W09/K27 || Kotschenreuther (truck trailer)
|-
| W09/L05 || Liebherr
|-
| W09/L06 || LMC Caravan (recreational vehicles)
|-
| W09/M08 || MEILLER Kipper (truck trailer)
|-
| W09/M09 || Meierling (truck trailer)
|-
| W09/M29 || MAFA (truck trailer)
|-
| W09/M40 || Franz Mersch (trailer)
|-
| W09/M79 || MKF Matallbau (truck trailer)
|-
| W09/N22 || NFP-Eurotrailer (truck trailer)
|-
| W09/P13 || Pagenkopf (truck trailer)
|-
| W09/P72 || De Tomaso Automobili (Capricorn)
|-
| W09/R06 || RUF
|-
| W09/R14 || Rancke (truck trailer)
|-
| W09/R27 || Gebr. Recker Fahrzeugbau (truck trailer)
|-
| W09/R30 || Reisch (truck trailer)
|-
| W09/R38 || Rewaco
|-
| W09/SG0 || Sileo (bus)
|-
| W09/SG1 || SEKA (truck trailer)
|-
| W09/S24 || Sommer (truck trailer)
|-
| W09/S25 || Spermann (truck trailer)
|-
| W09/S27 || Schröder (truck trailer)
|-
| W09/W11 || Wilken (truck trailer)
|-
| W09/W14 || Weka (truck trailer)
|-
| W09/W16 || Wellmeyer (truck trailer)
|-
| W09/W20 || Kurt Willig GmbH &amp; Co. KG  (truck trailer)
|-
| W09/W29 || Wiese (truck trailer)
|-
| W09/W35 || Wecon GmbH  (truck trailer)
|-
| W09/W46 || WT-Metall (trailer)
|-
| W09/W59 || Wiesmann
|-
| W09/W70 || Wüllhorst (truck trailer)
|-
| W09/W86 || Web Trailer GmbH  (truck trailer)
|-
| W09/004 || ORTEN Fahrzeugbau (truck trailer)
|-
| W1A || smart
|-
| W1H || Freightliner Econic
|-
| W1K || Mercedes-Benz car
|-
| W1N || Mercedes-Benz SUV
|-
| W1T || Mercedes-Benz truck
|-
| W1V || Mercedes-Benz van
|-
| W1W || Mercedes-Benz MPV (van with 2 or 3 rows of seats) (North America)
|-
| W1X || Mercedes-Benz incomplete vehicle (North America)
|-
| W1Y || Mercedes-Benz truck (cargo van with 1 row of seats) (North America)
|-
| W1Z || Mercedes-Benz &quot;bus&quot; (van with more than 3 rows of seats) (North America)
|-
| W2W || Freightliner Sprinter MPV (van with 2 or 3 rows of seats)
|-
| W2X || Freightliner Sprinter incomplete vehicle
|-
| W2Y || Freightliner Sprinter truck (cargo van with 1 row of seats)
|-
| W2Z || Freightliner Sprinter &quot;bus&quot; (van with more than 3 rows of seats)
|-
| XDN || Mercedes Sprinter Classic made by GAZ (Russia)
|-
| XD2 || CTTM Cargoline (truck trailer) (Russia)
|-
| XEA || AmberAvto (Avtotor) (Russia)
|-
| XE2 || AMKAR Automaster (truck trailer) (Russia)
|-
| XF9/B24 || NK Trailers (truck trailer) (Greece)
|-
| XF9/D44 || Militsis (trailer) (Greece)
|-
| XF9/J03 || Christos Nezis (truck trailer) (Greece)
|-
| XF9/J63 || Kaoussis (truck trailer) (Greece)
|-
| XG3 || Petros Petropoulos Group - Ecoshift NOOS electric motorscooters (Greece)
|-
| XG4|| Mpitis (trailer) (Greece)
|-
| XG5 || Stavropoulos trailers (Greece)
|-
| XG6 || MGK Hellenic Motor motorcycles (Greece)
|-
| XG8 || Gorgolis SA motorcycles (Greece)
|-
| XG9/B01 || Sfakianakis bus Greece
|-
| XG9/H33 || Rappas Trailer (Greece)
|-
| XG9/H51 || Eurotrailer Tourlakopoulos (trailer) (Greece)
|-
| XG9/H92 || Diamantis N. &amp; Co. (trailer) (Greece)
|-
| XΗ9/B21 || Hellenic Vehicle Industry - ELVO bus Greece
|-
| XH9/H08 || Poseidonas Litsakis (trailer) (Greece)
|-
| XH9/H34 || Flexi-Wheels (trailer) (Greece)
|-
| XJY || Bonum (truck trailer) (Russia)
|-
| XJ4 || PKTS (PK Transportnye Sistemy) bus (Russia)
|-
| XKM || Volgabus (Russia)
|-
| XLA || DAF Bus International
|-
| XLB || Volvo Car B.V./NedCar B.V. (Volvo Cars)
|-
| XLC || [[../Ford/VIN Codes|Ford]] Netherlands
|-
| XLD || Pacton Trailers B.V.
|-
| XLE || Scania Netherlands
|-
| XLH || Hapert (trailer)
|-
| XLJ || Anssems (trailer)
|-
| XLK || Burg Trailer Service BV (truck trailer)
|-
| XLR || DAF Trucks &amp; Leyland DAF
|-
| XLU || Henra (trailer)
|-
| XLV || DAF Bus
|-
| XLW || Terberg Benschop BV
|-
| XL3 || Ebusco
|-
| XL4 ||Lightyear
|-
| XL9/001 || ESVE BV (truck trailers)
|-
| XL9/002 || Jumbo Groenewegen (truck trailers)
|-
| XL9/003 || Autobusfabriek Bova BV
|-
| XL9/004 || G.S. Meppel (truck trailers)
|-
| XL9/007|| Broshuis BV (truck trailer)
|-
| XL9/010|| Ginaf Trucks
|-
| XL9/014 || Contar (truck trailer)
|-
| XL9/017 || Van Eck (truck trailer)
|-
| XL9/021 || Donkervoort Cars
|-
| XL9/033 || Wijer (trailer)
|-
| XL9/039 || Talson (truck trailer)
|-
| XL9/042 || Den Oudsten Bussen
|-
| XL9/052 || Witteveen (trailer)
|-
| XL9/055 || Fripaan (truck trailer)
|-
| XL9/067 || HTF (truck trailer)
|-
| XL9/068 || Vogelzang (truck trailer)
|-
| XL9/069 || Kraker (truck trailer)
|-
| XL9/070 || Veldhuizen (truck trailers)
|-
| XL9/073 || Zwalve (truck trailers)
|-
| XL9/074 || Draco (truck trailers)
|-
| XL9/081 || EBO van Weel (truck trailers)
|-
| XL9/084 || Vocol (truck trailers)
|-
| XL9/089 || Meijvo (trailers)
|-
| XL9/092 || Bulthuis (truck trailers)
|-
| XL9/103 || D-TEC (truck trailers)
|-
| XL9/109|| Groenewold Carrosseriefabriek B.V. (car transporter)
|-
| XL9/150 || Univan (truck trailer)
|-
| XL9/251 || Spierings Mobile Cranes
|-
| XL9/320 || VDL Bova bus
|-
| XL9/348 || HOKA (trailer)
|-
| XL9/355 || Berdex (truck trailer)
|-
| XL9/363 || Spyker
|-
| XL9/423 || Tijhof (trailer)
|-
| XL9/461 || BK Market Trailers (trailer)
|-
| XL9/495 || BE-Combi (truck trailer)
|-
| XL9/508 || Talson (truck trailer)
|-
| XL9/527 || GINAF
|-
| XL9/530 || Ebusco
|-
| XL9/611 || Zocon (trailer)
|-
| XMC || NedCar B.V. Mitsubishi Motors (LHD)
|-
| XMD || NedCar B.V. Mitsubishi Motors (RHD)
|-
| XMG || VDL Bus International
|-
| XMR || Nooteboom Trailers 
|-
| XM4 || RAVO Holding B.V. (sweeper)
|-
| XNB || NedCar B.V. Mitsubishi Motors made by Pininfarina (Colt CZC convertible - RHD)
|-
| XNC || NedCar B.V. Mitsubishi Motors made by Pininfarina (Colt CZC convertible - LHD)
|-
| XNJ || Broshuis (truck trailer)
|-
| XNL || VDL Bus &amp; Coach
|-
| XNT || Pacton Trailers B.V. (truck trailer)
|-
| XN1 || Kraker Trailers Axel B.V. (truck trailer)
|-
| XPN || Knapen Trailers
|-
| XPP || Atec Trailers
|-
| XP7 || Tesla Europe (based in the Netherlands) (Gigafactory Berlin-Brandenburg)
|-
| XRP || Proline (trailer)
|-
| XRY || D-TEC (truck trailer)
|-
| XR7 || Qarry
|-
| XTA || Lada / AvtoVAZ (Russia)
|-
| XTB || Moskvitch / AZLK (Russia)
|-
| XTC || KAMAZ (Russia)
|-
| XTD || LuAZ (Ukraine)
|-
| XTE || ZAZ (Ukraine)
|-
| XTF || GolAZ (Russia) 
|-
| XTH || GAZ (Russia)
|-
| XTJ || Lada Oka made by SeAZ (Russia)
|-
| XTK || IzhAvto (Russia)
|-
| XTM || MAZ (Belarus); used until 1997
|-
| XTP || Ural (Russia)
|-
| XTS || ChMZAP (truck trailer)
|-
| XTT || UAZ / Sollers (Russia)
|-
| XTU || Trolza, previously ZiU (Russia)
|-
| XTW || LAZ (Ukraine)
|-
| XTY || LiAZ (Russia)
|-
| XTZ || ZiL (Russia)
|-
| XUF || General Motors Russia
|-
| XUS || Nizhegorodets (minibus) (Russia)
|-
| XUU || Avtotor (Russia, Chevrolet Korea SKD, Kaiyi Auto)
|-
| XUV || Avtotor (DFSK, SWM)
|-
| XUZ || InterPipeVAN (truck trailer)
|-
| XU6 || Avtodom (minibus) (Russia)
|-
| XVG || MARZ (bus) (Russia)
|-
| XVU || Start (truck trailer)
|-
| XWB || UZ-Daewoo/GM Uzbekistan/Ravon/UzAuto Motors (Uzbekistan)
|-
| XWD || Avtotor (Russia, BAIC SKD)
|-
| XWE || Avtotor (Russia, Hyundai-Kia SKD)
|-
| XWF || Avtotor (Russia, Chevrolet Tahoe/Opel/Cadillac/Hummer SKD)
|-
| XWK || Kia assembled in Russia by IzhAvto 
|-
| XW7 || Toyota Motor Manufacturing Russia
|-
| XW8 || Volkswagen Group Russia (VW, Skoda)
|-
| XX3 || Ujet Manufacturing (Luxembourg)
|-
| XZB || SIMAZ (bus) (Russia)
|-
| XZE || Specpricep (truck trailer)
|-
| XZG || Great Wall Motor (Haval Motor Rus)
|-
| XZP || Gut Trailer (truck trailer)
|-
| XZT || FoxBus (minibus) (Russia)
|-
| X1D || RAF (Rīgas Autobusu Fabrika) (Latvia)
|-
| X1E || KAvZ (Russia)
|-
| X1F || NefAZ (Russia)
|-
| X1M || PAZ (Russia)
|-
| X1P || Ural (Russia)
|-
| X2L || Fox Trailer (truck trailer) (Russia)
|-
| X21 || Diesel-S (truck trailer) (Russia)
|-
| X4K || Volgabus (Volzhanin) (Russia)
|-
| X4T || Sommer (truck trailer) (Russia)
|-
| X4X || Avtotor (Russia, BMW SKD)
|-
| X5A || UralSpetzTrans (trailer) (Russia)
|-
| X6D || VIS-AVTO (Russia)
|-
| X6S || TZA (truck trailer) (Russia)
|-
| X7L || Renault AvtoFramos (1998-2014), Renault Russia (2014-2022), Moskvitch (2022-) (Russia)
|-
| X7M || [[../Hyundai/VIN Codes|Hyundai]] &amp; Vortex (rebadged Chery) made by TagAZ (Russia)
|-
| X89/AD4 || ВМЗ (VMZ) bus
|-
| X89/BF8 || Rosvan bus
|-
| X89/CU2 || EvoBus Russland (bus)
|-
| X89/DJ2 || VMK (bus)
|-
| X89/EY4 || Brabill (minibus)
|-
| X89/FF6 || Lotos (bus)
|-
| X89/FY1 || Sherp 
|-
| X8J || IMZ-Ural Ural Motorcycles
|-
| X8U || Scania Russia
|-
| X9F || Ford Motor Company ZAO
|-
| X9L || GM-AvtoVAZ  (Chevrolet Niva &amp; Viva)
|-
| X9N || Samoltor (minibus)
|-
| X9P || Volvo Vostok ZAO (Volvo Trucks)
|-
| X9W || Brilliance, Lifan made by Derways
|-
| X9X || Great Wall Motors 
|-
| X96 || GAZ
|-
| X99/000 || Marussia
|-
| X90 || GRAZ (truck trailer)
|-
| X0T || Tonar (truck trailer)
|-
| YAF || Faymonville (special transport trailers)
|-
| YAG || Syma aanhangwagenbouw BV (trailers)
|-
| YAM || MAX Trailer (truck trailers)
|-
| YAR || Toyota Motor Europe (based in Belgium) used for Toyota ProAce, Toyota ProAce City and Toyota ProAce Max made by PSA/Stellantis
|-
| YA2 || Atlas Copco Group
|-
| YA5 || Renders (truck trailers)
|-
| YA9/ || Lambrecht Constructie NV (truck trailers)
|-
| YA9/111 || OVA (truck trailer)
|-
| YA9/121 || Atcomex (truck trailer)
|-
| YA9/128 || EOS (bus)
|-
| YA9/139 || ATM Maaseik (truck trailer)
|-
| YA9/168 || Forthomme s.a. (truck trailer)
|-
| YA9/169 || Automobiles Gillet
|-
| YA9/180 || EOS (bus)
|-
| YA9/191 || Stokota (truck trailers)
|-
| YA9/195 || Denolf &amp; Depla (minibus)
|-
| YBC || Toyota Supra (Fifth generation for Europe)
|-
| YBD || Addax Motors
|-
| YBW || Volkswagen Belgium
|-
| YB1 || Volvo Trucks Belgium (truck)
|-
| YB2 || Volvo Trucks Belgium (bus chassis)
|-
| YB3 || Volvo Trucks Belgium (incomplete vehicle)
|-
| YB4 || LAG Trailers N.V. (truck trailer)
|-
| YB6 || Jonckheere (VDL Belgium)
|-
| YCM || Mazda Motor Logistics Europe (based in Belgium) used for European-market Mazda 121 made by Ford in UK
|-
| YC1 || Honda Belgium NV (motorcycle)
|-
| YC3 || Eduard Trailers
|-
| YD3 || Chateau Caravans (Belgium)
|-
| YE1 || Van Hool (trailers) (Belgium)
|-
| YE2 || Van Hool (buses) (Belgium)
|-
| YE6 || STAS (truck trailer)
|-
| YE7 || Turbo's Hoet (truck trailer)
|-
| YF1 || Närko (truck trailer) (Finland)
|-
| YF3 || NTM (truck trailer) (Finland)
|-
| YF9/050 || JYKI (truck trailer) (Finland)
|-
| YGU || JJ-Trailer (trailer) (Finland)
|-
|YG6
|Majava Group Oy; Majava trailers (Finland)
|-
| YH1 || Solifer (caravans)
|-
| YH2 || BRP Finland (Lynx snowmobiles)
|-
| YH4 || Fisker Automotive (Fisker Karma) built by Valmet Automotive
|-
| YK1 || Saab-Valmet Finland
|-
| YK2, YK7 || Sisu Auto
|-
| YK9/003 || Kabus (bus)
|-
| YK9/008 || Lahden Autokori (-2013), SOE Busproduction Finland (2014-2024) (bus)
|-
| YK9/016 || Linkker (bus)
|-
| YSC || Cadillac BLS (made by Saab)
|-
| YSM || Polestar cars 
|-
| YSP || Volta Trucks AB
|-
| YSR || Polestar SUV
|-
| YS2 || Scania commercial vehicles (Södertälje factory) 
|-
| YS3 || Saab cars
|-
| YS4 || Scania buses and bus chassis until 2002 (Katrineholm factory)
|-
| YS5 || OmniNova (minibus)
|-
| YS7 || Solifer (recreational vehicles)
|-
| YS9/KV1 || Backaryd (minibus)
|-
| YTN || Saab made by NEVS
|-
| YT7 || Kabe (recreational vehicles)
|-
| YT9/007 || Koenigsegg
|-
| YT9/034 || Carvia
|-
| YU1 || Fogelsta, Brenderup Group (trailer)
|-
| YU7 || Husaberg (motorcycles)
|-
| YVV || WiMa 442 EV
|-
| YV1 || [[../Volvo/VIN Codes|Volvo]] cars
|-
| YV2 || [[../Volvo/VIN Codes|Volvo]] trucks
|-
| YV3 || [[../Volvo/VIN Codes|Volvo]] buses and bus chassis
|-
| YV4 || [[../Volvo/VIN Codes|Volvo]] SUV
|-
| YV5 || [[../Volvo/VIN Codes|Volvo Trucks]] incomplete vehicle
|-
| YYB || Tysse (trailer) (Norway)
|-
| YYC || Think Nordic (Norway)
|-
| YY9/017 || Skala Fabrikk (truck trailer) (Norway)
|-
| Y29/005 || Buddy Electric (Norway)
|-
| Y3D || MTM (truck trailer) (Belarus)
|-
| Y3F || Lida Buses Neman (Belarus)
|-
| Y3J || Belkommunmash (Belarus)
|-
| Y3K || Neman Bus (Belarus)
|-
| Y3M || MAZ (Belarus)
|-
| Y3W || VFV built by Unison (Belarus)
|-
| Y39/047 || Altant-M (minibus) (Belarus)
|-
| Y39/051 || Bus-Master (minibus) (Belarus)
|-
| Y39/052 || Aktriya (minibus) (Belarus)
|-
| Y39/072 || Klassikbus (minibus) (Belarus)
|-
| Y39/074 || Alterra (minibus) (Belarus)
|-
| Y39/135 || EuroDjet (minibus) (Belarus)
|-
| Y39/240 || Alizana (minibus) (Belarus)
|-
| Y39/241 || RSBUS (minibus) (Belarus)
|-
| Y39/323 || KF-AVTO (minibus) (Belarus)
|-
| Y4F || [[../Ford/VIN Codes|Ford]] Belarus
|-
| Y4K || Geely / BelGee (Belarus)
|-
| Y6B || Iveco (Ukraine)
|-
| Y6D || ZAZ / AvtoZAZ, Chevrolet Lanos made by ZAZ (Ukraine)
|-
| Y6E || LAZ (Ukraine)
|-
| Y6J || Bogdan group (Ukraine)
|-
| Y6L || Bogdan group including buses, Lada, &amp; Hyundai made by Bogdan (Ukraine)
|-
| Y6U || Škoda Auto made by Eurocar (Ukraine)
|-
| Y6W || PGFM (trailer) (Ukraine)
|-
| Y6Y || LEV (trailer) (Ukraine)
|-
| Y69/B19 || Stryi Avto (bus) (Ukraine)
|-
| Y69/B98 || VESTT (truck trailer) (Ukraine)
|-
| Y69/C49 || TAD (truck trailer) (Ukraine)
|-
| Y69/D75 || Barrel Dash (truck trailer) (Ukraine)
|-
| Y7A || KrAZ trucks (Ukraine)
|-
| Y7B || Bogdan group (Ukraine)
|-
| Y7C || Great Wall Motors, Geely made by KrASZ (Ukraine)
|-
| Y7D || GAZ made by KrymAvtoGAZ (Ukraine)
|-
| Y7F || Boryspil Bus Factory (BAZ) (Ukraine)
|-
| Y7S || Korida-Tech (trailer) (Ukraine)
|-
| Y7W || Geely made by KrASZ (Ukraine)
|-
| Y7X || ChRZ - Ruta (minibus) (Ukraine)
|-
| Y79/A23 || OdAZ (truck trailer) (Ukraine)
|-
| Y79/B21 || Everlast (truck trailer) (Ukraine)
|-
| Y79/B65 || Avtoban (trailer) (Ukraine)
|-
| Y8A || LAZ (Ukraine)
|-
| Y8H || UNV Leader (trailer) (Ukraine)
|-
| Y8S || Alekseevka Ximmash (truck trailer) 
|-
| Y8X || GAZ Gazelle made by KrASZ (Ukraine)
|-
| Y89/A98 || VARZ (trailer) (Ukraine)
|-
| Y89/B75 || Knott (trailer) (Ukraine)
|-
| Y89/C65 || Electron (Ukraine)
|-
| Y9A || PAVAM (trailer) (Ukraine)
|-
| Y9H || LAZ (Ukraine)
|-
| Y9M || AMS (trailer) (Ukraine)
|-
| Y9T || Dnipro (trailer) (Ukraine)
|-
| Y9W || Pragmatec (trailer) (Ukraine)
|-
| Y9Z || Lada, Renault made in Ukraine
|-
| Y99/B32 || Santey (trailer) (Ukraine)
|-
| Y99/E21 || Zmiev-Trans (truck trailer) (Ukraine)
|-
| Y99/C79 || Electron (bus) (Ukraine)
|-
| ZAA || Autobianchi
|-
| ZAA || Alfa Romeo Junior 2024-
|-
| ZAC || Jeep, Dodge Hornet
|-
| ZAH || Rolfo SpA (car transporter)
|-
| ZAJ || Trigano SpA; Roller Team recreational vehicles
|-
| ZAM || [[../Maserati/VIN Codes|Maserati]]
|-
| ZAP || Piaggio/Vespa/Gilera
|-
| ZAR || Alfa Romeo car
|-
| ZAS || Alfa Romeo Alfasud &amp; Sprint through 1989
|-
| ZAS || Alfa Romeo SUV 2018-
|-
| ZAX || Zorzi (truck trailer)
|-
| ZA4 || Omar (truck trailer)
|-
| ZA9/A12 || [[../Lamborghini/VIN Codes|Lamborghini]] through mid-2003 (including LM002)
|-
| ZA9/A17 || Carrozzeria Luigi Dalla Via (bus)
|-
| ZA9/A18 || De Simon (bus)
|-
| ZA9/A33 || Bucher Schörling Italia (sweeper)
|-
| ZA9/A47 || Silver Car (truck trailer)
|-
| ZA9/B09 || Mauri Bus System
|-
| ZA9/B34 || Mistrall Siloveicoli (truck trailer)
|-
| ZA9/B45 || Bolgan (truck trailer)
|-
| ZA9/B49 || OMSP Macola (truck trailer)
|-
| ZA9/B95 || Carrozzeria Autodromo Modena (bus)
|-
| ZA9/C38 || Dulevo (sweeper)
|-
| ZA9/D38 || Cizeta Automobili SRL
|-
| ZA9/D39 || [[../Bugatti/VIN Codes|Bugatti Automobili S.p.A]]
|-
| ZA9/D50 || Italdesign Giugiaro
|-
| ZA9/E15 || Tecnobus Industries S.r.l.
|-
| ZA9/E73 || Sitcar (bus)
|-
| ZA9/E88 || Cacciamali (bus)
|-
| ZA9/F16 || OMT (truck trailer)
|-
| ZA9/F21 || FGM (truck trailer)
|-
| ZA9/F48 || Rampini Carlo S.p.A. (bus)
|-
| ZA9/F76 || Pagani Automobili S.p.A.
|-
| ZA9/G97 || EPT Horus (bus)
|-
| ZA9/H02 || O.ME.P.S. (truck trailer)
|-
| ZA9/H44|| Green-technik by Green Produzione s.r.l. (machine trailer)
|-
| ZA9/J21 || VRV (truck trailer)
|-
| ZA9/J93 || Barbi (bus)
|-
| ZA9/K98 || Esagono Energia S.r.l.
|-
| ZA9/M09 || Italdesign Automobili Speciali
|-
| ZA9/M27 || Dallara Stradale
|-
| ZA9/M91 || Automobili Pininfarina
|-
| ZA9/180 || De Simon (bus)
|-
| ZA0 || Acerbi (truck trailer)
|-
| ZBA || Piacenza (truck trailer)
|-
| ZBB || Bertone
|-
| ZBD || InBus
|-
| ZBN || Benelli
|-
| ZBW || Rayton-Fissore Magnum
|-
| ZB3 || Cardi (truck trailer)
|-
| ZCB || E. Bartoletti SpA (truck trailer)
|-
| ZCF || Iveco / Irisbus (Italy)
|-
| ZCG || Cagiva SpA / MV Agusta
|-
| ZCG || Husqvarna Motorcycles Under MV Agusta ownership
|-
| ZCM || BredaMenarinibus / Menarinibus / IIA (Industria Italiana Autobus)
|-
| ZCN || Astra Veicoli Industriali S.p.A.
|-
| ZCV || Vibreti (truck trailer)
|-
| ZCZ || BredaBus
|-
| ZC1 || AnsaldoBreda S.p.A.
|-
| ZC2 || Chrysler TC by Maserati
|-
| ZDC || Honda Italia Industriale SpA
|-
| ZDF || [[../Ferrari/VIN Codes|Ferrari]] Dino
|-
| ZDJ || ACM Biagini
|-
| ZDM || Ducati Motor Holdings SpA
|-
| ZDT || De Tomaso Modena SpA
|-
| ZDY || Cacciamali
|-
| ZD0 || Yamaha Motor Italia SpA &amp; Belgarda SpA
|-
| ZD3 || Beta Motor
|-
| ZD4 || Aprilia
|-
| ZD5 || Casalini
|-
| ZEB || Ellebi (trailer)
|-
| ZEH || Trigano SpA (former SEA Group); McLouis &amp; Mobilvetta recreational vehicles
|-
| ZES || Bimota
|-
| ZEX || TM Racing (motorcycle)
|-
| ZE5 || Carmosino (truck trailer)
|-
| ZFA || Fiat
|-
| ZFB || Fiat MPV/SUV &amp; Ram Promaster City
|-
| ZFC || Fiat truck (Fiat Ducato for Mexico, Ram 1200)
|-
| ZFE || KL Motorcycle
|-
| ZFF || [[../Ferrari/VIN Codes|Ferrari]]
|-
| ZFJ || Carrozzeria Pezzaioli (truck trailer)
|-
| ZFM || Fantic Motor
|-
| ZFR || Pininfarina
|-
| ZF4 || Qvale
|-
| ZGA || Iveco Bus
|-
| ZGP || Merker (truck trailer)
|-
| ZGU || Moto Guzzi
|-
| ZG2 || FAAM (commercial vehicle)
|-
| ZHU || Husqvarna Motorcycles Under Cagiva ownership
|-
| ZHW || [[../Lamborghini/VIN Codes|Lamborghini]] (Mid-2003 – )
|-
| ZHZ || Menci SpA (truck trailer)
|-
| ZH5 || FB Mondial (motorcycle)
|-
| ZJM || Malaguti
|-
| ZJN || Innocenti
|-
| ZJT || Italjet
|-
| ZKC || Ducati Energia Free Duck (electric quadricycle)
|-
| ZKH || Husqvarna Motorcycles Srl Under BMW ownership
|-
| ZLA || Lancia
|-
| ZLF || Tazzari GL SpA
|-
| ZLM || Moto Morini srl
|-
| ZLV || Laverda
|-
| ZNN || Energica
|-
| ZN0 || SWM Motorcycles S.r.l.
|-
| ZN3 || Iveco Defence
|-
| ZN6 || Maserati SUV
|-
| ZPB || [[../Lamborghini/VIN Codes|Lamborghini]] SUV
|-
| ZPY || DR Automobiles
|-
| ZP6 || XEV
|-
| ZP8 || Regis Motors
|-
| ZRG || Tazzari GL Imola SpA
|-
| ZR1 || Microlino
|-
| ZSG || [[../Ferrari/VIN Codes|Ferrari]] SUV
|-
| ZX1 || TAM (Tovarna Avtomobilov Maribor) bus (Slovenia)
|-
| ZX9/KU0 || K-Bus / Kutsenits (bus) (Slovenia)
|-
| ZX9/DUR || TAM bus (Slovenia)
|-
| ZX9/TV0 || TAM (Tovarna Vozil Maribor) bus (Slovenia)
|-
| ZY1 || Adria (recreational vehicles) (Slovenia)
|-
| ZY9/002 || Gorica (truck trailer) (Slovenia)
|-
| ZZ1 || Tomos motorcycle (Slovenia)
|-
| Z29/555 || Vozila FLuid (truck trailer) (Slovenia)
|-
| Z3D || Tauriga UAB; Tauras trailers (Lithuania)
|-
| Z39/008 || Autogalantas (truck trailer) (Lithuania)
|-
| Z39/009 || Patikima Linija / Rimo (truck trailer) (Lithuania)
|-
| Z6F || Ford Sollers (Russia)
|-
| Z7C || Luidor (bus) (Russia)
|-
| Z7N || KAvZ (bus) (Russia)
|-
| Z7T || RoAZ (bus) (Russia)
|-
| Z7X || Isuzu Rus (Russia)
|-
| Z76 || SEMAZ (Kazakhstan)
|-
| Z8M || Marussia (Russia)
|-
| Z8N || Nissan Manufacturing Rus &amp; Nissan and Datsun models made by AvtoVAZ (Russia)
|-
| Z8P || IRITO
|-
| Z8T || PCMA Rus (Peugeot, Citroen, Mitsubishi) (Russia)
|-
| Z8U || [[w:SsangYong Korando#Third generation (C200; 2010)|Ssangyong Actyon]] made by Sollers (Russia)
|-
| Z8Y || Nasteviya (bus) (Russia)
|-
| Z9B || KuzbassAvto (Hyundai bus) (Russia)
|-
| Z9M || Mercedes-Benz Manufacturing Rus / Mercedes-Benz Trucks Vostok (Russia)
|-
| Z9N || Samotlor-NN (Iveco) (Russia)
|-
| Z94 || Hyundai Motor Manufacturing Rus (Hyundai, Kia) (2008-2023), Solaris Auto - AGR Automotive (2023-) (Russia)
|-
| Z07 || Volgabus (Russia)
|-
| 1A4 1A8 || Chrysler brand MPV/SUV 2006–2009 only
|-
| 1A9/007 || Advance Mixer Inc.
|-
| 1A9/111 || Amerisport Inc. (federalized late model DeTomaso Pantera)
|-
| 1A9/398 || Ameritech (federalized McLaren F1 &amp; Bugatti EB110)
|-
| 1A9/569 || American Custom Golf Cars Inc. (AGC)
|-
| 1AC || American Motors Corporation MPV
|-
| 1AF || American LaFrance truck
|-
| 1AJ || Ajax Manufacturing (truck trailer)
|-
| 1AM || American Motors Corporation car &amp; Renault Alliance 1983 only
|-
| 1BN || Beall Trailers (truck trailer)
|-
| 1B3 || Dodge car 1981–2011
|-
| 1B4 || Dodge MPV/SUV 1981–2002
|-
| 1B6 || Dodge incomplete vehicle 1981–2002
|-
| 1B7 || Dodge truck 1981–2002
|-
| 1B9/133 || Buell Motorcycle Company through mid-1995
|-
| 1B9/274 || Brooks Brothers Trailers
|-
| 1B9/275 || Boydstun Metal Works (truck trailer)
|-
| 1B9/285 || Boss Hoss Cycles
|-
| 1B9/374 || Big Dog Custom Motorcycles through mid-2002
|-
| 1B9/975 || Motus Motorcycles
|-
| 1BA || Blue Bird Corporation bus
|-
| 1BB || Blue Bird Wanderlodge MPV
|-
| 1BD || Blue Bird Corporation incomplete vehicle
|-
| 1BL || Balko, Inc.
|-
| 1C3 || Chrysler brand car 1981–2011
|-
| 1C3 || Chrysler Group (all brands) car (including Lancia) 2012-
|-
| 1C4 || Chrysler brand MPV 1990–2005
|-
| 1C4 || Chrysler Group (all brands) MPV 2012–
|-
| 1C6 || Chrysler Group (all brands) truck 2012–
|-
| 1C8 || Chrysler brand MPV 2001–2005
|-
| 1C9/257 || CEI Equipment Company (truck trailer)
|-
| 1C9/291 || CX Automotive
|-
| 1C9/496 || Carlinville Truck Equipment (truck trailer)
|-
| 1C9/535 || Chance Coach (bus)
|-
| 1C9/737 || Corbin Motors, Inc.
|-
| 1C9/772 || Cozad (truck trailer)
|-
| 1C9/971 || Cool Amphibious Manufacturers International
|-
| 1CM || Checker Motors Corporation
|-
| 1CU || Cushman Haulster (Cushman division of Outboard Marine Corporation)
|-
| 1CY || Crane Carrier Company
|-
| 1CY || Battle Motors, Inc.
|-
| 1D3 || Dodge truck 2002–2009
|-
| 1D4 || Dodge MPV/SUV 2003–2011 only
|-
| 1D7 || Dodge truck 2002–2011
|-
| 1D8 || Dodge MPV/SUV 2003–2009 only
|-
| 1D9/008 || KME Fire Apparatus
|-
| 1D9/628 || Dymac Vehicle Group (low-speed vehicle)
|-
| 1D9/791 || Dennis Eagle, Inc.
|-
| 1DW || Stoughton Trailers (truck trailer)
|-
| 1E9/007 || E.D. Etnyre &amp; Co. (truck trailer)
|-
| 1E9/190 || Electric Transit Inc. (trolleybus)
|-
| 1E9/363 || E-SUV LLC (E-Ride Industries)
|-
| 1E9/456 || Electric Motorsport (GPR-S electric motorcycle)
|-
| 1E9/526 || Epic TORQ
|-
| 1E9/581 || Vetter Razor
|-
| 1EU || Eagle Coach Corporation (bus)
|-
| 1FA || [[../Ford/VIN Codes|Ford]] car
|-
| 1FB || [[../Ford/VIN Codes|Ford]] &quot;bus&quot; (van with more than 3 rows of seats)
|-
| 1FC || [[../Ford/VIN Codes|Ford]] stripped chassis made by Ford
|-
| 1FD || [[../Ford/VIN Codes|Ford]] incomplete vehicle
|-
| 1FM || [[../Ford/VIN Codes|Ford]] MPV/SUV
|-
| 1FT || [[../Ford/VIN Codes|Ford]] truck
|- 
| 1FU || Freightliner (truck)
|-
| 1FV || Freightliner (incomplete vehicle)
|-
| 1F1 || Ford SUV - Limousine (through 2009)
|-
| 1F6 || Ford stripped chassis made by Detroit Chassis LLC
|-
| 1F9/037 || Federal Motors Inc. 
|-
| 1F9/140 || Ferrara Fire Apparatus (incomplete vehicle)
|-
| 1F9/458 || Faraday Future prototypes
|- 
| 1F9/FT1 || FWD Corp.
|-
| 1F9/ST1 || Seagrave Fire Apparatus
|-
| 1F9/ST2 || Seagrave Fire Apparatus
|-
| 1G || [[../GM/VIN Codes|General Motors]] USA
|-
| 1G0 || GMC &quot;bus&quot; (van with more than 3 rows of seats) 1981–1986
|-
| 1G0 || GMC Rapid Transit Series (RTS) bus 1981–1984
|-
| 1G0 || Opel/Vauxhall car 2007–2017
|-
| 1G1 || [[../GM/VIN Codes|Chevrolet]] car
|-
| 1G2 || [[../GM/VIN Codes|Pontiac]] car
|-
| 1G3 || [[../GM/VIN Codes|Oldsmobile]] car
|-
| 1G4 || [[../GM/VIN Codes|Buick]] car
|-
| 1G5 || GMC MPV/SUV 1981–1986
|-
| 1G5 || Pontiac incomplete vehicle 1989-1990, 2003-2006
|-
| 1G6 || [[../GM/VIN Codes|Cadillac]] car
|-
| 1G7 || Pontiac car only sold by GM Canada
|-
| 1G8 || Chevrolet MPV/SUV 1981–1986
|-
| 1G8 || [[../GM/VIN Codes|Saturn]] car 1991–2010
|-
| 1G9/492 || GreenPower Motor Company incomplete vehicle 
|-
| 1G9/495 || Google &amp; Waymo
|-
| 1GA || Chevrolet &quot;bus&quot; (van with more than 3 rows of seats)
|-
| 1GB || Chevrolet incomplete vehicle
|-
| 1GC || [[../GM/VIN Codes|Chevrolet]] truck 
|-
| 1GD || GMC incomplete vehicle
|-
| 1GE || Cadillac incomplete vehicle
|-
| 1GF || Flxible bus
|-
| 1GG || Isuzu pickup trucks made by GM
|-
| 1GH || GMC Rapid Transit Series (RTS) bus 1985–1986
|-
| 1GH || Oldsmobile MPV/SUV 1990–2004
|-
| 1GH || Holden Acadia 2019–2020
|-
| 1GJ || GMC &quot;bus&quot; (van with more than 3 rows of seats) 1987–
|-
| 1GK || GMC MPV/SUV 1987–
|-
| 1GM || [[../GM/VIN Codes|Pontiac]] MPV
|-
| 1GN || [[../GM/VIN Codes|Chevrolet]] MPV/SUV 1987-
|-
| 1GR || Great Dane Trailers (truck trailer)
|-
| 1GT || [[../GM/VIN Codes|GMC]] Truck 
|-
| 1GW || Grumman Olson Kubvan (truck)
|-
| 1GY || [[../GM/VIN Codes|Cadillac]] SUV
|-
| 1HA || Chevrolet incomplete vehicles (Express cutaway) made by Navistar International/International Motors
|-
| 1HD || Harley-Davidson &amp; LiveWire
|-
| 1HF || Honda motorcycle/ATV/UTV
|-
| 1HG || [[../Honda/VIN Codes|Honda]] car made by Honda of America Mfg. in Ohio
|-
| 1HP || International Trucks (complete vehicle - straight truck)
|-
| 1HS || International Trucks &amp; Caterpillar Trucks (complete vehicle - truck tractor)
|-
| 1HT || International Trucks &amp; Caterpillar Trucks &amp; Chevrolet Silverado 4500HD, 5500HD, 6500HD (incomplete vehicle - straight truck)
|-
| 1HV || International or IC Bus (incomplete vehicle - bus) 
|-
| 1H9/484 || Hughes Trailers (Based in Canyon, TX) (trailer)
|-
| 1H9/674 || Hines Specialty Vehicle Group
|-
| 1JC || Jeep SUV 1981–1988 (using AMC-style VIN structure)
|-
| 1JJ || Wabash (truck trailer)
|-
| 1JT || Jeep truck 1981–1988 (using AMC-style VIN structure)
|-
| 1JU || Marmon Motor Company (truck)
|-
| 1J4 || Jeep SUV 1989–2011 (using Chrysler-style VIN structure)
|-
| 1J7 || Jeep truck 1989–1992 (using Chrysler-style VIN structure)
|-
| 1J8 || Jeep SUV 2002–2011 (using Chrysler-style VIN structure)
|-
| 1KB || Holiday Rambler Corp. 1981-2010 (trailer)
|-
| 1K9/058 || Kovatech Mobile Equipment (fire engine)
|-
| 1LH || Landoll (truck trailer)
|-
| 1LJ || Lincoln incomplete vehicle
|-
| 1LN || [[../Ford/VIN Codes|Lincoln]] car
|-
| 1LV || Lectra Motors
|-
| 1L0 || Lufkin Trailers
|-
| 1L1 || Lincoln car – limousine
|-
| 1L9/155 || LA Exotics
|-
| 1L9/234 || Laforza
|-
| 1MB || Mercedes-Benz Truck Co.
|-
| 1ME || [[../Ford/VIN Codes|Mercury]] car
|-
| 1MR || Continental Mark VI &amp; VII 1981–1985 &amp; Continental sedan 1982–1985
|-
| 1M0 || John Deere Gator
|-
| 1M1 || Mack Truck USA (truck)
|-
| 1M2 || Mack Truck USA (incomplete vehicle)
|-
| 1M3 || Mack Truck USA (glider)
|-
| 1M8 || Motor Coach Industries (bus)
|-
| 1M9/089 || Mauck Special Vehicles (bus)
|-
| 1M9/682 || Mosler Automotive
|-
| 1M9/816 || Proterra Through mid-2019
|-
| 1N4 || Nissan car
|-
| 1N6 || Nissan truck
|-
| 1N9/019 || Neoplan USA
|-
| 1N9/084 || Eldorado National (California)
|-
| 1N9/140 || North American Bus Industries (bus)
|-
| 1N9/393 || Nikola Corporation (truck)
|-
| 1NK || Kenworth (incomplete vehicle)
|-
| 1NL || Gulf Stream Coach (recreational vehicles)
|-
| 1NN || Monon made by Evans Products Co. (truck trailer)
|-
| 1NP || Peterbilt (incomplete vehicle)
|-
| 1NX || Toyota car made by NUMMI
|-
| 1P3 || Plymouth car
|-
| 1P4 || Plymouth MPV/SUV
|-
| 1P7 || Plymouth Scamp
|-
| 1P9/038 || Hawk Vehicles, Inc. (Trihawk motorcycles)
|-
| 1P9/213 || Panoz
|-
| 1P9/255 || Pinson Truck Equipment Company (truck trailer)
|-
| 1PM || Polar Tank Trailer (truck trailer)
|-
| 1PT || Trailmobile Trailer Corporation (truck trailer)
|-
| 1PY || John Deere USA
|-
| 1RF || Roadmaster, Monaco Coach Corporation (incomplete vehicle)
|-
| 1RN || Reitnouer (truck trailer)
|-
| 1R9/956 || Reede Fabrication and Design (motorcycles)
|-
| 1ST || Airstream (recreational vehicles)
|-
| 1S1 || Strick Trailers (truck trailer)
|-
| 1S9/003 || Sutphen Corporation (fire engines - truck)
|-
| 1S9/009|| Superior Trailer Works (truck trailer)
|-
| 1S9/098 || Scania AB (Scania CN112 bus made in Orange, CT)
|-
| 1S9/842 || Saleen S7
|-
| 1S9/260 || Stairs Welding RL (truck trailer)
|-
| 1S9/901 || Suckerpunch Sallys, LLC
|-
| 1S9/944 || SSC North America
|-
| 1TD || Timpte (truck trailer)
|-
| 1TK || Trail King (truck trailer)
|-
| 1TD || Transcraft Corporation (truck trailer)
|-
| 1T7 || Thomas Built Buses
|-
| 1T8 || Thomas Built Buses
|-
| 1T9/072 || The Trailer Co. (truck trailer)
|-
| 1T9/717 || Thunder Mountain Custom Cycles
|-
| 1T9/825 || TICO Manufacturing Company (truck)
|-
| 1T9/899 || Tomcar USA
|-
| 1T9/970 || Three Two Chopper
|-
| 1TC || Coachmen Recreational Vehicle Co., LLC
|-
| 1TU || Transportation Manufacturing Corporation
|-
| 1UJ || Jayco, Inc.
|-
| 1UT || AM General military trucks, Jeep DJ made by AM General
|-
| 1UY || Utility Trailer (truck trailer)
|-
| 1VH || Orion Bus Industries
|-
| 1VW || Volkswagen car
|-
| 1V1 || Volkswagen truck
|-
| 1V2 || Volkswagen SUV
|-
| 1V9/048 || Vector Aeromotive
|-
| 1V9/113 || Vantage Vehicle International Inc (low-speed vehicle)
|-
| 1V9/190 || Vanderhall Motor Works
|-
| 1WA || White Motor Company (Autocar brand truck)
|-
| 1WB || White Motor Company (Autocar brand incomplete vehicle)
|-
| 1WD || White Motor Company (Autocar brand glider)
|-
| 1WT || Winnebago Industries: Winnebago M.P.V.
|-
| 1WU || White Motor Company (White brand truck)
|-
| 1WV || Winnebago Industries: Winnebago M.P.V. - Class C Motorhome built on VW chassis &amp; front cab [Winnebago Rialta ('95-'96)]
|-
| 1WW || Winnebago Industries: Winnebago M.P.V. - Class B Motorhome built on Renault chassis [Winnebago LeSharo, Centauri, Itasca Phasar]
|-
| 1WX || White Motor Company (White brand incomplete vehicle)
|-
| 1WY || White Motor Company (White brand glider)
|-
| 1W1 || Wilson Trailer Co. (truck trailer)
|-
| 1W5 || Western Recreational Vehicles (Alpenlite)
|-
| 1W8 || Witzco (truck trailer)
|-
| 1W9/010 || Weld-It Company (truck trailer)
|-
| 1W9/485 || Wheego Electric Cars
|-
| 1W9/488 || Certified Stainless Services Inc. DBA West-Mark (truck trailer) (2010 &amp; later)
|-
| 1XA || Excalibur Automobile Corporation
|-
| 1XK || Kenworth (truck)
|-
| 1XM || Renault Alliance/GTA/Encore 1984–1987
|-
| 1XP || Peterbilt (truck)
|-
| 1Y1 || Chevrolet/Geo car made by NUMMI
|-
| 1YJ || Rokon International, Inc.
|-
| 1YV || [[../Ford/VIN Codes|Mazda made by Mazda Motor Manufacturing USA/AutoAlliance International]]
|-
| 1ZV || [[../Ford/VIN Codes|Ford made by Mazda Motor Manufacturing USA/AutoAlliance International]]
|-
| 1ZW || [[../Ford/VIN Codes|Mercury made by AutoAlliance International]]
|-
| 1Z3 1Z7 || Mitsubishi Raider
|-
| 1Z9/170 || [[w:Orange County Choppers|Orange County Choppers]]
|-
| 10B || Brenner Tank (truck trailer)
|-
| 10R || E-Z-GO
|-
| 10T || Oshkosh Corporation 
|-
| 11H || Hendrickson Mobile Equipment, Inc. (fire engines - incomplete vehicle)
|-
| 11V || Kalmar Solutions (Truck - Terminal Tractor)
|-
| 12A || Avanti
|-
| 137 || AM General Hummer &amp; Hummer H1
|-
| 13N || Fontaine (truck trailer)
|-
| 15G || Gillig bus
|-
| 16C || Clenet Coachworks
|-
| 16W || Certified Stainless Services Inc. DBA West-Mark (truck trailer) (prior to 2010)
|-
| 16X || Vixen 21 motorhome
|-
| 17N || John Deere incomplete vehicle (RV chassis)
|-
| 18X || Western Recreational Vehicles
|-
| 19U || Acura car made by Honda of America Mfg. in Ohio
|-
| 19V || Acura car made by Honda Manufacturing of Indiana
|-
| 19X || Honda car made by Honda Manufacturing of Indiana
|-
| 2A3 || Imperial
|-
| 2A4 2A8 || Chrysler brand MPV/SUV 2006–2011 only
|-
| 2AY 2AZ || Hino
|-
| 2BC || Jeep Wrangler (YJ) 1987–1988 (using AMC-style VIN structure)
|-
| 2BP || Ski-Doo
|-
| 2BV || Can-Am &amp; Bombardier ATV
|-
| 2BW || Can-Am Commander E LSV
|-
| 2BX || Can-Am Spyder &amp; Canyon 3-wheelers
|-
| 2BZ || Can-Am Freedom Trailer for Can-Am Spyder &amp; Canyon
|-
| 2B1 || Orion Bus Industries
|-
| 2B3 || Dodge car 1981–2011
|-
| 2B4 || Dodge MPV 1981–2002
|-
| 2B5 || Dodge &quot;bus&quot; (van with more than 3 rows of seats) 1981–2002
|-
| 2B6 || Dodge incomplete vehicle 1981–2002
|-
| 2B7 || Dodge truck 1981–2002
|-
| 2B9/001 || BWS Manufacturing (truck trailer)
|-
| 2C1 || Geo/Chevrolet car made by CAMI Automotive
|-
| 2C3 || Chrysler brand car 1981–2011
|-
| 2C3 || Chrysler Group (all brands) car (including Lancia) 2012-
|-
| 2C4 || Chrysler brand MPV/SUV 2000–2005
|-
| 2C4 || Chrysler Group (all brands) MPV (including Lancia Voyager &amp; Volkswagen Routan) 2012-
|-
| 2C7 || Pontiac car made by CAMI Automotive only sold by GM Canada
|-
| 2C8 || Chrysler brand MPV/SUV 2001–2005
|-
| 2C9/145 || Campagna Motors
|-
| 2C9/197 || Canadian Electric Vehicles
|-
| 2CC || American Motors Corporation MPV
|-
| 2CG || Asüna/Pontiac SUV made by CAMI Automotive only sold by GM Canada
|-
| 2CK || GMC Tracker SUV made by CAMI Automotive only sold by GM Canada 1990–1991 only
|-
| 2CK || Pontiac Torrent SUV made by CAMI Automotive 2006–2009 only
|-
| 2CM || American Motors Corporation car
|-
| 2CN || Geo/Chevrolet SUV made by CAMI Automotive 1990–2011 only
|-
| 2CT || GMC Terrain SUV made by CAMI Automotive 2010–2011 only
|-
| 2D4 || Dodge MPV 2003–2011 only
|-
| 2D6 || Dodge incomplete vehicle 2003
|-
| 2D7 || Dodge truck 2003
|-
| 2D8 || Dodge MPV 2003–2011 only
|-
| 2DG || Ontario Drive &amp; Gear
|-
| 2DM || Di-Mond Trailers (truck trailer)
|-
| 2DN || Dynasty Electric Car Corporation
|-
| 2EZ || Electra Meccanica Vehicles Corp. (Solo)
|-
| 2E3 || Eagle car 1989–1997 (using Chrysler-style VIN structure)
|-
| 2E4 || 2011 Lancia MPV (Voyager)
|-
| 2E9/080 || Electra Meccanica Vehicles Corp. (Solo)
|-
| 2FA || [[../Ford/VIN Codes|Ford]] car
|-
| 2FH || Zenn Motor Co., Ltd. (low-speed vehicle)
|-
| 2FM || [[../Ford/VIN Codes|Ford]] MPV/SUV
|-
| 2FT || [[../Ford/VIN Codes|Ford]] truck
|-
| 2FU || Freightliner (truck)
|-
| 2FV || Freightliner (incomplete vehicle)
|-
| 2FW || Sterling Trucks (truck-complete vehicle)
|-
| 2FY || New Flyer
|-
| 2FZ || Sterling Trucks (incomplete vehicle)
|- 
| 2Gx || [[../GM/VIN Codes|General Motors]] Canada
|-
| 2G0 || GMC &quot;bus&quot; (van with more than 3 rows of seats) 1981–1986
|-
| 2G1 || [[../GM/VIN Codes|Chevrolet]] car
|-
| 2G2 || [[../GM/VIN Codes|Pontiac]] car
|-
| 2G3 || [[../GM/VIN Codes|Oldsmobile]] car
|-
| 2G4 || [[../GM/VIN Codes|Buick]] car
|-
| 2G5 ||  GMC MPV 1981–1986
|-
| 2G5 ||  Chevrolet BrightDrop / BrightDrop Zevo truck 2023-2026
|-
| 2G6 || [[../GM/VIN Codes|Cadillac]] car
|-
| 2G7 ||  Pontiac car only sold by GM Canada
|-
| 2G8 ||  Chevrolet MPV 1981–1986
|-
| 2GA || Chevrolet &quot;bus&quot; (van with more than 3 rows of seats) 
|-
| 2GB || Chevrolet incomplete vehicle
|-
| 2GC || Chevrolet truck 
|-
| 2GD || GMC incomplete vehicle
|-
| 2GE || Cadillac incomplete vehicle 
|-
| 2GH || GMC GM New Look bus &amp; GM Classic series bus 
|-
| 2GJ || GMC &quot;bus&quot; (van with more than 3 rows of seats) 1987– 
|-
| 2GK || GMC MPV/SUV 1987– 
|-
| 2GN || Chevrolet MPV/SUV 1987- 
|-
| 2GT || GMC truck 
|-
| 2HG || [[../Honda/VIN Codes|Honda]] car made by Honda of Canada Manufacturing
|-
| 2HH || Acura car made by Honda of Canada Manufacturing
|-
| 2HJ || [[../Honda/VIN Codes|Honda]] truck made by Honda of Canada Manufacturing
|-
| 2HK || [[../Honda/VIN Codes|Honda]] MPV/SUV made by Honda of Canada Manufacturing
|-
| 2HM || Hyundai Canada
|-
| 2HN || Acura SUV made by Honda of Canada Manufacturing
|-
| 2HP || International Trucks (complete vehicle - straight truck)
|-
| 2HS || International Trucks (complete vehicle - truck tractor)
|-
| 2HT || International Trucks (incomplete vehicle - straight truck)
|-
| 2HV || International or IC Bus (incomplete vehicle - bus) 
|-
| 2J4 || Jeep Wrangler (YJ) 1989–1992 (using Chrysler-style VIN structure)
|-
| 2L1 || Lincoln incomplete vehicle – limo
|-
| 2LD || Triple E Canada Ltd.
|-
| 2LJ || Lincoln incomplete vehicle – hearse
|-
| 2LM || Lincoln SUV
|-
| 2LN || Lincoln car
|-
| 2M1 || Mack Trucks Canada (truck)
|-
| 2M2 || Mack Trucks Canada (incomplete vehicle)
|-
| 2M3 || Mack Truck Canada (glider)
|-
| 2ME || [[../Ford/VIN Codes|Mercury]] car
|-
| 2MG || Motor Coach Industries (Produced from Sept. 1, 2008 on)
|-
| 2MH || [[../Ford/VIN Codes|Mercury]] incomplete vehicle
|-
| 2MR || [[../Ford/VIN Codes|Mercury]] MPV
|-
| 2M9/044 || Westward Industries
|-
| 2M9/058 || Motor Coach Industries
|-
| 2NK || Kenworth incomplete vehicle
|-
| 2NP || Peterbilt incomplete vehicle
|-
| 2NV || Nova Bus 
|-
| 2P3 || Plymouth car
|-
| 2P4 || Plymouth MPV 1981–2000
|-
| 2P5 || Plymouth &quot;bus&quot; (van with more than 3 rows of seats) 1981–1983
|-
| 2P9/001 || Prevost 1981–1995
|-
| 2PC || Prevost 1996-
|-
| 2S2 || Suzuki car made by CAMI Automotive
|-
| 2S3 || Suzuki SUV made by CAMI Automotive
|-
| 2TU || Tri-Star Industries Limited
|-
| 2T1 || [[../Toyota/VIN Codes|Toyota]] car made by TMMC
|-
| 2T2 || Lexus SUV made by TMMC
|-
| 2T3 || [[../Toyota/VIN Codes|Toyota]] SUV made by TMMC
|-
| 2T9/206 || Triple E Canada Ltd.
|-
| 2V4 || Volkswagen Routan made by Chrysler Canada
|-
| 2V8 || Volkswagen Routan made by Chrysler Canada
|-
| 2W9/044 || Westward Industries
|-
| 2WK || Western Star (truck)
|-
| 2WL || Western Star (incomplete vehicle)
|-
| 2WM || Western Star (glider)
|-
| 2XK || Kenworth (truck)
|-
| 2XM || Eagle Premier 1988 only (using AMC-style VIN structure)
|-
| 2XP || Peterbilt (truck)
|-
| 3A4 3A8 || Chrysler brand MPV 2006–2010 only
|-
| 3A9/050 || MARGO (truck trailer)
|-
| 3AK || Freightliner Trucks (truck)
|-
| 3AL || Freightliner Trucks (incomplete vehicle)
|-
| 3AW || Fruehauf de Mexico (truck trailer)
|-
| 3AX || Scania Mexico
|-
| 3BE || Scania Mexico (buses)
|-
| 3BH || Western Star 3700 (truck) made by DINA S.A.
|-
| 3BH || Western Star (truck)
|-
| 3BJ || Western Star 3700 (incomplete vehicle) made by DINA S.A.
|-
| 3BJ || Western Star (incomplete vehicle)
|-
| 3BK || Kenworth (incomplete vehicle)
|-
| 3BM || Motor Coach Industries bus made by DINA S.A.
|-
| 3BP || Peterbilt  (incomplete vehicle)
|-
| 3B3 || Dodge car 1981–2011
|-
| 3B4 || Dodge SUV 1986–1993
|-
| 3B6 || Dodge incomplete vehicle 1981–2002
|-
| 3B7 || Dodge truck 1981–2002
|-
| 3C3 || Chrysler brand car 1981–2011
|-
| 3C3 || Chrysler Group (all brands) car (including Fiat) 2012-
|-
| 3C4 || Chrysler brand MPV 2001–2005
|-
| 3C4 || Chrysler Group (all brands) MPV (including Fiat) 2012-
|-
| 3C6 || Chrysler Group (all brands) truck 2012–
|-
| 3C7 || Chrysler Group (all brands) incomplete vehicle 2012–
|-
| 3C8 || Chrysler brand MPV 2001–2005
|-
| 3CA || Chrysler brand MPV 2001 (PT Cruiser w/serial# 232057-265662)
|-
| 3CE || Volvo Buses de Mexico
|-
| 3CG || KTMMEX S.A. de C.V.
|-
| 3CZ || Honda SUV made by Honda de Mexico
|-
| 3D2 || Dodge incomplete vehicle 2007–2009
|-
| 3D3 || Dodge truck 2006–2009
|-
| 3D4 || Dodge SUV 2009–2011
|-
| 3D6 || Dodge incomplete vehicle 2003–2011
|-
| 3D7 || Dodge truck 2002–2011
|-
| 3EL || ATRO (truck trailer)
|-
| 3E4 || 2011 Fiat SUV (Freemont)
|-
| 3FA || [[../Ford/VIN Codes|Ford]] car
|-
| 3FC || Ford stripped chassis made by Ford &amp; IMMSA
|-
| 3FE || [[../Ford/VIN Codes|Ford]] Mexico
|-
| 3FM || [[../Ford/VIN Codes|Ford]] MPV/SUV
|-
| 3FN || Ford F-650/F-750 made by Blue Diamond Truck Co. (truck)
|-
| 3FR || Ford F-650/F-750 &amp; Ford LCF made by Blue Diamond Truck Co. (incomplete vehicle)
|-
| 3FT || [[../Ford/VIN Codes|Ford]] truck
|-
| 3F6 || Sterling Bullet
|-
| 3G || [[../GM/VIN Codes|General Motors]] Mexico
|-
| 3G0 || Saab 9-4X 2011
|-
| 3G0 || Holden Equinox 2018–2020
|-
| 3G1 || [[../GM/VIN Codes|Chevrolet]] car
|-
| 3G2 || [[../GM/VIN Codes|Pontiac]] car
|-
| 3G4 || [[../GM/VIN Codes|Buick]] car
|-
| 3G5 || [[../GM/VIN Codes|Buick]] SUV
|-
| 3G7 || [[../GM/VIN Codes|Pontiac]] SUV
|-
| 3GA || JAC models assembled by Giant Motors in Mexico
|-
| 3GC || Chevrolet truck
|-
| 3GK || GMC SUV
|-
| 3GM || Holden Suburban
|-
| 3GN || Chevrolet SUV
|-
| 3GP || Honda Prologue EV made by GM
|-
| 3GS || Saturn SUV
|-
| 3GT || GMC truck
|-
| 3GY || Cadillac SUV
|-
| 3H1 || Honda motorcycle/UTV
|-
| 3H3 || Hyundai de Mexico, S.A. de C.V. for Hyundai Translead (truck trailers)
|-
| 3HA || International Trucks (incomplete vehicle - straight truck) made by Blue Diamond Truck Co. 2011-2015
|-
| 3HA || International Trucks (incomplete vehicle - straight truck) made by Navistar Mexico/International Motors Mexico 2016-
|-
| 3HC || International Trucks (complete vehicle - truck tractor) made by Blue Diamond Truck Co. 2011-2015
|-
| 3HC || International Trucks (complete vehicle - truck tractor) made by Navistar Mexico/International Motors Mexico 2016-
|-
| 3HD || Acura SUV made by Honda de Mexico
|-
| 3HG || [[../Honda/VIN Codes|Honda]] car made by Honda de Mexico
|-
| 3HR || International Trucks (complete vehicle - truck)
|-
| 3HS || International Trucks &amp; Caterpillar Trucks (complete vehicle - truck tractor)
|-
| 3HT || International Trucks &amp; Caterpillar Trucks (incomplete vehicle - straight truck)
|-
| 3HV || International (incomplete vehicle - bus)  
|-
| 3JB || BRP Mexico (Can-Am ATV/UTV &amp; Can-Am Ryker 3-wheeler)
|-
| 3JC || BRP Mexico (Can-Am Origin &amp; Pulse electric 2-wheel motorcycles)
|-
| 3KM || Kia/Hyundai MPV/SUV made by KMMX
|-
| 3KP || Kia/Hyundai car made by KMMX
|-
| 3LN || Lincoln car
|-
| 3MA || Mercury car (1988-1995)
|-
| 3MD || Mazda de Mexico car (Mazda 2)
|-
| 3ME || Mercury car (1996-2011)
|-
| 3MF || BMW M car
|-
| 3MG || Isuzu Motors de Mexico
|-
| 3MJ || Mazda CX-3 (Mazda de Mexico)
|-
| 3MV || Mazda de Mexico SUV (Mazda CX-30)
|-
| 3MW || BMW car
|-
| 3MY || Toyota car made by Mazda de Mexico Vehicle Operation
|-
| 3MZ || Mazda de Mexico car (Mazda 3)
|-
| 3N1 || Nissan Mexico car
|-
| 3N6 || Nissan Mexico truck &amp; Chevrolet City Express
|-
| 3N8 || Nissan Mexico MPV
|-
| 3NS || Polaris Industries ATV
|-
| 3NE || Polaris Industries UTV
|-
| 3P3 || Plymouth car
|-
| 3PC || Infiniti SUV made by COMPAS
|-
| 3TM || Toyota truck made by TMMBC
|-
| 3TY || Toyota truck made by TMMGT
|-
| 3VV || Volkswagen Mexico SUV
|-
| 3VW || Volkswagen Mexico car
|-
| 3WK || Kenworth truck
|-
| 3WP || Peterbilt truck
|-
| 3X1 || Mack Truck Mexico (truck)
|-
| 3X2 || Mack Truck Mexico (incomplete vehicle)
|-
| 4A3 || Mitsubishi Motors car
|-
| 4A4 || Mitsubishi Motors SUV
|-
| 4B3 || Dodge car made by Diamond-Star Motors factory
|-
| 4B9/038 || BYD Coach &amp; Bus LLC
|-
| 4C3 || Chrysler car made by Diamond-Star Motors factory
|-
| 4C6 || Reinke Manufacturing Company (truck trailer)
|-
| 4C9/272 || Christini Technologies (motorcycle)
|-
| 4C9/561 || Czinger
|-
| 4C9/626 || Canoo Inc.
|-
| 4CD || Oshkosh Chassis Division incomplete vehicle (RV chassis)
|-
| 4DR || IC Bus (complete vehicle - bus)
|-
| 4E3 || Eagle car made by Diamond-Star Motors factory
|-
| 4EN || E-ONE, Inc. (fire engines - truck)
|-
| 4EZ || KZ Recreational Vehicles (trailer)
|-
| 4F2 || Mazda SUV made by Ford
|-
| 4F4 || Mazda truck made by Ford
|-
| 4G1 || Chevrolet Cavalier convertible made by Genasys L.C. – a GM/ASC joint venture
|-
| 4G2 || Pontiac Sunfire convertible made by Genasys L.C. – a GM/ASC joint venture
|-
| 4G3 || Toyota Cavalier made by GM
|-
| 4G5 || General Motors EV1
|-
| 4GD || WhiteGMC Brigadier 1988–1989 made by GM
|-
| 4GD || Opel/Vauxhall Sintra
|-
| 4GL || Buick incomplete vehicle
|-
| 4GT || Isuzu incomplete vehicle built by GM
|-
| 4JG || [[../Mercedes-Benz/VIN Codes|Mercedes-Benz]] SUV
|-
| 4J8 || LBT, Inc. (truck trailer)
|-
| 4KA || IC Bus (complete vehicle - truck)
|-
| 4KB || Chevrolet W-Series (gas engine only) made by GM (Incomplete Vehicle - medium duty)
|-
| 4KD || GMC W-Series (gas engine only) made by GM (Incomplete Vehicle - medium duty)
|-
| 4KL || Isuzu N-Series (gas engine only) made by GM (Incomplete Vehicle - medium duty)
|-
| 4LM || Capacity Trucks (truck) [terminal tractors]
|-
| 4M2 || [[../Ford/VIN Codes|Mercury]] MPV/SUV
|-
| 4M9/220 || Meyers Manx, LLC (Manx 2.0 EV) [Passenger Car - Replica]
|-
| 4ML || Oshkosh Trailer Division
|-
| 4MZ || Buell Motorcycle Company (Mid-1995 – )
|-
| 4N2 || Nissan Quest made by Ford
|-
| 4NU || Isuzu Ascender made by GM
|-
| 4PR || Hughes Trailers of Jackson (trailer)
|-
| 4P1 || Pierce Manufacturing Inc. USA
|-
| 4P3 || Plymouth car made by Diamond-Star Motors factory 1990–1994
|-
| 4P3 || Mitsubishi Motors SUV made by Mitsubishi Motor Manufacturing of America 2013–2015 for export only
|-
| 4RK || Nova Bus &amp; Prevost made by Nova Bus (US) Inc.
|-
| 4S1 || Isuzu truck made by Subaru Isuzu Automotive
|-
| 4S2 || Isuzu SUV made by Subaru Isuzu Automotive &amp; 2nd gen. Holden Frontera made by SIA
|-
| 4S3 || [[../Subaru/VIN Codes|Subaru]] car
|-
| 4S4 || [[../Subaru/VIN Codes|Subaru]] SUV/MPV
|-
| 4S6 || Honda SUV made by Subaru Isuzu Automotive
|-
| 4S7 || Spartan Motors incomplete vehicle 
|-
| 4S9/197 || Smith Electric Vehicles
|-
| 4S9/345 || Satellite Suites (trailer)
|-
| 4S9/419 || Spartan Motors truck
|-
| 4S9/454 || Scuderia Cameron Glickenhaus passenger car
|-
| 4S9/520 || Signature Autosport, LLC (Osprey Custom Cars)
|-
| 4S9/542 || Scuderia Cameron Glickenhaus SCG Boot (M.P.V.)
|-
| 4S9/544 || Scuderia Cameron Glickenhaus passenger car
|-
| 4S9/559 || Spartan Fire, LLC truck (formerly Spartan ER)
|-
| 4S9/560 || Spartan Fire, LLC incomplete vehicle (formerly Spartan ER)
|-
| 4S9/569 || SC Autosports, LLC (Kandi)
|-
| 4TA || [[../Toyota/VIN Codes|Toyota]] truck made by NUMMI
|-
| 4T1 || [[../Toyota/VIN Codes|Toyota]] car made by Toyota Motor Manufacturing Kentucky
|-
| 4T3 || [[../Toyota/VIN Codes|Toyota]] MPV/SUV made by Toyota Motor Manufacturing Kentucky
|-
| 4T4 || [[../Toyota/VIN Codes|Toyota]] car made by Subaru of Indiana Automotive
|-
| 4T9/208 || Xos, Inc.
|-
| 4T9/228 || Lumen Motors
|-
| 4UF || Arctic Cat Inc.
|-
| 4US || BMW car
|-
| 4UZ || Freightliner Custom Chassis Corporation &amp; &lt;br /&gt; gas-powered Mitsubishi Fuso trucks assembled by Freightliner Custom Chassis &amp; &lt;br /&gt; Thomas Built Buses FS-65 &amp; Saf-T-Liner C2
|-
| 4V0 || Crossroads RV (recreational vehicles)
|-
| 4V1 || WhiteGMC (truck) 1988-1995
|-
| 4V2 || WhiteGMC (incomplete vehicle) 1988-1995
|-
| 4V3 || WhiteGMC (glider) 1988-1995
|-
| 4V1 || Volvo Trucks North America [low cab-over engine] (truck) 2000-2003
|-
| 4V2 || Volvo Trucks North America [low cab-over engine] (incomplete vehicle) 2000-2003
|-
| 4V4 || Volvo Trucks North America [conventional] (truck) 1996+
|-
| 4V5 || Volvo Trucks North America [conventional] (incomplete vehicle)  1996+
|-
| 4V6 || Volvo Trucks North America (glider)
|-
| 4VA || Volvo Trucks North America [conventional- Class 7 w/air brakes] (truck) 1997-1999
|-
| 4VB || Volvo Trucks North America [conventional- Class 7 w/air brakes] (incomplete vehicle) 1997-1999
|-
| 4VC || Volvo Trucks North America [conventional- Class 7 w/hydraulic brakes] (incomplete vehicle)
|-
| 4VD || Volvo Trucks North America [low cab-over engine- Class 7 w/air brakes] (truck)
|-
| 4VE || Volvo Trucks North America [low cab-over engine- Class 7 w/air brakes] (incomplete vehicle)
|-
| 4VG || Volvo Trucks North America [conventional- Class 8 w/air brakes] (truck) 1997-1999
|-
| 4VH || Volvo Trucks North America [conventional- Class 8 w/air brakes] (incomplete vehicle) 1997-1999
|-
| 4VJ || Volvo Trucks North America [high cab-over engine- Class 8 w/air brakes] (truck)
|-
| 4VK || Volvo Trucks North America [high cab-over engine- Class 8 w/air brakes] (incomplete vehicle)
|-
| 4VL || Volvo Trucks North America [low cab-over engine- Class 8 w/air brakes] (truck)
|-
| 4VM || Volvo Trucks North America [low cab-over engine- Class 8 w/air brakes] (incomplete vehicle)
|-
| 4VZ || Spartan Motors/The Shyft Group (incomplete vehicle – bare chassis only)
|-
| 4WW || Wilson Trailer Sales
|-
| 4W1 || '24+ Chevrolet Suburban HD made by GM Defense for US govt. in Concord, NC
|-
| 4W5 || Acura ZDX EV made by GM
|-
| 4XA || Polaris Inc.
|-
| 4X4 || Forest River
|-
| 4YD || KeyStone RV Company (recreational vehicle)
|-
| 4YM || Carry-On Trailer, Inc.
|-
| 4YM || Anderson Manufacturing (trailer)
|-
| 4Z3 || American LaFrance truck
|-
| 43C || Consulier
|-
| 44K || HME Inc. (fire engines - incomplete vehicle) (HME=Hendrickson Mobile Equipment)
|-
| 46G || Gillig incomplete vehicle
|-
| 46J || Federal Motors Inc
|-
| 478 || Honda ATV
|-
| 480 || Sterling Trucks (truck)
|-
| 49H || Sterling Trucks (incomplete vehicle)
|-
| 5AS || Global Electric Motorcars (GEM) 1999-2011
|-
| 5AX || Armor Chassis (truck trailer)
|-
| 5A4 || Load Rite Trailers Inc.
|-
| 5BP || Solectria
|-
| 5BZ || Nissan &quot;bus&quot; (van with more than 3 rows of seats)
|-
| 5B4 || Workhorse Custom Chassis, LLC incomplete vehicle (RV chassis)
|-
| 5CD || Indian Motorcycle Company of America (Gilroy, CA)
|-
| 5CJ || Western Star Trucks (incomplete vehicle)
|-
| 5CK || Western Star Trucks (truck)
|-
| 5CX || Shelby Series 1
|-
| 5DF || Thomas Dennis Company LLC
|-
| 5DG || Terex Advance Mixer, Inc. (Formerly Advance Mixer, Inc.) (truck)
|-
| 5EH || Excelsior-Henderson Motorcycle
|-
| 5EO || Cottrell (truck trailer)
|-
| 5FC || Columbia Vehicle Group (Columbia, Tomberlin) (low-speed vehicles)
|-
| 5FN || Honda MPV/SUV made by Honda Manufacturing of Alabama
|-
| 5FP || Honda truck made by Honda Manufacturing of Alabama
|-
| 5FR || Acura SUV made by Honda Manufacturing of Alabama 
|-
| 5FT || Feeling Trailers
|-
| 5FY || New Flyer
|-
| 5GA || Buick MPV/SUV
|-
| 5GD || Daewoo G2X
|-
| 5GN || Hummer H3T
|-
| 5GR || Hummer H2
|-
| 5GT || Hummer H3
|-
| 5GZ || Saturn MPV/SUV
|-
| 5G8 || Holden Volt
|-
| 5HD || Harley-Davidson for export markets
|-
| 5HT || Heil Trailer (truck trailer)
|-
| 5J1 || Big Dog Motorcycles (Mid-2002 – )
|-
| 5J5 || Club Car (low-speed vehicle)
|-
| 5J6 || Honda SUV made by Honda of America Mfg. in Ohio
|-
| 5J8 || Acura SUV made by Honda of America Mfg. in Ohio
|-
| 5KB || Honda car made by Honda Manufacturing of Alabama
|-
| 5KJ || Western Star Trucks (truck)
|-
| 5KK || Western Star Trucks (incomplete vehicle)
|-
| 5KM || Vento Motorcycles
|-
| 5KT || Karavan Trailers
|-
| 5L1 || [[../Ford/VIN Codes|Lincoln]] SUV - Limousine (2004–2009)
|-
| 5L5 || American IronHorse Motorcycle
|-
| 5LD || Ford &amp; Lincoln incomplete vehicle – limousine (2010–2014)
|-
| 5LM || [[../Ford/VIN Codes|Lincoln]] SUV
|-
| 5LT || [[../Ford/VIN Codes|Lincoln]] truck
|-
| 5MZ || Buell Motorcycle Company for export markets
|-
| 5N1 || Nissan &amp; Infiniti SUV
|-
| 5N3 || Infiniti SUV
|-
| 5NH || Forest River
|-
| 5NM || Hyundai SUV made by HMMA
|-
| 5NP || Hyundai car made by HMMA
|-
| 5NT || Hyundai truck made by HMMA
|-
| 5PV || Hino incomplete vehicle made by Hino Motors Manufacturing USA
|-
| 5RJ || International MXT made by Android Industries - Springfield LLC
|-
| 5RX || Heartland Recreational Vehicles
|-
| 5S3 || Saab 9-7X
|-
| 5SA || Suzuki Manufacturing of America Corp. (ATV)
|-
| 5SX || American LaFrance incomplete vehicle (Condor)
|-
| 5TB || [[../Toyota/VIN Codes|Toyota]] truck made by TMMI
|-
| 5TD || Toyota MPV/SUV &amp; Lexus TX made by TMMI
|-
| 5TE || Toyota truck made by NUMMI
|-
| 5TF || Toyota truck made by TMMTX
|-
| 5TU || Construction Trailer Specialist (truck trailer)
|-
| 5UM || BMW M car
|-
| 5UX || BMW SUV
|-
| 5VC || Autocar incomplete vehicle
|-
| 5VF || American Electric Vehicle Company (low-speed vehicle)
|-
| 5VK || Great Northern Trailer Works (truck trailer)
|-
| 5VP || Victory Motorcycles
|-
| 5V4 || Autocar truck
|-
| 5V8 || Vanguard National (truck trailer)
|-
| 5WE || IC Bus (incomplete vehicle - bus or truck)
|-
| 5XX || Kia car made by KMMG
|-
| 5XY || Kia/Hyundai SUV made by KMMG
|-
| 5YA || Indian Motorcycle Company (Kings Mountain, NC)
|-
| 5YF || Toyota car made by TMMMS
|-
| 5YJ || Tesla, Inc. passenger car (only used for US-built Model S and Model 3 starting from Nov, 1st 2021)
|-
| 5YM || BMW M SUV
|-
| 5YN || Cruise Car, Inc.
|-
| 5Y2 || Pontiac Vibe made by NUMMI
|-
| 5Y4 || Yamaha Motor Motor Mfg. Corp. of America (ATV, UTV)
|-
| 5ZT || Forest River (recreational vehicles)
|-
| 5ZU || Greenkraft (truck)
|-
| 5Z6 || Suzuki Equator (truck) made by Nissan
|-
| 50E || Lucid Motors passenger car
|-
| 50G || Karma Automotive
|-
| 50H || Norstar Company (truck trailers, truck beds)
|-
| 516 || Autocar truck
|-
| 51R || Brammo Motorcycles
|-
| 51T || Monaco RV LLC/Navistar RV LLC: Monaco (trailer)
|-
| 51U || Monaco RV LLC/Navistar RV LLC: Holiday Rambler 2010- (trailer)
|-
| 51V || Monaco RV LLC/Navistar RV LLC: R-Vision (trailer)
|-
| 51X || Monaco RV LLC/Navistar RV LLC: McKenzie (trailer)
|-
| 51Z || Monaco RV LLC/Navistar RV LLC: Monaco RV [Roadmaster Chassis] (incomplete vehicle) 
|-
| 522 || GreenGo Tek (low-speed vehicle)
|-
| 523 || VPG (The Vehicle Production Group)
|-
| 52C || GEM subsidiary of Polaris Inc.
|-
| 537 || Azure Dynamics Transit Connect Electric
|-
| 538 || Zero Motorcycles
|-
| 53G || Coda Automotive
|-
| 53T || Think North America in Elkhart, IN
|-
| 546 || EBR Motorcycles
|-
| 54C || Winnebago Industries travel trailer
|-
| 54D || Isuzu &amp; Chevrolet commercial trucks built by Spartan Motors/The Shyft Group
|-
| 54F || Rosenbauer Motors (incomplete vehicle)
|-
| 55S || Mercedes-Benz car
|-
| 56E || Armor Lite Trailer Mfg. (truck trailers)
|-
| 56K || Indian Motorcycle International, LLC (Polaris subsidiary)
|-
| 573 || Grand Design RV (truck trailer)
|-
| 57C || Maurer Manufacturing (truck trailer)
|-
| 57R || Oreion Motors
|-
| 57S || Lightning Motors Corp. (electric motorcycles)
|-
| 57W || Mobility Ventures
|-
| 57X || Polaris Slingshot
|-
| 58A || Lexus car made by TMMK (Lexus ES)
|-
| 6AB || MAN Australia
|-
| 6AM || Jayco Corp. (RVs)
|-
| 6F1 || Ford
|-
| 6F2 || Iveco Trucks Australia Ltd.
|-
| 6F4 || Nissan Motor Company Australia
|-
| 6F5 || Kenworth Australia
|-
| 6FM || Mack Trucks Australia
|-
| 6FP || [[../Ford/VIN Codes|Ford]] Australia
|-
| 6G1 || [[../GM/VIN Codes|General Motors]]-Holden (post Nov 2002), Chevrolet 2000-2013, Vauxhall Monaro &amp; VXR8 ('08-'17), Daewoo Statesman &amp; Veritas
|-
| 6G2 || [[../GM/VIN Codes|Pontiac]] made in Australia ('04-'06 GTO &amp; '08-'09 G8)
|-
| 6G3 || [[../GM/VIN Codes|General Motors]] Chevrolet Caprice PPV &amp; SS performance sedan 2014-2017, Middle East mkt. Chevrolet Caprice '14-'17
|-
| 6H8 || [[../GM/VIN Codes|General Motors]]-Holden (pre Nov 2002)
|-
| 6KT || BCI Bus
|-
| 6MM || Mitsubishi Motors Australia 
|-
| 6MP || Mercury Capri 1991-1994
|-
| 6T1 || [[../Toyota/VIN Codes|Toyota]] Motor Corporation Australia
|-
| 6T9 || Privately Imported car (VIN issued by Victoria) or Trailer in Australia
|-
| 6U9 || Privately Imported car in Australia
|-
| 6Y9/043 || Intertruck Distributors (NZ) Ltd. - International Trucks New Zealand
|-
| 6ZZ || Privately Imported car in Australia
|-
| 7AB || MAN New Zealand
|-
| 7AT || VIN assigned by the New Zealand Transport Authority Waka Kotahi from 29 November 2009
|-
| 7A1 || Mitsubishi New Zealand
|-
| 7A3 || Honda New Zealand
|-
| 7A4 || Toyota New Zealand
|-
| 7A5 || Ford New Zealand
|-
| 7A7 || Nissan New Zealand
|-
| 7A8 || VIN assigned by the New Zealand Transport Authority Waka Kotahi before 29 November 2009
|-
| 7B2 || Nissan Diesel bus New Zealand
|-
| 7FA || Honda SUV made by Honda Manufacturing of Indiana
|-
| 7FC || Rivian truck
|-
| 7F7 || Arcimoto, Inc. 
|-
| 7GZ || GMC incomplete vehicles (Savana cutaway) made by Navistar International/International Motors
|-
| 7G0 || Faraday Future
|- 
| 7G2 || Tesla, Inc. truck (used for Nevada-built Semi Trucks &amp; Texas-built Cybertruck)
|- 
| 7H4 || Hino truck
|-
| 7H8 || Cenntro Electric Group Limited low-speed vehicle
|- 
| 7JD || Volvo Cars SUV
|- 
| 7JR || Volvo Cars passenger car
|- 
| 7JS || White River Marine Group (trailer)
|- 
| 7JZ || Proterra From mid-2019 on
|- 
| 7KG || Vanderhall Motor Works
|- 
| 7KY || Dorsey (truck trailer)
|-
| 7MM || Mazda SUV made by MTMUS (Mazda-Toyota Joint Venture)
|- 
| 7MU || Toyota SUV made by MTMUS (Mazda-Toyota Joint Venture)
|-
| 7MW || Cenntro Electric Group Limited truck
|-
| 7MZ || HDK electric vehicles
|-
| 7NA || Navistar Defense/ND Defense
|- 
| 7NY || Lordstown Motors
|- 
| 7PD || Rivian SUV
|- 
| 7RZ || Electric Last Mile Solutions
|- 
| 7SA || Tesla, Inc. (US-built MPVs (e.g. Model X, Model Y))
|-
| 7SU || Blue Arc electric trucks made by The Shyft Group
|-
| 7SV || [[../Toyota/VIN Codes|Toyota]] SUV made by TMMTX
|-
| 7SX || Global Electric Motorcars (WAEV) 2022-
|- 
| 7SY || Polestar SUV
|-
| 7TN || Canoo
|-
| 7UU || Lucid Motors MPV/SUV
|-
| 7UZ || Kaufman Trailers (trailer)
|-
| 7VV || Ree Automotive
|-
| 7WA || Scout Motors (MPV)
|-
| 7WE || Bollinger Motors incomplete vehicle
|-
| 7XB || Denago EV Corporation (Low-Speed Vehicle)
|-
| 7YA || Hyundai &amp; Kia MPV/SUV made by HMGMA
|-
| 7ZJ || Meyers Manx, LLC (Manx EV Resorter) [Low Speed Vehicle]
|-
| 7Z0 || Zoox
|-
| 71T || Slate Auto (truck)
|-
| 71V || Slate Auto (MPV)
|-
| 722 || Isuzu North America Corp. (incomplete vehicle - medium duty)
|-
| 8AB || Mercedes Benz truck &amp; bus (Argentina)
|-
| 8AC || Mercedes Benz vans (for South America)
|-
| 8AD || Peugeot Argentina
|-
| 8AE || Peugeot van
|-
| 8AF || [[../Ford/VIN Codes|Ford]] Argentina
|-
| 8AG || [[../GM/VIN Codes|Chevrolet]] Argentina
|-
| 8AJ || [[../Toyota/VIN Codes|Toyota]] Argentina
|-
| 8AK || Suzuki Argentina
|-
| 8AN || Nissan Argentina
|-
| 8AP || Fiat Argentina
|-
| 8AT || Iveco Argentina
|-
| 8AW || Volkswagen Argentina
|-
| 8A1 || Renault Argentina
|-
| 8A3 || Scania Argentina
|-
| 8A7 || Minarelli S.A.
|-
| 8BB || Agrale Argentina S.A.
|-
| 8BC || Citroën Argentina
|-
| 8BN || Mercedes-Benz incomplete vehicle (North America)
|-
| 8BR || Mercedes-Benz &quot;bus&quot; (van with more than 3 rows of seats) (North America)
|-
| 8BT || Mercedes-Benz MPV (van with 2 or 3 rows of seats) (North America)
|-
| 8BU || Mercedes-Benz truck (cargo van with 1 row of seats) (North America)
|-
| 8CH || Honda motorcycle
|-
| 8C3 || Honda car/SUV
|-
| 8G1 || Automotores Franco Chilena S.A. Renault
|-
| 8GD || Automotores Franco Chilena S.A. Peugeot
|-
| 8GG || [[../GM/VIN Codes|Chevrolet]] Chile
|-
| 8LD || General Motors OBB - Chevrolet Ecuador
|-
| 8LF || Maresa (Mazda)
|-
| 8LG || Aymesa (Hyundai Motor &amp; Kia)
|-
| 8L4 || Great Wall Motors made by Ciudad del Auto (Ciauto)
|-
| 8XD || Ford Motor Venezuela
|-
| 8XJ || Mack de Venezuela C.A.
|-
| 8XV || Iveco Venezuela C.A.
|-
| 8Z1 || General Motors Venezolana C.A.
|-
| 829 || Industrias Quantum Motors S.A. (Bolivia)
|-
| 9BD || Fiat Brazil &amp; Dodge, Ram made by Fiat Brasil
|-
| 9BF || [[../Ford/VIN Codes|Ford]] Brazil
|-
| 9BG || [[../GM/VIN Codes|Chevrolet]] Brazil
|-
| 9BH || Hyundai Motor Brasil
|-
| 9BM || Mercedes-Benz Brazil car, SUV, commercial truck &amp; bus
|-
| 9BN || Mafersa
|-
| 9BR || [[../Toyota/VIN Codes|Toyota]] Brazil
|-
| 9BS || Scania Brazil
|-
| 9BU ||Gurgel Motores S.A. (defunct Brazilian automaker)
|-
| 9BV || Volvo Trucks Brazil
|-
| 9BW || Volkswagen Brazil
|-
| 9BY || Agrale S.A.
|-
| 9C2 || Moto Honda Da Amazonia Ltda.
|-
| 9C6 || Yamaha Motor Da Amazonia Ltda.
|-
| 9CD || Suzuki (motorcycles) assembled by J. Toledo Motos do Brasil
|-
| 9DF || Puma
|-
| 9DW || Kenworth &amp; Peterbilt trucks [incomplete vehicle] made by Volkswagen do Brasil
|-
| 9EZ || homemade or handbuilt vehicles
|-
| 92H || Origem Brazil
|-
| 932 || Harley-Davidson Brazil
|-
| 935 || Citroën Brazil
|-
| 936 || Peugeot Brazil
|-
| 937 || Dodge Dakota
|-
| 93C || Chevrolet SUV [Tracker] or pickup [Tornado, Montana, S10] (sold in Mexico, made in Brazil)
|-
| 93H || [[../Honda/VIN Codes|Honda]] Brazil car/SUV
|-
| 93K || Volvo Trucks Brazil
|-
| 93P || Volare
|-
| 93S || Navistar International
|-
| 93R || [[../Toyota/VIN Codes|Toyota]] Brazil
|-
| 93U || Audi Brazil 1999–2006
|-
| 93W || Fiat Ducato made by Iveco 2000–2016
|-
| 93V || Navistar International
|-
| 93X || Souza Ramos – Mitsubishi Motors / Suzuki Jimny
|-
| 93Y || Renault Brazil
|-
| 93Z || Iveco
|-
| 94D || Nissan Brazil
|-
| 94N || RWM Brazil
|-
| 94T || Troller Veículos Especiais
|-
| 95P || CAOA Hyundai &amp; CAOA Chery
|-
| 95V || Dafra Motos (motorscooters from SYM) &amp; Ducati, KTM, &amp; MV Agusta assembled by Dafra
|-
| 95V || BMW motorcycles assembled by Dafra Motos 2009–2016
|-
| 95Z || Buell Motorcycle Company assembled by Harley-Davidson Brazil
|-
| 953 || VW Truck &amp; Bus / MAN Truck &amp; Bus
|-
| 96P || Kawasaki
|-
| 97N || Triumph Motorcycles Ltd.
|-
| 988 || Jeep, Ram [Rampage], and Fiat [Toro] (made at the Goiana plant)
|-
| 98M || BMW car/SUV
|-
| 98P || DAF Trucks
|-
| 98R || Chery
|-
| 99A || Audi 2016-
|-
| 99H || Shineray
|-
| 99J || Jaguar Land Rover
|-
| 99K || Haojue &amp; Kymco assembled by JTZ Indústria e Comércio de Motos
|-
| 99L || BYD
|-
| 99Z || BMW Motorrad (Motorcycle assembled by BMW 2017-)
|-
| 9FB || Renault Colombia (Sofasa)
|-
| 9FC || Compañía Colombiana Automotriz S.A. (Mazda)
|-
| 9GA || [[../GM/VIN Codes|Chevrolet]] Colombia (GM Colmotores S.A.)
|-
| 9UJ || Chery assembled by Chery Socma S.A. (Uruguay)
|-
| 9UK || Lifan (Uruguay)
|-
| 9UT || Dongfeng trucks made by Nordex S.A.
|-
| 9UW || Kia made by Nordex S.A.
|-
| 9VC || Fiat made by Nordex S.A. (Scudo, 2025 Titano)
|-
| 9V7 || Citroen made by Nordex S.A. (Jumpy)
|-
| 9V8 || Peugeot made by Nordex S.A. (Expert)
|}

==References==
{{reflist}}
{{BookCat}}</text>
      <sha1>f33zf31u4qk94cya9ad5r7kdkx7h5b0</sha1>
    </revision>
  </page>
  <page>
    <title>Radiation Oncology/Prostate/Protons</title>
    <ns>0</ns>
    <id>142789</id>
    <revision>
      <id>4675713</id>
      <parentid>3627712</parentid>
      <timestamp>2026-10-12T12:05:35Z</timestamp>
      <contributor>
        <username>Jcb</username>
        <id>90773</id>
      </contributor>
      <origin>4675713</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="26878" sha1="ak44entec7clukmonxio26hb19cpdmi" xml:space="preserve">{{:Radiation Oncology/Prostate:TOC}}


&lt;big&gt;'''Proton Therapy in Prostate Cancer'''&lt;/big&gt;


==Outcome==
===Primary Treatment===
*'''Kobe University (Hyogo)''' 
**'''2007''' (2003-2004) {{PMID|17482768}} -- &quot;Acute morbidity of proton therapy for prostate cancer: the Hyogo Ion Beam Medical Center experience.&quot; (Mayahara H, Int J Radiat Oncol Biol Phys. 2007 Oct 1;69(2):434-43. Epub 2007 May 7.)
***Retrospective. 287 patients, cT1-T4N0 PCA. Treated with 190-230 MeV protons, lateral-opposed technique, 74 GyE. Acute toxicity evaluated by NCI CTC2.0. Neoadjuvant AST 71%
***Acute Toxicity: GI 0% G2+ , GU 39% G2 and 1% G3. Most relieved by alpha-1 blocker
***Predictors for acute toxicity: large CTV, AST
***Conclusion: Low incidence of GI toxicity, comparable GU toxicity to photons
**'''2004''' (2001) {{PMID|15289722}} -- &quot;Experience with conformal proton therapy for early prostate cancer.&quot; (Hara I, Am J Clin Oncol. 2004 Aug;27(4):323-7.)
***Initial Phase I. 16 patients, T1-T2b. Median F/U 12 months
***Outcome: 4/16 patients normal PSA, no change. 12/16 PSA CR by PSA; no PSA failures
***Toxicity: No acute Grade 3-4 toxicity
***Outcome: Minimum toxicity and good short-term responses

*'''Loma Linda''' (1991-1997)
**'''2004''' {{PMID|15491710}} -- &quot;Influence of patient age on biochemical freedom from disease in patients undergoing conformal proton radiotherapy of organ-confined prostate cancer.&quot; (Rossi CJ, Urology. 2004 Oct;64(4):729-32.)
***Retrospective. 1038 patients with cT1-T2c (AJCC 1992), definitive conformal protons. &lt;60 years (12%) vs. &gt;60 years (88%), comparable distribution. Median F/U 5.2 years
***Outcome: 5-year bNED &lt;60 82% vs. &gt;60 75% (NS)
***Conclusion: Patient age does not impact bNED
**'''2004''' {{PMID|15145147}} -- &quot;Proton therapy for prostate cancer: the initial Loma Linda University experience.&quot; (Slater JD, Int J Radiat Oncol Biol Phys. 2004 Jun 1;59(2):348-52.)
***Retrospective. 1255 patients with Stage Ia-III, no prior surgery or AST. Photons 45 Gy + proton boost 30/15 CGE to prostate/pelvic LN n=731, protons only 74/37 CGE to prostate/SV n=524. Protons delivered opposed laterals, typically one field/day. Water balloon in rectum. Median F/U 5.2 years
***Outcome: 5-year bNED 73%, if PSA &lt;=4.0 90%
***Toxicity: G3 late toxicity 1%, G4 late toxicity 0.2%; no difference between mixed treatment vs protons only
***Conclusion: Conformal PRT comparable to other local therapy, with minimal toxicity
**'''2002''' (1991-1996) {{PMID|10650829}} -- &quot;Value and perspectives of proton radiation therapy for limited stage prostate cancer.&quot; (Schulte RW, Strahlenther Onkol. 2000 Jan;176(1):3-8.)
***Retrospective. 911 patients with limited stage PCA.
***Outcome: 5-year bNED 82%
***Toxicity: no Grade 3/4; Grade 2 rectal 3.5%, Grade 2 bladder 5.4%
***Conclusion: Improved bNED and better late effects
**'''1999''' {{PMID|10394406}} -- &quot;Conformal proton beam therapy of prostate cancer--update on the Loma Linda University medical center experience.&quot; (Rossi CJ, Strahlenther Onkol. 1999 Jun;175 Suppl 2:82-4.)
***Retrospective. 643 patients with localized PCA, protons alone or photons/protons. Dose 74-75 CGE
***Outcome: 5-year bNED 79%, better in &quot;early&quot; (T1b-2b, PSA &lt;15) vs. &quot;advanced&quot; (PSA &gt;15, or T2c-T4)
***Toxicity: minimal proctitis 21%, greater toxicity &lt;1%
***Conclusion: Conformal proton beam high rate of response, minimal toxicity
**'''1999''' {{PMID|10223493}} -- &quot;Conformal proton therapy for early-stage prostate cancer.&quot; (Slater JD, Urology. 1999 May;53(5):978-84.)
***Retrospective. 319 patients, T1-T2b and PSA &lt;15, protons to 74-75 CGE. No hormones until disease progression
***Outcome: 5-year bNED 88%, clinical NED 97%
***Conclusion: Comparable outcomes to radical prostatectomy, with no significant toxicity

*'''Tsukuba; 1993''' (1983-1990) {{PMID|8380147}} -- &quot;Clinical results of fractionated proton therapy.&quot; (Tsujii H, Int J Radiat Oncol Biol Phys. 1993 Jan;25(1):49-60.)
**Phase I-II. 147 patients treated, various primaries
**Conclusion: Potential advantage in lung, esophageal, liver, uterine cervix, prostate, and head and neck malignancies; possible value in treatment of high-grade gliomas, and gastric, urinary bladder, and pediatric tumors.

===Proton Boost===
*'''National Cancer Center Hospital East; 2005''' (Japan)(2001-2003) {{PMID|16314345}} -- &quot;Phase II feasibility study of high-dose radiotherapy for prostate cancer using proton boost therapy: first clinical trial of proton beam therapy for prostate cancer in Japan.&quot; (Nihei K, Jpn J Clin Oncol. 2005 Dec;35(12):745-52. Epub 2005 Nov 28.)
**Phase II. 30 patients, cT1-3N0. RT photon to prostate &amp; SV 50/25 and proton boost 26/13 GyE. Boost PTV = prostate + 5mm + 5mm penumbra margin. Lateral opposed beams. Photon treatment to prostate/SV. PTV = prostate + 10 mm margin + 5 mm penumbra margin. 240 degree dynamic conformal arc. Hormonal therapy allowed. Median F/U 2.5 years
**Toxicity: no acute or late Grade 3 GI/GU toxicity. Acute G1-2 GI toxicity 57%, acute G1-G2 GU toxicity 80%. Late G1-2 GI toxicity 37%, G1-G2 GU toxicity 17%
**Conclusion: Proton boost is feasible, multi-institutional PII trial in progress

*'''PROG 95-09''' (1996-1999) -- Proton/photon 70.2 Gy vs. 79.2 Gy
**Randomized. 2 institutions (Harvard and Loma Linda). 392 patients, stage T1b-T2b, PSA &lt;15 ng/mL (median PSA 6.3). Arm 1) proton boost 19.8/11 GyE followed by photons 50.4/28 vs. Arm 2) proton boost 28.8/16 followed by photons 50.4/28. Proton CTV = prostate + 5 mm margin. PTV = CTV + 7-10 mm. Loma Linda used opposed lateral beams, 250 MeV protons; Harvard used perineal boost, 160 MeV protons. Rectal Lucite probe, inflated with 25-50 mL saline. Photons were 4F plan, photon CTV = prostate/SV + 10 mm margin. 
**'''5-years; 2005''' {{PMID|16160131}} -- &quot;Comparison of conventional-dose vs high-dose conformal radiation therapy in clinically localized adenocarcinoma of the prostate: a randomized controlled trial.&quot; (Zietman AL, JAMA. 2005 Sep 14;294(10):1233-9.) Median F/U 5.5 years
***Outcome: 5-year bNED 70.2 Gy 61% vs. 79.2 Gy 80% (SS), 50% reduction in risk of failure. LC (defined as PSA &lt;1.0) 48% vs. 67% (SS) No difference in OS 97% vs 96% (NS)
***Risk stratification: low risk (PSA &lt;10, stage &lt;=T2a, GS &lt;7) 60% vs. 80% (SS); high risk 63% vs. 79% (SS). Contemporary intermediate risk 63% vs. 81% (SS), but contemporary high risk (NS, but small number) 
***Late toxicity: Grade 3+ 70.2 Gy 1% vs. 79.2 2%; GU Grade 2 18% vs. 20% (NS), GI Grade 2 8% vs. 17% (SS). Most GI toxicity by 3 years; GU toxicity continuous
***Conclusion: Men with clinically localized PCA have better bNED with high dose, without worse severe toxicity
**'''10-years; 2010''' {{PMID|20124169}} -- &quot;Randomized Trial Comparing Conventional-Dose With High-Dose Conformal Radiation Therapy in Early-Stage Adenocarcinoma of the Prostate: Long-Term Results From Proton Radiation Oncology Group/American College of Radiology 95-09.&quot; (Zietman AL, J Clin Oncol. 2010 Mar 1;28(7):1106-11.) Median F/U 8.9 years
***Outcome: 10-year ASTRO (backdating) bPFS low-dose 68% vs. high-dose 83% (SS). For low-risk disease 72% vs 93% (SS); for intermediate-risk 58% vs. 70% (p=0.06). No difference in OS (78% vs 83%)
***Toxicity: Late Grade 2+ low-dose 29% vs. high-dose 39% (SS); Grade 3+ 2% in both arms (NS)
***Conclusion: Long-term advantage for high dose in low/intermediate risk PCA patients, with comparable Grade 3 toxicity


*'''Loma Linda''' (1991-1997)
**'''2004''' {{PMID|15145147}} -- &quot;Proton therapy for prostate cancer: the initial Loma Linda University experience.&quot; (Slater JD, Int J Radiat Oncol Biol Phys. 2004 Jun 1;59(2):348-52.)
***Retrospective. 1255 patients with Stage Ia-III, no prior surgery or AST. Photons 45 Gy + proton boost 30/15 CGE to prostate/pelvic LN n=731, protons only 74/37 CGE to prostate/SV n=524. Protons delivered opposed laterals, typically one field/day. Water balloon in rectum. Median F/U 5.2 years
***Outcome: 5-year bNED 73%, if PSA &lt;=4.0 90%
***Toxicity: G3 late toxicity 1%, G4 late toxicity 0.2%; no difference between mixed treatment vs protons only
***Conclusion: Conformal PRT comparable to other local therapy, with minimal toxicity
**'''1998''' {{PMID|9788407}} -- &quot;Conformal proton therapy for prostate carcinoma.&quot; (Slater JD, Int J Radiat Oncol Biol Phys. 1998 Sep 1;42(2):299-304.)
***Retrospective. 643 patients, localized PCA. Protons +/- photons, 74-75 CGE
***Outcome: 5-year clinical NED 89%; bNED PSA &lt;4 100%, PSA 4-10 89%, PSA 10-20 72%, PSA &gt;20 53%; nadir &lt;0.5 91%, 0.5-1.0 79%, &gt;1.0 40%
***Toxicity: minimal proctitis 21%, severe proctitis &lt;1%
***Conclusion: Minimal toxicity and excellent DFS with low initial PSA
**'''1997''' (1991-1993) {{PMID|9054873}} -- &quot;Combined proton and photon conformal radiation therapy for locally advanced carcinoma of the prostate: preliminary results of a phase I/II study.&quot; (Yonemoto LT, Int J Radiat Oncol Biol Phys. 1997 Jan 1;37(1):21-9.)
***Phase I/II. 106 patients, T2b-T4Nx. Proton 30/15 CGE prostate boost via opposed lateral fields, followed by photons 45/25 Gy to pelvis. No break. Target prostate/SV + 0.7 cm prescribed at 90% isodose line. 250 MeV proton beam. Median F/U 1.7 years
***Toxicity: 2-year Grade 3-4 0%, Grade 1-2 12% (8% rectal, 4% urinary)
***Outcome: 2-year PSA normalization: PSA 4-10 96%, PSA 10-20 97%, PSA &gt;20 63%
***Conclusion: Low incidence of side-effects, despite 75 CGE dose

*'''Harvard''' (1982-1992) -- Proton (dose escalated) vs. photon boost
**Randomized. 202 patients, Stage T3-T4Nx,0-2. Standard photons 50.4 Gy four-field, then Arm 1) Conformal protons 25.2 CGE (total 75.6 CGE) vs. Arm 2) Photons 16.8 Gy (total 67.2 Gy). Median F/U 5.1 years
**'''1993''' {{PMID|8514551}} -- &quot;Late rectal bleeding following combined X-ray and proton high dose irradiation for patients with stages T3-T4 prostate carcinoma&quot; (Benk VA, Int J Radiat Oncol Biol Phys. 1993 Jun 15;26(3):551-7.) Median F/U 3.7 years
***Rectal bleeding (none Grade 3-4): high dose 34% vs. low dose 16% (SS)
***DVH evaluation: significant bleeding risk if &gt;40% anterior rectum gets &gt;75 CGE
**'''1995''' {{PMID|7721636}} -- &quot;Advanced prostate cancer: the results of a randomized comparative trial of high dose irradiation boosting with conformal protons compared with conventional dose irradiation using photons alone.&quot; (Shipley WU, Int J Radiat Oncol Biol Phys. 1995 Apr 30;32(1):3-12.)
***Outcome: 5-year LC photon+proton 92% vs. photons 80% (NS), no difference in OS, DSS, TRFS. GS 4/5 patients 94% vs. 64% (SS)
***Toxicity: Rectal bleeding photon+proton 32% vs. photons 12% (SS), urethral stricture 19% vs. 8% (p=0.07)
***Conclusion: Boosting dose with protons increased LC in poorly differentiated tumors, but also worsened late toxicity
**'''2002''' {{PMID|11743288}} -- &quot;Late normal tissue sequelae in the second decade after high dose radiation therapy with combined photons and conformal protons for locally advanced prostate cancer.&quot; (Gardner BG, J Urol. 2002 Jan;167(1):123-6.)
***Retrospective. 39/42 patients alive from original cohort of 167 patients, T3-T4, treated with 4 field box photons to 50.4 Gy, follower by perineal proton boost to 27 Gy in 11 fractions. Median F/U 13.1 years
***GU toxicity: G2+ GU 59% at 15 years but persisted in 18%. G2+ hematuria 21% at 5 years, 47% at 15 years. G3+ hematuria 3% and 8%. Urethral stricture 10%, urinary incontinence 8% (strongly associated with prior/subsequent prostate surgery)
***GI toxicity: G2+ GI 13% at 15 years; G1 rectal bleeding in 41%
***Conclusion: High dose RT results in high rate of low-grade rectal bleeding, but low rate of G2+ GI toxicity; stable after 5 years. GU morbidity continues to worsen over time, but high grade uncommon

*'''Harvard''' (1976-1979) 
**'''1983''' {{PMID|6299503}} -- &quot;Protons or megavoltage X-rays as boost therapy for patients irradiated for localized prostatic carcinoma. An early phase I/II comparison.&quot; (Duttenhaver JR, Cancer. 1983 May 1;51(9):1599-604.)
***Phase I/II. 180 patients (Photons n=116, photons + proton boost n=64). Proton beam 160 MeV, boost single perineal portal. Photon dose 67 Gy vs. proton dose 74 Gy.
***Outcome: No difference in LRC, DFS, or OS
***Toxicity: no difference
***Conclusion: 10% increase in dose, but minimal complications. Plan to perform an RCT
**'''1979''' {{PMID|107338}} -- &quot;Proton radiation as boost therapy for localized prostatic carcinoma.&quot; (Shipley WU, JAMA. 1979 May 4;241(18):1912-5.)
***Retrospective. Initial report. 17 patients with localized PCA. Proton boost 20-25 Gy. F/U 12-27 months
***Outcome: no significant rectal toxicity, 2/17 urethral strictures, 16/17 locally controlled
***Conclusion: Proton boost feasible

==Treatment Techniques==
*'''Geneva, Switzerland'''
**'''2009''' {{PMID|19740429}} -- &quot;RapidArc, intensity modulated photon and proton techniques for recurrent prostate cancer in previously irradiated patients: a treatment planning comparison study.&quot; (Weber DC, Radiat Oncol. 2009 Sep 9;4(1):34.)
***Treatment planning. RapidArc vs IMRT vs IMPT. 7 patients with recurrent PC after RT. Dose 56/14
***Outcome: GTV V95% RA 93% vs. IMRT 89% vs. IMPT 90%, PTV V95% RA 84% vs. IMRT 77% vs. IMPT 86%
***Toxicity: Urethra V35 RA 5% vs. IMRT 10% vs. IMPT 4%
***Conclusion: RapidArc and IMPT improved indices over IMRT 
**'''2001''' {{PMID|11770521}} -- &quot;New techniques in hadrontherapy: intensity modulated proton beams.&quot; (Cella L, Phys Med. 2001;17 Suppl 1:100-2.)
***Comparative planning between intensity modulated XRT and PRT
***Outcome: Equally homogenous dose of PTV, equally low NTCPs, but less integral dose and reduced low-to-medium dose for protons
**'''2001''' {{PMID|11163518}} -- &quot;Potential role of intensity modulated proton beams in prostate cancer radiotherapy.&quot; (Cella L, Int J Radiat Oncol Biol Phys. 2001 Jan 1;49(1):217-23.)
***Four treatment plans to deliver 81 Gy: 1) 3D-CRT 18 MV 6 fields, 2) 214 MeV protons 2 fields, 3) IMRT 15 MV 5 fields, 4) 177-200 MeV IMPT 5 fields. Further dose escalation to 99 Gy
***Conclusion: Both IMRT and IMPT could optimize target dose and NTCP constraints; protons reduced low-to-medium dose and improved PTV dose heterogeneity

*'''Florida'''
**'''2009''' {{PMID|19619961}} -- &quot;Dosimetric Study of Pelvic Proton Radiotherapy for High-Risk Prostate Cancer.&quot; (Chera BS, Int J Radiat Oncol Biol Phys. 2009 Jul 18. [Epub ahead of print])
***Treatment planning. 5 high-risk prostate patients, treated to prostate, proximal SV, and pelvic LNs. IMRT vs IMRT+PT boost vs PT. Prescribed to 46 CGE pelvis and 78 CGE prostate/SV
***Outcome: PT plans reduced mean dose to rectum, rectal wall, bladder, bladder wall, small bowel, and pelvis by 40-70%
***Conclusion: PT significantly reduced dose to normal tissues in pelvis, while maintaining adequate target coverage compared with IMRT 
**'''2007''' {{PMID|17967305}} -- &quot;Rectal dose-volume differences using proton radiotherapy and a rectal balloon or water alone for the treatment of prostate cancer.&quot; (Vargas C, Int J Radiat Oncol Biol Phys. 2007 Nov 15;69(4):1110-6.)
***Retrospective. 30 proton plans for 15 patients, T1-2N0, both CT and MRI with rectal balloon (100ml saline) or water alone (100ml saline with contrast). Doses 78-82 GE to PTV. Planning done with Eclipse
***Conclusion: Rectum and rectal wall doses were low, regardless of water or rectal balloon; small difference for few patients
**'''2007''' {{PMID|17904306}} -- &quot;Dose-Volume Comparison of Proton Therapy and Intensity-Modulated Radiotherapy for Prostate Cancer.&quot; (Vargas C, Int J Radiat Oncol Biol Phys. 2007 Sep 26 [Epub ahead of print])
***Retrospective. First 10 patients treated on Phase II low-risk prostate protocol. Comparison between proton plans and IMRT plans. Dose to 78 GE
***Conclusion: Proton therapy reduced dose to rectum and bladder, while maintaining excellent PTV coverage

*'''NCC Korea''' 
**'''2009''' {{PMID|19647628}} -- &quot;Characteristics of movement-induced dose reduction in target volume: a comparison between photon and proton beam treatment.&quot; (Yoon M, Med Dosim. 2009 Fall;34(3):191-201. Epub 2008 Sep 24.)
***Treatment planning. Target displaced 3mm - 20 mm in a scanned phantom. Photon vs proton comparison
***Outcome: 6mm lateral movement: coverage worse by 9% for protons and 1% for photons; 15 mm lateral movement: coverage worse by 34% and minimally for photons. EUD and homogeneity index similar characteristics
***Conclusion: Movement-induced dose reduction differs significantly for proton and photon beams
**'''2009''' {{PMID|19616746}} -- &quot;Microscopic gold particle-based fiducial markers for proton therapy of prostate cancer.&quot; (Lim YK, Int J Radiat Oncol Biol Phys. 2009 Aug 1;74(5):1609-16.)
***Visibility comparison, two gold particles
***Outcome: x-ray - good visibility, proton beam - &lt;5% dose distortion. CT artifacts reduced for gold particle mixture
***Conclusion: Mixture of gold particles and polymers have excellent potential

*'''MD Anderson'''
**'''2009''' {{PMID|19550003}} -- &quot;Comparison of surface doses from spot scanning and passively scattered proton therapy beams.&quot; (Arjomandy B, Phys Med Biol. 2009 Jul 21;54(14):N295-302. Epub 2009 Jun 23.)
***Treatment planning. Proton plan, planned with scanning beam with scattered beam. Surface dose in phantom measured to estimate skin dose
***Outcome: Scanning beam dose lower by ~12% compared with scattered beam, equivalent to 4 CGE during 76 CGE course
**'''2009''' {{PMID|19427561}} -- &quot;Risk of secondary malignant neoplasms from proton therapy and intensity-modulated x-ray therapy for early-stage prostate cancer.&quot; (Fontenont JD, Int J Radiat Oncol Biol Phys. 2009 Jun 1;74(2):616-22.)
***Treatment planning. Proton plan vs 6-MV IMRT plan for 3 patients with early stage PCA. Primary doses determined from treatment plans, secondary doses from Monte Carlo and measured data. Risk of second malignancy estimated on organ-by-organ basis
***Outcome: PT reduced risk of SMN by 26%-39% compared with IMRT, due to substantial sparing of rectum/bladder
***Conclusion: PT can reduce risk of second malignancies in prostate patients
**'''2009''' {{PMID|19223836}} -- &quot;Dose perturbations from implanted helical gold markers in proton therapy of prostate cancer.&quot; (Giebeler A, J Appl Clin Med Phys. 2009 Jan 27;10(1):2875.)
***Gold fiducial marker evaluation. Small (0.35 mm), medium (0.75 mm), and large (1.15mm) marker with length of 10 mm implanted in phantom. Monte Carlo simulation
***Outcome: Perturbation of dose large marker 31%, medium marker 23%, so not well suited. Small marker too fragile for transrectal implantation
**'''2007''' {{PMID|17505081}} -- &quot;Monte Carlo simulations of the dosimetric impact of radiopaque fiducial markers for proton radiotherapy of the prostate.&quot; (Newhauser W, Phys Med Biol. 2007 Jun 7;52(11):2937-52. Epub 2007 May 2.)
***Compared various types of implantable markers for visibility on kV imagins, and reviewed dosimetry models by Monte Carlo
***Outcome: gold and stainless steel markers visible, titanium not so much. Stainless steel and titanium didn't perturb beam much, gold large shadow
***Conclusion: 0.9 mm diameter, 3.1 mm long stainless steel marker has good visibility on kV and &lt;8% beam pertuberance
**'''2007''' {{PMID|17236979}} -- &quot;Effect of anatomic motion on proton therapy dose distributions in prostate cancer treatment.&quot; (Zhang X, Int J Radiat Oncol Biol Phys. 2007 Feb 1;67(2):620-9.)
***Dosimetric impact, 10 patients, 8 daily CT scans each. Comparison of IMRT and proton dosimetry
***Conclusion: Interfractional anatomic motion has similar impact on both modalities

*'''Wollongong, Australia; 2008''' {{PMID|19239059}} -- &quot;A comparison of proton therapy and IMRT treatment plans for prostate radiotherapy.&quot; (Dowdell SJ, Australas Phys Eng Sci Med. 2008 Dec;31(4):325-31.)
**Treatment planning. Passive vs IMPT vs 7-F IMRT step-and-shoot vs 7-F IMRT sliding window. 78 CGE
**Outcome: Homogeneity and rectal sparing best for IMPT
**Conclusion: PT is suitable treatment option

*'''Harvard'''
**'''2007''' {{PMID|17513063}} -- &quot;Radiotherapy treatment of early-stage prostate cancer with IMRT and protons: a treatment planning comparison.&quot; (Trofimov A, Int J Radiat Oncol Biol Phys. 2007 Oct 1;69(2):444-53. Epub 2007 May 21.)
***Retrospective. 10 patients with early-stage PCA. Treated with 3D-CPT (two parallel-opposed lateral fields) and IMRT (7 coplanar fields). Dose 79.2 Gy/CGE
***Outcome: 98% of PTV received prescription dose. IMRT better dose conformity, 3D-CPT better dose homogeneity. 
***Normal organs: Bladder dosimetry: V30 better with protons, V70 better with IMRT. Rectal dosimetry: V70 comparable
***Conclusion: Above 60 Gy, IMRT better than protons for bladder, rectum comparable. Doses &lt;50% significantly better with protons
***Comment from PSI ({{PMID|17967323}})
**'''1996''' {{PMID|8948358}} -- &quot;Conformal irradiation of the prostate: estimating long-term rectal bleeding risk using dose-volume histograms.&quot; (Hartford AC, Int J Radiat Oncol Biol Phys. 1996 Oct 1;36(3):721-30.)
***41 patients treated with photons + perineal boost. Review of DVH for anterior rectal wall. Min F/U 4 years
***Toxicity: 14/41 (34%) rectal bleeding. Found dose-volume relationship between 60 - 75 CGE; development of low/moderate/high risk groups
**'''1990''' {{PMID|2157240}} -- &quot;Considerations in fractionated proton radiation therapy: clinical potential and results.&quot; (Austin-Seymour M, Radiother Oncol. 1990 Jan;17(1):29-35.)
***Comparative evaluation of X-ray and proton plans

*'''Paul Scherrer Institut'''
**'''2007''' {{PMID|17459608}} -- &quot;The impact of dose escalation on secondary cancer risk after radiotherapy of prostate cancer.&quot; (Schneider U, Int J Radiat Oncol Biol Phys. 2007 Jul 1;68(3):892-7. Epub 2007 Apr 24.)
***23 patient plans. Comparison of TCP and NTCP for 3D-CRT (n=7), 6 MV or 15 MV IMRT (n=8), and spot-scanned proton RT (n=8). Doses modeled 70 - 100 Gy, baseline 70 Gy 3D-CRT
***Outcome: Secondary cancer risk compared with 70 Gy 3D-CRT: 6 MV IMRT +18%, 15 MV IMRT +25%, spot-scanned protons -41%
***Conclusion: Spot-scanned protons can halve risk of secondary cancers with dose escalation
**'''2006''' {{PMID|17072522}} -- &quot;The impact of IMRT and proton radiotherapy on secondary cancer incidence.&quot; (Schneider U, Strahlenther Onkol. 2006 Nov;182(11):647-52.)
***30 patient plans. 15 MV 3D-CRT (n=11), 6 MV IMRT (n=11), spot-scanned protons (n=8). Secondary cancer risk estimated based on organ equivalent dose (OED)
***Outcome: Secondary cancer risk compared with 15 MV 3D-CRT: 6 MV IMRT +15%, 15 MV IMRT +20%, 18 MV IMRT 60%, spot-scanned protons -50%
***Conclusion: IMRT risk not as dramatic as expected, particularly at 6 MV. Spot-scanned protons treatment of choice
**'''2004''' {{PMID|15587667}} -- &quot;Treatment planning and verification of proton therapy using spot scanning: initial experiences.&quot; (Lomax AJ, Med Phys. 2004 Nov;31(11):3150-7.)
***Overview of 160 patients treated with spot-scanning, including some prostates. Mean 3 beams per plan, with 200-45,000 Bragg peaks per field. Treatment time few seconds to 20-25 minutes
***Mean width of beam at Bragg peak ~8mm; Precision: orthogonal +/- 1mm, range +/- 1.5 mm

*'''Loma Linda'''
**'''2006''' {{PMID|16551129}} -- &quot;Innovative strategies for image-guided proton treatment of prostate cancer.&quot; (Schulte RW, Technol Cancer Res Treat. 2006 Apr;5(2):91-100.)
***Review of rationale for reduction of high dose PTV margins
**'''2006''' {{PMID|16488552}} -- &quot;Patient tolerance of rectal balloons in conformal radiation treatment of prostate cancer.&quot; (Ronson BB, Int J Radiat Oncol Biol Phys. 2006 Apr 1;64(5):1367-70. Epub 2006 Feb 20.)
***Retrospective. 3561 patients, protons for prostate/SV and photon pelvis as necessary
***Outcome: 98% tolerated balloon throughout treatment, 2% declined balloon for at least one treatment but tolerated it on average for 85% of their treatments. Better tolerance if protons alone 99.5% vs combination 95.7% (SS)
***Conclusion: Intrarectal balloons well tolerated
**'''2003''' {{PMID|14529309}} -- &quot;Range, range modulation, and field radius requirements for proton therapy of prostate cancer.&quot; (Moyers MF, Technol Cancer Res Treat. 2003 Oct;2(5):445-7.)
***Analysis of 240 treatment fields from &gt;5,000 patients treated
***Range typically &lt;290 mm water, modulation width &lt;120 mm, radius &lt;75 mm

*'''Cambridge''' (UK) {{PMID|16510958}} -- &quot;Margins for treatment planning of proton therapy.&quot; (Thomas SJ, Phys Med Biol. 2006 Mar 21;51(6):1491-501. Epub 2006 Mar 1.)
**Evaluation of margins for H&amp;N and prostate plans, for single field, parallel opposed fields, and four fields
**Good dose distributions can be obtained with one or two fields

*'''Vienna; 2005''' (Austria) {{PMID|15995838}} -- &quot;Comparative treatment planning on localized prostate carcinoma conformal photon- versus proton-based radiotherapy.&quot; (Mock U, Strahlenther Onkol. 2005 Jul;181(7):448-55.)
**Comparison. 5 patients. 3D proton plan (2 lateral beams) vs. 3D conformal photons (4 field box) vs. IMRT (seven beams). PTV = CTV + 5 mm. Total dose 70 Gy.
**Outcome: PTV: similar dose distribution. Conformity indices photon 1.4-1.5, proton 1.1-1.4. OAR received more dose (&gt;=1.7x) with photons, mainly at low and medium dose levels
**Conclusion: PTV comparable, for OAR 2 field protons &gt; IMRT &gt; 3D-CRT

*'''Alberta; 2002''' (Canada) {{PMID|11865989}} -- &quot;Intensity and energy modulated radiotherapy with proton beams: variables affecting optimal prostate plan.&quot; (Yeboah C, Med Phys. 2002 Feb;29(2):176-89.)
**Influence of energy, beamlet width, number of beams, and beam orientation on treatment plans
**Conclusion: Need maximum 3-4 beams, but then beam orientation becomes important

==Cost-Effectiveness==
*''Please see [[Radiation_Oncology/Prostate/Utilization]]''

==Radiobiology==
*'''Wisconsin; 2003''' {{PMID|12602558}} -- &quot;What can we expect from dose escalation using proton beams?&quot; (Fowler JF, Clin Oncol (R Coll Radiol). 2003 Feb;15(1):S10-5.)
**Evaluation of tumor dose-response curves, and dose escalation benefit if normal tissue complications can be avoided

==Review==
*'''Harvard''' 
**'''2009''' {{PMID|19672148}} -- &quot;Life, liberty, and the pursuit of protons: an evidence-based review of the role of particle therapy in the treatment of prostate cancer.&quot; (Efstathiou JA, Cancer J. 2009 Jul-Aug;15(4):312-8.)
**'''2009''' {{PMID|19434101}} -- &quot;Proton radiation for localized prostate cancer.&quot; (Coen JJ, Nat Rev Urol. 2009 Jun;6(6):324-30. Epub 2009 May 12.)
**'''2007''' {{PMID|17921728}} -- &quot;High-dose external beam radiation for localized prostate cancer: current status and future challenges.&quot; (Nguyen PL, Cancer J. 2007 Sep-Oct;13(5):295-301.)

*'''Loma Linda; 2007''' [http://www.communityoncology.net/journal/articles/0404235.pdf full text] -- &quot;Conformal proton beam radiation therapy for prostate cancer: concepts and clinical results&quot; (Rossi CJ, Commun Oncol 2007; 4:235-240)</text>
      <sha1>ak44entec7clukmonxio26hb19cpdmi</sha1>
    </revision>
  </page>
  <page>
    <title>Linear Algebra/Gauss' Method</title>
    <ns>0</ns>
    <id>151723</id>
    <revision>
      <id>4675764</id>
      <parentid>4662555</parentid>
      <timestamp>2026-10-12T20:49:17Z</timestamp>
      <contributor>
        <username>Finbob83</username>
        <id>539834</id>
      </contributor>
      <comment>/* */</comment>
      <origin>4675764</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="30645" sha1="h4px50189f1u4sh0s4vzfluf1tqjjpn" xml:space="preserve">&lt;noinclude&gt;{{navigation|Book=Linear Algebra
|current=Gauss' Method
|previous=Solving Linear Systems
|next=Describing the Solution Set}}&lt;/noinclude&gt;

{{TextBox|1=
;Definition 1.1{{anchor|linear equation}}:
A '''linear equation''' in variables
&lt;math&gt;x_1,x_2,\ldots,x_n&lt;/math&gt; has the form

:&lt;math&gt;a_1x_1+a_2x_2+a_3x_3+\cdots+a_nx_n=d&lt;/math&gt;

where the numbers &lt;math&gt;a_1,\dots,a_n\in\R&lt;/math&gt; are the equation's
'''coefficients''' and
&lt;math&gt;d\in\R&lt;/math&gt; is the '''constant'''.
An &lt;math&gt;n&lt;/math&gt;-tuple &lt;math&gt;(s_1,s_2,\dots,s_n)\in\R^n &lt;/math&gt; is a 
'''solution''' 
of, or '''satisfies''', that equation if substituting the numbers
&lt;math&gt;s_1,\dots,s_n&lt;/math&gt; for the variables gives a true statement:
&lt;math&gt;a_1s_1+a_2s_2+\ldots+a_ns_n=d&lt;/math&gt;.

A '''system of linear equations'''

:&lt;math&gt;
\begin{array}{*{4}{rc}r}
a_{1,1}x_1 &amp;+ &amp;a_{1,2}x_2 &amp;+ &amp;\cdots &amp;+ &amp;a_{1,n}x_n &amp;=  &amp;d_1  \\
a_{2,1}x_1 &amp;+ &amp;a_{2,2}x_2 &amp;+ &amp;\cdots &amp;+ &amp;a_{2,n}x_n &amp;=  &amp;d_2  \\
&amp;  &amp;            &amp;   &amp;       &amp;  &amp;           &amp;\vdots   \\
a_{m,1}x_1 &amp;+ &amp;a_{m,2}x_2 &amp;+ &amp;\cdots &amp;+ &amp;a_{m,n}x_n &amp;=  &amp;d_m
\end{array}
&lt;/math&gt;

has the solution
&lt;math&gt;(s_1,s_2,\ldots,s_n)&lt;/math&gt; if that &lt;math&gt;n&lt;/math&gt;-tuple is a solution of all of the equations in the system.
}}

{{TextBox|1=
;Example 1.2:
The ordered pair &lt;math&gt;(-1,5)&lt;/math&gt; is a solution of this system.

:&lt;math&gt;
\begin{array}{*{2}{rc}r}
4x_1 &amp;+ &amp;2x_2 &amp;= &amp;6  \\
-x_1 &amp;+ &amp;x_2  &amp;= &amp;6
\end{array}
&lt;/math&gt;

In contrast, &lt;math&gt; (5,-1) &lt;/math&gt; is not a solution.
}}

Finding the set of all solutions is '''solving'''{{anchor|system of linear equations!solving}} the system. No guesswork or good fortune is needed to solve a linear system. There is an algorithm that always works. The next example introduces that algorithm, called '''Gauss' method'''{{anchor|Gauss' method}}. It transforms the system, step by step, into one with a form that is easily solved.

{{TextBox|1=
;Example 1.3:
To solve this system

:&lt;math&gt;
\begin{array}{*{3}{rc}r}
&amp;   &amp;      &amp;   &amp;3x_3  &amp;=  &amp;9  \\
x_1 &amp;+  &amp;5x_2  &amp;-  &amp;2x_3  &amp;=  &amp;2  \\
\frac{1}{3}x_1 &amp;+  &amp;2x_2  &amp;   &amp;      &amp;=  &amp;3  
\end{array}
&lt;/math&gt;

we repeatedly transform it until it is in a form that is easy to solve.

:&lt;math&gt;\begin{array}{rcl}
\quad
&amp;\xrightarrow[]{ \text{swap row 1 with row 3} }
&amp;\begin{array}{*{3}{rc}r}
\frac{1}{3}x_1 &amp;+  &amp;2x_2  &amp;   &amp;      &amp;=  &amp;3  \\
x_1 &amp;+  &amp;5x_2  &amp;-  &amp;2x_3  &amp;=  &amp;2  \\
&amp;   &amp;      &amp;   &amp;3x_3  &amp;=  &amp;9  
\end{array}                                         \\
&amp;\xrightarrow[]{ \text{multiply row 1 by 3} }
&amp;\begin{array}{*{3}{rc}r}
x_1 &amp;+  &amp;6x_2  &amp;   &amp;      &amp;=  &amp;9  \\
x_1 &amp;+  &amp;5x_2  &amp;-  &amp;2x_3  &amp;=  &amp;2  \\
&amp;   &amp;      &amp;   &amp;3x_3  &amp;=  &amp;9  
\end{array}                                          \\
&amp;\xrightarrow[]{ \text{add }-1\text{ times row 1 to row 2} }
&amp;\begin{array}{*{3}{rc}r}
x_1 &amp;+  &amp;6x_2  &amp;   &amp;      &amp;=  &amp;9  \\
&amp;   &amp;-x_2  &amp;-  &amp;2x_3  &amp;=  &amp;-7 \\
&amp;   &amp;      &amp;   &amp;3x_3  &amp;=  &amp;9  
\end{array}
\end{array}
&lt;/math&gt;
The third step is the only nontrivial one. We've mentally multiplied both sides of the first row by &lt;math&gt;-1&lt;/math&gt;, mentally added that to the old second row, and written the result in as the new second row.

Now we can find the value of each variable.
The bottom equation shows that &lt;math&gt;x_3=3&lt;/math&gt;. Substituting &lt;math&gt;3&lt;/math&gt; for &lt;math&gt;x_3&lt;/math&gt; in the middle equation shows that &lt;math&gt;x_2=1&lt;/math&gt;. Substituting those two into the top equation gives that &lt;math&gt;x_1=3&lt;/math&gt; and so the system has a unique solution: the solution set is &lt;math&gt;\{\,(3,1,3)\,\}&lt;/math&gt;.
}}

Most of this subsection and the next one consists of examples of solving linear systems by Gauss' method. We will use it throughout this book. It is fast and easy. But, before we get to those examples, we will first show that this method is also safe in that it never loses solutions or picks up extraneous solutions.

{{TextBox|1=
;Theorem 1.4 (Gauss' method) {{anchor|th:GaussMethod}}:&lt;!--\label{th:GaussMethod}--&gt;
If a linear system is changed to another by one of these operations
&lt;ol type=1 start=1&gt;
&lt;li&gt;
an equation is swapped with another
&lt;li&gt;
an equation has both sides multiplied by a nonzero constant
&lt;li&gt;
an equation is replaced by the sum of itself and a multiple of another
&lt;/ol&gt;
then the two systems have the same set of solutions.
}}

Each of those three operations has a restriction. Multiplying a row by &lt;math&gt;0&lt;/math&gt; is not allowed because obviously that can change the solution set of the system. Similarly, adding a multiple of a row to itself is not allowed because adding &lt;math&gt;-1&lt;/math&gt; times the row to itself has the effect of multiplying the row by &lt;math&gt;0&lt;/math&gt;. Finally, swapping a row with itself is disallowed to make some results in the fourth chapter easier to state and remember (and besides, self-swapping doesn't accomplish anything).

{{TextBox|1=
;Proof:
We will cover the equation swap operation here and save the other two
cases for [[#ex:ProveGaussMethod|Problem 14]]&lt;!--\ref{ex:ProveGaussMethod}--&gt;.

Consider this swap of row &lt;math&gt;i&lt;/math&gt; with row &lt;math&gt;j&lt;/math&gt;.

:&lt;math&gt;
\begin{array}{*{4}{rc}r}
a_{1,1}x_1  &amp;+  &amp;a_{1,2}x_2 &amp;+  &amp;\cdots  &amp;&amp;a_{1,n}x_n  &amp;=  &amp;d_1  \\
&amp;   &amp;           &amp;   &amp;        &amp;   &amp;            &amp;\vdots   \\
a_{i,1}x_1  &amp;+  &amp;a_{i,2}x_2 &amp;+  &amp;\cdots  &amp;&amp;a_{i,n}x_n  &amp;=  &amp;d_i  \\
&amp;   &amp;           &amp;   &amp;        &amp;   &amp;            &amp;\vdots   \\
a_{j,1}x_1  &amp;+  &amp;a_{j,2}x_2 &amp;+  &amp;\cdots  &amp;&amp;a_{j,n}x_n  &amp;=  &amp;d_j  \\
&amp;   &amp;           &amp;   &amp;        &amp;   &amp;            &amp;\vdots   \\
a_{m,1}x_1  &amp;+  &amp;a_{m,2}x_2 &amp;+  &amp;\cdots  &amp;&amp;a_{m,n}x_n  &amp;=  &amp;d_m  
\end{array}
\xrightarrow[]{}
\begin{array}{*{4}{rc}r}
a_{1,1}x_1  &amp;+  &amp;a_{1,2}x_2 &amp;+  &amp;\cdots  &amp;&amp;a_{1,n}x_n  &amp;=  &amp;d_1  \\
&amp;   &amp;           &amp;   &amp;        &amp;   &amp;            &amp;\vdots   \\
a_{j,1}x_1  &amp;+  &amp;a_{j,2}x_2 &amp;+  &amp;\cdots  &amp;&amp;a_{j,n}x_n  &amp;=  &amp;d_j  \\
&amp;   &amp;           &amp;   &amp;        &amp;   &amp;            &amp;\vdots   \\
a_{i,1}x_1  &amp;+  &amp;a_{i,2}x_2 &amp;+  &amp;\cdots  &amp;&amp;a_{i,n}x_n  &amp;=  &amp;d_i  \\
&amp;   &amp;           &amp;   &amp;        &amp;   &amp;            &amp;\vdots   \\
a_{m,1}x_1  &amp;+  &amp;a_{m,2}x_2 &amp;+  &amp;\cdots  &amp;&amp;a_{m,n}x_n  &amp;=  &amp;d_m  
\end{array}
&lt;/math&gt;


The &lt;math&gt;n&lt;/math&gt;-tuple &lt;math&gt;(s_1,\ldots,s_n)&lt;/math&gt; satisfies the system before the swap if and only if substituting the values, the &lt;math&gt;s&lt;/math&gt;'s, for the variables, the &lt;math&gt;x&lt;/math&gt;'s, gives true statements:
&lt;math&gt;a_{1,1}s_1+a_{1,2}s_2+\cdots+a_{1,n}s_n=d_1&lt;/math&gt;
and ... 
&lt;math&gt;a_{i,1}s_1+a_{i,2}s_2+\cdots+a_{i,n}s_n=d_i&lt;/math&gt;
and ...  &lt;math&gt;a_{j,1}s_1+a_{j,2}s_2+\cdots+a_{j,n}s_n=d_j&lt;/math&gt;
and ...  &lt;math&gt;a_{m,1}s_1+a_{m,2}s_2+\cdots+a_{m,n}s_n=d_m&lt;/math&gt;.

In a requirement consisting of statements and-ed together we can rearrange the order of the statements, so that this requirement is met if and only if
&lt;math&gt;a_{1,1}s_1+a_{1,2}s_2+\cdots+a_{1,n}s_n=d_1&lt;/math&gt;
and ...  &lt;math&gt;a_{j,1}s_1+a_{j,2}s_2+\cdots+a_{j,n}s_n=d_j&lt;/math&gt;
and ...  &lt;math&gt;a_{i,1}s_1+a_{i,2}s_2+\cdots+a_{i,n}s_n=d_i&lt;/math&gt;
and ...  &lt;math&gt;a_{m,1}s_1+a_{m,2}s_2+\cdots+a_{m,n}s_n=d_m&lt;/math&gt;.
This is exactly the requirement that &lt;math&gt;(s_1,\ldots,s_n)&lt;/math&gt; solves the system after the row swap.
}}

{{TextBox|1=
;Definition 1.5:{{anchor|elementary operations}}
The three operations from [[#th:GaussMethod|Theorem 1.4]]&lt;!--\ref{th:GaussMethod}--&gt;
are the '''elementary reduction operations''',
or '''row operations''', or '''Gaussian operations'''.
They are '''swapping''', '''multiplying by a scalar''' or '''rescaling''', and '''pivoting'''.
}}

When writing out the calculations, we will abbreviate &quot;row &lt;math&gt;i&lt;/math&gt;&quot; by &quot;&lt;math&gt;\rho_i&lt;/math&gt;&quot;. For instance, we will denote a pivot operation by &lt;math&gt;k\rho_i+\rho_j&lt;/math&gt;, with the row that is changed written second. We will also, to save writing, often list pivot steps together when they use the same &lt;math&gt;\rho_i&lt;/math&gt;.

{{TextBox|1=
;Example 1.6:
A typical use of Gauss' method is to solve this system.

:&lt;math&gt;
\begin{array}{*{3}{rc}r}
x  &amp;+  &amp;y  &amp;   &amp;   &amp;=  &amp;0  \\
2x  &amp;-  &amp;y  &amp;+  &amp;3z &amp;=  &amp;3  \\
x  &amp;-  &amp;2y &amp;-  &amp;z  &amp;=  &amp;3  
\end{array}
&lt;/math&gt;

The first transformation of the system involves using the first row to eliminate the &lt;math&gt;x&lt;/math&gt; in the second row and the &lt;math&gt;x&lt;/math&gt; in the third. To get rid of the second row's &lt;math&gt;2x&lt;/math&gt;, we multiply the entire first row by &lt;math&gt;-2&lt;/math&gt;, 
add that to the second row, and write the result in as the new second row. To get rid of the third row's &lt;math&gt;x&lt;/math&gt;, we multiply the first row by &lt;math&gt;-1&lt;/math&gt;, add that to the third row, and write the result in as the new third row.

:&lt;math&gt;\begin{array}{rcl}
&amp;\xrightarrow[-\rho_1+\rho_3]{-2\rho_1+\rho_2}
&amp;\begin{array}{*{3}{rc}r}
x  &amp;+  &amp;y  &amp;   &amp;   &amp;=  &amp;0  \\
&amp;   &amp;-3y&amp;+  &amp;3z &amp;=  &amp;3  \\
&amp;   &amp;-3y&amp;-  &amp;z  &amp;=  &amp;3  
\end{array}   
\end{array}
&lt;/math&gt;
(Note that the two &lt;math&gt;\rho_1&lt;/math&gt; steps &lt;math&gt;-2\rho_1+\rho_2&lt;/math&gt; and &lt;math&gt;-\rho_1+\rho_3&lt;/math&gt; are written as one operation.) In this second system, the last two equations involve only two unknowns. To finish we transform the second system into a third system, where the last equation involves only one unknown. This transformation uses the second row to eliminate &lt;math&gt;y&lt;/math&gt; from the third row.

:&lt;math&gt;\begin{array}{rcl}
&amp;\xrightarrow[]{-\rho_2+\rho_3}
&amp;\begin{array}{*{3}{rc}r}
x  &amp;+  &amp;y  &amp;   &amp;   &amp;=  &amp;0  \\
&amp;   &amp;-3y&amp;+  &amp;3z &amp;=  &amp;3  \\
&amp;   &amp;   &amp;   &amp;-4z&amp;=  &amp;0
\end{array}
\end{array}
&lt;/math&gt;
Now we are set up for the solution. The third row shows that &lt;math&gt;z=0&lt;/math&gt;. {{anchor|back substitution}}Substitute that back into the second row to get &lt;math&gt;y=-1&lt;/math&gt;, and then substitute back into the first row to get &lt;math&gt; x=1 &lt;/math&gt;.
}}

{{TextBox|1=
;Example 1.7{{anchor|statics problem}}:
For the Physics problem from the start of this
chapter, Gauss' method gives this.

:&lt;math&gt;\begin{array}{rcl}
\begin{array}{*{2}{rc}r}
40h  &amp;+  &amp;15c  &amp;=  &amp;100      \\
-50h &amp;+  &amp;25c  &amp;=  &amp;50         
\end{array}
&amp;\xrightarrow[]{5/4\rho_1 +\rho_2}
&amp;\begin{array}{*{2}{rc}r}
40h  &amp;+  &amp;15c       &amp;=  &amp;100      \\
&amp;   &amp;(175/4)c  &amp;=  &amp;175 
\end{array}
\end{array}
&lt;/math&gt;
So &lt;math&gt; c=4 &lt;/math&gt;, and back-substitution gives that &lt;math&gt; h=1 &lt;/math&gt;.
(The Chemistry problem is solved later.)
}}

{{TextBox|1=
;Example 1.8:
The reduction

:&lt;math&gt;\begin{array}{rcl}
\begin{array}{*{3}{rc}r}
x  &amp;+  &amp;y  &amp;+  &amp;z  &amp;=  &amp;9  \\
2x  &amp;+  &amp;4y &amp;-  &amp;3z &amp;=  &amp;1  \\
3x  &amp;+  &amp;6y &amp;-  &amp;5z &amp;=  &amp;0  
\end{array}
&amp;\xrightarrow[-3\rho_1 +\rho_3]{-2\rho_1 +\rho_2}
&amp;\begin{array}{*{3}{rc}r}
x  &amp;+  &amp;y  &amp;+  &amp;z  &amp;=  &amp;9  \\
&amp;   &amp;2y &amp;-  &amp;5z &amp;=  &amp;-17\\
&amp;   &amp;3y &amp;-  &amp;8z&amp;=  &amp;-27
\end{array}                                    \\
&amp;\xrightarrow[]{-(3/2)\rho_2+\rho_3}
&amp;\begin{array}{*{3}{rc}r}
x  &amp;+  &amp;y  &amp;+  &amp;z            &amp;=  &amp;9  \\
&amp;   &amp;2y &amp;-  &amp;5z           &amp;=  &amp;-17\\
&amp;   &amp;   &amp;   &amp;-(1/2)z      &amp;=  &amp;-(3/2) 
\end{array}
\end{array}
&lt;/math&gt;
shows that &lt;math&gt; z=3 &lt;/math&gt;, &lt;math&gt; y=-1 &lt;/math&gt;, and &lt;math&gt; x=7 &lt;/math&gt;.
}}

As these examples illustrate, Gauss' method uses the elementary reduction
operations to set up back-substitution.

{{TextBox|1=
;Definition 1.9{{anchor|echelon form}}:
In each row, the first variable with a nonzero coefficient is the row's
'''leading variable'''. 
A system is in '''echelon form'''
if each leading variable
is to the right of the leading variable in the row above it
(except for the leading variable in the first row).
}}

{{TextBox|1=
;Example 1.10: 
The only operation needed in the examples above is pivoting.
Here is a linear system that requires the operation of swapping equations. 
After the first pivot

:&lt;math&gt;\begin{array}{rcl}
\begin{array}{*{4}{rc}r}
x  &amp;-  &amp;y  &amp;   &amp;   &amp;   &amp;   &amp;=  &amp;0  \\
2x  &amp;-  &amp;2y &amp;+  &amp;z  &amp;+  &amp;2w &amp;=  &amp;4  \\
&amp;   &amp;y  &amp;   &amp;   &amp;+  &amp;w  &amp;=  &amp;0  \\
&amp;   &amp;   &amp;   &amp;2z &amp;+  &amp;w  &amp;=  &amp;5  
\end{array}
&amp;\xrightarrow[]{-2\rho_1 +\rho_2}
&amp;\begin{array}{*{4}{rc}r}
x  &amp;-  &amp;y  &amp;   &amp;   &amp;   &amp;   &amp;=  &amp;0  \\
&amp;   &amp;   &amp;   &amp;z  &amp;+  &amp;2w &amp;=  &amp;4  \\
&amp;   &amp;y  &amp;   &amp;   &amp;+  &amp;w  &amp;=  &amp;0  \\
&amp;   &amp;   &amp;   &amp;2z &amp;+  &amp;w  &amp;=  &amp;5  
\end{array}    
\end{array}
&lt;/math&gt;
the second equation has no leading &lt;math&gt;y&lt;/math&gt;.
To get one, 
we look lower down in the system for a row that has a leading &lt;math&gt;y&lt;/math&gt; and 
swap it in.

:&lt;math&gt;\begin{array}{rcl}
&amp;\xrightarrow[]{\rho_2 \leftrightarrow\rho_3}
&amp;\begin{array}{*{4}{rc}r}
x  &amp;-  &amp;y  &amp;   &amp;   &amp;   &amp;   &amp;=  &amp;0  \\
&amp;   &amp;y  &amp;   &amp;   &amp;+  &amp;w  &amp;=  &amp;0  \\
&amp;   &amp;   &amp;   &amp;z  &amp;+  &amp;2w &amp;=  &amp;4  \\
&amp;   &amp;   &amp;   &amp;2z &amp;+  &amp;w  &amp;=  &amp;5  
\end{array}    
\end{array}
&lt;/math&gt;
(Had there been more than one row below the second with a leading &lt;math&gt;y&lt;/math&gt;
then we could have swapped in any one.)
The rest of Gauss' method goes as before.

:&lt;math&gt;\begin{array}{rcl}
&amp;\xrightarrow[]{-2\rho_3 +\rho_4}
&amp;\begin{array}{*{4}{rc}r}
x  &amp;-  &amp;y  &amp;   &amp;   &amp;   &amp;   &amp;=  &amp;0  \\
&amp;   &amp;y  &amp;   &amp;   &amp;+  &amp;w  &amp;=  &amp;0  \\
&amp;   &amp;   &amp;   &amp;z  &amp;+  &amp;2w &amp;=  &amp;4  \\
&amp;   &amp;   &amp;   &amp;   &amp;   &amp;-3w&amp;=  &amp;-3 
\end{array}
\end{array}
&lt;/math&gt;
Back-substitution gives &lt;math&gt; w=1 &lt;/math&gt;, &lt;math&gt; z=2 &lt;/math&gt;, &lt;math&gt; y=-1 &lt;/math&gt;, and &lt;math&gt; x=-1 &lt;/math&gt;.
}}

Strictly speaking, the operation of rescaling rows is 
not needed to solve linear systems.  
We have included it because we will use it 
later in this chapter as part of a variation on Gauss' method, 
the Gauss-Jordan method.

All of the systems seen so far have the same number of equations as unknowns.
All of them have a solution, and for all of them there is only one solution.
We finish this subsection by seeing for contrast
some other things that can happen.

{{TextBox|1=
;Example 1.11{{anchor|ex:MoreEqsThanUnks}}: &lt;!--\label{ex:MoreEqsThanUnks}--&gt;
Linear systems need not have the same number of equations as unknowns.
This system 

:&lt;math&gt;
\begin{array}{*{2}{rc}r}
x  &amp;+  &amp;3y  &amp;=  &amp;1  \\
2x  &amp;+  &amp;y   &amp;=  &amp;-3 \\
2x  &amp;+  &amp;2y  &amp;=  &amp;-2 
\end{array}  
&lt;/math&gt;

has more equations than variables.
Gauss' method helps us understand this system also, since this

:&lt;math&gt;\begin{array}{rcl}
&amp;\xrightarrow[-2\rho_1 +\rho_3]{-2\rho_1 +\rho_2}
&amp;\begin{array}{*{2}{rc}r}
x  &amp;+  &amp;3y  &amp;=  &amp;1  \\
&amp;   &amp;-5y &amp;=  &amp;-5 \\
&amp;   &amp;-4y &amp;=  &amp;-4 
\end{array}
\end{array}
&lt;/math&gt;
shows that one of the equations is redundant.
Echelon form

:&lt;math&gt;\begin{array}{rcl}
&amp;\xrightarrow[]{-(4/5)\rho_2 +\rho_3}
&amp;\begin{array}{*{2}{rc}r}
x  &amp;+  &amp;3y  &amp;=  &amp;1  \\
&amp;   &amp;-5y &amp;=  &amp;-5 \\
&amp;   &amp;0   &amp;=  &amp;0  
\end{array}
\end{array}
&lt;/math&gt;
gives &lt;math&gt; y=1 &lt;/math&gt; and &lt;math&gt; x=-2 &lt;/math&gt;.
The &quot;&lt;math&gt; 0=0 &lt;/math&gt;&quot; is derived from the redundancy.
}}

That example's system has more equations than variables.
Gauss' method is also useful on systems with more variables than equations.
Many examples are in the next subsection.

Another way that linear systems can differ from the examples shown earlier 
is that some linear systems do not have a unique solution.
This can happen in two ways.

The first is that it can fail to have any solution at all.

{{TextBox|1=
;Example 1.12{{anchor|ex:MoreEqsThanUnksInconsis}}: &lt;!--\label{ex:MoreEqsThanUnksInconsis}--&gt;
Contrast the system in the last example with this one.

:&lt;math&gt;\begin{array}{rcl}
\begin{array}{*{2}{rc}r}
x  &amp;+  &amp;3y  &amp;=  &amp;1  \\
2x  &amp;+  &amp;y   &amp;=  &amp;-3 \\
2x  &amp;+  &amp;2y  &amp;=  &amp;0  
\end{array}
&amp;\xrightarrow[-2\rho_1 +\rho_3]{-2\rho_1 +\rho_2}
&amp;\begin{array}{*{2}{rc}r}
x  &amp;+  &amp;3y  &amp;=  &amp;1  \\
&amp;   &amp;-5y &amp;=  &amp;-5 \\
&amp;   &amp;-4y &amp;=  &amp;-2
\end{array}
\end{array}
&lt;/math&gt;
Here the system is inconsistent: no pair of numbers satisfies 
all of the equations simultaneously.
Echelon form makes this inconsistency obvious.

:&lt;math&gt;\begin{array}{rcl}
&amp;\xrightarrow[]{-(4/5)\rho_2 +\rho_3}
&amp;\begin{array}{*{2}{rc}r}
x  &amp;+  &amp;3y  &amp;=  &amp;1  \\
&amp;   &amp;-5y &amp;=  &amp;-5 \\
&amp;   &amp;0   &amp;=  &amp;2 
\end{array}
\end{array}
&lt;/math&gt;
The solution set is empty.
}}

{{TextBox|1=
;Example 1.13:
The prior system has more equations than unknowns, but
that is not what causes the inconsistency&amp;mdash; 
[[#ex:MoreEqsThanUnks|Example 1.11]]&lt;!--\ref{ex:MoreEqsThanUnks}--&gt;
has more equations than unknowns and yet is consistent.
Nor is having more equations than unknowns necessary for
inconsistency, as is illustrated by this inconsistent system with the 
same number of equations as unknowns.

:&lt;math&gt;\begin{array}{rcl}
\begin{array}{*{2}{rc}r}
x  &amp;+  &amp;2y  &amp;=  &amp;8  \\
2x  &amp;+  &amp;4y  &amp;=  &amp;8  
\end{array}
&amp;\xrightarrow[]{-2\rho_1 + \rho_2}
&amp;\begin{array}{*{2}{rc}r}
x  &amp;+  &amp;2y  &amp;=  &amp;8  \\
&amp;   &amp;0   &amp;=  &amp;-8
\end{array}
\end{array}
&lt;/math&gt;
}}

The other way that a linear system can fail to have a unique solution
is to have many solutions.

{{TextBox|1=
;Example 1.14:
In this system

:&lt;math&gt;
\begin{array}{*{2}{rc}r}
x  &amp;+  &amp;y   &amp;=  &amp;4  \\
2x  &amp;+  &amp;2y  &amp;=  &amp;8  
\end{array}
&lt;/math&gt;

any pair of numbers satisfying the first equation automatically
satisfies the second.
The solution set &lt;math&gt; \{ (x,y)\,\big|\, x+y=4 \} &lt;/math&gt; is infinite; some
of its members are &lt;math&gt;(0,4)&lt;/math&gt;, &lt;math&gt;(-1,5)&lt;/math&gt;, and &lt;math&gt;(2.5,1.5)&lt;/math&gt;.
The result of applying Gauss' method here contrasts with the prior example
because we do not get a contradictory equation.

:&lt;math&gt;\begin{array}{rcl}
&amp;\xrightarrow[]{-2\rho_1 + \rho_2}
&amp;\begin{array}{*{2}{rc}r}
x  &amp;+  &amp;y   &amp;=  &amp;4  \\
&amp;   &amp;0   &amp;=  &amp;0  
\end{array}
\end{array}
&lt;/math&gt;
}}

Don't be fooled by the &quot;&lt;math&gt; 0=0 &lt;/math&gt;&quot; equation in that example.
It is not the signal that a system has many solutions.

{{TextBox|1=
;Example 1.15{{anchor|ex:NoZerosInfManySols}}: &lt;!--\label{ex:NoZerosInfManySols}--&gt;
The absence of a &quot;&lt;math&gt; 0=0 &lt;/math&gt;&quot; does not keep a system from having
many different solutions.
This system is in echelon form

:&lt;math&gt;
\begin{array}{*{3}{rc}r}
x  &amp;+  &amp;y  &amp;+  &amp;z  &amp;=  &amp;0  \\
&amp;   &amp;y  &amp;+  &amp;z  &amp;=  &amp;0  
\end{array}
&lt;/math&gt;

has no &quot;&lt;math&gt;0=0&lt;/math&gt;&quot;, and yet has infinitely many solutions.
(For instance, each of these is a solution: &lt;math&gt;(0,1,-1)&lt;/math&gt;, 
&lt;math&gt;(0,1/2,-1/2)&lt;/math&gt;, &lt;math&gt;(0,0,0)&lt;/math&gt;, and &lt;math&gt;(0,-\pi,\pi)&lt;/math&gt;.
There are infinitely many solutions because
any triple whose first component is &lt;math&gt;0&lt;/math&gt; and whose second component is the 
negative of the third is a solution.)

Nor does the presence of a &quot;&lt;math&gt; 0=0 &lt;/math&gt;&quot; mean that the system must have 
many solutions.
[[#ex:MoreEqsThanUnks|Example 1.11]]&lt;!--\ref{ex:MoreEqsThanUnks}--&gt; shows that.
So does this system, which does not have 
many solutions&amp;mdash; in fact it has none&amp;mdash; despite that 
when it is brought to echelon form it has a &quot;&lt;math&gt;0=0&lt;/math&gt;&quot; row.

:&lt;math&gt;\begin{array}{rcl}
\begin{array}{*{3}{rc}r}
2x  &amp;   &amp;   &amp;-   &amp;2z  &amp;=  &amp;6  \\
&amp;   &amp;y  &amp;+   &amp;z   &amp;=  &amp;1  \\
2x  &amp;+  &amp;y  &amp;-   &amp;z   &amp;=  &amp;7  \\
&amp;   &amp;3y &amp;+   &amp;3z  &amp;=  &amp;0  
\end{array}
&amp;\xrightarrow[]{-\rho_1 +\rho_3}
&amp;\begin{array}{*{3}{rc}r}
2x  &amp;   &amp;   &amp;-   &amp;2z  &amp;=  &amp;6  \\
&amp;   &amp;y  &amp;+   &amp;z   &amp;=  &amp;1  \\
&amp;   &amp;y  &amp;+   &amp;z   &amp;=  &amp;1  \\
&amp;   &amp;3y &amp;+   &amp;3z  &amp;=  &amp;0  
\end{array}     \\
&amp;\xrightarrow[-3\rho_2 +\rho_4]{-\rho_2 +\rho_3}
&amp;\begin{array}{*{3}{rc}r}
2x  &amp;   &amp;   &amp;-   &amp;2z  &amp;=  &amp;6  \\
&amp;   &amp;y  &amp;+   &amp;z   &amp;=  &amp;1  \\
&amp;   &amp;   &amp;    &amp;0   &amp;=  &amp;0  \\
&amp;   &amp;   &amp;    &amp;0   &amp;=  &amp;-3 
\end{array}
\end{array}
&lt;/math&gt;
}}

We will finish this subsection with a summary of
what we've seen so far about Gauss' method.

Gauss' method uses the three row operations to 
set a system up for back substitution.
If any step shows a contradictory equation then we can stop with the
conclusion that the system has no solutions.
If we reach echelon form without a contradictory equation,
and each variable is a leading variable in its
row, then the system has a unique solution and we find it by
back substitution.
Finally, if we reach echelon form without a contradictory equation,
and there is not a unique solution
(at least one variable is not a leading variable) then the system has many
solutions.

The next subsection deals with the third case&amp;mdash; 
we will see how to describe the
solution set of a system with many solutions.

== Exercises ==
{{Linear Algebra/Book 2/Recommended}}
{{TextBox|1=
;Problem 1: 
Use Gauss' method to find the unique solution for each system.
&lt;ol type=1 start=1&gt;
&lt;li&gt; 
&lt;math&gt;\begin{array}{*{2}{rc}r}
2x  &amp;+  &amp;3y  &amp;=  &amp;13  \\
x   &amp;-  &amp;y   &amp;=  &amp;-1
\end{array}&lt;/math&gt;
&lt;br&gt;&lt;p&gt;&lt;br&gt;&lt;/p&gt;&lt;li&gt; 
&lt;math&gt;\begin{array}{*{3}{rc}r}
x   &amp;  &amp;  &amp;-  &amp;z  &amp;=  &amp;0  \\
3x  &amp;+ &amp;y &amp;   &amp;   &amp;=  &amp;1  \\
-x  &amp;+ &amp;y &amp;+  &amp;z  &amp;=  &amp;4
\end{array}&lt;/math&gt;
&lt;/ol&gt;
}}
{{Linear Algebra/Book 2/Recommended}}
{{TextBox|1=
;Problem 2:  
Use Gauss' method to solve each system
or conclude &quot;many solutions&quot; or &quot;no solutions&quot;.
&lt;ol type=1 start=1&gt;
&lt;li&gt; &lt;math&gt;
\begin{array}{*{2}{rc}r}
2x  &amp;+  &amp;2y  &amp;=  &amp;5  \\
x  &amp;-  &amp;4y  &amp;=  &amp;0  
\end{array}
&lt;/math&gt;
&lt;br&gt;&lt;p&gt;&lt;br&gt;&lt;/p&gt;
&lt;li&gt; &lt;math&gt;
\begin{array}{*{2}{rc}r}
-x  &amp;+  &amp;y   &amp;=  &amp;1  \\
x  &amp;+  &amp;y   &amp;=  &amp;2  
\end{array}
&lt;/math&gt; 
&lt;br&gt;&lt;p&gt;&lt;br&gt;&lt;/p&gt;
&lt;li&gt;  &lt;math&gt;
\begin{array}{*{3}{rc}r}
x  &amp;-  &amp;3y  &amp;+  &amp;z  &amp;=  &amp;1  \\
x  &amp;+  &amp;y   &amp;+  &amp;2z &amp;=  &amp;14 
\end{array}
&lt;/math&gt; 
&lt;br&gt;&lt;p&gt;&lt;br&gt;&lt;/p&gt;
&lt;li&gt;  &lt;math&gt;
\begin{array}{*{2}{rc}r}
-x  &amp;-  &amp;y   &amp;=  &amp;1  \\
-3x  &amp;-  &amp;3y  &amp;=  &amp;2  
\end{array}
&lt;/math&gt; 
&lt;br&gt;&lt;p&gt;&lt;br&gt;&lt;/p&gt;
&lt;li&gt;  &lt;math&gt;
\begin{array}{*{3}{rc}r}
&amp;   &amp;4y  &amp;+  &amp;z  &amp;=  &amp;20 \\
2x  &amp;-  &amp;2y  &amp;+  &amp;z  &amp;=  &amp;0  \\
x  &amp;   &amp;    &amp;+  &amp;z  &amp;=  &amp;5  \\
x  &amp;+  &amp;y   &amp;-  &amp;z  &amp;=  &amp;10 
\end{array}
&lt;/math&gt;
&lt;br&gt;&lt;p&gt;&lt;br&gt;&lt;/p&gt;
&lt;li&gt; &lt;math&gt; \begin{array}{*{4}{rc}r}
2x  &amp;   &amp;   &amp;+  &amp;z  &amp;+  &amp;w  &amp;=  &amp;5  \\
&amp;   &amp;y  &amp;   &amp;   &amp;-  &amp;w  &amp;=  &amp;-1 \\
3x  &amp;   &amp;   &amp;-  &amp;z  &amp;-  &amp;w  &amp;=  &amp;0  \\
4x  &amp;+  &amp;y  &amp;+  &amp;2z &amp;+  &amp;w  &amp;=  &amp;9  
\end{array}
&lt;/math&gt;
&lt;/ol&gt;
}}
{{Linear Algebra/Book 2/Recommended}}
{{TextBox|1=
;Problem 3: 
There are methods for solving linear systems other 
than Gauss' method.
One often taught in high school is to solve one of the 
equations for a variable, then substitute the resulting expression into
other equations.
That step is repeated until there is an equation with only one
variable.
From that, the first number in the solution is derived, and then 
back-substitution can be done.
This method takes longer than Gauss' method, since it involves
more arithmetic operations, and is also more
likely to lead to errors.
To illustrate how it can lead to wrong conclusions, we will use the system 

:&lt;math&gt;
\begin{array}{*{2}{rc}r}
x  &amp;+  &amp;3y  &amp;=  &amp;1  \\
2x  &amp;+  &amp;y   &amp;=  &amp;-3 \\
2x  &amp;+  &amp;2y  &amp;=  &amp;0  
\end{array}
&lt;/math&gt;

from [[#ex:MoreEqsThanUnksInconsis|Example 1.12]]&lt;!--\ref{ex:MoreEqsThanUnksInconsis}--&gt;.
&lt;ol type=1 start=1&gt;
&lt;li&gt; Solve the first equation for &lt;math&gt;x&lt;/math&gt; and 
substitute that expression into the second equation.
Find the resulting &lt;math&gt;y&lt;/math&gt;.
&lt;li&gt; Again solve the first equation for &lt;math&gt;x&lt;/math&gt;, 
but this time substitute that expression into the third equation.
Find this &lt;math&gt;y&lt;/math&gt;.
&lt;/ol&gt;
What extra step must a user of this method take to avoid 
erroneously concluding a system has a solution?
}}
{{Linear Algebra/Book 2/Recommended}}
{{TextBox|1=
;Problem 4: 
For which values of &lt;math&gt; k &lt;/math&gt; are
there no solutions, many solutions, or a unique solution
to this system?

:&lt;math&gt;
\begin{array}{*{2}{rc}r}
x  &amp;-  &amp;y  &amp;=  &amp;1  \\
3x  &amp;-  &amp;3y &amp;=  &amp;k  
\end{array}
&lt;/math&gt;
}}
{{Linear Algebra/Book 2/Recommended}}
{{TextBox|1=
;Problem 5: 
This system is not linear, in some sense,

:&lt;math&gt;
\begin{array}{*{3}{rc}r}
2\sin\alpha  &amp;-  &amp;\cos\beta  &amp;+  &amp;3\tan\gamma  &amp;=  &amp;3  \\
4\sin\alpha  &amp;+  &amp;2\cos\beta &amp;-  &amp;2\tan\gamma  &amp;=  &amp;10  \\
6\sin\alpha  &amp;-  &amp;3\cos\beta &amp;+  &amp;\tan\gamma   &amp;=  &amp;9  
\end{array}
&lt;/math&gt;

and yet we can nonetheless apply Gauss' method.
Do so. Does the system have a solution?
}}
{{Linear Algebra/Book 2/Recommended}}
{{TextBox|1=
;Problem 6: 
What conditions must the constants, the &lt;math&gt;b&lt;/math&gt;'s,
satisfy so that each of these systems has a solution?
''Hint.'' 
Apply Gauss' method and see what happens to the right side {{harv|Anton|1987}}.

&lt;ol type=1 start=1&gt;
&lt;li&gt;  &lt;math&gt;
\begin{array}{*{2}{rc}r}
x  &amp;-  &amp;3y  &amp;=  &amp;b_1 \\
3x  &amp;+  &amp;y   &amp;=  &amp;b_2 \\
x  &amp;+  &amp;7y  &amp;=  &amp;b_3 \\
2x  &amp;+  &amp;4y  &amp;=  &amp;b_4 
\end{array}   &lt;/math&gt;
&lt;br&gt;&lt;p&gt;&lt;br&gt;&lt;/p&gt;
&lt;li&gt; &lt;math&gt;
\begin{array}{*{3}{rc}r}
x_1  &amp;+  &amp;2x_2  &amp;+  &amp;3x_3  &amp;=  &amp;b_1  \\
2x_1  &amp;+  &amp;5x_2  &amp;+  &amp;3x_3  &amp;=  &amp;b_2  \\
x_1  &amp;   &amp;      &amp;+  &amp;8x_3  &amp;=  &amp;b_3  
\end{array}   &lt;/math&gt;
&lt;/ol&gt;
}}
{{TextBox|1=
;Problem 7: 
True or false: a system with more unknowns than equations
has at least one solution.
(As always, to say &quot;true&quot; you must prove it, while to say 
&quot;false&quot; you must produce a counterexample.)
}}
{{TextBox|1=
;Problem 8{{anchor|chemistry problem}}: 
Must any Chemistry problem like
the one that starts this subsection&amp;mdash;
a balance the reaction problem&amp;mdash; have infinitely many solutions?
}}
{{Linear Algebra/Book 2/Recommended}}
{{TextBox|1=
;Problem 9: 
Find the coefficients
&lt;math&gt; a &lt;/math&gt;, &lt;math&gt; b &lt;/math&gt;, and &lt;math&gt; c &lt;/math&gt; so that the graph of &lt;math&gt; f(x)=ax^2+bx+c &lt;/math&gt; 
passes through the points &lt;math&gt; (1,2) &lt;/math&gt;, &lt;math&gt; (-1,6) &lt;/math&gt;, and &lt;math&gt; (2,3) &lt;/math&gt;.
}}
{{TextBox|1=
;Problem 10: 
Gauss' method works by combining the equations in a system to make new
equations.
&lt;ol type=1 start=1&gt;
&lt;li&gt; Can the equation &lt;math&gt; 3x-2y=5 &lt;/math&gt; be derived, by a sequence of
Gaussian reduction steps, from the equations in this system?

:&lt;math&gt;
\begin{array}{*{2}{rc}r}
x  &amp;+  &amp;y  &amp;=  &amp;1  \\
4x  &amp;-  &amp;y  &amp;=  &amp;6
\end{array}
&lt;/math&gt;

&lt;li&gt; Can the equation &lt;math&gt; 5x-3y=2 &lt;/math&gt; be derived, by a sequence of
Gaussian reduction steps, from the equations in this system?

:&lt;math&gt;
\begin{array}{*{2}{rc}r}
2x  &amp;+  &amp;2y &amp;=  &amp;5  \\
3x  &amp;+  &amp;y  &amp;=  &amp;4
\end{array}
&lt;/math&gt;

&lt;li&gt; Can the equation &lt;math&gt; 6x-9y+5z=-2 &lt;/math&gt; be derived, 
by a sequence of
Gaussian reduction steps, from the equations in the system?

:&lt;math&gt;
\begin{array}{*{3}{rc}r}
2x  &amp;+  &amp;y  &amp;-  &amp;z  &amp;=  &amp;4  \\
6x  &amp;-  &amp;3y &amp;+  &amp;z  &amp;=  &amp;5
\end{array}
&lt;/math&gt;

&lt;/ol&gt;
}}
{{TextBox|1=
;Problem 11: 
Prove that, where &lt;math&gt; a,b,\ldots,e &lt;/math&gt; are real numbers
and &lt;math&gt; a\neq 0 &lt;/math&gt;, if

:&lt;math&gt;
ax+by=c
&lt;/math&gt;

has the same solution set as

:&lt;math&gt;
ax+dy=e
&lt;/math&gt;

then they are the same equation.
What if &lt;math&gt; a=0 &lt;/math&gt;?
}}
{{Linear Algebra/Book 2/Recommended}}
{{TextBox|1=
;Problem 12: 
Show that if &lt;math&gt; ad-bc\neq 0 &lt;/math&gt; then

:&lt;math&gt;
\begin{array}{*{2}{rc}r}
ax  &amp;+  &amp;by  &amp;=  &amp;j  \\
cx  &amp;+  &amp;dy  &amp;=  &amp;k  
\end{array}
&lt;/math&gt;

has a unique solution.
}}
{{Linear Algebra/Book 2/Recommended}}
{{TextBox|1=
;Problem 13: 
In the system

:&lt;math&gt;
\begin{array}{*{2}{rc}r}
ax  &amp;+  &amp;by  &amp;=  &amp;c  \\
dx  &amp;+  &amp;ey  &amp;=  &amp;f  
\end{array}
&lt;/math&gt;

each of the equations describes a line in the &lt;math&gt; xy &lt;/math&gt;-plane.
By geometrical reasoning, show that there are three possibilities:
there is a unique solution, there is no solution, 
and there are infinitely many solutions.
}}
{{TextBox|1=
;Problem 14 {{anchor|ex:ProveGaussMethod}}: &lt;!--\label{ex:ProveGaussMethod}--&gt;
Finish the proof of [[#th:GaussMethod|Theorem 1.4]]&lt;!--\ref{th:GaussMethod}--&gt;.
}}
{{TextBox|1=
;Problem 15: 
Is there a two-unknowns
linear system whose solution set is all of &lt;math&gt; \mathbb{R}^2 &lt;/math&gt;?
}}
{{Linear Algebra/Book 2/Recommended}}
{{TextBox|1=
;Problem 16: 
Are any of the operations used in Gauss' method
redundant?
That is, can any of the operations be synthesized from the others?
}}
{{TextBox|1=
;Problem 17: 
Prove that each operation of Gauss' method is reversible.
That is, show that if two systems are related by a row operation
&lt;math&gt;S_1\rightarrow S_2&lt;/math&gt; then there is a row operation to go back
&lt;math&gt;S_2\rightarrow S_1&lt;/math&gt;.
}}
{{TextBox|1=
;? Problem 18:  
A box holding pennies, nickels and dimes contains
thirteen coins with a total value of &lt;math&gt; 83 &lt;/math&gt; cents.
How many coins of each type are in the box?
{{harv|Anton|1987}}
}}
{{TextBox|1=
;? Problem 19: 
Four positive integers are given.
Select any three of the integers, find their arithmetic average,
and add this result to the fourth integer.
Thus the numbers 29, 23, 21, and 17 are obtained.
One of the original integers is:
&lt;ol type=1 start=1&gt;
&lt;li&gt; 19
&lt;li&gt; 21
&lt;li&gt; 23
&lt;li&gt; 29
&lt;li&gt; 17
&lt;/ol&gt;
{{harv|Salkind|1975|loc=1955 problem 38}}
}}
{{Linear Algebra/Book 2/Recommended}}
{{TextBox|1=
;? Problem 20:  
Laugh at this:  &lt;math&gt; \mbox{AHAHA}+\mbox{TEHE}=\mbox{TEHAW} &lt;/math&gt;.
It resulted from substituting a code letter for each digit of a simple
example in addition, and it is required to identify the letters
and prove the solution unique {{harv|Ransom|Gupta|1935}}.
}}
{{TextBox|1=
;? Problem 21: 
The Wohascum County Board of Commissioners, which has 20 members, 
recently had to elect a President.
There were three candidates (&lt;math&gt;A&lt;/math&gt;, &lt;math&gt;B&lt;/math&gt;, and &lt;math&gt;C&lt;/math&gt;); on each ballot
the three
candidates were to be listed in order of preference, with no abstentions.
It was found that 11 members, a majority, preferred &lt;math&gt;A&lt;/math&gt; over &lt;math&gt;B&lt;/math&gt;
(thus the other 9 preferred &lt;math&gt;B&lt;/math&gt; over &lt;math&gt;A&lt;/math&gt;).
Similarly, it was found that 12 members preferred &lt;math&gt;C&lt;/math&gt; over &lt;math&gt;A&lt;/math&gt;.
Given these results, it was suggested that &lt;math&gt;B&lt;/math&gt; should withdraw, to enable
a runoff election between &lt;math&gt;A&lt;/math&gt; and &lt;math&gt;C&lt;/math&gt;.
However, &lt;math&gt;B&lt;/math&gt; protested, and it was then found that 14 members preferred
&lt;math&gt;B&lt;/math&gt; over &lt;math&gt;C&lt;/math&gt;!
The Board has not yet recovered from the resulting confusion.
Given that every possible order of &lt;math&gt;A&lt;/math&gt;, &lt;math&gt;B&lt;/math&gt;, &lt;math&gt;C&lt;/math&gt; appeared on at least 
one ballot, how many members voted for &lt;math&gt;B&lt;/math&gt; as their first choice {{harv|Gilbert|Krusemeyer|Larson|1993|loc=Problem number 2}}?

}}
{{TextBox|1=
;? Problem 22:   
&quot;This system of &lt;math&gt;n&lt;/math&gt; linear equations with
&lt;math&gt;n&lt;/math&gt; unknowns,&quot; said the Great Mathematician, &quot;has a curious
property.&quot;

&quot;Good heavens!&quot; said the Poor Nut,  &quot;What is it?&quot;

&quot;Note,&quot; said the Great Mathematician, &quot;that the constants are in
arithmetic progression.&quot;

&quot;It's all so clear when you explain it!&quot; said the Poor Nut.
&quot;Do you mean like &lt;math&gt; 6x+9y=12 &lt;/math&gt; and &lt;math&gt; 15x+18y=21 &lt;/math&gt;?&quot;

&quot;Quite so,&quot; said the Great Mathematician, pulling out his bassoon.
&quot;Indeed, even larger systems can be solved regardless of their progression.
Can you find their solution?&quot;

&quot;Good heavens!&quot; cried the Poor Nut, &quot;I am baffled.&quot;

Are you? {{harv|Dudley|Lebow|Rothman|1963}}
}}
&lt;noinclude&gt;
[[/Solutions/]]

==References==
* {{citation|first=Howard|last=Anton|title=Elementary Linear Algebra|publisher=John Wiley &amp; Sons|year=1987}}.
* {{citation|first1=Underwood (proposer)|last1=Dudley|first2=Arnold (proposer)|last2=Lebow|first3=David (solver)|last3=Rothman|title=Elemantary problem 1151|journal=American Mathematical Monthly|volume=70|number=1|year=1963|pages=93}}.
* {{citation|first1=George T.|last1=Gilbert|first2=Mark|last2=Krusemeyer|first3=Loren C.|last3=Larson|title=The Wohascum County Problem Book|publisher=The Mathematical Association of America|year=1993}}.
* {{citation|first1=W. R. (proposer)|last1=Ransom|first2=Hansraj (solver)|last2=Gupta|title=Elementary problem 105|journal=American Mathematical Monthly|volume=42|number=1|year=1935|pages=47}}.
* {{citation|first=Charles T.|last=Salkind|title=Contest Problem Book No 1: Annual High School Mathematics Examinations 1950-1960|year=1975}}.

{{navigation|Book=Linear Algebra
|current=Gauss' Method
|previous=Solving Linear Systems
|next=Describing the Solution Set}}

{{BookCat}}
&lt;/noinclude&gt;</text>
      <sha1>h4px50189f1u4sh0s4vzfluf1tqjjpn</sha1>
    </revision>
  </page>
  <page>
    <title>Cookbook:Nasi Goreng (Indonesian Fried Rice)</title>
    <ns>102</ns>
    <id>152729</id>
    <revision>
      <id>4675785</id>
      <parentid>4512969</parentid>
      <timestamp>2026-10-13T05:46:44Z</timestamp>
      <contributor>
        <username>Arlorecruitz</username>
        <id>3628307</id>
      </contributor>
      <origin>4675785</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3284" sha1="bn1ng2ewa3qa9rtrusif4axgpwwin5p" xml:space="preserve">__NOTOC__
{{recipesummary|category=Indonesian recipes|servings=2|time=20 minutes|difficulty=2
}}{{recipe}} | [[Cookbook:Cuisine of Indonesia|Cuisine of Indonesia]]
== Ingredients ==
*2 servings of [[Cookbook:Steamed Rice|steamed rice]]
*2 [[Cookbook:Egg|eggs]]
*1 clove [[Cookbook:Garlic|garlic]]
*2 [[Cookbook:Shallot|shallots]]
*1 red [[Cookbook:Chiles|chile pepper]]
*1 [[Cookbook:Tablespoon|Tbsp]] [[Cookbook:Fish Oil|fish oil]]
*10 [[Cookbook:Milliliter|ml]] [[Cookbook:Coconut oil|coconut oil]]
*Sweet [[Cookbook:Soy Sauce|soy sauce]]
*Salty soy sauce or [[Cookbook:Salt|salt]]
*Ground pepper

=== Optional ingredients ===
*20 [[Cookbook:Bitter Bean|stink beans]] or [[Cookbook:Green Bean|green beans]]
*100 g [[Cookbook:Chicken|chicken]] fillet, cut into small pieces
*100 g small [[Cookbook:Prawn|prawns]]
*4 fish meatballs
*2 spoons of tinned [[Cookbook:Corned Beef|corned beef]]
*1 [[Cookbook:Cucumber|cucumber]]
*[[Cookbook:Slicing|Sliced]] [[Cookbook:Hot Dog|hot dogs]] or [[Cookbook:Sausage|sausages]]
*Sliced [[Cookbook:Chicken|chicken]] [[Cookbook:Liver|liver]]
*[[Cookbook:Cauliflower|Cauliflower]]
*Sliced salted dried fish
*[[Cookbook:Green Onion|Spring onion]]

== Procedure ==
# Slice shallots and red pepper into thin slices.
# Crush garlic, peel of the skin, and [[Cookbook:Mince|mince]] well.
# Slice stinky beans in half, or as desired.
# Heat oil in [[Cookbook:Wok|wok]], add the chicken or prawn, and [[Cookbook:Stir-frying|stir fry]] until done.
# Add shallot, pepper, garlic and stink beans. Stir until garlic turns golden.
# Crack in the eggs, and stir fry until half done.
# Add the steamed rice, and stir until all mixed.
# Add soy sauces, salt, and ground pepper as desired.
# Serve on plates, adding fresh cucumber slices or tomatoes as garnish.

== Notes, tips, and variations ==
*Use cold rice, preferably leftover from a day before. Unsticky rice is easier to cook and preferred by some.
*Some prefer not to use stinky beans and use green peas or green beans as a substitute. This will give a nice shade of green.

=== Variations ===
*If you are cooking with corned beef, leave the sweet soy sauce out. This is a variation of nasi goreng called ''nasi goreng kornet'' or corned beef fried rice.
*Try including a sunny side up egg as accompaniment on the side.
*Some also prefer adding vegetables such as cucumber and tomatoes.
*You can use salted fish as a variation to make ''nasi goreng ikan asin'', or salted fish fried rice. In this case, leave out the sweet soy sauce.
*Substitute green peas with sliced spring onions, adding them after the rice has been added to the wok. Spring onions will give nice aroma and color to the fried rice.
*Prawn cracker/chips are a nice condiment on the side.

[[Category:Recipes using rice]]
[[Category:Indonesian recipes]]
[[Category:Recipes_with_metric_units]]
[[Category:Recipes using egg]]
[[Category:Recipes using corned beef]]
[[Category:Recipes using bitter bean]]
[[Category:Recipes using chicken]]
[[Category:Recipes using chile]]
[[Category:Recipes using coconut oil]]
[[Category:Recipes using cucumber]]
[[Category:Recipes using garlic]]
[[Category:Recipes using hot dog]]
[[Category:Recipes using liver]]

[[ta:சமையல் நூல்/மரக்கறி நாசி கொரெங்]]</text>
      <sha1>bn1ng2ewa3qa9rtrusif4axgpwwin5p</sha1>
    </revision>
  </page>
  <page>
    <title>Wikibooks:Reading room/Proposals</title>
    <ns>4</ns>
    <id>155682</id>
    <revision>
      <id>4675751</id>
      <parentid>4675673</parentid>
      <timestamp>2026-10-12T16:06:16Z</timestamp>
      <contributor>
        <username>~2026-54774-31</username>
        <id>3628254</id>
      </contributor>
      <comment>/* Anahaw Street */ new section</comment>
      <origin>4675751</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="19728" sha1="92qdzox30zhht97599nflm1cy0aop1f" xml:space="preserve">__NEWSECTIONLINK__ {{Discussion Rooms}} {{Shortcut|WB:RFC|WB:PROPOSALS}} {{TOC left&lt;!--|limit=2--&gt;}}

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}}
&lt;!--Take threads to archive below this line--&gt;
&lt;!--Add new threads to bottom of page--&gt;

== New gadget to browse subpages ==

Hi all! I developed a gadget to easily browse subpages through a collapsible menu, that I think might be useful in Wikibooks. Here's a little demo video:

[[File:Subpages_gadget_demo.webm|frameless]]

To test it yourself, add the following to [[Special:MyPage/common.js|your common.js]]:

&lt;syntaxhighlight lang=&quot;javascript&quot;&gt;
mw.loader.load( '//www.mediawiki.org/w/load.php?modules=ext.gadget.Global-Subpages' );
&lt;/syntaxhighlight&gt;

If you find it useful, I can enable it as a gadget to make it generally available from the preferences. Thoughts? Cheers! [[User:Sophivorus|Sophivorus]] ([[User talk:Sophivorus|discuss]] • [[Special:Contributions/Sophivorus|contribs]]) 16:02, 2 July 2026 (UTC)

:Wikibooks relies heavily on subpages, so this is a nice addition. Merci. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 16:43, 2 July 2026 (UTC)
:This could be extremely useful for books here!! I'll note, though, that it doesn't work quite right with the vector legacy skin (what I use). —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:20, 3 July 2026 (UTC)
: @[[User:Sophivorus|Sophivorus]] I will be the one in charge installing this as a gadget since there is no objection, but what dependecies does this gadget need to use? You might also want to read Kittycataclysm's suggestion above. ''Muchos saludos''. [[User:Codename Noreste|&lt;span style=&quot;color:#0024FF&quot;&gt;Codename Noreste&lt;/span&gt;]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 23:08, 9 July 2026 (UTC)
::@[[User:Codename Noreste|Codename Noreste]] Hi! I just fixed the issue with Vector legacy and also for other skins. Regarding dependencies, this gadget requires &lt;code&gt;mediawiki.api&lt;/code&gt; and &lt;code&gt;@wikimedia/codex&lt;/code&gt;. If you want to take care of the installation, please do not copy-paste the source code, but rather load the global version using &lt;code&gt;mw.loader.load( '//www.mediawiki.org/w/load.php?modules=ext.gadget.Global-Subpages' );&lt;/code&gt;, like other [[mw:Global gadgets|global gadgets]]. Thanks! [[User:Sophivorus|Sophivorus]] ([[User talk:Sophivorus|discuss]] • [[Special:Contributions/Sophivorus|contribs]]) 14:22, 22 July 2026 (UTC)
::: I put the code on the gadgets definition page @[[User:Sophivorus|Sophivorus]], but feel free to fix what I placed. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 21:45, 22 July 2026 (UTC)

== Breadcrumbs in the title ==

Hi! I think breadcrumbs would be more intuitive, compact and cleaner if they were integrated into the title rather than below it, like so:

&lt;gallery&gt;
Wikisource breadcrumbs proposal (before).png|Current breadcrumbs
Wikisource breadcrumbs proposal (after).png|Proposed breadcrumbs
&lt;/gallery&gt;

What do you think? [[User:Sophivorus|Sophivorus]] ([[User talk:Sophivorus|discuss]] • [[Special:Contributions/Sophivorus|contribs]]) 16:02, 17 August 2026 (UTC)

:I appreciate the effort, but I don't see a big difference or that one would be more usable than another. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 19:14, 17 August 2026 (UTC)

:I like proposal and I think it would be an improvement. Having the breadcrumbs twice, as in the current system, creates a redundant ui element. I also think the formatting around the forward slashes in the &quot;new&quot; version better conveys that they have specific technical meaning and are not part of the name of the page. --[[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 14:52, 7 October 2026 (UTC)

== Approve [[Wikibooks:CheckUser]] as a local policy? ==
Some of the text was based off of the global CheckUser policy, but in this case, should we approve [[Wikibooks:CheckUser]] as a local policy? There is a special clause allowing stewards to perform checks even during non-emergency situations (as set in [[Wikibooks:Global rights policy]]). I have yet to include a part where users may request CU checks. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 21:55, 13 September 2026 (UTC)

:I'm somewhat just unsure on what the benefit of making this policy would be. Sure, there's strength in policy, of course. But this seems to be doing fine overall as an information page, no? It doesn't differ very much from the global CU policy, so I'm not sure that a page without any Wikibooks-specific information really benefits from policy status. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 00:22, 14 September 2026 (UTC)
:I would {{support}} this. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:26, 20 September 2026 (UTC)

== FlaggedRevs again ==
&lt;div class=&quot;cd-moveMark&quot;&gt;''Moved from [[Wikibooks:Reading room/General#FlaggedRevs again]].  [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:01, 1 October 2026 (UTC)''&lt;/div&gt;
Hi all. I already know there were various topics over the years about this subject, but I was considering for the project on whether we should remove this extension from this project, and go back to using MediaWiki's page patrol system.

Currently, there is a backlog of more than 3000 unreviewed edits (some going back as far as a few years ago); that’s why I started this discussion here.

{{collapse top}}
* &lt;code&gt;autoreview&lt;/code&gt; and &lt;code&gt;editor&lt;/code&gt; would be &lt;code&gt;autopatrolled&lt;/code&gt; and &lt;code&gt;patroller&lt;/code&gt;, respectively.
* &lt;code&gt;wgUseNPPatrol&lt;/code&gt; and &lt;code&gt;wgUseFilePatrol&lt;/code&gt; would be re-enabled for English Wikibooks.
* &lt;code&gt;autopatrol&lt;/code&gt; and &lt;code&gt;patrol&lt;/code&gt; would be re-assigned back to sysops and their respective user groups.
* &lt;code&gt;patroller&lt;/code&gt; would also have &lt;code&gt;rollback&lt;/code&gt; and &lt;code&gt;suppressredirect&lt;/code&gt; and its rate limit untouched.
{{collapse bottom}}

Best, [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 12:56, 30 September 2026 (UTC)

:{{s}} the removal of FlaggedRevs. Inasmuch as the extension works at all, it works best when it is used selectively on projects like Wikipedia, for individual high-traffic pages with lots of watchers which are subject to vandalism or controversy. Wikibooks is not a good use case for this extension. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 15:51, 1 October 2026 (UTC)
:{{s}} I don't see any way that backlog ever gets cleared, frankly, and if it isn't going to be cleared, we might as well go to something easier, which is the normal page patrol system, which works well off of [[Special:NewPages]] already. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 00:31, 3 October 2026 (UTC)
:{{neutral}} - Wikibooks is not a good use case for this extension, and with 3000 unreviewed edits with no progress at all, it does make sense to remove it. On the other hand, there could be a WikiProject to review each of these edits. For this reason, I am voting neutral [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 13:41, 3 October 2026 (UTC)
:: There was the outdated [[Wikibooks:New page patrol]] before this project used FlaggedRevs. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:22, 3 October 2026 (UTC)
:{{support}} the removal of FlaggedRevs from Wikibooks. It's a redundant extension that's not useful in this wiki. --[[User:Agusbou2015|Agusbou2015]] ([[User talk:Agusbou2015|discuss]] • [[Special:Contributions/Agusbou2015|contribs]]) 21:53, 3 October 2026 (UTC)
:{{Support}}. Several years ago I spent hundreds of hours trying to do the first review of every page. I managed to get all the root pages done but only got as far as &quot;E&quot; for the other pages. While I was doing this I stopped reviewing changes - and in that time over a 1,000 out of date pages were in the list. I concluded it was an impossible task unless lots of people joined in the work but that didn't happen and I doubt it ever will. I do think it has value for Wikijunior in showing the last reviewed page rather than the possibly offensively vandalised latest revision, but other than that it's a waste of time. At some point the extension will get fully deprecated and we'll be forced to stop using it anyway. [[User:MarcGarver|MarcGarver]] ([[User talk:MarcGarver|discuss]] • [[Special:Contributions/MarcGarver|contribs]]) 09:53, 6 October 2026 (UTC)
:Will &lt;code&gt;patroller&lt;/code&gt; be granted automatically? [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 13:24, 6 October 2026 (UTC)
:: Unfortunately, no. Since we will stop using FlaggedRevs, the patroller user group will not be granted automatically and thus will have to be manually given out by administrators. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 13:46, 6 October 2026 (UTC)
:::@[[User:Codename Noreste|Codename Noreste]]: And are we planning on giving back the &lt;code&gt;patroller&lt;/code&gt; right to existing reviewers? Or will they have to manually reapply? [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 02:30, 8 October 2026 (UTC)
:::: I have a plan: any former reviewer who has been active recently in the past two years will have patroller rights. This will be done to reduce a huge amount of inactive former reviewers. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 12:26, 8 October 2026 (UTC)
::::Keep the name the same; just remove the reviewer right. After all, patrolling is a form of reviewing. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 18:52, 8 October 2026 (UTC)
::::: Do we have to use the term {{tq|reviewing}} instead of {{tq|patrolling}}? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:57, 8 October 2026 (UTC)
:::{{ping|Codename Noreste}} Is there a reason that we should not simply give the reviewer group the &lt;code&gt;patrol&lt;/code&gt; right, and keep the auto-granting going? [[Wikibooks:Reviewers#Automatic criteria]] does not appear to be FlaggedRevs-specific, so auto-promotion should still be able to continue even without FlaggedRevs, and reviewers could simply become patrollers (in the technical sense). [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 07:55, 10 October 2026 (UTC)
:::: I believe that would require some additional code on InitialiseSettings.php, and as for &lt;code&gt;reviewer&lt;/code&gt;, I'm not sure we should still use that user group term over &lt;code&gt;patroller&lt;/code&gt; as per the point {{tq|Special groups on small wikis}} on [[m:Limits to configuration changes]]. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 13:58, 10 October 2026 (UTC)
: If you take a look at the extended content, I also included what I also proposed too. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:19, 6 October 2026 (UTC)
:{{comment}}. The [[mw:Extension:FlaggedRevs|FlaggedRevs extension]] is not recommended for production use, per Mediawiki. On this basis alone we should discontinue use of it. However, we haven't determined if page patrolling is the best replacement. There are [[mw:Content approval extensions|alternative extensions]] and the mediawiki page for FlaggedRevs specifically recommends [[mw:Extension:Approved Revs|'''Approved Revs extension''']]. We should determine which of page patrolling or these extensions is the most appropriate antivandalism tool first. (after all, according to [[Help:Tracking_changes#Reviewing_pages]], the purpose of FlaggedRevs is to be &quot;our primary counter-vandalism tool&quot;). --[[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 14:48, 7 October 2026 (UTC)
:: Approved Revs would require significant testing and approval per [[mw:Writing an extension for deployment]]. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 16:35, 7 October 2026 (UTC)

== Disable (some) page creation by temporary accounts ==
Creating a new book, or adding a chapter to an existing book, is a significant action, and users performing this action should be available to discuss it. Additionally, in practice, most page creations by temp accounts are out of scope, if not outright vandalism. (See https://en.wikibooks.org/w/index.php?title=Special:Log&amp;type=create for some examples.)

As such, I'd like to propose that the wiki require a registered account to create pages in any non-talk namespace. Temporary accounts will still be able to edit existing pages, or to create talk pages to start discussions. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:48, 1 October 2026 (UTC)
: From a technical point of view, this would require moving &lt;code&gt;createpage&lt;/code&gt; from unregistered users (&lt;code&gt;&lt;nowiki&gt;*&lt;/nowiki&gt;&lt;/code&gt;) to registered users (&lt;code&gt;user&lt;/code&gt;), but that would mean every non-registered user may not be able to create pages in every namespace, but talk pages.
: Another solution would be to add [[mw:Extension:ArticleCreationWorkflow]] to this project, but we don't have a system to create drafts (or similar).
: And a final solution would be to create an edit filter disallowing unregistered users from creating pages in mainspace. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:43, 1 October 2026 (UTC)
:: Just to note, please read the first point of [[m:Limits to configuration changes#Changes that are likely to be declined]] (Disable non-autoconfirmed page creation). [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:50, 1 October 2026 (UTC)
:::What I'm proposing is that we require a registered account for page creation, not autoconfirmed. enwiki (as well as a few other wikis) already use this configuration - it's not new. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 19:58, 1 October 2026 (UTC)
:::: Okay, but I provided some alternatives above. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 20:06, 1 October 2026 (UTC)
: In that case, I have no objections here. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:03, 6 October 2026 (UTC)
:I would propose the use of autoconfirmed, to better patrol new pages that are being created. There are countless advertisement pages being created on Wikibooks, usually in the user's userpage. The use of a registered account proposed by Omphalographer therefore may have some limitations. I agree with the proposal to make new pages strictly autoconfirmed. If a user wishes to create a page, there could be a feature for reviewers/patrollers to check such pages that are being created. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 13:36, 9 October 2026 (UTC)
:: You might want to read my point about limits to configuration changes. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:53, 9 October 2026 (UTC)
:Why turn off potential good contributors by telling them they must register AND log-in in order to contribute? The problem at Wikibooks right now is the dearth of contributions, not vandalism, I think (?). 
:* Anons are already precluded from editing pages that have been &quot;protected&quot; by admins. 
:* Anon user contributions are automatically marked for Review before they become public
:* There are less than 500 anon accounts that have contributed more than one edit to Wikibooks? 
:Is it really necessary to stop us from contributing to Wikibooks? [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 00:19, 10 October 2026 (UTC)
:: {{ping|~2026-40500-29}} The initial question was not whether registered accounts can contribute, it is whether temporary accounts can create pages. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:48, 10 October 2026 (UTC)
:::Isn't the creation of new pages a subset of potential contributions to Wikibooks? Are you saying that some members in good standing of this community are only allowed to correct obvious spelling and grammar mistakes by others? [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 19:23, 11 October 2026 (UTC)
:Limiting page creation to registered users might reduce new spam/promotional/out of scope pages. I disagree with 2026-405000-29 that requiring account registration is unnecessarily burdensome for new editors. 
:I don't know where the number &gt;500 anon accounts have contributed more than one edit comes from and it seems unlikely to me: that would mean there have only been 23 anon editors per year since wikibooks was founded. Looking at Special:RecentChanges there seems to be four or five anon editors a day. 
:Overall I think it is a reasonable restriction. I can't speak to the technical aspects of this change (re configuration changes, vs. autoconfirmed patrolling, etc) but if it is easy to implement I support it. [[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 10:13, 12 October 2026 (UTC)

== Anahaw Street ==
@ma,april melendrez[[Calculus/Functions]] [[Special:Contributions/~2026-54774-31|~2026-54774-31]] ([[User talk:~2026-54774-31|talk]]) 16:06, 12 October 2026 (UTC)</text>
      <sha1>92qdzox30zhht97599nflm1cy0aop1f</sha1>
    </revision>
    <revision>
      <id>4675753</id>
      <parentid>4675751</parentid>
      <timestamp>2026-10-12T16:10:56Z</timestamp>
      <contributor>
        <username>Koavf</username>
        <id>16549</id>
      </contributor>
      <minor />
      <comment>[[WB:REVERT|Reverted]] edit by [[Special:Contributions/~2026-54774-31|~2026-54774-31]] ([[User talk:~2026-54774-31|talk]]) to last version by JCrue</comment>
      <origin>4675673</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="19544" sha1="06aqlkgxsa1xbkjuyx7p1tv28l6cc4k" xml:space="preserve">__NEWSECTIONLINK__ {{Discussion Rooms}} {{Shortcut|WB:RFC|WB:PROPOSALS}} {{TOC left&lt;!--|limit=2--&gt;}}

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}}
&lt;!--Take threads to archive below this line--&gt;
&lt;!--Add new threads to bottom of page--&gt;

== New gadget to browse subpages ==

Hi all! I developed a gadget to easily browse subpages through a collapsible menu, that I think might be useful in Wikibooks. Here's a little demo video:

[[File:Subpages_gadget_demo.webm|frameless]]

To test it yourself, add the following to [[Special:MyPage/common.js|your common.js]]:

&lt;syntaxhighlight lang=&quot;javascript&quot;&gt;
mw.loader.load( '//www.mediawiki.org/w/load.php?modules=ext.gadget.Global-Subpages' );
&lt;/syntaxhighlight&gt;

If you find it useful, I can enable it as a gadget to make it generally available from the preferences. Thoughts? Cheers! [[User:Sophivorus|Sophivorus]] ([[User talk:Sophivorus|discuss]] • [[Special:Contributions/Sophivorus|contribs]]) 16:02, 2 July 2026 (UTC)

:Wikibooks relies heavily on subpages, so this is a nice addition. Merci. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 16:43, 2 July 2026 (UTC)
:This could be extremely useful for books here!! I'll note, though, that it doesn't work quite right with the vector legacy skin (what I use). —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:20, 3 July 2026 (UTC)
: @[[User:Sophivorus|Sophivorus]] I will be the one in charge installing this as a gadget since there is no objection, but what dependecies does this gadget need to use? You might also want to read Kittycataclysm's suggestion above. ''Muchos saludos''. [[User:Codename Noreste|&lt;span style=&quot;color:#0024FF&quot;&gt;Codename Noreste&lt;/span&gt;]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 23:08, 9 July 2026 (UTC)
::@[[User:Codename Noreste|Codename Noreste]] Hi! I just fixed the issue with Vector legacy and also for other skins. Regarding dependencies, this gadget requires &lt;code&gt;mediawiki.api&lt;/code&gt; and &lt;code&gt;@wikimedia/codex&lt;/code&gt;. If you want to take care of the installation, please do not copy-paste the source code, but rather load the global version using &lt;code&gt;mw.loader.load( '//www.mediawiki.org/w/load.php?modules=ext.gadget.Global-Subpages' );&lt;/code&gt;, like other [[mw:Global gadgets|global gadgets]]. Thanks! [[User:Sophivorus|Sophivorus]] ([[User talk:Sophivorus|discuss]] • [[Special:Contributions/Sophivorus|contribs]]) 14:22, 22 July 2026 (UTC)
::: I put the code on the gadgets definition page @[[User:Sophivorus|Sophivorus]], but feel free to fix what I placed. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 21:45, 22 July 2026 (UTC)

== Breadcrumbs in the title ==

Hi! I think breadcrumbs would be more intuitive, compact and cleaner if they were integrated into the title rather than below it, like so:

&lt;gallery&gt;
Wikisource breadcrumbs proposal (before).png|Current breadcrumbs
Wikisource breadcrumbs proposal (after).png|Proposed breadcrumbs
&lt;/gallery&gt;

What do you think? [[User:Sophivorus|Sophivorus]] ([[User talk:Sophivorus|discuss]] • [[Special:Contributions/Sophivorus|contribs]]) 16:02, 17 August 2026 (UTC)

:I appreciate the effort, but I don't see a big difference or that one would be more usable than another. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 19:14, 17 August 2026 (UTC)

:I like proposal and I think it would be an improvement. Having the breadcrumbs twice, as in the current system, creates a redundant ui element. I also think the formatting around the forward slashes in the &quot;new&quot; version better conveys that they have specific technical meaning and are not part of the name of the page. --[[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 14:52, 7 October 2026 (UTC)

== Approve [[Wikibooks:CheckUser]] as a local policy? ==
Some of the text was based off of the global CheckUser policy, but in this case, should we approve [[Wikibooks:CheckUser]] as a local policy? There is a special clause allowing stewards to perform checks even during non-emergency situations (as set in [[Wikibooks:Global rights policy]]). I have yet to include a part where users may request CU checks. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 21:55, 13 September 2026 (UTC)

:I'm somewhat just unsure on what the benefit of making this policy would be. Sure, there's strength in policy, of course. But this seems to be doing fine overall as an information page, no? It doesn't differ very much from the global CU policy, so I'm not sure that a page without any Wikibooks-specific information really benefits from policy status. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 00:22, 14 September 2026 (UTC)
:I would {{support}} this. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:26, 20 September 2026 (UTC)

== FlaggedRevs again ==
&lt;div class=&quot;cd-moveMark&quot;&gt;''Moved from [[Wikibooks:Reading room/General#FlaggedRevs again]].  [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:01, 1 October 2026 (UTC)''&lt;/div&gt;
Hi all. I already know there were various topics over the years about this subject, but I was considering for the project on whether we should remove this extension from this project, and go back to using MediaWiki's page patrol system.

Currently, there is a backlog of more than 3000 unreviewed edits (some going back as far as a few years ago); that’s why I started this discussion here.

{{collapse top}}
* &lt;code&gt;autoreview&lt;/code&gt; and &lt;code&gt;editor&lt;/code&gt; would be &lt;code&gt;autopatrolled&lt;/code&gt; and &lt;code&gt;patroller&lt;/code&gt;, respectively.
* &lt;code&gt;wgUseNPPatrol&lt;/code&gt; and &lt;code&gt;wgUseFilePatrol&lt;/code&gt; would be re-enabled for English Wikibooks.
* &lt;code&gt;autopatrol&lt;/code&gt; and &lt;code&gt;patrol&lt;/code&gt; would be re-assigned back to sysops and their respective user groups.
* &lt;code&gt;patroller&lt;/code&gt; would also have &lt;code&gt;rollback&lt;/code&gt; and &lt;code&gt;suppressredirect&lt;/code&gt; and its rate limit untouched.
{{collapse bottom}}

Best, [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 12:56, 30 September 2026 (UTC)

:{{s}} the removal of FlaggedRevs. Inasmuch as the extension works at all, it works best when it is used selectively on projects like Wikipedia, for individual high-traffic pages with lots of watchers which are subject to vandalism or controversy. Wikibooks is not a good use case for this extension. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 15:51, 1 October 2026 (UTC)
:{{s}} I don't see any way that backlog ever gets cleared, frankly, and if it isn't going to be cleared, we might as well go to something easier, which is the normal page patrol system, which works well off of [[Special:NewPages]] already. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 00:31, 3 October 2026 (UTC)
:{{neutral}} - Wikibooks is not a good use case for this extension, and with 3000 unreviewed edits with no progress at all, it does make sense to remove it. On the other hand, there could be a WikiProject to review each of these edits. For this reason, I am voting neutral [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 13:41, 3 October 2026 (UTC)
:: There was the outdated [[Wikibooks:New page patrol]] before this project used FlaggedRevs. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:22, 3 October 2026 (UTC)
:{{support}} the removal of FlaggedRevs from Wikibooks. It's a redundant extension that's not useful in this wiki. --[[User:Agusbou2015|Agusbou2015]] ([[User talk:Agusbou2015|discuss]] • [[Special:Contributions/Agusbou2015|contribs]]) 21:53, 3 October 2026 (UTC)
:{{Support}}. Several years ago I spent hundreds of hours trying to do the first review of every page. I managed to get all the root pages done but only got as far as &quot;E&quot; for the other pages. While I was doing this I stopped reviewing changes - and in that time over a 1,000 out of date pages were in the list. I concluded it was an impossible task unless lots of people joined in the work but that didn't happen and I doubt it ever will. I do think it has value for Wikijunior in showing the last reviewed page rather than the possibly offensively vandalised latest revision, but other than that it's a waste of time. At some point the extension will get fully deprecated and we'll be forced to stop using it anyway. [[User:MarcGarver|MarcGarver]] ([[User talk:MarcGarver|discuss]] • [[Special:Contributions/MarcGarver|contribs]]) 09:53, 6 October 2026 (UTC)
:Will &lt;code&gt;patroller&lt;/code&gt; be granted automatically? [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 13:24, 6 October 2026 (UTC)
:: Unfortunately, no. Since we will stop using FlaggedRevs, the patroller user group will not be granted automatically and thus will have to be manually given out by administrators. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 13:46, 6 October 2026 (UTC)
:::@[[User:Codename Noreste|Codename Noreste]]: And are we planning on giving back the &lt;code&gt;patroller&lt;/code&gt; right to existing reviewers? Or will they have to manually reapply? [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 02:30, 8 October 2026 (UTC)
:::: I have a plan: any former reviewer who has been active recently in the past two years will have patroller rights. This will be done to reduce a huge amount of inactive former reviewers. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 12:26, 8 October 2026 (UTC)
::::Keep the name the same; just remove the reviewer right. After all, patrolling is a form of reviewing. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 18:52, 8 October 2026 (UTC)
::::: Do we have to use the term {{tq|reviewing}} instead of {{tq|patrolling}}? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:57, 8 October 2026 (UTC)
:::{{ping|Codename Noreste}} Is there a reason that we should not simply give the reviewer group the &lt;code&gt;patrol&lt;/code&gt; right, and keep the auto-granting going? [[Wikibooks:Reviewers#Automatic criteria]] does not appear to be FlaggedRevs-specific, so auto-promotion should still be able to continue even without FlaggedRevs, and reviewers could simply become patrollers (in the technical sense). [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 07:55, 10 October 2026 (UTC)
:::: I believe that would require some additional code on InitialiseSettings.php, and as for &lt;code&gt;reviewer&lt;/code&gt;, I'm not sure we should still use that user group term over &lt;code&gt;patroller&lt;/code&gt; as per the point {{tq|Special groups on small wikis}} on [[m:Limits to configuration changes]]. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 13:58, 10 October 2026 (UTC)
: If you take a look at the extended content, I also included what I also proposed too. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:19, 6 October 2026 (UTC)
:{{comment}}. The [[mw:Extension:FlaggedRevs|FlaggedRevs extension]] is not recommended for production use, per Mediawiki. On this basis alone we should discontinue use of it. However, we haven't determined if page patrolling is the best replacement. There are [[mw:Content approval extensions|alternative extensions]] and the mediawiki page for FlaggedRevs specifically recommends [[mw:Extension:Approved Revs|'''Approved Revs extension''']]. We should determine which of page patrolling or these extensions is the most appropriate antivandalism tool first. (after all, according to [[Help:Tracking_changes#Reviewing_pages]], the purpose of FlaggedRevs is to be &quot;our primary counter-vandalism tool&quot;). --[[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 14:48, 7 October 2026 (UTC)
:: Approved Revs would require significant testing and approval per [[mw:Writing an extension for deployment]]. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 16:35, 7 October 2026 (UTC)

== Disable (some) page creation by temporary accounts ==
Creating a new book, or adding a chapter to an existing book, is a significant action, and users performing this action should be available to discuss it. Additionally, in practice, most page creations by temp accounts are out of scope, if not outright vandalism. (See https://en.wikibooks.org/w/index.php?title=Special:Log&amp;type=create for some examples.)

As such, I'd like to propose that the wiki require a registered account to create pages in any non-talk namespace. Temporary accounts will still be able to edit existing pages, or to create talk pages to start discussions. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:48, 1 October 2026 (UTC)
: From a technical point of view, this would require moving &lt;code&gt;createpage&lt;/code&gt; from unregistered users (&lt;code&gt;&lt;nowiki&gt;*&lt;/nowiki&gt;&lt;/code&gt;) to registered users (&lt;code&gt;user&lt;/code&gt;), but that would mean every non-registered user may not be able to create pages in every namespace, but talk pages.
: Another solution would be to add [[mw:Extension:ArticleCreationWorkflow]] to this project, but we don't have a system to create drafts (or similar).
: And a final solution would be to create an edit filter disallowing unregistered users from creating pages in mainspace. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:43, 1 October 2026 (UTC)
:: Just to note, please read the first point of [[m:Limits to configuration changes#Changes that are likely to be declined]] (Disable non-autoconfirmed page creation). [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:50, 1 October 2026 (UTC)
:::What I'm proposing is that we require a registered account for page creation, not autoconfirmed. enwiki (as well as a few other wikis) already use this configuration - it's not new. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 19:58, 1 October 2026 (UTC)
:::: Okay, but I provided some alternatives above. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 20:06, 1 October 2026 (UTC)
: In that case, I have no objections here. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:03, 6 October 2026 (UTC)
:I would propose the use of autoconfirmed, to better patrol new pages that are being created. There are countless advertisement pages being created on Wikibooks, usually in the user's userpage. The use of a registered account proposed by Omphalographer therefore may have some limitations. I agree with the proposal to make new pages strictly autoconfirmed. If a user wishes to create a page, there could be a feature for reviewers/patrollers to check such pages that are being created. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 13:36, 9 October 2026 (UTC)
:: You might want to read my point about limits to configuration changes. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:53, 9 October 2026 (UTC)
:Why turn off potential good contributors by telling them they must register AND log-in in order to contribute? The problem at Wikibooks right now is the dearth of contributions, not vandalism, I think (?). 
:* Anons are already precluded from editing pages that have been &quot;protected&quot; by admins. 
:* Anon user contributions are automatically marked for Review before they become public
:* There are less than 500 anon accounts that have contributed more than one edit to Wikibooks? 
:Is it really necessary to stop us from contributing to Wikibooks? [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 00:19, 10 October 2026 (UTC)
:: {{ping|~2026-40500-29}} The initial question was not whether registered accounts can contribute, it is whether temporary accounts can create pages. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:48, 10 October 2026 (UTC)
:::Isn't the creation of new pages a subset of potential contributions to Wikibooks? Are you saying that some members in good standing of this community are only allowed to correct obvious spelling and grammar mistakes by others? [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 19:23, 11 October 2026 (UTC)
:Limiting page creation to registered users might reduce new spam/promotional/out of scope pages. I disagree with 2026-405000-29 that requiring account registration is unnecessarily burdensome for new editors. 
:I don't know where the number &gt;500 anon accounts have contributed more than one edit comes from and it seems unlikely to me: that would mean there have only been 23 anon editors per year since wikibooks was founded. Looking at Special:RecentChanges there seems to be four or five anon editors a day. 
:Overall I think it is a reasonable restriction. I can't speak to the technical aspects of this change (re configuration changes, vs. autoconfirmed patrolling, etc) but if it is easy to implement I support it. [[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 10:13, 12 October 2026 (UTC)</text>
      <sha1>06aqlkgxsa1xbkjuyx7p1tv28l6cc4k</sha1>
    </revision>
    <revision>
      <id>4675786</id>
      <parentid>4675753</parentid>
      <timestamp>2026-10-13T05:47:13Z</timestamp>
      <contributor>
        <username>~2026-55204-42</username>
        <id>3628308</id>
      </contributor>
      <comment>/* Disable (some) page creation by temporary accounts */ Reply</comment>
      <origin>4675786</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="19673" sha1="6nnxzc82p9h1zyykv736avgqq542og2" xml:space="preserve">__NEWSECTIONLINK__ {{Discussion Rooms}} {{Shortcut|WB:RFC|WB:PROPOSALS}} {{TOC left&lt;!--|limit=2--&gt;}}

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}}
&lt;!--Take threads to archive below this line--&gt;
&lt;!--Add new threads to bottom of page--&gt;

== New gadget to browse subpages ==

Hi all! I developed a gadget to easily browse subpages through a collapsible menu, that I think might be useful in Wikibooks. Here's a little demo video:

[[File:Subpages_gadget_demo.webm|frameless]]

To test it yourself, add the following to [[Special:MyPage/common.js|your common.js]]:

&lt;syntaxhighlight lang=&quot;javascript&quot;&gt;
mw.loader.load( '//www.mediawiki.org/w/load.php?modules=ext.gadget.Global-Subpages' );
&lt;/syntaxhighlight&gt;

If you find it useful, I can enable it as a gadget to make it generally available from the preferences. Thoughts? Cheers! [[User:Sophivorus|Sophivorus]] ([[User talk:Sophivorus|discuss]] • [[Special:Contributions/Sophivorus|contribs]]) 16:02, 2 July 2026 (UTC)

:Wikibooks relies heavily on subpages, so this is a nice addition. Merci. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 16:43, 2 July 2026 (UTC)
:This could be extremely useful for books here!! I'll note, though, that it doesn't work quite right with the vector legacy skin (what I use). —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:20, 3 July 2026 (UTC)
: @[[User:Sophivorus|Sophivorus]] I will be the one in charge installing this as a gadget since there is no objection, but what dependecies does this gadget need to use? You might also want to read Kittycataclysm's suggestion above. ''Muchos saludos''. [[User:Codename Noreste|&lt;span style=&quot;color:#0024FF&quot;&gt;Codename Noreste&lt;/span&gt;]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 23:08, 9 July 2026 (UTC)
::@[[User:Codename Noreste|Codename Noreste]] Hi! I just fixed the issue with Vector legacy and also for other skins. Regarding dependencies, this gadget requires &lt;code&gt;mediawiki.api&lt;/code&gt; and &lt;code&gt;@wikimedia/codex&lt;/code&gt;. If you want to take care of the installation, please do not copy-paste the source code, but rather load the global version using &lt;code&gt;mw.loader.load( '//www.mediawiki.org/w/load.php?modules=ext.gadget.Global-Subpages' );&lt;/code&gt;, like other [[mw:Global gadgets|global gadgets]]. Thanks! [[User:Sophivorus|Sophivorus]] ([[User talk:Sophivorus|discuss]] • [[Special:Contributions/Sophivorus|contribs]]) 14:22, 22 July 2026 (UTC)
::: I put the code on the gadgets definition page @[[User:Sophivorus|Sophivorus]], but feel free to fix what I placed. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 21:45, 22 July 2026 (UTC)

== Breadcrumbs in the title ==

Hi! I think breadcrumbs would be more intuitive, compact and cleaner if they were integrated into the title rather than below it, like so:

&lt;gallery&gt;
Wikisource breadcrumbs proposal (before).png|Current breadcrumbs
Wikisource breadcrumbs proposal (after).png|Proposed breadcrumbs
&lt;/gallery&gt;

What do you think? [[User:Sophivorus|Sophivorus]] ([[User talk:Sophivorus|discuss]] • [[Special:Contributions/Sophivorus|contribs]]) 16:02, 17 August 2026 (UTC)

:I appreciate the effort, but I don't see a big difference or that one would be more usable than another. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 19:14, 17 August 2026 (UTC)

:I like proposal and I think it would be an improvement. Having the breadcrumbs twice, as in the current system, creates a redundant ui element. I also think the formatting around the forward slashes in the &quot;new&quot; version better conveys that they have specific technical meaning and are not part of the name of the page. --[[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 14:52, 7 October 2026 (UTC)

== Approve [[Wikibooks:CheckUser]] as a local policy? ==
Some of the text was based off of the global CheckUser policy, but in this case, should we approve [[Wikibooks:CheckUser]] as a local policy? There is a special clause allowing stewards to perform checks even during non-emergency situations (as set in [[Wikibooks:Global rights policy]]). I have yet to include a part where users may request CU checks. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 21:55, 13 September 2026 (UTC)

:I'm somewhat just unsure on what the benefit of making this policy would be. Sure, there's strength in policy, of course. But this seems to be doing fine overall as an information page, no? It doesn't differ very much from the global CU policy, so I'm not sure that a page without any Wikibooks-specific information really benefits from policy status. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 00:22, 14 September 2026 (UTC)
:I would {{support}} this. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:26, 20 September 2026 (UTC)

== FlaggedRevs again ==
&lt;div class=&quot;cd-moveMark&quot;&gt;''Moved from [[Wikibooks:Reading room/General#FlaggedRevs again]].  [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:01, 1 October 2026 (UTC)''&lt;/div&gt;
Hi all. I already know there were various topics over the years about this subject, but I was considering for the project on whether we should remove this extension from this project, and go back to using MediaWiki's page patrol system.

Currently, there is a backlog of more than 3000 unreviewed edits (some going back as far as a few years ago); that’s why I started this discussion here.

{{collapse top}}
* &lt;code&gt;autoreview&lt;/code&gt; and &lt;code&gt;editor&lt;/code&gt; would be &lt;code&gt;autopatrolled&lt;/code&gt; and &lt;code&gt;patroller&lt;/code&gt;, respectively.
* &lt;code&gt;wgUseNPPatrol&lt;/code&gt; and &lt;code&gt;wgUseFilePatrol&lt;/code&gt; would be re-enabled for English Wikibooks.
* &lt;code&gt;autopatrol&lt;/code&gt; and &lt;code&gt;patrol&lt;/code&gt; would be re-assigned back to sysops and their respective user groups.
* &lt;code&gt;patroller&lt;/code&gt; would also have &lt;code&gt;rollback&lt;/code&gt; and &lt;code&gt;suppressredirect&lt;/code&gt; and its rate limit untouched.
{{collapse bottom}}

Best, [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 12:56, 30 September 2026 (UTC)

:{{s}} the removal of FlaggedRevs. Inasmuch as the extension works at all, it works best when it is used selectively on projects like Wikipedia, for individual high-traffic pages with lots of watchers which are subject to vandalism or controversy. Wikibooks is not a good use case for this extension. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 15:51, 1 October 2026 (UTC)
:{{s}} I don't see any way that backlog ever gets cleared, frankly, and if it isn't going to be cleared, we might as well go to something easier, which is the normal page patrol system, which works well off of [[Special:NewPages]] already. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 00:31, 3 October 2026 (UTC)
:{{neutral}} - Wikibooks is not a good use case for this extension, and with 3000 unreviewed edits with no progress at all, it does make sense to remove it. On the other hand, there could be a WikiProject to review each of these edits. For this reason, I am voting neutral [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 13:41, 3 October 2026 (UTC)
:: There was the outdated [[Wikibooks:New page patrol]] before this project used FlaggedRevs. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:22, 3 October 2026 (UTC)
:{{support}} the removal of FlaggedRevs from Wikibooks. It's a redundant extension that's not useful in this wiki. --[[User:Agusbou2015|Agusbou2015]] ([[User talk:Agusbou2015|discuss]] • [[Special:Contributions/Agusbou2015|contribs]]) 21:53, 3 October 2026 (UTC)
:{{Support}}. Several years ago I spent hundreds of hours trying to do the first review of every page. I managed to get all the root pages done but only got as far as &quot;E&quot; for the other pages. While I was doing this I stopped reviewing changes - and in that time over a 1,000 out of date pages were in the list. I concluded it was an impossible task unless lots of people joined in the work but that didn't happen and I doubt it ever will. I do think it has value for Wikijunior in showing the last reviewed page rather than the possibly offensively vandalised latest revision, but other than that it's a waste of time. At some point the extension will get fully deprecated and we'll be forced to stop using it anyway. [[User:MarcGarver|MarcGarver]] ([[User talk:MarcGarver|discuss]] • [[Special:Contributions/MarcGarver|contribs]]) 09:53, 6 October 2026 (UTC)
:Will &lt;code&gt;patroller&lt;/code&gt; be granted automatically? [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 13:24, 6 October 2026 (UTC)
:: Unfortunately, no. Since we will stop using FlaggedRevs, the patroller user group will not be granted automatically and thus will have to be manually given out by administrators. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 13:46, 6 October 2026 (UTC)
:::@[[User:Codename Noreste|Codename Noreste]]: And are we planning on giving back the &lt;code&gt;patroller&lt;/code&gt; right to existing reviewers? Or will they have to manually reapply? [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 02:30, 8 October 2026 (UTC)
:::: I have a plan: any former reviewer who has been active recently in the past two years will have patroller rights. This will be done to reduce a huge amount of inactive former reviewers. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 12:26, 8 October 2026 (UTC)
::::Keep the name the same; just remove the reviewer right. After all, patrolling is a form of reviewing. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 18:52, 8 October 2026 (UTC)
::::: Do we have to use the term {{tq|reviewing}} instead of {{tq|patrolling}}? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:57, 8 October 2026 (UTC)
:::{{ping|Codename Noreste}} Is there a reason that we should not simply give the reviewer group the &lt;code&gt;patrol&lt;/code&gt; right, and keep the auto-granting going? [[Wikibooks:Reviewers#Automatic criteria]] does not appear to be FlaggedRevs-specific, so auto-promotion should still be able to continue even without FlaggedRevs, and reviewers could simply become patrollers (in the technical sense). [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 07:55, 10 October 2026 (UTC)
:::: I believe that would require some additional code on InitialiseSettings.php, and as for &lt;code&gt;reviewer&lt;/code&gt;, I'm not sure we should still use that user group term over &lt;code&gt;patroller&lt;/code&gt; as per the point {{tq|Special groups on small wikis}} on [[m:Limits to configuration changes]]. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 13:58, 10 October 2026 (UTC)
: If you take a look at the extended content, I also included what I also proposed too. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:19, 6 October 2026 (UTC)
:{{comment}}. The [[mw:Extension:FlaggedRevs|FlaggedRevs extension]] is not recommended for production use, per Mediawiki. On this basis alone we should discontinue use of it. However, we haven't determined if page patrolling is the best replacement. There are [[mw:Content approval extensions|alternative extensions]] and the mediawiki page for FlaggedRevs specifically recommends [[mw:Extension:Approved Revs|'''Approved Revs extension''']]. We should determine which of page patrolling or these extensions is the most appropriate antivandalism tool first. (after all, according to [[Help:Tracking_changes#Reviewing_pages]], the purpose of FlaggedRevs is to be &quot;our primary counter-vandalism tool&quot;). --[[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 14:48, 7 October 2026 (UTC)
:: Approved Revs would require significant testing and approval per [[mw:Writing an extension for deployment]]. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 16:35, 7 October 2026 (UTC)

== Disable (some) page creation by temporary accounts ==
Creating a new book, or adding a chapter to an existing book, is a significant action, and users performing this action should be available to discuss it. Additionally, in practice, most page creations by temp accounts are out of scope, if not outright vandalism. (See https://en.wikibooks.org/w/index.php?title=Special:Log&amp;type=create for some examples.)

As such, I'd like to propose that the wiki require a registered account to create pages in any non-talk namespace. Temporary accounts will still be able to edit existing pages, or to create talk pages to start discussions. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:48, 1 October 2026 (UTC)
: From a technical point of view, this would require moving &lt;code&gt;createpage&lt;/code&gt; from unregistered users (&lt;code&gt;&lt;nowiki&gt;*&lt;/nowiki&gt;&lt;/code&gt;) to registered users (&lt;code&gt;user&lt;/code&gt;), but that would mean every non-registered user may not be able to create pages in every namespace, but talk pages.
: Another solution would be to add [[mw:Extension:ArticleCreationWorkflow]] to this project, but we don't have a system to create drafts (or similar).
: And a final solution would be to create an edit filter disallowing unregistered users from creating pages in mainspace. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:43, 1 October 2026 (UTC)
:: Just to note, please read the first point of [[m:Limits to configuration changes#Changes that are likely to be declined]] (Disable non-autoconfirmed page creation). [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:50, 1 October 2026 (UTC)
:::What I'm proposing is that we require a registered account for page creation, not autoconfirmed. enwiki (as well as a few other wikis) already use this configuration - it's not new. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 19:58, 1 October 2026 (UTC)
:::: Okay, but I provided some alternatives above. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 20:06, 1 October 2026 (UTC)
: In that case, I have no objections here. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:03, 6 October 2026 (UTC)
:I would propose the use of autoconfirmed, to better patrol new pages that are being created. There are countless advertisement pages being created on Wikibooks, usually in the user's userpage. The use of a registered account proposed by Omphalographer therefore may have some limitations. I agree with the proposal to make new pages strictly autoconfirmed. If a user wishes to create a page, there could be a feature for reviewers/patrollers to check such pages that are being created. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 13:36, 9 October 2026 (UTC)
:: You might want to read my point about limits to configuration changes. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:53, 9 October 2026 (UTC)
:Why turn off potential good contributors by telling them they must register AND log-in in order to contribute? The problem at Wikibooks right now is the dearth of contributions, not vandalism, I think (?). 
:* Anons are already precluded from editing pages that have been &quot;protected&quot; by admins. 
:* Anon user contributions are automatically marked for Review before they become public
:* There are less than 500 anon accounts that have contributed more than one edit to Wikibooks? 
:Is it really necessary to stop us from contributing to Wikibooks? [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 00:19, 10 October 2026 (UTC)
:: {{ping|~2026-40500-29}} The initial question was not whether registered accounts can contribute, it is whether temporary accounts can create pages. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:48, 10 October 2026 (UTC)
:::Isn't the creation of new pages a subset of potential contributions to Wikibooks? Are you saying that some members in good standing of this community are only allowed to correct obvious spelling and grammar mistakes by others? [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 19:23, 11 October 2026 (UTC)
::::500 [[Special:Contributions/~2026-55204-42|~2026-55204-42]] ([[User talk:~2026-55204-42|talk]]) 05:47, 13 October 2026 (UTC)
:Limiting page creation to registered users might reduce new spam/promotional/out of scope pages. I disagree with 2026-405000-29 that requiring account registration is unnecessarily burdensome for new editors. 
:I don't know where the number &gt;500 anon accounts have contributed more than one edit comes from and it seems unlikely to me: that would mean there have only been 23 anon editors per year since wikibooks was founded. Looking at Special:RecentChanges there seems to be four or five anon editors a day. 
:Overall I think it is a reasonable restriction. I can't speak to the technical aspects of this change (re configuration changes, vs. autoconfirmed patrolling, etc) but if it is easy to implement I support it. [[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 10:13, 12 October 2026 (UTC)</text>
      <sha1>6nnxzc82p9h1zyykv736avgqq542og2</sha1>
    </revision>
    <revision>
      <id>4675796</id>
      <parentid>4675786</parentid>
      <timestamp>2026-10-13T07:22:14Z</timestamp>
      <contributor>
        <username>TechVindicator</username>
        <id>3626296</id>
      </contributor>
      <comment>/* Disable (some) page creation by temporary accounts */ Reply</comment>
      <origin>4675796</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="19967" sha1="6os6cr5oadqyxf79svh4jaez0zkwddw" xml:space="preserve">__NEWSECTIONLINK__ {{Discussion Rooms}} {{Shortcut|WB:RFC|WB:PROPOSALS}} {{TOC left&lt;!--|limit=2--&gt;}}

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}}
&lt;!--Take threads to archive below this line--&gt;
&lt;!--Add new threads to bottom of page--&gt;

== New gadget to browse subpages ==

Hi all! I developed a gadget to easily browse subpages through a collapsible menu, that I think might be useful in Wikibooks. Here's a little demo video:

[[File:Subpages_gadget_demo.webm|frameless]]

To test it yourself, add the following to [[Special:MyPage/common.js|your common.js]]:

&lt;syntaxhighlight lang=&quot;javascript&quot;&gt;
mw.loader.load( '//www.mediawiki.org/w/load.php?modules=ext.gadget.Global-Subpages' );
&lt;/syntaxhighlight&gt;

If you find it useful, I can enable it as a gadget to make it generally available from the preferences. Thoughts? Cheers! [[User:Sophivorus|Sophivorus]] ([[User talk:Sophivorus|discuss]] • [[Special:Contributions/Sophivorus|contribs]]) 16:02, 2 July 2026 (UTC)

:Wikibooks relies heavily on subpages, so this is a nice addition. Merci. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 16:43, 2 July 2026 (UTC)
:This could be extremely useful for books here!! I'll note, though, that it doesn't work quite right with the vector legacy skin (what I use). —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:20, 3 July 2026 (UTC)
: @[[User:Sophivorus|Sophivorus]] I will be the one in charge installing this as a gadget since there is no objection, but what dependecies does this gadget need to use? You might also want to read Kittycataclysm's suggestion above. ''Muchos saludos''. [[User:Codename Noreste|&lt;span style=&quot;color:#0024FF&quot;&gt;Codename Noreste&lt;/span&gt;]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 23:08, 9 July 2026 (UTC)
::@[[User:Codename Noreste|Codename Noreste]] Hi! I just fixed the issue with Vector legacy and also for other skins. Regarding dependencies, this gadget requires &lt;code&gt;mediawiki.api&lt;/code&gt; and &lt;code&gt;@wikimedia/codex&lt;/code&gt;. If you want to take care of the installation, please do not copy-paste the source code, but rather load the global version using &lt;code&gt;mw.loader.load( '//www.mediawiki.org/w/load.php?modules=ext.gadget.Global-Subpages' );&lt;/code&gt;, like other [[mw:Global gadgets|global gadgets]]. Thanks! [[User:Sophivorus|Sophivorus]] ([[User talk:Sophivorus|discuss]] • [[Special:Contributions/Sophivorus|contribs]]) 14:22, 22 July 2026 (UTC)
::: I put the code on the gadgets definition page @[[User:Sophivorus|Sophivorus]], but feel free to fix what I placed. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 21:45, 22 July 2026 (UTC)

== Breadcrumbs in the title ==

Hi! I think breadcrumbs would be more intuitive, compact and cleaner if they were integrated into the title rather than below it, like so:

&lt;gallery&gt;
Wikisource breadcrumbs proposal (before).png|Current breadcrumbs
Wikisource breadcrumbs proposal (after).png|Proposed breadcrumbs
&lt;/gallery&gt;

What do you think? [[User:Sophivorus|Sophivorus]] ([[User talk:Sophivorus|discuss]] • [[Special:Contributions/Sophivorus|contribs]]) 16:02, 17 August 2026 (UTC)

:I appreciate the effort, but I don't see a big difference or that one would be more usable than another. ―[[User:Koavf|Justin (&lt;span style=&quot;color:grey&quot;&gt;ko'''a'''&lt;span style=&quot;color:black&quot;&gt;v&lt;/span&gt;f&lt;/span&gt;)]]&lt;span style=&quot;color:red&quot;&gt;❤[[User talk:Koavf|T]]☮[[Special:Contributions/Koavf|C]]☺[[Special:Emailuser/Koavf|M]]☯&lt;/span&gt; 19:14, 17 August 2026 (UTC)

:I like proposal and I think it would be an improvement. Having the breadcrumbs twice, as in the current system, creates a redundant ui element. I also think the formatting around the forward slashes in the &quot;new&quot; version better conveys that they have specific technical meaning and are not part of the name of the page. --[[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 14:52, 7 October 2026 (UTC)

== Approve [[Wikibooks:CheckUser]] as a local policy? ==
Some of the text was based off of the global CheckUser policy, but in this case, should we approve [[Wikibooks:CheckUser]] as a local policy? There is a special clause allowing stewards to perform checks even during non-emergency situations (as set in [[Wikibooks:Global rights policy]]). I have yet to include a part where users may request CU checks. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 21:55, 13 September 2026 (UTC)

:I'm somewhat just unsure on what the benefit of making this policy would be. Sure, there's strength in policy, of course. But this seems to be doing fine overall as an information page, no? It doesn't differ very much from the global CU policy, so I'm not sure that a page without any Wikibooks-specific information really benefits from policy status. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 00:22, 14 September 2026 (UTC)
:I would {{support}} this. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:26, 20 September 2026 (UTC)

== FlaggedRevs again ==
&lt;div class=&quot;cd-moveMark&quot;&gt;''Moved from [[Wikibooks:Reading room/General#FlaggedRevs again]].  [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:01, 1 October 2026 (UTC)''&lt;/div&gt;
Hi all. I already know there were various topics over the years about this subject, but I was considering for the project on whether we should remove this extension from this project, and go back to using MediaWiki's page patrol system.

Currently, there is a backlog of more than 3000 unreviewed edits (some going back as far as a few years ago); that’s why I started this discussion here.

{{collapse top}}
* &lt;code&gt;autoreview&lt;/code&gt; and &lt;code&gt;editor&lt;/code&gt; would be &lt;code&gt;autopatrolled&lt;/code&gt; and &lt;code&gt;patroller&lt;/code&gt;, respectively.
* &lt;code&gt;wgUseNPPatrol&lt;/code&gt; and &lt;code&gt;wgUseFilePatrol&lt;/code&gt; would be re-enabled for English Wikibooks.
* &lt;code&gt;autopatrol&lt;/code&gt; and &lt;code&gt;patrol&lt;/code&gt; would be re-assigned back to sysops and their respective user groups.
* &lt;code&gt;patroller&lt;/code&gt; would also have &lt;code&gt;rollback&lt;/code&gt; and &lt;code&gt;suppressredirect&lt;/code&gt; and its rate limit untouched.
{{collapse bottom}}

Best, [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 12:56, 30 September 2026 (UTC)

:{{s}} the removal of FlaggedRevs. Inasmuch as the extension works at all, it works best when it is used selectively on projects like Wikipedia, for individual high-traffic pages with lots of watchers which are subject to vandalism or controversy. Wikibooks is not a good use case for this extension. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 15:51, 1 October 2026 (UTC)
:{{s}} I don't see any way that backlog ever gets cleared, frankly, and if it isn't going to be cleared, we might as well go to something easier, which is the normal page patrol system, which works well off of [[Special:NewPages]] already. [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 00:31, 3 October 2026 (UTC)
:{{neutral}} - Wikibooks is not a good use case for this extension, and with 3000 unreviewed edits with no progress at all, it does make sense to remove it. On the other hand, there could be a WikiProject to review each of these edits. For this reason, I am voting neutral [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 13:41, 3 October 2026 (UTC)
:: There was the outdated [[Wikibooks:New page patrol]] before this project used FlaggedRevs. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:22, 3 October 2026 (UTC)
:{{support}} the removal of FlaggedRevs from Wikibooks. It's a redundant extension that's not useful in this wiki. --[[User:Agusbou2015|Agusbou2015]] ([[User talk:Agusbou2015|discuss]] • [[Special:Contributions/Agusbou2015|contribs]]) 21:53, 3 October 2026 (UTC)
:{{Support}}. Several years ago I spent hundreds of hours trying to do the first review of every page. I managed to get all the root pages done but only got as far as &quot;E&quot; for the other pages. While I was doing this I stopped reviewing changes - and in that time over a 1,000 out of date pages were in the list. I concluded it was an impossible task unless lots of people joined in the work but that didn't happen and I doubt it ever will. I do think it has value for Wikijunior in showing the last reviewed page rather than the possibly offensively vandalised latest revision, but other than that it's a waste of time. At some point the extension will get fully deprecated and we'll be forced to stop using it anyway. [[User:MarcGarver|MarcGarver]] ([[User talk:MarcGarver|discuss]] • [[Special:Contributions/MarcGarver|contribs]]) 09:53, 6 October 2026 (UTC)
:Will &lt;code&gt;patroller&lt;/code&gt; be granted automatically? [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 13:24, 6 October 2026 (UTC)
:: Unfortunately, no. Since we will stop using FlaggedRevs, the patroller user group will not be granted automatically and thus will have to be manually given out by administrators. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 13:46, 6 October 2026 (UTC)
:::@[[User:Codename Noreste|Codename Noreste]]: And are we planning on giving back the &lt;code&gt;patroller&lt;/code&gt; right to existing reviewers? Or will they have to manually reapply? [[User:JJPMaster|JJP]]&lt;sub&gt;[[User talk:JJPMaster|Mas]]&lt;sub&gt;[[Special:Contributions/JJPMaster|ter]]&lt;/sub&gt;&lt;/sub&gt; ([[wikt:she|she]]/[[wikt:they|they]]) 02:30, 8 October 2026 (UTC)
:::: I have a plan: any former reviewer who has been active recently in the past two years will have patroller rights. This will be done to reduce a huge amount of inactive former reviewers. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 12:26, 8 October 2026 (UTC)
::::Keep the name the same; just remove the reviewer right. After all, patrolling is a form of reviewing. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 18:52, 8 October 2026 (UTC)
::::: Do we have to use the term {{tq|reviewing}} instead of {{tq|patrolling}}? [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:57, 8 October 2026 (UTC)
:::{{ping|Codename Noreste}} Is there a reason that we should not simply give the reviewer group the &lt;code&gt;patrol&lt;/code&gt; right, and keep the auto-granting going? [[Wikibooks:Reviewers#Automatic criteria]] does not appear to be FlaggedRevs-specific, so auto-promotion should still be able to continue even without FlaggedRevs, and reviewers could simply become patrollers (in the technical sense). [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 07:55, 10 October 2026 (UTC)
:::: I believe that would require some additional code on InitialiseSettings.php, and as for &lt;code&gt;reviewer&lt;/code&gt;, I'm not sure we should still use that user group term over &lt;code&gt;patroller&lt;/code&gt; as per the point {{tq|Special groups on small wikis}} on [[m:Limits to configuration changes]]. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 13:58, 10 October 2026 (UTC)
: If you take a look at the extended content, I also included what I also proposed too. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 18:19, 6 October 2026 (UTC)
:{{comment}}. The [[mw:Extension:FlaggedRevs|FlaggedRevs extension]] is not recommended for production use, per Mediawiki. On this basis alone we should discontinue use of it. However, we haven't determined if page patrolling is the best replacement. There are [[mw:Content approval extensions|alternative extensions]] and the mediawiki page for FlaggedRevs specifically recommends [[mw:Extension:Approved Revs|'''Approved Revs extension''']]. We should determine which of page patrolling or these extensions is the most appropriate antivandalism tool first. (after all, according to [[Help:Tracking_changes#Reviewing_pages]], the purpose of FlaggedRevs is to be &quot;our primary counter-vandalism tool&quot;). --[[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 14:48, 7 October 2026 (UTC)
:: Approved Revs would require significant testing and approval per [[mw:Writing an extension for deployment]]. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 16:35, 7 October 2026 (UTC)

== Disable (some) page creation by temporary accounts ==
Creating a new book, or adding a chapter to an existing book, is a significant action, and users performing this action should be available to discuss it. Additionally, in practice, most page creations by temp accounts are out of scope, if not outright vandalism. (See https://en.wikibooks.org/w/index.php?title=Special:Log&amp;type=create for some examples.)

As such, I'd like to propose that the wiki require a registered account to create pages in any non-talk namespace. Temporary accounts will still be able to edit existing pages, or to create talk pages to start discussions. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 18:48, 1 October 2026 (UTC)
: From a technical point of view, this would require moving &lt;code&gt;createpage&lt;/code&gt; from unregistered users (&lt;code&gt;&lt;nowiki&gt;*&lt;/nowiki&gt;&lt;/code&gt;) to registered users (&lt;code&gt;user&lt;/code&gt;), but that would mean every non-registered user may not be able to create pages in every namespace, but talk pages.
: Another solution would be to add [[mw:Extension:ArticleCreationWorkflow]] to this project, but we don't have a system to create drafts (or similar).
: And a final solution would be to create an edit filter disallowing unregistered users from creating pages in mainspace. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:43, 1 October 2026 (UTC)
:: Just to note, please read the first point of [[m:Limits to configuration changes#Changes that are likely to be declined]] (Disable non-autoconfirmed page creation). [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:50, 1 October 2026 (UTC)
:::What I'm proposing is that we require a registered account for page creation, not autoconfirmed. enwiki (as well as a few other wikis) already use this configuration - it's not new. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 19:58, 1 October 2026 (UTC)
:::: Okay, but I provided some alternatives above. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 20:06, 1 October 2026 (UTC)
: In that case, I have no objections here. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 19:03, 6 October 2026 (UTC)
:I would propose the use of autoconfirmed, to better patrol new pages that are being created. There are countless advertisement pages being created on Wikibooks, usually in the user's userpage. The use of a registered account proposed by Omphalographer therefore may have some limitations. I agree with the proposal to make new pages strictly autoconfirmed. If a user wishes to create a page, there could be a feature for reviewers/patrollers to check such pages that are being created. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 13:36, 9 October 2026 (UTC)
:: You might want to read my point about limits to configuration changes. [[User:Codename Noreste|&lt;span style=&quot;color: blue&quot;&gt;Codename Noreste&lt;/span&gt;]] /// [[User talk:Codename Noreste|⭐️✨]] 14:53, 9 October 2026 (UTC)
:Why turn off potential good contributors by telling them they must register AND log-in in order to contribute? The problem at Wikibooks right now is the dearth of contributions, not vandalism, I think (?). 
:* Anons are already precluded from editing pages that have been &quot;protected&quot; by admins. 
:* Anon user contributions are automatically marked for Review before they become public
:* There are less than 500 anon accounts that have contributed more than one edit to Wikibooks? 
:Is it really necessary to stop us from contributing to Wikibooks? [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 00:19, 10 October 2026 (UTC)
:: {{ping|~2026-40500-29}} The initial question was not whether registered accounts can contribute, it is whether temporary accounts can create pages. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 00:48, 10 October 2026 (UTC)
:::Isn't the creation of new pages a subset of potential contributions to Wikibooks? Are you saying that some members in good standing of this community are only allowed to correct obvious spelling and grammar mistakes by others? [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 19:23, 11 October 2026 (UTC)
::::500 [[Special:Contributions/~2026-55204-42|~2026-55204-42]] ([[User talk:~2026-55204-42|talk]]) 05:47, 13 October 2026 (UTC)
::::That message was to {{comment}} that this discussion was about creating pages, not about whether anonymous users can contribute. [[User:TechVindicator|TechVindicator]] ([[User talk:TechVindicator|discuss]] • [[Special:Contributions/TechVindicator|contribs]]) 07:22, 13 October 2026 (UTC)
:Limiting page creation to registered users might reduce new spam/promotional/out of scope pages. I disagree with 2026-405000-29 that requiring account registration is unnecessarily burdensome for new editors. 
:I don't know where the number &gt;500 anon accounts have contributed more than one edit comes from and it seems unlikely to me: that would mean there have only been 23 anon editors per year since wikibooks was founded. Looking at Special:RecentChanges there seems to be four or five anon editors a day. 
:Overall I think it is a reasonable restriction. I can't speak to the technical aspects of this change (re configuration changes, vs. autoconfirmed patrolling, etc) but if it is easy to implement I support it. [[User:JCrue|JCrue]] ([[User talk:JCrue|discuss]] • [[Special:Contributions/JCrue|contribs]]) 10:13, 12 October 2026 (UTC)</text>
      <sha1>6os6cr5oadqyxf79svh4jaez0zkwddw</sha1>
    </revision>
  </page>
  <page>
    <title>Erlang Programming/Creating Web Applications with yaws</title>
    <ns>0</ns>
    <id>189960</id>
    <revision>
      <id>4675750</id>
      <parentid>4662868</parentid>
      <timestamp>2026-10-12T15:50:08Z</timestamp>
      <contributor>
        <username>Acrions</username>
        <id>3509296</id>
      </contributor>
      <comment>fix link? this is the link from wikipedia</comment>
      <origin>4675750</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="798" sha1="a2cq50k9kyix0we5rws7tnsb0mrsppy" xml:space="preserve">Yaws is one of the popular web servers programmed in Erlang. The goals of Yaws is to be a feature rich web server with a multitude of options for the user to configure and deploy their web applications with.

{|width=&quot;100%&quot; cellspacing=&quot;0&quot; cellpadding=&quot;15&quot;  style=&quot;vertical-align:top; margin:0.8em 0;border:1px solid MediumAquamarine;background:honeydew;{{Text default color}};&quot;

|style=&quot;vertical-align:top; border-right: 1px dashed MediumAquamarine&quot;|

== Basic Yaws ==
*{{Yaws chapter/Yaws Basics|sep=
*}}

|valign=&quot;top&quot;|

== Elementary Yaws ==
*{{Yaws chapter/Elementary Yaws|sep=
*}}

|}

{{BookCat}}

== Additional Resources ==
* [https://erlyaws.github.io/ Yaws official website]
* [http://www.erlang.org/ Erlang official website]
* [http://www.erlang.org/doc/ Erlang documentation]


{{Stub}}</text>
      <sha1>a2cq50k9kyix0we5rws7tnsb0mrsppy</sha1>
    </revision>
  </page>
  <page>
    <title>Radiation Oncology/Prostate/Utilization</title>
    <ns>0</ns>
    <id>194566</id>
    <revision>
      <id>4675800</id>
      <parentid>1499275</parentid>
      <timestamp>2026-10-13T07:57:42Z</timestamp>
      <contributor>
        <username>Jcb</username>
        <id>90773</id>
      </contributor>
      <origin>4675800</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2906" sha1="fndixin0rl0ahuwqmlss5llb006qr4s" xml:space="preserve">{{:Radiation Oncology/Prostate:TOC}}


&lt;big&gt;'''Prostate Therapy Utilization'''&lt;/big&gt;


==Utilization==
*'''Center for Disease Control (CDC), Atlanta; 2007''' {{PMID|17469027}} -- &quot;Use of additional treatment for prostate cancer after radical prostatectomy, radiation therapy, androgen deprivation, or watchful waiting.&quot; (Berge V, Scand J Urol Nephrol. 2007;41(3):198-203.)
**SEER + Medicare claims data. 12,711 patients. Initial RP 31%, initial RT 31%, initial ADT 9%, initial WW 28%
**Outcome: Initial RP: 8% additional RT, 12% additional ADT. Initial RT: 23% additional ADT. Initial WW: 22% additional ADT
**Conclusion: If initially treated with RT or observation, more likely to receive ADT as follow-up treatment than if initially treated with RP


==Costs==
*'''American College of Radiology; 2002''' (1992-1993) {{PMID|12065564}} -- &quot;Comparing the costs of radiation therapy and radical prostatectomy for the initial treatment of early-stage prostate cancer.&quot; (Burkhardt JH, J Clin Oncol. 2002 Jun 15;20(12):2869-75.)
**Linked SEER-Medicare analysis. 
**Outcome: Costs RT $14,048 vs. RP $17,226 (SS)
**Conclusion: For early-stage PCA, average costs were at least 23% greater for RP

*'''UCLA; 2000''' (1993-1996) {{PMID|11042575}} -- &quot;A nationwide charge comparison of the principal treatments for early stage prostate carcinoma.&quot; (Brandeis J, Cancer. 2000 Oct 15;89(8):1792-9.)
**HCFA claims data for inpatient, outpatient and Part B claims. 10,107 men with initial diagnosis of prostate cancer, treatment, +6 months of follow-up. RT 58%, brachy 7%, RP 35%. During the 4 years, RT decreased by 20%, brachy increased by 21%
**Cost: RP + adjuvant RT $31,329 vs. RT + brachy boost $24,407 vs. RP $19,019 vs RT $15,937 vs brachy $15,301 (SS). Utilization varied with age, race, and geographic region
**Outcome: Without clear survival advantage, costs, QoL and patient preference take on paramount importance


==Proton Therapy==
*'''Fox Chase; 2007''' {{PMID|17704408}} -- &quot;Is proton beam therapy cost effective in the treatment of adenocarcinoma of the prostate?&quot; (Konski A, J Clin Oncol. 2007 Aug 20;25(24):3603-8.)
**Markov model. Cost-effectiveness evaluation of 91.8 CGE proton beam vs. 81 CGE photon IMRT, using cost, bNED, utility data
**15 year model: 70 year old: cost of protons $63,500 vs. IMRT $36,800; 60 year old: protons $65,000 vs. photons $39,400. Incremental cost/QALY 70-year old $63,6000 and 60-year old $55,700
**Conclusion: Assuming 10 Gy additional dose-escalation, proton beam not cost-effective for most patients
**Editorial {{PMID|17704400}}

*'''Oreboro; 2005''' (Sweden) {{PMID|16332598}} -- &quot;The potential of proton beam radiation therapy in prostate cancer, other urological cancers and gynaecological cancers.&quot; (Johansson B, Acta Oncol. 2005;44(8):890-5.)
**Estimate of the number of Swedish patients suitable for protons; annually ~300 prostate patients, ~50 GYN patients</text>
      <sha1>fndixin0rl0ahuwqmlss5llb006qr4s</sha1>
    </revision>
  </page>
  <page>
    <title>Radiation Oncology/Prostate/PSA</title>
    <ns>0</ns>
    <id>206861</id>
    <revision>
      <id>4675714</id>
      <parentid>3582961</parentid>
      <timestamp>2026-10-12T12:08:23Z</timestamp>
      <contributor>
        <username>Jcb</username>
        <id>90773</id>
      </contributor>
      <origin>4675714</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="21124" sha1="tdf2ukcdw1h66zdr0gwxg8anvc4cysi" xml:space="preserve">{{Radiation_Oncology:TOC}}


&lt;big&gt;'''Prostate Specific Antigen (PSA)'''&lt;/big&gt;
:''For PSA screening, see [[Radiation Oncology/Prostate/Screening and Prevention|Screening and Prevention]].''

==History of PSA==
'''''Defining &quot;PSA era&quot;:'''''
*The beginning of the PSA era is the late 1980s.&lt;ref name=&quot;Klein-2004&quot;&gt;Klein, Eric (ed.)(2004). ''Management of Prostate Cancer.'' [http://books.google.com/books?id=7WGIz-gT8MMC&amp;printsec=frontcover#v=onepage&amp;q&amp;f=false Google books link]&lt;/ref&gt;
*In the early PSA era (beginning approx. 1987), there was an abrupt rise in the incidence of prostate cancer, with a peak in 1992, then a decrease through 1995. The incidence remained stable between 1995 and 1999, but at a higher rate than in the pre-PSA era.&lt;ref name=&quot;Klein-2004&quot;/&gt;
*Approved by FDA in 1986 for disease monitoring.  Approved in 1992 for diagnosis. &lt;ref&gt;{{PMID|17372918}} &lt;/ref&gt;


'''''PSA use in early clinical trials:'''''
*EORTC 22863 (trial began 1987) - PSA in all pts at baseline
*RTOG 85-31 and 86-10 (trials began 1987) - PSA was not widely available at the beginning of the study. Made mandatory in 1990.


==PSA Measurement==
PSA level may be affected by a number of processes:
* Minimal impact - DRE, TRUS, cystoscopy
* Impact unclear - ejaculation (some studies show no impact, others show elevation at 24 or even 48 hours)
* Significant impact - prostatic massage, needle biopsy, TURP, prostatitis


===Impact of Ejaculation===
*'''1998''' {{PMID|9569113}} -- &quot;The effects of ejaculation on serum prostate-specific antigen (PSA).&quot; (Yavascaoglu I, Int Urol Nephrol. 1998).
**Conclusion: No relation between seminal plasma levels or total amounts expelled and the difference in serum levels due to ejaculation
*'''1998''' {{PMID|9510352}} -- &quot;The effect of ejaculation on prostate-specific antigen in a prostate cancer-screening population.&quot; (Stenner J, Urology. 1998)
**Conclusion: For the total screened population, ejaculation has no clinically significant effect. Men should not be asked to abstain from sexual activities before a PSA-screening test
*'''1997''' {{PMID|9255295}} -- &quot;Effect of ejaculation on serum total and free prostate-specific antigen concentrations.&quot; (Herschman JD, Urology. 1997)
**Conclusion: Both total and free PSA increase immediately after ejaculation, with differing rates of return to baseline levels. PSA testing within 24 hours after ejaculation may lead to an erroneous interpretation of the results of both total and percent free PSA measurements in a small proportion of men.
*'''1997''' {{PMID|9126226}} -- The effects of prostatic manipulation on prostate-specific antigen levels. (Klein LT, Urol Clin North Am. 1997)
**Minimal effect on PSA level - DRE, TRUS, cystoscopy, and ejaculation
**Significant effect on PSA level - Prostatic massage, needle biopsy, TURP, and prostatitis
*'''1997''' {{PMID|9266232}} -- &quot;Postejaculation serum prostate-specific antigen level.&quot; (Zisman A,  Eur Urol. 1997)
**Conclusion: A significant postejaculation serum PSA elevation does occur, it is thus recommended that men abstain from ejaculation for 24 h prior to PSA sampling.
*'''1997''' {{PMID|8976253}} -- &quot;The influence of ejaculation on serum levels of prostate specific antigen.&quot; (Heidenreich A,  J Urol. 1997)
**Conclusion: Ejaculation does not affect serum PSA concentration in young men, and there seems to be no physiological relationship between ejaculation and PSA level.
*'''1996''' {{PMID|8638359}} -- &quot;Ejaculation increases the serum prostate-specific antigen concentration.&quot; (Tchetgen MB, Urology. 1996)
**Conclusion: Ejaculation causes a significant increase in the serum PSA concentration in men between 49 and 79 years of age that may persist for up to 48 hours. This change appears to correlate with age and baseline PSA. It is recommended that men abstain from ejaculation for 48 hours prior to having a serum PSA determination.
*'''1995''' {{PMID|7544734}} -- &quot;Effect of ejaculation on prostate-specific antigen levels in normal men.&quot; (Kirkali Z, Eur Urol. 1995)
**Conclusion: Ejaculation does not seem to affect the serum PSA concentration at 5 consecutive days after ejaculation.
*'''1993''' {{PMID|7684542}} -- &quot;Effect of digital rectal examination (and ejaculation) on serum prostate-specific antigen after twenty-four hours. A randomized, prospective study.&quot; (McAleer JK, Urology. 1993)
**Conclusion: DRE had no clinically important effect on PSA values twenty-four hours later. Ejaculation had no meaningful effect on the serum PSA values.
*'''1992''' {{PMID|1384015}} -- &quot;Prostate-specific antigen: establishment of the reference range for the clinically normal prostate gland and the effect of digital rectal examination, ejaculation, and time on serum concentrations.&quot; (Glenski WJ, Prostate. 1992)
**Conclusion: Digital rectal examination and ejaculation have no significant effect on the serum concentration.


==Percent-Free PSA==
*'''Multicenter, 1998''' - {{PMID|9605898}} &amp;mdash; &quot;Use of the percentage of free prostate-specific antigen to enhance differentiation of prostate cancer from benign prostatic disease: a prospective multicenter clinical trial.&quot; Catalona WJ et al. JAMA. 1998 May 20;279(19):1542-7.
**Prospective. 773 men with PSA 4-10, ages 50-75, no palpable disease, histologically proven prostate cancer or benign disease. 
**Lower free PSA associated with a higher risk of prostate cancer. Using 25% free PSA cutoff lead to 95% sensitivity and avoided 20% of unnecessary biopsies. 


==PSA Failure==
=== PSA Nadir (PSAn) Post Radiotherapy===
In postradiotherapy patients PSA may never reach completely undetectable levels and rather will reach a very low nadir, typically below 1.0 ng/mL within 2 years after therapy. (0.2 ng/mL within 5 years in patients treated with simultaneous irradiation with a transperineal prostate iodine implant, followed by external beam irradiation)
Of particular interest is the correlation of PSA nadir levels to outcomes among RT patients.

*{{PMID|12946753}} - '''DWitt KD et al'''. &quot;What does postradiotherapy PSA nadir tell us about freedom from PSA failure and progression-free survival in patients with low and intermediate-risk localized prostate cancer?&quot; Urology. 2003 Sep;62(3):492-6.
**Patients were categorized by nPSA quartile groups with cutpoints of less than 0.3, 0.3 to less than 0.6, 0.6 to less than 1.2, and 1.2 ng/mL or greater.Freedom from PSA failure was strongly associated with nadir quartile groups (P &lt;0.0001). PFS was also significantly different statistically among nadir quartile groups (P = 0.02). No statistically significant difference was found in overall survival associated with nPSA at this point. CONCLUSIONS: nPSA is a strong independent predictor of freedom from PSA failure and PFS in patients with low and intermediate-risk localized prostate cancer treated with RT alone. Longer follow-up and larger patient numbers are required to confirm these observations.
*{{PMID|12441934}} - &quot;Time to achieve a prostate specific antigen nadir of 0.2 ng./ml. after simultaneous irradiation for prostate cancer.&quot; '''Critz FA ''' J Urol. 2002 Dec;168(6):2434-8.
**With rare exceptions to be potentially cured of prostate cancer by simultaneous irradiation men must achieve a PSA nadir of 0.2 ng./ml. within 5 years of implantation. Failure to reach this goal by 60 months of followup almost always indicates persistent disease.&quot;

Critz and colleagues found that a PSA nadir &lt; 0.2 ng/mL defines disease freedom following brachytherapy plus EBRT, and that a PSA nadir &gt; 1.0 ng/mL predicts for disease recurrence at a median of 5 years of follow-up. In addition, data from DeWitt and colleagues demonstrate that a PSA nadir &gt; 1.2 predicts worse outcomes in measures of freedom from PSA failure and progression-free survival in patients undergoing EBRT at the same time point.

===Definition of PSA Failure Post-Radiation therapy ===
*'''ASTRO Consensus Statement'''
**'''Phoenix Definition; 2006''' {{PMID|16798415}} &amp;mdash; &quot;Defining biochemical failure following radiotherapy with or without hormonal therapy in men with clinically localized prostate cancer: Recommendations of the RTOG-ASTRO Phoenix Consensus Conference.&quot; Roach M 3rd et al. Int J Radiat Oncol Biol Phys. 2006 Jul 15;65(4):965-74.
***1. Biochemical failure is defined as a rise of 2 ng/mL or more above the nadir after EBRT w/ or w/o hormonal therapy.
***2. The date of failure should be &quot;at call&quot; (not backdated).
**'''Original; 1997''' {{PMID|9169810}} (No abstract). &quot;Consensus statement: Guidelines for PSA following radiation therapy&quot; Int J Radiat Oncol Biol Phys. 1997 Mar 15;37(5):1035-41.
***1. Biochemical failure is not justification per se to initiate additional treatment. It is not equivalent to clinical failure.  It is, however, an appropriate early end point for clinical trials
***2. Three consecutive increases in PSA is a reasonable definition of biochemical failure after radiotherapy. For clinical trials, the date of failure should be the midpoint between the postirradiation nadir PSA and the first of the three consecutive rises
***3. No definition of PSA failure has, as yet, been shown to be a surrogate for clinical progression or survival
***4. Nadir PSA is a strong prognostic factor, but no absolute level is a valid cutpoint for separating successful and unsuccessful treatments. The nadir PSA is similar in prognostic value to pretreatment prognostic variables


*'''Vancouver rules (1999)''' - 1) True nadir is the lowest post-therapy PSA value. The reference nadir is the lowest reading which is not followed by a subsequent fall. 2) Must be 2 consecutive rises above the reference nadir, at least 1 month apart. 3) PSA &gt; 1.5 is required at any time after the reference nadir before PSA relapse can be scored. 4) Date of failure is midpoint between reference nadir and first post-true-nadir reading. 5) If true nadir is &gt;=4, relapse is scored at that time and no further rises are needed. 6) Salvage therapy is considered a relapse.
**(Letter) &quot;PSA relapse definitions--the Vancouver Rules show superior predictive power.&quot;  Pickles et al. Int J Radiat Oncol Biol Phys. 1999 Feb 1;43(3):699-700.

*'''Horwitz, William Beaumont (1996)''' - Determined difference in therapeutic outcome was observed if different definitions of PSA failure are used. 
**{{PMID|8948340}} &amp;mdash; &quot;Assessing the variability of outcome for patients treated with localized prostate irradiation using different definitions of biochemical control.&quot; Horwitz et al. Int J Radiat Oncol Biol Phys. 1996 Oct 1;36(3):565-71.

*'''Fox Chase (1995)''' - 2 consecutive rises to a level &gt; 1.5
**{{PMID|7531222}} (1995)
**{{PMID|10701734}} &amp;mdash; &quot;Scrutiny of the ASTRO consensus definition of biochemical failure in irradiated prostate cancer patients demonstrates its usefulness and robustness. American Society for Therapeutic Radiology and Oncology.&quot; Hanlon et al. Int J Radiat Oncol Biol Phys. 2000 Feb 1;46(3):559-66.

*'''Mass General''' - &quot;Strict definition&quot;: after a nadir of &lt;1 which occurs in 1 year, failure occurs if there are 2 consecutive rises. Failure is scored at the first increase. &quot;Liberal definition&quot;: same as strict, but nadir only needs to be &lt;4. 
**{{PMID|7751173}}

*'''Memorial''' - After a nadir of &lt;4, failure occurs if PSA rises above 4.
**{{PMID|7933238}}

*'''Stanford''' - Def#1:  Def#2: 2 consecutive increases where 2nd was higher than normal and at least 20% above the nadir. 
**{{PMID|7679756}}

*'''MDACC''' - 2 consecutive rises above nadir. Failure if increase by &gt;1 or by a factor of 1.5.
**{{PMID|7533459}}
**{{PMID|7686443}}

*'''Houston criteria''' - absolute increase of 2 above the nadir
**ASTRO 2002 - criteria proposed
**{{PMID|12909209}} &amp;mdash; &quot;Evaluation of the Houston biochemical relapse definition in men treated with prolonged neoadjuvant and adjuvant androgen ablation and assessment of follow-up lead-time bias.&quot; Pickles. Int J Radiat Oncol Biol Phys. 2003 Sep 1;57(1):11-8.
**Houston definition has improved predictive ability compared to ASTRO and Vancouver defs. Moreover, it does not violate the Cox propoprtional hazards test for patients treated both with and without androgen suppression.

====Comparison of PSA failure definitions====
*{{PMID|15711272}} -- '''Definitions of biochemical failure that best predict clinical failure in patients with prostate cancer treated with external beam radiation alone: a multi-institutional pooled analysis.''' (Horwitz EM,  J Urol. 2005)
**Pooled data on 4,839 patients with T1-2 prostate cancer treated with EBRT alone at 9 institutions
**&lt;u&gt;Conclusion&lt;/u&gt;: &quot;Defining BF as PSA greater than absolute nadir plus 2 ng/ml, dated at the call, PSA greater than current nadir plus 3 ng/ml, dated at the call, or 2 consecutive increases of at least 0.5 ng/ml, back dated, had higher sensitivity and specificity for DF alone or CF compared with the ASTRO definition.&quot;

*'''Taylor (Michigan)''' - [http://www.ncbi.nlm.nih.gov/entrez/query.fcgi?cmd=Retrieve&amp;db=pubmed&amp;dopt=Abstract&amp;list_uids=11483331 Abstract] &amp;mdash; &quot;Definitions of biochemical failure in prostate cancer following radiation therapy.&quot; Taylor JMG et al. Int J Radiat Oncol Biol Phys. 2001 Aug 1;50(5):1212-9.
**Single institution, 688 pts, 1987-96, all T stages, N0.  Evaluated 10 definitions of biochemical failure.  
**Favor Fox Chase Cancer Center method over ASTRO definition.

*'''Thames et al''' - [http://www.ncbi.nlm.nih.gov/entrez/query.fcgi?cmd=Retrieve&amp;db=pubmed&amp;dopt=Abstract&amp;list_uids=14575823 Abstract] &amp;mdash; &quot;Comparison of alternative biochemical failure definitions based on clinical outcome in 4839 prostate cancer patients treated by external beam radiotherapy between 1986 and 1995.&quot; Thames H et al. Int J Radiat Oncol Biol Phys. 2003 Nov 15;57(4):929-43.
**Used same pooled data set as [http://www.ncbi.nlm.nih.gov/entrez/query.fcgi?cmd=Retrieve&amp;db=pubmed&amp;dopt=Abstract&amp;list_uids=14575822  Kuban et al, 2003] with 4839 pts and median f/u 6 years. Assessed 102 definitions of biochemical failure.
**Favors ASTRO definition but recognizes its bias from the backdating of PSA failures.

==== PSA failure after RT + hormonal therapy ====
These methods account for the expected rise in PSA after coming off hormonal therapy.

*'''Fox Chase modification of ASTRO definition (2005)''' - Uses the original ASTRO definition, with the following modifications: 1) If after an initial rise there is a decline in PSA, 2 further consecutive rises in PSA &gt;0.1 are required for a failure. 2) If the PSA after 3 consecutive rises was unchanged but then declined, 2 further consecutive rises were also required. 
**{{PMID|15817330}} - &quot;Biochemical failure and the temporal kinetics of prostate-specific antigen after radiation therapy with androgen deprivation.&quot; Buyyounouski MK et al.  Int J Radiat Oncol Biol Phys. 2005 Apr 1;61(5):1291-8.

*'''EORTC (Bolla)''' - used PSA &gt; 1.5 and 2 consecutive rises separated by &gt;= 3 months (from {{PMID|12126818}}, 2002)

Comparisons:
*'''Fox Chase''', 2005 (1991-98) - {{PMID|16169682}} - &quot;Defining biochemical failure after radiotherapy with and without androgen deprivation for prostate cancer.&quot; Buyyounouski MK et al. Int J Radiat Oncol Biol Phys. 2005 Dec 1;63(5):1455-62.
**Purpose: Compare 3 definitions of biochemical failure in pts treated with or without AD: ASTRO, modified ASTRO, and nadir plus 2 (Houston definition). 
**Used same patient set as the other 2005 Fox Chase paper (see below). 
**Conclusion: Nadir + 2 (Houston definition) is superior to the ASTRO and modified ASTRO definitions in predicting true failures.

===Definition of PSA Failure Post-Radical Prostatectomy ===

Therapeutic goal of Radical prostatectomy is removal of prostatic and neoplastic tissue, so post-RP PSA level is undetectable, that is under 0.2 ng/ml (evaluated 30-45 days after surgery). Standard practice is to '''define post-RP biochemical failure as a PSA level exceeding 0.2 ng/mL on at least two successive evaluations''' ''or'' exceeding '''0.4 ng/mL on a single evaluation.''' By contrast, patients who never achieve undetectable levels '''and/or''' whose PSA rises very rapidly following surgery likely have metastatic disease.
* {{PMID|10799151}} - &quot;Prostate specific antigen only progression of prostate cancer.&quot; J Urol 2000 Jun;163(6):1632-42 Moul JW

The use of very low PSA thresholds risks overtreating patients whose PSA level is detectable due to residual benign prostatic tissue. For example, one recent report demonstrated that a single PSA elevation of less
than 0.4 ng/mL after radical prostatectomy is associated with subsequent stable, nonprogressing disease in up to 50% of patients.
* {{PMID|11257657}} - &quot;Defining prostate specific antigen progression after radical prostatectomy: what is the most appropriate cut point?&quot; Amling et  al. J Urol. 2001 Apr;165(4):1146-51.

*'''2006; Johns Hopkins''' (1985-2004) {{PMID|16921049}} -- &quot;Defining biochemical recurrence of prostate cancer after radical prostatectomy: a proposal for a standardized definition.&quot; (Stephenson AJ, J Clin Oncol. 2006 Aug 20;24(24):3973-8.)
**Conclusion: &quot;BCR defined as a PSA value of at least 0.4 ng/mL followed by another increase best explains the development of distant metastasis among 10 candidate definitions, after controlling for clinical variables and the use of secondary therapy. On the basis of this evidence, we propose that this definition be adopted as the standard for reporting the outcome of RP.&quot;

==PSA kinetics==
===Post-treatment PSA Bounce===
*{{PMID|15936550}} -- '''PSA bounces after neoadjuvant androgen deprivation and external beam radiation: Impact on definitions of failure.''' (Zietman AL, Int J Radiat Oncol Biol Phys. 2005)
**&lt;u&gt;Conclusion&lt;/u&gt;: &quot;A substantial proportion of patients treated by EBRT with neoadjuvant deprivation experienced a PSA bounce. A large percentage of these bounces scored as biochemical failure according to the ASTRO definition. The Nadir-plus-three definition is less vulnerable to this bias.&quot;
*{{PMID|12377320}} -- '''Using the magnitude of PSA bounce after MRI-guided prostate brachytherapy to distinguish recurrence, benign precipitating factors, and idiopathic bounce.''' (Das P, Int J Radiat Oncol Biol Phys. 2002)
**Results: +0.6ng/ml idiopathic bounce vs. +1.2ng/ml for ejaculation (p=0.003), instrumentation (p=0.007), proctitis (p&lt;0.0001) and biopsy-proven local recurrence (p=0.006)
**&lt;u&gt;Conclusion&lt;/u&gt;:&quot;In patients treated with MRI-guided prostate brachytherapy, recent ejaculation, instrumentation, or ongoing radiation proctitis can cause a transient increase in PSA, the magnitude of which is significantly higher than that for idiopathic PSA bounce, but is similar to that in patients with recurrent disease.&quot;

===After hormonal therapy + RT===
*'''Fox Chase''', 2005 (1991-98) - {{PMID|15817330}} - &quot;Biochemical failure and the temporal kinetics of prostate-specific antigen after radiation therapy with androgen deprivation.&quot; Buyyounouski MK et al. Int J Radiat Oncol Biol Phys. 2005 Apr 1;61(5):1291-8.
**Purpose: 1) describe the PSA kinetics after RT alone, RT + short term androgen deprivation (STAD, 3-12 months), and RT + long-term AD (LTAD, 1-3 yrs). 2) show the potential rise of PSA after withdrawal of AD. 3) Test the ASTRO definition in this setting. This paper provides a graphic representation of PSA kinetics.
**Retrospecitive. 688 men with localized prostate cancer treated with 3D-CRT, without AD or with STAD (82) or LTAD (20).  Minimum of 4 yrs f/u. Mean dose 74 Gy (ICRU dose). Biochemical failure used ASTRO definion as well as modified ASTRO definition (see section above). PSA obtained q6months.
**Median f/u 5-6 years. For those without biochemical failure, the PSA after STAD remains relatively constant, and after LTAD, PSA rises steadily towards 1. Between 22% and 29% of pts who had a failure by the ASTRO criteria subsequently had a fall in the PSA and were not classified as BF by the revised definition.

==Surrogate Endpoints==
*'''Post-treatment PSA-DT'''
**[http://www.asco.org/ac/1,1003,_12-002643-00_18-0034-00_19-0032291,00.asp ASCO Abstract]. Surrogate Endpoint for Prostate Cancer-specific Survival: Validation from an Analysis of Radiation Therapy Oncology Group Protocol 92-02. Valicenti et al.
***&lt;u&gt;Conclusion:&lt;/u&gt;Post-treatment PSA-DT &lt;12 months met all of Prentice’s criteria for surrogacy. For the first time, this was accomplished for a prospectively studied patient population, and justifies strong consideration for PSA-DT&lt; 12 months as a surrogate endpoint for prostate cancer mortality.

*{{PMID|13130113}} [http://jncicancerspectrum.oxfordjournals.org/cgi/reprint/jnci;95/18/1376.pdf Full text] - &quot;Surrogate End Point for Prostate Cancer–Specific Mortality After Radical Prostatectomy or Radiation Therapy.&quot; D'Amico et al Journal of the National Cancer Institute, Vol. 95, No. 18, 1376-1383, September 17, 2003
** A post-treatment PSA-DT of less than 3 months and the specific value of the post-treatment PSA-DT when it is 3 months or more appear to be surrogate end points for prostate cancer-specific mortality after surgery or radiation therapy.

==References==
&lt;references/&gt;</text>
      <sha1>tdf2ukcdw1h66zdr0gwxg8anvc4cysi</sha1>
    </revision>
  </page>
  <page>
    <title>OpenSCAD User Manual/Using OpenSCAD in a command line environment</title>
    <ns>0</ns>
    <id>227473</id>
    <revision>
      <id>4675812</id>
      <parentid>4675547</parentid>
      <timestamp>2026-10-13T10:02:17Z</timestamp>
      <contributor>
        <username>~2026-54954-64</username>
        <id>3628319</id>
      </contributor>
      <comment>/* BOM or datasheet exportation */ Add image exportation</comment>
      <origin>4675812</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="29515" sha1="r0a4ired1eui5l57fam43j6suyvv2bk" xml:space="preserve">__TOC__

=== Command line usage ===
OpenSCAD can not only be used as a GUI, but also handles command line arguments.

OpenSCAD (DEV/nightly) 2025.08.17 has these options

&lt;pre&gt;
Usage: openscad.exe [options] file.scad
Allowed options:
  --export-format arg               overrides format of exported scad file when
                                    using option '-o', arg can be any of its
                                    supported file extensions.  For ascii stl
                                    export, specify 'asciistl', and for binary
                                    stl export, specify 'binstl'.  Ascii export
                                    is the current stl default, but binary stl
                                    is planned as the future default so
                                    asciistl should be explicitly specified in
                                    scripts when needed.

  -o [ --o ] arg                    output specified file instead of running
                                    the GUI. The file extension specifies the
                                    type: stl, off, wrl, amf, 3mf, csg, dxf,
                                    svg, pdf, png, echo, ast, term, nef3,
                                    nefdbg, param, pov. May be used multiple
                                    times for different exports. Use '-' for
                                    stdout.

  -O [ --O ] arg                    pass settings value to the file export
                                    using the format section/key=value, e.g
                                    export-pdf/paper-size=a3. Use --help-export
                                    to list all available settings.
  -D [ --D ] arg                    var=val -pre-define variables
  -p [ --p ] arg                    customizer parameter file
  -P [ --P ] arg                    customizer parameter set
  --enable arg                      enable experimental features (specify 'all'
                                    for enabling all available features): roof
                                    | input-driver-dbus | lazy-union |
                                    vertex-object-renderers-indexing |
                                    textmetrics | import-function |
                                    predictible-output

  -h [ --help ]                     print this help message and exit
  --help-export                     print list of export parameters and values
                                    that can be set via -O
  -v [ --version ]                  print the version
  --info                            print information about the build process

  --camera arg                      camera parameters when exporting png:
                                    =translate_x,y,z,rot_x,y,z,dist or
                                    =eye_x,y,z,center_x,y,z
  --autocenter                      adjust camera to look at object's center
  --viewall                         adjust camera to fit object
  --backend arg                     3D rendering backend to use: 'CGAL'
                                    (old/slow) [default] or 'Manifold'
                                    (new/fast)
  --imgsize arg                     =width,height of exported png
  --render arg                      for full geometry evaluation when exporting
                                    png
  --preview arg                     [=throwntogether] -for ThrownTogether
                                    preview png
  --animate arg                     export N animated frames
  --animate_sharding arg            Parameter &lt;shard&gt;/&lt;num_shards&gt; - Divide
                                    work into &lt;num_shards&gt; and only output
                                    frames for &lt;shard&gt;. E.g. 2/5 only outputs
                                    the second 1/5 of frames. Use to
                                    parallelize work on multiple cores or
                                    machines.
  --view arg                        =view options: axes | crosshairs | edges |
                                    scales
  --projection arg                  =(o)rtho or (p)erspective when exporting
                                    png
  --csglimit arg                    =n -stop rendering at n CSG elements when
                                    exporting png
  --summary arg                     enable additional render summary and
                                    statistics: all | cache | time | camera |
                                    geometry | bounding-box | area
  --summary-file arg                output summary information in JSON format
                                    to the given file, using '-' outputs to
                                    stdout
  --colorscheme arg                 =colorscheme: *Cornfield | Metallic |
                                    Sunset | Starnight | BeforeDawn | Nature |
                                    Daylight Gem | Nocturnal Gem | DeepOcean |
                                    Solarized | Tomorrow | Tomorrow Night |
                                    ClearSky | Monotone

  -d [ --d ] arg                    deps_file -generate a dependency file for
                                    make
  -m [ --m ] arg                    make_cmd -runs make_cmd file if file is
                                    missing
  -q [ --quiet ]                    quiet mode (don't print anything *except*
                                    errors)
  --hardwarnings                    Stop on the first warning
  --trace-depth arg                 =n, maximum number of trace messages
  --trace-usermodule-parameters arg =true/false, configure the output of user
                                    module parameters in a trace
  --check-parameters arg            =true/false, configure the parameter check
                                    for user modules and functions
  --check-parameter-ranges arg      =true/false, configure the parameter range
                                    check for builtin modules
  --debug arg                       special debug info - specify 'all' or a set
                                    of source file names
  -s [ --s ] arg                    stl_file deprecated, use -o
  -x [ --x ] arg                    dxf_file deprecated, use -o
&lt;/pre&gt;

Export help
&lt;pre&gt;
OpenSCAD version 2025.08.17

List of settings that can be given using the -O option using the
format '&lt;section&gt;/&lt;key&gt;=value', e.g.:
openscad -O export-pdf/paper-size=a6 -O export-pdf/show-grid=false

Section 'export-pdf':
  - paper-size (enum): [a6,a5,&lt;a4&gt;,a3,letter,legal,tabloid]
  - orientation (enum): [&lt;portrait&gt;,landscape,auto]
  - show-filename (bool): &lt;true&gt;/false
  - show-scale (bool): &lt;true&gt;/false
  - show-scale-message (bool): &lt;true&gt;/false
  - show-grid (bool): &lt;true&gt;/false
  - grid-size (double): 1.000000 : &lt;10.000000&gt; : 100.000000
  - add-meta-data (bool): &lt;true&gt;/false
  - meta-data-title (string): &quot;&quot;
  - meta-data-author (string): &quot;&quot;
  - meta-data-subject (string): &quot;&quot;
  - meta-data-keywords (string): &quot;&quot;
Section 'export-3mf':
  - color-mode (enum): [&lt;model&gt;,none,selected-only]
  - unit (enum): [micron,&lt;millimeter&gt;,centimeter,meter,inch,foot]
  - color (string): &quot;#f9d72c&quot;
  - material-type (enum): [color,&lt;basematerial&gt;]
  - decimal-precision (int): 1 : &lt;6&gt; : 16
  - add-meta-data (bool): &lt;true&gt;/false
  - meta-data-title (string): &quot;&quot;
  - meta-data-designer (string): &quot;&quot;
  - meta-data-description (string): &quot;&quot;
  - meta-data-copyright (string): &quot;&quot;
  - meta-data-license-terms (string): &quot;&quot;
  - meta-data-rating (string): &quot;&quot;
&lt;/pre&gt;


OpenSCAD 2021.01 has these options:
 Usage: openscad [options] file.scad
 Allowed options:
  --export-format arg          overrides format of exported scad file when
                               using option '-o', arg can be any of its
                               supported file extensions.  For ascii stl
                               export, specify 'asciistl', and for binary stl
                               export, specify 'binstl'.  Ascii export is the
                               current stl default, but binary stl is planned
                               as the future default so asciistl should be
                               explicitly specified in scripts when needed.
  
  -o [ --o ] arg               output specified file instead of running the
                               GUI, the file extension specifies the type: stl,
                               off, wrl, amf, 3mf, csg, dxf, svg, pdf, png,
                               echo, ast, term, nef3, nefdbg (May be used
                               multiple time for different exports). Use '-'
                               for stdout
  
  -D [ --D ] arg               var=val -pre-define variables
  -p [ --p ] arg               customizer parameter file
  -P [ --P ] arg               customizer parameter set
  --enable arg                 enable experimental features (specify 'all' for
                               enabling all available features): roof |
                               input-driver-dbus | lazy-union |
                               vertex-object-renderers |
                               vertex-object-renderers-indexing |
                               vertex-object-renderers-direct |
                               vertex-object-renderers-prealloc | textmetrics
  
  -h [ --help ]                print this help message and exit
  -v [ --version ]             print the version
  --info                       print information about the build process
  
  --camera arg                 camera parameters when exporting png:
                               =translate_x,y,z,rot_x,y,z,dist or
                               =eye_x,y,z,center_x,y,z
  --autocenter                 adjust camera to look at object's center
  --viewall                    adjust camera to fit object
  --imgsize arg                =width,height of exported png
  --render                     for full geometry evaluation when exporting png
  --preview arg                [=throwntogether] -for ThrownTogether preview
                               png
  --animate arg                export N animated frames
  --view arg                   =view options: axes | crosshairs | edges |
                               scales | wireframe
  --projection arg             =(o)rtho or (p)erspective when exporting png
  --csglimit arg               =n -stop rendering at n CSG elements when
                               exporting png
  --summary arg                enable additional render summary and statistics:
                               all | cache | time | camera | geometry |
                               bounding-box | area
  --summary-file arg           output summary information in JSON format to the
                               given file, using '-' outputs to stdout
  --colorscheme arg            =colorscheme: *Cornfield | Metallic | Sunset |
                               Starnight | BeforeDawn | Nature | DeepOcean |
                               Solarized | Tomorrow | Tomorrow Night | Monotone
  
  -d [ --d ] arg               deps_file -generate a dependency file for make
  -m [ --m ] arg               make_cmd -runs make_cmd file if file is missing
  -q [ --quiet ]               quiet mode (don't print anything *except*
                               errors)
  --hardwarnings               Stop on the first warning
  --check-parameters arg       =true/false, configure the parameter check for
                               user modules and functions
  --check-parameter-ranges arg =true/false, configure the parameter range check
                               for builtin modules
  --debug arg                  special debug info - specify 'all' or a set of
                               source file names

=== Export options ===

When called with the &lt;code&gt;-o&lt;/code&gt; option, OpenSCAD does not start the GUI, but executes the given file and exports to the &lt;i&gt;output_file&lt;/i&gt; in a format depending on the extension (&lt;code&gt;.stl&lt;/code&gt; / &lt;code&gt;.off&lt;/code&gt; / &lt;code&gt;.dxf&lt;/code&gt;, &lt;code&gt;.csg&lt;/code&gt;).  

Some versions use -s/-d/-o to determine the output file format instead; check with &quot;openscad --help&quot;.

If the option &lt;code&gt;-d&lt;/code&gt; is given in addition to an export command, all files accessed while building the mesh are written in the argument of &lt;code&gt;-d&lt;/code&gt; in the syntax of a Makefile.

For at least 2015.03-2+, specifying the extension &lt;code&gt;.echo&lt;/code&gt; causes openscad to produce a text file containing error messages and the output of all &lt;code&gt;echo()&lt;/code&gt; calls in &lt;code&gt;filename&lt;/code&gt; as they would appear in the console window visible in the GUI. Multiple output files are not supported, so using this option you cannot also obtain the model that would have normally been generated.

Note:  When exporting to STL, the GUI defaults to binary STL (smaller, faster) and the CLI defaults to ASCII STL (larger, slower).  Post-processing pipelines may prefer ASCII STL; they should explicitly say `--export-format asciistl` in preparation for the default eventually changing to binary STL.

==== Camera and image output ====

For 2013.05+, the option to output a &lt;code&gt;.png&lt;/code&gt; image was added. There are two types of cameras available for the generation of images.  

The first camera type is a 'gimbal' camera that uses Euler angles, translation, and a camera distance, like OpenSCAD's GUI viewport display at the bottom of the OpenSCAD window.

The second camera type is a 'vector' camera, with an 'eye' camera location vector and a 'lookat' center vector. 

--imgsize x,y chooses the .png dimensions and --projection chooses orthogonal or perspective, as in the GUI. 

By default, cmdline .png output uses Preview mode (f5) with OpenCSG. For some situations it may be desirable to output the full render, with CGAL. This is done by adding '--render' as an option.

=== Constants ===

In order to pre-define variables, use the &lt;code&gt;-D&lt;/code&gt; option. It can be given repeatedly. Each occurrence of &lt;code&gt;-D&lt;/code&gt; must be followed by an assignment. Unlike normal OpenSCAD assignments, these assignments don't define variables, but constants, which cannot be changed inside the program, and can thus be used to overwrite values defined in the program at export time.

If you want to assign the -D variable to another variable, the -D variable MUST be initialized in the main .scad program

 param1=17;       // must be initialized
 val=param1;      // param1 passed via -D on cmd-line
 echo(val,param1); // outputs 17,17

without the first line, val would be undefined.

The right hand sides can be arbitrary OpenSCAD expressions, including mathematical operations and strings.

Be aware that your shell (bash, cmd, etc.) parses the arguments before passing them to &lt;code&gt;openscad&lt;/code&gt;, therefore you need to properly quote or escape arguments with special characters like spaces or quotation marks. For example to assign a string &lt;code&gt;production&lt;/code&gt; to a &lt;code&gt;quality&lt;/code&gt; parameter one has to ensure the &lt;code&gt;&quot;&lt;/code&gt; characters OpenSCAD expects aren't stripped by the shell. In bash one could write:

 openscad -o my_model_production.stl -D 'quality=&quot;production&quot;' my_model.scad

or from the Windows prompt:

 openscad.com -o my_model_production.stl -D &quot;quality=&quot;&quot;production&quot;&quot;&quot; my_model.scad

or you may need to escape the inner quotes instead:

 openscad -o my_model_production.stl -D &quot;quality=\&quot;production\&quot;&quot; my_model.scad

Note that this sort of double-escaping isn't necessary when executing OpenSCAD from another process that isn't using a shell, because each argument is passed separately. For example a Java application might start a process like so:

    pb = new ProcessBuilder(&quot;/usr/bin/openscad&quot;,
      &quot;-o&quot;, &quot;my_model_production.stl&quot;,
      &quot;-D&quot;, &quot;quality=\&quot;production\&quot;&quot;,
      &quot;my_model.scad&quot;);

// 12-Pole Fuse Box with Cover (EV Application)

// ================= PARAMETERS =================
length = 100;
width = 40;
height = 35;
wall = 2.5;

fuse_w = 4.2;
fuse_l = 12;
fuse_h = 12;

x_pitch = 8.5;
y_pitch = 14;

cover_height = 5;

// ================= MAIN HOUSING =================
difference() {
    cube([length, width, height]);

    // Hollow inside
    translate([wall, wall, wall])
        cube([length-2*wall, width-2*wall, height]);

    // Fuse slots (2 rows x 6 columns)
    for (row = [0:1]) {
        for (col = [0:5]) {
            x = 10 + col * x_pitch;
            y = 10 + row * y_pitch;

            translate([x, y, 5])
                cube([fuse_w, fuse_l, fuse_h]);
        }
    }
}

// ================= COVER =================
translate([0, 0, height])
    cube([length, width, cover_height]);

// ================= MOUNTING HOLES =================
for (x = [10, length-10]) {
    translate([x, width/2, 0])
        cylinder(h=height, d=5, center=false);
}

=== Processing all .scad files in a folder ===

Example to convert all the .scad in a folder into .stl:

In a folder with .scad files, make a .bat file with text:
    FOR %%f in (*.scad)  DO openscad -o &quot;%%~nf.stl&quot; &quot;%%f&quot; 

If it closes without processing, check to set the PATH by adding openscad directory to:

      Start - Settings - Control Panel - System - Advanced tab - Environment Variables - System Variables, select Path, then click Edit.
Add the openscad directory to the list


=== Makefile example ===

The &lt;code&gt;-d&lt;/code&gt; and &lt;code&gt;-m&lt;/code&gt; options only make sense together. (&lt;code&gt;-m&lt;/code&gt; without &lt;code&gt;-d&lt;/code&gt; would not consider modified dependencies when building exports, &lt;code&gt;-d&lt;/code&gt; without &lt;code&gt;-m&lt;/code&gt; would require the files to be already built for the first run that generates the dependencies.)

Here is an example of a basic Makefile that creates an .stl file from an .scad file of the same name:

 # explicit wildcard expansion suppresses errors when no files are found
 include $(wildcard *.deps)
 
 %.stl: %.scad
 	openscad -m make -o $@ -d $@.deps $&lt;

When &lt;code&gt;make my_example.stl&lt;/code&gt; is run for the first time, it finds no .deps files, and must depend on &lt;code&gt;my_example.scad&lt;/code&gt;. Because &lt;code&gt;my_example.stl&lt;/code&gt; is not yet present, it gets created unconditionally. If OpenSCAD finds missing files, it calls &lt;code&gt;make&lt;/code&gt; to build them, and it lists all used files in &lt;code&gt;my_example.stl.deps&lt;/code&gt;.

When &lt;code&gt;make my_example.stl&lt;/code&gt; is called subsequently, it finds and includes &lt;code&gt;my_example.stl.deps&lt;/code&gt; and check if any of the files listed there, including &lt;code&gt;my_example.scad&lt;/code&gt;, changed since &lt;code&gt;my_example.stl&lt;/code&gt; was built, based on their time stamps. Only if that is the case, it builds &lt;code&gt;my_example.stl&lt;/code&gt; again.

==== Automatic targets ====

When building similar .stl files from a single .scad file, there is a way to automate that too:

 # match &quot;module foobar() { // `make` me&quot;
 TARGETS=$(shell sed '/^module [a-z0-9_-]*().*make..\?me.*$$/!d;s/module //;s/().*/.stl/' base.scad)
 
 all: ${TARGETS}
 
 # auto-generated .scad files with .deps make make re-build always. keeping the
 # scad files solves this problem. ([[Talk:OpenSCAD User Manual/Using OpenSCAD in a command line environment|explanations are welcome]].)
 .SECONDARY: $(shell echo &quot;${TARGETS}&quot; | sed 's/\.stl/.scad/g')
 
 # explicit wildcard expansion suppresses errors when no files are found
 include $(wildcard *.deps)
 
 %.scad:
 	echo -ne 'use &lt;base.scad&gt;\n$*();' &gt; $@
 
 %.stl: %.scad
 	openscad -m make -o $@ -d $@.deps $&lt;

All objects that are supposed to be exported automatically have to be defined in &lt;code&gt;base.scad&lt;/code&gt; in an own module with their future file name (without the &quot;.stl&quot;), and have a comment like &quot;&lt;code&gt;// make me&lt;/code&gt;&quot; in the line of the module definition. The &quot;&lt;code&gt;TARGETS=&lt;/code&gt;&quot; line picks these out of the base file and creates the file names. These are built when &lt;code&gt;make all&lt;/code&gt; (or &lt;code&gt;make&lt;/code&gt;, for short) is called.

As the convention from the last example is to create the .stl files from .scad files of the same base name, for each of these files, an .scad file must be generated. This is done in the &quot;&lt;code&gt;%.scad:&lt;/code&gt;&quot; paragraph; &lt;code&gt;my_example.scad&lt;/code&gt; is a simple OpenSCAD file:

 use &lt;base.scad&gt;
 my_example();

The &quot;&lt;code&gt;.SECONDARY&lt;/code&gt;&quot; line is there to keep &lt;code&gt;make&lt;/code&gt; from deleting the generated .scad files. Its presence helps determine which files no longer need to be rebuilt; please post ideas about what exactly goes wrong there (or how to fix it better) on the [[Talk:OpenSCAD User Manual/Using OpenSCAD in a command line environment|talk]] page!

=== Windows notes ===

On Windows, openscad.com should be called from the command line as a wrapper for openscad.exe. This is because Openscad uses the 'devenv' solution to the Command-Line/GUI output issue. Typing 'openscad' at the cmd.exe prompt calls the .com program wrapper by default.

=== MacOS notes ===

On MacOS the binary is normally hidden inside the App folder. If OpenSCAD is installed in the global Applications folder, it can be called from command line like in the following example that just shows the OpenSCAD version:

 macbook:/$ /Applications/OpenSCAD.app/Contents/MacOS/OpenSCAD -v
 OpenSCAD version 2013.06

Alternatively, you may create a symbolic link to the binary to make calls from the command line easier:

  macbook:/$ sudo ln -sf /Applications/OpenSCAD.app/Contents/MacOS/OpenSCAD /usr/local/bin/openscad

Now you can call &lt;code&gt;openscad&lt;/code&gt; directly without having to type in the full path.

  macbook:/$ openscad -v
  OpenSCAD version 2015.03-3

On some versions of MacOS, you might get the following error when attempting to run openscad via that link:

  This application failed to start because it could not find or load the Qt platform plugin &quot;cocoa&quot;.

  Reinstalling the application may fix this problem.
  Abort trap: 6

You can fix this by creating a wrapper script to invoke the executable directly:

  sudo rm -f /usr/local/bin/openscad
  echo '#!/bin/sh' &gt; test
  echo '/Applications/OpenSCAD.app/Contents/MacOS/OpenSCAD &quot;$@&quot;' &gt;&gt; test
  chmod +x test ; sudo mv test /usr/local/bin/openscad
 
=== Automation ===
There are many solutions to automate Openscad operation, the following examples use Microsoft Powershell which is available either on Windows, on Linux (in deb and snap packages) or on MacOS.

Such script file shall be written on a text editor, much preferably a code editor with syntax coloring for powershell (e.g. VS code, Sublime text).

Note that while powershell script may be started directly from file browser in Linux, for debugging you may want to start script from a terminal window in order to see messages from script or OpenScad.

First you shall define the program call for your system and set it in a variable, adjust according your system

On Windows this may depends from your system disk, could be simpler if your environment variable are well set:
&lt;pre&gt;$scad = &quot;c:`&quot;/Program Files/OpenSCAD/openscad.exe`&quot;&quot;&lt;/pre&gt;
On Linux simply:
&lt;pre&gt;$scad = &quot;openscad&quot; &lt;/pre&gt;
On MacOS this may be:
&lt;pre&gt;$scad = &quot;/Applications/OpenSCAD.app/Contents/MacOS/OpenSCAD&quot;&lt;/pre&gt;

If you want to be capable to use a variation of openscad, say the nightly version, set the openscad version you want.
&lt;pre&gt;$scad = &quot;openscad-nightly&quot;&lt;/pre&gt;

==== Outputting different parts of a model ====
The first automation that you may want is to output automatically many parts from the same scad file.

You can use a variable ‘part’ to select the part to output.

code of 'mymodel.scad' might be:
&lt;pre&gt;
part = 0;  // [0:Ensemble, 1:Part 1, 2:Part 2, 3:Part 3]
...
if (part==1) {
...
}
else if (part==2) {
...
}
else if (part==3) {
...
}
&lt;/pre&gt;
and the automation file ‘mybatch.ps1’ will be:
&lt;pre&gt;
#!/usr/bin/env pwsh
# Above 'shebang' line required on Linux for automatic execution of powershell from a direct launch on file browser. 'mybatch.ps1' file attributes shall be made executable first.
#Powershell part batch generator
$arglist = &quot;-o mymodelpart1.stl -D part=1 mymodel.scad&quot;
Start-Process $scad -ArgumentList $arglist -Wait -NoNewWindow
$arglist = &quot;-o mymodelpart2.stl -D part=2 mymodel.scad&quot;
Start-Process $scad -ArgumentList $arglist -Wait -NoNewWindow
$arglist = &quot;-o mymodelpart2.stl -D part=3 mymodel.scad&quot;
Start-Process $scad -ArgumentList $arglist -Wait -NoNewWindow
&lt;/pre&gt;
-Wait parameter impose the task to be finished before continuing the script

-NoNewWindow will execute the script in the existing window without starting a new one

Note there is no space around the '=' sign for parameters

You may want to change any other parameter than 'part' at will, including or not a part number, in this case the argument list might be:
&lt;pre&gt;
$arglist = &quot;-o somepart.stl -D myvar1=value1 -D myvar2=value2 mymodel.scad&quot;
&lt;/pre&gt;

Note that if the value is a string, double quotes shall be escaped by a bactick ` : -D myvals=`&quot;myparam`&quot; for them not to be interpreted as the $arglist string end or start.

You may also define a string by setting it between simple quotes but that prevent you to use variables which will be interpreted when running command.

So the execution line became:
&lt;pre&gt;
Start-Process $scad -ArgumentList $arglist -Wait -NoNewWindow
&lt;/pre&gt;

==== BOM or datasheet exportation ====
Another frequent request is to export a BOM or a specification

This could be done by adapting your program to echo the stuff you want, by example:
&lt;pre&gt;
echoout = 0;  //0 is normal screen echo, 1 will be BOM, 2 will be data Specification
if (echoout==0) {
  echo(&quot;Normal echo&quot;);
}
...
if (echoout==1) {
  echo(&quot;Part 1 : description1&quot;);
  echo(&quot;Part 2 : description2&quot;);
  echo(&quot;Part 3 : description3 dimensions:&quot;, part3dim1,&quot;x&quot;,part3dim2);
}
...
if (echoout==2) {
  echo(str(&quot;First parameter =&quot;, var1));
  echo(str(&quot;Second parameter =&quot;, var2));
  echo(str(&quot;Third parameter =&quot;, var3));
}
&lt;/pre&gt;
Writing your own echo module may help.

then to obtain an output, your argument list may became:
&lt;pre&gt;$arglist = &quot;-o mymodel_BOM.txt -D echoout=1 --export-format echo mymodel.scad&quot;&lt;/pre&gt;
and
&lt;pre&gt;$arglist = &quot;-o mymodel_data.txt -D echoout=2 --export-format echo mymodel.scad&quot;&lt;/pre&gt;

However, the outputted text will have 'ECHO:' written at the beginning of each line and text will be set between &quot;, that you want to remove with following commands:
&lt;pre&gt;
$fc = Get-Content .\mymodel_BOM.txt  #get whole file in $fc variable
if($fc) { #check if the file have any content
  $fc = $fc -replace 'ECHO: ', '' #remove 'ECHO: ' text
  $fc = $fc -replace '&quot;' , '' #remove '&quot;' char - this is optional
  $fc &gt; .\mymodel_BOM.txt   #send variable content to the file which will be overwritten
}
&lt;/pre&gt;

==== Image exportation ====
You can export an image simply by defining the png extension. By default the image is the preview adapted to object size and viewed in 3D. Your argument list then became:
&lt;pre&gt;$arglist = &quot;-o mymodel.png --imgsize 1024,1024 mymodel.scad&quot;&lt;/pre&gt;
If you want the viewed image as rendered add '--render' parameter before the size definition:
&lt;pre&gt;$arglist = &quot;-o mymodel.png --render --imgsize 1024,1024 mymodel.scad&quot;&lt;/pre&gt;

==== Using datasets ====
An interesting option is to use Customizer datasets, however Customizer datasets variable values supersedes any values than you try to define in the command line:

The solution is to rename the parameter you need to modify and copy it to a variable that the command line will then be capable to change.

In your scad you may find:
&lt;pre&gt;
cpart = 0;  // [0:ensemble, 1:Part 1, 2:Part 2, 3:Part 3] //This variable will be recorded in the dataset, so not modifiable
part=cpart; // 'part' variable can be manipulated by the command line
//Argument list for all your runs could then be:
$arglist = &quot;-o mymodeldataset1part1.stl -D part=1 -p mymodel.json -P dataset1 mymodel.scad&quot;
$arglist = &quot;-o mymodeldataset1part2.stl -D part=2 -p mymodel.json -P dataset1 mymodel.scad&quot;
$arglist = &quot;-o mymodeldataset2part1.stl -D part=1 -p mymodel.json -P dataset2 mymodel.scad&quot;
$arglist = &quot;-o mymodeldataset2part2.stl -D part=2 -p mymodel.json -P dataset2 mymodel.scad&quot;
&lt;/pre&gt;
Do the same for any parameter that you want to manipulate in the command Line when using datasets:
&lt;pre&gt;
//This is parameter1
cvar1 = value1;
var1 = cvar1;
//This is parameter 2
cvar2 = value2;
var2 = cvar2;
&lt;/pre&gt;

==== Browsing datasets ====
A step further might be to automate the dataset browsing. You shall read the json file which contains all datasets:

A regular expression can then filter dataset names:
&lt;pre&gt;
$regex='\&quot;(?!parameterSets)([^\&quot;]+)\&quot;\:\s\{' # This regex extract anything between &quot;&quot; followed by ': {' excluding 'parameterSets'
$jfile = &quot;./mymodel.json  #directory localisation required by powershell
foreach($line in Get-Content $jfile) { # read json file Line by Line
  if($line -match $regex) { # We found a dataset name
    $dataset = $Matches.1  # dataset is the part captured by the regex parenthesis, will also be used in the part name
    Write-Output &quot;Dataset: $dataset&quot; #Output to console debugging info
    $datasetname = $dataset -replace ' ' , '_' #replace space by underscore
    #Dataset name containing often space character shall be set between double quotes
    #We may use simple quotes to define strings containing double quotes around dataset name
    $arglist = &quot;-o + mymodel&quot; + $datasetname + '.stl -p mymodel.json -P &quot;' + $dataset + '&quot; mymodel.scad'
    Write-Output &quot;Argument list: $arglist&quot; #Output to console debugging info
    Start-Process $scad -ArgumentList $arglist -Wait -NoNewWindow
  }
}
&lt;/pre&gt;

 {{BookCat}}</text>
      <sha1>r0a4ired1eui5l57fam43j6suyvv2bk</sha1>
    </revision>
  </page>
  <page>
    <title>Accordion/Left hand/Lesson 2</title>
    <ns>0</ns>
    <id>246270</id>
    <revision>
      <id>4675762</id>
      <parentid>4675454</parentid>
      <timestamp>2026-10-12T19:41:00Z</timestamp>
      <contributor>
        <username>WereSpielChequers</username>
        <id>248949</id>
      </contributor>
      <comment>typo</comment>
      <origin>4675762</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="9674" sha1="5zlehbyrra6hau03dxwle2ovkr0c0h2" xml:space="preserve">Now that you know all the available &quot;C&quot; chords, now it's time to learn to play in other keys. The basses are arranged in a [[circle of fifths]]. From the pedal &quot;C&quot; button, move up one button. This one plays a &quot;G&quot;. If you try the corresponding chord buttons on this row, you'll notice they're the same, but play in the key of G, not C. Move up another row and the bass note is &quot;D&quot;, then &quot;A&quot;, etc. Going &quot;upwards&quot; from the C, the circle of fifths goes C, G, D, A, E, B, F#, C#/Db, Ab, Eb, Bb, F, and then back to C. Similarly, if you go downwards from middle &quot;C&quot;, you will play an &quot;F&quot;, then a &quot;B flat&quot;, etc. The circle of fifths downward (technically this is a circle of fourths, which is the inversion of a fifth) is C, F, Bb, Eb, Ab, Db, Gb, B, E, A, D, G, then back to C. You may recognize the pattern from folk songs which have chords in this order (e.g., E, A, D, G).

The key here is to remember where each button is and the distance between buttons. Because you can't see your left hand, it can be challenging to play smoothly. To help guide your left hand, most accordions have one or more buttons with depressions, raised jewels or other tactile markers. Typically, the C bass button, the E bass button above the C, and the Ab bass button below the C have some type of engraving or marking. 

You can study a diagram of the Stradella bass button system to see how the buttons' musical keys are laid out. When you are starting iut, you can also look at your left hand in a mirror. Just as important as learning about diagrams and layouts, though, is [[ear training]], which is learning to hear and identify common intervals and chords just by hearing them. While there are countless possible chord movements to eventually learn by ear, the most important ones are I (the tonic or &quot;home chord&quot;), IV (the sub-dominant) and V7 (the dominant), which in C Major are the chords C Major, F Major, and G7. Many of the complex chords you will learn about later are substitutes for or chromatic alterations of these three basic chord functions.
----
*'''I, IV, V Exercise:''' Play the middle &quot;C&quot; and &quot;C major&quot; chord buttons. In this book, the instruction to &quot;play a C Major chord&quot; typically means to play the bass button and a chord from the same row  (advanced players will often play a bass button from one row and a chord button from a different row, but that is for later on in your studies). Then, move upward and play a &quot;G bass note&quot; and &quot;G major&quot; chord. Assuming you are in the key of C Major, the C chord is the tonic or &quot;home chord&quot;, and the G Major (or G7) is the dominant chord. Alternate between these two positions until you are comfortable with the distance. Now try going from C Major to the row below, an F Major chord. Now play a C Major chord, an F Major chord, a G7 chord, and then the C major chord. You can loop it and play it many times. This is the I-IV-V7-I sequence which is the foundation of many popular music songs. 

Try this blues progression (each slash means play one beat of the chord, so four slashes in the first bar means to play C, C, C, C for that first bar, and so on):

C__F__C__C__  
&lt;br&gt;
////|////|////|////

F__F__C__C__
&lt;br&gt;
////|////|////|////

G7_F__C__G7_
&lt;br&gt;
////|////|////|////

Now go from the &quot;C&quot; position and jump to a &quot;D&quot; and &quot;D major&quot; chord. You would do this if your bandleader told you the group would play in the key of D. Now you are in the key of D Major, the D chord is the tonic or &quot;home chord&quot;, and the A Major (or A7) is the dominant chord. Now try going from D Major to the row below, a G Major chord, the IV chord in D. Now play a D Major chord, a G Major chord, an A7 chord, and then the D major chord. Do this until the transition becomes reasonably smooth and you land right in the middle of the buttons. 

D__G__D__D__
&lt;br&gt;
////|////|////|////

G__G__D__D__
&lt;br&gt;
////|////|////|////

A7_G__D__A7_
&lt;br&gt;
////|////|////|////

Now that you can play the I, IV, V progression, you have the tools to play the 12 bar blues progression and play many simple folk and pop songs. 
*'''I, VI, ii, V7 Exercise:''' 
Go back to the key if C. To get a key &quot;in your ear&quot;, play the tonic, then the dominant seventh several times; in this case, play C Major, G7, C Major, G7 a couple of times.

Now we are going to learn the second most important chords in a key, The essential chords are I, IV, and V (or V7). You can do a lot with I, IV, V, but if you go to jam sessions, eventually you will hear people talking about &quot;ii chords&quot; (&quot;two chords&quot;) and &quot;vi chords&quot; (&quot;six chords&quot;). In the key of C, the ii chord is d minor. The d minor chord is, like the F major, a subdominant chord (meaning that its function is to lead you to the dominant). The d minor chord and the F major are so similar that they can often be substituted for each other. In the key of C, the vi chord is &quot;a minor&quot; (in quotes to make clear that it is the minor chord built on the note &quot;a&quot;). The &quot;a minor&quot; chord is so similar to the C major chord that &quot;a minor&quot; is considered a tonic substitute. 

The chord progression I, vi, ii, V7 in the key of C is: C Major , a minor, d minor, G7. This is used in many pop and jazz songs. You play the C chord, then you need to learn to shift up to the A bass button, hopping over the G and D rows, while moving your finger to the &quot;a minor&quot; chord once your hand in position. The next two chords are  easy, as you just move down row by row from d minor to G Major (or G7).
 
Here us how you might see it written in a jam session (the minus signs mean &quot;minor&quot;):

C__a-__d-__G7_
&lt;br&gt;
////|////|////|////

Eventually, you should be able to go all the way from C to distant buttons above and below quickly and smoothly. Try to &quot;remember&quot; each distance. This takes a lot of time to do well, so don't despair if it doesn't come easily! Just keep at it.

You can mix it up by playing a seventh chord instead of the usual chord. This is a jazzy variant of I, vi, ii, V in which the vi and ii are both dominant seventh chords:

C__A7_D7_G7__
&lt;br&gt;
////|////|////|////

Many rock and blues songs use another variant chord, the bVI chord (said &quot; flat sixth&quot;). In the key of C Major, the bVI chord is Ab. A popular chord to use along with the bVI is bVII, which is Bb. The resulting progression is I-bVII-bVI-V7, which is the chords C Major, Bb Major, Ab Major, and G7. On accordion, the first three are relatively easy, as you just skip a bass row for the C to Bb and the Bb to Ab. Getting the G7 quickly after Ab Major is more challenging, because you have to jump multiple rows. One way to make it easier is to leave a rest on the fourth beat of the third bar, to give time to move your hand.

C__Bb_Ab_G7_
&lt;br&gt;
////|////|////|////
*'''Minor key i, iv, V Exercise:'''  Play the middle &quot;C&quot; and &quot;C minor&quot; chord buttons. You are in the key of C minor, the C chord is the tonic or &quot;home chord&quot;, and the G Major (or G7) is the dominant chord. Alternate between these two positions until you are comfortable with the distance. Now try going from C minor to the row below, an F minor chord. Now play a C minor chord, an F minor chord, a G7 chord, and then the C minor chord. You can loop it and play it many times. This is the i-iv-V7-i sequence which is the foundation of many minor key songs. 

Try this minor blues progression:

c-__f-__c-__c-__ 
&lt;br&gt;
////|////|////|////

f-__f-__c-__c-__
&lt;br&gt;
////|////|////|////

G7_f-__c-__G7_
&lt;br&gt;
////|////|////|////

Now go from the &quot;C&quot; position and jump to a &quot;D&quot; and &quot;D minor&quot; chord. You would do this if your bandleader told you the group would play in the key of D. Now you are in the key of D minor, the D chord is the tonic or &quot;home chord&quot;, and the A Major (or A7) is the dominant chord. Now try going from D minor to the row below, a &quot;g minor&quot; chord, the iv chord in D. Now play a D minor chord, a g minor chord, an A7 chord, and then the D minor chord. Do this until the transition becomes reasonably smooth and you land right in the middle of the buttons. 

d-__g-__d-__d-__
&lt;br&gt;
////|////|////|////

g-__g-__d-__d-__
&lt;br&gt;
////|////|////|////

A7_g-__d-__A7_
&lt;br&gt;
////|////|////|////

Flat six chord variant (the 9th and the 10th bar are changed from V7-iv to bVI7-V7):

d-_g-__d-__d-__
&lt;br&gt;
////|////|////|////

g-__g-__d-__d-__
&lt;br&gt;
////|////|////|////

Bb7_A7_d-__A7_
&lt;br&gt;
////|////|////|////


Now that you can play the i, iv, V progression, you have the tools to play the 12 bar minor  blues progression and play many simple minor key songs. 

----
*'''Oom-pah Exercise:''' 

The classic accordion accompaniment pattern is &quot;oom-pah&quot;, which is a bass note followed by a chord. Both are usually played staccato (short). To play the &quot;oom-pah&quot; pattern in C Major, play the middle &quot;C&quot; bass note and then play the &quot;C major&quot; chord button. Then, play a G bass note followed by the &quot;C major&quot; chord again. 

Some important chord progressions to practice the &quot;oom-pah&quot; pattern on are:
*I to V7 (C Major to G7 and back to C; G Major to D7 and back to G; D Major to A7 and back to D; etc.)
*i to V7 (C minor to G7 and back to C minor; G minor to D7 and back to G minor; D minor to A7 and back to D minor; etc.)
*I IV V7 I (C Major, F Major, G7, C Major)
*I ii V7 I (C Major, d minor, G7, C Major)
*I VI7 ii V7 I (C Major, A7, d minor, G7, C Major)

You should also try these progressions with the bass note and chord together.
----
&lt;big&gt;'''[[Accordion/Left hand/Lesson 1|&lt;&lt; Back to Lesson 1]] • [[Accordion/Left hand/Lesson 3|Lesson 3 &gt;&gt;]]'''&lt;/big&gt;

&lt;div style=&quot;text-align: center;&quot;&gt;&lt;big&gt;''Go to:'' [[Accordion/Left hand|Introduction]] • Lesson [[Accordion/Left hand/Lesson 1|1]]• '''2''' • [[Accordion/Left hand/Lesson 3|3]] • [[Accordion/Left hand/Lesson 4|4]]&lt;/big&gt;&lt;/div&gt;

{{BookCat}}</text>
      <sha1>5zlehbyrra6hau03dxwle2ovkr0c0h2</sha1>
    </revision>
  </page>
  <page>
    <title>Physics Course/Motion/Non - Linear Motion</title>
    <ns>0</ns>
    <id>248029</id>
    <revision>
      <id>4675763</id>
      <parentid>4599462</parentid>
      <timestamp>2026-10-12T19:43:45Z</timestamp>
      <contributor>
        <username>WereSpielChequers</username>
        <id>248949</id>
      </contributor>
      <minor />
      <comment>typo</comment>
      <origin>4675763</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1099" sha1="ho7m229e5u5k18k3zmxc7jvbwrrl86k" xml:space="preserve">Motion not in straight line like Curve motion

==Characteristics of Curve Motion==
Average acceleration
: &lt;math&gt;a = \frac{\Delta v(t)}{\Delta t} = \frac{v(t+\Delta t) - v(t)}{(t+\Delta t) - t}&lt;/math&gt;
Aerage speed
: &lt;math&gt;s = \Delta t[v(t) + \frac{\Delta v(t)}{2}]&lt;/math&gt;

Instantenous acceleration
: &lt;math&gt;a(t) = \frac{d}{dt}  v(t) = \frac{v(t+\Delta t) - v(t)}{(t+\Delta t) - t}&lt;/math&gt;
Instantenous  speed
: &lt;math&gt;s(t) = \int v(t) dt&lt;/math&gt;

==Formula of Curve motion==
:{| class=&quot;prettytable&quot; width=100% align=left
! Characteristics !! Symbol !! Calculus Equation
|-
| Speed || v || &lt;math&gt;v(t)&lt;/math&gt; || &lt;math&gt;\frac{d}{dt} s(t)&lt;/math&gt; 
|-
| Accelleration || a || &lt;math&gt;\frac{d}{dt} v(t)&lt;/math&gt; || &lt;math&gt;\frac{d^2}{dt^2} s(t)&lt;/math&gt; 
|-
| Distance || s || &lt;math&gt;\int v(t) dt&lt;/math&gt; ||  &lt;math&gt;s(t)&lt;/math&gt; 
|-
| Force || F ||  &lt;math&gt;m \frac{d}{dt}v(t) &lt;/math&gt; || &lt;math&gt;m \frac{d^2}{dt^2} s(t)&lt;/math&gt; 
|-
| Work || W   || &lt;math&gt;F \int v(t)dt&lt;/math&gt; || p &lt;math&gt;\frac{d}{dt} s(t)&lt;/math&gt;
|-
| Energy || E || &lt;math&gt;\frac{F}{t} \int v(t) dt&lt;/math&gt; || p &lt;math&gt;\frac{d^2}{dt^2} s(t)&lt;/math&gt;
|-
|}

{{BookCat}}</text>
      <sha1>ho7m229e5u5k18k3zmxc7jvbwrrl86k</sha1>
    </revision>
  </page>
  <page>
    <title>OpenSSH/Client Applications</title>
    <ns>0</ns>
    <id>248400</id>
    <revision>
      <id>4675727</id>
      <parentid>4675560</parentid>
      <timestamp>2026-10-12T12:59:22Z</timestamp>
      <contributor>
        <username>Larsnooden</username>
        <id>430753</id>
      </contributor>
      <minor />
      <comment>capitalization</comment>
      <origin>4675727</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="17475" sha1="hxvepmvuy17ic3xi04rpr7wxjymodjq" xml:space="preserve">{{BookCat}}
On the client side, [http://man.openbsd.org/ssh.1 ssh(1)], [http://man.openbsd.org/scp.1 scp(1)], and [http://man.openbsd.org/sftp.1 sftp(1)] provide a wide range of capabilities.  Interactive logins and file transfers are just the tip of the iceberg.  

: [http://man.openbsd.org/ssh.1 ssh(1)] - The basic login shell-like client program.
: [http://man.openbsd.org/sftp.1 sftp(1)] - FTP-like program that works using the SSH protocol.
: [http://man.openbsd.org/scp.1 scp(1)] - File copy program that acts like rcp(1).

: [http://man.openbsd.org/ssh_config.5 ssh_config(5)] - The client configuration file.

==The SSH client==

[http://man.openbsd.org/ssh.1 ssh(1)] is a program which provides the client side for secure, encrypted communications between  hosts over an insecure network.  Its main use is for logging into and  running programs on a remote host.  It can also be used to secure remote X11 connections and forward arbitrary TCP ports to secure legacy protocols.
ssh was made, in part, to replace insecure tools like '''rsh''' and '''telnet'''.  It has largely succeeded at this goal.  '''rsh''' and '''telnet''' are rarely seen anymore for interactive sessions or anywhere else.  
ssh can authenticate using regular passwords or with the help of a public-private key pair.  More options, such as use of Kerberos, smartcards, or one-time passwords can be configured.  

Remote login, authenticating via password:
&lt;syntaxhighlight lang=&quot;shell&quot;&gt;
$ ssh fred@somehost.example.org 
&lt;/syntaxhighlight&gt;

Another way of logging in to the same account:
&lt;syntaxhighlight lang=&quot;shell&quot;&gt;
$ ssh -l fred somehost.example.org
&lt;/syntaxhighlight&gt;

Remote programs can be run interactively when the client is run via the shell on the remote host.  Or they can be run directly when passed as an argument to the SSH client.  They can even be	 pre-configured in the authentication key or the server configuration.  

Run [http://man.openbsd.org/uname.1 uname(1)] on the remote machine:
&lt;syntaxhighlight lang=&quot;shell&quot;&gt;
$ ssh -l fred  somehost.example.org  &quot;uname -a&quot;
&lt;/syntaxhighlight&gt;

See what file systems are mounted and how much space is used there:
&lt;syntaxhighlight lang=&quot;shell&quot;&gt;
$ ssh -l fred  somehost.example.org  &quot;mount; df -h&quot;
&lt;/syntaxhighlight&gt;

It is possible to configure in great detail which programs are allowed by which accounts.  There are many combinations of options that give extra capabilities, such as re-using a single connection for multiple sessions or passing through intermediary machines.  The level of granularity can be increased even more with the help of '''sudo(8)'''.  

===SSH Client Environment Variables — Server Side===

Of course the foundation of most SSH activity centers around use of the shell.  Upon a successful connection, OpenSSH sets several environment variables. 

&lt;pre&gt;
SSH_CLIENT='192.168.223.17 36673 22'
SSH_CONNECTION='192.168.223.17 36673 192.168.223.229 22'
SSH_TTY=/dev/pts/6
&lt;/pre&gt;

'''SSH_CLIENT''' shows the address of the client system, the outgoing port number on the client system, and the incoming port on the server.  '''SSH_CONNECTION''' shows the address of the client, the outgoing port on the client, the address of the server and the incoming port on the server.  '''SSH_TTY''' names the pseudo-terminal device, abbreviated PTY, on the server used by the connection.  For more information on pseudo-terminals see [http://man.openbsd.org/ptm.4 ptm(4)], [http://man.openbsd.org/tty.1 tty(1)] and [http://man.openbsd.org/tty.4 tty(4)].  

The login session can be constrained to a single program with a predetermined set of parameters using '''ForceCommand''' in the server configuration or '''Command=&quot;...&quot;''' in the authorized keys file.  When that happens an additional environment variable '''SSH_ORIGINAL_COMMAND''' gets set.

&lt;pre&gt;
SSH_ORIGINAL_COMMAND=echo &quot;hello, world&quot;
&lt;/pre&gt;

If the server has '''ExposeAuthInfo''' set, then the '''SSH_USER_AUTH''' environment variable points to a temporary file listing details about the authentication methods used to start the current session.  

&lt;pre&gt;
SSH_USER_AUTH=/tmp/sshauth.4JmbYfF0bhF6C17
&lt;/pre&gt;

The file is removed when the session ends.  

Other variables are set depending on the user's shell settings and the system's own settings.

===SSH Client Configuration Options===
{{RightHalf|'''[[w:Generic_Security_Services_Application_Program_Interface|GSSAPI]]''', or Generic Security Service Application Program Interface, a standard interface defined  by RFC 2743 to provide a means for independent modules with means for generic authentication and secure messaging.  Kerberos V is one of the more common examples of a service using it.  }}

Configuration options can be passed to [http://man.openbsd.org/ssh.1 ssh(1)] as arguments, see the manual pages for [http://man.openbsd.org/ssh.1 ssh(1)] and [http://man.openbsd.org/ssh_config.5 ssh_config(5)] for the full list.

Connect very verbose output, [[w:Generic_Security_Services_Application_Program_Interface|GSSAPI]] authentication: 
&lt;syntaxhighlight lang=&quot;shell&quot;&gt;
$ ssh -vv -K -l account host.example.org
&lt;/syntaxhighlight&gt;

A subset of options can be defined on the server host in the user's own authorized keys file, in conjunction with specific keys.  See [http://man.openbsd.org/sshd.8 sshd(8)] for which subset exactly.  

&lt;syntaxhighlight lang=&quot;apache&quot;&gt;
command=&quot;/usr/local/sbin/backup.sh&quot;,no-pty ssh-rsa AAAAB3NzaC1yc2EAAAQEAsY6u71N...
command=&quot;/usr/games/wump&quot;,no-port-forwarding,no-pty ssh-ed25519 AAAAC3NzaC1lZDI1...
environment=&quot;gtm_dist=/usr/local/gtm/utf8&quot;,environment=&quot;gtm_principal_editing=NOINSERT:EDITING&quot; ssh-rsa AAAA8a2s809poloh05yhh...
&lt;/syntaxhighlight&gt;

Note that some directives, like setting the environment variables, are disabled by default and must be named in the server configuration before available to the client.  
More configuration directives can be set by the user in '''~/.ssh/config''' or by the system administrator in '''/etc/ssh/ssh_config'''.  These same configuration directives can be passed as arguments using '''-o'''.  See [http://man.openbsd.org/ssh_config.5 ssh_config(5)] for the full list with descriptions.  
&lt;syntaxhighlight lang=&quot;shell&quot;&gt;
$ ssh  -l fred -o &quot;ServerAliveInterval=60&quot; -o &quot;Compression=yes&quot; server.example.org
&lt;/syntaxhighlight&gt;

The system administrators of the client host can set some global defaults in '''/etc/ssh/config'''.  Some of these global settings can be targeted to a specific group or user by using a '''Match''' directive.

For example, if a particular SSH server is available via port 2022, it may be convenient to have the client try that port automatically.  Some of OpenBSD’s anonymous CVS servers accept SSH connections on this port.  However, compression should not be used in this case because CVS already uses compression.  So it should be turned off.  Thus, one could specify something like the following in the '''$HOME/.ssh/config''' configuration file so that the default port is 2022 and the connection is made without compression:

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Host anoncvs anoncvs.example.org
        Compression no
        Port 2022
&lt;/syntaxhighlight&gt;

See [http://man.openbsd.org/ssh_config.5 ssh_config(5)] for the client side and [http://man.openbsd.org/sshd_config.5 sshd_config(5)] for the server side for the full lists with descriptions.

==The SFTP client==

[http://man.openbsd.org/sftp.1 sftp(1)] is an interactive file transfer program which performs all its operations over an encrypted SSH transport channel.  It may also use many features of [http://man.openbsd.org/ssh.1 ssh(1)], such as public key authentication and compression.  It is also the name of the protocol used.  

The SFTP protocol is similar in some ways to the now venerable File Transfer Protocol (FTP), except that the entire session, including the login, is encrypted.  However, SFTP is not FTPS.  The latter old-fashioned FTP tunneled over SSH/SSL.  In contrast, SFTP is actually a whole new protocol.  [http://man.openbsd.org/sftp.1 sftp(1)] can also be made to start in a specific directory on the remote host.  

&lt;syntaxhighlight lang=&quot;shell&quot;&gt;
$ sftp fred@server.example.org:/var/www
&lt;/syntaxhighlight&gt;

Frequently, SFTP is used to connect and log into a specified host and enter an interactive command mode.  See the manual page for [http://man.openbsd.org/sftp.1 sftp(1)] for the available interactive commands such as '''get''', '''put''', '''rename''', and so on.  Also, the same configuration options that work for [http://man.openbsd.org/ssh.1 ssh(1)] also apply to [http://man.openbsd.org/sftp.1 sftp(1)].  [http://man.openbsd.org/sftp.1 sftp(1)] accepts all [http://man.openbsd.org/ssh_config.5 ssh_config(5)] options and these can be passed along as arguments at run time.  Some have explicit shortcuts.

&lt;syntaxhighlight lang=&quot;shell&quot;&gt;
$ sftp -i ~/.ssh/some.key.ed25519 fred@server.example.org:/var/www
&lt;/syntaxhighlight&gt;

While others can be specified by naming them in full using the '''-o''' option.

&lt;syntaxhighlight lang=&quot;shell&quot;&gt;
$ sftp -o &quot;ServerAliveInterval=60&quot; -o &quot;Compression=yes&quot; fred@server.example.org
&lt;/syntaxhighlight&gt;

Another way to transfer is to send or receive files automatically.  If a non-interactive authentication method is used, the whole process can be automatic using batch mode.

&lt;syntaxhighlight lang=&quot;shell&quot;&gt;
$ sftp -b session.batch -i ~/.ssh/some_key_ed25519 fred@server.example.org
&lt;/syntaxhighlight&gt;

Batch processing only works with non-interactive authentication.

==The SCP client==

[http://man.openbsd.org/scp.1 scp(1)] is used for encrypted transfers of files between hosts and is used a lot like regular [http://man.openbsd.org/cp.1 cp(1)].  Since 9.0&lt;ref name=&quot;OpenSSH_9.0&quot;&gt;{{cite web | url=https://www.openssh.org/txt/release-9.0 | title=OpenSSH 9.0 Release Notes | publisher=www.openssh.org | date=2022-04-08 | accessdate=2026-04-03 }}&lt;/ref&gt; it is based on the SFTP protocol under the hood, while the old version prior to that was inspired by the Berkeley Software Distribution (BSD) Remote Copy Protocol (RCP) for which it has been a secure replacement.  Both the old and the new versions use SSH to encrypt the connection.  

The [http://man.openbsd.org/scp.1 scp(1)] client, unlike the SFTP client, is not based on any formal standard.  It has aimed at doing more or less what old '''rcp''' did and responded the same way.  Since with it the same program must be used at both ends of the connection and interoperability is required with other implementations of SSH.  Changes in functionality would probably break that interoperability, so new features are more likely to be added to [http://man.openbsd.org/sftp.1 sftp(1)] if at all.  Thus, it is best to lean towards using [http://man.openbsd.org/sftp.1 sftp(1)] instead when possible. Again, recent versions of [http://man.openbsd.org/scp.1 scp(1)] are a front end the SFTP protocol anyway.  

Copy from remote to local:
&lt;syntaxhighlight lang=&quot;shell&quot;&gt;
$ scp myaccount@sftp.example.org:*.txt .
&lt;/syntaxhighlight&gt;

Copy from local to remote, recursively:
&lt;syntaxhighlight lang=&quot;shell&quot;&gt;
$ scp -r /etc/ myaccount@sftp.example.org:.
&lt;/syntaxhighlight&gt;

Being a front end for the SFTP protocol now, the new [http://man.openbsd.org/scp.1 scp(1)] client can cover most but not all of the behavior of the old client and is not quite bug-for-bug compatible.  One noticeable change which is fixed on the server side in OpenSSH 8.7 or later was the absence of tilde (~) expansion.  So the &quot;expand-path@openssh.com&quot; protocol extension has been added to support this.  Another area where there can potentially be trouble is when there are shell meta-characters, such as * or ?, in the file names.  

See also the section for the SFTP client above.

==GUI Clients==

There are a great many graphical utilities that support SFTP and SSH.  Many started out as transfer utilities with the outdated legacy protocol FTP and grew with the times to include SSH and SFTP support.  Sadly, many retain the epithet FTP program despite modernization.  Others are more general file managers that include SFTP support as one means of network transparency.  Most if not all provide full SFTP support including Kerberos authentication.  

Below is a partial list to give an idea of the range of options available.  

'''Bluefish''' is a website management tool and web page editor with built in support for SFTP.  Closed source competitors XMetaL and Dreamweaver are said to have at least partial support for SFTP.  No support for SFTP is available for Quanta+ or Kompozer as of this writing.  
http://bluefish.openoffice.nl/

'''Cyberduck''' is a remote file browser for the Macintosh.  It supports an impressive range of protocols in addition to SFTP.  
https://cyberduck.io/

'''Dolphin''' is a highly functional file manager for the KDE desktop, but can also be run in other desktop environments.  It includes SFTP support

'''Fetch''', by Fetch Softworks, is a reliable and well-known SFTP client for the Macintosh.  It has been around since 1989 and started life as just an FTP client.  It has many useful features combined with ease of use.  It is closed source, but academic institutions are eligible for a free of charge site license.  
http://fetchsoftworks.com/fetch/

'''FileZilla''' is presented as a FTP utility, but it has built in support for SFTP.  It is available for multiple platforms under the Free Software license, the GPL.  
http://filezilla-project.org/

'''FireFTP''' is a SFTP plugin for Mozilla Firefox.  Though it is presented as an FTP add-on, it supports SFTP.  It is available under both the MIT license and the GPL.
http://fireftp.net/

'''Fugu''', was developed by the University of Michigan research systems unix group.  It was a graphical front-end for SFTP on the Macintosh.  It was kicked to the curb in 2011 and the files archived at SourceForge.
https://sourceforge.net/projects/fugussh/files/

'''gFTP''' is a multi-threaded file transfer client
https://www.gftp.org/

'''JuiceSSH''' is an SSH Client for Android/Linux.  It uses the [http://www.jcraft.com/jsch/ jsch] Java implementation of SSH2.  
https://juicessh.com/

'''Konqueror''' is a file manager and universal document viewer for the KDE desktop, but can also be run in other environments. It includes SFTP support.  
https://apps.kde.org/konqueror/

'''lftp''' is a file transfer program that supports multiple protocols.  
http://lftp.yar.ru/

'''Midnight Commander''' is a visual file manager based on a text interface and thus usable over a terminal or console.  It includes SFTP support.  
https://midnight-commander.org/

'''Nautilus''' is the default file manager for the GNOME desktop, but can also be run in other environments.  It includes SFTP support

'''PCManFM''' is an extremely fast, lightweight, yet feature-rich file manager with tabbed browsing which is the default for LXDE.  It includes SFTP support.
https://lxqt-project.org/

'''PuTTY''' is another FOSS implementation of Telnet and SSH for both legacy and Unix platforms.  It is released under the MIT license and includes an SFTP client, PSFTP, in addition to an xterm terminal emulator and other tools like a key agent, Paegent.   It is written and maintained primarily by Simon Tatham.  
http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html 

'''Remmina''' is a remote desktop client written in GTK+ which supports multiple network protocols, including SSH.
https://www.remmina.org/

'''RemoteShell''' is the default SSH client for MorphOS, written in C using the GUI library Magic User Interface (MUI). The operating system also contains the command-line tools [http://man.openbsd.org/ssh.1 ssh(1)], [http://man.openbsd.org/scp.1 scp(1)] and [http://man.openbsd.org/sftp.1 sftp(1)].  
https://www.morphos-team.net/

'''SecPanel''' is a GUI for managing and running SSH and scp connections.  It is not a new implementation of the protocol or software-suite, but sits on top of either of the SSH software-suites
https://themediahost.de/secpanel/

'''Thunar''' is the default file manager for the XFCE desktop.  It includes SFTP support.  
https://docs.xfce.org/xfce/thunar/start

'''Transfer''' is the default SFTP client for MorphOS, written in C using the GUI library Magic User Interface (MUI).
https://www.morphos-team.net/

'''Yafc''' is Yet Another FTP Client and despite the name supports SFTP.  
https://yafc.sourceforge.net/

===Other GUI Programs with SFTP Support===

A small but growing number of graphical applications include SFTP support, some fully.  This allows reliable access to remote files more or less as if they were local.

'''celluloid''', a media player, can play remote files over SFTP.  It can accept full URLs pointing to specific files on SFTP services.  It is aware of [http://man.openbsd.org/ssh_config.5 ssh_config(5)] and can utilize shortcuts stored there.  

'''mpv''', also a media player, can play remote files over SFTP and is also aware of [http://man.openbsd.org/ssh_config.5 ssh_config(5)] settings.  

'''LibreOffice''' has SFTP support, but only for password authentication.  Keys and certificates are not supported, at least not as of LibreOffice version 24.  

A work-around for programs which don't support SFTP or lack full support for [http://man.openbsd.org/ssh_config.5 ssh_config(5)] settings is to mount the remote directory via [http://linux.die.net/man/1/sshfs sshfs] which is a user-space file system client.  

&lt;noinclude&gt;{{OpenSSH/TOC|mini}}
&lt;/noinclude&gt;
{{status|100%}}</text>
      <sha1>hxvepmvuy17ic3xi04rpr7wxjymodjq</sha1>
    </revision>
  </page>
  <page>
    <title>OpenSSH/Cookbook/Host-based Authentication</title>
    <ns>0</ns>
    <id>248419</id>
    <revision>
      <id>4675782</id>
      <parentid>4663373</parentid>
      <timestamp>2026-10-13T05:01:48Z</timestamp>
      <contributor>
        <username>Larsnooden</username>
        <id>430753</id>
      </contributor>
      <comment>use Ed25519 in examples instead of RSA, plus refinements and updates</comment>
      <origin>4675782</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="20509" sha1="q67mksiz84ryhsuvtrhd7uigkf8le9f" xml:space="preserve">&lt;noinclude&gt;{{simple chapter navigation|previous=Certificate-based Authentication|next=Load Balancing}}&lt;/noinclude&gt;
&amp;nbsp;

Host-based authentication allows hosts to authenticate on behalf of all or some of that particular host's users.  Those accounts can be all of the accounts on a system or a subset designated by the '''Match''' directive.   This type of authentication can be useful for managing computing clusters and other fairly homogeneous pools of machines.  

In all, three files on the server must be prepared for host-based authentication.  On the client only two must be modified, but the host itself must have SSH host keys assigned.  What follows sets up host-based authentication from one system to another in a single direction.  For authentication both directions, follow the procedure twice but reverse the roles of the systems.  

==Client-side Configurations for Host-based Authentication==

On the client or source host, two files must be configured and in addition at least one host key must exist:
: '''/etc/ssh/ssh_known_hosts''' - global file for public keys for known hosts
: '''/etc/ssh/ssh_config'''      - allow clients to request host-based authentication

Then the client's host keys must be created if they do not already exist:
: '''/etc/ssh/ssh_host_ecdsa_key'''
: '''/etc/ssh/ssh_host_ed25519_key'''
: '''/etc/ssh/ssh_host_rsa_key'''

These three steps need to be done on each of the client systems which will be connecting to the specified host.  Once set up, the accounts logged on one system will be able to connect to another system without further interactive authentication.  

Note that in situations environments host-based authentication might not be considered sufficient to prevent unauthorized access since it goes on a host-by-host basis, mostly.  

===1. Populate the Client with the Server's Public Keys=== 

The remote server's public host keys must be stored on the client system in the global client configuration file '''/etc/ssh/ssh_known_hosts'''.  One way to get the public keys from the server is to fetch them using [http://man.openbsd.org/ssh-keyscan.1 ssh-keyscan(1)] and save them.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keyscan server.example.com | tee -a /etc/ssh/ssh_known_hosts
&lt;/syntaxhighlight&gt;

Be sure to make a backup copy of '''/etc/ssh/ssh_known_hosts''', if it exists, before trying anything.  Another way would be to add the server's public host key to the '''~/.ssh/known_hosts''' files in the relevant accounts.  But that way is more work.  

However they are acquired and verified, the public keys listed there must obviously correspond to the private host keys on the server.  Any or all of the three types can be used, RSA, ECDSA, or Ed25519.   DSA should no longer be used.  For verification of the public keys, refer to the section on [[OpenSSH/Cookbook/Public_Key_Authentication#Verify_a_Host_Key_by_Fingerprint|how to verify a host key by fingerprint]] for some relevant methods.

===2. System-wide Client Configuration===

Two changes must be made.  First, the client's configuration must request host-based authentication when connecting to the designated systems.  Second, the client configuration file must be set to enable [http://man.openbsd.org/ssh-keysign.8 ssh-keysign(8)].  It is a helper application to access the local host keys and generate the digital signature required for host-based authentication.  Both changes can be done globally in '''/etc/ssh/ssh_config'''.  

Here is an excerpt from '''/etc/ssh/ssh_config''' on the client trying host-based authentication to all machines.  The '''Host''' directive in [http://man.openbsd.org/ssh_config.5 ssh_config(5)] can be used to further constrain access to a particular server or group of servers.

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Host *.pool.example.org
	HostbasedAuthentication yes
	EnableSSHKeysign yes
&lt;/syntaxhighlight&gt;

In some distributions, such as Red Hat Enterprise Linux 8, the '''EnableSSHKeysign''' directive may need to be placed into the general section before it will work. In that case, do this:

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Host *.pool.example.org
	HostbasedAuthentication yes

Host *
	EnableSSHKeysign yes
&lt;/syntaxhighlight&gt;

Other configuration directives can be added as needed.  For example, here are two additional settings applied to the same pool:

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Host *.pool.example.org
	HostbasedAuthentication yes
	EnableSSHKeysign yes
	ServerAliveCountMax 3
	ServerAliveInterval 60
&lt;/syntaxhighlight&gt;

If the home directory of the client host is one that is shared with other machines, say using NFS or AFS, then it may be useful to look at the '''NoHostAuthenticationForLocalhost''' directive, too.  

As a bit of trivia, the program [http://man.openbsd.org/ssh-keysign.8 ssh-keysign(8)] itself must be SUID root.  But SUID was probably set when it was installed and no changes there are needed.

===3. Set Up the Client System's Own Host Keys===

The program [http://man.openbsd.org/ssh-keysign.8 ssh-keysign(8)] needs to read the client system's private host keys in '''/etc/ssh/'''.  Installing the OpenSSH server will create these keys but if the OpenSSH server has not been installed on the client system, it does not need to be.  It is enough to have the keys by themselves.  If the client system's private host keys do not exist, it will be necessary to add them manually using [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)] before host-based authentication will work.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -A
&lt;/syntaxhighlight&gt;

The default path is '''/etc/ssh/''' when using the '''-A''' option.  

Note that although the client's system does not have to have an SSH server actually running in order to use host-based authentication to reach another system, it is entirely feasible to install but then disable or uninstall the SSH server on the client's server as a way to get the host keys in place.

==Server-side Configurations for Host-based Authentication==

Three files on the server or target host must be modified to enable and allow host-based authentication:
: '''/etc/shosts.equiv''' 	 same syntax as old '''rhosts.equiv'''
: '''/etc/ssh/ssh_known_hosts''' 	 holds the host public keys from the clients
: '''/etc/ssh/sshd_config''' 	 turns on host-based authentication

The exact location of '''shosts.equiv''' may vary depending on operating system and distro.  

===1. Registering the Allowed Client Systems with the Server===

The '''shosts.equiv''' file must contain a list of the client systems which are allowed to attempt host-based authentication.  The file can contain host names, IP addresses, or net groups.   It is best to keep this file simple and oriented to just the list of hosts, either by name or IP number.  It provides only the first cut, anyway.  For fine tuning, use [http://man.openbsd.org/sshd_config.5 sshd_config(5)] instead to set or revoke access for specific users and groups.  

It is important to note that if you are using the '''shosts.equiv file''', the user name on the client and server system must match. For instance, to connect to bob@server1.example.org, the user name on the client must also be bob. If you need user 'alice' to connect to bob@server1.example.org, you need to specify this in the '''.shosts''' file for 'bob', not in the global '''shosts.equiv''' file.

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
client1.example.org
192.0.2.102
client8.example.org -bull
@statcluster
&lt;/syntaxhighlight&gt;

This file resides in the directory '''/etc/''' in OpenBSD, which this book uses for the reference system when possible.  On other systems the file might be found in the directory '''/etc/ssh/'''.  Either way, the '''shosts.equiv''' file identifies which addresses are allowed to try authenticating.  Check the manual page for [http://man.openbsd.org/sshd.1 sshd(1)] on the actual system being used to be sure of the correct location.

Hunt for a manual page '''hosts.equiv(5)''' for more details on '''.shosts.equiv''' (and  '''.shosts'''), but consider that its use is long since deprecated and most systems won't even have that manual page.

====Leftovers from the Old Days====

Two legacy files may be on really old systems and are optionally modified if they are referred to from within '''shosts.equiv'''.  Each line in the '''netgroup''' file consists of a net group name followed by a list of the members of the net group, specifically host, user, and domain.

: '''/etc/netgroup''' - default netgroup list
: '''/etc/netgroup.db''' - netgroup database, build from netgroup

However, these are mostly legacy from the old '''rhosts''' and should be avoided.

Another leftover is using '''.shosts''' in each account's home directory.  That would be a local equivalent to '''.shosts.equiv'''.  In that way, individual users can have a local '''.shosts''' containing a list of trusted remote machines, or user-machine pairs, which are allowed to try host-based authentication.  

'''.shosts''' must not writable by any group or any other users.  Permissions set to 0644 should do it.  The usage and format of '''.shosts''' is exactly the same as '''.rhosts''', but allows host-based authentication without permitting login by the insecure, legacy tools '''rlogin''' and '''rsh'''.  The list is one line per host.  The first column is obligatory and contains the name or address of the host permitted to attempt host-based authentication.  

However a global '''.shosts.equiv''' is preferable to having '''.shosts''' in each and every home directory.

===2. Populate the Server with the Client's Public Keys=== 

The client systems listed in the server's '''shosts.equiv''' must also have their public keys in '''/etc/ssh/ssh_known_hosts''' on the server in order to be acknowledged.  There are three required data fields per line.  First is the host name or IP address or comma separated list of them, corresponding to those from '''shosts.equiv'''.  Next is the key type, with ssh-ed25519 for Ed25519 keys or ecdsa-sha2-nistp256 for ECDSA keys etc.  The third field is the public key itself.  Last, and optionally, can be a comment about the key.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
desktop ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIEGebmw+HNClPTUH6qli4a7XxJtIQaISNTcWCry0rvRQ host-based auth
&lt;/syntaxhighlight&gt;

Just like step one for the client, there are many ways of collecting the public key information from the client and getting it to the server.  It can be copied using [http://man.openbsd.org/sftp.1 sftp(1)], copied from '''~/.ssh/known_hosts''', or grabbed using [http://man.openbsd.org/ssh-keyscan.1 ssh-keyscan(1)].  Though the latter two methods only work if the client system also has an SSH server running.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keyscan -t ed25519 client.example.org | tee -a /etc/ssh/ssh_known_hosts
&lt;/syntaxhighlight&gt;

===3. System-wide Server Configuration===

The third file that must be changed on the server is [http://man.openbsd.org/sshd_config.5 sshd_config(5)].  It must be told to allow host-based authentication by setting the '''HostbasedAuthentication''' directive, either for all users or just some users or just certain groups.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
HostbasedAuthentication yes
&lt;/syntaxhighlight&gt;

Host-based authentication can be limited to specific users or groups.  Here is an example excerpt from [http://man.openbsd.org/sshd_config.5 sshd_config(5)] allowing allow any user in the group 'cluster2' to let the hosts authenticate on their behalf: 

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Match Group cluster2
        HostbasedAuthentication yes
&lt;/syntaxhighlight&gt;

Certain host keys types can be allowed using '''HostbasedAcceptedAlgorithms''', which was formerly '''HostbasedAcceptedKeyTypes''', with a comma-delimited list of acceptable key algorithms.  All the key algorithms which are to be allowed must be listed because those not listed are not allowed.  Patterns can be used in the whitelist.  Below, Ed25519 and ECDSA keys are allowed, but others, such as RSA and DSA are not.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
HostbasedAuthentication yes
HostbasedAcceptedAlgorithms ssh-ed25519*,ecdsa-sha2*
&lt;/syntaxhighlight&gt;

====Host Names and Other DNS Matters====

Make complete DNS entries for the clients if possible, including allowing reverse lookups.  However, it may also be necessary to set '''UseDNS''' to 'yes' in [http://man.openbsd.org/sshd_config.5 sshd_config(5)] on the server.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
HostbasedAuthentication yes
UseDNS yes
&lt;/syntaxhighlight&gt;

Otherwise, [http://man.openbsd.org/sshd.8 sshd(8)] may report a mismatch in the logs:

&lt;syntaxhighlight lang=&quot;text&quot;&gt;
Sep 24 15:16:02 server sshd[1397]: userauth_hostbased mismatch: client sends client.example.org, but we resolve 203.0.113.68 to 203.0.113.68
Sep 24 15:16:02 server sshd[1397]: userauth_hostbased mismatch: client sends client.example.org, but we resolve 203.0.113.68 to 203.0.113.68
Sep 24 15:16:02 server sshd[1397]: Connection closed by authenticating user fred 203.0.113.68 port 36576 [preauth]
&lt;/syntaxhighlight&gt;

If the client machine is not listed in DNS, then the server might have trouble recognizing it.  In that case you might have to tell [http://man.openbsd.org/sshd.8 sshd(8)] not to do reverse lookups in DNS for connecting hosts.  This can be a problem on informal LANs where hosts have addresses but no registered host names.  Here is an example from '''/etc/ssh/sshd_config''' to work around lack of DNS records for the client using the '''HostbasedUsesNameFromPacketOnly''' directive.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
HostbasedAuthentication yes
HostbasedUsesNameFromPacketOnly yes
&lt;/syntaxhighlight&gt;

Don't add this directive unless the normal way fails.  Otherwise it can interfere and prevent authentication.  
  
Sometimes the host trying to connect gets identified to the target host as something other than what was expected.  That too will block authentication.  So make sure that the configuration files match what the host actually calls itself.

==Debugging==

Configuration should be quite straight forward, with small changes in only three files on the server and two on the client to manage.  If there are difficulties, be prepared to run [http://man.openbsd.org/sshd.8 sshd(8)] standalone at debug level 1 ('''-d''') to 3 ('''-ddd''') and [http://man.openbsd.org/ssh.1 ssh(1)] at debug level 3 ('''-vvv''') a few times to see what you missed.  The mistakes have to be cleared up in the right order, so take it one step at a time.  

If the server produces the message &quot;''debug3: auth_rhosts2_raw: no hosts access file exists''&quot; turns up, the '''shosts.equiv''' file is probably in the wrong place or missing and no fallback '''~/.shosts''' lies in reserve in that account.  

If the server cannot find the key for the client despite it being in '''known_hosts''' and if the client's host name is not in regular DNS, then it might be necessary to add the directive '''HostbasedUsesNameFromPacketOnly'''.  This uses the name supplied by the client itself rather than doing a DNS lookup.  

Here is a sample excerpt from a successful host-based authentication for user 'fred' from the host at ''192.0.2.102'', also known as ''desktop1'', using an Ed25519 key.  The server first tries looking for an ECDSA key and does not find it.   
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
# /usr/sbin/sshd -ddd
debug2: load_server_config: filename /etc/ssh/sshd_config
...
debug3: /etc/ssh/sshd_config:111 setting HostbasedAuthentication yes
debug3: /etc/ssh/sshd_config:112 setting HostbasedUsesNameFromPacketOnly yes
...
debug1: sshd version OpenSSH_6.8, LibreSSL 2.1
...
debug1: userauth-request for user fred service ssh-connection method hostbased [preauth]
debug1: attempt 1 failures 0 [preauth]
debug2: input_userauth_request: try method hostbased [preauth]
debug1: userauth_hostbased: cuser fred chost desktop1. pkalg ecdsa-sha2-nistp256 slen 100 [preauth]
...
debug3: mm_answer_keyallowed: key_from_blob: 0x76eede00
debug2: hostbased_key_allowed: chost desktop1. resolvedname 192.0.2.102 ipaddr 192.0.2.102
debug2: stripping trailing dot from chost desktop1.
debug2: auth_rhosts2: clientuser fred hostname desktop1 ipaddr desktop1
debug1: temporarily_use_uid: 1000/1000 (e=0/0)
debug1: restore_uid: 0/0
debug1: fd 4 clearing O_NONBLOCK
debug2: hostbased_key_allowed: access allowed by auth_rhosts2
debug3: hostkeys_foreach: reading file &quot;/etc/ssh/ssh_known_hosts&quot;
debug3: record_hostkey: found key type ED25519 in file /etc/ssh/ssh_known_hosts:1
debug3: load_hostkeys: loaded 1 keys from desktop1
debug1: temporarily_use_uid: 1000/1000 (e=0/0)
debug3: hostkeys_foreach: reading file &quot;/home/fred/.ssh/known_hosts&quot;
debug1: restore_uid: 0/0
debug1: check_key_in_hostfiles: key for host desktop1 not found
Failed hostbased for fred from 192.0.2.102 port 10827 ssh2: ECDSA SHA256:CEXGTmrVgeY1qEiwFe2Yy3XqrWdjm98jKmX0LK5mlQg, client user &quot;fred&quot;, client host &quot;desktop1&quot;
debug3: mm_answer_keyallowed: key 0x76eede00 is not allowed
debug3: mm_request_send entering: type 23
debug2: userauth_hostbased: authenticated 0 [preauth]
debug3: userauth_finish: failure partial=0 next methods=&quot;publickey,password,keyboard-interactive,hostbased&quot; [preauth]
debug1: userauth-request for user fred service ssh-connection method hostbased [preauth]
debug1: attempt 2 failures 1 [preauth]
debug2: input_userauth_request: try method hostbased [preauth]
debug1: userauth_hostbased: cuser fred chost desktop1. pkalg ssh-ed25519 slen 83 [preauth]
debug3: mm_key_allowed entering [preauth]
debug3: mm_request_send entering: type 22 [preauth]
debug3: mm_key_allowed: waiting for MONITOR_ANS_KEYALLOWED [preauth]
debug3: mm_request_receive_expect entering: type 23 [preauth]
debug3: mm_request_receive entering [preauth]
debug3: mm_request_receive entering
debug3: monitor_read: checking request 22
debug3: mm_answer_keyallowed entering
debug3: mm_answer_keyallowed: key_from_blob: 0x7e499180
debug2: hostbased_key_allowed: chost desktop1. resolvedname 192.0.2.102 ipaddr 192.0.2.102
debug2: stripping trailing dot from chost desktop1.
debug2: auth_rhosts2: clientuser fred hostname desktop1 ipaddr desktop1
debug1: temporarily_use_uid: 1000/1000 (e=0/0)
debug1: restore_uid: 0/0
debug1: fd 4 clearing O_NONBLOCK
debug2: hostbased_key_allowed: access allowed by auth_rhosts2
debug3: hostkeys_foreach: reading file &quot;/etc/ssh/ssh_known_hosts&quot;
debug3: record_hostkey: found key type ED25519 in file /etc/ssh/ssh_known_hosts:1
debug3: load_hostkeys: loaded 1 keys from desktop1
debug1: temporarily_use_uid: 1000/1000 (e=0/0)
debug3: hostkeys_foreach: reading file &quot;/home/fred/.ssh/known_hosts&quot;
debug1: restore_uid: 0/0
debug1: check_key_in_hostfiles: key for desktop1 found at /etc/ssh/ssh_known_hosts:1
Accepted ED25519 public key SHA256:BDBRg/JZ36+PKYSQTJDsWNW9rAfmUQCgWcY7desk/+Q from fred@desktop1
debug3: mm_answer_keyallowed: key 0x7e499180 is allowed
debug3: mm_request_send entering: type 23
debug3: mm_key_verify entering [preauth]
debug3: mm_request_send entering: type 24 [preauth]
debug3: mm_key_verify: waiting for MONITOR_ANS_KEYVERIFY [preauth]
debug3: mm_request_receive_expect entering: type 25 [preauth]
debug3: mm_request_receive entering [preauth]
debug3: mm_request_receive entering
debug3: monitor_read: checking request 24
debug3: mm_answer_keyverify: key 0x7e49a700 signature verified
debug3: mm_request_send entering: type 25
Accepted hostbased for fred from 192.0.2.102 port 10827 ssh2: ED25519 SHA256:BDBRg/JZ36+PKYSQTJDsWNW9rAfmUQCgWcY7desk/+Q, client user &quot;fred&quot;, client host &quot;desktop1&quot;
debug1: monitor_child_preauth: fred has been authenticated by privileged process
...
&lt;/syntaxhighlight&gt;

Note any warnings or error messages and read them carefully.  If there is too much output, remember the '''-e''' option for the server and use it to save the debugging output to a separate file and then read that file afterwards.  

Since this method relies on the client as well as the server, running the client with increased verbosity can sometimes help too.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -v fred@server.example.org
$ ssh -vv fred@server.example.org
$ ssh -vvv fred@server.example.org
&lt;/syntaxhighlight&gt;

If there is too much output from the client to handle, remember the '''-E''' option and redirect the debug logs to a file and then read that file at leisure.  

&lt;noinclude&gt;{{OpenSSH/TOC|mini}}&lt;/noinclude&gt;
{{BookCat}}
{{status|100%}}</text>
      <sha1>q67mksiz84ryhsuvtrhd7uigkf8le9f</sha1>
    </revision>
    <revision>
      <id>4675783</id>
      <parentid>4675782</parentid>
      <timestamp>2026-10-13T05:20:29Z</timestamp>
      <contributor>
        <username>Larsnooden</username>
        <id>430753</id>
      </contributor>
      <comment>use Ed25519 in examples instead of RSA, plus refinements and updates</comment>
      <origin>4675783</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="20764" sha1="4y0s7th36r140lnssa23kie3cgsirxd" xml:space="preserve">&lt;noinclude&gt;{{simple chapter navigation|previous=Certificate-based Authentication|next=Load Balancing}}&lt;/noinclude&gt;
&amp;nbsp;

Host-based authentication allows hosts to authenticate on behalf of all or some of a particular host's user accounts.  Those accounts can be all which are on a system or they can be a subset designated by the '''Match''' directive.   This type of authentication can be useful for managing computing clusters and other fairly homogeneous pools of machines.  

In all, three files on the server must be prepared for host-based authentication.  On the client only two files must be modified, but the host itself must have SSH host keys assigned.  What follows sets up host-based authentication from one system to another in a single direction.  For authentication both directions, follow the procedure twice but reverse the roles of the systems.  

==Client-side Configurations for Host-based Authentication==

On the client or source host, two files must be configured and in addition at least one host key must exist:
: '''/etc/ssh/ssh_known_hosts''' - global file for public keys for known hosts
: '''/etc/ssh/ssh_config'''      - allow clients to request host-based authentication

Then the client's host keys must be created if they do not already exist:
: '''/etc/ssh/ssh_host_ecdsa_key'''
: '''/etc/ssh/ssh_host_ed25519_key'''
: '''/etc/ssh/ssh_host_mldsa44_ed25519_key'''
: '''/etc/ssh/ssh_host_rsa_key'''

Note that in some situations and environments host-based authentication alone might not be considered sufficient to prevent unauthorized access since it goes on a host-by-host basis, mostly.  

The following three steps need to be done on each of the client systems which will be connecting to the specified host using host-based authentication.  Once set up, the accounts logged on one system will be able to connect to another system without further interactive authentication.  

===1. Populate the Client with the Server's Public Keys=== 

The remote server's public host keys must be stored on the client system in the global client configuration file '''/etc/ssh/ssh_known_hosts'''.  One way to get the public keys from the server is to fetch them using [http://man.openbsd.org/ssh-keyscan.1 ssh-keyscan(1)] and save them.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keyscan server.example.com | tee -a /etc/ssh/ssh_known_hosts
&lt;/syntaxhighlight&gt;

Be sure to make a backup copy of '''/etc/ssh/ssh_known_hosts''', if it exists, before trying anything.  Another way would be to add the server's public host key to the '''~/.ssh/known_hosts''' files in the relevant accounts.  But that way is more work.  

However they are acquired and verified, the public keys listed there must obviously correspond to the private host keys on the server.  Any or all of the key types can be used, RSA, ECDSA, Ed25519, or MLDSA44-Ed25519.   However, it is probably time to avoid RSA.  For verification of the public keys, refer to the section on [[OpenSSH/Cookbook/Public_Key_Authentication#Verify_a_Host_Key_by_Fingerprint|how to verify a host key by fingerprint]] for some relevant methods.

===2. System-wide Client Configuration===

Two changes must be made.  First, the client's configuration must request host-based authentication when connecting to the designated systems.  Second, the client configuration file must be set to enable [http://man.openbsd.org/ssh-keysign.8 ssh-keysign(8)].  It is a helper application to access the local host keys and generate the digital signature required for host-based authentication.  Both changes can be done globally in '''/etc/ssh/ssh_config'''.  

Here is an excerpt from '''/etc/ssh/ssh_config''' on the client trying host-based authentication to all machines.  The '''Host''' directive in [http://man.openbsd.org/ssh_config.5 ssh_config(5)] can be used to further constrain access to a particular server or group of servers.

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Host *.pool.example.org
        HostbasedAuthentication yes
        EnableSSHKeysign yes
&lt;/syntaxhighlight&gt;

In some distributions, such as Red Hat Enterprise Linux 8, the '''EnableSSHKeysign''' directive may need to be placed into the general section before it will work. In that case, do this:

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Host *.pool.example.org
        HostbasedAuthentication yes

Host *
        EnableSSHKeysign yes
&lt;/syntaxhighlight&gt;

Other configuration directives can be added as needed.  For example, here are two additional settings applied to the same pool:

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Host *.pool.example.org
        HostbasedAuthentication yes
        EnableSSHKeysign yes
        ServerAliveCountMax 3
        ServerAliveInterval 60
&lt;/syntaxhighlight&gt;

If the home directory of the client host is one that is shared with other machines, say using NFS or AFS, then it may be useful to look at the '''NoHostAuthenticationForLocalhost''' directive, too.  

As a bit of trivia, the program [http://man.openbsd.org/ssh-keysign.8 ssh-keysign(8)] itself must be SUID root.  But SUID was probably set when it was installed and no changes there are needed.

===3. Set Up the Client System's Own Host Keys===

The program [http://man.openbsd.org/ssh-keysign.8 ssh-keysign(8)] needs to read the client system's private host keys in '''/etc/ssh/'''.  Installing the OpenSSH server will create these keys but if the OpenSSH server has not been installed on the client system, it does not need to be.  It is enough to have the keys by themselves.  If the client system's private host keys do not exist, it will be necessary to add them manually using [http://man.openbsd.org/ssh-keygen.1 ssh-keygen(1)] before host-based authentication will work.  
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keygen -A
&lt;/syntaxhighlight&gt;

The default path is '''/etc/ssh/''' when using the '''-A''' option.  

Note that although the client's system does not have to have an SSH server actually running in order to use host-based authentication to reach another system, it is entirely feasible to install and then disable or uninstall the SSH server on the client's server as a way to get the host keys in place.

==Server-side Configurations for Host-based Authentication==

Three files on the server or target host must be modified to enable and allow host-based authentication:
: '''/etc/shosts.equiv''' 	 same syntax as old '''rhosts.equiv'''
: '''/etc/ssh/ssh_known_hosts''' 	 holds the host public keys from the clients
: '''/etc/ssh/sshd_config''' 	 turns on host-based authentication

The exact location of '''shosts.equiv''' may vary depending on operating system and distro.  

===1. Registering the Allowed Client Systems with the Server===

The '''shosts.equiv''' file must contain a list of the client systems which are allowed to attempt host-based authentication.  The file can contain host names, IP addresses, or net groups.   It is best to keep this file simple and oriented to just the list of hosts, either by name or IP number.  It provides only the first cut, anyway.  For fine tuning, use [http://man.openbsd.org/sshd_config.5 sshd_config(5)] instead to set or revoke access for specific users and groups.  

It is important to note that if you are using the '''shosts.equiv file''', the user name on the client and server system must match. For instance, to connect to bob@server1.example.org, the user name on the client must also be bob. If you need user 'alice' to connect to bob@server1.example.org, you need to specify this in the '''.shosts''' file for 'bob', not in the global '''shosts.equiv''' file.

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
client1.example.org
192.0.2.102
client8.example.org -bull
@statcluster
&lt;/syntaxhighlight&gt;

This file resides in the directory '''/etc/''' in OpenBSD, which this book uses for the reference system when possible.  On other systems the file might be found in the directory '''/etc/ssh/'''.  Either way, the '''shosts.equiv''' file identifies which addresses are allowed to try authenticating.  Check the manual page for [http://man.openbsd.org/sshd.1 sshd(1)] on the actual system being used to be sure of the correct location.

Hunt for a manual page '''hosts.equiv(5)''' for more details on '''.shosts.equiv''' (and  '''.shosts'''), but consider that its use is long since deprecated and most systems won't even have that manual page.

====Leftovers from the Old Days====

Two legacy files may be on really old systems and are optionally modified if they are referred to from within '''shosts.equiv'''.  Each line in the '''netgroup''' file consists of a net group name followed by a list of the members of the net group, specifically host, user, and domain.

: '''/etc/netgroup''' - default netgroup list
: '''/etc/netgroup.db''' - netgroup database, build from netgroup

However, these are mostly legacy from the old '''rhosts''' and should be avoided.

Another leftover is using '''.shosts''' in each account's home directory.  That would be a local equivalent to '''.shosts.equiv'''.  In that way, individual users can have a local '''.shosts''' containing a list of trusted remote machines, or user-machine pairs, which are allowed to try host-based authentication.  

'''.shosts''' must not writable by any group or any other users.  Permissions set to 0644 should do it.  The usage and format of '''.shosts''' is exactly the same as '''.rhosts''', but allows host-based authentication without permitting login by the insecure, legacy tools '''rlogin''' and '''rsh'''.  The list is one line per host.  The first column is obligatory and contains the name or address of the host permitted to attempt host-based authentication.  

However a global '''.shosts.equiv''' is preferable to having '''.shosts''' in each and every home directory.

===2. Populate the Server with the Client's Public Keys=== 

The client systems listed in the server's '''shosts.equiv''' must also have their public keys in '''/etc/ssh/ssh_known_hosts''' on the server in order to be acknowledged.  There are three required data fields per line.  First is the host name or IP address or comma separated list of them, corresponding to those from '''shosts.equiv'''.  Next is the key type, with ssh-ed25519 for Ed25519 keys or ecdsa-sha2-nistp256 for ECDSA keys etc.  The third field is the public key itself.  Last, and optionally, can be a comment about the key.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
desktop ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIEGebmw+HNClPTUH6qli4a7XxJtIQaISNTcWCry0rvRQ host-based auth
&lt;/syntaxhighlight&gt;

Just like step one for the client, there are many ways of collecting the public key information from the client and getting it to the server.  It can be copied using [http://man.openbsd.org/sftp.1 sftp(1)], copied from '''~/.ssh/known_hosts''', or grabbed using [http://man.openbsd.org/ssh-keyscan.1 ssh-keyscan(1)].  Though the latter two methods only work if the client system also has an SSH server running.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh-keyscan -t ed25519 client.example.org | tee -a /etc/ssh/ssh_known_hosts
&lt;/syntaxhighlight&gt;

===3. System-wide Server Configuration===

The third file that must be changed on the server is [http://man.openbsd.org/sshd_config.5 sshd_config(5)].  It must be told to allow host-based authentication by setting the '''HostbasedAuthentication''' directive, either for all users or just some users or just certain groups.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
HostbasedAuthentication yes
&lt;/syntaxhighlight&gt;

Host-based authentication can be limited to specific users or groups.  Here is an example excerpt from [http://man.openbsd.org/sshd_config.5 sshd_config(5)] allowing allow any user in the group 'cluster2' to let the hosts authenticate on their behalf: 

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Match Group cluster2
        HostbasedAuthentication yes
&lt;/syntaxhighlight&gt;

Certain host keys types can be allowed using '''HostbasedAcceptedAlgorithms''', which was formerly '''HostbasedAcceptedKeyTypes''', with a comma-delimited list of acceptable key algorithms.  All the key algorithms which are to be allowed must be listed because those not listed are not allowed.  Patterns can be used in the whitelist.  Below, MLDSA44-Ed25519, Ed25519, and ECDSA keys are allowed, but others, such as RSA and DSA are not.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
HostbasedAuthentication yes
HostbasedAcceptedAlgorithms ssh-mldsa44-ed25519*,ssh-ed25519*,ecdsa-sha2*
&lt;/syntaxhighlight&gt;

====Host Names and Other DNS Matters====

Make complete DNS entries for the clients if possible, including allowing reverse lookups.  However, it may also be necessary to set '''UseDNS''' to 'yes' in [http://man.openbsd.org/sshd_config.5 sshd_config(5)] on the server.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
HostbasedAuthentication yes
UseDNS yes
&lt;/syntaxhighlight&gt;

Otherwise, [http://man.openbsd.org/sshd.8 sshd(8)] may report a mismatch in the logs:

&lt;syntaxhighlight lang=&quot;text&quot;&gt;
Sep 24 15:16:02 server sshd[1397]: userauth_hostbased mismatch: client sends client.example.org, but we resolve 203.0.113.68 to 203.0.113.68
Sep 24 15:16:02 server sshd[1397]: userauth_hostbased mismatch: client sends client.example.org, but we resolve 203.0.113.68 to 203.0.113.68
Sep 24 15:16:02 server sshd[1397]: Connection closed by authenticating user fred 203.0.113.68 port 36576 [preauth]
&lt;/syntaxhighlight&gt;

If the client machine is not listed in DNS, then the server might have trouble recognizing it.  In that case you might have to tell [http://man.openbsd.org/sshd.8 sshd(8)] not to do reverse lookups in DNS for connecting hosts.  This can be a problem on informal LANs where hosts have addresses but no registered host names.  Here is an example from '''/etc/ssh/sshd_config''' to work around lack of DNS records for the client using the '''HostbasedUsesNameFromPacketOnly''' directive.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
HostbasedAuthentication yes
HostbasedUsesNameFromPacketOnly yes
&lt;/syntaxhighlight&gt;

Don't add this directive unless the normal way fails.  Otherwise it can interfere and prevent authentication.  
  
Sometimes the host trying to connect gets identified to the target host as something other than what was expected.  That too will block authentication.  So make sure that the configuration files match what the host actually calls itself.

==Debugging==

Configuration should be quite straight forward, with small changes in only three files on the server and two on the client to manage.  If there are difficulties, be prepared to run [http://man.openbsd.org/sshd.8 sshd(8)] standalone at debug level 1 ('''-d''') to 3 ('''-d -d -d''') and [http://man.openbsd.org/ssh.1 ssh(1)] at debug level 3 ('''-v -v -v''') a few times to see what you missed.  The mistakes have to be cleared up in the right order, so take it one step at a time.  

If the server produces the message &quot;''debug3: auth_rhosts2_raw: no hosts access file exists''&quot; turns up, the '''shosts.equiv''' file is probably in the wrong place or missing and no fallback '''~/.shosts''' lies in reserve in that account.  

If the server cannot find the key for the client despite it being in '''known_hosts''' and if the client's host name is not in regular DNS, then it might be necessary to add the directive '''HostbasedUsesNameFromPacketOnly'''.  This uses the name supplied by the client itself rather than doing a DNS lookup.  

Here is a sample excerpt from a successful host-based authentication for user 'fred' from the host at ''192.0.2.102'', also known as ''desktop1'', using an Ed25519 key.  The server first tries looking for an ECDSA key and does not find it.   
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
# /usr/sbin/sshd -ddd
debug2: load_server_config: filename /etc/ssh/sshd_config
...
debug3: /etc/ssh/sshd_config:111 setting HostbasedAuthentication yes
debug3: /etc/ssh/sshd_config:112 setting HostbasedUsesNameFromPacketOnly yes
...
debug1: sshd version OpenSSH_6.8, LibreSSL 2.1
...
debug1: userauth-request for user fred service ssh-connection method hostbased [preauth]
debug1: attempt 1 failures 0 [preauth]
debug2: input_userauth_request: try method hostbased [preauth]
debug1: userauth_hostbased: cuser fred chost desktop1. pkalg ecdsa-sha2-nistp256 slen 100 [preauth]
...
debug3: mm_answer_keyallowed: key_from_blob: 0x76eede00
debug2: hostbased_key_allowed: chost desktop1. resolvedname 192.0.2.102 ipaddr 192.0.2.102
debug2: stripping trailing dot from chost desktop1.
debug2: auth_rhosts2: clientuser fred hostname desktop1 ipaddr desktop1
debug1: temporarily_use_uid: 1000/1000 (e=0/0)
debug1: restore_uid: 0/0
debug1: fd 4 clearing O_NONBLOCK
debug2: hostbased_key_allowed: access allowed by auth_rhosts2
debug3: hostkeys_foreach: reading file &quot;/etc/ssh/ssh_known_hosts&quot;
debug3: record_hostkey: found key type ED25519 in file /etc/ssh/ssh_known_hosts:1
debug3: load_hostkeys: loaded 1 keys from desktop1
debug1: temporarily_use_uid: 1000/1000 (e=0/0)
debug3: hostkeys_foreach: reading file &quot;/home/fred/.ssh/known_hosts&quot;
debug1: restore_uid: 0/0
debug1: check_key_in_hostfiles: key for host desktop1 not found
Failed hostbased for fred from 192.0.2.102 port 10827 ssh2: ECDSA SHA256:CEXGTmrVgeY1qEiwFe2Yy3XqrWdjm98jKmX0LK5mlQg, client user &quot;fred&quot;, client host &quot;desktop1&quot;
debug3: mm_answer_keyallowed: key 0x76eede00 is not allowed
debug3: mm_request_send entering: type 23
debug2: userauth_hostbased: authenticated 0 [preauth]
debug3: userauth_finish: failure partial=0 next methods=&quot;publickey,password,keyboard-interactive,hostbased&quot; [preauth]
debug1: userauth-request for user fred service ssh-connection method hostbased [preauth]
debug1: attempt 2 failures 1 [preauth]
debug2: input_userauth_request: try method hostbased [preauth]
debug1: userauth_hostbased: cuser fred chost desktop1. pkalg ssh-ed25519 slen 83 [preauth]
debug3: mm_key_allowed entering [preauth]
debug3: mm_request_send entering: type 22 [preauth]
debug3: mm_key_allowed: waiting for MONITOR_ANS_KEYALLOWED [preauth]
debug3: mm_request_receive_expect entering: type 23 [preauth]
debug3: mm_request_receive entering [preauth]
debug3: mm_request_receive entering
debug3: monitor_read: checking request 22
debug3: mm_answer_keyallowed entering
debug3: mm_answer_keyallowed: key_from_blob: 0x7e499180
debug2: hostbased_key_allowed: chost desktop1. resolvedname 192.0.2.102 ipaddr 192.0.2.102
debug2: stripping trailing dot from chost desktop1.
debug2: auth_rhosts2: clientuser fred hostname desktop1 ipaddr desktop1
debug1: temporarily_use_uid: 1000/1000 (e=0/0)
debug1: restore_uid: 0/0
debug1: fd 4 clearing O_NONBLOCK
debug2: hostbased_key_allowed: access allowed by auth_rhosts2
debug3: hostkeys_foreach: reading file &quot;/etc/ssh/ssh_known_hosts&quot;
debug3: record_hostkey: found key type ED25519 in file /etc/ssh/ssh_known_hosts:1
debug3: load_hostkeys: loaded 1 keys from desktop1
debug1: temporarily_use_uid: 1000/1000 (e=0/0)
debug3: hostkeys_foreach: reading file &quot;/home/fred/.ssh/known_hosts&quot;
debug1: restore_uid: 0/0
debug1: check_key_in_hostfiles: key for desktop1 found at /etc/ssh/ssh_known_hosts:1
Accepted ED25519 public key SHA256:BDBRg/JZ36+PKYSQTJDsWNW9rAfmUQCgWcY7desk/+Q from fred@desktop1
debug3: mm_answer_keyallowed: key 0x7e499180 is allowed
debug3: mm_request_send entering: type 23
debug3: mm_key_verify entering [preauth]
debug3: mm_request_send entering: type 24 [preauth]
debug3: mm_key_verify: waiting for MONITOR_ANS_KEYVERIFY [preauth]
debug3: mm_request_receive_expect entering: type 25 [preauth]
debug3: mm_request_receive entering [preauth]
debug3: mm_request_receive entering
debug3: monitor_read: checking request 24
debug3: mm_answer_keyverify: key 0x7e49a700 signature verified
debug3: mm_request_send entering: type 25
Accepted hostbased for fred from 192.0.2.102 port 10827 ssh2: ED25519 SHA256:BDBRg/JZ36+PKYSQTJDsWNW9rAfmUQCgWcY7desk/+Q, client user &quot;fred&quot;, client host &quot;desktop1&quot;
debug1: monitor_child_preauth: fred has been authenticated by privileged process
...
&lt;/syntaxhighlight&gt;

Note any warnings or error messages and read them carefully.  If there is too much output, remember the '''-e''' option for the server and use it to save the debugging output to a separate file and then read that file afterwards.  

Since this method relies on the client as well as the server, running the client with increased verbosity can sometimes help too.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -v fred@server.example.org
$ ssh -v -v fred@server.example.org
$ ssh -v -v -v fred@server.example.org
&lt;/syntaxhighlight&gt;

If there is too much output from the client to handle, remember the '''-E''' option to redirect the debug logs into a file and then read that file at leisure.  

&lt;noinclude&gt;{{OpenSSH/TOC|mini}}&lt;/noinclude&gt;
{{BookCat}}
{{status|100%}}</text>
      <sha1>4y0s7th36r140lnssa23kie3cgsirxd</sha1>
    </revision>
  </page>
  <page>
    <title>OpenSSH/Third Party Utilities</title>
    <ns>0</ns>
    <id>248567</id>
    <revision>
      <id>4675721</id>
      <parentid>4675710</parentid>
      <timestamp>2026-10-12T12:27:49Z</timestamp>
      <contributor>
        <username>Larsnooden</username>
        <id>430753</id>
      </contributor>
      <comment>linebreaks before URLs</comment>
      <origin>4675721</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="8767" sha1="n9u20mcl5agpb0d4cl89655y609gsc4" xml:space="preserve">: [https://www.harding.motd.ca/autossh/ autossh] - Automatically restart SSH sessions and tunnels 
: [http://gstm.sourceforge.net/ gstm] - a graphical front-end for managing SSH-tunneled port redirects
: [http://linux.die.net/man/1/keychain keychain] - re-use ssh-agent and/or gpg-agent between logins
: [http://linux.die.net/man/1/rsync rsync] - synchronizes files and directories using delta encoding
: [http://manpages.debian.net/cgi-bin/man.cgi?query=scanssh scanssh] - a scanner for SSH hosts and some kinds of proxies
: [https://github.com/arthepsy/ssh-audit ssh-audit] - identifies the server's banner, key exchange, encryption, MAC, compression, compatibility, and other information.
: [http://linux.die.net/man/1/sshfp sshfp] - generates SSHFP DNS records from '''known_hosts''' files or ssh-keyscan(1)
: [http://linux.die.net/man/1/sshfs sshfs] - a user-space file system client based on SFTP
: [http://www.sshguard.net/ sshguard] - an intrusion detection system with packet filtering
: [https://www.rutschle.net/tech/sslh/README.html sslh] - a protocol demultiplexer
: [https://gitlab.freedesktop.org/mstoeckl/waypipe waypipe] - proxies graphical Wayland clients for systems using Wayland instead of X11.

----

==gstm (Gnome SSH Tunnel Manager)==

'''gstm''' is a graphical front-end for managing SSH connections and especially port forwarding.&lt;br /&gt;
http://sourceforge.net/projects/gstm/

==keychain==

'''keychain''' is another manager for [http://man.openbsd.org/ssh-agent.1 ssh-agent(1)] to allow multiple shells and processes, including [http://man.openbsd.org/cron.8 cron(8)] jobs, to use the keys held by the agent.  It is often integrated into desktop-specific tools like Apple Keychain on OS X or kdewallet for KDE.  &lt;br /&gt;
http://www.funtoo.org/en/security/keychain/intro/

==rsync==

'''rsync''' is a file transfer utility to transfer files between computers very efficiently. It can run on top of SSH or use its own protocol.  SSH is the default.  &lt;br /&gt;
http://rsync.samba.org/

See the Cookbook section on [[OpenSSH/Cookbook/Automated_Backup|Automated Backup]] for examples on using '''rsync''' live or in scripts.  

==scanssh==
'''scanssh''' scans hosts and networks for running services&lt;ref name=&quot;Provos_ScanSSH&quot;&gt;{{cite web |url=http://www.citi.umich.edu/u/provos/papers/scanssh.pdf
 |title=ScanSSH - Scanning the Internet for SSH Servers|author=Niels Provos| author2=Peter Honeyman |publisher=Center for Information Technology Integration (CITI), University of Michigan|year=2001|accessdate=2016-03-05}}&lt;/ref&gt;.  It checks the version number of the server and displays the results in a list.  It detects ssh, sftp and several kinds of  SOCKS, HTTP, and telnet  proxies.  

Scan a small subnet for ssh servers:
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ sudo scanssh -n 22 -s ssh 192.168.100.32/26
&lt;/syntaxhighlight&gt;

Scan the same small network for SOCKS proxies:
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ sudo scanssh -s socks5,socks4 192.168.100.32/26
&lt;/syntaxhighlight&gt;
Variable scanning speeds can be set as well as random sampling.  Open proxy detection scans to detect open proxies on common ports.

Scan 1000 hosts randomly selected from 172.16.1.1 through 172.31.254.254, at a rate of 200 per second:
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ sudo scanssh -r 200 -p random(1000)/172.16.0.0/12
&lt;/syntaxhighlight&gt;

The hosts and networks to be scanned can be either specified as an IPv4 address or a CIDR-like IP prefix with IP address and network mask.  Ports can be appended by adding a colon at the end of address specification.  The sequence of hosts scanned is random, but that can be modified by the following two parameters, '''random''' and '''split''':

'''random(n[,seed])/''' selects a sample of ''n'' random addresses from the range specified as targets for scanning.  ''n'' is the number of address to randomly create in the given network and ''seed'' is an optional seed for the pseudo random number generator.   For example, it is possible to sample 10000 random IPv4 hosts from the Internet by specifying 'random(10000)/0.0.0.0/0' as the address.

'''split(s,e)/'''	selects a specific segment of the address range for use.  ''e'' specifies the number of segments in parallel and ''s'' is the segment number used by this particular scan.  This can be used to scan from several hosts in parallel by scanning a different segment from each host. 

'''-n''' Specifies the port numbers to scan.  Ports are separated by commas.  Each specified scanner is run for each port in this list.  The default port is 22.

Scan for SSH servers on both port 22 and 2022:
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ sudo scanssh -s ssh -n 22,2022 192.168.0.0/24
&lt;/syntaxhighlight&gt;

==ssh-audit==

'''ssh-audit''' is a python script to gather information about SSH servers.  It can identify banners used, key exchange, encryption, Message Authentication Code (MAC) algorithms, compression, compatibility settings, and several other security-related aspects.&lt;br /&gt;
https://github.com/arthepsy/ssh-audit

==sshfp==

'''sshfp''' generates SSHFP NS records using the public keys stored in a '''known_hosts''' file or provided by [http://man.openbsd.org/ssh-keyscan.1 ssh-keyscan(1)] as a means to use DNS to publish SSH key fingerprints.  That in turn allows DNSSEC lookups to verify SSH keys before use.  
SSHFP resource records in DNS are used to store fingerprint of SSH public host keys that are associated with the host names.  A record itself consists of an algorithm number, fingerprint type, and the fingerprint of the public host key.  

See RFC 4255 for details on SSHFP.

==sshfs==

'''sshfs''' builds on the Filesystem in Userspace (FUSE) interface to allow non-privileged users to create a secure, reliable file system framework.  It allows a remote file system to be mounted as a local folder by taking advantage of the SFTP subsystem.   It uses SFTP to mount a directory from a remote server as a local directory. In that way, all use applications can interact with that directory and its contents as if it were local.As the name implies, this is done in user space and not the kernel as is usually required for file systems.  FUSE has a stable API library and bindings to C, C++, and Java.  In this case it is specifically the SFTP client that is run over [http://man.openbsd.org/ssh.1 ssh(1)] and is then mounted as a file system.  

See the Cookbook section on [[OpenSSH/Cookbook/SFTP|SFTP]] for more regarding '''sshfs'''.

==sshguard==

'''sshguard''' is an intrusion prevention system.  It monitors logs to detect undesirable patterns of activities and triggers corresponding packet filter rules for increasing periods of time.  It can be used with a few other services besides SSH.  &lt;br /&gt;
http://www.sshguard.net/

==sslh==

'''sslh''' is a protocol demultiplexer.  It accepts connections on specified ports and forwards them based on the first packet sent by the client.  It can be used to share a single port between SSH, SSL, HTTP, OpenVPN, tinc, and XMPP.  &lt;br /&gt;
https://www.rutschle.net/tech/sslh/README.html

See also the section on [[OpenSSH/Cookbook/Multiplexing#Multiplexing_HTTPS_and_SSH_Using_sslh|Multiplexing]] for a discussion with examples.

==waypipe==

'''waypipe''' is a proxy to forward Wayland messages.  It serializes changes to shared memory buffers over a single socket for graphical clients and provides functionality somewhat similar to the '''-X''' option for [https://man.openbsd.org/ssh ssh(1)] but for Wayland instead of X11. &lt;br /&gt;
https://gitlab.freedesktop.org/mstoeckl/waypipe 

==Additional Third Party Utilities==

The following are useful in working with OpenSSH, but outside the scope of this book to go into detail.  They are nevertheless worth mentioning enough to warrant a list:

: '''curl''' – A multi-protocol file transfer text-based client supporting SCP and SFTP.
: '''lftp''' – A handy interactive multi-protocol file transfer text-based client supporting SFTP.
: '''nmap''' – Network exploration tool and security scanner.
: '''nc''' or '''netcat''' – Netcat, the TCP/IP swiss army knife.
: '''netstat''' – Show network connections, routing tables, interface statistics, masquerade connections, and multicast memberships
: '''nohup''' – Invoke a process that ignores HANGUP signals
: '''pagsh''' – Creates a new credential cache sandbox and process authentication group (PAG).  
: '''socat''' – SOcket CAT, a multipurpose relay similar to netcat.
: '''sudo''' – Execute programs as another user
: '''tcpdump''' – Display network traffic real time.
: '''telnet''' – Unencrypted interaction with another host.
: '''tmux''' – A terminal multiplexer.

&lt;noinclude&gt;

== References ==
{{reflist}}
{{OpenSSH/TOC|mini}}
&lt;/noinclude&gt;
{{BookCat}}
{{status|100%}}</text>
      <sha1>n9u20mcl5agpb0d4cl89655y609gsc4</sha1>
    </revision>
    <revision>
      <id>4675723</id>
      <parentid>4675721</parentid>
      <timestamp>2026-10-12T12:32:51Z</timestamp>
      <contributor>
        <username>Larsnooden</username>
        <id>430753</id>
      </contributor>
      <comment>add old URL for scanssh + capitalization</comment>
      <origin>4675723</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="8809" sha1="m065vvjbhfjvywsipu0jfgzcwtjepet" xml:space="preserve">: [https://www.harding.motd.ca/autossh/ autossh] - Automatically restart SSH sessions and tunnels 
: [http://gstm.sourceforge.net/ gstm] - a graphical front-end for managing SSH-tunneled port redirects
: [http://linux.die.net/man/1/keychain keychain] - re-use ssh-agent and/or gpg-agent between logins
: [http://linux.die.net/man/1/rsync rsync] - synchronizes files and directories using delta encoding
: [http://manpages.debian.net/cgi-bin/man.cgi?query=scanssh scanssh] - a scanner for SSH hosts and some kinds of proxies
: [https://github.com/arthepsy/ssh-audit ssh-audit] - identifies the server's banner, key exchange, encryption, MAC, compression, compatibility, and other information.
: [http://linux.die.net/man/1/sshfp sshfp] - generates SSHFP DNS records from '''known_hosts''' files or ssh-keyscan(1)
: [http://linux.die.net/man/1/sshfs sshfs] - a user-space file system client based on SFTP
: [http://www.sshguard.net/ sshguard] - an intrusion detection system with packet filtering
: [https://www.rutschle.net/tech/sslh/README.html sslh] - a protocol demultiplexer
: [https://gitlab.freedesktop.org/mstoeckl/waypipe waypipe] - proxies graphical Wayland clients for systems using Wayland instead of X11.

----

==gstm (Gnome SSH Tunnel Manager)==

'''gstm''' is a graphical front-end for managing SSH connections and especially port forwarding.&lt;br /&gt;
http://sourceforge.net/projects/gstm/

==keychain==

'''keychain''' is another manager for [http://man.openbsd.org/ssh-agent.1 ssh-agent(1)] to allow multiple shells and processes, including [http://man.openbsd.org/cron.8 cron(8)] jobs, to use the keys held by the agent.  It is often integrated into desktop-specific tools like Apple Keychain on OS X or kdewallet for KDE.  &lt;br /&gt;
http://www.funtoo.org/en/security/keychain/intro/

==rsync==

'''rsync''' is a file transfer utility to transfer files between computers very efficiently. It can run on top of SSH or use its own protocol.  SSH is the default.  &lt;br /&gt;
http://rsync.samba.org/

See the Cookbook section on [[OpenSSH/Cookbook/Automated_Backup|Automated Backup]] for examples on using '''rsync''' live or in scripts.  

==scanssh==
'''scanssh''' scans hosts and networks for running services&lt;ref name=&quot;Provos_ScanSSH&quot;&gt;{{cite web |url=http://www.citi.umich.edu/u/provos/papers/scanssh.pdf
 |title=ScanSSH - Scanning the Internet for SSH Servers|author=Niels Provos| author2=Peter Honeyman |publisher=Center for Information Technology Integration (CITI), University of Michigan|year=2001|accessdate=2016-03-05}}&lt;/ref&gt;.  It checks the version number of the server and displays the results in a list.  It detects SSH, SFTP, and several kinds of  SOCKS, HTTP, and telnet  proxies.  

https://www.monkey.org/~provos/scanssh/

Scan a small subnet for ssh servers:
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ sudo scanssh -n 22 -s ssh 192.168.100.32/26
&lt;/syntaxhighlight&gt;

Scan the same small network for SOCKS proxies:
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ sudo scanssh -s socks5,socks4 192.168.100.32/26
&lt;/syntaxhighlight&gt;
Variable scanning speeds can be set as well as random sampling.  Open proxy detection scans to detect open proxies on common ports.

Scan 1000 hosts randomly selected from 172.16.1.1 through 172.31.254.254, at a rate of 200 per second:
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ sudo scanssh -r 200 -p random(1000)/172.16.0.0/12
&lt;/syntaxhighlight&gt;

The hosts and networks to be scanned can be either specified as an IPv4 address or a CIDR-like IP prefix with IP address and network mask.  Ports can be appended by adding a colon at the end of address specification.  The sequence of hosts scanned is random, but that can be modified by the following two parameters, '''random''' and '''split''':

'''random(n[,seed])/''' selects a sample of ''n'' random addresses from the range specified as targets for scanning.  ''n'' is the number of address to randomly create in the given network and ''seed'' is an optional seed for the pseudo random number generator.   For example, it is possible to sample 10000 random IPv4 hosts from the Internet by specifying 'random(10000)/0.0.0.0/0' as the address.

'''split(s,e)/'''	selects a specific segment of the address range for use.  ''e'' specifies the number of segments in parallel and ''s'' is the segment number used by this particular scan.  This can be used to scan from several hosts in parallel by scanning a different segment from each host. 

'''-n''' Specifies the port numbers to scan.  Ports are separated by commas.  Each specified scanner is run for each port in this list.  The default port is 22.

Scan for SSH servers on both port 22 and 2022:
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ sudo scanssh -s ssh -n 22,2022 192.168.0.0/24
&lt;/syntaxhighlight&gt;

==ssh-audit==

'''ssh-audit''' is a python script to gather information about SSH servers.  It can identify banners used, key exchange, encryption, Message Authentication Code (MAC) algorithms, compression, compatibility settings, and several other security-related aspects.&lt;br /&gt;
https://github.com/arthepsy/ssh-audit

==sshfp==

'''sshfp''' generates SSHFP NS records using the public keys stored in a '''known_hosts''' file or provided by [http://man.openbsd.org/ssh-keyscan.1 ssh-keyscan(1)] as a means to use DNS to publish SSH key fingerprints.  That in turn allows DNSSEC lookups to verify SSH keys before use.  
SSHFP resource records in DNS are used to store fingerprint of SSH public host keys that are associated with the host names.  A record itself consists of an algorithm number, fingerprint type, and the fingerprint of the public host key.  

See RFC 4255 for details on SSHFP.

==sshfs==

'''sshfs''' builds on the Filesystem in Userspace (FUSE) interface to allow non-privileged users to create a secure, reliable file system framework.  It allows a remote file system to be mounted as a local folder by taking advantage of the SFTP subsystem.   It uses SFTP to mount a directory from a remote server as a local directory. In that way, all use applications can interact with that directory and its contents as if it were local.As the name implies, this is done in user space and not the kernel as is usually required for file systems.  FUSE has a stable API library and bindings to C, C++, and Java.  In this case it is specifically the SFTP client that is run over [http://man.openbsd.org/ssh.1 ssh(1)] and is then mounted as a file system.  

See the Cookbook section on [[OpenSSH/Cookbook/SFTP|SFTP]] for more regarding '''sshfs'''.

==sshguard==

'''sshguard''' is an intrusion prevention system.  It monitors logs to detect undesirable patterns of activities and triggers corresponding packet filter rules for increasing periods of time.  It can be used with a few other services besides SSH.  &lt;br /&gt;
http://www.sshguard.net/

==sslh==

'''sslh''' is a protocol demultiplexer.  It accepts connections on specified ports and forwards them based on the first packet sent by the client.  It can be used to share a single port between SSH, SSL, HTTP, OpenVPN, tinc, and XMPP.  &lt;br /&gt;
https://www.rutschle.net/tech/sslh/README.html

See also the section on [[OpenSSH/Cookbook/Multiplexing#Multiplexing_HTTPS_and_SSH_Using_sslh|Multiplexing]] for a discussion with examples.

==waypipe==

'''waypipe''' is a proxy to forward Wayland messages.  It serializes changes to shared memory buffers over a single socket for graphical clients and provides functionality somewhat similar to the '''-X''' option for [https://man.openbsd.org/ssh ssh(1)] but for Wayland instead of X11. &lt;br /&gt;
https://gitlab.freedesktop.org/mstoeckl/waypipe 

==Additional Third Party Utilities==

The following are useful in working with OpenSSH, but outside the scope of this book to go into detail.  They are nevertheless worth mentioning enough to warrant a list:

: '''curl''' – A multi-protocol file transfer text-based client supporting SCP and SFTP.
: '''lftp''' – A handy interactive multi-protocol file transfer text-based client supporting SFTP.
: '''nmap''' – Network exploration tool and security scanner.
: '''nc''' or '''netcat''' – Netcat, the TCP/IP swiss army knife.
: '''netstat''' – Show network connections, routing tables, interface statistics, masquerade connections, and multicast memberships
: '''nohup''' – Invoke a process that ignores HANGUP signals
: '''pagsh''' – Creates a new credential cache sandbox and process authentication group (PAG).  
: '''socat''' – SOcket CAT, a multipurpose relay similar to netcat.
: '''sudo''' – Execute programs as another user
: '''tcpdump''' – Display network traffic real time.
: '''telnet''' – Unencrypted interaction with another host.
: '''tmux''' – A terminal multiplexer.

&lt;noinclude&gt;

== References ==
{{reflist}}
{{OpenSSH/TOC|mini}}
&lt;/noinclude&gt;
{{BookCat}}
{{status|100%}}</text>
      <sha1>m065vvjbhfjvywsipu0jfgzcwtjepet</sha1>
    </revision>
    <revision>
      <id>4675724</id>
      <parentid>4675723</parentid>
      <timestamp>2026-10-12T12:40:39Z</timestamp>
      <contributor>
        <username>Larsnooden</username>
        <id>430753</id>
      </contributor>
      <minor />
      <comment>capitalization</comment>
      <origin>4675724</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="8809" sha1="nynuitbymaqq4lkinlon546e8dn325d" xml:space="preserve">: [https://www.harding.motd.ca/autossh/ autossh] - Automatically restart SSH sessions and tunnels 
: [http://gstm.sourceforge.net/ gstm] - a graphical front-end for managing SSH-tunneled port redirects
: [http://linux.die.net/man/1/keychain keychain] - re-use ssh-agent and/or gpg-agent between logins
: [http://linux.die.net/man/1/rsync rsync] - synchronizes files and directories using delta encoding
: [http://manpages.debian.net/cgi-bin/man.cgi?query=scanssh scanssh] - a scanner for SSH hosts and some kinds of proxies
: [https://github.com/arthepsy/ssh-audit ssh-audit] - identifies the server's banner, key exchange, encryption, MAC, compression, compatibility, and other information.
: [http://linux.die.net/man/1/sshfp sshfp] - generates SSHFP DNS records from '''known_hosts''' files or ssh-keyscan(1)
: [http://linux.die.net/man/1/sshfs sshfs] - a user-space file system client based on SFTP
: [http://www.sshguard.net/ sshguard] - an intrusion detection system with packet filtering
: [https://www.rutschle.net/tech/sslh/README.html sslh] - a protocol demultiplexer
: [https://gitlab.freedesktop.org/mstoeckl/waypipe waypipe] - proxies graphical Wayland clients for systems using Wayland instead of X11.

----

==gstm (Gnome SSH Tunnel Manager)==

'''gstm''' is a graphical front-end for managing SSH connections and especially port forwarding.&lt;br /&gt;
http://sourceforge.net/projects/gstm/

==keychain==

'''keychain''' is another manager for [http://man.openbsd.org/ssh-agent.1 ssh-agent(1)] to allow multiple shells and processes, including [http://man.openbsd.org/cron.8 cron(8)] jobs, to use the keys held by the agent.  It is often integrated into desktop-specific tools like Apple Keychain on OS X or kdewallet for KDE.  &lt;br /&gt;
http://www.funtoo.org/en/security/keychain/intro/

==rsync==

'''rsync''' is a file transfer utility to transfer files between computers very efficiently. It can run on top of SSH or use its own protocol.  SSH is the default.  &lt;br /&gt;
http://rsync.samba.org/

See the Cookbook section on [[OpenSSH/Cookbook/Automated_Backup|Automated Backup]] for examples on using '''rsync''' live or in scripts.  

==scanssh==
'''scanssh''' scans hosts and networks for running services&lt;ref name=&quot;Provos_ScanSSH&quot;&gt;{{cite web |url=http://www.citi.umich.edu/u/provos/papers/scanssh.pdf
 |title=ScanSSH - Scanning the Internet for SSH Servers|author=Niels Provos| author2=Peter Honeyman |publisher=Center for Information Technology Integration (CITI), University of Michigan|year=2001|accessdate=2016-03-05}}&lt;/ref&gt;.  It checks the version number of the server and displays the results in a list.  It detects SSH, SFTP, and several kinds of  SOCKS, HTTP, and telnet  proxies.  

https://www.monkey.org/~provos/scanssh/

Scan a small subnet for SSH servers:
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ sudo scanssh -n 22 -s ssh 192.168.100.32/26
&lt;/syntaxhighlight&gt;

Scan the same small network for SOCKS proxies:
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ sudo scanssh -s socks5,socks4 192.168.100.32/26
&lt;/syntaxhighlight&gt;
Variable scanning speeds can be set as well as random sampling.  Open proxy detection scans to detect open proxies on common ports.

Scan 1000 hosts randomly selected from 172.16.1.1 through 172.31.254.254, at a rate of 200 per second:
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ sudo scanssh -r 200 -p random(1000)/172.16.0.0/12
&lt;/syntaxhighlight&gt;

The hosts and networks to be scanned can be either specified as an IPv4 address or a CIDR-like IP prefix with IP address and network mask.  Ports can be appended by adding a colon at the end of address specification.  The sequence of hosts scanned is random, but that can be modified by the following two parameters, '''random''' and '''split''':

'''random(n[,seed])/''' selects a sample of ''n'' random addresses from the range specified as targets for scanning.  ''n'' is the number of address to randomly create in the given network and ''seed'' is an optional seed for the pseudo random number generator.   For example, it is possible to sample 10000 random IPv4 hosts from the Internet by specifying 'random(10000)/0.0.0.0/0' as the address.

'''split(s,e)/'''	selects a specific segment of the address range for use.  ''e'' specifies the number of segments in parallel and ''s'' is the segment number used by this particular scan.  This can be used to scan from several hosts in parallel by scanning a different segment from each host. 

'''-n''' Specifies the port numbers to scan.  Ports are separated by commas.  Each specified scanner is run for each port in this list.  The default port is 22.

Scan for SSH servers on both port 22 and 2022:
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ sudo scanssh -s ssh -n 22,2022 192.168.0.0/24
&lt;/syntaxhighlight&gt;

==ssh-audit==

'''ssh-audit''' is a python script to gather information about SSH servers.  It can identify banners used, key exchange, encryption, Message Authentication Code (MAC) algorithms, compression, compatibility settings, and several other security-related aspects.&lt;br /&gt;
https://github.com/arthepsy/ssh-audit

==sshfp==

'''sshfp''' generates SSHFP NS records using the public keys stored in a '''known_hosts''' file or provided by [http://man.openbsd.org/ssh-keyscan.1 ssh-keyscan(1)] as a means to use DNS to publish SSH key fingerprints.  That in turn allows DNSSEC lookups to verify SSH keys before use.  
SSHFP resource records in DNS are used to store fingerprint of SSH public host keys that are associated with the host names.  A record itself consists of an algorithm number, fingerprint type, and the fingerprint of the public host key.  

See RFC 4255 for details on SSHFP.

==sshfs==

'''sshfs''' builds on the Filesystem in Userspace (FUSE) interface to allow non-privileged users to create a secure, reliable file system framework.  It allows a remote file system to be mounted as a local folder by taking advantage of the SFTP subsystem.   It uses SFTP to mount a directory from a remote server as a local directory. In that way, all use applications can interact with that directory and its contents as if it were local.As the name implies, this is done in user space and not the kernel as is usually required for file systems.  FUSE has a stable API library and bindings to C, C++, and Java.  In this case it is specifically the SFTP client that is run over [http://man.openbsd.org/ssh.1 ssh(1)] and is then mounted as a file system.  

See the Cookbook section on [[OpenSSH/Cookbook/SFTP|SFTP]] for more regarding '''sshfs'''.

==sshguard==

'''sshguard''' is an intrusion prevention system.  It monitors logs to detect undesirable patterns of activities and triggers corresponding packet filter rules for increasing periods of time.  It can be used with a few other services besides SSH.  &lt;br /&gt;
http://www.sshguard.net/

==sslh==

'''sslh''' is a protocol demultiplexer.  It accepts connections on specified ports and forwards them based on the first packet sent by the client.  It can be used to share a single port between SSH, SSL, HTTP, OpenVPN, tinc, and XMPP.  &lt;br /&gt;
https://www.rutschle.net/tech/sslh/README.html

See also the section on [[OpenSSH/Cookbook/Multiplexing#Multiplexing_HTTPS_and_SSH_Using_sslh|Multiplexing]] for a discussion with examples.

==waypipe==

'''waypipe''' is a proxy to forward Wayland messages.  It serializes changes to shared memory buffers over a single socket for graphical clients and provides functionality somewhat similar to the '''-X''' option for [https://man.openbsd.org/ssh ssh(1)] but for Wayland instead of X11. &lt;br /&gt;
https://gitlab.freedesktop.org/mstoeckl/waypipe 

==Additional Third Party Utilities==

The following are useful in working with OpenSSH, but outside the scope of this book to go into detail.  They are nevertheless worth mentioning enough to warrant a list:

: '''curl''' – A multi-protocol file transfer text-based client supporting SCP and SFTP.
: '''lftp''' – A handy interactive multi-protocol file transfer text-based client supporting SFTP.
: '''nmap''' – Network exploration tool and security scanner.
: '''nc''' or '''netcat''' – Netcat, the TCP/IP swiss army knife.
: '''netstat''' – Show network connections, routing tables, interface statistics, masquerade connections, and multicast memberships
: '''nohup''' – Invoke a process that ignores HANGUP signals
: '''pagsh''' – Creates a new credential cache sandbox and process authentication group (PAG).  
: '''socat''' – SOcket CAT, a multipurpose relay similar to netcat.
: '''sudo''' – Execute programs as another user
: '''tcpdump''' – Display network traffic real time.
: '''telnet''' – Unencrypted interaction with another host.
: '''tmux''' – A terminal multiplexer.

&lt;noinclude&gt;

== References ==
{{reflist}}
{{OpenSSH/TOC|mini}}
&lt;/noinclude&gt;
{{BookCat}}
{{status|100%}}</text>
      <sha1>nynuitbymaqq4lkinlon546e8dn325d</sha1>
    </revision>
    <revision>
      <id>4675725</id>
      <parentid>4675724</parentid>
      <timestamp>2026-10-12T12:41:25Z</timestamp>
      <contributor>
        <username>Larsnooden</username>
        <id>430753</id>
      </contributor>
      <minor />
      <comment>italicization of IP range</comment>
      <origin>4675725</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="8817" sha1="47xwkhxe8q7zqef4g8s6rq6rtq6sn92" xml:space="preserve">: [https://www.harding.motd.ca/autossh/ autossh] - Automatically restart SSH sessions and tunnels 
: [http://gstm.sourceforge.net/ gstm] - a graphical front-end for managing SSH-tunneled port redirects
: [http://linux.die.net/man/1/keychain keychain] - re-use ssh-agent and/or gpg-agent between logins
: [http://linux.die.net/man/1/rsync rsync] - synchronizes files and directories using delta encoding
: [http://manpages.debian.net/cgi-bin/man.cgi?query=scanssh scanssh] - a scanner for SSH hosts and some kinds of proxies
: [https://github.com/arthepsy/ssh-audit ssh-audit] - identifies the server's banner, key exchange, encryption, MAC, compression, compatibility, and other information.
: [http://linux.die.net/man/1/sshfp sshfp] - generates SSHFP DNS records from '''known_hosts''' files or ssh-keyscan(1)
: [http://linux.die.net/man/1/sshfs sshfs] - a user-space file system client based on SFTP
: [http://www.sshguard.net/ sshguard] - an intrusion detection system with packet filtering
: [https://www.rutschle.net/tech/sslh/README.html sslh] - a protocol demultiplexer
: [https://gitlab.freedesktop.org/mstoeckl/waypipe waypipe] - proxies graphical Wayland clients for systems using Wayland instead of X11.

----

==gstm (Gnome SSH Tunnel Manager)==

'''gstm''' is a graphical front-end for managing SSH connections and especially port forwarding.&lt;br /&gt;
http://sourceforge.net/projects/gstm/

==keychain==

'''keychain''' is another manager for [http://man.openbsd.org/ssh-agent.1 ssh-agent(1)] to allow multiple shells and processes, including [http://man.openbsd.org/cron.8 cron(8)] jobs, to use the keys held by the agent.  It is often integrated into desktop-specific tools like Apple Keychain on OS X or kdewallet for KDE.  &lt;br /&gt;
http://www.funtoo.org/en/security/keychain/intro/

==rsync==

'''rsync''' is a file transfer utility to transfer files between computers very efficiently. It can run on top of SSH or use its own protocol.  SSH is the default.  &lt;br /&gt;
http://rsync.samba.org/

See the Cookbook section on [[OpenSSH/Cookbook/Automated_Backup|Automated Backup]] for examples on using '''rsync''' live or in scripts.  

==scanssh==
'''scanssh''' scans hosts and networks for running services&lt;ref name=&quot;Provos_ScanSSH&quot;&gt;{{cite web |url=http://www.citi.umich.edu/u/provos/papers/scanssh.pdf
 |title=ScanSSH - Scanning the Internet for SSH Servers|author=Niels Provos| author2=Peter Honeyman |publisher=Center for Information Technology Integration (CITI), University of Michigan|year=2001|accessdate=2016-03-05}}&lt;/ref&gt;.  It checks the version number of the server and displays the results in a list.  It detects SSH, SFTP, and several kinds of  SOCKS, HTTP, and telnet  proxies.  

https://www.monkey.org/~provos/scanssh/

Scan a small subnet for SSH servers:
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ sudo scanssh -n 22 -s ssh 192.168.100.32/26
&lt;/syntaxhighlight&gt;

Scan the same small network for SOCKS proxies:
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ sudo scanssh -s socks5,socks4 192.168.100.32/26
&lt;/syntaxhighlight&gt;
Variable scanning speeds can be set as well as random sampling.  Open proxy detection scans to detect open proxies on common ports.

Scan 1000 hosts randomly selected from ''172.16.1.1'' through ''172.31.254.254'', at a rate of 200 per second:
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ sudo scanssh -r 200 -p random(1000)/172.16.0.0/12
&lt;/syntaxhighlight&gt;

The hosts and networks to be scanned can be either specified as an IPv4 address or a CIDR-like IP prefix with IP address and network mask.  Ports can be appended by adding a colon at the end of address specification.  The sequence of hosts scanned is random, but that can be modified by the following two parameters, '''random''' and '''split''':

'''random(n[,seed])/''' selects a sample of ''n'' random addresses from the range specified as targets for scanning.  ''n'' is the number of address to randomly create in the given network and ''seed'' is an optional seed for the pseudo random number generator.   For example, it is possible to sample 10000 random IPv4 hosts from the Internet by specifying 'random(10000)/0.0.0.0/0' as the address.

'''split(s,e)/'''	selects a specific segment of the address range for use.  ''e'' specifies the number of segments in parallel and ''s'' is the segment number used by this particular scan.  This can be used to scan from several hosts in parallel by scanning a different segment from each host. 

'''-n''' Specifies the port numbers to scan.  Ports are separated by commas.  Each specified scanner is run for each port in this list.  The default port is 22.

Scan for SSH servers on both port 22 and 2022:
&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ sudo scanssh -s ssh -n 22,2022 192.168.0.0/24
&lt;/syntaxhighlight&gt;

==ssh-audit==

'''ssh-audit''' is a python script to gather information about SSH servers.  It can identify banners used, key exchange, encryption, Message Authentication Code (MAC) algorithms, compression, compatibility settings, and several other security-related aspects.&lt;br /&gt;
https://github.com/arthepsy/ssh-audit

==sshfp==

'''sshfp''' generates SSHFP NS records using the public keys stored in a '''known_hosts''' file or provided by [http://man.openbsd.org/ssh-keyscan.1 ssh-keyscan(1)] as a means to use DNS to publish SSH key fingerprints.  That in turn allows DNSSEC lookups to verify SSH keys before use.  
SSHFP resource records in DNS are used to store fingerprint of SSH public host keys that are associated with the host names.  A record itself consists of an algorithm number, fingerprint type, and the fingerprint of the public host key.  

See RFC 4255 for details on SSHFP.

==sshfs==

'''sshfs''' builds on the Filesystem in Userspace (FUSE) interface to allow non-privileged users to create a secure, reliable file system framework.  It allows a remote file system to be mounted as a local folder by taking advantage of the SFTP subsystem.   It uses SFTP to mount a directory from a remote server as a local directory. In that way, all use applications can interact with that directory and its contents as if it were local.As the name implies, this is done in user space and not the kernel as is usually required for file systems.  FUSE has a stable API library and bindings to C, C++, and Java.  In this case it is specifically the SFTP client that is run over [http://man.openbsd.org/ssh.1 ssh(1)] and is then mounted as a file system.  

See the Cookbook section on [[OpenSSH/Cookbook/SFTP|SFTP]] for more regarding '''sshfs'''.

==sshguard==

'''sshguard''' is an intrusion prevention system.  It monitors logs to detect undesirable patterns of activities and triggers corresponding packet filter rules for increasing periods of time.  It can be used with a few other services besides SSH.  &lt;br /&gt;
http://www.sshguard.net/

==sslh==

'''sslh''' is a protocol demultiplexer.  It accepts connections on specified ports and forwards them based on the first packet sent by the client.  It can be used to share a single port between SSH, SSL, HTTP, OpenVPN, tinc, and XMPP.  &lt;br /&gt;
https://www.rutschle.net/tech/sslh/README.html

See also the section on [[OpenSSH/Cookbook/Multiplexing#Multiplexing_HTTPS_and_SSH_Using_sslh|Multiplexing]] for a discussion with examples.

==waypipe==

'''waypipe''' is a proxy to forward Wayland messages.  It serializes changes to shared memory buffers over a single socket for graphical clients and provides functionality somewhat similar to the '''-X''' option for [https://man.openbsd.org/ssh ssh(1)] but for Wayland instead of X11. &lt;br /&gt;
https://gitlab.freedesktop.org/mstoeckl/waypipe 

==Additional Third Party Utilities==

The following are useful in working with OpenSSH, but outside the scope of this book to go into detail.  They are nevertheless worth mentioning enough to warrant a list:

: '''curl''' – A multi-protocol file transfer text-based client supporting SCP and SFTP.
: '''lftp''' – A handy interactive multi-protocol file transfer text-based client supporting SFTP.
: '''nmap''' – Network exploration tool and security scanner.
: '''nc''' or '''netcat''' – Netcat, the TCP/IP swiss army knife.
: '''netstat''' – Show network connections, routing tables, interface statistics, masquerade connections, and multicast memberships
: '''nohup''' – Invoke a process that ignores HANGUP signals
: '''pagsh''' – Creates a new credential cache sandbox and process authentication group (PAG).  
: '''socat''' – SOcket CAT, a multipurpose relay similar to netcat.
: '''sudo''' – Execute programs as another user
: '''tcpdump''' – Display network traffic real time.
: '''telnet''' – Unencrypted interaction with another host.
: '''tmux''' – A terminal multiplexer.

&lt;noinclude&gt;

== References ==
{{reflist}}
{{OpenSSH/TOC|mini}}
&lt;/noinclude&gt;
{{BookCat}}
{{status|100%}}</text>
      <sha1>47xwkhxe8q7zqef4g8s6rq6rtq6sn92</sha1>
    </revision>
  </page>
  <page>
    <title>OpenSSH/Cookbook/Multiplexing</title>
    <ns>0</ns>
    <id>248568</id>
    <revision>
      <id>4675809</id>
      <parentid>4629164</parentid>
      <timestamp>2026-10-13T09:19:18Z</timestamp>
      <contributor>
        <username>Larsnooden</username>
        <id>430753</id>
      </contributor>
      <comment>-O check plus two minor tweaks</comment>
      <origin>4675809</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="28692" sha1="esarc4obpi93bore3fjmfw9hj2ak7b4" xml:space="preserve">&lt;noinclude&gt;{{simple chapter navigation|previous=Load Balancing|next=Proxies and Jump Hosts}}&lt;/noinclude&gt;
&amp;nbsp;

Multiplexing is the ability to send more than one signal over a single line or connection.  In OpenSSH, multiplexing can re-use an existing outgoing TCP connection for multiple concurrent SSH sessions to a remote SSH server, avoiding the overhead of creating a new TCP connection and reauthenticating each time.  

&lt;noinclude&gt;__TOC__&lt;/noinclude&gt; 

==Advantages of Multiplexing==

An advantage of SSH multiplexing is that the overhead of creating new TCP connections and negotiating the secure connection is eliminated.  The overall number of connections that a machine may accept is a finite resource and the limit is more noticeable on some machines than on others and varies greatly depending on both load and usage.  There is also a significant delay when opening a new connection.  Activities that repeatedly open new connections can be significantly sped up using multiplexing.

The difference between multiplexing and standalone sessions can be seen by comparing the tables below.  Both are selected output from &lt;code&gt;netstat -nt&lt;/code&gt; slightly edited for clarity.  We see in Table 1, &quot;SSH Connections, Separate&quot;, that without multiplexing each new login creates a new TCP connection, one per login session.  Following that we see in the other table, Table 2, &quot;SSH Connections, Multiplexed&quot;, that when multiplexing is used, new logins are channelled over the already established TCP connection.    

&lt;syntaxhighlight lang=&quot;text&quot;&gt;
#              Local Address       Foreign Address         State

# one connection
tcp    0   0   192.168.x.y:45050   192.168.x.z:22       ESTABLISHED

# two separate connections
tcp    0   0   192.168.x.y:45050   192.168.x.z:22       ESTABLISHED
tcp    0   0   192.168.x.y:45051   192.168.x.z:22       ESTABLISHED

# three separate connections
tcp    0   0   192.168.x.y:45050   192.168.x.z:22       ESTABLISHED
tcp    0   0   192.168.x.y:45051   192.168.x.z:22       ESTABLISHED
tcp    0   0   192.168.x.y:45052   192.168.x.z:22       ESTABLISHED

Table 1: SSH Connections, Separate
&lt;/syntaxhighlight&gt;

Both tables show TCP/IP connections associated with SSH sessions.  The table above shows a new TCP/IP connection for each new SSH connection.  The table below shows a single TCP/IP connection despite multiple active SSH sessions.  

&lt;syntaxhighlight lang=&quot;text&quot;&gt;
#              Local Address       Foreign Address         State

# one connection
tcp    0   0   192.168.x.y:58913   192.168.x.z:22       ESTABLISHED

# two multiplexed connections
tcp    0   0   192.168.x.y:58913   192.168.x.z:22       ESTABLISHED

# three multiplexed connections
tcp    0   0   192.168.x.y:58913   192.168.x.z:22       ESTABLISHED

Table 2: SSH Connections, Multiplexed
&lt;/syntaxhighlight&gt;

As we can see with multiplexing, only a single TCP connection is set up and used regardless of whether or not there are multiple SSH sessions carried over it.

Or we can compare the time it takes to run [http://man.openbsd.org/true.1 true(1)] on a slow remote server, using [http://linux.die.net/man/1/time  time(1)].  The two commands would be something like &lt;code&gt;time ssh server.example.org true&lt;/code&gt; versus &lt;code&gt;time ssh -S ./path/to/somesocket server.example.org true&lt;/code&gt; and use keys with an agent for each of them.  First without multiplexing, we see the normal connection time:

&lt;syntaxhighlight lang=&quot;text&quot;&gt;
real    0m0.658s
user    0m0.016s
sys     0m0.008s
&lt;/syntaxhighlight&gt;

Then we do the same thing again, but with a multiplexed connection to see a faster result:

&lt;syntaxhighlight lang=&quot;text&quot;&gt;
real    0m0.029s
user    0m0.004s
sys     0m0.004s
&lt;/syntaxhighlight&gt;

The difference is quite large and will definitely add up for any activity where connections are made repeatedly in rapid succession.  The speed gain for multiplexed connections doesn't come with the master connection, that is normal speed, but with the second and subsequent multiplexed connections.  The overhead for a new SSH connection remains, but the overhead of a new TCP connection is avoided.  The second and later connections will reuse the established TCP connection over and over and not need to create a new TCP connection for each new SSH connection.

==Setting Up Multiplexing==

The OpenSSH client supports multiplexing its outgoing connections, since version 3.9 (August 18, 2004)&lt;ref name=&quot;multiplexing&quot;&gt;{{cite web |url=https://www.openssh.org/txt/release-3.9 |title=OpenSSH 3.9 Release Notes |accessdate=2018-12-16 |date=2004-08-18 |publisher=OpenSSH }}&lt;/ref&gt;, using the '''ControlMaster''', '''ControlPath''' and '''ControlPersist''' configuration directives which get defined in [http://man.openbsd.org/ssh_config.5 ssh_config(5)].  The client configuration file usually defaults to the location '''~/.ssh/config'''.  All three directives are described in the manual page for [http://man.openbsd.org/ssh_config.5 ssh_config(5)].   See also the &quot;TOKENS&quot; section there for the list of tokens available for use in the '''ControlPath'''.  Any valid tokens used are expanded at run time.  

'''ControlMaster''' determines whether [http://man.openbsd.org/ssh.1 ssh(1)] will listen for control connections and what to do about them.  '''ControlPath''' sets the location for the control socket used by the multiplexed sessions.  These can be either globally or locally in [http://man.openbsd.org/ssh_config.5 ssh_config(5)] or else specified at run time.  Control sockets are removed automatically when the master connection has ended.  '''ControlPersist''' can be used in conjunction with '''ControlMaster'''.  If '''ControlPersist''' is set to 'yes', then it will leave the master connection open in the background to accept new connections until either killed explicitly or closed with '''-O''' or ends at a pre-defined timeout.  If '''ControlPersist''' is set to a time, then it will leave the master connection open for the designated time or until the last multiplexed session is closed, whichever is longer.  

Here is a sample excerpt from [http://man.openbsd.org/ssh_config.5 ssh_config(5)] applicable for starting a multiplexed session to ''machine1.example.org'' via the shortcut ''machine1''.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Host machine1
        HostName machine1.example.org
        ControlPath ~/.ssh/controlmasters/%r@%h:%p
        ControlMaster auto
        ControlPersist 10m
&lt;/syntaxhighlight&gt;

With that configuration, the first connection to ''machine1'' will create a control socket in the directory '''~/.ssh/controlmasters/''' and then any subsequent connections, up to 10 by default as set by '''MaxSessions''' on the SSH server, will re-use that control path automatically as multiplexed sessions.   Confirmation of each new connection can be required if '''ControlMaster''' set to 'autoask' instead of 'auto'.  

Please note with the settings above that the control socket would be placed into the folder '''~/.ssh/controlmasters/'''.  If that folder doesn't exist first, the SSH client will exit with a specific error about unix_listener complaining that the file or path does not exist:

&lt;syntaxhighlight lang=&quot;text&quot;&gt;
unix_listener: cannot bind to path /home/fred/.ssh/controlmasters/fred@machine1.example.org:22.EOWsvm5xFt30O6CB: No such file or directory
&lt;/syntaxhighlight&gt;

With the '''-O''' option, [http://man.openbsd.org/ssh.1 ssh(1)] can be used to manage the connection using the same shortcut configuration.  Use 'check' to see the status of the connections.  To cancel all existing connections, including the master connection, use 'exit' instead of 'stop'.   

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -O check machine1
Master running (pid=14379)
$ ssh -O stop machine1
Stop listening request sent
$ ssh -O check machine1
Control socket connect(/Users/Username/.ssh/sockets/machine1): No such file or directory
&lt;/syntaxhighlight&gt;

In that example, the status of the connection is checked first.  Then the master connection is told not to accept further multiplexing requests and finally we check again and verify that the control socket is not available any more.

It is also possible to show information about the connection.  Note that the ''machine1'' shortcut was defined above and sets the path to the '''ControlPath''' socket.  The option '''-O conninfo''' corresponds to the '''~I''' escape function.  The connections are being made from ''client.example.org'' at the address ''192.0.2.98'' to the system at the address ''203.0.113.206'' named ''machine1.example.org''.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -O conninfo machine1
Connection information for client.example.org pid 83539
  tcp 192.0.2.98:18952 -&gt; 203.0.113.206:22
  kexalgorithm mlkem768x25519-sha256
  hostkeyalgorithm ssh-ed25519
  cipher chacha20-poly1305@openssh.com
  mac &lt;implicit&gt;
  compression none
  rekey limit none interval none
  traffic 112 pkts 466 blks 6.4KB in, 94 pkts 329 blks 5.8KB out
&lt;/syntaxhighlight&gt;

Similarly, the  '''-O channels''' option displays which channels are open in that multiplexing session.  However, it has no corresponding escape sequence.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -O channels machine1
The following connections are open:
  #1 mux-control (t16 [mux-control] nr0 m0 i0/0 o0/0 e[closed]/0 fd 5/5/-1 sock 5 cc -1 c2 io 0x01/0x00 I)
  #2 client-session (t4 [session] r0 nm0 i0/0 o0/0 e[write]/0 fd 6/7/8 sock -1 cc 1 nc0 io 0x01/0x00 RTI)
  #3 mux-control (t16 [mux-control] nr0 m0 i0/0 o0/0 e[closed]/0 fd 9/9/-1 sock 9 cc -1 c4 io 0x01/0x00 I)
  #4 client-session (t4 [session] r1 nm0 i0/0 o0/0 e[write]/0 fd 10/11/12 sock -1 cc 3 nc0 io 0x01/0x00 RTI)
  #5 mux-control (t16 [mux-control] nr0 m0 i0/0 o0/0 e[closed]/0 fd 13/13/-1 sock 13 cc -1 nc0 io 0x01/0x01 I)
&lt;/syntaxhighlight&gt;

That example shows two SSH connections over the same network connection: one master connection plus one child.  

====Manually Establishing Multiplexed Connections====

Multiplexed sessions need a control master to connect to.  The run time parameters '''-M''' and '''-S''' also correspond to '''ControlMaster''' and '''ControlPath''', respectively.   So first an initial master connection is established using '''-M''' when accompanied by the path to the control socket using '''-S'''.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -M -S /home/fred/.ssh/controlmasters/fred@server.example.org:22 server.example.org
&lt;/syntaxhighlight&gt;

Then subsequent multiplexed connections are made in other terminals.  They use '''ControlPath''' or '''-S''' to point to the control socket.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -S /home/fred/.ssh/controlmasters/fred@server.example.org:22 server.example.org
&lt;/syntaxhighlight&gt;

Note that the control socket is named &quot;fred@server.example.org:22&quot;, or ''%r@%h:%p'', to try to make the name unique.  The combination %r,  %h and %p stand for the remote user name, the remote host and the remote host's port.  The control sockets should be given unique names.  

Multiple '''-M''' options place [http://man.openbsd.org/ssh.1 ssh(1)] into '''master''' mode with confirmation required before slave connections are accepted.  This is the same as '''ControlMaster=ask'''.  Both require X to ask for the confirmation.  

Here is the master connection for the host ''server.example.org'' as set to ask for confirmation of new multiplexed sessions:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -MM -S ~/.ssh/controlmasters/%r@%h:%p server.example.org
&lt;/syntaxhighlight&gt;

And here is a subsequent multiplexed connection:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -S ~/.ssh/controlmasters/%r@%h:%p server.example.org
&lt;/syntaxhighlight&gt;

The status of the control master connection can be queried using '''-O check''', which will tell if it is running or not.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -O check -S ~/.ssh/controlmasters/%r@%h:%p server.example.org
&lt;/syntaxhighlight&gt;

If the control session has been stopped, the query will return an error about &quot;No such file or directory&quot; even if there are still multiplexed sessions running because the socket is gone.  

Alternately, instead of specifying '''-M''' and '''-S''' as runtime options,  configuration options can be spelled out in full using '''-o''' for easier transfer to the client configuration file when figured out.   

The way below sets configuration options as run time parameters by first starting a control master.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -o &quot;ControlMaster=yes&quot; -o &quot;ControlPath=/home/fred/.ssh/controlmasters/%r@%h:%p&quot; server.example.org
&lt;/syntaxhighlight&gt;

Then subsequent sessions are connected to the control master via socket at the end of the control path.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -o &quot;ControlPath=/home/fred/.ssh/controlmasters/%r@%h:%p&quot;  server.example.org
&lt;/syntaxhighlight&gt;

And of course all that can be put into [http://man.openbsd.org/ssh_config.5 ssh_config(5)] as shown in the previous section.  Starting with 6.7, the combination of %r@%h:%p and variations on it can be replaced with %C which by itself generates a SHA1 hash from the concatenation of %l%h%p%r.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -S ~/.ssh/controlmasters/%C server.example.org
&lt;/syntaxhighlight&gt;

There are two advantages with that.  One is that the hash can be shorter than its combined elements while still uniquely identifying the connection.  The other is that it obfuscates the connection information which would have been otherwise displayed in the socket's name.

===Ending Multiplexed Connections===

One way to end multiplexed sessions is to exit all related SSH sessions, including the control master.  If the control master has been placed in the background using '''ControlPersist''', then it will be necessary to stop it with '''-O''' and either 'stop' or 'exit'.  That also requires knowing the full path to and filename of the control socket as used in the creation of the master session, if it has not been defined in a shortcut in [http://man.openbsd.org/ssh_config.5 ssh_config(5)].

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -O stop server1
$ ssh -O stop -S ~/.ssh/controlmasters/%C server1.example.org
&lt;/syntaxhighlight&gt;

The multiplex command '''-O stop''' will gracefully shutdown multiplexing.  After issuing the command, the control socket is removed and no new multiplexed sessions are accepted for that master.  Existing connections are allowed to continue and the master connection will persist until the last multiplexed connection closes.  

In contrast, the multiplex command '''-O exit''' removes the control socket and immediately terminates all existing connections.  

Again, the directive '''ControlPersist''' can also be set to timeout after a set period of disuse.  The time interval there is written in a time format listed in [http://man.openbsd.org/sshd_config.5 sshd_config(5)] or else defaults to seconds if no units are given.   It will cause the master connection to automatically close if it has no client connections for the specified time.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Host server1
        HostName server1.example.org
        ControlPath ~/.ssh/controlmasters/%C
        ControlMaster yes
        ControlPersist 2h
&lt;/syntaxhighlight&gt;

The above example lets the control master timeout after 2 hours of inactivity.  Care should be used with persistent control sockets.   A user that can read and write to a control socket can establish new connections without further authentication.

===Multiplexing Options===

The values for configuring session multiplexing can be set either in the user-specific [http://man.openbsd.org/ssh_config.5 ssh_config(5)], or the global '''/etc/ssh/ssh_config''', or using parameters when running from the shell or a script.   '''ControlMaster''' can be overridden in the run time arguments to re-use an existing master when '''ControlMaster''' is set to 'yes', by setting it explicitly to 'no':

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -o &quot;ControlMaster=no&quot; server.example.org
&lt;/syntaxhighlight&gt;

'''ControlMaster''' accepts five different values: 'no', 'yes', 'ask', 'auto', and 'autoask'.   

* 'no' is the default.  New sessions will not try to connect to an established master session, but additional sessions can still multiplex by connecting explicitly to an existing socket.
* 'yes' creates a new master session each time, unless explicitly overridden.  The new master session will listen for connections.   
* 'ask'  creates a new master each time, unless overridden, which listen for connections.  If overridden,  [http://man.openbsd.org/ssh-askpass.1 ssh-askpass(1)] will popup an message in X to ask the master session owner to approve or deny the request.  If the request is denied, then the session being created falls back to being a regular, standalone session.    
* 'auto' creates a master session automatically but if there is a master session already available, subsequent sessions are automatically multiplexed.
* 'autoask' automatically assumes that if a master session exists, that subsequent sessions should be multiplexed, but ask first before adding a session.   

Refused connections are logged to the master session.

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Host * 
        ControlMaster ask 
&lt;/syntaxhighlight&gt;

'''ControlPath'''  can be a fixed string or include any of several pre-defined variables described in the TOKENS section of the [http://man.openbsd.org/ssh_config.5#TOKENS ssh_config(5)].  '''%L''' is for the first component of the local host name and '''%l''' for the full local host name.  '''%h''' is the target host name and '''%n''' is the original target host name and '''%p''' is for the destination port on the remote server.  '''%r''' is for the remote user name and '''%u''' for the user running [http://man.openbsd.org/ssh.1 ssh(1)].  Or they can be combined as '''%C''' which is a SHA1 hash produced from '''%l%h%p%r'''.

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Host * 
        ControlMaster ask 
        ControlPath ~/.ssh/controlmasters/%C
&lt;/syntaxhighlight&gt;

'''ControlPersist''' accepts 'yes', 'no' or a time interval.  If a time interval is given, the default is in seconds.  Units can extend the time to minutes, hours, days, weeks or  a combination.  If 'yes' the master connection stays in the background indefinitely. 

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Host * 
        ControlMaster ask 
        ControlPath ~/.ssh/controlmasters/%C
        ControlPersist 10m
&lt;/syntaxhighlight&gt;

====Port Forwarding After the Fact====

It is possible to request port forwarding without having to establish new connections.  Here we forward port 8080 on the local host to port 80 on the remote host using '''-L''':

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -O forward -L 8080:localhost:80 -S ~/.ssh/controlmasters/fred@server.example.org:22  server.example.org
&lt;/syntaxhighlight&gt;

The same can be done for remote forwarding, using '''-R'''.  The escape sequence '''~C''' is not available for multiplexed sessions, so '''-O forward''' is the only way to add port forwarding on the fly.  

Port forwarding can be canceled without having to close any sessions using '''-O cancel'''.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -O cancel -L 8080:localhost:80 -S ~/.ssh/controlmasters/fred@server.example.org:22  server.example.org
&lt;/syntaxhighlight&gt;

The exact same syntax used for forwarding is used for cancelling.  However, there is no way currently to look up which ports are being forwarded and how they are forwarded.

==Additional Notes About Multiplexing==

Never use any publicly accessible directory for the control path sockets.  Place those sockets in a directory somewhere else, one to which only your account has access.  For example '''~/.ssh/socket/''' would be a much safer choice and '''/tmp/''' would be a bad choice. 

In cases where it is useful to have a standing connection, it is always possible to combine multiplexing with other options, such as '''-f''' or '''-N''' to have the control master drop to the background upon connection and not load a shell.  

In [http://man.openbsd.org/sshd_config.5 sshd_config(5)], the directive '''MaxSessions''' specifies the maximum number of open sessions permitted per network connection.  This is used when multiplexing ssh sessions over a single TCP connection.  Setting '''MaxSessions''' to 1 disables multiplexing and setting it to 0 disables login/shell/subsystem sessions completely.  The default is 10.  The '''MaxSessions''' directive can also be set under a '''Match''' conditional block so that different settings are available for different conditions.

===Errors Preventing Multiplexing===

The directory used for holding the control sockets must be on a file system that actually allows the creation of sockets.   AFS is one example that doesn't, as are some implementations of HFS+.  If an attempt is made at creating a socket on a file system that does not allow it, an error something like the following will occur:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -M -S /home/fred/.ssh/mux 192.0.2.57
muxserver_listen: link mux listener /home/fred/.ssh/mux.vjfeIFFzHnhgHoOV =&gt; /home/fred/.ssh/mux: Operation not permitted
&lt;/syntaxhighlight&gt;

A similar issue was seen when trying to make Unix domain sockets on OverlayFS filesystems, which are often used with Docker, prior to Linux 4.7 kernel&lt;ref name=&quot;docker-overlayfs-bug&quot;&gt;{{cite mailing list |url=https://lkml.org/lkml/2016/6/16/87 |title=[GIT PULL] overlayfs fixes for 4.7-rc3 |date=2016-06-16 |accessdate=2018-10-05 |mailing-list=LKML |last=Szeredi |first=Miklos |author=Miklos Szeredi}}&lt;/ref&gt;.

If the file system cannot be reconfigured to allow sockets, then the only other option is to place the control path socket somewhere else on a file system that does support creation of sockets.

===Observing Multiplexing===

It is possible to make some rough measurements to show the differences between multiplexed connections and one-off connections as shown in the tables and figures above.  

====Measuring the Number of TCP Connections====

Tables 1 and 2 above use output from [http://linux.die.net/man/8/netstat netstat(8)] and [http://linux.die.net/man/1/awk awk(1)] to show the number of TCP connections corresponding to the number of SSH connections.

{|
|
&lt;syntaxhighlight lang=&quot;bash&quot;&gt;
#!/bin/sh
netstat -nt | awk 'NR == 2'

ssh -f server.example.org sleep 60
echo # one connection
netstat -nt | awk '$5 ~ /:22$/'

ssh -f server.example.org sleep 60
echo # two connections
netstat -nt | awk '$5 ~ /:22$/'

ssh -f server.example.org sleep 60
echo # three connections
netstat -nt | awk '$5 ~ /:22$/'

echo Table 1
&lt;/syntaxhighlight&gt;
|
And
|
&lt;syntaxhighlight lang=&quot;bash&quot;&gt;
#!/bin/sh
netstat -nt | awk 'NR == 2'

ssh -f -M -S ~/.ssh/demo server.example.org sleep 60
echo # one connection
netstat -nt | awk '$5 ~ /:22$/'

ssh -f -S ~/.ssh/demo server.example.org sleep 60 &amp;
echo # two connections
netstat -nt | awk '$5 ~ /:22$/'

ssh -f -S ~/.ssh/demo server.example.org sleep 60 &amp;
echo # three connections
netstat -nt | awk '$5 ~ /:22$/'

echo Table 2
&lt;/syntaxhighlight&gt;
|}

The [http://linux.die.net/man/1/sleep sleep(1)] period can be increased if more delay is needed.  While the connections are active, it is also possible to look on the server using [http://linux.die.net/man/1/ps ps(1)], such as with &lt;code&gt;ps uwx&lt;/code&gt;, to see the processes as a means of verifying that multiple connections are indeed being made.  

====Measuring Response Time====

Measuring the response time requires setting up keys with an agent first so that the agent handles the authentication and eliminates authentication as a source of delay.  See the section on keys, if needed.  All of the response time tests below will depend on using keys for authentication.  

For a one-off connection, just add [http://linux.die.net/man/1/time time(1)] to check how long access takes.  

&lt;syntaxhighlight lang=&quot;bash&quot;&gt;$ time ssh -i ~/.ssh/rsakey server.example.org true&lt;/syntaxhighlight&gt;

For a multiplexed connection, a master control session must be established.  Then subsequent connections will show an increase in speed.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -f -M -S ~/.ssh/demo -i ~/.ssh/rsakey server.example.org 
$ time ssh  -S ~/.ssh/demo -i ~/.ssh/rsakey server.example.org true
$ time ssh  -S ~/.ssh/demo -i ~/.ssh/rsakey server.example.org true
&lt;/syntaxhighlight&gt;

These response times are approximate but the difference is nonetheless large enough to be seen between one-off connections and multiplexed connections.

====Keeping sessions open====
Probably you also want to keep your sessions open when inactive. You can configure it using '''ServerAliveInterval''' and '''ServerAliveCountMax''' options, see [http://man.openbsd.org/ssh_config.5 ssh_config(5)] for the details.

==Multiplexing HTTPS and SSH Using sslh==

A different kind of multiplexing is when more than one protocol is carried over the same port.  [https://www.rutschle.net/tech/sslh/README.html sslh] does just that with SSL and SSH.  It figures out what kind of connection is coming in and forwards it to the appropriate service.  Thus it allows a server to receive both HTTPS and SSH over the same port, making it possible to connect to the server from behind restrictive firewalls in some cases.  It does not hide SSH.  Even a quick scan for SSH on the listening port, say with [[OpenSSH/Third_Party_Utilities#scanssh|scanssh(1)]], will show that it is there.  Please note that this method only works with simpler packet filters, such as PF or nftables(8) and its front-ends, firewalld and UFW, which filter based on the destination port and won't fool protocol analysis and application layer filters, such as Zorp, which filter based on the actual protocol used.  Here's how [http://linux.die.net/man/8/sslh sslh(8)] can be installed in four steps:

* First install your web server and configure it to accept HTTPS requests.  Be sure that it listens for HTTPS on the localhost only.  It can help in that regard if it is on a non-standard port, say 2443, instead of 443.  
* Next, set your SSH server to accept connections on the localhost for port 22.  It really could be any port, but port 22 is the standard for SSH.  
* Next, create an unprivileged user to run [http://linux.die.net/man/8/sslh sslh(8)].  The example below has the user 'sslh' for the unprivileged account.  
* Lastly, install and launch [http://linux.die.net/man/8/sslh sslh(8)] so that it listens on port 443 and forwards HTTPS and SSH to the appropriate ports on the local host.  Substitute the external IP number for your machine.  The actual name of the executable and path may vary from system to system:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ /usr/local/sbin/sslh-fork -u sslh -p xx.yy.zz.aa:443 --tls 127.0.0.1:2443 --ssh 127.0.0.1:22
&lt;/syntaxhighlight&gt;

Another option is to use a configuration file with [http://linux.die.net/man/8/sslh sslh(8)] and not pass any parameters at runtime.  There should be at least one sample configuration file, '''basic.cfg''' or '''example.cfg''', included in the package when it is installed.  The finished configuration file should look something like this:

&lt;syntaxhighlight lang=&quot;apache&quot;&gt;
user: &quot;sslh&quot;;
listen: ( { host: &quot;xx.yy.zz.aa&quot;; port: &quot;443&quot; } );
on-timeout: &quot;ssl&quot;;
protocols:
(
   { name: &quot;ssh&quot;; host: &quot;localhost&quot;; port: &quot;22&quot;; probe: &quot;builtin&quot;; },
   { name: &quot;ssl&quot;; host: &quot;localhost&quot;; port: &quot;2443&quot;; probe: &quot;builtin&quot;; }
);
&lt;/syntaxhighlight&gt;

Mind the quotes, commas, and semicolons.  

If an old version of SSH is used in conjunction with now-deprecated TCP Wrappers, as described in [http://linux.die.net/man/5/hosts_access hosts_access(5)], then the option '''service:''' works to provide the name of the service that they need.    

&lt;syntaxhighlight lang=&quot;apache&quot;&gt;    { name: &quot;ssh&quot;; service: &quot;ssh&quot;; host: &quot;localhost&quot;; port: &quot;22&quot;; probe: &quot;builtin&quot;; },&lt;/syntaxhighlight&gt;

If TCP Wrappers are not used, which is most likely the case, then '''service:''' is not needed.  

Runtime parameters override any configuration file settings that may be in place.  [http://linux.die.net/man/8/sslh sslh(8)] supports the protocols HTTP, SSL, SSH, OpenVPN, tinc, and XMPP out of the box.  But actually any protocol that can be identified by regular expression pattern matching can be used.  There are two variants of [https://www.rutschle.net/tech/sslh/README.html sslh], a forked version (sslh or sslh-fork) and a single-threaded version (sslh-select).  See the project web site for more details: https://www.rutschle.net/tech/sslh/README.html 

&lt;noinclude&gt;

== References ==
{{reflist}}
{{OpenSSH/TOC|mini}}
&lt;/noinclude&gt;
{{BookCat}}
{{status|100%}}</text>
      <sha1>esarc4obpi93bore3fjmfw9hj2ak7b4</sha1>
    </revision>
    <revision>
      <id>4675810</id>
      <parentid>4675809</parentid>
      <timestamp>2026-10-13T09:22:51Z</timestamp>
      <contributor>
        <username>Larsnooden</username>
        <id>430753</id>
      </contributor>
      <minor />
      <comment>typo (word missing)</comment>
      <origin>4675810</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="28728" sha1="f7byl9zl5j6zlfiyk93k2czraedrzyz" xml:space="preserve">&lt;noinclude&gt;{{simple chapter navigation|previous=Load Balancing|next=Proxies and Jump Hosts}}&lt;/noinclude&gt;
&amp;nbsp;

Multiplexing is the ability to send more than one signal over a single line or connection.  In OpenSSH, multiplexing can re-use an existing outgoing TCP connection for multiple concurrent SSH sessions to a remote SSH server, avoiding the overhead of creating a new TCP connection and reauthenticating each time.  

&lt;noinclude&gt;__TOC__&lt;/noinclude&gt; 

==Advantages of Multiplexing==

An advantage of SSH multiplexing is that the overhead of creating new TCP connections and negotiating the secure connection is eliminated.  The overall number of connections that a machine may accept is a finite resource and the limit is more noticeable on some machines than on others and varies greatly depending on both load and usage.  There is also a significant delay when opening a new connection.  Activities that repeatedly open new connections can be significantly sped up using multiplexing.

The difference between multiplexing and standalone sessions can be seen by comparing the tables below.  Both are selected output from &lt;code&gt;netstat -nt&lt;/code&gt; slightly edited for clarity.  We see in Table 1, &quot;SSH Connections, Separate&quot;, that without multiplexing each new login creates a new TCP connection, one per login session.  Following that we see in the other table, Table 2, &quot;SSH Connections, Multiplexed&quot;, that when multiplexing is used, new logins are channelled over the already established TCP connection.    

&lt;syntaxhighlight lang=&quot;text&quot;&gt;
#              Local Address       Foreign Address         State

# one connection
tcp    0   0   192.168.x.y:45050   192.168.x.z:22       ESTABLISHED

# two separate connections
tcp    0   0   192.168.x.y:45050   192.168.x.z:22       ESTABLISHED
tcp    0   0   192.168.x.y:45051   192.168.x.z:22       ESTABLISHED

# three separate connections
tcp    0   0   192.168.x.y:45050   192.168.x.z:22       ESTABLISHED
tcp    0   0   192.168.x.y:45051   192.168.x.z:22       ESTABLISHED
tcp    0   0   192.168.x.y:45052   192.168.x.z:22       ESTABLISHED

Table 1: SSH Connections, Separate
&lt;/syntaxhighlight&gt;

Both tables show TCP/IP connections associated with SSH sessions.  The table above shows a new TCP/IP connection for each new SSH connection.  The table below shows a single TCP/IP connection despite multiple active SSH sessions.  

&lt;syntaxhighlight lang=&quot;text&quot;&gt;
#              Local Address       Foreign Address         State

# one connection
tcp    0   0   192.168.x.y:58913   192.168.x.z:22       ESTABLISHED

# two multiplexed connections
tcp    0   0   192.168.x.y:58913   192.168.x.z:22       ESTABLISHED

# three multiplexed connections
tcp    0   0   192.168.x.y:58913   192.168.x.z:22       ESTABLISHED

Table 2: SSH Connections, Multiplexed
&lt;/syntaxhighlight&gt;

As we can see with multiplexing, only a single TCP connection is set up and used regardless of whether or not there are multiple SSH sessions carried over it.

Or we can compare the time it takes to run [http://man.openbsd.org/true.1 true(1)] on a slow remote server, using [http://linux.die.net/man/1/time  time(1)].  The two commands would be something like &lt;code&gt;time ssh server.example.org true&lt;/code&gt; versus &lt;code&gt;time ssh -S ./path/to/somesocket server.example.org true&lt;/code&gt; and use keys with an agent for each of them.  First without multiplexing, we see the normal connection time:

&lt;syntaxhighlight lang=&quot;text&quot;&gt;
real    0m0.658s
user    0m0.016s
sys     0m0.008s
&lt;/syntaxhighlight&gt;

Then we do the same thing again, but with a multiplexed connection to see a faster result:

&lt;syntaxhighlight lang=&quot;text&quot;&gt;
real    0m0.029s
user    0m0.004s
sys     0m0.004s
&lt;/syntaxhighlight&gt;

The difference is quite large and will definitely add up for any activity where connections are made repeatedly in rapid succession.  The speed gain for multiplexed connections doesn't come with the master connection, that is normal speed, but with the second and subsequent multiplexed connections.  The overhead for a new SSH connection remains, but the overhead of a new TCP connection is avoided.  The second and later connections will reuse the established TCP connection over and over and not need to create a new TCP connection for each new SSH connection.

==Setting Up Multiplexing==

The OpenSSH client supports multiplexing its outgoing connections, since version 3.9 (August 18, 2004)&lt;ref name=&quot;multiplexing&quot;&gt;{{cite web |url=https://www.openssh.org/txt/release-3.9 |title=OpenSSH 3.9 Release Notes |accessdate=2018-12-16 |date=2004-08-18 |publisher=OpenSSH }}&lt;/ref&gt;, using the '''ControlMaster''', '''ControlPath''' and '''ControlPersist''' configuration directives which get defined in [http://man.openbsd.org/ssh_config.5 ssh_config(5)].  The client configuration file usually defaults to the location '''~/.ssh/config'''.  All three directives are described in the manual page for [http://man.openbsd.org/ssh_config.5 ssh_config(5)].   See also the &quot;TOKENS&quot; section there for the list of tokens available for use in the '''ControlPath'''.  Any valid tokens used are expanded at run time.  

'''ControlMaster''' determines whether [http://man.openbsd.org/ssh.1 ssh(1)] will listen for control connections and what to do about them.  '''ControlPath''' sets the location for the control socket used by the multiplexed sessions.  These can be either globally or locally in [http://man.openbsd.org/ssh_config.5 ssh_config(5)] or else specified at run time.  Control sockets are removed automatically when the master connection has ended.  '''ControlPersist''' can be used in conjunction with '''ControlMaster'''.  If '''ControlPersist''' is set to 'yes', then it will leave the master connection open in the background to accept new connections until either killed explicitly or closed with '''-O''' or ends at a pre-defined timeout.  If '''ControlPersist''' is set to a time, then it will leave the master connection open for the designated time or until the last multiplexed session is closed, whichever is longer.  

Here is a sample excerpt from [http://man.openbsd.org/ssh_config.5 ssh_config(5)] applicable for starting a multiplexed session to ''machine1.example.org'' via the shortcut ''machine1''.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Host machine1
        HostName machine1.example.org
        ControlPath ~/.ssh/controlmasters/%r@%h:%p
        ControlMaster auto
        ControlPersist 10m
&lt;/syntaxhighlight&gt;

With that configuration, the first connection to ''machine1'' will create a control socket in the directory '''~/.ssh/controlmasters/''' and then any subsequent connections, up to 10 by default as set by '''MaxSessions''' on the SSH server, will re-use that control path automatically as multiplexed sessions.   Confirmation of each new connection can be required if '''ControlMaster''' set to 'autoask' instead of 'auto'.  

Please note with the settings above that the control socket would be placed into the folder '''~/.ssh/controlmasters/'''.  If that folder doesn't exist first, the SSH client will exit with a specific error about unix_listener complaining that the file or path does not exist:

&lt;syntaxhighlight lang=&quot;text&quot;&gt;
unix_listener: cannot bind to path /home/fred/.ssh/controlmasters/fred@machine1.example.org:22.EOWsvm5xFt30O6CB: No such file or directory
&lt;/syntaxhighlight&gt;

With the '''-O''' option, [http://man.openbsd.org/ssh.1 ssh(1)] can be used to manage the connection using the same shortcut configuration.  Use 'check' to see the status of the connections.  To cancel all existing connections, including the master connection, use 'exit' instead of 'stop'.   

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -O check machine1
Master running (pid=14379)
$ ssh -O stop machine1
Stop listening request sent
$ ssh -O check machine1
Control socket connect(/Users/Username/.ssh/sockets/machine1): No such file or directory
&lt;/syntaxhighlight&gt;

In that example, the status of the connection is checked first.  Then the master connection is told not to accept further multiplexing requests and finally we check again and verify that the control socket is not available any more.

It is also possible to show information about the connection.  Note that the ''machine1'' shortcut was defined above and sets the path to the '''ControlPath''' socket.  The option '''-O conninfo''' corresponds to the '''~I''' escape function.  The connections are being made from ''client.example.org'' at the address ''192.0.2.98'' to the system at the address ''203.0.113.206'' named ''machine1.example.org''.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -O conninfo machine1
Connection information for client.example.org pid 83539
  tcp 192.0.2.98:18952 -&gt; 203.0.113.206:22
  kexalgorithm mlkem768x25519-sha256
  hostkeyalgorithm ssh-ed25519
  cipher chacha20-poly1305@openssh.com
  mac &lt;implicit&gt;
  compression none
  rekey limit none interval none
  traffic 112 pkts 466 blks 6.4KB in, 94 pkts 329 blks 5.8KB out
&lt;/syntaxhighlight&gt;

Similarly, the  '''-O channels''' option displays which channels are open in that multiplexing session.  However, it has no corresponding escape sequence.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -O channels machine1
The following connections are open:
  #1 mux-control (t16 [mux-control] nr0 m0 i0/0 o0/0 e[closed]/0 fd 5/5/-1 sock 5 cc -1 c2 io 0x01/0x00 I)
  #2 client-session (t4 [session] r0 nm0 i0/0 o0/0 e[write]/0 fd 6/7/8 sock -1 cc 1 nc0 io 0x01/0x00 RTI)
  #3 mux-control (t16 [mux-control] nr0 m0 i0/0 o0/0 e[closed]/0 fd 9/9/-1 sock 9 cc -1 c4 io 0x01/0x00 I)
  #4 client-session (t4 [session] r1 nm0 i0/0 o0/0 e[write]/0 fd 10/11/12 sock -1 cc 3 nc0 io 0x01/0x00 RTI)
  #5 mux-control (t16 [mux-control] nr0 m0 i0/0 o0/0 e[closed]/0 fd 13/13/-1 sock 13 cc -1 nc0 io 0x01/0x01 I)
&lt;/syntaxhighlight&gt;

That example shows two SSH connections over the same network connection: one master connection plus one child.  

====Manually Establishing Multiplexed Connections====

Multiplexed sessions need a control master to connect to.  The run time parameters '''-M''' and '''-S''' also correspond to '''ControlMaster''' and '''ControlPath''', respectively.   So first an initial master connection is established using '''-M''' when accompanied by the path to the control socket using '''-S'''.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -M -S /home/fred/.ssh/controlmasters/fred@server.example.org:22 server.example.org
&lt;/syntaxhighlight&gt;

Then subsequent multiplexed connections are made in other terminals.  They use '''ControlPath''' or '''-S''' to point to the control socket.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -S /home/fred/.ssh/controlmasters/fred@server.example.org:22 server.example.org
&lt;/syntaxhighlight&gt;

Note that the control socket is named &quot;fred@server.example.org:22&quot;, or ''%r@%h:%p'', to try to make the name unique.  The combination %r,  %h and %p stand for the remote user name, the remote host and the remote host's port.  The control sockets should be given unique names.  

Multiple '''-M''' options place [http://man.openbsd.org/ssh.1 ssh(1)] into '''master''' mode with confirmation required before slave connections are accepted.  This is the same as '''ControlMaster=ask'''.  Both require [http://man.openbsd.org/ssh.1 ssh(1)] to ask for the confirmation.  

Here is the master connection for the host ''server.example.org'' as set to ask for confirmation of new multiplexed sessions:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -MM -S ~/.ssh/controlmasters/%r@%h:%p server.example.org
&lt;/syntaxhighlight&gt;

And here is a subsequent multiplexed connection:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -S ~/.ssh/controlmasters/%r@%h:%p server.example.org
&lt;/syntaxhighlight&gt;

The status of the control master connection can be queried using '''-O check''', which will tell if it is running or not.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -O check -S ~/.ssh/controlmasters/%r@%h:%p server.example.org
&lt;/syntaxhighlight&gt;

If the control session has been stopped, the query will return an error about &quot;No such file or directory&quot; even if there are still multiplexed sessions running because the socket is gone.  

Alternately, instead of specifying '''-M''' and '''-S''' as runtime options,  configuration options can be spelled out in full using '''-o''' for easier transfer to the client configuration file when figured out.   

The way below sets configuration options as run time parameters by first starting a control master.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -o &quot;ControlMaster=yes&quot; -o &quot;ControlPath=/home/fred/.ssh/controlmasters/%r@%h:%p&quot; server.example.org
&lt;/syntaxhighlight&gt;

Then subsequent sessions are connected to the control master via socket at the end of the control path.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -o &quot;ControlPath=/home/fred/.ssh/controlmasters/%r@%h:%p&quot;  server.example.org
&lt;/syntaxhighlight&gt;

And of course all that can be put into [http://man.openbsd.org/ssh_config.5 ssh_config(5)] as shown in the previous section.  Starting with 6.7, the combination of %r@%h:%p and variations on it can be replaced with %C which by itself generates a SHA1 hash from the concatenation of %l%h%p%r.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -S ~/.ssh/controlmasters/%C server.example.org
&lt;/syntaxhighlight&gt;

There are two advantages with that.  One is that the hash can be shorter than its combined elements while still uniquely identifying the connection.  The other is that it obfuscates the connection information which would have been otherwise displayed in the socket's name.

===Ending Multiplexed Connections===

One way to end multiplexed sessions is to exit all related SSH sessions, including the control master.  If the control master has been placed in the background using '''ControlPersist''', then it will be necessary to stop it with '''-O''' and either 'stop' or 'exit'.  That also requires knowing the full path to and filename of the control socket as used in the creation of the master session, if it has not been defined in a shortcut in [http://man.openbsd.org/ssh_config.5 ssh_config(5)].

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -O stop server1
$ ssh -O stop -S ~/.ssh/controlmasters/%C server1.example.org
&lt;/syntaxhighlight&gt;

The multiplex command '''-O stop''' will gracefully shutdown multiplexing.  After issuing the command, the control socket is removed and no new multiplexed sessions are accepted for that master.  Existing connections are allowed to continue and the master connection will persist until the last multiplexed connection closes.  

In contrast, the multiplex command '''-O exit''' removes the control socket and immediately terminates all existing connections.  

Again, the directive '''ControlPersist''' can also be set to timeout after a set period of disuse.  The time interval there is written in a time format listed in [http://man.openbsd.org/sshd_config.5 sshd_config(5)] or else defaults to seconds if no units are given.   It will cause the master connection to automatically close if it has no client connections for the specified time.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Host server1
        HostName server1.example.org
        ControlPath ~/.ssh/controlmasters/%C
        ControlMaster yes
        ControlPersist 2h
&lt;/syntaxhighlight&gt;

The above example lets the control master timeout after 2 hours of inactivity.  Care should be used with persistent control sockets.   A user that can read and write to a control socket can establish new connections without further authentication.

===Multiplexing Options===

The values for configuring session multiplexing can be set either in the user-specific [http://man.openbsd.org/ssh_config.5 ssh_config(5)], or the global '''/etc/ssh/ssh_config''', or using parameters when running from the shell or a script.   '''ControlMaster''' can be overridden in the run time arguments to re-use an existing master when '''ControlMaster''' is set to 'yes', by setting it explicitly to 'no':

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -o &quot;ControlMaster=no&quot; server.example.org
&lt;/syntaxhighlight&gt;

'''ControlMaster''' accepts five different values: 'no', 'yes', 'ask', 'auto', and 'autoask'.   

* 'no' is the default.  New sessions will not try to connect to an established master session, but additional sessions can still multiplex by connecting explicitly to an existing socket.
* 'yes' creates a new master session each time, unless explicitly overridden.  The new master session will listen for connections.   
* 'ask'  creates a new master each time, unless overridden, which listen for connections.  If overridden,  [http://man.openbsd.org/ssh-askpass.1 ssh-askpass(1)] will popup an message in X to ask the master session owner to approve or deny the request.  If the request is denied, then the session being created falls back to being a regular, standalone session.    
* 'auto' creates a master session automatically but if there is a master session already available, subsequent sessions are automatically multiplexed.
* 'autoask' automatically assumes that if a master session exists, that subsequent sessions should be multiplexed, but ask first before adding a session.   

Refused connections are logged to the master session.

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Host * 
        ControlMaster ask 
&lt;/syntaxhighlight&gt;

'''ControlPath'''  can be a fixed string or include any of several pre-defined variables described in the TOKENS section of the [http://man.openbsd.org/ssh_config.5#TOKENS ssh_config(5)].  '''%L''' is for the first component of the local host name and '''%l''' for the full local host name.  '''%h''' is the target host name and '''%n''' is the original target host name and '''%p''' is for the destination port on the remote server.  '''%r''' is for the remote user name and '''%u''' for the user running [http://man.openbsd.org/ssh.1 ssh(1)].  Or they can be combined as '''%C''' which is a SHA1 hash produced from '''%l%h%p%r'''.

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Host * 
        ControlMaster ask 
        ControlPath ~/.ssh/controlmasters/%C
&lt;/syntaxhighlight&gt;

'''ControlPersist''' accepts 'yes', 'no' or a time interval.  If a time interval is given, the default is in seconds.  Units can extend the time to minutes, hours, days, weeks or  a combination.  If 'yes' the master connection stays in the background indefinitely. 

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Host * 
        ControlMaster ask 
        ControlPath ~/.ssh/controlmasters/%C
        ControlPersist 10m
&lt;/syntaxhighlight&gt;

====Port Forwarding After the Fact====

It is possible to request port forwarding without having to establish new connections.  Here we forward port 8080 on the local host to port 80 on the remote host using '''-L''':

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -O forward -L 8080:localhost:80 -S ~/.ssh/controlmasters/fred@server.example.org:22  server.example.org
&lt;/syntaxhighlight&gt;

The same can be done for remote forwarding, using '''-R'''.  The escape sequence '''~C''' is not available for multiplexed sessions, so '''-O forward''' is the only way to add port forwarding on the fly.  

Port forwarding can be canceled without having to close any sessions using '''-O cancel'''.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -O cancel -L 8080:localhost:80 -S ~/.ssh/controlmasters/fred@server.example.org:22  server.example.org
&lt;/syntaxhighlight&gt;

The exact same syntax used for forwarding is used for cancelling.  However, there is no way currently to look up which ports are being forwarded and how they are forwarded.

==Additional Notes About Multiplexing==

Never use any publicly accessible directory for the control path sockets.  Place those sockets in a directory somewhere else, one to which only your account has access.  For example '''~/.ssh/socket/''' would be a much safer choice and '''/tmp/''' would be a bad choice. 

In cases where it is useful to have a standing connection, it is always possible to combine multiplexing with other options, such as '''-f''' or '''-N''' to have the control master drop to the background upon connection and not load a shell.  

In [http://man.openbsd.org/sshd_config.5 sshd_config(5)], the directive '''MaxSessions''' specifies the maximum number of open sessions permitted per network connection.  This is used when multiplexing ssh sessions over a single TCP connection.  Setting '''MaxSessions''' to 1 disables multiplexing and setting it to 0 disables login/shell/subsystem sessions completely.  The default is 10.  The '''MaxSessions''' directive can also be set under a '''Match''' conditional block so that different settings are available for different conditions.

===Errors Preventing Multiplexing===

The directory used for holding the control sockets must be on a file system that actually allows the creation of sockets.   AFS is one example that doesn't, as are some implementations of HFS+.  If an attempt is made at creating a socket on a file system that does not allow it, an error something like the following will occur:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -M -S /home/fred/.ssh/mux 192.0.2.57
muxserver_listen: link mux listener /home/fred/.ssh/mux.vjfeIFFzHnhgHoOV =&gt; /home/fred/.ssh/mux: Operation not permitted
&lt;/syntaxhighlight&gt;

A similar issue was seen when trying to make Unix domain sockets on OverlayFS filesystems, which are often used with Docker, prior to Linux 4.7 kernel&lt;ref name=&quot;docker-overlayfs-bug&quot;&gt;{{cite mailing list |url=https://lkml.org/lkml/2016/6/16/87 |title=[GIT PULL] overlayfs fixes for 4.7-rc3 |date=2016-06-16 |accessdate=2018-10-05 |mailing-list=LKML |last=Szeredi |first=Miklos |author=Miklos Szeredi}}&lt;/ref&gt;.

If the file system cannot be reconfigured to allow sockets, then the only other option is to place the control path socket somewhere else on a file system that does support creation of sockets.

===Observing Multiplexing===

It is possible to make some rough measurements to show the differences between multiplexed connections and one-off connections as shown in the tables and figures above.  

====Measuring the Number of TCP Connections====

Tables 1 and 2 above use output from [http://linux.die.net/man/8/netstat netstat(8)] and [http://linux.die.net/man/1/awk awk(1)] to show the number of TCP connections corresponding to the number of SSH connections.

{|
|
&lt;syntaxhighlight lang=&quot;bash&quot;&gt;
#!/bin/sh
netstat -nt | awk 'NR == 2'

ssh -f server.example.org sleep 60
echo # one connection
netstat -nt | awk '$5 ~ /:22$/'

ssh -f server.example.org sleep 60
echo # two connections
netstat -nt | awk '$5 ~ /:22$/'

ssh -f server.example.org sleep 60
echo # three connections
netstat -nt | awk '$5 ~ /:22$/'

echo Table 1
&lt;/syntaxhighlight&gt;
|
And
|
&lt;syntaxhighlight lang=&quot;bash&quot;&gt;
#!/bin/sh
netstat -nt | awk 'NR == 2'

ssh -f -M -S ~/.ssh/demo server.example.org sleep 60
echo # one connection
netstat -nt | awk '$5 ~ /:22$/'

ssh -f -S ~/.ssh/demo server.example.org sleep 60 &amp;
echo # two connections
netstat -nt | awk '$5 ~ /:22$/'

ssh -f -S ~/.ssh/demo server.example.org sleep 60 &amp;
echo # three connections
netstat -nt | awk '$5 ~ /:22$/'

echo Table 2
&lt;/syntaxhighlight&gt;
|}

The [http://linux.die.net/man/1/sleep sleep(1)] period can be increased if more delay is needed.  While the connections are active, it is also possible to look on the server using [http://linux.die.net/man/1/ps ps(1)], such as with &lt;code&gt;ps uwx&lt;/code&gt;, to see the processes as a means of verifying that multiple connections are indeed being made.  

====Measuring Response Time====

Measuring the response time requires setting up keys with an agent first so that the agent handles the authentication and eliminates authentication as a source of delay.  See the section on keys, if needed.  All of the response time tests below will depend on using keys for authentication.  

For a one-off connection, just add [http://linux.die.net/man/1/time time(1)] to check how long access takes.  

&lt;syntaxhighlight lang=&quot;bash&quot;&gt;$ time ssh -i ~/.ssh/rsakey server.example.org true&lt;/syntaxhighlight&gt;

For a multiplexed connection, a master control session must be established.  Then subsequent connections will show an increase in speed.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -f -M -S ~/.ssh/demo -i ~/.ssh/rsakey server.example.org 
$ time ssh  -S ~/.ssh/demo -i ~/.ssh/rsakey server.example.org true
$ time ssh  -S ~/.ssh/demo -i ~/.ssh/rsakey server.example.org true
&lt;/syntaxhighlight&gt;

These response times are approximate but the difference is nonetheless large enough to be seen between one-off connections and multiplexed connections.

====Keeping sessions open====
Probably you also want to keep your sessions open when inactive. You can configure it using '''ServerAliveInterval''' and '''ServerAliveCountMax''' options, see [http://man.openbsd.org/ssh_config.5 ssh_config(5)] for the details.

==Multiplexing HTTPS and SSH Using sslh==

A different kind of multiplexing is when more than one protocol is carried over the same port.  [https://www.rutschle.net/tech/sslh/README.html sslh] does just that with SSL and SSH.  It figures out what kind of connection is coming in and forwards it to the appropriate service.  Thus it allows a server to receive both HTTPS and SSH over the same port, making it possible to connect to the server from behind restrictive firewalls in some cases.  It does not hide SSH.  Even a quick scan for SSH on the listening port, say with [[OpenSSH/Third_Party_Utilities#scanssh|scanssh(1)]], will show that it is there.  Please note that this method only works with simpler packet filters, such as PF or nftables(8) and its front-ends, firewalld and UFW, which filter based on the destination port and won't fool protocol analysis and application layer filters, such as Zorp, which filter based on the actual protocol used.  Here's how [http://linux.die.net/man/8/sslh sslh(8)] can be installed in four steps:

* First install your web server and configure it to accept HTTPS requests.  Be sure that it listens for HTTPS on the localhost only.  It can help in that regard if it is on a non-standard port, say 2443, instead of 443.  
* Next, set your SSH server to accept connections on the localhost for port 22.  It really could be any port, but port 22 is the standard for SSH.  
* Next, create an unprivileged user to run [http://linux.die.net/man/8/sslh sslh(8)].  The example below has the user 'sslh' for the unprivileged account.  
* Lastly, install and launch [http://linux.die.net/man/8/sslh sslh(8)] so that it listens on port 443 and forwards HTTPS and SSH to the appropriate ports on the local host.  Substitute the external IP number for your machine.  The actual name of the executable and path may vary from system to system:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ /usr/local/sbin/sslh-fork -u sslh -p xx.yy.zz.aa:443 --tls 127.0.0.1:2443 --ssh 127.0.0.1:22
&lt;/syntaxhighlight&gt;

Another option is to use a configuration file with [http://linux.die.net/man/8/sslh sslh(8)] and not pass any parameters at runtime.  There should be at least one sample configuration file, '''basic.cfg''' or '''example.cfg''', included in the package when it is installed.  The finished configuration file should look something like this:

&lt;syntaxhighlight lang=&quot;apache&quot;&gt;
user: &quot;sslh&quot;;
listen: ( { host: &quot;xx.yy.zz.aa&quot;; port: &quot;443&quot; } );
on-timeout: &quot;ssl&quot;;
protocols:
(
   { name: &quot;ssh&quot;; host: &quot;localhost&quot;; port: &quot;22&quot;; probe: &quot;builtin&quot;; },
   { name: &quot;ssl&quot;; host: &quot;localhost&quot;; port: &quot;2443&quot;; probe: &quot;builtin&quot;; }
);
&lt;/syntaxhighlight&gt;

Mind the quotes, commas, and semicolons.  

If an old version of SSH is used in conjunction with now-deprecated TCP Wrappers, as described in [http://linux.die.net/man/5/hosts_access hosts_access(5)], then the option '''service:''' works to provide the name of the service that they need.    

&lt;syntaxhighlight lang=&quot;apache&quot;&gt;    { name: &quot;ssh&quot;; service: &quot;ssh&quot;; host: &quot;localhost&quot;; port: &quot;22&quot;; probe: &quot;builtin&quot;; },&lt;/syntaxhighlight&gt;

If TCP Wrappers are not used, which is most likely the case, then '''service:''' is not needed.  

Runtime parameters override any configuration file settings that may be in place.  [http://linux.die.net/man/8/sslh sslh(8)] supports the protocols HTTP, SSL, SSH, OpenVPN, tinc, and XMPP out of the box.  But actually any protocol that can be identified by regular expression pattern matching can be used.  There are two variants of [https://www.rutschle.net/tech/sslh/README.html sslh], a forked version (sslh or sslh-fork) and a single-threaded version (sslh-select).  See the project web site for more details: https://www.rutschle.net/tech/sslh/README.html 

&lt;noinclude&gt;

== References ==
{{reflist}}
{{OpenSSH/TOC|mini}}
&lt;/noinclude&gt;
{{BookCat}}
{{status|100%}}</text>
      <sha1>f7byl9zl5j6zlfiyk93k2czraedrzyz</sha1>
    </revision>
  </page>
  <page>
    <title>Structural Biochemistry/Proteins/Histone Modifications</title>
    <ns>0</ns>
    <id>262816</id>
    <revision>
      <id>4675802</id>
      <parentid>4106198</parentid>
      <timestamp>2026-10-13T07:58:46Z</timestamp>
      <contributor>
        <username>Jcb</username>
        <id>90773</id>
      </contributor>
      <origin>4675802</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="8139" sha1="lz4gllmxqu32towxs7z709vr6dry31j" xml:space="preserve">=Histone=

A Histone is an alkaline protein found in eukaryotic cells that orders the DNA stain and plays a role in gene regulation. In order for DNA to form into chromosomes the DNA coils around the histone protein to form chromatin, without this process life would not exist. 

==Classes==
There are five major classes of Histones: H1/H5, H2A, H2B, H3, and H4. Histones H2A, H2B, H3, and H4 are known as the core histones, while histones H1/H5 are known as the linker histones.&lt;ref&gt;Cox, Michael; Nelson, David R.; Lehninger, Albert L (2005). Lehninger Principles of Biochemistry. San Francisco: W.H. Freeman. {{ISBN|0-7167-4339-6}}.&lt;/ref&gt; 
A nucleosome core particle is a combination of two of each of the core histones, and this core particle is responsible for winding up a section of the DNA, approximately 147 base pairs. The linker histone keeps the wound section of DNA in place by binding to the neucleosome and to the entry and exit sites of the DNA, locking it into place. The combination of DNA wound up in histones is called a chromatin.   

==Functions of Histone Modifications==

Sometimes histone modifications affect the structure of chromatin, or they may act as a mark or a signal for protein effectors. &lt;ref&gt; Suganuma, Tamaki, and Jerry L. Workman. &quot;Signals and Combinatorial Functions of Histone Modification.&quot; PubMed. Annual Reviews, 26 Apr. 2011. Web. 12 Dec. 2011. &lt;http://www.annualreviews.org/doi/full/10.1146/annurev-biochem-061809-175347?url_ver=Z39.88-2003&amp;rfr_id=ori:rid:crossref.org&amp;rfr_dat=cr_pub%3dpubmed&amp;&gt; &lt;/ref&gt; 


'''Alterations of the Structure of Chromatin'''

High orders of chromitin structure can be directly affected by Histone
modifications. Removal of Histone tails  by trypsin results in a decrease
of the ability of nucleosome arrays to comdense into 30 nanometer
chromatin fibers.  Acetylation of H4K16 has also been experimentally shown
to inhibit the formation of 30-nm chromatin fibers.  Many Histone
Acetyltransferase (HAT) complexes have the function of acetylating
multiple lysines of Histone H4, including H4K16. Histone acetylation occurs at the lysine residues and is recognized by the bromo domain proteins. It is important for chromatin decondensation and euchromatin formation. Euchromatin is considered to be open chromatin and is more accessible to proteins. Thus, acetylation leads to additional transcriptional factors binding and thus the DNA can be available for transcription.  Acetylation of H4K16
serves an important part in DNA replication, gene splicing, and life-span
regulation of yeast.

Chromatin can also be altered by methylation at the lysines and the arginines by histone methyl transferases (HMT) which add on methyl groups. These are recognized by chromo domain proteins and is important for the condensation of chromatin and heterochromatin formation. Heterochromatin is considered to be tightly closed chromatin and is less accessible to proteins.

Source: Molecular Cell Biology, Lodish et al., 6th edition (2008), pages 247-257

'''Targeting and/or Activating Chromatin-Remodeling Complexes'''

Histone modifications can also affect chromatin structures by acting as marks for the activity or the gathering of protein complexes that change and reconstruct the chromatin structure. These are ATP-dependent chromatin remodeling complexes which are a group of proteins that slide nucleosomes on DNA with the purpose of changing or getting rid of the histones.&lt;ref&gt; Suganuma, Tamaki, and Jerry L. Workman. &quot;Signals and Combinatorial Functions of Histone Modification.&quot; PubMed. Annual Reviews, 26 Apr. 2011. Web. 12 Dec. 2011. &lt;http://www.annualreviews.org/doi/full/10.1146/annurev-biochem-061809-175347?url_ver=Z39.88-2003&amp;rfr_id=ori:rid:crossref.org&amp;rfr_dat=cr_pub%3dpubmed&amp;&gt; &lt;/ref&gt; The nucleosome remodeling complexes have one to twelve subunits that include multiple protein domains that interact with DNA. Often, these domains recognize histone modifications.
One of the first domains discovered to interact with an already modified histone and to recognize acetyl-lysine residues in the histones were bromodomains. These bromodomains found in subunits of the SWI/SNF family of chromatin-remodeling complexes play an important role in gene activation.
For example, acetylated histones can be evicted from the DNA complex and replaced with the SWI/SNF complex (Figure 1). This process occurs when sequence-specific DNA-binding transcription activators recruit the SAGA histone acetyltransferase to target the genes where SAGA acetylated a patch of nucleosomes on the promoter region. Then, the same activators can obtain the SWI/SNF nucleosome -remodeling complex to the same site and binds to the acetylated histones. Finally, the SWI/SNF complex uses the energy of ATP hydrolysis to displace the acetylated histones generating a neucleosome free region.&lt;ref&gt; Suganuma, Tamaki, and Jerry L. Workman. &quot;Signals and Combinatorial Functions of Histone Modification.&quot; PubMed. Annual Reviews, 26 Apr. 2011. Web. 12 Dec. 2011. &lt;http://www.annualreviews.org/doi/full/10.1146/annurev-biochem-061809-175347?url_ver=Z39.88-2003&amp;rfr_id=ori:rid:crossref.org&amp;rfr_dat=cr_pub%3dpubmed&amp;&gt; &lt;/ref&gt;

'''Actively Transcribed Genes'''

Two of the histone modifications are involved in active transcription

-Trimethylation of H3 lysine 4 at the promoter of active genes, which is done by the COMPASS complex.&lt;ref&gt;Krogan NJ, Dover J, Wood A, Schneider J, Heidt J, Boateng MA et al. (2003). &quot;The Paf1 complex is required for histone H3 methylation by COMPASS and Dot1p: linking transcriptional elongation to histone methylation.&quot;. Mol Cell 11 (3): 721–9. doi:10.1016/S1097-2765(03)00091-1. {{PMID|12667454}}.&lt;/ref&gt; The role of this modification is not clear, but the level of this modification is correlated with the transcriptional activity of the gene. 

-Trimethylation of H3 lysine 36 at the body of active genes. This modification is recognized by the Rpd3 histone, which deacetylates surrounding histones. This increases chromatin compaction, which prevents the likelihood of new transcription events from occurring while one is already in progress.&lt;ref&gt;Carrozza MJ, Li B, Florens L, Suganuma T, Swanson SK, Lee KK et al. (2005). &quot;Histone H3 methylation by Set2 directs deacetylation of coding regions by Rpd3S to suppress spurious intragenic transcription.&quot;. Cell 123 (4): 581–92. doi:10.1016/j.cell.2005.10.023. {{PMID|16286007}}.&lt;/ref&gt; This helps to ensure that a transcription in progress is not interrupted.

'''Repressed Genes'''

There are three histone modifications that are associated with gene repression. 

-Trimethylation of H3 lysine 27. This is done by the polycomb complex PRC2, which is usually bound with other proteins and it binds to the gene, causing chromatin compaction, which silences transcription activity.&lt;ref&gt;Kuzmichev A, Nishioka K, Erdjument-Bromage H, Tempst P, Reinberg D (2002). &quot;Histone methyltransferase activity associated with a human multiprotein complex containing the Enhancer of Zeste protein.&quot;. Genes Dev 16 (22): 2893–905. doi:10.1101/gad.1035902. PMC 187479. {{PMID|12435631}}&lt;/ref&gt; PRC1 has also been known to aid PRC2 in the histone modification.

-Di and trimethylation of H3 lysine 9 is a well-known marker for heterochromatin, a tightly packed form of DNA. An RNA-induced transcriptional silencing complex (RITS) is responsible for this modification.&lt;ref&gt;Kuzmichev A, Nishioka K, Erdjument-Bromage H, Tempst P, Reinberg D (2002). &quot;Histone methyltransferase activity associated with a human multiprotein complex containing the Enhancer of Zeste protein.&quot;. Genes Dev 16 (22): 2893–905. doi:10.1101/gad.1035902. PMC 187479. {{PMID|12435631}}&lt;/ref&gt; 

-Trimethylation of H4 lysine 20 is a modification done by Suv4-20hmethyltransferase that is also associated with heterochromatin.&lt;ref&gt;Kuzmichev A, Nishioka K, Erdjument-Bromage H, Tempst P, Reinberg D (2002). &quot;Histone methyltransferase activity associated with a human multiprotein complex containing the Enhancer of Zeste protein.&quot;. Genes Dev 16 (22): 2893–905. doi:10.1101/gad.1035902. PMC 187479. {{PMID|12435631}}&lt;/ref&gt; 
   

==References==
{{reflist}}
{{BookCat}}</text>
      <sha1>lz4gllmxqu32towxs7z709vr6dry31j</sha1>
    </revision>
  </page>
  <page>
    <title>Koine Greek/Exercise in Pronunciation: John 1:1-5</title>
    <ns>0</ns>
    <id>266063</id>
    <revision>
      <id>4675767</id>
      <parentid>4672553</parentid>
      <timestamp>2026-10-13T00:27:02Z</timestamp>
      <contributor>
        <username>It-is-Truly-Meet</username>
        <id>3624460</id>
      </contributor>
      <minor />
      <origin>4675767</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1241" sha1="76vb52cry2xy66lm4v012z02p5nbqdm" xml:space="preserve">== John 1:1-5 == 

Try reading this out loud and check your pronunciation with the recording provided below. 

 &lt;sup&gt;1&lt;/sup&gt;Ἐν ἀρχῇ ἦν ὁ λόγος, καὶ ὁ λόγος ἦν πρὸς τὸν θεόν, καὶ θεὸς ἦν ὁ λόγος. &lt;sup&gt;2&lt;/sup&gt;οὗτος ἦν ἐν ἀρχῇ πρὸς τὸν θεόν. &lt;sup&gt;3&lt;/sup&gt;πάντα δι' αὐτοῦ ἐγένετο, καὶ χωρὶς αὐτοῦ ἐγένετο οὐδὲ ἕν ὃ γέγονεν. &lt;sup&gt;4&lt;/sup&gt;ἐν αὐτῷ ζωὴ ἦν, καὶ ἡ ζωὴ ἦν τὸ φῶς τῶν ἀνθρώπων &lt;sup&gt;5&lt;/sup&gt;καὶ τὸ φῶς ἐν τῇ σκοτίᾳ φαίνει, καὶ ἡ σκοτία αὐτὸ οὐ κατέλαβεν.
{{Audio|A Reading of John 1 1-5.ogg}}
----
 &lt;sup&gt;1&lt;/sup&gt;In the beginning was the Word, and the Word was with God, and the Word was God. &lt;sup&gt;2&lt;/sup&gt;The same was in the beginning with God. &lt;sup&gt;3&lt;/sup&gt; All things were made by him; and without him was not any thing made that was made. &lt;sup&gt;4&lt;/sup&gt;In him was life; and the life was the light of men. &lt;sup&gt;5&lt;/sup&gt;And the light shineth in darkness; and the darkness comprehended it not.

Congratulations on reciting your first few sentences in Koine Greek!

{{BookCat}}</text>
      <sha1>76vb52cry2xy66lm4v012z02p5nbqdm</sha1>
    </revision>
    <revision>
      <id>4675788</id>
      <parentid>4675767</parentid>
      <timestamp>2026-10-13T06:25:00Z</timestamp>
      <contributor>
        <username>It-is-Truly-Meet</username>
        <id>3624460</id>
      </contributor>
      <minor />
      <comment>https://lindaktaylor.com/2022/09/30/guidelines-for-quoting-bible-material-part-1/</comment>
      <origin>4675788</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="5945" sha1="gotbnh058vmatxw4wp7p6pi7j3nyx5e" xml:space="preserve">Try reading this out loud and check your pronunciation with the recording provided below. 

 &lt;sup&gt;1&lt;/sup&gt;Ἐν ἀρχῇ ἦν ὁ λόγος, καὶ ὁ λόγος ἦν πρὸς τὸν θεόν, καὶ θεὸς ἦν ὁ λόγος. &lt;sup&gt;2&lt;/sup&gt;οὗτος ἦν ἐν ἀρχῇ πρὸς τὸν θεόν. &lt;sup&gt;3&lt;/sup&gt;πάντα δι' αὐτοῦ ἐγένετο, καὶ χωρὶς αὐτοῦ ἐγένετο οὐδὲ ἕν ὃ γέγονεν. &lt;sup&gt;4&lt;/sup&gt;ἐν αὐτῷ ζωὴ ἦν, καὶ ἡ ζωὴ ἦν τὸ φῶς τῶν ἀνθρώπων &lt;sup&gt;5&lt;/sup&gt;καὶ τὸ φῶς ἐν τῇ σκοτίᾳ φαίνει, καὶ ἡ σκοτία αὐτὸ οὐ κατέλαβεν.
{{Audio|A Reading of John 1 1-5.ogg}}
----
 &lt;sup&gt;1&lt;/sup&gt;In the beginning was the Word, and the Word was with God, and the Word was God. &lt;sup&gt;2&lt;/sup&gt;The same was in the beginning with God. &lt;sup&gt;3&lt;/sup&gt; All things were made by him; and without him was not any thing made that was made. &lt;sup&gt;4&lt;/sup&gt;In him was life; and the life was the light of men. &lt;sup&gt;5&lt;/sup&gt;And the light shineth in darkness; and the darkness comprehended it not.

Congratulations on reciting your first few sentences in Koine Greek!

==Quoting Scripture==
Authors can accidentally misquote the words of a verse, miss punctuation, or give the wrong reference; some can quote from different versions of the Bible in their works due to how the texts render a passage, though they must state what version they're quoting: [Book Name] [Chapter]:[Verse(s)] [Translation Author]

An author who quoted from only one Bible version doesn't need to restate it after all references (e.g., the line on the copyright page can simply state that &quot;All Scripture quotations are taken from…&quot;), though even just one verse from another version needs to be noted.

Publishers have varying quoting guidelines: some use the Chicago Manual of Style, others the Christian Writer's Manual of Style. Moreover, they write references (hyphen, comma, or en-dash between verse spans), Biblical book names (Deut., Deu., or Dt.), and the capitalizations of various scriptural words (temple or Temple; rapture or Rapture) differently. Some publishers use the lowercase letters a or b to indicate in the reference that the author is using the first or second part of a verse (Psalm 139:14a).

===Quote the version correctly.===
* “Be careful, for writing books is endless” (Ecclesiastes 12:12, NLT).
* “Of making many books there is no end” (Ecclesiastes 12:12, NIV).
* “There’s no end to the publishing of books” (Ecclesiastes 12:12 MSG).

Be consistent with the various style guides of your publisher. Use your style sheet to make note of how you write the references (1:3, 4 vs. 1:3-4) and whether you’re writing Bible book names out in full or abbreviating them (and how you abbreviate them).

By far, the biggest key to quoting Scripture is quoting it accurately. '''Read the verses carefully''', word by word. If the author has copied verses from an electronic Bible like Bible Gateway, still recheck it. Read each verse aloud, comparing punctuation too. With an electronic Bible, minimize the document and the electronic quotes to avoid flipping between screens.

===Be sure that &quot;L&lt;small&gt;ORD&lt;/small&gt;&quot; or &quot;&lt;small&gt;GOD&lt;/small&gt;&quot; is in small caps where appropriate.===

Old Testament references to &quot;L&lt;small&gt;ORD&lt;/small&gt;&quot; or &quot;&lt;small&gt;GOD&lt;/small&gt;&quot; are in small caps, as this formatting shows that the translated word was Hebrew יהוה (Yahweh), contrary to other names of God like Elohim or Adonai.

===Italicize correctly.===

Some OT texts, but often not electronic bibles, italicize words that have been added for readability in English but are absent from source texts: &quot;And God called the dry ''land'' Earth; and the gathering together of the waters called the Seas: and God saw that ''it was'' good&quot; (Genesis 1:10 KJV). Foreign language must also be italicized: &quot;About three in the afternoon Jesus cried out in a loud voice, '''Eli, Eli, lema sabachthani?''&lt;nowiki&gt;'&lt;/nowiki&gt; (which means 'My God, my God, why have you forsaken me?')&quot; (Matthew 27:46 NIV).

===Use quotation marks accurately.===

Quotes less than five lines long are in quotation marks: “But God showed his great love for us by sending Christ to die for us while we were still sinners” (Romans 5:8 NLT); otherwise, they are put in a block:
 We can rejoice, too, when we run into problems and trials, for we know that they help us develop endurance. And endurance develops strength of character, and character strengthens our confident hope of salvation. And this hope will not lead to disappointment. For we know how dearly God loves us, because he has given us the Holy Spirit to fill our hearts with his love. When we were utterly helpless, Christ came at just the right time and died for us sinners. (Romans 5:3–6 NLT)

Nested quotations marks become single quotes: “Jesus told him, ‘I am the way, the truth, and the life’” (John 14:6 NLT); however, this rule does not apply to block quotes, as there are no open or close quotes around it. Also, capitalize letters at the beginning or lowercase letters that you incorporated into a sentence you wrote.

===Omit verse numbers.===

When quoting more than one verse, whether running into your text or in a block quote, you ''can'' exclude the verse numbers of each one.

“Versification” refers to Bibles where each verse starts in a new paragraph (i.e., the verses aren't run together to create paragraphs) due to a stylistic decision by the publisher. When copying from such Bibles, you don't need to keep the verses separate.

The same rule applies to quoting poetry in Scripture: You can preserve the poetic lines or type the poetry into a paragraph. Also note that when presenting poetry together in paragraph lines, you may need to lowercase some letters that were originally capitalized at the beginning of each new line.

{{BookCat}}</text>
      <sha1>gotbnh058vmatxw4wp7p6pi7j3nyx5e</sha1>
    </revision>
    <revision>
      <id>4675790</id>
      <parentid>4675788</parentid>
      <timestamp>2026-10-13T06:29:20Z</timestamp>
      <contributor>
        <username>It-is-Truly-Meet</username>
        <id>3624460</id>
      </contributor>
      <minor />
      <comment>&lt;sup&gt;4&lt;/sup&gt; was joined to &quot;In&quot; for consistency.</comment>
      <origin>4675790</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="5944" sha1="gic3r768lkr7axd585227wp8oug7xsl" xml:space="preserve">Try reading this out loud and check your pronunciation with the recording provided below. 

 &lt;sup&gt;1&lt;/sup&gt;Ἐν ἀρχῇ ἦν ὁ λόγος, καὶ ὁ λόγος ἦν πρὸς τὸν θεόν, καὶ θεὸς ἦν ὁ λόγος. &lt;sup&gt;2&lt;/sup&gt;οὗτος ἦν ἐν ἀρχῇ πρὸς τὸν θεόν. &lt;sup&gt;3&lt;/sup&gt;πάντα δι' αὐτοῦ ἐγένετο, καὶ χωρὶς αὐτοῦ ἐγένετο οὐδὲ ἕν ὃ γέγονεν. &lt;sup&gt;4&lt;/sup&gt;ἐν αὐτῷ ζωὴ ἦν, καὶ ἡ ζωὴ ἦν τὸ φῶς τῶν ἀνθρώπων &lt;sup&gt;5&lt;/sup&gt;καὶ τὸ φῶς ἐν τῇ σκοτίᾳ φαίνει, καὶ ἡ σκοτία αὐτὸ οὐ κατέλαβεν.
{{Audio|A Reading of John 1 1-5.ogg}}
----
 &lt;sup&gt;1&lt;/sup&gt;In the beginning was the Word, and the Word was with God, and the Word was God. &lt;sup&gt;2&lt;/sup&gt;The same was in the beginning with God. &lt;sup&gt;3&lt;/sup&gt;All things were made by him; and without him was not any thing made that was made. &lt;sup&gt;4&lt;/sup&gt;In him was life; and the life was the light of men. &lt;sup&gt;5&lt;/sup&gt;And the light shineth in darkness; and the darkness comprehended it not.

Congratulations on reciting your first few sentences in Koine Greek!

==Quoting Scripture==
Authors can accidentally misquote the words of a verse, miss punctuation, or give the wrong reference; some can quote from different versions of the Bible in their works due to how the texts render a passage, though they must state what version they're quoting: [Book Name] [Chapter]:[Verse(s)] [Translation Author]

An author who quoted from only one Bible version doesn't need to restate it after all references (e.g., the line on the copyright page can simply state that &quot;All Scripture quotations are taken from…&quot;), though even just one verse from another version needs to be noted.

Publishers have varying quoting guidelines: some use the Chicago Manual of Style, others the Christian Writer's Manual of Style. Moreover, they write references (hyphen, comma, or en-dash between verse spans), Biblical book names (Deut., Deu., or Dt.), and the capitalizations of various scriptural words (temple or Temple; rapture or Rapture) differently. Some publishers use the lowercase letters a or b to indicate in the reference that the author is using the first or second part of a verse (Psalm 139:14a).

===Quote the version correctly.===
* “Be careful, for writing books is endless” (Ecclesiastes 12:12, NLT).
* “Of making many books there is no end” (Ecclesiastes 12:12, NIV).
* “There’s no end to the publishing of books” (Ecclesiastes 12:12 MSG).

Be consistent with the various style guides of your publisher. Use your style sheet to make note of how you write the references (1:3, 4 vs. 1:3-4) and whether you’re writing Bible book names out in full or abbreviating them (and how you abbreviate them).

By far, the biggest key to quoting Scripture is quoting it accurately. '''Read the verses carefully''', word by word. If the author has copied verses from an electronic Bible like Bible Gateway, still recheck it. Read each verse aloud, comparing punctuation too. With an electronic Bible, minimize the document and the electronic quotes to avoid flipping between screens.

===Be sure that &quot;L&lt;small&gt;ORD&lt;/small&gt;&quot; or &quot;&lt;small&gt;GOD&lt;/small&gt;&quot; is in small caps where appropriate.===

Old Testament references to &quot;L&lt;small&gt;ORD&lt;/small&gt;&quot; or &quot;&lt;small&gt;GOD&lt;/small&gt;&quot; are in small caps, as this formatting shows that the translated word was Hebrew יהוה (Yahweh), contrary to other names of God like Elohim or Adonai.

===Italicize correctly.===

Some OT texts, but often not electronic bibles, italicize words that have been added for readability in English but are absent from source texts: &quot;And God called the dry ''land'' Earth; and the gathering together of the waters called the Seas: and God saw that ''it was'' good&quot; (Genesis 1:10 KJV). Foreign language must also be italicized: &quot;About three in the afternoon Jesus cried out in a loud voice, '''Eli, Eli, lema sabachthani?''&lt;nowiki&gt;'&lt;/nowiki&gt; (which means 'My God, my God, why have you forsaken me?')&quot; (Matthew 27:46 NIV).

===Use quotation marks accurately.===

Quotes less than five lines long are in quotation marks: “But God showed his great love for us by sending Christ to die for us while we were still sinners” (Romans 5:8 NLT); otherwise, they are put in a block:
 We can rejoice, too, when we run into problems and trials, for we know that they help us develop endurance. And endurance develops strength of character, and character strengthens our confident hope of salvation. And this hope will not lead to disappointment. For we know how dearly God loves us, because he has given us the Holy Spirit to fill our hearts with his love. When we were utterly helpless, Christ came at just the right time and died for us sinners. (Romans 5:3–6 NLT)

Nested quotations marks become single quotes: “Jesus told him, ‘I am the way, the truth, and the life’” (John 14:6 NLT); however, this rule does not apply to block quotes, as there are no open or close quotes around it. Also, capitalize letters at the beginning or lowercase letters that you incorporated into a sentence you wrote.

===Omit verse numbers.===

When quoting more than one verse, whether running into your text or in a block quote, you ''can'' exclude the verse numbers of each one.

“Versification” refers to Bibles where each verse starts in a new paragraph (i.e., the verses aren't run together to create paragraphs) due to a stylistic decision by the publisher. When copying from such Bibles, you don't need to keep the verses separate.

The same rule applies to quoting poetry in Scripture: You can preserve the poetic lines or type the poetry into a paragraph. Also note that when presenting poetry together in paragraph lines, you may need to lowercase some letters that were originally capitalized at the beginning of each new line.

{{BookCat}}</text>
      <sha1>gic3r768lkr7axd585227wp8oug7xsl</sha1>
    </revision>
  </page>
  <page>
    <title>On 2D Inverse Problems</title>
    <ns>0</ns>
    <id>279393</id>
    <revision>
      <id>4675775</id>
      <parentid>4675303</parentid>
      <timestamp>2026-10-13T01:35:32Z</timestamp>
      <contributor>
        <username>~2026-54854-94</username>
        <id>3628299</id>
      </contributor>
      <comment>progress...</comment>
      <origin>4675775</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1189" sha1="l35vmj5bim7us0bfg1nmntqapxtyd0w" xml:space="preserve">[[File:Book cover.jpg|thumbnail|DVD cover]]
&lt;!-- EDIT BELOW THIS LINE --&gt;
'''ON VERSE PROBLEMS'''
DVD version
== [[On 2D Inverse Problems/Preface|Pretty preface]] ==
== [[On 2D Inverse Problems/Body|Theory &amp; &quot;no problems...&quot;]] ==
== [[On 2D Inverse Problems/Bibliography|Bubbles]] == 
=== [[On 2D Inverse Problems/About the author|&quot;Who is talking?&quot;]] ===
== [[On 2D Inverse Problems/Ai|The volume II: AI DVD!?]] ==
=== [[On 2D Inverse Problems/Papirus|Papirus]] ===
=== [[On 2D Inverse Problems/Rotation|Spinning Spectrum]] ===
=== [[On 2D Inverse Problems/Spatial|Spatial Spectrum]] ===
== [[On 2D Inverse Problems/Characteristic|Characteristic: companion and circulant]] ==
=== [[On 2D Inverse Problems/Area|Energy Integral]] ===
=== [[On 2D Inverse Problems/Orthogonal|Gravity is Optional]] ===
=== [[On 2D Inverse Problems/Echo|Echo]] ===
== [[On 2D Inverse Problems/Private|The volume III: Piracy!?]] ==
=== [[On 2D Inverse Problems/4|Ghost Spiderweb]] ===
=== [[On 2D Inverse Problems/5|Shape-shifting]] ===
=== [[On 2D Inverse Problems/6|Six colors suffices surface]] ===
{{Shelves|Mathematical collections}}
{{Alphabetical|2}}
{{status|75%}}
{{reading level|Beginner}} 
{{BookCat}}</text>
      <sha1>l35vmj5bim7us0bfg1nmntqapxtyd0w</sha1>
    </revision>
  </page>
  <page>
    <title>On 2D Inverse Problems/Medial graphs</title>
    <ns>0</ns>
    <id>279649</id>
    <revision>
      <id>4675772</id>
      <parentid>3091489</parentid>
      <timestamp>2026-10-13T01:10:44Z</timestamp>
      <contributor>
        <username>DVD206</username>
        <id>724793</id>
      </contributor>
      <minor />
      <comment>grey hole</comment>
      <origin>4675772</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3875" sha1="7xkj25jobb3ebl4bqmvj0j5rowhfxb3" xml:space="preserve"> The following construction plays an important role in study of the graphs properly embedded into surfaces. One considers an embedded into a surface (2D manifold) finite graph w/vertices each w/four neighbors. The union of edges of such graph is equal to a union of closed curves on the surface, called '''geodesics'''. The faces of the graph can be two-colored. 

[[File:Morphedchessboard(1).jpg|thumb|Example of a medial graph on a surface]]

 The corresponding graph ''G'' and its dual ''G&lt;sup&gt;*&lt;/sup&gt;'' can be obtained by putting vertices in all faces of the same color and connecting two vertices by an edge if the corresponding faces of the '''medial graph''' ''M(G)'' have a common corner. Note that ''M(G)=M(G&lt;sup&gt;*&lt;/sup&gt;)''. The construction can be modified accordingly for the case of an embedded graph w/boundary by allowing vertices of the medial graph to have one neighbor.

The following transformations of the geodesics of the medial graph ''M(G)'' are similar to the '''Reidemeister moves''' of the knot theory. They correspond to the ''Y-Δ'' transformations of the graph ''G'' and ''G&lt;sup&gt;*&lt;/sup&gt;''.

[[File:Geodesics moves (1).jpg|450px|center |The three moves of geodesics curves]]

The following matrix consists of the distances (the fewest number of jumps across the geodesics or the edge distance in ''M&lt;sup&gt;*&lt;/sup&gt;(G)'') b/w boundary faces of the medial graph below.

:&lt;math&gt;
\begin{pmatrix}
 0 &amp; 1  &amp; 2 &amp; 3 &amp; 2 &amp; 3 &amp; 2 &amp; 1 \\
 1 &amp; 0  &amp; 1 &amp; 2 &amp; 3 &amp; 4 &amp; 3 &amp; 2 \\
 2 &amp; 1  &amp; 0 &amp; 1 &amp; 2 &amp; 3 &amp; 4 &amp; 3 \\
 3 &amp; 2  &amp; 1 &amp; 0 &amp; 1 &amp; 2 &amp; 3 &amp; 4 \\
 2 &amp; 3  &amp; 2 &amp; 1 &amp; 0 &amp; 1 &amp; 2 &amp; 3 \\
 3 &amp; 4  &amp; 3 &amp; 2 &amp; 1 &amp; 0 &amp; 1 &amp; 2 \\
 2 &amp; 3  &amp; 4 &amp; 3 &amp; 2 &amp; 1 &amp; 0 &amp; 1 \\
 1 &amp; 2  &amp; 3 &amp; 4 &amp; 3 &amp; 2 &amp; 1 &amp; 0
\end{pmatrix}
&lt;/math&gt;
[[File:Medial graphs (1).jpg|center|500px |Two examples of boundary isometric medial graphs with 4 and 5 geodesics]]

 '''Exercise (*).''' Prove that the distances between boundary faces of an embedded medial graph are invariant under the geodesics moves.

The geodesics of the medial graph form an arrangement of '''pseudo-lines''' if 

* none of them intersect itself
* none of them are closed
* no two of them intersect more than once

 '''Exercise (***).''' Prove that ''(a)'' one can recover a planar medial graph ''M(G)'', up to the moves, from the distances between its boundary faces, ''(b)'' every planar medial graph ''M(G)'' can be moved into an arrangement of pseudo-lines without changing the distance matrix.

(Hint). Look for the pattern
:&lt;math&gt;
\begin{pmatrix}
k+1 &amp; k \\
k &amp; k+1
\end{pmatrix}
&lt;/math&gt;
in the matrix of boundary distances. See [PU] for a continuous analog of the boundary distance rigidity result. 

The following min-cut max-flow result was formulated w/help of Derek Jerina, a student of REU summer school on inverse problems at the University of Washington.

 '''Exercise (**).''' Prove that the ranks of submatrices of the matrix of the Dirichlet-to-Neumann operator of a planar graph w/natural boundary determine the shortest distances between the boundary faces of its medial graph, and therefore determine the planar graph up to a finite sequence of [[On 2D Inverse Problems/Y-Δ and star-mesh transforms|Y-Δ transformations]]. (Hint.) It follows from the determinant identity in the section [[On 2D Inverse Problems/Special matrices| Special matrices]] that the ranks of the submatrices count the numbers of disjoint paths connecting boundary nodes of the planar graph.

It was proved in [DeV1], [DeV2] and [CIM] that if the medial graph of a planar network w/natural boundary is an arrangement of pseudo-lines then the conductivities of its edges are uniquely determined by its Dirichlet-to-Neumann operator and can be found by a layer stripping algorithm.

{{BookCat}}The geodesics of the medial graph give natural event horizon for harmonic/analytic continuation of functions on the vertices of the original graph...</text>
      <sha1>7xkj25jobb3ebl4bqmvj0j5rowhfxb3</sha1>
    </revision>
  </page>
  <page>
    <title>On 2D Inverse Problems/Special matrices</title>
    <ns>0</ns>
    <id>280574</id>
    <revision>
      <id>4675771</id>
      <parentid>3116390</parentid>
      <timestamp>2026-10-13T01:06:55Z</timestamp>
      <contributor>
        <username>DVD206</username>
        <id>724793</id>
      </contributor>
      <minor />
      <comment>self-aware</comment>
      <origin>4675771</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="6051" sha1="1gvca8se0zrsg4s5pqulx6j0iupamh9" xml:space="preserve">
An important object containing information about a weighted graph ''G(V,E,w)'' is its '''Laplacian matrix'''. Given a numbering of the vertices of the graph, it's an ''n'' by ''n'' square matrix ''L&lt;sub&gt;G&lt;/sub&gt;'', where ''n'' is the number of vertices in the graph, with the entries:
: &lt;math&gt;l_{kl}:=
\begin{cases}
\sum_{v_k \rightarrow v_l} w_{kl} \mbox{  if}\ k = l, \\
-w_{kl} \mbox{  if}\ v_k \rightarrow v_l, \\
0,  \mbox{  otherwise,}
\end{cases}
&lt;/math&gt;

where ''v''&lt;sub&gt;k&lt;/sub&gt; → ''v''&lt;sub&gt;l&lt;/sub&gt; means that there is a directed edge from vertex ''v''&lt;sub&gt;k&lt;/sub&gt; to the vertex ''v''&lt;sub&gt;l&lt;/sub&gt;, and where ''w'' is the weight function.

:'''Exercise (*)'''. Given a directed graph ''G'' without cycles, prove that one can number its vertices so that the corresponding Laplacian matrix ''L&lt;sub&gt;G&lt;/sub&gt;'' is triangular.

Given a weighted graph with boundary it is often convenient to number its boundary vertices first and to write its Laplacian matrix in the block form. 
: &lt;math&gt;
L_G = 
\begin{pmatrix}
A &amp; B \\
C &amp; D
\end{pmatrix}
&lt;/math&gt;
&lt;!--
:'''Exercise (*).''' Prove that a function/vector ''u'' is harmonic at the interior nodes of a graph ''G'' if 

:&lt;math&gt;
u|_{int G} = -D^{-1}Cu|_{\partial G}.
&lt;/math&gt;

Let &lt;math&gt;M=\begin{pmatrix} A &amp; B \\ C &amp; D \end{pmatrix}&lt;/math&gt;

be a block matrix with an invertible square block ''D''.
--&gt;
The '''Schur complement''' of the matrix &lt;math&gt;L_G&lt;/math&gt; w/respect of the invertible block ''D''  is the matrix &lt;math&gt; L_G/D = A-BD^{-1}C.&lt;/math&gt;
&lt;!--
The  (a multilinear function in the rows and columns) of a square ''n'' by ''n'' matrix ''M'' is:

:&lt;math&gt;\det M = \sum_{\sigma \in S_n} \sgn(\sigma) \prod_{k=1}^n M_{k,\sigma_k}.&lt;/math&gt;
 --&gt;
:'''Exercise (*).''' Prove the following determinant identity:&lt;math&gt;\det L_G = \det(L_G/D) \det D.&lt;/math&gt;

The following matrix ''W(G)'' consisting of random walk exiting probabilities (sums over weighted paths in a graph) plays an important role as boundary measurement for inverse problems. Suppose a weighted graph ''G'' has ''N'' boundary nodes, then the ''kl'' 'th entry of the ''N'' by ''N'' matrix equals to the probability that the first boundary vertex, that a particle starting its random walk at the boundary vertex ''v&lt;sub&gt;k&lt;/sub&gt;'' occupies, is the boundary vertex ''v&lt;sub&gt;l&lt;/sub&gt;''.
For a finite connected graph the columns of the matrix ''W(G)'' add up to ''1''.

:'''Exercise (**).''' Derive an explicit formula for the matrix &lt;math&gt;W_G&lt;/math&gt; in terms of the blocks of Laplace matrix &lt;math&gt;L_G&lt;/math&gt;of the graph ''G'': &lt;math&gt;W_G = I - D_A^{-1}(A - BD^{-1}C).&lt;/math&gt;

:'''Exercise (***).''' Prove the following expansion formulas for entries and blocks of the matrix ''W(G)'', 

* for two boundary vertices ''p&lt;sub&gt;k&lt;/sub&gt;'' and ''p&lt;sub&gt;l&lt;/sub&gt;'' of a graph ''G'' 
: &lt;math&gt; 
w_{kl} = \sum_{v_k\xrightarrow[]{path} v_l}\prod_{e=(p,q)\in path}w(e)/l_{pp},
&lt;/math&gt;
Hint: use the Leibniz definition of the determinant

* for two distinct boundary vertices ''v&lt;sub&gt;k&lt;/sub&gt;'' and ''v&lt;sub&gt;l&lt;/sub&gt;'' of a graph ''G''
:  &lt;math&gt;
w_{kl}\det D = \frac{1}{l_{kk}}\sum_{v_k\xrightarrow{path}v_l}\prod_{e\in path}l(e)\det D(\tilde{path},\tilde{path}),
&lt;/math&gt;

where &lt;math&gt; \tilde{path} = V-(\partial G\cup path).&lt;/math&gt; 

* for two disjoint subsets of boundary vertices ''P'' and ''Q'' of size ''n'' of a graph ''G'', see [6],[7] and [14]
: &lt;math&gt;
\det W(P,Q) \det D = \pm\frac{\sum_{\sigma\in S_{n}}(-1)^{\sgn(\sigma)}\sum_{p_k\xrightarrow{paths}q_{\sigma_k}}\prod_{e\in paths}l(e)\det D(\tilde{paths},\tilde{paths})}{\prod_{p\in P}l_{pp}},
&lt;/math&gt;

where 
: &lt;math&gt; \tilde{paths} = V-(\partial G\cup paths).&lt;/math&gt;

The exercises above provide a bridge b/w connectivity property of graph ''G'' and ranks of submatrices of its Laplacian matrix ''L(G)'' and the matrix of hitting probabilities ''W(G)''.

:'''Exercise (*).''' Let ''G'' be a planar graph w/natural boundary, numbered circulary. Let ''P'' and ''Q'' be two non-interlacing subsets of boundary nodes of size ''n''. Prove that
: &lt;math&gt; (-1)^{\frac{n(n+1)}{2}}\det\Lambda_G(P,Q) \ge 0,
&lt;/math&gt;

w/the strict inequality iff there is a disjoint set of paths from ''P'' to ''Q''.

:'''Exercise (*).''' Show that the numbers of paths in the following graph are equal to the binomial coefficients. 
[[File:Pascal paths (1).jpg|300px|center| The numbers of the paths of the graph are binomial coefficients]]

Gluing the graphs w/out loops corresponds to multiplication of the weighted paths matrices. 

:'''Exercise (**).''' Use the result of the previous exercise to it to prove the following '''Pascal triangle''' identity, see[13],

:&lt;math&gt;
\begin{pmatrix}
 1     &amp; 1  &amp;  1 &amp; 1 &amp; \ldots \\
 1     &amp; 2  &amp;  3 &amp; 4 &amp; \ldots \\
 1     &amp; 3  &amp;  6 &amp; \ldots &amp; \ddots \\
 1     &amp; 4  &amp; 10 &amp; \ldots &amp; \ddots \\
 1     &amp; \ldots  &amp; \ldots &amp; \ddots &amp; \ddots \\
\end{pmatrix}
 = 
\begin{pmatrix}
 1     &amp; 0  &amp;  0 &amp; 0 &amp; \ldots \\
 1     &amp; 1  &amp;  0 &amp; 0 &amp; \ldots \\
 1     &amp; 2  &amp;  1 &amp; 0 &amp; \ddots \\
 1     &amp; 3  &amp;  3 &amp; \ldots &amp; \ddots \\
 1     &amp; \ldots  &amp; \ldots &amp; \ddots &amp; \ddots \\
\end{pmatrix}
\begin{pmatrix}
 1     &amp; 1  &amp;  1 &amp; 1 &amp; \ldots \\
 0     &amp; 1  &amp;  2 &amp; 3 &amp; \ldots \\
 0     &amp; 0  &amp;  1 &amp; 3 &amp; \ddots \\
 0     &amp; 0  &amp;  0 &amp; \ldots &amp; \ddots \\
 0     &amp; \ldots  &amp; \ldots &amp; \ddots &amp; \ddots \\
\end{pmatrix}.
&lt;/math&gt;
&lt;!--
'''Exercise (***).''' Give a proof of a [http://en.wikipedia.org/wiki/Menger%27s_theorem Menger's theorem] based on the results of the exercise above: Let ''G'' be a finite  graph and ''p'' and ''q'' two vertices that are not neighbors. Then the size of the minimum vertex cut for ''p'' and ''q'' (the minimum number of vertices whose removal disconnects ''p'' and ''q'') is equal to the maximum number of pairwise vertex-independent paths from ''p'' to ''q''.--&gt;

{{BookCat}}

# the self-similar pattern lets you treat the entire system through its core parameters.

Whether you look at it as a repeating algebraic seed or a self-similar grid, it's the mathematical backbone of how complex, large-scale systems can be completely understood by looking at their foundational building blocks!?</text>
      <sha1>1gvca8se0zrsg4s5pqulx6j0iupamh9</sha1>
    </revision>
  </page>
  <page>
    <title>OpenSSH/Cookbook/Tunnels</title>
    <ns>0</ns>
    <id>281762</id>
    <revision>
      <id>4675738</id>
      <parentid>4659570</parentid>
      <timestamp>2026-10-12T13:55:29Z</timestamp>
      <contributor>
        <username>Larsnooden</username>
        <id>430753</id>
      </contributor>
      <minor />
      <comment>typo</comment>
      <origin>4675738</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="23895" sha1="p8xt3efb79yu4dn48zdhfcaws8brp3g" xml:space="preserve">&lt;noinclude&gt;{{simple chapter navigation|previous=The Client Configuration File|next=Automated Backup}}&lt;/noinclude&gt;
&amp;nbsp;

In tunneling, or port forwarding, a local port is connected to a port on a remote host or vice versa.  So connections to the port on one machine are in effect connections to a port on the other machine.  

The [http://man.openbsd.org/ssh.1 ssh(1)] options '''-f''' (go to background), '''-N''' (do not execute a remote program) and '''-T''' (disable pseudo-tty allocation) can be useful for connections that are used only for creation of tunnels.  

&lt;noinclude&gt;__TOC__&lt;/noinclude&gt;

==Tunneling==

[[File:Wikibook-diagram-SSH-forwarding-basic.png|thumb|Basic SSH Forwarding]]

In regular port forwarding, connections to a local port are forwarded to a port on a remote machine.  This is a way of securing an insecure protocol or of making a remote service appear as local.  Here we forwarded VNC in two steps.  First make the tunnel:  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -L 5901:localhost:5901 -l fred desktop.example.org
&lt;/syntaxhighlight&gt;

In that way connections on the local machine made to the forwarded port will in effect be connecting to the remote machine.  

Multiple tunnels can be specified at the same time.  The tunnels can be of any kind, not just regular forwarding.  See the next section below for reverse tunnels.  For dynamic forwarding see the section [[OpenSSH/Cookbook/Proxies_and_Jump_Hosts|Proxies and Jump Hosts]].

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -L 5901:localhost:5901 \
      -L 5432:localhost:5432 \
      -l fred desktop.example.org
&lt;/syntaxhighlight&gt;

If a connection is only used to create a tunnel, then it can be told not to execute any remote programs ('''-N'''), making it a non-interactive session, and also to drop to the background ('''-f''').  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -fN -L 3128:localhost:3128 -l fred server.example.org
&lt;/syntaxhighlight&gt;

Note that '''-N''' will work even if the '''authorized_keys''' forces a program using the '''command=&quot;...&quot;''' option.  So a connection using '''-N''' will stay open instead of running a program and then exiting.

The three connections above could be saved in the SSH client's configuration file, '''~/.ssh/config''' and even given shortcuts.

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Host desktop desktop.example.org
        HostName desktop.example.org
        User fred
        LocalForward 5901 localhost:5901

Host postgres
        HostName desktop.example.org
        User fred
        LocalForward 5901 localhost:5901
        LocalForward 5432 localhost:5432

Host server server.example.org
        HostName server.example.org
        User fred
        ExitOnForwardFailure no
        LocalForward 3128 localhost:3128

Host *
        ExitOnForwardFailure yes
&lt;/syntaxhighlight&gt;

With those settings, the tunnels listed are added automatically when connecting to ''desktop'', ''desktop.example.org'', ''postgres'', ''server'', or ''server.example.org''.  The catchall configuration at the end applies to any of the above hosts which have not already set '''ExitOnForwardFailure''' to 'no' and the client will refuse to connect if a tunnel cannot be made.  The first obtained value for any given configuration directive will be used, but the file's contents can be overridden with run-time options passed on the command line. 

===Tunneling Via A Single Intermediate Host===

Tunneling can go via one intermediate host to reach a second host, and the latter does not need to be on a publicly accessible network.  However, the target port on the second remote machine does have to be accessible on the same network as the first.  Here, ''192.168.0.101'' and ''bastion.example.org'' must be on the same network and, in addition, ''bastion.example.org'' has to be directly accessible to the client machine running '''ssh(1)'''.  So, port 80 on ''192.168.0.101'' has to be available to the machine ''bastion.example.org''.

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -fN -L 1880:192.168.0.101:80 -l fred bastion.example.org
&lt;/syntaxhighlight&gt;

Thus, once the tunnel is made, to connect to port 80 on ''192.168.2.101'' via the host ''bastion.example.org'', connect to port 1880 on ''localhost''.  This way works for one or two hosts.  It is also possible to chain multiple hosts, using different methods.  


====Securing a Hop, Tunneling Via One Or More Intermediate Hosts====

Here, the idea is to limit the ability of a group of users to the bare minimum needed to pass through a jump host yet still be able to forward ports onward to other machines.  If the account is sufficiently locked down then the bastion can only be used for forwarding and not shell access, scripts, or even SFTP.  The following settings on the bastion host in [http://man.openbsd.org/sshd_config.5 sshd_config(5)] prevent either shell access or SFTP but still allow port forwarding.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Match Group tunnelers
        ForceCommand /bin/false
        PasswordAuthentication no
        ChrootDirectory %h
        PermitTTY no
        X11Forwarding no
        AllowTcpForwarding yes
        PermitTunnel no
        Banner none
&lt;/syntaxhighlight&gt;

Note that their home directories, but not the files within them, must be owned by root and writable by only root because of the '''ChrootDirectory''' configuration directive there in [http://man.openbsd.org/sshd_config.5 sshd_config(5)].  Also, because of the '''PasswordAuthentication''' configuration directive keys will have to be set up in the home directory in '''~/.ssh/authorized_keys''', if an alternate location is not already configured.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -N -L 9980:localhost:80 -J fred@bastion.example.org fred@192.168.79.124
&lt;/syntaxhighlight&gt;

In that way port 9980 on the client is directed via ''bastion.example.org'' through to port 80 on ''192.168.79.124''.  

In cases where the bastion must have a reverse tunnel from the inner host in order to reach it, then the same method works but with the prerequisite of a reverse tunnel from the inner host to the bastion first.  

For more about passing through intermediate computers, see the Cookbook section on [[OpenSSH/Cookbook/Proxies_and_Jump_Hosts|Proxies and Jump Hosts]].

===Finding The Process ID (PID) Of A Tunnel Which Is In The Background===

When a tunneled connection is sent to the background execution using the '''-f''' option for the client, there is not currently an automatic way to find the process ID (PID) of the task sent to the background.  Background processes are often used for port forwarding or reverse port forwarding.  Here is an example of port forwarding, also called tunneling.  The connection is made and then the client goes away, leaving the tunnel available in the background, connecting port 2194 on the local host to port 194 of the remote system's local host.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -Nf -L 2194:localhost:194 fred@203.0.113.214
&lt;/syntaxhighlight&gt;

The special '''$!''' variable remains empty, even if '''$?''' reports success or failure of the action.  The reason is that the shell's job control did not put the client into the background.  Instead the client runs in the foreground for a moment and then exits normally, after leaving a different process to run in the background via a fork.  The process ID of the original client vanishes since that client is gone.  

Finding the process ID usually takes at least two steps.  Some of the ways to retroactively identify the process involve trying [http://man.openbsd.org/ps.1 ps(1)] and rummaging through the output for all that account's processes, but that is unnecessary effort.  If the background SSH client is the most recent one, then [http://man.openbsd.org/pgrep.1 pgrep(1)] can be used, or else the output needs to be comma delimited and fed into [http://man.openbsd.org/ps.1 ps(1)] via [http://man.openbsd.org/xargs.1 xargs(1)] or process substitution.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ps uw | less

$ pgrep -n -x ssh

$ pgrep -d, -x ssh | xargs ps -p

$ ps -p $(pgrep -d, -x ssh)
&lt;/syntaxhighlight&gt;

Some variations on the above might be needed depending on operating system if the '''-d''' option is not supported.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ pgrep -x ssh | xargs -n 1 ps -o user,pid,ppid,args -p | awk 'NR==1 || $3==1'
USER       PID  PPID COMMAND
fred     97778     1 ssh -fN -L 8008:localhost:80 fred@203.0.113.8
fred     14026     1 ssh -fN -L 8183:localhost:80 fred@203.0.113.183
fred     79522     1 ssh -fN -L 8228:localhost:80 fred@203.0.113.228
fred     49773     1 ssh -fN -L 8205:localhost:80 203.0.113.205
&lt;/syntaxhighlight&gt;

Either way, note that all the connections running in the background have a Parent Process ID (PPID) of 1, the process control initialization system for the operating system.

Being aware of this shortcoming, a proactive approach can be used with the '''ControlMaster''' and '''ControlPath''' configuration directives in order to leave a socket to read to get the background task's process ID.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -M -S ~/.ssh/sockets/pid.%C -fN -L 5901:localhost:5901 fred@203.0.113.122

$ ssh -S ~/.ssh/sockets/pid.%C -O check 203.0.113.122
&lt;/syntaxhighlight&gt;

The '''-M''' option causes the client to go into Master mode for multiplexing using the socket designated by the '''-S''' option.  Then, after '''-f''' forks the client into the background,  The control command ''check'' will then use the socket to check that the master process is running and report the Process ID.  

It is a good idea for the socket to be in an isolated directory not readable or writable by other accounts.  Aside from the complexity, a noticeable down side is that it can be possible for the socket to be reused for additional connections.  See the Cookbook section on [[OpenSSH/Cookbook/Multiplexing|Multiplexing]] for more about the risks and additional uses.

==Reverse Tunneling==

[[File:Wikibook-diagram-SSH-forwarding-reverse-basic.png|thumb|Basic SSH Reverse Forwarding]]

A reverse tunnel forwards connections in the opposite direction of a regular tunnel, that is to say the opposite direction from that which the SSH session is initiated.  With remote forwarding as it is also called, an SSH session begins from the local host to a remote host while a port is forwarded from the remote host to the local host.  There are two stages in using reverse tunneling, see the diagram: first, connect from endpoint ''198.51.100.56'' to endpoint ''203.0.113.8'' using SSH with remote forwarding enabled; second, connect other systems to the designated port on endpoint ''203.0.113.8'' and that port is then forwarded to endpoint ''198.51.100.56''.  

So while the originating system initiated the SSH connection to the remote system, the connections to the designated port on ''203.0.113.8'' are sent over to ''198.51.100.56'' over the reverse tunnel.  Once the SSH connection is made, the reverse tunnel can be used from the remote system the same as a regular tunnel, even though the originating system initiated the SSH connection.  

Remote forwarding is a method which can be used to forward SSH over SSH in order to work on an otherwise inaccessible system, such as an always-on SBC behind a home router.  First, open an SSH session from the inaccessible system to another which is accessible including a designated reverse tunnel.  In this example, while the SSH connection is from a local system (endpoint A) to a remote system (endpoint B), that connection contains a reverse tunnel from port 2022 on that remote system (endpoint B) to port 22 over on the local system:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -fN -R 2022:localhost:22 -l fred server.example.org
&lt;/syntaxhighlight&gt;

Lastly, using the example above, a connection is made on the remote machine, ''server.example.org'', to the reverse tunnel connection on port 2022.  Thus, even though the connection is made to port 2022 on ''localhost'' on ''server.example.org'', the packets end up over on port 22 on the system which initiated the SSH initial connection carrying the reverse tunnel.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -p 2022 -l fred localhost
&lt;/syntaxhighlight&gt;

Thus that example allows SSH access to an otherwise inaccessible system via SSH.  SSH goes out, makes a reverse tunnel, then the second system can connect at will to the first via SSH as long as the tunnel persists.  If keys and a loop are used to generate the SSH connection with the remote forwarding then the reverse tunnel can be maintained automatically.  

The next example makes VNC available over SSH from an otherwise inaccessible system via a second system, ''server.example.org''.  Starting from the system with a running VNC server, reverse forward the port for the first VNC display locally to the third VNC display over on ''server.example.org'':

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -fNT -R 5903:localhost:5901 -l fred server.example.org
&lt;/syntaxhighlight&gt;

Then on the system ''server.example.org'', people can connect to that system's ''localhost'' address on its third VNC display and be patched through to the originating system:

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ xvncviewer :3
&lt;/syntaxhighlight&gt;

That also is an example of how the forwarded ports don't have to be the same.  

Remote forwarding can be included in the SSH client's configuration file using the '''RemoteForward''' directive.  See the next subsection for that.  

A common use-case for reverse tunneling is when you have to access a system or service which is behind either NAT or a firewall or both and thus incoming SSH connections are blocked, but you have direct access to a second system outside the firewall which can accept incoming connections.  In such cases it is easy to make a reverse tunnel from the internal system behind the firewall to the second system on the outside.  Once the SSH connection has made the reverse tunnel, to connect to the internal system from outside, other systems can connect to the forwarded port on the remote system.  The remote system on the outside then acts as a relay server to forward connections to the initiating system on the inside.

===Configuring Remote Forwarding Using The Client Configuration File===

The '''RemoteForward''' client configuration directive can be used in [http://man.openbsd.org/ssh_config ssh_config(5)] to establish a reverse tunnel from another system.  The '''ForkAfterAuthentication''' would be '''-f''' and '''SessionType''' would be '''-N''' as run time arguments and, of course, optional in this example which is the same as the first example in the subsection above:

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Host server server.example.org
        User fred
        HostName server.example.org
        ForkAfterAuthentication yes
        SessionType none
        RemoteForward 2022 localhost:22
&lt;/syntaxhighlight&gt;

With that in place over on the other system, one can establish a reverse tunnel from ''server'' by simply connecting to it by entering &lt;code&gt;ssh server&lt;/code&gt;.  Then over on ''server.example.org'', connecting to ''localhost'' on port 2022  will carry through back to the original system on port 22.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Host server server.example.org
        User fred
        HostName server.example.org
        ForkAfterAuthentication yes
        SessionType none
        RequestTTY no
        RemoteForward 5903 localhost:5901
&lt;/syntaxhighlight&gt;

Likewise that duplicates the second example from the subsection above but in the client configuration file instead of using run time arguments.  More about that is covered in the chapter on using [[OpenSSH/Cookbook/The_Client_Configuration_File‎|The&amp;nbsp;Client&amp;nbsp;Configuration&amp;nbsp;File]].

==Adding or Removing Tunnels within an Established Connection==

It is possible to add or remove tunnels, reverse tunnels, and SOCKS proxies to or from an existing connection using escape sequences.  The default escape character is the tilde (~) and the full range of options is described in the manual page for [http://man.openbsd.org/ssh.1 ssh(1)].  Escape sequences only work if they are the first characters entered on a line and followed by a return.  When adding or removing a tunnel to or from an existing connection, '''~C''', the command line is used.  

To add a tunnel in an active SSH session, use the escape sequence to open a command line in SSH and then enter the parameters for the tunnel:

&lt;pre&gt;
~C
L 2022:localhost:22
&lt;/pre&gt;

To remove a tunnel from an active SSH session is almost the same.  Instead of -L, -R, or -D we have -KL, -KR, and -KD plus the port number.  Use the escape sequence to open a command line in SSH and then enter the parameters for removing the tunnel.

&lt;pre&gt;
~C
KL2022
&lt;/pre&gt;

===Adding or Removing Tunnels within a Multiplexed Connection===

There is an additional option for forwarding when multiplexing.   More than one SSH connection can be multiplexed over a single TCP connection.  Control commands can be passed to the master process to add or drop port forwarding to the master process.  

First a master connection is made and a socket path assigned. 

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -S '/home/fred/.ssh/%h:%p' -M server.example.org
&lt;/syntaxhighlight&gt;

Then using the socket path, it is possible to add port forwarding.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -O forward -L 2022:localhost:22 -S '/home/fred/.ssh/%h:%p' fred@server.example.org
&lt;/syntaxhighlight&gt;

Since OpenSSH 6.0 it is possible to cancel specific port forwarding using a control command. 

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -S  &quot;/home/fred/.ssh/%h:%p&quot; -O cancel -L 2022:localhost:22 fred@server.example.org
&lt;/syntaxhighlight&gt;

For more about multiplexing, see the Cookbook section on [[OpenSSH/Cookbook/Multiplexing|Multiplexing]].

==Restricting Tunnels to Specific Ports==

By default, port forwarding will allow forwarding to any port if it is allowed at all.  The way to restrict which ports a user can use in forwarding is to apply the '''PermitOpen''' option on the server side either in the server's configuration or inside the user's public key in '''authorized_keys'''.  For example, with this setting in [http://man.openbsd.org/sshd_config.5 sshd_config(5)] all users can forward only to port 7654 on the server, if they try forwarding:

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
PermitOpen localhost:7654
&lt;/syntaxhighlight&gt;

Multiple ports may be specified on the same line if separated by whitespace.

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
PermitOpen localhost:7654 localhost:3306
&lt;/syntaxhighlight&gt;

If the client tries to forward to a disallowed port, there will be a warning message that includes the text &quot;open failed: administratively prohibited: open failed&quot; while the connection otherwise continues as normal.  However, even if the client has '''ExitOnForwardFailure''' in its configuration a connection will still succeed, despite the warning message.  

However, if shell access is available, it is possible to run other port forwarders, so without further restrictions, '''PermitOpen''' is more of a reminder or recommendation than a restriction.  But for many cases, such a reminder might be enough.  

For reverse tunnels, the '''PermitListen''' option is available instead.  It determines which port on the remote system is available.  So the following, for example, allows &lt;code&gt;ssh -R 2022:localhost:''xxxx''&lt;/code&gt;, where ''xxxx'' can be any available port number at the origin of the reverse tunnel, but only 2022 on the far end of the tunnel.

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
PermitListen localhost:2022
&lt;/syntaxhighlight&gt;

The '''PermitOpen''' or '''PermitListen''' options can be used as part of one or more '''Match''' blocks if forwarding options need to vary depending on various combinations of user, group, client address or network, server address or network, and/or the listening port used by [http://man.openbsd.org/sshd.8 sshd(8)].  If using the '''Match''' criteria to selectively apply rules for port forwarding, it is also possible to prevent the account from getting an interactive shell by setting '''PermitTTY''' to '''no'''.  That will prevent the allocation of a pseudo-terminal (PTY) on the server thus prevent shell access, but allow other programs to still be run unless an appropriate forced command is specified in addition.  

&lt;syntaxhighlight lang=&quot;apache&quot; line=&quot;1&quot;&gt;
Match Group mariadbusers
        PermitOpen localhost:3306
        PermitTTY no
        ForceCommand /usr/bin/true
&lt;/syntaxhighlight&gt;

With that stanza in [http://man.openbsd.org/sshd_config.5 sshd_config(5)] it is only possible to connect by adding the '''-N''' option to avoid executing a remote command.  

&lt;syntaxhighlight lang=&quot;shell-session&quot;&gt;
$ ssh -N -L 3306:localhost:3306 server.example.org
&lt;/syntaxhighlight&gt;

The '''-N''' option can be used alone or with the '''-f''' option which drops the client to the background once the connection is established.  

Without the '''ForceCommand''' option in a '''Match''' block in the server configuration, if an attempt is made to get a PTY by a client that is blocked from getting one, the warning &quot;PTY allocation request failed on channel ''n''&quot; will show up on the client, with ''n'' being the channel number, but otherwise the connection will succeed without a remote shell and the port(s) will still be forwarded.  Various programs, including shells, can still be specified by the client, they just won't get a PTY.  So to really prevent access to the system other than forwarding, a forced command is needed.  The tool '''true(1)''' comes in handy for that.  Note that '''true(1)''' might be in a different location on different systems.  

===Limiting Port Forwarding Requests Using Keys Only===

The following '''authorized_keys''' line shows the '''PermitOpen''' option prepended to a key in order to limit a user connecting with that particular key to forwarding to just port 8765:

&lt;pre&gt;
permitopen=&quot;localhost:8765&quot; ssh-ed25519 AAAAC3NzaC1lZDI1NT...
&lt;/pre&gt;

Multiple '''PermitOpen''' options may be applied to the same public key if they are separated by commas and thus a key can allow multiple ports.  

By default, shell access is allowed.  With shell access it is still possible to run other port forwarders.  The '''no-pty''' option inside the key can facilitate making a key that only allows forwarding and not an interactive shell if combined with an appropriate forced command using the '''command''' option.  Here is an example of such a key as it would be listed in '''authorized_keys''':

&lt;pre&gt;
no-pty,permitopen=&quot;localhost:9876&quot;,command=&quot;/usr/bin/true&quot; ssh-ed25519 AAAAC3NzaC1lZDI1NT...
&lt;/pre&gt;

The '''no-pty''' option blocks interactive shell.  The client will still connect to the remote server and will allow forwarding but will respond with an error including the message &quot;PTY allocation request failed on channel&amp;nbsp;''n''&quot;.  But as mentioned in the previous subsection, there are still a lot of ways around that and adding the '''command''' option hinders them.  

This method is awkward to lock down.  If the account has write access in any way, directly or indirectly, to the '''authorized_keys''' file, then it is possible for the user to add a new key or overwrite the existing key(s) with more permissive options.  In order to prevent that, the server has to be configured to look for the file in a location outside of the user's reach.  See the section on [[OpenSSH/Cookbook/Public_Key_Authentication | Public Key Authentication]] for details on that.  The methods described above in the previous subsection using [http://man.openbsd.org/sshd_config.5 sshd_config(5)] might be more practical in many cases.

&lt;noinclude&gt;{{OpenSSH/TOC|mini}}&lt;/noinclude&gt;
{{BookCat}}
{{status|100%}}</text>
      <sha1>p8xt3efb79yu4dn48zdhfcaws8brp3g</sha1>
    </revision>
  </page>
  <page>
    <title>Aros/Platforms/Arm Raspberry Pi support</title>
    <ns>0</ns>
    <id>286123</id>
    <revision>
      <id>4675758</id>
      <parentid>4675529</parentid>
      <timestamp>2026-10-12T17:58:27Z</timestamp>
      <contributor>
        <username>Jeff1138</username>
        <id>301139</id>
      </contributor>
      <minor />
      <origin>4675758</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="104935" sha1="tnl9ot8z5pe33uzaz3zeip55kgs5tko" xml:space="preserve">{{ArosNav}}

[[#Native]]

[[#Hosted]]

[[#Build]]

[[#Hardware]]

[[#References]]

[[#Future]]


==Introduction==


[[File:Scalos00.png|thumb|Scalos on Aros Pi3b]]

Aros aims to cover Pi 3 to 5 512Mb+ RAM 


Options to boot from using a good power source to prevent the yellow lightning symbol. 
*With Pi3b+ the max you can get is 5.1V 2.5A with micro usb.
*With Pi4 5.1V 3A with usb-c 
*With Pi5 5.1V 5A, the amps went ever upwards, even to 5.1V 9A with usb-c 


* Pi500+ keyboard wedge - working 
* Pi500 wedge with up to date bootloader via PiOS - working 
* Pi 5  - Quad A76 64bit ARMv8 and RP1 &quot;southbridge&quot; with VideoCore 7 D0 (rev1.1) - untested 
* Pi 5  - Quad A76 64bit ARMv8 and RP1 &quot;southbridge&quot; with VideoCore 7 Pre-D0 C1 (Rev1.0) - untested 
* Pi400 RPI-400 keyboard wedge - resolution changing and audio from micro hdmi0 (near 40pin) and micro hdmi1 (near usb-c psu) - Fn F10 0x5e power on and off works or held down for over 7 seconds auto shutdown - keyboard ok - wifi and lan ethernet testing - 
* Pi 4  - Quad A72 64bit ARMv8 with VideoCore 6 
* Pi 3  - Quad A53 [https://www.raspberrypi.com/documentation/computers/processors.html 64 bit] ARMv8 with VideoCore 4 with '''fan''' to prevent overheating cpu 82C+ throttling 
* Pi02W - Quad A53 64bit - boots but [https://forums.raspberrypi.com/viewtopic.php?p=2387984#p2387984 usb not working but did in the past], 


* Pi 2 - Quad 32bit ARMv6 with VideoCore 4 - mostly not 64bit compatible 
* Pi Model B+ 32bit ARMv6 with VideoCore 4 - not 64bit compatible 
* Pi Model A and B 32bit ARMv6 with VideoCore 4 - not 64bit compatible 


===Native===

* 2013-03 Kalamatee starts work
* 2015-04 Work continues with mschulz on the kernel and Kalamatee (NicJA) on gpio and usb
* 2018 [https://www.patreon.com/posts/i-owe-you-some-20956961 mschulz resume adding BE big endian support], [https://www.patreon.com/michal_schulz/posts Big endian on Pi]  
* 2026 [https://github.com/aros-development-team/AROS/commits?author=bsek latest commits for pi 3b, 4 and 5 64bit] 
* 2026 [https://github.com/aros-development-team/AROS/commits?author=metaneutrons latest commits for Pi5]
* 2026 [https://github.com/aros-development-team/AROS/commits?author=bitplane latest commits for ARM]


====64bit====

'''Download''' A [https://archive.org/details/piAROS Pi Distribution (Distro) has started] and the contents copied to fat32 8GB+ microSD card (there will be drawers/folders - boot c Classes Demos Developer Devs Extras etc only showing). The SD can be plugged in to the Pi. And power on. [https://pi.amiga.icu/ Repository]

[https://aros.sourceforge.io/nightly1.html RaspberryPi 3, 3+, 4 and 5 64bit ArmV8 nightly builds] [https://sourceforge.net/projects/aros/files/ Alternative site and nightly2] which is a test beta limited apps version with both raspi-aarch64-system and raspi-aarch64-contrib can be unbz2'd to a SD or SSD as appropriate. 

64bit build works well on a single core LE little endian. Multicore [https://github.com/aros-development-team/AROS/commit/1df0747c2bda3523a43029725a709b1f377d84ec may follow]. Any issues booting could be down to the SD card so please use another SD to see if it is resolved. Remember Aros Arm uses FAT32 and Aros can detect issues with this format very acutely (once fault found, FAT 0x0FFFFFF7 bad cluster so no files written after that, no repair). Please report your experiences in the [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2138&amp;pid=15057#post_15057 Aros forum thread], [https://forums.raspberrypi.com/viewforum.php?f=179 Raspberry Pi Aros Dev and User forums], [https://forums.raspberrypi.com/viewtopic.php?p=2387984#p2387984 previous Raspberry Pi forum thread]. Any bugs or issues can be [https://github.com/aros-development-team/AROS/issues described here to fix] 

Boots with '''USB3''' port based sata3 ssd on Pi400 but untested on Pi4 (may need eeprom update from PiOS or Pi SD Imager) and Pi5 

Pi 3 B+ is pre-configured for USB sata3 boot - untested 

Pi 3 B may need [https://www.youtube.com/watch?v=ubnwvxF3Klc PiOS to set OTP to boot from usb - do so at your own risk] - if OTP set to usb, boot works but slower than SD card 

Speed write wise (top faster) 
&lt;pre&gt;
*NVME Pi5 untested    &gt;1000MB/sec  or faster if matched correctly 
*Sata3 ssd              500MB/sec
*SD        V90           90MB/sec  4K maybe 8K 
*SD        V60           60MB/sec  1080p 
*SD     U3 V30           30MB/sec  720p 
*SD C10 U1 V10 A1 A2     10MB/sec  minimum should be used now 
*SD C06                   6MB/sec  
*SD C04                   4MB/sec 
&lt;/pre&gt;


As a homage to the past, Aros shows a reduced number of icons but this can be changed by left mouse click in the window and then right click down to Window -&gt; View -&gt; All files

Windows can be manipulated by the top (moving) and the bottom right corner (resizing) only. 

Zune like MUI gui interface, has a unique quirk in that after changing a setting in a text box, you may sometimes need to press Enter/Return before clicking OK, Save, etc 


Double left mouse click on most picture (Developer/Debug/Tests/Datatypes), audio and video files are supported, via datatypes, by the multiview application. 
Esc escape key usually closes open windows even the desktop 

In Prefs/Appearance some decorative theming elements need work. There is a few Mason icons in /Prefs/Presets/Icons/Mason/ and the ever present default Gorilla - Icon exchange in works 

For more intensive graphics applications, you may need to edit config.txt in the root folder and change 128M to 256M to adjust more memory to graphics usage 

If your cursor should '''appear''' to vanish, fear not it is still there. Please head to the top of the screen i.e. the title bar, hold down the left click mouse and drag the screen down a little and the cursor will appear again. Then you can drag the screen up again. 


Like most amiga like OSs the audio and networking need to be setup manually 

Audio AHI prefs - Mode settings tab - needs both Music unit and Unit 0 set to RPiHDMI:16 bit stereo++  or RPiPWM:16 bit stereo++ at 44100Hz. Press '''Save or Use''' button after each choice 


For wireless, please use the Wifi prefs and already selected device bwfm.device. Press Scan and double right click on the router and enter password. You may need to setup after every power off
*if asking for password again - press cancel and go to Network Prefs, Wireless Networks tab and highlight the router line and hit the remove button and press the cancel button. Retry with Wifi prefs again 
*...waiting for an address - Disconnect and try Connect 
Until, Connected to &lt;router&gt; - 192.168.x.x 


For lan ethernet port, please use Network prefs and the following hardware is 
*lan9514  Pi3b Pi2 not supported at the moment 
*lan7515  Pi3b+ type into Device  usblan78xx.device as net0:  remove other device(s) 
*bcmgenet Pi4 Pi400 choose for Device bcmgenet.device 
*         Pi5 Pi500 Pi500+ RP1 i/o 
 (network prefs may forget random information when rebooted) 


Summary
&lt;pre&gt;
*3b    ethernet not supported, usb ethernet not working but wifi prefs setup works 
*3b+   wifi working and ethernet works 
*4     untested 
*400   wifi and ethernet untested 
*5     wifi and ethernet untested
*500   wifi and ethernet untested
*500+  wifi works 
&lt;/pre&gt;


Type in 'aarch64' in the [https://archives.arosworld.org/index.php?function=search&amp;tool=simple search box] and you will see available software packages / apps. apkg can be used to inspect and install applications. 

[http://archives.arosworld.org/index.php?function=browse&amp;cat=network/browser amelinium web browser (JS 1.6 ES9 ECMASCript 2018)] is available with an [https://eab.abime.net/showthread.php?t=122494&amp;page=51 eab thread] reminiscent of [https://github.com/zapek/Voyager Voyager] and to a lesser extent [https://github.com/amigazen/aweb3/ Aweb JavaScript 1.5 (ECMAScript 3)] as css and javascript websites can be slow to load or resolve (no JIT) and nothing from facebook, reddit etc. 

Press Cancel at screenmode selector or -wb argument to get windowed version. You could use the Shift + Del shortcut or mouse wheel should work to delete all text at once. To view wikibooks set Agent to Android (telefon) aka Google Chrome 126 or iPhone aka Safari 17 setting in menus. Html5test gives 189 (1.29), 300 (1.31), 311 (1.33) out of 555, some bigger Amiga like browsers are around 370+ but it does less better. 

You may have to delete the cache (Menu -&gt; Page -&gt; Delete cache) to fully retest big Amelinium updates or free up space. 
Be aware [https://pianetaamiga.it/en/reportage-pianeta-amiga-2026/ some site pages] can use up hundreds of MBs of cache very quickly 

 DNS lookup failed...  close browser and reboot and setup wifi again - repeat until it works again 

 youtube video and audio - js button for javascript must be on/shaded -  Settings -&gt; Soundoutput - AHI 
Usually restricted to lower resolutions due to [https://docs.invidious.io/faq/#q-where-are-the-360p480p1080p-quality-options bandwidth]. You can always [https://docs.invidious.io/installation/#install-the-dependencies self host] for better 

Telegram https://t.me/s/channel_name for public messages from vamped_amiga chatamigagames demoscenecracktros 

*art local js apps like dpaint.js 


There is normally no Bluetooth support for most amiga like OSs but Aros has one [https://github.com/aros-development-team/AROS/commit/6942cbfbf66426d21963a7fcd8aba6aff611a9e0 work in progress] [https://forums.raspberrypi.com/viewtopic.php?t=338466 firmware] 

*Bluetooth 4.1 BCM43430A1.hcd Pi3B, Pi3A, Zero 2W 
*Bluetooth 4.2 BCM4345C0.hcd  Pi3B+, Pi4 
*Bluetooth 5.0 BCM4345C5.hcd  Pi4B rev, CM4 and maybe Pi5 and CM5 

&lt;pre&gt;
*bthid    keyboard mouse support 
*btserial serial 
*btpan    short range wireless connecting devices 
&lt;/pre&gt;


Only the Pi5 has a RTC real time clock, the other Pis will need to use ntp services time.cloudflare.com pool.ntp.org or Cloudflare 162.159.200.1, 162.159.200.123, 2606:4700:f1::1, 2606:4700:f1::123 or [https://github.com/bohunamiga/PiNTP PiNTP -s goodtime.ijs.si or ntp1.ptb.de] to get the date and time from the internet. Can use date in a shell e.g.  date 24-Dec-2026 23:59:59  but this will need to be done again after every reset/power off. Maybe [https://github.com/aros-development-team/AROS/commit/28674a157bc56175aa668e7b62dca6fa740578dc ds3231 rtc with dtoverlay=i2c-rtc,ds3231 in config.txt] 


It helps to have all usb devices already plugged in before power on to detect at the moment. Even then some usb devices will freeze the mouse cursor and the only resolution is to remove the offending usb device and reinsert. Sometimes, the reinsert leads to the mouse cursor vanishing, it is still there and responds to left mouse clicks, top of the screen and pull down the screen. 

USB classes support from Prefs/Trident is still work in process 
*usbaudio working on usb3 port (blue) on pi4, 400 but not working (no rt isochronous) on usb2otg (white or black) for pi3b, zero 2w 
*[https://aminet.net/package/mus/midi/camd camdusbmidi] detects midi devices without a preferences file (Prefs/Env-Archive/sys/midi.prefs) as [https://www.youtube.com/watch?v=RBxHkwy4Nrw auto setup now] possibly with [https://github.com/metaneutrons/mt32-pi metaneutrons mt32-pi] [https://github.com/rtzor/mt32-pi mt32-pi fork] [https://github.com/ahmadexp/mt32-pi fork] [https://github.com/gmcn42/mt32-pi-control control of] [https://github.com/dwhinham/mt32-pi mt32-pi pi3+]. Alternative of [https://homspace.nl/samplerbox/ SamplerBox]. 

Will need developer clang gcc tools to look at 64bit ports of [https://archives.arosworld.org/?function=showfile&amp;file=driver/audio/usbmidi.i386-aros.lha usbmidi], [https://aminet.net/package/mus/midi/CAMD_Toolkit CAMD_Toolkit], [https://aminet.net/package/mus/midi/camdtools camdtools], [https://github.com/cnvogelg/amiditools amiditools], [https://github.com/timoinutilis/midi-sequencer-amigaos horny src], [https://aminet.net/package/mus/midi/horny-base horny-base], [http://bnp.hansfaust.de/index.html BnP], [https://arosarchives.os4depot.net/?function=showfile&amp;file=audio/misc/timidity.lha timidity], 


Regarding 680x0 emulation, there are several options (not implemented yet) that could be considered 
*[https://github.com/aros-development-team/AROS/blob/6722a0ae9e03fe5d26e32703360bd2059e0864cc/rom/m68kemu/README.md?plain=1#L424 m68kemu.library] for some Amiga productivity where the cpu is emulated and the system calls are redirected to Aros ones
*[https://github.com/BlitterStudio/amiberry amiberry] (winuae) for everything else like games 
*[https://github.com/jonx/AROS/tree/aarch64-darwin-graft/arch/all-darwin/libs/emu68k emu68k] 
*[https://scriptedamigaemulator.net/ Scripted Amiga] with [https://github.com/naTmeg/ScriptedAmigaEmulator ScriptedAmigaEmulator] or older [https://github.com/gbraad-amiga/ScriptedAmigaEmulator2 ScriptedAmigaEmulator2] 
 Hopefully getting Pi3 up to 25Mhz 68040 (non JIT) and 75Mhz 68040 (JIT) 
 Pi4 getting up to 50Mhz 68040 (no JIT) and 150Mhz 68040 (JIT) 


[https://pinout.xyz/ GPIO 40 pins] [https://learn.sparkfun.com/tutorials/raspberry-gpio/gpio-pinout pinout] 

Some exceptions:

*Physical pins 27, 28 (GPIO0, 1) are an internal I2C bus and should not be used
*The other I2C on pins 3, 5 (GPIO 2, 3) can be used generally, but be aware they have permanent pull-up resistors to 3.3V
*For MIDI use USB but there are dedicated UART pins 8, 10 (GPIO 14, 15).

With a HAT it's more awkward -- you need to know which pins are used by the HAT and avoid them. Hopefully this will be documented.

Remember all GPIOs are 3.3V (not 5V tolerant), floating/noisy inputs can cause odd behavior, and that shorting the power supplies can cause instant death of the Pi.

In the shell (Cntrl + C to end) 

 GPIO PIN/A/N,SET/N,GET/S,MODE/K,PULL/K

Controls and queries hardware GPIO pins via gpio.resource which is stored in the rom or Devs/ '''please test''' 

*PIN   -- (Required) Target GPIO pin number (e.g. 12).
*SET   -- Set pin output value to 0 (LOW) or 1 (HIGH).
*GET   -- Read and print current digital input level (0 or 1).
*MODE  -- Configure pin mode: IN (Input), OUT (Output), ALT (Alternate).
*PULL  -- Configure pull resistor: NONE, UP, DOWN.

EXAMPLES
&lt;pre&gt;
GPIO 12 MODE OUT
GPIO 12 SET 1
GPIO 12 GET
GPIO 13 PULL UP
&lt;/pre&gt;


[https://gpiozero.readthedocs.io/en/stable/installing.html Current] [https://gpiozero.readthedocs.io/en/v1.2.0/api_boards.html old support for gpiozero is unknown at present] [https://energenie4u.co.uk/res/pdfs/ENER314%20UM.pdf and associated 433MHz equipment] [ USA X10 security and lights via USB] [ OpenHab with Shelly Smart Plug connected over Wi-Fi, controlled by MQTT or HTTP] 


Printing only with Postscript but [https://github.com/bohunamiga/MintPRINT one] of [https://github.com/boingball/MintPRINT two] [https://github.com/Andiweli/AmiAirPrint/tree/main AirPrint] IPP has been attempted with [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2061&amp;pid=13954#post_13954 discussion] 


Youtube 

[], [], [https://www.youtube.com/watch?v=X4fmWAIv7FE Aros native on Pi3b], 

[], [], [https://www.youtube.com/watch?v=TSxlYb1eQWU Installed on Pi3b+], 

[], [], [https://www.youtube.com/watch?v=NFF1H3jCoz8 testing Aros native on Pi400], 

[], [], [https://www.youtube.com/watch?v=nIVx7mh1E1Q&amp;pp=ygUHYXJvcyBwadIHCQkTDAGHKiGM7w%3D%3D Aros on Thumb 2 based 32bit-ish ARM STM32H743 board], 


[https://www.youtube.com/watch?v=zQM4CD64xDE&amp;t=612s&amp;pp=ugUEEgJlbg%3D%3D Performance under Linux] but on Aros... 

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;10%&quot; |Pi
! width=&quot;10%&quot; |Single Core 2D
! width=&quot;10%&quot; |Single Core 3D
! width=&quot;10%&quot; |Single Core 3D
! width=&quot;10%&quot; |SMP 2D
! width=&quot;10%&quot; |SMP 3D
! width=&quot;10%&quot; |SMP 3D 
! width=&quot;35%&quot; |Comments
|-
| &lt;!--Pi--&gt;Pi3 
| &lt;!--Single Core 2D--&gt;
| &lt;!--Single Core 3D--&gt;
| &lt;!--Single Core 3D--&gt;
| &lt;!--SMP 2D--&gt;
| &lt;!--SMP 3D--&gt;
| &lt;!--SMP 3D--&gt;
| &lt;!--Comments--&gt;
|-
|}


==== 32bit ====

For the Pi1 Pi2 Pi2B the status of AROS native ARMv6 for 32bit RasPi was OK. System booting, USB working (although with some issues but plans to fix them). 32bit native [http://www.aros.org/nightly1.html ARMv6 32bit nightlys] raspi-armhf-system raspi-armhf-contrib unbz2'd to fat32 microSD 


===Hosted===


AArch64 CPU backend for AROS, a Cocoa/Metal display, clipboard / host-volume / CoreAudio / BSD-sockets bridges, GPU 2D via gpufx.library, a 68k→AArch64 JIT (run68k), and a full Rust std port. On [https://www.jkn.me/blog/macaros-aros-on-apple-silicon/ latest Apple Silicon] [https://github.com/jonx/Macaros early buggy alpha version of hosted Aros .dmg on MacOS12+]. Please use [https://github.com/jonx/Macaros/issues MACAros github] for issues, features etc and possibly [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2030&amp;pid=13910#post_13910 here] 


[http://www.aros.org/snapshots1.html old linux and android hosted 32bit] 


==== Hosted ====

=====64bit=====

[https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2019&amp;rowstart=80&amp;pid=13667#post_13667 Ubuntu Linux PC hosted Pi compiler build] 

[https://github.com/BlitterStudio/aros-compiler-docker Docker based cross compiler for various Aros systems], 

[https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2019&amp;rowstart=80 From the Aros Raspberry pi 3 64bit thread] 
Instructions on building 64-bit Raspberry Pi AROS and cross-compiler from sources.

You will need:
- Ubuntu 24.04 or 26.04
- qemu-system-aarch64 installed
- Internet connection
- rpi-scripts.tar.gz downloaded (https://axrt.org/download/aros/rpi/rpi-scripts.tar.gz)

1) Install prerequisites:

sudo apt install git gcc g++ make gawk bison flex bzip2 netpbm autoconf automake libc6-dev liblzo2-dev libpng-dev gcc-multilib byacc python3-mako cmake yasm curl nasm

2) Clone sources

cd &lt;project-directory&gt;
git clone https://github.com/aros-development-team/AROS.git --recurse-submodules

3) Extract rpi-scripts.tar.gz. Copy all files into your project directory so that you have:

AROS (the directory with cloned sources)
fix-dotdot.py
rebuild.sh
recreate-sdcard.sh
run-qemu.sh
update-sdcard.sh

4) Run ./rebuild.sh. Select option 1) toolchain-core-aarch64

This will execute process of building a cross-compiler. During this process packages will be downloaded from Internet. This process can take up to 2 hours. If there are some missing dependencies, install them with 'sudo apt install' and restart this step.

5) Run ./rebuild.sh again. Select option 2) core-raspi-aarch64

This will build system files for 64-bit Raspberry Pi AROS. This process can take around an hour.

6) Run ./recreate-sdcard.sh

This will create an sdcard.img file with contents of previous step.

7) Run ./run-qemu.sh

This will start QEMU with SD card image and ROM images. It will boot into AROS.


=====32bit=====

Ubuntu VM approach to compiling [http://lallafa.de/blog/2013/06/building-aros-hosted-for-raspbian/ Linux hosted AROS June 04, 2013]

 ../AROS/configure --target=linux-armhf  --enable-includes=/usr/arm-linux-gnueabihf/include --x-includes=/usr/arm-linux-gnueabihf/include --x-libraries=/usr/arm-linux-gnueabihf/lib

arm-elf- is symbol-linked to arm-linux-gnueabi- (arm-linux-gnueabi- is more correct in this case, because it's going to be compiling the ARM AROSBootstrap for ARM Linux)

*armel - many of the &quot;android&quot; machines require since the entire OS is made for soft float VFP. 
*armfp - Efika MX target, Raspberry PI, EfikaMX, Pandora and virtually everything (VFP)

Keep in mind it's possible to start hardfp AROS hosted on softfp system, though, as long as no calls between AROS and host require floating point parameters. NOTE: hardfloat objects *cannot* be linked with softfloat objects - they have a different ABI.

Just keep in mind the arm nightly build machine is quite complex beast. It needs the x86_64 host compiler to compile AROS tools. The arm version is built every night using gcc-4.6.2 crosscompiler (built together with AROS) and successfully builds armel and armhf linux hosted targets.

*needs an AROS code compiler for ARM target 
*as well as unix compiler for ARM linux host (would be best to have both softfp and armhf, we have softfp only now) with full set of libraries and includes.

with—disable-crosstools  $AROS_CC  is always a wrapper around $KERNEL_CC  ?  If  so,  this  is  wrong for some ports. This can break Darwin, Windows and Android port. 
Yes,  Android  port  will  build.  And  even  work. But it's not good because  the  port  will  not  be ABI-compatible with other ARM ports. Android's ABI is different from GNUEABI. For example:

&lt;pre&gt;
enum test {foo, bar};
enum test testvar;
&lt;/pre&gt;

sizeof(testvar)  will  be  equal  to sizeof(int) in GNUEABI (Linux and AROS)  and  sizeof(short)  on  Android. This affects linking objects from static linklibs, for example.

Previously everything worked because $AROS_CC was a wrapper on top of $HOST_CC. And a real crosscompiler was used on non-ELF hosts.

Android is the same. $KERNEL_CC is incompatible with AROS.

compiler=kernel  is  appropriate _ONLY FOR CODE WHICH RUNS ON HOST OS_ (or  barebone  hardware,  if  we  talk  about  native).  This includes bootstraps,  their  linklibs, and host-side dynamic libraries (Windows makes extensive use of them because of architectural considerations.

No single AROS object should be compiled with this setting. $KERNEL_CC is really compatible with AROS *ONLY IN LINUX-HOSTED* and no more. On other systems (Darwin, Windows,  Android) this is not true any more, and compiler=kernel is never going to work.

If  you  want  to  compile your AROS module against host OS includes, append  the  following  to  USER_INCLUDES  (or  USER_CFLAGS,  this  is effectively the same):

 -isystem $(GENINCDIR) $(KERNEL_INCLUDES)

$(KERNEL_INCLUDES) expands to:

 -isystem  &lt;your_os_includes&gt;  -isystem  &lt;host_OS_gcc_private_includes&gt;
 -nostdinc

This makes AROS compiler adhering to host OS APIs.

If you want some preprocessor symbols based on what your host OS actually is, add something like -DHOST_OS_$(AROS_HOST_ARCH).

Why is there $(GENINCDIR) at all? Because host OS has its own libc includes, which would conflict with AROS ones. And the host OS libc is not binary-compatible with AROS one.

Why doesn't Windows-hosted port use $(KERNEL_INCLUDES) ? Because WinAPI includes conflict with AROS ones in fundamental typedefs, like WORD, BYTE and BOOL. It's almost impossible to deal with this in any other way than rewriting WinAPI definitions using AROS types.

Building under centos 6.3 (i386) currently, and AROS creates the toolchain itself. haven't yet committed the necessary changes but &quot;./configure --target=raspi-armhf&quot; is enough to start, then &quot;make arosboot-raspi&quot; will generate arosraspi.img (containing the bootstrap, kernel.resource, and exec.library) as well as arosraspi.rom (containing all the other essentials components such as dos, graphics etc).  It will also copy over a config.txt file to make the raspi bootstrap code load the correct kernel, and a cmdline.txt that enables exec debug output.

*armel = typically Debian 6, Ubuntu Maverick, Android, 
*armhf = typically Debian 7, Debian 8, Ubuntu Precise,

Cross-compiling Ubuntu ARM softfp 
&lt;pre&gt;
    sudo sh
    echo 'foreign-architecture armel' &gt;&gt;/etc/dpkg/dpkg.cfg.d/multiarch
    echo 'deb [arch=armel] http://ports.ubuntu.com/ precise main universe' &gt;/etc/apt/sources.list.d/armel.list
    apt-get update
    apt-get install gcc-arm-linux-gnueabi libx11-dev:armel libsdl-dev:armel
&lt;/pre&gt;

&lt;pre&gt;
 ./configure --target=linux-arm --x-includes=/usr/include \
             --enable-includes=/usr/arm-linux-gnueabi/include
&lt;/pre&gt;

Cross-compiling Ubuntu ARM hard-float 
&lt;pre&gt;
    sudo sh
    echo 'foreign-architecture armhf' &gt;&gt;/etc/dpkg/dpkg.cfg.d/multiarch
    echo 'deb [arch=armhf] http://ports.ubuntu.com/ precise main universe' &gt;/etc/apt/sources.list.d/armhf.list
    apt-get update
    apt-get install gcc-arm-linux-gnueabihf libx11-dev:armhf libsdl-dev:armhf
&lt;/pre&gt;

&lt;pre&gt;
    ./configure --target=linux-armhf --x-includes=/usr/include \
                --enable-includes=/usr/arm-linux-gnueabihf/include
&lt;/pre&gt;

Now, the AROS build is configured properly and all you need to do is:

 make


==Build==

===64bit===


===32bit===


# download/checkout the source someplace, e.g. /build/AROS-Src/
# make a directory to store external sources AROS downloads, e.g. /build/Ports
# make a build directory, e.g. /build/aros-raspi-armhf
# cd into the build dir, configure, and then run make -:

&lt;pre&gt;
&gt;cd /build/aros-raspi-armhf
&gt;/build/AROS-Src/configure --target=raspberrypi-armhf --with-serial-debug --enable-ccache --with-portssources=/build/Ports
&gt;make
&gt;make arosboot-raspi
&lt;/pre&gt;

then copy the files from /build/aros-raspi-armhf/bin/raspi-armhf/AROS/ onto an sdcard, and download/copy the Raspi firmware files onto it.

You should then be able to boot the sdcard on your RasPi.

The current W.I.P tree to svn. it can be built as follows ..
&lt;pre&gt;
./configure --target=raspi-armhf
make arosboot-raspi
&lt;/pre&gt;

That will generate arosraspi.img, arosraspi.rom and config.txt in bin/raspi-arm/AROS - so either copy just those files to a fat formatted SD card (with the firmware files on), or copy the whole contents of the AROS folder.

NB - if you have a Linux/other install, backup the existing config.txt first

arosraspi.img contains the bootstrap (which has very basic mailbox code, framebuffer/gpio init, and console &quot;emulation&quot; via code pinched from our libbootconsole), kernel.resource, and exec.library

arosraspi.rom contains all the other components needed to boot AROS.

The config.txt file will tell the RasPI bootstrap to load the arosraspi kernel and ramdisk (rom).

the bootstrap has minimal mailbox code, planning on adding either a resource or library that driver/app code will use to access it (likewise for GPIO)


Help building AROS hosted on Linux ARM

Was looking a way to use more my Handheld ARM based called Pyra (Dragonbox Pyra) an ARM (Omap5 cpu with 4GB ram) linux based machine (Debian Buster v10 with kernel 5.6.19 adapted) and have a try to compile the latest Aros sources by Deadwood directly on this device.
Compilation stops after build libpopupmenu.a and trying to build libatomic have this error:

&lt;pre&gt;
    Configuring build in bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic
    configure: WARNING: unrecognized options: --disable-nls, --without-x
    checking for --enable-version-specific-runtime-libs... no
    checking for --enable-generated-files-in-srcdir... no
    checking build system type... arm-unknown-linux-gnu
    checking host system type... arm-unknown-aros
    checking target system type... arm-unknown-aros
    checking for a BSD-compatible install... /usr/bin/install -c
    checking whether build environment is sane... yes
    checking for arm-aros-strip... /media/farox/pyra2/arosbuilds/toolchain-core-armhf/arm-aros-strip
    checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
    checking for gawk... no
    checking for mawk... mawk
    checking whether make sets $(MAKE)... yes
    checking whether make supports nested variables... yes
    checking for arm-aros-gcc... /media/farox/pyra2/arosbuilds/toolchain-core-armhf/arm-aros-gcc
    checking whether the C compiler works... no
    configure: error: in /media/farox/pyra2/arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic':
    configure: error: C compiler cannot create executables
    See config.log' for more details
    make[2]: *** [mmakefile:4489: /media/farox/pyra2/arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic/.configured] Error 77
    [MMAKE] make --no-print-directory TOP=/media/farox/pyra2/arosbuilds/toolchain-core-armhf-build SRCDIR=/media/farox/pyra2/arosbuilds/AROS CURDIR=tools/crosstools/gnu TARGET=tools-crosstools-gcc-libatomic-configure -s --file=mmakefile tools-crosstools-gcc-libatomic-configure failed: 512
    [MMAKE] Error: Error while running make in tools/crosstools/gnu: No such file or directory
    make[1]: *** [Makefile:361: linklibs-libatomic] Error 10
    make: *** [Makefile:183: crosstools] Error 2
&lt;/pre&gt;


looking at config.log on arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic

found that arosbuilds/toolchain-core-armhf/arm-aros-ld: cannot find -laeabi
so do make linklibs-aeabi-arm-quick
and the missing lib was built.

now the next stop is at
fatal error: bits/libc-header-start.h: No such file or directory
and
fatal error: sys/cdefs.h: No such file or directory
in many places so after checking that have this missing include files i have noted that my include path is a bit different, standard searching path is /usr/arm-linux-gnueabihf but in my system is /usr/include/arm-linux-gnueabihf
so if i add my path to some mmakefiles compilation goes on....but is a better way to add this path to avoid every mmakefiles to be changed?

fixed with adding
-I/usr/include/arm-linux-gnueabihf
to where is missing on mmakefiles like
USER_INCLUDES := -isystem $(GENINCDIR) -I/usr/include/arm-linux-gnueabihf $(KERNEL_INCLUDES)

P.s. I have changed many mmakefiles and have at least compiled (after many hours) the toolchain doing make every time in arosbuilds/toolchain-core-armhf-build (also have to disable making tests under cplusplus but don't remember the directory ...) but ask an help to have an automated way to correctly build without modify mmakefiles.


Last time built armhf target was around 2 years ago. At that point built is via cross-compilation from linux (ubuntu 22.04) using linux armhf crosscompiler (this can explain the path differences you are experiencing) as well as using AROS gcc cross-compiler in version 6.5.0 (build with option 21) in rebuild.sh). Since then AROS GCC has been updated to 10.5.0 and don't believe anyone tried to build the armhf target again.

My suggestion would be to downgrade GCC to 6.5.0 (via editing AROS/config/gcc_def file) and try to first build using cross-compilation from x86_64 linux. Once that works, you will have a &quot;template&quot; to compare to native compilation under arm linux.


Thanks for your suggestion...but think the toolchain with GCC 10.5.0 is compilable if i found a way to pass the path of my system to the script that build (option 21 on rebuild).
The other only changes are (but don't know where to modify...) is to add the build of libaeabi and disable the building of some tests under cplusplus that use exceptions and is not supported under ARM. try to crosscompile with my Linux amd64 PC.

For paths look into core-linux-armhf/bin/linux-armhf/gen/config/target.cfg. A number of build-wide variable is set there containing paths to local build system. These variables and the target.cfg file are generated by AROS ./configure script.

Thanks compilation now go forward...changed target.cfg under &quot;toolchain-core-armhf-build/bin/linux-arm/gen/config&quot; and do make on &quot;toolchain-core-armhf-build&quot; dir.

Need to find where to enable build libaeabi.a so can build the entire toolchain with option 21 of rebuild.sh


Found something that looks like libeabi in AROS/arm-all/arm-aeabi/mmakefile.src. Try adding a third line there:

#MM- linklibs-armhd : libklibs-aeabi-arm

Don't remember needing this library. Possibly the 6.5.0 GCC somehow does this while 10.5.0 is missing this.

Try adding this line (and the variant &quot;linklibs-armhf&quot; instead of hd) but it did not solve the automatic building of the missing lib. I must do &quot;linklibs-aeabi-arm-quick&quot;.
Anyway after have build the aeabi lib i succefully built the toolchain (after many hours...). Smile

To test I restarted from selecting option 21 (on rebuild.sh) but after many hours i get the same error of the kernel includes not found...maybe i need to modify the configure script for my case.

With the toolchain built i try to build the core-linux-armhf (DEBUG) (option 22) but after a while it stopped with
&quot;cannot find -laeabi &quot; so i made it built manually...and now i can continue compiling...i'll let you know if all goes ok.


== Hardware ==

===64bit===


====BCM2712====

With the Pi5 

Broadcom VideoCore 7 vc7 is an integrated GPU with 12 cores and up to 800 MHz clock. VideoCore VII is capable of OpenGL ES 3.1 and Vulkan 1.2. The driver support for the Raspberry Pi continues to build upon the [https://lore.kernel.org/dri-devel/20230928114532.167854-1-itoral@igalia.com/ open-source V3D driver] stack within [https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25450 Mesa] hopefully be merged for Mesa 23.3. x265 HEVC accelerated untested, x264/h.264 and VP9 cpu only. 

*Raspberry Pi M.2 HAT+ Expansion Board 
*Geekworm X1001 PCIe to M.2 Key-M NVMe
*Geekworm X1003 PCIe to M.2 HAT NVMe SSD PIP Board for Raspberry Pi 5 
*Pineboards Pi Hut HatDrive! M.2 HAT 2024/V4 
*Hat+ Gen2 Gen3 Nvme
*GeeekPi 52Pi N04 for Raspberry Pi 5 NVME M.2
*


*2024 RPI AI HAT    - Hailo  20TOPs  no LLMs 
*2026 RPI AI HAT+ 2 - Hailo  40TOPs  slightly better? 


[https://www.raspberrypi.com/documentation/accessories/camera.html Cameras for Pi]
*Raspberry Pi camera module, the V3 with Sony IMX708 back-illuminated CMOS 12 Megapixel sensor
*Raspberry Pi Camera Module V2 – 8MP Sony IMX219 Sensor
*Raspberry Pi camera Rev 1.3, 5MP 1080P OV5647 image/video module, 2592 x 1944 pixels


====BCM2711====

With the Pi4 an ARM a72 cpu is about x3 times the size of an a53 in the Pi3 

the 2711b line used more power when idle, compared to the 2711c 

*2018 Raspberry Pi PoE HAT Power Over Ethernet Hat - design issues 
*2020 Raspberry Pi PoE+ HAT Power Over Ethernet Hat Pi3b+ Pi4 only - better design 
*Waveshare PoE HAT (B) with cooling fan for Raspberry Pi 3B+/4B 802.3af PoE 

*[https://github.com/axizo-pi/V3DLib vc6 V3D 4.2] is derived from [https://docs.broadcom.com/doc/12358545 vc4], but it is significantly different 
The QPU pipeline stays mostly the same, you still have an add ALU and a multiply ALU and it can issue two ALU OPs per cycle. There is still 4 SIMD lanes, interleaved over 4 cycles.
The instruction encoding for the QPUs is different, but the core instructions are the same.

Instructions for packed 8 bit int math has been dropped, along with most of the pack modes.
Instructions for packed 16bit float math has been added (2 floats at in a single operation)
With vc5/vc6, you write two packed 16f value to the tilebuffer (or four writes of 32f, if you are using the rgba32f framebuffer). And there is a handy vfpack operation which allows you to pack two f32s into a single 32bit value in a single instruction. You can vfpack directly into the tile buffer register.

the multiply ALU can now fadd, so you can issue two fadds per instruction. the add ALU has gained a bunch of new instructions 

the A and B register files have been merged. You still only get an A read and a B read per instruction, but they read from one big register file (which means the underlying memory block has gone from two sets of &quot;one read port, one write port&quot; to one &quot;two read ports, one write port&quot; block)

The theoretical max FLOPs per QPU remains the same at two per cycle, other than the bump from 400mhz to 500mhx but it looks like a lot of effort has been put putting those theoretical FLOPs to better use. 
*vc4 could run one or two threads per QPU. When you ran in two thread mode, the available register file halfed to 32 registers.
*vc5 added a four thread per QPU mode, with 16 registers per thread.
*vc6 doubled the size of the register file. You could now use all 64 threads in two thread mode and 32 registers in for thread mode. Single thread mode was removed, you always have at least two threads.

With the threading improvements, the QPUs should spent much less time idle waiting NOPs for memory requests. Most of the design changes have gone to improving the fixed function hardware around the QPUs. A fixed function blend unit has been added, which should reduce load on the QPUs when doing alpha blending. hope software blending is still possible 

The tile buffer can now store upto 4 render targets (up to 128bits per pixel, so if you are using 4 32bit render targets, you can't have a depth buffer)

A MMU, allowing a much simpler/faster kernel driver.

Many more texture formats, framebuffer formats.

h264/x264 as Pi3 

All the features needed for opengl es 3.0 

H.265 / HEVC decoder is a HEVCv2 Main 4:4:4 10 design supporting bitstreams up to profile 5.1
HEVC hardware decode supports 4kp60, 10-bit. Audio output is pretty much unchanged, but the HDMI audio channels now support 8x192kHz bitrates 

Each ALU typically have 2 floating point operators, and as you pointed out in a earlier post videocore 6 is no exception, with both a multiply and additive floating point operator. Thus theoretical GFLOPs are calculated with both operators in mind. That is what the 2 in my formula represents, and is common across any modern programmable shader, whether you calculate Nvidia, AMD, Intel, Boardcom or any other company's GPUs. Total ALUs * 2 * GHz clock = GFLOPs, In the case of Raspberry Pi 3, it's 24 ALUs * 2 operators * 0.4GHz = 19.2GFLOPs
If the Videocore 6 does indeed only have 16 ALUs (16 * 2 * 0.5GHz), you'd have only 16GFLOPs but they are better utilised 

Possible maximum performance 
&lt;pre&gt;
VideoCore IV @ 250MHz: 250 [MHz] x 3 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 24 Gflop/s
VideoCore IV @ 300MHz: 300 [MHz] x 3 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 28.8 Gflop/s
VideoCore VI @ 500MHz: 500 [MHz] x 2 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 32 Gflop/s
&lt;/pre&gt;

Faster LPDDR4 memory.


====BCM2837==== 

With the Pi3 
* Broadcom BCM43438 chip provides 2.4&amp;nbsp;GHz 802.11n wireless LAN, Bluetooth Low Energy, and Bluetooth 4.1 Classic radio support, 3B+ [https://github.com/aros-development-team/AROS/commit/afa5bc0bb17d5dd06bcfdbac00853a3799ca8d76 LAN7515] 

The overclock ability has diminished with each chip version as the energy usage has increased. BCM2837 is one of the warmest yet and benefits from active fan cooling if all four cpu cores are in use for a short while. Video playback is not affected due to the custom support in the GPU. 5 V / 2.4 or 2.5 amp power supply recommended if all four cpu cores are running, else throttling (cpu slowdown) might occur. 

Dual VDP and scalable QPU in VC4 and x.264/h.264 accelerated untested only and VP9 on cpu or neon help 


ARMv8-A has [https://developer.arm.com/documentation/102412/0100/Privilege-and-Exception-levels privilege levels] where userspace typically runs at ‘EL0’, the kernel at ‘EL1’ or ‘EL2’ and the firmware at the highest level ‘EL3’. 


===32bit===

=== Core Kernel ===


====BCM2708(family)====
which includes the [http://elinux.org/RPi_Hardware BCM2835] (ARM1176JZF-S 700&amp;nbsp;MHz CPU + VideoCore IV GPU + up to 1GB RAM)

*Framebuffer (fb) using mailbox 
*IRQ scheduler, etc 
*Arasan based SD Card controller 
*Synopsis DesignWare USB 2.0 OTG controller [http://networkdirection.net/index.php?option=com_content&amp;view=article&amp;id=106:rasperry-pi-usb-controller&amp;catid=45:raspberry-pi&amp;Itemid=54 Unofficial DOCS pdf],  [dwc_otg.c FreeBSD], [], [https://www.riscosopen.org/viewer/view/mixed/RiscOS/Sources/HWSupport/USB/Controllers/DWCDriver/ RiscOS USB Driver], [https://www.riscosopen.org/forum/forums/5/topics/878 RiscOS USB Discussion], [https://www.riscosopen.org/forum/forums/11/topics/1893 Other USB RiscOS], [http://plan9.bell-labs.com/plan9/index.html Plan9 Miller's usb] http://plan9.bell-labs.com/sources/contrib/miller/, [https://github.com/Chadderz121/csud CSUD driver], 
*[http://www.smsc.com/media/Downloads_Public/Data_Sheets/9512.pdf SMSC 9512] USB LAN/Hub chip 
*CMOS RAM 
*VCHIQ port which sends messages to the GPU e.g. for mouse, keyboard, audio on HDMI, etc 
*Audio Driver 
*Serial Peripheral Interface Bus (SPI) 
*[http://www.susa.net/wordpress/2012/06/raspberry-pi-pcf8563-real-time-clock-rtc/ I2C registers]
*I2S 
*Universal Asynchronous Receiver Transmitter (UART) 
*[http://elinux.org/RPi_BCM2835_GPIOs GPIOs] and [http://www.adafruit.com/blog/2012/08/17/broadcom-bcm2835-peripheral-memory-map-and-gpio-alternate-use-chart-piday-raspberrypi-raspberry_pi/ Alternative view of GPIO]

BCM2836 
* For Pi B+, PI 2 and Pi 3 SMSC LAN9514 chip adding 10/100 Ethernet connectivity and four USB channels to the board

*[http://www.andrewscheller.co.uk/rpi_pcb_modules.html PCB], [http://elinux.org/RPi_Low-level_peripherals Low level features],


 Implemented so far... 

# Modify the configure system so that it correctly builds for the arm hardware float raspi target.
# Implemented the bootstrap to load the aros modules and prepare the arm to jump into them. Reworked the x86 console support so that parts can be stolen for raspi to use since t has no basic functionality to output to the display.
# Implemented a kernel.resource to prepare the raspi for running aros and provide the low level api calls to expose available resources and allow exec, etc function.
# Implemented serial debug support
# Implemented the exec (and kernel) functionality required to make multitasking work (and interrupts, exceptions, syscalls, etc)
# Implemented a timer.device to utilise the hardware timers.
# Implemented a very basic gfx driver to expose the hardware's framebuffer.
# Implemented an SD-Card driver for AROS which presently only supports the raspi's chipset but can easily be modified to support all sd-card hardware and media.
# Fixed the fat filesystem support in AROS so that it can boot on RasPi's normal SD-Card setup. The &quot;rom&quot; image files needed use a different filename than the default linux, etc images so can be easily installed without harming the existing files - you only need to change the loaded images in the config file to get aros to boot.
# Updated the build scripts to automatically download the necessary raspi firmware files and wrap it all up so that you can simply extract the archive to a fat formatted sdcard and boot it on the raspi without having to get anything else.
# fix everything in contrib and ports to build for raspi (needs proper testing/fixes but allows every component to actually compile at least, including owb) + numerous other fixes to get things working on arm/raspi ..


Improvements...

# Implement a USB chipset driver &quot;OR&quot; finish the existing one [https://github.com/aros-development-team/AROS/commit/c07d13c724f944674be5db54fc6a71ee72a01809 usb otg] - the current code is mostly a skeleton that should initialise the chipset and then needs relevant code to support the different transfer types. It also has the &quot;virtual&quot; hub code in place to represent the raspi's USB port (from poseidons p.o.v) 
# Implement a driver for the USB NIC (a few weeks - depends on USB above) 
# Write an [https://github.com/aros-development-team/AROS/commit/d55d0f74d20b769bbb8c8d386e5c1d7a9154f05a audio driver] (a few weeks - independent of USB) and [https://github.com/aros-development-team/AROS/commit/e93a4c245f27a87c9c4c1d39206694b39059998a HDMI]
# fix syscall bug in the current raspi kernel code
# Graphics depend on having a decent &quot;bcmdma.resource&quot; implemented as to use the cpu's dma engine. The sd card driver needs to use it for transfers to/from the controller - and the gfx system needs to use it for &quot;blitting&quot;. 
# [https://github.com/aros-development-team/AROS/commit/4019d84e4975d4dad987a12d57fe108f5ac048e6 Improve the gfx driver], [ vc4gfx HIDD] add [http://dri.freedesktop.org/wiki/VC4/ Gallium3D support] 
# [https://github.com/aros-development-team/AROS/commit/b13905b3e8e45b089f520b44692c81affddd066f Improve] the [https://github.com/aros-development-team/AROS/commit/3a876755c070f5c73c4f53c7f4d35b4f923088b9 sdcard] device driver  - which is also pretty basic but should work with most cards, rework it to also support pci, etc. sd card interfaces on x86 
# The current code using very rudimentary access to the gpio interface - so that should be implemented as some resource for other components to access, as-well as the i2c interface exposed over the gpio interface. that should have a hidd class implemented which uses the gpio resource to communicate.


 Boot up typical for most other OSs before the open sourcing of many binary blobs from 2017 onwards 

On power-up, the rpi [http://www.open.com.au/mikem/bcm2835/ BCM 2835] [https://github.com/hermanhermitage/videocoreiv VideoCore4] GPU, not the ARM CPU, is in control, and the SD card slot is the only peripheral device with power. The firmware burned into the BCM2835's VideoCoreIV GPU PROM requires a DOS-style partition table; a FAT-formatted first partition; and the freely redistributable but closed sourced Broadcom files “bootcode.bin” and “start.elf” in that partition.

The boot sequence carries out several pre-boot tasks

*On powering of the rpi, the GPU reads and executes bootcode.bin, which then loads start.elf 
*The GPU loads the “start.elf” file, eventually, into the L2 cache and then executes it
*configures the memory split for the CPU and GPU
*reads and parses “config.txt” from the same partition on the SD card and applies the settings (like a PC’s BIOS settings)
*loads the “kernel.img” file, again from the same partition
*activates the CPU to begin executing the loaded kernel image

The CPU/GPU memory split is hard-coded into start.elf, so Broadcom provides three start.elf images, to give 32M, 64M, or 128M to the GPU for multimedia performance, and the remainder to the CPU.

RPi uses [https://github.com/raspberrypi/firmware some closed source loaders] and at some point it loads a binary blob named &quot;kernel.img&quot; at 0x8000, at that point there would be a rudimentary Aros alive. If one wants to use the SD-card then there would have to be a driver for the interface and a fat filesystem handler (SD-card has to be formatted to fat filesystem)

Boot code and kernel are now linked together and made into that binary blob, just for starters. Raspberry Pi uses [http://kernelnomicon.org/?p=133 u-boot] and [http://kernelnomicon.org/?p=138 UBoot] as bootloader, there's already some code in the Efika MX port for that. UBoot is a native bootloader and not just for the raspberry pi, it loads after start.elf.

You can find Efika MX port from arch implementations, some hacking is needed for the mmakefile.src'es as iit dates back to before the Aros crosstool era or else you get some weird errors while building. You also need to code the bootstrap and serial handling.

At the moment it seems that a fastest route for the native build would be to make one binary blob without using the package system. Raspberry's memory layout is pretty simple and if the implemented u-boot doesn't support loading other modules 

&lt;pre&gt;
?          - alias for 'help'
mtest      - simple RAM test
autoscr    - run script from memory
base       - print or set address offset
bbm        - BBM sub-system
bdinfo     - print Board Info structure
boot       - boot default, i.e., run 'bootcmd'
bootd      - boot default, i.e., run 'bootcmd'
bootm      - boot application image from memory
bootp      - boot image via network using BootP/TFTP protocol
cmp        - memory compare
coninfo    - print console devices and information
cp         - memory copy
crc32      - checksum calculation
echo       - echo args to console
fatinfo    - print information about filesystem
fatload    - load binary file from a dos filesystem
fatls      - list files in a directory (default /)
go         - start application at address 'addr'
help       - print online help
iminfo     - print header information for application image
itest      - return true/false on integer compare
jade       -
loadb      - load binary file over serial line (kermit mode)
loads      - load S-Record file over serial line
loady      - load binary file over serial line (ymodem mode)
loop       - infinite loop on address range
md         - memory display
mm         - memory modify (auto-incrementing)
mtest      - simple RAM test
mw         - memory write (fill)
nfs        - boot image via network using NFS protocol
nm         - memory modify (constant address)
pci        - list and access PCI Configuration Space
ping       - send ICMP ECHO_REQUEST to network host
printenv   - print environment variables
rarpboot   - boot image via network using RARP/TFTP protocol
reset      - Perform RESET of the CPU
run        - run commands in an environment variable
saveenv    - save environment variables to persistent storage
saves      - save S-Record file over serial line
setenv     - set environment variables
sleep      - delay execution for some time
tftpboot   - boot image via network using TFTP protocol
USB        - USB sub-system
usbboot    - boot from USB device
version    - print monitor version
&lt;/pre&gt;


And there is one more thing about modular ports. In order to actually implement this, your bootstrapping environment should provide the ability to load several files. On PC this is provided by GRUB2. on CHRP you can read filesystem via OpenFirmware, and Sam's Parthenope relies on modified u-boot. If your bootstrap allows to load only a single file, then you stuck with monolithic kickstart. By the way...  u-boot allows not only to boot up a single uImage or zImage, it also allows to write client programs AFAIK. With this approach, you actually can write modular bootstrap for ARM AROS using unmodified u-boot.

Most used [http://www.compulab.co.il/workspace/mediawiki/index.php5/U-Boot_quick_reference uboot options] are fatls usb 0:1,

the reason behind INTB_KERNEL is to allow use of the standard Exec function AddIntServer() to add interrupt handlers for
hardware drivers etc. AmigaOS never used it for abstract hardware drivers. AmigaOS  routed  only  raw  hardware IRQs there. Their assignment was hardcoded. As well as number of them. Actually on AmigaOS every bus has its own interrupt subsystem. For example PCI bus. PCI interrupts on Amiga are routed to a single exec interrupt.  1:1 relationship between CPU  and hardware interrupts is present only on PC.

IMHO we miss things like AddInterrupt/RemInterrupt methods on our PCI subsystem's device class.  PCI bus class should map these methods to whatever is appropriate. This is how it is done on AmigaOS and friends. When these are implemented, raw kernel.resource API will be needed only for several PC-specific drivers with hardwired resources. Exec IRQs are real IRQs only on Amiga hardware. On other machines they can be emulated where appropriate (VBlank is a good example). kernel.resource is meant  to be different, its IRQs are hardware-agnostic, they are plain &quot;Hardware IRQ number X, whatever this means&quot;. They are low-level actually, and meaningful only in the context of a particular system.

Was that not the transition from irq.hidd to kernel.resource? No.  A long time ago there was another hacky bit named INTB_TIMERTICK. It was &quot;abstract timer interrupt&quot;, used by timer.device. It was the same as VBlank, but with larger frequency. I removed it, because kernel.resource API was a cleaner way to access this interrupt. Furthermore, there can be more than one timer in the system. Thinking about bringing back timer HIDD definitions again. hpet.resource is a bad idea.

Can someone please enlighten me a little on how the scheduler is meant to work?
 
Poseidon.library creates its &quot;Poseidon Event Task&quot; during RTF_COLDSTART -&gt; then calls Wait(), and ends up in limbo because wait disables interrupts (used for the scheduler heartbeat), and basically waits forever because the sigbit is never set, since krnSwitch doesn't switch the task unless TF_SWITCH is set, and no codepath run during this seems to set it?? TF_SWITCH does not disable/enable switching. This flag just enables to run user-supplied hook when the task is being switched away. It is completely safe to call Wait() in Disable()d state. Doing this actually temporarily breaks this state. IDNestCnt gets remembered in struct Task, then next task is selected, and its IDNestCnt is restored in sysbase (see kernel_scheduler.c). If there are no other tasks, then your cpu_Dispatch() should enable interrupts on the CPU and enter idle mode. See x86 implementation for good example.

You miss what happens next...
 1. KrnSwitch() saves context of your task, saves IDNestCnt (core_Switch() and cpu_Switch()), then drops into cpu_Dispatch().
 2. cpu_Dispatch() calls core_Dispatch. Then two cases are possible:
 2a. There is a READY task. It is picked up, its IDNestCnt is restored in SysBase, then cpu_Dispatch() needs to restore registers and exit. The next task is run.
 2b. There are no READY tasks. core_Dispatch() returns NULL. In this case your cpu_Dispatch() should enter idle loop. It should just enable interrupts on the CPU and put it on halt. This allows it to process hardware interrupts. Eventually some of your interrupt handlers wakes up your task and puts it into READY list.

My heartbeat interrupt has been slowed atm to help debugging - but it never actually gets a chance to fire because of the Wait() disabling interrupts. Perhaps you have forgotten to enable interrupts in your idle loop.

There is a change in the format of AROS executables. Until now we were using Elf RELocable files which are usually used as intermediate object files. We had them for various reasons, one of them was how AROS files were built in the past. That days we had no real aros cross compiler and the option to embed relocation data in unix executables (or in executable files in general) was rather new and not every linux/unix system had it. Therefore we have decided to use intermediate files. Although it was somehow working (and it is still working :-)), it has some drawbacks. Therefore decided to introduce real Elf EXEC types, in first turn implemented on ARM target with option to expand in future to all other AROS architectures.

The first patch was pretty easy and appeared to work somehow. It generated nice executables with embedded relocation info. Not only that, it also removed all global symbols adjusting relocation data to be relative to the beginning of the sections. That move reduced number of symbols in each executable significantly (depending on the file between 20 and 80% of all symbols could be removed). The only symbols that stayed in the file are local ones - due to the nature of the patch wasn't able to remove them since we have not seen them in the symbol hash table.

The patch didn't worked though. The files were relocated, AROS kernel loaded, but it crashed very early. What happened? Well, the nature of ARM relocations happened :)

Most of the relocation data on all machines is rather simple. Relocation can be absolute or pc-relative, sometimes the offset has to be bit shifted. On ARM v7 there is another one. There, when one wants to load an address of function/variable into register a combination of two instructions can be used: movw and movt. The first one loads immediate into lower 16 bits of a register while clearing upper 16 bits. The second one loads immediate into upper 16 bits without touching lower halfword. Loading of a pointer into a register looks like this:

        movw r0, #:lower16:label

        movt   r0, #:upper16:label

In this case there are two relocations - one for lower halfword and another for upper. If an overflow of lower 16 bits occurs during relocation process, the upper one should be updated as well. Unfortunately with current patch and with typical ARM executables there is not enough information to perform the calculations.

There are two options - the first one would be to give up and go back to &quot;fake&quot; executables, another one would be to change from REL to RELA relocation info. The latter contains an addend, extra data which can be used to perform all the relocation calculations I need.

Decided for the second option. The patch is already in the works. There is another function for the binutils' bfd backend to perform the final relocation. There can decide what to do with every reloc info, modify data and eventually strip some symbols. An advantage is - at this stage of the linking process have also full access to all local symbols so can change all relocations section relative and eventually strip all symbols from the files. 


 GPU 

VCore developed by Alphamosaic Ltd and now owned by Broadcom. Most of start.elf runs on the GPU.   Placing ALL the userland GPU code in the videocore.hidd isn't going to be a terribly big problem because the code they published is nothing more than a shim that sends data straight to the GPU to execute.

The good news about this is that we only need to write our HIDD using the OpenVG API.   The shim is relatively small codewise and lives in the ARM memory (the actual OpenVG code itself lives in the GPU RAM area and its loaded from start.elf).   That's also the bad news.  Our driver has to translate AROS video calls to OpenVG calls, for most tasks it should be easy, for some, not so much.  It's still probably less difficult and less work, than controlling the GPU directly.

The other good news is that anything done through OpenVG happens on the GPU, its truly accelerated.   It also has some nice font functions, meaning we can lead into an accelerated text mode later.

Basically, AROS resets or locks up when it tries to use AROS_ATOMIC_INC or DEC.  If I comment out the byte/word operations in the header files and use non-atomic operations, the code works as expected.
 
have read that the L1 cache needs to be enabled to use LDREX and co (which I also read is only meant to be used on multi processor systems with shared memory) - however I am certain this is correctly enabled.

If you are using LREX or STREX, you should have L1 cache enabled, at least on the ARM CPU I work with at work.

L1 cache is enabled by enabling the MMU *AND* setting the C and I bits in the CPU - the C bit is ignored, and the I bit only covers the 16 byte instruction pipeline if the MMU is not enabled.

Can you verify that your assembly is generating LDREX/STREX? From the behavior, it almost sounds like its generating the default Semaphore locked atomics.
 Impossible. There are no semaphore-locked atomics. There are Disable()/Enable()-based ones instead. And there's a special #define AROS_NO_ATOMIC_OPERATIONS in this case, which tweaks Disable()/Enable() implementations not to recurse forever.
 I have tested this on ARMv5 which does not have ldrex/strex, it works fine. On those ARMs there's no way to have real atomics. On other OSes (like Linux) this is done by introducing things like atomic_t, which appears to be a complex structure, holding the value together with accompanying spinlock (implemented using swp).

    #warning &quot;TODO: lookup optimal mmu table settings for raspi memory&quot;
        /* Set up an identity-mapping for all 4GB */
        for(x = 0; x &lt; 4096; x ++)
        {
            pagetable[x] = x&lt;&lt;20 | (0x40002|0x80000|0x010000|0x00C00|0x04);
        }

Shouldn't there be a second loop that sets the 'C' bit in the descriptor for the RAM pages?

Currently, you have TEX=0, C=0, B=1 for all pages (Shared Device).

You should have TEX=0, C=1, B=0 for RAM (Write-Through, Cached)

    So ..
     
     pagetable[x] = x&lt;&lt;20 | 2;

     
    should be enough?

No, for RAM you need to change the '| 0x40' to '| 0x80'

tell dosboot the correct defaults to use

Please don't do this. This bootconfig.c is a deprecated legacy thing. I wanted it to go away completely with time. Instead,  display  drivers  should auto-install themselves during own initialization phase. I. e. detect hardware=&gt;instantiate itself. This   should   make  things way simpler. With this approach you only need  to add the driver into KS image to get the device autobooted. No hardcoded stuff. 
Currently  VESA  and  VGA drivers do this, look there for examples. never rewrote ATI driver because i don't have any test system for it.

they defined a smaller AROSCPUContext than the ExceptionContext - yet reference it as ExceptionContext in other places, and since it hasn't allocated enough storage for ExceptionContext, are corrupting memory/the structure (since the elements that are there don't map 1 to 1 with the exception context).

AFAIK, AROS has been moving in a different direction to this in recent years. It is the job of graphics HIDDs to allocate bitmaps etc. so that they have the most suitable characteristics, including allocating them from GPU RAM where possible. The concept of chip RAM is only for legacy code, and most if not all non-68k platforms should have all system RAM
marked as chip.

BTW, is the video processing code you mention CPU code or GPU code?

Also, IIRC we have support for &quot;external memory allocators&quot;. Perhaps that's what we need for the allocation of GPU RAM through the mailbox.

All hosted and x86 native ports should use proper context formats.

trying to clarify if the vblank handler has to have run by this point to prevent this deadlock. Actually, no. Unless you have installed VBlank handler which should wake up at some point. Without VBlank there will be no quantum count. Consequently, there will be no forced preemption. But the rest will work, and multitasking will be cooperative (switch happens only when current task voluntarily gives up the CPU). Does it depend on the vblank having run before this point? and if yes what does that mean on systems where it might be able to run enough code (e.g. get to this point) before the vblank interrupt has triggered? What is it waiting for? It could wait for timer, in this case you need timer.device working. VBlank is currently needed for exec's quantum counter. In current native ports we have only a single timer, which is served by timer.device. VBlank is simulated by timer.device also. If your machine has two timers, then you can use one of them for VBlank, and another for timer.device, this will simplify things down. VBlank needs to be 50 Hz for historical reasons, many programs use it as cheap timer. I am periodically thinking about making some abstract mechanism to be able to change quantum source (and untie it from 50 Hz), but have no time to come up with something good. Additionally i started disliking timer.device hardcoded design when PC has got many timers (old 8253, APIC, HPET).
Currently i think there should be some low-level entity representing tick source. timer.device should just select the most appropriate source for its units.
The BCM2835 has 4 GPU based timer sources - 2 are used by the GPU, so im using Timer3 for our heartbeat and the remaining one will be free to the system. There is also the less capable ARM timer but that is dependent on the CPU frequency. Very good. You won't need any emulation. Set the heartbeat to 50 Hz and drive VBlank from it. Use other timer for MicroHZ.

Can you use the 'econsole.hook' I make for debugging the Sam460 via the serial port?
It provides a before-anything-else shell prompt on the serial port.  You can then do 'NewCLI' to test your graphics, or use any DOS command in shellcommands.resource.

You should just be able to add econsole.hook to your module list, and use 'econsole' in your bootargs.

So long as you have a working Exec/RawMayGetChar and Exec/RawPutChar, it should work.

Also make sure to add shell.resource and shellcommands.resource for this.

That should have done it.

If you set &quot;#define DEBUG 1&quot; in  arch/all-native/econsole/econsole.c, do you get any additional serial output?

have added it to the build and added econsole to the command line - and can see the bootloader picks up on the emergency bootconsole tag, but I still only get the insert bootable media display?

Im assuming it exposes a fake filesystem that tricks aros into booting?
The contents of which are: ECON:AROS.boot

Way to handle the scheduling code? The implementations I had been following were causing problems, due to cascading interrupts which I cant handle properly in the asm stubs just now (when they break disable etc.) - since it means detecting the interrupted codes cpu mode and getting the correct sp/lr for it, and that's just too tedious for arm.
 
To work around this ive added a system idle task which does nothing - and when the scheduling code has no task to run switches this in and lets it run, thereby allowing the interrupts etc to resume until something does need to happen.
 
Also, by adding accounting code to cpu_Switch() and cpu_Dispatch(), it should allow the system to log idle time correctly (as well as running tasks).
 
have thought of also adding an additional task that never runs, solely to record time spent in IRQ handlers, but I digress..

was under the impression that kernel.resource should *never* be used outside of exec.library. This is a wrong impression.
Michal started designing it because portable nature of AROS does not fit well into exec's API with all its assumptions. So, he started the new, hardware-agnostic kernel API from scratch. Yes, exec sits on top of it in places. But kernel always meant to be open thing. Otherwise it would not exist. 
it wasn't meant to be just used willy nilly by user code - but by lower system components (e.g. exec) so that they could be implemented in a more generic fashion, and the kernel resource itself hide the systems quirks.

Adding new things there perfectly keeps up with our decision to minimize AROS-specific intervention into APIs which can clash with MorphOS or Amiga OS4 extensions. We want at least source-level compatibility there. Binary compatibility on PPC would be extremely cool, but at the other hand we have no maintainer for this, as well as their ABIs splintering. 
It depends on what exactly is being implemented - there's no reason we should have everything crammed into kernel.resource if it doesn't need to be (i.e. if its better suited as a separate component/subsystem in its own right)

The _LE versions are for when you have endian swapping taking place.  If the graphics are the same endian as the CPU, no swapping should occur.  I ran into a similar terminology problem in SDL with a friend insisting that his Radeon 7000 on his PC was big-endian.  It is not, it just uses the same endianness for the graphics card and the CPU so no swapping was necessary.  They were both little-endian.
The _LE versions are because the PixFmts refer to the bitmap data being in big endian format in memory, for which the normal version would need to do endianness conversion before applying the shifts/masks. on this platform it is in _LE in memory also so we don't need the conversion hence using the _LE version of the call). would use _LE (if it's really little endian 16 bit mode).

 
What is the bare minimum needed to implement a framebuffer based gfx driver, with our software handling the rest?

Have tried with just a gfx class that only expose new/dispose/newbitmap - and having an onscreenbitmap used only for the framebuffer itself (with all other bitmaps being chunkybm, and the framebuffer's superclass also being chunkybm), but that alone isn't enough it seems?
You can use workbench/hidds/sm502/ as your example - it is as simple as I could make it.
So, AROS creates the framebuffer bitmap (verified this) -&gt; so surely it should be capable of then rendeing into it? I don't actually create the framebuffer &quot;bitmap object&quot; myself - only as a result of being asked to. The code I currently have on SVN seems to create the framebuffers bitmap object fine, but then crashes in intuitions DisplayDriver callback.  In particular it crashes performing the getattr on the system default pointer. don't expose MEMF_CHIP in an allocatable form so AllocSpriteData was failing (and other code later doesn't check if the values are valid == illegal memory accesses) 

So far have -:

vc_init: queries the gpus memory, and sets up a fake memory handler for it, then adds the bootmode driver and returns saying all is well
vc_gfxhidd:New: sets up some fake syncmodes to test with and creates the real gfx object.
vc_gfxhidd:NewBitmap: checks if its a framebuffer and uses the onbitmap class or uses the chunkybm class otherwise
vc_onbitmap:New; creates a chunkybm object and then pushes the real framebuffer address into it as the buffer,

vc4 had v8adds, v8subs, v8muld, v8min and v8max which operated on four 8bit uint values packed into a 32bit register. Multiplication was in the range 0.0 to 1.0 and addition/subtraction saturated. There were also a range unpacking/packing modes that allowed you to pack and unpack 8bit values into 32bit registers. 

RasPi has to speak to the &quot;operating system&quot; which runs on the GPU itself and request/free memory - it cant directly manage it itself, and so the managed functions were used to wrap these calls.

The Arm and GPU share memory space. The framebuffer is shared. The Arm can write a pixel and it will appear on the screen (through GPU hardware) without flushing/copying being required.

The GPU can composite multiple FB's in real time - so you have a number of surfaces defined which are rotated etc and  composited in real time to the output. Copying can map from the address space of the Arm to the flat space of the GPU which takes some code, but I don't think whole buffers are copied.

The DMA hardware can also access the whole memory space and can perform 2D fills and blits (no blending). This is documented in the peripheral spec posted. The DMA is just an Arm accessible peripheral and can be set up with low latency (e.g. microseconds).
must use a 0xc0000000-based bus address to access SDRAM, yet non-DMA access should go via a 0x0-based bus address. 
For 2D dma, set TDMODE, and the spec says &quot;interpret the TXFR_LEN register as YLENGTH number of transfers each of XLENGTH, and add the strides to the address after each transfer.&quot; so set STRIDE to pitch of the image, the width is XLENGTH and height is YLENGTH. You would fill by not setting the SRC_INC and point source to your fill data.

The DMA cannot see the ARM's L1 cache, so you would map the framebuffer with ioremap_nocache. Depending on where the source data comes from, it may need an L1 cache flush. The DMA can see the L2 cache. Use 0xC0000000 bus addresses when L2 is disabled and 0x40000000 bus addresses when L2 is enabled. (actually just call virt_to_bus and you'll get the right address out).

openGLES/openVG has high latency. Writing to framebuffer then reading it back is very inefficient (e.g. milliseconds). If you can drive it a unidirectional way, just streaming commands at then that is efficient. openVG is not implemented on top of openGLES - it uses the same hardware but as a first class interface

To improve the Gfx driver, we will need a DMA resource implemented so can use to perform DMA operations. The Gfx driver will need this to perform blits.


Actually MEMF_CHIP has to present, for historical reasons.
This has been never fully agreed upon, but in ports i wrote i exposed the whole memory as MEMF_CHIP. The idea behind this is that CHIP is originally the memory where graphics and sound data can be put. On non-Amiga platforms there are no restrictions on this, so the whole memory is CHIP.
Yes, many old software can misbehave with CHIP memory size larger than 2MB. But this actually applies only to m68k AROS which is going to run m68k binaries. In other cases it's quite logical to fix the program when porting.

As to original question: yes, it's enough to have a framebuffer bitmap (one with aoHidd_BitMap_FrameBuffer set to TRUE) and PutPixel routine. It framebuffer can be served by chunky bitmap class, then you can simply create chunky bitmap with your own buffer (see how VESA driver does this). Chunky PutPixel is already there.

struggling to determine what is the correct pixfmt to use for the 24/16/15 bit gfx modes on the RasPi.  AFAIK it uses RGB565, for 16bit but im unsure what shifts etc should go with it? suffice to say Im getting the wrong colors so far lol.

&lt;pre&gt;
redmask: 0x0000F800
greenmask: 0x000007E0
bluemask: 0x0000001F
alphamask: 0

redshift: 16
greenshift: 21
blueshift: 27
alphashift: 0
&lt;/pre&gt;

It should likely be vHidd_StdPixFmt_RGB16_LE

This stuff is a bit confusing.  The &quot;names&quot; of the stdpixfmts are based on the layout in memory,
ignoring endianess. So for example:

ARGB32: will be 0xAA 0xRR 0xGG 0xBB in memory on both big endian and little endian machines.

The shifts and masks OTOH are based on pixel access (ULONG in this case), so differ depending
on whether you run on big endian machine or little endian machine (that's why there's stdpixfmt_le.h and
stdpixfmt_be.h in rom/hidds/graphics/).

With the 16 bit pixel format it's even more confusing, as for example it's impossible on little endian machine
to describe RGB16 with shifts/masks alone. That's why there's vHidd_PixFmt_SwapPixelBytes_Flag.
(RGB16 == RRRRRGGG GGGBBBBB in memory, and for pixel (WORD) access on little endian machine it needs to
be accessed as GGGBBBBBRRRRRGGGG).

The shifts btw indicate how much to shift the component to the left (!) so that it is moved to the highest bit (31).

The aHidd_PixFmt_StdPixFmt you specify will be ignored most of the time, because when the pixelfmt is registered,
the gfx hidd checks if there's an identical pixfmt (shifts/masks/etc., but ignoring pixfmt-&gt;stdpixfmt) already in the system,
and if so, it uses the already existing one and does not create a new one.

In theory it would be better if gfx drivers could simply/only specify a StdPixFmt without all the shifts/masks stuff when the
gfx driver uses pixfmt which matches one of the stdpixfmts exactly. Another possibility would be for gfx drivers to use
HIDD_Gfx_GetPIxFmt(stdpixfmt_gfx_driver_wants_to_use) and then peek shifts/masks from it and fill out a pixfmt
tag list based on that.
15bit very blue/green: Try to pass same shifts/masks/etc. as in 16 bit pixfmt (maybe you think it's using 15 bit R5G5B5
(or swapped) but it's actually still using 16 bit R5G6B5 (or swapped).
 aHidd_PixFmt_StdPixFmt you pass is mostly ignored. It's the shift/masks/etc. that count.
But I would still pass the correct one (_LE) == whatever rom/hidds/graphics/stdpixfmts_??.h uses
in the entry where you have looked up shifts/masks/etc.

Use the shifts/masks/etc. from the entry in stdpixfmt_le.h (if you are running on little endian machine) or stdpixfmt_be.h (if you
are running on little endian machine) that matches the pixfmt that its meant to be.

0xAA,0xRR,0xGG,0xBB on little endian (-&gt;entry in stdpixfmt_le.h which says vHidd_StdPixFmt_ARGB32)
0xBB,0xGG,0xRR,0xAA on little endian (-&gt;entry in stdpixfmt_le.h which says vHidd_StdPixFmt_BGRA32)

0xAA,0xRR,0xGG,0xBB on big endian (-&gt;entry in stdpixfmt_be.h which says vHidd_StdPixFmt_ARGB32)
0xBB,0xGG,0xRR,0xAA on big endian (-&gt;entry in stdpixfmt_be.h which says vHidd_StdPixFmt_BGRA32)

it feels like AROS trashes the alpha component, otherwise it should be 8A8R8G8B.

read on the subject suggest its in 1x5r5g5b (x is ignored) to keep 16bit alignment .
 
Suggests to me that wrong shift/mask are being applied - however going by the 16bit versions it all looks correct to me so I am really confused as to what is happening.

The output image looks to have too much green/blue, and very weak red.


 Kickstart 

The  idea  is  to minimize amount of archirecture-specific modules to make the user's  life  easier.  So,  the kickstart was split into 'base' (which  does  not  contain anything machine-specific) and 'BSP' (Board Support Package) which contains all hardware-specific stuff. This  way,  for  example, distribution makers can save up space on CD and  make  CDs with multiple platform support. Different configuration would load the same base with different BSP's.

Next  there  was some part which is entirely missing on hosted. These are   filesystems.  Hosted  ports  do  not need them to boot up, so on hosted   they  are  left  out.  At  the  other  hand,  they  are  also architecture-agnostic.  So  i put them into 'FS' package (standing for 'filesystem').


 USB 

Poseidon  is  one  more  big part. I made it into separate package in order to allow users to omit it if they don't need it (for example, to run  on retro PCs without USB). Personally i have one. Again, Poseidon is  hardware-agnostic (well, there are USB drivers but HCIs are pretty standard).

AFAIK its HCI 1.0 compliant but not familiar enough with poseidons drivers, nor USB, to just hack away at the existing code.  Perhaps once i'm more familiar with the workings I can merge in the changes needed to get it operating but for now I will focus on getting it running.  Also our drivers have known issues so perhaps a fresh set of eyes might shed some light on what is going wrong.

Another interesting question is whether Poseidon can operate on device side. Is it flexible enough? How similar is being a USB host and USB device? think it will need a bit of work on Poseidon's side.  Until then I will force the driver into Host/Master mode in the init code, but leave open device etc to configure the chipset for either's use - and look at trying to add support for working in Device/Slave mode &amp; switching modes once it's up and running.

Actually USBROMStartup is some kind of kludge. Can there be any alternative? Could device drivers be self-installing, like our HIDDs? This would get rid of need to list them in USBRomStartup.

* Model A and B limited to 150 mA per port. 
* Model B+ and Pi 2 introduced configurable 600 mA to 1.2 A support over all ports - anything above that requires a powered USB hub.

Implementing the hardware driver that Poseidon uses to interact with the USB components.

Have code in place to (try) and initialise the USB chipset, and configure host/device mode operation (though AFAICT Poseidon doesn't support device mode). Started to get the &quot;virtual&quot; root hub written for the single USB port so that Poseidon should at least list it correctly in the GUI - and try to interact with it to find peripherals.


The BCM2835 uses a soft IP block from Synopsys’ DesignWare library (DWC), specifically the block is called dwc_usb_2_0_hs_otg_subsystem-ahb_se (“USB 2.0 Hi-Speed OTG Controller Subsystem w/AHB Interface SE”).

There is no public documentation for this, and pretty much zero chance of anyone getting hold of it even with NDA. However, there's a Linux driver written by Synopsys ([https://github.com/raspberrypi/linux dwc_usb]). Specifically directories [https://github.com/raspberrypi/linux/tree/rpi-patches/drivers/usb/host dwc_common_port] and [https://github.com/raspberrypi/linux/tree/rpi-patches/drivers/usb/host dwc_otg].

The Synopsys code is actually under a fairly permissive licence – it's not GPL, it's similar to BSD (’don't sue us if it breaks’ is pretty much the only clause). So this should not be a barrier to porting the code.

The code is really well written, with a nice partition between the work done by the driver (dwc_otg, which is fairly involved, given the host does more work than a conventional EHCI driver), and the interface to Linux (dwc_common_port).

Probably only need provision of relevant changes to dwc_common_port. Other things to consider....

* Provision of necessary headers to get it to compile
* Provision of necessary functions (main issues are wait queues, threads, work queues, tasklets, timers, spinlocks and mutexes (multithreading) )
* Interfacing between USB stack and the driver. dwc_otg/dwc_otg_hcd_linux.c looks like the place to start.

the Linux bits of the headers are only required for the dwc_common_port library. dwc_common_port includes a variety of crypto functions which are not used – it appears to also be used for ultrawideband (UWB) and wireless USB (WUSB) drivers where crypto will be an issue, but it isn't going to be for plain wired USB.

Every USB driver acts as an USB hub as well in order to let Poseidon control the state of USB ports. The code there was reading status of the only USB port in Raspberry's CPU but when changing the status it erroneously deleted some of the status bits, including the port enable one. It was so because those bits in the status register are of a type Read/WriteToClear. It means, if one does not want to change their value from 1 back to 0, one has to actually write the 0 value. Very practical thing e.g. in interrupt handlers, where one reads the interrupt status register to learn what was the interrupt reason, and writes it back to the same register in order to clear the interrupts. 

After fixing that code it turned out that the communication was still unsuccessful. Apparently the USB device was not understanding the host for some reason. That should not happen since the request sent was one of the standard ones implemented by virtually anything with an USB connector, assumed that Poseidon clears the data caches before forwarding the work to the USB drivers but that's the responsibility of the driver itself. 

The USB device responded and acknowledged the transmission! But why were all the request sent after address change failing with timeout? They should not. Once again, address set is supported just by anything. Tried to contact the device at address 0 once again and there it was, still responding properly. The enlightenment came. The bus address for DMA transmissions was, as it is in many bare metal USB implementations, just the pure memory address of the buffer as seen by the ARM cpu. Have &quot;prefixed&quot; it with the real location of uncached RAM and booted AROS once again. 


Trident saw this:

    Product     : Hub: Vdr=0424/PID=9514
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 9
    SubClass  : 0
    DevProto  : 2
    VendorID  : 1060
    ProductID : 38164
    DevVers   : 0200

and this:

    Product     : Vendor: Vdr=0424/PID=EC00
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 255
    SubClass  : 0
    DevProto  : 1
    VendorID  : 1060
    ProductID : 60416
    DevVers   : 0200

and even this:

    Product     : Hub: Vdr=0424/PID=9514
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 9
    SubClass  : 0
    DevProto  : 2
    VendorID  : 1060
    ProductID : 38164
    DevVers   : 0200

What are these things? The first one is USB hub built in the Raspberry. Thanks to this one the Pi machines (with exception of Pi0 and computing modules) have more than just one single USB port. The second one is the network chip in raspberry, the third one is my USB SD card reader which have just connected to see what happens. AROS tried, of course, to boot from it ;)

So, the first step towards working USB is done. The control transfers are working as you can see above. Next step is to implement bulk and interrupt transfers, having the basics in place. Finally some error handling will be added and USB for Pi will be as complete as the PC version. 

[http://www.raspyfi.com/raspberry-pi-usb-audio-fix/ Issue with USB Audio]


 Audio 

The Pi 4B is the only Pi that can output HD Audio as an HD Audio passthrough bitstream, and it does it over HDMI. It's possible to use the two HDMI output for separate HDMI video and HDMI audio outputs to allow UHD HDR video and HD Audio with non-UHD HDR compatible AVRs. 

The Pi3B+ and earlier will decode to PCM 5.1/7.1 and output over HDMI.  HDMI is the only interconnect that has a standard for carrying Dolby True HD, DTS HD MA etc. as a bitstream - you can't carry it as a bitstream on any other interface.

Pi3 and Pi4 audio jack output derived from 12bit pulse width modulation is relatively poor. For better, choose USB Audio or I2C versions. 

[https://github.com/raspberrypi/linux/tree/rpi-patches/sound/arm audio] and its [https://github.com/raspberrypi/firmware/issues/2 very high speed message passing interface type of thing VCHI] 

The Model B+ added an additional voltage regulator for the audio output and an additional output driver to drive low-resistance loads like headphones. However it is still using pulse-width modulation (PWM), which has a major impact on sound quality

the old Raspberry Pi used a linear voltage regulator to provide the 3.3V to many of the components on the board while the new one uses a switching regulator. Both can perform reasonably well. However switch mode power supplies often show higher noise figures

Analogue audio

Audio over HDMI rev 1.3 &amp; 1.4


 Ethernet 

10/100 BaseT Ethernet RJ45 socket


 GPIO 

GPIO shouldn't be too bad but bear in mind it is already accessed in places so they would need to allocate pins etc through it (e.g. sdcard to flicker the activity light, serial debug to output data on the GPIO pins)

Probably a resource rather than a device...

Started an i2c driver that will need to allocate GPIO pins. Feel free to work on it if you are interested ;p


 GPU graphics with 2D and 3D acceleration 

Sadly none yet for 32bit but for 64bit... 


 Miscellanous

hdmi issues

Setting the hdmi_force_hotplug=1 makes sure the Pi believes the monitor/TV is really there.

You might also need to set config_hdmi_boost=4 or even higher (up to 9) if your display needs a stronger signal.

If the display is a computer monitor or newer tv, use hdmi_group=1 (auto HDMI use) and if it is an older TV, try hdmi_group=2 (for DMT formats, i.e. for PC monitors) then you HAVE to &quot;set hdmi_drive = 2 to enable HDMI output as this forces HDMI mode rather than DVI mode

Do not set hdmi_safe=1 as that overrides many of the previous options.

Using a shorter or better quality HDMI cable might help. Make sure your Pi's power supply delivers 1 A and not 500 mA.
If you see a problem with the red colour - either absent, or interference - then try a boost

composite video

changing the RCA cable, then the composite port worked out of the box

Boot it as you are doing, without HDMI. If you now plug in the HDMI, do you get the image? In other words, does the Pi think HDMI is connected even when it isn't?

Rename all the files in the first partion of the card except bootcode.bin, start.elf and fixup.dat  What's the result?

Put back config.txt What's the result?

for PAL mode   sdtv_mode=2

dmi_ignore_hotplug Pretends HDMI hotplug signal is not asserted so it appears a HDMI display is not attached
hdmi_ignore_hotplug=1 Use composite mode even if HDMI monitor is detected

&lt;pre&gt;
# NOOBS Auto-generated Settings:
#hdmi_force_hotplug=1
#config_hdmi_boost=4
#overscan_left=24
#overscan_right=24
#overscan_top=16
#overscan_bottom=16
#disable_overscan=0
start_x=1
gpu_mem=128
&lt;/pre&gt;

tvservice -c &quot;PAL 4:3&quot;

&lt;pre&gt;
/opt/vc/bin/tvservice -s   or tvservice -s 
state: HPD high|HDMI mode|HDCP off|composite off (0x12001a), 1920x1080 @ 60 Hz, progressive

/opt/vc/bin/tvservice -m CEA
Group CEA has 1 modes:
(native) mode 16: 1920x1080 @ 60 Hz, progressive

/opt/vc/bin/tvservice -m DMT
Group DMT has 0 modes:
&lt;/pre&gt;

sudo amixer cset numid=3 1

forces the audio to the headphone jack, even with the HDMI video output plugged in

config.txt

the hdmi_ignore_edid_audio=1 option sems relevant as it should tell ALSA that the only available audio is analog, no matter what the display says

There are several different ways that these 4 pole (ring) composite analog cables can be wired up, so some work great in some applications and can be a waste of time in others.

What is needed for the Raspberry Pi B+ and above, which like many camcorders needs the ring contact next to the base contact to be the ground.


The wiring for the 4 pole are:

TIP (LEFT AUDIO CHANNEL)

RING 1 (RIGHT AUDIO CHANNEL)

RING 2 (GROUND/EARTH)

RING 3 BASE/SLEEVE (VIDEO) YELLOW

Most Apple based Players and the Microsoft Zune (TM) are wired this way.

Most analogue camcorders are wired this way as well, where the ground in on Ring 2 will work with the Pi although you may need to swap your Video plug with the Right Audio plug.

Nearly all other MP3 players are not wired this way, the ground is on another ring ie the wrong one.


External devices

* Camera Module Omnivision ov5647 Sunny 5MP (NoIR version) V1.3 - NoIR at 850&amp;nbsp;nm, peak at 880&amp;nbsp;nm and trails off at 940&amp;nbsp;nm wavelengths 
* Camera V2 Sony IMX219 V2.1 8mpixel 8MP 8megapixel - 3280 x 2464 pixels - video at 1080p30, 720p60 and 640x480p90 - wider field of view, 62 vs 54 degrees horizontally - 
* Branded WIFI usb BCM43143 dongle

N.B.  dreaded error after changing cameras (stupidly without turning off the power first) and lasted through several power cycles.  It can be a bad 15-pin FFC ribbon cable, when swapped, camera(s) and the Pi itself are working OK. It can be an instance of a cold solder joint on the CSI connector on the pi board.  the camera can be detected (that's done via I2C) but may still not be able to receive image data (done via CSI-2) if something is broken. CSI-2 is uni-directional. Control is generally done via I2C. 
The CSI-2 receiver always writes to memory, not direct to the ISP. That's the way the Broadcom architecture works as it allows multipass processing easily. GPU memory is accessible from the ARM. Processing using the QPU graphics processors may be possible.  currently the only supported sensor is OV5647 and IMX219.  The linux drivers are all in the firmware blob, else you'd  be looking at at least a man-month of work in a fully fledged imaging lab to do a decent tuning of the camera modules' ISP parameters. 
Static electricity maybe an issue for the camera module and slightly less for the pi board.


== References ==


===Good sites to visit===

*[https://github.com/raspberrypi/firmware/tree/master/ Raspberry Pi Firmware build] 
*[https://www.raspberrypi.com/documentation/computers/software-sources.html Documentation] 
*[https://rpilocator.com/ RPiLocator] 


Linux only
*[https://github.com/raspberrypi/linux Raspberry Pi Linux Build] 
*[https://dietpi.com/ DietPi] 
*[http://www.tinycorelinux.net/ports.html piCore]
*[https://wiki.alpinelinux.org/wiki/Raspberry_Pi Alpine Linux] 
*[https://github.com/armbian/build Armbian] 


*[ FydeOS]
*[ TwisterOS based on ChromiumOS] 
*[https://note.com/jamesmondo/n/nc76e31402be8?hl=en BSD] 


*[https://www.raspberrypi.com/software/operating-systems/ PiOS Lite] and then [https://hstwb.firstrealize.com/ HST] 
*[ PiMiga for pi4 and pi5] 
*[ amibian for pi2 and pi3] 
*[ retropie pi1 and 2] 


Other alternative lighter smaller than Pi OS 
*[https://aros.sourceforge.io/nightly1.html Aros 64bit ARMV8 single core] 
*[https://www.riscosopen.org/wiki/documentation/show/Welcome%20to%20RISC%20OS%20Pi RiscOS on Pi3 and Pi4]
*[https://github.com/michalsc/Emu68 ARM based realtime JIT 68k for amiga computers] 
*[https://github.com/JJDSNT/bellatrix/releases/ Alternative use of Emu68 on Pi3b] 
*[https://github.com/stevereaver/uaos uaOS with Emu68k] 
*[https://github.com/aros-development-team/AROS/commit/f80a268607dfae81b2db94755ab4e4d31ccb72d6 m68kemu library reference] 
*[ HaikuOS]
*[https://github.com/raspberrypi/noobs NOOBS] os loader with successor [https://github.com/procount/pinn PINN] 
*[https://github.com/maxnet/berryboot berryboot]

*[https://github.com/brianwiddas/pi-baremetal Bare Metal Access on Pi 32bit] 


Testing procedure is put sd card in, connect board to board if necessary, plug in hdmi and then power nothing else is done especially CSI DSI etc 

[https://www.raspberrypi.com/documentation/computers/compute-module.html CM5] has the same 55mm x 40mm 2x100pin connectors form factor as the CM4 but [https://www.epdtonthenet.net/article/214508/Key-Considerations-When-Migrating-from-Raspberry-Pi-CM4-to-CM5.aspx some pins and other small things] have changed. Will need the [https://raspipcb.com/tech-blog/raspberry-pi-cm4-vs-cm5-difference-in-booting-from-sd-card/ right IO board to suit] 

*Green [ Raspberry Pi Compute Module 5 IO Board REV2 [https://pip.raspberrypi.com/categories/1097-raspberry-pi-compute-module-5-io-board SC1967]] - untested 
*Green [ RPi Compute Module 5 IO board REV1 [https://pip.raspberrypi.com/categories/1097-raspberry-pi-compute-module-5-io-board SC1751]] - untested 
*Black SupTronics Geekbord X1500 CM5 IO Carrier Board - untested
*Black DeskPi Super6C Cluster Mini-ITX Board - untested 
*[https://sipeed.com/nanocluster Sipeed NanoCluster] - untested up to 7 CM5 
*Green BentoIO CMX0 - untested 
*Box EDATec ED-CLAWBOX - untested 
*Home Assistant Yellow - Kit with PoE with Raspberry Pi Compute Module 5 - untested 
*Blue [https://www.waveshare.com/wiki/CM5_PoE_BASE_A Waveshare CM5-PoE-BASE-A] - untested 
*Box  Waveshare [ CM5-POE-BOX-A] - untested 
*Blue [https://www.waveshare.com/wiki/CM5-IO-BASE-B Waveshare CM5-IO-BASE-B] - untested 
*Blue [https://www.waveshare.com/wiki/CM5-IO-BASE-A Waveshare CM5-IO-BASE-A] - untested 
*Blue Waveshare [https://www.waveshare.com/wiki/CM5-NANO-B CM5-NANO-B] - untested 


*[https://carboncomputers.us/products/pi-flux piFlux]
*[https://carboncomputers.us/products/ Zitaotech Hackberry] CM5 lite only - 
*Portable [https://www.waveshare.com/pocketterm35.htm Waveshare PocketTerm35] with Pi4B or Pi5 - untested 
*Box [https://www.clockworkpi.com/uconsole ClockworkPi uConsole][https://www.youtube.com/watch?v=EtI_bAahbR8 CM4 into an adapter or CM3 into so-dimm - Cyberdeck] - untested 


*Green RPi [https://datasheets.raspberrypi.com/cm4io/CM4IO-KiCAD.zip Compute Module 4] [https://datasheets.raspberrypi.com/cm4io/cm4io-datasheet.pdf IO board] V1.4 [https://datasheets.raspberrypi.com/cm4io/CM4IOUSB3-KiCAD.zip USB3] [https://datasheets.raspberrypi.com/cm4io/cm4iousb3-appnote.pdf CM4ISO] [https://datasheets.raspberrypi.com/cm4/cm4-datasheet.pdf Dual100pin] (2020) aka Development Platform Board - untested 
*Purple Pi Hut Cytron CM4 Maker Board - untested 
*Black DeskPi Super6C Cluster Mini-ITX Board - untested 
*[ KubeSail PiBox mini 2] 
*Home Assistant Yellow with Raspberry Pi Compute Module 4 - untested 
*[ Turing Pi V2] - untested CM4 with 260-pin SO-DIMM socket adapters and/or nvidia jetson nanos - untested 
*Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-C Waveshare CM4-IO-BASE-C] - untested but binary blobs Rev01 Rev02 
*Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-B Waveshare CM4-IO-BASE-B] - untested but binary blobs 
*Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-A Waveshare CM4-IO-BASE-A] - untested but binary blobs 
*Blue [https://www.waveshare.com/wiki/CM4-NANO-B Waveshare CM4-NANO] - untested but usb and audio turned off or rerouted 
*Black [ Seeed Studio with BigTreeTech BTT pad 7] - bin blobs? 


CM3 has a 200 pin sodimm ddr2 connector form factor but not electrically SC0028, SC0029 
*Blue [https://wiki.geekworm.com/CM_IO_Board Geekworm RPi Compute Module IO Board] [https://github.com/geekworm-com/cm-io-board CSI DSI] with CM3 in ddr2 slot underside - '''works''' if SW1 on but CM3+ '''does not''' 
*Green [https://cdn-shop.adafruit.com/product-files/3442/CMIO_schematic.pdf RPi V3 IO board CM3IO] and CM3 Lite - untested 
*Green [https://turingpi.com/ turingpi v1 cluster] - untested up to 7 cm3 7xlan9514 12V discontinued, 3 x Pi4 homelab maybe better 
*Blue [https://www.waveshare.com/wiki/Compute_Module_PoE_Board Waveshare Compute Module PoE Board] and CM3 lite (if not lite, write files to internal eMMC fat32) '''AVOID''' bin blobs 
*Blue [https://www.waveshare.com/compute-module-io-board-plus.htm Waveshare Compute Module IO Board Plus] [https://www.waveshare.com/wiki/Compute_Module_IO_Board_Plus wiki] [https://forums.raspberrypi.com/viewtopic.php?t=235695 pin settings] with CM3+ Lite - '''AVOID''' binary blob 


*[ Pi02w on Geekworm SupTronics X305 Raspberry Pi Zero IO Baseboard] - untested 
*[ Spotpear Pi Zero 2w to Pi3b format-ish] - untested 


*[ pi-top v4] box has 128x64 oled display, micro hdmi, 19Whr battery with pi4 and 15V PD 36W min needed 
*[ pi-top v3] three green pieces, heatsink covers most of the base tray, pi-top hub mk1 lhs and Pi1B Pi2b Pi3b rhs secured from below, black rounded strip with pi-top above keyboard, 13.3&quot; HD 1366 x 768 display, small touchpad, 
*[ pi-top Model 2.0] pi-top on bottom bezel of 14-inch green laptop, large trackpad, keyboard slide down to reveal main system hub on slide rails moved to the right, Raspberry Pi3b screws down, hub slides in, 18V 2.5A 45W charger brick, battery 11.1V 3500mAh 38.85Wh and storage PiTopOS 
*[ Pi-Top CEED Raspberry Pi Modular Educational Desktop with RPI3] monitor 
*[https://www.indiegogo.com/en/projects/jesselozano/pi-top-a-raspberry-pi-laptop-you-build-yourself Pi-Top v1] wedge laptop with RPi2 


&lt;pre&gt;
2008 Trustees collected for Foundation
2009 Pi Foundation charity status gained 
2010 
2011 First Raspberry prototypes 
2012 First boards go on sale at CPC and RS. The Model A and B 700 MHz Arm11 - February 29th BCM 2835
2012 First million sold - more than the 10,000 original planned and anticipated 
2013 First Alpha Experimental builds of AROS Native for the 32bit Pi 
2013 Pi Trading launched making grants available, providing in house educational resources and Pi Academy for teacher training 
2013 Over two million sold 
2014 Over three million sold 
2014 Pi 1 Model B+ introduced that moved composite video to audio jack and same half gig of memory 
2014 Pi Model A+ v1.1 no ethernet and 1 usb - a little smaller - 
2015 Over four million first gen pis sold  
2015 Pi Zero 1.2 BCM2835 first production revision released with no camera port 
2016 Pi0 1.3 released with camera csi connector 
2017 Pi Zero W v1.1 1GHz Pi0W, single-core 32bit CPU BCM2835 released with Cypress CYW43438 wireless 
2020 Raspberry Pi Pico SC0919 with RP2040 32-bit 2Core ARM Cortex-M0+ up to 133 MHz - 264KB of SRAM and 2MB of on-board QSPI Flash - 
2024 Raspberry Pi Pico 2 with RP2350 2Core 32bit Arm Cortex-M33 and 2core open-hardware [https://github.com/wren6991/hazard3 Hazard3 RISC-V] 

2015 Pi 2 Model B v1.1 BCM2836 900/600 MHz ARM Cortex-A7 Armv7 quad 32bit, 32bit VideoCore IV GPU - 1Gb RAM - 5V 2A micro usb - SMSC LAN9514 chip - 
2015 Over a million pi2s sold 


2015 Raspberry Pi 2 Model B version 1.2 Pi2bv1.2, aka Pi2B2 has armv8 BCM2837 underclocked to 900Mhz without wifi/bluetooth module 
2016 Pi 3 Model B - Broadcom BCM2837 SOC four 64bit ARMv8 Cortex-A53 1.2GHz 32bit 1080p VideoCore IV GPU - 1Gb DDR2 - bluetooth 4.1, Cypress CYW43438 wireless 802.11n - 4 x USB2.0 ports - 5.1V 2.5A - SMSC LAN9514 chip 
2016 PIs total over 10 million worldwide 
2017 Compute Module 3 CM3 with BCM2837B0 armv8 Quad 64-bit - small 67.6mm x 31mm board which fits DDR2 SODIMM connector but not electrically compatible which plugs into needed IO board - beware of the I2C protocol issue 
     1Gb LPDDR2 RAM - Lite or 4Gb Emmc storage 
2017 12 million pis sold in total 
2018 Pi 3 Model B+ - 4c A53 BCM2837B0 1.4Ghz - 1Gb, wireless 802.11ac, gigabit ethernet (300Mbit/s) and bluetooth 4.2 - power over ethernet - 4 x USB2.0 ports - Microchip LAN7515 chip 
2019 Over 15 million sold 
2019 Pi 3 Model A+ with BCM2837b0 Cortex-A53 64-bit SoC @ 1.4 GHz with 512Mb LPDDR2, 1 usb2, 1 hdmi, 1 micro usb 5V 2A - no ethernet - 
2019 Raspberry Pi Compute Module 3+ CM3+ - Broadcom BCM2837B0 1.2Ghz, Cortex-A53 (ARMv8) 64-bit SoC on DDR2 SODIMM mechanically compatible only factor - IO board required 
     1Gb DDR2 and 8GB, 16GB, 32GB or a Lite variant without eMMC 
2021 Pi zero 2 (w or no W) RP3A0 quad 1GHz Cortex-A53 64bit BCM2710A1 512mB SDRam 
2025 edaTEC CM0 ED-CM0NANA with additional dev board with quad 1Ghz A53 with 512Mb Raysan RAM, 2 USB2 and 10/100 ethernet - pico castellated edge
 

2019 Pi 4 Model B RPI4B - BCM2711B0T quad 64bit A72 1.5GHz, 4K VideoCore VI, AC wifi, Bluetooth 5.0, GbE Broadcom BCM54213PE (PHY ID 0x600d84a2), 2 micro hdmi decode up to 4K, USB-C 5.1V 3A power, 2xVLI VL805 USB 3, 2xUSB 2.0, 2GB 9LDWW D9WHZ or 4GB 9FDWW D9WHV, 8GB 0AA47 D9ZCL ddr4 ram 
2020 Silent Pi 4 v1.2 upgrade with more USB-c psu support 
2020 PI400 BCM2711C0T 1.8GHz 4Gb DDR4 inside keyboard, 5.1V 5A 27W usb-c psu, 2 micro hdmi, external ide style 40pin gpio, no audio port - 
2020 Raspberry Pi Compute Module 4 BCM2711B0T on new 55mm x 40mm 2x100 pin form factor with extra breakout IO board 
     CM4101000 1Gb RAM Lite SOM 
     CM4102000 2GB RAM Lite 
     CM4104000 4GB RAM Lite 
     CM4004008-4GB-RAM 8GB-EMMC SOM System on Modules 
     CM4104032 4GB RAM 32GB emmc 
     CM4108000 8GB RAM Lite 
     CM4008016 8GB RAM 16Gb eMMc
2021 Raspberry Pi SC0763 Compute Module 4S CM4S with ddr2 sodimm pinouts but not electrically the same with suitable IO board extra cost - 
     CM4S01000 1GB RAM Lite
     CM4S01008 1GB RAM 8GB eMMC Flash
     CM4S02000 2GB RAM Lite
     CM4S04000 4GB RAM Lite
     CM4S04016 4GB RAM 16Gb KLMAG1JETD-B041 
     CM4S08000 8GB RAM Lite 
2021 Pi 4 v1.4 BCM2711B1 upgraded power regulator, to deal with 8gig of ram being more power hungry - 
2021-48 Raspberry Pi 4 model B v1.5 2GB 


2023 Pi 5 v1.0 BCM2712 Quad A76 @2.4Ghz - VideoCore VII - no audio socket - dual 4k from mini hdmi - fan connector - 5.1V 5A psu 
2024 Pi 5 2GB DDR4 version uses BCM2712D0 
2024 Pi-500 with 8Gb LPDDR5 and membrane keyboard 
2024 Pi 5 v1.1 
2024 Raspberry Pi Compute Module 5 CM5 BCM2712 55mm x 40mm form factor with additional IO board 
     CM5004000 04GB RAM 0GB eMMC Lite
     CM5008000 08GB RAM 0GB eMMC Lite
     CM5016000 16GB RAM 0GB eMMC Lite
2025 Pi-500+ with 256GB NVMe storage, 16GB LPDDR4 RAM, and Gateron KS-33 Low Profile Blue mechanical keyboard switches 
2025 Pi5 1GB DDR4 announced 


2022 PiOS linux goes 64bit 
2024 Pi Trading IPO stockmarket stock exchange listing 


2026 April and May Aros 64bit fixed, added AHI audio, VC4 gfx started, usb functions added to rom  
2026 June and July Aros 64bit usb2otg started, dma.resource, sdio.resource, bwfm.device wifi added 
2026 Late July daily 64bit Pi3 LE little endian builds start 
2026 August Pi 4, 400, 5 and 500 DTBs added, expanding existing support and wifi for Pi4 and Pi5 
2026 August Pi5 HAT+ nvme and HDMI, AHI RPiI2S added, Pi4 HVS5 video scaler started, 
2026 
2027 


2028 Pi 6 
&lt;/pre&gt;


The vcgencmd can be used to inspect and dump the current system configuration. 
vcgencmd runs on top of VCHIQ as an RPC. The mailbox interface is an alternate but much simpler RPC. 
VCHIQ is a bridge (queue) between the CPU and the GPU so they can communicate with the firmware. 

Loads of [https://github.com/6by9/rpi3-gpiovirtbuf/blob/master/rpi3-gpiovirtbuf.c mailbox] which uses the GPIO control calls. [https://github.com/raspberrypi/firmware/wiki/Mailboxes may also be of interest] 

A fair number of vcgencmd examples (search for vc_vchi_gencmd_init). [https://www.raspberrypi.org/forums/viewtopic.php?t=229203#p1406112 sends the relevant vcgencmd commands] to update the scaling kernel, but the [https://github.com/raspberrypi/userland/blob/master/host_applications/linux/apps/gencmd/gencmd.c command] is just a text string. Parsing and execution of the instructions is performed by the VideoCore firmware. 

The Raspberry Pi runs two separate operating systems: Linux/Aros on the ARM, and a threedx RTOS called vcos running on the Videocore 4 VPU: vcos is commonly called &quot;the firmware&quot;. Vcos is tasked with performing certain system services, for example running the display and audio outputs. The VCHI driver provides an interface to allow drivers to talk to vcos. 


Doubtful, on any [https://www.web3d.org/ Web3d] [https://developer.mozilla.org/en-US/docs/Web/API/WebGL_API WebGL] or [https://github.com/immersive-web/webxr WebXR] [https://developer.mozilla.org/en-US/docs/Web/API/WebXR_Device_API Device API] [https://developer.mozilla.org/en-US/docs/Web/API/XRInputSource XRInputSource] support. Hopefully, never/limited support features like location, peer-to-peer, invasive web apps, unwarranted storage, payments, proprietary video streaming etc 

*spreadsheet [https://git.sheetjs.com/sheetjs/sheetjs sheetjs] [https://github.com/mleibman/SlickGrid SlickGrid] [https://github.com/6pac/SlickGrid SlickGrid] [https://github.com/jspreadsheet/ce jspreadsheet ce] [https://github.com/dream-num/Luckysheet Luckysheet] [https://github.com/ruilisi/fortune-sheet fortune-sheet] [https://github.com/dream-num/univer/ univer]  probably without xlsx support 
*presentations [https://github.com/impress/impress.js/ impress.js simplified] [https://github.com/bwlewis/slides slides] [https://zenomt.github.io/mdslides/ github markdown slides] [https://github.com/Patternslib/slides Patternslib slides markdown] probably without pptx support 
*weather [https://github.com/kaushalsahu07/weather weather], [https://github.com/Himanshu3412/Weather-Forecast Weather Forecast],  


==Future==


[https://github.com/ARMSX2/ARMSX2 Arm pi of pcsx2] 


{{BookCat}}</text>
      <sha1>tnl9ot8z5pe33uzaz3zeip55kgs5tko</sha1>
    </revision>
    <revision>
      <id>4675814</id>
      <parentid>4675758</parentid>
      <timestamp>2026-10-13T11:49:08Z</timestamp>
      <contributor>
        <username>Jeff1138</username>
        <id>301139</id>
      </contributor>
      <minor />
      <origin>4675814</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="105041" sha1="i0dsb2uojpmi5e5dvstbw33yskfcp7h" xml:space="preserve">{{ArosNav}}

[[#Native]]

[[#Hosted]]

[[#Build]]

[[#Hardware]]

[[#References]]

[[#Future]]


==Introduction==


[[File:Scalos00.png|thumb|Scalos on Aros Pi3b]]

Aros aims to cover Pi 3 to 5 512Mb+ RAM 


Options to boot from using a good power source to prevent the yellow lightning symbol. 
*With Pi3b+ the max you can get is 5.1V 2.5A with micro usb.
*With Pi4 5.1V 3A with usb-c 
*With Pi5 5.1V 5A, the amps went ever upwards, even to 5.1V 9A with usb-c 


* Pi500+ keyboard wedge - working 
* Pi500 wedge with up to date bootloader via PiOS - working 
* Pi 5  - Quad A76 64bit ARMv8 and RP1 &quot;southbridge&quot; with VideoCore 7 D0 (rev1.1) - untested 
* Pi 5  - Quad A76 64bit ARMv8 and RP1 &quot;southbridge&quot; with VideoCore 7 Pre-D0 C1 (Rev1.0) - untested 
* Pi400 RPI-400 keyboard wedge - resolution changing and audio from micro hdmi0 (near 40pin) and micro hdmi1 (near usb-c psu) - Fn F10 0x5e power on and off works or held down for over 7 seconds auto shutdown - keyboard ok - wifi and lan ethernet testing - 
* Pi 4  - Quad A72 64bit ARMv8 with VideoCore 6 
* Pi 3  - Quad A53 [https://www.raspberrypi.com/documentation/computers/processors.html 64 bit] ARMv8 with VideoCore 4 with '''fan''' to prevent overheating cpu 82C+ throttling 
* Pi02W - Quad A53 64bit - boots but [https://forums.raspberrypi.com/viewtopic.php?p=2387984#p2387984 usb not working but did in the past], 


* Pi 2 - Quad 32bit ARMv6 with VideoCore 4 - mostly not 64bit compatible 
* Pi Model B+ 32bit ARMv6 with VideoCore 4 - not 64bit compatible 
* Pi Model A and B 32bit ARMv6 with VideoCore 4 - not 64bit compatible 


===Native===

* 2013-03 Kalamatee starts work
* 2015-04 Work continues with mschulz on the kernel and Kalamatee (NicJA) on gpio and usb
* 2018 [https://www.patreon.com/posts/i-owe-you-some-20956961 mschulz resume adding BE big endian support], [https://www.patreon.com/michal_schulz/posts Big endian on Pi]  
* 2026 [https://github.com/aros-development-team/AROS/commits?author=bsek latest commits for pi 3b, 4 and 5 64bit] 
* 2026 [https://github.com/aros-development-team/AROS/commits?author=metaneutrons latest commits for Pi5]
* 2026 [https://github.com/aros-development-team/AROS/commits?author=bitplane latest commits for ARM]


====64bit====

'''Download''' A [https://archive.org/details/piAROS Pi Distribution (Distro) has started] and the contents copied to fat32 8GB+ microSD card (there will be drawers/folders - boot c Classes Demos Developer Devs Extras etc only showing). The SD can be plugged in to the Pi. And power on. [https://pi.amiga.icu/ Repository]

[https://aros.sourceforge.io/nightly1.html RaspberryPi 3, 3+, 4 and 5 64bit ArmV8 nightly builds] [https://sourceforge.net/projects/aros/files/ Alternative site and nightly2] which is a test beta limited apps version with both raspi-aarch64-system and raspi-aarch64-contrib can be unbz2'd to a SD or SSD as appropriate. 

64bit build works well on a single core LE little endian. Multicore [https://github.com/aros-development-team/AROS/commit/1df0747c2bda3523a43029725a709b1f377d84ec may follow]. Any issues booting could be down to the SD card so please use another SD to see if it is resolved. Remember Aros Arm uses FAT32 and Aros can detect issues with this format very acutely (once fault found, FAT 0x0FFFFFF7 bad cluster so no files written after that, no repair). Please report your experiences in the [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2138&amp;pid=15057#post_15057 Aros forum thread], [https://forums.raspberrypi.com/viewforum.php?f=179 Raspberry Pi Aros Dev and User forums], [https://forums.raspberrypi.com/viewtopic.php?p=2387984#p2387984 previous Raspberry Pi forum thread]. Any bugs or issues can be [https://github.com/aros-development-team/AROS/issues described here to fix] 

Boots with '''USB3''' port based sata3 ssd on Pi400 but untested on Pi4 (may need eeprom update from PiOS or Pi SD Imager) and Pi5 

Pi 3 B+ is pre-configured for USB sata3 boot - untested 

Pi 3 B may need [https://www.youtube.com/watch?v=ubnwvxF3Klc PiOS to set OTP to boot from usb - do so at your own risk] - if OTP set to usb, boot works but slower than SD card 

Speed write wise (top faster) 
&lt;pre&gt;
*NVME Pi5 untested    &gt;1000MB/sec  or faster if matched correctly 
*Sata3 ssd              500MB/sec
*SD        V90           90MB/sec  4K maybe 8K 
*SD        V60           60MB/sec  1080p 
*SD     U3 V30           30MB/sec  720p 
*SD C10 U1 V10 A1 A2     10MB/sec  minimum should be used now 
*SD C06                   6MB/sec  
*SD C04                   4MB/sec 
&lt;/pre&gt;


As a homage to the past, Aros shows a reduced number of icons but this can be changed by left mouse click in the window and then right click down to Window -&gt; View -&gt; All files

Windows can be manipulated by the top (moving) and the bottom right corner (resizing) only. 

Zune like MUI gui interface, has a unique quirk in that after changing a setting in a text box, you may sometimes need to press Enter/Return before clicking OK, Save, etc 


Double left mouse click on most picture (Developer/Debug/Tests/Datatypes), audio and video files are supported, via datatypes, by the multiview application. 
Esc escape key usually closes open windows even the desktop 

In Prefs/Appearance some decorative theming elements need work. There is a few Mason icons in /Prefs/Presets/Icons/Mason/ and the ever present default Gorilla - Icon exchange in works 

For more intensive graphics applications, you may need to edit config.txt in the root folder and change 128M to 256M to adjust more memory to graphics usage 

If your cursor should '''appear''' to vanish, fear not it is still there. Please head to the top of the screen i.e. the title bar, hold down the left click mouse and drag the screen down a little and the cursor will appear again. Then you can drag the screen up again. 


Like most amiga like OSs the audio and networking need to be setup manually 

Audio AHI prefs - Mode settings tab - needs both Music unit and Unit 0 set to RPiHDMI:16 bit stereo++  or RPiPWM:16 bit stereo++ at 44100Hz. Press '''Save or Use''' button after each choice 


For wireless, please use the Wifi prefs and already selected device bwfm.device. Press Scan and double right click on the router and enter password. You may need to setup after every power off
*if asking for password again - press cancel and go to Network Prefs, Wireless Networks tab and highlight the router line and hit the remove button and press the cancel button. Retry with Wifi prefs again 
*...waiting for an address - Disconnect and try Connect 
Until, Connected to &lt;router&gt; - 192.168.x.x 


For lan ethernet port, please use Network prefs and the following hardware is 
*lan9514  Pi3b Pi2 not supported at the moment 
*lan7515  Pi3b+ type into Device  usblan78xx.device as net0:  remove other device(s) 
*bcmgenet Pi4 Pi400 choose for Device bcmgenet.device 
*         Pi5 Pi500 Pi500+ RP1 i/o 
 (network prefs may forget random information when rebooted) 


Summary
&lt;pre&gt;
*3b    ethernet not supported, usb ethernet not working but wifi prefs setup works 
*3b+   wifi working and ethernet works 
*4     untested 
*400   wifi and ethernet untested 
*5     wifi and ethernet untested
*500   wifi and ethernet untested
*500+  wifi works 
&lt;/pre&gt;


Type in 'aarch64' in the [https://archives.arosworld.org/index.php?function=search&amp;tool=simple search box] and you will see available software packages / apps. apkg can be used to inspect and install applications. 

[http://archives.arosworld.org/index.php?function=browse&amp;cat=network/browser amelinium web browser (JS 1.6 ES9 ECMASCript 2018)] is available with an [https://eab.abime.net/showthread.php?t=122494&amp;page=51 eab thread] reminiscent of [https://github.com/zapek/Voyager Voyager] and to a lesser extent [https://github.com/amigazen/aweb3/ Aweb JavaScript 1.5 (ECMAScript 3)] as css and javascript websites can be slow to load or resolve (no JIT) and nothing from facebook, reddit etc. 

Press Cancel at screenmode selector or -wb argument to get windowed version. You could use the Shift + Del shortcut or mouse wheel should work to delete all text at once. To view wikibooks set Agent to Android (telefon) aka Google Chrome 126 or iPhone aka Safari 17 setting in menus. Html5test gives 189 (1.29), 300 (1.31), 311 (1.33) out of 555, some bigger Amiga like browsers are around 370+ but it does less better. 

You may have to delete the cache (Menu -&gt; Page -&gt; Delete cache) to fully retest big Amelinium updates or free up space. 
Be aware [https://pianetaamiga.it/en/reportage-pianeta-amiga-2026/ some site pages] can use up hundreds of MBs of cache very quickly 

 DNS lookup failed...  close browser and reboot and setup wifi again - repeat until it works again 

 youtube video and audio - js button for javascript must be on/shaded -  Settings -&gt; Soundoutput - AHI 
Usually restricted to lower resolutions due to [https://docs.invidious.io/faq/#q-where-are-the-360p480p1080p-quality-options bandwidth]. You can always [https://docs.invidious.io/installation/#install-the-dependencies self host] for better 

Telegram https://t.me/s/channel_name for public messages from vamped_amiga chatamigagames demoscenecracktros 

*art local js apps like dpaint.js 


There is normally no Bluetooth support for most amiga like OSs but Aros has one [https://github.com/aros-development-team/AROS/commit/6942cbfbf66426d21963a7fcd8aba6aff611a9e0 work in progress] [https://forums.raspberrypi.com/viewtopic.php?t=338466 firmware] 

*Bluetooth 4.1 BCM43430A1.hcd Pi3B, Pi3A, Zero 2W 
*Bluetooth 4.2 BCM4345C0.hcd  Pi3B+, Pi4 
*Bluetooth 5.0 BCM4345C5.hcd  Pi4B rev, CM4 and maybe Pi5 and CM5 

&lt;pre&gt;
*bthid    keyboard mouse support 
*btserial serial 
*btpan    short range wireless connecting devices 
&lt;/pre&gt;


Only the Pi5 has a RTC real time clock, the other Pis will need to use ntp services [https://github.com/aros-development-team/AROS/commit/29cd4116330dc7f692d90757eacc59fb3f31ae70 sntp] with time.cloudflare.com pool.ntp.org or Cloudflare 162.159.200.1, 162.159.200.123, 2606:4700:f1::1, 2606:4700:f1::123 or [https://github.com/bohunamiga/PiNTP PiNTP -s goodtime.ijs.si or ntp1.ptb.de] to get the date and time from the internet. Can use date in a shell e.g.  date 24-Dec-2026 23:59:59  but this will need to be done again after every reset/power off. Maybe [https://github.com/aros-development-team/AROS/commit/28674a157bc56175aa668e7b62dca6fa740578dc ds3231 rtc with dtoverlay=i2c-rtc,ds3231 in config.txt] 


It helps to have all usb devices already plugged in before power on to detect at the moment. Even then some usb devices will freeze the mouse cursor and the only resolution is to remove the offending usb device and reinsert. Sometimes, the reinsert leads to the mouse cursor vanishing, it is still there and responds to left mouse clicks, top of the screen and pull down the screen. 

USB classes support from Prefs/Trident is still work in process 
*usbaudio working on usb3 port (blue) on pi4, 400 but not working (no rt isochronous) on usb2otg (white or black) for pi3b, zero 2w 
*[https://aminet.net/package/mus/midi/camd camdusbmidi] detects midi devices without a preferences file (Prefs/Env-Archive/sys/midi.prefs) as [https://www.youtube.com/watch?v=RBxHkwy4Nrw auto setup now] possibly with [https://github.com/metaneutrons/mt32-pi metaneutrons mt32-pi] [https://github.com/rtzor/mt32-pi mt32-pi fork] [https://github.com/ahmadexp/mt32-pi fork] [https://github.com/gmcn42/mt32-pi-control control of] [https://github.com/dwhinham/mt32-pi mt32-pi pi3+]. Alternative of [https://homspace.nl/samplerbox/ SamplerBox]. 

Will need developer clang gcc tools to look at 64bit ports of [https://archives.arosworld.org/?function=showfile&amp;file=driver/audio/usbmidi.i386-aros.lha usbmidi], [https://aminet.net/package/mus/midi/CAMD_Toolkit CAMD_Toolkit], [https://aminet.net/package/mus/midi/camdtools camdtools], [https://github.com/cnvogelg/amiditools amiditools], [https://github.com/timoinutilis/midi-sequencer-amigaos horny src], [https://aminet.net/package/mus/midi/horny-base horny-base], [http://bnp.hansfaust.de/index.html BnP], [https://arosarchives.os4depot.net/?function=showfile&amp;file=audio/misc/timidity.lha timidity], 


Regarding 680x0 emulation, there are several options (not implemented yet) that could be considered 
*[https://github.com/aros-development-team/AROS/blob/6722a0ae9e03fe5d26e32703360bd2059e0864cc/rom/m68kemu/README.md?plain=1#L424 m68kemu.library] for some Amiga productivity where the cpu is emulated and the system calls are redirected to Aros ones
*[https://github.com/BlitterStudio/amiberry amiberry] (winuae) for everything else like games 
*[https://github.com/jonx/AROS/tree/aarch64-darwin-graft/arch/all-darwin/libs/emu68k emu68k] 
*[https://scriptedamigaemulator.net/ Scripted Amiga] with [https://github.com/naTmeg/ScriptedAmigaEmulator ScriptedAmigaEmulator] or older [https://github.com/gbraad-amiga/ScriptedAmigaEmulator2 ScriptedAmigaEmulator2] 
 Hopefully getting Pi3 up to 25Mhz 68040 (non JIT) and 75Mhz 68040 (JIT) 
 Pi4 getting up to 50Mhz 68040 (no JIT) and 150Mhz 68040 (JIT) 


[https://pinout.xyz/ GPIO 40 pins] [https://learn.sparkfun.com/tutorials/raspberry-gpio/gpio-pinout pinout] 

Some exceptions:

*Physical pins 27, 28 (GPIO0, 1) are an internal I2C bus and should not be used
*The other I2C on pins 3, 5 (GPIO 2, 3) can be used generally, but be aware they have permanent pull-up resistors to 3.3V
*For MIDI use USB but there are dedicated UART pins 8, 10 (GPIO 14, 15).

With a HAT it's more awkward -- you need to know which pins are used by the HAT and avoid them. Hopefully this will be documented.

Remember all GPIOs are 3.3V (not 5V tolerant), floating/noisy inputs can cause odd behavior, and that shorting the power supplies can cause instant death of the Pi.

In the shell (Cntrl + C to end) 

 GPIO PIN/A/N,SET/N,GET/S,MODE/K,PULL/K

Controls and queries hardware GPIO pins via gpio.resource which is stored in the rom or Devs/ '''please test''' 

*PIN   -- (Required) Target GPIO pin number (e.g. 12).
*SET   -- Set pin output value to 0 (LOW) or 1 (HIGH).
*GET   -- Read and print current digital input level (0 or 1).
*MODE  -- Configure pin mode: IN (Input), OUT (Output), ALT (Alternate).
*PULL  -- Configure pull resistor: NONE, UP, DOWN.

EXAMPLES
&lt;pre&gt;
GPIO 12 MODE OUT
GPIO 12 SET 1
GPIO 12 GET
GPIO 13 PULL UP
&lt;/pre&gt;


[https://gpiozero.readthedocs.io/en/stable/installing.html Current] [https://gpiozero.readthedocs.io/en/v1.2.0/api_boards.html old support for gpiozero is unknown at present] [https://energenie4u.co.uk/res/pdfs/ENER314%20UM.pdf and associated 433MHz equipment] [ USA X10 security and lights via USB] [ OpenHab with Shelly Smart Plug connected over Wi-Fi, controlled by MQTT or HTTP] 


Printing only with Postscript but [https://github.com/bohunamiga/MintPRINT one] of [https://github.com/boingball/MintPRINT two] [https://github.com/Andiweli/AmiAirPrint/tree/main AirPrint] IPP has been attempted with [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2061&amp;pid=13954#post_13954 discussion] 


Youtube 

[], [], [https://www.youtube.com/watch?v=X4fmWAIv7FE Aros native on Pi3b], 

[], [], [https://www.youtube.com/watch?v=TSxlYb1eQWU Installed on Pi3b+], 

[], [], [https://www.youtube.com/watch?v=NFF1H3jCoz8 testing Aros native on Pi400], 

[], [], [https://www.youtube.com/watch?v=nIVx7mh1E1Q&amp;pp=ygUHYXJvcyBwadIHCQkTDAGHKiGM7w%3D%3D Aros on Thumb 2 based 32bit-ish ARM STM32H743 board], 


[https://www.youtube.com/watch?v=zQM4CD64xDE&amp;t=612s&amp;pp=ugUEEgJlbg%3D%3D Performance under Linux] but on Aros... 

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;10%&quot; |Pi
! width=&quot;10%&quot; |Single Core 2D
! width=&quot;10%&quot; |Single Core 3D
! width=&quot;10%&quot; |Single Core 3D
! width=&quot;10%&quot; |SMP 2D
! width=&quot;10%&quot; |SMP 3D
! width=&quot;10%&quot; |SMP 3D 
! width=&quot;35%&quot; |Comments
|-
| &lt;!--Pi--&gt;Pi3 
| &lt;!--Single Core 2D--&gt;
| &lt;!--Single Core 3D--&gt;
| &lt;!--Single Core 3D--&gt;
| &lt;!--SMP 2D--&gt;
| &lt;!--SMP 3D--&gt;
| &lt;!--SMP 3D--&gt;
| &lt;!--Comments--&gt;
|-
|}


==== 32bit ====

For the Pi1 Pi2 Pi2B the status of AROS native ARMv6 for 32bit RasPi was OK. System booting, USB working (although with some issues but plans to fix them). 32bit native [http://www.aros.org/nightly1.html ARMv6 32bit nightlys] raspi-armhf-system raspi-armhf-contrib unbz2'd to fat32 microSD 


===Hosted===


AArch64 CPU backend for AROS, a Cocoa/Metal display, clipboard / host-volume / CoreAudio / BSD-sockets bridges, GPU 2D via gpufx.library, a 68k→AArch64 JIT (run68k), and a full Rust std port. On [https://www.jkn.me/blog/macaros-aros-on-apple-silicon/ latest Apple Silicon] [https://github.com/jonx/Macaros early buggy alpha version of hosted Aros .dmg on MacOS12+]. Please use [https://github.com/jonx/Macaros/issues MACAros github] for issues, features etc and possibly [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2030&amp;pid=13910#post_13910 here] 


[http://www.aros.org/snapshots1.html old linux and android hosted 32bit] 


==== Hosted ====

=====64bit=====

[https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2019&amp;rowstart=80&amp;pid=13667#post_13667 Ubuntu Linux PC hosted Pi compiler build] 

[https://github.com/BlitterStudio/aros-compiler-docker Docker based cross compiler for various Aros systems], 

[https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=2019&amp;rowstart=80 From the Aros Raspberry pi 3 64bit thread] 
Instructions on building 64-bit Raspberry Pi AROS and cross-compiler from sources.

You will need:
- Ubuntu 24.04 or 26.04
- qemu-system-aarch64 installed
- Internet connection
- rpi-scripts.tar.gz downloaded (https://axrt.org/download/aros/rpi/rpi-scripts.tar.gz)

1) Install prerequisites:

sudo apt install git gcc g++ make gawk bison flex bzip2 netpbm autoconf automake libc6-dev liblzo2-dev libpng-dev gcc-multilib byacc python3-mako cmake yasm curl nasm

2) Clone sources

cd &lt;project-directory&gt;
git clone https://github.com/aros-development-team/AROS.git --recurse-submodules

3) Extract rpi-scripts.tar.gz. Copy all files into your project directory so that you have:

AROS (the directory with cloned sources)
fix-dotdot.py
rebuild.sh
recreate-sdcard.sh
run-qemu.sh
update-sdcard.sh

4) Run ./rebuild.sh. Select option 1) toolchain-core-aarch64

This will execute process of building a cross-compiler. During this process packages will be downloaded from Internet. This process can take up to 2 hours. If there are some missing dependencies, install them with 'sudo apt install' and restart this step.

5) Run ./rebuild.sh again. Select option 2) core-raspi-aarch64

This will build system files for 64-bit Raspberry Pi AROS. This process can take around an hour.

6) Run ./recreate-sdcard.sh

This will create an sdcard.img file with contents of previous step.

7) Run ./run-qemu.sh

This will start QEMU with SD card image and ROM images. It will boot into AROS.


=====32bit=====

Ubuntu VM approach to compiling [http://lallafa.de/blog/2013/06/building-aros-hosted-for-raspbian/ Linux hosted AROS June 04, 2013]

 ../AROS/configure --target=linux-armhf  --enable-includes=/usr/arm-linux-gnueabihf/include --x-includes=/usr/arm-linux-gnueabihf/include --x-libraries=/usr/arm-linux-gnueabihf/lib

arm-elf- is symbol-linked to arm-linux-gnueabi- (arm-linux-gnueabi- is more correct in this case, because it's going to be compiling the ARM AROSBootstrap for ARM Linux)

*armel - many of the &quot;android&quot; machines require since the entire OS is made for soft float VFP. 
*armfp - Efika MX target, Raspberry PI, EfikaMX, Pandora and virtually everything (VFP)

Keep in mind it's possible to start hardfp AROS hosted on softfp system, though, as long as no calls between AROS and host require floating point parameters. NOTE: hardfloat objects *cannot* be linked with softfloat objects - they have a different ABI.

Just keep in mind the arm nightly build machine is quite complex beast. It needs the x86_64 host compiler to compile AROS tools. The arm version is built every night using gcc-4.6.2 crosscompiler (built together with AROS) and successfully builds armel and armhf linux hosted targets.

*needs an AROS code compiler for ARM target 
*as well as unix compiler for ARM linux host (would be best to have both softfp and armhf, we have softfp only now) with full set of libraries and includes.

with—disable-crosstools  $AROS_CC  is always a wrapper around $KERNEL_CC  ?  If  so,  this  is  wrong for some ports. This can break Darwin, Windows and Android port. 
Yes,  Android  port  will  build.  And  even  work. But it's not good because  the  port  will  not  be ABI-compatible with other ARM ports. Android's ABI is different from GNUEABI. For example:

&lt;pre&gt;
enum test {foo, bar};
enum test testvar;
&lt;/pre&gt;

sizeof(testvar)  will  be  equal  to sizeof(int) in GNUEABI (Linux and AROS)  and  sizeof(short)  on  Android. This affects linking objects from static linklibs, for example.

Previously everything worked because $AROS_CC was a wrapper on top of $HOST_CC. And a real crosscompiler was used on non-ELF hosts.

Android is the same. $KERNEL_CC is incompatible with AROS.

compiler=kernel  is  appropriate _ONLY FOR CODE WHICH RUNS ON HOST OS_ (or  barebone  hardware,  if  we  talk  about  native).  This includes bootstraps,  their  linklibs, and host-side dynamic libraries (Windows makes extensive use of them because of architectural considerations.

No single AROS object should be compiled with this setting. $KERNEL_CC is really compatible with AROS *ONLY IN LINUX-HOSTED* and no more. On other systems (Darwin, Windows,  Android) this is not true any more, and compiler=kernel is never going to work.

If  you  want  to  compile your AROS module against host OS includes, append  the  following  to  USER_INCLUDES  (or  USER_CFLAGS,  this  is effectively the same):

 -isystem $(GENINCDIR) $(KERNEL_INCLUDES)

$(KERNEL_INCLUDES) expands to:

 -isystem  &lt;your_os_includes&gt;  -isystem  &lt;host_OS_gcc_private_includes&gt;
 -nostdinc

This makes AROS compiler adhering to host OS APIs.

If you want some preprocessor symbols based on what your host OS actually is, add something like -DHOST_OS_$(AROS_HOST_ARCH).

Why is there $(GENINCDIR) at all? Because host OS has its own libc includes, which would conflict with AROS ones. And the host OS libc is not binary-compatible with AROS one.

Why doesn't Windows-hosted port use $(KERNEL_INCLUDES) ? Because WinAPI includes conflict with AROS ones in fundamental typedefs, like WORD, BYTE and BOOL. It's almost impossible to deal with this in any other way than rewriting WinAPI definitions using AROS types.

Building under centos 6.3 (i386) currently, and AROS creates the toolchain itself. haven't yet committed the necessary changes but &quot;./configure --target=raspi-armhf&quot; is enough to start, then &quot;make arosboot-raspi&quot; will generate arosraspi.img (containing the bootstrap, kernel.resource, and exec.library) as well as arosraspi.rom (containing all the other essentials components such as dos, graphics etc).  It will also copy over a config.txt file to make the raspi bootstrap code load the correct kernel, and a cmdline.txt that enables exec debug output.

*armel = typically Debian 6, Ubuntu Maverick, Android, 
*armhf = typically Debian 7, Debian 8, Ubuntu Precise,

Cross-compiling Ubuntu ARM softfp 
&lt;pre&gt;
    sudo sh
    echo 'foreign-architecture armel' &gt;&gt;/etc/dpkg/dpkg.cfg.d/multiarch
    echo 'deb [arch=armel] http://ports.ubuntu.com/ precise main universe' &gt;/etc/apt/sources.list.d/armel.list
    apt-get update
    apt-get install gcc-arm-linux-gnueabi libx11-dev:armel libsdl-dev:armel
&lt;/pre&gt;

&lt;pre&gt;
 ./configure --target=linux-arm --x-includes=/usr/include \
             --enable-includes=/usr/arm-linux-gnueabi/include
&lt;/pre&gt;

Cross-compiling Ubuntu ARM hard-float 
&lt;pre&gt;
    sudo sh
    echo 'foreign-architecture armhf' &gt;&gt;/etc/dpkg/dpkg.cfg.d/multiarch
    echo 'deb [arch=armhf] http://ports.ubuntu.com/ precise main universe' &gt;/etc/apt/sources.list.d/armhf.list
    apt-get update
    apt-get install gcc-arm-linux-gnueabihf libx11-dev:armhf libsdl-dev:armhf
&lt;/pre&gt;

&lt;pre&gt;
    ./configure --target=linux-armhf --x-includes=/usr/include \
                --enable-includes=/usr/arm-linux-gnueabihf/include
&lt;/pre&gt;

Now, the AROS build is configured properly and all you need to do is:

 make


==Build==

===64bit===


===32bit===


# download/checkout the source someplace, e.g. /build/AROS-Src/
# make a directory to store external sources AROS downloads, e.g. /build/Ports
# make a build directory, e.g. /build/aros-raspi-armhf
# cd into the build dir, configure, and then run make -:

&lt;pre&gt;
&gt;cd /build/aros-raspi-armhf
&gt;/build/AROS-Src/configure --target=raspberrypi-armhf --with-serial-debug --enable-ccache --with-portssources=/build/Ports
&gt;make
&gt;make arosboot-raspi
&lt;/pre&gt;

then copy the files from /build/aros-raspi-armhf/bin/raspi-armhf/AROS/ onto an sdcard, and download/copy the Raspi firmware files onto it.

You should then be able to boot the sdcard on your RasPi.

The current W.I.P tree to svn. it can be built as follows ..
&lt;pre&gt;
./configure --target=raspi-armhf
make arosboot-raspi
&lt;/pre&gt;

That will generate arosraspi.img, arosraspi.rom and config.txt in bin/raspi-arm/AROS - so either copy just those files to a fat formatted SD card (with the firmware files on), or copy the whole contents of the AROS folder.

NB - if you have a Linux/other install, backup the existing config.txt first

arosraspi.img contains the bootstrap (which has very basic mailbox code, framebuffer/gpio init, and console &quot;emulation&quot; via code pinched from our libbootconsole), kernel.resource, and exec.library

arosraspi.rom contains all the other components needed to boot AROS.

The config.txt file will tell the RasPI bootstrap to load the arosraspi kernel and ramdisk (rom).

the bootstrap has minimal mailbox code, planning on adding either a resource or library that driver/app code will use to access it (likewise for GPIO)


Help building AROS hosted on Linux ARM

Was looking a way to use more my Handheld ARM based called Pyra (Dragonbox Pyra) an ARM (Omap5 cpu with 4GB ram) linux based machine (Debian Buster v10 with kernel 5.6.19 adapted) and have a try to compile the latest Aros sources by Deadwood directly on this device.
Compilation stops after build libpopupmenu.a and trying to build libatomic have this error:

&lt;pre&gt;
    Configuring build in bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic
    configure: WARNING: unrecognized options: --disable-nls, --without-x
    checking for --enable-version-specific-runtime-libs... no
    checking for --enable-generated-files-in-srcdir... no
    checking build system type... arm-unknown-linux-gnu
    checking host system type... arm-unknown-aros
    checking target system type... arm-unknown-aros
    checking for a BSD-compatible install... /usr/bin/install -c
    checking whether build environment is sane... yes
    checking for arm-aros-strip... /media/farox/pyra2/arosbuilds/toolchain-core-armhf/arm-aros-strip
    checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
    checking for gawk... no
    checking for mawk... mawk
    checking whether make sets $(MAKE)... yes
    checking whether make supports nested variables... yes
    checking for arm-aros-gcc... /media/farox/pyra2/arosbuilds/toolchain-core-armhf/arm-aros-gcc
    checking whether the C compiler works... no
    configure: error: in /media/farox/pyra2/arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic':
    configure: error: C compiler cannot create executables
    See config.log' for more details
    make[2]: *** [mmakefile:4489: /media/farox/pyra2/arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic/.configured] Error 77
    [MMAKE] make --no-print-directory TOP=/media/farox/pyra2/arosbuilds/toolchain-core-armhf-build SRCDIR=/media/farox/pyra2/arosbuilds/AROS CURDIR=tools/crosstools/gnu TARGET=tools-crosstools-gcc-libatomic-configure -s --file=mmakefile tools-crosstools-gcc-libatomic-configure failed: 512
    [MMAKE] Error: Error while running make in tools/crosstools/gnu: No such file or directory
    make[1]: *** [Makefile:361: linklibs-libatomic] Error 10
    make: *** [Makefile:183: crosstools] Error 2
&lt;/pre&gt;


looking at config.log on arosbuilds/toolchain-core-armhf-build/bin/linux-arm/gen/host/tools/crosstools/gnu/gcc/arm-aros/libatomic

found that arosbuilds/toolchain-core-armhf/arm-aros-ld: cannot find -laeabi
so do make linklibs-aeabi-arm-quick
and the missing lib was built.

now the next stop is at
fatal error: bits/libc-header-start.h: No such file or directory
and
fatal error: sys/cdefs.h: No such file or directory
in many places so after checking that have this missing include files i have noted that my include path is a bit different, standard searching path is /usr/arm-linux-gnueabihf but in my system is /usr/include/arm-linux-gnueabihf
so if i add my path to some mmakefiles compilation goes on....but is a better way to add this path to avoid every mmakefiles to be changed?

fixed with adding
-I/usr/include/arm-linux-gnueabihf
to where is missing on mmakefiles like
USER_INCLUDES := -isystem $(GENINCDIR) -I/usr/include/arm-linux-gnueabihf $(KERNEL_INCLUDES)

P.s. I have changed many mmakefiles and have at least compiled (after many hours) the toolchain doing make every time in arosbuilds/toolchain-core-armhf-build (also have to disable making tests under cplusplus but don't remember the directory ...) but ask an help to have an automated way to correctly build without modify mmakefiles.


Last time built armhf target was around 2 years ago. At that point built is via cross-compilation from linux (ubuntu 22.04) using linux armhf crosscompiler (this can explain the path differences you are experiencing) as well as using AROS gcc cross-compiler in version 6.5.0 (build with option 21) in rebuild.sh). Since then AROS GCC has been updated to 10.5.0 and don't believe anyone tried to build the armhf target again.

My suggestion would be to downgrade GCC to 6.5.0 (via editing AROS/config/gcc_def file) and try to first build using cross-compilation from x86_64 linux. Once that works, you will have a &quot;template&quot; to compare to native compilation under arm linux.


Thanks for your suggestion...but think the toolchain with GCC 10.5.0 is compilable if i found a way to pass the path of my system to the script that build (option 21 on rebuild).
The other only changes are (but don't know where to modify...) is to add the build of libaeabi and disable the building of some tests under cplusplus that use exceptions and is not supported under ARM. try to crosscompile with my Linux amd64 PC.

For paths look into core-linux-armhf/bin/linux-armhf/gen/config/target.cfg. A number of build-wide variable is set there containing paths to local build system. These variables and the target.cfg file are generated by AROS ./configure script.

Thanks compilation now go forward...changed target.cfg under &quot;toolchain-core-armhf-build/bin/linux-arm/gen/config&quot; and do make on &quot;toolchain-core-armhf-build&quot; dir.

Need to find where to enable build libaeabi.a so can build the entire toolchain with option 21 of rebuild.sh


Found something that looks like libeabi in AROS/arm-all/arm-aeabi/mmakefile.src. Try adding a third line there:

#MM- linklibs-armhd : libklibs-aeabi-arm

Don't remember needing this library. Possibly the 6.5.0 GCC somehow does this while 10.5.0 is missing this.

Try adding this line (and the variant &quot;linklibs-armhf&quot; instead of hd) but it did not solve the automatic building of the missing lib. I must do &quot;linklibs-aeabi-arm-quick&quot;.
Anyway after have build the aeabi lib i succefully built the toolchain (after many hours...). Smile

To test I restarted from selecting option 21 (on rebuild.sh) but after many hours i get the same error of the kernel includes not found...maybe i need to modify the configure script for my case.

With the toolchain built i try to build the core-linux-armhf (DEBUG) (option 22) but after a while it stopped with
&quot;cannot find -laeabi &quot; so i made it built manually...and now i can continue compiling...i'll let you know if all goes ok.


== Hardware ==

===64bit===


====BCM2712====

With the Pi5 

Broadcom VideoCore 7 vc7 is an integrated GPU with 12 cores and up to 800 MHz clock. VideoCore VII is capable of OpenGL ES 3.1 and Vulkan 1.2. The driver support for the Raspberry Pi continues to build upon the [https://lore.kernel.org/dri-devel/20230928114532.167854-1-itoral@igalia.com/ open-source V3D driver] stack within [https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25450 Mesa] hopefully be merged for Mesa 23.3. x265 HEVC accelerated untested, x264/h.264 and VP9 cpu only. 

*Raspberry Pi M.2 HAT+ Expansion Board 
*Geekworm X1001 PCIe to M.2 Key-M NVMe
*Geekworm X1003 PCIe to M.2 HAT NVMe SSD PIP Board for Raspberry Pi 5 
*Pineboards Pi Hut HatDrive! M.2 HAT 2024/V4 
*Hat+ Gen2 Gen3 Nvme
*GeeekPi 52Pi N04 for Raspberry Pi 5 NVME M.2
*


*2024 RPI AI HAT    - Hailo  20TOPs  no LLMs 
*2026 RPI AI HAT+ 2 - Hailo  40TOPs  slightly better? 


[https://www.raspberrypi.com/documentation/accessories/camera.html Cameras for Pi]
*Raspberry Pi camera module, the V3 with Sony IMX708 back-illuminated CMOS 12 Megapixel sensor
*Raspberry Pi Camera Module V2 – 8MP Sony IMX219 Sensor
*Raspberry Pi camera Rev 1.3, 5MP 1080P OV5647 image/video module, 2592 x 1944 pixels


====BCM2711====

With the Pi4 an ARM a72 cpu is about x3 times the size of an a53 in the Pi3 

the 2711b line used more power when idle, compared to the 2711c 

*2018 Raspberry Pi PoE HAT Power Over Ethernet Hat - design issues 
*2020 Raspberry Pi PoE+ HAT Power Over Ethernet Hat Pi3b+ Pi4 only - better design 
*Waveshare PoE HAT (B) with cooling fan for Raspberry Pi 3B+/4B 802.3af PoE 

*[https://github.com/axizo-pi/V3DLib vc6 V3D 4.2] is derived from [https://docs.broadcom.com/doc/12358545 vc4], but it is significantly different 
The QPU pipeline stays mostly the same, you still have an add ALU and a multiply ALU and it can issue two ALU OPs per cycle. There is still 4 SIMD lanes, interleaved over 4 cycles.
The instruction encoding for the QPUs is different, but the core instructions are the same.

Instructions for packed 8 bit int math has been dropped, along with most of the pack modes.
Instructions for packed 16bit float math has been added (2 floats at in a single operation)
With vc5/vc6, you write two packed 16f value to the tilebuffer (or four writes of 32f, if you are using the rgba32f framebuffer). And there is a handy vfpack operation which allows you to pack two f32s into a single 32bit value in a single instruction. You can vfpack directly into the tile buffer register.

the multiply ALU can now fadd, so you can issue two fadds per instruction. the add ALU has gained a bunch of new instructions 

the A and B register files have been merged. You still only get an A read and a B read per instruction, but they read from one big register file (which means the underlying memory block has gone from two sets of &quot;one read port, one write port&quot; to one &quot;two read ports, one write port&quot; block)

The theoretical max FLOPs per QPU remains the same at two per cycle, other than the bump from 400mhz to 500mhx but it looks like a lot of effort has been put putting those theoretical FLOPs to better use. 
*vc4 could run one or two threads per QPU. When you ran in two thread mode, the available register file halfed to 32 registers.
*vc5 added a four thread per QPU mode, with 16 registers per thread.
*vc6 doubled the size of the register file. You could now use all 64 threads in two thread mode and 32 registers in for thread mode. Single thread mode was removed, you always have at least two threads.

With the threading improvements, the QPUs should spent much less time idle waiting NOPs for memory requests. Most of the design changes have gone to improving the fixed function hardware around the QPUs. A fixed function blend unit has been added, which should reduce load on the QPUs when doing alpha blending. hope software blending is still possible 

The tile buffer can now store upto 4 render targets (up to 128bits per pixel, so if you are using 4 32bit render targets, you can't have a depth buffer)

A MMU, allowing a much simpler/faster kernel driver.

Many more texture formats, framebuffer formats.

h264/x264 as Pi3 

All the features needed for opengl es 3.0 

H.265 / HEVC decoder is a HEVCv2 Main 4:4:4 10 design supporting bitstreams up to profile 5.1
HEVC hardware decode supports 4kp60, 10-bit. Audio output is pretty much unchanged, but the HDMI audio channels now support 8x192kHz bitrates 

Each ALU typically have 2 floating point operators, and as you pointed out in a earlier post videocore 6 is no exception, with both a multiply and additive floating point operator. Thus theoretical GFLOPs are calculated with both operators in mind. That is what the 2 in my formula represents, and is common across any modern programmable shader, whether you calculate Nvidia, AMD, Intel, Boardcom or any other company's GPUs. Total ALUs * 2 * GHz clock = GFLOPs, In the case of Raspberry Pi 3, it's 24 ALUs * 2 operators * 0.4GHz = 19.2GFLOPs
If the Videocore 6 does indeed only have 16 ALUs (16 * 2 * 0.5GHz), you'd have only 16GFLOPs but they are better utilised 

Possible maximum performance 
&lt;pre&gt;
VideoCore IV @ 250MHz: 250 [MHz] x 3 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 24 Gflop/s
VideoCore IV @ 300MHz: 300 [MHz] x 3 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 28.8 Gflop/s
VideoCore VI @ 500MHz: 500 [MHz] x 2 [slice] x 4 [qpu/slice] x 4 [processor] x 2 [op/clock] = 32 Gflop/s
&lt;/pre&gt;

Faster LPDDR4 memory.


====BCM2837==== 

With the Pi3 
* Broadcom BCM43438 chip provides 2.4&amp;nbsp;GHz 802.11n wireless LAN, Bluetooth Low Energy, and Bluetooth 4.1 Classic radio support, 3B+ [https://github.com/aros-development-team/AROS/commit/afa5bc0bb17d5dd06bcfdbac00853a3799ca8d76 LAN7515] 

The overclock ability has diminished with each chip version as the energy usage has increased. BCM2837 is one of the warmest yet and benefits from active fan cooling if all four cpu cores are in use for a short while. Video playback is not affected due to the custom support in the GPU. 5 V / 2.4 or 2.5 amp power supply recommended if all four cpu cores are running, else throttling (cpu slowdown) might occur. 

Dual VDP and scalable QPU in VC4 and x.264/h.264 accelerated untested only and VP9 on cpu or neon help 


ARMv8-A has [https://developer.arm.com/documentation/102412/0100/Privilege-and-Exception-levels privilege levels] where userspace typically runs at ‘EL0’, the kernel at ‘EL1’ or ‘EL2’ and the firmware at the highest level ‘EL3’. 


===32bit===

=== Core Kernel ===


====BCM2708(family)====
which includes the [http://elinux.org/RPi_Hardware BCM2835] (ARM1176JZF-S 700&amp;nbsp;MHz CPU + VideoCore IV GPU + up to 1GB RAM)

*Framebuffer (fb) using mailbox 
*IRQ scheduler, etc 
*Arasan based SD Card controller 
*Synopsis DesignWare USB 2.0 OTG controller [http://networkdirection.net/index.php?option=com_content&amp;view=article&amp;id=106:rasperry-pi-usb-controller&amp;catid=45:raspberry-pi&amp;Itemid=54 Unofficial DOCS pdf],  [dwc_otg.c FreeBSD], [], [https://www.riscosopen.org/viewer/view/mixed/RiscOS/Sources/HWSupport/USB/Controllers/DWCDriver/ RiscOS USB Driver], [https://www.riscosopen.org/forum/forums/5/topics/878 RiscOS USB Discussion], [https://www.riscosopen.org/forum/forums/11/topics/1893 Other USB RiscOS], [http://plan9.bell-labs.com/plan9/index.html Plan9 Miller's usb] http://plan9.bell-labs.com/sources/contrib/miller/, [https://github.com/Chadderz121/csud CSUD driver], 
*[http://www.smsc.com/media/Downloads_Public/Data_Sheets/9512.pdf SMSC 9512] USB LAN/Hub chip 
*CMOS RAM 
*VCHIQ port which sends messages to the GPU e.g. for mouse, keyboard, audio on HDMI, etc 
*Audio Driver 
*Serial Peripheral Interface Bus (SPI) 
*[http://www.susa.net/wordpress/2012/06/raspberry-pi-pcf8563-real-time-clock-rtc/ I2C registers]
*I2S 
*Universal Asynchronous Receiver Transmitter (UART) 
*[http://elinux.org/RPi_BCM2835_GPIOs GPIOs] and [http://www.adafruit.com/blog/2012/08/17/broadcom-bcm2835-peripheral-memory-map-and-gpio-alternate-use-chart-piday-raspberrypi-raspberry_pi/ Alternative view of GPIO]

BCM2836 
* For Pi B+, PI 2 and Pi 3 SMSC LAN9514 chip adding 10/100 Ethernet connectivity and four USB channels to the board

*[http://www.andrewscheller.co.uk/rpi_pcb_modules.html PCB], [http://elinux.org/RPi_Low-level_peripherals Low level features],


 Implemented so far... 

# Modify the configure system so that it correctly builds for the arm hardware float raspi target.
# Implemented the bootstrap to load the aros modules and prepare the arm to jump into them. Reworked the x86 console support so that parts can be stolen for raspi to use since t has no basic functionality to output to the display.
# Implemented a kernel.resource to prepare the raspi for running aros and provide the low level api calls to expose available resources and allow exec, etc function.
# Implemented serial debug support
# Implemented the exec (and kernel) functionality required to make multitasking work (and interrupts, exceptions, syscalls, etc)
# Implemented a timer.device to utilise the hardware timers.
# Implemented a very basic gfx driver to expose the hardware's framebuffer.
# Implemented an SD-Card driver for AROS which presently only supports the raspi's chipset but can easily be modified to support all sd-card hardware and media.
# Fixed the fat filesystem support in AROS so that it can boot on RasPi's normal SD-Card setup. The &quot;rom&quot; image files needed use a different filename than the default linux, etc images so can be easily installed without harming the existing files - you only need to change the loaded images in the config file to get aros to boot.
# Updated the build scripts to automatically download the necessary raspi firmware files and wrap it all up so that you can simply extract the archive to a fat formatted sdcard and boot it on the raspi without having to get anything else.
# fix everything in contrib and ports to build for raspi (needs proper testing/fixes but allows every component to actually compile at least, including owb) + numerous other fixes to get things working on arm/raspi ..


Improvements...

# Implement a USB chipset driver &quot;OR&quot; finish the existing one [https://github.com/aros-development-team/AROS/commit/c07d13c724f944674be5db54fc6a71ee72a01809 usb otg] - the current code is mostly a skeleton that should initialise the chipset and then needs relevant code to support the different transfer types. It also has the &quot;virtual&quot; hub code in place to represent the raspi's USB port (from poseidons p.o.v) 
# Implement a driver for the USB NIC (a few weeks - depends on USB above) 
# Write an [https://github.com/aros-development-team/AROS/commit/d55d0f74d20b769bbb8c8d386e5c1d7a9154f05a audio driver] (a few weeks - independent of USB) and [https://github.com/aros-development-team/AROS/commit/e93a4c245f27a87c9c4c1d39206694b39059998a HDMI]
# fix syscall bug in the current raspi kernel code
# Graphics depend on having a decent &quot;bcmdma.resource&quot; implemented as to use the cpu's dma engine. The sd card driver needs to use it for transfers to/from the controller - and the gfx system needs to use it for &quot;blitting&quot;. 
# [https://github.com/aros-development-team/AROS/commit/4019d84e4975d4dad987a12d57fe108f5ac048e6 Improve the gfx driver], [ vc4gfx HIDD] add [http://dri.freedesktop.org/wiki/VC4/ Gallium3D support] 
# [https://github.com/aros-development-team/AROS/commit/b13905b3e8e45b089f520b44692c81affddd066f Improve] the [https://github.com/aros-development-team/AROS/commit/3a876755c070f5c73c4f53c7f4d35b4f923088b9 sdcard] device driver  - which is also pretty basic but should work with most cards, rework it to also support pci, etc. sd card interfaces on x86 
# The current code using very rudimentary access to the gpio interface - so that should be implemented as some resource for other components to access, as-well as the i2c interface exposed over the gpio interface. that should have a hidd class implemented which uses the gpio resource to communicate.


 Boot up typical for most other OSs before the open sourcing of many binary blobs from 2017 onwards 

On power-up, the rpi [http://www.open.com.au/mikem/bcm2835/ BCM 2835] [https://github.com/hermanhermitage/videocoreiv VideoCore4] GPU, not the ARM CPU, is in control, and the SD card slot is the only peripheral device with power. The firmware burned into the BCM2835's VideoCoreIV GPU PROM requires a DOS-style partition table; a FAT-formatted first partition; and the freely redistributable but closed sourced Broadcom files “bootcode.bin” and “start.elf” in that partition.

The boot sequence carries out several pre-boot tasks

*On powering of the rpi, the GPU reads and executes bootcode.bin, which then loads start.elf 
*The GPU loads the “start.elf” file, eventually, into the L2 cache and then executes it
*configures the memory split for the CPU and GPU
*reads and parses “config.txt” from the same partition on the SD card and applies the settings (like a PC’s BIOS settings)
*loads the “kernel.img” file, again from the same partition
*activates the CPU to begin executing the loaded kernel image

The CPU/GPU memory split is hard-coded into start.elf, so Broadcom provides three start.elf images, to give 32M, 64M, or 128M to the GPU for multimedia performance, and the remainder to the CPU.

RPi uses [https://github.com/raspberrypi/firmware some closed source loaders] and at some point it loads a binary blob named &quot;kernel.img&quot; at 0x8000, at that point there would be a rudimentary Aros alive. If one wants to use the SD-card then there would have to be a driver for the interface and a fat filesystem handler (SD-card has to be formatted to fat filesystem)

Boot code and kernel are now linked together and made into that binary blob, just for starters. Raspberry Pi uses [http://kernelnomicon.org/?p=133 u-boot] and [http://kernelnomicon.org/?p=138 UBoot] as bootloader, there's already some code in the Efika MX port for that. UBoot is a native bootloader and not just for the raspberry pi, it loads after start.elf.

You can find Efika MX port from arch implementations, some hacking is needed for the mmakefile.src'es as iit dates back to before the Aros crosstool era or else you get some weird errors while building. You also need to code the bootstrap and serial handling.

At the moment it seems that a fastest route for the native build would be to make one binary blob without using the package system. Raspberry's memory layout is pretty simple and if the implemented u-boot doesn't support loading other modules 

&lt;pre&gt;
?          - alias for 'help'
mtest      - simple RAM test
autoscr    - run script from memory
base       - print or set address offset
bbm        - BBM sub-system
bdinfo     - print Board Info structure
boot       - boot default, i.e., run 'bootcmd'
bootd      - boot default, i.e., run 'bootcmd'
bootm      - boot application image from memory
bootp      - boot image via network using BootP/TFTP protocol
cmp        - memory compare
coninfo    - print console devices and information
cp         - memory copy
crc32      - checksum calculation
echo       - echo args to console
fatinfo    - print information about filesystem
fatload    - load binary file from a dos filesystem
fatls      - list files in a directory (default /)
go         - start application at address 'addr'
help       - print online help
iminfo     - print header information for application image
itest      - return true/false on integer compare
jade       -
loadb      - load binary file over serial line (kermit mode)
loads      - load S-Record file over serial line
loady      - load binary file over serial line (ymodem mode)
loop       - infinite loop on address range
md         - memory display
mm         - memory modify (auto-incrementing)
mtest      - simple RAM test
mw         - memory write (fill)
nfs        - boot image via network using NFS protocol
nm         - memory modify (constant address)
pci        - list and access PCI Configuration Space
ping       - send ICMP ECHO_REQUEST to network host
printenv   - print environment variables
rarpboot   - boot image via network using RARP/TFTP protocol
reset      - Perform RESET of the CPU
run        - run commands in an environment variable
saveenv    - save environment variables to persistent storage
saves      - save S-Record file over serial line
setenv     - set environment variables
sleep      - delay execution for some time
tftpboot   - boot image via network using TFTP protocol
USB        - USB sub-system
usbboot    - boot from USB device
version    - print monitor version
&lt;/pre&gt;


And there is one more thing about modular ports. In order to actually implement this, your bootstrapping environment should provide the ability to load several files. On PC this is provided by GRUB2. on CHRP you can read filesystem via OpenFirmware, and Sam's Parthenope relies on modified u-boot. If your bootstrap allows to load only a single file, then you stuck with monolithic kickstart. By the way...  u-boot allows not only to boot up a single uImage or zImage, it also allows to write client programs AFAIK. With this approach, you actually can write modular bootstrap for ARM AROS using unmodified u-boot.

Most used [http://www.compulab.co.il/workspace/mediawiki/index.php5/U-Boot_quick_reference uboot options] are fatls usb 0:1,

the reason behind INTB_KERNEL is to allow use of the standard Exec function AddIntServer() to add interrupt handlers for
hardware drivers etc. AmigaOS never used it for abstract hardware drivers. AmigaOS  routed  only  raw  hardware IRQs there. Their assignment was hardcoded. As well as number of them. Actually on AmigaOS every bus has its own interrupt subsystem. For example PCI bus. PCI interrupts on Amiga are routed to a single exec interrupt.  1:1 relationship between CPU  and hardware interrupts is present only on PC.

IMHO we miss things like AddInterrupt/RemInterrupt methods on our PCI subsystem's device class.  PCI bus class should map these methods to whatever is appropriate. This is how it is done on AmigaOS and friends. When these are implemented, raw kernel.resource API will be needed only for several PC-specific drivers with hardwired resources. Exec IRQs are real IRQs only on Amiga hardware. On other machines they can be emulated where appropriate (VBlank is a good example). kernel.resource is meant  to be different, its IRQs are hardware-agnostic, they are plain &quot;Hardware IRQ number X, whatever this means&quot;. They are low-level actually, and meaningful only in the context of a particular system.

Was that not the transition from irq.hidd to kernel.resource? No.  A long time ago there was another hacky bit named INTB_TIMERTICK. It was &quot;abstract timer interrupt&quot;, used by timer.device. It was the same as VBlank, but with larger frequency. I removed it, because kernel.resource API was a cleaner way to access this interrupt. Furthermore, there can be more than one timer in the system. Thinking about bringing back timer HIDD definitions again. hpet.resource is a bad idea.

Can someone please enlighten me a little on how the scheduler is meant to work?
 
Poseidon.library creates its &quot;Poseidon Event Task&quot; during RTF_COLDSTART -&gt; then calls Wait(), and ends up in limbo because wait disables interrupts (used for the scheduler heartbeat), and basically waits forever because the sigbit is never set, since krnSwitch doesn't switch the task unless TF_SWITCH is set, and no codepath run during this seems to set it?? TF_SWITCH does not disable/enable switching. This flag just enables to run user-supplied hook when the task is being switched away. It is completely safe to call Wait() in Disable()d state. Doing this actually temporarily breaks this state. IDNestCnt gets remembered in struct Task, then next task is selected, and its IDNestCnt is restored in sysbase (see kernel_scheduler.c). If there are no other tasks, then your cpu_Dispatch() should enable interrupts on the CPU and enter idle mode. See x86 implementation for good example.

You miss what happens next...
 1. KrnSwitch() saves context of your task, saves IDNestCnt (core_Switch() and cpu_Switch()), then drops into cpu_Dispatch().
 2. cpu_Dispatch() calls core_Dispatch. Then two cases are possible:
 2a. There is a READY task. It is picked up, its IDNestCnt is restored in SysBase, then cpu_Dispatch() needs to restore registers and exit. The next task is run.
 2b. There are no READY tasks. core_Dispatch() returns NULL. In this case your cpu_Dispatch() should enter idle loop. It should just enable interrupts on the CPU and put it on halt. This allows it to process hardware interrupts. Eventually some of your interrupt handlers wakes up your task and puts it into READY list.

My heartbeat interrupt has been slowed atm to help debugging - but it never actually gets a chance to fire because of the Wait() disabling interrupts. Perhaps you have forgotten to enable interrupts in your idle loop.

There is a change in the format of AROS executables. Until now we were using Elf RELocable files which are usually used as intermediate object files. We had them for various reasons, one of them was how AROS files were built in the past. That days we had no real aros cross compiler and the option to embed relocation data in unix executables (or in executable files in general) was rather new and not every linux/unix system had it. Therefore we have decided to use intermediate files. Although it was somehow working (and it is still working :-)), it has some drawbacks. Therefore decided to introduce real Elf EXEC types, in first turn implemented on ARM target with option to expand in future to all other AROS architectures.

The first patch was pretty easy and appeared to work somehow. It generated nice executables with embedded relocation info. Not only that, it also removed all global symbols adjusting relocation data to be relative to the beginning of the sections. That move reduced number of symbols in each executable significantly (depending on the file between 20 and 80% of all symbols could be removed). The only symbols that stayed in the file are local ones - due to the nature of the patch wasn't able to remove them since we have not seen them in the symbol hash table.

The patch didn't worked though. The files were relocated, AROS kernel loaded, but it crashed very early. What happened? Well, the nature of ARM relocations happened :)

Most of the relocation data on all machines is rather simple. Relocation can be absolute or pc-relative, sometimes the offset has to be bit shifted. On ARM v7 there is another one. There, when one wants to load an address of function/variable into register a combination of two instructions can be used: movw and movt. The first one loads immediate into lower 16 bits of a register while clearing upper 16 bits. The second one loads immediate into upper 16 bits without touching lower halfword. Loading of a pointer into a register looks like this:

        movw r0, #:lower16:label

        movt   r0, #:upper16:label

In this case there are two relocations - one for lower halfword and another for upper. If an overflow of lower 16 bits occurs during relocation process, the upper one should be updated as well. Unfortunately with current patch and with typical ARM executables there is not enough information to perform the calculations.

There are two options - the first one would be to give up and go back to &quot;fake&quot; executables, another one would be to change from REL to RELA relocation info. The latter contains an addend, extra data which can be used to perform all the relocation calculations I need.

Decided for the second option. The patch is already in the works. There is another function for the binutils' bfd backend to perform the final relocation. There can decide what to do with every reloc info, modify data and eventually strip some symbols. An advantage is - at this stage of the linking process have also full access to all local symbols so can change all relocations section relative and eventually strip all symbols from the files. 


 GPU 

VCore developed by Alphamosaic Ltd and now owned by Broadcom. Most of start.elf runs on the GPU.   Placing ALL the userland GPU code in the videocore.hidd isn't going to be a terribly big problem because the code they published is nothing more than a shim that sends data straight to the GPU to execute.

The good news about this is that we only need to write our HIDD using the OpenVG API.   The shim is relatively small codewise and lives in the ARM memory (the actual OpenVG code itself lives in the GPU RAM area and its loaded from start.elf).   That's also the bad news.  Our driver has to translate AROS video calls to OpenVG calls, for most tasks it should be easy, for some, not so much.  It's still probably less difficult and less work, than controlling the GPU directly.

The other good news is that anything done through OpenVG happens on the GPU, its truly accelerated.   It also has some nice font functions, meaning we can lead into an accelerated text mode later.

Basically, AROS resets or locks up when it tries to use AROS_ATOMIC_INC or DEC.  If I comment out the byte/word operations in the header files and use non-atomic operations, the code works as expected.
 
have read that the L1 cache needs to be enabled to use LDREX and co (which I also read is only meant to be used on multi processor systems with shared memory) - however I am certain this is correctly enabled.

If you are using LREX or STREX, you should have L1 cache enabled, at least on the ARM CPU I work with at work.

L1 cache is enabled by enabling the MMU *AND* setting the C and I bits in the CPU - the C bit is ignored, and the I bit only covers the 16 byte instruction pipeline if the MMU is not enabled.

Can you verify that your assembly is generating LDREX/STREX? From the behavior, it almost sounds like its generating the default Semaphore locked atomics.
 Impossible. There are no semaphore-locked atomics. There are Disable()/Enable()-based ones instead. And there's a special #define AROS_NO_ATOMIC_OPERATIONS in this case, which tweaks Disable()/Enable() implementations not to recurse forever.
 I have tested this on ARMv5 which does not have ldrex/strex, it works fine. On those ARMs there's no way to have real atomics. On other OSes (like Linux) this is done by introducing things like atomic_t, which appears to be a complex structure, holding the value together with accompanying spinlock (implemented using swp).

    #warning &quot;TODO: lookup optimal mmu table settings for raspi memory&quot;
        /* Set up an identity-mapping for all 4GB */
        for(x = 0; x &lt; 4096; x ++)
        {
            pagetable[x] = x&lt;&lt;20 | (0x40002|0x80000|0x010000|0x00C00|0x04);
        }

Shouldn't there be a second loop that sets the 'C' bit in the descriptor for the RAM pages?

Currently, you have TEX=0, C=0, B=1 for all pages (Shared Device).

You should have TEX=0, C=1, B=0 for RAM (Write-Through, Cached)

    So ..
     
     pagetable[x] = x&lt;&lt;20 | 2;

     
    should be enough?

No, for RAM you need to change the '| 0x40' to '| 0x80'

tell dosboot the correct defaults to use

Please don't do this. This bootconfig.c is a deprecated legacy thing. I wanted it to go away completely with time. Instead,  display  drivers  should auto-install themselves during own initialization phase. I. e. detect hardware=&gt;instantiate itself. This   should   make  things way simpler. With this approach you only need  to add the driver into KS image to get the device autobooted. No hardcoded stuff. 
Currently  VESA  and  VGA drivers do this, look there for examples. never rewrote ATI driver because i don't have any test system for it.

they defined a smaller AROSCPUContext than the ExceptionContext - yet reference it as ExceptionContext in other places, and since it hasn't allocated enough storage for ExceptionContext, are corrupting memory/the structure (since the elements that are there don't map 1 to 1 with the exception context).

AFAIK, AROS has been moving in a different direction to this in recent years. It is the job of graphics HIDDs to allocate bitmaps etc. so that they have the most suitable characteristics, including allocating them from GPU RAM where possible. The concept of chip RAM is only for legacy code, and most if not all non-68k platforms should have all system RAM
marked as chip.

BTW, is the video processing code you mention CPU code or GPU code?

Also, IIRC we have support for &quot;external memory allocators&quot;. Perhaps that's what we need for the allocation of GPU RAM through the mailbox.

All hosted and x86 native ports should use proper context formats.

trying to clarify if the vblank handler has to have run by this point to prevent this deadlock. Actually, no. Unless you have installed VBlank handler which should wake up at some point. Without VBlank there will be no quantum count. Consequently, there will be no forced preemption. But the rest will work, and multitasking will be cooperative (switch happens only when current task voluntarily gives up the CPU). Does it depend on the vblank having run before this point? and if yes what does that mean on systems where it might be able to run enough code (e.g. get to this point) before the vblank interrupt has triggered? What is it waiting for? It could wait for timer, in this case you need timer.device working. VBlank is currently needed for exec's quantum counter. In current native ports we have only a single timer, which is served by timer.device. VBlank is simulated by timer.device also. If your machine has two timers, then you can use one of them for VBlank, and another for timer.device, this will simplify things down. VBlank needs to be 50 Hz for historical reasons, many programs use it as cheap timer. I am periodically thinking about making some abstract mechanism to be able to change quantum source (and untie it from 50 Hz), but have no time to come up with something good. Additionally i started disliking timer.device hardcoded design when PC has got many timers (old 8253, APIC, HPET).
Currently i think there should be some low-level entity representing tick source. timer.device should just select the most appropriate source for its units.
The BCM2835 has 4 GPU based timer sources - 2 are used by the GPU, so im using Timer3 for our heartbeat and the remaining one will be free to the system. There is also the less capable ARM timer but that is dependent on the CPU frequency. Very good. You won't need any emulation. Set the heartbeat to 50 Hz and drive VBlank from it. Use other timer for MicroHZ.

Can you use the 'econsole.hook' I make for debugging the Sam460 via the serial port?
It provides a before-anything-else shell prompt on the serial port.  You can then do 'NewCLI' to test your graphics, or use any DOS command in shellcommands.resource.

You should just be able to add econsole.hook to your module list, and use 'econsole' in your bootargs.

So long as you have a working Exec/RawMayGetChar and Exec/RawPutChar, it should work.

Also make sure to add shell.resource and shellcommands.resource for this.

That should have done it.

If you set &quot;#define DEBUG 1&quot; in  arch/all-native/econsole/econsole.c, do you get any additional serial output?

have added it to the build and added econsole to the command line - and can see the bootloader picks up on the emergency bootconsole tag, but I still only get the insert bootable media display?

Im assuming it exposes a fake filesystem that tricks aros into booting?
The contents of which are: ECON:AROS.boot

Way to handle the scheduling code? The implementations I had been following were causing problems, due to cascading interrupts which I cant handle properly in the asm stubs just now (when they break disable etc.) - since it means detecting the interrupted codes cpu mode and getting the correct sp/lr for it, and that's just too tedious for arm.
 
To work around this ive added a system idle task which does nothing - and when the scheduling code has no task to run switches this in and lets it run, thereby allowing the interrupts etc to resume until something does need to happen.
 
Also, by adding accounting code to cpu_Switch() and cpu_Dispatch(), it should allow the system to log idle time correctly (as well as running tasks).
 
have thought of also adding an additional task that never runs, solely to record time spent in IRQ handlers, but I digress..

was under the impression that kernel.resource should *never* be used outside of exec.library. This is a wrong impression.
Michal started designing it because portable nature of AROS does not fit well into exec's API with all its assumptions. So, he started the new, hardware-agnostic kernel API from scratch. Yes, exec sits on top of it in places. But kernel always meant to be open thing. Otherwise it would not exist. 
it wasn't meant to be just used willy nilly by user code - but by lower system components (e.g. exec) so that they could be implemented in a more generic fashion, and the kernel resource itself hide the systems quirks.

Adding new things there perfectly keeps up with our decision to minimize AROS-specific intervention into APIs which can clash with MorphOS or Amiga OS4 extensions. We want at least source-level compatibility there. Binary compatibility on PPC would be extremely cool, but at the other hand we have no maintainer for this, as well as their ABIs splintering. 
It depends on what exactly is being implemented - there's no reason we should have everything crammed into kernel.resource if it doesn't need to be (i.e. if its better suited as a separate component/subsystem in its own right)

The _LE versions are for when you have endian swapping taking place.  If the graphics are the same endian as the CPU, no swapping should occur.  I ran into a similar terminology problem in SDL with a friend insisting that his Radeon 7000 on his PC was big-endian.  It is not, it just uses the same endianness for the graphics card and the CPU so no swapping was necessary.  They were both little-endian.
The _LE versions are because the PixFmts refer to the bitmap data being in big endian format in memory, for which the normal version would need to do endianness conversion before applying the shifts/masks. on this platform it is in _LE in memory also so we don't need the conversion hence using the _LE version of the call). would use _LE (if it's really little endian 16 bit mode).

 
What is the bare minimum needed to implement a framebuffer based gfx driver, with our software handling the rest?

Have tried with just a gfx class that only expose new/dispose/newbitmap - and having an onscreenbitmap used only for the framebuffer itself (with all other bitmaps being chunkybm, and the framebuffer's superclass also being chunkybm), but that alone isn't enough it seems?
You can use workbench/hidds/sm502/ as your example - it is as simple as I could make it.
So, AROS creates the framebuffer bitmap (verified this) -&gt; so surely it should be capable of then rendeing into it? I don't actually create the framebuffer &quot;bitmap object&quot; myself - only as a result of being asked to. The code I currently have on SVN seems to create the framebuffers bitmap object fine, but then crashes in intuitions DisplayDriver callback.  In particular it crashes performing the getattr on the system default pointer. don't expose MEMF_CHIP in an allocatable form so AllocSpriteData was failing (and other code later doesn't check if the values are valid == illegal memory accesses) 

So far have -:

vc_init: queries the gpus memory, and sets up a fake memory handler for it, then adds the bootmode driver and returns saying all is well
vc_gfxhidd:New: sets up some fake syncmodes to test with and creates the real gfx object.
vc_gfxhidd:NewBitmap: checks if its a framebuffer and uses the onbitmap class or uses the chunkybm class otherwise
vc_onbitmap:New; creates a chunkybm object and then pushes the real framebuffer address into it as the buffer,

vc4 had v8adds, v8subs, v8muld, v8min and v8max which operated on four 8bit uint values packed into a 32bit register. Multiplication was in the range 0.0 to 1.0 and addition/subtraction saturated. There were also a range unpacking/packing modes that allowed you to pack and unpack 8bit values into 32bit registers. 

RasPi has to speak to the &quot;operating system&quot; which runs on the GPU itself and request/free memory - it cant directly manage it itself, and so the managed functions were used to wrap these calls.

The Arm and GPU share memory space. The framebuffer is shared. The Arm can write a pixel and it will appear on the screen (through GPU hardware) without flushing/copying being required.

The GPU can composite multiple FB's in real time - so you have a number of surfaces defined which are rotated etc and  composited in real time to the output. Copying can map from the address space of the Arm to the flat space of the GPU which takes some code, but I don't think whole buffers are copied.

The DMA hardware can also access the whole memory space and can perform 2D fills and blits (no blending). This is documented in the peripheral spec posted. The DMA is just an Arm accessible peripheral and can be set up with low latency (e.g. microseconds).
must use a 0xc0000000-based bus address to access SDRAM, yet non-DMA access should go via a 0x0-based bus address. 
For 2D dma, set TDMODE, and the spec says &quot;interpret the TXFR_LEN register as YLENGTH number of transfers each of XLENGTH, and add the strides to the address after each transfer.&quot; so set STRIDE to pitch of the image, the width is XLENGTH and height is YLENGTH. You would fill by not setting the SRC_INC and point source to your fill data.

The DMA cannot see the ARM's L1 cache, so you would map the framebuffer with ioremap_nocache. Depending on where the source data comes from, it may need an L1 cache flush. The DMA can see the L2 cache. Use 0xC0000000 bus addresses when L2 is disabled and 0x40000000 bus addresses when L2 is enabled. (actually just call virt_to_bus and you'll get the right address out).

openGLES/openVG has high latency. Writing to framebuffer then reading it back is very inefficient (e.g. milliseconds). If you can drive it a unidirectional way, just streaming commands at then that is efficient. openVG is not implemented on top of openGLES - it uses the same hardware but as a first class interface

To improve the Gfx driver, we will need a DMA resource implemented so can use to perform DMA operations. The Gfx driver will need this to perform blits.


Actually MEMF_CHIP has to present, for historical reasons.
This has been never fully agreed upon, but in ports i wrote i exposed the whole memory as MEMF_CHIP. The idea behind this is that CHIP is originally the memory where graphics and sound data can be put. On non-Amiga platforms there are no restrictions on this, so the whole memory is CHIP.
Yes, many old software can misbehave with CHIP memory size larger than 2MB. But this actually applies only to m68k AROS which is going to run m68k binaries. In other cases it's quite logical to fix the program when porting.

As to original question: yes, it's enough to have a framebuffer bitmap (one with aoHidd_BitMap_FrameBuffer set to TRUE) and PutPixel routine. It framebuffer can be served by chunky bitmap class, then you can simply create chunky bitmap with your own buffer (see how VESA driver does this). Chunky PutPixel is already there.

struggling to determine what is the correct pixfmt to use for the 24/16/15 bit gfx modes on the RasPi.  AFAIK it uses RGB565, for 16bit but im unsure what shifts etc should go with it? suffice to say Im getting the wrong colors so far lol.

&lt;pre&gt;
redmask: 0x0000F800
greenmask: 0x000007E0
bluemask: 0x0000001F
alphamask: 0

redshift: 16
greenshift: 21
blueshift: 27
alphashift: 0
&lt;/pre&gt;

It should likely be vHidd_StdPixFmt_RGB16_LE

This stuff is a bit confusing.  The &quot;names&quot; of the stdpixfmts are based on the layout in memory,
ignoring endianess. So for example:

ARGB32: will be 0xAA 0xRR 0xGG 0xBB in memory on both big endian and little endian machines.

The shifts and masks OTOH are based on pixel access (ULONG in this case), so differ depending
on whether you run on big endian machine or little endian machine (that's why there's stdpixfmt_le.h and
stdpixfmt_be.h in rom/hidds/graphics/).

With the 16 bit pixel format it's even more confusing, as for example it's impossible on little endian machine
to describe RGB16 with shifts/masks alone. That's why there's vHidd_PixFmt_SwapPixelBytes_Flag.
(RGB16 == RRRRRGGG GGGBBBBB in memory, and for pixel (WORD) access on little endian machine it needs to
be accessed as GGGBBBBBRRRRRGGGG).

The shifts btw indicate how much to shift the component to the left (!) so that it is moved to the highest bit (31).

The aHidd_PixFmt_StdPixFmt you specify will be ignored most of the time, because when the pixelfmt is registered,
the gfx hidd checks if there's an identical pixfmt (shifts/masks/etc., but ignoring pixfmt-&gt;stdpixfmt) already in the system,
and if so, it uses the already existing one and does not create a new one.

In theory it would be better if gfx drivers could simply/only specify a StdPixFmt without all the shifts/masks stuff when the
gfx driver uses pixfmt which matches one of the stdpixfmts exactly. Another possibility would be for gfx drivers to use
HIDD_Gfx_GetPIxFmt(stdpixfmt_gfx_driver_wants_to_use) and then peek shifts/masks from it and fill out a pixfmt
tag list based on that.
15bit very blue/green: Try to pass same shifts/masks/etc. as in 16 bit pixfmt (maybe you think it's using 15 bit R5G5B5
(or swapped) but it's actually still using 16 bit R5G6B5 (or swapped).
 aHidd_PixFmt_StdPixFmt you pass is mostly ignored. It's the shift/masks/etc. that count.
But I would still pass the correct one (_LE) == whatever rom/hidds/graphics/stdpixfmts_??.h uses
in the entry where you have looked up shifts/masks/etc.

Use the shifts/masks/etc. from the entry in stdpixfmt_le.h (if you are running on little endian machine) or stdpixfmt_be.h (if you
are running on little endian machine) that matches the pixfmt that its meant to be.

0xAA,0xRR,0xGG,0xBB on little endian (-&gt;entry in stdpixfmt_le.h which says vHidd_StdPixFmt_ARGB32)
0xBB,0xGG,0xRR,0xAA on little endian (-&gt;entry in stdpixfmt_le.h which says vHidd_StdPixFmt_BGRA32)

0xAA,0xRR,0xGG,0xBB on big endian (-&gt;entry in stdpixfmt_be.h which says vHidd_StdPixFmt_ARGB32)
0xBB,0xGG,0xRR,0xAA on big endian (-&gt;entry in stdpixfmt_be.h which says vHidd_StdPixFmt_BGRA32)

it feels like AROS trashes the alpha component, otherwise it should be 8A8R8G8B.

read on the subject suggest its in 1x5r5g5b (x is ignored) to keep 16bit alignment .
 
Suggests to me that wrong shift/mask are being applied - however going by the 16bit versions it all looks correct to me so I am really confused as to what is happening.

The output image looks to have too much green/blue, and very weak red.


 Kickstart 

The  idea  is  to minimize amount of archirecture-specific modules to make the user's  life  easier.  So,  the kickstart was split into 'base' (which  does  not  contain anything machine-specific) and 'BSP' (Board Support Package) which contains all hardware-specific stuff. This  way,  for  example, distribution makers can save up space on CD and  make  CDs with multiple platform support. Different configuration would load the same base with different BSP's.

Next  there  was some part which is entirely missing on hosted. These are   filesystems.  Hosted  ports  do  not need them to boot up, so on hosted   they  are  left  out.  At  the  other  hand,  they  are  also architecture-agnostic.  So  i put them into 'FS' package (standing for 'filesystem').


 USB 

Poseidon  is  one  more  big part. I made it into separate package in order to allow users to omit it if they don't need it (for example, to run  on retro PCs without USB). Personally i have one. Again, Poseidon is  hardware-agnostic (well, there are USB drivers but HCIs are pretty standard).

AFAIK its HCI 1.0 compliant but not familiar enough with poseidons drivers, nor USB, to just hack away at the existing code.  Perhaps once i'm more familiar with the workings I can merge in the changes needed to get it operating but for now I will focus on getting it running.  Also our drivers have known issues so perhaps a fresh set of eyes might shed some light on what is going wrong.

Another interesting question is whether Poseidon can operate on device side. Is it flexible enough? How similar is being a USB host and USB device? think it will need a bit of work on Poseidon's side.  Until then I will force the driver into Host/Master mode in the init code, but leave open device etc to configure the chipset for either's use - and look at trying to add support for working in Device/Slave mode &amp; switching modes once it's up and running.

Actually USBROMStartup is some kind of kludge. Can there be any alternative? Could device drivers be self-installing, like our HIDDs? This would get rid of need to list them in USBRomStartup.

* Model A and B limited to 150 mA per port. 
* Model B+ and Pi 2 introduced configurable 600 mA to 1.2 A support over all ports - anything above that requires a powered USB hub.

Implementing the hardware driver that Poseidon uses to interact with the USB components.

Have code in place to (try) and initialise the USB chipset, and configure host/device mode operation (though AFAICT Poseidon doesn't support device mode). Started to get the &quot;virtual&quot; root hub written for the single USB port so that Poseidon should at least list it correctly in the GUI - and try to interact with it to find peripherals.


The BCM2835 uses a soft IP block from Synopsys’ DesignWare library (DWC), specifically the block is called dwc_usb_2_0_hs_otg_subsystem-ahb_se (“USB 2.0 Hi-Speed OTG Controller Subsystem w/AHB Interface SE”).

There is no public documentation for this, and pretty much zero chance of anyone getting hold of it even with NDA. However, there's a Linux driver written by Synopsys ([https://github.com/raspberrypi/linux dwc_usb]). Specifically directories [https://github.com/raspberrypi/linux/tree/rpi-patches/drivers/usb/host dwc_common_port] and [https://github.com/raspberrypi/linux/tree/rpi-patches/drivers/usb/host dwc_otg].

The Synopsys code is actually under a fairly permissive licence – it's not GPL, it's similar to BSD (’don't sue us if it breaks’ is pretty much the only clause). So this should not be a barrier to porting the code.

The code is really well written, with a nice partition between the work done by the driver (dwc_otg, which is fairly involved, given the host does more work than a conventional EHCI driver), and the interface to Linux (dwc_common_port).

Probably only need provision of relevant changes to dwc_common_port. Other things to consider....

* Provision of necessary headers to get it to compile
* Provision of necessary functions (main issues are wait queues, threads, work queues, tasklets, timers, spinlocks and mutexes (multithreading) )
* Interfacing between USB stack and the driver. dwc_otg/dwc_otg_hcd_linux.c looks like the place to start.

the Linux bits of the headers are only required for the dwc_common_port library. dwc_common_port includes a variety of crypto functions which are not used – it appears to also be used for ultrawideband (UWB) and wireless USB (WUSB) drivers where crypto will be an issue, but it isn't going to be for plain wired USB.

Every USB driver acts as an USB hub as well in order to let Poseidon control the state of USB ports. The code there was reading status of the only USB port in Raspberry's CPU but when changing the status it erroneously deleted some of the status bits, including the port enable one. It was so because those bits in the status register are of a type Read/WriteToClear. It means, if one does not want to change their value from 1 back to 0, one has to actually write the 0 value. Very practical thing e.g. in interrupt handlers, where one reads the interrupt status register to learn what was the interrupt reason, and writes it back to the same register in order to clear the interrupts. 

After fixing that code it turned out that the communication was still unsuccessful. Apparently the USB device was not understanding the host for some reason. That should not happen since the request sent was one of the standard ones implemented by virtually anything with an USB connector, assumed that Poseidon clears the data caches before forwarding the work to the USB drivers but that's the responsibility of the driver itself. 

The USB device responded and acknowledged the transmission! But why were all the request sent after address change failing with timeout? They should not. Once again, address set is supported just by anything. Tried to contact the device at address 0 once again and there it was, still responding properly. The enlightenment came. The bus address for DMA transmissions was, as it is in many bare metal USB implementations, just the pure memory address of the buffer as seen by the ARM cpu. Have &quot;prefixed&quot; it with the real location of uncached RAM and booted AROS once again. 


Trident saw this:

    Product     : Hub: Vdr=0424/PID=9514
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 9
    SubClass  : 0
    DevProto  : 2
    VendorID  : 1060
    ProductID : 38164
    DevVers   : 0200

and this:

    Product     : Vendor: Vdr=0424/PID=EC00
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 255
    SubClass  : 0
    DevProto  : 1
    VendorID  : 1060
    ProductID : 60416
    DevVers   : 0200

and even this:

    Product     : Hub: Vdr=0424/PID=9514
    Manufacturer: Standard Microsystems Corp.
    SerialNumber: n/a
    /Users/michal/git/AROS/rom/USB/poseidon/./poseidon.library.c:psd_20_psdEnumerateDevice/3092: USBVersion: 0200
    Class     : 9
    SubClass  : 0
    DevProto  : 2
    VendorID  : 1060
    ProductID : 38164
    DevVers   : 0200

What are these things? The first one is USB hub built in the Raspberry. Thanks to this one the Pi machines (with exception of Pi0 and computing modules) have more than just one single USB port. The second one is the network chip in raspberry, the third one is my USB SD card reader which have just connected to see what happens. AROS tried, of course, to boot from it ;)

So, the first step towards working USB is done. The control transfers are working as you can see above. Next step is to implement bulk and interrupt transfers, having the basics in place. Finally some error handling will be added and USB for Pi will be as complete as the PC version. 

[http://www.raspyfi.com/raspberry-pi-usb-audio-fix/ Issue with USB Audio]


 Audio 

The Pi 4B is the only Pi that can output HD Audio as an HD Audio passthrough bitstream, and it does it over HDMI. It's possible to use the two HDMI output for separate HDMI video and HDMI audio outputs to allow UHD HDR video and HD Audio with non-UHD HDR compatible AVRs. 

The Pi3B+ and earlier will decode to PCM 5.1/7.1 and output over HDMI.  HDMI is the only interconnect that has a standard for carrying Dolby True HD, DTS HD MA etc. as a bitstream - you can't carry it as a bitstream on any other interface.

Pi3 and Pi4 audio jack output derived from 12bit pulse width modulation is relatively poor. For better, choose USB Audio or I2C versions. 

[https://github.com/raspberrypi/linux/tree/rpi-patches/sound/arm audio] and its [https://github.com/raspberrypi/firmware/issues/2 very high speed message passing interface type of thing VCHI] 

The Model B+ added an additional voltage regulator for the audio output and an additional output driver to drive low-resistance loads like headphones. However it is still using pulse-width modulation (PWM), which has a major impact on sound quality

the old Raspberry Pi used a linear voltage regulator to provide the 3.3V to many of the components on the board while the new one uses a switching regulator. Both can perform reasonably well. However switch mode power supplies often show higher noise figures

Analogue audio

Audio over HDMI rev 1.3 &amp; 1.4


 Ethernet 

10/100 BaseT Ethernet RJ45 socket


 GPIO 

GPIO shouldn't be too bad but bear in mind it is already accessed in places so they would need to allocate pins etc through it (e.g. sdcard to flicker the activity light, serial debug to output data on the GPIO pins)

Probably a resource rather than a device...

Started an i2c driver that will need to allocate GPIO pins. Feel free to work on it if you are interested ;p


 GPU graphics with 2D and 3D acceleration 

Sadly none yet for 32bit but for 64bit... 


 Miscellanous

hdmi issues

Setting the hdmi_force_hotplug=1 makes sure the Pi believes the monitor/TV is really there.

You might also need to set config_hdmi_boost=4 or even higher (up to 9) if your display needs a stronger signal.

If the display is a computer monitor or newer tv, use hdmi_group=1 (auto HDMI use) and if it is an older TV, try hdmi_group=2 (for DMT formats, i.e. for PC monitors) then you HAVE to &quot;set hdmi_drive = 2 to enable HDMI output as this forces HDMI mode rather than DVI mode

Do not set hdmi_safe=1 as that overrides many of the previous options.

Using a shorter or better quality HDMI cable might help. Make sure your Pi's power supply delivers 1 A and not 500 mA.
If you see a problem with the red colour - either absent, or interference - then try a boost

composite video

changing the RCA cable, then the composite port worked out of the box

Boot it as you are doing, without HDMI. If you now plug in the HDMI, do you get the image? In other words, does the Pi think HDMI is connected even when it isn't?

Rename all the files in the first partion of the card except bootcode.bin, start.elf and fixup.dat  What's the result?

Put back config.txt What's the result?

for PAL mode   sdtv_mode=2

dmi_ignore_hotplug Pretends HDMI hotplug signal is not asserted so it appears a HDMI display is not attached
hdmi_ignore_hotplug=1 Use composite mode even if HDMI monitor is detected

&lt;pre&gt;
# NOOBS Auto-generated Settings:
#hdmi_force_hotplug=1
#config_hdmi_boost=4
#overscan_left=24
#overscan_right=24
#overscan_top=16
#overscan_bottom=16
#disable_overscan=0
start_x=1
gpu_mem=128
&lt;/pre&gt;

tvservice -c &quot;PAL 4:3&quot;

&lt;pre&gt;
/opt/vc/bin/tvservice -s   or tvservice -s 
state: HPD high|HDMI mode|HDCP off|composite off (0x12001a), 1920x1080 @ 60 Hz, progressive

/opt/vc/bin/tvservice -m CEA
Group CEA has 1 modes:
(native) mode 16: 1920x1080 @ 60 Hz, progressive

/opt/vc/bin/tvservice -m DMT
Group DMT has 0 modes:
&lt;/pre&gt;

sudo amixer cset numid=3 1

forces the audio to the headphone jack, even with the HDMI video output plugged in

config.txt

the hdmi_ignore_edid_audio=1 option sems relevant as it should tell ALSA that the only available audio is analog, no matter what the display says

There are several different ways that these 4 pole (ring) composite analog cables can be wired up, so some work great in some applications and can be a waste of time in others.

What is needed for the Raspberry Pi B+ and above, which like many camcorders needs the ring contact next to the base contact to be the ground.


The wiring for the 4 pole are:

TIP (LEFT AUDIO CHANNEL)

RING 1 (RIGHT AUDIO CHANNEL)

RING 2 (GROUND/EARTH)

RING 3 BASE/SLEEVE (VIDEO) YELLOW

Most Apple based Players and the Microsoft Zune (TM) are wired this way.

Most analogue camcorders are wired this way as well, where the ground in on Ring 2 will work with the Pi although you may need to swap your Video plug with the Right Audio plug.

Nearly all other MP3 players are not wired this way, the ground is on another ring ie the wrong one.


External devices

* Camera Module Omnivision ov5647 Sunny 5MP (NoIR version) V1.3 - NoIR at 850&amp;nbsp;nm, peak at 880&amp;nbsp;nm and trails off at 940&amp;nbsp;nm wavelengths 
* Camera V2 Sony IMX219 V2.1 8mpixel 8MP 8megapixel - 3280 x 2464 pixels - video at 1080p30, 720p60 and 640x480p90 - wider field of view, 62 vs 54 degrees horizontally - 
* Branded WIFI usb BCM43143 dongle

N.B.  dreaded error after changing cameras (stupidly without turning off the power first) and lasted through several power cycles.  It can be a bad 15-pin FFC ribbon cable, when swapped, camera(s) and the Pi itself are working OK. It can be an instance of a cold solder joint on the CSI connector on the pi board.  the camera can be detected (that's done via I2C) but may still not be able to receive image data (done via CSI-2) if something is broken. CSI-2 is uni-directional. Control is generally done via I2C. 
The CSI-2 receiver always writes to memory, not direct to the ISP. That's the way the Broadcom architecture works as it allows multipass processing easily. GPU memory is accessible from the ARM. Processing using the QPU graphics processors may be possible.  currently the only supported sensor is OV5647 and IMX219.  The linux drivers are all in the firmware blob, else you'd  be looking at at least a man-month of work in a fully fledged imaging lab to do a decent tuning of the camera modules' ISP parameters. 
Static electricity maybe an issue for the camera module and slightly less for the pi board.


== References ==


===Good sites to visit===

*[https://github.com/raspberrypi/firmware/tree/master/ Raspberry Pi Firmware build] 
*[https://www.raspberrypi.com/documentation/computers/software-sources.html Documentation] 
*[https://rpilocator.com/ RPiLocator] 


Linux only
*[https://github.com/raspberrypi/linux Raspberry Pi Linux Build] 
*[https://dietpi.com/ DietPi] 
*[http://www.tinycorelinux.net/ports.html piCore]
*[https://wiki.alpinelinux.org/wiki/Raspberry_Pi Alpine Linux] 
*[https://github.com/armbian/build Armbian] 


*[ FydeOS]
*[ TwisterOS based on ChromiumOS] 
*[https://note.com/jamesmondo/n/nc76e31402be8?hl=en BSD] 


*[https://www.raspberrypi.com/software/operating-systems/ PiOS Lite] and then [https://hstwb.firstrealize.com/ HST] 
*[ PiMiga for pi4 and pi5] 
*[ amibian for pi2 and pi3] 
*[ retropie pi1 and 2] 


Other alternative lighter smaller than Pi OS 
*[https://aros.sourceforge.io/nightly1.html Aros 64bit ARMV8 single core] 
*[https://www.riscosopen.org/wiki/documentation/show/Welcome%20to%20RISC%20OS%20Pi RiscOS on Pi3 and Pi4]
*[https://github.com/michalsc/Emu68 ARM based realtime JIT 68k for amiga computers] 
*[https://github.com/JJDSNT/bellatrix/releases/ Alternative use of Emu68 on Pi3b] 
*[https://github.com/stevereaver/uaos uaOS with Emu68k] 
*[https://github.com/aros-development-team/AROS/commit/f80a268607dfae81b2db94755ab4e4d31ccb72d6 m68kemu library reference] 
*[ HaikuOS]
*[https://github.com/raspberrypi/noobs NOOBS] os loader with successor [https://github.com/procount/pinn PINN] 
*[https://github.com/maxnet/berryboot berryboot]

*[https://github.com/brianwiddas/pi-baremetal Bare Metal Access on Pi 32bit] 


Testing procedure is put sd card in, connect board to board if necessary, plug in hdmi and then power nothing else is done especially CSI DSI etc 

[https://www.raspberrypi.com/documentation/computers/compute-module.html CM5] has the same 55mm x 40mm 2x100pin connectors form factor as the CM4 but [https://www.epdtonthenet.net/article/214508/Key-Considerations-When-Migrating-from-Raspberry-Pi-CM4-to-CM5.aspx some pins and other small things] have changed. Will need the [https://raspipcb.com/tech-blog/raspberry-pi-cm4-vs-cm5-difference-in-booting-from-sd-card/ right IO board to suit] 

*Green [ Raspberry Pi Compute Module 5 IO Board REV2 [https://pip.raspberrypi.com/categories/1097-raspberry-pi-compute-module-5-io-board SC1967]] - untested 
*Green [ RPi Compute Module 5 IO board REV1 [https://pip.raspberrypi.com/categories/1097-raspberry-pi-compute-module-5-io-board SC1751]] - untested 
*Black SupTronics Geekbord X1500 CM5 IO Carrier Board - untested
*Black DeskPi Super6C Cluster Mini-ITX Board - untested 
*[https://sipeed.com/nanocluster Sipeed NanoCluster] - untested up to 7 CM5 
*Green BentoIO CMX0 - untested 
*Box EDATec ED-CLAWBOX - untested 
*Home Assistant Yellow - Kit with PoE with Raspberry Pi Compute Module 5 - untested 
*Blue [https://www.waveshare.com/wiki/CM5_PoE_BASE_A Waveshare CM5-PoE-BASE-A] - untested 
*Box  Waveshare [ CM5-POE-BOX-A] - untested 
*Blue [https://www.waveshare.com/wiki/CM5-IO-BASE-B Waveshare CM5-IO-BASE-B] - untested 
*Blue [https://www.waveshare.com/wiki/CM5-IO-BASE-A Waveshare CM5-IO-BASE-A] - untested 
*Blue Waveshare [https://www.waveshare.com/wiki/CM5-NANO-B CM5-NANO-B] - untested 


*[https://carboncomputers.us/products/pi-flux piFlux]
*[https://carboncomputers.us/products/ Zitaotech Hackberry] CM5 lite only - 
*Portable [https://www.waveshare.com/pocketterm35.htm Waveshare PocketTerm35] with Pi4B or Pi5 - untested 
*Box [https://www.clockworkpi.com/uconsole ClockworkPi uConsole][https://www.youtube.com/watch?v=EtI_bAahbR8 CM4 into an adapter or CM3 into so-dimm - Cyberdeck] - untested 


*Green RPi [https://datasheets.raspberrypi.com/cm4io/CM4IO-KiCAD.zip Compute Module 4] [https://datasheets.raspberrypi.com/cm4io/cm4io-datasheet.pdf IO board] V1.4 [https://datasheets.raspberrypi.com/cm4io/CM4IOUSB3-KiCAD.zip USB3] [https://datasheets.raspberrypi.com/cm4io/cm4iousb3-appnote.pdf CM4ISO] [https://datasheets.raspberrypi.com/cm4/cm4-datasheet.pdf Dual100pin] (2020) aka Development Platform Board - untested 
*Purple Pi Hut Cytron CM4 Maker Board - untested 
*Black DeskPi Super6C Cluster Mini-ITX Board - untested 
*[ KubeSail PiBox mini 2] 
*Home Assistant Yellow with Raspberry Pi Compute Module 4 - untested 
*[ Turing Pi V2] - untested CM4 with 260-pin SO-DIMM socket adapters and/or nvidia jetson nanos - untested 
*Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-C Waveshare CM4-IO-BASE-C] - untested but binary blobs Rev01 Rev02 
*Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-B Waveshare CM4-IO-BASE-B] - untested but binary blobs 
*Blue [https://www.waveshare.com/wiki/CM4-IO-BASE-A Waveshare CM4-IO-BASE-A] - untested but binary blobs 
*Blue [https://www.waveshare.com/wiki/CM4-NANO-B Waveshare CM4-NANO] - untested but usb and audio turned off or rerouted 
*Black [ Seeed Studio with BigTreeTech BTT pad 7] - bin blobs? 


CM3 has a 200 pin sodimm ddr2 connector form factor but not electrically SC0028, SC0029 
*Blue [https://wiki.geekworm.com/CM_IO_Board Geekworm RPi Compute Module IO Board] [https://github.com/geekworm-com/cm-io-board CSI DSI] with CM3 in ddr2 slot underside - '''works''' if SW1 on but CM3+ '''does not''' 
*Green [https://cdn-shop.adafruit.com/product-files/3442/CMIO_schematic.pdf RPi V3 IO board CM3IO] and CM3 Lite - untested 
*Green [https://turingpi.com/ turingpi v1 cluster] - untested up to 7 cm3 7xlan9514 12V discontinued, 3 x Pi4 homelab maybe better 
*Blue [https://www.waveshare.com/wiki/Compute_Module_PoE_Board Waveshare Compute Module PoE Board] and CM3 lite (if not lite, write files to internal eMMC fat32) '''AVOID''' bin blobs 
*Blue [https://www.waveshare.com/compute-module-io-board-plus.htm Waveshare Compute Module IO Board Plus] [https://www.waveshare.com/wiki/Compute_Module_IO_Board_Plus wiki] [https://forums.raspberrypi.com/viewtopic.php?t=235695 pin settings] with CM3+ Lite - '''AVOID''' binary blob 


*[ Pi02w on Geekworm SupTronics X305 Raspberry Pi Zero IO Baseboard] - untested 
*[ Spotpear Pi Zero 2w to Pi3b format-ish] - untested 


*[ pi-top v4] box has 128x64 oled display, micro hdmi, 19Whr battery with pi4 and 15V PD 36W min needed 
*[ pi-top v3] three green pieces, heatsink covers most of the base tray, pi-top hub mk1 lhs and Pi1B Pi2b Pi3b rhs secured from below, black rounded strip with pi-top above keyboard, 13.3&quot; HD 1366 x 768 display, small touchpad, 
*[ pi-top Model 2.0] pi-top on bottom bezel of 14-inch green laptop, large trackpad, keyboard slide down to reveal main system hub on slide rails moved to the right, Raspberry Pi3b screws down, hub slides in, 18V 2.5A 45W charger brick, battery 11.1V 3500mAh 38.85Wh and storage PiTopOS 
*[ Pi-Top CEED Raspberry Pi Modular Educational Desktop with RPI3] monitor 
*[https://www.indiegogo.com/en/projects/jesselozano/pi-top-a-raspberry-pi-laptop-you-build-yourself Pi-Top v1] wedge laptop with RPi2 


&lt;pre&gt;
2008 Trustees collected for Foundation
2009 Pi Foundation charity status gained 
2010 
2011 First Raspberry prototypes 
2012 First boards go on sale at CPC and RS. The Model A and B 700 MHz Arm11 - February 29th BCM 2835
2012 First million sold - more than the 10,000 original planned and anticipated 
2013 First Alpha Experimental builds of AROS Native for the 32bit Pi 
2013 Pi Trading launched making grants available, providing in house educational resources and Pi Academy for teacher training 
2013 Over two million sold 
2014 Over three million sold 
2014 Pi 1 Model B+ introduced that moved composite video to audio jack and same half gig of memory 
2014 Pi Model A+ v1.1 no ethernet and 1 usb - a little smaller - 
2015 Over four million first gen pis sold  
2015 Pi Zero 1.2 BCM2835 first production revision released with no camera port 
2016 Pi0 1.3 released with camera csi connector 
2017 Pi Zero W v1.1 1GHz Pi0W, single-core 32bit CPU BCM2835 released with Cypress CYW43438 wireless 
2020 Raspberry Pi Pico SC0919 with RP2040 32-bit 2Core ARM Cortex-M0+ up to 133 MHz - 264KB of SRAM and 2MB of on-board QSPI Flash - 
2024 Raspberry Pi Pico 2 with RP2350 2Core 32bit Arm Cortex-M33 and 2core open-hardware [https://github.com/wren6991/hazard3 Hazard3 RISC-V] 

2015 Pi 2 Model B v1.1 BCM2836 900/600 MHz ARM Cortex-A7 Armv7 quad 32bit, 32bit VideoCore IV GPU - 1Gb RAM - 5V 2A micro usb - SMSC LAN9514 chip - 
2015 Over a million pi2s sold 


2015 Raspberry Pi 2 Model B version 1.2 Pi2bv1.2, aka Pi2B2 has armv8 BCM2837 underclocked to 900Mhz without wifi/bluetooth module 
2016 Pi 3 Model B - Broadcom BCM2837 SOC four 64bit ARMv8 Cortex-A53 1.2GHz 32bit 1080p VideoCore IV GPU - 1Gb DDR2 - bluetooth 4.1, Cypress CYW43438 wireless 802.11n - 4 x USB2.0 ports - 5.1V 2.5A - SMSC LAN9514 chip 
2016 PIs total over 10 million worldwide 
2017 Compute Module 3 CM3 with BCM2837B0 armv8 Quad 64-bit - small 67.6mm x 31mm board which fits DDR2 SODIMM connector but not electrically compatible which plugs into needed IO board - beware of the I2C protocol issue 
     1Gb LPDDR2 RAM - Lite or 4Gb Emmc storage 
2017 12 million pis sold in total 
2018 Pi 3 Model B+ - 4c A53 BCM2837B0 1.4Ghz - 1Gb, wireless 802.11ac, gigabit ethernet (300Mbit/s) and bluetooth 4.2 - power over ethernet - 4 x USB2.0 ports - Microchip LAN7515 chip 
2019 Over 15 million sold 
2019 Pi 3 Model A+ with BCM2837b0 Cortex-A53 64-bit SoC @ 1.4 GHz with 512Mb LPDDR2, 1 usb2, 1 hdmi, 1 micro usb 5V 2A - no ethernet - 
2019 Raspberry Pi Compute Module 3+ CM3+ - Broadcom BCM2837B0 1.2Ghz, Cortex-A53 (ARMv8) 64-bit SoC on DDR2 SODIMM mechanically compatible only factor - IO board required 
     1Gb DDR2 and 8GB, 16GB, 32GB or a Lite variant without eMMC 
2021 Pi zero 2 (w or no W) RP3A0 quad 1GHz Cortex-A53 64bit BCM2710A1 512mB SDRam 
2025 edaTEC CM0 ED-CM0NANA with additional dev board with quad 1Ghz A53 with 512Mb Raysan RAM, 2 USB2 and 10/100 ethernet - pico castellated edge
 

2019 Pi 4 Model B RPI4B - BCM2711B0T quad 64bit A72 1.5GHz, 4K VideoCore VI, AC wifi, Bluetooth 5.0, GbE Broadcom BCM54213PE (PHY ID 0x600d84a2), 2 micro hdmi decode up to 4K, USB-C 5.1V 3A power, 2xVLI VL805 USB 3, 2xUSB 2.0, 2GB 9LDWW D9WHZ or 4GB 9FDWW D9WHV, 8GB 0AA47 D9ZCL ddr4 ram 
2020 Silent Pi 4 v1.2 upgrade with more USB-c psu support 
2020 PI400 BCM2711C0T 1.8GHz 4Gb DDR4 inside keyboard, 5.1V 5A 27W usb-c psu, 2 micro hdmi, external ide style 40pin gpio, no audio port - 
2020 Raspberry Pi Compute Module 4 BCM2711B0T on new 55mm x 40mm 2x100 pin form factor with extra breakout IO board 
     CM4101000 1Gb RAM Lite SOM 
     CM4102000 2GB RAM Lite 
     CM4104000 4GB RAM Lite 
     CM4004008-4GB-RAM 8GB-EMMC SOM System on Modules 
     CM4104032 4GB RAM 32GB emmc 
     CM4108000 8GB RAM Lite 
     CM4008016 8GB RAM 16Gb eMMc
2021 Raspberry Pi SC0763 Compute Module 4S CM4S with ddr2 sodimm pinouts but not electrically the same with suitable IO board extra cost - 
     CM4S01000 1GB RAM Lite
     CM4S01008 1GB RAM 8GB eMMC Flash
     CM4S02000 2GB RAM Lite
     CM4S04000 4GB RAM Lite
     CM4S04016 4GB RAM 16Gb KLMAG1JETD-B041 
     CM4S08000 8GB RAM Lite 
2021 Pi 4 v1.4 BCM2711B1 upgraded power regulator, to deal with 8gig of ram being more power hungry - 
2021-48 Raspberry Pi 4 model B v1.5 2GB 


2023 Pi 5 v1.0 BCM2712 Quad A76 @2.4Ghz - VideoCore VII - no audio socket - dual 4k from mini hdmi - fan connector - 5.1V 5A psu 
2024 Pi 5 2GB DDR4 version uses BCM2712D0 
2024 Pi-500 with 8Gb LPDDR5 and membrane keyboard 
2024 Pi 5 v1.1 
2024 Raspberry Pi Compute Module 5 CM5 BCM2712 55mm x 40mm form factor with additional IO board 
     CM5004000 04GB RAM 0GB eMMC Lite
     CM5008000 08GB RAM 0GB eMMC Lite
     CM5016000 16GB RAM 0GB eMMC Lite
2025 Pi-500+ with 256GB NVMe storage, 16GB LPDDR4 RAM, and Gateron KS-33 Low Profile Blue mechanical keyboard switches 
2025 Pi5 1GB DDR4 announced 


2022 PiOS linux goes 64bit 
2024 Pi Trading IPO stockmarket stock exchange listing 


2026 April and May Aros 64bit fixed, added AHI audio, VC4 gfx started, usb functions added to rom  
2026 June and July Aros 64bit usb2otg started, dma.resource, sdio.resource, bwfm.device wifi added 
2026 Late July daily 64bit Pi3 LE little endian builds start 
2026 August Pi 4, 400, 5 and 500 DTBs added, expanding existing support and wifi for Pi4 and Pi5 
2026 August Pi5 HAT+ nvme and HDMI, AHI RPiI2S added, Pi4 HVS5 video scaler started, 
2026 
2027 


2028 Pi 6 
&lt;/pre&gt;


The vcgencmd can be used to inspect and dump the current system configuration. 
vcgencmd runs on top of VCHIQ as an RPC. The mailbox interface is an alternate but much simpler RPC. 
VCHIQ is a bridge (queue) between the CPU and the GPU so they can communicate with the firmware. 

Loads of [https://github.com/6by9/rpi3-gpiovirtbuf/blob/master/rpi3-gpiovirtbuf.c mailbox] which uses the GPIO control calls. [https://github.com/raspberrypi/firmware/wiki/Mailboxes may also be of interest] 

A fair number of vcgencmd examples (search for vc_vchi_gencmd_init). [https://www.raspberrypi.org/forums/viewtopic.php?t=229203#p1406112 sends the relevant vcgencmd commands] to update the scaling kernel, but the [https://github.com/raspberrypi/userland/blob/master/host_applications/linux/apps/gencmd/gencmd.c command] is just a text string. Parsing and execution of the instructions is performed by the VideoCore firmware. 

The Raspberry Pi runs two separate operating systems: Linux/Aros on the ARM, and a threedx RTOS called vcos running on the Videocore 4 VPU: vcos is commonly called &quot;the firmware&quot;. Vcos is tasked with performing certain system services, for example running the display and audio outputs. The VCHI driver provides an interface to allow drivers to talk to vcos. 


Doubtful, on any [https://www.web3d.org/ Web3d] [https://developer.mozilla.org/en-US/docs/Web/API/WebGL_API WebGL] or [https://github.com/immersive-web/webxr WebXR] [https://developer.mozilla.org/en-US/docs/Web/API/WebXR_Device_API Device API] [https://developer.mozilla.org/en-US/docs/Web/API/XRInputSource XRInputSource] support. Hopefully, never/limited support features like location, peer-to-peer, invasive web apps, unwarranted storage, payments, proprietary video streaming etc 

*spreadsheet [https://git.sheetjs.com/sheetjs/sheetjs sheetjs] [https://github.com/mleibman/SlickGrid SlickGrid] [https://github.com/6pac/SlickGrid SlickGrid] [https://github.com/jspreadsheet/ce jspreadsheet ce] [https://github.com/dream-num/Luckysheet Luckysheet] [https://github.com/ruilisi/fortune-sheet fortune-sheet] [https://github.com/dream-num/univer/ univer]  probably without xlsx support 
*presentations [https://github.com/impress/impress.js/ impress.js simplified] [https://github.com/bwlewis/slides slides] [https://zenomt.github.io/mdslides/ github markdown slides] [https://github.com/Patternslib/slides Patternslib slides markdown] probably without pptx support 
*weather [https://github.com/kaushalsahu07/weather weather], [https://github.com/Himanshu3412/Weather-Forecast Weather Forecast],  


==Future==


[https://github.com/ARMSX2/ARMSX2 Arm pi of pcsx2] 


{{BookCat}}</text>
      <sha1>i0dsb2uojpmi5e5dvstbw33yskfcp7h</sha1>
    </revision>
  </page>
  <page>
    <title>Seed Factories/Introduction</title>
    <ns>0</ns>
    <id>288346</id>
    <revision>
      <id>4675808</id>
      <parentid>4533276</parentid>
      <timestamp>2026-10-13T09:01:25Z</timestamp>
      <contributor>
        <username>Danielravennest</username>
        <id>13526</id>
      </contributor>
      <minor />
      <comment>font size</comment>
      <origin>4675808</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="31663" sha1="3txzwnmkrfwpwoh2e2lzgjsf94zlteg" xml:space="preserve">{{DISPLAYTITLE:&lt;span style=&quot;display:block;text-align:left;font-size:100%;background:#d0f0f0;line-height:2.5em; font-family:'Georgia', serif;&quot;&gt;Chapter 1.0 - Introduction&lt;/span&gt;}}


&lt;div class=&quot;nonumtoc&quot;&gt;{{TOCright}}&lt;/div&gt;

&lt;div style=&quot;font-size:125%; font-family:'Georgia', serif;&quot;&gt;
&amp;emsp;In engineering, a '''[[w:System|System]]''' is a group of related elements that act by rules to form a whole.  Systems are  distinct entities with boundaries, surrounded by their environment.  They are defined for purposes like understanding, analysis, design, and improvement. Systems can include people, and any other kinds of elements. 

&amp;emsp;Systems have characteristics of interest, such as quality of life, size, emissions, and output rate.  Their change in a desired direction is considered an improvement.  Self-improvement is when the change is produced by internal action of the system.  It has occurred throughout history in many ways, such the as evolution of life, and the development of civilization.

&amp;emsp;Through history, large-scale systems like cities have grown, and made major improvements to themselves.  But intentional design for growth and self-improvement has been rare.  Designing from the start to avoid side effects like environmental damage and pollution is even rarer.  So these volumes are mostly future-oriented, describing types of projects that haven't been done before.  This is in comparison to mature fields like  '''[[w:Civil_engineering|Civil Engineering]]''', where there are many past examples of construction projects, and many people with skills and experience in developing them.


==&lt;span style=&quot;font-size:x-large; font-family:'Georgia', serif;&quot;&gt;1.0 - Volume Overview&lt;/span&gt;==
&amp;emsp;

&amp;emsp;Note that both volumes in this set are incomplete works-in-progress.  They present what we have done so far, but are far from done.  Chapters are divided into numbered web pages, and pages divided into sections and subsections for easier cross-reference.

&amp;emsp;In this volume we consider self-improvement generally, and a particular example called a '''Seed Factory'''.  This is a system with a starter set of equipment intentionally designed to improve by a repeating process:  

&amp;emsp;Part of the factory's capacity is used to make more or better equipment for the factory itself.  The remaining capacity is used to make useful products, like any other factory.  The fraction used for self-improvement can vary over time, according to whatever goals the factory operators choose.  The added equipment increases the ability to make the next round of equipment and further improve.  Output increases as you add more equipment.  So if a significant fraction is devoted to improvement then total capacity can grow exponentially.  This idea matters because civilization faces a number of large-scale problems which can only be addressed by large-scale solutions.  Exponentially growing systems can provide the necessary scale.

&amp;emsp;This Chapter (1.0) introduces some of the problems, how the systems engineering method can be used to develop solutions, and some examples of self-improving designs we will detail later.

&amp;emsp;'''[https://en.wikibooks.org/wiki/Seed_Factories/History Chapter 2]''' goes through the history of self-improvement in nature and in human civilization, and how those led to the problems we face.  We then look at self-improvement as an idea.  It is closely related to other ideas like progress and economic development.  More recently, ideas like self-replicating systems, and technologies like computers and automation, have led to the concept of a seed factory as an instance of self-improvement.  It is still a fairly new approach, so Chapter 2 finishes with what we don't know about it yet, and areas for further research.

&amp;emsp;If new systems are going to address current problems, and not create new ones as a result, they need to be carefully planned and designed before building and operating them.  Engineering is already a well-developed field, so we will not cover all of what already exists.  Instead, the next two chapters cover what is new in our approach from a technical engineering standpoint.

&amp;emsp;'''[https://en.wikibooks.org/wiki/Seed_Factories/Basics Chapter 3]''' presents new design elements to include in the design process.  This includes the current state of the seed factory idea, the pieces which make it up, and a reference architecture for system designs.

&amp;emsp;'''[https://en.wikibooks.org/wiki/Seed_Factories/Design Chapter 4]''' discusses the design process itself.  A constantly growing and improving system is complicated.  So we apply the &quot;systems engineering&quot; approach which was developed to handle such complex projects.  A complete system includes more than just factory equipment, but if it is intended to grow and self-improve it will use a number of production processes and equipment types.  So we provide a reference list of many of the available options as inputs to the design process.

&amp;emsp;'''Chapters 5 through 8''' are a series of design examples for use on Earth.  The series is linked by the fact that one example can grow into or produce starter sets for later ones.  The examples are intended to show how a design is developed, and also serve as a reference for building and operate them.  

&amp;emsp;The last chapter (9.0) of this volume is a set of notes that are too new or don't fit into the main discussion.  It also serves as part of our project database. 
 

&amp;emsp;The environments, resources, and distances are quite different in space compared to Earth.  In addition, objects in space are all in relative motion.  So '''[https://en.wikibooks.org/wiki/Space_Transport_and_Engineering_Methods Volume II]''' begins with the relevant science and engineering methods that apply to space projects.  We then continue the series of design examples for various space locations.  For each location we cover local conditions and resources which will affect the system designs.

&amp;emsp;Space projects are generally in order from nearest to farthest and in difficulty from easier to harder.  Nearest comes first, because the first set of people and equipment must come from Earth.  Later and more difficult locations will in turn get support from Earth and previous space projects.

 
==&lt;span style=&quot;font-size:x-large; font-family:'Georgia', serif;&quot;&gt;2.0 - Some Problems Facing Civilization&lt;/span&gt;==
&amp;emsp;

&amp;emsp;These are engineering-oriented books.  Engineering in general involves applying knowledge towards useful ends, such as satisfying people's needs, solving problems, or making life better.  If seed factories are to be more than just an interesting idea, they should be developed with such useful purposes in mind.  Here we identify some current and future problems facing civilization.  This is by no means a complete list.  Rather, they are problems we think worth solving, and could be addressed by technical solutions.  The ideas and methods in these books can then be applied with these problems in mind.


:'''Insufficient Development'''


&amp;emsp;Many places where people live have less of the artifacts and systems of civilization, and the benefits they bring, relative to intensely developed areas like large high-income cities.  Even in the most developed areas it would be difficult to find people perfectly satisfied with their current situation.  They can usually list a number of things they would like to improve, if only they had more time, money, or other resources.  There is no shortage of desire for improvements.  What is lacking are the means to make them happen.  This is particularly true in difficult or hostile environments, where the extra work required has left them nearly or entirely undeveloped.

&amp;emsp;In addition to uneven development, even the most developed areas have an uneven distribution of resources.  Those who have the least  lead a precarious existence, where any adverse event can seriously degrade their lives.  So in addition to general development, we would like to provide backup systems, reserves, and other buffers against adversity.


:'''A Deteriorating Environment'''


&amp;emsp;A healthy environment is necessary for us to live on Earth.  But side effects of our current civilization have led to changes for the worse.  Probably the most pressing environmental problem is excess carbon dioxide (CO&lt;sub&gt;2&lt;/sub&gt;) leading to climate change.  Others include deforestation, desertification, species extinction, and various kinds of pollution, like airborne particulates and micro-plastics.  In the future we would like to minimize, eliminate, or reverse these side effects and the changes for the worse they have caused.


:'''Technological Unemployment'''


&amp;emsp;Recent centuries have seen accelerating replacement of manual labor with powered equipment.  This produced a shift from farming, which used to be people's main activity, to manufacturing and services.  Continued improvements have reduced manufacturing labor, to where services are now the dominant activity in developed areas.  Since about the mid-20th century, technologies like automation, robotics, software, and artificial intelligence have enabled &quot;Smart Tools&quot;.  These have an increasing ability to work on their own, replacing much of the remaining labor.  

&amp;emsp;Our modern economic system is based on people trading their specialized labor for money, then the money for the other things they need and want.  If most labor can be replaced by smarter tools, we get the problem of technological unemployment.  The unemployed can no longer buy what they need, and the still-employed lose them as customers.  The system of trading work for money and then money for other goods breaks down.

&amp;emsp;This is not yet a severe problem. Through history, people displaced from one kind of work have found something else to do.  But the recent advances in smart tools threaten to displace many jobs in fields like transportation, distribution, and retail in a short period of time.  The displaced workers may not be able to find new jobs in other fields.  It is worth thinking about how to deal with this potential problem ''before'' it becomes severe and we are faced with mass unemployment.


==&lt;span style=&quot;font-size:x-large; font-family:'Georgia', serif;&quot;&gt;3.0 - How to Tackle These Problems?&lt;/span&gt;==
&amp;emsp;

&amp;emsp;Our civilization, and the parts that make it up, are very complex systems.  A method called '''Systems Engineering''' was developed in the 20th century to deal with such systems.  We propose to use it to address the problems noted above.  The systems approach starts by defining the unmet needs which one or more systems are intended to satisfy.  For existing systems this is in terms of what changes are needed.  Identifying what is wanted comes before any consideration of designs or solutions.  Having the answer in mind before stating the problem prematurely limits considering all the options.  Goals should also not be limited by what is thought to be possible now.  Partly meeting the goals, and identifying what research or improvements are needed for the rest is better than limiting our goals and going no further.

&amp;emsp;We identified some problems in a general way above.  For the systems approach we need to specify what we want more exactly.  That way we can measure how well proposed designs or solutions meet the goals, which ones are better or worse, and in what direction to make improvements.  We will start that process here, and continue it in later sections.  Since civilization already exists, these statements are in terms of changes.  The goal statements (in bold face) are followed by some explanations.


:'''(1) Bring less-developed parts of civilization up to [TBD] level of satisfaction with their situation, given sufficient information about their options.  Increase satisfaction in more developed areas by [TBD] and provide means to deal with adverse events.''' - TBD means &quot;to be determined&quot;.  We haven't defined how to measure satisfaction levels yet.  We know we want some kind of measure for it, so we use [TBD] as a marker for later work to fill in.  Significant numbers of people lack education and information on what is possible, and therefore can't know what they would want if they had that knowledge.  Supplying them with that knowledge so they can choose is part of the goal.  Satisfaction with the current state of things is not enough if something bad happens, so we also want to be able to handle adversity.

:'''(2) Reverse human-caused environmental problems by [TBD] percent while minimizing side effects.  To the extent possible, also minimize natural risks.''' - All human activities have side effects, so we can never entirely eliminate them. The goal is then to minimize them, and make them less harmful.  The natural world also presents many hazards, like hurricanes and earthquakes.  We can't eliminate these hazards either, but we can minimize the damage they cause.

:'''(3) Avoid or minimize future problems, such as technological unemployment.''' - Permanently displaced workers due to automation is one problem we already identified.  There may be others we want to deal with ahead of time.  Part of the goal is to identify them.


==&lt;span style=&quot;font-size:x-large; font-family:'Georgia', serif;&quot;&gt;4.0 - Systems and the Systems Engineering Method&lt;/span&gt;==
&amp;emsp;

&amp;emsp;A &quot;System&quot; is any collection of elements which interact with each other and the outside world, and performs some identifiable function or transformation.  For example, a computer system allows you to read this document on Wikibooks.  It contains elements like a power supply, semiconductor chips, and software that work together.  It interacts with you as the reader, and the Internet to access this page.  If you were editing this page, you would be transforming it from one version to the next.

&amp;emsp;We define systems to help with understanding, analysis, design, and improvement, and to help meet intended goals.  Every system has a boundary.  This is a mental construct rather than a wall or a fence.  It separates the system from what is outside the system.  In general the parts of a system are related in some way, and perform an identifiable function.  Sometimes system boundaries are natural and obvious, such as an airplane vs everything outside the airplane.  Other times system boundaries and their contents are arbitrary and in multiple pieces and places.  Defining them can still be helpful in working on a project.

&amp;emsp;A wide variety of things can cross the system boundary, and thus enter or leave the system.  For example, a factory system can take in raw materials and power as inputs, and deliver finished products and various kinds of wastes as outputs.  Physics tells us matter and energy can't spontaneously appear or disappear, only change form.  So mathematically, the change in the contents of a system equals the flows entering the system minus the flows leaving.

&amp;emsp;Systems can be any shape or size, and can contain other, smaller, systems.  Smaller systems within a larger one are called &quot;subsystems&quot;, which can in turn contain even smaller subsystems, to any level of depth.  The human mind can't comprehend the entirety of a large complex system.  So a key method in systems engineering is to break up large systems into smaller subsystems and sub-sub-systems, until they are small enough and simple enough to understand, design, build, etc.  The flows at every level must still equal the change in subsystem contents, so straightforward bookkeeping can ensure nothing has been forgotten or lost in the total system.

&amp;emsp;Having identified problems and set goals, the next step is starting to identify potential solutions that can meet them.  At the start, we don't know what the best approach will be.  So typically multiple candidates will be proposed or formulated.  Over time, most of these will be weeded out and optimized, until one or a few best options remain.  Research and testing may be needed before the final choices are made.  The details of the process are more fully covered in '''[https://en.wikibooks.org/wiki/Seed_Factories/Design Section 4]'''.

&amp;emsp;The premise of these books is that seed factories and self-improving systems can be part of the solutions to the problems noted above.  That needs to be proven, though, and not just assumed.  The examples we present and analyze will help to do that, but they need to be put to actual use and shown to work as expected.

&amp;emsp;Self-improvement is a design feature.  It is not a complete solution by itself.  System designs must also include and build on past experience in fields like '''[[w:Industrial_technology|Industrial Technology]]''', other '''[[w:Engineering|Engineering]]''' fields, and other parts of our accumulated human knowledge.  Those other subjects will be referenced and included where appropriate.


==&lt;span style=&quot;font-size:x-large; font-family:'Georgia', serif;&quot;&gt;5.0- Design Examples&lt;/span&gt;==
&amp;emsp;

&amp;emsp;Chapters 5 through 8 describe four types of self-improving production systems.  Each is intended to help solve the problems and meet the goals noted above. How we do this is by using particular approaches and features in their design.

&amp;emsp;The first problem is that of insufficient development in terms of modern artifacts and systems.  In principle this can be resolved by producing and delivering the needed items.  But that presents several secondary problems.  People in low-income areas may lack funds to pay for such things.  Even if they were donated, they may not have the skills and experience to operate and maintain them.  A solution to both secondary problems is to bootstrap their own production from seed factory starter sets and their own labor.  They will need less funds to build the factories if they self-build them, and they can then make the other finished products they want.  The experience gained in building the factories and making the products will then enable them to operate and maintain them later.

&amp;emsp;In more developed areas, there are still widespread shortages of time, money, or resources to make improvements and increase satisfaction.  Our approach to this is self-improving systems with a high level of smart tools.  Starter sets take less money, smart tools take less time to operate, and the production systems can produce their own energy and obtain material resources.  Due to the higher level of complexity and skills needed, these systems would likely be developed as cooperative projects involving many people.

&amp;emsp;The second problem is risk from environmental damage and natural events.  A start towards solving it is education about these risks and what can be done to reduce them.  New systems can be designed to incorporate renewable energy, avoid or recycle wastes, reduce pollution, and maintain natural habitats.  These design features would be included in both finished products and the production systems that make them.

&amp;emsp;The third item is addressing future problems before they become urgent.  An early task is to identify what those problems might be, besides technological unemployment that we already identified.  Then the systems approach would be used to identify solutions or preventive measures, and incorporate them into system designs.  The unemployment problem could be addressed by production systems of the types in our examples.  Their owner-builders receive a share of their output directly, regardless of how automated the systems are, or how much labor is needed for their operation.  In other words, the production systems work for their owners, so the owners don't have to, or as much.

&amp;emsp;The four examples form a linked series of projects.  One way to move through the series is by evolution.  Enough improvements and growth can turn one example into the next.  Another way is by setting up new seed factories for a later example.  The various parts for new seed factories can be made by matured previous ones.  A later example could also be started fresh by supplying equipment from elsewhere, or by some mixture of internal and outside sources.  However they are started, the experience from earlier projects and their growth paths can be applied to later ones.  

&amp;emsp;The example systems are:  


* '''[[Seed_Factories/Concept|Personal Production]] (Chapter 5)'''


&amp;emsp;This example has the goal of making a range of basic products for a local community of owner/operators, such as food, building materials, and utilities.  It is personal in the sense they make things for their own use and others in their community.  It is not like a personal computer in having just one owner.  It begins with a network of people interested in working together and conventional workshop tools.  At first, production is at hobby and home-use scale.  This keeps early costs within reach.  To this they gradually add a starter set of seed machines.  The combined collection is partly used to make more equipment, alongside the basic products.

&amp;emsp;Later equipment is scaled in size to increase output, and more diverse to increase product range.  The equipment eventually becomes too large for individuals to house, and too expensive for them to afford individually.  The wider product range also becomes too complex for one person to have all the skills needed.  The solution is building or acquiring larger and more dedicated production spaces, and have multiple owners with different skills who work together to make what is needed.  

&amp;emsp;There are two approaches to working together: distributed and centralized.  In the distributed approach, each person owns one or a few pieces of equipment.  A production request is then distributed as needed to the people and their equipment, who do their parts to make the product.  In this approach, ways are needed to settle up the resources and costs in meeting each other's needs.  In the centralized approach, the equipment is in one or a few larger places, with shared ownership.  A mixed approach is also possible, part distributed and part centralized.  

&amp;emsp;As production grows beyond personal needs, the network can start to operate like a commercial workshop, building items for outside customers in addition to the local community.  At the hobby and home-use scale, participation is mostly part-time, and the owners' main support is from conventional work.  As production grows to commercial levels, some of the people can transition to full-time self-employment and have a large part of their physical needs supplied from within the network.


* '''[[Seed_Factories/WWF|The &quot;Makernet&quot;]] (Chapter 6)'''


&amp;emsp;We define a '''Location''' as an area small enough that people can easily travel to work in person, and exchange products with each other.  An example would be a US metropolitan area.  In the Personal Production example, one location can then contain multiple home and dedicated sites where work is done.  Since modern communications are worldwide, the network of people working together and exchanging items does not have to be restricted to a single location.  So our second example extends the distributed approach to multiple locations in different parts of the world.  

&amp;emsp;Production sites are then network nodes that communicate by means such as the Internet.  We call it a &quot;Makernet&quot; because the network collectively makes things.  Owner-operators and customers can communicate with each other by any available method, including electronically.  Smart production machines can also communicate with each other directly, or be controlled by people and software remotely.  

&amp;emsp;Shipping physical items long distances involves significant cost, energy, and time.  Therefore makernet production will tend to be concentrated on items with higher value to mass ratios.  At the high end, electronic design files for new machines and products have no mass, and can be sent anywhere at low cost.  They are well suited for a worldwide network.  At the opposite end crushed stone for construction is heavy and cheap.  It will tend to be limited to a single location near the quarry rather than being shipped long distances.  

&amp;emsp;In a well-developed makernet, a customer may submit a product order to the network through a website.  Production requests are then routed to various network nodes, who supply the materials, fabricate parts, and do other necessary steps.  As each step is completed, payment is routed to the node.  Eventually the finished item is delivered to the customer.  Production nodes can contain any number of machines and processes.  Since new machines can collectively be made by already existing nodes, a single seed factory starter set can in theory extend the network everywhere over time.  

&amp;emsp;For node operators, modern communications allows people to work remotely from the actual equipment.  This has potential advantages in commuting cost and flexibility in hours and location.  The Personal Production example is a local community at a single location.  So much of the interaction can be in person or by voice.  The Makernet approach emphasizes software and networking, with people doing things at times of their choosing, rather than on a work schedule in a conventional factory.  New starter sets would tend to be optimized for size and mass, so they can be shipped farther at reasonable cost.


* '''[[Seed_Factories/Industrial|Industrial Production]] (Chapter 7)'''


&amp;emsp;The goal of this example is large-scale production of more specialized products, much like conventional factories.  It begins with smaller-scale commercial networks like the previous examples, or starter sets specifically designed to grow to industrial scale.  In either case, growth by self-expansion should be a less expensive way to reach the desired production capacity.  In one version, the starter sets are mobile, and are used like construction equipment.  They are brought to a new industrial site and start making parts and equipment.  Once the new factory reaches sufficient capacity, the seed factory components move on to the next project.  In another version, a commercial-scale network grows in place to the larger industrial scale.  

&amp;emsp;Individual industrial sites grow towards scale and efficiency rather than diversity of outputs.  This is partly because it gets harder to fit all the large equipment and operations in one place.  Starter sets and small-scale production favor flexibility in what they can make, at the expense of being less efficient.  At industrial scales, the individual machines can be optimized for their specific tasks.  They are then easier to automate because they each do fewer different things.  

&amp;emsp;Industrial-scale sites can still operate as a network, and make things for each other as needed.  However, the larger scale output goes well beyond the original owner's needs, or even the general needs of a given location  They can then sell products directly to a wider market.  They can also sell production shares to people who otherwise don't participate in site operations.  Production shares entitle people to a share of the products made, either without further payment, or just to cover inputs like raw materials.  An example of this would be a large-scale automated farm, whose shareholders then get a portion of the food produced.  Industrial-scale sites can use conventional factory financing via capital markets if internal funding is not sufficient.


* '''[[Seed_Factories/Remote|Remote and Difficult Locations]] (Chapter 8)'''


&amp;emsp;This book's last example is production in remote locations, or where environment conditions are difficult or extreme.  In such locations, the benefit of self-expanding systems is not having to bring all the infrastructure with you.  Instead, you bring a starter set and produce most of the rest locally.  Examples of remote and difficult locations on Earth include deserts, polar regions, and the ocean surface.  More extreme locations include high altitudes, ice caps, deep underground, or underwater.  Current civilization mostly occupies a thin layer within 30 meters of about 13% of the Earth's surface.  Extending it horizontally to the remaining area, and vertically beyond the first few meters would vastly increase available space and resources.  The key to this is affordability, which self-expanding systems can help provide.  

&amp;emsp;The more difficult and remote the location, the higher the cost of transporting everything there, and the more incentive there is to use a small starter set and build locally.  High levels of automation and productivity can make it possible to live and work in such locations by providing the infrastructure and resources needed.  Remote controlled operation allows building up capacity without necessarily living there.  For example, the Sahara Desert may be a great place to make solar panels, because of abundant sunlight and sand as inputs.  But people may not want to live there full time.  Working remotely can allow that choice.  Conversely, if technology enables living in a remote location, it might be desirable for some people.  Since other people don't live there, land would be cheap.  It might be scenic or have other features people would prefer.


* '''Space (Volume II)'''


&amp;emsp;The most remote and difficult places are regions in space beyond the Earth.  Synchronous orbits, where many satellites operate, are twice as far as any two points on Earth can be, and the farthest known Solar System orbits extend ten million times farther than that.  The space environment has a number of difficult or hostile conditions for people and other living things.  This includes lack of breathable atmosphere and water, high radiation levels, and low gravity.  On the other hand, space contains large amounts of untapped energy and material resources.  If seed factories and self-expanding production can help make these resources accessible, the potential gain for civilization is enormous.  

&amp;emsp;Since the conditions are so different, and involve different engineering specialties and designs, we reserve discussion of their examples to a second volume on '''[https://en.wikibooks.org/wiki/Space_Transport_and_Engineering_Methods Space Systems Engineering]'''.  The examples for space are linked to the previous ones for Earth in a couple of ways.  First, industrial and in some cases remote and difficult locations are needed make and operate transportation to reach space.  Second, the first seed factories to use in space must be designed and built down here, and some of their operation can be remotely controlled from Earth.


*'''[[Seed_Factories/Notes|Conceptual Design Notes]] (Chapter 9)'''


&amp;emsp;The final section of this volume is a collection of material that is (a) too new or not organized enough for the main text, or (b) is too detailed and would interrupt the flow of the discussion.  The ideas we present in these books are a work in progress, so the final section also serves as a kind of &quot;engineer's notebook&quot; to record that work.  In the past, such notebooks were on bound paper or pages in file folders.  Larger sketches and drawings were kept in drawers or rolls.  Only a few people could access them and collaborate.  The modern approach is a shared electronic database where everyone has access to the full contents.  Our work is open-source and we encourage collaboration.  So the notes in Section 9 form part of our database.  Material that is not suited to the Wikimedia format will be stored elsewhere and linked from that section, and from other parts of both volumes.
&lt;/div&gt;

{{BookCat}}</text>
      <sha1>3txzwnmkrfwpwoh2e2lzgjsf94zlteg</sha1>
    </revision>
    <revision>
      <id>4675813</id>
      <parentid>4675808</parentid>
      <timestamp>2026-10-13T10:02:53Z</timestamp>
      <contributor>
        <username>Danielravennest</username>
        <id>13526</id>
      </contributor>
      <minor />
      <comment>Update through section 2.0 insufficient development</comment>
      <origin>4675813</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="31876" sha1="hmxn2jaqldq7lf0nqtocndk0x0tr5mt" xml:space="preserve">{{DISPLAYTITLE:&lt;span style=&quot;display:block;text-align:left;font-size:100%;background:#d0f0f0;line-height:2.5em; font-family:'Georgia', serif;&quot;&gt;Chapter 1.0 - Introduction&lt;/span&gt;}}


&lt;div class=&quot;nonumtoc&quot;&gt;{{TOCright}}&lt;/div&gt;

&lt;div style=&quot;font-size:125%; font-family:'Georgia', serif;&quot;&gt;
&amp;emsp;In engineering, a '''[[w:System|System]]''' is a group of related elements that act by rules to form a whole.  Systems are  distinct entities with boundaries, surrounded by their environment.  They are defined for purposes like understanding, analysis, design, and improvement. Systems can include people, and any other kinds of elements. 

&amp;emsp;Systems have characteristics of interest, such as quality of life, size, emissions, and output rate.  Their change in a desired direction is considered an improvement.  Self-improvement is when the change is produced by internal action of the system.  It has occurred throughout history in many ways, such the as evolution of life, and the development of civilization.

&amp;emsp;Through history, large-scale systems like cities have grown, and made major improvements to themselves.  But intentional design for growth and self-improvement has been rare.  Designing from the start to avoid side effects like environmental damage and pollution is even rarer.  So these volumes are mostly future-oriented, describing types of projects that haven't been done before.  This is in comparison to mature fields like  '''[[w:Civil_engineering|Civil Engineering]]''', where there are many past examples of construction projects, and many people with skills and experience in developing them.


==&lt;span style=&quot;font-size:x-large; font-family:'Georgia', serif;&quot;&gt;1.0 - Volume Overview&lt;/span&gt;==
&amp;emsp;

&amp;emsp;Note that both volumes in this set are incomplete works-in-progress.  They present work we have done so far, but are far from finished.  Longer chapters are divided into numbered web pages, and pages divided into sections and subsections for easier cross-reference.

&amp;emsp;In this volume we consider self-improvement generally, and a particular example called a '''Seed Factory'''.  This is a system that includes a starter set of equipment intentionally designed to improve by a repeating process:  

&amp;emsp;Part of the factory's capacity is used to make more or better equipment for the factory itself.  The remaining capacity is used to make useful products, like any other factory.  The fraction used for self-improvement can vary over time, according to whatever goals the factory operators choose.  The added equipment increases the ability to make the next round of equipment and further improve.  Output capacity increases as you add more equipment.  So if a significant fraction is devoted to improvement then total capacity can grow exponentially.  This idea matters because civilization faces a number of large-scale problems which can only be addressed by large-scale solutions.  Exponentially growing systems can provide the necessary scale.

&amp;emsp;This Chapter (1.0) introduces some of the problems, how the systems engineering method can be used to develop solutions, and some examples of self-improving designs we will detail later.

&amp;emsp;'''[https://en.wikibooks.org/wiki/Seed_Factories/History Chapter 2]''' discusses the history of self-improvement in nature and in human civilization, and how those led to the problems we face.  We then look at self-improvement as an idea.  It is closely related to other ideas like progress and economic development.  More recently, ideas like self-replicating systems, and technologies like computers and automation, have led to the concept of a seed factory as an instance of self-improvement.  It is still a fairly new approach, so Chapter 2 finishes with what we don't know about it yet, and areas for further research.

&amp;emsp;If new systems are going to address current problems, and not create new ones as a result, they need to be carefully planned and designed before building and operating them.  Engineering is already a well-developed field, so we will not cover all of what already exists.  Instead, the next two chapters cover what is new in our approach from a technical engineering standpoint.

&amp;emsp;'''[https://en.wikibooks.org/wiki/Seed_Factories/Basics Chapter 3]''' presents new design elements to include in the design process.  This includes the current state of the seed factory idea, the pieces which make it up, and a reference architecture for system designs.

&amp;emsp;'''[https://en.wikibooks.org/wiki/Seed_Factories/Design Chapter 4]''' discusses the design process itself.  A constantly growing and improving system is complicated.  So we apply the &quot;systems engineering&quot; approach which was developed to handle such complex projects.  A complete system includes more than just factory equipment, but if it is intended to grow and self-improve it will use a number of production processes and equipment types.  So we provide a reference list of many of the available options as inputs to the design process.

&amp;emsp;'''Chapters 5 through 8''' are a series of design examples for use on Earth.  The series is linked by the fact that one example can grow into or produce starter sets for later ones.  The examples are intended to show how a design is developed, and also serve as a reference for building and operating them.  

&amp;emsp;The last chapter (9.0) of this volume is a set of notes that are too new or don't fit into the main discussion.  It also serves as part of our project database. 
 

&amp;emsp;The environments, resources, and distances of regions in space are typically more extreme and larger compared to those on Earth.  In addition, objects in space are all in fairly fast motion relative to each other compared to those on Earth.  So '''[https://en.wikibooks.org/wiki/Space_Transport_and_Engineering_Methods Volume II]''' begins with the relevant science and engineering methods that apply to space projects.  We then continue the series of design examples for various space regions.  For each region we summarize local conditions and available resources.  These will affect how systems are designed for each.

&amp;emsp;Space projects are presented in general order of distance from Earth and in difficulty from easier to harder.  Since the first set of people and equipment must come from Earth, this is the approximate order projects in each region would get started.  Also later and more difficult regions will be able get support both from Earth and previously developed regions.

 
==&lt;span style=&quot;font-size:x-large; font-family:'Georgia', serif;&quot;&gt;2.0 - Some Problems Facing Civilization&lt;/span&gt;==
&amp;emsp;

&amp;emsp;These are engineering-oriented books.  Engineering in general involves applying knowledge towards useful ends, such as satisfying people's needs, solving problems, or making life better.  If seed factories are to be more than just an interesting idea, they should be developed with such useful purposes in mind.  Here we identify some current and future problems facing civilization.  This is by no means a complete list.  Rather, they are problems we think worth solving, and could be addressed by technical solutions.  The ideas and methods in these books can then be applied with these problems in mind.


:'''Insufficient Development'''


&amp;emsp;Many places where people live have less of the artifacts and systems of civilization, and the benefits they bring, relative to intensely developed areas like large high-income cities.  Even in the most developed areas it would be difficult to find people perfectly satisfied with their current situation.  They can usually list a number of things they would like to improve, if only they had more time, money, or other resources.  There is no shortage of desire for improvements.  What is lacking are the means to make them happen.  This is particularly true in difficult or hostile environments, where the extra work required has left them nearly or entirely undeveloped.

&amp;emsp;In addition to uneven development, even the most developed areas have an uneven distribution of resources.  Those who have the least lead a precarious existence, where any adverse event can seriously degrade their lives.  So in addition to general development, we would like to enable backup systems, reserves, and other buffers against adversity.


:'''A Deteriorating Environment'''


&amp;emsp;A healthy environment is necessary for us to live on Earth.  But side effects of our current civilization have led to changes for the worse.  Probably the most pressing environmental problem is excess carbon dioxide (CO&lt;sub&gt;2&lt;/sub&gt;) leading to climate change.  Others include deforestation, desertification, species extinction, and various kinds of pollution, like airborne particulates and micro-plastics.  In the future we would like to minimize, eliminate, or reverse these side effects and the changes for the worse they have caused.


:'''Technological Unemployment'''


&amp;emsp;Recent centuries have seen accelerating replacement of manual labor with powered equipment.  This produced a shift from farming, which used to be people's main activity, to manufacturing and services.  Continued improvements have reduced manufacturing labor, to where services are now the dominant activity in developed areas.  Since about the mid-20th century, technologies like automation, robotics, software, and artificial intelligence have enabled &quot;Smart Tools&quot;.  These have an increasing ability to work on their own, replacing much of the remaining labor.  

&amp;emsp;Our modern economic system is based on people trading their specialized labor for money, then the money for the other things they need and want.  If most labor can be replaced by smarter tools, we get the problem of technological unemployment.  The unemployed can no longer buy what they need, and the still-employed lose them as customers.  The system of trading work for money and then money for other goods breaks down.

&amp;emsp;This is not yet a severe problem. Through history, people displaced from one kind of work have found something else to do.  But the recent advances in smart tools threaten to displace many jobs in fields like transportation, distribution, and retail in a short period of time.  The displaced workers may not be able to find new jobs in other fields.  It is worth thinking about how to deal with this potential problem ''before'' it becomes severe and we are faced with mass unemployment.


==&lt;span style=&quot;font-size:x-large; font-family:'Georgia', serif;&quot;&gt;3.0 - How to Tackle These Problems?&lt;/span&gt;==
&amp;emsp;

&amp;emsp;Our civilization, and the parts that make it up, are very complex systems.  A method called '''Systems Engineering''' was developed in the 20th century to deal with such systems.  We propose to use it to address the problems noted above.  The systems approach starts by defining the unmet needs which one or more systems are intended to satisfy.  For existing systems this is in terms of what changes are needed.  Identifying what is wanted comes before any consideration of designs or solutions.  Having the answer in mind before stating the problem prematurely limits considering all the options.  Goals should also not be limited by what is thought to be possible now.  Partly meeting the goals, and identifying what research or improvements are needed for the rest is better than limiting our goals and going no further.

&amp;emsp;We identified some problems in a general way above.  For the systems approach we need to specify what we want more exactly.  That way we can measure how well proposed designs or solutions meet the goals, which ones are better or worse, and in what direction to make improvements.  We will start that process here, and continue it in later sections.  Since civilization already exists, these statements are in terms of changes.  The goal statements (in bold face) are followed by some explanations.


:'''(1) Bring less-developed parts of civilization up to [TBD] level of satisfaction with their situation, given sufficient information about their options.  Increase satisfaction in more developed areas by [TBD] and provide means to deal with adverse events.''' - TBD means &quot;to be determined&quot;.  We haven't defined how to measure satisfaction levels yet.  We know we want some kind of measure for it, so we use [TBD] as a marker for later work to fill in.  Significant numbers of people lack education and information on what is possible, and therefore can't know what they would want if they had that knowledge.  Supplying them with that knowledge so they can choose is part of the goal.  Satisfaction with the current state of things is not enough if something bad happens, so we also want to be able to handle adversity.

:'''(2) Reverse human-caused environmental problems by [TBD] percent while minimizing side effects.  To the extent possible, also minimize natural risks.''' - All human activities have side effects, so we can never entirely eliminate them. The goal is then to minimize them, and make them less harmful.  The natural world also presents many hazards, like hurricanes and earthquakes.  We can't eliminate these hazards either, but we can minimize the damage they cause.

:'''(3) Avoid or minimize future problems, such as technological unemployment.''' - Permanently displaced workers due to automation is one problem we already identified.  There may be others we want to deal with ahead of time.  Part of the goal is to identify them.


==&lt;span style=&quot;font-size:x-large; font-family:'Georgia', serif;&quot;&gt;4.0 - Systems and the Systems Engineering Method&lt;/span&gt;==
&amp;emsp;

&amp;emsp;A &quot;System&quot; is any collection of elements which interact with each other and the outside world, and performs some identifiable function or transformation.  For example, a computer system allows you to read this document on Wikibooks.  It contains elements like a power supply, semiconductor chips, and software that work together.  It interacts with you as the reader, and the Internet to access this page.  If you were editing this page, you would be transforming it from one version to the next.

&amp;emsp;We define systems to help with understanding, analysis, design, and improvement, and to help meet intended goals.  Every system has a boundary.  This is a mental construct rather than a wall or a fence.  It separates the system from what is outside the system.  In general the parts of a system are related in some way, and perform an identifiable function.  Sometimes system boundaries are natural and obvious, such as an airplane vs everything outside the airplane.  Other times system boundaries and their contents are arbitrary and in multiple pieces and places.  Defining them can still be helpful in working on a project.

&amp;emsp;A wide variety of things can cross the system boundary, and thus enter or leave the system.  For example, a factory system can take in raw materials and power as inputs, and deliver finished products and various kinds of wastes as outputs.  Physics tells us matter and energy can't spontaneously appear or disappear, only change form.  So mathematically, the change in the contents of a system equals the flows entering the system minus the flows leaving.

&amp;emsp;Systems can be any shape or size, and can contain other, smaller, systems.  Smaller systems within a larger one are called &quot;subsystems&quot;, which can in turn contain even smaller subsystems, to any level of depth.  The human mind can't comprehend the entirety of a large complex system.  So a key method in systems engineering is to break up large systems into smaller subsystems and sub-sub-systems, until they are small enough and simple enough to understand, design, build, etc.  The flows at every level must still equal the change in subsystem contents, so straightforward bookkeeping can ensure nothing has been forgotten or lost in the total system.

&amp;emsp;Having identified problems and set goals, the next step is starting to identify potential solutions that can meet them.  At the start, we don't know what the best approach will be.  So typically multiple candidates will be proposed or formulated.  Over time, most of these will be weeded out and optimized, until one or a few best options remain.  Research and testing may be needed before the final choices are made.  The details of the process are more fully covered in '''[https://en.wikibooks.org/wiki/Seed_Factories/Design Section 4]'''.

&amp;emsp;The premise of these books is that seed factories and self-improving systems can be part of the solutions to the problems noted above.  That needs to be proven, though, and not just assumed.  The examples we present and analyze will help to do that, but they need to be put to actual use and shown to work as expected.

&amp;emsp;Self-improvement is a design feature.  It is not a complete solution by itself.  System designs must also include and build on past experience in fields like '''[[w:Industrial_technology|Industrial Technology]]''', other '''[[w:Engineering|Engineering]]''' fields, and other parts of our accumulated human knowledge.  Those other subjects will be referenced and included where appropriate.


==&lt;span style=&quot;font-size:x-large; font-family:'Georgia', serif;&quot;&gt;5.0- Design Examples&lt;/span&gt;==
&amp;emsp;

&amp;emsp;Chapters 5 through 8 describe four types of self-improving production systems.  Each is intended to help solve the problems and meet the goals noted above. How we do this is by using particular approaches and features in their design.

&amp;emsp;The first problem is that of insufficient development in terms of modern artifacts and systems.  In principle this can be resolved by producing and delivering the needed items.  But that presents several secondary problems.  People in low-income areas may lack funds to pay for such things.  Even if they were donated, they may not have the skills and experience to operate and maintain them.  A solution to both secondary problems is to bootstrap their own production from seed factory starter sets and their own labor.  They will need less funds to build the factories if they self-build them, and they can then make the other finished products they want.  The experience gained in building the factories and making the products will then enable them to operate and maintain them later.

&amp;emsp;In more developed areas, there are still widespread shortages of time, money, or resources to make improvements and increase satisfaction.  Our approach to this is self-improving systems with a high level of smart tools.  Starter sets take less money, smart tools take less time to operate, and the production systems can produce their own energy and obtain material resources.  Due to the higher level of complexity and skills needed, these systems would likely be developed as cooperative projects involving many people.

&amp;emsp;The second problem is risk from environmental damage and natural events.  A start towards solving it is education about these risks and what can be done to reduce them.  New systems can be designed to incorporate renewable energy, avoid or recycle wastes, reduce pollution, and maintain natural habitats.  These design features would be included in both finished products and the production systems that make them.

&amp;emsp;The third item is addressing future problems before they become urgent.  An early task is to identify what those problems might be, besides technological unemployment that we already identified.  Then the systems approach would be used to identify solutions or preventive measures, and incorporate them into system designs.  The unemployment problem could be addressed by production systems of the types in our examples.  Their owner-builders receive a share of their output directly, regardless of how automated the systems are, or how much labor is needed for their operation.  In other words, the production systems work for their owners, so the owners don't have to, or as much.

&amp;emsp;The four examples form a linked series of projects.  One way to move through the series is by evolution.  Enough improvements and growth can turn one example into the next.  Another way is by setting up new seed factories for a later example.  The various parts for new seed factories can be made by matured previous ones.  A later example could also be started fresh by supplying equipment from elsewhere, or by some mixture of internal and outside sources.  However they are started, the experience from earlier projects and their growth paths can be applied to later ones.  

&amp;emsp;The example systems are:  


* '''[[Seed_Factories/Concept|Personal Production]] (Chapter 5)'''


&amp;emsp;This example has the goal of making a range of basic products for a local community of owner/operators, such as food, building materials, and utilities.  It is personal in the sense they make things for their own use and others in their community.  It is not like a personal computer in having just one owner.  It begins with a network of people interested in working together and conventional workshop tools.  At first, production is at hobby and home-use scale.  This keeps early costs within reach.  To this they gradually add a starter set of seed machines.  The combined collection is partly used to make more equipment, alongside the basic products.

&amp;emsp;Later equipment is scaled in size to increase output, and more diverse to increase product range.  The equipment eventually becomes too large for individuals to house, and too expensive for them to afford individually.  The wider product range also becomes too complex for one person to have all the skills needed.  The solution is building or acquiring larger and more dedicated production spaces, and have multiple owners with different skills who work together to make what is needed.  

&amp;emsp;There are two approaches to working together: distributed and centralized.  In the distributed approach, each person owns one or a few pieces of equipment.  A production request is then distributed as needed to the people and their equipment, who do their parts to make the product.  In this approach, ways are needed to settle up the resources and costs in meeting each other's needs.  In the centralized approach, the equipment is in one or a few larger places, with shared ownership.  A mixed approach is also possible, part distributed and part centralized.  

&amp;emsp;As production grows beyond personal needs, the network can start to operate like a commercial workshop, building items for outside customers in addition to the local community.  At the hobby and home-use scale, participation is mostly part-time, and the owners' main support is from conventional work.  As production grows to commercial levels, some of the people can transition to full-time self-employment and have a large part of their physical needs supplied from within the network.


* '''[[Seed_Factories/WWF|The &quot;Makernet&quot;]] (Chapter 6)'''


&amp;emsp;We define a '''Location''' as an area small enough that people can easily travel to work in person, and exchange products with each other.  An example would be a US metropolitan area.  In the Personal Production example, one location can then contain multiple home and dedicated sites where work is done.  Since modern communications are worldwide, the network of people working together and exchanging items does not have to be restricted to a single location.  So our second example extends the distributed approach to multiple locations in different parts of the world.  

&amp;emsp;Production sites are then network nodes that communicate by means such as the Internet.  We call it a &quot;Makernet&quot; because the network collectively makes things.  Owner-operators and customers can communicate with each other by any available method, including electronically.  Smart production machines can also communicate with each other directly, or be controlled by people and software remotely.  

&amp;emsp;Shipping physical items long distances involves significant cost, energy, and time.  Therefore makernet production will tend to be concentrated on items with higher value to mass ratios.  At the high end, electronic design files for new machines and products have no mass, and can be sent anywhere at low cost.  They are well suited for a worldwide network.  At the opposite end crushed stone for construction is heavy and cheap.  It will tend to be limited to a single location near the quarry rather than being shipped long distances.  

&amp;emsp;In a well-developed makernet, a customer may submit a product order to the network through a website.  Production requests are then routed to various network nodes, who supply the materials, fabricate parts, and do other necessary steps.  As each step is completed, payment is routed to the node.  Eventually the finished item is delivered to the customer.  Production nodes can contain any number of machines and processes.  Since new machines can collectively be made by already existing nodes, a single seed factory starter set can in theory extend the network everywhere over time.  

&amp;emsp;For node operators, modern communications allows people to work remotely from the actual equipment.  This has potential advantages in commuting cost and flexibility in hours and location.  The Personal Production example is a local community at a single location.  So much of the interaction can be in person or by voice.  The Makernet approach emphasizes software and networking, with people doing things at times of their choosing, rather than on a work schedule in a conventional factory.  New starter sets would tend to be optimized for size and mass, so they can be shipped farther at reasonable cost.


* '''[[Seed_Factories/Industrial|Industrial Production]] (Chapter 7)'''


&amp;emsp;The goal of this example is large-scale production of more specialized products, much like conventional factories.  It begins with smaller-scale commercial networks like the previous examples, or starter sets specifically designed to grow to industrial scale.  In either case, growth by self-expansion should be a less expensive way to reach the desired production capacity.  In one version, the starter sets are mobile, and are used like construction equipment.  They are brought to a new industrial site and start making parts and equipment.  Once the new factory reaches sufficient capacity, the seed factory components move on to the next project.  In another version, a commercial-scale network grows in place to the larger industrial scale.  

&amp;emsp;Individual industrial sites grow towards scale and efficiency rather than diversity of outputs.  This is partly because it gets harder to fit all the large equipment and operations in one place.  Starter sets and small-scale production favor flexibility in what they can make, at the expense of being less efficient.  At industrial scales, the individual machines can be optimized for their specific tasks.  They are then easier to automate because they each do fewer different things.  

&amp;emsp;Industrial-scale sites can still operate as a network, and make things for each other as needed.  However, the larger scale output goes well beyond the original owner's needs, or even the general needs of a given location  They can then sell products directly to a wider market.  They can also sell production shares to people who otherwise don't participate in site operations.  Production shares entitle people to a share of the products made, either without further payment, or just to cover inputs like raw materials.  An example of this would be a large-scale automated farm, whose shareholders then get a portion of the food produced.  Industrial-scale sites can use conventional factory financing via capital markets if internal funding is not sufficient.


* '''[[Seed_Factories/Remote|Remote and Difficult Locations]] (Chapter 8)'''


&amp;emsp;This book's last example is production in remote locations, or where environment conditions are difficult or extreme.  In such locations, the benefit of self-expanding systems is not having to bring all the infrastructure with you.  Instead, you bring a starter set and produce most of the rest locally.  Examples of remote and difficult locations on Earth include deserts, polar regions, and the ocean surface.  More extreme locations include high altitudes, ice caps, deep underground, or underwater.  Current civilization mostly occupies a thin layer within 30 meters of about 13% of the Earth's surface.  Extending it horizontally to the remaining area, and vertically beyond the first few meters would vastly increase available space and resources.  The key to this is affordability, which self-expanding systems can help provide.  

&amp;emsp;The more difficult and remote the location, the higher the cost of transporting everything there, and the more incentive there is to use a small starter set and build locally.  High levels of automation and productivity can make it possible to live and work in such locations by providing the infrastructure and resources needed.  Remote controlled operation allows building up capacity without necessarily living there.  For example, the Sahara Desert may be a great place to make solar panels, because of abundant sunlight and sand as inputs.  But people may not want to live there full time.  Working remotely can allow that choice.  Conversely, if technology enables living in a remote location, it might be desirable for some people.  Since other people don't live there, land would be cheap.  It might be scenic or have other features people would prefer.


* '''Space (Volume II)'''


&amp;emsp;The most remote and difficult places are regions in space beyond the Earth.  Synchronous orbits, where many satellites operate, are twice as far as any two points on Earth can be, and the farthest known Solar System orbits extend ten million times farther than that.  The space environment has a number of difficult or hostile conditions for people and other living things.  This includes lack of breathable atmosphere and water, high radiation levels, and low gravity.  On the other hand, space contains large amounts of untapped energy and material resources.  If seed factories and self-expanding production can help make these resources accessible, the potential gain for civilization is enormous.  

&amp;emsp;Since the conditions are so different, and involve different engineering specialties and designs, we reserve discussion of their examples to a second volume on '''[https://en.wikibooks.org/wiki/Space_Transport_and_Engineering_Methods Space Systems Engineering]'''.  The examples for space are linked to the previous ones for Earth in a couple of ways.  First, industrial and in some cases remote and difficult locations are needed make and operate transportation to reach space.  Second, the first seed factories to use in space must be designed and built down here, and some of their operation can be remotely controlled from Earth.


*'''[[Seed_Factories/Notes|Conceptual Design Notes]] (Chapter 9)'''


&amp;emsp;The final section of this volume is a collection of material that is (a) too new or not organized enough for the main text, or (b) is too detailed and would interrupt the flow of the discussion.  The ideas we present in these books are a work in progress, so the final section also serves as a kind of &quot;engineer's notebook&quot; to record that work.  In the past, such notebooks were on bound paper or pages in file folders.  Larger sketches and drawings were kept in drawers or rolls.  Only a few people could access them and collaborate.  The modern approach is a shared electronic database where everyone has access to the full contents.  Our work is open-source and we encourage collaboration.  So the notes in Section 9 form part of our database.  Material that is not suited to the Wikimedia format will be stored elsewhere and linked from that section, and from other parts of both volumes.
&lt;/div&gt;

{{BookCat}}</text>
      <sha1>hmxn2jaqldq7lf0nqtocndk0x0tr5mt</sha1>
    </revision>
  </page>
  <page>
    <title>Historical Geology/Igneous rocks and stratigraphy</title>
    <ns>0</ns>
    <id>290741</id>
    <revision>
      <id>4675778</id>
      <parentid>3318398</parentid>
      <timestamp>2026-10-13T03:18:12Z</timestamp>
      <contributor>
        <username>~2026-54898-27</username>
        <id>3628301</id>
      </contributor>
      <comment>changed 's/he' to 'they' because it is less clunky language that expresses the same thing (ambiguous gender)</comment>
      <origin>4675778</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="5855" sha1="7r96kvkrhhapdg95ppudrrg534m47iy" xml:space="preserve">[[File:Ponta Sao Lourenço. Madeira.jpg|300px|thumb|right|Intrusive dikes, Madeira.]]In this article we shall briefly recap the facts about [[../Glossary and index#Igneous rock|igneous rocks]] as they relate to [[../Glossary and index#Stratigraphy|stratigraphy]]. The reader may find it helpful to go back and re-read [[../Igneous rocks|the main article on igneous rocks]].

==Igneous rocks and stratigraphy==

From the facts about [[../Glossary and index#Stratigraphy|stratigraphy]] and [[../Glossary and index#Igneous rock|igneous rocks]] that we have covered in previous articles, we may make the following statements:

When they are first formed, extrusive [[../Glossary and index#Igneous rock|igneous rocks]] ([[../Glossary and index#Lava|lava]] flows and [[../Glossary and index#Volcanic ash|volcanic ash]]) will be younger than the [[../Glossary and index#Sedimentary rock|sedimentary rocks]] below them, and will be older than the [[../Glossary and index#Sedimentary rock|sedimentary rocks]] which subsequently form above them.

Why so? Well, by definition, [[../Glossary and index#Extrusive rock|extrusive]] [[../Glossary and index#Igneous rock|igneous rocks]] are [[../Glossary and index#Igneous rock|igneous rocks]] which are deposited on the surface, and so the [[../Glossary and index#Principle of superposition|principle of superposition]] applies to them.

Note that as usual the original position of the rocks can be altered by tectonic events, and if this has happened the original order must be recovered by studying [[../Glossary and index#Way-up structure|way-up structures]] and observation of the [[../Glossary and index#Fault|faults]] and [[../Glossary and index#Fold|folds]] that have been formed. Using our &lt; notation, we may write that if rock A &lt; rock B &lt; rock C, where rocks A and C are sedimentary and rock B is [[../Glossary and index#Extrusive rock|extrusive]], then rock A was deposited before rock B, and rock C was deposited after it.

Now consider [[../Glossary and index#Intrusive rock|intrusive]] [[../Glossary and index#Igneous rock|igneous rocks]]. If we have an intrusive sheet-like structure (a [[../Glossary and index#Sill|sill]]) then this is necessarily younger than the [[../Glossary and index#Sedimentary rock|sedimentary rocks]] below it. But it is also younger than the [[../Glossary and index#Sedimentary rock|sedimentary rocks]] that were above it when it formed. (Note that something must have been above it when it formed, otherwise it would not be [[../Glossary and index#Intrusive rock|intrusive]].)

But it is only older than the sedimentary rocks above it ''when it formed''. Suppose that [[../Glossary and index#Igneous rock|igneous rock]] B intrudes between [[../Glossary and index#Sedimentary rock|sedimentary rocks]] A and C. Then further sediment is deposited on top of C, forming sedimentary rock D. Then B is younger than C but older than D.

When considering [[../Glossary and index#Intrusive rock|intrusive]] [[../Glossary and index#Igneous rock|igneous structures]] such as [[../Glossary and index#Dike|dikes]] and [[../Glossary and index#Pluton|plutons]], we may appeal to the [[../Glossary and index#Principle of cross-cutting relationships|principle of cross-cutting relationships]] to say that they are younger than the [[../Glossary and index#Sedimentary rock|sedimentary rocks]] through which they penetrate.

The reader should bear in mind that we can tell the difference between [[../Glossary and index#Intrusive rock|intrusive]] and [[../Glossary and index#Extrusive rock|extrusive]] [[../Glossary and index#Igneous rock|igneous rocks]] just by looking at them: [[../Glossary and index#Intrusive rock|intrusive]] igneous rocks are [[../Glossary and index#Coarse-grained|coarse-grained]], and [[../Glossary and index#Extrusive rock|extrusive]] igneous rocks are [[../Glossary and index#Fine-grained|fine-grained]]. So even though a [[../Glossary and index#Sill|sill]] and a [[../Glossary and index#Lava flow|lava flow]] are the same shape and may have just the same chemical composition, we can still tell the difference between them by their [[../Glossary and index#Texture|texture]].

==Why is this important?==

So far, we have only been able to consider the relative ages of features in the geological record; we can say that this [[../Glossary and index#Stratum|stratum]] is was deposited before that, and that the deposition of this [[../Glossary and index#Fossil|fossil]] preceded the deposition of the other. But this only provides us with relative ages: we can say that A is older than B, but how much older? Older by a minute? A day? A million years? We have relative ages, but so far we have no actual ''dates''.

Now the crucial thing about [[../Glossary and index#Igneous rock|igneous rocks]] is that we can assign actual dates to them by analysis of the rocks, something we can't usually do directly with [[../Glossary and index#Sedimentary rock|sedimentary rocks]] or [[../Glossary and index#Fossil|fossils]].

A geologist, if handed (for example) a fossil trilobite, cannot perform a physical or chemical analysis of the fossil and tell you how old it is. But if that same geologist finds the trilobite in the field lying in sedimentary rocks between two [[../Glossary and index#Lava flow|lava flows]], then they can find the actual dates of the lava flows, and can then tell you that the trilobite is younger than the oldest lava flow and older than the youngest lava flow, and by assigning dates to the [[../Glossary and index#Lava flow|lava flows]] can tell you that the date of the [[../Glossary and index#Fossil|fossil]] lies between them.

This brings us on to the topic of [[../Glossary and index#Absolute dating|absolute dating]], how it is done, and why it works.

{{chapter navigation|Cross-cutting relationships|Concepts in absolute dating}}

{{BookCat}}</text>
      <sha1>7r96kvkrhhapdg95ppudrrg534m47iy</sha1>
    </revision>
  </page>
  <page>
    <title>Template talk:Punjabi</title>
    <ns>11</ns>
    <id>308760</id>
    <revision>
      <id>4675739</id>
      <parentid>4674326</parentid>
      <timestamp>2026-10-12T14:11:48Z</timestamp>
      <contributor>
        <username>Kittycataclysm</username>
        <id>3371989</id>
      </contributor>
      <comment>Restoring revision 2761316 by [[Special:Contributions/Jaspalkaler|Jaspalkaler]]: later edits appear to be LLM generated</comment>
      <origin>4675739</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="58" sha1="klm48owo43h8qrerx7653oed0586c4f" xml:space="preserve">This page is composed to provide consistent navigation....</text>
      <sha1>klm48owo43h8qrerx7653oed0586c4f</sha1>
    </revision>
  </page>
  <page>
    <title>TI-Basic Z80 Programming/Loops</title>
    <ns>0</ns>
    <id>409648</id>
    <revision>
      <id>4675791</id>
      <parentid>4665715</parentid>
      <timestamp>2026-10-13T06:31:03Z</timestamp>
      <contributor>
        <username>Rex Valerio</username>
        <id>3628187</id>
      </contributor>
      <comment>Fix grammar and spelling in For loop description</comment>
      <origin>4675791</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="7224" sha1="42nb8x5iev9uzfo9kv6ovvsjcrrfy21" xml:space="preserve">It is important while writing programs to save space due to the calculator's limited memory. To help this, loops can be used which can repeat a section of code a number of times. TI-Basic offers a few types of loops: &lt;code&gt;While&lt;/code&gt;, &lt;code&gt;For&lt;/code&gt;, and &lt;code&gt;Repeat&lt;/code&gt;.
== While ==
The &lt;code&gt;'''[[../List of Commands/While|While]]'''&lt;/code&gt; ({{TI-Basic/Key|PRGM}}&lt;code&gt; '''''CTL'' 5'''&lt;/code&gt;) loop executes a block of commands between the &lt;code&gt;While&lt;/code&gt; and &lt;code&gt;End&lt;/code&gt; commands as long as the specified condition is true. The condition is tested at the beginning of the loop (when the &lt;code&gt;End&lt;/code&gt; command is encountered), so if the condition is initially false, the block of commands will never execute.
=== Syntax ===
{{bcode:Syntax|
While ''condition is true''
''statements''
End
|
* Where &lt;code&gt;condition&lt;/code&gt; is any statement resulting in a true/false/zero/non-zero result
** If &lt;code&gt;condition&lt;/code&gt; returns true or non-zero, &lt;code&gt;statement&lt;/code&gt; continues to execute 
** If &lt;code&gt;condition&lt;/code&gt; returns false or zero, &lt;code&gt;statement&lt;/code&gt; will not execute and will skip to after the &lt;code&gt;End&lt;/code&gt;
}}
=== Examples ===
The following example demonstrates a very basic &lt;code&gt;While&lt;/code&gt; Loop that will display &lt;code&gt;X&lt;/code&gt; until &lt;code&gt;Y&lt;/code&gt; equals 0:
{{bcode:Example|
:While Y≠0
:Disp X
:End
}}
== For ==
The &lt;code&gt;'''[[../List of Commands/For|For]]'''&lt;/code&gt; ({{TI-Basic/Key|PRGM}}&lt;code&gt; '''''CTL'' 4'''&lt;/code&gt;) loop executes a block of commands between the &lt;code&gt;For&lt;/code&gt; and &lt;code&gt;End&lt;/code&gt; commands ''n'' number of times. &lt;code&gt;For&lt;/code&gt; is useful when you know the exact number of times you want to repeat a section of code.
=== Syntax ===
{{bcode:Syntax|
For(variable,begin,end[,increment])
''statements''
End
|
* Where &lt;code&gt;variable&lt;/code&gt; is a &lt;code&gt;Real&lt;/code&gt; (A-Z &amp; θ). This variable represents a counter.
* Where &lt;code&gt;begin&lt;/code&gt; is the number to begin counting from
* Where &lt;code&gt;end&lt;/code&gt; is the number to stop execution once &lt;code&gt;variable&lt;/code&gt; equals &lt;code&gt;end&lt;/code&gt;
* Where, optionally, &lt;code&gt;increment&lt;/code&gt; is the amount to change &lt;code&gt;variable&lt;/code&gt; after each loop. If this argument is not passed, it is assumed to be &lt;code&gt;1&lt;/code&gt;.
}}
=== Examples ===
To print the numbers 1 to 5 using a &lt;code&gt;For&lt;/code&gt; loop:
{{bcode:Example|
:For(I,1,5)
:Disp I
:End
}}
This code will print:
{{Bcode:Output|&lt;nowiki&gt;
               1
               2
               3
               4
               5&lt;/nowiki&gt;}}
----
To traverse a list and print its elements:
{{bcode:Example|
:For(I,1,dim(L1))
:Disp L1(I)
:End
}}
== Repeat ==
The &lt;code&gt;'''[[../List of Commands/Repeat|Repeat]]'''&lt;/code&gt; ({{TI-Basic/Key|PRGM}}&lt;code&gt; '''''CTL'' 6'''&lt;/code&gt;) loop executes a block of commands between the &lt;code&gt;Repeat&lt;/code&gt; and &lt;code&gt;End&lt;/code&gt; commands until specified condition is true. The condition is tested at the beginning of the loop (when the &lt;code&gt;End&lt;/code&gt; command is encountered), so if the condition is initially true, the block of commands will never execute.

&lt;code&gt;Repeat&lt;/code&gt; is simply &lt;code&gt;While&lt;/code&gt; where the condition is inverted.
=== Syntax ===
{{bcode:Syntax|
Repeat ''condition''
''statements''
End
|
* Where &lt;code&gt;condition&lt;/code&gt; is any statement resulting in a true/false/zero/non-zero result
** If &lt;code&gt;condition&lt;/code&gt; returns false or zero, &lt;code&gt;statement&lt;/code&gt; continues to execute 
** If &lt;code&gt;condition&lt;/code&gt; returns true or non-zero, &lt;code&gt;statement&lt;/code&gt; will not execute and will skip to after the &lt;code&gt;End&lt;/code&gt;
}}
=== Examples ===
The following example demonstrates the use of a &lt;code&gt;Repeat&lt;/code&gt; statement. It will continue to ask the user for an &lt;code&gt;X&lt;/code&gt; value until &lt;code&gt;X &gt; 5 &lt;/code&gt;:
{{bcode:Example|
:0→X
:Repeat X&gt;5
:Prompt X
:End
}}

== You try it! ==
Try these examples to practice using loops.
=== Summation from 1 to ''n'' ===
Write a program that asks the user for a number ''n'' (must be greater than 1) and prints the sum of the numbers 1 to ''n''. For example, if ''n'' = 6, the program would display &lt;code&gt;21&lt;/code&gt; (&lt;math&gt;1+2+3+4+5+6=21&lt;/math&gt;).
{{Collapse top|title=Solution}}
{{bcode:Example|
:0→N         // Clear n
:Repeat N&gt;1  // Until n is greater than 1,
:Prompt N    // Ask for n
:End         // End repeat loop
:0→S         // Clear s (sum)
:For(X,1,N)  // From 1 to n,
:S+X→S       // Add X to S
:End         // End for loop
:Disp S      // Print
}}
{{Collapse top|title=Alternate solution using summation}}
{{bcode:Example|
:0→N             // Clear n
:Repeat N&gt;1      // Until n is greater than 1,
:Prompt N        // Ask for n
:End             // End repeat loop
:Disp Σ(X,X,1,N) // Summation Σ(expression,variable,start,end)
}}
This example uses the following summation expression: &lt;math&gt;\sum_{i=1}^N x_i&lt;/math&gt;
{{Collapse bottom}}
{{Collapse bottom}}
=== Fibonacci Sequence ===
The Fibonacci Sequence is defined as &lt;math&gt;F(n) = F(n-1) + F(n-2)&lt;/math&gt; where &lt;math&gt;F(1) = 0&lt;/math&gt; and &lt;math&gt;F(2) = 1&lt;/math&gt;. Therefore, the first 10 elements of the sequence are &lt;code&gt;0, 1, 1, 2, 3, 5, 8, 13, 21, 34&lt;/code&gt;. Write a program that stores the first 100 elements of the sequence to &lt;code&gt;L&lt;small&gt;1&lt;/small&gt;&lt;/code&gt;, then display them. ''Remember, you will have to instantiate the list first.''
{{Collapse top|title=Solution}}
{{bcode:Example|&lt;nowiki&gt;
:DelVar L1               // List instantiation
:100→dim(L1)             // List instantiation
:0→L1(1)                 // F(1) = 0
:1→L1(2)                 // F(2) = 1
:For(A,3,100)            // We start at 3 since 1 and 2 are already set
:L1(A-1)+L1(A-2)→L1(A)   // F(N) = F(N-1) + F(N-2)
:End                     // End for loop
:ClrHome                 // Clear screen
:For(A,1,100)            // From 1 to 100
:Disp L1(A)              // Print F(A)
:End                     // End for loop&lt;/nowiki&gt;
}}
{{Collapse bottom}}
=== FizzBuzz ===
FizzBuzz is a children's game often used today as a programming evaluation program. The original game consists of players taking turns to count incrementally, replacing any number divisible by 3 with the word &quot;fizz&quot;, and any number divisible by 5 with the word &quot;buzz&quot;. For this example, write a program that counts from 1 to 100, replacing numbers divisible by 3 with &quot;Fizz&quot;, 5 with &quot;Buzz&quot;, and 3 and 5 with &quot;FizzBuzz.&quot;

''Hint: Take the remainder of the current value and the key numbers and compare it to 0.''

You will have to get creative writing this program as there are many ways to approach it. The following solution is just one of many solutions:
{{Collapse top|title=Solution}}
In this example, we must check multiples of 15 before checking 3 or 5.
{{bcode:Example|&lt;nowiki&gt;
:ClrHome
:For(X,1,100)
:If remainder(X,15)=0:Then
:Disp &quot;FIZZBUZZ&quot;
:Else
:If remainder(X,3)=0:Then
:Disp &quot;FIZZ&quot;
:Else
:If remainder(X,5)=0:Then
:Disp &quot;BUZZ&quot;
:Else
:Disp X
:End
:End
:End
:End&lt;/nowiki&gt;
}}
{{Collapse top|title=Solution without &lt;code&gt;remainder&lt;/code&gt;}}
{{bcode:Example|&lt;nowiki&gt;
:ClrHome
:For(X,1,100)
:If fPart(X/15)*15=0:Then
:Disp &quot;FIZZBUZZ&quot;
:Else
:If fPart(X/3)*3=0:Then
:Disp &quot;FIZZ&quot;
:Else
:If fPart(X/5)*5=0:Then
:Disp &quot;BUZZ&quot;
:Else
:Disp X
:End
:End
:End
:End&lt;/nowiki&gt;
}}
{{Collapse bottom}}
{{Collapse bottom}}

{{BottomNav|Conditional Statements|Advanced Variables}}</text>
      <sha1>42nb8x5iev9uzfo9kv6ovvsjcrrfy21</sha1>
    </revision>
  </page>
  <page>
    <title>Super Smash Bros. Melee/Movelists/Gannondorf</title>
    <ns>0</ns>
    <id>426368</id>
    <revision>
      <id>4675765</id>
      <parentid>4440510</parentid>
      <timestamp>2026-10-12T21:20:34Z</timestamp>
      <contributor>
        <username>WereSpielChequers</username>
        <id>248949</id>
      </contributor>
      <minor />
      <comment>typo</comment>
      <origin>4675765</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3814" sha1="s0u2ppby9eyxpqyxkzxe4qtytw3h2wu" xml:space="preserve">==Basic Techniques==
====Standard Attacks====
{| border=1 cellspacing=0 cellpadding=2 style=&quot;border-collapse:collapse&quot;
|- bgcolor=#eeeeee
!bgcolor=&quot;#CCCCCC&quot;|Button(s)
!bgcolor=&quot;#CCCCCC&quot;|Description/notes
|-
| A
| A quick punch.
|-
| Forward + A
| Kick out in front of him.
|-
| Dash + A
| Rams into you with his shoulder
|-
| Down + A
| Kneels down and &quot;trips&quot; you with a ground kick.
|-
| Up + A
| Brings his foot above his head and slams it down onto the ground.
|-
| Smash Forward + A
| Thrusts his elbow forward, sending the opponent away in flames.
|-
| Smash Down + A
| He brings his foot behind him, then strongly kicks forward, then behind him.
|-
| Smash Up + A
| He ducks then kicks twice above his head. Usually the first kick is weak putting the enemy in perfect position for the second kick. If the opponent is far from him and gets hit with just the foot, it'll send him flying.
|-
| A (Lying down)
| Does a handstand, then does the splits while upside down attacking both in front of him and behind him at the same time, then flips back onto his feet.
|-
| A (Hanging of Edge)
| Ganondorf jumps back onto the edge, then does a quick kick.
|}

====Aerial Attacks====
{| border=1 cellspacing=0 cellpadding=2 style=&quot;border-collapse:collapse&quot;
|- bgcolor=#eeeeee
!bgcolor=&quot;#CCCCCC&quot;|Button(s)
!bgcolor=&quot;#CCCCCC&quot;|Description/notes
|-
| A
| He kicks while doing a kick.
|-
| Forward + A
| He performs a rather devastating punch. If your timing is of, it'll be very weak. If you connect just as he executes it, it'll be very strong and the enemy will get sent flying at a low trajectory.
|-
| Backwards + A
| He twists his body around and punches behind him.
|-
| Down + A
| He rams his feet downward sending opponents downward, unless they're on the ground. Then they go up.
|-
| Up + A
| He does a backflip in the air, attacking with his feet.
|}

====Special Attacks====
{| border=1 cellspacing=0 cellpadding=2 style=&quot;border-collapse:collapse&quot;
|- bgcolor=#eeeeee
!bgcolor=&quot;#CCCCCC&quot;|Button(s)
!bgcolor=&quot;#CCCCCC&quot;|Attack
!bgcolor=&quot;#CCCCCC&quot;|Description/notes
|-
| B
| Warlock Punch
| He charges up this punch for a little less than a second then unleashes a fiery attack that sends opponents flying quite far, even with the slightest damage.
|-
| Up + B
| Dark Dive
| He jumps into the air, attempting to grab an enemy. If he does then he attacks then causes an explosion, sending you away, in flames, might I add. If you've double jumped and you get hit, you can double jump again. If you connect with this move you can repeat it.
|-
| Down + B
| Wizard's Foot
| On the ground, he slides across the ground with a &quot;magic forcefield&quot; in front of him. In the air, he dives downward in the same fashion, and can spike in this fashion. 
|-
| Forward + B
| Gerudo Dragon
| On the ground, he charges forward for a short distance, and when he connects, he sends the opponent upward, in flames again. An aerial Gerudo Dragon will send the opponent up, but be careful, because you'll lose all attacking ability, as if you used an Up-B.
|}
====Throws====
{| border=1 cellspacing=0 cellpadding=2 style=&quot;border-collapse:collapse&quot;
|- bgcolor=#eeeeee
!bgcolor=&quot;#CCCCCC&quot;|Button(s)
!bgcolor=&quot;#CCCCCC&quot;|Description/notes
|-
| Down
| He throws the opponent on the ground. Follow up with a Gerudo Smash.
|-
| Forward
| He Punches you up into the air. Many moves can follow this.
|-
| Up
| After grabbing you, he will smash you upward with an open palm, sending you sky high.
|-
| Back
| He kicks you from behind himself. On the edge, you can follow with a Meteor Smash.
|}

==Advanced Techniques==
====Double Double Jump====
Double jump, then do a Wizard's Foot. Afterwards you can Double jump again. Since he loses a lot of height after the kick, only use it if you are hit away from the stage on a high trajectory.

{{bookcat}}</text>
      <sha1>s0u2ppby9eyxpqyxkzxe4qtytw3h2wu</sha1>
    </revision>
  </page>
  <page>
    <title>User talk:Xeverything11/updates</title>
    <ns>3</ns>
    <id>452115</id>
    <revision>
      <id>4675797</id>
      <parentid>4675621</parentid>
      <timestamp>2026-10-13T07:40:22Z</timestamp>
      <contributor>
        <username>MediaWiki message delivery</username>
        <id>1188004</id>
      </contributor>
      <comment>/* Tech News: 2026-42 */ new section</comment>
      <origin>4675797</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1199801" sha1="jmbx75f8qpt4xq6fzefh6s1fwppey29" xml:space="preserve">&lt;noinclude&gt;
{{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]]
}}
&lt;/noinclude&gt;
__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}} ==

&lt;section begin=&quot;technews-2023-W03&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;{{int:last}}&quot; links on page history now contain &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;diff=prev&amp;oldid=[revision ID]&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; in place of &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;diff=[revision ID]&amp;oldid=[revision ID]&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt;. 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 &lt;code&gt;{{ns:1}}:&lt;/code&gt; and &lt;code&gt;{{ns:3}}:&lt;/code&gt; namespaces.  These will be extended to other talk namespaces, such as &lt;code&gt;{{ns:5}}:&lt;/code&gt;.  They will continue to be unavailable in non-talk namespaces, including &lt;code&gt;{{ns:4}}:&lt;/code&gt; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2023/03|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2023-W03&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 01:11, 17 January 2023 (UTC)
&lt;!-- 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&amp;oldid=24381020 --&gt;

== Tech News: 2023-04 {{User:Xeverything11/tags/updates}} ==

&lt;section begin=&quot;technews-2023-W04&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2023/04|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2023-W04&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 23:46, 23 January 2023 (UTC)
&lt;!-- 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&amp;oldid=24418874 --&gt;

== Tech News: 2023-05 {{User:Xeverything11/tags/updates}} ==

&lt;section begin=&quot;technews-2023-W05&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2023/05|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2023-W05&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 00:06, 31 January 2023 (UTC)
&lt;!-- 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&amp;oldid=24455949 --&gt;

== Wikipedia translation of the week: 2023-06 {{User:Xeverything11/tags/updates}} ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Sweden Finns' Day]] '''&lt;br /&gt; &lt;small&gt;''([[:fi:Ruotsinsuomalaisten päivä]]) ([[:sv:Sverigefinnarnas dag]])''&lt;/small&gt;  &lt;/div&gt;

Please be bold and help translate this article!

----
[[File:Sverigefinskaflaggan.svg|center|300px]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=24491747 --&gt;

== Tech News: 2023-06 {{User:Xeverything11/tags/updates}} ==

&lt;section begin=&quot;technews-2023-W06&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;What links here&quot; 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 &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;skins=…&lt;/code&gt;&lt;/bdi&gt; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2023/06|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2023-W06&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 10:21, 6 February 2023 (UTC)
&lt;!-- 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&amp;oldid=24491749 --&gt;

== Wikipedia translation of the week: 2023-07 {{User:Xeverything11/tags/updates}} ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Delivery robot]] '''&lt;br /&gt;  &lt;/div&gt;

Please be bold and help translate this article!

----
[[File:Woman Takes Groceries from Dax Delivery Robot.jpg|center|300px]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
A '''delivery robot''' is an autonomous robot that provides &quot;last mile&quot; 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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=24515453 --&gt;

== Tech News: 2023-07 {{User:Xeverything11/tags/updates}} ==

&lt;section begin=&quot;technews-2023-W07&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2023/07|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2023-W07&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 01:49, 14 February 2023 (UTC)
&lt;!-- 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&amp;oldid=24540832 --&gt;

== Wikipedia translation of the week: 2023-08 {{User:Xeverything11/tags/updates}} ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Buddha Dhatu Jadi]] '''&lt;br /&gt;  &lt;/div&gt;

Please be bold and help translate this article!

----
[[File:Swarno Mandir.JPG|center|300px]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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.

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=24581813 --&gt;

== Tech News: 2023-08 {{User:Xeverything11/tags/updates}} ==

&lt;section begin=&quot;technews-2023-W08&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2023/08|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2023-W08&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 01:58, 21 February 2023 (UTC)
&lt;!-- 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&amp;oldid=24570514 --&gt;

== Wikipedia translation of the week: 2023-09 {{User:Xeverything11/tags/updates}} ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Alina Scholtz]] '''&lt;br /&gt;  &lt;/div&gt;

Please be bold and help translate this article!

----

&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=24617511 --&gt;

== Tech News: 2023-09 {{User:Xeverything11/tags/updates}} ==

&lt;section begin=&quot;technews-2023-W09&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2023/09|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2023-W09&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 23:47, 27 February 2023 (UTC)
&lt;!-- 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&amp;oldid=24634242 --&gt;

== Wikipedia translation of the week: 2023-10 {{User:Xeverything11/tags/updates}} ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Mary Nzimiro]] '''&lt;br /&gt;  &lt;/div&gt;

Please be bold and help translate this article!

----

&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=24636259 --&gt;

== Tech News: 2023-10 {{User:Xeverything11/tags/updates}} ==

&lt;section begin=&quot;technews-2023-W10&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2023/10|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2023-W10&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 23:50, 6 March 2023 (UTC)
&lt;!-- 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&amp;oldid=24676916 --&gt;

== Wikipedia translation of the week: 2023-11 {{User:Xeverything11/tags/updates}} ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Elizabeth Langdon Williams]] '''&lt;br /&gt;  &lt;/div&gt;

Please be bold and help translate this article!

----
[[File:Elizabeth Langdon Williams.jpg|300px|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=24700408 --&gt;

== Tech News: 2023-11 {{User:Xeverything11/tags/updates}} ==

&lt;section begin=&quot;technews-2023-W11&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;[[mw:Special:MyLanguage/Help:Growth/Tools/Add a link|Add a link]]&quot; ({{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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2023/11|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2023-W11&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 23:20, 13 March 2023 (UTC)
&lt;!-- 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&amp;oldid=24700189 --&gt;

== Wikipedia translation of the week: 2023-12 {{User:Xeverything11/tags/updates}} ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:I Didn't Raise My Boy to Be a Soldier]] '''&lt;br /&gt;  &lt;/div&gt;

Please be bold and help translate this article!

----
[[File:Peerless Quartet - I Didn't Raise my Boy to be a Soldier.ogg|300px|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
an American anti-war song that was influential within the pacifist movement that existed in the United States before it entered World War I. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=24720571 --&gt;

== Tech News: 2023-12 {{User:Xeverything11/tags/updates}} ==

&lt;section begin=&quot;technews-2023-W12&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2023/12|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2023-W12&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 01:26, 21 March 2023 (UTC)
&lt;!-- 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&amp;oldid=24732558 --&gt;

== Wikipedia translation of the week: 2023-13 {{User:Xeverything11/tags/updates}} ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:es:Diana Aguavil]]'''&lt;br /&gt; &lt;small&gt;''([[:en:Diana Aguavil]]) ([[:pt:Diana Aguavil]])        ''&lt;/small&gt;  &lt;/div&gt;

Please be bold and help translate this article!

----
[[File:Diana Aguavil.jpg|300px|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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.

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=24758626 --&gt;

== Tech News: 2023-13 {{User:Xeverything11/tags/updates}} ==

&lt;section begin=&quot;technews-2023-W13&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2023/13|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2023-W13&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 01:14, 28 March 2023 (UTC)
&lt;!-- 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&amp;oldid=24780854 --&gt;

== Tech News: 2023-14 {{User:Xeverything11/tags/updates}} ==

&lt;section begin=&quot;technews-2023-W14&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;jquery.hoverIntent&lt;/code&gt;&lt;/bdi&gt; 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 &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;hover()&lt;/code&gt;&lt;/bdi&gt; or &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;on()&lt;/code&gt;&lt;/bdi&gt; 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 &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;__ARCHIVEDTALK__&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; magic word.  There will also be a new &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;.mw-archivedtalk&lt;/code&gt;&lt;/bdi&gt; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2023/14|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2023-W14&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 23:40, 3 April 2023 (UTC)
&lt;!-- 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&amp;oldid=24820268 --&gt;

== Tech News: 2023-15 {{User:Xeverything11/tags/updates}} ==

&lt;section begin=&quot;technews-2023-W15&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;{{int:Echo-category-title-edit-user-page}}&quot; 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 &quot;[[mw:Special:MyLanguage/Help:Growth/Tools/Add a link|Add a link]]&quot; ({{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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2023/15|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2023-W15&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 20:05, 10 April 2023 (UTC)
&lt;!-- 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&amp;oldid=24851886 --&gt;

== Wikipedia translation of the week: 2023-16 ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:it:Lucy Salani]]'''&lt;br /&gt; &lt;small&gt;''([[:en:Lucy Salani]]) ([[:fr:Lucy Salani]])        ''&lt;/small&gt; &lt;/div&gt;

Please be bold and help translate this article!

----
[[File:Lucy Salani.jpg|300px|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''Lucy Salani''' was an Italian activist and is considered the only Italian transgender person to have survived the Nazi concentration camps.

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=24872966 --&gt;

== Tech News: 2023-16 ==

&lt;section begin=&quot;technews-2023-W16&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;{{int:Kartographer-sidebar-nearbybutton}}&quot;. 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 &quot;{{int:globalwatchlist-markpageseen}}&quot; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2023/16|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2023-W16&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 01:55, 18 April 2023 (UTC)
&lt;!-- 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&amp;oldid=24881071 --&gt;

== Wikipedia translation of the week: 2023-17 ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:ca:María Fernanda Castro Maya]]'''&lt;br /&gt; &lt;small&gt;''([[:pt:María Fernanda Castro Maya]]) ([[:eu:María Fernanda Castro Maya]])        ''&lt;/small&gt; &lt;/div&gt;

Please be bold and help translate this article!

----

&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''María Fernanda Castro Maya''' is a Mexican self-advocate disability rights activist.

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=24872966 --&gt;

== Tech News: 2023-17 ==

&lt;section begin=&quot;technews-2023-W17&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2023/17|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2023-W17&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 22:04, 24 April 2023 (UTC)
&lt;!-- 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&amp;oldid=24933592 --&gt;

== Wikipedia translation of the week: 2023-18 ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Sonia Orbuch]]'''&lt;br /&gt; &lt;/div&gt;

Please be bold and help translate this article!

----

&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=24872966 --&gt;

== Tech News: 2023-18 ==

&lt;section begin=&quot;technews-2023-W18&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;Who Wrote That?&quot; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2023/18|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2023-W18&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 01:45, 2 May 2023 (UTC)
&lt;!-- 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&amp;oldid=24966974 --&gt;

== Wikipedia translation of the week: 2023-19 ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Nadia Ghulam]]'''&lt;br /&gt;&lt;small&gt;''([[:fr:Nadia Ghulam]]) ([[:es:Nadia Ghulam]]) ([[:ca:Nadia Ghulam]])''&lt;/small&gt;  &lt;/div&gt;

Please be bold and help translate this article!

----
[[File:Nadia Ghulam (cropped).jpg|center|300px|]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=24966177 --&gt;

== Tech News: 2023-19 ==

&lt;section begin=&quot;technews-2023-W19&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;wikitext&lt;/code&gt;&lt;/bdi&gt; as a selected language. Old alternatives that were used to highlight wikitext, such as &lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;html5&lt;/code&gt;&lt;/bdi&gt;, &lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;moin&lt;/code&gt;&lt;/bdi&gt;, and &lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;html+handlebars&lt;/code&gt;&lt;/bdi&gt;, 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&amp;section=new&amp;preload=MediaWiki:July Here is an example] at the {{int:project-localized-name-cswiki/en}} that uses &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;preload=MediaWiki:July&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt;. [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 &lt;bdi lang=&quot;de&quot; dir=&quot;ltr&quot;&gt;[[:de:Modul:Graph]]&lt;/bdi&gt;. 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&amp;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]] &lt;code&gt;jquery.tipsy&lt;/code&gt; will be removed from the MediaWiki core. This will affect some user scripts. Many lines with &lt;code&gt;.tipsy(&lt;/code&gt; can be commented out. &lt;code&gt;OO.ui.PopupWidget&lt;/code&gt; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2023/19|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2023-W19&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 00:36, 9 May 2023 (UTC)
&lt;!-- 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&amp;oldid=24998636 --&gt;

== Wikipedia translation of the week: 2023-20 ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Purple Day]]'''&lt;br /&gt; &lt;/div&gt;

Please be bold and help translate this article!

----
[[File:Epilepsy Warrior Brooch May 2018 Purple Day.jpg|center|300px|]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=25000361 --&gt;

== Tech News: 2023-20 ==

&lt;section begin=&quot;technews-2023-W20&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;[[mw:Special:MyLanguage/Help:Growth/Tools/Add a link|Add a link]]&quot; ({{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 &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;jquery.cookie&lt;/code&gt;&lt;/bdi&gt; with &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;mediawiki.cookie&lt;/code&gt;&lt;/bdi&gt;. The &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;jquery.cookie&lt;/code&gt;&lt;/bdi&gt; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2023/20|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2023-W20&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 21:45, 15 May 2023 (UTC)
&lt;!-- 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&amp;oldid=25011501 --&gt;

== Tech News: 2023-21 ==

&lt;section begin=&quot;technews-2023-W21&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;recent edits&quot; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2023/21|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2023-W21&quot;/&gt;

16:55, 22 May 2023 (UTC)
&lt;!-- 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&amp;oldid=25028325 --&gt;

== Wikipedia translation of the week: 2023-22 ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Valencian Art Nouveau]]'''&lt;br /&gt; &lt;small&gt;''([[:es:Modernismo valenciano]])''&lt;/small&gt; &lt;/div&gt;

Please be bold and help translate this article!

----
[[File:Santuario Novelda.jpg|center|300px|]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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.

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=25074014 --&gt;

== Tech News: 2023-22 ==

&lt;section begin=&quot;technews-2023-W22&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;{{int:watchlistedit-normal-check-all}}&quot; 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 - &quot;check all&quot; checkbox|voted #161 in the 2023 Community Wishlist Survey]]. [https://phabricator.wikimedia.org/T334252]	

'''Problems'''
* For a few days earlier this month, the &quot;Add interlanguage link&quot; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2023/22|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2023-W22&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 22:04, 29 May 2023 (UTC)
&lt;!-- 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&amp;oldid=25079963 --&gt;

== Wikipedia translation of the week: 2023-23 ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:pt:Alessandra Korap]]'''&lt;br /&gt; &lt;small&gt;''([[:en:Alessandra Korap]])         ''&lt;/small&gt;  &lt;/div&gt;

Please be bold and help translate this article!

----

&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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.

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=25111481 --&gt;

== Tech News: 2023-23 ==

&lt;section begin=&quot;technews-2023-W23&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;{{int:Rcfilters-group-results-by-page}}&quot;. 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2023/23|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2023-W23&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 22:52, 5 June 2023 (UTC)
&lt;!-- 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&amp;oldid=25114640 --&gt;

== Wikipedia translation of the week: 2023-24 ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Cassinga Day]]'''&lt;br /&gt;  &lt;/div&gt;

Please be bold and help translate this article!

----

&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''Cassinga Day''' is a national public holiday in Namibia remembering the Cassinga Massacre. Commemorated annually on 4 May, the date &quot;remembers those (approximately 600) killed in 1978 when the South African Defence Force attacked a SWAPO base at Cassinga in southern Angola&quot;. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=25111481 --&gt;

== Tech News: 2023-24 ==

&lt;section begin=&quot;technews-2023-W24&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;Who Wrote That?&quot; 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 &lt;code&gt;&lt;nowiki&gt;__TOC__&lt;/nowiki&gt;&lt;/code&gt; (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 &quot;{{int:Visualeditor-dialog-meta-categories-defaultsort-label}}&quot; feature in VisualEditor is broken. Existing &lt;code&gt;&lt;nowiki&gt;{{DEFAULTSORT:...}}&lt;/nowiki&gt;&lt;/code&gt; 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 &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;#wpReason&lt;/code&gt;&lt;/bdi&gt; with &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot; style=&quot;white-space: nowrap;&quot;&gt;&lt;code&gt;#wpReason &gt; input&lt;/code&gt;&lt;/bdi&gt;. See [https://cs.wikipedia.org/w/index.php?title=MediaWiki%3AGadget-CleanDeleteReasons.js&amp;diff=22859956&amp;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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2023/24|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2023-W24&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 14:52, 12 June 2023 (UTC)
&lt;!-- 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&amp;oldid=25133779 --&gt;

== Tech News: 2023-25 ==

&lt;section begin=&quot;technews-2023-W25&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &lt;code&gt;\&lt;/code&gt; or pressing &lt;code&gt;ctrl + shift + p&lt;/code&gt;. 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2023/25|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2023-W25&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 20:09, 19 June 2023 (UTC)
&lt;!-- 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&amp;oldid=25159510 --&gt;

== Wikipedia translation of the week: 2023-26 ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Rawon]]'''&lt;br /&gt;  &lt;/div&gt;

Please be bold and help translate this article!

----
[[File:Rawon Setan.jpg|center|300px]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=25177056 --&gt;

== Tech News: 2023-26 ==

&lt;section begin=&quot;technews-2023-W26&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;/&lt;/code&gt;&lt;/bdi&gt; to all &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;prop=extlinks&lt;/code&gt;&lt;/bdi&gt; responses for bare domains. This is part of the work to remove duplication in the &lt;code&gt;externallinks&lt;/code&gt; 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 &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;.mbox-text&lt;/code&gt;&lt;/bdi&gt; 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 &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;|targets=&lt;/code&gt;&lt;/bdi&gt; 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 &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;|skins=&lt;/code&gt;&lt;/bdi&gt; parameter in &lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;MediaWiki:Gadgets-definition&lt;/bdi&gt;) 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2023/26|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2023-W26&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 16:19, 26 June 2023 (UTC)
&lt;!-- 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&amp;oldid=25202311 --&gt;

== Wikipedia translation of the week: 2023-27 ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Hook echo]]'''&lt;br /&gt;  &lt;/div&gt;

Please be bold and help translate this article!

----
[[File:Tornadic classic supercell radar.gif|center|300px]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=25241057 --&gt;

== Tech News: 2023-27 ==

&lt;section begin=&quot;technews-2023-W27&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2023/27|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2023-W27&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 22:51, 3 July 2023 (UTC)
&lt;!-- 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&amp;oldid=25231546 --&gt;

== Tech News: 2023-28 ==

&lt;section begin=&quot;technews-2023-W28&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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&amp;messages=&amp;x=D#sortable:0=asc the state of WikiEditor localization into your language], and if the &quot;Completion&quot; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2023/28|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2023-W28&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 19:54, 10 July 2023 (UTC)
&lt;!-- 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&amp;oldid=25278797 --&gt;

== Wikipedia translation of the week: 2023-29 ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Esther Cooper Jackson]]'''&lt;br /&gt; &lt;small&gt;''([[:fr:Esther Cooper Jackson]]) ([[:simple:Esther Cooper Jackson]])''&lt;/small&gt; &lt;/div&gt;

Please be bold and help translate this article!

----
[[File:Esther Cooper Jackson, 1968, Great Barrington.jpg|center|300px]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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.

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=25266525 --&gt;

== Tech News: 2023-29 ==

&lt;section begin=&quot;technews-2023-W29&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;en-ca&lt;/code&gt;&lt;/bdi&gt; and &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;en-gb&lt;/code&gt;&lt;/bdi&gt; 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 &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;action=growthsetmentorstatus&lt;/code&gt;&lt;/bdi&gt; API will be deprecated with the new MediaWiki version. Bots or scripts calling that API should use the &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;action=growthmanagementorlist&lt;/code&gt;&lt;/bdi&gt; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2023/29|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2023-W29&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 23:08, 17 July 2023 (UTC)
&lt;!-- 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&amp;oldid=25289122 --&gt;

== Wikipedia translation of the week: 2023-30 ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Cut of pork]]'''&lt;br /&gt;  &lt;/div&gt;

Please be bold and help translate this article!

----
[[File:American Pork Cuts.svg|center|300px]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=25318972 --&gt;

== Tech News: 2023-30 ==

&lt;section begin=&quot;technews-2023-W30&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2023/30|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2023-W30&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 02:20, 25 July 2023 (UTC)
&lt;!-- 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&amp;oldid=25332248 --&gt;

== Wikipedia translation of the week: 2023-31 ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Gunhild Cross]]'''&lt;br /&gt;  &lt;/div&gt;

Please be bold and help translate this article!

----
[[File:Gunhildkorset.jpg|center|300px]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=25380210 --&gt;

== Tech News: 2023-31 ==

&lt;section begin=&quot;technews-2023-W31&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;office hours&quot;|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 &quot;[[mw:Special:MyLanguage/Help:Growth/Tools/Add a link|Add a link]]&quot; ({{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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2023/31|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2023-W31&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 23:54, 31 July 2023 (UTC)
&lt;!-- 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&amp;oldid=25362228 --&gt;

== Wikipedia translation of the week: 2023-32 ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Polyura athamas]]'''&lt;br /&gt;  &lt;/div&gt;

Please be bold and help translate this article!

----
[[File:Close wing mud-puddling position of Charaxes bharata (C.&amp; R. Felder,1867) - Indian Nawab.jpg|center|300px]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''''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). 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=25410866 --&gt;

== Tech News: 2023-32 ==

&lt;section begin=&quot;technews-2023-W32&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;{{int:Mobile-frontend-mobile-option-amc}}&quot; in your settings and use the &quot;{{int:Minerva-page-actions-editfull}}&quot; button in the &quot;{{int:Minerva-page-actions-overflow}}&quot; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2023/32|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2023-W32&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 21:21, 7 August 2023 (UTC)
&lt;!-- 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&amp;oldid=25420038 --&gt;

== Wikipedia translation of the week: 2023-33 ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Women's page]]'''&lt;br /&gt;  &lt;/div&gt;

Please be bold and help translate this article!

----
[[File:&quot;Doings in Pittsburg Society&quot; The Pittsburg Press February 1, 1920.png|center|300px]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=25427472 --&gt;

== Tech News: 2023-33 ==

&lt;section begin=&quot;technews-2023-W33&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;[[mw:Special:MyLanguage/Help:Growth/Tools/Add a link|Add a link]]&quot; ({{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] &lt;!-- TODO replace wiki codes --&gt;

'''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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2023/33|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2023-W33&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 06:00, 15 August 2023 (UTC)
&lt;!-- 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&amp;oldid=25428668 --&gt;

== Wikipedia translation of the week: 2023-34 ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Insect toxin]]'''&lt;br /&gt; &lt;small&gt;''([[:de:Insektengift]])''&lt;/small&gt; &lt;/div&gt;

Please be bold and help translate this article!

----
[[File:PDB 1lmr EBI.jpg|center|300px]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''Insect toxins''' are various protein toxins produced by insect species. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=25427472 --&gt;

== Tech News: 2023-34 ==

&lt;section begin=&quot;technews-2023-W34&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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:|&lt;code&gt;wikt:blk:&lt;/code&gt;]]) [https://phabricator.wikimedia.org/T343540]
*** a Wikisource in [[d:Q34002|Sundanese]] ([[s:su:|&lt;code&gt;s:su:&lt;/code&gt;]]) [https://phabricator.wikimedia.org/T343539]
** To catch up, the next most recent six wikis are:
*** Wikifunctions ([[f:|&lt;code&gt;f:&lt;/code&gt;]]) [https://phabricator.wikimedia.org/T275945]
*** a Wiktionary in [[d:Q2891049|Mandailing]] ([[wikt:btm:|&lt;code&gt;wikt:btm:&lt;/code&gt;]]) [https://phabricator.wikimedia.org/T335216]
*** a Wikipedia in [[d:Q5555465|Ghanaian Pidgin]] ([[w:gpe:|&lt;code&gt;w:gpe:&lt;/code&gt;]]) [https://phabricator.wikimedia.org/T335969]
*** a Wikinews in [[d:Q3111668|Gungbe]] ([[n:guw:|&lt;code&gt;n:guw:&lt;/code&gt;]]) [https://phabricator.wikimedia.org/T334394]
*** a Wiktionary in [[d:Q33522|Kabardian]] ([[wikt:kbd:|&lt;code&gt;wikt:kbd:&lt;/code&gt;]]) [https://phabricator.wikimedia.org/T333266]
*** a Wikipedia in [[d:Q35570|Fante]] ([[w:fat:|&lt;code&gt;w:fat:&lt;/code&gt;]]) [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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2023/34|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2023-W34&quot;/&gt;

15:25, 21 August 2023 (UTC)
&lt;!-- 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&amp;oldid=25497111 --&gt;

== Wikipedia translation of the week: 2023-35 ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Manchester Blitz]]'''&lt;br /&gt;  &lt;/div&gt;

Please be bold and help translate this article!

----
[[File:Air Raid Damage in Britain- Manchester HU49833.jpg|center|300px]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=25427472 --&gt;

== Tech News: 2023-35 ==

&lt;section begin=&quot;technews-2023-W35&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;prpbengalicurrency&lt;/code&gt;&lt;/bdi&gt; label to denote Bengali currency characters as page numbers inside the &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;&lt;pagelist&gt;&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; tag.  [https://phabricator.wikimedia.org/T268932]
* Two preferences have been relocated. The preference &quot;{{int:visualeditor-preference-visualeditor}}&quot; is now shown on the [[Special:Preferences#mw-prefsection-editing|&quot;{{int:prefs-editing}}&quot; tab]] at all wikis. Previously it was shown on the &quot;{{int:prefs-betafeatures}}&quot; tab at some wikis. The preference &quot;{{int:visualeditor-preference-newwikitexteditor-enable}}&quot; is now also shown on the &quot;{{int:prefs-editing}}&quot; tab at all wikis, instead of the &quot;{{int:prefs-betafeatures}}&quot; 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 &lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[https://idm.wikimedia.org/ idm.wikimedia.org]&lt;/bdi&gt;, 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 &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;=&gt;&lt;/code&gt;&lt;/bdi&gt; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2023/35|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2023-W35&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 14:00, 28 August 2023 (UTC)
&lt;!-- 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&amp;oldid=25510866 --&gt;

== Wikipedia translation of the week: 2023-36 ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Ghana Independence Act 1957]]'''&lt;br /&gt;  &lt;/div&gt;

Please be bold and help translate this article!

----

&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=25427472 --&gt;

== Tech News: 2023-36 ==

&lt;section begin=&quot;technews-2023-W36&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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:|&lt;code&gt;w:tly:&lt;/code&gt;]]) [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 &quot;[[mw:Special:MyLanguage/Help:Growth/Tools/Add a link|Add a link]]&quot; ({{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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2023/36|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2023-W36&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 23:34, 4 September 2023 (UTC)
&lt;!-- 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&amp;oldid=25566983 --&gt;

== Wikipedia translation of the week: 2023-37 ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Betrayal trauma]]'''&lt;br /&gt; &lt;small&gt;''([[:sv:Svektrauma]]) ([[:ar:صدمة الخيانة]]) ([[:ko:배신 트라우마]])''&lt;/small&gt; &lt;/div&gt;

Please be bold and help translate this article!

----

&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''Betrayal trauma''' is defined as a trauma perpetrated by someone with whom the victim is close to and reliant upon for support and survival. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=25427472 --&gt;

== Tech News: 2023-37 ==

&lt;section begin=&quot;technews-2023-W37&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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, &quot;{{int:ores-rcfilters-damaging-title}}&quot; and &quot;{{int:ores-rcfilters-goodfaith-title}}&quot;), 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 &quot;[http://breakingnews-beta.enterprise.wikimedia.com/ breaking news]&quot;. Currently in BETA, this attempts to identify likely &quot;newsworthy&quot; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2023/37|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2023-W37&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 21:08, 11 September 2023 (UTC)
&lt;!-- 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&amp;oldid=25589064 --&gt;

== Wikipedia translation of the week: 2023-38 ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:es:Genocidio del Putumayo]]'''&lt;br /&gt; &lt;small&gt;''([[:en:Putumayo genocide]]) ([[:ca:Genocidi del Putumayo]])''&lt;/small&gt;&lt;/div&gt;

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|]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=25599361 --&gt;

== Tech News: 2023-38 ==

&lt;section begin=&quot;technews-2023-W38&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2023/38|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2023-W38&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 19:20, 18 September 2023 (UTC)
&lt;!-- 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&amp;oldid=25623533 --&gt;

== Tech News: 2023-39 ==

&lt;section begin=&quot;technews-2023-W39&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;mediawiki.ui&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; 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 &quot;namespaces&quot; 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]]: &lt;code&gt;&lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;global_account_groups&lt;/bdi&gt;&lt;/code&gt; and &lt;code&gt;&lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;global_account_editcount&lt;/bdi&gt;&lt;/code&gt;. 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2023/39|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2023-W39&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 16:51, 26 September 2023 (UTC)
&lt;!-- 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&amp;oldid=25655264 --&gt;

== Tech News: 2023-40 ==

&lt;section begin=&quot;technews-2023-W40&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;{{int:tog-forcesafemode}}&quot;. 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 &quot;&lt;var&gt;contentModels&lt;/var&gt;&quot; option]]. The option takes a list of page content models, like &lt;code&gt;&lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;wikitext&lt;/bdi&gt;&lt;/code&gt; or &lt;code&gt;&lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;css&lt;/bdi&gt;&lt;/code&gt;. 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2023/40|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2023-W40&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 01:27, 3 October 2023 (UTC)
&lt;!-- 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&amp;oldid=25686930 --&gt;

== Tech News: 2023-41 ==

&lt;section begin=&quot;technews-2023-W41&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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:|&lt;code&gt;w:fon:&lt;/code&gt;]]) [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 &quot;[[mw:Special:MyLanguage/Help:Growth/Tools/Add a link|Add a link]]&quot; ({{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 &quot;Images recommendations&quot; [[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 &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;#page-actions&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; will be replaced with &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;#p-views&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt;. 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2023/41|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2023-W41&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 14:39, 9 October 2023 (UTC)
&lt;!-- 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&amp;oldid=25712895 --&gt;

== Wikipedia translation of the week: 2023-42 ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Athyma nefte]]'''&lt;br /&gt; &lt;/div&gt;

Please be bold and help translate this article!

----
[[File:VB 019 Color Sergeant UP.jpg|center|300px|]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''''Athyma nefte''''', the colour sergeant, is a species of brush-footed butterfly found in tropical South and Southeast Asia. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=25693965 --&gt;

== Tech News: 2023-42 ==

&lt;section begin=&quot;technews-2023-W42&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;Log in&quot; 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 &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;addPortletLink&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; and &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;#p-namespaces&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; that was deprecated one year ago will be removed. If you notice tools that should appear next to the &quot;Discussion&quot; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2023/42|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2023-W42&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 23:47, 16 October 2023 (UTC)
&lt;!-- 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&amp;oldid=25745824 --&gt;

== Wikipedia translation of the week: 2023-43 ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Typhoon Rusa]]'''&lt;br /&gt; &lt;/div&gt;

Please be bold and help translate this article!

----
[[File:Rusa 2002-08-27 0350Z.jpg|center|300px|]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=25693965 --&gt;

== Tech News: 2023-43 ==

&lt;section begin=&quot;technews-2023-W43&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2023/43|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2023-W43&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 23:17, 23 October 2023 (UTC)
&lt;!-- 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&amp;oldid=25782286 --&gt;

== Wikipedia translation of the week: 2023-44 ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Hein Eersel]]'''&lt;br /&gt; &lt;small&gt;''([[:nl:Hein Eersel]]) ([[:it:Hein Eersel]])''&lt;/small&gt; &lt;/div&gt;

Please be bold and help translate this article!

----
[[File:HeinEersel.jpg|center|300px|]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''Christiaan Hendrik &quot;Hein&quot; 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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=25797248 --&gt;

== Tech News: 2023-44 ==

&lt;section begin=&quot;technews-2023-W44&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2023/44|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2023-W44&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 23:21, 30 October 2023 (UTC)
&lt;!-- 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&amp;oldid=25801989 --&gt;

== Tech News: 2023-45 ==

&lt;section begin=&quot;technews-2023-W45&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2023/45|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2023-W45&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 21:06, 6 November 2023 (UTC)
&lt;!-- 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&amp;oldid=25838105 --&gt;

== Wikipedia translation of the week: 2023-45 ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Reclaim the Night]]'''&lt;br /&gt; &lt;small&gt;''([[:de:Reclaim the Night]])''&lt;/small&gt; &lt;/div&gt;

Please be bold and help translate this article!

----
[[File:Reclaim the Night 2014.jpg|center|300px|]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=25797248 --&gt;

== Wikipedia translation of the week: 2023-46 ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Ishe Komborera Africa]]'''&lt;br /&gt;  &lt;/div&gt;

Please be bold and help translate this article!

----
[[File:Ishe Komborera Africa.mp3|center|300px|]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
&quot;'''Ishe Komborera Africa'''&quot; (Shona for: God Bless Africa), also called &quot;Ishe Komborera Zimbabwe&quot; (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 &quot;Nkosi Sikelel' iAfrika&quot; into Zimbabwe's native Shona and Ndebele languages. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=25797248 --&gt;

== Tech News: 2023-46 ==

&lt;section begin=&quot;technews-2023-W46&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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:|&lt;code&gt;w:zgh:&lt;/code&gt;]]) [https://phabricator.wikimedia.org/T350216]
** a Wikipedia in [[d:Q35159|Dagaare]] ([[w:dga:|&lt;code&gt;w:dga:&lt;/code&gt;]]) [https://phabricator.wikimedia.org/T350218]
** a Wikipedia in [[d:Q33017|Toba Batak]] ([[w:bbc:|&lt;code&gt;w:bbc:&lt;/code&gt;]]) [https://phabricator.wikimedia.org/T350320]
** a Wikiquote in [[d:Q33151|Banjar]] ([[q:bjn:|&lt;code&gt;q:bjn:&lt;/code&gt;]]) [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 &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;meta.domain == &quot;canary&quot;&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt;. 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2023/46|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2023-W46&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 23:52, 13 November 2023 (UTC)
&lt;!-- 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&amp;oldid=25859263 --&gt;

== Wikipedia translation of the week: 2023-47 ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Bhagavata Mela]]'''&lt;br /&gt;  &lt;/div&gt;

Please be bold and help translate this article!

----

&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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 &quot;gathering, meeting of a group&quot; and connotes a folk festival. The traditional Bhagavata Mela performance acts out the legends of Hinduism, set to the Carnatic style music. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=25797248 --&gt;

== Tech News: 2023-47 ==

&lt;section begin=&quot;technews-2023-W47&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;[[mw:Special:MyLanguage/Help:Growth/Tools/Add a link|Add a link]]&quot; ({{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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2023/47|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2023-W47&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 00:55, 21 November 2023 (UTC)
&lt;!-- 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&amp;oldid=25884616 --&gt;

== Wikipedia translation of the week: 2023-48 ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:fr:Zanskari]]'''&lt;br /&gt; &lt;small&gt;''([[:en:Zaniskari]])''&lt;/small&gt; &lt;/div&gt;

Please be bold and help translate this article!

----
[[File:Zaniskari Horse in Ladakh, India.jpg|center|300px|]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=25797248 --&gt;

== Tech News: 2023-48 ==

&lt;section begin=&quot;technews-2023-W48&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;async&lt;/code&gt;/&lt;code&gt;await&lt;/code&gt;&lt;/bdi&gt; 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 &quot;[[mw:Special:MyLanguage/Help:Growth/Tools/Add_a_link|Add a link]]&quot; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2023/48|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2023-W48&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 23:09, 27 November 2023 (UTC)
&lt;!-- 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&amp;oldid=25906379 --&gt;

== Wikipedia translation of the week: 2023-49 ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Sheikh Hussein]]'''&lt;br /&gt; &lt;small&gt;''([[:fr:Sheikh Hussein]]) ([[:it:Scec Hussèn]])''&lt;/small&gt; &lt;/div&gt;

Please be bold and help translate this article!

----
[[File:Sheikh Hussein.jpg|center|300px|]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=25921616 --&gt;

== Tech News: 2023-49 ==

&lt;section begin=&quot;technews-2023-W49&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;{{int:Visualeditor-dialog-meta-categories-defaultsort-label}}&quot; feature in VisualEditor is working again. You no longer need to switch to source editing to edit &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;{{DEFAULTSORT:...}}&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; 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 &quot;{{int:Discussiontools-preference-visualenhancements}}&quot; will notice the [[mw:Special:MyLanguage/Talk pages project/Usability|talk page usability improvements]] appear on pages that include the &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;__NEWSECTIONLINK__&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; 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 &amp; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2023/49|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2023-W49&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 23:50, 4 December 2023 (UTC)
&lt;!-- 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&amp;oldid=25914435 --&gt;

== Wikipedia translation of the week: 2023-50 ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:fr:Applaudissements aux fenêtres pendant la pandémie de Covid-19]]'''&lt;br /&gt; &lt;small&gt;''([[:es:Aplauso por los trabajadores de la salud]]) ([[:gl:Aplauso ao persoal sanitario]])''&lt;/small&gt; &lt;/div&gt;

Please be bold and help translate this article!

----
[[File:Koronabirus konfinamendua Lasarten 2020-03-29.jpg|center|300px|]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=25925561 --&gt;

== Tech News: 2023-50 ==

&lt;section begin=&quot;technews-2023-W50&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;choosing own vs not own work&quot; 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 &quot;impact module&quot; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2023/50|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2023-W50&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 02:13, 12 December 2023 (UTC)
&lt;!-- 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&amp;oldid=25945501 --&gt;

== Wikipedia translation of the week: 2023-51 ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Jamaica Bay Wildlife Refuge]]'''&lt;br /&gt;  &lt;/div&gt;

Please be bold and help translate this article!

----
[[File:Aerial view of Subway Island, July 2019.JPG|center|300px|]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=25951007 --&gt;

== Tech News: 2023-51 ==

&lt;section begin=&quot;technews-2023-W51&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;Move Page&quot; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2023/51|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2023-W51&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 16:18, 18 December 2023 (UTC)
&lt;!-- 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&amp;oldid=25959059 --&gt;

== Wikipedia translation of the week: 2023-52 ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2023 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Plant blindness]]'''&lt;br /&gt; &lt;small&gt;''([[:fr:Cécité botanique]]) ([[:de:Pflanzenblindheit]])''&lt;/small&gt; &lt;/div&gt;

Please be bold and help translate this article!

----
[[File:Plant blindness 0323.png|center|300px|]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=25971304 --&gt;

== Wikipedia translation of the week: 2024-02 ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Pax airship disaster]]'''&lt;br /&gt; &lt;small&gt;''([[:pt:Catástrofe do dirigível Pax]])''&lt;/small&gt; &lt;/div&gt;

Please be bold and help translate this article!

----
[[File:Sim new-mcclures-magazine 1902-09 19 5 (page 75 crop).jpg|center|300px|]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''''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é.

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=26033876 --&gt;

== Tech News: 2024-02 ==

&lt;section begin=&quot;technews-2024-W02&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2024/02|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2024-W02&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 01:20, 9 January 2024 (UTC)
&lt;!-- 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&amp;oldid=26026251 --&gt;

== Wikipedia translation of the week: 2024-03 ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Conversion to Islam]]'''&lt;br /&gt; &lt;small&gt;''([[:fr:Conversion à l'islam]])''&lt;/small&gt; &lt;/div&gt;

Please be bold and help translate this article!

----
[[File:Sahadah-Topkapi-Palace.jpg|center|300px|]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''Conversion to Islam''' is accepting Islam as a religion or faith and rejecting any other religion or irreligion. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=26044632 --&gt;

== Tech News: 2024-03 ==

&lt;section begin=&quot;technews-2024-W03&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;ES2015&quot;) and ES7 (&quot;ES2016&quot;). 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 &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;requiresES6&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; 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 &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;jquery.cookie&lt;/code&gt;&lt;/bdi&gt; module was deprecated and replaced with the &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;mediawiki.cookie&lt;/code&gt;&lt;/bdi&gt; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2024/03|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2024-W03&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 00:13, 16 January 2024 (UTC)
&lt;!-- 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&amp;oldid=26074460 --&gt;

== Wikipedia translation of the week: 2024-04 ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Kinder der Landstrasse]]'''&lt;br /&gt;  &lt;/div&gt;

Please be bold and help translate this article!

----
[[File:Kinderdlandstrasse plakat.jpg|center|300px|]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=26044632 --&gt;

== Tech News: 2024-04 ==

&lt;section begin=&quot;technews-2024-W04&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2024/04|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2024-W04&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 01:04, 23 January 2024 (UTC)
&lt;!-- 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&amp;oldid=26096197 --&gt;

== Wikipedia translation of the week: 2024-05 ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Qurm Nature Reserve]]'''&lt;br /&gt;  &lt;/div&gt;

Please be bold and help translate this article!

----
[[File:Al-Qurm Wetlands.jpg|center|300px|]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=26149847 --&gt;

== Tech News: 2024-05 ==

&lt;section begin=&quot;technews-2024-W05&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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]].&lt;!-- The Diff post will be published on Monday morning UTC--&gt; [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 &quot;Tools&quot; 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 &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;targets&lt;/code&gt;&lt;/bdi&gt; option to limit where you can use them. This will stop working this week. You should use the &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;skins&lt;/code&gt;&lt;/bdi&gt; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2024/05|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2024-W05&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 19:31, 29 January 2024 (UTC)
&lt;!-- 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&amp;oldid=26137870 --&gt;

== Wikipedia translation of the week: 2024-06 ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Timurid architecture]]'''&lt;br /&gt;  &lt;/div&gt;

Please be bold and help translate this article!

----
[[File:Gur-e-Amir Mausolueum - Samarkand - Uzbekistan (7488414078).jpg|center|300px|]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=26169542 --&gt;

== Tech News: 2024-06 ==

&lt;section begin=&quot;technews-2024-W06&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;action blocks&quot;]]. [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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2024/06|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2024-W06&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 19:22, 5 February 2024 (UTC)
&lt;!-- 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&amp;oldid=26180971 --&gt;

== Wikipedia translation of the week: 2024-07 ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Adoration of the Magi (Fra Angelico and Filippo Lippi)]]'''&lt;br /&gt;  &lt;/div&gt;

Please be bold and help translate this article!

----
[[File:Fra Angelico, Fra Filippo Lippi, The Adoration of the Magi.jpg|center|300px|]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=26187446 --&gt;

== Tech News: 2024-07 ==

&lt;section begin=&quot;technews-2024-W07&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2024/07|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2024-W07&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 05:49, 13 February 2024 (UTC)
&lt;!-- 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&amp;oldid=26223994 --&gt;

== Wikipedia translation of the week: 2024-08 ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:nl:Graf met de handjes]]'''&lt;br /&gt;  &lt;/div&gt;

Please be bold and help translate this article!

----
[[File:Weg langs het kerkhof tegenover 1, Roermond.jpg|center|300px|]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
The monument '''Van Gorkum-Van Aefferden''', more well known as the &quot;'''grave with the little hands'''&quot; is a monumental Tombstone in the Dutch city of Roermond.

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=26260848 --&gt;

== Tech News: 2024-08 ==

&lt;section begin=&quot;technews-2024-W08&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;{{int:Tog-enotifwatchlistpages}}&quot; 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 &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;[https://developer.mozilla.org/en-US/docs/Web/CSS/filter filter]&lt;/code&gt;&lt;/bdi&gt; property can now be used in HTML &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;style&lt;/code&gt;&lt;/bdi&gt; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2024/08|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2024-W08&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 15:37, 19 February 2024 (UTC)
&lt;!-- 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&amp;oldid=26254282 --&gt;

== Wikipedia translation of the week: 2024-09 ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Doorway effect]]'''&lt;br /&gt;  &lt;/div&gt;

Please be bold and help translate this article!

----

&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=26260848 --&gt;

== Tech News: 2024-09 ==

&lt;section begin=&quot;technews-2024-W09&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &lt;code&gt;wgGlobalGroups&lt;/code&gt; 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: &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;if (/globalgroupname/.test(mw.config.get(&quot;wgGlobalGroups&quot;)))&lt;/code&gt;&lt;/bdi&gt;. [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]] (&lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;changetags&lt;/code&gt;&lt;/bdi&gt;) 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2024/09|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2024-W09&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 19:23, 26 February 2024 (UTC)
&lt;!-- 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&amp;oldid=26294125 --&gt;

== Wikipedia translation of the week: 2024-10 ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Sissieretta Jones]]'''&lt;br /&gt;  &lt;/div&gt;

Please be bold and help translate this article!

----
[[File:1899 poster of Mme. M. Sissieretta Jones.jpg|center|300px]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''Matilda Sissieretta Joyner Jones''' (January 5, 1868, or 1869 – June 24, 1933) was an American soprano. She sometimes was called &quot;The Black Patti&quot; in reference to Italian opera singer Adelina Patti. Jones' repertoire included grand opera, light opera, and popular music 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=26313143 --&gt;

== Tech News: 2024-10 ==

&lt;section begin=&quot;technews-2024-W10&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;Special:Book&lt;/code&gt;&lt;/bdi&gt; page (as well as the associated &quot;Create a book&quot; 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 &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;Gadget&lt;/code&gt;&lt;/bdi&gt; and &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;Gadget_definition&lt;/code&gt;&lt;/bdi&gt; namespaces and &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;gadgets-definition-edit&lt;/code&gt;&lt;/bdi&gt; 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 &quot;Add a citation&quot; 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 &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;?useparsoid=1&lt;/code&gt;&lt;/bdi&gt; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2024/10|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2024-W10&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 19:47, 4 March 2024 (UTC)
&lt;!-- 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&amp;oldid=26329807 --&gt;

== Wikipedia translation of the week: 2024-11 ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Preventative Coup of November 11]]'''&lt;br /&gt; &lt;small&gt;''([[:es:Golpe de Estado en Brasil de 1955]])''&lt;/small&gt; &lt;/div&gt;

Please be bold and help translate this article!

----
[[File:Exército na casa de Café Filho.jpg|center|300px]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
The '''Preventative Coup of November 11''' sometimes called the '''1955 Brazilian coup d'état''' or referred to as an &quot;anti-coup&quot; or a &quot;counter-coup&quot; (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.

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=26366849 --&gt;

== Tech News: 2024-11 ==

&lt;section begin=&quot;technews-2024-W11&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2024/11|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2024-W11&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 23:04, 11 March 2024 (UTC)
&lt;!-- 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&amp;oldid=26374013 --&gt;

== Wikipedia translation of the week: 2024-12 ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Hojang Taret]]'''&lt;br /&gt; &lt;/div&gt;

Please be bold and help translate this article!

----

&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=26366849 --&gt;

== Tech News: 2024-12 ==

&lt;section begin=&quot;technews-2024-W12&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;Language links are at the top of the page&quot; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2024/12|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2024-W12&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 17:40, 18 March 2024 (UTC)
&lt;!-- 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&amp;oldid=26410165 --&gt;

== Wikipedia translation of the week: 2024-13 ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Magna Lykseth-Skogman]]'''&lt;br /&gt; &lt;/div&gt;

Please be bold and help translate this article!

----
[[File:Magna Lykseth in Tristan och Isolde at Kungliga Operan 1909 - SMV - GL164.jpg|center|300px|]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=26447450 --&gt;

== Tech News: 2024-13 ==

&lt;section begin=&quot;technews-2024-W13&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2024/13|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2024-W13&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 18:57, 25 March 2024 (UTC)
&lt;!-- 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&amp;oldid=26446209 --&gt;

== Wikipedia translation of the week: 2024-14 ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Lidder Valley]]'''&lt;br /&gt; &lt;/div&gt;

Please be bold and help translate this article!

----
[[File:Pahalgam Valley.jpg|center|300px|]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=26509189 --&gt;

== Tech News: 2024-14 ==

&lt;section begin=&quot;technews-2024-W14&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &amp; 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 &amp; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2024/14|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2024-W14&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 03:36, 2 April 2024 (UTC)
&lt;!-- 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&amp;oldid=26462933 --&gt;

== Wikipedia translation of the week: 2024-15 ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Operation Kraai]]'''&lt;br /&gt; &lt;/div&gt;

Please be bold and help translate this article!

----
[[File:Overzicht van het vliegveld te Djokja vanuit de 'Control Tower', Bestanddeelnr 5128.jpg|center|300px|]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=26550154 --&gt;

== Tech News: 2024-15 ==

&lt;section begin=&quot;technews-2024-W15&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2024/15|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2024-W15&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 23:38, 8 April 2024 (UTC)
&lt;!-- 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&amp;oldid=26564838 --&gt;

== Wikipedia translation of the week: 2024-16 ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:ru:Павильон Росси]]'''&lt;br /&gt; &lt;small&gt;''([[:en:Rossi Pavilion]])&amp;#32;([[:fr:Pavillon Rossi]])''&lt;/small&gt; &lt;/div&gt;

Please be bold and help translate this article!

----
[[File:Rossi's Pavilion in Mikhailovsky Garden. Saint-Petersburg. 1825..jpg|center|300px|]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=26565118 --&gt;

== Tech News: 2024-16 ==

&lt;section begin=&quot;technews-2024-W16&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;{{Int:tag-mw-reverted}}&quot; 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 &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;page_last_edit_age&lt;/code&gt;&lt;/bdi&gt; 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 &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;abuse_filter&lt;/code&gt;&lt;/bdi&gt; and &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;abuse_filter_history&lt;/code&gt;&lt;/bdi&gt; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2024/16|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2024-W16&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 23:29, 15 April 2024 (UTC)
&lt;!-- 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&amp;oldid=26564838 --&gt;

== Wikipedia translation of the week: 2024-17 ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Devorà Ascarelli]]'''&lt;br /&gt; &lt;small&gt;''([[:it:Debora Ascarelli]])&amp;#32;([[:es:Devorà Ascarelli]])''&lt;/small&gt; &lt;/div&gt;

Please be bold and help translate this article!

----

&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=26624302 --&gt;

== Tech News: 2024-17 ==

&lt;section begin=&quot;technews-2024-W17&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2024/17|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2024-W17&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 20:28, 22 April 2024 (UTC)
&lt;!-- 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&amp;oldid=26647188 --&gt;

== Wikipedia translation of the week: 2024-18 ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:1989 Serbian general election]]'''&lt;br /&gt; &lt;small&gt;''([[:sr:Председнички избори у Србији 1989.]])&amp;#32;([[:vi:Tổng tuyển cử Serbia 1989]])''&lt;/small&gt;&lt;/div&gt;

Please be bold and help translate this article!

----
[[File:Parliament of SR Serbia (1989–1991).svg|center|300px|]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=26624302 --&gt;

== Tech News: 2024-18 ==

&lt;section begin=&quot;technews-2024-W18&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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]] (&quot;{{int:discussiontools-preference-visualenhancements}}&quot;). 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:|&lt;code&gt;w:bew:&lt;/code&gt;]]) [https://phabricator.wikimedia.org/T357866]
** a {{int:project-localized-name-group-wikipedia}} in [[d:Q35708|Kusaal]] ([[w:kus:|&lt;code&gt;w:kus:&lt;/code&gt;]]) [https://phabricator.wikimedia.org/T359757]
** a {{int:project-localized-name-group-wikipedia}} in [[d:Q35513|Igala]] ([[w:igl:|&lt;code&gt;w:igl:&lt;/code&gt;]]) [https://phabricator.wikimedia.org/T361644]
** a {{int:project-localized-name-group-wiktionary}} in [[d:Q33541|Karakalpak]] ([[wikt:kaa:|&lt;code&gt;wikt:kaa:&lt;/code&gt;]]) [https://phabricator.wikimedia.org/T362135]
** a {{int:project-localized-name-group-wikisource}} in [[d:Q9228|Burmese]] ([[s:my:|&lt;code&gt;s:my:&lt;/code&gt;]]) [https://phabricator.wikimedia.org/T361085]
** a {{int:project-localized-name-group-wikisource}} in [[d:Q9237|Malay]] ([[s:ms:|&lt;code&gt;s:ms:&lt;/code&gt;]]) [https://phabricator.wikimedia.org/T363039]
** a {{int:project-localized-name-group-wikisource}} in [[d:Q8108|Georgian]] ([[s:ka:|&lt;code&gt;s:ka:&lt;/code&gt;]]) [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 &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;mapstyle=&quot;osm&quot;&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt;. 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2024/18|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2024-W18&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 03:34, 30 April 2024 (UTC)
&lt;!-- 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&amp;oldid=26689057 --&gt;

== Wikipedia translation of the week: 2024-19 ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:#DDDDDD; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Heinrich Bünting]]'''&lt;br /&gt; &lt;/div&gt;

Please be bold and help translate this article!

----

&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=26624302 --&gt;

== Tech News: 2024-19 ==

&lt;section begin=&quot;technews-2024-W19&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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]] (&quot;{{int:discussiontools-preference-visualenhancements}}&quot;). 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 &lt;code&gt;SiteAdminHelper&lt;/code&gt;. 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 &quot;All public logs&quot;, but it only shows some logs. This label will now say &quot;Main public logs&quot;. [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 &quot;[[mw:Special:MyLanguage/Help:Growth/Tools/Add a link|Add a link]]&quot;. 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2024/19|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2024-W19&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 16:45, 6 May 2024 (UTC)
&lt;!-- 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&amp;oldid=26729363 --&gt;

== Wikipedia translation of the week: 2024-20 ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background:var(--background-color-backdrop-dark, #DDDDDD); border:1px solid #BBBBBB; color:var(--color-inverted, #000000); padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Ruyan (district)]]'''&lt;br /&gt; &lt;small&gt;''([[:fa:رویان (طبرستان)]])''&lt;/small&gt; &lt;/div&gt;

Please be bold and help translate this article!

----
[[File:Northern Iran and its surroundings during the Iranian intermezzo.svg|300px|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=26755244 --&gt;

== Tech News: 2024-20 ==

&lt;section begin=&quot;technews-2024-W20&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;__EXPECTWITHOUTSCANS__&lt;/code&gt;&lt;/bdi&gt; 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]] &quot;{{int:tog-uselivepreview}}&quot;, then the template-page feature &quot;{{int:Templatesandbox-editform-legend}}&quot; 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 &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;alt=&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; attribute. This is identical in usage to the &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;alt=&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; 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 &quot;[[mw:Special:MyLanguage/Edit Review Improvements/New filters for edit review|New Filters for Edit Review]]&quot; 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 &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;[[mw:Special:MyLanguage/Manual:pagelinks table|pagelinks]]&lt;/code&gt;&lt;/bdi&gt; database table (&lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;pl_namespace&lt;/code&gt;&lt;/bdi&gt; and &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;pl_title&lt;/code&gt;&lt;/bdi&gt;) are being dropped soon. Users must use two columns of the new &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;[[mw:special:MyLanguage/Manual:linktarget table|linktarget]]&lt;/code&gt;&lt;/bdi&gt; table instead (&lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;lt_namespace&lt;/code&gt;&lt;/bdi&gt; and &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;lt_title&lt;/code&gt;&lt;/bdi&gt;). In your existing SQL queries:
*# Replace &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;JOIN pagelinks&lt;/code&gt;&lt;/bdi&gt; with &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;JOIN linktarget&lt;/code&gt;&lt;/bdi&gt; and &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;pl_&lt;/code&gt;&lt;/bdi&gt; with &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;lt_&lt;/code&gt;&lt;/bdi&gt; in the &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;ON&lt;/code&gt;&lt;/bdi&gt; statement
*# Below that add &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;JOIN pagelinks ON lt_id = pl_target_id&lt;/code&gt;&lt;/bdi&gt;
** See &lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[phab:T222224]]&lt;/bdi&gt; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2024/20|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2024-W20&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 23:59, 13 May 2024 (UTC)
&lt;!-- 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&amp;oldid=26762074 --&gt;

== Wikipedia translation of the week: 2024-21 ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: #f8f9fa; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Turlough (lake)]]'''&lt;br /&gt; &lt;small&gt;''([[:de:Turlough]])&amp;#32;([[:no:Turlough]])''&lt;/small&gt; &lt;/div&gt;

Please be bold and help translate this article!

----
[[File:Carran Turlough.jpg|300px|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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.  

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=26789673 --&gt;

== Tech News: 2024-21 ==

&lt;section begin=&quot;technews-2024-W21&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2024/21|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2024-W21&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 23:04, 20 May 2024 (UTC)
&lt;!-- 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&amp;oldid=26786311 --&gt;

== Wikipedia translation of the week: 2024-22 ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: #f8f9fa; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Geiranger Church]]'''&lt;br /&gt; &lt;small&gt;''([[:no:Geiranger kirke]])''&lt;/small&gt; &lt;/div&gt;

Please be bold and help translate this article!

----
[[File:Iglesia parroquial, Geiranger, Noruega, 2019-09-07, DD 84-97 PAN.jpg|300px|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=26828106 --&gt;

== Tech News: 2024-22 ==

&lt;section begin=&quot;technews-2024-W22&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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: &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;.collapsible&lt;/code&gt;&lt;/bdi&gt;{{int:comma-separator/en}}&lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;.multicol&lt;/code&gt;&lt;/bdi&gt;{{int:comma-separator/en}}&lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;.reflist&lt;/code&gt;&lt;/bdi&gt;{{int:comma-separator/en}}&lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;.coordinates&lt;/code&gt;&lt;/bdi&gt;{{int:comma-separator/en}}&lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;.topicon&lt;/code&gt;&lt;/bdi&gt;. [[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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2024/22|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2024-W22&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 00:15, 28 May 2024 (UTC)
&lt;!-- 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&amp;oldid=26832205 --&gt;

== Wikipedia translation of the week: 2024-23 ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: #f8f9fa; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Guillermo Larrazábal]]'''&lt;br /&gt;  &lt;/div&gt;

Please be bold and help translate this article!

----

&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=26828106 --&gt;

== Tech News: 2024-23 ==

&lt;section begin=&quot;technews-2024-W23&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;&lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;MediaWiki:Wikhiero-usage-tracking-category&lt;/code&gt;&lt;/bdi&gt;&quot; to &quot;&lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;MediaWiki:Wikihiero-usage-tracking-category&lt;/code&gt;&lt;/bdi&gt;&quot;. [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:|&lt;code&gt;w:dtp:&lt;/code&gt;]]) [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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2024/23|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2024-W23&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 22:35, 3 June 2024 (UTC)
&lt;!-- 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&amp;oldid=26844397 --&gt;

== Tech News: 2024-24 ==

&lt;section begin=&quot;technews-2024-W24&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;mw-reference-text&lt;/code&gt;&lt;/bdi&gt; class, Parsoid now also adds the &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;reference-text&lt;/code&gt;&lt;/bdi&gt; 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 &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;&lt;span class=&quot;mw-cite-backlink&quot;&gt;&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; 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 &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;&lt;translate&gt;&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2024/24|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2024-W24&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 20:20, 10 June 2024 (UTC)
&lt;!-- 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&amp;oldid=26893898 --&gt;

== Wikipedia translation of the week: 2024-25 ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: #f8f9fa; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:de:Magdalena Zeger]]'''&lt;br /&gt;  &lt;/div&gt;

Please be bold and help translate this article!

----

&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=26940351 --&gt;

== Tech News: 2024-25 ==

&lt;section begin=&quot;technews-2024-W25&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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]&lt;!-- NOTE: THE DIFF BLOG WILL BE PUBLISHED ON MONDAY --&gt;
* [[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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2024/25|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2024-W25&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 23:49, 17 June 2024 (UTC)
&lt;!-- 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&amp;oldid=26911987 --&gt;

== Wikipedia translation of the week: 2024-26 ==

{| class=&quot;plainlinks mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: #f8f9fa; border:1px solid #BBBBBB; color:#000000; padding .4em;&quot;
|-
|style=&quot;text-align:center;&quot;| The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Koreans in Micronesia]]'''&lt;br /&gt; &lt;small&gt;''([[:zh:朝鮮裔密克羅尼西亞人]])''&lt;/small&gt; &lt;/div&gt;

Please be bold and help translate this article!

----

&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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 &amp; 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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
|}
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=26940351 --&gt;

== Tech News: 2024-26 ==

&lt;section begin=&quot;technews-2024-W26&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2024/26|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2024-W26&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 22:33, 24 June 2024 (UTC)
&lt;!-- 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&amp;oldid=26989424 --&gt;

== Wikipedia translation of the week: 2024-27 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Roller printing on textiles]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Silverstudio.jpg|center|300px]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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 &quot;machine grounds&quot;. 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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
&lt;/div&gt;
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=27031540 --&gt;

== Tech News: 2024-27 ==

&lt;section begin=&quot;technews-2024-W27&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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:|&lt;code&gt;w:btm:&lt;/code&gt;]]) [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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2024/27|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2024-W27&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 23:59, 1 July 2024 (UTC)
&lt;!-- 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&amp;oldid=27038456 --&gt;

== Wikipedia translation of the week: 2024-28 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:simple:India naming dispute]]'''&lt;br /&gt; &lt;small&gt;''([[:ur:انڈیا نام کا تنازعہ]])''&lt;/small&gt; &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----

&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
&lt;/div&gt;
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=27031540 --&gt;

== Tech News: 2024-28 ==

&lt;section begin=&quot;technews-2024-W28&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2024/28|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2024-W28&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 21:32, 8 July 2024 (UTC)
&lt;!-- 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&amp;oldid=27080357 --&gt;

== Wikipedia translation of the week: 2024-29 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Adumu]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Maasai 2012 05 31 2782 (7522645058).jpg|center|300px|]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
&lt;/div&gt;
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=27031540 --&gt;

== Tech News: 2024-29 ==

&lt;section begin=&quot;technews-2024-W29&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2024/29|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;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]].
&lt;/div&gt;&lt;section end=&quot;technews-2024-W29&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 01:31, 16 July 2024 (UTC)
&lt;!-- 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&amp;oldid=27124561 --&gt;

== Wikipedia translation of the week: 2024-30 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Rathaus-Glockenspiel]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:2019-11-16, Glockenspiel, Neues Münchner Rathaus, IMG 7463 edit Christoph Braun.jpg|center|300px|]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
&lt;/div&gt;
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=27031540 --&gt;

== Tech News: 2024-30 ==

&lt;section begin=&quot;technews-2024-W30&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;Pending Changes&quot;) 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2024/30|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;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]].
&lt;/div&gt;&lt;section end=&quot;technews-2024-W30&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 00:05, 23 July 2024 (UTC)
&lt;!-- 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&amp;oldid=27142915 --&gt;

== Wikipedia translation of the week: 2024-31 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Nederlandsche Cocaïnefabriek]]'''&lt;br /&gt; &lt;small&gt;''([[:es:Nederlandsche Cocaïnefabriek]])&amp;#32;([[:nl:Nederlandsche Cocaïnefabriek]])''&lt;/small&gt; &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Nederlandsche Cocainefabriek Schinkelstraat Amsterdam architect HH Baanders 1902.jpg|center|300px|]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
&lt;/div&gt;
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=27150339 --&gt;

== Tech News: 2024-31 ==

&lt;section begin=&quot;technews-2024-W31&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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:|&lt;code&gt;voy:cs:&lt;/code&gt;]]) [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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2024/31|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2024-W31&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 23:11, 29 July 2024 (UTC)
&lt;!-- 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&amp;oldid=27164109 --&gt;

== Wikipedia translation of the week: 2024-32 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Suffrage drama]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Pamphlet from NAWSA for women's suffrage plays, page 1.jpg|center|300px|]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
&lt;/div&gt;
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=27150339 --&gt;

== Tech News: 2024-32 ==

&lt;section begin=&quot;technews-2024-W32&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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: &lt;code&gt;&lt;nowiki&gt;{{&lt;/nowiki&gt;[[mw:Special:MyLanguage/Help:Magic_words#dir|#dir]]&lt;nowiki&gt;}}&lt;/nowiki&gt;&lt;/code&gt; and &lt;code&gt;&lt;nowiki&gt;{{&lt;/nowiki&gt;[[mw:Special:MyLanguage/Help:Magic_words#bcp47|#bcp47]]&lt;nowiki&gt;}}&lt;/nowiki&gt;&lt;/code&gt;. These will reduce the need for &lt;code&gt;Template:Dir&lt;/code&gt; and &lt;code&gt;Template:BCP47&lt;/code&gt; on Commons and allow us to [[phab:T343131|drop 100 million rows]] from the &quot;what links here&quot; 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 &quot;Pages using Timeline&quot; has been renamed to &quot;Pages using the EasyTimeline extension&quot; [https://translatewiki.net/wiki/Special:Translations?message=MediaWiki%3ATimeline-tracking-category&amp;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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2024/32|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2024-W32&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 20:44, 5 August 2024 (UTC)
&lt;!-- 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&amp;oldid=27233905 --&gt;

== Wikipedia translation of the week: 2024-33 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Karatgurk]]'''&lt;br /&gt; &lt;small&gt;''([[:it:Karatgurk]])''&lt;/small&gt; &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----

&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the 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)''
&lt;/div&gt;
&lt;/div&gt;
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=27264174 --&gt;

== Tech News: 2024-33 ==

&lt;section begin=&quot;technews-2024-W33&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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:|&lt;code&gt;w:bdr:&lt;/code&gt;]]) [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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2024/33|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2024-W33&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 23:22, 12 August 2024 (UTC)
&lt;!-- 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&amp;oldid=27253654 --&gt;

== Wikipedia translation of the week: 2024-34 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:B1 (classification)]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----

&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=27278917 --&gt;

== Tech News: 2024-34 ==

&lt;section begin=&quot;technews-2024-W34&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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&amp;namespace=8 DynamicPageList], [https://translatewiki.net/wiki/Special:Translations?message=MediaWiki%3Akartographer-tracking-category&amp;namespace=8 Kartographer], [https://translatewiki.net/wiki/Special:Translations?message=MediaWiki%3Aphonos-tracking-category&amp;namespace=8 Phonos], [https://translatewiki.net/wiki/Special:Translations?message=MediaWiki%3Arss-tracking-category&amp;namespace=8 RSS], [https://translatewiki.net/wiki/Special:Translations?message=MediaWiki%3Ascore-use-category&amp;namespace=8 Score], [https://translatewiki.net/wiki/Special:Translations?message=MediaWiki%3Awikihiero-usage-tracking-category&amp;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 &lt;code&gt;&lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;categories&lt;/bdi&gt;&lt;/code&gt; property of &lt;code&gt;&lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;[[mediawikiwiki:Special:MyLanguage/Extension:Scribunto/Lua reference manual#Title objects|mw.title objects]]&lt;/bdi&gt;&lt;/code&gt;. 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 &lt;code&gt;Talk:WP:&lt;/code&gt; so that their titles start with &lt;code&gt;Wikipedia talk:&lt;/code&gt;), but it may have failed for some pages, and moved them to &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;[[Special:PrefixIndex/T195546/]]&lt;/bdi&gt; 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 &amp; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2024/34|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2024-W34&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 00:54, 20 August 2024 (UTC)
&lt;!-- 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&amp;oldid=27307284 --&gt;

== Wikipedia translation of the week: 2024-35 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Erzi (village)]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Caucasus, Ingushetia, Ингушские боевые и смотровые башни, горы Кавказа.jpg|300px|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=27345183 --&gt;

== Tech News: 2024-35 ==

&lt;section begin=&quot;technews-2024-W35&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;Pending Changes&quot;) 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2024/35|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2024-W35&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 20:34, 26 August 2024 (UTC)
&lt;!-- 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&amp;oldid=27341211 --&gt;

== Tech News: 2024-36 ==

&lt;section begin=&quot;technews-2024-W36&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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|&lt;code dir=&quot;ltr&quot;&gt;&lt;nowiki&gt;__EXPECTUNUSEDTEMPLATE__&lt;/nowiki&gt;&lt;/code&gt;]] 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2024/36|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2024-W36&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 01:08, 3 September 2024 (UTC)
&lt;!-- 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&amp;oldid=27390268 --&gt;

== Wikipedia translation of the week: 2024-37 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Cappadocian calendar]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----

&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=27357319 --&gt;

== Tech News: 2024-37 ==

&lt;section begin=&quot;technews-2024-W37&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;entity:getSitelink()&lt;/code&gt;&lt;/bdi&gt; and &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;mw.wikibase.getSitelink(qid)&lt;/code&gt;&lt;/bdi&gt; 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 &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;MOS&lt;/code&gt;&lt;/bdi&gt; namespace added to their Wikipedias. This improvement ensures that links beginning with &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;MOS:&lt;/code&gt;&lt;/bdi&gt; (usually shortcuts to the [[w:en:Wikipedia:Manual of Style|Manual of Style]]) are not broken by [[w:en:Mooré|Mooré]] Wikipedia (language code &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;mos&lt;/code&gt;&lt;/bdi&gt;). [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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2024/37|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2024-W37&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 18:53, 9 September 2024 (UTC)
&lt;!-- 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&amp;oldid=27424457 --&gt;

== Tech News: 2024-38 ==

&lt;section begin=&quot;technews-2024-W38&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;Edit Check (references) activated&quot; 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 &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;mw-message-box&lt;/code&gt;&lt;/bdi&gt; 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&amp;regex=1&amp;namespaces=&amp;title= global-search] to determine what needs to be changed. It is possible to use the newer &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;cdx-message&lt;/code&gt;&lt;/bdi&gt; 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&amp;diff=prev&amp;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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2024/38|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2024-W38&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 00:03, 17 September 2024 (UTC)
&lt;!-- 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&amp;oldid=27460876 --&gt;

== Wikipedia translation of the week: 2024-39 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Independence Day (Albania)]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----

&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=27456350 --&gt;

== Tech News: 2024-39 ==

&lt;section begin=&quot;technews-2024-W39&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;[[mw:Special:MyLanguage/Wikimedia Apps/iOS Suggested edits project#Hypothesis 2 Add an Image Suggested Edit|Add an image]]&quot;. 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 &lt;code&gt;&lt;nowiki&gt;&lt;syntaxhighlight&gt;&lt;/nowiki&gt;&lt;/code&gt; tags and on code pages (JavaScript, CSS, Scribunto and Sanitized CSS). Uses of template syntax &lt;code&gt;&lt;nowiki&gt;{{…}}&lt;/nowiki&gt;&lt;/code&gt; 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 &quot;[https://query-scholarly.wikidata.org scholarly]&quot; and &quot;[https://query-main.wikidata.org main]&quot; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2024/39|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2024-W39&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 23:37, 23 September 2024 (UTC)
&lt;!-- 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&amp;oldid=27493779 --&gt;

== Wikipedia translation of the week: 2024-40 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Wildlife of Bahrain]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Birds in Al-Areen Wildlife Park.jpg|300px|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=27456350 --&gt;

== Tech News: 2024-40 ==

&lt;section begin=&quot;technews-2024-W40&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &lt;code dir=ltr&gt;?veaction=editsource&lt;/code&gt; 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 &quot;donate&quot; link has been moved from a collapsible menu next to the content area into a more prominent top menu, next to &quot;Create an account&quot;. 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2024/40|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2024-W40&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 22:21, 30 September 2024 (UTC)
&lt;!-- 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&amp;oldid=27530062 --&gt;

== Tech News: 2024-41 ==

&lt;section begin=&quot;technews-2024-W41&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;Revert Risk&quot; 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&amp;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 &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;&lt;syntaxhighlight&gt;&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; code blocks to offer readers a &quot;Copy&quot; button if the &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;copy=1&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; 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:|&lt;code&gt;w:kge:&lt;/code&gt;]]) [https://phabricator.wikimedia.org/T374813]
** a {{int:project-localized-name-group-wikipedia}} in [[d:Q36096|Mooré]] ([[m:mos:|&lt;code&gt;m:mos:&lt;/code&gt;]]) [https://phabricator.wikimedia.org/T374641]
** a {{int:project-localized-name-group-wiktionary}} in [[d:Q36213|Madurese]] ([[wikt:mad:|&lt;code&gt;wikt:mad:&lt;/code&gt;]]) [https://phabricator.wikimedia.org/T374968]
** a {{int:project-localized-name-group-wikiquote}} in [[d:Q2501174|Gorontalo]] ([[q:gor:|&lt;code&gt;q:gor:&lt;/code&gt;]]) [https://phabricator.wikimedia.org/T375088]
** a {{int:project-localized-name-group-wikinews}} in [[d:Q56482|Shan]] ([[n:shn:|&lt;code&gt;n:shn:&lt;/code&gt;]]) [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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2024/41|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2024-W41&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 23:43, 7 October 2024 (UTC)
&lt;!-- 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&amp;oldid=27557422 --&gt;

== Wikipedia translation of the week: 2024-42 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Little Danes experiment]]'''&lt;br /&gt; &lt;small&gt;''([[:fa:آزمایش دانمارکی‌های کوچک]])''&lt;/small&gt; &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Children play at a Danish Red Cross-run orphanage in Greenland.jpg|300px|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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 &quot;little Danes&quot;. 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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=27572997 --&gt;

== Tech News: 2024-42 ==

&lt;section begin=&quot;technews-2024-W42&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;''hastemplate''&lt;/bdi&gt; and &lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;''incategory''&lt;/bdi&gt; 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 &quot;search engine&quot; 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 &lt;code&gt;&lt;nowiki&gt;&lt;bdi&gt;&lt;/nowiki&gt;&lt;/code&gt; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2024/42|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2024-W42&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 21:22, 14 October 2024 (UTC)
&lt;!-- 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&amp;oldid=27597254 --&gt;

== Wikipedia translation of the week: 2024-43 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Kharayeb]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Muharram 1Oth-Ashouraa 2007 in Kharayeb - panoramio.jpg|300px|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=27572997 --&gt;

== Tech News: 2024-43 ==

&lt;section begin=&quot;technews-2024-W43&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;Donate&quot; 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 &lt;code dir=&quot;ltr&quot;&gt;{{[[mw:Special:MyLanguage/Help:Extension:ParserFunctions##timef|#timef]]:…}}&lt;/code&gt; parser function. For example, &lt;code dir=&quot;ltr&quot;&gt;&lt;nowiki&gt;{{#timef:now|date|en}}&lt;/nowiki&gt;&lt;/code&gt; will show as &quot;&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;{{#timef:now|date|en}}&lt;/bdi&gt;&quot;. Previously, &lt;code dir=&quot;ltr&quot;&gt;&lt;nowiki&gt;{{#time:…}}&lt;/nowiki&gt;&lt;/code&gt; could be used to format dates, but this required knowledge of the order of the time and date components and their intervening punctuation. &lt;code dir=&quot;ltr&quot;&gt;#timef&lt;/code&gt; (or &lt;code dir=&quot;ltr&quot;&gt;#timefl&lt;/code&gt; 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 &lt;code dir=&quot;ltr&quot;&gt;&lt;nowiki&gt;{{USERLANGUAGE}}&lt;/nowiki&gt;&lt;/code&gt; instead of using &lt;code dir=&quot;ltr&quot;&gt;&lt;nowiki&gt;{{int:lang}}&lt;/nowiki&gt;&lt;/code&gt;. [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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2024/43|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2024-W43&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 20:53, 21 October 2024 (UTC)
&lt;!-- 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&amp;oldid=27634672 --&gt;

== Wikipedia translation of the week: 2024-44 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Christmas horror]]'''&lt;br /&gt; &lt;small&gt;''([[:es:Terror navideño]])''&lt;/small&gt; &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Christmascarol1843 -- 169.jpg|300px|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''Christmas horror''' is a fiction genre and film genre that incorporates horror elements into a seasonal setting. It is popular in multiple countries.  

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=27647428 --&gt;

== Tech News: 2024-44 ==

&lt;section begin=&quot;technews-2024-W44&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &lt;code&gt;emitTransitionOnStep&lt;/code&gt; to &lt;code&gt;true&lt;/code&gt; to fix an old bug. They can use the new flag &lt;code&gt;allowAutomaticBack&lt;/code&gt; 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 &quot;Nuke&quot; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2024/44|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2024-W44&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 20:57, 28 October 2024 (UTC)
&lt;!-- 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&amp;oldid=27668811 --&gt;

== Wikipedia translation of the week: 2024-45 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Placenta cake]]'''&lt;br /&gt; &lt;small&gt;''([[:simple:Placenta cake]])''&lt;/small&gt; &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Bucharest, Greek pie-maker, 1880.jpg|300px|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=27647428 --&gt;

== Tech News: 2024-45 ==

&lt;section begin=&quot;technews-2024-W45&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2024/45|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2024-W45&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 20:51, 4 November 2024 (UTC)
&lt;!-- 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&amp;oldid=27693917 --&gt;

== Wikipedia translation of the week: 2024-46 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Trisomy 16]]'''&lt;br /&gt; &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Chromosome 16.svg|300px|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=27708700 --&gt;

== Tech News: 2024-46 ==

&lt;section begin=&quot;technews-2024-W46&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &lt;code dir=&quot;ltr&quot;&gt;[[mw:MediaWiki_1.44/wmf.2|1.44.0-wmf-2]]&lt;/code&gt;, the logic of Wikibase function &lt;code&gt;getAllStatements&lt;/code&gt; changed to behave like &lt;code&gt;getBestStatements&lt;/code&gt;. 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]] &amp; [[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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2024/46|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2024-W46&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 00:08, 12 November 2024 (UTC)
&lt;!-- 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&amp;oldid=27732268 --&gt;

== Wikipedia translation of the week: 2024-47 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Boana platanera]]'''&lt;br /&gt; &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Rana platanera - Boana platanera.jpg|300px|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=27735014 --&gt;

== Tech News: 2024-47 ==

&lt;section begin=&quot;technews-2024-W47&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2024/47|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2024-W47&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 02:01, 19 November 2024 (UTC)
&lt;!-- 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&amp;oldid=27806858 --&gt;

== Wikipedia translation of the week: 2024-48 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Wang Su-bok]]'''&lt;br /&gt; &lt;small&gt;''([[:fa:وانگ سو بوک]])&amp;#32;([[:ko:왕수복]])''&lt;/small&gt; &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----

&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=27846897 --&gt;

== Tech News: 2024-48 ==

&lt;section begin=&quot;technews-2024-W48&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;Ctrl&lt;/code&gt;+&lt;code&gt;B&lt;/code&gt;&lt;/bdi&gt; for bold and &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;Ctrl&lt;/code&gt;+&lt;code&gt;I&lt;/code&gt;&lt;/bdi&gt; 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: &lt;bdi&gt;bswiki&lt;/bdi&gt;{{int:comma-separator/en}}&lt;bdi&gt;elwiki&lt;/bdi&gt;{{int:comma-separator/en}}&lt;bdi&gt;euwiki&lt;/bdi&gt;{{int:comma-separator/en}}&lt;bdi&gt;fawiki&lt;/bdi&gt;{{int:comma-separator/en}}&lt;bdi&gt;fiwiki&lt;/bdi&gt;{{int:comma-separator/en}}&lt;bdi&gt;frwikiquote&lt;/bdi&gt;{{int:comma-separator/en}}&lt;bdi&gt;frwikisource&lt;/bdi&gt;{{int:comma-separator/en}}&lt;bdi&gt;frwikiversity&lt;/bdi&gt;{{int:comma-separator/en}}&lt;bdi&gt;frwikivoyage&lt;/bdi&gt;{{int:comma-separator/en}}&lt;bdi&gt;idwiki&lt;/bdi&gt;{{int:comma-separator/en}}&lt;bdi&gt;lvwiki&lt;/bdi&gt;{{int:comma-separator/en}}&lt;bdi&gt;plwiki&lt;/bdi&gt;{{int:comma-separator/en}}&lt;bdi&gt;ptwiki&lt;/bdi&gt;{{int:comma-separator/en}}&lt;bdi&gt;urwiki&lt;/bdi&gt;{{int:comma-separator/en}}&lt;bdi&gt;viwikisource&lt;/bdi&gt;{{int:comma-separator/en}}&lt;bdi&gt;zhwikisource&lt;/bdi&gt;. 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 &quot;protected&quot; [[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 &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;Ctrl&lt;/code&gt;+&lt;code&gt;,&lt;/code&gt;&lt;/bdi&gt; and un-selecting &quot;&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;Live Autocompletion&lt;/bdi&gt;&quot;.
* [[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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2024/48|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2024-W48&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 22:42, 25 November 2024 (UTC)
&lt;!-- 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&amp;oldid=27847039 --&gt;

== Wikipedia translation of the week: 2024-49 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Storm Filomena]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Spain’s chilly blanket ESA22415247.jpeg|center|300px|]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=27846897 --&gt;

== Tech News: 2024-49 ==

&lt;section begin=&quot;technews-2024-W49&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &lt;code dir=&quot;ltr&quot;&gt;&lt;nowiki&gt;{{&lt;/nowiki&gt;[[mw:Special:MyLanguage/Help:Magic words#interwikilink|#interwikilink]]&lt;nowiki&gt;}}&lt;/nowiki&gt;&lt;/code&gt; function adds an [[mw:Special:MyLanguage/Help:Links#Interwiki links|interwiki link]] and the &lt;code dir=&quot;ltr&quot;&gt;&lt;nowiki&gt;{{&lt;/nowiki&gt;[[mw:Special:MyLanguage/Help:Magic words#interlanguagelink|#interlanguagelink]]&lt;nowiki&gt;}}&lt;/nowiki&gt;&lt;/code&gt; 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 &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;MOS:&lt;/code&gt;&lt;/bdi&gt; on English Wikipedia [[phab:T363538|conflict with the &lt;code&gt;mos&lt;/code&gt; 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: &lt;bdi&gt;arwiki&lt;/bdi&gt;{{int:comma-separator/en}}&lt;bdi&gt;cawiki&lt;/bdi&gt;{{int:comma-separator/en}}&lt;bdi&gt;frwiki&lt;/bdi&gt;{{int:comma-separator/en}}&lt;bdi&gt;mediawikiwiki&lt;/bdi&gt;{{int:comma-separator/en}}&lt;bdi&gt;orwiki&lt;/bdi&gt;{{int:comma-separator/en}}&lt;bdi&gt;wawiki&lt;/bdi&gt;{{int:comma-separator/en}}&lt;bdi&gt;wawiktionary&lt;/bdi&gt;{{int:comma-separator/en}}&lt;bdi&gt;wikidatawiki&lt;/bdi&gt;{{int:comma-separator/en}}&lt;bdi&gt;zhwiki&lt;/bdi&gt;. 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 &quot;Download as PDF&quot; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2024/49|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2024-W49&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 22:23, 2 December 2024 (UTC)
&lt;!-- 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&amp;oldid=27873992 --&gt;

== Wikipedia translation of the week: 2024-50 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Syrian literature]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Poem about Baybars page 1 from Hakawati book.jpg|center|300px|]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=27846897 --&gt;

== Tech News: 2024-50 ==

&lt;section begin=&quot;technews-2024-W50&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;#wikimedia-techdocs&lt;/bdi&gt; 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 &quot;[https://test.wikipedia.org/w/index.php?title=Special:ContentTranslation&amp;campaign=specialcx&amp;filter-type=automatic&amp;filter-id=collections&amp;active-list=suggestions&amp;from=es&amp;to=en All collection]&quot; category in the articles suggestion feature. Wikiproject Campaign organizers can use this feature, to help translators to discover articles of interest, by adding the &lt;code dir=ltr&gt;&lt;nowiki&gt;&lt;page-collection&gt; &lt;/page-collection&gt;&lt;/nowiki&gt;&lt;/code&gt; 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 &amp; 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, &lt;code dir=ltr&gt;archiveUrl&lt;/code&gt; and &lt;code dir=ltr&gt;archiveDate&lt;/code&gt;, 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&amp;diff=1261320172&amp;oldid=1260788022 example of a change in a template], and a [https://global-search.toolforge.org/?namespaces=10&amp;q=%5C%22citoid%5C%22%3A%20%5C%7B&amp;regex=1&amp;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:|&lt;code&gt;voy:id:&lt;/code&gt;]]) [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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2024/50|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2024-W50&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 22:16, 9 December 2024 (UTC)
&lt;!-- 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&amp;oldid=27919424 --&gt;

== Wikipedia translation of the week: 2024-51 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Mars ocean theory]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:AncientMars.jpg|center|300px|]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=27933909 --&gt;

== Tech News: 2024-51 ==

&lt;section begin=&quot;technews-2024-W51&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2024/51|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2024-W51&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 22:25, 16 December 2024 (UTC)
&lt;!-- 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&amp;oldid=27942374 --&gt;

== Wikipedia translation of the week: 2024-52 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2024 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:2023 Slovenia floods]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Sava v Tacnu 4. avgusta ob 16h.jpg|center|300px|]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=27933909 --&gt;

== Wikipedia translation of the week: 2025-01 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Uganda Railways Corporation]]'''&lt;br /&gt; &lt;small&gt;''([[:de:Schienenverkehr in Uganda]])&amp;#32;([[:no:Uganda Railways Corporation]])''&lt;/small&gt; &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:9620 mit Güterzug.jpg|center|300px|]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=28019313 --&gt;

== Wikipedia translation of the week: 2025-02 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Internment of Japanese Canadians]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Japanese road camp.jpg|center|300px|]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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 &quot;national security&quot;. 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 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=28070038 --&gt;

== Wikipedia translation of the week: 2025-03 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Christmas seals]]'''&lt;br /&gt; &lt;small&gt;''([[:no:Julemerke]])&amp;#32;([[:ru:Рождественская виньетка]])''&lt;/small&gt; &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:1915 US Christmas Seal.jpg|center|300px|]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=28086717 --&gt;

== Tech News: 2025-03 ==

&lt;section begin=&quot;technews-2025-W03&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &lt;code dir=ltr&gt;inproject:&lt;/code&gt; 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:|&lt;code&gt;w:tig:&lt;/code&gt;]]) [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 &lt;code&gt;sub&lt;/code&gt; 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 &lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[MediaWiki:Common.css]]&lt;/bdi&gt; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2025/03|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2025-W03&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 01:42, 14 January 2025 (UTC)
&lt;!-- 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&amp;oldid=28048614 --&gt;

== Wikipedia translation of the week: 2025-04 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:2010 Nagorno-Karabakh clashes]]'''&lt;br /&gt; &lt;small&gt;''([[:it:Scontri del Nagorno Karabakh del 2010]])&amp;#32;([[:tr:2010 Dağlık Karabağ çatışmaları]])''&lt;/small&gt; &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----

&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=28099770 --&gt;

== Tech News: 2025-04 ==

&lt;section begin=&quot;technews-2025-W04&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;manually patrolled&quot; instead of &quot;autopatrolled&quot;, 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 &quot;Insert link&quot; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2025/04|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2025-W04&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 01:37, 21 January 2025 (UTC)
&lt;!-- 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&amp;oldid=28129769 --&gt;

== Wikipedia translation of the week: 2025-05 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Jinnah's birthday]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Yorkstatue.jpg|center|300px]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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 (&quot;Great Leader&quot;). 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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=28156501 --&gt;

== Tech News: 2025-05 ==

&lt;section begin=&quot;technews-2025-W05&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &amp; 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 &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;mediawiki_user_history&lt;/code&gt;&lt;/bdi&gt; dump, the &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;anonymous&lt;/code&gt;&lt;/bdi&gt; field will be renamed to &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;is_anonymous&lt;/code&gt;&lt;/bdi&gt;. 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2025/05|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2025-W05&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 22:15, 27 January 2025 (UTC)
&lt;!-- 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&amp;oldid=28149374 --&gt;

== Wikipedia translation of the week: 2025-06 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:French conquest of Corsica]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Bataille de Ponte Novu.jpg|center|300px]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=28200320 --&gt;

== Tech News: 2025-06 ==

&lt;section begin=&quot;technews-2025-W06&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;Special characters&quot; 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 &lt;code&gt;&lt;nowiki&gt;&lt;code&gt;&lt;/nowiki&gt;&lt;/code&gt; 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 &lt;code dir=ltr&gt;MediaWiki:Citoid-template-type-map.json&lt;/code&gt; to include entries for &lt;code dir=ltr&gt;preprint&lt;/code&gt;, &lt;code dir=ltr&gt;standard&lt;/code&gt;, and &lt;code dir=ltr&gt;dataset&lt;/code&gt;; Here are example diffs to replicate [https://en.wikipedia.org/w/index.php?title=MediaWiki%3ACitoid-template-type-map.json&amp;diff=1189164774&amp;oldid=1165783565 for 'preprint'] and [https://en.wikipedia.org/w/index.php?title=MediaWiki%3ACitoid-template-type-map.json&amp;diff=1270832208&amp;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&amp;diff=1270829051&amp;oldid=1262470053 for 'preprint'] and [https://en.wikipedia.org/w/index.php?title=Template%3ACitation%2Fdoc&amp;diff=1270831369&amp;oldid=1270829480 for 'standard' and 'dataset']. The new fields that may need to be supported are &lt;code dir=ltr&gt;archiveID&lt;/code&gt;, &lt;code dir=ltr&gt;identifier&lt;/code&gt;, &lt;code dir=ltr&gt;repository&lt;/code&gt;, &lt;code dir=ltr&gt;organization&lt;/code&gt;, &lt;code dir=ltr&gt;repositoryLocation&lt;/code&gt;, &lt;code dir=ltr&gt;committee&lt;/code&gt;, and &lt;code dir=ltr&gt;versionNumber&lt;/code&gt;. [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:|&lt;code&gt;w:knc:&lt;/code&gt;]]) [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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2025/06|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2025-W06&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 00:09, 4 February 2025 (UTC)
&lt;!-- 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&amp;oldid=28203495 --&gt;

== Wikipedia translation of the week: 2025-07 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Assassination of Spencer Perceval]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:PercevalShooting.jpg|center|300px]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=28200320 --&gt;

== Tech News: 2025-07 ==

&lt;section begin=&quot;technews-2025-W07&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;Special pages&quot; portlet link will be moved from the &quot;Toolbox&quot; into the &quot;Navigation&quot; 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 (&lt;code dir=ltr&gt;[https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-reduced-motion prefers-reduced-motion]&lt;/code&gt;, &lt;code dir=ltr&gt;[https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-reduced-transparency prefers-reduced-transparency]&lt;/code&gt;, &lt;code dir=ltr&gt;[https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-contrast prefers-contrast]&lt;/code&gt;, and &lt;code dir=ltr&gt;[https://developer.mozilla.org/en-US/docs/Web/CSS/@media/forced-colors forced-colors]&lt;/code&gt;). 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 &quot;default for all languages&quot;]] 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 &lt;code dir=&quot;ltr&quot;&gt;getDescription&lt;/code&gt; 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 &lt;code dir=&quot;ltr&quot;&gt;/page/related&lt;/code&gt; 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 &quot;&lt;code dir=&quot;ltr&quot;&gt;morelike&lt;/code&gt;&quot; 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 &quot;Contribute&quot; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2025/07|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2025-W07&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 00:12, 11 February 2025 (UTC)
&lt;!-- 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&amp;oldid=28231022 --&gt;

== Wikipedia translation of the week: 2025-08 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:2010 Malagasy constitutional referendum]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----

&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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 &quot;Yes&quot; or &quot;No&quot; 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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=28245290 --&gt;

== Tech News: 2025-08 ==

&lt;section begin=&quot;technews-2025-W08&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &lt;code&gt;{{#special:Homepage}}&lt;/code&gt; 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 &lt;code&gt;{{#special:CommunityConfiguration}}&lt;/code&gt;. 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 &quot;1.23&quot; or localized alphabetic markers like &quot;a b c&quot; 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 &quot;1.23&quot; 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 &lt;code dir=ltr&gt;mw.Uri&lt;/code&gt; is deprecated. Tools requiring &lt;code dir=ltr&gt;mw.Uri&lt;/code&gt; must explicitly declare &lt;code dir=ltr&gt;mediawiki.Uri&lt;/code&gt; as a ResourceLoader dependency, and should migrate to the browser native &lt;code dir=ltr&gt;URL&lt;/code&gt; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2025/08|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2025-W08&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 21:17, 17 February 2025 (UTC)
&lt;!-- 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&amp;oldid=28275610 --&gt;

== Wikipedia translation of the week: 2025-09 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Cooler Heads Coalition]]'''&lt;br /&gt; &lt;small&gt;''([[:de:Cooler Heads Coalition]])&amp;#32;([[:fr:Cooler Heads Coalition]])''&lt;/small&gt; &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----

&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
The '''Cooler Heads Coalition''' is a politically conservative &quot;informal and ad-hoc group&quot; 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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=28300238 --&gt;

== Tech News: 2025-09 ==

&lt;section begin=&quot;technews-2025-W09&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[https://www.wikimedia.org/ wikimedia.org]&lt;/bdi&gt; 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 &lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[https://wikibooks.org wikibooks.org]&lt;/bdi&gt;, 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:|&lt;code&gt;wikt:sat:&lt;/code&gt;]]) [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&amp;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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2025/09|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2025-W09&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 00:42, 25 February 2025 (UTC)
&lt;!-- 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&amp;oldid=28296129 --&gt;

== Wikipedia translation of the week: 2025-10 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:pt:Transmissor de Ondas]]'''&lt;br /&gt; &lt;small&gt;''([[:en:Wave Transmitter]])''&lt;/small&gt; &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Esq eletr transm ondas color.jpg|center|300px]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=28317097 --&gt;

== Tech News: 2025-10 ==

&lt;section begin=&quot;technews-2025-W10&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;{{int:Minerva-page-actions-editfull}}&quot; link is accessible from the &quot;{{int:minerva-page-actions-overflow}}&quot; 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 &quot;&lt;code dir=&quot;ltr&quot;&gt;mw-ref&lt;/code&gt;&quot; from their local &lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[MediaWiki:Common.css]]&lt;/bdi&gt;. 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&amp;regex=1&amp;namespaces=8&amp;title=.*css can be found with this global search] and in [https://ace.wikipedia.org/w/index.php?title=MediaWiki:Common.css&amp;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 (&quot;&lt;code dir=&quot;ltr&quot;&gt;[1]&lt;/code&gt;&quot;) are now rendered by [[mw:Special:MyLanguage/Parsoid|Parsoid]], and the deprecated CSS is no longer needed. The CSS for backlinks (&quot;&lt;code dir=&quot;ltr&quot;&gt;mw:referencedBy&lt;/code&gt;&quot;) 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. &lt;code&gt;&lt;nowiki&gt;[[File:MediaWiki.png]]&lt;/nowiki&gt;&lt;/code&gt;) 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. &lt;code&gt;&lt;nowiki&gt;{{:File:MediaWiki.png}}&lt;/nowiki&gt;&lt;/code&gt;) 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:|&lt;code&gt;w:syl:&lt;/code&gt;]]) [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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2025/10|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2025-W10&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 02:31, 4 March 2025 (UTC)
&lt;!-- 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&amp;oldid=28334563 --&gt;

== Wikipedia translation of the week: 2025-11 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:it:Smoky (mascotte olimpica)]]'''&lt;br /&gt; &lt;small&gt;''([[:en:Smoky (Olympic mascot)]])''&lt;/small&gt; &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Smoky 1932 Olympic Village Mascot.webp|center|300px]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=28317097 --&gt;

== Tech News: 2025-11 ==

&lt;section begin=&quot;technews-2025-W11&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &amp; Limited Internet Use|Join the discussion]] or email &lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;aramadan@wikimedia.org&lt;/bdi&gt;!
* 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2025/11|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2025-W11&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 23:10, 10 March 2025 (UTC)
&lt;!-- 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&amp;oldid=28372257 --&gt;

== Wikipedia translation of the week: 2025-12 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Amazonas, o maior rio do mundo]]'''&lt;br /&gt; &lt;small&gt;''([[:pt:Amazonas, o maior rio do mundo]])&amp;#32;([[:es:Amazonas, o maior rio do mundo]])''&lt;/small&gt; &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Frame A from Amazonas, o maior rio do mundo.jpg|center|300px]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''''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 &quot;immense artistic value&quot; by Le Monde. It has also been described as the &quot;Holy Grail of Brazilian silent cinema&quot; by The Guardian. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=28392163 --&gt;

== Tech News: 2025-12 ==

&lt;section begin=&quot;technews-2025-W12&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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&amp;filter-type=automatic&amp;filter-id=previous-edits&amp;active-list=suggestions&amp;from=en&amp;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&amp;active-list=suggestions&amp;from=en&amp;to=ig&amp;filter-type=automatic&amp;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 &amp; Community-defined lists|Community-defined lists]] filter, also known as &quot;Collections&quot;, 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2025/12|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2025-W12&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 23:48, 17 March 2025 (UTC)
&lt;!-- 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&amp;oldid=28412594 --&gt;

== Wikipedia translation of the week: 2025-13 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Ali of the Eretnids]]'''&lt;br /&gt; &lt;small&gt;''([[:tr:Alaaddin Ali Bey]])''&lt;/small&gt; &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----

&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=28433698 --&gt;

== Tech News: 2025-13 ==

&lt;section begin=&quot;technews-2025-W13&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &amp; 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 &lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;white-space: nowrap;&quot;&gt;#campaigns-product-team&lt;/bdi&gt; 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 &lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;white-space: nowrap;&quot;&gt;#campaigns-product-team&lt;/bdi&gt; tag). Participants of past events can cancel their registration at any time.
* Administrators at wikis that have a customized &lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[MediaWiki:Sidebar]]&lt;/bdi&gt; should check that it contains an entry for the {{int:specialpages}} listing. If it does not, they should add it using &lt;code dir=ltr style=&quot;white-space: nowrap;&quot;&gt;* specialpages-url|specialpages&lt;/code&gt;. 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 &lt;code dir=ltr&gt;mw.Api&lt;/code&gt; JavaScript library, can now identify the tool using it with the &lt;code dir=ltr&gt;userAgent&lt;/code&gt; parameter: &lt;code dir=ltr&gt;var api = new mw.Api( { userAgent: 'GadgetNameHere/1.0.1' } );&lt;/code&gt;. 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2025/13|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2025-W13&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 22:43, 24 March 2025 (UTC)
&lt;!-- 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&amp;oldid=28443127 --&gt;

== Wikipedia translation of the week: 2025-14 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Chilembwe uprising]]'''&lt;br /&gt; &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Chilembwe supporters being led to be executed (cropped).jpg|center|300px]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=28454663 --&gt;

== Tech News: 2025-14 ==

&lt;section begin=&quot;technews-2025-W14&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[http://maps.wikimedia.org/ maps.wikimedia.org]&lt;/bdi&gt; - 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2025/14|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2025-W14&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 00:06, 1 April 2025 (UTC)
&lt;!-- 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&amp;oldid=28473566 --&gt;

== Wikipedia translation of the week: 2025-15 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:1930 Bago earthquake]]'''&lt;br /&gt; &lt;small&gt;''([[:my:၁၉၃၀ ပဲခူးငလျင်]])''&lt;/small&gt; &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Thiao Mueang Phama (1955, p. 165).jpg|center|300px]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=28454663 --&gt;

== Tech News: 2025-15 ==

&lt;section begin=&quot;technews-2025-W15&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &lt;code dir=ltr style=&quot;white-space: nowrap;&quot;&gt;font-size&lt;/code&gt;, &lt;code dir=ltr style=&quot;white-space: nowrap;&quot;&gt;line-height&lt;/code&gt;, and &lt;code dir=ltr style=&quot;white-space: nowrap;&quot;&gt;size-icon&lt;/code&gt;.
* 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2025/15|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2025-W15&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 18:53, 7 April 2025 (UTC)
&lt;!-- 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&amp;oldid=28507470 --&gt;

== Wikipedia translation of the week: 2025-16 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Museum of Zoology of the University of São Paulo]]'''&lt;br /&gt; &lt;small&gt;''([[:pt:Museu de Zoologia da Universidade de São Paulo]])''&lt;/small&gt; &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Museu de Zoologia da USP 02.jpg|center|300px]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=28454663 --&gt;

== Tech News: 2025-16 ==

&lt;section begin=&quot;technews-2025-W16&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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]
* &quot;Are you interested in taking a short survey to improve tools used for reviewing or reverting edits on your Wiki?&quot; 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 &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;[https://query.wikidata.org/ query.wikidata.org]&lt;/bdi&gt;. After this date, scholarly articles will be available through &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot; style=&quot;white-space:nowrap;&quot;&gt;[https://query-scholarly.wikidata.org/ query-scholarly.wikidata.org]&lt;/bdi&gt;, while the rest of the data hosted on Wikidata will be available through the &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;[https://query.wikidata.org/ query.wikidata.org]&lt;/bdi&gt; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2025/16|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2025-W16&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 00:25, 15 April 2025 (UTC)
&lt;!-- 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&amp;oldid=28540654 --&gt;

== Wikipedia translation of the week: 2025-17 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Fear of crime]]'''&lt;br /&gt; &lt;small&gt;''([[:ar:الخوف من الجريمة]])&amp;#32;([[:it:Criminofobia]])''&lt;/small&gt; &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----

&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=28559524 --&gt;

== Tech News: 2025-17 ==

&lt;section begin=&quot;technews-2025-W17&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;Structured Contents&quot; 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 &quot;peacock&quot; or &quot;overly-promotional&quot; or &quot;non-neutral&quot; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2025/17|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2025-W17&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 21:01, 21 April 2025 (UTC)
&lt;!-- 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&amp;oldid=28578245 --&gt;

== Wikipedia translation of the week: 2025-18 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Heritage preservation in South Korea]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Korean.Dance-03.jpg|300px|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=28583422 --&gt;

== Tech News: 2025-18 ==

&lt;section begin=&quot;technews-2025-W18&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &lt;code dir=&quot;ltr&quot;&gt;ipblocks&lt;/code&gt;, &lt;code dir=&quot;ltr&quot;&gt;ipblocks_ipindex&lt;/code&gt;, and &lt;code dir=&quot;ltr&quot;&gt;ipblocks_compat&lt;/code&gt; are [[phab:T390767|now deprecated]]. Users can query the &lt;code dir=&quot;ltr&quot;&gt;[[mw:Special:MyLanguage/Manual:Block_table|block]]&lt;/code&gt; and &lt;code dir=&quot;ltr&quot;&gt;[[mw:Special:MyLanguage/Manual:Block_target_table|block_target]]&lt;/code&gt; 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&amp;campaign=contributionsmenu&amp;to=es&amp;filter-type=automatic&amp;filter-id=previous-edits&amp;active-list=suggestions&amp;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 &quot;Understanding and Navigating Conflict in Wikimedia Projects&quot;. 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2025/18|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2025-W18&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 19:32, 28 April 2025 (UTC)
&lt;!-- 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&amp;oldid=28585685 --&gt;

== Wikipedia translation of the week: 2025-19 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Lhamana]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:We-Wa, a Zuni berdache, weaving - NARA - 523796 (cropped).jpg|300px|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=28583422 --&gt;

== Tech News: 2025-19 ==

&lt;section begin=&quot;technews-2025-W19&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &amp; 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 &lt;code dir=ltr&gt;moment&lt;/code&gt; library in gadgets and user scripts should revise their code to use alternatives like the &lt;code dir=ltr&gt;Intl&lt;/code&gt; library or the new &lt;code dir=ltr&gt;mediawiki.DateFormatter&lt;/code&gt; library. The &lt;code dir=ltr&gt;moment&lt;/code&gt; 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 (&lt;code dir=ltr style=&quot;white-space: nowrap;&quot;&gt;wbt_*&lt;/code&gt;) 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2025/19|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2025-W19&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 00:15, 6 May 2025 (UTC)
&lt;!-- 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&amp;oldid=28665011 --&gt;

== Wikipedia translation of the week: 2025-20 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:it:Gruppo del Sileno]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Parco3.JPG|300px|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=28709947 --&gt;

== Tech News: 2025-20 ==

&lt;section begin=&quot;technews-2025-W20&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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|&quot;Get shortened URL&quot;]] 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:|&lt;code&gt;w:nup:&lt;/code&gt;]]). 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 &lt;code dir=&quot;ltr&quot;&gt;/page/data-parsoid&lt;/code&gt; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2025/20|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2025-W20&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 22:38, 12 May 2025 (UTC)
&lt;!-- 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&amp;oldid=28714188 --&gt;

== Wikipedia translation of the week: 2025-21 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Lorrin A. Thurston]]'''&lt;br /&gt; &lt;small&gt;''([[:fi:Lorrin Thurston]])&amp;#32;([[:ko:로린 A. 서스턴]])''&lt;/small&gt; &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Lorrinandrewsthurston1892.jpg|300px|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=28731710 --&gt;

== Tech News: 2025-21 ==

&lt;section begin=&quot;technews-2025-W21&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &lt;code dir=ltr&gt;mw.title&lt;/code&gt; 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 &lt;code dir=ltr&gt;isDisambiguationPage&lt;/code&gt;. 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 &lt;code dir=ltr&gt;mw.loader.load&lt;/code&gt;. The tool's author hopes this will enable collaborative development workflows for user scripts including linting, unit tests, code generation, and code review on &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;gitlab.wikimedia.org&lt;/bdi&gt; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2025/21|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2025-W21&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 23:13, 19 May 2025 (UTC)
&lt;!-- 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&amp;oldid=28724712 --&gt;

== Wikipedia translation of the week: 2025-22 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:it:Lamiera bugnata]]'''&lt;br /&gt; &lt;small&gt;''([[:en:Tread plate]])''&lt;/small&gt; &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Diamond Plate.jpg|300px|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=28751788 --&gt;

== Tech News: 2025-22 ==

&lt;section begin=&quot;technews-2025-W22&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &lt;code&gt;+&lt;/code&gt; 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 &lt;code dir=ltr&gt;[[mw:Special:MyLanguage/Help:Extension:ParserFunctions##ifexist|#ifexist]]&lt;/code&gt; 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 &lt;code dir=ltr&gt;[[mw:Special:MyLanguage/Manual:Ipblocks table|ipblocks]]&lt;/code&gt; views in [[wikitech:Help:Wiki Replicas|Wiki Replicas]] will be removed in the beginning of June. Users are encouraged to query the new &lt;code dir=ltr&gt;[[mw:Special:MyLanguage/Manual:Block table|block]]&lt;/code&gt; and &lt;code dir=ltr&gt;[[mw:Special:MyLanguage/Manual:Block target table|block_target]]&lt;/code&gt; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2025/22|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2025-W22&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 20:05, 26 May 2025 (UTC)
&lt;!-- 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&amp;oldid=28788673 --&gt;

== Wikipedia translation of the week: 2025-23 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:it:Angelo azzurro (cocktail)]]'''&lt;br /&gt; &lt;small&gt;''([[:es:Ángel azul (cóctel)]])&amp;#32;([[:fr:Ange bleu (cocktail)]])''&lt;/small&gt; &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Angelo Azzurro Cocktail.png|300px|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=28788623 --&gt;

== Tech News: 2025-23 ==

&lt;section begin=&quot;technews-2025-W23&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &lt;code dir=ltr&gt;_default&lt;/code&gt; key in the local &lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[MediaWiki:Citoid-template-type-map.json]]&lt;/bdi&gt; 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 &lt;code dir=ltr&gt;action=login&lt;/code&gt; or &lt;code dir=ltr&gt;action=clientlogin&lt;/code&gt; 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 &lt;code dir=ltr&gt;action=login&lt;/code&gt; 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 &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;async&lt;/code&gt;/&lt;code&gt;await&lt;/code&gt;&lt;/bdi&gt; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2025/23|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2025-W23&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 23:55, 2 June 2025 (UTC)
&lt;!-- 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&amp;oldid=28819186 --&gt;

== Wikipedia translation of the week: 2025-24 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:fi:Kotiryssä]]'''&lt;br /&gt; &lt;small&gt;''([[:en:Kotiryssä]])''&lt;/small&gt; &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----

&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=28788623 --&gt;

== Tech News: 2025-24 ==

&lt;section begin=&quot;technews-2025-W24&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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]] (&quot;{{int:discussiontools-preference-visualenhancements}}&quot;). [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 &lt;code dir=ltr&gt;pageImage&lt;/code&gt; and &lt;code dir=ltr&gt;pageAssessments&lt;/code&gt;. [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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2025/24|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2025-W24&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 01:17, 10 June 2025 (UTC)
&lt;!-- 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&amp;oldid=28846858 --&gt;

== Wikipedia translation of the week: 2025-25 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Future self]]'''&lt;br /&gt; &lt;small&gt;''([[:pl:Przyszła jaźń]])''&lt;/small&gt; &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----

&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=28788623 --&gt;

== Tech News: 2025-25 ==

&lt;section begin=&quot;technews-2025-W25&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2025/25|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2025-W25&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 23:39, 16 June 2025 (UTC)
&lt;!-- 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&amp;oldid=28870688 --&gt;

== Wikipedia translation of the week: 2025-26 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Pictorial map]]'''&lt;br /&gt; &lt;small&gt;''([[:fa:نقشه تصویری]])&amp;#32;([[:ja:絵地図]])''&lt;/small&gt; &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Blake Britain Spearhead of Attack.jpg|center|300px]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=28788623 --&gt;

== Tech News: 2025-26 ==

&lt;section begin=&quot;technews-2025-W26&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &lt;code dir=ltr&gt;all_links&lt;/code&gt; variable in [[Special:AbuseFilter|AbuseFilter]] is now renamed to &lt;code dir=ltr&gt;new_links&lt;/code&gt; 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 &quot;Add a Link&quot; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2025/26|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2025-W26&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 23:21, 23 June 2025 (UTC)
&lt;!-- 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&amp;oldid=28870688 --&gt;

== Wikipedia translation of the week: 2025-27 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Queen Elizabeth University Hospital]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:QEUH.jpg|center|300px]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=28788623 --&gt;

== Tech News: 2025-27 ==

&lt;section begin=&quot;technews-2025-W27&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;Find in page&quot; 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 &quot;favourite list&quot;. 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2025/27|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2025-W27&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 23:41, 30 June 2025 (UTC)
&lt;!-- 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&amp;oldid=28917415 --&gt;

== Wikipedia translation of the week: 2025-28 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Non-constituency Member of Parliament]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----

&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=28788623 --&gt;

== Tech News: 2025-28 ==

&lt;section begin=&quot;technews-2025-W28&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;Connecting People through Linked Open Data&quot;.

'''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2025/28|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2025-W28&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 00:06, 8 July 2025 (UTC)
&lt;!-- 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&amp;oldid=28930584 --&gt;

== Wikipedia translation of the week: 2025-29 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Immunolabeling]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Immunolabeling process image.png|300px|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
---[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=28945528 --&gt;

== Tech News: 2025-29 ==

&lt;section begin=&quot;technews-2025-W29&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;featured&quot; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2025/29|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2025-W29&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 20:10, 14 July 2025 (UTC)
&lt;!-- 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&amp;oldid=28980963 --&gt;

== Wikipedia translation of the week: 2025-30 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Vespa analis]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Plumpy hornet on the ground - 1.jpg|300px|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''''Vespa analis''''', the yellow-vented hornet, is a species of common hornet found in Southeast Asia 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=28984647 --&gt;

== Tech News: 2025-30 ==

&lt;section begin=&quot;technews-2025-W30&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;[https://en.wikipedia.org/w/index.php?title=Special:ContentTranslation&amp;filter-type=automatic&amp;filter-id=previous-edits&amp;active-list=suggestions&amp;from=en&amp;to=fi#/ ... More]&quot; 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 &quot;{{int:Cx-sx-suggestions-filters-tab-regions}}&quot; filter. [https://phabricator.wikimedia.org/T113257]
* Administrators can now limit &quot;Add a Link&quot; to newcomers. The [[mw:Special:MyLanguage/Help:Growth/Tools/Add a link|&quot;Add a Link&quot;]] Structured Task [[mw:Special:MyLanguage/Growth/Constructive activation experimentation#Enwiki A/B test &amp; &quot;Add a Link&quot; Improvements (Wiki Experiences 1.2.11 &amp; 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 &lt;code dir=ltr&gt;beta.wmflabs.org&lt;/code&gt; to &lt;code dir=ltr&gt;beta.wmcloud.org&lt;/code&gt;. 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2025/30|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2025-W30&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 23:43, 21 July 2025 (UTC)
&lt;!-- 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&amp;oldid=29005283 --&gt;

== Wikipedia translation of the week: 2025-31 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Fernando de Noronha Marine National Park]]'''&lt;br /&gt; &lt;small&gt;''([[:pt:Parque Nacional Marinho de Fernando de Noronha]])''&lt;/small&gt; &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Baía dos Porcos - Fernando de Noronha (32811749914).jpg|300px|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''Fernando de Noronha Marine National Park''' (Portuguese: Parque Nacional Marinho de Fernando de Noronha) is a national park in the state of Pernambuco, Brazil. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=29047614 --&gt;

== Tech News: 2025-31 ==

&lt;section begin=&quot;technews-2025-W31&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &lt;code dir=ltr&gt;MediaWiki:Sp-contributions-footer-temp&lt;/code&gt;. [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 &quot;no camera&quot; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2025/31|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2025-W31&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 00:27, 29 July 2025 (UTC)
&lt;!-- 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&amp;oldid=29051727 --&gt;

== Wikipedia translation of the week: 2025-32 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Xie Zhiliu]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----

&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''Xie Zhiliu''' (Chinese: 谢稚柳; 1910–1997) was a leading traditional painter, calligrapher, and art connoisseur of modern China. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=29077280 --&gt;

== Tech News: 2025-32 ==

&lt;section begin=&quot;technews-2025-W32&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &lt;code dir=ltr&gt;MediaWiki:Ipb-default-expiry-temporary-account&lt;/code&gt; and use a value defined in &lt;code dir=ltr&gt;MediaWiki:Ipboptions&lt;/code&gt;. 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 &lt;code dir=ltr&gt;.vue&lt;/code&gt; 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 &quot;no camera&quot; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2025/32|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2025-W32&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 03:41, 5 August 2025 (UTC)
&lt;!-- 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&amp;oldid=29083927 --&gt;

== Wikipedia translation of the week: 2025-33 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Lethocerus patruelis]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Lethocerus patruelis.jpg|300px|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=29085671 --&gt;

== Tech News: 2025-33 ==

&lt;section begin=&quot;technews-2025-W33&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;X&quot; to a back arrow. This helps to distinguish it from the other &quot;X&quot; button that is used to clear any text. [https://phabricator.wikimedia.org/T393944]
* Editors on some wikis will see a new toggle for &quot;Group results by page&quot; 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 &quot;One common data source, multiple local wikis&quot;. 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 &lt;code dir=ltr&gt;mw.addWarning()&lt;/code&gt; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2025/33|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2025-W33&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 23:30, 11 August 2025 (UTC)
&lt;!-- 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&amp;oldid=29106516 --&gt;

== Wikipedia translation of the week: 2025-34 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Ikiza]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:CIA map of Burundi and surrounding countries during 1972 killings.jpg|300px|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=29115447 --&gt;

== Tech News: 2025-34 ==

&lt;section begin=&quot;technews-2025-W34&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;[[mw:Special:MyLanguage/Talk pages project/Feature summary|Discussion tools]]&quot; [[Special:Preferences#mw-prefsection-betafeatures|Beta Feature]] enabled will gain the ability to &quot;Thank&quot; 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:|&lt;code&gt;s:tl:&lt;/code&gt;]]) [https://phabricator.wikimedia.org/T388639]
** a {{int:project-localized-name-group-wikisource/en}} in [[d:Q36213|Madurese]] ([[s:mad:|&lt;code&gt;s:mad:&lt;/code&gt;]]) [https://phabricator.wikimedia.org/T391747]
** a {{int:project-localized-name-group-wikipedia/en}} in [[d:Q3450749|Rakhine]] ([[w:rki:|&lt;code&gt;w:rki:&lt;/code&gt;]]) [https://phabricator.wikimedia.org/T392490]
** a {{int:project-localized-name-group-wikibooks/en}} in [[d:Q13324|Minangkabau]] ([[b:min:|&lt;code&gt;b:min:&lt;/code&gt;]]) [https://phabricator.wikimedia.org/T395452]
** a {{int:project-localized-name-group-wiktionary/en}} in [[d:Q7598268|Standard Moroccan Amazigh]] ([[wikt:zgh:|&lt;code&gt;wikt:zgh:&lt;/code&gt;]]) [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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2025/34|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2025-W34&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 00:39, 19 August 2025 (UTC)
&lt;!-- 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&amp;oldid=29127690 --&gt;

== Wikipedia translation of the week: 2025-35 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Corallite]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Recent azooxanthellate Scleractinia (Cnidaria, Anthozoa) - ZooKeys-227-001-g004.jpeg|300px|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=29115447 --&gt;

== Tech News: 2025-35 ==

&lt;section begin=&quot;technews-2025-W35&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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: &lt;code&gt;width: fit-content&lt;/code&gt;; &lt;code&gt;ruby-align&lt;/code&gt;; relative units such as &lt;code&gt;lh&lt;/code&gt;; and custom strings in &lt;code&gt;list-style-type&lt;/code&gt;. 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:|&lt;code&gt;wikt:bew:&lt;/code&gt;]]) [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. &lt;code&gt;rc_new&lt;/code&gt; and &lt;code&gt;rc_type&lt;/code&gt; are being removed in favor of &lt;code&gt;rc_source&lt;/code&gt;. Queries to these older fields will start to fail starting this week and developers should use &lt;code&gt;rc_source&lt;/code&gt; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2025/35|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2025-W35&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 00:13, 26 August 2025 (UTC)
&lt;!-- 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&amp;oldid=29175124 --&gt;

== Wikipedia translation of the week: 2025-36 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Diksam Plateau]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Dixam plateau (6407168437).jpg|300px|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=29195081 --&gt;

== Tech News: 2025-36 ==

&lt;section begin=&quot;technews-2025-W36&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;Templates used on this page,&quot; 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 &lt;code&gt;Special:RecentChanges&lt;/code&gt;, &lt;code&gt;Special:Watchlist&lt;/code&gt;, and &lt;code&gt;Special:RelatedChanges&lt;/code&gt; 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 &quot;lightweight enumeration types&quot;, 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&amp;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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2025/36|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2025-W36&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 20:51, 1 September 2025 (UTC)
&lt;!-- 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&amp;oldid=29196010 --&gt;

== Wikipedia translation of the week: 2025-37 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:it:Ttongsul]]'''&lt;br /&gt; &lt;small&gt;''([[:ja:トンスル]])''&lt;/small&gt; &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Ttongsul (imitation).jpg|300px|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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.  

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=29195081 --&gt;

== Tech News: 2025-37 ==

&lt;section begin=&quot;technews-2025-W37&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;{{int:codemirror-beta-feature-title}}&quot; [[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 &lt;code dir=ltr&gt;en.wikipedia.org&lt;/code&gt;), the software responds in one of two ways: a desktop page, or a redirect to a mobile version on an &quot;m&quot; domain (like &lt;code dir=ltr&gt;en.m.wikipedia.org&lt;/code&gt;). 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 &quot;Desktop view&quot; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2025/37|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2025-W37&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 01:15, 9 September 2025 (UTC)
&lt;!-- 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&amp;oldid=29238161 --&gt;

== Wikipedia translation of the week: 2025-38 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Pak Kum-chol]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Pak Kum-chol in 1961 (cropped).jpg|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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 &quot;Kapsan faction&quot;. 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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=29249252 --&gt;

== Tech News: 2025-38 ==

&lt;section begin=&quot;technews-2025-W38&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &lt;code dir=ltr&gt;&lt;nowiki&gt;&lt;references/&gt;&lt;/nowiki&gt;&lt;/code&gt; [[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 &lt;code dir=ltr&gt;intitle:&lt;/code&gt; keyword: [[mw:Special:MyLanguage/Help:CirrusSearch#Metacharacters|metacharacters]] for start-of-line (&lt;code dir=ltr&gt;^&lt;/code&gt;) and end-of-line (&lt;code dir=ltr&gt;$&lt;/code&gt;) anchors [https://phabricator.wikimedia.org/T317599]
** for both &lt;code dir=ltr&gt;intitle:&lt;/code&gt; and &lt;code dir=ltr&gt;insource:&lt;/code&gt; keywords: shorthand [[mw:Special:MyLanguage/Help:CirrusSearch#Character_Classes|character classes]] for digits (&lt;code dir=ltr&gt;\d&lt;/code&gt;), whitespace (&lt;code dir=ltr&gt;\s&lt;/code&gt;), and word characters (&lt;code dir=ltr&gt;\w&lt;/code&gt;); and [[mw:Special:MyLanguage/Help:CirrusSearch#Escape codes|escape codes]] for line feed (&lt;code dir=ltr&gt;\r&lt;/code&gt;), newline (&lt;code dir=ltr&gt;\n&lt;/code&gt;), tab (&lt;code dir=ltr&gt;\t&lt;/code&gt;), and unicode (e.g. &lt;code dir=ltr&gt;\uHHHH&lt;/code&gt;). [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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2025/38|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2025-W38&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 17:08, 15 September 2025 (UTC)
&lt;!-- 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&amp;oldid=29263921 --&gt;

== Wikipedia translation of the week: 2025-39 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Federation of Central America (1921–1922)]]'''&lt;br /&gt; &lt;small&gt;''([[:es:Federación de Centro América (1921-1922)]])&amp;#32;([[:ar:اتحاد أمريكا الوسطى (1921-1922)]])''&lt;/small&gt; &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Central America's Northern Triangle (orthographic projection).png|300px|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=29311347 --&gt;

== Tech News: 2025-39 ==

&lt;section begin=&quot;technews-2025-W39&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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/ &quot;Listen to Wikipedia&quot;] 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: &lt;code&gt;&lt;nowiki&gt;{{#contentmodel}}&lt;/nowiki&gt;&lt;/code&gt;. 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 &lt;code&gt;DISPLAYTITLE&lt;/code&gt; for an article using VisualEditor will no longer be broken. Editors who use VisualEditor mode to modify the &lt;code&gt;&lt;nowiki&gt;{{DISPLAYTITLE}}&lt;/nowiki&gt;&lt;/code&gt; would no longer have the literal text &quot;DISPLAYTITLE&quot; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2025/39|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2025-W39&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 22:56, 22 September 2025 (UTC)
&lt;!-- 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&amp;oldid=29305556 --&gt;

== Wikipedia translation of the week: 2025-40 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:it:Palazzo delle Poste (Latina)]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Postelittoria2.jpg|300px|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=29341788 --&gt;

== Tech News: 2025-40 ==

&lt;section begin=&quot;technews-2025-W40&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &lt;code&gt;sp-contributions-blocked-notice&lt;/code&gt;] will be removed and replaced with [{{fullurl:Special:Allmessages|prefix=blocked-notice-logextract}} those prefixed with &lt;code&gt;blocked-notice-logextract&lt;/code&gt;] 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 &lt;code dir=ltr&gt;&lt;nowiki&gt;[ ] |&lt;/nowiki&gt;&lt;/code&gt; after the fragment identifier (&lt;code&gt;&lt;nowiki&gt;#&lt;/nowiki&gt;&lt;/code&gt;). 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:|&lt;code&gt;q:ms:&lt;/code&gt;]]) [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 &lt;code&gt;[[mw:Special:MyLanguage/Extension:Scribunto/Lua reference manual#mw.title.newBatch|mw.title.newBatch]]&lt;/code&gt; 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 &amp; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2025/40|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2025-W40&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 20:54, 29 September 2025 (UTC)
&lt;!-- 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&amp;oldid=29355230 --&gt;

== Wikipedia translation of the week: 2025-41 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Majed Abu Maraheel]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----

&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=29341788 --&gt;

== Tech News: 2025-41 ==

&lt;section begin=&quot;technews-2025-W41&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &lt;code&gt;en.wikipedia.org&lt;/code&gt;), instead of via a redirect to an &quot;m&quot; domain (like &lt;code&gt;en.m.wikipedia.org&lt;/code&gt;). This change improves performance. This week it will be enabled on Wikipedias. The existing mobile URLs and the &quot;Desktop view&quot; 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]], &lt;code dir=ltr&gt;creationdate:&lt;/code&gt; and &lt;code dir=ltr&gt;lasteditdate:&lt;/code&gt;, 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. &lt;code dir=ltr&gt;&gt;2024&lt;/code&gt;) and relative dates (e.g. &lt;code dir=ltr&gt;today-1d&lt;/code&gt;), 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 &lt;code dir=ltr&gt;rev_sha1&lt;/code&gt; in the revision database table is being removed in favor of &lt;code dir=ltr&gt;content_sha1&lt;/code&gt; 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 &lt;code&gt;rest.php&lt;/code&gt; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2025/41|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2025-W41&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 17:24, 6 October 2025 (UTC)
&lt;!-- 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&amp;oldid=29400897 --&gt;

== Wikipedia translation of the week: 2025-42 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Abortion in Eritrea]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----

&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=29341788 --&gt;

== Tech News: 2025-42 ==

&lt;section begin=&quot;technews-2025-W42&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2025/42|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2025-W42&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 19:00, 13 October 2025 (UTC)
&lt;!-- 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&amp;oldid=29434481 --&gt;

== Wikipedia translation of the week: 2025-43 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Liberation of Auschwitz concentration camp]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Auschwitz Liberated January 1945.jpg|300px|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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' &quot;Final Solution&quot; 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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=29452019 --&gt;

== Tech News: 2025-43 ==

&lt;section begin=&quot;technews-2025-W43&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &lt;code dir=ltr&gt;&lt;nowiki&gt;rest.php&lt;/nowiki&gt;&lt;/code&gt; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2025/43|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2025-W43&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 19:37, 20 October 2025 (UTC)
&lt;!-- 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&amp;oldid=29478670 --&gt;

== Wikipedia translation of the week: 2025-44 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Black Diaries]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----

&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=29487357 --&gt;

== Tech News: 2025-44 ==

&lt;section begin=&quot;technews-2025-W44&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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&amp;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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2025/44|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2025-W44&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 19:32, 27 October 2025 (UTC)
&lt;!-- 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&amp;oldid=29513638 --&gt;
|}

== Wikipedia translation of the week: 2025-45 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Consolations (Liszt)]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Franz Liszt - Consolation No. 3, Lento placido.ogg|center|300px|]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=29558323 --&gt;

== Tech News: 2025-45 ==

&lt;section begin=&quot;technews-2025-W45&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;{{int:discussiontools-preference-autotopicsub}}&quot; [[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 &quot;{{int:Skin-action-addsection}}&quot; or &quot;{{int:Discussiontools-replybutton}}&quot; 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 &quot;Get shortened URL&quot;. There are 30 wikis that also install an older &quot;ShortUrl&quot; extension. The old extension will soon be removed. This means &lt;code&gt;/s/&lt;/code&gt; URLs will not be advertised under article titles via HTML &lt;code dir=ltr&gt;class=&quot;title-shortlink&quot;&lt;/code&gt;. The &lt;code&gt;/s/&lt;/code&gt; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2025/45|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2025-W45&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 19:35, 3 November 2025 (UTC)
&lt;!-- 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&amp;oldid=29552512 --&gt;

== Wikipedia translation of the week: 2025-46 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Marine coastal ecosystem]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Vegetation and fauna processes controlling benthic biogeochemical fluxes.jpg|center|300px|]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=29584005 --&gt;

== Tech News: 2025-46 ==

&lt;section begin=&quot;technews-2025-W46&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;{{int:discussiontools-preference-visualenhancements}}&quot;. [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 &quot;{{int:showpreview}}&quot; or &quot;{{int:showdiff}}&quot; 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 &quot;Image browsing&quot; 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 &lt;code&gt;&lt;nowiki&gt;https://meta.wikimedia.org&lt;/nowiki&gt;&lt;/code&gt;. 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 &lt;code&gt;&lt;user id&gt;&lt;/code&gt; to &lt;code dir=ltr style=&quot;white-space:nowrap&quot;&gt;mw:&lt;identity type&gt;:&lt;user id&gt;&lt;/code&gt;, where &lt;code&gt;&lt;identity type&gt;&lt;/code&gt; is typically &lt;code dir=ltr&gt;CentralAuth:&lt;/code&gt;&lt;!-- not a typo --&gt; (for [[m:Special:MyLanguage/Help:Unified login|SUL wikis]]) or &lt;code dir=ltr style=&quot;white-space:nowrap&quot;&gt;local:&lt;wiki id&gt;&lt;/code&gt; (for other wikis). This is to avoid conflicts between different user ID types, and to make OAuth 2 access tokens and the &lt;code&gt;sessionJwt&lt;/code&gt; 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 &lt;code&gt;&lt;nowiki&gt;$9&lt;/nowiki&gt;&lt;/code&gt; or emailing other users &lt;code&gt;&lt;nowiki&gt;$&lt;/nowiki&gt;&lt;nowiki&gt;10&lt;/nowiki&gt;&lt;/code&gt;. [https://phabricator.wikimedia.org/T285612]
* A &lt;code&gt;REL1_45&lt;/code&gt; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2025/46|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2025-W46&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 20:38, 10 November 2025 (UTC)
&lt;!-- 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&amp;oldid=29606150 --&gt;

== Wikipedia translation of the week: 2025-47 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Elephant communication]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Three elephant's curly kisses.jpg|center|300px|]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''Elephants communicate''' via touching, visual displays, vocalisations, seismic vibrations, and semiochemicals. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=29627457 --&gt;

== Tech News: 2025-47 ==

&lt;section begin=&quot;technews-2025-W47&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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:|&lt;code&gt;s:min:&lt;/code&gt;]]) [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 ''&quot;Report Visual Bug&quot;'' 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 &lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;hackathon@wikimedia.org&lt;/bdi&gt;.

'''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2025/47|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2025-W47&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 17:27, 17 November 2025 (UTC)
&lt;!-- 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&amp;oldid=29627455 --&gt;

== Wikipedia translation of the week: 2025-48 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Animal-made art]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Painting Queen 1024x768.png|center|300px|]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=29627457 --&gt;

== Tech News: 2025-48 ==

&lt;section begin=&quot;technews-2025-W48&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;DWIM&quot; (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 ''&lt;span lang=&quot;und&quot; dir=&quot;ltr&quot;&gt;cxfcnmt&lt;/span&gt;'' on Russian Wikipedia will now add suggestions for ''&lt;span lang=&quot;ru&quot; dir=&quot;ltr&quot;&gt;счастье&lt;/span&gt;'' (&quot;happiness&quot;) 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 &quot;{{int:codemirror-beta-feature-title}}&quot; [[Special:Preferences#mw-prefsection-betafeatures|beta feature]] will have syntax highlighting available in [[mw:Special:MyLanguage/Help:DiscussionTools|DiscussionTools]]. This requires that the &quot;{{int:discussiontools-preference-sourcemodetoolbar}}&quot; 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 &lt;code dir=ltr&gt;format=xml'''&amp;xlst={stylesheet}'''&lt;/code&gt; 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 (&lt;span dir=ltr&gt;&lt;nowiki&gt;https://query.wikidata.org/&lt;/nowiki&gt;&lt;/span&gt; - Main graph or &lt;span dir=ltr&gt;&lt;nowiki&gt;https://query-scholarly.wikidata.org/&lt;/nowiki&gt;&lt;/span&gt; - 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2025/48|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2025-W48&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 15:57, 24 November 2025 (UTC)
&lt;!-- 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&amp;oldid=29702226 --&gt;

== Wikipedia translation of the week: 2025-49 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Halachic state]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----

&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
The term &quot;'''halachic state'''&quot; (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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=29719355 --&gt;

== Tech News: 2025-49 ==

&lt;section begin=&quot;technews-2025-W49&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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:|&lt;code&gt;w:tok:&lt;/code&gt;]]) [https://phabricator.wikimedia.org/T404457]
** a {{int:project-localized-name-group-wikiquote}} in [[d:Q33655|Nigerian Pidgin]] ([[q:pcm:|&lt;code&gt;q:pcm:&lt;/code&gt;]]) [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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2025/49|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2025-W49&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 18:58, 1 December 2025 (UTC)
&lt;!-- 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&amp;oldid=29732328 --&gt;

== Wikipedia translation of the week: 2025-50 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:ru:Сто лошадей]]'''&lt;br /&gt; &lt;small&gt;''([[:en:One Hundred Horses]])''&lt;/small&gt; &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:A_Hundred_Steeds.jpg|300px|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''''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.  

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=29719355 --&gt;

== Tech News: 2025-50 ==

&lt;section begin=&quot;technews-2025-W50&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &lt;bdi lang=&quot;ka-Latn&quot; dir=&quot;ltr&quot;&gt;''bedniereba''&lt;/bdi&gt; or &lt;bdi lang=&quot;ka-Cyrl&quot; dir=&quot;ltr&quot;&gt;''бедниереба''&lt;/bdi&gt; will now suggest the existing article about &lt;bdi lang=&quot;ka&quot; dir=&quot;ltr&quot;&gt;ბედნიერება&lt;/bdi&gt; (&quot;happiness&quot;). 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 &quot;Edit full page&quot; 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 &quot;{{int:codemirror-beta-feature-title}}&quot; [[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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2025/50|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2025-W50&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 17:46, 8 December 2025 (UTC)
&lt;!-- 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&amp;oldid=29738112 --&gt;

== Wikipedia translation of the week: 2025-51 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:First Universal Races Congress]]'''&lt;br /&gt; &lt;small&gt;''([[:fr:Premier Congrès universel des races]])''&lt;/small&gt; &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Universal Races Congress seated outside the entrance to the Imperial Institute, London, 1911.jpg|300px|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=29779168 --&gt;

== Tech News: 2025-51 ==

&lt;section begin=&quot;technews-2025-W51&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &lt;code dir=ltr&gt;externallinks&lt;/code&gt; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2025/51|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2025-W51&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 19:03, 15 December 2025 (UTC)
&lt;!-- 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&amp;oldid=29796010 --&gt;

== Wikipedia translation of the week: 2025-52 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2025 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Pin Malakul]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Pin Malakul, January 1922.jpg|300px|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
-[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=29802495 --&gt;

== Tech News: 2025-52 ==

&lt;section begin=&quot;technews-2025-W52&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;First Steps&quot; 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 &lt;code dir=ltr&gt;data-mw=&quot;interface&quot;&lt;/code&gt; to distinguish from wiki content. The attribute has been replaced with &lt;code dir=ltr&gt;data-mw-interface=&quot;&quot;&lt;/code&gt;, to avoid potential conflicts with other &lt;code dir=ltr&gt;data-mw&lt;/code&gt; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2025/52|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2025-W52&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 21:46, 22 December 2025 (UTC)
&lt;!-- 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&amp;oldid=29831856 --&gt;

== Wikipedia translation of the week: 2026-01 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:The Morning of the Magicians]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Le Matin des magiciens, couverture.jpg|300px|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=29802495 --&gt;

== Wikipedia translation of the week: 2026-02 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Somaliland War of Independence]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Somaliland, fighters of the Somali National Movement (SNM), 1980s.jpg|300px|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=29871911 --&gt;

== Wikipedia translation of the week: 2026-03 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:it:Pietro Lauro]]'''&lt;br /&gt; &lt;small&gt;''([[:en:Pietro Lauro]])''&lt;/small&gt; &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Master I.A.V.F., Pietro Lauro, born 1508, Modenese Poet and Scholar (obverse), 1555, NGA 45072.jpg|300px|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=29894468 --&gt;

== Tech News: 2026-03 ==

&lt;section begin=&quot;technews-2026-W03&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &amp; 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 &quot;map&quot; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2026/03|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2026-W03&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 19:34, 12 January 2026 (UTC)
&lt;!-- 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&amp;oldid=29907192 --&gt;

== Wikipedia translation of the week: 2026-04 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:it:Volto di Palazzo Vecchio]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Piazza della signoria angolo via della ninna, palazzo vecchio, cantonata con testa scolpita 02.jpg|300px|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=29945240 --&gt;

== Tech News: 2026-04 ==

&lt;section begin=&quot;technews-2026-W04&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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.: &lt;code dir=ltr&gt;https://en.wikipedia.org/api/rest_v1/&lt;/code&gt;) 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2026/04|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2026-W04&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 20:30, 19 January 2026 (UTC)
&lt;!-- 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&amp;oldid=29943403 --&gt;

== Wikipedia translation of the week: 2026-05 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:it:Raffaello Kobayashi]]'''&lt;br /&gt; &lt;small&gt;''([[:en:Raffaello Kobayashi]])''&lt;/small&gt; &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----

&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=29945240 --&gt;

== Tech News: 2026-05 ==

&lt;section begin=&quot;technews-2026-W05&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;prevent this user from editing their own talk page&quot; 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, &lt;code&gt;account_type&lt;/code&gt;, has been added to provide a reliable way to determine the account type being created in the &lt;code&gt;createaccount&lt;/code&gt; and &lt;code&gt;autocreateaccount&lt;/code&gt; actions. As part of this change, the variable &lt;code&gt;accountname&lt;/code&gt; has been renamed to &lt;code&gt;account_name&lt;/code&gt;, and &lt;code&gt;accountname&lt;/code&gt; 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 &lt;code dir=ltr&gt;&lt;nowiki&gt;upload.wikimedia.org/…&lt;/nowiki&gt;&lt;/code&gt; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2026/05|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2026-W05&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 21:18, 26 January 2026 (UTC)
&lt;!-- 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&amp;oldid=29969530 --&gt;

== Wikipedia translation of the week: 2026-06 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Censorship in the Czech Republic]]'''&lt;br /&gt; &lt;small&gt;''([[:cs:Cenzura v Česku]])''&lt;/small&gt; &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----

&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=29945240 --&gt;

== Tech News: 2026-06 ==

&lt;section begin=&quot;technews-2026-W06&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;{{int:pageinfo-toolboxlink}}&quot; 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 &amp; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2026/06|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2026-W06&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 17:44, 2 February 2026 (UTC)
&lt;!-- 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&amp;oldid=30000986 --&gt;

== Wikipedia translation of the week: 2026-07 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Petites Heures of Jean de France, Duc de Berry]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Jacquemart de Hesdin 002.jpg|300px|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=29945240 --&gt;

== Tech News: 2026-07 ==

&lt;section begin=&quot;technews-2026-W07&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;magic links&quot; 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]] &lt;code dir=ltr&gt;&lt;nowiki&gt;{{#isbn}}&lt;/nowiki&gt;&lt;/code&gt; 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:|&lt;code&gt;w:kaj:&lt;/code&gt;]]) [https://phabricator.wikimedia.org/T413283]
** a {{int:project-localized-name-group-wikipedia}} in [[d:Q1186896|Nawat]] ([[w:ppl:|&lt;code&gt;w:ppl:&lt;/code&gt;]]) [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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2026/07|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2026-W07&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 23:31, 9 February 2026 (UTC)
&lt;!-- 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&amp;oldid=30026671 --&gt;

== Wikipedia translation of the week: 2026-08 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Lysmata grabhami]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Lysmata grabhami1.jpg|300px|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=29945240 --&gt;

== Tech News: 2026-08 ==

&lt;section begin=&quot;technews-2026-W08&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &lt;code dir=&quot;ltr&quot;&gt;#siteNotice { display: none; }&lt;/code&gt; 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 &quot;view new changes since…&quot; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2026/08|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2026-W08&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 19:17, 16 February 2026 (UTC)
&lt;!-- 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&amp;oldid=30086330 --&gt;

== Wikipedia translation of the week: 2026-09 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:it:Elefante di Cremona]]'''&lt;br /&gt; &lt;small&gt;''([[:de:Elefant von Cremona]])&amp;#32;([[:eo:Elefanto de Cremona]])''&lt;/small&gt; &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Matthew Paris Elephant from Parker MS 16 fol 151v.jpg|300px|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=30097839 --&gt;

== Tech News: 2026-09 ==

&lt;section begin=&quot;technews-2026-W09&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;Edit full page&quot; 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 &quot;beta&quot; 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 &lt;code dir=ltr&gt;MediaWiki:skin-theme-description&lt;/code&gt; and &lt;code dir=ltr&gt;MediaWiki:Vector-night-mode-beta-tag&lt;/code&gt; 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]], &lt;code dir=ltr&gt;ext.globalwatchlist.rebuild&lt;/code&gt;, 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2026/09|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2026-W09&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 19:04, 23 February 2026 (UTC)
&lt;!-- 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&amp;oldid=30119102 --&gt;

== Wikipedia translation of the week: 2026-10 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Treaty of the Danish West Indies]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[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]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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 &quot;not object to the Danish Government extending their political and economic interests to the whole of Greenland&quot;. It is one of the most recent permanent expansions of United States territory.

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=30097839 --&gt;

== Tech News: 2026-10 ==

&lt;section begin=&quot;technews-2026-W10&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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&amp;group=ext-visualeditor-ve-mw-editcheck&amp;filter=&amp;optional=1&amp;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 &lt;code dir=ltr&gt;uselang=&lt;/code&gt; 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 &amp; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2026/10|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2026-W10&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 17:52, 2 March 2026 (UTC)
&lt;!-- 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&amp;oldid=30137798 --&gt;

== Wikipedia translation of the week: 2026-11 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Steens Mountain]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Steens Mountain near Andrews, Oregon.jpg|300px|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=30097839 --&gt;

== Tech News: 2026-11 ==

&lt;section begin=&quot;technews-2026-W11&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2026/11|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2026-W11&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 18:53, 9 March 2026 (UTC)
&lt;!-- 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&amp;oldid=30213008 --&gt;

== Wikipedia translation of the week: 2026-12 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Casque (anatomy)]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Great hornbill (Buceros bicornis) Photograph by Shantanu Kuveskar.jpg|300px|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=30245038 --&gt;

== Tech News: 2026-12 ==

&lt;section begin=&quot;technews-2026-W12&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &lt;code dir=ltr&gt;ext.CodeMirror&lt;/code&gt; or &lt;code dir=ltr&gt;ext.CodeMirror.lib&lt;/code&gt; modules from gadgets and user scripts was deprecated in July 2025. The use of the &lt;code dir=ltr&gt;ext.CodeMirror.switch&lt;/code&gt; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2026/12|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2026-W12&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 19:36, 16 March 2026 (UTC)
&lt;!-- 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&amp;oldid=30260505 --&gt;

== Wikipedia translation of the week: 2026-13 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Etruscan sculpture]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Frontone A del grande tempio di luni con concilio degli dei, 175-150 ac. ca. 01.JPG|300px|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=30245038 --&gt;

== Tech News: 2026-13 ==

&lt;section begin=&quot;technews-2026-W13&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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|&quot;Log in with passkey&quot; 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&amp;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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2026/13|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2026-W13&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 16:51, 23 March 2026 (UTC)
&lt;!-- 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&amp;oldid=30268305 --&gt;

== Wikipedia translation of the week: 2026-14 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Pulse (nightclub)]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Orlando FL Pulse Nightclub01.jpg|300px|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=30306870 --&gt;

== Tech News: 2026-14 ==

&lt;section begin=&quot;technews-2026-W14&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;Edit&quot;. 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2026/14|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2026-W14&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 19:26, 30 March 2026 (UTC)
&lt;!-- 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&amp;oldid=30329462 --&gt;

== Wikipedia translation of the week: 2026-15 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Tofana di Rozes]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Tofana di Rozes 04.jpg|300px|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=30306870 --&gt;

== Tech News: 2026-15 ==

&lt;section begin=&quot;technews-2026-W15&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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, &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;format=php&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt;, 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 &quot;WP&quot; for the &quot;Project&quot; (&quot;Wikipedia&quot;) 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2026/15|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2026-W15&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 16:19, 6 April 2026 (UTC)
&lt;!-- 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&amp;oldid=30362761 --&gt;

== Wikipedia translation of the week: 2026-16 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Very-low-calorie diet]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Green smoothie (8222465502).jpg|300px|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=30306870 --&gt;

== Tech News: 2026-16 ==

&lt;section begin=&quot;technews-2026-W16&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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]] (&lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;action=query&amp;meta=notifications&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt;) 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2026/16|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2026-W16&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 15:19, 13 April 2026 (UTC)
&lt;!-- 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&amp;oldid=30380527 --&gt;

== Wikipedia translation of the week: 2026-17 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Chromodoris willani]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Babosa de mar (Chromodoris willani), Anilao, Filipinas, 2023-08-24, DD 34.jpg|300px|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''''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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=30430366 --&gt;

== Tech News: 2026-17 ==

&lt;section begin=&quot;technews-2026-W17&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;Liquid Glass&quot; 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 &lt;code&gt;mirrors.wikimedia.org&lt;/code&gt; 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 &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;image&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; and &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;oldimage&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; table will be removed from [[wikitech:Help:Wiki Replicas|wikireplicas]]. If your tools or queries access &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;image&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; or &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;oldimage&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; directly, please update them to use the &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;file&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; and &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;filerevision&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; 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&amp;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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2026/17|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2026-W17&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 15:01, 20 April 2026 (UTC)
&lt;!-- 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&amp;oldid=30432763 --&gt;

== Wikipedia translation of the week: 2026-18 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Platypus venom]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Platypus spur.JPG|300px|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=30449041 --&gt;

== Tech News: 2026-18 ==

&lt;section begin=&quot;technews-2026-W18&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;automatically enable most beta features&quot; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2026/18|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2026-W18&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 18:06, 27 April 2026 (UTC)
&lt;!-- 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&amp;oldid=30458046 --&gt;

== Wikipedia translation of the week: 2026-19 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Kuwait National Assembly Building]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Kuwait City Arabian Gulf Street 10.jpg|300px|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
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. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[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)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=30464799 --&gt;

== Tech News: 2026-19 ==

&lt;section begin=&quot;technews-2026-W19&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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 &quot;Translate to English&quot; 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 &quot;changes 3&quot; instead of &quot;3 changes&quot; 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2026/19|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2026-W19&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 20:44, 4 May 2026 (UTC)
&lt;!-- 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&amp;oldid=30498077 --&gt;

== Wikipedia translation of the week: 2026-20 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Macau National Security Law]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Lei relative à defesa da segurança do Estado projecto.JPG|center|300px]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
The '''Macau National Security Law''' is a law in Macau which prohibits and punishes acts of treason, secession, and subversion against the Central government, as well as preparative acts leading to any of the three acts. Taken into effect on 3 March 2009, the purpose of the law is to fulfil Article 23 of the Macau Basic Law, the de facto constitution of the Macau Special Administration Region. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:53, 11 May 2026 (UTC)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=30513945 --&gt;

== Tech News: 2026-20 ==

&lt;section begin=&quot;technews-2026-W20&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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/20|Translations]] are available.

'''Weekly highlight'''
* Community Tech has published [[m:Special:MyLanguage/Community Wishlist/How to write a good wish|new guidance]] explaining how wishes on Community Wishlist are triaged and prioritized. The documentation is intended to help contributors write stronger proposals by clarifying the factors that influence prioritization decisions. Beyond vote counts, the guidance highlights considerations such as potential impact on the community when determining which wishes move forward.

'''Updates for editors'''
* The Reader Growth team is launching an experiment to test a new [[mw:Special:MyLanguage/Readers/Reader_Growth/Share_Card|Share Card feature]] that allows readers to create visually engaging cards from Wikipedia articles or selected article sections and share them online, with each card linking back to the original article to help expand readership and article discovery. The mobile-only A/B test will be available to a portion of readers on Arabic, Chinese, French, Vietnamese, and English Wikipedia to better understand reading and sharing habits, and is scheduled to begin the week of May 18 and run for four weeks.
* The Android and iOS Wikipedia apps recently released the [[mw:Special:MyLanguage/Wikimedia_Apps/Team/25th_Birthday_Reading_Challenge|25-day reading challenge]] into Beta, as part of efforts to drive reader engagement by encouraging users to complete reading milestones. To track their reading streak during the challenge, App users can add a widget featuring Baby Globe to their home screen. The challenge officially begins May 11.
* [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:17}} community-submitted {{PLURAL:17|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, an issue where the global preference for enabling syntax highlighting in wikitext could unexpectedly disable itself after being turned on, has now been fixed. [https://phabricator.wikimedia.org/T425286]

'''Updates for technical contributors'''
* [[File:Octicons-tools.svg|12px|link=|alt=|Advanced item]] The ResourceLoader module &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;mediawiki.ui.input&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt;, deprecated since [[m:Special:MyLanguage/Tech/News/2023/39|September 2023]], will be removed this week. There is a [[mw:Special:MyLanguage/Codex/Migrating_from_MediaWiki_UI|guide for migrating from MediaWiki UI to Codex]] for any tools that use it. [https://phabricator.wikimedia.org/T420125]
* [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.47/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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2026/20|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2026-W20&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 19:21, 11 May 2026 (UTC)
&lt;!-- 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&amp;oldid=30524429 --&gt;

== Tech News: 2026-21 ==

&lt;section begin=&quot;technews-2026-W21&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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/21|Translations]] are available.

'''Weekly highlight'''
* The Abstract Wikipedia team has identified five potential pilot wikis to assess their interest in adopting abstract articles on their wikis. The pilots are Malayalam, Bengali, Dagbani, Arabic, and Indonesian Wikipedia. The feedback period will be open until May 22. If your community is interested in becoming a pilot, [[m:Talk:Abstract Wikipedia|let us know on Meta]].

'''Updates for editors'''
* An experiment to show [[mw:Special:MyLanguage/Readers/Reader Experience/Reading lists|Reading Lists]] to logged-out readers on mobile web will launch on May 18 across German, Spanish, Italian, Portuguese, Polish, Dutch, Turkish, and Urdu Wikipedias, and will run for one month. The effort supports broader goals of helping readers save and organize articles for later reading, while encouraging habits that could lead to future Wikipedia contributions.
* To support a bookmark button in the Reading List beta feature, the &quot;Tools &gt; Action&quot; menu has been updated to display icons, including the watch star indicator that helps editors identify temporarily watched articles. The icons now also match those used on mobile, improving consistency across platforms. The change is currently limited to the actions menu and mainly affects editors with privileged user rights. [https://phabricator.wikimedia.org/T426008]
* [[mw:Special:MyLanguage/VisualEditor/Suggestion Mode|Suggestion Mode]] was released as an [[w:en:A/B test|A/B test]] for newcomer editors on the mobile website at [[phab:T421189|~15 Wikipedias]]. The experiment will measure the impact that Suggestion Mode has on the proportion of newcomer mobile web edit sessions that result in constructive (un-reverted) article edits. The experiment will also evaluate the feature's impact on editor retention, and monitor changes in revert and block rates.
* [[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, an issue in the Wikipedia Android app where images could sometimes fail to load after opening a recommended reading list notification, has now been fixed. [https://phabricator.wikimedia.org/T418231]

'''Updates for technical contributors'''
* The [[mw:Special:MyLanguage/Wikidata Platform|Wikidata Platform team]] has published its [[d:Special:MyLanguage/Wikidata:SPARQL query service/WDQS backend update/Backend Replacement|backend replacement recommendation]] and accompanying [[wikitech:Wikidata Query Service/WDQS Architecture re-design|technical architecture]] for the migration of the Wikidata Query Service (WDQS) away from Blazegraph. Feedback is invited until May 25th 2026, especially on potential gaps and impacts on advanced use cases. Wikidata community members and WDQS users are also encouraged to help identify high-impact tools and workflows that may need attention on [[d:Wikidata:SPARQL query service/WDQS backend update/High-Impact Use Cases|this page]]. Feedback can be shared on the [[d:Wikidata talk:SPARQL query service/WDQS backend update|Migration talk page]] or during the [[d:Special:MyLanguage/Wikidata:Blazegraph Migration Office Hours|next office hour]]. See the [[d:Special:MyLanguage/Wikidata:Wikidata Platform team/Newsletter|WDP team newsletter]] for more details.
* [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.47/wmf.3|MediaWiki]]

'''In depth'''

* On English, French, Japanese, and a few other Wikipedias, there was a [[diffblog:2025/09/02/better-detecting-bots-and-replacing-our-captcha/|trial of hCaptcha]], a third-party bot detection service. The trial showed that hCaptcha effectively detects and deters some bad-faith automated activity, on its own and by giving [[w:en:Wikipedia:Village pump (technical)/Archive 225#Introducing SuggestedInvestigations|checkusers and stewards]] signals to look into. Because the results were positive, hCaptcha will be rolled out across all wikis over the next few weeks. [[mw:Special:MyLanguage/Product Safety and Integrity/Anti-abuse signals/hCaptcha|See the hCaptcha project page]] for technical information about the implementation and privacy protections. [[diffblog:2026/05/04/better-detecting-bots-and-replacing-our-captcha-part-2/|Learn more]].
* The latest Community Tech update is now available, with progress across several Community Wishlist initiatives, including Reading Lists expansion from the mobile app to the website, new language support for &quot;Who Wrote That&quot; and the Personal Dashboard, improvements to 3D rendering and Charts, and upcoming work on talk page sorting, audio playback, and editing workflows. The update also shares current priorities, wishlist status trends, and opportunities for community feedback on future focus areas and the Wikimedia Foundation’s 2026–2027 Annual Plan. [[m:Special:MyLanguage/Community Wishlist/Updates#May 13, 2026: Latest updates from the Community Tech team|Read the full newsletter for details]].

'''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2026/21|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2026-W21&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 20:22, 18 May 2026 (UTC)
&lt;!-- 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&amp;oldid=30539262 --&gt;

== Wikipedia translation of the week: 2026-21 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Stela of the cactus bearer]]'''&lt;br /&gt; &lt;small&gt;''([[:es:Estela del portador del cactus]])&amp;#32;([[:ca:Estela del portador del cactus]])''&lt;/small&gt; &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Estela Wachumero en Chavin.jpg|center|300px]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
The '''stela of the cactus bearer''' is a monolith or stele of a single piece of granite, belonging to the Chavín culture of ancient Peru, which remains in its original location on the northwest side of the circular plaza at the archaeological site known as the ceremonial center of Chavín de Huántar in the Ancash region of Peru. It was discovered during the 1972 excavation season by Peruvian archaeologist Luis Guillermo Lumbreras. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 04:05, 21 May 2026 (UTC)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=30529698 --&gt;

== Wikipedia translation of the week: 2026-22 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Griffith Hughes]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----

&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
The Reverend '''Griffith Hughes''' (1707 – c.1758), FRS, was a Welsh naturalist, clergyman, and author. Hughes wrote The Natural History of Barbados, which included the first description of the grapefruit (also known as &quot;The Forbidden Fruit&quot;). His work was praised by Linnaeus, but it has also been considered a &quot;scientific fraud&quot;. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:32, 25 May 2026 (UTC)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=30529698 --&gt;

== Tech News: 2026-22 ==

&lt;section begin=&quot;technews-2026-W22&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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/22|Translations]] are available.

'''Weekly highlight'''
* Following a [[mw:Special:MyLanguage/Contributors/Account Creation Experiments#LOWM|successful account creation experiment]], an improved logged-out edit warning message will be deployed to all Wikimedia wikis in the first week of June. The change will only affect logged-out users on mobile web who open an editing session. The updated experience is designed to encourage account creation more clearly, while still allowing users to edit with temporary accounts. Results from the experiment showed a significant increase in account creation, with a 27% relative lift among users shown the updated message. As expected, as more people funnel into account creation, temporary accounts decreased by a relative 16%. The experiment did not show any significant changes in constructive edit rates or other monitored contributor metrics. [https://phabricator.wikimedia.org/T424595] 

'''Updates for editors'''
* 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. Members of these groups will be unable to disable the 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 next few weeks, users without 2FA will be removed from these groups. Notably, this applies to bureaucrats. See the linked tasks for deployment schedules. [https://phabricator.wikimedia.org/T423119][https://phabricator.wikimedia.org/T423120]
* [[m:Special:MyLanguage/WMDE Technical Wishes|WMDE Technical Wishes]] will run an [[w:en:A/B testing|A/B test]] on [[:phab:T415904|10 wikis]], testing [[m:WMDE Technical Wishes/References/Reference Previews|potential improvements for Reference Previews]]. The experiment will run for ~2 weeks at the end of May / beginning of June and will affect 10% of desktop readers on the participating wikis.
* After two successful experiments, the Reader Growth team is rolling out an [[mw:Special:MyLanguage/Readers/Reader Growth/Image Browsing|Image Browsing]] beta feature for all Wikipedias on mobile on May 25. This means that anyone who has all beta features on by default will start to see this feature, and others can check the box to turn it on in their preferences. The beta feature will include a carousel of all an article's images at the top of the article, with controls for editors to [[mw:Readers/Reader_Growth/Image_Browsing#Phase_2.1_beta_feature|exclude images from the article's carousel or to exclude an article from the feature entirely]].
* [[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, three dimensional STL files were being rendered incorrectly by the media viewer 3D extension which is now fixed. [https://phabricator.wikimedia.org/T416723]

'''Updates for technical contributors'''
* The legacy CSS classes &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;tleft&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; and &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;tright&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; have been replaced with &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;floatleft&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; and &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;floatright&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; as the former do not work consistently across all MediaWiki platforms, notably mobile web and mobile apps. Projects relying on these classes are encouraged to review related usage and plan for migration. Please note that &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;floatleft&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; and &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;floatright&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; may also be deprecated in future, although there are currently no plans to do so. [[phab:T426452|Read more]].
* [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.47/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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2026/22|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2026-W22&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 21:52, 25 May 2026 (UTC)
&lt;!-- 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&amp;oldid=30584502 --&gt;

== Wikipedia translation of the week: 2026-23 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Umuganda]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Umuganda&quot;Rwandan community work&quot;.jpg|300px|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''Umuganda''' is a national holiday in Rwanda taking place on the last Saturday of every month for mandatory nationwide community service from 08:00 to 11:00. Participation in Umuganda is required by law; failure to participate can result in a fine.

The program was most recently re-established under President Paul Kagame in 2009, having resulted in a notable improvement in the cleanliness of Rwanda. Also, there are other informal Umuganda day activities that occur in the middle of the month. These activities are initiated by either society or the government. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:55, 1 June 2026 (UTC)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=30529698 --&gt;

== Tech News: 2026-23 ==

&lt;section begin=&quot;technews-2026-W23&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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/23|Translations]] are available.

'''Updates for editors'''
* The [[mw:Special:MyLanguage/Readers/Reader Experience|Reader Experience team]] is conducting an experiment to show the [[mw:Special:MyLanguage/Readers/Reader Experience/Reading lists|reading lists]] feature, which is still in development, to logged-out mobile readers to test whether it encourages account creation at a higher rate compared to the watchstar button. The [[mw:Special:MyLanguage/Readers/Reader Experience/Reading lists#Experiment timeline|experiment]] was launched on May 18th on German, Spanish, Italian, Portuguese, Polish, Dutch, Turkish, and Urdu wikis, and it will run for a month.
* The Wikimedia Apps team released [[mw:Special:MyLanguage/Wikimedia Apps/Team/Explore Feed Refresh/Phase 1|Phase 1]] of the redesigned Home Feed to the Android Beta app. The new Home Feed includes a refreshed &quot;Community&quot; tab and a personalized &quot;For You&quot; tab featuring daily updated reading recommendations. The redesign is part of a broader effort to improve content discovery and create more engaging learning experiences in the Wikipedia apps.
* [[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, an issue where images could fail to load for some suggested edits on [[w:Special:Homepage|Special:Homepage]], leaving the thumbnail stuck in a loading state, has now been fixed. [https://phabricator.wikimedia.org/T424048]

'''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.47/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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2026/23|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2026-W23&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 21:09, 1 June 2026 (UTC)
&lt;!-- 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&amp;oldid=30613639 --&gt;

== Wikipedia translation of the week: 2026-24 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:it:Juryeonggu]]'''&lt;br /&gt; &lt;small&gt;''([[:kr:주령구]])&amp;#32;([[:ja:酒令具]])''&lt;/small&gt; &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:주령구의 발굴 당시 사진.png|300px|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
Il '''Juryeonggu''' (주령구?, 酒令具?, JuryeongguLR, ChuryŏngguMR) è un dado a 14 facce, risalente al periodo del Silla unificato (668-935 d.C.), ritrovato nel 1975 dopo alcuni scavi occorsi presso il Donggung e lo stagno Wolji di Gyeongju, in Corea del Sud. Le facce del dado mostravano inscrizioni recanti varie penalità o sfide, legate ad un gioco di bevute, dimostrando l'importanza dell'alcool e la raffinatezza con cui la sua assunzione veniva celebrata.

L'artefatto originale è andato perduto, incendiato in un maldestro tentativo di preservazione: oggi ne esistono delle repliche, disponibili anche commercialmente. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:20, 8 June 2026 (UTC)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=30622359 --&gt;

== Tech News: 2026-24 ==

&lt;section begin=&quot;technews-2026-W24&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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/24|Translations]] are available.

'''Weekly highlight'''
* Wikimedia Enterprise has increased the free usage limits for its API offerings. The monthly request limit for the On-demand API has increased from 5,000 to 50,000 requests, while the Snapshot API limit has increased from 15 to 30 requests per month. In addition, Structured Contents snapshots are now available for free accounts. These changes expand access to Wikimedia Enterprise data for developers, researchers, and organizations using Wikimedia content. [https://enterprise.wikimedia.com/blog/enhanced-free-api]

'''Updates for editors'''
* The [[mw:Special:MyLanguage/Wikimedia_Apps/Team/Explore Feed Refresh/Phase 1|refreshed Explore Feed]], now called the Home Feed, is rolling out to 50% of users of the Wikipedia Android app. The Home Feed helps readers discover relevant content through two new tabs: ''Community'' and ''For You''. The Community tab provides a scrollable feed of curated content and updates from the broader Wikimedia community and movement, while the ''For You'' tab offers a full-screen, swipeable experience that shows content tailored to a user's interests. The redesign is part of a broader effort to improve discovery and enhance the learning experience in the Wikipedia app.
* The [[mw:Special:MyLanguage/Wikimedia Apps/Team/iOS/&quot;Which came first?&quot; Game|Which came first?]] daily trivia game is now available in the beta version of the Wikipedia iOS app in English, German, French, Portuguese, Russian, Spanish, Arabic, Chinese, and Turkish. The game uses historical events from Wikipedia's &quot;On This Day&quot; content and challenges readers to guess which of two events happened first. The game was previously released on Android. Communities interested in making the game available in their languages can [[mw:Special:MyLanguage/Wikimedia_Apps/Team/Games#Game availability by language|read the instructions and requirements]].
* [[m:Special:MyLanguage/WMDE Technical Wishes/Sub-referencing|Sub-referencing]], a new MediaWiki feature that allows editors to reuse references with different details, will begin rolling out to Wikimedia wikis following a successful pilot phase. Deployment will start on 8 June for most [[wikitech:Deployments/Train#Wednesday|Group 1 wikis]] and French Wikipedia, with additional Wikipedia language editions receiving the feature over the coming months. Communities are encouraged to prepare by checking for [https://translatewiki.net/w/i.php?title=Special%3ATranslate&amp;group=ext-cite&amp;language=en&amp;action_source=search&amp;filter=%21translated&amp;optional=1&amp;action=translate untranslated Cite extension messages] in their language and reviewing any use of [[mw:Special:MyLanguage/Reference Tooltips|Reference Tooltips]], which may require [[:phab:T416304#11668731|updates]] to support the new functionality. Wikis using [[mw:Special:MyLanguage/Help:Reference Previews|Reference Previews]] do not need to take any action. Communities may also wish to create the ''cite-tracking-category-ref-details'' [[Special:TrackingCategories|tracking category]] as a hidden category using &lt;code&gt;&lt;nowiki&gt;__HIDDENCAT__&lt;/nowiki&gt;&lt;/code&gt; (or a dedicated template), and connect it to the corresponding Wikidata item [[d:Q129764848]]. [https://phabricator.wikimedia.org/T425662]
* The [[mw:Special:MyLanguage/Readers/Reader Growth/Mobile page previews#Experimentation|Page Previews experiment]] on mobile web has concluded. The team decided not to roll out the feature after the results showed no statistically significant impact on reader retention, as the primary success metric was retention improvement. Page Previews, which are already available on desktop and in the apps, display a thumbnail, lead paragraph, and link to the full article when readers tap a blue link. The experiment tested this experience on mobile web across six Wikipedias.
* The [[mw:Special:MyLanguage/Codex/Design/Icons|user interface icon library]] will be [[phab:T399175|updated later this week or next week]]. Most of the ~300 icons have been slightly refined and ~30 new icons have been added. These changes improve the icons to make them more consistent and comprehensible, and provide more visual balance when they are used in groups.
* The [[mw:Special:MyLanguage/Universal Language Selector|Universal Language Selector]] (ULS) interface in MediaWiki, which helps users select content in other languages, has been updated. The new version improves speed and accessibility, and users of Wikimedia projects can now pin languages for quicker language switching. The deployment to Wikimedia sites will happen gradually in the coming weeks. You can test it now as a beta feature by selecting [[Special:Preferences#mw-prefsection-betafeatures|beta features]] in your profile preferences and share your feedback on [[mw:Special:MyLanguage/Universal Language Selector/New ULS|the project page]]. 
* [[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, an issue where the Pageviews Analysis dashboard on pageviews.wmcloud.org stopped updating graph data in May 2026, affecting all users, has been fixed. [https://phabricator.wikimedia.org/T427171]

'''Updates for technical contributors'''
* The function signature for &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;mw.util.addPortletLink()&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; has been simplified. Developers can now pass a configuration object instead of a list of positional parameters when creating portlet links. The previous function signature remains supported for backwards compatibility. For example, instead of: &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;mw.util.addPortletLink('p-cactions', '#', 'Stub', 'ca-stubtag', 'Add a stub tag to this page');&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; use &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;mw.util.addPortletLink('p-cactions', { href: '#', text: 'Stub', id: 'ca-stubtag', tooltip: 'Add a stub tag to this page' });&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt;. Script maintainers are encouraged to review existing uses of &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;addPortletLink()&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; and update them where appropriate. This change will be available on all wikis from 11 June. Thanks to community volunteer Gerges for contributing this improvement. [https://phabricator.wikimedia.org/T427945]
* '''Community Wishlist discussion''': Product &amp; Technology [[m:Special:MyLanguage/Community Wishlist/Updates#May 20, 2026: Community Tech becomes a program|introduced changes]] meant to increase the number and complexity of wishes fulfilled, including the disbanding of the Community Tech team. They are [[m:Special:MyLanguage/Community Wishlist/Updates|engaging in discussions]] about a [[m:Talk:Community Wishlist#Proposed direction for Wishlist|proposed direction for the wishlist]] from community members. Includes ways to structure annual voting, better tracking of wishes, removing focus areas, and [[m:Special:MyLanguage/Community Wishlist/Updates|staffing updates]].
* [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.47/wmf.6|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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2026/24|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2026-W24&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 21:30, 8 June 2026 (UTC)
&lt;!-- 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&amp;oldid=30650573 --&gt;

== Wikipedia translation of the week: 2026-25 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Cape Fiolent]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Beach of Cape Fiolent, Crimea.jpg|300px|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''Cape Fiolent''' (Crimean Tatar: Felenk Burun; Ukrainian: Фіолент; Russian: Фиолент; Latin: Parthenium), also historically called Cape Fiolente, is a cape and nature reserve (zakaznik) located in southern Sevastopol, a city within Crimea that is internationally recognised as part of Ukraine but currently occupied by Russia since 2014. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:24, 15 June 2026 (UTC)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=30662919 --&gt;

== Tech News: 2026-25 ==

&lt;section begin=&quot;technews-2026-W25&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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/25|Translations]] are available.

'''Weekly highlight'''
* The [[mw:Special:MyLanguage/Readers/Reader Growth|Reader Growth team]] has launched an [[mw:Special:MyLanguage/Readers/Reader Growth/Image Browsing|Image Browsing]] beta feature on the mobile web version of all Wikipedias. The feature shows an image carousel at the top of articles with 3 or more images. Editors can configure this feature with the following controls: to hide a specific image from a page, either use &lt;code&gt;class=notpageimage&lt;/code&gt; excluding it from thumbnail previews, or &lt;code&gt;class=noviewer&lt;/code&gt; excluding it from MediaViewer. The carousel can also be disabled from a page entirely, with the magic word &lt;code&gt;&lt;nowiki&gt;__NOMEDIAVIEWERCAROUSEL__&lt;/nowiki&gt;&lt;/code&gt;. To submit feedback or flag bugs, please visit the [[mw:Talk:Readers/Reader Growth/Image Browsing|project page]]. 
* [[mw:Special:MyLanguage/Help:Tables#class=&quot;wikitable&quot;|Wikitables]] can now be [[mw:Special:MyLanguage/Help:Sortable tables#Forcing the initial sort direction|sorted in descending order]] on the first click by adding &lt;code dir=ltr&gt;data-sort-order=&quot;desc&quot;&lt;/code&gt; to the header cell. Previously, by default, clicking a column header for the first time sorts it in ascending order. This addition to a Wikitable gives it more control and flexibility, while the default behavior for subsequent clicks remains unchanged. [https://phabricator.wikimedia.org/T398416]

'''Updates for editors'''
* The [[mw:Special:MyLanguage/Article guidance|Article guidance]] feature is currently being tested with some editors creating new articles on the Simple English, French, and Turkish Wikipedias. The experiment will soon begin on the Arabic and Bangla Wikipedias as well. [[w:simple:Special:NewArticle|This feature]] gives editors community-curated guidance to help them create articles that follow community standards. Experienced editors can continue creating or adapting outlines for specific article types that are commonly created by less experienced contributors. The outlines guide less experienced editors in creating high-quality articles. A quick guide to markups used in outlines can be found on [[mw:Special:MyLanguage/Article guidance/Test feature guide#Markups in outlines|this page]]. [[w:simple:Wikipedia:Article Guidance|Example outlines]] that can be adapted and instructions for how to adapt them are on [[mw:Special:MyLanguage/Article guidance#Adapting a sample outline in a Wikipedia|this section]] of the project page.
* Wikis that wish to replace the &quot;indefinitely&quot; button in Special:Block for temporary accounts (for example, wikis that block temporary users only until account expiration) will be able to do so by creating [[MediaWiki:ipb-indefinite-expiry-temporary-account]] with the block duration they want. [https://phabricator.wikimedia.org/T427125]
* [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:41}} community-submitted {{PLURAL:41|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]].

'''Updates for technical contributors'''
* By the end of June, a valid user-agent string will be required for automated dumps downloads from the dumps.wikimedia.org website. Automated requests that provide a generic or empty user-agent will be blocked. This [[phab:T400119|extends enforcement]] of the long standing [[foundation:Special:MyLanguage/Policy:Wikimedia Foundation User-Agent Policy|user-agent policy]]. Access to dumps through Wikimedia Cloud Services will not change.
* The roll out of global [[mw:Wikimedia APIs/Rate limits|API rate limits]] is now complete, with limits enforced across all APIs and at the documented levels for all groups. Bots running in Toolforge/WMCS or with the bot user right on any wiki remain exempt. All bots should continue to follow the documented best practices to avoid being rate limited.
* The [https://api.wikimedia.org/wiki/Main_Page API Portal wiki] will be read only starting this week (June 15-18). The following week (June 22-25), all API Portal wiki URLs will redirect to [[mw:Wikimedia APIs|Wikimedia APIs on 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.47/wmf.7|MediaWiki]]

'''Meetings and events'''
* On June 17th at 6pm UTC the WMF will be holding Discord call focused on a code review. We've heard through the [[mw:Special:MyLanguage/Developer Satisfaction Survey/2026|Developer Satisfaction Survey]] that volunteers are struggling with code review and we'd like to discuss these experiences with the goal of surfacing workable solutions. You can join the call [https://discord.gg/wikipedia?event=1514727511102062664 via the Wikimedia Community Discord server].
* The [[m:Special:MyLanguage/Conferencia Wikimedia de América Latina 2026|Latin American Wikimedia Conference]] will host a regional hackathon that will bring together the Wikimedia movement’s technical community including developers, system administrators, data scientists, and users with extended rights. Interested technical contributors can [https://docs.google.com/forms/d/e/1FAIpQLSf4osJzTHBJjQbYJk7TMVEJjTEQv7IgtsUDfP-o-qTgeRQQxw/viewform apply for a scholarship] to participate until June 21 at midnight (Bolivia time, UTC-4).
* Sign up for Wikimania Team Challenges to join this special event. The Team challenges will take place online and in person from July 21 to 22, before Wikimania conference. Everyone is welcome, regardless of skills or Wikimania registration. Teams will work on 10 important challenges supporting the Wikimedia community. For details, visit [[wmania:Special:MyLanguage/2026:Team challenges|the Team Challenges page]] and [https://wikimedia.eventyay.com/wm/teamchallenges/ register there]. Registration closes on June 20th at 11pm 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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2026/25|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2026-W25&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 16:49, 15 June 2026 (UTC)
&lt;!-- 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&amp;oldid=30689604 --&gt;

== Wikipedia translation of the week: 2026-26 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Renovating Action Party]]'''&lt;br /&gt; &lt;small&gt;''([[:es:Partido de Acción Renovadora]])''&lt;/small&gt; &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Flag of the Renovating Action Party.svg|300px|center]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
The '''Renovating Action Party''' was a left-wing Salvadoran political party that existed from 1944 to 1967. The party had three distinct phases of its existence under the leaderships of Colonel José Asencio Menéndez (1944–1950), the old line (1950–1964), and the new line (1964–1967). 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:52, 22 June 2026 (UTC)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=30717601 --&gt;

== Tech News: 2026-26 ==

&lt;section begin=&quot;technews-2026-W26&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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/26|Translations]] are available.

'''Weekly highlight'''
* [[mw:Special:MyLanguage/Growth/Feature summary|Growth features]] are [[phab:T418115|now available at Wikidata]]. This update enables access to Mentorship ([[mw:Special:MyLanguage/Help:Growth/Mentorship|if configured]]), Impact module, the Help Panel, and a simplified Newcomer Homepage (without Suggested Edits). Wikidata administrators are still configuring the features through Community Configuration.

'''Updates for editors'''
* The special page [[{{#special:RangeCalculator}}]] has been created. It allows users to find an IP range without needing to rely on external tools. Until now, this tool was only available to CheckUsers. [https://phabricator.wikimedia.org/T268429]
* [[m:Special:MyLanguage/WMDE Technical Wishes/Sub-referencing|Sub-referencing]] is a new MediaWiki feature that allows editors to reuse references with different details. It will be deployed to most small and medium-sized Wikipedia language versions on June 23. The [[m:Special:MyLanguage/WMDE Technical Wishes/Sub-referencing#deployment|FAQ]] lists possible actions to take on your wiki to support the deployment. Check the [[:phab:T414094|rollout plan]] for the next deployment steps. [https://phabricator.wikimedia.org/T428902]
* Starting next week, users will get a notification when they are blocked or unblocked from editing, or if this block changes. [https://phabricator.wikimedia.org/T100974]
* [[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]].

'''Updates for technical contributors'''
* Starting next week, abuse filters that are set to &quot;require CAPTCHA verification&quot; will begin to also affect users with the &lt;code&gt;skipcaptcha&lt;/code&gt; right, which includes most autoconfirmed users. Bots are exempted. This change only affects edits that trigger an abuse filter. The &lt;code&gt;skipcaptcha&lt;/code&gt; right will continue to exempt users from having to solve CAPTCHAs in the ordinary course of using the wikis. [https://phabricator.wikimedia.org/T402595]
* Reference documentation for the [[wikitech:Machine_Learning/LiftWing/API|Lift Wing API]] has moved from the API Portal to the interactive [https://wikitech.wikimedia.org/w/index.php?api=lift-wing&amp;title=Special%3ARestSandbox REST Sandbox].
* The API Portal wiki is now closed. For API documentation, see [[mw:Special:MyLanguage/Wikimedia_APIs|Wikimedia APIs on mediawiki.org]]. All API Portal wiki URLs (https://api.wikimedia.org/wiki/) will redirect to the mediawiki.org page starting June 22. [https://phabricator.wikimedia.org/T427537]
* [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.47/wmf.8|MediaWiki]]

'''Meetings and events'''
* Join an online call on 25 June at 2:30pm UTC to meet the current Wikimedia interns for [[mw:Google_Summer_of_Code/2026|Google Summer of Code]] and [[mw:Outreachy/Round_32|Outreachy]]. Interns will provide an overview of their projects and a brief demo of their work so far. Attendees are encouraged to [[mw:event:Google_Summer_of_Code/Summer_2026_June_Internship_open_session|share ideas and connections in their community]].

'''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2026/26|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2026-W26&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 13:05, 23 June 2026 (UTC)
&lt;!-- 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&amp;oldid=30722494 --&gt;

== Wikipedia translation of the week: 2026-27 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Facial age estimation]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----

&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''Facial age estimation''' is the use of artificial intelligence to estimate the age of a person based on their facial features. Computer vision techniques are used to analyse the facial features in the images of millions of people whose age is known and then deep learning is used to create an algorithm that tries to predict the age of an unknown person. The key use of the technology is to prevent access to age-restricted goods and services. Examples include restricting children from accessing internet pornography, checking that they meet a mandatory minimum age when registering for an account on social media, or preventing adults from accessing websites, online chat or games designed only for use by children. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;--[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 00:44, 29 June 2026 (UTC)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=30717601 --&gt;

== Tech News: 2026-27 ==

&lt;section begin=&quot;technews-2026-W27&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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/27|Translations]] are available.

'''Updates for editors'''
* As part of the [[mw:Special:MyLanguage/Contributors/Account Creation Experiments|Account Creation Experiments]], the Growth team tested adding a user account icon in the mobile web header for logged-out users, providing direct access to &quot;Create account&quot; and &quot;Log in&quot; actions. The experiment increased account creation by about 20% without negatively affecting edit quality or constructive edit rates. The feature will now be rolled out to all Wikimedia Foundation wikis on mobile web in the first week of July. [https://phabricator.wikimedia.org/T428220]
* After a [[phab:T426248|successful experiment]], logged-in users who did not [[mw:Special:MyLanguage/Help:Email_confirmation|confirm their email address]] when their account was created see a new banner asking them to complete that process. This helps reduce the risk that users get locked out of their account, and makes account email addresses overall more reliable. This is part of the [[mw:Special:MyLanguage/Product Safety and Integrity/Account Security|Account Security]] project. [https://phabricator.wikimedia.org/T428292]
* An update to [[Special:Search|Search]] is refining how the &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;-prefix:&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; behaves when used to exclude results. Previously, using &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;-prefix:&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; with negation could unintentionally broaden search results by adding the namespaces included in the search scope, leading to confusing behavior for users expecting a straightforward exclusion filter. With the update, &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;-prefix:&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; will now strictly exclude matching page titles as intended and may display a warning if the relevant namespace has not been explicitly selected. The behavior of &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;prefix:&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; without negation however remains unchanged. [https://phabricator.wikimedia.org/T427443]
* [[File:Reload icon with two arrows.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]]. For example, an issue where reviewers using the Page Curation toolbar were not automatically subscribed to talk page discussions they started has now been fixed. Reviewers will now receive notifications when someone replies to those discussions. [https://phabricator.wikimedia.org/T329346]

'''Updates for technical contributors'''
* Starting June 29th, automated downloads from the dumps.wikimedia.org website will be subject to the [[Foundation:Special:MyLanguage/Policy:Wikimedia Foundation User-Agent Policy|user-agent policy]]. Automated requests that provide a generic or empty user-agent will be blocked. Access to dumps through Wikimedia Cloud Services remains unaffected. This is a follow up to the announcement made in the [[m:Special:MyLanguage/Tech/News/2026/25|2026/25 issue of Tech News]].
* [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.47/wmf.9|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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2026/27|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2026-W27&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 11:48, 29 June 2026 (UTC)
&lt;!-- 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&amp;oldid=30744833 --&gt;

== Wikipedia translation of the week: 2026-28 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Paulo César Vinha State Park]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Capim dourado.jpg|300px|center|]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
The '''Paulo César Vinha State Park''' (Portuguese: Parque Estadual Paulo César Vinha) is a state park in the state of Espírito Santo, Brazil. It protects an area of dunes, lagoons and marshes along the Atlantic shore. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:35, 6 July 2026 (UTC)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=30717601 --&gt;

== Tech News: 2026-28 ==

&lt;section begin=&quot;technews-2026-W28&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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/28|Translations]] are available.

'''Updates for editors'''
* [[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, an issue where the search bar results on Wikidata, showed English results instead of using the correct language fallback for users of language variants, has now been fixed. Search suggestions will now follow the expected language fallback chain. [https://phabricator.wikimedia.org/T429769]

'''Updates for technical contributors'''
* In preparation for [[m:Special:MyLanguage/Event:Celebrate Women|Celebrate Women campaign]] planned for March 2027, the Wikimedia Foundation’s [[m:Special:MyLanguage/Wikimedia Foundation/Advancement/Community Growth/Content Enablement|Content Enablement team]] has launched a 22-question survey to better understand technical contributions by women+ (anyone who identifies as a woman) across Wikimedia projects. The survey takes approximately 15–20 minutes to complete and will remain open until 20 July 2026. The [[m:Special:MyLanguage/Celebrate Women/Technical contributions survey|questions]] are also available on-wiki for review in advance.
* The [[mw:Special:MyLanguage/Extension:Score|Score extension]] now supports rendering music scores as SVG images in addition to PNG, addressing a long-standing [[:phab:T49578|feature request]] and resolving historical image quality issues. Both formats are now provided to clients, with PNG in the &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;src&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; attribute and SVG in the &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;srcset&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; attribute.
* The new [[wikitech:Parsoid|Parsoid]] parser [[mw:Special:MyLanguage/Parsoid/Parser_Unification/Updates|continues to be deployed to additional wikis]], making it easier to introduce new reading and editing features. It was enabled on French Wikipedia, bringing total progress to covering 78.9% of Wikipedia page views. Rollout to English Wikipedia desktop will progress through this week.
* [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.47/wmf.10|MediaWiki]]

'''In depth'''
* The Wikimedia Hackathon 2026 [[diffblog:2026/06/29/wikimedia-hackathon-2026-building-collaborating-and-shaping-the-future-together/|recap blog post]] is now live. It highlights the projects, sessions, and social activities from this year’s event, and shares initial plans for the 2027 Wikimedia Hackathon.

'''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2026/28|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2026-W28&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 13:57, 6 July 2026 (UTC)
&lt;!-- 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&amp;oldid=30773578 --&gt;

== Wikipedia translation of the week: 2026-29 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Caledonian MacBrayne]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Cal-Mac HQ2005.jpg|300px|center|]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''Caledonian MacBrayne''', in short form CalMac, is the trade name of CalMac Ferries Ltd, the major operator of passenger and vehicle ferries to the west coast of Scotland, serving ports on the mainland and 22 of the major islands. It is a subsidiary of holding company David MacBrayne, which is owned by the Scottish Government. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
-[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:20, 13 July 2026 (UTC)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=30717601 --&gt;

== Tech News: 2026-29 ==

&lt;section begin=&quot;technews-2026-W29&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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/29|Translations]] are available.

'''Updates for editors'''
* [[mw:Special:MyLanguage/Growth/Revise_Tone|Revise Tone]] helps newcomers identify passages in Wikipedia articles that may contain non-encyclopedic language and encourages them to consider revising the tone. The feature was [[w:en:A/B_testing|A/B tested]] on the Arabic, English, French, and Portuguese Wikipedias, where newcomer task completion rates [[mw:Special:MyLanguage/Growth/Revise_Tone#Experiment_Results|increased by 38.7%]] compared to the default Copyedit task, with no decrease in edit quality. The test ended on July 9, and the feature is now available for everyone on these wikis, configurable via Community Configuration. [[phab:T426364|The plan]] is to release Revise Tone to more wikis.
* The community configuration that allows [[mw:Special:MyLanguage/Help:Growth/Mentorship#Automated mentor list cleanup|automatic removal of inactive mentors]] based on configurable criteria will be enabled on Thursday 16, [[mw:Special:MyLanguage/Growth/Deployment|on some wikis]] to keep mentor lists up to date. Mentors are experienced contributors who opt in to help new users on-wiki through the [[mw:Special:MyLanguage/Growth/Feature summary|Growth Features]]. Administrators can now prepare the settings via [[w:Special:CommunityConfiguration/Mentorship|Special:CommunityConfiguration/Mentorship]]; they will take effect starting Thursday.
* [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] View all {{formatnum:38}} community-submitted {{PLURAL:38|task|tasks}} that were [[m:Special:MyLanguage/Tech/News/Recently resolved community tasks|resolved last week]]. For example, an issue where some users of the Wikipedia Android app were logged out immediately after signing in, preventing them from staying logged in and editing pages, has now been fixed. [https://phabricator.wikimedia.org/T316916]

'''Updates for technical contributors'''
* Editing a page via user scripts or gadgets was causing watchlist labels that the user had assigned to that page to reset. This has now been fixed. [https://phabricator.wikimedia.org/T423778]
* To work around a Safari bug (see [[phab:T425211]]), on Parsoid-enabled wikis, wikilink hrefs now use absolute urls instead of protocol-relative urls. REST API output remains unchanged and continue to use protocol-relative urls. Gadgets, user scripts, bots, and CSS might need to be adapted if they relied on the presence of protocol-relative urls in wikilink hrefs. [https://phabricator.wikimedia.org/T431358]
* [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.47/wmf.11|MediaWiki]]

'''In depth'''
* The Wikimedia Foundation’s Experiment Platform Team has published a blog post reflecting on its first year of structured experimentation. It highlights successful experiments such as Paste Check, Reference Check, and Tone Check, which improved editing outcomes and have been rolled out to more users, as well as experiments that did not lead to product changes. [[diffblog:2026/07/07/moving-the-needle-how-we-test-new-ideas-across-wikimedia-projects|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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2026/29|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2026-W29&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 16:12, 13 July 2026 (UTC)
&lt;!-- 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&amp;oldid=30804401 --&gt;

== Wikipedia translation of the week: 2026-30 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Immigration to Switzerland]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----

&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
In 2023, resident foreigners made up 26.3% of Switzerland's population. Most of these (83%) were from European countries. Italy provided the largest single group of foreigners, accounting for 14.7% of total foreign population, followed closely by Germany (14.0%), Portugal (11.7%), France (6.6%), Kosovo (5.1%), Spain (3.9%), Turkey (3.1%), North Macedonia (3.1%), Serbia (2.8%), Austria (2.0%), United Kingdom (1.9%), Bosnia and Herzegovina (1.3%) and Croatia (1.3%). Immigrants from Sri Lanka (1.3%), most of them former Tamil refugees, were the largest group of Asian origin (7.9%).  

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:18, 20 July 2026 (UTC)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=30717601 --&gt;

== Tech News: 2026-30 ==

&lt;section begin=&quot;technews-2026-W30&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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/30|Translations]] are available.

'''Updates for editors'''
* The [[mw:Special:MyLanguage/Reader/Reader Experience|Reader Experience team]] has incorporated community feedback around the placement of watchstar and watchlist buttons for the [[mw:Special:MyLanguage/Readers/Reader Experience/WE3.3.4 Reading lists|Reading Lists beta feature]], which would allow for saving articles for later reading – a [[m:Special:MyLanguage/Community Wishlist/W102|wishlist item]] to bring the functionality to web. Editors are invited to enable the beta feature to test it out and [[phab:T426453|share their thoughts]].
* [[mw:Special:MyLanguage/VisualEditor/Suggestion Mode|Suggestion Mode]] offers edit suggestions within the VisualEditor for improving Wikipedia articles. [[Special:EditChecks|All suggestions]] are [[mw:Special:MyLanguage/Help:Suggestion mode#For administrators – local customization|community-configurable]]. The [[mw:Special:MyLanguage/Edit check/TextMatch|TextMatch]] feature is a way for volunteers to create custom local suggestions. The feature searches in articles for strings of text, and now includes support for regular expressions. This gives volunteers greater precision and flexibility over the kinds of local suggestions they can create. Note: Suggestions [[mw:Special:MyLanguage/Edit check/Configuration#:~:text=maximumEditcount|can be targeted]] based on the edit count of the person editing as well as other aspects of the page. You can [[mw:Special:MyLanguage/Help:Suggestion mode#Create custom local types of Suggestions|find examples from other communities]] for inspiration, including TextMatches that detect: typos, grammar-errors, potential advertisements, clichés, incorrect dash or hyphen usage, non-specific time keywords, outdated names, and more. Any [[mw:Special:MyLanguage/Talk:VisualEditor/Suggestion Mode|feedback]] is appreciated.
* [[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, an issue where the SVG Translate tool could use an outdated version of a file, causing existing translations to be overwritten when new ones were uploaded, has now [[phab:T430577|been fixed]]. Overall, in the last quarter from April – June 2026 about 337 community tasks were resolved by the Wikimedia Foundation.

'''Updates for technical contributors'''
* On Parsoid-enabled wikis, Parsoid now renders a maximum of 1,250 images per page. A new tracking category, &quot;media-limit-reached&quot;, will be soon made available to identify pages where this limit is reached, making it easier to find content whose media output may have been restricted during rendering. See [[phab:T430854]] for more information and to provide feedback.
* [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.47/wmf.12|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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2026/30|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2026-W30&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 05:47, 21 July 2026 (UTC)
&lt;!-- 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&amp;oldid=30836091 --&gt;

== Wikipedia translation of the week: 2026-31 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:fr:Study of Man's Impact on Climate]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----

&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
La '''Study of Man's Impact on Climate''' (traduisible en français par « Étude de l'impact de l'homme sur le climat ») est une conférence scientifique internationale consacrée à l'influence humaine sur le climat qui s'est tenue à Stockholm, en Suède, du 28 juin au 16 juillet 1971. Elle aborde diverses hypothèses parmi lesquelles la destruction de la couche d'ozone et le réchauffement (ou refroidissement) climatique, établit l'état du savoir à leur sujet et, soulignant les nombreuses inconnues qui demeurent, appelle à consacrer davantage de fonds à la recherche scientifique sur le climat. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:00, 27 July 2026 (UTC)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=30849684 --&gt;

== Tech News: 2026-31 ==

&lt;section begin=&quot;technews-2026-W31&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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/31|Translations]] are available.

'''Updates for editors'''
* [[File:Maki-gift-15.svg|12px|link=|class=skin-invert|Wishlist item]] [[mw:Special:MyLanguage/ContentTranslation|Content Translation]] now supports dark mode, fulfilling a [[m:Community Wishlist/W544|Community Wishlist request]]. This brings the tool in line with the accessibility features available in the Vector 2022 and Minerva skins, helping reduce visual fatigue for users translating content. [https://phabricator.wikimedia.org/T367077]
* DiscussionTools' source mode and the 2017 wikitext editor will now offer autocomplete for links (&lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;[[&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt;), templates (&lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;{{&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt;), HTML and parser tags (&lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;&lt;&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt;), and magic words (&lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;__&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt;), making it quicker and easier to insert links, templates, and other wiki markup while editing. [https://phabricator.wikimedia.org/T432400]
* The [[mw:Special:MyLanguage/Readers/Reader Growth/Mobile page previews|Readers Growth team]] has concluded its experiment with mobile page previews and will not roll out the feature. Page Previews are a pop-up bottom sheet that appears when readers tap a blue link, showing a thumbnail, lead paragraph, and an option to open the article. The experiment showed flat retention and negative indicator metrics, suggesting that mobile web readers preferred navigating directly to linked articles rather than using page previews.
* The Reader Experience team has seen encouraging early results from the [[mw:Special:MyLanguage/Readers/Reader Experience/Reading lists|Reading Lists feature]], with 93% of participating users reporting that it was useful. Reading Lists help active readers save articles for future reading and support their learning goals on Wikimedia projects. The team plans further improvements before expanding the feature to more users.
* The [[mw:Special:MyLanguage/Wikimedia Apps/Team/Explore Feed Refresh|Explore Feed Refresh]] initiative was tested with new and casual Wikipedia app readers. The refreshed feed helps readers discover new and relevant content. After a 10.5% increase in engagement with the feed, Wikimedia Apps team has decided to scale the Home Feed redesign to iOS with the learnings from the Android release applied.
* [[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, an issue where subject names in the Article Guidance feature were displayed with incorrect capitalization on French Wikipedia, has now been fixed. Subject names will now follow the correct capitalization rules for the language. [https://phabricator.wikimedia.org/T427201]

'''Updates for technical contributors'''
* After running several [[mw:Special:MyLanguage/Contributors/Account Creation Experiments|Account Creation Experiments]] to improve registration completion rates, a new version of the username field on [[Special:CreateAccount|Create Account]] has been rolled out. It includes [[:c:File:Create account - July 2026 updates.png|a popover summarizing the username policy]] to provide clearer guidance during account creation. As part of this change, the messages &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;createacct-helpusername&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; and &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;createacct-username-help&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; that several communities have configured will no longer be used. If communities want to customize the guidance shown in the new popover, they can instead edit the following messages: &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;createacct-username-policy-popover-bullet1&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt;, &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;createacct-username-policy-popover-bullet2&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt;, and &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;createacct-username-policy-popover-bullet3&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt;. [https://phabricator.wikimedia.org/T430604]
* Later this week, the [[mw:Special:MyLanguage/Help:Extension:CodeMirror|CodeMirror syntax highlighter]] will offer [[w:en:Theme (computing)|themes]]. The themes can be picked from a dropdown menu in the full [[mw:Special:MyLanguage/Help:Extension:CodeMirror#CodeMirror preferences|CodeMirror preferences]] dialog. For wikitext, available themes are default, colorblind-friendly (previously the colorblind preference option on [[Special:Preferences#mw-prefsection-editing]]) and no-highlighting. For code languages (i.e., CSS/JavaScript/JSON/Vue/Lua), there are several themes available. These same themes will eventually be available for wikitext, too. [https://phabricator.wikimedia.org/T163533]
* From now on, wikis can restrict editing in the &quot;User&quot; namespace to only the page owner and certain user groups. [[mw:Special:MyLanguage/Manual:$wgRestrictUserPageEditing|Read the configuration documentation]] 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.47/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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2026/31|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2026-W31&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 18:50, 27 July 2026 (UTC)
&lt;!-- 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&amp;oldid=30856308 --&gt;

== Wikipedia translation of the week: 2026-32 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Plot of Prats de Molló]]'''&lt;br /&gt; &lt;small&gt;''([[:ca:Fets de Prats de Molló]])&amp;#32;([[:es:Complot de Prats de Molló]])''&lt;/small&gt; &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----

&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
The '''plot of Prats de Molló''' was an attempted military invasion of Catalonia carried out from France to achieve its independence planned by Francesc Macià and the leadership of the Estat Català party, discovered and aborted in 1926. The plan consisted of the penetration of two columns (one from Saint-Laurent-de-Cerdans, the other from Coll d'Ares), which were to occupy Olot and proclaim the Catalan Republic. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 03:11, 3 August 2026 (UTC)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=30879613 --&gt;

== Tech News: 2026-32 ==

&lt;section begin=&quot;technews-2026-W32&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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/32|Translations]] are available.

'''Updates for editors'''
* The [[mw:Special:MyLanguage/Readers/Reader Experience|Reader Experience team]] has developed a [https://82db7c8d4b.catalyst.wmcloud.org/w/index.php?title=Regent%27s_Park&amp;uselang=de patch demo] that wraps the page toolbar onto two lines when there is not enough horizontal space for all the buttons. This aims to reduce crowding in the Vector 2022 toolbar, which can occur on some language Wikipedias at certain screen widths. [https://phabricator.wikimedia.org/T429518]
* The Reader Experience team is planning to launch [[mw:Special:MyLanguage/Readers/Reader Experience/Reading lists|Reading Lists]], a [[m:Special:MyLanguage/Community Wishlist Survey 2021/Mobile and apps/Have Apps reading lists available on Destop/Mobile|Community Wishlist item]], which is currently available to try in beta, as a full feature in September. Before then, volunteer translator help is needed for [https://translatewiki.net/w/i.php?title=Special%3ATranslate&amp;group=ext-readinglists&amp;filter=&amp;action=translate string translations] into a number of languages. The feature supports reading and learning goals on Wikipedia.
* Next week, the table of contents on Wikimedia Commons file pages will be improved by consolidating the file page table of contents with the page table of contents. This will make it easier to understand a file page’s structure, navigate to specific sections, and share links to individual sections. [https://phabricator.wikimedia.org/T332644]
* [[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, an issue where some [[w:TIFF|TIFF]] images failed to load after clicking their thumbnail, causing a broken image to be displayed instead of the full-size image, has now been fixed. [https://phabricator.wikimedia.org/T429326]

'''Updates for technical contributors'''
* The variable and function selector in AbuseFilter has been updated to support search and autocomplete. It will allow filter maintainers to find the desired variable or function more quickly. [https://phabricator.wikimedia.org/T323698]
* The MJPEG and VP8 formats are removed from the video player. The MP4 format (MPEG-4 Part 2) is added instead, which provides higher quality videos to older iPhone devices. It may take a few weeks to retroactively update all existing videos. The default format for modern devices stays the same (VP9/WebM). [https://phabricator.wikimedia.org/T358266]
* [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.47/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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2026/32|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2026-W32&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 19:47, 3 August 2026 (UTC)
&lt;!-- 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&amp;oldid=30872536 --&gt;

== Wikipedia translation of the week: 2026-33 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:it:Composizione VII]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Composition VII - Wassily Kandinsky, GAC.jpg|300px|center|]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''Composizione VII''' (Композиция VII o Zu Komposition 7) è un olio su tela del 1913, realizzato dal pittore russo Vasilij Vasil'evič Kandinskij e conservato nella Galleria Tret'jakov di Mosca.

Prodotto centrale del pittore russo nel periodo 1910-1915, essa è considerata l'opera che certificò la raggiunta maturità creativa da parte di Kandinskij, rappresentando anche l'apice della sua energia creativa. È considerato il più rappresentativo tra i lavori completati durante l'anno del successo internazionale dell'artista, simboleggiando il punto di emancipazione definitivo dell'Astrattismo.

Opera più grande mai realizzata dall'artista per dimensione, facente parte della serie denominata Composizioni, rappresenta un'allegoria dell'Apocalisse, di cui riprende il tema e lo propone in una versione astratta, trasfigurata dalla realtà in una forma composta da sole linee e colori. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:24, 10 August 2026 (UTC)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=30889664 --&gt;

== Tech News: 2026-33 ==

&lt;section begin=&quot;technews-2026-W33&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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/33|Translations]] are available.

'''Updates for editors'''
* [[File:Maki-gift-15.svg|12px|link=|class=skin-invert|Wishlist item]] A new ChartWizard is [[c:Special:ChartWizard/Data:Example.Pie.chart|now available on Wikimedia Commons]] for users interested in creating charts from their own data. The wizard makes the [[mw:Special:MyLanguage/Extension:Chart|Chart extension]] more beginner-friendly by allowing editors to create charts, such as bar and pie charts, without needing to use JSON. Users can still switch to the JSON editor if they prefer. Feedback on the new tool is welcome on the [[m:Talk:Community Wishlist/W414|wish talk page]].
* [[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 where the Wikipedia iOS app’s Picture of the Day widget displayed the same image every day instead of updating daily, has now been fixed. [https://phabricator.wikimedia.org/T430692]

'''Updates for technical contributors'''
* [[mw:Special:MyLanguage/Extension:Math|Math formula]] SVG images will soon be generated in the browser instead of on the server. MathML continues to be generated on the server and renders in the browser without JavaScript. Wikibooks will see this change on 12 August, Wikisource on 19 August and Wikipedia from 20-27 August. You can try this by selecting &quot;{{int:Mw-math-mathjax}}&quot; in your preferences. This change is part of [[mw:Special:MyLanguage/RESTBase/deprecation|deprecating RESTBase]] and [[phab:T431372|deprecating Mathoid]]. [https://phabricator.wikimedia.org/T271001]
* Category pages will soon support sorting entries by the time they are added to a category. This will make it easier to find recently or long-standing categorized pages. It will also improve workflows for maintenance categories such as deletion backlogs and other time-based review tasks. You can use &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;cldsort=timestamp&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; URL argument in category view to sort the entries. [https://phabricator.wikimedia.org/T433768]
* [[mw:Special:MyLanguage/Extension:Gadgets|Gadgets]] and user scripts on Wikimedia wikis may now use [[phab:T395347|ES2018 features]] and [[phab:T419142|ES2019 features]] in JavaScript code. Previously, the platform only allowed up to ES2017. MediaWiki validates the source code to protect functionality from syntax errors and to ensure scripts are valid in all [[mw:Special:MyLanguage/Compatibility#Browser_support_matrix|supported browsers]]. [https://phabricator.wikimedia.org/T419142]
* [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.47/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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2026/33|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2026-W33&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 20:46, 10 August 2026 (UTC)
&lt;!-- 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&amp;oldid=30901051 --&gt;

== Wikipedia translation of the week: 2026-34 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Divorce in Poland]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----

&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''Divorce in Poland''' occurs at a rate slightly below that of the average for Europe. In the Polish legal system, divorce proceedings fall within the exclusive jurisdiction of the civil court; there is no legal basis for resolving a marriage through the agreement of the spouses or through administrative procedures. Divorce requests are assessed by the court, in accordance with the positive and negative prerequisites set in the relevant law. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:59, 17 August 2026 (UTC)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=30927700 --&gt;

== Tech News: 2026-34 ==

&lt;section begin=&quot;technews-2026-W34&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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/34|Translations]] are available.

'''Weekly highlight'''
* The [[mw:Special:MyLanguage/Help:Extension:CampaignEvents/Registration/Worklist|Worklist feature]] for the Event Registration tool is now live on all Wikimedia wikis. With Worklist, event organizers can add the articles their event will focus on directly to the event page. The Worklist also powers [[mw:Special:MyLanguage/Help:Extension:CampaignEvents/Registration/Worklist#How Event Pathways uses the worklist|Event Pathways]] which notifies other editors of the upcoming or ongoing event when they edit an article featured in the event's Worklist. This is the minimum viable version (MVP), and feedback is welcome. Organizers are encouraged to try the feature. A hands-on [[m:Special:MyLanguage/Event:Worklist Setup Workshop: Get Your Event Ready|Worklist Setup Workshop]] will take place on 18 August at 16:00 UTC and 19 August at 11:00 UTC.

'''Updates for editors'''
* [[Special:ShortPages]] displays short pages by their size, but in many cases it gets filled with disambiguations and soft redirects, making it harder to find the short articles themselves. Starting this weekend, you will be able to choose not to include an article in the special page by adding the magic word &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;__EXPECTSHORTPAGE__&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt;. [https://phabricator.wikimedia.org/T433203]
* One new wiki has been created: a {{int:project-localized-name-group-wikipedia/en}} in [[d:Q3436680|Bole]] ([[w:bol:|&lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;w:bol:&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt;]]) [https://phabricator.wikimedia.org/T429921]
* Starting the week of August 17, the page toolbar will wrap onto two lines when there is not enough horizontal space for all the buttons. This is a [[phab:T429518|fully merged patch from the Reader Experience team]] which aims to reduce crowding in the Vector 2022 toolbar, that may occur on some language Wikipedias at certain screen widths.
* [[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, uploading large files to Wikimedia Commons has become more stable and less prone to failure following some fixes related to the “Could not acquire lock” upload error. [https://phabricator.wikimedia.org/T386640]

'''Updates for technical contributors'''
* Debian Bullseye will reach the end of its Long Term Support on 31 August 2026. [[phab:T434103|Some Cloud VPS projects]] still have instances running Debian Bullseye. Maintainers of those projects are encouraged to migrate to Debian Bookworm or Debian Trixie. A [[wikitech:Help:Cloud VPS instance operating system migration|migration guide]] is available to help with the process, and users may also want to consider whether their workload is better suited to Toolforge. If you need help or cannot complete the migration by 31 August, please contact the Cloud VPS admins as soon as possible. [[listarchive:list/cloud-announce@lists.wikimedia.org/thread/RVIPQSYLKMSL5M46JP6NEJVGVE6I2RXQ/|Read more]].
* [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.47/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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2026/34|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2026-W34&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 21:04, 17 August 2026 (UTC)
&lt;!-- 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&amp;oldid=30922806 --&gt;

== Wikipedia translation of the week: 2026-35 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Day of the Macedonian Revolutionary Struggle]]'''&lt;br /&gt; &lt;small&gt;''([[:mk:Ден на македонската револуционерна борба]])''&lt;/small&gt; &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----

&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
The '''Day of the Macedonian Revolutionary Struggle''' (Macedonian: Ден на македонската револуционерна борба),[1] also known as Day of VMRO, is a national holiday which is celebrated on October 23 in North Macedonia. In 2007, the holiday was voted into law as a new national holiday. It is a non-working day. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:15, 24 August 2026 (UTC)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=30927700 --&gt;

== Tech News: 2026-35 ==

&lt;section begin=&quot;technews-2026-W35&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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/35|Translations]] are available.

'''Updates for editors'''
* The [[Special:CreateAccount|Special:CreateAccount]] page has been simplified as part of ongoing work to modernize the account creation experience. The panel showing project statistics no longer appears next to the form on desktop and mobile web. Multiple account creation experiments show that a simpler form helps newcomers complete registration. [https://phabricator.wikimedia.org/T433783]
* In order to improve page performance, images now load when they are viewed. This means images lower down an article will not load if a reader never scrolls to that part of the page, which may affect some image-related metrics. [https://phabricator.wikimedia.org/T148047]

* [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] 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, an issue where image thumbnails in Abstract Wikipedia could fail to display after the corresponding file was moved on Wikimedia Commons, has now been fixed. Thumbnails will now update correctly when files are moved. [https://phabricator.wikimedia.org/T433448]

'''Updates for technical contributors'''
* User Info card is a feature that helps patrollers see information about user accounts. So far, it has been available only in places such as page history, logs and recent changes. Now, it's possible to [[mw:Special:MyLanguage/Help:Extension:CheckUser#User_Info_card_in_page_content|place it in the page content]] as well, using the &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;{{#uic:}}&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; parser function. It can be particularly useful in templates like [[:en:Template:Userlinks|&lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;{{Userlinks}}&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt;]] (or their specialized variants), as it will make it easier to see the context about a user on various noticeboard pages. The card will be displayed only to users who have it enabled in their [[Special:Preferences#mw-input-wpcheckuser-userinfocard-enable|preferences]]. [https://phabricator.wikimedia.org/T424466]
* Due to user security and privacy risks, we have disabled access to &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;Special:MyPage&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; URLs when specifically using &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;action=raw&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt;. If you are impacted by this, consider whether you can use an alternative approach. &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;Special:MyPage&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; URLs can still be accessed and used without &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;action=raw&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt;. Specified user page URLs (e.g. &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;User:Myusername&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt;) can still be used with &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;action=raw&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt;. [https://phabricator.wikimedia.org/T120386]
* Due to an update, the thumbnailing software has been improved. This includes upgrading &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;librsvg&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; to 2.60 and &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;ImageMagick&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; to 7, as well as resolving a number of long-standing thumbnailing bugs like rendering errors. [https://phabricator.wikimedia.org/T419815#12222841]

* [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.47/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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2026/35|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2026-W35&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 20:46, 24 August 2026 (UTC)
&lt;!-- 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&amp;oldid=30961208 --&gt;

== Wikipedia translation of the week: 2026-36 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Wimmen's Comix]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----

&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''''Wimmen's Comix''''', later retitled (respelled) as Wimmin's Comix, is an influential all-female underground comics anthology published from 1972 to 1992. Though it covered a wide range of genres and subject matters, Wimmen's Comix focused more than other anthologies of the time on feminist concerns, homosexuality, sex and politics in general, and autobiographical comics. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:54, 31 August 2026 (UTC)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=30988228 --&gt;

== Tech News: 2026-36 ==

&lt;section begin=&quot;technews-2026-W36&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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/36|Translations]] are available.

'''Weekly highlight'''
* A new format for the Community Wishlist is open for feedback. You can [[m:Special:MyLanguage/Community Wishlist/Community Wishlist 2027|read the proposed ideas on Meta]]. This new process plans to improve how wishes are triaged, voted on, and prioritized in a way that is transparent and balanced across project families and language editions. This consultation is open for two weeks.

'''Updates for editors'''
* The latest release of the Wikipedia Android app includes updates to the Saved feature, bringing the app’s saving experience closer to iOS and Web. The update redesigns the Saved tab with an “All articles” view, removes the default “Saved” reading list, renames reading lists to “Collections,” and modernizes the article-saving experience. [https://phabricator.wikimedia.org/T420788]
* The [[mw:Special:MyLanguage/Readers/Reader Experience/Reading lists|Reading Lists]] feature was enabled for all logged-in users on Bengali, Chinese, Czech and Vietnamese Wikipedias on August 25, after several months as a beta feature. Reading Lists will be available to all logged-in users on Arabic, French and Indonesian Wikipedias on September 1, followed by English Wikipedia on September 14, and all other Wikipedia wikis on September 28.
* At the end of the month, some logged-out readers on Bengali, Czech, Persian, English, and Polish Wikipedias using the Minerva skin on mobile will see an [[mw:Special:MyLanguage/Readers/Reader_Growth/Minimal_Minerva|updated navigation bar]] in an [[w:A/B test|A/B test]]. The test will compare the current navigation bar with a new version designed to make it easier to find information more quickly. The goal is to determine whether these changes encourage readers to return more often. This experiment will not change the experience for logged-in readers and/or editors.
* Editors who maintain redirects, templates, and categories used on redirect pages now have improved ways for finding and curating redirects. Previously, redirects pages could not be searched. Two new search keywords, &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;onlyredirects:&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; and &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;withredirects:&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt;, now allow redirects to be searched directly and can be combined with existing keywords such as &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;incategory:&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt;, &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;intitle:&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt;, and &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;insource:&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt;. [https://phabricator.wikimedia.org/T204089]
* The ISBN lookup tools for generating citations were recently not working because of external service problems. Developers are working on solutions. [https://phabricator.wikimedia.org/T435179]
* [[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 searching for pages by category using &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;deepcat&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; could return no results or unrelated results has now been fixed. [https://phabricator.wikimedia.org/T414859]

'''Updates for technical contributors'''
* The domain of URLs for thumbnails is changing from upload.wikimedia.org to thumb.wikimedia.org. The old URLs will continue to work for the foreseeable future but MediaWiki will advertise the new domain instead. URLs to other types of media such as original files, videos and transcodes will still be served from upload.wikimedia.org. [https://phabricator.wikimedia.org/T427465]
* The Wikimedia [https://www.mediawiki.org/w/index.php?api=wmf-math%2Fv1&amp;title=Special%3ARestSandbox Math API] is now deprecated. These endpoints will be fully sunset by the end of September 2026. Developers who call these endpoints should transition to alternative math rendering solutions, such as the native [https://developer.mozilla.org/en-US/docs/Web/MathML MathML] or [https://www.mathjax.org/ MathJax]. Third-party MediaWiki installations that utilize the Math extension for formula rendering are required to upgrade to v1.43+ to avoid disruption of service.

* [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.47/wmf.18|MediaWiki]]

'''In depth'''
* Read more about [[mw:Special:MyLanguage/Edit_check/TextMatch|TextMatch]] in a Diff post titled, [[diffblog:2026/08/28/custom-edit-suggestions-for-every-wiki-how-communities-are-shaping-suggestion-mode-with-textmatch/|Custom edit suggestions for every wiki: How communities are shaping Suggestion Mode with TextMatch]].

'''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2026/36|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2026-W36&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 20:54, 31 August 2026 (UTC)
&lt;!-- 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&amp;oldid=30990659 --&gt;

== Wikipedia translation of the week: 2026-37 ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Paulet affair]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----

&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
The '''Paulet affair''', also known as British Hawaii, was the insubordinate five-month occupation of the Hawaiian Kingdom in 1843 by British naval officer Captain Lord George Paulet, of HMS Carysfort. It was ended by the arrival of American warships sent to defend Hawaii's independence. The British government in London did not authorise the move and it had no official status. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 01:59, 7 September 2026 (UTC)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=30993988 --&gt;

== Tech News: 2026-37 ==

&lt;section begin=&quot;technews-2026-W37&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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/37|Translations]] are available.

'''Updates for editors'''
* [[mw:Special:MyLanguage/Help:Growth/Tools/Add_a_link|Add a Link]] has been upgraded for English Wikipedia users with improved detection of links that have different capitalization. This will help reduce ambiguous suggestions caused by differences in capitalization in article titles, including articles about cultural goods. A second phase of improvements is planned, which will also prepare the feature for release in other languages. [https://phabricator.wikimedia.org/T435526#12240876] [https://phabricator.wikimedia.org/T434259]
* The [[mw:Special:MyLanguage/Article_guidance|Article guidance]] feature will be enabled by default for junior editors on Simple English and Turkish Wikipedia starting 10 September 2026 following [[mw:Special:MyLanguage/Article_guidance/Updates#Summary_of_experiment_result|an experiment]]. Junior editors with 0 to 99 edits will automatically see the feature when they click a red link or use the &quot;[[tr:Vikipedi:Madde_sihirbazı|Madde oluşturto]]&quot; option on Turkish Wikipedia to create a new article. The change is intended to help junior editors create higher-quality articles that meet each Wikipedia’s standards. [[phab:maniphest/query/z3tcTjmLMxk5/#R|Additional improvements]] will continue based on the experiment results and community feedback.
* The [https://pageviews.wmcloud.org Pageviews Analysis] tool which allows users to compare pageviews across multiple pages, turns 10 years old this year and several new features have been added. They include [[toolforge:wikinav|WikiNav]] which provides insights into how readers of Wikipedia explore the content, editing stats in [https://pageviews.wmcloud.org/siteviews?range=latest-30&amp;sites=en.wikipedia.org Siteviews], the ability to [https://pageviews.wmcloud.org/massviews?source=wikiproject&amp;project=en.wikipedia.org lookup articles belonging to a WikiProject], and support for dark mode. [https://phabricator.wikimedia.org/T378549]
* A [[mw:Special:MyLanguage/Readers/Reader_Growth/Minimal_Minerva|visually simplified Minerva]] navigation bar is being tested for logged-out readers using mobile web on the Bengali, Czech, English, Farsi, and Polish Wikipedias. The experiment aims to determine whether simplifying the navigation improves reader retention. The test will run from August 31 to September 28, and no action is required from users.
* [[m:Special:MyLanguage/WMDE Technical Wishes|WMDE Technical Wishes]] is working on improving [[en:Wikipedia:VisualEditor/Named references|auto-generated reference names in VisualEditor]]. Editors will only notice a slight change starting this week. When adding automatic reference names the numbering will start at &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;:1&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; instead of &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;:0&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt;. Read more on the [[m:WMDE Technical Wishes/References/VisualEditor automatic reference names|project page]]. [https://gerrit.wikimedia.org/r/c/VisualEditor/VisualEditor/+/1332704]
*  All wikis will be [[m:Special:MyLanguage/Tech/Server switch|read-only for a few minutes]] on September 23. 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/T433363]
* [[File:Reload icon with two arrows.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, an issue where [[mw:Special:MyLanguage/Parsoid|Parsoid]] could mishandle nested nowiki tags, causing content to be lost and displaying unwanted text has now been fixed. [https://phabricator.wikimedia.org/T435116]
'''Updates for technical contributors'''
* Interface administrators can configure gadgets from [[MediaWiki:Gadgets-definition]]. The definition format has been updated and no longer requires the &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;ResourceLoader&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; option, as gadgets are always loaded through &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;ResourceLoader&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt;. This simplifies gadget configuration by removing an option that is no longer necessary, making gadget definitions easier for administrators. [https://phabricator.wikimedia.org/T298199]
* [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.47/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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2026/37|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2026-W37&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 18:45, 7 September 2026 (UTC)
&lt;!-- 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&amp;oldid=31008437 --&gt;

== Wikipedia translation of the week: 2026-38 ==
&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:No-AI label]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:No AI Sign.svg|300px|center|]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
A '''no-AI label''' is a label used on a product to signify that it was not made using generative AI. Phrases on the labels include but are not limited to &quot;human-made&quot;, &quot;proudly human&quot; and &quot;AI-free&quot;. Some organisations that provide the labels allow product creators to download and use their no-AI labels for free, while others charge creators for analysing the content and allowing the use of the labels if the organisation believes that no AI was used. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:43, 14 September 2026 (UTC)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=31028050 --&gt;

== Tech News: 2026-38 ==
&lt;section begin=&quot;technews-2026-W38&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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/38|Translations]] are available.

'''Weekly highlight'''
* The Future Audiences team has started a [[en:Special:MyLanguage/Wikipedia:Village pump (proposals)#New proposed experiment to let readers know about “Google preferred sources”|discussion on English Wikipedia]] about a proposed new experiment to show a temporary notice about the new [https://blog.google/products-and-platforms/products/search/original-high-quality-content-search/ Google Preferred Sources] feature to Wikipedia readers coming from Google. The experiment is to test whether this notice makes visitors come back to Wikipedia more often. Preferred Sources feature lets users choose websites they trust so Google can highlight content from those sources more prominently in Search and AI experiences. We are interested in testing this on other languages that Google supports and would welcome assistance with starting conversations on other wikis. If interested, please reach out to Future Audiences on the [[m:Special:MyLanguage/Future Audiences/Preferred sources|talk page]].

'''Updates for editors'''
* The chat platform Discord is releasing a new self-service framework that websites can use to specify how their links should look when shared on Discord. The Future Audiences team is planning to start using this new framework to improve how Wikipedia links look when shared on Discord, giving better attribution and credit to contributors. The link appearance and behavior won't change in the first phase of this project as we want to first collect some baseline data to assess the impact of future changes. However, if community members who are active on Discord spot any issues, they can reach out on [[phab:tag/future-audiences/|Phabricator]] or [[m:Special:MyLanguage/Future Audiences|Metawiki]].
* The Reader Growth team will be running an experiment to test whether [[mw:Special:MyLanguage/Readers/Reader_Growth/Compact Lead|compacting article lead sections on mobiles]] with the addition of a &quot;read more&quot; button improves reader retention. The test will begin on September 17 on Arabic, Spanish, French, Indonesian, Italian, Japanese, Portuguese, Vietnamese, and Chinese Wikipedias and will run for four weeks.
* All wikis will be [[m:Special:MyLanguage/Tech/Server switch|read-only for a few minutes]] on September 23. 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 week. [https://phabricator.wikimedia.org/T433363]
* [[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, an issue where [https://wikistats.wmcloud.org/ Wikistats] for Wikipedias was returning an HTTP 500 error and could not be reached, has now been fixed. [https://phabricator.wikimedia.org/T435959]

'''Updates for technical contributors'''
* Developers who maintain a tool that queries the Wikimedia Commons links tables need to update their code to connect to the new x4 database cluster. The links tables have been moved from the s4 cluster to x4, and will no longer receive updates on s4. The page and redirect tables remain available on both clusters. A wiki replica for the x4 cluster will be set up afterwards. The change is being made because the s4 cluster has grown too large to operate efficiently. You can [[wikitech:Special:MyLanguage/News/2026 Commons links tables database split|read more]].
* [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.47/wmf.20|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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2026/38|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2026-W38&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 15:31, 14 September 2026 (UTC)
&lt;!-- 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&amp;oldid=31039826 --&gt;

== Wikipedia translation of the week: 2026-39 ==
&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Scotty (dinosaur)]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Scotty Tyrannosaurus.jpg|300px|center|]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''Scotty''' is the nickname for the Tyrannosaurus rex fossil, catalogued as RSM P2523.8, that was discovered in Saskatchewan, Canada in 1991.[3] The fossilised remains were painstakingly removed, almost completely by hand, over two decades from the rock in which they were embedded. When the preparation was complete in 2011, an around 65% complete T. rex skeleton was revealed. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:02, 21 September 2026 (UTC)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=31045260 --&gt;

== Tech News: 2026-39 ==
&lt;section begin=&quot;technews-2026-W39&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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/39|Translations]] are available.

'''Weekly highlight'''
* [[m:Special:MyLanguage/Tech/Server switch|All wikis will be read-only]] for a few minutes on Wednesday, 23 September 2026 at [https://zonestamp.toolforge.org/1790172000 14:00 UTC]. This is for the datacenter server switchover backup tests, [[wikitech:Special:MyLanguage/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. [https://phabricator.wikimedia.org/T433363]

'''Updates for editors'''
* The Growth team tested a new post-edit notice designed to [[mw:Special:MyLanguage/Contributors/Account Creation Experiments#4. Encourage Temporary Accounts to Register|encourage Temporary Account holders to register for a permanent account]]. The new notice replaced multiple dialogs and a simultaneous welcome notification with a single message highlighting the benefits of creating an account. The experiment increased permanent account creation from 1.94% to 3.66%, an 87% relative increase. The change will now be released to all wikis. [https://phabricator.wikimedia.org/T433551]
* For Wikipedia editors using the [[Special:Preferences#mw-prefsection-betafeatures|&quot;Suggestion mode&quot; Beta Feature]], there is a [[Special:Preferences#mw-input-wpvisualeditor-editcheck-experimental|new opt-in user preference]] for showing &quot;experimental&quot; edit checks and suggestions. These types are listed at [[Special:EditChecks#experimental-checks|Special:EditChecks]], and are intended for early developer-testing and for gathering feedback from experienced users. Administrators can change the [[mw:Special:MyLanguage/Edit check/Configuration|configuration details]] for each suggestion as usual. Administrators can also [[mw:Special:MyLanguage/Help:Suggestion mode#Experimental Suggestions|use this feature]] to help test their community's ideas for locally created checks and suggestions. Experimental types will have a more distinct visual style later this week. [[mw:Talk:VisualEditor/Suggestion Mode|Feedback is welcome]].
* The [[m:CEE Technical Village Pump|CEE Technical Village Pump]] has been launched as a space for technical discussions and collaboration among Wikimedia communities in Central and Eastern Europe.
* A new tool, [[mw:Special:MyLanguage/Language Onboarding and Development/Starter kit|Starter Kit]], is now available for new and small language Wikipedia communities. It brings together guided tasks, tools, and resources to help communities get started, monitor their progress, and collaborate with the broader Wikimedia community. Starter Kit is hosted on Wikimedia Toolforge and is designed for Wikipedias with fewer than 50,000 articles. Learn more about how Starter Kit works and how communities have been using it in [[diffblog:2026/09/18/introducing-starter-kit-for-new-and-small-language-wikipedias/|this Diff blog post]].
* The Reader Growth team is launching a retest of the [[mw:Special:MyLanguage/Readers/Reader Growth/Image Browsing|image carousel experiment]]. The retest will use three new versions of the design, updated based on community feedback. The team will assess results and determine with communities whether or not to proceed with the feature. The experiment will begin the week of September 28 and will run on Arabic, Bengali, Chinese, Czech, English, Farsi, French, German, Indonesian, Japanese, Polish, Portuguese, Spanish, Swedish, and Vietnamese Wikipedias.
* After successful rollouts to Arabic, Bengali, Chinese, Czech, English, French, Indonesian, and Vietnamese Wikipedias, the [[mw:Special:MyLanguage/Readers/Reader Experience/Reading lists|Reading Lists feature]] from the Reader Experience team will be available to all logged-in users on all Wikipedia wikis starting September 28.
* [[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, an issue where the mentor status script repeatedly updated mentors’ status even when nothing had changed, creating unnecessary Recent Changes entries, has now been fixed. [https://phabricator.wikimedia.org/T436659]

'''Updates for technical contributors'''
* The &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;abusefilters&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; list query API, used to retrieve specific details about active or historical abuse filters configured on a wiki, has been updated to support the &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;formatversion=2&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; configuration parameter, thereby leading to breaking changes to the API response. All users who maintain user-scripts or other code need to check if they use the &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;abusefilters&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; list query API, and respond to any breaking changes. [https://phabricator.wikimedia.org/T435828]
* [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.47/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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2026/39|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2026-W39&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 11:56, 27 September 2026 (UTC)
&lt;!-- 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&amp;oldid=31085309 --&gt;

== Wikipedia translation of the week: 2026-40 ==
&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:Descartes Highlands]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Apollo 16 landingsite.jpg|300px|center|]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
The '''Descartes Highlands''' is an area of lunar highlands located on the near side that served as the landing site of the American Apollo 16 mission in early 1972. The Descartes Highlands is located in the area surrounding Descartes crater, after which the feature received its name 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:27, 28 September 2026 (UTC)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=31087748 --&gt;

== Tech News: 2026-40 ==
&lt;section begin=&quot;technews-2026-W40&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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/40|Translations]] are available.

'''Updates for editors'''
* Users of default skins on desktop and mobile web (Vector 2022 and Minerva respectively) will now be informed if the search suggestions displayed as they type into Search come from page redirects. Previously, users could get confused when the top search suggestions did not match exactly what they had typed. The new redirect notice clarifies that these suggestions are not random, but related to the search. The suggested pages may be redirects to the most relevant destination articles being searched for. [https://phabricator.wikimedia.org/T303013]
* Logged-out Wikipedia users on mobile web will begin to see a bookmark button for saving articles to their [[mw:Special:MyLanguage/Readers/Reader Experience/Reading lists|reading lists]] instead of the current Watchstar button. When clicked, the bookmark button prompts users to log in or create an account to save an article for later. An earlier experiment found that the bookmark icon was four times more likely than the Watchstar button to encourage logged-out users to create an account. This change is part of efforts to encourage more readers to become account holders and use features that help them save and return to content. [https://phabricator.wikimedia.org/T438769]
* An experiment will begin on September 29 on Spanish, Arabic, English, and French Wikipedias to simplify the experience users encounter immediately after account creation. The test will explore whether removing friction from the current Welcome Survey helps new users understand what to do next more easily. The experiment will run through the end of October. [https://phabricator.wikimedia.org/T430058]

* The [[m:Special:MyLanguage/Product and Technology Advisory Council|Product and Technology Advisory Council]] has put out a call for the community to suggest topics that it should consider and discuss with the Wikimedia Foundation. Editors and technical contributors are invited to add topics to [[m:Talk:Product and Technology Advisory Council|the council's talk page]].
* Later this week, it will be possible for communities to configure [[mw:Special:MyLanguage/Help:Edit check|Edit Checks and Suggestions]] so that they are [[mw:Special:MyLanguage/Edit check/Configuration#extraNamespaces|shown within additional namespaces]], such as a &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;Draft:&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; namespace. [[mw:Talk:VisualEditor/Suggestion Mode|Feedback is welcome]].
* A bug in the [[m:Special:GlobalWatchlist|Global Watchlist]] is causing the page to fail to load for users that have unseen changes on Wikimedia Commons. Developers are working on a fix. Until then, affected users can follow the workarounds described in the [[mw:Special:MyLanguage/Extension:GlobalWatchlist#GlobalWatchlist temporarily broken for users with Wikimedia Commons|relevant]] help section.
* New magic words &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;{{CATEGORYSORT:TIMESTAMP}}&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; and &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;{{CATEGORYSORT:RTIMESTAMP}}&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; are now available for use. They are able to change the default sorting of categories to be based on timestamp of categorization. [https://phabricator.wikimedia.org/T433768]
* [[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 issue where [https://wikistats.wmcloud.org/ Wikistats] for Wikipedias was not reachable has now been fixed. [https://phabricator.wikimedia.org/T435959]

'''Updates for technical contributors'''
* The datacenter switchover, scheduled on September 23, has been postponed. [[diffblog:2025/03/12/hear-that-the-wikis-go-silent-twice-a-year/|The equinox exercise]] revealed capacity issues, preventing the switch of all services to the other datacenter. The process has been paused, prioritizing investigating that issue, to ensure that we continue to be able to serve our users reliably. A new exercise will be scheduled. Meanwhile, all traffic and edits continue to work as usual.
* On September 23, a power loss briefly affected all wikis, creating intermittent issues on both reading and editing modes. This also affected Gerrit. This is unrelated to the datacenter switchover postponement. [https://www.wikimediastatus.net/incidents/9fm19t8qykk8]
* [[mw:Special:MyLanguage/Help:Extension:Produnto|Produnto]] has been deployed to mediawiki.org and [[phab:T421436|some Indic language wikis]]. We want to hear your feedback on this experimental product. Produnto allows users to use Lua modules hosted in [[gitlab:repos/lua|Wikimedia's GitLab]]. It simplifies the sharing of Lua code between wikis. Instead of copying each individual Lua module from one wiki to another, users will be able to easily share packages across all wikis.
* [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.47/wmf.22|MediaWiki]]

'''Meetings and events'''
* A [[m:Event:Cross-wiki Code Collaboration Workshop|Cross-wiki code collaboration workshop]] will be held online on October 2 at 12:30 UTC, bringing together South Asian technical contributors to learn about Produnto and begin piloting it on Hindi, Punjabi, Odia, Telugu, and Malayalam Wikipedias. Produnto is a package manager for deploying Lua modules hosted on GitLab to Wikimedia wikis, and was recently deployed on some pilot wikis.

'''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2026/40|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2026-W40&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 10:49, 28 September 2026 (UTC)
&lt;!-- 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&amp;oldid=31092225 --&gt;

== Wikipedia translation of the week: 2026-41 ==
&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:it:Battaglia del pastificio]]'''&lt;br /&gt; &lt;small&gt;''([[:en:Battle of Checkpoint Pasta]])''&lt;/small&gt; &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:OTO Melara Somalia 1993.jpg|300px|center|]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
La '''battaglia del pastificio''', talvolta chiamata anche battaglia del checkpoint Pasta, fu uno scontro a fuoco verificatosi a Mogadiscio tra le truppe italiane e le milizie Mooryaan somale del generale Aidid ed è ricordata per essere stata la prima battaglia che vide impiegati i militari dell'Esercito Italiano dalla fine della seconda guerra mondiale. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 12:39, 5 October 2026 (UTC)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=31108366 --&gt;

== Tech News: 2026-41 ==
&lt;section begin=&quot;technews-2026-W41&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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/41|Translations]] are available.

'''Weekly highlight'''
* The process for this year’s Community Wishlist [[m:Special:MyLanguage/Community Wishlist/Community Wishlist 2027#Updated Community Wishlist Process 2027/2028|has been published]], incorporating community feedback. The wish submission process will [[m:Special:MyLanguage/Community Wishlist/FAQ#What is the deadline for submitting wishes?|end on November 8]]. This year, [[m:Special:MyLanguage/Community Wishlist/Community Wishlist 2027/Working group|a working group (open for volunteering)]] that includes community members familiar with the technical aspect of our wikis alongside Wikimedia Foundation staff, will take care of the [[m:Special:MyLanguage/Community Wishlist/FAQ#What is triage?|triage process]]. The triage is expected to be completed by late November. Votes for wishes will start in January.

'''Updates for editors'''
* Editors using the [[mw:Special:MyLanguage/VisualEditor|visual editor]] will now see a warning when they paste text that is likely to have initially been copied from one of five external generative AI chatbots into Wikipedia. This feature is known as [[mw:Special:MyLanguage/Edit check/LLM Paste Check|LLM Paste Check]]. It is a type of [[mw:Special:MyLanguage/Edit check|Edit Check]] that is community configurable. The check looks for markers in the copied HTML and is not using content watermark detection. Edits will also [[mw:Special:MyLanguage/Edit check/LLM Paste Check#Edit tags|be tagged]] so that patrollers can review them more closely. The feature helps newcomers add content that respects Wikipedia’s policies and makes it easier for experienced editors to identify problematic edits. Communities with local policies about LLM usage can [[mw:Special:MyLanguage/Edit check/LLM Paste Check#Configuration|adjust the wording and policy that is linked]]. The team [[listarchive:list/translators-l@lists.wikimedia.org/message/EVHKWJ4IERZELMPIWNH3XUVUSQV5KOO4/|apologizes]] that this was rolled out without a delay for translations.
* Editors can now easily [[mw:Special:MyLanguage/Wikimedia Apps/Team/Future of Editing on the Mobile Apps|access the web visual editor directly from the iOS and Android apps]]. When opening the editor, users will be given a choice between visual editing and source editing. If they choose visual editing, they will be sent to a mobile web window in their phone's browser. After completing their edit, a banner will give them the option to return to the app. This enables readers to make quick contributions while casually reading.
* Users of the Wikipedia Android and iOS apps will now see a one-time account creation prompt after they have used the app for two consecutive weeks. This prompt explains the benefits of having an account. It is intended to help more casual readers become logged-in users who return to the apps regularly. [https://phabricator.wikimedia.org/T434847]
* Editors on [[wmnoc:conf/dblists/group1.dblist|group1 wikis]], including Wikiquote, Wikibooks, Wikiversity, Wikivoyage, and Wikisource, will no longer see notifications on [[mw:Special:MyLanguage/Help:Recent changes|Recent Changes]] and [[mw:Special:MyLanguage/Help: Watching pages|Watchlist]] when a link to another language version of a page is added, removed, or changed in its Wikidata item. This change will begin on October 5 at 07:00 UTC as a two-week trial to reduce high-volume, low-value notifications and make important changes easier to identify. Editors who rely on these notifications can read more on the [[m:Wikidata For Wikimedia Projects/Clearer Wikidata Edit Summaries/Hide Language Link edits|project page]] and share feedback or concerns on the [[m:Talk:Wikidata_For_Wikimedia_Projects/Clearer_Wikidata_Edit_Summaries/Hide_Language_Link_edits|talk page]]. [https://phabricator.wikimedia.org/T439415]
* [[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, an issue where mentors who removed themselves from the mentorship program could still have mentees assigned to them and receive questions, has now been fixed. Mentees will now be reassigned when a mentor leaves the program. [https://phabricator.wikimedia.org/T418194]

'''Updates for technical contributors'''
* Wikimedia Brasil has published its [[m:Special:MyLanguage/Wikimedia Brasil/Arcabouço de Boas Práticas de Desenvolvimento|Development Best Practices Framework]] (ABPD). It is a guide for staff, contractors and volunteers building technical tools and projects. It covers the project lifecycle, security, accessibility, personal data protection and responsible AI use, and explains how movement-wide guidelines were adapted to a local context. They encourage other affiliates to reuse it and adapt it. Read more in the [[wmfblog:2026/09/26/wikimedia-brasils-development-best-practices-framework-technical-sustainability-as-an-organizational-responsibility|Diff post]]. 
* A new, canonical base URL for Wikimedia APIs will soon be introduced. The new canonical route follows a &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;{projectName}/api/&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt; pattern and will act as an alternative path for current REST APIs (for example: &lt;bdi lang=&quot;zxx&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;nowiki&gt;{projectName}/w/rest.php/&lt;/nowiki&gt;&lt;/code&gt;&lt;/bdi&gt;). Both versions will be callable for all existing APIs, but the new structure will be the preferred path for newly created API modules. This change will be non-breaking for most users. The existing pathways will remain available for all existing endpoint requests. However, some endpoints may return URLs following the new pattern in response bodies. Changes will be available on test wiki first, with the rollout expected to cover all wikis by the end of October. [https://phabricator.wikimedia.org/T433535]
* [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.47/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]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2026/41|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2026-W41&quot;/&gt;

18:52, 5 October 2026 (UTC)
&lt;!-- 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&amp;oldid=31098825 --&gt;

== Wikipedia translation of the week: 2026-42 ==
&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; style=&quot;width:100%; margin:0; background: var(--background-color-neutral-subtle,#f8f9fa); border:1px solid var(--border-color-base,#BBBBBB); padding .4em;color: inherit;&quot;&gt;
&lt;div style=&quot;text-align:center;&quot;&gt;The winner this [[m:Translation of the week/2026 translations|Translation of the week]] is

&lt;div style=&quot;font-size:140%;&quot;&gt;'''[[:en:The Trolleybus Museum at Sandtoft]]'''&lt;br /&gt;  &lt;/div&gt;
Please be bold and help translate this article!
&lt;/div&gt;
----
[[File:Lineup.5.JPG|300px|center|]]
&lt;div style=&quot;text-align:left; padding: .4em;&quot;&gt;
'''The Trolleybus Museum at Sandtoft''' is a transport museum which specialises in the preservation of trolleybuses. It is located by the village of Sandtoft, near Belton on the Isle of Axholme in the English county of Lincolnshire. 

&lt;small&gt;(Please update the interwiki links on [[d:|Wikidata]] of your language version of the article after each week's translation is finished so that all languages are linked to each other.)&lt;/small&gt;
----
[[File:TOTW.svg|24px|]]  ''[[m:Translation of the week|About]] · '''[[m:Translation of the week/Translation candidates|Nominate/Review]]''' · [[m:Translation of the week/MassMessage|Subscribe/Unsubscribe]] · [[m:MassMessage|Global message delivery]]''
&lt;/div&gt;
&lt;/div&gt;
--[[User:MediaWiki message delivery|MediaWiki message delivery]] ([[User talk:MediaWiki message delivery|discuss]] • [[Special:Contributions/MediaWiki message delivery|contribs]]) 02:09, 12 October 2026 (UTC)
&lt;!-- Message sent by User:Shizhao@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=Translation_of_the_week/MassMessage&amp;oldid=31131525 --&gt;

== Tech News: 2026-42 ==
&lt;section begin=&quot;technews-2026-W42&quot;/&gt;&lt;div class=&quot;plainlinks&quot;&gt;
Latest '''[[m:Special:MyLanguage/Tech/News|tech 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/42|Translations]] are available.

'''Weekly highlight'''
* Starting October 13, wikis can change the default pattern for [[:en:Wikipedia:VisualEditor/Named references|auto-generated reference names in VisualEditor]] (currently &lt;syntaxhighlight lang=&quot;wikitext&quot; inline&gt;&lt;ref name=&quot;:1&quot; /&gt;&lt;/syntaxhighlight&gt;). They will be able to use human-readable, content-based reference names that are more helpful to contributors using the source editor (e.g. &lt;syntaxhighlight lang=&quot;wikitext&quot; inline&gt;&lt;ref name=&quot;Miller2026-1&quot; /&gt;&lt;/syntaxhighlight&gt;). VisualEditor reference name patterns can be defined using MediaWiki system messages, JSON, templates and modules ([[:mw:Special:MyLanguage/Help:Cite/VisualEditor reference names|more information]]). Admins can enable these changes via [[Special:CommunityConfiguration/Cite-VisualEditor-Autonames|community configuration]]. This is a [[:m:Special:MyLanguage/Community_Wishlist/W17|community wish]] implemented by [[:m:Special:MyLanguage/WMDE Technical Wishes|WMDE Technical Wishes]]. [https://phabricator.wikimedia.org/T436255]
* [[m:Special:MyLanguage/WMDE Technical Wishes/Sub-referencing|Sub-referencing]] is a new MediaWiki feature that allows editors to reuse references with different details. It will be deployed to English Wikipedia on October 14 and to remaining Wikimedia Foundation wikis by end of October (likely October 21). The [[m:Special:MyLanguage/WMDE Technical Wishes/Sub-referencing#deployment|FAQ]] lists possible actions to take on your wiki to support the deployment. This is a [[:m:WMDE Technical Wishes/Sub-referencing/History|long-standing community wish]] implemented by [[:m:Special:MyLanguage/WMDE Technical Wishes|WMDE Technical Wishes]]. [https://phabricator.wikimedia.org/T440243][https://phabricator.wikimedia.org/T440304]

'''Updates for editors'''
* [[mw:Special:MyLanguage/Moderator Tools|Moderator Tools]] will be removing the list view of the Watchlist and defaulting everyone to the changelog view. Previously, there were two versions of how the Watchlist is shown to mobile web users: the list view, where editors could see watched articles in a list format, and the changelog view, where editors could see changes to watched articles in a log format, controlled by a user's Advanced Mobile Control settings. This has created issues for code-base maintenance: two different displays means two sets of code to manage. By defaulting to the changelog view, we are simplifying the codebase and avoiding the likelihood of missing bugs.
* The Wikipedia Android app is testing a way to listen to article introductions in the “For you” feed. A text-to-speech model reads the existing article text aloud without rewriting it or adding any content. The 30-day experiment will begin in the Wikipedia Beta app during the third week of September, then move to the regular Wikipedia Android app in October for a limited group of eligible users. A small portion of app users (those with English feeds and at least one topic interest) will have access to the feature. This experiment is part of broader efforts to give app readers options in how they consume content in order to deepen engagement and user retention. [[mw:Special:MyLanguage/Readers/Listening to Wikipedia/Phase 1|Learn more]] and [[mw:Talk:Readers/Listening to Wikipedia|share feedback]].
* [[mw:Special:MyLanguage/Help:Extension:CodeMirror|CodeMirror syntax highlighting]] was [[phab:T288161|enabled]] by default for all logged out and newly registered users on the English Wikipedia on September 14. With no signs of adverse effects, the same change is being proposed to be made globally across all wikis in a few weeks. If you have concerns or feedback, or if your wiki would like to opt out, [[mw:Special:MyLanguage/Help talk:Extension:CodeMirror#Enabling CodeMirror by default on all WMF wikis for newbies|please see the help page]]. [https://phabricator.wikimedia.org/T440077]
* [[d:Wikidata:Usability_and_usefulness/Item_editing_experience/Mobile_editing_of_statements|Wikidata mobile statement editing]] of all datatypes will be officially launched on October 13, when it will be removed from Wikidata [[d:Special:Preferences#mw-prefsection-betafeatures|beta features]] and become available to all editors. Users can [[d:Wikidata_talk:Usability_and_usefulness/Item_editing_experience/Mobile_editing_of_statements|report bugs and share feedback]].
* Last week, language link changes were removed from [[Special:RecentChanges|Recent Changes]] and [[Special:Watchlist|Watchlist]] feeds on Wikivoyage, Wikisource, Wikiversity, Wikiquote and Wiktionary. As no adverse effects have been observed, the [[m:Wikidata_For_Wikimedia_Projects|Wikidata For Wikimedia Projects]] plans to roll out this change globally to all Wikipedias. This is scheduled for October 13 at 07:00 UTC, after which editors will no longer see when a link to ''another'' language version of a page is added, removed, or changed in its Wikidata item. Editors who rely on these notifications can read more on the [[m:Wikidata For Wikimedia Projects/Clearer Wikidata Edit Summaries/Hide Language Link edits|project page]] and share feedback or ask to opt out their wiki on the [[m:Talk:Wikidata_For_Wikimedia_Projects/Clearer_Wikidata_Edit_Summaries/Hide_Language_Link_edits|talk page]]. [https://phabricator.wikimedia.org/T440698]
* [[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, an issue where accidentally touching the graph while scrolling on the Pageviews tool on mobile could unintentionally zoom in has now been fixed. Click-and-drag zoom is now disabled on touch devices. [https://phabricator.wikimedia.org/T440075]

'''Updates for technical contributors'''
* There are three major changes coming to dumps: the legacy content dumps [https://lists.wikimedia.org/hyperkitty/list/xmldatadumps-l@lists.wikimedia.org/thread/E6D5EU4PMSTSOI2J7A46HJ3YW2W554CS/ deprecated in January 2026] will now be sunset, the replacement [https://wikitech.wikimedia.org/wiki/MediaWiki_Content_File_Exports MediaWiki Content File Exports] will be delayed to implement a “safety buffer”, and they are now also available as 7zip-compressed files. Users will need to switch the URL they download their dump from. For more information, timeline and migration instructions, see [https://wikitech.wikimedia.org/wiki/Legacy_content_dumps_sunset Legacy content dumps sunset].
* [[File:Reload icon with two arrows.svg|12px|link=|class=skin-invert|Recurrent item]] Detailed code updates later this week: [[mw:MediaWiki 1.47/wmf.24|MediaWiki]]

'''In depth'''
* The Wikimedia Foundation discovered unauthorized activity by OpenAI agents on Wikimedia projects, including edits to wikis, attempts to exploit a public note-taking tool, and heavy automated traffic. [[diffblog:2026/10/05/openai-rogue-agent-activities-found-on-wikimedia-projects/|Read the blog post on Diff]] for more details about the activity and the Foundation’s response.

'''Meetings and events'''
* Save the date for the next Wikimedia Hackathon! We’ll be meeting in lovely Tirana, Albania for the [https://www.mediawiki.org/wiki/Wikimedia%20Hackathon%202027 2027 Wikimedia Hackathon] from April 9–11, 2027. Scholarship and staff sponsorship applications are currently being [https://pretix.eu/wikimedia/Hackathon-2027/ accepted through Pretix] and will close on October 30, 2026. General registration will open in January 2027.

'''''[[m:Special:MyLanguage/Tech/News|Tech news]]''' prepared by [[m:Special:MyLanguage/Tech/News/Writers|Tech News writers]] and posted by [[m:Special:MyLanguage/User:MediaWiki message delivery|bot]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News#contribute|Contribute]]&amp;nbsp;• [[m:Special:MyLanguage/Tech/News/2026/42|Translate]]&amp;nbsp;• [[m:Tech|Get help]]&amp;nbsp;• [[m:Talk:Tech/News|Give feedback]]&amp;nbsp;• [[m:Global message delivery/Targets/Tech ambassadors|Subscribe or unsubscribe]].''
&lt;/div&gt;&lt;section end=&quot;technews-2026-W42&quot;/&gt;

&lt;bdi lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[User:MediaWiki message delivery|MediaWiki message delivery]]&lt;/bdi&gt; 07:40, 13 October 2026 (UTC)
&lt;!-- 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&amp;oldid=31142468 --&gt;</text>
      <sha1>jmbx75f8qpt4xq6fzefh6s1fwppey29</sha1>
    </revision>
  </page>
  <page>
    <title>Simple Guide to Minecraft/Overworld/Structures</title>
    <ns>0</ns>
    <id>456607</id>
    <revision>
      <id>4675755</id>
      <parentid>4339055</parentid>
      <timestamp>2026-10-12T17:25:17Z</timestamp>
      <contributor>
        <username>~2026-54879-79</username>
        <id>3628262</id>
      </contributor>
      <comment>/* Villages */</comment>
      <origin>4675755</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3791" sha1="49xl285eovnu1qzfpd7ivtj9t067svb" xml:space="preserve">{{bookcat}}
= Important Structures in the Overworld =
The Overworld in Minecraft is replete with fascinating structures that dot the landscape, each holding its own secrets, challenges, and rewards. These structures provide players with opportunities for exploration, valuable loot, and unique gameplay experiences. Here are some of the notable structures you can discover in the Overworld:

== Villages ==
Villages are bustling communities inhabited by peaceful villagers. They consist of various buildings, including houses, farms, libraries, and blacksmiths. Villages offer a wide range of trades, allowing players to exchange resources for valuable items, enchantments, and rare enchanted books. Exploring villages can also reveal hidden chests containing useful loot. Players can either interact with villagers or defend the village from hostile mobs and zombie sieges on java edition. Players also must occasionally defend the village from illager raids.

== Strongholds ==
Strongholds are vast underground structures shrouded in mystery and danger. These fortresses house the End Portal, which serves as a gateway to the challenging dimension known as the End. Strongholds are filled with winding corridors, libraries, prison cells, and grand halls. Players must navigate through complex mazes, fend off silverfish, and solve puzzles to locate the End Portal room. Exploring strongholds is crucial for those seeking to battle the formidable Ender Dragon.

== Mineshafts ==
Mineshafts are intricate networks of tunnels and corridors that stretch underground, often intersecting with ravines or caves. They contain minecart rails, wooden supports, and minecart chests filled with valuable resources such as ores, melon seeds, and enchanted books. Players must be cautious of cave spiders, who inhabit these mineshafts and can inflict poison. Exploring mineshafts allows for resource gathering and the potential discovery of hidden treasures.

== Temples ==
Temples come in two varieties:

=== Desert Temples ===
Desert Temples are pyramid-like structures found in deserts, containing a tnt trap in the middle and a hidden chamber in the center  filled with valuable loot such as enchanted books, diamonds, and gold.

=== Jungle Temples ===
Jungle Temples, on the other hand, are elaborate structures hidden within jungle biomes, featuring puzzles and traps guarding their treasure-filled chests. Temples offer a thrilling challenge for players who dare to uncover their secrets.

== Witch Huts ==
Witch Huts are solitary structures that appear in swamp biomes. They are small, wooden huts with a cauldron and a brewing stand, indicating the presence of a witch. Players can find loot such as potions, redstone components, and glass bottles inside these huts. Beware, for the witch within will defend her abode fiercely, casting harmful potions and using her powerful magic against intruders.

== Abandoned Mineshafts ==
Abandoned Mineshafts are decrepit versions of mineshafts, overrun by cobwebs and infested with cave spiders. These structures provide players with opportunities to gather resources like ores, minecart chests, and rails. Players must exercise caution due to the presence of cave spider spawners and the potential danger of collapsing tunnels. Navigating these abandoned mineshafts can yield valuable rewards for resourceful adventurers.

== Conclusion ==
The Overworld's structures offer a wealth of adventure, treasure, and unique gameplay elements. Exploring these structures allows players to gather valuable resources, unlock hidden loot, and engage with the diverse inhabitants of the Minecraft world. Understanding the nature and challenges posed by each structure will aid players in their quest for exploration and discovery in the vast and dynamic Overworld.</text>
      <sha1>49xl285eovnu1qzfpd7ivtj9t067svb</sha1>
    </revision>
  </page>
  <page>
    <title>Math for Non-Geeks/The Bolzano-Weierstrass theorem</title>
    <ns>0</ns>
    <id>472643</id>
    <revision>
      <id>4675754</id>
      <parentid>4674608</parentid>
      <timestamp>2026-10-12T16:38:39Z</timestamp>
      <contributor>
        <username>Sascha Lill 95</username>
        <id>3167325</id>
      </contributor>
      <minor />
      <comment>[[WB:REVERT|Reverted]] edit by [[Special:Contributions/Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|talk]]) to last version by Sascha Lill 95</comment>
      <origin>4674596</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="17339" sha1="8shzpzthzislz4d6jrhw4fz89sk6pag" xml:space="preserve">{{#invoke:Math for Non-Geeks/Seite|oben}}

This article concerns a theorem that can be useful for many proofs in real analysis (and also in deeper maths topics): the &lt;dfn&gt;Bolzano-Weierstrass theorem&lt;/dfn&gt;. It is named after [[w:Bernard Bolzano|Bernard Bolzano]] and [[w:Karl Weierstraß|Karl Weierstraß]].

This theorem guarantees that there are accumulation points whenever a sequence is bounded. It is crucial for proving existence of limits (or at least accumulation points) for such sequences. One may also carry through these proofs using nested intervals, but it is often shorter to just use the Bolzano-Weierstrass theorem - which already makes use of nested intervals. 

Some textbooks use the Bolzano-Weierstrass theorem to prove validity of the monotonicity criterion for sequences and series. One may also go the other way round and prove the Bolzano-Weierstrass theorem if the monotonicity criterion is known to hold. Another implication of the Bolzano-Weierstrass theorem is that continuous functions on a compact interval &lt;math&gt;[a,b]&lt;/math&gt; with &lt;math&gt;a,b\in \R&lt;/math&gt; and &lt;math&gt;a \le b&lt;/math&gt; are bounded and take a minimum and a maximum value.

== The Bolzano-Weierstrass theorem ==
[[File:Satz von Bolzano-Weierstraß - Quatematik.webm|thumb|A visual explanation for the Bolzano-Weierstrass theorem - video in German. ([https://www.youtube.com/watch?v=GrvNQK7-kBs YouTube-video] by [https://www.youtube.com/channel/UC0LfPSALkn8YDhXZf8-Pl5A Quatematik])]]
[[File:Bernard Bolzano Kriehuber.jpg|thumb|125px|class=noprint|Bernard Bolzano]]
[[File:Karl Weierstrass.jpg|thumb|125px|class=noprint|Karl Weierstrass]]
The Bolzano-Weierstrass theorem reads as follows:

{{:Math for Non-Geeks: Template:Satz
 |titel=Bolzano-Weierstrass theorem
 |satz=
Every bounded sequence &lt;math&gt;(x_n)_{n\in\N}&lt;/math&gt; of real numbers has at least one accumulation point. That means, there is a real number &lt;math&gt;x&lt;/math&gt;, such that at least one subsequence &lt;math&gt;\left(x_{n_k}\right)_{k\in\N}&lt;/math&gt; of &lt;math&gt;(x_n)_{n\in\N}&lt;/math&gt; converges to &lt;math&gt;x&lt;/math&gt;.}}

You can intuitively justify this theorem as follows: A sequence is bounded if and only if all of its infinitely many elements fit inside the finite interval &lt;math&gt;[s,S]&lt;/math&gt; . Putting infinitely many points in a finite interval will necessarily make it crowded. So there should be some regions with a lot of points, crowding very closely together. The Bolzano-Weierstrass theorem now states that around one point &lt;math&gt;x&lt;/math&gt; , there are infinitely many points in each &lt;math&gt; \epsilon &lt;/math&gt;-neighbourhood. No matter how small &lt;math&gt; \epsilon &lt;/math&gt; is. This &lt;math&gt;x&lt;/math&gt; is an accumulation point. Note that &lt;math&gt;x&lt;/math&gt; does not need to be part of the sequence, and there may be multiple (even uncountably infinitely many) of those &lt;math&gt;x&lt;/math&gt;.

{{:Math for Non-Geeks: Template:Hinweis|Often, the Bolzano-Weierstrass theorem is formulated in the literature as follows: &quot;Every real and bounded sequence has a convergent subsequence&quot;. This formulation is equivalent to the above one.}}

== Why the completeness axiom is necessary ==
Completeness of the real numbers &lt;math&gt; \R &lt;/math&gt; means that each Cauchy sequence within &lt;math&gt; \R &lt;/math&gt; converges to an element in &lt;math&gt; \R &lt;/math&gt;. Roughly speaking, a Cauchy sequence is a sequence which &quot;looks as if it would converge&quot; and it will be precisely defined elsewhere. For now, you need to know that in &lt;math&gt; \R &lt;/math&gt; and &lt;math&gt; \mathbb{Q} &lt;/math&gt;, a Cauchy sequence is any sequence with a limit in &lt;math&gt; \R &lt;/math&gt;. Some of these sequences in &lt;math&gt;\mathbb{Q}&lt;/math&gt; converge to an element in &lt;math&gt; \R \setminus \mathbb{Q} &lt;/math&gt;, e.g.  &lt;math&gt; (a_n)_{n \in \N}, a_n = \left( 1 + \tfrac 1n \right)^n \to e &lt;/math&gt;. The limit &lt;math&gt; e &lt;/math&gt; would be the only possible accumulation point of &lt;math&gt; (a_n)_{n \in \N} &lt;/math&gt;. But &lt;math&gt; e \notin \mathbb{Q} &lt;/math&gt;. So &lt;math&gt; (a_n)_{n \in \N} &lt;/math&gt; has no limit in &lt;math&gt; \mathbb{Q} &lt;/math&gt;, which means the Bolzano-Weierstrass theorem cannot hold for &lt;math&gt; \mathbb{Q} &lt;/math&gt;.

The above example shows that the domain of the sequence elements is crucial for the Bolzano-Weierstrass theorem to hold. The complete &lt;math&gt; \R &lt;/math&gt; does work, whereas the incomplete &lt;math&gt; \mathbb{Q} &lt;/math&gt; does not. Mathematicians call a subset of &lt;math&gt;\R&lt;/math&gt; ''compact'' if every sequence with terms in that set has a subsequence converging to a limit in the same set. For instance, any bounded and closed interval &lt;math&gt; [s,S] &lt;/math&gt; is compact. Finite unions of these intervals are compact, too. The real numbers &lt;math&gt; \R &lt;/math&gt; are ''not compact'', since the Bolzano-Weierstrass theorem only guarantees an accumulation point if the sequence is bounded within some &lt;math&gt; [s,S] &lt;/math&gt;. Generally, unbounded subsets of &lt;math&gt;\R&lt;/math&gt; are not compact.

== Proof (by nested intervals) ==
{{:Math for Non-Geeks: Template:Beweis
 |titel=Bolzano-Weierstrass theorem
 |beweis=
Let &lt;math&gt;(x_n)_{n\in\N}&lt;/math&gt; be a bounded sequence. We know that there is a lower bound &lt;math&gt;s&lt;/math&gt; and an upper bound &lt;math&gt;S&lt;/math&gt; , such that all sequence elements lie in &lt;math&gt;[s,S]&lt;/math&gt; :

[[File:Bolzano–Weierstrass theorem - step 1.svg|center|400px|A bounded sequence and its lower and upper bounds]]

Now, we need to find an accumulation point of the sequence. Certainly, the completeness of &lt;math&gt;\R&lt;/math&gt; will be necessary, which we introduced via nested intervals. Recall: Nested intervals &lt;math&gt;I_n=[a_n,b_n]&lt;/math&gt; are a way to approximate any real number &lt;math&gt;x&lt;/math&gt;. Here, &lt;math&gt;a_n&lt;/math&gt; is a lower bound and &lt;math&gt;b_n&lt;/math&gt; an upper bound for &lt;math&gt;x&lt;/math&gt;. So &lt;math&gt;x&lt;/math&gt; is included in each of the nested intervals &lt;math&gt;[a_n, b_n]&lt;/math&gt;. Nested means that &lt;math&gt; [a_{n+1}, b_{n+1}] \subseteq [a_n, b_n] &lt;/math&gt; for all &lt;math&gt; n \in \N &lt;/math&gt;, so the intervals are included in each other and their widths cannot increase. 

If the width of the intervals converges to &lt;math&gt;0&lt;/math&gt;, then &lt;math&gt; x &lt;/math&gt; is indeed the only element included in all intervals &lt;math&gt;x \in[a_n,b_n]&lt;/math&gt; for all &lt;math&gt; n \in \N &lt;/math&gt;.

So if we can construct a sequence of nested intervals which are all including infinitely many points of the sequence &lt;math&gt;(x_n)_{n\in\N}&lt;/math&gt; , then there must be a point &lt;math&gt; x &lt;/math&gt; included in all intervals &lt;math&gt;[a_n, b_n]&lt;/math&gt;. This &lt;math&gt; x &lt;/math&gt; is a good candidate for an accumulation point of &lt;math&gt;(x_n)_{n\in\N}&lt;/math&gt;, as there are infinitely many sequence elements around it.

How do we find such a sequence of nested intervals containing infinitely many sequence elements? The interval &lt;math&gt;I_1 := [s,S]&lt;/math&gt; certainly contains infinitely many sequence elements &lt;math&gt;x_n&lt;/math&gt; (namely, all of them).

[[File:Bolzano–Weierstrass theorem - step 2.svg|center|400px|The first interval]]

Now, we need to make &lt;math&gt;I_1 &lt;/math&gt; smaller. So let us divide &lt;math&gt;I_1 &lt;/math&gt; into two equally large sub-intervals:

[[File:Bolzano–Weierstrass theorem - step 3.svg|center|400px|Splitting the interval in two equal parts]]

Since the sequence &lt;math&gt;(x_n)_{n\in\N}&lt;/math&gt; contains infinitely many elements, at least one of the two sub-intervals also has to contain infinitely many elements of &lt;math&gt;(x_n)_{n\in\N}&lt;/math&gt;. Otherwise, there would be only finitely many sequence elements, which is not the case. We define this interval with infinitely many elements as &lt;math&gt;I_2&lt;/math&gt;.

[[File:Bolzano–Weierstrass theorem - step 4.svg|center|400px|The second interval]]

We can repeat the step and split &lt;math&gt;I_2&lt;/math&gt; into two equal parts:

[[File:Bolzano–Weierstrass theorem - step 5.svg|center|400px|Splitting the second interval]]

The next interval &lt;math&gt;I_3&lt;/math&gt; is chosen as exactly that part of &lt;math&gt;I_2&lt;/math&gt;, which in turn contains infinitely many sequence elements. One of the two parts of &lt;math&gt;I_2&lt;/math&gt; has to contain infinitely many elements, since there are infinitely many elements in &lt;math&gt;I_2&lt;/math&gt; and otherwise, we would only have finitely many elements available. So we can indeed find a suitable &lt;math&gt;I_3&lt;/math&gt; with half the width of &lt;math&gt;I_2&lt;/math&gt;:

[[File:Bolzano–Weierstrass theorem - step 6.svg|center|400px|The third interval]]

We iterate this procedure arbitrarily many times and get a sequence of nested intervals &lt;math&gt;(I_n)_{n\in\N}&lt;/math&gt; , where each &lt;math&gt;I_{n+1}&lt;/math&gt; has half the width of &lt;math&gt;I_n&lt;/math&gt;.

Mathematically, we can describe this inductive procedure as follows: We set &lt;math&gt;I_1:=[s,S]&lt;/math&gt;. In each step, for &lt;math&gt;I_k=[a_k,b_k]&lt;/math&gt; we define the middle of the interval as &lt;math&gt;M=\tfrac 12 (a_k+b_k)&lt;/math&gt; and choose

{{Math|&lt;math&gt;I_{k+1} = [a_{k+1},b_{k+1}] = \begin{cases}
\;[ a_k,M ] &amp; \text{if } [a_k,M] \text{ contains infinitely many } x_n \\ 
\;[ M,b_k ] &amp; \text{else}
\end{cases}&lt;/math&gt;}}

Indeed, the width of &lt;math&gt;I_k&lt;/math&gt; is cut into half in each step:

{{Math|&lt;math&gt;\begin{align}
|I_1| &amp; = |S-s| \\
|I_2| &amp; = \frac 12 |I_1| = \frac 12 |S-s| \\
|I_3| &amp; = \frac 12 |I_2| = \frac 1{2^2} |S-s| \\ 
|I_4| &amp; = \frac 12 |I_3| = \frac 1{2^3} |S-s| \\
&amp; \vdots \\
|I_k| &amp; = \frac 12 |I_{k-1}| = \frac 1{2^{k-1}} |S-s| \quad (k \ge 2)
\end{align}&lt;/math&gt;}}

Here, &lt;math&gt;|I_k|&lt;/math&gt; is the width of interval number &lt;math&gt;k&lt;/math&gt;. Hence,

{{Math|&lt;math&gt;|I_k| = \frac 1{2^{k-1}} |S-s| \xrightarrow{k\to\infty} 0&lt;/math&gt;}}

The interval width tends to &lt;math&gt;0&lt;/math&gt; . So there must be a unique point &lt;math&gt;x&lt;/math&gt;, which is included in all intervals &lt;math&gt;I_k&lt;/math&gt;. This &lt;math&gt;x&lt;/math&gt; is the desired accumulation point candidate.

Let us finish the proof by verifying that &lt;math&gt;x&lt;/math&gt; is indeed an accumulation point. For any &lt;math&gt;\epsilon&gt;0&lt;/math&gt; , we consider the &lt;math&gt;\epsilon&lt;/math&gt;-neighbourhood  &lt;math&gt;(x-\epsilon, x+\epsilon)&lt;/math&gt; of &lt;math&gt;x&lt;/math&gt;. Since &lt;math&gt;\lim_{n\to\infty} |I_n|=0&lt;/math&gt; , there must be an &lt;math&gt;N\in\N&lt;/math&gt; with &lt;math&gt;|I_N|&lt;\epsilon&lt;/math&gt;. And since &lt;math&gt;x\in I_N&lt;/math&gt; there is &lt;math&gt;I_N\subseteq (x-\epsilon,x+\epsilon)&lt;/math&gt; (visualize this on a piece of paper or in your head). But now, we constructed the intervals such that they all contain infinitely many elements &lt;math&gt;(x_n)_{n\in\N}&lt;/math&gt; . So also &lt;math&gt;I_N&lt;/math&gt; and &lt;math&gt; (x-\epsilon,x+\epsilon) \supseteq I_N &lt;/math&gt; contain infinitely many elements.

Since this works for any &lt;math&gt;\epsilon&gt;0&lt;/math&gt; , we verified that &lt;math&gt;x&lt;/math&gt; is an accumulation point of &lt;math&gt;(x_n)_{n\in\N}&lt;/math&gt; , which was to be shown.}}

== Proof (alternatively via monotonicity criterion) ==

A further way to prove the Bolzano-Weierstrass theorem goes by the ''monotonicity criterion''. This criterion says that every monotone and bounded sequence of real numbers converges.

Boundedness is one of the assumptions of the Bolzano-Weierstrass theorem. So if we can establish that there is a monotone subsequence, we know that it must converge, which is what we want to show. Can we select such a subsequence? The answer is yes, as the following theorem will prove:

{{:Math for Non-Geeks: Template:Satz
 |satz=
Every real sequence has a monotone subsequence.

 |titel=Bolzano Weierstrass selection criterion 
 |erklärung=|beispiel=|zusammenfassung=|lösungsweg=
How can we select a monotone subsequence? Let's try to find a strictly monotonically decreasing subsequence, first. It is good to select an element &lt;math&gt;a_m &lt;/math&gt; with as many of the following elements smaller than it, i.e. &lt;math&gt;a_n &lt; a_m&lt;/math&gt; for &lt;math&gt;n&gt;m&lt;/math&gt;, as possible. If there are no such elements, we can definitely ''not'' proceed in selecting more elements for a strictly monotonically decreasing sequence. If there are only finitely many elements like this, we will sooner or later run out of elements to select, so this should also be avoided. By contrast, the best case is if  &lt;math&gt;a_n &lt; a_m&lt;/math&gt; for ''all'' &lt;math&gt;n&gt;m&lt;/math&gt;. We will call &lt;math&gt;a_m &lt;/math&gt; a ''&quot;peak element&quot;'' in that case.

As an example, we may consider the sequence &lt;math&gt;(a_n)_{n \in \N}&lt;/math&gt; with &lt;math&gt;a_n = \begin{cases} \tfrac 1n &amp; \text{for } n \text{ odd,} \\
0 &amp; \text{for } n \text{ even,}  \end{cases}&lt;/math&gt;, i.e. the sequence &lt;math&gt;(1,0,\tfrac 13,0,\tfrac 15,0,\tfrac 17,0,\tfrac 19, \ldots)&lt;/math&gt;. 

All odd indices &lt;math&gt;1,3,5,7,9,\ldots&lt;/math&gt; correspond to &quot;peak elements&quot;, since &lt;math&gt;a_1=1&gt;a_n&lt;/math&gt; for all &lt;math&gt;n&gt;1&lt;/math&gt;, &lt;math&gt;a_3=\tfrac 13&gt;a_n&lt;/math&gt; for all &lt;math&gt;n&gt;3&lt;/math&gt; and so on. So there are infinitely many peak element indices &lt;math&gt;2k-1&lt;/math&gt; for &lt;math&gt;k\in \N&lt;/math&gt;. If we proceed selecting one peak element after the other, we will certainly end up with a monotonically decreasing sequence:

{{Math|&lt;math&gt;(a_{2k-1})_{k \in \N} = (1,\tfrac 13, \tfrac 15, \tfrac 17, \tfrac 19, \ldots )&lt;/math&gt;}} 

If &lt;math&gt;m_k&lt;/math&gt; denotes the index of the (peak) element &lt;math&gt;a_{m_k}&lt;/math&gt; , then this element must be smaller than all the previous elements &lt;math&gt;a_{m_1},a_{m_2}, \ldots ,a_{m_{k-1}}&lt;/math&gt;, since they were peak elements, too. So &lt;math&gt;a_{m_1}&gt;a_{m_2}&gt;\ldots &gt;a_{m_{k-1}}&gt;a_{m_k}&lt;/math&gt;. That means, whenever the sequence &lt;math&gt;(a_n)&lt;/math&gt; has infinitely many &quot;peak elements&quot;, we can select a monotonically decreasing subsequence &lt;math&gt;(a_{m_k})_{k \in \N}&lt;/math&gt;. 

And what if we cannot find infinitely many &quot;peak points&quot;? Consider the following example:

Let &lt;math&gt;(a_n)_{n \in \N}&lt;/math&gt; be the sequence with &lt;math&gt;a_n = (-1)^n \tfrac{n}{n+1}&lt;/math&gt;, i.e. &lt;math&gt;(-\tfrac 12,\tfrac 23,-\tfrac 34,\tfrac 45,-\tfrac 56,\tfrac 67,-\tfrac 78,\tfrac 89,-\tfrac{9}{10}, \ldots)&lt;/math&gt;.

[[File:Sequence with two accumulation points (subsequences colored differently).svg|center|500px|The sequence a_n=(-1)^n*n/(n+1)]]

This sequence has ''no'' peak points ''at all'': The odd indices &lt;math&gt;2k-1&lt;/math&gt; have negative elements, which are situated below the even elements &lt;math&gt;2k&lt;/math&gt; , i.e. &lt;math&gt;a_{2k-1}&lt;0&lt;a_{2k}&lt;/math&gt;. However, the even indices &lt;math&gt;2k&lt;/math&gt; can also not contain peak points, since the subsequence of even-indexed elements is monotonically increasing: &lt;math&gt;(a_{2k})_{k \in \N} = (\tfrac 23,\tfrac 45,\tfrac 67,\tfrac 89, \ldots)&lt;/math&gt;. So there is always an &lt;math&gt;n&gt;2k&lt;/math&gt; with &lt;math&gt;a_{2k}&lt;a_n&lt;/math&gt;. But the even-indexed subsequence &lt;math&gt;(a_{2k})_{k \in \N}&lt;/math&gt; is already a monotone subsequence!  It is only monotonically ''increasing'', instead of decreasing.

Is there always such a monotonically increasing subsequence, if we cannot find any ''peak elements''? The answer is yes: If we selected &lt;math&gt; a_m &lt;/math&gt;, which is not a peak point and there is also no peak point after it, then there is some &lt;math&gt; a_n &lt;/math&gt; with &lt;math&gt; n&gt;m &lt;/math&gt;, with &lt;math&gt; a_n \ge a_m &lt;/math&gt;. Otherwise, &lt;math&gt; a_m &lt;/math&gt; would be a peak point. So we can select &lt;math&gt; a_n &lt;/math&gt; as the next element of the subsequence, which is again not a peak point. Now the same assumptions hold for &lt;math&gt; a_n &lt;/math&gt;, as for &lt;math&gt; a_m &lt;/math&gt; (not a peak point and no peak points after it) and we can choose a further subsequence element greater than or equal to &lt;math&gt;a_n&lt;/math&gt;. This step is repeated iteratively and renders an infinite subsequence &lt;math&gt;(a_{n_k})_{k\in \N}&lt;/math&gt; of &lt;math&gt;(a_n)&lt;/math&gt;.

The argument even runs through, if there are finitely many peak points: If &lt;math&gt;m_1,m_2, \ldots m_r&lt;/math&gt; are peak element indices, then &lt;math&gt;n_1 = m_r+1&lt;/math&gt; is not a peak point and has no peak points after it. So it can be used as a starting point for a construction. If there are no peak elements at all, we instead start with &lt;math&gt;n_1 = 1&lt;/math&gt;.

We recap: if there are ''finitely many'' peak points, we are able to construct a monotonically increasing subsequence. If there are ''infinitely many'' peak points, we just choose them as a monotonically decreasing subsequence. In any case, there is a monotone subsequence.

 |beweis=

'''Case 1:''' &lt;math&gt;(a_n)&lt;/math&gt; has infinitely many peak element indices &lt;math&gt;m_1&lt;m_2&lt; \ldots &lt;m_k&lt;m_{k+1}&lt;\ldots&lt;/math&gt;. Then, the subsequence &lt;math&gt;(a_{m_k})_{k \in \N}&lt;/math&gt; is by definition (strictly) monotonically decreasing.

'''Case 2:''' &lt;math&gt;(a_n)&lt;/math&gt; has finitely many peak elements. If there is at least one, list their indices as &lt;math&gt;m_1 &lt; m_2 &lt; \ldots &lt; m_r&lt;/math&gt; and set &lt;math&gt;n_1 = m_r+1&lt;/math&gt;. If there are none, set &lt;math&gt;n_1 = 1&lt;/math&gt;. Then choose &lt;math&gt;n_2 &gt; n_1&lt;/math&gt; with &lt;math&gt;a_{n_2} \ge a_{n_1}&lt;/math&gt;, and iteratively for all &lt;math&gt;k \ge 2&lt;/math&gt;: &lt;math&gt;n_{k+1} &gt; n_k&lt;/math&gt; with &lt;math&gt;a_{n_{k+1}} \ge a_{n_k}&lt;/math&gt;. This is possible, since every index &lt;math&gt;n \ge n_1&lt;/math&gt; corresponds to an element that is not a peak element. The subsequence &lt;math&gt;(a_{n_k})_{k \in \N}&lt;/math&gt; is then monotonically increasing.
}}

The above Bolzano-Weierstrass selection principle makes it very easy to prove the Bolzano-Weierstrass theorem:

{{:Math for Non-Geeks: Template:Beweis
 |titel=alternative proof for the Bolzano-Weierstrass theorem
 |beweis=
Let &lt;math&gt;(a_n)_{n \in \N}&lt;/math&gt; be a bounded real sequence. The Bolzano-Weierstrass selection principle shows that there is a monotone subsequence &lt;math&gt;(a_{n_k})_{k \in \N}&lt;/math&gt;. Since &lt;math&gt;(a_n)&lt;/math&gt; is bounded, so is &lt;math&gt;(a_{n_k})&lt;/math&gt; . The monotonicity criterion then implies convergence of &lt;math&gt;(a_{n_k})&lt;/math&gt;. Therefore, &lt;math&gt;(a_n)&lt;/math&gt; has a convergent subsequence and hence an accumulation point.
}}

{{#invoke:Math for Non-Geeks/Seite|unten}}

{{BookCat}}</text>
      <sha1>8shzpzthzislz4d6jrhw4fz89sk6pag</sha1>
    </revision>
  </page>
  <page>
    <title>Hereditary Multiple Exostoses</title>
    <ns>0</ns>
    <id>484817</id>
    <revision>
      <id>4675737</id>
      <parentid>4674916</parentid>
      <timestamp>2026-10-12T13:52:53Z</timestamp>
      <contributor>
        <username>LoveElectronicLiterature</username>
        <id>3414389</id>
      </contributor>
      <comment>fixed acronyms</comment>
      <origin>4675737</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="118410" sha1="j401bxuurdx20542g88jg2dko6a3x99" xml:space="preserve">{{new book}}
[[W: Hereditary Multiple Exostoses|Hereditary Multiple Exostoses]] (HME) is a rare disease. It is also referred to as Multiple Hereditary Exostoses (MHE), Hereditary Multiple Osteochondromas (HMO), and Multiple Osteochondromas (MO). 

== Bone Issues ==
The first sign of HME is usually multiple bone tumors. See the online Multiple Osteochondromas Mutation Database  for an overview of the reported variants.&lt;ref&gt;{{Cite journal |last=Jennes |first=Ivy |last2=Pedrini |first2=Elena |last3=Zuntini |first3=Monia |last4=Mordenti |first4=Marina |last5=Balkassmi |first5=Sahila |last6=Asteggiano |first6=Carla G. |last7=Casey |first7=Brett |last8=Bakker |first8=Bert |last9=Sangiorgi |first9=Luca |last10=Wuyts |first10=Wim |date=2009 |title=Multiple osteochondromas: mutation update and description of the multiple osteochondromas mutation database (MOdb) |url=https://onlinelibrary.wiley.com/doi/abs/10.1002/humu.21123 |journal=Human Mutation |language=en |volume=30 |issue=12 |pages=1620–1627 |doi=10.1002/humu.21123 |issn=1098-1004}}&lt;/ref&gt;  In MHE, the lack of HSPG causes patients to develop exostoses, which are benign tumors in multiple locations throughout the body (Brown 2008, Thompson 2011, and Mansouri et al. 2017). The severity (number and size of tumors and other complications) for MHE varies from patient to patient. Exostoses themselves can cause numerous problems including: irritation of tendons and muscles resulting in pain and loss of motion, skeletal deformity, short stature, limb length discrepancy, subluxations, and angular deformity, with a chance for chondrosarcoma (Fei et al. 2018). Problems directly associated with these exostoses include:

* Chronic pain and issues with quality of life (Goud et al. 2012,&lt;ref name=&quot;:9&quot;&gt;{{Cite web |title=Pain, Physical and Social Functioning, and... : Journal of Bone and Joint Surgery |url=https://www.ovid.com/jnls/jbjsjournal/fulltext/10.2106/jbjs.k.00406~pain-physical-and-social-functioning-and-quality-of-life-in |access-date=2026-07-16 |website=Ovid |language=en |doi=10.2106/JBJS.K.00406}}&lt;/ref&gt; Bathen et al. 2019, Tremorsini 2025)
* Inflammation, immune responses (Callaghan et al. 2018, Collins and Troeberg 2019)  
* Bursa formation (Rueda et al. 2025) and resulting bursitis as well as early onset arthritis 
* Breathing and lung issues when on ribs protruding into the thoracic cavity (Mazza et al. 2017)
*  Irritation of a nearby nerve (pain, weakness, numbness, tingling) 
*  Blood vessel aneurysm from exostoses pressing on blood vessels or other vascular problems (Albokhari et al. 2023)
* Spinal cord compression issues: incontinence, nerve damage and nerve problems associated with spinal tumors (Bari et al. 2012, Burki et al. 2011, Zaijun et al. 2013, Montgomery et al. 2019, and Monroig-Rivera et al. 2025)

== List of associated issues ==
'''Heparan Sulfate ProteoGlycan (HSPG) Deficiency Issues.''' MHE results from a mutation in the EXT1 and EXT2 genes.  MHE patients have defective HSPG biosynthesis--their bodies do not produce HSPG ('''cf''' Cueller et al. 2013, Jones et al,. 2014, and Pacifici et al. 2019&lt;ref name=&quot;:7&quot;&gt;{{Cite journal |last=Pacifici |first=Maurizio |date=2018-10 |title=The pathogenic roles of heparan sulfate deficiency in hereditary multiple exostoses |url=https://pmc.ncbi.nlm.nih.gov/articles/PMC6015767/ |journal=Matrix Biology: Journal of the International Society for Matrix Biology |volume=71-72 |pages=28–39 |doi=10.1016/j.matbio.2017.12.011 |issn=1569-1802 |pmc=6015767 |pmid=29277722}}&lt;/ref&gt;).  HSPGs are part of every cell surface and regulate biological processes ( '''cf''' Zak et al. 2002, Meneghetti et al. 2015). HSPGs  play a vital role in cell adhesion, migration, growth, and communication (Bishop et al. 20017, Kempf et al 2017, Vicente et al. 2018). Whitlock and Iozzo (2005) have identified '''various diseases related to HSPG's absence''' (i.e., i'''f a body process requires HSPG and there is not enough HSPG to complete that function, then these issues could occur).  MHErs reported symptoms such as:'''

* Severe and continuing fatigue (Berg et al. 1999, Bathen 2019) 
* Neurological deficiencies: Autism Spectrum Disorder (Fumitoshi et al. 2012,  Irie et al, 2012, Yamaguchi 2012, Perez et al. 2015, Kambouris et al. 2016, Kim et al 2022); cognitive issues (Farhan et al. 2015); tremors (Aldunate et al. 2004). 
* Sleep disorders (Clark 2022, Chen 2023)
* Vertigo and hyperacusis (Lundberg et al., 2014) 
* Low bone mass (Nozawa et al. 2018 and Matsumoto et al. 2020) 
* Severe gastric issues  (Huang et al. 2018, Rueda et al. 2025) , including non ''H. Pylori'' ulcers (Ascencio et al. 1993 and Chmiela et al. 1995), gastric cancer (Weihua et al. 2002) and Cyclic Vomiting Syndrome (Kucukesmen et al. 2007)
* Fronto-temporal dementia (Narvid et al. 2009) and ADHD (Mooney et al. 2016), brain function (Condomitti and Wit 2018). Also see video of MHE mice at &lt;nowiki&gt;https://www.youtube.com/watch?v=6-EXRt_YL6A&lt;/nowiki&gt;.
* Eyesight/ocular diseases (Park and Shukla, 2013)
* Dental defects (Kucukesmen et al. 2007 and Wiweger et al. 2012)
* Prediabetes  (Heibert 2021)Diabetes and glucose difficulty (Matsuzawa 2021)
* Unusual drug reactions (many drugs act on heparan-binding domain [Boer and Gaillard 2007])
* Kidney stones and other problems (See Van den Born et al. 1993 and Farhan et al. 2015)
* Lung issues (Nackerts et al. 1997 and Haeger et al. 2016)
* Anemia (Poli et al. 2017), blood clots and coagulation (Stringer and Gallagher 1997 and Ho et al. 1997), psuedoaneurysms (Wiater and Farley 1996 and Harari et al. 2024)
* Extremely painful menstruation and pregnancy issues (Alphin et al. 1988, Yin et al. 2018)
* Inflammation (Parish 2005); slow wound healing (Zhongjun et al. 2004); scarring and keloids  (Hosalkar et al. 2007)
* Connective tissue issues (Forsberg and Kjellen, 2001 and Otsuka et al. 2020).
* Liver functions (Arnold et al. 2020 and Dituri et al. 2022)
* Cholesterol and lipid functions (Kolsett and Salmverta 1999)
* Deficient Vitamin D synthesis (Cooper 2021)

== Children's Corner ==

=== Teach your child to live with MHE ===
You just got a diagnosis for your child and you are terrified for their life.  Yeah, MHE sucks. And it is a life-long, untreatable disease. Sure you can have surgery, sure, physical therapy helps. But the underlying condition will be there every day for the rest of your life. So. How can you prepare your child to live successfully with MHE?

* '''Believe their pain.''' MHE can have some strange symptoms. Even the bones can subluxate (go in and out) within seconds, so the kid who could not walk two minutes ago is running now. Believe your child. Do not let the doctors gaslight you or your child into pretending that nothing is wrong.
* '''Let your child master their pain.''' Give your child as much control and autonomy as possible. Provide a &quot;pain corner&quot; with comfy pillows, their favorite toys, quiet activities, warmies or coolies. Let your child go to that pain area whenever they feel the need--when they are tired or in pain. This lets them regulate their own pain and functions. 
* '''Teach your child to brainstorm and plan around problems.''' Pain and limited mobility may limit certain options, but life still goes on. So when your child can not do something, brainstorm with them. Use your imaginations. You can not climb these steps. Ok, how can you get into the room? Can you slide on your butt? Should we get a giraffe from next door to help out? (Throw in silly suggestions because that expands their imagination and puts a bit of humor into the situation.) 

=== Advocate for your child with HME in schools ===
It is vital to advocate for your child so that they can work well in schools. Here are some suggested ways to ask for accommodations for this complex disease. Note that not every child will need all of these accommodations. 

My child has MHE, which involves bony bumps on their bones that can vary in size, location, and number as well as some neurological and other physical symptoms.Accommodations are needed for my child’s symptoms, which include:

*  '''Limited mobility.&lt;ref name=&quot;:1&quot;&gt;{{Cite journal |last=Amajjar |first=Ihsane |last2=Vergauwen |first2=Kuni |last3=Willigenburg |first3=Nienke W. |last4=Huijnen |first4=Ivan P. J. |last5=Smeets |first5=Rob J. E. M. |last6=Ham |first6=S. John |date=2025-05-30 |title=Physical activity level and health-related quality of life in adults with multiple osteochondromas: a Dutch cross-sectional study |url=https://www.nature.com/articles/s41598-025-02812-3 |journal=Scientific Reports |language=en |volume=15 |issue=1 |pages=18990 |doi=10.1038/s41598-025-02812-3 |issn=2045-2322}}&lt;/ref&gt;''' Allow my child to participate in sports and in activities to the best of their abilities. When starting something new, allow my child to go last and ask my child privately if they can perform that action. If not, quietly allow them to pursue a different prearranged activity. Note that mobility changes daily and sometimes hourly, depending on the bone growth stages, whether muscle has moved over a bone growth,  or other complications.
*  '''Neurological symptoms'''. My child has Asperger-like and ADHD symptoms,&lt;ref name=&quot;:4&quot;&gt;{{Cite journal |last=Irie |first=Fumitoshi |last2=Badie-Mahdavi |first2=Hedieh |last3=Yamaguchi |first3=Yu |date=2012-03-27 |title=Autism-like socio-communicative deficits and stereotypies in mice lacking heparan sulfate |url=https://www.pnas.org/doi/abs/10.1073/pnas.1117881109 |journal=Proceedings of the National Academy of Sciences |volume=109 |issue=13 |pages=5052–5056 |doi=10.1073/pnas.1117881109}}&lt;/ref&gt;&lt;ref name=&quot;:5&quot;&gt;{{Cite journal |last=Irie |first=Fumitoshi |last2=Badie-Mahdavi |first2=Hedieh |last3=Yamaguchi |first3=Yu |date=2012-03-27 |title=Autism-like socio-communicative deficits and stereotypies in mice lacking heparan sulfate |url=https://pnas.org/doi/full/10.1073/pnas.1117881109 |journal=Proceedings of the National Academy of Sciences |language=en |volume=109 |issue=13 |pages=5052–5056 |doi=10.1073/pnas.1117881109 |issn=0027-8424 |pmc=3323986 |pmid=22411800}}&lt;/ref&gt;&lt;ref name=&quot;:8&quot;&gt;{{Cite journal |last=Pérez |first=Christine |last2=Sawmiller |first2=Darrell |last3=Tan |first3=Jun |date=2016-04-18 |title=The role of heparan sulfate deficiency in autistic phenotype: potential involvement of Slit/Robo/srGAPs-mediated dendritic spine formation |url=https://doi.org/10.1186/s13064-016-0066-x |journal=Neural Development |language=en |volume=11 |issue=1 |pages=11 |doi=10.1186/s13064-016-0066-x |issn=1749-8104 |pmc=4836088 |pmid=27089953}}&lt;/ref&gt; so please engage all measures for children on the spectrum as well as ADHD. Bone tumors on the spine can also create neurological issues.&lt;ref name=&quot;:2&quot;&gt;{{Cite web |url=https://www.semanticscholar.org/paper/Hereditary-multiple-exostoses-causing-cord-Bari-Alam/4687ea7d1225f1ecf4ecf4742a794f84576dce6d/figure/0 |access-date=2026-07-15 |website=www.semanticscholar.org}}&lt;/ref&gt; Please understand that bright lights or sound may cause pain or other issues. Please report any behavioral issues so that we can determine if MHE may be underlying these problems and we can address the issues with reasonable accommodations and an Individual Education Plan.
*  '''Frequent pain and fatigue&lt;ref name=&quot;:0&quot;&gt;{{Cite journal |last=Mitchell |first=Christina M. |last2=Beals |first2=Janette |last3=Whitesell |first3=Nancy Rumbaugh |last4=Voices of Indian Teens team |last5=Pathways of Choice team |date=2008-09 |title=Alcohol use among American Indian high school youths from adolescence and young adulthood: a latent Markov model |url=https://pubmed.ncbi.nlm.nih.gov/18781241 |journal=Journal of Studies on Alcohol and Drugs |volume=69 |issue=5 |pages=666–675 |issn=1937-1888 |pmc=2575396 |pmid=18781241}}&lt;/ref&gt;'''. If my child is in pain or is tired, allow them to rest in preplanned area with preplanned quiet activities (reading, watching an educational video, etc.). This area should be equipped with a heating pad and medication should be dispensed as agreed upon by me and the school.  
* '''Writing difficulties'''.&lt;ref name=&quot;:1&quot; /&gt; My child may have extra bones on their wrists or hands, making writing painful. Please allow my child to use a computer.  Typing may be slow and please allow other software such as Dragon Naturally Speaking or Otter AI.
*  '''Coordination difficulties'''. My child may have neurological difficulties and problems coordinating eyesight. Please allow more time for tests if needed. Administer tests that require filling in bubbles in an alternative method.
* '''Incontinence/Vomiting'''. Please allow my child free access to the restroom without requiring a pass for sudden issues. Keep a spare set of clothing at the school in case of accidents.
* '''Hall passes.'''  Give my child access to the nurse and bathroom as they determine that they need to go. My child may have bathroom urgencies or need to get pain medication quickly. My child may also have a limb that has &quot;gone out&quot; or stopped working for a few seconds to a few days and will need to attend to that medical urgency. 

=== Advocation Laws and Directives ===
In U.S. cite Section 504 of the Rehabilitation Act.


= How to Respond to Doctors =
There are suggested treatment protocols for MHE (see Rueda et al., 2025). However, MHE is a rare disease, and you will probably be the first patient that a medical practitioner has ever seen with this disease.  Try to be patient with the doctors and get doctors who work with you as a partner--you having lived with MHE do know a lot about your body! Ill-informed or too-busy doctors often rely on research that is outdated or inaccurate. Here are some common misconceptions that a doctor might tell you and how to respond. Before you go to the doctor, write out your questions. Take someone with you to take notes. Advocate for yourself! 

1.'''I have never seen an MHE patient. Surely this is just a bone condition!''' The condition involves much more than bone growths. MHErs do not biosynthesize heparan sulfate proteoglycans (HSPG), in much the same way that diabetics do not biosynthesize insulin (see Cueller et al. 2013 and Jones et al. 2014). Those HSPGs play a vital role in pretty much every single cell and every system in a human body (Bishop et al. 2017). Therefore, since I do not have sufficient levels of HSPG, I can have many different problems. Let's rule out anything comorbid (in other words, any other disease I might have at the same time). IF we can not find something to explain the cause of my symptoms of {REPEAT YOUR SYMPTOMS HERE} then we can blame the MHE and treat the symptoms.

'''2. You do not feel pain. It is just stress.'''  Bone does not have nerves, therefore there is no pain.  Even if that were true (which it is not--see Nencini and Ivanusic 2016&lt;ref name=&quot;:6&quot;&gt;{{Cite journal |last=Nencini |first=Sara |last2=Ivanusic |first2=Jason J. |date=2016-04-26 |title=The Physiology of Bone Pain. How Much Do We Really Know? |url=https://www.frontiersin.org/journals/physiology/articles/10.3389/fphys.2016.00157/full |journal=Frontiers in Physiology |language=English |volume=7 |doi=10.3389/fphys.2016.00157 |issn=1664-042X |pmc=4844598 |pmid=27199772}}&lt;/ref&gt; for example ), then you wouldn't mind putting a stone in your shoe, right? Because the stone would not feel any pain. Oh, you wouldn't like that because it might hurt? Really? Ok. So I have an extra bone (LIKE A STONE) where there should only be muscle, nerve, and ligaments (LIKE A FOOT). For MHE-specific pain studies, see Darilek et al. 2005.

3. '''Your MHE did not cause x symptom.'''  I had one MHE patient (or read a case study) and they did not have x symptom, so therefore you do not have x symptom (or x symptom is unrelated). MHE is a rare and complex disease. Sometimes medical professionals will resort to explanations of hypochondria or Munchausens to explain away something that they do not understand. MHE is different for each patient, as there are different genetic mutations (EXT1, EXT2, EXT3 genes all play a role, as well as your other genetic profiles). There is not enough research to determine whether your symptoms are or are not caused by MHE. It is best to work with a doctor who will look for causes and accept that your MHE is not the same as anyone else's--including your own family members. Also, look at the list below for similar case studies on HME.  

'''4. No one else has had that reaction to that drug. You are lying or mistaken.''' No. HSPG plays a role in nearly every body function and is assumed to be present. My body does not produce HSPG. Therefore my drug interactions may well differ!&lt;ref name=&quot;:3&quot;&gt;{{Cite journal |last=Boer |first=A. G. de |last2=Gaillard |first2=P. J. |date=2007-02-10 |title=Drug Targeting to the Brain |url=https://www.annualreviews.org/content/journals/10.1146/annurev.pharmtox.47.120505.105237 |journal=Annual Review of Pharmacology and Toxicology |language=en |volume=47 |issue=Volume 47, 2007 |pages=323–355 |doi=10.1146/annurev.pharmtox.47.120505.105237 |issn=0362-1642}}&lt;/ref&gt;  

5. '''The bones do not grow past puberty. If they have, then it is cancer.''' While studies have assumed this, it is not true. This has not been well researched, because it is difficult to have full xrays and to monitor over a lifetime, which would be required for absolute proof. But while there is a slight chance of chondrosarcoma, other MHE patients have reported bone growth past puberty. See the pictures of the 92- year old woman's skeleton with MHE. Bones grew back over her surgeries at age 70 and 80. If bones do not grow back, how do you explain the growths on her implants?

=== Questions to ask doctors if you are not being taken seriously ===
'''Scripts to Use When You Feel Dismissed'''

'''• This is affecting my daily life. I can not function well with this problem.''' Show pictures. Keep a diary of your pain and what you are not able to do. For example: When the tumor on my rib prevents me from raising my arm, I can not dress myself or brush my hair. When the fatigue is so bad, I can not go to class. When the pain is over a 5 (slamming your hand in a car door) continually, then I can not think well.

'''• Yes, the test results you got were normal, but I have problems.''' However, there are no tests for Heparan Sulfate Proteoglycans, which may play a role. Therefore, we need to look deeper. I still have these issues. Explain again that you have MHE and do not biosynthesize HSPG, which plays a role in every cell. Look for common problems--because of course you can still have those! But do not let the doctor gaslight you into thinking it is all in your head. If nothing else, look in Google Scholar with HSPG and your symptom. 

'''• I’m still concerned. Can we talk about next steps?'''  What can we do, and how long should we wait to see if that step works? Ask again about your specific symptom. There may be a medication to try, or physical therapy. Note what you have tried--keep a record!

'''Scripts for When Symptoms Are Minimized'''

'''• This may seem mild to you, but this is really affecting my life.''' Again, be specific. Use the analogy of a rock in your shoe or anything else that makes sense to you.

'''• I'm a zebra. I have a rare complex disease. What can we do?''' Again remind them that MHE is a complex systemic disease and the extra bones are only one symptom of a wider range of problems stemming from not biosynthesizing  HSPG. 

• '''While this may seem mild, I think it is part of an overall pattern. This symptom is persistent and worsening, which is why I’m concerned.''' (Keep a diary. Keep images over time). 

'''Scripts for Redirecting the Conversation'''

'''• I know my body is complex. But here is my main issue now--let's focus on that'''. Before your appointment, write out and send a list of your main symptoms. This is a complex disease and you will not get to everything.

• '''Can we  go back to what I mentioned earlier?''' I know that everything is connected, but I am most concerned about ... so I can live my life. Keep that list. Have someone else in the room taking notes on that list of symptoms. 

'''• Please send me a copy of my medical chart.''' I want to be sure my concern is documented in my chart. Always ask for a copy of your medical records, including doctors' notes.

'''Scripts for Asking for Clarification'''

• “Can you explain why you don’t think further evaluation is needed?” (MHE is a life long condition.)

• “What would be a red flag that should prompt me to follow up?” (Ask about red flags for chondrosarcoma)

• “If this doesn’t improve, what’s the next step?” (Get referrals.)

= See also (MHE sites) =
MHE Learning System&lt;ref&gt;{{Cite web |title=Home - MHE Learning System |url=https://mhels.org/ |access-date=2026-09-30 |website=mhels.org |language=en}}&lt;/ref&gt; a site for MHE patients to learn about the disease and to cope. 

MHE Research Foundation&lt;ref&gt;{{Cite web |title=Home |url=https://www.mherf.org/ |access-date=2026-09-30 |website=website |language=en}}&lt;/ref&gt; a site to share MHE research.

= Research and medical studies =
Italics after a citation is a sentence directly from that work that summarizes the main points for HME patients and their doctors. Please go to the actual study cited. 

== HME Specific studies ==

=== Summary studies ===
'''Rueda-de-Eusebio, A., Gomez-Pena, S., Moreno-Casado, M.J. et al. Hereditary multiple exostoses: an educational review. Insights Imaging 16, 46 (2025). &lt;nowiki&gt;https://doi.org/10.1186/s13244-025-01899-6&lt;/nowiki&gt;''' ''  This review summarises current knowledge on the clinical presentation, pathogenesis, imaging characteristics, complications, and treatment of HME.''

=== Autism and neurological issues ===
'''Yamaguchi, Yu. Research on rare bone disorder reveals new insights into autism. &lt;nowiki&gt;https://www.eurekalert.org/news-releases/857331&lt;/nowiki&gt; March 2012,''' ''Sanford-Burnham researchers discover the molecular basis of autistic symptoms in children with a rare bone disorder -- findings that also provide new insights for the general autistic population.Researchers at Sanford-Burnham Medical Research Institute (Sanford-Burnham) used a mouse model of MHE to investigate cognitive function. They found that mice with a genetic defect that models human MHE show symptoms that meet the three defining characteristics of autism: social impairment, language deficits, and repetitive behavior.''

See associated video presentations:

[https://www.youtube.com/watch?v=9SmRRG03zxo Yu Yamaguchi, M.D., Ph.D. - Consequences of Genetic Deficiency]

'Heparan Sulfate, Hereditary Multiple Exostoses, and Autism: Insight from a Rare Disease for a Common Disease&quot; at the Third Annual Rare Disease Day Symposium at Sanford-Burnham Medical Research Institute. The symposium took place at Sanford-Burnham's La Jolla campus on February 24, 2012 and the focus was Glycosylation-Based Disorders: Discovery, Patients, and Progress Toward Treatments.&lt;ref&gt;{{Citation |last=Sanford Burnham Prebys |title=Yu Yamaguchi, M.D., Ph.D. |date=2012-03-05 |url=https://www.youtube.com/watch?v=6-EXRt_YL6A |access-date=2026-09-10}}&lt;/ref&gt;

Heparan Sulfate and Human Diseases, March 5, 2012.&lt;ref&gt;{{Cite web |title=Yu Yamaguchi, M.D., Ph.D. |url=https://www.google.com/search?hl=en-US&amp;hl=en&amp;client=mobilesearchapp&amp;sca_esv=16067ccfc9d0a6cf&amp;channel=iss&amp;rlz=1MDAPLA_enUS667US667&amp;v=437.4.973319807&amp;q=yu+yamaguchi+video&amp;docid=8EyS2A5A5MmJHM&amp;ibp=video&amp;shem=epsd1,ivsple,rimspwouoe&amp;shndl=41&amp;shmd=H4sIAAAAAAAA_42Rz24TMRDGVeDUN4DTqAcqoc0mjUC0kSqUNG0DYkubRKjtbeqdjU3W9uIZN9kbD8UD8Cw8Aw-AFwTiABInW_Pnm983s_vt0e7jmwg3aHEVlTYZFPk0z-BSp-fJWos0POr3yanQNkJlT-7cIF-xoBiVK2_7JnUSv_p4nDKj8UV5dK6u3hWzKb-_qm6ro_nJ4banr882L9qLw_CB2nYwtJNC3Rer2Uu3vOXx9eYpHx8Mnn19-E-QDHwFC3SVD2VvEoPTaKGg0iisYU5MGJSG147FSBSCJqSYEwZtGATrdQZ7-zNqMKCDRawrFMpgRiFJCIYWiliLaWqC061n8UycAboSxlEM21EnbVZaoAreAsIcA8HUpLlMkKBS6MRb692v4B6ggGiCpTYhyTgXO9I_26bYwqK1jWcTbVf-__7yJEvAv5vF-zU0NSr6i84-w1uEN76uERTaJjIkzjO6C7FzPnyewXBwMPxhtyOuvEolG2Q4r1vlua3Tqb3rTRJ02dEnbQo86r7K31No05FSSbfvn0u7DH6VDsCw9BtM7peBUGyXz7dfHnza-bzzHdtbemZ3AgAA&amp;shmds=v1_ARwrE22JjgnjP0eJT9xgIFMVGTFJDAswWntiJI2oXY3-HEfR1A&amp;source=sh/x/vid/m1/5&amp;kgs=82929becb69767fb&amp;utm_source=epsd1,ivsple,rimspwouoe,sh/x/vid/m1/5#fpstate=ive&amp;vld=cid:911b02e3,vid:6-EXRt_YL6A,st:0 |access-date=2026-09-10 |website=www.google.com}}&lt;/ref&gt;

=== Pain, disability, and fatigue ===
'''Amajjar I, Vergauwen K, Willigenburg NW, Huijnen IPJ, Smeets RJEM, Ham SJ, 2025, Scientific report. Physical activity level and health-related quality of life in adults with multiple osteochondromas: a Dutch cross-sectional study. 2045-2322, 2025 May 30, Vol. 15, Issue 1'''&lt;ref name=&quot;:1&quot; /&gt; ''Multiple Osteochondromas (MO) can significantly impact physical functioning,..These results underscore the need for targeted interventions focusing on pain management, psychological factors, and lifestyle changes to improve both PAL and HRQOL in MO patients.''

'''Bathen T, Fredwall S, Steen U, 2019. Fatigue and pain in children and adults with multiple osteochondromas in Norway, a cross-sectional study. International journal of orthopaedic and trauma nursing [Int J Orthop Trauma Nurs] 2019 Aug; Vol. 34, pp. 28-35. Date of Electronic Publication: 2019 Feb 10.  ISSN: 18781241''' &lt;ref name=&quot;:0&quot; /&gt; ''Background: Multiple Osteochondromas (MO) is a rare skeletal disorder frequently needing orthopaedic surgery. High prevalence of pain has been reported, however fatigue has not previously been investigated.'' ''Results: Children with MO reported significantly higher fatigue than healthy children. Adults reported significantly higher fatigue than the general Norwegian population. Six of 11 children and 20 of 21 adults reported pain. Severe fatigue was more prevalent in persons with high age, high pain intensity and many pain locations; however none of these differences were significant.''

'''Darilek, Sandra MS*; Wicklund, Catherine MS†; Novy, Diane PhD‡; Scott, Allison MD§; Gambello, Michael MD, PhD*; Johnston, Dennis PhD¶; Hecht, Jacqueline PhD*. Hereditary Multiple Exostosis and Pain. Journal of Pediatric Orthopaedics 25(3):p 369-376, May 2005. | DOI: 10.1097/01.bpo.0000150813.18673.''' ''This study was undertaken to characterize pain in individuals with hereditary multiple exostosis (HME).  Eighty-four percent of participants reported having pain, indicating that pain is a real problem in HME.''

'''Goud, A. L., de Lange, J., Scholtes, V. A. B., Bulstra, S. K., &amp; Ham, S. J. (2012). Pain, Physical and Social Functioning, and Quality of Life in Individuals with Multiple Hereditary Exostoses in the Netherlands. Journal of Bone and Joint Surgery-American Volume, 94A(11), 1013-1020. &lt;nowiki&gt;https://doi.org/10.2106/JBJS.K.00406&lt;/nowiki&gt;.'''&lt;ref name=&quot;:9&quot; /&gt; ''Our study confirms that multiple hereditary exostoses is a chronic disease causing a profound impact on quality of life. The results suggest that pain is not the only problem associated with multiple hereditary exostoses, as it has an extensive influence on daily activities, as well as on social and psychological well-being, causing significant disability.''

'''Tremosini, M., Morri, M., Forni, C., Pedrini, E., Mordenti, M., Gnoli, M., Di Cecco, A., Moroni, A., &amp; Sangiorgi, L. (2025). Pain in patients with multiple inherited osteochondromas: Incidence and potential prognostic factors. Journal of Bone Oncology, 52, 100672.''' ''Purpose: the purpose of this study was to describe the baseline characteristics, presenting phenotype and treatment interventions for patients diagnosed with multiple osteochondromas who presented with severe pain'' ''symptoms. .Conclusion: from the early stages of multiple osteochondromas diagnosis, pain symptoms must be carefully assessed. An increase in age is associated with a worsening of pain; IOR classification of the multiple osteo-chondromas phenotype does not currently allow an association between the various classes and pain. A re-evaluation of the classification in this light could be an important new element for clinical practice.''

=== Bone growth complications ===
'''Burki, Vincent, Alexander So, Bérengère Aubry-Rozier, 2011. Cervical myelopathy in hereditary multiple exostoses, Joint Bone Spine, Volume 78, Issue 4, &lt;nowiki&gt;https://doi.org/10.1016/j.jbspin.2011.02.021&lt;/nowiki&gt;'''&lt;ref&gt;{{Cite journal |last=Burki |first=Vincent |last2=So |first2=Alexander |last3=Aubry-Rozier |first3=Bérengère |date=2011-07 |title=Cervical myelopathy in hereditary multiple exostoses |url=https://linkinghub.elsevier.com/retrieve/pii/S1297319X11000558 |journal=Joint Bone Spine |language=en |volume=78 |issue=4 |pages=412–414 |doi=10.1016/j.jbspin.2011.02.021}}&lt;/ref&gt;'''.''' ''Spinal cord compression due to cervical exostoses is a rare but recognized complication of hereditary multiple exostosis (HME), an autosomal dominant disorder. This disease, also called multiple osteochondromatosis, is characterised by osteocartilaginous exostoses, typically involving the juxtaepiphyseal regions of long bones. Complications such as transformation to sarcoma (1 to 5%) or neurological compression (of the spinal cord, 1 to 9%) can arise during the course of the disease.''

'''Bukowska-Olech Ewelina, Trzebiatowska Wiktoria, Czech Wiktor, Drzymała Olga, Frąk Piotr, Klarowski Franciszek, Kłusek Piotr, Szwajkowska Anna, Jamsheer Aleksander, Hereditary Multiple Exostoses—A Review of the Molecular Background, Diagnostics, and Potential Therapeutic Strategies. &lt;nowiki&gt;https://www.frontiersin.org/article/10.3389/fgene.2021.759129&lt;/nowiki&gt; '''&lt;ref&gt;{{Cite journal |last=Bukowska-Olech |first=Ewelina |last2=Trzebiatowska |first2=Wiktoria |last3=Czech |first3=Wiktor |last4=Drzymała |first4=Olga |last5=Frąk |first5=Piotr |last6=Klarowski |first6=Franciszek |last7=Kłusek |first7=Piotr |last8=Szwajkowska |first8=Anna |last9=Jamsheer |first9=Aleksander |date=2021-12-10 |title=Hereditary Multiple Exostoses—A Review of the Molecular Background, Diagnostics, and Potential Therapeutic Strategies |url=https://www.frontiersin.org/journals/genetics/articles/10.3389/fgene.2021.759129/full |journal=Frontiers in Genetics |language=English |volume=12 |doi=10.3389/fgene.2021.759129 |issn=1664-8021 |pmc=8704583 |pmid=34956317}}&lt;/ref&gt; ''' '''''Hereditary multiple exostoses (HMEs) syndrome, also known as multiple osteochondromas, represents a rare and severe human skeletal disorder. The disease may severely affect the quality of patients’ life due to motion impairments, skeletal deformations, chronic pain, or growth retardation and possibility of malignant transformation of exostoses.''

'''Matsumoto, K., Ogawa, H., Nozawa, S. et al. An analysis of osteoporosis in patients with hereditary multiple exostoses. Osteoporos Int 31, 2355–2361 (2020). &lt;nowiki&gt;https://doi.org/10.1007/s00198-020-05533-7&lt;/nowiki&gt;'''&lt;ref&gt;{{Cite journal |last=Matsumoto |first=K. |last2=Ogawa |first2=H. |last3=Nozawa |first3=S. |last4=Akiyama |first4=H. |date=2020-12-01 |title=An analysis of osteoporosis in patients with hereditary multiple exostoses |url=https://doi.org/10.1007/s00198-020-05533-7 |journal=Osteoporosis International |language=en |volume=31 |issue=12 |pages=2355–2361 |doi=10.1007/s00198-020-05533-7 |issn=1433-2965}}&lt;/ref&gt; ''We analyzed osteoporosis in 20 HME patients. Our results indicate HME patients have low bone mass. They do not have abnormal bone metabolism.''

'''Phan, A. Q., Pacifici, M., &amp; Esko, J. D. (2017). Advances in the pathogenesis and possible treatments for multiple hereditary exostoses from the 2016 international MHE conference. Connective Tissue Research, 59(1), 85–98. &lt;nowiki&gt;https://doi.org/10.1080/03008207.2017.1394295&lt;/nowiki&gt;.'''&lt;ref&gt;{{Cite web |url=https://www.tandfonline.com/action/cookieAbsent |access-date=2026-07-16 |website=www.tandfonline.com |doi=10.1080/03008207.2017.1394295 |pmc=7604901 |pmid=29099240}}&lt;/ref&gt;''  MHE, also known as hereditary multiple exostoses (HME) or multiple osteochondromas (MO), is characterized by cartilage-capped outgrowths called osteochondromas that develop adjacent to the growth plates of skeletal elements in young patients. These benign tumors can affect growth plate function, leading to skeletal growth retardation, or deformations, and can encroach on nerves, tendons, muscles, and other surrounding tissues and cause motion impairment, chronic pain, and early onset osteoarthritis. In about 2–5% of patients, the osteochondromas can become malignant and life threatening.''

'''Stiever, JR., and J.P. Dormans (2005). Manifestations of hereditary multiple exostoses. Journal of the American Academy of Orthopaedic Surgeons, 13: 110-120'''''.'' '''&lt;nowiki&gt;https://pubmed.ncbi.nlm.nih.gov/15850368/&lt;/nowiki&gt;''' ''Hereditary multiple exostosis is an autosomal dominant disorder manifested by the presence of multiple osteochondromas. Linkage analysis has implicated mutations in the EXT gene family, resulting in an error in the regulation of normal chondrocyte proliferation and maturation that leads to abnormal bone growth. Although exostoses are benign lesions, they are often associated with characteristic progressive skeletal deformities and may cause clinical symptoms. Patients with hereditary multiple exostosis have a slight risk of sarcomatous transformation of the cartilaginous portion of the exostosis.''

=== '''Screening and treatment''' ===
'''Fei, Li,  Clara Ngoh, Daniel E. Porter, Chondrosarcoma transformation in hereditary multiple exostoses: A systematic review and clinical and cost-effectiveness of a proposed screening model, Journal of Bone Oncology, Volume 13, 2018, Pages 114-122, ISSN 2212-1374, &lt;nowiki&gt;https://doi.org/10.1016/j.jbo.2018.09.011&lt;/nowiki&gt;.'''&lt;ref&gt;{{Cite journal |last=Fei |first=Li |last2=Ngoh |first2=Clara |last3=Porter |first3=Daniel E. |date=2018-11-01 |title=Chondrosarcoma transformation in hereditary multiple exostoses: A systematic review and clinical and cost-effectiveness of a proposed screening model |url=https://www.sciencedirect.com/science/article/pii/S2212137418300903 |journal=Journal of Bone Oncology |volume=13 |pages=114–122 |doi=10.1016/j.jbo.2018.09.011 |issn=2212-1374 |pmc=6303411 |pmid=30591865}}&lt;/ref&gt;''  The most serious complication of hereditary multiple exostoses (HME) is chondrosarcoma transformation. Three HME screening strategies were then developed and compared using cost per life-year gained and incremental cost-effectiveness ratio (ICER).''

'''Hosalkar, Harish MD, MBMS (Ortho), FCPS (Ortho), DNB (Ortho)*; Greenberg, Jared MD†; Gaugler, Rebecca L. BS‡; Garg, Sumeet MD§; Dormans, John P. MD∥, 2007. Abnormal Scarring With Keloid Formation After Osteochondroma Excision in Children With Multiple Hereditary Exostoses Journal of Pediatric Orthopaedics: May 2007 - Volume 27 - Issue 3 - p 333-337 doi: 10.1097/BPO.0b013e3180326732'''&lt;ref&gt;{{Cite journal |last=Hosalkar |first=Harish |last2=Greenberg |first2=Jared |last3=Gaugler |first3=Rebecca L. |last4=Garg |first4=Sumeet |last5=Dormans |first5=John P. |date=2007-05 |title=Abnormal Scarring With Keloid Formation After Osteochondroma Excision in Children With Multiple Hereditary Exostoses |url=https://journals.lww.com/01241398-200704000-00017 |journal=Journal of Pediatric Orthopaedics |language=en |volume=27 |issue=3 |pages=333–337 |doi=10.1097/BPO.0b013e3180326732 |issn=0271-6798}}&lt;/ref&gt;  ''Although this study has limited numbers, the results demonstrate a statistically significant correlation between keloid formation and MHE. The risk for abnormal scarring and keloid formation should be discussed with all patients before surgery.''

'''Monroig-Rivera, Carlos MD1; Bockhorn, Lauren MD1,2; Thornberg, David BS1; Santillan, Brenda BS1,2; Rathjen, Karl E. MD1,2,a. Prevalence of Osteochondromas in the Spine in Patients with Multiple Hereditary Exostoses. JBJS Open Access 10(1):e24.00072, January-March 2025. | DOI: 10.2106/JBJS.OA.24.00072.''' &lt;ref&gt;{{Cite journal |last=Monroig-Rivera |first=Carlos |last2=Bockhorn |first2=Lauren |last3=Thornberg |first3=David |last4=Santillan |first4=Brenda |last5=Rathjen |first5=Karl E. |date=2025-01 |title=Prevalence of Osteochondromas in the Spine in Patients with Multiple Hereditary Exostoses |url=https://journals.lww.com/10.2106/JBJS.OA.24.00072 |journal=JBJS Open Access |language=en |volume=10 |issue=1 |doi=10.2106/JBJS.OA.24.00072 |issn=2472-7245}}&lt;/ref&gt;''Although nearly half of the patients had spinal osteochondromas, neural impingement was rare (4%). Neither age, gender, nor the presence of rib and pelvic osteochondromas were associated with spinal involvement, osteochondromas in the canal, or neural impingement. This information can be used to guide clinical decision-making regarding the use of MRI scans for patient screening'''''.'''

'''Troxel, J., Fleury, I. G., &amp; Buckwalter V, J. A. (2025). Revisiting Sex Differences in Multiple Hereditary Exostoses (MHE): A Comprehensive Retrospective Analysis of Patient Characteristics and Surgical Patterns. ''Journal of Pediatric Orthopaedics'', ''46''(3), 180–185.''' ''We examined 103 MHE-diagnosed patients treated at the University of Iowa Hospitals and Clinics from June 2008 to March 2023.'' ''Our findings deviate from the commonly accepted male predominance in MHE, revealing an even male-female distribution.''

'''Van der Woude HJ, Flipsen M, Welsink C, Van der Zwan AL, Ham SJ, 2025. Is total-body MRI useful as a screening tool to rule out malignant progression in patients with multiple osteochondromas? Results in a single-center cohort of 319 adult patients. By''''':''  '''Skeletal radiology, 1432-2161, 2024 Jan, Vol. 53, Issue 1.'''''To evaluate the results of total-body (TB) MRI used as a screening tool for assessment or exclusion of malignant transformation in patients with hereditary multiple osteochondromas (HMO). Conclusion: TB-MRI can identify malignant transformation of osteochondromas in HMO patients. All peripheral chondrosarcomas occurred in flat bones (ribs, scapula, pelvis) in our study. TB-MRI might assist in triage between higher risk patients with a high burden of OC, including the location of OC in main flat bones vs lower risk patients without OC of the flat bones.''

'''Teeth'''

'''Wiweger, Malgorzata I. Wiweger, Zhe Zhao, Richard J. P. van Merkesteyn, Henry H. Roehl, and Pancras C. W. Hogendoorn, 2012. HSPG-Deficient Zebrafish Uncovers Dental Aspect of Multiple Osteochondromas. PLOS 1. &lt;nowiki&gt;https://doi.org/10.1371/journal.pone.0029734&lt;/nowiki&gt;'''''.'' ''Here we analyse dental defects present in ext2−/− fish. Histological analysis reveals that ext2−/− fish have very severe defects associated with the formation and the morphology of teeth. Our findings from zebrafish model were validated in a dental survey that was conducted with assistance of the MHE Research Foundation. The presence of the malformed and/or displaced teeth with abnormal enamel was declared by half of the respondents indicating that MO might indeed be also associated with dental problems.''

== Genetic studies (EXT genes) ==
As HME is associated with genetic issues on the EXT genes, here is a list of genetic studies:

'''Benoist-Lasselina, Catherine Emmanuel de Margerieb, Linda Gibbsa, Sarah Cormierc, Caroline Silvec, Gisèle Nicolasd, Martine LeMerrera, Jean-Francois Mallete, Arno­­­­ld Munnicha, Jacky Bonaventurea, Louise Zylberbergb, Laurence Legeai-Malleta,  2006.  ''Defective chondrocyte proliferation and differentiation in osteochondromas of MHE patients''. Bone, Volume 39, Issue 1, July 2006, Pages 17–26'''.&lt;ref&gt;{{Cite journal |last=Benoist-Lasselin |first=Catherine |last2=de Margerie |first2=Emmanuel |last3=Gibbs |first3=Linda |last4=Cormier |first4=Sarah |last5=Silve |first5=Caroline |last6=Nicolas |first6=Gisèle |last7=LeMerrer |first7=Martine |last8=Mallet |first8=Jean-Francois |last9=Munnich |first9=Arnold |last10=Bonaventure |first10=Jacky |last11=Zylberberg |first11=Louise |last12=Legeai-Mallet |first12=Laurence |date=2006-07 |title=Defective chondrocyte proliferation and differentiation in osteochondromas of MHE patients |url=http://www.thebonejournal.com/article/S8756-3282(05)00540-5/fulltext |journal=Bone |volume=39 |issue=1 |pages=17–26 |doi=10.1016/j.bone.2005.12.003 |issn=8756-3282}}&lt;/ref&gt; . ''Multiple hereditary exostoses (MHE) is an autosomal dominant skeletal disorder caused by mutations in one of the two EXT genes and characterized by multiple osteochondromas that generally arise near the ends of growing long bones.''

'''Busse-Wicher, Marta; Wicher, Krzysztof B.; Kusche-Gullberg, Marion (2014). &quot;The extostosin family: Proteins with many functions&quot;. Matrix Biology. Elsevier BV. 35: 25–33. doi:10.1016/j.matbio.2013.10.001. hdl:1956/10590. ISSN 0945-053X.''' ''Mutations in either EXT1 or EXT2 cause hereditary multiple osteochondromas (HMO), an autosomal dominant disorder characterized by bone deformities and cartilage-capped bony outgrowths, called exostoses or osteochondromas, at the ends of the long bones (reviewed in (Jennes et al., 2009)). HMO is one of the most common inherited skeletal disorders with an estimated incidence of 1–2 per 100 000 live births.''

'''Cuellar, A., Reddi, A.H. Cell biology of osteochondromas: Bone morphogenic protein signalling and heparan sulphates. International Orthopaedics (SICOT) 37, 1591–1596 (2013). &lt;nowiki&gt;https://doi.org/10.1007/s00264-013-1906-5&lt;/nowiki&gt;.'''&lt;ref&gt;{{Cite journal |last=Cuellar |first=Araceli |last2=Reddi |first2=A. Hari |date=2013-08-01 |title=Cell biology of osteochondromas: Bone morphogenic protein signalling and heparan sulphates |url=https://doi.org/10.1007/s00264-013-1906-5 |journal=International Orthopaedics |language=en |volume=37 |issue=8 |pages=1591–1596 |doi=10.1007/s00264-013-1906-5 |issn=1432-5195 |pmc=3728397 |pmid=23771188}}&lt;/ref&gt; ''While factors for severity remain unknown, mutations in exostosin 1 and exostosin 2 genes, encoding glycosyltransferases involved in the biosynthesis of ubiquitously expressed heparan sulphate (HS) chains, are associated with MHE.''

'''Nozawa S, Inubushi T, Irie F, et al. Osteoblastic heparan sulfate regulates osteoprotegerin function and bone mass. JCI Insight. 2018;3(3):e89624. Published 2018 Feb 8. doi:10.1172/jci.insight.89624.'''&lt;ref&gt;{{Cite journal |last=Nozawa |first=Satoshi |last2=Inubushi |first2=Toshihiro |last3=Irie |first3=Fumitoshi |last4=Takigami |first4=Iori |last5=Matsumoto |first5=Kazu |last6=Shimizu |first6=Katsuji |last7=Akiyama |first7=Haruhiko |last8=Yamaguchi |first8=Yu |date=2018-02-08 |title=Osteoblastic heparan sulfate regulates osteoprotegerin function and bone mass |url=https://insight.jci.org/articles/view/89624 |journal=JCI Insight |language=en |volume=3 |issue=3 |doi=10.1172/jci.insight.89624 |issn=2379-3708 |pmc=5821205 |pmid=29415886}}&lt;/ref&gt; ''To determine the role of HS in bone homeostasis, we conditionally ablated Ext1, which encodes an essential glycosyltransferase for HS biosynthesis, in osteoblasts. Resultant conditional mutant mice developed severe osteopenia. Surprisingly, this phenotype is not due to impairment in bone formation but to enhancement of bone resorption. We also show that bone mineral density is reduced in patients with multiple hereditary exostoses, a genetic bone disorder caused by heterozygous mutations of Ext1, suggesting that the mechanism revealed in this study may be relevant to low bone mass conditions in humans.''

'''Pacifici M. The pathogenic roles of heparan sulfate deficiency in hereditary multiple exostoses. Matrix Biol. 2018 Oct;71-72:28-39. doi: 10.1016/j.matbio.2017.12.011. Epub 2017 Dec 24. PMID: 29277722; PMCID: PMC6015767'''''.''&lt;ref name=&quot;:7&quot; /&gt; ''Heparan sulfate (HS) is an essential component of cell surface and matrix proteoglycans (HS-PGs) that include syndecans and perlecan. Because of their unique structural features, the HS chains are able to specifically interact with signaling proteins–including bone morphogenetic proteins (BMPs)-via their HS-binding domain, regulating protein availability, distribution and action on target cells. Hereditary Multiple Exostoses (HME) is a rare pediatric disorder linked to germline heterozygous loss-of-function mutations in EXT1 or EXT2 that encode Golgi-resident glycosyltransferases responsible for HS synthesis, resulting in a systemic HS deficiency. HME is characterized by cartilaginous/bony tumors-called osteochondromas or exostoses- that form within perichondrium in long bones, ribs and other elements. This review examines most recent studies in HME, framing them in the context of classic studies. New findings show that the spectrum of EXT mutations is larger than previously realized and the clinical complications of HME extend beyond the skeleton.''

'''Sefcik R, Earl D. Hereditary Multiple Osteochondromas. 2000 Aug 3 [Updated 2026 Jan 29]. In: Adam MP, Bick S, Mirzaa GM, et al., editors. GeneReviews® [Internet]. Seattle (WA): University of Washington, Seattle; 1993-2026. Available from: &lt;nowiki&gt;https://www.ncbi.nlm.nih.gov/books/NBK1235&lt;/nowiki&gt;.''' ''Each child of an individual with HMO has a 50% chance of inheriting an HMO-causing pathogenic variant.''

'''Zak, B.M., B.E. Crawford, and J.D. Esko, 2002. Hereditary multiple exostoses and heparan sulfate polymerization Biochimica et Biophysica Acta (BBA) Volume 1573, Issue 3, 19 December 2002, Pages 346–355 &lt;nowiki&gt;http://www.sciencedirect.com/science/article/pii/S0304416502004026&lt;/nowiki&gt;''' ''Hereditary multiple exostoses (HME, OMIM 133700, 133701) results from mutations in EXT1 and EXT2, genes encoding the copolymerase responsible for heparan sulfate (HS) biosynthesis. Here, we provide an overview of HME, the EXT family of proteins, and possible models for the relationship of altered HS biosynthesis to the ectopic bone growth characteristic of the disease.''

== HSPG-Related studies ==
While HME is a rare disease and rarely studied, the connection between HME and HSPG is noted. Therefore, this list of research articles covers HME, HSPG, and the genetic issues associated with the EXT1, EXT2, and EXT3 genes.

'''Aldunate, Rebecca, Juan Carlos Casar, Enrique Brandan, Nibaldo C. Inestrosa, 2004. Structural and functional organization of synaptic acetylcholinesterase, Brain Research Reviews, Volume 47, Issues 1–3,''' &lt;ref&gt;{{Cite journal |last=Aldunate |first=Rebeca |last2=Casar |first2=Juan Carlos |last3=Brandan |first3=Enrique |last4=Inestrosa |first4=Nibaldo C. |date=2004-12 |title=Structural and functional organization of synaptic acetylcholinesterase |url=https://linkinghub.elsevier.com/retrieve/pii/S0165017304001092 |journal=Brain Research Reviews |language=en |volume=47 |issue=1-3 |pages=96–104 |doi=10.1016/j.brainresrev.2004.07.019}}&lt;/ref&gt; ''&quot;The presence of two heparin-binding domains in ColQ that interact with heparan sulfate proteoglycans (HSPGs) at the synaptic basal lamina; and second, a knockout mouse for perlecan, a HSPG concentrated in nerve–muscle contact, in which absence of asymmetric AChE at the NMJ is observed.&quot;''

'''Aplin, J.D., Charlton, A.K. &amp; Ayad, S.  1988. An immunohistochemical study of human endometrial extracellular matrix during the menstrual cycle and first trimester of pregnancy. Cell Tissue Res. 253: 231. &lt;nowiki&gt;https://doi.org/10.1007/BF00221758&lt;/nowiki&gt;.''' &lt;ref&gt;{{Cite journal |last=Aplin |first=J. D. |last2=Charlton |first2=A. K. |last3=Ayad |first3=S. |date=1988-07-01 |title=An immunohistochemical study of human endometrial extracellular matrix during the menstrual cycle and first trimester of pregnancy |url=https://doi.org/10.1007/BF00221758 |journal=Cell and Tissue Research |language=en |volume=253 |issue=1 |pages=231–240 |doi=10.1007/BF00221758 |issn=1432-0878}}&lt;/ref&gt; ''Changes in the organisation and composition of extracellular matrix in human endometrium during the menstrual cycle and early pregnancy have been assessed by immunofluorescence.'' 

'''Arnold, K. Y-E. Liao, and J. Liu, 2020. ''Potential Use of Anti-Inflammatory Synthetic Heparan Sulfate to Attenuate Liver Damage. Biomedicines 2020, 8(11), 503;''''' &lt;ref&gt;{{Cite journal |last=Arnold |first=Katelyn |last2=Liao |first2=Yi-En |last3=Liu |first3=Jian |date=2020-11-16 |title=Potential Use of Anti-Inflammatory Synthetic Heparan Sulfate to Attenuate Liver Damage |url=https://www.mdpi.com/2227-9059/8/11/503 |journal=Biomedicines |language=en |volume=8 |issue=11 |pages=503 |doi=10.3390/biomedicines8110503 |issn=2227-9059}}&lt;/ref&gt; ''Heparan sulfate (HS) is an essential glycan for liver function.''

'''Ascencio, F. L. Å. Fransson and T. WadstrÖum, 1993. ''Affinity of the gastric pathogen Helicobacter pylori for the N-sulphated glycosaminoglycan heparan sulphate'' J Med Microbiol April 1993 vol. 38 no. 4 240-244''' &lt;ref&gt;{{Cite web |last=F |first=Ascencio |last2=A |first2=Fransson, L. |last3=T |first3=Wadstrom |date=1993-04-01 |title=Affinity of the gastric pathogen Helicobacter pylori for the N-sulphated glycosaminogly… |url=https://www.sgmjournals.org/jmm/content/38/4/240 |access-date=2026-07-15 |website=SGM Journals |language=en}}&lt;/ref&gt;'''.''' ''Binding of 125I-heparan sulphate was a common property of Helicobacter pylori strains isolated from patients with gastroduodenal ulcer diseases.''

'''Berg et al., 1999. Chronic fatigue syndrome and/or Fibromyalgia as a variation of Antiphospholipid antibody syndrome: an explanatory model and approach to laboratory  diagnosis'''&lt;ref&gt;{{Cite journal |last=Berg |first=D. |last2=Berg |first2=L. H. |last3=Couvaras |first3=J. |last4=Harrison |first4=H. |date=1999-10 |title=Chronic fatigue syndrome and/or fibromyalgia as a variation of antiphospholipid antibody syndrome: an explanatory model and approach to laboratory diagnosis |url=https://pubmed.ncbi.nlm.nih.gov/10695770 |journal=Blood Coagulation &amp; Fibrinolysis: An International Journal in Haemostasis and Thrombosis |volume=10 |issue=7 |pages=435–438 |doi=10.1097/00001721-199910000-00006 |issn=0957-5235 |pmid=10695770}}&lt;/ref&gt; Not in this paper, but the logic is that low levels of HSPG are found in patients with chronic fatigue, and there is probably a correlation with MHE fatigue and low levels of HSPG.

'''Bishop, J., Schuksz, M. &amp; Esko, J. Heparan sulphate proteoglycans fine-tune mammalian physiology. Nature 446, 1030–1037 (2007). &lt;nowiki&gt;https://doi.org/10.1038/nature05817&lt;/nowiki&gt;'''&lt;ref&gt;{{Cite journal |last=Bishop |first=Joseph R. |last2=Schuksz |first2=Manuela |last3=Esko |first3=Jeffrey D. |date=2007-04 |title=Heparan sulphate proteoglycans fine-tune mammalian physiology |url=https://www.nature.com/articles/nature05817 |journal=Nature |language=en |volume=446 |issue=7139 |pages=1030–1037 |doi=10.1038/nature05817 |issn=1476-4687}}&lt;/ref&gt; ''Heparan sulphate proteoglycans reside on the plasma membrane of all animal cells studied so far and are a major component of extracellular matrices. . A recurrent theme is the electrostatic interaction of the heparan sulphate chains with protein ligands, which affects metabolism, transport, information transfer, support and regulation in all organ systems.'' 

'''Boer and Gaillard, 2007. Drug Targeting to the Brain. Annual Review of Pharmacology and Toxicology. Volume 47, 2007. Pp 323-355'''&lt;ref name=&quot;:3&quot; /&gt;'''.'''''… For many diseases of the brain, such as Alzheimer's disease, Parkinson's disease, stroke, depression, schizophrenia, epilepsia and migraine headache, the drugs on the market … enter the cell following binding to heparan sulfate proteoglycan (HSPG) receptors …''

'''Brown, Anissa Joy. Function of heparan sulfate proteoglycans (HSPGs) and heparanase (HPSE) in endochondral bone formation University of Delaware, ProQuest Dissertations Publishing, 2008. 3324491.'''&lt;ref&gt;{{Cite web |title=Function of heparan sulfate proteoglycans (HSPGs) and heparanase (HPSE) in endochondral bone formation. by Brown, Anissa Joy (9781243986054) {{!}} Browns Books |url=https://www.brownsbfs.co.uk/Product/Brown-Anissa-Joy/Function-of-heparan-sulfate-proteoglycans-HSPGs-and-hepar/9781243986054 |access-date=2026-07-15 |website=www.brownsbfs.co.uk}}&lt;/ref&gt; ''Endochondral bone formation is a tightly regulated process involving coordination among cell-cell, cell-matrix and growth factor signaling that eventually results in the production of mineralized bone from a cartilage template. Chondrogenic and osteogenic differentiation occur in sequence during this process, and the temporospatial patterning clearly requires the activities of heparan sulfate proteoglycans (HSPGs), heparin binding growth factors (HBGFs) and their receptors.''

'''O'Callaghan P, Zhang X, Li JP. 2018. Heparan Sulfate Proteoglycans as Relays of Neuroinflammation. J Histochem Cytochem. 2018 Apr;66(4):305-319. doi: 10.1369/0022155417742147. Epub 2018 Jan 1. PMID: 29290138; PMCID: PMC5958378'''&lt;ref&gt;{{Cite journal |last=O'Callaghan |first=Paul |last2=Zhang |first2=Xiao |last3=Li |first3=Jin-Ping |date=2018-04 |title=Heparan Sulfate Proteoglycans as Relays of Neuroinflammation |url=https://pmc.ncbi.nlm.nih.gov/articles/PMC5958378/ |journal=The Journal of Histochemistry and Cytochemistry: Official Journal of the Histochemistry Society |volume=66 |issue=4 |pages=305–319 |doi=10.1369/0022155417742147 |issn=1551-5044 |pmc=5958378 |pmid=29290138}}&lt;/ref&gt;'''.''' ''.'' ''We summarize some of the contrasting roles that HS and heparanase have been assigned in diseases associated with chronic inflammatory states, including Alzheimer's disease (AD).''

'''Chen, Ming and Xiao, Xiao and Rui, Yimin and Jin, Yu,''' '''2023. Relationship of Sleep Disorder with Neurodegenerative and Psychiatric Diseases: An Updated Review. Available at SSRN:''' &lt;nowiki&gt;https://ssrn.com/abstract=4484640&lt;/nowiki&gt; or http://dx.doi.org/10.2139/ssrn.4484640. &quot;''Another key factor in the circadian timing of Aβ42 phagocytosis is the presence of cell-surface heparan sulfate proteoglycans (HSPGs), which highlights a potential causative factor for increased Aβ42 accumulation in patients with clock/sleep disorders due to the apparent circadian rhythmicity of HSPGs levels and the inhibitory role of HSPGs in the phagocytosis of Aβ42(Clark et al., 2022).&quot;''

'''Chmiela, M. et al. 1995. The role of heparan sulphate-binding activity of Helicobacter pylori bacteria in their adhesion to murine macrophages. &lt;nowiki&gt;http://onlinelibrary.wiley.com/doi/10.1111/j.1699-0463.1995.tb01133.x/full&lt;/nowiki&gt;'''&lt;ref&gt;{{Cite journal |last=Chmiela |first=M. |last2=Paziak-Domanska |first2=B. |last3=Rudnicka |first3=W. |last4=WadstrÖM |first4=T. |date=1995 |title=The role of heparan sulphate-binding activity of Helicobacter pylori bacteria in their adhesion to murine macrophages |url=https://onlinelibrary.wiley.com/doi/abs/10.1111/j.1699-0463.1995.tb01133.x |journal=APMIS |language=en |volume=103 |issue=1-6 |pages=469–474 |doi=10.1111/j.1699-0463.1995.tb01133.x |issn=1600-0463}}&lt;/ref&gt; ''The role of heparan sulphate (HS)-binding activity of Helicobacter pylori microbes in their adhesion to and ingestion by inflammatory peritoneal macrophages.''

'''Clark, GT, Yu Y, Urban C et al. 2023. Circadian control of heparan sulfate levels times phagocytosis of amyloid beta aggregates. February 10, 202. PLOS Genetics. https://doi.org/10.1371/journal.pgen.1009994&lt;nowiki/&gt;.'''  ''PGs like heparan sulfate proteoglycans (HSPGs) and chondroitin sulfate proteoglycans (CSPGs) are involved in the clearance of Aβ42, associate with Aβ42 to foster the formation of plaques, and reduce Aβ plaque load upon the knockout of a key enzyme in the HSPG biosynthesis pathway... our findings suggest the disruption of the circadian timing of macrophage/microglia phagocytosis may be a vital component in Aβ42 metabolism, highlighting a potential causative factor in the increase in accumulation of Aβ42 in patients with clock/sleep disturbances [8,13,20,22,25,94,97].'' 

'''Collins LE, Troeberg L. 2019. Heparan sulfate as a regulator of inflammation and immunity. J Leukoc Biol. 2019 Jan;105(1):81-92. doi: 10.1002/JLB.3RU0618-246R. Epub 2018 Oct 30. PMID: 30376187.'''&lt;ref&gt;{{Cite journal |last=Collins |first=Laura E |last2=Troeberg |first2=Linda |date=2018-12-27 |title=Heparan sulfate as a regulator of inflammation and immunity |url=https://academic.oup.com/jleukbio/article/105/1/81/6935486 |journal=Journal of Leukocyte Biology |language=en |volume=105 |issue=1 |pages=81–92 |doi=10.1002/JLB.3RU0618-246R |issn=1938-3673}}&lt;/ref&gt; ''In this review, we discuss the multiple roles for HS in regulating immune responses, and the evidence for inflammation-associated changes to HS structure.Keywords: chemokines; cytokines; heparan sulfate; inflammation; leukocyte.''

'''Condomitti, G., &amp; de Wit, J. (2018). Heparan Sulfate Proteoglycans as Emerging Players in Synaptic Specificity. Frontiers in molecular neuroscience, 11, 14. &lt;nowiki&gt;https://doi.org/10.3389/fnmol.2018.00014&lt;/nowiki&gt;'''&lt;ref&gt;{{Cite journal |last=Condomitti |first=Giuseppe |last2=de Wit |first2=Joris |date=2018-01-26 |title=Heparan Sulfate Proteoglycans as Emerging Players in Synaptic Specificity |url=https://www.frontiersin.org/journals/molecular-neuroscience/articles/10.3389/fnmol.2018.00014/full |journal=Frontiers in Molecular Neuroscience |language=English |volume=11 |doi=10.3389/fnmol.2018.00014 |issn=1662-5099 |pmc=5790772 |pmid=29434536}}&lt;/ref&gt; ''The heparan sulfate proteoglycan (HSPG) family of cell-surface proteins is emerging as a key regulator of connectivity. HSPGs are expressed throughout brain development and play important roles in axon guidance, synapse development and synapse function.''

'''Cooper, Isabella D.; Brookler, Kenneth H.; Crofts, Catherine A. P. (2021-09-06). &quot;Rethinking  Fragility Fractures in Type 2 Diabetes: The Link between Hyperinsulinaemia and Osteofragilitas&quot; Biomedicines 9, no. 9: 1165.'''&lt;ref&gt;{{Cite journal |last=Cooper |first=Isabella D. |last2=Brookler |first2=Kenneth H. |last3=Crofts |first3=Catherine A. P. |date=2021-09-06 |title=Rethinking Fragility Fractures in Type 2 Diabetes: The Link between Hyperinsulinaemia and Osteofragilitas |url=https://www.mdpi.com/2227-9059/9/9/1165 |journal=Biomedicines |language=en |volume=9 |issue=9 |pages=1165 |doi=10.3390/biomedicines9091165 |issn=2227-9059}}&lt;/ref&gt; ''&lt;nowiki&gt;https://doi.org/10.3390/biomedicines9091165&lt;/nowiki&gt;  Hyperinsulinaemia negatively impacts HSPG function and availability, via impairment of vitamin D regulation. Vitamin D regulates sulfate synthesis, required for heparan sulphate ['''145'''].''

'''Dituri F, Gigante G, Scialpi R, Mancarella S, Fabregat I, Giannelli G. Proteoglycans in Cancer: Friends or Enemies? A Special Focus on Hepatocellular Carcinoma. Cancers. 2022; 14(8):1902. &lt;nowiki&gt;https://doi.org/10.3390/cancers14081902&lt;/nowiki&gt;'''&lt;ref&gt;{{Cite journal |last=Dituri |first=Francesco |last2=Gigante |first2=Gianluigi |last3=Scialpi |first3=Rosanna |last4=Mancarella |first4=Serena |last5=Fabregat |first5=Isabel |last6=Giannelli |first6=Gianluigi |date=2022-04-09 |title=Proteoglycans in Cancer: Friends or Enemies? A Special Focus on Hepatocellular Carcinoma |url=https://www.mdpi.com/2072-6694/14/8/1902 |journal=Cancers |language=en |volume=14 |issue=8 |pages=1902 |doi=10.3390/cancers14081902 |issn=2072-6694 |pmc=9024587 |pmid=35454809}}&lt;/ref&gt; ''Proteoglycans are a class of highly glycosylated proteins expressed in virtually all tissues, which are localized within membranes, but more often in the pericellular space and extracellular matrix (ECM), and are involved in tissue homeostasis and remodeling of the stromal microenvironment during physiological and pathological processes, such as tissue regeneration, angiogenesis, and cancer.''

'''Farhan, S.M.K. , Wang J, Robinson JF, et al., 2015. Old gene, new phenotype: mutations in heparan sulfate synthesis enzyme, EXT2 leads to seizure and developmental disorder, no exostoses. Journal of Medical Genetics 2015;52:666-675. ''' ''Many genes are involved in modulating heparan sulfate synthesis, and when these genes are mutated, they can give rise to early-onset developmental disorders affecting multiple body systems.'' 

'''Forsberg E. and L. Kjellen, 2001. Heparan sulfate: lessons from knockout mice. Journal of Clinical Investigation. &lt;nowiki&gt;https://www.jci.org/articles/view/13561&lt;/nowiki&gt;.''' &lt;ref&gt;{{Cite journal |last=Forsberg |first=Erik |last2=Kjellén |first2=Lena |date=2001-07-15 |title=Heparan sulfate: lessons from knockout mice |url=https://www.jci.org/articles/view/13561 |journal=The Journal of Clinical Investigation |language=en |volume=108 |issue=2 |pages=175–180 |doi=10.1172/JCI13561 |issn=0021-9738 |pmid=11457868}}&lt;/ref&gt; ''Kidney'' ''agenesis, “broken heart,” abnormal mast cells, somatic overgrowth, lung dysfunction, and chondrodysplasia are some phenotypes of mice where different genes important for heparan sulfate (HS) expression have been knocked out.The authors speculate that, during inflammation or wounding when fibronectin is degraded, syndecan-4 may be important for focal adhesion formation and actin fiber organization, which in turn contribute to cell migration.'' 

'''Fumitoshi Irie, Hedieh Badie-Mahdavi, and Yu Yamaguchi, 2012. ''Autism-like socio-communicative deficits and stereotypies in mice lacking heparan sulfate''. PNAS 2012 109 (13) 5052-5056;  March 27, 2012 vol. 109 no. 13'''&lt;ref name=&quot;:4&quot; /&gt; '''&lt;nowiki&gt;http://www.pnas.org/content/109/13/5052.short&lt;/nowiki&gt;''' ''Heparan sulfate regulates diverse cell-surface signaling events, and its roles in the development of the nervous system recently have been increasingly uncovered by studies using genetic models carrying mutations of genes encoding enzymes for its synthesis. Our results demonstrate that heparan sulfate is critical for normal functioning of glutamatergic synapses and that its deficiency mediates socio-communicative deficits and stereotypes characteristic for autism.''

'''Ge, Xiao Na, Bastan, Idil, Ha, Sung Gil, Greenberg, Yana G., Esko, Jeffrey D., Rao, Savita P., Sriramarao, P., 2018. Regulation of eosinophil recruitment and allergic airway inflammation by heparan sulfate proteoglycan (HSPG) modifying enzymes. Experimental Lung Research, 01902148, Mar2018, Vol. 44, Issue''' ''Our study demonstrates that allergen exposure reduces expression of Hs2st; loss of uronyl 2-O-sulfation in endothelial and leukocyte HSPG amplifies recruitment of eosinophils likely due to a compromised vascular endothelium resulting in persistent inflammation whereas loss of N-sulfation limits eosinophilia and attenuates inflammation underscoring the importance of site-specific sulfation in HSPG to their role in AAI.''

'''Haeger SM, Yang Y, Schmidt EP. Heparan Sulfate in the Developing, Healthy, and Injured Lung. Am J Respir Cell Mol Biol. 2016;55(1):5-11. doi:10.1165/rcmb.2016-0043TR''' '''''&lt;nowiki&gt;https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4942210/&lt;/nowiki&gt;'''''&lt;ref&gt;{{Cite journal |last=Haeger |first=Sarah M. |last2=Yang |first2=Yimu |last3=Schmidt |first3=Eric P. |date=2016-07 |title=Heparan Sulfate in the Developing, Healthy, and Injured Lung |url=https://pmc.ncbi.nlm.nih.gov/articles/PMC4942210/ |journal=American Journal of Respiratory Cell and Molecular Biology |volume=55 |issue=1 |pages=5–11 |doi=10.1165/rcmb.2016-0043TR |issn=1535-4989 |pmc=4942210 |pmid=26982577}}&lt;/ref&gt; ''This Translational Review highlightsthe importance of athe glycosaminoglycan heparan sulfate (HS) on lung health and disease.''

'''Hiebert, Linda M. 2021. Heparan Sulfate Proteoglycans in Diabetes. DOI: 10.1055/s-0041-1724118. Thieme E-''' '''Journals - Seminars in Thrombosis and Hemostasis / Abstract (thieme-connect.com).''' &lt;ref&gt;{{Cite journal |last=Hiebert |first=Linda M. |date=2021-04 |title=Heparan Sulfate Proteoglycans in Diabetes |url=http://www.thieme-connect.de/DOI/DOI?10.1055/s-0041-1724118 |journal=Seminars in Thrombosis and Hemostasis |language=en |volume=47 |issue=03 |pages=261–273 |doi=10.1055/s-0041-1724118 |issn=0094-6176}}&lt;/ref&gt; ''Understanding the role of HSPGs and how they are modified by diabetes may lead to new treatments as well as preventative measures to reduce the morbidity and mortality associated with this complex condition.''

'''Ho, G., G Broze, A. Schwartz, 1997. Role of Heparan Sulfate Proteoglycans in the Uptake and Degradation of Tissue Factor Pathway Inhibitor-Coagulation Factor Xa Complexes. CELL BIOLOGY AND METABOLISM| VOLUME 272, ISSUE 27, P16838-16844, JULY 1997.&lt;nowiki&gt;https://www.jbc.org/article/S0021-9258(18)39299-8/fulltext&lt;/nowiki&gt;''' &lt;ref&gt;{{Cite journal |last=Ho |first=Guyu |last2=Broze |first2=George J. |last3=Schwartz |first3=Alan L. |date=1997-07-04 |title=Role of Heparan Sulfate Proteoglycans in the Uptake and Degradation of Tissue Factor Pathway Inhibitor-Coagulation Factor Xa Complexes * |url=https://www.jbc.org/article/S0021-9258(18)39299-8/abstract |journal=Journal of Biological Chemistry |language=English |volume=272 |issue=27 |pages=16838–16844 |doi=10.1074/jbc.272.27.16838 |issn=0021-9258}}&lt;/ref&gt;''These results suggest that heparan sulfate proteoglycans (HSPGs) are required for the uptake and degradation of 125I-TFPI·fXa complexes.'' 

'''Huang M, He H, Belenkaya T, Lin X. Multiple roles of epithelial heparan sulfate in stomach morphogenesis. J Cell Sci. 2018 May 29;131(10):jcs210781. doi: 10.1242/jcs.210781. PMID: 29700203; PMCID: PMC6031332.''' &lt;ref&gt;{{Cite journal |last=Huang |first=Meina |last2=He |first2=Hua |last3=Belenkaya |first3=Tatyana |last4=Lin |first4=Xinhua |date=2018-05-15 |title=Multiple roles of epithelial heparan sulfate in stomach morphogenesis |url=https://journals.biologists.com/jcs/article/131/10/jcs210781/56866/Multiple-roles-of-epithelial-heparan-sulfate-in |journal=Journal of Cell Science |language=en |volume=131 |issue=10 |doi=10.1242/jcs.210781 |issn=1477-9137 |pmc=6031332 |pmid=29700203}}&lt;/ref&gt; ''In the posterior stomach, HS depletion disrupts glandular stomach patterning and cytodifferentiation via attenuation of Fgf signaling activity.'' 

'''Irie, F.,  H. Badie-Mahdavi, Y. Yamaguchi, 2012. Autism-like socio-communicative deficits and stereotypies in mice lacking heparan sulfate Proc. Natl. Acad. Sci. U. S. A., 109 (2012), pp. 5052-5056. &lt;nowiki&gt;https://www.pnas.org/doi/pdf/10.1073/pnas.1117881109&lt;/nowiki&gt;.''' &lt;ref name=&quot;:5&quot; /&gt;''Our results demonstrate that heparan sulfate is critical for normal functioning of glutamatergic synapses and that its deficiency mediates socio-communicative deficits and stereotypies characteristic for autism.''

'''Jennes I, Pedrini E, Zuntini M, Mordenti M, Balkassmi S, Asteggiano CG, Casey B, Bakker B, Sangiorgi L, Wuyts W. Multiple osteochondromas: mutation update and description of the multiple osteochondromas mutation database (MOdb). Hum Mutat. 2009 Dec;30 (12):1620-7. doi: 10.1002/humu.21123. PMID: 19810120.''' &lt;ref&gt;{{Cite journal |last=Jennes |first=Ivy |last2=Pedrini |first2=Elena |last3=Zuntini |first3=Monia |last4=Mordenti |first4=Marina |last5=Balkassmi |first5=Sahila |last6=Asteggiano |first6=Carla G. |last7=Casey |first7=Brett |last8=Bakker |first8=Bert |last9=Sangiorgi |first9=Luca |last10=Wuyts |first10=Wim |date=2009-12 |title=Multiple osteochondromas: mutation update and description of the multiple osteochondromas mutation database (MOdb) |url=https://onlinelibrary.wiley.com/doi/10.1002/humu.21123 |journal=Human Mutation |language=en |volume=30 |issue=12 |pages=1620–1627 |doi=10.1002/humu.21123}}&lt;/ref&gt;''MO is genetically heterogeneous, and is associated with mutations in Exostosin-1 (EXT1) or Exostosin-2 (EXT2), both tumor-suppressor genes of the EXT gene family. All members of this multigene family encode glycosyltransferases involved in the adhesion and/or polymerization of heparin sulfate (HS) chains at HS proteoglycans (HSPGs).'' 

'''Jones, K. B., Pacifici, M., &amp; Hilton, M. J. (2014). Multiple hereditary exostoses (MHE): elucidating the pathogenesis of a rare skeletal disorder through interdisciplinary research. Connective Tissue Research, 55(2), 80–88. &lt;nowiki&gt;https://doi.org/10.3109/03008207.2013.867957&lt;/nowiki&gt;.''' ''MHE is largely caused by autosomal dominant mutations in EXT1 or EXT2, genes encoding Golgi-associated glycosyltransferases responsible for heparan sulfate (HS) synthesis. HS chains are key constituents of cell surface- and extracellular matrix-associated proteoglycans, which are known regulators of skeletal development. MHE affected individuals are HS-deficient, can display skeletal growth retardation and deformities, and consistently develop benign, cartilage-capped bony outgrowths (termed exostoses or osteochondromas) near the growth plates of many skeletal elements. Heparan sulfate proteoglycans (HSPGs) critically modulate adhesion-, growth-, and migration-related processes.''

'''Kemp, Annissa et al. 2017. Control of Cell Shape, Neurite Outgrowth, and Migration by a Nogo-A/HSPG Interaction, Developmental Cell, Volume 43, Issue 1, 24 - 34.e5 &lt;nowiki&gt;https://www.cell.com/developmental-cell/fulltext/S1534-5807(17)30674-3&lt;/nowiki&gt;'''&lt;ref&gt;{{Cite journal |last=Kempf |first=Anissa |last2=Boda |first2=Enrica |last3=Kwok |first3=Jessica C. F. |last4=Fritz |first4=Rafael |last5=Grande |first5=Valentina |last6=Kaelin |first6=Andrea M. |last7=Ristic |first7=Zorica |last8=Schmandke |first8=Andre |last9=Schmandke |first9=Antonio |last10=Tews |first10=Bjoern |last11=Fawcett |first11=James W. |last12=Pertz |first12=Olivier |last13=Buffo |first13=Annalisa |last14=Schwab |first14=Martin E. |date=2017-10-09 |title=Control of Cell Shape, Neurite Outgrowth, and Migration by a Nogo-A/HSPG Interaction |url=https://www.cell.com/developmental-cell/abstract/S1534-5807(17)30674-3 |journal=Developmental Cell |language=English |volume=43 |issue=1 |pages=24–34.e5 |doi=10.1016/j.devcel.2017.08.014 |issn=1534-5807 |pmid=28943240}}&lt;/ref&gt; ''Heparan sulfate proteoglycans (HSPGs) critically modulate adhesion-, growth-, and migration-related processes. Here, we show that the transmembrane protein, Nogo-A, inhibits neurite outgrowth and cell spreading in neurons and Nogo-A-responsive cell lines via HSPGs. Finally, we show in explant cultures ex vivo that Nogo-A-?20 promotes the migration of neuroblasts via HSPGs but not S1PR2.''

'''Kolset, S., Salmivirta, M. Cell surface heparan sulfate proteoglycans and lipoprotein metabolism. CMLS, Cell. Mol. Life Sci. 56, 857–870 (1999). &lt;nowiki&gt;https://doi.org/10.1007/s000180050031&lt;/nowiki&gt;''' [https://link.springer.com/article/10.1007/s000180050031. https://link.springer.com/article/10.1007/s000180050031.]  ''Heparan sulfate has been further implicated in presentation and stabilization of lipoprotein lipase and hepatic lipase on cell surfaces and in the transport of lipoprotein lipase from extravascular cells to the luminal surface of the endothelia. In atherosclerosis, heparan sulfate is intimately involved in several events important to the pathophysiology of the disease.''

'''Laabs, T.; Carulli, D.; Geller, H.M.; Fawcett, J.W. Chondroitin sulfate proteoglycans in neural development and regeneration. Curr. Opin. Neurobiol. 2005, 15, 116–120. [Google Scholar] [CrossRef] [PubMed]'''&lt;ref&gt;{{Cite journal |last=Carulli |first=Daniela |last2=Laabs |first2=Tracy |last3=Geller |first3=Herbert M. |last4=Fawcett |first4=James W. |date=2005-02 |title=Chondroitin sulfate proteoglycans in neural development and regeneration |url=https://pubmed.ncbi.nlm.nih.gov/15721753 |journal=Current Opinion in Neurobiology |volume=15 |issue=1 |pages=116–120 |doi=10.1016/j.conb.2005.01.014 |issn=0959-4388 |pmid=15721753}}&lt;/ref&gt; ''Proteoglycans are of two main types, chondroitin sulfate (CSPGs) and heparin sulfate (HSPGs). The CSPGs act mainly as barrier-forming molecules, whereas the HSPGs stabilise the interactions of receptors and ligands.'' 

'''Lundberg, Y.W., Y. Xu, K.D. Theissen, and K.L. Framer, 2014. Mechanisms of otoconia and otolith development. Developmental Dynamics, 9/24/2014.''' &lt;ref&gt;{{Cite journal |last=Lundberg |first=Yunxia Wang |last2=Xu |first2=Yinfang |last3=Thiessen |first3=Kevin D. |last4=Kramer |first4=Kenneth L. |date=2015 |title=Mechanisms of otoconia and otolith development |url=https://onlinelibrary.wiley.com/doi/abs/10.1002/dvdy.24195 |journal=Developmental Dynamics |language=en |volume=244 |issue=3 |pages=239–253 |doi=10.1002/dvdy.24195 |issn=1097-0177 |pmc=4482761 |pmid=25255879}}&lt;/ref&gt;  ''Deletion of different HSPGs and CSPGs causes calcification deficiencies  which exemplifies their critical role in bone and teeth formation.''

'''Mansouri, R., Jouan, Y., Hay, E. et al. Osteoblastic heparan sulfate glycosaminoglycans control bone remodeling by regulating Wnt signaling and the crosstalk between bone surface and marrow cells. Cell Death Dis 8, e2902 (2017). &lt;nowiki&gt;https://doi.org/10.1038/cddis.2017.287&lt;/nowiki&gt;'''&lt;ref&gt;{{Cite journal |last=Mansouri |first=Rafik |last2=Jouan |first2=Yohann |last3=Hay |first3=Eric |last4=Blin-Wakkach |first4=Claudine |last5=Frain |first5=Monique |last6=Ostertag |first6=Agnès |last7=Le Henaff |first7=Carole |last8=Marty |first8=Caroline |last9=Geoffroy |first9=Valérie |last10=Marie |first10=Pierre J. |last11=Cohen-Solal |first11=Martine |last12=Modrowski |first12=Dominique |date=2017-06 |title=Osteoblastic heparan sulfate glycosaminoglycans control bone remodeling by regulating Wnt signaling and the crosstalk between bone surface and marrow cells |url=https://www.nature.com/articles/cddis2017287 |journal=Cell Death &amp; Disease |language=en |volume=8 |issue=6 |pages=e2902–e2902 |doi=10.1038/cddis.2017.287 |issn=2041-4889 |pmc=5520938 |pmid=28661485}}&lt;/ref&gt;  ''Syndecan-2 is a membrane heparan sulfate proteoglycan that is associated with osteoblastic differentiation. The osteogenic properties of matrix glycosaminoglycans (GAGs) have been explored; however, the functions of GAGs at the surface of bone-forming cells are less documented.'' 

'''Matsuzawa, T. et al., 2021. Heparan sulfate promotes differentiation of white adipocytes to maintain insulin sensitivity and glucose homeostasis. Journal of Biological Chemistry.'''&lt;ref&gt;{{Cite journal |last=Matsuzawa |first=Takuro |last2=Morita |first2=Masanobu |last3=Shimane |first3=Ai |last4=Otsuka |first4=Rina |last5=Mei |first5=Yu |last6=Irie |first6=Fumitoshi |last7=Yamaguchi |first7=Yu |last8=Yanai |first8=Kazuhiko |last9=Yoshikawa |first9=Takeo |date=2021-09 |title=Heparan sulfate promotes differentiation of white adipocytes to maintain insulin sensitivity and glucose homeostasis |url=https://pubmed.ncbi.nlm.nih.gov/34310946 |journal=The Journal of Biological Chemistry |volume=297 |issue=3 |pages=101006 |doi=10.1016/j.jbc.2021.101006 |issn=1083-351X |pmc=8379462 |pmid=34310946}}&lt;/ref&gt; ''We observed that Ext1Δ/WT mice showed glucose intolerance because of insulin resistance. Our results demonstrate that HS plays a crucial role in the differentiation of white adipocytes through BMP4–FGF1 signaling pathways, thereby contributing to insulin sensitivity and glucose homeostasis.''

'''Meneghetti, Maria C. Z.; Hughes, Ashley J.; Rudd, Timothy R.; Nader, Helena B.; Powell, Andrew K.; Yates, Edwin A.; Lima, Marcelo A. (2015-09-06). &quot;Heparan sulfate and heparin interactions with proteins&quot;. Journal of the Royal Society, Interface. 12 (110): 0589. doi:10.1098/rsif.2015.0589. ISSN 1742-5662. PMC 4614469. &lt;nowiki&gt;PMID 26289657&lt;/nowiki&gt;'''&lt;ref&gt;{{Cite journal |last=Echits |first=S. V. |last2=Pichko |first2=V. B. |last3=Tikhomirova |first3=A. S. |last4=Letunova |first4=E. V. |date=1975 |title=[Preparation and properties of beta-galactosidase linked covalently with KM-cellulose] |url=https://pubmed.ncbi.nlm.nih.gov/1742 |journal=Prikladnaia Biokhimiia I Mikrobiologiia |volume=11 |issue=6 |pages=848–851 |issn=0555-1099 |pmid=1742}}&lt;/ref&gt;''. Heparan sulfate (HS) polysaccharides are ubiquitous components of the cell surface and extracellular matrix of all multicellular animals, whereas heparin is present within mast cells and can be viewed as a more sulfated, tissue-specific, HS variant. HS and heparin regulate biological processes through interactions with a large repertoire of proteins. Owing to these interactions and diverse effects observed during in vitro, ex vivo and in vivo experiments, manifold biological/pharmacological activities have been attributed to them'''''.'''

'''Mooney et al. 2016.Pathway analysis in attention deficit hyperactivity disorder: An ensemble approach. American Journal of Medical Genetics. Volume 171, Sept 2016. &lt;nowiki&gt;https://onlinelibrary.wiley.com/doi/abs/10.1002/ajmg.b.32446&lt;/nowiki&gt;''' &lt;ref&gt;{{Cite journal |last=Mooney |first=Michael A. |last2=McWeeney |first2=Shannon K. |last3=Faraone |first3=Stephen V. |last4=Hinney |first4=Anke |last5=Hebebrand |first5=Johannes |last6=Consortium |first6=Image2 |last7=Group |first7=German ADHD GWAS |last8=Nigg |first8=Joel T. |last9=Wilmot |first9=Beth |date=2016 |title=Pathway analysis in attention deficit hyperactivity disorder: An ensemble approach |url=https://onlinelibrary.wiley.com/doi/abs/10.1002/ajmg.b.32446 |journal=American Journal of Medical Genetics Part B: Neuropsychiatric Genetics |language=en |volume=171 |issue=6 |pages=815–826 |doi=10.1002/ajmg.b.32446 |issn=1552-485X |pmc=4983253 |pmid=27004716}}&lt;/ref&gt; ''These results support previous hypotheses about the role of regulation of neurotransmitter release, neurite outgrowth and axon guidance in contributing to the ADHD phenotype and suggest the value of cross-method convergence in evaluating pathway analysis results.''

'''Nackaerts, K. et al. 1997. Heparan Sulfate Proteoglycan Expression In Human Lung-Cancer Cells. Int. J. Cancer (Pred. Oncol.): 74, 335–345 (1997) r 1997 Wiley-Liss, Inc. &lt;nowiki&gt;https://www.researchgate.net/profile/Maurits_Demedts/publication/13997415_Heparan_sulfate_proteoglycan_expression_in_human_lung-cancer_cells/links/5600565108aeafc8ac8c7374.pdf&lt;/nowiki&gt;'''&lt;ref&gt;{{Cite journal |last=Nackaerts |first=Kris |last2=Verbeken |first2=Erik |last3=Deneffe |first3=Georges |last4=Vanderschueren |first4=Bernadette |last5=Demedts |first5=Maurits |last6=David |first6=Guido |date=1997-07-01 |title=Heparan sulfate proteoglycan expression in human lung-cancer cells |url=https://www.researchgate.net/publication/13997415_Heparan_sulfate_proteoglycan_expression_in_human_lung-cancer_cells |journal=International journal of cancer. Journal international du cancer |volume=74 |pages=335–45 |doi=10.1002/(SICI)1097-0215(19970620)74:33.3.CO;2-4}}&lt;/ref&gt; ''Heparan sulfate (HS) functions as a co-factor in several signal-transduction systems that affect cellular growth, differentiation, adhesion and motility. HS, therefore, may also play a role in the malignant transformation of cells, tumor growth, cell invasiveness and the formation of tumor metastases. Our results suggest that poorly differentiated lung tumors have markedly altered patterns of HSPG expression, which may contribute to their invasive phenotype. Int. J. Cancer 74:335– 345, 1997.''

'''Nencini Sara , Ivanusic Jason J. The Physiology of Bone Pain. How Much Do We Really Know? Frontiers in Physiology. Volume 7 - 2016.''' '''&lt;nowiki&gt;https://www.frontiersin.org/journals/physiology/articles/10.3389/fphys.2016.00157&lt;/nowiki&gt;. DOI=10.3389/fphys.2016.00157. ISSN=1664-042X'''&lt;ref name=&quot;:6&quot; /&gt; ''Pain is associated with most bony pathologies. Clinical and experimental observations suggest that bone pain can be derived from noxious stimulation of the periosteum or bone marrow Whilst these provide some clues as to the way information about bone pain is centrally coded, they need to be expanded to further our understanding of other central territories involved.''

'''Otsu, K.; Kato, S.; Ohtake, K.; Akamatsu, N. Alteration of rat liver proteoglycans during regeneration. Arch. Biochem. Biophys. 1992, 294, 544–549. Alteration of rat liver proteoglycans during regeneration - PubMed (nih.gov)'''''. Heparan sulfates (HS) are probably the major GAGs present on the surface of hepatocytes under normal conditions. Nevertheless, HSPGs expression increases during liver regeneration. Using [35S] sulfuric acid incorporation, Otsu et al. showed that, in the hepatic regeneration phase after hepatectomy, the synthesis of heparin sulfate proteoglycans, and to a lesser extent, of chondroitin/dermatan sulfate proteoglycans, increases up to 3–5 days and is temporally shifted compared to the stage of maximum mitosis that occurs 1–2 days following the surgical procedure [94].'' 

'''Otsuka, T., Phan, A.Q., Laurencin, C.T. et al. Identification of Heparan-Sulfate Rich Cells in the Loose Connective Tissues of the Axolotl (Ambystoma mexicanum) with the Potential to Mediate Growth Factor Signaling during Regeneration. Regen. Eng. Transl. Med. 6, 7–17 (2020). &lt;nowiki&gt;https://doi.org/10.1007/s40883-019-00140-3&lt;/nowiki&gt; &lt;nowiki&gt;https://link.springer.com/article/10.1007/s40883-019-00140-3&lt;/nowiki&gt;'''&lt;ref&gt;{{Cite journal |last=Otsuka |first=T. |last2=Phan |first2=A. Q. |last3=Laurencin |first3=C. T. |last4=Esko |first4=J. D. |last5=Bryant |first5=S. V. |last6=Gardiner |first6=D. M. |date=2020-03 |title=Identification of Heparan-Sulfate Rich Cells in the Loose Connective Tissues of the Axolotl (Ambystoma mexicanum) with the Potential to Mediate Growth Factor Signaling during Regeneration |url=http://link.springer.com/10.1007/s40883-019-00140-3 |journal=Regenerative Engineering and Translational Medicine |language=en |volume=6 |issue=1 |pages=7–17 |doi=10.1007/s40883-019-00140-3 |issn=2364-4133 |pmc=7971174 |pmid=33748405}}&lt;/ref&gt; ''. We hypothesized that there are cells in the axolotl that synthesize specific HSPGs that control growth factor signaling in time and space. Given their high level of HSPG expression, their stellate morphology, and their distribution throughout the loose connective tissues, we refer to these as the positional information GRID (Groups that are Regenerative, Interspersed and Dendritic) cells.''

'''Parish, C., 2005. Heparan sulfate and inflammation. Nature Immunology 6(9):861-2 ·  October. &lt;nowiki&gt;https://www.researchgate.net/publication/7645220_Heparan_sulfate_and_inflammation&lt;/nowiki&gt;.'''&lt;ref&gt;{{Cite journal |last=Parish |first=Christopher |date=2005-10-01 |title=Heparan sulfate and inflammation |url=https://www.researchgate.net/publication/7645220_Heparan_sulfate_and_inflammation |journal=Nature immunology |volume=6 |pages=861–2 |doi=10.1038/ni0905-861}}&lt;/ref&gt; ''Entry of leukocytes into tissues is a key feature of inflammation. New data suggest the polysaccharide heparan sulfate is required for several stages of this entry process.''

'''Park, P.J, and D. Shukla. Role of heparan sulfate in ocular diseases, Experimental Eye Research, Volume 110, 2013, Pages 1-9, ISSN 0014-4835, &lt;nowiki&gt;https://doi.org/10.1016/j.exer.2013.01.015&lt;/nowiki&gt;.'''&lt;ref&gt;{{Cite journal |last=Park |first=Paul J. |last2=Shukla |first2=Deepak |date=2013-05-01 |title=Role of heparan sulfate in ocular diseases |url=https://www.sciencedirect.com/science/article/pii/S0014483513000274 |journal=Experimental Eye Research |volume=110 |pages=1–9 |doi=10.1016/j.exer.2013.01.015 |issn=0014-4835 |pmc=3638857 |pmid=23410824}}&lt;/ref&gt; ''Abstract: Heparan sulfate (HS), a ubiquitous and structurally diverse cell surface polysaccharide and extracellular matrix component, is a factor common to several major eye pathologies. Its multitude of functions and variable distribution among the different ocular tissues makes it an important contributor to a variety of disease states. Although HS facilitates the pathogenesis of many disorders, its role in each varies. Unique functions of HS have been particularly noted in viral and bacterial keratitis and age-related macular degeneration.'' 

'''Pérez, C., Sawmiller, D. &amp; Tan, J. The role of heparan sulfate deficiency in autistic phenotype: potential involvement of Slit/Robo/srGAPs-mediated dendritic spine formation. Neural Dev 11, 11 (2016). &lt;nowiki&gt;https://doi.org/10.1186/s13064-016-0066-x&lt;/nowiki&gt;''' &lt;ref name=&quot;:8&quot; /&gt; ''Autism Spectrum Disorders (ASD) are the second most common developmental cause of disability in the United States. The brains of ASD patients have marked structural abnormalities, in the form of increased dendritic spines and decreased long distance connections. These structural differences may be due to deficiencies in Heparin Sulfate (HS), a proteoglycan involved in a variety of neurodevelopmental processes. Through interference with this pathway, HS deficiency can lead to excess spine formation.''

'''Poli, Maura, Michela Asperti, Paola Ruzzenenti, Annamaria Naggi, and Paolo Arosio. 2017. &quot;Non-Anticoagulant Heparins Are Hepcidin Antagonists for the Treatment of Anemia&quot; Molecules 22, no. 4: 598. &lt;nowiki&gt;https://doi.org/10.3390/molecules22040598&lt;/nowiki&gt;'''&lt;ref&gt;{{Cite journal |last=Poli |first=Maura |last2=Asperti |first2=Michela |last3=Ruzzenenti |first3=Paola |last4=Naggi |first4=Annamaria |last5=Arosio |first5=Paolo |date=2017-04-08 |title=Non-Anticoagulant Heparins Are Hepcidin Antagonists for the Treatment of Anemia |url=https://www.mdpi.com/1420-3049/22/4/598 |journal=Molecules |language=en |volume=22 |issue=4 |pages=598 |doi=10.3390/molecules22040598 |issn=1420-3049 |pmc=6154463 |pmid=28397746}}&lt;/ref&gt; ''This review summarizes recent findings on the anti-hepcidin activity of heparins and their possible use for the treatment of anemia caused by hepcidin excess, including the anemia of chronic diseases.''

'''Russel A.L. and M.F.McCarty, 2000 Glucosamine for migraine prophylaxis?  Medical Hypotheses. Volume 55, Issue 3, September 2000, Pages 195-198. &lt;nowiki&gt;http://www.sciencedirect.com/science/article/pii/S0306987799910125&lt;/nowiki&gt;''' ''We postulate that supplemental glucosamine can boost mast cell heparin synthesis – perhaps correcting a functional heparin deficiency – thereby preventing or ameliorating the neurogenic inflammation that mediates pain in vascular headache. Whether or not this idea has validity, a controlled study of glucosamine for migraine prophylaxis appears to be warranted.''

'''Stringer, S.E. and Gallagher. 1997. Molecules in focus. Heparan sulphate. The International Journal of Biochemistry &amp; Cell Biology, Volume 29, Issue 5, 1997.''' ''Heparan sulphates, the N-sulphated polysaccharides components of proteoglycans, are common constituents of cell surfaces and the extracellular matrix. The diverse functions of heparan sulphate, which range from the control of blood coagulation to the regulation of cell growth and adhesion, depend on the capacity of the chains to activate protein ligands, such as antithrombin III and members of the fibroblast growth factor family. These properties are currently being exploited in the development of synthetic heparan sulphates as anticoagulants and promoters of wound healing. Conversely organic mimics of growth factor activating saccharides could possibly be designed to suppress tumour growth and prevent restenosis after coronary vessel angioplasty.''

'''Theoharides TC et al.  1999. Stress-induced rat intestinal mast cell intragranular activation and inhibitory effect of sulfated proteoglycans.  Digestive Diseases and Sciences [1999, 44 (8 Suppl):87S-93S]. Pages 709-714. &lt;nowiki&gt;http://europepmc.org/abstract/med/10490045&lt;/nowiki&gt;''' ''Cyclic vomiting syndrome is characterized by sudden episodes of vomiting and abdominal pain. It occurs primarily in children, is exacerbated by stress, and is often considered a migraine equivalent. Migraines have been linked to mast cells, which are often found close to neurons where they are activated by neuropeptides. We investigated the ultrastructural appearance of rat ileal brush border and mast cells following acute stress by immobilization.These results suggest the possible usefulness of chondroitin sulfate in conditions such as cyclic vomiting syndrome.''

'''Thompson, W.R. 2011. Perlecan modulates the function of the osteocyte lacuno-canalicular system. University of Delaware, ProQuest Dissertations Publishing, 2011. 3443246.''' ''In this study, along with my colleagues, I examined osteocyte lacunocanalicular morphology in mice deficient in the large heparan sulfate proteoglycan (HSPG) PLN in this tissue. . . Ultrastructural measurements using electron micrograph images of PLN deficient mice demonstrate a significant decrease in osteocyte canalicular pericellular area, resulting from a reduction in the total canalicular area, when compared to controls. Additionally, PLN deficient mice show significantly diminished canalicular density and a significant reduction in the number of transverse tethering elements per canaliculus.''

'''van den Born J, van den Heuvel LP, Bakker MA, Veerkamp JH, Assmann KJ, Weening JJ, Berden JH., 1993. ''Distribution of GBM heparan sulfate proteoglycan core protein and side chains in human glomerular diseases.'' Kidney Int. 1993 Feb;43(2):454-63. &lt;nowiki&gt;http://www.ncbi.nlm.nih.gov/pubmed/8441243&lt;/nowiki&gt;'''  ''Using monoclonal antibodies (mAbs) recognizing either the core protein or the heparan sulfate (HS) side chain of human GBM heparan sulfate proteoglycan (HSPG), we investigated their glomerular distribution on cryostat sections of human kidney tissues. In conclusion, major alterations were observed in the glomerular distribution of HS and HSPG-core in various human glomerulopathies. The mAbs can be useful to further delineate the significance of HSPG and HS for glomerular diseases.''

'''Vicente, Carolina Meloni, da Silva, Daiana Aparecida, Sartorio, Priscila Veronica, Silva, Tiago Donizetti, Saad, Sarhan Sydney, Nader, Helena Bonciani, Forones, Nora Manoukian, Toma, Leny, Heparan Sulfate Proteoglycans in Human Colorectal Cancer, Analytical Cellular Pathology, 2018, 8389595, 10 pages, 2018.''' &lt;nowiki&gt;https://doi.org/10.1155/2018/8389595&lt;/nowiki&gt;'''  &lt;nowiki&gt;https://www.hindawi.com/journals/acp/2018/8389595/&lt;/nowiki&gt;''' ''Heparan sulfate proteoglycans are complex molecules present in the cell membrane and extracellular matrix, which play vital roles in cell adhesion, migration, proliferation, and signaling pathways. Heparan sulfate proteoglycans are candidate molecules to clarify colorectal cancer tumorigenesis, as well as important targets to therapy and diagnosis.''

'''Vlodavestky, I. et al. 2007. Heparanase: Structure, Biological Functions, and Inhibition by Heparin-Derived Mimetics of Heparan Sulfate. Current Pharmaceutical Design, Volume 13, Number 20, July 2007, pp. 2057-2073(17). &lt;nowiki&gt;http://www.ingentaconnect.com/content/ben/cpd/2007/00000013/00000020/art00004&lt;/nowiki&gt;''' ''Heparanase is an endoglycosidase which cleaves heparan sulfate (HS) and hence participates in degradation and remodeling of the extracellular matrix (ECM). Heparanase is preferentially expressed in human tumors and its over-expression in tumor cells confers an invasive phenotype in experimental animals. These observations and the unexpected identification of a single functional heparanase, suggest that the enzyme is a promising target for anti-cancer and anti-inflammatory drug development.''

'''Weihua T. et al. 2002. Heparanase: A Key Enzyme in Invasion and Metastasis of Gastric Carcinoma.Mod Pathol 2002;15(6):593–59. &lt;nowiki&gt;http://www.nature.com/modpathol/journal/v15/n6/abs/3880571a.html&lt;/nowiki&gt;''' ''Previous reports have shown that the biochemical activity of heparanase is significantly correlated with the invasion and metastasis of malignant cells in vitro.'' ''It was concluded that heparanase might play an important role in the development of invasion and metastasis of the gastric cancer. It was indicated that patients with heparanase-positive gastric carcinoma would have a greater chance of metastasis with a poor prognosis.''

'''Whitelock John M. and Renato V. Iozzo, 2005. H''eparan Sulfate:  A Complex Polymer Charged with Biological Activity''. Chem. Rev., 2005, 105 (7), pp 2745–2764. &lt;nowiki&gt;http://pubs.acs.org/doi/pdf/10.1021/cr0102&lt;/nowiki&gt;''' ''  “HS is a complex and highly active biopolymer…” one section is on heparan sulfate therapies,''

'''Yan Yin, Adam Wang, Li Feng, Yu Wang, Hong Zhang, Ivy Zhang, Brent M Bany, Liang Ma, Heparan Sulfate Proteoglycan Sulfation Regulates Uterine Differentiation and Signaling During Embryo Implantation, Endocrinology, Volume 159, Issue 6, June 2018, Pages 2459–2472, &lt;nowiki&gt;https://doi.org/10.1210/en.2018-00105&lt;/nowiki&gt;'''  ''One important modulator of these signaling pathways is the cell surface and extracellular matrix macromolecules, heparan sulfate proteoglycans (HSPGs). HSPGs play crucial roles in signal transduction by regulating morphogen transport and ligand binding. In this study, we examine the role of HSPG sulfation in regulating uterine receptivity…''

'''Zhongjun Zhou et al. 2004.  Impaired Angiogenesis, Delayed Wound Healing and Retarded Tumor Growth in Perlecan Heparan Sulfate-Deficient Mice. DOI: 10.1158/0008-5472.CAN-04-0810 Published July 2004. &lt;nowiki&gt;http://cancerres.aacrjournals.org/content/64/14/4699&lt;/nowiki&gt;.''' ''Perlecan, a modular proteoglycan carrying primary heparan sulfate (HS) side chains, is a major component of blood vessel basement membranes.Perlecan HS-deficient (Hspg2Δ3/Δ3) mice survived embryonic development and were apparently healthy as adults. However, mutant mice exhibited significantly delayed wound healing, retarded FGF-2-induced tumor growth, and defective angiogenesis.''

'''Zhu W, Li J, Liang G. How does cellular heparan sulfate function in viral pathogenicity? Biomed Environ Sci. 2011 Feb;24(1):81-7. doi: 10.3967/0895-3988.2011.01.011. PMID: 2144084'''4. ''Heparan sulfate (HS) is ubiquitously expressed on the surfaces and in the extracellular matrix of virtually all cell types, making it an ideal receptor for viral infection. Understanding how heparan sulfate functions during virus infection in vivo may prove critical for elucidating the molecular mechanism of viral pathogenesis, and may contribute to the development of therapeutics targeting HS''.

== Case studies ==
'''Ahn, YS., Kim, S., Kim, WJ. et al. Characteristics of hip impingement syndrome in patients with multiple hereditary exostoses. BMC Musculoskelet Disord 22, 153 (2021). &lt;nowiki&gt;https://doi.org/10.1186/s12891-021-04021-1&lt;/nowiki&gt;'''&lt;ref&gt;{{Cite journal |last=Ahn |first=Yeong-Seub |last2=Kim |first2=Sungmin |last3=Kim |first3=Woo-Jong |last4=Lim |first4=Jun-Hyuk |last5=Jung |first5=Sung-Taek |date=2021-02-06 |title=Characteristics of hip impingement syndrome in patients with multiple hereditary exostoses |url=https://doi.org/10.1186/s12891-021-04021-1 |journal=BMC Musculoskeletal Disorders |language=en |volume=22 |issue=1 |pages=153 |doi=10.1186/s12891-021-04021-1 |issn=1471-2474 |pmc=7868013 |pmid=33549073}}&lt;/ref&gt; ''Between 2001 and 2019, total 51 patients (102 hips) were evaluated in this study. Patients with MHE were classified to femoro-acetabular impingement (FAI) symptom group, ischio-femoral impingement (IFI) symptom group and non-impingement symptom group by comparing the symptoms, clinical signs and imaging studies.'' 

'''Albokhari, Daniah, Christopher R. Bailey, Francis Hwang, Clifford R. Weiss, Jonathan Forsberg, Nara Sobreira.  2023. Venous malformation may be a feature of EXT1-related hereditary multiple exostoses: A report of two unrelated probands.  American Journal of Medical Genetics.''' '' ''&lt;ref&gt;{{Cite journal |last=Albokhari |first=Daniah |last2=Bailey |first2=Christopher R. |last3=Hwang |first3=Francis |last4=Weiss |first4=Clifford R. |last5=Forsberg |first5=Jonathan |last6=Sobreira |first6=Nara |date=2023 |title=Venous malformation may be a feature of EXT1-related hereditary multiple exostoses: A report of two unrelated probands |url=https://onlinelibrary.wiley.com/doi/abs/10.1002/ajmg.a.63158 |journal=American Journal of Medical Genetics Part A |language=en |volume=191 |issue=6 |pages=1570–1575 |doi=10.1002/ajmg.a.63158 |issn=1552-4833}}&lt;/ref&gt; ''Report two unrelated probands that presented with a clinical and molecular diagnosis of HME with venous malformation, a clinical feature not previously reported in individuals with HME.''

'''Anel-Quimpo, Joselynna, Mark Anthony Santiago Sandoval, Frances Lina Lantion-Ang, 2011. Hypercalcaemia from genitourinary tuberculosis in a female with multiple exostoses. BMJ Journals. &lt;nowiki&gt;https://casereports.bmj.com/content/2011/bcr.12.2010.3651&lt;/nowiki&gt;.'''&lt;ref&gt;{{Cite journal |last=Anel-Quimpo |first=Joselynna |last2=Sandoval |first2=Mark Anthony Santiago |last3=Lantion-Ang |first3=Frances Lina |date=2011-05-17 |title=Hypercalcaemia from genitourinary tuberculosis in a female with multiple exostoses |url=https://casereports.bmj.com/content/2011/bcr.12.2010.3651 |journal=BMJ Case Reports |language=en |volume=2011 |pages=bcr1220103651 |doi=10.1136/bcr.12.2010.3651 |issn=1757-790X}}&lt;/ref&gt; ''The authors present a puzzling case of nephrolithiasis, hypercalcaemia, amenorrhoea, short stature and gross skeletal deformities in a 30-year-old female. Multiple pituitary hormone deficiency and metabolic bone disease were initially considered but were eventually excluded. The final diagnosis is genitourinary tuberculosis (TB) which caused the hypercalcaemia, nephrolithiasis and amenorrhoea, and also found to have the syndrome of multiple exostoses which explained the gross skeletal deformities and the short stature. After treatment with anti-TB therapy, there was resolution of hypercalcaemia and return of regular menstruation. The short stature and gross skeletal deformities remain as part of the congenital syndrome.''

'''Bari MS, Jahangir Alam MM, Chowdhury FR, Dhar PB, Begum A. 2012. Hereditary multiple exostoses causing cord compression. J Coll Physicians Surg Pak 22:797–799.'''&lt;ref name=&quot;:2&quot; /&gt;''' ''' ''Neurological presentations are rare and usually happened due to direct compression of a peripheral nerve or nerve root or less often the spinal cord. This case is possibly the first case of HME described from Bangladesh, presented with dorsal cord compression. Decompression was done and the complaints of myelopathy were improved.''

'''Caino, Silvia, Marisa Angelica Cubilla, Romina Alba, María Gabriela Obregón, Virginia Fano, Abel Gómez, Lorena Zecchini, Pablo Lapunzina, Miriam Aza-Carmona, Karen E. Heath, and et al. 2022. &quot;Clinical and Genetic Analysis of Multiple Osteochondromas in a Cohort of Argentine Patients&quot; Genes 13, no. 11: 2063.''' '''&lt;nowiki&gt;https://doi.org/10.3390/genes13112063&lt;/nowiki&gt;'''&lt;ref&gt;{{Cite journal |last=Caino |first=Silvia |last2=Cubilla |first2=Marisa Angelica |last3=Alba |first3=Romina |last4=Obregón |first4=María Gabriela |last5=Fano |first5=Virginia |last6=Gómez |first6=Abel |last7=Zecchini |first7=Lorena |last8=Lapunzina |first8=Pablo |last9=Aza-Carmona |first9=Miriam |last10=Heath |first10=Karen E. |last11=Asteggiano |first11=Carla Gabriela |date=2022-11-07 |title=Clinical and Genetic Analysis of Multiple Osteochondromas in a Cohort of Argentine Patients |url=https://www.mdpi.com/2073-4425/13/11/2063 |journal=Genes |language=en |volume=13 |issue=11 |pages=2063 |doi=10.3390/genes13112063 |issn=2073-4425 |pmc=9690389 |pmid=36360300}}&lt;/ref&gt; ''Multiple Osteochondromatosis (MO, MIM 133700 &amp; 133701), an autosomal dominant O-glycosylation disorder (EXT1/EXT2-CDG), can be associated with a reduction in skeletal growth, bony deformity, restricted joint motion, shortened stature and pathogenic variants in two tumor suppressor genes, EXT1 and EXT2. In this work, we report a cross-sectional study including 35 index patients and 20 affected family members. Clinical phenotyping of all 55 affected cases was obtained, but genetic studies were performed only in 35 indexes.''

'''Hariri O, Al Laham O, Ibrahim Basha Z, Ghannam E, Ghannam M, Mohammad A. Multiple Hereditary Exostoses instigating a popliteal pseudoaneurysm in a young Middle Eastern male: A case report and literature review. Int J Surg Case Rep. 2024 Apr 12;118:109633. doi: 10.1016/j.ijscr.2024.109633. Epub ahead of print. PMID: 38626641; PMCID: PMC11035074.'''&lt;ref&gt;{{Cite journal |last=Hariri |first=Omar |last2=Al Laham |first2=Omar |last3=Ibrahim Basha |first3=Zein |last4=Ghannam |first4=Eman |last5=Ghannam |first5=Mohammad |last6=Mohammad |first6=Ammar |date=2024-05 |title=Multiple Hereditary Exostoses instigating a popliteal pseudoaneurysm in a young Middle Eastern male: A case report and literature review |url=https://journals.lww.com/10.1016/j.ijscr.2024.109633 |journal=International Journal of Surgery Case Reports |language=en |volume=118 |issue=C |doi=10.1016/j.ijscr.2024.109633 |issn=2210-2612 |pmc=11035074 |pmid=38626641}}&lt;/ref&gt; ''We present the case of a 37-year-old Middle Eastern male with Multiple Hereditary Exostoses who experienced sudden-onset left lower limb pain persisting for a month prior to admission. It was associated with coldness and paresthesia of the ipsilateral lower limb. The presurgical radiological workup uncovered a popliteal pseudoaneurysm subsequent to Multiple Hereditary Exostoses.''

'''Kambouris, M., Fadda A, Al-Arraj, Y, et al., 2016. Putative Relation Between Autism Spectrum Disease &amp; Hereditary Multiple Exostosis Investigated by Whole Genome Sequencing &amp; Comparative Genome Analyses in a Family with ASD and HME with EXT-1 Mutations''' ''A family with two male children affected with ASD and HME as well as an unaffected female child, was studied to identify the Genetic basis of ASD in the family and the possible relation between ASD &amp; HME. The HME unaffected parent [mother] contributed heterozygous variants in the Heparan Sulfate biosynthesis pathway that in synergy with the EXT-1 mutation could be the genetic causes of ASD in the family.''

'''Kim, Min Jeong, Yunjin Lee, Sang Ook Nam, Young Mi Kim, 2021. An 8q24.11q24.13 Microdeletion Encompassing EXT1 in a Boy with Autistic Spectrum Disorder, Intellectual Disability, and Multiple Hereditary Exostoses. Annals of Child Neurology. Letter to the Editor, 11/9/2021.''' ''Here, we describe the case of a boy with a microdeletion (8q24.11q24.13 [118,625,768-124,169,620]×1), who presented with autism, intellectual disability, and MHE. the parents signed informed consent and approved the anonymous use of clinical and molecular data for the present diagnostic study'''''.'''

'''Küçükesmen, Çiḡdem DDS, PhD, Buḡra Özen, DDS, PhD,b and Mustafa Akçam, DDS, PhDc, 1997. Multiple Hereditary Osteochondromatosis: A Case Report. Eur J Dent. 2007 Jul; 1(3): 183–187.&lt;nowiki&gt;https://www.ncbi.nlm.nih&lt;/nowiki&gt;.''' ''Common carious lesions owing to vomiting are not widespread in children. In this case, we aimed to report an 11-years-old male patient with common carious lesions due to repeated vomitings, chewing and eating difficulty and retarded growth with Multiple Hereditary Osteochondromatosis (MHO).''

'''Li H, Yamagata T, Mori M, Momoi MY. 2002.Association of autism in two patients with hereditary multiple exostoses caused by novel deletion mutations of EXT1. J Hum Genet 2002;47:262-5. &lt;nowiki&gt;https://pubmed.ncbi.nlm.nih.gov/12032595/&lt;/nowiki&gt;.'''&lt;ref&gt;{{Cite journal |last=Li |first=Hung |last2=Yamagata |first2=Takanori |last3=Mori |first3=Masato |last4=Momoi |first4=Mariko Y. |date=2002 |title=Association of autism in two patients with hereditary multiple exostoses caused by novel deletion mutations of EXT1 |url=https://pubmed.ncbi.nlm.nih.gov/12032595 |journal=Journal of Human Genetics |volume=47 |issue=5 |pages=262–265 |doi=10.1007/s100380200036 |issn=1434-5161 |pmid=12032595}}&lt;/ref&gt;''  Two boys from separate families presented with hereditary multiple exostoses (EXT) and autism associated with mental retardation.'' 

'''Malagón, V., 2001.  Development of Hip Dysplasia in Hereditary Multiple Exostosis. Journal of Pediatric Orthopaedics, 21(2): 205-211.  &lt;nowiki&gt;https://journals.lww.com/pedorthopaedics/Abstract/2001/03000/Development_of_Hip_Dysplasia_in_Hereditary.14.aspx&lt;/nowiki&gt;''.'''''&lt;ref&gt;{{Cite web |title=Development of Hip Dysplasia in Hereditary... : Journal of Pediatric Orthopaedics |url=https://www.ovid.com/jnls/pedorthopaedics/fulltext/01241398-200103000-00014~development-of-hip-dysplasia-in-hereditary-multiple |access-date=2026-07-16 |website=Ovid |language=en}}&lt;/ref&gt; ''In approximately 25% of patients with hereditary multiple exostosis, there is an abnormal osteochondral formation localized in the femoral proximal metaphysis. Although this entity is rather frequent and quite severe, it is rarely found in the medical literature. The author describes six private cases, taken from a total of 24,000 patients (0.25/1000) as examples of this entity, and provides a review of the literature.'' 

'''Mazza, D., Fabbri, M., Calderaro, C., Iorio, C., Labianca, L., Poggi, C., Turturro, F., Montanaro, A., &amp; Ferretti, A. (2017). Chest pain caused by multiple exostoses of the ribs: A case report and a review of literature. World journal of orthopedics, 8(5), 436–440. https://doi.org/10.5312/wjo.v8.i5.436&lt;nowiki/&gt;.'''&lt;ref&gt;{{Cite journal |last=Mazza |first=Daniele |last2=Fabbri |first2=Mattia |last3=Calderaro |first3=Cosma |last4=Iorio |first4=Carlo |last5=Labianca |first5=Luca |last6=Poggi |first6=Camilla |last7=Turturro |first7=Francesco |last8=Montanaro |first8=Antonello |last9=Ferretti |first9=Andrea |date=2017 |title=Chest pain caused by multiple exostoses of the ribs: A case report and a review of literature |url=http://www.wjgnet.com/2218-5836/full/v8/i5/436.htm |journal=World Journal of Orthopedics |language=en |volume=8 |issue=5 |pages=436 |doi=10.5312/wjo.v8.i5.436 |issn=2218-5836 |pmc=5434351 |pmid=28567348}}&lt;/ref&gt; ''An exceptional case of multiple internal exostoses of the ribs in a young patient affected by multiple hereditary exostoses (MHE) coming to our observation for chest pain as the only symptom of an intra-thoracic localization. The computed tomography (CT) scan revealed the presence of three exostoses located on the left third, fourth and sixth ribs, all protruding into the thoracic cavity, directly in contact with visceral pleura. Moreover, the apex of the one located on the sixth rib revealed to be only 12 mm away from pericardium.'' 

'''Montgomery BK, Cahan EM, Frick S. Spinal Screening MRI Trends in Patients with Multiple Hereditary Exostoses: National Survey- PubMed''' '''. Cureus. 2019 Dec 23;11(12):e6452. doi: 10.7759/cureus.6452. PMID: 32010535; PMCID: PMC6975245'''''.''&lt;ref&gt;{{Cite journal |last=Montgomery |first=Blake K |last2=Cahan |first2=Eli M |last3=Frick |first3=Steve |date=2019-12-23 |title=Spinal Screening MRI Trends in Patients with Multiple Hereditary Exostoses: National Survey |url=https://www.cureus.com/articles/23789-spinal-screening-mri-trends-in-patients-with-multiple-hereditary-exostoses-national-survey |journal=Cureus |language=en |doi=10.7759/cureus.6452 |issn=2168-8184 |pmc=6975245 |pmid=32010535}}&lt;/ref&gt;  ''Background Multiple hereditary exostoses (MHE) is a rare disease characterized by multiple osteochondromas. Osteochondromas growing into the spinal canal can produce devastating consequences, including permanent neurologic deficits and even death.  This study presents a case of an intracanal osteochondroma at C1 identified by routine screening and a survey describing current practices of MHE experts.''

'''Narvid, J., M. L. Gorno-Tempini, A. Slavotinek, S. J. DeArmond, Y. H. Cha, B. L. Miller &amp; K. Rankin, 2009. Of brain and bone: The unusual case of Dr. A. Neurocase Vol. 15, Iss. 3, 2009.''' '''&lt;nowiki&gt;http://www.tandfonline.com/doi/full/10.1080/13554790802632967&lt;/nowiki&gt;'''&lt;ref&gt;{{Cite journal |last=Narvid |first=J. |last2=Gorno-Tempini |first2=M. L. |last3=Slavotinek |first3=A. |last4=DeArmond |first4=S. J. |last5=Cha |first5=Y. H. |last6=Miller |first6=B. L. |last7=Rankin |first7=K. |date=2009-06-01 |title=Of brain and bone: The unusual case of Dr. A |url=https://doi.org/10.1080/13554790802632967 |journal=Neurocase |volume=15 |issue=3 |pages=190–205 |doi=10.1080/13554790802632967 |issn=1355-4794 |pmc=2997763 |pmid=20183548}}&lt;/ref&gt;''. Frontotemporal dementia (FTD) is a clinical syndrome characterized by progressive decline in social conduct and a focal pattern of frontal and temporal lobe damage. Its biological basis is still poorly understood but the focality of the brain degeneration provides a powerful model to study the cognitive and anatomical basis of social cognition. Here, we present Dr. A, a patient with a rare hereditary bone disease (hereditary multiple exostoses) and FTD (pathologically characterized as Pick's disease),  This case provides new evidence regarding the neural basis of social cognition and suggests a possible genetic link between bone disease and FTD.''

'''Puiu1, Maria , Iulia Simina-Jurca, Simona Dumitriu, Smaranda Arghirescu,  Adela Chirita-Emandi,  2012. . Multiple Hereditary Exostoses - Clinical Features and Management.''' ''We report two cases of skeletally immature patients who presented with multiple exostoses, bone deformation without bone pain; and growth and pubertal retardation. The cases need adequate counseling, long-term follow-up, and measures to improve the quality of life of patients with multiple hereditary exostoses.''

'''Stitzman Wengrowicz, M.L., J  Pretell-Mazzini,  J.P. Dormans, R.S. Davidson, 2011.. Regression of a Sessile Osteochondroma: A Case Study and Review of the Literature.''' ''&lt;nowiki&gt;https://www.researchgate.net/publication/267426996_Regression_of_a_Sessile_Osteochondroma_A_Case_Study_and_Review_of_the_Literature&lt;/nowiki&gt; . The most common benign bone tumor is osteochondroma.  Its natural history is poorly understood as a consequence of its benign symptomatology in most cases. It typically grows in childhood and growth during adulthood can be a sign of malignant  degeneration. We present  a case of  spontaneous regression of  a solitary osteochondroma.  A review of the  current  literature which  reveals 21  other cases of  spontaneous regression  of solitary  osteochondromas is also discussed. We believe that the possibility of regression of solitary osteochondromas should be taken into account when considering surgical excision.''

'''Viala P, Vanel D, Larbi A, Cyteval C, Laredo JD. Bilateral ischiofemoral impingement in a patient with hereditary multiple exostoses. Skeletal Radiol. 2012;41:1637–40. [PubMed] &lt;nowiki&gt;https://pubmed.ncbi.nlm.nih.gov/22865159/&lt;/nowiki&gt;.'''&lt;ref&gt;{{Cite journal |last=Viala |first=Pierre |last2=Vanel |first2=Daniel |last3=Larbi |first3=Ahmed |last4=Cyteval |first4=Catherine |last5=Laredo |first5=Jean-Denis |date=2012-12 |title=Bilateral ischiofemoral impingement in a patient with hereditary multiple exostoses |url=https://pubmed.ncbi.nlm.nih.gov/22865159 |journal=Skeletal Radiology |volume=41 |issue=12 |pages=1637–1640 |doi=10.1007/s00256-012-1488-0 |issn=1432-2161 |pmid=22865159}}&lt;/ref&gt; ''We report a case of bilateral ischiofemoral impingement in a patient with hereditary multiple exostoses. The association of exostoses and femoral metaphyseal widening resulted in the narrowing of the ischiofemoral spaces.''

'''Wang YZ, Park KW, Oh CS, Ahn YS, Kang QL, Jung ST, Song HR. Developmental pattern of the hip in patients with hereditary multiple exostoses. BMC Musculoskelet Disord. 2015;16:54'''''.'' '''https://pmc.ncbi.nlm.nih.gov/articles/PMC4429362/&lt;nowiki/&gt;.'''&lt;ref&gt;{{Cite journal |last=Wang |first=Ya-Zhou |last2=Park |first2=Kwang-Won |last3=Oh |first3=Chang-Seon |last4=Ahn |first4=Yeong-Seub |last5=Kang |first5=Qing-Lin |last6=Jung |first6=Sung-Taek |last7=Song |first7=Hae-Ryong |date=2015-03-15 |title=Developmental pattern of the hip in patients with hereditary multiple exostoses |url=https://pmc.ncbi.nlm.nih.gov/articles/PMC4429362/ |journal=BMC musculoskeletal disorders |volume=16 |pages=54 |doi=10.1186/s12891-015-0514-5 |issn=1471-2474 |pmc=4429362 |pmid=25888017}}&lt;/ref&gt; '''C'''''oxa valga is a common clinical feature of hereditary multiple exostoses (HME). The current study aimed to determine the unique developmental pattern of the hip in patients with HME and evaluate the factors that influence its progression.''

'''Wiater JM, Farley FA. Popliteal pseudoaneurysm caused by an adjacent osteochondroma: a case report and review of the literature. Am J Orthop (Belle Mead NJ). 1999 Jul;28(7):412-6. PMID: 10426440.'''&lt;ref&gt;{{Cite journal |last=Wiater |first=J. M. |last2=Farley |first2=F. A. |date=1999-07 |title=Popliteal pseudoaneurysm caused by an adjacent osteochondroma: a case report and review of the literature |url=https://pubmed.ncbi.nlm.nih.gov/10426440 |journal=American Journal of Orthopedics |volume=28 |issue=7 |pages=412–416 |issn=1078-4519 |pmid=10426440}}&lt;/ref&gt; ''A male 17-year-old with multiple hereditary exostoses presented with a mass in the distal left thigh several days after lifting weights. An arteriogram showed a popliteal artery pseudoaneurysm adjacent to a femoral osteochondroma. The osteochondroma was excised and the artery was repaired with a saphenous vein interposition graft. A review of the literature identified 23 similar reports. The average age of the patients was 21.3 years. Seventy-eight percent were men and half of the patients had multiple hereditary exostoses. Ten patients were initially misdiagnosed. The clinician should consider the diagnosis of pseudoaneurysm in a young patient with an osteochondroma and a mass about the knee.''

'''Zaijun L, Xinhai Y, Zhipeng W, Wending H, Quan H, Zhenhua Z, Dapeng F, Jisheng Z, Wei Z, Jianru X. 2013. Outcome and prognosis of myelopathy and radiculopathy from osteochondroma in the mobile spine: a report on 14 patients. J Spinal Disord Tech 26:194–199.''' ''Fourteen symptomatic spinal osteochondroma (OC)  cases, including 2 hereditary multiple exostoses, were treated surgically from 2001 to 2010.''

= People and books with HME: =
[[w:Deena_Larsen|Deena Larsen]] wrote about her mother at http://www.deenalarsen.net/firs

Irv Rosenfeld wrote about his experiences with medical marijuana from the U.S. government in My Medicine.&lt;ref&gt;{{Cite web |title=MY MEDICINE |url=https://www.goodreads.com/book/show/22078567-my-medicine |access-date=2026-07-15 |website=Goodreads |language=en}}&lt;/ref&gt;

= Spanish Translation =


Problemas de deficiencia de proteoglicano de sulfato de heparán (HSPG). La MHE es el resultado de una mutación en los genes EXT1 y EXT2. Los pacientes con MHE tienen una biosíntesis de HSPG defectuosa: sus cuerpos no producen HSPG (cf Cueller et al. 2013 y Jones et al. 2014). Los HSPG son parte de cada superficie celular y regulan los procesos biológicos (cf Zak et al. 2002, Meneghetti et al. 2015). Desempeñan un papel vital en la adhesión, migración, crecimiento y comunicación celular (Vicente et al. 2018). Whitlock e Iozzo (2005) han identificado varias enfermedades relacionadas con la ausencia de HSPG (es decir, si un proceso corporal requiere HSPG y no hay suficiente HSPG para completar esa función, entonces podrían ocurrir estos problemas). Los pacientes con MHE han reportado síntomas como:

* Baja masa ósea (Nozawa et al. 2018 y Matsumoto et al. 2020)
* Deficiencias neurológicas: Trastorno del espectro autista (Li et al, 2002, Fumitoshi et al. 2012, Irie et al, 2012, Yamaguchi 2012, Perez et al. 2015, Kambouris et al. 2016, Kim et al 2022); y problemas cognitivos (Farhan et al. 2015)
* Demencia frontotemporal (Narvid et al. 2009) y TDAH (Mooney et al. 2016), función cerebral (Condomitti y Wit 2018). Vea también el vídeo de ratones MHE en &lt;nowiki&gt;https://www.youtube.com/watch?v=6-EXRt_YL6A&lt;/nowiki&gt;.
* Enfermedades oculares (Park y Shukla, 2013)
* Defectos dentales (Kucukesmen et al. 2007 y Wiweger et al. 2012)
* Prediabetes (Heibert 2021)Diabetes y dificultad para controlar la glucosa (Matsuzawa 2021)
* Reacciones medicamentosas inusuales (muchos medicamentos actúan sobre el dominio de unión del heparán [Boer y Gaillard 2007]) 
* Fatiga severa y continua (Berg et al. 1999)
* Problemas gástricos graves, incluidas úlceras no causadas por H. pylori (Ascencio et al. 1993 y Chmiela et al. 1995), cáncer gástrico (Weihua et al. 2002) y síndrome de vómitos cíclicos (Kucukesmen et al. 2007 y Theoharides et al. 1999)
* Cálculos renales y otros problemas (véase Van den Born et al. 1993 y Farhan et al. 2015)
* Vértigo e hiperacusia (Lundberg et al., 2014) y migrañas
* Problemas pulmonares (Nackerts et al. 1997 y Haeger et al. 2016)
* Anemia (Poli et al. 2017), coágulos sanguíneos y coagulación (Stringer y Gallagher 1997 y Ho et al. 1997), pseudoaneurismas (Wiater y Farley 1996 y Harari et al. 2024)
* Problemas menstruales y de embarazo extremadamente dolorosos (Alphin et al. 1988, Yin et al. 2018)
* Inflamación (Parroquia 2005); cicatrización lenta de heridas (Zhongjun et al. 2004); cicatrices y queloides (Hosalkar et al. 2007, y problemas del tejido conectivo (Forsberg y Kjellen, 2001 y Otsuka et al. 2020).
* Funciones hepáticas (Arnold et al. 2020 y Dituri et al. 2022)
* Funciones del colesterol y los lípidos (Kolsett y Salmverta 1999) y Síntesis de vitamina D (Cooper 2021)  '''Problemas de crecimiento óseo.''' En la MHE, la falta de HSPG hace que los pacientes desarrollen exostosis, que son tumores benignos en múltiples ubicaciones en todo el cuerpo (Brown 2008, Thompson 2011 y Mansouri et al. 2017). La gravedad (número y tamaño de los tumores y otras complicaciones) de la MHE varía de un paciente a otro. Las exostosis en sí mismas pueden causar numerosos problemas, incluidos: irritación de tendones y músculos que produce dolor y pérdida de movimiento, deformidad esquelética, baja estatura, discrepancia en la longitud de las extremidades, subluxaciones y deformidad angular. Los problemas directamente asociados con estas exostosis incluyen:

* Dolor crónico y problemas con la calidad de vida (Goud et al. 2012)
* Inflamación, respuestas inmunitarias (Callaghan et al. 2018 y Collins y Troeberg 2019)
* Formación de bursa y bursitis resultante, así como artritis de aparición temprana.
* Problemas respiratorios y pulmonares al estar sobre costillas que sobresalen hacia la cavidad torácica (Mazza et al. 2017)
* Irritación de un nervio cercano (dolor, debilidad, entumecimiento, hormigueo)
* Aneurisma de vasos sanguíneos por exostosis que presionan los vasos sanguíneos u otros problemas vasculares (Albokhari et al. 2023)
* Problemas de compresión de la médula espinal: incontinencia, daño nerv'''Résumé de la MEM pour les médecins et les écoles'''

== References ==</text>
      <sha1>j401bxuurdx20542g88jg2dko6a3x99</sha1>
    </revision>
  </page>
  <page>
    <title>Statistics for Sociologists</title>
    <ns>0</ns>
    <id>485134</id>
    <revision>
      <id>4675743</id>
      <parentid>4674439</parentid>
      <timestamp>2026-10-12T14:40:39Z</timestamp>
      <contributor>
        <username>Kittycataclysm</username>
        <id>3371989</id>
      </contributor>
      <comment>flag</comment>
      <origin>4675743</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2512" sha1="py9imxud8k5uh49wijwhvbec0y41ehf" xml:space="preserve">{{AI-suspected|reason=AI-generated graphics, certain typographical and stylistic quirks, massive addition of content in a short timeframe}}

== Table of Contents ==
{| class=&quot;wikitable&quot; | align=right
|-
| {{print version}}
|-
| {{PDF version|Statistics for Sociologists}}
|}

* '''Statistics for Sociologists: An Introduction Using R and the General Social Survey'''
* '''Part I: Foundations'''
** [[/Chapter 1: Why Statistics? Making Sense of Social Life with Data/]] {{stage short|100%|August 6, 2026}}
** [[/Chapter 2: Getting Started with R and RStudio/]] {{stage short|100%|August 6, 2026}}
** [[/Chapter 3: The General Social Survey - What It Is and How to Use It/]] {{stage short|100%|August 18, 2026}}
** [[/Chapter 4: Types of Variables and Levels of Measurement/]] {{stage short|100%|August 19, 2026}}
* '''Part II: Working with Data'''
** [[/Chapter 5: Loading, Exploring, and Cleaning GSS Data/]] {{stage short|100%|September 1, 2026}}
** [[/Chapter 6: Recoding and Transforming Variables/]] {{stage short|100%|September 14, 2026}}
* '''Part III: Descriptive Statistics'''
** [[/Chapter 7: Frequency Distributions and Visualizing Data/]] {{stage short|100%|September 20, 2026}}
** [[/Chapter 8: Measures of Central Tendency/]] {{stage short|100%|September 23, 2026}}
** [[/Chapter 9: Measures of Variability/]] {{stage short|100%|September 29, 2026}}
** [[/Chapter 10: The Normal Distribution and Areas Under the Curve/]] {{stage short|100%|October 5, 2026}}
** [[/Chapter 11: Sampling Distributions, Standard Error, and Statistical Power/]] {{stage short|100%|October 5, 2026}}
** [[/Chapter 12: Confidence Intervals/]] {{stage short|75%|August 6, 2026}}
* '''Part IV: Inferential Statistics'''
** [[/Chapter 13: Hypothesis Testing, t-Tests, and Effect Sizes/]] {{stage short|75%|August 6, 2026}}
** [[/Chapter 14: Chi-Square Tests and Effet Sizes/|Chapter 14: Chi-Square Tests and Effect Sizes]] {{stage short|75%|August 6, 2026}}
** [[/Chapter 15: ANOVA and Effect Sizes/]] {{stage short|75%|August 6, 2026}}
** [[/Chapter 16: Bivariate Regression, Correlation, and Effect Sizes/]] {{stage short|75%|August 6, 2026}}
** [[/Chapter 17: An Introduction to Bayesian Thinking/]] {{stage short|75%|August 6, 2026}}
** [[/Chapter 18: Putting It All Together - Replicating Sociological Research/]] {{stage short|75%|August 6, 2026}}

==Instructor Resources==
* [[/Noted Contributors/]] 
* [[/Course Adoptions/]] (if you adopt this text for your course, please make a note of it on this page)

{{BookCat}}</text>
      <sha1>py9imxud8k5uh49wijwhvbec0y41ehf</sha1>
    </revision>
  </page>
  <page>
    <title>User talk:~2026-40500-29</title>
    <ns>3</ns>
    <id>485583</id>
    <revision>
      <id>4675776</id>
      <parentid>4675663</parentid>
      <timestamp>2026-10-13T01:41:07Z</timestamp>
      <contributor>
        <username>~2026-40500-29</username>
        <id>3615407</id>
      </contributor>
      <comment>/* I have added a tag to a page you created */ Reply some facts about the situation</comment>
      <origin>4675776</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1858" sha1="q8nmk7ddsu7x7heod3nkoqn3ms2p726" xml:space="preserve">
== I have added a tag to a page you created ==
Hi! I'm EggRoll97, and I recently reviewed your page, [[:User:Ottawahitech/American politics]]. I have added a tag to the page, because it &lt;strong&gt;may meet the [[Wikibooks:Deletion policy#Speedy deletions|criteria for speedy deletion]].&lt;/strong&gt; This means that it can be deleted at any time.  If you believe that your page should not be deleted, please post a message on [[User talk:Ottawahitech/American politics|the page's talk page]] explaining why. &lt;strong&gt;If your reasoning is convincing, your page may be saved.&lt;/strong&gt; If you have any questions or concerns, please [[User talk:EggRoll97|let me know]]. Thank you! &lt;!-- Substituted from User:JJPMaster/CurateThisPage/authorMsg --&gt; [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 22:52, 13 September 2026 (UTC)

:Hi @[[User:EggRoll97|EggRoll97]], Thanks for letting me know. Unfortunately by the time I discovered your post here my file was already deleted. [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 01:39, 16 September 2026 (UTC)
::Stop creating pages in another user's space and they won't get deleted. [[User:MarcGarver|MarcGarver]] ([[User talk:MarcGarver|discuss]] • [[Special:Contributions/MarcGarver|contribs]]) 09:32, 12 October 2026 (UTC)
:::hi @[[User:MarcGarver|MarcGarver]],
:::I am editting here without logging in which gives me an anon account at Wikibooks. The pages I have added are to my own user-space. For more information about the file I am asking to undelete please see a discussion I started about it a month ago:
:::* [[Wikibooks:Reading room/General#Who is allowed to delete pages here?]]
:::[[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 01:41, 13 October 2026 (UTC)</text>
      <sha1>q8nmk7ddsu7x7heod3nkoqn3ms2p726</sha1>
    </revision>
    <revision>
      <id>4675804</id>
      <parentid>4675776</parentid>
      <timestamp>2026-10-13T08:27:50Z</timestamp>
      <contributor>
        <username>MarcGarver</username>
        <id>134830</id>
      </contributor>
      <comment>/* I have added a tag to a page you created */ Reply</comment>
      <origin>4675804</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2138" sha1="3eeodppl1g9ljiy8nv1x2hagnsv89dw" xml:space="preserve">
== I have added a tag to a page you created ==
Hi! I'm EggRoll97, and I recently reviewed your page, [[:User:Ottawahitech/American politics]]. I have added a tag to the page, because it &lt;strong&gt;may meet the [[Wikibooks:Deletion policy#Speedy deletions|criteria for speedy deletion]].&lt;/strong&gt; This means that it can be deleted at any time.  If you believe that your page should not be deleted, please post a message on [[User talk:Ottawahitech/American politics|the page's talk page]] explaining why. &lt;strong&gt;If your reasoning is convincing, your page may be saved.&lt;/strong&gt; If you have any questions or concerns, please [[User talk:EggRoll97|let me know]]. Thank you! &lt;!-- Substituted from User:JJPMaster/CurateThisPage/authorMsg --&gt; [[User:EggRoll97|EggRoll97]] ([[User talk:EggRoll97|discuss]] • [[Special:Contributions/EggRoll97|contribs]]) 22:52, 13 September 2026 (UTC)

:Hi @[[User:EggRoll97|EggRoll97]], Thanks for letting me know. Unfortunately by the time I discovered your post here my file was already deleted. [[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 01:39, 16 September 2026 (UTC)
::Stop creating pages in another user's space and they won't get deleted. [[User:MarcGarver|MarcGarver]] ([[User talk:MarcGarver|discuss]] • [[Special:Contributions/MarcGarver|contribs]]) 09:32, 12 October 2026 (UTC)
:::hi @[[User:MarcGarver|MarcGarver]],
:::I am editting here without logging in which gives me an anon account at Wikibooks. The pages I have added are to my own user-space. For more information about the file I am asking to undelete please see a discussion I started about it a month ago:
:::* [[Wikibooks:Reading room/General#Who is allowed to delete pages here?]]
:::[[Special:Contributions/~2026-40500-29|~2026-40500-29]] ([[User talk:~2026-40500-29|talk]]) 01:41, 13 October 2026 (UTC)
::::No, they aren't to your &quot;own&quot; user space. They are to a registered accounts user space. I have no idea if you are the same person. [[User:MarcGarver|MarcGarver]] ([[User talk:MarcGarver|discuss]] • [[Special:Contributions/MarcGarver|contribs]]) 08:27, 13 October 2026 (UTC)</text>
      <sha1>3eeodppl1g9ljiy8nv1x2hagnsv89dw</sha1>
    </revision>
  </page>
  <page>
    <title>User talk:ActStuffOGWiki</title>
    <ns>3</ns>
    <id>485697</id>
    <revision>
      <id>4675741</id>
      <parentid>4672483</parentid>
      <timestamp>2026-10-12T14:20:10Z</timestamp>
      <contributor>
        <username>Kittycataclysm</username>
        <id>3371989</id>
      </contributor>
      <comment>Notifying author about page tagging</comment>
      <origin>4675741</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2303" sha1="5dxap33zpttfkctz9b2hnnunc7l9w6v" xml:space="preserve">

== 2026-09-17 ==
&lt;div class=&quot;mw-content-ltr&quot; dir=&quot;ltr&quot; style=&quot;text-align: left&quot; lang=&quot;en&quot;&gt;[[File:Information.svg|25px|alt=Information icon]] Hello. Apologies for writing this in English, but I wanted to let you know that one or more of [[Special:Contributions/ActStuffOGWiki|your recent contributions]] have been undone because they did not appear constructive. If you would like to experiment, please use the sandbox. Thanks. &lt;/div&gt;&lt;!-- Glow-vandalism1 @ 1789652313696.5s --&gt;&lt;nowiki&gt;&lt;/nowiki&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 13:38, 17 September 2026 (UTC)

:Oh, it's fine. I understand English. Thanks :) [[User:ActStuffOGWiki|ActStuffOGWiki]] ([[User talk:ActStuffOGWiki|discuss]] • [[Special:Contributions/ActStuffOGWiki|contribs]]) 16:20, 17 September 2026 (UTC)

== Categories ==
Hi @[[User:ActStuffOGWiki|ActStuffOGWiki]]! I just wanted to let you know that I deleted [[:Category:Indian Railways]] because that's not how we do categories here at Wikibooks. See [[Wikibooks:Categories]] for additional information. Thanks! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 13:33, 18 September 2026 (UTC)

==[[:Weekly News Around the World!]]==
{{tmbox|type=delete|text='''ActStuffOGWiki, please [[Wikibooks:Requests for deletion#Weekly News Around the World!|share your thoughts]] about whether to [[WB:WIW|keep]] or [[WB:DP|delete]] &quot;[[:Weekly News Around the World!|Weekly News Around the World!]]&quot;.'''&lt;br /&gt;You are being notified because you have contributed to this work. [[User:Omphalographer|Omphalographer]] ([[User talk:Omphalographer|discuss]] • [[Special:Contributions/Omphalographer|contribs]]) 19:37, 26 September 2026 (UTC)}}
==[[:Digital Synthora]]==
{{tmbox|type=delete|text='''ActStuffOGWiki, please [[Wikibooks:Requests for deletion#Digital Synthora|share your thoughts]] about whether to [[WB:WIW|keep]] or [[WB:DP|delete]] &quot;[[:Digital Synthora|Digital Synthora]]&quot;.'''&lt;br /&gt;You are being notified because you have contributed to this work. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 14:20, 12 October 2026 (UTC)}}</text>
      <sha1>5dxap33zpttfkctz9b2hnnunc7l9w6v</sha1>
    </revision>
  </page>
  <page>
    <title>Vehicle Identification Numbers (VIN codes)/Jaguar/VIN Codes</title>
    <ns>0</ns>
    <id>485791</id>
    <revision>
      <id>4675726</id>
      <parentid>4675622</parentid>
      <timestamp>2026-10-12T12:46:43Z</timestamp>
      <contributor>
        <username>JustTheFacts33</username>
        <id>3434282</id>
      </contributor>
      <comment>/* Engine Type (Position 7): */</comment>
      <origin>4675726</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="33584" sha1="gsz134055y8vqwpde53n4eoq0m8xin1" xml:space="preserve">{{Vehicle Identification Numbers (VIN codes)/Warning}}{{clear}}

This VIN number decoding and designation system is used primarily for the North American Market. European and Asian markets use other decoding and designation systems.

==General Template for Jaguar's VIN format (All models: 2000-2015 plus F-Type '16-'17, XJ '16-'19)==

===Jaguar WMIs (2000-) (Position 1-3)===

* SAJ - Jaguar passenger car (UK)
* SAD - Jaguar SUV (UK &amp; Europe)
* L2C - Chery Jaguar Land Rover (China)

===Regional Spec/Restraint System (Position 4):===
* J = Manual seat belts, Dual front airbags (US: XK8 '00)
* B = Manual seat belts, Dual front airbags (Canada: XK8 '00)
* D = Manual seat belts, Depowered Dual front airbags, &amp; Front Side Airbags (US: S-Type '00-'02, XJ8/XJR '00-'03, XK8/XKR '01-'06, XK/XKR Early '07)
* F = Manual seat belts, Depowered Dual front airbags, &amp; Front Side Airbags (Canada: S-Type '00-'02, XJ8/XJR '00-'03, XK8/XKR '01-'06, XK/XKR Early '07)
* E = Manual seat belts, Depowered Dual front airbags w/occupant position sensing, &amp; Front Side Airbags &amp; Side Curtain Airbags (US: X-Type '02-'04, S-Type '03-'04, XJ8/XJR Early '04)
* G = Manual seat belts, Depowered Dual front airbags w/occupant position sensing, &amp; Front Side Airbags &amp; Side Curtain Airbags (Canada: X-Type '02-'04,&lt;br&gt; S-Type '03-'04, XJ8/XJR Early '04)
* W = Manual seat belts, Depowered Dual front airbags w/occupant position (driver) and weight (fr. psgr.) sensing, &amp; Front Side Airbags &amp; Side Curtain Airbags &lt;br&gt; (US: X-Type '05-'08, S-Type '05-'08, XF '09-'15,  XJ8/XJR '04-'09, XJ '10-)
* X = Manual seat belts, Depowered Dual front airbags w/occupant position (driver) and weight (fr. psgr.) sensing, &amp; Front Side Airbags &amp; Side Curtain Airbags (Canada: X-Type '05-'08, S-Type '05-'08, XF '09-'15, XJ8/XJR '04-'09, XJ '10-)
* W = Manual seat belts, Depowered Dual front airbags w/occupant position (driver) and weight (fr. psgr.) sensing, &amp; Front Side Head/Thorax Airbags &lt;br&gt; (US: XK/XKR '07-'15, F-Type '14-)
* X = Manual seat belts, Depowered Dual front airbags w/occupant position (driver) and weight (fr. psgr.) sensing, &amp; Front Side Head/Thorax Airbags &lt;br&gt; (Canada: XK/XKR '07-'15, F-Type '14-)

===Transmission &amp; Steering Location (Position 5 - '00-'12):===
* A = Automatic / LHD
* B = Manual / LHD (X-Type '02-'05, S-Type 3.0 '03-'04)

===Transmission &amp; Drive Wheels (Position 5 - '13-):===
* A = Automatic / Rwd (XF '13-'15, XJ '13-'19, XK '13-'15, F-Type '14-'17)
* B = Manual / Rwd (F-Type '16-'17)
* J = Automatic / Awd (XF Awd '13-'15, XJ Awd '13-'19, F-Type Awd '16-'17)

===Model Line (Position 6-7)===

{| class=&quot;wikitable&quot;
|+Position 6-7
!VIN code
!Description
|-
|51
|[[w:Jaguar X-Type|Jaguar X-Type sedan - High Series]] ('02-'08)
|-
|52
|[[w:Jaguar X-Type|Jaguar X-Type sedan - Entry Series]] ('03-'04)
|-
|53
|[[w:Jaguar X-Type|Jaguar X-Type sedan w/Sport Package]] ('02-'03)
|-
|54
|[[w:Jaguar X-Type|Jaguar X-Type Sportwagon]] ('05-'08)
|-
|01
|[[w:Jaguar S-Type (1999)|Jaguar S-Type]] ('00-'08)
|-
|03
|[[w:Jaguar S-Type (1999)|Jaguar S-Type Sport]] [3.0, 4.0] ('02)
|-
|03
|[[w:Jaguar S-Type (1999)|Jaguar S-Type Sport]] [3.0, 4.2] ('03)
|-
|03
|[[w:Jaguar S-Type (1999)|Jaguar S-Type R]] ('03-'08)
|-
|05
|[[w:Jaguar XF (X250)|Jaguar XF Luxury]] ('09)
|-
|06
|[[w:Jaguar XF (X250)|Jaguar XF Premium Luxury]] ('09)
|-
|07
|[[w:Jaguar XF (X250)|Jaguar XF Supercharged]] ('09)
|-
|0E
|[[w:Jaguar XF (X250)|Jaguar XF]] ('13-'14)
|-
|0F
|[[w:Jaguar XF (X250)|Jaguar XF]] ('10-'12)
|-
|0F
|[[w:Jaguar XF (X250)|Jaguar XF 2.0T Premium]] [8th pos. of VIN is S] ('15)
|-
|0F
|[[w:Jaguar XF (X250)|Jaguar XF 3.0 Sport Rwd or 3.0 Portfolio Rwd]] [8th pos. of VIN is 7] ('15)
|-
|0F
|[[w:Jaguar XF (X250)|Jaguar XF 3.0 Sport Awd or 3.0 Portfolio Awd]] [8th pos. of VIN is F] ('15)
|-
|0G
|[[w:Jaguar XF (X250)|Jaguar XF Premium]] ('10-'11)
|-
|0H
|[[w:Jaguar XF (X250)|Jaguar XF Portfolio]] [8th pos. of VIN is B] ('12)
|-
|0H
|[[w:Jaguar XF (X250)|Jaguar XF Supercharged]] [8th pos. of VIN is E: '10-'13 or P: '13-'15]
|-
|0J
|[[w:Jaguar XF (X250)|Jaguar XFR]] ('10-'15)
|-
|0K
|[[w:Jaguar XF (X250)|Jaguar XFR-S]] ('13-'15)
|-
|8J
|[[w:Jaguar XF (X250)|Jaguar XFR w/Speed Pack]] ('13-'15)
|-
|12
|[[w:Jaguar XJ (X308)#Sport|Jaguar XJ Sport]] ('02-'03)
|-
|14
|[[w:Jaguar XJ (X308)|Jaguar XJ8]] ('00-'03)
|-
|15
|[[w:Jaguar XJ (X308)#XJR|Jaguar XJR]] ('00-'03)
|-
|23
|[[w:Jaguar XJ (X308)|Jaguar XJ8L]] (LWB) ('00-'01)
|-
|24
|[[w:Jaguar XJ (X308)#Daimler/Vanden Plas|Jaguar XJ8 Vanden Plas]] (LWB) ('00-'03)
|-
|25
|[[w:Jaguar XJ (X308)#Daimler/Vanden Plas|Jaguar XJ8 Vanden Plas Supercharged]] (LWB) ('00-'01)
|-
|25
|[[w:Jaguar XJ (X308)#Daimler/Vanden Plas|Jaguar XJ Super V8]] (LWB) ('02-'03)
|-
|71
|[[w:Jaguar XJ (X350)|Jaguar XJ8]] ('04-'09)
|-
|73
|[[w:Jaguar XJ (X350)|Jaguar XJR]] ('04-'09)
|-
|74
|[[w:Jaguar XJ (X350)|Jaguar XJ8 Vanden Plas]] (SWB) ('04)
|-
|79
|[[w:Jaguar XJ (X350)|Jaguar XJ8L]] (LWB) ('05-'09)
|-
|82
|[[w:Jaguar XJ (X350)|Jaguar XJ8 Vanden Plas]] (LWB) ('05-'09)
|-
|82
|[[w:Jaguar XJ (X350)|Jaguar XJ Super V8]] (LWB, 5-psgr.) ('05-'09)
|-
|86
|[[w:Jaguar XJ (X350)|Jaguar XJ Super V8 Portfolio]] (LWB, 4-psgr.) ('06)
|-
|94
|[[w:Jaguar XJ (X350)|Jaguar XJ Super V8 Portfolio]] (LWB, 5-psgr.) ('09)
|-
|1C
|[[w:Jaguar XJ (X351)|Jaguar XJ]] ('10-'15)
|-
|1C
|[[w:Jaguar XJ (X351)|Jaguar XJ R-Sport]] [8th pos. of VIN is 7 (Rwd) or D (Awd)] ('16-'19)
|-
|1C
|[[w:Jaguar XJ (X351)|Jaguar XJ Supercharged]] [8th pos. of VIN is E] ('16-'19)
|-
|1E
|[[w:Jaguar XJ (X351)|Jaguar XJR]] ('14-'17)
|-
|1G
|[[w:Jaguar XJ (X351)|Jaguar XJ Supercharged]] [8th pos. of VIN is E: '10-'13 or T: '13-'15]
|-
|1J
|[[w:Jaguar XJ (X351)|Jaguar XJ Supersport]] ('11-'12)
|-
|2E
|[[w:Jaguar XJ (X351)|Jaguar XJR LWB]] ('14-'17), XJR575 LWB ('18-'19)
|-
|2G
|[[w:Jaguar XJ (X351)|Jaguar XJL]] [8th pos. of VIN is B] ('10-'11)
|-
|2G
|[[w:Jaguar XJ (X351)|Jaguar XJL Portfolio Rwd]] [8th pos. of VIN is B: '12-'13 or 1: '13]
|-
|2G
|[[w:Jaguar XJ (X351)|Jaguar XJL Portfolio Rwd]] [8th pos. of VIN is Z: '14-'15)
|-
|2G
|[[w:Jaguar XJ (X351)|Jaguar XJL Portfolio Rwd]] [8th pos. of VIN is 7: '16-'19), XJ50 3.0 Rwd (LWB) '19
|-
|2G
|[[w:Jaguar XJ (X351)|Jaguar XJL Portfolio Awd]] [8th pos. of VIN is D] ('13-'19), XJ50 3.0 Awd (LWB) '19
|-
|2G
|[[w:Jaguar XJ (X351)|Jaguar XJL Supercharged]] [8th pos. of VIN is E: '10-'13, '16-'19 or T: '13-'15], XJ50 5.0 Rwd (LWB) '19, XJ Collection (LWB) '19
|-
|2J
|[[w:Jaguar XJ (X351)|Jaguar XJL Supersport]] ('11-'13)
|-
|2K
|[[w:Jaguar XJ (X351)|Jaguar XJL Ultimate]] ('13)
|-
|3F
|[[w:Jaguar XJ (X351)|Jaguar XJ Supersport w/Speed Pack]] ('12-'13)
|-
|3G
|[[w:Jaguar XJ (X351)|Jaguar XJL Supersport w/Speed Pack]] ('12-'13)
|-
|3H
|[[w:Jaguar XJ (X351)|Jaguar XJ Supercharged w/Sport &amp; Speed Pack]] ('12-'15)
|-
|3K
|[[w:Jaguar XJ (X351)|Jaguar XJL Supercharged w/Sport &amp; Speed Pack]] ('12-'15)
|-
|41
|[[w:Jaguar XK (X100)|Jaguar XK8/XKR coupe]] ('00-'06)
|-
|42
|[[w:Jaguar XK (X100)|Jaguar XK8/XKR convertible]] ('00-'06)
|-
|43
|[[w:Jaguar XK (X150)|Jaguar XK/XKR coupe]] ('07-'09)
|-
|44
|[[w:Jaguar XK (X150)|Jaguar XK/XKR convertible]] ('07-'09)
|-
|45
|[[w:Jaguar XK (X150)|Jaguar XKR Portfolio Edition coupe]] ('09)
|-
|46
|[[w:Jaguar XK (X150)|Jaguar XKR Portfolio Edition convertible]] ('09)
|-
|4D
|[[w:Jaguar XK (X150)|Jaguar XK Touring coupe]] [8th pos. of VIN is B] ('13-'14)
|-
|4E
|[[w:Jaguar XK (X150)|Jaguar XK Touring convertible]] [8th pos. of VIN is B] ('13-'14)
|-
|4D
|[[w:Jaguar XK (X150)|Jaguar XKR coupe]] [8th pos. of VIN is C] ('10-'15)
|-
|4E
|[[w:Jaguar XK (X150)|Jaguar XKR convertible]] [8th pos. of VIN is C] ('10-'15)
|-
|4F
|[[w:Jaguar XK (X150)|Jaguar XK coupe]] (most Portfolio Edition features are std.) [8th pos. of VIN is B] ('10-'15)
|-
|4F
|[[w:Jaguar XK (X150)|Jaguar XKR175 coupe]] [8th pos. of VIN is C] ('11)
|-
|4F
|[[w:Jaguar XK (X150)|Jaguar XKR coupe w/Dynamic Pack]] [8th pos. of VIN is C] ('13-'15), XK Final Fifty Edition coupe ('15)
|-
|4G
|[[w:Jaguar XK (X150)|Jaguar XK convertible]] (most Portfolio Edition features are std.) [8th pos. of VIN is B] ('10-'15)
|-
|4G
|[[w:Jaguar XK (X150)|Jaguar XKR convertible w/Dynamic Pack]] [8th pos. of VIN is C] ('13-'15), XK Final Fifty Edition convertible ('15)
|-
|4H
|[[w:Jaguar XK (X150)|Jaguar XKR-S coupe]] ('12-'15), XKR-S GT coupe ('14)
|-
|4J
|[[w:Jaguar XK (X150)|Jaguar XKR-S convertible]] ('12-'15)
|-
|6A
|[[w:Jaguar F-Type)|Jaguar F-Type coupe]] ('15-'17), F-Type Premium coupe '17
|-
|6B
|[[w:Jaguar F-Type)|Jaguar F-Type S coupe]] ('15-'17), F-Type S British Design Edition coupe '17
|-
|6D
|[[w:Jaguar F-Type)|Jaguar F-Type R coupe]] ('15-'17)
|-
|6E
|[[w:Jaguar F-Type)|Jaguar F-Type convertible]] ('14-'17), F-Type Premium convertible '17
|-
|6F
|[[w:Jaguar F-Type)|Jaguar F-Type S convertible]] ('14-'17), F-Type S British Design Edition convertible '17
|-
|6G
|[[w:Jaguar F-Type)|Jaguar F-Type V8 S convertible]] ('14-'15)
|-
|6H
|[[w:Jaguar F-Type)|Jaguar F-Type R convertible]] ('16-'17)
|-
|6J
|[[w:Jaguar F-Type)|Jaguar F-Type SVR coupe]] ('17)
|-
|6K
|[[w:Jaguar F-Type)|Jaguar F-Type SVR convertible]] ('17)
|-
|7A
|[[w:Jaguar F-Type#Project 7)|Jaguar F-Type Project 7 convertible]] ('16)
|}

===Engine/Emissions Control System (Position 8)===

{| class=&quot;wikitable&quot;
|+Position 8
! VIN !! Size !! Type !! Fuel !! Valvetrain !! Engine Family/Notes/Applications
|-
| A || 3.0L || 60° V6 || Gas ||DOHC,&lt;br /&gt; 24 valve||MPI. ULEV. Variable intake valve timing. [[w:Jaguar AJ-V6 engine#AJ30|Jaguar AJ-V6 - AJ30 V6 engine]].&lt;br&gt; Jaguar X-Type 3.0 (Mid '05-'08), S-Type 3.0 ('06-'08). 
|-
| A || 4.2L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. ULEV. Continuously variable intake valve timing. [[w:Jaguar AJ-V8 engine#4.2 L|Jaguar AJ-V8 - AJ34 V8 engine]]. Jaguar XF ('10).
|-
| A || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; 550 PS/542 hp. Jaguar XKR-S ('12-'15), XKR-S GT ('14), F-Type R coupe ('15).
|-
| B || 4.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. [[w:Jaguar AJ-V8 engine#Supercharged|Jaguar AJ-V8 - AJ27S V8 engine]].&lt;br&gt; Jaguar XJR ('00-'03), Vanden Plas Supercharged ('00-'01), Super V8 ('02-'03), XKR ('00-'02).
|-
| B || 4.2L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. [[w:Jaguar AJ-V8 engine#Supercharged_2|Jaguar AJ-V8 - AJ33S V8 engine]]. Jaguar XJR ('04-'05), Super V8 ('05), XKR ('03-'06).
|-
| B || 4.2L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. ULEV. Continuously variable intake valve timing. [[w:Jaguar AJ-V8 engine#4.2 L|Jaguar AJ-V8 - AJ34 V8 engine]].&lt;br&gt; Jaguar S-Type ('06-'08), XF ('09), XJ8/Vanden Plas ('06-'09), XK ('07-'09).
|-
| B || 5.0L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. Variable intake valve lift. Variable intake.&lt;br&gt; [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; Jaguar XF ('10-'12), XJ ('11-'12), XJL ('11), XJL Portfolio Rwd ('12-'13), XK ('10-'15), XK Touring ('13-'14).
|-
| C || 3.0L || 60° V6 || Gas ||DOHC,&lt;br /&gt; 24 valve||MPI. Variable intake valve timing. [[w:Jaguar AJ-V6 engine#AJ30|Jaguar AJ-V6 - AJ30 V6 engine]].&lt;br&gt; Jaguar S-Type 3.0 ('00-'01), X-Type 3.0 ('02-Mid '05). 
|-
| C || 4.0L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. Continuously variable intake valve timing. [[w:Jaguar AJ-V8 engine#4.0 L|Jaguar AJ-V8 - AJ27 V8 engine]].&lt;br&gt; Jaguar XJ8/Vanden Plas ('00-'03), XJ Sport ('02-'03), XK8 ('00-'02).
|-
| C || 4.2L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. Continuously variable intake valve timing. [[w:Jaguar AJ-V8 engine#4.2 L|Jaguar AJ-V8 - AJ33 V8 engine]]. Jaguar XJ8 ('04-'05), XK8 ('03-'06).
|-
| C || 4.2L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. ULEV. Continuously variable intake valve timing. [[w:Jaguar AJ-V8 engine#Supercharged_2|Jaguar AJ-V8 - AJ34S V8 engine]].&lt;br&gt; Jaguar S-Type R ('06-'08), XF Supercharged ('09), XJR ('06-'09), Super V8 ('06-'09), XKR ('07-'09).
|-
| C || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; 510 PS/503 hp. Jaguar XFR ('10-'13), XJ/XJL Supersport ('11-'13), XKR ('10-'15).
|-
| C || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 380 PS/375 hp. Jaguar F-Type S ('14-'15), F-Type S w/man. trans. ('16-'17).
|-
| D || 4.0L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. Continuously variable intake valve timing. [[w:Jaguar AJ-V8 engine#4.0 L|Jaguar AJ-V8 - AJ28 V8 engine]]. Jaguar S-Type 4.0 ('00-'01).
|-
| D || 2.5L || 60° V6 || Gas ||DOHC,&lt;br /&gt; 24 valve||MPI. Variable intake valve timing. [[w:Jaguar AJ-V6 engine#AJ25|Jaguar AJ-V6 - AJ25 V6 engine]]. Jaguar X-Type 2.5 ('02-'05).
|-
| D || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar XJ Awd, XJL Portfolio Awd ('13-'15).
|-
| D || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. SULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar XJ R-Sport Awd, XJL Portfolio Awd ('16-'19), XJ50 3.0 Awd ('19).
|-
| E || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; 470 PS/464 hp.&lt;br&gt; Jaguar XF Supercharged ('10-'13), XJ/XJL Supercharged ('11-'13, '16-'19), XJ50 5.0 Rwd ('19), XJ Collection ('19).
|-
| F || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar XF 3.0 Awd ('13-'14).
|-
| F || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. SULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar XF 3.0 Awd ('15).
|-
| H || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas/E85 ||DOHC,&lt;br /&gt; 32 valve||Flex Fuel. Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]]. 510 PS/503 hp. Jaguar XFR ('13-'15).
|-
| K || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; 550 PS/542 hp. Jaguar XJR/XJR LWB ('14-'17).
|-
| K || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; 575 PS/567 hp. Jaguar XJR575 LWB ('18-'19).
|-
| L || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; 495 PS/488 hp. Jaguar F-Type V8 S convertible ('14-'15).
|-
| L || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; 550 PS/542 hp. Jaguar F-Type R  ('16-'17).
|-
| N || 3.0L || 60° V6 || Gas ||DOHC,&lt;br /&gt; 24 valve||MPI. Variable intake valve timing. [[w:Jaguar AJ-V6 engine#AJ30|Jaguar AJ-V6 - AJ30 V6 engine]]. Jaguar S-Type 3.0 ('01-'02).
|-
| P || 4.0L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. Continuously variable intake valve timing. [[w:Jaguar AJ-V8 engine#4.0 L|Jaguar AJ-V8 - AJ28 V8 engine]]. Jaguar S-Type 4.0 ('01-'02).
|-
| P || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas/E85 ||DOHC,&lt;br /&gt; 32 valve||Flex Fuel. Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]]. 470 PS/464 hp. Jaguar XF Supercharged ('13-'15).
|-
| S || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,&lt;br /&gt; 16 valve||Direct Injection. Dual VVT. Ford EcoBoost engine (Mazda L engine-based).&lt;br&gt; Jaguar XF 2.0T ('13-'14), XF 2.0T Premium ('15).
|-
| T || 3.0L || 60° V6 || Gas ||DOHC,&lt;br /&gt; 24 valve||MPI. Variable intake valve timing. [[w:Jaguar AJ-V6 engine#AJ30|Jaguar AJ-V6 - AJ30 V6 engine]]. Jaguar S-Type 3.0 ('03-'05).
|-
| T || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas/E85 ||DOHC,&lt;br /&gt; 32 valve||Flex Fuel. Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]]. 470 PS/464 hp. Jaguar XJ/XJL Supercharged ('13-'15).
|-
| T || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. SULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar F-Type w/auto. trans. ('15-'17), F-Type Premium w/auto. trans. ('17).
|-
| U || 4.2L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. Continuously variable intake valve timing. [[w:Jaguar AJ-V8 engine#4.2 L|Jaguar AJ-V8 - AJ33 V8 engine]]. Jaguar S-Type 4.2 ('03-'05).
|-
| U || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. SULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 380 PS/375 hp. Jaguar F-Type S ('15), F-Type S Rwd w/auto. trans. ('16-'17).
|-
| V || 4.2L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. [[w:Jaguar AJ-V8 engine#Supercharged_2|Jaguar AJ-V8 - AJ33S V8 engine]]. Jaguar S-Type R ('03-'05).
|-
| V || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. SULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 380 PS/375 hp. Jaguar F-Type S Awd w/auto. trans. ('16-'17).
|-
| X || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas/E85 ||DOHC,&lt;br /&gt; 24 valve||Flex Fuel. Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar XF 3.0 Rwd ('14).
|-
| Z || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; 550 PS/542 hp. Jaguar XFR-S ('13-'15).
|-
| Z || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas/E85 ||DOHC,&lt;br /&gt; 24 valve||Flex Fuel. Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar XJ Rwd, XJL Portfolio Rwd ('14-'15).
|-
| 1 || 5.0L || V8 || Gas/E85 ||DOHC,&lt;br /&gt; 32 valve||Flex Fuel. Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. Variable intake valve lift. Variable intake. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]]. Jaguar XJL Portfolio Rwd ('13).
|-
| 6 || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. SULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar F-Type w/man. trans. ('16-'17), F-Type Premium w/man. trans. ('17).
|-
| 7 || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar XF 3.0 Rwd ('13), XJ Rwd ('13), F-Type ('14-'15).
|-
| 7 || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. SULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar XF 3.0 Rwd ('15), XJ R-Sport Rwd ('16-'19), XJL Portfolio Rwd ('16-'19), XJ50 3.0 Rwd ('19).
|-
| 8 || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; 575 PS/567 hp. Jaguar F-Type Project 7 ('16), F-Type SVR ('17).
|}

===Check Digit/Gearbox (Position 9)===
* USA /Canada [[Vehicle Identification Numbers (VIN codes)/Check digit|Check digit]]

===Model Year Code (Position 10)===
''See: [[Vehicle Identification Numbers (VIN codes)/Model year]]''

===Plant Code/Model Line/Engine (Position 11) 2000-2019===
* X - Halewood, Merseyside, England, UK - X-Type 2.5 ('02-'05)
* W - Halewood, Merseyside, England, UK - X-Type 3.0 ('02-'08)
* F - Castle Bromwich, West Midlands, England, UK - S-Type 3.0 ('00-'08)
* G - Castle Bromwich, West Midlands, England, UK - S-Type 4.0 ('00-'02)
* H - Castle Bromwich, West Midlands, England, UK - S-Type 4.2 ('03-'08)
* 1 - Castle Bromwich, West Midlands, England, UK - S-Type R (4.2 supercharged) ('03-'08)
* H - Castle Bromwich, West Midlands, England, UK - XF 4.2 ('09-'10)
* 1 - Castle Bromwich, West Midlands, England, UK - XF Supercharged (4.2 supercharged) ('09)
* L - Castle Bromwich, West Midlands, England, UK - XF 5.0 ('10-'12)
* M - Castle Bromwich, West Midlands, England, UK - XF Supercharged, XFR (5.0 supercharged) ('10-'15), XFR-S (5.0 supercharged) ('13-'15)
* P - Castle Bromwich, West Midlands, England, UK - XF 2.0T ('13-'15)
* 8 - Castle Bromwich, West Midlands, England, UK - XF 3.0 supercharged ('13-'15)
* L - Browns Lane plant, Coventry, West Midlands, England, UK - XJ8 (4.0) ('00-'03), XJ8L (4.0) ('00-'01), XJ8 Vanden Plas (4.0) ('00-'03), XJ Sport (4.0) ('02-'03)
* M - Browns Lane plant, Coventry, West Midlands, England, UK - XJ8 Vanden Plas Supercharged (4.0 supercharged) ('00-'01),&lt;br&gt; Super V8 (4.0 supercharged) ('02-'03), XJR (4.0 supercharged) ('00-'03)
* S - Browns Lane plant, Coventry, West Midlands, England, UK - XJ8 (4.2) ('04-'06), XJ8L (4.2) ('05-'06), XJ8 Vanden Plas (4.0) ('04-'06)
* T - Browns Lane plant, Coventry, West Midlands, England, UK - Super V8 (4.2 supercharged) ('05-'06), Super V8 Portfolio (4.2 supercharged) ('06),&lt;br&gt; XJR (4.2 supercharged) ('04-'06)
* S - Castle Bromwich, West Midlands, England, UK - XJ8 (4.2) ('07-'09), XJ8L (4.2) ('07-'09), XJ8 Vanden Plas (4.0) ('07-'09)
* T - Castle Bromwich, West Midlands, England, UK - Super V8 (4.2 supercharged) ('07-'09), Super V8 Portfolio (4.2 supercharged) ('09),&lt;br&gt; XJR (4.2 supercharged) ('07-'09)
* L - Castle Bromwich, West Midlands, England, UK - XJ (5.0) ('10-'12), XJL (5.0) ('10-'11), XJL Portfolio (5.0) ('12-'13)
* M - Castle Bromwich, West Midlands, England, UK - XJ/XJL Supercharged (5.0 supercharged) ('10-'19), XJ/XJL Supersport (5.0 supercharged) ('11-'13),&lt;br&gt; XJL Ultimate (5.0 supercharged) ('13), XJR SWB/LWB (5.0 supercharged) ('14-'17), XJR575 LWB (5.0 supercharged) ('18-'19), XJ50 LWB (5.0 supercharged) ('19), XJ Collection Sp. Ed. LWB (5.0 supercharged) ('19)
* 8 - Castle Bromwich, West Midlands, England, UK - XJ base (3.0 supercharged) ('13-'15), XJ R-Sport (3.0 supercharged) ('16-'19),&lt;br&gt; XJL Portfolio AWD (3.0 supercharged) ('13-'19), XJL Portfolio RWD (3.0 supercharged) ('14-'19), XJ50 LWB (3.0 supercharged) ('19)
* N - Browns Lane plant, Coventry, West Midlands, England, UK - XK8 (4.0) ('00-'02)
* P - Browns Lane plant, Coventry, West Midlands, England, UK - XKR (4.0 supercharged) ('00-'02)
* 2 - Browns Lane plant, Coventry, West Midlands, England, UK - XK8 (4.2) ('03-'06)
* 3 - Browns Lane plant, Coventry, West Midlands, England, UK - XKR (4.2 supercharged) ('03-'06)
* 5 - Castle Bromwich, West Midlands, England, UK - XK (4.2) ('07-'09)
* 9 - Castle Bromwich, West Midlands, England, UK - XKR (4.2 supercharged) ('07-'09)
* L - Castle Bromwich, West Midlands, England, UK - XK (5.0) ('10-'15)
* M - Castle Bromwich, West Midlands, England, UK - XKR (5.0 supercharged) ('10-'15), XKR-S (5.0 supercharged) ('12-'15), XKR-S GT (5.0 supercharged) ('14)
* 8 - Castle Bromwich, West Midlands, England, UK - F-Type Base, S (3.0 supercharged) ('14-'17), F-Type Premium (3.0 supercharged) ('17)
* M - Castle Bromwich, West Midlands, England, UK - F-Type V8S (5.0 supercharged) ('14-'15), F-Type R (5.0 supercharged) ('15-'17),&lt;br&gt; F-Type Project 7 (5.0 supercharged) ('16), F-Type SVR (5.0 supercharged) ('17)

===Plant Codes (Position 11) 2016-2026===
* A - Solihull, West Midlands, England, UK (XE '17, F-Pace '17-'26)
* C - Castle Bromwich, West Midlands, England, UK (XE '17-'20, XF '16-'24, F-Type '18-'24)
* S - Oxford Road plant, Ryton, West Midlands, England, UK (JLR SVO plant) (XE SV Project 8 '19)
* 1 - Graz, Austria (Magna Steyr plant) (E-Pace '18-'24, I-Pace EV '19-'24)

===Model (Position 12)===
* C - X-Type ('02-'03)
* D - X-Type ('03-'04)
* E - X-Type ('04-'06)
* J - X-Type ('06-'08)
* L - S-Type ('00-'01)
* M - S-Type ('01-'04)
* N - S-Type ('04-'08)
* R - XF ('09-'11)
* S - XF ('11-'13)
* U - XF ('13-'15)
* Y - XF ('16-)
* F - XJ ('00-'03)
* G - XJ ('04-'06) [Browns Lane plant]
* H - XJ ('06-'09) [Castle Bromwich plant]
* V - XJ ('10-'16)
* W - XJ ('16-'19)
* A - XK ('00-'06)
* B - XK ('07-'15)
* K - F-Type ('14-'24)

'''Positions 13–17, Serial Number'''

==General Template for Jaguar's VIN format (1981 - 1999)==

===Jaguar WMIs (1981-1999) (Position 1-3)===
* SAJ - Jaguar passenger car

===Model Line (Position 4)===

{| class=&quot;wikitable&quot;
|+Position 4
!VIN code
!Description
|-
|A
|[[w:Jaguar XJ#Series 3 (1979–1992)|Jaguar XJ6]] ('81-'87), XJ6 Vanden Plas ('82-'87)
|-
|B
|[[w:Jaguar XJ#Series 3 (1979–1992)|Jaguar XJ12]] (Canada only: '81-'88)
|-
|D
|[[w:Jaguar XJ#Series 3 (1979–1992)|Jaguar XJ12]] (Canada only: '89-'92)
|-
|H
|[[w:Jaguar XJ (XJ40)|Jaguar XJ6]] ('88-'89, '93-'94)
|-
|F
|[[w:Jaguar XJ (XJ40)|Jaguar XJ6]] ('90-'92)
|-
|H
|[[w:Jaguar XJ (XJ40)|Jaguar XJ6 Sovereign]] ('90-'92)
|-
|K
|[[w:Jaguar XJ (XJ40)#Daimler/Vanden Plas|Jaguar XJ6 Vanden Plas]] ('88-'94)
|-
|M
|[[w:Jaguar XJ (XJ40)#Majestic (1989–1992 – SWB; 1993–1994 – LWB)|Jaguar XJ6 Vanden Plas Majestic]] ('89-'90, '92)
|-
|M
|[[w:Jaguar XJ (XJ40)#XJ12 and Daimler Double Six (XJ81)|Jaguar XJ12]] ('94)
|-
|H
|[[w:Jaguar XJ (X300)|Jaguar XJ6]] ('95-'97)
|-
|H
|[[w:Jaguar XJ (X300)|Jaguar XJ6L]] LWB [X330] ('97)
|-
|K
|[[w:Jaguar XJ (X300)#Daimler/Jaguar Vanden Plas|Jaguar XJ6 Vanden Plas]] SWB ('95)
|-
|K
|[[w:Jaguar XJ (X300)#Daimler/Jaguar Vanden Plas|Jaguar XJ6 Vanden Plas]] LWB [X330] ('96-'97)
|-
|M
|[[w:Jaguar XJ (X300)#XJ12 (X305)|Jaguar XJ12]] SWB ('95)
|-
|M
|[[w:Jaguar XJ (X300)#XJ12 (X305)|Jaguar XJ12]] LWB [X330] ('96)
|-
|P
|[[w:Jaguar XJ (X300)#XJR (X306)|Jaguar XJR]] ('95-'97)
|-
|H
|[[w:Jaguar XJ (X308)|Jaguar XJ8]] ('98-'99)
|-
|H
|[[w:Jaguar XJ (X308)|Jaguar XJ8L]] LWB ('98-'99)
|-
|K
|[[w:Jaguar XJ (X308)#Daimler/Vanden Plas|Jaguar XJ8 Vanden Plas]] LWB ('98-'99)
|-
|P
|[[w:Jaguar XJ (X308)#XJR|Jaguar XJR]] ('98-'99)
|-
|N
|[[w:Jaguar XJS|Jaguar XJ-S]] ('82-'91), XJ-SC ('86-'88), XJS ('92-'96)
|-
|T
|[[w:Jaguar XJS|Jaguar XJ-S]] Rouge Collection ('89-'90), Classic Collection ('90-'91)
|-
|S
|[[w:Jaguar XJS#XJR-S|Jaguar XJR-S]] ('93)
|-
|G
|[[w:Jaguar XK (X100)|Jaguar XK8]] ('97-'99)
|}

===Class (Regional Spec)/Restraint System (Position 5):===
* V = N. American-spec (Manual seat belts)
* L = Canadian-spec (Manual seat belts)

* Y = XJ6 Vanden Plas [Series III] ('82-'87) (Manual seat belts)

* A = Motorized Shoulder Belts (XJ-S coupe '88-'89, XJ-SC '88)
* Y = Motorized Shoulder Belts (XJ-S coupe '89, XJ sedan '89-'92)
* W = Manual seat belts, Driver-side airbag (US: XJ-S '90-'93, XJ6 '93, XJ12 Early '94)
* X = Manual seat belts, Dual front airbags (US: XJS '94-'96, XJ6 '94-'97, XJ12 '94-'96, XJR '95-'97, XK8 '97-'99)
* X = Manual seat belts, Dual front airbags, &amp; Front Side Airbags (US: XJ8/XJR '98-'99)
* D = Manual seat belts, Depowered Dual front airbags, &amp; Front Side Airbags (US: XJ8/XJR '99)
* M = Manual seat belts, Driver-side airbag (Canada)
* N = Manual seat belts, Dual front airbags (Canada)
* F = Manual seat belts, Depowered Dual front airbags, &amp; Front Side Airbags (Canada: XJ8/XJR '99)

===Body Style (Position 6):===
* 1 = 4-door sedan (XJ-series sedan '81-'99)
* 2 = 2-door convertible w/2+2 seating (XJS convertible '94-'96, XK8 convertible '97-'99)
* 3 = 2-door Cabriolet (XJ-SC '86-'88)
* 4 = 2-door convertible w/2-psgr. seating (factory-built XJS convertible '89-'94, XJR-S convertible '93)
* 5 = 2-door coupe (XJS coupe '82-'96, XJR-S coupe '93, XK8 coupe '97-'99)
* 5 = 2-door coupe (Hess &amp; Eisenhardt-built XJS convertible '87-'88) [coupe conversion]

===Engine Type (Position 7):===
{| class=&quot;wikitable&quot;
|+Position 7
|-
! VIN !! Size !! Type !! Fuel !! Valvetrain !! Engine Family/Notes/Applications
|-
| 1 || 4.0L || I6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||MPI. [[w:Jaguar AJ6 engine#AJ16S|Jaguar AJ16S I6]]. Jaguar XJR ('95-'97).
|-
| 2 || 4.2L || I6 || Gas ||DOHC,&lt;br /&gt; 12 valve||CA &amp; Canada-spec. MPI. [[w:Jaguar XK engine|Jaguar XK I6]]. Jaguar XJ6 ('81-'82).
|-
| 2 || 4.0L || I6 || Gas ||DOHC,&lt;br /&gt; 24 valve||MPI. Dual-canister evaporative emissions system. [[w:Jaguar AJ6 engine#AJ16|Jaguar AJ16 I6]]. Jaguar XJ6 ('96-'97).
|-
| 2 || 4.0L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. Variable intake valve timing. Dual-canister evaporative emissions system. [[w:Jaguar AJ-V8 engine#4.0 L|Jaguar AJ-V8 - AJ26 V8 engine]].&lt;br&gt; Jaguar XJ8 ('98), XK8 ('98).
|-
| 3 || 4.2L || I6 || Gas ||DOHC,&lt;br /&gt; 12 valve||N. America-spec. MPI. [[w:Jaguar XK engine|Jaguar XK I6]]. Jaguar XJ6 ('81-'87).
|-
| 3 || 6.0L || 60° V12 || Gas ||SOHC,&lt;br /&gt; 24 valve||MPI. [[w:Jaguar V12 engine|Jaguar V12]] modified by [[w:Tom Walkinshaw Racing|JaguarSport]]. Jaguar XJR-S ('93).
|-
| 3 || 6.0L || 60° V12 || Gas ||SOHC,&lt;br /&gt; 24 valve||MPI. [[w:Jaguar V12 engine|Jaguar V12]]. Jaguar XJS ('94-'95), XJ12 ('94-'96).
|-
| 5 || 3.6L || I6 || Gas ||DOHC,&lt;br /&gt; 24 valve||N. America-spec - Low Compression. MPI. [[w:Jaguar AJ6 engine|Jaguar AJ6 I6]]. Jaguar XJ6 ('88-'89).
|-
| 6 || 3.6L || I6 || Gas ||DOHC,&lt;br /&gt; 24 valve||N. America-spec - High Compression. MPI. [[w:Jaguar AJ6 engine|Jaguar AJ6 I6]]. Jaguar XJ6 ('88).
|-
| 7 || 4.0L || I6 || Gas ||DOHC,&lt;br /&gt; 24 valve||MPI. [[w:Jaguar AJ6 engine|Jaguar AJ6 I6]]. Jaguar XJ6 ('90-'94), XJS ('93-'94).
|-
| 7 || 4.0L || I6 || Gas ||DOHC,&lt;br /&gt; 24 valve||MPI. [[w:Jaguar AJ6 engine#AJ16|Jaguar AJ16 I6]]. Jaguar XJ6 ('95-'96), XJS ('95-'96).
|-
| 7 || 4.0L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. Variable intake valve timing. [[w:Jaguar AJ-V8 engine#4.0 L|Jaguar AJ-V8 - AJ26 V8 engine]]. Jaguar XK8 ('97).
|-
| 8 || 5.3L || 60° V12 || Gas ||SOHC,&lt;br /&gt; 24 valve||N. America-spec. MPI. [[w:Jaguar V12 engine|Jaguar V12]]. Jaguar XJ-S ('82-'92), XJ12 (Canada only: '88-'92).
|-
| 8 || 4.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. Dual-canister evaporative emissions system. [[w:Jaguar AJ-V8 engine#Supercharged|Jaguar AJ-V8 - AJ26S V8 engine]]. Jaguar XJR ('98-'99).
|-
| 9 || 4.0L || I6 || Gas ||DOHC,&lt;br /&gt; 24 valve||Canada-spec. MPI. [[w:Jaguar AJ6 engine|Jaguar AJ6 I6]]. Jaguar XJ6 ('90-'93), XJS ('93).
|-
| 0 || 5.3L || 60° V12 || Gas ||SOHC,&lt;br /&gt; 24 valve||Canada-spec. MPI. [[w:Jaguar V12 engine|Jaguar V12]]. Jaguar XJ-S ('82-'87), XJ12 (Canada only: '85-'87).
|-
| 0 || 4.0L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. Continuously variable intake valve timing. Dual-canister evaporative emissions system. Enhanced evaporative emissions control system. [[w:Jaguar AJ-V8 engine#4.0 L|Jaguar AJ-V8 - AJ27 V8 engine]]. Jaguar XJ8 ('99), XK8 ('99).
|}

===Transmission &amp; Steering Location (Position 8):===
* 4 = Automatic / LHD
* 8 = Manual / LHD ('93-'94 XJS 4.0 w/ optional 5-spd. manual)

===Check Digit/Gearbox (Position 9)===
* USA /Canada [[Vehicle Identification Numbers (VIN codes)/Check digit|Check digit]]

===Model Year Code (Position 10)===
''See: [[Vehicle Identification Numbers (VIN codes)/Model year]]''

===Plant Codes (Position 11)===
* C - Browns Lane plant, Coventry, West Midlands, England, UK

===Positions 12–17, Serial Number===
** 100001 and after - XJ-S/XJ-SC/XJS/XJR-S (XJ27)
** 300001 and after - XJ-series sedan Series III
** 500001 and after - XJ-series sedan (XJ40/XJ81)
** 720001 and after - XJ-series sedan (X300/X305/X306/X330)
** 810001 and after - XJ-series sedan (X308)
** 001001 and after - XK8 (X100)</text>
      <sha1>gsz134055y8vqwpde53n4eoq0m8xin1</sha1>
    </revision>
    <revision>
      <id>4675745</id>
      <parentid>4675726</parentid>
      <timestamp>2026-10-12T15:12:41Z</timestamp>
      <contributor>
        <username>JustTheFacts33</username>
        <id>3434282</id>
      </contributor>
      <comment>/* General Template for Jaguar's VIN format (All models: 2000-2015 plus F-Type '16-'17, XJ '16-'19) */</comment>
      <origin>4675745</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="35057" sha1="jong7tzzwt6vae2kl32u2fzb9qiiim1" xml:space="preserve">{{Vehicle Identification Numbers (VIN codes)/Warning}}{{clear}}

This VIN number decoding and designation system is used primarily for the North American Market. European and Asian markets use other decoding and designation systems.

==General Template for Jaguar's VIN format (All models: 2016- EXCEPT F-Type '16-'17, XJ '16-'19)==

===Jaguar WMIs (2016-) (Position 1-3)===

* SAJ - Jaguar passenger car (UK)
* SAD - Jaguar SUV (UK &amp; Europe)
* L2C - Chery Jaguar Land Rover (China)

===Model Line (Position 4)===

{| class=&quot;wikitable&quot;
|+Position 4
!VIN code
!Description
|-
|A
|[[w:Jaguar XE|Jaguar XE]] ('17-'20)
|-
|B
|[[w:Jaguar XF (X260)|Jaguar XF]] ('16-'24)
|-
|C
|[[w:Jaguar F-Pace|Jaguar F-Pace]] ('17-'26)
|-
|D
|[[w:Jaguar F-Type|Jaguar F-Type]] ('18-'24)
|-
|E
|[[w:Jaguar Type 01|Jaguar Type 01]] ('28-)
|-
|F
|[[w:Jaguar E-Pace|Jaguar E-Pace]] ('18-'24)
|-
|H
|[[w:Jaguar I-Pace|Jaguar I-Pace EV]] ('19-'24)
|}

===Body Style (Position 6):===
* 1 = Coupe (F-Type coupe)
* 2 = 5-door wagon (XF Sportbrake wagon)
* 2 = 5-door (E-Pace, F-Pace, I-Pace EV)
* 4 = 4-door sedan (XE, XF sedan, Type 01)
* 5 = Convertible (F-Type convertible)

===Transmission (Position 7) 2016-2017:===
* B = Automatic (XE '17, XF '16-'17, F-Pace '17)

===Check Digit/Gearbox (Position 9)===
* USA /Canada [[Vehicle Identification Numbers (VIN codes)/Check digit|Check digit]]

===Model Year Code (Position 10)===
''See: [[Vehicle Identification Numbers (VIN codes)/Model year]]''

===Plant Codes (Position 11) 2016-===
* A - Solihull, West Midlands, England, UK (XE '17, F-Pace '17-'26, Type 01 '28-)
* C - Castle Bromwich, West Midlands, England, UK (XE '17-'20, XF '16-'24, F-Type '18-'24)
* S - Oxford Road plant, Ryton, West Midlands, England, UK (JLR SVO plant) (XE SV Project 8 '19)
* 1 - Graz, Austria (Magna Steyr plant) (E-Pace '18-'24, I-Pace EV '19-'24)

===Model (Position 12)===
* 9 - XE ('17) [Solihull plant]
* P - XE ('17-'20) [Castle Bromwich plant]
* Y - XF ('16-'24)
* K - F-Type ('18-'24)
* Z - E-Pace ('18-'20)
* 0 - E-Pace ('20-'24)
* F - I-Pace EV ('19-'20)
* 6 - I-Pace EV ('20-'24)

'''Positions 13–17, Serial Number'''

==General Template for Jaguar's VIN format (All models: 2000-2015 plus F-Type '16-'17, XJ '16-'19)==

===Jaguar WMIs (2000-) (Position 1-3)===

* SAJ - Jaguar passenger car (UK)
* SAD - Jaguar SUV (UK &amp; Europe)

===Regional Spec/Restraint System (Position 4):===
* J = Manual seat belts, Dual front airbags (US: XK8 '00)
* B = Manual seat belts, Dual front airbags (Canada: XK8 '00)
* D = Manual seat belts, Depowered Dual front airbags, &amp; Front Side Airbags (US: S-Type '00-'02, XJ8/XJR '00-'03, XK8/XKR '01-'06, XK/XKR Early '07)
* F = Manual seat belts, Depowered Dual front airbags, &amp; Front Side Airbags (Canada: S-Type '00-'02, XJ8/XJR '00-'03, XK8/XKR '01-'06, XK/XKR Early '07)
* E = Manual seat belts, Depowered Dual front airbags w/occupant position sensing, &amp; Front Side Airbags &amp; Side Curtain Airbags (US: X-Type '02-'04, S-Type '03-'04, XJ8/XJR Early '04)
* G = Manual seat belts, Depowered Dual front airbags w/occupant position sensing, &amp; Front Side Airbags &amp; Side Curtain Airbags (Canada: X-Type '02-'04,&lt;br&gt; S-Type '03-'04, XJ8/XJR Early '04)
* W = Manual seat belts, Depowered Dual front airbags w/occupant position (driver) and weight (fr. psgr.) sensing, &amp; Front Side Airbags &amp; Side Curtain Airbags &lt;br&gt; (US: X-Type '05-'08, S-Type '05-'08, XF '09-'15,  XJ8/XJR '04-'09, XJ '10-)
* X = Manual seat belts, Depowered Dual front airbags w/occupant position (driver) and weight (fr. psgr.) sensing, &amp; Front Side Airbags &amp; Side Curtain Airbags (Canada: X-Type '05-'08, S-Type '05-'08, XF '09-'15, XJ8/XJR '04-'09, XJ '10-)
* W = Manual seat belts, Depowered Dual front airbags w/occupant position (driver) and weight (fr. psgr.) sensing, &amp; Front Side Head/Thorax Airbags &lt;br&gt; (US: XK/XKR '07-'15, F-Type '14-)
* X = Manual seat belts, Depowered Dual front airbags w/occupant position (driver) and weight (fr. psgr.) sensing, &amp; Front Side Head/Thorax Airbags &lt;br&gt; (Canada: XK/XKR '07-'15, F-Type '14-)

===Transmission &amp; Steering Location (Position 5 - '00-'12):===
* A = Automatic / LHD
* B = Manual / LHD (X-Type '02-'05, S-Type 3.0 '03-'04)

===Transmission &amp; Drive Wheels (Position 5 - '13-):===
* A = Automatic / Rwd (XF '13-'15, XJ '13-'19, XK '13-'15, F-Type '14-'17)
* B = Manual / Rwd (F-Type '16-'17)
* J = Automatic / Awd (XF Awd '13-'15, XJ Awd '13-'19, F-Type Awd '16-'17)

===Model Line (Position 6-7)===

{| class=&quot;wikitable&quot;
|+Position 6-7
!VIN code
!Description
|-
|51
|[[w:Jaguar X-Type|Jaguar X-Type sedan - High Series]] ('02-'08)
|-
|52
|[[w:Jaguar X-Type|Jaguar X-Type sedan - Entry Series]] ('03-'04)
|-
|53
|[[w:Jaguar X-Type|Jaguar X-Type sedan w/Sport Package]] ('02-'03)
|-
|54
|[[w:Jaguar X-Type|Jaguar X-Type Sportwagon]] ('05-'08)
|-
|01
|[[w:Jaguar S-Type (1999)|Jaguar S-Type]] ('00-'08)
|-
|03
|[[w:Jaguar S-Type (1999)|Jaguar S-Type Sport]] [3.0, 4.0] ('02)
|-
|03
|[[w:Jaguar S-Type (1999)|Jaguar S-Type Sport]] [3.0, 4.2] ('03)
|-
|03
|[[w:Jaguar S-Type (1999)|Jaguar S-Type R]] ('03-'08)
|-
|05
|[[w:Jaguar XF (X250)|Jaguar XF Luxury]] ('09)
|-
|06
|[[w:Jaguar XF (X250)|Jaguar XF Premium Luxury]] ('09)
|-
|07
|[[w:Jaguar XF (X250)|Jaguar XF Supercharged]] ('09)
|-
|0E
|[[w:Jaguar XF (X250)|Jaguar XF]] ('13-'14)
|-
|0F
|[[w:Jaguar XF (X250)|Jaguar XF]] ('10-'12)
|-
|0F
|[[w:Jaguar XF (X250)|Jaguar XF 2.0T Premium]] [8th pos. of VIN is S] ('15)
|-
|0F
|[[w:Jaguar XF (X250)|Jaguar XF 3.0 Sport Rwd or 3.0 Portfolio Rwd]] [8th pos. of VIN is 7] ('15)
|-
|0F
|[[w:Jaguar XF (X250)|Jaguar XF 3.0 Sport Awd or 3.0 Portfolio Awd]] [8th pos. of VIN is F] ('15)
|-
|0G
|[[w:Jaguar XF (X250)|Jaguar XF Premium]] ('10-'11)
|-
|0H
|[[w:Jaguar XF (X250)|Jaguar XF Portfolio]] [8th pos. of VIN is B] ('12)
|-
|0H
|[[w:Jaguar XF (X250)|Jaguar XF Supercharged]] [8th pos. of VIN is E: '10-'13 or P: '13-'15]
|-
|0J
|[[w:Jaguar XF (X250)|Jaguar XFR]] ('10-'15)
|-
|0K
|[[w:Jaguar XF (X250)|Jaguar XFR-S]] ('13-'15)
|-
|8J
|[[w:Jaguar XF (X250)|Jaguar XFR w/Speed Pack]] ('13-'15)
|-
|12
|[[w:Jaguar XJ (X308)#Sport|Jaguar XJ Sport]] ('02-'03)
|-
|14
|[[w:Jaguar XJ (X308)|Jaguar XJ8]] ('00-'03)
|-
|15
|[[w:Jaguar XJ (X308)#XJR|Jaguar XJR]] ('00-'03)
|-
|23
|[[w:Jaguar XJ (X308)|Jaguar XJ8L]] (LWB) ('00-'01)
|-
|24
|[[w:Jaguar XJ (X308)#Daimler/Vanden Plas|Jaguar XJ8 Vanden Plas]] (LWB) ('00-'03)
|-
|25
|[[w:Jaguar XJ (X308)#Daimler/Vanden Plas|Jaguar XJ8 Vanden Plas Supercharged]] (LWB) ('00-'01)
|-
|25
|[[w:Jaguar XJ (X308)#Daimler/Vanden Plas|Jaguar XJ Super V8]] (LWB) ('02-'03)
|-
|71
|[[w:Jaguar XJ (X350)|Jaguar XJ8]] ('04-'09)
|-
|73
|[[w:Jaguar XJ (X350)|Jaguar XJR]] ('04-'09)
|-
|74
|[[w:Jaguar XJ (X350)|Jaguar XJ8 Vanden Plas]] (SWB) ('04)
|-
|79
|[[w:Jaguar XJ (X350)|Jaguar XJ8L]] (LWB) ('05-'09)
|-
|82
|[[w:Jaguar XJ (X350)|Jaguar XJ8 Vanden Plas]] (LWB) ('05-'09)
|-
|82
|[[w:Jaguar XJ (X350)|Jaguar XJ Super V8]] (LWB, 5-psgr.) ('05-'09)
|-
|86
|[[w:Jaguar XJ (X350)|Jaguar XJ Super V8 Portfolio]] (LWB, 4-psgr.) ('06)
|-
|94
|[[w:Jaguar XJ (X350)|Jaguar XJ Super V8 Portfolio]] (LWB, 5-psgr.) ('09)
|-
|1C
|[[w:Jaguar XJ (X351)|Jaguar XJ]] ('10-'15)
|-
|1C
|[[w:Jaguar XJ (X351)|Jaguar XJ R-Sport]] [8th pos. of VIN is 7 (Rwd) or D (Awd)] ('16-'19)
|-
|1C
|[[w:Jaguar XJ (X351)|Jaguar XJ Supercharged]] [8th pos. of VIN is E] ('16-'19)
|-
|1E
|[[w:Jaguar XJ (X351)|Jaguar XJR]] ('14-'17)
|-
|1G
|[[w:Jaguar XJ (X351)|Jaguar XJ Supercharged]] [8th pos. of VIN is E: '10-'13 or T: '13-'15]
|-
|1J
|[[w:Jaguar XJ (X351)|Jaguar XJ Supersport]] ('11-'12)
|-
|2E
|[[w:Jaguar XJ (X351)|Jaguar XJR LWB]] ('14-'17), XJR575 LWB ('18-'19)
|-
|2G
|[[w:Jaguar XJ (X351)|Jaguar XJL]] [8th pos. of VIN is B] ('10-'11)
|-
|2G
|[[w:Jaguar XJ (X351)|Jaguar XJL Portfolio Rwd]] [8th pos. of VIN is B: '12-'13 or 1: '13]
|-
|2G
|[[w:Jaguar XJ (X351)|Jaguar XJL Portfolio Rwd]] [8th pos. of VIN is Z: '14-'15)
|-
|2G
|[[w:Jaguar XJ (X351)|Jaguar XJL Portfolio Rwd]] [8th pos. of VIN is 7: '16-'19), XJ50 3.0 Rwd (LWB) '19
|-
|2G
|[[w:Jaguar XJ (X351)|Jaguar XJL Portfolio Awd]] [8th pos. of VIN is D] ('13-'19), XJ50 3.0 Awd (LWB) '19
|-
|2G
|[[w:Jaguar XJ (X351)|Jaguar XJL Supercharged]] [8th pos. of VIN is E: '10-'13, '16-'19 or T: '13-'15], XJ50 5.0 Rwd (LWB) '19, XJ Collection (LWB) '19
|-
|2J
|[[w:Jaguar XJ (X351)|Jaguar XJL Supersport]] ('11-'13)
|-
|2K
|[[w:Jaguar XJ (X351)|Jaguar XJL Ultimate]] ('13)
|-
|3F
|[[w:Jaguar XJ (X351)|Jaguar XJ Supersport w/Speed Pack]] ('12-'13)
|-
|3G
|[[w:Jaguar XJ (X351)|Jaguar XJL Supersport w/Speed Pack]] ('12-'13)
|-
|3H
|[[w:Jaguar XJ (X351)|Jaguar XJ Supercharged w/Sport &amp; Speed Pack]] ('12-'15)
|-
|3K
|[[w:Jaguar XJ (X351)|Jaguar XJL Supercharged w/Sport &amp; Speed Pack]] ('12-'15)
|-
|41
|[[w:Jaguar XK (X100)|Jaguar XK8/XKR coupe]] ('00-'06)
|-
|42
|[[w:Jaguar XK (X100)|Jaguar XK8/XKR convertible]] ('00-'06)
|-
|43
|[[w:Jaguar XK (X150)|Jaguar XK/XKR coupe]] ('07-'09)
|-
|44
|[[w:Jaguar XK (X150)|Jaguar XK/XKR convertible]] ('07-'09)
|-
|45
|[[w:Jaguar XK (X150)|Jaguar XKR Portfolio Edition coupe]] ('09)
|-
|46
|[[w:Jaguar XK (X150)|Jaguar XKR Portfolio Edition convertible]] ('09)
|-
|4D
|[[w:Jaguar XK (X150)|Jaguar XK Touring coupe]] [8th pos. of VIN is B] ('13-'14)
|-
|4E
|[[w:Jaguar XK (X150)|Jaguar XK Touring convertible]] [8th pos. of VIN is B] ('13-'14)
|-
|4D
|[[w:Jaguar XK (X150)|Jaguar XKR coupe]] [8th pos. of VIN is C] ('10-'15)
|-
|4E
|[[w:Jaguar XK (X150)|Jaguar XKR convertible]] [8th pos. of VIN is C] ('10-'15)
|-
|4F
|[[w:Jaguar XK (X150)|Jaguar XK coupe]] (most Portfolio Edition features are std.) [8th pos. of VIN is B] ('10-'15)
|-
|4F
|[[w:Jaguar XK (X150)|Jaguar XKR175 coupe]] [8th pos. of VIN is C] ('11)
|-
|4F
|[[w:Jaguar XK (X150)|Jaguar XKR coupe w/Dynamic Pack]] [8th pos. of VIN is C] ('13-'15), XK Final Fifty Edition coupe ('15)
|-
|4G
|[[w:Jaguar XK (X150)|Jaguar XK convertible]] (most Portfolio Edition features are std.) [8th pos. of VIN is B] ('10-'15)
|-
|4G
|[[w:Jaguar XK (X150)|Jaguar XKR convertible w/Dynamic Pack]] [8th pos. of VIN is C] ('13-'15), XK Final Fifty Edition convertible ('15)
|-
|4H
|[[w:Jaguar XK (X150)|Jaguar XKR-S coupe]] ('12-'15), XKR-S GT coupe ('14)
|-
|4J
|[[w:Jaguar XK (X150)|Jaguar XKR-S convertible]] ('12-'15)
|-
|6A
|[[w:Jaguar F-Type)|Jaguar F-Type coupe]] ('15-'17), F-Type Premium coupe '17
|-
|6B
|[[w:Jaguar F-Type)|Jaguar F-Type S coupe]] ('15-'17), F-Type S British Design Edition coupe '17
|-
|6D
|[[w:Jaguar F-Type)|Jaguar F-Type R coupe]] ('15-'17)
|-
|6E
|[[w:Jaguar F-Type)|Jaguar F-Type convertible]] ('14-'17), F-Type Premium convertible '17
|-
|6F
|[[w:Jaguar F-Type)|Jaguar F-Type S convertible]] ('14-'17), F-Type S British Design Edition convertible '17
|-
|6G
|[[w:Jaguar F-Type)|Jaguar F-Type V8 S convertible]] ('14-'15)
|-
|6H
|[[w:Jaguar F-Type)|Jaguar F-Type R convertible]] ('16-'17)
|-
|6J
|[[w:Jaguar F-Type)|Jaguar F-Type SVR coupe]] ('17)
|-
|6K
|[[w:Jaguar F-Type)|Jaguar F-Type SVR convertible]] ('17)
|-
|7A
|[[w:Jaguar F-Type#Project 7)|Jaguar F-Type Project 7 convertible]] ('16)
|}

===Engine/Emissions Control System (Position 8)===

{| class=&quot;wikitable&quot;
|+Position 8
! VIN !! Size !! Type !! Fuel !! Valvetrain !! Engine Family/Notes/Applications
|-
| A || 3.0L || 60° V6 || Gas ||DOHC,&lt;br /&gt; 24 valve||MPI. ULEV. Variable intake valve timing. [[w:Jaguar AJ-V6 engine#AJ30|Jaguar AJ-V6 - AJ30 V6 engine]].&lt;br&gt; Jaguar X-Type 3.0 (Mid '05-'08), S-Type 3.0 ('06-'08). 
|-
| A || 4.2L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. ULEV. Continuously variable intake valve timing. [[w:Jaguar AJ-V8 engine#4.2 L|Jaguar AJ-V8 - AJ34 V8 engine]]. Jaguar XF ('10).
|-
| A || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; 550 PS/542 hp. Jaguar XKR-S ('12-'15), XKR-S GT ('14), F-Type R coupe ('15).
|-
| B || 4.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. [[w:Jaguar AJ-V8 engine#Supercharged|Jaguar AJ-V8 - AJ27S V8 engine]].&lt;br&gt; Jaguar XJR ('00-'03), Vanden Plas Supercharged ('00-'01), Super V8 ('02-'03), XKR ('00-'02).
|-
| B || 4.2L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. [[w:Jaguar AJ-V8 engine#Supercharged_2|Jaguar AJ-V8 - AJ33S V8 engine]]. Jaguar XJR ('04-'05), Super V8 ('05), XKR ('03-'06).
|-
| B || 4.2L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. ULEV. Continuously variable intake valve timing. [[w:Jaguar AJ-V8 engine#4.2 L|Jaguar AJ-V8 - AJ34 V8 engine]].&lt;br&gt; Jaguar S-Type ('06-'08), XF ('09), XJ8/Vanden Plas ('06-'09), XK ('07-'09).
|-
| B || 5.0L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. Variable intake valve lift. Variable intake.&lt;br&gt; [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; Jaguar XF ('10-'12), XJ ('11-'12), XJL ('11), XJL Portfolio Rwd ('12-'13), XK ('10-'15), XK Touring ('13-'14).
|-
| C || 3.0L || 60° V6 || Gas ||DOHC,&lt;br /&gt; 24 valve||MPI. Variable intake valve timing. [[w:Jaguar AJ-V6 engine#AJ30|Jaguar AJ-V6 - AJ30 V6 engine]].&lt;br&gt; Jaguar S-Type 3.0 ('00-'01), X-Type 3.0 ('02-Mid '05). 
|-
| C || 4.0L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. Continuously variable intake valve timing. [[w:Jaguar AJ-V8 engine#4.0 L|Jaguar AJ-V8 - AJ27 V8 engine]].&lt;br&gt; Jaguar XJ8/Vanden Plas ('00-'03), XJ Sport ('02-'03), XK8 ('00-'02).
|-
| C || 4.2L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. Continuously variable intake valve timing. [[w:Jaguar AJ-V8 engine#4.2 L|Jaguar AJ-V8 - AJ33 V8 engine]]. Jaguar XJ8 ('04-'05), XK8 ('03-'06).
|-
| C || 4.2L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. ULEV. Continuously variable intake valve timing. [[w:Jaguar AJ-V8 engine#Supercharged_2|Jaguar AJ-V8 - AJ34S V8 engine]].&lt;br&gt; Jaguar S-Type R ('06-'08), XF Supercharged ('09), XJR ('06-'09), Super V8 ('06-'09), XKR ('07-'09).
|-
| C || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; 510 PS/503 hp. Jaguar XFR ('10-'13), XJ/XJL Supersport ('11-'13), XKR ('10-'15).
|-
| C || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 380 PS/375 hp. Jaguar F-Type S ('14-'15), F-Type S w/man. trans. ('16-'17).
|-
| D || 4.0L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. Continuously variable intake valve timing. [[w:Jaguar AJ-V8 engine#4.0 L|Jaguar AJ-V8 - AJ28 V8 engine]]. Jaguar S-Type 4.0 ('00-'01).
|-
| D || 2.5L || 60° V6 || Gas ||DOHC,&lt;br /&gt; 24 valve||MPI. Variable intake valve timing. [[w:Jaguar AJ-V6 engine#AJ25|Jaguar AJ-V6 - AJ25 V6 engine]]. Jaguar X-Type 2.5 ('02-'05).
|-
| D || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar XJ Awd, XJL Portfolio Awd ('13-'15).
|-
| D || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. SULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar XJ R-Sport Awd, XJL Portfolio Awd ('16-'19), XJ50 3.0 Awd ('19).
|-
| E || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; 470 PS/464 hp.&lt;br&gt; Jaguar XF Supercharged ('10-'13), XJ/XJL Supercharged ('11-'13, '16-'19), XJ50 5.0 Rwd ('19), XJ Collection ('19).
|-
| F || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar XF 3.0 Awd ('13-'14).
|-
| F || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. SULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar XF 3.0 Awd ('15).
|-
| H || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas/E85 ||DOHC,&lt;br /&gt; 32 valve||Flex Fuel. Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]]. 510 PS/503 hp. Jaguar XFR ('13-'15).
|-
| K || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; 550 PS/542 hp. Jaguar XJR/XJR LWB ('14-'17).
|-
| K || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; 575 PS/567 hp. Jaguar XJR575 LWB ('18-'19).
|-
| L || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; 495 PS/488 hp. Jaguar F-Type V8 S convertible ('14-'15).
|-
| L || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; 550 PS/542 hp. Jaguar F-Type R  ('16-'17).
|-
| N || 3.0L || 60° V6 || Gas ||DOHC,&lt;br /&gt; 24 valve||MPI. Variable intake valve timing. [[w:Jaguar AJ-V6 engine#AJ30|Jaguar AJ-V6 - AJ30 V6 engine]]. Jaguar S-Type 3.0 ('01-'02).
|-
| P || 4.0L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. Continuously variable intake valve timing. [[w:Jaguar AJ-V8 engine#4.0 L|Jaguar AJ-V8 - AJ28 V8 engine]]. Jaguar S-Type 4.0 ('01-'02).
|-
| P || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas/E85 ||DOHC,&lt;br /&gt; 32 valve||Flex Fuel. Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]]. 470 PS/464 hp. Jaguar XF Supercharged ('13-'15).
|-
| S || 2.0L || I4 Turbo [[w:Intercooler|IC]] || Gas || DOHC,&lt;br /&gt; 16 valve||Direct Injection. Dual VVT. Ford EcoBoost engine (Mazda L engine-based).&lt;br&gt; Jaguar XF 2.0T ('13-'14), XF 2.0T Premium ('15).
|-
| T || 3.0L || 60° V6 || Gas ||DOHC,&lt;br /&gt; 24 valve||MPI. Variable intake valve timing. [[w:Jaguar AJ-V6 engine#AJ30|Jaguar AJ-V6 - AJ30 V6 engine]]. Jaguar S-Type 3.0 ('03-'05).
|-
| T || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas/E85 ||DOHC,&lt;br /&gt; 32 valve||Flex Fuel. Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]]. 470 PS/464 hp. Jaguar XJ/XJL Supercharged ('13-'15).
|-
| T || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. SULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar F-Type w/auto. trans. ('15-'17), F-Type Premium w/auto. trans. ('17).
|-
| U || 4.2L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. Continuously variable intake valve timing. [[w:Jaguar AJ-V8 engine#4.2 L|Jaguar AJ-V8 - AJ33 V8 engine]]. Jaguar S-Type 4.2 ('03-'05).
|-
| U || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. SULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 380 PS/375 hp. Jaguar F-Type S ('15), F-Type S Rwd w/auto. trans. ('16-'17).
|-
| V || 4.2L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. [[w:Jaguar AJ-V8 engine#Supercharged_2|Jaguar AJ-V8 - AJ33S V8 engine]]. Jaguar S-Type R ('03-'05).
|-
| V || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. SULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 380 PS/375 hp. Jaguar F-Type S Awd w/auto. trans. ('16-'17).
|-
| X || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas/E85 ||DOHC,&lt;br /&gt; 24 valve||Flex Fuel. Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar XF 3.0 Rwd ('14).
|-
| Z || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; 550 PS/542 hp. Jaguar XFR-S ('13-'15).
|-
| Z || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas/E85 ||DOHC,&lt;br /&gt; 24 valve||Flex Fuel. Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar XJ Rwd, XJL Portfolio Rwd ('14-'15).
|-
| 1 || 5.0L || V8 || Gas/E85 ||DOHC,&lt;br /&gt; 32 valve||Flex Fuel. Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. Variable intake valve lift. Variable intake. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]]. Jaguar XJL Portfolio Rwd ('13).
|-
| 6 || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. SULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar F-Type w/man. trans. ('16-'17), F-Type Premium w/man. trans. ('17).
|-
| 7 || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar XF 3.0 Rwd ('13), XJ Rwd ('13), F-Type ('14-'15).
|-
| 7 || 3.0L || 90° V6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||Direct Injection. SULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#V6|Jaguar AJ126 V6 engine]].&lt;br&gt; 340 PS/335 hp. Jaguar XF 3.0 Rwd ('15), XJ R-Sport Rwd ('16-'19), XJL Portfolio Rwd ('16-'19), XJ50 3.0 Rwd ('19).
|-
| 8 || 5.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||Direct Injection. ULEV. Continuously variable intake &amp; exhaust valve timing. [[w:Jaguar AJ-V8 engine#AJ-V8 Gen III 5.0|Jaguar AJ-V8 - AJ133 V8 engine]].&lt;br&gt; 575 PS/567 hp. Jaguar F-Type Project 7 ('16), F-Type SVR ('17).
|}

===Check Digit/Gearbox (Position 9)===
* USA /Canada [[Vehicle Identification Numbers (VIN codes)/Check digit|Check digit]]

===Model Year Code (Position 10)===
''See: [[Vehicle Identification Numbers (VIN codes)/Model year]]''

===Plant Code/Model Line/Engine (Position 11) 2000-2019===
* X - Halewood, Merseyside, England, UK - X-Type 2.5 ('02-'05)
* W - Halewood, Merseyside, England, UK - X-Type 3.0 ('02-'08)
* F - Castle Bromwich, West Midlands, England, UK - S-Type 3.0 ('00-'08)
* G - Castle Bromwich, West Midlands, England, UK - S-Type 4.0 ('00-'02)
* H - Castle Bromwich, West Midlands, England, UK - S-Type 4.2 ('03-'08)
* 1 - Castle Bromwich, West Midlands, England, UK - S-Type R (4.2 supercharged) ('03-'08)
* H - Castle Bromwich, West Midlands, England, UK - XF 4.2 ('09-'10)
* 1 - Castle Bromwich, West Midlands, England, UK - XF Supercharged (4.2 supercharged) ('09)
* L - Castle Bromwich, West Midlands, England, UK - XF 5.0 ('10-'12)
* M - Castle Bromwich, West Midlands, England, UK - XF Supercharged, XFR (5.0 supercharged) ('10-'15), XFR-S (5.0 supercharged) ('13-'15)
* P - Castle Bromwich, West Midlands, England, UK - XF 2.0T ('13-'15)
* 8 - Castle Bromwich, West Midlands, England, UK - XF 3.0 supercharged ('13-'15)
* L - Browns Lane plant, Coventry, West Midlands, England, UK - XJ8 (4.0) ('00-'03), XJ8L (4.0) ('00-'01), XJ8 Vanden Plas (4.0) ('00-'03), XJ Sport (4.0) ('02-'03)
* M - Browns Lane plant, Coventry, West Midlands, England, UK - XJ8 Vanden Plas Supercharged (4.0 supercharged) ('00-'01),&lt;br&gt; Super V8 (4.0 supercharged) ('02-'03), XJR (4.0 supercharged) ('00-'03)
* S - Browns Lane plant, Coventry, West Midlands, England, UK - XJ8 (4.2) ('04-'06), XJ8L (4.2) ('05-'06), XJ8 Vanden Plas (4.0) ('04-'06)
* T - Browns Lane plant, Coventry, West Midlands, England, UK - Super V8 (4.2 supercharged) ('05-'06), Super V8 Portfolio (4.2 supercharged) ('06),&lt;br&gt; XJR (4.2 supercharged) ('04-'06)
* S - Castle Bromwich, West Midlands, England, UK - XJ8 (4.2) ('07-'09), XJ8L (4.2) ('07-'09), XJ8 Vanden Plas (4.0) ('07-'09)
* T - Castle Bromwich, West Midlands, England, UK - Super V8 (4.2 supercharged) ('07-'09), Super V8 Portfolio (4.2 supercharged) ('09),&lt;br&gt; XJR (4.2 supercharged) ('07-'09)
* L - Castle Bromwich, West Midlands, England, UK - XJ (5.0) ('10-'12), XJL (5.0) ('10-'11), XJL Portfolio (5.0) ('12-'13)
* M - Castle Bromwich, West Midlands, England, UK - XJ/XJL Supercharged (5.0 supercharged) ('10-'19), XJ/XJL Supersport (5.0 supercharged) ('11-'13),&lt;br&gt; XJL Ultimate (5.0 supercharged) ('13), XJR SWB/LWB (5.0 supercharged) ('14-'17), XJR575 LWB (5.0 supercharged) ('18-'19), XJ50 LWB (5.0 supercharged) ('19), XJ Collection Sp. Ed. LWB (5.0 supercharged) ('19)
* 8 - Castle Bromwich, West Midlands, England, UK - XJ base (3.0 supercharged) ('13-'15), XJ R-Sport (3.0 supercharged) ('16-'19),&lt;br&gt; XJL Portfolio AWD (3.0 supercharged) ('13-'19), XJL Portfolio RWD (3.0 supercharged) ('14-'19), XJ50 LWB (3.0 supercharged) ('19)
* N - Browns Lane plant, Coventry, West Midlands, England, UK - XK8 (4.0) ('00-'02)
* P - Browns Lane plant, Coventry, West Midlands, England, UK - XKR (4.0 supercharged) ('00-'02)
* 2 - Browns Lane plant, Coventry, West Midlands, England, UK - XK8 (4.2) ('03-'06)
* 3 - Browns Lane plant, Coventry, West Midlands, England, UK - XKR (4.2 supercharged) ('03-'06)
* 5 - Castle Bromwich, West Midlands, England, UK - XK (4.2) ('07-'09)
* 9 - Castle Bromwich, West Midlands, England, UK - XKR (4.2 supercharged) ('07-'09)
* L - Castle Bromwich, West Midlands, England, UK - XK (5.0) ('10-'15)
* M - Castle Bromwich, West Midlands, England, UK - XKR (5.0 supercharged) ('10-'15), XKR-S (5.0 supercharged) ('12-'15), XKR-S GT (5.0 supercharged) ('14)
* 8 - Castle Bromwich, West Midlands, England, UK - F-Type Base, S (3.0 supercharged) ('14-'17), F-Type Premium (3.0 supercharged) ('17)
* M - Castle Bromwich, West Midlands, England, UK - F-Type V8S (5.0 supercharged) ('14-'15), F-Type R (5.0 supercharged) ('15-'17),&lt;br&gt; F-Type Project 7 (5.0 supercharged) ('16), F-Type SVR (5.0 supercharged) ('17)

===Model (Position 12)===
* C - X-Type ('02-'03)
* D - X-Type ('03-'04)
* E - X-Type ('04-'06)
* J - X-Type ('06-'08)
* L - S-Type ('00-'01)
* M - S-Type ('01-'04)
* N - S-Type ('04-'08)
* R - XF ('09-'11)
* S - XF ('11-'13)
* U - XF ('13-'15)
* F - XJ ('00-'03)
* G - XJ ('04-'06) [Browns Lane plant]
* H - XJ ('06-'09) [Castle Bromwich plant]
* V - XJ ('10-'16)
* W - XJ ('16-'19)
* A - XK ('00-'06)
* B - XK ('07-'15)
* K - F-Type ('14-'17)

'''Positions 13–17, Serial Number'''

==General Template for Jaguar's VIN format (1981 - 1999)==

===Jaguar WMIs (1981-1999) (Position 1-3)===
* SAJ - Jaguar passenger car

===Model Line (Position 4)===

{| class=&quot;wikitable&quot;
|+Position 4
!VIN code
!Description
|-
|A
|[[w:Jaguar XJ#Series 3 (1979–1992)|Jaguar XJ6]] ('81-'87), XJ6 Vanden Plas ('82-'87)
|-
|B
|[[w:Jaguar XJ#Series 3 (1979–1992)|Jaguar XJ12]] (Canada only: '81-'88)
|-
|D
|[[w:Jaguar XJ#Series 3 (1979–1992)|Jaguar XJ12]] (Canada only: '89-'92)
|-
|H
|[[w:Jaguar XJ (XJ40)|Jaguar XJ6]] ('88-'89, '93-'94)
|-
|F
|[[w:Jaguar XJ (XJ40)|Jaguar XJ6]] ('90-'92)
|-
|H
|[[w:Jaguar XJ (XJ40)|Jaguar XJ6 Sovereign]] ('90-'92)
|-
|K
|[[w:Jaguar XJ (XJ40)#Daimler/Vanden Plas|Jaguar XJ6 Vanden Plas]] ('88-'94)
|-
|M
|[[w:Jaguar XJ (XJ40)#Majestic (1989–1992 – SWB; 1993–1994 – LWB)|Jaguar XJ6 Vanden Plas Majestic]] ('89-'90, '92)
|-
|M
|[[w:Jaguar XJ (XJ40)#XJ12 and Daimler Double Six (XJ81)|Jaguar XJ12]] ('94)
|-
|H
|[[w:Jaguar XJ (X300)|Jaguar XJ6]] ('95-'97)
|-
|H
|[[w:Jaguar XJ (X300)|Jaguar XJ6L]] LWB [X330] ('97)
|-
|K
|[[w:Jaguar XJ (X300)#Daimler/Jaguar Vanden Plas|Jaguar XJ6 Vanden Plas]] SWB ('95)
|-
|K
|[[w:Jaguar XJ (X300)#Daimler/Jaguar Vanden Plas|Jaguar XJ6 Vanden Plas]] LWB [X330] ('96-'97)
|-
|M
|[[w:Jaguar XJ (X300)#XJ12 (X305)|Jaguar XJ12]] SWB ('95)
|-
|M
|[[w:Jaguar XJ (X300)#XJ12 (X305)|Jaguar XJ12]] LWB [X330] ('96)
|-
|P
|[[w:Jaguar XJ (X300)#XJR (X306)|Jaguar XJR]] ('95-'97)
|-
|H
|[[w:Jaguar XJ (X308)|Jaguar XJ8]] ('98-'99)
|-
|H
|[[w:Jaguar XJ (X308)|Jaguar XJ8L]] LWB ('98-'99)
|-
|K
|[[w:Jaguar XJ (X308)#Daimler/Vanden Plas|Jaguar XJ8 Vanden Plas]] LWB ('98-'99)
|-
|P
|[[w:Jaguar XJ (X308)#XJR|Jaguar XJR]] ('98-'99)
|-
|N
|[[w:Jaguar XJS|Jaguar XJ-S]] ('82-'91), XJ-SC ('86-'88), XJS ('92-'96)
|-
|T
|[[w:Jaguar XJS|Jaguar XJ-S]] Rouge Collection ('89-'90), Classic Collection ('90-'91)
|-
|S
|[[w:Jaguar XJS#XJR-S|Jaguar XJR-S]] ('93)
|-
|G
|[[w:Jaguar XK (X100)|Jaguar XK8]] ('97-'99)
|}

===Class (Regional Spec)/Restraint System (Position 5):===
* V = N. American-spec (Manual seat belts)
* L = Canadian-spec (Manual seat belts)

* Y = XJ6 Vanden Plas [Series III] ('82-'87) (Manual seat belts)

* A = Motorized Shoulder Belts (XJ-S coupe '88-'89, XJ-SC '88)
* Y = Motorized Shoulder Belts (XJ-S coupe '89, XJ sedan '89-'92)
* W = Manual seat belts, Driver-side airbag (US: XJ-S '90-'93, XJ6 '93, XJ12 Early '94)
* X = Manual seat belts, Dual front airbags (US: XJS '94-'96, XJ6 '94-'97, XJ12 '94-'96, XJR '95-'97, XK8 '97-'99)
* X = Manual seat belts, Dual front airbags, &amp; Front Side Airbags (US: XJ8/XJR '98-'99)
* D = Manual seat belts, Depowered Dual front airbags, &amp; Front Side Airbags (US: XJ8/XJR '99)
* M = Manual seat belts, Driver-side airbag (Canada)
* N = Manual seat belts, Dual front airbags (Canada)
* F = Manual seat belts, Depowered Dual front airbags, &amp; Front Side Airbags (Canada: XJ8/XJR '99)

===Body Style (Position 6):===
* 1 = 4-door sedan (XJ-series sedan '81-'99)
* 2 = 2-door convertible w/2+2 seating (XJS convertible '94-'96, XK8 convertible '97-'99)
* 3 = 2-door Cabriolet (XJ-SC '86-'88)
* 4 = 2-door convertible w/2-psgr. seating (factory-built XJS convertible '89-'94, XJR-S convertible '93)
* 5 = 2-door coupe (XJS coupe '82-'96, XJR-S coupe '93, XK8 coupe '97-'99)
* 5 = 2-door coupe (Hess &amp; Eisenhardt-built XJS convertible '87-'88) [coupe conversion]

===Engine Type (Position 7):===
{| class=&quot;wikitable&quot;
|+Position 7
|-
! VIN !! Size !! Type !! Fuel !! Valvetrain !! Engine Family/Notes/Applications
|-
| 1 || 4.0L || I6 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 24 valve||MPI. [[w:Jaguar AJ6 engine#AJ16S|Jaguar AJ16S I6]]. Jaguar XJR ('95-'97).
|-
| 2 || 4.2L || I6 || Gas ||DOHC,&lt;br /&gt; 12 valve||CA &amp; Canada-spec. MPI. [[w:Jaguar XK engine|Jaguar XK I6]]. Jaguar XJ6 ('81-'82).
|-
| 2 || 4.0L || I6 || Gas ||DOHC,&lt;br /&gt; 24 valve||MPI. Dual-canister evaporative emissions system. [[w:Jaguar AJ6 engine#AJ16|Jaguar AJ16 I6]]. Jaguar XJ6 ('96-'97).
|-
| 2 || 4.0L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. Variable intake valve timing. Dual-canister evaporative emissions system. [[w:Jaguar AJ-V8 engine#4.0 L|Jaguar AJ-V8 - AJ26 V8 engine]].&lt;br&gt; Jaguar XJ8 ('98), XK8 ('98).
|-
| 3 || 4.2L || I6 || Gas ||DOHC,&lt;br /&gt; 12 valve||N. America-spec. MPI. [[w:Jaguar XK engine|Jaguar XK I6]]. Jaguar XJ6 ('81-'87).
|-
| 3 || 6.0L || 60° V12 || Gas ||SOHC,&lt;br /&gt; 24 valve||MPI. [[w:Jaguar V12 engine|Jaguar V12]] modified by [[w:Tom Walkinshaw Racing|JaguarSport]]. Jaguar XJR-S ('93).
|-
| 3 || 6.0L || 60° V12 || Gas ||SOHC,&lt;br /&gt; 24 valve||MPI. [[w:Jaguar V12 engine|Jaguar V12]]. Jaguar XJS ('94-'95), XJ12 ('94-'96).
|-
| 5 || 3.6L || I6 || Gas ||DOHC,&lt;br /&gt; 24 valve||N. America-spec - Low Compression. MPI. [[w:Jaguar AJ6 engine|Jaguar AJ6 I6]]. Jaguar XJ6 ('88-'89).
|-
| 6 || 3.6L || I6 || Gas ||DOHC,&lt;br /&gt; 24 valve||N. America-spec - High Compression. MPI. [[w:Jaguar AJ6 engine|Jaguar AJ6 I6]]. Jaguar XJ6 ('88).
|-
| 7 || 4.0L || I6 || Gas ||DOHC,&lt;br /&gt; 24 valve||MPI. [[w:Jaguar AJ6 engine|Jaguar AJ6 I6]]. Jaguar XJ6 ('90-'94), XJS ('93-'94).
|-
| 7 || 4.0L || I6 || Gas ||DOHC,&lt;br /&gt; 24 valve||MPI. [[w:Jaguar AJ6 engine#AJ16|Jaguar AJ16 I6]]. Jaguar XJ6 ('95-'96), XJS ('95-'96).
|-
| 7 || 4.0L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. Variable intake valve timing. [[w:Jaguar AJ-V8 engine#4.0 L|Jaguar AJ-V8 - AJ26 V8 engine]]. Jaguar XK8 ('97).
|-
| 8 || 5.3L || 60° V12 || Gas ||SOHC,&lt;br /&gt; 24 valve||N. America-spec. MPI. [[w:Jaguar V12 engine|Jaguar V12]]. Jaguar XJ-S ('82-'92), XJ12 (Canada only: '88-'92).
|-
| 8 || 4.0L || V8 [[w:Supercharged|SC]] [[w:Intercooler|IC]] || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. Dual-canister evaporative emissions system. [[w:Jaguar AJ-V8 engine#Supercharged|Jaguar AJ-V8 - AJ26S V8 engine]]. Jaguar XJR ('98-'99).
|-
| 9 || 4.0L || I6 || Gas ||DOHC,&lt;br /&gt; 24 valve||Canada-spec. MPI. [[w:Jaguar AJ6 engine|Jaguar AJ6 I6]]. Jaguar XJ6 ('90-'93), XJS ('93).
|-
| 0 || 5.3L || 60° V12 || Gas ||SOHC,&lt;br /&gt; 24 valve||Canada-spec. MPI. [[w:Jaguar V12 engine|Jaguar V12]]. Jaguar XJ-S ('82-'87), XJ12 (Canada only: '85-'87).
|-
| 0 || 4.0L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||MPI. Continuously variable intake valve timing. Dual-canister evaporative emissions system. Enhanced evaporative emissions control system. [[w:Jaguar AJ-V8 engine#4.0 L|Jaguar AJ-V8 - AJ27 V8 engine]]. Jaguar XJ8 ('99), XK8 ('99).
|}

===Transmission &amp; Steering Location (Position 8):===
* 4 = Automatic / LHD
* 8 = Manual / LHD ('93-'94 XJS 4.0 w/ optional 5-spd. manual)

===Check Digit/Gearbox (Position 9)===
* USA /Canada [[Vehicle Identification Numbers (VIN codes)/Check digit|Check digit]]

===Model Year Code (Position 10)===
''See: [[Vehicle Identification Numbers (VIN codes)/Model year]]''

===Plant Codes (Position 11)===
* C - Browns Lane plant, Coventry, West Midlands, England, UK

===Positions 12–17, Serial Number===
** 100001 and after - XJ-S/XJ-SC/XJS/XJR-S (XJ27)
** 300001 and after - XJ-series sedan Series III
** 500001 and after - XJ-series sedan (XJ40/XJ81)
** 720001 and after - XJ-series sedan (X300/X305/X306/X330)
** 810001 and after - XJ-series sedan (X308)
** 001001 and after - XK8 (X100)</text>
      <sha1>jong7tzzwt6vae2kl32u2fzb9qiiim1</sha1>
    </revision>
  </page>
  <page>
    <title>Digital Synthora</title>
    <ns>0</ns>
    <id>485802</id>
    <revision>
      <id>4675740</id>
      <parentid>4673177</parentid>
      <timestamp>2026-10-12T14:20:10Z</timestamp>
      <contributor>
        <username>Kittycataclysm</username>
        <id>3371989</id>
      </contributor>
      <comment>Making [[WB:Requests for deletion|deletion request]]</comment>
      <origin>4675740</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1478" sha1="6i3pv7t1ia94kw7evjmvg3muxmv1fmo" xml:space="preserve">&lt;noinclude&gt;{{Rfd|example=false}}&lt;/noinclude&gt;
{{query|Appears to be an invention of the page creator; I can't find anything relevant online beyond the empty https://synthoraactstuff.fandom.com/.}}

''Note: Synthora is a '''conceptual language''' or a '''language concept'''. It means that this is not an officially recognized language nor a fully developed language either.''

== Table of Contents ==

=== 1. Synthora Basic ===

* [[Digital Synthora/Overview (Basic)|Overview]]
* [[Digital Synthora/Synthorentence Formation (Basic)|Synthorentence Formation]]
* [[Digital Synthora/Defrauacative Check (Basic)|Defrauacative Check]]
* [[Digital Synthora/Units of a Synthorode (Basic)|Units of a Synthorode]]
* [[Digital Synthora/Differences between Real and Digital Synthora (Basic)|Differences between Real and Digital Synthora]]

=== 2. Synthora Normal ===

* Overview
* Synthorentence Shortening
* Intermediate Units of a Synthorode 
* Old Synthora 
* Customization

=== 3. Synthora Encrypted ===

* Overview 
* Encrypting Synthorode
* Synthorentence Complicating 
* Intermediate Customization 

====== Hope You Enjoy Reading! ======

== About The Book ==

* This book is made by [[User:ActStuffOGWiki|ActStuffOGWiki]]. 
* This book is made for the sole purpose of showing '''Synthora''' to the world. 
* This book is typed '''completely from memory''' with no external sources. Therefore, I might miss some [[Wikibooks:Subject pages|pages]] or sections. 
{{shelves}} {{BookCat}}</text>
      <sha1>6i3pv7t1ia94kw7evjmvg3muxmv1fmo</sha1>
    </revision>
  </page>
  <page>
    <title>Koine Greek/Contract Verbs</title>
    <ns>0</ns>
    <id>485935</id>
    <revision>
      <id>4675759</id>
      <parentid>4673159</parentid>
      <timestamp>2026-10-12T18:43:30Z</timestamp>
      <contributor>
        <username>It-is-Truly-Meet</username>
        <id>3624460</id>
      </contributor>
      <minor />
      <origin>4675759</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2419" sha1="7mknw9j49hr8mwiddslqevfloq1luo0" xml:space="preserve">A special class of thematic verbs are the contracted verbs. In the dictionary these are entered as ending -άω, -έω, or -όω. For example, ὁράω &quot;I see&quot;, ποιέω &quot;I do&quot;, δηλόω &quot;I show&quot;; but in most cases when they are found in a text the vowel α, ε, ο (a, e, o) contracts with the ending to make a single vowel. Thus the present tense of ὁράω &quot;I see&quot; goes as follows:
::'''ὁρῶ''', ὁρᾷς, ὁρᾷ, ὁρῶμεν, ὁρᾶτε, ὁρῶσι(ν)
::I see, thou seest, he sees, we see, ye see, they see

while the present tense of ποιέω (poiéō) &quot;I do&quot; is as follows:
::'''ποιῶ''', ποιεῖς, ποιεῖ, ποιοῦμεν, ποιεῖτε, ποιοῦσι(ν) 
::I do, thou dost, he does, we do, ye do, they do

and the present tense of δηλόω &quot;I show&quot; is as follows:
::'''δηλῶ''', δηλοῖς, δηλοῖ, δηλοῦμεν, δηλοῦτε, δηλοῦσι(ν)
::I show, thou showest, he/she/it shows, we show, ye show, they show
The present infinitive active of the three types of contracted verbs is ὁρᾶν &quot;to see&quot;, ποιεῖν, &quot;to do&quot;, δηλοῦν &quot;to show&quot;.

Contracted verbs are also found in the middle and passive voices, e.g. ἀφικνέομαι/ἀφικνοῦμαι &quot;I arrive&quot; and τιμάομαι/τιμῶμαι &quot;I am honoured&quot;.

==Contraction Rules==
{| class=&quot;wikitable&quot;
! Following
! Α-stem
! Ε-stem
! Ο-stem
|-
| + ε||ᾱ||ει||ου
|-
| + ει||ᾳ||ει||οι
|-
| + η||ᾱ||η||ω
|-
| + ο||ω||ου||ου
|-
| + οι||ῳ||οι||οι
|-
| + ου||ω||ου||ου
|-
| + ω||ω||ω||ω
|}

==Common GNT Contract Verbs==
{| class=&quot;wikitable&quot;
! Α
! Ε
! Ο
|-
|ἀγαπάω: I love||ποιέω: I do, make||πληρόω: I fill, fulfill
|-
|ὁράω: I see||λαλέω: I speak||δικαιόω: I justify
|-
|ἐρωτάω: I ask||καλέω: I call||σταυρόω: I crucify
|-
|νικάω: I conquer||ζητέω: I seek||φανερόω: I reveal, manifest
|-
|τιμάω: I honor||θεωρέω: I see, observe||ἐλευθερόω: I set free
|-
|γεννάω: I beget||τηρέω: I keep, guard||ζηλόω: I am jealous
|-
|πλανάω: I lead astray||μαρτυρέω: I bear witness||ὑψόω: I exalt
|-
|πεινάω: I hunger||ἀκολουθέω: I follow||κοινόω: I make common, share
|-
|διψάω: I thirst||προσκυνέω: I worship||τελειόω: I make perfect, complete
|}

{{BookCat}}</text>
      <sha1>7mknw9j49hr8mwiddslqevfloq1luo0</sha1>
    </revision>
  </page>
  <page>
    <title>On 2D Inverse Problems/Rotation</title>
    <ns>0</ns>
    <id>485992</id>
    <revision>
      <id>4675803</id>
      <parentid>4675341</parentid>
      <timestamp>2026-10-13T08:22:04Z</timestamp>
      <contributor>
        <username>DVD206</username>
        <id>724793</id>
      </contributor>
      <minor />
      <comment>entries and blocks duality</comment>
      <origin>4675803</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="4264" sha1="2zr0gbs3rq8qd9zzeulabmj7ceddao3" xml:space="preserve">For the spiderweb the spinning spectrum could be circulant, rotation invariant:

&lt;math&gt;\det
\begin{pmatrix}
c+a &amp; -as &amp;-c/s \\
-a/s &amp; a+b &amp; -bs \\
-cs &amp; -b/s &amp; b+c
\end{pmatrix} = 
\det
\begin{pmatrix}
2d &amp; -ds &amp;-d/s \\
-d/s &amp; 2d &amp; -ds \\
-ds &amp; -d/s &amp; 2d
\end{pmatrix}.
&lt;/math&gt;

&lt;math&gt;\det(L_s)=abc(2-s^3-1/s^3)=d^3(2-s^3-1/s^3)&lt;/math&gt;

if
&lt;math&gt;abc=d^3&lt;/math&gt;.

in the smallest Spiderweb network case...
The zeros of &lt;math&gt;\det(L_s)=0&lt;/math&gt; are eigenvalues of the graph monodromy together with roots of unity symmetry rotation...
Also,
&lt;math&gt;L_s = \begin{pmatrix}
1 &amp; -s &amp; 0 \\
0 &amp; 1 &amp; -s \\
-s &amp; 0 &amp; 1
\end{pmatrix}
\begin{pmatrix}
c &amp; 0 &amp; 0 \\
0 &amp; a &amp; 0 \\
0 &amp; 0 &amp; b
\end{pmatrix}
\begin{pmatrix}
1 &amp; 0 &amp;-1/s \\
-1/s &amp; 1 &amp; 0 \\
0 &amp; -1/s &amp; 1
\end{pmatrix}.
&lt;/math&gt;

&lt;math&gt;L_s^*=L_{1/s}&lt;/math&gt; and the factorization holds

&lt;math&gt;\det(L_s)=d^3(1-s^3)(1-1/s^3)&lt;/math&gt;...

{{BookCat}}Prompt for Gemini, Meta or Copilot AIs:

A dimension reduction problem: Let &lt;math&gt; S=\begin{pmatrix}0 &amp; 1 &amp; 0 \\ 0 &amp; 0 &amp; 1 \\1 &amp; 0 &amp; 0\end{pmatrix}&lt;/math&gt; be the shift matrix and D and E two diagonal matrices. Let &lt;math&gt;L_s(D,E)=\begin{pmatrix}E &amp; -E \\-E &amp;E+(I-sS)D(I-S^T/s)\end{pmatrix}&lt;/math&gt; be the block matrix. Prove that &lt;math&gt; \det(L_s(D,E))=\det(L_s(d*I,e*I))&lt;/math&gt; and if the diagonal entries of D and E are positive then d and e &gt; 0. Or to match entries ad blocks (3 by 3 nodes case):
let &lt;math&gt; L_s=\begin{pmatrix}D_1 &amp; -D_1 &amp; 0 \\ -D_1 &amp; D_1+(I-sS)D_2(I-S^T/s)+D_3 &amp; -D_3 \\ 0 &amp; -D_3 &amp; D_3 +(I-sS)D_4(I-S^T/s)\end{pmatrix}&lt;/math&gt;. And, &lt;math&gt; \det(L_s(D_1,D_2,D_3,D_4))=\det(L_s(d_1*I,d_2*I,d_3*I,d_4*I))&lt;/math&gt;...

The answer from Germany/Gemini: Neither! Matrices structured like $L_s(D,E)$ with a cyclic shift operator $S$ typically arise in '''discrete physics models on periodic chains, lattice models in condensed matter, and localization theory''', rather than the mechanical spinning of a DVD or acoustic resonances.

Specifically, this setup is characteristic of:

=== 1. Tight-Binding Models and Periodic Lattices ===

* '''Physical context:''' Systems of quantum particles, electrons, or coupled oscillators arranged in a closed 1-dimensional ring or periodic lattice (like a crystal or polymer ring with 3 sites).
* '''Role of $S$:''' The matrix $S$ is a discrete shift (cyclic permutation) operator representing nearest-neighbor hopping around the periodic ring.
* '''Role of $D$ and $E$:''' These diagonal matrices represent site-dependent potentials, disorder strengths, or coupling parameters at each site of the lattice.

=== 2. Transfer Matrices and Duality Relations in Physics ===

* In statistical mechanics and condensed matter physics (such as studying the Anderson localization model for disordered media), block matrices of this form frequently appear when setting up '''transfer matrices'''.
* The parameter $s$ often plays the role of a complex spectral parameter or a twisted boundary condition (a Bloch-type phase factor $z = e^{i\theta}$) introduced to analyze extended versus localized states in periodic or quasi-periodic chains.

=== Why &quot;Dimension Reduction&quot;? ===
The calculation you are performing—reducing a system governed by individual, varying site parameters ($D$ and $E$) down to effective scalar parameters ($d$ and $e$) via determinants—is a technique used to find '''effective medium approximations''' or '''spectral invariants'''. It proves that the global spectral properties (like partition functions or total transmission determinants) of a disordered or inhomogeneous periodic ring can often be mapped back to an equivalent homogeneous system governed by mean scalar values ($d$ and $e$).

'''Dimension Reduction and Invariance:''' When you perform spider moves or analyze dual graphs, you often want to prove that the determinant (representing physical quantities like dimer partition functions or spectral curves) remains invariant, or that a complex system with many individual edge/face weights ($D$ and $E$) can be &quot;reduced&quot; to an effective scalar system ($d \cdot I$ and $e \cdot I$).

Whether you look at it as a repeating algebraic seed or a self-similar grid, it's the mathematical backbone of how complex, large-scale systems can be completely understood by looking at their foundational building blocks!</text>
      <sha1>2zr0gbs3rq8qd9zzeulabmj7ceddao3</sha1>
    </revision>
  </page>
  <page>
    <title>On 2D Inverse Problems/Area</title>
    <ns>0</ns>
    <id>486187</id>
    <revision>
      <id>4675773</id>
      <parentid>4675024</parentid>
      <timestamp>2026-10-13T01:19:07Z</timestamp>
      <contributor>
        <username>DVD206</username>
        <id>724793</id>
      </contributor>
      <minor />
      <comment>difference and differential...</comment>
      <origin>4675773</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1865" sha1="rr11bk48n42r0jbccr7m35x8xqo9yfz" xml:space="preserve">The energy integral represents the area of the image of the unique conformal map (discrete analytic map) under harmonic function with given boundary conditions:
&lt;math&gt;
E_\gamma(u)=\sum_{pq\in E}\gamma_{pq}(u(p)-u(q))^2\ge 0
&lt;/math&gt;
and for the dual graph/network harmonic conjugate:
&lt;math&gt;
E_\gamma(u)=\sum_{pq\in E}\frac{1}{\gamma_{pq}}(v(p)-v(q))^2=
\sum_{pq\in E}(u(p)-u(q))(v(p)-v(q)).
&lt;/math&gt;
For the analytic contimuation of Laplacian
&lt;math&gt;
E_{s,\gamma(u)}=\sum_{pq\in E}\gamma_{pq}(u^2(p)-(s+1/s)u(p)u(q)+u(q)^2).
&lt;/math&gt;
The harmonic function minimizes the integral with given boundary conditions and the response Dirichlet-to-Neumann map sends the boundary potential to boundary current for the harmonic function in interior...

For &lt;math&gt;s=e^{i\theta},&lt;/math&gt; &lt;math&gt;E_s=\sum_{pq\in E}\gamma_{pq}(u^2(p)-2\cos(\theta)u(p)u(q)+u(q)^2)\ge E_1\ge 0&lt;/math&gt; and, therefore Laplace, &lt;math&gt;&lt;f,\Lambda_s f&gt;\ge 0&lt;/math&gt; is Hermitian with non-negative eigenvalues.

We study the zeros and poles (monodromy eigenvalues) of the Schur complement of &lt;math&gt;L_s&lt;/math&gt; &lt;math&gt;\det(\Lambda_{s,\gamma})=0,\infty&lt;/math&gt;. They're simple positive and interlace for the circular planar graph because of total positivity of the monodromy matrix in the alternating basis...

Following the cycles in the Spiderweb network: &lt;math&gt;\det(L_s)=\det(L_{1/s})=\det(L^*_s)=\det(L_{sw})=\prod(s_k-s^n)(s_k-1/s^n), w^N=1&lt;/math&gt;, w is the N'th root of unity, where the roots &lt;math&gt;s_k&lt;/math&gt;'s are positive numbers (reciprocal eigenvalues of monodromy matrix) interlacing for homogenuous Dirichlet and Neumann boundary conditions...
The continuous differential version of &lt;math&gt;L_s(u)=s^{-\theta}L(s^\theta u)&lt;/math&gt;
 is generalization of &lt;math&gt;\frac{1}{r}\frac{d}{dr}(r\frac{d}{dr})-\frac{1}{r^2}(\frac{d}{d\theta}+\ln(s))^2&lt;/math&gt;, fractal Laplace operator in polar coordinates.
{{BookCat}}</text>
      <sha1>rr11bk48n42r0jbccr7m35x8xqo9yfz</sha1>
    </revision>
  </page>
  <page>
    <title>User talk:Luciérnaga de conocimiento</title>
    <ns>3</ns>
    <id>486324</id>
    <revision>
      <id>4675718</id>
      <timestamp>2026-10-12T12:19:16Z</timestamp>
      <contributor>
        <username>MarcGarver</username>
        <id>134830</id>
      </contributor>
      <comment>/* Removal of interwiki links */ new section</comment>
      <origin>4675718</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="276" sha1="i6695fthft4ov1a1fa3kvkqjireoszs" xml:space="preserve">== Removal of interwiki links ==
Wikibooks allows interwiki links, despite the existence of Wikidata. So, don't delete them. Thanks [[User:MarcGarver|MarcGarver]] ([[User talk:MarcGarver|discuss]] • [[Special:Contributions/MarcGarver|contribs]]) 12:19, 12 October 2026 (UTC)</text>
      <sha1>i6695fthft4ov1a1fa3kvkqjireoszs</sha1>
    </revision>
  </page>
  <page>
    <title>User:Yuzzo678</title>
    <ns>2</ns>
    <id>486325</id>
    <revision>
      <id>4675722</id>
      <timestamp>2026-10-12T12:28:39Z</timestamp>
      <contributor>
        <username>Yuzzo678</username>
        <id>3628232</id>
      </contributor>
      <comment>/* */ love45</comment>
      <origin>4675722</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="0" sha1="phoiac9h4m842xq45sp7s6u21eteeq1" />
      <sha1>phoiac9h4m842xq45sp7s6u21eteeq1</sha1>
    </revision>
  </page>
  <page>
    <title>Talk:A-level Computing AQA Paper 1 Skeleton program 2027</title>
    <ns>1</ns>
    <id>486327</id>
    <revision>
      <id>4675757</id>
      <timestamp>2026-10-12T17:57:27Z</timestamp>
      <contributor>
        <username>EmptyWeeble</username>
        <id>3628265</id>
      </contributor>
      <comment>/* Can we move the page? */ new section</comment>
      <origin>4675757</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="334" sha1="kuxvurxvi5emr5p249iiuiq1121svn4" xml:space="preserve">== Can we move the page? ==
Is it possible to move this page to match the URLs of former pages which all carry the same format?

e.g.
A-level_Computing/AQA/Paper_1/Skeleton_program/2027 [[User:EmptyWeeble|EmptyWeeble]] ([[User talk:EmptyWeeble|discuss]] • [[Special:Contributions/EmptyWeeble|contribs]]) 17:57, 12 October 2026 (UTC)</text>
      <sha1>kuxvurxvi5emr5p249iiuiq1121svn4</sha1>
    </revision>
  </page>
  <page>
    <title>Dendeng</title>
    <ns>0</ns>
    <id>486328</id>
    <revision>
      <id>4675794</id>
      <timestamp>2026-10-13T07:15:22Z</timestamp>
      <contributor>
        <username>Naila Fathinah</username>
        <id>3582567</id>
      </contributor>
      <comment>Created page with &quot;== Minang-Style: Dendeng Balado Recipe == {{Recipe|noincludecat=no}} {{recipe summary | cuisine = Indonesian | origin = West Sumatra, Indonesia | yield = 1 plate | servings = 4–5 | time = 1 hour | difficulty = 2 | image = [[File:Dendeng lambok 1.jpg|300px]] | note = Pound the beef gently to flatten it without tearing the meat apart. }} '''Dendeng Balado''' is a classic West Sumatran dish made from thinly sliced beef that is braised with aromatic spices, pounded until t...&quot;</comment>
      <origin>4675794</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2829" sha1="8v3s7kttx010d49jjbv7b2lfol1h46s" xml:space="preserve">== Minang-Style: Dendeng Balado Recipe ==
{{Recipe|noincludecat=no}}
{{recipe summary
| cuisine = Indonesian
| origin = West Sumatra, Indonesia
| yield = 1 plate
| servings = 4–5
| time = 1 hour
| difficulty = 2
| image = [[File:Dendeng lambok 1.jpg|300px]]
| note = Pound the beef gently to flatten it without tearing the meat apart.
}}
'''Dendeng Balado''' is a classic West Sumatran dish made from thinly sliced beef that is braised with aromatic spices, pounded until tender, and fried until crispy or chewy. It is then coated in a rich, fragrant, and fiery red chili sambal (''lado'') sautéed in the oil used to fry the beef, absorbing all the savory flavors into every bite.

== Main Ingredients ==

* '''500g (1.1 lbs)''' [[wikipedia:Beef|beef]] (''tenderloin'' or ''eye of round'')
* '''1 liter''' [[wikipedia:Water|water]] (for boiling)
* '''1 tbsp''' [[wikipedia:Tamarind|tamarind]] water/juice
* '''2''' [[wikipedia:Bay_leaf|Indonesian bay leaves]] (''daun salam'')
* '''[[wikipedia:Cooking_oil|Cooking oil]]''' as needed

== Boil/Braising Paste (Bumbu Ungkep) ==

* '''5 cloves''' [[wikipedia:Garlic|garlic]]
* '''1 tbsp''' [[wikipedia:Coriander|coriander]] powder
* '''2 cm (0.8 in)''' [[wikipedia:Ginger|ginger]]
* '''1 tsp''' [[wikipedia:Salt|salt]]

== Balado Chili Sambal ==

* '''15''' red curly or large red [[wikipedia:Chili_pepper|chilies]] (coarsely pounded/ground)
* '''10 cloves''' [[wikipedia:Shallot|shallots]] (coarsely pounded/ground)
* '''1''' red [[wikipedia:Tomato|tomato]] (chopped or lightly crushed)
* '''4''' [[wikipedia:Kaffir_lime|kaffir lime]] leaves (stems removed)
* '''1 tsp''' salt &amp; '''1/2 tsp''' [[wikipedia:Sugar|sugar]]

== Procedure ==

# '''Boil the Beef:''' Boil the beef in water along with the braising paste, bay leaves, and tamarind juice until tender and the liquid reduces significantly. Remove the beef and drain well.
# '''Slice &amp; Pound:''' Slice the beef thinly along the grain. Gently pound/flatten each slice using a meat mallet or pestle until widened without tearing the meat apart.
# '''Fry the Beef:''' Heat oil in a pan and fry the beef briefly until slightly crisp or cooked to your preferred texture (avoid over-frying so it doesn't get tough). Drain and set aside.
# '''Sauté the Sambal:''' Sauté the coarsely ground chilies, shallots, and tomato along with the kaffir lime leaves using some of the leftover beef-frying oil. Season with salt and sugar, then cook over low heat until fragrant and the raw chili flavor disappears.
# '''Serve:''' Add the fried beef to the pan with the balado sambal and toss until evenly coated. Remove from heat and serve hot with warm steamed rice.

[[Category:Indonesian recipes]]
[[Category:Southeast Asian recipes]]
[[Category:Beef recipes]]
[[Category:Recipes]]
[[Category:Recipes for chili]]
[[Category:Asian recipes]]</text>
      <sha1>8v3s7kttx010d49jjbv7b2lfol1h46s</sha1>
    </revision>
  </page>
  <page>
    <title>User:Naila Fathinah</title>
    <ns>2</ns>
    <id>486329</id>
    <revision>
      <id>4675795</id>
      <timestamp>2026-10-13T07:17:57Z</timestamp>
      <contributor>
        <username>Naila Fathinah</username>
        <id>3582567</id>
      </contributor>
      <comment>Created page with &quot;hi&quot;</comment>
      <origin>4675795</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2" sha1="moiryvew7z1nh6cf1srex5j09y58bpe" xml:space="preserve">hi</text>
      <sha1>moiryvew7z1nh6cf1srex5j09y58bpe</sha1>
    </revision>
  </page>
  <page>
    <title>PCBA</title>
    <ns>0</ns>
    <id>486330</id>
    <revision>
      <id>4675807</id>
      <timestamp>2026-10-13T08:57:28Z</timestamp>
      <contributor>
        <username>LokiZhan</username>
        <id>3628315</id>
      </contributor>
      <comment>Added a comprehensive PCBA learning resource covering assembly technologies, manufacturing processes, inspection methods, design requirements, and industry standards.</comment>
      <origin>4675807</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="11803" sha1="27yr8nxkclgk1q10s5o6t38wu6hykdc" xml:space="preserve">
'''Printed circuit board assembly''' ('''PCBA''') refers to the process of mounting and electrically connecting electronic components to a printed circuit board (PCB). The term also describes the resulting assembly, commonly called a printed circuit assembly (PCA).

A bare PCB contains the conductive paths, insulating layers, pads, and other features needed to support a circuit. Once components such as integrated circuits, resistors, capacitors, and connectors have been installed, the board becomes a PCBA. This distinction is important when specifying whether a manufacturing order requires bare boards or assembled electronics.&lt;ref&gt;[https://pcbcool.com/technical-guides/pcb-vs-pcba/ PCB vs. PCBA: Key Differences for Electronics Projects | PCBCool]&lt;/ref&gt;

The assembly method depends on the component packages, board layout, production quantity, and applicable manufacturing requirements.

== Assembly Technologies ==

Electronic components are generally attached using surface-mount technology (SMT), through-hole technology (THT), or a combination of the two.

=== Surface-Mount Technology ===

In surface-mount technology, component terminals are soldered directly to conductive pads on the PCB surface. Solder paste is deposited on the pads, usually through a metal stencil, before components are positioned by automated placement equipment.

Stencil aperture geometry affects the amount of solder paste deposited. IPC-7525 provides guidelines for designing stencils used in solder paste printing and surface-mount assembly.&lt;ref&gt;[https://www.ipc.org/TOC/IPC-7525B.pdf IPC-7525B: Stencil Design Guidelines | IPC]&lt;/ref&gt;

After placement, the populated PCB passes through a reflow oven. A controlled temperature profile heats the solder paste until it melts and forms solder joints. The profile must be compatible with the solder alloy, component packages, and PCB construction.

Texas Instruments identifies solder paste deposition, component placement, and reflow conditions as important factors affecting assembly quality, particularly for small and densely packaged devices.&lt;ref&gt;[https://www.ti.com/lit/pdf/slvafh0 Solving Assembly Issues with Chip Scale Power MOSFETs | Texas Instruments]&lt;/ref&gt;

SMT is widely used where small component packages and high component density are required. Some packages, including ball grid arrays (BGAs), have solder connections beneath the component body, making direct visual inspection difficult.

=== Through-Hole Technology ===

Through-hole components have leads that pass through holes in the PCB and are soldered to the appropriate conductive connections.

Manual soldering, wave soldering, and selective soldering are common methods for attaching through-hole components. Process selection depends on component characteristics, accessibility, production volume, and the board configuration.

Through-hole mounting is used for certain connectors, transformers, and components requiring particular mechanical mounting characteristics.

=== Mixed-Technology Assembly ===

A board may contain both SMT and through-hole components. In this case, the production sequence must accommodate different placement and soldering operations.

Surface-mount components are commonly assembled by reflow soldering before through-hole components are installed. Other sequences may be used when dictated by component limitations or manufacturing requirements.

== Manufacturing Process ==

Production begins with the preparation of the assembly documentation. The bill of materials (BOM) identifies the required components, while placement files and assembly drawings define their positions, orientations, and installation requirements.

The bare boards and components are checked before processing. Component storage conditions, moisture sensitivity, and handling requirements may affect preparation.

For a typical SMT assembly, the production sequence consists of the following operations.

=== Solder Paste Printing ===

A stencil printer deposits solder paste onto designated PCB pads. The amount of paste transferred depends on stencil geometry, alignment, paste properties, and printing conditions.

IPC-7527 addresses requirements associated with solder paste printing, while IPC-7525 provides related stencil design guidance.&lt;ref&gt;[https://www.ipc.org/ipc-document-revision-table IPC Document Revision Table | IPC]&lt;/ref&gt;

=== Component Placement ===

Pick-and-place equipment positions components according to the placement data. Accurate alignment is important for devices with closely spaced terminals and small solder pads.

Placement force must also be controlled for packages that are sensitive to mechanical loading. Texas Instruments provides package-specific assembly recommendations covering placement, solder paste patterns, and reflow conditions.&lt;ref&gt;[https://www.ti.com/lit/pdf/slvafh0 Solving Assembly Issues with Chip Scale Power MOSFETs | Texas Instruments]&lt;/ref&gt;

=== Reflow Soldering ===

The populated board is heated according to a defined temperature profile. During reflow, the solder alloy melts and wets the component terminals and PCB pads.

The assembly is subsequently cooled to solidify the joints. Temperature profiling must take account of the thermal limits of the components, board materials, and solder system.

For package-on-package assemblies, Texas Instruments identifies solder paste deposition and reflow conditions as significant factors affecting assembly quality and reliability.&lt;ref&gt;[https://www.ti.com/lit/an/spraba8/spraba8.pdf PCB Assembly Guidelines for 0.5 mm Package-on-Package Applications | Texas Instruments]&lt;/ref&gt;

=== Subsequent Operations ===

Additional processes may include through-hole component installation, cleaning, mechanical assembly, programming, or application-specific testing.

Not every PCBA requires all of these operations. The production route is determined by the assembly design and applicable manufacturing specifications.

== Inspection and Testing ==

Inspection and testing establish whether an assembly meets its physical and functional requirements.

'''Visual inspection''' examines accessible components, solder joints, markings, and board surfaces. '''Automated optical inspection''' (AOI) uses imaging systems to identify selected placement and soldering defects.

'''X-ray inspection''' is used for connections that cannot be examined directly, particularly those beneath certain area-array packages. The design and construction of BGA packages create inspection and assembly considerations that differ from components with externally visible leads.&lt;ref&gt;[https://www.analog.com/en/resources/app-notes/ball-grid-array-bga-packages-and-pcb-design-guidelines.html Ball Grid Array Packages and PCB Design Guidelines | Analog Devices]&lt;/ref&gt;

'''In-circuit testing''' (ICT) uses electrical measurements through accessible test points to identify certain component and connection faults.

'''Functional testing''' verifies specified circuit behavior. It may include checking power rails, communication interfaces, input and output functions, and other operating requirements.

Common assembly defects include:

* '''Solder bridges:''' Unintended solder connections between adjacent conductors.
* '''Insufficient solder:''' Inadequate solder volume or incomplete joint formation.
* '''Tombstoning:''' Lifting of one end of a small surface-mount component during reflow.
* '''Component misalignment:''' Placement outside the intended solder pad position.
* '''Solder voids:''' Gas pockets or unfilled regions within a solder connection.

Not all defects can be identified by a single inspection technique. The selection of inspection and testing methods depends on the product and the required fault coverage.

IPC-A-610 establishes acceptance criteria for electronic assemblies. IPC J-STD-001 addresses soldering processes, materials, and workmanship requirements. The two standards are frequently used together in electronics manufacturing.&lt;ref&gt;[https://www.ipc.org/news-release/ipc-releases-j-revisions-two-leading-standards-electronics-assembly IPC Releases J Revisions to Two Leading Standards for Electronics Assembly]&lt;/ref&gt;

== Design Requirements for Assembly ==

PCB layout affects component placement, solder joint formation, inspection access, and the feasibility of rework.

Component footprints must be compatible with the intended packages and soldering processes. Pad dimensions, solder mask openings, and stencil patterns require particular attention for fine-pitch devices and area-array packages.

Analog Devices discusses differences between solder mask-defined and non-solder mask-defined pads in its BGA package design guidance. The appropriate land pattern depends on the package and the manufacturer's recommendations.&lt;ref&gt;[https://www.analog.com/en/resources/app-notes/ball-grid-array-bga-packages-and-pcb-design-guidelines.html Ball Grid Array Packages and PCB Design Guidelines | Analog Devices]&lt;/ref&gt;

Adequate spacing is also needed for placement equipment, inspection, and any anticipated rework. Components connected to large copper areas may require additional consideration because of differences in thermal behavior during soldering.

Design for manufacturability (DFM) reviews address whether a board can be fabricated and assembled using the intended processes. Design for testability (DFT) reviews consider whether the completed circuit can be tested effectively.

The applicable design requirements vary by product and should be established before production.

== Handling and Environmental Protection ==

Electrostatic discharge (ESD) can damage sensitive electronic components during storage, assembly, inspection, and repair.

An ESD control program may include personnel grounding, protected workstations, suitable packaging, and controlled handling procedures.

ANSI/ESD S20.20 establishes administrative and technical requirements for developing and maintaining an ESD control program for electrical and electronic parts, assemblies, and equipment.&lt;ref&gt;[https://www.esda.org/store/standards/product/314/ansiesd-s20-20-2021/ ANSI/ESD S20.20-2021 | EOS/ESD Association]&lt;/ref&gt;

Assemblies used in environments involving moisture, contamination, or other environmental stresses may require additional protection.

Conformal coatings can be applied to selected electronic assemblies to reduce exposure to environmental contaminants. Coating selection depends on the materials, operating conditions, and product requirements.

NASA-STD-8739.1 addresses workmanship requirements for polymeric applications on electronic assemblies, including conformal coating and related processes.&lt;ref&gt;[https://standards.nasa.gov/standard/NASA/NASA-STD-87391 NASA-STD-8739.1: Workmanship Standard for Polymeric Application on Electronic Assemblies]&lt;/ref&gt;

== Industry Standards ==

Several IPC standards are commonly referenced in electronics assembly.

{| class=&quot;wikitable&quot;
! Standard
! Scope
|-
| IPC J-STD-001
| Requirements for soldered electrical and electronic assemblies
|-
| IPC-A-610
| Acceptability of electronic assemblies
|-
| IPC-7352
| Surface-mount land pattern design guidance
|-
| IPC-7525
| Stencil design guidelines
|-
| IPC-7527
| Requirements for solder paste printing
|-
| IPC-7530
| Temperature profiling guidance for wave and reflow soldering processes
|-
| IPC-7711/7721
| Rework, modification, and repair of electronic assemblies
|}

The IPC document revision table records current and historical editions of these publications.&lt;ref&gt;[https://www.ipc.org/ipc-document-revision-table IPC Document Revision Table]&lt;/ref&gt;

Different products may require different acceptance classes, standard revisions, or customer-specific requirements. These must be identified in the relevant manufacturing documentation.

== References ==

&lt;references/&gt;</text>
      <sha1>27yr8nxkclgk1q10s5o6t38wu6hykdc</sha1>
    </revision>
  </page>
</mediawiki>