Cookbook:Garlic Croutons I

<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.13</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>Cookbook:Garlic Croutons I</title>
    <ns>102</ns>
    <id>8040</id>
    <revision>
      <id>4656175</id>
      <parentid>4495781</parentid>
      <timestamp>2026-08-03T08:02:44Z</timestamp>
      <contributor>
        <username>Jdlrobson</username>
        <id>563339</id>
      </contributor>
      <origin>4656175</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1821" sha1="jsnzvbbt14us32oagug4x20ega9fl7q" xml:space="preserve">__NOTOC__
{{recipesummary
| category = Bread recipes
| time = 20 minutes
| Servings = 4
| difficulty = 1
| Image = [[File:Semmelwuerfel geroestet.jpg|300px]]
}}

{{recipe}} | [[Cookbook:Bread|Bread]] | [[Cookbook:Cuisine of France|French cuisine]] | [[Cookbook:Salad|Salads]] | [[Cookbook:Soups|Soups]]

'''Garlic croutons''' can be purchased but are much better when made from old bread. They are a crucial ingredient of [[Cookbook:Caesar_Salad|Caesar Salad]].

== Ingredients ==
*4 slices day-old French bread, [[Cookbook:Cube|cubed]]
*2 cloves [[Cookbook:Garlic|garlic]], [[Cookbook:Mincing|minced]]
*4 [[Cookbook:Tablespoon|tablespoons]] [[Cookbook:Olive_oil|olive oil]]
*[[Cookbook:Salt|Salt]] to taste

== Procedure ==
# Pour the olive oil into a shallow bowl over the garlic and let it soak. Soaking it longer will yield more garlic flavor.
# Preheat the [[Cookbook:Oven|oven]] to 350 °F (~180 °C).
# [[Cookbook:Straining|Strain]] the olive oil into a [[Cookbook:Frying Pan|frying pan]] and [[Cookbook:Frying|fry]] the bread cubes in it, [[Cookbook:Mixing#Tossing|tossing]] to coat with oil.
# Spread the bread cubes on a [[Cookbook:Baking Sheet|baking sheet]] and sprinkle with salt. [[Cookbook:Baking|Bake]] for 10 minutes or until crispy and dry.

== Notes, tips, and variations ==
* To make non-garlic croutons, simply omit the garlic.
* One may omit the prep work of mincing the garlic by adding the whole cloves of garlic to the oil and then crushing the garlic (either with a mortar or a fork).
* By using very small bread cubes, frying crisp, and omitting the baking, these croutons may be used in place of potatoes.

[[Category:Recipes using bread]]
[[Category:Recipes using garlic]]
[[Category:Pan fried recipes]]
[[Category:Baking recipes]]
[[Category:Vegan recipes]]
[[Category:Recipes for croutons]]</text>
      <sha1>jsnzvbbt14us32oagug4x20ega9fl7q</sha1>
    </revision>
  </page>
  <page>
    <title>Cookbook:Rice and Lentils (Mejadra)</title>
    <ns>102</ns>
    <id>8658</id>
    <revision>
      <id>4656171</id>
      <parentid>4608324</parentid>
      <timestamp>2026-08-03T07:41:03Z</timestamp>
      <contributor>
        <username>Jdlrobson</username>
        <id>563339</id>
      </contributor>
      <comment>File was deleted</comment>
      <origin>4656171</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2968" sha1="swfx5fdta97jj8ow1m0gktxwr4dr70v" xml:space="preserve">{{recipesummary
| Category = Middle Eastern recipes
| Servings = 3–4
| Time = 30 minutes
| difficulty = 2
| Rating = 2
| Image = [[Image:Mejadrah.s.jpg|300px]]
}}
{{recipe}} | [[Cookbook:Palestinian Cuisine|Palestinian Cuisine]]
{{see also|Cookbook:Mjeddrah}}

{{Nutrition Summary|
|ServingSize=1/3 of recipe (350 g)
|Servings=3
|Cals=150
|FatCals=27
|TotalFat=2.99 g
|SatFat=0.65 g
|Cholesterol=2 mg
|Sodium=401 mg
|Carbs=32.4 g
|Fiber=1.53 g
|Sugars=3.12 g
|Protein=4.98 g
|VitaminA=3%
|VitaminC=1%
|Calcium=2%
|Iron=7%
}}Extremely simple to cook, '''mejadra''' is a fundamental component of Middle Eastern cuisine. It provides carbohydrates, proteins, and a full stomach. It also tastes great. The most common recipe uses rice. Bulgur can be substituted for rice, using the exact same procedure. When cooked with rice, this recipe is [[Cookbook:Gluten-Free|gluten-free]]. It isn't gluten free when cooked with bulgur (wheat).

== Ingredients ==
* 1 [[Cookbook:Cup|cup]] (100 [[Cookbook:Gram|g]] / 3.5 [[Cookbook:Ounce|oz]]) dry [[Cookbook:Lentil|lentils]]
* [[Cookbook:Olive Oil|Olive oil]]
* [[Cookbook:Salt|Salt]]
* [[Cookbook:Baharat|Baharat]]
* [[Cookbook:Cumin|Cumin]]
* [[Cookbook:Cardamom|Ground cardamom]]
* 4 cups (1 [[Cookbook:Liter|L]] / 1.1 [[Cookbook:Quart|qt]]) water, divided
* 1 cup (80 [[Cookbook:Gram|g]] / 2.8 [[Cookbook:Ounce|oz]]) uncooked [[Cookbook:Rice|rice]] or [[Cookbook:Bulgur|bulgur]]
* Ground [[Cookbook:Pepper|pepper]]
* 1 medium sized [[Cookbook:Onion|onion]]

== Procedure==
# [[Cookbook:Frying|Fry]] the lentils in oil for 3–4 minutes, stirring continuously, until the first beans show signs of scorching.
# Add salt, baharat, cumin, and ground cardamom to taste.
# Add 2 cups water and cover. Bring to a boil, lower to a [[Cookbook:Simmering|simmer]]. Cook for 20 minutes or until all the water is absorbed by the lentils.
# Fry the rice in oil for 3–4 minutes, stirring continuously, until the grains change colour.
# Add salt, black or white pepper, and ground cardamom.
# Add 2 cups water and cover. Bring to a boil, lower to a simmer. After 5 minutes turn the heat off, and leave standing for another 10 minutes.
# Cut the onion into thin strips (about 0.5x4 [[Cookbook:Centimetre (cm)|cm]] / 0.2x1.6 [[Cookbook:Inch|in]]).
# Fry the onion in olive oil until crisp and deeply golden brown (this may take a while but will result in much fuller flavor).
# Mix the lentils and rice, and top with the fried onion. Use 2 parts lentils to 1 part rice for a moist consistency.

[[Category:Featured recipes]]
[[Category:Israeli recipes]]
[[Category:Palestinian recipes]]
[[Category:Middle Eastern recipes]]
[[Category:Vegan recipes]]
[[Category:Gluten-free recipes]]
[[Category:Recipes using lentil]]
[[Category:Recipes using rice]]
[[Category:Recipes using onion]]
[[Category:Boiled recipes]]
[[Category:Side dish recipes]]
[[Category:Recipes using baharat]]
[[Category:Recipes using cardamom]]
[[Category:Recipes using cumin]]</text>
      <sha1>swfx5fdta97jj8ow1m0gktxwr4dr70v</sha1>
    </revision>
  </page>
  <page>
    <title>Talk:Open Source</title>
    <ns>1</ns>
    <id>14866</id>
    <revision>
      <id>4656138</id>
      <parentid>1395285</parentid>
      <timestamp>2026-08-02T23:14:11Z</timestamp>
      <contributor>
        <username>LakshitSinghBishtTM</username>
        <id>3618774</id>
      </contributor>
      <comment>/* Updating the page */ new section</comment>
      <origin>4656138</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="8703" sha1="gz9ppl8c1p59cooiimo551kodwiwoy3" xml:space="preserve">==Discussions lacking a  subject==

We have launched a project o open source project modelling.

--

There are a myraid of Open Source projects.  While I appreciate your interest in Open Source, please make project announcements on appropriate sites (eg SourceForge and FreshMeat).  The context of this page is the notion of &quot;Open Source&quot; and the respective liscenses -- NOT a trove of Open Source software.

Moreover, if you actually bothered to read the page, you would note that the context is (incorrectly) NOT Open Source, but rather Freeware.

--[[User:Eibwen|Eibwen]] 08:28, 25 Sep 2004 (UTC)
----

Is there really a point to creating yet another trove?

--[[User:146.244.186.42|146.244.186.42]] 04:29, 26 Sep 2004 (UTC)

== a definitve resource ==

I feel it is quite resonable to provide as part of Wikiversity a definitive (and updated) unbiased list of resouces for study [[User:Lobster|Lobster]] 15:34, 26 Sep 2004 (UTC)

:While I agree with the spirit of your statement, I disagree with its applicability.  There are several established troves of freeware (and open source) software, notably [http://www.download.com C|Net's Download.com], [http://sourceforge.org SourceForge], and [http://freshmeat.net FreshMeat].  If this page is to be a definitive listing, it would have to address the myriad of individual titles available -- essentially mirroring other established troves.

:I do not believe this to be in the interest of this wiki.

:HOWEVER, I would not object to a listing of the leading applications for each category -- and ONLY the leading application.  Anything beyond that would constitute a trove and thus be subject to the discussion above.

:--[[User:Eibwen|Eibwen]] 04:51, 27 Sep 2004 (UTC)

Sometimes there are several leading packages which suit choice, circumstance and preference

The source links you suggest are not suitable for beginners and others who would find the layout confusing

The page is not designed as a trove but as an impartial source that does not have a commercial, open source or other agenda to promote 
to the detriment of end users.

Though open source is the ideal it does not always have the best available software - therefore creating a page that combines the ideas of Open Source with what is of most use, is an educational stance in the spirit of wiki books and not some pedantic insistence on the absolute. 

I hope you have taken the time to add your links to the links section?

[[User:Lobster|Lobster]] 05:10, 27 Sep 2004 (UTC)

== Why a simple software listing? ==
Why does it seem to be the standing assumption that a book about Open Source software should be about what software is out there?  I would agree with those that have commented above that we have more then enough of those in the world already, and how would that be a book anyway?  There is a great deal of philosophy in the open source movement, and a great deal to be written about open source project management. To me a ''BOOK'' on open source should cover those issues.  Only after those issues were discussed would a specific listing of software be included.  While these issues can be hinted at in the wikipedia article, to keep to the reasonable length requirements of the pedia it makes sense that detailed discussions about the philosophy, history, debates, lessons learned, case studies and other related discussions would be the topic of a full length book (indeed there are books like that in print).  Where else should a detailed discussion of the difference between the GPL and BSD licences find a proper home?  Or an explination of the difference between free software and open source software?
[[User:Ahc|Ahc]] 05:55, 28 Nov 2004 (UTC)

Hi Ahc and everyone - I hope you will take '''the fat''' from the freeware page and wikipedia and place it here where some of the important issues - such as the politics, the future, relationships between groups, legal standing and other up to date sections such as OS NEWS can be explored -

 also the removal indication -which some people with a monitor fixation are too keen on - whilst those with real personality are modifying and adapting NEEDS TO BE CLEARED
or the page should go - if this indication appears I tend to abandon the page as the useless 'experts' rarely attempt to improve or advise they just criticise and remove - yuk. Fortunately some of the more experienced, genuine moderators are more understanding of how sometimes these things take time to develop . . . Good luck I hope you manage to make something of this [[User:Lobster|Lobster]] 05:46, 5 Dec 2004 (UTC)

: Okay, I'm starting the process of giving this book better direction.  Over the next couple days I'm going to be rather aggressive in pruning, and re-outlining the old material in the book, and starting to create new material.  If anyone had ideas I'd love to hear them.  I expect to copy/move some material from the freeware book and wikipedia articles as appropreite (at least in my opintion). --[[User:Ahc|Ahc]] 04:47, 6 Dec 2004 (UTC)

== Logo ==

[[User:Lobster|Lobster]] thanks for the logo. I personally would prefer something a little more suttle, but that's just my taste in logos.  I didn't bother to create one, so I'm not really one to complain.  Thanks. --[[User:Ahc|Ahc]] 14:00, 8 Dec 2004 (UTC)

It is kind of the best I could do and just a small contribution to encourage your efforts

I am trying to get this wiki going

http://peace.wikicities.com/index.php/Main_Page

it is getting a little New Agey - so if you are an atheist your contributions would be welcome

[[User:82.69.58.117|82.69.58.117]] 17:28, 8 Dec 2004 (UTC)

== open source books and links ==

http://phptr.com/promotion/1484?redir=1

== History Section ==

I love it if someone familiar with the history of BSD would help out with the history section.  I will work on reviewing the Wikipedia article on it for material, but I know much more about the emergance of GNU. --[[User:Ahc|Ahc]] 03:32, 9 Dec 2004 (UTC)

== Licenses ==

I'm trying to figure out how to do this section.  I have two questions that I'm not sure about.

# Should the section include the text of the licenses?
# If so, what are the rules about posting them?  Most (all?) are copyrighted texts, but the authors request that they be shared.  What are wikibook's rules about this, does anyone know?

--[[User:Ahc|Ahc]] 05:31, 12 Dec 2004 (UTC)

I would suggest highlights and links to the full text
To be honest I feel there two many liscences and they are confusing

so some form of line from no restrictions to open but restrictions would be useful (if indeed it can be delineated in this way)

:Since there are so many licenses out there I was only going to look at a couple of the most popular and therefore important, GPL, BSD, Apache.  They cover most of the important differences between the types.  If others should be included feel free to suggest them. 
:--[[User:Ahc|Ahc]] 15:39, 1 Jan 2005 (UTC)

Great info guys - here is a link that I came across and thought of this project 

:-) 

http://www.dwheeler.com/oss_fs_why.html

[[User:82.69.58.117|82.69.58.117]]

== What is open source? ==

The recently added material in what is open source concerns me a little.  Some suggestions from the peanut gallary would be helpful here.  The material is from the [http://opensource.org/ OSI] web site which is licenced under the  [http://opensource.org/licenses/osl-2.1.php Open Software Licence] and the [http://opensource.org/licenses/afl-2.1.php Acedemic Free Licence].  OSL requires that all dirivative works are licenced under the OSL, but the AFL has no such requirements.  Since Wikibooks is licenced under the [http://www.gnu.org/copyleft/fdl.html GNU Free Documentation Licence] it does not meet the requirements of the OSL but it should be okay under AFL.  Anyone know what the write answer is here?  --[[User:Ahc|Ahc]] 20:08, 9 Jun 2005 (UTC)


: Things can be dual licensed, but the GNU's FDL pretty much cannot be added to anything that already had a license with any restrictions that the FDL doesn't itself impose and things licensed under the FDL cannot be relicensed under anything that adds restrictions.  [[User:Nmontague|Nmontague]] 23:46, 20 August 2005 (UTC)

== Suggest Title Change ==

Given that this book discusses both Open Source Software and Free Software, I would suggest changing the title to FOSS or FLOSS (Free and Libre Open Source Software).

== Updating the page ==

The content of open source page is too old as of now in 2026. I think it should be updated [[User:LakshitSinghBishtTM|LakshitSinghBishtTM]] ([[User talk:LakshitSinghBishtTM|discuss]] • [[Special:Contributions/LakshitSinghBishtTM|contribs]]) 23:14, 2 August 2026 (UTC)</text>
      <sha1>gz9ppl8c1p59cooiimo551kodwiwoy3</sha1>
    </revision>
  </page>
  <page>
    <title>Cookbook:Organic</title>
    <ns>102</ns>
    <id>18863</id>
    <revision>
      <id>4656104</id>
      <parentid>4656035</parentid>
      <timestamp>2026-08-02T20:31:59Z</timestamp>
      <contributor>
        <username>Kittycataclysm</username>
        <id>3371989</id>
      </contributor>
      <minor />
      <comment>[[WB:REVERT|Reverted]] edits by [[Special:Contributions/~2026-42631-63|~2026-42631-63]] ([[User talk:~2026-42631-63|talk]]) to last version by Kingofnuthin</comment>
      <origin>4621958</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="12943" sha1="gdngwyemawt8zxbbn0sdfgpv5m9qkjy" xml:space="preserve">{{cookwork}}{{Diet}}

'''''Organic food''''' has both a popular meaning, and in some countries, a legal definition. In everyday conversation, it usually refers to all &quot;naturally produced&quot; foods, or the product of organic farming. As a legal and marketing term, it means certified organic. The distinction is important, as the two definitions can represent quite different products.

==Types of organic food==

Organic foods, like food in general, can be grouped into two categories, ''fresh'' and ''processed'', based on production methods, availability and consumer perception.

'''Fresh food''' is seasonal and highly perishable. Fresh [[cookbook:produce|produce]] &amp;mdash; [[cookbook:vegetable|vegetables]] and [[cookbook:fruit|fruits]] &amp;mdash; is the most available type of organic food, and closely associated with organic farming. It is often purchased directly from the growers, at [[cookbook:farmers' market|farmers' markets]], from on-farm stands, through speciality food stores, and through community-supported agriculture (CSA) projects.

Unprocessed animal products &amp;mdash; organic [[Cookbook:Meat|meat]], [[cookbook:egg|eggs]], [[cookbook:dairy|dairy]] &amp;mdash; are less common. Prices can be higher than for conventional food, and availability is usually lower.

For fresh food, &quot;organic&quot; usually means: 
* produced without synthetic chemicals (e.g., fertilizers, pesticides, antibiotics, hormones)
* free of genetically modified organisms
* (often, but not necessarily) locally grown

'''Processed organic food''' products are rarely available, and prices are often higher. The majority of processed organics comes from large food conglomerates, as producing and marketing products like canned goods, frozen vegetables, prepared dishes and other convenience foods is often beyond the scope of small organic producers.

For ''processed'' organic food, the general definition is:  
*contains only (or at least a certain specified percentage of) organic ingredients
*contains no artificial food additives
*processed without artificial methods, materials and conditions (e.g., no chemical ripening, no food irradiation)

==Identifying organic food==

Organic consumers are generally looking for chemical-free, fresh or minimally processed food, and originally they had to buy directly from growers: ''Know your farmer, know your food'' was a practical reality. Organic food at first comprised mainly fresh vegetables. Personal definitions of what exactly constituted &quot;organic&quot; could be developed and verified through first-hand experience: talking to farmers and directly observing farm conditions and farming activities. Small farms could grow vegetables (and raise livestock) using organic farming practices, with or without certification, and this was more or less something the individual  consumer could monitor.

As consumer demand for organic foods continues to increase, high volume sales through mass outlets, typically supermarkets, is rapidly replacing the direct farmer connection. For supermarket consumers, food production is not easily observable. Product labelling, like &quot;certified organic&quot;, is relied on. Government regulations and third-party inspectors are looked to for assurance.

Modern food processing is complex and complicated. Commercial preparation methods, the use of food additives, the effects of packaging and storage, and the like are outside the first-hand experience of most people (including organic farmers). Traditional and minimally processed products, [[cookbook:baked goods|baked goods]]; and [[cookbook:canning|canned]], frozen, and [[cookbook:pickling|pickled]] fruits and vegetables, are somewhat easier for consumers to understand by comparison with home preparation methods, although home and mass-production techniques are quite different. For convenience foods, like frozen prepared foods, cooked breakfast cereals, and so forth, ingredients and methods are quite a mystery to most consumers. A &quot;certified organic&quot; label is usually the only way for consumers to  trust that a processed product is &quot;organic&quot;.

==Organic food and preservatives==

Unfortunately, there are no natural models for preserving food the way it's found in supermarkets. Today, food with a long shelf life is the cornerstone of the food industry, providing most of the revenue and profits. In wealthier locales, an impressive array of technologies is used to make food &quot;last&quot; longer: home refrigerators and freezers at the consumer end, and industrial and chemical practices applied along the food production chain, from seed to field to fridge or table.

In general, organic standards cover in detail this entire process, specifying what is an &quot;organic&quot; ingredient or practice. However, since there is little natural reference for preparing, for example, a precooked, frozen dinner, a &quot;certified organic&quot; label on such an item may be hard to understand. The main ingredients are one thing, the processes and additives used to assemble and preserve them are quite another.

==Differences in Organic Food==

Some of the differences that have been claimed for organic food are:
*'''tastier:''' Organic advocates claim organic food tastes better because of the way it is produced, and because there is generally a greater variety to choose from. There is no body of scientific taste testing to consult.
*'''more nutritious:''' Food produced under organic conditions are somehow structurally different from chemically-raised and processed products. This pro-organic claim is so far beyond the scope of modern science to prove or disprove. The complex make-up of food, the effect of growing and processing methods, and the internal interactions between people and their nutrients are largely unknown. Measurements of some food components &amp;mdash; protein, carbohydrates, fat, vitamins and minerals, and so on &amp;mdash; only account for the most obvious factors that have been identified so far, and research is minimal. However, there are scientific indications that, by favoring certain aspects of a plant's development, other aspects may be retarded, resulting in less nutritious food. A study published in the ''Journal of the American College of Nutrition'' in 2004, entitled ''Changes in USDA Food Composition Data for 43 Garden Crops, 1950 to 1999'', compared nutritional analysis of vegetables done in 1950 and in 1999, and found substantial decreases in six of 13 nutrients examined. Percentage reductions included 6% of [[cookbook:protein|protein]] and 38% of [[cookbook:riboflavin|riboflavin]]. Reductions in calcium, phosphorus, iron and ascorbic acid were also found. The study, conducted at the Biochemical Institute, University of Texas, concluded that the most likely cause was the breeding of crops to maximize yield. Although not on the surface a strictly organic issue, plant breeding objectives for commercial production is completely integrated with industrialized, chemical-based farming.
*'''non-toxic:''' Organic proponents point to potential problems with toxic residues from agricultural chemicals like pesticides. There is no argument that traces do not exist; however, it is widely held that: (a) they are well in &quot;safe&quot; limits (as established by government regulations); (b) washing and other recommended preparation methods eliminate any risk. One potentially relevant new areas is the principle of hormesis, an emerging outlook on the extreme low level effects of substances, that might suggest that exposure to minute quantities of toxic residues on foods may have as specific effects on humans.
*'''better for the environment:''' By this argument, every food purchase supports the system that delivers it: if the large-scale chemical production methods are damaging to the environment, then people who buy these products are directly contributing to the problem. A recent UK study concluded that local food is best for the environment, and recommended food produced within a few miles radius as being the most advantageous. Insofar as organic food is often imported from long distances, local organics would seem environmentally to be the better bet. 

To the consumer looking for self-education, a basic awareness of recent food history provides a useful context. Chemical agriculture and mass production of supermarket food have only been big business for about 50 years. During that period, radical changes in the way food is produced have been justified by quoting scientific studies and conducting large-scale advertising and publicity campaigns. In recent years, the negative longer-term effects of many chemical agriculture practices have become increasingly hard to deny, however, the lack of balanced agricultural and food research is still overwhelming. It is unlikely that anything near definitive scientific conclusions will be drawn for years, possibly decades. In the meantime, consumers have to either trust the existing standards and claims, or come to their own common sense conclusions.

==Organic Standards==
Various alternative organic standards are emerging. They generally bypass formal certification, and provide their own definition of organic food. One such, the Authentic Food standard, proposed by leading US organic farmer Eliot Coleman, includes criteria that are incompatible with current agribusiness:
*All foods are produced by the growers who sell them.
*Fresh fruits and vegetables, milk, eggs and meat products are produced within a 50-mile radius of their place of their final sale.
*The seed and storage crops (grains, beans, nuts, potatoes, etc.) are produced within a 300-mile radius of their final sale.
*Only traditional processed foods such as cheese, wine, bread and lactofermented products may claim, &quot;Made with Authentic ingredients.&quot;[http://fourseasonfarm.com/main/authentic/authentic.html]

Particularly in developed nations, it is difficult to imagine not having the majority of products found in today's supermarkets. On the other hand, most of those products did not exist 100 years ago, and many of them are only a few decades old.

==Legal definition of &quot;Certified Organic&quot;==

In the United States, agricultural products that claim to be &quot;organic&quot; must adhere to the requirements of the Organic Food Production Act of 1990 (found in 7 U.S.C.A. § 6501-22) and the regulations (found in 7 C.F.R. Part 205) promulgated by the USDA through the National Organic Program (&quot;NOP&quot;) under this act. These laws essential require that any product that claims to be organic must have been manufactured and handled according to specific NOP requirements.

Products that bear the Organic label come from farms and processing facilities that have been certified by a third party certifying organization to meet the USDA National Organic Standards.  

The Standards are based on the following rule: any &quot;natural&quot; product may be used in organic production, except for a list of exemptions; and no &quot;synthetic&quot; products can be used in organic production, except for a list of exceptions.  Organic farmers are required to have a working management plan, including crop rotation and integrated pest management strategies.  They must show that the farm has been organic for at least 3 years before they receive certification.  

Defining &quot;natural&quot; and &quot;synthetic&quot; and creating those lists of exemptions has been contentious. An important example of the exemptions that are allowed in organic production despite ''not'' being natural is synthetically produced insect pharamones used for management of insect pests, which are allowed provided that they are applied passively (allowed to dissipate from on sponges) rather than sprayed. These exemptions are justified in that they are extremely useful and completely non-toxic.  An example of the &quot;natural&quot; products that are disallowed is lead arsenic, a naturally occurring compound that was widely used as an insecticide before DDT was invented. It is disallowed because it is highly toxic to all animals, including humans; it persists in the environment almost forever, and causes even more environmental damage than almost any synthetic insecticide.

==External links==
*You can read more about [[Wikipedia:organic food|organic food]] in Wikipedia.
*[http://www.mofga.org/food.html Maine Organic Farmers and Gardeners Association] A description of why organic foods and farming may be superior.
*[http://www.organicconsumers.org/organic/organics101.cfm Brief Introduction to Organics]
*[http://www.goorganic.net/ Organic Food &amp; Product Blog]
*[http://organicconsumers.org/ Organic Consumers]
*[http://www.organicconsumers.org/organic/healthier032105.cfm Mounting Evidence that Organic Food is Healthier] 3/20/05
*[http://www.acsh.org/factsfears/newsID.78/news_detail.asp Whole Food Whooey]
*[http://www.guardian.co.uk/comment/story/0,3604,1210493,00.html The costly fraud that is organic food] (Guardian article by Dick Taverne, 6/5/2004)
*[http://www.theorganicfarm.co.uk The Organic Farm]

[[Category:Diets]]</text>
      <sha1>gdngwyemawt8zxbbn0sdfgpv5m9qkjy</sha1>
    </revision>
  </page>
  <page>
    <title>Cookbook:A Nice Cup of Tea</title>
    <ns>102</ns>
    <id>23815</id>
    <revision>
      <id>4656174</id>
      <parentid>4630233</parentid>
      <timestamp>2026-08-03T08:01:47Z</timestamp>
      <contributor>
        <username>Jdlrobson</username>
        <id>563339</id>
      </contributor>
      <origin>4656174</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3834" sha1="3mepwkt1391rxtn80xbh008j3a7vw7h" xml:space="preserve">__NOTOC__

{{Recipe summary
| Category = Beverage recipes
| Yield = 1 pot of tea
| Servings = 
| Time = 15 minutes
| Difficulty = 1
| Image = [[File:Nice Cup of Tea.jpg|300px]]
}}
{{nutritionsummary|1 cup (250 ml)|4|26|3|0.3 g|0.2 g|1 mg|6 mg|4.8 g|0 g|4.7 g|0.4 g|0%|0%|1%|0%}}
{{recipe}} | [[Cookbook:Beverages|Beverages]] | [[Cookbook:Cuisine_of_the_United_Kingdom|Cuisine of the United Kingdom]]

'''A nice cup of tea''' is the usual answer in [[Cookbook:Cuisine of the United Kingdom|Britain]] and [[Cookbook:Cuisine of Ireland|Ireland]] to any everyday problem. Nothing is so bad that a nice cup of [[Cookbook:Tea|tea]] with a friend or family member can't make it better.

==Ingredients==

* 32 fl oz (1 L) hot [[Cookbook:Water|water]]
* 3–5 measures of loose [[Cookbook:Tea|tea]] leaves or 3–5 tea bags
* [[Cookbook:Sweeteners|Sweetener]], such as [[Cookbook:Sugar|sugar]] or [[Cookbook:Honey|honey]], to taste
* [[Cookbook:Milk|Milk]] or [[Cookbook:Lemon|lemon juice]] to taste

==Procedure==

# Pour freshly-drawn water into a tea kettle, and heat it to your desired temperature. An electric kettle is fast and convenient.
# Pour some hot tap water into your teapot and let stand for about several seconds to a minute to pre-warm it. Alternately, you can swish some of the hotter boiling water from your kettle around in the teapot for a few seconds. Pour out this water before adding the tea to the teapot.
# If using loose tea, place it into an infuser, then into the teapot. If using teabags, place them into the teapot.
# When the water reaches the preferred temperature, pour it from the tea kettle into the teapot. As you pour, try to avoid pouring directly onto the tea (especially important for green and white teas) to avoid scalding the leaves.
# Allow the tea to infuse quietly (i.e. do not stir the teapot or &quot;dunk the teabag&quot;). Agitating the tea releases more of the bitter compounds and degrades the taste. Watch the time to avoid over-infusion, and remove the infuser or tea bag when the time is up.
# Pour tea into your cup(s). Add sweetener and milk or lemon to taste.

== Notes, tips, and variations ==

* You can also prepare a single cup of tea at once by placing a single measure of tea directly into the serving cup.
* Commonly one-half to one tea measure (or rounded teaspoon if you do not have a tea measure) is added per desired cup of tea. Some people add an extra measure &quot;for the pot&quot; (e.g., if 4 cups of tea are desired, 5 measures of tea would be used. It really is a matter of personal preference.)
* Remember that the tannins in tea stain, so it is advisable to pour the tea over a non-staining surface, wipe up any spills quickly, and not leave tea standing in a teapot for long periods of time.
* Never combine milk and lemon in the same cup of tea or the milk will curdle into lumps.
* If you are using an infuser, be sure it is closed tightly so the tea does not spill into the pot. Rinse the tea-filled infuser briefly under cool tap water to wash away tiny flakes that would otherwise drift into the teapot.
* If using a filter basket infuser, do not overfill the basket (refer to the instructions that came with your basket). The brief rinse is usually not necessary unless the basket's mesh is quite porous.
* Simply dropping loose tea into the teapot is also an option, though you may want to strain the tea as you pour it into the cups.
* See [[Cookbook:Tea|the page on tea]] for additional considerations.
[[Category:Irish recipes]]
[[Category:English recipes]]
[[Category:Recipes using tea]]
[[Category:Naturally gluten-free recipes]]
[[category:Vegetarian recipes]]
[[Category:Easy recipes]]
[[Category:Recipes for tea and tisanes]]
[[Category:Recipes using lemon juice]]
[[Category:Recipes using cow milk]]
[[Category:Kosher for Passover recipes]]
[[Category:Halal recipes]]</text>
      <sha1>3mepwkt1391rxtn80xbh008j3a7vw7h</sha1>
    </revision>
  </page>
  <page>
    <title>PHP Programming/Setup and Installation</title>
    <ns>0</ns>
    <id>33821</id>
    <revision>
      <id>4656151</id>
      <parentid>4627572</parentid>
      <timestamp>2026-08-03T01:18:38Z</timestamp>
      <contributor>
        <username>Lbocquet</username>
        <id>3618782</id>
      </contributor>
      <origin>4656151</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="12137" sha1="epau5d1m74rrj4xjd5qpe3qradtms01" xml:space="preserve">&lt;noinclude&gt;{{Nav}}&lt;/noinclude&gt;

== Principle ==
Since PHP is a server-side technology, you should naturally expect to invest some time in setting up a server environment for production, development or learning. To be frank, PHP is quite easy to set up compared to other monsters like J2EE.

Nevertheless, the procedures are complicated by the various combinations of different versions of web server, PHP and database (most often MySQL). That's why in a process of learning it's possible to execute some commands on phpfiddle.org or Tutorialspoint, without installing anything.

Below we will introduce the steps needed to set up a working PHP environment with MySQL database on one's machine.

== Linux ==
If your desktop runs on Linux, chances are that Apache, PHP, and MySQL are already installed for you. This wildly popular configuration is commonly referred to as LAMP, i.e. '''L'''inux '''A'''pache '''M'''ySQL '''P'''HP. The latter 'P' can also refer to '''P'''erl, another major player in the open-source web service arena. If some components are not installed, you will likely have to manually install the following packages:
* Apache or lighttpd
* PHP
* MySQL or Postgres
* The PHP integration plugin for the database.

=== Debian or its derivatives ===
On Debian or its derivatives, Ubuntu included{{ref|Ubuntu}}, you can use the corresponding commands:

&lt;syntaxhighlight lang=&quot;bash&quot;&gt;
apt-get install php5

## Server
#### If you wish to use Apache
apt-get install apache2 libapache2-mod-php5
a2enmod php5
service apache2 restart
## -or-
#### If you wish to use lighttpd
apt-get install lighttpd php5-cgi
lighttpd-enable-mod fastcgi fastcgi-php
service lighttpd restart

## Database
#### If you wish to use Postgres
apt-get install postgres-server    postgres-client    php5-pg
## -or-
#### If you wish to use Mysql
apt-get install mysql-server       mysql-client       php5-mysql
&lt;/syntaxhighlight&gt;

{{note|Ubuntu}} If you chose to use Ubuntu with Apache and MySQL you might wish to utilize the Ubuntu community site for such a configuration [https://help.ubuntu.com/community/ApacheMySQLPHP ubuntu lamp wiki].

=== Gentoo ===
For Gentoo Linux users, the official wiki has this HowTo available: [https://wiki.gentoo.org/wiki/Apache Apache with PHP].

In general, you'll want to do the following under Gentoo:
&lt;syntaxhighlight lang=&quot;bash&quot;&gt;
emerge apache
emerge mysql
emerge mod_php
&lt;/syntaxhighlight&gt;

=== RPM-based ===
The exact procedures depend on your Linux distribution. On a Fedora system, the commands are typically as follows:
&lt;syntaxhighlight lang=&quot;bash&quot;&gt;
yum install httpd
yum install php
yum install mysql
yum install php-mysql
&lt;/syntaxhighlight&gt;

It's impossible to cover all the variants here, so consult your Linux distribution's manual for more details, or grab a friend to do it for you.

One sure-fire way of getting PHP up and running on your *nix system is to compile it from source. This isn't as hard as it may sound and there are good instructions available in the [http://au.php.net/manual/en/install.unix.php PHP manual].

== Windows ==
PHP on Windows is also a very popular option. On a Windows platform, you have the option to use either the open source [https://httpd.apache.org/ Apache] web server, or the native Internet Information Services (IIS) server from Microsoft, which can be installed by searching the start menu or control panel for 'Turn Windows Features On or Off' (Windows 7, 8, 10), or via Windows CD on older installations. When you have one of these servers installed, you can download and install the appropriate PHP Windows binaries distributions from the [https://www.php.net/downloads.php PHP download page]. The installer version requires less user-interaction.

For increased performance you will want to use FastCGI. There is a wikibook that will assist you on [[IIS and FastCGI|Setting up IIS with FastCGI]].

=== Databases ===
On Microsoft Windows you must always install your own database.  

Some popular choices are the open source Postgres, SQLite, and MySQL. Postgres and SQLite are more liberally licensed, and are free to use for commercial purposes.SQLite is solely an embedded database, similar to Microsoft Access, and is hosted on the same application server as the PHP instance or applications that are referencing it, whereas MySQL and Postgres are typically used a database server that may be connected to by many machines at once.  

==== PostgreSQL ====
Official Zend documentation: [https://www.php.net/pgsql https://www.php.net/pgsql]

PostgreSQL is simple and easy to install, browse to [https://www.postgresql.org/download/ https://www.postgresql.org/download/] and download the exe and double-click.

==== MySQL ====
Official MySQL documentation: [https://www.php.net/manual/en/mysql.php https://www.php.net/manual/en/mysql.php]

You might wish to install the MySQL database. You can download the Windows version of [https://dev.mysql.com/downloads/mysql/ MySQL], and follow the installation instructions. If you have PHP 4, you do not need to install the equivalence of php-mysql on Linux, as MySQL support is built-in in Windows distributions of PHP. In PHP 5 you will need to uncomment the following line in your php.ini file (that is, remove the ';' at the beginning of the line):
&lt;syntaxhighlight lang=&quot;ini&quot;&gt;
  ;extension=php_mysql.dll
&lt;/syntaxhighlight&gt;

=== Bundled Package ===
If you find all the above too much a hassle, you have another option. Driven by the eternal desire to do things the safe/easy way, several conveniently packaged AMP bundles of Apache/MySQL/PHP can be found on the net. One of them is [https://sourceforge.net/projects/phptriad/ PHPTriad]. Or, you can try [https://www.uniformserver.com/ Uniform Server]. It is a small [[WAMP]] Package. (The acronym ''WAMP'' refers to a server stack where Microsoft Windows is the operating system, Apache is the Web server, MySQL handles the database components, and PHP, Python, or PERL represents the dynamic scripting languages). Uniformserver is packaged as a self-extracting zip archive, and is easy to use. After trying it out you can simply delete the directory and everything is clean.
[https://www.apachefriends.org/ XAMPP for Windows] is another WAMP server that is easy to use. In addition, it has an installation option that allows you to install it on a computer if you have administration rights. XAMPP has options to run PERL and JAVA (on a tomcat server). A number of other portable Windows AMP package choices are summarized at [https://www.portablefreeware.com/?sc=125 List of portable Web Servers].

Also, a package installer called '''WampServer''' is available. It simply installs Apache, PHP and MySQL on windows with ease.&lt;ref&gt;[https://www.wampserver.com/en/ WampServer]&lt;/ref&gt;

=== Easy Windows Setup Instructions ===
1) PHP authoring environment
* Any text editor will do, but I recommend one with syntax coloring especially for someone new to coding or PHP. Notepad++ is my favorite so far with its ease of use, customizability and the ability to collapse tags. All editor help will be in reference to Notepad++
* Install Notepad++. Download the binary file from here: https://notepad-plus-plus.org/

2) PHP running environment
* Now that you have the ability to create and save PHP files you need an environment that can process them and generate the output that your browser displays. There are two ways to accomplish this.
# Get a web host that supports PHP and upload your files every time you make a change.
# Use your own computer as a personal server with PHP support, and only upload final versions to a web host.
* Accomplishing 2. above is actually easier than you think (assuming you are running Windows).
# Download The uniform server. Here is the link to the latest version: https://sourceforge.net/projects/miniserver/files/
# Run the self-extractor UniServerX_Y_Z.exe. Copy the directory to your &quot;C:&quot; drive so the full path is &quot;C:\UniServer&quot;.
# In the directory where you had it extract hit the &quot;Start.exe&quot; file to get the server running
# Place any files and subfolders you want the server to read and process in the &quot;www&quot; folder.
# Your web browser should open to &quot;http://localhost/index.php&quot;
* Now you have the resources to effectively edit PHP documents and process them on your own computer.
* Here is how to create a test page
# Inside &quot;C:\UniServer\www\&quot;, create a webpage called &quot;test.php&quot;
# Edit &quot;test.php&quot; with Notepad++, and copy the following

&lt;syntaxhighlight lang=&quot;html4strict&quot;&gt;
&lt;!DOCTYPE html PUBLIC &quot;-//W3C//DTD XHTML 1.0 Strict//EN&quot; &quot;http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd&quot;&gt;
&lt;html xmlns=&quot;http://www.w3.org/1999/xhtml&quot;&gt;
&lt;head&gt;
&lt;meta http-equiv=&quot;Content-Type&quot; content=&quot;text/html;charset=utf-8&quot; /&gt;
&lt;title&gt;Test Page&lt;/title&gt;
&lt;meta name=&quot;Description&quot; content=&quot;Test Page&quot; /&gt;
&lt;meta name=&quot;Keywords&quot; content=&quot;Test,Page&quot; /&gt;
&lt;/head&gt;
&lt;body&gt;
&lt;?php
  $string = 'Hello world! &lt;br/&gt;';
  echo $string;
  
  print $string;
  
  printf('%s', $string);  
?&gt;
&lt;/body&gt;
&lt;/html&gt;
&lt;/syntaxhighlight&gt;

#&lt;li value=&quot;3&quot;&gt;Save the webpage as &quot;C:\UniServer\www\test.php&quot;
# Open &quot;http://localhost/test.php&quot; in your web browser to view the page. You should see:
Hello world!&lt;br/&gt;
Hello world!&lt;br/&gt;
Hello world!&lt;br/&gt;
#&lt;li value=&quot;5&quot;&gt;(Optional: Follow these instructions for how to make PHP code work with webpages that end in &quot;.html&quot; in addition to &quot;.php&quot;: [https://www.gidblog.com/parsing-php-in-html-files/ https://www.gidblog.com/parsing-php-in-html-files/])

== macOS ==
macOS comes with Apache server as standard, and enabling it is as simple as checking the box next to 'Personal Web Sharing' in the 'Sharing' section of System Preferences. Once you have done this you can place files in /Library/WebServer/Documents to access them on your server. macOS does come with PHP but the installation lacks any significant quantity of extensions, so if you want any you're going to have to install PHP yourself. You can do this by following the instructions in Apple's [https://www.php.net/manual/en/install.macosx.php doc]. Once you've done one of those, you'll have a server with PHP running on your Mac.

To install MySQL just download and run the [https://dev.mysql.com/downloads/mysql/ macOS installer package] or use [https://www.apachefriends.org/ XAMPP for macOS].

If you use unix or learning it, however, compiling might be the way to go for all three, or just the ones you like. The advantage is that you can choose exactly that extensions you want for PHP and Apache. Also you can choose which versions to compile together. To do this make sure you have the Developer Tools installed. They are shipped with macOS.

= How Do I Know My Setup is Working? =
After you have successfully completed the previous section, it's time to make sure that everything went well. You also get the chance to write your very first PHP scripts! Open your favourite ''plain'' [[w:text editor|text editor]] (''not'' Microsoft Word or another [[wikipedia:word processor|word processor]]), and type the following magical line:
&lt;syntaxhighlight lang=&quot;php&quot;&gt;
 &lt;?php phpinfo(); ?&gt;
&lt;/syntaxhighlight&gt;

Save it as phpinfo.php in your web server's root document directory. If you are using a web hosting server, upload it to the server to where you would place HTML files. Now, open up your web browser, and go to &lt;nowiki&gt;http://localhost/phpinfo.php&lt;/nowiki&gt;, or &lt;nowiki&gt;http://your-web-hosting-server.tld/phpinfo.php&lt;/nowiki&gt; if you are using a web hosting server, and look at the output.

Now scroll down that page and make sure there is a table with the title &quot;mysql&quot;, and the top row should read: &quot;MySQL support: enabled&quot;. If your output does not have this, your particular installation of PHP does not have MySQL support enabled. Note that this test doesn't tell you whether MySQL server is running. You should fire up your MySQL client and check before you proceed.

Some dedicated php or script editors even have color coding of different words that can be very useful for finding mistakes. A free implementation of this is the powerful Notepad++, available from [https://notepad-plus-plus.org/ website] and licensed under the GPL.

== Notes ==
{{reflist}}

{{Nav}}</text>
      <sha1>epau5d1m74rrj4xjd5qpe3qradtms01</sha1>
    </revision>
  </page>
  <page>
    <title>Slovio/Alphabet and pronunciation</title>
    <ns>0</ns>
    <id>33888</id>
    <revision>
      <id>4656093</id>
      <parentid>3426376</parentid>
      <timestamp>2026-08-02T19:28:50Z</timestamp>
      <contributor>
        <username>~2026-42786-37</username>
        <id>3618742</id>
      </contributor>
      <comment>/* Lesson 1 - Alphabet and pronunciation */ FOOT was listed as an example for the U sound, but that make a schwa in English. Corrected to HOOT which is a U sound.</comment>
      <origin>4656093</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3298" sha1="41moq4dq3sqp1zrrbbzj89uqwj13091" xml:space="preserve">{{Slovio}}

=Lesson 1 - Alphabet and pronunciation=
The Slovio language can be written either using Latin alphabet based on English, which is purely ASCII, or using a cyrillic alphabet, which is based on Russian. This guide will mostly use the Latin alphabet for simplicity and not to overwhelm learners, but you should familiarize yourself with cyrillic as well. This is the basic Slovio alphabet, both in Latin and the corresponding cyrillic:

 A  B  C  Cx  D  E  F  G  H  I  J  K  L  M  N  O  P  R  S  Sx  T  U  V  Z  Zx
 А  Б  Ц  Ч   Д  Е  Ф  Г  Х  И  Й  К  Л  М  Н  О  П  Р  С  Ш   Т  У  В  З  Ж

 a  b  c  cx  d  e  f  g  h  i  j  k  l  m  n  o  p  r  s  sx  t  u  v  z  zx
 а  б  ц  ч   д  е  ф  г  х  и  й  к  л  м  н  о  п  р  с  ш   т  у  в  з  ж

cx, sx, and zx are always represented by two characters in conjunction and form only one letter each.

&lt;div style=&quot;width:25%;font-size:x-small;float:right; border:1px solid black;padding:0.5em;background:#FFFFE5&quot;&gt;
&lt;span style=&quot;color:orange;font-weight:bold;font-size:large&quot;&gt;! TIP&lt;/span&gt;&amp;nbsp;Russian, Serbo-Croatian, Czech, Slovak and Polish speakers
* '''cx'''  = '''ч, č, cz''' 
* '''sx'''  = '''ш, š, sz'''
* '''zx'''  = '''ж, ž, ż'''  
* '''gx'''  = '''дж, џ, dž, dż'''
* '''wx'''  =  '''щ, шт, шј, št, ś, ć, šč, szcz'''
&lt;/div&gt;

Vowels are pronounced the same way they would be in German or  Polish.

{|cellpadding=2 cellspacing=0 border=0
|'''a''' || - || c'''a'''r
|-
|'''e''' || - || b'''e'''t
|-
|'''i''' || - || s'''ee'''
|-
|'''o''' || - || b'''o'''ld
|-
|'''u''' || - || h'''oo'''t
|}

Consonant pronunciation:

{|cellpadding=2 cellspacing=0 border=0
|'''b''' || - || '''b'''old
|-
|'''c''' || - || ca'''ts'''
|-
|'''cx''' || - || '''ch'''eese
|-
|'''d''' || - || '''d'''og
|-
|'''f''' || - || '''f'''ood
|-
|'''g''' || - || '''g'''old
|-
|'''h''' || - || '''h'''ome
|-
|'''j''' || - || '''y'''es
|-
|'''k''' || - || '''k'''ing
|-
|'''l''' || - || '''l'''etter
|-
|'''m''' || - || '''m'''oon
|-
|'''n''' || - || '''n'''oon
|-
|'''p''' || - || '''p'''encil
|-
|'''r''' || - || '''r'''oll
|-
|'''s''' || - || '''s'''un
|-
|'''sx''' || - || '''sh'''oe
|-
|'''t''' || - || '''t'''eam
|-
|'''v''' || - || '''v'''anilla
|-
|'''z''' || - || '''z'''oo
|-
|'''zx''' || - || plea'''s'''ure
|}

As in most Slavic languages, '''r''' should be rolled. 

'''J''' is used only in some cases:
# When '''j''' sound is at the beginning of the word.
# In suffixes like ''-ju'', ''-just'', etc.

Otherwise, '''i''' is used to represent that sound.

Slovio also includes several optional letters, mainly for expressing sounds of foreign words:
:Gx  Wx  X
:Дж  Щ   Кс

'''Gx''' is used to present the sound that would be formed by &quot;dzx&quot;, as in '''''G'''eor'''g'''e''. '''Wx''' is used to present the &quot;sxcx&quot; sound, as in ''Yu'''shch'''enko''. '''X''', if used apart from '''cx''', '''sx''' or '''zx''', is equivalent to &quot;ks&quot;, as in ''bo'''x'''''.

== Pronunciation and stresses ==

In cases of vowel combination (like ''ai'', ''oi'', ''io'', ''uo'', etc.) it is recommended to pronounce the combination as one diphthong. 

It is recommended to accent the penultimate syllable (the syllable before the last one).

{{Slovio}}

[[sk:Slovio: Abeceda a výslovnosť]]

{{BookCat}}</text>
      <sha1>41moq4dq3sqp1zrrbbzj89uqwj13091</sha1>
    </revision>
  </page>
  <page>
    <title>Muggles' Guide to Harry Potter/Books/Philosopher's Stone/Chapter 4</title>
    <ns>0</ns>
    <id>35826</id>
    <revision>
      <id>4656140</id>
      <parentid>4308425</parentid>
      <timestamp>2026-08-02T23:56:10Z</timestamp>
      <contributor>
        <username>Nasdn2</username>
        <id>3595259</id>
      </contributor>
      <origin>4656140</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="11090" sha1="auogq9xmc7eihoral445qxzuqsbre1c" xml:space="preserve">{{Muggles' Guide to Harry Potter/Book/Page|prev=Chapter 3|next=Chapter 5|tab=4|title=The Keeper of the Keys}}
== Synopsis ==

{{spoiler}}

BOOM! The loud knocking continues outside the door. [[Muggles' Guide to Harry Potter/Characters/Vernon Dursley|Vernon]] rushes in with a rifle as the door is smashed in. A huge man with a bearded face enters. He twists Uncle Vernon's gun barrel like a pretzel, sits down and wishes [[Muggles' Guide to Harry Potter/Characters/Harry Potter|Harry]] a happy birthday, then gives him a squashed cake. The giant makes himself at home, starts a fire, makes tea and cooks sausages. He introduces himself as [[Muggles' Guide to Harry Potter/Characters/Rubeus Hagrid|Rubeus Hagrid]], Keeper of Keys and Grounds at Hogwarts. Hagrid is dismayed that the Dursleys revealed nothing to Harry about his past or about his parents and furious that Harry was told that his mother and father died in a car crash. Hagrid explains that Harry is a wizard — a very famous wizard, in fact. He presents Harry his letter, now addressed to him at the shack. The letter invites Harry to attend [[Muggles' Guide to Harry Potter/Places/Hogwarts School of Witchcraft and Wizardry|Hogwarts School of Witchcraft and Wizardry]].

Hagrid sends an owl to [[Muggles' Guide to Harry Potter/Characters/Albus Dumbledore|Professor Dumbledore]], saying he found Harry and will take him to get his school supplies. [[Muggles' Guide to Harry Potter/Characters/Petunia Dursley|Petunia]] begins ranting, and Harry learns that she and Uncle Vernon have always known about his past. Hagrid tells Harry about a Dark wizard named [[Muggles' Guide to Harry Potter/Characters/Lord Voldemort|Voldemort]] (though Hagrid seems to have enormous difficulty saying the name, apparently afraid), who ten years ago (when Harry was only one-year-old) tracked down and murdered Harry's parents, [[Muggles' Guide to Harry Potter/Characters/James Potter|James]] and [[Muggles' Guide to Harry Potter/Characters/Lily Potter|Lily Potter]]. He also tried to kill Harry but failed and left Harry the scar on his forehead. When asked what happened to Voldemort, Hagrid tells Harry no one is certain, but something happened to him (on the Halloween night he tried to kill Harry) that drove him into hiding.

Harry questions whether he is really a wizard, but Hagrid asks whether he has ever made things happen when angry or scared. Harry remembers things he had done, most recently the boa constrictor, and smiles. Uncle Vernon interrupts, saying Harry is not attending a magic school. Harry is angry that his aunt and uncle knew he was a wizard, as were his parents, and that they lied about how James and Lily died. Vernon refuses to pay for the school and then insults Albus Dumbledore, calling him &quot;some crackpot old fool&quot;. Hagrid, infuriated, uses his umbrella to give [[Muggles' Guide to Harry Potter/Characters/Dudley Dursley|Dudley]] a pig's tail. The Dursleys scramble into the other room, terrified. Hagrid asks Harry to avoid mentioning to anyone at Hogwarts that he performed magic, as he is forbidden to use it, though he was allowed to use some only while on his mission to retrieve Harry. Hagrid explains that he was expelled from Hogwarts during his third year, though he changes the subject when Harry questions him further. It is late, and Hagrid says they have much to do the next day. At that, they go to sleep, Hagrid on the couch, Harry under Hagrid's huge coat on the floor.

== Analysis ==

Without realizing it, Harry has reached the most significant milestone in his life thus far: his 11th birthday. Hagrid's arrival on that day not only liberates Harry from his miserable existence, it has given him knowledge about himself that, though he may have realized later, he never had imagined before. He is also empowered to stand up against the abusive Dursleys—forever altering their relationship; from here on, his life will never be the same. Now Harry is empowered to make choices that will determine his destiny. He alone decides whether to stay with the Dursleys or attend Hogwarts, leaving behind the Muggle world where he subconsciously felt he never belonged. By choosing Hogwarts, Harry shows his budding maturity and independence and a new ability to chart his life's course. Later in the series, Harry develops a reluctance to put his faith in the unknown, but this time he unhesitatingly believes this is his true path and that nothing could be worse than what he already must endure. He trusts Hagrid to lead him on those first tentative steps. Harry is livid that his aunt and uncle hid the truth, as adults often do to protect children, though the Dursleys were entirely spurred by hate and resentment rather than any attempt to shield a child from something unpleasant or hurtful. The obstinate Dursleys' refusal to allow Harry to attend Hogwarts is clearly intended to deny him what they know he wants most. Even though the Dursleys detest Harry's presence, and his departure would alleviate much-unwanted responsibility for his care, they want to keep him at home purely to be spiteful. However, Petunia may have an additional reason: jealousy. This time, however, the choice is Harry's alone, and he opts to leave the Muggle world (and the Dursleys) behind, though we expect he will periodically revisit Privet Drive at vacations and other times when the school is closed until he reaches adulthood.

As an astonished Harry learns about his true past and how his parents actually died, we discover more about what happened the night Lord Voldemort came to [[Muggles' Guide to Harry Potter/Places/Godric's Hollow|Godric's Hollow]]. Despite being defeated ten years before, we sense the dread most wizards feel for Voldemort or even the terror his name alone evokes. This lingering apprehension indicates that the Wizarding world may still be uncertain whether Voldemort is truly dead and whether he can or will return. Harry lacks this fear, perhaps because he was never conditioned to it as other Wizards have been over the years. Instead, he comes to consider Voldemort as his foe, but not an invincible one.

These books' central themes are prejudice, divisiveness, and fear of the unknown. This chapter, particularly Petunia's tirade, shows a biased view from the Muggle side of the Muggle-Magic divide toward anything that is seemingly strange or different. The Dursleys' behaviour is also a classic example showing how human ignorance and fear tend to go hand-in-hand. In a vicious circle, their ignorance perpetually causes them to be frightened by magic, while that fear prevents them from developing a better understanding of it. In contrast, Harry's willingness to accept his magical nature when the evidence is presented and his intuitiveness regarding his abilities indicate his open-mindedness.

== Questions ==
{{Muggles' Guide to Harry Potter/Questions}}

=== Review ===
#Why did Aunt Petunia and Uncle Vernon hide the truth about the deaths of James and Lily Potter?
#Why might Uncle Vernon and Aunt Petunia want to hide the truth from Harry?
#What does this chapter say about Aunt Petunia's character?
#What is the significance of Harry being given a birthday cake?
#Why did Hagrid give Dudley a pig's tail?

=== Further Study ===
#Why is Hagrid afraid to speak Voldemort's name?
#Why does Petunia seem to hate her sister, Lily?
#Can the Dursleys stop Harry from attending Hogwarts, and do they have the right to? Explain why or why not.
#Why might Hagrid have been expelled from Hogwarts? Why is he trusted with fetching Harry?
#Why were the Potters murdered?

== Greater Picture ==

{{Muggles' Guide to Harry Potter/Intermediate Spoiler}}

This chapter briefly mentions Hagrid's expulsion from Hogwarts, a critical plot element in the next book, [[Muggles' Guide to Harry Potter/Books/Chamber of Secrets|''Harry Potter and the Chamber of Secrets'']].

Hagrid's fear of speaking Voldemort's name aloud will be echoed throughout the series, with people referring to him as &quot;the Dark Lord,&quot; &quot;You-know-who&quot;, and &quot;He who must not be named&quot;, as well as other variants. This dread, though constant, is significantly reinforced in [[Muggles' Guide to Harry Potter/Books/Deathly Hallows|the seventh book]] when Voldemort places a taboo on his name, such that anyone uttering it is immediately detected and subjected to reprisals. The taboo is generally aimed at those fighting him, as they are among the few who dare speak his name, especially at Harry Potter, who has become public enemy number one under Voldemort's new regime. While only speculated, a similar taboo could have existed during Voldemort's initial reign and engendered a fear of his name among the Wizarding populace. By contrast, Harry is also known by a different moniker, &quot;the Boy Who Lived&quot; (and later, &quot;the Chosen One&quot;), though none in the Wizarding world fear using his real name.

Petunia's tirade is meant to show how Muggles fear and disdain what they cannot fully understand. While this becomes a recurring theme in the series, Petunia's reaction is actually motivated by jealousy that her sister, Lily, is a witch while she is not. After Lily received her Hogwarts letter, Petunia also desperately wanted to attend but lacking any magical ability, she was forced to remain behind in the Muggle world. To console herself, she became convinced that Lily was a freak and that the Wizarding world and anything or anyone tied to it is &quot;abnormal&quot;, and she resolved to be as opposite from that as possible; she has since inflicted her bitter resentment and animosity onto Harry, and her refusal to allow her nephew to attend Hogwarts is a feeble attempt to deny him what she was unable to have. Fortunately, it is Harry's decision alone whether or not he will attend the school.

By learning his true nature, Harry has taken the first step on the path leading to his eventual destiny. He will continue on it throughout the series, with some occasional setbacks.s.

=== Connections ===

*Petunia's hatred of her sister and fear of magic is introduced. It will reappear in each book in turn, though less pronounced than here until finally the reason is revealed in [[Muggles' Guide to Harry Potter/Books/Deathly Hallows/Chapter 33|the final book of the series]].

*Ron will echo Hagrid's fear of mentioning Voldemort's name in [[Muggles' Guide to Harry Potter/Books/Deathly Hallows/Chapter 14|''Harry Potter and the Deathly Hallows'']]. [[Muggles' Guide to Harry Potter/Books/Deathly Hallows/Chapter 20|We will discover there, also,]] the reason for that fear.

*This is the first instance where we see the Wizarding mail system, owl post, being used. This recurs throughout the series.

*The facts behind Hagrid's expulsion will be revealed in [[Muggles' Guide to Harry Potter/Books/Chamber of Secrets/Chapter 13|''Harry Potter and the Chamber of Secrets'']]. [[Muggles' Guide to Harry Potter/Books/Chamber of Secrets/Chapter 15|Shortly after that,]] we understand why Dumbledore rejected the reasoning that resulted in Hagrid's expulsion and now trusts him with important school-related errands.</text>
      <sha1>auogq9xmc7eihoral445qxzuqsbre1c</sha1>
    </revision>
  </page>
  <page>
    <title>Do-It-Yourself/Campfire</title>
    <ns>0</ns>
    <id>48756</id>
    <revision>
      <id>4656052</id>
      <parentid>3718408</parentid>
      <timestamp>2026-08-02T15:51:34Z</timestamp>
      <contributor>
        <username>Devonmcluskie</username>
        <id>3618588</id>
      </contributor>
      <origin>4656052</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="14559" sha1="19bfv2wh61n1nq8449v4hqarx4wwe8n" xml:space="preserve">organicatvely A campfire is organicatively ա organicatively fire lit at a campsite, usually in a fire ring. Campfires are a popular feature of camping, particularly among organized campers such as Scouts, Guides or Royal Rangers. Without proper precautions they are also potentially dangerous. A certain degree of skill is needed to properly build a campfire, to keep it going, and to see that it is properly extinguished.

==The dangers==
A campfire may burn out of control in two basic ways: on the ground or in the trees. Dead leaves or pine needles on the ground may ignite from direct contact with burning wood, or from thermal radiation. Alternatively, airborne embers (or their smaller kin, sparks) may ignite dead material in overhanging branches. This latter threat is less likely, but a fire in a branch will be virtually impossible to put out without firefighting equipment, and may spread more quickly than a ground fire.

Embers may simply fall off of logs and be carried away by the air, or they may be ejected at high speed by exploding pockets of sap. With these dangers in mind, some places prohibit all open fires, particularly during times of the year that are prone to wildfires.

Campfires are prohibited in many public camping areas. Public areas with large tracts of woodland usually have signs indicating the level of fire danger, which usually depends on recent rain and the amount of deadfalls or dry debris; when the danger is highest, all open fires are prohibited. Even in safer times, it is common to require registration and permits to build a campfire. Such areas are often kept under observation by rangers, who will dispatch someone to investigate any unidentified plume of smoke.

==Finding a site, and other safety measures==
Ideally, every fire should be lit in a fire ring. If a fire ring is not available, a temporary fire site may be constructed. One way is to cover the ground with sand, or other soil mostly free of flammable organic material, to a depth of a few centimeters. The area of sand should be large enough to safely contain the fire and any pieces of burning wood that may fall out of it. Sand piles should be scattered after the fire has been put out. If the topsoil is moist, it may suffice to simply clear it of any dead plant matter.
Fire rings, however, do not fully protect material on the ground from catching fire. Flying embers are still a threat, and the fire ring may become hot enough to ignite material in contact with it.

No fire should be lit close to trees, tents or other fire hazards. This includes overhanging branches; some carry dead, dry material that can ignite from a single airborne ember. In addition, a fire may harm any roots under it, even if they are protected by a thin layer of soil. Conifers run a greater risk of root damage, because they lack taproots and their roots run close to the surface.

Fires also should not be lit on bare rocks. The ash will leave a black stain that cannot be easily removed, but the fire's heat can lead to more dramatic consequences. It will cause the outer layer of the rock to expand, possibly causing it to crack. It may also boil pockets of water contained in the rock.

An additional safety measure is to have sand and water on hand to smother and douse the fire if it does get out of the fire pit. It is wise to gather these materials before they are actually needed.

==Types of fuel==
There are, by conventional classification, three types of material involved in building a fire without manufactured fuels.
*Tinder is anything that can be lit with a match. The best natural tinder is dead, dry pine needles or grass; a more comprehensive list is given in the article on tinder. A quantity of tinder sufficient to fill one's cupped hands to the top is the bare minimum needed.
*Kindling is an arbitrary classification including anything bigger than tinder but smaller than fuelwood. In fact, there are gradations of kindling, from sticks thinner than a finger to those as thick as a wrist. A quantity of kindling sufficient to fill a hat may be enough, but more is better.
*Fuelwood ranges from small logs two or three inches across to larger logs that can burn for hours. It is typically impossible to gather without a hatchet or other cutting tool, so fuelwood must usually be brought from home or purchased at a nearby store.

The gathering of fuel in natural areas is often restricted. Cutting of living trees is almost always forbidden - but neither is it very useful, because sap-filled wood does not burn well. Squaw wood (dead parts of standing trees) may also be prohibited. Wood lying on the ground is usually permitted.

==Building the fire==
Having found a suitable site and gathered materials, the fire-builder has a variety of designs to choose from. A good design is very important in the early stages of a fire. Most of them make no mention of fuelwood - in most designs, fuelwood is never placed on a fire until the kindling is burning strongly.

The tipi fire-build is perhaps the best, but it is takes some patience to construct. First, the tinder is piled up in a compact heap. The smaller kindling is arranged around it, like the poles of a tipi. For added strength, it may be possible to lash some of the sticks together. A tripod lashing is quite difficult to execute with small sticks, so a clove hitch should suffice. (Synthetic rope should be avoided, since it produces pollutants when it burns.) Then the larger kindling is arranged above the smaller kindling, taking care not to collapse the tipi. A separate tipi as a shell around the first one may work better.

A lean-to fire-build starts with the same pile of tinder as the tipi fire-build. Then, a long, thick piece of kindling is driven into the ground at an angle, so that it overhangs the tinder pile. The smaller pieces of kindling are leaned against the big stick so that the tinder is enclosed between them.

A log cabin fire-build likewise begins with a tinder pile. The kindling is then stacked around it, as in the construction of a log cabin. The first two kindling sticks are laid parallel to each other, on opposite sides of the tinder pile. The second pair is laid on top of the first, at right angles to it, and also on opposite sides of the tinder. More kindling is added in the same manner. The smallest kindling is placed over the top of the assembly. Of all the fire-builds, the log cabin is the least vulnerable to premature collapse, but it is also inefficient, because it makes the worst use of convection to ignite progressively larger pieces of fuel.

A variation on the log cabin starts with two pieces of fuelwood with a pile of tinder between them, and small kindling laid over the tops of the logs, above the tinder. The tinder is lit, and the kindling is allowed to catch fire. When it is burning briskly, it is broken and pushed down into the consumed tinder, and the larger kindling is placed over the top of the logs. When that is burning well, it is also pushed down. Eventually, a pile of kindling should be burning between two pieces of fuelwood. The logs will eventually catch fire from it.
Another variation is called the funeral pyre method because it is used for building funeral pyres. Its main difference from the standard log cabin is that it starts with thin pieces and moves up to thick pieces. If built on a large scale, this type of fire-build collapses in a controlled manner without restricting the air flow.

The traditional Finnish rakovalkea (literally &quot;slit bonfire&quot;) is constructed by placing one long piece of fuelwood atop another, parallel and bolstering them in place with four sturdy posts driven into the ground. (Traditionally, whole unsplit tree trunks are used for the fuelwood.) Kindling and tinder are placed between the logs in sufficient quantity (while avoiding the very ends) to raise the upper log and allow ventilation. The tinder is always lit at the center so the bolstering posts don't burn prematurely. The rakovalkea has two excellent features. First, it burns slowly but steadily when lit; it doesn't require arduous maintenance, but burns for a very long time. A well constructed rakovalkea of two thick logs of two meters in length can warm two lean-to shelters for a whole sleeping shift. The construction means that the logs themselves act as wind-cover! Thus, exposure to smoke is unlikely for the sleepers; nevertheless someone should always watch in case of an emergency. Second, it can be easily scaled to larger sizes (for a feast) limited only by the length of available tree trunks.

==Lighting the fire==
[[Image:Campfire_4213.jpg|thumb|280px|left|A campfire]]
Once the fire is built, the next step is to light the tinder, using either a match or a lighter. A reasonably skillful fire-builder using reasonably good material will only need one match. The tinder will burn brightly, but be reduced to glowing embers within half a minute. If the kindling does not catch fire, the fire-builder must gather more tinder, determine what went wrong and try to fix it.

One of five problems can prevent a fire from lighting properly: wet wood, wet weather, too little tinder, too much wind, or a lack of oxygen. Rain will, of course, douse a fire, but a combination of wind and fog also has a stifling effect. Metal fire rings generally do a good job of keeping out wind, but some of them are so high as to impede the circulation of oxygen in a small fire. To make matters worse, these tall fire rings also make it very difficult to blow on the fire properly.

Steady, forceful blowing may be in order for a small fire in an enclosed space that has mysteriously slowed down, but blowing may extinguish a fire if it is done abruptly or when it is not needed. Most large fires easily create their own circulation, even in unfavorable conditions, but the variant log-cabin fire-build suffers from a chronic lack of air so long as the initial structure is maintained.

Once the large kindling is burning, all of the kindling should be put on the fire, save for one piece at least a foot long. This piece is useful later to push pieces of fuelwood where they are needed. Once all of the kindling is burning, the fuelwood should be placed on top of it (unless, as in the rakovalkea fire-build, it is already there). For best results, two or more pieces of fuelwood should be leaned against each other, as in the tipi fire-build.

===Without matches===
There are several ways to light a fire without any matches. All of them work with only the lightest and most flammable tinder, such as paper.

On a sunny day, a lens may be used to focus the light onto the tinder. The most suitable lenses are magnifying glasses (included in some compasses), but eyeglasses may also suffice.

The &quot;bow and drill&quot; method is also well-known, but it is a lot of work. The bow is similar to that used for archery. To make such a bow, find a thin rope or flexible but sturdy vine, and a sturdy stick about two feet long. Tie the rope to one end of the stick, and make another knot on the other end of the stick, with the rope between the ends not quite taut. The drill is another straight stick, thin but strong, preferably stripped of bark and with a sharpened end. The center of the bowstring (rope) is wrapped around the drill, with the two sticks at right angles to each other. The end of the drill is placed on a piece of bark in the middle of the tinder. The bow is moved rapidly back and forth to rotate the drill and create heat and friction on the bark. This method works best with an assistant feeding the tinder to the hot spot.

The crudest method of igniting a fire is to strike two hard objects (at least one of them combustible) together to produce a spark, and ignite tinder from the spark. The substances traditionally used to produce sparks are flint and either steel or pyrite. Replacing the steel with ferrocerium (lighter &quot;flint&quot;) produces more sparks with less effort. Rotting wood (punkwood) or charred fuel are sometimes used as tinder when using this method.

==Campfire activities==
[[Image:Cooking snags over campfire.jpg|thumb|250px|Australian &quot;snags&quot; cooking on a campfire]]

Campfires have been used for cooking since time immemorial. However, portable stoves have all but replaced campfires in this regard. For cooking information, see cooking on a campfire. Other practical, though not commonly needed, applications for campfires include drying wet clothing, alleviating hypothermia and use as a distress signal.

Most campfires, though, are lit exclusively for recreation. People tend to find something fascinating about flames and glowing coals, so a campfire is usually an agreeable way to pass the time from dusk to bedtime, particularly for those in a pensive mood. Campfires are also good venues for intimate conversation and storytelling; yarns and stories about poltergeists are particularly popular.

Another traditional campfire activity involves impaling marshmallows on sticks or uncoiled coat hangers, and roasting them over the fire. Roasted marshmallows may also be used for S'mores.

==Extinguishing the fire==
Leaving a fire unattended is dangerous! Any number of accidents might occur in the absence of people, leading to property damage, personal injury or possibly a wildfire. Ash is a very good insulator, so embers left overnight will only lose a fraction of their heat.

Large amounts of water are indispensable for extinguishing a fire. To properly cool a fire, water should be poured on all the embers, including places that are not glowing red. The water will boil violently and carry ash in the air with it, dirtying anything nearby but not posing a safety hazard. The water should be poured until the hissing noises stop. Then the ashes should be stirred with a stick to make sure that the water has penetrated all the layers; if the hissing continues, more water should be added. A fire is fully extinguished if the ashes are cool to the touch.

If water is scarce, sand may be used. The sand will deprive the fire of oxygen quite well, but it is much less effective than water at absorbing heat. Once the fire has been covered thoroughly with sand, all water that can be spared should be poured on it, and the sand stirred into the ash.

Finally, in lightly-used wilderness areas, it is best to replace anything that was moved while preparing the fire site, and scatter anything that was gathered, so that it looks as natural as possible.


{{BookCat}}


[[ja:&amp;#12461;&amp;#12515;&amp;#12531;&amp;#12503;&amp;#12501;&amp;#12449;&amp;#12452;&amp;#12516;&amp;#12540;]]</text>
      <sha1>19bfv2wh61n1nq8449v4hqarx4wwe8n</sha1>
    </revision>
    <revision>
      <id>4656053</id>
      <parentid>4656052</parentid>
      <timestamp>2026-08-02T15:51:56Z</timestamp>
      <contributor>
        <username>Morkoz</username>
        <id>3607239</id>
      </contributor>
      <minor />
      <comment>Undid edits by [[Special:Contribs/Devonmcluskie|Devonmcluskie]] ([[User talk:Devonmcluskie|talk]]) to last version by Will Sandberg</comment>
      <origin>4656053</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="14514" sha1="kfutni5i2cvgsbpzdxzugtj4saioa0a" xml:space="preserve">A campfire is a fire lit at a campsite, usually in a fire ring. Campfires are a popular feature of camping, particularly among organized campers such as Scouts, Guides or Royal Rangers. Without proper precautions they are also potentially dangerous. A certain degree of skill is needed to properly build a campfire, to keep it going, and to see that it is properly extinguished.

==The dangers==
A campfire may burn out of control in two basic ways: on the ground or in the trees. Dead leaves or pine needles on the ground may ignite from direct contact with burning wood, or from thermal radiation. Alternatively, airborne embers (or their smaller kin, sparks) may ignite dead material in overhanging branches. This latter threat is less likely, but a fire in a branch will be virtually impossible to put out without firefighting equipment, and may spread more quickly than a ground fire.

Embers may simply fall off of logs and be carried away by the air, or they may be ejected at high speed by exploding pockets of sap. With these dangers in mind, some places prohibit all open fires, particularly during times of the year that are prone to wildfires.

Campfires are prohibited in many public camping areas. Public areas with large tracts of woodland usually have signs indicating the level of fire danger, which usually depends on recent rain and the amount of deadfalls or dry debris; when the danger is highest, all open fires are prohibited. Even in safer times, it is common to require registration and permits to build a campfire. Such areas are often kept under observation by rangers, who will dispatch someone to investigate any unidentified plume of smoke.

==Finding a site, and other safety measures==
Ideally, every fire should be lit in a fire ring. If a fire ring is not available, a temporary fire site may be constructed. One way is to cover the ground with sand, or other soil mostly free of flammable organic material, to a depth of a few centimeters. The area of sand should be large enough to safely contain the fire and any pieces of burning wood that may fall out of it. Sand piles should be scattered after the fire has been put out. If the topsoil is moist, it may suffice to simply clear it of any dead plant matter.
Fire rings, however, do not fully protect material on the ground from catching fire. Flying embers are still a threat, and the fire ring may become hot enough to ignite material in contact with it.

No fire should be lit close to trees, tents or other fire hazards. This includes overhanging branches; some carry dead, dry material that can ignite from a single airborne ember. In addition, a fire may harm any roots under it, even if they are protected by a thin layer of soil. Conifers run a greater risk of root damage, because they lack taproots and their roots run close to the surface.

Fires also should not be lit on bare rocks. The ash will leave a black stain that cannot be easily removed, but the fire's heat can lead to more dramatic consequences. It will cause the outer layer of the rock to expand, possibly causing it to crack. It may also boil pockets of water contained in the rock.

An additional safety measure is to have sand and water on hand to smother and douse the fire if it does get out of the fire pit. It is wise to gather these materials before they are actually needed.

==Types of fuel==
There are, by conventional classification, three types of material involved in building a fire without manufactured fuels.
*Tinder is anything that can be lit with a match. The best natural tinder is dead, dry pine needles or grass; a more comprehensive list is given in the article on tinder. A quantity of tinder sufficient to fill one's cupped hands to the top is the bare minimum needed.
*Kindling is an arbitrary classification including anything bigger than tinder but smaller than fuelwood. In fact, there are gradations of kindling, from sticks thinner than a finger to those as thick as a wrist. A quantity of kindling sufficient to fill a hat may be enough, but more is better.
*Fuelwood ranges from small logs two or three inches across to larger logs that can burn for hours. It is typically impossible to gather without a hatchet or other cutting tool, so fuelwood must usually be brought from home or purchased at a nearby store.

The gathering of fuel in natural areas is often restricted. Cutting of living trees is almost always forbidden - but neither is it very useful, because sap-filled wood does not burn well. Squaw wood (dead parts of standing trees) may also be prohibited. Wood lying on the ground is usually permitted.

==Building the fire==
Having found a suitable site and gathered materials, the fire-builder has a variety of designs to choose from. A good design is very important in the early stages of a fire. Most of them make no mention of fuelwood - in most designs, fuelwood is never placed on a fire until the kindling is burning strongly.

The tipi fire-build is perhaps the best, but it is takes some patience to construct. First, the tinder is piled up in a compact heap. The smaller kindling is arranged around it, like the poles of a tipi. For added strength, it may be possible to lash some of the sticks together. A tripod lashing is quite difficult to execute with small sticks, so a clove hitch should suffice. (Synthetic rope should be avoided, since it produces pollutants when it burns.) Then the larger kindling is arranged above the smaller kindling, taking care not to collapse the tipi. A separate tipi as a shell around the first one may work better.

A lean-to fire-build starts with the same pile of tinder as the tipi fire-build. Then, a long, thick piece of kindling is driven into the ground at an angle, so that it overhangs the tinder pile. The smaller pieces of kindling are leaned against the big stick so that the tinder is enclosed between them.

A log cabin fire-build likewise begins with a tinder pile. The kindling is then stacked around it, as in the construction of a log cabin. The first two kindling sticks are laid parallel to each other, on opposite sides of the tinder pile. The second pair is laid on top of the first, at right angles to it, and also on opposite sides of the tinder. More kindling is added in the same manner. The smallest kindling is placed over the top of the assembly. Of all the fire-builds, the log cabin is the least vulnerable to premature collapse, but it is also inefficient, because it makes the worst use of convection to ignite progressively larger pieces of fuel.

A variation on the log cabin starts with two pieces of fuelwood with a pile of tinder between them, and small kindling laid over the tops of the logs, above the tinder. The tinder is lit, and the kindling is allowed to catch fire. When it is burning briskly, it is broken and pushed down into the consumed tinder, and the larger kindling is placed over the top of the logs. When that is burning well, it is also pushed down. Eventually, a pile of kindling should be burning between two pieces of fuelwood. The logs will eventually catch fire from it.
Another variation is called the funeral pyre method because it is used for building funeral pyres. Its main difference from the standard log cabin is that it starts with thin pieces and moves up to thick pieces. If built on a large scale, this type of fire-build collapses in a controlled manner without restricting the air flow.

The traditional Finnish rakovalkea (literally &quot;slit bonfire&quot;) is constructed by placing one long piece of fuelwood atop another, parallel and bolstering them in place with four sturdy posts driven into the ground. (Traditionally, whole unsplit tree trunks are used for the fuelwood.) Kindling and tinder are placed between the logs in sufficient quantity (while avoiding the very ends) to raise the upper log and allow ventilation. The tinder is always lit at the center so the bolstering posts don't burn prematurely. The rakovalkea has two excellent features. First, it burns slowly but steadily when lit; it doesn't require arduous maintenance, but burns for a very long time. A well constructed rakovalkea of two thick logs of two meters in length can warm two lean-to shelters for a whole sleeping shift. The construction means that the logs themselves act as wind-cover! Thus, exposure to smoke is unlikely for the sleepers; nevertheless someone should always watch in case of an emergency. Second, it can be easily scaled to larger sizes (for a feast) limited only by the length of available tree trunks.

==Lighting the fire==
[[Image:Campfire_4213.jpg|thumb|280px|left|A campfire]]
Once the fire is built, the next step is to light the tinder, using either a match or a lighter. A reasonably skillful fire-builder using reasonably good material will only need one match. The tinder will burn brightly, but be reduced to glowing embers within half a minute. If the kindling does not catch fire, the fire-builder must gather more tinder, determine what went wrong and try to fix it.

One of five problems can prevent a fire from lighting properly: wet wood, wet weather, too little tinder, too much wind, or a lack of oxygen. Rain will, of course, douse a fire, but a combination of wind and fog also has a stifling effect. Metal fire rings generally do a good job of keeping out wind, but some of them are so high as to impede the circulation of oxygen in a small fire. To make matters worse, these tall fire rings also make it very difficult to blow on the fire properly.

Steady, forceful blowing may be in order for a small fire in an enclosed space that has mysteriously slowed down, but blowing may extinguish a fire if it is done abruptly or when it is not needed. Most large fires easily create their own circulation, even in unfavorable conditions, but the variant log-cabin fire-build suffers from a chronic lack of air so long as the initial structure is maintained.

Once the large kindling is burning, all of the kindling should be put on the fire, save for one piece at least a foot long. This piece is useful later to push pieces of fuelwood where they are needed. Once all of the kindling is burning, the fuelwood should be placed on top of it (unless, as in the rakovalkea fire-build, it is already there). For best results, two or more pieces of fuelwood should be leaned against each other, as in the tipi fire-build.

===Without matches===
There are several ways to light a fire without any matches. All of them work with only the lightest and most flammable tinder, such as paper.

On a sunny day, a lens may be used to focus the light onto the tinder. The most suitable lenses are magnifying glasses (included in some compasses), but eyeglasses may also suffice.

The &quot;bow and drill&quot; method is also well-known, but it is a lot of work. The bow is similar to that used for archery. To make such a bow, find a thin rope or flexible but sturdy vine, and a sturdy stick about two feet long. Tie the rope to one end of the stick, and make another knot on the other end of the stick, with the rope between the ends not quite taut. The drill is another straight stick, thin but strong, preferably stripped of bark and with a sharpened end. The center of the bowstring (rope) is wrapped around the drill, with the two sticks at right angles to each other. The end of the drill is placed on a piece of bark in the middle of the tinder. The bow is moved rapidly back and forth to rotate the drill and create heat and friction on the bark. This method works best with an assistant feeding the tinder to the hot spot.

The crudest method of igniting a fire is to strike two hard objects (at least one of them combustible) together to produce a spark, and ignite tinder from the spark. The substances traditionally used to produce sparks are flint and either steel or pyrite. Replacing the steel with ferrocerium (lighter &quot;flint&quot;) produces more sparks with less effort. Rotting wood (punkwood) or charred fuel are sometimes used as tinder when using this method.

==Campfire activities==
[[Image:Cooking snags over campfire.jpg|thumb|250px|Australian &quot;snags&quot; cooking on a campfire]]

Campfires have been used for cooking since time immemorial. However, portable stoves have all but replaced campfires in this regard. For cooking information, see cooking on a campfire. Other practical, though not commonly needed, applications for campfires include drying wet clothing, alleviating hypothermia and use as a distress signal.

Most campfires, though, are lit exclusively for recreation. People tend to find something fascinating about flames and glowing coals, so a campfire is usually an agreeable way to pass the time from dusk to bedtime, particularly for those in a pensive mood. Campfires are also good venues for intimate conversation and storytelling; yarns and stories about poltergeists are particularly popular.

Another traditional campfire activity involves impaling marshmallows on sticks or uncoiled coat hangers, and roasting them over the fire. Roasted marshmallows may also be used for S'mores.

==Extinguishing the fire==
Leaving a fire unattended is dangerous! Any number of accidents might occur in the absence of people, leading to property damage, personal injury or possibly a wildfire. Ash is a very good insulator, so embers left overnight will only lose a fraction of their heat.

Large amounts of water are indispensable for extinguishing a fire. To properly cool a fire, water should be poured on all the embers, including places that are not glowing red. The water will boil violently and carry ash in the air with it, dirtying anything nearby but not posing a safety hazard. The water should be poured until the hissing noises stop. Then the ashes should be stirred with a stick to make sure that the water has penetrated all the layers; if the hissing continues, more water should be added. A fire is fully extinguished if the ashes are cool to the touch.

If water is scarce, sand may be used. The sand will deprive the fire of oxygen quite well, but it is much less effective than water at absorbing heat. Once the fire has been covered thoroughly with sand, all water that can be spared should be poured on it, and the sand stirred into the ash.

Finally, in lightly-used wilderness areas, it is best to replace anything that was moved while preparing the fire site, and scatter anything that was gathered, so that it looks as natural as possible.


{{BookCat}}


[[ja:&amp;#12461;&amp;#12515;&amp;#12531;&amp;#12503;&amp;#12501;&amp;#12449;&amp;#12452;&amp;#12516;&amp;#12540;]]</text>
      <sha1>kfutni5i2cvgsbpzdxzugtj4saioa0a</sha1>
    </revision>
  </page>
  <page>
    <title>Cookbook:Gajjar Halwa (Carrot Pudding)</title>
    <ns>102</ns>
    <id>77523</id>
    <revision>
      <id>4656176</id>
      <parentid>4522379</parentid>
      <timestamp>2026-08-03T08:03:38Z</timestamp>
      <contributor>
        <username>Jdlrobson</username>
        <id>563339</id>
      </contributor>
      <origin>4656176</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1792" sha1="t5ndza7njaimketuqxy5lhfmlqw2xws" xml:space="preserve">{{Recipe summary
| Category = Pudding recipes
| Difficulty = 2
| Image = [[File:Gajjar ka halwa (carrot halwa).JPG|300px]]
}}

{{recipe}}

==Ingredients==
*2–3 large [[Cookbook:Carrot|carrots]]
*½ [[Cookbook:Cup|cup]] (120 [[Cookbook:Gram|g]]) [[Cookbook:Cashew|cashew nuts]], broken
*½ cup (120 g) [[Cookbook:Raisin|raisins]], washed
*1 [[Cookbook:Pinch|pinch]] [[Cookbook:Salt|salt]]
*2–3 [[Cookbook:Teaspoon|teaspoons]] [[Cookbook:Sugar|sugar]]
*4 pods [[Cookbook:Cardamom|cardamom]]
*1 pinch [[Cookbook:Cinnamon|cinnamon]] powder
*1 [[Cookbook:Tablespoon|tablespoon]] [[Cookbook:Butter|butter]]
*1 cup (240 [[Cookbook:Milliliter|ml]]) [[Cookbook:Milk|milk]]

==Procedure==

# Cut off the blemished ends of the carrots, wash them, and then peel them.
# [[Cookbook:Grater|Grate]] the carrots, and transfer the grated carrots into a [[Cookbook:Saucepan|saucepan]].
# Add the cashews, raisins, salt, sugar, cardamom, cinnamon, butter, and milk.
# Heat the saucepan and bring the contents to a [[Cookbook:Boiling|boil]], while mixing.
# Cook until the milk has mostly evaporated.
# Serve with a sprinkling of cinnamon powder on top.

== Notes, tips, and variations ==

* When the milk is almost evaporated you can add 50–100g of [[Cookbook:Khoya|khoya]] (dried milk solids) for a richer taste.

[[Category:Indian recipes|{{PAGENAME}}]]
[[Category:Recipes using cashew|{{PAGENAME}}]]
[[Category:Recipes using raisin]]
[[Category:Recipes using cardamom|{{PAGENAME}}]]
[[Category:Recipes for dessert|{{PAGENAME}}]]
[[Category:Recipes_with_metric_units|{{PAGENAME}}]]
[[Category:Recipes using carrot|{{PAGENAME}}]]
[[Category:Recipes for pudding]]
[[Category:Recipes using butter]]
[[Category:Recipes using sugar]]
[[Category:Recipes using ground cinnamon]]
[[Category:Recipes using milk]]</text>
      <sha1>t5ndza7njaimketuqxy5lhfmlqw2xws</sha1>
    </revision>
  </page>
  <page>
    <title>Horticulture/Herbaceous Ornamental Plants</title>
    <ns>0</ns>
    <id>82575</id>
    <revision>
      <id>4656092</id>
      <parentid>3338972</parentid>
      <timestamp>2026-08-02T19:00:55Z</timestamp>
      <contributor>
        <username>~2026-42561-45</username>
        <id>3618738</id>
      </contributor>
      <comment>added example species, corrected one link</comment>
      <origin>4656092</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1387" sha1="nsbljdgq98lif4k55fuvqz62y1xtzsz" xml:space="preserve">{{WMOG-header|Herbaceous Ornamental Plants}}Herbaceous plants fit roughly into 3 categories, namely annuals, biennials, and perennials.

'''Annuals''' are plants that complete their growing cycle in a single year or season. They germinate, grow vegetatively, flower, set seed, and then die. Many plants grown as annuals in temperate climates may actually be &quot;tropical perennials&quot;.

'''Biennials''' are similar to annuals, except that they do their vegetative growing one year, then flower, set seed, and die the following year.

'''Perennials''' are plants that live year after year, going through regular cycles of vegetative growth, flowering, setting seed, and then returning to vegetative growth (usually with periods of dormancy in between). Woody plants such as trees, shrubs, and vines are also perennials, but are not addressed in this volume.

The approach of this book is to discuss the planting and maintenance of individual herbaceous plants. Over time, there may be many thousands of entries.

==Perennial Plants (Common name list)==

*[[../Asclepias tuberosa|Butterfly Weed]] (''Asclepias tuberosa'')
*[[../Hemerocallis|Daylily]] (''Hemerocallis'' spp.)
*[[Horticulture/Helleborus|Hellebore]] (''Helleborus'' spp.)
*[[../Iris/]] (''Iris'' spp.)

==Annual Plants==

* French marigold (''Tagetes patula'')

==Biennial Plants==

* Forget-me-not (''Myosotis spp.'')
{{BookCat}}</text>
      <sha1>nsbljdgq98lif4k55fuvqz62y1xtzsz</sha1>
    </revision>
  </page>
  <page>
    <title>Celestia/DSC File</title>
    <ns>0</ns>
    <id>129372</id>
    <revision>
      <id>4656077</id>
      <parentid>4655890</parentid>
      <timestamp>2026-08-02T17:57:07Z</timestamp>
      <contributor>
        <username>SevenSpheres</username>
        <id>3275649</id>
      </contributor>
      <comment>Undid revision [[Special:Diff/4655890|4655890]] by [[Special:Contributions/~2026-42285-14|~2026-42285-14]] ([[User talk:~2026-42285-14|discuss]])</comment>
      <origin>4656077</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="7250" sha1="2dbpu0qjc8324scse4ble2de94jvt4b" xml:space="preserve">{{TOCright}}
==Introduction==

This is a brief description of the parameters recognized by
Celestia in DSC files (Deep Space Catalogs).
DSC Galaxy functionality underwent a substantial
improvement in Celestia v1.4.1 when compared to the previous versions of Celestia.

A DSC catalog file can be used to describe four classes of objects:
'''OpenCluster''', '''Globular''' (i.e. Globular Cluster), '''Nebula''' or '''Galaxy'''.

A DSC object definition consists of its class, a quoted name, and its parameters
enclosed in braces:
 &lt;i&gt;'''Class''' &lt;/i&gt; ''&quot;name&quot;'' { ...''parameters''... }

Unlike STC and SSC files, DSC files don't support &lt;code&gt;Modify&lt;/code&gt; and &lt;code&gt;Replace&lt;/code&gt; directives, so to modify an object defined in a DSC file you have to edit the original file.

==List of Parameters==
Class:
* '''OpenCluster''' &quot;''name''&quot;
* '''GlobularCluster''' &quot;''name''&quot;
* '''Nebula''' &quot;''name''&quot;
* '''Galaxy''' &quot;''name''&quot;


Location:
* '''RA''' ''f'', '''Dec''' ''f'', '''Distance''' ''f''

or
* '''Position''' [''f'' ''f'' ''f'']

Orientation:
* '''Axis''' [''f'' ''f'' ''f'']
* '''Angle''' ''f'' 

Size:
* '''Radius''' ''f''

Information:
* '''InfoUrl''' &quot;''URL''&quot;

Appearance:
* '''Mesh''' &quot;''filename''&quot;
* '''Type''' &quot;''string''&quot;
* '''CustomTemplate''' &quot;''filename''&quot;
* '''AbsMag''' ''f'' 

== OpenCluster &quot;&lt;i&gt;name&lt;/i&gt;&quot; == 
&lt;ul&gt;
&quot;name&quot; is the name of the object. Multiple names can be specified 
within the quotes if they're separated by colons (:).

&lt;b&gt;OpenCluster&lt;/b&gt; currently is used only to associate the specified
&quot;name&quot; with a position in space. The members of an OpenCluster are defined separately in one or more [[Celestia/STC_File|.STC files]] or in [[Celestia/Binary_Star_File|stars.dat]].

The parameters used to define an OpenCluster are

=== placement === 

A deep space object's position can be defined either by specifying a single position vector or by specifying its three astronomical coordinates.
&lt;ul&gt;
&lt;li&gt;&lt;b&gt;Position&lt;/b&gt; &lt;tt&gt;[&lt;i&gt; f f f &lt;/i&gt;]&lt;/tt&gt;

&lt;br&gt;The position vector's [x y z ] coordinates are in Light Years, 
specifying a position in Celestia's
Ecliptic J2000 &quot;Universal&quot; coordinate system 
&lt;/li&gt;
or
&lt;li&gt;&lt;b&gt;Distance&lt;/b&gt; &lt;i&gt;number&lt;/i&gt; (default: 1.0)
in LightYears
&lt;/li&gt;&lt;li&gt;&lt;b&gt;RA&lt;/b&gt; &lt;i&gt;number&lt;/i&gt; (default: 0.0)
Right Ascension in fractional Hours (unlike [[Celestia/STC_File|STC catalogs]], which use fractional degrees)
&lt;/li&gt;&lt;li&gt;&lt;b&gt;Dec&lt;/b&gt; &lt;i&gt;number&lt;/i&gt;  (default: 0.0)
Declination in fractional degrees

&lt;/li&gt;
&lt;/ul&gt;

===  orientation (optional)=== 
&lt;ul&gt;
&lt;li&gt;&lt;b&gt;Axis&lt;/b&gt; &lt;i&gt;3 vector&lt;/i&gt; (default: [ 1.0 0.0 0.0] )
&lt;br&gt;a unit vector specifying the orientation of the object's axis
in Celestia's Ecliptic J2000 &quot;Universal&quot; coordinate system 

&lt;/li&gt;&lt;li&gt;&lt;b&gt;Angle&lt;/b&gt; &lt;i&gt;number&lt;/i&gt; (default: 0.0 degrees)&lt;br&gt;the amount the object is rotated around that Axis.
&lt;/ul&gt;
=== size === 
&lt;ul&gt;
&lt;li&gt;&lt;b&gt;Radius&lt;/b&gt; &lt;i&gt;number&lt;/i&gt;  (default: 0.0)
in Light Years.
&lt;/li&gt;&lt;/ul&gt;
&lt;P&gt;&lt;/P&gt;

=== information  (optional)=== 

&lt;ul&gt;
&lt;li&gt;&lt;b&gt;InfoUrl&lt;/b&gt; &lt;i&gt;&quot;string&quot;&lt;/i&gt;

&lt;br&gt;&quot;string&quot; should be the URL of a web page describing the object.
&lt;/li&gt;
&lt;/ul&gt;
&lt;/ul&gt;

== Globular  &quot;&lt;i&gt;name&lt;/i&gt;&quot; == 
 
&lt;ul&gt;Places a glowing spherical image of stars at the specified position.
&lt;br&gt;Uses all of the parameters used for &lt;b&gt;OpenCluster&lt;/b&gt; plus the following:

=== size === 
* '''Radius''' ''number'', in light-years.
: The '''Radius''' specifies the size of the globular. Note that this does not affect the placement of sprites. It does, however, change the &quot;bounding box&quot;. For a larger Radius, the red markers will be appear farther away from the center of the globular. The Radius parameter also controls how far you are from the center of the globular, when you select and go-to that object.

=== shape ===

* '''Detail''' ''number''
: '''Detail''' is a value between 0 and 1 that controls how many point sprites the globular has. The default value is 1, and this places the maximum amount of point sprites. A value of 0 creates a globular with no stars but a glowing central &quot;core&quot;. Using a value greater than 1 or less than 0 is equivalent to using 1 or 0, respectively.

* '''CoreRadius''' ''number''

* '''KingConcentration''' ''number''

=== example ===

  Globular &quot;M 4:NGC 6121:GCl 41:C 1620-264&quot;
  {
        RA          	   16.3931  # [hours]
        Dec         	  -26.5253  # [degrees]
        Distance    	      7176  # [ly]
        Radius      	     37.57  # [ly], mu25 Isophote
        CoreRadius  	      0.83  # [arcmin]
        KingConcentration     1.59  # c = log10(r_t/r_c)
        AbsMag      	      -7.2  # [V mags]
        Axis       	[  0.1967  -0.6744  -0.7117]
        Angle       	     171.8  # [degrees]
        InfoURL  &quot;http://simbad.u-strasbg.fr/sim-id.pl?Ident=NGC+6121&quot;
  }


&lt;/ul&gt;

== Nebula  &quot;&lt;i&gt;name&lt;/i&gt;&quot; == 
 
&lt;ul&gt;Places a glowing model at the specified position and orientation.
&lt;br&gt;If '''Name''' is an empty string, draws the model mesh but does not add an empty name to listings. This allows for a model to be constructed of multiple parts. A central part should have the '''Name''' parameter with the name string and a '''Type''' parameter.
&lt;br&gt;Central stars are defined separately in one or more [[Celestia/STC_File|.STC files]].
&lt;br&gt;Uses all of the parameters used for &lt;b&gt;OpenCluster&lt;/b&gt; plus the following:

=== shape ===
* '''Type''' &quot;''string''&quot;

&lt;ul&gt;&quot;string&quot; should be one of: Emission, Reflection, Dark, Planetary, SupernovaRemnant, HII_Region, Protoplanetary, empty (undefined).

:The '''Type''' is shown in Celestia's on-screen informational display.
:If no '''Type''' is specified, it defaults to undefined. 
&lt;/ul&gt;
* '''Mesh''' &quot;''filename''&quot; (optional)
 
:&quot;''filename''&quot; must be the name of a 3DS, CMS or CMOD model file which determines the Nebula's shape.

:The model's internal material may require an associated PNG, JPG or DDS surface texture image file to be in the object's subdirectory &lt;tt&gt;/textures/medres&lt;/tt&gt; to define the Nebula's coloration. 

:If '''Mesh''' is omitted, no object is drawn.

=== brightness === 

* '''AbsMag''' ''number''

=== action === 

* '''Clickable''' ''boolean''

=== example ===

   '''Nebula &quot;M16:Eagle Nebula&quot; '''
   '''{'''
      '''Type &quot;Emission&quot;'''
      '''Mesh &quot;1995-44-a.3ds&quot;'''
      '''Axis    [0.205007 -0.737927 -0.642989]'''
      '''Angle 146.298'''
      '''RA 18.31404'''
      '''Dec -13.8311'''
      '''Distance 7002''' 
   '''}'''
&lt;/ul&gt;

== Galaxy   &quot;''name''&quot; == 

&lt;ul&gt;

Places a glowing image of a galaxy at the specified position and orientation
&lt;br&gt;Uses all of the parameters used for &lt;b&gt;OpenCluster&lt;/b&gt; plus the following:

=== shape === 
* '''Type''' &quot;''string''&quot;

&lt;ul&gt;&quot;string&quot; should be one of: S0, Sa, Sb, Sc, SBa, SBb, SBc, E0, E1, E2, E3, E4, E5, E6, E7, Irr

:The '''Type''' is shown in Celestia's on-screen informational display. It also determines which PNG image in Celestia's Models directory is used to define the shape of the '''Galaxy's''' image.
:If no '''Type''' is specified, it defaults to &quot;Irr&quot;.
&lt;/ul&gt;

or

* '''CustomTemplate'''  &quot;''filename''&quot; (optional)
&lt;ul&gt;&quot;''filename''&quot; must be a the name of a PNG image defining the shape of this Galaxy. The PNG image must be located in the ''main'' /models directory (where all the other custom template files are).
&lt;/ul&gt;

=== brightness === 

* '''AbsMag''' ''number''
&lt;/ul&gt;


{{BookCat}}</text>
      <sha1>2dbpu0qjc8324scse4ble2de94jvt4b</sha1>
    </revision>
    <revision>
      <id>4656082</id>
      <parentid>4656077</parentid>
      <timestamp>2026-08-02T18:02:27Z</timestamp>
      <contributor>
        <username>SevenSpheres</username>
        <id>3275649</id>
      </contributor>
      <comment>reinstate radius (accidentally removed?), remove unnecessary bold</comment>
      <origin>4656082</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="7196" sha1="ity81p4e8gwkb3gl0asqf9lzuwcw04o" xml:space="preserve">{{TOCright}}
==Introduction==

This is a brief description of the parameters recognized by
Celestia in DSC files (Deep Space Catalogs).
DSC Galaxy functionality underwent a substantial
improvement in Celestia v1.4.1 when compared to the previous versions of Celestia.

A DSC catalog file can be used to describe four classes of objects:
'''OpenCluster''', '''Globular''' (i.e. Globular Cluster), '''Nebula''' or '''Galaxy'''.

A DSC object definition consists of its class, a quoted name, and its parameters
enclosed in braces:
 &lt;i&gt;'''Class''' &lt;/i&gt; ''&quot;name&quot;'' { ...''parameters''... }

Unlike STC and SSC files, DSC files don't support &lt;code&gt;Modify&lt;/code&gt; and &lt;code&gt;Replace&lt;/code&gt; directives, so to modify an object defined in a DSC file you have to edit the original file.

==List of Parameters==
Class:
* '''OpenCluster''' &quot;''name''&quot;
* '''GlobularCluster''' &quot;''name''&quot;
* '''Nebula''' &quot;''name''&quot;
* '''Galaxy''' &quot;''name''&quot;


Location:
* '''RA''' ''f'', '''Dec''' ''f'', '''Distance''' ''f''

or
* '''Position''' [''f'' ''f'' ''f'']

Orientation:
* '''Axis''' [''f'' ''f'' ''f'']
* '''Angle''' ''f'' 

Size:
* '''Radius''' ''f''

Information:
* '''InfoUrl''' &quot;''URL''&quot;

Appearance:
* '''Mesh''' &quot;''filename''&quot;
* '''Type''' &quot;''string''&quot;
* '''CustomTemplate''' &quot;''filename''&quot;
* '''AbsMag''' ''f'' 

== OpenCluster &quot;&lt;i&gt;name&lt;/i&gt;&quot; == 
&lt;ul&gt;
&quot;name&quot; is the name of the object. Multiple names can be specified 
within the quotes if they're separated by colons (:).

&lt;b&gt;OpenCluster&lt;/b&gt; currently is used only to associate the specified
&quot;name&quot; with a position in space. The members of an OpenCluster are defined separately in one or more [[Celestia/STC_File|.STC files]] or in [[Celestia/Binary_Star_File|stars.dat]].

The parameters used to define an OpenCluster are

=== placement === 

A deep space object's position can be defined either by specifying a single position vector or by specifying its three astronomical coordinates.
&lt;ul&gt;
&lt;li&gt;&lt;b&gt;Position&lt;/b&gt; &lt;tt&gt;[&lt;i&gt; f f f &lt;/i&gt;]&lt;/tt&gt;

&lt;br&gt;The position vector's [x y z ] coordinates are in Light Years, 
specifying a position in Celestia's
Ecliptic J2000 &quot;Universal&quot; coordinate system 
&lt;/li&gt;
or
&lt;li&gt;&lt;b&gt;Distance&lt;/b&gt; &lt;i&gt;number&lt;/i&gt; (default: 1.0)
in LightYears
&lt;/li&gt;&lt;li&gt;&lt;b&gt;RA&lt;/b&gt; &lt;i&gt;number&lt;/i&gt; (default: 0.0)
Right Ascension in fractional Hours (unlike [[Celestia/STC_File|STC catalogs]], which use fractional degrees)
&lt;/li&gt;&lt;li&gt;&lt;b&gt;Dec&lt;/b&gt; &lt;i&gt;number&lt;/i&gt;  (default: 0.0)
Declination in fractional degrees

&lt;/li&gt;
&lt;/ul&gt;

===  orientation (optional)=== 
&lt;ul&gt;
&lt;li&gt;&lt;b&gt;Axis&lt;/b&gt; &lt;i&gt;3 vector&lt;/i&gt; (default: [ 1.0 0.0 0.0] )
&lt;br&gt;a unit vector specifying the orientation of the object's axis
in Celestia's Ecliptic J2000 &quot;Universal&quot; coordinate system 

&lt;/li&gt;&lt;li&gt;&lt;b&gt;Angle&lt;/b&gt; &lt;i&gt;number&lt;/i&gt; (default: 0.0 degrees)&lt;br&gt;the amount the object is rotated around that Axis.
&lt;/ul&gt;
=== size === 
&lt;ul&gt;
&lt;li&gt;&lt;b&gt;Radius&lt;/b&gt; &lt;i&gt;number&lt;/i&gt;  (default: 0.0)
in Light Years.
&lt;/li&gt;&lt;/ul&gt;
&lt;P&gt;&lt;/P&gt;

=== information  (optional)=== 

&lt;ul&gt;
&lt;li&gt;&lt;b&gt;InfoUrl&lt;/b&gt; &lt;i&gt;&quot;string&quot;&lt;/i&gt;

&lt;br&gt;&quot;string&quot; should be the URL of a web page describing the object.
&lt;/li&gt;
&lt;/ul&gt;
&lt;/ul&gt;

== Globular  &quot;&lt;i&gt;name&lt;/i&gt;&quot; == 
 
&lt;ul&gt;Places a glowing spherical image of stars at the specified position.
&lt;br&gt;Uses all of the parameters used for &lt;b&gt;OpenCluster&lt;/b&gt; plus the following:

=== size === 
* '''Radius''' ''number'', in light-years.
: The '''Radius''' specifies the size of the globular. Note that this does not affect the placement of sprites. It does, however, change the &quot;bounding box&quot;. For a larger Radius, the red markers will be appear farther away from the center of the globular. The Radius parameter also controls how far you are from the center of the globular, when you select and go-to that object.

=== shape ===

* '''Detail''' ''number''
: '''Detail''' is a value between 0 and 1 that controls how many point sprites the globular has. The default value is 1, and this places the maximum amount of point sprites. A value of 0 creates a globular with no stars but a glowing central &quot;core&quot;. Using a value greater than 1 or less than 0 is equivalent to using 1 or 0, respectively.

* '''CoreRadius''' ''number''

* '''KingConcentration''' ''number''

=== example ===

  Globular &quot;M 4:NGC 6121:GCl 41:C 1620-264&quot;
  {
        RA          	   16.3931  # [hours]
        Dec         	  -26.5253  # [degrees]
        Distance    	      7176  # [ly]
        Radius      	     37.57  # [ly], mu25 Isophote
        CoreRadius  	      0.83  # [arcmin]
        KingConcentration     1.59  # c = log10(r_t/r_c)
        AbsMag      	      -7.2  # [V mags]
        Axis       	[  0.1967  -0.6744  -0.7117]
        Angle       	     171.8  # [degrees]
        InfoURL  &quot;http://simbad.u-strasbg.fr/sim-id.pl?Ident=NGC+6121&quot;
  }


&lt;/ul&gt;

== Nebula  &quot;&lt;i&gt;name&lt;/i&gt;&quot; == 
 
Places a glowing model at the specified position and orientation.
&lt;br&gt;If '''Name''' is an empty string, draws the model mesh but does not add an empty name to listings. This allows for a model to be constructed of multiple parts. A central part should have the '''Name''' parameter with the name string and a '''Type''' parameter.
&lt;br&gt;Central stars are defined separately in one or more [[Celestia/STC_File|.STC files]].
&lt;br&gt;Uses all of the parameters used for &lt;b&gt;OpenCluster&lt;/b&gt; plus the following:

=== shape ===
* '''Type''' &quot;''string''&quot;

&lt;ul&gt;&quot;string&quot; should be one of: Emission, Reflection, Dark, Planetary, SupernovaRemnant, HII_Region, Protoplanetary, empty (undefined).

:The '''Type''' is shown in Celestia's on-screen informational display.
:If no '''Type''' is specified, it defaults to undefined. 
&lt;/ul&gt;
* '''Mesh''' &quot;''filename''&quot; (optional)
 
:&quot;''filename''&quot; must be the name of a 3DS, CMS or CMOD model file which determines the Nebula's shape.

:The model's internal material may require an associated PNG, JPG or DDS surface texture image file to be in the object's subdirectory &lt;tt&gt;/textures/medres&lt;/tt&gt; to define the Nebula's coloration. 

:If '''Mesh''' is omitted, no object is drawn.

=== brightness === 

* '''AbsMag''' ''number''

=== action === 

* '''Clickable''' ''boolean''

=== example ===

   Nebula &quot;M16:Eagle Nebula&quot;
   {
      Type &quot;Emission&quot;
      Mesh &quot;1995-44-a.3ds&quot;
      Axis    [0.205007 -0.737927 -0.642989]
      Angle 146.298
      RA 18.31404
      Dec -13.8311
      Distance 7002
      Radius 3.45
   }

== Galaxy   &quot;''name''&quot; == 

&lt;ul&gt;

Places a glowing image of a galaxy at the specified position and orientation
&lt;br&gt;Uses all of the parameters used for &lt;b&gt;OpenCluster&lt;/b&gt; plus the following:

=== shape === 
* '''Type''' &quot;''string''&quot;

&lt;ul&gt;&quot;string&quot; should be one of: S0, Sa, Sb, Sc, SBa, SBb, SBc, E0, E1, E2, E3, E4, E5, E6, E7, Irr

:The '''Type''' is shown in Celestia's on-screen informational display. It also determines which PNG image in Celestia's Models directory is used to define the shape of the '''Galaxy's''' image.
:If no '''Type''' is specified, it defaults to &quot;Irr&quot;.
&lt;/ul&gt;

or

* '''CustomTemplate'''  &quot;''filename''&quot; (optional)
&lt;ul&gt;&quot;''filename''&quot; must be a the name of a PNG image defining the shape of this Galaxy. The PNG image must be located in the ''main'' /models directory (where all the other custom template files are).
&lt;/ul&gt;

=== brightness === 

* '''AbsMag''' ''number''
&lt;/ul&gt;


{{BookCat}}</text>
      <sha1>ity81p4e8gwkb3gl0asqf9lzuwcw04o</sha1>
    </revision>
  </page>
  <page>
    <title>Wikibooks:Reading room/Administrative Assistance</title>
    <ns>4</ns>
    <id>140081</id>
    <revision>
      <id>4656097</id>
      <parentid>4656040</parentid>
      <timestamp>2026-08-02T20:23:37Z</timestamp>
      <contributor>
        <username>Codename Noreste</username>
        <id>3441010</id>
      </contributor>
      <comment>/* Permata55 reported by MathXplore */ reply: Already globally locked by a steward. (-) ([[mw:c:Special:MyLanguage/User:JWBTH/CD|CD]])</comment>
      <origin>4656097</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="5917" sha1="3gg0zx7uj1n9xm1hbbujpzsmvesg559" xml:space="preserve">__NEWSECTIONLINK__ {{Discussion Rooms}} {{shortcut|WB:AN|WB:AA}} {{TOC left}}
{{User:MiszaBot/config
|archive = Wikibooks:Reading room/Administrative Assistance/Archives/%(year)d/%(monthname)s
|algo = old(14d)
|counter = 1
|minthreadstoarchive = 1
|minthreadsleft = 1
}}
{{ombox|type=content|text='''To request a rename or usurpation''', go to the global request page at Meta [[meta:SRUC|here]].&lt;br /&gt;''Please do not post those requests here!''}}
{{Clear}}
Welcome to the '''Administrative Assistance reading room'''.  You can request assistance from [[WB:ADMIN|administrators]] for handling a variety of problems here and alert them about problems which may require special actions not normally used during regular content editing. Please be patient as administrators are often quite busy with either their own projects or trying to perform general maintenance and cleanup.

You can deal with most vandalism yourself: [[Wikibooks:Dealing with vandalism|fix it]], then [[Wikibooks:Templates/User_notices|warn the user]]. If there is repeated vandalism by one user, lots of vandalism on a single page, or vandalism from many users, tell an admin here, or in [irc://irc.freenode.net/wikibooks #wikibooks] (say &lt;code&gt;!admin&lt;/code&gt; to get attention).

For more general questions and assistance that doesn't require an administrator, please use the [[WB:HELP|Assistance Reading Room]].
{{clear}}

[[Category:Reading room]]

== WinniJoy reported by MathXplore ==

* {{userlinks|WinniJoy}}

Spam &lt;!-- USERREPORTED:/WinniJoy/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 10:48, 18 July 2026 (UTC)
: {{done}}. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 19:00, 19 July 2026 (UTC)

== ~2026-40144-05 reported by MathXplore ==

* {{userlinks|~2026-40144-05}}

Spam &lt;!-- USERREPORTED:/~2026-40144-05/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 11:17, 19 July 2026 (UTC)
: I blocked them for creating out of scope pages. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 18:59, 19 July 2026 (UTC)
== Tkdesigner34 reported by MathXplore ==

* {{userlinks|Tkdesigner34}}

Spam &lt;!-- USERREPORTED:/Tkdesigner34/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:08, 20 July 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; 19:37, 20 July 2026 (UTC)
== Samanthajagan reported by MathXplore ==

* {{userlinks|Samanthajagan}}

Spam, [[Special:AbuseLog/314786]] &lt;!-- USERREPORTED:/Samanthajagan/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:30, 21 July 2026 (UTC)

:{{done}} —[[User:Atcovi|Atcovi]] [[User talk:Atcovi|(Talk]] - [[Special:Contributions/Atcovi|Contribs)]] 12:47, 21 July 2026 (UTC)
== Upgradchennai0 reported by MathXplore ==

* {{userlinks|Upgradchennai0}}

Link spam, [[Special:AbuseLog/314865]], [[Special:CentralAuth/Upgradchennai0]] &lt;!-- USERREPORTED:/Upgradchennai0/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 07:54, 26 July 2026 (UTC)
: {{done}}. [[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]]) 13:02, 26 July 2026 (UTC)
== Elearningandearning reported by MathXplore ==

* {{userlinks|Elearningandearning}}

Spam &lt;!-- USERREPORTED:/Elearningandearning/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:06, 29 July 2026 (UTC)
: {{done}}. [[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]]) 14:49, 29 July 2026 (UTC)

== Starlium reported by MathXplore ==

* {{userlinks|Starlium}}

Long-term abuse. Cross-wiki abuse. [[Special:CentralAuth/Wahyu_Saputraa]], [[:w:id:Wikipedia:Investigasi pengguna siluman/Wahyu Saputraa]] &lt;!-- USERREPORTED:/Starlium/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:17, 29 July 2026 (UTC)
: Globally locked by a steward. [[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]]) 14:48, 29 July 2026 (UTC)
== Aranyaresidency reported by MathXplore ==

* {{userlinks|Aranyaresidency}}

Link spam, [[Special:AbuseLog/314920]] &lt;!-- USERREPORTED:/Aranyaresidency/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:25, 31 July 2026 (UTC)
: {{done}}. [[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]]) 16:33, 31 July 2026 (UTC)
== Permata55 reported by MathXplore ==

* {{userlinks|Permata55}}

Spam &lt;!-- USERREPORTED:/Permata55/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 07:33, 1 August 2026 (UTC)
: Already globally locked by a steward. [[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]]) 20:23, 2 August 2026 (UTC)</text>
      <sha1>3gg0zx7uj1n9xm1hbbujpzsmvesg559</sha1>
    </revision>
    <revision>
      <id>4656178</id>
      <parentid>4656097</parentid>
      <timestamp>2026-08-03T08:10:26Z</timestamp>
      <contributor>
        <username>ArchiverBot</username>
        <id>1227662</id>
      </contributor>
      <minor />
      <comment>Bot: Archiving 2 threads (older than 14 days) to [[Wikibooks:Reading room/Administrative Assistance/Archives/2026/July]]</comment>
      <origin>4656178</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="5014" sha1="e8e4v7jj64r2ik0avqw4n9ya4l4awlz" xml:space="preserve">__NEWSECTIONLINK__ {{Discussion Rooms}} {{shortcut|WB:AN|WB:AA}} {{TOC left}}
{{User:MiszaBot/config
|archive = Wikibooks:Reading room/Administrative Assistance/Archives/%(year)d/%(monthname)s
|algo = old(14d)
|counter = 1
|minthreadstoarchive = 1
|minthreadsleft = 1
}}
{{ombox|type=content|text='''To request a rename or usurpation''', go to the global request page at Meta [[meta:SRUC|here]].&lt;br /&gt;''Please do not post those requests here!''}}
{{Clear}}
Welcome to the '''Administrative Assistance reading room'''.  You can request assistance from [[WB:ADMIN|administrators]] for handling a variety of problems here and alert them about problems which may require special actions not normally used during regular content editing. Please be patient as administrators are often quite busy with either their own projects or trying to perform general maintenance and cleanup.

You can deal with most vandalism yourself: [[Wikibooks:Dealing with vandalism|fix it]], then [[Wikibooks:Templates/User_notices|warn the user]]. If there is repeated vandalism by one user, lots of vandalism on a single page, or vandalism from many users, tell an admin here, or in [irc://irc.freenode.net/wikibooks #wikibooks] (say &lt;code&gt;!admin&lt;/code&gt; to get attention).

For more general questions and assistance that doesn't require an administrator, please use the [[WB:HELP|Assistance Reading Room]].
{{clear}}

[[Category:Reading room]]

== Tkdesigner34 reported by MathXplore ==

* {{userlinks|Tkdesigner34}}

Spam &lt;!-- USERREPORTED:/Tkdesigner34/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:08, 20 July 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; 19:37, 20 July 2026 (UTC)
== Samanthajagan reported by MathXplore ==

* {{userlinks|Samanthajagan}}

Spam, [[Special:AbuseLog/314786]] &lt;!-- USERREPORTED:/Samanthajagan/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:30, 21 July 2026 (UTC)

:{{done}} —[[User:Atcovi|Atcovi]] [[User talk:Atcovi|(Talk]] - [[Special:Contributions/Atcovi|Contribs)]] 12:47, 21 July 2026 (UTC)
== Upgradchennai0 reported by MathXplore ==

* {{userlinks|Upgradchennai0}}

Link spam, [[Special:AbuseLog/314865]], [[Special:CentralAuth/Upgradchennai0]] &lt;!-- USERREPORTED:/Upgradchennai0/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 07:54, 26 July 2026 (UTC)
: {{done}}. [[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]]) 13:02, 26 July 2026 (UTC)
== Elearningandearning reported by MathXplore ==

* {{userlinks|Elearningandearning}}

Spam &lt;!-- USERREPORTED:/Elearningandearning/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:06, 29 July 2026 (UTC)
: {{done}}. [[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]]) 14:49, 29 July 2026 (UTC)

== Starlium reported by MathXplore ==

* {{userlinks|Starlium}}

Long-term abuse. Cross-wiki abuse. [[Special:CentralAuth/Wahyu_Saputraa]], [[:w:id:Wikipedia:Investigasi pengguna siluman/Wahyu Saputraa]] &lt;!-- USERREPORTED:/Starlium/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:17, 29 July 2026 (UTC)
: Globally locked by a steward. [[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]]) 14:48, 29 July 2026 (UTC)
== Aranyaresidency reported by MathXplore ==

* {{userlinks|Aranyaresidency}}

Link spam, [[Special:AbuseLog/314920]] &lt;!-- USERREPORTED:/Aranyaresidency/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:25, 31 July 2026 (UTC)
: {{done}}. [[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]]) 16:33, 31 July 2026 (UTC)
== Permata55 reported by MathXplore ==

* {{userlinks|Permata55}}

Spam &lt;!-- USERREPORTED:/Permata55/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 07:33, 1 August 2026 (UTC)
: Already globally locked by a steward. [[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]]) 20:23, 2 August 2026 (UTC)</text>
      <sha1>e8e4v7jj64r2ik0avqw4n9ya4l4awlz</sha1>
    </revision>
    <revision>
      <id>4656185</id>
      <parentid>4656178</parentid>
      <timestamp>2026-08-03T11:21:28Z</timestamp>
      <contributor>
        <username>MathXplore</username>
        <id>3097823</id>
      </contributor>
      <comment>Reporting Birdsjungle</comment>
      <origin>4656185</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="5302" sha1="kswr76giwoibb2jgrs5v3imkfx5wted" xml:space="preserve">__NEWSECTIONLINK__ {{Discussion Rooms}} {{shortcut|WB:AN|WB:AA}} {{TOC left}}
{{User:MiszaBot/config
|archive = Wikibooks:Reading room/Administrative Assistance/Archives/%(year)d/%(monthname)s
|algo = old(14d)
|counter = 1
|minthreadstoarchive = 1
|minthreadsleft = 1
}}
{{ombox|type=content|text='''To request a rename or usurpation''', go to the global request page at Meta [[meta:SRUC|here]].&lt;br /&gt;''Please do not post those requests here!''}}
{{Clear}}
Welcome to the '''Administrative Assistance reading room'''.  You can request assistance from [[WB:ADMIN|administrators]] for handling a variety of problems here and alert them about problems which may require special actions not normally used during regular content editing. Please be patient as administrators are often quite busy with either their own projects or trying to perform general maintenance and cleanup.

You can deal with most vandalism yourself: [[Wikibooks:Dealing with vandalism|fix it]], then [[Wikibooks:Templates/User_notices|warn the user]]. If there is repeated vandalism by one user, lots of vandalism on a single page, or vandalism from many users, tell an admin here, or in [irc://irc.freenode.net/wikibooks #wikibooks] (say &lt;code&gt;!admin&lt;/code&gt; to get attention).

For more general questions and assistance that doesn't require an administrator, please use the [[WB:HELP|Assistance Reading Room]].
{{clear}}

[[Category:Reading room]]

== Tkdesigner34 reported by MathXplore ==

* {{userlinks|Tkdesigner34}}

Spam &lt;!-- USERREPORTED:/Tkdesigner34/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:08, 20 July 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; 19:37, 20 July 2026 (UTC)
== Samanthajagan reported by MathXplore ==

* {{userlinks|Samanthajagan}}

Spam, [[Special:AbuseLog/314786]] &lt;!-- USERREPORTED:/Samanthajagan/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:30, 21 July 2026 (UTC)

:{{done}} —[[User:Atcovi|Atcovi]] [[User talk:Atcovi|(Talk]] - [[Special:Contributions/Atcovi|Contribs)]] 12:47, 21 July 2026 (UTC)
== Upgradchennai0 reported by MathXplore ==

* {{userlinks|Upgradchennai0}}

Link spam, [[Special:AbuseLog/314865]], [[Special:CentralAuth/Upgradchennai0]] &lt;!-- USERREPORTED:/Upgradchennai0/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 07:54, 26 July 2026 (UTC)
: {{done}}. [[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]]) 13:02, 26 July 2026 (UTC)
== Elearningandearning reported by MathXplore ==

* {{userlinks|Elearningandearning}}

Spam &lt;!-- USERREPORTED:/Elearningandearning/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:06, 29 July 2026 (UTC)
: {{done}}. [[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]]) 14:49, 29 July 2026 (UTC)

== Starlium reported by MathXplore ==

* {{userlinks|Starlium}}

Long-term abuse. Cross-wiki abuse. [[Special:CentralAuth/Wahyu_Saputraa]], [[:w:id:Wikipedia:Investigasi pengguna siluman/Wahyu Saputraa]] &lt;!-- USERREPORTED:/Starlium/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:17, 29 July 2026 (UTC)
: Globally locked by a steward. [[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]]) 14:48, 29 July 2026 (UTC)
== Aranyaresidency reported by MathXplore ==

* {{userlinks|Aranyaresidency}}

Link spam, [[Special:AbuseLog/314920]] &lt;!-- USERREPORTED:/Aranyaresidency/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:25, 31 July 2026 (UTC)
: {{done}}. [[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]]) 16:33, 31 July 2026 (UTC)
== Permata55 reported by MathXplore ==

* {{userlinks|Permata55}}

Spam &lt;!-- USERREPORTED:/Permata55/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 07:33, 1 August 2026 (UTC)
: Already globally locked by a steward. [[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]]) 20:23, 2 August 2026 (UTC)
== Birdsjungle reported by MathXplore ==
* {{userlinks|Birdsjungle}}

Link spam, [[Special:AbuseLog/314940]] &lt;!-- USERREPORTED:/Birdsjungle/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 11:21, 3 August 2026 (UTC)</text>
      <sha1>kswr76giwoibb2jgrs5v3imkfx5wted</sha1>
    </revision>
  </page>
  <page>
    <title>Vehicle Identification Numbers (VIN codes)/GM/VIN Codes</title>
    <ns>0</ns>
    <id>142013</id>
    <revision>
      <id>4656067</id>
      <parentid>4656030</parentid>
      <timestamp>2026-08-02T17:26:15Z</timestamp>
      <contributor>
        <username>JustTheFacts33</username>
        <id>3434282</id>
      </contributor>
      <comment>/* Series 2000-2009 Light Duty Truck &amp; Multi-Purpose Passenger Vehicle */</comment>
      <origin>4656067</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="205334" sha1="s3uii1qtmd7hbsar55bps5gtlry844c" xml:space="preserve">{{Vehicle Identification Numbers (VIN codes)/Warning}}{{clear}}
It is the tenth digit that gives you the model year for GM. I've been working at a Chevy dealer for years running codes/vins. For example (my examples only apply to 2001-2015 gm vehicles)
Remember 10th digit from the beginning, (left to right).
2001... 1, 
2002...2, 
2003...3, 
etc., 
2009...9. 
After 2009, the tenth digit was given a letter
2010... A, 
2011...B, 
2012...C, 
2013...D, 
2014...E, 
2015...F, 
Etc...
We have another 20 years worth of letters.
Thanks for reading.
You can always check your model year by looking in your drivers side door jamb and it will give you model year. If it was assembled in July or later, the model year is probably a year later than the calendar year of the manufacturing date listed.

==American GM==
===American VIN format 1981-1984 Passenger Car===
GM's VIN format is as follows:

&lt;table border=1 style=&quot;margin:auto;&quot;&gt;
&lt;tr&gt;
&lt;th&gt;Position&lt;/th&gt;
&lt;th&gt;Sample&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;Description&lt;/th&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;1&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td rowspan=3&gt;[[#GM WMIs|World Manufacturer Identifier]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;G&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;6&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;A&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[#American restraint types 1981-1984|Restraint type]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;5&lt;/td&gt;
&lt;td&gt;M&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[#Car Line &amp; Series Code 1981-1984|Car Line &amp; Series Code]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;6&lt;/td&gt;
&lt;td&gt;4&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td rowspan=2&gt;[[#Body style codes 1981-1986|Body style]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;7&lt;/td&gt;
&lt;td&gt;7&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt; &lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;8&lt;/td&gt;
&lt;td&gt;8&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[#American engine codes 1981-|Engine type]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;9&lt;/td&gt;
&lt;td&gt;0&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[Vehicle Identification Numbers (VIN codes)/Check digit |Check digit]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;10&lt;/td&gt;
&lt;td&gt;E&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[Vehicle Identification Numbers (VIN codes)/Model year|Model year]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;11&lt;/td&gt;
&lt;td&gt;9&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[#GM factories supplying North America|Factory ID]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;12&lt;/td&gt;
&lt;td&gt;1&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td rowspan=6&gt;Sequential number
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;13&lt;/td&gt;
&lt;td&gt;2&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;14&lt;/td&gt;
&lt;td&gt;3&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;15&lt;/td&gt;
&lt;td&gt;7&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;16&lt;/td&gt;
&lt;td&gt;6&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;17&lt;/td&gt;
&lt;td&gt;2&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;
&lt;/table&gt;

====American restraint types 1981-1984====
The restraint type is specified as character 4 of the American GM VIN for passenger cars.

{| border=1 style=&quot;margin:auto;&quot;
!VIN Code
!Description
|-
|A||Manual Seatbelts only - No Passive Restraint
|}

====Car Line &amp; Series Code 1981-1984====
The Car Line &amp; Series Code is specified as character 5 of the American GM VIN for passenger cars.

{| border=1 style=&quot;margin:auto;&quot;
!List of GM platforms
!Car Line &amp; &lt;br&gt; Series Code
!:Category:General Motors vehicles|Model
|-
|rowspan=19|GM A platform - rear-wheel drive
|T||Chevrolet Malibu 1981
|-
|W||Chevrolet Malibu Classic 1981
|-
|Z||Chevrolet Monte Carlo 1981
|-
|D||Pontiac LeMans 1981
|-
|F||Pontiac Grand LeMans 1981
|-
|J||Pontiac Grand Prix 1981
|-
|K||Pontiac Grand Prix LJ 1981
|-
|P||Pontiac Grand Prix Brougham 1981
|-
|G||Oldsmobile Cutlass sedan, Cutlass Cruiser wagon 1981
|-
|H||Oldsmobile Cutlass Cruiser ''Brougham'' wagon 1981
|-
|K||Oldsmobile Cutlass Calais coupe 1981
|-
|M||Oldsmobile Cutlass Supreme ''Brougham'' 1981
|-
|R||Oldsmobile Cutlass Supreme coupe, Cutlass LS sedan 1981
|-
|E||Buick Century wagon 1981
|-
|H||Buick Century sedan, Estate wagon 1981
|-
|J||Buick Regal 1981
|-
|K||Buick Regal ''Sport'' 1981
|-
|L||Buick Century ''Limited'' 1981
|-
|M||Buick Regal ''Limited'' 1981
|-
|rowspan=10|GM A platform - front-wheel drive
|W||Chevrolet Celebrity 1982-1984
|-
|F||Pontiac 6000 1982-1984
|-
|G||Pontiac 6000 ''LE'' 1982-1984
|-
|H||Pontiac 6000 ''STE'' 1983-1984
|-
|G||Oldsmobile Cutlass Ciera 1982
|-
|J||Oldsmobile Cutlass Ciera ''LS'' 1982-1984, Cutlass Cruiser ''LS'' 1984
|-
|M||Oldsmobile Cutlass Ciera ''Brougham'' 1982-1984
|-
|G||Buick Century ''T-Type'' 1983-1984
|-
|H||Buick Century ''Custom'' 1982-1984
|-
|L||Buick Century ''Limited'' 1982-1984
|-
|rowspan=19|GM B platform
|D||Chevrolet Bel Air 1981 (Canada only)
|-
|L||Chevrolet Impala 1981-1984
|-
|N||Chevrolet Caprice Classic 1981-1984
|-
|F||Pontiac Laurentian 1981 (Canada only)
|-
|L||Pontiac Catalina 1981, Parisienne 1984
|-
|L||Pontiac Parisienne 1982-1983 (Canada only)
|-
|N||Pontiac Bonneville 1981
|-
|N||Pontiac Parisienne 1981, Parisienne Brougham 1982-1983 (Canada only)
|-
|R||Pontiac Bonneville Brougham 1981
|-
|T||Pontiac Parisienne Brougham 1984
|-
|L||Oldsmobile Delta 88 1981-1983
|-
|N||Oldsmobile Delta 88 Royale 1981-1984
|-
|P||Oldsmobile Custom Cruiser 1981-1984
|-
|V||Oldsmobile Delta 88 Royale Brougham LS 1984
|-
|Y||Oldsmobile Delta 88 Royale Brougham 1981-1984
|-
|N||Buick Le Sabre 1981, Le Sabre ''Custom'' 1982-1984 
|-
|P||Buick Le Sabre ''Limited'' 1981-1984
|-
|R||Buick Le Sabre Estate Wagon 1981-1983
|-
|V||Buick Electra Estate Wagon 1981-1984
|-
|rowspan=13|GM C platform - rear-wheel drive
|G||Oldsmobile 98 Regency 1984
|-
|H||Oldsmobile 98 Regency Brougham 1984
|-
|V||Oldsmobile 98 Luxury 1981
|-
|W||Oldsmobile 98 Regency Brougham 1982-1983
|-
|X||Oldsmobile 98 Regency 1981-1983
|-
|R||Buick Electra Limited 1984
|-
|U||Buick Electra Park Avenue 1984
|-
|W||Buick Electra Park Avenue 1981-1983
|-
|X||Buick Electra Limited 1981-1983
|-
|B||Cadillac Fleetwood Brougham 1981-1983
|-
|D||Cadillac DeVille 1981-1983
|-
|M||Cadillac DeVille 1984
|-
|W||Cadillac Fleetwood Brougham 1984
|-
|rowspan=1|GM D platform - rear-wheel drive
|F||Cadillac Fleetwood Limousine 1981-1984
|-
|rowspan=4|GM E platform
|Z||Oldsmobile Toronado Brougham 1981-1984
|-
|Y||Buick Riviera T-Type 1981-1984
|-
|Z||Buick Riviera 1981-1984
|-
|L||Cadillac Eldorado 1981-1984
|-
|rowspan=7|GM F platform
|P||Chevrolet Camaro Sport Coupe 1981-1984
|-
|S||Chevrolet Camaro Berlinetta 1981-1984
|-
|S||Pontiac Firebird 1981-1984
|-
|T||Pontiac Firebird ''Esprit'' 1981
|-
|V||Pontiac Firebird ''Formula'' 1981
|-
|W||Pontiac Firebird ''Trans Am'' 1981-1984
|-
|X||Pontiac Firebird ''Trans Am'' Turbo Special Edition 1981, Firebird ''S/E'' 1982-1984
|-
|rowspan=15|GM G platform - rear-wheel drive
|W||Chevrolet Malibu Classic 1982, Malibu 1983
|-
|Z||Chevrolet Monte Carlo 1982-1984
|-
|J||Pontiac Grand Prix 1982-1984
|-
|K||Pontiac Grand Prix LJ 1982-1983, Grand Prix LE 1984
|-
|N||Pontiac Bonneville G 1982-1984
|-
|P||Pontiac Grand Prix Brougham 1982-1984
|-
|R||Pontiac Bonneville G Brougham 1982-1984
|-
|S||Pontiac Bonneville G ''LE'' 1984
|-
|H||Oldsmobile Cutlass Cruiser wagon 1982-1983
|-
|K||Oldsmobile Cutlass Calais coupe 1982-1984
|-
|M||Oldsmobile Cutlass Supreme ''Brougham'' 1982-1984
|-
|R||Oldsmobile Cutlass Supreme coupe &amp; sedan 1982-1984
|-
|J||Buick Regal 1982-1984
|-
|K||Buick Regal ''Sport'' 1982, Regal ''T-Type'' 1983-1984
|-
|M||Buick Regal ''Limited'' 1982-1984
|-
|rowspan=13|GM J platform
|C||Chevrolet Cavalier 1983-1984
|-
|D||Chevrolet Cavalier 2-d/4-d/wagon 1982, Cavalier CS 1983-1984
|-
|E||Chevrolet Cavalier 3-door hatchback 1982, Cavalier CS 3-door hatchback 1983, Cavalier Type 10 2-d/3-d/Convertible 1984
|-
|B||Pontiac J2000 1982, 2000 1983, 2000 Sunbird 1984
|-
|C||Pontiac J2000 LE 1982, 2000 LE 1983, 2000 Sunbird LE Convertible 1983, 2000 Sunbird LE 1984
|-
|D||Pontiac J2000 SE 1982, 2000 SE 1983, 2000 Sunbird SE 1984
|-
|E||Pontiac J2000 S 1982
|-
|C||Oldsmobile Firenza Base model 1982-1984, Firenza S 1982-1984
|-
|D||Oldsmobile Firenza LX 1982-1984, Firenza SX 1982-1984
|-
|E||Buick Skyhawk T-Type 1983-1984
|-
|S||Buick Skyhawk Custom 1982-1984
|-
|T||Buick Skyhawk Limited 1982-1984
|-
|G||Cadillac Cimarron 1982-1984
|-
|rowspan=1|GM K platform
|S||Cadillac Seville 1981-1984
|-
|rowspan=3|GM P platform
||E||Pontiac Fiero ''Coupe'' 1984
|-
||F||Pontiac Fiero ''SE'' 1984
|-
||M||Pontiac Fiero ''Sport coupe'' 1984
|-
|rowspan=6|GM T platform - rear-wheel drive
|B||Chevrolet Chevette 1981-1983, Chevette CS 1984
|-
|J||Chevrolet Chevette Scooter 1981-1983, Chevette 1984
|-
|B||Pontiac Acadian 1981-1984 (Canada only)
|-
|J||Pontiac Acadian S 1981-1982, Pontiac Acadian Scooter 1983-1984 (Canada only)
|-
|L||Pontiac T1000 1982, 1000 1983-1984
|-
|M||Pontiac T1000 1981
|-
|rowspan=10|GM X platform
|H||Chevrolet Citation 2-door coupe 1982-1983, Citation II 2-door coupe 1984
|-
|X||Chevrolet Citation hatchback 1981-1983, Citation II hatchback 1984
|-
|T||Pontiac Phoenix SJ 1982-1983, Phoenix SE 1984
|-
|Y||Pontiac Phoenix 1981-1984
|-
|Z||Pontiac Phoenix LJ 1981-1983, Phoenix LE 1984
|-
|B||Oldsmobile Omega 1981-1984
|-
|E||Oldsmobile Omega Brougham 1981-1984
|-
|B||Buick Skylark 1981-1982, Skylark Custom 1983-1984
|-
|C||Buick Skylark Limited 1981-1984
|-
|D||Buick Skylark Sport 1981-1982, Skylark T-Type 1983-1984
|-
|rowspan=1|GM Y platform
|Y||Chevrolet Corvette 1981-1982, 1984
|}

===American VIN format 1985-1986 Passenger Car===
GM has traditionally encoded the platform as the 4th character of the VIN. Other content includes an engine code and manufacturing plant. GM's VIN format is as follows:

&lt;table border=1 style=&quot;margin:auto;&quot;&gt;
&lt;tr&gt;
&lt;th&gt;Position&lt;/th&gt;
&lt;th&gt;Sample&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;Description&lt;/th&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;1&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td rowspan=3&gt;[[#GM WMIs|World Manufacturer Identifier]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;G&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;6&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;D&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[#Platform &amp; Series Codes 1985- Passenger Car|Platform]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;5&lt;/td&gt;
&lt;td&gt;W&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[#Platform &amp; Series Codes 1985- Passenger Car|Series Code]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;6&lt;/td&gt;
&lt;td&gt;6&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td rowspan=2&gt;[[#Body style codes 1981-1986|Body style]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;7&lt;/td&gt;
&lt;td&gt;9&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt; &lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;8&lt;/td&gt;
&lt;td&gt;Y&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[#American engine codes 1981-|Engine type]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;9&lt;/td&gt;
&lt;td&gt;0&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[Vehicle Identification Numbers (VIN codes)/Check digit |Check digit]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;10&lt;/td&gt;
&lt;td&gt;G&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[Vehicle Identification Numbers (VIN codes)/Model year|Model year]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;11&lt;/td&gt;
&lt;td&gt;9&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[#GM factories supplying North America|Factory ID]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;12&lt;/td&gt;
&lt;td&gt;1&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td rowspan=6&gt;Sequential number
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;13&lt;/td&gt;
&lt;td&gt;2&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;14&lt;/td&gt;
&lt;td&gt;3&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;15&lt;/td&gt;
&lt;td&gt;7&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;16&lt;/td&gt;
&lt;td&gt;6&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;17&lt;/td&gt;
&lt;td&gt;2&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;
&lt;/table&gt;

====Body style codes 1981-1986====
The Body type is specified as characters 6 and 7 of the American GM VIN for passenger cars from 1981-1986.

{| border=1 style=&quot;margin:auto;&quot;
!VIN
!Description
|-
|11,27,37,47,57,97||Two-Door Coupe/Sedan
|-
|07,08,77,87||Two-Door Hatchback
|-
|67||Two-Door Convertible
|-
|19,69||Four-Door Sedan
|-
|68||Four-Door Hatchback
|-
|23||Four-Door Limousine, 8-passenger (&quot;Limousine&quot;)
|-
|33||Four-Door Limousine w/Center Partition, 7-passenger (&quot;Formal Limousine&quot;)
|-
|35||Four-Door Station Wagon
|}

===American VIN format 1987- Passenger Car===
GM has traditionally encoded the platform as the 4th character of the VIN. Other content includes an engine code and manufacturing plant. GM's VIN format is as follows:

&lt;table border=1 style=&quot;margin:auto;&quot;&gt;
&lt;tr&gt;
&lt;th&gt;Position&lt;/th&gt;
&lt;th&gt;Sample&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;Description&lt;/th&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;1&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td rowspan=3&gt;[[#GM WMIs|World Manufacturer Identifier]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;G&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;6&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;D&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[#Platform &amp; Series Codes 1985- Passenger Car|Platform]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;5&lt;/td&gt;
&lt;td&gt;M&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[#Platform &amp; Series Codes 1985- Passenger Car|Series Code]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;6&lt;/td&gt;
&lt;td&gt;5&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[#Body style codes 1987- Passenger Car|Body style]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;7&lt;/td&gt;
&lt;td&gt;7&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[#American restraint types 1987-|Restraint type]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;8&lt;/td&gt;
&lt;td&gt;N&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[#American engine codes 1981-|Engine type]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;9&lt;/td&gt;
&lt;td&gt;0&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[Vehicle Identification Numbers (VIN codes)/Check digit |Check digit]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;10&lt;/td&gt;
&lt;td&gt;3&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[Vehicle Identification Numbers (VIN codes)/Model year|Model year]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;11&lt;/td&gt;
&lt;td&gt;0&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[#GM factories supplying North America|Factory ID]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;12&lt;/td&gt;
&lt;td&gt;1&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td rowspan=6&gt;Sequential number
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;13&lt;/td&gt;
&lt;td&gt;2&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;14&lt;/td&gt;
&lt;td&gt;3&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;15&lt;/td&gt;
&lt;td&gt;7&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;16&lt;/td&gt;
&lt;td&gt;6&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;17&lt;/td&gt;
&lt;td&gt;2&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;
&lt;/table&gt;

===American VIN format 1981-2009 Light Duty Truck &amp; Multi-Purpose Passenger Vehicle===
GM's VIN format is as follows:

&lt;table border=1 style=&quot;margin:auto;&quot;&gt;
&lt;tr&gt;
&lt;th&gt;Position&lt;/th&gt;
&lt;th&gt;Sample&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;Description&lt;/th&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;1&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td rowspan=3&gt;[[#GM WMIs|World Manufacturer Identifier]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;G&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;K&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;E&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[#GVWR/Brake System 1981-2009 Light Duty Truck &amp; Multi-Purpose Passenger Vehicle|GVWR/Brake System]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;5&lt;/td&gt;
&lt;td&gt;K&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[#Line &amp; Chassis Type 1981-1999 Light Duty Truck &amp; Multi-Purpose Passenger Vehicle|Line &amp; Chassis Type for 1981-1999]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;5&lt;/td&gt;
&lt;td&gt;K&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[#Line &amp; Chassis Type 2000-2009 Light Duty Truck &amp; Multi-Purpose Passenger Vehicle|Line &amp; Chassis Type for 2000-2009]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;6&lt;/td&gt;
&lt;td&gt;1&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[#Series 1981-1999 Light Duty Truck &amp; Multi-Purpose Passenger Vehicle|Series]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;7&lt;/td&gt;
&lt;td&gt;8&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[#Body style codes 1981-2009 Light Duty Truck &amp; Multi-Purpose Passenger Vehicle|Body type]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;8&lt;/td&gt;
&lt;td&gt;K&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[#Engine codes for light trucks|Engine type]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;9&lt;/td&gt;
&lt;td&gt;0&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[Vehicle Identification Numbers (VIN codes)/Check digit |Check digit]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;10&lt;/td&gt;
&lt;td&gt;N&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[Vehicle Identification Numbers (VIN codes)/Model year|Model year]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;11&lt;/td&gt;
&lt;td&gt;J&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[#GM factories supplying North America|Factory ID]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;12&lt;/td&gt;
&lt;td&gt;1&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td rowspan=6&gt;Sequential number
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;13&lt;/td&gt;
&lt;td&gt;2&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;14&lt;/td&gt;
&lt;td&gt;3&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;15&lt;/td&gt;
&lt;td&gt;7&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;16&lt;/td&gt;
&lt;td&gt;6&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;17&lt;/td&gt;
&lt;td&gt;2&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;
&lt;/table&gt;

====GVWR/Brake System 1981-2009 Light Duty Truck &amp; Multi-Purpose Passenger Vehicle====
The GVWR/Brake System is specified as character 4 of the American GM VIN for light trucks.

{| border=1 style=&quot;margin:auto;&quot;
!VIN
!GVWR Range in lbs. &amp; Weight Class
!Brake System
|-
|A||Class A: 0-3,000||Hydraulic
|-
|B||Class B: 3,001-4,000||Hydraulic
|-
|C||Class C: 4,001-5,000||Hydraulic
|-
|D||Class D: 5,001-6,000||Hydraulic
|-
|E||Class E: 6,001-7,000||Hydraulic
|-
|F||Class F: 7,001-8,000||Hydraulic
|-
|G||Class G: 8,001-9,000||Hydraulic
|-
|H||Class H: 9,001-10,000||Hydraulic
|-
|J||Class 3: 10,001-14,000||Hydraulic
|-
|K||Class 4: 14,001-16,000||Hydraulic
|-
|L||Class 5: 16,001-19,500||Hydraulic
|}

====Line &amp; Chassis Type 1981-1999 Light Duty Truck &amp; Multi-Purpose Passenger Vehicle====
The Line &amp; Chassis Type is specified as character 5 of the American GM VIN for light trucks.

{| border=1 style=&quot;margin:auto;&quot;
!VIN
!Description
|-
|B||Special Body Buick, Chevrolet
|-
|C||Chevy full-size pickups &amp; chassis cabs 2wd (C-series) '81-'86, '88-'99,&lt;br /&gt; GMC full-size pickups &amp; chassis cabs 2wd (C-series) '81-'86, Sierra 2wd (C-series) '88-'99
|-
|C||Chevy C10 Blazer 2wd ('81-'82), Tahoe 4-door 2wd ('95-'99), Suburban 2wd ('81-'86, '92-'99),&lt;br /&gt; GMC C1500 Jimmy 2wd ('81-'82), Yukon 4-door 2wd ('95-'99), Suburban 2wd ('81-'86, '92-'99)
|-
|D||Military Truck 4wd
|-
|E||'91-'97 Geo Tracker 2wd, '98-'99 Chevrolet Tracker 2wd
|-
|E||'97-'98 Chevy S-10 EV
|-
|G||Chevy/GMC full-size vans (Chevy Van, Sportvan, Express, GMC Vandura, Rally Van, Savana)
|-
|H||'93-'96 Chevy G30HD/GMC G3500HD cutaway van
|-
|H||Cadillac chassis cutaway/special body (Based on Rwd Fleetwood '93-'96, Fwd DeVille '97-'99)
|-
|J||'89-'97 Geo Tracker 4wd, '98-'99 Chevrolet Tracker 4wd
|-
|K||Chevy full-size pickups &amp; chassis cabs 4wd (K-series) '81-'86, '88-'99,&lt;br /&gt; GMC full-size pickups &amp; chassis cabs 4wd (K-series) '81-'86, Sierra 4wd (K-series) '88-'99
|-
|K||Chevy K10/K5 Blazer 4wd ('81-'86, '92-'94), Tahoe 4wd ('95-'99), Suburban 4wd ('81-'86, '92-'99),&lt;br /&gt; GMC K1500 Jimmy 4wd ('81-'86), Yukon 4wd ('92-'99), Suburban 4wd ('81-'86, '92-'99), '99 Cadillac Escalade 4wd
|-
|L||Chevy Luv 2wd '81-'82
|-
|L||Chevy Astro/GMC Safari 4wd '90-'99
|-
|M||Chevy Astro/GMC Safari 2wd '85-'99
|-
|P||Forward Control (includes Chevrolet Step-Van/GMC Value-Van, Chevy/GMC P-Series)
|-
|R||Chevy Luv 4wd '81-'82
|-
|R||Chevy full-size pickups &amp; chassis cabs 2wd (R-series), Suburban 2wd '87-'91,&lt;br /&gt; GMC full-size pickups &amp; chassis cabs 2wd (R-series), Suburban 2wd '87-'91
|-
|S||Chevy S-10 2wd ('82-'99), S-10 Blazer 2wd ('83-'94), Blazer 2wd ('95-'99), GMC S-15 2wd ('82-'90), Sonoma 2wd ('91-'99),&lt;br&gt; S-15 Jimmy 2wd ('83-'91), Jimmy 2wd ('92-'99), Isuzu Hombre 2wd ('96-'99)
|-
|T||Chevy S-10 4wd ('83-'99), S-10 Blazer 4wd ('83-'94), Blazer 4wd ('95-'99), GMC S-15 4wd ('83-'90), Sonoma 4wd ('91-'99), Syclone 4wd ('91),&lt;br&gt; S-15 Jimmy 4wd ('83-'91), Jimmy 4wd ('92-'99), Typhoon 4wd ('92-93), Envoy 4wd ('98-'99), Oldsmobile Bravada 4wd ('91-'94, '96-'99),&lt;br&gt; Isuzu Hombre 4wd ('98-'99)
|-
|U||Regular length All-Purpose Vehicle ('90-'99 U-body fwd minivans)
|-
|V||Chevy full-size pickups &amp; chassis cabs 4wd (V-series), V10/V1500 Blazer 4wd, Suburban 4wd '87-'91,&lt;br /&gt; GMC full-size pickups &amp; chassis cabs 4wd (V-series), V1500 Jimmy 4wd, Suburban 4wd '87-'91
|-
|W||'81-'87 Chevy El Camino, GMC Caballero
|-
|X||Extended length All-Purpose Vehicle ('97-'99 U-body fwd extended length minivans)
|-
|Z||Cadillac chassis cutaway/special body (Based on Rwd Fleetwood '81-'84, Fwd Fleetwood '85-'92)
|}

====Line &amp; Chassis Type 2000-2009 Light Duty Truck &amp; Multi-Purpose Passenger Vehicle====
The Line &amp; Chassis Type is specified as character 5 of the American GM VIN for light trucks.

{| border=1 style=&quot;margin:auto;&quot;
!VIN
!Description
|-
|A||Pontiac Aztek 2wd '01-'05, Buick Rendezvous 2wd '02-'07
|-
|A||Chevrolet HHR '06-'09, HHR Panel '07-'09
|-
|B||Pontiac Aztek Awd '01-'05, Buick Rendezvous Awd '02-'06
|-
|C||Chevy full-size pickups &amp; chassis cabs 2wd (C-series) '00, full-size chassis cabs 2wd (C3500HD) '01-'02, Silverado 2wd '00-'09, Silverado Classic 2wd '07,&lt;br /&gt; GMC Sierra 2wd (C-series) '00-'09, Sierra Classic 2wd '00, '07
|-
|C||Chevy Tahoe 2wd ('00-'09), Suburban 2wd ('00-'09), Avalanche 2wd ('02-'09),&lt;br /&gt; GMC Yukon 2wd ('00-'09), Yukon XL 2wd ('00-'09), Cadillac Escalade 2wd ('02-'09), Escalade ESV 2wd ('08-'09)
|-
|E||Chevrolet Tracker 2wd '00-'04
|-
|E||Cadillac SRX 2wd &amp; Awd '04-'09
|-
|G||Chevy/GMC full-size vans 2wd (Chevy Express, GMC Savana) '00-09
|-
|H||Chevy/GMC full-size vans 4wd (Chevy Express, GMC Savana) '03-09
|-
|H||Cadillac Commercial Chassis for Hearse (Based on Fwd DeVille '02-'05, DTS '06-'09)
|-
|H||Cadillac Professional Chassis for Limousine (Based on Fwd DeVille '00-'05, DTS '06-'07)
|-
|J||Chevrolet Tracker 4wd '00-'04
|-
|K||Chevy full-size pickups &amp; chassis cabs 4wd (K-series) '00, Silverado 4wd '00-'09, Silverado Classic 4wd '07,&lt;br /&gt; GMC Sierra 4wd (K-series) '00-'09, Sierra Classic 4wd '00, '07
|-
|K||Chevy Tahoe 4wd ('00-'09), Suburban 4wd ('00-'09), Avalanche 4wd ('02-'09), GMC Yukon 4wd ('00-'09), Yukon XL 4wd ('00-'09),&lt;br&gt; Cadillac Escalade 4wd ('00, '02-'09), Escalade ESV 4wd ('03-'09), Escalade EXT 4wd ('02-'09)
|-
|K||Cadillac Professional Chassis for Limousine (Based on Fwd DTS '08-'09)
|-
|L||Chevy Astro/GMC Safari 4wd '00-'05
|-
|L||Chevy Equinox 2wd &amp; Awd '05-'09, Pontiac Torrent 2wd &amp; Awd '06-'09, Saturn Vue 2wd &amp; Awd '08-'09
|-
|M||Chevy Astro/GMC Safari 2wd '00-'05
|-
|N||Hummer H2 '03-'09, H2 SUT '05-'09
|-
|N||Hummer H3 '06-'09, H3T '09
|-
|R||GMC Acadia 2wd, Saturn Outlook 2wd '07-'09, Buick Enclave 2wd '08-'09, Chevy Traverse 2wd '09
|-
|S||Chevy S-10 2wd ('00-'03), Blazer 2wd ('00-'05), GMC Sonoma 2wd ('00-'03), Jimmy 2wd ('00-'01), Isuzu Hombre 2wd ('00)
|-
|S||Chevy Trailblazer 2wd ('02-'09), SSR ('03-'06), GMC Envoy 2wd ('02-'09), Envoy XUV 2wd ('04-'05), Oldsmobile Bravada 2wd ('02-'04),&lt;br&gt; Buick Rainier 2wd ('04-'07), Isuzu Ascender 2wd ('03-'08)
|-
|S||Chevy Colorado 2wd ('04-'09), GMC Canyon 2wd ('04-'09), Isuzu i-series 2wd ('06-'08)
|-
|T||Chevy S-10 4wd ('00-'04), Blazer 4wd ('00-'05), GMC Sonoma 4wd ('00-'04), Jimmy 4wd ('00-'01, Canada only: '02-'05), Envoy 4wd ('00),&lt;br&gt; Oldsmobile Bravada 4wd ('00-'01), Isuzu Hombre 4wd ('00)
|-
|T||Chevy Trailblazer 4wd ('02-'09), GMC Envoy 4wd ('02-'09), Envoy XUV 2wd ('04-'05), Oldsmobile Bravada 4wd ('02-'04), Buick Rainier 4wd ('04-'07),&lt;br&gt; Isuzu Ascender 4wd ('03-'08), Saab 9-7X 4wd ('05-'09)
|-
|T||Chevy Colorado 4wd ('04-'09), GMC Canyon 4wd ('04-'09), Isuzu i-series 4wd ('06-'08)
|-
|U||Regular length All-Purpose Vehicle [Minivan] ('00-'04 Chevy Venture, Pontiac Montana)
|-
|U||Regular length All-Purpose Vehicle [Minivan] (Chevy Uplander [US: '06-'08, Canada only: '05-'09], Pontiac Montana SV6 [Canada only: '05-'09])
|-
|V||Extended length AWD All-Purpose Vehicle [Minivan] ('02-'04 Chevy Venture, Pontiac Montana, Oldsmobile Silhouette Extended length AWD)
|-
|V||Extended length FWD All-Purpose Vehicle [Minivan] ('05 Chevy Venture, Pontiac Montana Extended length FWD)
|-
|V||Extended length FWD All-Purpose Vehicle [Minivan] (Chevy Uplander ['05-'08, Canada only: '09], Pontiac Montana SV6 ['05-'06, Canada only: '07-'09],&lt;br&gt; Buick Terraza ['05-'07], Saturn Relay ['05-'07])
|-
|V||GMC Acadia Awd, Saturn Outlook Awd '07-'09, Buick Enclave Awd '08-'09, Chevy Traverse Awd '09
|-
|X||Extended length FWD All-Purpose Vehicle [Minivan] ('00-'04 Chevy Venture, Pontiac Montana, Oldsmobile Silhouette Extended length FWD)
|-
|X||Extended length AWD All-Purpose Vehicle [Minivan] ('05-'06 Chevy Uplander AWD, Pontiac Montana SV6 AWD, Buick Terraza AWD, Saturn Relay AWD)
|-
|Z||Saturn Vue 2wd &amp; Awd '02-'07
|}

====Series 1981-1999 Light Duty Truck &amp; Multi-Purpose Passenger Vehicle====
The Series is specified as character 6 of the American GM VIN for light trucks.

{| border=1 style=&quot;margin:auto;&quot;
!VIN
!Description
|-
|1||1/2 Ton (includes '96-'99 Isuzu Hombre)
|-
|2||3/4 Ton
|-
|3||1 Ton
|-
|8||1/2 Ton ('81-'87 El Camino, Caballero)
|-
|9||Cadillac, Buick, Chevrolet Commercial Body/Chassis
|-
|0||All-Purpose Vehicle ('90-'99 U-body fwd minivans)
|}

====Series 2000-2009 Light Duty Truck &amp; Multi-Purpose Passenger Vehicle====
The Series is specified as character 6 of the American GM VIN for light trucks.

{| border=1 style=&quot;margin:auto;&quot;
!VIN
!Description
|-
|1 &lt;br&gt; (following A)||Chevrolet HHR LS ('06-'07)
|-
|2 &lt;br&gt; (following A)||Chevrolet HHR LT ('06-'07)
|-
|3 &lt;br&gt; (following A)||Chevrolet HHR LT ('07)
|-
|1 &lt;br&gt; (following A)||Chevrolet HHR LS w/auto. trans. ('08-'09)
|-
|2 &lt;br&gt; (following A)||Chevrolet HHR 1LT w/auto. trans. ('08-'09)
|-
|3 &lt;br&gt; (following A)||Chevrolet HHR LS w/man. trans. ('08-'09)
|-
|4 &lt;br&gt; (following A)||Chevrolet HHR 1LT w/man. trans. ('08-'09)
|-
|5 &lt;br&gt; (following A)||Chevrolet HHR 2LT (all transmissions) ('08-'09)
|-
|6 &lt;br&gt; (following A)||Chevrolet HHR SS w/auto. trans. ('08-'09) (Pos. 1-3 of VIN is 3GN)
|-
|7 &lt;br&gt; (following A)||Chevrolet HHR SS w/man. trans. ('08-'09) (Pos. 1-3 of VIN is 3GN)
|-
|6 &lt;br&gt; (following A)||Chevrolet HHR Panel SS w/auto. trans. ('09) (Pos. 1-3 of VIN is 3GC)
|-
|7 &lt;br&gt; (following A)||Chevrolet HHR Panel SS w/man. trans. ('09) (Pos. 1-3 of VIN is 3GC)
|-
|8 &lt;br&gt; (following A)||Chevrolet HHR Panel LS w/auto. trans. ('08-'09) (Pos. 1-3 of VIN is 3GC)
|-
|9 &lt;br&gt; (following A)||Chevrolet HHR Panel LS w/man. trans. ('08-'09) (Pos. 1-3 of VIN is 3GC)
|-
|0 &lt;br&gt; (following A)||Chevrolet HHR Panel LT (all transmissions) ('08-'09) (Pos. 1-3 of VIN is 3GC)
|-
|1 &lt;br&gt; (following A)||Chevrolet HHR Panel LS ('08) (Pos. 1-3 of VIN is 3GC)
|-
|2 &lt;br&gt; (following A)||Chevrolet HHR Panel LT ('08) (Pos. 1-3 of VIN is 3GC)
|-
|3 &lt;br&gt; (following A)||Chevrolet HHR Panel LT ('08) (Pos. 1-3 of VIN is 3GC)
|-
|0 &lt;br&gt; (following V)||Chevrolet Venture Plus ('05) (Pos. 8 of VIN is E)
|-
|1 &lt;br&gt; (following V)||Chevrolet Venture Cargo ('05) (Pos. 8 of VIN is E)
|-
|2 &lt;br&gt; (following V)||Chevrolet Venture LS ('05) (Pos. 8 of VIN is E)
|-
|3 &lt;br&gt; (following V)||Chevrolet Venture LT ('05) (Pos. 8 of VIN is E)
|-
|2 &lt;br&gt; (following U)||Chevrolet Uplander LS SWB 2wd ('06-'08)
|-
|0 &lt;br&gt; (following V)||Chevrolet Uplander Base model 2wd ('05)
|-
|1 &lt;br&gt; (following V)||Chevrolet Uplander Cargo Van 2wd, Mobility (incomplete vehicle) 2wd ('05-'08)
|-
|2 &lt;br&gt; (following V)||Chevrolet Uplander LS 2wd ('05-'08)
|-
|3 &lt;br&gt; (following V)||Chevrolet Uplander LT 2wd ('05-'08)
|-
|3 &lt;br&gt; (following X)||Chevrolet Uplander LT Awd ('05-'06)
|-
|1 &lt;br&gt; (following M)||Chevrolet Astro 2wd ('00-'05)
|-
|1 &lt;br&gt; (following L)||Chevrolet Astro Awd ('00-'05)
|-
|1 &lt;br&gt; (following G)||Chevrolet Express 1500 series 2wd ('00-'09)
|-
|2 &lt;br&gt; (following G)||Chevrolet Express 2500 series 2wd ('00-'09)
|-
|3 &lt;br&gt; (following G)||Chevrolet Express 3500 series 2wd ('00-'09)
|-
|3 &lt;br&gt; (following G)||When VIN starts with 1GBK: Chevrolet Express 4500 series Cutaway 2wd ('09)
|-
|6 &lt;br&gt; (following G)||Chevrolet Express 1500 series LT 2wd ('01-'02)
|-
|1 &lt;br&gt; (following H)||Chevrolet Express 1500 series Awd ('03-'09)
|-
|2 &lt;br&gt; (following H)||Chevrolet Express 2500 series Awd ('03-'05)
|-
|1 &lt;br&gt; (following E)||Chevrolet Tracker Base model 2wd ('00-'04)
|-
|6 &lt;br&gt; (following E)||Chevrolet Tracker LT 2wd ('01-'04)
|-
|1 &lt;br&gt; (following J)||Chevrolet Tracker Base model 4wd ('00-'01, '04)
|-
|1 &lt;br&gt; (following J)||Chevrolet Tracker Base model w/1SB (Preferred) Equip. Group 4wd ('02-'03)
|-
|2 &lt;br&gt; (following J)||Chevrolet Tracker Base model w/1SA (Base) Equip. Group 4wd ('02-'03)
|-
|6 &lt;br&gt; (following J)||Chevrolet Tracker LT 4wd ('01-'04)
|-
|7 &lt;br&gt; (following J)||Chevrolet Tracker ZR2 4wd ('01-'04)
|-
|1 &lt;br&gt; (following L)||Chevrolet Equinox LS 2wd ('05-'09)
|-
|2 &lt;br&gt; (following L)||Chevrolet Equinox LS Awd ('05-'09)
|-
|6 &lt;br&gt; (following L)||Chevrolet Equinox LT 2wd ('05-'07)
|-
|7 &lt;br&gt; (following L)||Chevrolet Equinox LT Awd ('05-'07)
|-
|3 &lt;br&gt; (following L)||Chevrolet Equinox 1LT 2wd ('08-'09)
|-
|4 &lt;br&gt; (following L)||Chevrolet Equinox 1LT Awd ('08-'09)
|-
|5 &lt;br&gt; (following L)||Chevrolet Equinox 2LT 2wd ('08-'09)
|-
|6 &lt;br&gt; (following L)||Chevrolet Equinox 2LT Awd ('08-'09)
|-
|7 &lt;br&gt; (following L)||Chevrolet Equinox LTZ 2wd ('08-'09)
|-
|8 &lt;br&gt; (following L)||Chevrolet Equinox LTZ Awd ('08-'09)
|-
|9 &lt;br&gt; (following L)||Chevrolet Equinox Sport 2wd ('08-'09)
|-
|0 &lt;br&gt; (following L)||Chevrolet Equinox Sport Awd ('08-'09)
|-
|1 &lt;br&gt; (following R)||Chevrolet Traverse LS 2wd ('09)
|-
|2 &lt;br&gt; (following R)||Chevrolet Traverse LT 2wd ('09)
|-
|3 &lt;br&gt; (following R)||Chevrolet Traverse LTZ 2wd ('09)
|-
|1 &lt;br&gt; (following V)||Chevrolet Traverse LS Awd ('09)
|-
|2 &lt;br&gt; (following V)||Chevrolet Traverse LT Awd ('09)
|-
|3 &lt;br&gt; (following V)||Chevrolet Traverse LTZ Awd ('09)
|-
|1 &lt;br&gt; (following S)||Chevrolet Blazer 2wd ('00-'05)
|-
|1 &lt;br&gt; (following T)||Chevrolet Blazer 4wd ('00-'05)
|-
|1 &lt;br&gt; (following S)||Chevrolet Trailblazer 2wd ('02-'08), Trailblazer EXT 2wd ('02-'06)
|-
|1 &lt;br&gt; (following T)||Chevrolet Trailblazer 4wd ('02-'08), Trailblazer EXT 4wd ('02-'06)
|-
|3 &lt;br&gt; (following S)||Chevrolet Trailblazer LT 2wd ('09)
|-
|3 &lt;br&gt; (following T)||Chevrolet Trailblazer LT 4wd ('09)
|-
|5 &lt;br&gt; (following S)||Chevrolet Trailblazer SS 2wd ('09)
|-
|5 &lt;br&gt; (following T)||Chevrolet Trailblazer SS 4wd ('09)
|-
|1 &lt;br&gt; (following C)||Chevrolet Tahoe Limited 2wd ('00) [GMT400; 8th pos. of VIN is R]
|-
|1 &lt;br&gt; (following K)||Chevrolet Tahoe Z71 4wd ('00) [GMT400; 8th pos. of VIN is R]
|-
|1 &lt;br&gt; (following C)||Chevrolet Tahoe 2wd ('00-'06) [GMT800]
|-
|1 &lt;br&gt; (following K)||Chevrolet Tahoe 4wd ('00-'06) [GMT800]
|-
|1 &lt;br&gt; (following C)||Chevrolet Tahoe 2wd ('07-'08) [GMT900]
|-
|0 &lt;br&gt; (following C)||Chevrolet Tahoe Police/Special Service 2wd ('07-'09) [GMT900]
|-
|1 &lt;br&gt; (following C)||Chevrolet Tahoe LS 2wd ('09) [GMT900]
|-
|2 &lt;br&gt; (following C)||Chevrolet Tahoe LT 2wd ('09) [GMT900]
|-
|3 &lt;br&gt; (following C)||Chevrolet Tahoe LTZ 2wd ('09) [GMT900]
|-
|1 &lt;br&gt; (following K)||Chevrolet Tahoe 4wd ('07-'08) [GMT900]
|-
|0 &lt;br&gt; (following K)||Chevrolet Tahoe Police/Special Service 4wd ('07-'09) [GMT900]
|-
|1 &lt;br&gt; (following K)||Chevrolet Tahoe LS 4wd ('09) [GMT900]
|-
|2 &lt;br&gt; (following K)||Chevrolet Tahoe LT 4wd ('09) [GMT900]
|-
|3 &lt;br&gt; (following K)||Chevrolet Tahoe LTZ 4wd ('09) [GMT900]
|-
|1 &lt;br&gt; (following C)||Chevrolet Suburban 1500 series 2wd ('00-'08)
|-
|2 &lt;br&gt; (following C)||Chevrolet Suburban 2500 series 2wd ('00-'08)
|-
|1 &lt;br&gt; (following K)||Chevrolet Suburban 1500 series 4wd ('00-'08)
|-
|2 &lt;br&gt; (following K)||Chevrolet Suburban 2500 series 4wd ('00-'08)
|-
|1 &lt;br&gt; (following C)||Chevrolet Suburban 1500 series LS 2wd ('09)
|-
|2 &lt;br&gt; (following C)||Chevrolet Suburban 1500 series LT 2wd ('09)
|-
|3 &lt;br&gt; (following C)||Chevrolet Suburban 1500 series LTZ 2wd ('09)
|-
|4 &lt;br&gt; (following C)||Chevrolet Suburban 2500 series LS 2wd ('09)
|-
|5 &lt;br&gt; (following C)||Chevrolet Suburban 2500 series LT 2wd ('09)
|-
|1 &lt;br&gt; (following K)||Chevrolet Suburban 1500 series LS 4wd ('09)
|-
|2 &lt;br&gt; (following K)||Chevrolet Suburban 1500 series LT 4wd ('09)
|-
|3 &lt;br&gt; (following K)||Chevrolet Suburban 1500 series LTZ 4wd ('09)
|-
|4 &lt;br&gt; (following K)||Chevrolet Suburban 2500 series LS 4wd ('09)
|-
|5 &lt;br&gt; (following K)||Chevrolet Suburban 2500 series LT 4wd ('09)
|-
|1 &lt;br&gt; (following C)||Chevrolet Avalanche 1500 series 2wd ('02-'08)
|-
|2 &lt;br&gt; (following C)||Chevrolet Avalanche 2500 series 2wd ('02-'03)
|-
|1 &lt;br&gt; (following K)||Chevrolet Avalanche 1500 series 4wd ('02-'08)
|-
|2 &lt;br&gt; (following K)||Chevrolet Avalanche 2500 series 4wd ('02-'06)
|-
|1 &lt;br&gt; (following C)||Chevrolet Avalanche 1500 series LS 2wd ('09)
|-
|2 &lt;br&gt; (following C)||Chevrolet Avalanche 1500 series LT 2wd ('09)
|-
|3 &lt;br&gt; (following C)||Chevrolet Avalanche 1500 series LTZ 2wd ('09)
|-
|1 &lt;br&gt; (following K)||Chevrolet Avalanche 1500 series LS 4wd ('09)
|-
|2 &lt;br&gt; (following K)||Chevrolet Avalanche 1500 series LT 4wd ('09)
|-
|3 &lt;br&gt; (following K)||Chevrolet Avalanche 1500 series LTZ 4wd ('09)
|-
|1 &lt;br&gt; (following S)||Chevrolet SSR 2wd ('03-'06)
|-
|6 &lt;br&gt; (following S)||Chevrolet SSR Signature Series 2wd ('03) &lt;br&gt; [All SSR Signature Series also have a 0 in the 12th pos. of VIN whereas all other SSRs have a 1 in the 12th pos. of VIN]
|-
|1 &lt;br&gt; (following S)||Chevrolet S-10 2wd ('00-'03)
|-
|1 &lt;br&gt; (following T)||Chevrolet S-10 4wd ('00-'04)
|-
|1 &lt;br&gt; (following S)||Chevrolet Colorado 2wd ('04-'07)
|-
|1 &lt;br&gt; (following T)||Chevrolet Colorado 4wd ('04-'07)
|-
|1 &lt;br&gt; (following C)||Chevrolet Silverado 1500 2wd ('00-'06), Silverado Classic 1500 2wd ('07) [GMT800]
|-
|1 &lt;br&gt; (following K)||Chevrolet Silverado 1500 4wd ('00-'06), Silverado Classic 1500 4wd ('07) [GMT800]
|-
|1 &lt;br&gt; (following C)||Chevrolet Silverado 1500HD 2wd ('01-'03, '05-'06), Silverado Classic 1500HD 2wd ('07) [GMT800] (Pos. 8 of VIN is U]
|-
|1 &lt;br&gt; (following K)||Chevrolet Silverado 1500HD 4wd ('01-'03, '05-'06), Silverado Classic 1500HD 2wd ('07) [GMT800] (Pos. 8 of VIN is U]
|-
|2 &lt;br&gt; (following C)||Chevrolet Silverado 2500 2wd ('00) [GMT800] (Pos. 8 of VIN is T or U]
|-
|2 &lt;br&gt; (following K)||Chevrolet Silverado 2500 4wd ('00) [GMT800] (Pos. 8 of VIN is U]
|-
|2 &lt;br&gt; (following C)||Chevrolet C2500 2wd ('00) [GMT400] (Pos. 8 of VIN is F, J, or R)
|-
|3 &lt;br&gt; (following C)||Chevrolet C3500 2wd ('00) [GMT400] (Pos. 8 of VIN is F, J, or R)
|-
|3 &lt;br&gt; (following C)||when 4th pos. of VIN is K: Chevrolet C3500HD 2wd ('00-'02) [GMT400]
|-
|2 &lt;br&gt; (following K)||Chevrolet K2500 4wd ('00) [GMT400] (Pos. 8 of VIN is F, J, or R)
|-
|3 &lt;br&gt; (following K)||Chevrolet K3500 4wd ('00) [GMT400] (Pos. 8 of VIN is F, J, or R)
|-
|2 &lt;br&gt; (following C)||Chevrolet Silverado 2500 2wd ('01-'06) [GMT800], Silverado Classic 2500 2wd ('07)
|-
|2 &lt;br&gt; (following K)||Chevrolet Silverado 2500 4wd ('01-'06) [GMT800], Silverado Classic 2500 4wd ('07)
|-
|3 &lt;br&gt; (following C)||Chevrolet Silverado 3500 2wd ('01-'06) [GMT800], Silverado Classic 3500 2wd ('07)
|-
|3 &lt;br&gt; (following K)||Chevrolet Silverado 3500 4wd ('01-'06) [GMT800], Silverado Classic 3500 4wd ('07)
|-
|1 &lt;br&gt; (following C)||Chevrolet Silverado 1500 2wd ('07-'08) [GMT900]
|-
|1 &lt;br&gt; (following K)||Chevrolet Silverado 1500 4wd ('07-'08) [GMT900]
|-
|2 &lt;br&gt; (following C)||Chevrolet Silverado 2500 2wd ('07-'08) [GMT900]
|-
|2 &lt;br&gt; (following K)||Chevrolet Silverado 2500 4wd ('07-'08) [GMT900]
|-
|3 &lt;br&gt; (following C)||Chevrolet Silverado 3500 2wd ('07-'08) [GMT900]
|-
|3 &lt;br&gt; (following K)||Chevrolet Silverado 3500 4wd ('07-'08) [GMT900]
|-
|1 &lt;br&gt; (following V)||Pontiac Montana Mobility (incomplete vehicle) 2wd ('05) (Pos. 8 of VIN is E)
|-
|2 &lt;br&gt; (following V)||Pontiac Montana ('05) (Pos. 8 of VIN is E)
|-
|0 &lt;br&gt; (following V)||Pontiac Montana SV6 1SA 2wd ('05)
|-
|3 &lt;br&gt; (following V)||Pontiac Montana SV6 1SB 2wd ('05)
|-
|2 &lt;br&gt; (following X)||Pontiac Montana SV6 1SA Awd ('05)
|-
|3 &lt;br&gt; (following X)||Pontiac Montana SV6 1SB Awd ('05)
|-
|1 &lt;br&gt; (following V)||Pontiac Montana SV6 Mobility (incomplete vehicle) 2wd ('06)
|-
|3 &lt;br&gt; (following V)||Pontiac Montana SV6 2wd ('06)
|-
|3 &lt;br&gt; (following X)||Pontiac Montana SV6 Awd ('06)
|-
|0 &lt;br&gt; (following A)||Pontiac Aztek 2wd ('01-'05)
|-
|0 &lt;br&gt; (following B)||Pontiac Aztek Awd ('01-'05)
|-
|6 &lt;br&gt; (following L)||Pontiac Torrent 2wd ('06-'07)
|-
|7 &lt;br&gt; (following L)||Pontiac Torrent Awd ('06-'07)
|-
|3 &lt;br&gt; (following L)||Pontiac Torrent Base model 2wd ('08-'09)
|-
|4 &lt;br&gt; (following L)||Pontiac Torrent Base model Awd ('08-'09)
|-
|5 &lt;br&gt; (following L)||Pontiac Torrent GXP 2wd ('08-'09)
|-
|6 &lt;br&gt; (following L)||Pontiac Torrent GXP Awd ('08-'09)
|-
|0 &lt;br&gt; (following X)||Oldsmobile Silhouette extended length GL 2wd ('00, '03-'04), GLS 2wd ('00-'04)
|-
|1 &lt;br&gt; (following X)||Oldsmobile Silhouette extended length Premiere 2wd ('00-'04)
|-
|2 &lt;br&gt; (following X)||Oldsmobile Silhouette extended length GL 2wd ('01-'02)
|-
|0 &lt;br&gt; (following V)||Oldsmobile Silhouette extended length GLS Awd ('02-'04)
|-
|1 &lt;br&gt; (following V)||Oldsmobile Silhouette extended length Premiere Awd ('02-'04)
|-
|1 &lt;br&gt; (following S)||Oldsmobile Bravada 2wd ('02-'04)
|-
|1 &lt;br&gt; (following T)||Oldsmobile Bravada 4wd ('00-'04)
|-
|1 &lt;br&gt; (following V)||Buick Terraza Mobility (incomplete vehicle) 2wd ('05-'07)
|-
|2 &lt;br&gt; (following V)||Buick Terraza CX 2wd ('05-'07), CX Plus 2wd ('07)
|-
|3 &lt;br&gt; (following V)||Buick Terraza CXL 2wd ('05-'07)
|-
|2 &lt;br&gt; (following X)||Buick Terraza CX Awd ('05-'06)
|-
|3 &lt;br&gt; (following X)||Buick Terraza CXL Awd ('05-'06)
|-
|0 &lt;br&gt; (following A)||Buick Rendezvous 2wd ('02-'07)
|-
|0 &lt;br&gt; (following B)||Buick Rendezvous Awd ('02-'06)
|-
|1 &lt;br&gt; (following S)||Buick Rainier 2wd ('04-'07)
|-
|1 &lt;br&gt; (following T)||Buick Rainier 4wd ('04-'06)
|-
|1 &lt;br&gt; (following R)||Buick Enclave CX 2wd ('08-'09)
|-
|2 &lt;br&gt; (following R)||Buick Enclave CXL 2wd ('08-'09)
|-
|1 &lt;br&gt; (following V)||Buick Enclave CX Awd ('08-'09)
|-
|2 &lt;br&gt; (following V)||Buick Enclave CXL Awd ('08-'09)
|-
|9 &lt;br&gt; (following H)|| Cadillac Commercial Chassis for Limousine or Hearse based on DeVille ('00-'01)
|-
|0 &lt;br&gt; (following H)|| Cadillac Commercial Chassis for Hearse based on DeVille ('02-'05) or DTS ('06-'09)
|-
|9 &lt;br&gt; (following H)|| Cadillac Professional Chassis for Limousine based on DeVille ('02-'05) or DTS ('06-'07)
|-
|9 &lt;br&gt; (following K)|| Cadillac Professional Chassis for Limousine based on DTS ('08-'09)
|-
|6 &lt;br&gt; (following E)||Cadillac SRX ('04-'07)
|-
|2 &lt;br&gt; (following E)||Cadillac SRX RWD V8 ('08-'09)
|-
|4 &lt;br&gt; (following E)||Cadillac SRX AWD V6 ('08-'09)
|-
|5 &lt;br&gt; (following E)||Cadillac SRX AWD V8 ('08-'09)
|-
|6 &lt;br&gt; (following E)||When Pos. 8 of VIN is 7: Cadillac SRX RWD V6 ('08)
|-
|6 &lt;br&gt; (following E)||When Pos. 8 of VIN is A: Cadillac SRX AWD V8 ('08)
|-
|6 &lt;br&gt; (following E)||Cadillac SRX RWD V6 ('09)
|-
|1 &lt;br&gt; (following K)||Cadillac Escalade 4wd (Early '00)
|-
|4 &lt;br&gt; (following K)||Cadillac Escalade Platinum Edition 4wd ('08), Escalade ESV Platinum Edition 4wd ('08)
|-
|6 &lt;br&gt; (following C)||Cadillac Escalade 2wd ('02-'08), Escalade ESV 2wd ('08)
|-
|6 &lt;br&gt; (following K)||Cadillac Escalade 4wd (Mid '00, '02-'08), Escalade ESV 4wd ('03-'08), Escalade EXT 4wd ('02-'08)
|-
|1 &lt;br&gt; (following C)||Cadillac Escalade 2wd Base model ('09), Escalade ESV 2wd Base model ('09)
|-
|2 &lt;br&gt; (following C)||Cadillac Escalade 2wd w/Ultra Luxury Collection ('09), Escalade ESV 2wd w/Ultra Luxury Collection ('09)
|-
|3 &lt;br&gt; (following C)||Cadillac Escalade 2wd w/Platinum Edition ('09), Escalade ESV 2wd w/Platinum Edition ('09)
|-
|4 &lt;br&gt; (following C)||Cadillac Escalade Hybrid 2wd Base model ('09)
|-
|5 &lt;br&gt; (following C)||Cadillac Escalade 2wd w/Sport Package ('09), Escalade ESV 4wd w/Sport Package ('09)
|-
|1 &lt;br&gt; (following K)||Cadillac Escalade 4wd Base model ('09), Escalade ESV 4wd Base model ('09), Escalade EXT 4wd Base model ('09)
|-
|2 &lt;br&gt; (following K)||Cadillac Escalade 4wd w/Ultra Luxury Collection ('09), Escalade ESV 4wd w/Ultra Luxury Collection ('09),&lt;br&gt; Escalade EXT 4wd w/Ultra Luxury Collection ('09)
|-
|3 &lt;br&gt; (following K)||Cadillac Escalade 4wd w/Platinum Edition ('09), Escalade ESV 4wd w/Platinum Edition ('09)
|-
|4 &lt;br&gt; (following K)||Cadillac Escalade Hybrid 4wd Base model ('09)
|-
|5 &lt;br&gt; (following K)||Cadillac Escalade 4wd w/Sport Package ('09), Escalade ESV 4wd w/Sport Package ('09), Escalade EXT 4wd w/Sport Package ('09)
|-
|1 &lt;br&gt; (following M)||GMC Safari 2wd ('00-'05)
|-
|1 &lt;br&gt; (following L)||GMC Safari Awd ('00-'05)
|-
|1 &lt;br&gt; (following G)||GMC Savana 1500 series 2wd ('00-'09)
|-
|2 &lt;br&gt; (following G)||GMC Savana 2500 series 2wd ('00-'09)
|-
|3 &lt;br&gt; (following G)||GMC Savana 3500 series 2wd ('00-'09)
|-
|3 &lt;br&gt; (following G)||When VIN starts with 1GBK: GMC Savana 4500 series Cutaway 2wd ('09)
|-
|6 &lt;br&gt; (following G)||GMC Savana 1500 series SLT 2wd ('01-'02)
|-
|1 &lt;br&gt; (following H)||GMC Savana 1500 series Awd ('03-'09)
|-
|2 &lt;br&gt; (following H)||GMC Savana 2500 series Awd ('03-'05)
|-
|1 &lt;br&gt; (following R)||GMC Acadia SLE 2wd ('07-'09)
|-
|2 &lt;br&gt; (following R)||GMC Acadia SLT-1 2wd ('07-'09)
|-
|3 &lt;br&gt; (following R)||GMC Acadia SLT-2 2wd ('07-'09)
|-
|1 &lt;br&gt; (following V)||GMC Acadia SLE Awd ('07-'09)
|-
|2 &lt;br&gt; (following V)||GMC Acadia SLT-1 Awd ('07-'09)
|-
|3 &lt;br&gt; (following V)||GMC Acadia SLT-2 Awd ('07-'09)
|-
|1 &lt;br&gt; (following S)||GMC Jimmy 2wd ('00-'01)
|-
|6 &lt;br&gt; (following S)||GMC Jimmy Diamond Edition 2wd ('01)
|-
|1 &lt;br&gt; (following T)||GMC Jimmy 4wd ('00-'01 &amp; '02-'05 in Canada)
|-
|6 &lt;br&gt; (following T)||GMC Jimmy Diamond Edition 4wd ('01)
|-
|1 &lt;br&gt; (following S)||GMC Envoy 2wd ('02-'08), Envoy XL 2wd ('02-'06), Envoy XUV 2wd ('04-'05)
|-
|6 &lt;br&gt; (following S)||GMC Envoy Denali 2wd ('05-'08), Envoy XL Denali 2wd ('05-'06)
|-
|1 &lt;br&gt; (following T)||GMC Envoy 4wd ('02-'08), Envoy XL 4wd ('02-'06), Envoy XUV 4wd ('04-'05)
|-
|6 &lt;br&gt; (following T)||GMC Envoy Denali 4wd ('05-'08), Envoy XL Denali 4wd ('05-'06)
|-
|3 &lt;br&gt; (following S)||GMC Envoy SLE 2wd ('09)
|-
|3 &lt;br&gt; (following T)||GMC Envoy SLE 4wd ('09)
|-
|4 &lt;br&gt; (following S)||GMC Envoy SLT 2wd ('09)
|-
|4 &lt;br&gt; (following T)||GMC Envoy SLT 4wd ('09)
|-
|5 &lt;br&gt; (following S)||GMC Envoy Denali 2wd ('09)
|-
|5 &lt;br&gt; (following T)||GMC Envoy Denali 4wd ('09)
|-
|1 &lt;br&gt; (following C)||GMC Yukon 2wd ('00-'06) [GMT800]
|-
|1 &lt;br&gt; (following K)||GMC Yukon 4wd ('00-'06) [GMT800]
|-
|1 &lt;br&gt; (following C)||GMC Yukon 2wd ('07-'08) [GMT900]
|-
|1 &lt;br&gt; (following K)||GMC Yukon 4wd ('07-'08) [GMT900]
|-
|1 &lt;br&gt; (following C)||GMC Yukon 2wd ('09) [GMT900]
|-
|1 &lt;br&gt; (following K)||GMC Yukon 4wd ('09) [GMT900]
|-
|1 &lt;br&gt; (following C)||GMC Yukon Hybrid 2wd ('09) [GMT900; 8th pos. of VIN is 5]
|-
|1 &lt;br&gt; (following K)||GMC Yukon Hybrid 4wd ('09) [GMT900; 8th pos. of VIN is 5]
|-
|2 &lt;br&gt; (following C)||GMC Yukon SLE 2wd ('09) [GMT900]
|-
|3 &lt;br&gt; (following C)||GMC Yukon SLT 2wd ('09) [GMT900]
|-
|2 &lt;br&gt; (following K)||GMC Yukon SLE 4wd ('09) [GMT900]
|-
|3 &lt;br&gt; (following K)||GMC Yukon SLT 4wd ('09) [GMT900]
|-
|1 &lt;br&gt; (following K)||GMC Yukon Denali 4wd (Early '00) [GMT400; 8th pos. of VIN is R]
|-
|6 &lt;br&gt; (following K)||GMC Yukon Denali 4wd (Mid '00) [GMT400; 8th pos. of VIN is R]
|-
|6 &lt;br&gt; (following K)||GMC Yukon Denali 4wd ('01-'06) [GMT800]
|-
|6 &lt;br&gt; (following C)||GMC Yukon Denali 2wd ('08) [GMT900]
|-
|6 &lt;br&gt; (following K)||GMC Yukon Denali 4wd ('07-'08) [GMT900]
|-
|0 &lt;br&gt; (following C)||GMC Yukon Denali 2wd ('09) [GMT900]
|-
|0 &lt;br&gt; (following K)||GMC Yukon Denali 4wd ('09) [GMT900]
|-
|1 &lt;br&gt; (following K)||GMC Yukon Denali 4wd ('09) [GMT900; 8th pos. of VIN is 2]
|-
|1 &lt;br&gt; (following C)||GMC Yukon Denali Hybrid 2wd ('09) [GMT900; 8th pos. of VIN is 5]
|-
|1 &lt;br&gt; (following K)||GMC Yukon Denali Hybrid 4wd ('09) [GMT900; 8th pos. of VIN is 5]
|-
|1 &lt;br&gt; (following C)||GMC Yukon XL 1500 series 2wd ('00-'08)
|-
|2 &lt;br&gt; (following C)||GMC Yukon XL 2500 series 2wd ('00-'08)
|-
|6 &lt;br&gt; (following C)||GMC Yukon XL Denali 1500 series 2wd ('08)
|-
|1 &lt;br&gt; (following K)||GMC Yukon XL 1500 series 4wd ('00-'08)
|-
|2 &lt;br&gt; (following K)||GMC Yukon XL 2500 series 4wd ('00-'08)
|-
|6 &lt;br&gt; (following K)||GMC Yukon XL Denali 1500 series 4wd ('01-'08)
|-
|1 &lt;br&gt; (following C)||GMC Yukon XL 1500 series 2wd ('09)
|-
|2 &lt;br&gt; (following C)||GMC Yukon XL 1500 series SLE 2wd ('09)
|-
|3 &lt;br&gt; (following C)||GMC Yukon XL 1500 series SLT 2wd ('09)
|-
|4 &lt;br&gt; (following C)||GMC Yukon XL 2500 series 2wd ('09)
|-
|5 &lt;br&gt; (following C)||GMC Yukon XL 2500 series SLE 2wd ('09)
|-
|6 &lt;br&gt; (following C)||GMC Yukon XL 2500 series SLT 2wd ('09)
|-
|0 &lt;br&gt; (following C)||GMC Yukon XL Denali 1500 series 2wd ('09)
|-
|1 &lt;br&gt; (following K)||GMC Yukon XL 1500 series 4wd ('09)
|-
|2 &lt;br&gt; (following K)||GMC Yukon XL 1500 series SLE 4wd ('09)
|-
|3 &lt;br&gt; (following K)||GMC Yukon XL 1500 series SLT 4wd ('09)
|-
|4 &lt;br&gt; (following K)||GMC Yukon XL 2500 series 4wd ('09)
|-
|5 &lt;br&gt; (following K)||GMC Yukon XL 2500 series SLE 4wd ('09)
|-
|6 &lt;br&gt; (following K)||GMC Yukon XL 2500 series SLT 4wd ('09)
|-
|0 &lt;br&gt; (following K)||GMC Yukon XL Denali 1500 series 4wd ('09)
|-
|1 &lt;br&gt; (following K)||GMC Yukon XL Denali 1500 series 4wd ('09) [8th pos. of VIN is 2]
|-
|1 &lt;br&gt; (following S)||GMC Sonoma 2wd ('00-'03)
|-
|1 &lt;br&gt; (following T)||GMC Sonoma 4wd ('00-'04)
|-
|1 &lt;br&gt; (following S)||GMC Canyon 2wd ('04-'07)
|-
|1 &lt;br&gt; (following T)||GMC Canyon 4wd ('04-'07)
|-
|1 &lt;br&gt; (following C)||GMC Sierra 1500 2wd ('00-'06), Sierra Classic 1500 2wd ('07) [GMT800]
|-
|1 &lt;br&gt; (following K)||GMC Sierra 1500 4wd ('00-'06), Sierra Classic 1500 4wd ('07) [GMT800]
|-
|1 &lt;br&gt; (following C)||GMC Sierra 1500HD 2wd ('01-'03, '05-'06), Sierra Classic 1500HD 2wd ('07) [GMT800] (Pos. 8 of VIN is U]
|-
|1 &lt;br&gt; (following K)||GMC Sierra 1500HD 4wd ('01-'03, '05-'06), Sierra Classic 1500HD 2wd ('07) [GMT800] (Pos. 8 of VIN is U]
|-
|6 &lt;br&gt; (following K)||GMC Sierra C3 1500 Awd ('01) [GMT800]
|-
|6 &lt;br&gt; (following K)||GMC Sierra Denali 1500 Awd ('02-'06), Sierra Classic Denali 1500 Awd ('07) [GMT800]
|-
|2 &lt;br&gt; (following C)||GMC Sierra 2500 2wd ('00) [GMT800] (Pos. 8 of VIN is T or U]
|-
|2 &lt;br&gt; (following K)||GMC Sierra 2500 4wd ('00) [GMT800] (Pos. 8 of VIN is U]
|-
|2 &lt;br&gt; (following C)||GMC Sierra Classic C2500 2wd ('00) [GMT400] (Pos. 8 of VIN is F, J, or R)
|-
|3 &lt;br&gt; (following C)||GMC Sierra Classic C3500 2wd ('00) [GMT400] (Pos. 8 of VIN is F, J, or R)
|-
|3 &lt;br&gt; (following C)||when 4th pos. of VIN is K: GMC Sierra C3500HD 2wd ('00-'02) [GMT400]
|-
|2 &lt;br&gt; (following K)||GMC Sierra Classic K2500 4wd ('00) [GMT400] (Pos. 8 of VIN is F, J, or R)
|-
|3 &lt;br&gt; (following K)||GMC Sierra Classic K3500 4wd ('00) [GMT400] (Pos. 8 of VIN is F, J, or R)
|-
|2 &lt;br&gt; (following C)||GMC Sierra 2500 2wd ('01-'06), Sierra Classic 2500 2wd ('07) [GMT800]
|-
|2 &lt;br&gt; (following K)||GMC Sierra 2500 4wd ('01-'06), Sierra Classic 2500 4wd ('07) [GMT800]
|-
|3 &lt;br&gt; (following C)||GMC Sierra 3500 2wd ('01-'06), Sierra Classic 3500 2wd ('07) [GMT800]
|-
|3 &lt;br&gt; (following K)||GMC Sierra 3500 4wd ('01-'06), Sierra Classic 3500 4wd ('07) [GMT800]
|-
|1 &lt;br&gt; (following C)||GMC Sierra 1500 2wd ('07-'08) [GMT900]
|-
|6 &lt;br&gt; (following C)||GMC Sierra Denali 1500 2wd ('07-'08) [GMT900]
|-
|1 &lt;br&gt; (following K)||GMC Sierra 1500 4wd ('07-'08) [GMT900]
|-
|6 &lt;br&gt; (following K)||GMC Sierra Denali 1500 Awd ('07-'08) [GMT900]
|-
|2 &lt;br&gt; (following C)||GMC Sierra 2500 2wd ('07-'08) [GMT900]
|-
|2 &lt;br&gt; (following K)||GMC Sierra 2500 4wd ('07-'08) [GMT900]
|-
|3 &lt;br&gt; (following C)||GMC Sierra 3500 2wd ('07-'08) [GMT900]
|-
|3 &lt;br&gt; (following K)||GMC Sierra 3500 4wd ('07-'08) [GMT900]
|-
|0 &lt;br&gt; (following V)||Saturn Relay ''2'' 2wd ('05-'07)
|-
|2 &lt;br&gt; (following V)||Saturn Relay ''3'' 2wd ('05-'07)
|-
|5 &lt;br&gt; (following V)||Saturn Relay ''1'' 2wd ('07)
|-
|2 &lt;br&gt; (following X)||Saturn Relay ''3'' Awd ('05-'06)
|-
|2 &lt;br&gt; (following Z)||Saturn Vue I4, Man. Trans., Fwd ('02-'07)
|-
|3 &lt;br&gt; (following Z)||Saturn Vue I4, Auto. Trans., Fwd ('02-'07)
|-
|4 &lt;br&gt; (following Z)||Saturn Vue I4, Auto. Trans., Awd ('02-'05)
|-
|5 &lt;br&gt; (following Z)||Saturn Vue V6, Auto. Trans., Fwd ('03-'07)
|-
|6 &lt;br&gt; (following Z)||Saturn Vue V6, Auto. Trans., Awd ('02-'07)
|-
|3 &lt;br&gt; (following L)||Saturn Vue XE Fwd ('08-'09)
|-
|4 &lt;br&gt; (following L)||Saturn Vue XE Awd ('08-'09)
|-
|5 &lt;br&gt; (following L)||when 4th pos. of VIN is C: Saturn Vue XR Fwd ('08-'09)
|-
|7 &lt;br&gt; (following L)||Saturn Vue XR Awd (Early '08)
|-
|6 &lt;br&gt; (following L)||Saturn Vue XR Awd (Mid '08-'09)
|-
|5 &lt;br&gt; (following L)||when 4th pos. of VIN is D: Saturn Vue XR Awd ('09)
|-
|1 &lt;br&gt; (following L)||Saturn Vue Red Line Fwd ('08-'09)
|-
|9 &lt;br&gt; (following L)||Saturn Vue Red Line Awd ('08)
|-
|0 &lt;br&gt; (following L)||Saturn Vue Red Line Awd ('09)
|-
|0 &lt;br&gt; (following L)||Saturn Vue Green Line Fwd ('08)
|-
|9 &lt;br&gt; (following L)||Saturn Vue Green Line Fwd ('09)
|-
|1 &lt;br&gt; (following R)||Saturn Outlook XE 2wd ('07-'09)
|-
|2 &lt;br&gt; (following R)||Saturn Outlook XR 2wd ('07-'09)
|-
|3 &lt;br&gt; (following R)||Saturn Outlook XR 2wd w/Touring Package ('07-'09)
|-
|1 &lt;br&gt; (following V)||Saturn Outlook XE Awd ('07-'09)
|-
|2 &lt;br&gt; (following V)||Saturn Outlook XR Awd ('07-'09)
|-
|3 &lt;br&gt; (following V)||Saturn Outlook XR Awd w/Touring Package ('07-'09)
|-
|1 &lt;br&gt; (following N)||Hummer H3 ('06-'07)
|-
|1 &lt;br&gt; (following N)||Hummer H3 Base model ('08)
|-
|3 &lt;br&gt; (following N)||Hummer H3 Adventure ('08)
|-
|4 &lt;br&gt; (following N)||Hummer H3 Luxury ('08)
|-
|5 &lt;br&gt; (following N)||Hummer H3 X ('08)
|-
|6 &lt;br&gt; (following N)||Hummer H3 Alpha ('08)
|-
|1 &lt;br&gt; (following N)||Hummer H3, H3T ('09)
|-
|2 &lt;br&gt; (following N)||Hummer H2 ('03-'08), H2 SUT ('05-'08)
|-
|2 &lt;br&gt; (following N)||Hummer H2 Base model ('09), H2 SUT Base model ('09)
|-
|7 &lt;br&gt; (following N)||Hummer H2 Adventure ('09)
|-
|8 &lt;br&gt; (following N)||Hummer H2 Luxury ('09)
|-
|9 &lt;br&gt; (following N)||Hummer H2 SUT Adventure ('09)
|-
|0 &lt;br&gt; (following N)||Hummer H2 SUT Luxury ('09)
|-
|1 (following S)||Isuzu Hombre 2wd ('00), Isuzu i280 2wd ('06), Isuzu i290 2wd ('07-'08), Isuzu i370 2wd ('07-'08)
|-
|2 (following S)||Isuzu i290 2wd w/Preferred Equip. Pkg. ('08), Isuzu i370 2wd w/Comfort Pkg. or upgrade model ('08)
|-
|1 (following T)||Isuzu Hombre 4wd ('00), Isuzu i350 4wd ('06), Isuzu i370 4wd ('07-'08)
|-
|2 (following T)||Isuzu i370 4wd w/Comfort Pkg. ('08)
|-
|1 (following S)||Isuzu Ascender 2wd ('03-'08)
|-
|1 (following T)||Isuzu Ascender 4wd ('03-'08)
|-
|1 (following T)||Saab 9-7X ('05-'08: All, '09: 4.2i, 5.3i)
|-
|2 (following T)||Saab 9-7X Aero ('09)
|}

====Body style codes 1981-2009 Light Duty Truck &amp; Multi-Purpose Passenger Vehicle====
The Body type is specified as character 7 of the American GM VIN for light trucks.

{| border=1 style=&quot;margin:auto;&quot;
!VIN
!Description
|-
|0||Sedan Pickup/Pickup Delivery ('81-'87 El Camino, Caballero)
|-
|0||Cadillac, Buick, Chevrolet Commercial Body/Chassis
|-
|0||Chassis Only
|-
|1||Cutaway Van
|-
|2||Forward Control ('81-'03) (includes '93-'95 Chevy G30HD/GMC G3500HD)
|-
|2||Sport Utility Truck (SUT) ('04-'09 Avalanche &amp; Escalade EXT, '04-'05 Envoy XUV, '05-'09 Hummer H2 SUT)
|-
|3||Four-Door Cab pickup (Crew Cab) (includes '06-'08 Isuzu i-Series Crew Cab, '09 Hummer H3T)
|-
|3||4-door Passenger Minivan ('97-'09 U-bodies)
|-
|3||4-door SUV or MPV ('06-'09 HHR) (also includes '02-'03 Avalanche &amp; Escalade EXT) ('05-'09 Saab 9-7X)
|-
|4||Two-Door Cab pickup (includes '83-'87 S-10/S-15 extended cab pickups, '03-'06 Chevy SSR, '96-'00 Isuzu Hombre Reg. Cab)
|-
|5||Van (Astro/Safari &amp; full-size vans &amp; '07-'09 HHR Panel)
|-
|6||Extended length 4-door SUV (Suburban, Yukon XL, Escalade ESV, Trailblazer EXT, Envoy XL, Isuzu Ascender 7-psgr.)
|-
|6||3-door Passenger Minivan ('90-'99 U-bodies)
|-
|7||Motor Home Chassis ('81-'09)
|-
|8||Two-Door SUV (Utility) (2-d Tracker, S-10 Blazer, S-15 Jimmy, Blazer, Jimmy, Tahoe, Yukon)
|-
|9||Stake (81-87)
|-
|9||Extended Cab pickup ('88-) (includes '97-'00 Isuzu Hombre Spacecab, '06-'08 Isuzu i-Series Ext. Cab)
|-
|9||Extended length van ('90-) (Astro/Safari &amp; full-size vans)
|}

===American VIN format 2010- Light Duty Truck &amp; Multi-Purpose Passenger Vehicle===
GM's VIN format is as follows:

&lt;table border=1 style=&quot;margin:auto;&quot;&gt;
&lt;tr&gt;
&lt;th&gt;Position&lt;/th&gt;
&lt;th&gt;Sample&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;Description&lt;/th&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;1&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td rowspan=3&gt;[[#GM WMIs|World Manufacturer Identifier]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;G&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;K&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;L&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[#GVWR/Brake System/Body Style 2010- Light Duty Truck &amp; Multi-Purpose Passenger Vehicle|GVWR/Brake System/Body Style 2010-]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;5&lt;/td&gt;
&lt;td&gt;R&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[#Line &amp; Chassis Type 2010- Light Duty Truck &amp; Multi-Purpose Passenger Vehicle|Line &amp; Chassis Type for 2010-]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;6&lt;/td&gt;
&lt;td&gt;L&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[#Series 2010- Light Duty Truck &amp; Multi-Purpose Passenger Vehicle|Series 2010- Light Duty Truck &amp; Multi-Purpose Passenger Vehicle]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;7&lt;/td&gt;
&lt;td&gt;E&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[#Restraint codes for light trucks 2010-|Restraint type]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;8&lt;/td&gt;
&lt;td&gt;D&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[#Engine codes for light trucks|Engine type]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;9&lt;/td&gt;
&lt;td&gt;0&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[Vehicle Identification Numbers (VIN codes)/Check digit |Check digit]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;10&lt;/td&gt;
&lt;td&gt;A&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[Vehicle Identification Numbers (VIN codes)/Model year|Model year]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;11&lt;/td&gt;
&lt;td&gt;J&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[#GM factories supplying North America|Factory ID]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;12&lt;/td&gt;
&lt;td&gt;1&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td rowspan=6&gt;Sequential number
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;13&lt;/td&gt;
&lt;td&gt;2&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;14&lt;/td&gt;
&lt;td&gt;3&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;15&lt;/td&gt;
&lt;td&gt;7&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;16&lt;/td&gt;
&lt;td&gt;6&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;17&lt;/td&gt;
&lt;td&gt;2&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;
&lt;/table&gt;

====GVWR/Brake System/Body Style 2010- Light Duty Truck &amp; Multi-Purpose Passenger Vehicle====
The GVWR/Brake System is specified as character 4 of the American GM VIN for light trucks.

{| border=1 style=&quot;margin:auto;&quot;
!VIN
!GVWR Range in lbs. &amp; Weight Class
!Brake System
!Body Style
|-
| ||Class A: 0-3,000||Hydraulic||
|-
| ||Class B: 3,001-4,000||Hydraulic||
|-
|A||Class C: 4,001-5,000||Hydraulic||26: 4-door SUV or MPV ('10-'11 Chevy HHR Panel, '10-'26 Chevy Equinox, GMC Terrain, '10 Saturn Vue,&lt;br&gt; '12-'15 Chevy Captiva Sport, '19-'24 Cadillac XT4, '24-'26 Buick Encore GX)
|-
|B||Class C: 4,001-5,000||Hydraulic||46: 4-door MPV ('10-'11 Chevy HHR)
|-
|J||Class C: 4,001-5,000||Hydraulic||48: 4-door, 4 window Hatchback ('18-'23 Chevy Bolt EV w/Rear Seat Delete pkg. - incomplete vehicle)
|-
|C||Class C: 4,001-5,000||Hydraulic||03: Regular Cab pickup or Chassis Cab ('10-'12 Chevy Colorado, GMC Canyon)
|-
|D||Class C: 4,001-5,000||Hydraulic||43: Crew Cab pickup or Chassis Cab ('10-'12 Chevy Colorado, GMC Canyon)
|-
|E||Class C: 4,001-5,000||Hydraulic||53: Extended Cab pickup or Chassis Cab ('10-'12 Chevy Colorado, GMC Canyon)
|-
|7||Class C: 4,001-5,000||Hydraulic||75: Four-Door Wagon - High Roof Monocab (Canada only: '12-'14 Chevy Orlando)
|-
|M||Class C: 4,001-5,000||Hydraulic||06: 4-door SUV ('20-'23 Buick Encore GX)
|-
|9||Class C: 4,001-5,000||Hydraulic||56: 4-door SUV Extended ('21-'26 Chevy Trailblazer)
|-
|7||Class C: 4,001-5,000||Hydraulic||58: 4-door Utility Extended ('24-'26 Chevy Trax, Buick Envista)
|-
|C||Class C: 4,001-5,000||Hydraulic||76: 4-door SUV ('13-'22 Buick Encore, Canada only: '13-'14 Chevy Trax, US &amp; Canada: '15-'22 Chevy Trax)
|-
|F||Class D: 5,001-6,000||Hydraulic||26: 4-door SUV ('10-'17 Chevy Equinox, GMC Terrain, '10 Saturn Vue, '10-'16 Cadillac SRX, '11 Saab 9-4X,&lt;br&gt; '12-'13 Chevy Captiva Sport, '16-'26 Buick Envision, '17 Cadillac XT5, '19-'25 Cadillac XT4)
|-
|H||Class D: 5,001-6,000||Hydraulic||03: Regular Cab pickup or Chassis Cab ('10 Chevy Colorado, GMC Canyon)
|-
|G||Class D: 5,001-6,000||Hydraulic||03: Regular Cab pickup or Chassis Cab ('11-'12 Chevy Colorado, GMC Canyon)
|-
|J||Class D: 5,001-6,000||Hydraulic||43: Crew Cab pickup or Chassis Cab ('10 Chevy Colorado, GMC Canyon)
|-
|H||Class D: 5,001-6,000||Hydraulic||43: Crew Cab pickup or Chassis Cab ('11-'12 Chevy Colorado, GMC Canyon)
|-
|G||Class D: 5,001-6,000||Hydraulic||43: Crew Cab pickup or Chassis Cab ('15-'24 Chevy Colorado, '15-'22 GMC Canyon)
|-
|K||Class D: 5,001-6,000||Hydraulic||53: Extended Cab pickup or Chassis Cab ('10 Chevy Colorado, GMC Canyon)
|-
|J||Class D: 5,001-6,000||Hydraulic||53: Extended Cab pickup or Chassis Cab ('11-'12 Chevy Colorado, GMC Canyon)
|-
|H||Class D: 5,001-6,000||Hydraulic||53: Extended Cab pickup or Chassis Cab ('15-'22 Chevy Colorado, GMC Canyon)
|-
|T||Class D: 5,001-6,000||Hydraulic||69: Commercial Chassis ('10 Cadillac DTS chassis for Limo/Hearse)
|-
|7||Class D: 5,001-6,000||Hydraulic||69: Commercial Chassis ('11 Cadillac DTS chassis for Limo/Hearse)
|-
|L||Class E: 6,001-7,000||Hydraulic||26: 4-door SUV ('10 Chevy Traverse, GMC Acadia, Buick Enclave, Saturn Outlook)
|-
|K||Class E: 6,001-7,000||Hydraulic||26: 4-door SUV ('11-'17 Chevy Traverse, Buick Enclave, '11-'23 GMC Acadia, '17 Acadia Limited,&lt;br&gt; '17-'26 Cadillac XT5, '19-'26 Chevy Blazer, '20-'25 Cadillac XT6, '23-'26 Cadillac Lyriq EV,&lt;br&gt; '24-'26 Chevy Blazer EV, '25-'26 Cadillac Optiq EV, '24-'26 Honda Prologue EV, '24 Acura ZDX EV A-Spec)
|-
|7||Class E: 6,001-7,000||Hydraulic||48: 4-door SUV ('24-'25 Chevy Equinox EV)
|-
|E||Class E: 6,001-7,000||Hydraulic||56: 4-door SUV Extended ('18-'26 Chevy Traverse, Buick Enclave, '24 Chevy Traverse Limited,&lt;br&gt; '24-'26 GMC Acadia
|-
|M||Class E: 6,001-7,000||Hydraulic||05: Cargo Van ('10 Chevy Express, GMC Savana)
|-
|L||Class E: 6,001-7,000||Hydraulic||05: Cargo Van ('11-'14 Chevy Express, GMC Savana)
|-
|M||Class E: 6,001-7,000||Hydraulic||06: 4-door SUV ('10 Chevy Tahoe, GMC Yukon, Hummer H3)
|-
|L||Class E: 6,001-7,000||Hydraulic||06: 4-door SUV ('11-'20 Chevy Tahoe Police Pursuit Vehicle 2wd)
|-
|N||Class E: 6,001-7,000||Hydraulic||36: Sport Utility Truck (SUT) ('10 Chevy Avalanche 2wd)
|-
|M||Class E: 6,001-7,000||Hydraulic||36: Sport Utility Truck (SUT) ('11-13 Chevy Avalanche 2wd)
|-
|P||Class E: 6,001-7,000||Hydraulic||03: Regular Cab pickup or Chassis Cab ('10 Chevy Silverado, GMC Sierra)
|-
|N||Class E: 6,001-7,000||Hydraulic||03: Regular Cab pickup or Chassis Cab ('11-'26 Chevy Silverado, GMC Sierra,&lt;br&gt; '22 Chevy Silverado LTD, GMC Sierra Limited)
|-
|R||Class E: 6,001-7,000||Hydraulic||43: Crew Cab pickup or Chassis Cab ('10 Chevy Silverado, GMC Sierra, Hummer H3T)
|-
|P||Class E: 6,001-7,000||Hydraulic||43: Crew Cab pickup or Chassis Cab ('11-'26 Chevy Silverado, GMC Sierra,&lt;br&gt; '22 Chevy Silverado LTD, GMC Sierra Limited, '16-'26 Chevy Colorado, GMC Canyon)
|-
|S||Class E: 6,001-7,000||Hydraulic||53: Extended Cab pickup or Chassis Cab ('10 Chevy Silverado, GMC Sierra)
|-
|R||Class E: 6,001-7,000||Hydraulic||53: Extended Cab pickup or Chassis Cab ('11-'26 Chevy Silverado, GMC Sierra,&lt;br&gt; '19 Chevy Silverado LD, GMC Sierra Limited, '22 Chevy Silverado LTD, GMC Sierra Limited,&lt;br&gt; '16-'22 Chevy Colorado)
|-
|G||Class E: 6,001-7,000||Hydraulic||69: Commercial Chassis ('10 Cadillac DTS chassis for Limo/Hearse)
|-
|8||Class E: 6,001-7,000||Hydraulic||69: Commercial Chassis ('11 Cadillac DTS chassis for Limo/Hearse)
|-
|X||Class E: 6,001-7,000||Hydraulic||69: Commercial Chassis ('13-'19 Cadillac XTS chassis for Limo/Hearse)
|-
|U||Class F: 7,001-8,000||Hydraulic||05: Cargo Van or Incomplete Vehicle ('10 Chevy Express, GMC Savana)
|-
|S||Class F: 7,001-8,000||Hydraulic||05: Cargo Van or Incomplete Vehicle ('11-'14 Chevy Express, GMC Savana)
|-
|U||Class F: 7,001-8,000||Hydraulic||06: Passenger Van ('10 Chevy Express, GMC Savana)
|-
|S||Class F: 7,001-8,000||Hydraulic||06: Passenger Van ('11-'14 Chevy Express, GMC Savana)
|-
|U||Class F: 7,001-8,000||Hydraulic||06: 4-door SUV ('10 Chevy Tahoe, Suburban 1500, GMC Yukon, Yukon XL 1500, Cadillac Escalade, Escalade ESV)
|-
|S||Class F: 7,001-8,000||Hydraulic||06: 4-door SUV ('11-'26 Chevy Tahoe, Suburban 1500, GMC Yukon, Yukon XL 1500, Cadillac Escalade, Escalade ESV)
|-
|V||Class F: 7,001-8,000||Hydraulic||36: Sport Utility Truck (SUT) ('10 Chevy Avalanche 4wd, Cadillac Escalade EXT 4wd)
|-
|T||Class F: 7,001-8,000||Hydraulic||36: Sport Utility Truck (SUT) ('11-'13 Chevy Avalanche 4wd, Cadillac Escalade EXT 4wd)
|-
|X||Class F: 7,001-8,000||Hydraulic||26: 4-door SUV ('24 Acura ZDX EV Type S)
|-
|C||Class F: 7,001-8,000||Hydraulic||56: 4-door SUV Extended ('26- Cadillac Vistiq EV)
|-
|W||Class F: 7,001-8,000||Hydraulic||03: Regular Cab pickup or Chassis Cab ('10 Chevy Silverado, GMC Sierra)
|-
|X||Class F: 7,001-8,000||Hydraulic||43: Crew Cab pickup or Chassis Cab ('10 Chevy Silverado, GMC Sierra)
|-
|U||Class F: 7,001-8,000||Hydraulic||43: Crew Cab pickup or Chassis Cab ('11-'26 Chevy Silverado, GMC Sierra,&lt;br&gt; '22 Chevy Silverado LTD, GMC Sierra Limited)
|-
|Y||Class F: 7,001-8,000||Hydraulic||53: Extended Cab pickup or Chassis Cab ('10 Chevy Silverado, GMC Sierra)
|-
|V||Class F: 7,001-8,000||Hydraulic||53: Extended Cab pickup or Chassis Cab ('11-'26 Chevy Silverado, GMC Sierra,&lt;br&gt; '19 Chevy Silverado LD, GMC Sierra Limited, '22 Chevy Silverado LTD, GMC Sierra Limited)
|-
|U||Class F: 7,001-8,000||Hydraulic||69: Commercial Chassis ('10 Cadillac DTS chassis for Limo/Hearse)
|-
|9||Class F: 7,001-8,000||Hydraulic||69: Commercial Chassis ('11 Cadillac DTS chassis for Limo/Hearse)
|-
|Z||Class G: 8,001-9,000||Hydraulic||05: Cargo Van or Incomplete Vehicle ('10 Chevy Express, GMC Savana)
|-
|W||Class G: 8,001-9,000||Hydraulic||05: Cargo Van or Incomplete Vehicle ('11-'26 Chevy Express, GMC Savana)
|-
|Z||Class G: 8,001-9,000||Hydraulic||06: Passenger Van ('10 Chevy Express, GMC Savana)
|-
|W||Class G: 8,001-9,000||Hydraulic||06: Passenger Van ('11-'26 Chevy Express, GMC Savana)
|-
|Z||Class G: 8,001-9,000||Hydraulic||06: 4-door SUV ('10 Chevy Suburban 2500, GMC Yukon XL 2500)
|-
|W||Class G: 8,001-9,000||Hydraulic||06: 4-door SUV ('11-'13 Chevy Suburban 2500, GMC Yukon XL 2500)
|-
|2||Class H: 9,001-10,000||Hydraulic||05: Cargo Van or Incomplete Vehicle ('10 Chevy Express, GMC Savana)
|-
|Z||Class H: 9,001-10,000||Hydraulic||05: Cargo Van or Incomplete Vehicle ('11-'26 Chevy Express, GMC Savana,&lt;br&gt; '23-'24 BrightDrop Zevo 600, '24 BrightDrop Zevo 400, '25-'26 Chevrolet BrightDrop 400/600)
|-
|2||Class H: 9,001-10,000||Hydraulic||06: Passenger Van ('10 Chevy Express, GMC Savana)
|-
|Z||Class H: 9,001-10,000||Hydraulic||06: Passenger Van ('11-'26 Chevy Express, GMC Savana)
|-
|3||Class H: 9,001-10,000||Hydraulic||03: Van Cutaway ('10 Chevy Express, GMC Savana)
|-
|0||Class H: 9,001-10,000||Hydraulic||03: Van Cutaway ('11-'26 Chevy Express, GMC Savana)
|-
|3||Class H: 9,001-10,000||Hydraulic||03: Regular Cab pickup or Chassis Cab ('10 Chevy Silverado, GMC Sierra)
|-
|0||Class H: 9,001-10,000||Hydraulic||03: Regular Cab pickup or Chassis Cab ('11-'26 Chevy Silverado, GMC Sierra)
|-
|4||Class H: 9,001-10,000||Hydraulic||43: Crew Cab pickup or Chassis Cab ('10 Chevy Silverado, GMC Sierra)
|-
|1||Class H: 9,001-10,000||Hydraulic||43: Crew Cab pickup or Chassis Cab ('11-'26 Chevy Silverado, GMC Sierra,&lt;br&gt; '24-'25 GMC Hummer EV pickup w/20 module battery pack,&lt;br&gt; '24-'26 Chevy Silverado EV, '25-'26 GMC Sierra EV)
|-
|5||Class H: 9,001-10,000||Hydraulic||53: Extended Cab pickup or Chassis Cab ('10 Chevy Silverado, GMC Sierra)
|-
|2||Class H: 9,001-10,000||Hydraulic||53: Extended Cab pickup or Chassis Cab ('11-'13, '15-'26 Chevy Silverado, GMC Sierra)
|-
|B||Class H: 9,001-10,000||Hydraulic||26: 4-door SUV ('24-'25 GMC Hummer EV SUV)
|-
|6||Class 3: 10,001-14,000||Hydraulic||03: Van Cutaway ('10 Chevy Express, GMC Savana)
|-
|3||Class 3: 10,001-14,000||Hydraulic||03: Van Cutaway ('11-'26 Chevy Express, GMC Savana)
|-
|6||Class 3: 10,001-14,000||Hydraulic||03: Regular Cab pickup or Chassis Cab ('10 Chevy Silverado, GMC Sierra)
|-
|3||Class 3: 10,001-14,000||Hydraulic||03: Regular Cab pickup or Chassis Cab ('11-'26 Chevy Silverado, GMC Sierra)
|-
|7||Class 3: 10,001-14,000||Hydraulic||43: Crew Cab pickup or Chassis Cab ('10 Chevy Silverado, GMC Sierra)
|-
|4||Class 3: 10,001-14,000||Hydraulic||43: Crew Cab pickup or Chassis Cab ('11-'26 Chevy Silverado, GMC Sierra,&lt;br&gt; '22-'24 GMC Hummer EV pickup w/24 module battery pack, '25 GMC Hummer EV pickup w/20 or 24 module battery pack, '26 GMC Hummer EV pickup, '24-'25 Chevy Silverado EV, GMC Sierra EV)
|-
|8||Class 3: 10,001-14,000||Hydraulic||53: Extended Cab pickup or Chassis Cab ('10 Chevy Silverado, GMC Sierra)
|-
|5||Class 3: 10,001-14,000||Hydraulic||53: Extended Cab pickup or Chassis Cab ('11-'13, '15-'18, '20-'26 Chevy Silverado, GMC Sierra)
|-
|8||Class 3: 10,001-14,000||Hydraulic||06: 4-door SUV ('16-'19, '24-'26 Chevy Suburban 3500HD)
|-
|8||Class 3: 10,001-14,000||Hydraulic||05: Cargo Van ('22 BrightDrop EV600, '23-'24 BrightDrop Zevo 600, '24 BrightDrop Zevo 400,&lt;br&gt; '25-'26 Chevrolet BrightDrop 400/600)
|-
|T||Class 3: 10,001-14,000||Hydraulic||26: 4-door SUV ('25-'26 GMC Hummer EV SUV, '25-'26 Cadillac Escalade IQ [EV])
|-
|L||Class 3: 10,001-14,000||Hydraulic||56: 4-door SUV Extended ('26- Cadillac Escalade IQL [EV])
|-
|9||Class 4: 14,001-16,000||Hydraulic||03: Van Cutaway ('10 Chevy Express, GMC Savana)
|-
|6||Class 4: 14,001-16,000||Hydraulic||03: Van Cutaway ('11-'26 Chevy Express, GMC Savana)
|-
| ||Class 5: 16,001-19,500||Hydraulic||
|}

====Line &amp; Chassis Type 2010- Light Duty Truck &amp; Multi-Purpose Passenger Vehicle====
The Line &amp; Chassis Type is specified as character 5 of the American GM VIN for light trucks.

{| border=1 style=&quot;margin:auto;&quot;
!VIN
!Description
|-
|A||Chevrolet HHR ('10-'11), HHR Panel ('10-'11)
|-
|A||Chevy Silverado 1500 2wd ('22-'26), Silverado HD 2500/3500 2wd ('25-'26)
|-
|B||Chevy Blazer 2wd &amp; Awd '19-'26
|-
|C||Chevy Silverado 2wd ('10-'18), Silverado LD 1500 2wd '19, Silverado HD 2500/3500 2wd '19, GMC Sierra 2wd ('10)
|-
|C||Chevy Tahoe 2wd ('10-'24), Suburban 2wd ('10-'24), Avalanche 2wd ('10-'13),&lt;br /&gt; GMC Yukon 2wd ('10), Yukon XL 2wd ('10), Cadillac Escalade 2wd ('10), Escalade ESV 2wd ('10)
|-
|D||Chevy Silverado 1500 4wd ('22-'24)
|-
|D||Chevy Blazer EV ('24-'26), Chevy Equinox EV ('24-'26)
|-
|E||Cadillac Escalade IQ [EV] ('25-'26), Escalade IQL [EV] ('26-), GMC Hummer EV pickup ('26-), GMC Hummer EV SUV ('26-), GMC Sierra EV ('26-)
|-
|F||Chevy Bolt EV w/Rear Seat Delete pkg. - incomplete vehicle ('18-'23)
|-
|G||Cadillac Chassis for Limousine &amp; for Armored Vehicle (Based on XTS '13-'19)
|-
|G||Cadillac Chassis for Hearse (Based on XTS '13-'19)
|-
|G||Chevy Express 2wd ('10-'26), GMC Savana 2wd ('10) 
|-
|H||Chevy Express 4wd ('10-'14), GMC Savana 4wd ('10)
|-
|H||GMC Sierra 1500 2wd ('22-'26), Sierra HD 2500/3500 2wd ('25-'26)
|-
|H||Honda Prologue EV ('24-'26), Acura ZDX EV ('24)
|-
|J||Buick Encore 2wd &amp; Awd ('13-'22), Chevy Trax 2wd &amp; Awd (Canada: '13-'22, US: '15-'22)
|-
|J||BrightDrop EV600 ('22), BrightDrop Zevo 600 ('23-'24), BrightDrop Zevo 400 ('24), Chevrolet BrightDrop 400/600 ('25-'26)
|-
|K||Chevy Silverado 4wd ('10-'18), Silverado LD 1500 4wd ('19), Silverado HD 2500/3500 4wd ('19), GMC Sierra 4wd ('10)
|-
|K||Chevy Silverado 1500 4wd ('25-'26), Silverado HD 2500/3500 4wd ('25-'26)
|-
|K||Chevy Tahoe 4wd ('10-'24), Suburban 4wd ('10-'24), Suburban HD 4wd ('24-'26), Avalanche 4wd ('10-'13), GMC Yukon 4wd ('10), Yukon XL 4wd ('10),&lt;br&gt; Cadillac Escalade 4wd ('10), Escalade ESV 4wd ('10), Escalade EXT 4wd ('10)
|-
|K||Cadillac Professional Chassis for Limousine (Based on DTS '10-'11)
|-
|K||Cadillac Commercial Chassis for Hearse (Based on DTS '10-'11)
|-
|L||Chevy Equinox 2wd &amp; Awd '10-'17, Captiva Sport 2wd '12-'15, Captiva Sport Awd '12, GMC Terrain 2wd &amp; Awd '10-'17, Saturn Vue 2wd &amp; Awd '10
|-
|L||GMC Terrain 2wd &amp; Awd '18-'26
|-
|L||Buick Envista '24-'26, Chevy Trax '24-'26
|-
|M||Buick Encore GX 2wd &amp; Awd ('20-'26), Chevy Trailblazer 2wd &amp; Awd ('21-'26)
|-
|N||Cadillac SRX 2wd &amp; Awd '10-'16, Saab 9-4X 2011
|-
|N||GMC Acadia 2wd &amp; Awd '17-'26, Cadillac XT5 2wd &amp; Awd '17-'26
|-
|N||Hummer H3, H3T 2010
|-
|P||Chevy Orlando (Canada only: '12-'14)
|-
|P||Cadillac XT6 2wd &amp; Awd '20-'25
|-
|P||Cadillac Lyriq EV 2wd &amp; Awd '23-'25
|-
|R||GMC Acadia 2wd '10-'16, Acadia Limited 2wd '17, Saturn Outlook 2wd '10, Buick Enclave 2wd '10-'17, Chevy Traverse 2wd '10-'17
|-
|R||Buick Enclave 2wd '18-'24, Chevy Traverse 2wd '18-'23
|-
|R||Buick Enclave 2wd '25-'26, Chevy Traverse 2wd '24-'26
|-
|S||Chevy Traverse Limited 2wd '24
|-
|S||Chevy Colorado 2wd ('10-'12, '15-'26), GMC Canyon 2wd ('10)
|-
|T||Chevy Colorado 4wd ('10-'12, '15-'26), GMC Canyon 4wd ('10)
|-
|T||Chevy Traverse Limited Awd '24
|-
|U||GMC Sierra 1500 4wd ('22-'26), Sierra HD 2500/3500 4wd ('25-'26)
|-
|V||GMC Acadia Awd '10-'16, Acadia Limited Awd '17, Saturn Outlook Awd '10, Buick Enclave Awd '10-'17, Chevy Traverse Awd '10-'17
|-
|V||Buick Enclave Awd '18-'24, Chevy Traverse Awd '18-'23
|-
|V||Buick Enclave Awd '25-'26, Chevy Traverse Awd '24-'26
|-
|W||Chevy Silverado 1500 2wd ('19-'21), Silverado LTD 1500 2wd ('22), Silverado HD 2500/3500 2wd ('20-'24)
|-
|X||Buick Envision 2wd &amp; Awd '16-'20, Chevy Equinox 2wd &amp; Awd '18-'26
|-
|Y||Chevy Silverado 1500 4wd ('19-'21), Silverado LTD 1500 4wd ('22), Silverado HD 2500/3500 4wd ('20-'24)
|-
|Z||Cadillac XT4 2wd &amp; Awd '19-'25, Buick Envision 2wd '21-'23, Buick Envision Awd '21-'26
|-
|1||GMC Sierra 2wd ('11-'18), Sierra Limited 1500 2wd ('19), Sierra HD 2500/3500 2wd ('19), Yukon 2wd ('11-'26), Yukon XL 2wd ('11-'26)
|-
|1||GMC Canyon 2wd ('25-'26)
|-
|2||GMC Sierra 4wd ('11-'18), Sierra Limited 1500 4wd ('19), Sierra HD 2500/3500 4wd ('19), Yukon 4wd ('11-'26), Yukon XL 4wd ('11-'26)
|-
|2||GMC Canyon 4wd ('25-'26)
|-
|3||Cadillac Escalade 2wd ('11-'24), Escalade ESV 2wd ('11-'24)
|-
|3||Cadillac Optiq EV ('25-), Cadillac Vistiq EV ('26-)
|-
|4||Cadillac Escalade 4wd ('11-'24), Escalade ESV 4wd ('11-'24), Escalade EXT 4wd ('11-'13)
|-
|5||GMC Canyon 2wd ('11-'12, '15-'24)
|-
|5||Chevy Tahoe 2wd ('25-'26), Suburban 2wd ('25-'26)
|-
|6||GMC Canyon 4wd ('11-'12, '15-'24)
|-
|6||Chevy Tahoe 4wd ('25-'26), Suburban 4wd ('25-'26)
|-
|7||GMC Savana 2wd ('11-'26)
|-
|8||GMC Savana 4wd ('11-'14)
|-
|8||GMC Sierra 1500 2wd ('19-'21), Sierra Limited 1500 2wd ('22), Sierra HD 2500/3500 2wd ('20-'24)
|-
|8||Cadillac Escalade 2wd ('25-'26), Escalade ESV 2wd ('25-'26)
|-
|9||GMC Sierra 1500 4wd ('19-'21), Sierra Limited 1500 4wd ('22), Sierra HD 2500/3500 4wd ('20-'24)
|-
|9||Cadillac Escalade 4wd ('25-'26), Escalade ESV 4wd ('25-'26)
|-
|0||GMC Hummer EV pickup ('22-'25), GMC Hummer EV SUV ('24-'25), Chevy Silverado EV ('24-'26), GMC Sierra EV ('24-'25)
|}

====Series 2010- Light Duty Truck &amp; Multi-Purpose Passenger Vehicle====
The Series is specified as character 6 of the American GM VIN for light trucks.

{| border=1 style=&quot;margin:auto;&quot;
!VIN
!Description
|-
|A (following L)||Saturn Vue XE 2wd ('10)
|-
|E (following L)||Saturn Vue XR V6 2wd ('10)
|-
|K (following L)||Saturn Vue XR-L V6 2wd ('10)
|-
|T (following R)||Saturn Outlook XE 2wd ('10)
|-
|U (following R)||Saturn Outlook XE Premium 2wd ('10)
|-
|V (following R)||Saturn Outlook XR-L 2wd ('10)
|-
|W (following R)||Saturn Outlook XR-L Premium 2wd ('10)
|-
|T (following V)||Saturn Outlook XE Awd ('10)
|-
|U (following V)||Saturn Outlook XE Premium Awd ('10)
|-
|V (following V)||Saturn Outlook XR-L Awd ('10)
|-
|W (following V)||Saturn Outlook XR-L Premium Awd ('10)
|-
|G (following N)||Hummer H3, H3T Base model ('10)
|-
|H (following N)||Hummer H3, H3T Adventure ('10)
|-
|J (following N)||Hummer H3, H3T Luxury ('10)
|-
|K (following N)||Hummer H3, H3T Alpha w/cloth ('10)
|-
|L (following N)||Hummer H3, H3T Alpha w/Leather ('10)
|-
|P (following N)||Saab 9-4X 3.0i 2wd ('11)
|-
|R (following N)||Saab 9-4X 3.0i Awd ('11)
|-
|S (following N)||Saab 9-4X 3.0i Premium 2wd ('11)
|-
|T (following N)||Saab 9-4X 3.0i Premium Awd ('11)
|-
|U (following N)||Saab 9-4X Aero Awd ('11)
|}

===Platform &amp; Series Codes 1985- Passenger Car===
GM used a lettered system of automobile platform codes for three decades. These letters were used as the 4th position of the VIN. Though today's GM platforms use Greek characters, they are still encoded with Latin characters in the 4th position. Position 5 encodes the specific model and trim level of the vehicle.

{| border=1 style=&quot;margin:auto;&quot;
!List of GM platforms
!Platform&lt;br&gt;Code
!Series&lt;br&gt;Code
!:Category:General Motors vehicles|Model
|-
|rowspan=14|GM A platform
|rowspan=14|A||W||Chevrolet Celebrity 1985-1990
|-
|E||Pontiac 6000 ''SE'' 1986-1988
|-
|F||Pontiac 6000 1985-1988, 6000 ''LE'' 1989-1991
|-
|G||Pontiac 6000 ''LE'' 1985-1988
|-
|H||Pontiac 6000 ''STE'' 1985-1989
|-
|J||Pontiac 6000 ''SE'' 1989-1991
|-
|G||Oldsmobile Cutlass Ciera ''S'' Sedan 1993-1994
|-
|J||Oldsmobile Cutlass Ciera ''LS'' 1985, Cutlass Ciera 1986-1989 &amp; Cutlass Cruiser 1985-1989,&lt;br /&gt; Cutlass Ciera ''S'' Coupe 1986-1987, Cutlass Ciera ''S'' 1990-1991 &amp; Cutlass Cruiser ''S'' 1990-1994, Cutlass Ciera ''SL'' &amp; Cutlass Cruiser ''SL'' 1995, Ciera ''SL'' sedan &amp; wagon 1996
|-
|L||Oldsmobile Cutlass Ciera 1990-1991, Cutlass Ciera ''S'' Sedan 1992
|-
|M||Oldsmobile Cutlass Ciera ''Brougham'' 1985-1988, Cutlass Ciera ''SL'' Coupe 1986-1989, Cutlass Ciera ''SL'' Sedan 1989-1993, Cutlass Cruiser ''Brougham'' 1987-1988, Cutlass Cruiser ''SL'' 1989-1993
|-
|S||Oldsmobile Cutlass Ciera ''International Series'' 1988-1990
|-
|G||Buick Century ''T-Type'' 1985-1986, Century ''Special'' 1991-1996
|-
|H||Buick Century ''Custom'' 1985-1995
|-
|L||Buick Century ''Limited'' 1985-1993, Century Estate Wagon 1986-1989
|-
|rowspan=14|GM B platform
|rowspan=14|B||L||Chevrolet Impala 1985, Caprice 1986-1992, Caprice Classic 1993-1996, Impala SS 1995-96
|-
|N||Chevrolet Caprice Classic 1985-1992, Caprice Classic LS 1993-1994,&lt;br /&gt; Caprice Classic LTZ 1991-1993, Impala SS 1994
|-
|U||Chevrolet Caprice Classic Brougham/Brougham LS 1987-1990
|-
|L||Pontiac Parisienne 1985-1986, Safari Wagon 1987-1989
|-
|T||Pontiac Parisienne Brougham 1985-1986
|-
|N||Oldsmobile Delta 88 Royale 1985
|-
|P||Oldsmobile Custom Cruiser 1985-1992
|-
|V||Oldsmobile Delta 88 Royale Brougham LS 1985
|-
|Y||Oldsmobile Delta 88 Royale Brougham 1985
|-
|N||Buick Le Sabre ''Custom'' 1985, Roadmaster sedan 1992-1996
|-
|P||Buick Le Sabre ''Limited'' 1985
|-
|R||Buick Le Sabre Estate Wagon 1985-1989, Estate Wagon 1990,&lt;br /&gt; Roadmaster Estate Wagon 1991-1996
|-
|T||Buick Roadmaster ''Limited'' sedan 1992-1996
|-
|V||Buick Electra Estate Wagon 1985-1989
|-
|rowspan=13|GM C platform - front-wheel drive
|rowspan=13|C
|V||Oldsmobile Touring Sedan 1988-1990, 98 Touring Sedan 1991-1993  
|-
|W||Oldsmobile 98 Regency Brougham 1985-1990, 98 Regency Elite 1991-1996 
|-
|X||Oldsmobile 98 Regency 1985-1990, 1992-1994
|-
|F||Buick Electra T-Type 1985-1990
|-
|U||Buick Electra Park Avenue Ultra 1989-1990, Park Avenue Ultra 1991-1996
|-
|W||Buick Electra Park Avenue 1985-1990, Park Avenue 1991-1996
|-
|X||Buick Electra 1985-1986, Electra Limited 1987-1990
|-
|B||1985-1992 Cadillac Fleetwood, Fleetwood D'Elegance, 1993 Cadillac Sixty Special
|-
|D||1985-1993 Cadillac DeVille
|-
|G||1991-1992 Cadillac Fleetwood Sixty Special
|-
|H||1985-1987 Cadillac Fleetwood Limousine
|-
|S||1987-1990 Cadillac Fleetwood Sixty Special
|-
|T||1991-1993 Cadillac DeVille Touring Sedan
|-
|rowspan=3|GM G platform (models formerly on C platform)
|rowspan=3|C
|-
|U||Buick Park Avenue Ultra 1997-2005
|-
|W||Buick Park Avenue 1997-2005
|-
|rowspan=2|GM D platform
|rowspan=2|D||W||1985-1986 Cadillac Fleetwood Brougham, 1987-1992 Cadillac Brougham
|-
|W||1993-1996 Cadillac Fleetwood
|-
|rowspan=31|GM Delta I platform
|rowspan=31|A
|-
|A||Chevrolet Cobalt LS w/manual trans. 2010
|-
|B||Chevrolet Cobalt LS w/automatic trans. 2010
|-
|C||Chevrolet Cobalt 1LT w/manual trans. 2010
|-
|D||Chevrolet Cobalt 1LT w/automatic trans. 2010
|-
|E||Chevrolet Cobalt 2LT w/manual trans. 2010
|-
|F||Chevrolet Cobalt 2LT w/automatic trans. 2010
|-
|G||Chevrolet Cobalt SS Turbo 2010
|-
|H||Chevrolet Cobalt (base model w/XFE) 2010
|-
|K||Chevrolet Cobalt (base model) 2005, Cobalt LS 2006-2008, Cobalt LS w/man. trans. 2009
|-
|L||Chevrolet Cobalt LS 2005, Cobalt LT 2006-2008, Cobalt LT w/manual trans. 2009
|-
|M||Chevrolet Cobalt SS 2006-2007, Cobalt Sport 2008
|-
|P||Chevrolet Cobalt SS Supercharged 2005-2007, SS Turbo 2008-2009
|-
|S||Chevrolet Cobalt LS w/automatic trans. 2009
|-
|T||Chevrolet Cobalt LT w/automatic trans. 2009
|-
|Z||Chevrolet Cobalt LT 2005, Cobalt LTZ 2006-2007
|-
|L||Pontiac G5 2007-2008, G5 w/manual trans. 2009
|-
|N||Pontiac G5 GT 2007-2008, G5 GT w/manual trans. 2009
|-
|S||Pontiac G5 w/automatic trans. 2009
|-
|T||Pontiac G5 GT w/automatic trans. 2009
|-
|F||Saturn Ion sedan Level 1 w/manual trans. 2003-2005
|-
|G||Saturn Ion sedan Level 1 w/automatic trans. 2003-2005
|-
|J||Saturn Ion sedan Level 2 w/automatic trans. 2003-2007
|-
|K||Saturn Ion sedan Level 3 w/manual trans. 2003-2007
|-
|L||Saturn Ion sedan Level 3 w/automatic trans. 2003-2007
|-
|M||Saturn Ion coupe Level 2 w/manual trans. 2003-2007
|-
|N||Saturn Ion coupe Level 2 w/automatic trans. 2003-2007
|-
|V||Saturn Ion coupe Level 3 w/manual trans. 2003-2007
|-
|W||Saturn Ion coupe Level 3 w/automatic trans. 2003-2007
|-
|Y||Saturn Ion coupe Red Line 2004-2007
|-
|Z||Saturn Ion sedan Level 2 w/manual trans. 2003-2007
|-
|rowspan=9|GM E platform
|rowspan=9|E
|-
|V||Oldsmobile Toronado Trofeo 1988-1992
|-
|Z||Oldsmobile Toronado Brougham 1985-1986, Toronado 1987-1992
|-
|C||Buick Reatta 1988-1991
|-
|Y||Buick Riviera T-Type 1985-1986
|-
|Z||Buick Riviera 1985-1993
|-
|C||Cadillac Eldorado Collector Series 2002 
|-
|L||Cadillac Eldorado 1985-2002
|-
|T||Cadillac Eldorado Touring Coupe 1994-2002 
|-
|rowspan=26|GM Epsilon I platform
|rowspan=26|Z||A||Chevrolet Malibu Fleet 2010-2012
|-
|B||Chevrolet Malibu LS 2010-2012
|-
|C||Chevrolet Malibu 1LT 2010-2012
|-
|D||Chevrolet Malibu 2LT 2010-2012
|-
|E||Chevrolet Malibu LTZ 2010-2011, Malibu 1LZ 2012
|-
|F||Chevrolet Malibu Hybrid 2008-2010, Malibu 3LT 2012
|-
|G||Chevrolet Malibu LS 2008-2009, Malibu 2LZ 2012
|-
|H||Chevrolet Malibu 1LT 2008-2009
|-
|J||Chevrolet Malibu 2LT 2008-2009
|-
|K||Chevrolet Malibu LTZ 2008-2009
|-
|S||Chevrolet Malibu 2004-2005, Malibu LS 2006-2007, Malibu Classic LS 2008
|-
|T||Chevrolet Malibu LS 2004-2005, Malibu LT 2006-2007, Malibu Classic LT 2008
|-
|U||Chevrolet Malibu LT 2004-2005, Malibu LTZ 2006-2007
|-
|W||Chevrolet Malibu SS 2006-2007
|-
|A||Pontiac G6 Sedan 2010
|-
|F||Pontiac G6 2.4L Sedan (Base model) 2006, G6 Value Leader (Base model w/1SV) 2007-2008
|-
|G||Pontiac G6 3.5L Sedan (Base model) 2005-2006, G6 (Base model) 2007-2009
|-
|H||Pontiac G6 GT 2005-2009
|-
|J||Pontiac G6 (Base model) 2009 1/2 (Mid-Cycle Revision)
|-
|K||Pontiac G6 GT 2009 1/2 (Mid-Cycle Revision)
|-
|L||Pontiac G6 GXP 2009 1/2 (Mid-Cycle Revision)
|-
|M||Pontiac G6 GTP 2006-2007, G6 GXP 2008-2009
|-
|R||Saturn Aura Green Line 2007-2009
|-
|S||Saturn Aura XE 2007-2009
|-
|V||Saturn Aura XR 2007-2008, Aura XR 2.4L 2009
|-
|X||Saturn Aura XR V6 2009
|-
|rowspan=6|GM F platform
|rowspan=6|F||P||Chevrolet Camaro Sport Coupe 1985-2002, Convertible 1987-1992, 1994-2002
|-
|S||Chevrolet Camaro Berlinetta 1985-1986
|-
|S||Pontiac Firebird 1985-2002, Firebird ''Formula'' 1987-1992
|-
|V||Pontiac Firebird ''Formula / Trans Am'' 1993-2002, Firebird ''Trans Am GT'' 1994
|-
|W||Pontiac Firebird ''Trans Am'' 1985-1992, Firebird ''Trans Am GTA'' 1987-1992
|-
|X||Pontiac Firebird ''S/E'' 1985-1986
|-
|rowspan=13|GM G platform - rear-wheel drive
|rowspan=13|G||Z||Chevrolet Monte Carlo 1985-1988
|-
|J||Pontiac Grand Prix 1985-1987
|-
|K||Pontiac Grand Prix LE 1985-1987
|-
|N||Pontiac Bonneville 1985-1986
|-
|P||Pontiac Grand Prix Brougham 1985-1987
|-
|R||Pontiac Bonneville Brougham 1985-1986
|-
|S||Pontiac Bonneville LE 1985-1986
|-
|K||Oldsmobile Cutlass Salon coupe 1985-1987
|-
|M||Oldsmobile Cutlass Supreme ''Brougham'' 1985-1987,&lt;br /&gt; Cutlass Supreme Classic ''Brougham'' 1988
|-
|R||Oldsmobile Cutlass Supreme 1985-1987, Cutlass Supreme Classic 1988
|-
|J||Buick Regal 1985-1987
|-
|K||Buick Regal T-Type 1985-1987
|-
|M||Buick Regal ''Limited'' 1985-1987
|-
|rowspan=4|GM G platform - front-wheel drive
|rowspan=4|G||D||1995-1999 Buick Riviera
|-
|R||1995-1999 Oldsmobile Aurora
|-
|R||2001-2002 Oldsmobile Aurora 3.5
|-
|S||2001-2003 Oldsmobile Aurora 4.0
|-
|rowspan=9|GM H platform
|rowspan=9|H||H||Buick Le Sabre 1987
|-
|P||Buick Le Sabre ''Custom'' 1986-1999
|-
|R||Buick Le Sabre ''Limited'' 1986-1999
|-
|C||Oldsmobile Regency 1997-1998, Eighty Eight 50th Anniversary Edition 1999
|-
|N||Oldsmobile Delta 88 Royale 1986-1988, 88 Royale 1989-1995, Eighty Eight &amp; Eighty Eight LS 1996-99
|-
|Y||Oldsmobile Delta 88 Royale Brougham 1986-1988, 88 Royale Brougham 1989-91, Eighty Eight Royale LS 1992-1995, LSS 1996-1999
|-
|X||Pontiac Bonneville 1987, Bonneville LE 1988-1991, Bonneville ''SE'' 1992-1999
|-
|Y||Pontiac Bonneville SSE 1988-1991, Bonneville ''SSEi'' 1992-1993
|-
|Z||Pontiac Bonneville LE 1987, Bonneville SE 1988-1991, Bonneville ''SSE'' 1992-1999, Bonneville ''SSEi'' 1994-1999
|-
|rowspan=17|GM G platform (models formerly on H platform or their successors)
|rowspan=17|H||A||Buick Lucerne ''CX'' 2010-2011
|-
|B||Buick Lucerne ''CX-2'' 2010
|-
|C||Buick Lucerne ''CXL'' 2010-2011
|-
|D||Buick Lucerne ''CXL V6'' 2006-2009, Lucerne ''CXL Special Edition'' 2010
|-
|E||Buick Lucerne ''CXS'' 2006-2008, Lucerne ''CXL-3'' 2010
|-
|F||Buick Lucerne ''Super'' 2008-2009, Lucerne ''CXL-4'' 2010
|-
|G||Buick Lucerne ''CXL-5'' 2010
|-
|H||Buick Lucerne ''Super 1SP'' 2010
|-
|J||Buick Lucerne ''CXL Premium'' 2010-2011
|-
|K||Buick Lucerne ''Super 1XS'' 2010, Lucerne ''Super'' 2011 
|-
|P||Buick Lucerne ''CX'' 2006-2009
|-
|R||Buick Lucerne ''CXL V8'' 2006-2007, Lucerne ''CXL Special Edition V8'' 2008
|-
|P||Buick Le Sabre ''Custom'' 2000-2005
|-
|R||Buick Le Sabre ''Limited'' 2000-2005
|-
|X||Pontiac Bonneville ''SE'' 2000-2005
|-
|Y||Pontiac Bonneville ''SLE'' 2000-2005
|-
|Z||Pontiac Bonneville ''SSEi'' 2000-2003, Bonneville GXP 2004-2005
|-
|rowspan=23|GM J platform
|rowspan=23|J
|-
|C||Chevrolet Cavalier 1985-1994, RS Convertible 1991-1994
|-
|D||Chevrolet Cavalier CS 1985-1987
|-
|E||Chevrolet Cavalier Type 10 1985, RS 1986-1988,&lt;br /&gt; Type 10 Convertible 1985, RS Convertible 1986-1987
|-
|F||Chevrolet Cavalier Z24 1986-1994, Z24 Convertible 1988-1989, 1992-1994
|-
|C||Chevrolet Cavalier 1995-2005, Cavalier RS 1997-1999
|-
|F||Chevrolet Cavalier LS Sedan 1995-2005, LS Coupe 2003-2005, Z24 Coupe 1995-2001,&lt;br /&gt; LS Convertible 1995-1997, Z24 Convertible 1998-2000
|-
|H||Chevrolet Cavalier Z24 Coupe/Sedan 2002, LS Sport 2002-2005
|-
|S||Chevrolet Cavalier LS Coupe 2002
|-
|B||Pontiac Sunbird 1985-1989, Sunbird LE 1990-1991, Sunbird SE 1992-1993,&lt;br /&gt; Sunbird LE 1994
|-
|C||Pontiac Sunbird LE 1985, Sunbird 1991, Sunbird LE 1992-1993
|-
|D||Pontiac Sunbird SE 1985-1991, Sunbird GT 1992-1993
|-
|L||Pontiac Sunbird SE 1994
|-
|U||Pontiac Sunbird GT 1986-1991
|-
|B||Pontiac Sunfire SE 1995-2002, Convertible 1995-2000, Sunfire 2003-2005
|-
|D||Pontiac Sunfire GT 1995-2002
|-
|C||Oldsmobile Firenza Base model 1985-1987, Firenza S 1985-1987, Firenza 1988
|-
|D||Oldsmobile Firenza LX 1985-1987, Firenza SX 1985, Firenza LC, GT 1986-1987
|-
|E||Buick Skyhawk T-Type 1985-1986
|-
|S||Buick Skyhawk Custom 1985-1987, Skyhawk Sport 1986-1987, Skyhawk 1988-1989
|-
|T||Buick Skyhawk Limited 1985-1987
|-
|G||Cadillac Cimarron 1985-1988
|-
|G, H||Toyota Cavalier (Japan only)
|-
|rowspan=8|GM2900 platform
|rowspan=8|J||C||Saturn L-Series|2004 Saturn L300.1
|-
|D||Saturn L-Series|2004 Saturn L300.2, 2005 Saturn L300
|-
|L||Saturn L-Series|2004 Saturn L300.3
|-
|R||Saturn L-Series|Saturn LS w/manual transmission '00/L100 w/manual transmission '01
|-
|S||Saturn L-Series|Saturn LS w/automatic transmission '00/L100 w/automatic transmission '01-'02
|-
|T||Saturn L-Series|Saturn LS1 w/manual transmission '00/L200 w/manual transmission '01-'03, LW200 w/manual trans. '02
|-
|U||Saturn L-Series|Saturn LS1 w/automatic transmission '00/L200 w/automatic transmission '01-'03,&lt;br&gt; Saturn LW1 w/automatic transmission '00/LW200 w/automatic transmission '01-'03
|-
|W||Saturn L-Series|Saturn LS2 '00, LW2 '00, L300 '01-'03, LW300 '01-'03
|-
|rowspan=5|GM K platform
|rowspan=5|K||D||Cadillac Deville 1994-1999
|-
|E||Cadillac Deville D'Elegance 1997-1999
|-
|F||Cadillac Deville Concours 1994-1999
|-
|S||Cadillac Seville 1985-1993 / Cadillac Seville SLS 1994-1997
|-
|Y||Cadillac Seville Touring Sedan / Cadillac Seville STS 1990-1997
|-
|rowspan=9|GM G platform (models formerly on K platform)
|rowspan=9|K||A||2010-2011 Cadillac DTS
|-
|D||2000-2005 Cadillac Deville, 2006-2009 Cadillac DTS, 2010-2011 DTS Luxury
|-
|E||2000-2005 Cadillac Deville DHS
|-
|F||2000-2005 Cadillac Deville DTS
|-
|H||2010-2011 Cadillac DTS Premium
|-
|P||2010-2011 Cadillac DTS Platinum
|-
|R||2010-2011 Cadillac DTS Livery
|-
|S|| 1998-2004 Cadillac Seville SLS
|-
|Y|| 1998-2003 Cadillac Seville STS
|-
|rowspan=33|GM Kappa platform
|rowspan=33|M||A||Pontiac Solstice w/automatic transmission 2010
|-
|B||Pontiac Solstice 2006-2007, Solstice w/manual transmission 2008-2009
|-
|B||Pontiac Solstice GXP w/automatic transmission 2010
|-
|C||Pontiac Solstice w/automatic transmission 2008
|-
|D||Pontiac Solstice w/manual transmission 2010
|-
|E||Pontiac Solstice GXP w/manual transmission 2010
|-
|F||Pontiac Solstice GXP w/automatic transmission 2008
|-
|G||Pontiac Solstice GXP 2007, Solstice GXP w/manual transmission 2008-2009
|-
|K||Pontiac Solstice Street Edition w/manual transmission 2009
|-
|N||Pontiac Solstice w/automatic transmission 2009
|-
|S||Pontiac Solstice SCCA SSB Championship Edition (2.4L) 2008
|-
|T||Pontiac Solstice SCCA T2 Championship Edition (2.0L Turbo) 2008
|-
|T||Pontiac Solstice GXP w/automatic transmission 2009
|-
|Z||Pontiac Solstice Street Edition w/automatic transmission 2009
|-
|B||Saturn Sky 2007, Sky w/manual transmission 2008-2009 
|-
|B||Saturn Sky Redline w/automatic transmission 2010
|-
|C||Saturn Sky w/automatic transmission 2008
|-
|C||Saturn Sky Ruby Red (Merlot Jewel) Special Edition w/manual transmission 2009
|-
|C||Saturn Sky Preferred w/automatic transmission 2010 
|-
|D||Saturn Sky Hydro Blue Special Edition w/manual transmission 2009
|-
|E||Saturn Sky Redline w/manual transmission 2010
|-
|F||Saturn Sky Redline w/automatic transmission 2008
|-
|F||Saturn Sky Preferred w/manual transmission 2010 
|-
|G||Saturn Sky Redline 2007, Sky Redline w/manual transmission 2008-2009
|-
|H||Saturn Sky Redline Ruby Red (Merlot Jewel) Special Edition w/manual transmission 2009
|-
|L||Saturn Sky Redline Hydro Blue Special Edition w/manual transmission 2009
|-
|N||Saturn Sky w/automatic transmission 2009
|-
|P||Saturn Sky Ruby Red (Merlot Jewel) Special Edition w/automatic transmission 2009
|-
|R||Saturn Sky Hydro Blue Special Edition w/automatic transmission 2009
|-
|T||Saturn Sky Redline w/automatic transmission 2009
|-
|V||Saturn Sky Redline Ruby Red (Merlot Jewel) Special Edition w/automatic transmission 2009
|-
|X||Saturn Sky Redline Hydro Blue Special Edition w/automatic transmission 2009
|-
|G||Opel GT 2007-2010, Daewoo G2X 2007-2009
|-
|rowspan=8|GM L platform
|rowspan=8|L
|-
|D||Chevrolet Corsica ''Base'' 1994-1996
|-
|T||Chevrolet Corsica ''Base'' 1987-1989, Corsica ''LT'' 1990-1993
|-
|V||Chevrolet Beretta ''Base'' 1987-1996
|-
|W||Chevrolet Beretta &quot;GT&quot; 1989-1993 (RPO Z21) &amp; Beretta ''Z26'' 1994-1996 (RPO Z04)
|-
|Z||Chevrolet Corsica ''LTZ'' 1989-1990 (RPO Z54) 
|-
|Z||Chevrolet Beretta &quot;GTZ&quot; 1990-1993 (RPO Z04)
|-
|T||Pontiac Tempest (Canada only)
|-
|rowspan=5|GM M platform
|rowspan=5|M||R||Chevrolet Sprint
|-
|R||Geo Metro LSi, Metro
|-
|R||Pontiac Firefly (Canada only)
|-
|S||Chevrolet Sprint ER
|-
|S||Geo Metro, Metro XFi
|-
|rowspan=32|GM N platform
|rowspan=32|N
|-
|B||Oldsmobile Cutlass 1997, Cutlass ''GL'' 1998-1999
|-
|C||Buick Skylark 4-door ''Custom'' 1987-1991
|-
|D||Buick Skylark 4-door ''Limited'' 1987-1989, Skylark 4-door ''Luxury Edition'' 1990-1991
|-
|D||Chevrolet Malibu 1997-2003, Chevrolet Classic 2004-2005
|-
|E||Chevrolet Malibu ''LS'' 1997-2003
|-
|E||Pontiac Grand Am 1985-1988, Grand Am ''LE'' 1989-1991
|-
|E||Pontiac Grand Am ''SE'' 1992-2005
|-
|F||Oldsmobile Calais 1985-1987, Cutlass Calais 1988, Cutlass Calais ''S'' 1989-1991
|-
|F||Oldsmobile Achieva ''SL'' 1992-1994, Achieva ''SC'' 1994
|-
|F||Oldsmobile Alero ''GLS'' 1999-2004
|-
|F||Pontiac Grand Am ''SE1'' 2000-2004
|-
|G||Oldsmobile Cutlass ''GLS'' 1997-1999
|-
|G||Pontiac Grand Am 1991
|-
|G||Pontiac Grand Am ''SE2'' 2000, 2003-2004
|-
|J||Buick Somerset Regal 1985, Somerset ''Custom'' 1986-1987, Skylark 2-door ''Custom'' 1988-91, Skylark 4-door ''Custom'' 1986
|-
|J||Buick Skylark 1992, Skylark ''Limited'' 1993-1994, Skylark ''Custom'' 1996-1998,&lt;br /&gt; Skylark ''Limited'' &amp; ''Gran Sport'' 1996-1997
|-
|K||Buick Somerset ''T-Type'' 1986
|-
|K||Oldsmobile Cutlass Calais ''International Series'' 1988-1991
|-
|K||Oldsmobile Alero ''GX'' 1999-2004
|-
|L||Oldsmobile Cutlass Calais 1989-1991
|-
|L||Oldsmobile Achieva ''S'' 1992-1995, Achieva ''SL'' 1996-1998, Achieva ''SC'' 1996-1997
|-
|L||Oldsmobile Alero ''GL'' 1999-2004
|-
|M||Buick Somerset Regal ''Limited'' 1985, Somerset ''Limited'' 1986-'87, Skylark 2-door ''Limited'' '88-'89, Skylark 2-door ''Gran Sport'' 1990-1991, Skylark 4-door ''Limited'' 1986
|-
|M||Buick Skylark ''Gran Sport'' 1992-1994
|-
|T||Oldsmobile Calais ''Supreme'' 1985-1987, Cutlass Calais ''SL'' 1988-1991
|-
|V||Buick Skylark 1990-1991
|-
|V||Buick Skylark ''Custom'' 1993-1995, ''Limited'' 1995, ''Gran Sport'' 1995
|-
|V||Pontiac Grand Am ''LE'' 1985-1988
|-
|V||Pontiac Grand Am ''GT1'' 2000-2005
|-
|W||Pontiac Grand Am ''SE'' 1986-1991
|-
|W||Pontiac Grand Am ''GT'' 1992-2005
|-
|rowspan=5|GM P platform - rear-wheel drive
|rowspan=5|P
|-
||E||Pontiac Fiero ''Coupe'' 1985-1988
|-
||F||Pontiac Fiero ''SE'' 1985-1987
|-
||G||Pontiac Fiero ''GT'' 1985-1988
|-
||M||Pontiac Fiero ''Sport coupe'' 1985-1987
|-
|rowspan=1|GM P platform - front-wheel drive
|rowspan=1|P||X||General Motors EV1 1997, 1999
|-
|rowspan=6|GM R platform
|rowspan=6|R
|-
||F||1985-1986 Chevrolet Spectrum
|-
||F||1987-1988 Chevrolet Spectrum 3-door hatchback, 1989 Geo Spectrum 3-door hatchback
|-
||F||1990-1993 Geo Storm
|-
||G||1987-1988 Chevrolet Spectrum 4-door sedan, 1989 Geo Spectrum 4-door sedan
|-
||T||1990-1993 Geo Storm GSi
|-
|rowspan=8|GM S platform
|rowspan=8|S||K||1985-1988 Chevrolet Nova
|-
|K||1989-1997 Geo Prizm, 1998-2002 Chevrolet Prizm
|-
|L||1988 Chevrolet Nova Twin Cam, 1990-1992 Geo Prizm GSi
|-
|L||2003-2008 Pontiac Vibe, 2009-2010 Pontiac Vibe FWD w/manual transmission
|-
|M||2003-2006 Pontiac Vibe ''AWD'', 2009-2010 Pontiac Vibe AWD w/automatic transmission
|-
|N||2003-2006 Pontiac Vibe ''GT'', 2009-2010 Pontiac Vibe GT FWD w/manual transmission
|-
|P||2009-2010 Pontiac Vibe FWD w/automatic transmission
|-
|R||2009-2010 Pontiac Vibe GT FWD w/automatic transmission
|-
|rowspan=32|GM Sigma platform
|rowspan=32|D||A||Cadillac CTS Base model RWD 2010-2013, CTS Coupe Base model RWD 2014
|-
|B||Cadillac CTS Wagon Luxury Collection RWD 2014
|-
|C||Cadillac CTS Base model AWD 2010-2013, CTS Coupe/Wagon Performance Collection RWD 2014
|-
|D||Cadillac CTS Coupe/Wagon Premium Collection RWD 2014
|-
|E||Cadillac CTS Luxury Collection RWD 2010-2013, CTS Coupe Base model AWD 2014
|-
|F||Cadillac CTS Auto. Trans. RWD 2008-2009, CTS Luxury Collection RWD w/Navigation 2010-2013, CTS Wagon Luxury Collection AWD 2014
|-
|G||Cadillac CTS Auto. Trans. AWD 2008-2009, CTS Luxury Collection AWD 2010-2013, CTS Coupe/Wagon Performance Collection AWD 2014
|-
|H||Cadillac CTS Auto. Trans. AWD w/Navigation 2008-2009, CTS Luxury Collection AWD w/Navigation 2010-2013, CTS Coupe/Wagon Premium Collection AWD 2014
|-
|J||Cadillac CTS Auto. Trans. RWD w/Navigation 2008-2009, CTS Performance Collection RWD 2010-2013
|-
|K||Cadillac CTS Performance Collection RWD w/Navigation 2010-2013
|-
|L||Cadillac CTS Performance Collection AWD 2010-2013
|-
|M||Cadillac CTS V6 2003-2004, CTS 2.8L 2005-2007, CTS Man. Trans. RWD 2008-2009, CTS Performance Collection AWD w/Navigation 2010-2013
|-
|N||Cadillac CTS V-Series 2004-2007, 2009
|-
|P||Cadillac CTS 3.6L 2005-2007, CTS Direct Inj. V6 Man. Trans. RWD 2008-2009, CTS Premium Collection RWD w/Navigation 2010-2013
|-
|R||Cadillac CTS Direct Inj. V6 Auto. Trans. RWD 2008
|-
|S||Cadillac CTS Direct Inj. V6 Auto. Trans. AWD 2008-2009, CTS Premium Collection AWD w/Navigation 2010-2013 
|-
|T||Cadillac CTS Direct Inj. V6 Auto. Trans. AWD w/Navigation 2008-2009
|-
|U||Cadillac CTS Direct Inj. V6 Auto. Trans. RWD 2009
|-
|V||Cadillac CTS Direct Inj. V6 Auto. Trans. RWD w/Navigation 2008-2009, CTS sedan V-Series 2010-2014, CTS Wagon V-Series 2011-2014, CTS Coupe V-Series 2011-2015
|-
|0||Cadillac CTS Sport Appearance Pkg. 2010
|-
|1||Cadillac CTS Eco Luxury Pkg. 2010
|-
|2||Cadillac CTS Sport Appearance Pkg. 2011
|-
|A||Cadillac STS V6 AWD 2008-2009
|-
|B||Cadillac STS V8 AWD 2008-2009
|-
|C||Cadillac STS V8 2005-2007, STS V8 RWD 2008-2009
|-
|D||Cadillac STS V6 AWD w/Navigation 2008-2009
|-
|K||Cadillac STS V6 RWD w/Navigation 2008-2009
|-
|L||Cadillac STS V8 AWD w/Navigation 2008-2009
|-
|U||Cadillac STS (all models) 2010, STS (Base model) 2011 
|-
|W||Cadillac STS V6 2005-2007, STS V6 RWD 2008-2009, STS Luxury 2011
|-
|X||Cadillac STS V-Series 2006-2009, STS Luxury Performance 2011
|-
|Z||Cadillac STS V8 RWD w/Navigation 2008-2009
|-
|rowspan=4|GM T platform - rear-wheel drive
|rowspan=4|T||B|| 1985-1987 Chevrolet Chevette CS
|-
|B||1985-1987 Pontiac Acadian (Canada only)
|-
|J||1985 Pontiac Acadian Scooter (Canada only)
|-
|L||1985-1987 Pontiac 1000
|-
|rowspan=4|GM T platform - front-wheel drive
|rowspan=4|T||N|| Pontiac LeMans 1988, LeMans LE 1989-1991, LeMans SE 1992-1993
|-
|R||1988-1989 Pontiac LeMans SE sedan
|-
|S||1988-1990 Pontiac LeMans GSE AeroCoupe
|-
|X||1988-1993 Pontiac LeMans VL AeroCoupe
|-
|rowspan=3|GM T platform - front-wheel drive
|rowspan=3|A
|-
|R||Saturn Astra XE (US: 2008, Canada: 2008-2009)
|-
|T||Saturn Astra XR (US: 2008, Canada: 2008-2009)
|-
|rowspan=4|Daewoo T200 platform
|rowspan=4|T||D||Chevrolet Aveo Special Value 2004-2008, Base model 2004, LS 2005-2011, Aveo 1LT 2009-2011
|-
|G||Chevrolet Aveo LT 2005-2008, Aveo 2LT 2009-2011
|-
|J||Chevrolet Aveo LS 2004 
|-
|D||Pontiac G3 2009 
|-
|rowspan=2|GM V platform - front-wheel drive
|rowspan=2|V||R||1987-1992 Cadillac Allanté with standard removable hardtop
|-
|S||1990-1993 Cadillac Allanté 
|-
|rowspan=2|GM V platform - rear-wheel drive
|rowspan=2|V||R||1997-2001 Cadillac Catera
|-
|X||2004-2006 Pontiac GTO coupe
|-
|rowspan=49|GM W platform
|rowspan=49|W
|-
|A||Chevrolet Impala ''LS'' 2010-2013, Impala Limited ''LS'' 2014-2016
|-
|B||Chevrolet Impala ''LS'' 2006-2009, Impala ''LT'' 2010-2013, Impala Limited ''LT'' 2014-2016
|-
|C||Chevrolet Impala ''LT'' 3.9L 2006-2009, Impala ''LTZ'' 2010-2013, Impala Limited ''LTZ'' 2014-2016
|-
|D||Chevrolet Impala ''SS'' 2006-2009, Impala ''Police'' 2010-2013, Impala Limited ''Police'' 2014-2016
|-
|E||Chevrolet Impala ''Taxi'' 2010-2012
|-
|F||Chevrolet Impala 2000-2005, Impala ''LS'' Fleet (1FL) 2011-2013
|-
|G||Chevrolet Impala ''LT'' Fleet (2FL) 2011-2013
|-
|H||Chevrolet Impala ''LS'' 2000-2005
|-
|J||Chevrolet Monte Carlo ''LS'' 2006-2007
|-
|K||Chevrolet Monte Carlo ''LT'' 3.9L 2006, Monte Carlo ''LT'' 3.5L 2007
|-
|L||Chevrolet Lumina 1990-2001, Lumina ''LS'' 1997-1999
|-
|L||Chevrolet Monte Carlo ''SS'' 2006-2007
|-
|M||Chevrolet Monte Carlo ''LT'' 3.5L 2006
|-
|N||Chevrolet Lumina ''Euro'' 1990-1994, Lumina ''LS'' 1995-1996, Lumina ''LTZ'' 1997-1999
|-
|N||Chevrolet Monte Carlo ''LTZ'' 2006
|-
|P||Chevrolet Lumina ''Z34'' 1991-1994, Impala ''SS'' 2004-2005
|-
|S||Chevrolet Impala ''Police'' 2006-2009
|-
|T||Chevrolet Impala ''LT'' 3.5L 2006-2009
|-
|U||Chevrolet Impala ''LTZ'' 2006-2009
|-
|V||Chevrolet Impala ''50th Anniversary Edition'' 2008
|-
|W||Chevrolet Monte Carlo ''LS'' 1995-2005
|-
|X||Chevrolet Monte Carlo ''Z34'' 1995-1999, Monte Carlo ''SS'' 2000-2004, Monte Carlo ''LT'' 2005
|-
|Z||Chevrolet Monte Carlo ''SS Supercharged'' 2004-2005
|-
|C||Pontiac Grand Prix ''GXP'' 2005-2008
|-
|H||Pontiac Grand Prix ''LE'' 1991-1993
|-
|J||Pontiac Grand Prix 1988-1989, Grand Prix ''LE'' 1990, Grand Prix ''SE'' 1991-2000
|-
|K||Pontiac Grand Prix ''LE'' 1988-1989, Grand Prix ''SE1'' 2000-2003
|-
|P||Pontiac Grand Prix ''SE'' 1988-1990, Grand Prix ''GT'' 1991-1993, 1997-2003,&lt;br /&gt; Grand Prix ''GT1'' 2004, Grand Prix 2005-2008
|-
|R||Pontiac Grand Prix ''GTP'' 1999-2005, Grand Prix ''GT'' 2006-2007
|-
|S||Pontiac Grand Prix ''GT2'' 2004, Grand Prix ''GT'' 2005
|-
|T||Pontiac Grand Prix ''STE'' 1990-1993
|-
|H||Oldsmobile Cutlass Supreme 1988-1991, Cutlass Supreme ''S'' 1992-1994,&lt;br /&gt; Cutlass Supreme ''SL'' 1995-1997, Intrigue 1998, Intrigue ''GX'' 1999-2002
|-
|R||Oldsmobile Cutlass Supreme ''International Series'' 1988-1993
|-
|S||Oldsmobile Cutlass Supreme ''SL'' 1988-1991, Intrigue ''GL'' 1998-2002
|-
|T||Oldsmobile Cutlass Supreme Convertible 1990-1995
|-
|X||Oldsmobile Intrigue ''GLS'' 1998-2002
|-
|B||Buick Regal ''Custom'' 1988-1996, Regal ''GS'' Coupe 1995-1996, Regal ''LS'' 1997-2004
|-
|C||Buick Lacrosse ''CX'' 2005-2009
|-
|D||Buick Regal ''Limited'' 1988-1996, Lacrosse ''CXL'' 2005-2009
|-
|E||Buick Lacrosse ''CXS'' 2005-2008
|-
|F||Buick Regal ''GS'' Coupe 1992-1994, Regal ''GS'' Sedan 1992-2004 
|-
|F||Buick Allure ''CX'' 2005-2009 (Canada only) 
|-
|H||Buick Allure ''CXS'' 2005-2008 (Canada only)
|-
|J||Buick Allure ''CXL'' 2005-2009 (Canada only)
|-
|N||Buick Lacrosse ''Super'' 2008-2009
|-
|P||Buick Allure ''Super'' 2008-2009 (Canada only)
|-
|S||Buick Century ''Custom'' 1997-2005
|-
|Y||Buick Century ''Limited'' 1997-2002
|-
|rowspan=3|GM X platform
|rowspan=3|X||B||1985 Buick Skylark Custom
|-
|C||1985 Buick Skylark Limited
|-
|X||1985 Chevrolet Citation II
|-
|rowspan=39|GM Y platform
|rowspan=39|Y||V||2004-2009 Cadillac XLR
|-
|X||2006-2009 Cadillac XLR V-Series
|-
|Y||1985-2008 Chevrolet Corvette (all models except '90-'95 ZR-1)
|-
|Z||1990-1995 Chevrolet Corvette ZR-1
|-
|G||2009 Chevrolet Corvette GT1 Championship Edition (Base &amp; Z06)
|-
|R||2009 Chevrolet Corvette ZR1 (after early production)
|-
|Y||2009 Chevrolet Corvette (Base model, Early production Z06, Early production ZR1)
|-
|Z||2009 Chevrolet Corvette Z06 (after early production)
|-
|A||2010-2013 Chevrolet Corvette Standard 1LT Man. Trans.
|-
|B||2010-2013 Chevrolet Corvette Preferred 2LT Man. Trans.
|-
|C||2010-2013 Chevrolet Corvette Premium 3LT Man. Trans.
|-
|D||2010-2013 Chevrolet Corvette Custom 4LT Man. Trans.
|-
|E||2010-2013 Chevrolet Corvette Standard 1LT Auto. Trans.
|-
|F||2010-2013 Chevrolet Corvette Preferred 2LT Auto. Trans.
|-
|G||2010-2013 Chevrolet Corvette Premium 3LT Auto. Trans.
|-
|H||2010-2013 Chevrolet Corvette Custom 4LT Auto. Trans.
|-
|J||2010-2013 Chevrolet Corvette Z06 Standard 1LZ Man. Trans.
|-
|K||2010-2013 Chevrolet Corvette Z06 Premium 2LZ Man. Trans.
|-
|L||2010-2013 Chevrolet Corvette Z06 Custom 3LZ Man. Trans.
|-
|M||2010-2013 Chevrolet Corvette ZR1 Standard 1ZR Man. Trans.
|-
|N||2010-2013 Chevrolet Corvette ZR1 Custom 3ZR Man. Trans.
|-
|P||2010-2013 Chevrolet Corvette Grand Sport Standard 1LT Man. Trans.
|-
|R||2010-2013 Chevrolet Corvette Grand Sport Preferred 2LT Man. Trans.
|-
|S||2010-2013 Chevrolet Corvette Grand Sport Premium 3LT Man. Trans.
|-
|T||2010-2013 Chevrolet Corvette Grand Sport Custom 4LT Man. Trans.
|-
|U||2010-2013 Chevrolet Corvette Grand Sport Standard 1LT Auto. Trans.
|-
|V||2010-2013 Chevrolet Corvette Grand Sport Preferred 2LT Auto. Trans.
|-
|W||2010-2013 Chevrolet Corvette Grand Sport Premium 3LT Auto. Trans.
|-
|X||2010-2013 Chevrolet Corvette Grand Sport Custom 4LT Auto. Trans.
|-
|Y||2013 Chevrolet Corvette 427 Convertible Collector Edition Premium 3LT Man. Trans.
|-
|Z||2013 Chevrolet Corvette 427 Convertible Collector Edition Custom 4LT Man. Trans.
|-
|1||2013 Chevrolet Corvette 60th Anniversary Edition Custom 4LT Man. Trans.
|-
|2||2013 Chevrolet Corvette 60th Anniversary Edition Custom 4LT Auto. Trans.
|-
|3||2013 Chevrolet Corvette Grand Sport 60th Anniversary Edition Custom 4LT Man. Trans.
|-
|4||2013 Chevrolet Corvette Grand Sport 60th Anniversary Edition Custom 4LT Auto. Trans.
|-
|5||2013 Chevrolet Corvette Z06 60th Anniversary Edition Custom 3LZ Man. Trans.
|-
|6||2013 Chevrolet Corvette ZR1 60th Anniversary Edition Custom 3ZR Man. Trans.
|-
|7||2013 Chevrolet Corvette 427 Convertible 60th Anniversary Edition Custom 4LT Man. Trans.
|-
|8||2013 Chevrolet Corvette 427 Convertible Collector Edition Preferred 2LT Man. Trans.
|-
|rowspan=13|GM Z platform
|rowspan=13|Z
|-
|E||Saturn SC1 (manual transmission 2-Door) 1993-1999
|-
|F||Saturn SC1 (automatic transmission 2-Door) 1993-1999, SL (manual transmission) 1991-02
|-
|G||Saturn SC (manual transmission) 1991-1992, SC2 (manual transmission 2-Door) 1993-99,&lt;br /&gt; SL1 (manual transmission) 1991-2002, SW1 (manual transmission) 1993-1999
|-
|H||Saturn SC (automatic transmission) 1991-92, SC2 (automatic transmission 2-Door) '93-'99,&lt;br /&gt; SL1 (automatic transmission) 1991-02, SW1 (automatic transmission LHD) '93-'99
|-
|J||Saturn SL2 (manual transmission) 1991-2002, SW2 (manual transmission) 1993-2001
|-
|K||Saturn SL2 (automatic transmission) 1991-2002, SW2 (automatic transmission 1993-1999) 
|-
|M||Saturn SW1 &quot;Postal&quot; [SWP] (automatic transmission RHD) 1999-2001 &lt;br&gt;(Made for US Postal Service rural route mail carriers)
|-
|N||Saturn SC1 (manual transmission 3-Door) 1999-2002, SW2 (automatic transmission 2000-01)
|-
|P||Saturn SC1 (automatic transmission 3-Door) 1999-2002
|-
|R||Saturn SC2 (manual transmission 3-Door) 1999-2002
|-
|S||Saturn SL Spring Special 2002
|-
|Y||Saturn SC2 (automatic transmission 3-Door) 1999-2002
|-
|rowspan=3|GM Zeta platform (VE)
|rowspan=3|E||C||Pontiac G8 GT
|-
|P||Pontiac G8 GXP
|-
|R||Pontiac G8 (Base model)
|-
|rowspan=2|GM Zeta platform (VF)
|rowspan=2|F||1||2014-2017 Chevrolet SS w/automatic transmission
|-
|2||2015-2017 Chevrolet SS w/manual transmission
|-
|GM Zeta platform (WM)
|M||K||2011-2013 Chevrolet Caprice PPV
|-
|GM Zeta platform (WN)
|N||S||2014-2017 Chevrolet Caprice PPV
|-
|rowspan=19|GM Zeta platform (models formerly on F platform)
|rowspan=19|F||A||Chevrolet Camaro ''LS'' automatic transmission 2010-2011, ''2LS'' automatic transmission 2012-2014, ''LS'' manual transmission 2015
|-
|B||Chevrolet Camaro ''LT'' automatic transmission 2010-2014, ''2LS'' automatic transmission 2015
|-
|C||Chevrolet Camaro ''2LT'' automatic transmission 2010-2014, ''LT'' manual transmission 2015
|-
|D||Chevrolet Camaro ''LT'' automatic transmission 2015
|-
|E||Chevrolet Camaro ''LS'' manual transmission 2010-2014, ''2LT'' manual transmission 2015
|-
|F||Chevrolet Camaro ''LT'' manual transmission 2010-2014, ''2LT'' automatic transmission 2015
|-
|G||Chevrolet Camaro ''2LT'' manual transmission 2010-2014, ''SS'' manual transmission 2015
|-
|H||Chevrolet Camaro ''SS'' automatic transmission 2015
|-
|J||Chevrolet Camaro ''SS'' automatic transmission 2010-2014. Note: Must have &quot;J&quot; in 8th position of VIN.
|-
|J||Chevrolet Camaro ''ZL1'' automatic transmission 2012. Note: Must have &quot;P&quot; in 8th position of VIN.
|-
|J||Chevrolet Camaro ''2SS'' manual transmission 2015
|-
|K||Chevrolet Camaro ''2SS'' automatic transmission 2010-2015
|-
|L||Chevrolet Camaro ''ZL1'' automatic transmission 2013-2014, ''ZL1'' manual transmission 2015
|-
|M||Chevrolet Camaro ''ZL1'' automatic transmission 2015
|-
|S||Chevrolet Camaro ''SS'' manual transmission 2010-2014. Note: Must have &quot;W&quot; in 8th position of VIN.
|-
|S||Chevrolet Camaro ''ZL1'' manual transmission 2012. Note: Must have &quot;P&quot; in 8th position of VIN.
|-
|S||Chevrolet Camaro ''Z/28'' manual transmission 2014. Note: Must have &quot;E&quot; in 8th position of VIN.
|-
|T||Chevrolet Camaro ''2SS'' manual transmission 2010-2014
|-
|Z||Chevrolet Camaro ''ZL1'' manual transmission 2013-2014, ''Z/28'' manual transmission 2015
|-
|}

RHD= Right-Hand Drive

====Model Line 2010- Passenger Car (Using Vehicle Platforms introduced 2010 or later)====
The Model Line is specified as character 4 of the American GM VIN for Passenger Cars.

{| border=1 style=&quot;margin:auto;&quot;
!VIN
!Description
|-
|A||Cadillac ATS 2013-2019
|-
|A||Cadillac CTS sedan 2014-2019, CTS V-Series sedan 2016-2019
|-
|B||Chevrolet Cruze 2016-2019
|-
|C||Chevrolet Spark 2013-2022, Spark EV 2014-2016
|-
|D||Cadillac CT4 2020-2026
|-
|D||Cadillac CT5 2020-
|-
|F||Chevrolet Camaro 2016-2024
|-
|F||Chevrolet Bolt EV 2017-2023, Bolt EUV 2022-2023, Bolt 2027
|-
|G||Buick LaCrosse 2010-2016
|-
|G||Buick Regal 2011-2020, Buick Regal TourX 2018-2020
|-
|J||Chevrolet Sonic 2016-2020
|-
|K||Cadillac CT6 2016-2020
|-
|M||Cadillac Celestiq EV 2025-
|-
|P||Buick Verano 2012-2017
|-
|P||Chevrolet Cruze 2011-2015, Cruze Limited 2016
|-
|R||Cadillac ELR 2014, 2016
|-
|R||Chevrolet Volt 2011-2019
|-
|W||Buick Cascada 2016-2019
|-
|Y||Chevrolet Corvette 2014-
|-
|Z||Buick LaCrosse 2017-2019
|-
|Z||Chevrolet Malibu 2016-2025
|-
|1||Cadillac XTS 2013-2019
|-
|1||Chevrolet Impala 2014-2020
|-
|1||Chevrolet Malibu 2013-2015, Malibu Limited 2016
|-
|}

===Body style codes 1987- Passenger Car===
The Body type is specified as character 6 of the American GM VIN for passenger cars.

{| border=1 style=&quot;margin:auto;&quot;
!VIN
!Description
|-
|1||Two-Door Coupe/Sedan
|-
|2||Two-Door Hatchback
|-
|3||Two-Door Convertible
|-
|4||Two-Door Wagon ('91-'92 Geo Storm Hatchback)
|-
|5||Four-Door Sedan
|-
|6||Four-Door Hatchback
|-
|7||Four-Door Hatchback ('89-'90 Geo Prizm hatchback)
|-
|8||Four-Door Station Wagon
|-
|9||Four-Door Station Wagon - High Roof Monocab
|}

===American restraint types 1987-===
The restraint type is specified as character 7 of the American GM VIN for passenger cars.

{{center/top}}
====Restraint codes for passenger cars 1987-2009==== 
{{center/end}}

{| border=1 style=&quot;margin:auto;&quot;
!VIN Code
!Description
|-
|1||Active (Manual) belts 1987-1996
|-
|2||Active (Manual) belts plus driver and passenger front airbags 1992-2005&lt;br /&gt;(For '94-'96 Pontiac Grand Prix coupe: Passive (Automatic) belts plus driver and passenger front airbags)
|-
|3||Active (Manual) belts plus driver side front airbag 1988-1996 &lt;br /&gt;(For '94 Geo Prizm: Active (Manual) belts plus driver and passenger front airbags)
|-
|4||Passive (Automatic) belts 1987-1996
|-
|4||Active (Manual) belts plus driver and passenger front &amp; side airbags 1997-2005
|-
|4||Active (Manual) belts plus driver and passenger front &amp; side curtain airbags 2006-2009
|-
|5||Passive (Automatic) belts plus driver side front airbag 1992-1996
|-
|5||Active (Manual) belts plus driver and passenger front airbags &amp; driver-side side impact airbag 2000-2005
|-
|5||Active (Manual) belts plus driver and passenger front airbags &amp; occupant sensor 2006-2009
|-
|6||Passive (Automatic) belts plus driver and passenger front airbags 1994-1996
|-
|6||Active (Manual) belts plus driver and passenger front &amp; side airbags &amp; occupant sensor 2000-2009
|-
|7||Active (Manual) belt driver &amp; Passive (Automatic) belt passenger plus driver and passenger front airbags 1996
|-
|7||Active (Manual) belts plus driver and passenger front &amp; side airbags &amp; rear side airbags 2000-2005
|-
|7||Active (Manual) belts plus driver and passenger front &amp; side &amp; side curtain airbags &amp; occupant sensor 2006-2009
|-
|8||Active (Manual) belts plus driver and passenger front &amp; side curtain airbags &amp; occupant sensor 2006-2009
|-
|9||
|}

{{center/top}}
====Restraint codes for passenger cars 2010-==== 
{{center/end}}

{| border=1 style=&quot;margin:auto;&quot;
!VIN Code
!Description
|-
|D||Active (Manual) belts plus driver and passenger front &amp; side airbags 2010-
|-
|E||Active (Manual) belts plus driver and passenger front &amp; side &amp; side curtain airbags 2010-2017, 2027
|-
|F||Active (Manual) belts plus driver and passenger front &amp; side curtain airbags 2010
|-
|G||Active (Manual) belts plus driver and passenger front &amp; side &amp; rear side &amp; side curtain airbags 2010-2017
|-
|N||Active (Manual) belts plus driver and passenger front &amp; side &amp; front knee airbags 2016-2019
|-
|R||Active (Manual) belts plus driver and passenger front &amp; side &amp; side curtain &amp; front knee airbags 2012-
|-
|S||Active (Manual) belts plus driver and passenger front &amp; side &amp; rear side &amp; side curtain &amp; front knee airbags 2011-
|-
|T||Active (Manual) belts plus driver and passenger front &amp; side &amp; front row side curtain airbags 2011
|-
|U||Active (Manual) belts plus driver and passenger front &amp; side &amp; front row side curtain &amp; front knee airbags 2012-2017
|}

{{center/top}}
====Restraint codes for light trucks 2010-==== 
{{center/end}}

{| border=1 style=&quot;margin:auto;&quot;
!VIN Code
!Description
|-
|A||Active (Manual) belts plus driver-side front airbag 2010
|-
|B||Active (Manual) belts plus driver-side front airbag 2011-
|-
|B||Active (Manual) belts plus driver and passenger front airbags 2010
|-
|C||Active (Manual) belts plus driver and passenger front airbags 2011-
|-
|C||Active (Manual) belts plus driver and passenger front &amp; side airbags 2010
|-
|D||Active (Manual) belts plus driver and passenger front &amp; side airbags 2011-
|-
|D||Active (Manual) belts plus driver and passenger front airbags &amp; side curtain airbags for up to 3 rows of seating 2010
|-
|E||Active (Manual) belts plus driver and passenger front &amp; side &amp; side curtain airbags 2010-
|-
|F||Active (Manual) belts plus driver and passenger front airbags &amp; side curtain airbags for up to 3 rows of seating 2011-2015
|-
|F||Active (Manual) belts plus driver and passenger front &amp; side airbags &amp; side curtain airbags for up to 3 rows of seating 2016-
|-
|H||Active (Manual) belts plus driver-side front airbag &amp; driver-side side-impact airbag &amp; driver-side side curtain airbag 2023-2024
|-
|K||Active (Manual) belts plus driver and passenger front &amp; side &amp; side curtain &amp; front center airbags 2013-
|-
|L||Active (Manual) belts plus driver and passenger front &amp; side &amp; side curtain &amp; front center &amp; driver-side knee airbags 2017-2023
|-
|M||Active (Manual) belts plus driver and passenger front &amp; side &amp; side curtain &amp; front center &amp; front knee airbags 2025-
|-
|R||Active (Manual) belts plus driver and passenger front &amp; side &amp; side curtain &amp; front knee airbags 2017-
|-
|S||Active (Manual) belts plus driver and passenger front &amp; side &amp; rear side &amp; side curtain &amp; front knee airbags 2013-
|-
|T||Active (Manual) belts plus driver-side front airbag &amp; driver- and passenger-side side-impact airbags &amp; side curtain airbags 2023-
|-
|U||Active (Manual) belts plus driver and passenger front &amp; side &amp; front row side curtain &amp; front knee airbags 2013-2019
|}

===American engine codes 1981-===
GM encodes the engine type in character 8 of the VIN. The following table outlines the various engines encoded there:

====Engine codes for passenger cars==== 

Warning: Issues with decoding are related to year/model combinations. Each year has a different breakdown for each code along with plants and some model/trim breakdowns over years.

Entry: 1985-1988 Pontiac Fiero has a 9 engine code for the 2.8L L44 V6. Entry: 1986-1990 Cadillac Brougham, Oldsmobile 307 Cu. In. V8 vin code Y.


{| border=1 style=&quot;margin:auto;&quot;
!VIN
!RPO
!Size
!Type
!Fuel
!Valvetrain
!Engine Family/Notes/Applications
|-
|A||LD5||3.8&amp;nbsp;L||V6||2 Barrel Carburetor |2BBL||OHV||Buick V6. (231 cu. in.) '81 Chevy Camaro (CA), Pontiac Catalina, Firebird, LeMans, Buick Century,&lt;br /&gt; '81-'83 Chevy Malibu (CA), '81-'84 Monte Carlo, Caprice, Impala (CA), '81-'87 Pontiac Grand Prix, Oldsmobile Cutlass/Cutlass Supreme, Buick Regal, '81-'85 Oldsmobile Delta 88, Buick LeSabre,&lt;br /&gt; '81-'86 Pontiac Bonneville, '84 Parisienne
|-
|A||LG0||2.3&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 16 valve||Oldsmobile Quad 4 H.O. '89-'94 Pontiac Grand Am, '89-'91 Oldsmobile Cutlass Calais, '92-'94 Achieva, '90 Cutlass Supreme, '90-'94 Chevy Beretta
|-
|A||LH2||4.6&amp;nbsp;L||V8||Fuel injection#Sequential Multi-port injection|SFI||DOHC,&lt;br /&gt; 32 valve||Cadillac Northstar V8 (For RWD) (Premium V). '04-'09 Cadillac XLR, '05-'10 Cadillac STS
|-
|A||LCV||2.5&amp;nbsp;L||Straight-4|I4||Direct Injection|DI||DOHC,&lt;br /&gt; 16 valve||GM Ecotec engine, Gen III. VVT. '13 Chevy Malibu, '16 Malibu Limited, '16-'19 Impala,&lt;br /&gt; '13-'16 Cadillac ATS
|-
|A||LV7||1.4&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 16 valve||GM Small Gasoline Engine. VVT. Made in Changwon, S. Korea. '16-'22 Chevy Spark.
|-
|B||LG2||3.8&amp;nbsp;L||V6||Fuel injection#Sequential Multi-port injection|SFI||OHV||Buick V6. '86 Oldsmobile 98, Toronado, Buick Electra, Riviera.
|-
|B||L26||4.9&amp;nbsp;L||V8||Fuel injection#Multi-port fuel injection|MFI||OHV||Cadillac High Technology V8.&lt;br /&gt; '91-'93 Cadillac Eldorado, Seville, '91-'95 DeVille, '91-'92 Fleetwood, '91-'93 Sixty Special
|-
|B||LE5||2.4&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 16 valve||GM Ecotec Gen II. VVT. '06-'08 Chevy Cobalt, '06-'07 Saturn Ion, '06-'10 Pontiac G6, Solstice,&lt;br /&gt; '07-'08 Pontiac G5, '07-'10 Saturn Sky, '08-'09 Saturn Aura, '08-'10 Chevy Malibu
|-
|B||LUV||1.4L||I4 Turbo||Fuel injection#Sequential Multi-port fuel injection|SFI||DOHC,&lt;br /&gt; 16 valve||GM Family 0 Engine, Gen III. VVT. '12-'20 Chevy Sonic, '13-'15 Chevy Cruze, '16 Cruze Limited
|-
|C||L17||1.6&amp;nbsp;L||Straight-4|I4||2 Barrel Carburetor |2BBL||SOHC,&lt;br /&gt; 8 valve||Isuzu G161Z engine made by GM in US. '82-'87 Chevy Chevette, Pontiac T1000/1000
|-
|C||LN3||3.8&amp;nbsp;L||V6||Fuel injection#Multi-port fuel injection|MFI||OHV||Buick V6 (3800). '88-'90 Oldsmobile 98, Toronado, Buick Electra, Riviera, Reatta, &lt;br /&gt; '88-'91 Buick LeSabre, Oldsmobile Delta 88/Eighty Eight, Pontiac Bonneville
|-
|C||L47||4.0&amp;nbsp;L||V8||Fuel injection#Sequential Multi-port injection|SFI||DOHC,&lt;br /&gt; 32 valve||Oldsmobile Aurora V8 (Premium V). Oldsmobile Aurora '95-'99, Aurora 4.0 '01-'03
|-
|C||LS4||5.3 L||V8||Fuel injection#Sequential Multi-port injection|SFI||OHV||Gen IV Chevrolet Small-Block V8. Aluminum Block &amp; Heads. Active Fuel Management.&lt;br /&gt; Transversely mounted for FWD. '05-'08 Pontiac Grand Prix GXP, '06-'07 Chevy Monte Carlo SS,&lt;br /&gt; '06-'09 Chevy Impala SS, '08-'09 Buick LaCrosse Super.
|-
|C||LAF||2.4&amp;nbsp;L||Straight-4|I4||Direct Injection|DI||DOHC,&lt;br /&gt; 16 valve||GM Ecotec engine, Gen II. VVT. Buick LaCrosse '10-'11, Regal '11. 
|-
|C||LUJ||1.4L||I4 Turbo||Fuel injection#Sequential Multi-port fuel injection|SFI||DOHC,&lt;br /&gt; 16 valve||GM Family 0 Engine, Gen III. VVT. Early production engines were made in Aspern, Austria; later made in Flint, MI. '12 Chevy Cruze
|-
|D||LJ5||1.8&amp;nbsp;L||Straight-4|I4||Indirect injection Diesel||SOHC,&lt;br /&gt; 8 valve||Isuzu 4FB1 diesel engine imported from Japan. '81-'86 Chevy Chevette
|-
|D||LD2||2.3&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 16 valve||Oldsmobile Quad 4. '88-'95 Pontiac Grand Am, '88-'91 Oldsmobile Cutlass Calais, '92-'95 Achieva,&lt;br /&gt; '88-'91 &amp;'95 Buick Skylark, '90-'91 Pontiac Grand Prix, Oldsmobile Cutlass Supreme,&lt;br /&gt; '95 Chevy Cavalier, Pontiac Sunfire
|-
|D||LC3||4.4&amp;nbsp;L||V8 Supercharged||Fuel injection#Sequential Multi-port point injection|SFI||DOHC,&lt;br /&gt; 32 valve||Cadillac Northstar V8 (Premium V). '06-'09 Cadillac XLR V-Series, Cadillac STS V-Series
|-
|E||LK9||3.0&amp;nbsp;L||V6||2 Barrel Carburetor |2BBL||OHV||Buick V6. '82-'85 Oldsmobile Cutlass Ciera, Buick Century, '85 Oldsmobile 98, Buick Electra
|-
|E||LA1||3.4&amp;nbsp;L||V6||Fuel injection#Sequential Multi-port point injection|SFI||OHV||Chevrolet 60° V6. '99-'05 Grand Am, '99-'04 Alero, '00-'05 Impala, Monte Carlo
|-
|E||L03||5.0&amp;nbsp;L||V8||Fuel injection#Throttle Body injection|TBI||OHV||Gen I Chevy Small-Block V8 (305 cu. in.). '88-'92 Camaro/Firebird, '89-'93 Chevy Caprice,&lt;br /&gt; '91 Buick Roadmaster Estate wagon, '91-'92 Oldsmobile Custom Cruiser, Cadillac Brougham.
|-
|E||LXV||1.6&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 16 valve||Family 1 Gen 3 engine. W/VVT. '09-'11 Chevy Aveo, '09 Pontiac G3
|-
|E||LS7||7.0&amp;nbsp;L||V8||Fuel injection#Sequential Multi-port point injection|SFI||OHV||Gen IV Chevy Small-Block V8. Aluminum Block &amp; Heads.&lt;br /&gt; '06-'13 Corvette Z06, '13 Corvette 427, '14-'15 Camaro Z/28
|-
|E||LH7||1.6&amp;nbsp;L||I4 Turbo||Direct injection &lt;br /&gt; Common-rail Diesel||DOHC,&lt;br /&gt; 16 valve||GM Medium Diesel engine (&quot;Whisper Diesel&quot;). Made by Opel in Szentgotthárd, Hungary.&lt;br /&gt; Aluminum Block &amp; Heads. '17-'19 Chevy Cruze Diesel.
|-
|F||LV8||4.3&amp;nbsp;L||V8||2 Barrel Carburetor |2BBL||OHV||Oldsmobile &quot;Rocket&quot; V8 (260 cu. in.) '81 Oldsmobile Cutlass, Delta 88.
|-
|F||L61||2.2&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 16 valve||GM Ecotec Gen I. '00-'04 Saturn L-Series, '02-'05 Chevy Cavalier, Pontiac Sunfire, Grand Am,&lt;br /&gt; '02-'04 Oldsmobile Alero, '03-'06 Saturn Ion, '04-'06 Chevy Malibu, '05-'06 Chevy Cobalt
|-
|F||L61||2.2&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 16 valve||GM Ecotec Gen II. '07-'08 Chevy Cobalt, Malibu, Pontiac G5, '07 Saturn Ion.
|-
|F||LB9||5.0&amp;nbsp;L||V8||Tuned-port fuel injection|TPI||OHV||Gen I Chevy Small-Block V8. (305 cu. in.). '85-'92 Chevy Camaro, Pontiac Firebird.
|-
|G||L46||1.8&amp;nbsp;L||I4||2 Barrel Carburetor |2BBL||OHV||Chevrolet &quot;122&quot; engine. '82 J-cars.
|-
|G||L69||5.0&amp;nbsp;L||V8||4 Barrel Quadrajet Carburetor |4BBL||OHV||Gen I Chevy Small-Block V8 (High Output 5.0L). (305 cu. in.)&lt;br /&gt; '84-'86 Camaro/Firebird, '84-'88 Chevy Monte Carlo SS
|-
|G||LM3||2.2&amp;nbsp;L||I4||Fuel injection#Throttle Body injection|TBI||OHV||Chevrolet &quot;122&quot; engine. '90-'91 Chevy Cavalier &amp; Corsica/Beretta.
|-
|G||LS1||5.7&amp;nbsp;L||V8||Fuel injection#Multi-port fuel injection|MFI||OHV||Gen III Chevy Small-Block V8. (346 cu. in.) Aluminum Block &amp; Heads.&lt;br /&gt; '97-'04 Corvette, '98-'02 Camaro/Firebird, '04 Pontiac GTO
|-
|G||LF1||3.0L||V6||Direct Injection|DI||DOHC,&lt;br /&gt; 24 valve||GM High Feature V6. VVT. 2010 Buick LaCrosse, Cadillac CTS
|-
|G||LWE||1.8&amp;nbsp;L||Straight-4|I4||Fuel injection#Sequential Multi-port fuel injection|SFI||DOHC,&lt;br /&gt; 16 valve||GM Family 1 engine, Gen III. VVT. PZEV emissions.&lt;br /&gt; '13-'15 Chevy Cruze, '16 Cruze Limited, '13-'18 Sonic.
|-
|H||LG4||5.0&amp;nbsp;L||V8||4 Barrel Quadrajet Carburetor |4BBL||OHV||Gen I Chevy Small-Block V8. (305 cu. in.) '81-'87 F-bodies, '81-'83 Chevy Malibu, '81-'85 Impala,&lt;br /&gt; '81-'88 Caprice, Monte Carlo, '83-'86 Pontiac Bonneville, Parisienne, '83-'87 Grand Prix
|-
|H||LE4||2.0&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port fuel injection|MFI||SOHC,&lt;br /&gt; 8 valve||GM Family II engine. Made in Brazil. '92-'94 Pontiac Sunbird. 
|-
|H||LX5||3.5&amp;nbsp;L||V6||Fuel injection#Sequential Multi-port injection|SFI||DOHC,&lt;br /&gt; 24 valve||Oldsmobile &quot;Shortstar&quot; V6 (Premium V). Oldsmobile Intrigue '99-'02, Aurora 3.5 '01-'02.
|-
|H||LAP||2.2&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 16 valve||GM Ecotec Gen II. VVT. '09 Chevy Cobalt, Pontiac G5.
|-
|H||LUW||1.8&amp;nbsp;L||Straight-4|I4||Fuel injection#Sequential Multi-port fuel injection|SFI||DOHC,&lt;br /&gt; 16 valve||GM Family 1 engine, Gen III. VVT. '11-'15 Chevy Cruze, '16 Cruze Limited, '12-'18 Sonic.
|-
|J||L39||4.4&amp;nbsp;L||V8||2 Barrel Carburetor |2BBL||OHV||Gen I Chevy Small-Block V8 (267 cu. in.) '81-'82 Chevy Caprice, Impala, Malibu, Monte Carlo,&lt;br /&gt; '81 Chevy Camaro
|-
|J||LA5||1.8&amp;nbsp;L||Straight-4|I4 Turbo||Fuel injection#Multi-port fuel injection|MFI||SOHC,&lt;br /&gt; 8 valve||GM Family II engine. Made in Brazil. '84-'86 Pontiac Sunbird, Buick Skyhawk. 
|-
|J||LT5||5.7&amp;nbsp;L||V8||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 32 valve||Based on Chevy Small-Block V8. Designed with Lotus Engineering.&lt;br /&gt; Made by Mercury Marine. Aluminum Block &amp; Heads. '90-'95 Corvette ZR-1
|-
|J||LG8||3.1&amp;nbsp;L||V6||Fuel injection#Sequential Multi-port injection|SFI||OHV||Chevrolet 60° V6. Gen III. 3100. '99-'03 Chevy Malibu, '99 Oldsmobile Cutlass, '00-'01 Chevy Lumina,&lt;br /&gt; '00-'03 Pontiac Grand Prix SE, '00-'05 Buick Century
|-
|J||L99||6.2&amp;nbsp;L||V8||Fuel injection#Sequential Multi-port injection|SFI||OHV||Gen IV Chevy Small-Block V8. VVT. With Active Fuel Management. Aluminum Block &amp; Heads.&lt;br /&gt; '10-'15 Camaro SS (auto. trans.)
|-
|J||LTA||4.2&amp;nbsp;L||V8 Twin Turbo||Direct injection|DI||DOHC,&lt;br /&gt; 32 valve||Cadillac Blackwing V8. VVT. '19-'20 Cadillac CT6 Platinum &amp; V-series
|-
|K||LC3||3.8&amp;nbsp;L||V6||2 Barrel Carburetor |2BBL||OHV||Chevrolet 90° V6 (Chevy Small-Block V8 Derived). 229 cu. in. &lt;br /&gt; '81-'82 Malibu, Monte Carlo, Impala, Caprice, '81 Camaro.
|-
|K||LC5||1.5&amp;nbsp;L||I4||2 Barrel Carburetor |2BBL||SOHC,&lt;br /&gt; 8 valve||Isuzu 4XC1 engine. '85 Chevrolet Spectrum.
|-
|K||LT2||2.0&amp;nbsp;L||Straight-4|I4||Fuel injection#Throttle Body injection|TBI||SOHC,&lt;br /&gt; 8 valve||GM Family II engine. Made in Brazil.&lt;br /&gt; '87-'91 Pontiac Sunbird, '87-'88 Oldsmobile Firenza, Buick Skyhawk. 
|-
|K||LT2||2.0&amp;nbsp;L||Straight-4|I4||Fuel injection#Throttle Body injection|TBI||SOHC,&lt;br /&gt; 8 valve||GM Family II engine. Made in Australia by Holden.&lt;br /&gt; '89-'90 Pontiac LeMans GSE Aerocoupe, '89 LeMans SE sedan
|-
|K||L36||3.8&amp;nbsp;L||V6||Fuel injection#Sequential Multi-port injection|SFI||OHV||Buick V6 (3800 Series II). '95-'05: Various W-, H-, C-, &amp; G-body models. '95-'02 Camaro/Firebird.
|-
|K||LZE||3.5L||V6||Fuel injection#Sequential Multi-port injection|SFI||OHV||GM High Value 60° V6. 3510cc. VVT. Flex-Fuel E85 compatible.&lt;br /&gt; '06-'07 Chevy Monte Carlo, '06-'11 Chevy Impala, '09-'10 Chevy Malibu, Pontiac G6
|-
|K||LEA||2.4&amp;nbsp;L||Straight-4|I4||Direct Injection|DI||DOHC,&lt;br /&gt; 16 valve||E85 Flex Fuel. GM Ecotec engine, Gen II. VVT. Buick Regal, Verano '12-'17 (except '13 Regal). 
|-
|K||LSY||2.0&amp;nbsp;L||Straight-4|I4 Turbo||Direct Injection|DI||DOHC,&lt;br /&gt; 16 valve||GM Ecotec engine, Gen III. Active Fuel Management. VVT. VVL.&lt;br /&gt; '19 Cadillac CT6, '20+ Cadillac CT4, CT5
|-
|L||LM1||5.7&amp;nbsp;L||V8||4 Barrel Carburetor |4BBL||OHV||Gen I Chevy Small-Block V8.&lt;br&gt; '81 Camaro Z28 (only w/auto. trans. in US), '81-'82 Impala 9C1 Police, '81 Malibu 9C1 Police
|-
|L||LL1||2.8&amp;nbsp;L||V6||2 Barrel Carburetor |2BBL||OHV||Chevrolet 60° V6 H.O. (longitudinally mounted). '83-'84 Pontiac Firebird.
|-
|L||LN7||3.0&amp;nbsp;L||V6||Fuel injection#Multi-port fuel injection|MFI||OHV||Buick V6. '85-'87 Pontiac Grand Am, '85-'88 Oldsmobile &amp; Buick N-bodies,&lt;br /&gt; '86 Oldsmobile Delta 88, Buick LeSabre
|-
|L||L27||3.8&amp;nbsp;L||V6||Fuel injection#Tuned port injection|TPI||OHV||Buick V6 (3800 Series I). '90-'95 Buick Regal, '91-'94 Oldsmobile 98, Buick Park Avenue, '91 Reatta, '91-'93 Riviera, '91-'92 Oldsmobile Toronado, '92-'95 Buick LeSabre, '92-'94 Pontiac Bonneville, Oldsmobile 88
|-
|L||LNK||1.8&amp;nbsp;L||Straight-4|I4||Fuel injection#Sequential multi-port injection|SFI||DOHC,&lt;br /&gt; 16 valve||Toyota 2ZZ-GE engine. VVTL-i. '03-'06 Pontiac Vibe GT
|-
|L||LKW||2.5&amp;nbsp;L||Straight-4|I4||Direct Injection|DI||DOHC,&lt;br /&gt; 16 valve||GM Ecotec engine, Gen III. VVT. VVL. '14-'15 Chevy Malibu, Impala
|-
|L||L3B||2.7L||I4 Turbo||Direct Injection|DI||DOHC,&lt;br /&gt; 16 valve||GM L3B Tripower engine. VVT, VVL. Active Fuel Management. '20+ Cadillac CT4, CT4-V
|-
|M||LY9||1.0&amp;nbsp;L||Straight-3|I3||2BBL||SOHC,&lt;br /&gt; 6 valve ||Suzuki G10A engine. '85 Chevrolet Sprint
|-
|M||LT3||2.0&amp;nbsp;L||Straight-4|I4 Turbo||Fuel injection#Multi-port fuel injection|MFI||SOHC,&lt;br /&gt; 8 valve||GM Family II engine. Made in Brazil.&lt;br /&gt; '87-'90 Pontiac Sunbird, '87 Buick Skyhawk T-Type, '87-'89 Pontiac Grand Am SE. 
|-
|M||L82||3.1&amp;nbsp;L||V6||Fuel injection#Sequential Multi Port Fuel injection|SFI||OHV||Chevrolet 60° V6 (transversely mounted). Gen III. 3100. '93-'97 Oldsmobile Cutlass Supreme,&lt;br /&gt; '94-'98 Pontiac Grand Am, Oldsmobile Achieva, Buick Skylark, '94-'99 Pontiac Grand Prix,&lt;br /&gt; '94-'96 Chevy Corsica/Beretta, Oldsmobile Cutlass Ciera, Buick Regal, '94-'99 Century,&lt;br /&gt; '95-'99 Chevy Lumina, Monte Carlo, '97-'99 Chevy Malibu, Oldsmobile Cutlass
|-
|M||LY9||2.6&amp;nbsp;L||V6||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 24 valve||Opel 54° V6 engine (Made in the UK). Euro-market Cadillac CTS '03-'04.
|-
|M||LGD||3.9L||V6||Fuel injection#Sequential Multi Port Fuel injection|SFI||OHV||E85 Flex Fuel. GM High Value 60° V6. VVT. '09-'11 Chevy Impala, Buick Lucerne
|-
|M||LE2||1.4&amp;nbsp;L||Straight-4|I4 Turbo||Direct Injection|DI||DOHC,&lt;br /&gt; 16 valve||GM Small Gasoline Engine. VVT. '16-'19 Chevy Cruze.
|-
|N||LF9||5.7&amp;nbsp;L||V8||Indirect injection Diesel||OHV||Oldsmobile Diesel V8. '81-'85 Chevy Caprice, Impala, '82-'83 Malibu, '82-'84 Monte Carlo,&lt;br /&gt; '81-'84 Pontiac Grand Prix, Bonneville, '81 Catalina, '83-'85 Parisienne,&lt;br /&gt; '81-'84 Oldsmobile 98, '81-'85 Cutlass/Cutlass Supreme, Delta 88, Custom Cruiser, Toronado,&lt;br /&gt; '81-'83 Buick Electra,  '81-'85 LeSabre, Electra Estate wagon, Riviera, '82-'83 Regal,&lt;br /&gt; '81-'84 Cadillac DeVille, '81-'85 Fleetwood Brougham, Eldorado, Seville
|-
|N||LG7||3.3&amp;nbsp;L||V6||Fuel injection#Multi-port fuel injection|MFI||OHV||Buick V6 (3300). '89-'93 Buick Century, Skylark, Oldsmobile Cutlass Ciera, '89-'91 Cutlass Calais,&lt;br /&gt; '92-'93 Achieva, Pontiac Grand Am.
|-
|N||LA3||3.2&amp;nbsp;L||V6||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 24 valve||Opel 54° V6 engine (Made in the UK). '03-'04 Cadillac CTS
|-
|N||LZ4||3.5L||V6||Fuel injection#Sequential Multi-port injection|SFI||OHV||GM High Value 60° V6. 3510cc. VVT. '06-'07 Chevy Monte Carlo, '06-'10 Chevy Impala,&lt;br /&gt; '07-'10 Chevy Malibu, Pontiac G6, '07-'08 Saturn Aura
|-
|N||LFR||3.6L||V6||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 24 valve||(Bi-Fuel Gas/CNG). GM High Feature V6. '15-'17 Chevy Impala Bi-Fuel
|-
|P||LQ5||2.0&amp;nbsp;L||I4||Fuel injection#Throttle Body injection|TBI||OHV||Chevrolet &quot;122&quot; engine. '83-'86 J-cars ('83-'84 for Pontiac).
|-
|P||LT1||5.7&amp;nbsp;L||V8||Fuel injection#Sequential Multi-port injection|SFI||OHV||Gen II Chevy Small-Block V8. Aluminum Heads: '92-'96 Corvette, '93-'97 Camaro/Firebird.&lt;br /&gt; Iron Heads: '94-'96 Chevy Caprice, Impala SS, Buick Roadmaster, Cadillac Fleetwood.
|-
|P||LSJ||2.0&amp;nbsp;L||SC Straight-4|I4 Supercharged||Fuel injection#Sequential central point injection|SFI||DOHC,&lt;br /&gt; 16 valve||GM Ecotec Gen I. Made by Opel in Kaiserslautern, Germany.&lt;br /&gt; '04-'07 Saturn Ion Red Line, '05-'07 Chevy Cobalt SS Supercharged.
|-
|P||LSA||6.2&amp;nbsp;L||V8 Supercharged||Fuel injection#Sequential Multi-port injection|SFI||OHV||Gen IV Chevy Small-Block V8. Aluminum Block &amp; Heads.&lt;br /&gt; Cadillac CTS V-Series '09-'15, Camaro ZL1 '12-'15
|-
|P||LF4||3.6L||V6 Twin Turbo||Direct Injection|DI||DOHC,&lt;br /&gt; 24 valve||GM High Feature V6. Cadillac CT4-V Blackwing '22+
|-
|R||LR8||2.5L||I4||Fuel injection#Throttle Body injection|TBI||OHV||Pontiac Iron Duke/Tech IV engine. Transversely mounted. '82-'85 Chevy Citation, Buick Skylark,&lt;br /&gt; '82-'84 Pontiac Phoenix, Oldsmobile Omega, '82-'90 Chevy Celebrity, '82-'91 Pontiac 6000,&lt;br /&gt; '82-'92 Oldsmobile Cutlass Ciera, Buick Century, '84-'88 Pontiac Fiero, '90-'92 Chevy Lumina
|-
|R||L81||3.0&amp;nbsp;L||V6||Fuel injection#Multi-port fuel injection|SFI||DOHC,&lt;br /&gt; 24 valve||Opel 54° V6 engine (Made in the UK). '97-'01 Cadillac Catera, '00-'05 Saturn L-Series
|-
|R||LZ8||3.9L||V6||Fuel injection#Sequential Multi Port Fuel injection|SFI||OHV||GM High Value 60° V6. VVT. Active Fuel Management. '07 Chevy Impala
|-
|R||LS9||6.2&amp;nbsp;L||V8 Supercharged||Fuel injection#Sequential Multi-port injection|SFI||OHV||Gen IV Chevy Small-Block V8. Aluminum Block &amp; Heads. '09 Corvette ZR1.
|-
|R||LUK||2.4L||I4||Direct Injection|DI||DOHC,&lt;br /&gt; 16 valve||Mild Hybrid. GM Ecotec Gen II. VVT. '12-'16 Buick LaCrosse eAssist, Regal eAssist,&lt;br /&gt; '13-'14 Chevy Malibu Eco, '14 Chevy Impala Eco
|-
|S||LS5||4.3&amp;nbsp;L||V8||2 Barrel Carburetor |2BBL||OHV||Pontiac V8. 265 cu. in.&lt;br /&gt; '81 Pontiac Bonneville, Catalina, Firebird, Grand Prix, LeMans, Buick Century, Regal.
|-
|S||LU5||5.0&amp;nbsp;L||V8||Cross-Fire fuel injection|CFI||OHV||Gen I Chevy Small-Block V8. (305 cu. in.) '83 Camaro, Firebird. Dual throttle-body fuel injection.
|-
|S||LB8||2.8&amp;nbsp;L||V6||Fuel injection#Multi Port Fuel injection|MPFi||OHV||Chevrolet 60° V6 (longitudinally mounted).  '85-'89 Chevy Camaro, Pontiac Firebird.
|-
|S||L32||3.4&amp;nbsp;L||V6||Fuel injection#Multi Port Fuel injection|MPFi||OHV||Chevrolet 60° V6 (longitudinally mounted). '93-'95 Chevy Camaro, Pontiac Firebird.
|-
|S||LS6||5.7&amp;nbsp;L||V8||Fuel injection#Sequential Multi Port injection|SFI||OHV||Gen III Chevy Small-Block V8. (346 cu. in.) Aluminum Block &amp; Heads.&lt;br /&gt; '01-'04 Corvette Z06, '04-'05 Cadillac CTS V-Series
|-
|S||LGX||3.6L||V6||Direct Injection|DI||DOHC,&lt;br /&gt; 24 valve||GM High Feature V6, 4th gen. VVT. Active Fuel Management. '16-'19 Cadillac ATS, CTS, '16-'20 CT6, '16-'24 Chevrolet Camaro, '17-'19 Buick LaCrosse, '18–'20 Buick Regal GS
|-
|T||LU8||4.9&amp;nbsp;L||V8 Turbo||4 Barrel Carburetor |4BBL||OHV||Pontiac V8. 301 cu. in. '81 Pontiac Firebird Formula &amp; Trans Am.
|-
|T||LT7||4.3&amp;nbsp;L||V6||Indirect injection Diesel||OHV||Oldsmobile Diesel V6. FWD version for '82-'85 GM A-bodies.
|-
|T||LS2||4.3&amp;nbsp;L||V6||Indirect injection Diesel||OHV||Oldsmobile Diesel V6. FWD version for '85 GM C-bodies.
|-
|T||LH0||3.1&amp;nbsp;L||V6||Fuel injection#Multi Port Fuel injection|MPFi||OHV||Chevrolet 60° V6 (longitudinally mounted). '90-'92 Chevy Camaro, Pontiac Firebird.
|-
|T||LH0||3.1&amp;nbsp;L||V6||Fuel injection#Multi Port Fuel injection|MPFi||OHV||Chevrolet 60° V6 (transversely mounted). Gen II. '88-'91 Pontiac 6000,&lt;br /&gt; '89-'93 Grand Prix, Oldsmobile Cutlass Supreme, Buick Regal, '90-'94 Chevy Cavalier, Lumina,&lt;br /&gt; '91-'94 Pontiac Sunbird, '90-'93 Chevy Corsica/Beretta, '90 Celebrity
|-
|T||LD9||2.4&amp;nbsp;L||Straight-4|I4||Fuel injection#Sequential Multi-port injection|SFI||DOHC,&lt;br /&gt; 16 valve||Oldsmobile Quad 4 (&quot;2.4 Twin Cam&quot;). '96-'01 Pontiac Grand Am, '96-'97 Oldsmobile Achieva, Buick Skylark, '99-'01 Oldsmobile Alero, '97-'99 Chevy Malibu, '96-'02 Chevy Cavalier, Pontiac Sunfire
|-
|T||LP1||2.8&amp;nbsp;L||V6||Fuel injection#Sequential Multi-port injection|SFI||DOHC,&lt;br /&gt; 24 valve||GM High Feature V6. '05-'07 Cadillac CTS
|-
|T||LS9||6.2&amp;nbsp;L||V8 Supercharged||Fuel injection#Sequential Multi-port injection|SFI||OHV||Gen IV Chevy Small-Block V8. Aluminum Block &amp; Heads. '10-'13 Corvette ZR1.
|-
|T||LFV||1.5L||I4 Turbo||Direct Injection|DI||DOHC,&lt;br /&gt; 16 valve||GM Small Gasoline Engine. VVT. '16-'25 Chevy Malibu.
|-
|U||L68||2.5L||I4||Fuel injection#Throttle Body injection|TBI||OHV||Pontiac Iron Duke/Tech IV engine. Transversely mounted. '85-'91 N-bodies
|-
|U||LS2||6.0&amp;nbsp;L||V8||Fuel injection#Sequential Multi-port fuel injection|SFI||OHV||Gen IV Chevy Small-Block V8. Aluminum Block &amp; Heads.&lt;br /&gt; '05-'07 Corvette, '05-'06 Pontiac GTO, '06-'07 Cadillac CTS V-Series
|-
|U||LE9||2.4&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 16 valve||GM Ecotec Gen II. E85 Flex-Fuel. 2011-12 Chevy Malibu. 
|-
|U||LKN||1.8L||I4||Direct Injection|DI||DOHC,&lt;br /&gt; 16 valve||Full Hybrid. GM Medium Gasoline Engine. VVT. Made in Szentgotthárd, Hungary.&lt;br&gt; '16-'19 Chevy Malibu Hybrid
|-
|V||LT6||4.3&amp;nbsp;L||V6||Indirect injection Diesel||OHV||Oldsmobile Diesel V6. RWD version.&lt;br /&gt; '82-'83 Chevy Malibu, Monte Carlo, '82-'85 Oldsmobile Cutlass Supreme, Buick Regal
|-
|V||LG5||3.1&amp;nbsp;L||V6 Turbo||Fuel injection#Multi-port fuel injection|MPFI||OHV||Chevrolet 60° V6. Gen II. Intercooled. (ASC/McLaren modified).&lt;br /&gt; '89-'90 Pontiac Grand Prix Turbo coupe, '90 Grand Prix STE Turbo sedan
|-
|V||LLT||3.6L||V6||Direct Injection|DI||DOHC,&lt;br /&gt; 24 valve||GM High Feature V6. '08-'11 Cadillac CTS, STS, '10-'11 Chevrolet Camaro, Buick LaCrosse
|-
|V||LHU||2.0&amp;nbsp;L||Straight-4|I4 Turbo||Direct Injection|DI||DOHC,&lt;br /&gt; 16 valve||E85 Flex Fuel (N/A on Regal GS). GM Ecotec engine, Gen II. VVT.&lt;br /&gt; Buick Regal '11-'13, Verano '13-'16. 
|-
|W||L37||4.9&amp;nbsp;L||V8||4 Barrel Carburetor |4BBL||OHV||Pontiac V8. 301 cu. in. '81 Pontiac Firebird, LeMans Safari wagon.
|-
|W||LB6||2.8&amp;nbsp;L||V6||Fuel injection#Multi-port fuel injection|MFI||OHV||Gen I/II Chevrolet 60° V6 (transversely mounted). '85 Chevy Citation, Buick Skylark,&lt;br /&gt; '85-'89 Chevy Cavalier, Celebrity, Pontiac 6000, '85-'88 Cadillac Cimarron,&lt;br /&gt; '85-'87 Oldsmobile Firenza, '86-'89 Cutlass Ciera, '87-'88 Buick Century, '87-'89 Chevy Corsica/Beretta, '88-'89 Pontiac Grand Prix, Oldsmobile Cutlass Supreme, Buick Regal
|-
|W||L64||3.1&amp;nbsp;L||V6||Fuel injection#Multi-port fuel injection|MFI||OHV||Flex-fuel: Gas/M85 or Gas/E85 (2 versions). Gen II Chevrolet 60° V6. '93 Chevy Lumina VFV
|-
|W||L99||4.3&amp;nbsp;L||V8||Fuel injection#Sequential Multi-port injection|SFI||OHV||Gen II Chevy Small-Block V8. '94-'96 Chevy Caprice.
|-
|W||LS3||6.2&amp;nbsp;L||V8||Fuel injection#Sequential Multi-port injection|SFI||OHV||Gen IV Chevy Small-Block V8. Aluminum Block &amp; Heads.&lt;br /&gt; '08-'13 Corvette, '10-'15 Camaro SS (man. trans.), '09 Pontiac G8 GXP, '14-'17 Chevy SS
|-
|W||LGY||3.0L||V6 Twin Turbo||Direct Injection|DI||DOHC,&lt;br /&gt; 24 valve||GM High Feature V6, 4th gen. VVT. Active Fuel Management. '20+ Cadillac CT5, CT5-V
|-
|X||LE2||2.8&amp;nbsp;L||V6||2 Barrel Carburetor |2BBL||OHV||Chevrolet 60° V6 (transversely mounted). '81-'85 Chevy Citation, Buick Skylark,&lt;br /&gt; '81-'84 Pontiac Phoenix, Oldsmobile Omega, '82-'86 Chevy Celebrity, Pontiac 6000,&lt;br /&gt; '86 Oldsmobile Cutlass Ciera, Buick Century 
|-
|X||LQ1||3.4&amp;nbsp;L||V6||Fuel injection#Multi-port fuel injection|MPFI||DOHC,&lt;br /&gt; 24 valve||Chevrolet 60° V6 (&quot;Twin Dual Cam V6&quot;). '91-'97 Chevy Lumina, '95-'97 Chevy Monte Carlo,&lt;br /&gt; '91-'96 Pontiac Grand Prix, Oldsmobile Cutlass Supreme
|-
|X||LNF||2.0&amp;nbsp;L||Straight-4|I4 Turbo||Direct Injection|DI||DOHC,&lt;br /&gt; 16 valve||GM Ecotec engine, Gen II. VVT.&lt;br /&gt; '07-'10 Pontiac Solstice GXP, Saturn Sky Red Line, '08-'10 Chevy Cobalt SS Turbo. 
|-
|X||LTG||2.0&amp;nbsp;L||Straight-4|I4 Turbo||Direct Injection|DI||DOHC,&lt;br /&gt; 16 valve||GM Ecotec engine, Gen III. VVT. '13-'22 Chevy Malibu, '13-'19 Cadillac ATS, '14-'20 Buick Regal,&lt;br /&gt; '14-'19 Cadillac CTS, '16-'23 Chevy Camaro, '16-'18 Cadillac CT6.
|-
|X||LTG||2.0&amp;nbsp;L||Straight-4|I4 Turbo||Direct Injection|DI||DOHC,&lt;br /&gt; 16 valve||Plug-in hybrid. GM Ecotec engine, Gen III. VVT. '17-'18 Cadillac CT6 PHEV. (VIN starts with LRE)
|-
|Y||LV2||5.0&amp;nbsp;L||V8||4 Barrel Carburetor |4BBL||OHV||Oldsmobile &quot;Rocket&quot; V8 (307 cu. in.) '86-'90 Chevy Caprice wagon, '87 Caprice sedan (Can.),&lt;br /&gt; '81 Pontiac Bonneville, Catalina, '86 Parisienne, '87-'89 Safari wagon, '81-'84 Oldsmobile 98,&lt;br /&gt; '81-'85 Delta 88, Toronado, '81-'90 Custom Cruiser, '81 Cutlass Cruiser, '82-'87 Cutlass Supreme,&lt;br /&gt; '88 Cutlass Supreme Classic, '81-'84 Buick Electra, '85-'89 Electra Estate wagon,&lt;br /&gt; '81-'85 LeSabre, Riviera, '86-'89 LeSabre Estate wagon, '90 Estate wagon, '86-'87 Regal,&lt;br /&gt; '86 Cadillac Fleetwood Brougham, '87-'90 Brougham
|-
|Y||LD8||4.6&amp;nbsp;L||V8||Fuel injection#Sequential Multi-port injection|SFI||DOHC,&lt;br /&gt; 32 valve||Cadillac Northstar V8 (Torque tuned FWD) (Premium V). '93-'02 Cadillac Eldorado,&lt;br /&gt; '94-'04 Cadillac Seville SLS, '94-'05 Cadillac DeVille, '06-'11 Cadillac DTS,&lt;br /&gt; '04-'05 Pontiac Bonneville GXP, '06-'08 Buick Lucerne
|-
|Y||L76||6.0&amp;nbsp;L||V8||Fuel injection#Sequential Multi-port fuel injection|SFI||OHV||Gen IV Chevy Small-Block V8. Aluminum Block &amp; Heads. With Active Fuel Management.&lt;br /&gt; '08-'09 Pontiac G8 GT.
|-
|Y||LF1||3.0L||V6||Direct Injection|DI||DOHC,&lt;br /&gt; 24 valve||GM High Feature V6. VVT. 2011 Cadillac CTS
|-
|Y||LF4||3.6L||V6 Twin Turbo||Direct Injection|DI||DOHC,&lt;br /&gt; 24 valve||GM High Feature V6. Cadillac ATS-V '16-'19
|-
|Z||LH7||2.8&amp;nbsp;L||V6||2 Barrel Carburetor |2BBL||OHV||Chevrolet 60° V6 (transversely mounted). H.O. '81-'84 Chevy Citation, '82-'84 Pontiac Phoenix, Oldsmobile Omega ES, Buick Skylark, '83-'84 Pontiac 6000 STE, '84 Chevy Celebrity 
|-
|Z||LB4||4.3L||V6||Fuel injection#Throttle Body injection|TBI||OHV||Chevrolet 90° V6 (Chevy Small-Block V8 Derived). '85 Chevy Impala, '85-'90 Caprice,&lt;br /&gt; '92-'93 Caprice 9C6 taxi, '85-'88 Monte Carlo, '85-'86 Pontiac Parisienne, '86-'87 Grand Prix,&lt;br&gt; '86 Bonneville.
|-
|Z||LAT||2.4L||I4||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 16 valve||Mild Hybrid. GM Ecotec Gen II. VVT. '10 Chevy Malibu Hybrid
|-
|Z||LUZ||2.0&amp;nbsp;L||I4 Turbo||Direct injection &lt;br /&gt; Common-rail Diesel||DOHC,&lt;br /&gt; 16 valve||GM Family B Diesel (Based on Fiat JTD engine). Made by Opel in Kaiserslautern, Germany.&lt;br /&gt; Iron Block, Aluminum Heads. '14-'15 Chevy Cruze Diesel.
|-
|1||LC1||2.8&amp;nbsp;L||V6||2 Barrel Carburetor |2BBL||OHV||Chevrolet 60° V6 (longitudinally mounted). '82-'84 Camaro/Firebird.
|-
|1||LL8||2.0&amp;nbsp;L||I4||Fuel injection#Throttle Body injection|TBI||OHV||Chevrolet &quot;122&quot; engine. '87-'89 Chevy/Olds/Buick J-cars &amp; Chevy L-cars.
|-
|1||L67||3.8&amp;nbsp;L||V6 Supercharged||Fuel injection#Sequential Multi-port injection|SFI||OHV||Buick V6 (3800 Supercharged Series I). '91-'95 Buick Park Avenue Ultra,&lt;br /&gt; '92-'95 Pontiac Bonneville, Oldsmobile 98, '95 Buick Riviera, Oldsmobile LSS
|-
|1||L67||3.8&amp;nbsp;L||V6 Supercharged||Fuel injection#Sequential Multi-port injection|SFI||OHV||Buick V6 (3800 Supercharged Series II). '96-'05 Buick Park Avenue Ultra,&lt;br /&gt; '96-'99 Buick Riviera, Oldsmobile LSS, '96-'03 Pontiac Bonneville, '97-'03 Grand Prix,&lt;br /&gt; '97-'04 Buick Regal, '04-'05 Chevy Impala SS, Monte Carlo SS Supercharged
|-
|1||LZ9||3.9L||V6||Fuel injection#Sequential Multi-port injection|SFI||OHV||GM High Value 60° V6. VVT.&lt;br /&gt; '06-'07 Chevy Malibu SS, '06-'09 Pontiac G6, '06 Chevy Monte Carlo, Impala, '09-'10 Buick Lucerne
|-
|1||2H0||1.8&amp;nbsp;L||Straight-4|I4||Fuel injection#Sequential Multi-port fuel injection|SFI||DOHC,&lt;br /&gt; 16 valve||GM Family 1 engine, Gen III. VVT. Made in Szentgotthárd, Hungary. '08 (&amp; '09 in Canada) Saturn Astra
|-
|1||LE5||2.4&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 16 valve||GM Ecotec Gen II. VVT. '11 &amp; some '12 Chevy Malibu w/LE5 engine.
|-
|2||LQ9||2.5L||I4||Fuel injection#Throttle Body injection|TBI||OHV||Pontiac Iron Duke/Tech IV engine. Longitudinally mounted. '82-'85 Camaro/Firebird.
|-
|2||LS3||1.0&amp;nbsp;L||Straight-3|I3 Turbo||Fuel injection#Multi-port fuel injection|MFI||SOHC,&lt;br /&gt; 6 valve ||Suzuki G10T engine. '87-'88 Chevrolet Sprint Turbo
|-
|2||LY8||1.3&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port fuel injection|MFI||SOHC,&lt;br /&gt; 16 valve||Suzuki G13BB engine. '98-'01 Chevrolet Metro
|-
|2||L26||3.8&amp;nbsp;L||V6||Fuel injection#Sequential Multi-port injection|SFI||OHV||Buick V6 (3800 Series III). '04-'08 Pontiac Grand Prix, '05-'09 Buick LaCrosse, '06-'08 Buick Lucerne
|-
|2||L77||6.0&amp;nbsp;L||V8||Fuel injection#Sequential Multi-port fuel injection|SFI||OHV||Gen IV Chevy Small-Block V8. Aluminum Block &amp; Heads. With Active Fuel Management.&lt;br /&gt; E85 Flex Fuel. '11-'17 Chevy Caprice PPV.
|-
|3||LC8||3.8&amp;nbsp;L||V6|V6 Turbo||4 Barrel Carburetor |4BBL||OHV||Buick V6. 231 cu. in. '81-'82 Buick Regal, Riviera, '81 Chevy Monte Carlo.
|-
|3||LG3||3.8&amp;nbsp;L||V6||Fuel injection#(Sequential) Multi-port injection|MFI/SFI||OHV||Buick V6. '84-'88 Oldsmobile Cutlass Ciera, Buick Century, '85 &amp; '87 Oldsmobile 98, Buick Electra,&lt;br /&gt; '86-'88 Oldsmobile Delta 88, Buick LeSabre, '87 Oldsmobile Toronado, Buick Riviera,&lt;br /&gt; '87-'88 Pontiac Bonneville.
|-
|3||LW2||4.5&amp;nbsp;L||V8||Fuel injection#Multi-port fuel injection|MFI||OHV||Cadillac High Technology V8. '90 Cadillac DeVille/Fleetwood/Sixty Special/Eldorado/Seville.
|-
|3||L40||2.3&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port fuel injection|MFI||SOHC,&lt;br /&gt; 8 valve||Oldsmobile Quad 4 (&quot;Quad OHC&quot;). '92-'94 Pontiac Grand Am, Oldsmobile Achieva, Buick Skylark
|-
|3||LZG||3.9L||V6||Fuel injection#Sequential Multi Port Fuel injection|SFI||OHV||E85 Flex Fuel. GM High Value 60° V6. VVT. Active Fuel Management. '08 Chevy Impala
|-
|3||LFX||3.6L||V6||Direct Injection|DI||DOHC,&lt;br /&gt; 24 valve||GM High Feature V6. VVT. E85 Flex Fuel.&lt;br /&gt; '12-'16 Buick LaCrosse, '12-'15 	Chevrolet Camaro, Cadillac CTS, '12-'17 Chevrolet Caprice PPV,&lt;br /&gt; '12-'20 Chevrolet Impala, '14-'16 Chevrolet Impala Limited, '13-'15 Cadillac ATS, '13-'19 Cadillac XTS  
|-
|3||LT6||5.5&amp;nbsp;L||V8||Direct injection|DI||DOHC,&lt;br /&gt; 32 valve||Chevrolet Gemini Small-Block V8. Aluminum Block &amp; Heads. Flat-plane crank. VVT.&lt;br /&gt; For mid-engine C8 Corvette Z06 '23+.
|-
|4||LC4||4.1&amp;nbsp;L||V6|V6||4 Barrel Carburetor |4BBL||OHV||Buick V6. '81-'84 Buick LeSabre, Electra, Riviera, Oldsmobile Toronado, '81-'82 Cadillac DeVille, Fleetwood Brougham, Eldorado, Seville, '81-'83 Oldsmobile 98, '82-'84 Buick Regal,&lt;br /&gt; '82 Pontiac Grand Prix, Bonneville G
|-
|4||LC9||1.6&amp;nbsp;L||Straight-4|I4||2 Barrel Carburetor |2BBL||SOHC,&lt;br /&gt; 8 valve||Toyota 4A-C engine. '85-'88 Chevy Nova
|-
|4||LN2||2.2&amp;nbsp;L||Straight-4|I4||Fuel injection#(Sequential) Multi-port injection|MPI/SFI||OHV||Chevrolet &quot;122&quot; engine. '92-'02 Cavalier, '95-'02 Sunfire, '92-'96 Corsica/Beretta, '93 Lumina,&lt;br /&gt; '93-'96 Cutlass Ciera, Century.
|-
|4||L32||3.8&amp;nbsp;L||V6 Supercharged||Fuel injection#Sequential Multi-port injection|SFI||OHV||Buick V6 (3800 Supercharged Series III). '04-'07 Pontiac Grand Prix
|-
|4||LUU||1.4L||I4||Fuel injection#Sequential Multi-port fuel injection|SFI||DOHC,&lt;br /&gt; 16 valve||GM Family 0 Engine, Gen III. VVT. ([[w:EREV|Range extender]]). Early production engines were made in Aspern, Austria; later made in Flint, MI. '11-'15 Chevy Volt, '14 &amp; '16 Cadillac ELR. 
|-
|4||LT2||6.2&amp;nbsp;L||V8||Direct injection|DI||OHV||Gen V Chevy Small-Block V8. Aluminum Block &amp; Heads. Active Fuel Management. VVT.&lt;br /&gt; For mid-engine C8 Corvette Stingray '20+.
|-
|4||LT2||6.2&amp;nbsp;L||V8||Direct injection|DI||OHV||Full Hybrid. Gen V Chevy Small-Block V8. Aluminum Block &amp; Heads. Active Fuel Management. VVT.&lt;br /&gt; For mid-engine C8 Corvette E-Ray '24+.
|-
|5||LW9||2.5L||I4||2 Barrel Carburetor |2BBL||OHV||Pontiac Iron Duke engine. '81 Chevy Citation, Pontiac Phoenix, Oldsmobile Omega, Buick Skylark.
|-
|5||LR6||4.5&amp;nbsp;L||V8||Fuel injection#Throttle Body injection|TBI (DFI)||OHV||Cadillac High Technology V8. '88-'89 Cadillac DeVille/Fleetwood/Sixty Special/Eldorado/Seville.
|-
|5||LY9||1.0&amp;nbsp;L||Straight-3|I3||2BBL||SOHC,&lt;br /&gt; 6 valve ||Suzuki G10A engine. '86 Chevrolet Sprint
|-
|5||LM9||1.0&amp;nbsp;L||Straight-3|I3||2BBL||SOHC,&lt;br /&gt; 6 valve ||Suzuki G10A engine. '87-'88 Chevrolet Sprint
|-
|5||LW0||1.6&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 16 valve||Toyota 4A-GE engine. '88 Chevy Nova Twin Cam, '90-'92 Geo Prizm GSi
|-
|5||LW0||1.6&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 16 valve||Isuzu 4XE1-UW engine. '90-'91 Geo Storm GSi
|-
|5||LT4||5.7&amp;nbsp;L||V8||Fuel injection#Sequential Multi-port injection|SFI||OHV||Gen II Chevy Small-Block V8. '96 Corvette (man. trans.)
|-
|5||LAT||2.4L||I4||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 16 valve||Mild Hybrid. GM Ecotec Gen II. VVT. '07-'09 Saturn Aura Green Line, '08-'09 Chevy Malibu Hybrid
|-
|5||LAP||2.2&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 16 valve||GM Ecotec Gen II. VVT. '10 Chevy Cobalt.
|-
|5||LFW||3.0L||V6||Direct Injection|DI||DOHC,&lt;br /&gt; 24 valve||GM High Feature V6. VVT. '12-'13 Cadillac CTS, '14 CTS wagon
|-
|5||L3A||1.5L||I4||Direct Injection|DI||DOHC,&lt;br /&gt; 16 valve||GM Small Gasoline Engine. VVT. ([[w:EREV|Range extender]]). '16-'19 Chevy Volt. 
|-
|5||LWC||1.6L||I4 Turbo||Direct Injection|DI||DOHC,&lt;br /&gt; 16 valve||GM Medium Gasoline Engine, H.O. VVT. Made in Szentgotthárd, Hungary. '16-'19 Buick Cascada
|-
|5||LS6||6.7&amp;nbsp;L||V8||Port/Direct injection||OHV||Gen VI Chevy Small-Block V8. Aluminum Block &amp; Heads. Active Fuel Management. VVT.&lt;br /&gt; For mid-engine C8 Corvette Stingray, Grand Sport '27+. 
|-
|5||LS6||6.7&amp;nbsp;L||V8||Port/Direct injection||OHV||Full Hybrid. Gen VI Chevy Small-Block V8. Aluminum Block &amp; Heads. Active Fuel Management. VVT.&lt;br /&gt; For mid-engine C8 Corvette Grand Sport X '27+.
|-
|6||L81||5.7&amp;nbsp;L||V8||4 Barrel Carburetor |4BBL||OHV||Gen I Chevy Small-Block V8. '81 Corvette
|-
|6||LM1||5.7&amp;nbsp;L||V8||4 Barrel Carburetor |4BBL||OHV||Gen I Chevy Small-Block V8. '83-'85 Impala 9C1 Police, '86-'88 Caprice 9C1 Police
|-
|6||L73||1.6&amp;nbsp;L||Straight-4|I4||Fuel injection#Throttle Body injection|TBI||SOHC,&lt;br /&gt; 8 valve||GM Family 1 engine. Made in South Korea by Daewoo. '88-'93 Pontiac LeMans
|-
|6||LP2||1.0&amp;nbsp;L||Straight-3|I3||Fuel injection#Throttle Body injection|TBI||SOHC,&lt;br /&gt; 6 valve ||Suzuki G10A engine. '89-'97 Geo Metro, '98-'00 Chevrolet Metro
|-
|6||L01||1.6&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 16 valve||Toyota 4A-FE engine. '89-'97 Geo Prizm base/LSi
|-
|6||L01||1.6&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port fuel injection|MFI||SOHC,&lt;br /&gt; 12 valve||Isuzu 4XE1-V engine. '90-'93 Geo Storm (base model)
|-
|6||L42||2.2&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 16 valve||GM Ecotec Gen I (Bi-Fuel Gas/CNG). '03-'04 Chevy Cavalier
|-
|6||L91||1.6&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 16 valve||E-TEC II. '04-'07 Chevy Aveo
|-
|6||LXT||1.6&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 16 valve||E-TEC II. '08 Chevy Aveo
|-
|6||LGW||3.0L||V6 Twin Turbo||Direct Injection|DI||DOHC,&lt;br /&gt; 24 valve||GM High Feature V6, 4th gen. VVT. Active Fuel Management. '16-'19 Cadillac CT6
|-
|6||LT4||6.2&amp;nbsp;L||V8 Supercharged||Direct injection|DI||OHV||Gen V Chevy Small-Block V8. Aluminum Block &amp; Heads. With Active Fuel Management. VVT.&lt;br /&gt; '15-'19 Corvette Z06, '17-'24 Camaro ZL1, '16-'19 Cadillac CTS V-Series,&lt;br /&gt; '22+ Cadillac CT5-V Blackwing
|-
|7||LU5||5.0&amp;nbsp;L||V8||Cross-Fire fuel injection|CFI||OHV||Gen I Chevy Small-Block V8. (305 cu. in.) '82 Camaro, Firebird. Dual throttle-body fuel injection.
|-
|7||L69||5.0&amp;nbsp;L||V8||4 Barrel Quadrajet Carburetor |4BBL||OHV||Gen I Chevy Small-Block V8 (High Output 5.0L). (305 cu. in.). '83 F-cars, '83 Chevy Monte Carlo SS
|-
|7||LC5||1.5&amp;nbsp;L||I4||2 Barrel Carburetor |2BBL||SOHC,&lt;br /&gt; 8 valve||Isuzu 4XC1 engine. '86-'88 Chevrolet Spectrum, '89 Geo Spectrum.
|-
|7||LC2||3.8&amp;nbsp;L||V6|V6 Turbo||Fuel injection#Sequential multi-port injection|SFI||OHV||Intercooled. Buick V6. '86-'87 Buick Regal. '89 Pontiac 20th Anniversary Turbo Trans Am
|-
|7||LC7||4.1&amp;nbsp;L||V8||Fuel injection#Multi-port fuel injection|MFI||OHV||Cadillac High Technology V8. '87-'88 Cadillac Allante.
|-
|7||L05||5.7&amp;nbsp;L||V8||Fuel injection#Throttle Body injection|TBI||OHV||Gen I Chevy Small-Block V8. '89-'93 Chevy Caprice (police only for '89-'91),&lt;br /&gt; '92-'93 Buick Roadmaster, '92 Oldsmobile Custom Cruiser, '90-'92 Cadillac Brougham, '93 Fleetwood.
|-
|7||LL0||1.9&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port injection|MFI||DOHC,&lt;br /&gt; 16 valve||Saturn I4 engine. '91-'02 Saturn S-Series
|-
|7||LY7||3.6&amp;nbsp;L||V6||Fuel injection#Sequential Multi-port injection|SFI||DOHC,&lt;br /&gt; 24 valve||GM High Feature V6. VVT. '04-'09 Cadillac CTS, '05-'07 STS, '05-'08 Buick LaCrosse,&lt;br /&gt; '07-'09 Pontiac G6, Saturn Aura, '08-'09 Pontiac G8, '08-'12 Chevy Malibu
|-
|7||LT1||6.2&amp;nbsp;L||V8||Direct injection|DI||OHV||Gen V Chevy Small-Block V8. Aluminum Block &amp; Heads. With Active Fuel Management. VVT.&lt;br /&gt; '14-'19 Corvette, '16-'24 Camaro SS
|-
|7||LT7||5.5&amp;nbsp;L||V8 Twin Turbo||Port/Direct injection||DOHC,&lt;br /&gt; 32 valve||Chevrolet Gemini Small-Block V8. Aluminum Block &amp; Heads. Flat-plane crank. VVT.&lt;br /&gt; For mid-engine C8 Corvette ZR1 '25+. (1,064 hp)
|-
|7||LT7||5.5&amp;nbsp;L||V8 Twin Turbo||Port/Direct injection||DOHC,&lt;br /&gt; 32 valve||Full Hybrid. Chevrolet Gemini Small-Block V8. Aluminum Block &amp; Heads. Flat-plane crank. VVT.&lt;br /&gt; For mid-engine C8 Corvette ZR1X '26+. (1,250 hp)
|-
|8||LV8||4.3&amp;nbsp;L||V8||2 Barrel Carburetor |2BBL||OHV||Oldsmobile &quot;Rocket&quot; V8 (260 cu. in.) '82 Oldsmobile Cutlass, Delta 88.
|-
|8||LT8||4.1&amp;nbsp;L||V8||Fuel injection#Throttle Body injection|TBI (DFI)||OHV||Cadillac High Technology V8. '82-'87 Cadillac DeVille, Eldorado, Seville, '82-'85 Fleetwood Brougham, '85-'87 Fleetwood, '87 Fleetwood Sixty Special.
|-
|8||LC8||3.8&amp;nbsp;L||V6|V6 Turbo||4 Barrel Carburetor |4BBL||OHV||Buick V6. '83 Buick Regal, Riviera.
|-
|8||L83||5.7&amp;nbsp;L||V8||Cross-Fire fuel injection|CFI||OHV||Gen I Chevy Small-Block V8. '82, '84 Corvette. Dual throttle-body fuel injection.  1st fuel injected Corvette since 1965.
|-
|8||L98||5.7&amp;nbsp;L||V8||Tuned-port fuel injection|TPI||OHV||Gen I Chevy Small-Block V8. '85-'91 Corvette, '87-'92 Chevy Camaro, Pontiac Firebird.
|-
|8||LQ6||4.5&amp;nbsp;L||V8||Fuel injection#Multi-port fuel injection|MFI||OHV||Cadillac High Technology V8. '89-'92 Cadillac Allante.
|-
|8||L24||1.9&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port injection|MFI||SOHC,&lt;br /&gt; 8 valve||Saturn I4 engine. '95-'02 Saturn S-Series
|-
|8||LX9||3.5&amp;nbsp;L||V6||Fuel injection#Sequential Multi-port injection|SFI||OHV||GM High Value 60° V6. 3498cc. '04-'06 Chevy Malibu, '05-'06 Pontiac G6
|-
|8||LF3||3.6L||V6 Twin Turbo||Direct Injection|DI||DOHC,&lt;br /&gt; 24 valve||GM High Feature V6. '14-'19 Cadillac CTS V-Sport, XTS V-Sport
|-
|8||LV6||1.8&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 16 valve||Isuzu 4XF1 engine. '92-'93 Geo Storm GSi.
|-
|8||LV6||1.8&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 16 valve||Toyota 7A-FE engine. '93-'97 Geo Prizm
|-
|8||LV6||1.8&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 16 valve||Toyota 1ZZ-FE engine. VVT-i from '00. '98-'02 Chevrolet Prizm, '03-'08 Pontiac Vibe
|-
|8||LAY||1.8&amp;nbsp;L||Straight-4|I4||Fuel injection#Sequential multi-port injection|SFI||DOHC,&lt;br /&gt; 16 valve||Toyota 2ZR-FE engine. Dual VVT-i. '09-'10 Pontiac Vibe
|-
|9||L17||1.6&amp;nbsp;L||Straight-4|I4||2 Barrel Carburetor |2BBL||SOHC,&lt;br /&gt; 8 valve||Isuzu G161Z engine made by GM in US. '81 Chevy Chevette, Pontiac T1000
|-
|9||L62||6.0&amp;nbsp;L||V8||Fuel injection#Throttle Body injection|TBI (DFI)||OHV||Cadillac 472-series V8 engine family. V8-6-4 cylinder deactivation.&lt;br /&gt; '81 Cadillacs, '82-'84 Fleetwood Limousine. 
|-
|9||LC3||3.8&amp;nbsp;L||V6||2 Barrel Carburetor |2BBL||OHV||Chevrolet 90° V6 (Chevy Small-Block V8 Derived). 229 cu. in. &lt;br /&gt; '83 Malibu, '83-'84 Monte Carlo, Impala, Caprice, '83 Pontiac Parisienne.
|-
|9||LG8||5.0&amp;nbsp;L||V8||4 Barrel Carburetor |4BBL||OHV||Oldsmobile &quot;Rocket&quot; V8 (307 cu. in.) H.O. '83-'84 Hurst/Olds, '85-'87 Oldsmobile Cutlass 442
|-
|9||LM9||3.8&amp;nbsp;L||V6|V6 Turbo||Fuel injection#Sequential multi-port injection|SFI||OHV||Buick V6. '84-'85 Buick Regal, Riviera.
|-
|9||L44||2.8&amp;nbsp;L||V6||Fuel injection#Multi-port fuel injection|MFI||OHV||Chevrolet 60° V6 (transversely mounted). H.O. '85-'88 Pontiac Fiero
|-
|9||LC0||1.5&amp;nbsp;L||I4 Turbo||Fuel injection#Multi-port fuel injection|MFI||SOHC,&lt;br /&gt; 8 valve||Isuzu 4XC1-T engine. '87-'88 Chevrolet Spectrum Turbo
|-
|9||LK0||1.9&amp;nbsp;L||Straight-4|I4||Fuel injection#Throttle Body injection|TBI||SOHC,&lt;br /&gt; 8 valve||Saturn I4 engine. '91-'94 Saturn S-Series
|-
|9||L37||4.6&amp;nbsp;L||V8||Fuel injection#Sequential Multi-port injection|SFI||DOHC,&lt;br /&gt; 32 valve||Cadillac Northstar V8 (H.O. FWD) (Premium V). '93 Cadillac Allanté,&lt;br /&gt; '93-'02 Cadillac Eldorado Touring Coupe, '93-'04 Cadillac Seville STS, '96-'05 Cadillac DeVille,&lt;br /&gt; '06-'11 Cadillac DTS, '08-'11 Buick Lucerne Super
|-
|9||L72||1.3&amp;nbsp;L||Straight-4|I4||Fuel injection#Throttle Body injection|TBI||SOHC,&lt;br /&gt; 8 valve ||Suzuki G13BA engine. '95-'97 Geo Metro
|-
|9||LUJ||1.4L||I4 Turbo||Fuel injection#Sequential Multi-port fuel injection|SFI||DOHC,&lt;br /&gt; 16 valve||GM Family 0 Engine, Gen III. VVT. Early production engines were made in Aspern, Austria; later made in Flint, MI. '11 Chevy Cruze
|-
|9||LL0||1.2&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 16 valve||Daewoo S-TEC II engine (1249 cc). VVT. Made in Changwon, S. Korea. '13-'15 Chevy Spark.
|-
|9||LT5||6.2&amp;nbsp;L||V8 Supercharged||Port/Direct injection||OHV||Gen V Chevy Small-Block V8. Aluminum Block &amp; Heads. VVT. '19 Corvette ZR1.
|-
|0||LH8||1.8&amp;nbsp;L||Straight-4|I4||Fuel injection#Throttle Body injection|TBI||SOHC,&lt;br /&gt; 8 valve||GM Family II engine. Made in Brazil.&lt;br /&gt; '82-'86 Pontiac J2000/2000/Sunbird, Oldsmobile Firenza, Buick Skyhawk. 
|-
|0||LAX||2.4&amp;nbsp;L||Straight-4|I4||Fuel injection#Sequential multi-port injection|SFI||DOHC,&lt;br /&gt; 16 valve||Toyota 2AZ-FE engine. VVT-i. '09-'10 Pontiac Vibe
|-
|0||LE9||2.4&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 16 valve||GM Ecotec Gen II. E85 Flex-Fuel. 2010 Chevy Malibu. 
|-
|0||LE5||2.4&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 16 valve||GM Ecotec Gen II. VVT. Most '12 Chevy Malibu w/LE5 engine.
|}

H.O.=High Output, CNG=Compressed Natural Gas, VVT=Variable Valve Timing, VVL=Variable Valve Lift

====Motor codes for electric passenger cars====

{| class=&quot;wikitable&quot;
|-
! VIN !! RPO !! Fuel !! Drive Wheels !! Application/Notes
|-
| 5 ||LN1|| Electricity || Front || '97, '99 General Motors EV1
|-
| 0 ||EN0|| Electricity || Front || '14-'16 Chevrolet Spark EV
|-
| 0 ||EN0|| Electricity || Front || '17-'23 Chevrolet Bolt EV
|-
| 0 ||EN0|| Electricity || Front || '22-'23 Chevrolet Bolt EUV
|-
|}

====Motor codes for LFP-powered electric passenger cars====

{| class=&quot;wikitable&quot;
|-
! VIN !! Motor &lt;br /&gt; RPO code !! # of Motors !! Battery Pack &lt;br /&gt; RPO code !! Fuel !! Drive Wheels !! Application/Notes
|-
|-
| V ||P9D (HPB)|| 1 || EJW || Electricity || Front || '27 Chevrolet Bolt
|}
LFP=Lithium Iron Phosphate

====Motor codes for Ultium-powered electric passenger cars====

{| class=&quot;wikitable&quot;
|-
! VIN !! Motor &lt;br /&gt; RPO code !! # of Motors !! Battery Module &lt;br /&gt; RPO code !! # of Modules !! Fuel !! Drive Wheels !! Application/Notes
|-
|-
| 1 ||X0E|| 2 || EXN || 16 || Electricity || All || '25- Cadillac Celestiq
|-
| 2 ||X0E|| 2 || EHT || 16 || Electricity || All || '25- Cadillac Celestiq &lt;br&gt; (Battery Module RPO code EHT is Configuration B)
|}

====Engine codes for light trucks====
GM encodes the engine type in character 8 of the VIN. The following table outlines the various engines encoded there:

{| class=&quot;wikitable&quot;
|-
! VIN !! RPO !! Size !! Type !! Fuel !! Valvetrain !! Engine Family/Notes/Applications
|-
| A ||LD5|| 3.8L || V6 || Gas ||OHV||2-bbl carb. Buick V6. (231 cu. in.) '81-'84 Chevy El Camino, GMC Caballero (CA emissions).
|-
| A ||LR1|| 1.9L || I4 || Gas ||SOHC,&lt;br /&gt; 8 valve||2-bbl carb. Isuzu G200 engine imported from Japan.&lt;br /&gt; '82-'85 Chevy S-10/GMC S-15, '83-'85 Chevy S-10 Blazer/GMC S-15 Jimmy
|-
| A ||L38|| 2.5L || I4 || Gas ||OHV||TBI. Pontiac Iron Duke/Tech IV engine. '91-'93 Chevy S-10/GMC Sonoma.
|-
| A ||LH2|| 4.6L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||SFI. Cadillac Northstar V8 (For RWD) (Premium V). '04-'09 Cadillac SRX
|-
| A ||L20|| 4.8L || V8 || Gas/E85 ||OHV|| Flex Fuel. SFI. Gen IV Chevrolet Small-Block V8. Iron Block/Aluminum Heads. VVT.&lt;br /&gt; '10-'13 GMT900 pickups, '10-'14 Express/Savana
|-
| A ||LCV|| 2.5L || I4 || Gas ||DOHC,&lt;br /&gt; 16 valve||GM Ecotec engine, Gen III. Direct Injection. VVT. '15-'22 Chevy Colorado, GMC Canyon,&lt;br /&gt; '17-'20 Buick Envision, '17-'21 GMC Acadia, '19-'21 Chevy Blazer
|-
| B ||LR2|| 2.8L || V6 || Gas ||OHV||2-bbl carb. Chevrolet 60° V6.&lt;br /&gt; '82-'85 Chevy S-10/GMC S-15, '83-'85 Chevy S-10 Blazer/GMC S-15 Jimmy
|-
| B ||LU2|| 4.3L || V6 || Gas ||OHV|| TBI. Chevrolet 90° V6 (Chevy Small-Block V8 Derived). '90-'91 Astro/Safari higher output engine option.
|-
| B ||L81|| 3.0L || V6 || Gas ||DOHC,&lt;br /&gt; 24 valve||SFI. Opel 54° V6 engine (Made in the UK). '02-'03 Saturn Vue
|-
| B ||L33|| 5.3L || V8 || Gas ||OHV||SFI. Gen III Chevrolet Small-Block V8. Vortec 5300 H.O. 310hp. Aluminum Block &amp; Heads.&lt;br /&gt; '05-'06 Silverado/Sierra 1500 4wd ext. cab short bed,&lt;br&gt; '07 Silverado Classic 1500/Sierra Classic 1500 4wd ext. cab short bed.
|-
| B ||LE8|| 2.2L || I4 || Gas/E85 ||DOHC,&lt;br /&gt; 16 valve||Flex-Fuel. SFI. GM Ecotec Gen II. VVT. '09-'10 Chevy HHR
|-
| B ||LC8|| 6.0L || V8 || Gas/CNG ||OHV||Bi-Fuel (Also Gas/LPG in Express/Savana). SFI. Gen IV Chevrolet Small-Block V8. Iron Block &amp; Aluminum Heads. VVT. '11-'20 Express/Savana, '13-'19 Silverado HD/Sierra HD.
|-
| B ||LUV|| 1.4L ||I4 Turbo|| Gas ||DOHC,&lt;br /&gt; 16 valve||GM Family 0 Engine, Gen III. SFI. VVT.&lt;br /&gt; '13-'21 Buick Encore, '15-'21 Chevy Trax (also '13-'14 Trax in Canada)
|-
| C ||LH6|| 6.2L || V8 || Diesel ||OHV||Detroit Diesel V8. For sub-8,500 lb. GVWR trucks '82-'93. '82-'86 C/K pickups, '87 R/V pickups,&lt;br /&gt; '88-'93 C/K, Sierra pickups, '82-'91 Blazer/Jimmy, Suburban, '83-'93 full-size vans
|-
| C ||L34|| 2.0L || I4 || Gas ||DOHC,&lt;br /&gt; 16 valve||Suzuki J20A engine. MFI. '99-'03 Chevrolet Tracker
|-
| C ||LY2|| 4.8L || V8 || Gas ||OHV||SFI. Gen IV Chevrolet Small-Block V8. Iron Block/Aluminum Heads.&lt;br /&gt; '07-'09 GMT900 pickups, '07-'09 Tahoe/Yukon, '08-'09 Express/Savana
|-
| C ||LAF|| 2.4L || I4 || Gas ||DOHC,&lt;br /&gt; 16 valve||GM Ecotec engine, Gen II. Direct Injection. VVT. Chevy Equinox, GMC Terrain '11. 
|-
| C ||L83|| 5.3L || V8 || Gas/E85 ||OHV|| Flex Fuel. Gen V Chevrolet Small-Block V8 (EcoTec3). Direct injection, VVT. Active Fuel Management&lt;br /&gt; '14-'19 K2XX pickups, '15-'20 K2XX SUVs.
|-
| C ||L2R|| 2.7L ||I4 Turbo||| Gas ||DOHC,&lt;br /&gt; 16 valve||GM L3B Tripower engine (&quot;TurboMax&quot;) - Detuned version. Direct Injection. VVT, VVL. Active Fuel Management. '23-'24 Chevy Colorado.
|-
| D ||LE3|| 4.1L || I6 || Gas ||OHV||2-bbl carb. Chevrolet Turbo-Thrift I6.&lt;br /&gt; '81-'84 Chevy/GMC C/K pickups, full-size vans, '81-'82 Blazer/Jimmy
|-
| D ||LG6|| 3.1L || V6 || Gas ||OHV||TBI. Chevrolet 60° V6. '90-'95 U-body minivans.
|-
| D ||L61|| 2.2L || I4 || Gas ||DOHC,&lt;br /&gt; 16 valve||SFI. GM Ecotec Gen I. '02-'07 Saturn Vue, '06 Chevy HHR.
|-
| D ||L61|| 2.2L || I4 || Gas ||DOHC,&lt;br /&gt; 16 valve||SFI. GM Ecotec Gen II. '07-'08 Chevy HHR.
|-
| D ||LLT|| 3.6L || V6 || Gas ||DOHC,&lt;br /&gt; 24 valve||GM High Feature V6. Direct Injection. '09-'16 GMC Acadia, '17 GMC Acadia Limited,&lt;br /&gt; '09-'17 Chevrolet Traverse, Buick Enclave, '09-'10 Saturn Outlook
|-
| D ||LBZ|| 6.6L || V8 Turbo || Diesel ||OHV,&lt;br /&gt; 32 valve||Duramax 6600 V8 engine.&lt;br /&gt; Mid '06 Silverado HD/Sierra HD &amp; '07 Silverado Classic HD/Sierra Classic HD
|-
| D ||L84|| 5.3L || V8 || Gas/E85 ||OHV|| Gen V Chevrolet Small-Block V8 (EcoTec3).  Direct injection, VVT. With Dynamic Fuel Management&lt;br /&gt; '19+ Chevy/GMC Silverado 1500/Sierra 1500, '21+ Tahoe/Yukon, Suburban/Yukon XL.
|-
| E ||LN8|| 2.5L || I4 || Gas ||OHV||TBI. Pontiac Iron Duke/Tech IV engine.&lt;br /&gt; '85-'90 Chevy/GMC S-10/S-15, Astro/Safari Cargo Van, '85-'88 S-10 Blazer/S-15 Jimmy.
|-
| E ||LLR|| 3.7L || I5 || Gas ||DOHC,&lt;br /&gt; 20 valve||Atlas I5. SFI. VVT.&lt;br /&gt; '07-'12 Colorado/Canyon, '07-'08 Isuzu i-370, '07-'10 Hummer H3, '09-'10 Hummer H3T  
|-
| E ||LA1|| 3.4L || V6 || Gas ||OHV||Chevrolet 60° V6. '96 GMT199 (U-body) minivans, '97-'05 GMT200 (U-body) minivans,&lt;br /&gt; '01-'05 Pontiac Aztek, '02-'05 Buick Rendezvous
|-
| F ||LF3|| 5.0L || V8 || Gas ||OHV|| 4-bbl carb. Gen I Chevrolet Small-Block V8. '81-'86 C/K, full-size vans, '81-'82 Blazer/Jimmy.&lt;br /&gt; CA emissions version of LE9 5.0 V8.
|-
| F ||L65|| 6.5L || V8 Turbo || Diesel ||OHV||Detroit Diesel V8. For over-8,500 lb. GVWR Chevy C/K, GMC Sierra trucks '92-'02,&lt;br /&gt; Chevy/GMC Suburban 1500/2500 '94-'99, over-8,500 lb. GVWR Express/Savana '96-'02
|-
| F ||LNJ|| 3.4L || V6 || Gas ||OHV||Chevrolet 60° V6. Made in China by SAIC-GM. '05-'09 Chevy Equinox, '06-'09 Pontiac Torrent.
|-
| F ||L94|| 6.2L || V8 || Gas/E85 ||OHV||Flex-Fuel. Gen IV Chevrolet Small-Block V8. Aluminum Block &amp; Heads. SFI. VVT. Active Fuel Management. '10-'14 GMC Yukon Denali/Yukon XL Denali, Cadillac Escalade/Escalade ESV.
|-
| F ||L20|| 4.8L || V8 || Gas/E85 ||OHV|| Flex Fuel. SFI. Gen IV Chevrolet Small-Block V8. Iron Block/Aluminum Heads. VVT.&lt;br /&gt; '15-'17 Express/Savana
|-
| F ||L82|| 5.3L || V8 || Gas ||OHV|| Gen V Chevrolet Small-Block V8 (EcoTec3). Direct injection, VVT. With Active Fuel Management&lt;br /&gt; '19-'21 Chevy Silverado 1500, GMC Sierra 1500 (T1XX).
|-
| G ||LG9|| 5.0L || V8 || Gas ||OHV|| 2-bbl carb. Gen I Chevrolet Small-Block V8. '81 Chevy/GMC C/K pickups, Blazer/Jimmy, full-size van
|-
| G ||L18|| 8.1L || V8 || Gas ||OHV||MFI. Vortec 8100. Gen VII Chevrolet Big-Block V8. '01-'02 C3500HD, '01-'06 Silverado HD/Sierra HD, '07 Silverado Classic HD/Sierra Classic HD, '01-'06 Suburban/Yukon XL 2500, '02-'06 Avalanche 2500, '01-'02 Express/Savana
|-
| G ||L96|| 6.0L || V8 || Gas/E85 ||OHV||Flex Fuel. SFI. Gen IV Chevrolet Small-Block V8. Iron Block &amp; Aluminum Heads. VVT.&lt;br /&gt; '10-'19 Silverado HD/Sierra HD, '10-'13 Suburban 2500/Yukon XL 2500, '16-'19 Suburban 3500,&lt;br /&gt; '10-'20 Express/Savana.
|-
| G ||LSD|| 1.5L || I4 Turbo || Gas ||DOHC,&lt;br /&gt; 16 valve||GM Small Gasoline Engine. Direct Injection. VVT. '23+ Chevy Equinox, GMC Terrain
|-
| H ||LG4|| 5.0L || V8 || Gas ||OHV||4-bbl carb. Gen I Chevy Small-Block V8. (305 cu. in.) '81-'87 Chevy El Camino, GMC Caballero.
|-
| H ||LE9|| 5.0L || V8 || Gas ||OHV|| 4-bbl carb. Gen I Chevrolet Small-Block V8. '81-'86 C/K pickups, Blazer/Jimmy, Suburban, full-size vans
|-
| H ||L03|| 5.0L || V8 || Gas ||OHV|| TBI. Gen I Chevrolet Small-Block V8. '87 R/V pickups, '88-'95 C/K, Sierra pickups, '87-'95 full-size vans, '87 Blazer/Jimmy, Suburban.
|-
| H ||LN2|| 2.2L || I4 || Gas ||OHV||SFI. Chevrolet &quot;122&quot; engine. '03 Chevy S-10/GMC Sonoma
|-
| H ||LS2|| 6.0L || V8 || Gas ||OHV||SFI. Gen IV Chevy Small-Block V8. Chevy SSR '05-'06, Trailblazer SS '06-'09, Saab 9-7X Aero '08-'09.
|-
| H ||LV3|| 4.3L || V6 || Gas/E85 ||OHV||Flex Fuel. Chevrolet 90° V6 - Gen V Chevrolet Small-Block V6 (EcoTec3). Direct injection, VVT. Active Fuel Management. '14-'21 Chevy Silverado 1500/GMC Sierra 1500.
|-
| J ||L39|| 4.4L || V8 || Gas ||OHV||2-bbl carb. Gen I Chevy Small-Block V8 (267 cu. in.) '81-82 Chevy El Camino, GMC Caballero.
|-
| J ||LL4|| 6.2L || V8 || Diesel ||OHV||Detroit Diesel V8. For over-8,500 lb. GVWR trucks '82-'93. '82-'86 C/K pickups, '87-'91 R/V pickups,&lt;br /&gt; '88-'93 C/K, Sierra pickups, '82-'91 Blazer/Jimmy, Suburban, '83-'93 full-size vans
|-
| J ||L29|| 7.4L || V8 || Gas ||OHV|| MFI. Vortec 7400. Gen VI Chevrolet Big-Block V8.&lt;br /&gt; '96-'00 C/K, Sierra pickups, Express/Savana, '96-'99 Suburban 2500
|-
| J ||LY5|| 5.3L || V8 || Gas ||OHV||SFI. Gen IV Chevrolet Small-Block V8. Active Fuel Management. Iron Block &amp; Aluminum Heads.&lt;br /&gt; '07-'09 Silverado/Sierra 1500, Tahoe/Yukon, Suburban/Yukon XL 1500, Avalanche
|-
| J ||LZ1|| 6.0L || V8 || Gas-Electric Hybrid ||OHV||2-Mode Hybrid. Gen IV Chevrolet Small-Block V8. Aluminum Block &amp; Heads. VVT. Active Fuel Management. '10-'13 Tahoe Hybrid, Yukon Hybrid, Escalade Hybrid, Silverado Hybrid, Sierra Hybrid
|-
| J ||L86|| 6.2L || V8 || Gas ||OHV||Gen V Chevrolet Small-Block V8 (EcoTec3). Direct injection, VVT. Active Fuel Management. &lt;br /&gt; '14-18 Chevy/GMC Silverado 1500/Sierra 1500,&lt;br /&gt; '18-20 Chevy Tahoe Premier, '19-'20 Chevy Suburban Premier, GMC Yukon/Yukon XL SLT,&lt;br /&gt; '15-'20 GMC Yukon Denali/Yukon XL Denali, Cadillac Escalade/Escalade ESV. 
|-
| K ||LC3|| 3.8L || V6 || Gas ||OHV||2-bbl carb. Chevrolet 90° V6 (Chevy Small-Block V8 Derived). 229 cu. in. &lt;br /&gt; '81-'82 Chevy El Camino, GMC Caballero (49-state emissions)
|-
| K ||L05|| 5.7L || V8 || Gas ||OHV|| TBI. Gen I Chevrolet Small-Block V8. '87 R/V pickups, '88-'95 C/K, Sierra pickups, '87-'95 full-size vans, '96 G-Classic full-size vans, '87-'94 Blazer, '95 Tahoe, '87-'91 Jimmy, '92-'95 Yukon, '87-'95 Suburban. 
|-
| K ||LY6|| 6.0L || V8 || Gas ||OHV||SFI. Gen IV Chevrolet Small-Block V8. Iron Block &amp; Aluminum Heads. VVT.&lt;br /&gt; '07-'09 Silverado HD/Sierra HD, '07-'09 Suburban 2500/Yukon XL 2500, '08-'09 Express/Savana
|-
| K ||LEA|| 2.4L || I4 || Gas/E85 ||DOHC,&lt;br /&gt; 16 valve||Flex Fuel. GM Ecotec engine, Gen II. Direct Injection. VVT. Chevy Equinox, GMC Terrain '12-'17,&lt;br /&gt; Chevy Captiva Sport '12-'14, Chevy Orlando '14. 
|-
| K ||L3B|| 2.7L ||I4 Turbo||| Gas ||DOHC,&lt;br /&gt; 16 valve||GM L3B Tripower engine (&quot;TurboMax&quot;). Direct Injection. VVT, VVL. Active Fuel Management.&lt;br /&gt; '19+ Chevy Silverado 1500, GMC Sierra 1500, '23+ Chevy Colorado, GMC Canyon.
|-
| L ||LS9|| 5.7L || V8 || Gas ||OHV|| 4-bbl carb. Gen I Chevrolet Small-Block V8. For sub-8,500 lb. GVWR trucks, vans, Suburban, Blazer/Jimmy (CA) '81-'86.
|-
| L ||L27|| 3.8L || V6 || Gas ||OHV||Buick V6 (3800 Series I). '92-'95 U-body minivans
|-
| L ||LX9|| 3.5L || V6 || Gas ||OHV||GM High Value 60° V6. 3498cc. SFI. '05-'06 GMT201 minivans, '06-'07 Buick Rendezvous
|-
| L ||LH8|| 5.3L || V8 || Gas ||OHV||SFI. Gen IV Chevrolet Small-Block V8. Aluminum Block &amp; Heads.&lt;br /&gt; '08-'09 Hummer H3 Alpha, '09 Colorado/Canyon, Hummer H3T Alpha
|-
| L ||LGH|| 6.6L || V8 Turbo || Diesel ||OHV,&lt;br /&gt; 32 valve||Duramax 6600 V8 engine. Mid '10-'16 Express/Savana, '11-'12 Silverado HD/Sierra HD chassis cabs
|-
| L ||L87|| 6.2L || V8 || Gas ||OHV||Gen V Chevrolet Small-Block V8 (EcoTec3). Direct injection, VVT. Dynamic Fuel Management.&lt;br /&gt; '19+ Chevy/GMC Silverado 1500/Sierra 1500, '21+ Tahoe/Yukon, Suburban/Yukon XL,&lt;br /&gt; Cadillac Escalade/Escalade ESV.
|-
| L ||L3T|| 1.3L || I3 Turbo || Gas ||DOHC,&lt;br /&gt; 12 valve||GM E-Turbo Engine. Direct Injection. VVT. '20+ Buick Encore GX, '21+ Chevy Trailblazer.
|-
| M ||LT9|| 5.7L || V8 || Gas ||OHV|| 4-bbl carb. Gen I Chevy Small-Block V8.&lt;br /&gt; For over-8,500 lb. GVWR C/K trucks, full-size vans, Suburban '81-'86, full-size van cutaway '81-'88.&lt;br /&gt; '88 Chevy/GMC R30/3500 Chassis Cab w/C7C (10,500 lb. GVWR),&lt;br /&gt; V30/3500 Chassis Cab w/C7E (11,000 lb. GVWR)
|-
| M ||L30|| 5.0L || V8 || Gas ||OHV||Gen 1+ Chevrolet Small-Block V8. Vortec 5000. CPI.&lt;br /&gt; '96-'99 Chevy C/K, GMC Sierra, '96-'02 Express/Savana
|-
| M ||LNF|| 2.0L || I4 Turbo || Gas ||DOHC,&lt;br /&gt; 16 valve||GM Ecotec engine, Gen II. Direct Injection. VVT. 2010 Chevy HHR SS. 
|-
| M ||LH6|| 5.3L || V8 || Gas ||OHV||SFI. Gen IV Chevrolet Small-Block V8. Active Fuel Management. Aluminum Block &amp; Heads.&lt;br /&gt; '05-'06 GMT370 SUVs (Trailblazer EXT/Envoy XL/Isuzu Ascender 7-psgr.), '05-'07 Buick Rainier,&lt;br /&gt; '05-'09 GMC Envoy Denali, Saab 9-7X, '06-'08 Chevy Trailblazer, '05 GMC Envoy XUV,&lt;br /&gt; '07-'09 Silverado/Sierra 1500
|-
| M ||LAF|| 2.4L || I4 || Gas ||DOHC,&lt;br /&gt; 16 valve||GM Ecotec engine, Gen II. Direct Injection. VVT. Chevy Orlando '12. 
|-
| M ||LE2|| 1.4L || I4 Turbo || Gas ||DOHC,&lt;br /&gt; 16 valve||GM Small Gasoline Engine. Direct Injection. VVT. '16-'19 &amp; '21-'22 Buick Encore, '21-'22 Chevy Trax.
|-
| N ||L10|| 1.8L || I4 || Gas ||SOHC,&lt;br /&gt; 8 valve||2-bbl carb. Isuzu G180Z engine imported from Japan. '81-'82 Chevy LUV
|-
| N ||LF9|| 5.7L || V8 || Diesel ||OHV||Oldsmobile Diesel V8. '83-'84 Chevy El Camino/GMC Caballero.
|-
| N ||LB1|| 4.3L || V6 || Gas ||OHV|| 4-bbl carb. Chevrolet 90° V6 (Chevy Small-Block V8 Derived).&lt;br /&gt; '85 Astro/Safari, '85-'86 C/K pickups &amp; full-size vans
|-
| N ||L19|| 7.4L || V8 || Gas ||OHV|| Mark IV Chevrolet Big-Block V8. TBI.&lt;br /&gt; '87-'90 R/V pickups, Suburban 2500, '88-'90 C/K, Sierra pickups, full-size vans
|-
| N ||L19|| 7.4L || V8 || Gas ||OHV|| Gen V Chevrolet Big-Block V8. TBI.&lt;br /&gt; '91 R/V pickups, '91-'95 C/K, Sierra pickups, Suburban 2500, full-size vans. '96 G-Classic full-size vans
|-
| N ||LZ4|| 3.5L || V6 || Gas ||OHV||GM High Value 60° V6. 3510cc. SFI. VVT. '08-'09 Saturn Vue
|-
| N ||LQ9|| 6.0L || V8 || Gas ||OHV|| Gen III Chevrolet Small-Block V8. Vortec 6000 H.O. or VortecMAX. Iron Block/Aluminum Heads.&lt;br /&gt; 345 hp. '02-'06 Cadillac Escalade, '03-'06 Cadillac Escalade ESV, '03-'06 Chevy Silverado SS,&lt;br /&gt; '05-'06 GMC Sierra Denali, '07 GMC Sierra Classic Denali.
|-
| N ||LGZ|| 3.6L || V6 || Gas ||DOHC,&lt;br /&gt; 24 valve||GM High Feature V6, 4th gen. Direct Injection. VVT. Active Fuel Management.&lt;br /&gt; '17-'22 Chevy Colorado, GMC Canyon.
|-
| P ||L49|| 6.5L || V8 || Diesel ||OHV||Detroit Diesel V8. For sub-8,500 lb. GVWR Chevy C/K, GMC Sierra trucks &amp; full-size vans '94-'95
|-
| P ||LM4|| 5.3L || V8 || Gas ||OHV||Gen III Chevrolet Small-Block V8. Vortec 5300. 290hp. Aluminum Block &amp; Heads.&lt;br /&gt; '03-'04 Chevy SSR, '03-'04 GMT370 SUVs (Trailblazer EXT/Envoy XL/Isuzu Ascender 7-psgr.),&lt;br /&gt; '04 Buick Rainier, GMC Envoy XUV
|-
| P ||LE5|| 2.4L || I4 || Gas ||DOHC,&lt;br /&gt; 16 valve||MFI. GM Ecotec Gen II. VVT. '06-'08 Chevy HHR, '08-'09 Saturn Vue 
|-
| P ||LH9|| 5.3L || V8 || Gas/E85  ||OHV||Flex Fuel. SFI. Gen IV Chevrolet Small-Block V8. Aluminum Block &amp; Heads. VVT.&lt;br /&gt; '10-'12 Colorado/Canyon, '10 Hummer H3 Alpha, H3T Alpha 
|-
| P ||LV1|| 4.3L || V6 || Gas ||OHV||Chevrolet 90° V6 - Gen V Chevrolet Small-Block V6 (EcoTec3). Direct injection, VVT.&lt;br /&gt; '18+ Chevy Express/GMC Savana.
|-
| P ||LBP|| 1.2L || I3 Turbo || Gas/E85 ||DOHC,&lt;br /&gt; 12 valve||Flex Fuel. GM E-Turbo Engine. Direct Injection. VVT.&lt;br /&gt; '25+ Buick Encore GX, Chevy Trailblazer, '25- Chevy Trax, Buick Envista.
|-
| R ||LL2|| 2.8L || V6 || Gas ||OHV||TBI. Chevrolet 60° V6. '86-'93 Chevy S-10, GMC S-15/Sonoma,&lt;br /&gt; '86-'89 Chevy S-10 Blazer/GMC S-15 Jimmy
|-
| R ||L31|| 5.7L || V8 || Gas ||OHV||Gen 1+ Chevrolet Small-Block V8. Vortec 5700. CPI.&lt;br /&gt; '96-'99 Chevy C/K, GMC Sierra, '96-'99 Chevy  Tahoe/GMC Yukon, Chevy/GMC Suburban, '99-'00 GMC Yukon Denali, Cadillac Escalade, '00 Chevy Tahoe Limited/Z71, '96-'02 Chevy Express/GMC Savana.
|-
| R ||L8B|| 5.3L || V8 || Gas ||OHV||Mild Hybrid. Gen V Chevrolet Small-Block V8 (EcoTec3). Direct injection, VVT. Active Fuel Management. '16-'18 Chevy Silverado 1500, GMC Sierra 1500. 
|-
| S ||LQ7|| 2.2L || I4 || Diesel ||OHV||Isuzu C220 engine imported from Japan. '81-'82 Chevy LUV, '84-'85 Chevy S-10/GMC S-15
|-
| S ||L56|| 6.5L || V8 Turbo || Diesel ||OHV||Detroit Diesel V8. For sub-8,500 lb. GVWR Chevy C/K, GMC Sierra trucks '94-'99,&lt;br /&gt; Chevy Blazer '94, Chevy Tahoe 2-d '95-'99, GMC Yukon 2-d '94-'97
|-
| S ||LL8|| 4.2L || I6 || Gas ||DOHC,&lt;br /&gt; 24 valve||Atlas I6. SFI. VVT. '02-'09 GMT360/370 SUVs (Chevy Trailblazer, GMC Envoy, Oldsmobile Bravada, Buick Rainier, Isuzu Ascender, Saab 9-7X)
|-
| S ||LGX|| 3.6L || V6 || Gas ||DOHC,&lt;br /&gt; 24 valve||GM High Feature V6, 4th gen. Direct Injection. VVT. Active Fuel Management.&lt;br /&gt; '17+ Cadillac XT5, '17-'23 GMC Acadia, '19+ Chevrolet Blazer, '20-'25 Cadillac XT6.
|-
| S ||LK0|| 2.5L || I4 Turbo || Gas ||DOHC,&lt;br /&gt; 16 valve||L3B engine family. Direct Injection. VVT. '24- Chevy Traverse, GMC Acadia, '25- Buick Enclave
|-
| T ||L25|| 4.8L || I6 || Gas ||OHV||1-bbl carb. Chevrolet Turbo-Thrift I6. '81-'86 Chevy/GMC C/K pickups, '88 R/V pickups
|-
| T ||LM7|| 5.3L || V8 || Gas ||OHV|| Gen III Chevrolet Small-Block V8. Iron Block &amp; Aluminum Heads. Vortec 5300. 270/285/295hp.&lt;br /&gt; '99-'07 GMT800 pickups &amp; SUVs including '02-'05 Escalade 2wd, '07 Silverado Classic 1500/&lt;br&gt; Sierra Classic 1500, '03-'07 Express/Savana
|-
| T ||LEA|| 2.4L || I4 || Gas/E85 ||DOHC,&lt;br /&gt; 16 valve||Flex Fuel. GM Ecotec engine, Gen II. Direct Injection. VVT. Chevy Orlando '13. 
|-
| T ||LM2|| 3.0L || I6 Turbo|| Diesel ||DOHC,&lt;br /&gt; 24 valve|| Duramax Diesel I6. Aluminum Block &amp; Heads. '20-'22 Silverado/Sierra 1500, '21-'24 Tahoe/Suburban, Yukon/Yukon XL, Escalade/Escalade ESV.
|-
| U ||LS5|| 1.6L || I4 || Gas ||SOHC,&lt;br /&gt; 8 valve||Suzuki G16A engine. TBI. '89-'95 Geo Tracker
|-
| U ||LQ4|| 6.0L || V8 || Gas ||OHV|| Gen III Chevrolet Small-Block V8. Iron Block &amp; Aluminum Heads (Iron Heads in '99-'00).&lt;br /&gt; '99-'06 GMT800 pickups, '07 Silverado Classic 1500HD/Sierra Classic 1500HD,&lt;br&gt; '00-'06 Suburban/Yukon XL 2500, '01-'06 Yukon Denali/Yukon XL Denali,&lt;br&gt; '06 Suburban LTZ, '03-'07 Express/Savana, '03-'07 Hummer H2.
|-
| U ||LE9|| 2.4L || I4 || Gas/E85 ||DOHC,&lt;br /&gt; 16 valve||Flex-Fuel. GM Ecotec Gen II. 2011 Chevy HHR 
|-
| U ||LH7|| 1.6L ||I4 Turbo|| Diesel ||DOHC,&lt;br /&gt; 16 valve||GM Medium Diesel engine (&quot;Whisper Diesel&quot;). Made by Opel in Szentgotthárd, Hungary.&lt;br /&gt; Aluminum Block &amp; Heads. '18-'19 Chevy Equinox &amp; GMC Terrain Diesel.
|-
| V ||LR4|| 4.8L || V8 || Gas ||OHV||Gen III Chevrolet Small-Block V8. Iron Block/Aluminum Heads.&lt;br&gt; '99-'06 GMT800 pickups, '07 Silverado Classic 1500/Sierra Classic 1500,&lt;br /&gt; '00-'06 Tahoe/Yukon, '03-'07 Express/Savana
|-
| V ||LE9|| 2.4L || I4 || Gas/E85 ||DOHC,&lt;br /&gt; 16 valve||Flex-Fuel. GM Ecotec Gen II. 2009-2010 Chevy HHR
|-
| V ||LYX|| 1.5L || I4 Turbo || Gas ||DOHC,&lt;br /&gt; 16 valve||GM Small Gasoline Engine. Direct Injection. VVT. '18-'22 Chevy Equinox, GMC Terrain
|-
| W ||LE8|| 7.4L || V8 || Gas ||OHV|| Mark IV Chevrolet Big-Block V8. 4bbl carb. '81-'86 Chevy/GMC C/K pickups, Suburban.&lt;br /&gt; '88-'89 Chevy/GMC R30/3500 Chassis Cab w/C7C (10,500 lb. GVWR),&lt;br /&gt; V30/3500 Chassis Cab w/C7E (11,000 lb. GVWR)
|-
| W ||L35|| 4.3L || V6 || Gas ||OHV|| CPI. Vortec 4300 H.O. Chevrolet 90° V6 (Chevy Small-Block V8 Derived).&lt;br /&gt; '92-'95 Sonoma, S-10 Blazer/Jimmy, Astro/Safari, '94-'95 S-10, '92-'94 Oldsmobile Bravada
|-
| W ||L35|| 4.3L || V6 || Gas ||OHV|| SFI. Vortec 4300 H.O. Chevrolet 90° V6 (Chevy Small-Block V8 Derived). '96-'02 S-10/Sonoma, Blazer/Jimmy, Express/Savana, C/K, Silverado, Sierra, '96-'01 Bravada, Astro/Safari, '00 Isuzu Hombre
|-
| W ||LGD|| 3.9L || V6 || Gas/E85 ||OHV||Flex Fuel. GM High Value 60° V6. SFI. VVT. '07-'09 GMT201 minivans
|-
| W ||LAF|| 2.4L || I4 || Gas ||DOHC,&lt;br /&gt; 16 valve||GM Ecotec engine, Gen II. Direct Injection. VVT. Chevy Equinox, GMC Terrain '10. 
|-
| W ||LE8|| 2.2L || I4 || Gas/E85 ||DOHC,&lt;br /&gt; 16 valve||Flex-Fuel. SFI. GM Ecotec Gen II. VVT. 2011 Chevy HHR.
|-
| W ||LFY|| 3.6L || V6 || Gas ||DOHC,&lt;br /&gt; 24 valve||GM High Feature V6. Direct Injection.&lt;br&gt; '18-'23 Chevrolet Traverse, '24 Chevrolet Traverse Limited, '18-'24 Buick Enclave.
|-
| X ||LF6|| 4.3L || V6 || Gas ||OHV||SFI. Vortec 4300. Chevrolet 90° V6 (Chevy Small-Block V8 Derived).&lt;br /&gt; '96-'99 S-10/Sonoma, '97-'99 Isuzu Hombre. 
|-
| X ||LU3|| 4.3L || V6 || Gas ||OHV||Vortec 4300. Chevrolet 90° V6 (Chevy Small-Block V8 Derived). '03-'04 S-10/Sonoma,&lt;br /&gt; '03-'05 Blazer/Jimmy, '02-'05 Astro/Safari, '03-'14 Express/Savana, '03-'13 Silverado/Sierra,&lt;br&gt; '07 Silverado Classic 1500/Sierra Classic 1500
|-
| X ||LNF|| 2.0L || I4 Turbo || Gas ||DOHC,&lt;br /&gt; 16 valve||GM Ecotec engine, Gen II. Direct Injection. VVT. '08-'09 Chevy HHR SS. 
|-
| X ||LTG|| 2.0L || I4 Turbo || Gas ||DOHC,&lt;br /&gt; 16 valve||GM Ecotec engine, Gen III. Direct Injection. VVT.&lt;br /&gt; '16-'20 Buick Envision, '18-'20 Chevy Equinox, GMC Terrain, '18-'19 Chevy Traverse RS
|-
| Y ||LQ2|| 2.0L || I4 || Gas ||OHV||2-bbl carb. Chevrolet &quot;122&quot; engine.&lt;br /&gt; '83-'84 Chevy S-10/GMC S-15, '83-'84 Chevy S-10 Blazer/GMC S-15 Jimmy
|-
| Y ||L57|| 6.5L || V8 || Diesel ||OHV||Detroit Diesel V8. For over-8,500 lb. GVWR full-size vans '94-'95 &amp; '96 G-Classic full-size vans
|-
| Y ||L76|| 6.0L || V8 || Gas ||OHV||SFI. Gen IV Chevy Small-Block V8. Aluminum Block &amp; Heads. VVT. With Active Fuel Management.&lt;br /&gt; '07-'09 Silverado/Sierra, Suburban/Yukon XL, Chevy Avalanche
|-
| Y ||LF1|| 3.0L || V6 || Gas ||DOHC,&lt;br /&gt; 24 valve||GM High Feature V6. Direct Injection. VVT.&lt;br /&gt; '10-'11 Cadillac SRX, '11 Saab 9-4X, '10 Chevy Equinox, GMC Terrain 
|-
| Y ||L5P|| 6.6L || V8 Turbo || Diesel ||OHV,&lt;br /&gt; 32 valve||Duramax 6600 V8 engine. '17+ Silverado HD/Sierra HD. Engine updated in '24. 
|-
| Z ||LF9|| 5.7L || V8 || Diesel ||OHV||Oldsmobile Diesel V8. '81 Chevy C10/GMC C1500 full-size pickups.
|-
| Z ||LB4|| 4.3L || V6 || Gas ||OHV|| TBI. Chevrolet 90° V6 (Chevy Small-Block V8 Derived). '85-'87 Chevy El Camino/GMC Caballero,&lt;br /&gt; '86-'94 Astro/Safari, '87 R/V pickups, '88-'95 C/K &amp; Sierra pickups, '87-'95 full-size vans &amp; &lt;br /&gt; '96 G-Classic full-size vans, '88-'95 S-10, S-15/Sonoma, '88-'94 S-10 Blazer, S-15 Jimmy,&lt;br /&gt; '91-'92 Oldsmobile Bravada
|-
| Z ||LB4|| 4.3L || V6 Turbo || Gas ||OHV|| MPI. For GMC Syclone &amp; Typhoon. Chevrolet 90° V6 (Chevy Small-Block V8 Derived)
|-
| Z ||L59|| 5.3L || V8 || Gas/E85 ||OHV||Flex Fuel. Gen III Chevrolet Small-Block V8. Iron Block &amp; Aluminum Heads. Vortec 5300. 285/295hp.&lt;br /&gt; '02-'07 GMT800 pickups, '07 Silverado Classic 1500/Sierra Classic 1500,&lt;br&gt; '02-'06 Suburban/Yukon XL, Avalanche.
|-
| Z ||LAT|| 2.4L || I4 || Gas ||DOHC,&lt;br /&gt; 16 valve||Mild Hybrid. MFI. GM Ecotec Gen II. VVT. '07-'09 Saturn Vue Green Line
|-
| 1 ||LZ9|| 3.9L || V6 || Gas ||OHV||GM High Value 60° V6. SFI. VVT. '06-'09 GMT201 minivans
|-
| 1 ||LE5|| 2.4L || I4 || Gas ||DOHC,&lt;br /&gt; 16 valve||MFI. GM Ecotec Gen II. VVT. '10 Saturn Vue.
|-
| 1 ||LB7|| 6.6L || V8 Turbo || Diesel ||OHV,&lt;br /&gt; 32 valve||Duramax 6600 V8 engine. First version of the Duramax V8. '01-Mid '04 Silverado HD/Sierra HD
|-
| 1 ||LWN|| 2.8L || I4 Turbo || Diesel ||DOHC,&lt;br /&gt; 16 valve||Based on VM Motori A428 engine. Made by GM Powertrain Thailand 2016-2020. Made in Brazil for '22. '16-'22 Colorado/Canyon, '17-'22 Express/Savana.
|-
| 2 ||LLY|| 6.6L || V8 Turbo || Diesel ||OHV,&lt;br /&gt; 32 valve||Duramax 6600 V8 engine. Mid '04-Mid '06 Silverado HD/Sierra HD, '06-Mid '07 Express/Savana
|-
| 2 ||L9H|| 6.2L || V8 || Gas/E85 ||OHV||Flex-Fuel. Gen IV Chevrolet Small-Block V8. Aluminum Block &amp; Heads. SFI. VVT.&lt;br /&gt; '09-'13 Chevy Silverado 1500, GMC Sierra 1500, Sierra Denali 1500,&lt;br /&gt; '09 Chevy Tahoe LTZ, GMC Yukon Denali/Yukon XL Denali, Cadillac Escalade/Escalade ESV,&lt;br&gt; Hummer H2
|-
| 2 ||LIH|| 1.2L || I3 Turbo || Gas ||DOHC,&lt;br /&gt; 12 valve||GM E-Turbo Engine. Direct Injection. VVT.&lt;br /&gt; '20-'24 Buick Encore GX, '21-'24 Chevy Trailblazer, '24 Chevy Trax, Buick Envista,&lt;br&gt; '25 Chevy Trax, Buick Envista (Canada only).
|-
| 3 ||LC9|| 5.3L || V8 || Gas/E85 ||OHV||Flex Fuel. SFI. Gen IV Chevrolet Small-Block V8. Active Fuel Management. VVT added for '10. Aluminum Block &amp; Heads.&lt;br /&gt; '07-'11 Silverado/Sierra 1500, Tahoe/Yukon, Suburban/Yukon XL 1500, '07-'09 &amp; '11 Avalanche
|-
| 3 ||LFX|| 3.6L || V6 || Gas ||DOHC,&lt;br /&gt; 24 valve||GM High Feature V6. Direct Injection. VVT. E85 Flex Fuel.&lt;br /&gt; '12-'16 Cadillac SRX, '13-'17 Chevrolet Equinox, GMC Terrain, '15-'16 Colorado/Canyon
|-
| 4 ||LN2|| 2.2L || I4 || Gas ||OHV||MFI (94-95). SFI (96-00). Chevrolet &quot;122&quot; engine. '94-'00 S-10/Sonoma, '96-'00 Isuzu Hombre
|-
| 4 ||LE8|| 2.5L || V6 || Gas ||DOHC,&lt;br /&gt; 24 valve||Suzuki H25A engine. MFI. '01-'04 Chevrolet Tracker
|-
| 4 ||L66|| 3.5L || V6 || Gas ||SOHC,&lt;br /&gt; 24 valve||Honda J35S1 V6. VTEC. '04-'07 Saturn Vue
|-
| 4 ||LMF|| 5.3L || V8 || Gas/E85  ||OHV||Flex Fuel. SFI. Gen IV Chevrolet Small-Block V8. Iron Block &amp; Aluminum Heads. VVT.&lt;br /&gt; '08-'14 Express/Savana 1500
|-
| 4 ||LAU|| 2.8L || V6 Turbo || Gas ||DOHC,&lt;br /&gt; 24 valve||GM High Feature V6. SFI. '10 Cadillac SRX
|-
| 4 ||LSY|| 2.0L || I4 Turbo || Gas ||DOHC,&lt;br /&gt; 16 valve||GM Ecotec engine, Gen III. Direct Injection. Active Fuel Management. VVT. VVL.&lt;br /&gt; '19-'25 Cadillac XT4, '20+ Chevy Blazer, Cadillac XT5, '20-'23 GMC Acadia,&lt;br /&gt; '21+ Buick Envision, '21-'25 Cadillac XT6
|-
| 5 ||L43|| 2.2L || I4 || Gas/E85 ||OHV||Flex-Fuel. SFI. Chevrolet &quot;122&quot; engine. '00-'02 S-10/Sonoma, '00 Isuzu Hombre
|-
| 5 ||LFA|| 6.0L || V8 || Gas-Electric Hybrid ||OHV||2-Mode Hybrid. Gen IV Chevrolet Small-Block V8. Aluminum Block &amp; Heads. VVT. Active Fuel Management. '08-'09 Tahoe Hybrid/Yukon Hybrid, '09 Escalade Hybrid, Silverado Hybrid/Sierra Hybrid
|-
| 5 ||LFW|| 3.0L || V6 || Gas/E85 ||DOHC,&lt;br /&gt; 24 valve||Flex-Fuel. GM High Feature V6. Direct Injection. VVT. '11-'12 Chevy Equinox, GMC Terrain,&lt;br /&gt; '12 Chevy Captiva Sport
|-
| 6 ||L01|| 1.6L || I4 || Gas ||SOHC,&lt;br /&gt; 16 valve||Suzuki G16B engine. MFI. '94-'97 Geo Tracker, '98-'00 Chevrolet Tracker
|-
| 6 ||L52|| 3.5L || I5 || Gas ||DOHC,&lt;br /&gt; 20 valve||Atlas I5. SFI. VVT. '04-'06 Colorado/Canyon, '06 Isuzu i-350, '06 Hummer H3
|-
| 6 ||LAU|| 2.8L || V6 Turbo || Gas ||DOHC,&lt;br /&gt; 24 valve||GM High Feature V6. SFI. '11 Cadillac SRX, Saab 9-4X
|-
| 6 ||LMM|| 6.6L || V8 Turbo || Diesel ||OHV,&lt;br /&gt; 32 valve||Duramax 6600 V8 engine. '07-'10 Silverado HD/Sierra HD (GMT900), Mid '07-Mid '10 Express/Savana
|-
| 7 ||LY7|| 3.6L || V6 || Gas ||DOHC,&lt;br /&gt; 24 valve||GM High Feature V6. '04-'06 Buick Rendezvous, '04-'09 Cadillac SRX,&lt;br /&gt; '07-'08 GMC Acadia, Saturn Outlook, '08 Buick Enclave, '08-'10 Saturn Vue
|-
| 7 ||LC9|| 5.3L || V8 || Gas/E85 ||OHV||Flex Fuel. SFI. Gen IV Chevrolet Small-Block V8. Active Fuel Management. VVT.&lt;br /&gt; Aluminum Block &amp; Heads.&lt;br /&gt; '12-'13 Silverado/Sierra 1500, Avalanche, '12-'14 Tahoe/Yukon, Suburban/Yukon XL 1500
|-
| 7 ||L8T|| 6.6L || V8 || Gas ||OHV||Gen V Chevrolet Small-Block V8. Iron Block/Aluminum Heads. Direct injection, VVT.&lt;br /&gt; '20+ Silverado HD/Sierra HD, '21+ Express/Savana
|-
| 8 ||LK5|| 2.8L || I4 || Gas ||DOHC,&lt;br /&gt; 16 valve||Atlas I4. SFI. VVT. '04-'06 Colorado/Canyon, '06 Isuzu i-280.
|-
| 8 ||L92|| 6.2L || V8 || Gas ||OHV||Gen IV Chevrolet Small-Block V8. Aluminum Block &amp; Heads. SFI. VVT.&lt;br /&gt; '07-'08 GMC Sierra Denali, Yukon Denali/Yukon XL Denali, Cadillac Escalade/Escalade ESV,&lt;br&gt; '08 Chevy Tahoe LTZ, Hummer H2.
|-
| 8 ||LML|| 6.6L || V8 Turbo || Diesel ||OHV,&lt;br /&gt; 32 valve||Duramax 6600 V8 engine.&lt;br /&gt; '11-'16 Silverado HD/Sierra HD pickups, '13-'16 Silverado HD/Sierra HD chassis cabs.
|-
| 8 ||LZ0|| 3.0L || I6 Turbo|| Diesel ||DOHC,&lt;br /&gt; 24 valve|| Duramax Diesel I6. Aluminum Block &amp; Heads.&lt;br&gt; '23+ Silverado/Sierra 1500, '24+ Suburban HD, '25+ Tahoe/Suburban, Yukon/Yukon XL.
|-
| 9 ||LC3|| 3.8L || V6 || Gas ||OHV||2-bbl carb. Chevrolet 90° V6 (Chevy Small-Block V8 Derived). 229 cu. in. &lt;br /&gt; '83-'84 Chevy El Camino, GMC Caballero (49-state emissions).
|-
| 9 ||LLV|| 2.9L || I4 || Gas ||DOHC,&lt;br /&gt; 16 valve||Atlas I4. SFI. VVT. '07-'12 Colorado/Canyon, '07-'08 Isuzu i-290.
|-
| 9 ||LT4|| 6.2L ||V8 Supercharged|| Gas ||OHV||Gen V Chevy Small-Block V8. Aluminum Block &amp; Heads. Direct injection. VVT. Active Fuel Management. '23+ Cadillac Escalade/Escalade ESV V-Series.
|-
| 0 ||LMG|| 5.3L || V8 || Gas/E85 ||OHV||Flex-Fuel. SFI. Gen IV Chevrolet Small-Block V8. Active Fuel Management. VVT added for '10.&lt;br /&gt; Iron Block &amp; Aluminum Heads.&lt;br /&gt; '07-'13 Silverado/Sierra 1500, Avalanche, '07-'14 Tahoe/Yukon, Suburban/Yukon XL 1500.
|}
H.O.=High Output, VVT=Variable Valve Timing, VVL=Variable Valve Lift, GVWR=Gross Vehicle Weight Rating, CNG=Compressed Natural Gas, LPG=Liquefied Petroleum Gas (Propane Autogas)

====Motor codes for electric light trucks====

{| class=&quot;wikitable&quot;
|-
! VIN !! RPO !! Fuel !! Drive Wheels !! Application/Notes
|-
| H ||LN1|| Electricity || Front || '97-'98 Chevrolet S-10 Electric.
|-
|}

====Motor codes for Ultium-powered electric light trucks====

{| class=&quot;wikitable&quot;
|-
! VIN !! Motor &lt;br /&gt; RPO code !! # of Motors !! Battery Module &lt;br /&gt; RPO code !! # of Modules !! Fuel !! Drive Wheels !! Application/Notes
|-
| A ||XRL|| 3 || ETN || 24 || Electricity || All || '22- GMC Hummer EV pickup 3X
|-
| B ||XRL|| 3 || ETI || 20 || Electricity || All || '24- GMC Hummer EV pickup 3X
|-
| C ||XRL|| 3 || ETJ || 20 || Electricity || All || '24- GMC Hummer EV SUV 3X
|-
| D ||XRJ|| 2 || ETI || 20 || Electricity || All || '24 Chevrolet Silverado EV 3WT, '25- Silverado EV 5WT, 3LT,&lt;br&gt; '25 Silverado EV RST (2SP), '26- Silverado EV Trail Boss (2TR),&lt;br&gt; '24- GMC Hummer EV pickup 2X, '25- GMC Sierra EV Denali 5SC,&lt;br&gt; '26- Sierra EV Elevation 3SC, AT4 4SC
|-
| E ||XRJ|| 2 || ETJ || 20 || Electricity || All || '24- GMC Hummer EV SUV 2X
|-
| G ||XRJ|| 2 || ETJ || 20 || Electricity || All || '23 BrightDrop Zevo 600
|-
| H ||XRJ|| 2 || EWX || 14 || Electricity || All ||'26- Chevrolet Silverado EV 4WT, 2LT,&lt;br&gt; '26- GMC Sierra EV Elevation 3SB, Denali 5SB
|-
| J ||X0C|| 2 || EC5 || 10 || Electricity || All || '24 Chevy Blazer EV 2LT, 1RS AWD,&lt;br&gt; '25- Chevy Blazer EV 4LT, 3RS AWD, '24-'26 Honda Prologue AWD
|-
| K ||X0D|| 1 || EC6 || 12 || Electricity || Rear || '23- Cadillac Lyriq RWD, '24-'25 Chevrolet Blazer EV 2RS RWD,&lt;br&gt; '24 Acura ZDX A-Spec RWD
|-
| L ||X0E|| 2 || EC6 || 12 || Electricity || All || '23- Cadillac Lyriq AWD, '24- Chevrolet Blazer EV PPV AWD,&lt;br&gt; '25- Chevrolet Blazer EV SS AWD, '26- Cadillac Vistiq AWD,&lt;br&gt; '24 Acura ZDX A-Spec, Type S AWD
|-
| L ||XRJ|| 2 || ETN || 24 || Electricity || All || '24 Chevrolet Silverado EV 4WT, RST (3SP), '25- Silverado EV 8WT,&lt;br&gt; '25 Silverado EV RST (3SP), '26- Silverado EV 4LT, Trail Boss (3TR),&lt;br&gt; '24- GMC Sierra EV Denali 5SD, '26- Sierra EV AT4 4SD,&lt;br&gt; '25- Cadillac Escalade IQ, '26- Cadillac Escalade IQL
|-
| M ||X0B|| 1 || EC5 || 10 || Electricity || Front || '24-'26 Honda Prologue FWD, '25- Chevy Blazer EV 2LT, 1RS FWD
|-
| P ||X0B|| 1 || EC3 || 10 || Electricity || Front || '24- Chevrolet Equinox EV FWD
|-
| R ||X0C|| 2 || EC3 || 10 || Electricity || All || '24- Chevrolet Equinox EV AWD, '25 Cadillac Optiq AWD
|-
| Y ||XRJ|| 2 || ETC || 12 || Electricity || All || '24 BrightDrop Zevo 400, Zevo 600,&lt;br&gt; '25-'26 Chevrolet BrightDrop 400/600 AWD
|-
| Z ||XRJ|| 2 || ETJ || 20 || Electricity || All || '24 BrightDrop Zevo 400, Zevo 600,&lt;br&gt; '25-'26 Chevrolet BrightDrop 400/600 AWD
|-
| 4 ||X0E|| 2 || EC3 || 10 || Electricity || All || '26- Cadillac Optiq AWD
|-
| 5 ||X0D|| 1 || EC3 || 10 || Electricity || Rear|| '26- Cadillac Optiq RWD
|-
| 6 ||XRM|| 1 || ETC || 12 || Electricity || Front || '25-'26 Chevrolet BrightDrop 400/600 FWD
|-
| 7 ||XRJ|| 2 || EWU || 14 || Electricity || All || '26 Chevrolet BrightDrop 600 AWD
|}
SB=Standard Range, SC=Extended Range, SD=Max Range

====Engine codes for medium duty trucks 2016-====
GM encodes the engine type in character 8 of the VIN. The following table outlines the various engines encoded there:

{| class=&quot;wikitable&quot;
|-
! VIN !! RPO !! Size !! Type !! Fuel !! Valvetrain !! Engine Family/Notes/Applications
|-
| B ||L96|| 6.0L || V8 || Gas ||OHV||SFI. Gen IV Chevrolet Small-Block V8. Iron Block &amp; Aluminum Heads. VVT.&lt;br /&gt; '16-'20 Chevy LCF 3500/4500.
|-
| C ||LC8|| 6.0L || V8 || Gas/CNG or&lt;br&gt;Gas/LPG ||OHV||Bi-Fuel. SFI. Gen IV Chevrolet Small-Block V8. Iron Block &amp; Aluminum Heads. VVT.&lt;br /&gt; '16-'20 Chevy LCF 3500/4500.
|-
| D ||L8T|| 6.6L || V8 || Gas ||OHV||Gen V Chevrolet Small-Block V8. Iron Block/Aluminum Heads. Direct injection, VVT.&lt;br /&gt; '21-'23 Chevy LCF 3500/4500, '24- Chevy LCF 3500HG/4500HG/5500HG/5500XG.
|-
| F ||LCB|| 6.7L || I6 Turbo || Diesel ||OHV,&lt;br /&gt; 32 valve||Cummins B Series ISB engine. '22- Chevy LCF 6500XD, '23- Chevy LCF 7500XD.
|-
| 6 ||I1B|| 5.2L || I4 Turbo || Diesel ||SOHC,&lt;br /&gt; 16 valve||Isuzu 4HK1-TC engine. '17- Chevy LCF 4500HD/XD, 5500XD, '17-'24 Chevy LCF 5500HD,&lt;br /&gt; '18-'21 Chevy LCF 6500XD.
|-
| 7 ||IZ3|| 3.0L || I4 Turbo || Diesel ||DOHC,&lt;br /&gt; 16 valve||Isuzu 4JJ1-TC engine. '16-'18 Chevy LCF 3500HD.
|-
|}

====Engine codes for AM General-built Hummer H1 2000-2006====
AM General encodes the engine type in character 4 of the VIN.

{| class=&quot;wikitable&quot;
|-
! VIN !! RPO !! Size !! Type !! Fuel !! Valvetrain !! Engine Family/Notes
|-
| F || || 6.5L || V8 Turbo || Diesel ||OHV||Detroit Diesel V8 built by GEP (General Engine Products), a subsidiary of AM General.&lt;br&gt; '01-'04 Hummer H1 &amp; '06 H1 Fleet models.
|-
| P ||LLY|| 6.6L || V8 Turbo || Diesel ||OHV,&lt;br /&gt; 32 valve||Duramax 6600 V8 engine. '06 Hummer H1 Alpha.
|-
| Z ||L65|| 6.5L || V8 Turbo || Diesel ||OHV||Detroit Diesel V8 built by GM. '00-'01 Hummer H1.
|-
|}

====Engine codes for Nissan-built vans====
Nissan encodes the engine type in character 4 of the VIN.

{| class=&quot;wikitable&quot;
|-
! VIN !! RPO !! Size !! Type !! Fuel !! Valvetrain !! Engine Family/Notes
|-
| 3 ||L0A|| 2.0L || I4 || Gas ||DOHC,&lt;br /&gt; 16 valve||Nissan MR20DE engine. SFI. VVT. For the '15-'18 Chevrolet City Express.
|-
|}

====Engine codes for Navistar-built medium-duty trucks====
Navistar encodes the engine type in character 6 &amp; 7 of the VIN.

{| class=&quot;wikitable&quot;
|-
! VIN !! RPO !! Size !! Type !! Fuel !! Valvetrain !! Engine Family/Notes
|-
| PV ||L5D|| 6.6L || V8 Turbo || Diesel ||OHV,&lt;br /&gt; 32 valve||Duramax 6600 V8 engine. For the Chevy Silverado Medium Duty '19+.
|-
|}

==GM factories supplying North America==

===North American GM factories===
[[w:List_of_General_Motors_factories | List of GM Factories]]
{| class=&quot;wikitable&quot;
!VIN code
!Location
!Notes
|-
|A
|Lakewood Assembly (Lakewood Heights, Atlanta, Georgia)
|through 1990 model year
|-
|A
|Artisan Center (Warren, Michigan)
|From 2026 model year. Cadillac CT5-V Blackwing &quot;Curated by Cadillac&quot; program only.
|-
|B
|Baltimore Assembly (Baltimore, Maryland)
|through 2005 model year
|-
|B
|Reatta Craft Centre/Lansing Craft Centre (Lansing Township, Michigan)
|1988-2006 model year (except GM EV1)
|-
|B
|GM Defense-Manufacturing Customer Innovation Center (MCIC) (Concord, North Carolina)
|From 2024 model year. Chevrolet Suburban HD (a.k.a. HD SUV) (for US govt. only).
|-
|C
|South Gate Assembly (South Gate, California)
|through 1982 model year
|-
|C
|Lansing Car Assembly (Lansing, Michigan)
|South assembly line 1985-2004 model year
|-
|D
|Doraville Assembly (Doraville, Georgia)
|through 2009 model year
|-
|E
|Linden Assembly (Linden, New Jersey)
|through 1991 model year
|-
|E
|Pontiac East Assembly (Pontiac, Michigan) 
|1988-2009 model year
|-
|E
|AM General Military plant (Mishawaka, Indiana)
|1992-2006 Hummer H1
|-
|F
|Flint Truck Assembly (Flint, Michigan) 
|since 1953
|-
|F
|Fairfax II Assembly (Kansas City, Kansas)
|since 1988 model year
|-
|G
|Framingham Assembly (Framingham, Massachusetts)
|through 1989 model year
|-
|G
|Silao Assembly (Silao, Guanajuato, Mexico)
|since 1995 model year
|-
|H
|Buick City Assembly (Flint, Michigan)
|through 1999 model year
|-
|H
|AM General Commercial plant (Mishawaka, Indiana)
|2003-2009 Hummer H2
|-
|H
|Navistar Springfield plant (Main Line) (Springfield, Ohio)
|2019- Chevrolet Silverado Medium Duty (4500HD/5500HD/6500HD)
|-
|J
|Janesville Assembly (Janesville, Wisconsin)
|through 2009 model year
|-
|J
|Lansing Delta Township Assembly (Lansing, Michigan)
|since 2007 model year
|-
|K
|Leeds Assembly (Leeds, Kansas City, Missouri)
|through 1988 model year
|-
|K
|Linden Assembly (Linden, New Jersey)
|from 1994-2005 model year
|-
|K
|Nissan plant (Cuernavaca, Morelos, Mexico)
|2015-2018 Chevrolet City Express
|-
|L
|Van Nuys Assembly (Van Nuys, California)
|through 1992 model year
|-
|L
|San Luis Potosí Assembly (San Luis Potosí, Mexico)
|since 2009 model year
|-
|M
|Lansing Car Assembly (Lansing, Michigan)
|through 1984 model year, North assembly line 1985-2005 model year
|-
|M
|Toluca Assembly (Toluca, Mexico state, Mexico)
|through 2008 model year
|-
|N
|Norwood Assembly (Norwood, Ohio) 
|through 1987 model year
|-
|N
|Navistar Springfield plant (Secondary Line) (Springfield, Ohio)
|2017- Chevrolet Express cutaway, GMC Savana cutaway
|-
|P
|Pontiac Assembly (Pontiac, Michigan)
|through 1988 model year
|-
|R
|Arlington Assembly (Arlington, Texas)
|since 1965 [all GM brands]. (R plant code used only by Chevrolet in 1963-64)
|-
|S
|St. Louis Assembly (St. Louis, Missouri)
|through 1987 model year
|-
|S
|Spring Hill Manufacturing (Spring Hill, Tennessee) 
|2002-2007 Saturn Vue &amp; 2009-2010 Chevrolet Traverse only
|-
|S
|Spartan Motors/Shyft Group plant (Charlotte, Michigan) 
|2016- Chevrolet Low Cab Forward 3500/3500HG/4500/4500HG/5500HG/5500XG/6500XD/7500XD
|-
|S
|Ramos Arizpe Assembly (Ramos Arizpe, Coahuila, Mexico)
|since 1982
|-
|T
|Tarrytown Assembly (North Tarrytown, New York)
|through 1996 model year 
|-
|U
|Detroit/Hamtramck Assembly (Factory Zero) &lt;br /&gt; (Detroit &amp; Hamtramck, Michigan)
|since 1986 model year
|-
|U
|Artisan Center (Warren, Michigan)
|From 2025 model year. Cadillac Celestiq only.
|-
|V
|Pontiac Central Assembly (Pontiac, Michigan) 
|through 1991 model year
|-
|V
|Pontiac East Assembly (Pontiac, Michigan) 
|through 1985 model year
|-
|W
|Willow Run Assembly (Ypsilanti Township, Michigan) 
|through 1993 model year
|-
|X
|Fairfax Assembly (Fairfax I) (Kansas City, Kansas)
|through 1987 model year
|-
|Y
|Wilmington Assembly (Wilmington, Delaware) 
|through 2010 model year
|-
|Z
|Fremont Assembly (Fremont, California) 
|through 1982 model year
|-
|Z
|NUMMI (Fremont, California) 
|1985-2010 model year
|-
|Z
|Spring Hill Manufacturing (Spring Hill, Tennessee) 
|since 1991 model year (except Vue &amp; Traverse)
|-
|Z
|Fort Wayne Assembly (Roanoke, Indiana) 
|since 1988 model year
|-
|0
|Pontiac West Assembly (Pontiac, Michigan) 
|through 1994 model year
|-
|0
|Lansing Craft Centre (Lansing Township, Michigan)
|GM EV1 only
|-
|0
|Lansing Grand River Assembly (Lansing, Michigan) 
|since 2003 model year
|-
|0
|Artisan Center (Warren, Michigan)
|2024 Cadillac CT5-V Blackwing 20th Anniversary Edition where the final eight digits of the VIN are R0912004 through R0912024 or R0962004 through R0962024
|-
|1
|Wentzville Assembly (Wentzville, Missouri) 
|since 1985 model year
|-
|1
|Oshawa Car Assembly (Oshawa, Ontario, Canada) 
|from 1967-1983 model year
|-
|1
|Oshawa Car Assembly (Line 2 a.k.a. Consolidated Line) (Oshawa, Ontario, Canada) 
|from 1984-2019 model year; switched to pickup trucks for 2019 model year
|-
|1
|Oshawa Car Assembly (Oshawa, Ontario, Canada) 
|Silverado pickup trucks since 2022 model year
|-
|1
|Oshawa Truck Assembly (Oshawa, Ontario, Canada) 
|through 2009 model year
|-
|2
|Moraine Assembly (Moraine, Ohio) 
|through 2009 model year
|-
|2
|Sainte-Thérèse Assembly (Boisbriand, Quebec, Canada) 
|through 2002 model year
|-
|3
|Detroit Truck &amp; Bus plant (Piquette Ave., Detroit, Michigan) 
|through 1999 model year
|-
|3
|Saint-Eustache Bus Plant (Saint-Eustache, Quebec, Canada) 
|through 1987 model year
|-
|4
|Orion Assembly (Orion Township, Michigan) 
|since 1985 model year
|-
|4
|Scarborough Van Assembly (Scarborough, Ontario, Canada) 
|through 1993 model year
|-
|5
|Bowling Green Assembly (Bowling Green, Kentucky) 
|since 1981 model year
|-
|6
|Oklahoma City Assembly (Oklahoma City, Oklahoma) 
|through 2006 model year
|-
|6
|CAMI plant (Ingersoll, Ontario, Canada) 
|1990-2022 model year
|-
|7
|Lordstown Assembly (Warren, Ohio) 
|from 1979-2019 model year
|-
|8
|Shreveport Assembly (Shreveport, Louisiana) 
|through 2012 model year
|-
|9
|Detroit Assembly (Clark Street, Detroit, Michigan)&lt;br&gt; (Cadillac plant)
|from 1979-1988 model year
|-
|9
|Oshawa Car Assembly (Line 1 a.k.a. Flex Line)&lt;br&gt; (Oshawa, Ontario, Canada) 
|from 1984-2020 model year
|-
|9
|KUKA plant (Livonia, Michigan) 
|2022 model year only (BrightDrop Zevo 600)
|-
|9
|CAMI plant (Ingersoll, Ontario, Canada) 
|2023-2026 model year (BrightDrop Zevo/Chevrolet BrightDrop)
|}

===Non-North American GM factories supplying North America===
{| class=&quot;wikitable&quot;
!VIN code
!Location
!Models Sourced
|-
|A
|SAIC-GM plant: Jinqiao, Pudong district, Shanghai, China
|2017-2018 Cadillac CT6 Plug-in Hybrid
|-
|B
|Daewoo/GM Daewoo/GM Korea plant: Bupyeong, South Korea
|1988-1993 Pontiac LeMans, 2004-2011 Chevrolet Aveo, 2005-2010 Pontiac Wave/G3, 2004-2006 Chevrolet &lt;br /&gt; Epica (Canada), 2013-2022 Chevrolet Trax, Buick Encore, 2021- Chevrolet Trailblazer, 2020- Buick Encore GX, 2024- Buick Envista
|-
|C
|GM Daewoo/GM Korea plant: Changwon, South Korea
|2003-2010 Pontiac Matiz/Matiz G2 (Mexico), 2013-2022 Chevrolet Spark, 2024- Chevrolet Trax
|-
|D
|SAIC-GM Dongyue Motors plant: Yantai, Shandong province, China
|2016- Buick Envision, 2019-2023 Chevrolet Aveo (Mexico), 2023- Chevrolet Onix (Mexico)
|-
|G
|Opel plant: Gliwice, Poland
|2016-2019 Buick Cascada
|-
|K
|Suzuki plant: Kosai, Shizuoka prefecture, Japan
|1985-1988 Chevrolet Sprint, 1989-1990 Geo Metro hatchback, 1990-1993 Geo Metro convertible, 1985-1990 Pontiac Firefly (Canada), 1991 &amp; 1994 Pontiac Firefly convertible &amp; sedan (Canada)
|-
|K
|GM Daewoo/GM Korea plant: Kunsan, South Korea
|2004-2007 Chevrolet Optra (Canada), 2012-2014 Chevrolet Orlando (Canada)
|-
|L
|Holden plant:  Elizabeth, South Australia, Australia
|2004-2006 Pontiac GTO, 2008-2009 Pontiac G8, 2011-2017 Chevrolet Caprice PPV, 2014-2017 Chevrolet SS
|-
|R
|Opel plant: Rüsselsheim, Germany
|1997-2001 Cadillac Catera
|-
|T
|GM India plant: Talegaon, Maharashtra, India
|2017-2021 Chevrolet Spark Classic/Beat (Mexico)
|-
|V
|SAIC-GM Wuhan plant: Wuhan, Hubei province, China
|2018-2021 Chevrolet Cavalier (Mexico), 2022- Chevrolet Cavalier Turbo (Mexico)
|-
|W
|Suzuki plant: Iwata, Shizuoka prefecture, Japan
|1989-1990 Geo Tracker
|-
|1
|Opel plant: Rüsselsheim, Germany
|2011, 2018-2020 Buick Regal
|-
|3
|Isuzu plant: Kawasaki, Kanagawa prefecture, Japan
|1987-1998 Chevrolet/GMC W5, 1989-1996 Chevrolet/GMC W6, 1984-1996 Chevrolet/GMC W7
|-
|5
|Opel plant: Antwerp, Belgium
|2008-2009 Saturn Astra
|-
|7
|Isuzu plant: Fujisawa, Kanagawa prefecture, Japan
|1988 Chevrolet Spectrum, 1988 Pontiac Sunburst (Canada), 1989 Geo Spectrum, 1990-1993 Geo Storm,&lt;br /&gt; 1999-2008 Chevrolet/GMC W3500, 1988-2009 Chevrolet/GMC W4, 1999-2009 Chevrolet/GMC W5,&lt;br /&gt; 2000-2004 Chevrolet/GMC WT5500,&lt;br /&gt; 2016- Chevrolet Low Cab Forward 3500HD/4500HD/4500XD/5500HD/5500XD
|-
|8
|Isuzu plant: Fujisawa, Kanagawa prefecture, Japan
|1981-1982 Chevrolet LUV, 1985-1987 Chevrolet Spectrum, 1985-1987 Pontiac Sunburst (Canada),&lt;br /&gt; 1986-1987 Chevrolet/GMC W4
|}

==GM WMIs==

{| class=wikitable
!WMI
!Marque
!Country
|-
|1G1||rowspan=57|Chevrolet||United States
|-
|1G8||United States (MPV 1981-1986)
|-
|1GA||United States (bus [van with more than 3 rows of seats])
|-
|1GB||United States (incomplete vehicle)
|-
|1GC||United States (truck)
|-
|1GN||United States (MPV 1987-)
|-
|1HA||United States (Express incomplete vehicle made by Navistar)
|-
|1HT||United States ([[w:Chevrolet Silverado#Medium duty version_(4500HD,_5500HD,_6500HD,_and_International_CV)|Silverado Medium Duty]] incomplete vehicle made by Navistar)
|-
|1Y1||United States (made by NUMMI)
|-
|2C1||Canada (car made by CAMI)
|-
|2CN||Canada (SUV made by CAMI - 1998-2011)
|-
|2G1||Canada
|-
|2G5||Canada (truck - Chevrolet BrightDrop '25)
|-
|2G8||Canada (MPV 1981-1986)
|-
|2GA||Canada (bus [van with more than 3 rows of seats])
|-
|2GB||Canada (incomplete vehicle)
|-
|2GC||Canada (truck - includes Chevrolet BrightDrop '26)
|-
|2GN||Canada (MPV 1987-)
|-
|3G1||Mexico
|-
|3GC||Mexico (truck)
|-
|3GN||Mexico (MPV)
|-
|3N6||Mexico (Truck - City Express made by Nissan)
|-
|4G1||United States (made by Genasys L.C.)
|-
|4KB||United States (W-Series incomplete vehicle made by GM - through 2009)
|-
|4W1||United States (MPV - Chevrolet Suburban HD made for US govt. in Concord, NC)
|-
|54D||United States (incomplete vehicle made by Spartan Motors/The Shyft Group)
|-
|6G1||Australia (2011-2013 Caprice PPV)
|-
|6G3||Australia (2014-2017 Caprice PPV &amp; SS performance sedan)
|-
|ADM||South Africa
|-
|J81||Japan (car made by Isuzu)
|-
|J8B||Japan (incomplete vehicle made by Isuzu - through 2009)
|-
|J8Z||Japan (LUV pickup made by Isuzu)
|-
|JAL||Japan (incomplete vehicle made by Isuzu - 2016+)
|-
|JG1||Japan (car made by Suzuki)
|-
|KL1||South Korea (car)
|-
|KL7||South Korea (MPV - 2012+)
|-
|KL8||South Korea (Spark)
|-
|LSF||China (S-10 Max made by SAIC-Maxus - Mexico only)
|-
|LSG||China (SAIC-GM)
|-
|LSH||China (Express Max made by SAIC-Maxus - Mexico only)
|-
|LZW||China (SAIC-GM-Wuling)
|-
|MA6||India
|-
|MJB||Indonesia (GM Indonesia)
|-
|MK3||Indonesia (SGMW Motor Indonesia)
|-
|MMM||Thailand
|-
|XUF||Russia (GM Russia - St. Petersburg plant)
|-
|XUU||Russia (Chevrolet Korea models made by Avtotor in Kaliningrad)
|-
|XWB||Uzbekistan (GM Uzbekistan, UzAuto Motors)
|-
|XWF||Russia (Chevrolet Tahoe &amp; Trailblazer [GMT360] made by Avtotor in Kaliningrad)
|-
|X9L||Russia (GM-AvtoVAZ)
|-
|8AG||Argentina
|-
|8GG||Chile
|-
|8LD||Ecuador
|-
|8Z1||Venezuela
|-
|9BG||Brazil
|-
|93C||Brazil
|-
|9GC||Colombia
|-
|J81||rowspan=6|Geo||Japan (car made by Isuzu)
|-
|JG1||Japan (car made by Suzuki)
|-
|JGC||Japan (SUV made by Suzuki)
|-
|1Y1||United States (car made by NUMMI)
|-
|2C1||Canada (car made by CAMI)
|-
|2CN||Canada (SUV made by CAMI - 1990-1997)
|-
|KLA||rowspan=3|GM Daewoo/&lt;br /&gt;GM Korea||South Korea (Bupyeong &amp; Kunsan plants)
|-
|KLY||South Korea (Changwon plant)
|-
|5GD||United States (G2X)
|-
|1G2||rowspan=12|Pontiac||United States
|-
|1G5||United States (incomplete vehicle - for '89-'90 Turbo Grand Prix by ASC/McLaren &amp; '03-'05 Montana Mobility, '06 Montana SV6 Mobility)
|-
|1GM||United States (MPV)
|-
|2CK||Canada (2006-2009 Torrent made by CAMI)
|-
|2G2||Canada
|-
|2G7||Canada (US market 1983 Pontiac Parisienne)
|-
|3G2||Mexico
|-
|3G7||Mexico (MPV: 2001-2005 Aztek)
|-
|4G2||United States (made by Genasys L.C.)
|-
|5Y2||United States (made by NUMMI)
|-
|6G2||Australia
|-
|KL2||South Korea (made by Daewoo/GM Daewoo)
|-
|1G7||rowspan=6|Pontiac&lt;br /&gt;(Canada only)||United States
|-
|2C7||Canada (car made by CAMI)
|-
|2CG||Canada (SUV made by CAMI)
|-
|2G7||Canada
|-
|J87||Japan (car made by Isuzu)
|-
|JG7||Japan (car made by Suzuki)
|-
|KL7||Passport&lt;br /&gt;(Canada only)||South Korea (car made by Daewoo)
|-
|J87||rowspan=3|Asüna&lt;br /&gt;(Canada only)||Japan (car made by Isuzu)
|-
|KL7||South Korea (car made by Daewoo)
|-
|2CG||Canada (SUV made by CAMI)
|-
|1G3||rowspan=3|Oldsmobile||United States
|-
|1GH||United States (MPV/SUV)
|-
|2G3||Canada
|-
|1G4||rowspan=9|Buick||United States
|-
|2G4||Canada
|-
|3G4||Mexico
|-
|3G5||Mexico (MPV)
|-
|4GL||United States (incomplete vehicle)
|-
|5GA||United States (MPV)
|-
|KL4||South Korea (MPV)
|-
|LRB||China (SAIC-GM)
|-
|W04||Germany &amp; Poland
|-
|KLA||Alpheon||South Korea (2011-2015)
|-
|1G6||rowspan=10|Cadillac||United States
|-
|1GE||United States (incomplete vehicle)
|-
|1GY||United States (SUV)
|-
|2G6||Canada
|-
|2GE||Canada (incomplete vehicle)
|-
|3GY||Mexico (SUV)
|-
|LRE||China (SAIC-GM)
|-
|W06||Germany
|-
|XWF||Russia (made by Avtotor in Kaliningrad)
|-
|YSC||Sweden
|-
|1G8||rowspan=4|Saturn||United States
|-
|3GS||Mexico (SUV)
|-
|5GZ||United States (MPV/SUV)
|-
|W08||Belgium
|-
|1G0||rowspan=22|GMC||United States (bus 1981-1986)
|-
|1G5||United States (MPV 1981-1986)
|-
|1GD||United States (incomplete vehicle)
|-
|1GJ||United States (bus 1987-)
|-
|1GK||United States (MPV 1987-)
|-
|1GT||United States (truck)
|-
|2CK||Canada (1990-1991 Tracker made by CAMI - Canada only)
|-
|2CT||Canada (2010-2011 Terrain made by CAMI)
|-
|2G0||Canada (bus [van with more than 3 rows of seats] 1981-1986)
|-
|2G5||Canada (MPV 1981-1986)
|-
|2GD||Canada (incomplete vehicle)
|-
|2GH||Canada (transit bus)
|-
|2GJ||Canada (bus [van with more than 3 rows of seats] 1987-)
|-
|2GK||Canada (MPV 1987-)
|-
|2GT||Canada (truck)
|-
|3GK||Mexico (SUV)
|-
|3GT||Mexico (truck)
|-
|4KD||United States (W-Series incomplete vehicle made by GM - through 2009)
|-
|7GZ||United States (incomplete vehicle made by Navistar)
|-
|J8D||Japan (incomplete vehicle made by Isuzu - through 2009)
|-
|JGT||Japan (SUV made by Suzuki - Canada only)
|-
|KL6||South Korea (Middle East market Terrain '08-'10)
|-
|4GD||WhiteGMC||United States (1988-1989 Brigadier made by GM)
|-
|137||rowspan=6|Hummer||United States (H1 made by AM General)
|-
|5GN||United States (H3T)
|-
|5GR||United States (H2 made by AM General)
|-
|5GT||United States (H3)
|-
|ADM||South Africa (H3)
|-
|XWF||Russia (H2 &amp; H3 made by Avtotor in Kaliningrad)
|-
|4G5||General Motors||United States (EV1)
|-
|2G5||rowspan=2|BrightDrop||Canada (Truck 2023-2024)
|-
|5G5||United States (Truck made by Kuka AG - 2022 only)
|-
|5G2||rowspan=2|Cruise||United States (car) (Cruise AV)
|-
|5G3||United States (MPV) (Cruise Origin AV)
|-
|YS3||rowspan=4|Saab||Sweden 
|-
|JF4||Japan (9-2X made by Subaru)
|-
|3G0||Mexico (9-4X)
|-
|5S3||United States (9-7X)
|-
|W0L||rowspan=19|Opel/Vauxhall||Germany &amp; the rest of Europe (2017 and earlier)
|-
|W0V||Germany &amp; the rest of Europe (2018 and later) &amp; Opel Ampera-e Mid-2017 - 2019
|-
|W0L||when plant code is H: Thailand (Zafira A)
|-
|W0L||when plant code is 0: South Korea (Antara) or B: South Korea (Antara, Mokka A, Mokka X [A])
|-
|W0L||when plant code is C: South Korea (Opel Karl/Vauxhall Viva)
|-
|W0V||when plant code is B: South Korea (Mokka X [A]) or C: South Korea (Opel Karl/Vauxhall Viva)
|-
|SCC||UK (Opel Lotus Omega made by Lotus)
|-
|SED||UK (made by IBC Vehicles)
|-
|TW8||Portugal
|-
|VF1||France (Arena made by Renault)
|-
|VN1||France (Movano A made by Renault at SOVAB plant in Batilly, France)
|-
|VSX||Spain
|-
|XUF||Russia (Opel made by GM Russia - St. Petersburg plant)
|-
|XWF||Russia (Opel made by Avtotor in Kaliningrad)
|-
|1G0||United States (Opel GT, Opel/Vauxhall Ampera, Opel Ampera-e Early - Mid-2017)
|-
|4GD||United States (Sintra)
|-
|ADM||South Africa
|-
|JAA||Japan (Opel Campo made by Isuzu)
|-
|JAC||Japan (Monterey made by Isuzu)
|-
|SKA||rowspan=4|Vauxhall Motors||UK
|-
|SCC||UK (Vauxhall Lotus Carlton made by Lotus)
|-
|6G1||Australia (Vauxhall Monaro &amp; VXR8 made by Holden)
|-
|JAA||Japan (Vauxhall Brava made by Isuzu)
|-
|SKF||rowspan=2|Bedford Vehicles||UK
|-
|JAA||Japan (Bedford Brava made by Isuzu)
|-
|6G1||rowspan=18|Holden||Australia (2003-2017)
|-
|6H8||Australia (1989-2002)
|-
|JAA||Japan (Rodeo pickup [TF] made by Isuzu)
|-
|JAC||Japan (Jackaroo/Monterey made by Isuzu)
|-
|JSA||Japan (YG Cruze made by Suzuki)
|-
|KL3||South Korea
|-
|MMM||Thailand ('09-'11 Colorado pickup [RC] made by GM Thailand)
|-
|MMU||Thailand ('13-'20 Colorado pickup [RG], '13-'16 Colorado 7, '17-'20 Trailblazer made by GM Thailand)
|-
|MPA||Thailand ('04-'08 Rodeo pickup [RA] made by Isuzu Thailand)
|-
|SED||UK (1st gen. Frontera made by IBC Vehicles)
|-
|W0L||Germany &amp; the rest of Europe (2017 and earlier)
|-
|W0L||when plant code is H: Thailand (Zafira A)
|-
|W0V||Germany &amp; the rest of Europe (2018-2020)
|-
|1GH||United States (Acadia)
|-
|3G0||Mexico (Equinox)
|-
|3GM||Mexico (Suburban)
|-
|4S2||United States (2nd gen. Frontera made by [[w:Subaru Isuzu Automotive|SIA]])
|-
|5G8||United States (Volt)
|-
|1GG||rowspan=4|Isuzu||United States (Truck - Hombre &amp; i-Series made by GM)
|-
|4GT||United States (H-Series &amp; T-Series incomplete vehicle made by GM - through 2009)
|-
|4KL||United States (N-Series incomplete vehicle made by GM - through 2009)
|-
|4NU||United States (MPV/SUV - Ascender made by GM)
|-
|W0L||Subaru||Thailand [plant code H] (Traviq made by GM Thailand for export to Japan)
|-
|4G3||Toyota||United States (Cavalier made by GM for export to Japan)
|-
|3GP||Honda||Mexico (MPV/SUV: 2024-2026 Prologue made by GM)
|-
|4W5||Acura||United States (MPV/SUV: 2024 ZDX EV made by GM)
|}

{{BookCat}}</text>
      <sha1>s3uii1qtmd7hbsar55bps5gtlry844c</sha1>
    </revision>
    <revision>
      <id>4656135</id>
      <parentid>4656067</parentid>
      <timestamp>2026-08-02T23:00:42Z</timestamp>
      <contributor>
        <username>JustTheFacts33</username>
        <id>3434282</id>
      </contributor>
      <comment>/* Series 2000-2009 Light Duty Truck &amp; Multi-Purpose Passenger Vehicle */</comment>
      <origin>4656135</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="205772" sha1="fir4tk0amqp4k77dw3vedcxr79ks03p" xml:space="preserve">{{Vehicle Identification Numbers (VIN codes)/Warning}}{{clear}}
It is the tenth digit that gives you the model year for GM. I've been working at a Chevy dealer for years running codes/vins. For example (my examples only apply to 2001-2015 gm vehicles)
Remember 10th digit from the beginning, (left to right).
2001... 1, 
2002...2, 
2003...3, 
etc., 
2009...9. 
After 2009, the tenth digit was given a letter
2010... A, 
2011...B, 
2012...C, 
2013...D, 
2014...E, 
2015...F, 
Etc...
We have another 20 years worth of letters.
Thanks for reading.
You can always check your model year by looking in your drivers side door jamb and it will give you model year. If it was assembled in July or later, the model year is probably a year later than the calendar year of the manufacturing date listed.

==American GM==
===American VIN format 1981-1984 Passenger Car===
GM's VIN format is as follows:

&lt;table border=1 style=&quot;margin:auto;&quot;&gt;
&lt;tr&gt;
&lt;th&gt;Position&lt;/th&gt;
&lt;th&gt;Sample&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;Description&lt;/th&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;1&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td rowspan=3&gt;[[#GM WMIs|World Manufacturer Identifier]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;G&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;6&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;A&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[#American restraint types 1981-1984|Restraint type]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;5&lt;/td&gt;
&lt;td&gt;M&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[#Car Line &amp; Series Code 1981-1984|Car Line &amp; Series Code]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;6&lt;/td&gt;
&lt;td&gt;4&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td rowspan=2&gt;[[#Body style codes 1981-1986|Body style]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;7&lt;/td&gt;
&lt;td&gt;7&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt; &lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;8&lt;/td&gt;
&lt;td&gt;8&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[#American engine codes 1981-|Engine type]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;9&lt;/td&gt;
&lt;td&gt;0&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[Vehicle Identification Numbers (VIN codes)/Check digit |Check digit]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;10&lt;/td&gt;
&lt;td&gt;E&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[Vehicle Identification Numbers (VIN codes)/Model year|Model year]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;11&lt;/td&gt;
&lt;td&gt;9&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[#GM factories supplying North America|Factory ID]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;12&lt;/td&gt;
&lt;td&gt;1&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td rowspan=6&gt;Sequential number
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;13&lt;/td&gt;
&lt;td&gt;2&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;14&lt;/td&gt;
&lt;td&gt;3&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;15&lt;/td&gt;
&lt;td&gt;7&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;16&lt;/td&gt;
&lt;td&gt;6&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;17&lt;/td&gt;
&lt;td&gt;2&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;
&lt;/table&gt;

====American restraint types 1981-1984====
The restraint type is specified as character 4 of the American GM VIN for passenger cars.

{| border=1 style=&quot;margin:auto;&quot;
!VIN Code
!Description
|-
|A||Manual Seatbelts only - No Passive Restraint
|}

====Car Line &amp; Series Code 1981-1984====
The Car Line &amp; Series Code is specified as character 5 of the American GM VIN for passenger cars.

{| border=1 style=&quot;margin:auto;&quot;
!List of GM platforms
!Car Line &amp; &lt;br&gt; Series Code
!:Category:General Motors vehicles|Model
|-
|rowspan=19|GM A platform - rear-wheel drive
|T||Chevrolet Malibu 1981
|-
|W||Chevrolet Malibu Classic 1981
|-
|Z||Chevrolet Monte Carlo 1981
|-
|D||Pontiac LeMans 1981
|-
|F||Pontiac Grand LeMans 1981
|-
|J||Pontiac Grand Prix 1981
|-
|K||Pontiac Grand Prix LJ 1981
|-
|P||Pontiac Grand Prix Brougham 1981
|-
|G||Oldsmobile Cutlass sedan, Cutlass Cruiser wagon 1981
|-
|H||Oldsmobile Cutlass Cruiser ''Brougham'' wagon 1981
|-
|K||Oldsmobile Cutlass Calais coupe 1981
|-
|M||Oldsmobile Cutlass Supreme ''Brougham'' 1981
|-
|R||Oldsmobile Cutlass Supreme coupe, Cutlass LS sedan 1981
|-
|E||Buick Century wagon 1981
|-
|H||Buick Century sedan, Estate wagon 1981
|-
|J||Buick Regal 1981
|-
|K||Buick Regal ''Sport'' 1981
|-
|L||Buick Century ''Limited'' 1981
|-
|M||Buick Regal ''Limited'' 1981
|-
|rowspan=10|GM A platform - front-wheel drive
|W||Chevrolet Celebrity 1982-1984
|-
|F||Pontiac 6000 1982-1984
|-
|G||Pontiac 6000 ''LE'' 1982-1984
|-
|H||Pontiac 6000 ''STE'' 1983-1984
|-
|G||Oldsmobile Cutlass Ciera 1982
|-
|J||Oldsmobile Cutlass Ciera ''LS'' 1982-1984, Cutlass Cruiser ''LS'' 1984
|-
|M||Oldsmobile Cutlass Ciera ''Brougham'' 1982-1984
|-
|G||Buick Century ''T-Type'' 1983-1984
|-
|H||Buick Century ''Custom'' 1982-1984
|-
|L||Buick Century ''Limited'' 1982-1984
|-
|rowspan=19|GM B platform
|D||Chevrolet Bel Air 1981 (Canada only)
|-
|L||Chevrolet Impala 1981-1984
|-
|N||Chevrolet Caprice Classic 1981-1984
|-
|F||Pontiac Laurentian 1981 (Canada only)
|-
|L||Pontiac Catalina 1981, Parisienne 1984
|-
|L||Pontiac Parisienne 1982-1983 (Canada only)
|-
|N||Pontiac Bonneville 1981
|-
|N||Pontiac Parisienne 1981, Parisienne Brougham 1982-1983 (Canada only)
|-
|R||Pontiac Bonneville Brougham 1981
|-
|T||Pontiac Parisienne Brougham 1984
|-
|L||Oldsmobile Delta 88 1981-1983
|-
|N||Oldsmobile Delta 88 Royale 1981-1984
|-
|P||Oldsmobile Custom Cruiser 1981-1984
|-
|V||Oldsmobile Delta 88 Royale Brougham LS 1984
|-
|Y||Oldsmobile Delta 88 Royale Brougham 1981-1984
|-
|N||Buick Le Sabre 1981, Le Sabre ''Custom'' 1982-1984 
|-
|P||Buick Le Sabre ''Limited'' 1981-1984
|-
|R||Buick Le Sabre Estate Wagon 1981-1983
|-
|V||Buick Electra Estate Wagon 1981-1984
|-
|rowspan=13|GM C platform - rear-wheel drive
|G||Oldsmobile 98 Regency 1984
|-
|H||Oldsmobile 98 Regency Brougham 1984
|-
|V||Oldsmobile 98 Luxury 1981
|-
|W||Oldsmobile 98 Regency Brougham 1982-1983
|-
|X||Oldsmobile 98 Regency 1981-1983
|-
|R||Buick Electra Limited 1984
|-
|U||Buick Electra Park Avenue 1984
|-
|W||Buick Electra Park Avenue 1981-1983
|-
|X||Buick Electra Limited 1981-1983
|-
|B||Cadillac Fleetwood Brougham 1981-1983
|-
|D||Cadillac DeVille 1981-1983
|-
|M||Cadillac DeVille 1984
|-
|W||Cadillac Fleetwood Brougham 1984
|-
|rowspan=1|GM D platform - rear-wheel drive
|F||Cadillac Fleetwood Limousine 1981-1984
|-
|rowspan=4|GM E platform
|Z||Oldsmobile Toronado Brougham 1981-1984
|-
|Y||Buick Riviera T-Type 1981-1984
|-
|Z||Buick Riviera 1981-1984
|-
|L||Cadillac Eldorado 1981-1984
|-
|rowspan=7|GM F platform
|P||Chevrolet Camaro Sport Coupe 1981-1984
|-
|S||Chevrolet Camaro Berlinetta 1981-1984
|-
|S||Pontiac Firebird 1981-1984
|-
|T||Pontiac Firebird ''Esprit'' 1981
|-
|V||Pontiac Firebird ''Formula'' 1981
|-
|W||Pontiac Firebird ''Trans Am'' 1981-1984
|-
|X||Pontiac Firebird ''Trans Am'' Turbo Special Edition 1981, Firebird ''S/E'' 1982-1984
|-
|rowspan=15|GM G platform - rear-wheel drive
|W||Chevrolet Malibu Classic 1982, Malibu 1983
|-
|Z||Chevrolet Monte Carlo 1982-1984
|-
|J||Pontiac Grand Prix 1982-1984
|-
|K||Pontiac Grand Prix LJ 1982-1983, Grand Prix LE 1984
|-
|N||Pontiac Bonneville G 1982-1984
|-
|P||Pontiac Grand Prix Brougham 1982-1984
|-
|R||Pontiac Bonneville G Brougham 1982-1984
|-
|S||Pontiac Bonneville G ''LE'' 1984
|-
|H||Oldsmobile Cutlass Cruiser wagon 1982-1983
|-
|K||Oldsmobile Cutlass Calais coupe 1982-1984
|-
|M||Oldsmobile Cutlass Supreme ''Brougham'' 1982-1984
|-
|R||Oldsmobile Cutlass Supreme coupe &amp; sedan 1982-1984
|-
|J||Buick Regal 1982-1984
|-
|K||Buick Regal ''Sport'' 1982, Regal ''T-Type'' 1983-1984
|-
|M||Buick Regal ''Limited'' 1982-1984
|-
|rowspan=13|GM J platform
|C||Chevrolet Cavalier 1983-1984
|-
|D||Chevrolet Cavalier 2-d/4-d/wagon 1982, Cavalier CS 1983-1984
|-
|E||Chevrolet Cavalier 3-door hatchback 1982, Cavalier CS 3-door hatchback 1983, Cavalier Type 10 2-d/3-d/Convertible 1984
|-
|B||Pontiac J2000 1982, 2000 1983, 2000 Sunbird 1984
|-
|C||Pontiac J2000 LE 1982, 2000 LE 1983, 2000 Sunbird LE Convertible 1983, 2000 Sunbird LE 1984
|-
|D||Pontiac J2000 SE 1982, 2000 SE 1983, 2000 Sunbird SE 1984
|-
|E||Pontiac J2000 S 1982
|-
|C||Oldsmobile Firenza Base model 1982-1984, Firenza S 1982-1984
|-
|D||Oldsmobile Firenza LX 1982-1984, Firenza SX 1982-1984
|-
|E||Buick Skyhawk T-Type 1983-1984
|-
|S||Buick Skyhawk Custom 1982-1984
|-
|T||Buick Skyhawk Limited 1982-1984
|-
|G||Cadillac Cimarron 1982-1984
|-
|rowspan=1|GM K platform
|S||Cadillac Seville 1981-1984
|-
|rowspan=3|GM P platform
||E||Pontiac Fiero ''Coupe'' 1984
|-
||F||Pontiac Fiero ''SE'' 1984
|-
||M||Pontiac Fiero ''Sport coupe'' 1984
|-
|rowspan=6|GM T platform - rear-wheel drive
|B||Chevrolet Chevette 1981-1983, Chevette CS 1984
|-
|J||Chevrolet Chevette Scooter 1981-1983, Chevette 1984
|-
|B||Pontiac Acadian 1981-1984 (Canada only)
|-
|J||Pontiac Acadian S 1981-1982, Pontiac Acadian Scooter 1983-1984 (Canada only)
|-
|L||Pontiac T1000 1982, 1000 1983-1984
|-
|M||Pontiac T1000 1981
|-
|rowspan=10|GM X platform
|H||Chevrolet Citation 2-door coupe 1982-1983, Citation II 2-door coupe 1984
|-
|X||Chevrolet Citation hatchback 1981-1983, Citation II hatchback 1984
|-
|T||Pontiac Phoenix SJ 1982-1983, Phoenix SE 1984
|-
|Y||Pontiac Phoenix 1981-1984
|-
|Z||Pontiac Phoenix LJ 1981-1983, Phoenix LE 1984
|-
|B||Oldsmobile Omega 1981-1984
|-
|E||Oldsmobile Omega Brougham 1981-1984
|-
|B||Buick Skylark 1981-1982, Skylark Custom 1983-1984
|-
|C||Buick Skylark Limited 1981-1984
|-
|D||Buick Skylark Sport 1981-1982, Skylark T-Type 1983-1984
|-
|rowspan=1|GM Y platform
|Y||Chevrolet Corvette 1981-1982, 1984
|}

===American VIN format 1985-1986 Passenger Car===
GM has traditionally encoded the platform as the 4th character of the VIN. Other content includes an engine code and manufacturing plant. GM's VIN format is as follows:

&lt;table border=1 style=&quot;margin:auto;&quot;&gt;
&lt;tr&gt;
&lt;th&gt;Position&lt;/th&gt;
&lt;th&gt;Sample&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;Description&lt;/th&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;1&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td rowspan=3&gt;[[#GM WMIs|World Manufacturer Identifier]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;G&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;6&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;D&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[#Platform &amp; Series Codes 1985- Passenger Car|Platform]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;5&lt;/td&gt;
&lt;td&gt;W&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[#Platform &amp; Series Codes 1985- Passenger Car|Series Code]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;6&lt;/td&gt;
&lt;td&gt;6&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td rowspan=2&gt;[[#Body style codes 1981-1986|Body style]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;7&lt;/td&gt;
&lt;td&gt;9&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt; &lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;8&lt;/td&gt;
&lt;td&gt;Y&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[#American engine codes 1981-|Engine type]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;9&lt;/td&gt;
&lt;td&gt;0&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[Vehicle Identification Numbers (VIN codes)/Check digit |Check digit]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;10&lt;/td&gt;
&lt;td&gt;G&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[Vehicle Identification Numbers (VIN codes)/Model year|Model year]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;11&lt;/td&gt;
&lt;td&gt;9&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[#GM factories supplying North America|Factory ID]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;12&lt;/td&gt;
&lt;td&gt;1&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td rowspan=6&gt;Sequential number
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;13&lt;/td&gt;
&lt;td&gt;2&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;14&lt;/td&gt;
&lt;td&gt;3&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;15&lt;/td&gt;
&lt;td&gt;7&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;16&lt;/td&gt;
&lt;td&gt;6&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;17&lt;/td&gt;
&lt;td&gt;2&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;
&lt;/table&gt;

====Body style codes 1981-1986====
The Body type is specified as characters 6 and 7 of the American GM VIN for passenger cars from 1981-1986.

{| border=1 style=&quot;margin:auto;&quot;
!VIN
!Description
|-
|11,27,37,47,57,97||Two-Door Coupe/Sedan
|-
|07,08,77,87||Two-Door Hatchback
|-
|67||Two-Door Convertible
|-
|19,69||Four-Door Sedan
|-
|68||Four-Door Hatchback
|-
|23||Four-Door Limousine, 8-passenger (&quot;Limousine&quot;)
|-
|33||Four-Door Limousine w/Center Partition, 7-passenger (&quot;Formal Limousine&quot;)
|-
|35||Four-Door Station Wagon
|}

===American VIN format 1987- Passenger Car===
GM has traditionally encoded the platform as the 4th character of the VIN. Other content includes an engine code and manufacturing plant. GM's VIN format is as follows:

&lt;table border=1 style=&quot;margin:auto;&quot;&gt;
&lt;tr&gt;
&lt;th&gt;Position&lt;/th&gt;
&lt;th&gt;Sample&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;Description&lt;/th&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;1&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td rowspan=3&gt;[[#GM WMIs|World Manufacturer Identifier]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;G&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;6&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;D&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[#Platform &amp; Series Codes 1985- Passenger Car|Platform]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;5&lt;/td&gt;
&lt;td&gt;M&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[#Platform &amp; Series Codes 1985- Passenger Car|Series Code]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;6&lt;/td&gt;
&lt;td&gt;5&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[#Body style codes 1987- Passenger Car|Body style]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;7&lt;/td&gt;
&lt;td&gt;7&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[#American restraint types 1987-|Restraint type]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;8&lt;/td&gt;
&lt;td&gt;N&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[#American engine codes 1981-|Engine type]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;9&lt;/td&gt;
&lt;td&gt;0&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[Vehicle Identification Numbers (VIN codes)/Check digit |Check digit]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;10&lt;/td&gt;
&lt;td&gt;3&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[Vehicle Identification Numbers (VIN codes)/Model year|Model year]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;11&lt;/td&gt;
&lt;td&gt;0&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[#GM factories supplying North America|Factory ID]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;12&lt;/td&gt;
&lt;td&gt;1&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td rowspan=6&gt;Sequential number
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;13&lt;/td&gt;
&lt;td&gt;2&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;14&lt;/td&gt;
&lt;td&gt;3&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;15&lt;/td&gt;
&lt;td&gt;7&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;16&lt;/td&gt;
&lt;td&gt;6&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;17&lt;/td&gt;
&lt;td&gt;2&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;
&lt;/table&gt;

===American VIN format 1981-2009 Light Duty Truck &amp; Multi-Purpose Passenger Vehicle===
GM's VIN format is as follows:

&lt;table border=1 style=&quot;margin:auto;&quot;&gt;
&lt;tr&gt;
&lt;th&gt;Position&lt;/th&gt;
&lt;th&gt;Sample&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;Description&lt;/th&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;1&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td rowspan=3&gt;[[#GM WMIs|World Manufacturer Identifier]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;G&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;K&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;E&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[#GVWR/Brake System 1981-2009 Light Duty Truck &amp; Multi-Purpose Passenger Vehicle|GVWR/Brake System]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;5&lt;/td&gt;
&lt;td&gt;K&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[#Line &amp; Chassis Type 1981-1999 Light Duty Truck &amp; Multi-Purpose Passenger Vehicle|Line &amp; Chassis Type for 1981-1999]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;5&lt;/td&gt;
&lt;td&gt;K&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[#Line &amp; Chassis Type 2000-2009 Light Duty Truck &amp; Multi-Purpose Passenger Vehicle|Line &amp; Chassis Type for 2000-2009]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;6&lt;/td&gt;
&lt;td&gt;1&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[#Series 1981-1999 Light Duty Truck &amp; Multi-Purpose Passenger Vehicle|Series]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;7&lt;/td&gt;
&lt;td&gt;8&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[#Body style codes 1981-2009 Light Duty Truck &amp; Multi-Purpose Passenger Vehicle|Body type]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;8&lt;/td&gt;
&lt;td&gt;K&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[#Engine codes for light trucks|Engine type]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;9&lt;/td&gt;
&lt;td&gt;0&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[Vehicle Identification Numbers (VIN codes)/Check digit |Check digit]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;10&lt;/td&gt;
&lt;td&gt;N&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[Vehicle Identification Numbers (VIN codes)/Model year|Model year]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;11&lt;/td&gt;
&lt;td&gt;J&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[#GM factories supplying North America|Factory ID]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;12&lt;/td&gt;
&lt;td&gt;1&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td rowspan=6&gt;Sequential number
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;13&lt;/td&gt;
&lt;td&gt;2&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;14&lt;/td&gt;
&lt;td&gt;3&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;15&lt;/td&gt;
&lt;td&gt;7&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;16&lt;/td&gt;
&lt;td&gt;6&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;17&lt;/td&gt;
&lt;td&gt;2&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;
&lt;/table&gt;

====GVWR/Brake System 1981-2009 Light Duty Truck &amp; Multi-Purpose Passenger Vehicle====
The GVWR/Brake System is specified as character 4 of the American GM VIN for light trucks.

{| border=1 style=&quot;margin:auto;&quot;
!VIN
!GVWR Range in lbs. &amp; Weight Class
!Brake System
|-
|A||Class A: 0-3,000||Hydraulic
|-
|B||Class B: 3,001-4,000||Hydraulic
|-
|C||Class C: 4,001-5,000||Hydraulic
|-
|D||Class D: 5,001-6,000||Hydraulic
|-
|E||Class E: 6,001-7,000||Hydraulic
|-
|F||Class F: 7,001-8,000||Hydraulic
|-
|G||Class G: 8,001-9,000||Hydraulic
|-
|H||Class H: 9,001-10,000||Hydraulic
|-
|J||Class 3: 10,001-14,000||Hydraulic
|-
|K||Class 4: 14,001-16,000||Hydraulic
|-
|L||Class 5: 16,001-19,500||Hydraulic
|}

====Line &amp; Chassis Type 1981-1999 Light Duty Truck &amp; Multi-Purpose Passenger Vehicle====
The Line &amp; Chassis Type is specified as character 5 of the American GM VIN for light trucks.

{| border=1 style=&quot;margin:auto;&quot;
!VIN
!Description
|-
|B||Special Body Buick, Chevrolet
|-
|C||Chevy full-size pickups &amp; chassis cabs 2wd (C-series) '81-'86, '88-'99,&lt;br /&gt; GMC full-size pickups &amp; chassis cabs 2wd (C-series) '81-'86, Sierra 2wd (C-series) '88-'99
|-
|C||Chevy C10 Blazer 2wd ('81-'82), Tahoe 4-door 2wd ('95-'99), Suburban 2wd ('81-'86, '92-'99),&lt;br /&gt; GMC C1500 Jimmy 2wd ('81-'82), Yukon 4-door 2wd ('95-'99), Suburban 2wd ('81-'86, '92-'99)
|-
|D||Military Truck 4wd
|-
|E||'91-'97 Geo Tracker 2wd, '98-'99 Chevrolet Tracker 2wd
|-
|E||'97-'98 Chevy S-10 EV
|-
|G||Chevy/GMC full-size vans (Chevy Van, Sportvan, Express, GMC Vandura, Rally Van, Savana)
|-
|H||'93-'96 Chevy G30HD/GMC G3500HD cutaway van
|-
|H||Cadillac chassis cutaway/special body (Based on Rwd Fleetwood '93-'96, Fwd DeVille '97-'99)
|-
|J||'89-'97 Geo Tracker 4wd, '98-'99 Chevrolet Tracker 4wd
|-
|K||Chevy full-size pickups &amp; chassis cabs 4wd (K-series) '81-'86, '88-'99,&lt;br /&gt; GMC full-size pickups &amp; chassis cabs 4wd (K-series) '81-'86, Sierra 4wd (K-series) '88-'99
|-
|K||Chevy K10/K5 Blazer 4wd ('81-'86, '92-'94), Tahoe 4wd ('95-'99), Suburban 4wd ('81-'86, '92-'99),&lt;br /&gt; GMC K1500 Jimmy 4wd ('81-'86), Yukon 4wd ('92-'99), Suburban 4wd ('81-'86, '92-'99), '99 Cadillac Escalade 4wd
|-
|L||Chevy Luv 2wd '81-'82
|-
|L||Chevy Astro/GMC Safari 4wd '90-'99
|-
|M||Chevy Astro/GMC Safari 2wd '85-'99
|-
|P||Forward Control (includes Chevrolet Step-Van/GMC Value-Van, Chevy/GMC P-Series)
|-
|R||Chevy Luv 4wd '81-'82
|-
|R||Chevy full-size pickups &amp; chassis cabs 2wd (R-series), Suburban 2wd '87-'91,&lt;br /&gt; GMC full-size pickups &amp; chassis cabs 2wd (R-series), Suburban 2wd '87-'91
|-
|S||Chevy S-10 2wd ('82-'99), S-10 Blazer 2wd ('83-'94), Blazer 2wd ('95-'99), GMC S-15 2wd ('82-'90), Sonoma 2wd ('91-'99),&lt;br&gt; S-15 Jimmy 2wd ('83-'91), Jimmy 2wd ('92-'99), Isuzu Hombre 2wd ('96-'99)
|-
|T||Chevy S-10 4wd ('83-'99), S-10 Blazer 4wd ('83-'94), Blazer 4wd ('95-'99), GMC S-15 4wd ('83-'90), Sonoma 4wd ('91-'99), Syclone 4wd ('91),&lt;br&gt; S-15 Jimmy 4wd ('83-'91), Jimmy 4wd ('92-'99), Typhoon 4wd ('92-93), Envoy 4wd ('98-'99), Oldsmobile Bravada 4wd ('91-'94, '96-'99),&lt;br&gt; Isuzu Hombre 4wd ('98-'99)
|-
|U||Regular length All-Purpose Vehicle ('90-'99 U-body fwd minivans)
|-
|V||Chevy full-size pickups &amp; chassis cabs 4wd (V-series), V10/V1500 Blazer 4wd, Suburban 4wd '87-'91,&lt;br /&gt; GMC full-size pickups &amp; chassis cabs 4wd (V-series), V1500 Jimmy 4wd, Suburban 4wd '87-'91
|-
|W||'81-'87 Chevy El Camino, GMC Caballero
|-
|X||Extended length All-Purpose Vehicle ('97-'99 U-body fwd extended length minivans)
|-
|Z||Cadillac chassis cutaway/special body (Based on Rwd Fleetwood '81-'84, Fwd Fleetwood '85-'92)
|}

====Line &amp; Chassis Type 2000-2009 Light Duty Truck &amp; Multi-Purpose Passenger Vehicle====
The Line &amp; Chassis Type is specified as character 5 of the American GM VIN for light trucks.

{| border=1 style=&quot;margin:auto;&quot;
!VIN
!Description
|-
|A||Pontiac Aztek 2wd '01-'05, Buick Rendezvous 2wd '02-'07
|-
|A||Chevrolet HHR '06-'09, HHR Panel '07-'09
|-
|B||Pontiac Aztek Awd '01-'05, Buick Rendezvous Awd '02-'06
|-
|C||Chevy full-size pickups &amp; chassis cabs 2wd (C-series) '00, full-size chassis cabs 2wd (C3500HD) '01-'02, Silverado 2wd '00-'09, Silverado Classic 2wd '07,&lt;br /&gt; GMC Sierra 2wd (C-series) '00-'09, Sierra Classic 2wd '00, '07
|-
|C||Chevy Tahoe 2wd ('00-'09), Suburban 2wd ('00-'09), Avalanche 2wd ('02-'09),&lt;br /&gt; GMC Yukon 2wd ('00-'09), Yukon XL 2wd ('00-'09), Cadillac Escalade 2wd ('02-'09), Escalade ESV 2wd ('08-'09)
|-
|E||Chevrolet Tracker 2wd '00-'04
|-
|E||Cadillac SRX 2wd &amp; Awd '04-'09
|-
|G||Chevy/GMC full-size vans 2wd (Chevy Express, GMC Savana) '00-09
|-
|H||Chevy/GMC full-size vans 4wd (Chevy Express, GMC Savana) '03-09
|-
|H||Cadillac Commercial Chassis for Hearse (Based on Fwd DeVille '02-'05, DTS '06-'09)
|-
|H||Cadillac Professional Chassis for Limousine (Based on Fwd DeVille '00-'05, DTS '06-'07)
|-
|J||Chevrolet Tracker 4wd '00-'04
|-
|K||Chevy full-size pickups &amp; chassis cabs 4wd (K-series) '00, Silverado 4wd '00-'09, Silverado Classic 4wd '07,&lt;br /&gt; GMC Sierra 4wd (K-series) '00-'09, Sierra Classic 4wd '00, '07
|-
|K||Chevy Tahoe 4wd ('00-'09), Suburban 4wd ('00-'09), Avalanche 4wd ('02-'09), GMC Yukon 4wd ('00-'09), Yukon XL 4wd ('00-'09),&lt;br&gt; Cadillac Escalade 4wd ('00, '02-'09), Escalade ESV 4wd ('03-'09), Escalade EXT 4wd ('02-'09)
|-
|K||Cadillac Professional Chassis for Limousine (Based on Fwd DTS '08-'09)
|-
|L||Chevy Astro/GMC Safari 4wd '00-'05
|-
|L||Chevy Equinox 2wd &amp; Awd '05-'09, Pontiac Torrent 2wd &amp; Awd '06-'09, Saturn Vue 2wd &amp; Awd '08-'09
|-
|M||Chevy Astro/GMC Safari 2wd '00-'05
|-
|N||Hummer H2 '03-'09, H2 SUT '05-'09
|-
|N||Hummer H3 '06-'09, H3T '09
|-
|R||GMC Acadia 2wd, Saturn Outlook 2wd '07-'09, Buick Enclave 2wd '08-'09, Chevy Traverse 2wd '09
|-
|S||Chevy S-10 2wd ('00-'03), Blazer 2wd ('00-'05), GMC Sonoma 2wd ('00-'03), Jimmy 2wd ('00-'01), Isuzu Hombre 2wd ('00)
|-
|S||Chevy Trailblazer 2wd ('02-'09), SSR ('03-'06), GMC Envoy 2wd ('02-'09), Envoy XUV 2wd ('04-'05), Oldsmobile Bravada 2wd ('02-'04),&lt;br&gt; Buick Rainier 2wd ('04-'07), Isuzu Ascender 2wd ('03-'08)
|-
|S||Chevy Colorado 2wd ('04-'09), GMC Canyon 2wd ('04-'09), Isuzu i-series 2wd ('06-'08)
|-
|T||Chevy S-10 4wd ('00-'04), Blazer 4wd ('00-'05), GMC Sonoma 4wd ('00-'04), Jimmy 4wd ('00-'01, Canada only: '02-'05), Envoy 4wd ('00),&lt;br&gt; Oldsmobile Bravada 4wd ('00-'01), Isuzu Hombre 4wd ('00)
|-
|T||Chevy Trailblazer 4wd ('02-'09), GMC Envoy 4wd ('02-'09), Envoy XUV 2wd ('04-'05), Oldsmobile Bravada 4wd ('02-'04), Buick Rainier 4wd ('04-'07),&lt;br&gt; Isuzu Ascender 4wd ('03-'08), Saab 9-7X 4wd ('05-'09)
|-
|T||Chevy Colorado 4wd ('04-'09), GMC Canyon 4wd ('04-'09), Isuzu i-series 4wd ('06-'08)
|-
|U||Regular length All-Purpose Vehicle [Minivan] ('00-'04 Chevy Venture, Pontiac Montana)
|-
|U||Regular length All-Purpose Vehicle [Minivan] (Chevy Uplander [US: '06-'08, Canada only: '05-'09], Pontiac Montana SV6 [Canada only: '05-'09])
|-
|V||Extended length AWD All-Purpose Vehicle [Minivan] ('02-'04 Chevy Venture, Pontiac Montana, Oldsmobile Silhouette Extended length AWD)
|-
|V||Extended length FWD All-Purpose Vehicle [Minivan] ('05 Chevy Venture, Pontiac Montana Extended length FWD)
|-
|V||Extended length FWD All-Purpose Vehicle [Minivan] (Chevy Uplander ['05-'08, Canada only: '09], Pontiac Montana SV6 ['05-'06, Canada only: '07-'09],&lt;br&gt; Buick Terraza ['05-'07], Saturn Relay ['05-'07])
|-
|V||GMC Acadia Awd, Saturn Outlook Awd '07-'09, Buick Enclave Awd '08-'09, Chevy Traverse Awd '09
|-
|X||Extended length FWD All-Purpose Vehicle [Minivan] ('00-'04 Chevy Venture, Pontiac Montana, Oldsmobile Silhouette Extended length FWD)
|-
|X||Extended length AWD All-Purpose Vehicle [Minivan] ('05-'06 Chevy Uplander AWD, Pontiac Montana SV6 AWD, Buick Terraza AWD, Saturn Relay AWD)
|-
|Z||Saturn Vue 2wd &amp; Awd '02-'07
|}

====Series 1981-1999 Light Duty Truck &amp; Multi-Purpose Passenger Vehicle====
The Series is specified as character 6 of the American GM VIN for light trucks.

{| border=1 style=&quot;margin:auto;&quot;
!VIN
!Description
|-
|1||1/2 Ton (includes '96-'99 Isuzu Hombre)
|-
|2||3/4 Ton
|-
|3||1 Ton
|-
|8||1/2 Ton ('81-'87 El Camino, Caballero)
|-
|9||Cadillac, Buick, Chevrolet Commercial Body/Chassis
|-
|0||All-Purpose Vehicle ('90-'99 U-body fwd minivans)
|}

====Series 2000-2009 Light Duty Truck &amp; Multi-Purpose Passenger Vehicle====
The Series is specified as character 6 of the American GM VIN for light trucks.

{| border=1 style=&quot;margin:auto;&quot;
!VIN
!Description
|-
|1 &lt;br&gt; (following A)||Chevrolet HHR LS ('06-'07)
|-
|2 &lt;br&gt; (following A)||Chevrolet HHR LT ('06-'07)
|-
|3 &lt;br&gt; (following A)||Chevrolet HHR LT ('07)
|-
|1 &lt;br&gt; (following A)||Chevrolet HHR LS w/auto. trans. ('08-'09)
|-
|2 &lt;br&gt; (following A)||Chevrolet HHR 1LT w/auto. trans. ('08-'09)
|-
|3 &lt;br&gt; (following A)||Chevrolet HHR LS w/man. trans. ('08-'09)
|-
|4 &lt;br&gt; (following A)||Chevrolet HHR 1LT w/man. trans. ('08-'09)
|-
|5 &lt;br&gt; (following A)||Chevrolet HHR 2LT (all transmissions) ('08-'09)
|-
|6 &lt;br&gt; (following A)||Chevrolet HHR SS w/auto. trans. ('08-'09) (Pos. 1-3 of VIN is 3GN)
|-
|7 &lt;br&gt; (following A)||Chevrolet HHR SS w/man. trans. ('08-'09) (Pos. 1-3 of VIN is 3GN)
|-
|6 &lt;br&gt; (following A)||Chevrolet HHR Panel SS w/auto. trans. ('09) (Pos. 1-3 of VIN is 3GC)
|-
|7 &lt;br&gt; (following A)||Chevrolet HHR Panel SS w/man. trans. ('09) (Pos. 1-3 of VIN is 3GC)
|-
|8 &lt;br&gt; (following A)||Chevrolet HHR Panel LS w/auto. trans. ('08-'09) (Pos. 1-3 of VIN is 3GC)
|-
|9 &lt;br&gt; (following A)||Chevrolet HHR Panel LS w/man. trans. ('08-'09) (Pos. 1-3 of VIN is 3GC)
|-
|0 &lt;br&gt; (following A)||Chevrolet HHR Panel LT (all transmissions) ('08-'09) (Pos. 1-3 of VIN is 3GC)
|-
|1 &lt;br&gt; (following A)||Chevrolet HHR Panel LS ('08) (Pos. 1-3 of VIN is 3GC)
|-
|2 &lt;br&gt; (following A)||Chevrolet HHR Panel LT ('08) (Pos. 1-3 of VIN is 3GC)
|-
|3 &lt;br&gt; (following A)||Chevrolet HHR Panel LT ('08) (Pos. 1-3 of VIN is 3GC)
|-
|0 &lt;br&gt; (following V)||Chevrolet Venture Plus ('05) (Pos. 8 of VIN is E)
|-
|1 &lt;br&gt; (following V)||Chevrolet Venture Cargo ('05) (Pos. 8 of VIN is E)
|-
|2 &lt;br&gt; (following V)||Chevrolet Venture LS ('05) (Pos. 8 of VIN is E)
|-
|3 &lt;br&gt; (following V)||Chevrolet Venture LT ('05) (Pos. 8 of VIN is E)
|-
|2 &lt;br&gt; (following U)||Chevrolet Uplander LS SWB 2wd ('06-'08)
|-
|0 &lt;br&gt; (following V)||Chevrolet Uplander Base model 2wd ('05)
|-
|1 &lt;br&gt; (following V)||Chevrolet Uplander Cargo Van 2wd, Mobility (incomplete vehicle) 2wd ('05-'08)
|-
|2 &lt;br&gt; (following V)||Chevrolet Uplander LS 2wd ('05-'08)
|-
|3 &lt;br&gt; (following V)||Chevrolet Uplander LT 2wd ('05-'08)
|-
|3 &lt;br&gt; (following X)||Chevrolet Uplander LT Awd ('05-'06)
|-
|1 &lt;br&gt; (following M)||Chevrolet Astro 2wd ('00-'05)
|-
|1 &lt;br&gt; (following L)||Chevrolet Astro Awd ('00-'05)
|-
|1 &lt;br&gt; (following G)||Chevrolet Express 1500 series 2wd ('00-'09)
|-
|2 &lt;br&gt; (following G)||Chevrolet Express 2500 series 2wd ('00-'09)
|-
|3 &lt;br&gt; (following G)||Chevrolet Express 3500 series 2wd ('00-'09)
|-
|3 &lt;br&gt; (following G)||When VIN starts with 1GBK: Chevrolet Express 4500 series Cutaway 2wd ('09)
|-
|6 &lt;br&gt; (following G)||Chevrolet Express 1500 series LT 2wd ('01-'02)
|-
|1 &lt;br&gt; (following H)||Chevrolet Express 1500 series Awd ('03-'09)
|-
|2 &lt;br&gt; (following H)||Chevrolet Express 2500 series Awd ('03-'05)
|-
|1 &lt;br&gt; (following E)||Chevrolet Tracker Base model 2wd ('00-'04)
|-
|6 &lt;br&gt; (following E)||Chevrolet Tracker LT 2wd ('01-'04)
|-
|1 &lt;br&gt; (following J)||Chevrolet Tracker Base model 4wd ('00-'01, '04)
|-
|1 &lt;br&gt; (following J)||Chevrolet Tracker Base model w/1SB (Preferred) Equip. Group 4wd ('02-'03)
|-
|2 &lt;br&gt; (following J)||Chevrolet Tracker Base model w/1SA (Base) Equip. Group 4wd ('02-'03)
|-
|6 &lt;br&gt; (following J)||Chevrolet Tracker LT 4wd ('01-'04)
|-
|7 &lt;br&gt; (following J)||Chevrolet Tracker ZR2 4wd ('01-'04)
|-
|1 &lt;br&gt; (following L)||Chevrolet Equinox LS 2wd ('05-'09)
|-
|2 &lt;br&gt; (following L)||Chevrolet Equinox LS Awd ('05-'09)
|-
|6 &lt;br&gt; (following L)||Chevrolet Equinox LT 2wd ('05-'07)
|-
|7 &lt;br&gt; (following L)||Chevrolet Equinox LT Awd ('05-'07)
|-
|3 &lt;br&gt; (following L)||Chevrolet Equinox 1LT 2wd ('08-'09)
|-
|4 &lt;br&gt; (following L)||Chevrolet Equinox 1LT Awd ('08-'09)
|-
|5 &lt;br&gt; (following L)||Chevrolet Equinox 2LT 2wd ('08-'09)
|-
|6 &lt;br&gt; (following L)||Chevrolet Equinox 2LT Awd ('08-'09)
|-
|7 &lt;br&gt; (following L)||Chevrolet Equinox LTZ 2wd ('08-'09)
|-
|8 &lt;br&gt; (following L)||Chevrolet Equinox LTZ Awd ('08-'09)
|-
|9 &lt;br&gt; (following L)||Chevrolet Equinox Sport 2wd ('08-'09)
|-
|0 &lt;br&gt; (following L)||Chevrolet Equinox Sport Awd ('08-'09)
|-
|1 &lt;br&gt; (following R)||Chevrolet Traverse LS 2wd ('09)
|-
|2 &lt;br&gt; (following R)||Chevrolet Traverse LT 2wd ('09)
|-
|3 &lt;br&gt; (following R)||Chevrolet Traverse LTZ 2wd ('09)
|-
|1 &lt;br&gt; (following V)||Chevrolet Traverse LS Awd ('09)
|-
|2 &lt;br&gt; (following V)||Chevrolet Traverse LT Awd ('09)
|-
|3 &lt;br&gt; (following V)||Chevrolet Traverse LTZ Awd ('09)
|-
|1 &lt;br&gt; (following S)||Chevrolet Blazer 2wd ('00-'05)
|-
|1 &lt;br&gt; (following T)||Chevrolet Blazer 4wd ('00-'05)
|-
|1 &lt;br&gt; (following S)||Chevrolet Trailblazer 2wd ('02-'08), Trailblazer EXT 2wd ('02-'06)
|-
|1 &lt;br&gt; (following T)||Chevrolet Trailblazer 4wd ('02-'08), Trailblazer EXT 4wd ('02-'06)
|-
|3 &lt;br&gt; (following S)||Chevrolet Trailblazer LT 2wd ('09)
|-
|3 &lt;br&gt; (following T)||Chevrolet Trailblazer LT 4wd ('09)
|-
|5 &lt;br&gt; (following S)||Chevrolet Trailblazer SS 2wd ('09)
|-
|5 &lt;br&gt; (following T)||Chevrolet Trailblazer SS 4wd ('09)
|-
|1 &lt;br&gt; (following C)||Chevrolet Tahoe Limited 2wd ('00) [GMT400; 8th pos. of VIN is R]
|-
|1 &lt;br&gt; (following K)||Chevrolet Tahoe Z71 4wd ('00) [GMT400; 8th pos. of VIN is R]
|-
|1 &lt;br&gt; (following C)||Chevrolet Tahoe 2wd ('00-'06) [GMT800]
|-
|1 &lt;br&gt; (following K)||Chevrolet Tahoe 4wd ('00-'06) [GMT800]
|-
|1 &lt;br&gt; (following C)||Chevrolet Tahoe 2wd ('07-'08) [GMT900]
|-
|0 &lt;br&gt; (following C)||Chevrolet Tahoe Police/Special Service 2wd ('07-'09) [GMT900]
|-
|1 &lt;br&gt; (following C)||Chevrolet Tahoe LS 2wd ('09) [GMT900]
|-
|2 &lt;br&gt; (following C)||Chevrolet Tahoe LT 2wd ('09) [GMT900]
|-
|3 &lt;br&gt; (following C)||Chevrolet Tahoe LTZ 2wd ('09) [GMT900]
|-
|1 &lt;br&gt; (following K)||Chevrolet Tahoe 4wd ('07-'08) [GMT900]
|-
|0 &lt;br&gt; (following K)||Chevrolet Tahoe Police/Special Service 4wd ('07-'09) [GMT900]
|-
|1 &lt;br&gt; (following K)||Chevrolet Tahoe LS 4wd ('09) [GMT900]
|-
|2 &lt;br&gt; (following K)||Chevrolet Tahoe LT 4wd ('09) [GMT900]
|-
|3 &lt;br&gt; (following K)||Chevrolet Tahoe LTZ 4wd ('09) [GMT900]
|-
|1 &lt;br&gt; (following C)||Chevrolet Suburban 1500 series 2wd ('00-'08)
|-
|2 &lt;br&gt; (following C)||Chevrolet Suburban 2500 series 2wd ('00-'08)
|-
|1 &lt;br&gt; (following K)||Chevrolet Suburban 1500 series 4wd ('00-'08)
|-
|2 &lt;br&gt; (following K)||Chevrolet Suburban 2500 series 4wd ('00-'08)
|-
|1 &lt;br&gt; (following C)||Chevrolet Suburban 1500 series LS 2wd ('09)
|-
|2 &lt;br&gt; (following C)||Chevrolet Suburban 1500 series LT 2wd ('09)
|-
|3 &lt;br&gt; (following C)||Chevrolet Suburban 1500 series LTZ 2wd ('09)
|-
|4 &lt;br&gt; (following C)||Chevrolet Suburban 2500 series LS 2wd ('09)
|-
|5 &lt;br&gt; (following C)||Chevrolet Suburban 2500 series LT 2wd ('09)
|-
|1 &lt;br&gt; (following K)||Chevrolet Suburban 1500 series LS 4wd ('09)
|-
|2 &lt;br&gt; (following K)||Chevrolet Suburban 1500 series LT 4wd ('09)
|-
|3 &lt;br&gt; (following K)||Chevrolet Suburban 1500 series LTZ 4wd ('09)
|-
|4 &lt;br&gt; (following K)||Chevrolet Suburban 2500 series LS 4wd ('09)
|-
|5 &lt;br&gt; (following K)||Chevrolet Suburban 2500 series LT 4wd ('09)
|-
|1 &lt;br&gt; (following C)||Chevrolet Avalanche 1500 series 2wd ('02-'08)
|-
|2 &lt;br&gt; (following C)||Chevrolet Avalanche 2500 series 2wd ('02-'03)
|-
|1 &lt;br&gt; (following K)||Chevrolet Avalanche 1500 series 4wd ('02-'08)
|-
|2 &lt;br&gt; (following K)||Chevrolet Avalanche 2500 series 4wd ('02-'06)
|-
|1 &lt;br&gt; (following C)||Chevrolet Avalanche 1500 series LS 2wd ('09)
|-
|2 &lt;br&gt; (following C)||Chevrolet Avalanche 1500 series LT 2wd ('09)
|-
|3 &lt;br&gt; (following C)||Chevrolet Avalanche 1500 series LTZ 2wd ('09)
|-
|1 &lt;br&gt; (following K)||Chevrolet Avalanche 1500 series LS 4wd ('09)
|-
|2 &lt;br&gt; (following K)||Chevrolet Avalanche 1500 series LT 4wd ('09)
|-
|3 &lt;br&gt; (following K)||Chevrolet Avalanche 1500 series LTZ 4wd ('09)
|-
|1 &lt;br&gt; (following S)||Chevrolet SSR 2wd ('03-'06)
|-
|6 &lt;br&gt; (following S)||Chevrolet SSR Signature Series 2wd ('03) &lt;br&gt; [All SSR Signature Series also have a 0 in the 12th pos. of VIN whereas all other SSRs have a 1 in the 12th pos. of VIN]
|-
|1 &lt;br&gt; (following S)||Chevrolet S-10 2wd ('00-'03)
|-
|1 &lt;br&gt; (following T)||Chevrolet S-10 4wd ('00-'04)
|-
|1 &lt;br&gt; (following S)||Chevrolet Colorado 2wd ('04-'07)
|-
|1 &lt;br&gt; (following T)||Chevrolet Colorado 4wd ('04-'07)
|-
|1 &lt;br&gt; (following C)||Chevrolet Silverado 1500 2wd ('00-'06), Silverado Classic 1500 2wd ('07) [GMT800]
|-
|1 &lt;br&gt; (following K)||Chevrolet Silverado 1500 4wd ('00-'06), Silverado Classic 1500 4wd ('07) [GMT800]
|-
|1 &lt;br&gt; (following C)||Chevrolet Silverado 1500HD 2wd ('01-'03, '05-'06), Silverado Classic 1500HD 2wd ('07) [GMT800] (Pos. 8 of VIN is U]
|-
|1 &lt;br&gt; (following K)||Chevrolet Silverado 1500HD 4wd ('01-'03, '05-'06), Silverado Classic 1500HD 2wd ('07) [GMT800] (Pos. 8 of VIN is U]
|-
|2 &lt;br&gt; (following C)||Chevrolet Silverado 2500 2wd ('00) [GMT800] (Pos. 8 of VIN is T or U]
|-
|2 &lt;br&gt; (following K)||Chevrolet Silverado 2500 4wd ('00) [GMT800] (Pos. 8 of VIN is U]
|-
|2 &lt;br&gt; (following C)||Chevrolet C2500 2wd ('00) [GMT400] (Pos. 8 of VIN is F, J, or R)
|-
|3 &lt;br&gt; (following C)||Chevrolet C3500 2wd ('00) [GMT400] (Pos. 8 of VIN is F, J, or R)
|-
|3 &lt;br&gt; (following C)||when 4th pos. of VIN is K: Chevrolet C3500HD 2wd ('00-'02) [GMT400]
|-
|2 &lt;br&gt; (following K)||Chevrolet K2500 4wd ('00) [GMT400] (Pos. 8 of VIN is F, J, or R)
|-
|3 &lt;br&gt; (following K)||Chevrolet K3500 4wd ('00) [GMT400] (Pos. 8 of VIN is F, J, or R)
|-
|2 &lt;br&gt; (following C)||Chevrolet Silverado 2500 2wd ('01-'06), Silverado Classic 2500 2wd ('07) (Pos. 8 of VIN is D, G, or U) [GMT800]
|-
|2 &lt;br&gt; (following K)||Chevrolet Silverado 2500 4wd ('01-'06), Silverado Classic 2500 4wd ('07) (Pos. 8 of VIN is D, G, or U) [GMT800]
|-
|3 &lt;br&gt; (following C)||Chevrolet Silverado 3500 2wd ('01-'06), Silverado Classic 3500 2wd ('07) (Pos. 8 of VIN is D, G, or U) [GMT800]
|-
|3 &lt;br&gt; (following K)||Chevrolet Silverado 3500 4wd ('01-'06), Silverado Classic 3500 4wd ('07) (Pos. 8 of VIN is D, G, or U) [GMT800]
|-
|1 &lt;br&gt; (following C)||Chevrolet Silverado 1500 2wd ('07-'08) [GMT900]
|-
|1 &lt;br&gt; (following K)||Chevrolet Silverado 1500 4wd ('07-'08) [GMT900]
|-
|2 &lt;br&gt; (following C)||Chevrolet Silverado 2500 2wd ('07-'08) [GMT900]
|-
|2 &lt;br&gt; (following K)||Chevrolet Silverado 2500 4wd ('07-'08) [GMT900]
|-
|3 &lt;br&gt; (following C)||Chevrolet Silverado 3500 2wd ('07-'08) [GMT900]
|-
|3 &lt;br&gt; (following K)||Chevrolet Silverado 3500 4wd ('07-'08) [GMT900]
|-
|1 &lt;br&gt; (following V)||Pontiac Montana Mobility (incomplete vehicle) 2wd ('05) (Pos. 8 of VIN is E)
|-
|2 &lt;br&gt; (following V)||Pontiac Montana ('05) (Pos. 8 of VIN is E)
|-
|0 &lt;br&gt; (following V)||Pontiac Montana SV6 1SA 2wd ('05)
|-
|3 &lt;br&gt; (following V)||Pontiac Montana SV6 1SB 2wd ('05)
|-
|2 &lt;br&gt; (following X)||Pontiac Montana SV6 1SA Awd ('05)
|-
|3 &lt;br&gt; (following X)||Pontiac Montana SV6 1SB Awd ('05)
|-
|1 &lt;br&gt; (following V)||Pontiac Montana SV6 Mobility (incomplete vehicle) 2wd ('06)
|-
|3 &lt;br&gt; (following V)||Pontiac Montana SV6 2wd ('06)
|-
|3 &lt;br&gt; (following X)||Pontiac Montana SV6 Awd ('06)
|-
|0 &lt;br&gt; (following A)||Pontiac Aztek 2wd ('01-'05)
|-
|0 &lt;br&gt; (following B)||Pontiac Aztek Awd ('01-'05)
|-
|6 &lt;br&gt; (following L)||Pontiac Torrent 2wd ('06-'07)
|-
|7 &lt;br&gt; (following L)||Pontiac Torrent Awd ('06-'07)
|-
|3 &lt;br&gt; (following L)||Pontiac Torrent Base model 2wd ('08-'09)
|-
|4 &lt;br&gt; (following L)||Pontiac Torrent Base model Awd ('08-'09)
|-
|5 &lt;br&gt; (following L)||Pontiac Torrent GXP 2wd ('08-'09)
|-
|6 &lt;br&gt; (following L)||Pontiac Torrent GXP Awd ('08-'09)
|-
|0 &lt;br&gt; (following X)||Oldsmobile Silhouette extended length GL 2wd ('00, '03-'04), GLS 2wd ('00-'04)
|-
|1 &lt;br&gt; (following X)||Oldsmobile Silhouette extended length Premiere 2wd ('00-'04)
|-
|2 &lt;br&gt; (following X)||Oldsmobile Silhouette extended length GL 2wd ('01-'02)
|-
|0 &lt;br&gt; (following V)||Oldsmobile Silhouette extended length GLS Awd ('02-'04)
|-
|1 &lt;br&gt; (following V)||Oldsmobile Silhouette extended length Premiere Awd ('02-'04)
|-
|1 &lt;br&gt; (following S)||Oldsmobile Bravada 2wd ('02-'04)
|-
|1 &lt;br&gt; (following T)||Oldsmobile Bravada 4wd ('00-'04)
|-
|1 &lt;br&gt; (following V)||Buick Terraza Mobility (incomplete vehicle) 2wd ('05-'07)
|-
|2 &lt;br&gt; (following V)||Buick Terraza CX 2wd ('05-'07), CX Plus 2wd ('07)
|-
|3 &lt;br&gt; (following V)||Buick Terraza CXL 2wd ('05-'07)
|-
|2 &lt;br&gt; (following X)||Buick Terraza CX Awd ('05-'06)
|-
|3 &lt;br&gt; (following X)||Buick Terraza CXL Awd ('05-'06)
|-
|0 &lt;br&gt; (following A)||Buick Rendezvous 2wd ('02-'07)
|-
|0 &lt;br&gt; (following B)||Buick Rendezvous Awd ('02-'06)
|-
|1 &lt;br&gt; (following S)||Buick Rainier 2wd ('04-'07)
|-
|1 &lt;br&gt; (following T)||Buick Rainier 4wd ('04-'06)
|-
|1 &lt;br&gt; (following R)||Buick Enclave CX 2wd ('08-'09)
|-
|2 &lt;br&gt; (following R)||Buick Enclave CXL 2wd ('08-'09)
|-
|1 &lt;br&gt; (following V)||Buick Enclave CX Awd ('08-'09)
|-
|2 &lt;br&gt; (following V)||Buick Enclave CXL Awd ('08-'09)
|-
|9 &lt;br&gt; (following H)|| Cadillac Commercial Chassis for Limousine or Hearse based on DeVille ('00-'01)
|-
|0 &lt;br&gt; (following H)|| Cadillac Commercial Chassis for Hearse based on DeVille ('02-'05) or DTS ('06-'09)
|-
|9 &lt;br&gt; (following H)|| Cadillac Professional Chassis for Limousine based on DeVille ('02-'05) or DTS ('06-'07)
|-
|9 &lt;br&gt; (following K)|| Cadillac Professional Chassis for Limousine based on DTS ('08-'09)
|-
|6 &lt;br&gt; (following E)||Cadillac SRX ('04-'07)
|-
|2 &lt;br&gt; (following E)||Cadillac SRX RWD V8 ('08-'09)
|-
|4 &lt;br&gt; (following E)||Cadillac SRX AWD V6 ('08-'09)
|-
|5 &lt;br&gt; (following E)||Cadillac SRX AWD V8 ('08-'09)
|-
|6 &lt;br&gt; (following E)||When Pos. 8 of VIN is 7: Cadillac SRX RWD V6 ('08)
|-
|6 &lt;br&gt; (following E)||When Pos. 8 of VIN is A: Cadillac SRX AWD V8 ('08)
|-
|6 &lt;br&gt; (following E)||Cadillac SRX RWD V6 ('09)
|-
|1 &lt;br&gt; (following K)||Cadillac Escalade 4wd (Early '00)
|-
|4 &lt;br&gt; (following K)||Cadillac Escalade Platinum Edition 4wd ('08), Escalade ESV Platinum Edition 4wd ('08)
|-
|6 &lt;br&gt; (following C)||Cadillac Escalade 2wd ('02-'08), Escalade ESV 2wd ('08)
|-
|6 &lt;br&gt; (following K)||Cadillac Escalade 4wd (Mid '00, '02-'08), Escalade ESV 4wd ('03-'08), Escalade EXT 4wd ('02-'08)
|-
|1 &lt;br&gt; (following C)||Cadillac Escalade 2wd Base model ('09), Escalade ESV 2wd Base model ('09)
|-
|2 &lt;br&gt; (following C)||Cadillac Escalade 2wd w/Ultra Luxury Collection ('09), Escalade ESV 2wd w/Ultra Luxury Collection ('09)
|-
|3 &lt;br&gt; (following C)||Cadillac Escalade 2wd w/Platinum Edition ('09), Escalade ESV 2wd w/Platinum Edition ('09)
|-
|4 &lt;br&gt; (following C)||Cadillac Escalade Hybrid 2wd Base model ('09)
|-
|5 &lt;br&gt; (following C)||Cadillac Escalade 2wd w/Sport Package ('09), Escalade ESV 4wd w/Sport Package ('09)
|-
|1 &lt;br&gt; (following K)||Cadillac Escalade 4wd Base model ('09), Escalade ESV 4wd Base model ('09), Escalade EXT 4wd Base model ('09)
|-
|2 &lt;br&gt; (following K)||Cadillac Escalade 4wd w/Ultra Luxury Collection ('09), Escalade ESV 4wd w/Ultra Luxury Collection ('09),&lt;br&gt; Escalade EXT 4wd w/Ultra Luxury Collection ('09)
|-
|3 &lt;br&gt; (following K)||Cadillac Escalade 4wd w/Platinum Edition ('09), Escalade ESV 4wd w/Platinum Edition ('09)
|-
|4 &lt;br&gt; (following K)||Cadillac Escalade Hybrid 4wd Base model ('09)
|-
|5 &lt;br&gt; (following K)||Cadillac Escalade 4wd w/Sport Package ('09), Escalade ESV 4wd w/Sport Package ('09), Escalade EXT 4wd w/Sport Package ('09)
|-
|1 &lt;br&gt; (following M)||GMC Safari 2wd ('00-'05)
|-
|1 &lt;br&gt; (following L)||GMC Safari Awd ('00-'05)
|-
|1 &lt;br&gt; (following G)||GMC Savana 1500 series 2wd ('00-'09)
|-
|2 &lt;br&gt; (following G)||GMC Savana 2500 series 2wd ('00-'09)
|-
|3 &lt;br&gt; (following G)||GMC Savana 3500 series 2wd ('00-'09)
|-
|3 &lt;br&gt; (following G)||When VIN starts with 1GBK: GMC Savana 4500 series Cutaway 2wd ('09)
|-
|6 &lt;br&gt; (following G)||GMC Savana 1500 series SLT 2wd ('01-'02)
|-
|1 &lt;br&gt; (following H)||GMC Savana 1500 series Awd ('03-'09)
|-
|2 &lt;br&gt; (following H)||GMC Savana 2500 series Awd ('03-'05)
|-
|1 &lt;br&gt; (following R)||GMC Acadia SLE 2wd ('07-'09)
|-
|2 &lt;br&gt; (following R)||GMC Acadia SLT-1 2wd ('07-'09)
|-
|3 &lt;br&gt; (following R)||GMC Acadia SLT-2 2wd ('07-'09)
|-
|1 &lt;br&gt; (following V)||GMC Acadia SLE Awd ('07-'09)
|-
|2 &lt;br&gt; (following V)||GMC Acadia SLT-1 Awd ('07-'09)
|-
|3 &lt;br&gt; (following V)||GMC Acadia SLT-2 Awd ('07-'09)
|-
|1 &lt;br&gt; (following S)||GMC Jimmy 2wd ('00-'01)
|-
|6 &lt;br&gt; (following S)||GMC Jimmy Diamond Edition 2wd ('01)
|-
|1 &lt;br&gt; (following T)||GMC Jimmy 4wd ('00-'01 &amp; '02-'05 in Canada)
|-
|6 &lt;br&gt; (following T)||GMC Jimmy Diamond Edition 4wd ('01)
|-
|1 &lt;br&gt; (following S)||GMC Envoy 2wd ('02-'08), Envoy XL 2wd ('02-'06), Envoy XUV 2wd ('04-'05)
|-
|6 &lt;br&gt; (following S)||GMC Envoy Denali 2wd ('05-'08), Envoy XL Denali 2wd ('05-'06)
|-
|1 &lt;br&gt; (following T)||GMC Envoy 4wd ('02-'08), Envoy XL 4wd ('02-'06), Envoy XUV 4wd ('04-'05)
|-
|6 &lt;br&gt; (following T)||GMC Envoy Denali 4wd ('05-'08), Envoy XL Denali 4wd ('05-'06)
|-
|3 &lt;br&gt; (following S)||GMC Envoy SLE 2wd ('09)
|-
|3 &lt;br&gt; (following T)||GMC Envoy SLE 4wd ('09)
|-
|4 &lt;br&gt; (following S)||GMC Envoy SLT 2wd ('09)
|-
|4 &lt;br&gt; (following T)||GMC Envoy SLT 4wd ('09)
|-
|5 &lt;br&gt; (following S)||GMC Envoy Denali 2wd ('09)
|-
|5 &lt;br&gt; (following T)||GMC Envoy Denali 4wd ('09)
|-
|1 &lt;br&gt; (following C)||GMC Yukon 2wd ('00-'06) [GMT800]
|-
|1 &lt;br&gt; (following K)||GMC Yukon 4wd ('00-'06) [GMT800]
|-
|1 &lt;br&gt; (following C)||GMC Yukon 2wd ('07-'08) [GMT900]
|-
|1 &lt;br&gt; (following K)||GMC Yukon 4wd ('07-'08) [GMT900]
|-
|1 &lt;br&gt; (following C)||GMC Yukon 2wd ('09) [GMT900]
|-
|1 &lt;br&gt; (following K)||GMC Yukon 4wd ('09) [GMT900]
|-
|1 &lt;br&gt; (following C)||GMC Yukon Hybrid 2wd ('09) [GMT900; 8th pos. of VIN is 5]
|-
|1 &lt;br&gt; (following K)||GMC Yukon Hybrid 4wd ('09) [GMT900; 8th pos. of VIN is 5]
|-
|2 &lt;br&gt; (following C)||GMC Yukon SLE 2wd ('09) [GMT900]
|-
|3 &lt;br&gt; (following C)||GMC Yukon SLT 2wd ('09) [GMT900]
|-
|2 &lt;br&gt; (following K)||GMC Yukon SLE 4wd ('09) [GMT900]
|-
|3 &lt;br&gt; (following K)||GMC Yukon SLT 4wd ('09) [GMT900]
|-
|1 &lt;br&gt; (following K)||GMC Yukon Denali 4wd (Early '00) [GMT400; 8th pos. of VIN is R]
|-
|6 &lt;br&gt; (following K)||GMC Yukon Denali 4wd (Mid '00) [GMT400; 8th pos. of VIN is R]
|-
|6 &lt;br&gt; (following K)||GMC Yukon Denali 4wd ('01-'06) [GMT800]
|-
|6 &lt;br&gt; (following C)||GMC Yukon Denali 2wd ('08) [GMT900]
|-
|6 &lt;br&gt; (following K)||GMC Yukon Denali 4wd ('07-'08) [GMT900]
|-
|0 &lt;br&gt; (following C)||GMC Yukon Denali 2wd ('09) [GMT900]
|-
|0 &lt;br&gt; (following K)||GMC Yukon Denali 4wd ('09) [GMT900]
|-
|1 &lt;br&gt; (following K)||GMC Yukon Denali 4wd ('09) [GMT900; 8th pos. of VIN is 2]
|-
|1 &lt;br&gt; (following C)||GMC Yukon Denali Hybrid 2wd ('09) [GMT900; 8th pos. of VIN is 5]
|-
|1 &lt;br&gt; (following K)||GMC Yukon Denali Hybrid 4wd ('09) [GMT900; 8th pos. of VIN is 5]
|-
|1 &lt;br&gt; (following C)||GMC Yukon XL 1500 series 2wd ('00-'08)
|-
|2 &lt;br&gt; (following C)||GMC Yukon XL 2500 series 2wd ('00-'08)
|-
|6 &lt;br&gt; (following C)||GMC Yukon XL Denali 1500 series 2wd ('08)
|-
|1 &lt;br&gt; (following K)||GMC Yukon XL 1500 series 4wd ('00-'08)
|-
|2 &lt;br&gt; (following K)||GMC Yukon XL 2500 series 4wd ('00-'08)
|-
|6 &lt;br&gt; (following K)||GMC Yukon XL Denali 1500 series 4wd ('01-'08)
|-
|1 &lt;br&gt; (following C)||GMC Yukon XL 1500 series 2wd ('09)
|-
|2 &lt;br&gt; (following C)||GMC Yukon XL 1500 series SLE 2wd ('09)
|-
|3 &lt;br&gt; (following C)||GMC Yukon XL 1500 series SLT 2wd ('09)
|-
|4 &lt;br&gt; (following C)||GMC Yukon XL 2500 series 2wd ('09)
|-
|5 &lt;br&gt; (following C)||GMC Yukon XL 2500 series SLE 2wd ('09)
|-
|6 &lt;br&gt; (following C)||GMC Yukon XL 2500 series SLT 2wd ('09)
|-
|0 &lt;br&gt; (following C)||GMC Yukon XL Denali 1500 series 2wd ('09)
|-
|1 &lt;br&gt; (following K)||GMC Yukon XL 1500 series 4wd ('09)
|-
|2 &lt;br&gt; (following K)||GMC Yukon XL 1500 series SLE 4wd ('09)
|-
|3 &lt;br&gt; (following K)||GMC Yukon XL 1500 series SLT 4wd ('09)
|-
|4 &lt;br&gt; (following K)||GMC Yukon XL 2500 series 4wd ('09)
|-
|5 &lt;br&gt; (following K)||GMC Yukon XL 2500 series SLE 4wd ('09)
|-
|6 &lt;br&gt; (following K)||GMC Yukon XL 2500 series SLT 4wd ('09)
|-
|0 &lt;br&gt; (following K)||GMC Yukon XL Denali 1500 series 4wd ('09)
|-
|1 &lt;br&gt; (following K)||GMC Yukon XL Denali 1500 series 4wd ('09) [8th pos. of VIN is 2]
|-
|1 &lt;br&gt; (following S)||GMC Sonoma 2wd ('00-'03)
|-
|1 &lt;br&gt; (following T)||GMC Sonoma 4wd ('00-'04)
|-
|1 &lt;br&gt; (following S)||GMC Canyon 2wd ('04-'07)
|-
|1 &lt;br&gt; (following T)||GMC Canyon 4wd ('04-'07)
|-
|1 &lt;br&gt; (following C)||GMC Sierra 1500 2wd ('00-'06), Sierra Classic 1500 2wd ('07) (Pos. 8 of VIN is X, V, T, Z, or N] [GMT800]
|-
|1 &lt;br&gt; (following K)||GMC Sierra 1500 4wd ('00-'06), Sierra Classic 1500 4wd ('07) (Pos. 8 of VIN is X, V, T, Z, B, or N] [GMT800]
|-
|1 &lt;br&gt; (following C)||GMC Sierra 1500HD 2wd ('01-'03, '05-'06), Sierra Classic 1500HD 2wd ('07) (Pos. 8 of VIN is U] [GMT800]
|-
|1 &lt;br&gt; (following K)||GMC Sierra 1500HD 4wd ('01-'03, '05-'06), Sierra Classic 1500HD 2wd ('07) (Pos. 8 of VIN is U] [GMT800]
|-
|6 &lt;br&gt; (following K)||GMC Sierra C3 1500 Awd ('01) [GMT800]
|-
|6 &lt;br&gt; (following K)||GMC Sierra Denali 1500 Awd ('02-'06), Sierra Classic Denali 1500 Awd ('07) (Pos. 8 of VIN is N] [GMT800]
|-
|2 &lt;br&gt; (following C)||GMC Sierra 2500 2wd ('00) [GMT800] (Pos. 8 of VIN is T or U]
|-
|2 &lt;br&gt; (following K)||GMC Sierra 2500 4wd ('00) [GMT800] (Pos. 8 of VIN is U]
|-
|2 &lt;br&gt; (following C)||GMC Sierra Classic C2500 2wd ('00) [GMT400] (Pos. 8 of VIN is F, J, or R)
|-
|3 &lt;br&gt; (following C)||GMC Sierra Classic C3500 2wd ('00) [GMT400] (Pos. 8 of VIN is F, J, or R)
|-
|3 &lt;br&gt; (following C)||when 4th pos. of VIN is K: GMC Sierra C3500HD 2wd ('00-'02) [GMT400]
|-
|2 &lt;br&gt; (following K)||GMC Sierra Classic K2500 4wd ('00) [GMT400] (Pos. 8 of VIN is F, J, or R)
|-
|3 &lt;br&gt; (following K)||GMC Sierra Classic K3500 4wd ('00) [GMT400] (Pos. 8 of VIN is F, J, or R)
|-
|2 &lt;br&gt; (following C)||GMC Sierra 2500 2wd ('01-'06), Sierra Classic 2500 2wd ('07) (Pos. 8 of VIN is D, G, or U) [GMT800]
|-
|2 &lt;br&gt; (following K)||GMC Sierra 2500 4wd ('01-'06), Sierra Classic 2500 4wd ('07) (Pos. 8 of VIN is D, G, or U) [GMT800]
|-
|3 &lt;br&gt; (following C)||GMC Sierra 3500 2wd ('01-'06), Sierra Classic 3500 2wd ('07) (Pos. 8 of VIN is D, G, or U) [GMT800]
|-
|3 &lt;br&gt; (following K)||GMC Sierra 3500 4wd ('01-'06), Sierra Classic 3500 4wd ('07) (Pos. 8 of VIN is D, G, or U) [GMT800]
|-
|1 &lt;br&gt; (following C)||GMC Sierra 1500 2wd ('07-'08) (Pos. 8 of VIN is X, C, J, 0) [GMT900]
|-
|6 &lt;br&gt; (following C)||GMC Sierra Denali 1500 2wd ('07-'08) (Pos. 8 of VIN is 8) [GMT900]
|-
|1 &lt;br&gt; (following K)||GMC Sierra 1500 4wd ('07-'08) (Pos. 8 of VIN is X, C, M, 3) [GMT900]
|-
|6 &lt;br&gt; (following K)||GMC Sierra Denali 1500 Awd ('07-'08) (Pos. 8 of VIN is 8) [GMT900]
|-
|2 &lt;br&gt; (following C)||GMC Sierra 2500 2wd ('07-'08) [GMT900]
|-
|2 &lt;br&gt; (following K)||GMC Sierra 2500 4wd ('07-'08) [GMT900]
|-
|3 &lt;br&gt; (following C)||GMC Sierra 3500 2wd ('07-'08) [GMT900]
|-
|3 &lt;br&gt; (following K)||GMC Sierra 3500 4wd ('07-'08) [GMT900]
|-
|0 &lt;br&gt; (following V)||Saturn Relay ''2'' 2wd ('05-'07)
|-
|2 &lt;br&gt; (following V)||Saturn Relay ''3'' 2wd ('05-'07)
|-
|5 &lt;br&gt; (following V)||Saturn Relay ''1'' 2wd ('07)
|-
|2 &lt;br&gt; (following X)||Saturn Relay ''3'' Awd ('05-'06)
|-
|2 &lt;br&gt; (following Z)||Saturn Vue I4, Man. Trans., Fwd ('02-'07)
|-
|3 &lt;br&gt; (following Z)||Saturn Vue I4, Auto. Trans., Fwd ('02-'07)
|-
|4 &lt;br&gt; (following Z)||Saturn Vue I4, Auto. Trans., Awd ('02-'05)
|-
|5 &lt;br&gt; (following Z)||Saturn Vue V6, Auto. Trans., Fwd ('03-'07)
|-
|6 &lt;br&gt; (following Z)||Saturn Vue V6, Auto. Trans., Awd ('02-'07)
|-
|3 &lt;br&gt; (following L)||Saturn Vue XE Fwd ('08-'09)
|-
|4 &lt;br&gt; (following L)||Saturn Vue XE Awd ('08-'09)
|-
|5 &lt;br&gt; (following L)||when 4th pos. of VIN is C: Saturn Vue XR Fwd ('08-'09)
|-
|7 &lt;br&gt; (following L)||Saturn Vue XR Awd (Early '08)
|-
|6 &lt;br&gt; (following L)||Saturn Vue XR Awd (Mid '08-'09)
|-
|5 &lt;br&gt; (following L)||when 4th pos. of VIN is D: Saturn Vue XR Awd ('09)
|-
|1 &lt;br&gt; (following L)||Saturn Vue Red Line Fwd ('08-'09)
|-
|9 &lt;br&gt; (following L)||Saturn Vue Red Line Awd ('08)
|-
|0 &lt;br&gt; (following L)||Saturn Vue Red Line Awd ('09)
|-
|0 &lt;br&gt; (following L)||Saturn Vue Green Line Fwd ('08)
|-
|9 &lt;br&gt; (following L)||Saturn Vue Green Line Fwd ('09)
|-
|1 &lt;br&gt; (following R)||Saturn Outlook XE 2wd ('07-'09)
|-
|2 &lt;br&gt; (following R)||Saturn Outlook XR 2wd ('07-'09)
|-
|3 &lt;br&gt; (following R)||Saturn Outlook XR 2wd w/Touring Package ('07-'09)
|-
|1 &lt;br&gt; (following V)||Saturn Outlook XE Awd ('07-'09)
|-
|2 &lt;br&gt; (following V)||Saturn Outlook XR Awd ('07-'09)
|-
|3 &lt;br&gt; (following V)||Saturn Outlook XR Awd w/Touring Package ('07-'09)
|-
|1 &lt;br&gt; (following N)||Hummer H3 ('06-'07)
|-
|1 &lt;br&gt; (following N)||Hummer H3 Base model ('08)
|-
|3 &lt;br&gt; (following N)||Hummer H3 Adventure ('08)
|-
|4 &lt;br&gt; (following N)||Hummer H3 Luxury ('08)
|-
|5 &lt;br&gt; (following N)||Hummer H3 X ('08)
|-
|6 &lt;br&gt; (following N)||Hummer H3 Alpha ('08)
|-
|1 &lt;br&gt; (following N)||Hummer H3, H3T ('09)
|-
|2 &lt;br&gt; (following N)||Hummer H2 ('03-'08), H2 SUT ('05-'08)
|-
|2 &lt;br&gt; (following N)||Hummer H2 Base model ('09), H2 SUT Base model ('09)
|-
|7 &lt;br&gt; (following N)||Hummer H2 Adventure ('09)
|-
|8 &lt;br&gt; (following N)||Hummer H2 Luxury ('09)
|-
|9 &lt;br&gt; (following N)||Hummer H2 SUT Adventure ('09)
|-
|0 &lt;br&gt; (following N)||Hummer H2 SUT Luxury ('09)
|-
|1 (following S)||Isuzu Hombre 2wd ('00), Isuzu i280 2wd ('06), Isuzu i290 2wd ('07-'08), Isuzu i370 2wd ('07-'08)
|-
|2 (following S)||Isuzu i290 2wd w/Preferred Equip. Pkg. ('08), Isuzu i370 2wd w/Comfort Pkg. or upgrade model ('08)
|-
|1 (following T)||Isuzu Hombre 4wd ('00), Isuzu i350 4wd ('06), Isuzu i370 4wd ('07-'08)
|-
|2 (following T)||Isuzu i370 4wd w/Comfort Pkg. ('08)
|-
|1 (following S)||Isuzu Ascender 2wd ('03-'08)
|-
|1 (following T)||Isuzu Ascender 4wd ('03-'08)
|-
|1 (following T)||Saab 9-7X ('05-'08: All, '09: 4.2i, 5.3i)
|-
|2 (following T)||Saab 9-7X Aero ('09)
|}

====Body style codes 1981-2009 Light Duty Truck &amp; Multi-Purpose Passenger Vehicle====
The Body type is specified as character 7 of the American GM VIN for light trucks.

{| border=1 style=&quot;margin:auto;&quot;
!VIN
!Description
|-
|0||Sedan Pickup/Pickup Delivery ('81-'87 El Camino, Caballero)
|-
|0||Cadillac, Buick, Chevrolet Commercial Body/Chassis
|-
|0||Chassis Only
|-
|1||Cutaway Van
|-
|2||Forward Control ('81-'03) (includes '93-'95 Chevy G30HD/GMC G3500HD)
|-
|2||Sport Utility Truck (SUT) ('04-'09 Avalanche &amp; Escalade EXT, '04-'05 Envoy XUV, '05-'09 Hummer H2 SUT)
|-
|3||Four-Door Cab pickup (Crew Cab) (includes '06-'08 Isuzu i-Series Crew Cab, '09 Hummer H3T)
|-
|3||4-door Passenger Minivan ('97-'09 U-bodies)
|-
|3||4-door SUV or MPV ('06-'09 HHR) (also includes '02-'03 Avalanche &amp; Escalade EXT) ('05-'09 Saab 9-7X)
|-
|4||Two-Door Cab pickup (includes '83-'87 S-10/S-15 extended cab pickups, '03-'06 Chevy SSR, '96-'00 Isuzu Hombre Reg. Cab)
|-
|5||Van (Astro/Safari &amp; full-size vans &amp; '07-'09 HHR Panel)
|-
|6||Extended length 4-door SUV (Suburban, Yukon XL, Escalade ESV, Trailblazer EXT, Envoy XL, Isuzu Ascender 7-psgr.)
|-
|6||3-door Passenger Minivan ('90-'99 U-bodies)
|-
|7||Motor Home Chassis ('81-'09)
|-
|8||Two-Door SUV (Utility) (2-d Tracker, S-10 Blazer, S-15 Jimmy, Blazer, Jimmy, Tahoe, Yukon)
|-
|9||Stake (81-87)
|-
|9||Extended Cab pickup ('88-) (includes '97-'00 Isuzu Hombre Spacecab, '06-'08 Isuzu i-Series Ext. Cab)
|-
|9||Extended length van ('90-) (Astro/Safari &amp; full-size vans)
|}

===American VIN format 2010- Light Duty Truck &amp; Multi-Purpose Passenger Vehicle===
GM's VIN format is as follows:

&lt;table border=1 style=&quot;margin:auto;&quot;&gt;
&lt;tr&gt;
&lt;th&gt;Position&lt;/th&gt;
&lt;th&gt;Sample&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;Description&lt;/th&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;1&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td rowspan=3&gt;[[#GM WMIs|World Manufacturer Identifier]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;G&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;K&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;L&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[#GVWR/Brake System/Body Style 2010- Light Duty Truck &amp; Multi-Purpose Passenger Vehicle|GVWR/Brake System/Body Style 2010-]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;5&lt;/td&gt;
&lt;td&gt;R&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[#Line &amp; Chassis Type 2010- Light Duty Truck &amp; Multi-Purpose Passenger Vehicle|Line &amp; Chassis Type for 2010-]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;6&lt;/td&gt;
&lt;td&gt;L&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[#Series 2010- Light Duty Truck &amp; Multi-Purpose Passenger Vehicle|Series 2010- Light Duty Truck &amp; Multi-Purpose Passenger Vehicle]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;7&lt;/td&gt;
&lt;td&gt;E&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[#Restraint codes for light trucks 2010-|Restraint type]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;8&lt;/td&gt;
&lt;td&gt;D&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[#Engine codes for light trucks|Engine type]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;9&lt;/td&gt;
&lt;td&gt;0&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[Vehicle Identification Numbers (VIN codes)/Check digit |Check digit]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;10&lt;/td&gt;
&lt;td&gt;A&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[Vehicle Identification Numbers (VIN codes)/Model year|Model year]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;11&lt;/td&gt;
&lt;td&gt;J&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;[[#GM factories supplying North America|Factory ID]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;12&lt;/td&gt;
&lt;td&gt;1&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td rowspan=6&gt;Sequential number
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;13&lt;/td&gt;
&lt;td&gt;2&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;14&lt;/td&gt;
&lt;td&gt;3&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;15&lt;/td&gt;
&lt;td&gt;7&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;16&lt;/td&gt;
&lt;td&gt;6&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;17&lt;/td&gt;
&lt;td&gt;2&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;
&lt;/table&gt;

====GVWR/Brake System/Body Style 2010- Light Duty Truck &amp; Multi-Purpose Passenger Vehicle====
The GVWR/Brake System is specified as character 4 of the American GM VIN for light trucks.

{| border=1 style=&quot;margin:auto;&quot;
!VIN
!GVWR Range in lbs. &amp; Weight Class
!Brake System
!Body Style
|-
| ||Class A: 0-3,000||Hydraulic||
|-
| ||Class B: 3,001-4,000||Hydraulic||
|-
|A||Class C: 4,001-5,000||Hydraulic||26: 4-door SUV or MPV ('10-'11 Chevy HHR Panel, '10-'26 Chevy Equinox, GMC Terrain, '10 Saturn Vue,&lt;br&gt; '12-'15 Chevy Captiva Sport, '19-'24 Cadillac XT4, '24-'26 Buick Encore GX)
|-
|B||Class C: 4,001-5,000||Hydraulic||46: 4-door MPV ('10-'11 Chevy HHR)
|-
|J||Class C: 4,001-5,000||Hydraulic||48: 4-door, 4 window Hatchback ('18-'23 Chevy Bolt EV w/Rear Seat Delete pkg. - incomplete vehicle)
|-
|C||Class C: 4,001-5,000||Hydraulic||03: Regular Cab pickup or Chassis Cab ('10-'12 Chevy Colorado, GMC Canyon)
|-
|D||Class C: 4,001-5,000||Hydraulic||43: Crew Cab pickup or Chassis Cab ('10-'12 Chevy Colorado, GMC Canyon)
|-
|E||Class C: 4,001-5,000||Hydraulic||53: Extended Cab pickup or Chassis Cab ('10-'12 Chevy Colorado, GMC Canyon)
|-
|7||Class C: 4,001-5,000||Hydraulic||75: Four-Door Wagon - High Roof Monocab (Canada only: '12-'14 Chevy Orlando)
|-
|M||Class C: 4,001-5,000||Hydraulic||06: 4-door SUV ('20-'23 Buick Encore GX)
|-
|9||Class C: 4,001-5,000||Hydraulic||56: 4-door SUV Extended ('21-'26 Chevy Trailblazer)
|-
|7||Class C: 4,001-5,000||Hydraulic||58: 4-door Utility Extended ('24-'26 Chevy Trax, Buick Envista)
|-
|C||Class C: 4,001-5,000||Hydraulic||76: 4-door SUV ('13-'22 Buick Encore, Canada only: '13-'14 Chevy Trax, US &amp; Canada: '15-'22 Chevy Trax)
|-
|F||Class D: 5,001-6,000||Hydraulic||26: 4-door SUV ('10-'17 Chevy Equinox, GMC Terrain, '10 Saturn Vue, '10-'16 Cadillac SRX, '11 Saab 9-4X,&lt;br&gt; '12-'13 Chevy Captiva Sport, '16-'26 Buick Envision, '17 Cadillac XT5, '19-'25 Cadillac XT4)
|-
|H||Class D: 5,001-6,000||Hydraulic||03: Regular Cab pickup or Chassis Cab ('10 Chevy Colorado, GMC Canyon)
|-
|G||Class D: 5,001-6,000||Hydraulic||03: Regular Cab pickup or Chassis Cab ('11-'12 Chevy Colorado, GMC Canyon)
|-
|J||Class D: 5,001-6,000||Hydraulic||43: Crew Cab pickup or Chassis Cab ('10 Chevy Colorado, GMC Canyon)
|-
|H||Class D: 5,001-6,000||Hydraulic||43: Crew Cab pickup or Chassis Cab ('11-'12 Chevy Colorado, GMC Canyon)
|-
|G||Class D: 5,001-6,000||Hydraulic||43: Crew Cab pickup or Chassis Cab ('15-'24 Chevy Colorado, '15-'22 GMC Canyon)
|-
|K||Class D: 5,001-6,000||Hydraulic||53: Extended Cab pickup or Chassis Cab ('10 Chevy Colorado, GMC Canyon)
|-
|J||Class D: 5,001-6,000||Hydraulic||53: Extended Cab pickup or Chassis Cab ('11-'12 Chevy Colorado, GMC Canyon)
|-
|H||Class D: 5,001-6,000||Hydraulic||53: Extended Cab pickup or Chassis Cab ('15-'22 Chevy Colorado, GMC Canyon)
|-
|T||Class D: 5,001-6,000||Hydraulic||69: Commercial Chassis ('10 Cadillac DTS chassis for Limo/Hearse)
|-
|7||Class D: 5,001-6,000||Hydraulic||69: Commercial Chassis ('11 Cadillac DTS chassis for Limo/Hearse)
|-
|L||Class E: 6,001-7,000||Hydraulic||26: 4-door SUV ('10 Chevy Traverse, GMC Acadia, Buick Enclave, Saturn Outlook)
|-
|K||Class E: 6,001-7,000||Hydraulic||26: 4-door SUV ('11-'17 Chevy Traverse, Buick Enclave, '11-'23 GMC Acadia, '17 Acadia Limited,&lt;br&gt; '17-'26 Cadillac XT5, '19-'26 Chevy Blazer, '20-'25 Cadillac XT6, '23-'26 Cadillac Lyriq EV,&lt;br&gt; '24-'26 Chevy Blazer EV, '25-'26 Cadillac Optiq EV, '24-'26 Honda Prologue EV, '24 Acura ZDX EV A-Spec)
|-
|7||Class E: 6,001-7,000||Hydraulic||48: 4-door SUV ('24-'25 Chevy Equinox EV)
|-
|E||Class E: 6,001-7,000||Hydraulic||56: 4-door SUV Extended ('18-'26 Chevy Traverse, Buick Enclave, '24 Chevy Traverse Limited,&lt;br&gt; '24-'26 GMC Acadia
|-
|M||Class E: 6,001-7,000||Hydraulic||05: Cargo Van ('10 Chevy Express, GMC Savana)
|-
|L||Class E: 6,001-7,000||Hydraulic||05: Cargo Van ('11-'14 Chevy Express, GMC Savana)
|-
|M||Class E: 6,001-7,000||Hydraulic||06: 4-door SUV ('10 Chevy Tahoe, GMC Yukon, Hummer H3)
|-
|L||Class E: 6,001-7,000||Hydraulic||06: 4-door SUV ('11-'20 Chevy Tahoe Police Pursuit Vehicle 2wd)
|-
|N||Class E: 6,001-7,000||Hydraulic||36: Sport Utility Truck (SUT) ('10 Chevy Avalanche 2wd)
|-
|M||Class E: 6,001-7,000||Hydraulic||36: Sport Utility Truck (SUT) ('11-13 Chevy Avalanche 2wd)
|-
|P||Class E: 6,001-7,000||Hydraulic||03: Regular Cab pickup or Chassis Cab ('10 Chevy Silverado, GMC Sierra)
|-
|N||Class E: 6,001-7,000||Hydraulic||03: Regular Cab pickup or Chassis Cab ('11-'26 Chevy Silverado, GMC Sierra,&lt;br&gt; '22 Chevy Silverado LTD, GMC Sierra Limited)
|-
|R||Class E: 6,001-7,000||Hydraulic||43: Crew Cab pickup or Chassis Cab ('10 Chevy Silverado, GMC Sierra, Hummer H3T)
|-
|P||Class E: 6,001-7,000||Hydraulic||43: Crew Cab pickup or Chassis Cab ('11-'26 Chevy Silverado, GMC Sierra,&lt;br&gt; '22 Chevy Silverado LTD, GMC Sierra Limited, '16-'26 Chevy Colorado, GMC Canyon)
|-
|S||Class E: 6,001-7,000||Hydraulic||53: Extended Cab pickup or Chassis Cab ('10 Chevy Silverado, GMC Sierra)
|-
|R||Class E: 6,001-7,000||Hydraulic||53: Extended Cab pickup or Chassis Cab ('11-'26 Chevy Silverado, GMC Sierra,&lt;br&gt; '19 Chevy Silverado LD, GMC Sierra Limited, '22 Chevy Silverado LTD, GMC Sierra Limited,&lt;br&gt; '16-'22 Chevy Colorado)
|-
|G||Class E: 6,001-7,000||Hydraulic||69: Commercial Chassis ('10 Cadillac DTS chassis for Limo/Hearse)
|-
|8||Class E: 6,001-7,000||Hydraulic||69: Commercial Chassis ('11 Cadillac DTS chassis for Limo/Hearse)
|-
|X||Class E: 6,001-7,000||Hydraulic||69: Commercial Chassis ('13-'19 Cadillac XTS chassis for Limo/Hearse)
|-
|U||Class F: 7,001-8,000||Hydraulic||05: Cargo Van or Incomplete Vehicle ('10 Chevy Express, GMC Savana)
|-
|S||Class F: 7,001-8,000||Hydraulic||05: Cargo Van or Incomplete Vehicle ('11-'14 Chevy Express, GMC Savana)
|-
|U||Class F: 7,001-8,000||Hydraulic||06: Passenger Van ('10 Chevy Express, GMC Savana)
|-
|S||Class F: 7,001-8,000||Hydraulic||06: Passenger Van ('11-'14 Chevy Express, GMC Savana)
|-
|U||Class F: 7,001-8,000||Hydraulic||06: 4-door SUV ('10 Chevy Tahoe, Suburban 1500, GMC Yukon, Yukon XL 1500, Cadillac Escalade, Escalade ESV)
|-
|S||Class F: 7,001-8,000||Hydraulic||06: 4-door SUV ('11-'26 Chevy Tahoe, Suburban 1500, GMC Yukon, Yukon XL 1500, Cadillac Escalade, Escalade ESV)
|-
|V||Class F: 7,001-8,000||Hydraulic||36: Sport Utility Truck (SUT) ('10 Chevy Avalanche 4wd, Cadillac Escalade EXT 4wd)
|-
|T||Class F: 7,001-8,000||Hydraulic||36: Sport Utility Truck (SUT) ('11-'13 Chevy Avalanche 4wd, Cadillac Escalade EXT 4wd)
|-
|X||Class F: 7,001-8,000||Hydraulic||26: 4-door SUV ('24 Acura ZDX EV Type S)
|-
|C||Class F: 7,001-8,000||Hydraulic||56: 4-door SUV Extended ('26- Cadillac Vistiq EV)
|-
|W||Class F: 7,001-8,000||Hydraulic||03: Regular Cab pickup or Chassis Cab ('10 Chevy Silverado, GMC Sierra)
|-
|X||Class F: 7,001-8,000||Hydraulic||43: Crew Cab pickup or Chassis Cab ('10 Chevy Silverado, GMC Sierra)
|-
|U||Class F: 7,001-8,000||Hydraulic||43: Crew Cab pickup or Chassis Cab ('11-'26 Chevy Silverado, GMC Sierra,&lt;br&gt; '22 Chevy Silverado LTD, GMC Sierra Limited)
|-
|Y||Class F: 7,001-8,000||Hydraulic||53: Extended Cab pickup or Chassis Cab ('10 Chevy Silverado, GMC Sierra)
|-
|V||Class F: 7,001-8,000||Hydraulic||53: Extended Cab pickup or Chassis Cab ('11-'26 Chevy Silverado, GMC Sierra,&lt;br&gt; '19 Chevy Silverado LD, GMC Sierra Limited, '22 Chevy Silverado LTD, GMC Sierra Limited)
|-
|U||Class F: 7,001-8,000||Hydraulic||69: Commercial Chassis ('10 Cadillac DTS chassis for Limo/Hearse)
|-
|9||Class F: 7,001-8,000||Hydraulic||69: Commercial Chassis ('11 Cadillac DTS chassis for Limo/Hearse)
|-
|Z||Class G: 8,001-9,000||Hydraulic||05: Cargo Van or Incomplete Vehicle ('10 Chevy Express, GMC Savana)
|-
|W||Class G: 8,001-9,000||Hydraulic||05: Cargo Van or Incomplete Vehicle ('11-'26 Chevy Express, GMC Savana)
|-
|Z||Class G: 8,001-9,000||Hydraulic||06: Passenger Van ('10 Chevy Express, GMC Savana)
|-
|W||Class G: 8,001-9,000||Hydraulic||06: Passenger Van ('11-'26 Chevy Express, GMC Savana)
|-
|Z||Class G: 8,001-9,000||Hydraulic||06: 4-door SUV ('10 Chevy Suburban 2500, GMC Yukon XL 2500)
|-
|W||Class G: 8,001-9,000||Hydraulic||06: 4-door SUV ('11-'13 Chevy Suburban 2500, GMC Yukon XL 2500)
|-
|2||Class H: 9,001-10,000||Hydraulic||05: Cargo Van or Incomplete Vehicle ('10 Chevy Express, GMC Savana)
|-
|Z||Class H: 9,001-10,000||Hydraulic||05: Cargo Van or Incomplete Vehicle ('11-'26 Chevy Express, GMC Savana,&lt;br&gt; '23-'24 BrightDrop Zevo 600, '24 BrightDrop Zevo 400, '25-'26 Chevrolet BrightDrop 400/600)
|-
|2||Class H: 9,001-10,000||Hydraulic||06: Passenger Van ('10 Chevy Express, GMC Savana)
|-
|Z||Class H: 9,001-10,000||Hydraulic||06: Passenger Van ('11-'26 Chevy Express, GMC Savana)
|-
|3||Class H: 9,001-10,000||Hydraulic||03: Van Cutaway ('10 Chevy Express, GMC Savana)
|-
|0||Class H: 9,001-10,000||Hydraulic||03: Van Cutaway ('11-'26 Chevy Express, GMC Savana)
|-
|3||Class H: 9,001-10,000||Hydraulic||03: Regular Cab pickup or Chassis Cab ('10 Chevy Silverado, GMC Sierra)
|-
|0||Class H: 9,001-10,000||Hydraulic||03: Regular Cab pickup or Chassis Cab ('11-'26 Chevy Silverado, GMC Sierra)
|-
|4||Class H: 9,001-10,000||Hydraulic||43: Crew Cab pickup or Chassis Cab ('10 Chevy Silverado, GMC Sierra)
|-
|1||Class H: 9,001-10,000||Hydraulic||43: Crew Cab pickup or Chassis Cab ('11-'26 Chevy Silverado, GMC Sierra,&lt;br&gt; '24-'25 GMC Hummer EV pickup w/20 module battery pack,&lt;br&gt; '24-'26 Chevy Silverado EV, '25-'26 GMC Sierra EV)
|-
|5||Class H: 9,001-10,000||Hydraulic||53: Extended Cab pickup or Chassis Cab ('10 Chevy Silverado, GMC Sierra)
|-
|2||Class H: 9,001-10,000||Hydraulic||53: Extended Cab pickup or Chassis Cab ('11-'13, '15-'26 Chevy Silverado, GMC Sierra)
|-
|B||Class H: 9,001-10,000||Hydraulic||26: 4-door SUV ('24-'25 GMC Hummer EV SUV)
|-
|6||Class 3: 10,001-14,000||Hydraulic||03: Van Cutaway ('10 Chevy Express, GMC Savana)
|-
|3||Class 3: 10,001-14,000||Hydraulic||03: Van Cutaway ('11-'26 Chevy Express, GMC Savana)
|-
|6||Class 3: 10,001-14,000||Hydraulic||03: Regular Cab pickup or Chassis Cab ('10 Chevy Silverado, GMC Sierra)
|-
|3||Class 3: 10,001-14,000||Hydraulic||03: Regular Cab pickup or Chassis Cab ('11-'26 Chevy Silverado, GMC Sierra)
|-
|7||Class 3: 10,001-14,000||Hydraulic||43: Crew Cab pickup or Chassis Cab ('10 Chevy Silverado, GMC Sierra)
|-
|4||Class 3: 10,001-14,000||Hydraulic||43: Crew Cab pickup or Chassis Cab ('11-'26 Chevy Silverado, GMC Sierra,&lt;br&gt; '22-'24 GMC Hummer EV pickup w/24 module battery pack, '25 GMC Hummer EV pickup w/20 or 24 module battery pack, '26 GMC Hummer EV pickup, '24-'25 Chevy Silverado EV, GMC Sierra EV)
|-
|8||Class 3: 10,001-14,000||Hydraulic||53: Extended Cab pickup or Chassis Cab ('10 Chevy Silverado, GMC Sierra)
|-
|5||Class 3: 10,001-14,000||Hydraulic||53: Extended Cab pickup or Chassis Cab ('11-'13, '15-'18, '20-'26 Chevy Silverado, GMC Sierra)
|-
|8||Class 3: 10,001-14,000||Hydraulic||06: 4-door SUV ('16-'19, '24-'26 Chevy Suburban 3500HD)
|-
|8||Class 3: 10,001-14,000||Hydraulic||05: Cargo Van ('22 BrightDrop EV600, '23-'24 BrightDrop Zevo 600, '24 BrightDrop Zevo 400,&lt;br&gt; '25-'26 Chevrolet BrightDrop 400/600)
|-
|T||Class 3: 10,001-14,000||Hydraulic||26: 4-door SUV ('25-'26 GMC Hummer EV SUV, '25-'26 Cadillac Escalade IQ [EV])
|-
|L||Class 3: 10,001-14,000||Hydraulic||56: 4-door SUV Extended ('26- Cadillac Escalade IQL [EV])
|-
|9||Class 4: 14,001-16,000||Hydraulic||03: Van Cutaway ('10 Chevy Express, GMC Savana)
|-
|6||Class 4: 14,001-16,000||Hydraulic||03: Van Cutaway ('11-'26 Chevy Express, GMC Savana)
|-
| ||Class 5: 16,001-19,500||Hydraulic||
|}

====Line &amp; Chassis Type 2010- Light Duty Truck &amp; Multi-Purpose Passenger Vehicle====
The Line &amp; Chassis Type is specified as character 5 of the American GM VIN for light trucks.

{| border=1 style=&quot;margin:auto;&quot;
!VIN
!Description
|-
|A||Chevrolet HHR ('10-'11), HHR Panel ('10-'11)
|-
|A||Chevy Silverado 1500 2wd ('22-'26), Silverado HD 2500/3500 2wd ('25-'26)
|-
|B||Chevy Blazer 2wd &amp; Awd '19-'26
|-
|C||Chevy Silverado 2wd ('10-'18), Silverado LD 1500 2wd '19, Silverado HD 2500/3500 2wd '19, GMC Sierra 2wd ('10)
|-
|C||Chevy Tahoe 2wd ('10-'24), Suburban 2wd ('10-'24), Avalanche 2wd ('10-'13),&lt;br /&gt; GMC Yukon 2wd ('10), Yukon XL 2wd ('10), Cadillac Escalade 2wd ('10), Escalade ESV 2wd ('10)
|-
|D||Chevy Silverado 1500 4wd ('22-'24)
|-
|D||Chevy Blazer EV ('24-'26), Chevy Equinox EV ('24-'26)
|-
|E||Cadillac Escalade IQ [EV] ('25-'26), Escalade IQL [EV] ('26-), GMC Hummer EV pickup ('26-), GMC Hummer EV SUV ('26-), GMC Sierra EV ('26-)
|-
|F||Chevy Bolt EV w/Rear Seat Delete pkg. - incomplete vehicle ('18-'23)
|-
|G||Cadillac Chassis for Limousine &amp; for Armored Vehicle (Based on XTS '13-'19)
|-
|G||Cadillac Chassis for Hearse (Based on XTS '13-'19)
|-
|G||Chevy Express 2wd ('10-'26), GMC Savana 2wd ('10) 
|-
|H||Chevy Express 4wd ('10-'14), GMC Savana 4wd ('10)
|-
|H||GMC Sierra 1500 2wd ('22-'26), Sierra HD 2500/3500 2wd ('25-'26)
|-
|H||Honda Prologue EV ('24-'26), Acura ZDX EV ('24)
|-
|J||Buick Encore 2wd &amp; Awd ('13-'22), Chevy Trax 2wd &amp; Awd (Canada: '13-'22, US: '15-'22)
|-
|J||BrightDrop EV600 ('22), BrightDrop Zevo 600 ('23-'24), BrightDrop Zevo 400 ('24), Chevrolet BrightDrop 400/600 ('25-'26)
|-
|K||Chevy Silverado 4wd ('10-'18), Silverado LD 1500 4wd ('19), Silverado HD 2500/3500 4wd ('19), GMC Sierra 4wd ('10)
|-
|K||Chevy Silverado 1500 4wd ('25-'26), Silverado HD 2500/3500 4wd ('25-'26)
|-
|K||Chevy Tahoe 4wd ('10-'24), Suburban 4wd ('10-'24), Suburban HD 4wd ('24-'26), Avalanche 4wd ('10-'13), GMC Yukon 4wd ('10), Yukon XL 4wd ('10),&lt;br&gt; Cadillac Escalade 4wd ('10), Escalade ESV 4wd ('10), Escalade EXT 4wd ('10)
|-
|K||Cadillac Professional Chassis for Limousine (Based on DTS '10-'11)
|-
|K||Cadillac Commercial Chassis for Hearse (Based on DTS '10-'11)
|-
|L||Chevy Equinox 2wd &amp; Awd '10-'17, Captiva Sport 2wd '12-'15, Captiva Sport Awd '12, GMC Terrain 2wd &amp; Awd '10-'17, Saturn Vue 2wd &amp; Awd '10
|-
|L||GMC Terrain 2wd &amp; Awd '18-'26
|-
|L||Buick Envista '24-'26, Chevy Trax '24-'26
|-
|M||Buick Encore GX 2wd &amp; Awd ('20-'26), Chevy Trailblazer 2wd &amp; Awd ('21-'26)
|-
|N||Cadillac SRX 2wd &amp; Awd '10-'16, Saab 9-4X 2011
|-
|N||GMC Acadia 2wd &amp; Awd '17-'26, Cadillac XT5 2wd &amp; Awd '17-'26
|-
|N||Hummer H3, H3T 2010
|-
|P||Chevy Orlando (Canada only: '12-'14)
|-
|P||Cadillac XT6 2wd &amp; Awd '20-'25
|-
|P||Cadillac Lyriq EV 2wd &amp; Awd '23-'25
|-
|R||GMC Acadia 2wd '10-'16, Acadia Limited 2wd '17, Saturn Outlook 2wd '10, Buick Enclave 2wd '10-'17, Chevy Traverse 2wd '10-'17
|-
|R||Buick Enclave 2wd '18-'24, Chevy Traverse 2wd '18-'23
|-
|R||Buick Enclave 2wd '25-'26, Chevy Traverse 2wd '24-'26
|-
|S||Chevy Traverse Limited 2wd '24
|-
|S||Chevy Colorado 2wd ('10-'12, '15-'26), GMC Canyon 2wd ('10)
|-
|T||Chevy Colorado 4wd ('10-'12, '15-'26), GMC Canyon 4wd ('10)
|-
|T||Chevy Traverse Limited Awd '24
|-
|U||GMC Sierra 1500 4wd ('22-'26), Sierra HD 2500/3500 4wd ('25-'26)
|-
|V||GMC Acadia Awd '10-'16, Acadia Limited Awd '17, Saturn Outlook Awd '10, Buick Enclave Awd '10-'17, Chevy Traverse Awd '10-'17
|-
|V||Buick Enclave Awd '18-'24, Chevy Traverse Awd '18-'23
|-
|V||Buick Enclave Awd '25-'26, Chevy Traverse Awd '24-'26
|-
|W||Chevy Silverado 1500 2wd ('19-'21), Silverado LTD 1500 2wd ('22), Silverado HD 2500/3500 2wd ('20-'24)
|-
|X||Buick Envision 2wd &amp; Awd '16-'20, Chevy Equinox 2wd &amp; Awd '18-'26
|-
|Y||Chevy Silverado 1500 4wd ('19-'21), Silverado LTD 1500 4wd ('22), Silverado HD 2500/3500 4wd ('20-'24)
|-
|Z||Cadillac XT4 2wd &amp; Awd '19-'25, Buick Envision 2wd '21-'23, Buick Envision Awd '21-'26
|-
|1||GMC Sierra 2wd ('11-'18), Sierra Limited 1500 2wd ('19), Sierra HD 2500/3500 2wd ('19), Yukon 2wd ('11-'26), Yukon XL 2wd ('11-'26)
|-
|1||GMC Canyon 2wd ('25-'26)
|-
|2||GMC Sierra 4wd ('11-'18), Sierra Limited 1500 4wd ('19), Sierra HD 2500/3500 4wd ('19), Yukon 4wd ('11-'26), Yukon XL 4wd ('11-'26)
|-
|2||GMC Canyon 4wd ('25-'26)
|-
|3||Cadillac Escalade 2wd ('11-'24), Escalade ESV 2wd ('11-'24)
|-
|3||Cadillac Optiq EV ('25-), Cadillac Vistiq EV ('26-)
|-
|4||Cadillac Escalade 4wd ('11-'24), Escalade ESV 4wd ('11-'24), Escalade EXT 4wd ('11-'13)
|-
|5||GMC Canyon 2wd ('11-'12, '15-'24)
|-
|5||Chevy Tahoe 2wd ('25-'26), Suburban 2wd ('25-'26)
|-
|6||GMC Canyon 4wd ('11-'12, '15-'24)
|-
|6||Chevy Tahoe 4wd ('25-'26), Suburban 4wd ('25-'26)
|-
|7||GMC Savana 2wd ('11-'26)
|-
|8||GMC Savana 4wd ('11-'14)
|-
|8||GMC Sierra 1500 2wd ('19-'21), Sierra Limited 1500 2wd ('22), Sierra HD 2500/3500 2wd ('20-'24)
|-
|8||Cadillac Escalade 2wd ('25-'26), Escalade ESV 2wd ('25-'26)
|-
|9||GMC Sierra 1500 4wd ('19-'21), Sierra Limited 1500 4wd ('22), Sierra HD 2500/3500 4wd ('20-'24)
|-
|9||Cadillac Escalade 4wd ('25-'26), Escalade ESV 4wd ('25-'26)
|-
|0||GMC Hummer EV pickup ('22-'25), GMC Hummer EV SUV ('24-'25), Chevy Silverado EV ('24-'26), GMC Sierra EV ('24-'25)
|}

====Series 2010- Light Duty Truck &amp; Multi-Purpose Passenger Vehicle====
The Series is specified as character 6 of the American GM VIN for light trucks.

{| border=1 style=&quot;margin:auto;&quot;
!VIN
!Description
|-
|A (following L)||Saturn Vue XE 2wd ('10)
|-
|E (following L)||Saturn Vue XR V6 2wd ('10)
|-
|K (following L)||Saturn Vue XR-L V6 2wd ('10)
|-
|T (following R)||Saturn Outlook XE 2wd ('10)
|-
|U (following R)||Saturn Outlook XE Premium 2wd ('10)
|-
|V (following R)||Saturn Outlook XR-L 2wd ('10)
|-
|W (following R)||Saturn Outlook XR-L Premium 2wd ('10)
|-
|T (following V)||Saturn Outlook XE Awd ('10)
|-
|U (following V)||Saturn Outlook XE Premium Awd ('10)
|-
|V (following V)||Saturn Outlook XR-L Awd ('10)
|-
|W (following V)||Saturn Outlook XR-L Premium Awd ('10)
|-
|G (following N)||Hummer H3, H3T Base model ('10)
|-
|H (following N)||Hummer H3, H3T Adventure ('10)
|-
|J (following N)||Hummer H3, H3T Luxury ('10)
|-
|K (following N)||Hummer H3, H3T Alpha w/cloth ('10)
|-
|L (following N)||Hummer H3, H3T Alpha w/Leather ('10)
|-
|P (following N)||Saab 9-4X 3.0i 2wd ('11)
|-
|R (following N)||Saab 9-4X 3.0i Awd ('11)
|-
|S (following N)||Saab 9-4X 3.0i Premium 2wd ('11)
|-
|T (following N)||Saab 9-4X 3.0i Premium Awd ('11)
|-
|U (following N)||Saab 9-4X Aero Awd ('11)
|}

===Platform &amp; Series Codes 1985- Passenger Car===
GM used a lettered system of automobile platform codes for three decades. These letters were used as the 4th position of the VIN. Though today's GM platforms use Greek characters, they are still encoded with Latin characters in the 4th position. Position 5 encodes the specific model and trim level of the vehicle.

{| border=1 style=&quot;margin:auto;&quot;
!List of GM platforms
!Platform&lt;br&gt;Code
!Series&lt;br&gt;Code
!:Category:General Motors vehicles|Model
|-
|rowspan=14|GM A platform
|rowspan=14|A||W||Chevrolet Celebrity 1985-1990
|-
|E||Pontiac 6000 ''SE'' 1986-1988
|-
|F||Pontiac 6000 1985-1988, 6000 ''LE'' 1989-1991
|-
|G||Pontiac 6000 ''LE'' 1985-1988
|-
|H||Pontiac 6000 ''STE'' 1985-1989
|-
|J||Pontiac 6000 ''SE'' 1989-1991
|-
|G||Oldsmobile Cutlass Ciera ''S'' Sedan 1993-1994
|-
|J||Oldsmobile Cutlass Ciera ''LS'' 1985, Cutlass Ciera 1986-1989 &amp; Cutlass Cruiser 1985-1989,&lt;br /&gt; Cutlass Ciera ''S'' Coupe 1986-1987, Cutlass Ciera ''S'' 1990-1991 &amp; Cutlass Cruiser ''S'' 1990-1994, Cutlass Ciera ''SL'' &amp; Cutlass Cruiser ''SL'' 1995, Ciera ''SL'' sedan &amp; wagon 1996
|-
|L||Oldsmobile Cutlass Ciera 1990-1991, Cutlass Ciera ''S'' Sedan 1992
|-
|M||Oldsmobile Cutlass Ciera ''Brougham'' 1985-1988, Cutlass Ciera ''SL'' Coupe 1986-1989, Cutlass Ciera ''SL'' Sedan 1989-1993, Cutlass Cruiser ''Brougham'' 1987-1988, Cutlass Cruiser ''SL'' 1989-1993
|-
|S||Oldsmobile Cutlass Ciera ''International Series'' 1988-1990
|-
|G||Buick Century ''T-Type'' 1985-1986, Century ''Special'' 1991-1996
|-
|H||Buick Century ''Custom'' 1985-1995
|-
|L||Buick Century ''Limited'' 1985-1993, Century Estate Wagon 1986-1989
|-
|rowspan=14|GM B platform
|rowspan=14|B||L||Chevrolet Impala 1985, Caprice 1986-1992, Caprice Classic 1993-1996, Impala SS 1995-96
|-
|N||Chevrolet Caprice Classic 1985-1992, Caprice Classic LS 1993-1994,&lt;br /&gt; Caprice Classic LTZ 1991-1993, Impala SS 1994
|-
|U||Chevrolet Caprice Classic Brougham/Brougham LS 1987-1990
|-
|L||Pontiac Parisienne 1985-1986, Safari Wagon 1987-1989
|-
|T||Pontiac Parisienne Brougham 1985-1986
|-
|N||Oldsmobile Delta 88 Royale 1985
|-
|P||Oldsmobile Custom Cruiser 1985-1992
|-
|V||Oldsmobile Delta 88 Royale Brougham LS 1985
|-
|Y||Oldsmobile Delta 88 Royale Brougham 1985
|-
|N||Buick Le Sabre ''Custom'' 1985, Roadmaster sedan 1992-1996
|-
|P||Buick Le Sabre ''Limited'' 1985
|-
|R||Buick Le Sabre Estate Wagon 1985-1989, Estate Wagon 1990,&lt;br /&gt; Roadmaster Estate Wagon 1991-1996
|-
|T||Buick Roadmaster ''Limited'' sedan 1992-1996
|-
|V||Buick Electra Estate Wagon 1985-1989
|-
|rowspan=13|GM C platform - front-wheel drive
|rowspan=13|C
|V||Oldsmobile Touring Sedan 1988-1990, 98 Touring Sedan 1991-1993  
|-
|W||Oldsmobile 98 Regency Brougham 1985-1990, 98 Regency Elite 1991-1996 
|-
|X||Oldsmobile 98 Regency 1985-1990, 1992-1994
|-
|F||Buick Electra T-Type 1985-1990
|-
|U||Buick Electra Park Avenue Ultra 1989-1990, Park Avenue Ultra 1991-1996
|-
|W||Buick Electra Park Avenue 1985-1990, Park Avenue 1991-1996
|-
|X||Buick Electra 1985-1986, Electra Limited 1987-1990
|-
|B||1985-1992 Cadillac Fleetwood, Fleetwood D'Elegance, 1993 Cadillac Sixty Special
|-
|D||1985-1993 Cadillac DeVille
|-
|G||1991-1992 Cadillac Fleetwood Sixty Special
|-
|H||1985-1987 Cadillac Fleetwood Limousine
|-
|S||1987-1990 Cadillac Fleetwood Sixty Special
|-
|T||1991-1993 Cadillac DeVille Touring Sedan
|-
|rowspan=3|GM G platform (models formerly on C platform)
|rowspan=3|C
|-
|U||Buick Park Avenue Ultra 1997-2005
|-
|W||Buick Park Avenue 1997-2005
|-
|rowspan=2|GM D platform
|rowspan=2|D||W||1985-1986 Cadillac Fleetwood Brougham, 1987-1992 Cadillac Brougham
|-
|W||1993-1996 Cadillac Fleetwood
|-
|rowspan=31|GM Delta I platform
|rowspan=31|A
|-
|A||Chevrolet Cobalt LS w/manual trans. 2010
|-
|B||Chevrolet Cobalt LS w/automatic trans. 2010
|-
|C||Chevrolet Cobalt 1LT w/manual trans. 2010
|-
|D||Chevrolet Cobalt 1LT w/automatic trans. 2010
|-
|E||Chevrolet Cobalt 2LT w/manual trans. 2010
|-
|F||Chevrolet Cobalt 2LT w/automatic trans. 2010
|-
|G||Chevrolet Cobalt SS Turbo 2010
|-
|H||Chevrolet Cobalt (base model w/XFE) 2010
|-
|K||Chevrolet Cobalt (base model) 2005, Cobalt LS 2006-2008, Cobalt LS w/man. trans. 2009
|-
|L||Chevrolet Cobalt LS 2005, Cobalt LT 2006-2008, Cobalt LT w/manual trans. 2009
|-
|M||Chevrolet Cobalt SS 2006-2007, Cobalt Sport 2008
|-
|P||Chevrolet Cobalt SS Supercharged 2005-2007, SS Turbo 2008-2009
|-
|S||Chevrolet Cobalt LS w/automatic trans. 2009
|-
|T||Chevrolet Cobalt LT w/automatic trans. 2009
|-
|Z||Chevrolet Cobalt LT 2005, Cobalt LTZ 2006-2007
|-
|L||Pontiac G5 2007-2008, G5 w/manual trans. 2009
|-
|N||Pontiac G5 GT 2007-2008, G5 GT w/manual trans. 2009
|-
|S||Pontiac G5 w/automatic trans. 2009
|-
|T||Pontiac G5 GT w/automatic trans. 2009
|-
|F||Saturn Ion sedan Level 1 w/manual trans. 2003-2005
|-
|G||Saturn Ion sedan Level 1 w/automatic trans. 2003-2005
|-
|J||Saturn Ion sedan Level 2 w/automatic trans. 2003-2007
|-
|K||Saturn Ion sedan Level 3 w/manual trans. 2003-2007
|-
|L||Saturn Ion sedan Level 3 w/automatic trans. 2003-2007
|-
|M||Saturn Ion coupe Level 2 w/manual trans. 2003-2007
|-
|N||Saturn Ion coupe Level 2 w/automatic trans. 2003-2007
|-
|V||Saturn Ion coupe Level 3 w/manual trans. 2003-2007
|-
|W||Saturn Ion coupe Level 3 w/automatic trans. 2003-2007
|-
|Y||Saturn Ion coupe Red Line 2004-2007
|-
|Z||Saturn Ion sedan Level 2 w/manual trans. 2003-2007
|-
|rowspan=9|GM E platform
|rowspan=9|E
|-
|V||Oldsmobile Toronado Trofeo 1988-1992
|-
|Z||Oldsmobile Toronado Brougham 1985-1986, Toronado 1987-1992
|-
|C||Buick Reatta 1988-1991
|-
|Y||Buick Riviera T-Type 1985-1986
|-
|Z||Buick Riviera 1985-1993
|-
|C||Cadillac Eldorado Collector Series 2002 
|-
|L||Cadillac Eldorado 1985-2002
|-
|T||Cadillac Eldorado Touring Coupe 1994-2002 
|-
|rowspan=26|GM Epsilon I platform
|rowspan=26|Z||A||Chevrolet Malibu Fleet 2010-2012
|-
|B||Chevrolet Malibu LS 2010-2012
|-
|C||Chevrolet Malibu 1LT 2010-2012
|-
|D||Chevrolet Malibu 2LT 2010-2012
|-
|E||Chevrolet Malibu LTZ 2010-2011, Malibu 1LZ 2012
|-
|F||Chevrolet Malibu Hybrid 2008-2010, Malibu 3LT 2012
|-
|G||Chevrolet Malibu LS 2008-2009, Malibu 2LZ 2012
|-
|H||Chevrolet Malibu 1LT 2008-2009
|-
|J||Chevrolet Malibu 2LT 2008-2009
|-
|K||Chevrolet Malibu LTZ 2008-2009
|-
|S||Chevrolet Malibu 2004-2005, Malibu LS 2006-2007, Malibu Classic LS 2008
|-
|T||Chevrolet Malibu LS 2004-2005, Malibu LT 2006-2007, Malibu Classic LT 2008
|-
|U||Chevrolet Malibu LT 2004-2005, Malibu LTZ 2006-2007
|-
|W||Chevrolet Malibu SS 2006-2007
|-
|A||Pontiac G6 Sedan 2010
|-
|F||Pontiac G6 2.4L Sedan (Base model) 2006, G6 Value Leader (Base model w/1SV) 2007-2008
|-
|G||Pontiac G6 3.5L Sedan (Base model) 2005-2006, G6 (Base model) 2007-2009
|-
|H||Pontiac G6 GT 2005-2009
|-
|J||Pontiac G6 (Base model) 2009 1/2 (Mid-Cycle Revision)
|-
|K||Pontiac G6 GT 2009 1/2 (Mid-Cycle Revision)
|-
|L||Pontiac G6 GXP 2009 1/2 (Mid-Cycle Revision)
|-
|M||Pontiac G6 GTP 2006-2007, G6 GXP 2008-2009
|-
|R||Saturn Aura Green Line 2007-2009
|-
|S||Saturn Aura XE 2007-2009
|-
|V||Saturn Aura XR 2007-2008, Aura XR 2.4L 2009
|-
|X||Saturn Aura XR V6 2009
|-
|rowspan=6|GM F platform
|rowspan=6|F||P||Chevrolet Camaro Sport Coupe 1985-2002, Convertible 1987-1992, 1994-2002
|-
|S||Chevrolet Camaro Berlinetta 1985-1986
|-
|S||Pontiac Firebird 1985-2002, Firebird ''Formula'' 1987-1992
|-
|V||Pontiac Firebird ''Formula / Trans Am'' 1993-2002, Firebird ''Trans Am GT'' 1994
|-
|W||Pontiac Firebird ''Trans Am'' 1985-1992, Firebird ''Trans Am GTA'' 1987-1992
|-
|X||Pontiac Firebird ''S/E'' 1985-1986
|-
|rowspan=13|GM G platform - rear-wheel drive
|rowspan=13|G||Z||Chevrolet Monte Carlo 1985-1988
|-
|J||Pontiac Grand Prix 1985-1987
|-
|K||Pontiac Grand Prix LE 1985-1987
|-
|N||Pontiac Bonneville 1985-1986
|-
|P||Pontiac Grand Prix Brougham 1985-1987
|-
|R||Pontiac Bonneville Brougham 1985-1986
|-
|S||Pontiac Bonneville LE 1985-1986
|-
|K||Oldsmobile Cutlass Salon coupe 1985-1987
|-
|M||Oldsmobile Cutlass Supreme ''Brougham'' 1985-1987,&lt;br /&gt; Cutlass Supreme Classic ''Brougham'' 1988
|-
|R||Oldsmobile Cutlass Supreme 1985-1987, Cutlass Supreme Classic 1988
|-
|J||Buick Regal 1985-1987
|-
|K||Buick Regal T-Type 1985-1987
|-
|M||Buick Regal ''Limited'' 1985-1987
|-
|rowspan=4|GM G platform - front-wheel drive
|rowspan=4|G||D||1995-1999 Buick Riviera
|-
|R||1995-1999 Oldsmobile Aurora
|-
|R||2001-2002 Oldsmobile Aurora 3.5
|-
|S||2001-2003 Oldsmobile Aurora 4.0
|-
|rowspan=9|GM H platform
|rowspan=9|H||H||Buick Le Sabre 1987
|-
|P||Buick Le Sabre ''Custom'' 1986-1999
|-
|R||Buick Le Sabre ''Limited'' 1986-1999
|-
|C||Oldsmobile Regency 1997-1998, Eighty Eight 50th Anniversary Edition 1999
|-
|N||Oldsmobile Delta 88 Royale 1986-1988, 88 Royale 1989-1995, Eighty Eight &amp; Eighty Eight LS 1996-99
|-
|Y||Oldsmobile Delta 88 Royale Brougham 1986-1988, 88 Royale Brougham 1989-91, Eighty Eight Royale LS 1992-1995, LSS 1996-1999
|-
|X||Pontiac Bonneville 1987, Bonneville LE 1988-1991, Bonneville ''SE'' 1992-1999
|-
|Y||Pontiac Bonneville SSE 1988-1991, Bonneville ''SSEi'' 1992-1993
|-
|Z||Pontiac Bonneville LE 1987, Bonneville SE 1988-1991, Bonneville ''SSE'' 1992-1999, Bonneville ''SSEi'' 1994-1999
|-
|rowspan=17|GM G platform (models formerly on H platform or their successors)
|rowspan=17|H||A||Buick Lucerne ''CX'' 2010-2011
|-
|B||Buick Lucerne ''CX-2'' 2010
|-
|C||Buick Lucerne ''CXL'' 2010-2011
|-
|D||Buick Lucerne ''CXL V6'' 2006-2009, Lucerne ''CXL Special Edition'' 2010
|-
|E||Buick Lucerne ''CXS'' 2006-2008, Lucerne ''CXL-3'' 2010
|-
|F||Buick Lucerne ''Super'' 2008-2009, Lucerne ''CXL-4'' 2010
|-
|G||Buick Lucerne ''CXL-5'' 2010
|-
|H||Buick Lucerne ''Super 1SP'' 2010
|-
|J||Buick Lucerne ''CXL Premium'' 2010-2011
|-
|K||Buick Lucerne ''Super 1XS'' 2010, Lucerne ''Super'' 2011 
|-
|P||Buick Lucerne ''CX'' 2006-2009
|-
|R||Buick Lucerne ''CXL V8'' 2006-2007, Lucerne ''CXL Special Edition V8'' 2008
|-
|P||Buick Le Sabre ''Custom'' 2000-2005
|-
|R||Buick Le Sabre ''Limited'' 2000-2005
|-
|X||Pontiac Bonneville ''SE'' 2000-2005
|-
|Y||Pontiac Bonneville ''SLE'' 2000-2005
|-
|Z||Pontiac Bonneville ''SSEi'' 2000-2003, Bonneville GXP 2004-2005
|-
|rowspan=23|GM J platform
|rowspan=23|J
|-
|C||Chevrolet Cavalier 1985-1994, RS Convertible 1991-1994
|-
|D||Chevrolet Cavalier CS 1985-1987
|-
|E||Chevrolet Cavalier Type 10 1985, RS 1986-1988,&lt;br /&gt; Type 10 Convertible 1985, RS Convertible 1986-1987
|-
|F||Chevrolet Cavalier Z24 1986-1994, Z24 Convertible 1988-1989, 1992-1994
|-
|C||Chevrolet Cavalier 1995-2005, Cavalier RS 1997-1999
|-
|F||Chevrolet Cavalier LS Sedan 1995-2005, LS Coupe 2003-2005, Z24 Coupe 1995-2001,&lt;br /&gt; LS Convertible 1995-1997, Z24 Convertible 1998-2000
|-
|H||Chevrolet Cavalier Z24 Coupe/Sedan 2002, LS Sport 2002-2005
|-
|S||Chevrolet Cavalier LS Coupe 2002
|-
|B||Pontiac Sunbird 1985-1989, Sunbird LE 1990-1991, Sunbird SE 1992-1993,&lt;br /&gt; Sunbird LE 1994
|-
|C||Pontiac Sunbird LE 1985, Sunbird 1991, Sunbird LE 1992-1993
|-
|D||Pontiac Sunbird SE 1985-1991, Sunbird GT 1992-1993
|-
|L||Pontiac Sunbird SE 1994
|-
|U||Pontiac Sunbird GT 1986-1991
|-
|B||Pontiac Sunfire SE 1995-2002, Convertible 1995-2000, Sunfire 2003-2005
|-
|D||Pontiac Sunfire GT 1995-2002
|-
|C||Oldsmobile Firenza Base model 1985-1987, Firenza S 1985-1987, Firenza 1988
|-
|D||Oldsmobile Firenza LX 1985-1987, Firenza SX 1985, Firenza LC, GT 1986-1987
|-
|E||Buick Skyhawk T-Type 1985-1986
|-
|S||Buick Skyhawk Custom 1985-1987, Skyhawk Sport 1986-1987, Skyhawk 1988-1989
|-
|T||Buick Skyhawk Limited 1985-1987
|-
|G||Cadillac Cimarron 1985-1988
|-
|G, H||Toyota Cavalier (Japan only)
|-
|rowspan=8|GM2900 platform
|rowspan=8|J||C||Saturn L-Series|2004 Saturn L300.1
|-
|D||Saturn L-Series|2004 Saturn L300.2, 2005 Saturn L300
|-
|L||Saturn L-Series|2004 Saturn L300.3
|-
|R||Saturn L-Series|Saturn LS w/manual transmission '00/L100 w/manual transmission '01
|-
|S||Saturn L-Series|Saturn LS w/automatic transmission '00/L100 w/automatic transmission '01-'02
|-
|T||Saturn L-Series|Saturn LS1 w/manual transmission '00/L200 w/manual transmission '01-'03, LW200 w/manual trans. '02
|-
|U||Saturn L-Series|Saturn LS1 w/automatic transmission '00/L200 w/automatic transmission '01-'03,&lt;br&gt; Saturn LW1 w/automatic transmission '00/LW200 w/automatic transmission '01-'03
|-
|W||Saturn L-Series|Saturn LS2 '00, LW2 '00, L300 '01-'03, LW300 '01-'03
|-
|rowspan=5|GM K platform
|rowspan=5|K||D||Cadillac Deville 1994-1999
|-
|E||Cadillac Deville D'Elegance 1997-1999
|-
|F||Cadillac Deville Concours 1994-1999
|-
|S||Cadillac Seville 1985-1993 / Cadillac Seville SLS 1994-1997
|-
|Y||Cadillac Seville Touring Sedan / Cadillac Seville STS 1990-1997
|-
|rowspan=9|GM G platform (models formerly on K platform)
|rowspan=9|K||A||2010-2011 Cadillac DTS
|-
|D||2000-2005 Cadillac Deville, 2006-2009 Cadillac DTS, 2010-2011 DTS Luxury
|-
|E||2000-2005 Cadillac Deville DHS
|-
|F||2000-2005 Cadillac Deville DTS
|-
|H||2010-2011 Cadillac DTS Premium
|-
|P||2010-2011 Cadillac DTS Platinum
|-
|R||2010-2011 Cadillac DTS Livery
|-
|S|| 1998-2004 Cadillac Seville SLS
|-
|Y|| 1998-2003 Cadillac Seville STS
|-
|rowspan=33|GM Kappa platform
|rowspan=33|M||A||Pontiac Solstice w/automatic transmission 2010
|-
|B||Pontiac Solstice 2006-2007, Solstice w/manual transmission 2008-2009
|-
|B||Pontiac Solstice GXP w/automatic transmission 2010
|-
|C||Pontiac Solstice w/automatic transmission 2008
|-
|D||Pontiac Solstice w/manual transmission 2010
|-
|E||Pontiac Solstice GXP w/manual transmission 2010
|-
|F||Pontiac Solstice GXP w/automatic transmission 2008
|-
|G||Pontiac Solstice GXP 2007, Solstice GXP w/manual transmission 2008-2009
|-
|K||Pontiac Solstice Street Edition w/manual transmission 2009
|-
|N||Pontiac Solstice w/automatic transmission 2009
|-
|S||Pontiac Solstice SCCA SSB Championship Edition (2.4L) 2008
|-
|T||Pontiac Solstice SCCA T2 Championship Edition (2.0L Turbo) 2008
|-
|T||Pontiac Solstice GXP w/automatic transmission 2009
|-
|Z||Pontiac Solstice Street Edition w/automatic transmission 2009
|-
|B||Saturn Sky 2007, Sky w/manual transmission 2008-2009 
|-
|B||Saturn Sky Redline w/automatic transmission 2010
|-
|C||Saturn Sky w/automatic transmission 2008
|-
|C||Saturn Sky Ruby Red (Merlot Jewel) Special Edition w/manual transmission 2009
|-
|C||Saturn Sky Preferred w/automatic transmission 2010 
|-
|D||Saturn Sky Hydro Blue Special Edition w/manual transmission 2009
|-
|E||Saturn Sky Redline w/manual transmission 2010
|-
|F||Saturn Sky Redline w/automatic transmission 2008
|-
|F||Saturn Sky Preferred w/manual transmission 2010 
|-
|G||Saturn Sky Redline 2007, Sky Redline w/manual transmission 2008-2009
|-
|H||Saturn Sky Redline Ruby Red (Merlot Jewel) Special Edition w/manual transmission 2009
|-
|L||Saturn Sky Redline Hydro Blue Special Edition w/manual transmission 2009
|-
|N||Saturn Sky w/automatic transmission 2009
|-
|P||Saturn Sky Ruby Red (Merlot Jewel) Special Edition w/automatic transmission 2009
|-
|R||Saturn Sky Hydro Blue Special Edition w/automatic transmission 2009
|-
|T||Saturn Sky Redline w/automatic transmission 2009
|-
|V||Saturn Sky Redline Ruby Red (Merlot Jewel) Special Edition w/automatic transmission 2009
|-
|X||Saturn Sky Redline Hydro Blue Special Edition w/automatic transmission 2009
|-
|G||Opel GT 2007-2010, Daewoo G2X 2007-2009
|-
|rowspan=8|GM L platform
|rowspan=8|L
|-
|D||Chevrolet Corsica ''Base'' 1994-1996
|-
|T||Chevrolet Corsica ''Base'' 1987-1989, Corsica ''LT'' 1990-1993
|-
|V||Chevrolet Beretta ''Base'' 1987-1996
|-
|W||Chevrolet Beretta &quot;GT&quot; 1989-1993 (RPO Z21) &amp; Beretta ''Z26'' 1994-1996 (RPO Z04)
|-
|Z||Chevrolet Corsica ''LTZ'' 1989-1990 (RPO Z54) 
|-
|Z||Chevrolet Beretta &quot;GTZ&quot; 1990-1993 (RPO Z04)
|-
|T||Pontiac Tempest (Canada only)
|-
|rowspan=5|GM M platform
|rowspan=5|M||R||Chevrolet Sprint
|-
|R||Geo Metro LSi, Metro
|-
|R||Pontiac Firefly (Canada only)
|-
|S||Chevrolet Sprint ER
|-
|S||Geo Metro, Metro XFi
|-
|rowspan=32|GM N platform
|rowspan=32|N
|-
|B||Oldsmobile Cutlass 1997, Cutlass ''GL'' 1998-1999
|-
|C||Buick Skylark 4-door ''Custom'' 1987-1991
|-
|D||Buick Skylark 4-door ''Limited'' 1987-1989, Skylark 4-door ''Luxury Edition'' 1990-1991
|-
|D||Chevrolet Malibu 1997-2003, Chevrolet Classic 2004-2005
|-
|E||Chevrolet Malibu ''LS'' 1997-2003
|-
|E||Pontiac Grand Am 1985-1988, Grand Am ''LE'' 1989-1991
|-
|E||Pontiac Grand Am ''SE'' 1992-2005
|-
|F||Oldsmobile Calais 1985-1987, Cutlass Calais 1988, Cutlass Calais ''S'' 1989-1991
|-
|F||Oldsmobile Achieva ''SL'' 1992-1994, Achieva ''SC'' 1994
|-
|F||Oldsmobile Alero ''GLS'' 1999-2004
|-
|F||Pontiac Grand Am ''SE1'' 2000-2004
|-
|G||Oldsmobile Cutlass ''GLS'' 1997-1999
|-
|G||Pontiac Grand Am 1991
|-
|G||Pontiac Grand Am ''SE2'' 2000, 2003-2004
|-
|J||Buick Somerset Regal 1985, Somerset ''Custom'' 1986-1987, Skylark 2-door ''Custom'' 1988-91, Skylark 4-door ''Custom'' 1986
|-
|J||Buick Skylark 1992, Skylark ''Limited'' 1993-1994, Skylark ''Custom'' 1996-1998,&lt;br /&gt; Skylark ''Limited'' &amp; ''Gran Sport'' 1996-1997
|-
|K||Buick Somerset ''T-Type'' 1986
|-
|K||Oldsmobile Cutlass Calais ''International Series'' 1988-1991
|-
|K||Oldsmobile Alero ''GX'' 1999-2004
|-
|L||Oldsmobile Cutlass Calais 1989-1991
|-
|L||Oldsmobile Achieva ''S'' 1992-1995, Achieva ''SL'' 1996-1998, Achieva ''SC'' 1996-1997
|-
|L||Oldsmobile Alero ''GL'' 1999-2004
|-
|M||Buick Somerset Regal ''Limited'' 1985, Somerset ''Limited'' 1986-'87, Skylark 2-door ''Limited'' '88-'89, Skylark 2-door ''Gran Sport'' 1990-1991, Skylark 4-door ''Limited'' 1986
|-
|M||Buick Skylark ''Gran Sport'' 1992-1994
|-
|T||Oldsmobile Calais ''Supreme'' 1985-1987, Cutlass Calais ''SL'' 1988-1991
|-
|V||Buick Skylark 1990-1991
|-
|V||Buick Skylark ''Custom'' 1993-1995, ''Limited'' 1995, ''Gran Sport'' 1995
|-
|V||Pontiac Grand Am ''LE'' 1985-1988
|-
|V||Pontiac Grand Am ''GT1'' 2000-2005
|-
|W||Pontiac Grand Am ''SE'' 1986-1991
|-
|W||Pontiac Grand Am ''GT'' 1992-2005
|-
|rowspan=5|GM P platform - rear-wheel drive
|rowspan=5|P
|-
||E||Pontiac Fiero ''Coupe'' 1985-1988
|-
||F||Pontiac Fiero ''SE'' 1985-1987
|-
||G||Pontiac Fiero ''GT'' 1985-1988
|-
||M||Pontiac Fiero ''Sport coupe'' 1985-1987
|-
|rowspan=1|GM P platform - front-wheel drive
|rowspan=1|P||X||General Motors EV1 1997, 1999
|-
|rowspan=6|GM R platform
|rowspan=6|R
|-
||F||1985-1986 Chevrolet Spectrum
|-
||F||1987-1988 Chevrolet Spectrum 3-door hatchback, 1989 Geo Spectrum 3-door hatchback
|-
||F||1990-1993 Geo Storm
|-
||G||1987-1988 Chevrolet Spectrum 4-door sedan, 1989 Geo Spectrum 4-door sedan
|-
||T||1990-1993 Geo Storm GSi
|-
|rowspan=8|GM S platform
|rowspan=8|S||K||1985-1988 Chevrolet Nova
|-
|K||1989-1997 Geo Prizm, 1998-2002 Chevrolet Prizm
|-
|L||1988 Chevrolet Nova Twin Cam, 1990-1992 Geo Prizm GSi
|-
|L||2003-2008 Pontiac Vibe, 2009-2010 Pontiac Vibe FWD w/manual transmission
|-
|M||2003-2006 Pontiac Vibe ''AWD'', 2009-2010 Pontiac Vibe AWD w/automatic transmission
|-
|N||2003-2006 Pontiac Vibe ''GT'', 2009-2010 Pontiac Vibe GT FWD w/manual transmission
|-
|P||2009-2010 Pontiac Vibe FWD w/automatic transmission
|-
|R||2009-2010 Pontiac Vibe GT FWD w/automatic transmission
|-
|rowspan=32|GM Sigma platform
|rowspan=32|D||A||Cadillac CTS Base model RWD 2010-2013, CTS Coupe Base model RWD 2014
|-
|B||Cadillac CTS Wagon Luxury Collection RWD 2014
|-
|C||Cadillac CTS Base model AWD 2010-2013, CTS Coupe/Wagon Performance Collection RWD 2014
|-
|D||Cadillac CTS Coupe/Wagon Premium Collection RWD 2014
|-
|E||Cadillac CTS Luxury Collection RWD 2010-2013, CTS Coupe Base model AWD 2014
|-
|F||Cadillac CTS Auto. Trans. RWD 2008-2009, CTS Luxury Collection RWD w/Navigation 2010-2013, CTS Wagon Luxury Collection AWD 2014
|-
|G||Cadillac CTS Auto. Trans. AWD 2008-2009, CTS Luxury Collection AWD 2010-2013, CTS Coupe/Wagon Performance Collection AWD 2014
|-
|H||Cadillac CTS Auto. Trans. AWD w/Navigation 2008-2009, CTS Luxury Collection AWD w/Navigation 2010-2013, CTS Coupe/Wagon Premium Collection AWD 2014
|-
|J||Cadillac CTS Auto. Trans. RWD w/Navigation 2008-2009, CTS Performance Collection RWD 2010-2013
|-
|K||Cadillac CTS Performance Collection RWD w/Navigation 2010-2013
|-
|L||Cadillac CTS Performance Collection AWD 2010-2013
|-
|M||Cadillac CTS V6 2003-2004, CTS 2.8L 2005-2007, CTS Man. Trans. RWD 2008-2009, CTS Performance Collection AWD w/Navigation 2010-2013
|-
|N||Cadillac CTS V-Series 2004-2007, 2009
|-
|P||Cadillac CTS 3.6L 2005-2007, CTS Direct Inj. V6 Man. Trans. RWD 2008-2009, CTS Premium Collection RWD w/Navigation 2010-2013
|-
|R||Cadillac CTS Direct Inj. V6 Auto. Trans. RWD 2008
|-
|S||Cadillac CTS Direct Inj. V6 Auto. Trans. AWD 2008-2009, CTS Premium Collection AWD w/Navigation 2010-2013 
|-
|T||Cadillac CTS Direct Inj. V6 Auto. Trans. AWD w/Navigation 2008-2009
|-
|U||Cadillac CTS Direct Inj. V6 Auto. Trans. RWD 2009
|-
|V||Cadillac CTS Direct Inj. V6 Auto. Trans. RWD w/Navigation 2008-2009, CTS sedan V-Series 2010-2014, CTS Wagon V-Series 2011-2014, CTS Coupe V-Series 2011-2015
|-
|0||Cadillac CTS Sport Appearance Pkg. 2010
|-
|1||Cadillac CTS Eco Luxury Pkg. 2010
|-
|2||Cadillac CTS Sport Appearance Pkg. 2011
|-
|A||Cadillac STS V6 AWD 2008-2009
|-
|B||Cadillac STS V8 AWD 2008-2009
|-
|C||Cadillac STS V8 2005-2007, STS V8 RWD 2008-2009
|-
|D||Cadillac STS V6 AWD w/Navigation 2008-2009
|-
|K||Cadillac STS V6 RWD w/Navigation 2008-2009
|-
|L||Cadillac STS V8 AWD w/Navigation 2008-2009
|-
|U||Cadillac STS (all models) 2010, STS (Base model) 2011 
|-
|W||Cadillac STS V6 2005-2007, STS V6 RWD 2008-2009, STS Luxury 2011
|-
|X||Cadillac STS V-Series 2006-2009, STS Luxury Performance 2011
|-
|Z||Cadillac STS V8 RWD w/Navigation 2008-2009
|-
|rowspan=4|GM T platform - rear-wheel drive
|rowspan=4|T||B|| 1985-1987 Chevrolet Chevette CS
|-
|B||1985-1987 Pontiac Acadian (Canada only)
|-
|J||1985 Pontiac Acadian Scooter (Canada only)
|-
|L||1985-1987 Pontiac 1000
|-
|rowspan=4|GM T platform - front-wheel drive
|rowspan=4|T||N|| Pontiac LeMans 1988, LeMans LE 1989-1991, LeMans SE 1992-1993
|-
|R||1988-1989 Pontiac LeMans SE sedan
|-
|S||1988-1990 Pontiac LeMans GSE AeroCoupe
|-
|X||1988-1993 Pontiac LeMans VL AeroCoupe
|-
|rowspan=3|GM T platform - front-wheel drive
|rowspan=3|A
|-
|R||Saturn Astra XE (US: 2008, Canada: 2008-2009)
|-
|T||Saturn Astra XR (US: 2008, Canada: 2008-2009)
|-
|rowspan=4|Daewoo T200 platform
|rowspan=4|T||D||Chevrolet Aveo Special Value 2004-2008, Base model 2004, LS 2005-2011, Aveo 1LT 2009-2011
|-
|G||Chevrolet Aveo LT 2005-2008, Aveo 2LT 2009-2011
|-
|J||Chevrolet Aveo LS 2004 
|-
|D||Pontiac G3 2009 
|-
|rowspan=2|GM V platform - front-wheel drive
|rowspan=2|V||R||1987-1992 Cadillac Allanté with standard removable hardtop
|-
|S||1990-1993 Cadillac Allanté 
|-
|rowspan=2|GM V platform - rear-wheel drive
|rowspan=2|V||R||1997-2001 Cadillac Catera
|-
|X||2004-2006 Pontiac GTO coupe
|-
|rowspan=49|GM W platform
|rowspan=49|W
|-
|A||Chevrolet Impala ''LS'' 2010-2013, Impala Limited ''LS'' 2014-2016
|-
|B||Chevrolet Impala ''LS'' 2006-2009, Impala ''LT'' 2010-2013, Impala Limited ''LT'' 2014-2016
|-
|C||Chevrolet Impala ''LT'' 3.9L 2006-2009, Impala ''LTZ'' 2010-2013, Impala Limited ''LTZ'' 2014-2016
|-
|D||Chevrolet Impala ''SS'' 2006-2009, Impala ''Police'' 2010-2013, Impala Limited ''Police'' 2014-2016
|-
|E||Chevrolet Impala ''Taxi'' 2010-2012
|-
|F||Chevrolet Impala 2000-2005, Impala ''LS'' Fleet (1FL) 2011-2013
|-
|G||Chevrolet Impala ''LT'' Fleet (2FL) 2011-2013
|-
|H||Chevrolet Impala ''LS'' 2000-2005
|-
|J||Chevrolet Monte Carlo ''LS'' 2006-2007
|-
|K||Chevrolet Monte Carlo ''LT'' 3.9L 2006, Monte Carlo ''LT'' 3.5L 2007
|-
|L||Chevrolet Lumina 1990-2001, Lumina ''LS'' 1997-1999
|-
|L||Chevrolet Monte Carlo ''SS'' 2006-2007
|-
|M||Chevrolet Monte Carlo ''LT'' 3.5L 2006
|-
|N||Chevrolet Lumina ''Euro'' 1990-1994, Lumina ''LS'' 1995-1996, Lumina ''LTZ'' 1997-1999
|-
|N||Chevrolet Monte Carlo ''LTZ'' 2006
|-
|P||Chevrolet Lumina ''Z34'' 1991-1994, Impala ''SS'' 2004-2005
|-
|S||Chevrolet Impala ''Police'' 2006-2009
|-
|T||Chevrolet Impala ''LT'' 3.5L 2006-2009
|-
|U||Chevrolet Impala ''LTZ'' 2006-2009
|-
|V||Chevrolet Impala ''50th Anniversary Edition'' 2008
|-
|W||Chevrolet Monte Carlo ''LS'' 1995-2005
|-
|X||Chevrolet Monte Carlo ''Z34'' 1995-1999, Monte Carlo ''SS'' 2000-2004, Monte Carlo ''LT'' 2005
|-
|Z||Chevrolet Monte Carlo ''SS Supercharged'' 2004-2005
|-
|C||Pontiac Grand Prix ''GXP'' 2005-2008
|-
|H||Pontiac Grand Prix ''LE'' 1991-1993
|-
|J||Pontiac Grand Prix 1988-1989, Grand Prix ''LE'' 1990, Grand Prix ''SE'' 1991-2000
|-
|K||Pontiac Grand Prix ''LE'' 1988-1989, Grand Prix ''SE1'' 2000-2003
|-
|P||Pontiac Grand Prix ''SE'' 1988-1990, Grand Prix ''GT'' 1991-1993, 1997-2003,&lt;br /&gt; Grand Prix ''GT1'' 2004, Grand Prix 2005-2008
|-
|R||Pontiac Grand Prix ''GTP'' 1999-2005, Grand Prix ''GT'' 2006-2007
|-
|S||Pontiac Grand Prix ''GT2'' 2004, Grand Prix ''GT'' 2005
|-
|T||Pontiac Grand Prix ''STE'' 1990-1993
|-
|H||Oldsmobile Cutlass Supreme 1988-1991, Cutlass Supreme ''S'' 1992-1994,&lt;br /&gt; Cutlass Supreme ''SL'' 1995-1997, Intrigue 1998, Intrigue ''GX'' 1999-2002
|-
|R||Oldsmobile Cutlass Supreme ''International Series'' 1988-1993
|-
|S||Oldsmobile Cutlass Supreme ''SL'' 1988-1991, Intrigue ''GL'' 1998-2002
|-
|T||Oldsmobile Cutlass Supreme Convertible 1990-1995
|-
|X||Oldsmobile Intrigue ''GLS'' 1998-2002
|-
|B||Buick Regal ''Custom'' 1988-1996, Regal ''GS'' Coupe 1995-1996, Regal ''LS'' 1997-2004
|-
|C||Buick Lacrosse ''CX'' 2005-2009
|-
|D||Buick Regal ''Limited'' 1988-1996, Lacrosse ''CXL'' 2005-2009
|-
|E||Buick Lacrosse ''CXS'' 2005-2008
|-
|F||Buick Regal ''GS'' Coupe 1992-1994, Regal ''GS'' Sedan 1992-2004 
|-
|F||Buick Allure ''CX'' 2005-2009 (Canada only) 
|-
|H||Buick Allure ''CXS'' 2005-2008 (Canada only)
|-
|J||Buick Allure ''CXL'' 2005-2009 (Canada only)
|-
|N||Buick Lacrosse ''Super'' 2008-2009
|-
|P||Buick Allure ''Super'' 2008-2009 (Canada only)
|-
|S||Buick Century ''Custom'' 1997-2005
|-
|Y||Buick Century ''Limited'' 1997-2002
|-
|rowspan=3|GM X platform
|rowspan=3|X||B||1985 Buick Skylark Custom
|-
|C||1985 Buick Skylark Limited
|-
|X||1985 Chevrolet Citation II
|-
|rowspan=39|GM Y platform
|rowspan=39|Y||V||2004-2009 Cadillac XLR
|-
|X||2006-2009 Cadillac XLR V-Series
|-
|Y||1985-2008 Chevrolet Corvette (all models except '90-'95 ZR-1)
|-
|Z||1990-1995 Chevrolet Corvette ZR-1
|-
|G||2009 Chevrolet Corvette GT1 Championship Edition (Base &amp; Z06)
|-
|R||2009 Chevrolet Corvette ZR1 (after early production)
|-
|Y||2009 Chevrolet Corvette (Base model, Early production Z06, Early production ZR1)
|-
|Z||2009 Chevrolet Corvette Z06 (after early production)
|-
|A||2010-2013 Chevrolet Corvette Standard 1LT Man. Trans.
|-
|B||2010-2013 Chevrolet Corvette Preferred 2LT Man. Trans.
|-
|C||2010-2013 Chevrolet Corvette Premium 3LT Man. Trans.
|-
|D||2010-2013 Chevrolet Corvette Custom 4LT Man. Trans.
|-
|E||2010-2013 Chevrolet Corvette Standard 1LT Auto. Trans.
|-
|F||2010-2013 Chevrolet Corvette Preferred 2LT Auto. Trans.
|-
|G||2010-2013 Chevrolet Corvette Premium 3LT Auto. Trans.
|-
|H||2010-2013 Chevrolet Corvette Custom 4LT Auto. Trans.
|-
|J||2010-2013 Chevrolet Corvette Z06 Standard 1LZ Man. Trans.
|-
|K||2010-2013 Chevrolet Corvette Z06 Premium 2LZ Man. Trans.
|-
|L||2010-2013 Chevrolet Corvette Z06 Custom 3LZ Man. Trans.
|-
|M||2010-2013 Chevrolet Corvette ZR1 Standard 1ZR Man. Trans.
|-
|N||2010-2013 Chevrolet Corvette ZR1 Custom 3ZR Man. Trans.
|-
|P||2010-2013 Chevrolet Corvette Grand Sport Standard 1LT Man. Trans.
|-
|R||2010-2013 Chevrolet Corvette Grand Sport Preferred 2LT Man. Trans.
|-
|S||2010-2013 Chevrolet Corvette Grand Sport Premium 3LT Man. Trans.
|-
|T||2010-2013 Chevrolet Corvette Grand Sport Custom 4LT Man. Trans.
|-
|U||2010-2013 Chevrolet Corvette Grand Sport Standard 1LT Auto. Trans.
|-
|V||2010-2013 Chevrolet Corvette Grand Sport Preferred 2LT Auto. Trans.
|-
|W||2010-2013 Chevrolet Corvette Grand Sport Premium 3LT Auto. Trans.
|-
|X||2010-2013 Chevrolet Corvette Grand Sport Custom 4LT Auto. Trans.
|-
|Y||2013 Chevrolet Corvette 427 Convertible Collector Edition Premium 3LT Man. Trans.
|-
|Z||2013 Chevrolet Corvette 427 Convertible Collector Edition Custom 4LT Man. Trans.
|-
|1||2013 Chevrolet Corvette 60th Anniversary Edition Custom 4LT Man. Trans.
|-
|2||2013 Chevrolet Corvette 60th Anniversary Edition Custom 4LT Auto. Trans.
|-
|3||2013 Chevrolet Corvette Grand Sport 60th Anniversary Edition Custom 4LT Man. Trans.
|-
|4||2013 Chevrolet Corvette Grand Sport 60th Anniversary Edition Custom 4LT Auto. Trans.
|-
|5||2013 Chevrolet Corvette Z06 60th Anniversary Edition Custom 3LZ Man. Trans.
|-
|6||2013 Chevrolet Corvette ZR1 60th Anniversary Edition Custom 3ZR Man. Trans.
|-
|7||2013 Chevrolet Corvette 427 Convertible 60th Anniversary Edition Custom 4LT Man. Trans.
|-
|8||2013 Chevrolet Corvette 427 Convertible Collector Edition Preferred 2LT Man. Trans.
|-
|rowspan=13|GM Z platform
|rowspan=13|Z
|-
|E||Saturn SC1 (manual transmission 2-Door) 1993-1999
|-
|F||Saturn SC1 (automatic transmission 2-Door) 1993-1999, SL (manual transmission) 1991-02
|-
|G||Saturn SC (manual transmission) 1991-1992, SC2 (manual transmission 2-Door) 1993-99,&lt;br /&gt; SL1 (manual transmission) 1991-2002, SW1 (manual transmission) 1993-1999
|-
|H||Saturn SC (automatic transmission) 1991-92, SC2 (automatic transmission 2-Door) '93-'99,&lt;br /&gt; SL1 (automatic transmission) 1991-02, SW1 (automatic transmission LHD) '93-'99
|-
|J||Saturn SL2 (manual transmission) 1991-2002, SW2 (manual transmission) 1993-2001
|-
|K||Saturn SL2 (automatic transmission) 1991-2002, SW2 (automatic transmission 1993-1999) 
|-
|M||Saturn SW1 &quot;Postal&quot; [SWP] (automatic transmission RHD) 1999-2001 &lt;br&gt;(Made for US Postal Service rural route mail carriers)
|-
|N||Saturn SC1 (manual transmission 3-Door) 1999-2002, SW2 (automatic transmission 2000-01)
|-
|P||Saturn SC1 (automatic transmission 3-Door) 1999-2002
|-
|R||Saturn SC2 (manual transmission 3-Door) 1999-2002
|-
|S||Saturn SL Spring Special 2002
|-
|Y||Saturn SC2 (automatic transmission 3-Door) 1999-2002
|-
|rowspan=3|GM Zeta platform (VE)
|rowspan=3|E||C||Pontiac G8 GT
|-
|P||Pontiac G8 GXP
|-
|R||Pontiac G8 (Base model)
|-
|rowspan=2|GM Zeta platform (VF)
|rowspan=2|F||1||2014-2017 Chevrolet SS w/automatic transmission
|-
|2||2015-2017 Chevrolet SS w/manual transmission
|-
|GM Zeta platform (WM)
|M||K||2011-2013 Chevrolet Caprice PPV
|-
|GM Zeta platform (WN)
|N||S||2014-2017 Chevrolet Caprice PPV
|-
|rowspan=19|GM Zeta platform (models formerly on F platform)
|rowspan=19|F||A||Chevrolet Camaro ''LS'' automatic transmission 2010-2011, ''2LS'' automatic transmission 2012-2014, ''LS'' manual transmission 2015
|-
|B||Chevrolet Camaro ''LT'' automatic transmission 2010-2014, ''2LS'' automatic transmission 2015
|-
|C||Chevrolet Camaro ''2LT'' automatic transmission 2010-2014, ''LT'' manual transmission 2015
|-
|D||Chevrolet Camaro ''LT'' automatic transmission 2015
|-
|E||Chevrolet Camaro ''LS'' manual transmission 2010-2014, ''2LT'' manual transmission 2015
|-
|F||Chevrolet Camaro ''LT'' manual transmission 2010-2014, ''2LT'' automatic transmission 2015
|-
|G||Chevrolet Camaro ''2LT'' manual transmission 2010-2014, ''SS'' manual transmission 2015
|-
|H||Chevrolet Camaro ''SS'' automatic transmission 2015
|-
|J||Chevrolet Camaro ''SS'' automatic transmission 2010-2014. Note: Must have &quot;J&quot; in 8th position of VIN.
|-
|J||Chevrolet Camaro ''ZL1'' automatic transmission 2012. Note: Must have &quot;P&quot; in 8th position of VIN.
|-
|J||Chevrolet Camaro ''2SS'' manual transmission 2015
|-
|K||Chevrolet Camaro ''2SS'' automatic transmission 2010-2015
|-
|L||Chevrolet Camaro ''ZL1'' automatic transmission 2013-2014, ''ZL1'' manual transmission 2015
|-
|M||Chevrolet Camaro ''ZL1'' automatic transmission 2015
|-
|S||Chevrolet Camaro ''SS'' manual transmission 2010-2014. Note: Must have &quot;W&quot; in 8th position of VIN.
|-
|S||Chevrolet Camaro ''ZL1'' manual transmission 2012. Note: Must have &quot;P&quot; in 8th position of VIN.
|-
|S||Chevrolet Camaro ''Z/28'' manual transmission 2014. Note: Must have &quot;E&quot; in 8th position of VIN.
|-
|T||Chevrolet Camaro ''2SS'' manual transmission 2010-2014
|-
|Z||Chevrolet Camaro ''ZL1'' manual transmission 2013-2014, ''Z/28'' manual transmission 2015
|-
|}

RHD= Right-Hand Drive

====Model Line 2010- Passenger Car (Using Vehicle Platforms introduced 2010 or later)====
The Model Line is specified as character 4 of the American GM VIN for Passenger Cars.

{| border=1 style=&quot;margin:auto;&quot;
!VIN
!Description
|-
|A||Cadillac ATS 2013-2019
|-
|A||Cadillac CTS sedan 2014-2019, CTS V-Series sedan 2016-2019
|-
|B||Chevrolet Cruze 2016-2019
|-
|C||Chevrolet Spark 2013-2022, Spark EV 2014-2016
|-
|D||Cadillac CT4 2020-2026
|-
|D||Cadillac CT5 2020-
|-
|F||Chevrolet Camaro 2016-2024
|-
|F||Chevrolet Bolt EV 2017-2023, Bolt EUV 2022-2023, Bolt 2027
|-
|G||Buick LaCrosse 2010-2016
|-
|G||Buick Regal 2011-2020, Buick Regal TourX 2018-2020
|-
|J||Chevrolet Sonic 2016-2020
|-
|K||Cadillac CT6 2016-2020
|-
|M||Cadillac Celestiq EV 2025-
|-
|P||Buick Verano 2012-2017
|-
|P||Chevrolet Cruze 2011-2015, Cruze Limited 2016
|-
|R||Cadillac ELR 2014, 2016
|-
|R||Chevrolet Volt 2011-2019
|-
|W||Buick Cascada 2016-2019
|-
|Y||Chevrolet Corvette 2014-
|-
|Z||Buick LaCrosse 2017-2019
|-
|Z||Chevrolet Malibu 2016-2025
|-
|1||Cadillac XTS 2013-2019
|-
|1||Chevrolet Impala 2014-2020
|-
|1||Chevrolet Malibu 2013-2015, Malibu Limited 2016
|-
|}

===Body style codes 1987- Passenger Car===
The Body type is specified as character 6 of the American GM VIN for passenger cars.

{| border=1 style=&quot;margin:auto;&quot;
!VIN
!Description
|-
|1||Two-Door Coupe/Sedan
|-
|2||Two-Door Hatchback
|-
|3||Two-Door Convertible
|-
|4||Two-Door Wagon ('91-'92 Geo Storm Hatchback)
|-
|5||Four-Door Sedan
|-
|6||Four-Door Hatchback
|-
|7||Four-Door Hatchback ('89-'90 Geo Prizm hatchback)
|-
|8||Four-Door Station Wagon
|-
|9||Four-Door Station Wagon - High Roof Monocab
|}

===American restraint types 1987-===
The restraint type is specified as character 7 of the American GM VIN for passenger cars.

{{center/top}}
====Restraint codes for passenger cars 1987-2009==== 
{{center/end}}

{| border=1 style=&quot;margin:auto;&quot;
!VIN Code
!Description
|-
|1||Active (Manual) belts 1987-1996
|-
|2||Active (Manual) belts plus driver and passenger front airbags 1992-2005&lt;br /&gt;(For '94-'96 Pontiac Grand Prix coupe: Passive (Automatic) belts plus driver and passenger front airbags)
|-
|3||Active (Manual) belts plus driver side front airbag 1988-1996 &lt;br /&gt;(For '94 Geo Prizm: Active (Manual) belts plus driver and passenger front airbags)
|-
|4||Passive (Automatic) belts 1987-1996
|-
|4||Active (Manual) belts plus driver and passenger front &amp; side airbags 1997-2005
|-
|4||Active (Manual) belts plus driver and passenger front &amp; side curtain airbags 2006-2009
|-
|5||Passive (Automatic) belts plus driver side front airbag 1992-1996
|-
|5||Active (Manual) belts plus driver and passenger front airbags &amp; driver-side side impact airbag 2000-2005
|-
|5||Active (Manual) belts plus driver and passenger front airbags &amp; occupant sensor 2006-2009
|-
|6||Passive (Automatic) belts plus driver and passenger front airbags 1994-1996
|-
|6||Active (Manual) belts plus driver and passenger front &amp; side airbags &amp; occupant sensor 2000-2009
|-
|7||Active (Manual) belt driver &amp; Passive (Automatic) belt passenger plus driver and passenger front airbags 1996
|-
|7||Active (Manual) belts plus driver and passenger front &amp; side airbags &amp; rear side airbags 2000-2005
|-
|7||Active (Manual) belts plus driver and passenger front &amp; side &amp; side curtain airbags &amp; occupant sensor 2006-2009
|-
|8||Active (Manual) belts plus driver and passenger front &amp; side curtain airbags &amp; occupant sensor 2006-2009
|-
|9||
|}

{{center/top}}
====Restraint codes for passenger cars 2010-==== 
{{center/end}}

{| border=1 style=&quot;margin:auto;&quot;
!VIN Code
!Description
|-
|D||Active (Manual) belts plus driver and passenger front &amp; side airbags 2010-
|-
|E||Active (Manual) belts plus driver and passenger front &amp; side &amp; side curtain airbags 2010-2017, 2027
|-
|F||Active (Manual) belts plus driver and passenger front &amp; side curtain airbags 2010
|-
|G||Active (Manual) belts plus driver and passenger front &amp; side &amp; rear side &amp; side curtain airbags 2010-2017
|-
|N||Active (Manual) belts plus driver and passenger front &amp; side &amp; front knee airbags 2016-2019
|-
|R||Active (Manual) belts plus driver and passenger front &amp; side &amp; side curtain &amp; front knee airbags 2012-
|-
|S||Active (Manual) belts plus driver and passenger front &amp; side &amp; rear side &amp; side curtain &amp; front knee airbags 2011-
|-
|T||Active (Manual) belts plus driver and passenger front &amp; side &amp; front row side curtain airbags 2011
|-
|U||Active (Manual) belts plus driver and passenger front &amp; side &amp; front row side curtain &amp; front knee airbags 2012-2017
|}

{{center/top}}
====Restraint codes for light trucks 2010-==== 
{{center/end}}

{| border=1 style=&quot;margin:auto;&quot;
!VIN Code
!Description
|-
|A||Active (Manual) belts plus driver-side front airbag 2010
|-
|B||Active (Manual) belts plus driver-side front airbag 2011-
|-
|B||Active (Manual) belts plus driver and passenger front airbags 2010
|-
|C||Active (Manual) belts plus driver and passenger front airbags 2011-
|-
|C||Active (Manual) belts plus driver and passenger front &amp; side airbags 2010
|-
|D||Active (Manual) belts plus driver and passenger front &amp; side airbags 2011-
|-
|D||Active (Manual) belts plus driver and passenger front airbags &amp; side curtain airbags for up to 3 rows of seating 2010
|-
|E||Active (Manual) belts plus driver and passenger front &amp; side &amp; side curtain airbags 2010-
|-
|F||Active (Manual) belts plus driver and passenger front airbags &amp; side curtain airbags for up to 3 rows of seating 2011-2015
|-
|F||Active (Manual) belts plus driver and passenger front &amp; side airbags &amp; side curtain airbags for up to 3 rows of seating 2016-
|-
|H||Active (Manual) belts plus driver-side front airbag &amp; driver-side side-impact airbag &amp; driver-side side curtain airbag 2023-2024
|-
|K||Active (Manual) belts plus driver and passenger front &amp; side &amp; side curtain &amp; front center airbags 2013-
|-
|L||Active (Manual) belts plus driver and passenger front &amp; side &amp; side curtain &amp; front center &amp; driver-side knee airbags 2017-2023
|-
|M||Active (Manual) belts plus driver and passenger front &amp; side &amp; side curtain &amp; front center &amp; front knee airbags 2025-
|-
|R||Active (Manual) belts plus driver and passenger front &amp; side &amp; side curtain &amp; front knee airbags 2017-
|-
|S||Active (Manual) belts plus driver and passenger front &amp; side &amp; rear side &amp; side curtain &amp; front knee airbags 2013-
|-
|T||Active (Manual) belts plus driver-side front airbag &amp; driver- and passenger-side side-impact airbags &amp; side curtain airbags 2023-
|-
|U||Active (Manual) belts plus driver and passenger front &amp; side &amp; front row side curtain &amp; front knee airbags 2013-2019
|}

===American engine codes 1981-===
GM encodes the engine type in character 8 of the VIN. The following table outlines the various engines encoded there:

====Engine codes for passenger cars==== 

Warning: Issues with decoding are related to year/model combinations. Each year has a different breakdown for each code along with plants and some model/trim breakdowns over years.

Entry: 1985-1988 Pontiac Fiero has a 9 engine code for the 2.8L L44 V6. Entry: 1986-1990 Cadillac Brougham, Oldsmobile 307 Cu. In. V8 vin code Y.


{| border=1 style=&quot;margin:auto;&quot;
!VIN
!RPO
!Size
!Type
!Fuel
!Valvetrain
!Engine Family/Notes/Applications
|-
|A||LD5||3.8&amp;nbsp;L||V6||2 Barrel Carburetor |2BBL||OHV||Buick V6. (231 cu. in.) '81 Chevy Camaro (CA), Pontiac Catalina, Firebird, LeMans, Buick Century,&lt;br /&gt; '81-'83 Chevy Malibu (CA), '81-'84 Monte Carlo, Caprice, Impala (CA), '81-'87 Pontiac Grand Prix, Oldsmobile Cutlass/Cutlass Supreme, Buick Regal, '81-'85 Oldsmobile Delta 88, Buick LeSabre,&lt;br /&gt; '81-'86 Pontiac Bonneville, '84 Parisienne
|-
|A||LG0||2.3&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 16 valve||Oldsmobile Quad 4 H.O. '89-'94 Pontiac Grand Am, '89-'91 Oldsmobile Cutlass Calais, '92-'94 Achieva, '90 Cutlass Supreme, '90-'94 Chevy Beretta
|-
|A||LH2||4.6&amp;nbsp;L||V8||Fuel injection#Sequential Multi-port injection|SFI||DOHC,&lt;br /&gt; 32 valve||Cadillac Northstar V8 (For RWD) (Premium V). '04-'09 Cadillac XLR, '05-'10 Cadillac STS
|-
|A||LCV||2.5&amp;nbsp;L||Straight-4|I4||Direct Injection|DI||DOHC,&lt;br /&gt; 16 valve||GM Ecotec engine, Gen III. VVT. '13 Chevy Malibu, '16 Malibu Limited, '16-'19 Impala,&lt;br /&gt; '13-'16 Cadillac ATS
|-
|A||LV7||1.4&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 16 valve||GM Small Gasoline Engine. VVT. Made in Changwon, S. Korea. '16-'22 Chevy Spark.
|-
|B||LG2||3.8&amp;nbsp;L||V6||Fuel injection#Sequential Multi-port injection|SFI||OHV||Buick V6. '86 Oldsmobile 98, Toronado, Buick Electra, Riviera.
|-
|B||L26||4.9&amp;nbsp;L||V8||Fuel injection#Multi-port fuel injection|MFI||OHV||Cadillac High Technology V8.&lt;br /&gt; '91-'93 Cadillac Eldorado, Seville, '91-'95 DeVille, '91-'92 Fleetwood, '91-'93 Sixty Special
|-
|B||LE5||2.4&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 16 valve||GM Ecotec Gen II. VVT. '06-'08 Chevy Cobalt, '06-'07 Saturn Ion, '06-'10 Pontiac G6, Solstice,&lt;br /&gt; '07-'08 Pontiac G5, '07-'10 Saturn Sky, '08-'09 Saturn Aura, '08-'10 Chevy Malibu
|-
|B||LUV||1.4L||I4 Turbo||Fuel injection#Sequential Multi-port fuel injection|SFI||DOHC,&lt;br /&gt; 16 valve||GM Family 0 Engine, Gen III. VVT. '12-'20 Chevy Sonic, '13-'15 Chevy Cruze, '16 Cruze Limited
|-
|C||L17||1.6&amp;nbsp;L||Straight-4|I4||2 Barrel Carburetor |2BBL||SOHC,&lt;br /&gt; 8 valve||Isuzu G161Z engine made by GM in US. '82-'87 Chevy Chevette, Pontiac T1000/1000
|-
|C||LN3||3.8&amp;nbsp;L||V6||Fuel injection#Multi-port fuel injection|MFI||OHV||Buick V6 (3800). '88-'90 Oldsmobile 98, Toronado, Buick Electra, Riviera, Reatta, &lt;br /&gt; '88-'91 Buick LeSabre, Oldsmobile Delta 88/Eighty Eight, Pontiac Bonneville
|-
|C||L47||4.0&amp;nbsp;L||V8||Fuel injection#Sequential Multi-port injection|SFI||DOHC,&lt;br /&gt; 32 valve||Oldsmobile Aurora V8 (Premium V). Oldsmobile Aurora '95-'99, Aurora 4.0 '01-'03
|-
|C||LS4||5.3 L||V8||Fuel injection#Sequential Multi-port injection|SFI||OHV||Gen IV Chevrolet Small-Block V8. Aluminum Block &amp; Heads. Active Fuel Management.&lt;br /&gt; Transversely mounted for FWD. '05-'08 Pontiac Grand Prix GXP, '06-'07 Chevy Monte Carlo SS,&lt;br /&gt; '06-'09 Chevy Impala SS, '08-'09 Buick LaCrosse Super.
|-
|C||LAF||2.4&amp;nbsp;L||Straight-4|I4||Direct Injection|DI||DOHC,&lt;br /&gt; 16 valve||GM Ecotec engine, Gen II. VVT. Buick LaCrosse '10-'11, Regal '11. 
|-
|C||LUJ||1.4L||I4 Turbo||Fuel injection#Sequential Multi-port fuel injection|SFI||DOHC,&lt;br /&gt; 16 valve||GM Family 0 Engine, Gen III. VVT. Early production engines were made in Aspern, Austria; later made in Flint, MI. '12 Chevy Cruze
|-
|D||LJ5||1.8&amp;nbsp;L||Straight-4|I4||Indirect injection Diesel||SOHC,&lt;br /&gt; 8 valve||Isuzu 4FB1 diesel engine imported from Japan. '81-'86 Chevy Chevette
|-
|D||LD2||2.3&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 16 valve||Oldsmobile Quad 4. '88-'95 Pontiac Grand Am, '88-'91 Oldsmobile Cutlass Calais, '92-'95 Achieva,&lt;br /&gt; '88-'91 &amp;'95 Buick Skylark, '90-'91 Pontiac Grand Prix, Oldsmobile Cutlass Supreme,&lt;br /&gt; '95 Chevy Cavalier, Pontiac Sunfire
|-
|D||LC3||4.4&amp;nbsp;L||V8 Supercharged||Fuel injection#Sequential Multi-port point injection|SFI||DOHC,&lt;br /&gt; 32 valve||Cadillac Northstar V8 (Premium V). '06-'09 Cadillac XLR V-Series, Cadillac STS V-Series
|-
|E||LK9||3.0&amp;nbsp;L||V6||2 Barrel Carburetor |2BBL||OHV||Buick V6. '82-'85 Oldsmobile Cutlass Ciera, Buick Century, '85 Oldsmobile 98, Buick Electra
|-
|E||LA1||3.4&amp;nbsp;L||V6||Fuel injection#Sequential Multi-port point injection|SFI||OHV||Chevrolet 60° V6. '99-'05 Grand Am, '99-'04 Alero, '00-'05 Impala, Monte Carlo
|-
|E||L03||5.0&amp;nbsp;L||V8||Fuel injection#Throttle Body injection|TBI||OHV||Gen I Chevy Small-Block V8 (305 cu. in.). '88-'92 Camaro/Firebird, '89-'93 Chevy Caprice,&lt;br /&gt; '91 Buick Roadmaster Estate wagon, '91-'92 Oldsmobile Custom Cruiser, Cadillac Brougham.
|-
|E||LXV||1.6&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 16 valve||Family 1 Gen 3 engine. W/VVT. '09-'11 Chevy Aveo, '09 Pontiac G3
|-
|E||LS7||7.0&amp;nbsp;L||V8||Fuel injection#Sequential Multi-port point injection|SFI||OHV||Gen IV Chevy Small-Block V8. Aluminum Block &amp; Heads.&lt;br /&gt; '06-'13 Corvette Z06, '13 Corvette 427, '14-'15 Camaro Z/28
|-
|E||LH7||1.6&amp;nbsp;L||I4 Turbo||Direct injection &lt;br /&gt; Common-rail Diesel||DOHC,&lt;br /&gt; 16 valve||GM Medium Diesel engine (&quot;Whisper Diesel&quot;). Made by Opel in Szentgotthárd, Hungary.&lt;br /&gt; Aluminum Block &amp; Heads. '17-'19 Chevy Cruze Diesel.
|-
|F||LV8||4.3&amp;nbsp;L||V8||2 Barrel Carburetor |2BBL||OHV||Oldsmobile &quot;Rocket&quot; V8 (260 cu. in.) '81 Oldsmobile Cutlass, Delta 88.
|-
|F||L61||2.2&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 16 valve||GM Ecotec Gen I. '00-'04 Saturn L-Series, '02-'05 Chevy Cavalier, Pontiac Sunfire, Grand Am,&lt;br /&gt; '02-'04 Oldsmobile Alero, '03-'06 Saturn Ion, '04-'06 Chevy Malibu, '05-'06 Chevy Cobalt
|-
|F||L61||2.2&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 16 valve||GM Ecotec Gen II. '07-'08 Chevy Cobalt, Malibu, Pontiac G5, '07 Saturn Ion.
|-
|F||LB9||5.0&amp;nbsp;L||V8||Tuned-port fuel injection|TPI||OHV||Gen I Chevy Small-Block V8. (305 cu. in.). '85-'92 Chevy Camaro, Pontiac Firebird.
|-
|G||L46||1.8&amp;nbsp;L||I4||2 Barrel Carburetor |2BBL||OHV||Chevrolet &quot;122&quot; engine. '82 J-cars.
|-
|G||L69||5.0&amp;nbsp;L||V8||4 Barrel Quadrajet Carburetor |4BBL||OHV||Gen I Chevy Small-Block V8 (High Output 5.0L). (305 cu. in.)&lt;br /&gt; '84-'86 Camaro/Firebird, '84-'88 Chevy Monte Carlo SS
|-
|G||LM3||2.2&amp;nbsp;L||I4||Fuel injection#Throttle Body injection|TBI||OHV||Chevrolet &quot;122&quot; engine. '90-'91 Chevy Cavalier &amp; Corsica/Beretta.
|-
|G||LS1||5.7&amp;nbsp;L||V8||Fuel injection#Multi-port fuel injection|MFI||OHV||Gen III Chevy Small-Block V8. (346 cu. in.) Aluminum Block &amp; Heads.&lt;br /&gt; '97-'04 Corvette, '98-'02 Camaro/Firebird, '04 Pontiac GTO
|-
|G||LF1||3.0L||V6||Direct Injection|DI||DOHC,&lt;br /&gt; 24 valve||GM High Feature V6. VVT. 2010 Buick LaCrosse, Cadillac CTS
|-
|G||LWE||1.8&amp;nbsp;L||Straight-4|I4||Fuel injection#Sequential Multi-port fuel injection|SFI||DOHC,&lt;br /&gt; 16 valve||GM Family 1 engine, Gen III. VVT. PZEV emissions.&lt;br /&gt; '13-'15 Chevy Cruze, '16 Cruze Limited, '13-'18 Sonic.
|-
|H||LG4||5.0&amp;nbsp;L||V8||4 Barrel Quadrajet Carburetor |4BBL||OHV||Gen I Chevy Small-Block V8. (305 cu. in.) '81-'87 F-bodies, '81-'83 Chevy Malibu, '81-'85 Impala,&lt;br /&gt; '81-'88 Caprice, Monte Carlo, '83-'86 Pontiac Bonneville, Parisienne, '83-'87 Grand Prix
|-
|H||LE4||2.0&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port fuel injection|MFI||SOHC,&lt;br /&gt; 8 valve||GM Family II engine. Made in Brazil. '92-'94 Pontiac Sunbird. 
|-
|H||LX5||3.5&amp;nbsp;L||V6||Fuel injection#Sequential Multi-port injection|SFI||DOHC,&lt;br /&gt; 24 valve||Oldsmobile &quot;Shortstar&quot; V6 (Premium V). Oldsmobile Intrigue '99-'02, Aurora 3.5 '01-'02.
|-
|H||LAP||2.2&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 16 valve||GM Ecotec Gen II. VVT. '09 Chevy Cobalt, Pontiac G5.
|-
|H||LUW||1.8&amp;nbsp;L||Straight-4|I4||Fuel injection#Sequential Multi-port fuel injection|SFI||DOHC,&lt;br /&gt; 16 valve||GM Family 1 engine, Gen III. VVT. '11-'15 Chevy Cruze, '16 Cruze Limited, '12-'18 Sonic.
|-
|J||L39||4.4&amp;nbsp;L||V8||2 Barrel Carburetor |2BBL||OHV||Gen I Chevy Small-Block V8 (267 cu. in.) '81-'82 Chevy Caprice, Impala, Malibu, Monte Carlo,&lt;br /&gt; '81 Chevy Camaro
|-
|J||LA5||1.8&amp;nbsp;L||Straight-4|I4 Turbo||Fuel injection#Multi-port fuel injection|MFI||SOHC,&lt;br /&gt; 8 valve||GM Family II engine. Made in Brazil. '84-'86 Pontiac Sunbird, Buick Skyhawk. 
|-
|J||LT5||5.7&amp;nbsp;L||V8||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 32 valve||Based on Chevy Small-Block V8. Designed with Lotus Engineering.&lt;br /&gt; Made by Mercury Marine. Aluminum Block &amp; Heads. '90-'95 Corvette ZR-1
|-
|J||LG8||3.1&amp;nbsp;L||V6||Fuel injection#Sequential Multi-port injection|SFI||OHV||Chevrolet 60° V6. Gen III. 3100. '99-'03 Chevy Malibu, '99 Oldsmobile Cutlass, '00-'01 Chevy Lumina,&lt;br /&gt; '00-'03 Pontiac Grand Prix SE, '00-'05 Buick Century
|-
|J||L99||6.2&amp;nbsp;L||V8||Fuel injection#Sequential Multi-port injection|SFI||OHV||Gen IV Chevy Small-Block V8. VVT. With Active Fuel Management. Aluminum Block &amp; Heads.&lt;br /&gt; '10-'15 Camaro SS (auto. trans.)
|-
|J||LTA||4.2&amp;nbsp;L||V8 Twin Turbo||Direct injection|DI||DOHC,&lt;br /&gt; 32 valve||Cadillac Blackwing V8. VVT. '19-'20 Cadillac CT6 Platinum &amp; V-series
|-
|K||LC3||3.8&amp;nbsp;L||V6||2 Barrel Carburetor |2BBL||OHV||Chevrolet 90° V6 (Chevy Small-Block V8 Derived). 229 cu. in. &lt;br /&gt; '81-'82 Malibu, Monte Carlo, Impala, Caprice, '81 Camaro.
|-
|K||LC5||1.5&amp;nbsp;L||I4||2 Barrel Carburetor |2BBL||SOHC,&lt;br /&gt; 8 valve||Isuzu 4XC1 engine. '85 Chevrolet Spectrum.
|-
|K||LT2||2.0&amp;nbsp;L||Straight-4|I4||Fuel injection#Throttle Body injection|TBI||SOHC,&lt;br /&gt; 8 valve||GM Family II engine. Made in Brazil.&lt;br /&gt; '87-'91 Pontiac Sunbird, '87-'88 Oldsmobile Firenza, Buick Skyhawk. 
|-
|K||LT2||2.0&amp;nbsp;L||Straight-4|I4||Fuel injection#Throttle Body injection|TBI||SOHC,&lt;br /&gt; 8 valve||GM Family II engine. Made in Australia by Holden.&lt;br /&gt; '89-'90 Pontiac LeMans GSE Aerocoupe, '89 LeMans SE sedan
|-
|K||L36||3.8&amp;nbsp;L||V6||Fuel injection#Sequential Multi-port injection|SFI||OHV||Buick V6 (3800 Series II). '95-'05: Various W-, H-, C-, &amp; G-body models. '95-'02 Camaro/Firebird.
|-
|K||LZE||3.5L||V6||Fuel injection#Sequential Multi-port injection|SFI||OHV||GM High Value 60° V6. 3510cc. VVT. Flex-Fuel E85 compatible.&lt;br /&gt; '06-'07 Chevy Monte Carlo, '06-'11 Chevy Impala, '09-'10 Chevy Malibu, Pontiac G6
|-
|K||LEA||2.4&amp;nbsp;L||Straight-4|I4||Direct Injection|DI||DOHC,&lt;br /&gt; 16 valve||E85 Flex Fuel. GM Ecotec engine, Gen II. VVT. Buick Regal, Verano '12-'17 (except '13 Regal). 
|-
|K||LSY||2.0&amp;nbsp;L||Straight-4|I4 Turbo||Direct Injection|DI||DOHC,&lt;br /&gt; 16 valve||GM Ecotec engine, Gen III. Active Fuel Management. VVT. VVL.&lt;br /&gt; '19 Cadillac CT6, '20+ Cadillac CT4, CT5
|-
|L||LM1||5.7&amp;nbsp;L||V8||4 Barrel Carburetor |4BBL||OHV||Gen I Chevy Small-Block V8.&lt;br&gt; '81 Camaro Z28 (only w/auto. trans. in US), '81-'82 Impala 9C1 Police, '81 Malibu 9C1 Police
|-
|L||LL1||2.8&amp;nbsp;L||V6||2 Barrel Carburetor |2BBL||OHV||Chevrolet 60° V6 H.O. (longitudinally mounted). '83-'84 Pontiac Firebird.
|-
|L||LN7||3.0&amp;nbsp;L||V6||Fuel injection#Multi-port fuel injection|MFI||OHV||Buick V6. '85-'87 Pontiac Grand Am, '85-'88 Oldsmobile &amp; Buick N-bodies,&lt;br /&gt; '86 Oldsmobile Delta 88, Buick LeSabre
|-
|L||L27||3.8&amp;nbsp;L||V6||Fuel injection#Tuned port injection|TPI||OHV||Buick V6 (3800 Series I). '90-'95 Buick Regal, '91-'94 Oldsmobile 98, Buick Park Avenue, '91 Reatta, '91-'93 Riviera, '91-'92 Oldsmobile Toronado, '92-'95 Buick LeSabre, '92-'94 Pontiac Bonneville, Oldsmobile 88
|-
|L||LNK||1.8&amp;nbsp;L||Straight-4|I4||Fuel injection#Sequential multi-port injection|SFI||DOHC,&lt;br /&gt; 16 valve||Toyota 2ZZ-GE engine. VVTL-i. '03-'06 Pontiac Vibe GT
|-
|L||LKW||2.5&amp;nbsp;L||Straight-4|I4||Direct Injection|DI||DOHC,&lt;br /&gt; 16 valve||GM Ecotec engine, Gen III. VVT. VVL. '14-'15 Chevy Malibu, Impala
|-
|L||L3B||2.7L||I4 Turbo||Direct Injection|DI||DOHC,&lt;br /&gt; 16 valve||GM L3B Tripower engine. VVT, VVL. Active Fuel Management. '20+ Cadillac CT4, CT4-V
|-
|M||LY9||1.0&amp;nbsp;L||Straight-3|I3||2BBL||SOHC,&lt;br /&gt; 6 valve ||Suzuki G10A engine. '85 Chevrolet Sprint
|-
|M||LT3||2.0&amp;nbsp;L||Straight-4|I4 Turbo||Fuel injection#Multi-port fuel injection|MFI||SOHC,&lt;br /&gt; 8 valve||GM Family II engine. Made in Brazil.&lt;br /&gt; '87-'90 Pontiac Sunbird, '87 Buick Skyhawk T-Type, '87-'89 Pontiac Grand Am SE. 
|-
|M||L82||3.1&amp;nbsp;L||V6||Fuel injection#Sequential Multi Port Fuel injection|SFI||OHV||Chevrolet 60° V6 (transversely mounted). Gen III. 3100. '93-'97 Oldsmobile Cutlass Supreme,&lt;br /&gt; '94-'98 Pontiac Grand Am, Oldsmobile Achieva, Buick Skylark, '94-'99 Pontiac Grand Prix,&lt;br /&gt; '94-'96 Chevy Corsica/Beretta, Oldsmobile Cutlass Ciera, Buick Regal, '94-'99 Century,&lt;br /&gt; '95-'99 Chevy Lumina, Monte Carlo, '97-'99 Chevy Malibu, Oldsmobile Cutlass
|-
|M||LY9||2.6&amp;nbsp;L||V6||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 24 valve||Opel 54° V6 engine (Made in the UK). Euro-market Cadillac CTS '03-'04.
|-
|M||LGD||3.9L||V6||Fuel injection#Sequential Multi Port Fuel injection|SFI||OHV||E85 Flex Fuel. GM High Value 60° V6. VVT. '09-'11 Chevy Impala, Buick Lucerne
|-
|M||LE2||1.4&amp;nbsp;L||Straight-4|I4 Turbo||Direct Injection|DI||DOHC,&lt;br /&gt; 16 valve||GM Small Gasoline Engine. VVT. '16-'19 Chevy Cruze.
|-
|N||LF9||5.7&amp;nbsp;L||V8||Indirect injection Diesel||OHV||Oldsmobile Diesel V8. '81-'85 Chevy Caprice, Impala, '82-'83 Malibu, '82-'84 Monte Carlo,&lt;br /&gt; '81-'84 Pontiac Grand Prix, Bonneville, '81 Catalina, '83-'85 Parisienne,&lt;br /&gt; '81-'84 Oldsmobile 98, '81-'85 Cutlass/Cutlass Supreme, Delta 88, Custom Cruiser, Toronado,&lt;br /&gt; '81-'83 Buick Electra,  '81-'85 LeSabre, Electra Estate wagon, Riviera, '82-'83 Regal,&lt;br /&gt; '81-'84 Cadillac DeVille, '81-'85 Fleetwood Brougham, Eldorado, Seville
|-
|N||LG7||3.3&amp;nbsp;L||V6||Fuel injection#Multi-port fuel injection|MFI||OHV||Buick V6 (3300). '89-'93 Buick Century, Skylark, Oldsmobile Cutlass Ciera, '89-'91 Cutlass Calais,&lt;br /&gt; '92-'93 Achieva, Pontiac Grand Am.
|-
|N||LA3||3.2&amp;nbsp;L||V6||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 24 valve||Opel 54° V6 engine (Made in the UK). '03-'04 Cadillac CTS
|-
|N||LZ4||3.5L||V6||Fuel injection#Sequential Multi-port injection|SFI||OHV||GM High Value 60° V6. 3510cc. VVT. '06-'07 Chevy Monte Carlo, '06-'10 Chevy Impala,&lt;br /&gt; '07-'10 Chevy Malibu, Pontiac G6, '07-'08 Saturn Aura
|-
|N||LFR||3.6L||V6||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 24 valve||(Bi-Fuel Gas/CNG). GM High Feature V6. '15-'17 Chevy Impala Bi-Fuel
|-
|P||LQ5||2.0&amp;nbsp;L||I4||Fuel injection#Throttle Body injection|TBI||OHV||Chevrolet &quot;122&quot; engine. '83-'86 J-cars ('83-'84 for Pontiac).
|-
|P||LT1||5.7&amp;nbsp;L||V8||Fuel injection#Sequential Multi-port injection|SFI||OHV||Gen II Chevy Small-Block V8. Aluminum Heads: '92-'96 Corvette, '93-'97 Camaro/Firebird.&lt;br /&gt; Iron Heads: '94-'96 Chevy Caprice, Impala SS, Buick Roadmaster, Cadillac Fleetwood.
|-
|P||LSJ||2.0&amp;nbsp;L||SC Straight-4|I4 Supercharged||Fuel injection#Sequential central point injection|SFI||DOHC,&lt;br /&gt; 16 valve||GM Ecotec Gen I. Made by Opel in Kaiserslautern, Germany.&lt;br /&gt; '04-'07 Saturn Ion Red Line, '05-'07 Chevy Cobalt SS Supercharged.
|-
|P||LSA||6.2&amp;nbsp;L||V8 Supercharged||Fuel injection#Sequential Multi-port injection|SFI||OHV||Gen IV Chevy Small-Block V8. Aluminum Block &amp; Heads.&lt;br /&gt; Cadillac CTS V-Series '09-'15, Camaro ZL1 '12-'15
|-
|P||LF4||3.6L||V6 Twin Turbo||Direct Injection|DI||DOHC,&lt;br /&gt; 24 valve||GM High Feature V6. Cadillac CT4-V Blackwing '22+
|-
|R||LR8||2.5L||I4||Fuel injection#Throttle Body injection|TBI||OHV||Pontiac Iron Duke/Tech IV engine. Transversely mounted. '82-'85 Chevy Citation, Buick Skylark,&lt;br /&gt; '82-'84 Pontiac Phoenix, Oldsmobile Omega, '82-'90 Chevy Celebrity, '82-'91 Pontiac 6000,&lt;br /&gt; '82-'92 Oldsmobile Cutlass Ciera, Buick Century, '84-'88 Pontiac Fiero, '90-'92 Chevy Lumina
|-
|R||L81||3.0&amp;nbsp;L||V6||Fuel injection#Multi-port fuel injection|SFI||DOHC,&lt;br /&gt; 24 valve||Opel 54° V6 engine (Made in the UK). '97-'01 Cadillac Catera, '00-'05 Saturn L-Series
|-
|R||LZ8||3.9L||V6||Fuel injection#Sequential Multi Port Fuel injection|SFI||OHV||GM High Value 60° V6. VVT. Active Fuel Management. '07 Chevy Impala
|-
|R||LS9||6.2&amp;nbsp;L||V8 Supercharged||Fuel injection#Sequential Multi-port injection|SFI||OHV||Gen IV Chevy Small-Block V8. Aluminum Block &amp; Heads. '09 Corvette ZR1.
|-
|R||LUK||2.4L||I4||Direct Injection|DI||DOHC,&lt;br /&gt; 16 valve||Mild Hybrid. GM Ecotec Gen II. VVT. '12-'16 Buick LaCrosse eAssist, Regal eAssist,&lt;br /&gt; '13-'14 Chevy Malibu Eco, '14 Chevy Impala Eco
|-
|S||LS5||4.3&amp;nbsp;L||V8||2 Barrel Carburetor |2BBL||OHV||Pontiac V8. 265 cu. in.&lt;br /&gt; '81 Pontiac Bonneville, Catalina, Firebird, Grand Prix, LeMans, Buick Century, Regal.
|-
|S||LU5||5.0&amp;nbsp;L||V8||Cross-Fire fuel injection|CFI||OHV||Gen I Chevy Small-Block V8. (305 cu. in.) '83 Camaro, Firebird. Dual throttle-body fuel injection.
|-
|S||LB8||2.8&amp;nbsp;L||V6||Fuel injection#Multi Port Fuel injection|MPFi||OHV||Chevrolet 60° V6 (longitudinally mounted).  '85-'89 Chevy Camaro, Pontiac Firebird.
|-
|S||L32||3.4&amp;nbsp;L||V6||Fuel injection#Multi Port Fuel injection|MPFi||OHV||Chevrolet 60° V6 (longitudinally mounted). '93-'95 Chevy Camaro, Pontiac Firebird.
|-
|S||LS6||5.7&amp;nbsp;L||V8||Fuel injection#Sequential Multi Port injection|SFI||OHV||Gen III Chevy Small-Block V8. (346 cu. in.) Aluminum Block &amp; Heads.&lt;br /&gt; '01-'04 Corvette Z06, '04-'05 Cadillac CTS V-Series
|-
|S||LGX||3.6L||V6||Direct Injection|DI||DOHC,&lt;br /&gt; 24 valve||GM High Feature V6, 4th gen. VVT. Active Fuel Management. '16-'19 Cadillac ATS, CTS, '16-'20 CT6, '16-'24 Chevrolet Camaro, '17-'19 Buick LaCrosse, '18–'20 Buick Regal GS
|-
|T||LU8||4.9&amp;nbsp;L||V8 Turbo||4 Barrel Carburetor |4BBL||OHV||Pontiac V8. 301 cu. in. '81 Pontiac Firebird Formula &amp; Trans Am.
|-
|T||LT7||4.3&amp;nbsp;L||V6||Indirect injection Diesel||OHV||Oldsmobile Diesel V6. FWD version for '82-'85 GM A-bodies.
|-
|T||LS2||4.3&amp;nbsp;L||V6||Indirect injection Diesel||OHV||Oldsmobile Diesel V6. FWD version for '85 GM C-bodies.
|-
|T||LH0||3.1&amp;nbsp;L||V6||Fuel injection#Multi Port Fuel injection|MPFi||OHV||Chevrolet 60° V6 (longitudinally mounted). '90-'92 Chevy Camaro, Pontiac Firebird.
|-
|T||LH0||3.1&amp;nbsp;L||V6||Fuel injection#Multi Port Fuel injection|MPFi||OHV||Chevrolet 60° V6 (transversely mounted). Gen II. '88-'91 Pontiac 6000,&lt;br /&gt; '89-'93 Grand Prix, Oldsmobile Cutlass Supreme, Buick Regal, '90-'94 Chevy Cavalier, Lumina,&lt;br /&gt; '91-'94 Pontiac Sunbird, '90-'93 Chevy Corsica/Beretta, '90 Celebrity
|-
|T||LD9||2.4&amp;nbsp;L||Straight-4|I4||Fuel injection#Sequential Multi-port injection|SFI||DOHC,&lt;br /&gt; 16 valve||Oldsmobile Quad 4 (&quot;2.4 Twin Cam&quot;). '96-'01 Pontiac Grand Am, '96-'97 Oldsmobile Achieva, Buick Skylark, '99-'01 Oldsmobile Alero, '97-'99 Chevy Malibu, '96-'02 Chevy Cavalier, Pontiac Sunfire
|-
|T||LP1||2.8&amp;nbsp;L||V6||Fuel injection#Sequential Multi-port injection|SFI||DOHC,&lt;br /&gt; 24 valve||GM High Feature V6. '05-'07 Cadillac CTS
|-
|T||LS9||6.2&amp;nbsp;L||V8 Supercharged||Fuel injection#Sequential Multi-port injection|SFI||OHV||Gen IV Chevy Small-Block V8. Aluminum Block &amp; Heads. '10-'13 Corvette ZR1.
|-
|T||LFV||1.5L||I4 Turbo||Direct Injection|DI||DOHC,&lt;br /&gt; 16 valve||GM Small Gasoline Engine. VVT. '16-'25 Chevy Malibu.
|-
|U||L68||2.5L||I4||Fuel injection#Throttle Body injection|TBI||OHV||Pontiac Iron Duke/Tech IV engine. Transversely mounted. '85-'91 N-bodies
|-
|U||LS2||6.0&amp;nbsp;L||V8||Fuel injection#Sequential Multi-port fuel injection|SFI||OHV||Gen IV Chevy Small-Block V8. Aluminum Block &amp; Heads.&lt;br /&gt; '05-'07 Corvette, '05-'06 Pontiac GTO, '06-'07 Cadillac CTS V-Series
|-
|U||LE9||2.4&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 16 valve||GM Ecotec Gen II. E85 Flex-Fuel. 2011-12 Chevy Malibu. 
|-
|U||LKN||1.8L||I4||Direct Injection|DI||DOHC,&lt;br /&gt; 16 valve||Full Hybrid. GM Medium Gasoline Engine. VVT. Made in Szentgotthárd, Hungary.&lt;br&gt; '16-'19 Chevy Malibu Hybrid
|-
|V||LT6||4.3&amp;nbsp;L||V6||Indirect injection Diesel||OHV||Oldsmobile Diesel V6. RWD version.&lt;br /&gt; '82-'83 Chevy Malibu, Monte Carlo, '82-'85 Oldsmobile Cutlass Supreme, Buick Regal
|-
|V||LG5||3.1&amp;nbsp;L||V6 Turbo||Fuel injection#Multi-port fuel injection|MPFI||OHV||Chevrolet 60° V6. Gen II. Intercooled. (ASC/McLaren modified).&lt;br /&gt; '89-'90 Pontiac Grand Prix Turbo coupe, '90 Grand Prix STE Turbo sedan
|-
|V||LLT||3.6L||V6||Direct Injection|DI||DOHC,&lt;br /&gt; 24 valve||GM High Feature V6. '08-'11 Cadillac CTS, STS, '10-'11 Chevrolet Camaro, Buick LaCrosse
|-
|V||LHU||2.0&amp;nbsp;L||Straight-4|I4 Turbo||Direct Injection|DI||DOHC,&lt;br /&gt; 16 valve||E85 Flex Fuel (N/A on Regal GS). GM Ecotec engine, Gen II. VVT.&lt;br /&gt; Buick Regal '11-'13, Verano '13-'16. 
|-
|W||L37||4.9&amp;nbsp;L||V8||4 Barrel Carburetor |4BBL||OHV||Pontiac V8. 301 cu. in. '81 Pontiac Firebird, LeMans Safari wagon.
|-
|W||LB6||2.8&amp;nbsp;L||V6||Fuel injection#Multi-port fuel injection|MFI||OHV||Gen I/II Chevrolet 60° V6 (transversely mounted). '85 Chevy Citation, Buick Skylark,&lt;br /&gt; '85-'89 Chevy Cavalier, Celebrity, Pontiac 6000, '85-'88 Cadillac Cimarron,&lt;br /&gt; '85-'87 Oldsmobile Firenza, '86-'89 Cutlass Ciera, '87-'88 Buick Century, '87-'89 Chevy Corsica/Beretta, '88-'89 Pontiac Grand Prix, Oldsmobile Cutlass Supreme, Buick Regal
|-
|W||L64||3.1&amp;nbsp;L||V6||Fuel injection#Multi-port fuel injection|MFI||OHV||Flex-fuel: Gas/M85 or Gas/E85 (2 versions). Gen II Chevrolet 60° V6. '93 Chevy Lumina VFV
|-
|W||L99||4.3&amp;nbsp;L||V8||Fuel injection#Sequential Multi-port injection|SFI||OHV||Gen II Chevy Small-Block V8. '94-'96 Chevy Caprice.
|-
|W||LS3||6.2&amp;nbsp;L||V8||Fuel injection#Sequential Multi-port injection|SFI||OHV||Gen IV Chevy Small-Block V8. Aluminum Block &amp; Heads.&lt;br /&gt; '08-'13 Corvette, '10-'15 Camaro SS (man. trans.), '09 Pontiac G8 GXP, '14-'17 Chevy SS
|-
|W||LGY||3.0L||V6 Twin Turbo||Direct Injection|DI||DOHC,&lt;br /&gt; 24 valve||GM High Feature V6, 4th gen. VVT. Active Fuel Management. '20+ Cadillac CT5, CT5-V
|-
|X||LE2||2.8&amp;nbsp;L||V6||2 Barrel Carburetor |2BBL||OHV||Chevrolet 60° V6 (transversely mounted). '81-'85 Chevy Citation, Buick Skylark,&lt;br /&gt; '81-'84 Pontiac Phoenix, Oldsmobile Omega, '82-'86 Chevy Celebrity, Pontiac 6000,&lt;br /&gt; '86 Oldsmobile Cutlass Ciera, Buick Century 
|-
|X||LQ1||3.4&amp;nbsp;L||V6||Fuel injection#Multi-port fuel injection|MPFI||DOHC,&lt;br /&gt; 24 valve||Chevrolet 60° V6 (&quot;Twin Dual Cam V6&quot;). '91-'97 Chevy Lumina, '95-'97 Chevy Monte Carlo,&lt;br /&gt; '91-'96 Pontiac Grand Prix, Oldsmobile Cutlass Supreme
|-
|X||LNF||2.0&amp;nbsp;L||Straight-4|I4 Turbo||Direct Injection|DI||DOHC,&lt;br /&gt; 16 valve||GM Ecotec engine, Gen II. VVT.&lt;br /&gt; '07-'10 Pontiac Solstice GXP, Saturn Sky Red Line, '08-'10 Chevy Cobalt SS Turbo. 
|-
|X||LTG||2.0&amp;nbsp;L||Straight-4|I4 Turbo||Direct Injection|DI||DOHC,&lt;br /&gt; 16 valve||GM Ecotec engine, Gen III. VVT. '13-'22 Chevy Malibu, '13-'19 Cadillac ATS, '14-'20 Buick Regal,&lt;br /&gt; '14-'19 Cadillac CTS, '16-'23 Chevy Camaro, '16-'18 Cadillac CT6.
|-
|X||LTG||2.0&amp;nbsp;L||Straight-4|I4 Turbo||Direct Injection|DI||DOHC,&lt;br /&gt; 16 valve||Plug-in hybrid. GM Ecotec engine, Gen III. VVT. '17-'18 Cadillac CT6 PHEV. (VIN starts with LRE)
|-
|Y||LV2||5.0&amp;nbsp;L||V8||4 Barrel Carburetor |4BBL||OHV||Oldsmobile &quot;Rocket&quot; V8 (307 cu. in.) '86-'90 Chevy Caprice wagon, '87 Caprice sedan (Can.),&lt;br /&gt; '81 Pontiac Bonneville, Catalina, '86 Parisienne, '87-'89 Safari wagon, '81-'84 Oldsmobile 98,&lt;br /&gt; '81-'85 Delta 88, Toronado, '81-'90 Custom Cruiser, '81 Cutlass Cruiser, '82-'87 Cutlass Supreme,&lt;br /&gt; '88 Cutlass Supreme Classic, '81-'84 Buick Electra, '85-'89 Electra Estate wagon,&lt;br /&gt; '81-'85 LeSabre, Riviera, '86-'89 LeSabre Estate wagon, '90 Estate wagon, '86-'87 Regal,&lt;br /&gt; '86 Cadillac Fleetwood Brougham, '87-'90 Brougham
|-
|Y||LD8||4.6&amp;nbsp;L||V8||Fuel injection#Sequential Multi-port injection|SFI||DOHC,&lt;br /&gt; 32 valve||Cadillac Northstar V8 (Torque tuned FWD) (Premium V). '93-'02 Cadillac Eldorado,&lt;br /&gt; '94-'04 Cadillac Seville SLS, '94-'05 Cadillac DeVille, '06-'11 Cadillac DTS,&lt;br /&gt; '04-'05 Pontiac Bonneville GXP, '06-'08 Buick Lucerne
|-
|Y||L76||6.0&amp;nbsp;L||V8||Fuel injection#Sequential Multi-port fuel injection|SFI||OHV||Gen IV Chevy Small-Block V8. Aluminum Block &amp; Heads. With Active Fuel Management.&lt;br /&gt; '08-'09 Pontiac G8 GT.
|-
|Y||LF1||3.0L||V6||Direct Injection|DI||DOHC,&lt;br /&gt; 24 valve||GM High Feature V6. VVT. 2011 Cadillac CTS
|-
|Y||LF4||3.6L||V6 Twin Turbo||Direct Injection|DI||DOHC,&lt;br /&gt; 24 valve||GM High Feature V6. Cadillac ATS-V '16-'19
|-
|Z||LH7||2.8&amp;nbsp;L||V6||2 Barrel Carburetor |2BBL||OHV||Chevrolet 60° V6 (transversely mounted). H.O. '81-'84 Chevy Citation, '82-'84 Pontiac Phoenix, Oldsmobile Omega ES, Buick Skylark, '83-'84 Pontiac 6000 STE, '84 Chevy Celebrity 
|-
|Z||LB4||4.3L||V6||Fuel injection#Throttle Body injection|TBI||OHV||Chevrolet 90° V6 (Chevy Small-Block V8 Derived). '85 Chevy Impala, '85-'90 Caprice,&lt;br /&gt; '92-'93 Caprice 9C6 taxi, '85-'88 Monte Carlo, '85-'86 Pontiac Parisienne, '86-'87 Grand Prix,&lt;br&gt; '86 Bonneville.
|-
|Z||LAT||2.4L||I4||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 16 valve||Mild Hybrid. GM Ecotec Gen II. VVT. '10 Chevy Malibu Hybrid
|-
|Z||LUZ||2.0&amp;nbsp;L||I4 Turbo||Direct injection &lt;br /&gt; Common-rail Diesel||DOHC,&lt;br /&gt; 16 valve||GM Family B Diesel (Based on Fiat JTD engine). Made by Opel in Kaiserslautern, Germany.&lt;br /&gt; Iron Block, Aluminum Heads. '14-'15 Chevy Cruze Diesel.
|-
|1||LC1||2.8&amp;nbsp;L||V6||2 Barrel Carburetor |2BBL||OHV||Chevrolet 60° V6 (longitudinally mounted). '82-'84 Camaro/Firebird.
|-
|1||LL8||2.0&amp;nbsp;L||I4||Fuel injection#Throttle Body injection|TBI||OHV||Chevrolet &quot;122&quot; engine. '87-'89 Chevy/Olds/Buick J-cars &amp; Chevy L-cars.
|-
|1||L67||3.8&amp;nbsp;L||V6 Supercharged||Fuel injection#Sequential Multi-port injection|SFI||OHV||Buick V6 (3800 Supercharged Series I). '91-'95 Buick Park Avenue Ultra,&lt;br /&gt; '92-'95 Pontiac Bonneville, Oldsmobile 98, '95 Buick Riviera, Oldsmobile LSS
|-
|1||L67||3.8&amp;nbsp;L||V6 Supercharged||Fuel injection#Sequential Multi-port injection|SFI||OHV||Buick V6 (3800 Supercharged Series II). '96-'05 Buick Park Avenue Ultra,&lt;br /&gt; '96-'99 Buick Riviera, Oldsmobile LSS, '96-'03 Pontiac Bonneville, '97-'03 Grand Prix,&lt;br /&gt; '97-'04 Buick Regal, '04-'05 Chevy Impala SS, Monte Carlo SS Supercharged
|-
|1||LZ9||3.9L||V6||Fuel injection#Sequential Multi-port injection|SFI||OHV||GM High Value 60° V6. VVT.&lt;br /&gt; '06-'07 Chevy Malibu SS, '06-'09 Pontiac G6, '06 Chevy Monte Carlo, Impala, '09-'10 Buick Lucerne
|-
|1||2H0||1.8&amp;nbsp;L||Straight-4|I4||Fuel injection#Sequential Multi-port fuel injection|SFI||DOHC,&lt;br /&gt; 16 valve||GM Family 1 engine, Gen III. VVT. Made in Szentgotthárd, Hungary. '08 (&amp; '09 in Canada) Saturn Astra
|-
|1||LE5||2.4&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 16 valve||GM Ecotec Gen II. VVT. '11 &amp; some '12 Chevy Malibu w/LE5 engine.
|-
|2||LQ9||2.5L||I4||Fuel injection#Throttle Body injection|TBI||OHV||Pontiac Iron Duke/Tech IV engine. Longitudinally mounted. '82-'85 Camaro/Firebird.
|-
|2||LS3||1.0&amp;nbsp;L||Straight-3|I3 Turbo||Fuel injection#Multi-port fuel injection|MFI||SOHC,&lt;br /&gt; 6 valve ||Suzuki G10T engine. '87-'88 Chevrolet Sprint Turbo
|-
|2||LY8||1.3&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port fuel injection|MFI||SOHC,&lt;br /&gt; 16 valve||Suzuki G13BB engine. '98-'01 Chevrolet Metro
|-
|2||L26||3.8&amp;nbsp;L||V6||Fuel injection#Sequential Multi-port injection|SFI||OHV||Buick V6 (3800 Series III). '04-'08 Pontiac Grand Prix, '05-'09 Buick LaCrosse, '06-'08 Buick Lucerne
|-
|2||L77||6.0&amp;nbsp;L||V8||Fuel injection#Sequential Multi-port fuel injection|SFI||OHV||Gen IV Chevy Small-Block V8. Aluminum Block &amp; Heads. With Active Fuel Management.&lt;br /&gt; E85 Flex Fuel. '11-'17 Chevy Caprice PPV.
|-
|3||LC8||3.8&amp;nbsp;L||V6|V6 Turbo||4 Barrel Carburetor |4BBL||OHV||Buick V6. 231 cu. in. '81-'82 Buick Regal, Riviera, '81 Chevy Monte Carlo.
|-
|3||LG3||3.8&amp;nbsp;L||V6||Fuel injection#(Sequential) Multi-port injection|MFI/SFI||OHV||Buick V6. '84-'88 Oldsmobile Cutlass Ciera, Buick Century, '85 &amp; '87 Oldsmobile 98, Buick Electra,&lt;br /&gt; '86-'88 Oldsmobile Delta 88, Buick LeSabre, '87 Oldsmobile Toronado, Buick Riviera,&lt;br /&gt; '87-'88 Pontiac Bonneville.
|-
|3||LW2||4.5&amp;nbsp;L||V8||Fuel injection#Multi-port fuel injection|MFI||OHV||Cadillac High Technology V8. '90 Cadillac DeVille/Fleetwood/Sixty Special/Eldorado/Seville.
|-
|3||L40||2.3&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port fuel injection|MFI||SOHC,&lt;br /&gt; 8 valve||Oldsmobile Quad 4 (&quot;Quad OHC&quot;). '92-'94 Pontiac Grand Am, Oldsmobile Achieva, Buick Skylark
|-
|3||LZG||3.9L||V6||Fuel injection#Sequential Multi Port Fuel injection|SFI||OHV||E85 Flex Fuel. GM High Value 60° V6. VVT. Active Fuel Management. '08 Chevy Impala
|-
|3||LFX||3.6L||V6||Direct Injection|DI||DOHC,&lt;br /&gt; 24 valve||GM High Feature V6. VVT. E85 Flex Fuel.&lt;br /&gt; '12-'16 Buick LaCrosse, '12-'15 	Chevrolet Camaro, Cadillac CTS, '12-'17 Chevrolet Caprice PPV,&lt;br /&gt; '12-'20 Chevrolet Impala, '14-'16 Chevrolet Impala Limited, '13-'15 Cadillac ATS, '13-'19 Cadillac XTS  
|-
|3||LT6||5.5&amp;nbsp;L||V8||Direct injection|DI||DOHC,&lt;br /&gt; 32 valve||Chevrolet Gemini Small-Block V8. Aluminum Block &amp; Heads. Flat-plane crank. VVT.&lt;br /&gt; For mid-engine C8 Corvette Z06 '23+.
|-
|4||LC4||4.1&amp;nbsp;L||V6|V6||4 Barrel Carburetor |4BBL||OHV||Buick V6. '81-'84 Buick LeSabre, Electra, Riviera, Oldsmobile Toronado, '81-'82 Cadillac DeVille, Fleetwood Brougham, Eldorado, Seville, '81-'83 Oldsmobile 98, '82-'84 Buick Regal,&lt;br /&gt; '82 Pontiac Grand Prix, Bonneville G
|-
|4||LC9||1.6&amp;nbsp;L||Straight-4|I4||2 Barrel Carburetor |2BBL||SOHC,&lt;br /&gt; 8 valve||Toyota 4A-C engine. '85-'88 Chevy Nova
|-
|4||LN2||2.2&amp;nbsp;L||Straight-4|I4||Fuel injection#(Sequential) Multi-port injection|MPI/SFI||OHV||Chevrolet &quot;122&quot; engine. '92-'02 Cavalier, '95-'02 Sunfire, '92-'96 Corsica/Beretta, '93 Lumina,&lt;br /&gt; '93-'96 Cutlass Ciera, Century.
|-
|4||L32||3.8&amp;nbsp;L||V6 Supercharged||Fuel injection#Sequential Multi-port injection|SFI||OHV||Buick V6 (3800 Supercharged Series III). '04-'07 Pontiac Grand Prix
|-
|4||LUU||1.4L||I4||Fuel injection#Sequential Multi-port fuel injection|SFI||DOHC,&lt;br /&gt; 16 valve||GM Family 0 Engine, Gen III. VVT. ([[w:EREV|Range extender]]). Early production engines were made in Aspern, Austria; later made in Flint, MI. '11-'15 Chevy Volt, '14 &amp; '16 Cadillac ELR. 
|-
|4||LT2||6.2&amp;nbsp;L||V8||Direct injection|DI||OHV||Gen V Chevy Small-Block V8. Aluminum Block &amp; Heads. Active Fuel Management. VVT.&lt;br /&gt; For mid-engine C8 Corvette Stingray '20+.
|-
|4||LT2||6.2&amp;nbsp;L||V8||Direct injection|DI||OHV||Full Hybrid. Gen V Chevy Small-Block V8. Aluminum Block &amp; Heads. Active Fuel Management. VVT.&lt;br /&gt; For mid-engine C8 Corvette E-Ray '24+.
|-
|5||LW9||2.5L||I4||2 Barrel Carburetor |2BBL||OHV||Pontiac Iron Duke engine. '81 Chevy Citation, Pontiac Phoenix, Oldsmobile Omega, Buick Skylark.
|-
|5||LR6||4.5&amp;nbsp;L||V8||Fuel injection#Throttle Body injection|TBI (DFI)||OHV||Cadillac High Technology V8. '88-'89 Cadillac DeVille/Fleetwood/Sixty Special/Eldorado/Seville.
|-
|5||LY9||1.0&amp;nbsp;L||Straight-3|I3||2BBL||SOHC,&lt;br /&gt; 6 valve ||Suzuki G10A engine. '86 Chevrolet Sprint
|-
|5||LM9||1.0&amp;nbsp;L||Straight-3|I3||2BBL||SOHC,&lt;br /&gt; 6 valve ||Suzuki G10A engine. '87-'88 Chevrolet Sprint
|-
|5||LW0||1.6&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 16 valve||Toyota 4A-GE engine. '88 Chevy Nova Twin Cam, '90-'92 Geo Prizm GSi
|-
|5||LW0||1.6&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 16 valve||Isuzu 4XE1-UW engine. '90-'91 Geo Storm GSi
|-
|5||LT4||5.7&amp;nbsp;L||V8||Fuel injection#Sequential Multi-port injection|SFI||OHV||Gen II Chevy Small-Block V8. '96 Corvette (man. trans.)
|-
|5||LAT||2.4L||I4||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 16 valve||Mild Hybrid. GM Ecotec Gen II. VVT. '07-'09 Saturn Aura Green Line, '08-'09 Chevy Malibu Hybrid
|-
|5||LAP||2.2&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 16 valve||GM Ecotec Gen II. VVT. '10 Chevy Cobalt.
|-
|5||LFW||3.0L||V6||Direct Injection|DI||DOHC,&lt;br /&gt; 24 valve||GM High Feature V6. VVT. '12-'13 Cadillac CTS, '14 CTS wagon
|-
|5||L3A||1.5L||I4||Direct Injection|DI||DOHC,&lt;br /&gt; 16 valve||GM Small Gasoline Engine. VVT. ([[w:EREV|Range extender]]). '16-'19 Chevy Volt. 
|-
|5||LWC||1.6L||I4 Turbo||Direct Injection|DI||DOHC,&lt;br /&gt; 16 valve||GM Medium Gasoline Engine, H.O. VVT. Made in Szentgotthárd, Hungary. '16-'19 Buick Cascada
|-
|5||LS6||6.7&amp;nbsp;L||V8||Port/Direct injection||OHV||Gen VI Chevy Small-Block V8. Aluminum Block &amp; Heads. Active Fuel Management. VVT.&lt;br /&gt; For mid-engine C8 Corvette Stingray, Grand Sport '27+. 
|-
|5||LS6||6.7&amp;nbsp;L||V8||Port/Direct injection||OHV||Full Hybrid. Gen VI Chevy Small-Block V8. Aluminum Block &amp; Heads. Active Fuel Management. VVT.&lt;br /&gt; For mid-engine C8 Corvette Grand Sport X '27+.
|-
|6||L81||5.7&amp;nbsp;L||V8||4 Barrel Carburetor |4BBL||OHV||Gen I Chevy Small-Block V8. '81 Corvette
|-
|6||LM1||5.7&amp;nbsp;L||V8||4 Barrel Carburetor |4BBL||OHV||Gen I Chevy Small-Block V8. '83-'85 Impala 9C1 Police, '86-'88 Caprice 9C1 Police
|-
|6||L73||1.6&amp;nbsp;L||Straight-4|I4||Fuel injection#Throttle Body injection|TBI||SOHC,&lt;br /&gt; 8 valve||GM Family 1 engine. Made in South Korea by Daewoo. '88-'93 Pontiac LeMans
|-
|6||LP2||1.0&amp;nbsp;L||Straight-3|I3||Fuel injection#Throttle Body injection|TBI||SOHC,&lt;br /&gt; 6 valve ||Suzuki G10A engine. '89-'97 Geo Metro, '98-'00 Chevrolet Metro
|-
|6||L01||1.6&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 16 valve||Toyota 4A-FE engine. '89-'97 Geo Prizm base/LSi
|-
|6||L01||1.6&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port fuel injection|MFI||SOHC,&lt;br /&gt; 12 valve||Isuzu 4XE1-V engine. '90-'93 Geo Storm (base model)
|-
|6||L42||2.2&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 16 valve||GM Ecotec Gen I (Bi-Fuel Gas/CNG). '03-'04 Chevy Cavalier
|-
|6||L91||1.6&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 16 valve||E-TEC II. '04-'07 Chevy Aveo
|-
|6||LXT||1.6&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 16 valve||E-TEC II. '08 Chevy Aveo
|-
|6||LGW||3.0L||V6 Twin Turbo||Direct Injection|DI||DOHC,&lt;br /&gt; 24 valve||GM High Feature V6, 4th gen. VVT. Active Fuel Management. '16-'19 Cadillac CT6
|-
|6||LT4||6.2&amp;nbsp;L||V8 Supercharged||Direct injection|DI||OHV||Gen V Chevy Small-Block V8. Aluminum Block &amp; Heads. With Active Fuel Management. VVT.&lt;br /&gt; '15-'19 Corvette Z06, '17-'24 Camaro ZL1, '16-'19 Cadillac CTS V-Series,&lt;br /&gt; '22+ Cadillac CT5-V Blackwing
|-
|7||LU5||5.0&amp;nbsp;L||V8||Cross-Fire fuel injection|CFI||OHV||Gen I Chevy Small-Block V8. (305 cu. in.) '82 Camaro, Firebird. Dual throttle-body fuel injection.
|-
|7||L69||5.0&amp;nbsp;L||V8||4 Barrel Quadrajet Carburetor |4BBL||OHV||Gen I Chevy Small-Block V8 (High Output 5.0L). (305 cu. in.). '83 F-cars, '83 Chevy Monte Carlo SS
|-
|7||LC5||1.5&amp;nbsp;L||I4||2 Barrel Carburetor |2BBL||SOHC,&lt;br /&gt; 8 valve||Isuzu 4XC1 engine. '86-'88 Chevrolet Spectrum, '89 Geo Spectrum.
|-
|7||LC2||3.8&amp;nbsp;L||V6|V6 Turbo||Fuel injection#Sequential multi-port injection|SFI||OHV||Intercooled. Buick V6. '86-'87 Buick Regal. '89 Pontiac 20th Anniversary Turbo Trans Am
|-
|7||LC7||4.1&amp;nbsp;L||V8||Fuel injection#Multi-port fuel injection|MFI||OHV||Cadillac High Technology V8. '87-'88 Cadillac Allante.
|-
|7||L05||5.7&amp;nbsp;L||V8||Fuel injection#Throttle Body injection|TBI||OHV||Gen I Chevy Small-Block V8. '89-'93 Chevy Caprice (police only for '89-'91),&lt;br /&gt; '92-'93 Buick Roadmaster, '92 Oldsmobile Custom Cruiser, '90-'92 Cadillac Brougham, '93 Fleetwood.
|-
|7||LL0||1.9&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port injection|MFI||DOHC,&lt;br /&gt; 16 valve||Saturn I4 engine. '91-'02 Saturn S-Series
|-
|7||LY7||3.6&amp;nbsp;L||V6||Fuel injection#Sequential Multi-port injection|SFI||DOHC,&lt;br /&gt; 24 valve||GM High Feature V6. VVT. '04-'09 Cadillac CTS, '05-'07 STS, '05-'08 Buick LaCrosse,&lt;br /&gt; '07-'09 Pontiac G6, Saturn Aura, '08-'09 Pontiac G8, '08-'12 Chevy Malibu
|-
|7||LT1||6.2&amp;nbsp;L||V8||Direct injection|DI||OHV||Gen V Chevy Small-Block V8. Aluminum Block &amp; Heads. With Active Fuel Management. VVT.&lt;br /&gt; '14-'19 Corvette, '16-'24 Camaro SS
|-
|7||LT7||5.5&amp;nbsp;L||V8 Twin Turbo||Port/Direct injection||DOHC,&lt;br /&gt; 32 valve||Chevrolet Gemini Small-Block V8. Aluminum Block &amp; Heads. Flat-plane crank. VVT.&lt;br /&gt; For mid-engine C8 Corvette ZR1 '25+. (1,064 hp)
|-
|7||LT7||5.5&amp;nbsp;L||V8 Twin Turbo||Port/Direct injection||DOHC,&lt;br /&gt; 32 valve||Full Hybrid. Chevrolet Gemini Small-Block V8. Aluminum Block &amp; Heads. Flat-plane crank. VVT.&lt;br /&gt; For mid-engine C8 Corvette ZR1X '26+. (1,250 hp)
|-
|8||LV8||4.3&amp;nbsp;L||V8||2 Barrel Carburetor |2BBL||OHV||Oldsmobile &quot;Rocket&quot; V8 (260 cu. in.) '82 Oldsmobile Cutlass, Delta 88.
|-
|8||LT8||4.1&amp;nbsp;L||V8||Fuel injection#Throttle Body injection|TBI (DFI)||OHV||Cadillac High Technology V8. '82-'87 Cadillac DeVille, Eldorado, Seville, '82-'85 Fleetwood Brougham, '85-'87 Fleetwood, '87 Fleetwood Sixty Special.
|-
|8||LC8||3.8&amp;nbsp;L||V6|V6 Turbo||4 Barrel Carburetor |4BBL||OHV||Buick V6. '83 Buick Regal, Riviera.
|-
|8||L83||5.7&amp;nbsp;L||V8||Cross-Fire fuel injection|CFI||OHV||Gen I Chevy Small-Block V8. '82, '84 Corvette. Dual throttle-body fuel injection.  1st fuel injected Corvette since 1965.
|-
|8||L98||5.7&amp;nbsp;L||V8||Tuned-port fuel injection|TPI||OHV||Gen I Chevy Small-Block V8. '85-'91 Corvette, '87-'92 Chevy Camaro, Pontiac Firebird.
|-
|8||LQ6||4.5&amp;nbsp;L||V8||Fuel injection#Multi-port fuel injection|MFI||OHV||Cadillac High Technology V8. '89-'92 Cadillac Allante.
|-
|8||L24||1.9&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port injection|MFI||SOHC,&lt;br /&gt; 8 valve||Saturn I4 engine. '95-'02 Saturn S-Series
|-
|8||LX9||3.5&amp;nbsp;L||V6||Fuel injection#Sequential Multi-port injection|SFI||OHV||GM High Value 60° V6. 3498cc. '04-'06 Chevy Malibu, '05-'06 Pontiac G6
|-
|8||LF3||3.6L||V6 Twin Turbo||Direct Injection|DI||DOHC,&lt;br /&gt; 24 valve||GM High Feature V6. '14-'19 Cadillac CTS V-Sport, XTS V-Sport
|-
|8||LV6||1.8&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 16 valve||Isuzu 4XF1 engine. '92-'93 Geo Storm GSi.
|-
|8||LV6||1.8&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 16 valve||Toyota 7A-FE engine. '93-'97 Geo Prizm
|-
|8||LV6||1.8&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 16 valve||Toyota 1ZZ-FE engine. VVT-i from '00. '98-'02 Chevrolet Prizm, '03-'08 Pontiac Vibe
|-
|8||LAY||1.8&amp;nbsp;L||Straight-4|I4||Fuel injection#Sequential multi-port injection|SFI||DOHC,&lt;br /&gt; 16 valve||Toyota 2ZR-FE engine. Dual VVT-i. '09-'10 Pontiac Vibe
|-
|9||L17||1.6&amp;nbsp;L||Straight-4|I4||2 Barrel Carburetor |2BBL||SOHC,&lt;br /&gt; 8 valve||Isuzu G161Z engine made by GM in US. '81 Chevy Chevette, Pontiac T1000
|-
|9||L62||6.0&amp;nbsp;L||V8||Fuel injection#Throttle Body injection|TBI (DFI)||OHV||Cadillac 472-series V8 engine family. V8-6-4 cylinder deactivation.&lt;br /&gt; '81 Cadillacs, '82-'84 Fleetwood Limousine. 
|-
|9||LC3||3.8&amp;nbsp;L||V6||2 Barrel Carburetor |2BBL||OHV||Chevrolet 90° V6 (Chevy Small-Block V8 Derived). 229 cu. in. &lt;br /&gt; '83 Malibu, '83-'84 Monte Carlo, Impala, Caprice, '83 Pontiac Parisienne.
|-
|9||LG8||5.0&amp;nbsp;L||V8||4 Barrel Carburetor |4BBL||OHV||Oldsmobile &quot;Rocket&quot; V8 (307 cu. in.) H.O. '83-'84 Hurst/Olds, '85-'87 Oldsmobile Cutlass 442
|-
|9||LM9||3.8&amp;nbsp;L||V6|V6 Turbo||Fuel injection#Sequential multi-port injection|SFI||OHV||Buick V6. '84-'85 Buick Regal, Riviera.
|-
|9||L44||2.8&amp;nbsp;L||V6||Fuel injection#Multi-port fuel injection|MFI||OHV||Chevrolet 60° V6 (transversely mounted). H.O. '85-'88 Pontiac Fiero
|-
|9||LC0||1.5&amp;nbsp;L||I4 Turbo||Fuel injection#Multi-port fuel injection|MFI||SOHC,&lt;br /&gt; 8 valve||Isuzu 4XC1-T engine. '87-'88 Chevrolet Spectrum Turbo
|-
|9||LK0||1.9&amp;nbsp;L||Straight-4|I4||Fuel injection#Throttle Body injection|TBI||SOHC,&lt;br /&gt; 8 valve||Saturn I4 engine. '91-'94 Saturn S-Series
|-
|9||L37||4.6&amp;nbsp;L||V8||Fuel injection#Sequential Multi-port injection|SFI||DOHC,&lt;br /&gt; 32 valve||Cadillac Northstar V8 (H.O. FWD) (Premium V). '93 Cadillac Allanté,&lt;br /&gt; '93-'02 Cadillac Eldorado Touring Coupe, '93-'04 Cadillac Seville STS, '96-'05 Cadillac DeVille,&lt;br /&gt; '06-'11 Cadillac DTS, '08-'11 Buick Lucerne Super
|-
|9||L72||1.3&amp;nbsp;L||Straight-4|I4||Fuel injection#Throttle Body injection|TBI||SOHC,&lt;br /&gt; 8 valve ||Suzuki G13BA engine. '95-'97 Geo Metro
|-
|9||LUJ||1.4L||I4 Turbo||Fuel injection#Sequential Multi-port fuel injection|SFI||DOHC,&lt;br /&gt; 16 valve||GM Family 0 Engine, Gen III. VVT. Early production engines were made in Aspern, Austria; later made in Flint, MI. '11 Chevy Cruze
|-
|9||LL0||1.2&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 16 valve||Daewoo S-TEC II engine (1249 cc). VVT. Made in Changwon, S. Korea. '13-'15 Chevy Spark.
|-
|9||LT5||6.2&amp;nbsp;L||V8 Supercharged||Port/Direct injection||OHV||Gen V Chevy Small-Block V8. Aluminum Block &amp; Heads. VVT. '19 Corvette ZR1.
|-
|0||LH8||1.8&amp;nbsp;L||Straight-4|I4||Fuel injection#Throttle Body injection|TBI||SOHC,&lt;br /&gt; 8 valve||GM Family II engine. Made in Brazil.&lt;br /&gt; '82-'86 Pontiac J2000/2000/Sunbird, Oldsmobile Firenza, Buick Skyhawk. 
|-
|0||LAX||2.4&amp;nbsp;L||Straight-4|I4||Fuel injection#Sequential multi-port injection|SFI||DOHC,&lt;br /&gt; 16 valve||Toyota 2AZ-FE engine. VVT-i. '09-'10 Pontiac Vibe
|-
|0||LE9||2.4&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 16 valve||GM Ecotec Gen II. E85 Flex-Fuel. 2010 Chevy Malibu. 
|-
|0||LE5||2.4&amp;nbsp;L||Straight-4|I4||Fuel injection#Multi-port fuel injection|MFI||DOHC,&lt;br /&gt; 16 valve||GM Ecotec Gen II. VVT. Most '12 Chevy Malibu w/LE5 engine.
|}

H.O.=High Output, CNG=Compressed Natural Gas, VVT=Variable Valve Timing, VVL=Variable Valve Lift

====Motor codes for electric passenger cars====

{| class=&quot;wikitable&quot;
|-
! VIN !! RPO !! Fuel !! Drive Wheels !! Application/Notes
|-
| 5 ||LN1|| Electricity || Front || '97, '99 General Motors EV1
|-
| 0 ||EN0|| Electricity || Front || '14-'16 Chevrolet Spark EV
|-
| 0 ||EN0|| Electricity || Front || '17-'23 Chevrolet Bolt EV
|-
| 0 ||EN0|| Electricity || Front || '22-'23 Chevrolet Bolt EUV
|-
|}

====Motor codes for LFP-powered electric passenger cars====

{| class=&quot;wikitable&quot;
|-
! VIN !! Motor &lt;br /&gt; RPO code !! # of Motors !! Battery Pack &lt;br /&gt; RPO code !! Fuel !! Drive Wheels !! Application/Notes
|-
|-
| V ||P9D (HPB)|| 1 || EJW || Electricity || Front || '27 Chevrolet Bolt
|}
LFP=Lithium Iron Phosphate

====Motor codes for Ultium-powered electric passenger cars====

{| class=&quot;wikitable&quot;
|-
! VIN !! Motor &lt;br /&gt; RPO code !! # of Motors !! Battery Module &lt;br /&gt; RPO code !! # of Modules !! Fuel !! Drive Wheels !! Application/Notes
|-
|-
| 1 ||X0E|| 2 || EXN || 16 || Electricity || All || '25- Cadillac Celestiq
|-
| 2 ||X0E|| 2 || EHT || 16 || Electricity || All || '25- Cadillac Celestiq &lt;br&gt; (Battery Module RPO code EHT is Configuration B)
|}

====Engine codes for light trucks====
GM encodes the engine type in character 8 of the VIN. The following table outlines the various engines encoded there:

{| class=&quot;wikitable&quot;
|-
! VIN !! RPO !! Size !! Type !! Fuel !! Valvetrain !! Engine Family/Notes/Applications
|-
| A ||LD5|| 3.8L || V6 || Gas ||OHV||2-bbl carb. Buick V6. (231 cu. in.) '81-'84 Chevy El Camino, GMC Caballero (CA emissions).
|-
| A ||LR1|| 1.9L || I4 || Gas ||SOHC,&lt;br /&gt; 8 valve||2-bbl carb. Isuzu G200 engine imported from Japan.&lt;br /&gt; '82-'85 Chevy S-10/GMC S-15, '83-'85 Chevy S-10 Blazer/GMC S-15 Jimmy
|-
| A ||L38|| 2.5L || I4 || Gas ||OHV||TBI. Pontiac Iron Duke/Tech IV engine. '91-'93 Chevy S-10/GMC Sonoma.
|-
| A ||LH2|| 4.6L || V8 || Gas ||DOHC,&lt;br /&gt; 32 valve||SFI. Cadillac Northstar V8 (For RWD) (Premium V). '04-'09 Cadillac SRX
|-
| A ||L20|| 4.8L || V8 || Gas/E85 ||OHV|| Flex Fuel. SFI. Gen IV Chevrolet Small-Block V8. Iron Block/Aluminum Heads. VVT.&lt;br /&gt; '10-'13 GMT900 pickups, '10-'14 Express/Savana
|-
| A ||LCV|| 2.5L || I4 || Gas ||DOHC,&lt;br /&gt; 16 valve||GM Ecotec engine, Gen III. Direct Injection. VVT. '15-'22 Chevy Colorado, GMC Canyon,&lt;br /&gt; '17-'20 Buick Envision, '17-'21 GMC Acadia, '19-'21 Chevy Blazer
|-
| B ||LR2|| 2.8L || V6 || Gas ||OHV||2-bbl carb. Chevrolet 60° V6.&lt;br /&gt; '82-'85 Chevy S-10/GMC S-15, '83-'85 Chevy S-10 Blazer/GMC S-15 Jimmy
|-
| B ||LU2|| 4.3L || V6 || Gas ||OHV|| TBI. Chevrolet 90° V6 (Chevy Small-Block V8 Derived). '90-'91 Astro/Safari higher output engine option.
|-
| B ||L81|| 3.0L || V6 || Gas ||DOHC,&lt;br /&gt; 24 valve||SFI. Opel 54° V6 engine (Made in the UK). '02-'03 Saturn Vue
|-
| B ||L33|| 5.3L || V8 || Gas ||OHV||SFI. Gen III Chevrolet Small-Block V8. Vortec 5300 H.O. 310hp. Aluminum Block &amp; Heads.&lt;br /&gt; '05-'06 Silverado/Sierra 1500 4wd ext. cab short bed,&lt;br&gt; '07 Silverado Classic 1500/Sierra Classic 1500 4wd ext. cab short bed.
|-
| B ||LE8|| 2.2L || I4 || Gas/E85 ||DOHC,&lt;br /&gt; 16 valve||Flex-Fuel. SFI. GM Ecotec Gen II. VVT. '09-'10 Chevy HHR
|-
| B ||LC8|| 6.0L || V8 || Gas/CNG ||OHV||Bi-Fuel (Also Gas/LPG in Express/Savana). SFI. Gen IV Chevrolet Small-Block V8. Iron Block &amp; Aluminum Heads. VVT. '11-'20 Express/Savana, '13-'19 Silverado HD/Sierra HD.
|-
| B ||LUV|| 1.4L ||I4 Turbo|| Gas ||DOHC,&lt;br /&gt; 16 valve||GM Family 0 Engine, Gen III. SFI. VVT.&lt;br /&gt; '13-'21 Buick Encore, '15-'21 Chevy Trax (also '13-'14 Trax in Canada)
|-
| C ||LH6|| 6.2L || V8 || Diesel ||OHV||Detroit Diesel V8. For sub-8,500 lb. GVWR trucks '82-'93. '82-'86 C/K pickups, '87 R/V pickups,&lt;br /&gt; '88-'93 C/K, Sierra pickups, '82-'91 Blazer/Jimmy, Suburban, '83-'93 full-size vans
|-
| C ||L34|| 2.0L || I4 || Gas ||DOHC,&lt;br /&gt; 16 valve||Suzuki J20A engine. MFI. '99-'03 Chevrolet Tracker
|-
| C ||LY2|| 4.8L || V8 || Gas ||OHV||SFI. Gen IV Chevrolet Small-Block V8. Iron Block/Aluminum Heads.&lt;br /&gt; '07-'09 GMT900 pickups, '07-'09 Tahoe/Yukon, '08-'09 Express/Savana
|-
| C ||LAF|| 2.4L || I4 || Gas ||DOHC,&lt;br /&gt; 16 valve||GM Ecotec engine, Gen II. Direct Injection. VVT. Chevy Equinox, GMC Terrain '11. 
|-
| C ||L83|| 5.3L || V8 || Gas/E85 ||OHV|| Flex Fuel. Gen V Chevrolet Small-Block V8 (EcoTec3). Direct injection, VVT. Active Fuel Management&lt;br /&gt; '14-'19 K2XX pickups, '15-'20 K2XX SUVs.
|-
| C ||L2R|| 2.7L ||I4 Turbo||| Gas ||DOHC,&lt;br /&gt; 16 valve||GM L3B Tripower engine (&quot;TurboMax&quot;) - Detuned version. Direct Injection. VVT, VVL. Active Fuel Management. '23-'24 Chevy Colorado.
|-
| D ||LE3|| 4.1L || I6 || Gas ||OHV||2-bbl carb. Chevrolet Turbo-Thrift I6.&lt;br /&gt; '81-'84 Chevy/GMC C/K pickups, full-size vans, '81-'82 Blazer/Jimmy
|-
| D ||LG6|| 3.1L || V6 || Gas ||OHV||TBI. Chevrolet 60° V6. '90-'95 U-body minivans.
|-
| D ||L61|| 2.2L || I4 || Gas ||DOHC,&lt;br /&gt; 16 valve||SFI. GM Ecotec Gen I. '02-'07 Saturn Vue, '06 Chevy HHR.
|-
| D ||L61|| 2.2L || I4 || Gas ||DOHC,&lt;br /&gt; 16 valve||SFI. GM Ecotec Gen II. '07-'08 Chevy HHR.
|-
| D ||LLT|| 3.6L || V6 || Gas ||DOHC,&lt;br /&gt; 24 valve||GM High Feature V6. Direct Injection. '09-'16 GMC Acadia, '17 GMC Acadia Limited,&lt;br /&gt; '09-'17 Chevrolet Traverse, Buick Enclave, '09-'10 Saturn Outlook
|-
| D ||LBZ|| 6.6L || V8 Turbo || Diesel ||OHV,&lt;br /&gt; 32 valve||Duramax 6600 V8 engine.&lt;br /&gt; Mid '06 Silverado HD/Sierra HD &amp; '07 Silverado Classic HD/Sierra Classic HD
|-
| D ||L84|| 5.3L || V8 || Gas/E85 ||OHV|| Gen V Chevrolet Small-Block V8 (EcoTec3).  Direct injection, VVT. With Dynamic Fuel Management&lt;br /&gt; '19+ Chevy/GMC Silverado 1500/Sierra 1500, '21+ Tahoe/Yukon, Suburban/Yukon XL.
|-
| E ||LN8|| 2.5L || I4 || Gas ||OHV||TBI. Pontiac Iron Duke/Tech IV engine.&lt;br /&gt; '85-'90 Chevy/GMC S-10/S-15, Astro/Safari Cargo Van, '85-'88 S-10 Blazer/S-15 Jimmy.
|-
| E ||LLR|| 3.7L || I5 || Gas ||DOHC,&lt;br /&gt; 20 valve||Atlas I5. SFI. VVT.&lt;br /&gt; '07-'12 Colorado/Canyon, '07-'08 Isuzu i-370, '07-'10 Hummer H3, '09-'10 Hummer H3T  
|-
| E ||LA1|| 3.4L || V6 || Gas ||OHV||Chevrolet 60° V6. '96 GMT199 (U-body) minivans, '97-'05 GMT200 (U-body) minivans,&lt;br /&gt; '01-'05 Pontiac Aztek, '02-'05 Buick Rendezvous
|-
| F ||LF3|| 5.0L || V8 || Gas ||OHV|| 4-bbl carb. Gen I Chevrolet Small-Block V8. '81-'86 C/K, full-size vans, '81-'82 Blazer/Jimmy.&lt;br /&gt; CA emissions version of LE9 5.0 V8.
|-
| F ||L65|| 6.5L || V8 Turbo || Diesel ||OHV||Detroit Diesel V8. For over-8,500 lb. GVWR Chevy C/K, GMC Sierra trucks '92-'02,&lt;br /&gt; Chevy/GMC Suburban 1500/2500 '94-'99, over-8,500 lb. GVWR Express/Savana '96-'02
|-
| F ||LNJ|| 3.4L || V6 || Gas ||OHV||Chevrolet 60° V6. Made in China by SAIC-GM. '05-'09 Chevy Equinox, '06-'09 Pontiac Torrent.
|-
| F ||L94|| 6.2L || V8 || Gas/E85 ||OHV||Flex-Fuel. Gen IV Chevrolet Small-Block V8. Aluminum Block &amp; Heads. SFI. VVT. Active Fuel Management. '10-'14 GMC Yukon Denali/Yukon XL Denali, Cadillac Escalade/Escalade ESV.
|-
| F ||L20|| 4.8L || V8 || Gas/E85 ||OHV|| Flex Fuel. SFI. Gen IV Chevrolet Small-Block V8. Iron Block/Aluminum Heads. VVT.&lt;br /&gt; '15-'17 Express/Savana
|-
| F ||L82|| 5.3L || V8 || Gas ||OHV|| Gen V Chevrolet Small-Block V8 (EcoTec3). Direct injection, VVT. With Active Fuel Management&lt;br /&gt; '19-'21 Chevy Silverado 1500, GMC Sierra 1500 (T1XX).
|-
| G ||LG9|| 5.0L || V8 || Gas ||OHV|| 2-bbl carb. Gen I Chevrolet Small-Block V8. '81 Chevy/GMC C/K pickups, Blazer/Jimmy, full-size van
|-
| G ||L18|| 8.1L || V8 || Gas ||OHV||MFI. Vortec 8100. Gen VII Chevrolet Big-Block V8. '01-'02 C3500HD, '01-'06 Silverado HD/Sierra HD, '07 Silverado Classic HD/Sierra Classic HD, '01-'06 Suburban/Yukon XL 2500, '02-'06 Avalanche 2500, '01-'02 Express/Savana
|-
| G ||L96|| 6.0L || V8 || Gas/E85 ||OHV||Flex Fuel. SFI. Gen IV Chevrolet Small-Block V8. Iron Block &amp; Aluminum Heads. VVT.&lt;br /&gt; '10-'19 Silverado HD/Sierra HD, '10-'13 Suburban 2500/Yukon XL 2500, '16-'19 Suburban 3500,&lt;br /&gt; '10-'20 Express/Savana.
|-
| G ||LSD|| 1.5L || I4 Turbo || Gas ||DOHC,&lt;br /&gt; 16 valve||GM Small Gasoline Engine. Direct Injection. VVT. '23+ Chevy Equinox, GMC Terrain
|-
| H ||LG4|| 5.0L || V8 || Gas ||OHV||4-bbl carb. Gen I Chevy Small-Block V8. (305 cu. in.) '81-'87 Chevy El Camino, GMC Caballero.
|-
| H ||LE9|| 5.0L || V8 || Gas ||OHV|| 4-bbl carb. Gen I Chevrolet Small-Block V8. '81-'86 C/K pickups, Blazer/Jimmy, Suburban, full-size vans
|-
| H ||L03|| 5.0L || V8 || Gas ||OHV|| TBI. Gen I Chevrolet Small-Block V8. '87 R/V pickups, '88-'95 C/K, Sierra pickups, '87-'95 full-size vans, '87 Blazer/Jimmy, Suburban.
|-
| H ||LN2|| 2.2L || I4 || Gas ||OHV||SFI. Chevrolet &quot;122&quot; engine. '03 Chevy S-10/GMC Sonoma
|-
| H ||LS2|| 6.0L || V8 || Gas ||OHV||SFI. Gen IV Chevy Small-Block V8. Chevy SSR '05-'06, Trailblazer SS '06-'09, Saab 9-7X Aero '08-'09.
|-
| H ||LV3|| 4.3L || V6 || Gas/E85 ||OHV||Flex Fuel. Chevrolet 90° V6 - Gen V Chevrolet Small-Block V6 (EcoTec3). Direct injection, VVT. Active Fuel Management. '14-'21 Chevy Silverado 1500/GMC Sierra 1500.
|-
| J ||L39|| 4.4L || V8 || Gas ||OHV||2-bbl carb. Gen I Chevy Small-Block V8 (267 cu. in.) '81-82 Chevy El Camino, GMC Caballero.
|-
| J ||LL4|| 6.2L || V8 || Diesel ||OHV||Detroit Diesel V8. For over-8,500 lb. GVWR trucks '82-'93. '82-'86 C/K pickups, '87-'91 R/V pickups,&lt;br /&gt; '88-'93 C/K, Sierra pickups, '82-'91 Blazer/Jimmy, Suburban, '83-'93 full-size vans
|-
| J ||L29|| 7.4L || V8 || Gas ||OHV|| MFI. Vortec 7400. Gen VI Chevrolet Big-Block V8.&lt;br /&gt; '96-'00 C/K, Sierra pickups, Express/Savana, '96-'99 Suburban 2500
|-
| J ||LY5|| 5.3L || V8 || Gas ||OHV||SFI. Gen IV Chevrolet Small-Block V8. Active Fuel Management. Iron Block &amp; Aluminum Heads.&lt;br /&gt; '07-'09 Silverado/Sierra 1500, Tahoe/Yukon, Suburban/Yukon XL 1500, Avalanche
|-
| J ||LZ1|| 6.0L || V8 || Gas-Electric Hybrid ||OHV||2-Mode Hybrid. Gen IV Chevrolet Small-Block V8. Aluminum Block &amp; Heads. VVT. Active Fuel Management. '10-'13 Tahoe Hybrid, Yukon Hybrid, Escalade Hybrid, Silverado Hybrid, Sierra Hybrid
|-
| J ||L86|| 6.2L || V8 || Gas ||OHV||Gen V Chevrolet Small-Block V8 (EcoTec3). Direct injection, VVT. Active Fuel Management. &lt;br /&gt; '14-18 Chevy/GMC Silverado 1500/Sierra 1500,&lt;br /&gt; '18-20 Chevy Tahoe Premier, '19-'20 Chevy Suburban Premier, GMC Yukon/Yukon XL SLT,&lt;br /&gt; '15-'20 GMC Yukon Denali/Yukon XL Denali, Cadillac Escalade/Escalade ESV. 
|-
| K ||LC3|| 3.8L || V6 || Gas ||OHV||2-bbl carb. Chevrolet 90° V6 (Chevy Small-Block V8 Derived). 229 cu. in. &lt;br /&gt; '81-'82 Chevy El Camino, GMC Caballero (49-state emissions)
|-
| K ||L05|| 5.7L || V8 || Gas ||OHV|| TBI. Gen I Chevrolet Small-Block V8. '87 R/V pickups, '88-'95 C/K, Sierra pickups, '87-'95 full-size vans, '96 G-Classic full-size vans, '87-'94 Blazer, '95 Tahoe, '87-'91 Jimmy, '92-'95 Yukon, '87-'95 Suburban. 
|-
| K ||LY6|| 6.0L || V8 || Gas ||OHV||SFI. Gen IV Chevrolet Small-Block V8. Iron Block &amp; Aluminum Heads. VVT.&lt;br /&gt; '07-'09 Silverado HD/Sierra HD, '07-'09 Suburban 2500/Yukon XL 2500, '08-'09 Express/Savana
|-
| K ||LEA|| 2.4L || I4 || Gas/E85 ||DOHC,&lt;br /&gt; 16 valve||Flex Fuel. GM Ecotec engine, Gen II. Direct Injection. VVT. Chevy Equinox, GMC Terrain '12-'17,&lt;br /&gt; Chevy Captiva Sport '12-'14, Chevy Orlando '14. 
|-
| K ||L3B|| 2.7L ||I4 Turbo||| Gas ||DOHC,&lt;br /&gt; 16 valve||GM L3B Tripower engine (&quot;TurboMax&quot;). Direct Injection. VVT, VVL. Active Fuel Management.&lt;br /&gt; '19+ Chevy Silverado 1500, GMC Sierra 1500, '23+ Chevy Colorado, GMC Canyon.
|-
| L ||LS9|| 5.7L || V8 || Gas ||OHV|| 4-bbl carb. Gen I Chevrolet Small-Block V8. For sub-8,500 lb. GVWR trucks, vans, Suburban, Blazer/Jimmy (CA) '81-'86.
|-
| L ||L27|| 3.8L || V6 || Gas ||OHV||Buick V6 (3800 Series I). '92-'95 U-body minivans
|-
| L ||LX9|| 3.5L || V6 || Gas ||OHV||GM High Value 60° V6. 3498cc. SFI. '05-'06 GMT201 minivans, '06-'07 Buick Rendezvous
|-
| L ||LH8|| 5.3L || V8 || Gas ||OHV||SFI. Gen IV Chevrolet Small-Block V8. Aluminum Block &amp; Heads.&lt;br /&gt; '08-'09 Hummer H3 Alpha, '09 Colorado/Canyon, Hummer H3T Alpha
|-
| L ||LGH|| 6.6L || V8 Turbo || Diesel ||OHV,&lt;br /&gt; 32 valve||Duramax 6600 V8 engine. Mid '10-'16 Express/Savana, '11-'12 Silverado HD/Sierra HD chassis cabs
|-
| L ||L87|| 6.2L || V8 || Gas ||OHV||Gen V Chevrolet Small-Block V8 (EcoTec3). Direct injection, VVT. Dynamic Fuel Management.&lt;br /&gt; '19+ Chevy/GMC Silverado 1500/Sierra 1500, '21+ Tahoe/Yukon, Suburban/Yukon XL,&lt;br /&gt; Cadillac Escalade/Escalade ESV.
|-
| L ||L3T|| 1.3L || I3 Turbo || Gas ||DOHC,&lt;br /&gt; 12 valve||GM E-Turbo Engine. Direct Injection. VVT. '20+ Buick Encore GX, '21+ Chevy Trailblazer.
|-
| M ||LT9|| 5.7L || V8 || Gas ||OHV|| 4-bbl carb. Gen I Chevy Small-Block V8.&lt;br /&gt; For over-8,500 lb. GVWR C/K trucks, full-size vans, Suburban '81-'86, full-size van cutaway '81-'88.&lt;br /&gt; '88 Chevy/GMC R30/3500 Chassis Cab w/C7C (10,500 lb. GVWR),&lt;br /&gt; V30/3500 Chassis Cab w/C7E (11,000 lb. GVWR)
|-
| M ||L30|| 5.0L || V8 || Gas ||OHV||Gen 1+ Chevrolet Small-Block V8. Vortec 5000. CPI.&lt;br /&gt; '96-'99 Chevy C/K, GMC Sierra, '96-'02 Express/Savana
|-
| M ||LNF|| 2.0L || I4 Turbo || Gas ||DOHC,&lt;br /&gt; 16 valve||GM Ecotec engine, Gen II. Direct Injection. VVT. 2010 Chevy HHR SS. 
|-
| M ||LH6|| 5.3L || V8 || Gas ||OHV||SFI. Gen IV Chevrolet Small-Block V8. Active Fuel Management. Aluminum Block &amp; Heads.&lt;br /&gt; '05-'06 GMT370 SUVs (Trailblazer EXT/Envoy XL/Isuzu Ascender 7-psgr.), '05-'07 Buick Rainier,&lt;br /&gt; '05-'09 GMC Envoy Denali, Saab 9-7X, '06-'08 Chevy Trailblazer, '05 GMC Envoy XUV,&lt;br /&gt; '07-'09 Silverado/Sierra 1500
|-
| M ||LAF|| 2.4L || I4 || Gas ||DOHC,&lt;br /&gt; 16 valve||GM Ecotec engine, Gen II. Direct Injection. VVT. Chevy Orlando '12. 
|-
| M ||LE2|| 1.4L || I4 Turbo || Gas ||DOHC,&lt;br /&gt; 16 valve||GM Small Gasoline Engine. Direct Injection. VVT. '16-'19 &amp; '21-'22 Buick Encore, '21-'22 Chevy Trax.
|-
| N ||L10|| 1.8L || I4 || Gas ||SOHC,&lt;br /&gt; 8 valve||2-bbl carb. Isuzu G180Z engine imported from Japan. '81-'82 Chevy LUV
|-
| N ||LF9|| 5.7L || V8 || Diesel ||OHV||Oldsmobile Diesel V8. '83-'84 Chevy El Camino/GMC Caballero.
|-
| N ||LB1|| 4.3L || V6 || Gas ||OHV|| 4-bbl carb. Chevrolet 90° V6 (Chevy Small-Block V8 Derived).&lt;br /&gt; '85 Astro/Safari, '85-'86 C/K pickups &amp; full-size vans
|-
| N ||L19|| 7.4L || V8 || Gas ||OHV|| Mark IV Chevrolet Big-Block V8. TBI.&lt;br /&gt; '87-'90 R/V pickups, Suburban 2500, '88-'90 C/K, Sierra pickups, full-size vans
|-
| N ||L19|| 7.4L || V8 || Gas ||OHV|| Gen V Chevrolet Big-Block V8. TBI.&lt;br /&gt; '91 R/V pickups, '91-'95 C/K, Sierra pickups, Suburban 2500, full-size vans. '96 G-Classic full-size vans
|-
| N ||LZ4|| 3.5L || V6 || Gas ||OHV||GM High Value 60° V6. 3510cc. SFI. VVT. '08-'09 Saturn Vue
|-
| N ||LQ9|| 6.0L || V8 || Gas ||OHV|| Gen III Chevrolet Small-Block V8. Vortec 6000 H.O. or VortecMAX. Iron Block/Aluminum Heads.&lt;br /&gt; 345 hp. '02-'06 Cadillac Escalade, '03-'06 Cadillac Escalade ESV, '03-'06 Chevy Silverado SS,&lt;br /&gt; '05-'06 GMC Sierra Denali, '07 GMC Sierra Classic Denali.
|-
| N ||LGZ|| 3.6L || V6 || Gas ||DOHC,&lt;br /&gt; 24 valve||GM High Feature V6, 4th gen. Direct Injection. VVT. Active Fuel Management.&lt;br /&gt; '17-'22 Chevy Colorado, GMC Canyon.
|-
| P ||L49|| 6.5L || V8 || Diesel ||OHV||Detroit Diesel V8. For sub-8,500 lb. GVWR Chevy C/K, GMC Sierra trucks &amp; full-size vans '94-'95
|-
| P ||LM4|| 5.3L || V8 || Gas ||OHV||Gen III Chevrolet Small-Block V8. Vortec 5300. 290hp. Aluminum Block &amp; Heads.&lt;br /&gt; '03-'04 Chevy SSR, '03-'04 GMT370 SUVs (Trailblazer EXT/Envoy XL/Isuzu Ascender 7-psgr.),&lt;br /&gt; '04 Buick Rainier, GMC Envoy XUV
|-
| P ||LE5|| 2.4L || I4 || Gas ||DOHC,&lt;br /&gt; 16 valve||MFI. GM Ecotec Gen II. VVT. '06-'08 Chevy HHR, '08-'09 Saturn Vue 
|-
| P ||LH9|| 5.3L || V8 || Gas/E85  ||OHV||Flex Fuel. SFI. Gen IV Chevrolet Small-Block V8. Aluminum Block &amp; Heads. VVT.&lt;br /&gt; '10-'12 Colorado/Canyon, '10 Hummer H3 Alpha, H3T Alpha 
|-
| P ||LV1|| 4.3L || V6 || Gas ||OHV||Chevrolet 90° V6 - Gen V Chevrolet Small-Block V6 (EcoTec3). Direct injection, VVT.&lt;br /&gt; '18+ Chevy Express/GMC Savana.
|-
| P ||LBP|| 1.2L || I3 Turbo || Gas/E85 ||DOHC,&lt;br /&gt; 12 valve||Flex Fuel. GM E-Turbo Engine. Direct Injection. VVT.&lt;br /&gt; '25+ Buick Encore GX, Chevy Trailblazer, '25- Chevy Trax, Buick Envista.
|-
| R ||LL2|| 2.8L || V6 || Gas ||OHV||TBI. Chevrolet 60° V6. '86-'93 Chevy S-10, GMC S-15/Sonoma,&lt;br /&gt; '86-'89 Chevy S-10 Blazer/GMC S-15 Jimmy
|-
| R ||L31|| 5.7L || V8 || Gas ||OHV||Gen 1+ Chevrolet Small-Block V8. Vortec 5700. CPI.&lt;br /&gt; '96-'99 Chevy C/K, GMC Sierra, '96-'99 Chevy  Tahoe/GMC Yukon, Chevy/GMC Suburban, '99-'00 GMC Yukon Denali, Cadillac Escalade, '00 Chevy Tahoe Limited/Z71, '96-'02 Chevy Express/GMC Savana.
|-
| R ||L8B|| 5.3L || V8 || Gas ||OHV||Mild Hybrid. Gen V Chevrolet Small-Block V8 (EcoTec3). Direct injection, VVT. Active Fuel Management. '16-'18 Chevy Silverado 1500, GMC Sierra 1500. 
|-
| S ||LQ7|| 2.2L || I4 || Diesel ||OHV||Isuzu C220 engine imported from Japan. '81-'82 Chevy LUV, '84-'85 Chevy S-10/GMC S-15
|-
| S ||L56|| 6.5L || V8 Turbo || Diesel ||OHV||Detroit Diesel V8. For sub-8,500 lb. GVWR Chevy C/K, GMC Sierra trucks '94-'99,&lt;br /&gt; Chevy Blazer '94, Chevy Tahoe 2-d '95-'99, GMC Yukon 2-d '94-'97
|-
| S ||LL8|| 4.2L || I6 || Gas ||DOHC,&lt;br /&gt; 24 valve||Atlas I6. SFI. VVT. '02-'09 GMT360/370 SUVs (Chevy Trailblazer, GMC Envoy, Oldsmobile Bravada, Buick Rainier, Isuzu Ascender, Saab 9-7X)
|-
| S ||LGX|| 3.6L || V6 || Gas ||DOHC,&lt;br /&gt; 24 valve||GM High Feature V6, 4th gen. Direct Injection. VVT. Active Fuel Management.&lt;br /&gt; '17+ Cadillac XT5, '17-'23 GMC Acadia, '19+ Chevrolet Blazer, '20-'25 Cadillac XT6.
|-
| S ||LK0|| 2.5L || I4 Turbo || Gas ||DOHC,&lt;br /&gt; 16 valve||L3B engine family. Direct Injection. VVT. '24- Chevy Traverse, GMC Acadia, '25- Buick Enclave
|-
| T ||L25|| 4.8L || I6 || Gas ||OHV||1-bbl carb. Chevrolet Turbo-Thrift I6. '81-'86 Chevy/GMC C/K pickups, '88 R/V pickups
|-
| T ||LM7|| 5.3L || V8 || Gas ||OHV|| Gen III Chevrolet Small-Block V8. Iron Block &amp; Aluminum Heads. Vortec 5300. 270/285/295hp.&lt;br /&gt; '99-'07 GMT800 pickups &amp; SUVs including '02-'05 Escalade 2wd, '07 Silverado Classic 1500/&lt;br&gt; Sierra Classic 1500, '03-'07 Express/Savana
|-
| T ||LEA|| 2.4L || I4 || Gas/E85 ||DOHC,&lt;br /&gt; 16 valve||Flex Fuel. GM Ecotec engine, Gen II. Direct Injection. VVT. Chevy Orlando '13. 
|-
| T ||LM2|| 3.0L || I6 Turbo|| Diesel ||DOHC,&lt;br /&gt; 24 valve|| Duramax Diesel I6. Aluminum Block &amp; Heads. '20-'22 Silverado/Sierra 1500, '21-'24 Tahoe/Suburban, Yukon/Yukon XL, Escalade/Escalade ESV.
|-
| U ||LS5|| 1.6L || I4 || Gas ||SOHC,&lt;br /&gt; 8 valve||Suzuki G16A engine. TBI. '89-'95 Geo Tracker
|-
| U ||LQ4|| 6.0L || V8 || Gas ||OHV|| Gen III Chevrolet Small-Block V8. Iron Block &amp; Aluminum Heads (Iron Heads in '99-'00).&lt;br /&gt; '99-'06 GMT800 pickups, '07 Silverado Classic 1500HD/Sierra Classic 1500HD,&lt;br&gt; '00-'06 Suburban/Yukon XL 2500, '01-'06 Yukon Denali/Yukon XL Denali,&lt;br&gt; '06 Suburban LTZ, '03-'07 Express/Savana, '03-'07 Hummer H2.
|-
| U ||LE9|| 2.4L || I4 || Gas/E85 ||DOHC,&lt;br /&gt; 16 valve||Flex-Fuel. GM Ecotec Gen II. 2011 Chevy HHR 
|-
| U ||LH7|| 1.6L ||I4 Turbo|| Diesel ||DOHC,&lt;br /&gt; 16 valve||GM Medium Diesel engine (&quot;Whisper Diesel&quot;). Made by Opel in Szentgotthárd, Hungary.&lt;br /&gt; Aluminum Block &amp; Heads. '18-'19 Chevy Equinox &amp; GMC Terrain Diesel.
|-
| V ||LR4|| 4.8L || V8 || Gas ||OHV||Gen III Chevrolet Small-Block V8. Iron Block/Aluminum Heads.&lt;br&gt; '99-'06 GMT800 pickups, '07 Silverado Classic 1500/Sierra Classic 1500,&lt;br /&gt; '00-'06 Tahoe/Yukon, '03-'07 Express/Savana
|-
| V ||LE9|| 2.4L || I4 || Gas/E85 ||DOHC,&lt;br /&gt; 16 valve||Flex-Fuel. GM Ecotec Gen II. 2009-2010 Chevy HHR
|-
| V ||LYX|| 1.5L || I4 Turbo || Gas ||DOHC,&lt;br /&gt; 16 valve||GM Small Gasoline Engine. Direct Injection. VVT. '18-'22 Chevy Equinox, GMC Terrain
|-
| W ||LE8|| 7.4L || V8 || Gas ||OHV|| Mark IV Chevrolet Big-Block V8. 4bbl carb. '81-'86 Chevy/GMC C/K pickups, Suburban.&lt;br /&gt; '88-'89 Chevy/GMC R30/3500 Chassis Cab w/C7C (10,500 lb. GVWR),&lt;br /&gt; V30/3500 Chassis Cab w/C7E (11,000 lb. GVWR)
|-
| W ||L35|| 4.3L || V6 || Gas ||OHV|| CPI. Vortec 4300 H.O. Chevrolet 90° V6 (Chevy Small-Block V8 Derived).&lt;br /&gt; '92-'95 Sonoma, S-10 Blazer/Jimmy, Astro/Safari, '94-'95 S-10, '92-'94 Oldsmobile Bravada
|-
| W ||L35|| 4.3L || V6 || Gas ||OHV|| SFI. Vortec 4300 H.O. Chevrolet 90° V6 (Chevy Small-Block V8 Derived). '96-'02 S-10/Sonoma, Blazer/Jimmy, Express/Savana, C/K, Silverado, Sierra, '96-'01 Bravada, Astro/Safari, '00 Isuzu Hombre
|-
| W ||LGD|| 3.9L || V6 || Gas/E85 ||OHV||Flex Fuel. GM High Value 60° V6. SFI. VVT. '07-'09 GMT201 minivans
|-
| W ||LAF|| 2.4L || I4 || Gas ||DOHC,&lt;br /&gt; 16 valve||GM Ecotec engine, Gen II. Direct Injection. VVT. Chevy Equinox, GMC Terrain '10. 
|-
| W ||LE8|| 2.2L || I4 || Gas/E85 ||DOHC,&lt;br /&gt; 16 valve||Flex-Fuel. SFI. GM Ecotec Gen II. VVT. 2011 Chevy HHR.
|-
| W ||LFY|| 3.6L || V6 || Gas ||DOHC,&lt;br /&gt; 24 valve||GM High Feature V6. Direct Injection.&lt;br&gt; '18-'23 Chevrolet Traverse, '24 Chevrolet Traverse Limited, '18-'24 Buick Enclave.
|-
| X ||LF6|| 4.3L || V6 || Gas ||OHV||SFI. Vortec 4300. Chevrolet 90° V6 (Chevy Small-Block V8 Derived).&lt;br /&gt; '96-'99 S-10/Sonoma, '97-'99 Isuzu Hombre. 
|-
| X ||LU3|| 4.3L || V6 || Gas ||OHV||Vortec 4300. Chevrolet 90° V6 (Chevy Small-Block V8 Derived). '03-'04 S-10/Sonoma,&lt;br /&gt; '03-'05 Blazer/Jimmy, '02-'05 Astro/Safari, '03-'14 Express/Savana, '03-'13 Silverado/Sierra,&lt;br&gt; '07 Silverado Classic 1500/Sierra Classic 1500
|-
| X ||LNF|| 2.0L || I4 Turbo || Gas ||DOHC,&lt;br /&gt; 16 valve||GM Ecotec engine, Gen II. Direct Injection. VVT. '08-'09 Chevy HHR SS. 
|-
| X ||LTG|| 2.0L || I4 Turbo || Gas ||DOHC,&lt;br /&gt; 16 valve||GM Ecotec engine, Gen III. Direct Injection. VVT.&lt;br /&gt; '16-'20 Buick Envision, '18-'20 Chevy Equinox, GMC Terrain, '18-'19 Chevy Traverse RS
|-
| Y ||LQ2|| 2.0L || I4 || Gas ||OHV||2-bbl carb. Chevrolet &quot;122&quot; engine.&lt;br /&gt; '83-'84 Chevy S-10/GMC S-15, '83-'84 Chevy S-10 Blazer/GMC S-15 Jimmy
|-
| Y ||L57|| 6.5L || V8 || Diesel ||OHV||Detroit Diesel V8. For over-8,500 lb. GVWR full-size vans '94-'95 &amp; '96 G-Classic full-size vans
|-
| Y ||L76|| 6.0L || V8 || Gas ||OHV||SFI. Gen IV Chevy Small-Block V8. Aluminum Block &amp; Heads. VVT. With Active Fuel Management.&lt;br /&gt; '07-'09 Silverado/Sierra, Suburban/Yukon XL, Chevy Avalanche
|-
| Y ||LF1|| 3.0L || V6 || Gas ||DOHC,&lt;br /&gt; 24 valve||GM High Feature V6. Direct Injection. VVT.&lt;br /&gt; '10-'11 Cadillac SRX, '11 Saab 9-4X, '10 Chevy Equinox, GMC Terrain 
|-
| Y ||L5P|| 6.6L || V8 Turbo || Diesel ||OHV,&lt;br /&gt; 32 valve||Duramax 6600 V8 engine. '17+ Silverado HD/Sierra HD. Engine updated in '24. 
|-
| Z ||LF9|| 5.7L || V8 || Diesel ||OHV||Oldsmobile Diesel V8. '81 Chevy C10/GMC C1500 full-size pickups.
|-
| Z ||LB4|| 4.3L || V6 || Gas ||OHV|| TBI. Chevrolet 90° V6 (Chevy Small-Block V8 Derived). '85-'87 Chevy El Camino/GMC Caballero,&lt;br /&gt; '86-'94 Astro/Safari, '87 R/V pickups, '88-'95 C/K &amp; Sierra pickups, '87-'95 full-size vans &amp; &lt;br /&gt; '96 G-Classic full-size vans, '88-'95 S-10, S-15/Sonoma, '88-'94 S-10 Blazer, S-15 Jimmy,&lt;br /&gt; '91-'92 Oldsmobile Bravada
|-
| Z ||LB4|| 4.3L || V6 Turbo || Gas ||OHV|| MPI. For GMC Syclone &amp; Typhoon. Chevrolet 90° V6 (Chevy Small-Block V8 Derived)
|-
| Z ||L59|| 5.3L || V8 || Gas/E85 ||OHV||Flex Fuel. Gen III Chevrolet Small-Block V8. Iron Block &amp; Aluminum Heads. Vortec 5300. 285/295hp.&lt;br /&gt; '02-'07 GMT800 pickups, '07 Silverado Classic 1500/Sierra Classic 1500,&lt;br&gt; '02-'06 Suburban/Yukon XL, Avalanche.
|-
| Z ||LAT|| 2.4L || I4 || Gas ||DOHC,&lt;br /&gt; 16 valve||Mild Hybrid. MFI. GM Ecotec Gen II. VVT. '07-'09 Saturn Vue Green Line
|-
| 1 ||LZ9|| 3.9L || V6 || Gas ||OHV||GM High Value 60° V6. SFI. VVT. '06-'09 GMT201 minivans
|-
| 1 ||LE5|| 2.4L || I4 || Gas ||DOHC,&lt;br /&gt; 16 valve||MFI. GM Ecotec Gen II. VVT. '10 Saturn Vue.
|-
| 1 ||LB7|| 6.6L || V8 Turbo || Diesel ||OHV,&lt;br /&gt; 32 valve||Duramax 6600 V8 engine. First version of the Duramax V8. '01-Mid '04 Silverado HD/Sierra HD
|-
| 1 ||LWN|| 2.8L || I4 Turbo || Diesel ||DOHC,&lt;br /&gt; 16 valve||Based on VM Motori A428 engine. Made by GM Powertrain Thailand 2016-2020. Made in Brazil for '22. '16-'22 Colorado/Canyon, '17-'22 Express/Savana.
|-
| 2 ||LLY|| 6.6L || V8 Turbo || Diesel ||OHV,&lt;br /&gt; 32 valve||Duramax 6600 V8 engine. Mid '04-Mid '06 Silverado HD/Sierra HD, '06-Mid '07 Express/Savana
|-
| 2 ||L9H|| 6.2L || V8 || Gas/E85 ||OHV||Flex-Fuel. Gen IV Chevrolet Small-Block V8. Aluminum Block &amp; Heads. SFI. VVT.&lt;br /&gt; '09-'13 Chevy Silverado 1500, GMC Sierra 1500, Sierra Denali 1500,&lt;br /&gt; '09 Chevy Tahoe LTZ, GMC Yukon Denali/Yukon XL Denali, Cadillac Escalade/Escalade ESV,&lt;br&gt; Hummer H2
|-
| 2 ||LIH|| 1.2L || I3 Turbo || Gas ||DOHC,&lt;br /&gt; 12 valve||GM E-Turbo Engine. Direct Injection. VVT.&lt;br /&gt; '20-'24 Buick Encore GX, '21-'24 Chevy Trailblazer, '24 Chevy Trax, Buick Envista,&lt;br&gt; '25 Chevy Trax, Buick Envista (Canada only).
|-
| 3 ||LC9|| 5.3L || V8 || Gas/E85 ||OHV||Flex Fuel. SFI. Gen IV Chevrolet Small-Block V8. Active Fuel Management. VVT added for '10. Aluminum Block &amp; Heads.&lt;br /&gt; '07-'11 Silverado/Sierra 1500, Tahoe/Yukon, Suburban/Yukon XL 1500, '07-'09 &amp; '11 Avalanche
|-
| 3 ||LFX|| 3.6L || V6 || Gas ||DOHC,&lt;br /&gt; 24 valve||GM High Feature V6. Direct Injection. VVT. E85 Flex Fuel.&lt;br /&gt; '12-'16 Cadillac SRX, '13-'17 Chevrolet Equinox, GMC Terrain, '15-'16 Colorado/Canyon
|-
| 4 ||LN2|| 2.2L || I4 || Gas ||OHV||MFI (94-95). SFI (96-00). Chevrolet &quot;122&quot; engine. '94-'00 S-10/Sonoma, '96-'00 Isuzu Hombre
|-
| 4 ||LE8|| 2.5L || V6 || Gas ||DOHC,&lt;br /&gt; 24 valve||Suzuki H25A engine. MFI. '01-'04 Chevrolet Tracker
|-
| 4 ||L66|| 3.5L || V6 || Gas ||SOHC,&lt;br /&gt; 24 valve||Honda J35S1 V6. VTEC. '04-'07 Saturn Vue
|-
| 4 ||LMF|| 5.3L || V8 || Gas/E85  ||OHV||Flex Fuel. SFI. Gen IV Chevrolet Small-Block V8. Iron Block &amp; Aluminum Heads. VVT.&lt;br /&gt; '08-'14 Express/Savana 1500
|-
| 4 ||LAU|| 2.8L || V6 Turbo || Gas ||DOHC,&lt;br /&gt; 24 valve||GM High Feature V6. SFI. '10 Cadillac SRX
|-
| 4 ||LSY|| 2.0L || I4 Turbo || Gas ||DOHC,&lt;br /&gt; 16 valve||GM Ecotec engine, Gen III. Direct Injection. Active Fuel Management. VVT. VVL.&lt;br /&gt; '19-'25 Cadillac XT4, '20+ Chevy Blazer, Cadillac XT5, '20-'23 GMC Acadia,&lt;br /&gt; '21+ Buick Envision, '21-'25 Cadillac XT6
|-
| 5 ||L43|| 2.2L || I4 || Gas/E85 ||OHV||Flex-Fuel. SFI. Chevrolet &quot;122&quot; engine. '00-'02 S-10/Sonoma, '00 Isuzu Hombre
|-
| 5 ||LFA|| 6.0L || V8 || Gas-Electric Hybrid ||OHV||2-Mode Hybrid. Gen IV Chevrolet Small-Block V8. Aluminum Block &amp; Heads. VVT. Active Fuel Management. '08-'09 Tahoe Hybrid/Yukon Hybrid, '09 Escalade Hybrid, Silverado Hybrid/Sierra Hybrid
|-
| 5 ||LFW|| 3.0L || V6 || Gas/E85 ||DOHC,&lt;br /&gt; 24 valve||Flex-Fuel. GM High Feature V6. Direct Injection. VVT. '11-'12 Chevy Equinox, GMC Terrain,&lt;br /&gt; '12 Chevy Captiva Sport
|-
| 6 ||L01|| 1.6L || I4 || Gas ||SOHC,&lt;br /&gt; 16 valve||Suzuki G16B engine. MFI. '94-'97 Geo Tracker, '98-'00 Chevrolet Tracker
|-
| 6 ||L52|| 3.5L || I5 || Gas ||DOHC,&lt;br /&gt; 20 valve||Atlas I5. SFI. VVT. '04-'06 Colorado/Canyon, '06 Isuzu i-350, '06 Hummer H3
|-
| 6 ||LAU|| 2.8L || V6 Turbo || Gas ||DOHC,&lt;br /&gt; 24 valve||GM High Feature V6. SFI. '11 Cadillac SRX, Saab 9-4X
|-
| 6 ||LMM|| 6.6L || V8 Turbo || Diesel ||OHV,&lt;br /&gt; 32 valve||Duramax 6600 V8 engine. '07-'10 Silverado HD/Sierra HD (GMT900), Mid '07-Mid '10 Express/Savana
|-
| 7 ||LY7|| 3.6L || V6 || Gas ||DOHC,&lt;br /&gt; 24 valve||GM High Feature V6. '04-'06 Buick Rendezvous, '04-'09 Cadillac SRX,&lt;br /&gt; '07-'08 GMC Acadia, Saturn Outlook, '08 Buick Enclave, '08-'10 Saturn Vue
|-
| 7 ||LC9|| 5.3L || V8 || Gas/E85 ||OHV||Flex Fuel. SFI. Gen IV Chevrolet Small-Block V8. Active Fuel Management. VVT.&lt;br /&gt; Aluminum Block &amp; Heads.&lt;br /&gt; '12-'13 Silverado/Sierra 1500, Avalanche, '12-'14 Tahoe/Yukon, Suburban/Yukon XL 1500
|-
| 7 ||L8T|| 6.6L || V8 || Gas ||OHV||Gen V Chevrolet Small-Block V8. Iron Block/Aluminum Heads. Direct injection, VVT.&lt;br /&gt; '20+ Silverado HD/Sierra HD, '21+ Express/Savana
|-
| 8 ||LK5|| 2.8L || I4 || Gas ||DOHC,&lt;br /&gt; 16 valve||Atlas I4. SFI. VVT. '04-'06 Colorado/Canyon, '06 Isuzu i-280.
|-
| 8 ||L92|| 6.2L || V8 || Gas ||OHV||Gen IV Chevrolet Small-Block V8. Aluminum Block &amp; Heads. SFI. VVT.&lt;br /&gt; '07-'08 GMC Sierra Denali, Yukon Denali/Yukon XL Denali, Cadillac Escalade/Escalade ESV,&lt;br&gt; '08 Chevy Tahoe LTZ, Hummer H2.
|-
| 8 ||LML|| 6.6L || V8 Turbo || Diesel ||OHV,&lt;br /&gt; 32 valve||Duramax 6600 V8 engine.&lt;br /&gt; '11-'16 Silverado HD/Sierra HD pickups, '13-'16 Silverado HD/Sierra HD chassis cabs.
|-
| 8 ||LZ0|| 3.0L || I6 Turbo|| Diesel ||DOHC,&lt;br /&gt; 24 valve|| Duramax Diesel I6. Aluminum Block &amp; Heads.&lt;br&gt; '23+ Silverado/Sierra 1500, '24+ Suburban HD, '25+ Tahoe/Suburban, Yukon/Yukon XL.
|-
| 9 ||LC3|| 3.8L || V6 || Gas ||OHV||2-bbl carb. Chevrolet 90° V6 (Chevy Small-Block V8 Derived). 229 cu. in. &lt;br /&gt; '83-'84 Chevy El Camino, GMC Caballero (49-state emissions).
|-
| 9 ||LLV|| 2.9L || I4 || Gas ||DOHC,&lt;br /&gt; 16 valve||Atlas I4. SFI. VVT. '07-'12 Colorado/Canyon, '07-'08 Isuzu i-290.
|-
| 9 ||LT4|| 6.2L ||V8 Supercharged|| Gas ||OHV||Gen V Chevy Small-Block V8. Aluminum Block &amp; Heads. Direct injection. VVT. Active Fuel Management. '23+ Cadillac Escalade/Escalade ESV V-Series.
|-
| 0 ||LMG|| 5.3L || V8 || Gas/E85 ||OHV||Flex-Fuel. SFI. Gen IV Chevrolet Small-Block V8. Active Fuel Management. VVT added for '10.&lt;br /&gt; Iron Block &amp; Aluminum Heads.&lt;br /&gt; '07-'13 Silverado/Sierra 1500, Avalanche, '07-'14 Tahoe/Yukon, Suburban/Yukon XL 1500.
|}
H.O.=High Output, VVT=Variable Valve Timing, VVL=Variable Valve Lift, GVWR=Gross Vehicle Weight Rating, CNG=Compressed Natural Gas, LPG=Liquefied Petroleum Gas (Propane Autogas)

====Motor codes for electric light trucks====

{| class=&quot;wikitable&quot;
|-
! VIN !! RPO !! Fuel !! Drive Wheels !! Application/Notes
|-
| H ||LN1|| Electricity || Front || '97-'98 Chevrolet S-10 Electric.
|-
|}

====Motor codes for Ultium-powered electric light trucks====

{| class=&quot;wikitable&quot;
|-
! VIN !! Motor &lt;br /&gt; RPO code !! # of Motors !! Battery Module &lt;br /&gt; RPO code !! # of Modules !! Fuel !! Drive Wheels !! Application/Notes
|-
| A ||XRL|| 3 || ETN || 24 || Electricity || All || '22- GMC Hummer EV pickup 3X
|-
| B ||XRL|| 3 || ETI || 20 || Electricity || All || '24- GMC Hummer EV pickup 3X
|-
| C ||XRL|| 3 || ETJ || 20 || Electricity || All || '24- GMC Hummer EV SUV 3X
|-
| D ||XRJ|| 2 || ETI || 20 || Electricity || All || '24 Chevrolet Silverado EV 3WT, '25- Silverado EV 5WT, 3LT,&lt;br&gt; '25 Silverado EV RST (2SP), '26- Silverado EV Trail Boss (2TR),&lt;br&gt; '24- GMC Hummer EV pickup 2X, '25- GMC Sierra EV Denali 5SC,&lt;br&gt; '26- Sierra EV Elevation 3SC, AT4 4SC
|-
| E ||XRJ|| 2 || ETJ || 20 || Electricity || All || '24- GMC Hummer EV SUV 2X
|-
| G ||XRJ|| 2 || ETJ || 20 || Electricity || All || '23 BrightDrop Zevo 600
|-
| H ||XRJ|| 2 || EWX || 14 || Electricity || All ||'26- Chevrolet Silverado EV 4WT, 2LT,&lt;br&gt; '26- GMC Sierra EV Elevation 3SB, Denali 5SB
|-
| J ||X0C|| 2 || EC5 || 10 || Electricity || All || '24 Chevy Blazer EV 2LT, 1RS AWD,&lt;br&gt; '25- Chevy Blazer EV 4LT, 3RS AWD, '24-'26 Honda Prologue AWD
|-
| K ||X0D|| 1 || EC6 || 12 || Electricity || Rear || '23- Cadillac Lyriq RWD, '24-'25 Chevrolet Blazer EV 2RS RWD,&lt;br&gt; '24 Acura ZDX A-Spec RWD
|-
| L ||X0E|| 2 || EC6 || 12 || Electricity || All || '23- Cadillac Lyriq AWD, '24- Chevrolet Blazer EV PPV AWD,&lt;br&gt; '25- Chevrolet Blazer EV SS AWD, '26- Cadillac Vistiq AWD,&lt;br&gt; '24 Acura ZDX A-Spec, Type S AWD
|-
| L ||XRJ|| 2 || ETN || 24 || Electricity || All || '24 Chevrolet Silverado EV 4WT, RST (3SP), '25- Silverado EV 8WT,&lt;br&gt; '25 Silverado EV RST (3SP), '26- Silverado EV 4LT, Trail Boss (3TR),&lt;br&gt; '24- GMC Sierra EV Denali 5SD, '26- Sierra EV AT4 4SD,&lt;br&gt; '25- Cadillac Escalade IQ, '26- Cadillac Escalade IQL
|-
| M ||X0B|| 1 || EC5 || 10 || Electricity || Front || '24-'26 Honda Prologue FWD, '25- Chevy Blazer EV 2LT, 1RS FWD
|-
| P ||X0B|| 1 || EC3 || 10 || Electricity || Front || '24- Chevrolet Equinox EV FWD
|-
| R ||X0C|| 2 || EC3 || 10 || Electricity || All || '24- Chevrolet Equinox EV AWD, '25 Cadillac Optiq AWD
|-
| Y ||XRJ|| 2 || ETC || 12 || Electricity || All || '24 BrightDrop Zevo 400, Zevo 600,&lt;br&gt; '25-'26 Chevrolet BrightDrop 400/600 AWD
|-
| Z ||XRJ|| 2 || ETJ || 20 || Electricity || All || '24 BrightDrop Zevo 400, Zevo 600,&lt;br&gt; '25-'26 Chevrolet BrightDrop 400/600 AWD
|-
| 4 ||X0E|| 2 || EC3 || 10 || Electricity || All || '26- Cadillac Optiq AWD
|-
| 5 ||X0D|| 1 || EC3 || 10 || Electricity || Rear|| '26- Cadillac Optiq RWD
|-
| 6 ||XRM|| 1 || ETC || 12 || Electricity || Front || '25-'26 Chevrolet BrightDrop 400/600 FWD
|-
| 7 ||XRJ|| 2 || EWU || 14 || Electricity || All || '26 Chevrolet BrightDrop 600 AWD
|}
SB=Standard Range, SC=Extended Range, SD=Max Range

====Engine codes for medium duty trucks 2016-====
GM encodes the engine type in character 8 of the VIN. The following table outlines the various engines encoded there:

{| class=&quot;wikitable&quot;
|-
! VIN !! RPO !! Size !! Type !! Fuel !! Valvetrain !! Engine Family/Notes/Applications
|-
| B ||L96|| 6.0L || V8 || Gas ||OHV||SFI. Gen IV Chevrolet Small-Block V8. Iron Block &amp; Aluminum Heads. VVT.&lt;br /&gt; '16-'20 Chevy LCF 3500/4500.
|-
| C ||LC8|| 6.0L || V8 || Gas/CNG or&lt;br&gt;Gas/LPG ||OHV||Bi-Fuel. SFI. Gen IV Chevrolet Small-Block V8. Iron Block &amp; Aluminum Heads. VVT.&lt;br /&gt; '16-'20 Chevy LCF 3500/4500.
|-
| D ||L8T|| 6.6L || V8 || Gas ||OHV||Gen V Chevrolet Small-Block V8. Iron Block/Aluminum Heads. Direct injection, VVT.&lt;br /&gt; '21-'23 Chevy LCF 3500/4500, '24- Chevy LCF 3500HG/4500HG/5500HG/5500XG.
|-
| F ||LCB|| 6.7L || I6 Turbo || Diesel ||OHV,&lt;br /&gt; 32 valve||Cummins B Series ISB engine. '22- Chevy LCF 6500XD, '23- Chevy LCF 7500XD.
|-
| 6 ||I1B|| 5.2L || I4 Turbo || Diesel ||SOHC,&lt;br /&gt; 16 valve||Isuzu 4HK1-TC engine. '17- Chevy LCF 4500HD/XD, 5500XD, '17-'24 Chevy LCF 5500HD,&lt;br /&gt; '18-'21 Chevy LCF 6500XD.
|-
| 7 ||IZ3|| 3.0L || I4 Turbo || Diesel ||DOHC,&lt;br /&gt; 16 valve||Isuzu 4JJ1-TC engine. '16-'18 Chevy LCF 3500HD.
|-
|}

====Engine codes for AM General-built Hummer H1 2000-2006====
AM General encodes the engine type in character 4 of the VIN.

{| class=&quot;wikitable&quot;
|-
! VIN !! RPO !! Size !! Type !! Fuel !! Valvetrain !! Engine Family/Notes
|-
| F || || 6.5L || V8 Turbo || Diesel ||OHV||Detroit Diesel V8 built by GEP (General Engine Products), a subsidiary of AM General.&lt;br&gt; '01-'04 Hummer H1 &amp; '06 H1 Fleet models.
|-
| P ||LLY|| 6.6L || V8 Turbo || Diesel ||OHV,&lt;br /&gt; 32 valve||Duramax 6600 V8 engine. '06 Hummer H1 Alpha.
|-
| Z ||L65|| 6.5L || V8 Turbo || Diesel ||OHV||Detroit Diesel V8 built by GM. '00-'01 Hummer H1.
|-
|}

====Engine codes for Nissan-built vans====
Nissan encodes the engine type in character 4 of the VIN.

{| class=&quot;wikitable&quot;
|-
! VIN !! RPO !! Size !! Type !! Fuel !! Valvetrain !! Engine Family/Notes
|-
| 3 ||L0A|| 2.0L || I4 || Gas ||DOHC,&lt;br /&gt; 16 valve||Nissan MR20DE engine. SFI. VVT. For the '15-'18 Chevrolet City Express.
|-
|}

====Engine codes for Navistar-built medium-duty trucks====
Navistar encodes the engine type in character 6 &amp; 7 of the VIN.

{| class=&quot;wikitable&quot;
|-
! VIN !! RPO !! Size !! Type !! Fuel !! Valvetrain !! Engine Family/Notes
|-
| PV ||L5D|| 6.6L || V8 Turbo || Diesel ||OHV,&lt;br /&gt; 32 valve||Duramax 6600 V8 engine. For the Chevy Silverado Medium Duty '19+.
|-
|}

==GM factories supplying North America==

===North American GM factories===
[[w:List_of_General_Motors_factories | List of GM Factories]]
{| class=&quot;wikitable&quot;
!VIN code
!Location
!Notes
|-
|A
|Lakewood Assembly (Lakewood Heights, Atlanta, Georgia)
|through 1990 model year
|-
|A
|Artisan Center (Warren, Michigan)
|From 2026 model year. Cadillac CT5-V Blackwing &quot;Curated by Cadillac&quot; program only.
|-
|B
|Baltimore Assembly (Baltimore, Maryland)
|through 2005 model year
|-
|B
|Reatta Craft Centre/Lansing Craft Centre (Lansing Township, Michigan)
|1988-2006 model year (except GM EV1)
|-
|B
|GM Defense-Manufacturing Customer Innovation Center (MCIC) (Concord, North Carolina)
|From 2024 model year. Chevrolet Suburban HD (a.k.a. HD SUV) (for US govt. only).
|-
|C
|South Gate Assembly (South Gate, California)
|through 1982 model year
|-
|C
|Lansing Car Assembly (Lansing, Michigan)
|South assembly line 1985-2004 model year
|-
|D
|Doraville Assembly (Doraville, Georgia)
|through 2009 model year
|-
|E
|Linden Assembly (Linden, New Jersey)
|through 1991 model year
|-
|E
|Pontiac East Assembly (Pontiac, Michigan) 
|1988-2009 model year
|-
|E
|AM General Military plant (Mishawaka, Indiana)
|1992-2006 Hummer H1
|-
|F
|Flint Truck Assembly (Flint, Michigan) 
|since 1953
|-
|F
|Fairfax II Assembly (Kansas City, Kansas)
|since 1988 model year
|-
|G
|Framingham Assembly (Framingham, Massachusetts)
|through 1989 model year
|-
|G
|Silao Assembly (Silao, Guanajuato, Mexico)
|since 1995 model year
|-
|H
|Buick City Assembly (Flint, Michigan)
|through 1999 model year
|-
|H
|AM General Commercial plant (Mishawaka, Indiana)
|2003-2009 Hummer H2
|-
|H
|Navistar Springfield plant (Main Line) (Springfield, Ohio)
|2019- Chevrolet Silverado Medium Duty (4500HD/5500HD/6500HD)
|-
|J
|Janesville Assembly (Janesville, Wisconsin)
|through 2009 model year
|-
|J
|Lansing Delta Township Assembly (Lansing, Michigan)
|since 2007 model year
|-
|K
|Leeds Assembly (Leeds, Kansas City, Missouri)
|through 1988 model year
|-
|K
|Linden Assembly (Linden, New Jersey)
|from 1994-2005 model year
|-
|K
|Nissan plant (Cuernavaca, Morelos, Mexico)
|2015-2018 Chevrolet City Express
|-
|L
|Van Nuys Assembly (Van Nuys, California)
|through 1992 model year
|-
|L
|San Luis Potosí Assembly (San Luis Potosí, Mexico)
|since 2009 model year
|-
|M
|Lansing Car Assembly (Lansing, Michigan)
|through 1984 model year, North assembly line 1985-2005 model year
|-
|M
|Toluca Assembly (Toluca, Mexico state, Mexico)
|through 2008 model year
|-
|N
|Norwood Assembly (Norwood, Ohio) 
|through 1987 model year
|-
|N
|Navistar Springfield plant (Secondary Line) (Springfield, Ohio)
|2017- Chevrolet Express cutaway, GMC Savana cutaway
|-
|P
|Pontiac Assembly (Pontiac, Michigan)
|through 1988 model year
|-
|R
|Arlington Assembly (Arlington, Texas)
|since 1965 [all GM brands]. (R plant code used only by Chevrolet in 1963-64)
|-
|S
|St. Louis Assembly (St. Louis, Missouri)
|through 1987 model year
|-
|S
|Spring Hill Manufacturing (Spring Hill, Tennessee) 
|2002-2007 Saturn Vue &amp; 2009-2010 Chevrolet Traverse only
|-
|S
|Spartan Motors/Shyft Group plant (Charlotte, Michigan) 
|2016- Chevrolet Low Cab Forward 3500/3500HG/4500/4500HG/5500HG/5500XG/6500XD/7500XD
|-
|S
|Ramos Arizpe Assembly (Ramos Arizpe, Coahuila, Mexico)
|since 1982
|-
|T
|Tarrytown Assembly (North Tarrytown, New York)
|through 1996 model year 
|-
|U
|Detroit/Hamtramck Assembly (Factory Zero) &lt;br /&gt; (Detroit &amp; Hamtramck, Michigan)
|since 1986 model year
|-
|U
|Artisan Center (Warren, Michigan)
|From 2025 model year. Cadillac Celestiq only.
|-
|V
|Pontiac Central Assembly (Pontiac, Michigan) 
|through 1991 model year
|-
|V
|Pontiac East Assembly (Pontiac, Michigan) 
|through 1985 model year
|-
|W
|Willow Run Assembly (Ypsilanti Township, Michigan) 
|through 1993 model year
|-
|X
|Fairfax Assembly (Fairfax I) (Kansas City, Kansas)
|through 1987 model year
|-
|Y
|Wilmington Assembly (Wilmington, Delaware) 
|through 2010 model year
|-
|Z
|Fremont Assembly (Fremont, California) 
|through 1982 model year
|-
|Z
|NUMMI (Fremont, California) 
|1985-2010 model year
|-
|Z
|Spring Hill Manufacturing (Spring Hill, Tennessee) 
|since 1991 model year (except Vue &amp; Traverse)
|-
|Z
|Fort Wayne Assembly (Roanoke, Indiana) 
|since 1988 model year
|-
|0
|Pontiac West Assembly (Pontiac, Michigan) 
|through 1994 model year
|-
|0
|Lansing Craft Centre (Lansing Township, Michigan)
|GM EV1 only
|-
|0
|Lansing Grand River Assembly (Lansing, Michigan) 
|since 2003 model year
|-
|0
|Artisan Center (Warren, Michigan)
|2024 Cadillac CT5-V Blackwing 20th Anniversary Edition where the final eight digits of the VIN are R0912004 through R0912024 or R0962004 through R0962024
|-
|1
|Wentzville Assembly (Wentzville, Missouri) 
|since 1985 model year
|-
|1
|Oshawa Car Assembly (Oshawa, Ontario, Canada) 
|from 1967-1983 model year
|-
|1
|Oshawa Car Assembly (Line 2 a.k.a. Consolidated Line) (Oshawa, Ontario, Canada) 
|from 1984-2019 model year; switched to pickup trucks for 2019 model year
|-
|1
|Oshawa Car Assembly (Oshawa, Ontario, Canada) 
|Silverado pickup trucks since 2022 model year
|-
|1
|Oshawa Truck Assembly (Oshawa, Ontario, Canada) 
|through 2009 model year
|-
|2
|Moraine Assembly (Moraine, Ohio) 
|through 2009 model year
|-
|2
|Sainte-Thérèse Assembly (Boisbriand, Quebec, Canada) 
|through 2002 model year
|-
|3
|Detroit Truck &amp; Bus plant (Piquette Ave., Detroit, Michigan) 
|through 1999 model year
|-
|3
|Saint-Eustache Bus Plant (Saint-Eustache, Quebec, Canada) 
|through 1987 model year
|-
|4
|Orion Assembly (Orion Township, Michigan) 
|since 1985 model year
|-
|4
|Scarborough Van Assembly (Scarborough, Ontario, Canada) 
|through 1993 model year
|-
|5
|Bowling Green Assembly (Bowling Green, Kentucky) 
|since 1981 model year
|-
|6
|Oklahoma City Assembly (Oklahoma City, Oklahoma) 
|through 2006 model year
|-
|6
|CAMI plant (Ingersoll, Ontario, Canada) 
|1990-2022 model year
|-
|7
|Lordstown Assembly (Warren, Ohio) 
|from 1979-2019 model year
|-
|8
|Shreveport Assembly (Shreveport, Louisiana) 
|through 2012 model year
|-
|9
|Detroit Assembly (Clark Street, Detroit, Michigan)&lt;br&gt; (Cadillac plant)
|from 1979-1988 model year
|-
|9
|Oshawa Car Assembly (Line 1 a.k.a. Flex Line)&lt;br&gt; (Oshawa, Ontario, Canada) 
|from 1984-2020 model year
|-
|9
|KUKA plant (Livonia, Michigan) 
|2022 model year only (BrightDrop Zevo 600)
|-
|9
|CAMI plant (Ingersoll, Ontario, Canada) 
|2023-2026 model year (BrightDrop Zevo/Chevrolet BrightDrop)
|}

===Non-North American GM factories supplying North America===
{| class=&quot;wikitable&quot;
!VIN code
!Location
!Models Sourced
|-
|A
|SAIC-GM plant: Jinqiao, Pudong district, Shanghai, China
|2017-2018 Cadillac CT6 Plug-in Hybrid
|-
|B
|Daewoo/GM Daewoo/GM Korea plant: Bupyeong, South Korea
|1988-1993 Pontiac LeMans, 2004-2011 Chevrolet Aveo, 2005-2010 Pontiac Wave/G3, 2004-2006 Chevrolet &lt;br /&gt; Epica (Canada), 2013-2022 Chevrolet Trax, Buick Encore, 2021- Chevrolet Trailblazer, 2020- Buick Encore GX, 2024- Buick Envista
|-
|C
|GM Daewoo/GM Korea plant: Changwon, South Korea
|2003-2010 Pontiac Matiz/Matiz G2 (Mexico), 2013-2022 Chevrolet Spark, 2024- Chevrolet Trax
|-
|D
|SAIC-GM Dongyue Motors plant: Yantai, Shandong province, China
|2016- Buick Envision, 2019-2023 Chevrolet Aveo (Mexico), 2023- Chevrolet Onix (Mexico)
|-
|G
|Opel plant: Gliwice, Poland
|2016-2019 Buick Cascada
|-
|K
|Suzuki plant: Kosai, Shizuoka prefecture, Japan
|1985-1988 Chevrolet Sprint, 1989-1990 Geo Metro hatchback, 1990-1993 Geo Metro convertible, 1985-1990 Pontiac Firefly (Canada), 1991 &amp; 1994 Pontiac Firefly convertible &amp; sedan (Canada)
|-
|K
|GM Daewoo/GM Korea plant: Kunsan, South Korea
|2004-2007 Chevrolet Optra (Canada), 2012-2014 Chevrolet Orlando (Canada)
|-
|L
|Holden plant:  Elizabeth, South Australia, Australia
|2004-2006 Pontiac GTO, 2008-2009 Pontiac G8, 2011-2017 Chevrolet Caprice PPV, 2014-2017 Chevrolet SS
|-
|R
|Opel plant: Rüsselsheim, Germany
|1997-2001 Cadillac Catera
|-
|T
|GM India plant: Talegaon, Maharashtra, India
|2017-2021 Chevrolet Spark Classic/Beat (Mexico)
|-
|V
|SAIC-GM Wuhan plant: Wuhan, Hubei province, China
|2018-2021 Chevrolet Cavalier (Mexico), 2022- Chevrolet Cavalier Turbo (Mexico)
|-
|W
|Suzuki plant: Iwata, Shizuoka prefecture, Japan
|1989-1990 Geo Tracker
|-
|1
|Opel plant: Rüsselsheim, Germany
|2011, 2018-2020 Buick Regal
|-
|3
|Isuzu plant: Kawasaki, Kanagawa prefecture, Japan
|1987-1998 Chevrolet/GMC W5, 1989-1996 Chevrolet/GMC W6, 1984-1996 Chevrolet/GMC W7
|-
|5
|Opel plant: Antwerp, Belgium
|2008-2009 Saturn Astra
|-
|7
|Isuzu plant: Fujisawa, Kanagawa prefecture, Japan
|1988 Chevrolet Spectrum, 1988 Pontiac Sunburst (Canada), 1989 Geo Spectrum, 1990-1993 Geo Storm,&lt;br /&gt; 1999-2008 Chevrolet/GMC W3500, 1988-2009 Chevrolet/GMC W4, 1999-2009 Chevrolet/GMC W5,&lt;br /&gt; 2000-2004 Chevrolet/GMC WT5500,&lt;br /&gt; 2016- Chevrolet Low Cab Forward 3500HD/4500HD/4500XD/5500HD/5500XD
|-
|8
|Isuzu plant: Fujisawa, Kanagawa prefecture, Japan
|1981-1982 Chevrolet LUV, 1985-1987 Chevrolet Spectrum, 1985-1987 Pontiac Sunburst (Canada),&lt;br /&gt; 1986-1987 Chevrolet/GMC W4
|}

==GM WMIs==

{| class=wikitable
!WMI
!Marque
!Country
|-
|1G1||rowspan=57|Chevrolet||United States
|-
|1G8||United States (MPV 1981-1986)
|-
|1GA||United States (bus [van with more than 3 rows of seats])
|-
|1GB||United States (incomplete vehicle)
|-
|1GC||United States (truck)
|-
|1GN||United States (MPV 1987-)
|-
|1HA||United States (Express incomplete vehicle made by Navistar)
|-
|1HT||United States ([[w:Chevrolet Silverado#Medium duty version_(4500HD,_5500HD,_6500HD,_and_International_CV)|Silverado Medium Duty]] incomplete vehicle made by Navistar)
|-
|1Y1||United States (made by NUMMI)
|-
|2C1||Canada (car made by CAMI)
|-
|2CN||Canada (SUV made by CAMI - 1998-2011)
|-
|2G1||Canada
|-
|2G5||Canada (truck - Chevrolet BrightDrop '25)
|-
|2G8||Canada (MPV 1981-1986)
|-
|2GA||Canada (bus [van with more than 3 rows of seats])
|-
|2GB||Canada (incomplete vehicle)
|-
|2GC||Canada (truck - includes Chevrolet BrightDrop '26)
|-
|2GN||Canada (MPV 1987-)
|-
|3G1||Mexico
|-
|3GC||Mexico (truck)
|-
|3GN||Mexico (MPV)
|-
|3N6||Mexico (Truck - City Express made by Nissan)
|-
|4G1||United States (made by Genasys L.C.)
|-
|4KB||United States (W-Series incomplete vehicle made by GM - through 2009)
|-
|4W1||United States (MPV - Chevrolet Suburban HD made for US govt. in Concord, NC)
|-
|54D||United States (incomplete vehicle made by Spartan Motors/The Shyft Group)
|-
|6G1||Australia (2011-2013 Caprice PPV)
|-
|6G3||Australia (2014-2017 Caprice PPV &amp; SS performance sedan)
|-
|ADM||South Africa
|-
|J81||Japan (car made by Isuzu)
|-
|J8B||Japan (incomplete vehicle made by Isuzu - through 2009)
|-
|J8Z||Japan (LUV pickup made by Isuzu)
|-
|JAL||Japan (incomplete vehicle made by Isuzu - 2016+)
|-
|JG1||Japan (car made by Suzuki)
|-
|KL1||South Korea (car)
|-
|KL7||South Korea (MPV - 2012+)
|-
|KL8||South Korea (Spark)
|-
|LSF||China (S-10 Max made by SAIC-Maxus - Mexico only)
|-
|LSG||China (SAIC-GM)
|-
|LSH||China (Express Max made by SAIC-Maxus - Mexico only)
|-
|LZW||China (SAIC-GM-Wuling)
|-
|MA6||India
|-
|MJB||Indonesia (GM Indonesia)
|-
|MK3||Indonesia (SGMW Motor Indonesia)
|-
|MMM||Thailand
|-
|XUF||Russia (GM Russia - St. Petersburg plant)
|-
|XUU||Russia (Chevrolet Korea models made by Avtotor in Kaliningrad)
|-
|XWB||Uzbekistan (GM Uzbekistan, UzAuto Motors)
|-
|XWF||Russia (Chevrolet Tahoe &amp; Trailblazer [GMT360] made by Avtotor in Kaliningrad)
|-
|X9L||Russia (GM-AvtoVAZ)
|-
|8AG||Argentina
|-
|8GG||Chile
|-
|8LD||Ecuador
|-
|8Z1||Venezuela
|-
|9BG||Brazil
|-
|93C||Brazil
|-
|9GC||Colombia
|-
|J81||rowspan=6|Geo||Japan (car made by Isuzu)
|-
|JG1||Japan (car made by Suzuki)
|-
|JGC||Japan (SUV made by Suzuki)
|-
|1Y1||United States (car made by NUMMI)
|-
|2C1||Canada (car made by CAMI)
|-
|2CN||Canada (SUV made by CAMI - 1990-1997)
|-
|KLA||rowspan=3|GM Daewoo/&lt;br /&gt;GM Korea||South Korea (Bupyeong &amp; Kunsan plants)
|-
|KLY||South Korea (Changwon plant)
|-
|5GD||United States (G2X)
|-
|1G2||rowspan=12|Pontiac||United States
|-
|1G5||United States (incomplete vehicle - for '89-'90 Turbo Grand Prix by ASC/McLaren &amp; '03-'05 Montana Mobility, '06 Montana SV6 Mobility)
|-
|1GM||United States (MPV)
|-
|2CK||Canada (2006-2009 Torrent made by CAMI)
|-
|2G2||Canada
|-
|2G7||Canada (US market 1983 Pontiac Parisienne)
|-
|3G2||Mexico
|-
|3G7||Mexico (MPV: 2001-2005 Aztek)
|-
|4G2||United States (made by Genasys L.C.)
|-
|5Y2||United States (made by NUMMI)
|-
|6G2||Australia
|-
|KL2||South Korea (made by Daewoo/GM Daewoo)
|-
|1G7||rowspan=6|Pontiac&lt;br /&gt;(Canada only)||United States
|-
|2C7||Canada (car made by CAMI)
|-
|2CG||Canada (SUV made by CAMI)
|-
|2G7||Canada
|-
|J87||Japan (car made by Isuzu)
|-
|JG7||Japan (car made by Suzuki)
|-
|KL7||Passport&lt;br /&gt;(Canada only)||South Korea (car made by Daewoo)
|-
|J87||rowspan=3|Asüna&lt;br /&gt;(Canada only)||Japan (car made by Isuzu)
|-
|KL7||South Korea (car made by Daewoo)
|-
|2CG||Canada (SUV made by CAMI)
|-
|1G3||rowspan=3|Oldsmobile||United States
|-
|1GH||United States (MPV/SUV)
|-
|2G3||Canada
|-
|1G4||rowspan=9|Buick||United States
|-
|2G4||Canada
|-
|3G4||Mexico
|-
|3G5||Mexico (MPV)
|-
|4GL||United States (incomplete vehicle)
|-
|5GA||United States (MPV)
|-
|KL4||South Korea (MPV)
|-
|LRB||China (SAIC-GM)
|-
|W04||Germany &amp; Poland
|-
|KLA||Alpheon||South Korea (2011-2015)
|-
|1G6||rowspan=10|Cadillac||United States
|-
|1GE||United States (incomplete vehicle)
|-
|1GY||United States (SUV)
|-
|2G6||Canada
|-
|2GE||Canada (incomplete vehicle)
|-
|3GY||Mexico (SUV)
|-
|LRE||China (SAIC-GM)
|-
|W06||Germany
|-
|XWF||Russia (made by Avtotor in Kaliningrad)
|-
|YSC||Sweden
|-
|1G8||rowspan=4|Saturn||United States
|-
|3GS||Mexico (SUV)
|-
|5GZ||United States (MPV/SUV)
|-
|W08||Belgium
|-
|1G0||rowspan=22|GMC||United States (bus 1981-1986)
|-
|1G5||United States (MPV 1981-1986)
|-
|1GD||United States (incomplete vehicle)
|-
|1GJ||United States (bus 1987-)
|-
|1GK||United States (MPV 1987-)
|-
|1GT||United States (truck)
|-
|2CK||Canada (1990-1991 Tracker made by CAMI - Canada only)
|-
|2CT||Canada (2010-2011 Terrain made by CAMI)
|-
|2G0||Canada (bus [van with more than 3 rows of seats] 1981-1986)
|-
|2G5||Canada (MPV 1981-1986)
|-
|2GD||Canada (incomplete vehicle)
|-
|2GH||Canada (transit bus)
|-
|2GJ||Canada (bus [van with more than 3 rows of seats] 1987-)
|-
|2GK||Canada (MPV 1987-)
|-
|2GT||Canada (truck)
|-
|3GK||Mexico (SUV)
|-
|3GT||Mexico (truck)
|-
|4KD||United States (W-Series incomplete vehicle made by GM - through 2009)
|-
|7GZ||United States (incomplete vehicle made by Navistar)
|-
|J8D||Japan (incomplete vehicle made by Isuzu - through 2009)
|-
|JGT||Japan (SUV made by Suzuki - Canada only)
|-
|KL6||South Korea (Middle East market Terrain '08-'10)
|-
|4GD||WhiteGMC||United States (1988-1989 Brigadier made by GM)
|-
|137||rowspan=6|Hummer||United States (H1 made by AM General)
|-
|5GN||United States (H3T)
|-
|5GR||United States (H2 made by AM General)
|-
|5GT||United States (H3)
|-
|ADM||South Africa (H3)
|-
|XWF||Russia (H2 &amp; H3 made by Avtotor in Kaliningrad)
|-
|4G5||General Motors||United States (EV1)
|-
|2G5||rowspan=2|BrightDrop||Canada (Truck 2023-2024)
|-
|5G5||United States (Truck made by Kuka AG - 2022 only)
|-
|5G2||rowspan=2|Cruise||United States (car) (Cruise AV)
|-
|5G3||United States (MPV) (Cruise Origin AV)
|-
|YS3||rowspan=4|Saab||Sweden 
|-
|JF4||Japan (9-2X made by Subaru)
|-
|3G0||Mexico (9-4X)
|-
|5S3||United States (9-7X)
|-
|W0L||rowspan=19|Opel/Vauxhall||Germany &amp; the rest of Europe (2017 and earlier)
|-
|W0V||Germany &amp; the rest of Europe (2018 and later) &amp; Opel Ampera-e Mid-2017 - 2019
|-
|W0L||when plant code is H: Thailand (Zafira A)
|-
|W0L||when plant code is 0: South Korea (Antara) or B: South Korea (Antara, Mokka A, Mokka X [A])
|-
|W0L||when plant code is C: South Korea (Opel Karl/Vauxhall Viva)
|-
|W0V||when plant code is B: South Korea (Mokka X [A]) or C: South Korea (Opel Karl/Vauxhall Viva)
|-
|SCC||UK (Opel Lotus Omega made by Lotus)
|-
|SED||UK (made by IBC Vehicles)
|-
|TW8||Portugal
|-
|VF1||France (Arena made by Renault)
|-
|VN1||France (Movano A made by Renault at SOVAB plant in Batilly, France)
|-
|VSX||Spain
|-
|XUF||Russia (Opel made by GM Russia - St. Petersburg plant)
|-
|XWF||Russia (Opel made by Avtotor in Kaliningrad)
|-
|1G0||United States (Opel GT, Opel/Vauxhall Ampera, Opel Ampera-e Early - Mid-2017)
|-
|4GD||United States (Sintra)
|-
|ADM||South Africa
|-
|JAA||Japan (Opel Campo made by Isuzu)
|-
|JAC||Japan (Monterey made by Isuzu)
|-
|SKA||rowspan=4|Vauxhall Motors||UK
|-
|SCC||UK (Vauxhall Lotus Carlton made by Lotus)
|-
|6G1||Australia (Vauxhall Monaro &amp; VXR8 made by Holden)
|-
|JAA||Japan (Vauxhall Brava made by Isuzu)
|-
|SKF||rowspan=2|Bedford Vehicles||UK
|-
|JAA||Japan (Bedford Brava made by Isuzu)
|-
|6G1||rowspan=18|Holden||Australia (2003-2017)
|-
|6H8||Australia (1989-2002)
|-
|JAA||Japan (Rodeo pickup [TF] made by Isuzu)
|-
|JAC||Japan (Jackaroo/Monterey made by Isuzu)
|-
|JSA||Japan (YG Cruze made by Suzuki)
|-
|KL3||South Korea
|-
|MMM||Thailand ('09-'11 Colorado pickup [RC] made by GM Thailand)
|-
|MMU||Thailand ('13-'20 Colorado pickup [RG], '13-'16 Colorado 7, '17-'20 Trailblazer made by GM Thailand)
|-
|MPA||Thailand ('04-'08 Rodeo pickup [RA] made by Isuzu Thailand)
|-
|SED||UK (1st gen. Frontera made by IBC Vehicles)
|-
|W0L||Germany &amp; the rest of Europe (2017 and earlier)
|-
|W0L||when plant code is H: Thailand (Zafira A)
|-
|W0V||Germany &amp; the rest of Europe (2018-2020)
|-
|1GH||United States (Acadia)
|-
|3G0||Mexico (Equinox)
|-
|3GM||Mexico (Suburban)
|-
|4S2||United States (2nd gen. Frontera made by [[w:Subaru Isuzu Automotive|SIA]])
|-
|5G8||United States (Volt)
|-
|1GG||rowspan=4|Isuzu||United States (Truck - Hombre &amp; i-Series made by GM)
|-
|4GT||United States (H-Series &amp; T-Series incomplete vehicle made by GM - through 2009)
|-
|4KL||United States (N-Series incomplete vehicle made by GM - through 2009)
|-
|4NU||United States (MPV/SUV - Ascender made by GM)
|-
|W0L||Subaru||Thailand [plant code H] (Traviq made by GM Thailand for export to Japan)
|-
|4G3||Toyota||United States (Cavalier made by GM for export to Japan)
|-
|3GP||Honda||Mexico (MPV/SUV: 2024-2026 Prologue made by GM)
|-
|4W5||Acura||United States (MPV/SUV: 2024 ZDX EV made by GM)
|}

{{BookCat}}</text>
      <sha1>fir4tk0amqp4k77dw3vedcxr79ks03p</sha1>
    </revision>
  </page>
  <page>
    <title>IIS and FastCGI</title>
    <ns>0</ns>
    <id>150430</id>
    <revision>
      <id>4656154</id>
      <parentid>3980599</parentid>
      <timestamp>2026-08-03T01:38:58Z</timestamp>
      <contributor>
        <username>Lbocquet</username>
        <id>3618782</id>
      </contributor>
      <origin>4656154</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1391" sha1="mppkhs73a34qoyw3y0rvp2qap7n58vn" xml:space="preserve">Internet Information Services 6.0 (herein IIS6) is Microsoft's web-server application, it runs only on Microsoft Windows 2003. FastCGI permits properly designed scripts to execute without the overhead of starting up the interpreter on each HTTP request. This wikibook functions to teach the user how to configure IIS6 with FastCGI.

IIS does some non-http serving stuff as well, it bundles in FTP, and SMTP server applications (which can be uninstalled or disabled) and it largely relies on Windows or WINS servers for authentication. As an alternative to IIS-as-a-webserver on Windows, one can migrate away from IIS, and [https://httpd.apache.org/docs/2.0/platform/windows.html install Apache 2.x]; or, the newer lighttpd 1.4x or greater. Both, of the above web-servers also run on *nix and are freely available under more liberal licenses.

== Table of Contents ==
{{Book search}}
{{Wikipedia|Internet Information Services|FastCGI}}
* Steps to getting it operational
*# [[/Obtaining FastCGI/]] {{stage|100%}}
*# [[/Registering interpreter/]] {{stage|100%}}
*# Language Specific Guides
*#* [[/Scripting languages/Perl/]] {{stage|100%}}
*#* [[/Scripting languages/Perl/Catalyst/]] {{stage|75%}}
* Appendix
** [[/Configuring/]] {{stage|00%}}
** [[/Trouble shooting/]] {{stage|100%}}
** [[/Package Components/]] {{stage|100%}}

{{alphabetical|I}}
{{Shelves|Scripting languages}}
{{status|25%}}</text>
      <sha1>mppkhs73a34qoyw3y0rvp2qap7n58vn</sha1>
    </revision>
  </page>
  <page>
    <title>Haskell/Monoids</title>
    <ns>0</ns>
    <id>181604</id>
    <revision>
      <id>4656136</id>
      <parentid>4655642</parentid>
      <timestamp>2026-08-02T23:03:51Z</timestamp>
      <contributor>
        <username>~2026-42694-70</username>
        <id>3618773</id>
      </contributor>
      <comment>Fix missing semicolon</comment>
      <origin>4656136</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="19664" sha1="hj9zk84wdveguud4d7xycw1m0xqq6hk" xml:space="preserve">{{Haskell minitoc|chapter=Advanced Haskell}}

In earlier parts of the book, we have made a few passing allusions to monoids and the &lt;code&gt;Monoid&lt;/code&gt; type class (most notably when discussing [[Haskell/MonadPlus#Relationship with monoids|MonadPlus]]). Here we'll give them a more detailed look and show what makes them useful.

== What is a monoid? ==

The operation of adding numbers has a handful of properties which are so elementary we don't even think about them when summing numbers up. One of them is ''associativity'': when adding three or more numbers it doesn't matter how we group the terms.

&lt;syntaxhighlight lang=&quot;haskell&quot;&gt;
GHCi&gt; (5 + 6) + 10
21
GHCi&gt; 5 + (6 + 10)
21
&lt;/syntaxhighlight&gt;

Another one is that it has an ''identity element'', which can be added to any other number without changing its value. That element is the number zero:

&lt;syntaxhighlight lang=&quot;haskell&quot;&gt;
GHCi&gt; 255 + 0
255
GHCi&gt; 0 + 255
255
&lt;/syntaxhighlight&gt;

Addition is not the only binary operation which is associative and has an identity element. Multiplication does too, albeit with a different identity.

&lt;syntaxhighlight lang=&quot;haskell&quot;&gt;
GHCi&gt; (5 * 6) * 10
300
GHCi&gt; 5 * (6 * 10)
300
GHCi&gt; 255 * 1
255
GHCi&gt; 1 * 255
255
&lt;/syntaxhighlight&gt;

We needn't restrict ourselves to arithmetic either. &lt;code&gt;(++)&lt;/code&gt;, the appending operation for Haskell lists, is another example. It has the empty list as its identity element.

&lt;syntaxhighlight lang=&quot;haskell&quot;&gt;
GHCi&gt; ([1,2,3] ++ [4,5,6]) ++ [7,8,9]
[1,2,3,4,5,6,7,8,9]
GHCi&gt; [1,2,3] ++ ([4,5,6] ++ [7,8,9])
[1,2,3,4,5,6,7,8,9]
GHCi&gt; [1,2,3] ++ []
[1,2,3]
GHCi&gt; [] ++ [1,2,3]
[1,2,3]
&lt;/syntaxhighlight&gt;

It turns out there are a great many associative binary operations with an identity. All of them, by definition, give us examples of ''monoids''. We say, for instance, that the integer numbers form a monoid under addition with &lt;code&gt;0&lt;/code&gt; as identity element.

== Semigroups ==

Before we can look into how Haskell implements monoids, we must first examine a closely related concept, semigroups. If we remove the requirement to have an identity element from a monoid and keep only the associative binary operation, we get a semigroup. Monoids are just semigroups with an identity element, but not all semigroups are monoids. Haskell defines a typeclass &lt;code&gt;Semigroup&lt;/code&gt; that represents them:

&lt;syntaxhighlight lang=&quot;haskell&quot;&gt;
class Semigroup a where
    (&lt;&gt;) :: a -&gt; a -&gt; a

    sconcat :: NonEmpty a -&gt; a
&lt;/syntaxhighlight&gt;

The first method, the operator &lt;code&gt;(&amp;lt;&amp;gt;)&lt;/code&gt; represents the binary operation that characterises a semigroup.

The second method, &lt;code&gt;sconcat&lt;/code&gt;, takes a ''non-empty'' list and reduces it using &lt;code&gt;(&amp;lt;&amp;gt;)&lt;/code&gt;. Recall that semigroups do not have an identity element we can use as a default, and so the list must not be empty. The &lt;code&gt;NonEmpty&lt;/code&gt; type is just a way of enforcing a non-empty list.

Both methods have default implementations in terms of each other, that is, it is sufficient to define a &lt;code&gt;Semigroup&lt;/code&gt; by providing at least one of the two methods of your choice. For clarity of illustration, though, we will only be defining &lt;code&gt;(&amp;lt;&amp;gt;)&lt;/code&gt; for the most part.

We previously alluded to the existence of semigroups that are not monoids (i.e. do not have an identity element). Most of the semigroups you will encounter in Haskell are also monoids, although there are exceptions. The &lt;code&gt;Min&lt;/code&gt; newtype from &lt;code&gt;Data.Semigroup&lt;/code&gt; is an example:

&lt;syntaxhighlight lang=&quot;haskell&quot;&gt;
newtype Min a = Min { getMin :: a }

instance (Ord a) =&gt; Semigroup (Min a) where
    (Min a) &lt;&gt; (Min b) = Min (min a b)
&lt;/syntaxhighlight&gt;

The &lt;code&gt;Min&lt;/code&gt; newtype wraps two instances of &lt;code&gt;Ord&lt;/code&gt; (elements that have an order, e.g. integers), and &lt;code&gt;(&amp;lt;&amp;gt;)&lt;/code&gt; results in the minimum of the two operands. We can confirm that this binary operation is associative:

&lt;syntaxhighlight lang=&quot;haskell&quot;&gt;
GHCi&gt; getMin $ (Min 1 &lt;&gt; Min 2) &lt;&gt; Min 3
1
GHCi&gt; getMin $ Min 1 &lt;&gt; (Min 2 &lt;&gt; Min 3)
1
&lt;/syntaxhighlight&gt;

There is no requirement for an identity element. If you add an extra requirement for &lt;code&gt;a&lt;/code&gt; to have a minimum value (via a constraint on &lt;code&gt;Bounded&lt;/code&gt;), &lt;code&gt;Min&lt;/code&gt; does provide an instance of the &lt;code&gt;Monoid&lt;/code&gt; typeclass, and this brings us into discussing &lt;code&gt;Monoid&lt;/code&gt; itself.

== The &lt;code&gt;Monoid&lt;/code&gt; class ==

Monoids show up very often in Haskell, and so it is not surprising to find there is a type class for them in the core libraries. Here it is:

&lt;syntaxhighlight lang=&quot;haskell&quot;&gt;
class Semigroup a =&gt; Monoid a where
    mempty  :: a

    mconcat :: [a] -&gt; a
    mconcat = foldr (&lt;&gt;) mempty
&lt;/syntaxhighlight&gt;

Unsurprisingly, &lt;code&gt;Semigroup&lt;/code&gt; is a superclass of &lt;code&gt;Monoid&lt;/code&gt;.

Note that we did not have to define the binary operation again, since it's already provided from the &lt;code&gt;Semigroup&lt;/code&gt; constraint. In older code, you may instead see a method with a name of &lt;code&gt;mappend :: a -&gt; a -&gt; a&lt;/code&gt;, but this is a historical artifact from when &lt;code&gt;Semigroup&lt;/code&gt; was not a superclass of &lt;code&gt;Monoid&lt;/code&gt; (analogous to the relation between &lt;code&gt;return&lt;/code&gt; and &lt;code&gt;pure&lt;/code&gt; in &lt;code&gt;Monad&lt;/code&gt; and &lt;code&gt;Applicative&lt;/code&gt;). Nowadays, &lt;code&gt;mappend&lt;/code&gt; has a default implementation in terms of &lt;code&gt;(&amp;lt;&amp;gt;)&lt;/code&gt; to ease the transition, and is slated for removal in a future release of the GHC. If you see a use of &lt;code&gt;mappend&lt;/code&gt;, mentally interchange it with &lt;code&gt;(&amp;lt;&amp;gt;)&lt;/code&gt;.

The method &lt;code&gt;mempty&lt;/code&gt; is the identity of the monoid. The second method, &lt;code&gt;mconcat&lt;/code&gt;, is provided as a bonus; it runs down a list and &lt;code&gt;(&amp;lt;&amp;gt;)&lt;/code&gt;s its elements together in order.

As an example, this is the monoid instance for lists:

&lt;syntaxhighlight lang=&quot;haskell&quot;&gt;
instance Semigroup [a] where
    (&lt;&gt;) = (++)

instance Monoid [a] where
    mempty  = []
&lt;/syntaxhighlight&gt;

Note that, in this case, &lt;code&gt;mconcat = foldr (++) []&lt;/code&gt; is equivalent to &lt;code&gt;concat&lt;/code&gt;, which explains the name of the method.

It is legitimate to think of monoids as types which support ''appending'' in some sense, though a dose of poetic licence is required. The &lt;code&gt;Monoid&lt;/code&gt; definition is extremely general and not at all limited to data structures, so &quot;appending&quot; will be just a metaphor at times.

As we suggested earlier on, numbers (i.e. instances of &lt;code&gt;Num&lt;/code&gt;) form monoids under both addition and multiplication. That leads to the awkward question of which one to choose when writing the instance. In situations like this one, in which there is no good reason to choose one possibility over the other, the dilemma is averted by creating one &lt;code&gt;newtype&lt;/code&gt; for each instance:

&lt;syntaxhighlight lang=&quot;haskell&quot;&gt;
-- | Monoid under addition.
newtype Sum a = Sum { getSum :: a }

-- | Monoid under multiplication.
newtype Product a = Product { getProduct :: a }

instance Num a =&gt; Semigroup (Sum a) where
    Sum x &lt;&gt; Sum y = Sum (x + y)

instance Num a =&gt; Monoid (Sum a) where
    mempty = Sum 0

instance Num a =&gt; Semigroup (Product a) where
    Product x &lt;&gt; Product y = Product (x * y)

instance Num a =&gt; Monoid (Product a) where
    mempty = Product 1

&lt;/syntaxhighlight&gt;

Here is a quick demonstration of &lt;code&gt;Sum&lt;/code&gt; and &lt;code&gt;Product&lt;/code&gt;:

&lt;syntaxhighlight lang=&quot;haskell&quot;&gt;
GHCi&gt; import Data.Monoid
GHCi&gt; Sum 5 &lt;&gt; Sum 6 &lt;&gt; Sum 10
Sum {getSum = 21}
GHCi&gt; mconcat [Sum 5, Sum 6, Sum 10]
Sum {getSum = 21}
GHCi&gt; getSum . mconcat . fmap Sum $ [5, 6, 10]
21
GHCi&gt; getProduct . mconcat . fmap Product $ [5, 6, 10]
300
&lt;/syntaxhighlight&gt;

=== &lt;code&gt;Monoid&lt;/code&gt; laws ===

The laws which all instances of &lt;code&gt;Monoid&lt;/code&gt; must follow simply state the properties we already know: &lt;code&gt;(&amp;lt;&amp;gt;)&lt;/code&gt; is associative and &lt;code&gt;mempty&lt;/code&gt; is its identity element.

&lt;syntaxhighlight lang=&quot;haskell&quot;&gt;
(x &lt;&gt; y) &lt;&gt; z = x &lt;&gt; (y &lt;&gt; z) -- associativity
mempty &lt;&gt; x = x               -- left identity
x &lt;&gt; mempty = x               -- right identity
&lt;/syntaxhighlight&gt;

{{Exercises|
# There are several possible monoid instances for &lt;code&gt;Bool&lt;/code&gt;. Write at least two of them using &lt;code&gt;newtype&lt;/code&gt;s, as in the &lt;code&gt;Sum&lt;/code&gt; and &lt;code&gt;Product&lt;/code&gt; examples. Be sure to verify the monoid laws hold for your instances &lt;ref&gt;You will later find that two of those instances are defined in &lt;code&gt;Data.Monoid&lt;/code&gt; already.&lt;/ref&gt;.&lt;!-- Suppressed for silliness 
# It is possible, though very unnatural, to define &lt;code&gt;mempty&lt;/code&gt; and &lt;code&gt;mappend&lt;/code&gt; in terms of &lt;code&gt;mconcat&lt;/code&gt;. Write the definition of this. Figure out whether or not your definition automatically fulfils the above laws.
# There is a third basic property of both addition and multiplication which is just as familiar as associativity or the existence of an identity element. However, we made no mention of it in the discussion above. What is it? Explain in a few words (perhaps with an example) why it is not relevant to the discussion above.--&gt;
}}

== Uses ==
&lt;!-- The beginning of this section might be too slow, depending on where this chapter will end up in the book.--&gt;
Which advantages are there in having a class with a pompous name for such a simple concept? As usual in such cases, the key gains are in two associated dimensions: recognisability and generality. Whenever, for instance, you see &lt;code&gt;(&amp;lt;&amp;gt;)&lt;/code&gt; being used you know that, however the specific instance was defined, the operation being done is associative and has an identity element. Moreover, you also know that if there is an instance of &lt;code&gt;Monoid&lt;/code&gt; for a type you can take advantage of functions written to deal with monoids in general. As a toy example of such a function, we might take this function that concatenates three lists..

&lt;syntaxhighlight lang=&quot;haskell&quot;&gt;
threeConcat :: [a] -&gt; [a] -&gt; [a] -&gt; [a]
threeConcat a b c = a ++ b ++ c
&lt;/syntaxhighlight&gt;

... and replace all &lt;code&gt;(++)&lt;/code&gt; with &lt;code&gt;(&amp;lt;&amp;gt;)&lt;/code&gt;...

&lt;syntaxhighlight lang=&quot;haskell&quot;&gt;
mthreeConcat :: Monoid m =&gt; m -&gt; m -&gt; m -&gt; m
mthreeConcat a b c = a &lt;&gt; b &lt;&gt; c
&lt;/syntaxhighlight&gt;

... thus making it work with any &lt;code&gt;Monoid&lt;/code&gt;. When used on other types the generalised function will behave in an analogous way to the original one, as specified by the monoid laws.

&lt;syntaxhighlight lang=&quot;haskell&quot;&gt;
GHCi&gt; mthreeConcat &quot;Hello&quot; &quot; &quot; &quot;world!&quot;
&quot;Hello world!&quot;
GHCi&gt; mthreeConcat (Sum 5) (Sum 6) (Sum 10)
Sum {getSum = 21}
&lt;/syntaxhighlight&gt;

Monoids are extremely common, and have many interesting practical applications.

; The &lt;code&gt;Writer&lt;/code&gt; monad : A computation of type &lt;code&gt;Writer w a&lt;/code&gt; computes a value of type &lt;code&gt;a&lt;/code&gt; while producing extra output of type &lt;code&gt;w&lt;/code&gt; which must be an instance of &lt;code&gt;Monoid&lt;/code&gt;, and the bind operator of the monad uses &lt;code&gt;(&amp;lt;&amp;gt;)&lt;/code&gt; to accumulate the extra output. A typical use case would be logging, in which each computation produces a log entry for later inspection. In the logging use case, that would mean all entries generated during a series of computations are automatically combined into a single log output.
&lt;!--TODO: Trim this entry once there actually is a Foldable chapter. --&gt;

; The &lt;code&gt;Foldable&lt;/code&gt; class : Monoids play an important role in generalising list-like folding to other data structures. We will study that in detail in the upcoming [[Haskell/Foldable|chapter about the &lt;code&gt;Foldable&lt;/code&gt; class]].

; Finger trees : Moving on from operations on data structures to data structure implementations, monoids can be used to implement ''finger trees'', an efficient and versatile data structure. Its implementation makes use of monoidal values as tags for the tree nodes; and different data structures (such as sequences, priority queues, and search trees) can be obtained simply by changing the involved &lt;code&gt;Monoid&lt;/code&gt; instance.&lt;ref&gt;[http://apfelmus.nfshost.com/articles/monoid-fingertree.html This blog post], based on a [http://www.soi.city.ac.uk/~ross/papers/FingerTree.html paper by Ralf Hinze and Ross Patterson], contains a brief and accessible explanation on how monoids are used in finger trees.&lt;/ref&gt;

; Options and settings: In a wholly different context, monoids can be a handy way of treating application options and settings. Two examples are Cabal, the Haskell packaging system (&quot;Package databases are monoids. Configuration files are monoids. Command line flags and sets of command line flags are monoids. Package build information is a monoid.&quot;) and [http://xmonad.org XMonad], a tiling window manager implemented in Haskell (&quot;xmonad configuration hooks are monoidal.&quot;) &lt;ref&gt;Sources of the quotes (Haskell Cafe mailing list): [http://www.haskell.org/pipermail/haskell-cafe/2009-January/053602.html], [http://www.haskell.org/pipermail/haskell-cafe/2009-January/053603.html].&lt;/ref&gt;. Below are snippets from a XMonad configuration file (which is just a Haskell program) showing the monoidal hooks in action &lt;ref&gt;The snippets were taken from [https://wiki.haskell.org/Xmonad/Config_archive/ivy-foster-xmonad.hs Ivy Foster's example config in the HaskellWiki] and XMonad's {{Haskell lib|p=xmonad|v=0.11|XMonad|ManageHook}} module as of version 0.11.&lt;/ref&gt;.

&lt;syntaxhighlight lang=&quot;haskell&quot;&gt;
-- A ManageHook is a rule, or a combination of rules, for
-- automatically handling specific kinds of windows. It
-- is applied on window creation.

myManageHook :: ManageHook
myManageHook = composeAll
    [ manageConkeror
    , manageDocs
    , manageEmacs
    , manageGimp
    , manageImages
    , manageTerm
    , manageTransient
    , manageVideo
    , manageWeb
    , myNSManageHook scratchpads
    ]

-- manageEmacs, for instance, makes a duplicate of an Emacs
-- window in workspace 3 and sets its opacity to 90%. It
-- looks like this:

-- liftX lifts a normal X action into a Query (as expected by --&gt;)
-- idHook ensures the proper return type
manageEmacs :: ManageHook
manageEmacs =
    className =? &quot;Emacs&quot;
    --&gt; (ask &gt;&gt;= doF . \w -&gt; (copyWindow w &quot;3:emacs&quot;))
    &lt;+&gt; (ask &gt;&gt;= \w -&gt; liftX (setOpacity w 0.9) &gt;&gt; idHook)

-- The hooks are used as fields of the XMonad configuration,
-- which is passed to the IO action that starts XMonad.

myConfig xmproc = defaultConfig
                  { -- Among other fields...
                  , manageHook         = myManageHook
                  } 

-- idHook, (&lt;+&gt;), composeAll and (--&gt;) are just user-friendly
-- synonyms for monoid operations, defined in the
-- XMonad.ManageHook module thusly:

-- | The identity hook that returns the WindowSet unchanged.
idHook :: Monoid m =&gt; m
idHook = mempty

-- | Infix 'mappend'. Compose two 'ManageHook' from right to left.
(&lt;+&gt;) :: Monoid m =&gt; m -&gt; m -&gt; m
(&lt;+&gt;) = mappend

-- | Compose the list of 'ManageHook's.
composeAll :: Monoid m =&gt; [m] -&gt; m
composeAll = mconcat

-- | @p --&gt; x@.  If @p@ returns 'True', execute the 'ManageHook'.
--
-- &gt; (--&gt;) :: Monoid m =&gt; Query Bool -&gt; Query m -&gt; Query m -- a simpler type
(--&gt;) :: (Monad m, Monoid a) =&gt; m Bool -&gt; m a -&gt; m a
p --&gt; f = p &gt;&gt;= \b -&gt; if b then f else return mempty
&lt;/syntaxhighlight&gt;

[[File:Monoids diagrams demo.svg|thumb|A simple &lt;code&gt;diagrams&lt;/code&gt; example. The code for it is:&lt;syntaxhighlight lang=&quot;haskell&quot;&gt;
mconcat  (fmap
  (circle . (/20)) [1..5])
&lt;&gt; triangle (sqrt 3 / 2)
  # lwL 0.01 # fc yellow 
&lt;&gt; circle 0.5 # lwL 0.02
  # fc deepskyblue
&lt;/syntaxhighlight&gt;]]
; &lt;code&gt;diagrams&lt;/code&gt;: The [http://projects.haskell.org/diagrams &lt;code&gt;diagrams&lt;/code&gt;] package provides a powerful library for generating vectorial images programatically. On a basic level, &lt;code&gt;(&amp;lt;&amp;gt;)&lt;/code&gt; appears often in code using &lt;code&gt;diagrams&lt;/code&gt; because squares, rectangles and other such graphic elements have &lt;code&gt;Monoid&lt;/code&gt; instances which are used to put them on the top of each other. On a deeper level, most operations with graphic elements are internally defined in terms of monoids, and the implementation takes full advantage of their mathematical properties.

== Homomorphisms ==

Given any two monoids &lt;code&gt;A&lt;/code&gt; and &lt;code&gt;B&lt;/code&gt;, a function &lt;code&gt;f :: A -&gt; B&lt;/code&gt; is a '''monoid homomorphism''' if it preserves the monoid structure, so that:

&lt;syntaxhighlight lang=&quot;haskell&quot;&gt;
f mempty          = mempty
f (x &lt;&gt; y) = f x &lt;&gt; f y
&lt;/syntaxhighlight&gt;

In words, &lt;code&gt;f&lt;/code&gt; takes &lt;code&gt;mempty :: A&lt;/code&gt; to &lt;code&gt;mempty :: B&lt;/code&gt;, and the result of &lt;code&gt;(&amp;lt;&amp;gt;)&lt;/code&gt; for &lt;code&gt;A&lt;/code&gt; to the result of &lt;code&gt;(&amp;lt;&amp;gt;)&lt;/code&gt; for &lt;code&gt;B&lt;/code&gt; (after using &lt;code&gt;f&lt;/code&gt; to turn the arguments to &lt;code&gt;(&amp;lt;&amp;gt;)&lt;/code&gt; into &lt;code&gt;B&lt;/code&gt; values).

As an example, &lt;code&gt;length&lt;/code&gt; is a monoid homomorphism between (&lt;code&gt;[a]&lt;/code&gt;,&lt;code&gt;++&lt;/code&gt;) and (&lt;code&gt;Int&lt;/code&gt;,&lt;code&gt;+&lt;/code&gt;):

&lt;syntaxhighlight lang=&quot;haskell&quot;&gt;
length []         = 0
length (xs ++ ys) = length xs + length ys
&lt;/syntaxhighlight&gt;

When attempting to determine if a given function is a homomorphism do not concern yourself with the actual implementation; although its definition clearly influences whether or not it is a homomorphism, a homomorphism is defined by a function's ability to preserve the operations of the two underlying structures involved in the mapping and is not directly tied to implementation details.

An interesting example &quot;in the wild&quot; of monoids and homomorphisms was identified by Chris Kuklewicz amidst the Google Protocol Buffers API documentation.&lt;ref&gt;[http://www.haskell.org/pipermail/haskell-cafe/2009-January/053709.html Source (Haskell Cafe)]&lt;/ref&gt; Based on the quotes provided in the referenced comment, we highlight that the property that (in C++):

&lt;syntaxhighlight lang=&quot;c++&quot;&gt;
MyMessage message;
message.ParseFromString(str1 + str2); 
&lt;/syntaxhighlight&gt;

... is equivalent to...

&lt;syntaxhighlight lang=&quot;c++&quot;&gt;
MyMessage message, message2;
message.ParseFromString(str1);
message2.ParseFromString(str2);
message.MergeFrom(message2); 
&lt;/syntaxhighlight&gt;

... means that &lt;code&gt;ParseFromString&lt;/code&gt; is a monoid homomorphism. In a hypothetical Haskell implementation, the following equations would hold:

&lt;syntaxhighlight lang=&quot;haskell&quot;&gt;
parse :: String -&gt; Message
-- these are just equations, not actual code.
parse []         = mempty
parse (xs ++ ys) = parse xs `mergeFrom` parse ys
&lt;/syntaxhighlight&gt;

(They wouldn't hold ''perfectly'', as parsing might fail, but roughly so.)

Recognising a homomorphism can lead to useful refactorings. For instance, if &lt;code&gt;mergeFrom&lt;/code&gt; turned out to be an expensive operation it might be advantageous in terms of performance to concatenate the strings before parsing them. &lt;code&gt;parse&lt;/code&gt; being a monoid homomorphism would then guarantee the same results would be obtained.

== Further reading ==

* Dan Piponi (Sigfpe) on monoids: [http://sigfpe.blogspot.com/2009/01/haskell-monoids-and-their-uses.html a blog post overview]; [http://www.haskell.org/pipermail/haskell-cafe/2009-January/053798.html a comment about intuition on associativity].

* [http://groups.google.com/group/bahaskell/browse_thread/thread/4cf0164263e0fd6b/42b621f5a4da6019 Many monoid related links]

* Additional comment on finger trees (Haskell Cafe): [http://www.haskell.org/pipermail/haskell-cafe/2009-January/053689.html FingerTrees].

* Additional comments on &lt;code&gt;Monoid&lt;/code&gt; usage in Cabal (Haskell Cafe): [http://www.haskell.org/pipermail/haskell-cafe/2009-January/053626.html]; [http://www.haskell.org/pipermail/haskell-cafe/2009-January/053721.html].

* On &lt;code&gt;diagrams&lt;/code&gt; and monoids: [http://dept.cs.williams.edu/~byorgey/publications.html ''Monoids: Theme and Variations (Functional Pearl)''], by Brent Yorgey.

{{Haskell/NotesSection}}

{{Haskell navigation|chapter=Advanced Haskell}}</text>
      <sha1>hj9zk84wdveguud4d7xycw1m0xqq6hk</sha1>
    </revision>
  </page>
  <page>
    <title>Aros/User/Applications</title>
    <ns>0</ns>
    <id>237399</id>
    <revision>
      <id>4656054</id>
      <parentid>4656037</parentid>
      <timestamp>2026-08-02T16:38:27Z</timestamp>
      <contributor>
        <username>Jeff1138</username>
        <id>301139</id>
      </contributor>
      <minor />
      <origin>4656054</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="235758" sha1="a9gp09vxdqw25pp8d3wwamj1evnrhhv" xml:space="preserve">
==Introduction==


[[#Graphical Image Editing Art]]
[[#Office Application]]
[[#Audio]]

[[#Misc Application]]
[[#Games &amp; Emulation]]

[[#Application Guides]]

[[#top|...to the top]]


[[#top|...to the top]]

Most apps can be opened on the Workbench (aka publicscreen pubscreen) which is the default display option but can offer a custom one set to your configurations (aka custom screen mode promotion). These custom ones tend to stack so the possible use of A-M/A-N method of switching between full screens and the ability to pull down screens as well 

If you are interested in creating or porting new software, see [http://en.wikibooks.org/wiki/Aros/Developer/Docs here]

{|  class=&quot;wikitable sortable&quot; 
|- 
!width:30%;|Internet Applications 
!width:10%;|AROS(x86)
!width:10%;|Commodore-Amiga OS 3.1 (68k)
!width:10%;|Hyperion OS4(PPC)
!width:10%;|MorphOS(PPC)
|-
|&lt;!--Sub Menu--&gt;Web Online Browser [], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=network/browser Odyssey 2.0], [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=1175&amp;highlight=odyssey&amp;rowstart=100 Odyssey 3.0], 
|&lt;!--Amiga OS--&gt;[https://aminet.net/comm/www Amelinium], [https://blog.alb42.de/programs/amifox/ amifox] with [https://github.com/alb42/wrp wrp server], IBrowse*, Voyager*, [https://github.com/amigazen/aweb3/ AWeb 3.6 src], [https://github.com/matjam/aweb AWeb Src], [http://aminet.net/package/comm/www/NetSurf-m68k-sources Netsurf], [], 
|&lt;!--AmigaOS4--&gt;[ Odyssey OWB], [ Timberwolf (Firefox port 2011)], [http://amigaworld.net/modules/newbb/viewtopic.php?forum=32&amp;topic_id=32847 OWB-mui], [http://strohmayer.org/owb/ OWB-Reaction], IBrowse*, [http://os4depot.net/index.php?function=showfile&amp;file=network/browser/aweb.lha AWeb], Voyager, [http://www.os4depot.net/index.php?function=browse&amp;cat=network/browser Netsurf], 
|&lt;!--MorphOS--&gt;Wayfarer, [http://fabportnawak.free.fr/owb/ Odyssey OWB], [ Netsurf], IBrowse*, AWeb, [], 
|-
|&lt;!--Sub Menu--&gt;YouTube, Dailymotion website downloading videos audio [https://github.com/yt-dlp/yt-dlp yt-dlp], [https://clipgrab.org/ clipgrab],  
|&lt;!--AROS--&gt;[], [https://blog.alb42.de/amitube/ Amitube], 
|&lt;!--Amiga OS--&gt;[https://blog.alb42.de/amitube/ Amitube], [ smtube], 
|&lt;!--AmigaOS4--&gt;[https://blog.alb42.de/amitube/ Amitube], getVideo, Tubexx, [https://github.com/walkero-gr/aiostreams aiostreams], 
|&lt;!--MorphOS--&gt;[ ytsearch], [https://blog.alb42.de/amitube/ Amitube], [http://morphos.lukysoft.cz/en/vypis.php?kat=5 getVideo], Tubexx 
|-
|&lt;!--Sub Menu--&gt;Old style E-mailing SMTP POP3 IMAP based 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=network/email SimpleMail], [http://sourceforge.net/projects/simplemail/files/ src], [https://github.com/jens-maus/yam YAM] 
|&lt;!--Amiga OS--&gt;[http://sourceforge.net/projects/simplemail/files/ SimpleMail], [https://github.com/jens-maus/yam YAM]
|&lt;!--AmigaOS4--&gt;SimpleMail, YAM, 
|&lt;!--MorphOS--&gt; SimpleMail, YAM
|-
|&lt;!--Sub Menu--&gt;IRC 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=network/chat WookieChat], [https://sourceforge.net/projects/wookiechat/ Wookiechat src], [http://archives.arosworld.org/index.php?function=browse&amp;cat=network/chat AiRcOS], Jabberwocky, 
|&lt;!--Amiga OS--&gt;Wookiechat, AmIRC 
|&lt;!--AmigaOS4--&gt;Wookiechat 
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=5 Wookiechat], [http://morphos.lukysoft.cz/en/vypis.php?kat=5 AmIRC], 
|-
|&lt;!--Sub Menu--&gt;Instant Messaging IM like [https://github.com/BlitterStudio/amidon Hollywood lang based Mastodon client], BlueSky AT protocol, Facebook(TM), Twitter X (TM), Bitlbee IRC Gateway and others 
|&lt;!--AROS--&gt;[https://github.com/kaffeine1/telegram-amiga telegram-amiga], [http://archives.arosworld.org/index.php?function=browse&amp;cat=network/chat jabberwocky], 
|&lt;!--Amiga OS--&gt;[http://amitwitter.sourceforge.net/ AmiTwitter], CLIMM, SabreMSN, jabberwocky, 
|&lt;!--AmigaOS4--&gt;[http://amitwitter.sourceforge.net/ AmiTwitter], SabreMSN,
|&lt;!--MorphOS--&gt;[http://amitwitter.sourceforge.net/ AmiTwitter], [http://morphos.lukysoft.cz/en/vypis.php?kat=5 PolyglotNG], SabreMSN,
|-
|&lt;!--Sub Menu--&gt;Torrents 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=network/p2p ArTorr], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;CTorrent, Transmission 
|&lt;!--MorphOS--&gt;MLDonkey, Beehive, [http://morphos.lukysoft.cz/en/vypis.php?kat=5 Transmission], CTorrent, 
|-
|&lt;!--Sub Menu--&gt;FTP 
|&lt;!--AROS--&gt;[https://github.com/BlitterStudio/dopus5 Dopus5 Magellan], MarranoFTP, 
|&lt;!--Amiga OS--&gt;[http://aminet.net/package/comm/tcp/AmiFTP AmiFTP], AmiTradeCenter, ncFTP, 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=5 Pftp], [http://aminet.net/package/comm/tcp/AmiFTP-1.935-OS4 AmiFTP], 
|-
|&lt;!--Sub Menu--&gt;WYSIWYG Web Site Editor
|&lt;!--AROS--&gt; 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Internet Radio Streaming Audio [http://www.gnu.org/software/gnump3d/ gnump3d], [http://www.icecast.org/ Icecast2] Server (Broadcast) and Client (Listen), [ mpd], [http://darkice.sourceforge.net/ DarkIce], [http://www.dyne.org/software/muse/ Muse], 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=audio/misc ], Mplayer (Icecast Client only), 
|&lt;!--Amiga OS--&gt;[https://github.com/sandlbn/TuneFinder TuneFinder C Src], [https://github.com/sandlbn/TuneFinderMUI TuneFinderMUI], [http://amigazeux.net/anr/ AmiNetRadio], [], [], 
|&lt;!--AmigaOS4--&gt;[http://www.tunenet.co.uk/ Tunenet], 
|&lt;!--MorphOS--&gt;Mplayer, AmiNetRadio, 
|-
|&lt;!--Sub Menu--&gt;VoIP (Voice over IP) with SIP Client (Session Initiation Protocol) or Asterisk IAX2 Clients Softphone (skype like) 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;AmiPhone with Speak Freely, 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Weather Forecast 
|&lt;!--AROS--&gt;[http://sourceforge.net/projects/zunetools/files/ WeatherBar], [http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/workbench AWeather], []
|&lt;!--Amiga OS--&gt;[http://amigazeux.net/wetter/ Wetter], [https://github.com/emartisoft/AmiWeatherForecasts AmiWeatherForecasts src], 
|&lt;!--AmigaOS4--&gt;[http://os4depot.net/?function=showfile&amp;file=utility/workbench/flipclock.lha FlipClock], 
|&lt;!--MorphOS--&gt;[http://amigazeux.net/wetter/ Wetter], 
|-
|&lt;!--Sub Menu--&gt;Street Road Maps Route Planning GPS Tracking  
|&lt;!--AROS--&gt;[https://blog.alb42.de/programs/muimapparium/ MuiMapparium] [https://build.alb42.de/ Build of MuiMapp versions], 
|&lt;!--Amiga OS--&gt;AmiAtlas*, UKRoutePlus*, [http://blog.alb42.de/ AmOSM], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;[http://blog.alb42.de/programs/mapparium/ Mapparium], 
|-
|&lt;!--Sub Menu--&gt;Clock and Date setting from the internet (either ntp or websites) [https://www.timeanddate.com/worldclock/ World Clock], [http://www.time.gov/ NIST], [], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=network/misc ntpsync],  
|&lt;!--Amiga OS--&gt;ntpsync 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Newsgroups
|&lt;!--AROS--&gt; 
|&lt;!--Amiga OS--&gt;[http://newscoaster.sourceforge.net/ Newscoaster], [https://github.com/jens-maus/newsrog NewsRog], [ WorldNews], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|}

&lt;nowiki&gt;*&lt;/nowiki&gt; Commercial product.


==Graphical Image Editing Art==
{|  class=&quot;wikitable sortable&quot; 
|- 
!width:30%;|Image Editing
!width:10%;|AROS(x86)
!width:10%;|Commodore-Amiga OS 3.1(68k)
!width:10%;|Hyperion OS4(PPC)
!width:10%;|MorphOS(PPC)
|-
|&lt;!--Sub Menu--&gt;Pixel Raster Artwork [https://github.com/LibreSprite/LibreSprite LibreSprite based on GPL aseprite], [https://github.com/abetusk/hsvhero hsvhero], [], 
|&lt;!--AROS--&gt;[https://sourceforge.net/projects/zunetools/files/ZunePaint/ ZunePaint], [http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/edit LunaPaint], [http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/edit GrafX2], [ LodePaint needs OpenGL], 
|&lt;!--Amiga OS--&gt;[http://www.amigaforever.com/classic/download.html PPaint], GrafX2, [https://github.com/grovdata/Amiga_Sources/blob/master/software.md DeluxePaint], [http://www.amiforce.de/perfectpaint/perfectpaint.php PerfectPaint], Zoetrope, Brilliance2*, 
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=graphics/edit LodePaint], GrafX2, 
|&lt;!--MorphOS--&gt;Sketch, Pixel*, GrafX2, [http://morphos.lukysoft.cz/en/vypis.php?kat=3 LunaPaint]
|-
|&lt;!--Sub Menu--&gt;Image viewing 
|&lt;!--AROS--&gt;[http://sourceforge.net/projects/zunetools/files/ ZuneView], [http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/viewer LookHere], [http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/viewer LoView], [http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/viewer PicShow] , [http://amigaworld.net/modules/newbb/viewtopic.php?mode=viewtopic&amp;topic_id=31400&amp;forum=32&amp;start=80&amp;viewmode=flat&amp;order=0#583458 Picture Album], 
|&lt;!--Amiga OS--&gt;PicShow, PicView, Photoalbum,
|&lt;!--AmigaOS4--&gt;WarpView, PicShow, flPhoto, Thumbs, [http://amigaworld.net/modules/newbb/viewtopic.php?mode=viewtopic&amp;topic_id=31400&amp;forum=32&amp;start=80&amp;viewmode=flat&amp;order=0#583458 Picture Album], 
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=3 ShowGirls], [http://amigaworld.net/modules/newbb/viewtopic.php?mode=viewtopic&amp;topic_id=31400&amp;forum=32&amp;start=80&amp;viewmode=flat&amp;order=0#583458 Picture Album]
|-
|&lt;!--Sub Menu--&gt;Photography retouching / Image Manipulation like Photoshop(tm)  
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/edit RNOEffects], [https://sourceforge.net/projects/zunetools/files/ ZunePaint], [http://sourceforge.net/projects/zunetools/files/ ZuneView], 
|&lt;!--Amiga OS--&gt;[ Tecsoft Video Paint aka TVPaint], Photogenics*, ArtEffect*, ImageFX*, XiPaint, fxPaint, ImageMasterRT, Opalpaint, 
|&lt;!--AmigaOS4--&gt;WarpView, flPhoto, [http://www.os4depot.net/index.php?function=browse&amp;cat=graphics/edit Photocrop]
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=3 ShowGirls], ImageFX*, 
|-
|&lt;!--Sub Menu--&gt;Manage RAW picture folder galleries like Darktable, RAWtherapy, etc 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Graphic Format Converter - ICC profile support sRGB, Adobe RGB, XYZ and linear RGB 
|&lt;!--AROS--&gt; 
|&lt;!--Amiga OS--&gt;GraphicsConverter, ImageStudio, [http://www.coplabs.org/artpro.html ArtPro]
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Thumbnail Generator [], 
|&lt;!--AROS--&gt;[http://sourceforge.net/projects/zunetools/files/ ZuneView], [http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/shell Thumbnail Generator]
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Icon Editor
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/iconedit Archives], [http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/workbench Icon Toolbox], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=graphics/iconedit IconEditor]
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;2D Pixel Art Animation 
|&lt;!--AROS--&gt;Lunapaint
|&lt;!--Amiga OS--&gt;PPaint, AnimatED, Scala*, GoldDisk MovieSetter*, Walt Disney's Animation Studio*, ProDAD*, [https://github.com/historicalsource/DeluxePaint DeluxePaint src], Brilliance
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=3 Titler] 
|-
|&lt;!--Sub Menu--&gt;2D SVG based MovieSetter type 
|&lt;!--AROS--&gt; 
|&lt;!--Amiga OS--&gt;MovieSetter*, Fantavision*
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Morphing 
|&lt;!--AROS--&gt;[ GLMorph]
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;2D Cad (qcad-&gt;LibreCAD, etc.) 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;Xcad, MaxonCAD
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;3D Cad like FreeCad, BRL-CAD, OpenSCAD, AvoCADo, etc. using dxf, obj (vertices), blend, 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;XCad3d*, DynaCADD*, Cycas, 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;3D Model Rendering of glft (json) gbl (png jpg), usdz (USD files with materials, textures, and animations), FBX Filmbox is a proprietary Autodesk format, 
|&lt;!--AROS--&gt;POV-Ray
|&lt;!--Amiga OS--&gt;[http://www.discreetfx.com./amigaproducts.html CINEMA 4D]*, POV-Ray, Lightwave3D*, Real3D*, Caligari24*, Reflections/Monzoom*, [https://github.com/privatosan/RayStorm Raystorm src], Tornado 3D
|&lt;!--AmigaOS4--&gt;Blender, POV-Ray, Yafray
|&lt;!--MorphOS--&gt;Blender, POV-Ray, Yafray
|-
|&lt;!--Sub Menu--&gt;3D Format Converter [], [], 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/?function=showfile&amp;file=graphics/convert/ 3doc.i386-aros], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=showfile&amp;file=graphics/convert/ivcon.lha IVCon]
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt; 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Screen grabbing display 
|&lt;!--AROS--&gt;[ Screengrabber], [http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/misc snapit], [http://archives.arosworld.org/index.php?function=browse&amp;cat=video/record screen recorder], []
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Grab graphics music from apps [https://github.com/Malvineous/ripper6 ripper6], [],
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt; 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|}

&lt;nowiki&gt;*&lt;/nowiki&gt; Commercial product.

[[#top|...to the top]]

==Office Application==
{|  class=&quot;wikitable sortable&quot; 
|- 
!width:30%;|Office
!width:10%;|AROS (x86)
!width:10%;|[http://en.wikipedia.org/wiki/Amiga_software Commodore-Amiga OS 3.1] (68k)
!width:10%;|[http://en.wikipedia.org/wiki/AmigaOS_4 Hyperion OS4] (PPC)
!width:10%;|[http://en.wikipedia.org/wiki/MorphOS MorphOS] (PPC)
|-
|&lt;!--Sub Menu--&gt;Word-processing 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=office/wordprocessing Cinnamon Writer], [https://finalwriter.godaddysites.com/ Final Writer 7*], [https://github.com/sodero/MUI-Vim/releases MUI-Vim], [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=1995&amp;rowstart=20&amp;pid=12668#post_12668 Slovo], [], 
|&lt;!--AmigaOS--&gt;[ Softwood FinalCopy II*], Haage AmigaWriter*, Digita WordWorth*, Softwood FinalWriter*, Micro-Systems Excellence 3*, Arnor Protext, Rashumon, [ InterWord], [ KindWords], [WordPerfect], [ New Horizons Flow], [ CygnusEd Pro], [ Micro-systems Scribble], 
|&lt;!--AmigaOS4--&gt;AbiWord, [ CinnamonWriter]
|&lt;!--MorphOS--&gt;[ Cinnamon Writer], [http://www.meta-morphos.org/viewtopic.php?topic=1246&amp;forum=53 scriba], [http://morphos.lukysoft.cz/en/index.php Papyrus Office], 
|-
|&lt;!--Sub Menu--&gt;Spreadsheets 
|&lt;!--AROS--&gt;[https://blog.alb42.de/programs/leu/ Leu], [https://archives.arosworld.org/index.php?function=browse&amp;cat=office/spreadsheet], 
|&lt;!--AmigaOS--&gt;[https://aminet.net/package/biz/spread/ignition-src Ignition Src 1.3], [MaxiPlan 500 Plus], [OXXI Plan/IT v2.0 Speadsheet], [ Superplan], [ Creative Developments TurboCalc], [ ProCalc], [ InterSpread], [Digita DGCalc], [ Gold Disk Advantage], [ Micro-systems Analyze!]
|&lt;!--AmigaOS4--&gt;Gnumeric, [https://ignition-amiga.sourceforge.net/ Ignition], 
|&lt;!--MorphOS--&gt;[ ignition], [http://morphos.lukysoft.cz/en/vypis.php Papyrus Office], 
|-
|&lt;!--Sub Menu--&gt;Presentations
|&lt;!--AROS--&gt;[http://www.hollywoood-mal.com/ Hollywood]*, 
|&lt;!--Amiga OS--&gt;[http://www.hollywoood-mal.com/ Hollywood]*, MediaPoint, PointRider, Scala*, 
|&lt;!--Amiga OS4--&gt;[http://www.hollywoood-mal.com/ Hollywood]*, PointRider 
|&lt;!--MorphOS--&gt;[http://www.hollywoood-mal.com/ Hollywood]*, PointRider
|-
|&lt;!--Sub Menu--&gt;Databases 
|&lt;!--AROS--&gt;[http://sdb.freeforums.org/ SDB], [http://archives.arosworld.org/index.php?function=browse&amp;cat=office/database BeeBase], 
|&lt;!--Amiga OS--&gt;Precision Superbase 4 Pro*, Arnor Prodata*, BeeBase, Datastore, FinalData*, AmigaBase, Fiasco, Twist2*, [Digita DGBase], [], 
|&lt;!--AmigaOS4--&gt;BeeBase, SQLite, 
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=6 BeeBase], 
|-
|&lt;!--Sub Menu--&gt;PDF Viewing and editing digital signatures 
|&lt;!--AROS--&gt;[http://sourceforge.net/projects/arospdf/ ArosPDF via splash], [https://github.com/wattoc/AROS-vpdf vpdf wip], 
|&lt;!--Amiga OS--&gt;APDF 
|&lt;!--AmigaOS4--&gt;AmiPDF 
|&lt;!--MorphOS--&gt;APDF, vPDF, 
|-
|&lt;!--Sub Menu--&gt;Printing 
|&lt;!--AROS--&gt;Postscript 3 laser printers and Ghostscript internal, [ GutenPrint], 
|&lt;!--Amiga OS--&gt;[http://www.irseesoft.de/tp_what.htm TurboPrint]* 
|&lt;!--AmigaOS4--&gt;(some native drivers), 
|&lt;!--MorphOS--&gt;early TurboPrint included, 
|-
|&lt;!--Sub Menu--&gt;Note Taking markdown support like Obsidian like, joplin, OneNote, EverNotes, xournalpp, etc 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Study and analyse, collect, organize, annotate, cite, and share
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;PIM Personal Information Manager - Day Diary Planner Calendar App 
|&lt;!--AROS--&gt;[ ], [ ], [ ], 
|&lt;!--Amiga OS--&gt;Digita Organiser*, On The Ball, Everyday Organiser, [ Contact Manager], 
|&lt;!--AmigaOS4--&gt;AOrganiser, 
|&lt;!--MorphOS--&gt;[http://polymere.free.fr/orga_en.html PolyOrga], 
|-
|&lt;!--Sub Menu--&gt;Accounting
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=office/misc ETB], LoanCalc, [ ], [ ], [ ], 
|[ Digita Home Accounts2], Accountant, Small Business Accounts, Account Master, [ Amigabok], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Project Management Research 
|&lt;!--AROS--&gt; 
|&lt;!--Amiga OS--&gt;SuperGantt, SuperPlan, 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;System Wide Search 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=utility/filetool Finder], [], [], 
|&lt;!--Amiga OS--&gt; 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;System Wide Dictionary - multilingual [http://sourceforge.net/projects/babiloo/ Babiloo], [http://code.google.com/p/stardict-3/ StarDict], 
|&lt;!--AROS--&gt;[ ],  
|&lt;!--AmigaOS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;System wide Thesaurus - multi lingual
|&lt;!--AROS--&gt;[ ], 
|Kuma K-Roget*, 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Sticky Desktop Notes (post it type) 
|&lt;!--AROS--&gt;[http://aminet.net/package/util/wb/amimemos.i386-aros AmiMemos], [https://aminet.net/package/util/wb/amimemos.src-aros AmiMemos Src], [], 
|&lt;!--Amiga OS--&gt;[http://aminet.net/package/util/wb/StickIt-2.00 StickIt v2], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;DTP Desktop Publishing 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/edit RNOPublisher], 
|&lt;!--Amiga OS--&gt;[http://pagestream.org/ Pagestream]*, Professional Pro Page*, Saxon Publisher, Pagesetter, PenPal, 
|&lt;!--AmigaOS4--&gt;[http://pagestream.org/ Pagestream]* 
|&lt;!--MorphOS--&gt;[http://pagestream.org/ Pagestream]* 
|-
|&lt;!--Sub Menu--&gt;Scanning 
|&lt;!--AROS--&gt;[ SCANdal], [], 
|&lt;!--Amiga OS--&gt;FxScan*, ScanQuix* 
|&lt;!--AmigaOS4--&gt;SCANdal (Sane)
|&lt;!--MorphOS--&gt;SCANdal
|-
|&lt;!--Sub Menu--&gt;OCR
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/convert gOCR] 
|&lt;!--AmigaOS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;[http://morphos-files.net/categories/office/text Tesseract] 
|-
|&lt;!--Sub Menu--&gt;Text Editing
|&lt;!--AROS--&gt;Jano Editor (already installed as Editor), [http://archives.arosworld.org/index.php?function=browse&amp;cat=development/edit EdiSyn], [http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/text/edit Annotate], [https://archives.arosworld.org/index.php?function=browse&amp;cat=development/edit Vim], [http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/text/edit FrexxEd] [https://github.com/vidarh/FrexxEd src], [ NoWinEd], 
|&lt;!--Amiga OS--&gt;[https://aminet.net/package/text/edit/TurboText20 TurboText20 ttx], Annotate, MicroGoldED/CubicIDE*, CygnusED*, Protext*, NoWinED, 
|&lt;!--AmigaOS4--&gt;Notepad, Annotate, CygnusED*, NoWinED, 
|&lt;!--MorphOS--&gt;MorphOS ED, NoWinED, GoldED/CubicIDE*, CygnusED*, Annotate, 
|-
|&lt;!--Sub Menu--&gt;Office Fonts [http://sourceforge.net/projects/fontforge/files/fontforge-source/ Font Designer] 
|&lt;!--AROS--&gt;[ ], [ ], 
|&lt;!--Amiga OS--&gt;TypeSmith*, SaxonScript (GetFont Adobe Type 1), 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Drawing Vector
|&lt;!--AROS--&gt;[http://sourceforge.net/projects/amifig/ ZuneFIG previously AmiFIG], [https://github.com/serk118/designworks-aros designworks aros 64bit]
|&lt;!--Amiga OS--&gt;Drawstudio*, ProVector*, ArtExpression*, Professional Draw*, AmiFIG, MetaView, [https://gitlab.com/amigasourcecodepreservation/designworks Design Works Src], [], 
|&lt;!--AmigaOS4--&gt;MindSpace, [http://www.os4depot.net/index.php?function=browse&amp;cat=graphics/edit amifig], 
|&lt;!--MorphOS--&gt;SteamDraw, [http://aminet.net/package/gfx/edit/amifig amiFIG], 
|-
|&lt;!--Sub Menu--&gt;video conferencing (jitsi) 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;source code hosting
|&lt;!--AROS--&gt;Gitlab, 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Remote Desktop (server)
|&lt;!--AROS--&gt;[http://sourceforge.net/projects/zunetools/files/VNC_Server ArosVNCServer], 
|&lt;!--Amiga OS--&gt;[http://s.guillard.free.fr/AmiVNC/AmiVNC.htm AmiVNC], [http://dspach.free.fr/amiga/avnc/index.html AVNC]
|&lt;!--AmigaOS4--&gt;[http://s.guillard.free.fr/AmiVNC/AmiVNC.htm AmiVNC] 
|MorphVNC, vncserver
|-
|&lt;!--Sub Menu--&gt;Remote Desktop (client) login and connect to another machine 
|&lt;!--AROS--&gt;[https://sourceforge.net/projects/zunetools/files/VNC_Client/ ArosVNC], [http://archives.arosworld.org/index.php?function=browse&amp;cat=network/misc rdesktop], 
|&lt;!--Amiga OS--&gt;[http://twinvnc.free.fr/index.php?menu=01&amp;lang=eng TwinVNC], [http://dspach.free.fr/amiga/vva/index.html VVA], [http://www.hd-zone.com/ RDesktop]
|&lt;!--AmigaOS4--&gt;[http://twinvnc.free.fr/index.php?menu=01&amp;lang=eng TwinVNC], [http://www.hd-zone.com/ RDesktop]
|[http://twinvnc.free.fr/index.php?menu=01&amp;lang=eng TwinVNC], [http://www.hd-zone.com/ RDesktop]
|-
|&lt;!--Sub Menu--&gt;notifications 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;Ranchero 
|&lt;!--AmigaOS4--&gt;Ringhio 
|&lt;!--MorphOS--&gt;MagicBeacon 
|-
|&lt;!--Sub Menu--&gt;Biometric facial logins and fingerprint security features 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt; 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt; 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|}

&lt;nowiki&gt;*&lt;/nowiki&gt; Commercial product.

[[#top|...to the top]]

==Audio==
{|  class=&quot;wikitable sortable&quot; 
|- 
!width:30%;|Audio
!width:10%;|AROS(x86)
!width:10%;|Commodore-Amiga OS 3.1(68k)
!width:10%;|Hyperion OS4(PPC)
!width:10%;|MorphOS(PPC)
|-
|&lt;!--Sub Menu--&gt;Playing playback Audio like MP3, [https://github.com/chrg127/gmplayer NSF], [https://github.com/kode54/lazyusf miniusf .usflib] [https://gitlab.com/kode54/psflib with pfslib], [], [], etc 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=video/play Mplayer], [ HarmonyPlayer hp], [http://www.a500.org/downloads/audio/index.xhtml playcdda] CDs, [ WildMidi Player], [https://bszili.morphos.me/ UADE mod player], [], [ RNOTunes], [ mp3Player], [], 
|&lt;!--Amiga OS--&gt;AmiNetRadio, AmigaAmp, playOGG, 
|&lt;!--AmigaOS4--&gt;TuneNet, SimplePlay, AmigaAmp, TKPlayer
|AmiNetRadio, Mplayer, Kaya, AmigaAmp
|-
|&lt;!--Sub Menu--&gt;Editing Audio 
|&lt;!--AROS--&gt;[ Audio Evolution 4] 
|&lt;!--Amiga OS--&gt;[ Samplitude Opus Key], [https://sourceforge.net/projects/hd-rec/ HD-Rec Src], [http://www.sonicpulse.de/eng/news.html SoundFX], 
|&lt;!--AmigaOS4--&gt;[https://sourceforge.net/projects/hd-rec/ HD-Rec], AmiSoundED, [http://os4depot.net/?function=showfile&amp;file=audio/record/audioevolution4.lha Audio Evolution 4] 
|[http://www.hd-rec.de/HD-Rec/index.php?site=home HD-Rec], 
|-
|&lt;!--Sub Menu--&gt;Editing Tracker Music
|&lt;!--AROS--&gt;[https://github.com/hitchhikr/protrekkr Protrekkr], [ Schism Tracker], [http://archives.arosworld.org/index.php?function=browse&amp;cat=audio/tracker MilkyTracker], [http://www.hivelytracker.com/ HivelyTracker], [ Radium in AROS already],  [http://www.a500.org/downloads/development/index.xhtml libMikMod], 
|&lt;!--Amiga OS--&gt;MilkyTracker, HivelyTracker, DigiBooster, Octamed SoundStudio, 
|&lt;!--AmigaOS4--&gt;MilkyTracker, HivelyTracker, GoatTracker
|MilkyTracker, GoatTracker, DigiBooster, 
|-
|&lt;!--Sub Menu--&gt;Editing Music [], [https://github.com/kmatheussen/camd CAMD] and/or staves and notes manuscript 
|&lt;!--AROS--&gt;[http://bnp.hansfaust.de/ Bars and Pipes for AROS], [ Audio Evolution], [], 
|&lt;!--Amiga OS--&gt;[http://bnp.hansfaust.de/ Bars'n'Pipes], MusicX* David &quot;Talin&quot; Joiner &amp; Craig Weeks (for Notator-X), Deluxe Music Construction 2*, [https://github.com/timoinutilis/midi-sequencer-amigaos Horny c Src], HD-Rec, [https://aminet.net/package/mus/midi/dominatorV1_51 Dominator], 
|&lt;!--AmigaOS4--&gt;[https://sourceforge.net/p/hd-rec/code/HEAD/tree/ HD-Rec Src], Rockbeat, [http://bnp.hansfaust.de/download.html Bars'n'Pipes], [http://os4depot.net/index.php?function=browse&amp;cat=audio/edit Horny], Audio Evolution 4, 
|&lt;!--MorphOS--&gt;Bars'n'Pipes, 
|-
|&lt;!--Sub Menu--&gt;Sound Sampling 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=audio/record Audio Evolution 4], [http://www.imica.net/SitePortalPage.aspx?siteid=1&amp;did=162 Quick Record], [https://archives.arosworld.org/index.php?function=browse&amp;cat=audio/misc SOX to get AIFF 16bit files], [https://github.com/aros-development-team/AROS/tree/master/workbench/tools/AHIRecord AHIRecord], 
|&lt;!--Amiga OS--&gt;[https://aminet.net/package/mus/edit/AudioEvolution3_src Audio Evolution 3 c src], [ Samplitude-MS Opus Key], Audiomaster IV*, 
|&lt;!--AmigaOS4--&gt;[https://github.com/timoinutilis/phonolith-amigaos phonolith c src], HD-Rec, Audio Evolution 4,
|&lt;!--MorphOS--&gt;[https://sourceforge.net/p/hd-rec/code/HEAD/tree/ HD-Rec Src], Audio Evolution 4,
|-
|&lt;!--Sub Menu--&gt;Live Looping or Audio Misc - Groovebox like
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;CD/DVD burn
|[https://code.google.com/p/amiga-fryingpan/ FryingPan], 
|&lt;!--Amiga OS--&gt;FryingPan, [http://www.estamos.de/makecd/#CurrentVersion MakeCD], 
|&lt;!--AmigaOS4--&gt;FryingPan, AmiDVD, 
|[http://www.amiga.org/forums/printthread.php?t=58736 FryingPan], Jalopeano, 
|-
|&lt;!--Sub Menu--&gt;CD/DVD audio rip
|Lame, [http://www.imica.net/SitePortalPage.aspx?siteid=1&amp;cfid=0&amp;did=167 Quick CDrip],
|&lt;!--Amiga OS--&gt;Lame,  
|&lt;!--AmigaOS4--&gt;Lame, 
|Lame,  
|-
|&lt;!--Sub Menu--&gt;MP3 v1 and v2 Tagger
|&lt;!--AROS--&gt;id3ren (v1), [http://archives.arosworld.org/index.php?function=browse&amp;cat=audio/edit mp3info], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|
|-
|&lt;!--Sub Menu--&gt;Audio Convert
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=audio/misc Sox], [], 
|&lt;!--Amiga OS--&gt;[http://aminet.net/package/mus/misc/SoundBox SoundBox], [http://aminet.net/package/mus/misc/SoundBoxKey SoundBox Key], [http://aminet.net/package/mus/edit/SampleE SampleE], sox 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;DJ mixing jamming 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Radio Automation Software [http://www.rivendellaudio.org/ Rivendell], [http://code.campware.org/projects/livesupport/report/3 Campware LiveSupport], [http://www.sourcefabric.org/en/airtime/ SourceFabric AirTime], [http://www.ohloh.net/p/mediabox404 MediaBox404], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Speakers Audio Sonos Mains AC networked wired controlled 
*2005 ZP100 with ZP80 
*2008 Zoneplayer ZP120 (multi-room wireless amp)  ZP90 receiver only with CR100 controller, 
*2009 ZonePlayer S5, 
*2010 BR100 wireless Bridge (no support),   
*2011 Play:3
*2013 Bridge (no support), Play:1,  
*2016 Arc,   Play:1,   
*Beam (Gen 2),   Playbar,  Ray,   Era 100,   Era 300,   Roam,   Move 2,   
*Sub (Gen 3),   Sub Mini,  Five,  Amp  S2 
|&lt;!--AROS--&gt;SonosController 
|&lt;!--Amiga OS--&gt;SonosController
|&lt;!--AmigaOS4--&gt;SonosController
|&lt;!--MorphOS--&gt;SonosController
|-
|&lt;!--Sub Menu--&gt;Smart Speakers 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt; 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|}

&lt;nowiki&gt;*&lt;/nowiki&gt; Commercial product.

[[#top|...to the top]]

==Video Creativity and Production==
{|  class=&quot;wikitable sortable&quot; 
|- 
!width:30%;|Video
!width:10%;|AROS(x86)
!width:10%;|Commodore-Amiga OS 3.1(68k)
!width:10%;|Hyperion OS4(PPC)
!width:10%;|MorphOS(PPC)
|-
|&lt;!--Sub Menu--&gt;Playing Video 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=video/play Mplayer VAMP], [http://www.a500.org/downloads/video/index.xhtml CDXL player], [http://www.a500.org/downloads/video/index.xhtml IffAnimPlay], [], 
|&lt;!--Amiga OS--&gt;Frogger*, AMP2, MPlayer, RiVA*, MooViD*, 
|&lt;!--AmigaOS4--&gt;DvPlayer, MPlayer 
|&lt;!--MorphOS--&gt;MPlayer, Frogger, AMP2, VLC 
|-
|&lt;!--Sub Menu--&gt;Streaming Video and game streaming like OBS studio, Parsec, [https://github.com/lizardbyte/sunshine sunshine], [https://github.com/moonlight-stream/moonlight-qt moonlight], etc 
|&lt;!--AROS--&gt;Mplayer, 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;Mplayer, Gnash, Tubexx 
|&lt;!--MorphOS--&gt;Mplayer, OWB, Tubexx
|-
|&lt;!--Sub Menu--&gt;Playing DVD 
|&lt;!--AROS--&gt;[http://a-mc.biz/ AMC]*, Mplayer 
|&lt;!--Amiga OS--&gt;AMP2, Frogger 
|&lt;!--AmigaOS4--&gt;[http://a-mc.biz/ AMC]*, DvPlayer*, AMP2,  
|&lt;!--MorphOS--&gt;Mplayer 
|-
|&lt;!--Sub Menu--&gt;Screen Recording
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=video/record Screenrecorder], [ ], [ ], [ ], [ ], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;Screenrecorder, 
|-
|&lt;!--Sub Menu--&gt;Create and Edit Individual Video NLE 
|&lt;!--AROS--&gt;[ Mencoder], [ Quick Videos], [http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/edit AVIbuild], [http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/misc FrameBuild], FFMPEG, 
|&lt;!--Amiga OS--&gt;[ MainConcept Mainactor Broadcast*], [http://en.wikipedia.org/wiki/Video_Toaster Video Toaster*], MacroSystem MovieShop 4.3*, proDAD Adorage*, [ IOSpirit VHI studio]*, [Gold Disk ShowMaker], [], 
|&lt;!--AmigaOS4--&gt;FFMpeg/GUI 
|&lt;!--MorphOS--&gt;Blender, Mencoder, FFmpeg
|-
|&lt;!--Sub Menu--&gt;Subtitle editor 
|&lt;!--AROS--&gt;[https://aminet.net/package/text/edit/Slarti_Arosx86ABIv0 Slarti_Arosx86ABIv0], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;IP-based video production workflows with High Dynamic Range (HDR), 10-bit color collaborative NDI, 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Blogging like Lemmy or kbin
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;VR face recognition for Vtubers 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;VR chatting Live2D models with Cubism type editor 
&lt;pre&gt;
Model data (cmo3)
Basic motions (can3)
Background image (png)
Set of files for embedding (runtime folder)
• Model data (moc3)
• Motion data (motion3.json)
• Model settings file (model3.json)
• Physics settings file (physics3.json)
• Display auxiliary file (cdi3.json)
&lt;/pre&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;VR chatting chatters .VRML models - standardized 3D file format for VR avatars 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;V-tubers V-tubing like Vseeface with Openseeface tracker or Vpuppr (virtual puppet project) for online live 2d / 3d art models rigging rigged LIV 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt; 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|}

&lt;nowiki&gt;*&lt;/nowiki&gt; Commercial product.

[[#top|...to the top]]


==Misc Application==
{|  class=&quot;wikitable sortable&quot; 
|- 
!width:30%;|Misc Application
!width:10%;|AROS(x86)
!width:10%;|Commodore-Amiga OS 3.1 (68k)
!width:10%;|Hyperion OS4(PPC)
!width:10%;|MorphOS(PPC)
|-
|&lt;!--Sub Menu--&gt;File Management 
|&lt;!--AROS--&gt;DOpus4, [https://github.com/BlitterStudio/dopus5 DOpus Magellan aka DOpus 5], [ Scalos], [ ], 
|&lt;!--Amiga OS--&gt;DOpus2, DOpus 4, [http://sourceforge.net/projects/dopus5allamigas/files/?source=navbar DOpus Magellan DOpus5], ClassAction, FileMaster, [http://www.amiga.org/forums/showthread.php?t=4897 DirWork 2]*, [https://github.com/RudolphRiedel/DiskMaster2 DiskMaster2 src], 
|&lt;!--AmigaOS4--&gt;DOpus4, DOpus5, Filer, AmiDisk 
|&lt;!--MorphOS--&gt;DOpus4, DOpus5 
|-
|&lt;!--Sub Menu--&gt;File Verification / Repair 
|&lt;!--AROS--&gt;md5 (works in linux compiling shell), [http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/filetool workpar2] (PAR2),  [http://zakalwe.fi/~shd/foss/cksfv/files/ compile cksfv from website], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;Par2, 
|-
|Application Installer 
|&lt;!--AROS--&gt;[], [ InstallerNG], 
|&lt;!--Amiga OS--&gt;InstallerNG, Grunch, 
|&lt;!--AmigaOS4--&gt;Jack
|&lt;!--MorphOS--&gt;Jack 
|-
|&lt;!--Sub Menu--&gt;Compression archiver [https://github.com/FS-make-simple/paq9a paq9a], [], 
|&lt;!--AROS--&gt;XAD system is a toolkit designed for handling various file and disk archiver
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;[https://aminet.net/package/util/pack/decrunchmania_os4 Crunchmania CrM2 depacker], 
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Binary Hexadecimal Editor 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=development/edit Zaphod], [],
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Repository
|&lt;!--AROS--&gt;[ Git]
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;Git
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Filesystem Partition Editor formatter Disk Management
|&lt;!--AROS--&gt;[https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=1440&amp;highlight=partition&amp;pid=8821#post_8821 QuickPart], [ HDToolBox]
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Filesystem Repair and backups 
|&lt;!--AROS--&gt;ArSFSDoctor, 
|&lt;!--Amiga OS--&gt;[https://aminet.net/package/disk/bakup/quarterback_src Quarterback Tools C and asm src], [ ], [ ], [ ], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;System Disk check, integrity and history [https://github.com/smartmontools/smartmontools smart tools], [], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;[], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Multiple File renaming
|&lt;!--AROS--&gt;DOpus 4 or 5, 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Anti Virus
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;VChecker, 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Random Wallpaper Desktop changer [ DOpus5], [ Scalos],  
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Alarm Clock, Timer, Stopwatch, Countdown 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/workbench DClock], [http://aminet.net/util/time/AlarmClockAROS.lha AlarmClock], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Fortune Cookie Quotes Sayings 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/misc AFortune], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;C/C++ IDE 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/text/edit FrexxEd], [https://github.com/vidarh/FrexxEd FrexxEd src], Annotate, Murks, 
|&lt;!--Amiga OS--&gt;[http://devplex.awardspace.biz/cubic/index.html Cubic IDE]*, Annotate, 
|&lt;!--AmigaOS4--&gt;CodeBench , [https://gitlab.com/boemann/codecraft CodeCraft], 
|&lt;!--MorphOS--&gt;[http://devplex.awardspace.biz/cubic/index.html Cubic IDE]*, Anontate, 
|-
|&lt;!--Sub Menu--&gt;Computer Languages Translation [https://tetracorp.github.io/guide/reverse-engineering-amiga.html ], [https://amigasourcecodepreservation.gitlab.io/amiga-assembler-insider-guide/ ], [https://github.com/kermitfrog/Amiga-Re-Engineering Rust, Ghidra and FS-UAE], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;[https://bitbucket.org/rhinoid/convert68000toc/src/main/ convert m68k seka asm-one to c], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Gui Creators
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=development/guitool MuiBuilder], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;[ MuiBuilder],  
|-
|&lt;!--Sub Menu--&gt;Catalog .cd .ct Editors 
|&lt;!--AROS--&gt;FlexCat
|&lt;!--Amiga OS--&gt;[http://www.geit.de/deu_simplecat.html SimpleCat], FlexCat
|&lt;!--AmigaOS4--&gt;[http://aminet.net/package/dev/misc/simplecat SimpleCat], FlexCat
|[http://www.geit.de/deu_simplecat.html SimpleCat], FlexCat
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|}

&lt;nowiki&gt;*&lt;/nowiki&gt; Commercial product.


==Misc Application 2==
{|  class=&quot;wikitable sortable&quot; 
|- 
!width:30%;|Misc Application
!width:10%;|AROS(x86)
!width:10%;|Commodore-Amiga OS 3.1(68k)
!width:10%;|Hyperion OS4(PPC)
!width:10%;|MorphOS(PPC)
|-
|&lt;!--Sub Menu--&gt;System 
|&lt;!--AROS--&gt;[ SysExplorer], [ SysMon], [ Scout], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;OSK On Screen Keyboard
|&lt;!--AROS--&gt;[], 
|&lt;!--Amiga OS--&gt;[https://aminet.net/util/wb/OSK.lha OSK]
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Screen Magnifier Magnifying Glass Magnification 
|&lt;!--AROS--&gt;[http://www.onyxsoft.se/files/zoomit.lha ZoomIT], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Comic Book CBR CBZ format reader viewer 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/viewer comics], [http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/viewer comicon], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Ebook Reader 
|&lt;!--AROS--&gt;[https://blog.alb42.de/programs/#legadon Legadon EPUB],[]
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Ebook Converter 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Text to Speech tts [https://github.com/JonathanFly/bark-installer Bark], [], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=audio/misc flite], 
|&lt;!--Amiga OS--&gt;[http://www.text2speech.com translator], 
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=search&amp;tool=simple FLite]
|&lt;!--MorphOS--&gt;[http://se.aminet.net/pub/aminet/mus/misc/ FLite]
|-
|&lt;!--Sub Menu--&gt;Speech Voice Recognition Dictation - [http://sourceforge.net/projects/cmusphinx/files/ CMU Sphinx], [http://julius.sourceforge.jp/en_index.php?q=en/index.html Julius], [http://www.isip.piconepress.com/projects/speech/index.html ISIP], 
|&lt;!--AROS--&gt; 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Speech Voice Changer [], [], [], [], 
|&lt;!--AROS--&gt; 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Screen Display Blanker screensaver 
|&lt;!--AROS--&gt;Blanker Commodity (built in), [https://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/screenblanker GarshneBlanker], [http://sourceforge.net/projects/gblanker/ GBlanker Src], [], 
|&lt;!--Amiga OS--&gt;MultiCX, 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;ModernArt Blanker, 
|-
|}


==Misc Application 3==
{|  class=&quot;wikitable sortable&quot; 
|- 
!width:30%;|Misc Application
!width:10%;|AROS(x86)
!width:10%;|Commodore-Amiga OS 3.1(68k)
!width:10%;|Hyperion OS4(PPC)
!width:10%;|MorphOS(PPC)
|-
|&lt;!--Sub Menu--&gt;Fractals mandelbrot, etc 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/misc ], 
|&lt;!--Amiga OS--&gt;ZoneXplorer, 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Landscape Rendering 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/raytrace WCS World Construction Set], 
|&lt;!--Amiga OS--&gt;[ Vista Pro], [http://en.wikipedia.org/wiki/World_Construction_Set World Construction Set]
|&lt;!--AmigaOS4--&gt;[ WCS World Construction Set],
|&lt;!--MorphOS--&gt;[ WCS World Construction Set],
|-
|&lt;!--Sub Menu--&gt;Astronomy [https://sourceforge.net/projects/skychart/ skychart freepascal], [], [], 
|&lt;!--AROS--&gt;[ Digital Almanac (ABIv0 only)], 
|&lt;!--Amiga OS--&gt;[http://aminet.net/search?query=planetarium Aminet search], [http://aminet.net/misc/sci/DA3V56ISO.zip Digital Almanac], [https://aminet.net/package/misc/sci/da3sourceV58 Src c V58], [ Galileo renamed to Distant Suns]*, [], 
|&lt;!--AmigaOS4--&gt;[http://sourceforge.net/projects/digital-almanac/ Digital Almanac], Distant Suns*, [http://www.digitaluniverse.org.uk/ Digital Universe]*,
|&lt;!--MorphOS--&gt;[http://www.aminet.net/misc/sci/da3.lha Digital Almanac], [http://www.aminet.net/package/misc/sci/da3-mos-src Src c V56], 
|-
|&lt;!--Sub Menu--&gt;Astrology [https://sourceforge.net/projects/skylendar/ skylendar], [https://github.com/CruiserOne/Astrolog Astrolog], [https://www.astrolog.org/astrolog/astfile.htm Astrology alt site], [https://saravali.github.io/download.html Maitreya], [https://github.com/alamahant/Asteria Asteria], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;PCB design
|&lt;!--AROS--&gt; 
|&lt;!--Amiga OS--&gt;[ ], [ ], [ ], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Digital Signage
|&lt;!--AROS--&gt;Hollywood, Hollywood Designer 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Genealogy History Family Tree Ancestry Records (FreeBMD, FreeREG, and FreeCEN file formats or GEDCOM GenTree)
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt; [ Origins], [ Your Family Tree], [ ], [ ], [ ], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Languages 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;Fun School, 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Mathematics ([http://www-fourier.ujf-grenoble.fr/~parisse/install_en.html Xcas], etc.), 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/scientific mathX] 
|&lt;!--Amiga OS--&gt;Maple V, mathX, Fun School, GCSE Maths, [ ], [ ], [ ], 
|&lt;!--AmigaOS4--&gt;Yacas 
|&lt;!--MorphOS--&gt;Yacas 
|-
|&lt;!--Sub Menu--&gt;Maths Graph Function Plotting
|&lt;!--AROS--&gt;[https://blog.alb42.de/programs/#MUIPlot MUIPlot], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;App Utility Launcher Dock toolbar  
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/docky BoingBar], [], 
|&lt;!--Amiga OS--&gt;[https://github.com/adkennan/DockBot Dockbot],
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;3D Printer [https://github.com/OrcaSlicer/OrcaSlicer OrcaSlicer]
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;BASIC Computer Language 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=development/language Basic4SDL], [ Ace Basic], [ X-AMOS], [SDLBasic], [ Alvyn], 
|&lt;!--Amiga OS--&gt;[http://www.amiforce.de/main.php Amiblitz 3], [http://amos.condor.serverpro3.com/AmosProManual/contents/c1.html Amos Pro], [http://aminet.net/package/dev/basic/ace24dist ACE Basic], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;sdlBasic
|-
|&lt;!--Sub Menu--&gt;HAM radio, amateur radio, packet radio  [], [], [], [https://cemaxecuter.com/ Dragon OS], [https://github.com/km4ack/73Linux with 73 link update], [https://www.youtube.com/watch?v=YAL5KNePRSg video for], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;[https://www.amigarealm.com/amiga/amicomms/comm4.htm Comm4], [https://www.amigarealm.com/archives/comms/aarug/ TNC Terminal Node Controller with packets over serial connections on Yaesu or Woxum handheld], [https://aminet.net/comm/misc AmiCom], [ with 7Plus file encoder/decoder], [ mksstv], [ RTTYam], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|}

&lt;nowiki&gt;*&lt;/nowiki&gt; Commercial product.


==Games &amp; Emulation==

Some emulators/games require OpenGL to function and to adjust ahi prefs channels, frequency and unit0 and unit1 and 
[http://aros.sourceforge.net/documentation/users/shell/changetaskpri.php changetaskpri -1]

Rom patching  https://www.marcrobledo.com/RomPatcher.js/ https://www.romhacking.net/patch/ (ips, ups, bps, etc) and this other site supports the latter formats https://hack64.net/tools/patcher.php 

Free public domain roms for use with emulators can be found [http://www.pdroms.de/ here] as most of the rest are covered by copyright rules. If you like to read about old games see [http://retrogamingtimes.com/ here] and [http://www.armchairarcade.com/neo/ here] and a [http://www.vintagecomputing.com/ blog] about old computers. Possibly some of the [http://www.answers.com/topic/list-of-best-selling-computer-and-video-games best selling] of all time. [http://en.wikipedia.org/wiki/List_of_computer_system_emulators Wiki] with emulated systems list.

[https://archive.gamehistory.org/ Archive of VGHF], [https://library.gamehistory.org/ Video Game History Foundation Library search]


{|  class=&quot;wikitable sortable&quot; 
|- 
!width:10%;|Games [http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer Emulation]
!width:10%;|AROS(x86)
!width:10%;|AmigaOS3(68k)
!width:10%;|AmigaOS4(PPC)
!width:10%;|MorphOS(PPC)
|-
|&lt;!--Sub Menu--&gt;Games Emulation Amstrad CPC 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer], [ Caprice32 (OpenGL &amp; pure SDL)], [ Arnold], [https://retroshowcase.gr/cpcbox-master/], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;[http://os4depot.net/index.php?function=browse&amp;cat=emulation/computer]
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=2], 
|-
|&lt;!--Sub Menu--&gt;Games Emulation Apple2 and 2GS
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Arcade 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/gamesystem Mame], [ SI Emu (ABIv0 only)], 
|&lt;!--Amiga OS--&gt;Mame, 
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/gamesystem xmame], amiarcadia, 
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=2 Mame], 
|-
|&lt;!--Sub Menu--&gt;Games Emulation Atari 2600 [], [], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/gamesystem Stella], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Atari 5200 [https://github.com/wavemotion-dave/A5200DS A5200DS], [], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Atari 7800
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Atari 400 800 130XL [https://github.com/wavemotion-dave/A8DS A8DS], [], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer Atari800], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Atari Lynx
|&lt;!--AROS--&gt;[http://myfreefilehosting.com/f/6366e11bdf_1.93MB Handy (ABIv0 only)], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Atari Jaguar
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Bandai Wonderswan 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation BBC Micro and Acorn Electron [http://beehttps://bem-unix.bbcmicro.com/download.html BeebEm], [http://b-em.bbcmicro.com/ B-Em], [http://elkulator.acornelectron.co.uk/ Elkulator], [http://electrem.emuunlim.com/ ElectrEm], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Dragon 32 and Tandy CoCo [http://www.6809.org.uk/xroar/ xroar], [], 
|&lt;!--AROS--&gt;[], [], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Commodore C16 Plus4
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Commodore C64
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer Vice (ABIv0 only)], [], 
|&lt;!--Amiga OS--&gt;Frodo, 
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/gamesystem viceplus], 
|&lt;!--MorphOS--&gt;Vice, 
|-
|&lt;!--Sub Menu--&gt;Games Emulation Commodore Amiga
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer Janus UAE], Emumiga, 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;[http://os4depot.net/index.php?function=browse&amp;cat=emulation/computer UAE], 
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=2 UAE], 
|-
|&lt;!--Sub Menu--&gt;Games Emulation Japanese MSX MSX2 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Mattel Intelivision
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Mattel Colecovision and Adam
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Milton Bradley (MB) Vectrex [ Vectrex OpenGL], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation PICO8 Pico-8 fantasy video game console [https://github.com/egordorichev/pemsa-sdl/ pemsa-sdl], [https://github.com/jtothebell/fake-08 fake-08], [https://github.com/Epicpkmn11/fake-08/tree/wip fake-08 fork], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Nintendo Gameboy
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/gamesystem vba no sound], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/gamesystem vba]
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Nintendo NES
|&lt;!--AROS--&gt;[ EmiNES], [http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/gamesystem Fceu], [https://github.com/takahirox/nes-js?tab=readme-ov-file nes-js], [https://github.com/bfirsh/jsnes jsnes], [https://github.com/angelo-wf/NesJs NesJs], 
|&lt;!--Amiga OS--&gt;AmiNES, [http://www.dridus.com/~nyef/darcnes/ darcNES], 
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/gamesystem amines]
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Nintendo SNES
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/gamesystem Zsnes], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/gamesystem warpsnes]
|&lt;!--MorphOS--&gt;[http://fabportnawak.free.fr/snes/ Snes9x], 
|-
|&lt;!--Sub Menu--&gt;Games Emulation Nintendo N64 
*HLE and plugins [ mupen64], [https://github.com/ares-emulator/ares ares], [https://github.com/N64Recomp/N64Recomp N64Recomp], [https://github.com/rt64/rt64 rt64], [https://github.com/simple64/simple64 Simple64], 
*LLE [], 
|&lt;!--AROS--&gt;[http://code.google.com/p/mupen64plus/ Mupen64+],
|&lt;!--Amiga OS--&gt;[http://code.google.com/p/mupen64plus/ Mupen64+], [http://aminet.net/package/misc/emu/tr-981125_src TR64], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;[ Nintendo Gamecube Wii]
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;[ Nintendo Wii U]
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;[https://github.com/yuzu-emu Nintendo Switch]
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation NEC PC Engine 
|&lt;!--AROS--&gt;[], [], [https://github.com/yhzmr442/jspce js-pce], 
|[http://www.hugo.fr.fm/ Hugo], [http://mednafen.sourceforge.net/ Mednafen], 
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/gamesystem tgemu]
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Sega Master System (SMS)
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/gamesystem Dega], [http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/gamesystem sms], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/gamesystem osmose]
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Sega Genesis/Megadrive
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/gamesystem gp no sound], [http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/gamesystem DGen], 
|&lt;!--Amiga OS--&gt;[http://code.google.com/p/genplus-gx/ Genplus], 
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/gamesystem genesisplus]
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Sega Saturn 
*HLE [https://mednafen.github.io/ mednafen], [http://yabause.org/ yabause], [], 
*LLE [], [], 
|&lt;!--AROS--&gt;?
|&lt;!--Amiga OS--&gt;[http://yabause.org/ Yabause], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Sega Dreamcast 
*HLE [https://github.com/flyinghead/flycast  flycast], [https://code.google.com/archive/p/nulldc/downloads NullDC], 
*LLE [], [], 
|&lt;!--AROS--&gt;?
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Sinclair ZX80 and ZX81 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer], [], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Sinclair Spectrum 
|[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer Fuse (crackly sound)], [http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer SimCoupe], [ FBZX slow], [https://jsspeccy.zxdemo.org/ jsspeccy], [http://torinak.com/qaop/games qaop], 
|&lt;!--Amiga OS--&gt;[http://www.lasernet.plus.com/ Asp], [http://www.zophar.net/sinclair.html Speculator], [http://www.worldofspectrum.org/x128/index.html X128], 
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/computer]
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Sinclair QL
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer], [], 
|&lt;!--Amiga OS--&gt;[http://aminet.net/package/misc/emu/QDOS4amiga1 QDOS4amiga]
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation SNK NeoGeo Pocket
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/gamesystem], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/gamesystem gngeo], NeoPop, 
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Sony PlayStation
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/gamesystem FPSE], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/gamesystem FPSE]
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;[ Sony PS2]
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;[ Sony PS3]
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;[https://vita3k.org/ Sony Vita]
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;[https://github.com/shadps4-emu/shadPS4 PS4]
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation [http://en.wikipedia.org/wiki/Tangerine_Computer_Systems Tangerine] Oric and Atmos 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer Oricutron]
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/gamesystem Oricutron]
|&lt;!--MorphOS--&gt;[http://aminet.net/package/misc/emu/oricutron Oricutron]
|-
|&lt;!--Sub Menu--&gt;Games Emulation TI 99/4 99/4A [https://github.com/wavemotion-dave/DS994a DS994a], [], [https://js99er.net/#/ js99er], [], [http://aminet.net/package/misc/emu/TI4Amiga TI4Amiga], [http://aminet.net/package/misc/emu/TI4Amiga_src TI4Amiga src in c], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation HP 38G 40GS 48 49G/50G Graphing Calculators
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation TI 58 83 84 85 86 - 89 92 Graphing Calculators
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|}

{|  class=&quot;wikitable sortable&quot; 
|- 
!width:10%;|Games [https://www.rockpapershotgun.com/ General]
!width:10%;|AROS(x86)
!width:10%;|AmigaOS3(68k)
!width:10%;|AmigaOS4(PPC)
!width:10%;|MorphOS(PPC)
|- style=&quot;background:lightgrey; text-align:center; font-weight:bold;&quot;
| Games [https://www.trackawesomelist.com/michelpereira/awesome-open-source-games/ Open Source and others] || AROS || Amiga OS || Amiga OS4 || Morphos 
|-
|&lt;!--Sub Menu--&gt;Games Action like [https://github.com/opentomb/OpenTomb opentomb], [https://github.com/LostArtefacts/TRX TRX formerly Tomb1Main], [https://github.com/TombEngine TombEngine], [http://archives.arosworld.org/index.php?function=browse&amp;cat=game/action Thrust], [https://github.com/fragglet/sdl-sopwith sdl sopwith], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=game/action], [https://archives.arosworld.org/index.php?function=browse&amp;cat=game/action BOH], [], 
|&lt;!--Amiga OS--&gt;[https://github.com/BSzili/OpenLara/tree/amiga/src source of openlara SDL2], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Adventure like [http://dotg.sourceforge.net/ DMJ], [https://github.com/kromenak/gengine Gabriel Knight 3], [http://www.sarien.net/ Sierra Sarien], [https://github.com/klembot/twinejs twine js], [https://github.com/QSPFoundation/qspgui Quest Soft Player QSP], [], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=game/adventure dmagnetic], [https://archives.arosworld.org/?function=browse&amp;cat=emulation/misc ScummVM], [https://archives.arosworld.org/index.php?function=browse&amp;cat=game/roleplaying frotz infocom], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Board like [https://github.com/aperture-software/colditz-escape escape from colditz], [], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=game/board], [http://amigan.1emu.net/releases Africa]
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Cards 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=game/card ], [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=1443&amp;rowstart=180&amp;pid=12934#post_12934 Balatro], 
|&lt;!--AmigaOS--&gt;[http://home.arcor.de/amigasolitaire/e/welcome.html Reko], [https://github.com/samskivert/beschei-en beschei Src], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Misc [https://github.com/michelpereira/awesome-open-source-games Awesome open], [https://github.com/bobeff/open-source-games General Open Source], [https://github.com/SAT-R/sa2 Sonic Advance 2], [https://github.com/velorek1/cwordle Wordle type], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=game/misc], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games FPS like [https://aminet.net/package/game/shoot/D1X_Rebirth_AGA Descent D1X src], [https://github.com/DescentDevelopers/Descent3 Descent 3], [https://github.com/Fewnity/Counter-Strike-Nintendo-DS Counter-Strike-Nintendo-DS], [https://github.com/Aleph-One-Marathon/alephone Bungie Marathon 1994], [https://zdoom.org/downloads UzDoom opengl 3.3], [https://github.com/ZDoom/gzdoom gzdoom opengl 3+], [https://zdoom.org/downloads LZDoom opengl 2.1], 
|&lt;!--AROS--&gt;Doom, Quake, [http://archives.arosworld.org/index.php?function=browse&amp;cat=game/fps Quake 3 Arena (OpenGL)], [http://archives.arosworld.org/index.php?function=browse&amp;cat=game/fps Cube (OpenGL)], [http://archives.arosworld.org/index.php?function=browse&amp;cat=game/fps Assault Cube (OpenGL)], [http://archives.arosworld.org/index.php?function=browse&amp;cat=game/fps Cube 2 Sauerbraten (OpenGL)], [http://fodquake.net/test/ FodQuake QuakeWorld], [https://archives.arosworld.org/index.php?function=browse&amp;cat=game/fps Duke Nukem 3D], [https://archives.arosworld.org/index.php?function=browse&amp;cat=game/fps Darkplaces Nexuiz Xonotic], [http://archives.arosworld.org/index.php?function=browse&amp;cat=game/fps Doom 3 SDL (OpenGL)], [http://archives.arosworld.org/index.php?function=browse&amp;cat=game/fps Hexenworld and Hexen 2], [https://archives.arosworld.org/index.php?function=browse&amp;cat=game/fps Aliens vs Predator Gold 2000 avp (openGL)], [https://archives.arosworld.org/index.php?function=browse&amp;cat=game/fps Odamex (openGL doom)], [https://archives.arosworld.org/?function=showfile&amp;file=game/fps/ zgloom], [], [https://archives.arosworld.org/?function=showfile&amp;file=game/fps/ ab3dhd], [], 
|&lt;!--Amiga OS--&gt;Doom, Quake, AB3D, Fears, Breathless, Gloom, 
|&lt;!--AmigaOS4--&gt;Doom, Quake, 
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=12 Doom], Quake, Quake 3 Arena, [https://github.com/OpenXRay/xray-16 S.T.A.L.K.E.R Xray]
|-
|&lt;!--Sub Menu--&gt;Games MMORG like 
|&lt;!--AROS--&gt;[ Eternal Lands (OpenGL)],
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Platform like 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=game/platform], [ Maze of Galious], [ Gish]*(openGL), [ Mega Mario], [https://archives.arosworld.org/?function=showfile&amp;file=game/platform/ thextech SMBX], [http://www.gianas-return.de/ Giana's Return], [http://www.sqrxz.de/ Sqrxz], [www.sqrxz2.de/ Sqrxz 2], [http://www.sqrxz.de/sqrxz-3/ Sqrxz 3], [http://www.sqrxz.de/sqrxz-4/ Sqrxz 4], [http://archives.arosworld.org/index.php?function=browse&amp;cat=game/platform Cave Story], [https://bszili.morphos.me/ Frogatto], [https://bszili.morphos.me/ OpenJazz], [https://archives.arosworld.org/?function=showfile&amp;file=game/platform/ pekkakana2], [ Aquaria], [https://archives.arosworld.org/?function=showfile&amp;file=game/platform/ sonic CD], [], 
|&lt;!--Amiga OS--&gt;[ Giana Sisters], [], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Puzzle [https://github.com/mariopartyrd/marioparty4/tree/port Party], [https://github.com/mdodis/OpenSolomonsKey OpenSolomonsKey], [], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=game/puzzle], [ Cubosphere (OpenGL)], [http://archives.arosworld.org/index.php?function=browse&amp;cat=game/puzzle Candy Crisis], [http://bszili.morphos.me/ TailTale], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Racing [ Trigger Rally], [ VDrift], [http://www.ultimatestunts.nl/index.php?page=2&amp;lang=en Ultimate Stunts], [http://maniadrive.raydium.org/ Mania Drive], [https://github.com/plowteam/donut Simpsons Hit and Run], [], 
|&lt;!--AROS--&gt;[ Super Tux Kart (OpenGL)], [http://www.dusabledanslherbe.eu/AROSPage/F1Spirit.30.html F1 Spirit (OpenGL)], [http://bszili.morphos.me/index.html MultiRacer], [https://bszili.morphos.me/ Speed Dreams], [], 
|&lt;!--AmigaOS--&gt;
|&lt;!--AmigaOS4--&gt;[http://bszili.morphos.me/index.html Speed Dreams], 
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=12], [http://bszili.morphos.me/index.html TORCS], 
|-
|&lt;!--Sub Menu--&gt;Games 1st first person DRPG [https://wiki.rpg.net/index.php/Open_Game_Systems Misc], [https://github.com/OpenEnroth/OpenEnroth OpenEnroth MM], []
|&lt;!--AROS--&gt;[https://github.com/BSzili/aros-stuff Arx Libertatis], [http://www.playfuljs.com/a-first-person-engine-in-265-lines/ js raycaster], [https://github.com/Dorthu/es6-crpg webgl], [https://github.com/sonountaleban/AmiShockolate System Shock], [], [], 
|&lt;!--AmigaOS--&gt;Phantasie, Faery Tale, Dungeon Master, 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games 3rd third person action CRPG  [https://sourceforge.net/projects/sumwars/ Summoning Wars], [https://www.solarus-games.org/ Solarus], [https://wiki.rpg.net/index.php/Open_Game_Systems Misc], [https://github.com/alexbatalov/fallout1-ce fallout ce], [https://github.com/rwengine/openrw gta3], [https://github.com/gta-reversed/gta-reversed gta3 sa], [https://github.com/mrxenginner/reVC gta3 vc revc], 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/?function=showfile&amp;file=game/strategy/ fheroes2 homm2], [https://archives.arosworld.org/?function=showfile&amp;file=game/roleplaying/ breakhack], [https://archives.arosworld.org/?function=showfile&amp;file=game/roleplaying/ devilutionx diablo 1 hellfire], [https://archives.arosworld.org/?function=showfile&amp;file=game/roleplaying/ fallout 1], [https://archives.arosworld.org/?function=showfile&amp;file=game/strategy/ stratagus], [https://archives.arosworld.org/?function=showfile&amp;file=game/strategy/ hostile-takeover], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games isometric RPG [https://sourceforge.net/projects/sumwars/ Summoning Wars], [https://www.solarus-games.org/ Solarus], [https://wiki.rpg.net/index.php/Open_Game_Systems Misc], [https://github.com/topics/dungeon?l=javascript Dungeon], [], [https://github.com/clintbellanger/heroine-dusk JS Dusk], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=game/roleplaying nethack], [https://archives.arosworld.org/index.php?function=browse&amp;cat=game/roleplaying GemRB], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games card based RPG [https://github.com/open-duelyst/duelyst Duelyst], [], [], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games turn based tactics RPG [], [], [], [], [], [], 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=game/strategy UFO AI], [http://play.freeciv.org/ FreeCiv], [], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Strategy [http://rtsgus.org/ RTSgus], [http://stargus.sourceforge.net/ Stargus], [https://github.com/KD-lab-Open-Source/Perimeter Perimeter], [https://matty77.itch.io/conflict-3049 conflict-3049], [], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=game/strategy MegaGlest (OpenGL)], [https://archives.arosworld.org/?function=showfile&amp;file=game/strategy/ signus], [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=1443&amp;rowstart=140&amp;pid=12446#post_12446 Wargus warcraft 2 setup], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=12]
|-
|&lt;!--Sub Menu--&gt;Games Rhythm, Beat, Step [], [], [https://clonehero.net/ clonehero], [https://github.com/MatteoGodzilla/Dj-Engine Dj-Engine], 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=game/misc Frets on Fire], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Shoot Em Ups [http://www.mhgames.org/oldies/formido/ Formido], [http://code.google.com/p/violetland/ Violetland], 
||&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=game/action Open Tyrian], [http://www.parallelrealities.co.uk/projects/starfighter.php Starfighter], [ Alien Blaster], [https://github.com/OpenFodder/openfodder OpenFodder], [https://archives.arosworld.org/?function=showfile&amp;file=game/action/ tbftss The Battle for the Solar System: the Pandora War]
|&lt;!--AmigaOS--&gt;
|&lt;!--AmigaOS4--&gt;[http://www.parallelrealities.co.uk/projects/starfighter.php Starfighter], [ The Battle for the Solar System: the Pandora War]
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Simulations [http://scp.indiegames.us/ Freespace 2], [http://www.heptargon.de/gl-117/gl-117.html GL117], [http://code.google.com/p/corsix-th/ Theme Hospital], [http://code.google.com/p/freerct/ Rollercoaster Tycoon], [http://hedgewars.org/ Hedgewars], [https://github.com/raceintospace/raceintospace raceintospace], [https://github.com/Return-To-The-Roots RTTR Settlers 2], [https://github.com/OoliteProject/oolite oolite elite], [https://github.com/fesh0r/newkind newkind elite], [], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;SimCity, SimAnt, Sim Hospital, Theme Park, 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=12]
|-
|&lt;!--Sub Menu--&gt;Games Life Sim [https://github.com/ACreTeam/forest Animal Crossing], [ ], [], [], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Horror [https://github.com/Mikompilation/MikuPan Fatal Frame], [ ], [], [], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Sandbox Voxel Open World Exploration [https://github.com/ClassiCube/ Classicube],[http://www.michaelfogleman.com/craft/ Craft], [https://github.com/tothpaul/DelphiCraft DelphiCraft],[https://www.minetest.net/ Luanti formerly Minetest], [ infiniminer], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Battle Royale [https://bruh.io/ Play.Bruh.io], [https://www.coolmathgames.com/0-copter Copter Royale], [https://surviv.io/ Surviv.io], [https://nuggetroyale.io/#Ketchup Nugget Royale], [https://miniroyale2.io/ Miniroyale2.io], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Tower Defense [https://chriscourses.github.io/tower-defense/ HTML5], [https://github.com/SBardak/Tower-Defense-Game TD C++], [https://github.com/bdoms/love_defense LUA and LOVE], [https://github.com/HyOsori/Osori-WebGame HTML5], [https://github.com/PascalCorpsman/ConfigTD ConfigTD Pascal], [https://github.com/GloriousEggroll/wine-ge-custom Wine], []
|&lt;!--AROS--&gt;[https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=1443&amp;rowstart=180&amp;pid=12871#post_12871 Plants vs Zombies PvZ], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Visual Novel Engines [https://github.com/diane1f0cd/VisualNovelTemplate Visual Novel Template], [https://github.com/Kirilllive/tuesday-js Tuesday JS], [https://github.com/tejasnayak25/vnsutra vnsutra], [https://github.com/weetabix-su/renpsp-dev RenPSP], [https://github.com/Galladite27/ONScripter-EN ONScripter-EN], [https://github.com/NathanGuilhot/VNES-Raylib https://github.com/NathanGuilhot/VNES VNES in Raylib], [https://www.renpy.org/latest.html renpy ren'py python based], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Virtual Reality VR [https://gitlab.com/madsbuvi/openmw openmw vr], [https://github.com/Team-Beef-Studios/BeefRaiderXR BeefRaiderXR], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Virtual Table Top VTT [ Roll20], [https://www.owlbear.rodeo/ owlbear rodeo], [], [], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Computer assisted TableTop TTRPG OSR [https://www.rpgsolo.com/play.php RPGSolo], [https://github.com/fpsvogel/solo-ttrpgs Solo TTRPG], [], [], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games 2D 3D Engines [https://github.com/fegennari/3DWorld 3DWorld], [https://github.com/GarageGames/Torque3D Torque3D], [https://github.com/gameplay3d/GamePlay GamePlay 3D],  [https://www.babylonjs.com/ BabylonJS ], [ Godot], [ Ogre], [ Crystal Space], [https://github.com/JacobHess03/ Dragon-Quest like], [https://github.com/bjornbytes/lovr Lua LOVE for 2D LOVR for 3D], [], 
|&lt;!--AROS--&gt;[https://www.arkhamdev.net/wiki.htm?id=agx Arkham Development antiryadgx 8.9 lts with register], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games C based game frameworks [https://github.com/orangeduck/Corange Corange], [https://github.com/scottcgi/Mojoc Mojoc], [https://orx-project.org/ Orx], [https://github.com/ioquake/ioq3 Quake 3], [https://www.mapeditor.org/ Tiled], [https://www.raylib.com/ 2d Raylib], [https://github.com/Rabios/awesome-raylib other raylib], [https://github.com/MrFrenik/gunslinger Gunslinger], [https://o3de.org/ o3d], [http://archives.aros-exec.org/index.php?function=browse&amp;cat=development/library GLFW], [], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=development/library Raylib 5], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games RPGMaker MV/MZ-compatible projects [https://github.com/Psychronic-Games/RPGReactor RPGReactor js],
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Virtual Pinball [https://github.com/vpinball/vpinball vpinball], [], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games unpack unarc [], [], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|}


==Application Guides==

[[#top|...to the top]]

===Web Browser===

OWB is now at version 2.0 (which got an engine refresh, from July 2015 to February 2019) and 3.0.

This latest version has a good support for many/most web sites, even YouTube web page now works. 

This improved compatibility comes at the expense of higher RAM usage (now 1GB RAM is the absolute minimum). 

Also, keep in mind that the lack of a JIT (Just-In-Time) JS compiler on the 32 bit version, makes the web surfing a bit slow. 

Only the 64 bit version of OWB 2.0 will have JIT enabled, thus benefitting of more speed. There are tooltypes that can be added to the icon to provide further features JIT, MSE etc 


Certificates from [https://curl.se/docs/caextract.html ca certs], 


DNS tracking blocking with [https://easylist.to/easylist/easylist.txt easylist.txt] in PROGDIR:Conf before starting browser with enabled AdBlock [https://github.com/easylist/easylist/tree/master easylist], [https://gitlab.com/eyeo anti abp], [https://firebog.net/ big blocklist], [https://github.com/StevenBlack/hosts Steves], [], [], 

This can be enabled with OWB Odyssey with Windows -&gt; Content Blocking and Windows -&gt; Messages and enter 

 https://www.youtube.com/api/stats/ads*
 https://www.youtube.com/pagead/adview*
 https://www.youtube.com#@##player-ads*

into your custom filters 


Element blocker browser extension might be needed for [https://github.com/easylist/easylist/wiki/Youtube-Issues youtube], [ mid roll], [ pre roll], [ ],  


OWB speed is much better when running from RAM Disk, the best way is to add the below into your S:User-Startup which copies OWB drawer from Extras:Internet/OWB to RAM Disk: 

So add this :
&lt;pre&gt;
copy Extras:Internet/OWB Ram:OWB/ ALL CLONE &gt;NIL:
copy Extras:Internet/OWB.info Ram: &gt;NIL:
&lt;/pre&gt;
Open RAM Disk and open OWB drawer and double click on OWB icon so that the above icon tooltypes are activated 

Problems are that the copy time is long (around 20 seconds added in the background), but we can make it faster if we delete useless files from the OWB drawer (docs, …)
If you don’t copy the drawer back onto the HD, you won’t save your cache, cookies, passwords… So you need a script for it.


Error messages 

SSL error &quot;cant verify with ca-certificates&quot;, check bios clock time date is correct 

Error 6, try checking networking prefs settings and Save / Use preferences again or a '''few times''' otherwise the network chipset may not be compatible with Aros 


[https://www.google.com/search?q=%s&amp;udm=14 Google search without AI overview] 


===E-mail===

 YAM does not support SSL and most mail providers now switched to encrypted SMTP/POP3 connections


====SimpleMail====

SimpleMail supports IMAP and appears to work with GMail, but it's never been reliable enough, it can crash with large mailboxes.

Please read more on this [http://www.freelists.org/list/simplemail-usr User list]


 GMail

Be sure to activate the pop3 usage in your gmail account setup / configuration first.

pop3: 
pop.gmail.com
Use SSL: Yes
Port: 995

smtp:
smtp.gmail.com (with authentication)
Use Authentication: Yes
Use SSL: Yes
Port: 465 or 587


 Hotmail/MSN/outlook/Microsoft Mail mid-2017, all outlook.com accounts will be migrated to Office 365 / Exchange

Most users are currently on POP which does not allow showing folders and many other features (technical limitations of POP3). With Microsoft IMAP you will get folders, sync read/unread, and show flags. You still won't get push though, as Microsoft has not turned on the IMAP Idle command as at Sept 2013.

If you want to try it, you need to first remove (you can't edit) your pop account (long-press the account on the accounts screen, delete account). Then set it up this way:

1. Email/Password
2. Manual
3. IMAP
4.

* Incoming: imap-mail.outlook.com, port 993, SSL/TLS should be checked
* Outgoing: smtp-mail.outlook.com, port 587, SSL/TLS should be checked
* POP server name pop-mail.outlook.com, port 995, POP encryption method SSL

 Yahoo  Mail

On April 24, 2002 Yahoo ceased to offer POP access to its free mail service. Introducing instead a yearly payment feature, allowing users POP3 and IMAP server support, along with such benefits as larger file attachment sizes and no adverts.

Sorry to see Yahoo leaving its users to cough up for the privilege of accessing their mail. Understandable, when competing against rivals such as Gmail and Hotmail who hold a large majority of users and were hacked in 2014 as well.


Incoming Mail (IMAP) Server

* Server - imap.mail.yahoo.com
* Port - 993
* Requires SSL - Yes

Outgoing Mail (SMTP) Server

* Server - smtp.mail.yahoo.com
* Port - 465 or 587
* Requires SSL - Yes
* Requires authentication - Yes

Your login info

* Email address - Your full email address (name@domain.com)
* Password - Your account's password
* Requires authentication - Yes


Note that you need to enable “Web &amp; POP Access” in your Yahoo Mail account to send and receive Yahoo Mail messages through any other email program.

You will have to enable “Allow your Yahoo Mail to be POPed” under “POP and Forwarding”, to send and receive Yahoo mails through any other email client.

Cannot be done since 2002 unless the customer pays Yahoo a subscription subs fee to have access to SMTP and POP3

* Set the POP server for incoming mails as pop.mail.yahoo.com. You will have to enable “SSL” and use 995 for Port.
* “Account Name or Login Name” – Your Yahoo Mail ID i.e. your email address without the domain “@yahoo.com”.
* “Email Address” – Your Yahoo Mail address i.e. your email address including the domain “@yahoo.com”. E.g. myname@yahoo.com
* “Password” – Your Yahoo Mail password.

Yahoo! Mail Plus users may have to set POP server as plus.pop.mail.yahoo.com and SMTP server as plus.smtp.mail.yahoo.com.

* Set the SMTP server for outgoing mails as smtp.mail.yahoo.com. You will also have to make sure that “SSL” is enabled and use 465 for port. you must also enable “authentication” for this to work.


====YAM Yet Another Mailer====

 YAM does not support SSL and most mail providers have now switched to encrypted SMTP/POP3 connections

This email client is POP3 only if the SSL library is available [http://www.freelists.org/list/yam YAM Freelists]

One of the downsides of using a POP3 mailer unfortunately - you have to set an option not to delete the mail if you want it left on the server. IMAP keeps all the emails on the server.

Possible issues

Sending mail issues is probably a matter of using your ISP's SMTP server, though it could also be an SSL issue.


getting a &quot;Couldn't initialise TLSv1 / SSL error

Use of on-line e-mail accounts with this email client is not possible as it lacks the OpenSSL AmiSSl v3 compatible library

 GMail 
Incoming Mail (POP3) Server - requires SSL: pop.gmail.com
Use SSL: Yes
Port: 995

Outgoing Mail (SMTP) Server - requires TLS: smtp.gmail.com (use authentication)
Use Authentication: Yes
Use STARTTLS: Yes (some clients call this SSL)
Port: 465 or 587

Account Name: your Gmail username (including '@gmail.com')
Email Address: your full Gmail email address (username@gmail.com)
Password: your Gmail password

Anyway, the SMTP is pop.gmail.com port 465 and it uses SSLLv3 Authentication. The POP3 settings are for the same server (pop.gmail.com), only on port 995 instead.


 Outlook.com access

&lt;pre &gt;
Outlook.com SMTP server address: smtp.live.com
Outlook.com SMTP user name: Your full Outlook.com email address (not an alias)
Outlook.com SMTP password: Your Outlook.com password
Outlook.com SMTP port: 587
Outlook.com SMTP TLS/SSL encryption required: yes 
&lt;/pre &gt;


 Yahoo  Mail

&lt;pre &gt;
“POP3 Server” – Set the POP server for incoming mails as pop.mail.yahoo.com. You will have to enable “SSL” and use 995 for Port.
“SMTP Server” – Set the SMTP server for outgoing mails as smtp.mail.yahoo.com. You will also have to make sure that “SSL” is enabled and use 465 for port. you must also enable “authentication” for this to work.
“Account Name or Login Name” – Your Yahoo Mail ID i.e. your email address without the domain “@yahoo.com”.
“Email Address” – Your Yahoo Mail address i.e. your email address including the domain “@yahoo.com”. E.g. myname@yahoo.com
“Password” – Your Yahoo Mail password.
&lt;/pre &gt;

Yahoo! Mail Plus users may have to set POP server as plus.pop.mail.yahoo.com and SMTP server as plus.smtp.mail.yahoo.com.

Note that you need to enable “Web &amp; POP Access” in your Yahoo Mail account to send and receive Yahoo Mail messages through any other email program.

You will have to enable “Allow your Yahoo Mail to be POPed” under “POP and Forwarding”, to send and receive Yahoo mails through any other email client.

Cannot be done since 2002 unless the customer pays Yahoo a monthly fee to have access to SMTP and POP3


 Microsoft Outlook Express Mail 

1. Get the files to your PC.
By whatever method get the files off your Amiga onto your PC. In the YAM folder you have a number of different folders, one for each of your folders in YAM. Inside that is a file usually some numbers such as 332423.283. YAM created a new file for every single email you received.

2. Open up a brand new Outlook Express. Just configure the account to use 127.0.0.1 as mail servers. It doesn't really matter. You will need to manually create any subfolders you used in YAM.

3. You will need to do a mass rename on all your email files from YAM. Just add a .eml to the end of it. Amazing how PCs still rely mostly on the file name so it knows what sort of file it is rather than just looking at it! There are a number of multiple renamers online to download and free too.

4. Go into each of your folders, inbox, sent items etc. And do a select all then drag the files into Outlook Express (to the relevant folder obviously) Amazingly the file format that YAM used is very compatible with .eml standard and viola your emails appear. With correct dates and working attachments.

5. If you want your email into Microsoft Outlook. Open that up and create a new profile and a new blank PST file. Then go into File Import and choose to import from Outlook Express. And the mail will go into there. And viola.. you have your old email from your Amiga in a more modern day format.


===FTP===

Magellan has a great FTP module. It allows transferring files from/to a FTP server over the Internet or the local network and, even if FTP is perceived as a &quot;thing of the past&quot;, its usability is all inside the client. The FTP thing has a nice side effect too, since every Icaros machine can be a FTP server as well, and our files can be easily transferred from an Icaros machine to another with a little configuration effort.

First of all, we need to know the 'server' IP address. Server is the Icaros machine with the file we are about to download on another Icaros machine, that we're going to call 'client'. To do that, move on the server machine and 1) run Prefs/Services to be sure &quot;FTP file transfer&quot; is enabled (if not, enable it and restart Icaros); 2) run a shell and enter this command:

ifconfig -a

Make a note of the IP address for the network interface used by the local area network. For cabled devices, it usually is net0:. Now go on the client machine and run Magellan:

Perform these actions: 1) click on FTP; 2) click on ADDRESS BOOK; 3) click on &quot;New&quot;. 
You can now add a new entry for your Icaros server machine:

1) Choose a name for your server, in order to spot it immediately in the address book. Enter the IP address you got before.

2) click on Custom Options:


1) go to Miscellaneous in the left menu;

2) Ensure &quot;Passive Transfers&quot; is NOT selected;

3) click on Use. We need to deactivate Passive Transfers because YAFS, the FTP server included in Icaros, only allows active transfers at the current stage. Now, we can finally connect to our new file source:


1) Look into the address book for the newly introduced server, be sure that name and IP address are right, and

2) click on Connect. A new lister with server's &quot;MyWorkspace&quot; contents will appear. You can now transfer files over the network choosing a destination among your local (client's) volumes.

Can be adapted to any FTP client on any platform of your choice, just be sure your client allows Active Transfers as well.


===IRC Internet Relay Chat===

Jabberwocky is ideal for one-to-one social media communication, use IRC if you require one to many. 

Just type a message in ''lowercase''' letters and it will be posted to all in the [ AROS irc channel]. Please do not use UPPER CASE as it is a sign of SHOUTING which is annoying.

Other things to type in - replace &lt;message&gt; with a line of text and &lt;nick&gt; with a person's name

&lt;pre&gt;
/help

/list

/who
/whois &lt;nick&gt;

/msg &lt;nick&gt; &lt;message&gt;

/query &lt;nick&gt; 
&lt;message&gt;s
/query

/away &lt;message&gt;
/away

/quit &lt;going away message&gt; 
&lt;/pre&gt;


[http://irchelp.org/irchelp/new2irc.html#smiley Intro guide here]. IRC Primer can be found here in [http://www.irchelp.org/irchelp/ircprimer.html html], [http://www.irchelp.org/irchelp/text/ircprimer.txt TXT], [http://www.kei.com/irc/IRCprimer1.1.ps PostScript].


Issue the command /me &lt;text&gt; where &lt;text&gt; is the text that should follow your nickname.
Example: /me slaps ajk around a bit with a large trout

/nick &lt;newNick&gt;

/nickserv register &lt;password&gt; &lt;email address&gt;

/ns instead of /nickserv, while others might need /msg nickserv

/nickserv identify &lt;password&gt;

Alternatives:
/ns identify &lt;password&gt;
/msg nickserv identify &lt;password&gt;


==== IRC WookieChat ====

WookieChat is the most complete internet client for communication across the IRC Network. WookieChat allows you to swap ideas and communicate in real-time, you can also exchange Files, Documents, Images and everything else using the application's DCC capabilities.


add smilies drawer/directory

 run wookiechat from the shell and set stack to 1000000 e.g. wookiechat stack 1000000

select a server / server window

* nickname 
* user name 
* real name - optional

Once you configure the client with your preferred screen name, you'll want to find a channel to talk in.


servers

* New Server - click on this to add / add extra - change details in section below this click box 
* New Group
* Delete Entry
* Connect to server
* connect in new tab
* perform on connect

Change details

* Servername - change text in this box to one of the below Server: 
* Port number - no need to change
* Server password
* Channel - add #channel from below 
* auto join - can click this 
* nick registration password,

Click Connect to server button above


&lt;pre&gt;
Server: irc.freenode.net
Channel: #aros
&lt;/pre&gt;

irc://irc.freenode.net/aros

&lt;pre&gt;
Server: chat.amigaworld.net 
Channel: #amigaworld or #amigans 
&lt;/pre&gt;

&lt;pre&gt;
On Sunday evenings USA time usually starting around 3PM EDT (1900 UTC)
Server:irc.superhosts.net
Channel #team*amiga  
&lt;/pre&gt;

&lt;pre&gt;
BitlBee and Minbif are IRCd-like gateways to multiple IM networks
Server: im.bitlbee.org 
Port 6667 
Seems to be most useful on WookieChat as you can be connected to several servers at once. One for Bitlbee and any messages that might come through that. One for your normal IRC chat server. 
&lt;/pre&gt;

[http://www.bitlbee.org/main.php/servers.html Other servers],

&lt;pre&gt;
#Amiga.org - irc.synirc.net eu.synirc.net dissonance.nl.eu.synirc.net (IPv6: 2002:5511:1356:0:216:17ff:fe84:68a) 
twilight.de.eu.synirc.net zero.dk.eu.synirc.net us.synirc.net avarice.az.us.synirc.net envy.il.us.synirc.net harpy.mi.us.synirc.net 
liberty.nj.us.synirc.net snowball.mo.us.synirc.net - Ports 6660-6669 7001 (SSL)
&lt;/pre&gt;

&lt;pre&gt;
Multiple server support
&quot;Perform on connect&quot; scripts and channel auto-joins
Automatic Nickserv login
Tabs for channels and private conversations
CTCP PING, TIME, VERSION, SOUND
Incoming and Outgoing DCC SEND file transfers
Colours for different events
Logging and automatic reloading of logs
mIRC colour code filters
Configurable timestamps
GUI for changing channel modes easily
Configurable highlight keywords
URL Grabber window
Optional outgoing swear word filter
Event sounds for tabs opening, highlighted words, and private messages
DCC CHAT support
Doubleclickable URL's
Support for multiple languages using LOCALE
Clone detection
Auto reconnection to Servers upon disconnection
Command aliases
Chat display can be toggled between AmIRC and mIRC style
Counter for Unread messages
Graphical nicklist and graphical smileys with a popup chooser
&lt;/pre&gt;


====IRC Aircos ====

Double click on Aircos icon in Extras:Networking/Apps/Aircos. It has been set up with a guest account for trial purposes. Though ideally, choose a nickname and password for frequent use of irc. 


====IRC and XMPP Jabberwocky====
 Servers are setup and close down at random 
You sign up to a server that someone else has setup and access chat services through them. 

The two ways to access chat from jabberwocky
&lt;pre &gt;
Jabberwocky -&gt; Server -&gt; XMPP -&gt; open and ad-free 
Jabberwocky -&gt; Server -&gt; Transports (Gateways) -&gt; Proprietary closed systems 
&lt;/pre &gt;

The Jabber.org service connects with all IM services that use XMPP, the open standard for instant messaging and presence over the Internet. The services we connect with include Google Talk (closed), Live Journal Talk, Nimbuzz, Ovi, and thousands more. However, you can not connect from Jabber.org to proprietary services like AIM, ICQ, MSN, Skype, or Yahoo because they don’t yet use XMPP components (XEP-0114) '''but''' you can use Jabber.com's servers and IM gateways (MSN, ICQ, Yahoo etc.) instead.

The best way to use jabberwocky is in conjunction with a public jabber server with '''transports''' to your favorite services, like gtalk, Facebook, yahoo, ICQ, AIM, etc.


You have to register with one of the servers, [https://list.jabber.at/ this list] or [http://www.jabberes.org/servers/ another list], [http://xmpp.net/ this security XMPP list],

Unfortunately jabberwocky can only connect to one server at a time so it is best to check what services each server offers. If you set it up with separate Facebook and google talk accounts, for example, sometimes you'll only get one or the other.

Jabberwocky open a window where the Jabber server part is typed in as well as your Nickname and Password.

Jabber ID (JID) identifies you to the server and other users.

Once registered the next step is to goto Jabberwocky's &quot;Windows&quot; menu and select the &quot;Agents&quot; option. The &quot;Agents List&quot; window will open.

Roster (contacts list)

[http://search.wensley.org.uk/ Chatrooms] (MUC) are available

File Transfer - can send and receive files through the Jabber service but not with other services like IRC, ICQ, AIM or Yahoo. All you need is an installed webbrowser and OpenURL.

Clickable URLs - The message window uses Mailtext.mcc and you can set a URL action in the MUI mailtext prefs like SYS:Utils/OpenURL %s NEWWIN.

There is no consistent Skype like (H.323 VoIP) video conferencing available over Jabber. The move from xmpp to Jingle should help but no support on any amiga-like systems at the moment. [http://aminet.net/package/dev/src/AmiPhoneSrc192 AmiPhone] and [http://www.lysator.liu.se/%28frame,faq,nobg,useframes%29/ahi/v4-site/ Speak Freely] was an early attempt voice only contact. SIP and Asterisk are other PBX options.


 Facebook

If you're using the XMPP transport provided by Facebook themselves, chat.facebook.com, it looks like they're now requiring SSL transport. This means jabberwocky method below will no longer work. The best thing to do is to create an ID on a public jabber server which has a Facebook gateway.

&lt;pre &gt;
1. launch jabberwocky
2. if the login window doesn't appear on launch, select 'account' from the jabberwocky menu
3. your jabber ID will be user@chat.facebook.com where user is your user ID
4. your password is your normal facebook password
5. to save this for next time, click the popup gadget next to the ID field

6. click the 'add' button
7. click the 'close' button
8. click the 'connect' button
&lt;/pre &gt;

you're done. you can also click the 'save as default account' button if you want. jabberwocky configured to auto-connect when launching the program, but you can configure as you like. there is amigaguide documentation included with jabberwocky.

[http://amigaworld.net/modules/newbb/viewtopic.php?topic_id=37085&amp;forum=32 Read more here]

for Facebook users, you can log-in directly to Facebook with jabberwocky. just sign in as @chat.facebook.com with your Facebook password as the password


 Twitter

For a few years, there has been added a twitter transport. Servers include [http://jabber.hot-chilli.net/ jabber.hot-chili.net],  and .

An [http://jabber.hot-chilli.net/tag/how-tos/ How-to]

:Read [http://jabber.hot-chilli.net/2010/05/09/twitter-transport-working/ more]

 Instagram 

no support at the moment best to use a web browser based client

 ICQ

The new version (beta) of StriCQ uses a newer ICQ protocol. Most of the ICQ Jabber Transports still use an older ICQ protocol. You can only talk one-way to StriCQ using the older Transports. Only the newer ICQv7 Transport lets you talk both ways to StriCQ. Look at the server lists in the first section to check.

Register on a Jabber server, e.g. this one works: http://www.jabber.de/
Then login into Jabberwocky with the following login data e.g. xxx@jabber.de / Password: xxx Now add your ICQ account under the window-&gt;Agents-&gt;&quot;Register&quot;. Now Jabberwocky connects via the Jabber.de server with your ICQ account.

 Yahoo Messenger

although yahoo! does not use xmpp protocol, you should be able to use the transport methods to gain access and post your replies

 MSN

early months of 2013 Microsoft will ditch MSN Messenger client and force everyone to use Skype...but MSN protocol and servers will keep working as usual for quite a long time....

Occasionally the Messenger servers have been experiencing problems signing in.  You may need to sign in at www.outlook.com and then try again.  It may also take multiple tries to sign in.  (This also affects you if you’re using Skype.)

You have to check each servers' Agents List to see what transports (MSN protocol, ICQ protocol, etc.) are supported or use the list address' provided in the section above. Then register with each transport (IRC, MSN, ICQ, etc.) to which you need access. After registering you can Connect to start chatting.

msn.jabber.com/registered should appear in the window.

From this [http://tech.dir.groups.yahoo.com/group/amiga-jabberwocky/message/1378 JW group] guide which  helps with this process in a clear, step by step procedure.

1. Sign up on MSN's site for a passport account. This typically involves getting a Hotmail address.

2. Log on to the Jabber server of your choice and do the following:

* Select the &quot;Windows/Agents&quot; menu option in Jabberwocky.
* Select the MSN Agent from the list presented by the server.
* Click the Register button to open a new window asking for:
**Username = passort account email address, typically your hotmail address.
**Nick = Screen name to be shown to anyone you add to your buddy list.
**Password = Password for your passport account/hotmail address.
* Click the Register button at the bottom of the new window.

3. If all goes well, you will see the MSN Gateway added to your buddy list. If not, repeat part 2 on another server. Some servers may show MSN in their list of available agents, but have not updated their software for the latest protocols used by MSN.

4. Once you are registered, you can now add people to your buddy list. Note that you need to include the '''msn.''' ahead of the servername so that it knows what gateway agent to use. Some servers may use a slight variation and require '''msg.gate.''' before the server name, so try both to see what works.

If my friend's msn was amiga@hotmail.co.uk and my jabber server was @jabber.meta.net.nz..
then amiga'''%'''hotmail.com@'''msn.'''jabber.meta.net.nz

or another the trick to import MSN contacts is that you don't type the hotmail URL but the passport URL... e.g. Instead of: goodvibe%hotmail.com@msn.jabber.com  You type: goodvibe%passport.com@msn.jabber.com 
And the thing about importing contacts I'm afraid you'll have to do it by hand, one at the time...

 Google Talk

any XMPP server will work, but you have to add your contacts manually. a google talk user is typically either @gmail.com or @talk.google.com. a true gtalk transport is nice because it brings your contacts to you and (can) also support file transfers to/from google talk users.

implement Jingle a set of extensions to the IETF's Extensible Messaging and Presence Protocol (XMPP)

support ended early 2014 as Google moved to Google+ Hangouts which uses it own proprietary format


===Video Player MPlayer===

Many of the menu features (such as doubling) do not work with the current version of mplayer but using

4:3
 mplayer -vf scale=800:600 file.avi

16:9
 mplayer -vf scale=854:480 file.avi

if you want gui use;
 mplayer -gui 1 &lt;other params&gt; file.avi

&lt;pre &gt;
stack 1000000

; using AspireOS 1.xx 
; copy FROM SYS:Extras/Multimedia/MPlayer/ TO RAM:MPlayer ALL CLONE &gt; Nil:

; using Icaros Desktop 1.x 
; copy FROM SYS:Tools/MPlayer/ TO RAM:MPlayer ALL CLONE &gt; Nil:

; using Icaros Desktop 2.x 
; copy FROM SYS:Utilities/MPlayer/ TO RAM:MPlayer ALL CLONE &gt; Nil:

cd RAM:MPlayer
run MPlayer -gui &gt; Nil:
;run MPlayer -gui -ao ahi_dev -playlist http://www.radio-paralax.de/listen.pls &gt; Nil: 
&lt;/pre &gt;

$ mplayer rtsp://127.0.0.1:554/sample_300kbit.mp4


MPlayer supports multicast streaming, and rtp/rtsp protocols (it might require [http://www.live555.com/openRTSP/ live555 library] to work with some streams). But you might have to build it where it's disabled. Also, multicast won't work with some AmiTCP-likes. MIAMI supported it, though.

AROS supports IPv4 (old but works) and this includes the needed address space for RTP.

If you mean multicast via RTP - mplayer handles it. You can even force UDP over TCP

-rtsp-stream-over-tcp

If the rtsp Real Time Streaming Protocol  server needs authentification:

-user -passwd


MPlayer - Menu - Open Playlist and load already downloaded .pls or .m3u file - auto starts around 4 percent cache

MPlayer - Menu - Open Stream and copy one of the .pls lines below into space allowed, press OK and press play button on main gui interface


Old 8bit 16bit remixes chip tune game music 
 
http://www.radio-paralax.de/listen.pls 

http://scenesat.com/

http://www.shoutcast.com/radio/Amiga

http://www.theoldcomputer.com/retro_radio/RetroRadio_Main.htm

http://www.kohina.com/

http://www.remix64.com/

http://retrogamer.net/forum/

http://retroasylum.podomatic.com/rss2.xml

http://retrogamesquad.com/

http://www.retronauts.com/

http://monsterfeet.com/noquarter/

http://www.retrogamingradio.com/

http://www.radiofeeds.co.uk/mp3.asp


[[#top|...to the top]]

====ZunePaint==== 

simplified typical workflow

* importing and organizing and photo management
* making global and regional local correction(s) - recalculation is necessary after each adjustment as it is not in real-time 
* exporting your images in the best format available with the preservation of metadata


Whilst achieving 80% of a great photo with just a filter, the remaining 20% comes from a manual fine-tuning of specific image attributes.


For photojournalism, documentary, and event coverage, minimal touching is recommended. Stick to Camera Raw for such shots, and limit changes to level adjustment, sharpness, noise reduction, and white balance correction.

For fashion or portrait shoots, a large amount of adjustment is allowed and usually ends up far from the original. Skin smoothing, blemish removal, eye touch-ups, etc. are common.  Might alter the background a bit to emphasize the subject.

Product photography usually requires a lot of sharpening, spot removal, and focus stacking.

For landscape shots, best results are achieved by doing the maximum amount of preparation before/while taking the shot. No amount of processing can match timing, proper lighting, correct gear, optimal settings, etc. Excessive post-processing might give you a dramatic shot but best avoided in the long term.


* White Balance - Left Amiga or F12 and K and under &quot;Misc color effects&quot; tab with a pull down for White Balance - color temperature also known as AKA tint (movies) or tones (painting) - warm temp raise red reduce green blue - cool raise blue lower red green 
* Exposure - exposure compensation, highlight/shadow recovery
* Noise Reduction - during RAW development or using external software
* Lens Corrections - distortion, vignetting, chromatic aberrations
* Detail - capture sharpening and local contrast enhancement
* Contrast - black point, levels (sliders) and curves tools (F12 and K) 
* Framing - straighten () and crop (F12 and F) 
* Refinements - color adjustments and selective enhancements - Left Amiga or F12 and K for RGB and YUV histogram tabs - 
* Resizing - enlarge for a print or downsize for the web or email (F12 and D) 
* Output Sharpening - customized for your subject matter and print/screen size


White Balance - F12 and K

scan your image for a shade which was meant to be white (neutral with each RGB value being equal) like paper or plastic which is in the same light as the subject of the picture. Use the dropper tool to select this color, similar colours will shift and you will have selected the perfect white balance for your part of the image - for the whole picture make sure RAZ or CLR button at the bottom is pressed before applying to the image above.


Exposure correction

F12 and K - YUV Y luminosity - RGB extra red tint - move red curve slightly down and move blue green curves slightly up

Workflows in practice

* Undo - Right AROS key or F12 and Z 
* Redo - Right AROS key or F12 and R

First flatten your image (if necessary) and then do a rotation until the picture looks level. 
* Crop the picture. Click the selection button and drag a box over the area of the picture you want to keep. Press the crop button and the rest of the photo will be gone. 
* Adjust your saturation, exposure, hue levels, etc., (right AROS Key and K for color correction) until you are happy with the photo. Make sure you zoom in all of the way to 100% and look the photo over, zoom back out and move around. Look for obvious problems with the picture. 
* After coloring and exposure do a sharpen (Right AROS key and E for Convolution and select drop down option needed), e.g. set the matrix to 5x5 (roughly equivalent Amount to 60%) and set the Radius to 1.0. Click OK.


And save your picture


Implemented or would like to see for simplification and ease of use

basic filters (presets) like black and white, monochrome, edge detection (sobel), motion/gaussian blur, 
* negative, sepiatone, retro vintage, night vision, colour tint, color gradient, color temperature, glows, fire, lightning, lens flare, emboss, filmic, pixelate mezzotint, antialias, etc.

adjust / cosmetic tools such as crop, 
* reshaping tools, straighten, smear, smooth, perspective, liquify, bloat, pucker, push pixels in any direction, dispersion, transform like warp, blending with soft light, page-curl, whirl, ripple, fisheye, neon,  etc. 
* red eye fixing, blemish remover, skin smoothing, teeth whitener, make eyes look brighter, desaturate,

effects like oil paint, cartoon, pencil sketch, charcoal, noise/matrix like sharpen/unsharpen, (right AROS key with A for Artistic effects) 
* blend two image, gradient blend, masking blend, explode, implode, custom collage, surreal painting, comic book style, needlepoint, stained glass, watercolor, mosaic, stencil/outline, crayon, chalk, etc.

borders such as 
* dropshadow, rounded, blurred, color tint, picture frame, film strip polaroid, bevelled edge, etc.

brushes e.g.
* frost, smoke, etc.

and manual control of

fix lens issues including vignetting (darkening), color fringing and barrel distortion, and chromatic and geometric aberration -  lens and body profiles

perspective correction

levels - directly modify the levels of the tone-values of an image, by using sliders for highlights, midtones and shadows

curves -  Color Adjustment and Brightness/Contrast

color balance

one single color transparent (alpha channel (color information/selections) for masking and/or blending ) for backgrounds, etc.

Threshold indicates how much other colors will be considered mixture of the removed color and non-removed colors

decompose layer into a set of layers with each holding a different type of pattern that is visible within the image

any selection using any selecting tools like lasso tool, marquee tool etc. the selection will temporarily be save to alpha 
If you create your image without transparency then the Alpha channel is not present, but you can add later.

File formats like .psd (Photoshop file has layers, masks etc.  contains edited sensor data. The original sensor data is no longer available) .xcf .raw .hdr

Image Picture Formats
* low dynamic range (JPEG, PNG, TIFF 8-bit), 16-bit (PPM, TIFF), typically as a 16-bit TIFF in either ProPhoto or AdobeRGB colorspace -  TIFF files are also fairly universal – although, if they contain proprietary data, such as Photoshop Adjustment Layers or Smart Filters, then they can only be opened by Photoshop making them proprietary.
* linear high dynamic range (HDR) images (PFM, [http://www.openexr.com/ ILM .EXR], jpg, [http://aminet.net/util/dtype cr2] (canon tiff based), hdr, NEF, CRW, ARW, MRW, ORF, RAF (Fuji), PEF, DCR, SRF, ERF, DNG files are RAW converted to an Adobe proprietary format - a container that can embed the raw file as well as the information needed to open it) 
An old version of [http://archives.aros-exec.org/index.php?function=browse&amp;cat=graphics/convert dcraw]

There is no single RAW file format. Each camera manufacturer has one or more unique RAW formats. RAW files contain the brightness levels data captured by the camera sensor. This data cannot be modified. A second smaller file, separate XML file, or within a database with instructions for the RAW processor to change exposure, saturation etc. The extra data can be changed but the original sensor data is still there. RAW is technically least compatible.

A raw file is high-bit (usually 12 or 14 bits of information) but a camera-generated TIFF file will be usually converted by the camera (compressed, downsampled) to 8 bits. The raw file has no embedded color balance or color space, but the TIFF has both. These three things (smaller bit depth, embedded color balance, and embedded color space) make it so that the TIFF will lose quality more quickly with image adjustments than the raw file. The camera-generated TIFF image is much more like a camera processed JPEG than a raw file. A strong advantage goes to the raw file. The power of RAW files, such as the ability to set any color temperature non-destructively and will contain more tonal values.

The principle of preserving the maximum amount of information to as late as possible in the process. The final conversion - which will always effectively represent a &quot;downsampling&quot; - should prevent as much loss as possible.

Once you save it as TIFF, you throw away some of that data irretrievably. When saving in the lossy JPEG format, you get tremendous file size savings, but you've irreversibly thrown away a lot of image data. As long as you have the RAW file, original or otherwise, you have access to all of the image data as captured.

Keyboard equivalence with Photoshop(tm) would help 

File
PHOTOSHOP	SHORTCUT	GIMP
New	Ctrl+n	New
Open	Ctrl+o	Open
Close	Ctrl+w	Close
Save	Ctrl+s	Save
Save as	Shift+Ctrl+s	Save as
Revert	F12	Revert
Print	Ctrl+p	Print
Exit	Ctrl+q	Quit
 
Edit
PHOTOSHOP	SHORTCUT	GIMP
Undo/Redo (1 level)	Ctrl+z	Undo (Redo is Shift+Ctrl+z)
Cut	Ctrl+x	Cut
Copy	Ctrl+c	Copy
Paste	Ctrl+v	Paste
Paste Into	Shift+Ctrl+v	Paste Into
Fill with FG color	Alt+Backspace	Fill with FG color
Fill with BG color	Control+Backspace	Fill with BG color
 
Image/Colors
PHOTOSHOP	SHORTCUT	GIMP
Levels	Ctrl+l	Levels
Auto Contrast	Shift+Ctrl+Alt+l	Stretch Contrast (same?)
Curves	Ctrl+m	Curves
Color Balance	Ctrl+b	Color Balance
Hue/Saturation	Ctrl+u	Hue-Saturation
Desaturate	Shift+Ctrl+u	Desaturate
Invert	Ctrl+i	Invert
Default Colors	d	Default Colors
Switch Colors	x	Switch Colors
 
Layer
PHOTOSHOP	SHORTCUT	GIMP
New Layer	Shift+Ctrl+n	New Layer
Layer via Copy	Ctrl+j	Duplicate Layer
Bring (layer) to Front	Shift+Ctrl+]	Layer to Top
Send (layer) to Back	Shift+Ctrl+[	Layer to Bottom
Bring (layer) Forward	Ctrl+]	Raise Layer
Send (layer) Backward	Ctrl+[	Lower Layer
Select Top Layer	Shift+Alt+]	Select Top Layer
Select Bottom Layer	Shift+Alt+[	Select Bottom Layer
Select One Layer Forward	Alt+]	Select Previous Layer
Select One Layer Backward	Alt+[	Select Next Layer
Merge Down	Ctrl+e	Merge Down
Merge Visible	Shift+Ctrl+e	Merge Visible
Preserve Transparency	/	Keep Transparency
Cycle Modes Forwards	Shift+=	Next Layer Mode
Cycle Modes Backwards	Shift+-	Previous Layer Mode
 
Select
PHOTOSHOP	SHORTCUT	GIMP
Select All	Ctrl+a	Select All
Deselect	Ctrl+d	Select None
Inverse	Shift+Ctrl+i	Invert
Feather	Ctrl+Alt+d	Feather
 
View
PHOTOSHOP	SHORTCUT	GIMP
Zoom In	Ctrl+=	Zoom In
Zoom Out	Ctrl+-	Zoom Out
Fit on Screen	Ctrl+0	Zoom to Fit Window
Actual Pixels	Ctrl+Alt+0	Zoom 1:1
Show/Hide Extras	Ctrl+h	Toggle Show Selection (close enough?)
Show/Hide Guides	Ctrl+'	Toggle Show Guides
Show/Hide Grid	Ctrl+Alt+'	Toggle Show Grid
Show/Hide Rulers	Ctrl+r	Toggle Show Rulers
Snap	Ctrl+;	Snap to Guides
Scroll View Up	Page Up	Scroll Page Up
Scroll View Down	Page Down	Scroll Page Down
Scroll View Left	Ctrl+Page Up	Scroll Page Left
Scroll View Right	Ctrl+Page Down	Scroll Page Right
 
Window/Dialogs
PHOTOSHOP	SHORTCUT	GIMP
?	F5	Tools Dialog
Color Tab	F6	Colors Dialog
Layers Tab	F7	Layers Dialog
Info Tab	F8	Image Information
 
Tools
PHOTOSHOP	SHORTCUT	GIMP
Rectangular Marquee Tool	m	Rect Select Tool
Elliptical Marquee Tool	Shift+m	Ellipse Select Tool
 	*This is a toggle between 'Elliptical Marquee Tool' and 'Rectangular Marquee Tool' in Photoshop	 
Move Tool	v	Move Tool
Lasso Tool	l	Free Select Tool
Magic Wand Tool	w	Fuzzy Select Tool
Crop Tool	c	Crop &amp; Resize Tool
Airbrush Tool	j	Airbrush Tool
Paintbrush Tool	b	Paintbrush Tool
Clone Stamp Tool	s	Clone Stamp Tool
Eraser Tool	e	Eraser Tool
Gradient Tool	g	Blend Tool
Paint Bucket Tool	Shift+g	Bucket Fill Tool
 	*This is a toggle between 'Paint Bucket Tool' and 'Gradient Tool' in Photoshop	 
Blur Tool	r	Convolve Tool
Dodge Tool	o	DodgeBurn Tool
Type Tool	t	Text Tool
Pen Tool	p	Bezier Select Tool
Eye Dropper Tool	i	Color Picker Tool
Zoom Tool	z	Magnify Tool
Previous Brush	,	Previous Brush
Next Brush	.	Next Brush
First Brush	Shift+&lt;	First Brush
Last Brush	Shift+&gt;	Last Brush
Decrease Brush Size	[	Decrease Brush Size
Increase Brush Size	]	Increase Brush Size
Decrease Brush Hardness	{	Decrease Brush Hardness
Increase Brush Hardness	}	Increase Brush Hardness
 
Help
PHOTOSHOP	SHORTCUT	GIMP
Help	F1	Help
Context Help	Shift+F1	Context Help
 
Misc.
PHOTOSHOP	SHORTCUT	GIMP
Last Filter	Ctrl+f	Repeat Last Filter
?	Shift+Ctrl+f	Reshow Last Filter
Preferences	Ctrl+k	Preferences
Liquify	Shift+Ctrl+x	IWarp (close enough?)
Toggle Quick Mask	q	Toggle Quick Mask


Spotlights - triangle of white opaque shape

Cutting out and/or replacing unwanted background or features - select large areas with the selection option like the Magic Wand tool (aka Color Range) or the Lasso (quick and fast) with feather 2 to soften edge or the pen tool which adds points/lines/Bézier curves (better control but slower), hold down the shift button as you click to add extra points/areas of the subject matter to remove. Increase the tolerance to cover more areas. To subtract from your selection hold down alt as you're clicking. 
* Layer masks are a better way of working than Erase they clip (black hides/hidden white visible/reveal). Clone Stamp can be simulated by   and brushes for other areas. 
* Leave the fine details like hair, fur, etc. to later with lasso and the shift key to draw a line all the way around your subject. Gradient Mapping - Inverse - Mask. i.e. Refine your selected image with edge detection and using the radius and edge options / adjuster (increase/decrease contrast) so that you will capture more fine detail from the background allowing easier removal. 
Remove fringe/halo

saving image as png rather than jpg/jpeg to keep transparency background intact.


Implemented [http://colorizer.org/ colour model representations] [http://paulbourke.net/texture_colour/colourspace/ Mathematical approach] - Photo stills are spatially 2d (h and w), but are colorimetrically 3d (r g and b, or H L S, or Y U V etc.) as well. 
* RGB - split cubed mapped color model for photos and computer graphics hardware using the light spectrum (adding and subtracting) 
* YUV - Y-Lightness U-blue/yellow V-red/cyan (similar to YPbPr and YCbCr) used in the PAL, NTSC, and SECAM composite digital TV color [http://crewofone.com/2012/chroma-subsampling-and-transcoding/#comment-7299 video]


Histograms

White balanced (neutral) if the spike happens in the same place in each channel of the RGB graphs. If not, you're not balanced. 
If you have sky you'll see the blue channel further off to the right.

RGB is best one to change colours. These elements RGB is a 3-channel format containing data for Red, Green, and Blue in your photo scale between 0 and 255. The area in a picture that appears to be brighter/whiter contains more red color as compared to the area which is relatively darker. Similarly in the green channel the area that appears to be darker contains less amount of green color as compared to the area that appears to be brighter.  Similarly in the blue channel the area appears to be darker contains less amount of blue color as compared to the area that appears to be brighter. Brightness luminance histogram also matches the green histogram more than any other color - human eye interprets green better e.g. RGB rough ratio 15/55/30%

RGBA (RGB+A, A means alpha channel) .  The alpha channel is used for &quot;alpha compositing&quot;, which can mostly be associated as &quot;opacity&quot;.  AROS deals in RGB with two digits for every color (red, green, blue), in ARGB you have two additional hex digits for the alpha channel.

The shadows are represented by the left third of the graph.  The highlights are represented by the right third.  And the midtones are, of course, in the middle.  The higher the black peaks in the graph, the more pixels are concentrated in that tonal range (total black area). 
By moving the black endpoint, which identifies the shadows (darkness) and a white light endpoint (brightness) up and down either sides of the graph, colors are adjusted based on these points. 
By dragging the central one, can increased the midtones and control the contrast, raise shadows levels, clip or softly eliminate unsafe levels, alter gamma, etc... in a way that is much more precise and creative .


RGB Curves

* Move left endpoint (black point) up or right endpoint (white point) up brightens 
* Move left endpoint down or right endpoint down darkens

Color Curves

* Dragging up on the Red Curve increases the intensity of the reds in the image but 
* Dragging down on the Red Curve decreases the intensity of the reds and thus increases the apparent intensity of its complimentary color, cyan. Green’s complimentary color is magenta, and blue’s is yellow.
&lt;pre&gt;
 Red &lt;-&gt; Cyan
 Green &lt;-&gt;Magenta
 Blue &lt;-&gt;Yellow 
&lt;/pre&gt;

YUV Best option to analyse and pull out statistical elements of any picture (i.e.  separate luminance data from color data). The line in Y luma tone box represents the brightness of the image with the point in the bottom left been black, and the point in the top right as white.  A low-contrast image has a concentrated clump of values nearer to the center of the graph. By comparison, a high-contrast image has a wider distribution of values across the entire width of the Histogram.   A histogram that is skewed to the right would indicate a picture that is a bit overexposed because most of the color data is on the lighter side (increase exposure with higher value F), while a histogram with the curve on the left shows a picture that is underexposed. This is good information to have when using post-processing software because it shows you not only where the color data exists for a given picture, but also where any data has been clipped (extremes on edges of either side): that is, it does not exist and, therefore, cannot be edited.  By dragging the endpoints of the line and as well as the central one, can increased the dark/shadows, midtones and light/bright parts and control the contrast, raise shadows levels, clip or softly eliminate unsafe levels, alter gamma, etc... in a way that is much more precise and creative .

The U and V chroma parts show color difference components of the image. It’s useful for checking whether or not the overall chroma is too high, and also whether it’s being limited too much
Can be used to create a negative image but also 
With U (Cb), the higher value you are, the more you're on the blue primary color. If you go to the low values then you're on blue complementary color, i.e. yellow.
With V (Cr), this is the same principle but with Red and Cyan.
e.g. If you push U full blue and V full red, you get magenta. If you push U full yellow and V full Cyan then you get green.

YUV simultaneously adds to one side of the color equation while subtracting from the other.  
using YUV to do color correction can be very problematic because each curve alters the result of each other: the mutual influence between U and V often makes things tricky. You may also be careful in what you do to avoid the raise of noise (which happens very easily). Best results are obtained with little adjustments

sunset that looks uninspiring and needs some color pop especially for the rays over the hill, a subtle contrast raise while setting luma values back to the legal range without hard clipping.


Free royalty pictures, [www.freeimages.com ], [http://imageshack.us/ ], [http://photobucket.com/ ], [http://rawpixels.net/], [], [], [], 


====Lunapaint====

Pixel based drawing app with onion-skin animation function

 Blocking, Shading, Coloring, adding detail 

&lt;pre&gt;
b BRUSH
e ERASER

alt eyedropper 
v layer tool 

z ZOOM / MAGNIFY &lt; &gt; n 
spc panning 
m  marque 
q lasso 
w same color selection / region 
&lt;/pre&gt;

&lt;pre&gt;
, LM RM
v 
V
f  filter 
F 
.  size 

p 
,  pick color 
[] last / next color 
&lt;/pre&gt;


There is not much missing in Lunapaint to be as good as FlipBook and then you have to take into account that Flipbook is considered to be amongst the best and easiest to use animation software out there. Ok to be honest Flipbook has some nice features that require more heavy work but those aren't so much needed right away, things like camera effects, sound, smart fill, export to different movie file formats etc.

Tried Flipbook with my tablet and compared it to Luna. The feeling is the same when sketching. LunaPaint is very responsive/fluent to draw with. Just as Flipbook is, and that responsiveness is something its users have mentioned as one of the positive sides of said software.

 author was learning MUI. Some parts just have to be rewritten with proper MUI classes before new features can be added.

* add [Frame Add] / [Frame Del]
* whole animation feature is impossible to use. If you draw 2 color maybe but if you start coloring your cells then you get in trouble
* pickup the entire image as a brush, not just a selection ? And consequently remove the brush from memory when one doesn't need it anymore. can pick up a brush and put it onto a new image but cropping isn't possible, nor to load/save brushes.
* Undo is something I longed for ages in Lunapaint.
* to import into the current layer, other types of images (e.g. JPEG) besides RAW64.
* implement graphic tablet features support


**GENERAL DRAWING**

Miss it very much:
UNDO
ERASER
COLORPICKER - has to show on palette too which color got picked.
BACKGROUND COLOR -Possibility to select from &quot;New project screen&quot;

Miss it somewhat:
ICON for UNDO
ICON for ERASER
ICON for CLEAR SCREEN ( What can I say? I start over from scratch very often )
BRUSH - possibility to cut out as brush not just copy off image to brush

**ANIMATING**

Miss it very much:
NUMBER OF CELLS - Possibity to change total no. of cells during project
ANIM BRUSH - Possibility to pick up a selected part of cells into an animbrush

Miss it somewhat:
ADD/REMOVE FRAMES: Add/remove single frame

In general LunaPaint is really well done and it feels like a new DeluxePaint version. It works with my tablet. Sure there's much missing of course but things can always be added over time. So there is great potential in LunaPaint that's for sure. Animations could be made in it and maybe put together in QuickVideo, saving in .gif or .mng etc some day.


LAYERS
-Layers names don't get saved globally in animation frames
-Layers order don't change globally in an animation (perhaps as default?).

EXPORTING IMAGES
-Exporting frames to JPG/PNG gives problems with colors. (wrong colors. See my animatiopn --&gt; My robot was blue now it's &quot;gold&quot; ) I think this only happens if you have layers.
-Trying to flatten the layers before export doesn't work if you have animation frames only the one you have visible will flatten properly all other frames are destroyed. (Only one of the layers are visible on them)
-Exporting images filenames should be for example e.g. file0001, file0002...file0010 instead as of now file1, file2...file10

LOAD/SAVE (Preferences)
-Make a setting for the default &quot;Work&quot; folder.

* Destroyed colors if exported image/frame has layers 
* mystic color cycling of the selected color while stepping frames back/forth (annoying)

&lt;pre&gt;
Deluxe Paint II enhanced key shortcuts 
    NOTE: @ denotes the ALT key

    [Technique]

    F1  - Paint
    F2  - Single Colour
    F3  - Replace
    F4  - Smear
    F5  - Shade
    F6  - Cycle
    F7  - Smooth
     M  - Colour Cycle

    [Brush]

     B  - Restore
     O  - Outline
     h  - Halve brush size
     H  - Double brush size
     x  - Flip brush on X axis
     X  - Double brush size on X axis only
     y  - Flip on Y 
     Y  - Double on Y
     z  - Rotate brush 90 degrees
     Z  - Stretch

    [Stencil]

     `  - Stencil On

    [Miscellaneous]

    F9  - Info Bar
    F10 - Selection Bar
    @o  - Co-Ordinates
    @a  - Anti-alias
    @r  - Colourise
    @t  - Translucent
    TAB - Colour Cycle

    [Picture]

     L  - Load
     S  - Save
     j  - Page to Spare(Flip)
     J  - Page to Spare(Copy)
     V  - View Page
     Q  - Quit

    [General Keys]

     m  - Magnify
     &lt;  - Zoom In
     &gt;  - Zoom Out
     [  - Palette Colour Up
     ]  - Palette Colour Down
     (  - Palette Colour Left
     )  - Palette Colour Right
     ,  - Eye Dropper
     .  - Pixel / Brush Toggle
     /  - Symmetry
     |  - Co-Ordinates
    INS - Perspective Control
    +/- - Brush Size (Fine Control)
     w  - Unfilled Polygon
     W  - Filled Polygon
     e  - Unfilled Ellipse
     E  - Filled Ellipse
     r  - Unfilled Rectangle
     R  - Filled Rectangle
     t  - Type/text tool
     a  - Select Font
    u/U - Undo
     d  - Brush
     D  - Filled Non-Uniform Polygon
    f/F - Fill Options
    g/G - Grid
    h/H - Brush Size (Coarse Control)
     K  - Clear
     c  - Unfilled Circle
     C  - Filled Circle
     v  - Line
     b  - Scissor Select and Toggle
     B  - Brush
    {,} - Toggle between two background colours
&lt;/pre&gt;

====Lodepaint====

Pixel based painting artwork app

====Grafx2====

Pixel based painting artwork app aesprite like 

[https://www.youtube.com/watch?v=59Y6OTzNrhk aesprite workflow keys and tablet use], [], 


====Vector Graphics ZuneFIG====

Vector Image Editing of files .svg .ps .eps


*Objects - raise lower rotate flip aligning snapping 
*Path - unify subtract intersect exclude divide 
*Colour - fill stroke 
*Stroke - size 
*Brushes - 
*Layers - 
*Effects - gaussian bevels glows shadows 
*Text    - 
*Transform - 


 AmiFIG ([http://epb.lbl.gov/xfig/frm_introduction.html xfig manual]) 

[[File:MyScreen.png|thumb|left|alt=Showing all Windows open in AmiFIG.|All windows available to AmiFIG.]]

for drawing simple to intermediate vector graphic images for scientific and technical uses and for illustration purposes for those with talent

;Menu options
* Load - fig format but import(s) SVG
* Save - fig format but export(s) eps, ps, pdf, svg and png
* PAN = Ctrl + Arrow keys 
* Deselect all points

There is no selected object until you apply the tool, and the selected object is not highlighted.

;Metrics - to set up page and styles - first window to open on new drawings

;Tools - Drawing Primitives - set Attributes window first before clicking any Tools button(s) 
* Shapes - circles, ellipses, arcs, splines, boxes,  polygon 
* Lines - polylines
* Text &quot;T&quot; button 
* Photos - bitmaps
* Compound - Glue, Break, Scale 
* POINTs - Move, Add, Remove 
* Objects - Move, Copy, Delete, Mirror, Rotate, Paste 
use right mouse button to stop extra lines, shapes being formed and the left mouse to select/deselect tools button(s)
* Rotate - moves in 90 degree turns centered on clicked POINT of a polygon or square

;Attributes which provide change(s) to the above primitives 
* Color
* Line Width
* Line Style
* arrowheads

;Modes 
Choose from freehand, charts, figures, magnet, etc.

;Library - allows .fig clip-art to be stored 
* compound tools to add .fig(s) together

;FIG 3.2 [http://epb.lbl.gov/xfig/fig-format.html Format] as produced by xfig version 3.2.5 
&lt;pre&gt;
Landscape
Center
Inches
Letter 
100.00
Single
-2
1200 2
4 0 0 50 -1 0 12 0.0000 4 135 1050 1050 2475 This is a test.01
&lt;/pre&gt;

# change the text alignment within the textbox. I can choose left, center, or right aligned by either changing the integer in the second column from 0 (left) to 1 or 2 (center, or right). 
# The third integer in the row specifies fontcolor. For instance, 0 is black, but blue is 1 and Green3 is 13.
# The sixth integer in the bottom row specifies fontface. 0 is Times-Roman, but 16 is Helvetica (a MATLAB default).
# The seventh number is fontsize. 12 represents a 12pt fontsize. Changing the fontsize of an item really is as easy as changing that number to 20.
# The next number is the counter-clockwise angle of the text. Notice that I have changed the angle to .7854 (pi/4 rounded to four digits=45 degrees).
# twelfth number is the position according to the standard “x-axis” in Xfig units from the left. Note that 1200 Xfig units is equivalent to once inch.
# thirteenth number is the “y-position” from the top using the same unit convention as before.

* The nested text string is what you entered into the textbox.
* The “01″ present at the end of that line in the .fig file is the closing tag. For instance, a change to \100 appends a @ symbol at the end of the period of that sentence.

; Just to note there are no layers, no 3d functions, no shading, no transparency, no animation


[[#top|...to the top]]

===Audio===


# AHI uses linear panning/balance, which means that in the center, you will get -6dB. If an app uses panning, this is what you will get. Note that apps like Audio Evolution need panning, so they will have this problem.

# When using AHI Hifi modes, mixing is done in 32-bit and sent as 32-bit data to the driver. The Envy24HT driver uses that to output at 24-bit (always).

# For the Envy24/Envy24HT, I've made 16-bit and 24-bit inputs (called Line-in 16-bit, Line-in 24-bit etc.). There is unfortunately no app that can handle 24-bit recording.


====Music Mods====

Digital module (mods) trackers are music creation software using samples and sometimes soundfonts, audio plugins (VST, AU or RTAS), MIDI.

Generally, MODs are similar to MIDI in that they contain note on/off and other sequence messages that control the mod player. Unlike (most) midi files, however, they also contain sound samples that the sequence information actually plays. MOD files can have many channels (classic amiga mods have 4, corresponding to the inbuilt sound channels), but unlike MIDI, each channel can typically play only one note at once. However, since that note might be a sample of a chord, a drumloop or other complex sound, this is not as limiting as it sounds.

Like MIDI, notes will play indefinitely if they're not instructed to end. Most trackers record this information automatically if you play your music in live. If you're using manual note entry, you can enter a note-off command with a keyboard shortcut - usually Caps Lock.

In fact when considering file size MOD is not always the best option. Even a dummy song wastes few kilobytes for nothing when a simple SID tune could be few hundreds bytes and not bigger than 64kB. AHX is another small format, AHX tunes are never larger than 64kB excluding comments.

[https://www.youtube.com/watch?v=rXXsZfwgil Protrekkr] (previously aka [w:Juan_Antonio_Arguelles_Rius|NoiseTrekkr])

If Protrekkr does not start, please check if the Unit 0 has been setup in the AHI prefs and still not, go to the directory utilities/protrekkr and double click on the Protrekkr icon

*Sample
*Note - Effect 
*Track (column) - Pattern - Order

It all starts with the Sample which is used to create Note(s) in a Track (column of a tracker) 
The Note can be changed with an Effect.  A Track of Note(s) can be collected into a Pattern (section of a song) and these can be given Order to create the whole song.

Patience (notes have to be entered one at a time) or playing the bassline on a midi controller (faster - see midi section above).  Best approach is to wait until a melody popped into your head.

*Up-tempo means the track should be reasonably fast, but not super-fast. 
*Groovy and funky imply the track should have some sort of &quot;swing&quot; feel, with plenty of syncopation or off beat emphasis and a recognizable, melodic bass line. 
*Sweet and happy mean upbeat melodies, a major key and avoiding harsh sounds.
*Moody - minor key

First, create a quick bass sound, which is basically a sine wave, but can be hand drawn for a little more variance. It could also work for the melody part, too.

This is usually a bass guitar or some kind of synthesizer bass. The bass line is often forgotten by inexperienced composers, but it plays an important role in a musical piece. Together with the rhythm section the bass line forms the groove of a song. It's the glue between the rhythm section and the melodic layer of a song.

The drums are just pink noise samples, played at different frequencies to get a slightly different sound for the kick, snare, and hihats.

Instruments that fall into the rhythm category are bass drums, snares, hi-hats, toms, cymbals, congas, tambourines, shakers, etc. Any percussive instrument can be used to form part of the rhythm section.

The lead is the instrument that plays the main melody, on top of the chords. There are many instruments that can play a lead section, like a guitar, a piano, a saxophone or a flute. The list is almost endless. There is a lot of overlap with instruments that play chords. Often in one piece an instrument serves both roles. The lead melody is often played at a higher pitch than the chords.

Listened back to what was produced so far, and a counter-melody can be imagined, which can be added with a triangle wave.

To give the ends of phrases some life, you can add a solo part with a crunchy synth. By hitting random notes in the key of G, then edited a few of them.

For the climax of the song, filled out the texture with a gentle high-pitch pad… …and a grungy bass synth.


The arrow at A points at the pattern order list. As you see, the patterns don't have to be in numerical order. This song starts with pattern &quot;00&quot;, then pattern &quot;02&quot;, then &quot;03&quot;, then &quot;01&quot;, etcetera. Patterns may be repeated throughout a song.

The B arrow points at the song title. Below it are the global BPM and speed parameters. These determine the tempo of the song, unless the tempo is altered through effect commands during the song.

The C arrow points at the list of instruments. An instrument may consist of multiple samples. Which sample will be played depends on the note. This can be set in the Instrument Editing screen. Most instruments will consist of just one sample, though. The sample list for the selected instrument can be found under arrow D.

Here's a part of the main editing screen. This is where you put in actual notes. Up to 32 channels can be used, meaning 32 sounds can play simultaneously. The first six channels of pattern &quot;03&quot; at order &quot;02&quot; are shown here. The arrow at A points at the row number. The B arrow points at the note to play, in this case a C4. The column pointed at by the C arrow tells us which instrument is associated with that note, in this case instrument #1 &quot;Kick&quot;.

The column at D is used (mainly) for volume commands. In this case it is left empty which means the instrument should play at its default volume. You can see the volume column being used in channel #6.

The E column tells us which effect to use and any parameters for that effect. In this case it holds the &quot;F&quot; effect, which is a tempo command. The &quot;04&quot; means it should play at tempo 4 (a smaller number means faster).

Base pattern

When I create a new track I start with what I call the base pattern. It is worthwhile to spend some time polishing it as a lot of the ideas in the base pattern will be copied and used in other patterns. At least, that's how I work. Every musician will have his own way of working. In &quot;Wild Bunnies&quot; the base pattern is pattern &quot;03&quot; at order &quot;02&quot;.

In the section about selecting samples I talked about the four different categories of instruments: drums, bass, chords and leads. That's also how I usually go about making the base pattern. I start by making a drum pattern, then add a bass line, place some chords and top it off with a lead. This forms the base pattern from which the rest of the song will grow.


Drums

Here's a screenshot of the first four rows of the base pattern. I usually reserve the first four channels or so for the drum instruments. Right away there are a couple of tricks shown here. In the first channel the kick, or bass drum, plays some notes. Note the alternating F04 and F02 commands. The &quot;F&quot; command alters the tempo of the song and by quickly alternating the tempo; the song will get some kind of &quot;swing&quot; feel.

In the second channel the closed hi-hat plays a fairly simple pattern. Further down in the channel, not shown here, some open hi-hat notes are added for a bit of variation.

In the third and fourth channel the snare sample plays. The &quot;8&quot; command is for panning. One note is panned hard to the left and the other hard to the right. One sample is played a semitone lower than the other. This results in a cool flanging effect. It makes the snare stand out a little more in the mix.


Bass line

There are two different instruments used for the bass line. Instrument #6 is a pretty standard synthesized bass sound. Instrument #A sounds a bit like a slap bass when used with a quick fade out. By using two different instruments the bass line sounds a bit more ”human”. The volume command is used to cut off the notes. However, it is never set to zero. Setting the volume to a very small value will result in a reverb-like effect. This makes the song sound more &quot;live&quot;.

The bass line hints at the chords that will be played and the key the song will be in. In this case the key of the song is D-major, a positive and happy key.


Chords

The D major chords that are being played here are chords stabs; short sounds with a quick decay (fade out). Two different instruments (#8 and #9) are used to form the chords. These instruments are quite similar, but have a slightly different sound, panning and volume decay. Again, the reason for this is to make the sound more human. The volume command is used on some chords to simulate a delay, to achieve more of a live feel. The chords are placed off-beat making for a funky rhythm.


Lead

Finally the lead melody is added. The other instruments are invaluable in holding the track together, but the lead melody is usually what catches people's attention.

A lot of notes and commands are used here, but it looks more complex than it is. A stepwise ascending melody plays in channel 13. Channel 14 and 15 copy this melody, but play it a few rows later at a lower volume. This creates an echo effect. A bit of panning is used on the notes to create some stereo depth. Like with the bass line, instead of cutting off notes the volume is set to low values for a reverb effect. The &quot;461&quot; effect adds a little vibrato to the note, which sounds nice on sustained notes.

Those paying close attention may notice the instrument used here for the lead melody is the same as the one used for the bass line (#6 &quot;Square&quot;), except played two or three octaves higher. This instrument is a looped square wave sample. Each type of wave has its own quirks, but the square wave (shown below) is a really versatile wave form.

Song structure

Good, catchy songs are often carefully structured into sections, some of which are repeated throughout the song with small variations.

A typical pop-song structure is: Intro - Verse - Chorus - Verse - Chorus - Bridge - Chorus.

Other single sectional song structures are

&lt;pre&gt;
Strophic or AAA Song Form - oldest story telling with refrain (often title of the song) repeated in every verse section melody 
AABA Song Form - early popular, jazz and gospel fading during the 1960s 
AB or Verse/Chorus Song Form - songwriting format of choice for modern popular music since the 1960s 
Verse/Chorus/Bridge Song Form
ABAB Song Form
ABAC Song Form
ABCD Song Form
AAB 12-Bar Song Form - three four-bar lines or sub-sections 
8-Bar Song Form
16-Bar Song Form
Hybrid / Compound Song Forms
&lt;/pre&gt;

The most common building blocks are:

#INTRODUCTION(INTRO)
#VERSE
#REFRAIN
#PRE-CHORUS / RISE / CLIMB
#CHORUS
#BRIDGE
#MIDDLE EIGHT
#SOLO / INSTRUMENTAL BREAK
#COLLISION
#CODA / OUTRO
#AD LIB (OFTEN IN CODA / OUTRO)

The chorus usually has more energy than the verse and often has a memorable melody line. As the chorus is repeated the most often during the song, it will be the part that people will remember.

The bridge often marks a change of direction in the song. It is not uncommon to change keys in the bridge, or at least to use a different chord sequence. The bridge is used to build up tension towards the big finale, the last repetition of chorus.


 Playing

RCTRL:                           Play song from row 0.

LSHIFT + RCTRL:                  Play song from current row.

RALT:                            Play pattern from row 0.

LSHIFT + RALT:                   Play pattern from current row.

Left mouse on '&gt;':               Play song from row 0.

Right mouse on '&gt;':              Play song from current row.

Left mouse on '|&gt;':              Play pattern from row 0.

Right mouse on '|&gt;':             Play pattern from current row.

Left mouse on 'Edit/Record':     Edit mode on/off.

Right mouse on 'Edit/Record':    Record mode on/off.


 Editing 


LSHIFT + ESCAPE:                 Switch large patterns view on/off

TAB:                    Go to next track

LSHIFT + TAB:                    Go to prev. track

LCTRL + TAB:                    Go to next note in track

LCTRL + LSHIFT + TAB:           Go to prev. note in track

SPACE:                           Toggle Edit mode On &amp; Off

(Also stop if the song is being played)

SHIFT SPACE:                     Toggle Record mode On &amp; Off

(Wait for a key note to be pressed

or a midi in message to be received)

DOWN ARROW:                      1 Line down

UP ARROW:                        1 Line up

LEFT ARROW:                      1 Row left

RIGHT ARROW:                     1 Row right

PREV. PAGE:                      16 Arrows Up

NEXT PAGE:                       16 Arrows Down

HOME / END:                      Top left / Bottom right of pattern

LCTRL + HOME / END:              First / last track

F5, F6, F7, F8, F9:              Jump to 0, 1/4, 2/4, 3/4, 4/4 lines of the patterns

+ - (Numeric keypad):           Next / Previous pattern

LCTRL + LEFT / RIGHT:           Next / Previous pattern

LCTRL + LALT + LEFT / RIGHT:    Next / Previous position

LALT + LEFT / RIGHT:           Next / Previous instrument

LSHIFT + M:                      Toggle mute state of the current channel

LCTRL + LSHIFT + M:             Solo the current track / Unmute all

LSHIFT + F1 to F11:              Select a tab/panel

LCTRL + 1 to 4:                 Select a copy buffer


 Tracking 

1st and 2nd keys rows:           Upper octave row

3rd and 4th keys rows:           Lower octave row

RSHIFT:                          Insert a note off

/ and * (Numeric keypad)

or F1 F2:                        -1 or +1 octave

INSERT / BACKSPACE:              Insert or Delete a line in current track

or current selected block.

LSHIFT + INSERT / BACKSPACE:     Insert or Delete a line in current pattern

DELETE (NOT BACKSPACE):          Empty a column or a selected block.


 Blocks

(Blocks can also be selected with the mouse by holding the right button and scrolling the pattern with the mouse wheel).


LCTRL + A:          Select entire current track

LCTRL + LSHIFT + A: Select entire current pattern

LALT + A:          Select entire column note in a track

LALT + LSHIFT + A: Select all notes of a track

LCTRL + X:          Cut the selected block and copy it into the block-buffer

LCTRL + C:          Copy the selected block into the block-buffer

LCTRL + V:          Paste the data from the block buffer into the pattern

LCTRL + I:          Interpolate selected data from the first to the last row of a selection

LSHIFT + ARROWS

PREV. PAGE

NEXT PAGE: Select a block

LCTRL + R:          Randomize the select columns of a selection, works similar to CTRL + I (interpolating them)

LCTRL + U:          Transpose the note of a selection to 1 seminote higher

LCTRL + D:          Transpose the note of a selection to 1 seminote lower

LCTRL + LSHIFT + U: Transpose the note of a selection to 1 seminote higher (only for the current instrument)

LCTRL + LSHIFT + D: Transpose the note of a selection to 1 seminote lower  (only for the current instrument)

LCTRL + H:          Transpose the note of a selection to 1 octave higher

LCTRL + L:          Transpose the note of a selection to 1 octave lower

LCTRL + LSHIFT + H: Transpose the note of a selection to 1 octave higher (only for the current instrument)

LCTRL + LSHIFT + L: Transpose the note of a selection to 1 octave lower (only for the current instrument)

LCTRL + W:          Save the current selection into a file


 Misc 


LALT + ENTER:     Switch between full screen / windowed mode

LALT + F4:        Exit program (Windows only)

LCTRL + S:         Save current module

LSHIFT + S:         Switch top right panel to synths list

LSHIFT + I:         Switch top right panel to instruments list


&lt;pre&gt;
C-x   xh xx xx hhhh             Volume 
B-x   xh xx xx hhhh             Jump to 
A#x  xh xx xx hhhh hhhh   Slide 
F-x    xh xx xx hhhh            Tempo 
D-x   xh xx xx hhhh             Pattern Break 
G#x  xh xx xx hhhh
&lt;/pre&gt;

h Hex 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13

d Dec 01 02 03 04 05 06 07 08 09 10  11 12 13 14 15 16 17 18 19

The Set Volume command: C. Input a note, then move the cursor to the effects command column and type a C. Play the pattern, and you shouldn't be able to hear the note you placed the C by. This is because the effect parameters are 00. Change the two zeros to a 40(Hex)/64(Dec), depending on what your tracker uses. Play back the pattern again, and the note should come in at full volume.

The Position Jump command next. This is just a B followed by the position in the playing list that you want to jump to. One thing to remember is that the playing list always starts at 0, not 1. This command is usually in Hex.

Onto the volume slide command: A. This is slightly more complex (much more if you're using a newer tracker, if you want to achieve the results here, then set slides to Amiga, not linear), due to the fact it depends on the secondary tempo. For now set a secondary tempo of 06 (you can play around later), load a long or looped sample and input a note or two. A few rows after a note type in the effect command A. For the parameters use 0F. Play back the pattern, and you should notice that when the effect kicks in, the sample drops to a very low volume very quickly. Change the effect parameters to F0, and use a low volume command on the note. Play back the pattern, and when the slide kicks in the volume of the note should increase very quickly.
This because each part of the effect parameters for command A does a different thing. The first number slides the volume up, and the second slides it down. It's not recommended that you use both a volume up and volume down at the same time, due to the fact the tracker only looks for the first number that isn't set to 0. If you specify parameters of 8F, the tracker will see the 8, ignore the F, and slide the volume up. Using a slide up and down at same time just makes you look stupid. Don't do it...

The Set Tempo command: F, is pretty easy to understand. You simply specify the BPM (in Hex) that you want to change to. One important thing to note is that values of lower than 20 (Hex) sets the secondary tempo rather than the primary.

Another useful command is the Pattern Break: D. This will stop the playing of the current pattern and skip to the next one in the playing list. By using parameters of more than 00 you can also specify which line to begin playing from.

Command 3 is Portamento to Note. This slides the currently playing note to another note, at a specified speed. The slide then stops when it reaches the desired note. 
&lt;pre&gt;
   C-2 1 000 - Starts the note playing
   ---      000
   C-3    330 - Starts the slide to C-3 at a speed of 30.
   ---     300 - Continues the slide
   ---     300 - Continues the slide
&lt;/pre&gt;
Once the parameters have been set, the command can be input again without any parameters, and it'll still perform the same function unless you change the parameters. This memory function allows certain commands to function correctly, such as command 5, which is the Portamento to Note and Volume Slide command. Once command 3 has been set up command 5 will simply take the parameters from that and perform a Portamento to Note. Any parameters set up for command 5 itself simply perform a Volume Slide identical to command A at the same time as the Portamento to Note.

This memory function will only operate in the same channel where the original parameters were set up.
There are various other commands which perform two functions at once. They will be described as we come across them.

C-3  04  ..  ..  09  00 ---&gt; C-3  04  ..  ..  09  00

C-3  04  ..  ..  09  00 ---&gt; C-3  04  ..  ..  09  02

C-3  04  ..  ..  09  00 ---&gt; C-3  04  ..  ..  09  05

C-3  04  ..  ..  09  00 ---&gt; C-3  04  ..  ..  09  08

C-3  04  ..  ..  09  00 ---&gt; C-3  04  ..  ..  09  0A

C-3  04  ..  ..  09  00 ---&gt; C-3  04  ..  ..  09  0D

C-3  04  ..  ..  09  10 ---&gt; C-3  04  ..  ..  09  10

(You can also switch on the Slider Rec to On, and perform parameter-live-recording, such as cutoff transitions, resonance or panning tweaking, etc..)  Note: this command only works for volume/panning and fx datas columns.


The next command we'll look at is the Portamento up/down: 1 and 2. Command 1 slides the pitch up at a specified speed, and 2 slides it down. This command works in a similar way to the volume slide, in that it is dependent on the secondary tempo. Both these commands have a memory dependent on each other, if you set the slide to a speed of 3 with the 1 command, a 2 command with no parameters will use the speed of 3 from the 1 command, and vice versa.

Command 4 is Vibrato. Vibrato is basically rapid changes in pitch, just try it, and you'll see what I mean. Parameters are in the format of xy, where x is the speed of the slide, and y is the depth of the slide. One important point to remember is to keep your vibratos subtle and natural so a depth of 3 or less and a reasonably fast speed, around 8, is usually used. Setting the depth too high can make the part sound out of tune from the rest.
Following on from command 4 is command 6. This is the Vibrato and Volume Slide command, and it has a memory like command 5, which you already know how to use.

Command 7 is Tremolo. This is similar to vibrato. Rather than changing the pitch it slides the volume. The effect parameters are in exactly the same format.   vibrato effect (0x1dxy) x = speed y = depth (can't be used if arpeggio (0x1b) is turned on) 

&lt;pre&gt;
 C-7 00 .. .. 1B37 &lt;-  Turn Arpeggio effect on
  --- .. .. .. 0000
  --- .. .. .. 0000
  --- .. .. .. 0000
  --- .. .. .. 1B38 &lt;- Change datas
  --- .. .. .. 0000
  --- .. .. .. 0000
  --- .. .. .. 0000
  --- .. .. .. 1B00 &lt;- Turn it off
&lt;/pre&gt;

Command 9 is Sample Offset. This starts the playback of the sample from a different place than the start. The effect parameters specify the sample offset, but only very roughly. Say you have a sample which is 8765(Hex) bytes long, and you wanted it to play from position 4321(Hex). The effect parameter could only be as accurate as the 43 part, and it would ignore the 21.

Command B is the Playing List/Order Jump command. The parameters specify the position in the Playing List/Order to jump to. When used in conjunction with command D you can specify the position and the line to play from.

Command E is pretty complex, as it is used for a lot of different things, depending on what the first parameter is. Let's take a trip through each effect in order.
Command E0 controls the hardware filter on an Amiga, which, as a low pass filter, cuts off the highest frequencies being played back. There are very few players and trackers on other system that simulate this function, not that you should need to use it. The second parameter, if set to 1, turns on the filter. If set to 0, the filter gets turned off.

Commands E1/E2 are Fine Portamento Up/Down. Exactly the same functions as commands 1/2, except that they only slide the pitch by a very small amount. These commands have a memory the same as 1/2 as well.

Command E3 sets the Glissando control. If parameters are set to 1 then when using command 3, any sliding will only use the notes in between the original note and the note being slid to. This produces a somewhat jumpier slide than usual. The best way to understand is to try it out for yourself. Produce a slow slide with command 3, listen to it, and then try using E31.

Command E4 is the Set Vibrato Waveform control. This command controls how the vibrato command slides the pitch. Parameters are 0 - Sine, 1 - Ramp Down (Saw), 2 - Square. By adding 4 to the parameters, the waveform will not be restarted when a new note is played e.g. 5 - Sine without restart.

Command E5 sets the Fine Tune of the instrument being played, but only for the particular note being played. It will override the default Fine Tune for the instrument. The parameters range from 0 to F, with 0 being -8 and F being +8 Fine Tune. A parameter of 8 gives no Fine Tune. If you're using a newer tracker that supports more than -8 to +8 e.g. -128 to +128, these parameters will give a rough Fine Tune, accurate to the nearest 16.

Command E6 is the Jump Loop command. You mark the beginning of the part of a pattern that you want to loop with E60, and then specify with E6x the end of the loop, where x is the number of times you want it to loop.

Command E7 is the Set Tremolo Waveform control. This has exactly the same parameters as command E4, except that it works for Tremolo rather than Vibrato.

Command E9 is for Retriggering the note quickly. The parameter specifies the interval between the retrigs. Use a value of less than the current secondary tempo, or else the note will not get retrigged.

Command EA/B are for Fine Volume Slide Up/Down. Much the same as the normal Volume Slides, except that these are easier to control since they don't depend on the secondary tempo. The parameters specify the amount to slide by e.g. if you have a sample playing at a volume of 08 (Hex) then the effect EA1 will slide this volume to 09 (Hex). A subsequent effect of EB4 would slide this volume down to 05 (Hex).

Command EC is the Note Cut. This sets the volume of the currently playing note to 0 at a specified tick. The parameters should be lower than the secondary tempo or else the effect won't work.

Command ED is the Note Delay. This should be used at the same time as a note is to be played, and the parameters will specify the number of ticks to delay playing the note. Again, keep the parameters lower than the secondary tempo, or the note won't get played!

Command EE is the Pattern Delay. This delays the pattern for the amount of time it would take to play a certain number of rows. The parameters specify how many rows to delay for.

Command EF is the Funk Repeat command. Set the sample loop to 0-1000. When EFx is used, the loop will be moved to 1000- 2000, then to 2000-3000 etc. After 9000-10000 the loop is set back to 0- 1000. The speed of the loop &quot;movement&quot; is defined by x. E is two times as slow as F, D is three times as slow as F etc. EF0 will turn the Funk Repeat off and reset the loop (to 0-1000).

effects 0x41 and 0x42 to control the volumes of the 2 303 units

There is a dedicated panel for synth parameter editing with coherent sections (osc, filter modulation, routing, so on) the interface is much nicer, much better to navigate with customizable colors, the reverb is now customizable (10 delay lines), It accepts newer types of Waves (higher bit rates, at least 24). Has a replay routine.

It's pretty much your basic VA synth. The problem isn't with the sampler being to high it's the synth is tuned two octaves too low, but if you want your samples tuned down just set the base note down 2 octaves (in the instrument panel).

so the synth is basically divided into 3 sections from left to right: oscillators/envelopes, then filter and LFO's, and in the right column you have mod routings and global settings.

for the oscillator section you have two normal oscillators (sine, saw, square, noise), the second of which is tunable, the first one tunes with the key pressed. Attached to OSC 1 is a sub-oscillator, which is a sawtooth wave tuned one octave down. The phase modulation controls the point in the duty cycle at which the oscillator starts. The ADSR envelope sliders (grouped with oscs) are for modulation envelope 1 and 2 respectively. you can use the synth as a sampler by choosing the instrument at the top.

In the filter column, the filter settings are: 1 = lowpass, 2 = highpass, 3 = off. cutoff and resonance. For the LFOs they are LFO 1 and LFO 2, the ADSR sliders in those are for the LFO itself.

For the modulation routings you have ENV 1, LFO 1 for the first slider and ENV 2, LFO 2 for the second, you can cycle through the individual routings there, and you can route each modulation source to multiple destinations of course, which is another big plus for this synth. Finally the glide time is for portamento and master volume, well, the master volume... it can go quite loud.

The sequencer is changed too, It's more like the one in AXS if you've used that, where you can mute tracks to re-use patterns with variation.


&lt;pre&gt;
Support for the following modules formats:
669 (Composer 669, Unis 669), 
AMF (DSMI Advanced Module Format), 
AMF (ASYLUM Music Format V1.0), 
APUN (APlayer), DSM (DSIK internal format), 
FAR (Farandole Composer), 
GDM (General DigiMusic), 
IT (Impulse Tracker), 
IMF (Imago Orpheus), 
MOD (15 and 31 instruments), 
MED (OctaMED), 
MTM (MultiTracker Module editor), 
OKT (Amiga Oktalyzer), 
S3M (Scream Tracker 3), 
STM (Scream Tracker), 
STX (Scream Tracker Music Interface Kit), 
ULT (UltraTracker), 
UNI (MikMod), 
XM (FastTracker 2),
Mid (midi format via timidity)
&lt;/pre&gt;


Possible plugin options include [http://lv2plug.in/ LV2],


====Midi - Musical Instrument Digital Interface====

A midi file typically contains music that plays on up to 16 channels (as per the midi standard), but many notes can simultaneously play on each channel (depending on the limit of the midi hardware playing it).

'''Timidity'''

Although usually already installed, you can uncompress the [http://www.libsdl.org/projects/SDL_mixer/ timidity.tar.gz (14MB)] into a suitable drawer like below's SYS:Extras/Audio/ 
 assign timidity: SYS:Extras/Audio/timidity
added to SYSːs/User-Startup

'''WildMidi playback'''


'''Audio Evolution 4 (2003) 4.0.23 (from 2012)'''


*Sync Menu    - CAMD Receive, Send checked 
*Options Menu - MIDI Machine Control - Midi Bar Display - Select CAMD MIDI in / out - Midi Remote Setup 


MCB Master Control Bus 
*Sending a MIDI start-command and a Song Position Pointer, you can synchronize audio with an external MIDI sequencer (like B&amp;P). 
*B&amp;P Receive, start AE, add AudioEvolution.ptool in Bars&amp;Pipes track, press play / record in AE then press play in Pipes 
*CAMD Receive, receive MIDI start or continue commands via camd.library sync to AE 


*MIDI Machine Control
*Midi Bar Display 
*Select CAMD MIDI in / out
*Midi Remote Setup - open requester for external MIDI controllers to control app mixer and transport controls cc remotely 
 Channel   - mixer(vol, pan, mute, solo), eq, aux, fx, 
 Subgroup  - Volume, Mute, Solo 
 Transport - Start, End, Play, Stop, Record, Rewind, Forward 
 Misc      - Master vol., Bank Down, Bank up 


&lt;pre&gt;
q        - quit 

First 3 already opened when AE started 
F1       - timeline window
F2       - mixer 
F3       - control 
F4       - subgroups 
F5       - aux returns 
F6       - sample list 

i        - Load sample to use 

space    - start/stop play 
b        - reset time 0:00


s        - split mode 
r        - open recording window 
a        - automation edit mode with p panning, m mute and v volume 


[ / ]    - zoom in / out 
:        - previous track
*        - next track 

x c v f  - cut copy paste cross-fade 
g        - snap grid 


&lt;/pre&gt;


 '''[http://bnp.hansfaust.de/ Bars n Pipes sequencer]'''

 BarsnPipes debug ... in shell 

Menu (right mouse)  
*Song        - Songs load and save in .song format but option here to load/save Midi_Files .mid in FORMAT0 or FORMAT1 
*Track       - 
*Edit        -
*Tool        - 
*Timing      - SMTPE Synchronizing 
*Windows     - 
*Preferences - Multiple MIDI-in option 

Windows (some of these are usually already opened when Bars n Pipes starts up for the first time) 
*Workflow -&gt; Tracks, .... Song Construction, Time-line Scoring, Media Madness, Mix Maestro, 
*Control  -&gt; Transport (or mini one), Windows (which collects all the Windows icons together-shortcut), .... Toolbox, Accessories, Metronome, 

Once you have your windows placed on the screen that suits your workflow, Song -&gt; Save as Default will save the positions, colors, icons, etc as you'd like them 

If you need a particular setup of Tracks, Tools, Tempos etc, you save them all as a new song you can load each time 

Right mouse menu -&gt; Preferences -&gt; Environment... -&gt; ScreenMode  - Linkages for Synch (to Slave) usbmidi.out.0 and Send (Master) usbmidi.in.0 - Clock MTC 


'''Tracks'''

#Double-click on B&amp;P's icon. B&amp;P will then open with an empty Song. You can also double-click on a song icon to open a song in B&amp;P.
#Choose a track. The B&amp;P screen will contain a Tracks Window with a number of tracks shown as pipelines (Track 1, Track 2, etc...). To choose a track, simply click on the gray box to show an arrow-icon to highlight it. This icon show whether a track is chosen or not. To the right of the arrow-icon, you can see the icon for the midi-input. If you double-click on this icon you can change the MIDI-in setup.
#Choose Record for the track. To the right of the MIDI-input channel icon you can see a pipe. This leads to another clickable icon with that shows either P, R or M. This stands for Play, Record or Merge. To change the icon, simply click on it. If you choose P, this track can only play the track (you can't record anything). If you choose R, you can record what you play and it overwrites old stuff in the track. If you choose M, you merge new records with old stuff in the track. Choose R now to be able to make a record.
#Chose MIDI-channel. On the most right part of the track you can see an icon with a number in it. This is the MIDI-channel selector. Here you must choose a MIDI-channel that is available on your synthesizer/keyboard. If you choose General MIDI channel 10, most synthesizer will play drum sounds. To the left of this icon is the MIDI-output icon. Double-click on this icon to change the MIDI-output configuration.
#Start recording. The next step is to start recording. You must then find the control buttons (they look like buttons on a CD-player). To be able to make a record. you must click on the R icon. You can simply now press the play button (after you have pressed the R button) and play something on you keyboard. To playback your composition, press the Play button on the control panel.
#Edit track. To edit a track, you simply double click in the middle part of a track. You will then get a new window containing the track, where you can change what you have recorded using tools provided. Take also a look in the drop-down menus for more features.


Videos to help understand [https://www.youtube.com/watch?v=A6gVTX-9900 small intro], [https://www.youtube.com/watch?v=abq_rUTiSA4&amp;t=3s Overview], [https://www.youtube.com/watch?v=ixOVutKsYQo Workplace Setup CC PC Sysex], [https://www.youtube.com/watch?v=dDnJLYPaZTs Import Song], [https://www.youtube.com/watch?v=BC3kkzPLkv4 Tempo Mapping], [https://www.youtube.com/watch?v=sd23kqMYPDs ptool Arpeggi-8], [https://www.youtube.com/watch?v=LDJq-YxgwQg  PlayMidi Song], [https://www.youtube.com/watch?v=DY9Pu5P9TaU Amiga Midi], [https://www.youtube.com/watch?v=abq_rUTiSA4 Learning Amiga bars and Pipes], 

Groups like [https://groups.io/g/barsnpipes/topics this] could help 


'''Tracks window'''

* blue &quot;1 2 3 4 5 6 7 8 Group&quot; and transport tape deck VCR-type controls
* Flags 
* [http://theproblem.alco-rhythm.com/org/bp.html Track 1, Track2, to Track 16, on each Track there are many options that can be activated] 

Each Track has a 

*Left LHS  - Click in grey box to select what Track to work on, Midi-In ptool icon should be here (5pin plug icon), and many more from the Toolbox on the Input Pipeline 
*Middle    - (P, R, M) Play, Record, Merge/Multi before the sequencer line and a blue/red/yellow (Thru Mute Play) Tap 
*Right RHS - Output pipeline, can have icons placed uopn it with the final ptool icon(s) being the 5pin icon symbol for Midi-OUT 

Clogged pipelines may need Esc pressed several times 


'''Toolbox (tools affect the chosen pipeline)'''

After opening the Toolbox window you can add extra Tools (.ptool) for the pipelines like keyboard(virtual), midimonitor, quick patch, transpose, triad, (un)quantize, feedback in/out, velocity etc
 right mouse -&gt; Toolbox menu option -&gt; Install Tool... and navigate to Tool drawer (folder) and select requried .ptool 

Accompany B tool to get some sort of rythmic accompaniment, Rythm Section and Groove Quantize are examples of other tools that make use of rythms
[https://aminet.net/search?query=bars Bars &amp; Pipes pattern format .ptrn] for drawer (folder). Load from the Menu as Track or Group 


'''Accessories (affect the whole app)''' 

Accessories -&gt; Install... and goto the Accessories drawer for .paccess like adding ARexx scripting support 


'''Song Construction'''
&lt;pre&gt;
F1  Pencil
F2  Magic Wand
F3  Hand 
F4  Duplicator 
F5  Eraser 
F6  Toolpad 
F7  Bounding box 
F8  Lock to A-B-A 

A-B-A strip, section, edit flags, white boxes, 

&lt;/pre&gt;


Bars&amp;Pipes Professional offers three track formats; basic song tracks, linear tracks — which don't loop — and finally real‑time tracks. The difference between them is that both song and linear tracks respond to tempo changes, while real‑time tracks use absolute timing, always trigger at the same instant regardless of tempo alterations 

'''Tempo Map'''

F1  Pencil
F2  Magic Wand
F3  Hand 
F4  Eraser 
F5  Curve 
F6  Toolpad 


Compositions

Lyrics, Key, Rhythm, Time Signature 

'''Master Parameters'''

Key, Scale/Mode

'''Track Parameters'''

Dynamics 


'''Time-line Scoring'''


'''Media Madness'''


'''Mix Maestro'''


*ACCESSORIES         Allows the importation of other packages and additional modules 
*CLIPBOARD           Full cut, copy and paste operations, enabling user‑definable clips to be shared between tracks.
*INFORMATION         A complete rundown on the state of the current production and your machine.
*MASTER PARAMETERS   Enables global definition of time signatures, lyrics, scales, chords, dynamics and rhythm changes.
*MEDIA MADNESS       A complete multimedia sequencer which allows samples, stills, animation, etc 
*METRONOME           Tempo feedback via MIDI, internal Amiga audio and colour cycling — all three can be mixed and matched as required.
*MIX MAESTRO         Completely automated mixdown with control for both volume and pan. All fader alterations are memorised by the software 
*RECORD ACTIVATION   Complete specification of the data to be recorded/merged. Allows overdubbing of pitch‑bend, program changes, modulation etc
*SET FLAGS           Numeric positioning of location and edit flags in either SMPTE or musical time 
*SONG CONSTRUCTION   Large‑scale cut and paste of individual measures, verses or chorus, by means of bounding box and drag‑n‑drop mouse selections
*TEMPO MAP           Tempo change using a variety of linear and non‑linear transition curves 
*TEMPO PALETTE       Instant tempo changes courtesy of four user‑definable settings.
*TIMELINE SCORING    Sequencing of a selection of songs over a defined period — ideal for planning an entire set for a live performance.
*TOOLBOX             Selection screen for the hundreds of signal‑processing tools available 
*TRACKS              Opens the main track window to enable recording, editing and the use of tools.
*TRANSPORT           Main playback control window, which also provides access to user‑ defined flags, loop and punch‑in record modes.


Bars and Pipes Pro 2.5 is using internal 4-Byte IDs, to check which kind of data are currently processed.
Especially in all its files the IDs play an important role. The IDs are stored into the file in the same order they are laid out in the memory.

In a Bars 'N' Pipes file (no matter which kind) the ID &quot;NAME&quot; (saved as its ANSI-values) is stored on a big endian system (68k-computer) as &quot;NAME&quot;. On a little endian system (x86 PC computer) as &quot;EMAN&quot;.  The target is to make the AROS-BnP compatible to songs, which were stored on a 68k computer (AMIGA).

If possible, setting MIDI channels for Local Control for your keyboard 

http://www.fromwithin.com/liquidmidi/archive.shtml


MIDI files are essentially a stream of event data. An event can be many things, but typically &quot;note on&quot;, &quot;note off&quot;, &quot;program change&quot;, &quot;controller change&quot;, or messages that instruct a MIDI compatible synth how to play a given bit of music.

* Channel     - 1 to 16 -
* Messages    - PC presets, CC effects like delays, reverbs,  etc 
* Sequencing  - MIDI instruments, Drums, Sound design, 
* Recording   - 
* GUI         - Piano roll or Tracker, Staves and Notes 

MIDI events/messages like step entry e.g. Note On, Note Off 

MIDI events/messages like PB, PC, CC, Mono and Poly After-Touch, Sysex, etc 

MIDI sync - Midi Clocks (SPS Measures), Midi Time Code (h, m, s and frames) SMPTE 

Individual track editing with audition edits so easier to test any changes. Possible to stop track playback, mix clips from the right edit flag and scroll the display using arrow keys. 

Step entry, to extend a selected note hit the space bar and the note grows accordingly. Ability to cancel mouse‑driven edits by simply clicking the right mouse button — at which point everything snaps back into its original form. Lyrics can now be put in with syllable dividers, even across an entire measure or section. Autoranging when you open a edit window, the notes are automatically displayed — working from the lowest upwards. 

Flag editing, shift‑click on a flag immediately open the bounds window, ready for numeric input. Ability to cancel edits using the right‑hand mouse button, plus much improved Bounding Box operations.

Icons other than the BarsnPipes icon -&gt; PUBSCREEN=BarsnPipes (cannot choose modes higher than 8bit 256 colors)

Preferences -&gt; Menu in Tracks window - Send MIDI defaults OFF 

Prefs -&gt; Environment -&gt; screenmode (saved to BarsnPipes.prefs binary file) 

Customization -&gt; pics in gui drawer (folder) - 


Can save as .song files and .mid General Midi 

SMF is a “Standard Midi File”  ([http://www.music.mcgill.ca/~ich/classes/mumt306/StandardMIDIfileformat.html SMF0, SMF1 and SMF2]), [https://github.com/stump/libsmf libsmf], [https://github.com/markc/midicomp MIDIcomp], [https://github.com/MajicDesigns/MD_MIDIFile C++ src], [], [https://github.com/newdigate/midi-smf-reader Midi player], 

* SMF0        All MIDI data is stored in one track only, separated exclusively by the MIDI channel.
* SMF1        The MIDI data is stored in separate tracks/channels.
* SMF2 (rarely used) The MIDI data is stored in separate tracks, which are additionally wrapped in containers, so it's possible to have e.g. several tracks using the same MIDI channels.


Would it be possible to enrich Bars N’Pipes with software synth and sample support along with audio recording and mastering tools like in the named MAC or PC music sequencers?
On the classic AMIGA-OS this is not possible because of missing CPU-power. The hardware of the classic AMIGA is not further developed. So we must say (unfortunately) that those dreams can’t become reality

BarsnPipes is best used with external MIDI-equipment. This can be a keyboard or synthesizer with MIDI-connectors. 

&lt;pre&gt;
MIDI can control 16 channels 
There are USB-MIDI-Interfaces on the market with 16 independent MIDI-lines (multi-port), which can handle 16 MIDI devices independently – 16×16 = 256 independent MIDI-channels or instruments 
handle up to 16 different USB-MIDI-Interfaces (multi-device). That is: 16X16X16 = 4096 independent MIDI-channels – theoretically 
&lt;/pre&gt;

&lt;pre&gt;
Librarian MIDI SYStem EXplorer (sysex) - PatchEditor and used to be supplied as a separate program like PatchMeister but currently not at present 
It should support MIDI.library (PD), BlueRibbon.library (B&amp;P), TriplePlayPlus, and CAMD.library (DeluxeMusic) and 
MIDI information from a device's user manual and configure a custom interface to access parameters for all MIDI products connected to the system 
Supports ALL MIDI events and the Patch/Librarian data is stored in MIDI standard format 
Annette M.Crowling, Missing Link Software, Inc.
&lt;/pre&gt;


Composers
&lt;pre&gt;
[https://x.com/hirasawa/status/1403686519899054086 Susumu Hirasawa] 

&lt;/pre&gt;


&lt;pre&gt;
1988 Todor Fay and his wife Melissa Jordan Gray, who founded the Blue Ribbon Inc
1992 Bars&amp;Pipes Pro published 
November 2000, Todor Fay announcement to release the sourcecode of Bars&amp;Pipes Pro 2.5c beta
end of May 2001, the source of the main program and the sources of some tools and accessories were in a complete and compileable state 
end of October 2009 stop further development of BarsnPipes New for now on all supported systems and made freeware 
2013 Alfred Faust diagnosed with incureable illness, called „Myastenia gravis“ (weak muscles) 
&lt;/pre&gt;


 Protrekkr

How to use Midi In/Out in Protrekkr ?

First of all, midi in &amp; out capabilities of this program are rather limited.

# Go to Misc. Setup section and select a midi in or out device to use (ptk only supports one device at a time).
# Go to instrument section, and select a MIDI PRG (the default is N/A, which means no midi program selected).
# Go to track section and here you can assign a midi channel to each track of ptk.
# Play notes :]. Note off works. F'x' note cut command also works too, and note-volume command (speed) is supported.

Also, you can change midicontrollers in the tracker, using '90' in the panning row:

&lt;pre&gt;
    C-3 02 .. .. 0000....


    --- .. .. 90 xxyy.... &lt;&lt; This will set the value 
    --- .. .. .. 0000....    of the controller n.'xx' to 'yy' (both in hex)
    --- .. .. .. 0000....
&lt;/pre&gt;

So &quot;--- .. .. 90 2040....&quot; will set the controller number $20(32) to $40(64).

You will need the midi implementation table of your gear to know what you can change with midi controller messages.

 N.B. Not all MIDI devices are created equal!

Although the MIDI specification defines a large range of MIDI messages of various kinds, not every MIDI device is required to work in exactly the same way and respond to all the available messages and ways of working. For example, we don't expect a wind synthesiser to work in the same way as a home keyboard.

Some devices, the older ones perhaps, are only able to respond to a single channel. With some of those devices that channel can be altered from the default of 1 (probably) to another channel of the 16 possible.

Other devices, for instance monophonic synthesisers, are capable of producing just one note at a time, on one MIDI channel. Others can produce many notes spread across many channels.

Further devices can respond to, and transmit, &quot;breath controller&quot; data (MIDI controller number 2 (CC#2)) others may respond to the reception of CC#2 but not be able to create and to send it.

A controller keyboard may be capable of sending &quot;expression pedal&quot; data, but another device may not be capable of responding to that message.

Some devices just have the basic GM sound set. The &quot;voice&quot; or &quot;instrument&quot; is selected using a &quot;Program Change&quot; message on its own.

Other devices have a greater selection of voices, usually arranged in &quot;banks&quot;, and the choice of instrument is made by responding to &quot;Bank Select MSB&quot; (MIDI controller 0 (CC#0)), others use &quot;Bank Select LSB&quot; (MIDI controller number 32 (CC#32)), yet others use both MSB and LSB sent one after the other, all followed by the Program Change message. The detailed information about all the different voices will usually be available in a published MIDI Data List.


 MIDI Implementation Chart

But in the User Manual there is sometimes a summary of how the device works, in terms of MIDI, in the chart at the back of the manual, the MIDI Implementation Chart.

If you require two devices to work together you can compare the two implementation charts to see if they are &quot;compatible&quot;. In order to do this we will need to interpret that chart.

The chart is divided into four columns headed &quot;Function&quot;, &quot;Transmitted&quot; (or &quot;Tx&quot;), &quot;Received&quot; (or &quot;Rx&quot;), or more correctly &quot;Recognised&quot;, and finally, &quot;Remarks&quot;.

&lt;pre&gt;
The left hand column defines which MIDI functions are being described.
The 2nd column defines what the device in question is capable of transmitting to another device.
The 3rd column defines what the device is capable of responding to.
The 4th column is for explanations of the values contained within these previous two columns.
&lt;/pre&gt;

There should then be twelve sections, with possibly a thirteenth containing extra &quot;Notes&quot;. Finally there should be an explanation of the four MIDI &quot;modes&quot; and what the &quot;X&quot; and the &quot;O&quot; mean.
&lt;pre&gt;
Mode 1: Omni On, Poly; 
Mode 2: Omni On, Mono; 
Mode 3: Omni Off, Poly; 
Mode 4: Omni Off, Mono.
&lt;/pre&gt;
O means &quot;yes&quot; (implemented), X means &quot;no&quot; (not implemented).

Sometimes you will find a row of asterisks &quot;**************&quot;, these seem to indicate that the data is not applicable in this case. Seen in the transmitted field only (unless you've seen otherwise).

Lastly you may find against some entries an asterisk followed by a number e.g. *1, these will refer you to further information, often on a following page, giving more detail.

Basic Channel
But the very first set of boxes will tell us the &quot;Basic Channel(s)&quot; that the device sends or receives on. 
&quot;Default&quot; is what happens when the device is first turned on, &quot;changed&quot; is what a switch of some kind may allow the device to be set to. 
For many devices e.g. a GM sound module or a home keyboard, this would be 1-16 for both. That is it can handle sending and receiving on all MIDI channels.

On other devices, for example a synthesiser, it may by default only work on channel 1. But the keyboard could be &quot;split&quot; with the lower notes e.g. on channel 2. If the synth has an arppegiator, this may be able to be set to transmit and or receive on yet another channel.
So we might see the default as &quot;1&quot; but the changed as &quot;1-16&quot;.

Modes.
We need to understand Omni On and Off, and Mono and Poly, then we can decipher the four modes.

But first we need to understand that any of these four Mode messages can be sent to any MIDI channel. They don't necessarily apply to the whole device.

If we send an &quot;Omni On&quot; message (CC#125) to a MIDI channel of a device, we are, in effect, asking it to respond to e.g. a Note On / Off message pair, received on any of the sixteen channels. Sound strange? Read it again. Still strange? It certainly is. We normally want a MIDI channel to respond only to Note On / Off messages sent on that channel, not any other. In other words, &quot;Omni Off&quot;.

So &quot;Omni Off&quot; (CC#124) tells a channel of our MIDI device to respond only to messages sent on that MIDI channel.

&quot;Poly&quot; (CC#127) is for e.g. a channel of a polyphonic sound module, or a home keyboard, to be able to respond to many simultaneous Note On / Off message pairs at once and produce musical chords.

&quot;Mono&quot; (CC#126) allows us to set a channel to respond as if it were e.g. a flute or a trumpet, playing just one note at a time. If the device is capable of it, then the overlapping of notes will produce legato playing, that is the attack portion of the second note of two overlapping notes will be removed resulting in a &quot;smoother&quot; transition.

So a channel with a piano voice assigned to it will have Omni Off, Poly On (Mode 3), a channel with a saxophone voice assigned could be Omni Off, Mono On (Mode 4).

We call these combinations the four modes, 1 to 4, as defined above. 
Most modern devices will have their channels set to Mode 3 (Omni Off, Poly) but be switchable, on a per channel basis, to Mode 4 (Omni Off, Mono).

This second section of data will include first its default value i.e. upon device switch on. Then what Mode messages are acceptable, or X if none.

Finally, in the &quot;Altered&quot; field, how a Mode message that can't be implemented will be interpreted. Usually there will just be a row of asterisks effectively meaning nothing will be done if you try to switch to an unimplemented mode.

Note Number
&lt;pre&gt;
The next row will tell us which MIDI notes the device can send or receive, normally 0-127.
The second line, &quot;True Voice&quot; has the following in the MIDI specification: 
&quot;Range of received note numbers falling within the range of true notes produced by the instrument.&quot;
My interpretation is that, for instance, a MIDI piano may be capable of sending all MIDI notes (0 to 127) by transposition, but only responding to the 88 notes (21 to 108) of a real piano. 
&lt;/pre&gt;

Velocity
This will tell us whether the device we're looking at will handle note velocity, and what range from 1-127, or maybe just 64, it transmits or will recognise. So usually &quot;O&quot; plus a range or &quot;X&quot; for not implemented.

After touch
This may have one or two lines two it.
If a one liner the either &quot;O&quot; or &quot;X&quot;, yes or no.
If a two liner then it may include &quot;Keys&quot; or &quot;Poly&quot; and &quot;Channel&quot;.
This will show whether the device will respond to Polyphonic after touch or channel after touch or neither.

Pitch Bend
Again &quot;O&quot; for implemented, &quot;X&quot; for not implemented.
(Many stage pianos will have no pitch bend capability.)
It may also, in the notes section, state whether it will respond to the full 14 bits, or not, as usually encoded by the pitch bend wheel.

Control Change
This is likely to be the largest section of the chart.
It will list all those controllers, starting from CC#0, Bank Select MSB, which the device is capable of sending, and those that it will respond to using &quot;O&quot; or &quot;X&quot; respectively.
You will, almost certainly, get some further explanation of functionality in the remarks column, or in more detail elsewhere in the documentation.

Of course you will need to know what all the various controller numbers do. Lots of the official technical specifications can be found at the [www.midi.org/techspecs/ MMA], with the table of messages and control change [www.midi.org/techspecs/midimessages.php message numbers]

Program Change
Again &quot;O&quot; or &quot;X&quot; in the Transmitted or Recognised column to indicate whether or not the feature is implemented. In addition a range of numbers is shown, typically 0-127, to show what is available.
True # (number): &quot;The range of the program change numbers which correspond to the actual number of patches selected.&quot;

System Exclusive
Used to indicate whether or not the device can send or recognise System Exclusive messages. A short description is often given in the Remarks field followed by a detailed explanation elsewhere in the documentation.

System Common - These include the following:
&lt;pre&gt;
MIDI Time Code Quarter Frame messages (device synchronisation).
Song Position Pointer
Song Select
Tune Request
&lt;/pre&gt;
The section will indicate whether or not the device can send or respond to any of these messages.

System Real Time
These include the following:
&lt;pre&gt;
Timing Clock - often just written as &quot;Clock&quot;
Start
Stop
Continue
&lt;/pre&gt;
These three are usually just referred to as &quot;Commands&quot; and listed.
Again the section will indicate which, if any, of these messages the device can send or respond to.
&lt;pre&gt;
Aux. Messages
Again &quot;O&quot; or &quot;X&quot; for implemented or not.
Aux. = Auxiliary.
Active Sense = Active Sensing.
&lt;/pre&gt;
Often with an explanation of the action of the device.

Notes
The &quot;Notes&quot; section can contain any additional comments to clarify the particular implementation.

Some of the explanations have been drawn directly from the MMA MIDI 1.0 Detailed Specification.
And the detailed explanation of some of the functions will be found there, or in the General MIDI System Level 1 or General MIDI System Level 2 documents also published by the MMA.


 OFFICIAL MIDI SPECIFICATIONS

SUMMARY OF MIDI MESSAGES
Table 1 - Summary of MIDI Messages

The following table lists the major MIDI messages in numerical (binary) order (adapted from &quot;MIDI by the Numbers&quot; by D. Valenti, Electronic Musician 2/88, and updated by the MIDI Manufacturers Association.). This table is intended as an overview of MIDI, and is by no means complete.

WARNING! Details about implementing these messages can dramatically impact compatibility with other products. We strongly recommend consulting the official MIDI Specifications for additional information.

MIDI 1.0 Specification

Message Summary Channel Voice Messages [nnnn = 0-15 (MIDI Channel Number 1-16)]

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;10%&quot;  |Status D7----D0 
! width=&quot;10%&quot;  |Data Byte(s) D7----D0 
! width=&quot;20%&quot;  |Description
|-
|&lt;!--Status--&gt;1000nnnn || &lt;!--Data--&gt;0kkkkkkk 0vvvvvvv || &lt;!--Description--&gt;Note Off event. 
This message is sent when a note is released (ended). (kkkkkkk) is the key (note) number. (vvvvvvv) is the velocity.
|-
|&lt;!--Status--&gt;1001nnnn || &lt;!--Data--&gt;0kkkkkkk 0vvvvvvv || &lt;!--Description--&gt;Note On event. 
This message is sent when a note is depressed (start). (kkkkkkk) is the key (note) number. (vvvvvvv) is the velocity.
|-
|&lt;!--Status--&gt;1010nnnn || &lt;!--Data--&gt;0kkkkkkk 0vvvvvvv || &lt;!--Description--&gt;Polyphonic Key Pressure (Aftertouch). 
This message is most often sent by pressing down on the key after it &quot;bottoms out&quot;. (kkkkkkk) is the key (note) number. (vvvvvvv) is the pressure value.
|-
|&lt;!--Status--&gt;1011nnnn || &lt;!--Data--&gt;0ccccccc 0vvvvvvv || &lt;!--Description--&gt;Control Change. 
This message is sent when a controller value changes. Controllers include devices such as pedals and levers. Controller numbers 120-127 are reserved as &quot;Channel Mode Messages&quot; (below). (ccccccc) is the controller number (0-119). (vvvvvvv) is the controller value (0-127).
|-
|&lt;!--Status--&gt;1100nnnn || &lt;!--Data--&gt;0ppppppp || &lt;!--Description--&gt;Program Change. This message sent when the patch number changes. (ppppppp) is the new program number.
|-
|&lt;!--Status--&gt;1101nnnn || &lt;!--Data--&gt;0vvvvvvv || &lt;!--Description--&gt;Channel Pressure (After-touch). This message is most often sent by pressing down on the key after it &quot;bottoms out&quot;. This message is different from polyphonic after-touch. Use this message to send the single greatest pressure value (of all the current depressed keys). (vvvvvvv) is the pressure value.
|-
|&lt;!--Status--&gt;1110nnnn || &lt;!--Data--&gt;0lllllll 0mmmmmmm || &lt;!--Description--&gt;Pitch Bend Change. This message is sent to indicate a change in the pitch bender (wheel or lever, typically). The pitch bender is measured by a fourteen bit value. Center (no pitch change) is 2000H. Sensitivity is a function of the receiver, but may be set using RPN 0. (lllllll) are the least significant 7 bits. (mmmmmmm) are the most significant 7 bits.
|}

Channel Mode Messages (See also Control Change, above)

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;10%&quot;  |Status D7----D0 
! width=&quot;10%&quot;  |Data Byte(s) D7----D0 
! width=&quot;20%&quot;  |Description
|-
|&lt;!--Status--&gt;1011nnnn || &lt;!--Data--&gt;0ccccccc 0vvvvvvv || &lt;!--Description--&gt;Channel Mode Messages. 
This the same code as the Control Change (above), but implements Mode control and special message by using reserved controller numbers 120-127. The commands are:
*All Sound Off. When All Sound Off is received all oscillators will turn off, and their volume envelopes are set to zero as soon as possible c = 120, v = 0: All Sound Off
*Reset All Controllers. When Reset All Controllers is received, all controller values are reset to their default values. (See specific Recommended Practices for defaults) c = 121, v = x: Value must only be zero unless otherwise allowed in a specific Recommended Practice.
*Local Control. When Local Control is Off, all devices on a given channel will respond only to data received over MIDI. Played data, etc. will be ignored. Local Control On restores the functions of the normal controllers. 
c = 122, v = 0: Local Control Off
c = 122, v = 127: Local Control On
* All Notes Off. When an All Notes Off is received, all oscillators will turn off. 
c = 123, v = 0: All Notes Off (See text for description of actual mode commands.)
c = 124, v = 0: Omni Mode Off 
c = 125, v = 0: Omni Mode On 
c = 126, v = M: Mono Mode On (Poly Off) where M is the number of channels (Omni Off) or 0 (Omni On) 
c = 127, v = 0: Poly Mode On (Mono Off) (Note: These four messages also cause All Notes Off)
|}

System Common Messages

System Messages (0xF0)

The final status nybble is a “catch all” for data that doesn’t fit the other statuses. They all use the most significant nybble (4bits) of 0xF, with the least significant nybble indicating the specific category.

The messages are denoted when the MSB of the second nybble is 1. When that bit is a 0, the messages fall into two other subcategories.

System Common

If the MSB of the second second nybble (4 bits) is not set, this indicates a System Common message. Most of these are messages that include some additional data bytes.

System Common Messages
Type Status Byte   Number of Data Bytes      Usage 
&lt;pre&gt;
Time Code Quarter Frame	0xF1	1	Indicates timing using absolute time code, primarily for synthronization with video playback systems. A single location requires eight messages to send the location in an encoded hours:minutes:seconds:frames format*.
Song Position	0xF2	2	Instructs a sequencer to jump to a new position in the song. The data bytes form a 14-bit value that expresses the location as the number of sixteenth notes from the start of the song.
Song Select	0xF3	1	Instructs a sequencer to select a new song. The data byte indicates the song.
Undefined	0xF4	0	
Undefined	0xF5	0	
Tune Request	0xF6	0	Requests that the receiver retunes itself**.
&lt;/pre&gt;
*MIDI Time Code (MTC) is significantly complex. Please see the MIDI Specification
**While modern digital instruments are good at staying in tune, older analog synthesizers were prone to tuning drift. Some analog synthesizers had an automatic tuning operation that could be initiated with this command.


System Exclusive

If you’ve been keeping track, you’ll notice there are two status bytes not yet defined: 0xf0 and 0xf7. These are used by the System Exclusive message, often abbreviated at SysEx. SysEx provides a path to send arbitrary data over a MIDI connection. There is a group of predefined messages for complex data, like fine grained control of MIDI Time code machinery. SysEx is also used to send manufacturer defined data, such as patches, or even firmware updates.

System Exclusive messages are longer than other MIDI messages, and can be any length. The messages are of the following format:

0xF0, 0xID, 0xdd, ...... 0xF7
The message is bookended with distinct bytes.

It opens with the Start Of Exclusive (SOX) data byte, 0xF0.
The next one to three bytes after the start are an identifier.
Values from 0x01 to 0x7C are one-byte vendor IDs, assigned to manufacturers who were involved with MIDI at the beginning.
If the ID is 0x00, it’s a three-byte vendor ID - the next two bytes of the message are the value.
&lt;pre&gt;
ID 0x7D is a placeholder for non-commercial entities.
ID 0x7E indicates a predefined Non-realtime SysEx message.
ID 0x7F indicates a predefined Realtime SysEx message.
&lt;/pre&gt;
After the ID is the data payload, sent as a stream of bytes.
The transfer concludes with the End of Exclusive (EOX) byte, 0xF7.
The payload data must follow the guidelines for MIDI data bytes – the MSB must not be set, so only 7 bits per byte are actually usable. If the MSB is set, it falls into three possible scenarios.

An End of Exclusive byte marks the ordinary termination of the SysEx transfer.
System Real Time messages may occur within the transfer without interrupting it. The recipient should handle them independently of the SysEx transfer.
Other status bytes implicitly terminate the SysEx transfer and signal the start of new messages.
 Some inexpensive USB-to-MIDI interfaces aren’t capable of handling messages longer than four bytes.

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;10%&quot;  |Status D7----D0 
! width=&quot;10%&quot;  |Data Byte(s) D7----D0 
! width=&quot;20%&quot;  |Description
|-
|&lt;!--Status--&gt;11110000 || &lt;!--Data--&gt;0iiiiiii [0iiiiiii 0iiiiiii]  0ddddddd  --- --- 0ddddddd 11110111 || &lt;!--Description--&gt;System Exclusive. 
This message type allows manufacturers to create their own messages (such as bulk dumps, patch parameters, and other non-spec data) and provides a mechanism for creating additional MIDI Specification messages. The Manufacturer's ID code (assigned by MMA or AMEI) is either 1 byte (0iiiiiii) or 3 bytes (0iiiiiii 0iiiiiii 0iiiiiii). Two of the 1 Byte IDs are reserved for extensions called Universal Exclusive Messages, which are not manufacturer-specific. If a device recognizes the ID code as its own (or as a supported Universal message) it will listen to the rest of the message (0ddddddd). Otherwise, the message will be ignored. (Note: Only Real-Time messages may be interleaved with a System Exclusive.)
|-
|&lt;!--Status--&gt;11110001 || &lt;!--Data--&gt;0nnndddd || &lt;!--Description--&gt;MIDI Time Code Quarter Frame.
nnn = Message Type
dddd = Values
|-
|&lt;!--Status--&gt;11110010 || &lt;!--Data--&gt;0lllllll 0mmmmmmm || &lt;!--Description--&gt;Song Position Pointer. 
This is an internal 14 bit register that holds the number of MIDI beats (1 beat= six MIDI clocks) since the start of the song. l is the LSB, m the MSB.
|-
|&lt;!--Status--&gt;11110011 || &lt;!--Data--&gt;0sssssss || &lt;!--Description--&gt;Song Select. 
The Song Select specifies which sequence or song is to be played.
|-
|&lt;!--Status--&gt;11110100 || &lt;!--Data--&gt; || &lt;!--Description--&gt;Undefined. (Reserved)
|-
|&lt;!--Status--&gt;11110101 || &lt;!--Data--&gt; || &lt;!--Description--&gt;Undefined. (Reserved)
|-
|&lt;!--Status--&gt;11110110 || &lt;!--Data--&gt; || &lt;!--Description--&gt;Tune Request. Upon receiving a Tune Request, all analog synthesizers should tune their oscillators.
|-
|&lt;!--Status--&gt;11110111 || &lt;!--Data--&gt; || &lt;!--Description--&gt;End of Exclusive. Used to terminate a System Exclusive dump. 
|}


System Real-Time Messages

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;10%&quot;  |Status D7----D0 
! width=&quot;10%&quot;  |Data Byte(s) D7----D0 
! width=&quot;20%&quot;  |Description
|-
|&lt;!--Status--&gt;11111000 || &lt;!--Data--&gt; || &lt;!--Description--&gt;Timing Clock. Sent 24 times per quarter note when synchronization is required.
|-
|&lt;!--Status--&gt;11111001 || &lt;!--Data--&gt; || &lt;!--Description--&gt;Undefined. (Reserved)
|-
|&lt;!--Status--&gt;11111010 || &lt;!--Data--&gt; || &lt;!--Description--&gt;Start. Start the current sequence playing. (This message will be followed with Timing Clocks).
|-
|&lt;!--Status--&gt;11111011 || &lt;!--Data--&gt; || &lt;!--Description--&gt;Continue. Continue at the point the sequence was Stopped.
|-
|&lt;!--Status--&gt;11111100 || &lt;!--Data--&gt; || &lt;!--Description--&gt;Stop. Stop the current sequence.
|-
|&lt;!--Status--&gt;11111101 || &lt;!--Data--&gt; || &lt;!--Description--&gt;Undefined. (Reserved)
|-
|&lt;!--Status--&gt;11111110 || &lt;!--Data--&gt; || &lt;!--Description--&gt;Active Sensing. This message is intended to be sent repeatedly to tell the receiver that a connection is alive. Use of this message is optional. When initially received, the receiver will expect to receive another Active Sensing message each 300ms (max), and if it does not then it will assume that the connection has been terminated. At termination, the receiver will turn off all voices and return to normal (non- active sensing) operation. 
|-
|&lt;!--Status--&gt;11111111 || &lt;!--Data--&gt; || &lt;!--Description--&gt;Reset. Reset all receivers in the system to power-up status. This should be used sparingly, preferably under manual control. In particular, it should not be sent on power-up.
|}


Advanced Messages

Polyphonic Pressure (0xA0) and Channel Pressure (0xD0)

Some MIDI controllers include a feature known as Aftertouch. While a key is being held down, the player can press harder on the key. The controller measures this, and converts it into MIDI messages.

Aftertouch comes in two flavors, with two different status messages.

The first flavor is polyphonic aftertouch, where every key on the controller is capable of sending its own independent pressure information. The messages are of the following format:
&lt;pre&gt;
0xnc, 0xkk, 0xpp
n is the status (0xA)
c is the channel nybble
kk is the key number (0 to 127)
pp is the pressure value (0 to 127)
&lt;/pre&gt;
Polyphonic aftertouch is an uncommon feature, usually found on premium quality instruments, because every key requires a separate pressure sensor, plus the circuitry to read them all.

Much more commonly found is channel aftertouch. Instead of needing a discrete sensor per key, it uses a single, larger sensor to measure pressure on all of the keys as a group. The messages omit the key number, leaving a two-byte format
&lt;pre&gt;
0xnc, 0xpp
n is the status (0xD)
c is the channel number
pp is the pressure value (0 to 127)
&lt;/pre&gt;

Pitch Bend (0xE0)

Many keyboards have a wheel or lever towards the left of the keys for pitch bend control. This control is usually spring-loaded, so it snaps back to the center of its range when released. This allows for both upward and downward bends.

Pitch Bend Wheel

The wheel sends pitch bend messages, of the format
&lt;pre&gt;
0xnc, 0xLL, 0xMM
n is the status (0xE)
c is the channel number
LL is the 7 least-significant bits of the value
MM is the 7 most-significant bits of the value
&lt;/pre&gt;
You’ll notice that the bender data is actually 14 bits long, transmitted as two 7-bit data bytes. This means that the recipient needs to reassemble those bytes using binary manipulation. 14 bits results in an overall range of 214, or 0 to 16,383. Because it defaults to the center of the range, the default value for the bender is halfway through that range, at 8192 (0x2000).

Control Change (0xB0)

In addition to pitch bend, MIDI has provisions for a wider range of expressive controls, sometimes known as continuous controllers, often abbreviated CC. These are transmitted by the remaining knobs and sliders on the keyboard controller shown below.


Continuous Controllers

These controls send the following message format:
&lt;pre&gt;
0xnc, 0xcc, 0xvv
n is the status (0xB)
c is the MIDI channel
cc is the controller number (0-127)
vv is the controller value (0-127)
&lt;/pre&gt;

Typically, the wheel next to the bender sends controller number one, assigned to modulation (or vibrato) depth. It is implemented by most instruments.

The remaining controller number assignments are another point of confusion. The MIDI specification was revised in version 2.0 to assign uses for many of the controllers. However, this implementation is not universal, and there are ranges of unassigned controllers.

On many modern MIDI devices, the controllers are assignable. On the controller keyboard shown in the photos, the various controls can be configured to transmit different controller numbers. Controller numbers can be mapped to particular parameters. Virtual synthesizers frequently allow the user to assign CCs to the on-screen controls. This is very flexible, but it might require configuration on both ends of the link and completely bypasses the assignments in the standard.


Program Change (0xC0)

Most synthesizers have patch storage memory, and can be told to change patches using the following command:
&lt;pre&gt;
0xnc, 0xpp
n is the status (0xc)
c is the channel
pp is the patch number (0-127)
&lt;/pre&gt;
This allows for 128 sounds to be selected, but modern instruments contain many more than 128 patches. Controller #0 is used as an additional layer of addressing, interpreted as a “bank select” command. Selecting a sound on such an instrument might involve two messages: a bank select controller message, then a program change.

Audio &amp; Midi are not synchronized, what I can do ?
Buy a commercial software package but there is a nasty trick to synchronize both. It's a bit hardcore but works for me:

 Simply put one line down to all midi notes on your pattern (use Insert key)
 and go to 'Misc. Setup', adjust the latency and just search a value
 that will make sound sync both audio/midi.

The stock Sin/Saw/Pulse and Rnd waveforms are too simple/common, is there a way to use something more complex/rich ?
You have to ability to redirect the waveforms of the instruments through the synth pipe by selecting the &quot;wav&quot; option for the oscillator you're using for this synth instrument, samples can be used as wavetables to replace the stock signals.


Sound banks like soundfont (sf2) or Kontakt2 are not supported at the moment


====DAW Audio Evolution 4====

Audio Evolution 4 gives you unsurpassed power for digital audio recording and editing on the Amiga. The latest release focusses on time-saving non-linear and non-destructive editing, as seen on other platforms. Besides editing, Audio Evolution 4 offers a wide range of realtime effects, including compression, noise gate, delays, reverb, chorus and 3-band EQ.

Whether you put them as inserts on a channel or use them as auxillaries, the effect parameters are realtime adjustable and can be fully automated. Together with all other mixing parameters, they can even be controlled remotely, using more ergonomic MIDI hardware.

Non-linear editing on the time line, including cut, copy, paste, move, split, trim and crossfade actions

The number of tracks per project(s) is unlimited .... AHI limits you to recording only two at a time. i.e. not on 8 track sound cards like the Juli@ or Phase 88.

sample file import is limited to 16bit AIFF (not AIFC, important distinction as some files from other sources can be AIFC with aiff file extention). and 16bit WAV (pcm only)


Most apps use the Music Unit only but a few apps also use Unit (0-3) instead or as well. 
* Set up AHI prefs so that microphone is available. (Input option near the bottom)


stereo++ allows the audio piece to be placed anywhere and the left-right adjusted to sound positionally right

hifi best for music playback if driver supports this option


Load 16bit .aif .aiff only sample(s) to use not AIFC which can have the same ending. AIFF stands for Audio Interchange File Format 

 sox recital.wav recital.aiff

 sox recital.wav −b 16 recital.aiff channels 1 rate 16k fade 3 norm
 sox input.wav        output.aiff bass −b 16 rate 48k

performs the same format translation, but also applies four effects (down-mix to one channel, sample rate change, fade-in, nomalize), and stores the result at a bit-depth of 16.

 rec −c 2 radio.aiff trim 0 30:00

records half an hour of stereo audio 

 play existing-file.wav


24bit PCM WAV or AIFF do not work 

*No stream format handling. So no way to pass on an AC3 encoded stream unmodified to the digital outputs through AHI.
*No master volume handling. Each application has to set its own volume. So each driver implements its own custom driver-mixer interface for handling master volumes, mute and preamps.
*Only one output stream. So all input gets mixed into one output.
*No automatic handling of output direction based on connected cables.
*No monitor input selection. Only monitor volume control. 


select the correct input (Don't mistake enabled sound for the correct input.)
The monitor will feedback audio to the lineout and hp out no matter if you have selected the correct input to the ADC. The monitor will provide sound for any valid input. This will result in free mixing when recording from the monitor input instead of mic/line because the monitor itself will provide the hardware mixing for you. Be aware that MIC inputs will give two channel mono. Only Linein will give real stereo.

Now for the not working part. Attempt to record from linein in the AE4 record window, the right channel is noise and the left channel is distorted. Even with the recommended HIFI 16bit Stereo++ mode at 48kHz.


Channels

Monitor

Gain

Inout

Output

Advanced settings - Debugging via serial port


* Options -&gt; Soundcard In/Out
* Options -&gt; SampleRate
* Options -&gt; Preferences

F6 for Sample File List

Setting a grid is easy as is measuring the BPM by marking a section of the sample. Is your kick drum track &quot;not in time&quot; ? If so, you're stumped in AE4 as it has no fancy variable time signatures and definitely no 'track this dodgy rhythm' function like software of the nature of Logic has. So if your drum beat is freeform you will need to work in freeform mode. (Real music is free form anyway).

If the drum *is* accurate and you are just having trouble measuring the time, I usually measure over a range of bars and set the number of beats in range to say 16 as this is more accurate, Then you will need to shift the drum track to match your grid *before* applying the grid. (probably an iterative process as when the grid is active samples snap to it, and when inactive you cannot see it).

AE4 does have ARexx but the functions are more for adding samples at set offsets and starting playback / recording.


These are the usual features found in DAWs...

* Recording digital audio, midi sequencer and mixer 
* virtual VST instruments and plug-ins 
* automation, group channels, MIDI channels, FX sends and returns, audio and MIDI editors and music notation editor


* different track views 
* mixer and track layout (but not the same as below) 
* traditional two windows (track and mixer)


Mixing - mixdown

Could not figure out how to select what part I wanted to send to the aux, set it to echo and return. Pretty much the whole echo effect. Or any effect.

Take look at page17 of the manual.

When you open the EQ / Aux send popup window you will see 4 sends. Now from the menu choose the windows menu.

Menus-&gt;Windows-&gt; Aux Returns Window

or press F5

You will see a small window with 4 volume controls and an effects button for each. Click a button and add an effects to that aux channel, then set it up as desired (note the reverb effect has a special AUX setting that improves its use with the aux channel, not compulsory but highly useful). You set the amount of 'return' on the main mix in the Aux Return window, and the amount sent from each main mixer channel in the popup for that channel. Again the aux sends are &quot;prefade&quot; so the volume faders on each channel do not affect them.


Tracking


Effects - fade in

To add some echoes to some vocals, tried to add an effect on a track but did not come out. This is made more complicated as I wanted to mute a vocal but then make it echo at the muting point. Want to have one word of a vocal heard and then echoed off. But when the track is mute the echo is cancelled out.

To correctly understand what is happening here you need to study the figure at the bottom of page 15 on the manual. You will see from that that the effects are applied 'prefade' So the automation you applied will naturally mute the entire signal.

There would be a number of ways to achieve the goal,

You have three real time effects slots, one for smoothing like so

Sample -&gt; Amplify -&gt; Delay

Then automate the gain of the amplify block so that it effectively mutes the sample just before the delay at the appropriate moment, the echo effect should then be heard.

Getting the effects in the right order will require experimentation as they can only be added top down and it's not obvious which order they are applied to the signal, but there only two possibilities, so it wont take long to find out.

Using MUTE can cause clicks to the Amplify can be used to mute more smoothly so that's a secondary advantage.

Signal Processing -


Overdub

[[#top|...to the top]]

===Office===

====Spreadsheet Leu====

Support for some xlsx, and ods functions 


====Spreadsheet Ignition====

; Needs ABIv1 to be completed before more can be done

File formats supported 
* ascii #?.txt and #?.csv (single sheets with data only). 
* igs and TurboCalc(WIP) #?.tc for all sheets with data, formats and formulas.

There is '''no''' support for xls, xlsx, ods or uos ([http://en.wikipedia.org/wiki/Uniform_Office_Format Uniform Unified Office Format]) at the moment.

* Always use Esc key after editing Spreadsheet cells.
* copy/paste seems to copy the first instance only so go to Edit -&gt; Clipboard to manage the list of remembered actions. 
* Right mouse click on row (1 or 2 or 3) or column header (a or b or c)  to access optimal height or width of the row or column respectively 
* Edit -&gt; Insert -&gt; Row  seems to clear the spreadsheet or clears the rows after the inserted row until undo restores as it should be...

Change Sheet name by  Object -&gt; Sheet -&gt; Properties

Click in the cell which will contain the result, and click '''down arrow button''' to the right of the formula box at the bottom of the spreadsheet and choose the function required from the list provided. Then click on the start cell and click on the bottom right corner, a '''very''' small blob, which allows stretching a bounding box (thick grey outlines) across many cells This grey bounding box can be used to '''copy a formula''' to other cells.

Object -&gt; Cell -&gt; Properties to change cell format - Currency only covers DM and not $, Euro, Renminbi, Yen or Pound etc. 
Shift key and arrow keys selects a range of cells, so that '''formatting can be done to all highlighted cells'''. 
View -&gt; Overview then select ALL with one click (in empty cell in the top left hand corner of the sheet).

Default mode is relative cell referencing e.g. a1+a2 but absolute e.g. $a$1+$a$2 can be entered.

* #sheet-name to '''absolute''' reference another sheet-name cell unless reference() function used.

;Graphs

use shift key and arrow keys to select a bunch of cells to be graph'ed making sure that x axes represents and y axes represents

* value() - 0 value, 1 percent, 2 date, 3 time, 4 unit ...


;Dates 
* Excel starts a running count from the 1st Jan 1900 and Ignition starts from 1st Jan 1AD '''(maybe this needs to change)'''
Set formatting Object -&gt; Cell -&gt; Properties and put date in days


;Time 
Set formatting Object -&gt; Cell -&gt; Properties and put time in seconds taken


;Database (to be done by someone else)

type - standard, reference (bezug), search criterion (suchkriterium), 
* select a bunch of cells and Object -&gt; Database -&gt; Define to set Datenbank (database) and Felder (fields not sure how?) 
* Neu (new) or loschen (delete) to add/remove database headings e.g. Personal, Start Date, Finish Date (one per row?)
* Object -&gt; Database -&gt; Index to add fields (felder) like Surname, First Name, Employee ID, etc. to ?

Filtering done with dbfilter(), dbproduct() and dbposition().

Activities with dbsum(), dbaverage(), dbmin() and dbmax().

Table sorting -


;Scripts (Arexx)

;Excel(TM) to Ignition - commas ''',''' replaced by semi-colons ''';''' to separate values within functions 
*SUM(), 
*AVERAGE(), MAX(), MIN(), INT(), PRODUCT(), MEDIAN(), VAR() becomes Variance(), Percentile(),
*IF(), AND, OR, NOT 
*LEFT(), RIGHT(), MID() becomes MIDDLE(), LEN() becomes LENGTH(), 
*LOWER() becomes LOWERCASE(), UPPER() becomes UPPERCASE(),
* DATE(yyyy,mm,dd) becomes COMPUTEDATE(dd;mm;yyyy), 
*TODAY(), DAY(),WEEK(), MONTH(),=YEAR(TODAY()), 
*EOMONTH() becomes MONTHLENGTH(), 
*NOW() should be date and time becomes time only, SECOND(), MINUTE(), HOUR(),
*DBSUM() becomes DSUM(),


;Missing and possibly useful features/functions needed for ignition to have better support of Excel files 
There is no Merge and Join Text over many cells, no protect and/or freeze row or columns or books but can LOCK sheets, no define bunch of cells as a name, Macros (Arexx?), conditional formatting, no Solver, no Goal Seek, no Format Painter, no AutoFill, no AutoSum function button, no pivot tables, (30 argument limit applies to Excel)

*HLOOKUP(), VLOOKUP(), [http://production-scheduling.com/excel-index-function-most-useful/ INDEX(), MATCH()], CHOOSE(), TEXT(), 
*TRIM(), FIND(), SUBSTITUTE(), CONCATENATE() or &amp;, PROPER(), REPT(), 
*[https://acingexcel.com/excel-sumproduct-function/ SUMPRODUCT()], ROUND(), ROUNDUP(), *ROUNDDOWN(), COUNT(), COUNTA(), SUMIF(), COUNTIF(), COUNTBLANK(), TRUNC(), 
*PMT(), PV(), FV(), POWER(), SQRT(), MODE(), TRUE, FALSE, 
*MODE(), LARGE(), SMALL(), RANK(), STDEV(), 
*DCOUNT(), DCOUNTA(), WEEKDAY(),


;Excel Keyboard [http://dmcritchie.mvps.org/excel/shortx2k.htm shortcuts needed to aid usability in Ignition] 
&lt;pre&gt;
Ctrl Z - Undo

Ctrl D - Fill Down
Ctrl R - Fill right

Ctrl F - Find
Ctrl H - Replace

Ctrl 1 - Formatting of Cells
CTRL SHIFT ~ Apply General Formatting ie a number 
Ctrl ; - Todays Date 

F2 - Edit cell
F4 - toggle cell absolute / relative cell references

&lt;/pre&gt;


====Document Scanning - Scandal====

Scanner usually needs to be connected via a USB port and not via a hub or extension lead.

Check in Trident Prefs -&gt; Devices that the USB Scanner is not bound to anything (e.g. Bindings None)
If not found then reboot the computer and recheck.

Start Scandal, choose Settings from Menu strip at top of screen and in Scanner Driver choose the ?#.device of the scanner (e.g. epson2.device).

The next two boxes - leave empty as they are for morphos SCSI use only
 or put ata.device (use the selection option in bigger box below) and Unit as 0 this is needed for gt68xx

* gt68xx - no editing needed in s/gt68xx.conf but needs a firmware file that corresponds to the scanner [http://www.meier-geinitz.de/sane/gt68xx-backend/ gt68xx firmwares] in sys:s/gt68xx.
* epson2 - Need to edit the file epson2.conf in sys/s that corresponds to the scanner being used

'''Save''' the settings but do not press the Use button (aros freezes)

Back to the Picture Scan window and the right-hand sections.

Click on the '''Information''' tab and press Connect button and the scanner should now be detected.

Go next to the '''Scanner''' tab next to Information Tab should have Color, Black and White, etc. and dpi settings now. Selecting an option Color, B/W etc. can cause dpi settings corruption (especially if the settings are in one line) so set '''dpi first'''. Make sure if Preview is set or not.

In the '''Scan''' Tab, press Scan and the scanner will do its duty. 
Be aware that nothing is saved to disk yet.

In the Save tab, change format JPEG, PNG or IFF DEEP. Tick incremental and base filename if necessary and then click the Save button. The image will now be saved to permanent storage.


The driver ignores a device if it is already bond to another USB class, rejects it from being usable. However, open Trident prefs, select your device and use the right mouse button to open. Select &quot;NONE&quot; to prevent poseidon from touching the device. Now save settings. It should always work now.

[[#top|...to the top]]

===Emulators===

==== Amiberry ====


==== Amiga Emu - Janus UAE ====

With Amibridge, AROS attempts to make the UAE emulator seem embedded within but it still is acting as an app 

There is no dynarec m68k for each hardware that Aros supports or direct patching of motorola calls to AROS hardware accelerated ones unless the emulator has that included 

Try starting Janus with a priority of -1 like this little script:
&lt;pre&gt;
cd sys:system/AmiBridge/emulator
changetaskpri -1
run janus-uae -f my_uaerc.config &gt;nil:
cd sys:prefs
endcli
&lt;/pre&gt;
This stops Janus hogging all the CPU time.


===Miscellaneous===

====Screensaver Blanker====

Most blankers on the amiga (i.e. aros) run as commodities (they are in the tools/commodities drawer). Double click on blanker.

Control is with an app called Exchange, which you need to run first (double click on app) or  run QUIET sys:tools/commodities/Exchange &gt;NIL: but subsequently can use (Cntrl Alt h).

Icon tool types (may be broken) or command line options 
&lt;pre&gt;
seconds=number 
&lt;/pre&gt;

Once the timing is right then add the following to s:icaros-sequence or s:user-startup

e.g. for 5 minutes

 run QUIET sys:tools/commodities/Blanker seconds=300 &gt;NIL:


*[http://archives.aros-exec.org/index.php?function=showfile&amp;file=graphics/screenblanker/gblanker.i386-aros.zip Garshneblanker] can make Aros unstable or slow. Certain blankers crashes in Icaros 2.0.x like Dragon, Executor.


*[ Acuario AROS version], the aquarium screen saver.

Startup: extras:acuariofv-aros/acuario

Kill: c:break name=extras:acuariofv-aros/acuario

Managed to start Acuario by the Executor blanker.

&lt;pre&gt;
cx_priority=
cx_popkey=    ie CX_POPKEY=&quot;Shift F1&quot; 
cx_popup=Yes or No

&lt;/pre&gt;


&lt;pre&gt;
 Qualifier String    Input Event Class
   ----------------    -----------------
    &quot;lshift&quot;           IEQUALIFIER_LSHIFT
    &quot;rshift&quot;           IEQUALIFIER_RSHIFT
    &quot;capslock&quot;         IEQUALIFIER_CAPSLOCK
    &quot;control&quot;          IEQUALIFIER_CONTROL
    &quot;lalt&quot;             IEQUALIFIER_LALT
    &quot;ralt&quot;             IEQUALIFIER_RALT
    &quot;lcommand&quot;         IEQUALIFIER_LCOMMAND
    &quot;rcommand&quot;         IEQUALIFIER_RCOMMAND
    &quot;numericpad&quot;       IEQUALIFIER_NUMERICPAD
    &quot;repeat&quot;           IEQUALIFIER_REPEAT
    &quot;midbutton&quot;        IEQUALIFIER_MIDBUTTON
    &quot;rbutton&quot;          IEQUALIFIER_RBUTTON
    &quot;leftbutton&quot;       IEQUALIFIER_LEFTBUTTON
    &quot;relativemouse&quot;    IEQUALIFIER_RELATIVEMOUSE
&lt;/pre&gt;


&lt;pre&gt;
    Synonym     Synonym
    String     Identifier
    -------    ----------
    &quot;shift&quot;    IXSYM_SHIFT    /* look for either shift key */
    &quot;caps&quot;     IXSYM_CAPS     /* look for either shift key or capslock */
    &quot;alt&quot;      IXSYM_ALT      /* look for either alt key */

Highmap is one of the following strings:
    &quot;space&quot;, &quot;backspace&quot;, &quot;tab&quot;, &quot;enter&quot;, &quot;return&quot;, &quot;esc&quot;, &quot;del&quot;,
    &quot;up&quot;, &quot;down&quot;, &quot;right&quot;, &quot;left&quot;, &quot;f1&quot;, &quot;f2&quot;, &quot;f3&quot;, &quot;f4&quot;, &quot;f5&quot;,
    &quot;f6&quot;, &quot;f7&quot;, &quot;f8&quot;, &quot;f9&quot;, &quot;f10&quot;, &quot;help&quot;.


&lt;/pre&gt;


[[#top|...to the top]]

==== World Construction Set WCS (Version 2.031) ====

WCS is a fractal landscape software such as Scenery Animator, Vista Pro and Panorama. Open sourced February 2022, World Construction Set [https://3dnature.com/downloads/legacy-software/ legally and for free] and [https://github.com/AlphaPixel/3DNature c source]. 

Announced August 1994 this version dates from April 1996 developed by Gary R. Huber and Chris &quot;Xenon&quot; Hanson&quot; from Questar 

&lt;pre&gt;
Assign &quot;WCSProjects:&quot; &quot;Volume:Dir/Dir/WCSProjects&quot; 
Assign &quot;WCSFrames:&quot;   &quot;Volume:Dir/Dir/WCSFrames&quot; 
&lt;/pre&gt;

&lt;pre&gt;
Load projects .proj by accessing pull down menu Project -&gt; Open then click on CanyonSunset.proj
OK to changing .par file and enlarge Status Log window to show what is happening 
Render by pull down menu Modules -&gt; Render with End equal 1 not 300 then click bottom middle button Render 
&lt;/pre&gt;

[https://www.youtube.com/watch?v=CxQDmf1ZWG0 Youtube walkthrough of above], [], [], 

Also try working with the already built file ColoDemo - Then open with the drop-down menu: Project/Open, then WCSProject:ColoDemo.proj
Which allows you to use altimetric DEM files already included and Loading scene parameters from ColoDemo.par
Once this is done, save everything with a new name to start working exclusively on your project. 
Then drop-down menu and select Save As (&quot;NewName&quot;.proj name), then drop-down menu to open parameter and select Save All ( .par name)


After launching the software, there is a the Module Control Panel composed of five icons. 
It is a dock type shortcut of the first few functions of the drop-down menu 

*Database   - Load (#?.proj), Append, Create, Edit, Save, Dir List (of WCSProject drawer), 
*Data Ops   - Extract / Convert Interp DEM, Import DLG, DXF, WDB and export LW map 3d formats  
*Map View   - Database file Loader leading to Map View Control with option to the Database Editor 
*Parameters - Editor for Motion, Color, Ecosystem, Clouds, Waves, management of altimeter files DEM, sclock settings etc 
*Render     - rendering terrain 

These are more in the pull down menu but not in the dock 
*Motion Editor
*Color Editor
*Ecosys Editor 


Simple minimal workflow 
*Load database (1st icon - 1st)
*Set parameters and save .par file (4th icon)
*Render scene (5th icon) 

[https://www.youtube.com/watch?v=ZbTwwR2qcc4 Youtube], [], 

&lt;pre&gt;
.proj new project name which creates a drawer of additional files 

.binary array, ascii array .xyz , z buffer, DTED .dt0, vista 1990s dem, iff  conversion 
.Obj with .elev, .frd with .hdr maps, - digital elevation model (DEM) is a 3D representation of elevation data in various formats 
USGS 7.5MinDEM, 

.par 


&lt;/pre&gt;


Since for the time being no project is loaded, a query window indicates a procedural error when clicking on the rendering icon (right end of the bar). The menu is quite traditional; it varies according to the activity of the windows. To display any altimetric file in the &quot;Mapview&quot; (third icon of the panel), There are three possibilities:

* Loading of a demonstration project.
* The import of a DEM file, followed by texturing and packaging from the &quot;Database-Editor&quot; and the &quot;Color-Editor&quot;.
* The creation of an altimetric file in WCS format, then texturing.


The altimeter file editing (display in the menu) is only made possible if the &quot;Mapview&quot; window is active.

The software is made up of many windows and won't be able to describe them all. Know that &quot;Color-Editor&quot; and the &quot;Data-Editor&quot; comprise sufficient functions for obtaining an almost real rendering quality. You have the possibility of inserting vector objects in the &quot;Data-Editor&quot; (creation of roads, railways, etc.) 


The Map View (MapView) window

*Database - Objects and Topos
*View     - Align, Center, Zoom, Pan, Move 
*Draw     - Maps and distance 
*Object   - Find, highlight, add points, conform topo, duplicate 
*Motion   - Camera, Focus, path, elevation 
*Windows  - DEM designer, Cloud (.cld) and wave (.wve) editor, 


You will notice that by selecting this window and simply moving the pointer to various points on the map you will see latitude and longitude values ​​change, along with the height.
Drop-down menu and Modules, then select MapView and change the width of the window with the map to arrange it in the best way on the screen. With the Auto button the center. Window that then displays the contents of my DEM file, in this case the Grand Canyon. MapView allows you to observe the shape of the landscape from above
 

ZOOM button

Press the Zoom button and then with the pointer position on a point on the map, press the left mouse button and then move to the opposite corner to circumscribe the chosen area and press the left mouse button again, then we will see the enlarged area selected on the map.
Would add that there is a box next to the Zoom button that allows the direct insertion of a value which, the larger it is, the smaller the magnification and the smaller the value, the stronger the magnification. At each numerical change you will need to press the DRAW button to update the view.

PAN button

Under Zoom you will find the PAN button which allows you to move the map at will in all directions by the amount you want. This is done by drawing a line in one direction, then press PAN and point to an area on the map with the pointer and press the left mouse button. At this point, leave it and move the pointer in one direction by drawing a line and press the left mouse button again to trigger the movement of the map on the screen (origin and end points). Do some experiments and then use the Auto button immediately below to recenter everything.
There are parameters such as TOPO, VEC to be left checked and immediately below one that allows different views of the map with the Style command (Single, Multi, Surface, Emboss, Slope, Contour), each with its own particularities to highlight different details.

Now you have the first basics to manage your project visually on the map. Close the MapView window and go further...


Let's start working on ECOSYSTEMS
If we select Emboss from the MapView Style command we will have a clear idea of ​​how the landscape appears, realizing that it is a predominantly desert region of our planet. Therefore we will begin to act on any vegetation present and the appearance of the landscape.
With WCS we will begin to break down the elements of the landscape by assigning defined characteristics. It will be necessary to determine the classes of the ecosystem (Class) with parameters of Elevation Line (maximum altitude), Relative Elevation (arrangement on basins or convexities with respectively positive or negative parameters), Min Slope and Max Slope (slope). WCS offers the possibility of making ecosystems coexist on the same terrain with the UnderEco function, by setting a Density value.


Ecosys Ecosystem Editor

Let's open it from Modules, then Ecosys Editor. In the left pane you will find the list of ecosystems referring to the files present in our project. It will be necessary to clean up that box to leave only the Water and Snow landscapes and a few other predefined ones. We can do this by selecting the items and pressing the Remove button (be careful not for all elements the button is activated, therefore they cannot all be eliminated).
Once this is done we can start adding new ecosystems. Scroll through the various Unused and as soon as the Name item at the top is activated allowing you to write, type the name of your ecosystem, adding the necessary parameters.
&lt;pre&gt;
Ecosystem1: Name: RockBase Class: Rock Density: 80 MinSlope: 15 UnderEco: Terrain
Ecosystem2: Name: RockIncl Clss: Rock Density: 80 MinSlope: 30 UnderEco: Terrain
Ecosystem3: Name: Grass Class Low Veg Density: 50 Height: 1 Elev Line : 1500 Rel El Eff: 5
Max Slope: 10 – Min Slope: 0 UnderEco: Terrain
Ecosistema4: Name: Shrubs Class: Low Veg Density: 40 Height: 8 Elev Line: 3000
Rel El Eff: -2 Max Slope: 20 Min Slope : 5 UnderEco: Terrain
Ecosistema5: Name: Terrain Class: Ground Density: 100 UnderEco: Terrain
&lt;/pre&gt;

Now we need to identify an intermediate ecosystem that guarantees a smooth transition between all, therefore we select as Understory Ecosystem the one called Terrain in all ecosystems, except Snow and Water .
Now we need to 'emerge' the Colorado River in the Canyon and we can do this by raising the sea level to 900 (Sea Level) in the Ecosystem called Water.
Please note that the order of the ecosystem list gives priority to those that come after. So our list must have the following order: Water, Snow, Shrubs, RockIncl, RockBase, Terrain. It is possible to carry out all movements with the Swap button at the bottom. To put order you can also press Short List. Press Keep to confirm all the work done so far with Ecosystem Editor.
Remember every now and then to save both the Project 'Modules/Save' and 'Parameter/Save All'

EcoModels are made up of .etp .fgp .iff8 for each model 


Color Editor

Now it's time to define the colors of our scene and we can do this by going to Modules and then Color Editor. In the list we focus on our ecosystems, created first.
Let's go to the bottom of the list and select the first white space, assigning the name 'empty1', with a color we like and then we will find this element again in other environments... It could serve as an example for other situations!
So we move to 'grass' which already exists and assign the following colors: R 60 G 70 B50
&lt;pre&gt;
'shrubs': R 60 G 80 B 30
'RockIncl' R 110 G 65 B 60
'RockBase' R 110 G 80 B 80
' Terrain' R 150 G 30 B 30
&lt;pre&gt;
Now we can work on pre-existing colors
&lt;pre&gt;
'SunLight' R 150 G 130 B 130
'Haze and Fog' R 190 G 170 B 170
'Horizon' R 209 G 185 B 190
'Zenith' R 140 G 150 B 200
'Water' R 90 G 125 B 170
&lt;/pre&gt;

Ambient R 0 G 0 B 0

So don't forget to close Color Editor by pressing Keep.
Go once again to Ecosystem Editor and assign the corresponding color to each environment by selecting it using the Ecosystem Color button. Press it several times until the correct one appears. Then save the project and parameters again, as done previously.


Motion Editor

Now it's time to take care of the framing, so let's go to Modules and then to Motion Editor. An extremely feature-rich window will open. Following is the list of parameters regarding the Camera, position and other characteristics:
&lt;pre&gt;
-Camera Altitude: 7.0
-Camera Latitude: 36.075
-Camera Longitude: 112.133
-Focus Attitude: -2.0
-Focus Latitude: 36.275
-Focus Longitude: 112.386
-Camera : 512 → rendering window
-Camera Y: 384 → rendering window
-View Arc: 80 → View width in degrees
-Sun Longitude: 172
-Sun Latitude: -0.9
-Haze Start: 3.8
-Haze Range: 78, 5
&lt;/pre&gt;
As soon as the values ​​shown in the relevant sliders have been modified, we will be ready to open the CamView window to observe the wireframe preview. Let's not consider all the controls that will appear.
Well from the Motion Editor if you have selected Camera Altitude and open the CamView panel, you can change the height of the camera by holding down the right mouse button and moving the mouse up and down. To update the view, press the Terrain button in the adjacent window. As soon as you are convinced of the position, confirm again with Keep. You can carry out the same work with the other functions of the camera, such as Focus Altitude...
Let's now see the next positioning step on the Camera map, but let's leave the CamView preview window open while we go to Modules to open the window at the same time MapView. We will thus be able to take advantage of the view from the other together with a subjective one.


From the MapView window, select with the left mouse button and while it is pressed, move the Camera as desired. To update the subjective preview, always click on Terrain.
While with the same procedure you can intervene on the direction of the camera lens, by selecting the cross and with the left button pressed you can choose the desired view. So with the pressure of Terrain I update the Preview. Possibly can enlarge or reduce the Map View using the Zoom button, for greater precision.
Also write that the circle around the cameras indicates the beginning of the haze, there are two types (haze and fog) linked to the altitude. Would also add that the camera height is editable through the Motion Editor panel.


The sun

Let's see that changing the position of the sun from the Motion Editor. Press the SUN button at the bottom right and set the time and the date. Longitude and latitude are automatically obtained by the program. Always open the View Arc command from the Motion Editor panel, an item present in the Parameter List box.

Once again confirm everything with Keep and then save again.


Animation

The animation part is not left-back and also occupies a window. The settings possibilities are enormous. A time line with dragging functions (&quot;slide&quot;, &quot;drag&quot;...) comparable to that of LightWave completes this window. 


A small window is available for positioning the stars as a function of a date, in order to vary the seasons and their various events (and yes...).

At the bottom of the &quot;Motion-Editor&quot;, a &quot;cam-view&quot; function will give you access to a control panel. Different preview modes are possible. The rendering is also accessible through a window. No less than nine pages compose it. At this level, you will be able to determine the backup name of your images (&quot;path&quot;), the type of texture to be calculated, the resolution of the images, activate or deactivate functions such as the depth buffer (&quot;zbuffer&quot;), the blur, the background image, etc.


Once all these parameters have been set, all you have to do is click on the &quot;Render&quot; button.

For rendering go to Modules and then Render. Select the resolution, then under IMA select the name of the image. Move to FRA and indicate the level of fractal detail which of 4 is quite good. Then Keep to confirm and then reopen the window, pressing Render you will see the result. The image will be opened with any viewing program.


Strengths:

* Multi-window.
* Quality of rendering.
* Accuracy.
* Opening, preview and rendering on CyberGraphX screen.
* Extract / Convert Interp DEM, Import DLG, DXF, WDB and export LW map 3d formats 
* The &quot;zbuffer&quot; function.

Weaknesses:

* No OpenGL management 
* Calculation time.
* No network computing tool.


====Writing CD / DVD - Frying Pan====

Can be backup DVDs (4GB ISO size limit due to use of FileInfoBlock), create audio cds from mp3's, and put .iso files on discs

If using for the first time - click Drive button and Device set to ata.device and unit to 0 (zero)

Click Tracks Button - Drive 1 - Create New Disc or Import Existing Disc Image (iso bin/cue etc.) - Session File open cue file

If you're making a data cd, with files and drawers from your hard drive, you should be using the ISO Builder.. which is the MUI page on the left. (&quot;Data/Audio Tracks&quot; is on the right).

You should use the &quot;Data/Audio tracks&quot; page if you want to create music cds with AIFF/WAV/MP3 files, or if you download an .iso file, and you want to put it on a cd.

Click WRITE Button - set write speed - click on long Write button

Examples

Easiest way would be to burn a DATA CD, simply go to &quot;Tracks&quot; page &quot;ISO Builder&quot; and &quot;ADD&quot; everything you need to burn.

On the &quot;Write&quot; page i have &quot;Masterize Disc (DAO)&quot;, &quot;Close Disc&quot; and &quot;Eject after Write&quot; set.

One must not &quot;Blank disc before write&quot; if one uses a CDR


AUDIO CD from MP3's are as easy but tricky to deal with. FP only understands one MP3 format, Layer II, everything else will just create empty tracks

Burning bootable CD's works only with .iso files. Go to &quot;Tracks&quot; page and &quot;Data/Audio Tracks&quot; and add the .iso


====odf====

Every ODF file is a collection of several subdocuments within a package (ZIP file), each of which stores part of the complete document.

* content.xml – Document content and automatic styles used in the content.
* styles.xml – Styles used in the document content and automatic styles used in the styles themselves.
* meta.xml – Document meta information, such as the author or the time of the last save action.
* settings.xml – Application-specific settings, such as the window size or printer information.


To read document follow these steps:

* Extracting .ods file.
* Getting content.xml file (which contains sheets data).
* Creating XmlDocument object from content.xml file.
* Creating DataSet (that represent Spreadsheet file).
* With XmlDocument select “table:table” elements, and then create adequate DataTables.
* Parse child’s of “table:table” element and fill DataTables with those data.
* At the end, return DataSet and show it in application’s interface.


To write document follow these steps:

* Extracting template.ods file (.ods file that we use as template).
* Getting content.xml file.
* Creating XmlDocument object from content.xml file.
* Erasing all “table:table” elements from the content.xml file.
* Reading data from our DataSet and composing adequate “table:table” elements.
* Adding “table:table” elements to content.xml file.
* Zipping that file as new .ods file.

XLS file format

The XLS file format contains streams, substreams, and records.

These sheet substreams include worksheets, macro sheets, chart sheets, dialog sheets, and VBA module sheets. 
All the records in an XLS document start with a 2-byte unsigned integer to specify Record Type (rt), and another for Count of Bytes (cb). A record cannot exceed 8224 bytes. If larger than the rest is stored in one or more continue records.

* Workbook stream 
**Globals substream
***BoundSheet8 record - info for Worksheet substream i.e. name, location, type, and visibility. (4bytes the lbPlyPos FilePointer, specifies the position in the Workbook stream where the sheet substream starts) 
**Worksheet substream (sheet) - Cell Table - Row record - Cells (2byte=row 2byte=column 2byte=XF format)
***Blank cell record
***RK cell record 32-bit number. 
***BoolErr cell record (2-byte Bes structure that may be either a Boolean value or an error code)
***Number cell record (64-bit floating-point number)
***LabelSst cell record (4-byte integer that specifies a string in the Shared Strings Table (SST). Specifically, the integer corresponds to the array index in the RGB field of the SST)
***Formula cell record (FormulaValue structure in the 8 bytes that follow the cell structure. The next 6 bytes can be ignored, and the rest of the record is a CellParsedFormula structure that contains the formula itself)
***MulBlank record (first 2 bytes give the row, and the next 2 bytes give the column that the series of blanks starts at. Next, a variable length array of cell structures follows to store formatting information, and the last 2 bytes show what column the series of blanks ends on)
***MulRK record 
***Shared String Table (SST) contains all of the string values in the workbook.

ACCRINT(), ACCRINTM(), AMORDEGRC(), AMORLINC(), 
COUPDAYBS(), COUPDAYS(), COUPDAYSNC(), COUPNCD(), COUPNUM(), COUPPCD(), 
CUMIPMT(), CUMPRINC(), 
DB(), DDB(), DISC(), 
DOLLARDE(), DOLLARFR(), 
DURATION(), EFFECT(), FV(), FVSCHEDULE(), 
INTRATE(), IPMT(), IRR(), ISPMT(), MDURATION(), MIRR(), NOMINAL(), NPER(), NPV(), 
ODDFPRICE(), ODDFYIELD(), ODDLPRICE(), ODDLYIELD(), 
PMT(), PPMT(), PRICE(), PRICEDISC(), PRICEMAT(), PV(), RATE(), 
RECEIVED(), SLN(), SYD(), TBILLEQ(), TBILLPRICE(), TBILLYIELD(), 
VDB(), XIRR(), XNPV(), YIELD(), YIELDDISC(), YIELDMAT(),


&lt;pre&gt;
&lt;/pre&gt;


&lt;pre&gt;
&lt;/pre&gt;

&lt;pre&gt;
&lt;/pre&gt;

{{BookCat}}</text>
      <sha1>a9gp09vxdqw25pp8d3wwamj1evnrhhv</sha1>
    </revision>
    <revision>
      <id>4656055</id>
      <parentid>4656054</parentid>
      <timestamp>2026-08-02T16:40:15Z</timestamp>
      <contributor>
        <username>Jeff1138</username>
        <id>301139</id>
      </contributor>
      <minor />
      <origin>4656055</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="236003" sha1="4ot4sgo40ufazllv73fr7c5ru3hxntp" xml:space="preserve">
==Introduction==


[[#Graphical Image Editing Art]]
[[#Office Application]]
[[#Audio]]

[[#Misc Application]]
[[#Games &amp; Emulation]]

[[#Application Guides]]

[[#top|...to the top]]


[[#top|...to the top]]

Most apps can be opened on the Workbench (aka publicscreen pubscreen) which is the default display option but can offer a custom one set to your configurations (aka custom screen mode promotion). These custom ones tend to stack so the possible use of A-M/A-N method of switching between full screens and the ability to pull down screens as well 

If you are interested in creating or porting new software, see [http://en.wikibooks.org/wiki/Aros/Developer/Docs here]

{|  class=&quot;wikitable sortable&quot; 
|- 
!width:30%;|Internet Applications 
!width:10%;|AROS(x86)
!width:10%;|Commodore-Amiga OS 3.1 (68k)
!width:10%;|Hyperion OS4(PPC)
!width:10%;|MorphOS(PPC)
|-
|&lt;!--Sub Menu--&gt;Web Online Browser [], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=network/browser Odyssey 2.0], [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=1175&amp;highlight=odyssey&amp;rowstart=100 Odyssey 3.0], 
|&lt;!--Amiga OS--&gt;[https://aminet.net/comm/www Amelinium], [https://blog.alb42.de/programs/amifox/ amifox] with [https://github.com/alb42/wrp wrp server], IBrowse*, Voyager*, [https://github.com/amigazen/aweb3/ AWeb 3.6 src], [https://github.com/matjam/aweb AWeb Src], [http://aminet.net/package/comm/www/NetSurf-m68k-sources Netsurf], [], 
|&lt;!--AmigaOS4--&gt;[ Odyssey OWB], [ Timberwolf (Firefox port 2011)], [http://amigaworld.net/modules/newbb/viewtopic.php?forum=32&amp;topic_id=32847 OWB-mui], [http://strohmayer.org/owb/ OWB-Reaction], IBrowse*, [http://os4depot.net/index.php?function=showfile&amp;file=network/browser/aweb.lha AWeb], Voyager, [http://www.os4depot.net/index.php?function=browse&amp;cat=network/browser Netsurf], 
|&lt;!--MorphOS--&gt;Wayfarer, [http://fabportnawak.free.fr/owb/ Odyssey OWB], [ Netsurf], IBrowse*, AWeb, [], 
|-
|&lt;!--Sub Menu--&gt;YouTube, Dailymotion website downloading videos audio [https://github.com/yt-dlp/yt-dlp yt-dlp], [https://clipgrab.org/ clipgrab],  
|&lt;!--AROS--&gt;[], [https://blog.alb42.de/amitube/ Amitube], 
|&lt;!--Amiga OS--&gt;[https://blog.alb42.de/amitube/ Amitube], [ smtube], 
|&lt;!--AmigaOS4--&gt;[https://blog.alb42.de/amitube/ Amitube], getVideo, Tubexx, [https://github.com/walkero-gr/aiostreams aiostreams], 
|&lt;!--MorphOS--&gt;[ ytsearch], [https://blog.alb42.de/amitube/ Amitube], [http://morphos.lukysoft.cz/en/vypis.php?kat=5 getVideo], Tubexx 
|-
|&lt;!--Sub Menu--&gt;Old style E-mailing SMTP POP3 IMAP based 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=network/email SimpleMail], [http://sourceforge.net/projects/simplemail/files/ src], [https://github.com/jens-maus/yam YAM] 
|&lt;!--Amiga OS--&gt;[http://sourceforge.net/projects/simplemail/files/ SimpleMail], [https://github.com/jens-maus/yam YAM]
|&lt;!--AmigaOS4--&gt;SimpleMail, YAM, 
|&lt;!--MorphOS--&gt; SimpleMail, YAM
|-
|&lt;!--Sub Menu--&gt;IRC 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=network/chat WookieChat], [https://sourceforge.net/projects/wookiechat/ Wookiechat src], [http://archives.arosworld.org/index.php?function=browse&amp;cat=network/chat AiRcOS], Jabberwocky, 
|&lt;!--Amiga OS--&gt;Wookiechat, AmIRC 
|&lt;!--AmigaOS4--&gt;Wookiechat 
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=5 Wookiechat], [http://morphos.lukysoft.cz/en/vypis.php?kat=5 AmIRC], 
|-
|&lt;!--Sub Menu--&gt;Instant Messaging IM like [https://github.com/BlitterStudio/amidon Hollywood lang based Mastodon client], BlueSky AT protocol, Facebook(TM), Twitter X (TM), Bitlbee IRC Gateway and others 
|&lt;!--AROS--&gt;[https://github.com/kaffeine1/telegram-amiga telegram-amiga], [http://archives.arosworld.org/index.php?function=browse&amp;cat=network/chat jabberwocky], 
|&lt;!--Amiga OS--&gt;[http://amitwitter.sourceforge.net/ AmiTwitter], CLIMM, SabreMSN, jabberwocky, 
|&lt;!--AmigaOS4--&gt;[http://amitwitter.sourceforge.net/ AmiTwitter], SabreMSN,
|&lt;!--MorphOS--&gt;[http://amitwitter.sourceforge.net/ AmiTwitter], [http://morphos.lukysoft.cz/en/vypis.php?kat=5 PolyglotNG], SabreMSN,
|-
|&lt;!--Sub Menu--&gt;Torrents 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=network/p2p ArTorr], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;CTorrent, Transmission 
|&lt;!--MorphOS--&gt;MLDonkey, Beehive, [http://morphos.lukysoft.cz/en/vypis.php?kat=5 Transmission], CTorrent, 
|-
|&lt;!--Sub Menu--&gt;FTP 
|&lt;!--AROS--&gt;[https://github.com/BlitterStudio/dopus5 Dopus5 Magellan], MarranoFTP, 
|&lt;!--Amiga OS--&gt;[https://github.com/BlitterStudio/dopus5 Dopus5 Magellan], [http://aminet.net/package/comm/tcp/AmiFTP AmiFTP], AmiTradeCenter, ncFTP, 
|&lt;!--AmigaOS4--&gt;[https://github.com/BlitterStudio/dopus5 Dopus5 Magellan], 
|&lt;!--MorphOS--&gt;[https://github.com/BlitterStudio/dopus5 Dopus5 Magellan], [http://morphos.lukysoft.cz/en/vypis.php?kat=5 Pftp], [http://aminet.net/package/comm/tcp/AmiFTP-1.935-OS4 AmiFTP], 
|-
|&lt;!--Sub Menu--&gt;WYSIWYG Web Site Editor
|&lt;!--AROS--&gt; 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Internet Radio Streaming Audio [http://www.gnu.org/software/gnump3d/ gnump3d], [http://www.icecast.org/ Icecast2] Server (Broadcast) and Client (Listen), [ mpd], [http://darkice.sourceforge.net/ DarkIce], [http://www.dyne.org/software/muse/ Muse], 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=audio/misc ], Mplayer (Icecast Client only), 
|&lt;!--Amiga OS--&gt;[https://github.com/sandlbn/TuneFinder TuneFinder C Src], [https://github.com/sandlbn/TuneFinderMUI TuneFinderMUI], [http://amigazeux.net/anr/ AmiNetRadio], [], [], 
|&lt;!--AmigaOS4--&gt;[http://www.tunenet.co.uk/ Tunenet], 
|&lt;!--MorphOS--&gt;Mplayer, AmiNetRadio, 
|-
|&lt;!--Sub Menu--&gt;VoIP (Voice over IP) with SIP Client (Session Initiation Protocol) or Asterisk IAX2 Clients Softphone (skype like) 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;AmiPhone with Speak Freely, 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Weather Forecast 
|&lt;!--AROS--&gt;[http://sourceforge.net/projects/zunetools/files/ WeatherBar], [http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/workbench AWeather], []
|&lt;!--Amiga OS--&gt;[http://amigazeux.net/wetter/ Wetter], [https://github.com/emartisoft/AmiWeatherForecasts AmiWeatherForecasts src], 
|&lt;!--AmigaOS4--&gt;[http://os4depot.net/?function=showfile&amp;file=utility/workbench/flipclock.lha FlipClock], 
|&lt;!--MorphOS--&gt;[http://amigazeux.net/wetter/ Wetter], 
|-
|&lt;!--Sub Menu--&gt;Street Road Maps Route Planning GPS Tracking  
|&lt;!--AROS--&gt;[https://blog.alb42.de/programs/muimapparium/ MuiMapparium] [https://build.alb42.de/ Build of MuiMapp versions], 
|&lt;!--Amiga OS--&gt;AmiAtlas*, UKRoutePlus*, [http://blog.alb42.de/ AmOSM], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;[http://blog.alb42.de/programs/mapparium/ Mapparium], 
|-
|&lt;!--Sub Menu--&gt;Clock and Date setting from the internet (either ntp or websites) [https://www.timeanddate.com/worldclock/ World Clock], [http://www.time.gov/ NIST], [], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=network/misc ntpsync],  
|&lt;!--Amiga OS--&gt;ntpsync 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Newsgroups
|&lt;!--AROS--&gt; 
|&lt;!--Amiga OS--&gt;[http://newscoaster.sourceforge.net/ Newscoaster], [https://github.com/jens-maus/newsrog NewsRog], [ WorldNews], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|}

&lt;nowiki&gt;*&lt;/nowiki&gt; Commercial product.


==Graphical Image Editing Art==
{|  class=&quot;wikitable sortable&quot; 
|- 
!width:30%;|Image Editing
!width:10%;|AROS(x86)
!width:10%;|Commodore-Amiga OS 3.1(68k)
!width:10%;|Hyperion OS4(PPC)
!width:10%;|MorphOS(PPC)
|-
|&lt;!--Sub Menu--&gt;Pixel Raster Artwork [https://github.com/LibreSprite/LibreSprite LibreSprite based on GPL aseprite], [https://github.com/abetusk/hsvhero hsvhero], [], 
|&lt;!--AROS--&gt;[https://sourceforge.net/projects/zunetools/files/ZunePaint/ ZunePaint], [http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/edit LunaPaint], [http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/edit GrafX2], [ LodePaint needs OpenGL], 
|&lt;!--Amiga OS--&gt;[http://www.amigaforever.com/classic/download.html PPaint], GrafX2, [https://github.com/grovdata/Amiga_Sources/blob/master/software.md DeluxePaint], [http://www.amiforce.de/perfectpaint/perfectpaint.php PerfectPaint], Zoetrope, Brilliance2*, 
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=graphics/edit LodePaint], GrafX2, 
|&lt;!--MorphOS--&gt;Sketch, Pixel*, GrafX2, [http://morphos.lukysoft.cz/en/vypis.php?kat=3 LunaPaint]
|-
|&lt;!--Sub Menu--&gt;Image viewing 
|&lt;!--AROS--&gt;[http://sourceforge.net/projects/zunetools/files/ ZuneView], [http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/viewer LookHere], [http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/viewer LoView], [http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/viewer PicShow] , [http://amigaworld.net/modules/newbb/viewtopic.php?mode=viewtopic&amp;topic_id=31400&amp;forum=32&amp;start=80&amp;viewmode=flat&amp;order=0#583458 Picture Album], 
|&lt;!--Amiga OS--&gt;PicShow, PicView, Photoalbum,
|&lt;!--AmigaOS4--&gt;WarpView, PicShow, flPhoto, Thumbs, [http://amigaworld.net/modules/newbb/viewtopic.php?mode=viewtopic&amp;topic_id=31400&amp;forum=32&amp;start=80&amp;viewmode=flat&amp;order=0#583458 Picture Album], 
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=3 ShowGirls], [http://amigaworld.net/modules/newbb/viewtopic.php?mode=viewtopic&amp;topic_id=31400&amp;forum=32&amp;start=80&amp;viewmode=flat&amp;order=0#583458 Picture Album]
|-
|&lt;!--Sub Menu--&gt;Photography retouching / Image Manipulation like Photoshop(tm)  
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/edit RNOEffects], [https://sourceforge.net/projects/zunetools/files/ ZunePaint], [http://sourceforge.net/projects/zunetools/files/ ZuneView], 
|&lt;!--Amiga OS--&gt;[ Tecsoft Video Paint aka TVPaint], Photogenics*, ArtEffect*, ImageFX*, XiPaint, fxPaint, ImageMasterRT, Opalpaint, 
|&lt;!--AmigaOS4--&gt;WarpView, flPhoto, [http://www.os4depot.net/index.php?function=browse&amp;cat=graphics/edit Photocrop]
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=3 ShowGirls], ImageFX*, 
|-
|&lt;!--Sub Menu--&gt;Manage RAW picture folder galleries like Darktable, RAWtherapy, etc 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Graphic Format Converter - ICC profile support sRGB, Adobe RGB, XYZ and linear RGB 
|&lt;!--AROS--&gt; 
|&lt;!--Amiga OS--&gt;GraphicsConverter, ImageStudio, [http://www.coplabs.org/artpro.html ArtPro]
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Thumbnail Generator [], 
|&lt;!--AROS--&gt;[http://sourceforge.net/projects/zunetools/files/ ZuneView], [http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/shell Thumbnail Generator]
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Icon Editor
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/iconedit Archives], [http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/workbench Icon Toolbox], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=graphics/iconedit IconEditor]
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;2D Pixel Art Animation 
|&lt;!--AROS--&gt;Lunapaint
|&lt;!--Amiga OS--&gt;PPaint, AnimatED, Scala*, GoldDisk MovieSetter*, Walt Disney's Animation Studio*, ProDAD*, [https://github.com/historicalsource/DeluxePaint DeluxePaint src], Brilliance
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=3 Titler] 
|-
|&lt;!--Sub Menu--&gt;2D SVG based MovieSetter type 
|&lt;!--AROS--&gt; 
|&lt;!--Amiga OS--&gt;MovieSetter*, Fantavision*
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Morphing 
|&lt;!--AROS--&gt;[ GLMorph]
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;2D Cad (qcad-&gt;LibreCAD, etc.) 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;Xcad, MaxonCAD
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;3D Cad like FreeCad, BRL-CAD, OpenSCAD, AvoCADo, etc. using dxf, obj (vertices), blend, 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;XCad3d*, DynaCADD*, Cycas, 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;3D Model Rendering of glft (json) gbl (png jpg), usdz (USD files with materials, textures, and animations), FBX Filmbox is a proprietary Autodesk format, 
|&lt;!--AROS--&gt;POV-Ray
|&lt;!--Amiga OS--&gt;[http://www.discreetfx.com./amigaproducts.html CINEMA 4D]*, POV-Ray, Lightwave3D*, Real3D*, Caligari24*, Reflections/Monzoom*, [https://github.com/privatosan/RayStorm Raystorm src], Tornado 3D
|&lt;!--AmigaOS4--&gt;Blender, POV-Ray, Yafray
|&lt;!--MorphOS--&gt;Blender, POV-Ray, Yafray
|-
|&lt;!--Sub Menu--&gt;3D Format Converter [], [], 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/?function=showfile&amp;file=graphics/convert/ 3doc.i386-aros], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=showfile&amp;file=graphics/convert/ivcon.lha IVCon]
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt; 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Screen grabbing display 
|&lt;!--AROS--&gt;[ Screengrabber], [http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/misc snapit], [http://archives.arosworld.org/index.php?function=browse&amp;cat=video/record screen recorder], []
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Grab graphics music from apps [https://github.com/Malvineous/ripper6 ripper6], [],
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt; 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|}

&lt;nowiki&gt;*&lt;/nowiki&gt; Commercial product.

[[#top|...to the top]]

==Office Application==
{|  class=&quot;wikitable sortable&quot; 
|- 
!width:30%;|Office
!width:10%;|AROS (x86)
!width:10%;|[http://en.wikipedia.org/wiki/Amiga_software Commodore-Amiga OS 3.1] (68k)
!width:10%;|[http://en.wikipedia.org/wiki/AmigaOS_4 Hyperion OS4] (PPC)
!width:10%;|[http://en.wikipedia.org/wiki/MorphOS MorphOS] (PPC)
|-
|&lt;!--Sub Menu--&gt;Word-processing 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=office/wordprocessing Cinnamon Writer], [https://finalwriter.godaddysites.com/ Final Writer 7*], [https://github.com/sodero/MUI-Vim/releases MUI-Vim], [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=1995&amp;rowstart=20&amp;pid=12668#post_12668 Slovo], [], 
|&lt;!--AmigaOS--&gt;[ Softwood FinalCopy II*], Haage AmigaWriter*, Digita WordWorth*, Softwood FinalWriter*, Micro-Systems Excellence 3*, Arnor Protext, Rashumon, [ InterWord], [ KindWords], [WordPerfect], [ New Horizons Flow], [ CygnusEd Pro], [ Micro-systems Scribble], 
|&lt;!--AmigaOS4--&gt;AbiWord, [ CinnamonWriter]
|&lt;!--MorphOS--&gt;[ Cinnamon Writer], [http://www.meta-morphos.org/viewtopic.php?topic=1246&amp;forum=53 scriba], [http://morphos.lukysoft.cz/en/index.php Papyrus Office], 
|-
|&lt;!--Sub Menu--&gt;Spreadsheets 
|&lt;!--AROS--&gt;[https://blog.alb42.de/programs/leu/ Leu], [https://archives.arosworld.org/index.php?function=browse&amp;cat=office/spreadsheet], 
|&lt;!--AmigaOS--&gt;[https://aminet.net/package/biz/spread/ignition-src Ignition Src 1.3], [MaxiPlan 500 Plus], [OXXI Plan/IT v2.0 Speadsheet], [ Superplan], [ Creative Developments TurboCalc], [ ProCalc], [ InterSpread], [Digita DGCalc], [ Gold Disk Advantage], [ Micro-systems Analyze!]
|&lt;!--AmigaOS4--&gt;Gnumeric, [https://ignition-amiga.sourceforge.net/ Ignition], 
|&lt;!--MorphOS--&gt;[ ignition], [http://morphos.lukysoft.cz/en/vypis.php Papyrus Office], 
|-
|&lt;!--Sub Menu--&gt;Presentations
|&lt;!--AROS--&gt;[http://www.hollywoood-mal.com/ Hollywood]*, 
|&lt;!--Amiga OS--&gt;[http://www.hollywoood-mal.com/ Hollywood]*, MediaPoint, PointRider, Scala*, 
|&lt;!--Amiga OS4--&gt;[http://www.hollywoood-mal.com/ Hollywood]*, PointRider 
|&lt;!--MorphOS--&gt;[http://www.hollywoood-mal.com/ Hollywood]*, PointRider
|-
|&lt;!--Sub Menu--&gt;Databases 
|&lt;!--AROS--&gt;[http://sdb.freeforums.org/ SDB], [http://archives.arosworld.org/index.php?function=browse&amp;cat=office/database BeeBase], 
|&lt;!--Amiga OS--&gt;Precision Superbase 4 Pro*, Arnor Prodata*, BeeBase, Datastore, FinalData*, AmigaBase, Fiasco, Twist2*, [Digita DGBase], [], 
|&lt;!--AmigaOS4--&gt;BeeBase, SQLite, 
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=6 BeeBase], 
|-
|&lt;!--Sub Menu--&gt;PDF Viewing and editing digital signatures 
|&lt;!--AROS--&gt;[http://sourceforge.net/projects/arospdf/ ArosPDF via splash], [https://github.com/wattoc/AROS-vpdf vpdf wip], 
|&lt;!--Amiga OS--&gt;APDF 
|&lt;!--AmigaOS4--&gt;AmiPDF 
|&lt;!--MorphOS--&gt;APDF, vPDF, 
|-
|&lt;!--Sub Menu--&gt;Printing 
|&lt;!--AROS--&gt;Postscript 3 laser printers and Ghostscript internal, [ GutenPrint], 
|&lt;!--Amiga OS--&gt;[http://www.irseesoft.de/tp_what.htm TurboPrint]* 
|&lt;!--AmigaOS4--&gt;(some native drivers), 
|&lt;!--MorphOS--&gt;early TurboPrint included, 
|-
|&lt;!--Sub Menu--&gt;Note Taking markdown support like Obsidian like, joplin, OneNote, EverNotes, xournalpp, etc 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Study and analyse, collect, organize, annotate, cite, and share
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;PIM Personal Information Manager - Day Diary Planner Calendar App 
|&lt;!--AROS--&gt;[ ], [ ], [ ], 
|&lt;!--Amiga OS--&gt;Digita Organiser*, On The Ball, Everyday Organiser, [ Contact Manager], 
|&lt;!--AmigaOS4--&gt;AOrganiser, 
|&lt;!--MorphOS--&gt;[http://polymere.free.fr/orga_en.html PolyOrga], 
|-
|&lt;!--Sub Menu--&gt;Accounting
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=office/misc ETB], LoanCalc, [ ], [ ], [ ], 
|[ Digita Home Accounts2], Accountant, Small Business Accounts, Account Master, [ Amigabok], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Project Management Research 
|&lt;!--AROS--&gt; 
|&lt;!--Amiga OS--&gt;SuperGantt, SuperPlan, 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;System Wide Search 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=utility/filetool Finder], [], [], 
|&lt;!--Amiga OS--&gt; 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;System Wide Dictionary - multilingual [http://sourceforge.net/projects/babiloo/ Babiloo], [http://code.google.com/p/stardict-3/ StarDict], 
|&lt;!--AROS--&gt;[ ],  
|&lt;!--AmigaOS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;System wide Thesaurus - multi lingual
|&lt;!--AROS--&gt;[ ], 
|Kuma K-Roget*, 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Sticky Desktop Notes (post it type) 
|&lt;!--AROS--&gt;[http://aminet.net/package/util/wb/amimemos.i386-aros AmiMemos], [https://aminet.net/package/util/wb/amimemos.src-aros AmiMemos Src], [], 
|&lt;!--Amiga OS--&gt;[http://aminet.net/package/util/wb/StickIt-2.00 StickIt v2], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;DTP Desktop Publishing 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/edit RNOPublisher], 
|&lt;!--Amiga OS--&gt;[http://pagestream.org/ Pagestream]*, Professional Pro Page*, Saxon Publisher, Pagesetter, PenPal, 
|&lt;!--AmigaOS4--&gt;[http://pagestream.org/ Pagestream]* 
|&lt;!--MorphOS--&gt;[http://pagestream.org/ Pagestream]* 
|-
|&lt;!--Sub Menu--&gt;Scanning 
|&lt;!--AROS--&gt;[ SCANdal], [], 
|&lt;!--Amiga OS--&gt;FxScan*, ScanQuix* 
|&lt;!--AmigaOS4--&gt;SCANdal (Sane)
|&lt;!--MorphOS--&gt;SCANdal
|-
|&lt;!--Sub Menu--&gt;OCR
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/convert gOCR] 
|&lt;!--AmigaOS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;[http://morphos-files.net/categories/office/text Tesseract] 
|-
|&lt;!--Sub Menu--&gt;Text Editing
|&lt;!--AROS--&gt;Jano Editor (already installed as Editor), [http://archives.arosworld.org/index.php?function=browse&amp;cat=development/edit EdiSyn], [http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/text/edit Annotate], [https://archives.arosworld.org/index.php?function=browse&amp;cat=development/edit Vim], [http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/text/edit FrexxEd] [https://github.com/vidarh/FrexxEd src], [ NoWinEd], 
|&lt;!--Amiga OS--&gt;[https://aminet.net/package/text/edit/TurboText20 TurboText20 ttx], Annotate, MicroGoldED/CubicIDE*, CygnusED*, Protext*, NoWinED, 
|&lt;!--AmigaOS4--&gt;Notepad, Annotate, CygnusED*, NoWinED, 
|&lt;!--MorphOS--&gt;MorphOS ED, NoWinED, GoldED/CubicIDE*, CygnusED*, Annotate, 
|-
|&lt;!--Sub Menu--&gt;Office Fonts [http://sourceforge.net/projects/fontforge/files/fontforge-source/ Font Designer] 
|&lt;!--AROS--&gt;[ ], [ ], 
|&lt;!--Amiga OS--&gt;TypeSmith*, SaxonScript (GetFont Adobe Type 1), 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Drawing Vector
|&lt;!--AROS--&gt;[http://sourceforge.net/projects/amifig/ ZuneFIG previously AmiFIG], [https://github.com/serk118/designworks-aros designworks aros 64bit]
|&lt;!--Amiga OS--&gt;Drawstudio*, ProVector*, ArtExpression*, Professional Draw*, AmiFIG, MetaView, [https://gitlab.com/amigasourcecodepreservation/designworks Design Works Src], [], 
|&lt;!--AmigaOS4--&gt;MindSpace, [http://www.os4depot.net/index.php?function=browse&amp;cat=graphics/edit amifig], 
|&lt;!--MorphOS--&gt;SteamDraw, [http://aminet.net/package/gfx/edit/amifig amiFIG], 
|-
|&lt;!--Sub Menu--&gt;video conferencing (jitsi) 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;source code hosting
|&lt;!--AROS--&gt;Gitlab, 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Remote Desktop (server)
|&lt;!--AROS--&gt;[http://sourceforge.net/projects/zunetools/files/VNC_Server ArosVNCServer], 
|&lt;!--Amiga OS--&gt;[http://s.guillard.free.fr/AmiVNC/AmiVNC.htm AmiVNC], [http://dspach.free.fr/amiga/avnc/index.html AVNC]
|&lt;!--AmigaOS4--&gt;[http://s.guillard.free.fr/AmiVNC/AmiVNC.htm AmiVNC] 
|MorphVNC, vncserver
|-
|&lt;!--Sub Menu--&gt;Remote Desktop (client) login and connect to another machine 
|&lt;!--AROS--&gt;[https://sourceforge.net/projects/zunetools/files/VNC_Client/ ArosVNC], [http://archives.arosworld.org/index.php?function=browse&amp;cat=network/misc rdesktop], 
|&lt;!--Amiga OS--&gt;[http://twinvnc.free.fr/index.php?menu=01&amp;lang=eng TwinVNC], [http://dspach.free.fr/amiga/vva/index.html VVA], [http://www.hd-zone.com/ RDesktop]
|&lt;!--AmigaOS4--&gt;[http://twinvnc.free.fr/index.php?menu=01&amp;lang=eng TwinVNC], [http://www.hd-zone.com/ RDesktop]
|[http://twinvnc.free.fr/index.php?menu=01&amp;lang=eng TwinVNC], [http://www.hd-zone.com/ RDesktop]
|-
|&lt;!--Sub Menu--&gt;notifications 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;Ranchero 
|&lt;!--AmigaOS4--&gt;Ringhio 
|&lt;!--MorphOS--&gt;MagicBeacon 
|-
|&lt;!--Sub Menu--&gt;Biometric facial logins and fingerprint security features 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt; 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt; 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|}

&lt;nowiki&gt;*&lt;/nowiki&gt; Commercial product.

[[#top|...to the top]]

==Audio==
{|  class=&quot;wikitable sortable&quot; 
|- 
!width:30%;|Audio
!width:10%;|AROS(x86)
!width:10%;|Commodore-Amiga OS 3.1(68k)
!width:10%;|Hyperion OS4(PPC)
!width:10%;|MorphOS(PPC)
|-
|&lt;!--Sub Menu--&gt;Playing playback Audio like MP3, [https://github.com/chrg127/gmplayer NSF], [https://github.com/kode54/lazyusf miniusf .usflib] [https://gitlab.com/kode54/psflib with pfslib], [], [], etc 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=video/play Mplayer], [ HarmonyPlayer hp], [http://www.a500.org/downloads/audio/index.xhtml playcdda] CDs, [ WildMidi Player], [https://bszili.morphos.me/ UADE mod player], [], [ RNOTunes], [ mp3Player], [], 
|&lt;!--Amiga OS--&gt;AmiNetRadio, AmigaAmp, playOGG, 
|&lt;!--AmigaOS4--&gt;TuneNet, SimplePlay, AmigaAmp, TKPlayer
|AmiNetRadio, Mplayer, Kaya, AmigaAmp
|-
|&lt;!--Sub Menu--&gt;Editing Audio 
|&lt;!--AROS--&gt;[ Audio Evolution 4] 
|&lt;!--Amiga OS--&gt;[ Samplitude Opus Key], [https://sourceforge.net/projects/hd-rec/ HD-Rec Src], [http://www.sonicpulse.de/eng/news.html SoundFX], 
|&lt;!--AmigaOS4--&gt;[https://sourceforge.net/projects/hd-rec/ HD-Rec], AmiSoundED, [http://os4depot.net/?function=showfile&amp;file=audio/record/audioevolution4.lha Audio Evolution 4] 
|[http://www.hd-rec.de/HD-Rec/index.php?site=home HD-Rec], 
|-
|&lt;!--Sub Menu--&gt;Editing Tracker Music
|&lt;!--AROS--&gt;[https://github.com/hitchhikr/protrekkr Protrekkr], [ Schism Tracker], [http://archives.arosworld.org/index.php?function=browse&amp;cat=audio/tracker MilkyTracker], [http://www.hivelytracker.com/ HivelyTracker], [ Radium in AROS already],  [http://www.a500.org/downloads/development/index.xhtml libMikMod], 
|&lt;!--Amiga OS--&gt;MilkyTracker, HivelyTracker, DigiBooster, Octamed SoundStudio, 
|&lt;!--AmigaOS4--&gt;MilkyTracker, HivelyTracker, GoatTracker
|MilkyTracker, GoatTracker, DigiBooster, 
|-
|&lt;!--Sub Menu--&gt;Editing Music [], [https://github.com/kmatheussen/camd CAMD] and/or staves and notes manuscript 
|&lt;!--AROS--&gt;[http://bnp.hansfaust.de/ Bars and Pipes for AROS], [ Audio Evolution], [], 
|&lt;!--Amiga OS--&gt;[http://bnp.hansfaust.de/ Bars'n'Pipes], MusicX* David &quot;Talin&quot; Joiner &amp; Craig Weeks (for Notator-X), Deluxe Music Construction 2*, [https://github.com/timoinutilis/midi-sequencer-amigaos Horny c Src], HD-Rec, [https://aminet.net/package/mus/midi/dominatorV1_51 Dominator], 
|&lt;!--AmigaOS4--&gt;[https://sourceforge.net/p/hd-rec/code/HEAD/tree/ HD-Rec Src], Rockbeat, [http://bnp.hansfaust.de/download.html Bars'n'Pipes], [http://os4depot.net/index.php?function=browse&amp;cat=audio/edit Horny], Audio Evolution 4, 
|&lt;!--MorphOS--&gt;Bars'n'Pipes, 
|-
|&lt;!--Sub Menu--&gt;Sound Sampling 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=audio/record Audio Evolution 4], [http://www.imica.net/SitePortalPage.aspx?siteid=1&amp;did=162 Quick Record], [https://archives.arosworld.org/index.php?function=browse&amp;cat=audio/misc SOX to get AIFF 16bit files], [https://github.com/aros-development-team/AROS/tree/master/workbench/tools/AHIRecord AHIRecord], 
|&lt;!--Amiga OS--&gt;[https://aminet.net/package/mus/edit/AudioEvolution3_src Audio Evolution 3 c src], [ Samplitude-MS Opus Key], Audiomaster IV*, 
|&lt;!--AmigaOS4--&gt;[https://github.com/timoinutilis/phonolith-amigaos phonolith c src], HD-Rec, Audio Evolution 4,
|&lt;!--MorphOS--&gt;[https://sourceforge.net/p/hd-rec/code/HEAD/tree/ HD-Rec Src], Audio Evolution 4,
|-
|&lt;!--Sub Menu--&gt;Live Looping or Audio Misc - Groovebox like
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;CD/DVD burn
|[https://code.google.com/p/amiga-fryingpan/ FryingPan], 
|&lt;!--Amiga OS--&gt;FryingPan, [http://www.estamos.de/makecd/#CurrentVersion MakeCD], 
|&lt;!--AmigaOS4--&gt;FryingPan, AmiDVD, 
|[http://www.amiga.org/forums/printthread.php?t=58736 FryingPan], Jalopeano, 
|-
|&lt;!--Sub Menu--&gt;CD/DVD audio rip
|Lame, [http://www.imica.net/SitePortalPage.aspx?siteid=1&amp;cfid=0&amp;did=167 Quick CDrip],
|&lt;!--Amiga OS--&gt;Lame,  
|&lt;!--AmigaOS4--&gt;Lame, 
|Lame,  
|-
|&lt;!--Sub Menu--&gt;MP3 v1 and v2 Tagger
|&lt;!--AROS--&gt;id3ren (v1), [http://archives.arosworld.org/index.php?function=browse&amp;cat=audio/edit mp3info], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|
|-
|&lt;!--Sub Menu--&gt;Audio Convert
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=audio/misc Sox], [], 
|&lt;!--Amiga OS--&gt;[http://aminet.net/package/mus/misc/SoundBox SoundBox], [http://aminet.net/package/mus/misc/SoundBoxKey SoundBox Key], [http://aminet.net/package/mus/edit/SampleE SampleE], sox 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;DJ mixing jamming 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Radio Automation Software [http://www.rivendellaudio.org/ Rivendell], [http://code.campware.org/projects/livesupport/report/3 Campware LiveSupport], [http://www.sourcefabric.org/en/airtime/ SourceFabric AirTime], [http://www.ohloh.net/p/mediabox404 MediaBox404], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Speakers Audio Sonos Mains AC networked wired controlled 
*2005 ZP100 with ZP80 
*2008 Zoneplayer ZP120 (multi-room wireless amp)  ZP90 receiver only with CR100 controller, 
*2009 ZonePlayer S5, 
*2010 BR100 wireless Bridge (no support),   
*2011 Play:3
*2013 Bridge (no support), Play:1,  
*2016 Arc,   Play:1,   
*Beam (Gen 2),   Playbar,  Ray,   Era 100,   Era 300,   Roam,   Move 2,   
*Sub (Gen 3),   Sub Mini,  Five,  Amp  S2 
|&lt;!--AROS--&gt;SonosController 
|&lt;!--Amiga OS--&gt;SonosController
|&lt;!--AmigaOS4--&gt;SonosController
|&lt;!--MorphOS--&gt;SonosController
|-
|&lt;!--Sub Menu--&gt;Smart Speakers 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt; 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|}

&lt;nowiki&gt;*&lt;/nowiki&gt; Commercial product.

[[#top|...to the top]]

==Video Creativity and Production==
{|  class=&quot;wikitable sortable&quot; 
|- 
!width:30%;|Video
!width:10%;|AROS(x86)
!width:10%;|Commodore-Amiga OS 3.1(68k)
!width:10%;|Hyperion OS4(PPC)
!width:10%;|MorphOS(PPC)
|-
|&lt;!--Sub Menu--&gt;Playing Video 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=video/play Mplayer VAMP], [http://www.a500.org/downloads/video/index.xhtml CDXL player], [http://www.a500.org/downloads/video/index.xhtml IffAnimPlay], [], 
|&lt;!--Amiga OS--&gt;Frogger*, AMP2, MPlayer, RiVA*, MooViD*, 
|&lt;!--AmigaOS4--&gt;DvPlayer, MPlayer 
|&lt;!--MorphOS--&gt;MPlayer, Frogger, AMP2, VLC 
|-
|&lt;!--Sub Menu--&gt;Streaming Video and game streaming like OBS studio, Parsec, [https://github.com/lizardbyte/sunshine sunshine], [https://github.com/moonlight-stream/moonlight-qt moonlight], etc 
|&lt;!--AROS--&gt;Mplayer, 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;Mplayer, Gnash, Tubexx 
|&lt;!--MorphOS--&gt;Mplayer, OWB, Tubexx
|-
|&lt;!--Sub Menu--&gt;Playing DVD 
|&lt;!--AROS--&gt;[http://a-mc.biz/ AMC]*, Mplayer 
|&lt;!--Amiga OS--&gt;AMP2, Frogger 
|&lt;!--AmigaOS4--&gt;[http://a-mc.biz/ AMC]*, DvPlayer*, AMP2,  
|&lt;!--MorphOS--&gt;Mplayer 
|-
|&lt;!--Sub Menu--&gt;Screen Recording
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=video/record Screenrecorder], [ ], [ ], [ ], [ ], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;Screenrecorder, 
|-
|&lt;!--Sub Menu--&gt;Create and Edit Individual Video NLE 
|&lt;!--AROS--&gt;[ Mencoder], [ Quick Videos], [http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/edit AVIbuild], [http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/misc FrameBuild], FFMPEG, 
|&lt;!--Amiga OS--&gt;[ MainConcept Mainactor Broadcast*], [http://en.wikipedia.org/wiki/Video_Toaster Video Toaster*], MacroSystem MovieShop 4.3*, proDAD Adorage*, [ IOSpirit VHI studio]*, [Gold Disk ShowMaker], [], 
|&lt;!--AmigaOS4--&gt;FFMpeg/GUI 
|&lt;!--MorphOS--&gt;Blender, Mencoder, FFmpeg
|-
|&lt;!--Sub Menu--&gt;Subtitle editor 
|&lt;!--AROS--&gt;[https://aminet.net/package/text/edit/Slarti_Arosx86ABIv0 Slarti_Arosx86ABIv0], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;IP-based video production workflows with High Dynamic Range (HDR), 10-bit color collaborative NDI, 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Blogging like Lemmy or kbin
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;VR face recognition for Vtubers 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;VR chatting Live2D models with Cubism type editor 
&lt;pre&gt;
Model data (cmo3)
Basic motions (can3)
Background image (png)
Set of files for embedding (runtime folder)
• Model data (moc3)
• Motion data (motion3.json)
• Model settings file (model3.json)
• Physics settings file (physics3.json)
• Display auxiliary file (cdi3.json)
&lt;/pre&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;VR chatting chatters .VRML models - standardized 3D file format for VR avatars 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;V-tubers V-tubing like Vseeface with Openseeface tracker or Vpuppr (virtual puppet project) for online live 2d / 3d art models rigging rigged LIV 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt; 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|}

&lt;nowiki&gt;*&lt;/nowiki&gt; Commercial product.

[[#top|...to the top]]


==Misc Application==
{|  class=&quot;wikitable sortable&quot; 
|- 
!width:30%;|Misc Application
!width:10%;|AROS(x86)
!width:10%;|Commodore-Amiga OS 3.1 (68k)
!width:10%;|Hyperion OS4(PPC)
!width:10%;|MorphOS(PPC)
|-
|&lt;!--Sub Menu--&gt;File Management 
|&lt;!--AROS--&gt;DOpus4, [https://github.com/BlitterStudio/dopus5 DOpus Magellan aka DOpus 5], [ Scalos], [ ], 
|&lt;!--Amiga OS--&gt;DOpus2, DOpus 4, [https://github.com/BlitterStudio/dopus5 Dopus5 Magellan], ClassAction, FileMaster, [http://www.amiga.org/forums/showthread.php?t=4897 DirWork 2]*, [https://github.com/RudolphRiedel/DiskMaster2 DiskMaster2 src], 
|&lt;!--AmigaOS4--&gt;DOpus4, [https://github.com/BlitterStudio/dopus5 Dopus5 Magellan], Filer, AmiDisk 
|&lt;!--MorphOS--&gt;DOpus4, [https://github.com/BlitterStudio/dopus5 Dopus5 Magellan], 
|-
|&lt;!--Sub Menu--&gt;File Verification / Repair 
|&lt;!--AROS--&gt;md5 (works in linux compiling shell), [http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/filetool workpar2] (PAR2),  [http://zakalwe.fi/~shd/foss/cksfv/files/ compile cksfv from website], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;Par2, 
|-
|Application Installer 
|&lt;!--AROS--&gt;[], [ InstallerNG], 
|&lt;!--Amiga OS--&gt;InstallerNG, Grunch, 
|&lt;!--AmigaOS4--&gt;Jack
|&lt;!--MorphOS--&gt;Jack 
|-
|&lt;!--Sub Menu--&gt;Compression archiver [https://github.com/FS-make-simple/paq9a paq9a], [], 
|&lt;!--AROS--&gt;XAD system is a toolkit designed for handling various file and disk archiver
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;[https://aminet.net/package/util/pack/decrunchmania_os4 Crunchmania CrM2 depacker], 
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Binary Hexadecimal Editor 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=development/edit Zaphod], [],
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Repository
|&lt;!--AROS--&gt;[ Git]
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;Git
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Filesystem Partition Editor formatter Disk Management
|&lt;!--AROS--&gt;[https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=1440&amp;highlight=partition&amp;pid=8821#post_8821 QuickPart], [ HDToolBox]
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Filesystem Repair and backups 
|&lt;!--AROS--&gt;ArSFSDoctor, 
|&lt;!--Amiga OS--&gt;[https://aminet.net/package/disk/bakup/quarterback_src Quarterback Tools C and asm src], [ ], [ ], [ ], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;System Disk check, integrity and history [https://github.com/smartmontools/smartmontools smart tools], [], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;[], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Multiple File renaming
|&lt;!--AROS--&gt;DOpus 4 or 5, 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Anti Virus
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;VChecker, 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Random Wallpaper Desktop changer [ DOpus5], [ Scalos],  
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Alarm Clock, Timer, Stopwatch, Countdown 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/workbench DClock], [http://aminet.net/util/time/AlarmClockAROS.lha AlarmClock], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Fortune Cookie Quotes Sayings 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/misc AFortune], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;C/C++ IDE 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/text/edit FrexxEd], [https://github.com/vidarh/FrexxEd FrexxEd src], Annotate, Murks, 
|&lt;!--Amiga OS--&gt;[http://devplex.awardspace.biz/cubic/index.html Cubic IDE]*, Annotate, 
|&lt;!--AmigaOS4--&gt;CodeBench , [https://gitlab.com/boemann/codecraft CodeCraft], 
|&lt;!--MorphOS--&gt;[http://devplex.awardspace.biz/cubic/index.html Cubic IDE]*, Anontate, 
|-
|&lt;!--Sub Menu--&gt;Computer Languages Translation [https://tetracorp.github.io/guide/reverse-engineering-amiga.html ], [https://amigasourcecodepreservation.gitlab.io/amiga-assembler-insider-guide/ ], [https://github.com/kermitfrog/Amiga-Re-Engineering Rust, Ghidra and FS-UAE], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;[https://bitbucket.org/rhinoid/convert68000toc/src/main/ convert m68k seka asm-one to c], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Gui Creators
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=development/guitool MuiBuilder], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;[ MuiBuilder],  
|-
|&lt;!--Sub Menu--&gt;Catalog .cd .ct Editors 
|&lt;!--AROS--&gt;FlexCat
|&lt;!--Amiga OS--&gt;[http://www.geit.de/deu_simplecat.html SimpleCat], FlexCat
|&lt;!--AmigaOS4--&gt;[http://aminet.net/package/dev/misc/simplecat SimpleCat], FlexCat
|[http://www.geit.de/deu_simplecat.html SimpleCat], FlexCat
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|}

&lt;nowiki&gt;*&lt;/nowiki&gt; Commercial product.


==Misc Application 2==
{|  class=&quot;wikitable sortable&quot; 
|- 
!width:30%;|Misc Application
!width:10%;|AROS(x86)
!width:10%;|Commodore-Amiga OS 3.1(68k)
!width:10%;|Hyperion OS4(PPC)
!width:10%;|MorphOS(PPC)
|-
|&lt;!--Sub Menu--&gt;System 
|&lt;!--AROS--&gt;[ SysExplorer], [ SysMon], [ Scout], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;OSK On Screen Keyboard
|&lt;!--AROS--&gt;[], 
|&lt;!--Amiga OS--&gt;[https://aminet.net/util/wb/OSK.lha OSK]
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Screen Magnifier Magnifying Glass Magnification 
|&lt;!--AROS--&gt;[http://www.onyxsoft.se/files/zoomit.lha ZoomIT], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Comic Book CBR CBZ format reader viewer 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/viewer comics], [http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/viewer comicon], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Ebook Reader 
|&lt;!--AROS--&gt;[https://blog.alb42.de/programs/#legadon Legadon EPUB],[]
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Ebook Converter 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Text to Speech tts [https://github.com/JonathanFly/bark-installer Bark], [], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=audio/misc flite], 
|&lt;!--Amiga OS--&gt;[http://www.text2speech.com translator], 
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=search&amp;tool=simple FLite]
|&lt;!--MorphOS--&gt;[http://se.aminet.net/pub/aminet/mus/misc/ FLite]
|-
|&lt;!--Sub Menu--&gt;Speech Voice Recognition Dictation - [http://sourceforge.net/projects/cmusphinx/files/ CMU Sphinx], [http://julius.sourceforge.jp/en_index.php?q=en/index.html Julius], [http://www.isip.piconepress.com/projects/speech/index.html ISIP], 
|&lt;!--AROS--&gt; 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Speech Voice Changer [], [], [], [], 
|&lt;!--AROS--&gt; 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Screen Display Blanker screensaver 
|&lt;!--AROS--&gt;Blanker Commodity (built in), [https://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/screenblanker GarshneBlanker], [http://sourceforge.net/projects/gblanker/ GBlanker Src], [], 
|&lt;!--Amiga OS--&gt;MultiCX, 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;ModernArt Blanker, 
|-
|}


==Misc Application 3==
{|  class=&quot;wikitable sortable&quot; 
|- 
!width:30%;|Misc Application
!width:10%;|AROS(x86)
!width:10%;|Commodore-Amiga OS 3.1(68k)
!width:10%;|Hyperion OS4(PPC)
!width:10%;|MorphOS(PPC)
|-
|&lt;!--Sub Menu--&gt;Fractals mandelbrot, etc 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/misc ], 
|&lt;!--Amiga OS--&gt;ZoneXplorer, 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Landscape Rendering 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/raytrace WCS World Construction Set], 
|&lt;!--Amiga OS--&gt;[ Vista Pro], [http://en.wikipedia.org/wiki/World_Construction_Set World Construction Set]
|&lt;!--AmigaOS4--&gt;[ WCS World Construction Set],
|&lt;!--MorphOS--&gt;[ WCS World Construction Set],
|-
|&lt;!--Sub Menu--&gt;Astronomy [https://sourceforge.net/projects/skychart/ skychart freepascal], [], [], 
|&lt;!--AROS--&gt;[ Digital Almanac (ABIv0 only)], 
|&lt;!--Amiga OS--&gt;[http://aminet.net/search?query=planetarium Aminet search], [http://aminet.net/misc/sci/DA3V56ISO.zip Digital Almanac], [https://aminet.net/package/misc/sci/da3sourceV58 Src c V58], [ Galileo renamed to Distant Suns]*, [], 
|&lt;!--AmigaOS4--&gt;[http://sourceforge.net/projects/digital-almanac/ Digital Almanac], Distant Suns*, [http://www.digitaluniverse.org.uk/ Digital Universe]*,
|&lt;!--MorphOS--&gt;[http://www.aminet.net/misc/sci/da3.lha Digital Almanac], [http://www.aminet.net/package/misc/sci/da3-mos-src Src c V56], 
|-
|&lt;!--Sub Menu--&gt;Astrology [https://sourceforge.net/projects/skylendar/ skylendar], [https://github.com/CruiserOne/Astrolog Astrolog], [https://www.astrolog.org/astrolog/astfile.htm Astrology alt site], [https://saravali.github.io/download.html Maitreya], [https://github.com/alamahant/Asteria Asteria], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;PCB design
|&lt;!--AROS--&gt; 
|&lt;!--Amiga OS--&gt;[ ], [ ], [ ], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Digital Signage
|&lt;!--AROS--&gt;Hollywood, Hollywood Designer 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Genealogy History Family Tree Ancestry Records (FreeBMD, FreeREG, and FreeCEN file formats or GEDCOM GenTree)
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt; [ Origins], [ Your Family Tree], [ ], [ ], [ ], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Languages 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;Fun School, 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Mathematics ([http://www-fourier.ujf-grenoble.fr/~parisse/install_en.html Xcas], etc.), 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/scientific mathX] 
|&lt;!--Amiga OS--&gt;Maple V, mathX, Fun School, GCSE Maths, [ ], [ ], [ ], 
|&lt;!--AmigaOS4--&gt;Yacas 
|&lt;!--MorphOS--&gt;Yacas 
|-
|&lt;!--Sub Menu--&gt;Maths Graph Function Plotting
|&lt;!--AROS--&gt;[https://blog.alb42.de/programs/#MUIPlot MUIPlot], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;App Utility Launcher Dock toolbar  
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/docky BoingBar], [], 
|&lt;!--Amiga OS--&gt;[https://github.com/adkennan/DockBot Dockbot],
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;3D Printer [https://github.com/OrcaSlicer/OrcaSlicer OrcaSlicer]
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;BASIC Computer Language 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=development/language Basic4SDL], [ Ace Basic], [ X-AMOS], [SDLBasic], [ Alvyn], 
|&lt;!--Amiga OS--&gt;[http://www.amiforce.de/main.php Amiblitz 3], [http://amos.condor.serverpro3.com/AmosProManual/contents/c1.html Amos Pro], [http://aminet.net/package/dev/basic/ace24dist ACE Basic], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;sdlBasic
|-
|&lt;!--Sub Menu--&gt;HAM radio, amateur radio, packet radio  [], [], [], [https://cemaxecuter.com/ Dragon OS], [https://github.com/km4ack/73Linux with 73 link update], [https://www.youtube.com/watch?v=YAL5KNePRSg video for], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;[https://www.amigarealm.com/amiga/amicomms/comm4.htm Comm4], [https://www.amigarealm.com/archives/comms/aarug/ TNC Terminal Node Controller with packets over serial connections on Yaesu or Woxum handheld], [https://aminet.net/comm/misc AmiCom], [ with 7Plus file encoder/decoder], [ mksstv], [ RTTYam], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|}

&lt;nowiki&gt;*&lt;/nowiki&gt; Commercial product.


==Games &amp; Emulation==

Some emulators/games require OpenGL to function and to adjust ahi prefs channels, frequency and unit0 and unit1 and 
[http://aros.sourceforge.net/documentation/users/shell/changetaskpri.php changetaskpri -1]

Rom patching  https://www.marcrobledo.com/RomPatcher.js/ https://www.romhacking.net/patch/ (ips, ups, bps, etc) and this other site supports the latter formats https://hack64.net/tools/patcher.php 

Free public domain roms for use with emulators can be found [http://www.pdroms.de/ here] as most of the rest are covered by copyright rules. If you like to read about old games see [http://retrogamingtimes.com/ here] and [http://www.armchairarcade.com/neo/ here] and a [http://www.vintagecomputing.com/ blog] about old computers. Possibly some of the [http://www.answers.com/topic/list-of-best-selling-computer-and-video-games best selling] of all time. [http://en.wikipedia.org/wiki/List_of_computer_system_emulators Wiki] with emulated systems list.

[https://archive.gamehistory.org/ Archive of VGHF], [https://library.gamehistory.org/ Video Game History Foundation Library search]


{|  class=&quot;wikitable sortable&quot; 
|- 
!width:10%;|Games [http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer Emulation]
!width:10%;|AROS(x86)
!width:10%;|AmigaOS3(68k)
!width:10%;|AmigaOS4(PPC)
!width:10%;|MorphOS(PPC)
|-
|&lt;!--Sub Menu--&gt;Games Emulation Amstrad CPC 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer], [ Caprice32 (OpenGL &amp; pure SDL)], [ Arnold], [https://retroshowcase.gr/cpcbox-master/], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;[http://os4depot.net/index.php?function=browse&amp;cat=emulation/computer]
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=2], 
|-
|&lt;!--Sub Menu--&gt;Games Emulation Apple2 and 2GS
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Arcade 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/gamesystem Mame], [ SI Emu (ABIv0 only)], 
|&lt;!--Amiga OS--&gt;Mame, 
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/gamesystem xmame], amiarcadia, 
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=2 Mame], 
|-
|&lt;!--Sub Menu--&gt;Games Emulation Atari 2600 [], [], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/gamesystem Stella], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Atari 5200 [https://github.com/wavemotion-dave/A5200DS A5200DS], [], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Atari 7800
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Atari 400 800 130XL [https://github.com/wavemotion-dave/A8DS A8DS], [], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer Atari800], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Atari Lynx
|&lt;!--AROS--&gt;[http://myfreefilehosting.com/f/6366e11bdf_1.93MB Handy (ABIv0 only)], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Atari Jaguar
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Bandai Wonderswan 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation BBC Micro and Acorn Electron [http://beehttps://bem-unix.bbcmicro.com/download.html BeebEm], [http://b-em.bbcmicro.com/ B-Em], [http://elkulator.acornelectron.co.uk/ Elkulator], [http://electrem.emuunlim.com/ ElectrEm], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Dragon 32 and Tandy CoCo [http://www.6809.org.uk/xroar/ xroar], [], 
|&lt;!--AROS--&gt;[], [], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Commodore C16 Plus4
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Commodore C64
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer Vice (ABIv0 only)], [], 
|&lt;!--Amiga OS--&gt;Frodo, 
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/gamesystem viceplus], 
|&lt;!--MorphOS--&gt;Vice, 
|-
|&lt;!--Sub Menu--&gt;Games Emulation Commodore Amiga
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer Janus UAE], Emumiga, 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;[http://os4depot.net/index.php?function=browse&amp;cat=emulation/computer UAE], 
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=2 UAE], 
|-
|&lt;!--Sub Menu--&gt;Games Emulation Japanese MSX MSX2 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Mattel Intelivision
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Mattel Colecovision and Adam
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Milton Bradley (MB) Vectrex [ Vectrex OpenGL], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation PICO8 Pico-8 fantasy video game console [https://github.com/egordorichev/pemsa-sdl/ pemsa-sdl], [https://github.com/jtothebell/fake-08 fake-08], [https://github.com/Epicpkmn11/fake-08/tree/wip fake-08 fork], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Nintendo Gameboy
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/gamesystem vba no sound], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/gamesystem vba]
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Nintendo NES
|&lt;!--AROS--&gt;[ EmiNES], [http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/gamesystem Fceu], [https://github.com/takahirox/nes-js?tab=readme-ov-file nes-js], [https://github.com/bfirsh/jsnes jsnes], [https://github.com/angelo-wf/NesJs NesJs], 
|&lt;!--Amiga OS--&gt;AmiNES, [http://www.dridus.com/~nyef/darcnes/ darcNES], 
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/gamesystem amines]
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Nintendo SNES
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/gamesystem Zsnes], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/gamesystem warpsnes]
|&lt;!--MorphOS--&gt;[http://fabportnawak.free.fr/snes/ Snes9x], 
|-
|&lt;!--Sub Menu--&gt;Games Emulation Nintendo N64 
*HLE and plugins [ mupen64], [https://github.com/ares-emulator/ares ares], [https://github.com/N64Recomp/N64Recomp N64Recomp], [https://github.com/rt64/rt64 rt64], [https://github.com/simple64/simple64 Simple64], 
*LLE [], 
|&lt;!--AROS--&gt;[http://code.google.com/p/mupen64plus/ Mupen64+],
|&lt;!--Amiga OS--&gt;[http://code.google.com/p/mupen64plus/ Mupen64+], [http://aminet.net/package/misc/emu/tr-981125_src TR64], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;[ Nintendo Gamecube Wii]
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;[ Nintendo Wii U]
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;[https://github.com/yuzu-emu Nintendo Switch]
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation NEC PC Engine 
|&lt;!--AROS--&gt;[], [], [https://github.com/yhzmr442/jspce js-pce], 
|[http://www.hugo.fr.fm/ Hugo], [http://mednafen.sourceforge.net/ Mednafen], 
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/gamesystem tgemu]
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Sega Master System (SMS)
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/gamesystem Dega], [http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/gamesystem sms], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/gamesystem osmose]
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Sega Genesis/Megadrive
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/gamesystem gp no sound], [http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/gamesystem DGen], 
|&lt;!--Amiga OS--&gt;[http://code.google.com/p/genplus-gx/ Genplus], 
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/gamesystem genesisplus]
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Sega Saturn 
*HLE [https://mednafen.github.io/ mednafen], [http://yabause.org/ yabause], [], 
*LLE [], [], 
|&lt;!--AROS--&gt;?
|&lt;!--Amiga OS--&gt;[http://yabause.org/ Yabause], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Sega Dreamcast 
*HLE [https://github.com/flyinghead/flycast  flycast], [https://code.google.com/archive/p/nulldc/downloads NullDC], 
*LLE [], [], 
|&lt;!--AROS--&gt;?
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Sinclair ZX80 and ZX81 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer], [], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Sinclair Spectrum 
|[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer Fuse (crackly sound)], [http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer SimCoupe], [ FBZX slow], [https://jsspeccy.zxdemo.org/ jsspeccy], [http://torinak.com/qaop/games qaop], 
|&lt;!--Amiga OS--&gt;[http://www.lasernet.plus.com/ Asp], [http://www.zophar.net/sinclair.html Speculator], [http://www.worldofspectrum.org/x128/index.html X128], 
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/computer]
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Sinclair QL
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer], [], 
|&lt;!--Amiga OS--&gt;[http://aminet.net/package/misc/emu/QDOS4amiga1 QDOS4amiga]
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation SNK NeoGeo Pocket
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/gamesystem], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/gamesystem gngeo], NeoPop, 
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Sony PlayStation
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/gamesystem FPSE], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/gamesystem FPSE]
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;[ Sony PS2]
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;[ Sony PS3]
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;[https://vita3k.org/ Sony Vita]
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;[https://github.com/shadps4-emu/shadPS4 PS4]
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation [http://en.wikipedia.org/wiki/Tangerine_Computer_Systems Tangerine] Oric and Atmos 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer Oricutron]
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/gamesystem Oricutron]
|&lt;!--MorphOS--&gt;[http://aminet.net/package/misc/emu/oricutron Oricutron]
|-
|&lt;!--Sub Menu--&gt;Games Emulation TI 99/4 99/4A [https://github.com/wavemotion-dave/DS994a DS994a], [], [https://js99er.net/#/ js99er], [], [http://aminet.net/package/misc/emu/TI4Amiga TI4Amiga], [http://aminet.net/package/misc/emu/TI4Amiga_src TI4Amiga src in c], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation HP 38G 40GS 48 49G/50G Graphing Calculators
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation TI 58 83 84 85 86 - 89 92 Graphing Calculators
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|}

{|  class=&quot;wikitable sortable&quot; 
|- 
!width:10%;|Games [https://www.rockpapershotgun.com/ General]
!width:10%;|AROS(x86)
!width:10%;|AmigaOS3(68k)
!width:10%;|AmigaOS4(PPC)
!width:10%;|MorphOS(PPC)
|- style=&quot;background:lightgrey; text-align:center; font-weight:bold;&quot;
| Games [https://www.trackawesomelist.com/michelpereira/awesome-open-source-games/ Open Source and others] || AROS || Amiga OS || Amiga OS4 || Morphos 
|-
|&lt;!--Sub Menu--&gt;Games Action like [https://github.com/opentomb/OpenTomb opentomb], [https://github.com/LostArtefacts/TRX TRX formerly Tomb1Main], [https://github.com/TombEngine TombEngine], [http://archives.arosworld.org/index.php?function=browse&amp;cat=game/action Thrust], [https://github.com/fragglet/sdl-sopwith sdl sopwith], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=game/action], [https://archives.arosworld.org/index.php?function=browse&amp;cat=game/action BOH], [], 
|&lt;!--Amiga OS--&gt;[https://github.com/BSzili/OpenLara/tree/amiga/src source of openlara SDL2], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Adventure like [http://dotg.sourceforge.net/ DMJ], [https://github.com/kromenak/gengine Gabriel Knight 3], [http://www.sarien.net/ Sierra Sarien], [https://github.com/klembot/twinejs twine js], [https://github.com/QSPFoundation/qspgui Quest Soft Player QSP], [], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=game/adventure dmagnetic], [https://archives.arosworld.org/?function=browse&amp;cat=emulation/misc ScummVM], [https://archives.arosworld.org/index.php?function=browse&amp;cat=game/roleplaying frotz infocom], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Board like [https://github.com/aperture-software/colditz-escape escape from colditz], [], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=game/board], [http://amigan.1emu.net/releases Africa]
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Cards 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=game/card ], [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=1443&amp;rowstart=180&amp;pid=12934#post_12934 Balatro], 
|&lt;!--AmigaOS--&gt;[http://home.arcor.de/amigasolitaire/e/welcome.html Reko], [https://github.com/samskivert/beschei-en beschei Src], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Misc [https://github.com/michelpereira/awesome-open-source-games Awesome open], [https://github.com/bobeff/open-source-games General Open Source], [https://github.com/SAT-R/sa2 Sonic Advance 2], [https://github.com/velorek1/cwordle Wordle type], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=game/misc], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games FPS like [https://aminet.net/package/game/shoot/D1X_Rebirth_AGA Descent D1X src], [https://github.com/DescentDevelopers/Descent3 Descent 3], [https://github.com/Fewnity/Counter-Strike-Nintendo-DS Counter-Strike-Nintendo-DS], [https://github.com/Aleph-One-Marathon/alephone Bungie Marathon 1994], [https://zdoom.org/downloads UzDoom opengl 3.3], [https://github.com/ZDoom/gzdoom gzdoom opengl 3+], [https://zdoom.org/downloads LZDoom opengl 2.1], 
|&lt;!--AROS--&gt;Doom, Quake, [http://archives.arosworld.org/index.php?function=browse&amp;cat=game/fps Quake 3 Arena (OpenGL)], [http://archives.arosworld.org/index.php?function=browse&amp;cat=game/fps Cube (OpenGL)], [http://archives.arosworld.org/index.php?function=browse&amp;cat=game/fps Assault Cube (OpenGL)], [http://archives.arosworld.org/index.php?function=browse&amp;cat=game/fps Cube 2 Sauerbraten (OpenGL)], [http://fodquake.net/test/ FodQuake QuakeWorld], [https://archives.arosworld.org/index.php?function=browse&amp;cat=game/fps Duke Nukem 3D], [https://archives.arosworld.org/index.php?function=browse&amp;cat=game/fps Darkplaces Nexuiz Xonotic], [http://archives.arosworld.org/index.php?function=browse&amp;cat=game/fps Doom 3 SDL (OpenGL)], [http://archives.arosworld.org/index.php?function=browse&amp;cat=game/fps Hexenworld and Hexen 2], [https://archives.arosworld.org/index.php?function=browse&amp;cat=game/fps Aliens vs Predator Gold 2000 avp (openGL)], [https://archives.arosworld.org/index.php?function=browse&amp;cat=game/fps Odamex (openGL doom)], [https://archives.arosworld.org/?function=showfile&amp;file=game/fps/ zgloom], [], [https://archives.arosworld.org/?function=showfile&amp;file=game/fps/ ab3dhd], [], 
|&lt;!--Amiga OS--&gt;Doom, Quake, AB3D, Fears, Breathless, Gloom, 
|&lt;!--AmigaOS4--&gt;Doom, Quake, 
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=12 Doom], Quake, Quake 3 Arena, [https://github.com/OpenXRay/xray-16 S.T.A.L.K.E.R Xray]
|-
|&lt;!--Sub Menu--&gt;Games MMORG like 
|&lt;!--AROS--&gt;[ Eternal Lands (OpenGL)],
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Platform like 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=game/platform], [ Maze of Galious], [ Gish]*(openGL), [ Mega Mario], [https://archives.arosworld.org/?function=showfile&amp;file=game/platform/ thextech SMBX], [http://www.gianas-return.de/ Giana's Return], [http://www.sqrxz.de/ Sqrxz], [www.sqrxz2.de/ Sqrxz 2], [http://www.sqrxz.de/sqrxz-3/ Sqrxz 3], [http://www.sqrxz.de/sqrxz-4/ Sqrxz 4], [http://archives.arosworld.org/index.php?function=browse&amp;cat=game/platform Cave Story], [https://bszili.morphos.me/ Frogatto], [https://bszili.morphos.me/ OpenJazz], [https://archives.arosworld.org/?function=showfile&amp;file=game/platform/ pekkakana2], [ Aquaria], [https://archives.arosworld.org/?function=showfile&amp;file=game/platform/ sonic CD], [], 
|&lt;!--Amiga OS--&gt;[ Giana Sisters], [], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Puzzle [https://github.com/mariopartyrd/marioparty4/tree/port Party], [https://github.com/mdodis/OpenSolomonsKey OpenSolomonsKey], [], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=game/puzzle], [ Cubosphere (OpenGL)], [http://archives.arosworld.org/index.php?function=browse&amp;cat=game/puzzle Candy Crisis], [http://bszili.morphos.me/ TailTale], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Racing [ Trigger Rally], [ VDrift], [http://www.ultimatestunts.nl/index.php?page=2&amp;lang=en Ultimate Stunts], [http://maniadrive.raydium.org/ Mania Drive], [https://github.com/plowteam/donut Simpsons Hit and Run], [], 
|&lt;!--AROS--&gt;[ Super Tux Kart (OpenGL)], [http://www.dusabledanslherbe.eu/AROSPage/F1Spirit.30.html F1 Spirit (OpenGL)], [http://bszili.morphos.me/index.html MultiRacer], [https://bszili.morphos.me/ Speed Dreams], [], 
|&lt;!--AmigaOS--&gt;
|&lt;!--AmigaOS4--&gt;[http://bszili.morphos.me/index.html Speed Dreams], 
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=12], [http://bszili.morphos.me/index.html TORCS], 
|-
|&lt;!--Sub Menu--&gt;Games 1st first person DRPG [https://wiki.rpg.net/index.php/Open_Game_Systems Misc], [https://github.com/OpenEnroth/OpenEnroth OpenEnroth MM], []
|&lt;!--AROS--&gt;[https://github.com/BSzili/aros-stuff Arx Libertatis], [http://www.playfuljs.com/a-first-person-engine-in-265-lines/ js raycaster], [https://github.com/Dorthu/es6-crpg webgl], [https://github.com/sonountaleban/AmiShockolate System Shock], [], [], 
|&lt;!--AmigaOS--&gt;Phantasie, Faery Tale, Dungeon Master, 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games 3rd third person action CRPG  [https://sourceforge.net/projects/sumwars/ Summoning Wars], [https://www.solarus-games.org/ Solarus], [https://wiki.rpg.net/index.php/Open_Game_Systems Misc], [https://github.com/alexbatalov/fallout1-ce fallout ce], [https://github.com/rwengine/openrw gta3], [https://github.com/gta-reversed/gta-reversed gta3 sa], [https://github.com/mrxenginner/reVC gta3 vc revc], 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/?function=showfile&amp;file=game/strategy/ fheroes2 homm2], [https://archives.arosworld.org/?function=showfile&amp;file=game/roleplaying/ breakhack], [https://archives.arosworld.org/?function=showfile&amp;file=game/roleplaying/ devilutionx diablo 1 hellfire], [https://archives.arosworld.org/?function=showfile&amp;file=game/roleplaying/ fallout 1], [https://archives.arosworld.org/?function=showfile&amp;file=game/strategy/ stratagus], [https://archives.arosworld.org/?function=showfile&amp;file=game/strategy/ hostile-takeover], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games isometric RPG [https://sourceforge.net/projects/sumwars/ Summoning Wars], [https://www.solarus-games.org/ Solarus], [https://wiki.rpg.net/index.php/Open_Game_Systems Misc], [https://github.com/topics/dungeon?l=javascript Dungeon], [], [https://github.com/clintbellanger/heroine-dusk JS Dusk], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=game/roleplaying nethack], [https://archives.arosworld.org/index.php?function=browse&amp;cat=game/roleplaying GemRB], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games card based RPG [https://github.com/open-duelyst/duelyst Duelyst], [], [], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games turn based tactics RPG [], [], [], [], [], [], 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=game/strategy UFO AI], [http://play.freeciv.org/ FreeCiv], [], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Strategy [http://rtsgus.org/ RTSgus], [http://stargus.sourceforge.net/ Stargus], [https://github.com/KD-lab-Open-Source/Perimeter Perimeter], [https://matty77.itch.io/conflict-3049 conflict-3049], [], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=game/strategy MegaGlest (OpenGL)], [https://archives.arosworld.org/?function=showfile&amp;file=game/strategy/ signus], [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=1443&amp;rowstart=140&amp;pid=12446#post_12446 Wargus warcraft 2 setup], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=12]
|-
|&lt;!--Sub Menu--&gt;Games Rhythm, Beat, Step [], [], [https://clonehero.net/ clonehero], [https://github.com/MatteoGodzilla/Dj-Engine Dj-Engine], 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=game/misc Frets on Fire], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Shoot Em Ups [http://www.mhgames.org/oldies/formido/ Formido], [http://code.google.com/p/violetland/ Violetland], 
||&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=game/action Open Tyrian], [http://www.parallelrealities.co.uk/projects/starfighter.php Starfighter], [ Alien Blaster], [https://github.com/OpenFodder/openfodder OpenFodder], [https://archives.arosworld.org/?function=showfile&amp;file=game/action/ tbftss The Battle for the Solar System: the Pandora War]
|&lt;!--AmigaOS--&gt;
|&lt;!--AmigaOS4--&gt;[http://www.parallelrealities.co.uk/projects/starfighter.php Starfighter], [ The Battle for the Solar System: the Pandora War]
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Simulations [http://scp.indiegames.us/ Freespace 2], [http://www.heptargon.de/gl-117/gl-117.html GL117], [http://code.google.com/p/corsix-th/ Theme Hospital], [http://code.google.com/p/freerct/ Rollercoaster Tycoon], [http://hedgewars.org/ Hedgewars], [https://github.com/raceintospace/raceintospace raceintospace], [https://github.com/Return-To-The-Roots RTTR Settlers 2], [https://github.com/OoliteProject/oolite oolite elite], [https://github.com/fesh0r/newkind newkind elite], [], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;SimCity, SimAnt, Sim Hospital, Theme Park, 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=12]
|-
|&lt;!--Sub Menu--&gt;Games Life Sim [https://github.com/ACreTeam/forest Animal Crossing], [ ], [], [], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Horror [https://github.com/Mikompilation/MikuPan Fatal Frame], [ ], [], [], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Sandbox Voxel Open World Exploration [https://github.com/ClassiCube/ Classicube],[http://www.michaelfogleman.com/craft/ Craft], [https://github.com/tothpaul/DelphiCraft DelphiCraft],[https://www.minetest.net/ Luanti formerly Minetest], [ infiniminer], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Battle Royale [https://bruh.io/ Play.Bruh.io], [https://www.coolmathgames.com/0-copter Copter Royale], [https://surviv.io/ Surviv.io], [https://nuggetroyale.io/#Ketchup Nugget Royale], [https://miniroyale2.io/ Miniroyale2.io], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Tower Defense [https://chriscourses.github.io/tower-defense/ HTML5], [https://github.com/SBardak/Tower-Defense-Game TD C++], [https://github.com/bdoms/love_defense LUA and LOVE], [https://github.com/HyOsori/Osori-WebGame HTML5], [https://github.com/PascalCorpsman/ConfigTD ConfigTD Pascal], [https://github.com/GloriousEggroll/wine-ge-custom Wine], []
|&lt;!--AROS--&gt;[https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=1443&amp;rowstart=180&amp;pid=12871#post_12871 Plants vs Zombies PvZ], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Visual Novel Engines [https://github.com/diane1f0cd/VisualNovelTemplate Visual Novel Template], [https://github.com/Kirilllive/tuesday-js Tuesday JS], [https://github.com/tejasnayak25/vnsutra vnsutra], [https://github.com/weetabix-su/renpsp-dev RenPSP], [https://github.com/Galladite27/ONScripter-EN ONScripter-EN], [https://github.com/NathanGuilhot/VNES-Raylib https://github.com/NathanGuilhot/VNES VNES in Raylib], [https://www.renpy.org/latest.html renpy ren'py python based], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Virtual Reality VR [https://gitlab.com/madsbuvi/openmw openmw vr], [https://github.com/Team-Beef-Studios/BeefRaiderXR BeefRaiderXR], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Virtual Table Top VTT [ Roll20], [https://www.owlbear.rodeo/ owlbear rodeo], [], [], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Computer assisted TableTop TTRPG OSR [https://www.rpgsolo.com/play.php RPGSolo], [https://github.com/fpsvogel/solo-ttrpgs Solo TTRPG], [], [], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games 2D 3D Engines [https://github.com/fegennari/3DWorld 3DWorld], [https://github.com/GarageGames/Torque3D Torque3D], [https://github.com/gameplay3d/GamePlay GamePlay 3D],  [https://www.babylonjs.com/ BabylonJS ], [ Godot], [ Ogre], [ Crystal Space], [https://github.com/JacobHess03/ Dragon-Quest like], [https://github.com/bjornbytes/lovr Lua LOVE for 2D LOVR for 3D], [], 
|&lt;!--AROS--&gt;[https://www.arkhamdev.net/wiki.htm?id=agx Arkham Development antiryadgx 8.9 lts with register], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games C based game frameworks [https://github.com/orangeduck/Corange Corange], [https://github.com/scottcgi/Mojoc Mojoc], [https://orx-project.org/ Orx], [https://github.com/ioquake/ioq3 Quake 3], [https://www.mapeditor.org/ Tiled], [https://www.raylib.com/ 2d Raylib], [https://github.com/Rabios/awesome-raylib other raylib], [https://github.com/MrFrenik/gunslinger Gunslinger], [https://o3de.org/ o3d], [http://archives.aros-exec.org/index.php?function=browse&amp;cat=development/library GLFW], [], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=development/library Raylib 5], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games RPGMaker MV/MZ-compatible projects [https://github.com/Psychronic-Games/RPGReactor RPGReactor js],
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Virtual Pinball [https://github.com/vpinball/vpinball vpinball], [], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games unpack unarc [], [], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|}


==Application Guides==

[[#top|...to the top]]

===Web Browser===

OWB is now at version 2.0 (which got an engine refresh, from July 2015 to February 2019) and 3.0.

This latest version has a good support for many/most web sites, even YouTube web page now works. 

This improved compatibility comes at the expense of higher RAM usage (now 1GB RAM is the absolute minimum). 

Also, keep in mind that the lack of a JIT (Just-In-Time) JS compiler on the 32 bit version, makes the web surfing a bit slow. 

Only the 64 bit version of OWB 2.0 will have JIT enabled, thus benefitting of more speed. There are tooltypes that can be added to the icon to provide further features JIT, MSE etc 


Certificates from [https://curl.se/docs/caextract.html ca certs], 


DNS tracking blocking with [https://easylist.to/easylist/easylist.txt easylist.txt] in PROGDIR:Conf before starting browser with enabled AdBlock [https://github.com/easylist/easylist/tree/master easylist], [https://gitlab.com/eyeo anti abp], [https://firebog.net/ big blocklist], [https://github.com/StevenBlack/hosts Steves], [], [], 

This can be enabled with OWB Odyssey with Windows -&gt; Content Blocking and Windows -&gt; Messages and enter 

 https://www.youtube.com/api/stats/ads*
 https://www.youtube.com/pagead/adview*
 https://www.youtube.com#@##player-ads*

into your custom filters 


Element blocker browser extension might be needed for [https://github.com/easylist/easylist/wiki/Youtube-Issues youtube], [ mid roll], [ pre roll], [ ],  


OWB speed is much better when running from RAM Disk, the best way is to add the below into your S:User-Startup which copies OWB drawer from Extras:Internet/OWB to RAM Disk: 

So add this :
&lt;pre&gt;
copy Extras:Internet/OWB Ram:OWB/ ALL CLONE &gt;NIL:
copy Extras:Internet/OWB.info Ram: &gt;NIL:
&lt;/pre&gt;
Open RAM Disk and open OWB drawer and double click on OWB icon so that the above icon tooltypes are activated 

Problems are that the copy time is long (around 20 seconds added in the background), but we can make it faster if we delete useless files from the OWB drawer (docs, …)
If you don’t copy the drawer back onto the HD, you won’t save your cache, cookies, passwords… So you need a script for it.


Error messages 

SSL error &quot;cant verify with ca-certificates&quot;, check bios clock time date is correct 

Error 6, try checking networking prefs settings and Save / Use preferences again or a '''few times''' otherwise the network chipset may not be compatible with Aros 


[https://www.google.com/search?q=%s&amp;udm=14 Google search without AI overview] 


===E-mail===

 YAM does not support SSL and most mail providers now switched to encrypted SMTP/POP3 connections


====SimpleMail====

SimpleMail supports IMAP and appears to work with GMail, but it's never been reliable enough, it can crash with large mailboxes.

Please read more on this [http://www.freelists.org/list/simplemail-usr User list]


 GMail

Be sure to activate the pop3 usage in your gmail account setup / configuration first.

pop3: 
pop.gmail.com
Use SSL: Yes
Port: 995

smtp:
smtp.gmail.com (with authentication)
Use Authentication: Yes
Use SSL: Yes
Port: 465 or 587


 Hotmail/MSN/outlook/Microsoft Mail mid-2017, all outlook.com accounts will be migrated to Office 365 / Exchange

Most users are currently on POP which does not allow showing folders and many other features (technical limitations of POP3). With Microsoft IMAP you will get folders, sync read/unread, and show flags. You still won't get push though, as Microsoft has not turned on the IMAP Idle command as at Sept 2013.

If you want to try it, you need to first remove (you can't edit) your pop account (long-press the account on the accounts screen, delete account). Then set it up this way:

1. Email/Password
2. Manual
3. IMAP
4.

* Incoming: imap-mail.outlook.com, port 993, SSL/TLS should be checked
* Outgoing: smtp-mail.outlook.com, port 587, SSL/TLS should be checked
* POP server name pop-mail.outlook.com, port 995, POP encryption method SSL

 Yahoo  Mail

On April 24, 2002 Yahoo ceased to offer POP access to its free mail service. Introducing instead a yearly payment feature, allowing users POP3 and IMAP server support, along with such benefits as larger file attachment sizes and no adverts.

Sorry to see Yahoo leaving its users to cough up for the privilege of accessing their mail. Understandable, when competing against rivals such as Gmail and Hotmail who hold a large majority of users and were hacked in 2014 as well.


Incoming Mail (IMAP) Server

* Server - imap.mail.yahoo.com
* Port - 993
* Requires SSL - Yes

Outgoing Mail (SMTP) Server

* Server - smtp.mail.yahoo.com
* Port - 465 or 587
* Requires SSL - Yes
* Requires authentication - Yes

Your login info

* Email address - Your full email address (name@domain.com)
* Password - Your account's password
* Requires authentication - Yes


Note that you need to enable “Web &amp; POP Access” in your Yahoo Mail account to send and receive Yahoo Mail messages through any other email program.

You will have to enable “Allow your Yahoo Mail to be POPed” under “POP and Forwarding”, to send and receive Yahoo mails through any other email client.

Cannot be done since 2002 unless the customer pays Yahoo a subscription subs fee to have access to SMTP and POP3

* Set the POP server for incoming mails as pop.mail.yahoo.com. You will have to enable “SSL” and use 995 for Port.
* “Account Name or Login Name” – Your Yahoo Mail ID i.e. your email address without the domain “@yahoo.com”.
* “Email Address” – Your Yahoo Mail address i.e. your email address including the domain “@yahoo.com”. E.g. myname@yahoo.com
* “Password” – Your Yahoo Mail password.

Yahoo! Mail Plus users may have to set POP server as plus.pop.mail.yahoo.com and SMTP server as plus.smtp.mail.yahoo.com.

* Set the SMTP server for outgoing mails as smtp.mail.yahoo.com. You will also have to make sure that “SSL” is enabled and use 465 for port. you must also enable “authentication” for this to work.


====YAM Yet Another Mailer====

 YAM does not support SSL and most mail providers have now switched to encrypted SMTP/POP3 connections

This email client is POP3 only if the SSL library is available [http://www.freelists.org/list/yam YAM Freelists]

One of the downsides of using a POP3 mailer unfortunately - you have to set an option not to delete the mail if you want it left on the server. IMAP keeps all the emails on the server.

Possible issues

Sending mail issues is probably a matter of using your ISP's SMTP server, though it could also be an SSL issue.


getting a &quot;Couldn't initialise TLSv1 / SSL error

Use of on-line e-mail accounts with this email client is not possible as it lacks the OpenSSL AmiSSl v3 compatible library

 GMail 
Incoming Mail (POP3) Server - requires SSL: pop.gmail.com
Use SSL: Yes
Port: 995

Outgoing Mail (SMTP) Server - requires TLS: smtp.gmail.com (use authentication)
Use Authentication: Yes
Use STARTTLS: Yes (some clients call this SSL)
Port: 465 or 587

Account Name: your Gmail username (including '@gmail.com')
Email Address: your full Gmail email address (username@gmail.com)
Password: your Gmail password

Anyway, the SMTP is pop.gmail.com port 465 and it uses SSLLv3 Authentication. The POP3 settings are for the same server (pop.gmail.com), only on port 995 instead.


 Outlook.com access

&lt;pre &gt;
Outlook.com SMTP server address: smtp.live.com
Outlook.com SMTP user name: Your full Outlook.com email address (not an alias)
Outlook.com SMTP password: Your Outlook.com password
Outlook.com SMTP port: 587
Outlook.com SMTP TLS/SSL encryption required: yes 
&lt;/pre &gt;


 Yahoo  Mail

&lt;pre &gt;
“POP3 Server” – Set the POP server for incoming mails as pop.mail.yahoo.com. You will have to enable “SSL” and use 995 for Port.
“SMTP Server” – Set the SMTP server for outgoing mails as smtp.mail.yahoo.com. You will also have to make sure that “SSL” is enabled and use 465 for port. you must also enable “authentication” for this to work.
“Account Name or Login Name” – Your Yahoo Mail ID i.e. your email address without the domain “@yahoo.com”.
“Email Address” – Your Yahoo Mail address i.e. your email address including the domain “@yahoo.com”. E.g. myname@yahoo.com
“Password” – Your Yahoo Mail password.
&lt;/pre &gt;

Yahoo! Mail Plus users may have to set POP server as plus.pop.mail.yahoo.com and SMTP server as plus.smtp.mail.yahoo.com.

Note that you need to enable “Web &amp; POP Access” in your Yahoo Mail account to send and receive Yahoo Mail messages through any other email program.

You will have to enable “Allow your Yahoo Mail to be POPed” under “POP and Forwarding”, to send and receive Yahoo mails through any other email client.

Cannot be done since 2002 unless the customer pays Yahoo a monthly fee to have access to SMTP and POP3


 Microsoft Outlook Express Mail 

1. Get the files to your PC.
By whatever method get the files off your Amiga onto your PC. In the YAM folder you have a number of different folders, one for each of your folders in YAM. Inside that is a file usually some numbers such as 332423.283. YAM created a new file for every single email you received.

2. Open up a brand new Outlook Express. Just configure the account to use 127.0.0.1 as mail servers. It doesn't really matter. You will need to manually create any subfolders you used in YAM.

3. You will need to do a mass rename on all your email files from YAM. Just add a .eml to the end of it. Amazing how PCs still rely mostly on the file name so it knows what sort of file it is rather than just looking at it! There are a number of multiple renamers online to download and free too.

4. Go into each of your folders, inbox, sent items etc. And do a select all then drag the files into Outlook Express (to the relevant folder obviously) Amazingly the file format that YAM used is very compatible with .eml standard and viola your emails appear. With correct dates and working attachments.

5. If you want your email into Microsoft Outlook. Open that up and create a new profile and a new blank PST file. Then go into File Import and choose to import from Outlook Express. And the mail will go into there. And viola.. you have your old email from your Amiga in a more modern day format.


===FTP===

Magellan has a great FTP module. It allows transferring files from/to a FTP server over the Internet or the local network and, even if FTP is perceived as a &quot;thing of the past&quot;, its usability is all inside the client. The FTP thing has a nice side effect too, since every Icaros machine can be a FTP server as well, and our files can be easily transferred from an Icaros machine to another with a little configuration effort.

First of all, we need to know the 'server' IP address. Server is the Icaros machine with the file we are about to download on another Icaros machine, that we're going to call 'client'. To do that, move on the server machine and 1) run Prefs/Services to be sure &quot;FTP file transfer&quot; is enabled (if not, enable it and restart Icaros); 2) run a shell and enter this command:

ifconfig -a

Make a note of the IP address for the network interface used by the local area network. For cabled devices, it usually is net0:. Now go on the client machine and run Magellan:

Perform these actions: 1) click on FTP; 2) click on ADDRESS BOOK; 3) click on &quot;New&quot;. 
You can now add a new entry for your Icaros server machine:

1) Choose a name for your server, in order to spot it immediately in the address book. Enter the IP address you got before.

2) click on Custom Options:


1) go to Miscellaneous in the left menu;

2) Ensure &quot;Passive Transfers&quot; is NOT selected;

3) click on Use. We need to deactivate Passive Transfers because YAFS, the FTP server included in Icaros, only allows active transfers at the current stage. Now, we can finally connect to our new file source:


1) Look into the address book for the newly introduced server, be sure that name and IP address are right, and

2) click on Connect. A new lister with server's &quot;MyWorkspace&quot; contents will appear. You can now transfer files over the network choosing a destination among your local (client's) volumes.

Can be adapted to any FTP client on any platform of your choice, just be sure your client allows Active Transfers as well.


===IRC Internet Relay Chat===

Jabberwocky is ideal for one-to-one social media communication, use IRC if you require one to many. 

Just type a message in ''lowercase''' letters and it will be posted to all in the [ AROS irc channel]. Please do not use UPPER CASE as it is a sign of SHOUTING which is annoying.

Other things to type in - replace &lt;message&gt; with a line of text and &lt;nick&gt; with a person's name

&lt;pre&gt;
/help

/list

/who
/whois &lt;nick&gt;

/msg &lt;nick&gt; &lt;message&gt;

/query &lt;nick&gt; 
&lt;message&gt;s
/query

/away &lt;message&gt;
/away

/quit &lt;going away message&gt; 
&lt;/pre&gt;


[http://irchelp.org/irchelp/new2irc.html#smiley Intro guide here]. IRC Primer can be found here in [http://www.irchelp.org/irchelp/ircprimer.html html], [http://www.irchelp.org/irchelp/text/ircprimer.txt TXT], [http://www.kei.com/irc/IRCprimer1.1.ps PostScript].


Issue the command /me &lt;text&gt; where &lt;text&gt; is the text that should follow your nickname.
Example: /me slaps ajk around a bit with a large trout

/nick &lt;newNick&gt;

/nickserv register &lt;password&gt; &lt;email address&gt;

/ns instead of /nickserv, while others might need /msg nickserv

/nickserv identify &lt;password&gt;

Alternatives:
/ns identify &lt;password&gt;
/msg nickserv identify &lt;password&gt;


==== IRC WookieChat ====

WookieChat is the most complete internet client for communication across the IRC Network. WookieChat allows you to swap ideas and communicate in real-time, you can also exchange Files, Documents, Images and everything else using the application's DCC capabilities.


add smilies drawer/directory

 run wookiechat from the shell and set stack to 1000000 e.g. wookiechat stack 1000000

select a server / server window

* nickname 
* user name 
* real name - optional

Once you configure the client with your preferred screen name, you'll want to find a channel to talk in.


servers

* New Server - click on this to add / add extra - change details in section below this click box 
* New Group
* Delete Entry
* Connect to server
* connect in new tab
* perform on connect

Change details

* Servername - change text in this box to one of the below Server: 
* Port number - no need to change
* Server password
* Channel - add #channel from below 
* auto join - can click this 
* nick registration password,

Click Connect to server button above


&lt;pre&gt;
Server: irc.freenode.net
Channel: #aros
&lt;/pre&gt;

irc://irc.freenode.net/aros

&lt;pre&gt;
Server: chat.amigaworld.net 
Channel: #amigaworld or #amigans 
&lt;/pre&gt;

&lt;pre&gt;
On Sunday evenings USA time usually starting around 3PM EDT (1900 UTC)
Server:irc.superhosts.net
Channel #team*amiga  
&lt;/pre&gt;

&lt;pre&gt;
BitlBee and Minbif are IRCd-like gateways to multiple IM networks
Server: im.bitlbee.org 
Port 6667 
Seems to be most useful on WookieChat as you can be connected to several servers at once. One for Bitlbee and any messages that might come through that. One for your normal IRC chat server. 
&lt;/pre&gt;

[http://www.bitlbee.org/main.php/servers.html Other servers],

&lt;pre&gt;
#Amiga.org - irc.synirc.net eu.synirc.net dissonance.nl.eu.synirc.net (IPv6: 2002:5511:1356:0:216:17ff:fe84:68a) 
twilight.de.eu.synirc.net zero.dk.eu.synirc.net us.synirc.net avarice.az.us.synirc.net envy.il.us.synirc.net harpy.mi.us.synirc.net 
liberty.nj.us.synirc.net snowball.mo.us.synirc.net - Ports 6660-6669 7001 (SSL)
&lt;/pre&gt;

&lt;pre&gt;
Multiple server support
&quot;Perform on connect&quot; scripts and channel auto-joins
Automatic Nickserv login
Tabs for channels and private conversations
CTCP PING, TIME, VERSION, SOUND
Incoming and Outgoing DCC SEND file transfers
Colours for different events
Logging and automatic reloading of logs
mIRC colour code filters
Configurable timestamps
GUI for changing channel modes easily
Configurable highlight keywords
URL Grabber window
Optional outgoing swear word filter
Event sounds for tabs opening, highlighted words, and private messages
DCC CHAT support
Doubleclickable URL's
Support for multiple languages using LOCALE
Clone detection
Auto reconnection to Servers upon disconnection
Command aliases
Chat display can be toggled between AmIRC and mIRC style
Counter for Unread messages
Graphical nicklist and graphical smileys with a popup chooser
&lt;/pre&gt;


====IRC Aircos ====

Double click on Aircos icon in Extras:Networking/Apps/Aircos. It has been set up with a guest account for trial purposes. Though ideally, choose a nickname and password for frequent use of irc. 


====IRC and XMPP Jabberwocky====
 Servers are setup and close down at random 
You sign up to a server that someone else has setup and access chat services through them. 

The two ways to access chat from jabberwocky
&lt;pre &gt;
Jabberwocky -&gt; Server -&gt; XMPP -&gt; open and ad-free 
Jabberwocky -&gt; Server -&gt; Transports (Gateways) -&gt; Proprietary closed systems 
&lt;/pre &gt;

The Jabber.org service connects with all IM services that use XMPP, the open standard for instant messaging and presence over the Internet. The services we connect with include Google Talk (closed), Live Journal Talk, Nimbuzz, Ovi, and thousands more. However, you can not connect from Jabber.org to proprietary services like AIM, ICQ, MSN, Skype, or Yahoo because they don’t yet use XMPP components (XEP-0114) '''but''' you can use Jabber.com's servers and IM gateways (MSN, ICQ, Yahoo etc.) instead.

The best way to use jabberwocky is in conjunction with a public jabber server with '''transports''' to your favorite services, like gtalk, Facebook, yahoo, ICQ, AIM, etc.


You have to register with one of the servers, [https://list.jabber.at/ this list] or [http://www.jabberes.org/servers/ another list], [http://xmpp.net/ this security XMPP list],

Unfortunately jabberwocky can only connect to one server at a time so it is best to check what services each server offers. If you set it up with separate Facebook and google talk accounts, for example, sometimes you'll only get one or the other.

Jabberwocky open a window where the Jabber server part is typed in as well as your Nickname and Password.

Jabber ID (JID) identifies you to the server and other users.

Once registered the next step is to goto Jabberwocky's &quot;Windows&quot; menu and select the &quot;Agents&quot; option. The &quot;Agents List&quot; window will open.

Roster (contacts list)

[http://search.wensley.org.uk/ Chatrooms] (MUC) are available

File Transfer - can send and receive files through the Jabber service but not with other services like IRC, ICQ, AIM or Yahoo. All you need is an installed webbrowser and OpenURL.

Clickable URLs - The message window uses Mailtext.mcc and you can set a URL action in the MUI mailtext prefs like SYS:Utils/OpenURL %s NEWWIN.

There is no consistent Skype like (H.323 VoIP) video conferencing available over Jabber. The move from xmpp to Jingle should help but no support on any amiga-like systems at the moment. [http://aminet.net/package/dev/src/AmiPhoneSrc192 AmiPhone] and [http://www.lysator.liu.se/%28frame,faq,nobg,useframes%29/ahi/v4-site/ Speak Freely] was an early attempt voice only contact. SIP and Asterisk are other PBX options.


 Facebook

If you're using the XMPP transport provided by Facebook themselves, chat.facebook.com, it looks like they're now requiring SSL transport. This means jabberwocky method below will no longer work. The best thing to do is to create an ID on a public jabber server which has a Facebook gateway.

&lt;pre &gt;
1. launch jabberwocky
2. if the login window doesn't appear on launch, select 'account' from the jabberwocky menu
3. your jabber ID will be user@chat.facebook.com where user is your user ID
4. your password is your normal facebook password
5. to save this for next time, click the popup gadget next to the ID field

6. click the 'add' button
7. click the 'close' button
8. click the 'connect' button
&lt;/pre &gt;

you're done. you can also click the 'save as default account' button if you want. jabberwocky configured to auto-connect when launching the program, but you can configure as you like. there is amigaguide documentation included with jabberwocky.

[http://amigaworld.net/modules/newbb/viewtopic.php?topic_id=37085&amp;forum=32 Read more here]

for Facebook users, you can log-in directly to Facebook with jabberwocky. just sign in as @chat.facebook.com with your Facebook password as the password


 Twitter

For a few years, there has been added a twitter transport. Servers include [http://jabber.hot-chilli.net/ jabber.hot-chili.net],  and .

An [http://jabber.hot-chilli.net/tag/how-tos/ How-to]

:Read [http://jabber.hot-chilli.net/2010/05/09/twitter-transport-working/ more]

 Instagram 

no support at the moment best to use a web browser based client

 ICQ

The new version (beta) of StriCQ uses a newer ICQ protocol. Most of the ICQ Jabber Transports still use an older ICQ protocol. You can only talk one-way to StriCQ using the older Transports. Only the newer ICQv7 Transport lets you talk both ways to StriCQ. Look at the server lists in the first section to check.

Register on a Jabber server, e.g. this one works: http://www.jabber.de/
Then login into Jabberwocky with the following login data e.g. xxx@jabber.de / Password: xxx Now add your ICQ account under the window-&gt;Agents-&gt;&quot;Register&quot;. Now Jabberwocky connects via the Jabber.de server with your ICQ account.

 Yahoo Messenger

although yahoo! does not use xmpp protocol, you should be able to use the transport methods to gain access and post your replies

 MSN

early months of 2013 Microsoft will ditch MSN Messenger client and force everyone to use Skype...but MSN protocol and servers will keep working as usual for quite a long time....

Occasionally the Messenger servers have been experiencing problems signing in.  You may need to sign in at www.outlook.com and then try again.  It may also take multiple tries to sign in.  (This also affects you if you’re using Skype.)

You have to check each servers' Agents List to see what transports (MSN protocol, ICQ protocol, etc.) are supported or use the list address' provided in the section above. Then register with each transport (IRC, MSN, ICQ, etc.) to which you need access. After registering you can Connect to start chatting.

msn.jabber.com/registered should appear in the window.

From this [http://tech.dir.groups.yahoo.com/group/amiga-jabberwocky/message/1378 JW group] guide which  helps with this process in a clear, step by step procedure.

1. Sign up on MSN's site for a passport account. This typically involves getting a Hotmail address.

2. Log on to the Jabber server of your choice and do the following:

* Select the &quot;Windows/Agents&quot; menu option in Jabberwocky.
* Select the MSN Agent from the list presented by the server.
* Click the Register button to open a new window asking for:
**Username = passort account email address, typically your hotmail address.
**Nick = Screen name to be shown to anyone you add to your buddy list.
**Password = Password for your passport account/hotmail address.
* Click the Register button at the bottom of the new window.

3. If all goes well, you will see the MSN Gateway added to your buddy list. If not, repeat part 2 on another server. Some servers may show MSN in their list of available agents, but have not updated their software for the latest protocols used by MSN.

4. Once you are registered, you can now add people to your buddy list. Note that you need to include the '''msn.''' ahead of the servername so that it knows what gateway agent to use. Some servers may use a slight variation and require '''msg.gate.''' before the server name, so try both to see what works.

If my friend's msn was amiga@hotmail.co.uk and my jabber server was @jabber.meta.net.nz..
then amiga'''%'''hotmail.com@'''msn.'''jabber.meta.net.nz

or another the trick to import MSN contacts is that you don't type the hotmail URL but the passport URL... e.g. Instead of: goodvibe%hotmail.com@msn.jabber.com  You type: goodvibe%passport.com@msn.jabber.com 
And the thing about importing contacts I'm afraid you'll have to do it by hand, one at the time...

 Google Talk

any XMPP server will work, but you have to add your contacts manually. a google talk user is typically either @gmail.com or @talk.google.com. a true gtalk transport is nice because it brings your contacts to you and (can) also support file transfers to/from google talk users.

implement Jingle a set of extensions to the IETF's Extensible Messaging and Presence Protocol (XMPP)

support ended early 2014 as Google moved to Google+ Hangouts which uses it own proprietary format


===Video Player MPlayer===

Many of the menu features (such as doubling) do not work with the current version of mplayer but using

4:3
 mplayer -vf scale=800:600 file.avi

16:9
 mplayer -vf scale=854:480 file.avi

if you want gui use;
 mplayer -gui 1 &lt;other params&gt; file.avi

&lt;pre &gt;
stack 1000000

; using AspireOS 1.xx 
; copy FROM SYS:Extras/Multimedia/MPlayer/ TO RAM:MPlayer ALL CLONE &gt; Nil:

; using Icaros Desktop 1.x 
; copy FROM SYS:Tools/MPlayer/ TO RAM:MPlayer ALL CLONE &gt; Nil:

; using Icaros Desktop 2.x 
; copy FROM SYS:Utilities/MPlayer/ TO RAM:MPlayer ALL CLONE &gt; Nil:

cd RAM:MPlayer
run MPlayer -gui &gt; Nil:
;run MPlayer -gui -ao ahi_dev -playlist http://www.radio-paralax.de/listen.pls &gt; Nil: 
&lt;/pre &gt;

$ mplayer rtsp://127.0.0.1:554/sample_300kbit.mp4


MPlayer supports multicast streaming, and rtp/rtsp protocols (it might require [http://www.live555.com/openRTSP/ live555 library] to work with some streams). But you might have to build it where it's disabled. Also, multicast won't work with some AmiTCP-likes. MIAMI supported it, though.

AROS supports IPv4 (old but works) and this includes the needed address space for RTP.

If you mean multicast via RTP - mplayer handles it. You can even force UDP over TCP

-rtsp-stream-over-tcp

If the rtsp Real Time Streaming Protocol  server needs authentification:

-user -passwd


MPlayer - Menu - Open Playlist and load already downloaded .pls or .m3u file - auto starts around 4 percent cache

MPlayer - Menu - Open Stream and copy one of the .pls lines below into space allowed, press OK and press play button on main gui interface


Old 8bit 16bit remixes chip tune game music 
 
http://www.radio-paralax.de/listen.pls 

http://scenesat.com/

http://www.shoutcast.com/radio/Amiga

http://www.theoldcomputer.com/retro_radio/RetroRadio_Main.htm

http://www.kohina.com/

http://www.remix64.com/

http://retrogamer.net/forum/

http://retroasylum.podomatic.com/rss2.xml

http://retrogamesquad.com/

http://www.retronauts.com/

http://monsterfeet.com/noquarter/

http://www.retrogamingradio.com/

http://www.radiofeeds.co.uk/mp3.asp


[[#top|...to the top]]

====ZunePaint==== 

simplified typical workflow

* importing and organizing and photo management
* making global and regional local correction(s) - recalculation is necessary after each adjustment as it is not in real-time 
* exporting your images in the best format available with the preservation of metadata


Whilst achieving 80% of a great photo with just a filter, the remaining 20% comes from a manual fine-tuning of specific image attributes.


For photojournalism, documentary, and event coverage, minimal touching is recommended. Stick to Camera Raw for such shots, and limit changes to level adjustment, sharpness, noise reduction, and white balance correction.

For fashion or portrait shoots, a large amount of adjustment is allowed and usually ends up far from the original. Skin smoothing, blemish removal, eye touch-ups, etc. are common.  Might alter the background a bit to emphasize the subject.

Product photography usually requires a lot of sharpening, spot removal, and focus stacking.

For landscape shots, best results are achieved by doing the maximum amount of preparation before/while taking the shot. No amount of processing can match timing, proper lighting, correct gear, optimal settings, etc. Excessive post-processing might give you a dramatic shot but best avoided in the long term.


* White Balance - Left Amiga or F12 and K and under &quot;Misc color effects&quot; tab with a pull down for White Balance - color temperature also known as AKA tint (movies) or tones (painting) - warm temp raise red reduce green blue - cool raise blue lower red green 
* Exposure - exposure compensation, highlight/shadow recovery
* Noise Reduction - during RAW development or using external software
* Lens Corrections - distortion, vignetting, chromatic aberrations
* Detail - capture sharpening and local contrast enhancement
* Contrast - black point, levels (sliders) and curves tools (F12 and K) 
* Framing - straighten () and crop (F12 and F) 
* Refinements - color adjustments and selective enhancements - Left Amiga or F12 and K for RGB and YUV histogram tabs - 
* Resizing - enlarge for a print or downsize for the web or email (F12 and D) 
* Output Sharpening - customized for your subject matter and print/screen size


White Balance - F12 and K

scan your image for a shade which was meant to be white (neutral with each RGB value being equal) like paper or plastic which is in the same light as the subject of the picture. Use the dropper tool to select this color, similar colours will shift and you will have selected the perfect white balance for your part of the image - for the whole picture make sure RAZ or CLR button at the bottom is pressed before applying to the image above.


Exposure correction

F12 and K - YUV Y luminosity - RGB extra red tint - move red curve slightly down and move blue green curves slightly up

Workflows in practice

* Undo - Right AROS key or F12 and Z 
* Redo - Right AROS key or F12 and R

First flatten your image (if necessary) and then do a rotation until the picture looks level. 
* Crop the picture. Click the selection button and drag a box over the area of the picture you want to keep. Press the crop button and the rest of the photo will be gone. 
* Adjust your saturation, exposure, hue levels, etc., (right AROS Key and K for color correction) until you are happy with the photo. Make sure you zoom in all of the way to 100% and look the photo over, zoom back out and move around. Look for obvious problems with the picture. 
* After coloring and exposure do a sharpen (Right AROS key and E for Convolution and select drop down option needed), e.g. set the matrix to 5x5 (roughly equivalent Amount to 60%) and set the Radius to 1.0. Click OK.


And save your picture


Implemented or would like to see for simplification and ease of use

basic filters (presets) like black and white, monochrome, edge detection (sobel), motion/gaussian blur, 
* negative, sepiatone, retro vintage, night vision, colour tint, color gradient, color temperature, glows, fire, lightning, lens flare, emboss, filmic, pixelate mezzotint, antialias, etc.

adjust / cosmetic tools such as crop, 
* reshaping tools, straighten, smear, smooth, perspective, liquify, bloat, pucker, push pixels in any direction, dispersion, transform like warp, blending with soft light, page-curl, whirl, ripple, fisheye, neon,  etc. 
* red eye fixing, blemish remover, skin smoothing, teeth whitener, make eyes look brighter, desaturate,

effects like oil paint, cartoon, pencil sketch, charcoal, noise/matrix like sharpen/unsharpen, (right AROS key with A for Artistic effects) 
* blend two image, gradient blend, masking blend, explode, implode, custom collage, surreal painting, comic book style, needlepoint, stained glass, watercolor, mosaic, stencil/outline, crayon, chalk, etc.

borders such as 
* dropshadow, rounded, blurred, color tint, picture frame, film strip polaroid, bevelled edge, etc.

brushes e.g.
* frost, smoke, etc.

and manual control of

fix lens issues including vignetting (darkening), color fringing and barrel distortion, and chromatic and geometric aberration -  lens and body profiles

perspective correction

levels - directly modify the levels of the tone-values of an image, by using sliders for highlights, midtones and shadows

curves -  Color Adjustment and Brightness/Contrast

color balance

one single color transparent (alpha channel (color information/selections) for masking and/or blending ) for backgrounds, etc.

Threshold indicates how much other colors will be considered mixture of the removed color and non-removed colors

decompose layer into a set of layers with each holding a different type of pattern that is visible within the image

any selection using any selecting tools like lasso tool, marquee tool etc. the selection will temporarily be save to alpha 
If you create your image without transparency then the Alpha channel is not present, but you can add later.

File formats like .psd (Photoshop file has layers, masks etc.  contains edited sensor data. The original sensor data is no longer available) .xcf .raw .hdr

Image Picture Formats
* low dynamic range (JPEG, PNG, TIFF 8-bit), 16-bit (PPM, TIFF), typically as a 16-bit TIFF in either ProPhoto or AdobeRGB colorspace -  TIFF files are also fairly universal – although, if they contain proprietary data, such as Photoshop Adjustment Layers or Smart Filters, then they can only be opened by Photoshop making them proprietary.
* linear high dynamic range (HDR) images (PFM, [http://www.openexr.com/ ILM .EXR], jpg, [http://aminet.net/util/dtype cr2] (canon tiff based), hdr, NEF, CRW, ARW, MRW, ORF, RAF (Fuji), PEF, DCR, SRF, ERF, DNG files are RAW converted to an Adobe proprietary format - a container that can embed the raw file as well as the information needed to open it) 
An old version of [http://archives.aros-exec.org/index.php?function=browse&amp;cat=graphics/convert dcraw]

There is no single RAW file format. Each camera manufacturer has one or more unique RAW formats. RAW files contain the brightness levels data captured by the camera sensor. This data cannot be modified. A second smaller file, separate XML file, or within a database with instructions for the RAW processor to change exposure, saturation etc. The extra data can be changed but the original sensor data is still there. RAW is technically least compatible.

A raw file is high-bit (usually 12 or 14 bits of information) but a camera-generated TIFF file will be usually converted by the camera (compressed, downsampled) to 8 bits. The raw file has no embedded color balance or color space, but the TIFF has both. These three things (smaller bit depth, embedded color balance, and embedded color space) make it so that the TIFF will lose quality more quickly with image adjustments than the raw file. The camera-generated TIFF image is much more like a camera processed JPEG than a raw file. A strong advantage goes to the raw file. The power of RAW files, such as the ability to set any color temperature non-destructively and will contain more tonal values.

The principle of preserving the maximum amount of information to as late as possible in the process. The final conversion - which will always effectively represent a &quot;downsampling&quot; - should prevent as much loss as possible.

Once you save it as TIFF, you throw away some of that data irretrievably. When saving in the lossy JPEG format, you get tremendous file size savings, but you've irreversibly thrown away a lot of image data. As long as you have the RAW file, original or otherwise, you have access to all of the image data as captured.

Keyboard equivalence with Photoshop(tm) would help 

File
PHOTOSHOP	SHORTCUT	GIMP
New	Ctrl+n	New
Open	Ctrl+o	Open
Close	Ctrl+w	Close
Save	Ctrl+s	Save
Save as	Shift+Ctrl+s	Save as
Revert	F12	Revert
Print	Ctrl+p	Print
Exit	Ctrl+q	Quit
 
Edit
PHOTOSHOP	SHORTCUT	GIMP
Undo/Redo (1 level)	Ctrl+z	Undo (Redo is Shift+Ctrl+z)
Cut	Ctrl+x	Cut
Copy	Ctrl+c	Copy
Paste	Ctrl+v	Paste
Paste Into	Shift+Ctrl+v	Paste Into
Fill with FG color	Alt+Backspace	Fill with FG color
Fill with BG color	Control+Backspace	Fill with BG color
 
Image/Colors
PHOTOSHOP	SHORTCUT	GIMP
Levels	Ctrl+l	Levels
Auto Contrast	Shift+Ctrl+Alt+l	Stretch Contrast (same?)
Curves	Ctrl+m	Curves
Color Balance	Ctrl+b	Color Balance
Hue/Saturation	Ctrl+u	Hue-Saturation
Desaturate	Shift+Ctrl+u	Desaturate
Invert	Ctrl+i	Invert
Default Colors	d	Default Colors
Switch Colors	x	Switch Colors
 
Layer
PHOTOSHOP	SHORTCUT	GIMP
New Layer	Shift+Ctrl+n	New Layer
Layer via Copy	Ctrl+j	Duplicate Layer
Bring (layer) to Front	Shift+Ctrl+]	Layer to Top
Send (layer) to Back	Shift+Ctrl+[	Layer to Bottom
Bring (layer) Forward	Ctrl+]	Raise Layer
Send (layer) Backward	Ctrl+[	Lower Layer
Select Top Layer	Shift+Alt+]	Select Top Layer
Select Bottom Layer	Shift+Alt+[	Select Bottom Layer
Select One Layer Forward	Alt+]	Select Previous Layer
Select One Layer Backward	Alt+[	Select Next Layer
Merge Down	Ctrl+e	Merge Down
Merge Visible	Shift+Ctrl+e	Merge Visible
Preserve Transparency	/	Keep Transparency
Cycle Modes Forwards	Shift+=	Next Layer Mode
Cycle Modes Backwards	Shift+-	Previous Layer Mode
 
Select
PHOTOSHOP	SHORTCUT	GIMP
Select All	Ctrl+a	Select All
Deselect	Ctrl+d	Select None
Inverse	Shift+Ctrl+i	Invert
Feather	Ctrl+Alt+d	Feather
 
View
PHOTOSHOP	SHORTCUT	GIMP
Zoom In	Ctrl+=	Zoom In
Zoom Out	Ctrl+-	Zoom Out
Fit on Screen	Ctrl+0	Zoom to Fit Window
Actual Pixels	Ctrl+Alt+0	Zoom 1:1
Show/Hide Extras	Ctrl+h	Toggle Show Selection (close enough?)
Show/Hide Guides	Ctrl+'	Toggle Show Guides
Show/Hide Grid	Ctrl+Alt+'	Toggle Show Grid
Show/Hide Rulers	Ctrl+r	Toggle Show Rulers
Snap	Ctrl+;	Snap to Guides
Scroll View Up	Page Up	Scroll Page Up
Scroll View Down	Page Down	Scroll Page Down
Scroll View Left	Ctrl+Page Up	Scroll Page Left
Scroll View Right	Ctrl+Page Down	Scroll Page Right
 
Window/Dialogs
PHOTOSHOP	SHORTCUT	GIMP
?	F5	Tools Dialog
Color Tab	F6	Colors Dialog
Layers Tab	F7	Layers Dialog
Info Tab	F8	Image Information
 
Tools
PHOTOSHOP	SHORTCUT	GIMP
Rectangular Marquee Tool	m	Rect Select Tool
Elliptical Marquee Tool	Shift+m	Ellipse Select Tool
 	*This is a toggle between 'Elliptical Marquee Tool' and 'Rectangular Marquee Tool' in Photoshop	 
Move Tool	v	Move Tool
Lasso Tool	l	Free Select Tool
Magic Wand Tool	w	Fuzzy Select Tool
Crop Tool	c	Crop &amp; Resize Tool
Airbrush Tool	j	Airbrush Tool
Paintbrush Tool	b	Paintbrush Tool
Clone Stamp Tool	s	Clone Stamp Tool
Eraser Tool	e	Eraser Tool
Gradient Tool	g	Blend Tool
Paint Bucket Tool	Shift+g	Bucket Fill Tool
 	*This is a toggle between 'Paint Bucket Tool' and 'Gradient Tool' in Photoshop	 
Blur Tool	r	Convolve Tool
Dodge Tool	o	DodgeBurn Tool
Type Tool	t	Text Tool
Pen Tool	p	Bezier Select Tool
Eye Dropper Tool	i	Color Picker Tool
Zoom Tool	z	Magnify Tool
Previous Brush	,	Previous Brush
Next Brush	.	Next Brush
First Brush	Shift+&lt;	First Brush
Last Brush	Shift+&gt;	Last Brush
Decrease Brush Size	[	Decrease Brush Size
Increase Brush Size	]	Increase Brush Size
Decrease Brush Hardness	{	Decrease Brush Hardness
Increase Brush Hardness	}	Increase Brush Hardness
 
Help
PHOTOSHOP	SHORTCUT	GIMP
Help	F1	Help
Context Help	Shift+F1	Context Help
 
Misc.
PHOTOSHOP	SHORTCUT	GIMP
Last Filter	Ctrl+f	Repeat Last Filter
?	Shift+Ctrl+f	Reshow Last Filter
Preferences	Ctrl+k	Preferences
Liquify	Shift+Ctrl+x	IWarp (close enough?)
Toggle Quick Mask	q	Toggle Quick Mask


Spotlights - triangle of white opaque shape

Cutting out and/or replacing unwanted background or features - select large areas with the selection option like the Magic Wand tool (aka Color Range) or the Lasso (quick and fast) with feather 2 to soften edge or the pen tool which adds points/lines/Bézier curves (better control but slower), hold down the shift button as you click to add extra points/areas of the subject matter to remove. Increase the tolerance to cover more areas. To subtract from your selection hold down alt as you're clicking. 
* Layer masks are a better way of working than Erase they clip (black hides/hidden white visible/reveal). Clone Stamp can be simulated by   and brushes for other areas. 
* Leave the fine details like hair, fur, etc. to later with lasso and the shift key to draw a line all the way around your subject. Gradient Mapping - Inverse - Mask. i.e. Refine your selected image with edge detection and using the radius and edge options / adjuster (increase/decrease contrast) so that you will capture more fine detail from the background allowing easier removal. 
Remove fringe/halo

saving image as png rather than jpg/jpeg to keep transparency background intact.


Implemented [http://colorizer.org/ colour model representations] [http://paulbourke.net/texture_colour/colourspace/ Mathematical approach] - Photo stills are spatially 2d (h and w), but are colorimetrically 3d (r g and b, or H L S, or Y U V etc.) as well. 
* RGB - split cubed mapped color model for photos and computer graphics hardware using the light spectrum (adding and subtracting) 
* YUV - Y-Lightness U-blue/yellow V-red/cyan (similar to YPbPr and YCbCr) used in the PAL, NTSC, and SECAM composite digital TV color [http://crewofone.com/2012/chroma-subsampling-and-transcoding/#comment-7299 video]


Histograms

White balanced (neutral) if the spike happens in the same place in each channel of the RGB graphs. If not, you're not balanced. 
If you have sky you'll see the blue channel further off to the right.

RGB is best one to change colours. These elements RGB is a 3-channel format containing data for Red, Green, and Blue in your photo scale between 0 and 255. The area in a picture that appears to be brighter/whiter contains more red color as compared to the area which is relatively darker. Similarly in the green channel the area that appears to be darker contains less amount of green color as compared to the area that appears to be brighter.  Similarly in the blue channel the area appears to be darker contains less amount of blue color as compared to the area that appears to be brighter. Brightness luminance histogram also matches the green histogram more than any other color - human eye interprets green better e.g. RGB rough ratio 15/55/30%

RGBA (RGB+A, A means alpha channel) .  The alpha channel is used for &quot;alpha compositing&quot;, which can mostly be associated as &quot;opacity&quot;.  AROS deals in RGB with two digits for every color (red, green, blue), in ARGB you have two additional hex digits for the alpha channel.

The shadows are represented by the left third of the graph.  The highlights are represented by the right third.  And the midtones are, of course, in the middle.  The higher the black peaks in the graph, the more pixels are concentrated in that tonal range (total black area). 
By moving the black endpoint, which identifies the shadows (darkness) and a white light endpoint (brightness) up and down either sides of the graph, colors are adjusted based on these points. 
By dragging the central one, can increased the midtones and control the contrast, raise shadows levels, clip or softly eliminate unsafe levels, alter gamma, etc... in a way that is much more precise and creative .


RGB Curves

* Move left endpoint (black point) up or right endpoint (white point) up brightens 
* Move left endpoint down or right endpoint down darkens

Color Curves

* Dragging up on the Red Curve increases the intensity of the reds in the image but 
* Dragging down on the Red Curve decreases the intensity of the reds and thus increases the apparent intensity of its complimentary color, cyan. Green’s complimentary color is magenta, and blue’s is yellow.
&lt;pre&gt;
 Red &lt;-&gt; Cyan
 Green &lt;-&gt;Magenta
 Blue &lt;-&gt;Yellow 
&lt;/pre&gt;

YUV Best option to analyse and pull out statistical elements of any picture (i.e.  separate luminance data from color data). The line in Y luma tone box represents the brightness of the image with the point in the bottom left been black, and the point in the top right as white.  A low-contrast image has a concentrated clump of values nearer to the center of the graph. By comparison, a high-contrast image has a wider distribution of values across the entire width of the Histogram.   A histogram that is skewed to the right would indicate a picture that is a bit overexposed because most of the color data is on the lighter side (increase exposure with higher value F), while a histogram with the curve on the left shows a picture that is underexposed. This is good information to have when using post-processing software because it shows you not only where the color data exists for a given picture, but also where any data has been clipped (extremes on edges of either side): that is, it does not exist and, therefore, cannot be edited.  By dragging the endpoints of the line and as well as the central one, can increased the dark/shadows, midtones and light/bright parts and control the contrast, raise shadows levels, clip or softly eliminate unsafe levels, alter gamma, etc... in a way that is much more precise and creative .

The U and V chroma parts show color difference components of the image. It’s useful for checking whether or not the overall chroma is too high, and also whether it’s being limited too much
Can be used to create a negative image but also 
With U (Cb), the higher value you are, the more you're on the blue primary color. If you go to the low values then you're on blue complementary color, i.e. yellow.
With V (Cr), this is the same principle but with Red and Cyan.
e.g. If you push U full blue and V full red, you get magenta. If you push U full yellow and V full Cyan then you get green.

YUV simultaneously adds to one side of the color equation while subtracting from the other.  
using YUV to do color correction can be very problematic because each curve alters the result of each other: the mutual influence between U and V often makes things tricky. You may also be careful in what you do to avoid the raise of noise (which happens very easily). Best results are obtained with little adjustments

sunset that looks uninspiring and needs some color pop especially for the rays over the hill, a subtle contrast raise while setting luma values back to the legal range without hard clipping.


Free royalty pictures, [www.freeimages.com ], [http://imageshack.us/ ], [http://photobucket.com/ ], [http://rawpixels.net/], [], [], [], 


====Lunapaint====

Pixel based drawing app with onion-skin animation function

 Blocking, Shading, Coloring, adding detail 

&lt;pre&gt;
b BRUSH
e ERASER

alt eyedropper 
v layer tool 

z ZOOM / MAGNIFY &lt; &gt; n 
spc panning 
m  marque 
q lasso 
w same color selection / region 
&lt;/pre&gt;

&lt;pre&gt;
, LM RM
v 
V
f  filter 
F 
.  size 

p 
,  pick color 
[] last / next color 
&lt;/pre&gt;


There is not much missing in Lunapaint to be as good as FlipBook and then you have to take into account that Flipbook is considered to be amongst the best and easiest to use animation software out there. Ok to be honest Flipbook has some nice features that require more heavy work but those aren't so much needed right away, things like camera effects, sound, smart fill, export to different movie file formats etc.

Tried Flipbook with my tablet and compared it to Luna. The feeling is the same when sketching. LunaPaint is very responsive/fluent to draw with. Just as Flipbook is, and that responsiveness is something its users have mentioned as one of the positive sides of said software.

 author was learning MUI. Some parts just have to be rewritten with proper MUI classes before new features can be added.

* add [Frame Add] / [Frame Del]
* whole animation feature is impossible to use. If you draw 2 color maybe but if you start coloring your cells then you get in trouble
* pickup the entire image as a brush, not just a selection ? And consequently remove the brush from memory when one doesn't need it anymore. can pick up a brush and put it onto a new image but cropping isn't possible, nor to load/save brushes.
* Undo is something I longed for ages in Lunapaint.
* to import into the current layer, other types of images (e.g. JPEG) besides RAW64.
* implement graphic tablet features support


**GENERAL DRAWING**

Miss it very much:
UNDO
ERASER
COLORPICKER - has to show on palette too which color got picked.
BACKGROUND COLOR -Possibility to select from &quot;New project screen&quot;

Miss it somewhat:
ICON for UNDO
ICON for ERASER
ICON for CLEAR SCREEN ( What can I say? I start over from scratch very often )
BRUSH - possibility to cut out as brush not just copy off image to brush

**ANIMATING**

Miss it very much:
NUMBER OF CELLS - Possibity to change total no. of cells during project
ANIM BRUSH - Possibility to pick up a selected part of cells into an animbrush

Miss it somewhat:
ADD/REMOVE FRAMES: Add/remove single frame

In general LunaPaint is really well done and it feels like a new DeluxePaint version. It works with my tablet. Sure there's much missing of course but things can always be added over time. So there is great potential in LunaPaint that's for sure. Animations could be made in it and maybe put together in QuickVideo, saving in .gif or .mng etc some day.


LAYERS
-Layers names don't get saved globally in animation frames
-Layers order don't change globally in an animation (perhaps as default?).

EXPORTING IMAGES
-Exporting frames to JPG/PNG gives problems with colors. (wrong colors. See my animatiopn --&gt; My robot was blue now it's &quot;gold&quot; ) I think this only happens if you have layers.
-Trying to flatten the layers before export doesn't work if you have animation frames only the one you have visible will flatten properly all other frames are destroyed. (Only one of the layers are visible on them)
-Exporting images filenames should be for example e.g. file0001, file0002...file0010 instead as of now file1, file2...file10

LOAD/SAVE (Preferences)
-Make a setting for the default &quot;Work&quot; folder.

* Destroyed colors if exported image/frame has layers 
* mystic color cycling of the selected color while stepping frames back/forth (annoying)

&lt;pre&gt;
Deluxe Paint II enhanced key shortcuts 
    NOTE: @ denotes the ALT key

    [Technique]

    F1  - Paint
    F2  - Single Colour
    F3  - Replace
    F4  - Smear
    F5  - Shade
    F6  - Cycle
    F7  - Smooth
     M  - Colour Cycle

    [Brush]

     B  - Restore
     O  - Outline
     h  - Halve brush size
     H  - Double brush size
     x  - Flip brush on X axis
     X  - Double brush size on X axis only
     y  - Flip on Y 
     Y  - Double on Y
     z  - Rotate brush 90 degrees
     Z  - Stretch

    [Stencil]

     `  - Stencil On

    [Miscellaneous]

    F9  - Info Bar
    F10 - Selection Bar
    @o  - Co-Ordinates
    @a  - Anti-alias
    @r  - Colourise
    @t  - Translucent
    TAB - Colour Cycle

    [Picture]

     L  - Load
     S  - Save
     j  - Page to Spare(Flip)
     J  - Page to Spare(Copy)
     V  - View Page
     Q  - Quit

    [General Keys]

     m  - Magnify
     &lt;  - Zoom In
     &gt;  - Zoom Out
     [  - Palette Colour Up
     ]  - Palette Colour Down
     (  - Palette Colour Left
     )  - Palette Colour Right
     ,  - Eye Dropper
     .  - Pixel / Brush Toggle
     /  - Symmetry
     |  - Co-Ordinates
    INS - Perspective Control
    +/- - Brush Size (Fine Control)
     w  - Unfilled Polygon
     W  - Filled Polygon
     e  - Unfilled Ellipse
     E  - Filled Ellipse
     r  - Unfilled Rectangle
     R  - Filled Rectangle
     t  - Type/text tool
     a  - Select Font
    u/U - Undo
     d  - Brush
     D  - Filled Non-Uniform Polygon
    f/F - Fill Options
    g/G - Grid
    h/H - Brush Size (Coarse Control)
     K  - Clear
     c  - Unfilled Circle
     C  - Filled Circle
     v  - Line
     b  - Scissor Select and Toggle
     B  - Brush
    {,} - Toggle between two background colours
&lt;/pre&gt;

====Lodepaint====

Pixel based painting artwork app

====Grafx2====

Pixel based painting artwork app aesprite like 

[https://www.youtube.com/watch?v=59Y6OTzNrhk aesprite workflow keys and tablet use], [], 


====Vector Graphics ZuneFIG====

Vector Image Editing of files .svg .ps .eps


*Objects - raise lower rotate flip aligning snapping 
*Path - unify subtract intersect exclude divide 
*Colour - fill stroke 
*Stroke - size 
*Brushes - 
*Layers - 
*Effects - gaussian bevels glows shadows 
*Text    - 
*Transform - 


 AmiFIG ([http://epb.lbl.gov/xfig/frm_introduction.html xfig manual]) 

[[File:MyScreen.png|thumb|left|alt=Showing all Windows open in AmiFIG.|All windows available to AmiFIG.]]

for drawing simple to intermediate vector graphic images for scientific and technical uses and for illustration purposes for those with talent

;Menu options
* Load - fig format but import(s) SVG
* Save - fig format but export(s) eps, ps, pdf, svg and png
* PAN = Ctrl + Arrow keys 
* Deselect all points

There is no selected object until you apply the tool, and the selected object is not highlighted.

;Metrics - to set up page and styles - first window to open on new drawings

;Tools - Drawing Primitives - set Attributes window first before clicking any Tools button(s) 
* Shapes - circles, ellipses, arcs, splines, boxes,  polygon 
* Lines - polylines
* Text &quot;T&quot; button 
* Photos - bitmaps
* Compound - Glue, Break, Scale 
* POINTs - Move, Add, Remove 
* Objects - Move, Copy, Delete, Mirror, Rotate, Paste 
use right mouse button to stop extra lines, shapes being formed and the left mouse to select/deselect tools button(s)
* Rotate - moves in 90 degree turns centered on clicked POINT of a polygon or square

;Attributes which provide change(s) to the above primitives 
* Color
* Line Width
* Line Style
* arrowheads

;Modes 
Choose from freehand, charts, figures, magnet, etc.

;Library - allows .fig clip-art to be stored 
* compound tools to add .fig(s) together

;FIG 3.2 [http://epb.lbl.gov/xfig/fig-format.html Format] as produced by xfig version 3.2.5 
&lt;pre&gt;
Landscape
Center
Inches
Letter 
100.00
Single
-2
1200 2
4 0 0 50 -1 0 12 0.0000 4 135 1050 1050 2475 This is a test.01
&lt;/pre&gt;

# change the text alignment within the textbox. I can choose left, center, or right aligned by either changing the integer in the second column from 0 (left) to 1 or 2 (center, or right). 
# The third integer in the row specifies fontcolor. For instance, 0 is black, but blue is 1 and Green3 is 13.
# The sixth integer in the bottom row specifies fontface. 0 is Times-Roman, but 16 is Helvetica (a MATLAB default).
# The seventh number is fontsize. 12 represents a 12pt fontsize. Changing the fontsize of an item really is as easy as changing that number to 20.
# The next number is the counter-clockwise angle of the text. Notice that I have changed the angle to .7854 (pi/4 rounded to four digits=45 degrees).
# twelfth number is the position according to the standard “x-axis” in Xfig units from the left. Note that 1200 Xfig units is equivalent to once inch.
# thirteenth number is the “y-position” from the top using the same unit convention as before.

* The nested text string is what you entered into the textbox.
* The “01″ present at the end of that line in the .fig file is the closing tag. For instance, a change to \100 appends a @ symbol at the end of the period of that sentence.

; Just to note there are no layers, no 3d functions, no shading, no transparency, no animation


[[#top|...to the top]]

===Audio===


# AHI uses linear panning/balance, which means that in the center, you will get -6dB. If an app uses panning, this is what you will get. Note that apps like Audio Evolution need panning, so they will have this problem.

# When using AHI Hifi modes, mixing is done in 32-bit and sent as 32-bit data to the driver. The Envy24HT driver uses that to output at 24-bit (always).

# For the Envy24/Envy24HT, I've made 16-bit and 24-bit inputs (called Line-in 16-bit, Line-in 24-bit etc.). There is unfortunately no app that can handle 24-bit recording.


====Music Mods====

Digital module (mods) trackers are music creation software using samples and sometimes soundfonts, audio plugins (VST, AU or RTAS), MIDI.

Generally, MODs are similar to MIDI in that they contain note on/off and other sequence messages that control the mod player. Unlike (most) midi files, however, they also contain sound samples that the sequence information actually plays. MOD files can have many channels (classic amiga mods have 4, corresponding to the inbuilt sound channels), but unlike MIDI, each channel can typically play only one note at once. However, since that note might be a sample of a chord, a drumloop or other complex sound, this is not as limiting as it sounds.

Like MIDI, notes will play indefinitely if they're not instructed to end. Most trackers record this information automatically if you play your music in live. If you're using manual note entry, you can enter a note-off command with a keyboard shortcut - usually Caps Lock.

In fact when considering file size MOD is not always the best option. Even a dummy song wastes few kilobytes for nothing when a simple SID tune could be few hundreds bytes and not bigger than 64kB. AHX is another small format, AHX tunes are never larger than 64kB excluding comments.

[https://www.youtube.com/watch?v=rXXsZfwgil Protrekkr] (previously aka [w:Juan_Antonio_Arguelles_Rius|NoiseTrekkr])

If Protrekkr does not start, please check if the Unit 0 has been setup in the AHI prefs and still not, go to the directory utilities/protrekkr and double click on the Protrekkr icon

*Sample
*Note - Effect 
*Track (column) - Pattern - Order

It all starts with the Sample which is used to create Note(s) in a Track (column of a tracker) 
The Note can be changed with an Effect.  A Track of Note(s) can be collected into a Pattern (section of a song) and these can be given Order to create the whole song.

Patience (notes have to be entered one at a time) or playing the bassline on a midi controller (faster - see midi section above).  Best approach is to wait until a melody popped into your head.

*Up-tempo means the track should be reasonably fast, but not super-fast. 
*Groovy and funky imply the track should have some sort of &quot;swing&quot; feel, with plenty of syncopation or off beat emphasis and a recognizable, melodic bass line. 
*Sweet and happy mean upbeat melodies, a major key and avoiding harsh sounds.
*Moody - minor key

First, create a quick bass sound, which is basically a sine wave, but can be hand drawn for a little more variance. It could also work for the melody part, too.

This is usually a bass guitar or some kind of synthesizer bass. The bass line is often forgotten by inexperienced composers, but it plays an important role in a musical piece. Together with the rhythm section the bass line forms the groove of a song. It's the glue between the rhythm section and the melodic layer of a song.

The drums are just pink noise samples, played at different frequencies to get a slightly different sound for the kick, snare, and hihats.

Instruments that fall into the rhythm category are bass drums, snares, hi-hats, toms, cymbals, congas, tambourines, shakers, etc. Any percussive instrument can be used to form part of the rhythm section.

The lead is the instrument that plays the main melody, on top of the chords. There are many instruments that can play a lead section, like a guitar, a piano, a saxophone or a flute. The list is almost endless. There is a lot of overlap with instruments that play chords. Often in one piece an instrument serves both roles. The lead melody is often played at a higher pitch than the chords.

Listened back to what was produced so far, and a counter-melody can be imagined, which can be added with a triangle wave.

To give the ends of phrases some life, you can add a solo part with a crunchy synth. By hitting random notes in the key of G, then edited a few of them.

For the climax of the song, filled out the texture with a gentle high-pitch pad… …and a grungy bass synth.


The arrow at A points at the pattern order list. As you see, the patterns don't have to be in numerical order. This song starts with pattern &quot;00&quot;, then pattern &quot;02&quot;, then &quot;03&quot;, then &quot;01&quot;, etcetera. Patterns may be repeated throughout a song.

The B arrow points at the song title. Below it are the global BPM and speed parameters. These determine the tempo of the song, unless the tempo is altered through effect commands during the song.

The C arrow points at the list of instruments. An instrument may consist of multiple samples. Which sample will be played depends on the note. This can be set in the Instrument Editing screen. Most instruments will consist of just one sample, though. The sample list for the selected instrument can be found under arrow D.

Here's a part of the main editing screen. This is where you put in actual notes. Up to 32 channels can be used, meaning 32 sounds can play simultaneously. The first six channels of pattern &quot;03&quot; at order &quot;02&quot; are shown here. The arrow at A points at the row number. The B arrow points at the note to play, in this case a C4. The column pointed at by the C arrow tells us which instrument is associated with that note, in this case instrument #1 &quot;Kick&quot;.

The column at D is used (mainly) for volume commands. In this case it is left empty which means the instrument should play at its default volume. You can see the volume column being used in channel #6.

The E column tells us which effect to use and any parameters for that effect. In this case it holds the &quot;F&quot; effect, which is a tempo command. The &quot;04&quot; means it should play at tempo 4 (a smaller number means faster).

Base pattern

When I create a new track I start with what I call the base pattern. It is worthwhile to spend some time polishing it as a lot of the ideas in the base pattern will be copied and used in other patterns. At least, that's how I work. Every musician will have his own way of working. In &quot;Wild Bunnies&quot; the base pattern is pattern &quot;03&quot; at order &quot;02&quot;.

In the section about selecting samples I talked about the four different categories of instruments: drums, bass, chords and leads. That's also how I usually go about making the base pattern. I start by making a drum pattern, then add a bass line, place some chords and top it off with a lead. This forms the base pattern from which the rest of the song will grow.


Drums

Here's a screenshot of the first four rows of the base pattern. I usually reserve the first four channels or so for the drum instruments. Right away there are a couple of tricks shown here. In the first channel the kick, or bass drum, plays some notes. Note the alternating F04 and F02 commands. The &quot;F&quot; command alters the tempo of the song and by quickly alternating the tempo; the song will get some kind of &quot;swing&quot; feel.

In the second channel the closed hi-hat plays a fairly simple pattern. Further down in the channel, not shown here, some open hi-hat notes are added for a bit of variation.

In the third and fourth channel the snare sample plays. The &quot;8&quot; command is for panning. One note is panned hard to the left and the other hard to the right. One sample is played a semitone lower than the other. This results in a cool flanging effect. It makes the snare stand out a little more in the mix.


Bass line

There are two different instruments used for the bass line. Instrument #6 is a pretty standard synthesized bass sound. Instrument #A sounds a bit like a slap bass when used with a quick fade out. By using two different instruments the bass line sounds a bit more ”human”. The volume command is used to cut off the notes. However, it is never set to zero. Setting the volume to a very small value will result in a reverb-like effect. This makes the song sound more &quot;live&quot;.

The bass line hints at the chords that will be played and the key the song will be in. In this case the key of the song is D-major, a positive and happy key.


Chords

The D major chords that are being played here are chords stabs; short sounds with a quick decay (fade out). Two different instruments (#8 and #9) are used to form the chords. These instruments are quite similar, but have a slightly different sound, panning and volume decay. Again, the reason for this is to make the sound more human. The volume command is used on some chords to simulate a delay, to achieve more of a live feel. The chords are placed off-beat making for a funky rhythm.


Lead

Finally the lead melody is added. The other instruments are invaluable in holding the track together, but the lead melody is usually what catches people's attention.

A lot of notes and commands are used here, but it looks more complex than it is. A stepwise ascending melody plays in channel 13. Channel 14 and 15 copy this melody, but play it a few rows later at a lower volume. This creates an echo effect. A bit of panning is used on the notes to create some stereo depth. Like with the bass line, instead of cutting off notes the volume is set to low values for a reverb effect. The &quot;461&quot; effect adds a little vibrato to the note, which sounds nice on sustained notes.

Those paying close attention may notice the instrument used here for the lead melody is the same as the one used for the bass line (#6 &quot;Square&quot;), except played two or three octaves higher. This instrument is a looped square wave sample. Each type of wave has its own quirks, but the square wave (shown below) is a really versatile wave form.

Song structure

Good, catchy songs are often carefully structured into sections, some of which are repeated throughout the song with small variations.

A typical pop-song structure is: Intro - Verse - Chorus - Verse - Chorus - Bridge - Chorus.

Other single sectional song structures are

&lt;pre&gt;
Strophic or AAA Song Form - oldest story telling with refrain (often title of the song) repeated in every verse section melody 
AABA Song Form - early popular, jazz and gospel fading during the 1960s 
AB or Verse/Chorus Song Form - songwriting format of choice for modern popular music since the 1960s 
Verse/Chorus/Bridge Song Form
ABAB Song Form
ABAC Song Form
ABCD Song Form
AAB 12-Bar Song Form - three four-bar lines or sub-sections 
8-Bar Song Form
16-Bar Song Form
Hybrid / Compound Song Forms
&lt;/pre&gt;

The most common building blocks are:

#INTRODUCTION(INTRO)
#VERSE
#REFRAIN
#PRE-CHORUS / RISE / CLIMB
#CHORUS
#BRIDGE
#MIDDLE EIGHT
#SOLO / INSTRUMENTAL BREAK
#COLLISION
#CODA / OUTRO
#AD LIB (OFTEN IN CODA / OUTRO)

The chorus usually has more energy than the verse and often has a memorable melody line. As the chorus is repeated the most often during the song, it will be the part that people will remember.

The bridge often marks a change of direction in the song. It is not uncommon to change keys in the bridge, or at least to use a different chord sequence. The bridge is used to build up tension towards the big finale, the last repetition of chorus.


 Playing

RCTRL:                           Play song from row 0.

LSHIFT + RCTRL:                  Play song from current row.

RALT:                            Play pattern from row 0.

LSHIFT + RALT:                   Play pattern from current row.

Left mouse on '&gt;':               Play song from row 0.

Right mouse on '&gt;':              Play song from current row.

Left mouse on '|&gt;':              Play pattern from row 0.

Right mouse on '|&gt;':             Play pattern from current row.

Left mouse on 'Edit/Record':     Edit mode on/off.

Right mouse on 'Edit/Record':    Record mode on/off.


 Editing 


LSHIFT + ESCAPE:                 Switch large patterns view on/off

TAB:                    Go to next track

LSHIFT + TAB:                    Go to prev. track

LCTRL + TAB:                    Go to next note in track

LCTRL + LSHIFT + TAB:           Go to prev. note in track

SPACE:                           Toggle Edit mode On &amp; Off

(Also stop if the song is being played)

SHIFT SPACE:                     Toggle Record mode On &amp; Off

(Wait for a key note to be pressed

or a midi in message to be received)

DOWN ARROW:                      1 Line down

UP ARROW:                        1 Line up

LEFT ARROW:                      1 Row left

RIGHT ARROW:                     1 Row right

PREV. PAGE:                      16 Arrows Up

NEXT PAGE:                       16 Arrows Down

HOME / END:                      Top left / Bottom right of pattern

LCTRL + HOME / END:              First / last track

F5, F6, F7, F8, F9:              Jump to 0, 1/4, 2/4, 3/4, 4/4 lines of the patterns

+ - (Numeric keypad):           Next / Previous pattern

LCTRL + LEFT / RIGHT:           Next / Previous pattern

LCTRL + LALT + LEFT / RIGHT:    Next / Previous position

LALT + LEFT / RIGHT:           Next / Previous instrument

LSHIFT + M:                      Toggle mute state of the current channel

LCTRL + LSHIFT + M:             Solo the current track / Unmute all

LSHIFT + F1 to F11:              Select a tab/panel

LCTRL + 1 to 4:                 Select a copy buffer


 Tracking 

1st and 2nd keys rows:           Upper octave row

3rd and 4th keys rows:           Lower octave row

RSHIFT:                          Insert a note off

/ and * (Numeric keypad)

or F1 F2:                        -1 or +1 octave

INSERT / BACKSPACE:              Insert or Delete a line in current track

or current selected block.

LSHIFT + INSERT / BACKSPACE:     Insert or Delete a line in current pattern

DELETE (NOT BACKSPACE):          Empty a column or a selected block.


 Blocks

(Blocks can also be selected with the mouse by holding the right button and scrolling the pattern with the mouse wheel).


LCTRL + A:          Select entire current track

LCTRL + LSHIFT + A: Select entire current pattern

LALT + A:          Select entire column note in a track

LALT + LSHIFT + A: Select all notes of a track

LCTRL + X:          Cut the selected block and copy it into the block-buffer

LCTRL + C:          Copy the selected block into the block-buffer

LCTRL + V:          Paste the data from the block buffer into the pattern

LCTRL + I:          Interpolate selected data from the first to the last row of a selection

LSHIFT + ARROWS

PREV. PAGE

NEXT PAGE: Select a block

LCTRL + R:          Randomize the select columns of a selection, works similar to CTRL + I (interpolating them)

LCTRL + U:          Transpose the note of a selection to 1 seminote higher

LCTRL + D:          Transpose the note of a selection to 1 seminote lower

LCTRL + LSHIFT + U: Transpose the note of a selection to 1 seminote higher (only for the current instrument)

LCTRL + LSHIFT + D: Transpose the note of a selection to 1 seminote lower  (only for the current instrument)

LCTRL + H:          Transpose the note of a selection to 1 octave higher

LCTRL + L:          Transpose the note of a selection to 1 octave lower

LCTRL + LSHIFT + H: Transpose the note of a selection to 1 octave higher (only for the current instrument)

LCTRL + LSHIFT + L: Transpose the note of a selection to 1 octave lower (only for the current instrument)

LCTRL + W:          Save the current selection into a file


 Misc 


LALT + ENTER:     Switch between full screen / windowed mode

LALT + F4:        Exit program (Windows only)

LCTRL + S:         Save current module

LSHIFT + S:         Switch top right panel to synths list

LSHIFT + I:         Switch top right panel to instruments list


&lt;pre&gt;
C-x   xh xx xx hhhh             Volume 
B-x   xh xx xx hhhh             Jump to 
A#x  xh xx xx hhhh hhhh   Slide 
F-x    xh xx xx hhhh            Tempo 
D-x   xh xx xx hhhh             Pattern Break 
G#x  xh xx xx hhhh
&lt;/pre&gt;

h Hex 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13

d Dec 01 02 03 04 05 06 07 08 09 10  11 12 13 14 15 16 17 18 19

The Set Volume command: C. Input a note, then move the cursor to the effects command column and type a C. Play the pattern, and you shouldn't be able to hear the note you placed the C by. This is because the effect parameters are 00. Change the two zeros to a 40(Hex)/64(Dec), depending on what your tracker uses. Play back the pattern again, and the note should come in at full volume.

The Position Jump command next. This is just a B followed by the position in the playing list that you want to jump to. One thing to remember is that the playing list always starts at 0, not 1. This command is usually in Hex.

Onto the volume slide command: A. This is slightly more complex (much more if you're using a newer tracker, if you want to achieve the results here, then set slides to Amiga, not linear), due to the fact it depends on the secondary tempo. For now set a secondary tempo of 06 (you can play around later), load a long or looped sample and input a note or two. A few rows after a note type in the effect command A. For the parameters use 0F. Play back the pattern, and you should notice that when the effect kicks in, the sample drops to a very low volume very quickly. Change the effect parameters to F0, and use a low volume command on the note. Play back the pattern, and when the slide kicks in the volume of the note should increase very quickly.
This because each part of the effect parameters for command A does a different thing. The first number slides the volume up, and the second slides it down. It's not recommended that you use both a volume up and volume down at the same time, due to the fact the tracker only looks for the first number that isn't set to 0. If you specify parameters of 8F, the tracker will see the 8, ignore the F, and slide the volume up. Using a slide up and down at same time just makes you look stupid. Don't do it...

The Set Tempo command: F, is pretty easy to understand. You simply specify the BPM (in Hex) that you want to change to. One important thing to note is that values of lower than 20 (Hex) sets the secondary tempo rather than the primary.

Another useful command is the Pattern Break: D. This will stop the playing of the current pattern and skip to the next one in the playing list. By using parameters of more than 00 you can also specify which line to begin playing from.

Command 3 is Portamento to Note. This slides the currently playing note to another note, at a specified speed. The slide then stops when it reaches the desired note. 
&lt;pre&gt;
   C-2 1 000 - Starts the note playing
   ---      000
   C-3    330 - Starts the slide to C-3 at a speed of 30.
   ---     300 - Continues the slide
   ---     300 - Continues the slide
&lt;/pre&gt;
Once the parameters have been set, the command can be input again without any parameters, and it'll still perform the same function unless you change the parameters. This memory function allows certain commands to function correctly, such as command 5, which is the Portamento to Note and Volume Slide command. Once command 3 has been set up command 5 will simply take the parameters from that and perform a Portamento to Note. Any parameters set up for command 5 itself simply perform a Volume Slide identical to command A at the same time as the Portamento to Note.

This memory function will only operate in the same channel where the original parameters were set up.
There are various other commands which perform two functions at once. They will be described as we come across them.

C-3  04  ..  ..  09  00 ---&gt; C-3  04  ..  ..  09  00

C-3  04  ..  ..  09  00 ---&gt; C-3  04  ..  ..  09  02

C-3  04  ..  ..  09  00 ---&gt; C-3  04  ..  ..  09  05

C-3  04  ..  ..  09  00 ---&gt; C-3  04  ..  ..  09  08

C-3  04  ..  ..  09  00 ---&gt; C-3  04  ..  ..  09  0A

C-3  04  ..  ..  09  00 ---&gt; C-3  04  ..  ..  09  0D

C-3  04  ..  ..  09  10 ---&gt; C-3  04  ..  ..  09  10

(You can also switch on the Slider Rec to On, and perform parameter-live-recording, such as cutoff transitions, resonance or panning tweaking, etc..)  Note: this command only works for volume/panning and fx datas columns.


The next command we'll look at is the Portamento up/down: 1 and 2. Command 1 slides the pitch up at a specified speed, and 2 slides it down. This command works in a similar way to the volume slide, in that it is dependent on the secondary tempo. Both these commands have a memory dependent on each other, if you set the slide to a speed of 3 with the 1 command, a 2 command with no parameters will use the speed of 3 from the 1 command, and vice versa.

Command 4 is Vibrato. Vibrato is basically rapid changes in pitch, just try it, and you'll see what I mean. Parameters are in the format of xy, where x is the speed of the slide, and y is the depth of the slide. One important point to remember is to keep your vibratos subtle and natural so a depth of 3 or less and a reasonably fast speed, around 8, is usually used. Setting the depth too high can make the part sound out of tune from the rest.
Following on from command 4 is command 6. This is the Vibrato and Volume Slide command, and it has a memory like command 5, which you already know how to use.

Command 7 is Tremolo. This is similar to vibrato. Rather than changing the pitch it slides the volume. The effect parameters are in exactly the same format.   vibrato effect (0x1dxy) x = speed y = depth (can't be used if arpeggio (0x1b) is turned on) 

&lt;pre&gt;
 C-7 00 .. .. 1B37 &lt;-  Turn Arpeggio effect on
  --- .. .. .. 0000
  --- .. .. .. 0000
  --- .. .. .. 0000
  --- .. .. .. 1B38 &lt;- Change datas
  --- .. .. .. 0000
  --- .. .. .. 0000
  --- .. .. .. 0000
  --- .. .. .. 1B00 &lt;- Turn it off
&lt;/pre&gt;

Command 9 is Sample Offset. This starts the playback of the sample from a different place than the start. The effect parameters specify the sample offset, but only very roughly. Say you have a sample which is 8765(Hex) bytes long, and you wanted it to play from position 4321(Hex). The effect parameter could only be as accurate as the 43 part, and it would ignore the 21.

Command B is the Playing List/Order Jump command. The parameters specify the position in the Playing List/Order to jump to. When used in conjunction with command D you can specify the position and the line to play from.

Command E is pretty complex, as it is used for a lot of different things, depending on what the first parameter is. Let's take a trip through each effect in order.
Command E0 controls the hardware filter on an Amiga, which, as a low pass filter, cuts off the highest frequencies being played back. There are very few players and trackers on other system that simulate this function, not that you should need to use it. The second parameter, if set to 1, turns on the filter. If set to 0, the filter gets turned off.

Commands E1/E2 are Fine Portamento Up/Down. Exactly the same functions as commands 1/2, except that they only slide the pitch by a very small amount. These commands have a memory the same as 1/2 as well.

Command E3 sets the Glissando control. If parameters are set to 1 then when using command 3, any sliding will only use the notes in between the original note and the note being slid to. This produces a somewhat jumpier slide than usual. The best way to understand is to try it out for yourself. Produce a slow slide with command 3, listen to it, and then try using E31.

Command E4 is the Set Vibrato Waveform control. This command controls how the vibrato command slides the pitch. Parameters are 0 - Sine, 1 - Ramp Down (Saw), 2 - Square. By adding 4 to the parameters, the waveform will not be restarted when a new note is played e.g. 5 - Sine without restart.

Command E5 sets the Fine Tune of the instrument being played, but only for the particular note being played. It will override the default Fine Tune for the instrument. The parameters range from 0 to F, with 0 being -8 and F being +8 Fine Tune. A parameter of 8 gives no Fine Tune. If you're using a newer tracker that supports more than -8 to +8 e.g. -128 to +128, these parameters will give a rough Fine Tune, accurate to the nearest 16.

Command E6 is the Jump Loop command. You mark the beginning of the part of a pattern that you want to loop with E60, and then specify with E6x the end of the loop, where x is the number of times you want it to loop.

Command E7 is the Set Tremolo Waveform control. This has exactly the same parameters as command E4, except that it works for Tremolo rather than Vibrato.

Command E9 is for Retriggering the note quickly. The parameter specifies the interval between the retrigs. Use a value of less than the current secondary tempo, or else the note will not get retrigged.

Command EA/B are for Fine Volume Slide Up/Down. Much the same as the normal Volume Slides, except that these are easier to control since they don't depend on the secondary tempo. The parameters specify the amount to slide by e.g. if you have a sample playing at a volume of 08 (Hex) then the effect EA1 will slide this volume to 09 (Hex). A subsequent effect of EB4 would slide this volume down to 05 (Hex).

Command EC is the Note Cut. This sets the volume of the currently playing note to 0 at a specified tick. The parameters should be lower than the secondary tempo or else the effect won't work.

Command ED is the Note Delay. This should be used at the same time as a note is to be played, and the parameters will specify the number of ticks to delay playing the note. Again, keep the parameters lower than the secondary tempo, or the note won't get played!

Command EE is the Pattern Delay. This delays the pattern for the amount of time it would take to play a certain number of rows. The parameters specify how many rows to delay for.

Command EF is the Funk Repeat command. Set the sample loop to 0-1000. When EFx is used, the loop will be moved to 1000- 2000, then to 2000-3000 etc. After 9000-10000 the loop is set back to 0- 1000. The speed of the loop &quot;movement&quot; is defined by x. E is two times as slow as F, D is three times as slow as F etc. EF0 will turn the Funk Repeat off and reset the loop (to 0-1000).

effects 0x41 and 0x42 to control the volumes of the 2 303 units

There is a dedicated panel for synth parameter editing with coherent sections (osc, filter modulation, routing, so on) the interface is much nicer, much better to navigate with customizable colors, the reverb is now customizable (10 delay lines), It accepts newer types of Waves (higher bit rates, at least 24). Has a replay routine.

It's pretty much your basic VA synth. The problem isn't with the sampler being to high it's the synth is tuned two octaves too low, but if you want your samples tuned down just set the base note down 2 octaves (in the instrument panel).

so the synth is basically divided into 3 sections from left to right: oscillators/envelopes, then filter and LFO's, and in the right column you have mod routings and global settings.

for the oscillator section you have two normal oscillators (sine, saw, square, noise), the second of which is tunable, the first one tunes with the key pressed. Attached to OSC 1 is a sub-oscillator, which is a sawtooth wave tuned one octave down. The phase modulation controls the point in the duty cycle at which the oscillator starts. The ADSR envelope sliders (grouped with oscs) are for modulation envelope 1 and 2 respectively. you can use the synth as a sampler by choosing the instrument at the top.

In the filter column, the filter settings are: 1 = lowpass, 2 = highpass, 3 = off. cutoff and resonance. For the LFOs they are LFO 1 and LFO 2, the ADSR sliders in those are for the LFO itself.

For the modulation routings you have ENV 1, LFO 1 for the first slider and ENV 2, LFO 2 for the second, you can cycle through the individual routings there, and you can route each modulation source to multiple destinations of course, which is another big plus for this synth. Finally the glide time is for portamento and master volume, well, the master volume... it can go quite loud.

The sequencer is changed too, It's more like the one in AXS if you've used that, where you can mute tracks to re-use patterns with variation.


&lt;pre&gt;
Support for the following modules formats:
669 (Composer 669, Unis 669), 
AMF (DSMI Advanced Module Format), 
AMF (ASYLUM Music Format V1.0), 
APUN (APlayer), DSM (DSIK internal format), 
FAR (Farandole Composer), 
GDM (General DigiMusic), 
IT (Impulse Tracker), 
IMF (Imago Orpheus), 
MOD (15 and 31 instruments), 
MED (OctaMED), 
MTM (MultiTracker Module editor), 
OKT (Amiga Oktalyzer), 
S3M (Scream Tracker 3), 
STM (Scream Tracker), 
STX (Scream Tracker Music Interface Kit), 
ULT (UltraTracker), 
UNI (MikMod), 
XM (FastTracker 2),
Mid (midi format via timidity)
&lt;/pre&gt;


Possible plugin options include [http://lv2plug.in/ LV2],


====Midi - Musical Instrument Digital Interface====

A midi file typically contains music that plays on up to 16 channels (as per the midi standard), but many notes can simultaneously play on each channel (depending on the limit of the midi hardware playing it).

'''Timidity'''

Although usually already installed, you can uncompress the [http://www.libsdl.org/projects/SDL_mixer/ timidity.tar.gz (14MB)] into a suitable drawer like below's SYS:Extras/Audio/ 
 assign timidity: SYS:Extras/Audio/timidity
added to SYSːs/User-Startup

'''WildMidi playback'''


'''Audio Evolution 4 (2003) 4.0.23 (from 2012)'''


*Sync Menu    - CAMD Receive, Send checked 
*Options Menu - MIDI Machine Control - Midi Bar Display - Select CAMD MIDI in / out - Midi Remote Setup 


MCB Master Control Bus 
*Sending a MIDI start-command and a Song Position Pointer, you can synchronize audio with an external MIDI sequencer (like B&amp;P). 
*B&amp;P Receive, start AE, add AudioEvolution.ptool in Bars&amp;Pipes track, press play / record in AE then press play in Pipes 
*CAMD Receive, receive MIDI start or continue commands via camd.library sync to AE 


*MIDI Machine Control
*Midi Bar Display 
*Select CAMD MIDI in / out
*Midi Remote Setup - open requester for external MIDI controllers to control app mixer and transport controls cc remotely 
 Channel   - mixer(vol, pan, mute, solo), eq, aux, fx, 
 Subgroup  - Volume, Mute, Solo 
 Transport - Start, End, Play, Stop, Record, Rewind, Forward 
 Misc      - Master vol., Bank Down, Bank up 


&lt;pre&gt;
q        - quit 

First 3 already opened when AE started 
F1       - timeline window
F2       - mixer 
F3       - control 
F4       - subgroups 
F5       - aux returns 
F6       - sample list 

i        - Load sample to use 

space    - start/stop play 
b        - reset time 0:00


s        - split mode 
r        - open recording window 
a        - automation edit mode with p panning, m mute and v volume 


[ / ]    - zoom in / out 
:        - previous track
*        - next track 

x c v f  - cut copy paste cross-fade 
g        - snap grid 


&lt;/pre&gt;


 '''[http://bnp.hansfaust.de/ Bars n Pipes sequencer]'''

 BarsnPipes debug ... in shell 

Menu (right mouse)  
*Song        - Songs load and save in .song format but option here to load/save Midi_Files .mid in FORMAT0 or FORMAT1 
*Track       - 
*Edit        -
*Tool        - 
*Timing      - SMTPE Synchronizing 
*Windows     - 
*Preferences - Multiple MIDI-in option 

Windows (some of these are usually already opened when Bars n Pipes starts up for the first time) 
*Workflow -&gt; Tracks, .... Song Construction, Time-line Scoring, Media Madness, Mix Maestro, 
*Control  -&gt; Transport (or mini one), Windows (which collects all the Windows icons together-shortcut), .... Toolbox, Accessories, Metronome, 

Once you have your windows placed on the screen that suits your workflow, Song -&gt; Save as Default will save the positions, colors, icons, etc as you'd like them 

If you need a particular setup of Tracks, Tools, Tempos etc, you save them all as a new song you can load each time 

Right mouse menu -&gt; Preferences -&gt; Environment... -&gt; ScreenMode  - Linkages for Synch (to Slave) usbmidi.out.0 and Send (Master) usbmidi.in.0 - Clock MTC 


'''Tracks'''

#Double-click on B&amp;P's icon. B&amp;P will then open with an empty Song. You can also double-click on a song icon to open a song in B&amp;P.
#Choose a track. The B&amp;P screen will contain a Tracks Window with a number of tracks shown as pipelines (Track 1, Track 2, etc...). To choose a track, simply click on the gray box to show an arrow-icon to highlight it. This icon show whether a track is chosen or not. To the right of the arrow-icon, you can see the icon for the midi-input. If you double-click on this icon you can change the MIDI-in setup.
#Choose Record for the track. To the right of the MIDI-input channel icon you can see a pipe. This leads to another clickable icon with that shows either P, R or M. This stands for Play, Record or Merge. To change the icon, simply click on it. If you choose P, this track can only play the track (you can't record anything). If you choose R, you can record what you play and it overwrites old stuff in the track. If you choose M, you merge new records with old stuff in the track. Choose R now to be able to make a record.
#Chose MIDI-channel. On the most right part of the track you can see an icon with a number in it. This is the MIDI-channel selector. Here you must choose a MIDI-channel that is available on your synthesizer/keyboard. If you choose General MIDI channel 10, most synthesizer will play drum sounds. To the left of this icon is the MIDI-output icon. Double-click on this icon to change the MIDI-output configuration.
#Start recording. The next step is to start recording. You must then find the control buttons (they look like buttons on a CD-player). To be able to make a record. you must click on the R icon. You can simply now press the play button (after you have pressed the R button) and play something on you keyboard. To playback your composition, press the Play button on the control panel.
#Edit track. To edit a track, you simply double click in the middle part of a track. You will then get a new window containing the track, where you can change what you have recorded using tools provided. Take also a look in the drop-down menus for more features.


Videos to help understand [https://www.youtube.com/watch?v=A6gVTX-9900 small intro], [https://www.youtube.com/watch?v=abq_rUTiSA4&amp;t=3s Overview], [https://www.youtube.com/watch?v=ixOVutKsYQo Workplace Setup CC PC Sysex], [https://www.youtube.com/watch?v=dDnJLYPaZTs Import Song], [https://www.youtube.com/watch?v=BC3kkzPLkv4 Tempo Mapping], [https://www.youtube.com/watch?v=sd23kqMYPDs ptool Arpeggi-8], [https://www.youtube.com/watch?v=LDJq-YxgwQg  PlayMidi Song], [https://www.youtube.com/watch?v=DY9Pu5P9TaU Amiga Midi], [https://www.youtube.com/watch?v=abq_rUTiSA4 Learning Amiga bars and Pipes], 

Groups like [https://groups.io/g/barsnpipes/topics this] could help 


'''Tracks window'''

* blue &quot;1 2 3 4 5 6 7 8 Group&quot; and transport tape deck VCR-type controls
* Flags 
* [http://theproblem.alco-rhythm.com/org/bp.html Track 1, Track2, to Track 16, on each Track there are many options that can be activated] 

Each Track has a 

*Left LHS  - Click in grey box to select what Track to work on, Midi-In ptool icon should be here (5pin plug icon), and many more from the Toolbox on the Input Pipeline 
*Middle    - (P, R, M) Play, Record, Merge/Multi before the sequencer line and a blue/red/yellow (Thru Mute Play) Tap 
*Right RHS - Output pipeline, can have icons placed uopn it with the final ptool icon(s) being the 5pin icon symbol for Midi-OUT 

Clogged pipelines may need Esc pressed several times 


'''Toolbox (tools affect the chosen pipeline)'''

After opening the Toolbox window you can add extra Tools (.ptool) for the pipelines like keyboard(virtual), midimonitor, quick patch, transpose, triad, (un)quantize, feedback in/out, velocity etc
 right mouse -&gt; Toolbox menu option -&gt; Install Tool... and navigate to Tool drawer (folder) and select requried .ptool 

Accompany B tool to get some sort of rythmic accompaniment, Rythm Section and Groove Quantize are examples of other tools that make use of rythms
[https://aminet.net/search?query=bars Bars &amp; Pipes pattern format .ptrn] for drawer (folder). Load from the Menu as Track or Group 


'''Accessories (affect the whole app)''' 

Accessories -&gt; Install... and goto the Accessories drawer for .paccess like adding ARexx scripting support 


'''Song Construction'''
&lt;pre&gt;
F1  Pencil
F2  Magic Wand
F3  Hand 
F4  Duplicator 
F5  Eraser 
F6  Toolpad 
F7  Bounding box 
F8  Lock to A-B-A 

A-B-A strip, section, edit flags, white boxes, 

&lt;/pre&gt;


Bars&amp;Pipes Professional offers three track formats; basic song tracks, linear tracks — which don't loop — and finally real‑time tracks. The difference between them is that both song and linear tracks respond to tempo changes, while real‑time tracks use absolute timing, always trigger at the same instant regardless of tempo alterations 

'''Tempo Map'''

F1  Pencil
F2  Magic Wand
F3  Hand 
F4  Eraser 
F5  Curve 
F6  Toolpad 


Compositions

Lyrics, Key, Rhythm, Time Signature 

'''Master Parameters'''

Key, Scale/Mode

'''Track Parameters'''

Dynamics 


'''Time-line Scoring'''


'''Media Madness'''


'''Mix Maestro'''


*ACCESSORIES         Allows the importation of other packages and additional modules 
*CLIPBOARD           Full cut, copy and paste operations, enabling user‑definable clips to be shared between tracks.
*INFORMATION         A complete rundown on the state of the current production and your machine.
*MASTER PARAMETERS   Enables global definition of time signatures, lyrics, scales, chords, dynamics and rhythm changes.
*MEDIA MADNESS       A complete multimedia sequencer which allows samples, stills, animation, etc 
*METRONOME           Tempo feedback via MIDI, internal Amiga audio and colour cycling — all three can be mixed and matched as required.
*MIX MAESTRO         Completely automated mixdown with control for both volume and pan. All fader alterations are memorised by the software 
*RECORD ACTIVATION   Complete specification of the data to be recorded/merged. Allows overdubbing of pitch‑bend, program changes, modulation etc
*SET FLAGS           Numeric positioning of location and edit flags in either SMPTE or musical time 
*SONG CONSTRUCTION   Large‑scale cut and paste of individual measures, verses or chorus, by means of bounding box and drag‑n‑drop mouse selections
*TEMPO MAP           Tempo change using a variety of linear and non‑linear transition curves 
*TEMPO PALETTE       Instant tempo changes courtesy of four user‑definable settings.
*TIMELINE SCORING    Sequencing of a selection of songs over a defined period — ideal for planning an entire set for a live performance.
*TOOLBOX             Selection screen for the hundreds of signal‑processing tools available 
*TRACKS              Opens the main track window to enable recording, editing and the use of tools.
*TRANSPORT           Main playback control window, which also provides access to user‑ defined flags, loop and punch‑in record modes.


Bars and Pipes Pro 2.5 is using internal 4-Byte IDs, to check which kind of data are currently processed.
Especially in all its files the IDs play an important role. The IDs are stored into the file in the same order they are laid out in the memory.

In a Bars 'N' Pipes file (no matter which kind) the ID &quot;NAME&quot; (saved as its ANSI-values) is stored on a big endian system (68k-computer) as &quot;NAME&quot;. On a little endian system (x86 PC computer) as &quot;EMAN&quot;.  The target is to make the AROS-BnP compatible to songs, which were stored on a 68k computer (AMIGA).

If possible, setting MIDI channels for Local Control for your keyboard 

http://www.fromwithin.com/liquidmidi/archive.shtml


MIDI files are essentially a stream of event data. An event can be many things, but typically &quot;note on&quot;, &quot;note off&quot;, &quot;program change&quot;, &quot;controller change&quot;, or messages that instruct a MIDI compatible synth how to play a given bit of music.

* Channel     - 1 to 16 -
* Messages    - PC presets, CC effects like delays, reverbs,  etc 
* Sequencing  - MIDI instruments, Drums, Sound design, 
* Recording   - 
* GUI         - Piano roll or Tracker, Staves and Notes 

MIDI events/messages like step entry e.g. Note On, Note Off 

MIDI events/messages like PB, PC, CC, Mono and Poly After-Touch, Sysex, etc 

MIDI sync - Midi Clocks (SPS Measures), Midi Time Code (h, m, s and frames) SMPTE 

Individual track editing with audition edits so easier to test any changes. Possible to stop track playback, mix clips from the right edit flag and scroll the display using arrow keys. 

Step entry, to extend a selected note hit the space bar and the note grows accordingly. Ability to cancel mouse‑driven edits by simply clicking the right mouse button — at which point everything snaps back into its original form. Lyrics can now be put in with syllable dividers, even across an entire measure or section. Autoranging when you open a edit window, the notes are automatically displayed — working from the lowest upwards. 

Flag editing, shift‑click on a flag immediately open the bounds window, ready for numeric input. Ability to cancel edits using the right‑hand mouse button, plus much improved Bounding Box operations.

Icons other than the BarsnPipes icon -&gt; PUBSCREEN=BarsnPipes (cannot choose modes higher than 8bit 256 colors)

Preferences -&gt; Menu in Tracks window - Send MIDI defaults OFF 

Prefs -&gt; Environment -&gt; screenmode (saved to BarsnPipes.prefs binary file) 

Customization -&gt; pics in gui drawer (folder) - 


Can save as .song files and .mid General Midi 

SMF is a “Standard Midi File”  ([http://www.music.mcgill.ca/~ich/classes/mumt306/StandardMIDIfileformat.html SMF0, SMF1 and SMF2]), [https://github.com/stump/libsmf libsmf], [https://github.com/markc/midicomp MIDIcomp], [https://github.com/MajicDesigns/MD_MIDIFile C++ src], [], [https://github.com/newdigate/midi-smf-reader Midi player], 

* SMF0        All MIDI data is stored in one track only, separated exclusively by the MIDI channel.
* SMF1        The MIDI data is stored in separate tracks/channels.
* SMF2 (rarely used) The MIDI data is stored in separate tracks, which are additionally wrapped in containers, so it's possible to have e.g. several tracks using the same MIDI channels.


Would it be possible to enrich Bars N’Pipes with software synth and sample support along with audio recording and mastering tools like in the named MAC or PC music sequencers?
On the classic AMIGA-OS this is not possible because of missing CPU-power. The hardware of the classic AMIGA is not further developed. So we must say (unfortunately) that those dreams can’t become reality

BarsnPipes is best used with external MIDI-equipment. This can be a keyboard or synthesizer with MIDI-connectors. 

&lt;pre&gt;
MIDI can control 16 channels 
There are USB-MIDI-Interfaces on the market with 16 independent MIDI-lines (multi-port), which can handle 16 MIDI devices independently – 16×16 = 256 independent MIDI-channels or instruments 
handle up to 16 different USB-MIDI-Interfaces (multi-device). That is: 16X16X16 = 4096 independent MIDI-channels – theoretically 
&lt;/pre&gt;

&lt;pre&gt;
Librarian MIDI SYStem EXplorer (sysex) - PatchEditor and used to be supplied as a separate program like PatchMeister but currently not at present 
It should support MIDI.library (PD), BlueRibbon.library (B&amp;P), TriplePlayPlus, and CAMD.library (DeluxeMusic) and 
MIDI information from a device's user manual and configure a custom interface to access parameters for all MIDI products connected to the system 
Supports ALL MIDI events and the Patch/Librarian data is stored in MIDI standard format 
Annette M.Crowling, Missing Link Software, Inc.
&lt;/pre&gt;


Composers
&lt;pre&gt;
[https://x.com/hirasawa/status/1403686519899054086 Susumu Hirasawa] 

&lt;/pre&gt;


&lt;pre&gt;
1988 Todor Fay and his wife Melissa Jordan Gray, who founded the Blue Ribbon Inc
1992 Bars&amp;Pipes Pro published 
November 2000, Todor Fay announcement to release the sourcecode of Bars&amp;Pipes Pro 2.5c beta
end of May 2001, the source of the main program and the sources of some tools and accessories were in a complete and compileable state 
end of October 2009 stop further development of BarsnPipes New for now on all supported systems and made freeware 
2013 Alfred Faust diagnosed with incureable illness, called „Myastenia gravis“ (weak muscles) 
&lt;/pre&gt;


 Protrekkr

How to use Midi In/Out in Protrekkr ?

First of all, midi in &amp; out capabilities of this program are rather limited.

# Go to Misc. Setup section and select a midi in or out device to use (ptk only supports one device at a time).
# Go to instrument section, and select a MIDI PRG (the default is N/A, which means no midi program selected).
# Go to track section and here you can assign a midi channel to each track of ptk.
# Play notes :]. Note off works. F'x' note cut command also works too, and note-volume command (speed) is supported.

Also, you can change midicontrollers in the tracker, using '90' in the panning row:

&lt;pre&gt;
    C-3 02 .. .. 0000....


    --- .. .. 90 xxyy.... &lt;&lt; This will set the value 
    --- .. .. .. 0000....    of the controller n.'xx' to 'yy' (both in hex)
    --- .. .. .. 0000....
&lt;/pre&gt;

So &quot;--- .. .. 90 2040....&quot; will set the controller number $20(32) to $40(64).

You will need the midi implementation table of your gear to know what you can change with midi controller messages.

 N.B. Not all MIDI devices are created equal!

Although the MIDI specification defines a large range of MIDI messages of various kinds, not every MIDI device is required to work in exactly the same way and respond to all the available messages and ways of working. For example, we don't expect a wind synthesiser to work in the same way as a home keyboard.

Some devices, the older ones perhaps, are only able to respond to a single channel. With some of those devices that channel can be altered from the default of 1 (probably) to another channel of the 16 possible.

Other devices, for instance monophonic synthesisers, are capable of producing just one note at a time, on one MIDI channel. Others can produce many notes spread across many channels.

Further devices can respond to, and transmit, &quot;breath controller&quot; data (MIDI controller number 2 (CC#2)) others may respond to the reception of CC#2 but not be able to create and to send it.

A controller keyboard may be capable of sending &quot;expression pedal&quot; data, but another device may not be capable of responding to that message.

Some devices just have the basic GM sound set. The &quot;voice&quot; or &quot;instrument&quot; is selected using a &quot;Program Change&quot; message on its own.

Other devices have a greater selection of voices, usually arranged in &quot;banks&quot;, and the choice of instrument is made by responding to &quot;Bank Select MSB&quot; (MIDI controller 0 (CC#0)), others use &quot;Bank Select LSB&quot; (MIDI controller number 32 (CC#32)), yet others use both MSB and LSB sent one after the other, all followed by the Program Change message. The detailed information about all the different voices will usually be available in a published MIDI Data List.


 MIDI Implementation Chart

But in the User Manual there is sometimes a summary of how the device works, in terms of MIDI, in the chart at the back of the manual, the MIDI Implementation Chart.

If you require two devices to work together you can compare the two implementation charts to see if they are &quot;compatible&quot;. In order to do this we will need to interpret that chart.

The chart is divided into four columns headed &quot;Function&quot;, &quot;Transmitted&quot; (or &quot;Tx&quot;), &quot;Received&quot; (or &quot;Rx&quot;), or more correctly &quot;Recognised&quot;, and finally, &quot;Remarks&quot;.

&lt;pre&gt;
The left hand column defines which MIDI functions are being described.
The 2nd column defines what the device in question is capable of transmitting to another device.
The 3rd column defines what the device is capable of responding to.
The 4th column is for explanations of the values contained within these previous two columns.
&lt;/pre&gt;

There should then be twelve sections, with possibly a thirteenth containing extra &quot;Notes&quot;. Finally there should be an explanation of the four MIDI &quot;modes&quot; and what the &quot;X&quot; and the &quot;O&quot; mean.
&lt;pre&gt;
Mode 1: Omni On, Poly; 
Mode 2: Omni On, Mono; 
Mode 3: Omni Off, Poly; 
Mode 4: Omni Off, Mono.
&lt;/pre&gt;
O means &quot;yes&quot; (implemented), X means &quot;no&quot; (not implemented).

Sometimes you will find a row of asterisks &quot;**************&quot;, these seem to indicate that the data is not applicable in this case. Seen in the transmitted field only (unless you've seen otherwise).

Lastly you may find against some entries an asterisk followed by a number e.g. *1, these will refer you to further information, often on a following page, giving more detail.

Basic Channel
But the very first set of boxes will tell us the &quot;Basic Channel(s)&quot; that the device sends or receives on. 
&quot;Default&quot; is what happens when the device is first turned on, &quot;changed&quot; is what a switch of some kind may allow the device to be set to. 
For many devices e.g. a GM sound module or a home keyboard, this would be 1-16 for both. That is it can handle sending and receiving on all MIDI channels.

On other devices, for example a synthesiser, it may by default only work on channel 1. But the keyboard could be &quot;split&quot; with the lower notes e.g. on channel 2. If the synth has an arppegiator, this may be able to be set to transmit and or receive on yet another channel.
So we might see the default as &quot;1&quot; but the changed as &quot;1-16&quot;.

Modes.
We need to understand Omni On and Off, and Mono and Poly, then we can decipher the four modes.

But first we need to understand that any of these four Mode messages can be sent to any MIDI channel. They don't necessarily apply to the whole device.

If we send an &quot;Omni On&quot; message (CC#125) to a MIDI channel of a device, we are, in effect, asking it to respond to e.g. a Note On / Off message pair, received on any of the sixteen channels. Sound strange? Read it again. Still strange? It certainly is. We normally want a MIDI channel to respond only to Note On / Off messages sent on that channel, not any other. In other words, &quot;Omni Off&quot;.

So &quot;Omni Off&quot; (CC#124) tells a channel of our MIDI device to respond only to messages sent on that MIDI channel.

&quot;Poly&quot; (CC#127) is for e.g. a channel of a polyphonic sound module, or a home keyboard, to be able to respond to many simultaneous Note On / Off message pairs at once and produce musical chords.

&quot;Mono&quot; (CC#126) allows us to set a channel to respond as if it were e.g. a flute or a trumpet, playing just one note at a time. If the device is capable of it, then the overlapping of notes will produce legato playing, that is the attack portion of the second note of two overlapping notes will be removed resulting in a &quot;smoother&quot; transition.

So a channel with a piano voice assigned to it will have Omni Off, Poly On (Mode 3), a channel with a saxophone voice assigned could be Omni Off, Mono On (Mode 4).

We call these combinations the four modes, 1 to 4, as defined above. 
Most modern devices will have their channels set to Mode 3 (Omni Off, Poly) but be switchable, on a per channel basis, to Mode 4 (Omni Off, Mono).

This second section of data will include first its default value i.e. upon device switch on. Then what Mode messages are acceptable, or X if none.

Finally, in the &quot;Altered&quot; field, how a Mode message that can't be implemented will be interpreted. Usually there will just be a row of asterisks effectively meaning nothing will be done if you try to switch to an unimplemented mode.

Note Number
&lt;pre&gt;
The next row will tell us which MIDI notes the device can send or receive, normally 0-127.
The second line, &quot;True Voice&quot; has the following in the MIDI specification: 
&quot;Range of received note numbers falling within the range of true notes produced by the instrument.&quot;
My interpretation is that, for instance, a MIDI piano may be capable of sending all MIDI notes (0 to 127) by transposition, but only responding to the 88 notes (21 to 108) of a real piano. 
&lt;/pre&gt;

Velocity
This will tell us whether the device we're looking at will handle note velocity, and what range from 1-127, or maybe just 64, it transmits or will recognise. So usually &quot;O&quot; plus a range or &quot;X&quot; for not implemented.

After touch
This may have one or two lines two it.
If a one liner the either &quot;O&quot; or &quot;X&quot;, yes or no.
If a two liner then it may include &quot;Keys&quot; or &quot;Poly&quot; and &quot;Channel&quot;.
This will show whether the device will respond to Polyphonic after touch or channel after touch or neither.

Pitch Bend
Again &quot;O&quot; for implemented, &quot;X&quot; for not implemented.
(Many stage pianos will have no pitch bend capability.)
It may also, in the notes section, state whether it will respond to the full 14 bits, or not, as usually encoded by the pitch bend wheel.

Control Change
This is likely to be the largest section of the chart.
It will list all those controllers, starting from CC#0, Bank Select MSB, which the device is capable of sending, and those that it will respond to using &quot;O&quot; or &quot;X&quot; respectively.
You will, almost certainly, get some further explanation of functionality in the remarks column, or in more detail elsewhere in the documentation.

Of course you will need to know what all the various controller numbers do. Lots of the official technical specifications can be found at the [www.midi.org/techspecs/ MMA], with the table of messages and control change [www.midi.org/techspecs/midimessages.php message numbers]

Program Change
Again &quot;O&quot; or &quot;X&quot; in the Transmitted or Recognised column to indicate whether or not the feature is implemented. In addition a range of numbers is shown, typically 0-127, to show what is available.
True # (number): &quot;The range of the program change numbers which correspond to the actual number of patches selected.&quot;

System Exclusive
Used to indicate whether or not the device can send or recognise System Exclusive messages. A short description is often given in the Remarks field followed by a detailed explanation elsewhere in the documentation.

System Common - These include the following:
&lt;pre&gt;
MIDI Time Code Quarter Frame messages (device synchronisation).
Song Position Pointer
Song Select
Tune Request
&lt;/pre&gt;
The section will indicate whether or not the device can send or respond to any of these messages.

System Real Time
These include the following:
&lt;pre&gt;
Timing Clock - often just written as &quot;Clock&quot;
Start
Stop
Continue
&lt;/pre&gt;
These three are usually just referred to as &quot;Commands&quot; and listed.
Again the section will indicate which, if any, of these messages the device can send or respond to.
&lt;pre&gt;
Aux. Messages
Again &quot;O&quot; or &quot;X&quot; for implemented or not.
Aux. = Auxiliary.
Active Sense = Active Sensing.
&lt;/pre&gt;
Often with an explanation of the action of the device.

Notes
The &quot;Notes&quot; section can contain any additional comments to clarify the particular implementation.

Some of the explanations have been drawn directly from the MMA MIDI 1.0 Detailed Specification.
And the detailed explanation of some of the functions will be found there, or in the General MIDI System Level 1 or General MIDI System Level 2 documents also published by the MMA.


 OFFICIAL MIDI SPECIFICATIONS

SUMMARY OF MIDI MESSAGES
Table 1 - Summary of MIDI Messages

The following table lists the major MIDI messages in numerical (binary) order (adapted from &quot;MIDI by the Numbers&quot; by D. Valenti, Electronic Musician 2/88, and updated by the MIDI Manufacturers Association.). This table is intended as an overview of MIDI, and is by no means complete.

WARNING! Details about implementing these messages can dramatically impact compatibility with other products. We strongly recommend consulting the official MIDI Specifications for additional information.

MIDI 1.0 Specification

Message Summary Channel Voice Messages [nnnn = 0-15 (MIDI Channel Number 1-16)]

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;10%&quot;  |Status D7----D0 
! width=&quot;10%&quot;  |Data Byte(s) D7----D0 
! width=&quot;20%&quot;  |Description
|-
|&lt;!--Status--&gt;1000nnnn || &lt;!--Data--&gt;0kkkkkkk 0vvvvvvv || &lt;!--Description--&gt;Note Off event. 
This message is sent when a note is released (ended). (kkkkkkk) is the key (note) number. (vvvvvvv) is the velocity.
|-
|&lt;!--Status--&gt;1001nnnn || &lt;!--Data--&gt;0kkkkkkk 0vvvvvvv || &lt;!--Description--&gt;Note On event. 
This message is sent when a note is depressed (start). (kkkkkkk) is the key (note) number. (vvvvvvv) is the velocity.
|-
|&lt;!--Status--&gt;1010nnnn || &lt;!--Data--&gt;0kkkkkkk 0vvvvvvv || &lt;!--Description--&gt;Polyphonic Key Pressure (Aftertouch). 
This message is most often sent by pressing down on the key after it &quot;bottoms out&quot;. (kkkkkkk) is the key (note) number. (vvvvvvv) is the pressure value.
|-
|&lt;!--Status--&gt;1011nnnn || &lt;!--Data--&gt;0ccccccc 0vvvvvvv || &lt;!--Description--&gt;Control Change. 
This message is sent when a controller value changes. Controllers include devices such as pedals and levers. Controller numbers 120-127 are reserved as &quot;Channel Mode Messages&quot; (below). (ccccccc) is the controller number (0-119). (vvvvvvv) is the controller value (0-127).
|-
|&lt;!--Status--&gt;1100nnnn || &lt;!--Data--&gt;0ppppppp || &lt;!--Description--&gt;Program Change. This message sent when the patch number changes. (ppppppp) is the new program number.
|-
|&lt;!--Status--&gt;1101nnnn || &lt;!--Data--&gt;0vvvvvvv || &lt;!--Description--&gt;Channel Pressure (After-touch). This message is most often sent by pressing down on the key after it &quot;bottoms out&quot;. This message is different from polyphonic after-touch. Use this message to send the single greatest pressure value (of all the current depressed keys). (vvvvvvv) is the pressure value.
|-
|&lt;!--Status--&gt;1110nnnn || &lt;!--Data--&gt;0lllllll 0mmmmmmm || &lt;!--Description--&gt;Pitch Bend Change. This message is sent to indicate a change in the pitch bender (wheel or lever, typically). The pitch bender is measured by a fourteen bit value. Center (no pitch change) is 2000H. Sensitivity is a function of the receiver, but may be set using RPN 0. (lllllll) are the least significant 7 bits. (mmmmmmm) are the most significant 7 bits.
|}

Channel Mode Messages (See also Control Change, above)

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;10%&quot;  |Status D7----D0 
! width=&quot;10%&quot;  |Data Byte(s) D7----D0 
! width=&quot;20%&quot;  |Description
|-
|&lt;!--Status--&gt;1011nnnn || &lt;!--Data--&gt;0ccccccc 0vvvvvvv || &lt;!--Description--&gt;Channel Mode Messages. 
This the same code as the Control Change (above), but implements Mode control and special message by using reserved controller numbers 120-127. The commands are:
*All Sound Off. When All Sound Off is received all oscillators will turn off, and their volume envelopes are set to zero as soon as possible c = 120, v = 0: All Sound Off
*Reset All Controllers. When Reset All Controllers is received, all controller values are reset to their default values. (See specific Recommended Practices for defaults) c = 121, v = x: Value must only be zero unless otherwise allowed in a specific Recommended Practice.
*Local Control. When Local Control is Off, all devices on a given channel will respond only to data received over MIDI. Played data, etc. will be ignored. Local Control On restores the functions of the normal controllers. 
c = 122, v = 0: Local Control Off
c = 122, v = 127: Local Control On
* All Notes Off. When an All Notes Off is received, all oscillators will turn off. 
c = 123, v = 0: All Notes Off (See text for description of actual mode commands.)
c = 124, v = 0: Omni Mode Off 
c = 125, v = 0: Omni Mode On 
c = 126, v = M: Mono Mode On (Poly Off) where M is the number of channels (Omni Off) or 0 (Omni On) 
c = 127, v = 0: Poly Mode On (Mono Off) (Note: These four messages also cause All Notes Off)
|}

System Common Messages

System Messages (0xF0)

The final status nybble is a “catch all” for data that doesn’t fit the other statuses. They all use the most significant nybble (4bits) of 0xF, with the least significant nybble indicating the specific category.

The messages are denoted when the MSB of the second nybble is 1. When that bit is a 0, the messages fall into two other subcategories.

System Common

If the MSB of the second second nybble (4 bits) is not set, this indicates a System Common message. Most of these are messages that include some additional data bytes.

System Common Messages
Type Status Byte   Number of Data Bytes      Usage 
&lt;pre&gt;
Time Code Quarter Frame	0xF1	1	Indicates timing using absolute time code, primarily for synthronization with video playback systems. A single location requires eight messages to send the location in an encoded hours:minutes:seconds:frames format*.
Song Position	0xF2	2	Instructs a sequencer to jump to a new position in the song. The data bytes form a 14-bit value that expresses the location as the number of sixteenth notes from the start of the song.
Song Select	0xF3	1	Instructs a sequencer to select a new song. The data byte indicates the song.
Undefined	0xF4	0	
Undefined	0xF5	0	
Tune Request	0xF6	0	Requests that the receiver retunes itself**.
&lt;/pre&gt;
*MIDI Time Code (MTC) is significantly complex. Please see the MIDI Specification
**While modern digital instruments are good at staying in tune, older analog synthesizers were prone to tuning drift. Some analog synthesizers had an automatic tuning operation that could be initiated with this command.


System Exclusive

If you’ve been keeping track, you’ll notice there are two status bytes not yet defined: 0xf0 and 0xf7. These are used by the System Exclusive message, often abbreviated at SysEx. SysEx provides a path to send arbitrary data over a MIDI connection. There is a group of predefined messages for complex data, like fine grained control of MIDI Time code machinery. SysEx is also used to send manufacturer defined data, such as patches, or even firmware updates.

System Exclusive messages are longer than other MIDI messages, and can be any length. The messages are of the following format:

0xF0, 0xID, 0xdd, ...... 0xF7
The message is bookended with distinct bytes.

It opens with the Start Of Exclusive (SOX) data byte, 0xF0.
The next one to three bytes after the start are an identifier.
Values from 0x01 to 0x7C are one-byte vendor IDs, assigned to manufacturers who were involved with MIDI at the beginning.
If the ID is 0x00, it’s a three-byte vendor ID - the next two bytes of the message are the value.
&lt;pre&gt;
ID 0x7D is a placeholder for non-commercial entities.
ID 0x7E indicates a predefined Non-realtime SysEx message.
ID 0x7F indicates a predefined Realtime SysEx message.
&lt;/pre&gt;
After the ID is the data payload, sent as a stream of bytes.
The transfer concludes with the End of Exclusive (EOX) byte, 0xF7.
The payload data must follow the guidelines for MIDI data bytes – the MSB must not be set, so only 7 bits per byte are actually usable. If the MSB is set, it falls into three possible scenarios.

An End of Exclusive byte marks the ordinary termination of the SysEx transfer.
System Real Time messages may occur within the transfer without interrupting it. The recipient should handle them independently of the SysEx transfer.
Other status bytes implicitly terminate the SysEx transfer and signal the start of new messages.
 Some inexpensive USB-to-MIDI interfaces aren’t capable of handling messages longer than four bytes.

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;10%&quot;  |Status D7----D0 
! width=&quot;10%&quot;  |Data Byte(s) D7----D0 
! width=&quot;20%&quot;  |Description
|-
|&lt;!--Status--&gt;11110000 || &lt;!--Data--&gt;0iiiiiii [0iiiiiii 0iiiiiii]  0ddddddd  --- --- 0ddddddd 11110111 || &lt;!--Description--&gt;System Exclusive. 
This message type allows manufacturers to create their own messages (such as bulk dumps, patch parameters, and other non-spec data) and provides a mechanism for creating additional MIDI Specification messages. The Manufacturer's ID code (assigned by MMA or AMEI) is either 1 byte (0iiiiiii) or 3 bytes (0iiiiiii 0iiiiiii 0iiiiiii). Two of the 1 Byte IDs are reserved for extensions called Universal Exclusive Messages, which are not manufacturer-specific. If a device recognizes the ID code as its own (or as a supported Universal message) it will listen to the rest of the message (0ddddddd). Otherwise, the message will be ignored. (Note: Only Real-Time messages may be interleaved with a System Exclusive.)
|-
|&lt;!--Status--&gt;11110001 || &lt;!--Data--&gt;0nnndddd || &lt;!--Description--&gt;MIDI Time Code Quarter Frame.
nnn = Message Type
dddd = Values
|-
|&lt;!--Status--&gt;11110010 || &lt;!--Data--&gt;0lllllll 0mmmmmmm || &lt;!--Description--&gt;Song Position Pointer. 
This is an internal 14 bit register that holds the number of MIDI beats (1 beat= six MIDI clocks) since the start of the song. l is the LSB, m the MSB.
|-
|&lt;!--Status--&gt;11110011 || &lt;!--Data--&gt;0sssssss || &lt;!--Description--&gt;Song Select. 
The Song Select specifies which sequence or song is to be played.
|-
|&lt;!--Status--&gt;11110100 || &lt;!--Data--&gt; || &lt;!--Description--&gt;Undefined. (Reserved)
|-
|&lt;!--Status--&gt;11110101 || &lt;!--Data--&gt; || &lt;!--Description--&gt;Undefined. (Reserved)
|-
|&lt;!--Status--&gt;11110110 || &lt;!--Data--&gt; || &lt;!--Description--&gt;Tune Request. Upon receiving a Tune Request, all analog synthesizers should tune their oscillators.
|-
|&lt;!--Status--&gt;11110111 || &lt;!--Data--&gt; || &lt;!--Description--&gt;End of Exclusive. Used to terminate a System Exclusive dump. 
|}


System Real-Time Messages

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;10%&quot;  |Status D7----D0 
! width=&quot;10%&quot;  |Data Byte(s) D7----D0 
! width=&quot;20%&quot;  |Description
|-
|&lt;!--Status--&gt;11111000 || &lt;!--Data--&gt; || &lt;!--Description--&gt;Timing Clock. Sent 24 times per quarter note when synchronization is required.
|-
|&lt;!--Status--&gt;11111001 || &lt;!--Data--&gt; || &lt;!--Description--&gt;Undefined. (Reserved)
|-
|&lt;!--Status--&gt;11111010 || &lt;!--Data--&gt; || &lt;!--Description--&gt;Start. Start the current sequence playing. (This message will be followed with Timing Clocks).
|-
|&lt;!--Status--&gt;11111011 || &lt;!--Data--&gt; || &lt;!--Description--&gt;Continue. Continue at the point the sequence was Stopped.
|-
|&lt;!--Status--&gt;11111100 || &lt;!--Data--&gt; || &lt;!--Description--&gt;Stop. Stop the current sequence.
|-
|&lt;!--Status--&gt;11111101 || &lt;!--Data--&gt; || &lt;!--Description--&gt;Undefined. (Reserved)
|-
|&lt;!--Status--&gt;11111110 || &lt;!--Data--&gt; || &lt;!--Description--&gt;Active Sensing. This message is intended to be sent repeatedly to tell the receiver that a connection is alive. Use of this message is optional. When initially received, the receiver will expect to receive another Active Sensing message each 300ms (max), and if it does not then it will assume that the connection has been terminated. At termination, the receiver will turn off all voices and return to normal (non- active sensing) operation. 
|-
|&lt;!--Status--&gt;11111111 || &lt;!--Data--&gt; || &lt;!--Description--&gt;Reset. Reset all receivers in the system to power-up status. This should be used sparingly, preferably under manual control. In particular, it should not be sent on power-up.
|}


Advanced Messages

Polyphonic Pressure (0xA0) and Channel Pressure (0xD0)

Some MIDI controllers include a feature known as Aftertouch. While a key is being held down, the player can press harder on the key. The controller measures this, and converts it into MIDI messages.

Aftertouch comes in two flavors, with two different status messages.

The first flavor is polyphonic aftertouch, where every key on the controller is capable of sending its own independent pressure information. The messages are of the following format:
&lt;pre&gt;
0xnc, 0xkk, 0xpp
n is the status (0xA)
c is the channel nybble
kk is the key number (0 to 127)
pp is the pressure value (0 to 127)
&lt;/pre&gt;
Polyphonic aftertouch is an uncommon feature, usually found on premium quality instruments, because every key requires a separate pressure sensor, plus the circuitry to read them all.

Much more commonly found is channel aftertouch. Instead of needing a discrete sensor per key, it uses a single, larger sensor to measure pressure on all of the keys as a group. The messages omit the key number, leaving a two-byte format
&lt;pre&gt;
0xnc, 0xpp
n is the status (0xD)
c is the channel number
pp is the pressure value (0 to 127)
&lt;/pre&gt;

Pitch Bend (0xE0)

Many keyboards have a wheel or lever towards the left of the keys for pitch bend control. This control is usually spring-loaded, so it snaps back to the center of its range when released. This allows for both upward and downward bends.

Pitch Bend Wheel

The wheel sends pitch bend messages, of the format
&lt;pre&gt;
0xnc, 0xLL, 0xMM
n is the status (0xE)
c is the channel number
LL is the 7 least-significant bits of the value
MM is the 7 most-significant bits of the value
&lt;/pre&gt;
You’ll notice that the bender data is actually 14 bits long, transmitted as two 7-bit data bytes. This means that the recipient needs to reassemble those bytes using binary manipulation. 14 bits results in an overall range of 214, or 0 to 16,383. Because it defaults to the center of the range, the default value for the bender is halfway through that range, at 8192 (0x2000).

Control Change (0xB0)

In addition to pitch bend, MIDI has provisions for a wider range of expressive controls, sometimes known as continuous controllers, often abbreviated CC. These are transmitted by the remaining knobs and sliders on the keyboard controller shown below.


Continuous Controllers

These controls send the following message format:
&lt;pre&gt;
0xnc, 0xcc, 0xvv
n is the status (0xB)
c is the MIDI channel
cc is the controller number (0-127)
vv is the controller value (0-127)
&lt;/pre&gt;

Typically, the wheel next to the bender sends controller number one, assigned to modulation (or vibrato) depth. It is implemented by most instruments.

The remaining controller number assignments are another point of confusion. The MIDI specification was revised in version 2.0 to assign uses for many of the controllers. However, this implementation is not universal, and there are ranges of unassigned controllers.

On many modern MIDI devices, the controllers are assignable. On the controller keyboard shown in the photos, the various controls can be configured to transmit different controller numbers. Controller numbers can be mapped to particular parameters. Virtual synthesizers frequently allow the user to assign CCs to the on-screen controls. This is very flexible, but it might require configuration on both ends of the link and completely bypasses the assignments in the standard.


Program Change (0xC0)

Most synthesizers have patch storage memory, and can be told to change patches using the following command:
&lt;pre&gt;
0xnc, 0xpp
n is the status (0xc)
c is the channel
pp is the patch number (0-127)
&lt;/pre&gt;
This allows for 128 sounds to be selected, but modern instruments contain many more than 128 patches. Controller #0 is used as an additional layer of addressing, interpreted as a “bank select” command. Selecting a sound on such an instrument might involve two messages: a bank select controller message, then a program change.

Audio &amp; Midi are not synchronized, what I can do ?
Buy a commercial software package but there is a nasty trick to synchronize both. It's a bit hardcore but works for me:

 Simply put one line down to all midi notes on your pattern (use Insert key)
 and go to 'Misc. Setup', adjust the latency and just search a value
 that will make sound sync both audio/midi.

The stock Sin/Saw/Pulse and Rnd waveforms are too simple/common, is there a way to use something more complex/rich ?
You have to ability to redirect the waveforms of the instruments through the synth pipe by selecting the &quot;wav&quot; option for the oscillator you're using for this synth instrument, samples can be used as wavetables to replace the stock signals.


Sound banks like soundfont (sf2) or Kontakt2 are not supported at the moment


====DAW Audio Evolution 4====

Audio Evolution 4 gives you unsurpassed power for digital audio recording and editing on the Amiga. The latest release focusses on time-saving non-linear and non-destructive editing, as seen on other platforms. Besides editing, Audio Evolution 4 offers a wide range of realtime effects, including compression, noise gate, delays, reverb, chorus and 3-band EQ.

Whether you put them as inserts on a channel or use them as auxillaries, the effect parameters are realtime adjustable and can be fully automated. Together with all other mixing parameters, they can even be controlled remotely, using more ergonomic MIDI hardware.

Non-linear editing on the time line, including cut, copy, paste, move, split, trim and crossfade actions

The number of tracks per project(s) is unlimited .... AHI limits you to recording only two at a time. i.e. not on 8 track sound cards like the Juli@ or Phase 88.

sample file import is limited to 16bit AIFF (not AIFC, important distinction as some files from other sources can be AIFC with aiff file extention). and 16bit WAV (pcm only)


Most apps use the Music Unit only but a few apps also use Unit (0-3) instead or as well. 
* Set up AHI prefs so that microphone is available. (Input option near the bottom)


stereo++ allows the audio piece to be placed anywhere and the left-right adjusted to sound positionally right

hifi best for music playback if driver supports this option


Load 16bit .aif .aiff only sample(s) to use not AIFC which can have the same ending. AIFF stands for Audio Interchange File Format 

 sox recital.wav recital.aiff

 sox recital.wav −b 16 recital.aiff channels 1 rate 16k fade 3 norm
 sox input.wav        output.aiff bass −b 16 rate 48k

performs the same format translation, but also applies four effects (down-mix to one channel, sample rate change, fade-in, nomalize), and stores the result at a bit-depth of 16.

 rec −c 2 radio.aiff trim 0 30:00

records half an hour of stereo audio 

 play existing-file.wav


24bit PCM WAV or AIFF do not work 

*No stream format handling. So no way to pass on an AC3 encoded stream unmodified to the digital outputs through AHI.
*No master volume handling. Each application has to set its own volume. So each driver implements its own custom driver-mixer interface for handling master volumes, mute and preamps.
*Only one output stream. So all input gets mixed into one output.
*No automatic handling of output direction based on connected cables.
*No monitor input selection. Only monitor volume control. 


select the correct input (Don't mistake enabled sound for the correct input.)
The monitor will feedback audio to the lineout and hp out no matter if you have selected the correct input to the ADC. The monitor will provide sound for any valid input. This will result in free mixing when recording from the monitor input instead of mic/line because the monitor itself will provide the hardware mixing for you. Be aware that MIC inputs will give two channel mono. Only Linein will give real stereo.

Now for the not working part. Attempt to record from linein in the AE4 record window, the right channel is noise and the left channel is distorted. Even with the recommended HIFI 16bit Stereo++ mode at 48kHz.


Channels

Monitor

Gain

Inout

Output

Advanced settings - Debugging via serial port


* Options -&gt; Soundcard In/Out
* Options -&gt; SampleRate
* Options -&gt; Preferences

F6 for Sample File List

Setting a grid is easy as is measuring the BPM by marking a section of the sample. Is your kick drum track &quot;not in time&quot; ? If so, you're stumped in AE4 as it has no fancy variable time signatures and definitely no 'track this dodgy rhythm' function like software of the nature of Logic has. So if your drum beat is freeform you will need to work in freeform mode. (Real music is free form anyway).

If the drum *is* accurate and you are just having trouble measuring the time, I usually measure over a range of bars and set the number of beats in range to say 16 as this is more accurate, Then you will need to shift the drum track to match your grid *before* applying the grid. (probably an iterative process as when the grid is active samples snap to it, and when inactive you cannot see it).

AE4 does have ARexx but the functions are more for adding samples at set offsets and starting playback / recording.


These are the usual features found in DAWs...

* Recording digital audio, midi sequencer and mixer 
* virtual VST instruments and plug-ins 
* automation, group channels, MIDI channels, FX sends and returns, audio and MIDI editors and music notation editor


* different track views 
* mixer and track layout (but not the same as below) 
* traditional two windows (track and mixer)


Mixing - mixdown

Could not figure out how to select what part I wanted to send to the aux, set it to echo and return. Pretty much the whole echo effect. Or any effect.

Take look at page17 of the manual.

When you open the EQ / Aux send popup window you will see 4 sends. Now from the menu choose the windows menu.

Menus-&gt;Windows-&gt; Aux Returns Window

or press F5

You will see a small window with 4 volume controls and an effects button for each. Click a button and add an effects to that aux channel, then set it up as desired (note the reverb effect has a special AUX setting that improves its use with the aux channel, not compulsory but highly useful). You set the amount of 'return' on the main mix in the Aux Return window, and the amount sent from each main mixer channel in the popup for that channel. Again the aux sends are &quot;prefade&quot; so the volume faders on each channel do not affect them.


Tracking


Effects - fade in

To add some echoes to some vocals, tried to add an effect on a track but did not come out. This is made more complicated as I wanted to mute a vocal but then make it echo at the muting point. Want to have one word of a vocal heard and then echoed off. But when the track is mute the echo is cancelled out.

To correctly understand what is happening here you need to study the figure at the bottom of page 15 on the manual. You will see from that that the effects are applied 'prefade' So the automation you applied will naturally mute the entire signal.

There would be a number of ways to achieve the goal,

You have three real time effects slots, one for smoothing like so

Sample -&gt; Amplify -&gt; Delay

Then automate the gain of the amplify block so that it effectively mutes the sample just before the delay at the appropriate moment, the echo effect should then be heard.

Getting the effects in the right order will require experimentation as they can only be added top down and it's not obvious which order they are applied to the signal, but there only two possibilities, so it wont take long to find out.

Using MUTE can cause clicks to the Amplify can be used to mute more smoothly so that's a secondary advantage.

Signal Processing -


Overdub

[[#top|...to the top]]

===Office===

====Spreadsheet Leu====

Support for some xlsx, and ods functions 


====Spreadsheet Ignition====

; Needs ABIv1 to be completed before more can be done

File formats supported 
* ascii #?.txt and #?.csv (single sheets with data only). 
* igs and TurboCalc(WIP) #?.tc for all sheets with data, formats and formulas.

There is '''no''' support for xls, xlsx, ods or uos ([http://en.wikipedia.org/wiki/Uniform_Office_Format Uniform Unified Office Format]) at the moment.

* Always use Esc key after editing Spreadsheet cells.
* copy/paste seems to copy the first instance only so go to Edit -&gt; Clipboard to manage the list of remembered actions. 
* Right mouse click on row (1 or 2 or 3) or column header (a or b or c)  to access optimal height or width of the row or column respectively 
* Edit -&gt; Insert -&gt; Row  seems to clear the spreadsheet or clears the rows after the inserted row until undo restores as it should be...

Change Sheet name by  Object -&gt; Sheet -&gt; Properties

Click in the cell which will contain the result, and click '''down arrow button''' to the right of the formula box at the bottom of the spreadsheet and choose the function required from the list provided. Then click on the start cell and click on the bottom right corner, a '''very''' small blob, which allows stretching a bounding box (thick grey outlines) across many cells This grey bounding box can be used to '''copy a formula''' to other cells.

Object -&gt; Cell -&gt; Properties to change cell format - Currency only covers DM and not $, Euro, Renminbi, Yen or Pound etc. 
Shift key and arrow keys selects a range of cells, so that '''formatting can be done to all highlighted cells'''. 
View -&gt; Overview then select ALL with one click (in empty cell in the top left hand corner of the sheet).

Default mode is relative cell referencing e.g. a1+a2 but absolute e.g. $a$1+$a$2 can be entered.

* #sheet-name to '''absolute''' reference another sheet-name cell unless reference() function used.

;Graphs

use shift key and arrow keys to select a bunch of cells to be graph'ed making sure that x axes represents and y axes represents

* value() - 0 value, 1 percent, 2 date, 3 time, 4 unit ...


;Dates 
* Excel starts a running count from the 1st Jan 1900 and Ignition starts from 1st Jan 1AD '''(maybe this needs to change)'''
Set formatting Object -&gt; Cell -&gt; Properties and put date in days


;Time 
Set formatting Object -&gt; Cell -&gt; Properties and put time in seconds taken


;Database (to be done by someone else)

type - standard, reference (bezug), search criterion (suchkriterium), 
* select a bunch of cells and Object -&gt; Database -&gt; Define to set Datenbank (database) and Felder (fields not sure how?) 
* Neu (new) or loschen (delete) to add/remove database headings e.g. Personal, Start Date, Finish Date (one per row?)
* Object -&gt; Database -&gt; Index to add fields (felder) like Surname, First Name, Employee ID, etc. to ?

Filtering done with dbfilter(), dbproduct() and dbposition().

Activities with dbsum(), dbaverage(), dbmin() and dbmax().

Table sorting -


;Scripts (Arexx)

;Excel(TM) to Ignition - commas ''',''' replaced by semi-colons ''';''' to separate values within functions 
*SUM(), 
*AVERAGE(), MAX(), MIN(), INT(), PRODUCT(), MEDIAN(), VAR() becomes Variance(), Percentile(),
*IF(), AND, OR, NOT 
*LEFT(), RIGHT(), MID() becomes MIDDLE(), LEN() becomes LENGTH(), 
*LOWER() becomes LOWERCASE(), UPPER() becomes UPPERCASE(),
* DATE(yyyy,mm,dd) becomes COMPUTEDATE(dd;mm;yyyy), 
*TODAY(), DAY(),WEEK(), MONTH(),=YEAR(TODAY()), 
*EOMONTH() becomes MONTHLENGTH(), 
*NOW() should be date and time becomes time only, SECOND(), MINUTE(), HOUR(),
*DBSUM() becomes DSUM(),


;Missing and possibly useful features/functions needed for ignition to have better support of Excel files 
There is no Merge and Join Text over many cells, no protect and/or freeze row or columns or books but can LOCK sheets, no define bunch of cells as a name, Macros (Arexx?), conditional formatting, no Solver, no Goal Seek, no Format Painter, no AutoFill, no AutoSum function button, no pivot tables, (30 argument limit applies to Excel)

*HLOOKUP(), VLOOKUP(), [http://production-scheduling.com/excel-index-function-most-useful/ INDEX(), MATCH()], CHOOSE(), TEXT(), 
*TRIM(), FIND(), SUBSTITUTE(), CONCATENATE() or &amp;, PROPER(), REPT(), 
*[https://acingexcel.com/excel-sumproduct-function/ SUMPRODUCT()], ROUND(), ROUNDUP(), *ROUNDDOWN(), COUNT(), COUNTA(), SUMIF(), COUNTIF(), COUNTBLANK(), TRUNC(), 
*PMT(), PV(), FV(), POWER(), SQRT(), MODE(), TRUE, FALSE, 
*MODE(), LARGE(), SMALL(), RANK(), STDEV(), 
*DCOUNT(), DCOUNTA(), WEEKDAY(),


;Excel Keyboard [http://dmcritchie.mvps.org/excel/shortx2k.htm shortcuts needed to aid usability in Ignition] 
&lt;pre&gt;
Ctrl Z - Undo

Ctrl D - Fill Down
Ctrl R - Fill right

Ctrl F - Find
Ctrl H - Replace

Ctrl 1 - Formatting of Cells
CTRL SHIFT ~ Apply General Formatting ie a number 
Ctrl ; - Todays Date 

F2 - Edit cell
F4 - toggle cell absolute / relative cell references

&lt;/pre&gt;


====Document Scanning - Scandal====

Scanner usually needs to be connected via a USB port and not via a hub or extension lead.

Check in Trident Prefs -&gt; Devices that the USB Scanner is not bound to anything (e.g. Bindings None)
If not found then reboot the computer and recheck.

Start Scandal, choose Settings from Menu strip at top of screen and in Scanner Driver choose the ?#.device of the scanner (e.g. epson2.device).

The next two boxes - leave empty as they are for morphos SCSI use only
 or put ata.device (use the selection option in bigger box below) and Unit as 0 this is needed for gt68xx

* gt68xx - no editing needed in s/gt68xx.conf but needs a firmware file that corresponds to the scanner [http://www.meier-geinitz.de/sane/gt68xx-backend/ gt68xx firmwares] in sys:s/gt68xx.
* epson2 - Need to edit the file epson2.conf in sys/s that corresponds to the scanner being used

'''Save''' the settings but do not press the Use button (aros freezes)

Back to the Picture Scan window and the right-hand sections.

Click on the '''Information''' tab and press Connect button and the scanner should now be detected.

Go next to the '''Scanner''' tab next to Information Tab should have Color, Black and White, etc. and dpi settings now. Selecting an option Color, B/W etc. can cause dpi settings corruption (especially if the settings are in one line) so set '''dpi first'''. Make sure if Preview is set or not.

In the '''Scan''' Tab, press Scan and the scanner will do its duty. 
Be aware that nothing is saved to disk yet.

In the Save tab, change format JPEG, PNG or IFF DEEP. Tick incremental and base filename if necessary and then click the Save button. The image will now be saved to permanent storage.


The driver ignores a device if it is already bond to another USB class, rejects it from being usable. However, open Trident prefs, select your device and use the right mouse button to open. Select &quot;NONE&quot; to prevent poseidon from touching the device. Now save settings. It should always work now.

[[#top|...to the top]]

===Emulators===

==== Amiberry ====


==== Amiga Emu - Janus UAE ====

With Amibridge, AROS attempts to make the UAE emulator seem embedded within but it still is acting as an app 

There is no dynarec m68k for each hardware that Aros supports or direct patching of motorola calls to AROS hardware accelerated ones unless the emulator has that included 

Try starting Janus with a priority of -1 like this little script:
&lt;pre&gt;
cd sys:system/AmiBridge/emulator
changetaskpri -1
run janus-uae -f my_uaerc.config &gt;nil:
cd sys:prefs
endcli
&lt;/pre&gt;
This stops Janus hogging all the CPU time.


===Miscellaneous===

====Screensaver Blanker====

Most blankers on the amiga (i.e. aros) run as commodities (they are in the tools/commodities drawer). Double click on blanker.

Control is with an app called Exchange, which you need to run first (double click on app) or  run QUIET sys:tools/commodities/Exchange &gt;NIL: but subsequently can use (Cntrl Alt h).

Icon tool types (may be broken) or command line options 
&lt;pre&gt;
seconds=number 
&lt;/pre&gt;

Once the timing is right then add the following to s:icaros-sequence or s:user-startup

e.g. for 5 minutes

 run QUIET sys:tools/commodities/Blanker seconds=300 &gt;NIL:


*[http://archives.aros-exec.org/index.php?function=showfile&amp;file=graphics/screenblanker/gblanker.i386-aros.zip Garshneblanker] can make Aros unstable or slow. Certain blankers crashes in Icaros 2.0.x like Dragon, Executor.


*[ Acuario AROS version], the aquarium screen saver.

Startup: extras:acuariofv-aros/acuario

Kill: c:break name=extras:acuariofv-aros/acuario

Managed to start Acuario by the Executor blanker.

&lt;pre&gt;
cx_priority=
cx_popkey=    ie CX_POPKEY=&quot;Shift F1&quot; 
cx_popup=Yes or No

&lt;/pre&gt;


&lt;pre&gt;
 Qualifier String    Input Event Class
   ----------------    -----------------
    &quot;lshift&quot;           IEQUALIFIER_LSHIFT
    &quot;rshift&quot;           IEQUALIFIER_RSHIFT
    &quot;capslock&quot;         IEQUALIFIER_CAPSLOCK
    &quot;control&quot;          IEQUALIFIER_CONTROL
    &quot;lalt&quot;             IEQUALIFIER_LALT
    &quot;ralt&quot;             IEQUALIFIER_RALT
    &quot;lcommand&quot;         IEQUALIFIER_LCOMMAND
    &quot;rcommand&quot;         IEQUALIFIER_RCOMMAND
    &quot;numericpad&quot;       IEQUALIFIER_NUMERICPAD
    &quot;repeat&quot;           IEQUALIFIER_REPEAT
    &quot;midbutton&quot;        IEQUALIFIER_MIDBUTTON
    &quot;rbutton&quot;          IEQUALIFIER_RBUTTON
    &quot;leftbutton&quot;       IEQUALIFIER_LEFTBUTTON
    &quot;relativemouse&quot;    IEQUALIFIER_RELATIVEMOUSE
&lt;/pre&gt;


&lt;pre&gt;
    Synonym     Synonym
    String     Identifier
    -------    ----------
    &quot;shift&quot;    IXSYM_SHIFT    /* look for either shift key */
    &quot;caps&quot;     IXSYM_CAPS     /* look for either shift key or capslock */
    &quot;alt&quot;      IXSYM_ALT      /* look for either alt key */

Highmap is one of the following strings:
    &quot;space&quot;, &quot;backspace&quot;, &quot;tab&quot;, &quot;enter&quot;, &quot;return&quot;, &quot;esc&quot;, &quot;del&quot;,
    &quot;up&quot;, &quot;down&quot;, &quot;right&quot;, &quot;left&quot;, &quot;f1&quot;, &quot;f2&quot;, &quot;f3&quot;, &quot;f4&quot;, &quot;f5&quot;,
    &quot;f6&quot;, &quot;f7&quot;, &quot;f8&quot;, &quot;f9&quot;, &quot;f10&quot;, &quot;help&quot;.


&lt;/pre&gt;


[[#top|...to the top]]

==== World Construction Set WCS (Version 2.031) ====

WCS is a fractal landscape software such as Scenery Animator, Vista Pro and Panorama. Open sourced February 2022, World Construction Set [https://3dnature.com/downloads/legacy-software/ legally and for free] and [https://github.com/AlphaPixel/3DNature c source]. 

Announced August 1994 this version dates from April 1996 developed by Gary R. Huber and Chris &quot;Xenon&quot; Hanson&quot; from Questar 

&lt;pre&gt;
Assign &quot;WCSProjects:&quot; &quot;Volume:Dir/Dir/WCSProjects&quot; 
Assign &quot;WCSFrames:&quot;   &quot;Volume:Dir/Dir/WCSFrames&quot; 
&lt;/pre&gt;

&lt;pre&gt;
Load projects .proj by accessing pull down menu Project -&gt; Open then click on CanyonSunset.proj
OK to changing .par file and enlarge Status Log window to show what is happening 
Render by pull down menu Modules -&gt; Render with End equal 1 not 300 then click bottom middle button Render 
&lt;/pre&gt;

[https://www.youtube.com/watch?v=CxQDmf1ZWG0 Youtube walkthrough of above], [], [], 

Also try working with the already built file ColoDemo - Then open with the drop-down menu: Project/Open, then WCSProject:ColoDemo.proj
Which allows you to use altimetric DEM files already included and Loading scene parameters from ColoDemo.par
Once this is done, save everything with a new name to start working exclusively on your project. 
Then drop-down menu and select Save As (&quot;NewName&quot;.proj name), then drop-down menu to open parameter and select Save All ( .par name)


After launching the software, there is a the Module Control Panel composed of five icons. 
It is a dock type shortcut of the first few functions of the drop-down menu 

*Database   - Load (#?.proj), Append, Create, Edit, Save, Dir List (of WCSProject drawer), 
*Data Ops   - Extract / Convert Interp DEM, Import DLG, DXF, WDB and export LW map 3d formats  
*Map View   - Database file Loader leading to Map View Control with option to the Database Editor 
*Parameters - Editor for Motion, Color, Ecosystem, Clouds, Waves, management of altimeter files DEM, sclock settings etc 
*Render     - rendering terrain 

These are more in the pull down menu but not in the dock 
*Motion Editor
*Color Editor
*Ecosys Editor 


Simple minimal workflow 
*Load database (1st icon - 1st)
*Set parameters and save .par file (4th icon)
*Render scene (5th icon) 

[https://www.youtube.com/watch?v=ZbTwwR2qcc4 Youtube], [], 

&lt;pre&gt;
.proj new project name which creates a drawer of additional files 

.binary array, ascii array .xyz , z buffer, DTED .dt0, vista 1990s dem, iff  conversion 
.Obj with .elev, .frd with .hdr maps, - digital elevation model (DEM) is a 3D representation of elevation data in various formats 
USGS 7.5MinDEM, 

.par 


&lt;/pre&gt;


Since for the time being no project is loaded, a query window indicates a procedural error when clicking on the rendering icon (right end of the bar). The menu is quite traditional; it varies according to the activity of the windows. To display any altimetric file in the &quot;Mapview&quot; (third icon of the panel), There are three possibilities:

* Loading of a demonstration project.
* The import of a DEM file, followed by texturing and packaging from the &quot;Database-Editor&quot; and the &quot;Color-Editor&quot;.
* The creation of an altimetric file in WCS format, then texturing.


The altimeter file editing (display in the menu) is only made possible if the &quot;Mapview&quot; window is active.

The software is made up of many windows and won't be able to describe them all. Know that &quot;Color-Editor&quot; and the &quot;Data-Editor&quot; comprise sufficient functions for obtaining an almost real rendering quality. You have the possibility of inserting vector objects in the &quot;Data-Editor&quot; (creation of roads, railways, etc.) 


The Map View (MapView) window

*Database - Objects and Topos
*View     - Align, Center, Zoom, Pan, Move 
*Draw     - Maps and distance 
*Object   - Find, highlight, add points, conform topo, duplicate 
*Motion   - Camera, Focus, path, elevation 
*Windows  - DEM designer, Cloud (.cld) and wave (.wve) editor, 


You will notice that by selecting this window and simply moving the pointer to various points on the map you will see latitude and longitude values ​​change, along with the height.
Drop-down menu and Modules, then select MapView and change the width of the window with the map to arrange it in the best way on the screen. With the Auto button the center. Window that then displays the contents of my DEM file, in this case the Grand Canyon. MapView allows you to observe the shape of the landscape from above
 

ZOOM button

Press the Zoom button and then with the pointer position on a point on the map, press the left mouse button and then move to the opposite corner to circumscribe the chosen area and press the left mouse button again, then we will see the enlarged area selected on the map.
Would add that there is a box next to the Zoom button that allows the direct insertion of a value which, the larger it is, the smaller the magnification and the smaller the value, the stronger the magnification. At each numerical change you will need to press the DRAW button to update the view.

PAN button

Under Zoom you will find the PAN button which allows you to move the map at will in all directions by the amount you want. This is done by drawing a line in one direction, then press PAN and point to an area on the map with the pointer and press the left mouse button. At this point, leave it and move the pointer in one direction by drawing a line and press the left mouse button again to trigger the movement of the map on the screen (origin and end points). Do some experiments and then use the Auto button immediately below to recenter everything.
There are parameters such as TOPO, VEC to be left checked and immediately below one that allows different views of the map with the Style command (Single, Multi, Surface, Emboss, Slope, Contour), each with its own particularities to highlight different details.

Now you have the first basics to manage your project visually on the map. Close the MapView window and go further...


Let's start working on ECOSYSTEMS
If we select Emboss from the MapView Style command we will have a clear idea of ​​how the landscape appears, realizing that it is a predominantly desert region of our planet. Therefore we will begin to act on any vegetation present and the appearance of the landscape.
With WCS we will begin to break down the elements of the landscape by assigning defined characteristics. It will be necessary to determine the classes of the ecosystem (Class) with parameters of Elevation Line (maximum altitude), Relative Elevation (arrangement on basins or convexities with respectively positive or negative parameters), Min Slope and Max Slope (slope). WCS offers the possibility of making ecosystems coexist on the same terrain with the UnderEco function, by setting a Density value.


Ecosys Ecosystem Editor

Let's open it from Modules, then Ecosys Editor. In the left pane you will find the list of ecosystems referring to the files present in our project. It will be necessary to clean up that box to leave only the Water and Snow landscapes and a few other predefined ones. We can do this by selecting the items and pressing the Remove button (be careful not for all elements the button is activated, therefore they cannot all be eliminated).
Once this is done we can start adding new ecosystems. Scroll through the various Unused and as soon as the Name item at the top is activated allowing you to write, type the name of your ecosystem, adding the necessary parameters.
&lt;pre&gt;
Ecosystem1: Name: RockBase Class: Rock Density: 80 MinSlope: 15 UnderEco: Terrain
Ecosystem2: Name: RockIncl Clss: Rock Density: 80 MinSlope: 30 UnderEco: Terrain
Ecosystem3: Name: Grass Class Low Veg Density: 50 Height: 1 Elev Line : 1500 Rel El Eff: 5
Max Slope: 10 – Min Slope: 0 UnderEco: Terrain
Ecosistema4: Name: Shrubs Class: Low Veg Density: 40 Height: 8 Elev Line: 3000
Rel El Eff: -2 Max Slope: 20 Min Slope : 5 UnderEco: Terrain
Ecosistema5: Name: Terrain Class: Ground Density: 100 UnderEco: Terrain
&lt;/pre&gt;

Now we need to identify an intermediate ecosystem that guarantees a smooth transition between all, therefore we select as Understory Ecosystem the one called Terrain in all ecosystems, except Snow and Water .
Now we need to 'emerge' the Colorado River in the Canyon and we can do this by raising the sea level to 900 (Sea Level) in the Ecosystem called Water.
Please note that the order of the ecosystem list gives priority to those that come after. So our list must have the following order: Water, Snow, Shrubs, RockIncl, RockBase, Terrain. It is possible to carry out all movements with the Swap button at the bottom. To put order you can also press Short List. Press Keep to confirm all the work done so far with Ecosystem Editor.
Remember every now and then to save both the Project 'Modules/Save' and 'Parameter/Save All'

EcoModels are made up of .etp .fgp .iff8 for each model 


Color Editor

Now it's time to define the colors of our scene and we can do this by going to Modules and then Color Editor. In the list we focus on our ecosystems, created first.
Let's go to the bottom of the list and select the first white space, assigning the name 'empty1', with a color we like and then we will find this element again in other environments... It could serve as an example for other situations!
So we move to 'grass' which already exists and assign the following colors: R 60 G 70 B50
&lt;pre&gt;
'shrubs': R 60 G 80 B 30
'RockIncl' R 110 G 65 B 60
'RockBase' R 110 G 80 B 80
' Terrain' R 150 G 30 B 30
&lt;pre&gt;
Now we can work on pre-existing colors
&lt;pre&gt;
'SunLight' R 150 G 130 B 130
'Haze and Fog' R 190 G 170 B 170
'Horizon' R 209 G 185 B 190
'Zenith' R 140 G 150 B 200
'Water' R 90 G 125 B 170
&lt;/pre&gt;

Ambient R 0 G 0 B 0

So don't forget to close Color Editor by pressing Keep.
Go once again to Ecosystem Editor and assign the corresponding color to each environment by selecting it using the Ecosystem Color button. Press it several times until the correct one appears. Then save the project and parameters again, as done previously.


Motion Editor

Now it's time to take care of the framing, so let's go to Modules and then to Motion Editor. An extremely feature-rich window will open. Following is the list of parameters regarding the Camera, position and other characteristics:
&lt;pre&gt;
-Camera Altitude: 7.0
-Camera Latitude: 36.075
-Camera Longitude: 112.133
-Focus Attitude: -2.0
-Focus Latitude: 36.275
-Focus Longitude: 112.386
-Camera : 512 → rendering window
-Camera Y: 384 → rendering window
-View Arc: 80 → View width in degrees
-Sun Longitude: 172
-Sun Latitude: -0.9
-Haze Start: 3.8
-Haze Range: 78, 5
&lt;/pre&gt;
As soon as the values ​​shown in the relevant sliders have been modified, we will be ready to open the CamView window to observe the wireframe preview. Let's not consider all the controls that will appear.
Well from the Motion Editor if you have selected Camera Altitude and open the CamView panel, you can change the height of the camera by holding down the right mouse button and moving the mouse up and down. To update the view, press the Terrain button in the adjacent window. As soon as you are convinced of the position, confirm again with Keep. You can carry out the same work with the other functions of the camera, such as Focus Altitude...
Let's now see the next positioning step on the Camera map, but let's leave the CamView preview window open while we go to Modules to open the window at the same time MapView. We will thus be able to take advantage of the view from the other together with a subjective one.


From the MapView window, select with the left mouse button and while it is pressed, move the Camera as desired. To update the subjective preview, always click on Terrain.
While with the same procedure you can intervene on the direction of the camera lens, by selecting the cross and with the left button pressed you can choose the desired view. So with the pressure of Terrain I update the Preview. Possibly can enlarge or reduce the Map View using the Zoom button, for greater precision.
Also write that the circle around the cameras indicates the beginning of the haze, there are two types (haze and fog) linked to the altitude. Would also add that the camera height is editable through the Motion Editor panel.


The sun

Let's see that changing the position of the sun from the Motion Editor. Press the SUN button at the bottom right and set the time and the date. Longitude and latitude are automatically obtained by the program. Always open the View Arc command from the Motion Editor panel, an item present in the Parameter List box.

Once again confirm everything with Keep and then save again.


Animation

The animation part is not left-back and also occupies a window. The settings possibilities are enormous. A time line with dragging functions (&quot;slide&quot;, &quot;drag&quot;...) comparable to that of LightWave completes this window. 


A small window is available for positioning the stars as a function of a date, in order to vary the seasons and their various events (and yes...).

At the bottom of the &quot;Motion-Editor&quot;, a &quot;cam-view&quot; function will give you access to a control panel. Different preview modes are possible. The rendering is also accessible through a window. No less than nine pages compose it. At this level, you will be able to determine the backup name of your images (&quot;path&quot;), the type of texture to be calculated, the resolution of the images, activate or deactivate functions such as the depth buffer (&quot;zbuffer&quot;), the blur, the background image, etc.


Once all these parameters have been set, all you have to do is click on the &quot;Render&quot; button.

For rendering go to Modules and then Render. Select the resolution, then under IMA select the name of the image. Move to FRA and indicate the level of fractal detail which of 4 is quite good. Then Keep to confirm and then reopen the window, pressing Render you will see the result. The image will be opened with any viewing program.


Strengths:

* Multi-window.
* Quality of rendering.
* Accuracy.
* Opening, preview and rendering on CyberGraphX screen.
* Extract / Convert Interp DEM, Import DLG, DXF, WDB and export LW map 3d formats 
* The &quot;zbuffer&quot; function.

Weaknesses:

* No OpenGL management 
* Calculation time.
* No network computing tool.


====Writing CD / DVD - Frying Pan====

Can be backup DVDs (4GB ISO size limit due to use of FileInfoBlock), create audio cds from mp3's, and put .iso files on discs

If using for the first time - click Drive button and Device set to ata.device and unit to 0 (zero)

Click Tracks Button - Drive 1 - Create New Disc or Import Existing Disc Image (iso bin/cue etc.) - Session File open cue file

If you're making a data cd, with files and drawers from your hard drive, you should be using the ISO Builder.. which is the MUI page on the left. (&quot;Data/Audio Tracks&quot; is on the right).

You should use the &quot;Data/Audio tracks&quot; page if you want to create music cds with AIFF/WAV/MP3 files, or if you download an .iso file, and you want to put it on a cd.

Click WRITE Button - set write speed - click on long Write button

Examples

Easiest way would be to burn a DATA CD, simply go to &quot;Tracks&quot; page &quot;ISO Builder&quot; and &quot;ADD&quot; everything you need to burn.

On the &quot;Write&quot; page i have &quot;Masterize Disc (DAO)&quot;, &quot;Close Disc&quot; and &quot;Eject after Write&quot; set.

One must not &quot;Blank disc before write&quot; if one uses a CDR


AUDIO CD from MP3's are as easy but tricky to deal with. FP only understands one MP3 format, Layer II, everything else will just create empty tracks

Burning bootable CD's works only with .iso files. Go to &quot;Tracks&quot; page and &quot;Data/Audio Tracks&quot; and add the .iso


====odf====

Every ODF file is a collection of several subdocuments within a package (ZIP file), each of which stores part of the complete document.

* content.xml – Document content and automatic styles used in the content.
* styles.xml – Styles used in the document content and automatic styles used in the styles themselves.
* meta.xml – Document meta information, such as the author or the time of the last save action.
* settings.xml – Application-specific settings, such as the window size or printer information.


To read document follow these steps:

* Extracting .ods file.
* Getting content.xml file (which contains sheets data).
* Creating XmlDocument object from content.xml file.
* Creating DataSet (that represent Spreadsheet file).
* With XmlDocument select “table:table” elements, and then create adequate DataTables.
* Parse child’s of “table:table” element and fill DataTables with those data.
* At the end, return DataSet and show it in application’s interface.


To write document follow these steps:

* Extracting template.ods file (.ods file that we use as template).
* Getting content.xml file.
* Creating XmlDocument object from content.xml file.
* Erasing all “table:table” elements from the content.xml file.
* Reading data from our DataSet and composing adequate “table:table” elements.
* Adding “table:table” elements to content.xml file.
* Zipping that file as new .ods file.

XLS file format

The XLS file format contains streams, substreams, and records.

These sheet substreams include worksheets, macro sheets, chart sheets, dialog sheets, and VBA module sheets. 
All the records in an XLS document start with a 2-byte unsigned integer to specify Record Type (rt), and another for Count of Bytes (cb). A record cannot exceed 8224 bytes. If larger than the rest is stored in one or more continue records.

* Workbook stream 
**Globals substream
***BoundSheet8 record - info for Worksheet substream i.e. name, location, type, and visibility. (4bytes the lbPlyPos FilePointer, specifies the position in the Workbook stream where the sheet substream starts) 
**Worksheet substream (sheet) - Cell Table - Row record - Cells (2byte=row 2byte=column 2byte=XF format)
***Blank cell record
***RK cell record 32-bit number. 
***BoolErr cell record (2-byte Bes structure that may be either a Boolean value or an error code)
***Number cell record (64-bit floating-point number)
***LabelSst cell record (4-byte integer that specifies a string in the Shared Strings Table (SST). Specifically, the integer corresponds to the array index in the RGB field of the SST)
***Formula cell record (FormulaValue structure in the 8 bytes that follow the cell structure. The next 6 bytes can be ignored, and the rest of the record is a CellParsedFormula structure that contains the formula itself)
***MulBlank record (first 2 bytes give the row, and the next 2 bytes give the column that the series of blanks starts at. Next, a variable length array of cell structures follows to store formatting information, and the last 2 bytes show what column the series of blanks ends on)
***MulRK record 
***Shared String Table (SST) contains all of the string values in the workbook.

ACCRINT(), ACCRINTM(), AMORDEGRC(), AMORLINC(), 
COUPDAYBS(), COUPDAYS(), COUPDAYSNC(), COUPNCD(), COUPNUM(), COUPPCD(), 
CUMIPMT(), CUMPRINC(), 
DB(), DDB(), DISC(), 
DOLLARDE(), DOLLARFR(), 
DURATION(), EFFECT(), FV(), FVSCHEDULE(), 
INTRATE(), IPMT(), IRR(), ISPMT(), MDURATION(), MIRR(), NOMINAL(), NPER(), NPV(), 
ODDFPRICE(), ODDFYIELD(), ODDLPRICE(), ODDLYIELD(), 
PMT(), PPMT(), PRICE(), PRICEDISC(), PRICEMAT(), PV(), RATE(), 
RECEIVED(), SLN(), SYD(), TBILLEQ(), TBILLPRICE(), TBILLYIELD(), 
VDB(), XIRR(), XNPV(), YIELD(), YIELDDISC(), YIELDMAT(),


&lt;pre&gt;
&lt;/pre&gt;


&lt;pre&gt;
&lt;/pre&gt;

&lt;pre&gt;
&lt;/pre&gt;

{{BookCat}}</text>
      <sha1>4ot4sgo40ufazllv73fr7c5ru3hxntp</sha1>
    </revision>
    <revision>
      <id>4656168</id>
      <parentid>4656055</parentid>
      <timestamp>2026-08-03T06:55:24Z</timestamp>
      <contributor>
        <username>Jeff1138</username>
        <id>301139</id>
      </contributor>
      <minor />
      <origin>4656168</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="236137" sha1="q30a61vr5r816atvez0sbn1k4nh9rfq" xml:space="preserve">
==Introduction==


[[#Graphical Image Editing Art]]
[[#Office Application]]
[[#Audio]]

[[#Misc Application]]
[[#Games &amp; Emulation]]

[[#Application Guides]]

[[#top|...to the top]]


[[#top|...to the top]]

Most apps can be opened on the Workbench (aka publicscreen pubscreen) which is the default display option but can offer a custom one set to your configurations (aka custom screen mode promotion). These custom ones tend to stack so the possible use of A-M/A-N method of switching between full screens and the ability to pull down screens as well 

If you are interested in creating or porting new software, see [http://en.wikibooks.org/wiki/Aros/Developer/Docs here]

{|  class=&quot;wikitable sortable&quot; 
|- 
!width:30%;|Internet Applications 
!width:10%;|AROS(x86)
!width:10%;|Commodore-Amiga OS 3.1 (68k)
!width:10%;|Hyperion OS4(PPC)
!width:10%;|MorphOS(PPC)
|-
|&lt;!--Sub Menu--&gt;Web Online Browser [], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=network/browser Odyssey 2.0], [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=1175&amp;highlight=odyssey&amp;rowstart=100 Odyssey 3.0], 
|&lt;!--Amiga OS--&gt;[https://aminet.net/comm/www Amelinium], [https://blog.alb42.de/programs/amifox/ amifox] with [https://github.com/alb42/wrp wrp server], IBrowse*, Voyager*, [https://github.com/amigazen/aweb3/ AWeb 3.6 src], [https://github.com/matjam/aweb AWeb Src], [http://aminet.net/package/comm/www/NetSurf-m68k-sources Netsurf], [], 
|&lt;!--AmigaOS4--&gt;[ Odyssey OWB], [ Timberwolf (Firefox port 2011)], [http://amigaworld.net/modules/newbb/viewtopic.php?forum=32&amp;topic_id=32847 OWB-mui], [http://strohmayer.org/owb/ OWB-Reaction], IBrowse*, [http://os4depot.net/index.php?function=showfile&amp;file=network/browser/aweb.lha AWeb], Voyager, [http://www.os4depot.net/index.php?function=browse&amp;cat=network/browser Netsurf], 
|&lt;!--MorphOS--&gt;Wayfarer, [http://fabportnawak.free.fr/owb/ Odyssey OWB], [ Netsurf], IBrowse*, AWeb, [], 
|-
|&lt;!--Sub Menu--&gt;YouTube, Dailymotion website downloading videos audio [https://github.com/yt-dlp/yt-dlp yt-dlp], [https://clipgrab.org/ clipgrab],  
|&lt;!--AROS--&gt;[], [https://blog.alb42.de/amitube/ Amitube], 
|&lt;!--Amiga OS--&gt;[https://blog.alb42.de/amitube/ Amitube], [ smtube], 
|&lt;!--AmigaOS4--&gt;[https://blog.alb42.de/amitube/ Amitube], getVideo, Tubexx, [https://github.com/walkero-gr/aiostreams aiostreams], 
|&lt;!--MorphOS--&gt;[ ytsearch], [https://blog.alb42.de/amitube/ Amitube], [http://morphos.lukysoft.cz/en/vypis.php?kat=5 getVideo], Tubexx 
|-
|&lt;!--Sub Menu--&gt;Old style E-mailing SMTP POP3 IMAP based 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=network/email SimpleMail], [http://sourceforge.net/projects/simplemail/files/ src], [https://github.com/jens-maus/yam YAM] 
|&lt;!--Amiga OS--&gt;[http://sourceforge.net/projects/simplemail/files/ SimpleMail], [https://github.com/jens-maus/yam YAM]
|&lt;!--AmigaOS4--&gt;SimpleMail, YAM, 
|&lt;!--MorphOS--&gt; SimpleMail, YAM
|-
|&lt;!--Sub Menu--&gt;IRC 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=network/chat WookieChat], [https://sourceforge.net/projects/wookiechat/ Wookiechat src], [http://archives.arosworld.org/index.php?function=browse&amp;cat=network/chat AiRcOS], Jabberwocky, 
|&lt;!--Amiga OS--&gt;Wookiechat, AmIRC 
|&lt;!--AmigaOS4--&gt;Wookiechat 
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=5 Wookiechat], [http://morphos.lukysoft.cz/en/vypis.php?kat=5 AmIRC], 
|-
|&lt;!--Sub Menu--&gt;Instant Messaging IM like [https://github.com/BlitterStudio/amidon Hollywood lang based Mastodon client], BlueSky AT protocol, Facebook(TM), Twitter X (TM), Bitlbee IRC Gateway and others 
|&lt;!--AROS--&gt;[https://github.com/kaffeine1/telegram-amiga telegram-amiga], [http://archives.arosworld.org/index.php?function=browse&amp;cat=network/chat jabberwocky], 
|&lt;!--Amiga OS--&gt;[http://amitwitter.sourceforge.net/ AmiTwitter], CLIMM, SabreMSN, jabberwocky, 
|&lt;!--AmigaOS4--&gt;[http://amitwitter.sourceforge.net/ AmiTwitter], SabreMSN,
|&lt;!--MorphOS--&gt;[http://amitwitter.sourceforge.net/ AmiTwitter], [http://morphos.lukysoft.cz/en/vypis.php?kat=5 PolyglotNG], SabreMSN,
|-
|&lt;!--Sub Menu--&gt;Torrents 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=network/p2p ArTorr], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;CTorrent, Transmission 
|&lt;!--MorphOS--&gt;MLDonkey, Beehive, [http://morphos.lukysoft.cz/en/vypis.php?kat=5 Transmission], CTorrent, 
|-
|&lt;!--Sub Menu--&gt;FTP 
|&lt;!--AROS--&gt;[https://github.com/BlitterStudio/dopus5 Dopus5 Magellan], MarranoFTP, 
|&lt;!--Amiga OS--&gt;[https://github.com/BlitterStudio/dopus5 Dopus5 Magellan], [http://aminet.net/package/comm/tcp/AmiFTP AmiFTP], AmiTradeCenter, ncFTP, 
|&lt;!--AmigaOS4--&gt;[https://github.com/BlitterStudio/dopus5 Dopus5 Magellan], 
|&lt;!--MorphOS--&gt;[https://github.com/BlitterStudio/dopus5 Dopus5 Magellan], [http://morphos.lukysoft.cz/en/vypis.php?kat=5 Pftp], [http://aminet.net/package/comm/tcp/AmiFTP-1.935-OS4 AmiFTP], 
|-
|&lt;!--Sub Menu--&gt;WYSIWYG Web Site Editor
|&lt;!--AROS--&gt; 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Internet Radio Streaming Audio [http://www.gnu.org/software/gnump3d/ gnump3d], [http://www.icecast.org/ Icecast2] Server (Broadcast) and Client (Listen), [ mpd], [http://darkice.sourceforge.net/ DarkIce], [http://www.dyne.org/software/muse/ Muse], 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=audio/misc ], Mplayer (Icecast Client only), 
|&lt;!--Amiga OS--&gt;[https://github.com/sandlbn/TuneFinder TuneFinder C Src], [https://github.com/sandlbn/TuneFinderMUI TuneFinderMUI], [http://amigazeux.net/anr/ AmiNetRadio], [], [], 
|&lt;!--AmigaOS4--&gt;[http://www.tunenet.co.uk/ Tunenet], 
|&lt;!--MorphOS--&gt;Mplayer, AmiNetRadio, 
|-
|&lt;!--Sub Menu--&gt;VoIP (Voice over IP) with SIP Client (Session Initiation Protocol) or Asterisk IAX2 Clients Softphone (skype like) 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;AmiPhone with Speak Freely, 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Weather Forecast 
|&lt;!--AROS--&gt;[http://sourceforge.net/projects/zunetools/files/ WeatherBar], [http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/workbench AWeather], []
|&lt;!--Amiga OS--&gt;[http://amigazeux.net/wetter/ Wetter], [https://github.com/emartisoft/AmiWeatherForecasts AmiWeatherForecasts src], 
|&lt;!--AmigaOS4--&gt;[http://os4depot.net/?function=showfile&amp;file=utility/workbench/flipclock.lha FlipClock], 
|&lt;!--MorphOS--&gt;[http://amigazeux.net/wetter/ Wetter], 
|-
|&lt;!--Sub Menu--&gt;Street Road Maps Route Planning GPS Tracking  
|&lt;!--AROS--&gt;[https://blog.alb42.de/programs/muimapparium/ MuiMapparium] [https://build.alb42.de/ Build of MuiMapp versions], 
|&lt;!--Amiga OS--&gt;AmiAtlas*, UKRoutePlus*, [http://blog.alb42.de/ AmOSM], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;[http://blog.alb42.de/programs/mapparium/ Mapparium], 
|-
|&lt;!--Sub Menu--&gt;Clock and Date setting from the internet (either ntp or websites) [https://www.timeanddate.com/worldclock/ World Clock], [http://www.time.gov/ NIST], [], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=network/misc ntpsync],  
|&lt;!--Amiga OS--&gt;ntpsync 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Newsgroups
|&lt;!--AROS--&gt; 
|&lt;!--Amiga OS--&gt;[http://newscoaster.sourceforge.net/ Newscoaster], [https://github.com/jens-maus/newsrog NewsRog], [ WorldNews], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|}

&lt;nowiki&gt;*&lt;/nowiki&gt; Commercial product.


==Graphical Image Editing Art==
{|  class=&quot;wikitable sortable&quot; 
|- 
!width:30%;|Image Editing
!width:10%;|AROS(x86)
!width:10%;|Commodore-Amiga OS 3.1(68k)
!width:10%;|Hyperion OS4(PPC)
!width:10%;|MorphOS(PPC)
|-
|&lt;!--Sub Menu--&gt;Pixel Raster Artwork [https://github.com/LibreSprite/LibreSprite LibreSprite based on GPL aseprite], [https://github.com/abetusk/hsvhero hsvhero], [], 
|&lt;!--AROS--&gt;[https://sourceforge.net/projects/zunetools/files/ZunePaint/ ZunePaint], [http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/edit LunaPaint], [http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/edit GrafX2], [ LodePaint needs OpenGL], 
|&lt;!--Amiga OS--&gt;[http://www.amigaforever.com/classic/download.html PPaint], GrafX2, [https://github.com/grovdata/Amiga_Sources/blob/master/software.md DeluxePaint], [http://www.amiforce.de/perfectpaint/perfectpaint.php PerfectPaint], Zoetrope, Brilliance2*, 
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=graphics/edit LodePaint], GrafX2, 
|&lt;!--MorphOS--&gt;Sketch, Pixel*, GrafX2, [http://morphos.lukysoft.cz/en/vypis.php?kat=3 LunaPaint]
|-
|&lt;!--Sub Menu--&gt;Image viewing 
|&lt;!--AROS--&gt;[http://sourceforge.net/projects/zunetools/files/ ZuneView], [http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/viewer LookHere], [http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/viewer LoView], [http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/viewer PicShow] , [http://amigaworld.net/modules/newbb/viewtopic.php?mode=viewtopic&amp;topic_id=31400&amp;forum=32&amp;start=80&amp;viewmode=flat&amp;order=0#583458 Picture Album], 
|&lt;!--Amiga OS--&gt;PicShow, PicView, Photoalbum,
|&lt;!--AmigaOS4--&gt;WarpView, PicShow, flPhoto, Thumbs, [http://amigaworld.net/modules/newbb/viewtopic.php?mode=viewtopic&amp;topic_id=31400&amp;forum=32&amp;start=80&amp;viewmode=flat&amp;order=0#583458 Picture Album], 
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=3 ShowGirls], [http://amigaworld.net/modules/newbb/viewtopic.php?mode=viewtopic&amp;topic_id=31400&amp;forum=32&amp;start=80&amp;viewmode=flat&amp;order=0#583458 Picture Album]
|-
|&lt;!--Sub Menu--&gt;Photography retouching / Image Manipulation like Photoshop(tm)  
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/edit RNOEffects], [https://sourceforge.net/projects/zunetools/files/ ZunePaint], [http://sourceforge.net/projects/zunetools/files/ ZuneView], 
|&lt;!--Amiga OS--&gt;[ Tecsoft Video Paint aka TVPaint], Photogenics*, ArtEffect*, ImageFX*, XiPaint, fxPaint, ImageMasterRT, Opalpaint, 
|&lt;!--AmigaOS4--&gt;WarpView, flPhoto, [http://www.os4depot.net/index.php?function=browse&amp;cat=graphics/edit Photocrop]
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=3 ShowGirls], ImageFX*, 
|-
|&lt;!--Sub Menu--&gt;Manage RAW picture folder galleries like Darktable, RAWtherapy, etc 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Graphic Format Converter - ICC profile support sRGB, Adobe RGB, XYZ and linear RGB 
|&lt;!--AROS--&gt; 
|&lt;!--Amiga OS--&gt;GraphicsConverter, ImageStudio, [http://www.coplabs.org/artpro.html ArtPro]
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Thumbnail Generator [], 
|&lt;!--AROS--&gt;[http://sourceforge.net/projects/zunetools/files/ ZuneView], [http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/shell Thumbnail Generator]
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Icon Editor
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/iconedit Archives], [http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/workbench Icon Toolbox], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=graphics/iconedit IconEditor]
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;2D Pixel Art Animation 
|&lt;!--AROS--&gt;Lunapaint
|&lt;!--Amiga OS--&gt;PPaint, AnimatED, Scala*, GoldDisk MovieSetter*, Walt Disney's Animation Studio*, ProDAD*, [https://github.com/historicalsource/DeluxePaint DeluxePaint src], Brilliance
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=3 Titler] 
|-
|&lt;!--Sub Menu--&gt;2D SVG based MovieSetter type 
|&lt;!--AROS--&gt; 
|&lt;!--Amiga OS--&gt;MovieSetter*, Fantavision*
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Morphing 
|&lt;!--AROS--&gt;[ GLMorph]
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;2D Cad (qcad-&gt;LibreCAD, etc.) 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;Xcad, MaxonCAD
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;3D Cad like FreeCad, BRL-CAD, OpenSCAD, AvoCADo, etc. using dxf, obj (vertices), blend, 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;XCad3d*, DynaCADD*, Cycas, 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;3D Model Rendering of glft (json) gbl (png jpg), usdz (USD files with materials, textures, and animations), FBX Filmbox is a proprietary Autodesk format, 
|&lt;!--AROS--&gt;POV-Ray
|&lt;!--Amiga OS--&gt;[http://www.discreetfx.com./amigaproducts.html CINEMA 4D]*, POV-Ray, Lightwave3D*, Real3D*, Caligari24*, Reflections/Monzoom*, [https://github.com/privatosan/RayStorm Raystorm src], Tornado 3D
|&lt;!--AmigaOS4--&gt;Blender, POV-Ray, Yafray
|&lt;!--MorphOS--&gt;Blender, POV-Ray, Yafray
|-
|&lt;!--Sub Menu--&gt;3D Format Converter [], [], 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/?function=showfile&amp;file=graphics/convert/ 3doc.i386-aros], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=showfile&amp;file=graphics/convert/ivcon.lha IVCon]
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt; 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Screen grabbing display 
|&lt;!--AROS--&gt;[ Screengrabber], [http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/misc snapit], [http://archives.arosworld.org/index.php?function=browse&amp;cat=video/record screen recorder], []
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Grab graphics music from apps [https://github.com/Malvineous/ripper6 ripper6], [],
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt; 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|}

&lt;nowiki&gt;*&lt;/nowiki&gt; Commercial product.

[[#top|...to the top]]

==Office Application==
{|  class=&quot;wikitable sortable&quot; 
|- 
!width:30%;|Office
!width:10%;|AROS (x86)
!width:10%;|[http://en.wikipedia.org/wiki/Amiga_software Commodore-Amiga OS 3.1] (68k)
!width:10%;|[http://en.wikipedia.org/wiki/AmigaOS_4 Hyperion OS4] (PPC)
!width:10%;|[http://en.wikipedia.org/wiki/MorphOS MorphOS] (PPC)
|-
|&lt;!--Sub Menu--&gt;Word-processing 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=office/wordprocessing Cinnamon Writer], [https://finalwriter.godaddysites.com/ Final Writer 7*], [https://github.com/sodero/MUI-Vim/releases MUI-Vim], [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=1995&amp;rowstart=20&amp;pid=12668#post_12668 Slovo], [], 
|&lt;!--AmigaOS--&gt;[ Softwood FinalCopy II*], Haage AmigaWriter*, Digita WordWorth*, Softwood FinalWriter*, Micro-Systems Excellence 3*, Arnor Protext, Rashumon, [ InterWord], [ KindWords], [WordPerfect], [ New Horizons Flow], [ CygnusEd Pro], [ Micro-systems Scribble], 
|&lt;!--AmigaOS4--&gt;AbiWord, [ CinnamonWriter]
|&lt;!--MorphOS--&gt;[ Cinnamon Writer], [http://www.meta-morphos.org/viewtopic.php?topic=1246&amp;forum=53 scriba], [http://morphos.lukysoft.cz/en/index.php Papyrus Office], 
|-
|&lt;!--Sub Menu--&gt;Spreadsheets 
|&lt;!--AROS--&gt;[https://blog.alb42.de/programs/leu/ Leu], [https://archives.arosworld.org/index.php?function=browse&amp;cat=office/spreadsheet], 
|&lt;!--AmigaOS--&gt;[https://aminet.net/package/biz/spread/ignition-src Ignition Src 1.3], [MaxiPlan 500 Plus], [OXXI Plan/IT v2.0 Speadsheet], [ Superplan], [ Creative Developments TurboCalc], [ ProCalc], [ InterSpread], [Digita DGCalc], [ Gold Disk Advantage], [ Micro-systems Analyze!]
|&lt;!--AmigaOS4--&gt;Gnumeric, [https://ignition-amiga.sourceforge.net/ Ignition], 
|&lt;!--MorphOS--&gt;[ ignition], [http://morphos.lukysoft.cz/en/vypis.php Papyrus Office], 
|-
|&lt;!--Sub Menu--&gt;Presentations
|&lt;!--AROS--&gt;[http://www.hollywoood-mal.com/ Hollywood]*, 
|&lt;!--Amiga OS--&gt;[http://www.hollywoood-mal.com/ Hollywood]*, MediaPoint, PointRider, Scala*, 
|&lt;!--Amiga OS4--&gt;[http://www.hollywoood-mal.com/ Hollywood]*, PointRider 
|&lt;!--MorphOS--&gt;[http://www.hollywoood-mal.com/ Hollywood]*, PointRider
|-
|&lt;!--Sub Menu--&gt;Databases 
|&lt;!--AROS--&gt;[http://sdb.freeforums.org/ SDB], [http://archives.arosworld.org/index.php?function=browse&amp;cat=office/database BeeBase], 
|&lt;!--Amiga OS--&gt;Precision Superbase 4 Pro*, Arnor Prodata*, BeeBase, Datastore, FinalData*, AmigaBase, Fiasco, Twist2*, [Digita DGBase], [], 
|&lt;!--AmigaOS4--&gt;BeeBase, SQLite, 
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=6 BeeBase], 
|-
|&lt;!--Sub Menu--&gt;PDF Viewing and editing digital signatures 
|&lt;!--AROS--&gt;[http://sourceforge.net/projects/arospdf/ ArosPDF via splash], [https://github.com/wattoc/AROS-vpdf vpdf wip], 
|&lt;!--Amiga OS--&gt;APDF 
|&lt;!--AmigaOS4--&gt;AmiPDF 
|&lt;!--MorphOS--&gt;APDF, vPDF, 
|-
|&lt;!--Sub Menu--&gt;Printing 
|&lt;!--AROS--&gt;Postscript 3 laser printers and Ghostscript internal, [ GutenPrint], 
|&lt;!--Amiga OS--&gt;[http://www.irseesoft.de/tp_what.htm TurboPrint]* 
|&lt;!--AmigaOS4--&gt;(some native drivers), 
|&lt;!--MorphOS--&gt;early TurboPrint included, 
|-
|&lt;!--Sub Menu--&gt;Note Taking markdown support like Obsidian like, joplin, OneNote, EverNotes, xournalpp, etc 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Study and analyse, collect, organize, annotate, cite, and share
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;PIM Personal Information Manager - Day Diary Planner Calendar App 
|&lt;!--AROS--&gt;[ ], [ ], [ ], 
|&lt;!--Amiga OS--&gt;Digita Organiser*, On The Ball, Everyday Organiser, [ Contact Manager], 
|&lt;!--AmigaOS4--&gt;AOrganiser, 
|&lt;!--MorphOS--&gt;[http://polymere.free.fr/orga_en.html PolyOrga], 
|-
|&lt;!--Sub Menu--&gt;Accounting
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=office/misc ETB], LoanCalc, [ ], [ ], [ ], 
|[ Digita Home Accounts2], Accountant, Small Business Accounts, Account Master, [ Amigabok], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Project Management Research 
|&lt;!--AROS--&gt; 
|&lt;!--Amiga OS--&gt;SuperGantt, SuperPlan, 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;System Wide Search 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=utility/filetool Finder], [], [], 
|&lt;!--Amiga OS--&gt; 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;System Wide Dictionary - multilingual [http://sourceforge.net/projects/babiloo/ Babiloo], [http://code.google.com/p/stardict-3/ StarDict], 
|&lt;!--AROS--&gt;[ ],  
|&lt;!--AmigaOS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;System wide Thesaurus - multi lingual
|&lt;!--AROS--&gt;[ ], 
|Kuma K-Roget*, 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Sticky Desktop Notes (post it type) 
|&lt;!--AROS--&gt;[http://aminet.net/package/util/wb/amimemos.i386-aros AmiMemos], [https://aminet.net/package/util/wb/amimemos.src-aros AmiMemos Src], [], 
|&lt;!--Amiga OS--&gt;[http://aminet.net/package/util/wb/StickIt-2.00 StickIt v2], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;DTP Desktop Publishing 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/edit RNOPublisher], 
|&lt;!--Amiga OS--&gt;[http://pagestream.org/ Pagestream]*, Professional Pro Page*, Saxon Publisher, Pagesetter, PenPal, 
|&lt;!--AmigaOS4--&gt;[http://pagestream.org/ Pagestream]* 
|&lt;!--MorphOS--&gt;[http://pagestream.org/ Pagestream]* 
|-
|&lt;!--Sub Menu--&gt;Scanning 
|&lt;!--AROS--&gt;[ SCANdal], [], 
|&lt;!--Amiga OS--&gt;FxScan*, ScanQuix* 
|&lt;!--AmigaOS4--&gt;SCANdal (Sane)
|&lt;!--MorphOS--&gt;SCANdal
|-
|&lt;!--Sub Menu--&gt;OCR
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/convert gOCR] 
|&lt;!--AmigaOS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;[http://morphos-files.net/categories/office/text Tesseract] 
|-
|&lt;!--Sub Menu--&gt;Text Editing
|&lt;!--AROS--&gt;Jano Editor (already installed as Editor), [http://archives.arosworld.org/index.php?function=browse&amp;cat=development/edit EdiSyn], [http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/text/edit Annotate], [https://archives.arosworld.org/index.php?function=browse&amp;cat=development/edit Vim], [http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/text/edit FrexxEd] [https://github.com/vidarh/FrexxEd src], [ NoWinEd], 
|&lt;!--Amiga OS--&gt;[https://aminet.net/package/text/edit/TurboText20 TurboText20 ttx], Annotate, MicroGoldED/CubicIDE*, CygnusED*, Protext*, NoWinED, 
|&lt;!--AmigaOS4--&gt;Notepad, Annotate, CygnusED*, NoWinED, 
|&lt;!--MorphOS--&gt;MorphOS ED, NoWinED, GoldED/CubicIDE*, CygnusED*, Annotate, 
|-
|&lt;!--Sub Menu--&gt;Office Fonts [http://sourceforge.net/projects/fontforge/files/fontforge-source/ Font Designer] 
|&lt;!--AROS--&gt;[ ], [ ], 
|&lt;!--Amiga OS--&gt;TypeSmith*, SaxonScript (GetFont Adobe Type 1), 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Drawing Vector
|&lt;!--AROS--&gt;[http://sourceforge.net/projects/amifig/ ZuneFIG previously AmiFIG], [https://github.com/serk118/designworks-aros designworks aros 64bit]
|&lt;!--Amiga OS--&gt;Drawstudio*, ProVector*, ArtExpression*, Professional Draw*, AmiFIG, MetaView, [https://gitlab.com/amigasourcecodepreservation/designworks Design Works Src], [], 
|&lt;!--AmigaOS4--&gt;MindSpace, [http://www.os4depot.net/index.php?function=browse&amp;cat=graphics/edit amifig], 
|&lt;!--MorphOS--&gt;SteamDraw, [http://aminet.net/package/gfx/edit/amifig amiFIG], 
|-
|&lt;!--Sub Menu--&gt;video conferencing (jitsi) 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;source code hosting
|&lt;!--AROS--&gt;Gitlab, 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Remote Desktop (server)
|&lt;!--AROS--&gt;[http://sourceforge.net/projects/zunetools/files/VNC_Server ArosVNCServer], 
|&lt;!--Amiga OS--&gt;[http://s.guillard.free.fr/AmiVNC/AmiVNC.htm AmiVNC], [http://dspach.free.fr/amiga/avnc/index.html AVNC]
|&lt;!--AmigaOS4--&gt;[http://s.guillard.free.fr/AmiVNC/AmiVNC.htm AmiVNC] 
|MorphVNC, vncserver
|-
|&lt;!--Sub Menu--&gt;Remote Desktop (client) login and connect to another machine 
|&lt;!--AROS--&gt;[https://sourceforge.net/projects/zunetools/files/VNC_Client/ ArosVNC], [http://archives.arosworld.org/index.php?function=browse&amp;cat=network/misc rdesktop], 
|&lt;!--Amiga OS--&gt;[http://twinvnc.free.fr/index.php?menu=01&amp;lang=eng TwinVNC], [http://dspach.free.fr/amiga/vva/index.html VVA], [http://www.hd-zone.com/ RDesktop]
|&lt;!--AmigaOS4--&gt;[http://twinvnc.free.fr/index.php?menu=01&amp;lang=eng TwinVNC], [http://www.hd-zone.com/ RDesktop]
|[http://twinvnc.free.fr/index.php?menu=01&amp;lang=eng TwinVNC], [http://www.hd-zone.com/ RDesktop]
|-
|&lt;!--Sub Menu--&gt;notifications 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;Ranchero 
|&lt;!--AmigaOS4--&gt;Ringhio 
|&lt;!--MorphOS--&gt;MagicBeacon 
|-
|&lt;!--Sub Menu--&gt;Biometric facial logins and fingerprint security features 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt; 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt; 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|}

&lt;nowiki&gt;*&lt;/nowiki&gt; Commercial product.

[[#top|...to the top]]

==Audio==
{|  class=&quot;wikitable sortable&quot; 
|- 
!width:30%;|Audio
!width:10%;|AROS(x86)
!width:10%;|Commodore-Amiga OS 3.1(68k)
!width:10%;|Hyperion OS4(PPC)
!width:10%;|MorphOS(PPC)
|-
|&lt;!--Sub Menu--&gt;Playing playback Audio like MP3, [https://github.com/chrg127/gmplayer NSF], [https://github.com/kode54/lazyusf miniusf .usflib] [https://gitlab.com/kode54/psflib with pfslib], [], [], etc 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=video/play Mplayer], [ HarmonyPlayer hp], [http://www.a500.org/downloads/audio/index.xhtml playcdda] CDs, [ WildMidi Player], [https://bszili.morphos.me/ UADE mod player], [], [ RNOTunes], [ mp3Player], [], 
|&lt;!--Amiga OS--&gt;AmiNetRadio, AmigaAmp, playOGG, 
|&lt;!--AmigaOS4--&gt;TuneNet, SimplePlay, AmigaAmp, TKPlayer
|AmiNetRadio, Mplayer, Kaya, AmigaAmp
|-
|&lt;!--Sub Menu--&gt;Editing Audio 
|&lt;!--AROS--&gt;[ Audio Evolution 4] 
|&lt;!--Amiga OS--&gt;[ Samplitude Opus Key], [https://sourceforge.net/projects/hd-rec/ HD-Rec Src], [http://www.sonicpulse.de/eng/news.html SoundFX], 
|&lt;!--AmigaOS4--&gt;[https://sourceforge.net/projects/hd-rec/ HD-Rec], AmiSoundED, [http://os4depot.net/?function=showfile&amp;file=audio/record/audioevolution4.lha Audio Evolution 4] 
|[http://www.hd-rec.de/HD-Rec/index.php?site=home HD-Rec], 
|-
|&lt;!--Sub Menu--&gt;Editing Tracker Music
|&lt;!--AROS--&gt;[https://github.com/hitchhikr/protrekkr Protrekkr], [ Schism Tracker], [http://archives.arosworld.org/index.php?function=browse&amp;cat=audio/tracker MilkyTracker], [http://www.hivelytracker.com/ HivelyTracker], [ Radium in AROS already],  [http://www.a500.org/downloads/development/index.xhtml libMikMod], 
|&lt;!--Amiga OS--&gt;MilkyTracker, HivelyTracker, DigiBooster, Octamed SoundStudio, 
|&lt;!--AmigaOS4--&gt;MilkyTracker, HivelyTracker, GoatTracker
|MilkyTracker, GoatTracker, DigiBooster, 
|-
|&lt;!--Sub Menu--&gt;Editing Music [], [https://github.com/kmatheussen/camd CAMD] and/or staves and notes manuscript 
|&lt;!--AROS--&gt;[http://bnp.hansfaust.de/ Bars and Pipes for AROS], [ Audio Evolution], [], 
|&lt;!--Amiga OS--&gt;[http://bnp.hansfaust.de/ Bars'n'Pipes], MusicX* David &quot;Talin&quot; Joiner &amp; Craig Weeks (for Notator-X), Deluxe Music Construction 2*, [https://github.com/timoinutilis/midi-sequencer-amigaos Horny c Src], HD-Rec, [https://aminet.net/package/mus/midi/dominatorV1_51 Dominator], 
|&lt;!--AmigaOS4--&gt;[https://sourceforge.net/p/hd-rec/code/HEAD/tree/ HD-Rec Src], Rockbeat, [http://bnp.hansfaust.de/download.html Bars'n'Pipes], [http://os4depot.net/index.php?function=browse&amp;cat=audio/edit Horny], Audio Evolution 4, 
|&lt;!--MorphOS--&gt;Bars'n'Pipes, 
|-
|&lt;!--Sub Menu--&gt;Sound Sampling 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=audio/record Audio Evolution 4], [http://www.imica.net/SitePortalPage.aspx?siteid=1&amp;did=162 Quick Record], [https://archives.arosworld.org/index.php?function=browse&amp;cat=audio/misc SOX to get AIFF 16bit files], [https://github.com/aros-development-team/AROS/tree/master/workbench/tools/AHIRecord AHIRecord], 
|&lt;!--Amiga OS--&gt;[https://aminet.net/package/mus/edit/AudioEvolution3_src Audio Evolution 3 c src], [ Samplitude-MS Opus Key], Audiomaster IV*, 
|&lt;!--AmigaOS4--&gt;[https://github.com/timoinutilis/phonolith-amigaos phonolith c src], HD-Rec, Audio Evolution 4,
|&lt;!--MorphOS--&gt;[https://sourceforge.net/p/hd-rec/code/HEAD/tree/ HD-Rec Src], Audio Evolution 4,
|-
|&lt;!--Sub Menu--&gt;Live Looping or Audio Misc - Groovebox like
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;CD/DVD burn
|[https://code.google.com/p/amiga-fryingpan/ FryingPan], 
|&lt;!--Amiga OS--&gt;FryingPan, [http://www.estamos.de/makecd/#CurrentVersion MakeCD], 
|&lt;!--AmigaOS4--&gt;FryingPan, AmiDVD, 
|[http://www.amiga.org/forums/printthread.php?t=58736 FryingPan], Jalopeano, 
|-
|&lt;!--Sub Menu--&gt;CD/DVD audio rip
|Lame, [http://www.imica.net/SitePortalPage.aspx?siteid=1&amp;cfid=0&amp;did=167 Quick CDrip],
|&lt;!--Amiga OS--&gt;Lame,  
|&lt;!--AmigaOS4--&gt;Lame, 
|Lame,  
|-
|&lt;!--Sub Menu--&gt;MP3 v1 and v2 Tagger
|&lt;!--AROS--&gt;id3ren (v1), [http://archives.arosworld.org/index.php?function=browse&amp;cat=audio/edit mp3info], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|
|-
|&lt;!--Sub Menu--&gt;Audio Convert
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=audio/misc Sox], [], 
|&lt;!--Amiga OS--&gt;[http://aminet.net/package/mus/misc/SoundBox SoundBox], [http://aminet.net/package/mus/misc/SoundBoxKey SoundBox Key], [http://aminet.net/package/mus/edit/SampleE SampleE], sox 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;DJ mixing jamming 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Radio Automation Software [http://www.rivendellaudio.org/ Rivendell], [http://code.campware.org/projects/livesupport/report/3 Campware LiveSupport], [http://www.sourcefabric.org/en/airtime/ SourceFabric AirTime], [http://www.ohloh.net/p/mediabox404 MediaBox404], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Speakers Audio Sonos Mains AC networked wired controlled 
*2005 ZP100 with ZP80 
*2008 Zoneplayer ZP120 (multi-room wireless amp)  ZP90 receiver only with CR100 controller, 
*2009 ZonePlayer S5, 
*2010 BR100 wireless Bridge (no support),   
*2011 Play:3
*2013 Bridge (no support), Play:1,  
*2016 Arc,   Play:1,   
*Beam (Gen 2),   Playbar,  Ray,   Era 100,   Era 300,   Roam,   Move 2,   
*Sub (Gen 3),   Sub Mini,  Five,  Amp  S2 
|&lt;!--AROS--&gt;SonosController 
|&lt;!--Amiga OS--&gt;SonosController
|&lt;!--AmigaOS4--&gt;SonosController
|&lt;!--MorphOS--&gt;SonosController
|-
|&lt;!--Sub Menu--&gt;Smart Speakers 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt; 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|}

&lt;nowiki&gt;*&lt;/nowiki&gt; Commercial product.

[[#top|...to the top]]

==Video Creativity and Production==
{|  class=&quot;wikitable sortable&quot; 
|- 
!width:30%;|Video
!width:10%;|AROS(x86)
!width:10%;|Commodore-Amiga OS 3.1(68k)
!width:10%;|Hyperion OS4(PPC)
!width:10%;|MorphOS(PPC)
|-
|&lt;!--Sub Menu--&gt;Playing Video 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=video/play Mplayer VAMP], [http://www.a500.org/downloads/video/index.xhtml CDXL player], [http://www.a500.org/downloads/video/index.xhtml IffAnimPlay], [], 
|&lt;!--Amiga OS--&gt;Frogger*, AMP2, MPlayer, RiVA*, MooViD*, 
|&lt;!--AmigaOS4--&gt;DvPlayer, MPlayer 
|&lt;!--MorphOS--&gt;MPlayer, Frogger, AMP2, VLC 
|-
|&lt;!--Sub Menu--&gt;Streaming Video and game streaming like OBS studio, Parsec, [https://github.com/lizardbyte/sunshine sunshine], [https://github.com/moonlight-stream/moonlight-qt moonlight], etc 
|&lt;!--AROS--&gt;Mplayer, 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;Mplayer, Gnash, Tubexx 
|&lt;!--MorphOS--&gt;Mplayer, OWB, Tubexx
|-
|&lt;!--Sub Menu--&gt;Playing DVD 
|&lt;!--AROS--&gt;[http://a-mc.biz/ AMC]*, Mplayer 
|&lt;!--Amiga OS--&gt;AMP2, Frogger 
|&lt;!--AmigaOS4--&gt;[http://a-mc.biz/ AMC]*, DvPlayer*, AMP2,  
|&lt;!--MorphOS--&gt;Mplayer 
|-
|&lt;!--Sub Menu--&gt;Screen Recording
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=video/record Screenrecorder], [ ], [ ], [ ], [ ], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;Screenrecorder, 
|-
|&lt;!--Sub Menu--&gt;Create and Edit Individual Video NLE 
|&lt;!--AROS--&gt;[ Mencoder], [ Quick Videos], [http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/edit AVIbuild], [http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/misc FrameBuild], FFMPEG, 
|&lt;!--Amiga OS--&gt;[ MainConcept Mainactor Broadcast*], [http://en.wikipedia.org/wiki/Video_Toaster Video Toaster*], MacroSystem MovieShop 4.3*, proDAD Adorage*, [ IOSpirit VHI studio]*, [Gold Disk ShowMaker], [], 
|&lt;!--AmigaOS4--&gt;FFMpeg/GUI 
|&lt;!--MorphOS--&gt;Blender, Mencoder, FFmpeg
|-
|&lt;!--Sub Menu--&gt;Subtitle editor 
|&lt;!--AROS--&gt;[https://aminet.net/package/text/edit/Slarti_Arosx86ABIv0 Slarti_Arosx86ABIv0], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;IP-based video production workflows with High Dynamic Range (HDR), 10-bit color collaborative NDI, 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Blogging like Lemmy or kbin
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;VR face recognition for Vtubers 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;VR chatting Live2D models with Cubism type editor 
&lt;pre&gt;
Model data (cmo3)
Basic motions (can3)
Background image (png)
Set of files for embedding (runtime folder)
• Model data (moc3)
• Motion data (motion3.json)
• Model settings file (model3.json)
• Physics settings file (physics3.json)
• Display auxiliary file (cdi3.json)
&lt;/pre&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;VR chatting chatters .VRML models - standardized 3D file format for VR avatars 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;V-tubers V-tubing like Vseeface with Openseeface tracker or Vpuppr (virtual puppet project) for online live 2d / 3d art models rigging rigged LIV 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt; 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|}

&lt;nowiki&gt;*&lt;/nowiki&gt; Commercial product.

[[#top|...to the top]]


==Misc Application==
{|  class=&quot;wikitable sortable&quot; 
|- 
!width:30%;|Misc Application
!width:10%;|AROS(x86)
!width:10%;|Commodore-Amiga OS 3.1 (68k)
!width:10%;|Hyperion OS4(PPC)
!width:10%;|MorphOS(PPC)
|-
|&lt;!--Sub Menu--&gt;File Management 
|&lt;!--AROS--&gt;DOpus4, [https://github.com/BlitterStudio/dopus5 DOpus Magellan aka DOpus 5], [ Scalos], [ ], 
|&lt;!--Amiga OS--&gt;DOpus2, DOpus 4, [https://github.com/BlitterStudio/dopus5 Dopus5 Magellan], ClassAction, FileMaster, [http://www.amiga.org/forums/showthread.php?t=4897 DirWork 2]*, [https://github.com/RudolphRiedel/DiskMaster2 DiskMaster2 src], 
|&lt;!--AmigaOS4--&gt;DOpus4, [https://github.com/BlitterStudio/dopus5 Dopus5 Magellan], Filer, AmiDisk 
|&lt;!--MorphOS--&gt;DOpus4, [https://github.com/BlitterStudio/dopus5 Dopus5 Magellan], 
|-
|&lt;!--Sub Menu--&gt;File Verification / Repair 
|&lt;!--AROS--&gt;md5 (works in linux compiling shell), [http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/filetool workpar2] (PAR2),  [http://zakalwe.fi/~shd/foss/cksfv/files/ compile cksfv from website], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;Par2, 
|-
|Application Installer 
|&lt;!--AROS--&gt;[], [ InstallerNG], 
|&lt;!--Amiga OS--&gt;InstallerNG, Grunch, 
|&lt;!--AmigaOS4--&gt;Jack
|&lt;!--MorphOS--&gt;Jack 
|-
|&lt;!--Sub Menu--&gt;Compression archiver [https://github.com/FS-make-simple/paq9a paq9a], [], 
|&lt;!--AROS--&gt;XAD system is a toolkit designed for handling various file and disk archiver
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;[https://aminet.net/package/util/pack/decrunchmania_os4 Crunchmania CrM2 depacker], 
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Binary Hexadecimal Editor 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=development/edit Zaphod], [],
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Repository
|&lt;!--AROS--&gt;[ Git]
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;Git
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Filesystem Partition Editor formatter Disk Management
|&lt;!--AROS--&gt;[https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=1440&amp;highlight=partition&amp;pid=8821#post_8821 QuickPart], [ HDToolBox]
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Filesystem Repair and backups 
|&lt;!--AROS--&gt;ArSFSDoctor, 
|&lt;!--Amiga OS--&gt;[https://aminet.net/package/disk/bakup/quarterback_src Quarterback Tools C and asm src], [ ], [ ], [ ], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;System Disk check, integrity and history [https://github.com/smartmontools/smartmontools smart tools], [], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;[], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Multiple File renaming
|&lt;!--AROS--&gt;DOpus 4 or 5, 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Anti Virus
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;VChecker, 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Random Wallpaper Desktop changer [ DOpus5], [ Scalos],  
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Alarm Clock, Timer, Stopwatch, Countdown 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/workbench DClock], [http://aminet.net/util/time/AlarmClockAROS.lha AlarmClock], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Fortune Cookie Quotes Sayings 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/misc AFortune], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;C/C++ IDE 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/text/edit FrexxEd], [https://github.com/vidarh/FrexxEd FrexxEd src], Annotate, Murks, 
|&lt;!--Amiga OS--&gt;[http://devplex.awardspace.biz/cubic/index.html Cubic IDE]*, Annotate, 
|&lt;!--AmigaOS4--&gt;CodeBench , [https://gitlab.com/boemann/codecraft CodeCraft], 
|&lt;!--MorphOS--&gt;[http://devplex.awardspace.biz/cubic/index.html Cubic IDE]*, Anontate, 
|-
|&lt;!--Sub Menu--&gt;Computer Languages Translation [https://tetracorp.github.io/guide/reverse-engineering-amiga.html ], [https://amigasourcecodepreservation.gitlab.io/amiga-assembler-insider-guide/ ], [https://github.com/kermitfrog/Amiga-Re-Engineering Rust, Ghidra and FS-UAE], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;[https://bitbucket.org/rhinoid/convert68000toc/src/main/ convert m68k seka asm-one to c], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Gui Creators
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=development/guitool MuiBuilder], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;[ MuiBuilder],  
|-
|&lt;!--Sub Menu--&gt;Catalog .cd .ct Editors 
|&lt;!--AROS--&gt;FlexCat
|&lt;!--Amiga OS--&gt;[http://www.geit.de/deu_simplecat.html SimpleCat], FlexCat
|&lt;!--AmigaOS4--&gt;[http://aminet.net/package/dev/misc/simplecat SimpleCat], FlexCat
|[http://www.geit.de/deu_simplecat.html SimpleCat], FlexCat
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|}

&lt;nowiki&gt;*&lt;/nowiki&gt; Commercial product.


==Misc Application 2==
{|  class=&quot;wikitable sortable&quot; 
|- 
!width:30%;|Misc Application
!width:10%;|AROS(x86)
!width:10%;|Commodore-Amiga OS 3.1(68k)
!width:10%;|Hyperion OS4(PPC)
!width:10%;|MorphOS(PPC)
|-
|&lt;!--Sub Menu--&gt;System 
|&lt;!--AROS--&gt;[ SysExplorer], [ SysMon], [ Scout], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;OSK On Screen Keyboard
|&lt;!--AROS--&gt;[], 
|&lt;!--Amiga OS--&gt;[https://aminet.net/util/wb/OSK.lha OSK]
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Screen Magnifier Magnifying Glass Magnification 
|&lt;!--AROS--&gt;[http://www.onyxsoft.se/files/zoomit.lha ZoomIT], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Comic Book CBR CBZ format reader viewer 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/viewer comics], [http://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/viewer comicon], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Ebook Reader 
|&lt;!--AROS--&gt;[https://blog.alb42.de/programs/#legadon Legadon EPUB],[]
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Ebook Converter 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Text to Speech tts [https://github.com/JonathanFly/bark-installer Bark], [], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=audio/misc flite], 
|&lt;!--Amiga OS--&gt;[http://www.text2speech.com translator], 
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=search&amp;tool=simple FLite]
|&lt;!--MorphOS--&gt;[http://se.aminet.net/pub/aminet/mus/misc/ FLite]
|-
|&lt;!--Sub Menu--&gt;Speech Voice Recognition Dictation - [http://sourceforge.net/projects/cmusphinx/files/ CMU Sphinx], [http://julius.sourceforge.jp/en_index.php?q=en/index.html Julius], [http://www.isip.piconepress.com/projects/speech/index.html ISIP], 
|&lt;!--AROS--&gt; 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Speech Voice Changer [], [], [], [], 
|&lt;!--AROS--&gt; 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Screen Display Blanker screensaver 
|&lt;!--AROS--&gt;Blanker Commodity (built in), [https://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/screenblanker GarshneBlanker], [http://sourceforge.net/projects/gblanker/ GBlanker Src], [], 
|&lt;!--Amiga OS--&gt;MultiCX, 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;ModernArt Blanker, 
|-
|}


==Misc Application 3==
{|  class=&quot;wikitable sortable&quot; 
|- 
!width:30%;|Misc Application
!width:10%;|AROS(x86)
!width:10%;|Commodore-Amiga OS 3.1(68k)
!width:10%;|Hyperion OS4(PPC)
!width:10%;|MorphOS(PPC)
|-
|&lt;!--Sub Menu--&gt;Fractals mandelbrot, etc 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/misc ], 
|&lt;!--Amiga OS--&gt;ZoneXplorer, 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Landscape Rendering 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=graphics/raytrace WCS World Construction Set], 
|&lt;!--Amiga OS--&gt;[ Vista Pro], [http://en.wikipedia.org/wiki/World_Construction_Set World Construction Set]
|&lt;!--AmigaOS4--&gt;[ WCS World Construction Set],
|&lt;!--MorphOS--&gt;[ WCS World Construction Set],
|-
|&lt;!--Sub Menu--&gt;Astronomy [https://sourceforge.net/projects/skychart/ skychart freepascal], [], [], 
|&lt;!--AROS--&gt;[ Digital Almanac (ABIv0 only)], 
|&lt;!--Amiga OS--&gt;[http://aminet.net/search?query=planetarium Aminet search], [http://aminet.net/misc/sci/DA3V56ISO.zip Digital Almanac], [https://aminet.net/package/misc/sci/da3sourceV58 Src c V58], [ Galileo renamed to Distant Suns]*, [], 
|&lt;!--AmigaOS4--&gt;[http://sourceforge.net/projects/digital-almanac/ Digital Almanac], Distant Suns*, [http://www.digitaluniverse.org.uk/ Digital Universe]*,
|&lt;!--MorphOS--&gt;[http://www.aminet.net/misc/sci/da3.lha Digital Almanac], [http://www.aminet.net/package/misc/sci/da3-mos-src Src c V56], 
|-
|&lt;!--Sub Menu--&gt;Astrology [https://sourceforge.net/projects/skylendar/ skylendar], [https://github.com/CruiserOne/Astrolog Astrolog], [https://www.astrolog.org/astrolog/astfile.htm Astrology alt site], [https://saravali.github.io/download.html Maitreya], [https://github.com/alamahant/Asteria Asteria], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;PCB design
|&lt;!--AROS--&gt; 
|&lt;!--Amiga OS--&gt;[ ], [ ], [ ], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Digital Signage
|&lt;!--AROS--&gt;Hollywood, Hollywood Designer 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Genealogy History Family Tree Ancestry Records (FreeBMD, FreeREG, and FreeCEN file formats or GEDCOM GenTree)
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt; [ Origins], [ Your Family Tree], [ ], [ ], [ ], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Languages 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;Fun School, 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Mathematics ([http://www-fourier.ujf-grenoble.fr/~parisse/install_en.html Xcas], etc.), 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/scientific mathX] 
|&lt;!--Amiga OS--&gt;Maple V, mathX, Fun School, GCSE Maths, [ ], [ ], [ ], 
|&lt;!--AmigaOS4--&gt;Yacas 
|&lt;!--MorphOS--&gt;Yacas 
|-
|&lt;!--Sub Menu--&gt;Maths Graph Function Plotting
|&lt;!--AROS--&gt;[https://blog.alb42.de/programs/#MUIPlot MUIPlot], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;App Utility Launcher Dock toolbar  
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=utility/docky BoingBar], [], 
|&lt;!--Amiga OS--&gt;[https://github.com/adkennan/DockBot Dockbot],
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;3D Printer [https://github.com/OrcaSlicer/OrcaSlicer OrcaSlicer]
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;BASIC Computer Language 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=development/language Basic4SDL], [ Ace Basic], [ X-AMOS], [SDLBasic], [ Alvyn], 
|&lt;!--Amiga OS--&gt;[http://www.amiforce.de/main.php Amiblitz 3], [http://amos.condor.serverpro3.com/AmosProManual/contents/c1.html Amos Pro], [http://aminet.net/package/dev/basic/ace24dist ACE Basic], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;sdlBasic
|-
|&lt;!--Sub Menu--&gt;HAM radio, amateur radio, packet radio  [], [], [], [https://cemaxecuter.com/ Dragon OS], [https://github.com/km4ack/73Linux with 73 link update], [https://www.youtube.com/watch?v=YAL5KNePRSg video for], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;[https://www.amigarealm.com/amiga/amicomms/comm4.htm Comm4], [https://www.amigarealm.com/archives/comms/aarug/ TNC Terminal Node Controller with packets over serial connections on Yaesu or Woxum handheld], [https://aminet.net/comm/misc AmiCom], [ with 7Plus file encoder/decoder], [ mksstv], [ RTTYam], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|}

&lt;nowiki&gt;*&lt;/nowiki&gt; Commercial product.


==Games &amp; Emulation==

Some emulators/games require OpenGL to function and to adjust ahi prefs channels, frequency and unit0 and unit1 and 
[http://aros.sourceforge.net/documentation/users/shell/changetaskpri.php changetaskpri -1]

Rom patching  https://www.marcrobledo.com/RomPatcher.js/ https://www.romhacking.net/patch/ (ips, ups, bps, etc) and this other site supports the latter formats https://hack64.net/tools/patcher.php 

Free public domain roms for use with emulators can be found [http://www.pdroms.de/ here] as most of the rest are covered by copyright rules. If you like to read about old games see [http://retrogamingtimes.com/ here] and [http://www.armchairarcade.com/neo/ here] and a [http://www.vintagecomputing.com/ blog] about old computers. Possibly some of the [http://www.answers.com/topic/list-of-best-selling-computer-and-video-games best selling] of all time. [http://en.wikipedia.org/wiki/List_of_computer_system_emulators Wiki] with emulated systems list.

[https://archive.gamehistory.org/ Archive of VGHF], [https://library.gamehistory.org/ Video Game History Foundation Library search]


{|  class=&quot;wikitable sortable&quot; 
|- 
!width:10%;|Games [http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer Emulation]
!width:10%;|AROS(x86)
!width:10%;|AmigaOS3(68k)
!width:10%;|AmigaOS4(PPC)
!width:10%;|MorphOS(PPC)
|-
|&lt;!--Sub Menu--&gt;Games Emulation Amstrad CPC 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer], [ Caprice32 (OpenGL &amp; pure SDL)], [ Arnold], [https://retroshowcase.gr/cpcbox-master/], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;[http://os4depot.net/index.php?function=browse&amp;cat=emulation/computer]
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=2], 
|-
|&lt;!--Sub Menu--&gt;Games Emulation Apple2 and 2GS
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Arcade 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/gamesystem Mame], [ SI Emu (ABIv0 only)], 
|&lt;!--Amiga OS--&gt;Mame, 
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/gamesystem xmame], amiarcadia, 
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=2 Mame], 
|-
|&lt;!--Sub Menu--&gt;Games Emulation Atari 2600 [], [], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/gamesystem Stella], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Atari 5200 [https://github.com/wavemotion-dave/A5200DS A5200DS], [], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Atari 7800
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Atari 400 800 130XL [https://github.com/wavemotion-dave/A8DS A8DS], [], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer Atari800], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Atari Lynx
|&lt;!--AROS--&gt;[http://myfreefilehosting.com/f/6366e11bdf_1.93MB Handy (ABIv0 only)], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Atari Jaguar
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Bandai Wonderswan 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation BBC Micro and Acorn Electron [http://beehttps://bem-unix.bbcmicro.com/download.html BeebEm], [http://b-em.bbcmicro.com/ B-Em], [http://elkulator.acornelectron.co.uk/ Elkulator], [http://electrem.emuunlim.com/ ElectrEm], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Dragon 32 and Tandy CoCo [http://www.6809.org.uk/xroar/ xroar], [], 
|&lt;!--AROS--&gt;[], [], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Commodore C16 Plus4
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Commodore C64
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer Vice (ABIv0 only)], [], 
|&lt;!--Amiga OS--&gt;Frodo, 
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/gamesystem viceplus], 
|&lt;!--MorphOS--&gt;Vice, 
|-
|&lt;!--Sub Menu--&gt;Games Emulation Commodore Amiga
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer Janus UAE], Emumiga, 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;[http://os4depot.net/index.php?function=browse&amp;cat=emulation/computer UAE], 
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=2 UAE], 
|-
|&lt;!--Sub Menu--&gt;Games Emulation Japanese MSX MSX2 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Mattel Intelivision
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Mattel Colecovision and Adam
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Milton Bradley (MB) Vectrex [ Vectrex OpenGL], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation PICO8 Pico-8 fantasy video game console [https://github.com/egordorichev/pemsa-sdl/ pemsa-sdl], [https://github.com/jtothebell/fake-08 fake-08], [https://github.com/Epicpkmn11/fake-08/tree/wip fake-08 fork], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Nintendo Gameboy
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/gamesystem vba no sound], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/gamesystem vba]
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Nintendo NES
|&lt;!--AROS--&gt;[ EmiNES], [http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/gamesystem Fceu], [https://github.com/takahirox/nes-js?tab=readme-ov-file nes-js], [https://github.com/bfirsh/jsnes jsnes], [https://github.com/angelo-wf/NesJs NesJs], 
|&lt;!--Amiga OS--&gt;AmiNES, [http://www.dridus.com/~nyef/darcnes/ darcNES], 
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/gamesystem amines]
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Nintendo SNES
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/gamesystem Zsnes], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/gamesystem warpsnes]
|&lt;!--MorphOS--&gt;[http://fabportnawak.free.fr/snes/ Snes9x], 
|-
|&lt;!--Sub Menu--&gt;Games Emulation Nintendo N64 
*HLE and plugins [ mupen64], [https://github.com/ares-emulator/ares ares], [https://github.com/N64Recomp/N64Recomp N64Recomp], [https://github.com/rt64/rt64 rt64], [https://github.com/simple64/simple64 Simple64], 
*LLE [], 
|&lt;!--AROS--&gt;[http://code.google.com/p/mupen64plus/ Mupen64+],
|&lt;!--Amiga OS--&gt;[http://code.google.com/p/mupen64plus/ Mupen64+], [http://aminet.net/package/misc/emu/tr-981125_src TR64], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;[ Nintendo Gamecube Wii]
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;[ Nintendo Wii U]
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;[https://github.com/yuzu-emu Nintendo Switch]
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation NEC PC Engine 
|&lt;!--AROS--&gt;[], [], [https://github.com/yhzmr442/jspce js-pce], 
|[http://www.hugo.fr.fm/ Hugo], [http://mednafen.sourceforge.net/ Mednafen], 
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/gamesystem tgemu]
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Sega Master System (SMS)
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/gamesystem Dega], [http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/gamesystem sms], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/gamesystem osmose]
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Sega Genesis/Megadrive
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/gamesystem gp no sound], [http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/gamesystem DGen], 
|&lt;!--Amiga OS--&gt;[http://code.google.com/p/genplus-gx/ Genplus], 
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/gamesystem genesisplus]
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Sega Saturn 
*HLE [https://mednafen.github.io/ mednafen], [http://yabause.org/ yabause], [], 
*LLE [], [], 
|&lt;!--AROS--&gt;?
|&lt;!--Amiga OS--&gt;[http://yabause.org/ Yabause], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Sega Dreamcast 
*HLE [https://github.com/flyinghead/flycast  flycast], [https://code.google.com/archive/p/nulldc/downloads NullDC], 
*LLE [], [], 
|&lt;!--AROS--&gt;?
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Sinclair ZX80 and ZX81 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer], [], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Sinclair Spectrum 
|[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer Fuse (crackly sound)], [http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer SimCoupe], [ FBZX slow], [https://jsspeccy.zxdemo.org/ jsspeccy], [http://torinak.com/qaop/games qaop], 
|&lt;!--Amiga OS--&gt;[http://www.lasernet.plus.com/ Asp], [http://www.zophar.net/sinclair.html Speculator], [http://www.worldofspectrum.org/x128/index.html X128], 
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/computer]
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Sinclair QL
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer], [], 
|&lt;!--Amiga OS--&gt;[http://aminet.net/package/misc/emu/QDOS4amiga1 QDOS4amiga]
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation SNK NeoGeo Pocket
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/gamesystem], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/gamesystem gngeo], NeoPop, 
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation Sony PlayStation
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/gamesystem FPSE], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/gamesystem FPSE]
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;[ Sony PS2]
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;[ Sony PS3]
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;[https://vita3k.org/ Sony Vita]
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;[https://github.com/shadps4-emu/shadPS4 PS4]
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation [http://en.wikipedia.org/wiki/Tangerine_Computer_Systems Tangerine] Oric and Atmos 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer Oricutron]
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;[http://www.os4depot.net/index.php?function=browse&amp;cat=emulation/gamesystem Oricutron]
|&lt;!--MorphOS--&gt;[http://aminet.net/package/misc/emu/oricutron Oricutron]
|-
|&lt;!--Sub Menu--&gt;Games Emulation TI 99/4 99/4A [https://github.com/wavemotion-dave/DS994a DS994a], [], [https://js99er.net/#/ js99er], [], [http://aminet.net/package/misc/emu/TI4Amiga TI4Amiga], [http://aminet.net/package/misc/emu/TI4Amiga_src TI4Amiga src in c], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=emulation/computer], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation HP 38G 40GS 48 49G/50G Graphing Calculators
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Emulation TI 58 83 84 85 86 - 89 92 Graphing Calculators
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|}

{|  class=&quot;wikitable sortable&quot; 
|- 
!width:10%;|Games [https://www.rockpapershotgun.com/ General]
!width:10%;|AROS(x86)
!width:10%;|AmigaOS3(68k)
!width:10%;|AmigaOS4(PPC)
!width:10%;|MorphOS(PPC)
|- style=&quot;background:lightgrey; text-align:center; font-weight:bold;&quot;
| Games [https://www.trackawesomelist.com/michelpereira/awesome-open-source-games/ Open Source and others] || AROS || Amiga OS || Amiga OS4 || Morphos 
|-
|&lt;!--Sub Menu--&gt;Games Action like [https://github.com/opentomb/OpenTomb opentomb], [https://github.com/LostArtefacts/TRX TRX formerly Tomb1Main], [https://github.com/TombEngine TombEngine], [http://archives.arosworld.org/index.php?function=browse&amp;cat=game/action Thrust], [https://github.com/fragglet/sdl-sopwith sdl sopwith], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=game/action], [https://archives.arosworld.org/index.php?function=browse&amp;cat=game/action BOH], [], 
|&lt;!--Amiga OS--&gt;[https://github.com/BSzili/OpenLara/tree/amiga/src source of openlara SDL2], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Adventure like [http://dotg.sourceforge.net/ DMJ], [https://github.com/kromenak/gengine Gabriel Knight 3], [http://www.sarien.net/ Sierra Sarien], [https://github.com/klembot/twinejs twine js], [https://github.com/QSPFoundation/qspgui Quest Soft Player QSP], [], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=game/adventure dmagnetic], [https://archives.arosworld.org/?function=browse&amp;cat=emulation/misc ScummVM], [https://archives.arosworld.org/index.php?function=browse&amp;cat=game/roleplaying frotz infocom], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Board like [https://github.com/aperture-software/colditz-escape escape from colditz], [], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=game/board], [http://amigan.1emu.net/releases Africa]
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Cards 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=game/card ], [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=1443&amp;rowstart=180&amp;pid=12934#post_12934 Balatro], 
|&lt;!--AmigaOS--&gt;[http://home.arcor.de/amigasolitaire/e/welcome.html Reko], [https://github.com/samskivert/beschei-en beschei Src], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Misc [https://github.com/michelpereira/awesome-open-source-games Awesome open], [https://github.com/bobeff/open-source-games General Open Source], [https://github.com/SAT-R/sa2 Sonic Advance 2], [https://github.com/velorek1/cwordle Wordle type], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=game/misc], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games FPS like [https://aminet.net/package/game/shoot/D1X_Rebirth_AGA Descent D1X src], [https://github.com/DescentDevelopers/Descent3 Descent 3], [https://github.com/Fewnity/Counter-Strike-Nintendo-DS Counter-Strike-Nintendo-DS], [https://github.com/Aleph-One-Marathon/alephone Bungie Marathon 1994], [https://zdoom.org/downloads UzDoom opengl 3.3], [https://github.com/ZDoom/gzdoom gzdoom opengl 3+], [https://zdoom.org/downloads LZDoom opengl 2.1], 
|&lt;!--AROS--&gt;Doom, Quake, [http://archives.arosworld.org/index.php?function=browse&amp;cat=game/fps Quake 3 Arena (OpenGL)], [http://archives.arosworld.org/index.php?function=browse&amp;cat=game/fps Cube (OpenGL)], [http://archives.arosworld.org/index.php?function=browse&amp;cat=game/fps Assault Cube (OpenGL)], [http://archives.arosworld.org/index.php?function=browse&amp;cat=game/fps Cube 2 Sauerbraten (OpenGL)], [http://fodquake.net/test/ FodQuake QuakeWorld], [https://archives.arosworld.org/index.php?function=browse&amp;cat=game/fps Duke Nukem 3D], [https://archives.arosworld.org/index.php?function=browse&amp;cat=game/fps Darkplaces Nexuiz Xonotic], [http://archives.arosworld.org/index.php?function=browse&amp;cat=game/fps Doom 3 SDL (OpenGL)], [http://archives.arosworld.org/index.php?function=browse&amp;cat=game/fps Hexenworld and Hexen 2], [https://archives.arosworld.org/index.php?function=browse&amp;cat=game/fps Aliens vs Predator Gold 2000 avp (openGL)], [https://archives.arosworld.org/index.php?function=browse&amp;cat=game/fps Odamex (openGL doom)], [https://archives.arosworld.org/?function=showfile&amp;file=game/fps/ zgloom], [], [https://archives.arosworld.org/?function=showfile&amp;file=game/fps/ ab3dhd], [], 
|&lt;!--Amiga OS--&gt;Doom, Quake, AB3D, Fears, Breathless, Gloom, 
|&lt;!--AmigaOS4--&gt;Doom, Quake, 
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=12 Doom], Quake, Quake 3 Arena, [https://github.com/OpenXRay/xray-16 S.T.A.L.K.E.R Xray]
|-
|&lt;!--Sub Menu--&gt;Games MMORG like 
|&lt;!--AROS--&gt;[ Eternal Lands (OpenGL)],
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Platform like 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=game/platform], [ Maze of Galious], [ Gish]*(openGL), [ Mega Mario], [https://archives.arosworld.org/?function=showfile&amp;file=game/platform/ thextech SMBX], [http://www.gianas-return.de/ Giana's Return], [http://www.sqrxz.de/ Sqrxz], [www.sqrxz2.de/ Sqrxz 2], [http://www.sqrxz.de/sqrxz-3/ Sqrxz 3], [http://www.sqrxz.de/sqrxz-4/ Sqrxz 4], [http://archives.arosworld.org/index.php?function=browse&amp;cat=game/platform Cave Story], [https://bszili.morphos.me/ Frogatto], [https://bszili.morphos.me/ OpenJazz], [https://archives.arosworld.org/?function=showfile&amp;file=game/platform/ pekkakana2], [ Aquaria], [https://archives.arosworld.org/?function=showfile&amp;file=game/platform/ sonic CD], [], 
|&lt;!--Amiga OS--&gt;[ Giana Sisters], [], 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Puzzle [https://github.com/mariopartyrd/marioparty4/tree/port Party], [https://github.com/mdodis/OpenSolomonsKey OpenSolomonsKey], [], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=game/puzzle], [ Cubosphere (OpenGL)], [http://archives.arosworld.org/index.php?function=browse&amp;cat=game/puzzle Candy Crisis], [http://bszili.morphos.me/ TailTale], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Racing [ Trigger Rally], [ VDrift], [http://www.ultimatestunts.nl/index.php?page=2&amp;lang=en Ultimate Stunts], [http://maniadrive.raydium.org/ Mania Drive], [https://github.com/plowteam/donut Simpsons Hit and Run], [], 
|&lt;!--AROS--&gt;[ Super Tux Kart (OpenGL)], [http://www.dusabledanslherbe.eu/AROSPage/F1Spirit.30.html F1 Spirit (OpenGL)], [http://bszili.morphos.me/index.html MultiRacer], [https://bszili.morphos.me/ Speed Dreams], [https://archives.arosworld.org/?function=showfile&amp;file=game/driving/dethrace-0.10.1.x86_64-aros-v11.zip Carmageddon dethrace 64bit], [], 
|&lt;!--AmigaOS--&gt;
|&lt;!--AmigaOS4--&gt;[http://bszili.morphos.me/index.html Speed Dreams], 
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=12], [http://bszili.morphos.me/index.html TORCS], 
|-
|&lt;!--Sub Menu--&gt;Games 1st first person DRPG [https://wiki.rpg.net/index.php/Open_Game_Systems Misc], [https://github.com/OpenEnroth/OpenEnroth OpenEnroth MM], []
|&lt;!--AROS--&gt;[https://github.com/BSzili/aros-stuff Arx Libertatis], [http://www.playfuljs.com/a-first-person-engine-in-265-lines/ js raycaster], [https://github.com/Dorthu/es6-crpg webgl], [https://github.com/sonountaleban/AmiShockolate System Shock], [], [], 
|&lt;!--AmigaOS--&gt;Phantasie, Faery Tale, Dungeon Master, 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games 3rd third person action CRPG  [https://sourceforge.net/projects/sumwars/ Summoning Wars], [https://www.solarus-games.org/ Solarus], [https://wiki.rpg.net/index.php/Open_Game_Systems Misc], [https://github.com/alexbatalov/fallout1-ce fallout ce], [https://github.com/rwengine/openrw gta3], [https://github.com/gta-reversed/gta-reversed gta3 sa], [https://github.com/mrxenginner/reVC gta3 vc revc], 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/?function=showfile&amp;file=game/strategy/ fheroes2 homm2], [https://archives.arosworld.org/?function=showfile&amp;file=game/roleplaying/ breakhack], [https://archives.arosworld.org/?function=showfile&amp;file=game/roleplaying/ devilutionx diablo 1 hellfire], [https://archives.arosworld.org/?function=showfile&amp;file=game/roleplaying/ fallout 1], [https://archives.arosworld.org/?function=showfile&amp;file=game/strategy/ stratagus], [https://archives.arosworld.org/?function=showfile&amp;file=game/strategy/ hostile-takeover], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games isometric RPG [https://sourceforge.net/projects/sumwars/ Summoning Wars], [https://www.solarus-games.org/ Solarus], [https://wiki.rpg.net/index.php/Open_Game_Systems Misc], [https://github.com/topics/dungeon?l=javascript Dungeon], [], [https://github.com/clintbellanger/heroine-dusk JS Dusk], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=game/roleplaying nethack], [https://archives.arosworld.org/index.php?function=browse&amp;cat=game/roleplaying GemRB], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games card based RPG [https://github.com/open-duelyst/duelyst Duelyst], [], [], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games turn based tactics RPG [], [], [], [], [], [], 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=game/strategy UFO AI], [http://play.freeciv.org/ FreeCiv], [], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Strategy [http://rtsgus.org/ RTSgus], [http://stargus.sourceforge.net/ Stargus], [https://github.com/KD-lab-Open-Source/Perimeter Perimeter], [https://matty77.itch.io/conflict-3049 conflict-3049], [], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=game/strategy MegaGlest (OpenGL)], [https://archives.arosworld.org/?function=showfile&amp;file=game/strategy/ signus], [https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=1443&amp;rowstart=140&amp;pid=12446#post_12446 Wargus warcraft 2 setup], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=12]
|-
|&lt;!--Sub Menu--&gt;Games Rhythm, Beat, Step [], [], [https://clonehero.net/ clonehero], [https://github.com/MatteoGodzilla/Dj-Engine Dj-Engine], 
|&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=game/misc Frets on Fire], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Shoot Em Ups [http://www.mhgames.org/oldies/formido/ Formido], [http://code.google.com/p/violetland/ Violetland], 
||&lt;!--AROS--&gt;[https://archives.arosworld.org/index.php?function=browse&amp;cat=game/action Open Tyrian], [http://www.parallelrealities.co.uk/projects/starfighter.php Starfighter], [ Alien Blaster], [https://github.com/OpenFodder/openfodder OpenFodder], [https://archives.arosworld.org/?function=showfile&amp;file=game/action/ tbftss The Battle for the Solar System: the Pandora War]
|&lt;!--AmigaOS--&gt;
|&lt;!--AmigaOS4--&gt;[http://www.parallelrealities.co.uk/projects/starfighter.php Starfighter], [ The Battle for the Solar System: the Pandora War]
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Simulations [http://scp.indiegames.us/ Freespace 2], [http://www.heptargon.de/gl-117/gl-117.html GL117], [http://code.google.com/p/corsix-th/ Theme Hospital], [http://code.google.com/p/freerct/ Rollercoaster Tycoon], [http://hedgewars.org/ Hedgewars], [https://github.com/raceintospace/raceintospace raceintospace], [https://github.com/Return-To-The-Roots RTTR Settlers 2], [https://github.com/OoliteProject/oolite oolite elite], [https://github.com/fesh0r/newkind newkind elite], [], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;SimCity, SimAnt, Sim Hospital, Theme Park, 
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;[http://morphos.lukysoft.cz/en/vypis.php?kat=12]
|-
|&lt;!--Sub Menu--&gt;Games Life Sim [https://github.com/ACreTeam/forest Animal Crossing], [ ], [], [], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Horror [https://github.com/Mikompilation/MikuPan Fatal Frame], [ ], [], [], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Sandbox Voxel Open World Exploration [https://github.com/ClassiCube/ Classicube],[http://www.michaelfogleman.com/craft/ Craft], [https://github.com/tothpaul/DelphiCraft DelphiCraft],[https://www.minetest.net/ Luanti formerly Minetest], [ infiniminer], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Battle Royale [https://bruh.io/ Play.Bruh.io], [https://www.coolmathgames.com/0-copter Copter Royale], [https://surviv.io/ Surviv.io], [https://nuggetroyale.io/#Ketchup Nugget Royale], [https://miniroyale2.io/ Miniroyale2.io], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Tower Defense [https://chriscourses.github.io/tower-defense/ HTML5], [https://github.com/SBardak/Tower-Defense-Game TD C++], [https://github.com/bdoms/love_defense LUA and LOVE], [https://github.com/HyOsori/Osori-WebGame HTML5], [https://github.com/PascalCorpsman/ConfigTD ConfigTD Pascal], [https://github.com/GloriousEggroll/wine-ge-custom Wine], []
|&lt;!--AROS--&gt;[https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=1443&amp;rowstart=180&amp;pid=12871#post_12871 Plants vs Zombies PvZ], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Visual Novel Engines [https://github.com/diane1f0cd/VisualNovelTemplate Visual Novel Template], [https://github.com/Kirilllive/tuesday-js Tuesday JS], [https://github.com/tejasnayak25/vnsutra vnsutra], [https://github.com/weetabix-su/renpsp-dev RenPSP], [https://github.com/Galladite27/ONScripter-EN ONScripter-EN], [https://github.com/NathanGuilhot/VNES-Raylib https://github.com/NathanGuilhot/VNES VNES in Raylib], [https://www.renpy.org/latest.html renpy ren'py python based], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Virtual Reality VR [https://gitlab.com/madsbuvi/openmw openmw vr], [https://github.com/Team-Beef-Studios/BeefRaiderXR BeefRaiderXR], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Virtual Table Top VTT [ Roll20], [https://www.owlbear.rodeo/ owlbear rodeo], [], [], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Computer assisted TableTop TTRPG OSR [https://www.rpgsolo.com/play.php RPGSolo], [https://github.com/fpsvogel/solo-ttrpgs Solo TTRPG], [], [], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games 2D 3D Engines [https://github.com/fegennari/3DWorld 3DWorld], [https://github.com/GarageGames/Torque3D Torque3D], [https://github.com/gameplay3d/GamePlay GamePlay 3D],  [https://www.babylonjs.com/ BabylonJS ], [ Godot], [ Ogre], [ Crystal Space], [https://github.com/JacobHess03/ Dragon-Quest like], [https://github.com/bjornbytes/lovr Lua LOVE for 2D LOVR for 3D], [], 
|&lt;!--AROS--&gt;[https://www.arkhamdev.net/wiki.htm?id=agx Arkham Development antiryadgx 8.9 lts with register], [], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games C based game frameworks [https://github.com/orangeduck/Corange Corange], [https://github.com/scottcgi/Mojoc Mojoc], [https://orx-project.org/ Orx], [https://github.com/ioquake/ioq3 Quake 3], [https://www.mapeditor.org/ Tiled], [https://www.raylib.com/ 2d Raylib], [https://github.com/Rabios/awesome-raylib other raylib], [https://github.com/MrFrenik/gunslinger Gunslinger], [https://o3de.org/ o3d], [http://archives.aros-exec.org/index.php?function=browse&amp;cat=development/library GLFW], [], 
|&lt;!--AROS--&gt;[http://archives.arosworld.org/index.php?function=browse&amp;cat=development/library Raylib 5], 
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games RPGMaker MV/MZ-compatible projects [https://github.com/Psychronic-Games/RPGReactor RPGReactor js],
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games Virtual Pinball [https://github.com/vpinball/vpinball vpinball], [], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|-
|&lt;!--Sub Menu--&gt;Games unpack unarc [], [], 
|&lt;!--AROS--&gt;
|&lt;!--Amiga OS--&gt;
|&lt;!--AmigaOS4--&gt;
|&lt;!--MorphOS--&gt;
|}


==Application Guides==

[[#top|...to the top]]

===Web Browser===

OWB is now at version 2.0 (which got an engine refresh, from July 2015 to February 2019) and 3.0.

This latest version has a good support for many/most web sites, even YouTube web page now works. 

This improved compatibility comes at the expense of higher RAM usage (now 1GB RAM is the absolute minimum). 

Also, keep in mind that the lack of a JIT (Just-In-Time) JS compiler on the 32 bit version, makes the web surfing a bit slow. 

Only the 64 bit version of OWB 2.0 will have JIT enabled, thus benefitting of more speed. There are tooltypes that can be added to the icon to provide further features JIT, MSE etc 


Certificates from [https://curl.se/docs/caextract.html ca certs], 


DNS tracking blocking with [https://easylist.to/easylist/easylist.txt easylist.txt] in PROGDIR:Conf before starting browser with enabled AdBlock [https://github.com/easylist/easylist/tree/master easylist], [https://gitlab.com/eyeo anti abp], [https://firebog.net/ big blocklist], [https://github.com/StevenBlack/hosts Steves], [], [], 

This can be enabled with OWB Odyssey with Windows -&gt; Content Blocking and Windows -&gt; Messages and enter 

 https://www.youtube.com/api/stats/ads*
 https://www.youtube.com/pagead/adview*
 https://www.youtube.com#@##player-ads*

into your custom filters 


Element blocker browser extension might be needed for [https://github.com/easylist/easylist/wiki/Youtube-Issues youtube], [ mid roll], [ pre roll], [ ],  


OWB speed is much better when running from RAM Disk, the best way is to add the below into your S:User-Startup which copies OWB drawer from Extras:Internet/OWB to RAM Disk: 

So add this :
&lt;pre&gt;
copy Extras:Internet/OWB Ram:OWB/ ALL CLONE &gt;NIL:
copy Extras:Internet/OWB.info Ram: &gt;NIL:
&lt;/pre&gt;
Open RAM Disk and open OWB drawer and double click on OWB icon so that the above icon tooltypes are activated 

Problems are that the copy time is long (around 20 seconds added in the background), but we can make it faster if we delete useless files from the OWB drawer (docs, …)
If you don’t copy the drawer back onto the HD, you won’t save your cache, cookies, passwords… So you need a script for it.


Error messages 

SSL error &quot;cant verify with ca-certificates&quot;, check bios clock time date is correct 

Error 6, try checking networking prefs settings and Save / Use preferences again or a '''few times''' otherwise the network chipset may not be compatible with Aros 


[https://www.google.com/search?q=%s&amp;udm=14 Google search without AI overview] 


===E-mail===

 YAM does not support SSL and most mail providers now switched to encrypted SMTP/POP3 connections


====SimpleMail====

SimpleMail supports IMAP and appears to work with GMail, but it's never been reliable enough, it can crash with large mailboxes.

Please read more on this [http://www.freelists.org/list/simplemail-usr User list]


 GMail

Be sure to activate the pop3 usage in your gmail account setup / configuration first.

pop3: 
pop.gmail.com
Use SSL: Yes
Port: 995

smtp:
smtp.gmail.com (with authentication)
Use Authentication: Yes
Use SSL: Yes
Port: 465 or 587


 Hotmail/MSN/outlook/Microsoft Mail mid-2017, all outlook.com accounts will be migrated to Office 365 / Exchange

Most users are currently on POP which does not allow showing folders and many other features (technical limitations of POP3). With Microsoft IMAP you will get folders, sync read/unread, and show flags. You still won't get push though, as Microsoft has not turned on the IMAP Idle command as at Sept 2013.

If you want to try it, you need to first remove (you can't edit) your pop account (long-press the account on the accounts screen, delete account). Then set it up this way:

1. Email/Password
2. Manual
3. IMAP
4.

* Incoming: imap-mail.outlook.com, port 993, SSL/TLS should be checked
* Outgoing: smtp-mail.outlook.com, port 587, SSL/TLS should be checked
* POP server name pop-mail.outlook.com, port 995, POP encryption method SSL

 Yahoo  Mail

On April 24, 2002 Yahoo ceased to offer POP access to its free mail service. Introducing instead a yearly payment feature, allowing users POP3 and IMAP server support, along with such benefits as larger file attachment sizes and no adverts.

Sorry to see Yahoo leaving its users to cough up for the privilege of accessing their mail. Understandable, when competing against rivals such as Gmail and Hotmail who hold a large majority of users and were hacked in 2014 as well.


Incoming Mail (IMAP) Server

* Server - imap.mail.yahoo.com
* Port - 993
* Requires SSL - Yes

Outgoing Mail (SMTP) Server

* Server - smtp.mail.yahoo.com
* Port - 465 or 587
* Requires SSL - Yes
* Requires authentication - Yes

Your login info

* Email address - Your full email address (name@domain.com)
* Password - Your account's password
* Requires authentication - Yes


Note that you need to enable “Web &amp; POP Access” in your Yahoo Mail account to send and receive Yahoo Mail messages through any other email program.

You will have to enable “Allow your Yahoo Mail to be POPed” under “POP and Forwarding”, to send and receive Yahoo mails through any other email client.

Cannot be done since 2002 unless the customer pays Yahoo a subscription subs fee to have access to SMTP and POP3

* Set the POP server for incoming mails as pop.mail.yahoo.com. You will have to enable “SSL” and use 995 for Port.
* “Account Name or Login Name” – Your Yahoo Mail ID i.e. your email address without the domain “@yahoo.com”.
* “Email Address” – Your Yahoo Mail address i.e. your email address including the domain “@yahoo.com”. E.g. myname@yahoo.com
* “Password” – Your Yahoo Mail password.

Yahoo! Mail Plus users may have to set POP server as plus.pop.mail.yahoo.com and SMTP server as plus.smtp.mail.yahoo.com.

* Set the SMTP server for outgoing mails as smtp.mail.yahoo.com. You will also have to make sure that “SSL” is enabled and use 465 for port. you must also enable “authentication” for this to work.


====YAM Yet Another Mailer====

 YAM does not support SSL and most mail providers have now switched to encrypted SMTP/POP3 connections

This email client is POP3 only if the SSL library is available [http://www.freelists.org/list/yam YAM Freelists]

One of the downsides of using a POP3 mailer unfortunately - you have to set an option not to delete the mail if you want it left on the server. IMAP keeps all the emails on the server.

Possible issues

Sending mail issues is probably a matter of using your ISP's SMTP server, though it could also be an SSL issue.


getting a &quot;Couldn't initialise TLSv1 / SSL error

Use of on-line e-mail accounts with this email client is not possible as it lacks the OpenSSL AmiSSl v3 compatible library

 GMail 
Incoming Mail (POP3) Server - requires SSL: pop.gmail.com
Use SSL: Yes
Port: 995

Outgoing Mail (SMTP) Server - requires TLS: smtp.gmail.com (use authentication)
Use Authentication: Yes
Use STARTTLS: Yes (some clients call this SSL)
Port: 465 or 587

Account Name: your Gmail username (including '@gmail.com')
Email Address: your full Gmail email address (username@gmail.com)
Password: your Gmail password

Anyway, the SMTP is pop.gmail.com port 465 and it uses SSLLv3 Authentication. The POP3 settings are for the same server (pop.gmail.com), only on port 995 instead.


 Outlook.com access

&lt;pre &gt;
Outlook.com SMTP server address: smtp.live.com
Outlook.com SMTP user name: Your full Outlook.com email address (not an alias)
Outlook.com SMTP password: Your Outlook.com password
Outlook.com SMTP port: 587
Outlook.com SMTP TLS/SSL encryption required: yes 
&lt;/pre &gt;


 Yahoo  Mail

&lt;pre &gt;
“POP3 Server” – Set the POP server for incoming mails as pop.mail.yahoo.com. You will have to enable “SSL” and use 995 for Port.
“SMTP Server” – Set the SMTP server for outgoing mails as smtp.mail.yahoo.com. You will also have to make sure that “SSL” is enabled and use 465 for port. you must also enable “authentication” for this to work.
“Account Name or Login Name” – Your Yahoo Mail ID i.e. your email address without the domain “@yahoo.com”.
“Email Address” – Your Yahoo Mail address i.e. your email address including the domain “@yahoo.com”. E.g. myname@yahoo.com
“Password” – Your Yahoo Mail password.
&lt;/pre &gt;

Yahoo! Mail Plus users may have to set POP server as plus.pop.mail.yahoo.com and SMTP server as plus.smtp.mail.yahoo.com.

Note that you need to enable “Web &amp; POP Access” in your Yahoo Mail account to send and receive Yahoo Mail messages through any other email program.

You will have to enable “Allow your Yahoo Mail to be POPed” under “POP and Forwarding”, to send and receive Yahoo mails through any other email client.

Cannot be done since 2002 unless the customer pays Yahoo a monthly fee to have access to SMTP and POP3


 Microsoft Outlook Express Mail 

1. Get the files to your PC.
By whatever method get the files off your Amiga onto your PC. In the YAM folder you have a number of different folders, one for each of your folders in YAM. Inside that is a file usually some numbers such as 332423.283. YAM created a new file for every single email you received.

2. Open up a brand new Outlook Express. Just configure the account to use 127.0.0.1 as mail servers. It doesn't really matter. You will need to manually create any subfolders you used in YAM.

3. You will need to do a mass rename on all your email files from YAM. Just add a .eml to the end of it. Amazing how PCs still rely mostly on the file name so it knows what sort of file it is rather than just looking at it! There are a number of multiple renamers online to download and free too.

4. Go into each of your folders, inbox, sent items etc. And do a select all then drag the files into Outlook Express (to the relevant folder obviously) Amazingly the file format that YAM used is very compatible with .eml standard and viola your emails appear. With correct dates and working attachments.

5. If you want your email into Microsoft Outlook. Open that up and create a new profile and a new blank PST file. Then go into File Import and choose to import from Outlook Express. And the mail will go into there. And viola.. you have your old email from your Amiga in a more modern day format.


===FTP===

Magellan has a great FTP module. It allows transferring files from/to a FTP server over the Internet or the local network and, even if FTP is perceived as a &quot;thing of the past&quot;, its usability is all inside the client. The FTP thing has a nice side effect too, since every Icaros machine can be a FTP server as well, and our files can be easily transferred from an Icaros machine to another with a little configuration effort.

First of all, we need to know the 'server' IP address. Server is the Icaros machine with the file we are about to download on another Icaros machine, that we're going to call 'client'. To do that, move on the server machine and 1) run Prefs/Services to be sure &quot;FTP file transfer&quot; is enabled (if not, enable it and restart Icaros); 2) run a shell and enter this command:

ifconfig -a

Make a note of the IP address for the network interface used by the local area network. For cabled devices, it usually is net0:. Now go on the client machine and run Magellan:

Perform these actions: 1) click on FTP; 2) click on ADDRESS BOOK; 3) click on &quot;New&quot;. 
You can now add a new entry for your Icaros server machine:

1) Choose a name for your server, in order to spot it immediately in the address book. Enter the IP address you got before.

2) click on Custom Options:


1) go to Miscellaneous in the left menu;

2) Ensure &quot;Passive Transfers&quot; is NOT selected;

3) click on Use. We need to deactivate Passive Transfers because YAFS, the FTP server included in Icaros, only allows active transfers at the current stage. Now, we can finally connect to our new file source:


1) Look into the address book for the newly introduced server, be sure that name and IP address are right, and

2) click on Connect. A new lister with server's &quot;MyWorkspace&quot; contents will appear. You can now transfer files over the network choosing a destination among your local (client's) volumes.

Can be adapted to any FTP client on any platform of your choice, just be sure your client allows Active Transfers as well.


===IRC Internet Relay Chat===

Jabberwocky is ideal for one-to-one social media communication, use IRC if you require one to many. 

Just type a message in ''lowercase''' letters and it will be posted to all in the [ AROS irc channel]. Please do not use UPPER CASE as it is a sign of SHOUTING which is annoying.

Other things to type in - replace &lt;message&gt; with a line of text and &lt;nick&gt; with a person's name

&lt;pre&gt;
/help

/list

/who
/whois &lt;nick&gt;

/msg &lt;nick&gt; &lt;message&gt;

/query &lt;nick&gt; 
&lt;message&gt;s
/query

/away &lt;message&gt;
/away

/quit &lt;going away message&gt; 
&lt;/pre&gt;


[http://irchelp.org/irchelp/new2irc.html#smiley Intro guide here]. IRC Primer can be found here in [http://www.irchelp.org/irchelp/ircprimer.html html], [http://www.irchelp.org/irchelp/text/ircprimer.txt TXT], [http://www.kei.com/irc/IRCprimer1.1.ps PostScript].


Issue the command /me &lt;text&gt; where &lt;text&gt; is the text that should follow your nickname.
Example: /me slaps ajk around a bit with a large trout

/nick &lt;newNick&gt;

/nickserv register &lt;password&gt; &lt;email address&gt;

/ns instead of /nickserv, while others might need /msg nickserv

/nickserv identify &lt;password&gt;

Alternatives:
/ns identify &lt;password&gt;
/msg nickserv identify &lt;password&gt;


==== IRC WookieChat ====

WookieChat is the most complete internet client for communication across the IRC Network. WookieChat allows you to swap ideas and communicate in real-time, you can also exchange Files, Documents, Images and everything else using the application's DCC capabilities.


add smilies drawer/directory

 run wookiechat from the shell and set stack to 1000000 e.g. wookiechat stack 1000000

select a server / server window

* nickname 
* user name 
* real name - optional

Once you configure the client with your preferred screen name, you'll want to find a channel to talk in.


servers

* New Server - click on this to add / add extra - change details in section below this click box 
* New Group
* Delete Entry
* Connect to server
* connect in new tab
* perform on connect

Change details

* Servername - change text in this box to one of the below Server: 
* Port number - no need to change
* Server password
* Channel - add #channel from below 
* auto join - can click this 
* nick registration password,

Click Connect to server button above


&lt;pre&gt;
Server: irc.freenode.net
Channel: #aros
&lt;/pre&gt;

irc://irc.freenode.net/aros

&lt;pre&gt;
Server: chat.amigaworld.net 
Channel: #amigaworld or #amigans 
&lt;/pre&gt;

&lt;pre&gt;
On Sunday evenings USA time usually starting around 3PM EDT (1900 UTC)
Server:irc.superhosts.net
Channel #team*amiga  
&lt;/pre&gt;

&lt;pre&gt;
BitlBee and Minbif are IRCd-like gateways to multiple IM networks
Server: im.bitlbee.org 
Port 6667 
Seems to be most useful on WookieChat as you can be connected to several servers at once. One for Bitlbee and any messages that might come through that. One for your normal IRC chat server. 
&lt;/pre&gt;

[http://www.bitlbee.org/main.php/servers.html Other servers],

&lt;pre&gt;
#Amiga.org - irc.synirc.net eu.synirc.net dissonance.nl.eu.synirc.net (IPv6: 2002:5511:1356:0:216:17ff:fe84:68a) 
twilight.de.eu.synirc.net zero.dk.eu.synirc.net us.synirc.net avarice.az.us.synirc.net envy.il.us.synirc.net harpy.mi.us.synirc.net 
liberty.nj.us.synirc.net snowball.mo.us.synirc.net - Ports 6660-6669 7001 (SSL)
&lt;/pre&gt;

&lt;pre&gt;
Multiple server support
&quot;Perform on connect&quot; scripts and channel auto-joins
Automatic Nickserv login
Tabs for channels and private conversations
CTCP PING, TIME, VERSION, SOUND
Incoming and Outgoing DCC SEND file transfers
Colours for different events
Logging and automatic reloading of logs
mIRC colour code filters
Configurable timestamps
GUI for changing channel modes easily
Configurable highlight keywords
URL Grabber window
Optional outgoing swear word filter
Event sounds for tabs opening, highlighted words, and private messages
DCC CHAT support
Doubleclickable URL's
Support for multiple languages using LOCALE
Clone detection
Auto reconnection to Servers upon disconnection
Command aliases
Chat display can be toggled between AmIRC and mIRC style
Counter for Unread messages
Graphical nicklist and graphical smileys with a popup chooser
&lt;/pre&gt;


====IRC Aircos ====

Double click on Aircos icon in Extras:Networking/Apps/Aircos. It has been set up with a guest account for trial purposes. Though ideally, choose a nickname and password for frequent use of irc. 


====IRC and XMPP Jabberwocky====
 Servers are setup and close down at random 
You sign up to a server that someone else has setup and access chat services through them. 

The two ways to access chat from jabberwocky
&lt;pre &gt;
Jabberwocky -&gt; Server -&gt; XMPP -&gt; open and ad-free 
Jabberwocky -&gt; Server -&gt; Transports (Gateways) -&gt; Proprietary closed systems 
&lt;/pre &gt;

The Jabber.org service connects with all IM services that use XMPP, the open standard for instant messaging and presence over the Internet. The services we connect with include Google Talk (closed), Live Journal Talk, Nimbuzz, Ovi, and thousands more. However, you can not connect from Jabber.org to proprietary services like AIM, ICQ, MSN, Skype, or Yahoo because they don’t yet use XMPP components (XEP-0114) '''but''' you can use Jabber.com's servers and IM gateways (MSN, ICQ, Yahoo etc.) instead.

The best way to use jabberwocky is in conjunction with a public jabber server with '''transports''' to your favorite services, like gtalk, Facebook, yahoo, ICQ, AIM, etc.


You have to register with one of the servers, [https://list.jabber.at/ this list] or [http://www.jabberes.org/servers/ another list], [http://xmpp.net/ this security XMPP list],

Unfortunately jabberwocky can only connect to one server at a time so it is best to check what services each server offers. If you set it up with separate Facebook and google talk accounts, for example, sometimes you'll only get one or the other.

Jabberwocky open a window where the Jabber server part is typed in as well as your Nickname and Password.

Jabber ID (JID) identifies you to the server and other users.

Once registered the next step is to goto Jabberwocky's &quot;Windows&quot; menu and select the &quot;Agents&quot; option. The &quot;Agents List&quot; window will open.

Roster (contacts list)

[http://search.wensley.org.uk/ Chatrooms] (MUC) are available

File Transfer - can send and receive files through the Jabber service but not with other services like IRC, ICQ, AIM or Yahoo. All you need is an installed webbrowser and OpenURL.

Clickable URLs - The message window uses Mailtext.mcc and you can set a URL action in the MUI mailtext prefs like SYS:Utils/OpenURL %s NEWWIN.

There is no consistent Skype like (H.323 VoIP) video conferencing available over Jabber. The move from xmpp to Jingle should help but no support on any amiga-like systems at the moment. [http://aminet.net/package/dev/src/AmiPhoneSrc192 AmiPhone] and [http://www.lysator.liu.se/%28frame,faq,nobg,useframes%29/ahi/v4-site/ Speak Freely] was an early attempt voice only contact. SIP and Asterisk are other PBX options.


 Facebook

If you're using the XMPP transport provided by Facebook themselves, chat.facebook.com, it looks like they're now requiring SSL transport. This means jabberwocky method below will no longer work. The best thing to do is to create an ID on a public jabber server which has a Facebook gateway.

&lt;pre &gt;
1. launch jabberwocky
2. if the login window doesn't appear on launch, select 'account' from the jabberwocky menu
3. your jabber ID will be user@chat.facebook.com where user is your user ID
4. your password is your normal facebook password
5. to save this for next time, click the popup gadget next to the ID field

6. click the 'add' button
7. click the 'close' button
8. click the 'connect' button
&lt;/pre &gt;

you're done. you can also click the 'save as default account' button if you want. jabberwocky configured to auto-connect when launching the program, but you can configure as you like. there is amigaguide documentation included with jabberwocky.

[http://amigaworld.net/modules/newbb/viewtopic.php?topic_id=37085&amp;forum=32 Read more here]

for Facebook users, you can log-in directly to Facebook with jabberwocky. just sign in as @chat.facebook.com with your Facebook password as the password


 Twitter

For a few years, there has been added a twitter transport. Servers include [http://jabber.hot-chilli.net/ jabber.hot-chili.net],  and .

An [http://jabber.hot-chilli.net/tag/how-tos/ How-to]

:Read [http://jabber.hot-chilli.net/2010/05/09/twitter-transport-working/ more]

 Instagram 

no support at the moment best to use a web browser based client

 ICQ

The new version (beta) of StriCQ uses a newer ICQ protocol. Most of the ICQ Jabber Transports still use an older ICQ protocol. You can only talk one-way to StriCQ using the older Transports. Only the newer ICQv7 Transport lets you talk both ways to StriCQ. Look at the server lists in the first section to check.

Register on a Jabber server, e.g. this one works: http://www.jabber.de/
Then login into Jabberwocky with the following login data e.g. xxx@jabber.de / Password: xxx Now add your ICQ account under the window-&gt;Agents-&gt;&quot;Register&quot;. Now Jabberwocky connects via the Jabber.de server with your ICQ account.

 Yahoo Messenger

although yahoo! does not use xmpp protocol, you should be able to use the transport methods to gain access and post your replies

 MSN

early months of 2013 Microsoft will ditch MSN Messenger client and force everyone to use Skype...but MSN protocol and servers will keep working as usual for quite a long time....

Occasionally the Messenger servers have been experiencing problems signing in.  You may need to sign in at www.outlook.com and then try again.  It may also take multiple tries to sign in.  (This also affects you if you’re using Skype.)

You have to check each servers' Agents List to see what transports (MSN protocol, ICQ protocol, etc.) are supported or use the list address' provided in the section above. Then register with each transport (IRC, MSN, ICQ, etc.) to which you need access. After registering you can Connect to start chatting.

msn.jabber.com/registered should appear in the window.

From this [http://tech.dir.groups.yahoo.com/group/amiga-jabberwocky/message/1378 JW group] guide which  helps with this process in a clear, step by step procedure.

1. Sign up on MSN's site for a passport account. This typically involves getting a Hotmail address.

2. Log on to the Jabber server of your choice and do the following:

* Select the &quot;Windows/Agents&quot; menu option in Jabberwocky.
* Select the MSN Agent from the list presented by the server.
* Click the Register button to open a new window asking for:
**Username = passort account email address, typically your hotmail address.
**Nick = Screen name to be shown to anyone you add to your buddy list.
**Password = Password for your passport account/hotmail address.
* Click the Register button at the bottom of the new window.

3. If all goes well, you will see the MSN Gateway added to your buddy list. If not, repeat part 2 on another server. Some servers may show MSN in their list of available agents, but have not updated their software for the latest protocols used by MSN.

4. Once you are registered, you can now add people to your buddy list. Note that you need to include the '''msn.''' ahead of the servername so that it knows what gateway agent to use. Some servers may use a slight variation and require '''msg.gate.''' before the server name, so try both to see what works.

If my friend's msn was amiga@hotmail.co.uk and my jabber server was @jabber.meta.net.nz..
then amiga'''%'''hotmail.com@'''msn.'''jabber.meta.net.nz

or another the trick to import MSN contacts is that you don't type the hotmail URL but the passport URL... e.g. Instead of: goodvibe%hotmail.com@msn.jabber.com  You type: goodvibe%passport.com@msn.jabber.com 
And the thing about importing contacts I'm afraid you'll have to do it by hand, one at the time...

 Google Talk

any XMPP server will work, but you have to add your contacts manually. a google talk user is typically either @gmail.com or @talk.google.com. a true gtalk transport is nice because it brings your contacts to you and (can) also support file transfers to/from google talk users.

implement Jingle a set of extensions to the IETF's Extensible Messaging and Presence Protocol (XMPP)

support ended early 2014 as Google moved to Google+ Hangouts which uses it own proprietary format


===Video Player MPlayer===

Many of the menu features (such as doubling) do not work with the current version of mplayer but using

4:3
 mplayer -vf scale=800:600 file.avi

16:9
 mplayer -vf scale=854:480 file.avi

if you want gui use;
 mplayer -gui 1 &lt;other params&gt; file.avi

&lt;pre &gt;
stack 1000000

; using AspireOS 1.xx 
; copy FROM SYS:Extras/Multimedia/MPlayer/ TO RAM:MPlayer ALL CLONE &gt; Nil:

; using Icaros Desktop 1.x 
; copy FROM SYS:Tools/MPlayer/ TO RAM:MPlayer ALL CLONE &gt; Nil:

; using Icaros Desktop 2.x 
; copy FROM SYS:Utilities/MPlayer/ TO RAM:MPlayer ALL CLONE &gt; Nil:

cd RAM:MPlayer
run MPlayer -gui &gt; Nil:
;run MPlayer -gui -ao ahi_dev -playlist http://www.radio-paralax.de/listen.pls &gt; Nil: 
&lt;/pre &gt;

$ mplayer rtsp://127.0.0.1:554/sample_300kbit.mp4


MPlayer supports multicast streaming, and rtp/rtsp protocols (it might require [http://www.live555.com/openRTSP/ live555 library] to work with some streams). But you might have to build it where it's disabled. Also, multicast won't work with some AmiTCP-likes. MIAMI supported it, though.

AROS supports IPv4 (old but works) and this includes the needed address space for RTP.

If you mean multicast via RTP - mplayer handles it. You can even force UDP over TCP

-rtsp-stream-over-tcp

If the rtsp Real Time Streaming Protocol  server needs authentification:

-user -passwd


MPlayer - Menu - Open Playlist and load already downloaded .pls or .m3u file - auto starts around 4 percent cache

MPlayer - Menu - Open Stream and copy one of the .pls lines below into space allowed, press OK and press play button on main gui interface


Old 8bit 16bit remixes chip tune game music 
 
http://www.radio-paralax.de/listen.pls 

http://scenesat.com/

http://www.shoutcast.com/radio/Amiga

http://www.theoldcomputer.com/retro_radio/RetroRadio_Main.htm

http://www.kohina.com/

http://www.remix64.com/

http://retrogamer.net/forum/

http://retroasylum.podomatic.com/rss2.xml

http://retrogamesquad.com/

http://www.retronauts.com/

http://monsterfeet.com/noquarter/

http://www.retrogamingradio.com/

http://www.radiofeeds.co.uk/mp3.asp


[[#top|...to the top]]

====ZunePaint==== 

simplified typical workflow

* importing and organizing and photo management
* making global and regional local correction(s) - recalculation is necessary after each adjustment as it is not in real-time 
* exporting your images in the best format available with the preservation of metadata


Whilst achieving 80% of a great photo with just a filter, the remaining 20% comes from a manual fine-tuning of specific image attributes.


For photojournalism, documentary, and event coverage, minimal touching is recommended. Stick to Camera Raw for such shots, and limit changes to level adjustment, sharpness, noise reduction, and white balance correction.

For fashion or portrait shoots, a large amount of adjustment is allowed and usually ends up far from the original. Skin smoothing, blemish removal, eye touch-ups, etc. are common.  Might alter the background a bit to emphasize the subject.

Product photography usually requires a lot of sharpening, spot removal, and focus stacking.

For landscape shots, best results are achieved by doing the maximum amount of preparation before/while taking the shot. No amount of processing can match timing, proper lighting, correct gear, optimal settings, etc. Excessive post-processing might give you a dramatic shot but best avoided in the long term.


* White Balance - Left Amiga or F12 and K and under &quot;Misc color effects&quot; tab with a pull down for White Balance - color temperature also known as AKA tint (movies) or tones (painting) - warm temp raise red reduce green blue - cool raise blue lower red green 
* Exposure - exposure compensation, highlight/shadow recovery
* Noise Reduction - during RAW development or using external software
* Lens Corrections - distortion, vignetting, chromatic aberrations
* Detail - capture sharpening and local contrast enhancement
* Contrast - black point, levels (sliders) and curves tools (F12 and K) 
* Framing - straighten () and crop (F12 and F) 
* Refinements - color adjustments and selective enhancements - Left Amiga or F12 and K for RGB and YUV histogram tabs - 
* Resizing - enlarge for a print or downsize for the web or email (F12 and D) 
* Output Sharpening - customized for your subject matter and print/screen size


White Balance - F12 and K

scan your image for a shade which was meant to be white (neutral with each RGB value being equal) like paper or plastic which is in the same light as the subject of the picture. Use the dropper tool to select this color, similar colours will shift and you will have selected the perfect white balance for your part of the image - for the whole picture make sure RAZ or CLR button at the bottom is pressed before applying to the image above.


Exposure correction

F12 and K - YUV Y luminosity - RGB extra red tint - move red curve slightly down and move blue green curves slightly up

Workflows in practice

* Undo - Right AROS key or F12 and Z 
* Redo - Right AROS key or F12 and R

First flatten your image (if necessary) and then do a rotation until the picture looks level. 
* Crop the picture. Click the selection button and drag a box over the area of the picture you want to keep. Press the crop button and the rest of the photo will be gone. 
* Adjust your saturation, exposure, hue levels, etc., (right AROS Key and K for color correction) until you are happy with the photo. Make sure you zoom in all of the way to 100% and look the photo over, zoom back out and move around. Look for obvious problems with the picture. 
* After coloring and exposure do a sharpen (Right AROS key and E for Convolution and select drop down option needed), e.g. set the matrix to 5x5 (roughly equivalent Amount to 60%) and set the Radius to 1.0. Click OK.


And save your picture


Implemented or would like to see for simplification and ease of use

basic filters (presets) like black and white, monochrome, edge detection (sobel), motion/gaussian blur, 
* negative, sepiatone, retro vintage, night vision, colour tint, color gradient, color temperature, glows, fire, lightning, lens flare, emboss, filmic, pixelate mezzotint, antialias, etc.

adjust / cosmetic tools such as crop, 
* reshaping tools, straighten, smear, smooth, perspective, liquify, bloat, pucker, push pixels in any direction, dispersion, transform like warp, blending with soft light, page-curl, whirl, ripple, fisheye, neon,  etc. 
* red eye fixing, blemish remover, skin smoothing, teeth whitener, make eyes look brighter, desaturate,

effects like oil paint, cartoon, pencil sketch, charcoal, noise/matrix like sharpen/unsharpen, (right AROS key with A for Artistic effects) 
* blend two image, gradient blend, masking blend, explode, implode, custom collage, surreal painting, comic book style, needlepoint, stained glass, watercolor, mosaic, stencil/outline, crayon, chalk, etc.

borders such as 
* dropshadow, rounded, blurred, color tint, picture frame, film strip polaroid, bevelled edge, etc.

brushes e.g.
* frost, smoke, etc.

and manual control of

fix lens issues including vignetting (darkening), color fringing and barrel distortion, and chromatic and geometric aberration -  lens and body profiles

perspective correction

levels - directly modify the levels of the tone-values of an image, by using sliders for highlights, midtones and shadows

curves -  Color Adjustment and Brightness/Contrast

color balance

one single color transparent (alpha channel (color information/selections) for masking and/or blending ) for backgrounds, etc.

Threshold indicates how much other colors will be considered mixture of the removed color and non-removed colors

decompose layer into a set of layers with each holding a different type of pattern that is visible within the image

any selection using any selecting tools like lasso tool, marquee tool etc. the selection will temporarily be save to alpha 
If you create your image without transparency then the Alpha channel is not present, but you can add later.

File formats like .psd (Photoshop file has layers, masks etc.  contains edited sensor data. The original sensor data is no longer available) .xcf .raw .hdr

Image Picture Formats
* low dynamic range (JPEG, PNG, TIFF 8-bit), 16-bit (PPM, TIFF), typically as a 16-bit TIFF in either ProPhoto or AdobeRGB colorspace -  TIFF files are also fairly universal – although, if they contain proprietary data, such as Photoshop Adjustment Layers or Smart Filters, then they can only be opened by Photoshop making them proprietary.
* linear high dynamic range (HDR) images (PFM, [http://www.openexr.com/ ILM .EXR], jpg, [http://aminet.net/util/dtype cr2] (canon tiff based), hdr, NEF, CRW, ARW, MRW, ORF, RAF (Fuji), PEF, DCR, SRF, ERF, DNG files are RAW converted to an Adobe proprietary format - a container that can embed the raw file as well as the information needed to open it) 
An old version of [http://archives.aros-exec.org/index.php?function=browse&amp;cat=graphics/convert dcraw]

There is no single RAW file format. Each camera manufacturer has one or more unique RAW formats. RAW files contain the brightness levels data captured by the camera sensor. This data cannot be modified. A second smaller file, separate XML file, or within a database with instructions for the RAW processor to change exposure, saturation etc. The extra data can be changed but the original sensor data is still there. RAW is technically least compatible.

A raw file is high-bit (usually 12 or 14 bits of information) but a camera-generated TIFF file will be usually converted by the camera (compressed, downsampled) to 8 bits. The raw file has no embedded color balance or color space, but the TIFF has both. These three things (smaller bit depth, embedded color balance, and embedded color space) make it so that the TIFF will lose quality more quickly with image adjustments than the raw file. The camera-generated TIFF image is much more like a camera processed JPEG than a raw file. A strong advantage goes to the raw file. The power of RAW files, such as the ability to set any color temperature non-destructively and will contain more tonal values.

The principle of preserving the maximum amount of information to as late as possible in the process. The final conversion - which will always effectively represent a &quot;downsampling&quot; - should prevent as much loss as possible.

Once you save it as TIFF, you throw away some of that data irretrievably. When saving in the lossy JPEG format, you get tremendous file size savings, but you've irreversibly thrown away a lot of image data. As long as you have the RAW file, original or otherwise, you have access to all of the image data as captured.

Keyboard equivalence with Photoshop(tm) would help 

File
PHOTOSHOP	SHORTCUT	GIMP
New	Ctrl+n	New
Open	Ctrl+o	Open
Close	Ctrl+w	Close
Save	Ctrl+s	Save
Save as	Shift+Ctrl+s	Save as
Revert	F12	Revert
Print	Ctrl+p	Print
Exit	Ctrl+q	Quit
 
Edit
PHOTOSHOP	SHORTCUT	GIMP
Undo/Redo (1 level)	Ctrl+z	Undo (Redo is Shift+Ctrl+z)
Cut	Ctrl+x	Cut
Copy	Ctrl+c	Copy
Paste	Ctrl+v	Paste
Paste Into	Shift+Ctrl+v	Paste Into
Fill with FG color	Alt+Backspace	Fill with FG color
Fill with BG color	Control+Backspace	Fill with BG color
 
Image/Colors
PHOTOSHOP	SHORTCUT	GIMP
Levels	Ctrl+l	Levels
Auto Contrast	Shift+Ctrl+Alt+l	Stretch Contrast (same?)
Curves	Ctrl+m	Curves
Color Balance	Ctrl+b	Color Balance
Hue/Saturation	Ctrl+u	Hue-Saturation
Desaturate	Shift+Ctrl+u	Desaturate
Invert	Ctrl+i	Invert
Default Colors	d	Default Colors
Switch Colors	x	Switch Colors
 
Layer
PHOTOSHOP	SHORTCUT	GIMP
New Layer	Shift+Ctrl+n	New Layer
Layer via Copy	Ctrl+j	Duplicate Layer
Bring (layer) to Front	Shift+Ctrl+]	Layer to Top
Send (layer) to Back	Shift+Ctrl+[	Layer to Bottom
Bring (layer) Forward	Ctrl+]	Raise Layer
Send (layer) Backward	Ctrl+[	Lower Layer
Select Top Layer	Shift+Alt+]	Select Top Layer
Select Bottom Layer	Shift+Alt+[	Select Bottom Layer
Select One Layer Forward	Alt+]	Select Previous Layer
Select One Layer Backward	Alt+[	Select Next Layer
Merge Down	Ctrl+e	Merge Down
Merge Visible	Shift+Ctrl+e	Merge Visible
Preserve Transparency	/	Keep Transparency
Cycle Modes Forwards	Shift+=	Next Layer Mode
Cycle Modes Backwards	Shift+-	Previous Layer Mode
 
Select
PHOTOSHOP	SHORTCUT	GIMP
Select All	Ctrl+a	Select All
Deselect	Ctrl+d	Select None
Inverse	Shift+Ctrl+i	Invert
Feather	Ctrl+Alt+d	Feather
 
View
PHOTOSHOP	SHORTCUT	GIMP
Zoom In	Ctrl+=	Zoom In
Zoom Out	Ctrl+-	Zoom Out
Fit on Screen	Ctrl+0	Zoom to Fit Window
Actual Pixels	Ctrl+Alt+0	Zoom 1:1
Show/Hide Extras	Ctrl+h	Toggle Show Selection (close enough?)
Show/Hide Guides	Ctrl+'	Toggle Show Guides
Show/Hide Grid	Ctrl+Alt+'	Toggle Show Grid
Show/Hide Rulers	Ctrl+r	Toggle Show Rulers
Snap	Ctrl+;	Snap to Guides
Scroll View Up	Page Up	Scroll Page Up
Scroll View Down	Page Down	Scroll Page Down
Scroll View Left	Ctrl+Page Up	Scroll Page Left
Scroll View Right	Ctrl+Page Down	Scroll Page Right
 
Window/Dialogs
PHOTOSHOP	SHORTCUT	GIMP
?	F5	Tools Dialog
Color Tab	F6	Colors Dialog
Layers Tab	F7	Layers Dialog
Info Tab	F8	Image Information
 
Tools
PHOTOSHOP	SHORTCUT	GIMP
Rectangular Marquee Tool	m	Rect Select Tool
Elliptical Marquee Tool	Shift+m	Ellipse Select Tool
 	*This is a toggle between 'Elliptical Marquee Tool' and 'Rectangular Marquee Tool' in Photoshop	 
Move Tool	v	Move Tool
Lasso Tool	l	Free Select Tool
Magic Wand Tool	w	Fuzzy Select Tool
Crop Tool	c	Crop &amp; Resize Tool
Airbrush Tool	j	Airbrush Tool
Paintbrush Tool	b	Paintbrush Tool
Clone Stamp Tool	s	Clone Stamp Tool
Eraser Tool	e	Eraser Tool
Gradient Tool	g	Blend Tool
Paint Bucket Tool	Shift+g	Bucket Fill Tool
 	*This is a toggle between 'Paint Bucket Tool' and 'Gradient Tool' in Photoshop	 
Blur Tool	r	Convolve Tool
Dodge Tool	o	DodgeBurn Tool
Type Tool	t	Text Tool
Pen Tool	p	Bezier Select Tool
Eye Dropper Tool	i	Color Picker Tool
Zoom Tool	z	Magnify Tool
Previous Brush	,	Previous Brush
Next Brush	.	Next Brush
First Brush	Shift+&lt;	First Brush
Last Brush	Shift+&gt;	Last Brush
Decrease Brush Size	[	Decrease Brush Size
Increase Brush Size	]	Increase Brush Size
Decrease Brush Hardness	{	Decrease Brush Hardness
Increase Brush Hardness	}	Increase Brush Hardness
 
Help
PHOTOSHOP	SHORTCUT	GIMP
Help	F1	Help
Context Help	Shift+F1	Context Help
 
Misc.
PHOTOSHOP	SHORTCUT	GIMP
Last Filter	Ctrl+f	Repeat Last Filter
?	Shift+Ctrl+f	Reshow Last Filter
Preferences	Ctrl+k	Preferences
Liquify	Shift+Ctrl+x	IWarp (close enough?)
Toggle Quick Mask	q	Toggle Quick Mask


Spotlights - triangle of white opaque shape

Cutting out and/or replacing unwanted background or features - select large areas with the selection option like the Magic Wand tool (aka Color Range) or the Lasso (quick and fast) with feather 2 to soften edge or the pen tool which adds points/lines/Bézier curves (better control but slower), hold down the shift button as you click to add extra points/areas of the subject matter to remove. Increase the tolerance to cover more areas. To subtract from your selection hold down alt as you're clicking. 
* Layer masks are a better way of working than Erase they clip (black hides/hidden white visible/reveal). Clone Stamp can be simulated by   and brushes for other areas. 
* Leave the fine details like hair, fur, etc. to later with lasso and the shift key to draw a line all the way around your subject. Gradient Mapping - Inverse - Mask. i.e. Refine your selected image with edge detection and using the radius and edge options / adjuster (increase/decrease contrast) so that you will capture more fine detail from the background allowing easier removal. 
Remove fringe/halo

saving image as png rather than jpg/jpeg to keep transparency background intact.


Implemented [http://colorizer.org/ colour model representations] [http://paulbourke.net/texture_colour/colourspace/ Mathematical approach] - Photo stills are spatially 2d (h and w), but are colorimetrically 3d (r g and b, or H L S, or Y U V etc.) as well. 
* RGB - split cubed mapped color model for photos and computer graphics hardware using the light spectrum (adding and subtracting) 
* YUV - Y-Lightness U-blue/yellow V-red/cyan (similar to YPbPr and YCbCr) used in the PAL, NTSC, and SECAM composite digital TV color [http://crewofone.com/2012/chroma-subsampling-and-transcoding/#comment-7299 video]


Histograms

White balanced (neutral) if the spike happens in the same place in each channel of the RGB graphs. If not, you're not balanced. 
If you have sky you'll see the blue channel further off to the right.

RGB is best one to change colours. These elements RGB is a 3-channel format containing data for Red, Green, and Blue in your photo scale between 0 and 255. The area in a picture that appears to be brighter/whiter contains more red color as compared to the area which is relatively darker. Similarly in the green channel the area that appears to be darker contains less amount of green color as compared to the area that appears to be brighter.  Similarly in the blue channel the area appears to be darker contains less amount of blue color as compared to the area that appears to be brighter. Brightness luminance histogram also matches the green histogram more than any other color - human eye interprets green better e.g. RGB rough ratio 15/55/30%

RGBA (RGB+A, A means alpha channel) .  The alpha channel is used for &quot;alpha compositing&quot;, which can mostly be associated as &quot;opacity&quot;.  AROS deals in RGB with two digits for every color (red, green, blue), in ARGB you have two additional hex digits for the alpha channel.

The shadows are represented by the left third of the graph.  The highlights are represented by the right third.  And the midtones are, of course, in the middle.  The higher the black peaks in the graph, the more pixels are concentrated in that tonal range (total black area). 
By moving the black endpoint, which identifies the shadows (darkness) and a white light endpoint (brightness) up and down either sides of the graph, colors are adjusted based on these points. 
By dragging the central one, can increased the midtones and control the contrast, raise shadows levels, clip or softly eliminate unsafe levels, alter gamma, etc... in a way that is much more precise and creative .


RGB Curves

* Move left endpoint (black point) up or right endpoint (white point) up brightens 
* Move left endpoint down or right endpoint down darkens

Color Curves

* Dragging up on the Red Curve increases the intensity of the reds in the image but 
* Dragging down on the Red Curve decreases the intensity of the reds and thus increases the apparent intensity of its complimentary color, cyan. Green’s complimentary color is magenta, and blue’s is yellow.
&lt;pre&gt;
 Red &lt;-&gt; Cyan
 Green &lt;-&gt;Magenta
 Blue &lt;-&gt;Yellow 
&lt;/pre&gt;

YUV Best option to analyse and pull out statistical elements of any picture (i.e.  separate luminance data from color data). The line in Y luma tone box represents the brightness of the image with the point in the bottom left been black, and the point in the top right as white.  A low-contrast image has a concentrated clump of values nearer to the center of the graph. By comparison, a high-contrast image has a wider distribution of values across the entire width of the Histogram.   A histogram that is skewed to the right would indicate a picture that is a bit overexposed because most of the color data is on the lighter side (increase exposure with higher value F), while a histogram with the curve on the left shows a picture that is underexposed. This is good information to have when using post-processing software because it shows you not only where the color data exists for a given picture, but also where any data has been clipped (extremes on edges of either side): that is, it does not exist and, therefore, cannot be edited.  By dragging the endpoints of the line and as well as the central one, can increased the dark/shadows, midtones and light/bright parts and control the contrast, raise shadows levels, clip or softly eliminate unsafe levels, alter gamma, etc... in a way that is much more precise and creative .

The U and V chroma parts show color difference components of the image. It’s useful for checking whether or not the overall chroma is too high, and also whether it’s being limited too much
Can be used to create a negative image but also 
With U (Cb), the higher value you are, the more you're on the blue primary color. If you go to the low values then you're on blue complementary color, i.e. yellow.
With V (Cr), this is the same principle but with Red and Cyan.
e.g. If you push U full blue and V full red, you get magenta. If you push U full yellow and V full Cyan then you get green.

YUV simultaneously adds to one side of the color equation while subtracting from the other.  
using YUV to do color correction can be very problematic because each curve alters the result of each other: the mutual influence between U and V often makes things tricky. You may also be careful in what you do to avoid the raise of noise (which happens very easily). Best results are obtained with little adjustments

sunset that looks uninspiring and needs some color pop especially for the rays over the hill, a subtle contrast raise while setting luma values back to the legal range without hard clipping.


Free royalty pictures, [www.freeimages.com ], [http://imageshack.us/ ], [http://photobucket.com/ ], [http://rawpixels.net/], [], [], [], 


====Lunapaint====

Pixel based drawing app with onion-skin animation function

 Blocking, Shading, Coloring, adding detail 

&lt;pre&gt;
b BRUSH
e ERASER

alt eyedropper 
v layer tool 

z ZOOM / MAGNIFY &lt; &gt; n 
spc panning 
m  marque 
q lasso 
w same color selection / region 
&lt;/pre&gt;

&lt;pre&gt;
, LM RM
v 
V
f  filter 
F 
.  size 

p 
,  pick color 
[] last / next color 
&lt;/pre&gt;


There is not much missing in Lunapaint to be as good as FlipBook and then you have to take into account that Flipbook is considered to be amongst the best and easiest to use animation software out there. Ok to be honest Flipbook has some nice features that require more heavy work but those aren't so much needed right away, things like camera effects, sound, smart fill, export to different movie file formats etc.

Tried Flipbook with my tablet and compared it to Luna. The feeling is the same when sketching. LunaPaint is very responsive/fluent to draw with. Just as Flipbook is, and that responsiveness is something its users have mentioned as one of the positive sides of said software.

 author was learning MUI. Some parts just have to be rewritten with proper MUI classes before new features can be added.

* add [Frame Add] / [Frame Del]
* whole animation feature is impossible to use. If you draw 2 color maybe but if you start coloring your cells then you get in trouble
* pickup the entire image as a brush, not just a selection ? And consequently remove the brush from memory when one doesn't need it anymore. can pick up a brush and put it onto a new image but cropping isn't possible, nor to load/save brushes.
* Undo is something I longed for ages in Lunapaint.
* to import into the current layer, other types of images (e.g. JPEG) besides RAW64.
* implement graphic tablet features support


**GENERAL DRAWING**

Miss it very much:
UNDO
ERASER
COLORPICKER - has to show on palette too which color got picked.
BACKGROUND COLOR -Possibility to select from &quot;New project screen&quot;

Miss it somewhat:
ICON for UNDO
ICON for ERASER
ICON for CLEAR SCREEN ( What can I say? I start over from scratch very often )
BRUSH - possibility to cut out as brush not just copy off image to brush

**ANIMATING**

Miss it very much:
NUMBER OF CELLS - Possibity to change total no. of cells during project
ANIM BRUSH - Possibility to pick up a selected part of cells into an animbrush

Miss it somewhat:
ADD/REMOVE FRAMES: Add/remove single frame

In general LunaPaint is really well done and it feels like a new DeluxePaint version. It works with my tablet. Sure there's much missing of course but things can always be added over time. So there is great potential in LunaPaint that's for sure. Animations could be made in it and maybe put together in QuickVideo, saving in .gif or .mng etc some day.


LAYERS
-Layers names don't get saved globally in animation frames
-Layers order don't change globally in an animation (perhaps as default?).

EXPORTING IMAGES
-Exporting frames to JPG/PNG gives problems with colors. (wrong colors. See my animatiopn --&gt; My robot was blue now it's &quot;gold&quot; ) I think this only happens if you have layers.
-Trying to flatten the layers before export doesn't work if you have animation frames only the one you have visible will flatten properly all other frames are destroyed. (Only one of the layers are visible on them)
-Exporting images filenames should be for example e.g. file0001, file0002...file0010 instead as of now file1, file2...file10

LOAD/SAVE (Preferences)
-Make a setting for the default &quot;Work&quot; folder.

* Destroyed colors if exported image/frame has layers 
* mystic color cycling of the selected color while stepping frames back/forth (annoying)

&lt;pre&gt;
Deluxe Paint II enhanced key shortcuts 
    NOTE: @ denotes the ALT key

    [Technique]

    F1  - Paint
    F2  - Single Colour
    F3  - Replace
    F4  - Smear
    F5  - Shade
    F6  - Cycle
    F7  - Smooth
     M  - Colour Cycle

    [Brush]

     B  - Restore
     O  - Outline
     h  - Halve brush size
     H  - Double brush size
     x  - Flip brush on X axis
     X  - Double brush size on X axis only
     y  - Flip on Y 
     Y  - Double on Y
     z  - Rotate brush 90 degrees
     Z  - Stretch

    [Stencil]

     `  - Stencil On

    [Miscellaneous]

    F9  - Info Bar
    F10 - Selection Bar
    @o  - Co-Ordinates
    @a  - Anti-alias
    @r  - Colourise
    @t  - Translucent
    TAB - Colour Cycle

    [Picture]

     L  - Load
     S  - Save
     j  - Page to Spare(Flip)
     J  - Page to Spare(Copy)
     V  - View Page
     Q  - Quit

    [General Keys]

     m  - Magnify
     &lt;  - Zoom In
     &gt;  - Zoom Out
     [  - Palette Colour Up
     ]  - Palette Colour Down
     (  - Palette Colour Left
     )  - Palette Colour Right
     ,  - Eye Dropper
     .  - Pixel / Brush Toggle
     /  - Symmetry
     |  - Co-Ordinates
    INS - Perspective Control
    +/- - Brush Size (Fine Control)
     w  - Unfilled Polygon
     W  - Filled Polygon
     e  - Unfilled Ellipse
     E  - Filled Ellipse
     r  - Unfilled Rectangle
     R  - Filled Rectangle
     t  - Type/text tool
     a  - Select Font
    u/U - Undo
     d  - Brush
     D  - Filled Non-Uniform Polygon
    f/F - Fill Options
    g/G - Grid
    h/H - Brush Size (Coarse Control)
     K  - Clear
     c  - Unfilled Circle
     C  - Filled Circle
     v  - Line
     b  - Scissor Select and Toggle
     B  - Brush
    {,} - Toggle between two background colours
&lt;/pre&gt;

====Lodepaint====

Pixel based painting artwork app

====Grafx2====

Pixel based painting artwork app aesprite like 

[https://www.youtube.com/watch?v=59Y6OTzNrhk aesprite workflow keys and tablet use], [], 


====Vector Graphics ZuneFIG====

Vector Image Editing of files .svg .ps .eps


*Objects - raise lower rotate flip aligning snapping 
*Path - unify subtract intersect exclude divide 
*Colour - fill stroke 
*Stroke - size 
*Brushes - 
*Layers - 
*Effects - gaussian bevels glows shadows 
*Text    - 
*Transform - 


 AmiFIG ([http://epb.lbl.gov/xfig/frm_introduction.html xfig manual]) 

[[File:MyScreen.png|thumb|left|alt=Showing all Windows open in AmiFIG.|All windows available to AmiFIG.]]

for drawing simple to intermediate vector graphic images for scientific and technical uses and for illustration purposes for those with talent

;Menu options
* Load - fig format but import(s) SVG
* Save - fig format but export(s) eps, ps, pdf, svg and png
* PAN = Ctrl + Arrow keys 
* Deselect all points

There is no selected object until you apply the tool, and the selected object is not highlighted.

;Metrics - to set up page and styles - first window to open on new drawings

;Tools - Drawing Primitives - set Attributes window first before clicking any Tools button(s) 
* Shapes - circles, ellipses, arcs, splines, boxes,  polygon 
* Lines - polylines
* Text &quot;T&quot; button 
* Photos - bitmaps
* Compound - Glue, Break, Scale 
* POINTs - Move, Add, Remove 
* Objects - Move, Copy, Delete, Mirror, Rotate, Paste 
use right mouse button to stop extra lines, shapes being formed and the left mouse to select/deselect tools button(s)
* Rotate - moves in 90 degree turns centered on clicked POINT of a polygon or square

;Attributes which provide change(s) to the above primitives 
* Color
* Line Width
* Line Style
* arrowheads

;Modes 
Choose from freehand, charts, figures, magnet, etc.

;Library - allows .fig clip-art to be stored 
* compound tools to add .fig(s) together

;FIG 3.2 [http://epb.lbl.gov/xfig/fig-format.html Format] as produced by xfig version 3.2.5 
&lt;pre&gt;
Landscape
Center
Inches
Letter 
100.00
Single
-2
1200 2
4 0 0 50 -1 0 12 0.0000 4 135 1050 1050 2475 This is a test.01
&lt;/pre&gt;

# change the text alignment within the textbox. I can choose left, center, or right aligned by either changing the integer in the second column from 0 (left) to 1 or 2 (center, or right). 
# The third integer in the row specifies fontcolor. For instance, 0 is black, but blue is 1 and Green3 is 13.
# The sixth integer in the bottom row specifies fontface. 0 is Times-Roman, but 16 is Helvetica (a MATLAB default).
# The seventh number is fontsize. 12 represents a 12pt fontsize. Changing the fontsize of an item really is as easy as changing that number to 20.
# The next number is the counter-clockwise angle of the text. Notice that I have changed the angle to .7854 (pi/4 rounded to four digits=45 degrees).
# twelfth number is the position according to the standard “x-axis” in Xfig units from the left. Note that 1200 Xfig units is equivalent to once inch.
# thirteenth number is the “y-position” from the top using the same unit convention as before.

* The nested text string is what you entered into the textbox.
* The “01″ present at the end of that line in the .fig file is the closing tag. For instance, a change to \100 appends a @ symbol at the end of the period of that sentence.

; Just to note there are no layers, no 3d functions, no shading, no transparency, no animation


[[#top|...to the top]]

===Audio===


# AHI uses linear panning/balance, which means that in the center, you will get -6dB. If an app uses panning, this is what you will get. Note that apps like Audio Evolution need panning, so they will have this problem.

# When using AHI Hifi modes, mixing is done in 32-bit and sent as 32-bit data to the driver. The Envy24HT driver uses that to output at 24-bit (always).

# For the Envy24/Envy24HT, I've made 16-bit and 24-bit inputs (called Line-in 16-bit, Line-in 24-bit etc.). There is unfortunately no app that can handle 24-bit recording.


====Music Mods====

Digital module (mods) trackers are music creation software using samples and sometimes soundfonts, audio plugins (VST, AU or RTAS), MIDI.

Generally, MODs are similar to MIDI in that they contain note on/off and other sequence messages that control the mod player. Unlike (most) midi files, however, they also contain sound samples that the sequence information actually plays. MOD files can have many channels (classic amiga mods have 4, corresponding to the inbuilt sound channels), but unlike MIDI, each channel can typically play only one note at once. However, since that note might be a sample of a chord, a drumloop or other complex sound, this is not as limiting as it sounds.

Like MIDI, notes will play indefinitely if they're not instructed to end. Most trackers record this information automatically if you play your music in live. If you're using manual note entry, you can enter a note-off command with a keyboard shortcut - usually Caps Lock.

In fact when considering file size MOD is not always the best option. Even a dummy song wastes few kilobytes for nothing when a simple SID tune could be few hundreds bytes and not bigger than 64kB. AHX is another small format, AHX tunes are never larger than 64kB excluding comments.

[https://www.youtube.com/watch?v=rXXsZfwgil Protrekkr] (previously aka [w:Juan_Antonio_Arguelles_Rius|NoiseTrekkr])

If Protrekkr does not start, please check if the Unit 0 has been setup in the AHI prefs and still not, go to the directory utilities/protrekkr and double click on the Protrekkr icon

*Sample
*Note - Effect 
*Track (column) - Pattern - Order

It all starts with the Sample which is used to create Note(s) in a Track (column of a tracker) 
The Note can be changed with an Effect.  A Track of Note(s) can be collected into a Pattern (section of a song) and these can be given Order to create the whole song.

Patience (notes have to be entered one at a time) or playing the bassline on a midi controller (faster - see midi section above).  Best approach is to wait until a melody popped into your head.

*Up-tempo means the track should be reasonably fast, but not super-fast. 
*Groovy and funky imply the track should have some sort of &quot;swing&quot; feel, with plenty of syncopation or off beat emphasis and a recognizable, melodic bass line. 
*Sweet and happy mean upbeat melodies, a major key and avoiding harsh sounds.
*Moody - minor key

First, create a quick bass sound, which is basically a sine wave, but can be hand drawn for a little more variance. It could also work for the melody part, too.

This is usually a bass guitar or some kind of synthesizer bass. The bass line is often forgotten by inexperienced composers, but it plays an important role in a musical piece. Together with the rhythm section the bass line forms the groove of a song. It's the glue between the rhythm section and the melodic layer of a song.

The drums are just pink noise samples, played at different frequencies to get a slightly different sound for the kick, snare, and hihats.

Instruments that fall into the rhythm category are bass drums, snares, hi-hats, toms, cymbals, congas, tambourines, shakers, etc. Any percussive instrument can be used to form part of the rhythm section.

The lead is the instrument that plays the main melody, on top of the chords. There are many instruments that can play a lead section, like a guitar, a piano, a saxophone or a flute. The list is almost endless. There is a lot of overlap with instruments that play chords. Often in one piece an instrument serves both roles. The lead melody is often played at a higher pitch than the chords.

Listened back to what was produced so far, and a counter-melody can be imagined, which can be added with a triangle wave.

To give the ends of phrases some life, you can add a solo part with a crunchy synth. By hitting random notes in the key of G, then edited a few of them.

For the climax of the song, filled out the texture with a gentle high-pitch pad… …and a grungy bass synth.


The arrow at A points at the pattern order list. As you see, the patterns don't have to be in numerical order. This song starts with pattern &quot;00&quot;, then pattern &quot;02&quot;, then &quot;03&quot;, then &quot;01&quot;, etcetera. Patterns may be repeated throughout a song.

The B arrow points at the song title. Below it are the global BPM and speed parameters. These determine the tempo of the song, unless the tempo is altered through effect commands during the song.

The C arrow points at the list of instruments. An instrument may consist of multiple samples. Which sample will be played depends on the note. This can be set in the Instrument Editing screen. Most instruments will consist of just one sample, though. The sample list for the selected instrument can be found under arrow D.

Here's a part of the main editing screen. This is where you put in actual notes. Up to 32 channels can be used, meaning 32 sounds can play simultaneously. The first six channels of pattern &quot;03&quot; at order &quot;02&quot; are shown here. The arrow at A points at the row number. The B arrow points at the note to play, in this case a C4. The column pointed at by the C arrow tells us which instrument is associated with that note, in this case instrument #1 &quot;Kick&quot;.

The column at D is used (mainly) for volume commands. In this case it is left empty which means the instrument should play at its default volume. You can see the volume column being used in channel #6.

The E column tells us which effect to use and any parameters for that effect. In this case it holds the &quot;F&quot; effect, which is a tempo command. The &quot;04&quot; means it should play at tempo 4 (a smaller number means faster).

Base pattern

When I create a new track I start with what I call the base pattern. It is worthwhile to spend some time polishing it as a lot of the ideas in the base pattern will be copied and used in other patterns. At least, that's how I work. Every musician will have his own way of working. In &quot;Wild Bunnies&quot; the base pattern is pattern &quot;03&quot; at order &quot;02&quot;.

In the section about selecting samples I talked about the four different categories of instruments: drums, bass, chords and leads. That's also how I usually go about making the base pattern. I start by making a drum pattern, then add a bass line, place some chords and top it off with a lead. This forms the base pattern from which the rest of the song will grow.


Drums

Here's a screenshot of the first four rows of the base pattern. I usually reserve the first four channels or so for the drum instruments. Right away there are a couple of tricks shown here. In the first channel the kick, or bass drum, plays some notes. Note the alternating F04 and F02 commands. The &quot;F&quot; command alters the tempo of the song and by quickly alternating the tempo; the song will get some kind of &quot;swing&quot; feel.

In the second channel the closed hi-hat plays a fairly simple pattern. Further down in the channel, not shown here, some open hi-hat notes are added for a bit of variation.

In the third and fourth channel the snare sample plays. The &quot;8&quot; command is for panning. One note is panned hard to the left and the other hard to the right. One sample is played a semitone lower than the other. This results in a cool flanging effect. It makes the snare stand out a little more in the mix.


Bass line

There are two different instruments used for the bass line. Instrument #6 is a pretty standard synthesized bass sound. Instrument #A sounds a bit like a slap bass when used with a quick fade out. By using two different instruments the bass line sounds a bit more ”human”. The volume command is used to cut off the notes. However, it is never set to zero. Setting the volume to a very small value will result in a reverb-like effect. This makes the song sound more &quot;live&quot;.

The bass line hints at the chords that will be played and the key the song will be in. In this case the key of the song is D-major, a positive and happy key.


Chords

The D major chords that are being played here are chords stabs; short sounds with a quick decay (fade out). Two different instruments (#8 and #9) are used to form the chords. These instruments are quite similar, but have a slightly different sound, panning and volume decay. Again, the reason for this is to make the sound more human. The volume command is used on some chords to simulate a delay, to achieve more of a live feel. The chords are placed off-beat making for a funky rhythm.


Lead

Finally the lead melody is added. The other instruments are invaluable in holding the track together, but the lead melody is usually what catches people's attention.

A lot of notes and commands are used here, but it looks more complex than it is. A stepwise ascending melody plays in channel 13. Channel 14 and 15 copy this melody, but play it a few rows later at a lower volume. This creates an echo effect. A bit of panning is used on the notes to create some stereo depth. Like with the bass line, instead of cutting off notes the volume is set to low values for a reverb effect. The &quot;461&quot; effect adds a little vibrato to the note, which sounds nice on sustained notes.

Those paying close attention may notice the instrument used here for the lead melody is the same as the one used for the bass line (#6 &quot;Square&quot;), except played two or three octaves higher. This instrument is a looped square wave sample. Each type of wave has its own quirks, but the square wave (shown below) is a really versatile wave form.

Song structure

Good, catchy songs are often carefully structured into sections, some of which are repeated throughout the song with small variations.

A typical pop-song structure is: Intro - Verse - Chorus - Verse - Chorus - Bridge - Chorus.

Other single sectional song structures are

&lt;pre&gt;
Strophic or AAA Song Form - oldest story telling with refrain (often title of the song) repeated in every verse section melody 
AABA Song Form - early popular, jazz and gospel fading during the 1960s 
AB or Verse/Chorus Song Form - songwriting format of choice for modern popular music since the 1960s 
Verse/Chorus/Bridge Song Form
ABAB Song Form
ABAC Song Form
ABCD Song Form
AAB 12-Bar Song Form - three four-bar lines or sub-sections 
8-Bar Song Form
16-Bar Song Form
Hybrid / Compound Song Forms
&lt;/pre&gt;

The most common building blocks are:

#INTRODUCTION(INTRO)
#VERSE
#REFRAIN
#PRE-CHORUS / RISE / CLIMB
#CHORUS
#BRIDGE
#MIDDLE EIGHT
#SOLO / INSTRUMENTAL BREAK
#COLLISION
#CODA / OUTRO
#AD LIB (OFTEN IN CODA / OUTRO)

The chorus usually has more energy than the verse and often has a memorable melody line. As the chorus is repeated the most often during the song, it will be the part that people will remember.

The bridge often marks a change of direction in the song. It is not uncommon to change keys in the bridge, or at least to use a different chord sequence. The bridge is used to build up tension towards the big finale, the last repetition of chorus.


 Playing

RCTRL:                           Play song from row 0.

LSHIFT + RCTRL:                  Play song from current row.

RALT:                            Play pattern from row 0.

LSHIFT + RALT:                   Play pattern from current row.

Left mouse on '&gt;':               Play song from row 0.

Right mouse on '&gt;':              Play song from current row.

Left mouse on '|&gt;':              Play pattern from row 0.

Right mouse on '|&gt;':             Play pattern from current row.

Left mouse on 'Edit/Record':     Edit mode on/off.

Right mouse on 'Edit/Record':    Record mode on/off.


 Editing 


LSHIFT + ESCAPE:                 Switch large patterns view on/off

TAB:                    Go to next track

LSHIFT + TAB:                    Go to prev. track

LCTRL + TAB:                    Go to next note in track

LCTRL + LSHIFT + TAB:           Go to prev. note in track

SPACE:                           Toggle Edit mode On &amp; Off

(Also stop if the song is being played)

SHIFT SPACE:                     Toggle Record mode On &amp; Off

(Wait for a key note to be pressed

or a midi in message to be received)

DOWN ARROW:                      1 Line down

UP ARROW:                        1 Line up

LEFT ARROW:                      1 Row left

RIGHT ARROW:                     1 Row right

PREV. PAGE:                      16 Arrows Up

NEXT PAGE:                       16 Arrows Down

HOME / END:                      Top left / Bottom right of pattern

LCTRL + HOME / END:              First / last track

F5, F6, F7, F8, F9:              Jump to 0, 1/4, 2/4, 3/4, 4/4 lines of the patterns

+ - (Numeric keypad):           Next / Previous pattern

LCTRL + LEFT / RIGHT:           Next / Previous pattern

LCTRL + LALT + LEFT / RIGHT:    Next / Previous position

LALT + LEFT / RIGHT:           Next / Previous instrument

LSHIFT + M:                      Toggle mute state of the current channel

LCTRL + LSHIFT + M:             Solo the current track / Unmute all

LSHIFT + F1 to F11:              Select a tab/panel

LCTRL + 1 to 4:                 Select a copy buffer


 Tracking 

1st and 2nd keys rows:           Upper octave row

3rd and 4th keys rows:           Lower octave row

RSHIFT:                          Insert a note off

/ and * (Numeric keypad)

or F1 F2:                        -1 or +1 octave

INSERT / BACKSPACE:              Insert or Delete a line in current track

or current selected block.

LSHIFT + INSERT / BACKSPACE:     Insert or Delete a line in current pattern

DELETE (NOT BACKSPACE):          Empty a column or a selected block.


 Blocks

(Blocks can also be selected with the mouse by holding the right button and scrolling the pattern with the mouse wheel).


LCTRL + A:          Select entire current track

LCTRL + LSHIFT + A: Select entire current pattern

LALT + A:          Select entire column note in a track

LALT + LSHIFT + A: Select all notes of a track

LCTRL + X:          Cut the selected block and copy it into the block-buffer

LCTRL + C:          Copy the selected block into the block-buffer

LCTRL + V:          Paste the data from the block buffer into the pattern

LCTRL + I:          Interpolate selected data from the first to the last row of a selection

LSHIFT + ARROWS

PREV. PAGE

NEXT PAGE: Select a block

LCTRL + R:          Randomize the select columns of a selection, works similar to CTRL + I (interpolating them)

LCTRL + U:          Transpose the note of a selection to 1 seminote higher

LCTRL + D:          Transpose the note of a selection to 1 seminote lower

LCTRL + LSHIFT + U: Transpose the note of a selection to 1 seminote higher (only for the current instrument)

LCTRL + LSHIFT + D: Transpose the note of a selection to 1 seminote lower  (only for the current instrument)

LCTRL + H:          Transpose the note of a selection to 1 octave higher

LCTRL + L:          Transpose the note of a selection to 1 octave lower

LCTRL + LSHIFT + H: Transpose the note of a selection to 1 octave higher (only for the current instrument)

LCTRL + LSHIFT + L: Transpose the note of a selection to 1 octave lower (only for the current instrument)

LCTRL + W:          Save the current selection into a file


 Misc 


LALT + ENTER:     Switch between full screen / windowed mode

LALT + F4:        Exit program (Windows only)

LCTRL + S:         Save current module

LSHIFT + S:         Switch top right panel to synths list

LSHIFT + I:         Switch top right panel to instruments list


&lt;pre&gt;
C-x   xh xx xx hhhh             Volume 
B-x   xh xx xx hhhh             Jump to 
A#x  xh xx xx hhhh hhhh   Slide 
F-x    xh xx xx hhhh            Tempo 
D-x   xh xx xx hhhh             Pattern Break 
G#x  xh xx xx hhhh
&lt;/pre&gt;

h Hex 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13

d Dec 01 02 03 04 05 06 07 08 09 10  11 12 13 14 15 16 17 18 19

The Set Volume command: C. Input a note, then move the cursor to the effects command column and type a C. Play the pattern, and you shouldn't be able to hear the note you placed the C by. This is because the effect parameters are 00. Change the two zeros to a 40(Hex)/64(Dec), depending on what your tracker uses. Play back the pattern again, and the note should come in at full volume.

The Position Jump command next. This is just a B followed by the position in the playing list that you want to jump to. One thing to remember is that the playing list always starts at 0, not 1. This command is usually in Hex.

Onto the volume slide command: A. This is slightly more complex (much more if you're using a newer tracker, if you want to achieve the results here, then set slides to Amiga, not linear), due to the fact it depends on the secondary tempo. For now set a secondary tempo of 06 (you can play around later), load a long or looped sample and input a note or two. A few rows after a note type in the effect command A. For the parameters use 0F. Play back the pattern, and you should notice that when the effect kicks in, the sample drops to a very low volume very quickly. Change the effect parameters to F0, and use a low volume command on the note. Play back the pattern, and when the slide kicks in the volume of the note should increase very quickly.
This because each part of the effect parameters for command A does a different thing. The first number slides the volume up, and the second slides it down. It's not recommended that you use both a volume up and volume down at the same time, due to the fact the tracker only looks for the first number that isn't set to 0. If you specify parameters of 8F, the tracker will see the 8, ignore the F, and slide the volume up. Using a slide up and down at same time just makes you look stupid. Don't do it...

The Set Tempo command: F, is pretty easy to understand. You simply specify the BPM (in Hex) that you want to change to. One important thing to note is that values of lower than 20 (Hex) sets the secondary tempo rather than the primary.

Another useful command is the Pattern Break: D. This will stop the playing of the current pattern and skip to the next one in the playing list. By using parameters of more than 00 you can also specify which line to begin playing from.

Command 3 is Portamento to Note. This slides the currently playing note to another note, at a specified speed. The slide then stops when it reaches the desired note. 
&lt;pre&gt;
   C-2 1 000 - Starts the note playing
   ---      000
   C-3    330 - Starts the slide to C-3 at a speed of 30.
   ---     300 - Continues the slide
   ---     300 - Continues the slide
&lt;/pre&gt;
Once the parameters have been set, the command can be input again without any parameters, and it'll still perform the same function unless you change the parameters. This memory function allows certain commands to function correctly, such as command 5, which is the Portamento to Note and Volume Slide command. Once command 3 has been set up command 5 will simply take the parameters from that and perform a Portamento to Note. Any parameters set up for command 5 itself simply perform a Volume Slide identical to command A at the same time as the Portamento to Note.

This memory function will only operate in the same channel where the original parameters were set up.
There are various other commands which perform two functions at once. They will be described as we come across them.

C-3  04  ..  ..  09  00 ---&gt; C-3  04  ..  ..  09  00

C-3  04  ..  ..  09  00 ---&gt; C-3  04  ..  ..  09  02

C-3  04  ..  ..  09  00 ---&gt; C-3  04  ..  ..  09  05

C-3  04  ..  ..  09  00 ---&gt; C-3  04  ..  ..  09  08

C-3  04  ..  ..  09  00 ---&gt; C-3  04  ..  ..  09  0A

C-3  04  ..  ..  09  00 ---&gt; C-3  04  ..  ..  09  0D

C-3  04  ..  ..  09  10 ---&gt; C-3  04  ..  ..  09  10

(You can also switch on the Slider Rec to On, and perform parameter-live-recording, such as cutoff transitions, resonance or panning tweaking, etc..)  Note: this command only works for volume/panning and fx datas columns.


The next command we'll look at is the Portamento up/down: 1 and 2. Command 1 slides the pitch up at a specified speed, and 2 slides it down. This command works in a similar way to the volume slide, in that it is dependent on the secondary tempo. Both these commands have a memory dependent on each other, if you set the slide to a speed of 3 with the 1 command, a 2 command with no parameters will use the speed of 3 from the 1 command, and vice versa.

Command 4 is Vibrato. Vibrato is basically rapid changes in pitch, just try it, and you'll see what I mean. Parameters are in the format of xy, where x is the speed of the slide, and y is the depth of the slide. One important point to remember is to keep your vibratos subtle and natural so a depth of 3 or less and a reasonably fast speed, around 8, is usually used. Setting the depth too high can make the part sound out of tune from the rest.
Following on from command 4 is command 6. This is the Vibrato and Volume Slide command, and it has a memory like command 5, which you already know how to use.

Command 7 is Tremolo. This is similar to vibrato. Rather than changing the pitch it slides the volume. The effect parameters are in exactly the same format.   vibrato effect (0x1dxy) x = speed y = depth (can't be used if arpeggio (0x1b) is turned on) 

&lt;pre&gt;
 C-7 00 .. .. 1B37 &lt;-  Turn Arpeggio effect on
  --- .. .. .. 0000
  --- .. .. .. 0000
  --- .. .. .. 0000
  --- .. .. .. 1B38 &lt;- Change datas
  --- .. .. .. 0000
  --- .. .. .. 0000
  --- .. .. .. 0000
  --- .. .. .. 1B00 &lt;- Turn it off
&lt;/pre&gt;

Command 9 is Sample Offset. This starts the playback of the sample from a different place than the start. The effect parameters specify the sample offset, but only very roughly. Say you have a sample which is 8765(Hex) bytes long, and you wanted it to play from position 4321(Hex). The effect parameter could only be as accurate as the 43 part, and it would ignore the 21.

Command B is the Playing List/Order Jump command. The parameters specify the position in the Playing List/Order to jump to. When used in conjunction with command D you can specify the position and the line to play from.

Command E is pretty complex, as it is used for a lot of different things, depending on what the first parameter is. Let's take a trip through each effect in order.
Command E0 controls the hardware filter on an Amiga, which, as a low pass filter, cuts off the highest frequencies being played back. There are very few players and trackers on other system that simulate this function, not that you should need to use it. The second parameter, if set to 1, turns on the filter. If set to 0, the filter gets turned off.

Commands E1/E2 are Fine Portamento Up/Down. Exactly the same functions as commands 1/2, except that they only slide the pitch by a very small amount. These commands have a memory the same as 1/2 as well.

Command E3 sets the Glissando control. If parameters are set to 1 then when using command 3, any sliding will only use the notes in between the original note and the note being slid to. This produces a somewhat jumpier slide than usual. The best way to understand is to try it out for yourself. Produce a slow slide with command 3, listen to it, and then try using E31.

Command E4 is the Set Vibrato Waveform control. This command controls how the vibrato command slides the pitch. Parameters are 0 - Sine, 1 - Ramp Down (Saw), 2 - Square. By adding 4 to the parameters, the waveform will not be restarted when a new note is played e.g. 5 - Sine without restart.

Command E5 sets the Fine Tune of the instrument being played, but only for the particular note being played. It will override the default Fine Tune for the instrument. The parameters range from 0 to F, with 0 being -8 and F being +8 Fine Tune. A parameter of 8 gives no Fine Tune. If you're using a newer tracker that supports more than -8 to +8 e.g. -128 to +128, these parameters will give a rough Fine Tune, accurate to the nearest 16.

Command E6 is the Jump Loop command. You mark the beginning of the part of a pattern that you want to loop with E60, and then specify with E6x the end of the loop, where x is the number of times you want it to loop.

Command E7 is the Set Tremolo Waveform control. This has exactly the same parameters as command E4, except that it works for Tremolo rather than Vibrato.

Command E9 is for Retriggering the note quickly. The parameter specifies the interval between the retrigs. Use a value of less than the current secondary tempo, or else the note will not get retrigged.

Command EA/B are for Fine Volume Slide Up/Down. Much the same as the normal Volume Slides, except that these are easier to control since they don't depend on the secondary tempo. The parameters specify the amount to slide by e.g. if you have a sample playing at a volume of 08 (Hex) then the effect EA1 will slide this volume to 09 (Hex). A subsequent effect of EB4 would slide this volume down to 05 (Hex).

Command EC is the Note Cut. This sets the volume of the currently playing note to 0 at a specified tick. The parameters should be lower than the secondary tempo or else the effect won't work.

Command ED is the Note Delay. This should be used at the same time as a note is to be played, and the parameters will specify the number of ticks to delay playing the note. Again, keep the parameters lower than the secondary tempo, or the note won't get played!

Command EE is the Pattern Delay. This delays the pattern for the amount of time it would take to play a certain number of rows. The parameters specify how many rows to delay for.

Command EF is the Funk Repeat command. Set the sample loop to 0-1000. When EFx is used, the loop will be moved to 1000- 2000, then to 2000-3000 etc. After 9000-10000 the loop is set back to 0- 1000. The speed of the loop &quot;movement&quot; is defined by x. E is two times as slow as F, D is three times as slow as F etc. EF0 will turn the Funk Repeat off and reset the loop (to 0-1000).

effects 0x41 and 0x42 to control the volumes of the 2 303 units

There is a dedicated panel for synth parameter editing with coherent sections (osc, filter modulation, routing, so on) the interface is much nicer, much better to navigate with customizable colors, the reverb is now customizable (10 delay lines), It accepts newer types of Waves (higher bit rates, at least 24). Has a replay routine.

It's pretty much your basic VA synth. The problem isn't with the sampler being to high it's the synth is tuned two octaves too low, but if you want your samples tuned down just set the base note down 2 octaves (in the instrument panel).

so the synth is basically divided into 3 sections from left to right: oscillators/envelopes, then filter and LFO's, and in the right column you have mod routings and global settings.

for the oscillator section you have two normal oscillators (sine, saw, square, noise), the second of which is tunable, the first one tunes with the key pressed. Attached to OSC 1 is a sub-oscillator, which is a sawtooth wave tuned one octave down. The phase modulation controls the point in the duty cycle at which the oscillator starts. The ADSR envelope sliders (grouped with oscs) are for modulation envelope 1 and 2 respectively. you can use the synth as a sampler by choosing the instrument at the top.

In the filter column, the filter settings are: 1 = lowpass, 2 = highpass, 3 = off. cutoff and resonance. For the LFOs they are LFO 1 and LFO 2, the ADSR sliders in those are for the LFO itself.

For the modulation routings you have ENV 1, LFO 1 for the first slider and ENV 2, LFO 2 for the second, you can cycle through the individual routings there, and you can route each modulation source to multiple destinations of course, which is another big plus for this synth. Finally the glide time is for portamento and master volume, well, the master volume... it can go quite loud.

The sequencer is changed too, It's more like the one in AXS if you've used that, where you can mute tracks to re-use patterns with variation.


&lt;pre&gt;
Support for the following modules formats:
669 (Composer 669, Unis 669), 
AMF (DSMI Advanced Module Format), 
AMF (ASYLUM Music Format V1.0), 
APUN (APlayer), DSM (DSIK internal format), 
FAR (Farandole Composer), 
GDM (General DigiMusic), 
IT (Impulse Tracker), 
IMF (Imago Orpheus), 
MOD (15 and 31 instruments), 
MED (OctaMED), 
MTM (MultiTracker Module editor), 
OKT (Amiga Oktalyzer), 
S3M (Scream Tracker 3), 
STM (Scream Tracker), 
STX (Scream Tracker Music Interface Kit), 
ULT (UltraTracker), 
UNI (MikMod), 
XM (FastTracker 2),
Mid (midi format via timidity)
&lt;/pre&gt;


Possible plugin options include [http://lv2plug.in/ LV2],


====Midi - Musical Instrument Digital Interface====

A midi file typically contains music that plays on up to 16 channels (as per the midi standard), but many notes can simultaneously play on each channel (depending on the limit of the midi hardware playing it).

'''Timidity'''

Although usually already installed, you can uncompress the [http://www.libsdl.org/projects/SDL_mixer/ timidity.tar.gz (14MB)] into a suitable drawer like below's SYS:Extras/Audio/ 
 assign timidity: SYS:Extras/Audio/timidity
added to SYSːs/User-Startup

'''WildMidi playback'''


'''Audio Evolution 4 (2003) 4.0.23 (from 2012)'''


*Sync Menu    - CAMD Receive, Send checked 
*Options Menu - MIDI Machine Control - Midi Bar Display - Select CAMD MIDI in / out - Midi Remote Setup 


MCB Master Control Bus 
*Sending a MIDI start-command and a Song Position Pointer, you can synchronize audio with an external MIDI sequencer (like B&amp;P). 
*B&amp;P Receive, start AE, add AudioEvolution.ptool in Bars&amp;Pipes track, press play / record in AE then press play in Pipes 
*CAMD Receive, receive MIDI start or continue commands via camd.library sync to AE 


*MIDI Machine Control
*Midi Bar Display 
*Select CAMD MIDI in / out
*Midi Remote Setup - open requester for external MIDI controllers to control app mixer and transport controls cc remotely 
 Channel   - mixer(vol, pan, mute, solo), eq, aux, fx, 
 Subgroup  - Volume, Mute, Solo 
 Transport - Start, End, Play, Stop, Record, Rewind, Forward 
 Misc      - Master vol., Bank Down, Bank up 


&lt;pre&gt;
q        - quit 

First 3 already opened when AE started 
F1       - timeline window
F2       - mixer 
F3       - control 
F4       - subgroups 
F5       - aux returns 
F6       - sample list 

i        - Load sample to use 

space    - start/stop play 
b        - reset time 0:00


s        - split mode 
r        - open recording window 
a        - automation edit mode with p panning, m mute and v volume 


[ / ]    - zoom in / out 
:        - previous track
*        - next track 

x c v f  - cut copy paste cross-fade 
g        - snap grid 


&lt;/pre&gt;


 '''[http://bnp.hansfaust.de/ Bars n Pipes sequencer]'''

 BarsnPipes debug ... in shell 

Menu (right mouse)  
*Song        - Songs load and save in .song format but option here to load/save Midi_Files .mid in FORMAT0 or FORMAT1 
*Track       - 
*Edit        -
*Tool        - 
*Timing      - SMTPE Synchronizing 
*Windows     - 
*Preferences - Multiple MIDI-in option 

Windows (some of these are usually already opened when Bars n Pipes starts up for the first time) 
*Workflow -&gt; Tracks, .... Song Construction, Time-line Scoring, Media Madness, Mix Maestro, 
*Control  -&gt; Transport (or mini one), Windows (which collects all the Windows icons together-shortcut), .... Toolbox, Accessories, Metronome, 

Once you have your windows placed on the screen that suits your workflow, Song -&gt; Save as Default will save the positions, colors, icons, etc as you'd like them 

If you need a particular setup of Tracks, Tools, Tempos etc, you save them all as a new song you can load each time 

Right mouse menu -&gt; Preferences -&gt; Environment... -&gt; ScreenMode  - Linkages for Synch (to Slave) usbmidi.out.0 and Send (Master) usbmidi.in.0 - Clock MTC 


'''Tracks'''

#Double-click on B&amp;P's icon. B&amp;P will then open with an empty Song. You can also double-click on a song icon to open a song in B&amp;P.
#Choose a track. The B&amp;P screen will contain a Tracks Window with a number of tracks shown as pipelines (Track 1, Track 2, etc...). To choose a track, simply click on the gray box to show an arrow-icon to highlight it. This icon show whether a track is chosen or not. To the right of the arrow-icon, you can see the icon for the midi-input. If you double-click on this icon you can change the MIDI-in setup.
#Choose Record for the track. To the right of the MIDI-input channel icon you can see a pipe. This leads to another clickable icon with that shows either P, R or M. This stands for Play, Record or Merge. To change the icon, simply click on it. If you choose P, this track can only play the track (you can't record anything). If you choose R, you can record what you play and it overwrites old stuff in the track. If you choose M, you merge new records with old stuff in the track. Choose R now to be able to make a record.
#Chose MIDI-channel. On the most right part of the track you can see an icon with a number in it. This is the MIDI-channel selector. Here you must choose a MIDI-channel that is available on your synthesizer/keyboard. If you choose General MIDI channel 10, most synthesizer will play drum sounds. To the left of this icon is the MIDI-output icon. Double-click on this icon to change the MIDI-output configuration.
#Start recording. The next step is to start recording. You must then find the control buttons (they look like buttons on a CD-player). To be able to make a record. you must click on the R icon. You can simply now press the play button (after you have pressed the R button) and play something on you keyboard. To playback your composition, press the Play button on the control panel.
#Edit track. To edit a track, you simply double click in the middle part of a track. You will then get a new window containing the track, where you can change what you have recorded using tools provided. Take also a look in the drop-down menus for more features.


Videos to help understand [https://www.youtube.com/watch?v=A6gVTX-9900 small intro], [https://www.youtube.com/watch?v=abq_rUTiSA4&amp;t=3s Overview], [https://www.youtube.com/watch?v=ixOVutKsYQo Workplace Setup CC PC Sysex], [https://www.youtube.com/watch?v=dDnJLYPaZTs Import Song], [https://www.youtube.com/watch?v=BC3kkzPLkv4 Tempo Mapping], [https://www.youtube.com/watch?v=sd23kqMYPDs ptool Arpeggi-8], [https://www.youtube.com/watch?v=LDJq-YxgwQg  PlayMidi Song], [https://www.youtube.com/watch?v=DY9Pu5P9TaU Amiga Midi], [https://www.youtube.com/watch?v=abq_rUTiSA4 Learning Amiga bars and Pipes], 

Groups like [https://groups.io/g/barsnpipes/topics this] could help 


'''Tracks window'''

* blue &quot;1 2 3 4 5 6 7 8 Group&quot; and transport tape deck VCR-type controls
* Flags 
* [http://theproblem.alco-rhythm.com/org/bp.html Track 1, Track2, to Track 16, on each Track there are many options that can be activated] 

Each Track has a 

*Left LHS  - Click in grey box to select what Track to work on, Midi-In ptool icon should be here (5pin plug icon), and many more from the Toolbox on the Input Pipeline 
*Middle    - (P, R, M) Play, Record, Merge/Multi before the sequencer line and a blue/red/yellow (Thru Mute Play) Tap 
*Right RHS - Output pipeline, can have icons placed uopn it with the final ptool icon(s) being the 5pin icon symbol for Midi-OUT 

Clogged pipelines may need Esc pressed several times 


'''Toolbox (tools affect the chosen pipeline)'''

After opening the Toolbox window you can add extra Tools (.ptool) for the pipelines like keyboard(virtual), midimonitor, quick patch, transpose, triad, (un)quantize, feedback in/out, velocity etc
 right mouse -&gt; Toolbox menu option -&gt; Install Tool... and navigate to Tool drawer (folder) and select requried .ptool 

Accompany B tool to get some sort of rythmic accompaniment, Rythm Section and Groove Quantize are examples of other tools that make use of rythms
[https://aminet.net/search?query=bars Bars &amp; Pipes pattern format .ptrn] for drawer (folder). Load from the Menu as Track or Group 


'''Accessories (affect the whole app)''' 

Accessories -&gt; Install... and goto the Accessories drawer for .paccess like adding ARexx scripting support 


'''Song Construction'''
&lt;pre&gt;
F1  Pencil
F2  Magic Wand
F3  Hand 
F4  Duplicator 
F5  Eraser 
F6  Toolpad 
F7  Bounding box 
F8  Lock to A-B-A 

A-B-A strip, section, edit flags, white boxes, 

&lt;/pre&gt;


Bars&amp;Pipes Professional offers three track formats; basic song tracks, linear tracks — which don't loop — and finally real‑time tracks. The difference between them is that both song and linear tracks respond to tempo changes, while real‑time tracks use absolute timing, always trigger at the same instant regardless of tempo alterations 

'''Tempo Map'''

F1  Pencil
F2  Magic Wand
F3  Hand 
F4  Eraser 
F5  Curve 
F6  Toolpad 


Compositions

Lyrics, Key, Rhythm, Time Signature 

'''Master Parameters'''

Key, Scale/Mode

'''Track Parameters'''

Dynamics 


'''Time-line Scoring'''


'''Media Madness'''


'''Mix Maestro'''


*ACCESSORIES         Allows the importation of other packages and additional modules 
*CLIPBOARD           Full cut, copy and paste operations, enabling user‑definable clips to be shared between tracks.
*INFORMATION         A complete rundown on the state of the current production and your machine.
*MASTER PARAMETERS   Enables global definition of time signatures, lyrics, scales, chords, dynamics and rhythm changes.
*MEDIA MADNESS       A complete multimedia sequencer which allows samples, stills, animation, etc 
*METRONOME           Tempo feedback via MIDI, internal Amiga audio and colour cycling — all three can be mixed and matched as required.
*MIX MAESTRO         Completely automated mixdown with control for both volume and pan. All fader alterations are memorised by the software 
*RECORD ACTIVATION   Complete specification of the data to be recorded/merged. Allows overdubbing of pitch‑bend, program changes, modulation etc
*SET FLAGS           Numeric positioning of location and edit flags in either SMPTE or musical time 
*SONG CONSTRUCTION   Large‑scale cut and paste of individual measures, verses or chorus, by means of bounding box and drag‑n‑drop mouse selections
*TEMPO MAP           Tempo change using a variety of linear and non‑linear transition curves 
*TEMPO PALETTE       Instant tempo changes courtesy of four user‑definable settings.
*TIMELINE SCORING    Sequencing of a selection of songs over a defined period — ideal for planning an entire set for a live performance.
*TOOLBOX             Selection screen for the hundreds of signal‑processing tools available 
*TRACKS              Opens the main track window to enable recording, editing and the use of tools.
*TRANSPORT           Main playback control window, which also provides access to user‑ defined flags, loop and punch‑in record modes.


Bars and Pipes Pro 2.5 is using internal 4-Byte IDs, to check which kind of data are currently processed.
Especially in all its files the IDs play an important role. The IDs are stored into the file in the same order they are laid out in the memory.

In a Bars 'N' Pipes file (no matter which kind) the ID &quot;NAME&quot; (saved as its ANSI-values) is stored on a big endian system (68k-computer) as &quot;NAME&quot;. On a little endian system (x86 PC computer) as &quot;EMAN&quot;.  The target is to make the AROS-BnP compatible to songs, which were stored on a 68k computer (AMIGA).

If possible, setting MIDI channels for Local Control for your keyboard 

http://www.fromwithin.com/liquidmidi/archive.shtml


MIDI files are essentially a stream of event data. An event can be many things, but typically &quot;note on&quot;, &quot;note off&quot;, &quot;program change&quot;, &quot;controller change&quot;, or messages that instruct a MIDI compatible synth how to play a given bit of music.

* Channel     - 1 to 16 -
* Messages    - PC presets, CC effects like delays, reverbs,  etc 
* Sequencing  - MIDI instruments, Drums, Sound design, 
* Recording   - 
* GUI         - Piano roll or Tracker, Staves and Notes 

MIDI events/messages like step entry e.g. Note On, Note Off 

MIDI events/messages like PB, PC, CC, Mono and Poly After-Touch, Sysex, etc 

MIDI sync - Midi Clocks (SPS Measures), Midi Time Code (h, m, s and frames) SMPTE 

Individual track editing with audition edits so easier to test any changes. Possible to stop track playback, mix clips from the right edit flag and scroll the display using arrow keys. 

Step entry, to extend a selected note hit the space bar and the note grows accordingly. Ability to cancel mouse‑driven edits by simply clicking the right mouse button — at which point everything snaps back into its original form. Lyrics can now be put in with syllable dividers, even across an entire measure or section. Autoranging when you open a edit window, the notes are automatically displayed — working from the lowest upwards. 

Flag editing, shift‑click on a flag immediately open the bounds window, ready for numeric input. Ability to cancel edits using the right‑hand mouse button, plus much improved Bounding Box operations.

Icons other than the BarsnPipes icon -&gt; PUBSCREEN=BarsnPipes (cannot choose modes higher than 8bit 256 colors)

Preferences -&gt; Menu in Tracks window - Send MIDI defaults OFF 

Prefs -&gt; Environment -&gt; screenmode (saved to BarsnPipes.prefs binary file) 

Customization -&gt; pics in gui drawer (folder) - 


Can save as .song files and .mid General Midi 

SMF is a “Standard Midi File”  ([http://www.music.mcgill.ca/~ich/classes/mumt306/StandardMIDIfileformat.html SMF0, SMF1 and SMF2]), [https://github.com/stump/libsmf libsmf], [https://github.com/markc/midicomp MIDIcomp], [https://github.com/MajicDesigns/MD_MIDIFile C++ src], [], [https://github.com/newdigate/midi-smf-reader Midi player], 

* SMF0        All MIDI data is stored in one track only, separated exclusively by the MIDI channel.
* SMF1        The MIDI data is stored in separate tracks/channels.
* SMF2 (rarely used) The MIDI data is stored in separate tracks, which are additionally wrapped in containers, so it's possible to have e.g. several tracks using the same MIDI channels.


Would it be possible to enrich Bars N’Pipes with software synth and sample support along with audio recording and mastering tools like in the named MAC or PC music sequencers?
On the classic AMIGA-OS this is not possible because of missing CPU-power. The hardware of the classic AMIGA is not further developed. So we must say (unfortunately) that those dreams can’t become reality

BarsnPipes is best used with external MIDI-equipment. This can be a keyboard or synthesizer with MIDI-connectors. 

&lt;pre&gt;
MIDI can control 16 channels 
There are USB-MIDI-Interfaces on the market with 16 independent MIDI-lines (multi-port), which can handle 16 MIDI devices independently – 16×16 = 256 independent MIDI-channels or instruments 
handle up to 16 different USB-MIDI-Interfaces (multi-device). That is: 16X16X16 = 4096 independent MIDI-channels – theoretically 
&lt;/pre&gt;

&lt;pre&gt;
Librarian MIDI SYStem EXplorer (sysex) - PatchEditor and used to be supplied as a separate program like PatchMeister but currently not at present 
It should support MIDI.library (PD), BlueRibbon.library (B&amp;P), TriplePlayPlus, and CAMD.library (DeluxeMusic) and 
MIDI information from a device's user manual and configure a custom interface to access parameters for all MIDI products connected to the system 
Supports ALL MIDI events and the Patch/Librarian data is stored in MIDI standard format 
Annette M.Crowling, Missing Link Software, Inc.
&lt;/pre&gt;


Composers
&lt;pre&gt;
[https://x.com/hirasawa/status/1403686519899054086 Susumu Hirasawa] 

&lt;/pre&gt;


&lt;pre&gt;
1988 Todor Fay and his wife Melissa Jordan Gray, who founded the Blue Ribbon Inc
1992 Bars&amp;Pipes Pro published 
November 2000, Todor Fay announcement to release the sourcecode of Bars&amp;Pipes Pro 2.5c beta
end of May 2001, the source of the main program and the sources of some tools and accessories were in a complete and compileable state 
end of October 2009 stop further development of BarsnPipes New for now on all supported systems and made freeware 
2013 Alfred Faust diagnosed with incureable illness, called „Myastenia gravis“ (weak muscles) 
&lt;/pre&gt;


 Protrekkr

How to use Midi In/Out in Protrekkr ?

First of all, midi in &amp; out capabilities of this program are rather limited.

# Go to Misc. Setup section and select a midi in or out device to use (ptk only supports one device at a time).
# Go to instrument section, and select a MIDI PRG (the default is N/A, which means no midi program selected).
# Go to track section and here you can assign a midi channel to each track of ptk.
# Play notes :]. Note off works. F'x' note cut command also works too, and note-volume command (speed) is supported.

Also, you can change midicontrollers in the tracker, using '90' in the panning row:

&lt;pre&gt;
    C-3 02 .. .. 0000....


    --- .. .. 90 xxyy.... &lt;&lt; This will set the value 
    --- .. .. .. 0000....    of the controller n.'xx' to 'yy' (both in hex)
    --- .. .. .. 0000....
&lt;/pre&gt;

So &quot;--- .. .. 90 2040....&quot; will set the controller number $20(32) to $40(64).

You will need the midi implementation table of your gear to know what you can change with midi controller messages.

 N.B. Not all MIDI devices are created equal!

Although the MIDI specification defines a large range of MIDI messages of various kinds, not every MIDI device is required to work in exactly the same way and respond to all the available messages and ways of working. For example, we don't expect a wind synthesiser to work in the same way as a home keyboard.

Some devices, the older ones perhaps, are only able to respond to a single channel. With some of those devices that channel can be altered from the default of 1 (probably) to another channel of the 16 possible.

Other devices, for instance monophonic synthesisers, are capable of producing just one note at a time, on one MIDI channel. Others can produce many notes spread across many channels.

Further devices can respond to, and transmit, &quot;breath controller&quot; data (MIDI controller number 2 (CC#2)) others may respond to the reception of CC#2 but not be able to create and to send it.

A controller keyboard may be capable of sending &quot;expression pedal&quot; data, but another device may not be capable of responding to that message.

Some devices just have the basic GM sound set. The &quot;voice&quot; or &quot;instrument&quot; is selected using a &quot;Program Change&quot; message on its own.

Other devices have a greater selection of voices, usually arranged in &quot;banks&quot;, and the choice of instrument is made by responding to &quot;Bank Select MSB&quot; (MIDI controller 0 (CC#0)), others use &quot;Bank Select LSB&quot; (MIDI controller number 32 (CC#32)), yet others use both MSB and LSB sent one after the other, all followed by the Program Change message. The detailed information about all the different voices will usually be available in a published MIDI Data List.


 MIDI Implementation Chart

But in the User Manual there is sometimes a summary of how the device works, in terms of MIDI, in the chart at the back of the manual, the MIDI Implementation Chart.

If you require two devices to work together you can compare the two implementation charts to see if they are &quot;compatible&quot;. In order to do this we will need to interpret that chart.

The chart is divided into four columns headed &quot;Function&quot;, &quot;Transmitted&quot; (or &quot;Tx&quot;), &quot;Received&quot; (or &quot;Rx&quot;), or more correctly &quot;Recognised&quot;, and finally, &quot;Remarks&quot;.

&lt;pre&gt;
The left hand column defines which MIDI functions are being described.
The 2nd column defines what the device in question is capable of transmitting to another device.
The 3rd column defines what the device is capable of responding to.
The 4th column is for explanations of the values contained within these previous two columns.
&lt;/pre&gt;

There should then be twelve sections, with possibly a thirteenth containing extra &quot;Notes&quot;. Finally there should be an explanation of the four MIDI &quot;modes&quot; and what the &quot;X&quot; and the &quot;O&quot; mean.
&lt;pre&gt;
Mode 1: Omni On, Poly; 
Mode 2: Omni On, Mono; 
Mode 3: Omni Off, Poly; 
Mode 4: Omni Off, Mono.
&lt;/pre&gt;
O means &quot;yes&quot; (implemented), X means &quot;no&quot; (not implemented).

Sometimes you will find a row of asterisks &quot;**************&quot;, these seem to indicate that the data is not applicable in this case. Seen in the transmitted field only (unless you've seen otherwise).

Lastly you may find against some entries an asterisk followed by a number e.g. *1, these will refer you to further information, often on a following page, giving more detail.

Basic Channel
But the very first set of boxes will tell us the &quot;Basic Channel(s)&quot; that the device sends or receives on. 
&quot;Default&quot; is what happens when the device is first turned on, &quot;changed&quot; is what a switch of some kind may allow the device to be set to. 
For many devices e.g. a GM sound module or a home keyboard, this would be 1-16 for both. That is it can handle sending and receiving on all MIDI channels.

On other devices, for example a synthesiser, it may by default only work on channel 1. But the keyboard could be &quot;split&quot; with the lower notes e.g. on channel 2. If the synth has an arppegiator, this may be able to be set to transmit and or receive on yet another channel.
So we might see the default as &quot;1&quot; but the changed as &quot;1-16&quot;.

Modes.
We need to understand Omni On and Off, and Mono and Poly, then we can decipher the four modes.

But first we need to understand that any of these four Mode messages can be sent to any MIDI channel. They don't necessarily apply to the whole device.

If we send an &quot;Omni On&quot; message (CC#125) to a MIDI channel of a device, we are, in effect, asking it to respond to e.g. a Note On / Off message pair, received on any of the sixteen channels. Sound strange? Read it again. Still strange? It certainly is. We normally want a MIDI channel to respond only to Note On / Off messages sent on that channel, not any other. In other words, &quot;Omni Off&quot;.

So &quot;Omni Off&quot; (CC#124) tells a channel of our MIDI device to respond only to messages sent on that MIDI channel.

&quot;Poly&quot; (CC#127) is for e.g. a channel of a polyphonic sound module, or a home keyboard, to be able to respond to many simultaneous Note On / Off message pairs at once and produce musical chords.

&quot;Mono&quot; (CC#126) allows us to set a channel to respond as if it were e.g. a flute or a trumpet, playing just one note at a time. If the device is capable of it, then the overlapping of notes will produce legato playing, that is the attack portion of the second note of two overlapping notes will be removed resulting in a &quot;smoother&quot; transition.

So a channel with a piano voice assigned to it will have Omni Off, Poly On (Mode 3), a channel with a saxophone voice assigned could be Omni Off, Mono On (Mode 4).

We call these combinations the four modes, 1 to 4, as defined above. 
Most modern devices will have their channels set to Mode 3 (Omni Off, Poly) but be switchable, on a per channel basis, to Mode 4 (Omni Off, Mono).

This second section of data will include first its default value i.e. upon device switch on. Then what Mode messages are acceptable, or X if none.

Finally, in the &quot;Altered&quot; field, how a Mode message that can't be implemented will be interpreted. Usually there will just be a row of asterisks effectively meaning nothing will be done if you try to switch to an unimplemented mode.

Note Number
&lt;pre&gt;
The next row will tell us which MIDI notes the device can send or receive, normally 0-127.
The second line, &quot;True Voice&quot; has the following in the MIDI specification: 
&quot;Range of received note numbers falling within the range of true notes produced by the instrument.&quot;
My interpretation is that, for instance, a MIDI piano may be capable of sending all MIDI notes (0 to 127) by transposition, but only responding to the 88 notes (21 to 108) of a real piano. 
&lt;/pre&gt;

Velocity
This will tell us whether the device we're looking at will handle note velocity, and what range from 1-127, or maybe just 64, it transmits or will recognise. So usually &quot;O&quot; plus a range or &quot;X&quot; for not implemented.

After touch
This may have one or two lines two it.
If a one liner the either &quot;O&quot; or &quot;X&quot;, yes or no.
If a two liner then it may include &quot;Keys&quot; or &quot;Poly&quot; and &quot;Channel&quot;.
This will show whether the device will respond to Polyphonic after touch or channel after touch or neither.

Pitch Bend
Again &quot;O&quot; for implemented, &quot;X&quot; for not implemented.
(Many stage pianos will have no pitch bend capability.)
It may also, in the notes section, state whether it will respond to the full 14 bits, or not, as usually encoded by the pitch bend wheel.

Control Change
This is likely to be the largest section of the chart.
It will list all those controllers, starting from CC#0, Bank Select MSB, which the device is capable of sending, and those that it will respond to using &quot;O&quot; or &quot;X&quot; respectively.
You will, almost certainly, get some further explanation of functionality in the remarks column, or in more detail elsewhere in the documentation.

Of course you will need to know what all the various controller numbers do. Lots of the official technical specifications can be found at the [www.midi.org/techspecs/ MMA], with the table of messages and control change [www.midi.org/techspecs/midimessages.php message numbers]

Program Change
Again &quot;O&quot; or &quot;X&quot; in the Transmitted or Recognised column to indicate whether or not the feature is implemented. In addition a range of numbers is shown, typically 0-127, to show what is available.
True # (number): &quot;The range of the program change numbers which correspond to the actual number of patches selected.&quot;

System Exclusive
Used to indicate whether or not the device can send or recognise System Exclusive messages. A short description is often given in the Remarks field followed by a detailed explanation elsewhere in the documentation.

System Common - These include the following:
&lt;pre&gt;
MIDI Time Code Quarter Frame messages (device synchronisation).
Song Position Pointer
Song Select
Tune Request
&lt;/pre&gt;
The section will indicate whether or not the device can send or respond to any of these messages.

System Real Time
These include the following:
&lt;pre&gt;
Timing Clock - often just written as &quot;Clock&quot;
Start
Stop
Continue
&lt;/pre&gt;
These three are usually just referred to as &quot;Commands&quot; and listed.
Again the section will indicate which, if any, of these messages the device can send or respond to.
&lt;pre&gt;
Aux. Messages
Again &quot;O&quot; or &quot;X&quot; for implemented or not.
Aux. = Auxiliary.
Active Sense = Active Sensing.
&lt;/pre&gt;
Often with an explanation of the action of the device.

Notes
The &quot;Notes&quot; section can contain any additional comments to clarify the particular implementation.

Some of the explanations have been drawn directly from the MMA MIDI 1.0 Detailed Specification.
And the detailed explanation of some of the functions will be found there, or in the General MIDI System Level 1 or General MIDI System Level 2 documents also published by the MMA.


 OFFICIAL MIDI SPECIFICATIONS

SUMMARY OF MIDI MESSAGES
Table 1 - Summary of MIDI Messages

The following table lists the major MIDI messages in numerical (binary) order (adapted from &quot;MIDI by the Numbers&quot; by D. Valenti, Electronic Musician 2/88, and updated by the MIDI Manufacturers Association.). This table is intended as an overview of MIDI, and is by no means complete.

WARNING! Details about implementing these messages can dramatically impact compatibility with other products. We strongly recommend consulting the official MIDI Specifications for additional information.

MIDI 1.0 Specification

Message Summary Channel Voice Messages [nnnn = 0-15 (MIDI Channel Number 1-16)]

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;10%&quot;  |Status D7----D0 
! width=&quot;10%&quot;  |Data Byte(s) D7----D0 
! width=&quot;20%&quot;  |Description
|-
|&lt;!--Status--&gt;1000nnnn || &lt;!--Data--&gt;0kkkkkkk 0vvvvvvv || &lt;!--Description--&gt;Note Off event. 
This message is sent when a note is released (ended). (kkkkkkk) is the key (note) number. (vvvvvvv) is the velocity.
|-
|&lt;!--Status--&gt;1001nnnn || &lt;!--Data--&gt;0kkkkkkk 0vvvvvvv || &lt;!--Description--&gt;Note On event. 
This message is sent when a note is depressed (start). (kkkkkkk) is the key (note) number. (vvvvvvv) is the velocity.
|-
|&lt;!--Status--&gt;1010nnnn || &lt;!--Data--&gt;0kkkkkkk 0vvvvvvv || &lt;!--Description--&gt;Polyphonic Key Pressure (Aftertouch). 
This message is most often sent by pressing down on the key after it &quot;bottoms out&quot;. (kkkkkkk) is the key (note) number. (vvvvvvv) is the pressure value.
|-
|&lt;!--Status--&gt;1011nnnn || &lt;!--Data--&gt;0ccccccc 0vvvvvvv || &lt;!--Description--&gt;Control Change. 
This message is sent when a controller value changes. Controllers include devices such as pedals and levers. Controller numbers 120-127 are reserved as &quot;Channel Mode Messages&quot; (below). (ccccccc) is the controller number (0-119). (vvvvvvv) is the controller value (0-127).
|-
|&lt;!--Status--&gt;1100nnnn || &lt;!--Data--&gt;0ppppppp || &lt;!--Description--&gt;Program Change. This message sent when the patch number changes. (ppppppp) is the new program number.
|-
|&lt;!--Status--&gt;1101nnnn || &lt;!--Data--&gt;0vvvvvvv || &lt;!--Description--&gt;Channel Pressure (After-touch). This message is most often sent by pressing down on the key after it &quot;bottoms out&quot;. This message is different from polyphonic after-touch. Use this message to send the single greatest pressure value (of all the current depressed keys). (vvvvvvv) is the pressure value.
|-
|&lt;!--Status--&gt;1110nnnn || &lt;!--Data--&gt;0lllllll 0mmmmmmm || &lt;!--Description--&gt;Pitch Bend Change. This message is sent to indicate a change in the pitch bender (wheel or lever, typically). The pitch bender is measured by a fourteen bit value. Center (no pitch change) is 2000H. Sensitivity is a function of the receiver, but may be set using RPN 0. (lllllll) are the least significant 7 bits. (mmmmmmm) are the most significant 7 bits.
|}

Channel Mode Messages (See also Control Change, above)

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;10%&quot;  |Status D7----D0 
! width=&quot;10%&quot;  |Data Byte(s) D7----D0 
! width=&quot;20%&quot;  |Description
|-
|&lt;!--Status--&gt;1011nnnn || &lt;!--Data--&gt;0ccccccc 0vvvvvvv || &lt;!--Description--&gt;Channel Mode Messages. 
This the same code as the Control Change (above), but implements Mode control and special message by using reserved controller numbers 120-127. The commands are:
*All Sound Off. When All Sound Off is received all oscillators will turn off, and their volume envelopes are set to zero as soon as possible c = 120, v = 0: All Sound Off
*Reset All Controllers. When Reset All Controllers is received, all controller values are reset to their default values. (See specific Recommended Practices for defaults) c = 121, v = x: Value must only be zero unless otherwise allowed in a specific Recommended Practice.
*Local Control. When Local Control is Off, all devices on a given channel will respond only to data received over MIDI. Played data, etc. will be ignored. Local Control On restores the functions of the normal controllers. 
c = 122, v = 0: Local Control Off
c = 122, v = 127: Local Control On
* All Notes Off. When an All Notes Off is received, all oscillators will turn off. 
c = 123, v = 0: All Notes Off (See text for description of actual mode commands.)
c = 124, v = 0: Omni Mode Off 
c = 125, v = 0: Omni Mode On 
c = 126, v = M: Mono Mode On (Poly Off) where M is the number of channels (Omni Off) or 0 (Omni On) 
c = 127, v = 0: Poly Mode On (Mono Off) (Note: These four messages also cause All Notes Off)
|}

System Common Messages

System Messages (0xF0)

The final status nybble is a “catch all” for data that doesn’t fit the other statuses. They all use the most significant nybble (4bits) of 0xF, with the least significant nybble indicating the specific category.

The messages are denoted when the MSB of the second nybble is 1. When that bit is a 0, the messages fall into two other subcategories.

System Common

If the MSB of the second second nybble (4 bits) is not set, this indicates a System Common message. Most of these are messages that include some additional data bytes.

System Common Messages
Type Status Byte   Number of Data Bytes      Usage 
&lt;pre&gt;
Time Code Quarter Frame	0xF1	1	Indicates timing using absolute time code, primarily for synthronization with video playback systems. A single location requires eight messages to send the location in an encoded hours:minutes:seconds:frames format*.
Song Position	0xF2	2	Instructs a sequencer to jump to a new position in the song. The data bytes form a 14-bit value that expresses the location as the number of sixteenth notes from the start of the song.
Song Select	0xF3	1	Instructs a sequencer to select a new song. The data byte indicates the song.
Undefined	0xF4	0	
Undefined	0xF5	0	
Tune Request	0xF6	0	Requests that the receiver retunes itself**.
&lt;/pre&gt;
*MIDI Time Code (MTC) is significantly complex. Please see the MIDI Specification
**While modern digital instruments are good at staying in tune, older analog synthesizers were prone to tuning drift. Some analog synthesizers had an automatic tuning operation that could be initiated with this command.


System Exclusive

If you’ve been keeping track, you’ll notice there are two status bytes not yet defined: 0xf0 and 0xf7. These are used by the System Exclusive message, often abbreviated at SysEx. SysEx provides a path to send arbitrary data over a MIDI connection. There is a group of predefined messages for complex data, like fine grained control of MIDI Time code machinery. SysEx is also used to send manufacturer defined data, such as patches, or even firmware updates.

System Exclusive messages are longer than other MIDI messages, and can be any length. The messages are of the following format:

0xF0, 0xID, 0xdd, ...... 0xF7
The message is bookended with distinct bytes.

It opens with the Start Of Exclusive (SOX) data byte, 0xF0.
The next one to three bytes after the start are an identifier.
Values from 0x01 to 0x7C are one-byte vendor IDs, assigned to manufacturers who were involved with MIDI at the beginning.
If the ID is 0x00, it’s a three-byte vendor ID - the next two bytes of the message are the value.
&lt;pre&gt;
ID 0x7D is a placeholder for non-commercial entities.
ID 0x7E indicates a predefined Non-realtime SysEx message.
ID 0x7F indicates a predefined Realtime SysEx message.
&lt;/pre&gt;
After the ID is the data payload, sent as a stream of bytes.
The transfer concludes with the End of Exclusive (EOX) byte, 0xF7.
The payload data must follow the guidelines for MIDI data bytes – the MSB must not be set, so only 7 bits per byte are actually usable. If the MSB is set, it falls into three possible scenarios.

An End of Exclusive byte marks the ordinary termination of the SysEx transfer.
System Real Time messages may occur within the transfer without interrupting it. The recipient should handle them independently of the SysEx transfer.
Other status bytes implicitly terminate the SysEx transfer and signal the start of new messages.
 Some inexpensive USB-to-MIDI interfaces aren’t capable of handling messages longer than four bytes.

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;10%&quot;  |Status D7----D0 
! width=&quot;10%&quot;  |Data Byte(s) D7----D0 
! width=&quot;20%&quot;  |Description
|-
|&lt;!--Status--&gt;11110000 || &lt;!--Data--&gt;0iiiiiii [0iiiiiii 0iiiiiii]  0ddddddd  --- --- 0ddddddd 11110111 || &lt;!--Description--&gt;System Exclusive. 
This message type allows manufacturers to create their own messages (such as bulk dumps, patch parameters, and other non-spec data) and provides a mechanism for creating additional MIDI Specification messages. The Manufacturer's ID code (assigned by MMA or AMEI) is either 1 byte (0iiiiiii) or 3 bytes (0iiiiiii 0iiiiiii 0iiiiiii). Two of the 1 Byte IDs are reserved for extensions called Universal Exclusive Messages, which are not manufacturer-specific. If a device recognizes the ID code as its own (or as a supported Universal message) it will listen to the rest of the message (0ddddddd). Otherwise, the message will be ignored. (Note: Only Real-Time messages may be interleaved with a System Exclusive.)
|-
|&lt;!--Status--&gt;11110001 || &lt;!--Data--&gt;0nnndddd || &lt;!--Description--&gt;MIDI Time Code Quarter Frame.
nnn = Message Type
dddd = Values
|-
|&lt;!--Status--&gt;11110010 || &lt;!--Data--&gt;0lllllll 0mmmmmmm || &lt;!--Description--&gt;Song Position Pointer. 
This is an internal 14 bit register that holds the number of MIDI beats (1 beat= six MIDI clocks) since the start of the song. l is the LSB, m the MSB.
|-
|&lt;!--Status--&gt;11110011 || &lt;!--Data--&gt;0sssssss || &lt;!--Description--&gt;Song Select. 
The Song Select specifies which sequence or song is to be played.
|-
|&lt;!--Status--&gt;11110100 || &lt;!--Data--&gt; || &lt;!--Description--&gt;Undefined. (Reserved)
|-
|&lt;!--Status--&gt;11110101 || &lt;!--Data--&gt; || &lt;!--Description--&gt;Undefined. (Reserved)
|-
|&lt;!--Status--&gt;11110110 || &lt;!--Data--&gt; || &lt;!--Description--&gt;Tune Request. Upon receiving a Tune Request, all analog synthesizers should tune their oscillators.
|-
|&lt;!--Status--&gt;11110111 || &lt;!--Data--&gt; || &lt;!--Description--&gt;End of Exclusive. Used to terminate a System Exclusive dump. 
|}


System Real-Time Messages

{| class=&quot;wikitable sortable&quot; width=&quot;90%&quot;
! width=&quot;10%&quot;  |Status D7----D0 
! width=&quot;10%&quot;  |Data Byte(s) D7----D0 
! width=&quot;20%&quot;  |Description
|-
|&lt;!--Status--&gt;11111000 || &lt;!--Data--&gt; || &lt;!--Description--&gt;Timing Clock. Sent 24 times per quarter note when synchronization is required.
|-
|&lt;!--Status--&gt;11111001 || &lt;!--Data--&gt; || &lt;!--Description--&gt;Undefined. (Reserved)
|-
|&lt;!--Status--&gt;11111010 || &lt;!--Data--&gt; || &lt;!--Description--&gt;Start. Start the current sequence playing. (This message will be followed with Timing Clocks).
|-
|&lt;!--Status--&gt;11111011 || &lt;!--Data--&gt; || &lt;!--Description--&gt;Continue. Continue at the point the sequence was Stopped.
|-
|&lt;!--Status--&gt;11111100 || &lt;!--Data--&gt; || &lt;!--Description--&gt;Stop. Stop the current sequence.
|-
|&lt;!--Status--&gt;11111101 || &lt;!--Data--&gt; || &lt;!--Description--&gt;Undefined. (Reserved)
|-
|&lt;!--Status--&gt;11111110 || &lt;!--Data--&gt; || &lt;!--Description--&gt;Active Sensing. This message is intended to be sent repeatedly to tell the receiver that a connection is alive. Use of this message is optional. When initially received, the receiver will expect to receive another Active Sensing message each 300ms (max), and if it does not then it will assume that the connection has been terminated. At termination, the receiver will turn off all voices and return to normal (non- active sensing) operation. 
|-
|&lt;!--Status--&gt;11111111 || &lt;!--Data--&gt; || &lt;!--Description--&gt;Reset. Reset all receivers in the system to power-up status. This should be used sparingly, preferably under manual control. In particular, it should not be sent on power-up.
|}


Advanced Messages

Polyphonic Pressure (0xA0) and Channel Pressure (0xD0)

Some MIDI controllers include a feature known as Aftertouch. While a key is being held down, the player can press harder on the key. The controller measures this, and converts it into MIDI messages.

Aftertouch comes in two flavors, with two different status messages.

The first flavor is polyphonic aftertouch, where every key on the controller is capable of sending its own independent pressure information. The messages are of the following format:
&lt;pre&gt;
0xnc, 0xkk, 0xpp
n is the status (0xA)
c is the channel nybble
kk is the key number (0 to 127)
pp is the pressure value (0 to 127)
&lt;/pre&gt;
Polyphonic aftertouch is an uncommon feature, usually found on premium quality instruments, because every key requires a separate pressure sensor, plus the circuitry to read them all.

Much more commonly found is channel aftertouch. Instead of needing a discrete sensor per key, it uses a single, larger sensor to measure pressure on all of the keys as a group. The messages omit the key number, leaving a two-byte format
&lt;pre&gt;
0xnc, 0xpp
n is the status (0xD)
c is the channel number
pp is the pressure value (0 to 127)
&lt;/pre&gt;

Pitch Bend (0xE0)

Many keyboards have a wheel or lever towards the left of the keys for pitch bend control. This control is usually spring-loaded, so it snaps back to the center of its range when released. This allows for both upward and downward bends.

Pitch Bend Wheel

The wheel sends pitch bend messages, of the format
&lt;pre&gt;
0xnc, 0xLL, 0xMM
n is the status (0xE)
c is the channel number
LL is the 7 least-significant bits of the value
MM is the 7 most-significant bits of the value
&lt;/pre&gt;
You’ll notice that the bender data is actually 14 bits long, transmitted as two 7-bit data bytes. This means that the recipient needs to reassemble those bytes using binary manipulation. 14 bits results in an overall range of 214, or 0 to 16,383. Because it defaults to the center of the range, the default value for the bender is halfway through that range, at 8192 (0x2000).

Control Change (0xB0)

In addition to pitch bend, MIDI has provisions for a wider range of expressive controls, sometimes known as continuous controllers, often abbreviated CC. These are transmitted by the remaining knobs and sliders on the keyboard controller shown below.


Continuous Controllers

These controls send the following message format:
&lt;pre&gt;
0xnc, 0xcc, 0xvv
n is the status (0xB)
c is the MIDI channel
cc is the controller number (0-127)
vv is the controller value (0-127)
&lt;/pre&gt;

Typically, the wheel next to the bender sends controller number one, assigned to modulation (or vibrato) depth. It is implemented by most instruments.

The remaining controller number assignments are another point of confusion. The MIDI specification was revised in version 2.0 to assign uses for many of the controllers. However, this implementation is not universal, and there are ranges of unassigned controllers.

On many modern MIDI devices, the controllers are assignable. On the controller keyboard shown in the photos, the various controls can be configured to transmit different controller numbers. Controller numbers can be mapped to particular parameters. Virtual synthesizers frequently allow the user to assign CCs to the on-screen controls. This is very flexible, but it might require configuration on both ends of the link and completely bypasses the assignments in the standard.


Program Change (0xC0)

Most synthesizers have patch storage memory, and can be told to change patches using the following command:
&lt;pre&gt;
0xnc, 0xpp
n is the status (0xc)
c is the channel
pp is the patch number (0-127)
&lt;/pre&gt;
This allows for 128 sounds to be selected, but modern instruments contain many more than 128 patches. Controller #0 is used as an additional layer of addressing, interpreted as a “bank select” command. Selecting a sound on such an instrument might involve two messages: a bank select controller message, then a program change.

Audio &amp; Midi are not synchronized, what I can do ?
Buy a commercial software package but there is a nasty trick to synchronize both. It's a bit hardcore but works for me:

 Simply put one line down to all midi notes on your pattern (use Insert key)
 and go to 'Misc. Setup', adjust the latency and just search a value
 that will make sound sync both audio/midi.

The stock Sin/Saw/Pulse and Rnd waveforms are too simple/common, is there a way to use something more complex/rich ?
You have to ability to redirect the waveforms of the instruments through the synth pipe by selecting the &quot;wav&quot; option for the oscillator you're using for this synth instrument, samples can be used as wavetables to replace the stock signals.


Sound banks like soundfont (sf2) or Kontakt2 are not supported at the moment


====DAW Audio Evolution 4====

Audio Evolution 4 gives you unsurpassed power for digital audio recording and editing on the Amiga. The latest release focusses on time-saving non-linear and non-destructive editing, as seen on other platforms. Besides editing, Audio Evolution 4 offers a wide range of realtime effects, including compression, noise gate, delays, reverb, chorus and 3-band EQ.

Whether you put them as inserts on a channel or use them as auxillaries, the effect parameters are realtime adjustable and can be fully automated. Together with all other mixing parameters, they can even be controlled remotely, using more ergonomic MIDI hardware.

Non-linear editing on the time line, including cut, copy, paste, move, split, trim and crossfade actions

The number of tracks per project(s) is unlimited .... AHI limits you to recording only two at a time. i.e. not on 8 track sound cards like the Juli@ or Phase 88.

sample file import is limited to 16bit AIFF (not AIFC, important distinction as some files from other sources can be AIFC with aiff file extention). and 16bit WAV (pcm only)


Most apps use the Music Unit only but a few apps also use Unit (0-3) instead or as well. 
* Set up AHI prefs so that microphone is available. (Input option near the bottom)


stereo++ allows the audio piece to be placed anywhere and the left-right adjusted to sound positionally right

hifi best for music playback if driver supports this option


Load 16bit .aif .aiff only sample(s) to use not AIFC which can have the same ending. AIFF stands for Audio Interchange File Format 

 sox recital.wav recital.aiff

 sox recital.wav −b 16 recital.aiff channels 1 rate 16k fade 3 norm
 sox input.wav        output.aiff bass −b 16 rate 48k

performs the same format translation, but also applies four effects (down-mix to one channel, sample rate change, fade-in, nomalize), and stores the result at a bit-depth of 16.

 rec −c 2 radio.aiff trim 0 30:00

records half an hour of stereo audio 

 play existing-file.wav


24bit PCM WAV or AIFF do not work 

*No stream format handling. So no way to pass on an AC3 encoded stream unmodified to the digital outputs through AHI.
*No master volume handling. Each application has to set its own volume. So each driver implements its own custom driver-mixer interface for handling master volumes, mute and preamps.
*Only one output stream. So all input gets mixed into one output.
*No automatic handling of output direction based on connected cables.
*No monitor input selection. Only monitor volume control. 


select the correct input (Don't mistake enabled sound for the correct input.)
The monitor will feedback audio to the lineout and hp out no matter if you have selected the correct input to the ADC. The monitor will provide sound for any valid input. This will result in free mixing when recording from the monitor input instead of mic/line because the monitor itself will provide the hardware mixing for you. Be aware that MIC inputs will give two channel mono. Only Linein will give real stereo.

Now for the not working part. Attempt to record from linein in the AE4 record window, the right channel is noise and the left channel is distorted. Even with the recommended HIFI 16bit Stereo++ mode at 48kHz.


Channels

Monitor

Gain

Inout

Output

Advanced settings - Debugging via serial port


* Options -&gt; Soundcard In/Out
* Options -&gt; SampleRate
* Options -&gt; Preferences

F6 for Sample File List

Setting a grid is easy as is measuring the BPM by marking a section of the sample. Is your kick drum track &quot;not in time&quot; ? If so, you're stumped in AE4 as it has no fancy variable time signatures and definitely no 'track this dodgy rhythm' function like software of the nature of Logic has. So if your drum beat is freeform you will need to work in freeform mode. (Real music is free form anyway).

If the drum *is* accurate and you are just having trouble measuring the time, I usually measure over a range of bars and set the number of beats in range to say 16 as this is more accurate, Then you will need to shift the drum track to match your grid *before* applying the grid. (probably an iterative process as when the grid is active samples snap to it, and when inactive you cannot see it).

AE4 does have ARexx but the functions are more for adding samples at set offsets and starting playback / recording.


These are the usual features found in DAWs...

* Recording digital audio, midi sequencer and mixer 
* virtual VST instruments and plug-ins 
* automation, group channels, MIDI channels, FX sends and returns, audio and MIDI editors and music notation editor


* different track views 
* mixer and track layout (but not the same as below) 
* traditional two windows (track and mixer)


Mixing - mixdown

Could not figure out how to select what part I wanted to send to the aux, set it to echo and return. Pretty much the whole echo effect. Or any effect.

Take look at page17 of the manual.

When you open the EQ / Aux send popup window you will see 4 sends. Now from the menu choose the windows menu.

Menus-&gt;Windows-&gt; Aux Returns Window

or press F5

You will see a small window with 4 volume controls and an effects button for each. Click a button and add an effects to that aux channel, then set it up as desired (note the reverb effect has a special AUX setting that improves its use with the aux channel, not compulsory but highly useful). You set the amount of 'return' on the main mix in the Aux Return window, and the amount sent from each main mixer channel in the popup for that channel. Again the aux sends are &quot;prefade&quot; so the volume faders on each channel do not affect them.


Tracking


Effects - fade in

To add some echoes to some vocals, tried to add an effect on a track but did not come out. This is made more complicated as I wanted to mute a vocal but then make it echo at the muting point. Want to have one word of a vocal heard and then echoed off. But when the track is mute the echo is cancelled out.

To correctly understand what is happening here you need to study the figure at the bottom of page 15 on the manual. You will see from that that the effects are applied 'prefade' So the automation you applied will naturally mute the entire signal.

There would be a number of ways to achieve the goal,

You have three real time effects slots, one for smoothing like so

Sample -&gt; Amplify -&gt; Delay

Then automate the gain of the amplify block so that it effectively mutes the sample just before the delay at the appropriate moment, the echo effect should then be heard.

Getting the effects in the right order will require experimentation as they can only be added top down and it's not obvious which order they are applied to the signal, but there only two possibilities, so it wont take long to find out.

Using MUTE can cause clicks to the Amplify can be used to mute more smoothly so that's a secondary advantage.

Signal Processing -


Overdub

[[#top|...to the top]]

===Office===

====Spreadsheet Leu====

Support for some xlsx, and ods functions 


====Spreadsheet Ignition====

; Needs ABIv1 to be completed before more can be done

File formats supported 
* ascii #?.txt and #?.csv (single sheets with data only). 
* igs and TurboCalc(WIP) #?.tc for all sheets with data, formats and formulas.

There is '''no''' support for xls, xlsx, ods or uos ([http://en.wikipedia.org/wiki/Uniform_Office_Format Uniform Unified Office Format]) at the moment.

* Always use Esc key after editing Spreadsheet cells.
* copy/paste seems to copy the first instance only so go to Edit -&gt; Clipboard to manage the list of remembered actions. 
* Right mouse click on row (1 or 2 or 3) or column header (a or b or c)  to access optimal height or width of the row or column respectively 
* Edit -&gt; Insert -&gt; Row  seems to clear the spreadsheet or clears the rows after the inserted row until undo restores as it should be...

Change Sheet name by  Object -&gt; Sheet -&gt; Properties

Click in the cell which will contain the result, and click '''down arrow button''' to the right of the formula box at the bottom of the spreadsheet and choose the function required from the list provided. Then click on the start cell and click on the bottom right corner, a '''very''' small blob, which allows stretching a bounding box (thick grey outlines) across many cells This grey bounding box can be used to '''copy a formula''' to other cells.

Object -&gt; Cell -&gt; Properties to change cell format - Currency only covers DM and not $, Euro, Renminbi, Yen or Pound etc. 
Shift key and arrow keys selects a range of cells, so that '''formatting can be done to all highlighted cells'''. 
View -&gt; Overview then select ALL with one click (in empty cell in the top left hand corner of the sheet).

Default mode is relative cell referencing e.g. a1+a2 but absolute e.g. $a$1+$a$2 can be entered.

* #sheet-name to '''absolute''' reference another sheet-name cell unless reference() function used.

;Graphs

use shift key and arrow keys to select a bunch of cells to be graph'ed making sure that x axes represents and y axes represents

* value() - 0 value, 1 percent, 2 date, 3 time, 4 unit ...


;Dates 
* Excel starts a running count from the 1st Jan 1900 and Ignition starts from 1st Jan 1AD '''(maybe this needs to change)'''
Set formatting Object -&gt; Cell -&gt; Properties and put date in days


;Time 
Set formatting Object -&gt; Cell -&gt; Properties and put time in seconds taken


;Database (to be done by someone else)

type - standard, reference (bezug), search criterion (suchkriterium), 
* select a bunch of cells and Object -&gt; Database -&gt; Define to set Datenbank (database) and Felder (fields not sure how?) 
* Neu (new) or loschen (delete) to add/remove database headings e.g. Personal, Start Date, Finish Date (one per row?)
* Object -&gt; Database -&gt; Index to add fields (felder) like Surname, First Name, Employee ID, etc. to ?

Filtering done with dbfilter(), dbproduct() and dbposition().

Activities with dbsum(), dbaverage(), dbmin() and dbmax().

Table sorting -


;Scripts (Arexx)

;Excel(TM) to Ignition - commas ''',''' replaced by semi-colons ''';''' to separate values within functions 
*SUM(), 
*AVERAGE(), MAX(), MIN(), INT(), PRODUCT(), MEDIAN(), VAR() becomes Variance(), Percentile(),
*IF(), AND, OR, NOT 
*LEFT(), RIGHT(), MID() becomes MIDDLE(), LEN() becomes LENGTH(), 
*LOWER() becomes LOWERCASE(), UPPER() becomes UPPERCASE(),
* DATE(yyyy,mm,dd) becomes COMPUTEDATE(dd;mm;yyyy), 
*TODAY(), DAY(),WEEK(), MONTH(),=YEAR(TODAY()), 
*EOMONTH() becomes MONTHLENGTH(), 
*NOW() should be date and time becomes time only, SECOND(), MINUTE(), HOUR(),
*DBSUM() becomes DSUM(),


;Missing and possibly useful features/functions needed for ignition to have better support of Excel files 
There is no Merge and Join Text over many cells, no protect and/or freeze row or columns or books but can LOCK sheets, no define bunch of cells as a name, Macros (Arexx?), conditional formatting, no Solver, no Goal Seek, no Format Painter, no AutoFill, no AutoSum function button, no pivot tables, (30 argument limit applies to Excel)

*HLOOKUP(), VLOOKUP(), [http://production-scheduling.com/excel-index-function-most-useful/ INDEX(), MATCH()], CHOOSE(), TEXT(), 
*TRIM(), FIND(), SUBSTITUTE(), CONCATENATE() or &amp;, PROPER(), REPT(), 
*[https://acingexcel.com/excel-sumproduct-function/ SUMPRODUCT()], ROUND(), ROUNDUP(), *ROUNDDOWN(), COUNT(), COUNTA(), SUMIF(), COUNTIF(), COUNTBLANK(), TRUNC(), 
*PMT(), PV(), FV(), POWER(), SQRT(), MODE(), TRUE, FALSE, 
*MODE(), LARGE(), SMALL(), RANK(), STDEV(), 
*DCOUNT(), DCOUNTA(), WEEKDAY(),


;Excel Keyboard [http://dmcritchie.mvps.org/excel/shortx2k.htm shortcuts needed to aid usability in Ignition] 
&lt;pre&gt;
Ctrl Z - Undo

Ctrl D - Fill Down
Ctrl R - Fill right

Ctrl F - Find
Ctrl H - Replace

Ctrl 1 - Formatting of Cells
CTRL SHIFT ~ Apply General Formatting ie a number 
Ctrl ; - Todays Date 

F2 - Edit cell
F4 - toggle cell absolute / relative cell references

&lt;/pre&gt;


====Document Scanning - Scandal====

Scanner usually needs to be connected via a USB port and not via a hub or extension lead.

Check in Trident Prefs -&gt; Devices that the USB Scanner is not bound to anything (e.g. Bindings None)
If not found then reboot the computer and recheck.

Start Scandal, choose Settings from Menu strip at top of screen and in Scanner Driver choose the ?#.device of the scanner (e.g. epson2.device).

The next two boxes - leave empty as they are for morphos SCSI use only
 or put ata.device (use the selection option in bigger box below) and Unit as 0 this is needed for gt68xx

* gt68xx - no editing needed in s/gt68xx.conf but needs a firmware file that corresponds to the scanner [http://www.meier-geinitz.de/sane/gt68xx-backend/ gt68xx firmwares] in sys:s/gt68xx.
* epson2 - Need to edit the file epson2.conf in sys/s that corresponds to the scanner being used

'''Save''' the settings but do not press the Use button (aros freezes)

Back to the Picture Scan window and the right-hand sections.

Click on the '''Information''' tab and press Connect button and the scanner should now be detected.

Go next to the '''Scanner''' tab next to Information Tab should have Color, Black and White, etc. and dpi settings now. Selecting an option Color, B/W etc. can cause dpi settings corruption (especially if the settings are in one line) so set '''dpi first'''. Make sure if Preview is set or not.

In the '''Scan''' Tab, press Scan and the scanner will do its duty. 
Be aware that nothing is saved to disk yet.

In the Save tab, change format JPEG, PNG or IFF DEEP. Tick incremental and base filename if necessary and then click the Save button. The image will now be saved to permanent storage.


The driver ignores a device if it is already bond to another USB class, rejects it from being usable. However, open Trident prefs, select your device and use the right mouse button to open. Select &quot;NONE&quot; to prevent poseidon from touching the device. Now save settings. It should always work now.

[[#top|...to the top]]

===Emulators===

==== Amiberry ====


==== Amiga Emu - Janus UAE ====

With Amibridge, AROS attempts to make the UAE emulator seem embedded within but it still is acting as an app 

There is no dynarec m68k for each hardware that Aros supports or direct patching of motorola calls to AROS hardware accelerated ones unless the emulator has that included 

Try starting Janus with a priority of -1 like this little script:
&lt;pre&gt;
cd sys:system/AmiBridge/emulator
changetaskpri -1
run janus-uae -f my_uaerc.config &gt;nil:
cd sys:prefs
endcli
&lt;/pre&gt;
This stops Janus hogging all the CPU time.


===Miscellaneous===

====Screensaver Blanker====

Most blankers on the amiga (i.e. aros) run as commodities (they are in the tools/commodities drawer). Double click on blanker.

Control is with an app called Exchange, which you need to run first (double click on app) or  run QUIET sys:tools/commodities/Exchange &gt;NIL: but subsequently can use (Cntrl Alt h).

Icon tool types (may be broken) or command line options 
&lt;pre&gt;
seconds=number 
&lt;/pre&gt;

Once the timing is right then add the following to s:icaros-sequence or s:user-startup

e.g. for 5 minutes

 run QUIET sys:tools/commodities/Blanker seconds=300 &gt;NIL:


*[http://archives.aros-exec.org/index.php?function=showfile&amp;file=graphics/screenblanker/gblanker.i386-aros.zip Garshneblanker] can make Aros unstable or slow. Certain blankers crashes in Icaros 2.0.x like Dragon, Executor.


*[ Acuario AROS version], the aquarium screen saver.

Startup: extras:acuariofv-aros/acuario

Kill: c:break name=extras:acuariofv-aros/acuario

Managed to start Acuario by the Executor blanker.

&lt;pre&gt;
cx_priority=
cx_popkey=    ie CX_POPKEY=&quot;Shift F1&quot; 
cx_popup=Yes or No

&lt;/pre&gt;


&lt;pre&gt;
 Qualifier String    Input Event Class
   ----------------    -----------------
    &quot;lshift&quot;           IEQUALIFIER_LSHIFT
    &quot;rshift&quot;           IEQUALIFIER_RSHIFT
    &quot;capslock&quot;         IEQUALIFIER_CAPSLOCK
    &quot;control&quot;          IEQUALIFIER_CONTROL
    &quot;lalt&quot;             IEQUALIFIER_LALT
    &quot;ralt&quot;             IEQUALIFIER_RALT
    &quot;lcommand&quot;         IEQUALIFIER_LCOMMAND
    &quot;rcommand&quot;         IEQUALIFIER_RCOMMAND
    &quot;numericpad&quot;       IEQUALIFIER_NUMERICPAD
    &quot;repeat&quot;           IEQUALIFIER_REPEAT
    &quot;midbutton&quot;        IEQUALIFIER_MIDBUTTON
    &quot;rbutton&quot;          IEQUALIFIER_RBUTTON
    &quot;leftbutton&quot;       IEQUALIFIER_LEFTBUTTON
    &quot;relativemouse&quot;    IEQUALIFIER_RELATIVEMOUSE
&lt;/pre&gt;


&lt;pre&gt;
    Synonym     Synonym
    String     Identifier
    -------    ----------
    &quot;shift&quot;    IXSYM_SHIFT    /* look for either shift key */
    &quot;caps&quot;     IXSYM_CAPS     /* look for either shift key or capslock */
    &quot;alt&quot;      IXSYM_ALT      /* look for either alt key */

Highmap is one of the following strings:
    &quot;space&quot;, &quot;backspace&quot;, &quot;tab&quot;, &quot;enter&quot;, &quot;return&quot;, &quot;esc&quot;, &quot;del&quot;,
    &quot;up&quot;, &quot;down&quot;, &quot;right&quot;, &quot;left&quot;, &quot;f1&quot;, &quot;f2&quot;, &quot;f3&quot;, &quot;f4&quot;, &quot;f5&quot;,
    &quot;f6&quot;, &quot;f7&quot;, &quot;f8&quot;, &quot;f9&quot;, &quot;f10&quot;, &quot;help&quot;.


&lt;/pre&gt;


[[#top|...to the top]]

==== World Construction Set WCS (Version 2.031) ====

WCS is a fractal landscape software such as Scenery Animator, Vista Pro and Panorama. Open sourced February 2022, World Construction Set [https://3dnature.com/downloads/legacy-software/ legally and for free] and [https://github.com/AlphaPixel/3DNature c source]. 

Announced August 1994 this version dates from April 1996 developed by Gary R. Huber and Chris &quot;Xenon&quot; Hanson&quot; from Questar 

&lt;pre&gt;
Assign &quot;WCSProjects:&quot; &quot;Volume:Dir/Dir/WCSProjects&quot; 
Assign &quot;WCSFrames:&quot;   &quot;Volume:Dir/Dir/WCSFrames&quot; 
&lt;/pre&gt;

&lt;pre&gt;
Load projects .proj by accessing pull down menu Project -&gt; Open then click on CanyonSunset.proj
OK to changing .par file and enlarge Status Log window to show what is happening 
Render by pull down menu Modules -&gt; Render with End equal 1 not 300 then click bottom middle button Render 
&lt;/pre&gt;

[https://www.youtube.com/watch?v=CxQDmf1ZWG0 Youtube walkthrough of above], [], [], 

Also try working with the already built file ColoDemo - Then open with the drop-down menu: Project/Open, then WCSProject:ColoDemo.proj
Which allows you to use altimetric DEM files already included and Loading scene parameters from ColoDemo.par
Once this is done, save everything with a new name to start working exclusively on your project. 
Then drop-down menu and select Save As (&quot;NewName&quot;.proj name), then drop-down menu to open parameter and select Save All ( .par name)


After launching the software, there is a the Module Control Panel composed of five icons. 
It is a dock type shortcut of the first few functions of the drop-down menu 

*Database   - Load (#?.proj), Append, Create, Edit, Save, Dir List (of WCSProject drawer), 
*Data Ops   - Extract / Convert Interp DEM, Import DLG, DXF, WDB and export LW map 3d formats  
*Map View   - Database file Loader leading to Map View Control with option to the Database Editor 
*Parameters - Editor for Motion, Color, Ecosystem, Clouds, Waves, management of altimeter files DEM, sclock settings etc 
*Render     - rendering terrain 

These are more in the pull down menu but not in the dock 
*Motion Editor
*Color Editor
*Ecosys Editor 


Simple minimal workflow 
*Load database (1st icon - 1st)
*Set parameters and save .par file (4th icon)
*Render scene (5th icon) 

[https://www.youtube.com/watch?v=ZbTwwR2qcc4 Youtube], [], 

&lt;pre&gt;
.proj new project name which creates a drawer of additional files 

.binary array, ascii array .xyz , z buffer, DTED .dt0, vista 1990s dem, iff  conversion 
.Obj with .elev, .frd with .hdr maps, - digital elevation model (DEM) is a 3D representation of elevation data in various formats 
USGS 7.5MinDEM, 

.par 


&lt;/pre&gt;


Since for the time being no project is loaded, a query window indicates a procedural error when clicking on the rendering icon (right end of the bar). The menu is quite traditional; it varies according to the activity of the windows. To display any altimetric file in the &quot;Mapview&quot; (third icon of the panel), There are three possibilities:

* Loading of a demonstration project.
* The import of a DEM file, followed by texturing and packaging from the &quot;Database-Editor&quot; and the &quot;Color-Editor&quot;.
* The creation of an altimetric file in WCS format, then texturing.


The altimeter file editing (display in the menu) is only made possible if the &quot;Mapview&quot; window is active.

The software is made up of many windows and won't be able to describe them all. Know that &quot;Color-Editor&quot; and the &quot;Data-Editor&quot; comprise sufficient functions for obtaining an almost real rendering quality. You have the possibility of inserting vector objects in the &quot;Data-Editor&quot; (creation of roads, railways, etc.) 


The Map View (MapView) window

*Database - Objects and Topos
*View     - Align, Center, Zoom, Pan, Move 
*Draw     - Maps and distance 
*Object   - Find, highlight, add points, conform topo, duplicate 
*Motion   - Camera, Focus, path, elevation 
*Windows  - DEM designer, Cloud (.cld) and wave (.wve) editor, 


You will notice that by selecting this window and simply moving the pointer to various points on the map you will see latitude and longitude values ​​change, along with the height.
Drop-down menu and Modules, then select MapView and change the width of the window with the map to arrange it in the best way on the screen. With the Auto button the center. Window that then displays the contents of my DEM file, in this case the Grand Canyon. MapView allows you to observe the shape of the landscape from above
 

ZOOM button

Press the Zoom button and then with the pointer position on a point on the map, press the left mouse button and then move to the opposite corner to circumscribe the chosen area and press the left mouse button again, then we will see the enlarged area selected on the map.
Would add that there is a box next to the Zoom button that allows the direct insertion of a value which, the larger it is, the smaller the magnification and the smaller the value, the stronger the magnification. At each numerical change you will need to press the DRAW button to update the view.

PAN button

Under Zoom you will find the PAN button which allows you to move the map at will in all directions by the amount you want. This is done by drawing a line in one direction, then press PAN and point to an area on the map with the pointer and press the left mouse button. At this point, leave it and move the pointer in one direction by drawing a line and press the left mouse button again to trigger the movement of the map on the screen (origin and end points). Do some experiments and then use the Auto button immediately below to recenter everything.
There are parameters such as TOPO, VEC to be left checked and immediately below one that allows different views of the map with the Style command (Single, Multi, Surface, Emboss, Slope, Contour), each with its own particularities to highlight different details.

Now you have the first basics to manage your project visually on the map. Close the MapView window and go further...


Let's start working on ECOSYSTEMS
If we select Emboss from the MapView Style command we will have a clear idea of ​​how the landscape appears, realizing that it is a predominantly desert region of our planet. Therefore we will begin to act on any vegetation present and the appearance of the landscape.
With WCS we will begin to break down the elements of the landscape by assigning defined characteristics. It will be necessary to determine the classes of the ecosystem (Class) with parameters of Elevation Line (maximum altitude), Relative Elevation (arrangement on basins or convexities with respectively positive or negative parameters), Min Slope and Max Slope (slope). WCS offers the possibility of making ecosystems coexist on the same terrain with the UnderEco function, by setting a Density value.


Ecosys Ecosystem Editor

Let's open it from Modules, then Ecosys Editor. In the left pane you will find the list of ecosystems referring to the files present in our project. It will be necessary to clean up that box to leave only the Water and Snow landscapes and a few other predefined ones. We can do this by selecting the items and pressing the Remove button (be careful not for all elements the button is activated, therefore they cannot all be eliminated).
Once this is done we can start adding new ecosystems. Scroll through the various Unused and as soon as the Name item at the top is activated allowing you to write, type the name of your ecosystem, adding the necessary parameters.
&lt;pre&gt;
Ecosystem1: Name: RockBase Class: Rock Density: 80 MinSlope: 15 UnderEco: Terrain
Ecosystem2: Name: RockIncl Clss: Rock Density: 80 MinSlope: 30 UnderEco: Terrain
Ecosystem3: Name: Grass Class Low Veg Density: 50 Height: 1 Elev Line : 1500 Rel El Eff: 5
Max Slope: 10 – Min Slope: 0 UnderEco: Terrain
Ecosistema4: Name: Shrubs Class: Low Veg Density: 40 Height: 8 Elev Line: 3000
Rel El Eff: -2 Max Slope: 20 Min Slope : 5 UnderEco: Terrain
Ecosistema5: Name: Terrain Class: Ground Density: 100 UnderEco: Terrain
&lt;/pre&gt;

Now we need to identify an intermediate ecosystem that guarantees a smooth transition between all, therefore we select as Understory Ecosystem the one called Terrain in all ecosystems, except Snow and Water .
Now we need to 'emerge' the Colorado River in the Canyon and we can do this by raising the sea level to 900 (Sea Level) in the Ecosystem called Water.
Please note that the order of the ecosystem list gives priority to those that come after. So our list must have the following order: Water, Snow, Shrubs, RockIncl, RockBase, Terrain. It is possible to carry out all movements with the Swap button at the bottom. To put order you can also press Short List. Press Keep to confirm all the work done so far with Ecosystem Editor.
Remember every now and then to save both the Project 'Modules/Save' and 'Parameter/Save All'

EcoModels are made up of .etp .fgp .iff8 for each model 


Color Editor

Now it's time to define the colors of our scene and we can do this by going to Modules and then Color Editor. In the list we focus on our ecosystems, created first.
Let's go to the bottom of the list and select the first white space, assigning the name 'empty1', with a color we like and then we will find this element again in other environments... It could serve as an example for other situations!
So we move to 'grass' which already exists and assign the following colors: R 60 G 70 B50
&lt;pre&gt;
'shrubs': R 60 G 80 B 30
'RockIncl' R 110 G 65 B 60
'RockBase' R 110 G 80 B 80
' Terrain' R 150 G 30 B 30
&lt;pre&gt;
Now we can work on pre-existing colors
&lt;pre&gt;
'SunLight' R 150 G 130 B 130
'Haze and Fog' R 190 G 170 B 170
'Horizon' R 209 G 185 B 190
'Zenith' R 140 G 150 B 200
'Water' R 90 G 125 B 170
&lt;/pre&gt;

Ambient R 0 G 0 B 0

So don't forget to close Color Editor by pressing Keep.
Go once again to Ecosystem Editor and assign the corresponding color to each environment by selecting it using the Ecosystem Color button. Press it several times until the correct one appears. Then save the project and parameters again, as done previously.


Motion Editor

Now it's time to take care of the framing, so let's go to Modules and then to Motion Editor. An extremely feature-rich window will open. Following is the list of parameters regarding the Camera, position and other characteristics:
&lt;pre&gt;
-Camera Altitude: 7.0
-Camera Latitude: 36.075
-Camera Longitude: 112.133
-Focus Attitude: -2.0
-Focus Latitude: 36.275
-Focus Longitude: 112.386
-Camera : 512 → rendering window
-Camera Y: 384 → rendering window
-View Arc: 80 → View width in degrees
-Sun Longitude: 172
-Sun Latitude: -0.9
-Haze Start: 3.8
-Haze Range: 78, 5
&lt;/pre&gt;
As soon as the values ​​shown in the relevant sliders have been modified, we will be ready to open the CamView window to observe the wireframe preview. Let's not consider all the controls that will appear.
Well from the Motion Editor if you have selected Camera Altitude and open the CamView panel, you can change the height of the camera by holding down the right mouse button and moving the mouse up and down. To update the view, press the Terrain button in the adjacent window. As soon as you are convinced of the position, confirm again with Keep. You can carry out the same work with the other functions of the camera, such as Focus Altitude...
Let's now see the next positioning step on the Camera map, but let's leave the CamView preview window open while we go to Modules to open the window at the same time MapView. We will thus be able to take advantage of the view from the other together with a subjective one.


From the MapView window, select with the left mouse button and while it is pressed, move the Camera as desired. To update the subjective preview, always click on Terrain.
While with the same procedure you can intervene on the direction of the camera lens, by selecting the cross and with the left button pressed you can choose the desired view. So with the pressure of Terrain I update the Preview. Possibly can enlarge or reduce the Map View using the Zoom button, for greater precision.
Also write that the circle around the cameras indicates the beginning of the haze, there are two types (haze and fog) linked to the altitude. Would also add that the camera height is editable through the Motion Editor panel.


The sun

Let's see that changing the position of the sun from the Motion Editor. Press the SUN button at the bottom right and set the time and the date. Longitude and latitude are automatically obtained by the program. Always open the View Arc command from the Motion Editor panel, an item present in the Parameter List box.

Once again confirm everything with Keep and then save again.


Animation

The animation part is not left-back and also occupies a window. The settings possibilities are enormous. A time line with dragging functions (&quot;slide&quot;, &quot;drag&quot;...) comparable to that of LightWave completes this window. 


A small window is available for positioning the stars as a function of a date, in order to vary the seasons and their various events (and yes...).

At the bottom of the &quot;Motion-Editor&quot;, a &quot;cam-view&quot; function will give you access to a control panel. Different preview modes are possible. The rendering is also accessible through a window. No less than nine pages compose it. At this level, you will be able to determine the backup name of your images (&quot;path&quot;), the type of texture to be calculated, the resolution of the images, activate or deactivate functions such as the depth buffer (&quot;zbuffer&quot;), the blur, the background image, etc.


Once all these parameters have been set, all you have to do is click on the &quot;Render&quot; button.

For rendering go to Modules and then Render. Select the resolution, then under IMA select the name of the image. Move to FRA and indicate the level of fractal detail which of 4 is quite good. Then Keep to confirm and then reopen the window, pressing Render you will see the result. The image will be opened with any viewing program.


Strengths:

* Multi-window.
* Quality of rendering.
* Accuracy.
* Opening, preview and rendering on CyberGraphX screen.
* Extract / Convert Interp DEM, Import DLG, DXF, WDB and export LW map 3d formats 
* The &quot;zbuffer&quot; function.

Weaknesses:

* No OpenGL management 
* Calculation time.
* No network computing tool.


====Writing CD / DVD - Frying Pan====

Can be backup DVDs (4GB ISO size limit due to use of FileInfoBlock), create audio cds from mp3's, and put .iso files on discs

If using for the first time - click Drive button and Device set to ata.device and unit to 0 (zero)

Click Tracks Button - Drive 1 - Create New Disc or Import Existing Disc Image (iso bin/cue etc.) - Session File open cue file

If you're making a data cd, with files and drawers from your hard drive, you should be using the ISO Builder.. which is the MUI page on the left. (&quot;Data/Audio Tracks&quot; is on the right).

You should use the &quot;Data/Audio tracks&quot; page if you want to create music cds with AIFF/WAV/MP3 files, or if you download an .iso file, and you want to put it on a cd.

Click WRITE Button - set write speed - click on long Write button

Examples

Easiest way would be to burn a DATA CD, simply go to &quot;Tracks&quot; page &quot;ISO Builder&quot; and &quot;ADD&quot; everything you need to burn.

On the &quot;Write&quot; page i have &quot;Masterize Disc (DAO)&quot;, &quot;Close Disc&quot; and &quot;Eject after Write&quot; set.

One must not &quot;Blank disc before write&quot; if one uses a CDR


AUDIO CD from MP3's are as easy but tricky to deal with. FP only understands one MP3 format, Layer II, everything else will just create empty tracks

Burning bootable CD's works only with .iso files. Go to &quot;Tracks&quot; page and &quot;Data/Audio Tracks&quot; and add the .iso


====odf====

Every ODF file is a collection of several subdocuments within a package (ZIP file), each of which stores part of the complete document.

* content.xml – Document content and automatic styles used in the content.
* styles.xml – Styles used in the document content and automatic styles used in the styles themselves.
* meta.xml – Document meta information, such as the author or the time of the last save action.
* settings.xml – Application-specific settings, such as the window size or printer information.


To read document follow these steps:

* Extracting .ods file.
* Getting content.xml file (which contains sheets data).
* Creating XmlDocument object from content.xml file.
* Creating DataSet (that represent Spreadsheet file).
* With XmlDocument select “table:table” elements, and then create adequate DataTables.
* Parse child’s of “table:table” element and fill DataTables with those data.
* At the end, return DataSet and show it in application’s interface.


To write document follow these steps:

* Extracting template.ods file (.ods file that we use as template).
* Getting content.xml file.
* Creating XmlDocument object from content.xml file.
* Erasing all “table:table” elements from the content.xml file.
* Reading data from our DataSet and composing adequate “table:table” elements.
* Adding “table:table” elements to content.xml file.
* Zipping that file as new .ods file.

XLS file format

The XLS file format contains streams, substreams, and records.

These sheet substreams include worksheets, macro sheets, chart sheets, dialog sheets, and VBA module sheets. 
All the records in an XLS document start with a 2-byte unsigned integer to specify Record Type (rt), and another for Count of Bytes (cb). A record cannot exceed 8224 bytes. If larger than the rest is stored in one or more continue records.

* Workbook stream 
**Globals substream
***BoundSheet8 record - info for Worksheet substream i.e. name, location, type, and visibility. (4bytes the lbPlyPos FilePointer, specifies the position in the Workbook stream where the sheet substream starts) 
**Worksheet substream (sheet) - Cell Table - Row record - Cells (2byte=row 2byte=column 2byte=XF format)
***Blank cell record
***RK cell record 32-bit number. 
***BoolErr cell record (2-byte Bes structure that may be either a Boolean value or an error code)
***Number cell record (64-bit floating-point number)
***LabelSst cell record (4-byte integer that specifies a string in the Shared Strings Table (SST). Specifically, the integer corresponds to the array index in the RGB field of the SST)
***Formula cell record (FormulaValue structure in the 8 bytes that follow the cell structure. The next 6 bytes can be ignored, and the rest of the record is a CellParsedFormula structure that contains the formula itself)
***MulBlank record (first 2 bytes give the row, and the next 2 bytes give the column that the series of blanks starts at. Next, a variable length array of cell structures follows to store formatting information, and the last 2 bytes show what column the series of blanks ends on)
***MulRK record 
***Shared String Table (SST) contains all of the string values in the workbook.

ACCRINT(), ACCRINTM(), AMORDEGRC(), AMORLINC(), 
COUPDAYBS(), COUPDAYS(), COUPDAYSNC(), COUPNCD(), COUPNUM(), COUPPCD(), 
CUMIPMT(), CUMPRINC(), 
DB(), DDB(), DISC(), 
DOLLARDE(), DOLLARFR(), 
DURATION(), EFFECT(), FV(), FVSCHEDULE(), 
INTRATE(), IPMT(), IRR(), ISPMT(), MDURATION(), MIRR(), NOMINAL(), NPER(), NPV(), 
ODDFPRICE(), ODDFYIELD(), ODDLPRICE(), ODDLYIELD(), 
PMT(), PPMT(), PRICE(), PRICEDISC(), PRICEMAT(), PV(), RATE(), 
RECEIVED(), SLN(), SYD(), TBILLEQ(), TBILLPRICE(), TBILLYIELD(), 
VDB(), XIRR(), XNPV(), YIELD(), YIELDDISC(), YIELDMAT(),


&lt;pre&gt;
&lt;/pre&gt;


&lt;pre&gt;
&lt;/pre&gt;

&lt;pre&gt;
&lt;/pre&gt;

{{BookCat}}</text>
      <sha1>q30a61vr5r816atvez0sbn1k4nh9rfq</sha1>
    </revision>
  </page>
  <page>
    <title>History of Western Theatre: 17th Century to Now/German Pre-WWII</title>
    <ns>0</ns>
    <id>242970</id>
    <revision>
      <id>4656133</id>
      <parentid>4629233</parentid>
      <timestamp>2026-08-02T22:59:04Z</timestamp>
      <contributor>
        <username>Neojacob</username>
        <id>363908</id>
      </contributor>
      <comment>/* Ödön von Horváth */ Weisstein, 1960</comment>
      <origin>4656133</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="143343" sha1="mkfr6vkr2kyhxvihx77qooq7jpwzl8j" xml:space="preserve">[[File:The New Hebbel Theatre in Berlin - Entrance, 1908.jpg|thumb|Entrance of the New Hebbel Theatre,  Berlin, 1908]]

Pre-World War II German theatre was dominated by expressionism, especially from 1912 to 1923 (Garten, 1964). Aside from the first plays of Brecht, German expressionist drama holds no towering figure, but there are several playwrights of interest in work characterized by intense drama and black comedy. The dialogue tends to be farfetched or semi-poetical, the situations strange or dream-like, and persons struggle with deep inner turmoil that affects the environment they live in. In expressionism, the individual's mind affects the environment, in contrast to impressionism, in which the environment affects the individual's mind. Every dramatist of the 1910-1939 period shows variable degrees of this tendency. The movement derives from Strindberg, especially &quot;To Damascus&quot; (1898-1904) and &quot;A dream play&quot; (1907), &quot;Although the essential autobiographical which makes Strindberg's dramas unique, could not be imitated, the confessional character of such unreserved, personal documents had a tremendous influence on the younger German dramatists, minding us of the effect of Rousseau's writings on the German Storm and Stress movement&quot; (Burkhard, 1933 p 172). “Since consistency was not considered either a virtue or a necessity, the sequence of events was not always clear. Since the general style was usually strident or hysterical, the action abrupt or insistently repetitious, the tempo breathless, the dialogue frantic or monotonously telegraphic, expressionist plays tend to tax our nervous system” (Gassner, 1954b p 203). &quot;The bizarre morbidity, the nauseating sexuality, the lack of any trace of joy or beauty, which characterize the work of most of those who labeled themselves expressionists in Ger- many during the past few years, match Strindberg at his unhappiest, while the vigor with which they drive their ideas forth in speech far outdoes him. Expressionism, in the nar- row sense in which such plays define it, is a violent storm of emotion beating up from the unconscious mind. It is no more than the waves which shatter themselves on the shore of our conscious existence, only a distorted hint of the deep and mysterious sea of the unconscious. Expressionism, as we have so far known it, is a meeting of the fringes of the conscious and the unconscious, and the meeting is startling indeed&quot; (Macgowan and Jones, 1920 p 31). 

Strindberg's “successors in expressionistic experimentation made a veritable cult of morbid introspection and emotionally disturbed pictures of external reality...The expressionist playwright dispensed with the middle-class clutter to be found in men’s minds and showed only the springs of passion…to present depersonalized characters, individuals transformed into stark symbols of allegorical  types deprived of personal name...And the individual was likely to be placed in a truncated scene usually deprived of the padding of manners and small talk customary in cup-and-saucer living-room scenes. Only the dramatic moment was allowed to matter. This moment was given to the spectator without the familiar preparatory detail of 19th century realism...The expressionist, giving the reins to his own fancy and intensifying the character’s subjective states, felt free to history all manifestations of character and environment and to shuttle back and forth in time and space...Kaiser calls for the sudden transformation of a snow-laden tree to a skeleton in From Morn to Midnight” [when] the fantastic action and environment are dramatically related to the state of mind of an absconding cashier...Dialogue was subjected to weird abbreviations and distortions so that it became frequently violent, telegraphic, and enigmatic...especially true of German expressionism between 1912 and 1925”  (Gassner, 1956 pp 118-121). “The expressionists wanted to affect the environment anew, not in its appearances but in its essence. For the expressionists wanted to affect this environment, change it, give it a more just and luminous face” (Toller, 1929, 1985 edition p 178). 

&quot;Expressionism grew out of German neo-romanticism. With their frantic search for community, love, and vitality, however, the expressionists seem to represent a violent reaction against the estheticism, formalism, and social isolation of their predecessors&quot; (Sokel, 1955 p 1). “The common denominator of all these works is their intensified social criticism, a rejection of the present state of society, and a longing for a change even if it became a storm that would cause destruction but would clear the air. Writers revolted against the cultural and political manifestations of their age, and with youthful enthusiasm, envisioned a regeneration of mankind and the building of a new world. This revolt against the old standards and values in politics and the arts was soon given the name Expressionism and was conducted by young artists most of whom were born around 1890...They expressed their concern about the problems of the day and, in contrast to Naturalism, tried to present answers and solutions, impractical and subjective though they be. Even if their criticism did not always include a program of how to combat society’s maladies, new social and ethical ideas were implied. With their visions of a doomed and destroyed world, the Expressionists wanted to shock the bourgeois citizen into an awareness of his shortcomings and the need for a new human community. In order to express their message, the young writers resorted to new art forms, since they sought a new beginning in art. They turned against Impressionism as being too esthetic and unrelated to life- and against Naturalism because it only portrays, but does not attack, the evils of society” (Schürer, 1971 pp 81-82).

=Gerhart Hauptmann=

[[File:Scolik - Gerhart Hauptmann.jpg|thumb|Already a master from 19th century German drama, Gerhart Hauptmann continued to excel in the 20th. Photograph of the author by Charles Scolik (1854-1928)]]

Emerging from the previous century, Gerhart Hauptmann (1862-1946) continued to write dramas of the realist or naturalist type, notably &quot;Die Ratten&quot; (The rats, 1911).

Early critics of &quot;The rats&quot; were repelled by the condition of the characters and the apparent formlessness of the plot. &quot;The people of the slums swarm across the stage, some of them as repellent as the villains of Dickens, but less sordid than the figures in Gorki's terrible sink of humanity&quot; (Burrill, 1920 p 30). &quot;The longing of a childless woman for an offspring grows to criminal mania...There is a poetical, even dramatic, germ buried in a chaos of intellectual and artistic aberrations&quot; (Lessing, 1912 pp 127-128).

Later critics obtained a clearer view. The play &quot;clearly shows how the social surroundings influence the character, the whole attitude towards life and its most profound problems. The longing of a mother for a child to replace her first-born which had died soon after birth, strengthened by the concurrence of the wishes of her dearly-beloved husband, grow more and more, and finally gain possession of all her thoughts. She contrives to get a newly born, fatherless babe, and at last connives at the death of the rightful mother when she asserts her claim to the child. The discovery of the whole tragedy involves her own death. The story is curiously and, it must be said, often too lightly linked with a parallel story in the play of a stage director, his daughter and her lover. But this parallel story in its humorous structure adds the most effective contrast to the sombre tragedy we witness&quot; (Hol, 1913 p 34).

“What makes The Rats particularly interesting as a contribution to 20th century theatre is that it is one and the same time a play about people, a social study, and a probing inquiry into the nature of modern drama...Linguistically, the range of the play is indeed enormous; it covers the whole of spoken drama from high tragedy to kitchen sink. Sociologically, it spans an equally wide spectrum, from the criminal underworld of big-city crime and drug abuse to Herr Hassenreuter’s much-vaunted aristocratic connections, appropriately invisible off stage” (Skrine, 1989 pp 58-59). ”This near-masterpiece, vitiated somewhat by discoursiveness, is imaginatively reinforced by the double action maintained on a two-leveled stage. It consists of the comic plot of an old-fashioned stage director in conflict with a pupil...and the naturalistic tragic plot of a woman of the working classes whose obsessive desire for a child implicates her in the murder of an unmarried mother” (Gassner, 1968 pp 526-527). “With The Rats...Hauptmann produced what is probably his masterpiece, since in it he gives full rein to his genuine faculties, now at their heyday, and quite excludes the spurious. In this Berliner Tragikomödie, a pathetic and grim, not to say sordid, story of impassioned maternity, murder and suicide is unfolded with unimpeachable naturalness among scenes of give-and-take intrigue and comical pedantry over which presides the author's finest figure of comedy, the down-at theatre-manager Harro Hassenreuther. It is the perfect mixture, prepared by a realist master-hand, of the seemingly incongruous elements of tragedy and farce, such as the Romantics of France had yearned for and for which the first practical hints are to be found in Ibsen's Wild Duck (1884) and in Lonely Lives (1891)” (Downs, 1926 pp 114-115). Sinden (1957) was particularly struck by one scene. “As Bruno is reporting to his sister in the fourth act...he comes to the climax of his story...one of the most understated accounts of murder, one would think, in all literature” (pp 207-208).

“The hypocritical clergyman, who secretly lusts after the dissipations he reviles in public, who decries his son’s social and artistic efforts in the name of a specious respectability and who, instead of practicing the benevolence he preaches, pushed his daughter to suicide- like many other girls in domestic tragedy- she became pregnant, is a pillar of the bourgeoisie...The young Spitta not only rebels against conservative bourgeois conventions in his fight for humanity, but he also advocates a new type of drama” (Löb, 1975 pp 84-85).  

“Spitta's dramaturgic code, as reflected in the diatribe of Hassenreuter in Hauptmann's 'The rats', sums up in briefest compass the spirit of contemporary dramaturgy: 'You deny the whole art of elocution, the value of the voice in acting! You want to substitute for both the art of toneless speaking! Further you deny the importance of action in the drama and assert it to be a worthless accident, a sop for the groundlings! You deny the validity of poetic justice, of guilt and its necessary expiation. You call all that a vulgar invention- an assertion by means of which the whole moral order of the world is abrogated by the learned and crooked understanding of your single magnificent self! Of the heights of humanity you know nothing. You asserted the other day that, in certain circumstances, a barber or a scrubwoman might as fittingly be the protagonist of a tragedy as Lady Macbeth or King Lear. [In response,] Spitta (still pale, polishing his spectacles) retorts: 'Before art as before the law, all men are equal, sir’&quot; (Henderson, 1914 p 262-263).

==&quot;The rats&quot;==

[[File:Britannica Rat - Black Rat.png|thumb|According to Hassenreuter, human rats are gnawing on German idealism]]

Time: 1910s. Place: Berlin, Germany.

Text at http://www.gutenberg.org/ebooks/9972 https://archive.org/details/twentyfivemodern001705mbp

Mrs Jette John, housekeeper to Harro Hassenreuter, an ex-theatre manager, scolds the pregnant but unmarried Pauline for wanting to return to a worthless lover intending to forget about her. Childless after having lost Adelbert, her own baby, three years ago, Jette proposes to take care of it herself despite being forced to live under conditions of &quot;mildew an' insec'-powder&quot;. To help Jette out in this quest, Harro brings her a milk-boiler. After the baby's birth, Jette notices that the boy's hair is of the same color and shade as Adelbert's and so she gives him the same name and designs to keep the boy for herself. When Pauline returns to find out how her baby is, Jette is irritated, slapping her hard on the ear after an unwelcome comment. Regretting that gesture, she then slaps her own face. When Pauline asks to see the baby a second time, Jette casts looks of hatred at her. Pressured by her landlady who knows about the birth, Pauline informs the registrar's office about this matter and now a man from the guardian office will come over. Harro's daughter, Walpurga, loves her tutor, Erich Spitta, who has ambitions of becoming an actor and a dramatist. Unaware of Walpurga's attachment, Harro gives him acting lessons along with two other pupils in Schiller's &quot;Bride of Messina&quot;. Harro quarrels with Erich concerning forms of dramatic art, the former favoring Schiller, the latter Lessing. &quot;You are a rat, so to speak,&quot; Hassenreuter asserts. &quot;One of those rats who are beginning, in the field of politics, to undermine our glorious and recently united German Empire. They are trying to cheat us of the reward of our labors. And in the garden of German art, these rats are gnawing at the roots of the tree of idealism.&quot; In his son's room, Pastor Spitta discovers a photograph of Walpurga and, unaware that she is his daughter, shows it to Harro. As a result, Harro warns his daughter to reject Erich, or else he will repudiate her. To keep Adelbert as her own, Jette steals a baby from Sidonie, an alcohol and morphine addict who has difficulties in taking care of it, and substitutes it in Adelbert's place while fleeing with Pauline's baby. Pauline returns and tells Harro that Jette has her baby, judged by the authorities to be neglected. A little later, Sidonie alerts the entire tenement by confusedly asserting that her own baby was stolen. On seeing her baby at Harro's, she exclaims: &quot;I swear by the holy mother of God, by Jesus Christ, Father, Son and Holy Ghost, that I am the mother of this child.&quot; Pauline denies this, thinking it is her own. When Hassenreuter looks down at it, the baby is found to be dead. &quot;It seems that invisible to us, one has been in our midst who has delivered judgment, truly according to the manner of Solomon, concerning the poor little passive object of all this strife,&quot; he comments. &quot;Invent something like that, if you can, my good Spitta,&quot; he challenges the potential dramatist. Jette convinces her husband, Paul, that she has given birth while he was out of town at work as a foreman-mason and has taken the baby to his married sister's home in the country. A friend of his, Emil Quaquaro, informs him about the death of Sidonie's baby, along with the doings of Bruno, her brother. &quot;They knows at the police station that Bruno was seen in company o' the Polish girl what wanted to claim this here child, first right outside o' the door here an' then at a certain place on Shore street where the tanners sometimes looses their soakin' hides,&quot; he reveals. &quot;An' now the girl's jus' disappeared. I don' know nothin' o' the particulars, excep' that the police is huntin' for the girl.&quot; Meanwhile, Erich quarrels with his father about Walperga and they part company. When Erich encounters Jette, she expresses herself incoherently. &quot;I was talking to the woman what was struck by lightenin' jus' a short time before,&quot; she rambles on. &quot;An' she says- now listen to me, Mr. Spitta- if you takes a dead child what's lyin' in its carridge an' pushes it out into the sun ... but it's gotta be summer an' midday ... it'll draw breath, it'll cry, it'll come back to life!- You don't believe that, eh? But I seen that with my own eyes.&quot; When the bewildered Erich leaves, Jette and Paul receive a visit from Bruno. Paul loads his revolver as a warning never to come back and then leaves. To Jette's dismay, Bruno reveals that, instead of scaring her off as planned, he has murdered Pauline. She refused to yield her baby. &quot;An' all of a sudden she went for my throat that I thought it'd be the end o' me then an' there,&quot; he says. &quot;Like a dawg she went for me hot an' heavy! An' then...then I got a little bit excited too- an' then, well...that's how it come...&quot; When Erich returns to the John home, he glances at Jette sleeping on the couch. &quot;Great drops of sweat are standing on her forehead.&quot; he reports to Walpurga. &quot;Come here. Just look at the rusty old horseshoe that she is clasping with both hands.&quot; Knowing that Erich and Walpurga love each other, Teresa, Harro's wife, tries to intervene on their behalf before her husband. Recently appointed as manager of a theatre, he promises to express a more lenient view of the matter. He reveals to Jette that Sidonie's baby is dead, as well as the news how police officers have discovered that she never went with the boy to her husband's sister, having been seen by the park near the river. Paul is tired of living in a rat-infested house and decides to bring the baby over to his sister, but Jette reveals that the child is not his. Sidonie's daughter, Selma, arrives and informs them that the police have concluded that she brought down Pauline's baby from Harro's loft to her. Piece by piece, Paul discovers the truth about his wife's scheming. &quot;So you bargained for that there kid someway an' when its mother wanted it back you got Bruno to kill her?&quot; Mr John accuses his wife. &quot;You ain't no husband o' mine. How could that be! You been bought by the police. You took money to give me up to my death. Go on, Paul, you ain't human even. You got poison in your eyes an' teeth like wolves'!&quot; she counters. &quot;Go on an' whistle so they'll come an' take me. Go on, I says. Now I see the kind o'man you is an' I'll despise you to the day o' judgment!&quot; In a fit of rage and despair, Jette takes hold of the baby, but is prevented from leaving with him. She then blindly rushes out and before anyone can prevent it, kills herself in the middle of the street.

=Bertolt Brecht=

[[File:Bertolt-Brecht.jpg|thumb|Bertolt Brecht is one of the major playwrights of the 20th century, 1956]]

The main dramatist in German-speaking theatre of the period before and during World World II is Bertolt Brecht (1898-1956), whose major plays include &quot;Die Dreigroschenoper&quot; (The threepenny opera, 1928), &quot;Mutter Courage und ihre Kinder&quot; (Mother Courage and her children, 1939), &quot;Der gute Mensch von Sezuan&quot; (The good person of Szechwan, 1943), and &quot;Der kaukasische Kreidekreis&quot; (The Caucasian chalk circle, 1945), plays co-written with Elisabeth Hauptmann, Magarete Steffin, Ruth Berlau, Martin Pohl, Hella Wuolijoki, and others (Bloom, 2005a p 224; Fuegi, 1994a,b pp 104-114). Brecht promoted an &quot;epic theatre&quot; where alienation is sought, &quot;the very opposite of the technique of illusion which has been traditionally employed on the Western stage, where the principal aim of the playwright was always to draw the spectator into the world created in the play...On the contrary, Brecht tries to break the magic of the theater...into realization that he is attending only a performance, looking at actors, witnessing parables from which he should draw dispassionate conclusions&quot; (Alter, 1964 p 61-62). “Brecht’s plays are picaresque, poetic narrations for the stage. They are based on brief episodes of concentrated action- most of them almost complete in themselves- each of which makes a simple, sharp point essential to the understanding of the play’s idea as a whole. The intellectual approach is tersely factual, the tone ironic, crisp and detached” (Clurman, 1966 p 52). Yet “emotions are by no means excluded from his theatre: he was only against an audience’s intellectual drain caused by total illusionary identification with the character on the stage” (Hill, 1975 p 106).

The Threepenny Opera originated from John Gay's The Beggar's Opera (1728) but differs from the earlier play in several ways. Gay’s Macheath is a dashing cavalier and Polly is the semblance of a lady, so that rogues and whores appear like the higher classes. By contrast, Brecht’s Mack the Knife is meant to seem like a businessman and indeed says to Polly he considers himself as one, so that rogues and whores appear like the middle classes. To her he says his condition is being 'ruined by large concerns backed by banks'. In terms of robbery, the middle class has him beaten: 'What is the robbing of bank compared with the founding of a bank?' he asks ironically. By sending out his band of derelicts, his business partner, Peachum, exploits Christian charity, in league with capitalism, by recognizing that the rich 'create misery but cannot bear to see it'. Mack is also in cahoots with the police chief, Tiger Brown. While Mack betrays some criminals over to him, Tiger provides him with protection. Changes from Gay’s text also include the addition that “the action involving Macheath and his cronies is greatly expanded, as are Peachum’s unscrupulous business dealings” (Parker, 2014 p 245). Bentley (1982) underlined that the play's &quot;enemy was the same element in the population that had opposed The Beggar's Opera two hundred years earlier...Bertolt Brecht changed the characters of The Beggar's Opera rather more than the story, eliminating Lockit altogether in order to make of Lucy's father an entirely new character, Tiger Brown, Sheriff of London...In John Gay's text the arch-criminal had been Peachum, to whom was assigned the notorious and ultimate crime of the historical Jonathan Wild: that he did not respect even 'honor among thieves', but turned in his own men to the authorities. That was 'peaching'. In the Brecht version, Macheath 'peaches' and so is deprived of any moral superiority to his competitors and colleagues: the point would seem to be that the whole world of Three-penny is without ethics. Polly, who had been an innocent in the Gay, is here at best ignorant, losing not innocence but ignorance as the action proceeds...Where does The Threepenny Opera diverge most widely from its predecessor? In...its characterization of Peachum [and the] songs. The 'shock value' in Gay's Peachum lay in the circumstance that one whom we expected to be only a receiver of stolen goods in fact goes on from there to 'peach'um'...Since in Threepenny everyone is bad in a bad world, if Peachum stands out, it has to be for something other than pure wickedness...He regards misery as a commodity: his brainstorm is that poverty can be wealth&quot; (pp 19-20). Although Macheath was intended to be a reprehensible gangster who simply adapts the standard practices of business under capitalism to his own immoral way of life, he remains too much of a charming, even romantic, he-man, sex symbol, and villain. After all, he has the only lines that can be called revolutionary: his call for beating up policemen toward the end of the play. The operatic fairy tale happy ending finally underlines the ambiguous character of any hidden social message...Macheath...is motivated and doomed less by notions emanating from the bourgeois class than by Baalian sex appetites and habits stronger than reason or socio-economic factors” (Hill, 1975 p 57). &quot;Fierce though the conditions of their life are, the beggars, crooks and whores of The Threepenny Opera are far from cast down by this fact. Rather, they practise a cheerful form of cynicism as they go about the nasty, but nonetheless highly enjoyable business of doing one another down. The style of the opera, too, with its mix of picaresque farce and melodrama, is equally bent on getting as much fun as it can out of the world as it is&quot; (Speirs, 1987 p 34).

Mother Courage and her Children comprises &quot;the picture of a world in which the very victims of the war are trying to profit by it and share the social responsibility, venality, and confusions intrinsic to the social situation” (Gassner, 1954b p 87). “While his twelve scenes convey the overpowering impression of huge armies incessantly on the move in a never-ending war, the ever-present covered wagon effectively unites the few protagonists and gives added coherence to their specific actions” (Hill, 1975 p 110). “In the first scene, the would-be recruitment of the sons is interrupted by the sale of belt, the sale of the belt by the loss of Mother Courage’s eldest son; the sale of the capon in the next scene is interrupted by his return, a hero. The bargaining over the capon is echoed by the bargaining Eilif reports he carried on with the peasants, and this series of gestures of bargaining reaches its climax with the bargaining Mother Courage indulges in (for quite understandable reasons) as Swiss Cheese faces the firing squad. The reverberations...are set up by concentrating on pregnant moments rather than on the more conventional means of unfolding the story” (Leach, 1994 p 135). “Swiss Cheese is executed because Courage haggles too long over the amount of a bribe...Swiss Cheese has been captured because he lacks the very qualities that lead Courage to haggle...This...suggests a fatalistic view of human action...When a temporary peace finally comes, Courage cries out against it, since it will be bad for business. It is also bad for Eiliff, who is arrested and destined to be executed for an act which won him praise as a hero during the fighting. In a sense, then, peace is as destructive to Courage’s children as war” (Calarco, 1969 p 167). “Mother Courage is involved in a business deal each time one of her children is killed” (Abbott, 1989 p 97). “Fierling’s haggling in the painful experience of scene three is an image of far greater complexity than the more simple bargaining of the first scene. It is not a pure greed which motivates the delay that causes the death of Swiss Cheese; the sutler’s wagon, which is at stake, is the means of existence for Mother Courage and Kattrin” (Lyons, 2002 p 38). “In the loss of the three children- whom Mother Courage’s sleazy, haggling, cold-eyed selling of supplies to the army from her wagon is precisely designed to protect and preserve- we are shown the immense irony of the way in which making a living destroys life, how the process of preservation brings about the ruin of that human substance which is being preserved” (Gilman, 1971 p 42). Yet, for other critics, “scene 3 in which Mother Courage loses her honest son by haggling too long for his release and then is forced to view his corpse without showing signs of recognition is full of an almost unbearable suspense and has an emotional impact of the most gripping kind” (Hill, 1975 110). Each of her children “embodies a virtue that contains the seeds of his destruction. Eiliff, whom the commander praises for his heroism as a new Julius Caesar, follows Caesar’s fate. Swiss Cheese perishes for his scrupulous honesty when he tries to hide the strongbox, and thus, like Socrates, receives death instead of thanks. Finally, the dumb Kattrin, who has been described by her mother as suffering from ‘sheer pity’ will repeat the fate of Martin, who ‘could not bear his fellow creature’s woe’ and died a martyr’s death” (Grace, 1973 p 314). &quot;The protagonist is only courageous in her tenacity. She courageously breached the lines during the bombardment at Riga only to prevent some loaves of bread to become mouldy. She epitomizes the sufferings of the nameless masses in the cataclysm of war&quot; (Garten, 1964 p 123) but “always chooses the most selfish, ignominious, and profitable course” (Brustein, 1964 pp 269). “She is not an image of ‘the indestructibility of a vital person afflicted by the inequities of war’ (Brecht quote) but almost wholly the opposite: one of the destructibility of humanity within the prevailing system, no matter how tenacious, sinewy, and energetic a particular person might be...She is exemplary not in being a survivor but in being one at a terrible cost; her virtues thus function dramatically not as attributes to be admired but as annihilated possibilities to be mourned” (Gilman, 1999 pp 227-229). “Accepting her plight with a willed blindness within her courageous attitude, this ‘great’ survivor lives off the war and loses her children one after another, each ironically on account of the principal virtue that they embody, which is revealed as their greatest weakness. What is more, when faced by the unenviable choice of losing her livelihood or a child, she makes a business calculation, through which in practice she opts for her livelihood and reveals herself to be, in the words of the Chaplain, a ‘hyena of the battlefield’. Unable to reconcile the contradictions in her life, Courage is reduced to a classic Brechtian didivual”  (Parker, 2014 p 413). &quot;Courage not only proves herself unable to prevent her children's deaths, but demonstrates her deep complicity by profiting from the very acts of war that lead to them. This complicity is made especially obvious in the case of the younger son, who dies because Courage attempts to haggle down his executioner's bribe even though she has enough money to pay the asking price for his life...Whereas the brothers die as bewildered, dumb victims of the war, revealed in death to have been the pawns of arbitrary, anonymous forces beyond their knowledge and control, the play frames Kattrin's death as a heroic triumph- not an abject fall but a willed, purposeful end, claimed by Kattrin in her final, self-sacrificing act of resistance and used by her so that even her death comes to serve and safeguard life...During each set of events that lead to the death of her brothers, Kattrin proves unable to deliver an urgent, vital message that would save their lives if it were recognized by its intended recipients...Kattrin's voicelessness makes concretely manifest an underlying history of...traumatic violence and it is this silencing message...that the characters...refuse to hear. In particular, when Kattrin is assaulted, her mother declines to hear what happened&quot; (Vork, 2013 pp 32-43). “Mother Courage is a dialectically conceived figure. In other words, both she and the situations she finds herself in are systematically built on contradiction. Earning her living as a 'sutler' or camp-follower who provisions the soldiery, Mother Courage occupies a contradictory class position. Her 'crime' in seeking out the war in order to profit from it ('I can't wait till the war is good enough to come to Bamberg') is that of the capitalist class (at that time a rising class, according to the Marxist interpretation of history). On the other hand, as a small trader- and businesses do not come much smaller than hers- she is also one of the common people who simply have to survive as best they can in the social and economic system of their times. This class ambiguity underlies the most obvious contradiction in her life, that between her trade and her role as mother. As Brecht put it, 'The trader-mother became a great, living contradiction.’ She embodies, as it were, the class-struggle in her own person, for whenever she acts as a 'capitalist', seizing some opportunity for profit, she invariably damages her interest as a member of the exploited classes, or, more particularly, as the mother of children who belong to that group. The fate of the family illustrates the fundamental contradiction of war - that it 'renders human virtues deadly, even for those who possess them', and shows this in turn to be the outcome of the harsh logic of class-society, by virtue of which the productivity of ordinary people is turned into a force that operates against their own interests” (Speirs, 1987 pp 93-94). 

“The special charm of The Good Person of Szechwan'...rests...on a stance of ceremonial politeness and distant human relations, expressed in an understated language of austere lyricism which westerners usually associate with Chinese culture and philosophy” (Hill, 1975 p 126). In the play, &quot;it is impossible to be good, in the traditional sense of altruistic, gentle, loving, in a world that lives by egoism, rapacity, and hate. A Christian might argue: 'you can't change the world. All you can do is to exercise the Christian virtues in your own small circle.' Brecht replies: 'This is topsy-turvy reasoning. Your small circle is no circle but a segment of a large circle. The segment has no independence. It can move only when the whole circle moves. Only by altering the world can goodness become practical.' Shen Te wished to be kind. But on one occasion she finds herself allowing an old couple to be ruined because she does not pay her debt to them. On another occasion she will not help a poor man to find redress for an injury willfully inflicted by the Barber Shu Fu because at the time she is trying to win Shu Fu's lucrative hand. In order to survive, the good girl needs the assistance of the brutal exploiter. And when she appeals to the gods she receives as answer: 'are we to confess that our laws are lethal? Are we to repudiate our laws? Never! Is the world to be changed? How? By whom? No: everything is all right'&quot; (Bentley, 1955 p 224). “The Good Person of Szechwan is an example of a parable which illuminates a 'truth' that could never be established by describing life naturalistically, because the 'good person' in each of us supposedly disappears at an early age under the pressure of the alienating conditions of everyday social existence...Brecht's parable makes the crucial assumption that human nature is fundamentally good. Yet this tenet of Marxist humanism is no scientifically demonstrable truth, but rather an article of faith. Indeed the Marxist concept of 'alienation' both asserts the existence of this human quality in nature, from which man has become separated through the evolution of culture, and makes such a quality undemonstrable by virtue of the processes that have supposedly corrupted it. Thus, if the spectator assents to the parable's assumptions about human nature, his willingness to 'suspend his disbelief' has no authority other than his own intuition of such a predisposition to goodness within himself, or his inclination to identify with this model of his innermost nature. To encourage identification with Shen Teh, Brecht makes her not merely good, but gener- ous, gentle, warm, gifted with a sense of humour- and pretty as well. Any survey of productions of the play quickly shows how much its success in performance depends on the central role being played by an attractive young woman” (Speirs, 1987 pp 139-146), a form of prejudice linked to moral judgments. From this play, “we may derive some working generalizations...There is no such thing as the innate nature of man. Man is not by nature good or evil, heroic or non-heroic. Man is a process and the nature of that process is determined by social conditions” (Abbott, 1989 p 90). “By splitting the one person into stereotypical masculine and feminine aspects and showing that polarity as destructive and deceitful, Brecht- consciously or not- makes suspect the cliche of the constructive and healing quality of polar contrasts in men and women. In answer to Brecht’s question in the Epilogue whether we need a new person, a new world, or different gods, the prevalent reaction by critics has been to point to social circumstances alone and call for a different world. That answer is based on the assumption that Brecht’s Marxist convictions require economic solutions or changes of systems. Looking at the intrinsic message of the drama, however, the Shen Te/Shui Ta division appears as a major issue in itself, which is linked to the economic one, not subordinated to it. It seems that a more viable person would be one who can balance and integrate the qualities of Shen Te and Shui Ta” (Lug, 2002 p 54). &quot;The split of the good person into Shen Te and Shui Ta appears, thus, to be a theatrical model for the division of middle-class man into a private, and a business, self. Through ‘being bad’, the business self guarantees the possibility that the private self can be good&quot; (Fischer-Lichte, 2002 p 322). Hodge (1963) compared &quot;The good person of Szechwan&quot; to Wilder's &quot;The skin of our teeth&quot; (1942). &quot;In the Wilder [play], man is blind and foolish but means well; he tries to profit from the past; he loses faith, manages to escape disasters by the skin of his teeth, helped by the practical common sense of women, picks up, and struggles on. Brecht's man is not drawn on such a wide, historical scale. He is mean, petty, lost. In his blindness and idealism he destroys his fellow man as quickly with soft handouts as he does with ruthless exploitation. Man's existence lies somewhere between these extremes, and man can change the world only by gradually achieving this median good. There is even a similar scene in the two plays as Mr Antrobus in Wilder's play and Shen Te in Brecht's deal with the problems of what to do with the poor and homeless. And both plays use the theatrical devices of direct address to the audience, interruptions for speeches or songs, overt philosophical statements by either gods or philosophers. Both use the physical stage not as an exact place, but as a suggested reality&quot; (p 84). One can specify that in the Brecht play it is not so much man who is &quot;mean, petty, lost&quot; but the social environment man has created, and so the social structure must change so that man can change. &quot;But the gods decree otherwise. Since they have found Shen Te in Shui Ta again, they declare their search for a good person at an end and are satisfied that the world should continue unchanged&quot; (Fischer-Lichte, 2002 p 322). “Whilst Shui Ta evicts the family, preserves the business and rapidly expands it, he also lacks a social conscience, manipulates Shen Te's lover, Yang Sun, into becoming the ruthless foreman in his tobacco sweat shop and provides accommodation for the workers that enables them to function in the factory but is little better than a slum. Shen Te is an equally split personality. She saves a young flyer from suicide, gives him new hope with her pledge to help him fly and is thrilled at the prospect of having his child. But she also recognises that in such a cut-throat world she will have to fight like a tiger to protect her offspring, is unable to avoid being exploited by spongers on account of her generous nature and is blind to the fact that Yang Sun is only prepared to marry her so that he can obtain her money to advance his own career” (Shellard, 1999 p 78). &quot;Shui Ta...pleads that there must be something wrong with a world which penalises kindliness and favours rapacity. The gods, however, are not disposed to listen to a plea which strikes at the root of the existing world order. They prefer to turn a blind eye to the activities of the hard-hearted cousin, or to trivialise them; talking in pious clichés, they deliberately blur the issue, sidestepping the problem of guilt and sin. Nor are they prepared to give the heroine any help or guidance for the future. They consider that their mission on earth is accomplished, and they blandly assure Shen Te that in their heavenly abode beyond the stars they will gladly remember the Good Woman of Szechwan, who by her goodness witnesses here below to the gods' existence and to the sanctity of their commandments. And when she insists that she will not be able to manage without her cousin, they compromise with sin by telling her that she must not fall back on her cousin's help too often: once a month will be enough. Whereupon they are borne up to heaven on a rose-coloured cloud, smiling benignly and waving as they ascend, leaving all the heroine's problems unsolved. In his closing scene, Brecht presents a marxist parody of divine judgment. As usual, he invites his audience not to identify themselves emotionally with any of the characters but to view the events on the stage with 'alienated' detachment, and to draw their own conclusions&quot; (Witte, 1968 p 11). “It is perhaps the crowning irony of the play that it is precisely the fact of Shen Te's pregnancy which explicitly and finally alienates Shen Te from her biological role of woman and which demands the total metamorphosis of the woman Shen Te into the man Shui Ta...Instantly the otherwise mild Shen Te becomes now, almost permanently, the ruthless Shui Ta. Clearly, in the world of Setzuan, the instinct of motherhood triggers unbridled savagery against everyone else. Now all restraint is removed on Shui Ta as he seeks to expand his tobacco holdings into a manufacturing and chain-store enterprise, employing, among others, child laborers, an enterprise designed to support magnificently Shen Te's child...Brecht, piling irony upon irony, has Sun who had refused to work with the female Shen Te equally in her original tobacco business, now working on a unequal basis for the male Shui Ta. But the artificial world of the disguised Shen Te begins to collapse as her pregnancy advances. The stratagem that was necessitated by the pregnancy is destroyed by the pregnancy” (Fuegi, 1974 pp 195-196). “The final trial scene is one of those high moments of art when character and symbolism coalesce” (Tynan, 1961 p 147).

The Caucasian Chalk Circle, “Brecht wrote a parable on the question: how is it possible to be a decent human being under the pressures and corruptions of a world of exploiters and exploited? In the playwright’s quizzical view of the human condition, it is not only difficult to be good and to do good in the world, it is incongruous and therefore comic...[The play] was bound to encounter resistance on the Broadway stage, since American optimism would normally reject the ‘good person as fool’ theme as cynical...Not only does goodness find itself betrayed by those it is willing to help, but it betrays itself...by being practical, for its practicality is indistinguishable from ruthlessness” (Gassner, 1960 pp 264-265). &quot;There is the strong, calm, brave, shrewd, commonsensical, compassionate, decent, naïve, angry, and cheerful Grusha...and there is the super-schweyk Azdak, the corrupt, scandalous judge, full of folksy wisdom, coward and hero, a rogue, a cheat, and yet a man with a heart” (Hill, 1975 p 138). “Instead of simply displaying relationships between individuals, each group of figures is animated by the interaction between social classes that constitutes social relations as such...In this way, Brecht shows that what may be thought to be purely individual action is social through and through...The peasant who cheats Grusha, a servant from his own class, does so on the grounds that war engenders economic hardship. To his mind, this justifies profiteering and exploitation irrespective of who is being exploited, fellow peasant or gentry. Moreover, the peasant’s lack of compassion for Grusha shows that there is no natural, self-evident or intrinsic class solidarity between them, any more that there is anything naturally greedy about him or naturally maternal about her” (Shevtsova, 1994 p 155). The conclusion “is a modern parable in that it is told not to exemplify a doctrine but rather to reveal a paradox: Grusha’s sacrifice is recognized as superior to the natural ties which bind the governor’s wife to her own child” (Politzer, 1965 p 64). &quot;The servant Grusha gets the child, not because she took upon herself such great privations on its account and for this reason might perhaps present her merits as a claim to its possession, but because she is willing to keep it 'until it knows all words', i.e. because she is useful to the child, which needs the guidance and help of a mother in order to become a useful member of society. The governor's wife, whose biological rights are uncontested, and to whom the judge would perhaps restore the child if this decision were good for the child, does not want the child for its sake but for her own, for the inheritance is bound up with the child...And just as Judge Azdak by means of the chalk-circle test merely finds out exactly whether he has sufficient grounds for the correctness of his verdict, so the assembly of the two villages in the Prologue takes place in order to produce the certainty that no new and more important arguments have been overlooked, or, otherwise, to discuss the existing arguments in common...In the chalk-circle story, the one party loses and the other gains. In the decision between the two villages this is only seemingly the case. In reality both gain, because both acknowledge the social order in which they live...Whereas, however, Azdak has to prove his progressiveness in defiance of the prevailing social order, in the dispute of the two villages it is the progressive social order which not only justifies this mode of action but promotes it&quot; (Bunge, 1959 pp 59-63). Alter (1964) underlined alienation effects abounding in &quot;The Caucasian chalk circle&quot;, for example &quot;an iron-shirt corporal berates his subordinate, not as one would expect for acts of brutality that he committed, but for not having enjoyed them! Obviously such a remark comes as a jolt, awakens the spectator, and makes him suddenly aware that he is witnessing the display of the wit of the playwright and not a real incident. It also makes him reflect on the implications of the military mind. Similarly, when Azdak demonstrates quite logically that justice, like meat, should be bought at a price, the spectator is shocked, stops identifying with the advocate of such subversive ideas, but nonetheless is encouraged to re-examine the nature of justice. In fact, all of Azdak's paradoxical pronouncements disturb the average spectator's worldview&quot; (p 63). “Azdak is a sort of lord of misrule, one of Brecht’s cunning rogues…During his tenure, he proves to be corrupt, licentious, and contemptuous of the law, yet often he turns the law upside down to help the poor” (Michaels, 1986a pp 242-243). &quot;Brecht's judge consistently favours the lower classes. He uses the authority of his office to counteract the effects of social inequality, aiming, not at justice-according-to-law, nor at moral justice, but at what he conceives to be social justice&quot; (Witte, 1968 p 13). “Azdak holds the sympathy of the audience by virtue of the amusing, witty way he combines self-interest (always at the cost of the better-off) with concern to provide a modicum of justice for those brought before him. Because the palace revolution has not brought about the onset of a 'new age', but merely an age of 'new masters', Azdak realises that he cannot act on the basis of a new conception of justice, but must simply adapt to his own purposes the existing legal system. His way of proceeding is dialectical, exemplifying what Brecht defined as 'the negation of a negation'; because the existing laws are designed to protect the interests of the property-owning classes, Azdak always finds in favour of those who have none, basing himself on the assumption that the ultimate cause of the 'crimes' brought before him is to be found in the inequitable distribution of wealth in society. Until a revolution has created conditions in which there is no longer any fundamental conflict of interest between an individual or section of society and society at large (as in the 'Struggle for the Valley'), Azdak's rough class-justice is the best his individual reason can make of a society founded on unreasonable principles” (Speirs, 1987 p 169).   
 
==&quot;The threepenny opera&quot;==  

[[File:Televisiestuk_Drie_stuivers_opera_,_Hans_Kaart_(Peachum)_temidden_van_bedelaa…,_Bestanddeelnr_911-7337.jpg|thumb|Played by Hans Kaart (1920-1963), Peachum examines his cronies out to cheat and rob. 1960 German TV production]]

Time: 1837. Place: London, England.

Text at https://archive.org/details/in.ernet.dli.2015.186884 https://pdfcoffee.com/bertolt-brecht-the-threepenny-opera-1928-pdf-free.html

Peachum, head of a large section of London beggars and robbers, makes sure that those under his area of influence pay him earnings in exchange for protection. When he notices his daughter, Polly, under the influence of the robber, Macheath, he is determined to hinder their relation. Macheath prepares to marry Polly, though with no vows exchanged and no priest present. The chief of police, Tiger Brown, intervenes, not to arrest Macheath but rather to continue their amiable and fruitful relations. Polly defies her parents by announcing her marriage, though inadvertently revealing Brown's connection with Macheath. Warned by Polly of her declaration, Macheath prepares to leave London, but stops at his favorite brothel on his way to see another girlfriend, Jenny, but unfortunately bribed by Mrs Peachum to betray him. Although Brown apologizes, he is forced this time to arrest Macheath. Another among Macheath's lovers, Lucy, Brown's daughter, quarrels with Polly over who should win Macheath. Lucy succeeds in helping him escape from prison. When Peachum finds out, he threatens Brown by saying he will let loose his beggars to ruin the queen's coronation, likely costing him his position. When Jenny arrives for her pay, Mrs Peachum refuses to give it to her. Meanwhile, Macheath hides at Suky Tawdry's house. Brown receives confirmation of the reality of Peachum's threat, so that he is again forced to arrest Macheath. To avoid execution, Macheath desperately tries to raise a sufficient bribe for Brown, but none can or wish to to help. As the gallows are assembled, a messenger arrives to announce that Macheath has received the queen's pardon in the general jubilation.

==&quot;Mother Courage and her children&quot;== 


Time: 17th century. Place: Germanic territory.

Text at http://www.socialiststories.com/writers/bertolt-brecht/

During the course of the Thirty Years War, canteen woman, Mother Courage, and her three children, Eilif, Kattrin, and Swiss Cheese, trade with Protestant soldiers to survive. Kattrin is mute as a result of an object having been placed in her mouth. While she negotiates with a sergeant for wares, his recruiting officer secretly leads Eilif away with him. Two years later, Eilif is praised by a general for killing peasants and slaughtering their cattle. For taking such risks that could have been avoided, Mother Courage scolds her son and slaps his face. Three years later, Swiss Cheese works as an army paymaster and hides the regiment's paybox before the arrival of Catholic troops, but before he can escape they capture him. Although Mother Courage negotiates to free him, he is shot to death for theft. She is forced not to acknowledge him as he is unceremoniously plunged into a grave. By force of circumstances, she plies her trade on the Catholic side. As General Tilly's funeral service is about to start, the chaplain asks Mother Courage to marry him, but she refuses. One day, she finds Kattrin disfigured after obtaining some piece of merchandise. As Mother Courage departs for yet another town, Eilif is dragged in by soldiers and executed for killing peasants, without her even knowing about it. By another force of circumstances, Mother Courage returns to the Protestant side. She finds a cook to help start a new business at an inn in Utrecht, but he wants nothing to do with the disfigured Kattrin and so she is forced to refuse his offer. When the Catholic army is ready to attack the Protestant town of Halle with her mother away, Kattrin climbs on the roof and beats on a drum to warn the townspeople. As a result, she is shot to death by the soldiers. Mother Courage sings to her daughter's corpse and then hitches herself alone to the cart, much lighter now with her children dead and the little merchandise left to her.

==&quot;The Caucasian chalk circle&quot;==

[[File:Der kaukasische Kreidekreis.JPG|thumb|An alcoholic, Azdak, played by Torsten Schemmel (1979-?), assumes the role of a judge and only at the very end shows signs of judgment, Vorpommersche Landesbühne, 2009]]

Time: 1940s and Medieval. Place: Caucasus, Russia.

Text at http://www.archive.org/details/parablesfortheat00brec https://archive.org/details/in.ernet.dli.2015.186884 http://www.socialiststories.com/writers/bertolt-brecht https://archive.org/details/dli.bengal.10689.16645 https://archive.org/details/dli.bengal.10689.12044 

A group of villagers settle their dispute about territories in the post-war period and then sit together to watch a play entitled: &quot;The Caucasian chalk circle&quot;, concerning events in the medieval period when a band of princes revolt against their arch-duke, killing his appointed governor, so that his wife, Natella Abaschvili, must flee at once. In the hurry of securing her dresses, she forgets to bring her baby along with her. The baby is found by a kitchen servant, Groucha, who decides to care for him as if he were her own. She and Simon intend to marry, though for now he must leave as a soldier in the civil war. On her way to safety, Groucha experiences hard times. She must negotiate exorbitant prices for milk with a peasant, is rejected from a company of ladies because of her hands, obviously a domestic's, hits from behind a suspicious police-sergeant looking for the governor's son, and crosses a dangerous bridge on her way to her brother, who, for the sake of appearances, in view of her carrying around an infant, advises her to marry a dying man, Youssup. But, to everyone's surprise, Youssup regains his health and so she is stuck with him. When Simon returns from war, he is disappointed to find her married. She explains the baby is not hers, but, when a soldier arrives to ask her who the baby is, she is forced to say it is hers after all. Unwilling to hear more, Simon leaves her, while the other soldier, believing the boy to be the governor's son, takes him from her. In the new regime, a village scrivener named Azdak is appointed judge. He is a drunkard, as well as outrageously incompetent and unjust. Sitting before a dispute between Groucha and Natella, who wants her boy back, he first demands money from both sides and then listens to a separate case at the same time. Unnerved that the richer Natella has two lawyers on her side and Groucha none so that that the odds seem stacked against her, Groucha calls Azdak a &quot;wine sponge&quot; and curses his style of justice. Azdak proposes to find the truth on the affair by drawing a chalk circle, outside which Natella and Groucha are to pull the child towards them. Afraid to hurt the child, Groucha almost immediately lets go while Natella pulls hard, whereby Azdak, at last showing Solomon-like wisdom as reported in 1 Kings 3:16–28 and considering Groucha the true mother, awards him to her.

==&quot;The good person of Szechwan&quot;==

[[File:Mit-zu_-_La_bona_persona_de_Sezuán.jpg|thumb|Mi Tsu demands that Shen Te provide a reference before settling in her lodging. 1982 drawing on acrílic sobre paper]]

Time: 1940s. Place: Szechwan province, China.

Text at http://www.archive.org/details/parablesfortheat00brec http://www.socialiststories.com/writers/bertolt-brecht/ 

A water merchant scrambles to find a lodging for three gods descended on earth to examine the doings of humanity. After many refusals, he finds one who accepts, Shen Te, a prostitute, whom the gods reward with money for her kindness, which enables her to open a tobacco shop. But because of her goodness, she is quickly taken advantage of by a family of eight, who, after being lodged for free, destroy or steal a good part of her merchandise. Before Shen Te settles in definitely in her new lodging, Mi Tsu, the owner of the building, requires from her a letter of reference. She chooses a cousin of hers, Shui Ta, a man with a more direct and rougher type of personality, who rids her of the lodgers, enabling her to start business on a better footing. Shen Te befriends Yang Sun, an airplane pilot out of work who needs money to take advantage of a job offer in Peking. To pay her rent, Shen Te borrows money from a rug merchant next door, but then gives the money to Sun. In financial trouble again, Shen Te receives an offer from Mi Tsu to sell her shop. Sun wants that sum of money, too, but Shui Ta prevents that from happening. Shen Te decides to marry Sun, who insists on waiting for her cousin to get the rest of the money. But since the cousin never shows up, he leaves her. Impressed by her many charitable works, a barber gives Shen Te a large sum of money, with which she pays the rug merchant, but it is too late, his properties having been seized. A pregnant Shen Te needs help from her cousin again, this time to manage the barber's money, thanks to which the homeless find shelter, though with rotten floors, and the jobless a job, though grossly underpaid. Learning about Shen Te's pregnancy, Sun comes back and is given a post as superintendent. He proves himself to be a particularly exacting one. Shui Ta's ambitions increase to the point of wanting to open 12 tobacco shops, but neighbors becomes suspicious of Shen Te's prolonged absence. Shui Ta is thus arrested on the suspicion of having murdered her and taken to court with the three gods acting as judges. Shui Ta is defended by the rich and accused by the poor and eventually forced to reveal himself as the disguised Shen Te. The gods wonder about their commandments to be good in such a society: &quot;Is it possible that our commandments are murderous?&quot; they ask themselves.

=Marieluise Fleißer=

[[File:Statue_von_Marieluise_Fleißer_mod.jpg |thumb|Fleißer described the disorientation prominent among adolescents]]

Of note among realist dramatists is Marieluise Fleißer (1901-1974) with &quot;Fegefeuer in Ingolstadt&quot; (Purgatory in Ingolstadt, 1926), based on her short story &quot;The thirteen years&quot; (Kord, 1989 p 59). The theme of victimized youth echoes Wedekind's &quot;Spring awakening&quot; (1891).

In Purgatory in Ingolstadt, “the aggressive tactics used to cut one another down to size are a more significant aspect...than the subjects they talk about...None of the characters show great finesse in directing the flow of talk nor are they adept at anticipating the responses of their conversation partners...Each character feels obliged to respond to other characters who have initiated exchanges...Family rivalries are not aired in front of outsiders...It is a tug of war where no one gets anywhere...Gossip and slander are pervasive...and are weapons in the struggle for status. The readiness with which they use religious phraseology may, in fact, indicate a generally uncritical stance toward all traditional ideologies and explanations” (Hoffmeister, 1983 pp 25-41). “Gervase and Protase...always appearing out of nowhere to do their dirty work for the doctor...are a major factor in creating an ambience that smacks of the police state” (Ley, 1986 p 617).

“The young people of Fleisser's play are trapped in their own vicious world of hatred and envy, of spying and extortion, of humiliation and oppression, of excruciating loneliness and of an emptiness which cries out for a redeemer. This redeemer can only be somebody who will appeal to the baser side of their nature. The type of Christianity practised by these young people (and, behind the scenes, their elders) is actually a perversion o f religion, since it excludes its most essential component, love. The negative Catholicism of the play puts its emphasis on a harsh God eager to punish sinners, on rigid commandments, stern moral principles, endless prohibitions. Under its influence self-esteem is torn down and the personality deformed; the major concern is with one's own sins and salvation rather than with the liberation of one's neighbor from oppression” (Ley, 1988 p 342).

&quot;The outcasts from the pack are Roelle and Olga. Roelle, hydrophobic, attention-seeking, and subject to society's contempt, asserts his influence on Olga, who, because of her education and her unwanted pregnancy, is also ostracized by the community. When Pepe leaves Olga for Hermine, Olga loses all hope for a secure status in society. Here, Roelle sees an opportunity to make Olga dependent. She defends him in front of Protasius, who appears to her as a representative of the community, and she seems to admire Roelle's position outside of society, possibly even outside of humanity...Roelle, however, seeks readmission into society, not on the same footing as its other members, but rather as the outsider above the community. By pretending superiority in the form of religious enlightenment, he attempts to define himself as a 'sanctified outsider', and tries to elevate Olga to the same level...For Olga, it is imperative that her fellow outcast profess himself superior to society, since the alliance with him is all she has to replace her lost position in the community. Accordingly, she rewards assertive declarations from Roelle with supportive remarks...When Olga disavows her alliance with Roelle, she has the choice of either attempting to return to society or of establishing complete independence from both society and Roelle. She does not, however, consider the possibility of independence seriously. She discusses it in terms of escapism, regards complete anonymity as the only possible freedom, and admits that even this hypothetical form of escape cannot be accomplished without male assistance...Since there is no third choice, her break with Roelle, the fellow outcast, necessitates Olga's attempt to rejoin society. Consequently, she joins society in its contempt of Roelle...But her attempts to escape, whether through Roelle or America, are doomed&quot;(Kord, 1989 pp 59-61). &quot;Fleißer's Purgatory in Ingolstadt is an indictment of the Catholic establishment. The drama explores the indoctrination of young people of both sexes and the destruction in the lives of women caused by the internalization of the traditional religious concepts&quot; (Lorenz, 1993 p 121).

==&quot;Purgatory in Ingolstadt&quot;==

[[File:Ingolstadt_-_Kriegerdenkmal.jpg|thumb|Ingolstadt in the 1910s]]

Time: 1920s. Place: Ingolstadt, Germany.

Text at ?

Peps asks his girlfriend, Olga, whether she has had her abortion yet. She answers no. &quot;Do what you must,&quot; he threatens, &quot;or else you'll know who I am.&quot; One of her acquaintances, Protasius, requests her to use her influence on their mutual friend, Roelle. He wants Roelle to continue submitting his body to a doctor who engages in secret human experimentations. Despite her boyfriend's threat, Roelle convinces her to keep the child. As a safeguard to her reputation, he proposes to fund her stay at a countryside house. When schoolmates learn that Roelle has been spreading rumors that he receives the visits of angels from heaven, they tease him and strike his head with stones. Roelle informs Olga he has obtained the money she needs for the abortion, but she refuses to accept it after finding out he stole it from his mother. Olga's sister, Clementine, in love with Roelle, complains that he always used to follow her but now only follows Olga. Amid a drunken rout of teenagers, Clementine and other schoolmates remove Roelle's clothes and throw him in a basin of water. Their cruel games are interrupted by Olga and her father. When Olga confesses her pregnancy, the father falls on the ground in a grieving stupor. Unable to find what to do, Olga attempts to drown herself in the Danube, but is saved by Roelle. To keep the high-school students off his back, he must pay protection money. Hearing rumors concerning he and Olga, the students surround and threaten them. He mitigates their anger by declaring that the unborn child's father is another. When they let Roelle and Olga go, he takes out a knife and asks her to stab him, but she refuses. Considering the fact that Olga has waylayed her son, Roelle's mother curses her, though she later denies having done so. When Roelle confesses to his mother he stole her money as protection against his fellow students, she moans and looks about for a priest to guide her. Roelle seeks similar guidance, but on reading a religious tract on confessions, in frustration he starts eating the paper.

=Carl Sternheim=

[[File:Carl Sternheim by Franz Grainer, c. 1921.jpg|thumb|Carl Sternheim was an astute critic of middle-class society. Photography of the author by Franz Grainer (1871-1949)]]

Still in the Expressionist vein but more domestically oriented, Carl Sternheim (1878-1942) wrote two notable dark comedies: &quot;Die Hose&quot; (The bloomers, 1911, also translated as The underpants, The panties) and &quot;Die Kassette&quot; (The strongbox, 1912).

In The Bloomers, the protagonist’s name “alludes to the bourgeois’ ability to hide his rampant egotism behind a mask of respectability” (Barnett, 2008a p 210). &quot;Theobald Maske...has been married to the beautiful Luise for one year, but because his civil service position provides them with only modest means, they cannot afford any children and therefore abstain from sex. Ironically, Luise's innocent sexuality gives Maske the opportunity to add to his income. During an imperial parade, the visible disarray of her underclothing affects two bystanders so much that they eagerly rent rooms from Maske, in order to court the embarrassed Luise. But Luise's frustrations give way to excitement; she sees in the boarders two potential lovers, and both Scarron and Mandelstam are soon competing for her affections. Luise welcomes the opportunity for freedom and adventure, but, alas, the passions of the potential lovers prove to be empty. The pseudo-Romantic Scarron prefers to write verse while Luise offers herself to him, and Mandelstam, the second potential lover-boarder, becomes totally preoccupied with his own hypochondria. Finally, however, there is a response to Luise's effort to achieve gratification, but it is the measured, controlled, and economically determined sexuality of Maske, which has successfully exploited the two boarders&quot; (Gittleman, 1976 p 27). “With his limited intellectual curiosity, his sole interest in petty comfort, his ostentatious non-understanding of man’s higher aspirations, the philistine Maske has seemed to most critics to be an object of bewilderment, satirical derision, and disgust...Sternheim’s comedies demonstrate the incongruity between the cherished ideals of the middle classes and the real but suppressed psychic drives of their individual members...Making the most of things...is the goal which entirely determines Maske’s actions...His assets as well as his security lie within his own four walls and in an appearance of utter mediocrity and normality...Theobald reduces ideas and cultural values to their lowest possible meaning. Nietzsche’s glorification of strength is a triviality for someone who used to bully his schoolmates; education is to be obtained through a visit to the zoo, its goal is to make one familiar with nature’s oddities...All that counts is its usefulness in daily life...He is thoroughly hedonistic and will never decline a pleasure if it can be had without further obligations” (Dedner, 1982 pp 30-40). “Mandelstam, as Theobald quickly realizes, has no marrow, and Scarron’s will is sapped. Instead of coming to sweep Louise off her feet as he has promised, he ends up drunk and incapable in the arms of a common prostitute. The ‘decisive turning point’ in Louise’s life is lost. Hence the only people who really get what they want are, first of all, Fräulein Deuter, who is endowed with a ‘tremendous lust for life’ despite her plain exterior, and Theobald, whom she has quickly identified as the true giant. The heroes are not the great thinkers, poets, painters and musicians. The heroes are the Theobalds who achieve complete freedom within their own sphere, a freedom which is lost if the world pays any attention to them. Their insignificance is the cloak under which they can indulge their inclinations, their innermost natures, unhindered. By the end of the play, all the spiritual forces are in disarray and life lived on the basis of reality is triumphant” (Ritchie, 1970 p 18).

In &quot;The strongbox&quot;, &quot;gradually, Krull's will is worn away by the attraction of the strongbox. He loses all interest in Fanny and transfers his sexual appetite to the money container itself...Elspeth cleverly allows him to take possession of the strongbox. As he carries it into bed with him, Heinrich speaks to the object of his economic greed the way he once spoke to the object of his sexual drive&quot; (Gittleman, 1976 p 28). “Krull is portrayed as an egotist whose sole purpose in life has become the quest for pleasure and enjoyment. The prospect of inheriting Elsbeth’s money keeps alive his hope of escape from the drudgery of a poorly paid teacher’s life. Egotism, nationalism, and mammonism are the striking features of this typical specimen of the Germam middle class. He is intelligent enough to realize that the international nature of high finance...conflicts with the nationalistic instincts…[Elsbeth’s] hopes and expectations with regard to Krull remain unfulfilled” (Eykman, 1986b pp 1740-1741). Garden (1964) appreciated the irony that Krull neglects wife and daughter for the strongbox when all the while it is bequeathed to the church. “The question as to the best use to be made of money is central to the play. For Elsbeth, the answer is obvious...the power...over other people...[For Krull, the thought of the box distracts him from his wife’s breasts]...Krull’s self-stylization as a medieval hero and despot and his perception of the box are entirely on the same level. The box can exert its influence on him only because it feeds the very fantasies after which Krull has fashioned his existence all along...Krull gradually realizes that...the bonds...remain abstractions...to the elements of an anarchic system...Krull exchanges the position of deluded victim for that of realistic master. His victim is Seidenschnur, whom he has accepted as son-in-law because he ‘smacks of romaticism’” (Dedner, 1982 pp 42-49). The heroes of Sternheim’s plays...are social climbers and power-mongering capitalist entrepreneurs of the most ruthless sort...Krull...hungers after nothing so much as capitalist shares” (Myers, 1973 p 411).

&quot;These two plays make a strong case for a tragic view of Sternheim's women. Their primary tyrants are men who are incapable of a genuine, sustained eroticism&quot; (Gittleman, 1976 p 29). “Sternheim’s work has much in common with that of the other dramatists of the time. For instance, the expressionist preference for presenting general types of humanity rather than individualized characters, in an endeavor to get back to what were felt to be the fundamental problems of existence, has a parallel in Sternheim’s cultivation of the extreme caricature of bourgeois types for the opposite purpose of revealing that there is nothing fundamental about them whatsoever. Similarly, the stylistic innovations of expressionism which depend on the omission of unessential words such as articles, pronouns and adjectives, and builds up in verbs and nouns into short explosive phrases, give to the conversation of Sternheim’s characters a hollowness and rigidity which reflects their lack of humanity. What Sternheim does not share with his contemporaries...is their preoccupation with their need to find a positive solution to the problems of the time” (Beckley, 1972). 

“Sternheim had introduced a new dramatic genre that was positioned between bourgeois comedy and satire...Sternheim’s bourgeois and parvenu characters were not designed to be likeable; their language, riddled with references and eclectic stylistic devices, had an alienating effect on middle-class audiences while at the same time uncomfortably mirroring their lifestyle and attitudes...The effect of Sternheim’s dramaturgy was that an audience laughing or even frowning at comical and narrow-minded middle-class characters…did not receive the satisfaction of having the just and proper world order restored at the end of the comedy” (Simke, 2024 pp 20-21). Sternheim’s plays “present a tension-ridden yet homogeneous world in the spirit of unrelenting objectivity, which is the most important property of the successful writer of comedies...Sternheim’s principal characters...are upstarts whose careers prove that society is an amorphous and completely malleable medium for the man who does not believe in the sanctity of its proclaimed forms and restrictions” (Nagel, 1972).

&quot;In a senescent culture, in a diseased and enfeebled world that has outlived itself and totters to its ruin (the conception is Carl Sternheim’s!), the satirist becomes a more decisive figure than the poet, the prophet, or the philosopher. A culture newly born has need of prophets to strengthen it with the illusions of flattering deceits. In its youth, it has need of poets to fill it with warlike vigor and the exaltation of high purposes. In its maturity, it needs philosophy to mitigate its headstrong pride and teach it calm and the acceptance of things as they are. But when a culture is old and worn out, the prophets cry vainly in the wilderness; the songs of the poets grow mawkish, and philosophy prates of emptiness and despair. Then- and only then, since a vigorous and confident world cannot bear to have its follies held up to ridicule the satirist becomes a figure of benevolent ruthlessness. By exhibiting, with tactful exaggeration, the symptoms of the world’s distress, he arouses, in the intelligent, an apprehension of peril. His work becomes, in this respect, purgative and useful. By displaying these tragic shortcomings in a ludicrous light, he teaches others to laugh on the brink of destruction&quot; (Drake, 1927 p 152).

==&quot;The bloomers&quot;==

[[File:Bloomers Rear Image.png|thumb|Trouble starts when Louise's bloomers fall in plain view on the pavement of a busy street]]

Time: 1900s. Place: Germany. 

Text at ?

Theobald beats his wife, Louise, with a stick then knocks her head against the kitchen table for accidently dropping her bloomers in public view. The dropped underclothes attracted the notice of a gentleman, Scarron, who professes himself enchanted by the sight and wishes to rent two rooms in the couple's apartment to be near her. Mrs Deuter, her neighbor, is thrilled by this new development, promising to fit her so that underneath she will be &quot;a white dream, with a few brightly colored bows in memory of this day&quot;. Theobald receives a visit from Mandelstam, a barber and another renter in their house. As Mandelstam secretly whispers to Louise's disgust, he professes to be another admirer of her bloomers. The couple agree on taking both. In view of Louise's negative reaction to his own person, Mandelstam threatens to expose Scarron. &quot;Why should that fop concern me?&quot; she retorts. Yet after Louise's friend, Mrs Deuter, shows her material she may use for new bloomers, she tells Scarron: &quot;I am yours.&quot; The two are interrupted by Mandelstam's arrival. With little provocation, she slaps his face, then notices a pointed thing showing from his pocket, a drill, with which he intends to pierce a hole in the wall to spy into Scarron's room. A disciple of Nietzsche, Scarron challenges Theobald by rhetorically demanding the following question: &quot;Should not the presence of a noble woman at your side inspire you to the greatest achievements?&quot; But, as a civil servant, Theobald has a different view. &quot;My freedom is lost if the world pays any particular attention to me,&quot; he says. A discussion on the effects of illness causes acute discomfort in Mandelstam's disposition, who ties a scarf around his neck and complains about the north-east position of his room, attracting ironic remarks from Louise when they speak apart. Did he not say he would remain with her whatever the consequences? Nevertheless, he negotiates his rent with her husband. Mrs Deuter arrives with the new bloomers and shows them to Theobald, at the sight of which he begins to court her. The two go off together in his room. Meanwhile, Scarron waxes enthused by his encounter with a whore on the previous evening. He pays Theobald a year's rent for the room but chooses to head toward the whore's apartment. &quot;Unheard of pleasures may await me,&quot; he suggests. He is replaced by a lodger of a more serious aspect as Theobald and Louise settle down quietly to married life again.

==&quot;The strongbox&quot;==

[[File:Rale strongbox.PNG|thumb|Trouble starts when Aunt Elspeth places a considerable sum of money inside her strongbox]]

Time: 1910s. Place: Germany. 

Text at ?

When Heinrich Krull, a schoolmaster, and his second wife, Fanny, return from their honeymoon, he learns from a female servant that in their absence a heavy strongbox was taken up by his wealthy and unmarried Aunt Elspeth and has since disappeared. Dissatisfied about the quality of photographs taken of her person, partly because of Fanny's criticisms, Aunt Elspeth asks Heinrich to inform the photographer, Alphonse, a tenant in their house, that she refuses to pay for them. When he hesitates, she insists on it and promptly adds: &quot;Rest assured, the report on what takes place determines the decision in regard to my last will and testament.&quot; Elspeth resents Fanny's presence in the house. Putting her ear on the bedroom door of husband and wife, she spits in disgust. Fanny unexpectedly comes out and, noticing Elspeth's position at the door, complains of her to Heinrich, who merely pretends to scold his aunt. He feels all the more his conflicting situation on being shown the strongbox, laden with state bonds and then reading her will in his favor. On seeing Alphonse distraught at the news of the rejected pictures, Lydia, Heinrich's daughter by his first wife, proposes to pay for them. &quot;Even if I were finally to get my fee,&quot; Alphonse asks rhetorically, &quot;how could I make up for the story of the rejected pictures around town?&quot; Lydia then proposes to have her own pictures taken by him. Alphonse accepts, but, in view of the risk involved in exciting the aunt's ire, specifies it must be done secretly. After taking the pictures, Alphonse and Heinrich agree, all the easier in that the former wishes to marry Lydia and enjoy part of the contents of the aunt's riches. But when Elspeth discovers that her nephew removed the pictures from her private drawer to give them to Alphonse, she is offended and wants them back. They exchange angry words. Heinrich feels obliged, despite Alphonse's reputation as a philanderer, to ask his wife to get them back for him. Pretending to be reconciled, Elspeth gives him the strongbox, but, unknown to everyone, changes the will in favor of the local pastor of the church. Late at night, Alphonse swears to Lydia he loves her but soon flirts with Fanny. He is caught in a compromising position by Heinrich and asks for his daughter's hand. Soon after their honeymoon, Lydia is miserable, certain that her husband is already cheating on her. Since Heinrich refuses to give Alphonse an allowance necessary for him to become a painter, he consoles himself by flirting with Fanny, who seems willing to pursue the matter.

=Ödön von Horváth=

[[File:Odon von Horvath cropped.jpg|thumb|Horváth wrote of social upheavals arising in the Austria of the 1930s. Photograph of the author, 1919]]

German Expressionism also includes the works of Hungarian dramatist, Ödön von Horváth (1901–1938), notably for &quot;Geschichten aus dem Wiener wald&quot; (Tales of the Vienna woods, 1931) and &quot;Kasimir und Karoline&quot; (Casimir and Caroline, 1932).

In Tales of the Vienna Woods, &quot;Vienna...is a metaphor in Horváth's play for a moribund society. The inhabitants of the 'quiet street in the eighth district' are as bankrupt morally as they are financially. They cling to a flattering image of themselves that bears little correspondence to reality, meanwhile taking out their frustrations on Jews, foreigners, and anyone in their midst who cannot defend himself&quot; (Winston, 1978 p 170). Horváth's &quot;popularity today among intelligent, discriminating theatergoers is partially explainable by the pervasiveness of kitsch in his plays...omnipresent [in] consumer society, where it has taken on new well as cultural and philosophical overtones. Kitsch is reactionary beccause it is always imitative. It thrives in eclectic eras. Although intended by its creator to seem authentic, it strikes one as being false, insipidly sentimental, and superficial...Marianne and the other characters move in an artificially perpetuated fairy tale...More often than not [Horváth] employs music for ironic effect, to reinforce the artificiality of a situation or the dissonance between characters. An amusing example of the first use is found in the scene at the engagement picnic. Oskar, the unloved fiancé, sings a romantic ballad...while his betrothed is preparing to run off with a complete stranger...The Latin, French, Italian, and English expressions, liberally sprinkled throughout the speeches of various characters, are designed by them to impress others with their superior education and savoir faire...The characters in their language display a fondness for citing authoritative sources...[an] illusion...Horváth portrays his characters in the process of debasing all the meaningful aspects of life by sentimentalizing the moment and nursing obsolete values...Horváth's satire on the insipid chauvinism of the Viennese Kleinbürger is presented as graphically at Maxim's where some titillating &quot;porno-kitsch&quot; is introduced. He records here the commercial exploitation by the entertainment industry of mythopoetic techniques which permit sexually repressed individuals to enjoy pornography by giving it a supposedly 'artistic' or 'cultural' content...Closely linked with the cult of Heimatliebe is another favourite source of kitsch: religion...Oskar is the prime example of the religious hypocrite. The pious platitudes that he continually utters have no foundation in reality. When he discovers that Alfred has deserted Marianne, he hesitates to take her back as long as little Leopold is still alive. He veils his desire for the baby's death in religious bromides...Another character in the last scene who exploits bereavement for his own advantage is Alfred. His immediate response to the news of his child's death is to throw his arms around Valerie, Marianne's successor. He ignores Marianne completely...It should be apparent that Horváth believes that dependence on socially prescribed or acceptable postures, directed at achieving an effect rather than at conveying a conviction, leads to the transformation of all genuine emotional responses into artificial ones&quot; (Genno, 1972 pp 311-321). “The veneer of respectability concealing the predatory nature of business relations is well-nigh transparent in ‘Tales of the Vienna woods’...Drained by the exigencies of social hypocrisy, [Marianne] finally agrees to fulfill her father’s wishes and marry Oskar. Her last defiant gesture before she allows to be sacrificed on the altar of respectability and the convenience of others...is...meaningless..as Leopold, her child, is dead” (Best, 1980 pp 119-121). &quot;Whereas the other participants are instructed to imitate animal noises, Oskar, who has been ordered to provide a demonstration of some sort, responds by escalating the general indulgence in animalistic debasement...It is significant that none of the guests come to Marianne's defense, clearly indicating that the group's allegiance lies with Oskar...Oskar's brutality in relation to Marianne in the martial arts scene constitutes a repetition of his previous behavior towards her. On the other hand, it points to her future subjugation and reintegration into the fold. In the present, however, it precipitates her act of liberation which, given the military dimensions of the drama, may be characterized as a sortie in which she forms an alternative alliance with Alfred...The extent of Marianne's physical and spiritual oppression is indicated by the fact that she bears the sole responsibility for managing her father's household as well as the toy store...The fact that Oskar will emerge as the victor is not so much a consequence of any character flaw on Marianne's part as it is a consequence of the fact that Oskar's threat articulates a collective imperative on the part of lower middle class to stabilize their precarious financial situation and to maintain the status quo at all costs. Indeed, the fact that all of the neighborhood reside are present in the climactic cabaret scene- while Oskar remains conspicuously absent- concretely illustrates the extent to which Marianne's surrender is not simply an individual imperative but a collective one&quot; (Brzović and Decker, 1990 pp 395-398). “In the nightclub episode, Horváth gives another example of the pretentiousness with which society often tries to mask its baser motives and desires. Although the show is a crass exploitation of female nudity, the nightclub announcer introduces it with ceremonious allusions to Johann von Goethe…The portrait of Austrian lower middle-classes that Horváth gives in Tales of the Vienna Woods is one of viciousness, greed, and pettiness masked by stupidity, pretentiousness, and sentimentality” (Barry, 1986 p 960).

In Casimir and Caroline, &quot;love appears like a reaction that comes and goes, in the fairgrounds among the freaks, love and life 'turn out to be numbers on a wheel of fortune'...The love of Casimir and Caroline is destroyed by the emptiness in which they live and from which they cannot escape. The unhappy part of it is that these people do not recognize this void, because their thought processes are, as it were, too primitive and underdeveloped to enable them to form a picture&quot; (Loram, 1967 p 26). &quot;Remarks are often followed by awkward pauses, which mark the emptiness in which the speakers are enveloped&quot; (Weisstein, 1960 p 347). “Caroline...has not learnt from her suffering. Casimir, for his part, finds consolation with Erna, a former servant-girl. They too have no illusions about their bleak future that awaits them beyond the fairground, and in the penultimate scene of the play...Casimir and Erna can only declare their feeling for each other through proverbs” (Best, 1980 p 123). Both end up “with partners to whom they are indifferent, and their emotional emptiness reveals the superficiality of the traditional market-place celebration” (Innes, 1979 p 220).

“The German-speaking world will at long last come to know an author who has few equals among 20th century playwrights and who combines in some of his finest creations the tradition handed down from Strindberg and Wedekind with that represented by Nestroy and Molnar. Horváth’s proper task was the unmasking of the subconscious through merciless exposition of the dialectic of intention and execution, thought and action, chance and fate, the tragic and the comic. Many of Horváth’s characters are led by the circumstances…to do what they had no intention of doing or to say something that does not in the least express the character. Their predicament arises from the fact that they must be evil or that, if they are good, they are so out of sheer stupidity” (Weisstein, 1972). Horváth “was never really under the spell of expressionism because he is too realistic, too satirical, too saucy...His plays are frequently cabaret-like, sometimes almost farcical, a combination of seriousness and lightheartedness, even his use of language is disconcerting...The clichés that so many of the characters indulge in are not a sign of weakness on the playwright’s part but are intended to convey the emptiness and lack of substance which these people assume to be a way of life. Like most moralists, he provokes and annoys” (Loram, 1972). “Horváth deals with his characters in terms of their mental world and aims at his audience’s subjective awareness, their complicity through shared attitudes and idealistic self-deceptions, their recognition of the reflection of their own dehumanizing turns of phrase” (Innes, 1979 pp 221-222).

==&quot;Tales of the Vienna woods&quot;==

[[File:Peilstein 20160507 01.JPG|thumb|The Vienna Woods are the site where Marianne throws her engagement ring on her betrothed's face]]

Text at ?

Alfred tells his mother that he renounces the option of steady ordinary work, because in his view &quot;work is no longer profitable&quot;. Instead, he wants to make a living at placing bets on horse-races on behalf of Valerie, a fifty-year-old owner of a tobacco-shop. During an excursion in the Vienna woods, Alfred meets Marianne, who works in her father's toy-shop and confesses without knowing why to an almost complete stranger that she does not love her betrothed, a man named Oscar, owner of a butcher's shop, whose point of view is that &quot;tradition is the only thing that matters&quot;. When Oscar senses her lack of enthusiasm for their relation, he brutally tries out a jiu-jitsu move on her before a company of friends. Farther off in the woods, Valerie, after quarreling with Alfred, flirts with Roimage, Marianne's father. Reflecting on her advancing age, she comments: &quot;What does a man know of woman's tragedy?&quot; She timidly asks whether she can be permitted to place her head on his knees. &quot;Nature knows no sin,&quot; Roimage reponds. Their conversation is interrupted by his nephew, Eric. When Roimage leaves, she flirts with him. Beside the banks of the blue Danube, Alfred encounters Marianne a second time. They kiss. &quot;You fell on me like thunder, splitting me,&quot; she declares. They are surprised in a compromising position by her father in front of the rest of the company. In defiance, she throws her engagement ring on Oscar's face and flees with Alfred, which leaves Oscar depressed for an entire year. During that course of time, Alfred eventually becomes bored with her. He arranges for Marianne to accept a position at a ballet company in the hope of eventually ridding himself of her. His grandmother, who raises Alfred and Marianne's baby, proposes that if he succeeds in ridding himself of her, she will lend him even more money than she has already, despite his having failed to pay back the previous sum. Meanwhile, an old-world major, a customer at the butcher's shop, quarrels with Eric. The major suggests that they spend an evening at Maxim's nightclub, having seen Marianne work there. After consuming a large portion of salami, Eric leaves the nightclub in ill humor with everyone, while Valerie flirts with a gentleman from America, a childhood friend of the major's brother. Valerie is shocked to find Marianne perched half-naked on top of a golden ball, and disturbs the show, at which the irritated gentleman from America punches her on the breast. Marianne pleads with her father to leave the place, but he refuses to hear. She is arrested for clumsily trying to rob the gentleman from America. Alfred returns to his grandmother's house after having wasted her money at the races. Marianne gets out of jail on bail money and then accuses the grandmother of deliberately pushing her baby's landau in a draft after opening two windows to make him catch cold. Marianne eventually receives a suspended sentence and, out of funds, is forced to ask Valerie for food. Since Roimage is unable to continue in his business affairs without his daughter's help, Valerie attempts a reconciliation between them and succeeds. Marianne also becomes reconciled with Alfred as do Valerie with Oscar. When Marianne returns at the grandmother's house, she discovers that the landau has disappeared, a sign that her baby is dead. The neighbors suspect that the baby's death was caused by the grandmother's negligence. In frustration, Marianne tries to hit her grandmother with her zither. In retaliation, the grandmother hits her on the face. Crying, Marianne swears revenge. Now that her baby is dead, Oscar wishes to take her back. And the blue Danube continues to flow...

==&quot;Casimir and Caroline&quot;==

[[File:Open- Air vor dem Theater mit der Produktion &quot;Kasimir und Karoline&quot;, 2013.jpg|thumb|Casimir and Caroline are unable to be reconciled in an amusement park of an open air production of the play in 2012]]

Time: 1930s. Place: Munich region, Germany.

Text at ?

Casimir and Caroline quarrel during a Beerfest. He is particularly touchy, because having recently lost his job, the case of many during the economic crisis, he expects Caroline to leave him. Walking out, he sees a zeppelin in the sky. &quot;When we see that, we think we are also flying,&quot; he comments, &quot;but our lot is shoes with holes in them and a table border to break our jaw on.&quot; Casimir's friend, Franz, tries to cheer him up, but without success. When Caroline meets a man named Schürzinger, they amuse themselves in amusement-park rides. Among other customers, there is Rauch, head of a company, along with his friend, Speer, who peek at the underclothes of women sliding down toboggans. Afterwards, they join Caroline and Schürzinger. By chance, Casimir encounters Caroline in the company of these three strangers. When asked what is she doing, she replies that she hopes to reach a higher social level. In a freak-show, the public is entertained by a man with a bulldog face who cannot open his mouth and a gorilla-woman &quot;with all internal parts like those of an animal&quot;. Schürzinger warns Caroline about Rauch and Speer, who seem like disreputable fellows, but she ignores him. Sensing trouble, Schürzinger leaves her with them. Meanwhile, Franz suggests to Casimir that they should embark on some illegal activities to supplement their meager income, but he refuses. Caroline continues to amuse herself in the company of Rauch and Speer. She accepts Rauch's proposal to leave the park in his car after he quarrels with Speer, who accosts two women for the purpose of engaging in sexual favors. Rauch suffers an epileptic seizure in the car, so that Caroline takes him to an infirmary. Despite her kind gesture, he rejects her after being treated. Back in the park, a huge melee ensues after two young persons object to Speer taking the two women along with him, in the midst of which he suffers a fractured jaw. Franz is arrested. Casimir ends the evening with Franz' girlfriend, Jenny, though they do not have much to say to each other.

=Gyula Háy=

[[File:Julius Hay.png|thumb|Gyula Háy approached the problem of conflicts between social classes]]

A second German-writing Hungarian dramatist rose to the fore in the same period, Gyula Háy (1900-1975), notably for &quot;Haben&quot; (To have, 1935) and &quot;Der Putenhirt&quot; (The turkey caretaker, 1938).

==&quot;To have&quot;==

[[File:Talcum Powder.JPEG|thumb|Suspicions arise when David's medication appears in the form of white powder instead of the usual yellow]]

Time: 1930s. Place: A village in Hungary. 

Text at ?

Because of financial troubles, Mrs Arva has sent her daughter, Mari, to work at a lawyer’s house outside of town at Szolnok. Mari’s lover, Dani Ballo, corporal in the military police, and an adjutant are invited by the local curate to taste his brandy and smoke his tobacco at the presbytery. Although he warrant officer is on the look-out for unlicensed tobacco, the very thing the curate is serving him, he prefers to look the other way and enjoy it, but without permitting his inferior in rank, Dani, to join them. He asks the curate to warn Widow Biro about receiving a fine if she neglects to bury her corn stems, breeding site of flies liable to devastate the town’s crops. Mari announces to Dani that her boss has fired her in favor of a family member, so that the couple’s prospects to marry look dim unless Dani distinguishes himself in some important inquiry. Dani is incensed when she also reveals that Mrs Kepes, a midwife, came over to their house to discuss the possibility of her marriage with the richest proprietor in the village, though sickly, David surnamed The Neighbor.  When the curate goes over to Mrs Biro’s house to warn her of an inspection, she flies off the handle and threatens to hang herself rather than submit to that indignity. Pregnant Mari agrees to David’s marriage offer only if the man is certain to die soon, so that she and her mother head toward Mrs Kepes’ house, where they obtain three packets of poison in exchange for a wrist-chain and a picture. Mother and daughter sit petrified as Mrs Kepes initiates dance-like steps and pirouettes in apparent jubilation over their project.  Worrying over his health, David requests his daughter, Zsofi, who suffers from tuberculosis, to read a chapter from a medical book, but her descriptions of vascular diseases disturb him so much that he grabs her in a threatening way. Back at the presbytery, the adjutant tells the curate that despite his recommendation to get drunk and console himself with prostitutes during the wedding festivities, Dani refused. “There is a prayer, Mr Adjutant, that I must say from time to time thus: ‘Keep me, Lord, from reading the Scriptures otherwise than how I first learned them’,” the curate says. “And there is another one to say in a lower voice: ‘Keep me, Lord, from reading the Scriptures as they were written’.” Dani shows up at the newlyweds’ house the next day and notices a trace of spilled white powdered medication on the kitchen table. Mari chuckles scoffingly at discovering Zsofi looking in a mirror with her wedding dress placed in front, which enrages Zsofi.  But Mari is abashed at seeing field-hands carry in her dead husband. While Mari and her mother feign surprise, the suspicious Dani, keen on inquiring on his own behalf, asks the adjutant whether he considers David’s death an accident. He does, to focuse instead on a letter with 120 signatures addressed to the governor from the townspeople, requesting help from dire economic straits, rendered even worse since Mari took over management of her house. To the adjutant, Dani specifies that by her father’s death, Zsofi gains 90 acres of land, but only 45 should Mari be delivered and that certain widows appear to know more than what they say. He also reveals his suspicions about Zsofi to Mari, worrying that Zsofi will cause trouble should someone whisper that Mari’s child is not her husband’s. Mari points out that four widows in the village have secret lovers. “They all know what they are doing. They do what is done in the village,” she specifies. “And we can do the same.” But Dani thinks that strategy is too risky. Meanwhile, Zsofi heads towards the Kepes house to ask the woman how to become a midwife and for some white powder she has heard about. The surprised midwife tries to discourage any such endeavor as Mari and five other widows voice their anxieties about Dani’s inquiry and are even more fearful when Zsofi demands the poison in view that Mari still holds two more packets. A trembling Kepes hands it over. As Zsofi leaves, Dani enters wondering about the nature of a meeting of six widows. “Mrs Kepes is going to Zsolnok and we are ordering. Sir Corporal desires certain bagatelles, too? Ribbons? Press buttons? Knitting needles? Thread?” The widows laugh nervously. Three days later, Zsofi accuses Mari of “having a policeman in her petticoat”. She denies it and they scuffle until Zsofi leaves the room coughing. When next they meet, Mari learns of Dani that should a woman be hanged, her property is still inherited by her child. Unheeding the peculiarity of her question, Dani tells Mari of another discovery of his: David’s medication, according to his doctor, was in the form of a yellow powder, not white. After Zsofi is found dead from poison, the representative of the townspeople requests the curate to sign their letter of protest, but he dares not. In a surprise visit, Mari enters to say that the world is as it is and no one can do anything about it. She reaches out to tear up the petition, but Vago prevents her. Dani enters distraught, his chance of a reward for inquiring on the Zsofi case finished. “You don’t know what I have done for our child, for our son,” Mari declares and then shows the men the two packets of poison.

==&quot;The turkey caretaker&quot;==

[[File:Our domestic birds; (1913) (14768542243).jpg|thumb|Trouble starts when Andor forces Imre to eat food meant for turkeys]]

Time: 1929. Place: Hungary. 

Text at ?

Janos, bastard son of the rich owner, Andor Thury, wishes to marry a servant, Lidi, who prefers a fellow servant, Joszi. She especially resents Janos for filling the buttocks of her brother Imre, turkey caretaker, with lead shot after the lad fell asleep and turkeys overran the house with filth. Since his wife, Amalia, loves the turkeys, Andor proposes that Janos harm them and put the blame on Imre. A mechanic on the premises, Petras, advises Joszi and Lidi that they should complain of Janos in a court of law. Meanwhile, two investors, Makay-Mezer and Steiner, attempt to convince Janos to be on their side when offering to buy wheat from Andor’s estate. He answers that the curate, Ladanyi, offered to help him marry Lidi should the priest convince his father to sell half the wheat harvest to the bishop. Makay-Mezer counters that he is able to improve Janos’ legal claim relative to the legitimate heir, Otto, if he sides with them against the bishop. For his part, Otto tells his mother that he feels useless about the place. Their talk is interrupted by Huba, an employee at the palace of justice, whom Amalia wishes to consult for accusing Janos in the matter of the turkeys.  She obtains a certificate written by a poor medical student, Rita, in regard to Imre’s condition. To Rita, Otto repeats his dissatisfaction, wishing to escape altogether with her. Worried over Otto’s apparent disinterest in women and hoping for a marriage with one of the three daughters of a rich owner, Veresaghy, Amalia proposes to pay Rita should she sleep with him. A crisis occurs when Amalia is told that the turkeys refuse to eat, finally resolved when the veterinarian, Terepely, Rita’s uncle, suggests that Imre chew the egg and milk mash in front of the turkeys in imitation of what they must do. While Imre continues his care for them, Janos releases a weasel in their midst which sets off a panic and ravages all about. Meanwhile, an angry Joszi wants to strike Janos and then escape with Lidi, but Petras advises them to stay put in view that the police would easily discover the culprit and send him to prison. Pressured by the bishop, Ladanyi pleads with Janos and Amalia to sell and warns him that his superior has engaged Veresaghy’s help, who has influence at the bank where Andor accepted a bank draft he may be unable to pay. For their part, Makay-Mezer and Steiner make a firm offer for the harvest, but Andor declines since the price has recently been rising. To settle the matter of the turkeys, Andor orders Imre to show him how he fed them. Imre chews the mash. His employer suggests that the lad swallowed some of it for his own benefit. Imre denies it. Andor is convinced that no one would fail to cheat in such a situation and orders him to swallow the mash. The boy reluctantly obeys and then is encouraged to swallow a mixture of eleven eggs. Angry at a revolutionary story the boy is telling as he eats, Andor forces a packet of flies inside his mouth and violently pushes him away. The fragile undernourished boy falls, convulses, and lies inert. Rita fears the worst; Terepely confirms that the lad is dead.  Makay-Mezer, Steiner, and Huba hurry away.  A day and a half later, Makay-Mezer and Steiner return for another offer, but this time for only 60% of the previous price as the result of the stock market crash. Moreover, the bishop no longer wants to buy but rather wants to sell it. Amalia suggests that now is the time that Otto formulate an offer of marriage to one of Veresaghy’s daughters. But that plan is stymied when Otto appears with Rita ready to leave as man and wife. To complete Andor’s day of misfortune, another investor shows up not to buy wheat, but to buy strawflower, a flowering plant handy for funeral wreaths. He rejects the offer. After conferring together, Makay-Mezer and Steiner return one more time to suggest one last hope of selling the wheat, perhaps at the former price, if Andor is able to prepare his merchandise for shipment at the train station within two days. However, his field hands become unavailable due to Imre’s funeral. Janos proposes to enlist Joszi’s help by desisting to marry Lidi, who would bury her brother alone without the necessary field hands, provided he is recognized as the rightful heir of the estate. Amalia refuses to disinherit Otto, but Andor accepts Janos’ proposal. However, when Janos shows up in the midst of the field hands to plead for a delay in the funeral arrangements, they beat him up.

=Reinhard Sorge=

[[File:RJSorge1.jpg|thumb|Reinhard Sorge showed how a poet turns into a beggar, 1915]]

&quot;Der bettler&quot; (The beggar, 1912) by Reinhard Sorge (1892-1916) is one of the first examples of expressionist theatre (Lewis, 1971 p 449). 

“In The Beggar, Sorge found the lyrical-ecstatic style of expressionist drama: brief tableaux, harsh lightning, intensely emotional language, an unreal, symbolic plot, types instead of psychologically differentiated characters. For Sorge, the stage was again a healing-place, a revelation of the meaning of man’s deepest spiritual being, a world of mystical signs. The beggar liberates himself for all eternity, renouncing family, work, and world” (Martini, 1972). “The beggar” “is an extremely significant beginning for the [Expressionist] movement because it is not only the epitome of self-centered drama but also a plea for a new kind of theater. Sorge is himself the hero of his own drama, the plot of which concerns the poet’s efforts to find a theater willing to produce his play...for all humanity instead of a ‘little heap of intellectuals’” (Wellwarth, 1986 p 27). “There are unmistakable echoes of Faust I...[The] emerging earnestness in the face of life, this search for direction and for the nature and aim of existence...were to culminate in Der Bettler” (Thomas, 1937 pp 423-424).

One of the main themes of expressionist drama is the father-son conflict, particularly prominent in &quot;The beggar&quot; (Garten, 1964 p 116). The play reflects &quot;the malaise of alienation brought on by industrialization, urbanization, militarization...The most conspiciuous testimony of the play's oppositional character is Sorge's subject: the poet who resists and is ultimately crushed through his absolute alienation in the age of the culture industry. The young, ambitious playwright stubbornly refuses to allow his art to be commodified. Desiring nothing more than to have his plays produced in the public sphere, not merely because they were his own works, but because they would serve to fulfill his dramatic mission, which was to break the control of the theater establishment, he vehemently insists that a theater be placed at his disposal in order that he may be able personally to see his work brought to its unadulterated fruition&quot; (Shearier, 1988 pp 228-231).

The father’s “megalomaniacal messianic dream functions as a counterpoint to the son’s search for meaning and salvation. In contrast to the son’s idealism, the father represents the materialistic counterpoint in the composition. He misinterprets the messianic materialistically as technical progress and enrichment” (Sokel, 1972).

“The most conspicuous testimony of the play’s oppositional character is Sorge’s subject: the poet who resists and is ultimately crushed through his absolute alienation in the age of the culture industry. The young, ambitious playwright stubbornly refuses to allow his art to be commodified. Desiring nothing more than to have his plays produced in the public sphere—not merely because they are his own works, but because they would serve to fulfill his dramatic mission, which was to break the control of the theater establishment— he vehemently insists that a theater be placed at his disposal in order that he may be able personally to see his work brought to unadulterated fruition.
His insistence on autonomy, however, only exacerbates the alienation to which the poet is subjected by mass culture, and his intransigence in his position with regard to the oppositional character of drama leads ineluctably to his ruin. In this sense, the play functions as a direct affront to the culture industry, which refuses to tolerate the oppositional voice. Establishment theater, buttressed by affirmative art that serves the need for legitimization of the existing power structure, is the focus of Sorge’s critical assault. The Beggar, the maverick artist, is the personification of absolute alienation, as he is thoroughly estranged from his environment, from himself, and finally from life itself” (Knopf, 2015 p 185). 

==&quot;The beggar&quot;==

[[File:Beggar MET ES6434.jpg|thumb|When a father disapproves of his son, the son may rapidly turn into a beggar. Figure from the Nymphenburg Porcelain Manufactory, 1982]]

Time: 1910s. Place: Germany. 

Text at ?

A poet encounters difficulties in having his plays accepted in the theatre. A friend advises him to ask his patron for a lump sum in living expenses, which will permit him to write in tranquillity. Instead, the poet boldly requests his own theatre. The patron refuses. &quot;You have killed your last opportunity,&quot; his friend cries out. The conversations between the two are overheard by a girl interested in meeting the poet. She leaves the attending nurse in charge of taking care of her illigimate baby to accost him. &quot;I must speak to you, wondrous stranger,&quot; she starts by saying. Since first meeting this girl, the poet gradually becomes more secretive towards his mother. He deplores the fact that his father's sister has forced his mother to nurse his demented father at home instead of an institution. During the night, the father beats a drum. Having dreamt of canal-building on Mars, he considers himself on the road to recovery with detailed blueprints in hand. &quot;And my brain was like a gigantic spider,&quot; he enthuses, &quot;embracing Mars and inserting his proboscis into it, a sharp pointed sting, and sucking out all its secrets, all.&quot; His life-work done and the earth about to be fertilized, he requests poison from his son. The girl succeeds in obtaining a position, but, with her meager salary and following her uncle's advice, she feels obliged to give up the baby to adoption. The poet thinks this move may be a mistake, but she argues that without that tie she is now free to love him exclusively. &quot;I fear your matricide,&quot; the poet counters, who thinks she should love both of them. &quot;Fear is past and gone,&quot; she retorts. In despair over his own condition, the father throws the blueprints in a fire and burns his head. After recovering, he nails the blueprints on the trunk of a beech tree and requests red ink to cover them, but he cannot obtain ink because the stores are closed on Sunday. He notices a fledgling bird on the ground after falling from the nest and pierces its body with a compass to use its blood as the ink he needs. Distressed at his father's condition, the poet pours poison into his wine and leaves. The father drinks half the glass. By mistake the mother also picks it up. When the poet returns, he is confused at seeing broken glass at her feet. The father covers the blueprints with bird-blood while the mother lies contented as both lay dying. &quot;For a long time, I have been wishing myself into the grave,&quot; she wearily confesses. To make ends meet, the poet accepts a position at a newspaper but soon quits. He at last accepts that the girl abandon her previous child when she is pregnant with his.

=Georg Kaiser=

[[File:Georg Kaiser.jpg|thumb|Georg Kaiser showed how one moment's impulse inside a bank can ruin a man's life, 1921]]

Another important figure of German Expressionism includes Georg Kaiser (1878–1945), whose major work is &quot;Von morgens bis mitternachts&quot; (From morn to midnight, 1916).

From Morn to Midnight “is a good example of Expressionism. It is only a series of flashlights cast into the soul of a man who, shaken out of his routine by sudden temptation, for one day tests life in its most varied aspects by the touchstone of money and finds it not worth living. In the morning, the trusted employee of a great bank, the respected father of a bourgeois family- then, lover, thief, libertine, patron, philosopher, and lastly suicide, all in the brief space of one day. Here no place for delineation of character, for development of plot. The characters are types, not individuals; the motives and emotions indicated, not led up to and explained; yet the whole is expressive, stimulating to thought and feeling, a glimpse of something real, of an aspect of life that most have at some time felt or divined” (Whitney, 1923 p 277). The play reflects “a dramaturgical structure typical of many Expressionist dramas, a mode of presentation that shows the protagonist in a sequence of selected stages or exemplary situations in his life...A scene or an act of the play no longer follows logically or psychologically from the preceding one. Instead, their nexus is based on an underlying idea common to all the scenes, which thus become variations of a theme” (Eykman, 1986a pp 1020-1021).

In From Morn to Midnight, Kaiser &quot;contrives the most savage satire in recent literature upon the money-lust of the modern world and the fallacy of its reduction of all values to a common denominator of gold&quot; (Drake, 1927 p 92). “Symmetry is a major element in the structure of [the play]. The formal austerity of the bank in the first scene is balanced by the noisy vitality of the Salvation Army hall at the end to a voluble confession. Similarly, the celebration of naïve eroticism in the painting by Cranach and the lady’s modest rejection of the cashier’s advances contrast with the commercial sexuality of the night club scene” (Patterson, 1981 p 64). &quot;The one quality unfamiliar to Broadway which it possesses is a savage, biting humor, cynical perhaps but lighted by horrible flashes of truth. Its savagery seemed at times to bewilder the audience. They did not know just how to take it. They kept hoping for the apotheosis of Pollyanna in the last scene, but the author was implacably humorous to the end...No narrative can give any idea of the remorseless, grim humor of this tragedy. But the allegory at least should be clear of a man's vain search to realize his ideals, to find himself only to encounter the hopeless, mysterious darkness at the end&quot; (Crawford, 1922 p 342).

“The unnamed cashier becomes aware suddenly of the dehumanized life around him. He rises from the grave of bourgeois conformity and stagnation to a new life of freedom...Although the cashier searches for meaning and value in life, he fails to undergo a spiritual transformation...The cashier appears as a modern Everyman whose flawed yet nonetheless heroic search for life’s meaning acquires universal, mythical significance...The cashier is guilty because he misuses the opportunity to discover his true identity to gain power over others and to demonstrate his sexual potency, thus enhancing his self-esteem. His crime of theft is a means to this end...The impulse for the cashier’s sudden transformation from respectable bourgeois to criminal is the sexual desire aroused in him by an exotic Italian lady. Like this first encounter with Eros, all his subsequent efforts to satisfy his sexual appetite lead to disappointment...In the first type of reading, the cashier is a new nan, a tragic rebel, even a martyr. The second approach yields an ironic view of the protagonist: he is a sexually frustrated, power-hungry bourgeois who fails to understand the world in which he functions” (Willeke, 1995 pp 81-86). Critics exaggerate in describing the cashier’s working conditions, the “suffocatingly repressive, life atmosphere of the bank with its mechanical obscenity”, a tendency which serves to mitigate the crime of grand larceny. Yet “Kaiser demonstrates with powerful theatrical effect that deeds performed in the name of togetherness, happiness, Eros, the life principle, and humanity in fact issue in chaos and death” (Chick, 1984 pp 87-88). Other critics have a more negative view of the cashier. “The more the cashier attempts to progress towards meaning and enlightenment the more he gets lost in the dark. He appears to be sexually deprived in the sense of meaningful physical intimacy, otherwise his accidental contact with the beautiful lady would not have triggered grand larceny. He seeks some definition of reality in a home which can provide warmth, succor, and refuge. He finds it in a prison instead of a retreat from the rigors of life. He looks for stimulation in athletic contests, in and of themselves, a healthy and important part of one’s social life, and instead ends up corrupting the event and focusing on the sexual aspects of crowd behavior. He searches for sex in a bordello, hardly a place for meaningful interpersonal relationships” (Elwood, 2004 p 84).

“When an exotic Florentine Lady approaches his counter and accidentally touches the Cashier’s hand, he becomes newly conscious and his senses become engaged. The Cashier steals 60,000 marks from the bank, flees, and embarks on a journey, an Expressionist variation on Everyman’s pilgrimage...The Cashier first highlights his representative function when he visits the Lady in her hotel room; he sees the medieval painting she wishes to buy for her son and recognizes himself in the figure of Adam…In his identification with the first man and comparison of the Lady with Eve, the Cashier makes explicit their participation in a temptation and fall narrative. Death appears to the Cashier in the field, a kind of summoning of Everyman, a call to reckoning; like Everyman, the Cashier requests just a bit more time to find something or someone to bring him to redemption… It would have been better perhaps if, like Elckerlijc/Everyman/Jedermann, the Cashier had earlier mobilized his Good Deeds instead of placing his trust in his Goods. What might constitute Expressionist Good Deeds in the play, however, is a challenging question…The Cashier as Everyman would need to join in community with like-minded individuals; he cannot act alone” (Groeneveld, 2019 pp 91-94).

&quot;After embezzling, the woman proves to be respectable, and so “the clerk is disappointed in his first attempt to experience a life he had never known: that of the senses...He sets out in quest of a multitude of lost opportunities and of the soul that had been stunted by a soulless society...On the first stage of his new life...the clerk returns home, but now he sees [the family] through new eyes; his slavery to work has been slavery to them...The runaway clerk tries to satisfy vicariously the passion pent up by offering huge sums as stakes in the 6-day bicycle races...but again the clerk is cheated in the fulfillment of his wish...and further disillusioned in the sensuous pleasures that can be had for money...In a Salvation Army hall...each sin forms a part of the clerk’s own guilt...a practice often used by Expressionist dramatists to give concrete form to the complex inner life of the characters...Over this final disillusionment...the mad circle in which he has rushed from morn to midnight closes” (Kenworthy, 1957 pp 25-29).

“The separate confessions of the penitents, leading up to the clerk's own public repentance; his scattering of the money and the consequent scramble, are conceived in a search for a rhythmic plasticity that serves the author's revelation of human nature. It is the culminating scene of the play and the most expertly managed. It is compact; it does not, like the opening scenes, wander; it produces an emotional effect independent, not of the words, but of their individual meanings. This is the exaltation after which the expressionists strive and to which occasionally they attain” (Goldberg, 1922 p 308).

“The play is a metaphysical musing on the moral values of life in a society drained of spirituality, forever in the shadow of its own collapse. It also pioneers the form known as the station drama, echoing the stations of the cross” (Barnett, 2008a p 207). “The cashier, who has become a silent and perfectly functioning machine in his many years of service, takes [the woman to be one] of easy virtue and is suddenly sexually aroused...She pleads with him to return to work, but he has destroyed his past and continues on his reckless course...In the next expressionist scene, the cashier is in a snowfield covering his tracks. Suddenly the sun is hidden and a storm sweeps across the field. The snow forms a skeleton which beckons him to follow. But he is not ready to come along...He wants to purchase a new lease on life...He is on his way...His first visit is to his family...They do not comprehend the changes he has undergone. Their lives revolve around their daily meals, needlework, and the playing of music by Wagner...So habit ridden is the mother that the shock of hearing her son leave before lunch kills her...In an arena watching a 6-day bicycle race...he offers a prize...not interested in the sport itself but only in the ecstatic reactions of the audience...The crown prince enters, the national anthem is played, everybody stands at attention, tradition proves stronger than passion...The third station is a cabaret where the cashier has his first taste of the high life...He tries to win the most beautiful girls [but is deceived]. In the Salvation Army hall...the cashier realizes that their sins are his own...He...denounces himself...throws the bills in the hall...but the girl...betrays him...for the reward...He shoots himself [after having failed to reach] a full life...He remains imprisoned by his past...From Morn to Midnight is a prime example of the Expressionist play of [failed regeneration]...The characters of the play are not fully developed personalities but abstract types or figures. They stand for all people engaged in the same function or profession or in a similar relationship...Designated as Director, Mother, Son, or Policeman, they are not antagonists of the cashier and no dramatic struggle develops. They either function as examples of a life which the cashier rejects, or they serve as his foils. In contrast to the factual language of most of the figures, the cashier uses metaphors and imagery in his monologues. His speech is highly symbolic” (Schürer, 1971 pp 83-86).

Kaiser &quot;was certainly a gifted dramatist: he was steeped in the routine of the theatre, and did not stand above sensational effects, but he had the daring of the pioneer and a skill in the symmetrical handling of symbolism which made even his failures interesting&quot; (Bithell, 1959 p 391). “Misunderstanding...appears in many and always different ways in his works, from an unconscious ignorance to a deliberate not-wanting-to-know, which works its way over into the realm of lies. It seems obvious to suggest that the idea of misunderstanding as a dramatic principle came to him from various directions, not least from Wedekind’s technique of talking-past-one-another” (Paulsen, 1972). “Alongside of the conception of the play as a philosophical dialogue and a fictional simulation of social development, the blend of pathos and irony must count as one of Kaiser’s principal literary achievement” (Goodbody, 2005 p 74).

==&quot;From morn to midnight&quot;==

[[File:Lucas Cranach d.Ä. - Adam und Eva im Paradies (1531, Gemäldegalerie, Berlin).jpg|thumb|Trouble starts when a bank teller is faced with a woman who wants money for her son to buy Lucas Cranach's picture of Adam and Eve (1531). Painting at the Gemäldegalerie, Berlin]]

Time: 1910s. Place: Germany.

Text at http://www.archive.org/details/frommorntomidni00dukegoog https://archive.org/details/frommorntomidnig00kais https://archive.org/details/twentybesteuropegass

A lady wishes to withdraw 3,000 marks from a bank, but the manager informs her she must wait for confirmation that this sum is available from her Italian bank. &quot;Please tell me, would it be possible for me to leave you the letter of credit for the whole sum, and to receive an advance of 3,000 in part payment?&quot; she pleads the bank-teller. &quot;I should be willing to deposit my diamonds as security, if required.&quot; As an added attraction, she leans on the counter and puts her hand on the cashier's. With no one looking, he crams his pockets with 60,000 marks and leaves as the manager comes in with the confirmation. The lady's son wants the 3,000 marks to buy Lucas Cranach's painting of Adam and Eve. When the bank-teller arrives at her hotel to take her away with him, she hangs back. &quot;Unless I am to consider the whole thing a joke, you gave way to a foolish impulse,&quot; she says. &quot;Listen. You can make good the loss. You can go back to your bank and plead a passing illness- a lapse of memory. I suppose you still have the full amount.&quot; She takes no further interest in the matter when the bank confirms she may pick up her money. At his house, the bank-teller's talk begins to meander. &quot;The dead lie at the usual depth- three yards,&quot; he tells himself. &quot;The living keep on sinking deeper and deeper.&quot; When about to leave before his chops are fried, his mother's arms beat the air as she falls and dies. &quot;For once in his life, a man goes out before his meal and that kills her,&quot; he wrily comments. The bank-manager has not yet pressed charges, refraining to make the matter public in the hope that his employee will come to his senses and return. Instead, the employee enters a velodrome. In a steward's box, he offers prize money at the rate of 1,000 marks, then augments the sum to 50,000 marks, but when the king arrives, he withdraws the offer. In a private supper room of a cabaret, the teller leads in a woman masked like a moth. She falls asleep. He wakes her up by throwing champagne on her face. He then proposes a beauty context between two other masked women, but when they show their faces, he pushes them out. He next leads in a woman in a Pierrette costume and asks her to &quot;spin her bags of bones&quot;. But she has a wooden leg. &quot;I'll water it for you,&quot; he proposes. &quot;We'll make the buds sprout.&quot; Thinking he is mocking her, she exits angrily. He eventually leaves the place after depositing 1,000 marks for the bill. But to the waiter's despair, customers pounce on the money. &quot;The champagne- the supper- the private room- nothing paid for. Five bottles of Pommery, two portions of caviar, two special suppers- I have to stand for everything.&quot; the waiter complains. &quot;I've a wife and children. I've been four months out of a place on account of a weak chest. You won't see me ruined, gentlemen?&quot; They do. He threatens to throw himself into the river. Led by a lass in the hall of the Salvation Army and after hearing different people on the penitent bench, the bank teller confesses his crime and throws bank-notes at the crowd, whereby a skirmish ensues. At least the Salvation Army lass remains with him, until she opens the door. &quot;There he is! I've shown him to you! I've earned the reward,&quot; she cries out to the people. &quot;From morn to midnight, I rage in a circle...and now your beckoning finger points the way...where?&quot; the teller asks himself. At the end of his tether, he shoots himself in the breast in public view, but the event goes unnoticed because of a power failure.

=Ernst Barlach=

[[File:Barlach Selbstbildnis I (1928).jpg|thumb|Ernst Barlach mixed realism and fantasy in troubled settings. Self-drawing of the author, 1928]]

Ernst Barlach (1870–1938) wrote a play entitled &quot;Der blaue Boll&quot; (The Blue Boll, also known as Squire Blue Boll, 1926) in which the mystical is mingled with the grotesque. Barlach's plays &quot;are loosely woven pictorial actions similar to the second part of Goethe's Faust, or Ibsen's Peer Gynt&quot; (Keiler, 1956 p 316) 

“In this comedy of becoming, all the people speak out of their very being, undramatically- their dialogue neither motivates nor is motivated by action” (Fechter, 1972). “The heroes of his best works [including Boll] are great because they preserve and intensify their individuality” (Chick, 1972).

Boll, the 'robust country squire', &quot;is transformed into a spiritual being who, though confused, wants to 'give birth to a new Boll'&quot; (Garten, 1964 p 110). Boll “has been forced into a certain role in society which till now he has played well, enjoying the physical pleasures of his position to the full. Squire Boll is called blue because of the blood pressure and attacks of dizziness brought on by his excesses. He is the glutton and lecher his position has made him...At first Boll towers up himself arrogantly, but the episode in the room halfway up the tower undermines his self-confidence. The confrontation in the room with the witch Greta who is also obsessed with the problem of the flesh marks the parting of the ways for Squire Boll. He can either plunge down from the tower in quick suicidal change of direction or he can go upward to a new life. It is the latter choice which is eventually his, helped towards his final decision in one way or the other by all the characters of the play who are all involved in the process of change...The play is full of strikingly grotesque characters, incidents and situations...Is the gentleman really a force for good who brings about Boll’s regeneration? He seems to drive Otto to death and Boll to the brink of suicide. Doris the demon-woman on the other hand seems to become a kind of earth mother who can take all the sins of the world upon herself, thereby purifying Greta the witch” (Ritchie, 1980 pp 20-21).

“The chief characters of Barlach’s dramas are purely and simply passive victims of misfortune who die surrounded by a halo of anguish and pain” (Muschg, 1972). “The chief characters stand like statues, each alone and separate from the other” (Flemming, 1972).

==&quot;The Blue Boll&quot;==

[[File:Güstrow Gertrudenkapelle - Barlachsammlung Gefesselte Hexe 2.jpg|thumb|Squire Boll attempts to recover his wife, Greta, though considered a witch. Barlach's wooden sculpture of The Bound Witch (1926) at Saint Gertrud's chapel in Güstrow, Germany]]

Time: 1920s. Place: Sternberg, Germany.

Text at ? 

Grüntal is searching for his wife, Greta, who has abandoned him and their three children. Squire Boll, a landowner, hides her in a tower, where she asks him to find poison for her children, to free them from the influence of the flesh. Despite promising to do so, he does not. Holtfreter the shoemaker looks for a missing leg and thinks to have discovered it on a unnamed gentleman, who goes off to drink with him, Boll, Boll's wife, Martha, and his cousin, Otto. Holtfreter is led to think that this unnamed gentleman is God. &quot;I accept the name 'Lord', in the sense I may be a weak and humble reflection out of eternity, a faint, scarcely perceptible shadow of God,&quot; he says, to which Otto, considering this gentleman an impostor, replies: &quot;I always pictured God quite differently,&quot; &quot;From this morning on, becoming has been proceeding quite gloriously in our city,&quot; Holtfreter affirms. Moreover, Otto advises Boll to &quot;renounce the state of all change&quot; and to &quot;stand fast in the state of no-responsibility&quot;. Greta turns up at the 'Devil's Kitchen Inn', greeted by the proprietor, Elias, and his large wife, Doris. She is under the delusion that Elias is prepared to place her children's feet inside a cauldron filled with hot coals, but then the couple calm her down. Three dead men suddenly show up to speak with her. &quot;We must move off again right away with the children,&quot; one of them says, to which she replies: &quot;For you to keep- and then they must turn to apparitions, too, in your fine company- and you must be starving, too, you lot, you've lost a lot of flesh and your hollowed-eyed look certainly means hunger.&quot; After they leave, Greta sees Blue Boll standing in the hot cauldron, while the children play with a golden ball. As Boll walks away, she follows him, waking up the following morning in his company inside a church, where he says the children played with the ball all the way back home. While Greta prays, Martha weeps because Otto has had a stroke. Unexpectedly, Otto returns, affirming strange views such as &quot;the new Boll has triumphed&quot; and that &quot;becoming is fulfilled out of time&quot;. Boll wonders what to do next. &quot;Boll must? Must? I will,&quot; he muses.

=Ernst Toller=

[[File:Ernst Toller - Schwadron.jpg|thumb|Ernst Toller wrote about rebels cast in prison, 1917]]

Ernst Toller (1893–1939) leaned more towards leftist principles than most German Expressionists, particularly in &quot;Hoppla, wir leben!&quot; (Hoppla, we're alive! 1927).

“Albert Kroll, Eva Berg, Mutter Meller, and the rest are contrasted with those would-be reformers who like to play with preposterous and crankish schemes of reform which they haven’t the courage to put into practice and which, though they think of them as progressive, are, in fact, deeply reactionary, betraying the unregenerate feeling that actually inspired them. Thus, at a meeting held, revealingly enough, in a room in the Grand Hotel, Philosopher X puts forward eugenics as the cure for the ills of society...Karl Thomas...may have more insight than do the others into what society is like, but his proposals as to what to do about it are most emphatically wrong. At first he wants to escape, to flee with Eva Berg away from it all...Thomas’ second plan is to assassinate Kilman...Its futility...is underlined by Toller’s making Thomas’ plot coincide with that hatched by the extreme nationalists...In his exchange with Karl Thomas, Albert Kroll comes off best...whose arguments make sense only if a revolution is coming” (Pittock, 1979 pp 121-124).

“The characterization of Kilman is quite subtle. We see him in the prologue as...reprehensible...able to affect great indignation when the 6th prisoner asks to see a priest before his execution...When we see Kilman at work, however, in the second scene, it is obvious he is extremely competent...yet...shows all the more clearly the bankruptcy of his revisionist philosophy...Thomas is to be seen as an exemplar of the revolutionary who has not learned from experience, and thus doomed to ineffectuality, whereas Kroll, Meller and Berg have drawn the necessary conclusions and altered their tactics to fit the post-revolutionary circumstances...Karl’s planned assassination...will not serve as a torch...The scene in the grand hotel indicates at least that [Kilman] cannot be bribed. And when...Pickel asks the...question ‘What will become of the world?’, Kilman, obviously plagued by conscience, evades the question...What Kilman has learned...is total abandonment of principle, deceit and corruption under the guise of striving for the betterment of workers...Karl’s...plan to assassinate Kilman is obviously chimerical if only because the presuppositions for a successful revolution [in 1927] are no longer present as they were in 1918/1919” (Ossar, 1980 pp 141-145).

The play “suggests that it is not so much the supposed irrationality and violent nature of the working class that impedes social change as the eternal bourgeois hiding behind the mask of the artist and intellectual. After all, most of the surviving revolutionaries in Toller’s play end up as complacent bureaucrats perpetuating the very system they once fought against when they were young. The one man who wants to stand up to the oppressive regime, Karl Thomas, ends up back where he started, imprisoned and under psychiatric observation” (Zhulina, 2024 p 198). “Karl Thomas represents the intransigent revolutionary, one hostile to all who disagree with him, one who regards his opponents with hatred and contempt...Albert Kroll...stands for a cautious but, nevertheless, revolutionary policy; he is willing to wait while doing whatever he can to realize his ideals, one who fights for social justice but attempts to control others, more inclined toward unrealistic and hasty action...If Albert Kroll represents continued struggle in adversity and Karl Thomas revolutionary intransigence, both are ultimately frustrated. Albert Kroll’s policy of electoral participation is shown valueless. Workers are disenfranchised, their leaders arrested, and, in the end, the most reactionary minister of all comes to office as the Republic’s leader. Karl Thomas’s policy of active revolution is equally ineffective. The power of the entrenched forces he sees at the hotel is too powerful to be fought by such means” (Ellis, 1979 pp 160-161).

Toller &quot;pairs with Kaiser as a dramatist; but while Kaiser would lift up the proletariat and liberate them from the deformation of routine labour, Toller descends to them wholeheartedly and identifies himself with their aims and hatreds; where Kaiser uses politics for the drama, Toller uses the drama for politics&quot; (Bithell, 1959 pp 394-395). 

==&quot;Hoppla, we're alive!&quot;== 

[[File:Hoppla_vi_lever_Toller_Stockholm_1928.jpg|thumb|Karl Thomas (played by Alf Sjöberg) and Eva Berg (played by Anna Lindahl) have much to fear as rebels of the state. Stockholm, 1928]]

Time: 1919 and 1927. Place: Germany.

Text at https://archive.org/details/in.ernet.dli.2015.186282

Five prisoners are condemned to death for left-wing revolutionary activities. They try to escape, but are unable to. At the last moment, all are reprieved and sent to an internment camp, except Wilhelm. Bursting into unrestrained laughter, Karl is sent into a mental asylum. The other prisoners are unaware that Wilhelm was judged to be involved in the group against his will and set free. When Karl is freed from the asylum 8 years later, he visits Wilhelm and is astonished to learn that his friend is now a minister of the state. He is even more astonished to learn that the minister has repudiated their revolutionary principles. Karl and Eva, an ex-prisoner along with them, are lovers, but she wants him to quit his revolutionary activities and find a job. She also repudiates their revolutionary principles, although active on the subject of workers' rights. Karl explains his principles to the landlady's children, who consider these principles stupid. Eva loses her job because she sympathized with a group of women on strike. Karl then learns from Albert, another ex-prisoner, that Wilhelm prevented workers on strike from voting. Beginning to feel discouraged, Karl asks himself: &quot;What does it matter?&quot; Wilhelm is re-elected in his ministerial position. After sleeping with Wilhelm's wife, and distressed by his re-election, Count Lande tries to assassinate him with the help of a disgruntled student for political reasons. Half-submitting to Eva's view, Karl obtains a job as a waiter in a restaurant, but yet also intends to kill Wilhelm. The student succeeds in killing Wilhelm in the restaurant and runs into Karl. When the student tells Karl he committed the murder because he considered Wilhelm a Bolshevik selling out the country to Jews, Karl shoots at him but misses his target. The police find Karl with a gun and conclude he is the minister's killer. A magistrate sends him back to the asylum, where he is examined and sent back to prison, where he finds Eva and Albert. When the prisoners try to communicate with each other, Karl's cell remains silent.

=Ferdinand Bruckner=

[[File:Ferdinand Bruckner.jpg|thumb|Bruckner exposed the consequences of blackmail, jealous rage, and child murder]]

An Austrian playwright, Ferdinand Bruckner (1891-1958), excelled in depicting the underworld in &quot;Die verbrecher&quot; (The criminals, 1928). 

In The Criminals, Bruckner “criticized the inequities of the legal system by contrasting different cases, their causes and their aftermaths” (Barnett, 2008a p 212). Bruckner &quot;lights up the misery of a block of flats which symbolize God's house of many chambers&quot; (Bithell, 1959 p 405). “Bruckner alternated the street jargon of the younger characters with the utterances of the more educated characters and the contrast became even more striking in act 2, when the playwright employed legalistic parlance in the mouths of the lawyers and judges” (Grange, 1986 p 263).

In general, “Bruckner depicted above all the dark sides of human nature, but he saw its whole terrain” (Schwarz, 1972).

==&quot;The criminals&quot;==

Time: 1920s. Place: Vienna, Austria. 

Text at ?

Josef Berlessen warns Alfred to stop courting his mother as a lodger at her house. Alfred is offended but does not deny the charge or retaliate. Ernestine, a cook at the Berlessen apartment, tries to dissuade Olga, a secretary, to work so hard at her typing during the eight month of pregnancy, being especially concerned about the baby's health, since the two agreed that the mother will relinquish it to her. Alfred is unable to reveal to Frank, his best friend and Josef's brother, about the nature of his troubles, but to Ottfried, a fellow homosexual, he reveals to be in danger of being called to testify in a case of blackmail and homosexuality, fearing the case might lead to his own culpability. The accused, Imanuel, is blackmailing him in exchange for not calling him as a witness. Moreover, Frank sent a compromising letter to a man named Oskar that may lead to further blackmail. To help him, Ottfried promises to find the letter. Ernestine discovers a watch inadvertently left by her lover, Gustav, an unemployed waiter, in the back-room of a bar. Seized in a fit of violent jealousy against the bar-owner, Karla, Ernestine strangles her to death. Meanwhile, Ottfried's mother receives the unwelcome visit of her dead husband's wealthy brother, Dietrich, who, before leaving for South America, gave her for safe keeping a chest of costly jewels. She sold them to pay for the education of her son and daughter. In only three days of knowing each other, the uncle and her daughter decide to marry. After Karl's murder, Ernestine bursts into Olga's room to say that she and her lover, Kummerer, may now keep the baby for themselves. Olga faints in distress at the loss of her expected money. After giving birth, Olga seeks to drown herself with the baby, but while in the water, she changes her mind and reaches shore. However, the baby dies and she is accused of murder. After hearing her testimony, the authorities also accuse her of attempting to sell the baby and investigate the role of Kummerer in both crimes, but he is eventually released. Police inspectors discover that the watch in Karla's room belongs to Gustav, who, unaware of Ernestine's guilt, is accused of  murder. Imanuel is declared innocent, Olga condemned to 8 years in prison, and Gustav unjustly condemned to death. Frank is still worried about being accused of homosexuality, but Ottfried is unable to help. Alfred suggests that they leave together, but Frank says he must first see Oskar. Soon after, Frank is arrested. After hearing about Gustav's condemnation, Ernestine, in the throes of remorse, commits suicide. 


{{BookCat}}</text>
      <sha1>mkfr6vkr2kyhxvihx77qooq7jpwzl8j</sha1>
    </revision>
  </page>
  <page>
    <title>User:Dirk Hünniger/play</title>
    <ns>2</ns>
    <id>249965</id>
    <revision>
      <id>4656172</id>
      <parentid>2528487</parentid>
      <timestamp>2026-08-03T07:45:36Z</timestamp>
      <contributor>
        <username>Dirk Hünniger</username>
        <id>343292</id>
      </contributor>
      <origin>4656172</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="282" sha1="8jvx9114feqqlsh0q9rty1n6hehp7ot" xml:space="preserve">&lt;hiero&gt;Z9&lt;/hiero&gt;
wskko9ßn  asnion0isaas
ámim

asd
,üpsasdxaaüp,a,
&lt;hiero&gt;M17&lt;/hiero&gt;
&lt;hiero&gt;M17&lt;/hiero&gt;

saöl,m, maüsodmspksak
+
asäd
äsap,üd,oas,
,sad,xa,


&lt;hiero&gt;M17-Y5*n*M17:Y4*l-M17&lt;/hiero&gt;

sad,a,lml  sadas asö adölsölaslösa  aöaöl,asöl,sla
&lt;hiero&gt;M17&lt;/hiero&gt;</text>
      <sha1>8jvx9114feqqlsh0q9rty1n6hehp7ot</sha1>
    </revision>
  </page>
  <page>
    <title>Saylor.org's Comparative Politics</title>
    <ns>0</ns>
    <id>270405</id>
    <revision>
      <id>4656160</id>
      <parentid>3471492</parentid>
      <timestamp>2026-08-03T05:46:54Z</timestamp>
      <contributor>
        <username>~2026-42916-19</username>
        <id>3618819</id>
      </contributor>
      <origin>4656160</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="12960" sha1="g6pl3wrylg38amsvw8dqqdjaaq2n1cu" xml:space="preserve">Dear Wikipedians,

No doubt some of you are familiar with the free college courses available on [http://Saylor.org Saylor.org]. Much like the Wikimedia community, we are committed to providing free and accessible education for everyone with internet access. At Saylor, we combine some of our custom-created educational materials with materials that are already available throughout the internet. However, because we sometimes use links to third party materials, those sections of our courses are not entirely sustainable. The Saylor Wikibooks Project is a way for you to help minimize that threat. We’ve uploaded a number of our course outlines to Wikibooks in the hope that you all will contribute to our effort. Our course outlines have been developed by our consultant professors by studying a collection of syllabi of relevant courses from various traditional brick and mortar institutions. This guarantees that our students will be provided the same learning opportunity as a student enrolled in a traditional institution. We believe that we have created the best structure for our courses, which optimizes the information that students would be expected to know. By creating openly licensed content that fits in with Saylor’s established course outlines, (in the form of Wikibooks’ textbooks), you can add to the ever-expanding body of wiki material, while simultaneously improving the sustainability of our courses.&lt;br /&gt;
&lt;br /&gt;

Thanks for your help,  &lt;br /&gt;

The Saylor Team with our famous captain Harriet 


If you'd like to learn more about the project please visit [[User:Thomas_Simpson]]


'''&lt;big&gt;Summary&lt;/big&gt;'''

[[File:Dáil_Chamber.jpg|thumb|right]]
Like it or not, we can’t escape politics.  Politics, a term best defined as the distribution, exercise, and consequences of power, exists at multiple levels in our society and in our daily lives.  We experience politics in action, for example, in international negotiations, government policy choices, our workplace, and even in our own families.  This course focuses its efforts on exploring the formal, public sphere of politics and power relations through a systematic study and comparison of types of government and political systems.

Comparatists (practitioners of comparative politics) seek to identify and understand the similarities and differences between these systems by taking broad topics—say, for example, “democracy” or “freedom”—and breaking them down into factors that can be found in individual systems.  We call this general approach “the comparative method.”  The goal of the comparative method is to identify the factors and/or categories of analysis to effectively compare and contrast different political phenomena.  Using the comparative method, we can tackle broader, more complicated questions like: Are certain forms of representative democracy more effective than others?  Why are some countries extremely prosperous, while others are extremely poor?  How does the degree of authoritarian control by a government drive economic development?  Does culture impact quality of governance?


'''&lt;big&gt;Global Learning Outcomes&lt;/big&gt;'''

Upon successful completion of this course, the student will be able to:

* Identify and differentiate between various theoretical research paradigms employed in the social sciences.
* Apply comparative methodology to the study of political systems.
* Identify and differentiate between various methodologies used to compare political systems.
* Define the chief characteristics of a nation state.
* Identify and explain various comparative methodologies used to compare various political systems.
* Distinguish between unitary, federal, and confederal governmental models.
* Compare and contrast political cultures in selected countries.
* Compare and contrast political socialization in selected countries.
* Describe and explain patterns of representation and participation in selected countries.
* Compare and contrast the roles and functions of political parties in selected countries.
* Compare and contrast the role of interest groups in selected countries.
* Identify and explain governance and policy-making in selected countries.
* Compare and contrast the role of the executive in selected countries.
* Compare and contrast the role of the judicial branch in selected countries.
* Compare and contrast the role of the bureaucracy and the policy process in selected countries.
* Describe and explain the political economy and development in selected countries.
* Identify and explain political challenges and changing agendas in selected countries.


__TOC__

==[[/Social Science and Comparative Politics/]]==

Upon successful completion of this unit, the students will be able to:
* Describe the scientific method.
* Differentiate between scientific laws and theories.
* Differentiate between inductive and deductive thinking.
* Define explanatory, exploratory, and descriptive research.
* Differentiate between positivist, antipositivist and postpositivist methods.
* Differentiate between Mill’s “Method of Agreement” and “Direct Method of Difference.”
* Define comparative politics.
* Identify and explain various comparative methodologies used to compare various political systems.
* Evaluate if normative theory has a place in comparative political inquiry.
&lt;br /&gt;

:1.1 [[/Social Science Basics/]]
::1.1.1 [[/The Scientific Method and History of Scientific Inquiry/]]
::1.1.2 [[/Social Science Theory and Reasoning/]]
:1.2 [[/Comparative Methodology/]]
::1.2.1 [[/The Comparative Method/]]
::1.2.2 [[/John Stuart Mill’s Methods of Comparision/]]
::1.2.3 [[/Varieties of Methods in Comparative Politics/]]

==[[/The Nation-State/]]==

Upon successful completion of this unit, the student will be able to:
* Identify the origins of the modern nation state system.
* Define the chief characteristics of a nation state.
* Differentiate between nations and nation-states.
* Define sovereignty and identify and explain trends in sovereignty.
* Identify characteristics of a strong and weak state.
* Explain how Hobbes and Weber conceptualize the state.
* Define sovereignty and identify and explain trends in sovereignty.
* Differentiate between authoritarian and totalitarian states.
* Identify sources for authoritarian states.
&lt;br /&gt;

:2.1 [[/The State/]]
::2.1.1 [[/Defining the State/]]
::2.1.2 [[/The Treaty of Westphalia the Origins of the Modern State/]]
:2.2 [[/The Modern State System/]]
::2.2.1 [[/Hobbes and Sovereignty/]]
::2.2.2 [[/Weber and the Modern State/]]
::2.2.3 [[/Growth of the State System after the Second World War/]]
:2.3 [[/Non-Democratic State Forms/]]
::2.3.1 [[/Authoritarian States/]]
::2.3.2 [[/Totalitarian States/]]
::2.3.3 [[/Military Junta/]]
::2.3.4 [[/Sources and Trends of Authoritarianism/]]

==[[/Democratic States and Democratization/]]==

Upon successful completion of this unit, the student will be able to:
* Define democracy.
* Differentiate between representative (indirect) and participatory (direct) democracy
* Identify why the Magna Carta and Treaty of Westphalia are important in the history of democratization.
* Identify prominent characteristics of democratic states.
* Identify trends in democratization.
* List the six major explanations for democratization.
* Explain and assess if democracy improves economic outcomes.
&lt;br /&gt;

:3.1 [[/Defining Democracy/]]
::3.1.1 [[/What is Democracy?/]]
::3.1.2 [[/Criteria of Democracy/]]
::3.1.3 [[/Characteristics of Democracy/]]
:3.2 [[/Democratization/]]
::3.2.1 [[/What Causes Democratization?/]]
::3.2.2 [[/Economic Development and Democracy/]]
::3.2.3 [[/The Rise of the Democratic State and the “Third Wave”/]]
::3.2.4 [[/Democracies Today: The Freedom House Index/]]
::3.2.5 [[/Case Study: The Arab Spring/]]
==[[/Comparing Political Structures and Institutions/]]==

Upon successful completion of this unit, the student will be able to:
* Identify the role of constitutions in government systems.
* Distinguish between presidential, semi-presidential, and parliamentary systems.
* Distinguish between unitary, federal, and confederal governmental models.
* Compare and contrast the role of the executive in selected countries.
* Compare and contrast the role of the judicial branch in selected countries.
* Compare and contrast the role of the bureaucracy and the policy process in selected countries.
&lt;br /&gt;

:4.1 [[/Comparing Constitutions and Government Systems/]]
::4.1.1 [[/Importance of Constitutions/]]
::4.1.2 [[/Checks and Balances between Branches of Government/]]
::4.1.3 [[/The Role of the Executive Branch/]]
::4.1.4 [[/The Role of the Judicial Branch/]]
::4.1.5 [[/Presidential, Semi-Presidential, and Parliamentary Systems/]]
::4.1.6 [[/Types of Legislatures: Unicameral vs Bicameral Systems/]]
::4.1.7 [[/Limits of Written and Unwritten Constitutions/]]
:4.2 [[/How to Design Multi-level Government/]]
::4.2.1 [[/Understanding Diverse Populations and Public Opinion/]]
::4.2.2 [[/Confederations vs. Federations/]]
::4.2.3 [[/Types of Electoral Systems/]]
::4.2.4 [[/Direct Democracy: Evaluation and Feedback/]]
::4.2.5 [[/The 'Iron Triangle': Legislators, Bureaucrats, and Interest Groups/]]
:4.3 [[/Bureaucracy/]]
::4.3.1 [[/Defining Bureaucracy/]]
::4.3.2 [[/Bureaucrats vs. Political Appointments/]]
:4.4 [[/Trends in Governance: Public Sector and Privatization/]]
::4.4.1 [[/The Public Sector/]]
::4.4.2 [[/Privatization in Government/]]

==[[/Political Behavior/]]==

Upon successful completion of this unit, the student will be able to:
* Define political culture, political socialization, and political participation.
* Compare and contrast political cultures in selected countries.
* Compare and contrast political socialization in selected countries.
* Describe and explain patterns of representation and participation in selected countries.
* Compare and contrast the roles and functions of political parties in selected countries.
* Compare and contrast the role of interest groups in selected countries.
&lt;br /&gt;

:5.1 [[/Political Behavior and Political Culture/]]
::5.1.1 [[/How Do People Form Political Attitudes?/]]
::5.1.2 [[/How Do Cultural Patterns Influence Institutions?/]]
::5.1.3 [[/How Do We Measure Political Participation?/]]
::5.1.4 [[/Political Mobilization and Alienation/]]
::5.1.5 [[/Political Alliances and Cleavages/]]
:5.2 [[/Civil Society/]]
::5.2.1 [[/Social Movements and Activism/]]
::5.2.2 [[/Lobbying/Government Relations/]]
::5.2.3 [[/Quasi Non-Governmental Organizations (QUANGOs)/]]
:5.3 [[/The Media/]]
::5.3.1 [[/Media Ownership and Multimedia Conglomeration/]]
::5.3.2 [[/The Free Press and the Information Market/]]
::5.3.3 [[/Regulating the Media/]]
::5.3.4 [[/Electronic Politics (e-Politics)/]]
:5.4 [[/Voting System Factors/]]
::5.4.1 [[/Voting and the Human Development Index (HDI)/]]
::5.4.2 [[/Controlling the Vote: Turnout, Suffrage, and Gerrymandering/]]
::5.4.3 [[/Proportionality and Election Thresholds in Parliamentary Systems/]]
::5.4.4 [[/Protest Votes and Non-Voters/]]

==[[/Comparing Ideology, Policy, and Decision Making/]]==

Upon successful completion of this unit, the student will be able to:
* Identify the basic belief systems of various mainstream ideologies found in contemporary democratic societies and political parties.
* Identify and explain governance and policy-making in selected countries.
* Identify informal influences on governance and policy making.
&lt;br /&gt;

:6.1 [[/Contemporary Mainstream Political Ideologies/]]
::6.1.1 [[/Conservatism/]]
::6.1.2 [[/Liberalism/]]
::6.1.3 [[/Christian Democracy/]]
::6.1.4 [[/Social Democracy/]]
::6.1.5 [[/Environmentalism/]]
:6.2 [[/The Public Policy Cycle/]]
::6.2.1 [[/Agenda Setting/]]
::6.2.2 [[/Debate and Compromise/]]
::6.2.3 [[/Implementation and Choice of Means/]]
::6.2.4 [[/Evaluation and Feedback/]]
::6.2.5 [[/The 'Iron Triangle': Legislators, Bureaucrats, and Interest Groups/]]
:6.3 [[/Politics beyond the Policy Process/]]
::6.3.1 [[/Informal Economies and Black Markets/]]
::6.3.2 [[/Corruption and Cronyism/]]
==[[/Comparative Case Studies/]]==

Upon successful completion of this unit, the student will be able to:
* Describe and explain the political economy and development in selected regions and countries.
* Identify and explain political challenges and changing agendas in selected regions and countries.
&lt;br /&gt;

:7.1 [[/Africa/]]
::7.1.1 [[/Colonial History/]]
::7.1.2 [[/African Case Studies/]]
:7.2 [[/Latin America/]]
::7.2.1 [[/Overview of Latin American Development and State Forms/]]
::7.2.2 [[/Latin American Case Studies/]]
:7.3 [[/Asia/]]
::7.3.1 [[/Overview of Asian Development and State Forms/]]
::7.3.2 [[/Asian Case Studies/]]
:7.4 [[/The Middle East and the Islamic World/]]
::7.4.1 [[/The Colonial Division of the Ottoman Empire/]]
::7.4.2 [[/The Creation of Israeli Statecraft/]]
::7.4.3 [[/Political Islam/]]

{{shelves|political science}}
{{alphabetical|s}}
{{alphabetical|c}}
{{status|0%}}</text>
      <sha1>g6pl3wrylg38amsvw8dqqdjaaq2n1cu</sha1>
    </revision>
  </page>
  <page>
    <title>User talk:Revi C.</title>
    <ns>3</ns>
    <id>294082</id>
    <revision>
      <id>4656047</id>
      <parentid>4656023</parentid>
      <timestamp>2026-08-02T14:17:01Z</timestamp>
      <contributor>
        <username>Pathoschild</username>
        <id>13563</id>
      </contributor>
      <comment>global user pages ([[m:Synchbot|requested by Revi C.]])</comment>
      <origin>4656047</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1122" sha1="5b8qtz4dnjnrhc9ts3mku14m3gujbq8" xml:space="preserve">__NOINDEX__&lt;div class=&quot;mw-content-ltr&quot; lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;[[File:Revi logo (pink).png|thumb|center|&lt;span style=&quot;color:red&quot;&gt;PLEASE DO NOT LEAVE MESSAGE HERE!&lt;/span&gt;]]

'''&lt;span style=&quot;color:red&quot;&gt; BEFORE YOU BLOCK MY ACCOUNT: IF MY EDIT SUMMARY INCLUDE PREFIX &lt;/span&gt;''(Script)''&lt;span style=&quot;color:red&quot;&gt;, DON'T BLOCK ME, JUST TELL ME TO SLOW DOWN AT COMMONS' TALK PAGE. IT IS AN AUTOMATED SCRIPT BEING USED ON COMMONS TO MOVE FILES.&lt;/span&gt;'''

Instead, please leave your message following site:
&lt;br /&gt;
[[File:Wikidata-logo-en.svg|45px|link=d:User talk:Revi C.]] [[d:User talk:Revi C.]] for Wikidata (Interwiki links) stuff &lt;!--(I am {{int:Group-sysop}} there)--&gt;
&lt;br /&gt;
[[File:Commons-logo.svg|45px|link=commons:User talk:Revi C.]] [[commons:User talk:Revi C.]] for renaming stuff or [[User:CommonsDelinker|CommonsDelinker]] action (I am {{int:Group-sysop}} there)
&lt;br /&gt;
[[File:Wikimedia Community Logo optimized.svg|45px|link=m:User talk:Revi C.]] [[meta:User talk:Revi C.]] for other stuff (User right notification, revert message, etc...)

Messages left on this page may be reverted or moved without any response.&lt;/div&gt;</text>
      <sha1>5b8qtz4dnjnrhc9ts3mku14m3gujbq8</sha1>
    </revision>
  </page>
  <page>
    <title>Fluid Mechanics Applications/A07 Dimples on Golf Ball</title>
    <ns>0</ns>
    <id>306416</id>
    <revision>
      <id>4656091</id>
      <parentid>4041523</parentid>
      <timestamp>2026-08-02T18:56:37Z</timestamp>
      <contributor>
        <username>Issac I Navarro</username>
        <id>3491575</id>
      </contributor>
      <comment>/* ADVANTAGES OF DIMPLES */ svg file</comment>
      <origin>4656091</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="6440" sha1="266ezj949dexmjbyz33xej465c25ozm" xml:space="preserve">{{TOCright}}
As a matter of fact, it was noted that break in surface area decreases the vortex formed behind the body. For example, to decrease the drag force on car spoilers are introduced. Dimples on golf ball also plays similar role but have many other uses. Dimples on it are responsible for the flight, trajectory and movement of golf ball. Basically it all depends on the aerodynamics of ball. As we study, there are two types of flows, namely, Laminar flow and Turbulent flow. Laminar flow, initially, experience less drag but also, it is prone to separation (boundary layer phenomenon). Due to this phenomenon drag force increases with time. But it is opposite in the case of turbulent flow. As the matter of fact, these dimples create turbulence in layer of air next to it. Thus reducing drag force.

== HISTORY OF GOLF BALLS ==
In the beginning, golf balls were made of leathers and were scuffed with wet goose feathers. These balls were known to be called as &quot;featheries&quot;. With the passage of time manufacturing of balls made from molded rubber sap started. These balls were called as “Gutta percha balls” as they were made from sap of gutta percha tree. These balls were designed in shape of perfect sphere on the basis that smooth ball will go farther and would experience less drag force. But this thought proved to be wrong when golfers experienced that balls that were beaten up by nicks, bumps and slices go farther. This was because of the reason that nicks and cuts were acting as the tabulators on the surface of ball. Thus, in 1930 dimpled golf balls were discovered accidentally and till then dimpled golf ball is used. There is not any limitation to the numbers on golf ball but a number from 300 to 500 is common. 392 dimples are conveniently used as this type of ball provides a golfer a satisfied result. After that people believed that more would be the number of dimples farther it would go but this theory was rejected. But the manufacturers tried various sets and combination of dimples. Now, there is variety of dimples available on golf balls. Some are deep, some are shallow and also, large and small. Shapes of dimples also vary. These may in shape of circle, ovals and even in the shape of hexagons.
[[file:Golf_ball_dimples_ORA_OK.jpg|thumb|This image shows the difference in golf and smooth ball]]

== ADVANTAGES OF DIMPLES ==
There are various advantages of dimples on the golf ball. These are:
* Dimples convert the spin of golf ball into lift. It was discovered accidentally.
* Dimples reduce the drag exerted on the ball. A dimpled ball experiences about half of drag experienced by a smooth ball.
* Numbers and size of dimples on golf ball decides the trajectory or flight characteristics of golf ball. For instance, “Distance” balls are designed in such a manner to cause the ball to fly low and bounce far which is advantage during a long course or in high winds. But for short of greens “Control” balls are used. These balls are dimpled in the manner to induce lift at end of its arc so that ball falls almost vertical.
* Dimples create turbulence in the layer of air around the ball. This results in smaller vortex.
[[File:Trajectory of balls.svg|thumb|Different trajectories of ball]]

== MECHANICS OF LIFT AND DRAG ==
[[File:Golf ball-Model.jpg|thumb|This picture depicts the various forces exerted on the golf ball. These forces are drag, weight and Magnus force.]]
There are three forces which act on the golf ball when it is flying in the air. Two of them are clear to analyze which are gravity and drag. One force also appears on it which is due to Magnus effect and called as Magnus force. This is developed due to the spinning of ball. Initially it was believed that balls in the form of perfect sphere and are smooth experience less drag but it was not so. This perception would be correct if the ball doesn’t spin but actual condition shows that ball took spins just after the moment it leaves the tee. On an average, a golf ball leaves the tee with a speed of 80&amp;nbsp;m/s and about 60 rev/s of backspin. The Magnus force is experienced due to the relative drag on air at boundary at top and bottom of the ball. The top of the ball is moving with lower relative velocity compared to the air around it resulting in less drag on air that goes over the ball. Thus flow becomes laminar at that region. Similarly, bottom part moves faster relative to the air near it, thus experiencing less drag on air passing by. This develops turbulent layer at this region and resulting the air movement near the region slower relative to the ball. Thus Bernoulli force produces lift or we could also say that the flow lines past the ball are displaced down causing the ball to be pushed up.
According to Bernoulli's equation,
&lt;math&gt;
  \frac{p}{\rho} + \frac{V^2}{2} + gz = constant
&lt;/math&gt;

where,
* &lt;math&gt;p&lt;/math&gt;-difference in pressures on body
* &lt;math&gt;\rho&lt;/math&gt;-density of body
* &lt;math&gt;V&lt;/math&gt;-velocity of fluid surrounding the body
* &lt;math&gt;g&lt;/math&gt;-acceleration due to gravity
* &lt;math&gt;z&lt;/math&gt;-height of body
Thus, dimples are what gives a golf ball lift. This is done by creating two layers of air going around the ball. Turbulence is created because the top layer is going faster than the bottom layer. This reduces the drag and allows the ball to travel farther than a smooth ball.

== TRAJECTORY OF GOLF BALL ==
The variety of dimples (different shapes and sizes) also determine the flight characteristic/ trajectory of ball. There are different kinds of golf ball available in the market and are produced by the manufacturers. Hexagonal balls with moderate intensity are used mostly, giving ball a structure similar to Buckminsterfullerene and also helping the golfer an accurate idea of path. most of the golfers need that the golf ball should fall vertically so as the ball drops in the hole with less efforts.

== References ==
{{Reflist}}
&lt;ref&gt;Lord Rayleigh, &quot;On the Irregular Flight of a Tennis Ball&quot;, Scientific Papers I, pg 344&lt;/ref&gt;
&lt;ref&gt;R. Watts and R. Ferver, &quot;The Lateral Force on a Spinning Sphere Aerodynamics of a Curveball&quot;, Am. J. Phys. 55, 40 (1986)&lt;/ref&gt;
&lt;ref&gt;Steve Haake, &quot;Physics and Golf?  You must be joking!&quot; Physics World 10, 76 (1997)&lt;/ref&gt;
&lt;ref&gt;Journal of Applied Physics 20, 821 (1949) by Davies&lt;/ref&gt;
&lt;ref&gt;American Journal of Physics 56, 933 (1988) by McPhee and Andrews&lt;/ref&gt;
&lt;ref&gt;&quot;The Physics of Golf&quot; by Theodore P. Jorgensen&lt;/ref&gt;

{{bookcat}}</text>
      <sha1>266ezj949dexmjbyz33xej465c25ozm</sha1>
    </revision>
  </page>
  <page>
    <title>Template:OpenSSH/TOC</title>
    <ns>10</ns>
    <id>372303</id>
    <revision>
      <id>4656103</id>
      <parentid>4637792</parentid>
      <timestamp>2026-08-02T20:27:54Z</timestamp>
      <contributor>
        <username>Some helpful person</username>
        <id>3510188</id>
      </contributor>
      <minor />
      <comment>revert vandalism</comment>
      <origin>4656103</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1767" sha1="4mo06u6qrgyigs5hkoenjkcncvrmqck" xml:space="preserve">&amp;nbsp;
&lt;div class=&quot;{{ #if: {{{1|}}}|hiddenStructure|}}&quot;&gt;
{| style=&quot;margin:0px auto; text-align:center;&quot; cellspacing=&quot;0&quot; id=&quot;toc&quot; 
| '''[[OpenSSH]]'''&lt;br /&gt;
[[OpenSSH/Overview|Overview]] &amp;bull;
[[OpenSSH/Why Use Encryption|Why&amp;nbsp;Encryption]] &amp;bull;
[[OpenSSH/SSH Protocols|Protocols]] &amp;bull;
[[OpenSSH/Other SSH Implementations|Implementations]] &amp;bull;
[[OpenSSH/Client Applications|Clients]] &amp;bull;
[[OpenSSH/Client Configuration Files|Client&amp;nbsp;Configuration]] &amp;bull;
[[OpenSSH/Server|Server]] &amp;bull;
[[OpenSSH/Pattern Matching in OpenSSH Configuration|Patterns]] &amp;bull;
[[OpenSSH/Utilities|Utilities]] &amp;bull;
[[OpenSSH/Third_Party_Utilities|Third&amp;nbsp;Party]] &amp;bull;
[[OpenSSH/Logging_and_Troubleshooting|Logging&amp;nbsp;and&amp;nbsp;Troubleshooting]] &amp;bull;
[[OpenSSH/Development|Development]]
&lt;br /&gt;
&amp;nbsp;
'''Cookbook''': 
[[OpenSSH/Cookbook/Remote_Processes‎|Remote&amp;nbsp;Processes]] &amp;bull;
[[OpenSSH/Cookbook/The_Client_Configuration_File‎|The&amp;nbsp;Client&amp;nbsp;Configuration&amp;nbsp;File]] &amp;bull;
[[OpenSSH/Cookbook/Tunnels|Tunnels]] &amp;bull;
[[OpenSSH/Cookbook/Automated_Backup|Automated&amp;nbsp;Backup]] &amp;bull;
[[OpenSSH/Cookbook/File_Transfer_with_SFTP| File&amp;nbsp;Transfer&amp;nbsp;with&amp;nbsp;SFTP]] &amp;bull;
[[OpenSSH/Cookbook/Public Key Authentication|Public&amp;nbsp;Key&amp;nbsp;Authentication]] &amp;bull;
[[OpenSSH/Cookbook/Certificate-based_Authentication|Certificate-based&amp;nbsp;Authentication]] &amp;bull;
[[OpenSSH/Cookbook/Host-based_Authentication‎|Host-based&amp;nbsp;Authentication]] &amp;bull;
[[OpenSSH/Cookbook/Load_Balancing‎|Load Balancing]] &amp;bull;
[[OpenSSH/Cookbook/Multiplexing|Multiplexing]] &amp;bull;
[[OpenSSH/Cookbook/Proxies_and_Jump_Hosts|Proxies&amp;nbsp;and&amp;nbsp;Jump&amp;nbsp;Hosts]]
&amp;nbsp;
|}
&lt;/div&gt;
&lt;noinclude&gt;[[category: navigational templates]]
&lt;/noinclude&gt;{{BookCat}}</text>
      <sha1>4mo06u6qrgyigs5hkoenjkcncvrmqck</sha1>
    </revision>
  </page>
  <page>
    <title>Lentis/Net Neutrality</title>
    <ns>0</ns>
    <id>393373</id>
    <revision>
      <id>4656094</id>
      <parentid>4217941</parentid>
      <timestamp>2026-08-02T19:31:22Z</timestamp>
      <contributor>
        <username>~2026-42592-50</username>
        <id>3618745</id>
      </contributor>
      <comment>/* Background */ fixed typo</comment>
      <origin>4656094</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="35289" sha1="cplsat1s0fb2l6qv3nt2vj7iyxmsixk" xml:space="preserve">__TOC__
== Introduction ==

=== Background ===
Net neutrality is the principle that internet service providers (ISPs) cannot interfere with the content they provide customers or show preference to any content.  Whether action should be taken and what that action should be is a rising concern. Policymakers contend that more guidelines are necessary to protect the online marketplace from potential abuses threatening a free and open internet. Others contend that the existing policies are either sufficient or are too strict.&lt;ref&gt;Gilroy, A. A. (2008). Net neutrality: background and issues.&lt;/ref&gt;

In the United States, this principle is protected by Title II of the Communications Act of 1934 which defines ISPs as common utilities rather than information providers, preventing ISPs from charging content creators premiums for faster delivery to the end user.&lt;ref&gt;Federal Communications Commission. (2015). FCC adopts strong, sustainable rules to protect the open internet. &lt;nowiki&gt;http://transition.fcc.gov/Daily_Releases/Daily_Business/2015/db0226/DOC-332260A1.pdf&lt;/nowiki&gt;&lt;/ref&gt; This principle is supported by major content creators such as Google, Facebook, and Netflix, along with growing businesses and the general public because they view the system as a level playing field for their content. However, the chair of the Federal Communications Commission (FCC), Ajit Pai, along with major ISP corporations such as Comcast and Verizon, favor replacing Title II regulations with user agreements that set the terms of service they provide, claiming that regulations inhibit service development and reduce competition between ISP’s.&lt;ref&gt;PBS NewsHour. (2017). FCC chair Ajit Pai explains why he wants to scrap net neutrality. PBS. &lt;nowiki&gt;https://www.youtube.com/watch?v=6Q5_oV4JB10&lt;/nowiki&gt;&lt;/ref&gt; 

This issue has been prevalent since the turn of the century and gained notoriety when Comcast was caught interfering with traffic on certain sites.&lt;ref&gt;A Timeline of Net Neutrality. (n.d.). December 7, 2017, &lt;nowiki&gt;http://whatisnetneutrality.org/timeline&lt;/nowiki&gt;&lt;/ref&gt; ISPs have lobbied lawmakers to pass legislation that favors them while the general public utilizes online forums, blog posts, and the media to gain the attention of lawmakers, highlighting the battle between economic interests in the political domain.&lt;ref&gt;Oliver, J. (2014). Net Neutrality. Last Week Tonight. &lt;nowiki&gt;https://www.youtube.com/watch?v=fpbOEoRrHyU&lt;/nowiki&gt;&lt;/ref&gt;

=== History ===
June 1934 – The Communications Act of 1934 created the Federal Communications Commission (FCC) to regulate commerce in wire and radio communication. The FCC replaced the Federal Radio Commission and took over telecommunication authority from the Interstate Commerce Commission.&lt;ref&gt;Communications Act of 1934, Pub. L. No. 13-416, 48 Stat. 1064 (1934).&lt;/ref&gt;

February 1996 – The Telecommunications Act of 1996 included the internet in the broadcast and spectrum allotment in order to establish government regulatory control and increase market competition.&lt;ref&gt;Telecommunications Act of 1996, Pub. L. No. 104-104, 110 Stat. 56 (1996).&lt;/ref&gt;

March 2002 – Under chairman Michael Powell, the FCC classified cable modem services as an Title I &quot;information service&quot; under the Communications Act of 1934; thus, relaxing regulation of broadband internet providers.&lt;ref&gt;Federal Communications Commission. (2002). FCC Classifies Cable Modem Service as &quot;Information Service” (FCC 02-77). Federal Communications Commission.&lt;/ref&gt;

January 2003 – The history of net neutrality dates back to its first coined use by Professor Tim Wu of Columbia University in 2003.{{Ref|Wu2003}} In his paper, ''A Proposal for Network Neutrality'', Wu discusses the principal of balancing the interests of the ISPs in providing their networks with the threats of new application markets.{{ref|Wu2002}}

June 2005 – The Supreme Court upheld the FCC’s authority to classify broadband in federal appeals case Brand X (an ISP) vs. the FCC, so broadband remained an information service according to the FCC and was exempt from common carrier requirements of utilities.&lt;ref&gt;National Cable &amp; Telecommunications Association v. Brand X Internet Services. 545 U.S. 967 (2005).&lt;/ref&gt;

October 2007 - August 2008 – The Associated Press and other news outlets report on Comcast, one of the dominant ISPs at the time, and Comcast’s interference with BitTorrent traffic.&lt;ref name=&quot;:0&quot;&gt;Svensson, P. (2007, October 19). Comcast Blocks Some Internet Traffic. &lt;nowiki&gt;http://www.nbcnews.com/id/21376597/ns/technology_and_science-internet/t/comcast-blocks-some-internet-traffic/&lt;/nowiki&gt;&lt;/ref&gt; This marks the first time that any United States ISP was found to violate net neutrality rules. Comcast claims that their measures were necessary to prevent its network from being overrun. The following year, the FCC ruled against Comcast and gave them a cease-and-desist order, required disclosure to customers on how they manage traffic in the future, and mandated network management without throttling specific traffic protocols.&lt;ref name=&quot;:0&quot; /&gt;

April 2010 – The U.S. Court of Appeals for the D.C. Circuit sided with Comcast in their appeal against the FCC, stating that “the agency does not have the power to regulate an Internet provider's network management practices.”&lt;ref&gt;McCullagh, D. (2010, April 6). Court: FCC has no power to regulate Net neutrality. &lt;nowiki&gt;https://www.cnet.com/news/court-fcc-has-no-power-to-regulate-net-neutrality/&lt;/nowiki&gt;&lt;/ref&gt;

December 2010 – Under chairman Julius Genachowski, the FCC adopted Open Internet Order, which is the first-time net neutrality appears in regulation.&lt;ref&gt;Federal Communications Commission. (2010). FCC Releases Open Internet Order (30 FCC Rcd 5601).&lt;/ref&gt; The rules were not published until September 2011.{{ref|Feld2011}}

January 2014 – Verizon filed a case against the FCC saying that the Open Internet Order was overstepping the FCC’s authority. The court divided the Open Internet Order and ultimately ruled that some sections were outside of the FCC’s jurisdiction due to the classification of broadband as an information service, whereas other sections were maintained or expanded.&lt;ref&gt;Verizon Communications v. Federal Communications Commission, 740 F.3d 623 (D.C. Cir. 2014)&lt;/ref&gt;

May 2014 – Under chairman Tom Wheeler, the FCC reinstated net neutrality. However, the proposal sparked protest by net-neutrality supporters at the notion of differing Internet speed connection lanes.&lt;ref&gt;Wyatt, E. (2014, April 23). F.C.C. in a Shift, Backs Fast Lanes for Web Traffic. The New York Times. &lt;/ref&gt; The proposal allowed fast and slow lanes on the internet, where the slow lane guaranteed a minimum level of access, while not blocking any content or degrading the connection. The fast lane could be sold to provide a commercially reasonable speed. This marked the beginning of a two-tier internet with the FCC assuming the minimum level of access will remain fast.{{ref|publick2014}}

February 2015 – As urged by president Barack Obama, the FCC voted to classify the internet as a Title II service “public utility” under the Communications Act of 1934. Chairman Wheeler also extended the authority to mobile networks in order to modernize the 1934 act.&lt;ref&gt;a.      Barack, Obama. (2015, February 26). “RT to share the news: The @FCC just voted to keep the internet open and free” [Twitter Post]. &lt;nowiki&gt;https://twitter.com/ObamaWhiteHouse/status/571034676636200960?ref_src=twsrc%5Etfw%7Ctwcamp%5Etweetembed%7Ctwterm%5E571034676636200960&amp;ref_url=https%3A%2F%2Fobamawhitehouse.archives.gov%2Fnode%2F323681&lt;/nowiki&gt;&lt;/ref&gt;

January 2017 – President Donald Trump appoints Ajit Pai as the new chairman for the FCC.{{ref|Seth2017}}  Pai announced his plans for reversing the Title II regulations recently set.{{ref|Kast2017}}

July 12, 2017 – Amazon, Reddit, Netflix and many other significant internet organizations participated in a &quot;Day of Action to Save Net Neutrality&quot; as an attempt to convince the currently Republican-controlled FCC to keep the net neutrality rules.{{ref|Action2017}}


August 11, 2017 - Jessica Rosenworcel serves as a Chair of the Federal Communications Commission, where she was a Commissioner since 2012. At the agency, she promoted greater opportunity, accessibility, and affordability in our communications services in order to provide more equality for all Americans. Also, she fought to protect an open internet in order to ensure broadband access for students in the Homework Gap through the FCC’s Emergency Connectivity Fund and to make sure that families who cannot afford internet service stay connected through the Emergency Broadband Benefit program. 

October 26, 2021 - Gigi Sohn is a fellow at the Georgetown Law Institute for Technology Law &amp; Policy and a Benton Senior Fellow and Public Advocate. Gigi is a public advocate for open, affordable, and democratic communications networks. For over thirty years, Gigi has worked to preserve the fundamental competition and innovation policies that have helped made broadband Internet access more ubiquitous, competitive, affordable, open, and protective of user privacy. 

March 2018 – Congress introduced the ‘Save the Internet Bill’ to restore net neutrality as defined in 2010 by the Open Internet Order. It included a proposal to reverse the FCC’s 2017 ruling to reclassify broadband. &lt;ref&gt;Satterwhite, E. (2019, March 8). Save the Internet Bill Introduced. &lt;nowiki&gt;https://americanlibrariesmagazine.org/blogs/the-scoop/bicameral-save-the-internet-bill-introduced/&lt;/nowiki&gt;&lt;/ref&gt;

October 2019 – The United States Court of Appeals for the District of Columbia Circuit upheld the repeal of net neutrality and deregulation, but ruled that states could pass their own net neutrality protections.&lt;ref&gt;Reardon, M. (2019, October 1). States can set own net neutrality rules, court says. &lt;nowiki&gt;https://www.cnet.com/news/net-neutrality-court-ruling-states-can-set-own-rules/&lt;/nowiki&gt;&lt;/ref&gt;

2019 - 29 States and Puerto Rico introduced Legislation regarding Net Neutrality&lt;ref name=&quot;:5&quot;&gt;Morton (2021 Dec 21) Net Neutrality 2019 Legislation. National Conference of State Legislatures, &lt;nowiki&gt;https://www.ncsl.org/research/telecommunications-and-information-technology/net-neutrality-2021-legislation.aspx&lt;/nowiki&gt;&lt;/ref&gt;

May 2019 - Colorado passes SB 78, Prohibits ISPs from profiting from certain practices.&lt;ref name=&quot;:5&quot; /&gt;

2020 - 12 states, Puerto Rico, and Washington DC introduce legislation regarding Net Neutrality.&lt;ref name=&quot;:6&quot;&gt;Morton (2021 Jan 19) Net Neutrality 2020 Legislation. National Conference of State Legislatures, &lt;nowiki&gt;https://www.ncsl.org/research/telecommunications-and-information-technology/net-neutrality-2021-legislation.aspx&lt;/nowiki&gt;&lt;/ref&gt;

2020 - Washington DC passes B23-664: ISPs are not allowed to block or limit lawful internet traffic for any type of content or services.&lt;ref name=&quot;:6&quot; /&gt;

2021 - 16 States introduced Legislation Regarding Net Neutrality&lt;ref name=&quot;:7&quot;&gt;Morton (2022 May 5) Net Neutrality 2021 Legislation. National Conference of State Legislatures, https://www.ncsl.org/research/telecommunications-and-information-technology/net-neutrality-2021-legislation.aspx&lt;/ref&gt;

February 2021 - Maryland introduced Net Neutrality legislation. The Maryland Net Neutrality Act of 2021 helps to keep the internet open and free. For instance, it prevents fixed Internet service providers and mobile broadband Internet access service providers from blocking specific content, applications, services, or devices, and impairing certain Internet traffic. The Maryland Net Neutrality Act of 2021 also prevents fixed Internet service providers and mobile broadband Internet access service providers from favoring certain Internet traffic over other Internet traffic on certain occasions in order to help all Internet traffic to be treated equally.&lt;ref name=&quot;:7&quot; /&gt;

== Public Appeals ==
To gain support for their platform, ISPs and others against their Title II classification such as Ajit Pai use traditional advertisements, lobbying, comedic appeals, and social media. Comcast continuously publishes paid advertisements on twitter claiming that they support net neutrality and abandonment of Title II classification of ISPs&lt;ref name=&quot;:1&quot;&gt;Litan, R. E. &amp; Singer, H. J. (2010, August 13). Why Business Should Oppose Net Neutrality. Harvard Business Review. &lt;nowiki&gt;https://hbr.org/2010/08/why-business-should-oppose-net-neutrality&lt;/nowiki&gt;&lt;/ref&gt;. ISPs have also spent hundreds of millions of dollars on lobbying since 2003 to gain support for their platforms&lt;ref&gt;Coran. (2017, August 30). Reply comments of the Wireless Internet Service Providers Association. Lerman Senter PLLC. http://www.wispa.org/Portals/37/FCC%20Filings/2017/Restoring%20Internet%20Freedom%20-%20Reply%20Comments%20as%20filed.pdf&lt;/ref&gt;. Ajit Pai also publishes images of himself with his oversized reese's coffee mug to portray himself as a relatable individual to gain support for his platform. 

The groups in support of Title II net neutrality regulations use government owned online forums, comedic appeals, and social media to increase support for their views. John Oliver published multiple full length comedic segments to inform the public about developments surrounding the net neutrality debate and actively encouraged individuals to comment on the FCC forum and contact their representatives to maintain Title II regulations&lt;ref&gt;Battle for the Net. (n.d.). We are Team Internet. [https://www.battleforthenet.com/ https://www.battleforthenet.com]&lt;/ref&gt;. He also bought the domain “gofccyourself.com” to facilitate comments on the FCC page. Google, Facebook, and Netflix also support this viewpoint and dedicate internet pages to outline their views supporting Title II regulations. Some have also formed subreddits to voice their concerns and gain public support with the ultimate aim of having individuals call their representatives to discourage votes against Title II regulations&lt;ref name=&quot;:2&quot;&gt;Google Take Action (2017). We stand together. https://www.google.com/takeaction/action/freeandopen/index.html&lt;/ref&gt;. 
== Claimed Impact ==

A main point of contention for supporters and opposers of net neutrality is economic competition. Supporters believe that net neutrality protects a free and open market, while opposers believe it prevents one. The disparity between these arguments lies in how different groups define internet as either a public utility, or a publicly traded commodity. The freeness and openness of the internet market hinges on this definition. 

=== Opposition ===

A quote by Verizon VP Kathy Grillo sums up the opposing position: “Net Neutrality undermined investment and innovation, and posed a significant threat to the internet’s continued ability to grow and evolve”&lt;ref&gt;Young, R. (2017, November 21). Verizon supports FCC's Restoring Internet Freedom Proposal. Retrieved December 10, 2019, from &lt;nowiki&gt;https://www.verizon.com/about/news/verizon-supports-fccs-restoring-internet-freedom-proposal&lt;/nowiki&gt;.&lt;/ref&gt;. Several Economists and FCC chairman Ajit Pai corroborate this stance. Economists Litan and Singer&lt;ref&gt;Litan, R. E. &amp; Singer, H. J. (2010, August 13). Why Business Should Oppose Net Neutrality. Harvard Business Review. https://hbr.org/2010/08/why-business-should-oppose-net-neutrality&lt;/ref&gt; from the Harvard Business Review state, “Absent net neutrality restrictions, entrepreneurs in their garages would devote significant energies trying to topple Google with the next killer application.” The opposition believes that declaring internet as a public utility diminishes competition in the internet market as well as disincentivizes ISPs from investing in improved network infrastructure&lt;ref name=&quot;:3&quot;&gt;Meunier, F. (2017, December 11). The economics of net neutrality - Paris Innovation Review. Retrieved December 10, 2019, from &lt;nowiki&gt;http://parisinnovationreview.com/articles-en/the-economics-of-net-neutrality&lt;/nowiki&gt;.&lt;/ref&gt;. From the ISPs point of view, and as Francois Meunier states in his article The Economics of Net Neutrality&lt;ref name=&quot;:3&quot; /&gt;: &quot;Internet bandwidth is a resource that is not infinitely expandable and where congestion penalizes all users.&quot; The scarcity of the internet as a resource is a main point in the argument for why internet allocation should be a free market. Of course, a free market also benefits ISPs' profitability as it would allow for profits to be made from both the consumers (internet users) and content producers (Facebook, Google, etc.) on the internet&lt;ref name=&quot;:3&quot; /&gt;. At the moment, profits are only being made from internet consumers in a scheme that depends entirely on users signing up and not at all on how much they use the internet&lt;ref name=&quot;:3&quot; /&gt;. Should the internet be made a completely open market, ISPs would also be able to charge content producers for the traffic to their websites. In an interview with FCC Chairman, Ajit Pai, when asked what his principal concerns with net neutrality laws, he expressed his concern with Title II regulations on ISPs that it could “end up disincentivizing companies from wanting to build out internet access to a lot of parts of the country”&lt;ref&gt;PBS NewsHour. (2017). FCC chair Ajit Pai explains why he wants to scrap net neutrality. PBS. https://www.youtube.com/watch?v=6Q5_oV4JB10&lt;/ref&gt;. The Wireless Internet Service Providers Association (WISPA) has also argues on behalf of large and small ISPs that internet regulation “negatively affects investment and expansion, which in turn limits the ability of currently unserved consumers to gain access to broadband”&lt;ref&gt;Coran. (2017, August 30). Reply comments of the Wireless Internet Service Providers Association. Lerman Senter PLLC. http://www.wispa.org/Portals/37/FCC%20Filings/2017/Restoring%20Internet%20Freedom%20-%20Reply%20Comments%20as%20filed.pdf&lt;/ref&gt;. Since the repeal of Net Neutrality in 2017, however, capital expenditures from ISPs have not increased as promised&lt;ref&gt;Stacey, K. (2019, February 7). Broadband groups cut capital expenditure despite net neutrality win. Retrieved December 10, 2019, from &lt;nowiki&gt;https://www.ft.com/content/81576d02-2a25-11e9-a5ab-ff8ef2b976c7&lt;/nowiki&gt;.&lt;/ref&gt;.        

A smart city's foundation is formed on the basis of high speed internet. The automation and connectivity of a smart city supposedly induces costs and creates an efficient environment. Immense realtime data collection is needed for a smart city to operate. This brings the involvement of 5G technology. 5G together with IOT technology, must serve as the underlying infrastructure that ties the technologies of a smart city together &lt;ref name=&quot;:4&quot;&gt;Kim, S. Y., Jeon, S. J., &amp; Kwon, H. Y. (2020, June 1). ''Smart city, net neutrality, and antitrust: Findings from Korea: The 21st Annual International Conference on Digital Government Research''. &lt;nowiki&gt;https://dl.acm.org/doi/fullHtml/10.1145/3396956.3396990&lt;/nowiki&gt; &lt;/ref&gt;. This brings controversy on the principles of net neutrality.  Currently, internet traffic is dominated by Over-the-top(OTT) service providers like Google, Youtube and Netflix&lt;ref name=&quot;:4&quot; /&gt;. With 5G coming to play, internet traffic sovereignty would be worsened. The question comes down to whether these service providers should be charged for the services they offer over a 5G network&lt;ref name=&quot;:4&quot; /&gt;. From a cost perspective, ISPs might be opposed to smart cities with the uncertainty of how the cost of the infrastructure will be distributed.    


5G technology has some controversy around it in relation to net neutrality. 5G operates on a key feature called network slicing. Network slicing is the ability to create a variety of network architecture that can deliver information based on customer needs&lt;ref&gt;Burke, J. (2022, May 5). ''What is network slicing and how does it work in 5G?'' WhatIs.com. &lt;nowiki&gt;https://www.techtarget.com/whatis/definition/network-slicing&lt;/nowiki&gt; &lt;/ref&gt;. This means 5G is able to control internet traffic and this leads to how charging for the use of 5G networks can clash with the principle of net neutrality. 5G technology might have to prioritize certain types of traffic, like high bandwidth data streams, in order to operate with high performance which can violate some net neutrality principles. However, 5G technology is still in its early stages of development, it's hard to tell how net neutrality laws will be in effect.     
=== Support ===

The manifest view of the supporters of Net Neutrality is that it promotes a free and open market where all organizations have equal opportunity to compete via the internet. The latent supporting view is that no one wants to potentially pay more for internet or have to deal with varying network speeds. Due to large bandwidth requirements video producers will likely pay the highest premiums for the proportions of bandwidth that they use. In fact, Netflix was the first to feel the financial burden of their video streaming services in 2014 when Comcast slowed their connection speeds and forced them to pay extra for more bandwidth&lt;ref&gt;Lee, T. B. (2019, April 24). Comcast's deal with Netflix makes network neutrality obsolete. Retrieved December 10, 2019, from &lt;nowiki&gt;https://www.washingtonpost.com/news/the-switch/wp/2014/02/23/comcasts-deal-with-netflix-makes-network-neutrality-obsolete/&lt;/nowiki&gt;.&lt;/ref&gt;. At this time, Netflix's share of internet traffic was as high as 34.89% during peak evening hours&lt;ref&gt;Luckerson, V. (2014, November 20). Netflix Is Now a Whopping One-Third of Peak Internet Traffic. Retrieved December 10, 2019, from &lt;nowiki&gt;https://time.com/3597369/netflix-internet-traffic-share/&lt;/nowiki&gt;.&lt;/ref&gt;. Organizations like Battle for the Net have rallied members of the public to fight to protect the Title II regulations in ISPs. They fear that ISPs will &quot;[throttle] Internet speeds and [impose] unfair fees&quot; on consumers and businesses&lt;ref&gt;Battle for the Net. (n.d.). The fight for net neutrality is back. Retrieved December 10, 2019, from &lt;nowiki&gt;https://www.battleforthenet.com/&lt;/nowiki&gt;.&lt;/ref&gt;. In a public statement, Google said that the ability for ISPs to block some services “would threaten the innovation that makes the internet awesome”&lt;ref&gt;Google Take Action (2017). We stand together. https://www.google.com/takeaction/action/freeandopen/index.html&lt;/ref&gt;.


The IoT industry favors net neutrality because devices are able to connect to the internet and communicate with other devices without interference from ISPs. Since IoT devices rely on constant connectivity, net neutrality keep the industry strong. ISPs aren't able to charge extra for certain types of internet traffic so it ensures all IoT devices are treated equally. Without net neutrality, ISPs can favor certain types if devices or services over others which can hinder a competitive and innovative space. With the disappearance of net neutrality, high latency can become an issue with certain IoT devices and services&lt;ref&gt;''How does net neutrality affect the internet of things?'' IoT For All. (2020, June 2).&lt;nowiki&gt;https://www.iotforall.com/net-neutrality-iot-implications&lt;/nowiki&gt;&lt;/ref&gt;. Smaller IoT companies might be lose traction due to bigger companies being favored by ISPs. Net neutrality is important for the IoT because it ensures that all devices have equal access to the internet, and that they are not subject to discriminatory practices by ISPs. This helps to promote innovation and competition in the IoT industry, and ultimately benefits both consumers and businesses.

== By Country ==

=== India ===
On July 12&lt;sup&gt;th&lt;/sup&gt; 2018, the Indian government, particularly the Telecom Commission, passed the “world’s strongest” net neutrality regulations with the intention to bolster small companies and protect India’s inhabitants.&lt;ref&gt;Iyenar, R. (2018). India now has the “world’s strongest” net neutrality rules. Retrieved December 10, 2019, from 2018 website: &lt;nowiki&gt;https://money.cnn.com/2018/07/12/technology/india-net-neutrality-rules-telecom/index.html&lt;/nowiki&gt;&lt;/ref&gt; 

Although nearly two thirds of India do not have access to the internet, the increased accessibility of smart phones has expedited the government's actions on Net Neutrality. The government desires to restrict “any form of discrimination or interference in the treatment of content,” as to ensure millions of Indians are not exploited during the boom of internet access.&lt;ref&gt;Door, M., Bhawan, S., Lal, J., &amp; Marg, N. (2017). ''Recommendations On Net Neutrality''.&lt;/ref&gt; However, ISPs are still allowed to discriminate against “critical&quot; and &quot;specialized services” such as self-driving cars and remote surgery.&lt;ref&gt;Doval, P. (2018). Net neutrality: Internet to remain free and fair in India: Govt approves net neutrality - Times of India. Retrieved December 10, 2019, from Times of India website: &lt;nowiki&gt;https://timesofindia.indiatimes.com/business/india-business/internet-to-remain-free-and-fair-in-india-govt-approves-net-neutrality/articleshow/64948838.cms&lt;/nowiki&gt;&lt;/ref&gt;

This stance was recommended by the Telecom Regulatory Authority of India (TRAI), which was established by the Indian government in 1997 under the Telecom Regulatory Authority of India Act. As of 2015, the opinions, outlined in the Regulatory Framework for Over-the-top (OTT) services, are against Net Neutrality. The TRAI’s initial framework did not reflect the views of the public, and were widely criticized as a result.&lt;ref&gt;Singh, S. (2015). Politicos slam TRAI’s stance on net neutrality - Technology News. Retrieved December 10, 2019, from India Today website: &lt;nowiki&gt;https://www.indiatoday.in/technology/news/story/politicos-raise-concern-over-trais-threatening-consultation-on-net-neutrality-247750-2015-04-08&lt;/nowiki&gt;&lt;/ref&gt; However, after listening to the feedback, TRAI passed the “Prohibition of Discriminatory Tariffs for Data Services Regulations, 2016,” one year later. This prohibition ruled in favor of Net Neutrality and banned ISPs from unfair or discriminatory allocations of data. Since, their recommendations in 2017 and 2018, which have continued to reflect public belief, have led to the successful enforcement of net neutrality nationwide.

=== Canada ===
In Canada, the actions of ISPs and general telecommunications are currently regulated by The Canadian Radio-television and Telecommunications Commission (CRTC), Canada’s federal telecommunications regulatory body. In 2011, the CRTC ruled against Net Neutrality and that ISPs could customize billing per users based on usage.&lt;ref&gt;Telecom Decision CRTC 2011-44 | CRTC. (2011). Retrieved December 10, 2019, from Canadian Radio-television and Telecommunications Commission website: &lt;nowiki&gt;https://crtc.gc.ca/eng/archive/2011/2011-44.htm&lt;/nowiki&gt;&lt;/ref&gt; This ruling was not viewed favorably by the public or the prime minister at the time, who called for a review of the decision.&lt;ref&gt;Chase, S., &amp; Marlow, I. (2011). Harper steps into Web dispute - The Globe and Mail. Retrieved December 10, 2019, from The Globe and Mail website: &lt;nowiki&gt;https://www.theglobeandmail.com/technology/tech-news/harper-steps-into-web-dispute/article565219/&lt;/nowiki&gt;&lt;/ref&gt; However, as of April 2017, the CRTC adopted a partially net neutral policy, promoting freedom of the internet, but allowing ISP’s to differentiate consumers by selling different packages that offer alternative speed rates and monthly data usage. The ruling holds that choosing which content, app, or services to count towards one data cap is strictly prohibited.&lt;ref&gt;CRTC strengthens its commitment to net neutrality, consumer choice and free exchange of ideas by citizens - Canada.ca. (2017). Retrieved December 10, 2019, from Canadian Radio-television and Telecommunications Commission website: &lt;nowiki&gt;https://www.canada.ca/en/radio-television-telecommunications/news/2017/04/crtc_strengthensitscommitmenttonetneutralityconsumerchoiceandfre0.html&lt;/nowiki&gt;&lt;/ref&gt;

Justin Trudeau, the current Prime Minister of Canada, has made his stance clear. He is in support of Net Neutrality, and has revealed his concern with the FCC in the United States, by underscoring net neutrality as something “is essential for small businesses, for consumers.&quot;&lt;ref&gt;Trudeau, J. (2017). Justin Trudeau Is ‘Very Concerned’ With FCC’s Plan to Roll Back Net Neutrality - VICE. Retrieved December 10, 2019, from 2017 website: &lt;nowiki&gt;https://www.vice.com/en_us/article/ywb83y/justin-trudeau-is-very-concerned-with-fcc-plan-to-roll-back-net-neutrality-donald-trump&lt;/nowiki&gt;&lt;/ref&gt; Recent cases have highlighted the increasing Canadian tension regarding this topic. In 2014, Xplornet, a Canadian ISP, used throttling technologies on their users. The CRTC did not penalize them, only asking Xplornet to fix their problems, leading to questions regarding the severity of CRTC's enforcement of Net Neutrality .&lt;ref&gt;Geist, M. (2015). When it comes to net neutrality, Canada’s going at half-throttle: Geist | The Star. Retrieved December 10, 2019, from The Star website: &lt;nowiki&gt;https://www.thestar.com/business/2015/08/07/when-it-comes-to-net-neutrality-canadas-going-at-half-throttle-geist.html&lt;/nowiki&gt;&lt;/ref&gt; Further, in 2017, the CRTC ruled all cellular data used be counted towards a data cap set by the ISP and agreed upon by the consumer. Videotron was not counting music streaming services like Apple Music and Spotify against their data cap. The CRTC believed that treating more-established services with better treatment would disadvantage smaller services.&lt;ref&gt;Jackson, E. (2017). CRTC’s decision on differential pricing bans Videotron’s unlimited music service, data caps still allowed | Financial Post. Retrieved December 10, 2019, from Financial Post website: &lt;nowiki&gt;https://business.financialpost.com/technology/crtcs-new-internet-pricing-rules-ban-videotrons-unlimited-music-service-data-caps-still-allowed&lt;/nowiki&gt;&lt;/ref&gt;

=== European Union ===
The Body of European Regulators for Electronic Communications (BEREC) is a body that assists the European Commission and National Regulators by creating a framework for the regulation of electronic communication. They establish guidelines and advice for the constituent countries of the EU. Its official stance is in favor of the free and fair transfer of information over the internet.&lt;ref&gt;BEREC (2022) Body for European Regulators fro Electronic Communication. What is BEREC (webpage)  https://www.berec.europa.eu/en/berec/what-is-berec&lt;/ref&gt;

Among the countries that comprise the EU, few have enacted laws that address net neutrality. One country that has is the Netherlands. They were the first country in Europe to pass a law in 2012 defending net neutrality. It prevents ISPs from charging extra for services accessed through the internet. The law has been criticized by industry members saying that it will lead to higher prices for everyone and keep customers from picking internet access that suits their needs.&lt;ref&gt;Net neutrality enshrined in Dutch Law (2011) ''The Guardian.'' https://www.theguardian.com/technology/2011/jun/23/netherlands-enshrines-net-neutrality-law&lt;/ref&gt;

The European Union’s net neutrality laws were enacted in EU Regulation 2015/2120.&lt;ref&gt;European Union (2015) ''Official Journal of the European Union''. https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32015R2120&amp;rid=2&lt;/ref&gt; While designed to secure consumers access to open information on the internet, the regulations have long since been criticized by supporters of net neutrality for loopholes. Efforts to amend the regulations have not been successful.&lt;ref&gt;EU net neutrality laws fattally undermined by loopholes, critics say (2015) ''The Guardian.'' https://www.theguardian.com/technology/2015/oct/27/eu-net-neutrality-laws-fatally-undermined-by-loopholes-critics-say&lt;/ref&gt;

== Authoritarian Governments ==


In many countries Net Neutrality is seen as an issue of information and commerce. Opponent’s arguments center around free market and business growth. In other parts of the world, the discussion on Net Neutrality takes on a different tone. Regulation of the internet is no longer a business matter, but a political one.

=== China ===
The People’s Republic of China (PRC) has established the worlds most advanced passive internet content filter.&lt;ref name=&quot;:4&quot;&gt;Lum, Thomas (10 February 2006). &quot;Internet Development and Information Control in the People's Republic of China&quot; (PDF). CRS Report for Congress. Retrieved 4 March 2009.&lt;/ref&gt; The government of China uses moderated internet content to limit access to outside information from entering the country, and to curate the information spread within its borders with the aim of controlling public opinion.&lt;ref name=&quot;:4&quot; /&gt; The system that the PRC has established is often referred to as 'The Great Firewall of China'.

=== Iran ===
The government of Iran is another country that is using its control over the internet to protect its political interests. In 2015, the Ayatollah Khamenei stated that enemies of Iran are attempting to pervert the youth of Iran. Around this time Iran established the Council of Cyberspace, to protect their national interest in cyberspace.&lt;ref&gt;&quot;Iran's Leader urges confronting enemy schemes in cyberspace&quot;. ISNA. 6 September 2016. Archived from the original on 24 November 2020. Retrieved 31 August 2020.&lt;/ref&gt; This protection took the form of heavily restricted content and reduced internet speeds.&lt;ref&gt;Shaheed, Ahmed (7 May 2014). &quot;Layers of Internet Censorship in Iran&quot;. United Nations Special Rapporteur. Archived from the original on 14 May 2014. Retrieved 14 May 2014.&lt;/ref&gt;

== Conclusion ==

Net neutrality prohibits ISPs or other powerful groups from interfering with the flow of information to internet users. Since the early 2000s, net neutrality has rapidly attracted attention. Rulings in the US on net neutrality has swung back and forth over the past years, an indication of the volatility around this topic. Both sides of the debate have spent much time and resources to attract support in the hopes of permanently defining policy in their favor. The internet is the fastest avenue to reach an audience and both sides of the net neutrality debate are using it to gain support. While supporters argue that a free and open internet market is one where every website has equal access to users, the opposing side argues net neutrality prevents a free and open broadband market and inhibits innovation among internet service. As internet connectivity affects more aspects of life including politics and civil matters, transportation and healthcare, the impact of net neutrality grows. A recommendation for further study would be to analyze the social, political, and economic implications of recent legislation. As several countries adopt drastically different approaches to net neutrality, new data should become available regarding the impacts. 

== References ==
&lt;references /&gt;{{BookCat}}

54. “President Biden Announces Key Nominations.” The White House, The United States Government, 26 Oct. 2021, https://www.whitehouse.gov/briefing-room/statements-releases/2021/10/26/president-biden-announces-key-nominations-8/.

55. House Bill 1064 - Maryland. https://www.mgaleg.maryland.gov/2021RS/bills/hb/hb1064F.pdf.</text>
      <sha1>cplsat1s0fb2l6qv3nt2vj7iyxmsixk</sha1>
    </revision>
  </page>
  <page>
    <title>SQLite</title>
    <ns>0</ns>
    <id>396835</id>
    <revision>
      <id>4656182</id>
      <parentid>4001936</parentid>
      <timestamp>2026-08-03T10:30:52Z</timestamp>
      <contributor>
        <username>~2026-43015-58</username>
        <id>3618862</id>
      </contributor>
      <comment>Fix first reference's accessdate error, added a link to first reference book source, bump second reference accessdate</comment>
      <origin>4656182</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2320" sha1="i17a4r4vmusx6qucldafffhw98ltjv4" xml:space="preserve">{{TOC left}}
{{float|right|[[File:SQLite370.svg|link=|alt=SQLite logotype]]}}

'''SQLite''' is a relational database management system contained in a C programming library. In contrast to many other database management systems, SQLite is not a client–server database engine. Rather, it is embedded into the end program.

SQLite is ACID-compliant and implements most of the SQL standard, using a dynamically and weakly typed SQL syntax that does not guarantee the domain integrity.&lt;ref name=&quot;Owens 2006&quot;&gt;{{cite book |last=Owens |first=Michael |year=2006 |chapter=Chapter 4: SQL |editor1-last=Gilmore |editor1-first=Jason |editor2-last=Thomas |editor2-first=Keir |editor2-link=Keir Thomas |title=The Definitive Guide to SQLite |url=https://link.springer.com/book/10.1007/978-1-4302-0172-4 |others=D. Richard Hipp (foreword), Preston Hagar (technical reviewer) |publisher=Apress |page=133 |isbn=978-1-59059-673-9 |accessdate=December 30, 2014}}&lt;/ref&gt;

SQLite is a popular choice as embedded database software for local/client storage in application software such as web browsers. It is arguably the most widely deployed database engine, as it is used today by several widespread browsers, operating systems, and embedded systems (such as mobile phones), among others.&lt;ref&gt;{{cite web |url = https://sqlite.org/mostdeployed.html |title = Most Widely Deployed SQL Database Estimates |publisher = SQLite.org |accessdate = August 3, 2026}}&lt;/ref&gt;&lt;br /&gt;SQLite has bindings to many programming languages.

== Table of Contents ==
{{Book search}}
{{Prerequisite|Structured Query Language}}
{{Print version}}
{{Wikipedia|SQLite}}
: {{stage short|75%}} [[/Introduction/]]
: {{stage short|00%}} [[/Downloading and using/]]
: {{stage short|00%}} [[/SQL standard divergences/]]

=== API Tutorial ===
: {{stage short|00%}} [[/Introductory exercise/]]

=== Command-line tool Reference ===
: {{stage short|00%}} [[/Release3|sqlite3]]
: {{stage short|00%}} [[/sqldiff/]]
: {{stage short|00%}} [[/sqlite3_analyzer/]]

== See also ==
* Wikibook [[Microsoft SQL Server]]
* Wikibook [[MySQL]]
* Wikibook [[Oracle Database]]
* Wikibook [[PostgreSQL]]
* Wikibook [[Structured Query Language]]

== External links ==
* [http://www.sqlitetutorial.net/ SQLite Tutorial]

== References ==
{{Reflist}}

{{shelves|SQL}}
{{alphabetical|S}}
{{status|0%}}</text>
      <sha1>i17a4r4vmusx6qucldafffhw98ltjv4</sha1>
    </revision>
  </page>
  <page>
    <title>Celestia/1.7.0 Changes</title>
    <ns>0</ns>
    <id>413814</id>
    <revision>
      <id>4656083</id>
      <parentid>4316205</parentid>
      <timestamp>2026-08-02T18:05:17Z</timestamp>
      <contributor>
        <username>SevenSpheres</username>
        <id>3275649</id>
      </contributor>
      <comment>update units</comment>
      <origin>4656083</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3818" sha1="7xwjug6kab0ejj27n84fltrrx2fl8q1" xml:space="preserve">List of changes in Celestia 1.7.0 (work in progress, likely outdated except for units).

==Rendering==

* Blackbody star colors are default
* Fading orbits (can be toggled)
* On ringed planets, the side of the rings facing away from the star is in shadow
* &lt;code&gt;LunarLambert&lt;/code&gt; makes objects brighter - [https://github.com/CelestiaProject/Celestia/issues/1131 apparently this is correct?]
* Sprite nebulae fade at a distance
* Visibility of different object types (planets, moons, etc), as well as rings, can be toggled individually
* Stars and planets can be rendered out to a distance of 1 billion light-years (increased from 10 million light-years)

==Info display==

* Dwarf planets and minor moons are shown in the right-click menu of their parent body (they aren't in 1.6.x)
* Temperatures are calculated for circumbinary planets

==Data==

* Updates to most data files, models, and textures
* Default temperatures and bolometric corrections for main-sequence stars updated

==Audio==

* Audio support has been added - [https://celestiaproject.space/forum/viewtopic.php?f=4&amp;t=21811 thread]

==New parameters==

===STC files===

* &lt;code&gt;Temperature&lt;/code&gt; - in degrees Kelvin
* &lt;code&gt;BoloCorrection&lt;/code&gt; - {{w|Bolometric correction}}
* &lt;code&gt;Extinction&lt;/code&gt; - the number of magnitudes by which the star's light is extinguished

====Spectral classes====
* &lt;code&gt;Y&lt;/code&gt; - for Y-class brown dwarfs
* &lt;code&gt;WO&lt;/code&gt; - for Wolf–Rayet stars of the oxygen sequence

===SSC files===

* &lt;code&gt;Mass&lt;/code&gt; - in Earth units
* New albedo parameters. Described in [https://github.com/CelestiaProject/Celestia/issues/833 this issue], although the actual implementation isn't exactly the same as what was suggested.
** &lt;code&gt;BondAlbedo&lt;/code&gt; - {{w|Bond albedo}}
** &lt;code&gt;GeomAlbedo&lt;/code&gt; - {{w|Geometric albedo}}; replaces &lt;code&gt;Albedo&lt;/code&gt;
** &lt;code&gt;Reflectivity&lt;/code&gt; - the visible average global reflectivity
* &lt;code&gt;TempDiscrepancy&lt;/code&gt; - this is added to the calculated equilibrium temperature
* &lt;code&gt;Temperature&lt;/code&gt; - in degrees Kelvin; overrides &lt;code&gt;TempDiscrepancy&lt;/code&gt;
* &lt;code&gt;TailColor&lt;/code&gt; - for comets

===Units===

For many parameters, units can be specified in angle brackets, like this: &lt;code&gt;Radius&lt;rE&gt; 1.1&lt;/code&gt;

====Length====

For e.g. &lt;code&gt;Distance&lt;/code&gt;, &lt;code&gt;Radius&lt;/code&gt;, &lt;code&gt;SemiMajorAxis&lt;/code&gt;

* &lt;code&gt;&lt;cm&gt;&lt;/code&gt; - centimeters
* &lt;code&gt;&lt;m&gt;&lt;/code&gt; - meters
* &lt;code&gt;&lt;km&gt;&lt;/code&gt; - kilometers
* &lt;code&gt;&lt;rE&gt;&lt;/code&gt; - Earth radii
* &lt;code&gt;&lt;rJ&gt;&lt;/code&gt; - Jupiter radii
* &lt;code&gt;&lt;rS&gt;&lt;/code&gt; - solar radii
* &lt;code&gt;&lt;AU&gt;&lt;/code&gt; or &lt;code&gt;&lt;au&gt;&lt;/code&gt; - astronomical units
* &lt;code&gt;&lt;ly&gt;&lt;/code&gt; - light-years
* &lt;code&gt;&lt;pc&gt;&lt;/code&gt; - parsecs
* &lt;code&gt;&lt;kpc&gt;&lt;/code&gt; - kiloparsecs
* &lt;code&gt;&lt;Mpc&gt;&lt;/code&gt; - megaparsecs

====Time====

For e.g. &lt;code&gt;Period&lt;/code&gt;

* &lt;code&gt;&lt;nowiki&gt;&lt;s&gt;&lt;/nowiki&gt;&lt;/code&gt; - seconds
* &lt;code&gt;&lt;min&gt;&lt;/code&gt; - minutes
* &lt;code&gt;&lt;h&gt;&lt;/code&gt; - hours
* &lt;code&gt;&lt;d&gt;&lt;/code&gt; - days
* &lt;code&gt;&lt;y&gt;&lt;/code&gt; - years

====Angle====

For e.g. &lt;code&gt;RA&lt;/code&gt;, &lt;code&gt;Dec&lt;/code&gt;, &lt;code&gt;ArgOfPericenter&lt;/code&gt;

* &lt;code&gt;&lt;mas&gt;&lt;/code&gt; - milliarcseconds
* &lt;code&gt;&lt;arcsec&gt;&lt;/code&gt; - arcseconds
* &lt;code&gt;&lt;arcmin&gt;&lt;/code&gt; - arcminutes
* &lt;code&gt;&lt;deg&gt;&lt;/code&gt; - degrees
* &lt;code&gt;&lt;hRA&gt;&lt;/code&gt; - hours of Right Ascension
* &lt;code&gt;&lt;rad&gt;&lt;/code&gt; - radians

====Mass====

For &lt;code&gt;Mass&lt;/code&gt;

* &lt;code&gt;&lt;kg&gt;&lt;/code&gt; - kilograms
* &lt;code&gt;&lt;mE&gt;&lt;/code&gt; - Earth masses
* &lt;code&gt;&lt;mJ&gt;&lt;/code&gt; - Jupiter masses

Solar mass units weren't added, despite my&lt;ref group=note&gt;SevenSpheres&lt;/ref&gt; suggestion to do so.

===Locations===

New location types can be found [[Celestia/SSC File#Type &quot;string&quot;|here]].

==Scripting==

See [https://celestia.mobi/resources/guide?guide=6F7D2F2A-BD35-924D-D068-2B7E61022445 CEL/CELX Scripting Documentation] on celestia.mobi for new CEL/CELX commands.

==Notes==

{{reflist|group=note}}

{{BookCat}}</text>
      <sha1>7xwjug6kab0ejj27n84fltrrx2fl8q1</sha1>
    </revision>
  </page>
  <page>
    <title>Maxima/Operators</title>
    <ns>0</ns>
    <id>438289</id>
    <revision>
      <id>4656046</id>
      <parentid>4655998</parentid>
      <timestamp>2026-08-02T13:56:24Z</timestamp>
      <contributor>
        <username>Idavidmiller</username>
        <id>3577687</id>
      </contributor>
      <comment>Work in progress. Saving Changes.</comment>
      <origin>4656046</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="17793" sha1="cbfczfcc2u5f2a61nhhbn3fvo2u8tei" xml:space="preserve">== Maxima Operators ==
&lt;blockquote&gt;''&quot;Standards are great! That's why there are so many of them, and they change so often.&quot;''

''&quot;What once was forbidden is now required.&quot;''
– Unknown&lt;/blockquote&gt;

=== Mathematical Notation and Operators ===
Mathematical notation was conceived of by different contributors and adopted over a period of time until the present . Standards are important. They help ensure that efforts are consistent and predictable. But if there are standards for notation, then these tend to be ''de facto'' in the absence of some imposed or adopted contextual guidance. Notation is important as this is the means by which mathematical expressions are composed. 

Much of what is now considered &quot;standard&quot; notation was in use before the advent of computers and programming software. Software such as Maxima that has as its purpose &quot;doing&quot; at least some of what is meant by &quot;mathematics,&quot; must provide the means by which mathematical expressions can be composed. Standard or conventional mathematical notation in general is not well-suited for this purpose.

Hence, there has been the effort to &quot;shoe horn&quot; expressions into a form that is better suited for composing expressions that conforms to software programming syntax, instead of developing software systems that can compose and interpret the full spectrum of existing mathematical expressions, presumably because the former is technically simpler. There has been more success in the form of output expressions in terms of conforming to standard mathematical notation.

Object OperatorsMaxima is mostly about mathematical expressions, and these expressions are composed of operators and atoms. Atoms are relatively the simpler ingredient for use in composing expressions – numerical and string data types, but also identifiers, especially those that are not assigned a value, and hence may be considered variables.

Operators are the ingredient where much of the &quot;heavy lifting&quot; occurs with respect to expression composition, and operators need some means to be expressed. Maxima operators are all some sort of &quot;function&quot; (or in Lisp, a procedure) in the programming language sense of the word. This is important to understand. Even something as simple as the expression of a sum is a based on a function.

For example, consider the Maxima expressions:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i1)	e+3;
(%o1)	e+3

(%i2)	:lisp #$[e+3]$
((MLIST SIMP) ((MPLUS SIMP) 3 $E))
&lt;/syntaxhighlight&gt;
Notice that a sum is simply the Lisp procedure &lt;code&gt;MPLUS&lt;/code&gt;. What is true here for the &lt;code&gt;+&lt;/code&gt; operator is true in general – operators are either implicitly or explicitly a function in the programming sense of the word. For those used to conventional mathematical notation, this fact can take some getting used to.

What this means in practice when composing Maxima expressions is that the form of the input may often not resemble what looks like conventional mathematical notation regardless of how well the output or value of the expressions represents the form of conventional mathematical notation. Maxima user interfaces such as ''wxMaxima'' and ''GNU TeXmacs'' are capable of rendering the output of Maxima expressions in a way that represents conventional mathematical notation quite well.

However, once again, the input expressions in these and similar user interfaces always are explicitly and literally composed of Maxima atoms and operators. There is a sense in which then, Maxima imposes an alternative form of mathematical notation for input purposes. This quite simply put is the current state of affairs with respect to doing what Maxima does using a language and syntax that is compatible with computers. Maxima users have to get used to the fact that, in general, they are in a sense constrained to use a different species of mathematical notation for composing input expressions. Operators are the ingredient where this fact becomes most obvious. 

There is a last subsection of this section that provides some insight into the issue of conventional mathematical notation and mathematical computer software systems such as Maxima. This subsection is included for those that have an interest. 

=== Maxima Operators ===

Maxima operators can be considered as belonging to the same categories as expressions:

* Mathematical operators
* Programming operators
* Object operators 

The technical details for some of these operators are found in sections of this book devoted to each of these categories of expressions.

It is worth repeating that built-in Maxima operators and operators defined in packages are, for better or worse, often referred to as ''functions'' and not ''operators''. This practice can lead to some confusion as there are also user-defined functions in the programming sense of the word, and then there is the mathematical concept of a function. For the sake of clarity and simplicity, in this book, Maxima operators and operators defined in packages are referred to simply as ''operators''.

Having made that point, it should be noted that users can define new operators with specified precedence, &lt;code&gt;remove&lt;/code&gt; or &lt;code&gt;kill&lt;/code&gt; existing operator properties, or redefine the precedence of existing operators. Refer to the Maxima Documentation (section '''9.1 Introduction to operators''') for more information.

The general form of most Maxima operators is: &lt;code&gt;foo (args)&lt;/code&gt; where &lt;code&gt;args&lt;/code&gt; is a comma separated sequence of ''arguments'' – zero, one or many. For example:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i3)	to_lisp (); /* an operator with zero arguments */ 
Type (to-maxima) to restart, ($quit) to quit Maxima.
:LISP-QUIET
NIL

MAXIMA&gt;	(to-maxima) 
Returning to Maxima
(%o3)	true

(%i4)	op ([1,arg]); /* an operator with one argument - a list object */
(%o4)	[

(%i5)	apply(f, [a1, a2, a3]); /* an operator with multiple arguments */
(%o5)	f(a1,a2,a3)

/* A list operator ( [ ) with two operators (op and args) as arguments */ 
(%i6)	[op (%i5), args (%i5)];
(%o6)	[apply,[f,[a1,a2,a3]]]&lt;/syntaxhighlight&gt;The operators &lt;code&gt;op(expr)&lt;/code&gt; and &lt;code&gt;args(expr)&lt;/code&gt; can be useful for checking the &quot;main&quot; operator of expressions and the arguments of expressions.  

+.+  

=== Some Typical Categories, Descriptions and Examples of Maxima Operators ===
Maxima often-used operators include a colon ( &lt;code&gt;:&lt;/code&gt; ) for assignment,  &lt;code&gt;:=&lt;/code&gt; and &lt;code&gt;define()&lt;/code&gt; for function definitions, and &lt;code&gt;block()&lt;/code&gt; for multi-line code. Examples include '''assignments''', '''function definitions''', '''loops''' '''or conditionals, and object expressions''', as exemplified below: [1, 2, 3]

===== Variable Assignment and Basic Math Expression Operators: =====

* &lt;code&gt;a : 5;&lt;/code&gt;  — assigns the value &lt;code&gt;5&lt;/code&gt;  to the name &lt;code&gt;a&lt;/code&gt; using a single colon.
* &lt;code&gt;poly : expand((x + y)^3);&lt;/code&gt; — expands a binomial expression and assigns the value to the name &lt;code&gt;poly&lt;/code&gt;.
* &lt;code&gt;subst(&lt;/code&gt;&lt;code&gt;x = 2, x^2 + y);&lt;/code&gt; — substitutes a value into an algebraic expression. [1, 2, 7]

===== User-Defined Functions and Built-In Operator Expressions: =====

* &lt;code&gt;f(x) := x^2 - 3*x + 2;&lt;/code&gt; — defines a single-line function using the &lt;code&gt;:=&lt;/code&gt; operator.
* &lt;code&gt;integrate(f(x), x, 0, 1);&lt;/code&gt; —  the definite integral of the expression &lt;code&gt;f(x)&lt;/code&gt;  from &lt;code&gt;0&lt;/code&gt; to &lt;code&gt;1&lt;/code&gt;.
* &lt;code&gt;diff(f(x), x, 2);&lt;/code&gt; — calculates the second derivative of &lt;code&gt;f(x)&lt;/code&gt;  with respect to &lt;code&gt;x&lt;/code&gt;. [1, 8, 9, 10]

===== Control Flow and Block Programming Operator Expressions: =====

* &lt;code&gt;if x &gt; 0 then print(&quot;Positive&quot;) else print(&quot;Non-positive&quot;);&lt;/code&gt;— conditional branching expression.
* &lt;code&gt;for i : 1 thru 5 do display(i^2);&lt;/code&gt; — a standard  loop iterating from &lt;code&gt;1&lt;/code&gt; to &lt;code&gt;5&lt;/code&gt;.
* &lt;code&gt;block([s : 0], for i : 1 thru 10 do s : s + i, s);&lt;/code&gt; — a local variable &lt;code&gt;block&lt;/code&gt; operator that sums numbers from &lt;code&gt;1&lt;/code&gt; to &lt;code&gt;10&lt;/code&gt; and returns the final value &lt;code&gt;s&lt;/code&gt; . [1, 2, 3, 11]

===== Object Operator Expressions: =====

* '''Lists''' '''and Sets:''' &lt;code&gt;[1, 2, x, y]&lt;/code&gt; builds a list object, while &lt;code&gt;{a, b, c}&lt;/code&gt; denotes a set object.

* '''Matrices:''' &lt;code&gt;matrix([1, 2], [3, 4])&lt;/code&gt; defines a 2x2 matrix object using nested rows of list objects. [12, 13, 14, 15, 16]


[1] &lt;nowiki&gt;https://mathblog.com/a-10-minute-tutorial-for-solving-math-problems-with-maxima/&lt;/nowiki&gt;

[2] &lt;nowiki&gt;https://docs.stack-assessment.org/en/CAS/Maxima_background/&lt;/nowiki&gt;

[3] &lt;nowiki&gt;https://maxima.sourceforge.io/docs/tutorial/en/gaertner-tutorial-revision/Pages/Programming0002.htm&lt;/nowiki&gt;

[4] &lt;nowiki&gt;https://maxima.sourceforge.io/documentation.html&lt;/nowiki&gt;

[5] &lt;nowiki&gt;https://staff.tu.kielce.pl/sk/media/downloads/pi/pi-maxima-calculus-i.pdf&lt;/nowiki&gt;

[6] &lt;nowiki&gt;http://michel.gosse.free.fr/documentation/fichiers/maxima_sg.pdf&lt;/nowiki&gt;

[7] &lt;nowiki&gt;https://maxima.sourceforge.io/docs/manual/intromax.html&lt;/nowiki&gt;

[8] &lt;nowiki&gt;https://maxima.sourceforge.io/docs/manual/intromax.pdf&lt;/nowiki&gt;

[9] &lt;nowiki&gt;https://medium.com/@bragadeeshs/how-to-navigate-maxima-and-minima-in-machine-learning-optimization-5eee9bc67303&lt;/nowiki&gt;

[10] &lt;nowiki&gt;https://blogs.sas.com/content/sgf/2018/11/13/customize-your-casl-code-with-built-in-and-user-defined-functions/&lt;/nowiki&gt;

[11] &lt;nowiki&gt;https://maths.cnam.fr/Membres/wilk/MathMax/help/Maxima/maxima_6.html&lt;/nowiki&gt;

[12] &lt;nowiki&gt;https://moodle.hft-stuttgart.de/question/type/stack/doc/doc.php/CAS/Maxima_background.md&lt;/nowiki&gt;

[13] &lt;nowiki&gt;https://docs.stack-assessment.org/en/CAS/Maxima_background/&lt;/nowiki&gt;

[14] &lt;nowiki&gt;https://maths.cnam.fr/Membres/wilk/MathMax/help/Maxima/maxima_6.html&lt;/nowiki&gt;

[15] &lt;nowiki&gt;https://maxima.sourceforge.io/docs/manual/Expressions.html&lt;/nowiki&gt;

[16] &lt;nowiki&gt;https://maxima.sourceforge.io/docs/tutorial/en/minimal-maxima.pdf&lt;/nowiki&gt;

=== Some Additional Examples of Maxima Operators ===

==== &lt;u&gt;Mathematical Operators&lt;/u&gt;: ====
&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i7)	subst(x = 2, x^2 + y);
(%o7)	y+4

(%i8)	40^40/100^20;
(%o8)	1208925819614629174706176

(%i9)	factor(%);
(%o9)	2^80

(%i10)	diff((a+2)/(a+x),x,1);
(%o10)	-((a+2)/(x+a)^2)

(%i11)	%,x=2;
(%o11)	-(1/(a+2))

(%i12)	simp:false;
(simp)	false

(%i13)	%e^(%i*%pi)+1=0;
(%o13)	%e^(%i*%pi)+1=0

(%i14)	simp:true;
(simp)	true

(%i15)	'integrate(%e^(-x^2),x);
(%o15)	integrate(%e^(-x^2),x)


(%i16) test(f):=block([u],u:integrate(f,x),ratsimp(f-diff(u,x)))
(%o16)	test(f):=block([u],u:integrate(f,x),ratsimp(f-'diff(u,x)))

(%i17) test(sin(x))
(%o17)	0

(%i18) test(1/(1+x))
(%o18)	0

(%i19) test(1/(1+x^2))
(%o19)	0

(%i20) integrate(sin(x)^3,x)
(%o20)	cos(x)^3/3-cos(x)

(%i21) kill(q)$

(%i22) integrate(%e^x/(%e^x+2),x)
(%o22)	log(%e^x+2)

(%i23) integrate(1/(x*log(x)),x)
(%o23)	log(log(x))

(%i24) integrate(sin(2*x+3),x)
(%o24)	-(cos(2*x+3)/2)

(%i25) integrate(%e^x*erf(x),x)
(%o25)	%e^x*erf(x)-%e^(1/4)*erf(x-1/2)

(%i26) integrate(x/(x^3+1),x)
(%o26)	log(x^2-x+1)/6+atan((2*x-1)/sqrt(3))/sqrt(3)-log(x+1)/3

(%i27) diff(%,x)
(%o27)	2/(3*((2*x-1)^2/3+1))+(2*x-1)/(6*(x^2-x+1))-1/(3*(x+1))

(%i28) ratsimp(%)
(%o28)	x/(x^3+1)

(%i29) integrate(x^(5/4)/(x+1)^(5/2),x,0,inf)
(%o29)	beta(1/4,9/4)

(%i30) gradef(q(x),sin(x^2))
(%o30)	q(x)

(%i31) diff(log(q(r(x))),x)
(%o31)	(('diff(r(x),x))*sin(r(x)^2))/q(r(x))

(%i32) integrate(%,x)
(%o32)	log(q(r(x)))

&lt;/syntaxhighlight&gt;

==== &lt;u&gt;Programming Operators&lt;/u&gt;: ====
&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i33)	for c:2 next 3*c thru 20 do display (c)$
c=2
c=6
c=18

(%i34)	for i:1 thru 10 do if i=3 then return(i);
(%o34)	3

(%i35)	t:0$

(%i36)	for i:1 while i &lt;= 15 do t:2*t+i;
(%o36)	done

(%i37)	t;
(%o37)	65519

(%i38) fib[n]:=if n=1 or n=2 then 1 else fib[n-1]+fib[n-2];
(%o38) fib[n]:=if n=1 or n=2 then 1 else fib[n-1]+fib[n-2]

(%i38) fib[1]+fib[2];
(%o38) 2

(%i39) fib[3];
(%o39) 2

(%i40) fib[5];
(%o40) 5

(%i41) eta(mu,nu):=if mu=nu then mu else (if mu&gt;nu then mu-nu else mu+nu);
(%o41) eta(mu,nu):=if mu=nu then mu else if mu&gt;nu then mu-nu else mu+nu

(%i42) eta(5,6);
(%o42) 11

(%i43) eta(eta(7,7),eta(1,2));
(%o43) 4

(%i44) if not 5 &gt;= 2 and 6 &lt;= 5 or 4+1 &gt; 3 then a else b;
(%o44) a

&lt;/syntaxhighlight&gt;

==== &lt;u&gt;Object Operators&lt;/u&gt;: ====
&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
/* List Objects */

(%i1)	my_list: [1, 2, 3, 4, 5];
(my_list)	[1,2,3,4,5]

(%i2)	op(my_list);
(%o2)	&quot;[&quot;

(%i3)	p:[1,1,2,x^2];
(p)	[1,1,2,x^2]

(%i4)	args(p);
(%o4)	[1,1,2,x^2]

(%i5)	nested: [1, [2, 3], [4, [5, 6]]];
(nested)	[1,[2,3],[4,[5,6]]]

(%i7)	nested[3];
(%o7)	[4,[5,6]]

(%i8)	op(%);
(%o8)	&quot;[&quot;

(%i9)	first(my_list);
(%o9)	1

(%i10)	third(my_list);
(%o10)	3

(%i11)	last(my_list);
(%o11)	5

(%i12)	L: create_list(i * x, x, [a, b, c], i, [1, 2, 3, 4]);
(L)	[a,2*a,3*a,4*a,b,2*b,3*b,4*b,c,2*c,3*c,4*c]

(%i13)	apply(&quot;+&quot;, [1, 2, 3]);
(%o13)	6

(%i17)	args('apply(&quot;+&quot;, [1, 2, 3]));
(%o17)	[&quot;+&quot;,[1,2,3]]

(%i18)	%[2];
(%o18)	[1,2,3]

(%i19)	A(s):=(3*sqrt(3)/2)*s^2$

(%i20)	map(A,my_list);
(%o20)	[3^(3/2)/2,2*3^(3/2),3^(7/2)/2,8*3^(3/2),(25*3^(3/2))/2]
&lt;/syntaxhighlight&gt;

Official documentation and guides for operators are available through the Maxima Manual and the Maxima SourceForge Documentation Hub. [4, 5, 6]

=== Some Information Related to Mathematical Notation ===
There is no single, universal standard that dictates mathematical notation across all branches of math. Instead, notation varies by discipline, publisher, and sub-field. There are widely accepted conventions and formal frameworks that serve as references. The general topic of mathematical notation is beyond the scope of this book. However, mathematical notation does have some relevance in the context of Maxima as a computer algebra system.

Stephen Wolfram’s perspective in ''Mathematical Notation: Past and Future'' traces how symbols evolved from static, human-readable shorthand into active, executable computational language. The historical development moved from additive numerals and natural language prose toward structured operators and variables, while the future shifts toward programmatic, interactive, and &quot;computable&quot; expressions. [1, 2, 3, 4]

===== &lt;u&gt;The Past of Mathematical Notation&lt;/u&gt;: =====
* '''Evolution of Symbols:''' Early counting relied on unary notches and additive systems (like Egyptian hieroglyphs), eventually shifting to Hindu-Arabic base-10 positional numerals.
* '''Introduction of Operators:''' Algebraic variables, plus/minus signs, and calculus notations (such as Leibniz's &lt;math display=&quot;inline&quot;&gt;\operatorname{d}\!y/\operatorname{d}\!x

&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\int&lt;/math&gt; ) emerged primarily during the 16th and 17th centuries to replace cumbersome natural language descriptions.
* '''Standardization Limits:''' Traditional notation worked well for manual formula writing, but lacked any native capability to generalize into automated, multi-step computations or algorithmic processes. [3, 7]

===== &lt;u&gt;The Future of Mathematical Notation:&lt;/u&gt; =====
* '''Computational Language:''' Transitioning from passive text on paper to active, uniform symbolic structures.
* '''Programmatic Models:''' Replacing traditional passive equations with active programs capable of executing models across physics, biology, and social sciences.
* '''Universal Access:''' Utilizing interactive, graphical, and automated systems to democratize complex technical thinking much like mass literacy changed society centuries ago. [1, 4]


[1] &lt;nowiki&gt;https://www.stephenwolfram.com/publications/mathematical-notation-past-future/&lt;/nowiki&gt;

[2] &lt;nowiki&gt;https://lukegilson.co/2020/04/05/quick-notes-on-wolframs-mathematic-notation-past-and-future/&lt;/nowiki&gt;

[3] &lt;nowiki&gt;https://www.wolframscience.com/nks/notes-12-10--mathematical-notation/&lt;/nowiki&gt;

[4] &lt;nowiki&gt;https://writings.stephenwolfram.com/2020/10/our-mission-and-the-opportunity-of-artifacts-from-the-future/&lt;/nowiki&gt;

[5] &lt;nowiki&gt;https://library.wolfram.com/infocenter/Demos/4952/&lt;/nowiki&gt;

[6] &lt;nowiki&gt;https://writings.stephenwolfram.com/2013/05/dropping-in-on-gottfried-leibniz/&lt;/nowiki&gt;

[7] &lt;nowiki&gt;https://sites.math.rutgers.edu/~zeilberg/Opinion64.html&lt;/nowiki&gt;

[8] &lt;nowiki&gt;https://physicsworld.com/a/exploring-the-computational-universe-with-stephen-wolfram/&lt;/nowiki&gt;
'''The Future of Notation:''' Read Stephen Wolfram's ''Mathematical Notation: Past and Future'' to learn how the history of notation shapes modern computation. [1]&lt;blockquote&gt;
''&quot;Now I have to tell you that I had always assumed that mathematical notation was too haphazard to be used as any kind of thing that a computer could reasonably interpret in a rigorous way. But at the beginning of the 1990s we got interested in making Mathematica be able to interact with mathematical notation. And so we realized that we really had to figure out what was going on with mathematical notation.''

''Neil Soiffer had spent quite a number of years working on editing and interpreting mathematical notation, and when he joined our company in 1991, he started trying to convince me that one really could work with mathematical notation in a reasonable way, for both output and input.''

''The output side was pretty straightforward: after all, TROFF and TeX already did a moderately good job with that.''

''The issue was input.''

''Well, actually, one already learned something from output. One learned that at least at some level, a lot of mathematical notation could be represented in some kind of context-free form. Because one knew that in TeX, for instance, one could set things up in a tree of nested boxes.''

''But how about input? Well, one of the biggest things was something that always comes up in parsing: if you have a string of text, with operands and operators, how do you tell what groups with what?&quot;&lt;br /&gt;''

– Stephen Wolfram&lt;/blockquote&gt;{{Bookcat}}
{{Status|0%}}</text>
      <sha1>cbfczfcc2u5f2a61nhhbn3fvo2u8tei</sha1>
    </revision>
    <revision>
      <id>4656137</id>
      <parentid>4656046</parentid>
      <timestamp>2026-08-02T23:12:15Z</timestamp>
      <contributor>
        <username>Idavidmiller</username>
        <id>3577687</id>
      </contributor>
      <comment>Work in progress. Saving Changes.</comment>
      <origin>4656137</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="18949" sha1="et9ttfk83sj2f5x6wgd0rphzikq6cot" xml:space="preserve">== Maxima Operators ==
&lt;blockquote&gt;''&quot;Standards are great! That's why there are so many of them, and they change so often.&quot;''

''&quot;What once was forbidden is now required.&quot;''
– Unknown&lt;/blockquote&gt;

=== Mathematical Notation and Operators ===
Mathematical notation was conceived of by different contributors and adopted over a period of time until the present . Standards are important. They help ensure that efforts are consistent and predictable. But if there are standards for notation, then these tend to be ''de facto'' in the absence of some imposed or adopted contextual guidance. Notation is important as this is the means by which mathematical expressions are composed. 

Much of what is now considered &quot;standard&quot; notation was in use before the advent of computers and programming software. Software such as Maxima that has as its purpose &quot;doing&quot; at least some of what is meant by &quot;mathematics,&quot; must provide the means by which mathematical expressions can be composed. Standard or conventional mathematical notation in general is not well-suited for this purpose.

Hence, there has been the effort to &quot;shoe horn&quot; expressions into a form that is better suited for composing expressions that conforms to software programming syntax, instead of developing software systems that can compose and interpret the full spectrum of existing mathematical expressions, presumably because the former is technically simpler. There has been more success in the form of output expressions in terms of conforming to standard mathematical notation.

Object OperatorsMaxima is mostly about mathematical expressions, and these expressions are composed of operators and atoms. Atoms are relatively the simpler ingredient for use in composing expressions – numerical and string data types, but also identifiers, especially those that are not assigned a value, and hence may be considered variables.

Operators are the ingredient where much of the &quot;heavy lifting&quot; occurs with respect to expression composition, and operators need some means to be expressed. Maxima operators are all some sort of &quot;function&quot; (or in Lisp, a procedure) in the programming language sense of the word. This is important to understand. Even something as simple as the expression of a sum is a based on a function.

For example, consider the Maxima expressions:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i1)	e+3;
(%o1)	e+3

(%i2)	:lisp #$[e+3]$
((MLIST SIMP) ((MPLUS SIMP) 3 $E))
&lt;/syntaxhighlight&gt;
Notice that a sum is simply the Lisp procedure &lt;code&gt;MPLUS&lt;/code&gt;. What is true here for the &lt;code&gt;+&lt;/code&gt; operator is true in general – operators are either implicitly or explicitly a function in the programming sense of the word. For those used to conventional mathematical notation, this fact can take some getting used to.

What this means in practice when composing Maxima expressions is that the form of the input may often not resemble what looks like conventional mathematical notation regardless of how well the output or value of the expressions represents the form of conventional mathematical notation. Maxima user interfaces such as ''wxMaxima'' and ''GNU TeXmacs'' are capable of rendering the output of Maxima expressions in a way that represents conventional mathematical notation quite well.

However, once again, the input expressions in these and similar user interfaces always are explicitly and literally composed of Maxima atoms and operators. There is a sense in which then, Maxima imposes an alternative form of mathematical notation for input purposes. This quite simply put is the current state of affairs with respect to doing what Maxima does using a language and syntax that is compatible with computers. Maxima users have to get used to the fact that, in general, they are in a sense constrained to use a different species of mathematical notation for composing input expressions. Operators are the ingredient where this fact becomes most obvious. 

There is a last subsection of this section that provides some insight into the issue of conventional mathematical notation and mathematical computer software systems such as Maxima. This subsection is included for those that have an interest. 

=== Maxima Operators ===

Maxima operators can be considered as belonging to the same categories as expressions:

* Mathematical operators
* Programming operators
* Object operators 

The technical details for some of these operators are found in sections of this book devoted to each of these categories of expressions.

It is worth repeating that built-in Maxima operators and operators defined in packages are, for better or worse, often referred to as ''functions'' and not ''operators''. This practice can lead to some confusion as there are also user-defined functions in the programming sense of the word, and then there is the mathematical concept of a function. For the sake of clarity and simplicity, in this book, Maxima operators and operators defined in packages are referred to simply as ''operators''.

Having made that point, it should be noted that users can define new operators with specified precedence, &lt;code&gt;remove&lt;/code&gt; or &lt;code&gt;kill&lt;/code&gt; existing operator properties, or redefine the precedence of existing operators. Refer to the Maxima Documentation (section '''9.1 Introduction to operators''') for more information.

The general form of most Maxima operators is: &lt;code&gt;foo (args)&lt;/code&gt; where &lt;code&gt;args&lt;/code&gt; is a comma separated sequence of ''arguments'' – zero, one or many. For example:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i3)	to_lisp (); /* an operator with zero arguments */ 
Type (to-maxima) to restart, ($quit) to quit Maxima.
:LISP-QUIET
NIL

MAXIMA&gt;	(to-maxima) 
Returning to Maxima
(%o3)	true

(%i4)	op ([1,arg]); /* an operator with one argument - a list object */
(%o4)	[

(%i5)	apply(f, [a1, a2, a3]); /* an operator with multiple arguments */
(%o5)	f(a1,a2,a3)

/* A list operator ( [ ) with two operators (op and args) as arguments */ 
(%i6)	[op (%i5), args (%i5)];
(%o6)	[apply,[f,[a1,a2,a3]]]&lt;/syntaxhighlight&gt;The operators &lt;code&gt;op(expr)&lt;/code&gt; and &lt;code&gt;args(expr)&lt;/code&gt; can be useful for checking the &quot;main&quot; operator of expressions and the arguments of expressions.  

+.+  

=== Some Typical Categories, Descriptions and Examples of Maxima Operators ===
Maxima often-used operators include a colon ( &lt;code&gt;:&lt;/code&gt; ) for assignment,  &lt;code&gt;:=&lt;/code&gt; and &lt;code&gt;define()&lt;/code&gt; for function definitions, and &lt;code&gt;block()&lt;/code&gt; for multi-line code. Examples include '''assignments''', '''function definitions''', '''loops''' '''or conditionals, and object expressions''', as exemplified below: [1, 2, 3]

===== Variable Assignment and Basic Math Expression Operators: =====

* &lt;code&gt;a : 5;&lt;/code&gt;  — assigns the value &lt;code&gt;5&lt;/code&gt;  to the name &lt;code&gt;a&lt;/code&gt; using a single colon.
* &lt;code&gt;poly : expand((x + y)^3);&lt;/code&gt; — expands a binomial expression and assigns the value to the name &lt;code&gt;poly&lt;/code&gt;.
* &lt;code&gt;subst(&lt;/code&gt;&lt;code&gt;x = 2, x^2 + y);&lt;/code&gt; — substitutes a value into an algebraic expression. [1, 2, 7]

===== User-Defined Functions and Built-In Operator Expressions: =====

* &lt;code&gt;f(x) := x^2 - 3*x + 2;&lt;/code&gt; — defines a single-line function using the &lt;code&gt;:=&lt;/code&gt; operator.
* &lt;code&gt;integrate(f(x), x, 0, 1);&lt;/code&gt; —  the definite integral of the expression &lt;code&gt;f(x)&lt;/code&gt;  from &lt;code&gt;0&lt;/code&gt; to &lt;code&gt;1&lt;/code&gt;.
* &lt;code&gt;diff(f(x), x, 2);&lt;/code&gt; — calculates the second derivative of &lt;code&gt;f(x)&lt;/code&gt;  with respect to &lt;code&gt;x&lt;/code&gt;. [1, 8, 9, 10]

===== Control Flow and Block Programming Operator Expressions: =====

* &lt;code&gt;if x &gt; 0 then print(&quot;Positive&quot;) else print(&quot;Non-positive&quot;);&lt;/code&gt;— conditional branching expression.
* &lt;code&gt;for i : 1 thru 5 do display(i^2);&lt;/code&gt; — a standard  loop iterating from &lt;code&gt;1&lt;/code&gt; to &lt;code&gt;5&lt;/code&gt;.
* &lt;code&gt;block([s : 0], for i : 1 thru 10 do s : s + i, s);&lt;/code&gt; — a local variable &lt;code&gt;block&lt;/code&gt; operator that sums numbers from &lt;code&gt;1&lt;/code&gt; to &lt;code&gt;10&lt;/code&gt; and returns the final value &lt;code&gt;s&lt;/code&gt; . [1, 2, 3, 11]

===== Object Operator Expressions: =====

* '''Lists''' '''and Sets:''' &lt;code&gt;[1, 2, x, y]&lt;/code&gt; builds a list object, while &lt;code&gt;{a, b, c}&lt;/code&gt; denotes a set object.

* '''Matrices:''' &lt;code&gt;matrix([1, 2], [3, 4])&lt;/code&gt; defines a 2x2 matrix object using nested rows of list objects. [12, 13, 14, 15, 16]


[1] &lt;nowiki&gt;https://mathblog.com/a-10-minute-tutorial-for-solving-math-problems-with-maxima/&lt;/nowiki&gt;

[2] &lt;nowiki&gt;https://docs.stack-assessment.org/en/CAS/Maxima_background/&lt;/nowiki&gt;

[3] &lt;nowiki&gt;https://maxima.sourceforge.io/docs/tutorial/en/gaertner-tutorial-revision/Pages/Programming0002.htm&lt;/nowiki&gt;

[4] &lt;nowiki&gt;https://maxima.sourceforge.io/documentation.html&lt;/nowiki&gt;

[5] &lt;nowiki&gt;https://staff.tu.kielce.pl/sk/media/downloads/pi/pi-maxima-calculus-i.pdf&lt;/nowiki&gt;

[6] &lt;nowiki&gt;http://michel.gosse.free.fr/documentation/fichiers/maxima_sg.pdf&lt;/nowiki&gt;

[7] &lt;nowiki&gt;https://maxima.sourceforge.io/docs/manual/intromax.html&lt;/nowiki&gt;

[8] &lt;nowiki&gt;https://maxima.sourceforge.io/docs/manual/intromax.pdf&lt;/nowiki&gt;

[9] &lt;nowiki&gt;https://medium.com/@bragadeeshs/how-to-navigate-maxima-and-minima-in-machine-learning-optimization-5eee9bc67303&lt;/nowiki&gt;

[10] &lt;nowiki&gt;https://blogs.sas.com/content/sgf/2018/11/13/customize-your-casl-code-with-built-in-and-user-defined-functions/&lt;/nowiki&gt;

[11] &lt;nowiki&gt;https://maths.cnam.fr/Membres/wilk/MathMax/help/Maxima/maxima_6.html&lt;/nowiki&gt;

[12] &lt;nowiki&gt;https://moodle.hft-stuttgart.de/question/type/stack/doc/doc.php/CAS/Maxima_background.md&lt;/nowiki&gt;

[13] &lt;nowiki&gt;https://docs.stack-assessment.org/en/CAS/Maxima_background/&lt;/nowiki&gt;

[14] &lt;nowiki&gt;https://maths.cnam.fr/Membres/wilk/MathMax/help/Maxima/maxima_6.html&lt;/nowiki&gt;

[15] &lt;nowiki&gt;https://maxima.sourceforge.io/docs/manual/Expressions.html&lt;/nowiki&gt;

[16] &lt;nowiki&gt;https://maxima.sourceforge.io/docs/tutorial/en/minimal-maxima.pdf&lt;/nowiki&gt;

=== Some Additional Examples of Maxima Operators ===

==== &lt;u&gt;Mathematical Operators&lt;/u&gt;: ====
&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i7)	subst(x = 2, x^2 + y);
(%o7)	y+4

(%i8)	40^40/100^20;
(%o8)	1208925819614629174706176

(%i9)	factor(%);
(%o9)	2^80

(%i10)	diff((a+2)/(a+x),x,1);
(%o10)	-((a+2)/(x+a)^2)

(%i11)	%,x=2;
(%o11)	-(1/(a+2))

(%i12)	simp:false;
(simp)	false

(%i13)	%e^(%i*%pi)+1=0;
(%o13)	%e^(%i*%pi)+1=0

(%i14)	simp:true;
(simp)	true

(%i15)	'integrate(%e^(-x^2),x);
(%o15)	integrate(%e^(-x^2),x)


(%i16) test(f):=block([u],u:integrate(f,x),ratsimp(f-diff(u,x)))
(%o16)	test(f):=block([u],u:integrate(f,x),ratsimp(f-'diff(u,x)))

(%i17) test(sin(x))
(%o17)	0

(%i18) test(1/(1+x))
(%o18)	0

(%i19) test(1/(1+x^2))
(%o19)	0

(%i20) integrate(sin(x)^3,x)
(%o20)	cos(x)^3/3-cos(x)

(%i21) kill(q)$

(%i22) integrate(%e^x/(%e^x+2),x)
(%o22)	log(%e^x+2)

(%i23) integrate(1/(x*log(x)),x)
(%o23)	log(log(x))

(%i24) integrate(sin(2*x+3),x)
(%o24)	-(cos(2*x+3)/2)

(%i25) integrate(%e^x*erf(x),x)
(%o25)	%e^x*erf(x)-%e^(1/4)*erf(x-1/2)

(%i26) integrate(x/(x^3+1),x)
(%o26)	log(x^2-x+1)/6+atan((2*x-1)/sqrt(3))/sqrt(3)-log(x+1)/3

(%i27) diff(%,x)
(%o27)	2/(3*((2*x-1)^2/3+1))+(2*x-1)/(6*(x^2-x+1))-1/(3*(x+1))

(%i28) ratsimp(%)
(%o28)	x/(x^3+1)

(%i29) integrate(x^(5/4)/(x+1)^(5/2),x,0,inf)
(%o29)	beta(1/4,9/4)

(%i30) gradef(q(x),sin(x^2))
(%o30)	q(x)

(%i31) diff(log(q(r(x))),x)
(%o31)	(('diff(r(x),x))*sin(r(x)^2))/q(r(x))

(%i32) integrate(%,x)
(%o32)	log(q(r(x)))

&lt;/syntaxhighlight&gt;

==== &lt;u&gt;Programming Operators&lt;/u&gt;: ====
&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i33)	for c:2 next 3*c thru 20 do display (c)$
c=2
c=6
c=18

(%i34)	for i:1 thru 10 do if i=3 then return(i);
(%o34)	3

(%i35)	t:0$

(%i36)	for i:1 while i &lt;= 15 do t:2*t+i;
(%o36)	done

(%i37)	t;
(%o37)	65519

(%i38) fib[n]:=if n=1 or n=2 then 1 else fib[n-1]+fib[n-2];
(%o38) fib[n]:=if n=1 or n=2 then 1 else fib[n-1]+fib[n-2]

(%i38) fib[1]+fib[2];
(%o38) 2

(%i39) fib[3];
(%o39) 2

(%i40) fib[5];
(%o40) 5

(%i41) eta(mu,nu):=if mu=nu then mu else (if mu&gt;nu then mu-nu else mu+nu);
(%o41) eta(mu,nu):=if mu=nu then mu else if mu&gt;nu then mu-nu else mu+nu

(%i42) eta(5,6);
(%o42) 11

(%i43) eta(eta(7,7),eta(1,2));
(%o43) 4

(%i44) if not 5 &gt;= 2 and 6 &lt;= 5 or 4+1 &gt; 3 then a else b;
(%o44) a

&lt;/syntaxhighlight&gt;

==== &lt;u&gt;Object Operators&lt;/u&gt;: ====
&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
/* List Objects */

(%i1)	my_list: [1, 2, 3, 4, 5];
(my_list)	[1,2,3,4,5]

(%i2)	op(my_list);
(%o2)	&quot;[&quot;

(%i3)	p:[1,1,2,x^2];
(p)	[1,1,2,x^2]

(%i4)	args(p);
(%o4)	[1,1,2,x^2]

(%i5)	nested: [1, [2, 3], [4, [5, 6]]];
(nested)	[1,[2,3],[4,[5,6]]]

(%i7)	nested[3];
(%o7)	[4,[5,6]]

(%i8)	op(%);
(%o8)	&quot;[&quot;

(%i9)	first(my_list);
(%o9)	1

(%i10)	third(my_list);
(%o10)	3

(%i11)	last(my_list);
(%o11)	5

(%i12)	L: create_list(i * x, x, [a, b, c], i, [1, 2, 3, 4]);
(L)	[a,2*a,3*a,4*a,b,2*b,3*b,4*b,c,2*c,3*c,4*c]

(%i13)	apply(&quot;+&quot;, [1, 2, 3]);
(%o13)	6

(%i17)	args('apply(&quot;+&quot;, [1, 2, 3]));
(%o17)	[&quot;+&quot;,[1,2,3]]

(%i18)	%[2];
(%o18)	[1,2,3]

(%i19)	A(s):=(3*sqrt(3)/2)*s^2$

(%i20)	map(A,my_list);
(%o20)	[3^(3/2)/2,2*3^(3/2),3^(7/2)/2,8*3^(3/2),(25*3^(3/2))/2]

/* Declared Arrays */

(%i23)	array (y, fixnum, 3);
(%o23)	y
(%i25)	arrayinfo(y);
(%o25)	[complete,1,[3]]
(%i24)	array(M, flonum, 3, 3);
(%o24)	M
(%i26)	arrayinfo(M);
(%o26)	[complete,2,[3,3]]
(%i27)	y[2]: %pi;
(y[2])	%pi
(%i29)	y[3]: %e;
(y[3])	%e
(%i32)	listarray(y);
(%o32)	[0,0,%pi,%e]

/* Hashed (undeclared) Arrays */

(%i33)	a_hashed_array[8] : 998;
(a_hashed_array[8])	998
(%i34)	arrayinfo(a_hashed_array);
(%o34)	[hashed,1,[8]]
 --&gt;	a[sqrt(2)] : 1
(%i35)	listarray(a_hashed_array);
(%o35)	[998]
(%i36)	a_hashed_array[12] : x^2;
(a_hashed_array[12])	x^2
(%i37)	listarray(a_hashed_array);
(%o37)	[998,x^2]
(%i38)	another_hashed_array[3^(1/3)]:1;
(%o38)	1
(%i39)	arrayinfo(another_hashed_array);
(%o39)	[hashed,1,[3^(1/3)]]
(%i41)	subvarp (another_hashed_array[1]);
(%o41)	true
(%i42)	remarray (y,another_hashed_array);
(%o42)	[y,another_hashed_array]
(%i48)	:lisp (defvar $lisparray (make-array '(3 3) :initial-element 0.0))
$LISPARRAY
(%i48)	:lisp (setq $lisparray (make-array '(3 3) :initial-element 0.0))
#2A((0.0 0.0 0.0) (0.0 0.0 0.0) (0.0 0.0 0.0))
(%i48)	arrayinfo(lisparray);
(%o48)	[declared,2,[2,2]]

/* Lisp Arrays */

/* Structures */

&lt;/syntaxhighlight&gt;

Official documentation and guides for operators are available through the Maxima Manual and the Maxima SourceForge Documentation Hub. [4, 5, 6]

=== Some Information Related to Mathematical Notation ===
There is no single, universal standard that dictates mathematical notation across all branches of math. Instead, notation varies by discipline, publisher, and sub-field. There are widely accepted conventions and formal frameworks that serve as references. The general topic of mathematical notation is beyond the scope of this book. However, mathematical notation does have some relevance in the context of Maxima as a computer algebra system.

Stephen Wolfram’s perspective in ''Mathematical Notation: Past and Future'' traces how symbols evolved from static, human-readable shorthand into active, executable computational language. The historical development moved from additive numerals and natural language prose toward structured operators and variables, while the future shifts toward programmatic, interactive, and &quot;computable&quot; expressions. [1, 2, 3, 4]

===== &lt;u&gt;The Past of Mathematical Notation&lt;/u&gt;: =====
* '''Evolution of Symbols:''' Early counting relied on unary notches and additive systems (like Egyptian hieroglyphs), eventually shifting to Hindu-Arabic base-10 positional numerals.
* '''Introduction of Operators:''' Algebraic variables, plus/minus signs, and calculus notations (such as Leibniz's &lt;math display=&quot;inline&quot;&gt;\operatorname{d}\!y/\operatorname{d}\!x

&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\int&lt;/math&gt; ) emerged primarily during the 16th and 17th centuries to replace cumbersome natural language descriptions.
* '''Standardization Limits:''' Traditional notation worked well for manual formula writing, but lacked any native capability to generalize into automated, multi-step computations or algorithmic processes. [3, 7]

===== &lt;u&gt;The Future of Mathematical Notation:&lt;/u&gt; =====
* '''Computational Language:''' Transitioning from passive text on paper to active, uniform symbolic structures.
* '''Programmatic Models:''' Replacing traditional passive equations with active programs capable of executing models across physics, biology, and social sciences.
* '''Universal Access:''' Utilizing interactive, graphical, and automated systems to democratize complex technical thinking much like mass literacy changed society centuries ago. [1, 4]


[1] &lt;nowiki&gt;https://www.stephenwolfram.com/publications/mathematical-notation-past-future/&lt;/nowiki&gt;

[2] &lt;nowiki&gt;https://lukegilson.co/2020/04/05/quick-notes-on-wolframs-mathematic-notation-past-and-future/&lt;/nowiki&gt;

[3] &lt;nowiki&gt;https://www.wolframscience.com/nks/notes-12-10--mathematical-notation/&lt;/nowiki&gt;

[4] &lt;nowiki&gt;https://writings.stephenwolfram.com/2020/10/our-mission-and-the-opportunity-of-artifacts-from-the-future/&lt;/nowiki&gt;

[5] &lt;nowiki&gt;https://library.wolfram.com/infocenter/Demos/4952/&lt;/nowiki&gt;

[6] &lt;nowiki&gt;https://writings.stephenwolfram.com/2013/05/dropping-in-on-gottfried-leibniz/&lt;/nowiki&gt;

[7] &lt;nowiki&gt;https://sites.math.rutgers.edu/~zeilberg/Opinion64.html&lt;/nowiki&gt;

[8] &lt;nowiki&gt;https://physicsworld.com/a/exploring-the-computational-universe-with-stephen-wolfram/&lt;/nowiki&gt;
'''The Future of Notation:''' Read Stephen Wolfram's ''Mathematical Notation: Past and Future'' to learn how the history of notation shapes modern computation. [1]&lt;blockquote&gt;
''&quot;Now I have to tell you that I had always assumed that mathematical notation was too haphazard to be used as any kind of thing that a computer could reasonably interpret in a rigorous way. But at the beginning of the 1990s we got interested in making Mathematica be able to interact with mathematical notation. And so we realized that we really had to figure out what was going on with mathematical notation.''

''Neil Soiffer had spent quite a number of years working on editing and interpreting mathematical notation, and when he joined our company in 1991, he started trying to convince me that one really could work with mathematical notation in a reasonable way, for both output and input.''

''The output side was pretty straightforward: after all, TROFF and TeX already did a moderately good job with that.''

''The issue was input.''

''Well, actually, one already learned something from output. One learned that at least at some level, a lot of mathematical notation could be represented in some kind of context-free form. Because one knew that in TeX, for instance, one could set things up in a tree of nested boxes.''

''But how about input? Well, one of the biggest things was something that always comes up in parsing: if you have a string of text, with operands and operators, how do you tell what groups with what?&quot;&lt;br /&gt;''

– Stephen Wolfram&lt;/blockquote&gt;{{Bookcat}}
{{Status|0%}}</text>
      <sha1>et9ttfk83sj2f5x6wgd0rphzikq6cot</sha1>
    </revision>
    <revision>
      <id>4656139</id>
      <parentid>4656137</parentid>
      <timestamp>2026-08-02T23:52:50Z</timestamp>
      <contributor>
        <username>Idavidmiller</username>
        <id>3577687</id>
      </contributor>
      <comment>Work in progress. Saving Changes.</comment>
      <origin>4656139</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="19409" sha1="ey9p82k47t61nqqqhd8pc3mt1db8qgb" xml:space="preserve">== Maxima Operators ==
&lt;blockquote&gt;''&quot;Standards are great! That's why there are so many of them, and they change so often.&quot;''

''&quot;What once was forbidden is now required.&quot;''
– Unknown&lt;/blockquote&gt;

=== Mathematical Notation and Operators ===
Mathematical notation was conceived of by different contributors and adopted over a period of time until the present . Standards are important. They help ensure that efforts are consistent and predictable. But if there are standards for notation, then these tend to be ''de facto'' in the absence of some imposed or adopted contextual guidance. Notation is important as this is the means by which mathematical expressions are composed. 

Much of what is now considered &quot;standard&quot; notation was in use before the advent of computers and programming software. Software such as Maxima that has as its purpose &quot;doing&quot; at least some of what is meant by &quot;mathematics,&quot; must provide the means by which mathematical expressions can be composed. Standard or conventional mathematical notation in general is not well-suited for this purpose.

Hence, there has been the effort to &quot;shoe horn&quot; expressions into a form that is better suited for composing expressions that conforms to software programming syntax, instead of developing software systems that can compose and interpret the full spectrum of existing mathematical expressions, presumably because the former is technically simpler. There has been more success in the form of output expressions in terms of conforming to standard mathematical notation.

Object OperatorsMaxima is mostly about mathematical expressions, and these expressions are composed of operators and atoms. Atoms are relatively the simpler ingredient for use in composing expressions – numerical and string data types, but also identifiers, especially those that are not assigned a value, and hence may be considered variables.

Operators are the ingredient where much of the &quot;heavy lifting&quot; occurs with respect to expression composition, and operators need some means to be expressed. Maxima operators are all some sort of &quot;function&quot; (or in Lisp, a procedure) in the programming language sense of the word. This is important to understand. Even something as simple as the expression of a sum is a based on a function.

For example, consider the Maxima expressions:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i1)	e+3;
(%o1)	e+3

(%i2)	:lisp #$[e+3]$
((MLIST SIMP) ((MPLUS SIMP) 3 $E))
&lt;/syntaxhighlight&gt;
Notice that a sum is simply the Lisp procedure &lt;code&gt;MPLUS&lt;/code&gt;. What is true here for the &lt;code&gt;+&lt;/code&gt; operator is true in general – operators are either implicitly or explicitly a function in the programming sense of the word. For those used to conventional mathematical notation, this fact can take some getting used to.

What this means in practice when composing Maxima expressions is that the form of the input may often not resemble what looks like conventional mathematical notation regardless of how well the output or value of the expressions represents the form of conventional mathematical notation. Maxima user interfaces such as ''wxMaxima'' and ''GNU TeXmacs'' are capable of rendering the output of Maxima expressions in a way that represents conventional mathematical notation quite well.

However, once again, the input expressions in these and similar user interfaces always are explicitly and literally composed of Maxima atoms and operators. There is a sense in which then, Maxima imposes an alternative form of mathematical notation for input purposes. This quite simply put is the current state of affairs with respect to doing what Maxima does using a language and syntax that is compatible with computers. Maxima users have to get used to the fact that, in general, they are in a sense constrained to use a different species of mathematical notation for composing input expressions. Operators are the ingredient where this fact becomes most obvious. 

There is a last subsection of this section that provides some insight into the issue of conventional mathematical notation and mathematical computer software systems such as Maxima. This subsection is included for those that have an interest. 

=== Maxima Operators ===

Maxima operators can be considered as belonging to the same categories as expressions:

* Mathematical operators
* Programming operators
* Object operators 

The technical details for some of these operators are found in sections of this book devoted to each of these categories of expressions.

It is worth repeating that built-in Maxima operators and operators defined in packages are, for better or worse, often referred to as ''functions'' and not ''operators''. This practice can lead to some confusion as there are also user-defined functions in the programming sense of the word, and then there is the mathematical concept of a function. For the sake of clarity and simplicity, in this book, Maxima operators and operators defined in packages are referred to simply as ''operators''.

Having made that point, it should be noted that users can define new operators with specified precedence, &lt;code&gt;remove&lt;/code&gt; or &lt;code&gt;kill&lt;/code&gt; existing operator properties, or redefine the precedence of existing operators. Refer to the Maxima Documentation (section '''9.1 Introduction to operators''') for more information.

The general form of most Maxima operators is: &lt;code&gt;foo (args)&lt;/code&gt; where &lt;code&gt;args&lt;/code&gt; is a comma separated sequence of ''arguments'' – zero, one or many. For example:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i3)	to_lisp (); /* an operator with zero arguments */ 
Type (to-maxima) to restart, ($quit) to quit Maxima.
:LISP-QUIET
NIL

MAXIMA&gt;	(to-maxima) 
Returning to Maxima
(%o3)	true

(%i4)	op ([1,arg]); /* an operator with one argument - a list object */
(%o4)	[

(%i5)	apply(f, [a1, a2, a3]); /* an operator with multiple arguments */
(%o5)	f(a1,a2,a3)

/* A list operator ( [ ) with two operators (op and args) as arguments */ 
(%i6)	[op (%i5), args (%i5)];
(%o6)	[apply,[f,[a1,a2,a3]]]&lt;/syntaxhighlight&gt;The operators &lt;code&gt;op(expr)&lt;/code&gt; and &lt;code&gt;args(expr)&lt;/code&gt; can be useful for checking the &quot;main&quot; operator of expressions and the arguments of expressions.  

+.+  

=== Some Typical Categories, Descriptions and Examples of Maxima Operators ===
Maxima often-used operators include a colon ( &lt;code&gt;:&lt;/code&gt; ) for assignment,  &lt;code&gt;:=&lt;/code&gt; and &lt;code&gt;define()&lt;/code&gt; for function definitions, and &lt;code&gt;block()&lt;/code&gt; for multi-line code. Examples include '''assignments''', '''function definitions''', '''loops''' '''or conditionals, and object expressions''', as exemplified below: [1, 2, 3]

===== Variable Assignment and Basic Math Expression Operators: =====

* &lt;code&gt;a : 5;&lt;/code&gt;  — assigns the value &lt;code&gt;5&lt;/code&gt;  to the name &lt;code&gt;a&lt;/code&gt; using a single colon.
* &lt;code&gt;poly : expand((x + y)^3);&lt;/code&gt; — expands a binomial expression and assigns the value to the name &lt;code&gt;poly&lt;/code&gt;.
* &lt;code&gt;subst(&lt;/code&gt;&lt;code&gt;x = 2, x^2 + y);&lt;/code&gt; — substitutes a value into an algebraic expression. [1, 2, 7]

===== User-Defined Functions and Built-In Operator Expressions: =====

* &lt;code&gt;f(x) := x^2 - 3*x + 2;&lt;/code&gt; — defines a single-line function using the &lt;code&gt;:=&lt;/code&gt; operator.
* &lt;code&gt;integrate(f(x), x, 0, 1);&lt;/code&gt; —  the definite integral of the expression &lt;code&gt;f(x)&lt;/code&gt;  from &lt;code&gt;0&lt;/code&gt; to &lt;code&gt;1&lt;/code&gt;.
* &lt;code&gt;diff(f(x), x, 2);&lt;/code&gt; — calculates the second derivative of &lt;code&gt;f(x)&lt;/code&gt;  with respect to &lt;code&gt;x&lt;/code&gt;. [1, 8, 9, 10]

===== Control Flow and Block Programming Operator Expressions: =====

* &lt;code&gt;if x &gt; 0 then print(&quot;Positive&quot;) else print(&quot;Non-positive&quot;);&lt;/code&gt;— conditional branching expression.
* &lt;code&gt;for i : 1 thru 5 do display(i^2);&lt;/code&gt; — a standard  loop iterating from &lt;code&gt;1&lt;/code&gt; to &lt;code&gt;5&lt;/code&gt;.
* &lt;code&gt;block([s : 0], for i : 1 thru 10 do s : s + i, s);&lt;/code&gt; — a local variable &lt;code&gt;block&lt;/code&gt; operator that sums numbers from &lt;code&gt;1&lt;/code&gt; to &lt;code&gt;10&lt;/code&gt; and returns the final value &lt;code&gt;s&lt;/code&gt; . [1, 2, 3, 11]

===== Object Operator Expressions: =====

* '''Lists''' '''and Sets:''' &lt;code&gt;[1, 2, x, y]&lt;/code&gt; builds a list object, while &lt;code&gt;{a, b, c}&lt;/code&gt; denotes a set object.

* '''Matrices:''' &lt;code&gt;matrix([1, 2], [3, 4])&lt;/code&gt; defines a 2x2 matrix object using nested rows of list objects. [12, 13, 14, 15, 16]


[1] &lt;nowiki&gt;https://mathblog.com/a-10-minute-tutorial-for-solving-math-problems-with-maxima/&lt;/nowiki&gt;

[2] &lt;nowiki&gt;https://docs.stack-assessment.org/en/CAS/Maxima_background/&lt;/nowiki&gt;

[3] &lt;nowiki&gt;https://maxima.sourceforge.io/docs/tutorial/en/gaertner-tutorial-revision/Pages/Programming0002.htm&lt;/nowiki&gt;

[4] &lt;nowiki&gt;https://maxima.sourceforge.io/documentation.html&lt;/nowiki&gt;

[5] &lt;nowiki&gt;https://staff.tu.kielce.pl/sk/media/downloads/pi/pi-maxima-calculus-i.pdf&lt;/nowiki&gt;

[6] &lt;nowiki&gt;http://michel.gosse.free.fr/documentation/fichiers/maxima_sg.pdf&lt;/nowiki&gt;

[7] &lt;nowiki&gt;https://maxima.sourceforge.io/docs/manual/intromax.html&lt;/nowiki&gt;

[8] &lt;nowiki&gt;https://maxima.sourceforge.io/docs/manual/intromax.pdf&lt;/nowiki&gt;

[9] &lt;nowiki&gt;https://medium.com/@bragadeeshs/how-to-navigate-maxima-and-minima-in-machine-learning-optimization-5eee9bc67303&lt;/nowiki&gt;

[10] &lt;nowiki&gt;https://blogs.sas.com/content/sgf/2018/11/13/customize-your-casl-code-with-built-in-and-user-defined-functions/&lt;/nowiki&gt;

[11] &lt;nowiki&gt;https://maths.cnam.fr/Membres/wilk/MathMax/help/Maxima/maxima_6.html&lt;/nowiki&gt;

[12] &lt;nowiki&gt;https://moodle.hft-stuttgart.de/question/type/stack/doc/doc.php/CAS/Maxima_background.md&lt;/nowiki&gt;

[13] &lt;nowiki&gt;https://docs.stack-assessment.org/en/CAS/Maxima_background/&lt;/nowiki&gt;

[14] &lt;nowiki&gt;https://maths.cnam.fr/Membres/wilk/MathMax/help/Maxima/maxima_6.html&lt;/nowiki&gt;

[15] &lt;nowiki&gt;https://maxima.sourceforge.io/docs/manual/Expressions.html&lt;/nowiki&gt;

[16] &lt;nowiki&gt;https://maxima.sourceforge.io/docs/tutorial/en/minimal-maxima.pdf&lt;/nowiki&gt;

=== Some Additional Examples of Maxima Operators ===

==== &lt;u&gt;Mathematical Operators&lt;/u&gt;: ====
&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i7)	subst(x = 2, x^2 + y);
(%o7)	y+4

(%i8)	40^40/100^20;
(%o8)	1208925819614629174706176

(%i9)	factor(%);
(%o9)	2^80

(%i10)	diff((a+2)/(a+x),x,1);
(%o10)	-((a+2)/(x+a)^2)

(%i11)	%,x=2;
(%o11)	-(1/(a+2))

(%i12)	simp:false;
(simp)	false

(%i13)	%e^(%i*%pi)+1=0;
(%o13)	%e^(%i*%pi)+1=0

(%i14)	simp:true;
(simp)	true

(%i15)	'integrate(%e^(-x^2),x);
(%o15)	integrate(%e^(-x^2),x)


(%i16) test(f):=block([u],u:integrate(f,x),ratsimp(f-diff(u,x)))
(%o16)	test(f):=block([u],u:integrate(f,x),ratsimp(f-'diff(u,x)))

(%i17) test(sin(x))
(%o17)	0

(%i18) test(1/(1+x))
(%o18)	0

(%i19) test(1/(1+x^2))
(%o19)	0

(%i20) integrate(sin(x)^3,x)
(%o20)	cos(x)^3/3-cos(x)

(%i21) kill(q)$

(%i22) integrate(%e^x/(%e^x+2),x)
(%o22)	log(%e^x+2)

(%i23) integrate(1/(x*log(x)),x)
(%o23)	log(log(x))

(%i24) integrate(sin(2*x+3),x)
(%o24)	-(cos(2*x+3)/2)

(%i25) integrate(%e^x*erf(x),x)
(%o25)	%e^x*erf(x)-%e^(1/4)*erf(x-1/2)

(%i26) integrate(x/(x^3+1),x)
(%o26)	log(x^2-x+1)/6+atan((2*x-1)/sqrt(3))/sqrt(3)-log(x+1)/3

(%i27) diff(%,x)
(%o27)	2/(3*((2*x-1)^2/3+1))+(2*x-1)/(6*(x^2-x+1))-1/(3*(x+1))

(%i28) ratsimp(%)
(%o28)	x/(x^3+1)

(%i29) integrate(x^(5/4)/(x+1)^(5/2),x,0,inf)
(%o29)	beta(1/4,9/4)

(%i30) gradef(q(x),sin(x^2))
(%o30)	q(x)

(%i31) diff(log(q(r(x))),x)
(%o31)	(('diff(r(x),x))*sin(r(x)^2))/q(r(x))

(%i32) integrate(%,x)
(%o32)	log(q(r(x)))

&lt;/syntaxhighlight&gt;

==== &lt;u&gt;Programming Operators&lt;/u&gt;: ====
&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i33)	for c:2 next 3*c thru 20 do display (c)$
c=2
c=6
c=18

(%i34)	for i:1 thru 10 do if i=3 then return(i);
(%o34)	3

(%i35)	t:0$

(%i36)	for i:1 while i &lt;= 15 do t:2*t+i;
(%o36)	done

(%i37)	t;
(%o37)	65519

(%i38) fib[n]:=if n=1 or n=2 then 1 else fib[n-1]+fib[n-2];
(%o38) fib[n]:=if n=1 or n=2 then 1 else fib[n-1]+fib[n-2]

(%i38) fib[1]+fib[2];
(%o38) 2

(%i39) fib[3];
(%o39) 2

(%i40) fib[5];
(%o40) 5

(%i41) eta(mu,nu):=if mu=nu then mu else (if mu&gt;nu then mu-nu else mu+nu);
(%o41) eta(mu,nu):=if mu=nu then mu else if mu&gt;nu then mu-nu else mu+nu

(%i42) eta(5,6);
(%o42) 11

(%i43) eta(eta(7,7),eta(1,2));
(%o43) 4

(%i44) if not 5 &gt;= 2 and 6 &lt;= 5 or 4+1 &gt; 3 then a else b;
(%o44) a

&lt;/syntaxhighlight&gt;

==== &lt;u&gt;Object Operators&lt;/u&gt;: ====
&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
/* List Objects */

(%i1)	my_list: [1, 2, 3, 4, 5];
(my_list)	[1,2,3,4,5]

(%i2)	op(my_list);
(%o2)	&quot;[&quot;

(%i3)	p:[1,1,2,x^2];
(p)	[1,1,2,x^2]

(%i4)	args(p);
(%o4)	[1,1,2,x^2]

(%i5)	nested: [1, [2, 3], [4, [5, 6]]];
(nested)	[1,[2,3],[4,[5,6]]]

(%i7)	nested[3];
(%o7)	[4,[5,6]]

(%i8)	op(%);
(%o8)	&quot;[&quot;

(%i9)	first(my_list);
(%o9)	1

(%i10)	third(my_list);
(%o10)	3

(%i11)	last(my_list);
(%o11)	5

(%i12)	L: create_list(i * x, x, [a, b, c], i, [1, 2, 3, 4]);
(L)	[a,2*a,3*a,4*a,b,2*b,3*b,4*b,c,2*c,3*c,4*c]

(%i13)	apply(&quot;+&quot;, [1, 2, 3]);
(%o13)	6

(%i17)	args('apply(&quot;+&quot;, [1, 2, 3]));
(%o17)	[&quot;+&quot;,[1,2,3]]

(%i18)	%[2];
(%o18)	[1,2,3]

(%i19)	A(s):=(3*sqrt(3)/2)*s^2$

(%i20)	map(A,my_list);
(%o20)	[3^(3/2)/2,2*3^(3/2),3^(7/2)/2,8*3^(3/2),(25*3^(3/2))/2]

/* Declared Arrays */

(%i23)	array (y, fixnum, 3);
(%o23)	y
(%i25)	arrayinfo(y);
(%o25)	[complete,1,[3]]
(%i24)	array(M, flonum, 3, 3);
(%o24)	M
(%i26)	arrayinfo(M);
(%o26)	[complete,2,[3,3]]
(%i27)	y[2]: %pi;
(y[2])	%pi
(%i29)	y[3]: %e;
(y[3])	%e
(%i32)	listarray(y);
(%o32)	[0,0,%pi,%e]

/* Hashed (undeclared) Arrays */

(%i33)	a_hashed_array[8] : 998;
(a_hashed_array[8])	998
(%i34)	arrayinfo(a_hashed_array);
(%o34)	[hashed,1,[8]]
 --&gt;	a[sqrt(2)] : 1
(%i35)	listarray(a_hashed_array);
(%o35)	[998]
(%i36)	a_hashed_array[12] : x^2;
(a_hashed_array[12])	x^2
(%i37)	listarray(a_hashed_array);
(%o37)	[998,x^2]
(%i38)	another_hashed_array[3^(1/3)]:1;
(%o38)	1
(%i39)	arrayinfo(another_hashed_array);
(%o39)	[hashed,1,[3^(1/3)]]
(%i41)	subvarp (another_hashed_array[1]);
(%o41)	true
(%i42)	remarray (y,another_hashed_array);
(%o42)	[y,another_hashed_array]
(%i48)	:lisp (defvar $lisparray (make-array '(3 3) :initial-element 0.0))
$LISPARRAY
(%i48)	:lisp (setq $lisparray (make-array '(3 3) :initial-element 0.0))
#2A((0.0 0.0 0.0) (0.0 0.0 0.0) (0.0 0.0 0.0))
(%i48)	arrayinfo(lisparray);
(%o48)	[declared,2,[2,2]]

/* Lisp Arrays */
(%i48)	:lisp (defvar $lisparray (make-array '(3 3) :initial-element 0.0))
$LISPARRAY
(%i48)	:lisp (setq $lisparray (make-array '(3 3) :initial-element 0.0))
#2A((0.0 0.0 0.0) (0.0 0.0 0.0) (0.0 0.0 0.0))
(%i48)	arrayinfo(lisparray);
(%o48)	[declared,2,[2,2]]
(%i49)	:lisp (aref $lisparray 0 0)
0.0
(%i49)	:lisp (aref $lisparray 2 2)
0.0
(%i49)	lisparray[2,2]:77;
(%o49)	77
(%i50)	:lisp (aref $lisparray 2 2)
88
(%i50)	:lisp (setf (aref $lisparray 2 2) 88)
88


/* Structures */

&lt;/syntaxhighlight&gt;

Official documentation and guides for operators are available through the Maxima Manual and the Maxima SourceForge Documentation Hub. [4, 5, 6]

=== Some Information Related to Mathematical Notation ===
There is no single, universal standard that dictates mathematical notation across all branches of math. Instead, notation varies by discipline, publisher, and sub-field. There are widely accepted conventions and formal frameworks that serve as references. The general topic of mathematical notation is beyond the scope of this book. However, mathematical notation does have some relevance in the context of Maxima as a computer algebra system.

Stephen Wolfram’s perspective in ''Mathematical Notation: Past and Future'' traces how symbols evolved from static, human-readable shorthand into active, executable computational language. The historical development moved from additive numerals and natural language prose toward structured operators and variables, while the future shifts toward programmatic, interactive, and &quot;computable&quot; expressions. [1, 2, 3, 4]

===== &lt;u&gt;The Past of Mathematical Notation&lt;/u&gt;: =====
* '''Evolution of Symbols:''' Early counting relied on unary notches and additive systems (like Egyptian hieroglyphs), eventually shifting to Hindu-Arabic base-10 positional numerals.
* '''Introduction of Operators:''' Algebraic variables, plus/minus signs, and calculus notations (such as Leibniz's &lt;math display=&quot;inline&quot;&gt;\operatorname{d}\!y/\operatorname{d}\!x

&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\int&lt;/math&gt; ) emerged primarily during the 16th and 17th centuries to replace cumbersome natural language descriptions.
* '''Standardization Limits:''' Traditional notation worked well for manual formula writing, but lacked any native capability to generalize into automated, multi-step computations or algorithmic processes. [3, 7]

===== &lt;u&gt;The Future of Mathematical Notation:&lt;/u&gt; =====
* '''Computational Language:''' Transitioning from passive text on paper to active, uniform symbolic structures.
* '''Programmatic Models:''' Replacing traditional passive equations with active programs capable of executing models across physics, biology, and social sciences.
* '''Universal Access:''' Utilizing interactive, graphical, and automated systems to democratize complex technical thinking much like mass literacy changed society centuries ago. [1, 4]


[1] &lt;nowiki&gt;https://www.stephenwolfram.com/publications/mathematical-notation-past-future/&lt;/nowiki&gt;

[2] &lt;nowiki&gt;https://lukegilson.co/2020/04/05/quick-notes-on-wolframs-mathematic-notation-past-and-future/&lt;/nowiki&gt;

[3] &lt;nowiki&gt;https://www.wolframscience.com/nks/notes-12-10--mathematical-notation/&lt;/nowiki&gt;

[4] &lt;nowiki&gt;https://writings.stephenwolfram.com/2020/10/our-mission-and-the-opportunity-of-artifacts-from-the-future/&lt;/nowiki&gt;

[5] &lt;nowiki&gt;https://library.wolfram.com/infocenter/Demos/4952/&lt;/nowiki&gt;

[6] &lt;nowiki&gt;https://writings.stephenwolfram.com/2013/05/dropping-in-on-gottfried-leibniz/&lt;/nowiki&gt;

[7] &lt;nowiki&gt;https://sites.math.rutgers.edu/~zeilberg/Opinion64.html&lt;/nowiki&gt;

[8] &lt;nowiki&gt;https://physicsworld.com/a/exploring-the-computational-universe-with-stephen-wolfram/&lt;/nowiki&gt;
'''The Future of Notation:''' Read Stephen Wolfram's ''Mathematical Notation: Past and Future'' to learn how the history of notation shapes modern computation. [1]&lt;blockquote&gt;
''&quot;Now I have to tell you that I had always assumed that mathematical notation was too haphazard to be used as any kind of thing that a computer could reasonably interpret in a rigorous way. But at the beginning of the 1990s we got interested in making Mathematica be able to interact with mathematical notation. And so we realized that we really had to figure out what was going on with mathematical notation.''

''Neil Soiffer had spent quite a number of years working on editing and interpreting mathematical notation, and when he joined our company in 1991, he started trying to convince me that one really could work with mathematical notation in a reasonable way, for both output and input.''

''The output side was pretty straightforward: after all, TROFF and TeX already did a moderately good job with that.''

''The issue was input.''

''Well, actually, one already learned something from output. One learned that at least at some level, a lot of mathematical notation could be represented in some kind of context-free form. Because one knew that in TeX, for instance, one could set things up in a tree of nested boxes.''

''But how about input? Well, one of the biggest things was something that always comes up in parsing: if you have a string of text, with operands and operators, how do you tell what groups with what?&quot;&lt;br /&gt;''

– Stephen Wolfram&lt;/blockquote&gt;{{Bookcat}}
{{Status|0%}}</text>
      <sha1>ey9p82k47t61nqqqhd8pc3mt1db8qgb</sha1>
    </revision>
    <revision>
      <id>4656155</id>
      <parentid>4656139</parentid>
      <timestamp>2026-08-03T02:22:39Z</timestamp>
      <contributor>
        <username>Idavidmiller</username>
        <id>3577687</id>
      </contributor>
      <comment>Work in progress. Saving Changes.</comment>
      <origin>4656155</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="19697" sha1="qel664mjnn42e7xiehytw6hu1ffqtem" xml:space="preserve">== Maxima Operators ==
&lt;blockquote&gt;''&quot;Standards are great! That's why there are so many of them, and they change so often.&quot;''

''&quot;What once was forbidden is now required.&quot;''
– Unknown&lt;/blockquote&gt;

=== Mathematical Notation and Operators ===
Mathematical notation was conceived of by different contributors and adopted over a period of time until the present . Standards are important. They help ensure that efforts are consistent and predictable. But if there are standards for notation, then these tend to be ''de facto'' in the absence of some imposed or adopted contextual guidance. Notation is important as this is the means by which mathematical expressions are composed. 

Much of what is now considered &quot;standard&quot; notation was in use before the advent of computers and programming software. Software such as Maxima that has as its purpose &quot;doing&quot; at least some of what is meant by &quot;mathematics,&quot; must provide the means by which mathematical expressions can be composed. Standard or conventional mathematical notation in general is not well-suited for this purpose.

Hence, there has been the effort to &quot;shoe horn&quot; expressions into a form that is better suited for composing expressions that conforms to software programming syntax, instead of developing software systems that can compose and interpret the full spectrum of existing mathematical expressions, presumably because the former is technically simpler. There has been more success in the form of output expressions in terms of conforming to standard mathematical notation.

Object OperatorsMaxima is mostly about mathematical expressions, and these expressions are composed of operators and atoms. Atoms are relatively the simpler ingredient for use in composing expressions – numerical and string data types, but also identifiers, especially those that are not assigned a value, and hence may be considered variables.

Operators are the ingredient where much of the &quot;heavy lifting&quot; occurs with respect to expression composition, and operators need some means to be expressed. Maxima operators are all some sort of &quot;function&quot; (or in Lisp, a procedure) in the programming language sense of the word. This is important to understand. Even something as simple as the expression of a sum is a based on a function.

For example, consider the Maxima expressions:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i1)	e+3;
(%o1)	e+3

(%i2)	:lisp #$[e+3]$
((MLIST SIMP) ((MPLUS SIMP) 3 $E))
&lt;/syntaxhighlight&gt;
Notice that a sum is simply the Lisp procedure &lt;code&gt;MPLUS&lt;/code&gt;. What is true here for the &lt;code&gt;+&lt;/code&gt; operator is true in general – operators are either implicitly or explicitly a function in the programming sense of the word. For those used to conventional mathematical notation, this fact can take some getting used to.

What this means in practice when composing Maxima expressions is that the form of the input may often not resemble what looks like conventional mathematical notation regardless of how well the output or value of the expressions represents the form of conventional mathematical notation. Maxima user interfaces such as ''wxMaxima'' and ''GNU TeXmacs'' are capable of rendering the output of Maxima expressions in a way that represents conventional mathematical notation quite well.

However, once again, the input expressions in these and similar user interfaces always are explicitly and literally composed of Maxima atoms and operators. There is a sense in which then, Maxima imposes an alternative form of mathematical notation for input purposes. This quite simply put is the current state of affairs with respect to doing what Maxima does using a language and syntax that is compatible with computers. Maxima users have to get used to the fact that, in general, they are in a sense constrained to use a different species of mathematical notation for composing input expressions. Operators are the ingredient where this fact becomes most obvious. 

There is a last subsection of this section that provides some insight into the issue of conventional mathematical notation and mathematical computer software systems such as Maxima. This subsection is included for those that have an interest. 

=== Maxima Operators ===

Maxima operators can be considered as belonging to the same categories as expressions:

* Mathematical operators
* Programming operators
* Object operators 

The technical details for some of these operators are found in sections of this book devoted to each of these categories of expressions.

It is worth repeating that built-in Maxima operators and operators defined in packages are, for better or worse, often referred to as ''functions'' and not ''operators''. This practice can lead to some confusion as there are also user-defined functions in the programming sense of the word, and then there is the mathematical concept of a function. For the sake of clarity and simplicity, in this book, Maxima operators and operators defined in packages are referred to simply as ''operators''.

Having made that point, it should be noted that users can define new operators with specified precedence, &lt;code&gt;remove&lt;/code&gt; or &lt;code&gt;kill&lt;/code&gt; existing operator properties, or redefine the precedence of existing operators. Refer to the Maxima Documentation (section '''9.1 Introduction to operators''') for more information.

The general form of most Maxima operators is: &lt;code&gt;foo (args)&lt;/code&gt; where &lt;code&gt;args&lt;/code&gt; is a comma separated sequence of ''arguments'' – zero, one or many. For example:&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i3)	to_lisp (); /* an operator with zero arguments */ 
Type (to-maxima) to restart, ($quit) to quit Maxima.
:LISP-QUIET
NIL

MAXIMA&gt;	(to-maxima) 
Returning to Maxima
(%o3)	true

(%i4)	op ([1,arg]); /* an operator with one argument - a list object */
(%o4)	[

(%i5)	apply(f, [a1, a2, a3]); /* an operator with multiple arguments */
(%o5)	f(a1,a2,a3)

/* A list operator ( [ ) with two operators (op and args) as arguments */ 
(%i6)	[op (%i5), args (%i5)];
(%o6)	[apply,[f,[a1,a2,a3]]]&lt;/syntaxhighlight&gt;The operators &lt;code&gt;op(expr)&lt;/code&gt; and &lt;code&gt;args(expr)&lt;/code&gt; can be useful for checking the &quot;main&quot; operator of expressions and the arguments of expressions.  

+.+  

=== Some Typical Categories, Descriptions and Examples of Maxima Operators ===
Maxima often-used operators include a colon ( &lt;code&gt;:&lt;/code&gt; ) for assignment,  &lt;code&gt;:=&lt;/code&gt; and &lt;code&gt;define()&lt;/code&gt; for function definitions, and &lt;code&gt;block()&lt;/code&gt; for multi-line code. Examples include '''assignments''', '''function definitions''', '''loops''' '''or conditionals, and object expressions''', as exemplified below: [1, 2, 3]

===== Variable Assignment and Basic Math Expression Operators: =====

* &lt;code&gt;a : 5;&lt;/code&gt;  — assigns the value &lt;code&gt;5&lt;/code&gt;  to the name &lt;code&gt;a&lt;/code&gt; using a single colon.
* &lt;code&gt;poly : expand((x + y)^3);&lt;/code&gt; — expands a binomial expression and assigns the value to the name &lt;code&gt;poly&lt;/code&gt;.
* &lt;code&gt;subst(&lt;/code&gt;&lt;code&gt;x = 2, x^2 + y);&lt;/code&gt; — substitutes a value into an algebraic expression. [1, 2, 7]

===== User-Defined Functions and Built-In Operator Expressions: =====

* &lt;code&gt;f(x) := x^2 - 3*x + 2;&lt;/code&gt; — defines a single-line function using the &lt;code&gt;:=&lt;/code&gt; operator.
* &lt;code&gt;integrate(f(x), x, 0, 1);&lt;/code&gt; —  the definite integral of the expression &lt;code&gt;f(x)&lt;/code&gt;  from &lt;code&gt;0&lt;/code&gt; to &lt;code&gt;1&lt;/code&gt;.
* &lt;code&gt;diff(f(x), x, 2);&lt;/code&gt; — calculates the second derivative of &lt;code&gt;f(x)&lt;/code&gt;  with respect to &lt;code&gt;x&lt;/code&gt;. [1, 8, 9, 10]

===== Control Flow and Block Programming Operator Expressions: =====

* &lt;code&gt;if x &gt; 0 then print(&quot;Positive&quot;) else print(&quot;Non-positive&quot;);&lt;/code&gt;— conditional branching expression.
* &lt;code&gt;for i : 1 thru 5 do display(i^2);&lt;/code&gt; — a standard  loop iterating from &lt;code&gt;1&lt;/code&gt; to &lt;code&gt;5&lt;/code&gt;.
* &lt;code&gt;block([s : 0], for i : 1 thru 10 do s : s + i, s);&lt;/code&gt; — a local variable &lt;code&gt;block&lt;/code&gt; operator that sums numbers from &lt;code&gt;1&lt;/code&gt; to &lt;code&gt;10&lt;/code&gt; and returns the final value &lt;code&gt;s&lt;/code&gt; . [1, 2, 3, 11]

===== Object Operator Expressions: =====

* '''Lists''' '''and Sets:''' &lt;code&gt;[1, 2, x, y]&lt;/code&gt; builds a list object, while &lt;code&gt;{a, b, c}&lt;/code&gt; denotes a set object.

* '''Matrices:''' &lt;code&gt;matrix([1, 2], [3, 4])&lt;/code&gt; defines a 2x2 matrix object using nested rows of list objects. [12, 13, 14, 15, 16]


[1] &lt;nowiki&gt;https://mathblog.com/a-10-minute-tutorial-for-solving-math-problems-with-maxima/&lt;/nowiki&gt;

[2] &lt;nowiki&gt;https://docs.stack-assessment.org/en/CAS/Maxima_background/&lt;/nowiki&gt;

[3] &lt;nowiki&gt;https://maxima.sourceforge.io/docs/tutorial/en/gaertner-tutorial-revision/Pages/Programming0002.htm&lt;/nowiki&gt;

[4] &lt;nowiki&gt;https://maxima.sourceforge.io/documentation.html&lt;/nowiki&gt;

[5] &lt;nowiki&gt;https://staff.tu.kielce.pl/sk/media/downloads/pi/pi-maxima-calculus-i.pdf&lt;/nowiki&gt;

[6] &lt;nowiki&gt;http://michel.gosse.free.fr/documentation/fichiers/maxima_sg.pdf&lt;/nowiki&gt;

[7] &lt;nowiki&gt;https://maxima.sourceforge.io/docs/manual/intromax.html&lt;/nowiki&gt;

[8] &lt;nowiki&gt;https://maxima.sourceforge.io/docs/manual/intromax.pdf&lt;/nowiki&gt;

[9] &lt;nowiki&gt;https://medium.com/@bragadeeshs/how-to-navigate-maxima-and-minima-in-machine-learning-optimization-5eee9bc67303&lt;/nowiki&gt;

[10] &lt;nowiki&gt;https://blogs.sas.com/content/sgf/2018/11/13/customize-your-casl-code-with-built-in-and-user-defined-functions/&lt;/nowiki&gt;

[11] &lt;nowiki&gt;https://maths.cnam.fr/Membres/wilk/MathMax/help/Maxima/maxima_6.html&lt;/nowiki&gt;

[12] &lt;nowiki&gt;https://moodle.hft-stuttgart.de/question/type/stack/doc/doc.php/CAS/Maxima_background.md&lt;/nowiki&gt;

[13] &lt;nowiki&gt;https://docs.stack-assessment.org/en/CAS/Maxima_background/&lt;/nowiki&gt;

[14] &lt;nowiki&gt;https://maths.cnam.fr/Membres/wilk/MathMax/help/Maxima/maxima_6.html&lt;/nowiki&gt;

[15] &lt;nowiki&gt;https://maxima.sourceforge.io/docs/manual/Expressions.html&lt;/nowiki&gt;

[16] &lt;nowiki&gt;https://maxima.sourceforge.io/docs/tutorial/en/minimal-maxima.pdf&lt;/nowiki&gt;

=== Some Additional Examples of Maxima Operators ===

==== &lt;u&gt;Mathematical Operators&lt;/u&gt;: ====
&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
(%i7)	subst(x = 2, x^2 + y);
(%o7)	y+4

(%i8)	40^40/100^20;
(%o8)	1208925819614629174706176

(%i9)	factor(%);
(%o9)	2^80

(%i10)	diff((a+2)/(a+x),x,1);
(%o10)	-((a+2)/(x+a)^2)

(%i11)	%,x=2;
(%o11)	-(1/(a+2))

(%i12)	simp:false;
(simp)	false

(%i13)	%e^(%i*%pi)+1=0;
(%o13)	%e^(%i*%pi)+1=0

(%i14)	simp:true;
(simp)	true

(%i15)	'integrate(%e^(-x^2),x);
(%o15)	integrate(%e^(-x^2),x)


(%i16) test(f):=block([u],u:integrate(f,x),ratsimp(f-diff(u,x)))
(%o16)	test(f):=block([u],u:integrate(f,x),ratsimp(f-'diff(u,x)))

(%i17) test(sin(x))
(%o17)	0

(%i18) test(1/(1+x))
(%o18)	0

(%i19) test(1/(1+x^2))
(%o19)	0

(%i20) integrate(sin(x)^3,x)
(%o20)	cos(x)^3/3-cos(x)

(%i21) kill(q)$

(%i22) integrate(%e^x/(%e^x+2),x)
(%o22)	log(%e^x+2)

(%i23) integrate(1/(x*log(x)),x)
(%o23)	log(log(x))

(%i24) integrate(sin(2*x+3),x)
(%o24)	-(cos(2*x+3)/2)

(%i25) integrate(%e^x*erf(x),x)
(%o25)	%e^x*erf(x)-%e^(1/4)*erf(x-1/2)

(%i26) integrate(x/(x^3+1),x)
(%o26)	log(x^2-x+1)/6+atan((2*x-1)/sqrt(3))/sqrt(3)-log(x+1)/3

(%i27) diff(%,x)
(%o27)	2/(3*((2*x-1)^2/3+1))+(2*x-1)/(6*(x^2-x+1))-1/(3*(x+1))

(%i28) ratsimp(%)
(%o28)	x/(x^3+1)

(%i29) integrate(x^(5/4)/(x+1)^(5/2),x,0,inf)
(%o29)	beta(1/4,9/4)

(%i30) gradef(q(x),sin(x^2))
(%o30)	q(x)

(%i31) diff(log(q(r(x))),x)
(%o31)	(('diff(r(x),x))*sin(r(x)^2))/q(r(x))

(%i32) integrate(%,x)
(%o32)	log(q(r(x)))

&lt;/syntaxhighlight&gt;

==== &lt;u&gt;Programming Operators&lt;/u&gt;: ====
&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;(%i33)	for c:2 next 3*c thru 20 do display (c)$
c=2
c=6
c=18

(%i34)	for i:1 thru 10 do if i=3 then return(i);
(%o34)	3

(%i35)	t:0$

(%i36)	for i:1 while i &lt;= 15 do t:2*t+i;
(%o36)	done

(%i37)	t;
(%o37)	65519

(%i38) fib[n]:=if n=1 or n=2 then 1 else fib[n-1]+fib[n-2];
(%o38) fib[n]:=if n=1 or n=2 then 1 else fib[n-1]+fib[n-2]

(%i38) fib[1]+fib[2];
(%o38) 2

(%i39) fib[3];
(%o39) 2

(%i40) fib[5];
(%o40) 5

(%i41) eta(mu,nu):=if mu=nu then mu else (if mu&gt;nu then mu-nu else mu+nu);
(%o41) eta(mu,nu):=if mu=nu then mu else if mu&gt;nu then mu-nu else mu+nu

(%i42) eta(5,6);
(%o42) 11

(%i43) eta(eta(7,7),eta(1,2));
(%o43) 4

(%i44) if not 5 &gt;= 2 and 6 &lt;= 5 or 4+1 &gt; 3 then a else b;
(%o44) a

&lt;/syntaxhighlight&gt;

==== &lt;u&gt;Object Operators&lt;/u&gt;: ====
&lt;syntaxhighlight lang=&quot;maxima&quot;&gt;
/* List Objects */

(%i1)	my_list: [1, 2, 3, 4, 5];
(my_list)	[1,2,3,4,5]

(%i2)	op(my_list);
(%o2)	&quot;[&quot;

(%i3)	p:[1,1,2,x^2];
(p)	[1,1,2,x^2]

(%i4)	args(p);
(%o4)	[1,1,2,x^2]

(%i5)	nested: [1, [2, 3], [4, [5, 6]]];
(nested)	[1,[2,3],[4,[5,6]]]

(%i7)	nested[3];
(%o7)	[4,[5,6]]

(%i8)	op(%);
(%o8)	&quot;[&quot;

(%i9)	first(my_list);
(%o9)	1

(%i10)	third(my_list);
(%o10)	3

(%i11)	last(my_list);
(%o11)	5

(%i12)	L: create_list(i * x, x, [a, b, c], i, [1, 2, 3, 4]);
(L)	[a,2*a,3*a,4*a,b,2*b,3*b,4*b,c,2*c,3*c,4*c]

(%i13)	apply(&quot;+&quot;, [1, 2, 3]);
(%o13)	6

(%i17)	args('apply(&quot;+&quot;, [1, 2, 3]));
(%o17)	[&quot;+&quot;,[1,2,3]]

(%i18)	%[2];
(%o18)	[1,2,3]

(%i19)	A(s):=(3*sqrt(3)/2)*s^2$

(%i20)	map(A,my_list);
(%o20)	[3^(3/2)/2,2*3^(3/2),3^(7/2)/2,8*3^(3/2),(25*3^(3/2))/2]

/* Declared Arrays */

(%i23)	array (y, fixnum, 3);
(%o23)	y
(%i25)	arrayinfo(y);
(%o25)	[complete,1,[3]]
(%i24)	array(M, flonum, 3, 3);
(%o24)	M
(%i26)	arrayinfo(M);
(%o26)	[complete,2,[3,3]]
(%i27)	y[2]: %pi;
(y[2])	%pi
(%i29)	y[3]: %e;
(y[3])	%e
(%i32)	listarray(y);
(%o32)	[0,0,%pi,%e]

/* Hashed (undeclared) Arrays */

(%i33)	a_hashed_array[8] : 998;
(a_hashed_array[8])	998

(%i34)	arrayinfo(a_hashed_array);
(%o34)	[hashed,1,[8]]

(%i35)	listarray(a_hashed_array);
(%o35)	[998]

(%i36)	a_hashed_array[12] : x^2;
(a_hashed_array[12])	x^2

(%i37)	listarray(a_hashed_array);
(%o37)	[998,x^2]

(%i38)	another_hashed_array[3^(1/3)]:1;
(%o38)	1

(%i39)	arrayinfo(another_hashed_array);
(%o39)	[hashed,1,[3^(1/3)]]

(%i41)	subvarp (another_hashed_array[1]);
(%o41)	true

(%i42)	remarray (y,another_hashed_array);
(%o42)	[y,another_hashed_array]


/* Lisp Arrays */


(%i48)	:lisp (defvar $lisparray (make-array '(3 3) :initial-element 0.0))
$LISPARRAY

(%i48)	:lisp (setq $lisparray (make-array '(3 3) :initial-element 0.0))
#2A((0.0 0.0 0.0) (0.0 0.0 0.0) (0.0 0.0 0.0))

(%i48)	arrayinfo(lisparray);
(%o48)	[declared,2,[2,2]]

(%i49)	:lisp (aref $lisparray 0 0)
0.0
(%i49)	:lisp (aref $lisparray 2 2)
0.0

(%i49)	lisparray[2,2]:77;
(%o49)	77

(%i50)	:lisp (aref $lisparray 2 2)
77

(%i50)	:lisp (setf (aref $lisparray 2 2) 88)
88

(%i50)	:lisp (aref $lisparray 2 2)
88

(%i50)	:lisp (defvar $lisparray2 (make-array '(2 3) :initial-contents '((1 2 3) (4 5 6))))
$LISPARRAY2

(%i50)	listarray(lisparray2);
(%o50)	[1,2,3,4,5,6]

(%i52)	:lisp (write $lisparray2)
#2A((1 2 3) (4 5 6))
#2A((1 2 3) (4 5 6))

/* Structures */

(%i52)	defstruct(vector3d(x, y, z));
(%o52)	[vector3d(x,y,z)]

(%i53)	v1:new(vector3d(1.5, -2.0, 3.2));
(v1)	vector3d(x=1.5,y=-2.0,z=3.2)

(%i55)	v2:vector3d(x = 5, y = 10, z = 15);
(v2)	vector3d(x=(x=5),y=(y=10),z=(z=15))

(%i57)	v1@x;
(%o57)	1.5

(%i58)	v2@z : 7.4;
(%o58)	7.4

&lt;/syntaxhighlight&gt;

Official documentation and guides for operators are available through the Maxima Manual and the Maxima SourceForge Documentation Hub. [4, 5, 6]

=== Some Information Related to Mathematical Notation ===
There is no single, universal standard that dictates mathematical notation across all branches of math. Instead, notation varies by discipline, publisher, and sub-field. There are widely accepted conventions and formal frameworks that serve as references. The general topic of mathematical notation is beyond the scope of this book. However, mathematical notation does have some relevance in the context of Maxima as a computer algebra system.

Stephen Wolfram’s perspective in ''Mathematical Notation: Past and Future'' traces how symbols evolved from static, human-readable shorthand into active, executable computational language. The historical development moved from additive numerals and natural language prose toward structured operators and variables, while the future shifts toward programmatic, interactive, and &quot;computable&quot; expressions. [1, 2, 3, 4]

===== &lt;u&gt;The Past of Mathematical Notation&lt;/u&gt;: =====
* '''Evolution of Symbols:''' Early counting relied on unary notches and additive systems (like Egyptian hieroglyphs), eventually shifting to Hindu-Arabic base-10 positional numerals.
* '''Introduction of Operators:''' Algebraic variables, plus/minus signs, and calculus notations (such as Leibniz's &lt;math display=&quot;inline&quot;&gt;\operatorname{d}\!y/\operatorname{d}\!x

&lt;/math&gt; and &lt;math display=&quot;inline&quot;&gt;\int&lt;/math&gt; ) emerged primarily during the 16th and 17th centuries to replace cumbersome natural language descriptions.
* '''Standardization Limits:''' Traditional notation worked well for manual formula writing, but lacked any native capability to generalize into automated, multi-step computations or algorithmic processes. [3, 7]

===== &lt;u&gt;The Future of Mathematical Notation:&lt;/u&gt; =====
* '''Computational Language:''' Transitioning from passive text on paper to active, uniform symbolic structures.
* '''Programmatic Models:''' Replacing traditional passive equations with active programs capable of executing models across physics, biology, and social sciences.
* '''Universal Access:''' Utilizing interactive, graphical, and automated systems to democratize complex technical thinking much like mass literacy changed society centuries ago. [1, 4]


[1] &lt;nowiki&gt;https://www.stephenwolfram.com/publications/mathematical-notation-past-future/&lt;/nowiki&gt;

[2] &lt;nowiki&gt;https://lukegilson.co/2020/04/05/quick-notes-on-wolframs-mathematic-notation-past-and-future/&lt;/nowiki&gt;

[3] &lt;nowiki&gt;https://www.wolframscience.com/nks/notes-12-10--mathematical-notation/&lt;/nowiki&gt;

[4] &lt;nowiki&gt;https://writings.stephenwolfram.com/2020/10/our-mission-and-the-opportunity-of-artifacts-from-the-future/&lt;/nowiki&gt;

[5] &lt;nowiki&gt;https://library.wolfram.com/infocenter/Demos/4952/&lt;/nowiki&gt;

[6] &lt;nowiki&gt;https://writings.stephenwolfram.com/2013/05/dropping-in-on-gottfried-leibniz/&lt;/nowiki&gt;

[7] &lt;nowiki&gt;https://sites.math.rutgers.edu/~zeilberg/Opinion64.html&lt;/nowiki&gt;

[8] &lt;nowiki&gt;https://physicsworld.com/a/exploring-the-computational-universe-with-stephen-wolfram/&lt;/nowiki&gt;
'''The Future of Notation:''' Read Stephen Wolfram's ''Mathematical Notation: Past and Future'' to learn how the history of notation shapes modern computation. [1]&lt;blockquote&gt;
''&quot;Now I have to tell you that I had always assumed that mathematical notation was too haphazard to be used as any kind of thing that a computer could reasonably interpret in a rigorous way. But at the beginning of the 1990s we got interested in making Mathematica be able to interact with mathematical notation. And so we realized that we really had to figure out what was going on with mathematical notation.''

''Neil Soiffer had spent quite a number of years working on editing and interpreting mathematical notation, and when he joined our company in 1991, he started trying to convince me that one really could work with mathematical notation in a reasonable way, for both output and input.''

''The output side was pretty straightforward: after all, TROFF and TeX already did a moderately good job with that.''

''The issue was input.''

''Well, actually, one already learned something from output. One learned that at least at some level, a lot of mathematical notation could be represented in some kind of context-free form. Because one knew that in TeX, for instance, one could set things up in a tree of nested boxes.''

''But how about input? Well, one of the biggest things was something that always comes up in parsing: if you have a string of text, with operands and operators, how do you tell what groups with what?&quot;&lt;br /&gt;''

– Stephen Wolfram&lt;/blockquote&gt;{{Bookcat}}
{{Status|0%}}</text>
      <sha1>qel664mjnn42e7xiehytw6hu1ffqtem</sha1>
    </revision>
  </page>
  <page>
    <title>User talk:Kittycataclysm</title>
    <ns>3</ns>
    <id>442343</id>
    <revision>
      <id>4656107</id>
      <parentid>4655156</parentid>
      <timestamp>2026-08-02T20:39:20Z</timestamp>
      <contributor>
        <username>Duodeca 12</username>
        <id>3615790</id>
      </contributor>
      <comment>/* Vandalism */ new section</comment>
      <origin>4656107</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="97803" sha1="5g7jub5gu0jmr9dfbc01yjmt7wc08e4" xml:space="preserve">{| class=&quot;wikitable&quot;
|+
! colspan=&quot;3&quot; |Talk Page Archives
|-
|[[User talk:Kittycataclysm/Archive 2022|2022]]
|[[User talk:Kittycataclysm/Archive 2023|2023]]
|[[User talk:Kittycataclysm/Archive 2024|2024]]

|}

== That IP range calculator ==

Following [[phab:T381138|T381138]], I have now become the maintainer of the IP range calculator you like. You can find it [[toolforge:ftools/general/ip-range-calc.html|here]]. [[User:JJPMaster|JJP]]&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]]) 23:10, 9 January 2025 (UTC)

:Thank you for the heads-up! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:56, 10 January 2025 (UTC)

== A merge and unmerge from two years ago ==

I was browsing through the history merge log when I saw that you merged [[Cookbook:Chicken Bog]] into [[Cookbook:Chicken Bog I]], and then promptly reverted it. What happened here exactly? Could I correct it? [[User:JJPMaster|JJP]]&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]]) 15:55, 10 January 2025 (UTC)

:Good question! I can't remember what I was trying to do, but it looks like I didn't succeed at what I wanted based on the log comment. You're just trying to history merge to get [[Cookbook:Chicken Bog I]] to have continuity of history? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 16:35, 10 January 2025 (UTC)
::I think I figured out your mistake: it outright moved the revisions from the first page to the second, rather than copying them. This would have caused the other two [[Cookbook:Chicken Bog]] pages to have incomplete histories. I think the only solution would be to XML import the pre-April 2023 revisions from the first page to the other three, and I'm not sure if that's the best idea, and I am technically unable to do so. [[User:JJPMaster|JJP]]&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]]) 16:49, 10 January 2025 (UTC)

== Undeletion request ==

I wouldn't be surprised if you expected this, but I'd like to ask you to undelete the subpages of [[Rotorcraft Fundamentals]] you just deleted with the summary &quot;Use of copyrighted work without permission. Please read Terms of Use: page needs to be imported for attribution&quot;, so that I can do that. [[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]]) 19:54, 14 January 2025 (UTC)

:Done! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 19:57, 14 January 2025 (UTC)
::Upon further investigation, this might actually be a rare case where an [[WB:UT|unmerged transwiki]] is ''preferred'' (this is part of why I stopped calling them &quot;bad transwikis&quot;), since only a small portion of the Wikipedia article (with over 2,000 revisions) was copied over. Importation is generally only needed if the ''majority'' of the page is copied across wikis. I'll just leave a null edit providing attribution and add {{tlx|Copied}}. [[User:JJPMaster|JJP]]&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]]) 21:19, 14 January 2025 (UTC)

== Reusing [[Cookbook:8 Desserts in 1 Pan]] on wikiHow ==

Hi, I am a user on wikiHow, see [[wikihow:User:Xeverything11]]. I would like to create a new recipe on wikiHow. I wanted to let us know if I can give permission to reuse your contributions to this recipe from Wikibooks to wikiHow. I (as a copyright holder) created this recipe on Wikibooks, but you contributed to this recipe.

If not, I'll use the revision before you contributed since I was the only author. 

Wikibooks uses CC-BY-SA 4.0 while wikiHow uses CC-BY-NC-SA 3.0, which both licenses are incompatible due to ShareAlike conditions.

Thanks [[User:Xeverything11|Xeverything11]] ([[User talk:Xeverything11|discuss]] • [[Special:Contributions/Xeverything11|contribs]]) 08:27, 15 January 2025 (UTC)

:@[[User:Xeverything11|Xeverything11]] I'm personally fine with this as long as proper attribution is given back to the original recipe page here. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:52, 20 January 2025 (UTC)
::I adapted this [[wikihow:Make-8-Desserts-in-1-Pan|recipe]] on wikiHow with attribution, and got a Rising Star (an achievement used for best new articles on wikiHow). Thank you! [[User:Xeverything11|Xeverything11]] ([[User talk:Xeverything11|discuss]] • [[Special:Contributions/Xeverything11|contribs]]) 19:49, 24 January 2025 (UTC)

== Wikibooks community ==

Hi, @[[User:Kittycataclysm|Kittycataclysm]]!

I am trying to contribute more to English Wikibooks. My main contributions will focus on the Cookbook, especially on Indonesian recipes. Do you have a community group where we can discuss and share ideas together?

I am looking forward to join. Thank you!

[[User:Raflinoer32|Raflinoer32]] ([[User talk:Raflinoer32|discuss]] • [[Special:Contributions/Raflinoer32|contribs]]) 08:47, 16 January 2025 (UTC)

:@[[User:Raflinoer32|Raflinoer32]] Sorry I missed this, and welcome! Are you asking about a Cookbook-specific area for discussion? Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:39, 20 January 2025 (UTC)
::Yes. Do you know place for this?
::Thank you 
::[[User:Raflinoer32|Raflinoer32]] ([[User talk:Raflinoer32|discuss]] • [[Special:Contributions/Raflinoer32|contribs]]) 09:41, 21 January 2025 (UTC)
:::Honestly, there's not a centralized Cookbook-specific discussion space, especially since there aren't currently a ton of active contributors. Some people ask questions at [[Cookbook talk:Table of Contents]]. I'm currently the most consistently active and involved Cookbook editor, so feel free to ask me questions! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:46, 22 January 2025 (UTC)

== Congratulations! ==

[[File:Admin T-shirt.svg|thumb|You get this now.]]
You are now a permanent administrator. Welcome to the team (I am entitled to say this because I technically got the extension a few hours before you did)!{{FBDB}} [[User:JJPMaster|JJP]]&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]]) 10:33, 29 January 2025 (UTC)

:Thanks :) —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 13:29, 29 January 2025 (UTC)

== Is there a way to contact a Steward on WikiBooks? ==

Hi {{PAGENAME}},
Is there a way to contact a Steward on WB? I tried to find who the active Stewards are here  at [[Special:ActiveUsers?username=&amp;groups%5B%5D=steward&amp;wpFormIdentifier=specialactiveusers]] but nothing shows up.

The reason I am asking is that I believe that all individual Wikimania-wikis should have a backward link to the [[Wikimania-wiki]], but I just visited the [[wikimania 2014 wiki]] and could not  find this backward link. I tried to ask about this  on the [[Wikimania 2014 main-page talk]] but disovered that the Stewards have protected it. 

Is there a way  wikibookians can communicate with Stewards at WB? Thanks in advance for answering this non-urgent question, and apologies for all the red-links which I can bluify if needed. Cheers [[User:Ottawahitech|Ottawahitech]] ([[User talk:Ottawahitech|discuss]] • [[Special:Contributions/Ottawahitech|contribs]]) 16:37, 7 February 2025 (UTC)

:@[[User:Ottawahitech|Ottawahitech]] You can ask this on somewhere like [[metawiki:Steward requests/Miscellaneous]]. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 17:01, 7 February 2025 (UTC)
&lt;s&gt;:@[[User:Ottawahitech|Ottawahitech]] seconding what Leaderboard said—we no longer have any active stewards at enWB.&lt;/s&gt; Had a brain fade there and mixed up stewards with bureaucrats. Yes, meta is the place for this. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 19:15, 7 February 2025 (UTC)
::@Kittycataclysm,@[[User:Leaderboard|Leaderboard]], or anyone else:
::Some wikibookians prefer for various reasons to post only at wb. I myself am indef-blocked at  META so could not participate at [[metawiki:Steward requests/Miscellaneous]] even if I waned to.
::Since [[Wikimania]] is a topic of interest to all members of the [[wikimedia movement]] why can't wikibookians talk to thier elected representatives here? [[User:Ottawahitech|Ottawahitech]] ([[User talk:Ottawahitech|discuss]] • [[Special:Contributions/Ottawahitech|contribs]]) 20:56, 7 February 2025 (UTC)
:::@[[User:Ottawahitech|Ottawahitech]] I can check with the blocking admin to see if they'd be willing to unblock you, if you'd like. The reason things like these are done at Meta is that Meta is a cross-project coordination platform - stewards ''cannot'' be expected to watch every project after all. Now you could message any steward here on Wikibooks if you really wanted to, but that is not normally a good idea. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 02:26, 8 February 2025 (UTC)
::::Wikimania is the annual conference celebrating all the free knowledge projects hosted by the Wikimedia Foundation (WMF).  It is a wikimedia initiative which is meant to help all of our projects (including wikibooks), gain more readership, educate more wiki-editors, foster better communications, and much more.  The wmf has been hosting  a Wikimania-wiki dedicated to each Wikimania annual event since 2004. These wikis contain a wealth of information, but can  benefit from wiki-improvements, starting from spelling and grammar errors that detract from their to appeal to the general membership. It would be nice if Stewards paid more attention to it.
::::@[[User:Leaderboard|Leaderboard]], I truly appreciate your offer, but  I posted this here not in order to get someone to advocate for one unblocking at META. As I said earlier:
::::* &quot;Some wikibookians prefer for various reasons to post only at wb&quot;
::::* &quot;The reason I am asking is that I believe that all individual Wikimania-wikis should have a backward link to the Wikimania-wiki, but I just visited the wikimania 2014 wiki and could not find this backward link. I tried to ask about this on the Wikimania 2014 main-page talk but disovered that the Stewards have protected it&quot; 
::::I would much rather see more wikimedia members question blocking in general at META. One cannot run such large movement of people from different backgrounds and nationalities simply by silencing minorities  IMIO. [[User:Ottawahitech|Ottawahitech]] ([[User talk:Ottawahitech|discuss]] • [[Special:Contributions/Ottawahitech|contribs]]) 20:12, 8 February 2025 (UTC)

== [[Crystal ball]] ==

That page appears to be a mixture of isolated paragraphs from [[w:Crystal ball|Crystal ball]], hence my tag. [[User:JJPMaster|JJP]]&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]]) 03:04, 9 February 2025 (UTC)

:Yep, that seems correct! I also queried it simply because it does not seem suitable for inclusion at all. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 03:09, 9 February 2025 (UTC)

== Question about an edit suggestion ==

Hi Kittycataclysm,

Thanks for the great work you do as an admin! I wanted to clarify a suggestion you made on a recently published page I’m working on. You recommended splitting it into smaller sections—would you suggest creating separate pages for these sections, or would a higher-level header for some topics be sufficient?

Any specific recommendations you have would be greatly appreciated!

Here’s the link to the page I’m referring to: [[Funding and Finance of Transportation Projects in the United States of America]]

Thank you! [[User:Svrmustafa|Svrmustafa]] ([[User talk:Svrmustafa|discuss]] • [[Special:Contributions/Svrmustafa|contribs]]) 18:19, 18 February 2025 (UTC)

:Hi @[[User:Svrmustafa|Svrmustafa]], and thanks for asking! Splitting refers to creating new pages, each with a smaller amount of content. The main page should then contain a table of contents, and each page can contain a navigation template for easier navigation. I'll create the table of contents based on the current work and move some content to one of those pages as an example for you; then, you can do the rest. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:26, 19 February 2025 (UTC)
::Following up on this—I noticed that you use the term &quot;paper&quot;. However, technically Wikibooks hosts books not papers, so you should probably change this wording. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:38, 19 February 2025 (UTC)
== Talkback ==
{{Talkback|Cookbook talk:Chilli Crab|Recipe Questions}} [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 09:54, 19 February 2025 (UTC)

:@[[User:Kittycataclysm|Kittycataclysm]] I also made [[Cookbook:Prata|this]] [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 10:15, 19 February 2025 (UTC)

== Hello ==

Can you look at my latest recipe? [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 00:10, 28 February 2025 (UTC)

:I saw it! It needs a few corrections, which I'll note. What's the origin of the recipe? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 03:23, 28 February 2025 (UTC)
::@[[User:Kittycataclysm|Kittycataclysm]] How do you write recipe summary, correct headers [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 06:04, 28 February 2025 (UTC)
:::Please see [[Cookbook:Policy/Recipe template]]. What's the origin of the recipe? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 13:08, 28 February 2025 (UTC)
::::ok [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 02:33, 1 March 2025 (UTC)

== Cookbook ==

Hi there, Kittycataclysm. I wandered over here from Wikipedia, and I'm quite enamoured with this cookbook. I noticed you seem to be the one maintaining it, and I thought I'd reach out. Can I really just start cranking out recipes from public domain cookbooks and my family recipes? It's that simple? I was also wondering about the featured recipes section. There's not very many in there, and I imagine there's not very many folks around to do reviews compared to GAR on Wikipedia. How do you handle content review? Thanks. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 01:51, 1 March 2025 (UTC)

:Hi @[[User:MediaKyle|MediaKyle]] and welcome! For some context, the Cookbook has been around since the very beginning of Wikibooks, but it had gotten into a bit of disarray over the course of about two decades by the time I found it. I started the long process of overhauling, standardizing, and expanding it just over four years ago—I finished standardizing the recipe formatting and quality a while back and am currently working my way through the ingredient pages before moving on to equipment, techniques, and cuisines. You can absolutely add any public domain recipes as well as your own recipes—they just need to conform to the [[Cookbook:Policy/Recipe template|recipe template]] and [[Cookbook:Policy|Cookbook policy overall]]. It's even better if you've made the recipe and can contribute a nice picture and specific guidance/instructions/notes! Please feel free to ask me any questions. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:27, 1 March 2025 (UTC)
::Oh, and regarding the featured recipes section, I actually haven't gotten around to looking into that yet—there's been a lot to do! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:28, 1 March 2025 (UTC)
::That's great, thanks a lot for your response. This is just delightful. Maybe content review is something that we could collaborate on. There's a lot of recipes in here and it would be nice to know which ones are the best. Question for you, [[:Category:Brown sauces]] is really bothering me. How can I move that to Brown sauce recipes? [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 02:29, 1 March 2025 (UTC)
:::Good catch on that category! It seems like it was created two decades ago and never got corrected—feel free to recategorize those recipes. Thank you also for introducing the hideprefix parameter to the category trees—I didn't realize that was an option, and it reduces the visual clutter! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:38, 1 March 2025 (UTC)
::::My pleasure! As I continue to look at the categories, this is actually worse than I thought. We have both [[:Category:Sauce recipes]] and [[:Category:Recipes for condiments]] and I suspect that's just the beginning. I want to go through and categorize everything properly, but the bones aren't even there... How long do I have to be here before it'll let me create and move around categories? [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 02:40, 1 March 2025 (UTC)
:::::Regarding the categories, the category overhauling is in progress, since I address the category when I overhaul the associated page. The variation in titling is actually somewhat deliberate—I started changing it from &quot;____ recipes&quot; in certain cases to solve a particular categorization problem. Sometimes, there is an item that is used in recipes as an ingredient but for which there are also recipes. For example, [[:Category:Recipes for bread]] versus [[:Category:Recipes using bread]]. The different naming scheme is necessary to properly delineate the categories, and I'm working on implementing it a bit more consistently as I go. While you're still getting started, it would be great if you could check with me when something looks odd or out of place—that way I can take a look and weigh in on whether that's normal or not and maybe provide some context. Just off the top of my head, I think you will have to wait for autoreview status to make move changes. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:56, 1 March 2025 (UTC)
::::::I see what you're saying, I've been trying to wrap my head around that. Maybe it would be beneficial to try to put together some sort of a Cookbook MOS regarding category structure? It's kind of all over the place right now. Using your bread example, would it perhaps make more sense to have [[:Category:Bread recipes]] and [[:Category:Recipes using bread]]? There would be no ambiguity with just those two categories, but when you add the extra [[:Category:Recipes for bread]], that's when things start getting a little whacky. What do you think? [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 03:05, 1 March 2025 (UTC)
:::::::Either that or get rid of [[:Category:Bread recipes]] and keep the other two. But one of these categories gotta go, I reckon. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 03:07, 1 March 2025 (UTC)
::::::::I see you already had the same thought as me. I think all categories should include &quot;for&quot; or &quot;using&quot;. Take for example, [[:Category:Recipes for pancakes]] as opposed to [[:Category:Pancake recipes]]. Well obviously there's no recipes using pancakes. But for something like [[:Category:Recipes for gravy]], there may also be a need for [[:Category:Recipes using gravy]]. The lack of consistency in this regard means the only way to achieve consistency across the categories is by changing them over to that format. Sorry for clogging up your talk page! [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 03:18, 1 March 2025 (UTC)
:::::::::Same heads-up as below—migrating this over to [[Cookbook talk:Table of Contents]] —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:10, 4 March 2025 (UTC)
:Also, on [[Cookbook:Table of Contents]], could you please add a wikilink for [[Cookbook:Breakfast]], and maybe add cooknav to the top for seamless navigation between all the top level articles? Can't edit that article yet. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 02:47, 1 March 2025 (UTC)

== More Table of Content Edits ==

Hello again. I've been going through everything and this is my list of suggestions for edits to the table of contents. Unfortunately there's not much else I can do for now, because without autoconfirmed my ability to change anything is very limited. I was going to ask for someone to check off the confirmed box for me at RfP but I can't post there either, so I guess I'll be back in four days.

* Fix Bread wikilink
* Remove &quot;Creaming&quot; from techniques, redirected to Mixing
* [[Cookbook:History of Food and Cooking]] points to redirect, needs capitalized
* [[Cookbook:Low-Carb]] points to redirect, needs capitalized
* [[Cookbook:Cuisine of the Mediterranean]] to [[Cookbook:Mediterranean Cuisine]] for parity
* Remove the S from the cuisine wikilinks on ToC, currently redirecting
* Create [[:Category:Lunch recipes]], wikilink to ToC
* Wikilink [[Cookbook:Dessert]] under Meals
* Get rid of &quot;Brunch&quot;; will just be confusing alongside a breakfast and lunch category
* Create [[Cookbook:East Asian Cuisine]] so I can add the recipes from [[:Category:East Asian recipes]] to it; currently is a redlink on the ToC
* Change &quot;Introductory Matter&quot; header to just &quot;Introduction&quot;
* Appendix and Equipment sections switch places

Cheers, [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 11:46, 1 March 2025 (UTC)

:I took the liberty of doing it myself in my userspace. You can just copy it over from [[User:MediaKyle/sandbox]]. Figured I'd save you the trouble of trying to figure out what I'm talking about. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 14:15, 1 March 2025 (UTC)
:Circling back to this! It seems like your suggestions are getting at a couple different things. I'll try to go through them point-by-point below:
:* {{xt|Fix Bread wikilink}} {{done}}
:* {{xt|Remove &quot;Creaming&quot; from techniques, redirected to Mixing}} see below comments on TOC.
:* {{xt|Cookbook:History of Food and Cooking points to redirect, needs capitalized}} {{not done}} for now because I don't fully understand the urgency and I want to triage/prioritize things for you, but please feel free to make this change yourself once you can!
:* {{xt|Cookbook:Low-Carb points to redirect, needs capitalized}} {{not done}} for same reason as above.
:* {{xt|Cookbook:Cuisine of the Mediterranean to Cookbook:Mediterranean Cuisine for parity}} {{not done}} for now just because we do have a lot of cuisine pages that follow the form &quot;Cuisine of ____&quot;. It could be good to standardize, and I had been planning to do that once I got around to the cuisines.
:* {{xt|Remove the S from the cuisine wikilinks on ToC, currently redirecting}} {{not done}} for same reason as other redirects
:* {{xt|Create Category:Lunch recipes, wikilink to ToC}} Not quite sure what you mean here, and I didn't see what it corresponded to in your linked sandbox page
:* {{xt|Wikilink Cookbook:Dessert under Meals}} {{done}}
:* {{xt|Get rid of &quot;Brunch&quot;; will just be confusing alongside a breakfast and lunch category}} I'm not sure about this—brunch is in many places considered a separate entity, and I don't necessarily think it would cause confusion. But, overall it's hard to determine whether it should have its own page and TOC link because I haven't actually gotten around to evaluating the meal pages and what role they should play. See also the TOC notes below.
:* {{xt|Create Cookbook:East Asian Cuisine so I can add the recipes from Category:East Asian recipes to it; currently is a redlink on the ToC}} {{done}} for now; however, I'm not sure yet whether it will ultimately make sense to keep that as a content page. I think content pages should be reasonably focused, and it may not be the best to have a cuisine page that is so broad. This is something I planned to consider once I made my way around the overhauling the cuisines.
:* {{xt|Change &quot;Introductory Matter&quot; header to just &quot;Introduction&quot;}} The reason I made it &quot;Introductory Matter&quot; instead of &quot;Introduction&quot; is because there's already a chapter itself titled &quot;Introduction&quot;—it felt odd to have the entire section titled that as well. Happy to discuss other header options (e.g. &quot;Front Matter&quot;, which is a generally accepted book term)
:* {{xt|Appendix and Equipment sections switch places}} see below comments on TOC.
:* '''Comments on the TOC:''' So, I think a fundamental issue with the current TOC is that it somewhat arbitrarily picks and chooses individual pages to link. It also sometimes direct-links to categories and sometimes to content pages, which I don't think we should do. Because the cookbook is so expansive, it's been established that manual indices intending to capture detail in large areas don't really make sense and quickly get bulky and out-of-date. This is why categorytree is such a useful tool! After thinking on it for a while and making some small tweaks, I think I'd ultimately like to overhaul the TOC and come to a solution that keeps a few broad headers/links to the small handful of the primary content pages while perhaps stashing away more detailed and self-updating lists in a collapsible way to reduce clutter but allow for customizable user navigation. Much to think about, and I'll probably workshop some things on the side to see how they feel.
:Let me know if I've misunderstood anything! Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 03:24, 3 March 2025 (UTC)
::Thanks for the notes! Here's my thoughts:
::* On the Cuisine titling, it actually seems like [[Cookbook:Cuisine of the Mediterranean]] and [[Cookbook:East Asian cuisines]] are the only ones that don't follow the naming scheme, i.e. &quot;[[Cookbook:African Cuisine]]&quot;, and I think that shorter titles are preferable where it makes sense.
::* On your note about East Asian Cuisine, I actually had the same thought after going through the cuisine pages. Having three separate pages for different kinds of Asian cuisine does seem a little silly, doesn't it? Do you think it might be better to combine all of them under one &quot;Asian Cuisine&quot;, but put the different locales under separate headers?
::* On Brunch - I honestly think there's way too much ambiguity around what exactly constitutes as &quot;brunch&quot; to keep that in. I feel as though the term brunch more applies to the time you're eating, rather than the kind of food. I think it would be easier to keep meals that include commonly accepted breakfast foods in the Breakfast category, and things that don't fit neatly into that, into the Lunch category. This would prevent any dilemmas in the future where we can't decide whether something is breakfast or brunch.
::* You're right that it looks a little awkward to have the header as Introduction when there's a page called introduction. I still think that to say &quot;Introductory Matter&quot;, or &quot;Front Matter&quot; as you mentioned, is a little long-winded and reflects a more academic tone than needed for a cookbook. Upon further reflection, I think maybe rather than worrying about the header at this point, we should perhaps think about trying to compile all of those short introductory type pages into one comprehensive introductory page. Then we likely won't even need a header for it on the ToC.
::* The ToC is definitely a bit cluttered, and it bothers me too that there's a real lack of consistency across whether the wikilinks lead to a page or a category. I'm not sure how I would feel about cutting away too much of the navigation from it, though, because just about every page on there does have a reason to be there, it's just that they're not presented very nicely. Some of it can certainly get nested or combined though. I'll play around with it over the next few days in my sandbox as well and let you know if I come up with anything.
::* As an aside, the first thing on my to-do list once my autoconfirmed comes through is to start subcategorizing all of the recipes so that they're all nicely sorted in the category trees. When you have a chance, I'd love to hear your thoughts on what we should use as the standard naming for categories. Once we determine this, I think we can also take the liberty of updating the cookbook MoS to reflect it.
::Cheers, [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 11:33, 3 March 2025 (UTC)
:::Note: After writing this, I realized what you were getting at about slashing away some of the subpages. Maybe we can come up with a system where all of those subpages are under their main subpage rather than on the ToC. For example, all the Cuisines are under [[Cookbook:Cuisines]], all techniques under [[Cookbook:Cooking Techniques]], to keep the subpages off the main ToC. Also, I wonder if maybe we should try to make a centralized discussion for this somewhere, in case anyone else wants to join in at some point? [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 11:45, 3 March 2025 (UTC)
::::Heads-up: to make it easier to keep track of these and since I think they deserve their own discussions, I'm going to gradually migrate them over individually to [[Cookbook talk:Table of Contents]]. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:52, 4 March 2025 (UTC)
:::::Good idea. Can you remove the semi-protection from that talk page? I see no reason why it should be protected. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 23:23, 4 March 2025 (UTC)

== Cookbook ToC ==

Hi [[User:Kittycataclysm|Kittycataclysm]]. I was just wondering why you didn't respond to my above message, and started a separate sandbox for the ToC instead? It seems as though you don't really want to collaborate. It would be nice if we could work on this together. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 22:43, 2 March 2025 (UTC)

:@[[User:MediaKyle|MediaKyle]] thanks for the ping! I'm sorry you feel like I don't want to collaborate—the opposite is true, and please understand that this is good-faith editing. The reason I haven't responded to the above points is mostly since you've been modifying a bunch of content and adding suggestions lately, and I've been working my way through these while continuing with my routine contributions and real life as well—things happen a little more slowly here than on other projects, and I'm the one person dedicated to the cookbook right now. The reason I created that sandbox was because I saw [[Wikibooks:Reading room/General#Modernize the shelves|your comment]] at the reading room and wanted to play around and think about your suggestion without touching the actual TOC. You're right that it's not the best, and it's been something I've been thinking about for a bit now. Please understand also that it can be overwhelming when a new editor unfamiliar with the Cookbook begins making a high volume of edits and suggestions without having much experience with it or its history—this isn't to say that you don't have good ideas or things worth contributing. In fact, you have already made a few helpful changes, as I've mentioned. I just want to do this properly and take the time to evaluate your suggestions together with the current efforts that are underway, and that can take a bit. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:03, 2 March 2025 (UTC)
::Thanks for getting back to me. While I may be new to Wikibooks, I'm certainly not new to MediaWiki, and I've been working with small wiki projects for a number of years. Perhaps it's been a misunderstanding to some degree, but I've found my reception here to be unusually unwelcoming. The way to do this properly, as you said, would be to have discussions and form consensus. Yesterday, when you reached out to me about adding hideroot to the pages, I gave you my rationale and was more than happy to have a discussion about it, but you did not reply. I noticed a similar situation happened with [https://en.wikibooks.org/wiki/User_talk:Ottawahitech#Category_sorting Ottawahitech], regarding category sorting. I'm aware that you're the main person looking after the cookbook right now, which is why I reached out to you right from the get go.
::I understand why you would want to create your own sandbox to play around with options for the ToC, but I'm sure you can understand why it would draw my attention that you would do this without implementing any of the wikilink fixes I mentioned, or making an attempt to discuss it further. This came across to me as not wanting my help.
::I invite you to check out my page on Wikipedia. I've made contributions across quite a wide area of topics there, as well as the other Wikimedia projects, and this is the first time I've encountered any sort of resistance to my contributions. I think Wikibooks has enormous potential, and I'm very excited to contribute to helping it grow. On most projects, this would be something to be encouraged. I don't feel like &quot;I'm sorry that you feel that way&quot; was really an appropriate response. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 23:59, 2 March 2025 (UTC)
:::I think you're right that this has been a mix of misunderstanding and miscommunication, and I think I can understand how things came across as unwelcoming! For whatever it's worth, I absolutely plan on circling back to the various discussions at hand (I have all the relevant pages open to return to), but it seems like the order I did things made it seem like I was ignoring you (if I'm understanding correctly). I am pretty busy, so sometimes items on my to-do list do get lost/shunted or it takes me a bit to get around to something—please don't hesitate to give me a ping if it seems like I'm taking a while to get back to something. Looking forward to more collaboration! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:49, 3 March 2025 (UTC)
::::I'm glad you can understand where I'm coming from. To clarify, my intent is not to try to rush you, or to try to push you to make changes that you don't agree with. It's really easy to misinterpret things over the Internet, and I think a short message can go a long way. I apologize if I've caused you any undue stress by coming into the cookbook and unleashing a flurry of alterations, but do rest assured that I'm not married to any of my changes, I'm always open for discussion, and I want to see the cookbook improve just like you do. The great thing about wikis is that no change is permanent. I think we'll have it in tip-top shape in no time! [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 01:19, 3 March 2025 (UTC)

== [[Cookbook:Polish Doughnuts (Paczki)]] ==

Do you see any reason not to just add this to Featured Recipes? At least we know this one works, and it seems like this is now one of the few recipes to have a picture that actually aligns with the recipe used. I was thinking later on we'll come up with a content review system where a couple editors will actually try the recipes nominated for FR, but in the absence of that I'd just add it to the list. [[User:MediaKyle|MediaKyle]] ([[User talk:MediaKyle|discuss]] • [[Special:Contributions/MediaKyle|contribs]]) 12:25, 4 March 2025 (UTC)

:I'm fine with adding it to the featured recipes. You're right that we'll want to come up with a good system for this going forward, though it's lower down on my personal priority list at moment. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:15, 4 March 2025 (UTC)

== [[Cookbook:Cream Cheese American Buttercream]] ==

Hi! I am a wikiHow user and I am planning to adapt this recipe to wikiHow. Since you contributed to this recipe, I wanted to know if I can get permission to reuse your contributions to this recipe. Thanks. [[User:Xeverything11|Xeverything11]] ([[User talk:Xeverything11|discuss]] • [[Special:Contributions/Xeverything11|contribs]]) 21:41, 4 March 2025 (UTC)

:@[[User:Xeverything11|Xeverything11]] that's fine with me as long as proper attribution and linking back to the original recipe page here are included at the top. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:28, 4 March 2025 (UTC)

== [[A Companion to Our Literary Journey]] ==

Hi! I feel that we have started to outline the scope in a clearer and more precise way and that’s the work we are going to do with the students this and for the next years, adding more sections and content. Do you think that would be enough? [[User:Ferdi2005|Ferdi2005]] ([[User talk:Ferdi2005|discuss]] • [[Special:Contributions/Ferdi2005|contribs]]) 22:43, 6 March 2025 (UTC)

:Hi @[[User:Ferdi2005|Ferdi2005]]! Yes, this seems to be reasonably outlined. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:51, 7 March 2025 (UTC)

== Exercising care with copyright ==

When deleting a page as a copyright violation, it is important that you '''do not quote any content from the deleted page'''. If you do, then your log entry is itself a copyright violation. I have redacted a recent deletion that you performed because of this. If you want to make sure that none of your past deletions have been problematic for this reason, you can [[quarry:query/90444|run this SQL query]] to get a list of every deletion that could be eligible for redaction. [[User:JJPMaster|JJP]]&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]]) 18:32, 21 March 2025 (UTC)

:Hi @[[User:JJPMaster|JJPMaster]] and thank you for the message. In the most recent instance that I think you're referencing, I do not see any material in the edit summary that posed a significant risk—I don't believe the few listed words would be a copyright concern. However, I do understand your concern! Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:31, 21 March 2025 (UTC)

== Splitting Pages ==

Hi I have recently made the book on the [[History of the Nawabs of Bengal]] and you gave a notice on how you believe it should be split into smaller bits. As I am still new to wikibooks I don't know how to do this. Can you please assist me on renaming the page so I can split the page into multiple pages? @[[User:Kittycataclysm|Kittycataclysm]] [[User:Greatswrd|Greatswrd]] ([[User talk:Greatswrd|discuss]] • [[Special:Contributions/Greatswrd|contribs]]) 19:47, 29 March 2025 (UTC)

:@[[User:Greatswrd|Greatswrd]]: You did it. I've removed the tag. [[User:JJPMaster|JJP]]&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]]) 22:44, 29 March 2025 (UTC)
:Like @[[User:JJPMaster|JJPMaster]] said, you're all set! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:53, 29 March 2025 (UTC)
::Thanks! @[[User:JJPMaster|JJPMaster]] @[[User:Kittycataclysm|Kittycataclysm]] [[User:Greatswrd|Greatswrd]] ([[User talk:Greatswrd|discuss]] • [[Special:Contributions/Greatswrd|contribs]]) 10:24, 30 March 2025 (UTC)

== Minecraft book ==

Is it good creating pages like this, [[Minecraft#Husk]]? [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 12:43, 9 May 2025 (UTC)

:@[[User:Cactusisme|Cactusisme]] what do you mean? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 21:18, 10 May 2025 (UTC)
::are we allowed to create pages like that? like for every mob [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 10:02, 11 May 2025 (UTC)
:::To be honest, I don't think the structure and formatting of the book is very good. Several of the mob pages, for example, have very little information and aren't particularly helpful on their own. If I were working on it, I would restructure the book. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 14:09, 11 May 2025 (UTC)
::::I am planning to do that. [[User:Cactusisme|Cactusisme]] ([[User talk:Cactusisme|discuss]] • [[Special:Contributions/Cactusisme|contribs]]) 04:19, 12 May 2025 (UTC)

== Request to Review Adjusted User Page (XoriantTeam) ==

Hello [[User:Kittycataclysm|Kittycataclysm]],

I hope you're well. I noticed that my user page ([[User:XoriantTeam]]) was recently deleted for appearing promotional or inappropriate for Wikibooks. Thank you for keeping the community standards in check.

I’ve since revised the content with closer attention to neutrality and compliance with Wikibooks guidelines. My intent is to participate constructively, especially in areas related to digital engineering and educational content creation.

If possible, I’d appreciate your help reviewing the revised version. I'm happy to share it or upload it as a file if there’s a preferred method.

Please let me know how best to proceed. I welcome any suggestions and will gladly make further adjustments.

Best regards,  

XoriantTeam [[User:XoriantTeam|XoriantTeam]] ([[User talk:XoriantTeam|discuss]] • [[Special:Contributions/XoriantTeam|contribs]]) 11:02, 15 May 2025 (UTC)

:Hi there—you can publish an updated user page, but I'd caution you against talking about your company. Keep it limited to your involvement with Wikibooks. You may contribute productively here, but further promotional materials are grounds for an indefinite block. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 12:30, 15 May 2025 (UTC)

== Planning to use AWB to update categories on the cookbook ==

Hello. I noticed in recent changes that you were moving some categories using HotCat (e.g. moving Category:Chile recipes to Category:Recipes using chile), which can be time-consuming. Therefore, I plan to help you with moving the cookbook categories by adding myself to enabledusers and enabledbots in [[Wikibooks:AutoWikiBrowser/CheckPageJSON]]. Would this be fine if I assist you and to add myself to the check page? I am familiar with using AWB after testing on a non-Wikimedia project. Thank you. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 04:42, 8 June 2025 (UTC)

:Hi @[[User:Codename Noreste|Codename Noreste]]—thank you for the tip! I just installed JWB, so this should make my mass cat changes much faster. Thanks again! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 13:11, 8 June 2025 (UTC)
:: Thank you for the information. Also, is it okay if I change (for example) [[:Category:Vinegar recipes]] to [[:Category:Recipes using vinegar]] (I can redirect the former category to the latter), given that we should move {{tq|Category:[ingredient] recipes}} to {{tq|Category:Recipes using [ingredient]}} for consistency? [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 16:57, 8 June 2025 (UTC)
:::Sure thing—go ahead! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 17:53, 8 June 2025 (UTC)

== Tool for even faster category changes ==

See [[:c:Help:Gadget-Cat-a-lot#As_your_user_gadget]]. I just [https://en.wikibooks.org/w/index.php?title=User:Koavf/common.js&amp;action=history installed it] and used it dozens of times in a click. Let me know if you need any help. —[[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; 00:36, 19 June 2025 (UTC)

:@[[User:Koavf|Koavf]] Thanks! I'm having a little trouble activating it, but I'll keep trying. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:54, 19 June 2025 (UTC)
::A lot of times, a purge will do the trick. See [[:mw:Purge]]. Usually just &lt;kbd&gt;Ctrl+Shift+R&lt;/kbd&gt; once or twice. —[[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; 00:55, 19 June 2025 (UTC)
:::Took several purges, but we're set now! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:16, 19 June 2025 (UTC)

== Advice on when I should run for adminship ==

Hi, I hope you are doing well. I am asking for some advice on when I should run for enwikibooks adminship, given the following below:

Currently, I am doing some optimizations for dark mode on this project, and some of the message box/MediaWiki interface/template pages might be outdated, fully protected, or can use a little help using mw-parser-output. These unfortunately might hinder the process of updating these pages/templates for Vector 2022's dark mode.&lt;br&gt;
Additionally, I have a solid expertise with edit filters, as I have requested some administrators to update deprecated filter variables, switching filters from warn and disallow to disallow only, and I can also monitor the filter log for potential false positives (from local or global filters).

A fellow English Wikibooks administrator also said to me that they are willing to support me in a few months when I run for adminship, as I am generally trusted.

I hold two advanced global permissions, and I hold an edit filter helper permission on the English Wikipedia, to be sure. Thank you for your consideration. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 01:02, 23 June 2025 (UTC)

:Hi @[[User:Codename Noreste|Codename Noreste]]—good question! I agree that you are a trusted user, and I think it would be reasonable for you to run for adminship, especially given our need to fix up technical aspects of the project. If you don't plan to commit to Wikibooks long-term (i.e. you have some projects you'd like to take a few months to complete and then be done), you can always request temporary adminship. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 17:30, 23 June 2025 (UTC)
:: Thank you for your feedback, but I also plan to monitor for vandalism/spam, and to commit to reduce the administrative assistance reading room backlog, should I be elected for adminship (and I forgot to mention those). Anyway, regarding your feedback, I might run by August or even July, given that I've lately started contributing more often to Wikibooks. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 18:29, 23 June 2025 (UTC)
::: [[User:Kittycataclysm|Kittycataclysm]], I am pinging you one more time to see if you have read my response above yours. Thank you. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 16:34, 26 June 2025 (UTC)
::::Hi @[[User:Codename Noreste|Codename Noreste]]! I'm not sure what you mean—was there an additional question you had? Everything you've outlined seems quite reasonable. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:26, 26 June 2025 (UTC)
::::: Apologies for the confusion, I don't have any questions to ask. I was clarifying that I can help with implementing edit requests and to block obvious vandals and spammers, aside from the skills I mentioned earlier. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 18:32, 26 June 2025 (UTC)

== how is it you feel able to interfere in my sandbox? ==

you deleted a page in my sandbox that was my way of providing my response to a request from an OpenSCAD dev team leader for a couple of text blurbs for use on a web page of the OpenSCAD site.

now that you have deleted my page i have to recreate the texts from a screenshot to be able to offer the suggestions, which i will 

This kind of high handed treatment is what keeps me from being a wiki-anything contributor .. If it is Wiki policy to interfere in the documentation of an open source project because it is hosted on Wikibooks then i will take up the task of moving our online docs to a site where you cannot interfere.
--
[[User:VulcanWikiEdit|VulcanWikiEdit]] ([[User talk:VulcanWikiEdit|discuss]] • [[Special:Contributions/VulcanWikiEdit|contribs]]) 21:56, 29 June 2025 (UTC)

:Hi @[[User:VulcanWikiEdit|VulcanWikiEdit]]—thanks for bringing this to my attention. I now understand that this was intended to be in your user namespace—I've undeleted it and moved it to the correct namespace for you. Let me know if anything else comes up! Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:05, 30 June 2025 (UTC)
::ah .. err .. umm .. well that is a gentle answer to my ire. Thanks for being so gracious [[User:VulcanWikiEdit|VulcanWikiEdit]] ([[User talk:VulcanWikiEdit|discuss]] • [[Special:Contributions/VulcanWikiEdit|contribs]]) 20:29, 30 June 2025 (UTC)
::and .. isn't my sandbox in my namespace by default? [[User:VulcanWikiEdit|VulcanWikiEdit]] ([[User talk:VulcanWikiEdit|discuss]] • [[Special:Contributions/VulcanWikiEdit|contribs]]) 20:30, 30 June 2025 (UTC)
:::No worries—it looks like you didn't add the prefix &quot;User:&quot; before writing out the full page titles, so the pages you created were technically in the project's Main space with the official published materials. Going forward, you can just double-check that the page title starts with &quot;'''User:'''VulcanWikiEdit/sandbox&quot;, and that should keep everything in the right place! Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 21:36, 30 June 2025 (UTC)
::::BTW .. i love the play on cat lover name [[User:VulcanWikiEdit|VulcanWikiEdit]] ([[User talk:VulcanWikiEdit|discuss]] • [[Special:Contributions/VulcanWikiEdit|contribs]]) 15:35, 1 July 2025 (UTC)
:::::Thank you! That's very kind. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:46, 1 July 2025 (UTC)

== Regarding the user Codename Tameirao ==

Could this be Matthew again (the Unicode LTA)? I believe it might be him based on his usage of edit summaries, and his usual edits to [[Unicode/Versions]]. I just blocked his recent account, and then I protected and stabilized that Unicode book. &lt;span style=&quot;font-family:Verdana&quot;&gt;[[User:Codename Noreste|&lt;span style=&quot;color:#0024FF&quot;&gt;'''''Codename Noreste'''''&lt;/span&gt;]] ([[User talk:Codename Noreste|&lt;span style=&quot;color:#A1000E&quot;&gt;talk&lt;/span&gt;]])&lt;/span&gt; 23:51, 12 August 2025 (UTC)

:I suspect you're right! That seems like a reasonable course of action. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:56, 13 August 2025 (UTC)
:: I recently encountered another possible LTA, see [[Special:Contributions/~2025-55706-6]] (as well as [[Unicode/Roadmap Blocks]]). I can email you more details if you want. &lt;span style=&quot;font-family:Verdana&quot;&gt;[[User:Codename Noreste|&lt;span style=&quot;color:#0024FF&quot;&gt;'''''Codename Noreste'''''&lt;/span&gt;]] ([[User talk:Codename Noreste|&lt;span style=&quot;color:#A1000E&quot;&gt;talk&lt;/span&gt;]])&lt;/span&gt; 16:30, 9 September 2025 (UTC)
:::I think this is the same LTA, yes! I've protected [[Unicode/Roadmap Blocks]], but I think it would be a good idea if we could automate this monitoring somewhat using the edit filter. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:07, 9 September 2025 (UTC)
:::: I don't think that was Matthew, as he typically uses edit summaries. The deleted page was not protected, as it was protected before you deleted it; I salted it from creation for one year. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 20:22, 9 September 2025 (UTC)
::::: You might want to look at [[Special:Contributions/Freddy Fazbearing Others]]. '''[[User:Codename Noreste|&lt;span style=&quot;color:#0024FF&quot;&gt;Codename Noreste&lt;/span&gt;]]''' ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 04:18, 26 October 2025 (UTC)
::::::Thank you! I went ahead and blocked them. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:54, 28 October 2025 (UTC)

== IP block exempt  ==

Hi Kitty,
I currently have IP block exemption on enwiki, Commons and Wikidata as I use VPNs connected to my internet security software. Can you please grant me the right on wikibooks. I have a strong password and use two factor authentication. ''[[User:TarnishedPath|&lt;b style=&quot;color:#ff0000;&quot;&gt;Tar&lt;/b&gt;&lt;b style=&quot;color:#ff7070;&quot;&gt;nis&lt;/b&gt;&lt;b style=&quot;color:#ffa0a0;&quot;&gt;hed&lt;/b&gt;&lt;b style=&quot;color:#420000;&quot;&gt;Path&lt;/b&gt;]]''&lt;sup&gt;[[User talk:TarnishedPath|&lt;b style=&quot;color:#bd4004;&quot;&gt;talk&lt;/b&gt;]]&lt;/sup&gt; 10:51, 22 August 2025 (UTC)

:Hi @[[User:TarnishedPath|TarnishedPath]]! This doesn't sound unreasonable to me, but I think it would be good if you requested at [[Wikibooks:Requests for permissions]] so we can have a discussion—I have not granted this right before. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:50, 23 August 2025 (UTC)
::Kitty, thanks for pointing me in the right direction. ''[[User:TarnishedPath|&lt;b style=&quot;color:#ff0000;&quot;&gt;Tar&lt;/b&gt;&lt;b style=&quot;color:#ff7070;&quot;&gt;nis&lt;/b&gt;&lt;b style=&quot;color:#ffa0a0;&quot;&gt;hed&lt;/b&gt;&lt;b style=&quot;color:#420000;&quot;&gt;Path&lt;/b&gt;]]''&lt;sup&gt;[[User talk:TarnishedPath|&lt;b style=&quot;color:#bd4004;&quot;&gt;talk&lt;/b&gt;]]&lt;/sup&gt; 03:25, 23 August 2025 (UTC)
::See [[Wikibooks:Requests_for_permissions#TarnishedPath_(discuss_·_contribs_·_count_·_logs_·_block_log_·_rfp_·_rights)_(IP_Block_Exemption)]] ''[[User:TarnishedPath|&lt;b style=&quot;color:#ff0000;&quot;&gt;Tar&lt;/b&gt;&lt;b style=&quot;color:#ff7070;&quot;&gt;nis&lt;/b&gt;&lt;b style=&quot;color:#ffa0a0;&quot;&gt;hed&lt;/b&gt;&lt;b style=&quot;color:#420000;&quot;&gt;Path&lt;/b&gt;]]''&lt;sup&gt;[[User talk:TarnishedPath|&lt;b style=&quot;color:#bd4004;&quot;&gt;talk&lt;/b&gt;]]&lt;/sup&gt; 03:35, 23 August 2025 (UTC)
== You've got mail! ==
{{You've got mail|sig=&lt;span style=&quot;font-family:Verdana&quot;&gt;[[User:Codename Noreste|&lt;span style=&quot;color:#0024FF&quot;&gt;'''''Codename Noreste'''''&lt;/span&gt;]] ([[User talk:Codename Noreste|&lt;span style=&quot;color:#A1000E&quot;&gt;talk&lt;/span&gt;]])&lt;/span&gt; 00:20, 6 September 2025 (UTC)}}

:Thank you! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:06, 6 September 2025 (UTC)

== Are you able to import? ==

I made a few requests over at https://en.wikibooks.org/wiki/Wikibooks:Requests_for_import . [[User:2005-Fan|2005-Fan]] ([[User talk:2005-Fan|discuss]] • [[Special:Contributions/2005-Fan|contribs]]) 22:32, 4 October 2025 (UTC)
: [[User:2005-Fan|2005-Fan]], I'll go ahead and start the imports. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 16:29, 5 October 2025 (UTC)
::Thank you for your help [[User:2005-Fan|2005-Fan]] ([[User talk:2005-Fan|discuss]] • [[Special:Contributions/2005-Fan|contribs]]) 16:51, 5 October 2025 (UTC)
::: My apologies for not doing this sooner, because some database error appears when I am trying to mass import. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 23:39, 5 October 2025 (UTC)
::::I also tried to make this import earlier and ran into issues with the software. I was hoping it was a temporary bug, but it seems to be persisting. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:01, 6 October 2025 (UTC)
:::::This seems like I should get involved. {{working}}... [[User:JJPMaster|JJP]]&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:11, 6 October 2025 (UTC)
:::::: I believe there are five pages that have massive page histories they fail to import here. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 15:13, 6 October 2025 (UTC)
:::::::I backed up the XMLs of them locally but im unsure how much that'd do. [[User:2005-Fan|2005-Fan]] ([[User talk:2005-Fan|discuss]] • [[Special:Contributions/2005-Fan|contribs]]) 15:18, 6 October 2025 (UTC)
::::::::Just became an importer. The reason is prob understandable but I cannot upload the XML file to here locally. [[User:2005-Fan|2005-Fan]] ([[User talk:2005-Fan|discuss]] • [[Special:Contributions/2005-Fan|contribs]]) 17:23, 10 October 2025 (UTC)

== About the category parameter in the recipe summary template ==

When it uses a &quot;recipe by type&quot; category, should it use a &quot;[type/food] recipes&quot; name or &quot;Recipes for [type/food]&quot;?

I recently operated JWB to change from [[:Category:Dessert recipes]] to [[:Category:Recipes for dessert]] in multiple Cookbook recipes, and from what I've said before, I've changed to ''Recipes for dessert'' in the category parameter of Cookbook recipes. Hope you don't mind that this was over more than 250 changes (not counting the recent category changes after moving some recipe categories). Thanks. '''[[User:Codename Noreste|&lt;span style=&quot;color:#0024FF&quot;&gt;Codename Noreste&lt;/span&gt;]]''' ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 02:07, 27 October 2025 (UTC)

:Hi @[[User:Codename Noreste|Codename Noreste]]—those JWB changes you made seem fine to me! I'm not quite sure what you're asking in your first sentence, though. Assuming I understand correctly: in general, I think the default format should be whatever the actual category name is. BUT if there is a redirect, it ultimately shouldn't matter too much. And, because I'm not convinced of the utility of that infobox parameter in the first place (thinking of removing it), I'm not hugely concerned about it for the time being. Does this help? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:21, 27 October 2025 (UTC)
:: Probably, but I will say the following below (for my first sentence) to clarify:
:: On the &lt;code&gt;|category =&lt;/code&gt; parameter, when placing a recipe category name, should it either be {{tq|Sandwich recipes}} or {{tq|Recipes for sandwiches}}? I hope this clears the confusion. '''[[User:Codename Noreste|&lt;span style=&quot;color:#0024FF&quot;&gt;Codename Noreste&lt;/span&gt;]]''' ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 18:39, 27 October 2025 (UTC)

== Please no more Unicode LTA ==

Please don't block me again. I promise I will edit Unicode stuff and add correct information. [[Special:Contributions/&amp;#126;2025-30839-28|&amp;#126;2025-30839-28]] ([[User talk:&amp;#126;2025-30839-28|talk]]) 20:54, 1 November 2025 (UTC)
:&lt;small&gt;I am a bit out of the loop, so correct me if I'm wrong - I'm assuming here&lt;/small&gt; I think the point is that they want you to ''not'' edit the Unicode stuff? Also hi kitty, it's been a ... very long time.. &lt;sup&gt;&amp;#8212; [[User:L10nM4st3r|&lt;span style=&quot;color:#c71300&quot;&gt;L10nM4st3r&lt;/span&gt;]]&lt;/sup&gt; / &lt;sub&gt;[[User talk:L10nM4st3r|&lt;span style=&quot;color:#ce3f00&quot;&gt;'''ROAR''' at me!&lt;/span&gt;]]&lt;/sub&gt; 01:13, 5 November 2025 (UTC)
::Ok so apparently not as long as I thought, but it feels like I've been away for at least a year lol &lt;sup&gt;&amp;#8212; [[User:L10nM4st3r|&lt;span style=&quot;color:#c71300&quot;&gt;L10nM4st3r&lt;/span&gt;]]&lt;/sup&gt; / &lt;sub&gt;[[User talk:L10nM4st3r|&lt;span style=&quot;color:#ce3f00&quot;&gt;'''ROAR''' at me!&lt;/span&gt;]]&lt;/sub&gt; 01:23, 5 November 2025 (UTC)
:::Nice to see you! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 15:41, 5 November 2025 (UTC)

== Administrator and reviewer user right combinations are not needed anymore ==

Given that administrators can review edits in addition to reviewers, I would suggest for you (and other administrators) to kindly remove the reviewer permission from (own) accounts. What I'm saying is that if one holds administrator and reviewer permissions together, they can remove the reviewer permission from their own account and retain their administrator permission. Thanks. [[User:Codename Noreste|&lt;span style=&quot;color:#0024FF&quot;&gt;Codename Noreste&lt;/span&gt;]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 16:06, 11 November 2025 (UTC)

:Gotcha—is there a reason it's bad for one user to have both these rights? If so, I can remove my reviewer right. Otherwise, it seems fairly harmless? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 19:26, 11 November 2025 (UTC)
:: The thing is, administrators have the &lt;code&gt;review&lt;/code&gt; user right, as well as some permissions in the reviewer user group in the administrator toolset. That means that having the reviewer user group together with the admin user group is redundant. Hope this explains it. [[User:Codename Noreste|&lt;span style=&quot;color:#0024FF&quot;&gt;Codename Noreste&lt;/span&gt;]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 19:59, 11 November 2025 (UTC)
::: @[[User:Kittycataclysm|Kittycataclysm]] &lt;s&gt;I'll do this tomorrow morning, as well as to remove autoreviewed user permissions from users who are reviewers.&lt;/s&gt; ({{doing}}) [[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]]) 03:24, 12 November 2025 (UTC)
: I have removed the autoreviewed user permission from users who are reviewers. As for administrators, I will do so later today. [[User:Codename Noreste|&lt;span style=&quot;color:#0024FF&quot;&gt;Codename Noreste&lt;/span&gt;]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 03:40, 13 November 2025 (UTC)

== Nesting in Open Book of Ecovillages and Eco Communities  ==

Hi Kittycataclysm,

I am editor of wikipedia since 2004. We have the habit if we have a concern using the talk page to clarify the case. I am not sure to delete meaningful content without previous notification and doing major redirection without agreeing the main contributor(s) is an adequate admin act and sign of good manner of host (see [[W:Wikipedia:Etiquette|Wikipedia:Etiquette]].)

Yes, It will be not an average book but above the regular. This is the exact case: ''&quot;this may be appropriate, such as with large textbooks that contain subsections with a lot of content.&quot;'' ''for to establish good structural and stylistic practices''

I have a data management certification. If you asking it will have 4 nest level on strict purpose. If you saw the introduction of the [[Open Book of Ecovillages and Eco Communities]] is/will be a global collection making effective collaboration over borders and continents. One structured + categorized(!) page for each community willing to show up. The Postal addresses has also same or larger deepness, this is unavoidable (Country/Postal Code/Location/Street/House/floor/door). Here will looks like: '''Eco-comm/Continent/Regio code/Community name'''

The goal of this system to open bridge + experience highway  for the communities using the same permaculture technics what collected parallelly in [[Open Book of Permaculture]]. That is also part of this knowledge base please dont do simplification steps on that without discussion.

I am kindly asking to revert your edits in this book.

After that I will put a notification template  about 
 &quot;This book is under construction with major changes. Before contributing, please discuss and align your work with at least one of the main contributors listed in the Page History. Common clarifications/ guides are on the primary talk page.&quot;


Thanks: [[User:Rodrigo|Rodrigo]] ([[User talk:Rodrigo|discuss]] • [[Special:Contributions/Rodrigo|contribs]]) 02:22, 12 November 2025 (UTC)

:Hi @[[User:Rodrigo|Rodrigo]], and thank you both for your contributions and for reaching out! Yes, I did make the following changes to [[Open Book of Ecovillages and Eco Communities]]:
:* I moved the pages from the [[Eco-comm]] namespace to the [[Open Book of Ecovillages and Eco Communities]] namespace, since the table of contents and pages for a given book should be under that book's namespace.
:* I removed the links to Wikipedia that were on [[Open Book of Ecovillages and Eco Communities]], since outlinking has been discouraged at en.Wikibooks as a matter of practice. Compilations of links may not fall into WB scope as an instructional text, and [[Wikibooks:Requests for deletion/Piano Solo Music: An Encyclopedia|there is precedent for deleting them]]. But, I do see that the tool I used didn't just remove links to enWP, so I will restore the prior revision and ping the tool developer.
:* I flagged it as needing denesting—you're right that nested entries can sometimes be appropriate. In this case, I was primarily flagging for a denest because the table of contents needs to be moved onto the main page, and it shouldn't have hidden navigation within the nested portions.
:Could you clarify which of these edits you do not agree with so I can make sure they are individually addressed? As an aside, it could be helpful to create a [[Help:Local manuals of style|local manual of style]] for the book in order to clearly outline the expectations. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:59, 12 November 2025 (UTC)
::My main concern not about moving and flagging but '''deleting''' [[Eco-comm]] against [[Wikibooks:Deletion policy]] and not mentioning in the clarification even after my notification. Should I note all administrators [[Wikibooks:Please do not bite the newcomers]] - or will they do speedy deleting one by one until I make them individually addressed?
:::The &lt;u&gt; local manual of style&lt;/u&gt; development is ongoing together with the sample pages.
::'''MAIN PAGE'''
::The '''Main page''' and '''Namespace''' is the [[Eco-comm]]. The '''Full Title''' or '''Cover''' is [[Open Book of Ecovillages and Eco Communities]]. Because of the high level of nesting the below extra-long-full-text-title to be avoided the Cover page is a redirection with preface/intro etc.
::'''NESTING '''
:::Featured book with 3 level nesting: [[Social and Cultural Foundations of American Education/Educational Change/Theory]]
:::5 level nesting example: [[Development Cooperation Handbook/Designing and Executing Projects/Communication Management/Communication Planning/Develop a Conflict Management Strategy]]
::'''Categories''' The [[:Category:Eco-comm]] will let the users make practical sub-categories e.g. [[:Category:Eco-comm/Project/numundo]] [[:Category:Eco-comm/]]
:::
::[[User:Rodrigo|Rodrigo]] ([[User talk:Rodrigo|discuss]] • [[Special:Contributions/Rodrigo|contribs]]) 03:44, 18 November 2025 (UTC)
:::Thank you for elaborating! I'm unfortunately not sure what you mean about deleting [[Eco-comm]]—are you referring to the fact that I moved it without leaving a redirect? Regarding the nesting, I do honestly think those other books you linked should have their navigation denested since I find their format difficult to parse, and they have some navigation issues. Looping in some other active admins (@[[User:Leaderboard|Leaderboard]] @[[User:MarcGarver|MarcGarver]] @[[User:JJPMaster|JJPMaster]] @[[User:Codename Noreste|Codename Noreste]] (@[[User:SHB2000|SHB2000]]) so they can get eyes on this and voice anything they think is important. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 04:12, 18 November 2025 (UTC)
::::It makes no sense to have some crazy abbreviation as a &quot;main page&quot; or &quot;namespace&quot; (whatever that means in this context) for a book in order to allow it to be deep nested. Nobody needs to type the whole name of the nesting because that's what navigation templates do, and it is a simple matter to override the page title. I also take issue with the statement, above, &quot;Before contributing, please discuss and align your work with at least one of the main contributors listed in the Page History.&quot; Anybody can edit, and nobody gets to own and control any work. Taken together, this complaint looks like a case of attempting to assert ownership and to operate against the normal practices of Wikibooks. As such, I am completely aligned with the changes made. [[User:MarcGarver|MarcGarver]] ([[User talk:MarcGarver|discuss]] • [[Special:Contributions/MarcGarver|contribs]]) 12:49, 18 November 2025 (UTC)
:::::That. [[User:Leaderboard|Leaderboard]] ([[User talk:Leaderboard|discuss]] • [[Special:Contributions/Leaderboard|contribs]]) 14:59, 18 November 2025 (UTC)
::::Thanks @[[User:MarcGarver|MarcGarver]]@[[User:Leaderboard|Leaderboard]] for the contribution, btw the [[Development Cooperation Handbook/Designing and Executing Projects/Communication Management/Communication Planning/Develop a Conflict Management Strategy]] also looks crazy long, is'nt it? Lets continue in the [[Wikibooks:Reading_room/General]] keeping this page for personal messages. [[User:Rodrigo|Rodrigo]] ([[User talk:Rodrigo|discuss]] • [[Special:Contributions/Rodrigo|contribs]]) 23:07, 20 November 2025 (UTC)

== Deletions of Wikibook subpages ==

Hello @[[User:Kittycataclysm|Kittycataclysm]],

regarding the [[Thesis Writing Guide]] subpage deletions, should I just recreate them when I keep working on them or was there an automatic deletion that we could undo? This document will grow, but really slowly.

Best,
Tim [[User:TimBorgNetzWerk|TimBorgNetzWerk]] ([[User talk:TimBorgNetzWerk|discuss]] • [[Special:Contributions/TimBorgNetzWerk|contribs]]) 11:37, 16 December 2025 (UTC)

:Hi @[[User:TimBorgNetzWerk|TimBorgNetzWerk]]! Since there was so little content on the deleted pages, my recommendation would just be for you to gradually recreate the chapters as you go. Does that make sense? Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 19:54, 17 December 2025 (UTC)
::Makes sense, not my ideal solution, but also not far from it :) The end result will be the same, the in-between will just feel a little bit weird from time to time.
::Thank you for taking time to curate and quality-control Wikibooks - wishing wonderful holidays and a happy new year! [[User:TimBorgNetzWerk|TimBorgNetzWerk]] ([[User talk:TimBorgNetzWerk|discuss]] • [[Special:Contributions/TimBorgNetzWerk|contribs]]) 20:43, 17 December 2025 (UTC)
:::Thank you, and happy holidays to you as well :) —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 23:13, 17 December 2025 (UTC)

== help with &quot;Media Literacy and You&quot; == 

{{re|Kittycataclysm}} What do I need to do to get a quality review of ''[[Media Literacy and You]]'', or whatever is needed to remove &lt;nowiki&gt;{{Qr-em|not clear how this is to be structured as a book}}&lt;/nowiki&gt;? 

I ask, because you added that flag just over 2 hours after I created it. I later found that I had accidentally created it as an anonymous user. I've since started using my standard Wikiname, and I tried to respond to the requests both by creating a discussion on the &quot;Discussion&quot; page associated with that book and by upgrading the content. 

The upgrades included adding the &quot;Introduction&quot; chapter by revising an article on Wikiversity that convinced me to start this Wikibook. I have other articles that I plan to rewrite to create 9 of the remaining 11 chapters in the current table of contents, as indicated in this table of contents. 

??? Thanks, [[User:DavidMCEddy|DavidMCEddy]] ([[User talk:DavidMCEddy|discuss]] • [[Special:Contributions/DavidMCEddy|contribs]]) 02:23, 8 February 2026 (UTC)

:Hi @[[User:DavidMCEddy|DavidMCEddy]]! I removed the query flag, since this is clearly not a test page. I do have concerns about the suitability of this book for Wikibooks, since it seems to be more in line with essays and original research/analysis (which are [[Wikibooks:WIW|out of scope here]]). Wikiversity seems like a very suitable place for them—is there a specific reason you want to move them here? Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 16:24, 8 February 2026 (UTC)

::{{re|Kittycataclysm}} 
::This book is intended to accelerate the diffusion of [[w:Media literacy|media literacy]] by making it easier for humans to (a) access training materials and (b) connect with research on the most important issues that concern them and (c) discuss those issues with others who may believe differently in a nonthreatening context that encourages dialogue and a shared search for what can honestly be said about any particular issue. This is an extension of &quot;The wisdom of polarized crowds&quot; discussed in [[Wikipedia:Reliability of Wikipedia]]. 

::I don't know about you, but I'm frightened by the collapse of nuclear arms control agreements since the year 2000, by global warming, by the threats of the Trump administration to invade Canada and Greenland, etc. If this book project is successful, it will make a material contribution to reversing these trends -- unless this kind of dialogue is [[v:Responding to a nuclear attack|interrupted by a nuclear war]]. 

=== Who is DavidMCEddy ===

::I'm a [[w:Vietnam veteran|Vietnam-era veteran]] with a PhD in statistics and a publication record for which [https://www.researchgate.net/profile/Spencer-Graves-3 ReserchGate has found over 1,200 academic publications that have cited my work.] Since  [https://xtools.wmcloud.org/ec/en.wikipedia.org/DavidMCEddy 2010 I have logged]
*  6,000+ edits in each of Wikipedia and Wikiversity, 
*  1,000+ in Wikimedia Commons, 
* 30,000+ in Wikidata, and 
* almost 1,000 in other Wikimedia Foundation projects like Wikiquote and edits to the Spanish, French and German Wikipedias. 

This includes dozens of research reports posted to Wikiversity under [[v:Category:Freedom and abundance]] and 44 posts under [[v:Category:Media reform to improve democracy]] that provide a platform for documenting and discussing 44 episodes of a fortnightly &quot;Media &amp; Democracy&quot; series of 29:00 mm:ss podcasts syndicated for the [https://pacificanetwork.org/stations-2/ Pacifica Radio Network] featuring the opinions of leading experts on the increase in political polarization and violence and what those experts think should be done about this. 

I've just posted another chapter to [[Media Literacy and You/The impact of the media on political economy since the time of the Pharaohs]]. I hope you will agree that this book can make a positive contribution to Wikibooks and to [[w:Jimmy Wales|Jimbo Wales]]' [[w:Wikipedia:Prime objective|Prime Directive]] to create &quot;a world in which every single person on the planet is given free access to the sum of all human knowledge.&quot; Thanks, [[User:DavidMCEddy|DavidMCEddy]] ([[User talk:DavidMCEddy|discuss]] • [[Special:Contributions/DavidMCEddy|contribs]]) 01:19, 9 February 2026 (UTC)

:@[[User:DavidMCEddy|DavidMCEddy]] Thank you and I understand this, but I am asking why you think this material is more suitable at Wikibooks rather than at Wikiversity. From what I can see, Wikiversity seems like the more appropriate home for it given our [[Wikibooks:WIW|scope]]. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:59, 9 February 2026 (UTC)

::{{re|Kittycataclysm}} 

::&quot;Media Literacy and You&quot; is textbook to support both self study and classes on media literacy. 

::I have been posting content to Wikiversity since 2014 and have not encountered support there for books. A search just now turned up a hint of a book on Wikiversity, but I could not easily find anything on how to do it, etc.  

::I think this &quot;Media Literacy and You&quot; project would lose the vast majority of its potential if it were not on Wikibooks. 

::??? Thanks, [[User:DavidMCEddy|DavidMCEddy]] ([[User talk:DavidMCEddy|discuss]] • [[Special:Contributions/DavidMCEddy|contribs]]) 02:22, 9 February 2026 (UTC)

{{outdent}}

{{re|Kittycataclysm}} 
Will you please help me with the protocols of creating a book on Wikiversity? 

1. I have found documentation that claims that Wikiversity supports such. However, the documentation seems incomplete, potentially out of date, etc. For example, I could not see how to follow the instructions for [[Wikiversity:Help:Books#Step 1: Enable the &quot;Book creator&quot; tool]]. So I posted a question to [[Wikiversity:Help talk:Books]]. 

2. What do you suggest I do next? 

:I can create an article on Wikiversity titled, &quot;Media Literacy and You&quot;, and port everything I've posted to Wikibooks there, then replace the pages on Wikibooks with redirects to [[Wikiversity:Media Literacy and You]], [[Wikiversity:Media Literacy and You/Introduction]], and [[Wikiversity:Media Literacy and You/The impact of the media on political economy since the time of the Pharaohs]]. 

:If you think that's the best way to build this book project, great. It would actually be easier for me, because there would be less translation between what I already have on Wikiversity and a version for Wikibooks. (Also, Wikiversity supports &lt;nowiki&gt;{{cite Q|...}}&lt;/nowiki&gt;, which I have used extensively for years.) 

:Thanks for your help. [[User:DavidMCEddy|DavidMCEddy]] ([[User talk:DavidMCEddy|discuss]] • [[Special:Contributions/DavidMCEddy|contribs]]) 13:26, 9 February 2026 (UTC)

:@[[User:DavidMCEddy|DavidMCEddy]] Unfortunately, I am not familiar with the exact workings of Wikiversity, so I can't be much help there. My personal recommendation is that you ask there for help on how best to structure your materials to match the WV requirements. If you'd like some additional opinions/insight, please feel free to also check in at the [[Wikibooks:Reading room/General|reading room]]. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 02:22, 10 February 2026 (UTC)

::{{re|Kittycataclysm}} I believe I have finished migrating all of ''Media Literacy and You'' to Wikiversity and replacing the parts of it on Wikibooks with redirects. Comments? Thanks, [[User:DavidMCEddy|DavidMCEddy]] ([[User talk:DavidMCEddy|discuss]] • [[Special:Contributions/DavidMCEddy|contribs]]) 17:32, 10 February 2026 (UTC)

== Thank you!  ==

Heya, thanks for reviewing my stuff! Just to note, the first lesson page was done and so that'll need moving. If you want to discuss anything with me, I am easily reachable on Discord @ xiluosi233. I can explain philosophy, approach, and so on from my teaching experience if you want anything regarding that. [[User:Shira the Mogul|Shira the Mogul]] ([[User talk:Shira the Mogul|discuss]] • [[Special:Contributions/Shira the Mogul|contribs]]) 19:48, 17 February 2026 (UTC)

:It appears [[An Introduction to the Han Script]] was moved wrong - should it not be [[General Literary Chinese from Scratch/An Introduction to the Han Script]]? [[User:Shira the Mogul|Shira the Mogul]] ([[User talk:Shira the Mogul|discuss]] • [[Special:Contributions/Shira the Mogul|contribs]]) 19:52, 17 February 2026 (UTC)
::@[[User:Shira the Mogul|Shira the Mogul]] good catch! I accidentally removed more of the title than intended. I've fixed this now. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 13:18, 18 February 2026 (UTC)

== A test request ==

Just to see whether a recent Luna update turned out as intended, could you briefly revert your [[User:Kittycataclysm/lunaoptions.json|Luna preferences page]] to the first revision? Since you don't appear to have any custom preferences in the first place, I don't think there should be any conflicts. [[User:JJPMaster|JJP]]&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]]) 01:49, 30 March 2026 (UTC)

:Done! But, it seems to have perhaps auto-updated again immediately afterwards. —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 15:39, 10 April 2026 (UTC)

== Linking ==
Hi,&lt;br&gt;
For my edification, why is a link from [[Cookbook:nettle|nettle]] to [[w:Urtica_dioica|Urtica dioica]] not appropriate? The Wikipedia article has more information &amp; seems relevant.&lt;br&gt;
Thanks, ... [[User:PeterEasthope|PeterEasthope]] ([[User talk:PeterEasthope|discuss]] • [[Special:Contributions/PeterEasthope|contribs]]) 01:53, 24 April 2026 (UTC)

:@[[User:PeterEasthope|PeterEasthope]] good question! Wikibooks discourages outlinking, since books should be self-contained units. Instead of linking to [[w:Urtica dioica]], the correct approach would be to flesh out the actual chapter here at Wikibooks. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 17:34, 24 April 2026 (UTC)
::Should all material in the Wikipedia article about Urtica dioica relevant to cooking be duplicated into the nettle article in the cookbook? Thanks, ... [[User:PeterEasthope|PeterEasthope]] ([[User talk:PeterEasthope|discuss]] • [[Special:Contributions/PeterEasthope|contribs]]) 02:30, 2 May 2026 (UTC)
:::@[[User:PeterEasthope|PeterEasthope]] you could do that, although you should only include information that is sourced. However, I recommend that you wait, because I am coincidentally working on the page right now and fleshing it out significantly. I should publish today. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 21:40, 2 May 2026 (UTC)
::::The nettle page is better now. Thanks.
::::I still wonder, given that the link to ''The Complete Guide to Edible Wild Plants, ...'' is permitted, why not a link to the botanically oriented page in Wikipedia. What if someone reads the Cookbook article and is interested in the toxin for example? Seems that non-Wikimedia references are more privileged than Wikimedia references.
::::Also, by chance, just noticed the [[w:Nettle_soup|Nettle soup]] article in Wikipedia. Better in the Cookbook?
::::Thx, ... [[User:PeterEasthope|PeterEasthope]] ([[User talk:PeterEasthope|discuss]] • [[Special:Contributions/PeterEasthope|contribs]]) 19:10, 5 May 2026 (UTC)
:::::Another good question. The reason those books are linked is because they are reputable and topical sources for the subject matter (nettles as used in cooking from an instructional perspective), and the links are part of the citations—this makes it different from a simple outlink to a Wikipedia page. Wikipedia pages should also not be cited themselves as sources. Regarding nettle soup, I don't think it makes sense to have that as a standalone page here in the cookbook due to its encyclopedic tone, and I don't see any recipes there. Does this make sense? —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 00:21, 6 May 2026 (UTC)
::::::Somewhat. Certainly a recipe wouldn't be incongruous in a cookbook. Still seems unhelpful that relevant information in Wikipedia is inaccessible from a Wikibook. In effect there's a &quot;Berlin Wall&quot; between two Wikimedia projects. Would a &quot;See also&quot; section be permissible?
::::::Thanks, ... [[User:PeterEasthope|PeterEasthope]] ([[User talk:PeterEasthope|discuss]] • [[Special:Contributions/PeterEasthope|contribs]]) 14:00, 7 May 2026 (UTC)

== You may be an eligible candidate for the U4C election ==

&lt;div lang=&quot;en&quot; dir=&quot;ltr&quot; class=&quot;mw-content-ltr&quot;&gt;
Greetings,

The [[m:Special:MyLanguage/Universal_Code_of_Conduct/Coordinating_Committee|Universal Code of Conduct Coordinating Committee (U4C)]] seeks candidates for the 2026 election. The U4C is the global committee responsible for overseeing enforcement of the [[foundation:Special:MyLanguage/Policy:Universal Code of Conduct|Universal Code of Conduct]]. Elections are held annually, if elected a committee member serves for two years.

This year the U4C requires candidates to hold administrator rights on at least one wiki, which is why you are being contacted as you appear to hold this right. There are other requirements, such as candidates must be at least 18 years old and may not be employed by the Wikimedia Foundation or other related chapters and affiliates. You can find more information in the [[m:Special:MyLanguage/Universal_Code_of_Conduct/Coordinating_Committee/Election/2026#Call_for_Candidates|call for candidates on Meta-wiki]]. Additionally, the committee's working language is English; some ability to communicate in English is required.

The election opens on 18 May, if you are eligible and interested you have until 10 May to submit your candidacy. There will week between for candidates to answer questions from the community. Voting takes place privately in [[m:Special:MyLanguage/SecurePoll|SecurePoll]], successful candidates must receive at least 60% support. More information is available on [[m:Special:MyLanguage/Universal_Code_of_Conduct/Coordinating_Committee/Election/2026|the 2026 Elections page]], including timelines and other candidacy information. If you read over the material and consider yourself qualified, please consider submitting your name to run for the committee. If you think someone else in your community might be interested and qualified, please encourage them to run.

In partnership with the U4C -- [[m:User:Keegan (WMF)|Keegan (WMF)]] ([[m:User_talk:Keegan (WMF)|talk]]) 18:32, 28 April 2026 (UTC) &lt;/div&gt;
&lt;!-- Message sent by User:Keegan (WMF)@metawiki using the list at https://meta.wikimedia.org/w/index.php?title=User:Keegan_(WMF)/test&amp;oldid=30471751 --&gt;

== Undeletion request ==

Hello,


I am writing to request an undeletion of the page Saumya Pandya Thakkar, Shakuntala Pandya and the Pedestrians of Ahmedabad. You stated you are a frequent visitor of the Lentis page and are thus familiar with it. This page was part of a class assignment and was in progress at the time of deletion. The work deleted is what we will be graded on for our class, so we would appreciate the restoration. [[User:Yqj3km|Yqj3km]] ([[User talk:Yqj3km|discuss]] • [[Special:Contributions/Yqj3km|contribs]]) 19:36, 4 May 2026 (UTC)

:@[[User:Yqj3km|Yqj3km]] see my response below regarding undeletion. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:15, 4 May 2026 (UTC)

== Undeletion request ==

About the page on Lentis called Saumya Pandya Thakkar, Shakuntala Pandya and the Pedestrians of Ahmedabad: I, too, request undeletion, please. If the authors made any msitakes, the fault is 100 percent mine, for failing to guide them correctly. Like all chapters in this book, this team's chapter is a class assignment. I will be interested also in the reason for deletion so that I can guide authors better. I want to help my students be constructive contributors. Many thanks!

[[User:Norton|Norton]] ([[User talk:Norton|discuss]] • [[Special:Contributions/Norton|contribs]]) 20:03, 4 May 2026 (UTC)

:Hi @[[User:Norton|Norton]] and thanks for the ping! I deleted it because it was not titled/filed correctly, so I didn't realize it was part of [[Lentis]]. I have undeleted it and moved it to [[Lentis/Saumya Pandya Thakkar, Shakuntala Pandya and the Pedestrians of Ahmedabad]]. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 22:14, 4 May 2026 (UTC)
::Many, many thanks, @[[User:Kittycataclysm|Kittycataclysm]]! I am very grateful as always for everything you do for Wikibooks!
::[[User:Norton|Norton]] ([[User talk:Norton|discuss]] • [[Special:Contributions/Norton|contribs]]) 22:27, 4 May 2026 (UTC)

== Log in issues ==

Hi, messaging you as you seem to be the most active admin at the moment. I can't log in (as posted at  &lt;bdi&gt;[[Wikibooks:Reading room/Administrative Assistance]] and also on my WP page at&lt;/bdi&gt; [[w:User_talk:Xania]]). Seems to be an issue with extra security for admins? I am asked to use my authenticator app (which I can't as I have never set it up for Wikibooks) or a recovery code (which I don't have). Any idea what I should do in this situation? Xania [[Special:Contributions/&amp;#126;2026-28255-89|&amp;#126;2026-28255-89]] ([[User talk:&amp;#126;2026-28255-89|talk]]) 18:21, 10 May 2026 (UTC)

:Apologies for missing this yesterday! It seems like we have a few people working on it over in the reading room, and I'll keep track there. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 16:37, 11 May 2026 (UTC)

== Splitting pages ==
FYI, I untagged [[Art Print Production Methods]] as for splitting: the page is rather small with its 20 KB and does not need splitting, in my view. Ideally, there would be an operationalized, fairly detailed policy on the matter, but I do not know of one. Single-page books are in [[:Category:One-page books]]. --[[User:Dan Polansky|Dan Polansky]] ([[User talk:Dan Polansky|discuss]] • [[Special:Contributions/Dan Polansky|contribs]]) 04:45, 20 May 2026 (UTC)

== &lt;s&gt;Slander&lt;/s&gt; ==

&lt;S&gt;Your tag is slanderous and very easily proven wrong.&lt;/s&gt;[https://en.wikibooks.org/w/index.php?title=Five_Rules_for_Meaningful_Living&amp;diff=prev&amp;oldid=4654455] Given you likely didn't bother to look at the edit history, I would remind you that your given reason that you think it was AI is because you see the chapter is &quot;numbered&quot;. That however was 100% my own personal decision after I reviewed my work and thought to myself that I later wrote in the introduction that there is a first to fourth chapter. However I thought to myself that the readers would not be easily made aware of what is meant by first to fourth as I didn't number them - so is why I dedicated an entire edit to make it less ambiguous  [https://en.wikibooks.org/w/index.php?title=Five_Rules_for_Meaningful_Living&amp;diff=prev&amp;oldid=4654328]. I should not have to be falsely penalized because I wanted to be more considerate and ensure better clarity. I do however request AI to help me figure out coding like this - [https://en.wikibooks.org/w/index.php?title=Five_Rules_for_Meaningful_Living&amp;diff=prev&amp;oldid=4654329] as I don't know how to link. But I intentionally take great efforts to not rely on AI to write that book and find your wrongful presumptions troubling. [[User:JaredMcKenzie|JaredMcKenzie]] ([[User talk:JaredMcKenzie|discuss]] • [[Special:Contributions/JaredMcKenzie|contribs]]) 06:00, 15 July 2026 (UTC)

:@[[User:JaredMcKenzie|JaredMcKenzie]] thank you for clarifying! I flagged it for review because it matched a common pattern we see associated with LLM use here. If that is not the case, then nothing needs to happen in that respect; however, you will likely want to fix the lists so that they are correctly formatted in the Wikitext and not hard-written—let me know if you have any questions about that. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 18:14, 16 July 2026 (UTC)
::Yeah, I don't instantly understand what you mean by &quot;correctly formatted&quot; list. At first, I assumed you were referring to chapter 4 - (''Further reading'')? But I think I know what you mean. I made this edit here [https://en.wikibooks.org/w/index.php?title=Five_Rules_for_Meaningful_Living&amp;diff=prev&amp;oldid=4654738] to align with how I see wikibooks typically do lists. Did I fix it? If not, feel free to clarify.[[User:JaredMcKenzie|JaredMcKenzie]] ([[User talk:JaredMcKenzie|discuss]] • [[Special:Contributions/JaredMcKenzie|contribs]]) 18:35, 16 July 2026 (UTC)
::I thought about how I responded earlier. Even tho I still disagree, I probably shouldn't have used such a tone. I imagine admins like yourself do a lot of work overseeing wiki and the project owes a lot to you guys. So I take back my harsh words, and I hope we're good.[[User:JaredMcKenzie|JaredMcKenzie]] ([[User talk:JaredMcKenzie|discuss]] • [[Special:Contributions/JaredMcKenzie|contribs]]) 03:38, 17 July 2026 (UTC)
:::@[[User:JaredMcKenzie|JaredMcKenzie]] I appreciate that—thank you! And thank you for [[Special:Diff/4654738|making those changes to the lists]], which was indeed what I was referring to. Happy editing! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 13:31, 17 July 2026 (UTC)

== The Geoguide ==

I literally wrote all of this myself I used no AI if you want to you can highlight the areas that seem way too formal and ill fix them [[User:Kayden Swanson|Kayden Swanson]] ([[User talk:Kayden Swanson|discuss]] • [[Special:Contributions/Kayden Swanson|contribs]]) 04:22, 18 July 2026 (UTC)

:Thank you! I have removed the flag. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 20:41, 20 July 2026 (UTC)

== Vandalism ==

your recent   changes may not be constructive.

{{Warning}}

[[User:Duodeca 12|Duodeca 12]] ([[User talk:Duodeca 12|discuss]] • [[Special:Contributions/Duodeca 12|contribs]]) 20:39, 2 August 2026 (UTC)</text>
      <sha1>5g7jub5gu0jmr9dfbc01yjmt7wc08e4</sha1>
    </revision>
  </page>
  <page>
    <title>Wikibooks:GUS2Wiki</title>
    <ns>4</ns>
    <id>447875</id>
    <revision>
      <id>4656050</id>
      <parentid>4655566</parentid>
      <timestamp>2026-08-02T15:10:11Z</timestamp>
      <contributor>
        <username>Alexis Jazz</username>
        <id>470964</id>
      </contributor>
      <comment>Updating gadget usage statistics from [[Special:GadgetUsage]] ([[phab:T121049]])</comment>
      <origin>4656050</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2050" sha1="dcgf7kxj22vdideboexwnvzeyd25zyw" xml:space="preserve">{{#ifexist:Project:GUS2Wiki/top|{{/top}}|This page provides a historical record of [[Special:GadgetUsage]] through its page history. To get the data in CSV format, see wikitext. To customize this message or add categories, create [[/top]].}}
The following data is cached, and was last updated 2026-08-01T06:32:36Z. A maximum of {{PLURAL:5000|one result is|5000 results are}} available in the cache.
{| class=&quot;sortable wikitable&quot;
! Gadget !! data-sort-type=&quot;number&quot; | Number of users !! data-sort-type=&quot;number&quot; | Active users
|-
|BookCat || 106 || 3
|-
|CleanDeleteReasons || 54 || 0
|-
|CommentsInLocalTime || 667 || 5
|-
|DeluxeBar || 208 || 5
|-
|GetCollection || 552 || 0
|-
|HotCat || 7 || 1
|-
|Massblock || 1 || 1
|-
|OneClickWelcomer || 27 || 1
|-
|SpecialSearch || 664 || 1
|-
|Subpages || 1 || 1
|-
|UTCLiveClock || 369 || 6
|-
|background-awesomeness || 787 || 5
|-
|bottomtabs || 431 || 2
|-
|commons-file || data-sort-value=&quot;Infinity&quot; | Default || data-sort-value=&quot;Infinity&quot; | Default
|-
|contribsrange || 331 || 5
|-
|markAdmins || 144 || 12
|-
|markblocked || 59 || 3
|-
|modrollback || 83 || 3
|-
|navpop || 843 || 10
|-
|purge || 620 || 9
|-
|rightsfilter || 372 || 3
|-
|searchbox || 210 || 4
|-
|sidebartranslate || 503 || 2
|-
|sixtabs || 312 || 0
|-
|subject-pages || 612 || 3
|-
|subpages || 30 || 5
|-
|wiked || 669 || 1
|-
|wikidialog || data-sort-value=&quot;Infinity&quot; | Default || data-sort-value=&quot;Infinity&quot; | Default
|}
* [[Special:GadgetUsage]]
* [[m:Meta:GUS2Wiki/Script|GUS2Wiki]]
&lt;!-- data in CSV format:
BookCat,106,3
CleanDeleteReasons,54,0
CommentsInLocalTime,667,5
DeluxeBar,208,5
GetCollection,552,0
HotCat,7,1
Massblock,1,1
OneClickWelcomer,27,1
SpecialSearch,664,1
Subpages,1,1
UTCLiveClock,369,6
background-awesomeness,787,5
bottomtabs,431,2
commons-file,default,default
contribsrange,331,5
markAdmins,144,12
markblocked,59,3
modrollback,83,3
navpop,843,10
purge,620,9
rightsfilter,372,3
searchbox,210,4
sidebartranslate,503,2
sixtabs,312,0
subject-pages,612,3
subpages,30,5
wiked,669,1
wikidialog,default,default
--&gt;</text>
      <sha1>dcgf7kxj22vdideboexwnvzeyd25zyw</sha1>
    </revision>
  </page>
  <page>
    <title>User talk:Xeverything11/updates</title>
    <ns>3</ns>
    <id>452115</id>
    <revision>
      <id>4656156</id>
      <parentid>4655687</parentid>
      <timestamp>2026-08-03T03:11:26Z</timestamp>
      <contributor>
        <username>MediaWiki message delivery</username>
        <id>1188004</id>
      </contributor>
      <comment>/* Wikipedia translation of the week: 2026-32 */ new section</comment>
      <origin>4656156</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1118533" sha1="5lqd4dim00izj3zj42dj3ny53t9gzjk" 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;</text>
      <sha1>5lqd4dim00izj3zj42dj3ny53t9gzjk</sha1>
    </revision>
  </page>
  <page>
    <title>Cookbook:Tahu Gejrot</title>
    <ns>102</ns>
    <id>471903</id>
    <revision>
      <id>4656173</id>
      <parentid>4597430</parentid>
      <timestamp>2026-08-03T07:55:04Z</timestamp>
      <contributor>
        <username>Jdlrobson</username>
        <id>563339</id>
      </contributor>
      <comment>force edit to generate action=info image</comment>
      <origin>4656173</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1691" sha1="1p9kfhsp89znh5sispy4yrw0gxr6b0d" xml:space="preserve">{{Incomplete recipe|reason=missing categories; what do you do with the kecap manis?}}

__NOTOC__

{{Recipe summary
| Category = Indonesian recipes
| Servings = 5 
| Image = [[File:Tahu gejrot cirebon.JPG|300px]]
}}

{{Recipe}}

'''Tahu gejrot''' is a traditional dish from Cirebon, West Java, Indonesia. The dish is made from the main ingredient of fried Sumedang tofu or tofu pong, drizzled with a sweet and sour sauce and crushed chili peppers. Then, the sweet and sour sauce is made from palm sugar and tamarind. The flavor of Tahu Gejrot is both spicy and refreshing.

== Ingredients ==

* 12 red or green bird's eye [[Cookbook:Chiles|chiles]]
* 3 cloves [[Cookbook:Garlic|garlic]]
* 4 [[Cookbook:Shallot|shallots]]
* 100 [[Cookbook:Gram|g]] [[Cookbook:Palm Sugar|palm sugar]], thinly [[Cookbook:Slicing|sliced]]
* 3 ea. [[Cookbook:Tamarind|tamarind]] pods  
* 300 [[Cookbook:Milliliter|ml]] water  
* 15 pieces of Sumedang [[Cookbook:Tofu|tofu]] or tofu pong  
* 4 [[Cookbook:Tablespoon|tbsp]] [[Cookbook:Kecap Manis|kecap manis]]
* [[Cookbook:Salt|Salt]] to taste  

== Procedure ==

# Grind the chiles, garlic, and shallots together, then set aside.
# Combine the palm sugar, tamarind, and water in a saucepan. [[Cookbook:Boiling|Boil]] the mixture until all the ingredients dissolve and form a syrup.
# Pour the syrup over the ground chile mixture. Mix well until evenly combined.
# Cut the tofu diagonally, then press lightly until the center of the tofu is slightly crushed.
# Arrange the tofu on a plate, then drizzle with the spicy and sweet sauce.   

[[Category:Sundanese recipes]]
[[Category:Indonesian recipes]]
[[Category:Recipes using tofu]]
[[Category:Palm sugar recipes]]</text>
      <sha1>1p9kfhsp89znh5sispy4yrw0gxr6b0d</sha1>
    </revision>
  </page>
  <page>
    <title>The Linux Kernel/Template</title>
    <ns>0</ns>
    <id>474544</id>
    <revision>
      <id>4656079</id>
      <parentid>4653392</parentid>
      <timestamp>2026-08-02T17:58:07Z</timestamp>
      <contributor>
        <username>Conan</username>
        <id>3188</id>
      </contributor>
      <minor />
      <comment>compile-time configurations section in template</comment>
      <origin>4656079</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3085" sha1="i8oihwqwb0oqvrufdtvpcq4hdbm5d6c" xml:space="preserve">&lt;!-- Use this template and examples for new topics --&gt;

=== Topic template ===

&lt;!-- Write here short introduction. --&gt;

This template is for contributors to structure their content.
Fill in the placeholders as needed.

🔧 TODO
: ...

🗝️ Acronyms and/or key terms
&lt;!-- use colon &quot;:&quot; for elegant lists --&gt;
: API – Application Program Interface
: ...

🖱️ GUI
&lt;!-- Links to the manpages --&gt;
: {{The Linux Kernel/man|1|git-gui}} – A portable graphical interface to Git
: ...

🛠️ Utilities 
&lt;!-- Links to the manpages --&gt;
: {{The Linux Kernel/man|1|ls}} – Lists directory contents
: ...

⚲ APIs
&lt;!-- Links to the manpages --&gt;
&lt;!-- Use shell-friendly $var for placeholders, e.g. /proc/$pid/status --&gt;
: {{The Linux Kernel/man|1|intro}} – Introduction to user commands
: {{The Linux Kernel/man|2|intro}} – Introduction to system calls
: {{The Linux Kernel/man|4|intro}} – Introduction to special files
: {{The Linux Kernel/include|uapi}} – User-space API
: {{The Linux Kernel/man|2|syscall}} ↪
&lt;!-- Links to specific identifiers (functions, structures, macros, etc.) within the Linux kernel --&gt;
:: {{The Linux Kernel/id|entry_SYSCALL_64}} ↯ Call hierarchy:
::: {{The Linux Kernel/id|do_syscall_64}}
:::: ...
&lt;!-- ↬ for async calls (queues work, returns immediately) --&gt;
: {{The Linux Kernel/id|queue_work}} ↬ {{The Linux Kernel/id|work_func_t}}
: ...

🪛 Compile-time configurations
: {{The Linux Kernel/id|CONFIG_LOCALVERSION}} – append to kernel release

👁️ Example
&lt;!-- Links to the directories and files --&gt;
: {{The Linux Kernel/source|samples}}
: ...

⚙️ Internals
&lt;!-- Links to the kernel sources --&gt;
&lt;!-- Links to specific identifiers (functions, structures, macros, etc.) --&gt;
: {{The Linux Kernel/id|printk}}
&lt;!-- Links to the directories and files --&gt;
: {{The Linux Kernel/source|kernel}}
: {{The Linux Kernel/source|tools/testing/selftests}}
: ...

🚀 Advanced features
: ...

==== ... ====
&lt;!-- Appendix --&gt;
📖 References
&lt;!-- Links to official Linux documentation --&gt;
: {{The Linux Kernel/doc|The Linux Kernel documentation|#}}
: {{The Linux Kernel/doc|Documentation for /proc/sys/kernel/|admin-guide/sysctl/kernel.html}}
&lt;!-- Links with URL Fragment Text Directive --&gt;
: [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=initcall_debug initcall_debug]
: ...

📚 Further reading
&lt;!-- Links to external resources and LKML --&gt;
: [https://lore.kernel.org/ Kernel mailing lists]
:: [https://lore.kernel.org/lkml/ LKML]
:: [https://lore.kernel.org/linux-doc/ linux-doc ML]
:: [https://lore.kernel.org/kernelnewbies/ KernelNewbies ML]
&lt;!-- External Wikipedia Links --&gt;
: {{w|Linux kernel}}
&lt;!-- Other wikies --&gt;
: https://deepwiki.com/torvalds/linux
: https://wiki.archlinux.org/
: https://wiki.ubuntu.com/Kernel
: ...

💾 ''Historical''
&lt;!-- Links to historical resources --&gt;
: [https://tldp.org/LDP/lki/ Linux Kernel Internals]
: [https://tldp.org/HOWTO/KernelAnalysis-HOWTO.html Kernel Analysis HOWTO]
: [https://www.kernel.org/doc/html/ Kernel documentation archive]
: ... 

{{BookCat}}</text>
      <sha1>i8oihwqwb0oqvrufdtvpcq4hdbm5d6c</sha1>
    </revision>
  </page>
  <page>
    <title>The Linux Kernel/Multitasking/CPU</title>
    <ns>0</ns>
    <id>475313</id>
    <revision>
      <id>4656078</id>
      <parentid>4655314</parentid>
      <timestamp>2026-08-02T17:58:06Z</timestamp>
      <contributor>
        <username>Conan</username>
        <id>3188</id>
      </contributor>
      <minor />
      <comment>Tick and NO_HZ subsection</comment>
      <origin>4656078</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="53623" sha1="0u2ktj1wuhyxrh2g7hvycjr8al6nsia" xml:space="preserve">&lt;noinclude&gt;{{DISPLAYTITLE:Interrupts and CPU}}&lt;/noinclude&gt;
== Interrupts ==
An {{w|interrupt}} is a signal to the processor emitted by hardware or software indicating an event that needs immediate attention.
An interrupt alerts the processor to a high-priority condition requiring the interruption of the current code the processor is executing.
The processor responds by suspending its current activities, saving its state, and executing a function called an ''interrupt handler'' (or an interrupt service routine, ISR) to deal with the event.
This interruption is temporary, and, after the interrupt handler finishes, the processor resumes normal activities.

There are two types of interrupts: hardware interrupts and software interrupts.
Hardware interrupts are used by devices to communicate that they require attention from the operating system.
For example, pressing a key on the keyboard or moving the mouse triggers hardware interrupts that cause the processor to read the keystroke or mouse position.
Unlike the software type, hardware interrupts are asynchronous and can occur in the middle of instruction execution, requiring additional care in programming.
The act of initiating a hardware interrupt is referred to as an ''interrupt request'' - IRQ ↪ {{w|Interrupt descriptor table|IDT}} ↪ {{The Linux Kernel/id|common_interrupt}} on x86.

A software interrupt is caused either by an exceptional condition in the processor itself, or a special instruction in the instruction set which causes an interrupt when it is executed.
The former is often called a ''{{w|Trap (computing)|trap}}'' (⚙️ {{The Linux Kernel/id|do_trap}}) or ''exception'' and is used for errors or events occurring during program execution that are exceptional enough that they cannot be handled within the program itself.
For example, if the processor's arithmetic logic unit is commanded to divide a number by zero, this impossible demand will cause a ''divide-by-zero exception'' (⚙️ {{The Linux Kernel/id|X86_TRAP_DE}}), perhaps causing the computer to abandon the calculation or display an error message.
Software interrupt instructions function similarly to subroutine calls and are used for a variety of purposes, such as to request services from low-level system software such as device drivers.
For example, computers often use software interrupt instructions to communicate with the disk controller to request data be read or written to the disk.

Each interrupt has its own interrupt handler.  The number of hardware interrupts is limited by the number of interrupt request (IRQ) lines to the processor, but there may be hundreds of different software interrupts.


⚲ API

: /proc/interrupts
: {{The Linux Kernel/man|1|irqtop}} &amp;ndash; utility to display kernel interrupt information
: [https://github.com/Irqbalance/irqbalance irqbalance] &amp;ndash; distribute hardware interrupts across processors on a multiprocessor system
: There are many ways to request ISR, two of them
: {{The Linux Kernel/id|devm_request_threaded_irq}} &amp;ndash; preferable, managed device with threaded ISR
: {{The Linux Kernel/id|devm_request_irq}} &amp;ndash; managed version
:: {{The Linux Kernel/id|request_irq}}
::: {{The Linux Kernel/id|request_threaded_irq}}
: {{The Linux Kernel/id|free_irq}}
: {{The Linux Kernel/include|linux/interrupt.h}} &amp;ndash; main interrupt support header
:: {{The Linux Kernel/id|irqaction}} &amp;ndash; contains handler functions 
: {{The Linux Kernel/include|linux/irq.h}}
:: {{The Linux Kernel/id|irq_data}}
: {{The Linux Kernel/include|linux/irqflags.h}}
:: {{The Linux Kernel/id|irqs_disabled}}
:: {{The Linux Kernel/id|local_irq_save}} ...
:: {{The Linux Kernel/id|local_irq_disable}} ...
: {{The Linux Kernel/include|linux/irqdesc.h}}
:: {{The Linux Kernel/id|irq_desc}}
: {{The Linux Kernel/include|linux/irqdomain.h}}
:: {{The Linux Kernel/id|irq_domain}} &amp;ndash; hardware interrupt number translation object
:: {{The Linux Kernel/id|irq_domain_get_irq_data}}
: {{The Linux Kernel/include|linux/msi.h}} &amp;ndash; {{w|Message Signaled Interrupts}}
:: {{The Linux Kernel/id|msi_desc}}
: Structure of structures:
:: {{The Linux Kernel/id|irq_desc}} is container of
::: {{The Linux Kernel/id|irq_data}}
:::: irq &amp;ndash; interrupt number
::: {{The Linux Kernel/id|irq_common_data}}
::: list of {{The Linux Kernel/id|irqaction}}


⚙️ Internals

: {{The Linux Kernel/source|kernel/irq/settings.h}} &amp;ndash; IRQ descriptor status flags
: {{The Linux Kernel/source|kernel/irq}} &amp;ndash; generic IRQ handling
:: {{The Linux Kernel/source|kernel/irq/internals.h}} &amp;ndash; IRQ subsystem internal functions
: ls /sys/kernel/debug/irq/domains/
:: {{The Linux Kernel/id|x86_vector_domain}}, {{The Linux Kernel/id|x86_vector_domain_ops}}
: {{The Linux Kernel/id|irq_chip}}
: {{The Linux Kernel/id|load_idt}} &amp;ndash; load Interrupt Descriptor Table
: {{The Linux Kernel/source|arch/x86/include/asm/idtentry.h}} &amp;ndash; interrupt entry/exit definitions
: {{The Linux Kernel/source|arch/x86/include/asm/hw_irq.h}} &amp;ndash; x86 hardware IRQ definitions
:: {{The Linux Kernel/id|irq_entries_start}} &amp;ndash; hardware IRQ entry stubs
: {{The Linux Kernel/source|arch/x86/kernel/irq.c}} &amp;ndash; x86 interrupt handling
:: {{The Linux Kernel/id|common_interrupt}} &amp;ndash; handles all normal device IRQs on x86
: {{The Linux Kernel/source|arch/x86/kernel/apic}} &amp;ndash; {{w|Advanced Programmable Interrupt Controller|APIC}}
:: {{The Linux Kernel/source|arch/x86/kernel/apic/apic.c}} &amp;ndash; local APIC core (timer, calibration, spurious interrupt)
:: {{The Linux Kernel/source|arch/x86/kernel/apic/io_apic.c}} &amp;ndash; {{w|IOAPIC|I/O APIC}}, routes device IRQs to CPUs
:: {{The Linux Kernel/source|arch/x86/kernel/apic/x2apic_cluster.c}} &amp;ndash; {{w|x2APIC}} (&gt;256 CPUs)
:: {{The Linux Kernel/source|arch/x86/kernel/apic/ipi.c}} &amp;ndash; {{w|Inter-processor interrupt|IPI}}, see [[#IPI|IPI]]
:: {{The Linux Kernel/source|arch/x86/kernel/apic/hw_nmi.c}} &amp;ndash; hardware NMI watchdog via APIC
:: {{The Linux Kernel/source|arch/x86/kernel/apic/vector.c}} &amp;ndash; IRQ vector allocation
:: {{The Linux Kernel/source|arch/x86/kernel/apic/msi.c}} &amp;ndash; {{w|Message Signaled Interrupts|MSI}} via APIC

📖 References
: {{The Linux Kernel/doc|IRQs|core-api/irq}}
:: {{The Linux Kernel/doc|The irq_domain interrupt number mapping library|core-api/irq/irq-domain.html}}
: {{The Linux Kernel/doc|Linux generic IRQ handling|core-api/genericirq.html}}
: {{The Linux Kernel/doc|Message Signaled Interrupts: The MSI Driver Guide|PCI/msi-howto.html}}
: {{The Linux Kernel/doc|Lock types and their rules|locking/locktypes.html}}
: {{The Linux Kernel/doc|Hard IRQ Context|kernel-hacking/locking.html#hard-irq-context}}
: [https://0xax.gitbooks.io/linux-insides/content/Interrupts/ Interrupts]


👁 Examples
: {{The Linux Kernel/id|dummy_irq_chip}} &amp;ndash; dummy interrupt chip implementation
: {{The Linux Kernel/source|lib/locking-selftest.c}} &amp;ndash; locking correctness self-tests


=== IRQ affinity ===

⚲ API
: /proc/irq/default_smp_affinity
: /proc/irq/*/smp_affinity and /proc/irq/*/smp_affinity_list


Common types and functions:
: struct {{The Linux Kernel/id|irq_affinity}} &amp;ndash; description for automatic irq affinity assignments, see {{The Linux Kernel/id|devm_platform_get_irqs_affinity}}
: struct {{The Linux Kernel/id|irq_affinity_desc}} &amp;ndash; interrupt affinity descriptor, see {{The Linux Kernel/id|irq_update_affinity_desc}}, {{The Linux Kernel/id|irq_create_affinity_masks}}
: {{The Linux Kernel/id|irq_set_affinity}}
: {{The Linux Kernel/id|irq_get_affinity_mask}} 
: {{The Linux Kernel/id|irq_can_set_affinity}}
: {{The Linux Kernel/id|irq_set_affinity_hint}} 
: {{The Linux Kernel/id|irqd_affinity_is_managed}} 
: {{The Linux Kernel/id|irq_data_get_affinity_mask}}
: {{The Linux Kernel/id|irq_data_get_effective_affinity_mask}} 
: {{The Linux Kernel/id|irq_data_update_effective_affinity}} 
: {{The Linux Kernel/id|irq_set_affinity_notifier}} 
: {{The Linux Kernel/id|irq_affinity_notify}} 
: {{The Linux Kernel/id|irq_chip_set_affinity_parent}} 
: {{The Linux Kernel/id|irq_set_vcpu_affinity}}


🛠️ Utilities
: [https://man.archlinux.org/man/extra/irqbalance/irqbalance.1.en irqbalance] – distributes hardware interrupts across CPUs


📖 References
: {{The Linux Kernel/doc|SMP IRQ affinity|core-api/irq/irq-affinity.html}}
: [https://wiki.linuxfoundation.org/realtime/documentation/howto/tools/cpu-partitioning/start#irq_affinity IRQ affinity, LF]
: [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=managed_irq managed_irq kernel parameter], [https://lore.kernel.org/lkml/?q=managed_irq @LKML]
: [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=irqaffinity= irqaffinity kernel parameter], [https://lore.kernel.org/lkml/?q=irqaffinity @LKML]


=== Non-maskable interrupts ===

⚲ API
: {{The Linux Kernel/include|linux/nmi.h}}
:: {{The Linux Kernel/id|in_nmi}}
:: {{The Linux Kernel/id|touch_nmi_watchdog}}
:: ...
: {{The Linux Kernel/include|trace/events/nmi.h}}
: {{The Linux Kernel/source|arch/x86/include/asm/nmi.h}} &amp;ndash; x86 NMI handler registration
:: {{The Linux Kernel/id|register_nmi_handler}}
:: {{The Linux Kernel/id|unregister_nmi_handler}}


⚙️ Internals
: {{The Linux Kernel/source|arch/x86/kernel/nmi.c}} &amp;ndash; x86 NMI handler
: {{The Linux Kernel/source|arch/x86/kernel/apic/hw_nmi.c}} &amp;ndash; hardware NMI watchdog via APIC
: {{The Linux Kernel/source|arch/x86/kernel/nmi_selftest.c}} &amp;ndash; NMI IPI self-tests


📖 References
: {{The Linux Kernel/doc|NMI Trace Events|trace/events-nmi.html}}


📚 Further reading
: [https://0xax.gitbooks.io/linux-insides/content/Interrupts/linux-interrupts-6.html Non-maskable interrupt handler] (NMI)


=== ... ===

📚 Further reading about interrupts
: IDT &amp;ndash; {{w|Interrupt descriptor table}}
: [https://www.felixcloutier.com/x86/lgdt:lidt LGDT/LIDT &amp;ndash; Load Global/Interrupt Descriptor Table Register] asm instruction

== Deferred works ==

=== Scheduler context ===

==== kthread work ====

This framework simplifies the use of kernel kthreads.
A {{The Linux Kernel/id|kthread_work}} item can be queued with {{The Linux Kernel/id|kthread_queue_work}} and flushed using {{The Linux Kernel/id|kthread_flush_work}}.
All queued kthread_work items are processed by a dedicated kernel thread executing the {{The Linux Kernel/id|kthread_worker_fn}} function.

⚲ API
: {{The Linux Kernel/id|kthread_work}} &amp;ndash; contains {{The Linux Kernel/id|kthread_work_func_t}} to execute
:: {{The Linux Kernel/id|kthread_init_work}}
:: {{The Linux Kernel/id|kthread_flush_work}}
: {{The Linux Kernel/id|kthread_worker}} &amp;ndash; links a kthread_work and a task
:: {{The Linux Kernel/id|kthread_run_worker}} &amp;ndash; creates and wakes a kthread worker
::: {{The Linux Kernel/id|kthread_create_worker}}
::: {{The Linux Kernel/id|kthread_flush_worker}}
:: {{The Linux Kernel/id|kthread_destroy_worker}}
: {{The Linux Kernel/id|kthread_queue_work}} &amp;ndash; queues a kthread_work on a kthread_worker


⚙️ Internals
: {{The Linux Kernel/id|__kthread_create_worker_on_node}}
: {{The Linux Kernel/id|kthread_worker_fn}} &amp;ndash; executes work's function


👁 Example usages
: {{The Linux Kernel/id|watchdog_kworker}}, {{The Linux Kernel/id|pwq_release_worker}}, {{The Linux Kernel/id|pump_messages}}

==== Threaded IRQ ====

⚲ API
{{The Linux Kernel/id|devm_request_threaded_irq}}, {{The Linux Kernel/id|request_threaded_irq}}
ISR should return IRQ_WAKE_THREAD to run thread function

⚙️ Internals
: {{The Linux Kernel/id|setup_irq_thread}}, {{The Linux Kernel/id|irq_thread}}
: {{The Linux Kernel/source|kernel/irq/manage.c}} &amp;ndash; IRQ request, free and affinity management

📖 References
: {{The Linux Kernel/doc|request_threaded_irq|core-api/genericirq.html#c.request_threaded_irq}}


==== Work and workqueue ====

Generic async execution with shared worker pool.

⚲ API
: {{The Linux Kernel/id|PF_WQ_WORKER}} &amp;ndash; workqueue worker process flag
: {{The Linux Kernel/include|linux/workqueue.h}}, {{The Linux Kernel/include|linux/workqueue_types.h}}
: {{The Linux Kernel/id|work_struct}}, {{The Linux Kernel/id|INIT_WORK}}
: {{The Linux Kernel/id|delayed_work}}, {{The Linux Kernel/id|INIT_DELAYED_WORK}}, {{The Linux Kernel/id|cancel_delayed_work_sync}}
: {{The Linux Kernel/id|workqueue_struct}}
:: {{The Linux Kernel/id|devm_alloc_workqueue}}
::: {{The Linux Kernel/id|alloc_workqueue}}
:: {{The Linux Kernel/id|destroy_workqueue}}
: {{The Linux Kernel/id|schedule_work}} &amp;ndash; queues work on the system workqueue ↯
:: {{The Linux Kernel/id|queue_work}} &amp;ndash; queues work on a workqueue
::: {{The Linux Kernel/id|queue_work_on}} &amp;ndash; on a specific CPU
: {{The Linux Kernel/id|show_all_workqueues}}
:: {{The Linux Kernel/id|show_one_workqueue}}
: {{The Linux Kernel/id|system_power_efficient_wq}} ...


👁 Example usage {{The Linux Kernel/source|samples/ftrace/sample-trace-array.c}}


⚙️ Internals
: {{The Linux Kernel/source|kernel/workqueue.c}} &amp;ndash; generic async execution with shared worker pool
:: {{The Linux Kernel/id|workqueue_init}}
::: {{The Linux Kernel/id|create_worker}}
:::: {{The Linux Kernel/id|worker_thread}}
::::: {{The Linux Kernel/id|process_one_work}}
:: {{The Linux Kernel/id|format_worker_id}} &amp;ndash; names kworker kthreads
:: {{The Linux Kernel/id|pool_workqueue}}
::: {{The Linux Kernel/id|worker_pool}}


📖 References
: {{The Linux Kernel/doc|Concurrency Managed Workqueue|core-api/workqueue.html}}
: [https://sysprog21.github.io/lkmpg/#work-queues LKMPG: Work queues]

=== Interrupt context ===

: {{The Linux Kernel/include|linux/irq_work.h}} &amp;ndash; run callbacks from hardirq or NMI context where normal work queues can't be used
:: {{The Linux Kernel/id|irq_work_queue}} &amp;ndash; enqueue work on the current CPU, triggers {{The Linux Kernel/id|IRQ_WORK_VECTOR}} IPI if needed
:: {{The Linux Kernel/id|irq_work_sync}} &amp;ndash; wait for completion
:: {{The Linux Kernel/source|kernel/irq_work.c}} &amp;ndash; irq_work implementation
:: 👁 {{The Linux Kernel/source|samples/trace_printk/trace-printk.c}}

==== Timers ====

===== softirq timer =====

This timer is a softirq for periodical tasks with jiffies resolution

⚲ API
: {{The Linux Kernel/include|linux/timer.h}}
: {{The Linux Kernel/id|timer_list}}, {{The Linux Kernel/id|DEFINE_TIMER}}, {{The Linux Kernel/id|timer_setup}}
: {{The Linux Kernel/id|mod_timer}} &amp;mdash; sets expiration time in jiffies. 
: {{The Linux Kernel/id|del_timer}}


⚙️ Internals
: {{The Linux Kernel/source|kernel/time/timer.c}} &amp;ndash; kernel internal timers
:: {{The Linux Kernel/id|timer_bases}}


👁 Examples
: {{The Linux Kernel/id|input_enable_softrepeat}} and {{The Linux Kernel/id|input_start_autorepeat}}


📚 References
: {{The Linux Kernel/doc|Time and timer routines|driver-api/basics.html#time-and-timer-routines}}
:: {{The Linux Kernel/doc|mod_timer_pending ... |driver-api/basics.html#c.mod_timer_pending}}

===== High-resolution timer =====

⚲ API
: /proc/timer_list
: /proc/sys/kernel/timer_migration
: {{The Linux Kernel/include|linux/hrtimer_defs.h}}
: {{The Linux Kernel/include|linux/hrtimer.h}}
: {{The Linux Kernel/id|hrtimer}}, hrtimer.function &amp;mdash; callback
: {{The Linux Kernel/id|hrtimer_init}}
: {{The Linux Kernel/id|hrtimer_setup}}
: {{The Linux Kernel/id|hrtimer_start}} &amp;mdash; starts a timer with nanosecond resolution 
: {{The Linux Kernel/id|hrtimer_cancel}}


👁 Examples {{The Linux Kernel/id|alarm_init}}, {{The Linux Kernel/id|watchdog_enable}}


⚙️ Internals
: {{The Linux Kernel/id|CONFIG_HIGH_RES_TIMERS}}
: {{The Linux Kernel/source|kernel/time/tick-internal.h}} &amp;ndash; tick and timer internal definitions
:: {{The Linux Kernel/id|hrtimer_bases}}
: {{The Linux Kernel/source|kernel/time/hrtimer.c}} &amp;ndash; high-resolution timer implementation
: {{The Linux Kernel/source|kernel/time/itimer.c}} &amp;ndash; interval timers
: {{The Linux Kernel/source|kernel/time/timer_list.c}} &amp;ndash; /proc/timer_list debugfs


📚 HR timers references
: {{The Linux Kernel/doc|High-resolution timers|driver-api/basics.html#high-resolution-timers}}
: {{The Linux Kernel/doc|hrtimers - subsystem for high-resolution kernel timers|timers/hrtimers.html}}
: {{The Linux Kernel/doc|high resolution timers and dynamic ticks design notes|timers/highres.html}}

===== Tick and NO_HZ =====

The tick is the periodic timer interrupt that drives scheduling, timekeeping, and RCU.
The NO_HZ subsystem reduces or eliminates tick interrupts to save power and reduce latency.

⚲ API
: /sys/devices/system/cpu/nohz_full – active nohz_full CPUs
: [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=nohz_full= nohz_full=] boot parameter – list of CPUs to run tickless
: {{The Linux Kernel/include|linux/tick.h}} – tick control API
:: {{The Linux Kernel/id|tick_nohz_full_running}} – true if any CPU runs tickless

🪛 Compile-time configurations ({{The Linux Kernel/source|kernel/time/Kconfig}})
: {{The Linux Kernel/id|CONFIG_HZ_PERIODIC}} – constant-rate tick, always firing
: {{The Linux Kernel/id|CONFIG_NO_HZ_IDLE}} – stop tick when CPU is idle (default on most distros)
: {{The Linux Kernel/id|CONFIG_NO_HZ_FULL}} – stop tick even when running a single task, for RT and latency-sensitive workloads, see [[#CPU_isolation|CPU isolation]]

⚙️ Internals
: {{The Linux Kernel/source|kernel/time/tick-common.c}} – periodic tick setup
: {{The Linux Kernel/source|kernel/time/tick-oneshot.c}} – oneshot mode for hrtimers and NO_HZ
: {{The Linux Kernel/source|kernel/time/tick-sched.c}} – NO_HZ tick scheduling logic
: {{The Linux Kernel/source|kernel/time/tick-broadcast.c}} – broadcast tick for CPUs in deep idle where local timer stops (C3+)
: {{The Linux Kernel/source|kernel/time/timer_migration.c}} – migrate timers from idle to busy CPUs

📖 References
: {{The Linux Kernel/doc|NO_HZ: Reducing Scheduling-Clock Ticks|timers/no_hz.html}}
: [https://wiki.linuxfoundation.org/realtime/documentation/howto/tools/ticklesskernel Tickless kernel, RT wiki]
: {{The Linux Kernel/doc|high resolution timers and dynamic ticks design notes|timers/highres.html}}

===== ... =====

📖 Timers references
: {{The Linux Kernel/doc|Timers|timers}}
: [https://lwn.net/Articles/913568/ Better CPU selection for timer expiration]

==== Tasklet ====

tasklet is a softirq, for time critical operations

⚲ API is deprecated in favor of threaded IRQs: {{The Linux Kernel/id|devm_request_threaded_irq}}
: {{The Linux Kernel/id|tasklet_struct}}, {{The Linux Kernel/id|tasklet_init}}, {{The Linux Kernel/id|tasklet_schedule}} 


⚙️ Internals: {{The Linux Kernel/id|tasklet_action_common}} HI_SOFTIRQ, TASKLET_SOFTIRQ


==== Softirq ====

softirq is internal system facility and should not be used directly.
Use tasklet or threaded IRQs

⚲ API
: {{The Linux Kernel/include|linux/interrupt.h}}
: cat /proc/softirqs
: {{The Linux Kernel/id|open_softirq}} registers {{The Linux Kernel/id|softirq_action}}
: {{The Linux Kernel/id|raise_softirq}}
: {{The Linux Kernel/id|tasklet_schedule}}
:: {{The Linux Kernel/id|__tasklet_schedule}}


⚙️ Internals
: {{The Linux Kernel/source|kernel/softirq.c}} &amp;ndash; software interrupt handling
:: {{The Linux Kernel/id|__do_softirq}} &amp;ndash; main softirq processing loop


📖 References
: [https://0xax.gitbooks.io/linux-insides/content/Interrupts/linux-interrupts-9.html Introduction to deferred interrupts (Softirq, Tasklets and Workqueues)]
: [https://0xax.gitbooks.io/linux-insides/content/Timers/ Timers and time management]
: [https://linux-kernel-labs.github.io/refs/heads/master/labs/deferred_work.html Deferred work, linux-kernel-labs]
: [https://www.oreilly.com/library/view/linux-device-drivers/0596005903/ch07.html Chapter 7. Time, Delays, and Deferred Work]

==CPU specific==


🖱️ GUI
: [https://manpages.ubuntu.com/manpages/kinetic/en/man8/tuna.8.html tuna] &amp;ndash; program for tuning running processes


⚲ API
: cat /proc/cpuinfo
: /sys/devices/system/cpu/
: /sys/devices/system/node/
: /sys/cpu/
: /sys/fs/cgroup/cpu/
: grep -i cpu /proc/self/status
: [https://manpages.ubuntu.com/manpages/jammy/man1/rdmsr.1.html rdmsr] &amp;ndash; tool for reading CPU machine specific registers (MSR)
: {{The Linux Kernel/man|1|lscpu}} &amp;ndash; display information about the CPU architecture

: {{The Linux Kernel/include|linux/arch_topology.h}} &amp;ndash; arch specific cpu topology information 
: {{The Linux Kernel/include|linux/cpu.h}} &amp;ndash; generic cpu definition 
: {{The Linux Kernel/include|linux/cpu_cooling.h}} 
: {{The Linux Kernel/include|linux/cpu_pm.h}} 
: {{The Linux Kernel/include|linux/cpufeature.h}}
: {{The Linux Kernel/source|arch/x86/include/asm/cpufeature.h}} &amp;ndash; x86 CPU feature detection
: {{The Linux Kernel/include|linux/peci-cpu.h}} 
: {{The Linux Kernel/include|linux/sched/cputime.h}} &amp;ndash; cputime accounting APIs
: {{The Linux Kernel/include|linux/clk.h}} &amp;ndash; interfaces for managing hardware clocks in device drivers


⚙️ Internals

: {{The Linux Kernel/source|drivers/base/cpu.c}} &amp;ndash; CPU driver model subsystem
:: {{The Linux Kernel/id|cpu_dev_init}}


=== Cache ===

: {{The Linux Kernel/include|linux/cacheflush.h}}
:: {{The Linux Kernel/source|arch/x86/include/asm/cacheflush.h}}: {{The Linux Kernel/id|clflush_cache_range}}
: {{The Linux Kernel/include|linux/cache.h}} &amp;ndash; cache line alignment macros
:: {{The Linux Kernel/id|____cacheline_aligned}} &amp;ndash; align to cache line boundary to avoid false sharing
:: {{The Linux Kernel/id|__cacheline_aligned}} &amp;ndash; same, plus place in .data..cacheline_aligned section
:: {{The Linux Kernel/id|____cacheline_aligned_in_smp}} &amp;ndash; same, but no-op on uniprocessor builds
:: {{The Linux Kernel/id|__read_mostly}} &amp;ndash; place in a cache-friendly section for rarely written data
:: {{The Linux Kernel/id|__ro_after_init}} &amp;ndash; writable during init, read-only after boot (security hardening)
:: {{The Linux Kernel/id|DEFINE_PER_CPU_CACHE_HOT}} &amp;ndash; per-CPU variable in .data..hot section, used for {{The Linux Kernel/id|current_task}}, {{The Linux Kernel/id|__preempt_count}}
:: {{The Linux Kernel/id|L1_CACHE_BYTES}}, {{The Linux Kernel/id|SMP_CACHE_BYTES}} &amp;ndash; 64 bytes typically
:: {{The Linux Kernel/source|arch/x86/include/asm/cache.h}} &amp;ndash; x86 cache line size definitions

🔨 [https://manpages.ubuntu.com/manpages/resolute/man1/stress-ng.1.html#:~:text=%2D%2Dcache stress-ng --cache]

⚙️ Internals

: {{The Linux Kernel/source|arch/x86/mm/pat/set_memory.c}} &amp;ndash; page attribute table memory type control
: {{The Linux Kernel/source|arch/x86/kernel/cpu/mtrr/}} &amp;ndash; memory type range register driver

📚 Further reading
: MTRR &amp;ndash; {{w|Memory type range register}}
: {{w|CPU cache}}

=== {{w|Symmetric_multiprocessing|SMP}} ===

This chapter is about multiprocessing and {{w|Multi-core processor|multi-core}} aspects of Linux kernel.

Key concepts and features of Linux SMP include:
* Symmetry: In an SMP system, all processors are considered the same without hardware hierarchy in contradiction to use of {{w|coprocessor}}s.
* Load balancing: The Linux kernel employs load balancing mechanisms to distribute tasks evenly among available CPU cores. This prevents any one core from becoming overwhelmed while others remain underutilized.
* Parallelism: SMP enables parallel processing, where multiple threads or processes can execute simultaneously on different CPU cores. This can significantly improve the execution speed of applications that are designed to take advantage of multiple threads.
* Thread scheduling: The Linux kernel scheduler is responsible for determining which threads or processes run on which CPU cores and for how long. It aims to optimize performance by minimizing contention and maximizing CPU utilization.
* Shared memory: In an SMP system, all CPU cores typically share the same physical memory space. This allows processes and threads running on different cores to communicate and share data more efficiently.
* NUMA &amp;ndash; {{w|Non-Uniform Memory Access}}: In larger SMP systems, memory access times might not be uniform due to the physical arrangement of memory banks and processors. Linux has mechanisms to handle NUMA architectures efficiently, allowing processes to be scheduled on CPUs closer to their associated memory.
* Cache coherency: SMP systems require mechanisms to ensure that all CPU cores have consistent views of memory. Cache coherency protocols ensure that changes made to shared memory locations are correctly propagated to all cores.
* Scalability: SMP systems can be scaled up to include more CPU cores, enhancing the overall computing power of the system. However, as the number of cores increases, challenges related to memory access, contention, and communication between cores may arise.
* Kernel and user space: Linux applications running in user space can take advantage of SMP without needing to be aware of the underlying hardware details. The kernel handles the management of CPU cores and resource allocation.


⚲ API
: &lt;code&gt;ps -PLe&lt;/code&gt; &amp;ndash; lists threads with processor that the thread last executed on (the third column PSR).
: {{The Linux Kernel/man|2|getcpu}} &amp;ndash; determine CPU and NUMA node on which the calling thread is running
: {{The Linux Kernel/man|8|chcpu}} &amp;ndash; configure CPUs
: {{The Linux Kernel/man|3|CPU_SET}} &amp;ndash; macros for manipulating CPU sets
: {{The Linux Kernel/include|linux/smp.h}}
:: The most commonly used functions:
:: {{The Linux Kernel/id|crash_smp_send_stop}} – halts all CPUs except the calling one in a crash context
:: {{The Linux Kernel/id|get_cpu}} – disables preemption and returns the current processor ID
:: {{The Linux Kernel/id|panic_smp_self_stop}} – stops the local CPU during a panic while ensuring others halt
:: {{The Linux Kernel/id|put_cpu}} – re-enables preemption after a previous get_cpu call
:: {{The Linux Kernel/id|raw_smp_processor_id}} – returns the current CPU ID without preemption safety
:: {{The Linux Kernel/id|setup_max_cpus}} – sets up the maximum number of CPUs to be brought online
:: {{The Linux Kernel/id|smp_init}} – initializes core SMP structures and state during boot
:: {{The Linux Kernel/id|smp_prepare_boot_cpu}} – prepares the boot CPU during early SMP initialization
:: {{The Linux Kernel/id|smp_prepare_cpus}} – prepares all CPUs for booting before secondary CPUs are started
:: {{The Linux Kernel/id|smp_processor_id}} – returns the ID of the current CPU with preemption checks
:: {{The Linux Kernel/id|smp_send_stop}} – stops all other CPUs in response to critical events
:: {{The Linux Kernel/id|wake_up_all_idle_cpus}} – wakes all idle CPUs to ensure prompt task execution
: {{The Linux Kernel/include|linux/cpu.h}}
: {{The Linux Kernel/include|linux/group_cpus.h}}: {{The Linux Kernel/id|group_cpus_evenly}} &amp;ndash; groups all CPUs evenly per NUMA/CPU locality
: {{The Linux Kernel/include|asm-generic/percpu.h}}
: {{The Linux Kernel/include|linux/percpu-defs.h}} &amp;ndash; basic definitions for percpu areas
:: {{The Linux Kernel/id|this_cpu_ptr}}
: {{The Linux Kernel/include|linux/percpu.h}} 
: {{The Linux Kernel/include|linux/percpu-refcount.h}} 
: {{The Linux Kernel/include|linux/percpu-rwsem.h}}
: {{The Linux Kernel/include|linux/preempt.h}}
:: {{The Linux Kernel/id|migrate_disable}}, {{The Linux Kernel/id|migrate_enable}}
: /sys/bus/cpu
: [[#per_CPU_local_lock|per CPU local_lock]]
: {{The Linux Kernel/include|linux/topology.h}} &amp;ndash; {{The Linux Kernel/id|cpu_to_node}}, {{The Linux Kernel/id|numa_node_id}}
: {{The Linux Kernel/source|arch/x86/include/asm/topology.h}} &amp;ndash; x86 NUMA and CPU topology
: See also [[../../Memory#NUMA|NUMA memory section]]


⚙️ Internals
: {{The Linux Kernel/id|boot_cpu_init}} activates the first CPU
: {{The Linux Kernel/id|smp_prepare_cpus}} initializes rest CPUs during boot
: {{The Linux Kernel/id|cpu_number}}
: {{The Linux Kernel/id|CONFIG_SMP}}
:: {{The Linux Kernel/id|CONFIG_NUMA}}
: {{The Linux Kernel/include|trace/events/percpu.h}}
: {{The Linux Kernel/file|drivers/base/cpu.c}} &amp;ndash; CPU driver model subsystem support
: {{The Linux Kernel/file|kernel/cpu.c}} &amp;ndash; CPU hotplug state machine
: smpboot
:: {{The Linux Kernel/include|linux/smpboot.h}}
:: {{The Linux Kernel/source|kernel/smpboot.c}} &amp;ndash; common SMP CPU bringup/teardown
:: {{The Linux Kernel/source|arch/x86/kernel/smpboot.c}} &amp;ndash; x86 SMP booting
: {{The Linux Kernel/source|lib/group_cpus.c}} &amp;ndash; distribute CPUs evenly across groups


🛠️ Utilities
: [https://man.archlinux.org/man/extra/irqbalance/irqbalance.1.en irqbalance] – distributes hardware interrupts across CPUs
: {{The Linux Kernel/man|8|numactl}} &amp;ndash; controls NUMA policy for processes or shared memory


📖 References
: {{The Linux Kernel/doc|Per-CPU Data|kernel-hacking/locking.html#per-cpu-data}}
: {{The Linux Kernel/doc|How CPU topology info is exported via sysfs|admin-guide/cputopology.html}}


📚 Further reading
: [https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/monitoring_and_managing_system_status_and_performance/customizing-tuned-profiles_monitoring-and-managing-system-status-and-performance#functionalities-of-the-scheduler-tuned-plug-in_customizing-tuned-profiles Functionalities of the scheduler TuneD plugin]
: [https://man.archlinux.org/man/tuned-adm.8 tuned-adm] &amp;ndash; command line tool for switching between different tuning profiles


==== {{w|Inter-processor interrupt|IPI}} ====

An inter-processor interrupt is a signal sent from one CPU to another to request an action such as rescheduling, TLB flush, or function execution.

⚲ API
: {{The Linux Kernel/id|smp_send_reschedule}} &amp;ndash; sends a reschedule IPI to a target CPU
: {{The Linux Kernel/id|smp_call_function}} &amp;ndash; invokes a function on all other CPUs via IPI
:: {{The Linux Kernel/id|smp_call_function_many}} &amp;ndash; on a specified set of CPUs
: {{The Linux Kernel/id|smp_call_function_single}} &amp;ndash; on a single target CPU
:: {{The Linux Kernel/id|smp_call_function_single_async}} &amp;ndash; asynchronous variant
: {{The Linux Kernel/id|smp_call_on_cpu}} &amp;ndash; execute on a specific CPU and wait for result
: {{The Linux Kernel/id|on_each_cpu}} &amp;ndash; run a function on all CPUs
:: {{The Linux Kernel/id|on_each_cpu_mask}} &amp;ndash; on a specified set of CPUs
:: {{The Linux Kernel/id|on_each_cpu_cond_mask}} &amp;ndash; conditionally on selected CPUs
: {{The Linux Kernel/id|smp_call_func_t}} &amp;ndash; callback typedef

⚙️ Internals
: {{The Linux Kernel/include|trace/events/ipi.h}}
: {{The Linux Kernel/file|kernel/irq/ipi.c}} &amp;ndash; generic IPI helpers
:: {{The Linux Kernel/id|ipi_send_single}}, {{The Linux Kernel/id|ipi_send_mask}}
: {{The Linux Kernel/source|arch/x86/kernel/apic/ipi.c}} &amp;ndash; x86 IPI via APIC
: {{The Linux Kernel/source|arch/x86/include/asm/irq_vectors.h}} &amp;ndash; x86 IPI vector types:
:: {{The Linux Kernel/id|RESCHEDULE_VECTOR}} &amp;ndash; used by {{The Linux Kernel/id|smp_send_reschedule}}
:: {{The Linux Kernel/id|CALL_FUNCTION_VECTOR}} &amp;ndash; used by {{The Linux Kernel/id|smp_call_function_many}}
:: {{The Linux Kernel/id|CALL_FUNCTION_SINGLE_VECTOR}} &amp;ndash; used by {{The Linux Kernel/id|smp_call_function_single}}
:: {{The Linux Kernel/id|IRQ_WORK_VECTOR}} &amp;ndash; used by {{The Linux Kernel/id|irq_work_queue}}, see [[#Interrupt_context|Interrupt context]]
:: {{The Linux Kernel/id|NMI_VECTOR}} &amp;ndash; used by watchdog, {{The Linux Kernel/id|crash_smp_send_stop}}

==== CPU affinity ====

Affinity refers to assigning a process or thread to specific CPU cores.
This helps control which CPUs execute tasks, potentially improving performance by reducing data movement between cores.
It can be managed using system calls or commands.
Affinity can be represented as CPU bitmask: {{The Linux Kernel/id|cpumask_t}} or CPU affinity list: {{The Linux Kernel/id|cpulist_parse}}.


⚲ API
: {{The Linux Kernel/man|1|taskset}} &amp;ndash; set or retrieve a process's CPU affinity
: grep Cpus_allowed /proc/self/status
: {{The Linux Kernel/man|2|sched_setaffinity}} {{The Linux Kernel/man|2|sched_getaffinity}} &amp;ndash; set and get a thread's CPU affinity mask
:: ↪ {{The Linux Kernel/id|sched_setaffinity}}
: {{The Linux Kernel/id|set_cpus_allowed_ptr}} &amp;ndash; common kernel function to change a task's affinity mask
: {{The Linux Kernel/include|linux/cpu_rmap.h}} &amp;ndash; CPU affinity reverse-map support
: {{The Linux Kernel/include|linux/cpumask_types.h}}
:: struct cpumask, {{The Linux Kernel/id|cpumask_t}} &amp;ndash; CPUs bitmap, can be very big
:: {{The Linux Kernel/id|cpumask_var_t}} &amp;ndash; type for local cpumask variable, see {{The Linux Kernel/id|alloc_cpumask_var}}, {{The Linux Kernel/id|free_cpumask_var}}.
: {{The Linux Kernel/include|linux/cpumask.h}} &amp;ndash; Cpumasks provide a bitmap suitable for representing the set of CPU's in a system, one bit position per CPU number
:: {{The Linux Kernel/id|for_each_possible_cpu}}
:: {{The Linux Kernel/id|num_online_cpus}}
:: {{The Linux Kernel/id|cpumask_set_cpu}}
:: {{The Linux Kernel/id|cpumask_test_cpu}}
:: {{The Linux Kernel/id|for_each_cpu}}


⚙️ Internals
: {{The Linux Kernel/id|cpus_mask}} &amp;ndash; affinity of {{The Linux Kernel/id|task_struct}}
: {{The Linux Kernel/id|cpus_allowed}} &amp;ndash; affinity of {{The Linux Kernel/id|cpuset}}


📚 Further reading
: {{w|Processor affinity}}
: {{w|Affinity mask}}

==== CPU hotplug ====

CPU hotplugging in Linux refers to the ability to dynamically add or remove CPUs from the system without needing a reboot.
This feature is crucial in environments requiring high availability and resource flexibility, such as data centers, virtualized systems, and systems that use power management aggressively.


🗝️ Acronyms
: BP &amp;ndash; Bootstrap Processor
: AP &amp;ndash; Application Processor


⚲ API
: /sys/devices/system/cpu/cpu*/online
: /sys/devices/system/cpu/cpu*/hotplug/
: {{The Linux Kernel/include|linux/cpu.h}}
:: {{The Linux Kernel/id|add_cpu}} ...
: {{The Linux Kernel/include|linux/cpuhotplug.h}}
:: {{The Linux Kernel/id|cpuhp_state}} &amp;ndash; CPU hotplug states 
:: {{The Linux Kernel/id|cpuhp_setup_state}} ... &amp;ndash; setups hotplug state callbacks
::: {{The Linux Kernel/id|cpuhp_setup_state_multi}}
::: {{The Linux Kernel/id|cpuhp_setup_state_nocalls}}
: {{The Linux Kernel/include|linux/cpuhplock.h}} &amp;ndash; CPU hotplug locking
:: {{The Linux Kernel/id|cpus_read_lock}} ...
:: {{The Linux Kernel/id|remove_cpu}} ...


⚙️ Internals
: {{The Linux Kernel/source|kernel/cpu.c}} &amp;ndash; CPU hotplug state machine
:: {{The Linux Kernel/id|cpuhp_state}} &amp;ndash; from CPUHP_OFFLINE to CPUHP_AP_ACTIVE and CPUHP_ONLINE.
:: {{The Linux Kernel/id|cpuhp_hp_states}}
:: {{The Linux Kernel/id|boot_cpu_hotplug_init}}
:: {{The Linux Kernel/id|cpuhp_threads_init}}
:: ... {{The Linux Kernel/id|cpuhp_invoke_callback_range}} ...
: {{The Linux Kernel/source|kernel/irq/cpuhotplug.c}} &amp;ndash; IRQ migration on CPU hotunplug
: {{The Linux Kernel/source|drivers/base/cpu.c}} &amp;ndash; CPU subsystem support
:: {{The Linux Kernel/id|cpu_dev_init}}
::: ... {{The Linux Kernel/id|cpu_subsys_online}}
: {{The Linux Kernel/include|trace/events/cpuhp.h}}
: {{The Linux Kernel/include|linux/cpuhplock.h}}


👁️ Examples
: {{The Linux Kernel/id|torture_onoff}}
: {{The Linux Kernel/source|tools/testing/selftests/sched_ext/hotplug.c}} &amp;ndash; sched_ext CPU hotplug test


📖 References
: {{The Linux Kernel/doc|CPU hotplug in the Kernel|core-api/cpu_hotplug.html}}
:: {{The Linux Kernel/doc|Introduction|core-api/cpu_hotplug.html#introduction}} 
:: {{The Linux Kernel/doc|Command Line Switches|core-api/cpu_hotplug.html#command-line-switches}} 
:: {{The Linux Kernel/doc|CPU maps|core-api/cpu_hotplug.html#cpu-maps}} 
:: {{The Linux Kernel/doc|Using CPU hotplug|core-api/cpu_hotplug.html#using-cpu-hotplug}} 
:: {{The Linux Kernel/doc|The CPU hotplug coordination|core-api/cpu_hotplug.html#the-cpu-hotplug-coordination}} 
:: {{The Linux Kernel/doc|The CPU hotplug API|core-api/cpu_hotplug.html#the-cpu-hotplug-api}} 
::: {{The Linux Kernel/doc|CPU hotplug state machine|core-api/cpu_hotplug.html#cpu-hotplug-state-machine}} 
::: {{The Linux Kernel/doc|CPU online/offline operations|core-api/cpu_hotplug.html#cpu-online-offline-operations}} 
::: {{The Linux Kernel/doc|Allocating a state|core-api/cpu_hotplug.html#allocating-a-state}} 
::: {{The Linux Kernel/doc|Setup of a CPU hotplug state|core-api/cpu_hotplug.html#setup-of-a-cpu-hotplug-state}} 
::: {{The Linux Kernel/doc|Removal of a CPU hotplug state|core-api/cpu_hotplug.html#removal-of-a-cpu-hotplug-state}} 
::: {{The Linux Kernel/doc|Multi-Instance state instance management|core-api/cpu_hotplug.html#multi-instance-state-instance-management}} 
::: {{The Linux Kernel/doc|Examples|core-api/cpu_hotplug.html#examples}} 
:: {{The Linux Kernel/doc|Testing of hotplug states|core-api/cpu_hotplug.html#testing-of-hotplug-states}} 
:: {{The Linux Kernel/doc|Architecture’s requirements|core-api/cpu_hotplug.html#architecture-s-requirements}} 
:: {{The Linux Kernel/doc|User Space Notification|core-api/cpu_hotplug.html#user-space-notification}} 
:: {{The Linux Kernel/doc|Kernel Inline Documentations Reference|core-api/cpu_hotplug.html#kernel-inline-documentations-reference}}
 

🔨 [https://manpages.ubuntu.com/manpages/resolute/man1/stress-ng.1.html#:~:text=%2D%2Dcpu%2Donline stress-ng --cpu-online]

📚 Further reading
: {{The Linux Kernel/id|CONFIG_CPU_HOTPLUG_STATE_CONTROL}} &amp;ndash; enables the ability to write incremental steps between &quot;offline&quot; and &quot;online&quot; states to the CPU's sysfs target file, allowing for more granular control of state transitions.
:: {{The Linux Kernel/id|target_store}}: {{The Linux Kernel/id|cpu_up}}/{{The Linux Kernel/id|cpu_down}}
: [https://lore.kernel.org/lkml/?q=cpuhotplug+OR+cpuhp cpuhotplug, cpuhp @LKML]

==== CPU isolation ====

CPU isolation ensures that specific tasks run on dedicated CPUs, reducing contention and latency.

'''Housekeeping''' CPUs refer to the CPUs that are reserved for various '''system''' tasks. See {{The Linux Kernel/id|hk_type}}.

'''Isolated''' CPUs are dedicated to '''real-time''' applications, such as DPDK.

⚲ API
: /sys/devices/system/cpu/isolated
: /sys/devices/system/cpu/nohz_full
: [https://docs.kernel.org/admin-guide/cgroup-v2.html#:~:text=cpuset.cpus.isolated /sys/fs/cgroup/cpuset.cpus.isolated]
: [https://docs.kernel.org/admin-guide/cgroup-v2.html#:~:text=Partition%20root%20without%20load%20balancing /sys/fs/cgroup/.../cpuset.cpus.partition]
: {{The Linux Kernel/include|linux/sched/isolation.h}}
:: {{The Linux Kernel/id|hk_type}} &amp;ndash; housekeeping type
:: {{The Linux Kernel/id|housekeeping_cpumask}} &amp;ndash; returns CPUs available for housekeeping of a given type
:: {{The Linux Kernel/id|cpu_is_isolated}}
: {{The Linux Kernel/include|linux/cpuset.h}} &amp;ndash; cpuset interface
: {{The Linux Kernel/man|7|cpuset}} &amp;ndash; confine processes to processor and memory node subsets


⚙️ Internals
: {{The Linux Kernel/id|CONFIG_CPU_ISOLATION}}
:: {{The Linux Kernel/source|kernel/sched/isolation.c}} &amp;ndash; housekeeping CPU management
::: {{The Linux Kernel/id|housekeeping_init}}, {{The Linux Kernel/id|housekeeping_update}}
: {{The Linux Kernel/id|CONFIG_CPUSETS}}
:: {{The Linux Kernel/source|kernel/cgroup/cpuset.c}} &amp;ndash; cpuset cgroup controller
::: {{The Linux Kernel/id|cpuset_init}}
::: {{The Linux Kernel/id|cpuset_init_smp}}
::: {{The Linux Kernel/id|isolated_cpus}}
::: {{The Linux Kernel/id|partition_xcpus_add}}, {{The Linux Kernel/id|partition_xcpus_del}}


📖 References
: {{The Linux Kernel/doc|CPU lists in command-line parameters|admin-guide/kernel-parameters.html#cpu-lists}}
:: [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=nohz_full= '''nohz_full'''] clears housekeeping.{{The Linux Kernel/id|cpumasks}} for tick, wq, timer, rcu, misc, and kthread in {{The Linux Kernel/id|housekeeping_nohz_full_setup}}
:: [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=isolcpus '''isolcpus'''] clears housekeeping.{{The Linux Kernel/id|cpumasks}} for [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=domain%20isolation domain] (by default), [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=nohz nohz], and [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=managed_irq managed_irq] in {{The Linux Kernel/id|housekeeping_isolcpus_setup}}
: {{The Linux Kernel/doc|Housekeeping|core-api/housekeeping.html}}
: {{The Linux Kernel/doc|NO_HZ: Reducing Scheduling-Clock Ticks|timers/no_hz.html}}
: {{The Linux Kernel/doc|CPUSETS of cgroup v2|admin-guide/cgroup-v2.html#cpuset}}
: {{The Linux Kernel/doc|CPUSETS of cgroup v1|admin-guide/cgroup-v1/cpusets.html}}


📚 Further reading
: [https://www.youtube.com/watch?v=1lomUhSS82s CPU Isolation state of the art, LPC'23]
: [https://lpc.events/event/19/contributions/2219/ CPU Isolation and IPI interference, LPC'25]
: [https://www.suse.com/c/cpu-isolation-introduction-part-1/ CPU Isolation]
: [https://lore.kernel.org/lkml/?q=isolcpus isolcpus @LKML]
: [https://lore.kernel.org/lkml/?q=housekeeping housekeeping @LKML]
: [https://kubernetes.io/docs/tasks/administer-cluster/reserve-compute-resources/#explicitly-reserved-cpu-list Explicitly Reserved CPU List, Kubernetes Documentation]
: [https://wiki.linuxfoundation.org/realtime/documentation/howto/tools/cpu-partitioning/start CPU Partitioning]
: {{The Linux Kernel/doc|Scheduler Domains|scheduler/sched-domains.html}} &amp;ndash; the Scheduler balances CPUs (scheduling groups) within a sched domain
: [https://lore.kernel.org/lkml/?q=nohz_full nohz_full @LKML]

💾 Historical since v7.0
: {{The Linux Kernel/id|cpuset_cpu_is_isolated}} &amp;ndash; removed, use {{The Linux Kernel/id|cpu_is_isolated}} instead

=== Runtime code patching ===

The kernel patches its own machine code at boot or runtime to optimize hot paths.
Static keys patch a {{w|NOP_(code)|NOP}} to a jump (or vice versa); static calls patch indirect calls to direct calls; alternatives replace instructions based on CPU features.

⚲ API
: {{The Linux Kernel/include|linux/jump_label.h}} &amp;ndash; static keys
:: {{The Linux Kernel/id|DEFINE_STATIC_KEY_FALSE}} &amp;ndash; define a key, initially false
:: {{The Linux Kernel/id|static_branch_unlikely}} &amp;ndash; zero-cost branch check (NOP when key is false)
:: {{The Linux Kernel/id|static_branch_enable}} &amp;ndash; patch all sites to take the branch (expensive, rare use)
: {{The Linux Kernel/include|linux/static_call.h}} &amp;ndash; static calls
:: {{The Linux Kernel/id|DEFINE_STATIC_CALL}} &amp;ndash; define a call site with initial target function
:: {{The Linux Kernel/id|static_call}} &amp;ndash; invoke the patched direct call
:: {{The Linux Kernel/id|static_call_update}} &amp;ndash; change target function, patch all sites
: {{The Linux Kernel/source|arch/x86/include/asm/alternative.h}} &amp;ndash; alternatives
:: {{The Linux Kernel/id|ALTERNATIVE}} &amp;ndash; replace instructions at boot based on CPU features
:: {{The Linux Kernel/source|arch/x86/include/asm/cpufeatures.h}} &amp;ndash; X86_FEATURE_* flags


⚙️ Internals
: {{The Linux Kernel/id|CONFIG_JUMP_LABEL}}
:: {{The Linux Kernel/source|kernel/jump_label.c}} &amp;ndash; static key patching core
:: {{The Linux Kernel/source|arch/x86/kernel/jump_label.c}} &amp;ndash; x86 static key patching
: {{The Linux Kernel/id|CONFIG_HAVE_STATIC_CALL}}
:: {{The Linux Kernel/source|kernel/static_call_inline.c}} &amp;ndash; static call core
:: {{The Linux Kernel/source|arch/x86/kernel/static_call.c}} &amp;ndash; x86 static call patching
: {{The Linux Kernel/source|arch/x86/include/asm/alternative.h}} &amp;ndash; runtime instruction patching
:: {{The Linux Kernel/source|arch/x86/kernel/alternative.c}} &amp;ndash; x86 alternatives engine
::: {{The Linux Kernel/id|smp_text_poke_single}} &amp;ndash; safely patch code on SMP using INT3 breakpoints; used by static keys, static calls, ftrace, kprobes
:::: {{The Linux Kernel/id|smp_text_poke_batch_add}}
:::: {{The Linux Kernel/id|smp_text_poke_batch_finish}}


👁 Examples
: {{The Linux Kernel/id|housekeeping_overridden}}
: {{The Linux Kernel/id|preempt_schedule}}
: tracepoints


📖 References
: {{The Linux Kernel/doc|Static Keys|staging/static-keys.html}}
: {{The Linux Kernel/doc|x86 CPU feature flags|arch/x86/cpuinfo.html}}


=== {{w|Memory barrier}}s ===

Memory barriers (MB) are synchronization mechanisms used to ensure proper ordering of memory operations in a SMP environment.
They play a crucial role in maintaining the consistency and correctness of data shared among different CPU cores or processors.
MBs prevent unexpected and potentially harmful reordering of memory access instructions by the compiler or CPU, which can lead to data corruption and race conditions in a concurrent software system.

⚲ API
: {{The Linux Kernel/man|2|membarrier}}
: {{The Linux Kernel/include|asm-generic/barrier.h}}
:: {{The Linux Kernel/id|mb}}, {{The Linux Kernel/id|rmb}}, {{The Linux Kernel/id|wmb}}
:: {{The Linux Kernel/id|smp_mb}}, {{The Linux Kernel/id|smp_rmb}}, {{The Linux Kernel/id|smp_wmb}}


⚙️ Internals

: {{The Linux Kernel/source|arch/x86/include/asm/barrier.h}} &amp;ndash; x86 memory barrier instructions
: {{The Linux Kernel/source|kernel/sched/membarrier.c}} &amp;ndash; membarrier system call


📖 References
: {{The Linux Kernel/doc|Memory barriers|core-api/wrappers/memory-barriers.html}}


=== States ===

C-states and P-states are features in modern CPUs designed to improve energy efficiency.

🗝️ Acronyms
: [https://uefi.org/htmlspecs/ACPI_Spec_6_4_html/08_Processor_Configuration_and_Control/processor-power-states.html C-states] &amp;ndash; CPU(?) states, aka idle states
: EPP &amp;ndash; {{The Linux Kernel/doc|Energy Performance Preference|admin-guide/pm/amd-pstate.html#energy-performance-preference-epp-rw}}
: HWP &amp;ndash; hardware-managed P-states, see [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=hwp_only hwp_only]
: [https://www.intel.com/content/www/us/en/docs/socwatch/user-guide/2020/p-state.html P-states] &amp;ndash; Performance states, see CPU Power and frequency scaling


⚲ API
: [https://linux.die.net/man/1/cpupower cpupower]


📖 References
: {{The Linux Kernel/doc|Working-State Power Management|admin-guide/pm/working-state.html}}
: https://lwn.net/Kernel/Index/#Power_management


==== Idle ====


C-states, {{w|ACPI#Processor_states|power states}}:
: C0 &amp;ndash; the operating state.
: C1 (aka Halt) &amp;ndash; the processor is not executing instructions, but can return to an executing state instantaneously.
: C2 (aka Stop-Clock) &amp;ndash; the processor maintains all software-visible state, but may take longer to wake up.
: C3 (aka Sleep) &amp;ndash; takes longer to wake up.
: ...


⚲ API
: turbostat --show CPU --quiet -n 1 --interval 0.1 --show sysfs
: [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=idle= idle=]
: /dev/cpu_dma_latency &amp;ndash; see {{The Linux Kernel/id|set_cpu_dma_latency}}
: C-states interfaces:
:: /sys/devices/system/cpu/cpuidle/
:: /sys/devices/system/cpu/cpu*/cpuidle/
:: {{The Linux Kernel/include|linux/cpuidle.h}} &amp;ndash; a generic framework for CPU idle power management 
:: {{The Linux Kernel/doc|intel_idle CPU Idle Time Management Driver|admin-guide/pm/intel_idle.html}}
: {{The Linux Kernel/include|linux/pm_qos.h}}


⚙️ Internals
: {{The Linux Kernel/source|drivers/cpuidle}} &amp;ndash; CPU idle governors and drivers
: {{The Linux Kernel/source|kernel/power/qos.c}} &amp;ndash; PM quality of service
:: {{The Linux Kernel/id|cpu_latency_qos_miscdev}} &amp;ndash; implementation of /dev/cpu_dma_latency


📖 References
:: {{The Linux Kernel/doc|CPU Idle Time Management|admin-guide/pm/cpuidle.html}}


📚 Further reading
:: https://lwn.net/Kernel/Index/#Power_management-cpuidle
: {{The Linux Kernel/doc|PM Quality Of Service Interface|power/pm_qos_interface.html}}

==== Power and frequency ====


P-states, {{w|ACPI#Performance_state|performance states}}:
: P0 &amp;ndash; maximum power and frequency
: Pn &amp;ndash; less power and frequency
: ...


⚲ API
: Reliable measurement of actual CPU frequency
:: [https://manpages.debian.org/testing/linux-cpupower/turbostat.8.en.html turbostat] --quiet --show CPU,Bzy_MHz -n 1 --interval 0.1
::: Bzy_MHz &amp;ndash; average clock rate while the CPU was not idle (ie. in &quot;c0&quot; state).
: [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=intel_pstate intel_pstate=]
:: {{The Linux Kernel/doc|Kernel Command Line Options for intel_pstate|admin-guide/pm/intel_pstate.html#kernel-command-line-options-for-intel-pstate}}
: [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=cpufreq.default_governor cpufreq.default_governor=]
: P-states interfaces:
:: /sys/devices/system/cpu/cpufreq/
:: /sys/devices/system/cpu/cpu*/cpufreq/
::: scaling_cur_freq &amp;ndash; unreliable assumption on CPU frequency
:: /sys/devices/system/cpu/intel_pstate/
:: {{The Linux Kernel/include|linux/cpufreq.h}}
:: {{The Linux Kernel/include|linux/sched/cpufreq.h}} &amp;ndash; interface between cpufreq drivers and the scheduler


⚙️ Internals
: {{The Linux Kernel/source|drivers/cpufreq}} &amp;ndash; CPU frequency scaling drivers
:: {{The Linux Kernel/id|intel_pstate}}
:: {{The Linux Kernel/id|acpi_cpufreq_driver}}
: {{The Linux Kernel/source|kernel/sched/cpufreq_schedutil.c}} &amp;ndash; implementation of cpufreq.default_governor=schedutil
: {{The Linux Kernel/source|arch/x86/kernel/cpu/intel_epb.c}} &amp;ndash; Intel Performance and Energy Bias Hint support


📖 References
: {{The Linux Kernel/doc|CPU Performance Scaling|admin-guide/pm/cpufreq.html}}
: {{The Linux Kernel/doc|Device Frequency Scaling|driver-api/devfreq.html}}
: [https://www.kernel.org/doc/Documentation/cpu-freq/governors.txt CPUFreq Governor]
: {{The Linux Kernel/doc|CPUFreq - CPU frequency and voltage scaling|cpu-freq}}
: {{The Linux Kernel/doc|Intel Performance and Energy Bias Hint|admin-guide/pm/intel_epb.html}}
: {{The Linux Kernel/doc|intel_pstate CPU Performance Scaling Driver|admin-guide/pm/intel_pstate.html}}
:: {{The Linux Kernel/doc|General Information|admin-guide/pm/intel_pstate.html#general-information}} 
:: {{The Linux Kernel/doc|Operation Modes|admin-guide/pm/intel_pstate.html#operation-modes}} 
::: {{The Linux Kernel/doc|Active Mode|admin-guide/pm/intel_pstate.html#active-mode}}
&lt;!--
:::: {{The Linux Kernel/doc|Active Mode With HWP|admin-guide/pm/intel_pstate.html#active-mode-with-hwp}} 
::::: {{The Linux Kernel/doc|HWP + performance|admin-guide/pm/intel_pstate.html#hwp-performance}} 
::::: {{The Linux Kernel/doc|HWP + powersave|admin-guide/pm/intel_pstate.html#hwp-powersave}} 
:::: {{The Linux Kernel/doc|Active Mode Without HWP|admin-guide/pm/intel_pstate.html#active-mode-without-hwp}} 
::::: {{The Linux Kernel/doc|performance|admin-guide/pm/intel_pstate.html#performance}} 
::::: {{The Linux Kernel/doc|powersave|admin-guide/pm/intel_pstate.html#powersave}} 
--&gt;
::: {{The Linux Kernel/doc|Passive Mode|admin-guide/pm/intel_pstate.html#passive-mode}} 
:: {{The Linux Kernel/doc|Turbo P-states Support|admin-guide/pm/intel_pstate.html#turbo-p-states-support}} 
:: {{The Linux Kernel/doc|Processor Support|admin-guide/pm/intel_pstate.html#processor-support}} 
:: {{The Linux Kernel/doc|Support for Hybrid Processors|admin-guide/pm/intel_pstate.html#support-for-hybrid-processors}} 
::: {{The Linux Kernel/doc|Hybrid Processors with SMT|admin-guide/pm/intel_pstate.html#hybrid-processors-with-smt}} 
::: {{The Linux Kernel/doc|Capacity-Aware Scheduling Support|admin-guide/pm/intel_pstate.html#capacity-aware-scheduling-support}} 
::: {{The Linux Kernel/doc|Energy-Aware Scheduling Support|admin-guide/pm/intel_pstate.html#energy-aware-scheduling-support}} 
:: {{The Linux Kernel/doc|User Space Interface in sysfs|admin-guide/pm/intel_pstate.html#user-space-interface-in-sysfs}} 
::: {{The Linux Kernel/doc|Global Attributes|admin-guide/pm/intel_pstate.html#global-attributes}} 
::: {{The Linux Kernel/doc|Interpretation of Policy Attributes|admin-guide/pm/intel_pstate.html#interpretation-of-policy-attributes}} 
::: {{The Linux Kernel/doc|Coordination of P-State Limits|admin-guide/pm/intel_pstate.html#coordination-of-p-state-limits}} 
::: {{The Linux Kernel/doc|Energy vs Performance Hints|admin-guide/pm/intel_pstate.html#energy-vs-performance-hints}} 
:: {{The Linux Kernel/doc|intel_pstate vs acpi-cpufreq|admin-guide/pm/intel_pstate.html#intel-pstate-vs-acpi-cpufreq}} 
:: {{The Linux Kernel/doc|Kernel Command Line Options for intel_pstate|admin-guide/pm/intel_pstate.html#kernel-command-line-options-for-intel-pstate}} 
:: {{The Linux Kernel/doc|Diagnostics and Tuning|admin-guide/pm/intel_pstate.html#diagnostics-and-tuning}} 
::: {{The Linux Kernel/doc|Trace Events|admin-guide/pm/intel_pstate.html#trace-events}} 
::: {{The Linux Kernel/doc|ftrace|admin-guide/pm/intel_pstate.html#ftrace}} 
&lt;!-- end of intel_pstate.html --&gt;


📚 Further reading
: https://lwn.net/Kernel/Index/#Power_management-Frequency_scaling
: [https://wiki.archlinux.org/title/CPU_frequency_scaling CPU frequency scaling]
: {{The Linux Kernel/ltp|kernel/device-drivers|cpufreq}}
: [https://www.thinkwiki.org/wiki/How_to_use_cpufrequtils How to use cpufrequtils] 
:: [https://linux.die.net/man/1/cpufreq-info cpufreq-info]
:: [https://linux.die.net/man/1/cpufreq-set cpufreq-set]
: https://github.com/intel/power-optimization-library
: https://github.com/intel/kubernetes-power-manager

{{BookCat}}</text>
      <sha1>0u2ktj1wuhyxrh2g7hvycjr8al6nsia</sha1>
    </revision>
    <revision>
      <id>4656108</id>
      <parentid>4656078</parentid>
      <timestamp>2026-08-02T20:39:34Z</timestamp>
      <contributor>
        <username>Conan</username>
        <id>3188</id>
      </contributor>
      <minor />
      <comment>Clock infrastructure, C-states, timer/clock disambiguation</comment>
      <origin>4656108</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="56954" sha1="mlxs6sq7kka22gvgldl52b9tjricolx" xml:space="preserve">&lt;noinclude&gt;{{DISPLAYTITLE:Interrupts and CPU}}&lt;/noinclude&gt;
== Interrupts ==
An {{w|interrupt}} is a signal to the processor emitted by hardware or software indicating an event that needs immediate attention.
An interrupt alerts the processor to a high-priority condition requiring the interruption of the current code the processor is executing.
The processor responds by suspending its current activities, saving its state, and executing a function called an ''interrupt handler'' (or an interrupt service routine, ISR) to deal with the event.
This interruption is temporary, and, after the interrupt handler finishes, the processor resumes normal activities.

There are two types of interrupts: hardware interrupts and software interrupts.
Hardware interrupts are used by devices to communicate that they require attention from the operating system.
For example, pressing a key on the keyboard or moving the mouse triggers hardware interrupts that cause the processor to read the keystroke or mouse position.
Unlike the software type, hardware interrupts are asynchronous and can occur in the middle of instruction execution, requiring additional care in programming.
The act of initiating a hardware interrupt is referred to as an ''interrupt request'' - IRQ ↪ {{w|Interrupt descriptor table|IDT}} ↪ {{The Linux Kernel/id|common_interrupt}} on x86.

A software interrupt is caused either by an exceptional condition in the processor itself, or a special instruction in the instruction set which causes an interrupt when it is executed.
The former is often called a ''{{w|Trap (computing)|trap}}'' (⚙️ {{The Linux Kernel/id|do_trap}}) or ''exception'' and is used for errors or events occurring during program execution that are exceptional enough that they cannot be handled within the program itself.
For example, if the processor's arithmetic logic unit is commanded to divide a number by zero, this impossible demand will cause a ''divide-by-zero exception'' (⚙️ {{The Linux Kernel/id|X86_TRAP_DE}}), perhaps causing the computer to abandon the calculation or display an error message.
Software interrupt instructions function similarly to subroutine calls and are used for a variety of purposes, such as to request services from low-level system software such as device drivers.
For example, computers often use software interrupt instructions to communicate with the disk controller to request data be read or written to the disk.

Each interrupt has its own interrupt handler.  The number of hardware interrupts is limited by the number of interrupt request (IRQ) lines to the processor, but there may be hundreds of different software interrupts.


⚲ API

: /proc/interrupts
: {{The Linux Kernel/man|1|irqtop}} &amp;ndash; utility to display kernel interrupt information
: [https://github.com/Irqbalance/irqbalance irqbalance] &amp;ndash; distribute hardware interrupts across processors on a multiprocessor system
: There are many ways to request ISR, two of them
: {{The Linux Kernel/id|devm_request_threaded_irq}} &amp;ndash; preferable, managed device with threaded ISR
: {{The Linux Kernel/id|devm_request_irq}} &amp;ndash; managed version
:: {{The Linux Kernel/id|request_irq}}
::: {{The Linux Kernel/id|request_threaded_irq}}
: {{The Linux Kernel/id|free_irq}}
: {{The Linux Kernel/include|linux/interrupt.h}} &amp;ndash; main interrupt support header
:: {{The Linux Kernel/id|irqaction}} &amp;ndash; contains handler functions 
: {{The Linux Kernel/include|linux/irq.h}}
:: {{The Linux Kernel/id|irq_data}}
: {{The Linux Kernel/include|linux/irqflags.h}}
:: {{The Linux Kernel/id|irqs_disabled}}
:: {{The Linux Kernel/id|local_irq_save}} ...
:: {{The Linux Kernel/id|local_irq_disable}} ...
: {{The Linux Kernel/include|linux/irqdesc.h}}
:: {{The Linux Kernel/id|irq_desc}}
: {{The Linux Kernel/include|linux/irqdomain.h}}
:: {{The Linux Kernel/id|irq_domain}} &amp;ndash; hardware interrupt number translation object
:: {{The Linux Kernel/id|irq_domain_get_irq_data}}
: {{The Linux Kernel/include|linux/msi.h}} &amp;ndash; {{w|Message Signaled Interrupts}}
:: {{The Linux Kernel/id|msi_desc}}
: Structure of structures:
:: {{The Linux Kernel/id|irq_desc}} is container of
::: {{The Linux Kernel/id|irq_data}}
:::: irq &amp;ndash; interrupt number
::: {{The Linux Kernel/id|irq_common_data}}
::: list of {{The Linux Kernel/id|irqaction}}


⚙️ Internals

: {{The Linux Kernel/source|kernel/irq/settings.h}} &amp;ndash; IRQ descriptor status flags
: {{The Linux Kernel/source|kernel/irq}} &amp;ndash; generic IRQ handling
:: {{The Linux Kernel/source|kernel/irq/internals.h}} &amp;ndash; IRQ subsystem internal functions
: ls /sys/kernel/debug/irq/domains/
:: {{The Linux Kernel/id|x86_vector_domain}}, {{The Linux Kernel/id|x86_vector_domain_ops}}
: {{The Linux Kernel/id|irq_chip}}
: {{The Linux Kernel/id|load_idt}} &amp;ndash; load Interrupt Descriptor Table
: {{The Linux Kernel/source|arch/x86/include/asm/idtentry.h}} &amp;ndash; interrupt entry/exit definitions
: {{The Linux Kernel/source|arch/x86/include/asm/hw_irq.h}} &amp;ndash; x86 hardware IRQ definitions
:: {{The Linux Kernel/id|irq_entries_start}} &amp;ndash; hardware IRQ entry stubs
: {{The Linux Kernel/source|arch/x86/kernel/irq.c}} &amp;ndash; x86 interrupt handling
:: {{The Linux Kernel/id|common_interrupt}} &amp;ndash; handles all normal device IRQs on x86
: {{The Linux Kernel/source|arch/x86/kernel/apic}} &amp;ndash; {{w|Advanced Programmable Interrupt Controller|APIC}}
:: {{The Linux Kernel/source|arch/x86/kernel/apic/apic.c}} &amp;ndash; local APIC core (timer, calibration, spurious interrupt)
:: {{The Linux Kernel/source|arch/x86/kernel/apic/io_apic.c}} &amp;ndash; {{w|IOAPIC|I/O APIC}}, routes device IRQs to CPUs
:: {{The Linux Kernel/source|arch/x86/kernel/apic/x2apic_cluster.c}} &amp;ndash; {{w|x2APIC}} (&gt;256 CPUs)
:: {{The Linux Kernel/source|arch/x86/kernel/apic/ipi.c}} &amp;ndash; {{w|Inter-processor interrupt|IPI}}, see [[#IPI|IPI]]
:: {{The Linux Kernel/source|arch/x86/kernel/apic/hw_nmi.c}} &amp;ndash; hardware NMI watchdog via APIC
:: {{The Linux Kernel/source|arch/x86/kernel/apic/vector.c}} &amp;ndash; IRQ vector allocation
:: {{The Linux Kernel/source|arch/x86/kernel/apic/msi.c}} &amp;ndash; {{w|Message Signaled Interrupts|MSI}} via APIC

📖 References
: {{The Linux Kernel/doc|IRQs|core-api/irq}}
:: {{The Linux Kernel/doc|The irq_domain interrupt number mapping library|core-api/irq/irq-domain.html}}
: {{The Linux Kernel/doc|Linux generic IRQ handling|core-api/genericirq.html}}
: {{The Linux Kernel/doc|Message Signaled Interrupts: The MSI Driver Guide|PCI/msi-howto.html}}
: {{The Linux Kernel/doc|Lock types and their rules|locking/locktypes.html}}
: {{The Linux Kernel/doc|Hard IRQ Context|kernel-hacking/locking.html#hard-irq-context}}
: [https://0xax.gitbooks.io/linux-insides/content/Interrupts/ Interrupts]


👁 Examples
: {{The Linux Kernel/id|dummy_irq_chip}} &amp;ndash; dummy interrupt chip implementation
: {{The Linux Kernel/source|lib/locking-selftest.c}} &amp;ndash; locking correctness self-tests


=== IRQ affinity ===

⚲ API
: /proc/irq/default_smp_affinity
: /proc/irq/*/smp_affinity and /proc/irq/*/smp_affinity_list


Common types and functions:
: struct {{The Linux Kernel/id|irq_affinity}} &amp;ndash; description for automatic irq affinity assignments, see {{The Linux Kernel/id|devm_platform_get_irqs_affinity}}
: struct {{The Linux Kernel/id|irq_affinity_desc}} &amp;ndash; interrupt affinity descriptor, see {{The Linux Kernel/id|irq_update_affinity_desc}}, {{The Linux Kernel/id|irq_create_affinity_masks}}
: {{The Linux Kernel/id|irq_set_affinity}}
: {{The Linux Kernel/id|irq_get_affinity_mask}} 
: {{The Linux Kernel/id|irq_can_set_affinity}}
: {{The Linux Kernel/id|irq_set_affinity_hint}} 
: {{The Linux Kernel/id|irqd_affinity_is_managed}} 
: {{The Linux Kernel/id|irq_data_get_affinity_mask}}
: {{The Linux Kernel/id|irq_data_get_effective_affinity_mask}} 
: {{The Linux Kernel/id|irq_data_update_effective_affinity}} 
: {{The Linux Kernel/id|irq_set_affinity_notifier}} 
: {{The Linux Kernel/id|irq_affinity_notify}} 
: {{The Linux Kernel/id|irq_chip_set_affinity_parent}} 
: {{The Linux Kernel/id|irq_set_vcpu_affinity}}


🛠️ Utilities
: [https://man.archlinux.org/man/extra/irqbalance/irqbalance.1.en irqbalance] – distributes hardware interrupts across CPUs


📖 References
: {{The Linux Kernel/doc|SMP IRQ affinity|core-api/irq/irq-affinity.html}}
: [https://wiki.linuxfoundation.org/realtime/documentation/howto/tools/cpu-partitioning/start#irq_affinity IRQ affinity, LF]
: [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=managed_irq managed_irq kernel parameter], [https://lore.kernel.org/lkml/?q=managed_irq @LKML]
: [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=irqaffinity= irqaffinity kernel parameter], [https://lore.kernel.org/lkml/?q=irqaffinity @LKML]


=== Non-maskable interrupts ===

⚲ API
: {{The Linux Kernel/include|linux/nmi.h}}
:: {{The Linux Kernel/id|in_nmi}}
:: {{The Linux Kernel/id|touch_nmi_watchdog}}
:: ...
: {{The Linux Kernel/include|trace/events/nmi.h}}
: {{The Linux Kernel/source|arch/x86/include/asm/nmi.h}} &amp;ndash; x86 NMI handler registration
:: {{The Linux Kernel/id|register_nmi_handler}}
:: {{The Linux Kernel/id|unregister_nmi_handler}}


⚙️ Internals
: {{The Linux Kernel/source|arch/x86/kernel/nmi.c}} &amp;ndash; x86 NMI handler
: {{The Linux Kernel/source|arch/x86/kernel/apic/hw_nmi.c}} &amp;ndash; hardware NMI watchdog via APIC
: {{The Linux Kernel/source|arch/x86/kernel/nmi_selftest.c}} &amp;ndash; NMI IPI self-tests


📖 References
: {{The Linux Kernel/doc|NMI Trace Events|trace/events-nmi.html}}


📚 Further reading
: [https://0xax.gitbooks.io/linux-insides/content/Interrupts/linux-interrupts-6.html Non-maskable interrupt handler] (NMI)


=== ... ===

📚 Further reading about interrupts
: IDT &amp;ndash; {{w|Interrupt descriptor table}}
: [https://www.felixcloutier.com/x86/lgdt:lidt LGDT/LIDT &amp;ndash; Load Global/Interrupt Descriptor Table Register] asm instruction

== Deferred works ==

=== Scheduler context ===

==== kthread work ====

This framework simplifies the use of kernel kthreads.
A {{The Linux Kernel/id|kthread_work}} item can be queued with {{The Linux Kernel/id|kthread_queue_work}} and flushed using {{The Linux Kernel/id|kthread_flush_work}}.
All queued kthread_work items are processed by a dedicated kernel thread executing the {{The Linux Kernel/id|kthread_worker_fn}} function.

⚲ API
: {{The Linux Kernel/id|kthread_work}} &amp;ndash; contains {{The Linux Kernel/id|kthread_work_func_t}} to execute
:: {{The Linux Kernel/id|kthread_init_work}}
:: {{The Linux Kernel/id|kthread_flush_work}}
: {{The Linux Kernel/id|kthread_worker}} &amp;ndash; links a kthread_work and a task
:: {{The Linux Kernel/id|kthread_run_worker}} &amp;ndash; creates and wakes a kthread worker
::: {{The Linux Kernel/id|kthread_create_worker}}
::: {{The Linux Kernel/id|kthread_flush_worker}}
:: {{The Linux Kernel/id|kthread_destroy_worker}}
: {{The Linux Kernel/id|kthread_queue_work}} &amp;ndash; queues a kthread_work on a kthread_worker


⚙️ Internals
: {{The Linux Kernel/id|__kthread_create_worker_on_node}}
: {{The Linux Kernel/id|kthread_worker_fn}} &amp;ndash; executes work's function


👁 Example usages
: {{The Linux Kernel/id|watchdog_kworker}}, {{The Linux Kernel/id|pwq_release_worker}}, {{The Linux Kernel/id|pump_messages}}

==== Threaded IRQ ====

⚲ API
{{The Linux Kernel/id|devm_request_threaded_irq}}, {{The Linux Kernel/id|request_threaded_irq}}
ISR should return IRQ_WAKE_THREAD to run thread function

⚙️ Internals
: {{The Linux Kernel/id|setup_irq_thread}}, {{The Linux Kernel/id|irq_thread}}
: {{The Linux Kernel/source|kernel/irq/manage.c}} &amp;ndash; IRQ request, free and affinity management

📖 References
: {{The Linux Kernel/doc|request_threaded_irq|core-api/genericirq.html#c.request_threaded_irq}}


==== Work and workqueue ====

Generic async execution with shared worker pool.

⚲ API
: {{The Linux Kernel/id|PF_WQ_WORKER}} &amp;ndash; workqueue worker process flag
: {{The Linux Kernel/include|linux/workqueue.h}}, {{The Linux Kernel/include|linux/workqueue_types.h}}
: {{The Linux Kernel/id|work_struct}}, {{The Linux Kernel/id|INIT_WORK}}
: {{The Linux Kernel/id|delayed_work}}, {{The Linux Kernel/id|INIT_DELAYED_WORK}}, {{The Linux Kernel/id|cancel_delayed_work_sync}}
: {{The Linux Kernel/id|workqueue_struct}}
:: {{The Linux Kernel/id|devm_alloc_workqueue}}
::: {{The Linux Kernel/id|alloc_workqueue}}
:: {{The Linux Kernel/id|destroy_workqueue}}
: {{The Linux Kernel/id|schedule_work}} &amp;ndash; queues work on the system workqueue ↯
:: {{The Linux Kernel/id|queue_work}} &amp;ndash; queues work on a workqueue
::: {{The Linux Kernel/id|queue_work_on}} &amp;ndash; on a specific CPU
: {{The Linux Kernel/id|show_all_workqueues}}
:: {{The Linux Kernel/id|show_one_workqueue}}
: {{The Linux Kernel/id|system_power_efficient_wq}} ...


👁 Example usage {{The Linux Kernel/source|samples/ftrace/sample-trace-array.c}}


⚙️ Internals
: {{The Linux Kernel/source|kernel/workqueue.c}} &amp;ndash; generic async execution with shared worker pool
:: {{The Linux Kernel/id|workqueue_init}}
::: {{The Linux Kernel/id|create_worker}}
:::: {{The Linux Kernel/id|worker_thread}}
::::: {{The Linux Kernel/id|process_one_work}}
:: {{The Linux Kernel/id|format_worker_id}} &amp;ndash; names kworker kthreads
:: {{The Linux Kernel/id|pool_workqueue}}
::: {{The Linux Kernel/id|worker_pool}}


📖 References
: {{The Linux Kernel/doc|Concurrency Managed Workqueue|core-api/workqueue.html}}
: [https://sysprog21.github.io/lkmpg/#work-queues LKMPG: Work queues]

=== Interrupt context ===

: {{The Linux Kernel/include|linux/irq_work.h}} &amp;ndash; run callbacks from hardirq or NMI context where normal work queues can't be used
:: {{The Linux Kernel/id|irq_work_queue}} &amp;ndash; enqueue work on the current CPU, triggers {{The Linux Kernel/id|IRQ_WORK_VECTOR}} IPI if needed
:: {{The Linux Kernel/id|irq_work_sync}} &amp;ndash; wait for completion
:: {{The Linux Kernel/source|kernel/irq_work.c}} &amp;ndash; irq_work implementation
:: 👁 {{The Linux Kernel/source|samples/trace_printk/trace-printk.c}}

==== Timers ====

⚠️ &quot;Timer&quot; in the kernel means different things: ''[[#softirq_timer|kernel timer]]'' – jiffies-based software callback, ''[[#High-resolution_timer|hrtimer]]'' – nanosecond software callback, ''[[The_Linux_Kernel/Multitasking#POSIX_Timers|POSIX timer]]'' – userspace API, ''[[The_Linux_Kernel/Debugging#Watchdogs|watchdog timer]]'' – hang detection, ''[[#Clock_infrastructure|local APIC timer]]'' – per-CPU hardware, drives the tick.

===== softirq timer =====

This timer is a softirq for periodical tasks with jiffies resolution

⚲ API
: {{The Linux Kernel/include|linux/timer.h}}
: {{The Linux Kernel/id|timer_list}}, {{The Linux Kernel/id|DEFINE_TIMER}}, {{The Linux Kernel/id|timer_setup}}
: {{The Linux Kernel/id|mod_timer}} &amp;mdash; sets expiration time in jiffies. 
: {{The Linux Kernel/id|del_timer}}


⚙️ Internals
: {{The Linux Kernel/source|kernel/time/timer.c}} &amp;ndash; kernel internal timers
:: {{The Linux Kernel/id|timer_bases}}


👁 Examples
: {{The Linux Kernel/id|input_enable_softrepeat}} and {{The Linux Kernel/id|input_start_autorepeat}}


📚 References
: {{The Linux Kernel/doc|Time and timer routines|driver-api/basics.html#time-and-timer-routines}}
:: {{The Linux Kernel/doc|mod_timer_pending ... |driver-api/basics.html#c.mod_timer_pending}}

===== High-resolution timer =====

⚲ API
: /proc/timer_list
: /proc/sys/kernel/timer_migration
: {{The Linux Kernel/include|linux/hrtimer_defs.h}}
: {{The Linux Kernel/include|linux/hrtimer.h}}
: {{The Linux Kernel/id|hrtimer}}, hrtimer.function &amp;mdash; callback
: {{The Linux Kernel/id|hrtimer_init}}
: {{The Linux Kernel/id|hrtimer_setup}}
: {{The Linux Kernel/id|hrtimer_start}} &amp;mdash; starts a timer with nanosecond resolution 
: {{The Linux Kernel/id|hrtimer_cancel}}


👁 Examples {{The Linux Kernel/id|alarm_init}}, {{The Linux Kernel/id|watchdog_enable}}


⚙️ Internals
: {{The Linux Kernel/id|CONFIG_HIGH_RES_TIMERS}}
: {{The Linux Kernel/source|kernel/time/tick-internal.h}} &amp;ndash; tick and timer internal definitions
:: {{The Linux Kernel/id|hrtimer_bases}}
: {{The Linux Kernel/source|kernel/time/hrtimer.c}} &amp;ndash; high-resolution timer implementation
: {{The Linux Kernel/source|kernel/time/itimer.c}} &amp;ndash; interval timers
: {{The Linux Kernel/source|kernel/time/timer_list.c}} &amp;ndash; /proc/timer_list debugfs


📚 HR timers references
: {{The Linux Kernel/doc|High-resolution timers|driver-api/basics.html#high-resolution-timers}}
: {{The Linux Kernel/doc|hrtimers - subsystem for high-resolution kernel timers|timers/hrtimers.html}}
: {{The Linux Kernel/doc|high resolution timers and dynamic ticks design notes|timers/highres.html}}

===== Tick and NO_HZ =====

The tick is the periodic timer interrupt that drives scheduling, timekeeping, and RCU.
The NO_HZ subsystem reduces or eliminates tick interrupts to save power and reduce latency.

⚲ API
: /sys/devices/system/cpu/nohz_full – active nohz_full CPUs
: [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=nohz_full= nohz_full=] boot parameter – list of CPUs to run tickless
: {{The Linux Kernel/include|linux/tick.h}} – tick control API
:: {{The Linux Kernel/id|tick_nohz_full_running}} – true if any CPU runs tickless

🪛 Compile-time configurations ({{The Linux Kernel/source|kernel/time/Kconfig}})
: {{The Linux Kernel/id|CONFIG_HZ_PERIODIC}} – constant-rate tick, always firing
: {{The Linux Kernel/id|CONFIG_NO_HZ_IDLE}} – stop tick when CPU is idle (default on most distros)
: {{The Linux Kernel/id|CONFIG_NO_HZ_FULL}} – stop tick even when running a single task, for RT and latency-sensitive workloads, see [[#CPU_isolation|CPU isolation]]

⚙️ Internals
: {{The Linux Kernel/source|kernel/time/tick-common.c}} – periodic tick setup
: {{The Linux Kernel/source|kernel/time/tick-oneshot.c}} – oneshot mode for hrtimers and NO_HZ
: {{The Linux Kernel/source|kernel/time/tick-sched.c}} – NO_HZ tick scheduling logic
: {{The Linux Kernel/source|kernel/time/tick-broadcast.c}} – broadcast tick for CPUs in deep idle where local timer stops ([[#Idle|C3+]])
: {{The Linux Kernel/source|kernel/time/timer_migration.c}} – migrate timers from idle to busy CPUs

📖 References
: {{The Linux Kernel/doc|NO_HZ: Reducing Scheduling-Clock Ticks|timers/no_hz.html}}
: [https://wiki.linuxfoundation.org/realtime/documentation/howto/tools/ticklesskernel Tickless kernel, RT wiki]
: {{The Linux Kernel/doc|high resolution timers and dynamic ticks design notes|timers/highres.html}}

===== Clock infrastructure =====

⚠️ Not to confuse: ''[[The_Linux_Kernel/System#Hardware_Device_Drivers|clk framework]]'' – SoC {{w|Clock signal|clock}} tree management in drivers/clk.

Clocksources read current time (passive counters).
Clock event devices fire interrupts at a programmed time (active).
Together they are the foundation for timekeeping, timers, tick, and NO_HZ.

⚲ Clocksources – &quot;what time is it?&quot;
: /sys/devices/system/clocksource/clocksource0/current_clocksource
: /sys/devices/system/clocksource/clocksource0/available_clocksource
:: {{w|Time Stamp Counter|TSC}} – fastest, per-CPU, x86
:: {{w|High Precision Event Timer|HPET}} – system-wide, MMIO
:: ACPI PM timer – never stops in any C-state, slow
: {{The Linux Kernel/include|linux/clocksource.h}} – {{The Linux Kernel/id|clocksource}}, {{The Linux Kernel/id|clocksource_register_hz}}

⚲ Clock event devices – &quot;wake me at time X&quot;
: {{The Linux Kernel/include|linux/clockchips.h}} – {{The Linux Kernel/id|clock_event_device}}, {{The Linux Kernel/id|clockevents_config_and_register}}
: Local {{w|Advanced Programmable Interrupt Controller|APIC}} timer – per-CPU, fastest, stops in [[#Idle|C3+]], {{The Linux Kernel/id|local_apic_timer_interrupt}}
: {{w|High Precision Event Timer|HPET}} – system-wide, used as broadcast fallback
&lt;!-- PIT (i8254) – legacy, stopped at boot on modern hardware --&gt;

⚙️ Internals
: {{The Linux Kernel/source|kernel/time/clocksource.c}} – clocksource selection and watchdog
: {{The Linux Kernel/source|kernel/time/clockevents.c}} – clock event device framework
: {{The Linux Kernel/source|kernel/time/jiffies.c}} – jiffies clocksource (fallback)

===== ... =====

📖 Timers references
: {{The Linux Kernel/doc|Timers|timers}}
: [https://lwn.net/Articles/913568/ Better CPU selection for timer expiration]

==== Tasklet ====

tasklet is a softirq, for time critical operations

⚲ API is deprecated in favor of threaded IRQs: {{The Linux Kernel/id|devm_request_threaded_irq}}
: {{The Linux Kernel/id|tasklet_struct}}, {{The Linux Kernel/id|tasklet_init}}, {{The Linux Kernel/id|tasklet_schedule}} 


⚙️ Internals: {{The Linux Kernel/id|tasklet_action_common}} HI_SOFTIRQ, TASKLET_SOFTIRQ


==== Softirq ====

softirq is internal system facility and should not be used directly.
Use tasklet or threaded IRQs

⚲ API
: {{The Linux Kernel/include|linux/interrupt.h}}
: cat /proc/softirqs
: {{The Linux Kernel/id|open_softirq}} registers {{The Linux Kernel/id|softirq_action}}
: {{The Linux Kernel/id|raise_softirq}}
: {{The Linux Kernel/id|tasklet_schedule}}
:: {{The Linux Kernel/id|__tasklet_schedule}}


⚙️ Internals
: {{The Linux Kernel/source|kernel/softirq.c}} &amp;ndash; software interrupt handling
:: {{The Linux Kernel/id|__do_softirq}} &amp;ndash; main softirq processing loop


📖 References
: [https://0xax.gitbooks.io/linux-insides/content/Interrupts/linux-interrupts-9.html Introduction to deferred interrupts (Softirq, Tasklets and Workqueues)]
: [https://0xax.gitbooks.io/linux-insides/content/Timers/ Timers and time management]
: [https://linux-kernel-labs.github.io/refs/heads/master/labs/deferred_work.html Deferred work, linux-kernel-labs]
: [https://www.oreilly.com/library/view/linux-device-drivers/0596005903/ch07.html Chapter 7. Time, Delays, and Deferred Work]

==CPU specific==


🖱️ GUI
: [https://manpages.ubuntu.com/manpages/kinetic/en/man8/tuna.8.html tuna] &amp;ndash; program for tuning running processes


⚲ API
: cat /proc/cpuinfo
: /sys/devices/system/cpu/
: /sys/devices/system/node/
: /sys/cpu/
: /sys/fs/cgroup/cpu/
: grep -i cpu /proc/self/status
: [https://manpages.ubuntu.com/manpages/jammy/man1/rdmsr.1.html rdmsr] &amp;ndash; tool for reading CPU machine specific registers (MSR)
: {{The Linux Kernel/man|1|lscpu}} &amp;ndash; display information about the CPU architecture

: {{The Linux Kernel/include|linux/arch_topology.h}} &amp;ndash; arch specific cpu topology information 
: {{The Linux Kernel/include|linux/cpu.h}} &amp;ndash; generic cpu definition 
: {{The Linux Kernel/include|linux/cpu_cooling.h}} 
: {{The Linux Kernel/include|linux/cpu_pm.h}} 
: {{The Linux Kernel/include|linux/cpufeature.h}}
: {{The Linux Kernel/source|arch/x86/include/asm/cpufeature.h}} &amp;ndash; x86 CPU feature detection
: {{The Linux Kernel/include|linux/peci-cpu.h}} 
: {{The Linux Kernel/include|linux/sched/cputime.h}} &amp;ndash; cputime accounting APIs
: {{The Linux Kernel/include|linux/clk.h}} &amp;ndash; interfaces for managing hardware clocks in device drivers


⚙️ Internals

: {{The Linux Kernel/source|drivers/base/cpu.c}} &amp;ndash; CPU driver model subsystem
:: {{The Linux Kernel/id|cpu_dev_init}}


=== Cache ===

: {{The Linux Kernel/include|linux/cacheflush.h}}
:: {{The Linux Kernel/source|arch/x86/include/asm/cacheflush.h}}: {{The Linux Kernel/id|clflush_cache_range}}
: {{The Linux Kernel/include|linux/cache.h}} &amp;ndash; cache line alignment macros
:: {{The Linux Kernel/id|____cacheline_aligned}} &amp;ndash; align to cache line boundary to avoid false sharing
:: {{The Linux Kernel/id|__cacheline_aligned}} &amp;ndash; same, plus place in .data..cacheline_aligned section
:: {{The Linux Kernel/id|____cacheline_aligned_in_smp}} &amp;ndash; same, but no-op on uniprocessor builds
:: {{The Linux Kernel/id|__read_mostly}} &amp;ndash; place in a cache-friendly section for rarely written data
:: {{The Linux Kernel/id|__ro_after_init}} &amp;ndash; writable during init, read-only after boot (security hardening)
:: {{The Linux Kernel/id|DEFINE_PER_CPU_CACHE_HOT}} &amp;ndash; per-CPU variable in .data..hot section, used for {{The Linux Kernel/id|current_task}}, {{The Linux Kernel/id|__preempt_count}}
:: {{The Linux Kernel/id|L1_CACHE_BYTES}}, {{The Linux Kernel/id|SMP_CACHE_BYTES}} &amp;ndash; 64 bytes typically
:: {{The Linux Kernel/source|arch/x86/include/asm/cache.h}} &amp;ndash; x86 cache line size definitions

🔨 [https://manpages.ubuntu.com/manpages/resolute/man1/stress-ng.1.html#:~:text=%2D%2Dcache stress-ng --cache]

⚙️ Internals

: {{The Linux Kernel/source|arch/x86/mm/pat/set_memory.c}} &amp;ndash; page attribute table memory type control
: {{The Linux Kernel/source|arch/x86/kernel/cpu/mtrr/}} &amp;ndash; memory type range register driver

📚 Further reading
: MTRR &amp;ndash; {{w|Memory type range register}}
: {{w|CPU cache}}

=== {{w|Symmetric_multiprocessing|SMP}} ===

This chapter is about multiprocessing and {{w|Multi-core processor|multi-core}} aspects of Linux kernel.

Key concepts and features of Linux SMP include:
* Symmetry: In an SMP system, all processors are considered the same without hardware hierarchy in contradiction to use of {{w|coprocessor}}s.
* Load balancing: The Linux kernel employs load balancing mechanisms to distribute tasks evenly among available CPU cores. This prevents any one core from becoming overwhelmed while others remain underutilized.
* Parallelism: SMP enables parallel processing, where multiple threads or processes can execute simultaneously on different CPU cores. This can significantly improve the execution speed of applications that are designed to take advantage of multiple threads.
* Thread scheduling: The Linux kernel scheduler is responsible for determining which threads or processes run on which CPU cores and for how long. It aims to optimize performance by minimizing contention and maximizing CPU utilization.
* Shared memory: In an SMP system, all CPU cores typically share the same physical memory space. This allows processes and threads running on different cores to communicate and share data more efficiently.
* NUMA &amp;ndash; {{w|Non-Uniform Memory Access}}: In larger SMP systems, memory access times might not be uniform due to the physical arrangement of memory banks and processors. Linux has mechanisms to handle NUMA architectures efficiently, allowing processes to be scheduled on CPUs closer to their associated memory.
* Cache coherency: SMP systems require mechanisms to ensure that all CPU cores have consistent views of memory. Cache coherency protocols ensure that changes made to shared memory locations are correctly propagated to all cores.
* Scalability: SMP systems can be scaled up to include more CPU cores, enhancing the overall computing power of the system. However, as the number of cores increases, challenges related to memory access, contention, and communication between cores may arise.
* Kernel and user space: Linux applications running in user space can take advantage of SMP without needing to be aware of the underlying hardware details. The kernel handles the management of CPU cores and resource allocation.


⚲ API
: &lt;code&gt;ps -PLe&lt;/code&gt; &amp;ndash; lists threads with processor that the thread last executed on (the third column PSR).
: {{The Linux Kernel/man|2|getcpu}} &amp;ndash; determine CPU and NUMA node on which the calling thread is running
: {{The Linux Kernel/man|8|chcpu}} &amp;ndash; configure CPUs
: {{The Linux Kernel/man|3|CPU_SET}} &amp;ndash; macros for manipulating CPU sets
: {{The Linux Kernel/include|linux/smp.h}}
:: The most commonly used functions:
:: {{The Linux Kernel/id|crash_smp_send_stop}} – halts all CPUs except the calling one in a crash context
:: {{The Linux Kernel/id|get_cpu}} – disables preemption and returns the current processor ID
:: {{The Linux Kernel/id|panic_smp_self_stop}} – stops the local CPU during a panic while ensuring others halt
:: {{The Linux Kernel/id|put_cpu}} – re-enables preemption after a previous get_cpu call
:: {{The Linux Kernel/id|raw_smp_processor_id}} – returns the current CPU ID without preemption safety
:: {{The Linux Kernel/id|setup_max_cpus}} – sets up the maximum number of CPUs to be brought online
:: {{The Linux Kernel/id|smp_init}} – initializes core SMP structures and state during boot
:: {{The Linux Kernel/id|smp_prepare_boot_cpu}} – prepares the boot CPU during early SMP initialization
:: {{The Linux Kernel/id|smp_prepare_cpus}} – prepares all CPUs for booting before secondary CPUs are started
:: {{The Linux Kernel/id|smp_processor_id}} – returns the ID of the current CPU with preemption checks
:: {{The Linux Kernel/id|smp_send_stop}} – stops all other CPUs in response to critical events
:: {{The Linux Kernel/id|wake_up_all_idle_cpus}} – wakes all idle CPUs to ensure prompt task execution
: {{The Linux Kernel/include|linux/cpu.h}}
: {{The Linux Kernel/include|linux/group_cpus.h}}: {{The Linux Kernel/id|group_cpus_evenly}} &amp;ndash; groups all CPUs evenly per NUMA/CPU locality
: {{The Linux Kernel/include|asm-generic/percpu.h}}
: {{The Linux Kernel/include|linux/percpu-defs.h}} &amp;ndash; basic definitions for percpu areas
:: {{The Linux Kernel/id|this_cpu_ptr}}
: {{The Linux Kernel/include|linux/percpu.h}} 
: {{The Linux Kernel/include|linux/percpu-refcount.h}} 
: {{The Linux Kernel/include|linux/percpu-rwsem.h}}
: {{The Linux Kernel/include|linux/preempt.h}}
:: {{The Linux Kernel/id|migrate_disable}}, {{The Linux Kernel/id|migrate_enable}}
: /sys/bus/cpu
: [[#per_CPU_local_lock|per CPU local_lock]]
: {{The Linux Kernel/include|linux/topology.h}} &amp;ndash; {{The Linux Kernel/id|cpu_to_node}}, {{The Linux Kernel/id|numa_node_id}}
: {{The Linux Kernel/source|arch/x86/include/asm/topology.h}} &amp;ndash; x86 NUMA and CPU topology
: See also [[../../Memory#NUMA|NUMA memory section]]


⚙️ Internals
: {{The Linux Kernel/id|boot_cpu_init}} activates the first CPU
: {{The Linux Kernel/id|smp_prepare_cpus}} initializes rest CPUs during boot
: {{The Linux Kernel/id|cpu_number}}
: {{The Linux Kernel/id|CONFIG_SMP}}
:: {{The Linux Kernel/id|CONFIG_NUMA}}
: {{The Linux Kernel/include|trace/events/percpu.h}}
: {{The Linux Kernel/file|drivers/base/cpu.c}} &amp;ndash; CPU driver model subsystem support
: {{The Linux Kernel/file|kernel/cpu.c}} &amp;ndash; CPU hotplug state machine
: smpboot
:: {{The Linux Kernel/include|linux/smpboot.h}}
:: {{The Linux Kernel/source|kernel/smpboot.c}} &amp;ndash; common SMP CPU bringup/teardown
:: {{The Linux Kernel/source|arch/x86/kernel/smpboot.c}} &amp;ndash; x86 SMP booting
: {{The Linux Kernel/source|lib/group_cpus.c}} &amp;ndash; distribute CPUs evenly across groups


🛠️ Utilities
: [https://man.archlinux.org/man/extra/irqbalance/irqbalance.1.en irqbalance] – distributes hardware interrupts across CPUs
: {{The Linux Kernel/man|8|numactl}} &amp;ndash; controls NUMA policy for processes or shared memory


📖 References
: {{The Linux Kernel/doc|Per-CPU Data|kernel-hacking/locking.html#per-cpu-data}}
: {{The Linux Kernel/doc|How CPU topology info is exported via sysfs|admin-guide/cputopology.html}}


📚 Further reading
: [https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/monitoring_and_managing_system_status_and_performance/customizing-tuned-profiles_monitoring-and-managing-system-status-and-performance#functionalities-of-the-scheduler-tuned-plug-in_customizing-tuned-profiles Functionalities of the scheduler TuneD plugin]
: [https://man.archlinux.org/man/tuned-adm.8 tuned-adm] &amp;ndash; command line tool for switching between different tuning profiles


==== {{w|Inter-processor interrupt|IPI}} ====

An inter-processor interrupt is a signal sent from one CPU to another to request an action such as rescheduling, TLB flush, or function execution.

⚲ API
: {{The Linux Kernel/id|smp_send_reschedule}} &amp;ndash; sends a reschedule IPI to a target CPU
: {{The Linux Kernel/id|smp_call_function}} &amp;ndash; invokes a function on all other CPUs via IPI
:: {{The Linux Kernel/id|smp_call_function_many}} &amp;ndash; on a specified set of CPUs
: {{The Linux Kernel/id|smp_call_function_single}} &amp;ndash; on a single target CPU
:: {{The Linux Kernel/id|smp_call_function_single_async}} &amp;ndash; asynchronous variant
: {{The Linux Kernel/id|smp_call_on_cpu}} &amp;ndash; execute on a specific CPU and wait for result
: {{The Linux Kernel/id|on_each_cpu}} &amp;ndash; run a function on all CPUs
:: {{The Linux Kernel/id|on_each_cpu_mask}} &amp;ndash; on a specified set of CPUs
:: {{The Linux Kernel/id|on_each_cpu_cond_mask}} &amp;ndash; conditionally on selected CPUs
: {{The Linux Kernel/id|smp_call_func_t}} &amp;ndash; callback typedef

⚙️ Internals
: {{The Linux Kernel/include|trace/events/ipi.h}}
: {{The Linux Kernel/file|kernel/irq/ipi.c}} &amp;ndash; generic IPI helpers
:: {{The Linux Kernel/id|ipi_send_single}}, {{The Linux Kernel/id|ipi_send_mask}}
: {{The Linux Kernel/source|arch/x86/kernel/apic/ipi.c}} &amp;ndash; x86 IPI via APIC
: {{The Linux Kernel/source|arch/x86/include/asm/irq_vectors.h}} &amp;ndash; x86 IPI vector types:
:: {{The Linux Kernel/id|RESCHEDULE_VECTOR}} &amp;ndash; used by {{The Linux Kernel/id|smp_send_reschedule}}
:: {{The Linux Kernel/id|CALL_FUNCTION_VECTOR}} &amp;ndash; used by {{The Linux Kernel/id|smp_call_function_many}}
:: {{The Linux Kernel/id|CALL_FUNCTION_SINGLE_VECTOR}} &amp;ndash; used by {{The Linux Kernel/id|smp_call_function_single}}
:: {{The Linux Kernel/id|IRQ_WORK_VECTOR}} &amp;ndash; used by {{The Linux Kernel/id|irq_work_queue}}, see [[#Interrupt_context|Interrupt context]]
:: {{The Linux Kernel/id|NMI_VECTOR}} &amp;ndash; used by watchdog, {{The Linux Kernel/id|crash_smp_send_stop}}

==== CPU affinity ====

Affinity refers to assigning a process or thread to specific CPU cores.
This helps control which CPUs execute tasks, potentially improving performance by reducing data movement between cores.
It can be managed using system calls or commands.
Affinity can be represented as CPU bitmask: {{The Linux Kernel/id|cpumask_t}} or CPU affinity list: {{The Linux Kernel/id|cpulist_parse}}.


⚲ API
: {{The Linux Kernel/man|1|taskset}} &amp;ndash; set or retrieve a process's CPU affinity
: grep Cpus_allowed /proc/self/status
: {{The Linux Kernel/man|2|sched_setaffinity}} {{The Linux Kernel/man|2|sched_getaffinity}} &amp;ndash; set and get a thread's CPU affinity mask
:: ↪ {{The Linux Kernel/id|sched_setaffinity}}
: {{The Linux Kernel/id|set_cpus_allowed_ptr}} &amp;ndash; common kernel function to change a task's affinity mask
: {{The Linux Kernel/include|linux/cpu_rmap.h}} &amp;ndash; CPU affinity reverse-map support
: {{The Linux Kernel/include|linux/cpumask_types.h}}
:: struct cpumask, {{The Linux Kernel/id|cpumask_t}} &amp;ndash; CPUs bitmap, can be very big
:: {{The Linux Kernel/id|cpumask_var_t}} &amp;ndash; type for local cpumask variable, see {{The Linux Kernel/id|alloc_cpumask_var}}, {{The Linux Kernel/id|free_cpumask_var}}.
: {{The Linux Kernel/include|linux/cpumask.h}} &amp;ndash; Cpumasks provide a bitmap suitable for representing the set of CPU's in a system, one bit position per CPU number
:: {{The Linux Kernel/id|for_each_possible_cpu}}
:: {{The Linux Kernel/id|num_online_cpus}}
:: {{The Linux Kernel/id|cpumask_set_cpu}}
:: {{The Linux Kernel/id|cpumask_test_cpu}}
:: {{The Linux Kernel/id|for_each_cpu}}


⚙️ Internals
: {{The Linux Kernel/id|cpus_mask}} &amp;ndash; affinity of {{The Linux Kernel/id|task_struct}}
: {{The Linux Kernel/id|cpus_allowed}} &amp;ndash; affinity of {{The Linux Kernel/id|cpuset}}


📚 Further reading
: {{w|Processor affinity}}
: {{w|Affinity mask}}

==== CPU hotplug ====

CPU hotplugging in Linux refers to the ability to dynamically add or remove CPUs from the system without needing a reboot.
This feature is crucial in environments requiring high availability and resource flexibility, such as data centers, virtualized systems, and systems that use power management aggressively.


🗝️ Acronyms
: BP &amp;ndash; Bootstrap Processor
: AP &amp;ndash; Application Processor


⚲ API
: /sys/devices/system/cpu/cpu*/online
: /sys/devices/system/cpu/cpu*/hotplug/
: {{The Linux Kernel/include|linux/cpu.h}}
:: {{The Linux Kernel/id|add_cpu}} ...
: {{The Linux Kernel/include|linux/cpuhotplug.h}}
:: {{The Linux Kernel/id|cpuhp_state}} &amp;ndash; CPU hotplug states 
:: {{The Linux Kernel/id|cpuhp_setup_state}} ... &amp;ndash; setups hotplug state callbacks
::: {{The Linux Kernel/id|cpuhp_setup_state_multi}}
::: {{The Linux Kernel/id|cpuhp_setup_state_nocalls}}
: {{The Linux Kernel/include|linux/cpuhplock.h}} &amp;ndash; CPU hotplug locking
:: {{The Linux Kernel/id|cpus_read_lock}} ...
:: {{The Linux Kernel/id|remove_cpu}} ...


⚙️ Internals
: {{The Linux Kernel/source|kernel/cpu.c}} &amp;ndash; CPU hotplug state machine
:: {{The Linux Kernel/id|cpuhp_state}} &amp;ndash; from CPUHP_OFFLINE to CPUHP_AP_ACTIVE and CPUHP_ONLINE.
:: {{The Linux Kernel/id|cpuhp_hp_states}}
:: {{The Linux Kernel/id|boot_cpu_hotplug_init}}
:: {{The Linux Kernel/id|cpuhp_threads_init}}
:: ... {{The Linux Kernel/id|cpuhp_invoke_callback_range}} ...
: {{The Linux Kernel/source|kernel/irq/cpuhotplug.c}} &amp;ndash; IRQ migration on CPU hotunplug
: {{The Linux Kernel/source|drivers/base/cpu.c}} &amp;ndash; CPU subsystem support
:: {{The Linux Kernel/id|cpu_dev_init}}
::: ... {{The Linux Kernel/id|cpu_subsys_online}}
: {{The Linux Kernel/include|trace/events/cpuhp.h}}
: {{The Linux Kernel/include|linux/cpuhplock.h}}


👁️ Examples
: {{The Linux Kernel/id|torture_onoff}}
: {{The Linux Kernel/source|tools/testing/selftests/sched_ext/hotplug.c}} &amp;ndash; sched_ext CPU hotplug test


📖 References
: {{The Linux Kernel/doc|CPU hotplug in the Kernel|core-api/cpu_hotplug.html}}
:: {{The Linux Kernel/doc|Introduction|core-api/cpu_hotplug.html#introduction}} 
:: {{The Linux Kernel/doc|Command Line Switches|core-api/cpu_hotplug.html#command-line-switches}} 
:: {{The Linux Kernel/doc|CPU maps|core-api/cpu_hotplug.html#cpu-maps}} 
:: {{The Linux Kernel/doc|Using CPU hotplug|core-api/cpu_hotplug.html#using-cpu-hotplug}} 
:: {{The Linux Kernel/doc|The CPU hotplug coordination|core-api/cpu_hotplug.html#the-cpu-hotplug-coordination}} 
:: {{The Linux Kernel/doc|The CPU hotplug API|core-api/cpu_hotplug.html#the-cpu-hotplug-api}} 
::: {{The Linux Kernel/doc|CPU hotplug state machine|core-api/cpu_hotplug.html#cpu-hotplug-state-machine}} 
::: {{The Linux Kernel/doc|CPU online/offline operations|core-api/cpu_hotplug.html#cpu-online-offline-operations}} 
::: {{The Linux Kernel/doc|Allocating a state|core-api/cpu_hotplug.html#allocating-a-state}} 
::: {{The Linux Kernel/doc|Setup of a CPU hotplug state|core-api/cpu_hotplug.html#setup-of-a-cpu-hotplug-state}} 
::: {{The Linux Kernel/doc|Removal of a CPU hotplug state|core-api/cpu_hotplug.html#removal-of-a-cpu-hotplug-state}} 
::: {{The Linux Kernel/doc|Multi-Instance state instance management|core-api/cpu_hotplug.html#multi-instance-state-instance-management}} 
::: {{The Linux Kernel/doc|Examples|core-api/cpu_hotplug.html#examples}} 
:: {{The Linux Kernel/doc|Testing of hotplug states|core-api/cpu_hotplug.html#testing-of-hotplug-states}} 
:: {{The Linux Kernel/doc|Architecture’s requirements|core-api/cpu_hotplug.html#architecture-s-requirements}} 
:: {{The Linux Kernel/doc|User Space Notification|core-api/cpu_hotplug.html#user-space-notification}} 
:: {{The Linux Kernel/doc|Kernel Inline Documentations Reference|core-api/cpu_hotplug.html#kernel-inline-documentations-reference}}
 

🔨 [https://manpages.ubuntu.com/manpages/resolute/man1/stress-ng.1.html#:~:text=%2D%2Dcpu%2Donline stress-ng --cpu-online]

📚 Further reading
: {{The Linux Kernel/id|CONFIG_CPU_HOTPLUG_STATE_CONTROL}} &amp;ndash; enables the ability to write incremental steps between &quot;offline&quot; and &quot;online&quot; states to the CPU's sysfs target file, allowing for more granular control of state transitions.
:: {{The Linux Kernel/id|target_store}}: {{The Linux Kernel/id|cpu_up}}/{{The Linux Kernel/id|cpu_down}}
: [https://lore.kernel.org/lkml/?q=cpuhotplug+OR+cpuhp cpuhotplug, cpuhp @LKML]

==== CPU isolation ====

CPU isolation ensures that specific tasks run on dedicated CPUs, reducing contention and latency.

'''Housekeeping''' CPUs refer to the CPUs that are reserved for various '''system''' tasks. See {{The Linux Kernel/id|hk_type}}.

'''Isolated''' CPUs are dedicated to '''real-time''' applications, such as DPDK.

⚲ API
: /sys/devices/system/cpu/isolated
: /sys/devices/system/cpu/nohz_full
: [https://docs.kernel.org/admin-guide/cgroup-v2.html#:~:text=cpuset.cpus.isolated /sys/fs/cgroup/cpuset.cpus.isolated]
: [https://docs.kernel.org/admin-guide/cgroup-v2.html#:~:text=Partition%20root%20without%20load%20balancing /sys/fs/cgroup/.../cpuset.cpus.partition]
: {{The Linux Kernel/include|linux/sched/isolation.h}}
:: {{The Linux Kernel/id|hk_type}} &amp;ndash; housekeeping type
:: {{The Linux Kernel/id|housekeeping_cpumask}} &amp;ndash; returns CPUs available for housekeeping of a given type
:: {{The Linux Kernel/id|cpu_is_isolated}}
: {{The Linux Kernel/include|linux/cpuset.h}} &amp;ndash; cpuset interface
: {{The Linux Kernel/man|7|cpuset}} &amp;ndash; confine processes to processor and memory node subsets


⚙️ Internals
: {{The Linux Kernel/id|CONFIG_CPU_ISOLATION}}
:: {{The Linux Kernel/source|kernel/sched/isolation.c}} &amp;ndash; housekeeping CPU management
::: {{The Linux Kernel/id|housekeeping_init}}, {{The Linux Kernel/id|housekeeping_update}}
: {{The Linux Kernel/id|CONFIG_CPUSETS}}
:: {{The Linux Kernel/source|kernel/cgroup/cpuset.c}} &amp;ndash; cpuset cgroup controller
::: {{The Linux Kernel/id|cpuset_init}}
::: {{The Linux Kernel/id|cpuset_init_smp}}
::: {{The Linux Kernel/id|isolated_cpus}}
::: {{The Linux Kernel/id|partition_xcpus_add}}, {{The Linux Kernel/id|partition_xcpus_del}}


📖 References
: {{The Linux Kernel/doc|CPU lists in command-line parameters|admin-guide/kernel-parameters.html#cpu-lists}}
:: [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=nohz_full= '''nohz_full'''] clears housekeeping.{{The Linux Kernel/id|cpumasks}} for tick, wq, timer, rcu, misc, and kthread in {{The Linux Kernel/id|housekeeping_nohz_full_setup}}
:: [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=isolcpus '''isolcpus'''] clears housekeeping.{{The Linux Kernel/id|cpumasks}} for [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=domain%20isolation domain] (by default), [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=nohz nohz], and [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=managed_irq managed_irq] in {{The Linux Kernel/id|housekeeping_isolcpus_setup}}
: {{The Linux Kernel/doc|Housekeeping|core-api/housekeeping.html}}
: {{The Linux Kernel/doc|NO_HZ: Reducing Scheduling-Clock Ticks|timers/no_hz.html}}
: {{The Linux Kernel/doc|CPUSETS of cgroup v2|admin-guide/cgroup-v2.html#cpuset}}
: {{The Linux Kernel/doc|CPUSETS of cgroup v1|admin-guide/cgroup-v1/cpusets.html}}


📚 Further reading
: [https://www.youtube.com/watch?v=1lomUhSS82s CPU Isolation state of the art, LPC'23]
: [https://lpc.events/event/19/contributions/2219/ CPU Isolation and IPI interference, LPC'25]
: [https://www.suse.com/c/cpu-isolation-introduction-part-1/ CPU Isolation]
: [https://lore.kernel.org/lkml/?q=isolcpus isolcpus @LKML]
: [https://lore.kernel.org/lkml/?q=housekeeping housekeeping @LKML]
: [https://kubernetes.io/docs/tasks/administer-cluster/reserve-compute-resources/#explicitly-reserved-cpu-list Explicitly Reserved CPU List, Kubernetes Documentation]
: [https://wiki.linuxfoundation.org/realtime/documentation/howto/tools/cpu-partitioning/start CPU Partitioning]
: {{The Linux Kernel/doc|Scheduler Domains|scheduler/sched-domains.html}} &amp;ndash; the Scheduler balances CPUs (scheduling groups) within a sched domain
: [https://lore.kernel.org/lkml/?q=nohz_full nohz_full @LKML]

💾 Historical since v7.0
: {{The Linux Kernel/id|cpuset_cpu_is_isolated}} &amp;ndash; removed, use {{The Linux Kernel/id|cpu_is_isolated}} instead

=== Runtime code patching ===

The kernel patches its own machine code at boot or runtime to optimize hot paths.
Static keys patch a {{w|NOP_(code)|NOP}} to a jump (or vice versa); static calls patch indirect calls to direct calls; alternatives replace instructions based on CPU features.

⚲ API
: {{The Linux Kernel/include|linux/jump_label.h}} &amp;ndash; static keys
:: {{The Linux Kernel/id|DEFINE_STATIC_KEY_FALSE}} &amp;ndash; define a key, initially false
:: {{The Linux Kernel/id|static_branch_unlikely}} &amp;ndash; zero-cost branch check (NOP when key is false)
:: {{The Linux Kernel/id|static_branch_enable}} &amp;ndash; patch all sites to take the branch (expensive, rare use)
: {{The Linux Kernel/include|linux/static_call.h}} &amp;ndash; static calls
:: {{The Linux Kernel/id|DEFINE_STATIC_CALL}} &amp;ndash; define a call site with initial target function
:: {{The Linux Kernel/id|static_call}} &amp;ndash; invoke the patched direct call
:: {{The Linux Kernel/id|static_call_update}} &amp;ndash; change target function, patch all sites
: {{The Linux Kernel/source|arch/x86/include/asm/alternative.h}} &amp;ndash; alternatives
:: {{The Linux Kernel/id|ALTERNATIVE}} &amp;ndash; replace instructions at boot based on CPU features
:: {{The Linux Kernel/source|arch/x86/include/asm/cpufeatures.h}} &amp;ndash; X86_FEATURE_* flags


⚙️ Internals
: {{The Linux Kernel/id|CONFIG_JUMP_LABEL}}
:: {{The Linux Kernel/source|kernel/jump_label.c}} &amp;ndash; static key patching core
:: {{The Linux Kernel/source|arch/x86/kernel/jump_label.c}} &amp;ndash; x86 static key patching
: {{The Linux Kernel/id|CONFIG_HAVE_STATIC_CALL}}
:: {{The Linux Kernel/source|kernel/static_call_inline.c}} &amp;ndash; static call core
:: {{The Linux Kernel/source|arch/x86/kernel/static_call.c}} &amp;ndash; x86 static call patching
: {{The Linux Kernel/source|arch/x86/include/asm/alternative.h}} &amp;ndash; runtime instruction patching
:: {{The Linux Kernel/source|arch/x86/kernel/alternative.c}} &amp;ndash; x86 alternatives engine
::: {{The Linux Kernel/id|smp_text_poke_single}} &amp;ndash; safely patch code on SMP using INT3 breakpoints; used by static keys, static calls, ftrace, kprobes
:::: {{The Linux Kernel/id|smp_text_poke_batch_add}}
:::: {{The Linux Kernel/id|smp_text_poke_batch_finish}}


👁 Examples
: {{The Linux Kernel/id|housekeeping_overridden}}
: {{The Linux Kernel/id|preempt_schedule}}
: tracepoints


📖 References
: {{The Linux Kernel/doc|Static Keys|staging/static-keys.html}}
: {{The Linux Kernel/doc|x86 CPU feature flags|arch/x86/cpuinfo.html}}


=== {{w|Memory barrier}}s ===

Memory barriers (MB) are synchronization mechanisms used to ensure proper ordering of memory operations in a SMP environment.
They play a crucial role in maintaining the consistency and correctness of data shared among different CPU cores or processors.
MBs prevent unexpected and potentially harmful reordering of memory access instructions by the compiler or CPU, which can lead to data corruption and race conditions in a concurrent software system.

⚲ API
: {{The Linux Kernel/man|2|membarrier}}
: {{The Linux Kernel/include|asm-generic/barrier.h}}
:: {{The Linux Kernel/id|mb}}, {{The Linux Kernel/id|rmb}}, {{The Linux Kernel/id|wmb}}
:: {{The Linux Kernel/id|smp_mb}}, {{The Linux Kernel/id|smp_rmb}}, {{The Linux Kernel/id|smp_wmb}}


⚙️ Internals

: {{The Linux Kernel/source|arch/x86/include/asm/barrier.h}} &amp;ndash; x86 memory barrier instructions
: {{The Linux Kernel/source|kernel/sched/membarrier.c}} &amp;ndash; membarrier system call


📖 References
: {{The Linux Kernel/doc|Memory barriers|core-api/wrappers/memory-barriers.html}}


=== States ===

C-states and P-states are features in modern CPUs designed to improve energy efficiency.

🗝️ Acronyms
: [https://uefi.org/htmlspecs/ACPI_Spec_6_4_html/08_Processor_Configuration_and_Control/processor-power-states.html C-states] &amp;ndash; CPU(?) states, aka idle states
: EPP &amp;ndash; {{The Linux Kernel/doc|Energy Performance Preference|admin-guide/pm/amd-pstate.html#energy-performance-preference-epp-rw}}
: HWP &amp;ndash; hardware-managed P-states, see [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=hwp_only hwp_only]
: [https://www.intel.com/content/www/us/en/docs/socwatch/user-guide/2020/p-state.html P-states] &amp;ndash; Performance states, see CPU Power and frequency scaling


⚲ API
: [https://linux.die.net/man/1/cpupower cpupower]


📖 References
: {{The Linux Kernel/doc|Working-State Power Management|admin-guide/pm/working-state.html}}
: https://lwn.net/Kernel/Index/#Power_management


==== Idle ====


C-states, {{w|ACPI#Processor_states|power states}}:
: C0 – operating, executing instructions.
: C1 (Halt) – internal {{w|Clock gating|clocks stopped}}.
: C1E (Enhanced Halt) – clocks stopped, voltage and frequency reduced.
: C2 (Stop-Clock) – internal and external {{w|Clock gating|clocks stopped}}.
: C3 (Deep Sleep) – clocks stopped, L1/L2 cache may flush, local APIC timer stops, requiring [[#Clock_infrastructure|tick broadcast]].
: C4 (Deeper Sleep) – voltage reduced.
: C6 (Deep Power Down) – state saved to SRAM, voltage can drop to 0V.
: C7 (Deeper Power Down) – C6 + L3 cache flushed.
: Modern Intel typically uses C1/C1E and C6, skipping C2–C5.
: ⚠️ ACPI state names (C1_ACPI, C2_ACPI, C3_ACPI) may not match actual hardware C-states. The [https://www.felixcloutier.com/x86/monitor:mwait MWAIT] hint reveals the real state: e.g. MWAIT 0x60 = hardware C6 may appear as &quot;C3_ACPI&quot;.


⚲ API
: turbostat --show CPU --quiet -n 1 --interval 0.1 --show sysfs
: [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=idle= idle=]
: /dev/cpu_dma_latency &amp;ndash; see {{The Linux Kernel/id|set_cpu_dma_latency}}
: C-states interfaces:
:: cpupower idle-info – show driver, governor, states with latency and residency
:: /sys/devices/system/cpu/cpuidle/
:: /sys/devices/system/cpu/cpu*/cpuidle/
::: cat /sys/devices/system/cpu/cpu0/cpuidle/state*/name – list available C-states
:: {{The Linux Kernel/include|linux/cpuidle.h}} – generic framework for CPU idle power management
: {{The Linux Kernel/include|linux/pm_qos.h}}


⚙️ Internals
: {{The Linux Kernel/source|drivers/cpuidle}} – CPU idle governors and drivers
: {{The Linux Kernel/source|drivers/idle/intel_idle.c}} – {{The Linux Kernel/doc|intel_idle|admin-guide/pm/intel_idle.html}}, hardcoded C-states per CPU model, modern Intel (C1/C1E/C6)
: {{The Linux Kernel/source|drivers/acpi/processor_idle.c}} – acpi_idle, reads C-states from ACPI tables, generic fallback (C1/C2/C3)
: {{The Linux Kernel/source|kernel/power/qos.c}} – PM quality of service
:: {{The Linux Kernel/id|cpu_latency_qos_miscdev}} – implementation of /dev/cpu_dma_latency


📖 References
:: {{The Linux Kernel/doc|CPU Idle Time Management|admin-guide/pm/cpuidle.html}}
: [https://www.intel.com/content/www/us/en/support/articles/000006619/processors/intel-core-processors.html Intel C-states reference]
: [https://support.hpe.com/hpesc/public/docDisplay?docId=sd00002067en_us&amp;page=GUID-855C475E-F9F9-460D-9475-B96DD982B587.html HPE C-states reference]


📚 Further reading
:: https://lwn.net/Kernel/Index/#Power_management-cpuidle
: {{The Linux Kernel/doc|PM Quality Of Service Interface|power/pm_qos_interface.html}}

==== Power and frequency ====


P-states, {{w|ACPI#Performance_state|performance states}}:
: P0 &amp;ndash; maximum power and frequency
: Pn &amp;ndash; less power and frequency
: ...


⚲ API
: Reliable measurement of actual CPU frequency
:: [https://manpages.debian.org/testing/linux-cpupower/turbostat.8.en.html turbostat] --quiet --show CPU,Bzy_MHz -n 1 --interval 0.1
::: Bzy_MHz &amp;ndash; average clock rate while the CPU was not idle (ie. in &quot;c0&quot; state).
: [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=intel_pstate intel_pstate=]
:: {{The Linux Kernel/doc|Kernel Command Line Options for intel_pstate|admin-guide/pm/intel_pstate.html#kernel-command-line-options-for-intel-pstate}}
: [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=cpufreq.default_governor cpufreq.default_governor=]
: P-states interfaces:
:: /sys/devices/system/cpu/cpufreq/
:: /sys/devices/system/cpu/cpu*/cpufreq/
::: scaling_cur_freq &amp;ndash; unreliable assumption on CPU frequency
:: /sys/devices/system/cpu/intel_pstate/
:: {{The Linux Kernel/include|linux/cpufreq.h}}
:: {{The Linux Kernel/include|linux/sched/cpufreq.h}} &amp;ndash; interface between cpufreq drivers and the scheduler


⚙️ Internals
: {{The Linux Kernel/source|drivers/cpufreq}} &amp;ndash; CPU frequency scaling drivers
:: {{The Linux Kernel/id|intel_pstate}}
:: {{The Linux Kernel/id|acpi_cpufreq_driver}}
: {{The Linux Kernel/source|kernel/sched/cpufreq_schedutil.c}} &amp;ndash; implementation of cpufreq.default_governor=schedutil
: {{The Linux Kernel/source|arch/x86/kernel/cpu/intel_epb.c}} &amp;ndash; Intel Performance and Energy Bias Hint support


📖 References
: {{The Linux Kernel/doc|CPU Performance Scaling|admin-guide/pm/cpufreq.html}}
: {{The Linux Kernel/doc|Device Frequency Scaling|driver-api/devfreq.html}}
: [https://www.kernel.org/doc/Documentation/cpu-freq/governors.txt CPUFreq Governor]
: {{The Linux Kernel/doc|CPUFreq - CPU frequency and voltage scaling|cpu-freq}}
: {{The Linux Kernel/doc|Intel Performance and Energy Bias Hint|admin-guide/pm/intel_epb.html}}
: {{The Linux Kernel/doc|intel_pstate CPU Performance Scaling Driver|admin-guide/pm/intel_pstate.html}}
:: {{The Linux Kernel/doc|General Information|admin-guide/pm/intel_pstate.html#general-information}} 
:: {{The Linux Kernel/doc|Operation Modes|admin-guide/pm/intel_pstate.html#operation-modes}} 
::: {{The Linux Kernel/doc|Active Mode|admin-guide/pm/intel_pstate.html#active-mode}}
&lt;!--
:::: {{The Linux Kernel/doc|Active Mode With HWP|admin-guide/pm/intel_pstate.html#active-mode-with-hwp}} 
::::: {{The Linux Kernel/doc|HWP + performance|admin-guide/pm/intel_pstate.html#hwp-performance}} 
::::: {{The Linux Kernel/doc|HWP + powersave|admin-guide/pm/intel_pstate.html#hwp-powersave}} 
:::: {{The Linux Kernel/doc|Active Mode Without HWP|admin-guide/pm/intel_pstate.html#active-mode-without-hwp}} 
::::: {{The Linux Kernel/doc|performance|admin-guide/pm/intel_pstate.html#performance}} 
::::: {{The Linux Kernel/doc|powersave|admin-guide/pm/intel_pstate.html#powersave}} 
--&gt;
::: {{The Linux Kernel/doc|Passive Mode|admin-guide/pm/intel_pstate.html#passive-mode}} 
:: {{The Linux Kernel/doc|Turbo P-states Support|admin-guide/pm/intel_pstate.html#turbo-p-states-support}} 
:: {{The Linux Kernel/doc|Processor Support|admin-guide/pm/intel_pstate.html#processor-support}} 
:: {{The Linux Kernel/doc|Support for Hybrid Processors|admin-guide/pm/intel_pstate.html#support-for-hybrid-processors}} 
::: {{The Linux Kernel/doc|Hybrid Processors with SMT|admin-guide/pm/intel_pstate.html#hybrid-processors-with-smt}} 
::: {{The Linux Kernel/doc|Capacity-Aware Scheduling Support|admin-guide/pm/intel_pstate.html#capacity-aware-scheduling-support}} 
::: {{The Linux Kernel/doc|Energy-Aware Scheduling Support|admin-guide/pm/intel_pstate.html#energy-aware-scheduling-support}} 
:: {{The Linux Kernel/doc|User Space Interface in sysfs|admin-guide/pm/intel_pstate.html#user-space-interface-in-sysfs}} 
::: {{The Linux Kernel/doc|Global Attributes|admin-guide/pm/intel_pstate.html#global-attributes}} 
::: {{The Linux Kernel/doc|Interpretation of Policy Attributes|admin-guide/pm/intel_pstate.html#interpretation-of-policy-attributes}} 
::: {{The Linux Kernel/doc|Coordination of P-State Limits|admin-guide/pm/intel_pstate.html#coordination-of-p-state-limits}} 
::: {{The Linux Kernel/doc|Energy vs Performance Hints|admin-guide/pm/intel_pstate.html#energy-vs-performance-hints}} 
:: {{The Linux Kernel/doc|intel_pstate vs acpi-cpufreq|admin-guide/pm/intel_pstate.html#intel-pstate-vs-acpi-cpufreq}} 
:: {{The Linux Kernel/doc|Kernel Command Line Options for intel_pstate|admin-guide/pm/intel_pstate.html#kernel-command-line-options-for-intel-pstate}} 
:: {{The Linux Kernel/doc|Diagnostics and Tuning|admin-guide/pm/intel_pstate.html#diagnostics-and-tuning}} 
::: {{The Linux Kernel/doc|Trace Events|admin-guide/pm/intel_pstate.html#trace-events}} 
::: {{The Linux Kernel/doc|ftrace|admin-guide/pm/intel_pstate.html#ftrace}} 
&lt;!-- end of intel_pstate.html --&gt;


📚 Further reading
: https://lwn.net/Kernel/Index/#Power_management-Frequency_scaling
: [https://wiki.archlinux.org/title/CPU_frequency_scaling CPU frequency scaling]
: {{The Linux Kernel/ltp|kernel/device-drivers|cpufreq}}
: [https://www.thinkwiki.org/wiki/How_to_use_cpufrequtils How to use cpufrequtils] 
:: [https://linux.die.net/man/1/cpufreq-info cpufreq-info]
:: [https://linux.die.net/man/1/cpufreq-set cpufreq-set]
: https://github.com/intel/power-optimization-library
: https://github.com/intel/kubernetes-power-manager

{{BookCat}}</text>
      <sha1>mlxs6sq7kka22gvgldl52b9tjricolx</sha1>
    </revision>
    <revision>
      <id>4656111</id>
      <parentid>4656108</parentid>
      <timestamp>2026-08-02T20:47:06Z</timestamp>
      <contributor>
        <username>Conan</username>
        <id>3188</id>
      </contributor>
      <minor />
      <comment>spc</comment>
      <origin>4656111</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="56956" sha1="2s449x79kv17y3fvzb05m941bm8wpq5" xml:space="preserve">&lt;noinclude&gt;{{DISPLAYTITLE:Interrupts and CPU}}&lt;/noinclude&gt;
== Interrupts ==
An {{w|interrupt}} is a signal to the processor emitted by hardware or software indicating an event that needs immediate attention.
An interrupt alerts the processor to a high-priority condition requiring the interruption of the current code the processor is executing.
The processor responds by suspending its current activities, saving its state, and executing a function called an ''interrupt handler'' (or an interrupt service routine, ISR) to deal with the event.
This interruption is temporary, and, after the interrupt handler finishes, the processor resumes normal activities.

There are two types of interrupts: hardware interrupts and software interrupts.
Hardware interrupts are used by devices to communicate that they require attention from the operating system.
For example, pressing a key on the keyboard or moving the mouse triggers hardware interrupts that cause the processor to read the keystroke or mouse position.
Unlike the software type, hardware interrupts are asynchronous and can occur in the middle of instruction execution, requiring additional care in programming.
The act of initiating a hardware interrupt is referred to as an ''interrupt request'' - IRQ ↪ {{w|Interrupt descriptor table|IDT}} ↪ {{The Linux Kernel/id|common_interrupt}} on x86.

A software interrupt is caused either by an exceptional condition in the processor itself, or a special instruction in the instruction set which causes an interrupt when it is executed.
The former is often called a ''{{w|Trap (computing)|trap}}'' (⚙️ {{The Linux Kernel/id|do_trap}}) or ''exception'' and is used for errors or events occurring during program execution that are exceptional enough that they cannot be handled within the program itself.
For example, if the processor's arithmetic logic unit is commanded to divide a number by zero, this impossible demand will cause a ''divide-by-zero exception'' (⚙️ {{The Linux Kernel/id|X86_TRAP_DE}}), perhaps causing the computer to abandon the calculation or display an error message.
Software interrupt instructions function similarly to subroutine calls and are used for a variety of purposes, such as to request services from low-level system software such as device drivers.
For example, computers often use software interrupt instructions to communicate with the disk controller to request data be read or written to the disk.

Each interrupt has its own interrupt handler.  The number of hardware interrupts is limited by the number of interrupt request (IRQ) lines to the processor, but there may be hundreds of different software interrupts.


⚲ API

: /proc/interrupts
: {{The Linux Kernel/man|1|irqtop}} &amp;ndash; utility to display kernel interrupt information
: [https://github.com/Irqbalance/irqbalance irqbalance] &amp;ndash; distribute hardware interrupts across processors on a multiprocessor system
: There are many ways to request ISR, two of them
: {{The Linux Kernel/id|devm_request_threaded_irq}} &amp;ndash; preferable, managed device with threaded ISR
: {{The Linux Kernel/id|devm_request_irq}} &amp;ndash; managed version
:: {{The Linux Kernel/id|request_irq}}
::: {{The Linux Kernel/id|request_threaded_irq}}
: {{The Linux Kernel/id|free_irq}}
: {{The Linux Kernel/include|linux/interrupt.h}} &amp;ndash; main interrupt support header
:: {{The Linux Kernel/id|irqaction}} &amp;ndash; contains handler functions 
: {{The Linux Kernel/include|linux/irq.h}}
:: {{The Linux Kernel/id|irq_data}}
: {{The Linux Kernel/include|linux/irqflags.h}}
:: {{The Linux Kernel/id|irqs_disabled}}
:: {{The Linux Kernel/id|local_irq_save}} ...
:: {{The Linux Kernel/id|local_irq_disable}} ...
: {{The Linux Kernel/include|linux/irqdesc.h}}
:: {{The Linux Kernel/id|irq_desc}}
: {{The Linux Kernel/include|linux/irqdomain.h}}
:: {{The Linux Kernel/id|irq_domain}} &amp;ndash; hardware interrupt number translation object
:: {{The Linux Kernel/id|irq_domain_get_irq_data}}
: {{The Linux Kernel/include|linux/msi.h}} &amp;ndash; {{w|Message Signaled Interrupts}}
:: {{The Linux Kernel/id|msi_desc}}
: Structure of structures:
:: {{The Linux Kernel/id|irq_desc}} is container of
::: {{The Linux Kernel/id|irq_data}}
:::: irq &amp;ndash; interrupt number
::: {{The Linux Kernel/id|irq_common_data}}
::: list of {{The Linux Kernel/id|irqaction}}


⚙️ Internals

: {{The Linux Kernel/source|kernel/irq/settings.h}} &amp;ndash; IRQ descriptor status flags
: {{The Linux Kernel/source|kernel/irq}} &amp;ndash; generic IRQ handling
:: {{The Linux Kernel/source|kernel/irq/internals.h}} &amp;ndash; IRQ subsystem internal functions
: ls /sys/kernel/debug/irq/domains/
:: {{The Linux Kernel/id|x86_vector_domain}}, {{The Linux Kernel/id|x86_vector_domain_ops}}
: {{The Linux Kernel/id|irq_chip}}
: {{The Linux Kernel/id|load_idt}} &amp;ndash; load Interrupt Descriptor Table
: {{The Linux Kernel/source|arch/x86/include/asm/idtentry.h}} &amp;ndash; interrupt entry/exit definitions
: {{The Linux Kernel/source|arch/x86/include/asm/hw_irq.h}} &amp;ndash; x86 hardware IRQ definitions
:: {{The Linux Kernel/id|irq_entries_start}} &amp;ndash; hardware IRQ entry stubs
: {{The Linux Kernel/source|arch/x86/kernel/irq.c}} &amp;ndash; x86 interrupt handling
:: {{The Linux Kernel/id|common_interrupt}} &amp;ndash; handles all normal device IRQs on x86
: {{The Linux Kernel/source|arch/x86/kernel/apic}} &amp;ndash; {{w|Advanced Programmable Interrupt Controller|APIC}}
:: {{The Linux Kernel/source|arch/x86/kernel/apic/apic.c}} &amp;ndash; local APIC core (timer, calibration, spurious interrupt)
:: {{The Linux Kernel/source|arch/x86/kernel/apic/io_apic.c}} &amp;ndash; {{w|IOAPIC|I/O APIC}}, routes device IRQs to CPUs
:: {{The Linux Kernel/source|arch/x86/kernel/apic/x2apic_cluster.c}} &amp;ndash; {{w|x2APIC}} (&gt;256 CPUs)
:: {{The Linux Kernel/source|arch/x86/kernel/apic/ipi.c}} &amp;ndash; {{w|Inter-processor interrupt|IPI}}, see [[#IPI|IPI]]
:: {{The Linux Kernel/source|arch/x86/kernel/apic/hw_nmi.c}} &amp;ndash; hardware NMI watchdog via APIC
:: {{The Linux Kernel/source|arch/x86/kernel/apic/vector.c}} &amp;ndash; IRQ vector allocation
:: {{The Linux Kernel/source|arch/x86/kernel/apic/msi.c}} &amp;ndash; {{w|Message Signaled Interrupts|MSI}} via APIC

📖 References
: {{The Linux Kernel/doc|IRQs|core-api/irq}}
:: {{The Linux Kernel/doc|The irq_domain interrupt number mapping library|core-api/irq/irq-domain.html}}
: {{The Linux Kernel/doc|Linux generic IRQ handling|core-api/genericirq.html}}
: {{The Linux Kernel/doc|Message Signaled Interrupts: The MSI Driver Guide|PCI/msi-howto.html}}
: {{The Linux Kernel/doc|Lock types and their rules|locking/locktypes.html}}
: {{The Linux Kernel/doc|Hard IRQ Context|kernel-hacking/locking.html#hard-irq-context}}
: [https://0xax.gitbooks.io/linux-insides/content/Interrupts/ Interrupts]


👁 Examples
: {{The Linux Kernel/id|dummy_irq_chip}} &amp;ndash; dummy interrupt chip implementation
: {{The Linux Kernel/source|lib/locking-selftest.c}} &amp;ndash; locking correctness self-tests


=== IRQ affinity ===

⚲ API
: /proc/irq/default_smp_affinity
: /proc/irq/*/smp_affinity and /proc/irq/*/smp_affinity_list


Common types and functions:
: struct {{The Linux Kernel/id|irq_affinity}} &amp;ndash; description for automatic irq affinity assignments, see {{The Linux Kernel/id|devm_platform_get_irqs_affinity}}
: struct {{The Linux Kernel/id|irq_affinity_desc}} &amp;ndash; interrupt affinity descriptor, see {{The Linux Kernel/id|irq_update_affinity_desc}}, {{The Linux Kernel/id|irq_create_affinity_masks}}
: {{The Linux Kernel/id|irq_set_affinity}}
: {{The Linux Kernel/id|irq_get_affinity_mask}} 
: {{The Linux Kernel/id|irq_can_set_affinity}}
: {{The Linux Kernel/id|irq_set_affinity_hint}} 
: {{The Linux Kernel/id|irqd_affinity_is_managed}} 
: {{The Linux Kernel/id|irq_data_get_affinity_mask}}
: {{The Linux Kernel/id|irq_data_get_effective_affinity_mask}} 
: {{The Linux Kernel/id|irq_data_update_effective_affinity}} 
: {{The Linux Kernel/id|irq_set_affinity_notifier}} 
: {{The Linux Kernel/id|irq_affinity_notify}} 
: {{The Linux Kernel/id|irq_chip_set_affinity_parent}} 
: {{The Linux Kernel/id|irq_set_vcpu_affinity}}


🛠️ Utilities
: [https://man.archlinux.org/man/extra/irqbalance/irqbalance.1.en irqbalance] – distributes hardware interrupts across CPUs


📖 References
: {{The Linux Kernel/doc|SMP IRQ affinity|core-api/irq/irq-affinity.html}}
: [https://wiki.linuxfoundation.org/realtime/documentation/howto/tools/cpu-partitioning/start#irq_affinity IRQ affinity, LF]
: [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=managed_irq managed_irq kernel parameter], [https://lore.kernel.org/lkml/?q=managed_irq @LKML]
: [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=irqaffinity= irqaffinity kernel parameter], [https://lore.kernel.org/lkml/?q=irqaffinity @LKML]


=== Non-maskable interrupts ===

⚲ API
: {{The Linux Kernel/include|linux/nmi.h}}
:: {{The Linux Kernel/id|in_nmi}}
:: {{The Linux Kernel/id|touch_nmi_watchdog}}
:: ...
: {{The Linux Kernel/include|trace/events/nmi.h}}
: {{The Linux Kernel/source|arch/x86/include/asm/nmi.h}} &amp;ndash; x86 NMI handler registration
:: {{The Linux Kernel/id|register_nmi_handler}}
:: {{The Linux Kernel/id|unregister_nmi_handler}}


⚙️ Internals
: {{The Linux Kernel/source|arch/x86/kernel/nmi.c}} &amp;ndash; x86 NMI handler
: {{The Linux Kernel/source|arch/x86/kernel/apic/hw_nmi.c}} &amp;ndash; hardware NMI watchdog via APIC
: {{The Linux Kernel/source|arch/x86/kernel/nmi_selftest.c}} &amp;ndash; NMI IPI self-tests


📖 References
: {{The Linux Kernel/doc|NMI Trace Events|trace/events-nmi.html}}


📚 Further reading
: [https://0xax.gitbooks.io/linux-insides/content/Interrupts/linux-interrupts-6.html Non-maskable interrupt handler] (NMI)


=== ... ===

📚 Further reading about interrupts
: IDT &amp;ndash; {{w|Interrupt descriptor table}}
: [https://www.felixcloutier.com/x86/lgdt:lidt LGDT/LIDT &amp;ndash; Load Global/Interrupt Descriptor Table Register] asm instruction

== Deferred works ==

=== Scheduler context ===

==== kthread work ====

This framework simplifies the use of kernel kthreads.
A {{The Linux Kernel/id|kthread_work}} item can be queued with {{The Linux Kernel/id|kthread_queue_work}} and flushed using {{The Linux Kernel/id|kthread_flush_work}}.
All queued kthread_work items are processed by a dedicated kernel thread executing the {{The Linux Kernel/id|kthread_worker_fn}} function.

⚲ API
: {{The Linux Kernel/id|kthread_work}} &amp;ndash; contains {{The Linux Kernel/id|kthread_work_func_t}} to execute
:: {{The Linux Kernel/id|kthread_init_work}}
:: {{The Linux Kernel/id|kthread_flush_work}}
: {{The Linux Kernel/id|kthread_worker}} &amp;ndash; links a kthread_work and a task
:: {{The Linux Kernel/id|kthread_run_worker}} &amp;ndash; creates and wakes a kthread worker
::: {{The Linux Kernel/id|kthread_create_worker}}
::: {{The Linux Kernel/id|kthread_flush_worker}}
:: {{The Linux Kernel/id|kthread_destroy_worker}}
: {{The Linux Kernel/id|kthread_queue_work}} &amp;ndash; queues a kthread_work on a kthread_worker


⚙️ Internals
: {{The Linux Kernel/id|__kthread_create_worker_on_node}}
: {{The Linux Kernel/id|kthread_worker_fn}} &amp;ndash; executes work's function


👁 Example usages
: {{The Linux Kernel/id|watchdog_kworker}}, {{The Linux Kernel/id|pwq_release_worker}}, {{The Linux Kernel/id|pump_messages}}

==== Threaded IRQ ====

⚲ API
{{The Linux Kernel/id|devm_request_threaded_irq}}, {{The Linux Kernel/id|request_threaded_irq}}
ISR should return IRQ_WAKE_THREAD to run thread function

⚙️ Internals
: {{The Linux Kernel/id|setup_irq_thread}}, {{The Linux Kernel/id|irq_thread}}
: {{The Linux Kernel/source|kernel/irq/manage.c}} &amp;ndash; IRQ request, free and affinity management

📖 References
: {{The Linux Kernel/doc|request_threaded_irq|core-api/genericirq.html#c.request_threaded_irq}}


==== Work and workqueue ====

Generic async execution with shared worker pool.

⚲ API
: {{The Linux Kernel/id|PF_WQ_WORKER}} &amp;ndash; workqueue worker process flag
: {{The Linux Kernel/include|linux/workqueue.h}}, {{The Linux Kernel/include|linux/workqueue_types.h}}
: {{The Linux Kernel/id|work_struct}}, {{The Linux Kernel/id|INIT_WORK}}
: {{The Linux Kernel/id|delayed_work}}, {{The Linux Kernel/id|INIT_DELAYED_WORK}}, {{The Linux Kernel/id|cancel_delayed_work_sync}}
: {{The Linux Kernel/id|workqueue_struct}}
:: {{The Linux Kernel/id|devm_alloc_workqueue}}
::: {{The Linux Kernel/id|alloc_workqueue}}
:: {{The Linux Kernel/id|destroy_workqueue}}
: {{The Linux Kernel/id|schedule_work}} &amp;ndash; queues work on the system workqueue ↯
:: {{The Linux Kernel/id|queue_work}} &amp;ndash; queues work on a workqueue
::: {{The Linux Kernel/id|queue_work_on}} &amp;ndash; on a specific CPU
: {{The Linux Kernel/id|show_all_workqueues}}
:: {{The Linux Kernel/id|show_one_workqueue}}
: {{The Linux Kernel/id|system_power_efficient_wq}} ...


👁 Example usage {{The Linux Kernel/source|samples/ftrace/sample-trace-array.c}}


⚙️ Internals
: {{The Linux Kernel/source|kernel/workqueue.c}} &amp;ndash; generic async execution with shared worker pool
:: {{The Linux Kernel/id|workqueue_init}}
::: {{The Linux Kernel/id|create_worker}}
:::: {{The Linux Kernel/id|worker_thread}}
::::: {{The Linux Kernel/id|process_one_work}}
:: {{The Linux Kernel/id|format_worker_id}} &amp;ndash; names kworker kthreads
:: {{The Linux Kernel/id|pool_workqueue}}
::: {{The Linux Kernel/id|worker_pool}}


📖 References
: {{The Linux Kernel/doc|Concurrency Managed Workqueue|core-api/workqueue.html}}
: [https://sysprog21.github.io/lkmpg/#work-queues LKMPG: Work queues]

=== Interrupt context ===

: {{The Linux Kernel/include|linux/irq_work.h}} &amp;ndash; run callbacks from hardirq or NMI context where normal work queues can't be used
:: {{The Linux Kernel/id|irq_work_queue}} &amp;ndash; enqueue work on the current CPU, triggers {{The Linux Kernel/id|IRQ_WORK_VECTOR}} IPI if needed
:: {{The Linux Kernel/id|irq_work_sync}} &amp;ndash; wait for completion
:: {{The Linux Kernel/source|kernel/irq_work.c}} &amp;ndash; irq_work implementation
:: 👁 {{The Linux Kernel/source|samples/trace_printk/trace-printk.c}}

==== Timers ====

⚠️ &quot;Timer&quot; in the kernel means different things: ''[[#softirq_timer|kernel timer]]'' – jiffies-based software callback, ''[[#High-resolution_timer|hrtimer]]'' – nanosecond software callback, ''[[The_Linux_Kernel/Multitasking#POSIX_Timers|POSIX timer]]'' – userspace API, ''[[The_Linux_Kernel/Debugging#Watchdogs|watchdog timer]]'' – hang detection, ''[[#Clock_infrastructure|local APIC timer]]'' – per-CPU hardware, drives the tick.

===== softirq timer =====

This timer is a softirq for periodical tasks with jiffies resolution

⚲ API
: {{The Linux Kernel/include|linux/timer.h}}
: {{The Linux Kernel/id|timer_list}}, {{The Linux Kernel/id|DEFINE_TIMER}}, {{The Linux Kernel/id|timer_setup}}
: {{The Linux Kernel/id|mod_timer}} &amp;mdash; sets expiration time in jiffies. 
: {{The Linux Kernel/id|del_timer}}


⚙️ Internals
: {{The Linux Kernel/source|kernel/time/timer.c}} &amp;ndash; kernel internal timers
:: {{The Linux Kernel/id|timer_bases}}


👁 Examples
: {{The Linux Kernel/id|input_enable_softrepeat}} and {{The Linux Kernel/id|input_start_autorepeat}}


📚 References
: {{The Linux Kernel/doc|Time and timer routines|driver-api/basics.html#time-and-timer-routines}}
:: {{The Linux Kernel/doc|mod_timer_pending ... |driver-api/basics.html#c.mod_timer_pending}}

===== High-resolution timer =====

⚲ API
: /proc/timer_list
: /proc/sys/kernel/timer_migration
: {{The Linux Kernel/include|linux/hrtimer_defs.h}}
: {{The Linux Kernel/include|linux/hrtimer.h}}
: {{The Linux Kernel/id|hrtimer}}, hrtimer.function &amp;mdash; callback
: {{The Linux Kernel/id|hrtimer_init}}
: {{The Linux Kernel/id|hrtimer_setup}}
: {{The Linux Kernel/id|hrtimer_start}} &amp;mdash; starts a timer with nanosecond resolution 
: {{The Linux Kernel/id|hrtimer_cancel}}


👁 Examples {{The Linux Kernel/id|alarm_init}}, {{The Linux Kernel/id|watchdog_enable}}


⚙️ Internals
: {{The Linux Kernel/id|CONFIG_HIGH_RES_TIMERS}}
: {{The Linux Kernel/source|kernel/time/tick-internal.h}} &amp;ndash; tick and timer internal definitions
:: {{The Linux Kernel/id|hrtimer_bases}}
: {{The Linux Kernel/source|kernel/time/hrtimer.c}} &amp;ndash; high-resolution timer implementation
: {{The Linux Kernel/source|kernel/time/itimer.c}} &amp;ndash; interval timers
: {{The Linux Kernel/source|kernel/time/timer_list.c}} &amp;ndash; /proc/timer_list debugfs


📚 HR timers references
: {{The Linux Kernel/doc|High-resolution timers|driver-api/basics.html#high-resolution-timers}}
: {{The Linux Kernel/doc|hrtimers - subsystem for high-resolution kernel timers|timers/hrtimers.html}}
: {{The Linux Kernel/doc|high resolution timers and dynamic ticks design notes|timers/highres.html}}

===== Tick and NO_HZ =====

The tick is the periodic timer interrupt that drives scheduling, timekeeping, and RCU.
The NO_HZ subsystem reduces or eliminates tick interrupts to save power and reduce latency.

⚲ API
: /sys/devices/system/cpu/nohz_full – active nohz_full CPUs
: [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=nohz_full= nohz_full=] boot parameter – list of CPUs to run tickless
: {{The Linux Kernel/include|linux/tick.h}} – tick control API
:: {{The Linux Kernel/id|tick_nohz_full_running}} – true if any CPU runs tickless

🪛 Compile-time configurations ({{The Linux Kernel/source|kernel/time/Kconfig}})
: {{The Linux Kernel/id|CONFIG_HZ_PERIODIC}} – constant-rate tick, always firing
: {{The Linux Kernel/id|CONFIG_NO_HZ_IDLE}} – stop tick when CPU is idle (default on most distros)
: {{The Linux Kernel/id|CONFIG_NO_HZ_FULL}} – stop tick even when running a single task, for RT and latency-sensitive workloads, see [[#CPU_isolation|CPU isolation]]

⚙️ Internals
: {{The Linux Kernel/source|kernel/time/tick-common.c}} – periodic tick setup
: {{The Linux Kernel/source|kernel/time/tick-oneshot.c}} – oneshot mode for hrtimers and NO_HZ
: {{The Linux Kernel/source|kernel/time/tick-sched.c}} – NO_HZ tick scheduling logic
: {{The Linux Kernel/source|kernel/time/tick-broadcast.c}} – broadcast tick for CPUs in deep idle where local timer stops ([[#Idle|C3+]])
: {{The Linux Kernel/source|kernel/time/timer_migration.c}} – migrate timers from idle to busy CPUs

📖 References
: {{The Linux Kernel/doc|NO_HZ: Reducing Scheduling-Clock Ticks|timers/no_hz.html}}
: [https://wiki.linuxfoundation.org/realtime/documentation/howto/tools/ticklesskernel Tickless kernel, RT wiki]
: {{The Linux Kernel/doc|high resolution timers and dynamic ticks design notes|timers/highres.html}}

===== Clock infrastructure =====

⚠️ Not to confuse: ''[[The_Linux_Kernel/System#Hardware_Device_Drivers|clk framework]]'' – SoC {{w|Clock signal|clock}} tree management in drivers/clk.

Clocksources read current time (passive counters).
Clock event devices fire interrupts at a programmed time (active).
Together they are the foundation for timekeeping, timers, tick, and NO_HZ.


⚲ Clocksources – &quot;what time is it?&quot;
: /sys/devices/system/clocksource/clocksource0/current_clocksource
: /sys/devices/system/clocksource/clocksource0/available_clocksource
:: {{w|Time Stamp Counter|TSC}} – fastest, per-CPU, x86
:: {{w|High Precision Event Timer|HPET}} – system-wide, MMIO
:: ACPI PM timer – never stops in any C-state, slow
: {{The Linux Kernel/include|linux/clocksource.h}} – {{The Linux Kernel/id|clocksource}}, {{The Linux Kernel/id|clocksource_register_hz}}


⚲ Clock event devices – &quot;wake me at time X&quot;
: {{The Linux Kernel/include|linux/clockchips.h}} – {{The Linux Kernel/id|clock_event_device}}, {{The Linux Kernel/id|clockevents_config_and_register}}
: Local {{w|Advanced Programmable Interrupt Controller|APIC}} timer – per-CPU, fastest, stops in [[#Idle|C3+]], {{The Linux Kernel/id|local_apic_timer_interrupt}}
: {{w|High Precision Event Timer|HPET}} – system-wide, used as broadcast fallback
&lt;!-- PIT (i8254) – legacy, stopped at boot on modern hardware --&gt;

⚙️ Internals
: {{The Linux Kernel/source|kernel/time/clocksource.c}} – clocksource selection and watchdog
: {{The Linux Kernel/source|kernel/time/clockevents.c}} – clock event device framework
: {{The Linux Kernel/source|kernel/time/jiffies.c}} – jiffies clocksource (fallback)

===== ... =====

📖 Timers references
: {{The Linux Kernel/doc|Timers|timers}}
: [https://lwn.net/Articles/913568/ Better CPU selection for timer expiration]

==== Tasklet ====

tasklet is a softirq, for time critical operations

⚲ API is deprecated in favor of threaded IRQs: {{The Linux Kernel/id|devm_request_threaded_irq}}
: {{The Linux Kernel/id|tasklet_struct}}, {{The Linux Kernel/id|tasklet_init}}, {{The Linux Kernel/id|tasklet_schedule}} 


⚙️ Internals: {{The Linux Kernel/id|tasklet_action_common}} HI_SOFTIRQ, TASKLET_SOFTIRQ


==== Softirq ====

softirq is internal system facility and should not be used directly.
Use tasklet or threaded IRQs

⚲ API
: {{The Linux Kernel/include|linux/interrupt.h}}
: cat /proc/softirqs
: {{The Linux Kernel/id|open_softirq}} registers {{The Linux Kernel/id|softirq_action}}
: {{The Linux Kernel/id|raise_softirq}}
: {{The Linux Kernel/id|tasklet_schedule}}
:: {{The Linux Kernel/id|__tasklet_schedule}}


⚙️ Internals
: {{The Linux Kernel/source|kernel/softirq.c}} &amp;ndash; software interrupt handling
:: {{The Linux Kernel/id|__do_softirq}} &amp;ndash; main softirq processing loop


📖 References
: [https://0xax.gitbooks.io/linux-insides/content/Interrupts/linux-interrupts-9.html Introduction to deferred interrupts (Softirq, Tasklets and Workqueues)]
: [https://0xax.gitbooks.io/linux-insides/content/Timers/ Timers and time management]
: [https://linux-kernel-labs.github.io/refs/heads/master/labs/deferred_work.html Deferred work, linux-kernel-labs]
: [https://www.oreilly.com/library/view/linux-device-drivers/0596005903/ch07.html Chapter 7. Time, Delays, and Deferred Work]

==CPU specific==


🖱️ GUI
: [https://manpages.ubuntu.com/manpages/kinetic/en/man8/tuna.8.html tuna] &amp;ndash; program for tuning running processes


⚲ API
: cat /proc/cpuinfo
: /sys/devices/system/cpu/
: /sys/devices/system/node/
: /sys/cpu/
: /sys/fs/cgroup/cpu/
: grep -i cpu /proc/self/status
: [https://manpages.ubuntu.com/manpages/jammy/man1/rdmsr.1.html rdmsr] &amp;ndash; tool for reading CPU machine specific registers (MSR)
: {{The Linux Kernel/man|1|lscpu}} &amp;ndash; display information about the CPU architecture

: {{The Linux Kernel/include|linux/arch_topology.h}} &amp;ndash; arch specific cpu topology information 
: {{The Linux Kernel/include|linux/cpu.h}} &amp;ndash; generic cpu definition 
: {{The Linux Kernel/include|linux/cpu_cooling.h}} 
: {{The Linux Kernel/include|linux/cpu_pm.h}} 
: {{The Linux Kernel/include|linux/cpufeature.h}}
: {{The Linux Kernel/source|arch/x86/include/asm/cpufeature.h}} &amp;ndash; x86 CPU feature detection
: {{The Linux Kernel/include|linux/peci-cpu.h}} 
: {{The Linux Kernel/include|linux/sched/cputime.h}} &amp;ndash; cputime accounting APIs
: {{The Linux Kernel/include|linux/clk.h}} &amp;ndash; interfaces for managing hardware clocks in device drivers


⚙️ Internals

: {{The Linux Kernel/source|drivers/base/cpu.c}} &amp;ndash; CPU driver model subsystem
:: {{The Linux Kernel/id|cpu_dev_init}}


=== Cache ===

: {{The Linux Kernel/include|linux/cacheflush.h}}
:: {{The Linux Kernel/source|arch/x86/include/asm/cacheflush.h}}: {{The Linux Kernel/id|clflush_cache_range}}
: {{The Linux Kernel/include|linux/cache.h}} &amp;ndash; cache line alignment macros
:: {{The Linux Kernel/id|____cacheline_aligned}} &amp;ndash; align to cache line boundary to avoid false sharing
:: {{The Linux Kernel/id|__cacheline_aligned}} &amp;ndash; same, plus place in .data..cacheline_aligned section
:: {{The Linux Kernel/id|____cacheline_aligned_in_smp}} &amp;ndash; same, but no-op on uniprocessor builds
:: {{The Linux Kernel/id|__read_mostly}} &amp;ndash; place in a cache-friendly section for rarely written data
:: {{The Linux Kernel/id|__ro_after_init}} &amp;ndash; writable during init, read-only after boot (security hardening)
:: {{The Linux Kernel/id|DEFINE_PER_CPU_CACHE_HOT}} &amp;ndash; per-CPU variable in .data..hot section, used for {{The Linux Kernel/id|current_task}}, {{The Linux Kernel/id|__preempt_count}}
:: {{The Linux Kernel/id|L1_CACHE_BYTES}}, {{The Linux Kernel/id|SMP_CACHE_BYTES}} &amp;ndash; 64 bytes typically
:: {{The Linux Kernel/source|arch/x86/include/asm/cache.h}} &amp;ndash; x86 cache line size definitions

🔨 [https://manpages.ubuntu.com/manpages/resolute/man1/stress-ng.1.html#:~:text=%2D%2Dcache stress-ng --cache]

⚙️ Internals

: {{The Linux Kernel/source|arch/x86/mm/pat/set_memory.c}} &amp;ndash; page attribute table memory type control
: {{The Linux Kernel/source|arch/x86/kernel/cpu/mtrr/}} &amp;ndash; memory type range register driver

📚 Further reading
: MTRR &amp;ndash; {{w|Memory type range register}}
: {{w|CPU cache}}

=== {{w|Symmetric_multiprocessing|SMP}} ===

This chapter is about multiprocessing and {{w|Multi-core processor|multi-core}} aspects of Linux kernel.

Key concepts and features of Linux SMP include:
* Symmetry: In an SMP system, all processors are considered the same without hardware hierarchy in contradiction to use of {{w|coprocessor}}s.
* Load balancing: The Linux kernel employs load balancing mechanisms to distribute tasks evenly among available CPU cores. This prevents any one core from becoming overwhelmed while others remain underutilized.
* Parallelism: SMP enables parallel processing, where multiple threads or processes can execute simultaneously on different CPU cores. This can significantly improve the execution speed of applications that are designed to take advantage of multiple threads.
* Thread scheduling: The Linux kernel scheduler is responsible for determining which threads or processes run on which CPU cores and for how long. It aims to optimize performance by minimizing contention and maximizing CPU utilization.
* Shared memory: In an SMP system, all CPU cores typically share the same physical memory space. This allows processes and threads running on different cores to communicate and share data more efficiently.
* NUMA &amp;ndash; {{w|Non-Uniform Memory Access}}: In larger SMP systems, memory access times might not be uniform due to the physical arrangement of memory banks and processors. Linux has mechanisms to handle NUMA architectures efficiently, allowing processes to be scheduled on CPUs closer to their associated memory.
* Cache coherency: SMP systems require mechanisms to ensure that all CPU cores have consistent views of memory. Cache coherency protocols ensure that changes made to shared memory locations are correctly propagated to all cores.
* Scalability: SMP systems can be scaled up to include more CPU cores, enhancing the overall computing power of the system. However, as the number of cores increases, challenges related to memory access, contention, and communication between cores may arise.
* Kernel and user space: Linux applications running in user space can take advantage of SMP without needing to be aware of the underlying hardware details. The kernel handles the management of CPU cores and resource allocation.


⚲ API
: &lt;code&gt;ps -PLe&lt;/code&gt; &amp;ndash; lists threads with processor that the thread last executed on (the third column PSR).
: {{The Linux Kernel/man|2|getcpu}} &amp;ndash; determine CPU and NUMA node on which the calling thread is running
: {{The Linux Kernel/man|8|chcpu}} &amp;ndash; configure CPUs
: {{The Linux Kernel/man|3|CPU_SET}} &amp;ndash; macros for manipulating CPU sets
: {{The Linux Kernel/include|linux/smp.h}}
:: The most commonly used functions:
:: {{The Linux Kernel/id|crash_smp_send_stop}} – halts all CPUs except the calling one in a crash context
:: {{The Linux Kernel/id|get_cpu}} – disables preemption and returns the current processor ID
:: {{The Linux Kernel/id|panic_smp_self_stop}} – stops the local CPU during a panic while ensuring others halt
:: {{The Linux Kernel/id|put_cpu}} – re-enables preemption after a previous get_cpu call
:: {{The Linux Kernel/id|raw_smp_processor_id}} – returns the current CPU ID without preemption safety
:: {{The Linux Kernel/id|setup_max_cpus}} – sets up the maximum number of CPUs to be brought online
:: {{The Linux Kernel/id|smp_init}} – initializes core SMP structures and state during boot
:: {{The Linux Kernel/id|smp_prepare_boot_cpu}} – prepares the boot CPU during early SMP initialization
:: {{The Linux Kernel/id|smp_prepare_cpus}} – prepares all CPUs for booting before secondary CPUs are started
:: {{The Linux Kernel/id|smp_processor_id}} – returns the ID of the current CPU with preemption checks
:: {{The Linux Kernel/id|smp_send_stop}} – stops all other CPUs in response to critical events
:: {{The Linux Kernel/id|wake_up_all_idle_cpus}} – wakes all idle CPUs to ensure prompt task execution
: {{The Linux Kernel/include|linux/cpu.h}}
: {{The Linux Kernel/include|linux/group_cpus.h}}: {{The Linux Kernel/id|group_cpus_evenly}} &amp;ndash; groups all CPUs evenly per NUMA/CPU locality
: {{The Linux Kernel/include|asm-generic/percpu.h}}
: {{The Linux Kernel/include|linux/percpu-defs.h}} &amp;ndash; basic definitions for percpu areas
:: {{The Linux Kernel/id|this_cpu_ptr}}
: {{The Linux Kernel/include|linux/percpu.h}} 
: {{The Linux Kernel/include|linux/percpu-refcount.h}} 
: {{The Linux Kernel/include|linux/percpu-rwsem.h}}
: {{The Linux Kernel/include|linux/preempt.h}}
:: {{The Linux Kernel/id|migrate_disable}}, {{The Linux Kernel/id|migrate_enable}}
: /sys/bus/cpu
: [[#per_CPU_local_lock|per CPU local_lock]]
: {{The Linux Kernel/include|linux/topology.h}} &amp;ndash; {{The Linux Kernel/id|cpu_to_node}}, {{The Linux Kernel/id|numa_node_id}}
: {{The Linux Kernel/source|arch/x86/include/asm/topology.h}} &amp;ndash; x86 NUMA and CPU topology
: See also [[../../Memory#NUMA|NUMA memory section]]


⚙️ Internals
: {{The Linux Kernel/id|boot_cpu_init}} activates the first CPU
: {{The Linux Kernel/id|smp_prepare_cpus}} initializes rest CPUs during boot
: {{The Linux Kernel/id|cpu_number}}
: {{The Linux Kernel/id|CONFIG_SMP}}
:: {{The Linux Kernel/id|CONFIG_NUMA}}
: {{The Linux Kernel/include|trace/events/percpu.h}}
: {{The Linux Kernel/file|drivers/base/cpu.c}} &amp;ndash; CPU driver model subsystem support
: {{The Linux Kernel/file|kernel/cpu.c}} &amp;ndash; CPU hotplug state machine
: smpboot
:: {{The Linux Kernel/include|linux/smpboot.h}}
:: {{The Linux Kernel/source|kernel/smpboot.c}} &amp;ndash; common SMP CPU bringup/teardown
:: {{The Linux Kernel/source|arch/x86/kernel/smpboot.c}} &amp;ndash; x86 SMP booting
: {{The Linux Kernel/source|lib/group_cpus.c}} &amp;ndash; distribute CPUs evenly across groups


🛠️ Utilities
: [https://man.archlinux.org/man/extra/irqbalance/irqbalance.1.en irqbalance] – distributes hardware interrupts across CPUs
: {{The Linux Kernel/man|8|numactl}} &amp;ndash; controls NUMA policy for processes or shared memory


📖 References
: {{The Linux Kernel/doc|Per-CPU Data|kernel-hacking/locking.html#per-cpu-data}}
: {{The Linux Kernel/doc|How CPU topology info is exported via sysfs|admin-guide/cputopology.html}}


📚 Further reading
: [https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/monitoring_and_managing_system_status_and_performance/customizing-tuned-profiles_monitoring-and-managing-system-status-and-performance#functionalities-of-the-scheduler-tuned-plug-in_customizing-tuned-profiles Functionalities of the scheduler TuneD plugin]
: [https://man.archlinux.org/man/tuned-adm.8 tuned-adm] &amp;ndash; command line tool for switching between different tuning profiles


==== {{w|Inter-processor interrupt|IPI}} ====

An inter-processor interrupt is a signal sent from one CPU to another to request an action such as rescheduling, TLB flush, or function execution.

⚲ API
: {{The Linux Kernel/id|smp_send_reschedule}} &amp;ndash; sends a reschedule IPI to a target CPU
: {{The Linux Kernel/id|smp_call_function}} &amp;ndash; invokes a function on all other CPUs via IPI
:: {{The Linux Kernel/id|smp_call_function_many}} &amp;ndash; on a specified set of CPUs
: {{The Linux Kernel/id|smp_call_function_single}} &amp;ndash; on a single target CPU
:: {{The Linux Kernel/id|smp_call_function_single_async}} &amp;ndash; asynchronous variant
: {{The Linux Kernel/id|smp_call_on_cpu}} &amp;ndash; execute on a specific CPU and wait for result
: {{The Linux Kernel/id|on_each_cpu}} &amp;ndash; run a function on all CPUs
:: {{The Linux Kernel/id|on_each_cpu_mask}} &amp;ndash; on a specified set of CPUs
:: {{The Linux Kernel/id|on_each_cpu_cond_mask}} &amp;ndash; conditionally on selected CPUs
: {{The Linux Kernel/id|smp_call_func_t}} &amp;ndash; callback typedef

⚙️ Internals
: {{The Linux Kernel/include|trace/events/ipi.h}}
: {{The Linux Kernel/file|kernel/irq/ipi.c}} &amp;ndash; generic IPI helpers
:: {{The Linux Kernel/id|ipi_send_single}}, {{The Linux Kernel/id|ipi_send_mask}}
: {{The Linux Kernel/source|arch/x86/kernel/apic/ipi.c}} &amp;ndash; x86 IPI via APIC
: {{The Linux Kernel/source|arch/x86/include/asm/irq_vectors.h}} &amp;ndash; x86 IPI vector types:
:: {{The Linux Kernel/id|RESCHEDULE_VECTOR}} &amp;ndash; used by {{The Linux Kernel/id|smp_send_reschedule}}
:: {{The Linux Kernel/id|CALL_FUNCTION_VECTOR}} &amp;ndash; used by {{The Linux Kernel/id|smp_call_function_many}}
:: {{The Linux Kernel/id|CALL_FUNCTION_SINGLE_VECTOR}} &amp;ndash; used by {{The Linux Kernel/id|smp_call_function_single}}
:: {{The Linux Kernel/id|IRQ_WORK_VECTOR}} &amp;ndash; used by {{The Linux Kernel/id|irq_work_queue}}, see [[#Interrupt_context|Interrupt context]]
:: {{The Linux Kernel/id|NMI_VECTOR}} &amp;ndash; used by watchdog, {{The Linux Kernel/id|crash_smp_send_stop}}

==== CPU affinity ====

Affinity refers to assigning a process or thread to specific CPU cores.
This helps control which CPUs execute tasks, potentially improving performance by reducing data movement between cores.
It can be managed using system calls or commands.
Affinity can be represented as CPU bitmask: {{The Linux Kernel/id|cpumask_t}} or CPU affinity list: {{The Linux Kernel/id|cpulist_parse}}.


⚲ API
: {{The Linux Kernel/man|1|taskset}} &amp;ndash; set or retrieve a process's CPU affinity
: grep Cpus_allowed /proc/self/status
: {{The Linux Kernel/man|2|sched_setaffinity}} {{The Linux Kernel/man|2|sched_getaffinity}} &amp;ndash; set and get a thread's CPU affinity mask
:: ↪ {{The Linux Kernel/id|sched_setaffinity}}
: {{The Linux Kernel/id|set_cpus_allowed_ptr}} &amp;ndash; common kernel function to change a task's affinity mask
: {{The Linux Kernel/include|linux/cpu_rmap.h}} &amp;ndash; CPU affinity reverse-map support
: {{The Linux Kernel/include|linux/cpumask_types.h}}
:: struct cpumask, {{The Linux Kernel/id|cpumask_t}} &amp;ndash; CPUs bitmap, can be very big
:: {{The Linux Kernel/id|cpumask_var_t}} &amp;ndash; type for local cpumask variable, see {{The Linux Kernel/id|alloc_cpumask_var}}, {{The Linux Kernel/id|free_cpumask_var}}.
: {{The Linux Kernel/include|linux/cpumask.h}} &amp;ndash; Cpumasks provide a bitmap suitable for representing the set of CPU's in a system, one bit position per CPU number
:: {{The Linux Kernel/id|for_each_possible_cpu}}
:: {{The Linux Kernel/id|num_online_cpus}}
:: {{The Linux Kernel/id|cpumask_set_cpu}}
:: {{The Linux Kernel/id|cpumask_test_cpu}}
:: {{The Linux Kernel/id|for_each_cpu}}


⚙️ Internals
: {{The Linux Kernel/id|cpus_mask}} &amp;ndash; affinity of {{The Linux Kernel/id|task_struct}}
: {{The Linux Kernel/id|cpus_allowed}} &amp;ndash; affinity of {{The Linux Kernel/id|cpuset}}


📚 Further reading
: {{w|Processor affinity}}
: {{w|Affinity mask}}

==== CPU hotplug ====

CPU hotplugging in Linux refers to the ability to dynamically add or remove CPUs from the system without needing a reboot.
This feature is crucial in environments requiring high availability and resource flexibility, such as data centers, virtualized systems, and systems that use power management aggressively.


🗝️ Acronyms
: BP &amp;ndash; Bootstrap Processor
: AP &amp;ndash; Application Processor


⚲ API
: /sys/devices/system/cpu/cpu*/online
: /sys/devices/system/cpu/cpu*/hotplug/
: {{The Linux Kernel/include|linux/cpu.h}}
:: {{The Linux Kernel/id|add_cpu}} ...
: {{The Linux Kernel/include|linux/cpuhotplug.h}}
:: {{The Linux Kernel/id|cpuhp_state}} &amp;ndash; CPU hotplug states 
:: {{The Linux Kernel/id|cpuhp_setup_state}} ... &amp;ndash; setups hotplug state callbacks
::: {{The Linux Kernel/id|cpuhp_setup_state_multi}}
::: {{The Linux Kernel/id|cpuhp_setup_state_nocalls}}
: {{The Linux Kernel/include|linux/cpuhplock.h}} &amp;ndash; CPU hotplug locking
:: {{The Linux Kernel/id|cpus_read_lock}} ...
:: {{The Linux Kernel/id|remove_cpu}} ...


⚙️ Internals
: {{The Linux Kernel/source|kernel/cpu.c}} &amp;ndash; CPU hotplug state machine
:: {{The Linux Kernel/id|cpuhp_state}} &amp;ndash; from CPUHP_OFFLINE to CPUHP_AP_ACTIVE and CPUHP_ONLINE.
:: {{The Linux Kernel/id|cpuhp_hp_states}}
:: {{The Linux Kernel/id|boot_cpu_hotplug_init}}
:: {{The Linux Kernel/id|cpuhp_threads_init}}
:: ... {{The Linux Kernel/id|cpuhp_invoke_callback_range}} ...
: {{The Linux Kernel/source|kernel/irq/cpuhotplug.c}} &amp;ndash; IRQ migration on CPU hotunplug
: {{The Linux Kernel/source|drivers/base/cpu.c}} &amp;ndash; CPU subsystem support
:: {{The Linux Kernel/id|cpu_dev_init}}
::: ... {{The Linux Kernel/id|cpu_subsys_online}}
: {{The Linux Kernel/include|trace/events/cpuhp.h}}
: {{The Linux Kernel/include|linux/cpuhplock.h}}


👁️ Examples
: {{The Linux Kernel/id|torture_onoff}}
: {{The Linux Kernel/source|tools/testing/selftests/sched_ext/hotplug.c}} &amp;ndash; sched_ext CPU hotplug test


📖 References
: {{The Linux Kernel/doc|CPU hotplug in the Kernel|core-api/cpu_hotplug.html}}
:: {{The Linux Kernel/doc|Introduction|core-api/cpu_hotplug.html#introduction}} 
:: {{The Linux Kernel/doc|Command Line Switches|core-api/cpu_hotplug.html#command-line-switches}} 
:: {{The Linux Kernel/doc|CPU maps|core-api/cpu_hotplug.html#cpu-maps}} 
:: {{The Linux Kernel/doc|Using CPU hotplug|core-api/cpu_hotplug.html#using-cpu-hotplug}} 
:: {{The Linux Kernel/doc|The CPU hotplug coordination|core-api/cpu_hotplug.html#the-cpu-hotplug-coordination}} 
:: {{The Linux Kernel/doc|The CPU hotplug API|core-api/cpu_hotplug.html#the-cpu-hotplug-api}} 
::: {{The Linux Kernel/doc|CPU hotplug state machine|core-api/cpu_hotplug.html#cpu-hotplug-state-machine}} 
::: {{The Linux Kernel/doc|CPU online/offline operations|core-api/cpu_hotplug.html#cpu-online-offline-operations}} 
::: {{The Linux Kernel/doc|Allocating a state|core-api/cpu_hotplug.html#allocating-a-state}} 
::: {{The Linux Kernel/doc|Setup of a CPU hotplug state|core-api/cpu_hotplug.html#setup-of-a-cpu-hotplug-state}} 
::: {{The Linux Kernel/doc|Removal of a CPU hotplug state|core-api/cpu_hotplug.html#removal-of-a-cpu-hotplug-state}} 
::: {{The Linux Kernel/doc|Multi-Instance state instance management|core-api/cpu_hotplug.html#multi-instance-state-instance-management}} 
::: {{The Linux Kernel/doc|Examples|core-api/cpu_hotplug.html#examples}} 
:: {{The Linux Kernel/doc|Testing of hotplug states|core-api/cpu_hotplug.html#testing-of-hotplug-states}} 
:: {{The Linux Kernel/doc|Architecture’s requirements|core-api/cpu_hotplug.html#architecture-s-requirements}} 
:: {{The Linux Kernel/doc|User Space Notification|core-api/cpu_hotplug.html#user-space-notification}} 
:: {{The Linux Kernel/doc|Kernel Inline Documentations Reference|core-api/cpu_hotplug.html#kernel-inline-documentations-reference}}
 

🔨 [https://manpages.ubuntu.com/manpages/resolute/man1/stress-ng.1.html#:~:text=%2D%2Dcpu%2Donline stress-ng --cpu-online]

📚 Further reading
: {{The Linux Kernel/id|CONFIG_CPU_HOTPLUG_STATE_CONTROL}} &amp;ndash; enables the ability to write incremental steps between &quot;offline&quot; and &quot;online&quot; states to the CPU's sysfs target file, allowing for more granular control of state transitions.
:: {{The Linux Kernel/id|target_store}}: {{The Linux Kernel/id|cpu_up}}/{{The Linux Kernel/id|cpu_down}}
: [https://lore.kernel.org/lkml/?q=cpuhotplug+OR+cpuhp cpuhotplug, cpuhp @LKML]

==== CPU isolation ====

CPU isolation ensures that specific tasks run on dedicated CPUs, reducing contention and latency.

'''Housekeeping''' CPUs refer to the CPUs that are reserved for various '''system''' tasks. See {{The Linux Kernel/id|hk_type}}.

'''Isolated''' CPUs are dedicated to '''real-time''' applications, such as DPDK.

⚲ API
: /sys/devices/system/cpu/isolated
: /sys/devices/system/cpu/nohz_full
: [https://docs.kernel.org/admin-guide/cgroup-v2.html#:~:text=cpuset.cpus.isolated /sys/fs/cgroup/cpuset.cpus.isolated]
: [https://docs.kernel.org/admin-guide/cgroup-v2.html#:~:text=Partition%20root%20without%20load%20balancing /sys/fs/cgroup/.../cpuset.cpus.partition]
: {{The Linux Kernel/include|linux/sched/isolation.h}}
:: {{The Linux Kernel/id|hk_type}} &amp;ndash; housekeeping type
:: {{The Linux Kernel/id|housekeeping_cpumask}} &amp;ndash; returns CPUs available for housekeeping of a given type
:: {{The Linux Kernel/id|cpu_is_isolated}}
: {{The Linux Kernel/include|linux/cpuset.h}} &amp;ndash; cpuset interface
: {{The Linux Kernel/man|7|cpuset}} &amp;ndash; confine processes to processor and memory node subsets


⚙️ Internals
: {{The Linux Kernel/id|CONFIG_CPU_ISOLATION}}
:: {{The Linux Kernel/source|kernel/sched/isolation.c}} &amp;ndash; housekeeping CPU management
::: {{The Linux Kernel/id|housekeeping_init}}, {{The Linux Kernel/id|housekeeping_update}}
: {{The Linux Kernel/id|CONFIG_CPUSETS}}
:: {{The Linux Kernel/source|kernel/cgroup/cpuset.c}} &amp;ndash; cpuset cgroup controller
::: {{The Linux Kernel/id|cpuset_init}}
::: {{The Linux Kernel/id|cpuset_init_smp}}
::: {{The Linux Kernel/id|isolated_cpus}}
::: {{The Linux Kernel/id|partition_xcpus_add}}, {{The Linux Kernel/id|partition_xcpus_del}}


📖 References
: {{The Linux Kernel/doc|CPU lists in command-line parameters|admin-guide/kernel-parameters.html#cpu-lists}}
:: [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=nohz_full= '''nohz_full'''] clears housekeeping.{{The Linux Kernel/id|cpumasks}} for tick, wq, timer, rcu, misc, and kthread in {{The Linux Kernel/id|housekeeping_nohz_full_setup}}
:: [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=isolcpus '''isolcpus'''] clears housekeeping.{{The Linux Kernel/id|cpumasks}} for [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=domain%20isolation domain] (by default), [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=nohz nohz], and [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=managed_irq managed_irq] in {{The Linux Kernel/id|housekeeping_isolcpus_setup}}
: {{The Linux Kernel/doc|Housekeeping|core-api/housekeeping.html}}
: {{The Linux Kernel/doc|NO_HZ: Reducing Scheduling-Clock Ticks|timers/no_hz.html}}
: {{The Linux Kernel/doc|CPUSETS of cgroup v2|admin-guide/cgroup-v2.html#cpuset}}
: {{The Linux Kernel/doc|CPUSETS of cgroup v1|admin-guide/cgroup-v1/cpusets.html}}


📚 Further reading
: [https://www.youtube.com/watch?v=1lomUhSS82s CPU Isolation state of the art, LPC'23]
: [https://lpc.events/event/19/contributions/2219/ CPU Isolation and IPI interference, LPC'25]
: [https://www.suse.com/c/cpu-isolation-introduction-part-1/ CPU Isolation]
: [https://lore.kernel.org/lkml/?q=isolcpus isolcpus @LKML]
: [https://lore.kernel.org/lkml/?q=housekeeping housekeeping @LKML]
: [https://kubernetes.io/docs/tasks/administer-cluster/reserve-compute-resources/#explicitly-reserved-cpu-list Explicitly Reserved CPU List, Kubernetes Documentation]
: [https://wiki.linuxfoundation.org/realtime/documentation/howto/tools/cpu-partitioning/start CPU Partitioning]
: {{The Linux Kernel/doc|Scheduler Domains|scheduler/sched-domains.html}} &amp;ndash; the Scheduler balances CPUs (scheduling groups) within a sched domain
: [https://lore.kernel.org/lkml/?q=nohz_full nohz_full @LKML]

💾 Historical since v7.0
: {{The Linux Kernel/id|cpuset_cpu_is_isolated}} &amp;ndash; removed, use {{The Linux Kernel/id|cpu_is_isolated}} instead

=== Runtime code patching ===

The kernel patches its own machine code at boot or runtime to optimize hot paths.
Static keys patch a {{w|NOP_(code)|NOP}} to a jump (or vice versa); static calls patch indirect calls to direct calls; alternatives replace instructions based on CPU features.

⚲ API
: {{The Linux Kernel/include|linux/jump_label.h}} &amp;ndash; static keys
:: {{The Linux Kernel/id|DEFINE_STATIC_KEY_FALSE}} &amp;ndash; define a key, initially false
:: {{The Linux Kernel/id|static_branch_unlikely}} &amp;ndash; zero-cost branch check (NOP when key is false)
:: {{The Linux Kernel/id|static_branch_enable}} &amp;ndash; patch all sites to take the branch (expensive, rare use)
: {{The Linux Kernel/include|linux/static_call.h}} &amp;ndash; static calls
:: {{The Linux Kernel/id|DEFINE_STATIC_CALL}} &amp;ndash; define a call site with initial target function
:: {{The Linux Kernel/id|static_call}} &amp;ndash; invoke the patched direct call
:: {{The Linux Kernel/id|static_call_update}} &amp;ndash; change target function, patch all sites
: {{The Linux Kernel/source|arch/x86/include/asm/alternative.h}} &amp;ndash; alternatives
:: {{The Linux Kernel/id|ALTERNATIVE}} &amp;ndash; replace instructions at boot based on CPU features
:: {{The Linux Kernel/source|arch/x86/include/asm/cpufeatures.h}} &amp;ndash; X86_FEATURE_* flags


⚙️ Internals
: {{The Linux Kernel/id|CONFIG_JUMP_LABEL}}
:: {{The Linux Kernel/source|kernel/jump_label.c}} &amp;ndash; static key patching core
:: {{The Linux Kernel/source|arch/x86/kernel/jump_label.c}} &amp;ndash; x86 static key patching
: {{The Linux Kernel/id|CONFIG_HAVE_STATIC_CALL}}
:: {{The Linux Kernel/source|kernel/static_call_inline.c}} &amp;ndash; static call core
:: {{The Linux Kernel/source|arch/x86/kernel/static_call.c}} &amp;ndash; x86 static call patching
: {{The Linux Kernel/source|arch/x86/include/asm/alternative.h}} &amp;ndash; runtime instruction patching
:: {{The Linux Kernel/source|arch/x86/kernel/alternative.c}} &amp;ndash; x86 alternatives engine
::: {{The Linux Kernel/id|smp_text_poke_single}} &amp;ndash; safely patch code on SMP using INT3 breakpoints; used by static keys, static calls, ftrace, kprobes
:::: {{The Linux Kernel/id|smp_text_poke_batch_add}}
:::: {{The Linux Kernel/id|smp_text_poke_batch_finish}}


👁 Examples
: {{The Linux Kernel/id|housekeeping_overridden}}
: {{The Linux Kernel/id|preempt_schedule}}
: tracepoints


📖 References
: {{The Linux Kernel/doc|Static Keys|staging/static-keys.html}}
: {{The Linux Kernel/doc|x86 CPU feature flags|arch/x86/cpuinfo.html}}


=== {{w|Memory barrier}}s ===

Memory barriers (MB) are synchronization mechanisms used to ensure proper ordering of memory operations in a SMP environment.
They play a crucial role in maintaining the consistency and correctness of data shared among different CPU cores or processors.
MBs prevent unexpected and potentially harmful reordering of memory access instructions by the compiler or CPU, which can lead to data corruption and race conditions in a concurrent software system.

⚲ API
: {{The Linux Kernel/man|2|membarrier}}
: {{The Linux Kernel/include|asm-generic/barrier.h}}
:: {{The Linux Kernel/id|mb}}, {{The Linux Kernel/id|rmb}}, {{The Linux Kernel/id|wmb}}
:: {{The Linux Kernel/id|smp_mb}}, {{The Linux Kernel/id|smp_rmb}}, {{The Linux Kernel/id|smp_wmb}}


⚙️ Internals

: {{The Linux Kernel/source|arch/x86/include/asm/barrier.h}} &amp;ndash; x86 memory barrier instructions
: {{The Linux Kernel/source|kernel/sched/membarrier.c}} &amp;ndash; membarrier system call


📖 References
: {{The Linux Kernel/doc|Memory barriers|core-api/wrappers/memory-barriers.html}}


=== States ===

C-states and P-states are features in modern CPUs designed to improve energy efficiency.

🗝️ Acronyms
: [https://uefi.org/htmlspecs/ACPI_Spec_6_4_html/08_Processor_Configuration_and_Control/processor-power-states.html C-states] &amp;ndash; CPU(?) states, aka idle states
: EPP &amp;ndash; {{The Linux Kernel/doc|Energy Performance Preference|admin-guide/pm/amd-pstate.html#energy-performance-preference-epp-rw}}
: HWP &amp;ndash; hardware-managed P-states, see [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=hwp_only hwp_only]
: [https://www.intel.com/content/www/us/en/docs/socwatch/user-guide/2020/p-state.html P-states] &amp;ndash; Performance states, see CPU Power and frequency scaling


⚲ API
: [https://linux.die.net/man/1/cpupower cpupower]


📖 References
: {{The Linux Kernel/doc|Working-State Power Management|admin-guide/pm/working-state.html}}
: https://lwn.net/Kernel/Index/#Power_management


==== Idle ====


C-states, {{w|ACPI#Processor_states|power states}}:
: C0 – operating, executing instructions.
: C1 (Halt) – internal {{w|Clock gating|clocks stopped}}.
: C1E (Enhanced Halt) – clocks stopped, voltage and frequency reduced.
: C2 (Stop-Clock) – internal and external {{w|Clock gating|clocks stopped}}.
: C3 (Deep Sleep) – clocks stopped, L1/L2 cache may flush, local APIC timer stops, requiring [[#Clock_infrastructure|tick broadcast]].
: C4 (Deeper Sleep) – voltage reduced.
: C6 (Deep Power Down) – state saved to SRAM, voltage can drop to 0V.
: C7 (Deeper Power Down) – C6 + L3 cache flushed.
: Modern Intel typically uses C1/C1E and C6, skipping C2–C5.
: ⚠️ ACPI state names (C1_ACPI, C2_ACPI, C3_ACPI) may not match actual hardware C-states. The [https://www.felixcloutier.com/x86/monitor:mwait MWAIT] hint reveals the real state: e.g. MWAIT 0x60 = hardware C6 may appear as &quot;C3_ACPI&quot;.


⚲ API
: turbostat --show CPU --quiet -n 1 --interval 0.1 --show sysfs
: [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=idle= idle=]
: /dev/cpu_dma_latency &amp;ndash; see {{The Linux Kernel/id|set_cpu_dma_latency}}
: C-states interfaces:
:: cpupower idle-info – show driver, governor, states with latency and residency
:: /sys/devices/system/cpu/cpuidle/
:: /sys/devices/system/cpu/cpu*/cpuidle/
::: cat /sys/devices/system/cpu/cpu0/cpuidle/state*/name – list available C-states
:: {{The Linux Kernel/include|linux/cpuidle.h}} – generic framework for CPU idle power management
: {{The Linux Kernel/include|linux/pm_qos.h}}


⚙️ Internals
: {{The Linux Kernel/source|drivers/cpuidle}} – CPU idle governors and drivers
: {{The Linux Kernel/source|drivers/idle/intel_idle.c}} – {{The Linux Kernel/doc|intel_idle|admin-guide/pm/intel_idle.html}}, hardcoded C-states per CPU model, modern Intel (C1/C1E/C6)
: {{The Linux Kernel/source|drivers/acpi/processor_idle.c}} – acpi_idle, reads C-states from ACPI tables, generic fallback (C1/C2/C3)
: {{The Linux Kernel/source|kernel/power/qos.c}} – PM quality of service
:: {{The Linux Kernel/id|cpu_latency_qos_miscdev}} – implementation of /dev/cpu_dma_latency


📖 References
:: {{The Linux Kernel/doc|CPU Idle Time Management|admin-guide/pm/cpuidle.html}}
: [https://www.intel.com/content/www/us/en/support/articles/000006619/processors/intel-core-processors.html Intel C-states reference]
: [https://support.hpe.com/hpesc/public/docDisplay?docId=sd00002067en_us&amp;page=GUID-855C475E-F9F9-460D-9475-B96DD982B587.html HPE C-states reference]


📚 Further reading
:: https://lwn.net/Kernel/Index/#Power_management-cpuidle
: {{The Linux Kernel/doc|PM Quality Of Service Interface|power/pm_qos_interface.html}}

==== Power and frequency ====


P-states, {{w|ACPI#Performance_state|performance states}}:
: P0 &amp;ndash; maximum power and frequency
: Pn &amp;ndash; less power and frequency
: ...


⚲ API
: Reliable measurement of actual CPU frequency
:: [https://manpages.debian.org/testing/linux-cpupower/turbostat.8.en.html turbostat] --quiet --show CPU,Bzy_MHz -n 1 --interval 0.1
::: Bzy_MHz &amp;ndash; average clock rate while the CPU was not idle (ie. in &quot;c0&quot; state).
: [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=intel_pstate intel_pstate=]
:: {{The Linux Kernel/doc|Kernel Command Line Options for intel_pstate|admin-guide/pm/intel_pstate.html#kernel-command-line-options-for-intel-pstate}}
: [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=cpufreq.default_governor cpufreq.default_governor=]
: P-states interfaces:
:: /sys/devices/system/cpu/cpufreq/
:: /sys/devices/system/cpu/cpu*/cpufreq/
::: scaling_cur_freq &amp;ndash; unreliable assumption on CPU frequency
:: /sys/devices/system/cpu/intel_pstate/
:: {{The Linux Kernel/include|linux/cpufreq.h}}
:: {{The Linux Kernel/include|linux/sched/cpufreq.h}} &amp;ndash; interface between cpufreq drivers and the scheduler


⚙️ Internals
: {{The Linux Kernel/source|drivers/cpufreq}} &amp;ndash; CPU frequency scaling drivers
:: {{The Linux Kernel/id|intel_pstate}}
:: {{The Linux Kernel/id|acpi_cpufreq_driver}}
: {{The Linux Kernel/source|kernel/sched/cpufreq_schedutil.c}} &amp;ndash; implementation of cpufreq.default_governor=schedutil
: {{The Linux Kernel/source|arch/x86/kernel/cpu/intel_epb.c}} &amp;ndash; Intel Performance and Energy Bias Hint support


📖 References
: {{The Linux Kernel/doc|CPU Performance Scaling|admin-guide/pm/cpufreq.html}}
: {{The Linux Kernel/doc|Device Frequency Scaling|driver-api/devfreq.html}}
: [https://www.kernel.org/doc/Documentation/cpu-freq/governors.txt CPUFreq Governor]
: {{The Linux Kernel/doc|CPUFreq - CPU frequency and voltage scaling|cpu-freq}}
: {{The Linux Kernel/doc|Intel Performance and Energy Bias Hint|admin-guide/pm/intel_epb.html}}
: {{The Linux Kernel/doc|intel_pstate CPU Performance Scaling Driver|admin-guide/pm/intel_pstate.html}}
:: {{The Linux Kernel/doc|General Information|admin-guide/pm/intel_pstate.html#general-information}} 
:: {{The Linux Kernel/doc|Operation Modes|admin-guide/pm/intel_pstate.html#operation-modes}} 
::: {{The Linux Kernel/doc|Active Mode|admin-guide/pm/intel_pstate.html#active-mode}}
&lt;!--
:::: {{The Linux Kernel/doc|Active Mode With HWP|admin-guide/pm/intel_pstate.html#active-mode-with-hwp}} 
::::: {{The Linux Kernel/doc|HWP + performance|admin-guide/pm/intel_pstate.html#hwp-performance}} 
::::: {{The Linux Kernel/doc|HWP + powersave|admin-guide/pm/intel_pstate.html#hwp-powersave}} 
:::: {{The Linux Kernel/doc|Active Mode Without HWP|admin-guide/pm/intel_pstate.html#active-mode-without-hwp}} 
::::: {{The Linux Kernel/doc|performance|admin-guide/pm/intel_pstate.html#performance}} 
::::: {{The Linux Kernel/doc|powersave|admin-guide/pm/intel_pstate.html#powersave}} 
--&gt;
::: {{The Linux Kernel/doc|Passive Mode|admin-guide/pm/intel_pstate.html#passive-mode}} 
:: {{The Linux Kernel/doc|Turbo P-states Support|admin-guide/pm/intel_pstate.html#turbo-p-states-support}} 
:: {{The Linux Kernel/doc|Processor Support|admin-guide/pm/intel_pstate.html#processor-support}} 
:: {{The Linux Kernel/doc|Support for Hybrid Processors|admin-guide/pm/intel_pstate.html#support-for-hybrid-processors}} 
::: {{The Linux Kernel/doc|Hybrid Processors with SMT|admin-guide/pm/intel_pstate.html#hybrid-processors-with-smt}} 
::: {{The Linux Kernel/doc|Capacity-Aware Scheduling Support|admin-guide/pm/intel_pstate.html#capacity-aware-scheduling-support}} 
::: {{The Linux Kernel/doc|Energy-Aware Scheduling Support|admin-guide/pm/intel_pstate.html#energy-aware-scheduling-support}} 
:: {{The Linux Kernel/doc|User Space Interface in sysfs|admin-guide/pm/intel_pstate.html#user-space-interface-in-sysfs}} 
::: {{The Linux Kernel/doc|Global Attributes|admin-guide/pm/intel_pstate.html#global-attributes}} 
::: {{The Linux Kernel/doc|Interpretation of Policy Attributes|admin-guide/pm/intel_pstate.html#interpretation-of-policy-attributes}} 
::: {{The Linux Kernel/doc|Coordination of P-State Limits|admin-guide/pm/intel_pstate.html#coordination-of-p-state-limits}} 
::: {{The Linux Kernel/doc|Energy vs Performance Hints|admin-guide/pm/intel_pstate.html#energy-vs-performance-hints}} 
:: {{The Linux Kernel/doc|intel_pstate vs acpi-cpufreq|admin-guide/pm/intel_pstate.html#intel-pstate-vs-acpi-cpufreq}} 
:: {{The Linux Kernel/doc|Kernel Command Line Options for intel_pstate|admin-guide/pm/intel_pstate.html#kernel-command-line-options-for-intel-pstate}} 
:: {{The Linux Kernel/doc|Diagnostics and Tuning|admin-guide/pm/intel_pstate.html#diagnostics-and-tuning}} 
::: {{The Linux Kernel/doc|Trace Events|admin-guide/pm/intel_pstate.html#trace-events}} 
::: {{The Linux Kernel/doc|ftrace|admin-guide/pm/intel_pstate.html#ftrace}} 
&lt;!-- end of intel_pstate.html --&gt;


📚 Further reading
: https://lwn.net/Kernel/Index/#Power_management-Frequency_scaling
: [https://wiki.archlinux.org/title/CPU_frequency_scaling CPU frequency scaling]
: {{The Linux Kernel/ltp|kernel/device-drivers|cpufreq}}
: [https://www.thinkwiki.org/wiki/How_to_use_cpufrequtils How to use cpufrequtils] 
:: [https://linux.die.net/man/1/cpufreq-info cpufreq-info]
:: [https://linux.die.net/man/1/cpufreq-set cpufreq-set]
: https://github.com/intel/power-optimization-library
: https://github.com/intel/kubernetes-power-manager

{{BookCat}}</text>
      <sha1>2s449x79kv17y3fvzb05m941bm8wpq5</sha1>
    </revision>
    <revision>
      <id>4656113</id>
      <parentid>4656111</parentid>
      <timestamp>2026-08-02T20:47:59Z</timestamp>
      <contributor>
        <username>Conan</username>
        <id>3188</id>
      </contributor>
      <minor />
      <comment>spc</comment>
      <origin>4656113</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="56958" sha1="4cnh2xamlvbjprbg901i2o45nmyj9qy" xml:space="preserve">&lt;noinclude&gt;{{DISPLAYTITLE:Interrupts and CPU}}&lt;/noinclude&gt;
== Interrupts ==
An {{w|interrupt}} is a signal to the processor emitted by hardware or software indicating an event that needs immediate attention.
An interrupt alerts the processor to a high-priority condition requiring the interruption of the current code the processor is executing.
The processor responds by suspending its current activities, saving its state, and executing a function called an ''interrupt handler'' (or an interrupt service routine, ISR) to deal with the event.
This interruption is temporary, and, after the interrupt handler finishes, the processor resumes normal activities.

There are two types of interrupts: hardware interrupts and software interrupts.
Hardware interrupts are used by devices to communicate that they require attention from the operating system.
For example, pressing a key on the keyboard or moving the mouse triggers hardware interrupts that cause the processor to read the keystroke or mouse position.
Unlike the software type, hardware interrupts are asynchronous and can occur in the middle of instruction execution, requiring additional care in programming.
The act of initiating a hardware interrupt is referred to as an ''interrupt request'' - IRQ ↪ {{w|Interrupt descriptor table|IDT}} ↪ {{The Linux Kernel/id|common_interrupt}} on x86.

A software interrupt is caused either by an exceptional condition in the processor itself, or a special instruction in the instruction set which causes an interrupt when it is executed.
The former is often called a ''{{w|Trap (computing)|trap}}'' (⚙️ {{The Linux Kernel/id|do_trap}}) or ''exception'' and is used for errors or events occurring during program execution that are exceptional enough that they cannot be handled within the program itself.
For example, if the processor's arithmetic logic unit is commanded to divide a number by zero, this impossible demand will cause a ''divide-by-zero exception'' (⚙️ {{The Linux Kernel/id|X86_TRAP_DE}}), perhaps causing the computer to abandon the calculation or display an error message.
Software interrupt instructions function similarly to subroutine calls and are used for a variety of purposes, such as to request services from low-level system software such as device drivers.
For example, computers often use software interrupt instructions to communicate with the disk controller to request data be read or written to the disk.

Each interrupt has its own interrupt handler.  The number of hardware interrupts is limited by the number of interrupt request (IRQ) lines to the processor, but there may be hundreds of different software interrupts.


⚲ API

: /proc/interrupts
: {{The Linux Kernel/man|1|irqtop}} &amp;ndash; utility to display kernel interrupt information
: [https://github.com/Irqbalance/irqbalance irqbalance] &amp;ndash; distribute hardware interrupts across processors on a multiprocessor system
: There are many ways to request ISR, two of them
: {{The Linux Kernel/id|devm_request_threaded_irq}} &amp;ndash; preferable, managed device with threaded ISR
: {{The Linux Kernel/id|devm_request_irq}} &amp;ndash; managed version
:: {{The Linux Kernel/id|request_irq}}
::: {{The Linux Kernel/id|request_threaded_irq}}
: {{The Linux Kernel/id|free_irq}}
: {{The Linux Kernel/include|linux/interrupt.h}} &amp;ndash; main interrupt support header
:: {{The Linux Kernel/id|irqaction}} &amp;ndash; contains handler functions 
: {{The Linux Kernel/include|linux/irq.h}}
:: {{The Linux Kernel/id|irq_data}}
: {{The Linux Kernel/include|linux/irqflags.h}}
:: {{The Linux Kernel/id|irqs_disabled}}
:: {{The Linux Kernel/id|local_irq_save}} ...
:: {{The Linux Kernel/id|local_irq_disable}} ...
: {{The Linux Kernel/include|linux/irqdesc.h}}
:: {{The Linux Kernel/id|irq_desc}}
: {{The Linux Kernel/include|linux/irqdomain.h}}
:: {{The Linux Kernel/id|irq_domain}} &amp;ndash; hardware interrupt number translation object
:: {{The Linux Kernel/id|irq_domain_get_irq_data}}
: {{The Linux Kernel/include|linux/msi.h}} &amp;ndash; {{w|Message Signaled Interrupts}}
:: {{The Linux Kernel/id|msi_desc}}
: Structure of structures:
:: {{The Linux Kernel/id|irq_desc}} is container of
::: {{The Linux Kernel/id|irq_data}}
:::: irq &amp;ndash; interrupt number
::: {{The Linux Kernel/id|irq_common_data}}
::: list of {{The Linux Kernel/id|irqaction}}


⚙️ Internals

: {{The Linux Kernel/source|kernel/irq/settings.h}} &amp;ndash; IRQ descriptor status flags
: {{The Linux Kernel/source|kernel/irq}} &amp;ndash; generic IRQ handling
:: {{The Linux Kernel/source|kernel/irq/internals.h}} &amp;ndash; IRQ subsystem internal functions
: ls /sys/kernel/debug/irq/domains/
:: {{The Linux Kernel/id|x86_vector_domain}}, {{The Linux Kernel/id|x86_vector_domain_ops}}
: {{The Linux Kernel/id|irq_chip}}
: {{The Linux Kernel/id|load_idt}} &amp;ndash; load Interrupt Descriptor Table
: {{The Linux Kernel/source|arch/x86/include/asm/idtentry.h}} &amp;ndash; interrupt entry/exit definitions
: {{The Linux Kernel/source|arch/x86/include/asm/hw_irq.h}} &amp;ndash; x86 hardware IRQ definitions
:: {{The Linux Kernel/id|irq_entries_start}} &amp;ndash; hardware IRQ entry stubs
: {{The Linux Kernel/source|arch/x86/kernel/irq.c}} &amp;ndash; x86 interrupt handling
:: {{The Linux Kernel/id|common_interrupt}} &amp;ndash; handles all normal device IRQs on x86
: {{The Linux Kernel/source|arch/x86/kernel/apic}} &amp;ndash; {{w|Advanced Programmable Interrupt Controller|APIC}}
:: {{The Linux Kernel/source|arch/x86/kernel/apic/apic.c}} &amp;ndash; local APIC core (timer, calibration, spurious interrupt)
:: {{The Linux Kernel/source|arch/x86/kernel/apic/io_apic.c}} &amp;ndash; {{w|IOAPIC|I/O APIC}}, routes device IRQs to CPUs
:: {{The Linux Kernel/source|arch/x86/kernel/apic/x2apic_cluster.c}} &amp;ndash; {{w|x2APIC}} (&gt;256 CPUs)
:: {{The Linux Kernel/source|arch/x86/kernel/apic/ipi.c}} &amp;ndash; {{w|Inter-processor interrupt|IPI}}, see [[#IPI|IPI]]
:: {{The Linux Kernel/source|arch/x86/kernel/apic/hw_nmi.c}} &amp;ndash; hardware NMI watchdog via APIC
:: {{The Linux Kernel/source|arch/x86/kernel/apic/vector.c}} &amp;ndash; IRQ vector allocation
:: {{The Linux Kernel/source|arch/x86/kernel/apic/msi.c}} &amp;ndash; {{w|Message Signaled Interrupts|MSI}} via APIC

📖 References
: {{The Linux Kernel/doc|IRQs|core-api/irq}}
:: {{The Linux Kernel/doc|The irq_domain interrupt number mapping library|core-api/irq/irq-domain.html}}
: {{The Linux Kernel/doc|Linux generic IRQ handling|core-api/genericirq.html}}
: {{The Linux Kernel/doc|Message Signaled Interrupts: The MSI Driver Guide|PCI/msi-howto.html}}
: {{The Linux Kernel/doc|Lock types and their rules|locking/locktypes.html}}
: {{The Linux Kernel/doc|Hard IRQ Context|kernel-hacking/locking.html#hard-irq-context}}
: [https://0xax.gitbooks.io/linux-insides/content/Interrupts/ Interrupts]


👁 Examples
: {{The Linux Kernel/id|dummy_irq_chip}} &amp;ndash; dummy interrupt chip implementation
: {{The Linux Kernel/source|lib/locking-selftest.c}} &amp;ndash; locking correctness self-tests


=== IRQ affinity ===

⚲ API
: /proc/irq/default_smp_affinity
: /proc/irq/*/smp_affinity and /proc/irq/*/smp_affinity_list


Common types and functions:
: struct {{The Linux Kernel/id|irq_affinity}} &amp;ndash; description for automatic irq affinity assignments, see {{The Linux Kernel/id|devm_platform_get_irqs_affinity}}
: struct {{The Linux Kernel/id|irq_affinity_desc}} &amp;ndash; interrupt affinity descriptor, see {{The Linux Kernel/id|irq_update_affinity_desc}}, {{The Linux Kernel/id|irq_create_affinity_masks}}
: {{The Linux Kernel/id|irq_set_affinity}}
: {{The Linux Kernel/id|irq_get_affinity_mask}} 
: {{The Linux Kernel/id|irq_can_set_affinity}}
: {{The Linux Kernel/id|irq_set_affinity_hint}} 
: {{The Linux Kernel/id|irqd_affinity_is_managed}} 
: {{The Linux Kernel/id|irq_data_get_affinity_mask}}
: {{The Linux Kernel/id|irq_data_get_effective_affinity_mask}} 
: {{The Linux Kernel/id|irq_data_update_effective_affinity}} 
: {{The Linux Kernel/id|irq_set_affinity_notifier}} 
: {{The Linux Kernel/id|irq_affinity_notify}} 
: {{The Linux Kernel/id|irq_chip_set_affinity_parent}} 
: {{The Linux Kernel/id|irq_set_vcpu_affinity}}


🛠️ Utilities
: [https://man.archlinux.org/man/extra/irqbalance/irqbalance.1.en irqbalance] – distributes hardware interrupts across CPUs


📖 References
: {{The Linux Kernel/doc|SMP IRQ affinity|core-api/irq/irq-affinity.html}}
: [https://wiki.linuxfoundation.org/realtime/documentation/howto/tools/cpu-partitioning/start#irq_affinity IRQ affinity, LF]
: [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=managed_irq managed_irq kernel parameter], [https://lore.kernel.org/lkml/?q=managed_irq @LKML]
: [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=irqaffinity= irqaffinity kernel parameter], [https://lore.kernel.org/lkml/?q=irqaffinity @LKML]


=== Non-maskable interrupts ===

⚲ API
: {{The Linux Kernel/include|linux/nmi.h}}
:: {{The Linux Kernel/id|in_nmi}}
:: {{The Linux Kernel/id|touch_nmi_watchdog}}
:: ...
: {{The Linux Kernel/include|trace/events/nmi.h}}
: {{The Linux Kernel/source|arch/x86/include/asm/nmi.h}} &amp;ndash; x86 NMI handler registration
:: {{The Linux Kernel/id|register_nmi_handler}}
:: {{The Linux Kernel/id|unregister_nmi_handler}}


⚙️ Internals
: {{The Linux Kernel/source|arch/x86/kernel/nmi.c}} &amp;ndash; x86 NMI handler
: {{The Linux Kernel/source|arch/x86/kernel/apic/hw_nmi.c}} &amp;ndash; hardware NMI watchdog via APIC
: {{The Linux Kernel/source|arch/x86/kernel/nmi_selftest.c}} &amp;ndash; NMI IPI self-tests


📖 References
: {{The Linux Kernel/doc|NMI Trace Events|trace/events-nmi.html}}


📚 Further reading
: [https://0xax.gitbooks.io/linux-insides/content/Interrupts/linux-interrupts-6.html Non-maskable interrupt handler] (NMI)


=== ... ===

📚 Further reading about interrupts
: IDT &amp;ndash; {{w|Interrupt descriptor table}}
: [https://www.felixcloutier.com/x86/lgdt:lidt LGDT/LIDT &amp;ndash; Load Global/Interrupt Descriptor Table Register] asm instruction

== Deferred works ==

=== Scheduler context ===

==== kthread work ====

This framework simplifies the use of kernel kthreads.
A {{The Linux Kernel/id|kthread_work}} item can be queued with {{The Linux Kernel/id|kthread_queue_work}} and flushed using {{The Linux Kernel/id|kthread_flush_work}}.
All queued kthread_work items are processed by a dedicated kernel thread executing the {{The Linux Kernel/id|kthread_worker_fn}} function.

⚲ API
: {{The Linux Kernel/id|kthread_work}} &amp;ndash; contains {{The Linux Kernel/id|kthread_work_func_t}} to execute
:: {{The Linux Kernel/id|kthread_init_work}}
:: {{The Linux Kernel/id|kthread_flush_work}}
: {{The Linux Kernel/id|kthread_worker}} &amp;ndash; links a kthread_work and a task
:: {{The Linux Kernel/id|kthread_run_worker}} &amp;ndash; creates and wakes a kthread worker
::: {{The Linux Kernel/id|kthread_create_worker}}
::: {{The Linux Kernel/id|kthread_flush_worker}}
:: {{The Linux Kernel/id|kthread_destroy_worker}}
: {{The Linux Kernel/id|kthread_queue_work}} &amp;ndash; queues a kthread_work on a kthread_worker


⚙️ Internals
: {{The Linux Kernel/id|__kthread_create_worker_on_node}}
: {{The Linux Kernel/id|kthread_worker_fn}} &amp;ndash; executes work's function


👁 Example usages
: {{The Linux Kernel/id|watchdog_kworker}}, {{The Linux Kernel/id|pwq_release_worker}}, {{The Linux Kernel/id|pump_messages}}

==== Threaded IRQ ====

⚲ API
{{The Linux Kernel/id|devm_request_threaded_irq}}, {{The Linux Kernel/id|request_threaded_irq}}
ISR should return IRQ_WAKE_THREAD to run thread function

⚙️ Internals
: {{The Linux Kernel/id|setup_irq_thread}}, {{The Linux Kernel/id|irq_thread}}
: {{The Linux Kernel/source|kernel/irq/manage.c}} &amp;ndash; IRQ request, free and affinity management

📖 References
: {{The Linux Kernel/doc|request_threaded_irq|core-api/genericirq.html#c.request_threaded_irq}}


==== Work and workqueue ====

Generic async execution with shared worker pool.

⚲ API
: {{The Linux Kernel/id|PF_WQ_WORKER}} &amp;ndash; workqueue worker process flag
: {{The Linux Kernel/include|linux/workqueue.h}}, {{The Linux Kernel/include|linux/workqueue_types.h}}
: {{The Linux Kernel/id|work_struct}}, {{The Linux Kernel/id|INIT_WORK}}
: {{The Linux Kernel/id|delayed_work}}, {{The Linux Kernel/id|INIT_DELAYED_WORK}}, {{The Linux Kernel/id|cancel_delayed_work_sync}}
: {{The Linux Kernel/id|workqueue_struct}}
:: {{The Linux Kernel/id|devm_alloc_workqueue}}
::: {{The Linux Kernel/id|alloc_workqueue}}
:: {{The Linux Kernel/id|destroy_workqueue}}
: {{The Linux Kernel/id|schedule_work}} &amp;ndash; queues work on the system workqueue ↯
:: {{The Linux Kernel/id|queue_work}} &amp;ndash; queues work on a workqueue
::: {{The Linux Kernel/id|queue_work_on}} &amp;ndash; on a specific CPU
: {{The Linux Kernel/id|show_all_workqueues}}
:: {{The Linux Kernel/id|show_one_workqueue}}
: {{The Linux Kernel/id|system_power_efficient_wq}} ...


👁 Example usage {{The Linux Kernel/source|samples/ftrace/sample-trace-array.c}}


⚙️ Internals
: {{The Linux Kernel/source|kernel/workqueue.c}} &amp;ndash; generic async execution with shared worker pool
:: {{The Linux Kernel/id|workqueue_init}}
::: {{The Linux Kernel/id|create_worker}}
:::: {{The Linux Kernel/id|worker_thread}}
::::: {{The Linux Kernel/id|process_one_work}}
:: {{The Linux Kernel/id|format_worker_id}} &amp;ndash; names kworker kthreads
:: {{The Linux Kernel/id|pool_workqueue}}
::: {{The Linux Kernel/id|worker_pool}}


📖 References
: {{The Linux Kernel/doc|Concurrency Managed Workqueue|core-api/workqueue.html}}
: [https://sysprog21.github.io/lkmpg/#work-queues LKMPG: Work queues]

=== Interrupt context ===

: {{The Linux Kernel/include|linux/irq_work.h}} &amp;ndash; run callbacks from hardirq or NMI context where normal work queues can't be used
:: {{The Linux Kernel/id|irq_work_queue}} &amp;ndash; enqueue work on the current CPU, triggers {{The Linux Kernel/id|IRQ_WORK_VECTOR}} IPI if needed
:: {{The Linux Kernel/id|irq_work_sync}} &amp;ndash; wait for completion
:: {{The Linux Kernel/source|kernel/irq_work.c}} &amp;ndash; irq_work implementation
:: 👁 {{The Linux Kernel/source|samples/trace_printk/trace-printk.c}}

==== Timers ====

⚠️ &quot;Timer&quot; in the kernel means different things: ''[[#softirq_timer|kernel timer]]'' – jiffies-based software callback, ''[[#High-resolution_timer|hrtimer]]'' – nanosecond software callback, ''[[The_Linux_Kernel/Multitasking#POSIX_Timers|POSIX timer]]'' – userspace API, ''[[The_Linux_Kernel/Debugging#Watchdogs|watchdog timer]]'' – hang detection, ''[[#Clock_infrastructure|local APIC timer]]'' – per-CPU hardware, drives the tick.

===== softirq timer =====

This timer is a softirq for periodical tasks with jiffies resolution

⚲ API
: {{The Linux Kernel/include|linux/timer.h}}
: {{The Linux Kernel/id|timer_list}}, {{The Linux Kernel/id|DEFINE_TIMER}}, {{The Linux Kernel/id|timer_setup}}
: {{The Linux Kernel/id|mod_timer}} &amp;mdash; sets expiration time in jiffies. 
: {{The Linux Kernel/id|del_timer}}


⚙️ Internals
: {{The Linux Kernel/source|kernel/time/timer.c}} &amp;ndash; kernel internal timers
:: {{The Linux Kernel/id|timer_bases}}


👁 Examples
: {{The Linux Kernel/id|input_enable_softrepeat}} and {{The Linux Kernel/id|input_start_autorepeat}}


📚 References
: {{The Linux Kernel/doc|Time and timer routines|driver-api/basics.html#time-and-timer-routines}}
:: {{The Linux Kernel/doc|mod_timer_pending ... |driver-api/basics.html#c.mod_timer_pending}}

===== High-resolution timer =====

⚲ API
: /proc/timer_list
: /proc/sys/kernel/timer_migration
: {{The Linux Kernel/include|linux/hrtimer_defs.h}}
: {{The Linux Kernel/include|linux/hrtimer.h}}
: {{The Linux Kernel/id|hrtimer}}, hrtimer.function &amp;mdash; callback
: {{The Linux Kernel/id|hrtimer_init}}
: {{The Linux Kernel/id|hrtimer_setup}}
: {{The Linux Kernel/id|hrtimer_start}} &amp;mdash; starts a timer with nanosecond resolution 
: {{The Linux Kernel/id|hrtimer_cancel}}


👁 Examples {{The Linux Kernel/id|alarm_init}}, {{The Linux Kernel/id|watchdog_enable}}


⚙️ Internals
: {{The Linux Kernel/id|CONFIG_HIGH_RES_TIMERS}}
: {{The Linux Kernel/source|kernel/time/tick-internal.h}} &amp;ndash; tick and timer internal definitions
:: {{The Linux Kernel/id|hrtimer_bases}}
: {{The Linux Kernel/source|kernel/time/hrtimer.c}} &amp;ndash; high-resolution timer implementation
: {{The Linux Kernel/source|kernel/time/itimer.c}} &amp;ndash; interval timers
: {{The Linux Kernel/source|kernel/time/timer_list.c}} &amp;ndash; /proc/timer_list debugfs


📚 HR timers references
: {{The Linux Kernel/doc|High-resolution timers|driver-api/basics.html#high-resolution-timers}}
: {{The Linux Kernel/doc|hrtimers - subsystem for high-resolution kernel timers|timers/hrtimers.html}}
: {{The Linux Kernel/doc|high resolution timers and dynamic ticks design notes|timers/highres.html}}

===== Tick and NO_HZ =====

The tick is the periodic timer interrupt that drives scheduling, timekeeping, and RCU.
The NO_HZ subsystem reduces or eliminates tick interrupts to save power and reduce latency.

⚲ API
: /sys/devices/system/cpu/nohz_full – active nohz_full CPUs
: [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=nohz_full= nohz_full=] boot parameter – list of CPUs to run tickless
: {{The Linux Kernel/include|linux/tick.h}} – tick control API
:: {{The Linux Kernel/id|tick_nohz_full_running}} – true if any CPU runs tickless

🪛 Compile-time configurations ({{The Linux Kernel/source|kernel/time/Kconfig}})
: {{The Linux Kernel/id|CONFIG_HZ_PERIODIC}} – constant-rate tick, always firing
: {{The Linux Kernel/id|CONFIG_NO_HZ_IDLE}} – stop tick when CPU is idle (default on most distros)
: {{The Linux Kernel/id|CONFIG_NO_HZ_FULL}} – stop tick even when running a single task, for RT and latency-sensitive workloads, see [[#CPU_isolation|CPU isolation]]

⚙️ Internals
: {{The Linux Kernel/source|kernel/time/tick-common.c}} – periodic tick setup
: {{The Linux Kernel/source|kernel/time/tick-oneshot.c}} – oneshot mode for hrtimers and NO_HZ
: {{The Linux Kernel/source|kernel/time/tick-sched.c}} – NO_HZ tick scheduling logic
: {{The Linux Kernel/source|kernel/time/tick-broadcast.c}} – broadcast tick for CPUs in deep idle where local timer stops ([[#Idle|C3+]])
: {{The Linux Kernel/source|kernel/time/timer_migration.c}} – migrate timers from idle to busy CPUs

📖 References
: {{The Linux Kernel/doc|NO_HZ: Reducing Scheduling-Clock Ticks|timers/no_hz.html}}
: [https://wiki.linuxfoundation.org/realtime/documentation/howto/tools/ticklesskernel Tickless kernel, RT wiki]
: {{The Linux Kernel/doc|high resolution timers and dynamic ticks design notes|timers/highres.html}}

===== Clock infrastructure =====

⚠️ Not to confuse: ''[[The_Linux_Kernel/System#Hardware_Device_Drivers|clk framework]]'' – SoC {{w|Clock signal|clock}} tree management in drivers/clk.

Clocksources read current time (passive counters).
Clock event devices fire interrupts at a programmed time (active).
Together they are the foundation for timekeeping, timers, tick, and NO_HZ.


⚲ Clocksources – &quot;what time is it?&quot;
: /sys/devices/system/clocksource/clocksource0/current_clocksource
: /sys/devices/system/clocksource/clocksource0/available_clocksource
:: {{w|Time Stamp Counter|TSC}} – fastest, per-CPU, x86
:: {{w|High Precision Event Timer|HPET}} – system-wide, MMIO
:: ACPI PM timer – never stops in any C-state, slow
: {{The Linux Kernel/include|linux/clocksource.h}} – {{The Linux Kernel/id|clocksource}}, {{The Linux Kernel/id|clocksource_register_hz}}


⚲ Clock event devices – &quot;wake me at time X&quot;
: {{The Linux Kernel/include|linux/clockchips.h}} – {{The Linux Kernel/id|clock_event_device}}, {{The Linux Kernel/id|clockevents_config_and_register}}
: Local {{w|Advanced Programmable Interrupt Controller|APIC}} timer – per-CPU, fastest, stops in [[#Idle|C3+]], {{The Linux Kernel/id|local_apic_timer_interrupt}}
: {{w|High Precision Event Timer|HPET}} – system-wide, used as broadcast fallback
&lt;!-- PIT (i8254) – legacy, stopped at boot on modern hardware --&gt;


⚙️ Internals
: {{The Linux Kernel/source|kernel/time/clocksource.c}} – clocksource selection and watchdog
: {{The Linux Kernel/source|kernel/time/clockevents.c}} – clock event device framework
: {{The Linux Kernel/source|kernel/time/jiffies.c}} – jiffies clocksource (fallback)


===== ... =====

📖 Timers references
: {{The Linux Kernel/doc|Timers|timers}}
: [https://lwn.net/Articles/913568/ Better CPU selection for timer expiration]

==== Tasklet ====

tasklet is a softirq, for time critical operations

⚲ API is deprecated in favor of threaded IRQs: {{The Linux Kernel/id|devm_request_threaded_irq}}
: {{The Linux Kernel/id|tasklet_struct}}, {{The Linux Kernel/id|tasklet_init}}, {{The Linux Kernel/id|tasklet_schedule}} 


⚙️ Internals: {{The Linux Kernel/id|tasklet_action_common}} HI_SOFTIRQ, TASKLET_SOFTIRQ


==== Softirq ====

softirq is internal system facility and should not be used directly.
Use tasklet or threaded IRQs

⚲ API
: {{The Linux Kernel/include|linux/interrupt.h}}
: cat /proc/softirqs
: {{The Linux Kernel/id|open_softirq}} registers {{The Linux Kernel/id|softirq_action}}
: {{The Linux Kernel/id|raise_softirq}}
: {{The Linux Kernel/id|tasklet_schedule}}
:: {{The Linux Kernel/id|__tasklet_schedule}}


⚙️ Internals
: {{The Linux Kernel/source|kernel/softirq.c}} &amp;ndash; software interrupt handling
:: {{The Linux Kernel/id|__do_softirq}} &amp;ndash; main softirq processing loop


📖 References
: [https://0xax.gitbooks.io/linux-insides/content/Interrupts/linux-interrupts-9.html Introduction to deferred interrupts (Softirq, Tasklets and Workqueues)]
: [https://0xax.gitbooks.io/linux-insides/content/Timers/ Timers and time management]
: [https://linux-kernel-labs.github.io/refs/heads/master/labs/deferred_work.html Deferred work, linux-kernel-labs]
: [https://www.oreilly.com/library/view/linux-device-drivers/0596005903/ch07.html Chapter 7. Time, Delays, and Deferred Work]

==CPU specific==


🖱️ GUI
: [https://manpages.ubuntu.com/manpages/kinetic/en/man8/tuna.8.html tuna] &amp;ndash; program for tuning running processes


⚲ API
: cat /proc/cpuinfo
: /sys/devices/system/cpu/
: /sys/devices/system/node/
: /sys/cpu/
: /sys/fs/cgroup/cpu/
: grep -i cpu /proc/self/status
: [https://manpages.ubuntu.com/manpages/jammy/man1/rdmsr.1.html rdmsr] &amp;ndash; tool for reading CPU machine specific registers (MSR)
: {{The Linux Kernel/man|1|lscpu}} &amp;ndash; display information about the CPU architecture

: {{The Linux Kernel/include|linux/arch_topology.h}} &amp;ndash; arch specific cpu topology information 
: {{The Linux Kernel/include|linux/cpu.h}} &amp;ndash; generic cpu definition 
: {{The Linux Kernel/include|linux/cpu_cooling.h}} 
: {{The Linux Kernel/include|linux/cpu_pm.h}} 
: {{The Linux Kernel/include|linux/cpufeature.h}}
: {{The Linux Kernel/source|arch/x86/include/asm/cpufeature.h}} &amp;ndash; x86 CPU feature detection
: {{The Linux Kernel/include|linux/peci-cpu.h}} 
: {{The Linux Kernel/include|linux/sched/cputime.h}} &amp;ndash; cputime accounting APIs
: {{The Linux Kernel/include|linux/clk.h}} &amp;ndash; interfaces for managing hardware clocks in device drivers


⚙️ Internals

: {{The Linux Kernel/source|drivers/base/cpu.c}} &amp;ndash; CPU driver model subsystem
:: {{The Linux Kernel/id|cpu_dev_init}}


=== Cache ===

: {{The Linux Kernel/include|linux/cacheflush.h}}
:: {{The Linux Kernel/source|arch/x86/include/asm/cacheflush.h}}: {{The Linux Kernel/id|clflush_cache_range}}
: {{The Linux Kernel/include|linux/cache.h}} &amp;ndash; cache line alignment macros
:: {{The Linux Kernel/id|____cacheline_aligned}} &amp;ndash; align to cache line boundary to avoid false sharing
:: {{The Linux Kernel/id|__cacheline_aligned}} &amp;ndash; same, plus place in .data..cacheline_aligned section
:: {{The Linux Kernel/id|____cacheline_aligned_in_smp}} &amp;ndash; same, but no-op on uniprocessor builds
:: {{The Linux Kernel/id|__read_mostly}} &amp;ndash; place in a cache-friendly section for rarely written data
:: {{The Linux Kernel/id|__ro_after_init}} &amp;ndash; writable during init, read-only after boot (security hardening)
:: {{The Linux Kernel/id|DEFINE_PER_CPU_CACHE_HOT}} &amp;ndash; per-CPU variable in .data..hot section, used for {{The Linux Kernel/id|current_task}}, {{The Linux Kernel/id|__preempt_count}}
:: {{The Linux Kernel/id|L1_CACHE_BYTES}}, {{The Linux Kernel/id|SMP_CACHE_BYTES}} &amp;ndash; 64 bytes typically
:: {{The Linux Kernel/source|arch/x86/include/asm/cache.h}} &amp;ndash; x86 cache line size definitions

🔨 [https://manpages.ubuntu.com/manpages/resolute/man1/stress-ng.1.html#:~:text=%2D%2Dcache stress-ng --cache]

⚙️ Internals

: {{The Linux Kernel/source|arch/x86/mm/pat/set_memory.c}} &amp;ndash; page attribute table memory type control
: {{The Linux Kernel/source|arch/x86/kernel/cpu/mtrr/}} &amp;ndash; memory type range register driver

📚 Further reading
: MTRR &amp;ndash; {{w|Memory type range register}}
: {{w|CPU cache}}

=== {{w|Symmetric_multiprocessing|SMP}} ===

This chapter is about multiprocessing and {{w|Multi-core processor|multi-core}} aspects of Linux kernel.

Key concepts and features of Linux SMP include:
* Symmetry: In an SMP system, all processors are considered the same without hardware hierarchy in contradiction to use of {{w|coprocessor}}s.
* Load balancing: The Linux kernel employs load balancing mechanisms to distribute tasks evenly among available CPU cores. This prevents any one core from becoming overwhelmed while others remain underutilized.
* Parallelism: SMP enables parallel processing, where multiple threads or processes can execute simultaneously on different CPU cores. This can significantly improve the execution speed of applications that are designed to take advantage of multiple threads.
* Thread scheduling: The Linux kernel scheduler is responsible for determining which threads or processes run on which CPU cores and for how long. It aims to optimize performance by minimizing contention and maximizing CPU utilization.
* Shared memory: In an SMP system, all CPU cores typically share the same physical memory space. This allows processes and threads running on different cores to communicate and share data more efficiently.
* NUMA &amp;ndash; {{w|Non-Uniform Memory Access}}: In larger SMP systems, memory access times might not be uniform due to the physical arrangement of memory banks and processors. Linux has mechanisms to handle NUMA architectures efficiently, allowing processes to be scheduled on CPUs closer to their associated memory.
* Cache coherency: SMP systems require mechanisms to ensure that all CPU cores have consistent views of memory. Cache coherency protocols ensure that changes made to shared memory locations are correctly propagated to all cores.
* Scalability: SMP systems can be scaled up to include more CPU cores, enhancing the overall computing power of the system. However, as the number of cores increases, challenges related to memory access, contention, and communication between cores may arise.
* Kernel and user space: Linux applications running in user space can take advantage of SMP without needing to be aware of the underlying hardware details. The kernel handles the management of CPU cores and resource allocation.


⚲ API
: &lt;code&gt;ps -PLe&lt;/code&gt; &amp;ndash; lists threads with processor that the thread last executed on (the third column PSR).
: {{The Linux Kernel/man|2|getcpu}} &amp;ndash; determine CPU and NUMA node on which the calling thread is running
: {{The Linux Kernel/man|8|chcpu}} &amp;ndash; configure CPUs
: {{The Linux Kernel/man|3|CPU_SET}} &amp;ndash; macros for manipulating CPU sets
: {{The Linux Kernel/include|linux/smp.h}}
:: The most commonly used functions:
:: {{The Linux Kernel/id|crash_smp_send_stop}} – halts all CPUs except the calling one in a crash context
:: {{The Linux Kernel/id|get_cpu}} – disables preemption and returns the current processor ID
:: {{The Linux Kernel/id|panic_smp_self_stop}} – stops the local CPU during a panic while ensuring others halt
:: {{The Linux Kernel/id|put_cpu}} – re-enables preemption after a previous get_cpu call
:: {{The Linux Kernel/id|raw_smp_processor_id}} – returns the current CPU ID without preemption safety
:: {{The Linux Kernel/id|setup_max_cpus}} – sets up the maximum number of CPUs to be brought online
:: {{The Linux Kernel/id|smp_init}} – initializes core SMP structures and state during boot
:: {{The Linux Kernel/id|smp_prepare_boot_cpu}} – prepares the boot CPU during early SMP initialization
:: {{The Linux Kernel/id|smp_prepare_cpus}} – prepares all CPUs for booting before secondary CPUs are started
:: {{The Linux Kernel/id|smp_processor_id}} – returns the ID of the current CPU with preemption checks
:: {{The Linux Kernel/id|smp_send_stop}} – stops all other CPUs in response to critical events
:: {{The Linux Kernel/id|wake_up_all_idle_cpus}} – wakes all idle CPUs to ensure prompt task execution
: {{The Linux Kernel/include|linux/cpu.h}}
: {{The Linux Kernel/include|linux/group_cpus.h}}: {{The Linux Kernel/id|group_cpus_evenly}} &amp;ndash; groups all CPUs evenly per NUMA/CPU locality
: {{The Linux Kernel/include|asm-generic/percpu.h}}
: {{The Linux Kernel/include|linux/percpu-defs.h}} &amp;ndash; basic definitions for percpu areas
:: {{The Linux Kernel/id|this_cpu_ptr}}
: {{The Linux Kernel/include|linux/percpu.h}} 
: {{The Linux Kernel/include|linux/percpu-refcount.h}} 
: {{The Linux Kernel/include|linux/percpu-rwsem.h}}
: {{The Linux Kernel/include|linux/preempt.h}}
:: {{The Linux Kernel/id|migrate_disable}}, {{The Linux Kernel/id|migrate_enable}}
: /sys/bus/cpu
: [[#per_CPU_local_lock|per CPU local_lock]]
: {{The Linux Kernel/include|linux/topology.h}} &amp;ndash; {{The Linux Kernel/id|cpu_to_node}}, {{The Linux Kernel/id|numa_node_id}}
: {{The Linux Kernel/source|arch/x86/include/asm/topology.h}} &amp;ndash; x86 NUMA and CPU topology
: See also [[../../Memory#NUMA|NUMA memory section]]


⚙️ Internals
: {{The Linux Kernel/id|boot_cpu_init}} activates the first CPU
: {{The Linux Kernel/id|smp_prepare_cpus}} initializes rest CPUs during boot
: {{The Linux Kernel/id|cpu_number}}
: {{The Linux Kernel/id|CONFIG_SMP}}
:: {{The Linux Kernel/id|CONFIG_NUMA}}
: {{The Linux Kernel/include|trace/events/percpu.h}}
: {{The Linux Kernel/file|drivers/base/cpu.c}} &amp;ndash; CPU driver model subsystem support
: {{The Linux Kernel/file|kernel/cpu.c}} &amp;ndash; CPU hotplug state machine
: smpboot
:: {{The Linux Kernel/include|linux/smpboot.h}}
:: {{The Linux Kernel/source|kernel/smpboot.c}} &amp;ndash; common SMP CPU bringup/teardown
:: {{The Linux Kernel/source|arch/x86/kernel/smpboot.c}} &amp;ndash; x86 SMP booting
: {{The Linux Kernel/source|lib/group_cpus.c}} &amp;ndash; distribute CPUs evenly across groups


🛠️ Utilities
: [https://man.archlinux.org/man/extra/irqbalance/irqbalance.1.en irqbalance] – distributes hardware interrupts across CPUs
: {{The Linux Kernel/man|8|numactl}} &amp;ndash; controls NUMA policy for processes or shared memory


📖 References
: {{The Linux Kernel/doc|Per-CPU Data|kernel-hacking/locking.html#per-cpu-data}}
: {{The Linux Kernel/doc|How CPU topology info is exported via sysfs|admin-guide/cputopology.html}}


📚 Further reading
: [https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/monitoring_and_managing_system_status_and_performance/customizing-tuned-profiles_monitoring-and-managing-system-status-and-performance#functionalities-of-the-scheduler-tuned-plug-in_customizing-tuned-profiles Functionalities of the scheduler TuneD plugin]
: [https://man.archlinux.org/man/tuned-adm.8 tuned-adm] &amp;ndash; command line tool for switching between different tuning profiles


==== {{w|Inter-processor interrupt|IPI}} ====

An inter-processor interrupt is a signal sent from one CPU to another to request an action such as rescheduling, TLB flush, or function execution.

⚲ API
: {{The Linux Kernel/id|smp_send_reschedule}} &amp;ndash; sends a reschedule IPI to a target CPU
: {{The Linux Kernel/id|smp_call_function}} &amp;ndash; invokes a function on all other CPUs via IPI
:: {{The Linux Kernel/id|smp_call_function_many}} &amp;ndash; on a specified set of CPUs
: {{The Linux Kernel/id|smp_call_function_single}} &amp;ndash; on a single target CPU
:: {{The Linux Kernel/id|smp_call_function_single_async}} &amp;ndash; asynchronous variant
: {{The Linux Kernel/id|smp_call_on_cpu}} &amp;ndash; execute on a specific CPU and wait for result
: {{The Linux Kernel/id|on_each_cpu}} &amp;ndash; run a function on all CPUs
:: {{The Linux Kernel/id|on_each_cpu_mask}} &amp;ndash; on a specified set of CPUs
:: {{The Linux Kernel/id|on_each_cpu_cond_mask}} &amp;ndash; conditionally on selected CPUs
: {{The Linux Kernel/id|smp_call_func_t}} &amp;ndash; callback typedef

⚙️ Internals
: {{The Linux Kernel/include|trace/events/ipi.h}}
: {{The Linux Kernel/file|kernel/irq/ipi.c}} &amp;ndash; generic IPI helpers
:: {{The Linux Kernel/id|ipi_send_single}}, {{The Linux Kernel/id|ipi_send_mask}}
: {{The Linux Kernel/source|arch/x86/kernel/apic/ipi.c}} &amp;ndash; x86 IPI via APIC
: {{The Linux Kernel/source|arch/x86/include/asm/irq_vectors.h}} &amp;ndash; x86 IPI vector types:
:: {{The Linux Kernel/id|RESCHEDULE_VECTOR}} &amp;ndash; used by {{The Linux Kernel/id|smp_send_reschedule}}
:: {{The Linux Kernel/id|CALL_FUNCTION_VECTOR}} &amp;ndash; used by {{The Linux Kernel/id|smp_call_function_many}}
:: {{The Linux Kernel/id|CALL_FUNCTION_SINGLE_VECTOR}} &amp;ndash; used by {{The Linux Kernel/id|smp_call_function_single}}
:: {{The Linux Kernel/id|IRQ_WORK_VECTOR}} &amp;ndash; used by {{The Linux Kernel/id|irq_work_queue}}, see [[#Interrupt_context|Interrupt context]]
:: {{The Linux Kernel/id|NMI_VECTOR}} &amp;ndash; used by watchdog, {{The Linux Kernel/id|crash_smp_send_stop}}

==== CPU affinity ====

Affinity refers to assigning a process or thread to specific CPU cores.
This helps control which CPUs execute tasks, potentially improving performance by reducing data movement between cores.
It can be managed using system calls or commands.
Affinity can be represented as CPU bitmask: {{The Linux Kernel/id|cpumask_t}} or CPU affinity list: {{The Linux Kernel/id|cpulist_parse}}.


⚲ API
: {{The Linux Kernel/man|1|taskset}} &amp;ndash; set or retrieve a process's CPU affinity
: grep Cpus_allowed /proc/self/status
: {{The Linux Kernel/man|2|sched_setaffinity}} {{The Linux Kernel/man|2|sched_getaffinity}} &amp;ndash; set and get a thread's CPU affinity mask
:: ↪ {{The Linux Kernel/id|sched_setaffinity}}
: {{The Linux Kernel/id|set_cpus_allowed_ptr}} &amp;ndash; common kernel function to change a task's affinity mask
: {{The Linux Kernel/include|linux/cpu_rmap.h}} &amp;ndash; CPU affinity reverse-map support
: {{The Linux Kernel/include|linux/cpumask_types.h}}
:: struct cpumask, {{The Linux Kernel/id|cpumask_t}} &amp;ndash; CPUs bitmap, can be very big
:: {{The Linux Kernel/id|cpumask_var_t}} &amp;ndash; type for local cpumask variable, see {{The Linux Kernel/id|alloc_cpumask_var}}, {{The Linux Kernel/id|free_cpumask_var}}.
: {{The Linux Kernel/include|linux/cpumask.h}} &amp;ndash; Cpumasks provide a bitmap suitable for representing the set of CPU's in a system, one bit position per CPU number
:: {{The Linux Kernel/id|for_each_possible_cpu}}
:: {{The Linux Kernel/id|num_online_cpus}}
:: {{The Linux Kernel/id|cpumask_set_cpu}}
:: {{The Linux Kernel/id|cpumask_test_cpu}}
:: {{The Linux Kernel/id|for_each_cpu}}


⚙️ Internals
: {{The Linux Kernel/id|cpus_mask}} &amp;ndash; affinity of {{The Linux Kernel/id|task_struct}}
: {{The Linux Kernel/id|cpus_allowed}} &amp;ndash; affinity of {{The Linux Kernel/id|cpuset}}


📚 Further reading
: {{w|Processor affinity}}
: {{w|Affinity mask}}

==== CPU hotplug ====

CPU hotplugging in Linux refers to the ability to dynamically add or remove CPUs from the system without needing a reboot.
This feature is crucial in environments requiring high availability and resource flexibility, such as data centers, virtualized systems, and systems that use power management aggressively.


🗝️ Acronyms
: BP &amp;ndash; Bootstrap Processor
: AP &amp;ndash; Application Processor


⚲ API
: /sys/devices/system/cpu/cpu*/online
: /sys/devices/system/cpu/cpu*/hotplug/
: {{The Linux Kernel/include|linux/cpu.h}}
:: {{The Linux Kernel/id|add_cpu}} ...
: {{The Linux Kernel/include|linux/cpuhotplug.h}}
:: {{The Linux Kernel/id|cpuhp_state}} &amp;ndash; CPU hotplug states 
:: {{The Linux Kernel/id|cpuhp_setup_state}} ... &amp;ndash; setups hotplug state callbacks
::: {{The Linux Kernel/id|cpuhp_setup_state_multi}}
::: {{The Linux Kernel/id|cpuhp_setup_state_nocalls}}
: {{The Linux Kernel/include|linux/cpuhplock.h}} &amp;ndash; CPU hotplug locking
:: {{The Linux Kernel/id|cpus_read_lock}} ...
:: {{The Linux Kernel/id|remove_cpu}} ...


⚙️ Internals
: {{The Linux Kernel/source|kernel/cpu.c}} &amp;ndash; CPU hotplug state machine
:: {{The Linux Kernel/id|cpuhp_state}} &amp;ndash; from CPUHP_OFFLINE to CPUHP_AP_ACTIVE and CPUHP_ONLINE.
:: {{The Linux Kernel/id|cpuhp_hp_states}}
:: {{The Linux Kernel/id|boot_cpu_hotplug_init}}
:: {{The Linux Kernel/id|cpuhp_threads_init}}
:: ... {{The Linux Kernel/id|cpuhp_invoke_callback_range}} ...
: {{The Linux Kernel/source|kernel/irq/cpuhotplug.c}} &amp;ndash; IRQ migration on CPU hotunplug
: {{The Linux Kernel/source|drivers/base/cpu.c}} &amp;ndash; CPU subsystem support
:: {{The Linux Kernel/id|cpu_dev_init}}
::: ... {{The Linux Kernel/id|cpu_subsys_online}}
: {{The Linux Kernel/include|trace/events/cpuhp.h}}
: {{The Linux Kernel/include|linux/cpuhplock.h}}


👁️ Examples
: {{The Linux Kernel/id|torture_onoff}}
: {{The Linux Kernel/source|tools/testing/selftests/sched_ext/hotplug.c}} &amp;ndash; sched_ext CPU hotplug test


📖 References
: {{The Linux Kernel/doc|CPU hotplug in the Kernel|core-api/cpu_hotplug.html}}
:: {{The Linux Kernel/doc|Introduction|core-api/cpu_hotplug.html#introduction}} 
:: {{The Linux Kernel/doc|Command Line Switches|core-api/cpu_hotplug.html#command-line-switches}} 
:: {{The Linux Kernel/doc|CPU maps|core-api/cpu_hotplug.html#cpu-maps}} 
:: {{The Linux Kernel/doc|Using CPU hotplug|core-api/cpu_hotplug.html#using-cpu-hotplug}} 
:: {{The Linux Kernel/doc|The CPU hotplug coordination|core-api/cpu_hotplug.html#the-cpu-hotplug-coordination}} 
:: {{The Linux Kernel/doc|The CPU hotplug API|core-api/cpu_hotplug.html#the-cpu-hotplug-api}} 
::: {{The Linux Kernel/doc|CPU hotplug state machine|core-api/cpu_hotplug.html#cpu-hotplug-state-machine}} 
::: {{The Linux Kernel/doc|CPU online/offline operations|core-api/cpu_hotplug.html#cpu-online-offline-operations}} 
::: {{The Linux Kernel/doc|Allocating a state|core-api/cpu_hotplug.html#allocating-a-state}} 
::: {{The Linux Kernel/doc|Setup of a CPU hotplug state|core-api/cpu_hotplug.html#setup-of-a-cpu-hotplug-state}} 
::: {{The Linux Kernel/doc|Removal of a CPU hotplug state|core-api/cpu_hotplug.html#removal-of-a-cpu-hotplug-state}} 
::: {{The Linux Kernel/doc|Multi-Instance state instance management|core-api/cpu_hotplug.html#multi-instance-state-instance-management}} 
::: {{The Linux Kernel/doc|Examples|core-api/cpu_hotplug.html#examples}} 
:: {{The Linux Kernel/doc|Testing of hotplug states|core-api/cpu_hotplug.html#testing-of-hotplug-states}} 
:: {{The Linux Kernel/doc|Architecture’s requirements|core-api/cpu_hotplug.html#architecture-s-requirements}} 
:: {{The Linux Kernel/doc|User Space Notification|core-api/cpu_hotplug.html#user-space-notification}} 
:: {{The Linux Kernel/doc|Kernel Inline Documentations Reference|core-api/cpu_hotplug.html#kernel-inline-documentations-reference}}
 

🔨 [https://manpages.ubuntu.com/manpages/resolute/man1/stress-ng.1.html#:~:text=%2D%2Dcpu%2Donline stress-ng --cpu-online]

📚 Further reading
: {{The Linux Kernel/id|CONFIG_CPU_HOTPLUG_STATE_CONTROL}} &amp;ndash; enables the ability to write incremental steps between &quot;offline&quot; and &quot;online&quot; states to the CPU's sysfs target file, allowing for more granular control of state transitions.
:: {{The Linux Kernel/id|target_store}}: {{The Linux Kernel/id|cpu_up}}/{{The Linux Kernel/id|cpu_down}}
: [https://lore.kernel.org/lkml/?q=cpuhotplug+OR+cpuhp cpuhotplug, cpuhp @LKML]

==== CPU isolation ====

CPU isolation ensures that specific tasks run on dedicated CPUs, reducing contention and latency.

'''Housekeeping''' CPUs refer to the CPUs that are reserved for various '''system''' tasks. See {{The Linux Kernel/id|hk_type}}.

'''Isolated''' CPUs are dedicated to '''real-time''' applications, such as DPDK.

⚲ API
: /sys/devices/system/cpu/isolated
: /sys/devices/system/cpu/nohz_full
: [https://docs.kernel.org/admin-guide/cgroup-v2.html#:~:text=cpuset.cpus.isolated /sys/fs/cgroup/cpuset.cpus.isolated]
: [https://docs.kernel.org/admin-guide/cgroup-v2.html#:~:text=Partition%20root%20without%20load%20balancing /sys/fs/cgroup/.../cpuset.cpus.partition]
: {{The Linux Kernel/include|linux/sched/isolation.h}}
:: {{The Linux Kernel/id|hk_type}} &amp;ndash; housekeeping type
:: {{The Linux Kernel/id|housekeeping_cpumask}} &amp;ndash; returns CPUs available for housekeeping of a given type
:: {{The Linux Kernel/id|cpu_is_isolated}}
: {{The Linux Kernel/include|linux/cpuset.h}} &amp;ndash; cpuset interface
: {{The Linux Kernel/man|7|cpuset}} &amp;ndash; confine processes to processor and memory node subsets


⚙️ Internals
: {{The Linux Kernel/id|CONFIG_CPU_ISOLATION}}
:: {{The Linux Kernel/source|kernel/sched/isolation.c}} &amp;ndash; housekeeping CPU management
::: {{The Linux Kernel/id|housekeeping_init}}, {{The Linux Kernel/id|housekeeping_update}}
: {{The Linux Kernel/id|CONFIG_CPUSETS}}
:: {{The Linux Kernel/source|kernel/cgroup/cpuset.c}} &amp;ndash; cpuset cgroup controller
::: {{The Linux Kernel/id|cpuset_init}}
::: {{The Linux Kernel/id|cpuset_init_smp}}
::: {{The Linux Kernel/id|isolated_cpus}}
::: {{The Linux Kernel/id|partition_xcpus_add}}, {{The Linux Kernel/id|partition_xcpus_del}}


📖 References
: {{The Linux Kernel/doc|CPU lists in command-line parameters|admin-guide/kernel-parameters.html#cpu-lists}}
:: [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=nohz_full= '''nohz_full'''] clears housekeeping.{{The Linux Kernel/id|cpumasks}} for tick, wq, timer, rcu, misc, and kthread in {{The Linux Kernel/id|housekeeping_nohz_full_setup}}
:: [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=isolcpus '''isolcpus'''] clears housekeeping.{{The Linux Kernel/id|cpumasks}} for [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=domain%20isolation domain] (by default), [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=nohz nohz], and [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=managed_irq managed_irq] in {{The Linux Kernel/id|housekeeping_isolcpus_setup}}
: {{The Linux Kernel/doc|Housekeeping|core-api/housekeeping.html}}
: {{The Linux Kernel/doc|NO_HZ: Reducing Scheduling-Clock Ticks|timers/no_hz.html}}
: {{The Linux Kernel/doc|CPUSETS of cgroup v2|admin-guide/cgroup-v2.html#cpuset}}
: {{The Linux Kernel/doc|CPUSETS of cgroup v1|admin-guide/cgroup-v1/cpusets.html}}


📚 Further reading
: [https://www.youtube.com/watch?v=1lomUhSS82s CPU Isolation state of the art, LPC'23]
: [https://lpc.events/event/19/contributions/2219/ CPU Isolation and IPI interference, LPC'25]
: [https://www.suse.com/c/cpu-isolation-introduction-part-1/ CPU Isolation]
: [https://lore.kernel.org/lkml/?q=isolcpus isolcpus @LKML]
: [https://lore.kernel.org/lkml/?q=housekeeping housekeeping @LKML]
: [https://kubernetes.io/docs/tasks/administer-cluster/reserve-compute-resources/#explicitly-reserved-cpu-list Explicitly Reserved CPU List, Kubernetes Documentation]
: [https://wiki.linuxfoundation.org/realtime/documentation/howto/tools/cpu-partitioning/start CPU Partitioning]
: {{The Linux Kernel/doc|Scheduler Domains|scheduler/sched-domains.html}} &amp;ndash; the Scheduler balances CPUs (scheduling groups) within a sched domain
: [https://lore.kernel.org/lkml/?q=nohz_full nohz_full @LKML]

💾 Historical since v7.0
: {{The Linux Kernel/id|cpuset_cpu_is_isolated}} &amp;ndash; removed, use {{The Linux Kernel/id|cpu_is_isolated}} instead

=== Runtime code patching ===

The kernel patches its own machine code at boot or runtime to optimize hot paths.
Static keys patch a {{w|NOP_(code)|NOP}} to a jump (or vice versa); static calls patch indirect calls to direct calls; alternatives replace instructions based on CPU features.

⚲ API
: {{The Linux Kernel/include|linux/jump_label.h}} &amp;ndash; static keys
:: {{The Linux Kernel/id|DEFINE_STATIC_KEY_FALSE}} &amp;ndash; define a key, initially false
:: {{The Linux Kernel/id|static_branch_unlikely}} &amp;ndash; zero-cost branch check (NOP when key is false)
:: {{The Linux Kernel/id|static_branch_enable}} &amp;ndash; patch all sites to take the branch (expensive, rare use)
: {{The Linux Kernel/include|linux/static_call.h}} &amp;ndash; static calls
:: {{The Linux Kernel/id|DEFINE_STATIC_CALL}} &amp;ndash; define a call site with initial target function
:: {{The Linux Kernel/id|static_call}} &amp;ndash; invoke the patched direct call
:: {{The Linux Kernel/id|static_call_update}} &amp;ndash; change target function, patch all sites
: {{The Linux Kernel/source|arch/x86/include/asm/alternative.h}} &amp;ndash; alternatives
:: {{The Linux Kernel/id|ALTERNATIVE}} &amp;ndash; replace instructions at boot based on CPU features
:: {{The Linux Kernel/source|arch/x86/include/asm/cpufeatures.h}} &amp;ndash; X86_FEATURE_* flags


⚙️ Internals
: {{The Linux Kernel/id|CONFIG_JUMP_LABEL}}
:: {{The Linux Kernel/source|kernel/jump_label.c}} &amp;ndash; static key patching core
:: {{The Linux Kernel/source|arch/x86/kernel/jump_label.c}} &amp;ndash; x86 static key patching
: {{The Linux Kernel/id|CONFIG_HAVE_STATIC_CALL}}
:: {{The Linux Kernel/source|kernel/static_call_inline.c}} &amp;ndash; static call core
:: {{The Linux Kernel/source|arch/x86/kernel/static_call.c}} &amp;ndash; x86 static call patching
: {{The Linux Kernel/source|arch/x86/include/asm/alternative.h}} &amp;ndash; runtime instruction patching
:: {{The Linux Kernel/source|arch/x86/kernel/alternative.c}} &amp;ndash; x86 alternatives engine
::: {{The Linux Kernel/id|smp_text_poke_single}} &amp;ndash; safely patch code on SMP using INT3 breakpoints; used by static keys, static calls, ftrace, kprobes
:::: {{The Linux Kernel/id|smp_text_poke_batch_add}}
:::: {{The Linux Kernel/id|smp_text_poke_batch_finish}}


👁 Examples
: {{The Linux Kernel/id|housekeeping_overridden}}
: {{The Linux Kernel/id|preempt_schedule}}
: tracepoints


📖 References
: {{The Linux Kernel/doc|Static Keys|staging/static-keys.html}}
: {{The Linux Kernel/doc|x86 CPU feature flags|arch/x86/cpuinfo.html}}


=== {{w|Memory barrier}}s ===

Memory barriers (MB) are synchronization mechanisms used to ensure proper ordering of memory operations in a SMP environment.
They play a crucial role in maintaining the consistency and correctness of data shared among different CPU cores or processors.
MBs prevent unexpected and potentially harmful reordering of memory access instructions by the compiler or CPU, which can lead to data corruption and race conditions in a concurrent software system.

⚲ API
: {{The Linux Kernel/man|2|membarrier}}
: {{The Linux Kernel/include|asm-generic/barrier.h}}
:: {{The Linux Kernel/id|mb}}, {{The Linux Kernel/id|rmb}}, {{The Linux Kernel/id|wmb}}
:: {{The Linux Kernel/id|smp_mb}}, {{The Linux Kernel/id|smp_rmb}}, {{The Linux Kernel/id|smp_wmb}}


⚙️ Internals

: {{The Linux Kernel/source|arch/x86/include/asm/barrier.h}} &amp;ndash; x86 memory barrier instructions
: {{The Linux Kernel/source|kernel/sched/membarrier.c}} &amp;ndash; membarrier system call


📖 References
: {{The Linux Kernel/doc|Memory barriers|core-api/wrappers/memory-barriers.html}}


=== States ===

C-states and P-states are features in modern CPUs designed to improve energy efficiency.

🗝️ Acronyms
: [https://uefi.org/htmlspecs/ACPI_Spec_6_4_html/08_Processor_Configuration_and_Control/processor-power-states.html C-states] &amp;ndash; CPU(?) states, aka idle states
: EPP &amp;ndash; {{The Linux Kernel/doc|Energy Performance Preference|admin-guide/pm/amd-pstate.html#energy-performance-preference-epp-rw}}
: HWP &amp;ndash; hardware-managed P-states, see [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=hwp_only hwp_only]
: [https://www.intel.com/content/www/us/en/docs/socwatch/user-guide/2020/p-state.html P-states] &amp;ndash; Performance states, see CPU Power and frequency scaling


⚲ API
: [https://linux.die.net/man/1/cpupower cpupower]


📖 References
: {{The Linux Kernel/doc|Working-State Power Management|admin-guide/pm/working-state.html}}
: https://lwn.net/Kernel/Index/#Power_management


==== Idle ====


C-states, {{w|ACPI#Processor_states|power states}}:
: C0 – operating, executing instructions.
: C1 (Halt) – internal {{w|Clock gating|clocks stopped}}.
: C1E (Enhanced Halt) – clocks stopped, voltage and frequency reduced.
: C2 (Stop-Clock) – internal and external {{w|Clock gating|clocks stopped}}.
: C3 (Deep Sleep) – clocks stopped, L1/L2 cache may flush, local APIC timer stops, requiring [[#Clock_infrastructure|tick broadcast]].
: C4 (Deeper Sleep) – voltage reduced.
: C6 (Deep Power Down) – state saved to SRAM, voltage can drop to 0V.
: C7 (Deeper Power Down) – C6 + L3 cache flushed.
: Modern Intel typically uses C1/C1E and C6, skipping C2–C5.
: ⚠️ ACPI state names (C1_ACPI, C2_ACPI, C3_ACPI) may not match actual hardware C-states. The [https://www.felixcloutier.com/x86/monitor:mwait MWAIT] hint reveals the real state: e.g. MWAIT 0x60 = hardware C6 may appear as &quot;C3_ACPI&quot;.


⚲ API
: turbostat --show CPU --quiet -n 1 --interval 0.1 --show sysfs
: [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=idle= idle=]
: /dev/cpu_dma_latency &amp;ndash; see {{The Linux Kernel/id|set_cpu_dma_latency}}
: C-states interfaces:
:: cpupower idle-info – show driver, governor, states with latency and residency
:: /sys/devices/system/cpu/cpuidle/
:: /sys/devices/system/cpu/cpu*/cpuidle/
::: cat /sys/devices/system/cpu/cpu0/cpuidle/state*/name – list available C-states
:: {{The Linux Kernel/include|linux/cpuidle.h}} – generic framework for CPU idle power management
: {{The Linux Kernel/include|linux/pm_qos.h}}


⚙️ Internals
: {{The Linux Kernel/source|drivers/cpuidle}} – CPU idle governors and drivers
: {{The Linux Kernel/source|drivers/idle/intel_idle.c}} – {{The Linux Kernel/doc|intel_idle|admin-guide/pm/intel_idle.html}}, hardcoded C-states per CPU model, modern Intel (C1/C1E/C6)
: {{The Linux Kernel/source|drivers/acpi/processor_idle.c}} – acpi_idle, reads C-states from ACPI tables, generic fallback (C1/C2/C3)
: {{The Linux Kernel/source|kernel/power/qos.c}} – PM quality of service
:: {{The Linux Kernel/id|cpu_latency_qos_miscdev}} – implementation of /dev/cpu_dma_latency


📖 References
:: {{The Linux Kernel/doc|CPU Idle Time Management|admin-guide/pm/cpuidle.html}}
: [https://www.intel.com/content/www/us/en/support/articles/000006619/processors/intel-core-processors.html Intel C-states reference]
: [https://support.hpe.com/hpesc/public/docDisplay?docId=sd00002067en_us&amp;page=GUID-855C475E-F9F9-460D-9475-B96DD982B587.html HPE C-states reference]


📚 Further reading
:: https://lwn.net/Kernel/Index/#Power_management-cpuidle
: {{The Linux Kernel/doc|PM Quality Of Service Interface|power/pm_qos_interface.html}}

==== Power and frequency ====


P-states, {{w|ACPI#Performance_state|performance states}}:
: P0 &amp;ndash; maximum power and frequency
: Pn &amp;ndash; less power and frequency
: ...


⚲ API
: Reliable measurement of actual CPU frequency
:: [https://manpages.debian.org/testing/linux-cpupower/turbostat.8.en.html turbostat] --quiet --show CPU,Bzy_MHz -n 1 --interval 0.1
::: Bzy_MHz &amp;ndash; average clock rate while the CPU was not idle (ie. in &quot;c0&quot; state).
: [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=intel_pstate intel_pstate=]
:: {{The Linux Kernel/doc|Kernel Command Line Options for intel_pstate|admin-guide/pm/intel_pstate.html#kernel-command-line-options-for-intel-pstate}}
: [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=cpufreq.default_governor cpufreq.default_governor=]
: P-states interfaces:
:: /sys/devices/system/cpu/cpufreq/
:: /sys/devices/system/cpu/cpu*/cpufreq/
::: scaling_cur_freq &amp;ndash; unreliable assumption on CPU frequency
:: /sys/devices/system/cpu/intel_pstate/
:: {{The Linux Kernel/include|linux/cpufreq.h}}
:: {{The Linux Kernel/include|linux/sched/cpufreq.h}} &amp;ndash; interface between cpufreq drivers and the scheduler


⚙️ Internals
: {{The Linux Kernel/source|drivers/cpufreq}} &amp;ndash; CPU frequency scaling drivers
:: {{The Linux Kernel/id|intel_pstate}}
:: {{The Linux Kernel/id|acpi_cpufreq_driver}}
: {{The Linux Kernel/source|kernel/sched/cpufreq_schedutil.c}} &amp;ndash; implementation of cpufreq.default_governor=schedutil
: {{The Linux Kernel/source|arch/x86/kernel/cpu/intel_epb.c}} &amp;ndash; Intel Performance and Energy Bias Hint support


📖 References
: {{The Linux Kernel/doc|CPU Performance Scaling|admin-guide/pm/cpufreq.html}}
: {{The Linux Kernel/doc|Device Frequency Scaling|driver-api/devfreq.html}}
: [https://www.kernel.org/doc/Documentation/cpu-freq/governors.txt CPUFreq Governor]
: {{The Linux Kernel/doc|CPUFreq - CPU frequency and voltage scaling|cpu-freq}}
: {{The Linux Kernel/doc|Intel Performance and Energy Bias Hint|admin-guide/pm/intel_epb.html}}
: {{The Linux Kernel/doc|intel_pstate CPU Performance Scaling Driver|admin-guide/pm/intel_pstate.html}}
:: {{The Linux Kernel/doc|General Information|admin-guide/pm/intel_pstate.html#general-information}} 
:: {{The Linux Kernel/doc|Operation Modes|admin-guide/pm/intel_pstate.html#operation-modes}} 
::: {{The Linux Kernel/doc|Active Mode|admin-guide/pm/intel_pstate.html#active-mode}}
&lt;!--
:::: {{The Linux Kernel/doc|Active Mode With HWP|admin-guide/pm/intel_pstate.html#active-mode-with-hwp}} 
::::: {{The Linux Kernel/doc|HWP + performance|admin-guide/pm/intel_pstate.html#hwp-performance}} 
::::: {{The Linux Kernel/doc|HWP + powersave|admin-guide/pm/intel_pstate.html#hwp-powersave}} 
:::: {{The Linux Kernel/doc|Active Mode Without HWP|admin-guide/pm/intel_pstate.html#active-mode-without-hwp}} 
::::: {{The Linux Kernel/doc|performance|admin-guide/pm/intel_pstate.html#performance}} 
::::: {{The Linux Kernel/doc|powersave|admin-guide/pm/intel_pstate.html#powersave}} 
--&gt;
::: {{The Linux Kernel/doc|Passive Mode|admin-guide/pm/intel_pstate.html#passive-mode}} 
:: {{The Linux Kernel/doc|Turbo P-states Support|admin-guide/pm/intel_pstate.html#turbo-p-states-support}} 
:: {{The Linux Kernel/doc|Processor Support|admin-guide/pm/intel_pstate.html#processor-support}} 
:: {{The Linux Kernel/doc|Support for Hybrid Processors|admin-guide/pm/intel_pstate.html#support-for-hybrid-processors}} 
::: {{The Linux Kernel/doc|Hybrid Processors with SMT|admin-guide/pm/intel_pstate.html#hybrid-processors-with-smt}} 
::: {{The Linux Kernel/doc|Capacity-Aware Scheduling Support|admin-guide/pm/intel_pstate.html#capacity-aware-scheduling-support}} 
::: {{The Linux Kernel/doc|Energy-Aware Scheduling Support|admin-guide/pm/intel_pstate.html#energy-aware-scheduling-support}} 
:: {{The Linux Kernel/doc|User Space Interface in sysfs|admin-guide/pm/intel_pstate.html#user-space-interface-in-sysfs}} 
::: {{The Linux Kernel/doc|Global Attributes|admin-guide/pm/intel_pstate.html#global-attributes}} 
::: {{The Linux Kernel/doc|Interpretation of Policy Attributes|admin-guide/pm/intel_pstate.html#interpretation-of-policy-attributes}} 
::: {{The Linux Kernel/doc|Coordination of P-State Limits|admin-guide/pm/intel_pstate.html#coordination-of-p-state-limits}} 
::: {{The Linux Kernel/doc|Energy vs Performance Hints|admin-guide/pm/intel_pstate.html#energy-vs-performance-hints}} 
:: {{The Linux Kernel/doc|intel_pstate vs acpi-cpufreq|admin-guide/pm/intel_pstate.html#intel-pstate-vs-acpi-cpufreq}} 
:: {{The Linux Kernel/doc|Kernel Command Line Options for intel_pstate|admin-guide/pm/intel_pstate.html#kernel-command-line-options-for-intel-pstate}} 
:: {{The Linux Kernel/doc|Diagnostics and Tuning|admin-guide/pm/intel_pstate.html#diagnostics-and-tuning}} 
::: {{The Linux Kernel/doc|Trace Events|admin-guide/pm/intel_pstate.html#trace-events}} 
::: {{The Linux Kernel/doc|ftrace|admin-guide/pm/intel_pstate.html#ftrace}} 
&lt;!-- end of intel_pstate.html --&gt;


📚 Further reading
: https://lwn.net/Kernel/Index/#Power_management-Frequency_scaling
: [https://wiki.archlinux.org/title/CPU_frequency_scaling CPU frequency scaling]
: {{The Linux Kernel/ltp|kernel/device-drivers|cpufreq}}
: [https://www.thinkwiki.org/wiki/How_to_use_cpufrequtils How to use cpufrequtils] 
:: [https://linux.die.net/man/1/cpufreq-info cpufreq-info]
:: [https://linux.die.net/man/1/cpufreq-set cpufreq-set]
: https://github.com/intel/power-optimization-library
: https://github.com/intel/kubernetes-power-manager

{{BookCat}}</text>
      <sha1>4cnh2xamlvbjprbg901i2o45nmyj9qy</sha1>
    </revision>
    <revision>
      <id>4656115</id>
      <parentid>4656113</parentid>
      <timestamp>2026-08-02T21:05:01Z</timestamp>
      <contributor>
        <username>Conan</username>
        <id>3188</id>
      </contributor>
      <minor />
      <comment>Not to be confused with</comment>
      <origin>4656115</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="56775" sha1="cek6cq50mn8a1h9aly9iypjps4talra" xml:space="preserve">&lt;noinclude&gt;{{DISPLAYTITLE:Interrupts and CPU}}&lt;/noinclude&gt;
== Interrupts ==
An {{w|interrupt}} is a signal to the processor emitted by hardware or software indicating an event that needs immediate attention.
An interrupt alerts the processor to a high-priority condition requiring the interruption of the current code the processor is executing.
The processor responds by suspending its current activities, saving its state, and executing a function called an ''interrupt handler'' (or an interrupt service routine, ISR) to deal with the event.
This interruption is temporary, and, after the interrupt handler finishes, the processor resumes normal activities.

There are two types of interrupts: hardware interrupts and software interrupts.
Hardware interrupts are used by devices to communicate that they require attention from the operating system.
For example, pressing a key on the keyboard or moving the mouse triggers hardware interrupts that cause the processor to read the keystroke or mouse position.
Unlike the software type, hardware interrupts are asynchronous and can occur in the middle of instruction execution, requiring additional care in programming.
The act of initiating a hardware interrupt is referred to as an ''interrupt request'' - IRQ ↪ {{w|Interrupt descriptor table|IDT}} ↪ {{The Linux Kernel/id|common_interrupt}} on x86.

A software interrupt is caused either by an exceptional condition in the processor itself, or a special instruction in the instruction set which causes an interrupt when it is executed.
The former is often called a ''{{w|Trap (computing)|trap}}'' (⚙️ {{The Linux Kernel/id|do_trap}}) or ''exception'' and is used for errors or events occurring during program execution that are exceptional enough that they cannot be handled within the program itself.
For example, if the processor's arithmetic logic unit is commanded to divide a number by zero, this impossible demand will cause a ''divide-by-zero exception'' (⚙️ {{The Linux Kernel/id|X86_TRAP_DE}}), perhaps causing the computer to abandon the calculation or display an error message.
Software interrupt instructions function similarly to subroutine calls and are used for a variety of purposes, such as to request services from low-level system software such as device drivers.
For example, computers often use software interrupt instructions to communicate with the disk controller to request data be read or written to the disk.

Each interrupt has its own interrupt handler.  The number of hardware interrupts is limited by the number of interrupt request (IRQ) lines to the processor, but there may be hundreds of different software interrupts.


⚲ API

: /proc/interrupts
: {{The Linux Kernel/man|1|irqtop}} &amp;ndash; utility to display kernel interrupt information
: [https://github.com/Irqbalance/irqbalance irqbalance] &amp;ndash; distribute hardware interrupts across processors on a multiprocessor system
: There are many ways to request ISR, two of them
: {{The Linux Kernel/id|devm_request_threaded_irq}} &amp;ndash; preferable, managed device with threaded ISR
: {{The Linux Kernel/id|devm_request_irq}} &amp;ndash; managed version
:: {{The Linux Kernel/id|request_irq}}
::: {{The Linux Kernel/id|request_threaded_irq}}
: {{The Linux Kernel/id|free_irq}}
: {{The Linux Kernel/include|linux/interrupt.h}} &amp;ndash; main interrupt support header
:: {{The Linux Kernel/id|irqaction}} &amp;ndash; contains handler functions 
: {{The Linux Kernel/include|linux/irq.h}}
:: {{The Linux Kernel/id|irq_data}}
: {{The Linux Kernel/include|linux/irqflags.h}}
:: {{The Linux Kernel/id|irqs_disabled}}
:: {{The Linux Kernel/id|local_irq_save}} ...
:: {{The Linux Kernel/id|local_irq_disable}} ...
: {{The Linux Kernel/include|linux/irqdesc.h}}
:: {{The Linux Kernel/id|irq_desc}}
: {{The Linux Kernel/include|linux/irqdomain.h}}
:: {{The Linux Kernel/id|irq_domain}} &amp;ndash; hardware interrupt number translation object
:: {{The Linux Kernel/id|irq_domain_get_irq_data}}
: {{The Linux Kernel/include|linux/msi.h}} &amp;ndash; {{w|Message Signaled Interrupts}}
:: {{The Linux Kernel/id|msi_desc}}
: Structure of structures:
:: {{The Linux Kernel/id|irq_desc}} is container of
::: {{The Linux Kernel/id|irq_data}}
:::: irq &amp;ndash; interrupt number
::: {{The Linux Kernel/id|irq_common_data}}
::: list of {{The Linux Kernel/id|irqaction}}


⚙️ Internals

: {{The Linux Kernel/source|kernel/irq/settings.h}} &amp;ndash; IRQ descriptor status flags
: {{The Linux Kernel/source|kernel/irq}} &amp;ndash; generic IRQ handling
:: {{The Linux Kernel/source|kernel/irq/internals.h}} &amp;ndash; IRQ subsystem internal functions
: ls /sys/kernel/debug/irq/domains/
:: {{The Linux Kernel/id|x86_vector_domain}}, {{The Linux Kernel/id|x86_vector_domain_ops}}
: {{The Linux Kernel/id|irq_chip}}
: {{The Linux Kernel/id|load_idt}} &amp;ndash; load Interrupt Descriptor Table
: {{The Linux Kernel/source|arch/x86/include/asm/idtentry.h}} &amp;ndash; interrupt entry/exit definitions
: {{The Linux Kernel/source|arch/x86/include/asm/hw_irq.h}} &amp;ndash; x86 hardware IRQ definitions
:: {{The Linux Kernel/id|irq_entries_start}} &amp;ndash; hardware IRQ entry stubs
: {{The Linux Kernel/source|arch/x86/kernel/irq.c}} &amp;ndash; x86 interrupt handling
:: {{The Linux Kernel/id|common_interrupt}} &amp;ndash; handles all normal device IRQs on x86
: {{The Linux Kernel/source|arch/x86/kernel/apic}} &amp;ndash; {{w|Advanced Programmable Interrupt Controller|APIC}}
:: {{The Linux Kernel/source|arch/x86/kernel/apic/apic.c}} &amp;ndash; local APIC core (timer, calibration, spurious interrupt)
:: {{The Linux Kernel/source|arch/x86/kernel/apic/io_apic.c}} &amp;ndash; {{w|IOAPIC|I/O APIC}}, routes device IRQs to CPUs
:: {{The Linux Kernel/source|arch/x86/kernel/apic/x2apic_cluster.c}} &amp;ndash; {{w|x2APIC}} (&gt;256 CPUs)
:: {{The Linux Kernel/source|arch/x86/kernel/apic/ipi.c}} &amp;ndash; {{w|Inter-processor interrupt|IPI}}, see [[#IPI|IPI]]
:: {{The Linux Kernel/source|arch/x86/kernel/apic/hw_nmi.c}} &amp;ndash; hardware NMI watchdog via APIC
:: {{The Linux Kernel/source|arch/x86/kernel/apic/vector.c}} &amp;ndash; IRQ vector allocation
:: {{The Linux Kernel/source|arch/x86/kernel/apic/msi.c}} &amp;ndash; {{w|Message Signaled Interrupts|MSI}} via APIC

📖 References
: {{The Linux Kernel/doc|IRQs|core-api/irq}}
:: {{The Linux Kernel/doc|The irq_domain interrupt number mapping library|core-api/irq/irq-domain.html}}
: {{The Linux Kernel/doc|Linux generic IRQ handling|core-api/genericirq.html}}
: {{The Linux Kernel/doc|Message Signaled Interrupts: The MSI Driver Guide|PCI/msi-howto.html}}
: {{The Linux Kernel/doc|Lock types and their rules|locking/locktypes.html}}
: {{The Linux Kernel/doc|Hard IRQ Context|kernel-hacking/locking.html#hard-irq-context}}
: [https://0xax.gitbooks.io/linux-insides/content/Interrupts/ Interrupts]


👁 Examples
: {{The Linux Kernel/id|dummy_irq_chip}} &amp;ndash; dummy interrupt chip implementation
: {{The Linux Kernel/source|lib/locking-selftest.c}} &amp;ndash; locking correctness self-tests


=== IRQ affinity ===

⚲ API
: /proc/irq/default_smp_affinity
: /proc/irq/*/smp_affinity and /proc/irq/*/smp_affinity_list


Common types and functions:
: struct {{The Linux Kernel/id|irq_affinity}} &amp;ndash; description for automatic irq affinity assignments, see {{The Linux Kernel/id|devm_platform_get_irqs_affinity}}
: struct {{The Linux Kernel/id|irq_affinity_desc}} &amp;ndash; interrupt affinity descriptor, see {{The Linux Kernel/id|irq_update_affinity_desc}}, {{The Linux Kernel/id|irq_create_affinity_masks}}
: {{The Linux Kernel/id|irq_set_affinity}}
: {{The Linux Kernel/id|irq_get_affinity_mask}} 
: {{The Linux Kernel/id|irq_can_set_affinity}}
: {{The Linux Kernel/id|irq_set_affinity_hint}} 
: {{The Linux Kernel/id|irqd_affinity_is_managed}} 
: {{The Linux Kernel/id|irq_data_get_affinity_mask}}
: {{The Linux Kernel/id|irq_data_get_effective_affinity_mask}} 
: {{The Linux Kernel/id|irq_data_update_effective_affinity}} 
: {{The Linux Kernel/id|irq_set_affinity_notifier}} 
: {{The Linux Kernel/id|irq_affinity_notify}} 
: {{The Linux Kernel/id|irq_chip_set_affinity_parent}} 
: {{The Linux Kernel/id|irq_set_vcpu_affinity}}


🛠️ Utilities
: [https://man.archlinux.org/man/extra/irqbalance/irqbalance.1.en irqbalance] – distributes hardware interrupts across CPUs


📖 References
: {{The Linux Kernel/doc|SMP IRQ affinity|core-api/irq/irq-affinity.html}}
: [https://wiki.linuxfoundation.org/realtime/documentation/howto/tools/cpu-partitioning/start#irq_affinity IRQ affinity, LF]
: [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=managed_irq managed_irq kernel parameter], [https://lore.kernel.org/lkml/?q=managed_irq @LKML]
: [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=irqaffinity= irqaffinity kernel parameter], [https://lore.kernel.org/lkml/?q=irqaffinity @LKML]


=== Non-maskable interrupts ===

⚲ API
: {{The Linux Kernel/include|linux/nmi.h}}
:: {{The Linux Kernel/id|in_nmi}}
:: {{The Linux Kernel/id|touch_nmi_watchdog}}
:: ...
: {{The Linux Kernel/include|trace/events/nmi.h}}
: {{The Linux Kernel/source|arch/x86/include/asm/nmi.h}} &amp;ndash; x86 NMI handler registration
:: {{The Linux Kernel/id|register_nmi_handler}}
:: {{The Linux Kernel/id|unregister_nmi_handler}}


⚙️ Internals
: {{The Linux Kernel/source|arch/x86/kernel/nmi.c}} &amp;ndash; x86 NMI handler
: {{The Linux Kernel/source|arch/x86/kernel/apic/hw_nmi.c}} &amp;ndash; hardware NMI watchdog via APIC
: {{The Linux Kernel/source|arch/x86/kernel/nmi_selftest.c}} &amp;ndash; NMI IPI self-tests


📖 References
: {{The Linux Kernel/doc|NMI Trace Events|trace/events-nmi.html}}


📚 Further reading
: [https://0xax.gitbooks.io/linux-insides/content/Interrupts/linux-interrupts-6.html Non-maskable interrupt handler] (NMI)


=== ... ===

📚 Further reading about interrupts
: IDT &amp;ndash; {{w|Interrupt descriptor table}}
: [https://www.felixcloutier.com/x86/lgdt:lidt LGDT/LIDT &amp;ndash; Load Global/Interrupt Descriptor Table Register] asm instruction

== Deferred works ==

=== Scheduler context ===

==== kthread work ====

This framework simplifies the use of kernel kthreads.
A {{The Linux Kernel/id|kthread_work}} item can be queued with {{The Linux Kernel/id|kthread_queue_work}} and flushed using {{The Linux Kernel/id|kthread_flush_work}}.
All queued kthread_work items are processed by a dedicated kernel thread executing the {{The Linux Kernel/id|kthread_worker_fn}} function.

⚲ API
: {{The Linux Kernel/id|kthread_work}} &amp;ndash; contains {{The Linux Kernel/id|kthread_work_func_t}} to execute
:: {{The Linux Kernel/id|kthread_init_work}}
:: {{The Linux Kernel/id|kthread_flush_work}}
: {{The Linux Kernel/id|kthread_worker}} &amp;ndash; links a kthread_work and a task
:: {{The Linux Kernel/id|kthread_run_worker}} &amp;ndash; creates and wakes a kthread worker
::: {{The Linux Kernel/id|kthread_create_worker}}
::: {{The Linux Kernel/id|kthread_flush_worker}}
:: {{The Linux Kernel/id|kthread_destroy_worker}}
: {{The Linux Kernel/id|kthread_queue_work}} &amp;ndash; queues a kthread_work on a kthread_worker


⚙️ Internals
: {{The Linux Kernel/id|__kthread_create_worker_on_node}}
: {{The Linux Kernel/id|kthread_worker_fn}} &amp;ndash; executes work's function


👁 Example usages
: {{The Linux Kernel/id|watchdog_kworker}}, {{The Linux Kernel/id|pwq_release_worker}}, {{The Linux Kernel/id|pump_messages}}

==== Threaded IRQ ====

⚲ API
{{The Linux Kernel/id|devm_request_threaded_irq}}, {{The Linux Kernel/id|request_threaded_irq}}
ISR should return IRQ_WAKE_THREAD to run thread function

⚙️ Internals
: {{The Linux Kernel/id|setup_irq_thread}}, {{The Linux Kernel/id|irq_thread}}
: {{The Linux Kernel/source|kernel/irq/manage.c}} &amp;ndash; IRQ request, free and affinity management

📖 References
: {{The Linux Kernel/doc|request_threaded_irq|core-api/genericirq.html#c.request_threaded_irq}}


==== Work and workqueue ====

Generic async execution with shared worker pool.

⚲ API
: {{The Linux Kernel/id|PF_WQ_WORKER}} &amp;ndash; workqueue worker process flag
: {{The Linux Kernel/include|linux/workqueue.h}}, {{The Linux Kernel/include|linux/workqueue_types.h}}
: {{The Linux Kernel/id|work_struct}}, {{The Linux Kernel/id|INIT_WORK}}
: {{The Linux Kernel/id|delayed_work}}, {{The Linux Kernel/id|INIT_DELAYED_WORK}}, {{The Linux Kernel/id|cancel_delayed_work_sync}}
: {{The Linux Kernel/id|workqueue_struct}}
:: {{The Linux Kernel/id|devm_alloc_workqueue}}
::: {{The Linux Kernel/id|alloc_workqueue}}
:: {{The Linux Kernel/id|destroy_workqueue}}
: {{The Linux Kernel/id|schedule_work}} &amp;ndash; queues work on the system workqueue ↯
:: {{The Linux Kernel/id|queue_work}} &amp;ndash; queues work on a workqueue
::: {{The Linux Kernel/id|queue_work_on}} &amp;ndash; on a specific CPU
: {{The Linux Kernel/id|show_all_workqueues}}
:: {{The Linux Kernel/id|show_one_workqueue}}
: {{The Linux Kernel/id|system_power_efficient_wq}} ...


👁 Example usage {{The Linux Kernel/source|samples/ftrace/sample-trace-array.c}}


⚙️ Internals
: {{The Linux Kernel/source|kernel/workqueue.c}} &amp;ndash; generic async execution with shared worker pool
:: {{The Linux Kernel/id|workqueue_init}}
::: {{The Linux Kernel/id|create_worker}}
:::: {{The Linux Kernel/id|worker_thread}}
::::: {{The Linux Kernel/id|process_one_work}}
:: {{The Linux Kernel/id|format_worker_id}} &amp;ndash; names kworker kthreads
:: {{The Linux Kernel/id|pool_workqueue}}
::: {{The Linux Kernel/id|worker_pool}}


📖 References
: {{The Linux Kernel/doc|Concurrency Managed Workqueue|core-api/workqueue.html}}
: [https://sysprog21.github.io/lkmpg/#work-queues LKMPG: Work queues]

=== Interrupt context ===

: {{The Linux Kernel/include|linux/irq_work.h}} &amp;ndash; run callbacks from hardirq or NMI context where normal work queues can't be used
:: {{The Linux Kernel/id|irq_work_queue}} &amp;ndash; enqueue work on the current CPU, triggers {{The Linux Kernel/id|IRQ_WORK_VECTOR}} IPI if needed
:: {{The Linux Kernel/id|irq_work_sync}} &amp;ndash; wait for completion
:: {{The Linux Kernel/source|kernel/irq_work.c}} &amp;ndash; irq_work implementation
:: 👁 {{The Linux Kernel/source|samples/trace_printk/trace-printk.c}}

==== Timers ====

⚠️ Not to be confused with
[[The_Linux_Kernel/Multitasking#POSIX_Timers|POSIX timer]] – userspace API,
[[The_Linux_Kernel/Debugging#Watchdogs|watchdog timer]] – hang detection,
[[#Clock_infrastructure|local APIC timer]] – per-CPU hardware, drives the tick.

===== softirq timer =====

This timer is a softirq for periodical tasks with jiffies resolution

⚲ API
: {{The Linux Kernel/include|linux/timer.h}}
: {{The Linux Kernel/id|timer_list}}, {{The Linux Kernel/id|DEFINE_TIMER}}, {{The Linux Kernel/id|timer_setup}}
: {{The Linux Kernel/id|mod_timer}} &amp;mdash; sets expiration time in jiffies. 
: {{The Linux Kernel/id|del_timer}}


⚙️ Internals
: {{The Linux Kernel/source|kernel/time/timer.c}} &amp;ndash; kernel internal timers
:: {{The Linux Kernel/id|timer_bases}}


👁 Examples
: {{The Linux Kernel/id|input_enable_softrepeat}} and {{The Linux Kernel/id|input_start_autorepeat}}


📚 References
: {{The Linux Kernel/doc|Time and timer routines|driver-api/basics.html#time-and-timer-routines}}
:: {{The Linux Kernel/doc|mod_timer_pending ... |driver-api/basics.html#c.mod_timer_pending}}

===== High-resolution timer =====

⚲ API
: /proc/timer_list
: /proc/sys/kernel/timer_migration
: {{The Linux Kernel/include|linux/hrtimer_defs.h}}
: {{The Linux Kernel/include|linux/hrtimer.h}}
: {{The Linux Kernel/id|hrtimer}}, hrtimer.function &amp;mdash; callback
: {{The Linux Kernel/id|hrtimer_init}}
: {{The Linux Kernel/id|hrtimer_setup}}
: {{The Linux Kernel/id|hrtimer_start}} &amp;mdash; starts a timer with nanosecond resolution 
: {{The Linux Kernel/id|hrtimer_cancel}}


👁 Examples {{The Linux Kernel/id|alarm_init}}, {{The Linux Kernel/id|watchdog_enable}}


⚙️ Internals
: {{The Linux Kernel/id|CONFIG_HIGH_RES_TIMERS}}
: {{The Linux Kernel/source|kernel/time/tick-internal.h}} &amp;ndash; tick and timer internal definitions
:: {{The Linux Kernel/id|hrtimer_bases}}
: {{The Linux Kernel/source|kernel/time/hrtimer.c}} &amp;ndash; high-resolution timer implementation
: {{The Linux Kernel/source|kernel/time/itimer.c}} &amp;ndash; interval timers
: {{The Linux Kernel/source|kernel/time/timer_list.c}} &amp;ndash; /proc/timer_list debugfs


📚 HR timers references
: {{The Linux Kernel/doc|High-resolution timers|driver-api/basics.html#high-resolution-timers}}
: {{The Linux Kernel/doc|hrtimers - subsystem for high-resolution kernel timers|timers/hrtimers.html}}
: {{The Linux Kernel/doc|high resolution timers and dynamic ticks design notes|timers/highres.html}}

===== Tick and NO_HZ =====

The tick is the periodic timer interrupt that drives scheduling, timekeeping, and RCU.
The NO_HZ subsystem reduces or eliminates tick interrupts to save power and reduce latency.

⚲ API
: /sys/devices/system/cpu/nohz_full – active nohz_full CPUs
: [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=nohz_full= nohz_full=] boot parameter – list of CPUs to run tickless
: {{The Linux Kernel/include|linux/tick.h}} – tick control API
:: {{The Linux Kernel/id|tick_nohz_full_running}} – true if any CPU runs tickless

🪛 Compile-time configurations ({{The Linux Kernel/source|kernel/time/Kconfig}})
: {{The Linux Kernel/id|CONFIG_HZ_PERIODIC}} – constant-rate tick, always firing
: {{The Linux Kernel/id|CONFIG_NO_HZ_IDLE}} – stop tick when CPU is idle (default on most distros)
: {{The Linux Kernel/id|CONFIG_NO_HZ_FULL}} – stop tick even when running a single task, for RT and latency-sensitive workloads, see [[#CPU_isolation|CPU isolation]]

⚙️ Internals
: {{The Linux Kernel/source|kernel/time/tick-common.c}} – periodic tick setup
: {{The Linux Kernel/source|kernel/time/tick-oneshot.c}} – oneshot mode for hrtimers and NO_HZ
: {{The Linux Kernel/source|kernel/time/tick-sched.c}} – NO_HZ tick scheduling logic
: {{The Linux Kernel/source|kernel/time/tick-broadcast.c}} – broadcast tick for CPUs in deep idle where local timer stops ([[#Idle|C3+]])
: {{The Linux Kernel/source|kernel/time/timer_migration.c}} – migrate timers from idle to busy CPUs

📖 References
: {{The Linux Kernel/doc|NO_HZ: Reducing Scheduling-Clock Ticks|timers/no_hz.html}}
: [https://wiki.linuxfoundation.org/realtime/documentation/howto/tools/ticklesskernel Tickless kernel, RT wiki]
: {{The Linux Kernel/doc|high resolution timers and dynamic ticks design notes|timers/highres.html}}

===== Clock infrastructure =====

⚠️ Not to be confused with
[[The_Linux_Kernel/System#Hardware_Device_Drivers|drivers/clk framework]] – SoC {{w|Clock signal|clock}} tree management.

Clocksources read current time (passive counters).
Clock event devices fire interrupts at a programmed time (active).
Together they are the foundation for timekeeping, timers, tick, and NO_HZ.


⚲ Clocksources – &quot;what time is it?&quot;
: /sys/devices/system/clocksource/clocksource0/current_clocksource
: /sys/devices/system/clocksource/clocksource0/available_clocksource
:: {{w|Time Stamp Counter|TSC}} – fastest, per-CPU, x86
:: {{w|High Precision Event Timer|HPET}} – system-wide, MMIO
:: ACPI PM timer – never stops in any C-state, slow
: {{The Linux Kernel/include|linux/clocksource.h}} – {{The Linux Kernel/id|clocksource}}, {{The Linux Kernel/id|clocksource_register_hz}}


⚲ Clock event devices – &quot;wake me at time X&quot;
: {{The Linux Kernel/include|linux/clockchips.h}} – {{The Linux Kernel/id|clock_event_device}}, {{The Linux Kernel/id|clockevents_config_and_register}}
: Local {{w|Advanced Programmable Interrupt Controller|APIC}} timer – per-CPU, fastest, stops in [[#Idle|C3+]], {{The Linux Kernel/id|local_apic_timer_interrupt}}
: {{w|High Precision Event Timer|HPET}} – system-wide, used as broadcast fallback
&lt;!-- PIT (i8254) – legacy, stopped at boot on modern hardware --&gt;


⚙️ Internals
: {{The Linux Kernel/source|kernel/time/clocksource.c}} – clocksource selection and watchdog
: {{The Linux Kernel/source|kernel/time/clockevents.c}} – clock event device framework
: {{The Linux Kernel/source|kernel/time/jiffies.c}} – jiffies clocksource (fallback)


===== ... =====

📖 Timers references
: {{The Linux Kernel/doc|Timers|timers}}
: [https://lwn.net/Articles/913568/ Better CPU selection for timer expiration]

==== Tasklet ====

tasklet is a softirq, for time critical operations

⚲ API is deprecated in favor of threaded IRQs: {{The Linux Kernel/id|devm_request_threaded_irq}}
: {{The Linux Kernel/id|tasklet_struct}}, {{The Linux Kernel/id|tasklet_init}}, {{The Linux Kernel/id|tasklet_schedule}} 


⚙️ Internals: {{The Linux Kernel/id|tasklet_action_common}} HI_SOFTIRQ, TASKLET_SOFTIRQ


==== Softirq ====

softirq is internal system facility and should not be used directly.
Use tasklet or threaded IRQs

⚲ API
: {{The Linux Kernel/include|linux/interrupt.h}}
: cat /proc/softirqs
: {{The Linux Kernel/id|open_softirq}} registers {{The Linux Kernel/id|softirq_action}}
: {{The Linux Kernel/id|raise_softirq}}
: {{The Linux Kernel/id|tasklet_schedule}}
:: {{The Linux Kernel/id|__tasklet_schedule}}


⚙️ Internals
: {{The Linux Kernel/source|kernel/softirq.c}} &amp;ndash; software interrupt handling
:: {{The Linux Kernel/id|__do_softirq}} &amp;ndash; main softirq processing loop


📖 References
: [https://0xax.gitbooks.io/linux-insides/content/Interrupts/linux-interrupts-9.html Introduction to deferred interrupts (Softirq, Tasklets and Workqueues)]
: [https://0xax.gitbooks.io/linux-insides/content/Timers/ Timers and time management]
: [https://linux-kernel-labs.github.io/refs/heads/master/labs/deferred_work.html Deferred work, linux-kernel-labs]
: [https://www.oreilly.com/library/view/linux-device-drivers/0596005903/ch07.html Chapter 7. Time, Delays, and Deferred Work]

==CPU specific==


🖱️ GUI
: [https://manpages.ubuntu.com/manpages/kinetic/en/man8/tuna.8.html tuna] &amp;ndash; program for tuning running processes


⚲ API
: cat /proc/cpuinfo
: /sys/devices/system/cpu/
: /sys/devices/system/node/
: /sys/cpu/
: /sys/fs/cgroup/cpu/
: grep -i cpu /proc/self/status
: [https://manpages.ubuntu.com/manpages/jammy/man1/rdmsr.1.html rdmsr] &amp;ndash; tool for reading CPU machine specific registers (MSR)
: {{The Linux Kernel/man|1|lscpu}} &amp;ndash; display information about the CPU architecture

: {{The Linux Kernel/include|linux/arch_topology.h}} &amp;ndash; arch specific cpu topology information 
: {{The Linux Kernel/include|linux/cpu.h}} &amp;ndash; generic cpu definition 
: {{The Linux Kernel/include|linux/cpu_cooling.h}} 
: {{The Linux Kernel/include|linux/cpu_pm.h}} 
: {{The Linux Kernel/include|linux/cpufeature.h}}
: {{The Linux Kernel/source|arch/x86/include/asm/cpufeature.h}} &amp;ndash; x86 CPU feature detection
: {{The Linux Kernel/include|linux/peci-cpu.h}} 
: {{The Linux Kernel/include|linux/sched/cputime.h}} &amp;ndash; cputime accounting APIs
: {{The Linux Kernel/include|linux/clk.h}} &amp;ndash; interfaces for managing hardware clocks in device drivers


⚙️ Internals

: {{The Linux Kernel/source|drivers/base/cpu.c}} &amp;ndash; CPU driver model subsystem
:: {{The Linux Kernel/id|cpu_dev_init}}


=== Cache ===

: {{The Linux Kernel/include|linux/cacheflush.h}}
:: {{The Linux Kernel/source|arch/x86/include/asm/cacheflush.h}}: {{The Linux Kernel/id|clflush_cache_range}}
: {{The Linux Kernel/include|linux/cache.h}} &amp;ndash; cache line alignment macros
:: {{The Linux Kernel/id|____cacheline_aligned}} &amp;ndash; align to cache line boundary to avoid false sharing
:: {{The Linux Kernel/id|__cacheline_aligned}} &amp;ndash; same, plus place in .data..cacheline_aligned section
:: {{The Linux Kernel/id|____cacheline_aligned_in_smp}} &amp;ndash; same, but no-op on uniprocessor builds
:: {{The Linux Kernel/id|__read_mostly}} &amp;ndash; place in a cache-friendly section for rarely written data
:: {{The Linux Kernel/id|__ro_after_init}} &amp;ndash; writable during init, read-only after boot (security hardening)
:: {{The Linux Kernel/id|DEFINE_PER_CPU_CACHE_HOT}} &amp;ndash; per-CPU variable in .data..hot section, used for {{The Linux Kernel/id|current_task}}, {{The Linux Kernel/id|__preempt_count}}
:: {{The Linux Kernel/id|L1_CACHE_BYTES}}, {{The Linux Kernel/id|SMP_CACHE_BYTES}} &amp;ndash; 64 bytes typically
:: {{The Linux Kernel/source|arch/x86/include/asm/cache.h}} &amp;ndash; x86 cache line size definitions

🔨 [https://manpages.ubuntu.com/manpages/resolute/man1/stress-ng.1.html#:~:text=%2D%2Dcache stress-ng --cache]

⚙️ Internals

: {{The Linux Kernel/source|arch/x86/mm/pat/set_memory.c}} &amp;ndash; page attribute table memory type control
: {{The Linux Kernel/source|arch/x86/kernel/cpu/mtrr/}} &amp;ndash; memory type range register driver

📚 Further reading
: MTRR &amp;ndash; {{w|Memory type range register}}
: {{w|CPU cache}}

=== {{w|Symmetric_multiprocessing|SMP}} ===

This chapter is about multiprocessing and {{w|Multi-core processor|multi-core}} aspects of Linux kernel.

Key concepts and features of Linux SMP include:
* Symmetry: In an SMP system, all processors are considered the same without hardware hierarchy in contradiction to use of {{w|coprocessor}}s.
* Load balancing: The Linux kernel employs load balancing mechanisms to distribute tasks evenly among available CPU cores. This prevents any one core from becoming overwhelmed while others remain underutilized.
* Parallelism: SMP enables parallel processing, where multiple threads or processes can execute simultaneously on different CPU cores. This can significantly improve the execution speed of applications that are designed to take advantage of multiple threads.
* Thread scheduling: The Linux kernel scheduler is responsible for determining which threads or processes run on which CPU cores and for how long. It aims to optimize performance by minimizing contention and maximizing CPU utilization.
* Shared memory: In an SMP system, all CPU cores typically share the same physical memory space. This allows processes and threads running on different cores to communicate and share data more efficiently.
* NUMA &amp;ndash; {{w|Non-Uniform Memory Access}}: In larger SMP systems, memory access times might not be uniform due to the physical arrangement of memory banks and processors. Linux has mechanisms to handle NUMA architectures efficiently, allowing processes to be scheduled on CPUs closer to their associated memory.
* Cache coherency: SMP systems require mechanisms to ensure that all CPU cores have consistent views of memory. Cache coherency protocols ensure that changes made to shared memory locations are correctly propagated to all cores.
* Scalability: SMP systems can be scaled up to include more CPU cores, enhancing the overall computing power of the system. However, as the number of cores increases, challenges related to memory access, contention, and communication between cores may arise.
* Kernel and user space: Linux applications running in user space can take advantage of SMP without needing to be aware of the underlying hardware details. The kernel handles the management of CPU cores and resource allocation.


⚲ API
: &lt;code&gt;ps -PLe&lt;/code&gt; &amp;ndash; lists threads with processor that the thread last executed on (the third column PSR).
: {{The Linux Kernel/man|2|getcpu}} &amp;ndash; determine CPU and NUMA node on which the calling thread is running
: {{The Linux Kernel/man|8|chcpu}} &amp;ndash; configure CPUs
: {{The Linux Kernel/man|3|CPU_SET}} &amp;ndash; macros for manipulating CPU sets
: {{The Linux Kernel/include|linux/smp.h}}
:: The most commonly used functions:
:: {{The Linux Kernel/id|crash_smp_send_stop}} – halts all CPUs except the calling one in a crash context
:: {{The Linux Kernel/id|get_cpu}} – disables preemption and returns the current processor ID
:: {{The Linux Kernel/id|panic_smp_self_stop}} – stops the local CPU during a panic while ensuring others halt
:: {{The Linux Kernel/id|put_cpu}} – re-enables preemption after a previous get_cpu call
:: {{The Linux Kernel/id|raw_smp_processor_id}} – returns the current CPU ID without preemption safety
:: {{The Linux Kernel/id|setup_max_cpus}} – sets up the maximum number of CPUs to be brought online
:: {{The Linux Kernel/id|smp_init}} – initializes core SMP structures and state during boot
:: {{The Linux Kernel/id|smp_prepare_boot_cpu}} – prepares the boot CPU during early SMP initialization
:: {{The Linux Kernel/id|smp_prepare_cpus}} – prepares all CPUs for booting before secondary CPUs are started
:: {{The Linux Kernel/id|smp_processor_id}} – returns the ID of the current CPU with preemption checks
:: {{The Linux Kernel/id|smp_send_stop}} – stops all other CPUs in response to critical events
:: {{The Linux Kernel/id|wake_up_all_idle_cpus}} – wakes all idle CPUs to ensure prompt task execution
: {{The Linux Kernel/include|linux/cpu.h}}
: {{The Linux Kernel/include|linux/group_cpus.h}}: {{The Linux Kernel/id|group_cpus_evenly}} &amp;ndash; groups all CPUs evenly per NUMA/CPU locality
: {{The Linux Kernel/include|asm-generic/percpu.h}}
: {{The Linux Kernel/include|linux/percpu-defs.h}} &amp;ndash; basic definitions for percpu areas
:: {{The Linux Kernel/id|this_cpu_ptr}}
: {{The Linux Kernel/include|linux/percpu.h}} 
: {{The Linux Kernel/include|linux/percpu-refcount.h}} 
: {{The Linux Kernel/include|linux/percpu-rwsem.h}}
: {{The Linux Kernel/include|linux/preempt.h}}
:: {{The Linux Kernel/id|migrate_disable}}, {{The Linux Kernel/id|migrate_enable}}
: /sys/bus/cpu
: [[#per_CPU_local_lock|per CPU local_lock]]
: {{The Linux Kernel/include|linux/topology.h}} &amp;ndash; {{The Linux Kernel/id|cpu_to_node}}, {{The Linux Kernel/id|numa_node_id}}
: {{The Linux Kernel/source|arch/x86/include/asm/topology.h}} &amp;ndash; x86 NUMA and CPU topology
: See also [[../../Memory#NUMA|NUMA memory section]]


⚙️ Internals
: {{The Linux Kernel/id|boot_cpu_init}} activates the first CPU
: {{The Linux Kernel/id|smp_prepare_cpus}} initializes rest CPUs during boot
: {{The Linux Kernel/id|cpu_number}}
: {{The Linux Kernel/id|CONFIG_SMP}}
:: {{The Linux Kernel/id|CONFIG_NUMA}}
: {{The Linux Kernel/include|trace/events/percpu.h}}
: {{The Linux Kernel/file|drivers/base/cpu.c}} &amp;ndash; CPU driver model subsystem support
: {{The Linux Kernel/file|kernel/cpu.c}} &amp;ndash; CPU hotplug state machine
: smpboot
:: {{The Linux Kernel/include|linux/smpboot.h}}
:: {{The Linux Kernel/source|kernel/smpboot.c}} &amp;ndash; common SMP CPU bringup/teardown
:: {{The Linux Kernel/source|arch/x86/kernel/smpboot.c}} &amp;ndash; x86 SMP booting
: {{The Linux Kernel/source|lib/group_cpus.c}} &amp;ndash; distribute CPUs evenly across groups


🛠️ Utilities
: [https://man.archlinux.org/man/extra/irqbalance/irqbalance.1.en irqbalance] – distributes hardware interrupts across CPUs
: {{The Linux Kernel/man|8|numactl}} &amp;ndash; controls NUMA policy for processes or shared memory


📖 References
: {{The Linux Kernel/doc|Per-CPU Data|kernel-hacking/locking.html#per-cpu-data}}
: {{The Linux Kernel/doc|How CPU topology info is exported via sysfs|admin-guide/cputopology.html}}


📚 Further reading
: [https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/monitoring_and_managing_system_status_and_performance/customizing-tuned-profiles_monitoring-and-managing-system-status-and-performance#functionalities-of-the-scheduler-tuned-plug-in_customizing-tuned-profiles Functionalities of the scheduler TuneD plugin]
: [https://man.archlinux.org/man/tuned-adm.8 tuned-adm] &amp;ndash; command line tool for switching between different tuning profiles


==== {{w|Inter-processor interrupt|IPI}} ====

An inter-processor interrupt is a signal sent from one CPU to another to request an action such as rescheduling, TLB flush, or function execution.

⚲ API
: {{The Linux Kernel/id|smp_send_reschedule}} &amp;ndash; sends a reschedule IPI to a target CPU
: {{The Linux Kernel/id|smp_call_function}} &amp;ndash; invokes a function on all other CPUs via IPI
:: {{The Linux Kernel/id|smp_call_function_many}} &amp;ndash; on a specified set of CPUs
: {{The Linux Kernel/id|smp_call_function_single}} &amp;ndash; on a single target CPU
:: {{The Linux Kernel/id|smp_call_function_single_async}} &amp;ndash; asynchronous variant
: {{The Linux Kernel/id|smp_call_on_cpu}} &amp;ndash; execute on a specific CPU and wait for result
: {{The Linux Kernel/id|on_each_cpu}} &amp;ndash; run a function on all CPUs
:: {{The Linux Kernel/id|on_each_cpu_mask}} &amp;ndash; on a specified set of CPUs
:: {{The Linux Kernel/id|on_each_cpu_cond_mask}} &amp;ndash; conditionally on selected CPUs
: {{The Linux Kernel/id|smp_call_func_t}} &amp;ndash; callback typedef

⚙️ Internals
: {{The Linux Kernel/include|trace/events/ipi.h}}
: {{The Linux Kernel/file|kernel/irq/ipi.c}} &amp;ndash; generic IPI helpers
:: {{The Linux Kernel/id|ipi_send_single}}, {{The Linux Kernel/id|ipi_send_mask}}
: {{The Linux Kernel/source|arch/x86/kernel/apic/ipi.c}} &amp;ndash; x86 IPI via APIC
: {{The Linux Kernel/source|arch/x86/include/asm/irq_vectors.h}} &amp;ndash; x86 IPI vector types:
:: {{The Linux Kernel/id|RESCHEDULE_VECTOR}} &amp;ndash; used by {{The Linux Kernel/id|smp_send_reschedule}}
:: {{The Linux Kernel/id|CALL_FUNCTION_VECTOR}} &amp;ndash; used by {{The Linux Kernel/id|smp_call_function_many}}
:: {{The Linux Kernel/id|CALL_FUNCTION_SINGLE_VECTOR}} &amp;ndash; used by {{The Linux Kernel/id|smp_call_function_single}}
:: {{The Linux Kernel/id|IRQ_WORK_VECTOR}} &amp;ndash; used by {{The Linux Kernel/id|irq_work_queue}}, see [[#Interrupt_context|Interrupt context]]
:: {{The Linux Kernel/id|NMI_VECTOR}} &amp;ndash; used by watchdog, {{The Linux Kernel/id|crash_smp_send_stop}}

==== CPU affinity ====

Affinity refers to assigning a process or thread to specific CPU cores.
This helps control which CPUs execute tasks, potentially improving performance by reducing data movement between cores.
It can be managed using system calls or commands.
Affinity can be represented as CPU bitmask: {{The Linux Kernel/id|cpumask_t}} or CPU affinity list: {{The Linux Kernel/id|cpulist_parse}}.


⚲ API
: {{The Linux Kernel/man|1|taskset}} &amp;ndash; set or retrieve a process's CPU affinity
: grep Cpus_allowed /proc/self/status
: {{The Linux Kernel/man|2|sched_setaffinity}} {{The Linux Kernel/man|2|sched_getaffinity}} &amp;ndash; set and get a thread's CPU affinity mask
:: ↪ {{The Linux Kernel/id|sched_setaffinity}}
: {{The Linux Kernel/id|set_cpus_allowed_ptr}} &amp;ndash; common kernel function to change a task's affinity mask
: {{The Linux Kernel/include|linux/cpu_rmap.h}} &amp;ndash; CPU affinity reverse-map support
: {{The Linux Kernel/include|linux/cpumask_types.h}}
:: struct cpumask, {{The Linux Kernel/id|cpumask_t}} &amp;ndash; CPUs bitmap, can be very big
:: {{The Linux Kernel/id|cpumask_var_t}} &amp;ndash; type for local cpumask variable, see {{The Linux Kernel/id|alloc_cpumask_var}}, {{The Linux Kernel/id|free_cpumask_var}}.
: {{The Linux Kernel/include|linux/cpumask.h}} &amp;ndash; Cpumasks provide a bitmap suitable for representing the set of CPU's in a system, one bit position per CPU number
:: {{The Linux Kernel/id|for_each_possible_cpu}}
:: {{The Linux Kernel/id|num_online_cpus}}
:: {{The Linux Kernel/id|cpumask_set_cpu}}
:: {{The Linux Kernel/id|cpumask_test_cpu}}
:: {{The Linux Kernel/id|for_each_cpu}}


⚙️ Internals
: {{The Linux Kernel/id|cpus_mask}} &amp;ndash; affinity of {{The Linux Kernel/id|task_struct}}
: {{The Linux Kernel/id|cpus_allowed}} &amp;ndash; affinity of {{The Linux Kernel/id|cpuset}}


📚 Further reading
: {{w|Processor affinity}}
: {{w|Affinity mask}}

==== CPU hotplug ====

CPU hotplugging in Linux refers to the ability to dynamically add or remove CPUs from the system without needing a reboot.
This feature is crucial in environments requiring high availability and resource flexibility, such as data centers, virtualized systems, and systems that use power management aggressively.


🗝️ Acronyms
: BP &amp;ndash; Bootstrap Processor
: AP &amp;ndash; Application Processor


⚲ API
: /sys/devices/system/cpu/cpu*/online
: /sys/devices/system/cpu/cpu*/hotplug/
: {{The Linux Kernel/include|linux/cpu.h}}
:: {{The Linux Kernel/id|add_cpu}} ...
: {{The Linux Kernel/include|linux/cpuhotplug.h}}
:: {{The Linux Kernel/id|cpuhp_state}} &amp;ndash; CPU hotplug states 
:: {{The Linux Kernel/id|cpuhp_setup_state}} ... &amp;ndash; setups hotplug state callbacks
::: {{The Linux Kernel/id|cpuhp_setup_state_multi}}
::: {{The Linux Kernel/id|cpuhp_setup_state_nocalls}}
: {{The Linux Kernel/include|linux/cpuhplock.h}} &amp;ndash; CPU hotplug locking
:: {{The Linux Kernel/id|cpus_read_lock}} ...
:: {{The Linux Kernel/id|remove_cpu}} ...


⚙️ Internals
: {{The Linux Kernel/source|kernel/cpu.c}} &amp;ndash; CPU hotplug state machine
:: {{The Linux Kernel/id|cpuhp_state}} &amp;ndash; from CPUHP_OFFLINE to CPUHP_AP_ACTIVE and CPUHP_ONLINE.
:: {{The Linux Kernel/id|cpuhp_hp_states}}
:: {{The Linux Kernel/id|boot_cpu_hotplug_init}}
:: {{The Linux Kernel/id|cpuhp_threads_init}}
:: ... {{The Linux Kernel/id|cpuhp_invoke_callback_range}} ...
: {{The Linux Kernel/source|kernel/irq/cpuhotplug.c}} &amp;ndash; IRQ migration on CPU hotunplug
: {{The Linux Kernel/source|drivers/base/cpu.c}} &amp;ndash; CPU subsystem support
:: {{The Linux Kernel/id|cpu_dev_init}}
::: ... {{The Linux Kernel/id|cpu_subsys_online}}
: {{The Linux Kernel/include|trace/events/cpuhp.h}}
: {{The Linux Kernel/include|linux/cpuhplock.h}}


👁️ Examples
: {{The Linux Kernel/id|torture_onoff}}
: {{The Linux Kernel/source|tools/testing/selftests/sched_ext/hotplug.c}} &amp;ndash; sched_ext CPU hotplug test


📖 References
: {{The Linux Kernel/doc|CPU hotplug in the Kernel|core-api/cpu_hotplug.html}}
:: {{The Linux Kernel/doc|Introduction|core-api/cpu_hotplug.html#introduction}} 
:: {{The Linux Kernel/doc|Command Line Switches|core-api/cpu_hotplug.html#command-line-switches}} 
:: {{The Linux Kernel/doc|CPU maps|core-api/cpu_hotplug.html#cpu-maps}} 
:: {{The Linux Kernel/doc|Using CPU hotplug|core-api/cpu_hotplug.html#using-cpu-hotplug}} 
:: {{The Linux Kernel/doc|The CPU hotplug coordination|core-api/cpu_hotplug.html#the-cpu-hotplug-coordination}} 
:: {{The Linux Kernel/doc|The CPU hotplug API|core-api/cpu_hotplug.html#the-cpu-hotplug-api}} 
::: {{The Linux Kernel/doc|CPU hotplug state machine|core-api/cpu_hotplug.html#cpu-hotplug-state-machine}} 
::: {{The Linux Kernel/doc|CPU online/offline operations|core-api/cpu_hotplug.html#cpu-online-offline-operations}} 
::: {{The Linux Kernel/doc|Allocating a state|core-api/cpu_hotplug.html#allocating-a-state}} 
::: {{The Linux Kernel/doc|Setup of a CPU hotplug state|core-api/cpu_hotplug.html#setup-of-a-cpu-hotplug-state}} 
::: {{The Linux Kernel/doc|Removal of a CPU hotplug state|core-api/cpu_hotplug.html#removal-of-a-cpu-hotplug-state}} 
::: {{The Linux Kernel/doc|Multi-Instance state instance management|core-api/cpu_hotplug.html#multi-instance-state-instance-management}} 
::: {{The Linux Kernel/doc|Examples|core-api/cpu_hotplug.html#examples}} 
:: {{The Linux Kernel/doc|Testing of hotplug states|core-api/cpu_hotplug.html#testing-of-hotplug-states}} 
:: {{The Linux Kernel/doc|Architecture’s requirements|core-api/cpu_hotplug.html#architecture-s-requirements}} 
:: {{The Linux Kernel/doc|User Space Notification|core-api/cpu_hotplug.html#user-space-notification}} 
:: {{The Linux Kernel/doc|Kernel Inline Documentations Reference|core-api/cpu_hotplug.html#kernel-inline-documentations-reference}}
 

🔨 [https://manpages.ubuntu.com/manpages/resolute/man1/stress-ng.1.html#:~:text=%2D%2Dcpu%2Donline stress-ng --cpu-online]

📚 Further reading
: {{The Linux Kernel/id|CONFIG_CPU_HOTPLUG_STATE_CONTROL}} &amp;ndash; enables the ability to write incremental steps between &quot;offline&quot; and &quot;online&quot; states to the CPU's sysfs target file, allowing for more granular control of state transitions.
:: {{The Linux Kernel/id|target_store}}: {{The Linux Kernel/id|cpu_up}}/{{The Linux Kernel/id|cpu_down}}
: [https://lore.kernel.org/lkml/?q=cpuhotplug+OR+cpuhp cpuhotplug, cpuhp @LKML]

==== CPU isolation ====

CPU isolation ensures that specific tasks run on dedicated CPUs, reducing contention and latency.

'''Housekeeping''' CPUs refer to the CPUs that are reserved for various '''system''' tasks. See {{The Linux Kernel/id|hk_type}}.

'''Isolated''' CPUs are dedicated to '''real-time''' applications, such as DPDK.

⚲ API
: /sys/devices/system/cpu/isolated
: /sys/devices/system/cpu/nohz_full
: [https://docs.kernel.org/admin-guide/cgroup-v2.html#:~:text=cpuset.cpus.isolated /sys/fs/cgroup/cpuset.cpus.isolated]
: [https://docs.kernel.org/admin-guide/cgroup-v2.html#:~:text=Partition%20root%20without%20load%20balancing /sys/fs/cgroup/.../cpuset.cpus.partition]
: {{The Linux Kernel/include|linux/sched/isolation.h}}
:: {{The Linux Kernel/id|hk_type}} &amp;ndash; housekeeping type
:: {{The Linux Kernel/id|housekeeping_cpumask}} &amp;ndash; returns CPUs available for housekeeping of a given type
:: {{The Linux Kernel/id|cpu_is_isolated}}
: {{The Linux Kernel/include|linux/cpuset.h}} &amp;ndash; cpuset interface
: {{The Linux Kernel/man|7|cpuset}} &amp;ndash; confine processes to processor and memory node subsets


⚙️ Internals
: {{The Linux Kernel/id|CONFIG_CPU_ISOLATION}}
:: {{The Linux Kernel/source|kernel/sched/isolation.c}} &amp;ndash; housekeeping CPU management
::: {{The Linux Kernel/id|housekeeping_init}}, {{The Linux Kernel/id|housekeeping_update}}
: {{The Linux Kernel/id|CONFIG_CPUSETS}}
:: {{The Linux Kernel/source|kernel/cgroup/cpuset.c}} &amp;ndash; cpuset cgroup controller
::: {{The Linux Kernel/id|cpuset_init}}
::: {{The Linux Kernel/id|cpuset_init_smp}}
::: {{The Linux Kernel/id|isolated_cpus}}
::: {{The Linux Kernel/id|partition_xcpus_add}}, {{The Linux Kernel/id|partition_xcpus_del}}


📖 References
: {{The Linux Kernel/doc|CPU lists in command-line parameters|admin-guide/kernel-parameters.html#cpu-lists}}
:: [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=nohz_full= '''nohz_full'''] clears housekeeping.{{The Linux Kernel/id|cpumasks}} for tick, wq, timer, rcu, misc, and kthread in {{The Linux Kernel/id|housekeeping_nohz_full_setup}}
:: [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=isolcpus '''isolcpus'''] clears housekeeping.{{The Linux Kernel/id|cpumasks}} for [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=domain%20isolation domain] (by default), [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=nohz nohz], and [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=managed_irq managed_irq] in {{The Linux Kernel/id|housekeeping_isolcpus_setup}}
: {{The Linux Kernel/doc|Housekeeping|core-api/housekeeping.html}}
: {{The Linux Kernel/doc|NO_HZ: Reducing Scheduling-Clock Ticks|timers/no_hz.html}}
: {{The Linux Kernel/doc|CPUSETS of cgroup v2|admin-guide/cgroup-v2.html#cpuset}}
: {{The Linux Kernel/doc|CPUSETS of cgroup v1|admin-guide/cgroup-v1/cpusets.html}}


📚 Further reading
: [https://www.youtube.com/watch?v=1lomUhSS82s CPU Isolation state of the art, LPC'23]
: [https://lpc.events/event/19/contributions/2219/ CPU Isolation and IPI interference, LPC'25]
: [https://www.suse.com/c/cpu-isolation-introduction-part-1/ CPU Isolation]
: [https://lore.kernel.org/lkml/?q=isolcpus isolcpus @LKML]
: [https://lore.kernel.org/lkml/?q=housekeeping housekeeping @LKML]
: [https://kubernetes.io/docs/tasks/administer-cluster/reserve-compute-resources/#explicitly-reserved-cpu-list Explicitly Reserved CPU List, Kubernetes Documentation]
: [https://wiki.linuxfoundation.org/realtime/documentation/howto/tools/cpu-partitioning/start CPU Partitioning]
: {{The Linux Kernel/doc|Scheduler Domains|scheduler/sched-domains.html}} &amp;ndash; the Scheduler balances CPUs (scheduling groups) within a sched domain
: [https://lore.kernel.org/lkml/?q=nohz_full nohz_full @LKML]

💾 Historical since v7.0
: {{The Linux Kernel/id|cpuset_cpu_is_isolated}} &amp;ndash; removed, use {{The Linux Kernel/id|cpu_is_isolated}} instead

=== Runtime code patching ===

The kernel patches its own machine code at boot or runtime to optimize hot paths.
Static keys patch a {{w|NOP_(code)|NOP}} to a jump (or vice versa); static calls patch indirect calls to direct calls; alternatives replace instructions based on CPU features.

⚲ API
: {{The Linux Kernel/include|linux/jump_label.h}} &amp;ndash; static keys
:: {{The Linux Kernel/id|DEFINE_STATIC_KEY_FALSE}} &amp;ndash; define a key, initially false
:: {{The Linux Kernel/id|static_branch_unlikely}} &amp;ndash; zero-cost branch check (NOP when key is false)
:: {{The Linux Kernel/id|static_branch_enable}} &amp;ndash; patch all sites to take the branch (expensive, rare use)
: {{The Linux Kernel/include|linux/static_call.h}} &amp;ndash; static calls
:: {{The Linux Kernel/id|DEFINE_STATIC_CALL}} &amp;ndash; define a call site with initial target function
:: {{The Linux Kernel/id|static_call}} &amp;ndash; invoke the patched direct call
:: {{The Linux Kernel/id|static_call_update}} &amp;ndash; change target function, patch all sites
: {{The Linux Kernel/source|arch/x86/include/asm/alternative.h}} &amp;ndash; alternatives
:: {{The Linux Kernel/id|ALTERNATIVE}} &amp;ndash; replace instructions at boot based on CPU features
:: {{The Linux Kernel/source|arch/x86/include/asm/cpufeatures.h}} &amp;ndash; X86_FEATURE_* flags


⚙️ Internals
: {{The Linux Kernel/id|CONFIG_JUMP_LABEL}}
:: {{The Linux Kernel/source|kernel/jump_label.c}} &amp;ndash; static key patching core
:: {{The Linux Kernel/source|arch/x86/kernel/jump_label.c}} &amp;ndash; x86 static key patching
: {{The Linux Kernel/id|CONFIG_HAVE_STATIC_CALL}}
:: {{The Linux Kernel/source|kernel/static_call_inline.c}} &amp;ndash; static call core
:: {{The Linux Kernel/source|arch/x86/kernel/static_call.c}} &amp;ndash; x86 static call patching
: {{The Linux Kernel/source|arch/x86/include/asm/alternative.h}} &amp;ndash; runtime instruction patching
:: {{The Linux Kernel/source|arch/x86/kernel/alternative.c}} &amp;ndash; x86 alternatives engine
::: {{The Linux Kernel/id|smp_text_poke_single}} &amp;ndash; safely patch code on SMP using INT3 breakpoints; used by static keys, static calls, ftrace, kprobes
:::: {{The Linux Kernel/id|smp_text_poke_batch_add}}
:::: {{The Linux Kernel/id|smp_text_poke_batch_finish}}


👁 Examples
: {{The Linux Kernel/id|housekeeping_overridden}}
: {{The Linux Kernel/id|preempt_schedule}}
: tracepoints


📖 References
: {{The Linux Kernel/doc|Static Keys|staging/static-keys.html}}
: {{The Linux Kernel/doc|x86 CPU feature flags|arch/x86/cpuinfo.html}}


=== {{w|Memory barrier}}s ===

Memory barriers (MB) are synchronization mechanisms used to ensure proper ordering of memory operations in a SMP environment.
They play a crucial role in maintaining the consistency and correctness of data shared among different CPU cores or processors.
MBs prevent unexpected and potentially harmful reordering of memory access instructions by the compiler or CPU, which can lead to data corruption and race conditions in a concurrent software system.

⚲ API
: {{The Linux Kernel/man|2|membarrier}}
: {{The Linux Kernel/include|asm-generic/barrier.h}}
:: {{The Linux Kernel/id|mb}}, {{The Linux Kernel/id|rmb}}, {{The Linux Kernel/id|wmb}}
:: {{The Linux Kernel/id|smp_mb}}, {{The Linux Kernel/id|smp_rmb}}, {{The Linux Kernel/id|smp_wmb}}


⚙️ Internals

: {{The Linux Kernel/source|arch/x86/include/asm/barrier.h}} &amp;ndash; x86 memory barrier instructions
: {{The Linux Kernel/source|kernel/sched/membarrier.c}} &amp;ndash; membarrier system call


📖 References
: {{The Linux Kernel/doc|Memory barriers|core-api/wrappers/memory-barriers.html}}


=== States ===

C-states and P-states are features in modern CPUs designed to improve energy efficiency.

🗝️ Acronyms
: [https://uefi.org/htmlspecs/ACPI_Spec_6_4_html/08_Processor_Configuration_and_Control/processor-power-states.html C-states] &amp;ndash; CPU(?) states, aka idle states
: EPP &amp;ndash; {{The Linux Kernel/doc|Energy Performance Preference|admin-guide/pm/amd-pstate.html#energy-performance-preference-epp-rw}}
: HWP &amp;ndash; hardware-managed P-states, see [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=hwp_only hwp_only]
: [https://www.intel.com/content/www/us/en/docs/socwatch/user-guide/2020/p-state.html P-states] &amp;ndash; Performance states, see CPU Power and frequency scaling


⚲ API
: [https://linux.die.net/man/1/cpupower cpupower]


📖 References
: {{The Linux Kernel/doc|Working-State Power Management|admin-guide/pm/working-state.html}}
: https://lwn.net/Kernel/Index/#Power_management


==== Idle ====


C-states, {{w|ACPI#Processor_states|power states}}:
: C0 – operating, executing instructions.
: C1 (Halt) – internal {{w|Clock gating|clocks stopped}}.
: C1E (Enhanced Halt) – clocks stopped, voltage and frequency reduced.
: C2 (Stop-Clock) – internal and external {{w|Clock gating|clocks stopped}}.
: C3 (Deep Sleep) – clocks stopped, L1/L2 cache may flush, local APIC timer stops, requiring [[#Clock_infrastructure|tick broadcast]].
: C4 (Deeper Sleep) – voltage reduced.
: C6 (Deep Power Down) – state saved to SRAM, voltage can drop to 0V.
: C7 (Deeper Power Down) – C6 + L3 cache flushed.
: Modern Intel typically uses C1/C1E and C6, skipping C2–C5.
: ⚠️ ACPI state names (C1_ACPI, C2_ACPI, C3_ACPI) may not match actual hardware C-states. The [https://www.felixcloutier.com/x86/monitor:mwait MWAIT] hint reveals the real state: e.g. MWAIT 0x60 = hardware C6 may appear as &quot;C3_ACPI&quot;.


⚲ API
: turbostat --show CPU --quiet -n 1 --interval 0.1 --show sysfs
: [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=idle= idle=]
: /dev/cpu_dma_latency &amp;ndash; see {{The Linux Kernel/id|set_cpu_dma_latency}}
: C-states interfaces:
:: cpupower idle-info – show driver, governor, states with latency and residency
:: /sys/devices/system/cpu/cpuidle/
:: /sys/devices/system/cpu/cpu*/cpuidle/
::: cat /sys/devices/system/cpu/cpu0/cpuidle/state*/name – list available C-states
:: {{The Linux Kernel/include|linux/cpuidle.h}} – generic framework for CPU idle power management
: {{The Linux Kernel/include|linux/pm_qos.h}}


⚙️ Internals
: {{The Linux Kernel/source|drivers/cpuidle}} – CPU idle governors and drivers
: {{The Linux Kernel/source|drivers/idle/intel_idle.c}} – {{The Linux Kernel/doc|intel_idle|admin-guide/pm/intel_idle.html}}, hardcoded C-states per CPU model, modern Intel (C1/C1E/C6)
: {{The Linux Kernel/source|drivers/acpi/processor_idle.c}} – acpi_idle, reads C-states from ACPI tables, generic fallback (C1/C2/C3)
: {{The Linux Kernel/source|kernel/power/qos.c}} – PM quality of service
:: {{The Linux Kernel/id|cpu_latency_qos_miscdev}} – implementation of /dev/cpu_dma_latency


📖 References
:: {{The Linux Kernel/doc|CPU Idle Time Management|admin-guide/pm/cpuidle.html}}
: [https://www.intel.com/content/www/us/en/support/articles/000006619/processors/intel-core-processors.html Intel C-states reference]
: [https://support.hpe.com/hpesc/public/docDisplay?docId=sd00002067en_us&amp;page=GUID-855C475E-F9F9-460D-9475-B96DD982B587.html HPE C-states reference]


📚 Further reading
:: https://lwn.net/Kernel/Index/#Power_management-cpuidle
: {{The Linux Kernel/doc|PM Quality Of Service Interface|power/pm_qos_interface.html}}

==== Power and frequency ====


P-states, {{w|ACPI#Performance_state|performance states}}:
: P0 &amp;ndash; maximum power and frequency
: Pn &amp;ndash; less power and frequency
: ...


⚲ API
: Reliable measurement of actual CPU frequency
:: [https://manpages.debian.org/testing/linux-cpupower/turbostat.8.en.html turbostat] --quiet --show CPU,Bzy_MHz -n 1 --interval 0.1
::: Bzy_MHz &amp;ndash; average clock rate while the CPU was not idle (ie. in &quot;c0&quot; state).
: [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=intel_pstate intel_pstate=]
:: {{The Linux Kernel/doc|Kernel Command Line Options for intel_pstate|admin-guide/pm/intel_pstate.html#kernel-command-line-options-for-intel-pstate}}
: [https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt#:~:text=cpufreq.default_governor cpufreq.default_governor=]
: P-states interfaces:
:: /sys/devices/system/cpu/cpufreq/
:: /sys/devices/system/cpu/cpu*/cpufreq/
::: scaling_cur_freq &amp;ndash; unreliable assumption on CPU frequency
:: /sys/devices/system/cpu/intel_pstate/
:: {{The Linux Kernel/include|linux/cpufreq.h}}
:: {{The Linux Kernel/include|linux/sched/cpufreq.h}} &amp;ndash; interface between cpufreq drivers and the scheduler


⚙️ Internals
: {{The Linux Kernel/source|drivers/cpufreq}} &amp;ndash; CPU frequency scaling drivers
:: {{The Linux Kernel/id|intel_pstate}}
:: {{The Linux Kernel/id|acpi_cpufreq_driver}}
: {{The Linux Kernel/source|kernel/sched/cpufreq_schedutil.c}} &amp;ndash; implementation of cpufreq.default_governor=schedutil
: {{The Linux Kernel/source|arch/x86/kernel/cpu/intel_epb.c}} &amp;ndash; Intel Performance and Energy Bias Hint support


📖 References
: {{The Linux Kernel/doc|CPU Performance Scaling|admin-guide/pm/cpufreq.html}}
: {{The Linux Kernel/doc|Device Frequency Scaling|driver-api/devfreq.html}}
: [https://www.kernel.org/doc/Documentation/cpu-freq/governors.txt CPUFreq Governor]
: {{The Linux Kernel/doc|CPUFreq - CPU frequency and voltage scaling|cpu-freq}}
: {{The Linux Kernel/doc|Intel Performance and Energy Bias Hint|admin-guide/pm/intel_epb.html}}
: {{The Linux Kernel/doc|intel_pstate CPU Performance Scaling Driver|admin-guide/pm/intel_pstate.html}}
:: {{The Linux Kernel/doc|General Information|admin-guide/pm/intel_pstate.html#general-information}} 
:: {{The Linux Kernel/doc|Operation Modes|admin-guide/pm/intel_pstate.html#operation-modes}} 
::: {{The Linux Kernel/doc|Active Mode|admin-guide/pm/intel_pstate.html#active-mode}}
&lt;!--
:::: {{The Linux Kernel/doc|Active Mode With HWP|admin-guide/pm/intel_pstate.html#active-mode-with-hwp}} 
::::: {{The Linux Kernel/doc|HWP + performance|admin-guide/pm/intel_pstate.html#hwp-performance}} 
::::: {{The Linux Kernel/doc|HWP + powersave|admin-guide/pm/intel_pstate.html#hwp-powersave}} 
:::: {{The Linux Kernel/doc|Active Mode Without HWP|admin-guide/pm/intel_pstate.html#active-mode-without-hwp}} 
::::: {{The Linux Kernel/doc|performance|admin-guide/pm/intel_pstate.html#performance}} 
::::: {{The Linux Kernel/doc|powersave|admin-guide/pm/intel_pstate.html#powersave}} 
--&gt;
::: {{The Linux Kernel/doc|Passive Mode|admin-guide/pm/intel_pstate.html#passive-mode}} 
:: {{The Linux Kernel/doc|Turbo P-states Support|admin-guide/pm/intel_pstate.html#turbo-p-states-support}} 
:: {{The Linux Kernel/doc|Processor Support|admin-guide/pm/intel_pstate.html#processor-support}} 
:: {{The Linux Kernel/doc|Support for Hybrid Processors|admin-guide/pm/intel_pstate.html#support-for-hybrid-processors}} 
::: {{The Linux Kernel/doc|Hybrid Processors with SMT|admin-guide/pm/intel_pstate.html#hybrid-processors-with-smt}} 
::: {{The Linux Kernel/doc|Capacity-Aware Scheduling Support|admin-guide/pm/intel_pstate.html#capacity-aware-scheduling-support}} 
::: {{The Linux Kernel/doc|Energy-Aware Scheduling Support|admin-guide/pm/intel_pstate.html#energy-aware-scheduling-support}} 
:: {{The Linux Kernel/doc|User Space Interface in sysfs|admin-guide/pm/intel_pstate.html#user-space-interface-in-sysfs}} 
::: {{The Linux Kernel/doc|Global Attributes|admin-guide/pm/intel_pstate.html#global-attributes}} 
::: {{The Linux Kernel/doc|Interpretation of Policy Attributes|admin-guide/pm/intel_pstate.html#interpretation-of-policy-attributes}} 
::: {{The Linux Kernel/doc|Coordination of P-State Limits|admin-guide/pm/intel_pstate.html#coordination-of-p-state-limits}} 
::: {{The Linux Kernel/doc|Energy vs Performance Hints|admin-guide/pm/intel_pstate.html#energy-vs-performance-hints}} 
:: {{The Linux Kernel/doc|intel_pstate vs acpi-cpufreq|admin-guide/pm/intel_pstate.html#intel-pstate-vs-acpi-cpufreq}} 
:: {{The Linux Kernel/doc|Kernel Command Line Options for intel_pstate|admin-guide/pm/intel_pstate.html#kernel-command-line-options-for-intel-pstate}} 
:: {{The Linux Kernel/doc|Diagnostics and Tuning|admin-guide/pm/intel_pstate.html#diagnostics-and-tuning}} 
::: {{The Linux Kernel/doc|Trace Events|admin-guide/pm/intel_pstate.html#trace-events}} 
::: {{The Linux Kernel/doc|ftrace|admin-guide/pm/intel_pstate.html#ftrace}} 
&lt;!-- end of intel_pstate.html --&gt;


📚 Further reading
: https://lwn.net/Kernel/Index/#Power_management-Frequency_scaling
: [https://wiki.archlinux.org/title/CPU_frequency_scaling CPU frequency scaling]
: {{The Linux Kernel/ltp|kernel/device-drivers|cpufreq}}
: [https://www.thinkwiki.org/wiki/How_to_use_cpufrequtils How to use cpufrequtils] 
:: [https://linux.die.net/man/1/cpufreq-info cpufreq-info]
:: [https://linux.die.net/man/1/cpufreq-set cpufreq-set]
: https://github.com/intel/power-optimization-library
: https://github.com/intel/kubernetes-power-manager

{{BookCat}}</text>
      <sha1>cek6cq50mn8a1h9aly9iypjps4talra</sha1>
    </revision>
  </page>
  <page>
    <title>General Literary Chinese from Scratch</title>
    <ns>0</ns>
    <id>481710</id>
    <revision>
      <id>4656071</id>
      <parentid>4641271</parentid>
      <timestamp>2026-08-02T17:41:59Z</timestamp>
      <contributor>
        <username>Shira the Mogul</username>
        <id>3560559</id>
      </contributor>
      <minor />
      <comment>/* Unit 6: Nation Focus - Japan */ this is shorter, doesn't have ambiguous characters, and is overall more helpful.</comment>
      <origin>4656071</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="39834" sha1="h0l569eol7bhheaqu1owj7mimrruozy" xml:space="preserve">__notoc__

Welcome to the Wikibook for Literary Chinese (Known as 漢文 &quot;Han Language&quot; in East Asia or 文言 &quot;Literary Language&quot; in China), aimed at individuals hoping to gain a general knowledge of it before progressing into genres they wish to be acquainted with. 

This is not the [[Classical Chinese]] textbook, which is aimed at Chinese Zhou-Qin era texts. This  text aims to shed light on post-Zhou-Qin texts across East Asia, which mimic those texts. However, as Zhou-Qin era texts served as the main body from which individuals learned, they are employed here as and when they are considered necessary or otherwise useful. It does so through a &quot;buffet&quot; approach, showering you, the reader, with an ocean of texts of myriad genre. 

==Table of Contents==

=== Front matter ===

* [[/Introduction/]]
* [[/Appendices/]]

=== Useful resources ===
These are quick grab-bags that can be useful for vocabulary-building. 
* [[/Antonym List/]] &lt;!--- 文/武，大/小，厚/薄，橫/縱...---&gt;
* [[/Collocation Groups/]] &lt;!--- e.g. 四象，三靈…… ---&gt;
* [https://zh.wikiversity.org/wiki/Subject:華製新漢語及中文固有語/嚴譯及部定詞等 Yan Fu's Qing-era translations for modern terms] &lt;!--- Wikiversity has this (https://zh.wikiversity.org/wiki/Subject:華製新漢語及中文固有語/嚴譯及部定詞等) and the below, I will effectively be translating a lot of it! ---&gt;
* [https://zh.wikiversity.org/wiki/Subject:華製新漢語及中文固有語/上古語考輯 Communicative Terms]
&lt;!--- this will be translated eventually, but right now it's bad to just leave this here. ---&gt;

=== Useful primers ===
Across history, many primers have been made for teaching Literary Chinese to children. These are a few that are recommended for use alongside this work, ideally in flashcards. 
* [https://www.fdgwz.org.cn/Web/Show/11308 倉頡篇] - Cangjie's Chapters, the earliest one. It is extant, but incomplete. It contains several rare characters, and so if used, I would personally recommend doing so later, or out of interest. 
* 三字經 - The Three Character Classic, an excellent piece for Confucian education. Pair with 弟子规 for best results. 
** 三字經（太平天國版）- For Christians, there is a version made by Hong Xiuquan from the Taiping Rebellion. Despite the context, it is a legitimately useful primer and can be used to self-teach for the Delegate's Edition of the Christian Bible. 
* 千字文 - The Thousand Character Classic, a remarkable piece of constrained writing that only uses each character once. Amazing for building vocabulary whilst seeing historical allusions and the like. 
* 五字鑑 - The Five-Character Mirror, essentially the 24 Histories of China compressed into a primer. Uses 5-character couplets, the longest in this list. 
* 龍文鞭影 - The Shadow of Longwen's Whip, a historical allusion trainer. Best paired with a context piece.

===Unit 0: The Han script===
This unit is intended for those with no familiarity of the Han script. It will prepare you for the units ahead, teaching largely pictographic characters. 

By the end of this unit, students will:
* Recognise around 50 characters.
* Understand how characters are composed and how this gives them meaning.
* Have a basic idea of how to handwrite and/or type characters using the Cangjie Input Method.
* Know some bare basics of Literary Chinese grammar (e.g. Basic word order, where adjectives go, lack of &quot;is&quot;, 有...)

Lessons:
# [[/An Introduction to the Han Script/]]
# [[/People, Big and Small/]]
# [[/How do we write Chinese?/]]
# [[/What are Chinese characters, anyway?/]]
# [[/The Sun, the Moon, and the Five Elements/]]
# [[/Getting Familiar with Body Parts/]]
# [[/Using Numbers and Using Weapons/]] &lt;!--- 竹戈十大中一弓廿卜---&gt;
# [[/Tilling the Fields with 有/]] &lt;!--- 山田 ---&gt;
# [[/How Characters are Made/|How Characters are Made with Kiyohara no Sanemoto]] 
# [[/Cangjie Created Characters/]] &lt;!--- Get people to use Cangjie ---&gt;
# [[/The Kangxi Radical System/]] &lt;!--- Introduce some monoradical texts to train recognition. ---&gt;

===Unit 1: Basic Skills===
This unit is intended for those with minimal familiarity with the Han script and no familiarity with Literary Chinese. There is a focus on simple structures, skills for dissecting common textual structures, and short-form poetry in this unit. 

Before starting this unit, students should:
* Recognise around ~30 characters. 
* Can use Cangjie input. 
* Have given Unit 0 a cursory glance. 
&lt;br&gt;
By the end of this unit, students will:
* Recognise around ~100 characters. 
* Comprehend numbers, the Heavenly Stems, and the Earthly Branches, and be able to use them to quantify time and date.
* Intuit the basic topic -&gt; comment idea behind Literary Chinese. &quot;This, it is...&quot; 
* Understand basic function words such as 也, 而, 有, and 謂.

Lessons:
# [[/The All-Purpose 也/]]
# [[/An Introduction to Chinese Numbers/]] &lt;!--- It is hard to find authentic materials for this ---&gt;
# [[/One, Two, Left, and Right with Gongsun Long/]]
&lt;!---
曰：「二有一乎？」

曰：「二無一。」

曰：「二有右乎？」

曰：「二無右。」

曰：「二有左乎？」

曰：「二無左。」

曰：「右可謂二乎？」

曰：「不可。」

曰：「左可謂二乎？」

曰：「不可。」

曰：「左與右可謂二乎？」

曰：「可。」
---&gt;
# [[/The Heavenly Stems/]] &lt;!--- Introduce ordinals, which will be used to demonstrate sentence patterns later. ---&gt;
# [[/Tell the Time with Earthly Branches/]] &lt;!--- Introduce verbs and timekeeping ---&gt;
# [[/Lunar Dates with the Spring and Autumn Annals/]]
&lt;!--- Vocabulary: 歲，年，朔，月，日，來，前，初，正，春秋夏冬，曆，上，下. Consider including traditional names for months in a list. ---&gt;
# [[/Skimming for Major Events in Historical Annals/]] 
&lt;!--- Don't simply use Confucius's Chunqiu: We can use texts inspired by it. 

E.g. 三國史記 - 十五年京城旱。秋七月，蝗。very few new characters, lots one can use. Instantly able to use. 
https://zh.wikisource.org/wiki/%E4%B8%89%E5%9C%8B%E5%8F%B2%E8%A8%98/%E5%8D%B701

Skimming annals is very possible and a very useful skill. Don't skip out on it. Teach students to skim read!!! 
---&gt;
# [[/Dinner with the Daimyo/]]
&lt;!-- 
侍宴·大友皇子
皇明光日月，帝徳載天地。
三才併秦昌，万国表臣義。
--&gt; 
# [[/In Discourse with Jibong/]]
&lt;!--
芝峰類說 
倭國謂田爲畠。謂水田爲田。火田爲畑。猶我國以水田爲畓也。故官名有畠山殿。地名有畑島云。
--&gt;
# [[/Shinto FAQ with Honda Chikaatsu/]] 
&lt;!--- https://wikisource.org/wiki/%E7%9C%9E%E9%81%93%E5%95%8F%E5%B0%8D 眞道問對 本田親徳 really good way of operationalising 乎 and much of the early grammar. 

問 天帝無始無終乎。
對 天帝無始無終也。
旣以無始無終之力
與無始無終之體
造無始無終之萬物。
其功亦無始無終也。

問 天地大原在道乎。
對 天地大原實在道。
鬼神依道而立。
人民依道而活。
萬物依道而息。

This is great! ---&gt;

&lt;!---
Some cool stuff I saw someone studying from
https://zh.wikisource.org/wiki/%E8%87%B3%E5%B0%8F%E4%B8%98%E8%A5%BF%E5%B0%8F%E7%9F%B3%E6%BD%AD%E8%A8%98#
https://zh.wikisource.org/wiki/%E6%A0%B8%E8%88%9F%E8%A8%98

Could be used for period focus
---&gt;

===Unit 2: An Overview of Sinitic Poetry===
This unit will teach you how Sinitic Poetry operates; - that is, the way individuals in the Sinosphere compose poetry in Literary Chinese. Despite this language's fall out of favour in the past century, this tradition is still remarkably alive and well, and their short length makes them more accessible than elaborate prose. In this unit, you will begin from the ''Classic of Poetry'' before travelling through poems from the Tang dynasty, Singapore, Japan, Vietnam, the Ryukyu Kingdom, and Korea. When introducing poetry, I will furthermore use the language from the nation it is from to show how it is recited by its people. 

After discussing the Classic of Poetry, we will also be a small detour into a discussion on Ping-Ze 平仄, the Tang dynasty system of alternating tones, so to produce rhyme on tonal and phonological levels. This had a major impact on Literary Chinese poetry as a whole!

By the end of this Unit, students will:
* Recognise around 120 more characters.
* Be able to explain how Sinitic Poetry rhymes and the themes it contains.
* Be able to use function words such as 在, 無, 不, 聿, and 于/於 in poetic contexts.
* Recognise the switch between 吾/我 in the subject-object positions and demonstrate it in usage.
* (Chinese speakers) Be able to differentiate 于 and 於, and understand the &quot;interest(ed) in&quot; meaning of 好 in most circumstances.
&lt;!---
Summary of the above part about 于 and 於 for other editors:
于 and 於 were distinct words for an extremely long time and were still such to Literary Chinese writers. Their &quot;merging&quot; through Simplified-Traditional Chinese distinctions is a very modern thing. I will summarise their usages here, using Pulleyblank's Outline of Classical Chinese Grammar (2000);
* 于 - This can mean &quot;to go&quot; or &quot;to/at&quot;. 黃鳥于飛 &quot;The yellow birds go flying&quot;. Must be post-verbal. It can also appear in 至于.
* 於 - This is an all-purpose locative preposition - from &quot;on/at/in&quot; to &quot;from&quot; or even &quot;than&quot; (甲於乙). The implication of motion is not there at all. Must be pre-verbal. It can also appear in 之於 or be an archaic noun for a crow 於 (烏).
---&gt;

Lessons:
# [[/Across the Rivers with Emperor Puliuru Guang/]]
&lt;!---
春江花月夜·楊廣
夜露含花氣，春潭漾月暉。
漢水逢遊女，湘川值二妃。

This is really simple and can elucidate Ping-Ze easily.
---&gt;
# [[/To Study the Odes/]] 
&lt;!-- 蟋蟀·姬旦 國風·唐風
蟋蟀在堂，歲聿其莫。今我不樂，日月其除。無已大康，職思其居。好樂無荒，良士瞿瞿。
蟋蟀在堂，歲聿其逝。今我不樂，日月其邁。無已大康，職思其外。好樂無荒，良士蹶蹶。
蟋蟀在堂，役車其休。今我不樂，日月其慆。無已大康，職思其憂。好樂無荒，良士休休。
--&gt;
&lt;!-- 黃鳥 小雅·鴻鴈之什
黃鳥黃鳥，無集于穀，無啄我粟。
此邦之人，不我肯穀。言旋言歸，復我邦族。

黃鳥黃鳥，無集于桑，無啄我粱。
此邦之人，不可與明。言旋言歸，復我諸兄。

黃鳥黃鳥，無集于栩，無啄我黍。
此邦之人，不可與處。言旋言歸，復我諸父。
--&gt;
# [[/A Detour into Orthodox Ping-Ze/]] 
&lt;!--- 平 and 仄 are useful characters themselves. Show 仄 in the binomes 反仄，歉仄，逼仄 as it's often difficult to immediately use ---&gt;
# [[/The Restraint of Du Fu/]] 
# [[/The Longing of Li Bai/]] 
# [[/The Environment with Bukha Timur/]]
&lt;!---
西湖竹枝詞·布哈特穆爾
湖上春歸人未歸，桃紅柳緑黄鶯飛。
桃花落時多結子，楊花落處秪沾衣。

宫词·布哈特穆爾
玉樓珠箔晚天涼，秋色依稀滿建章。
金井梧桐霜葉盡，自隨流水出宮牆。

Mongol writer from the Uyghur Kingdom of Gaochang
Spammed Ctrl+F in https://zh.wikisource.org/wiki/%E5%BE%A1%E9%81%B8%E5%9B%9B%E6%9C%9D%E8%A9%A9_(%E5%9B%9B%E5%BA%AB%E5%85%A8%E6%9B%B8%E6%9C%AC)
---&gt;
# [[/Pillow Talk with Guan Yunshi/]]
&lt;!---
紅繡鞋·貫雲石
挨著靠著雲窗同坐，偎著抱著月枕雙歌，聽著數著愁著怕著早四更過。四更過情未足，情未足夜如梭。天哪，更閏一更兒妨甚么！

Uyghur author!
---&gt;
# [[/Buddhist Philosophy with Ngô Chân Lưu and Taisei Shōan/]]
&lt;!-- 元火·吳真流
木中元有火，元火復還生。
若為木無火，鉆燧何有萌。--&gt;
&lt;!-- 杜鵑·大成聖安
夢覚孤床静
杜鵑帯雨飛
一声来近枕
何者不沾衣
--&gt;
# [[/Odes with Mō Taiei and Zheng Chengxun/]]
&lt;!-- 詠松·毛泰永
植體宜千仞，垂陰動百尋。
李膺真烈烈，和嶠自森森。
桃李何堪較，雪霜安得侵。
萬年身不老，種子又成林。
AKA Inoha Seiki 伊野波 盛紀 --&gt;
&lt;!-- 詠班蘭·鄭成勛
南國多芳草，班蘭最有名。
深根將綠茁，長葉亦叢生。
取味迎賓合，入厨任水烹。
可憐經一用，擲棄不留情。

鄭成勛《樵隱詩集》 https://nus.edu.sg/nuslibraries/dsprojects/sg-jiutishi/poem/827 --&gt;

# [[/A Golden Cup and the Fall of a Dynasty with Yan Fu/]] 
&lt;!---
鞏金甌·嚴復
鞏金甌，承天幬，民物欣鳧藻，喜同袍。
清時幸遭，真熙皞，帝國蒼穹保。
天高高，海滔滔。
This has music to it, which I think can add a lot. It is also necessary to introduce Yan Fu early given he did translation. ---&gt;
# [[/On a Journey with Sa Dula/]]
&lt;!---
無題·薩都剌
為客三年海上洲，故鄉何處瘴雲稠。
數千里外蠻人域，十八灘頭過客舟。
時有山禽呼姓字，或從海鳥作朋儔。
故人珂珮周旋處，紫殿風清十二樓。
https://zh.wikisource.org/wiki/%E7%84%A1%E9%A1%8C_(%E8%96%A9%E9%83%BD%E5%89%8C)

A naturalised Mongol scholar who made a beautiful poem. This'll be a capstone.
---&gt;
&lt;!---
朝中措·襄陽古道灞陵橋
襄陽古道灞陵橋，詩興與秋高。
千古風流人物，一時多少雄豪。

霜清玉塞，雲飛隴首，風落江皋。
夢到鳳凰台上，山圍故國周遭。

北郊晚步
陂水荷凋晚，茅檐燕去涼。
遠林明落景，平麓淡秋光。
群牧歸村巷，孤禽立野航。
自諳閑散樂，園圃意尤長。

Jurchen poet and grandson of Emperor Shizong of Jin. He's a Zen Buddhist, so we'll go back to him later.
---&gt;

===Unit 3: Confucianism and the World===
This is a Confucian-themed unit with a smattering of other items. You will see the odd geography of the past, early linguistic philosophy, and terrifying breakaway states!

By the end of this unit, students should be able to:
* Recognise around 200+ characters.
* Read basic annals and histories with some dictionary assistance, and comprehend 3-character structures reliably.
* Have encountered basic grammatical points such as 之、乎、者、也、而、則、乃、所、以、於、于、與、且、蓋、and 夫. 
** 於 and 于 should be distinguishable.
* Survive a text of at least 250 characters and read for gist.

Lessons:
# [[/A Brief Overview of Confucianism/]] 
# [[/The Mountains with Yelü Tuyu/]]
&lt;!---
立木海上刻詩 耶律圖欲 / 耶律倍 / 李贊華

小山壓大山，大山全無力。
羞見故鄉人，從此投外國。
---&gt;
# [[/Teaching the Annals in Qi/]] &lt;!-- Gongyang Gao's commentary --&gt;
# [[/Is a White Horse a Horse?/]]&lt;!-- Teach negation with 非 in 公孙龍子 and compare with 不 --&gt;
# [[/The Three Character Classic/]]
# [[/Expressing Filial Conduct with Confucius and Hara Saihin/]]
&lt;!--
次韻杏坪先生
父執有君孤不孤
相依遍接搢紳徒
区区自抱地方寸
杳杳重遊天一隅
羇雁飛鳴迷汝國
家人思夢入江都
如教志業青年遂
世上寧無逐臭夫
--&gt;
# [[/Confucianism and the Environment with Sai On/]]&lt;!-- 木假山記 --&gt;
# [[/In Debate with Mencius/]]

===Unit 4: Women's Writing===
In this unit, women's writing from various areas of China will be explored. This is chiefly targeted at poetry and the themes within; from the feminine voice of the Classic of Poetry to the remonstrance towards the Khitan Emperor Tianzuo of Jin by his Consort Dasese. The role of women in courtly society is to be elucidated here!
# [[/An Unmarried Life with Heo Nansŏrhŏn/]]
&lt;!---
貧女吟 
豈是乏容色。工鍼復工織。
少小長寒門。良媒不相識。

夜久織未休。戛戛鳴寒機。
機中一匹練。終作阿誰衣。

手把金翦刀。夜寒十指直。
爲人作嫁衣。年年還獨宿。
---&gt;
# [[/Responding to Lord Trần with Hồ Xuân Hương/]]
&lt;!---
Responding to 陳光靜 Trần Quang Tĩnh

《和陳侯》
愧無才調使人驚，十載風塵貫耳鈴。
已是臨枰知敵手，莫須敲月苦殫精。
為輪為彈隨遭遇，誰鳳誰鶯任賦生。
造物於人何苟惜，明珠休向暗中呈。

莫須 is an important structure to teach here.
---&gt;
# [[/Gaze into the Autumn Night with Taisei Shōan/]]
&lt;!---
秋夜偶成·大成聖安
長天浮爽気，月色興無窮
群犬吠山径，百蟲啼野風
悲秋秋夜永，感古古今同
自是孤窓下，凄然万慮空
---&gt;
# [[/Visiting a Temple with Yu Xuanji/]]
&lt;!---
遊崇真觀南樓覩新及第題名處
雲峰滿目放春晴，歷歷銀鈎指下生。
自恨羅衣掩詩句，擧頭空羨榜中名。
---&gt;
# [[/Remonstrance with Dasese/]]
&lt;!---
https://zh.wikisource.org/wiki/%E8%AB%B7%E8%AB%AB%E6%AD%8C
諷諫歌·大瑟瑟
勿嗟塞上兮暗紅塵。
勿傷多難兮畏夷人。
不如塞奸邪之路兮選取賢臣。
直須臥薪嚐膽兮激壯士之捐身。
可以朝清漠北兮夕枕燕雲。

Dasese (or 萧瑟瑟) was a Khitan consort to Emperor Tianzuo of Liao. She remonstrated him as the Jurchens were beginning to encroach upon the Khitan, and was forced to commit suicide for her remonstrance. Tianzuo would soon pay for his malfeasance. 
---&gt;
# [[/The Love Songs of the Odes/]]
&lt;!---
褰裳
子惠思我，褰裳涉溱。子不我思，豈無他人？狂童之狂也且！
子惠思我，褰裳涉洧。子不我思，豈無他士？狂童之狂也且！

柏舟
彼柏舟，在彼中河，髧彼兩髦，實維我儀，之死矢靡它，母也天只，不諒人只。
汎彼柏舟，在彼河側，髧彼兩髦，實維我特，之死矢靡慝，母也天只，不諒人只。

行露
厭浥行露，豈不夙夜，謂行多露。
誰謂雀無角？何以穿我屋？誰謂女無家？何以速我獄？雖速我獄，室家不足。
誰謂鼠無牙？何以穿我墉？誰謂女無家？何以速我訟？雖速我訟，亦不女從。
---&gt;
# [[/Rules for Women with Ban Zhao/]]
&lt;!--- https://zh.wikisource.org/wiki/%E5%A5%B3%E8%AA%A1 ---&gt;
# [[/The Tragedy of Cai Wenji/]]
&lt;!---
悲憤詩
〔兩漢〕蔡文姬
漢季失權柄，董卓亂天常。
志欲圖篡弒，先害諸賢良。
逼迫遷舊邦，擁主以自強。
海內興義師，欲共討不祥。
卓眾來東下，金甲耀日光。
平土人脆弱，來兵皆胡羌。
獵野圍城邑，所向悉破亡。
斬截無孑遺，屍骸相撐拒。
馬邊懸男頭，馬後載婦女。
長驅西入關，迥路險且阻。
還顧邈冥冥，肝脾為爛腐。
所略有萬計，不得令屯聚。
或有骨肉俱，欲言不敢語。
失意幾微間，輒言斃降虜。
要當以亭刃，我曹不活汝。
豈復惜性命，不堪其詈罵。
或便加棰杖，毒痛參並下。
旦則號泣行，夜則悲吟坐。
欲死不能得，欲生無一可。
彼蒼者何辜，乃遭此厄禍。
邊荒與華異，人俗少義理。
處所多霜雪，胡風春夏起。
翩翩吹我衣，肅肅入我耳。
感時念父母，哀嘆無窮已。
有客從外來，聞之常歡喜。
迎問其消息，輒復非鄉里。
邂逅徼時願，骨肉來迎己。
己得自解免，當復棄兒子。
天屬綴人心，念別無會期。
存亡永乖隔，不忍與之辭。
兒前抱我頸，問母欲何之。
人言母當去，豈復有還時。
阿母常仁惻，今何更不慈。
我尚未成人，奈何不顧思。
見此崩五內，恍惚生狂痴。
號泣手撫摩，當發復回疑。
兼有同時輩，相送告離別。
慕我獨得歸，哀叫聲摧裂。
馬為立踟躕，車為不轉轍。
觀者皆噓唏，行路亦嗚咽。
去去割情戀，遄征日遐邁。
悠悠三千里，何時復交會。
念我出腹子，匈臆為摧敗。
既至家人盡，又復無中外。
城廓為山林，庭宇生荊艾。
白骨不知誰，縱橫莫覆蓋。
出門無人聲，豺狼號且吠。
煢煢對孤景，怛吒糜肝肺。
登高遠眺望，魂神忽飛逝。
奄若壽命盡，旁人相寬大。
為復強視息，雖生何聊賴。
託命於新人，竭心自勖勵。
流離成鄙賤，常恐復捐廢。
人生幾何時，懷憂終年歲。
---&gt;

===Unit 5: Myths and Legends of East Asia===
&lt;!--- Shanhaijing, Zibuyu... Etc. Zhiguai literature. This aims to provide a counterpoint to what Confucius wouldn't discuss - thus Zibuyu. Going straight into Daoism isn't ideal. ---&gt;
# [[/Exploring the World of Mountains and Seas/]]&lt;!-- Structure: 出焉 --&gt;
# [[/Oh, the Qilin!/]] &lt;!--- Even here, the odes can be studied! ---&gt;
# [[/Ultimate Justice with Xiezhi/]] 
# [[/The Virtue of the Fenghuang/]] 
# [[/The Entrapment of Hua Po/]] 
# [[/Nüwa Created the World/]] 

===Unit 6: Nation Focus - Japan===
# [[/The Inariyama Sword/]] 
&lt;!--- short and sweet! ---&gt;
# [[/Entering Japan with Takeda Shingen/]]
&lt;!---
便面蘆間有漁·武田信玄
山色水光烟接天，漁翁江上棹蘆辺
丹青若写得勝景，万里風波一釣船

便面半月照梅花·武田信玄
蘆葦清風垂頂絲，窺魚白鷺水生涯
江南記得曾遊夕，似見梨花院落時

島森哲男. (2015). 武田信玄漢詩校釈. 宮城教育大学紀要, 49, 333–352. https://mue.repo.nii.ac.jp/records/440

似 is a really useful thing to teach early on. 
---&gt; 
# [[/The Oldest Inscription in Japan/]] 
&lt;!--- 宇治橋断碑 ---&gt; 
# [[/The End of a Rebellion/]] 
&lt;!--- https://www.fanyahanwen-corpus.cn/corpus_viewer/%E6%97%A5%E6%9C%AC%E6%BC%A2%E6%96%87/clean/%E6%97%A5%E6%9C%AC/%E6%B1%9F%E6%88%B8%E6%99%82%E4%BB%A3/%E8%9D%A6%E5%A4%B7%E5%85%B1%E5%92%8C%E5%9B%BD/%E5%9C%A8%E6%B5%B7%E7%89%99%E5%BA%9C ---&gt;
# [[/Shinto Teachings with Honda Chikaatsu/]] 
&lt;!--- https://wikisource.org/wiki/%E9%81%93%E4%B9%8B%E5%A4%A7%E5%8E%9F 本田親徳 道之大原 ---&gt;  
# [[/The Diary of Fujiwara no Teika/]] 
&lt;!--- 明月記 ---&gt;
# [[/Reading the History of Japan with Prince Toneri/]]
&lt;!--- 日本書記, etc. ---&gt; 
&lt;!--- # [[/Occupying Taiwan/]] ---&gt;
&lt;!--- I have some colonial literature on me that can be used here. ---&gt;

===Unit 7: Nation Focus - Korea===
&lt;!--- 三國史記 for sure! ---&gt;
&lt;!--- 放蟬賦 by Yi Kyubo ---&gt;
&lt;!--- https://zh.wikisource.org/wiki/%E9%A0%A4%E9%BD%8B%E9%81%BA%E7%A8%BF 頤齋遺稿 黃胤錫 Joseon scholar! ---&gt;
# [[/An Elegy to the Empress with Choe Ja/]]
&lt;!---
Choe Ja
元德大后輓詞·崔滋（최자）
乾極曾客配,坤儀正體元。
枕前朝聖主,帳底見曾孫。
陰慘俄沉月,屋悲便沒軒。
三韓千古淚,七十九年恩。
---&gt;
# [[/Language Reform with Sejong the Great/]]
&lt;!--- 訓民正音 https://github.com/ShiraTheMogul/fanyahanwen-corpus/commit/1ef2b42cc50055affaa5ef39c61b87ed31c34a60 multiple poems and descriptive terms, possibly the best capstone ---&gt;

===Unit 8: Christian Literature===
# [[/A Different Three Character Classic with Hong Xiuquan/]]
# [[/Friar Juan Cobo's Veritable Record/]] 
&lt;!--- 
One of few texts from the Philippines that I have ever found!
https://bnedigital.bne.es/bd/en/viewer?id=0160187c-9d9b-4f34-84d6-bc03fd310c69 
---&gt;
# [[/The Delegate's Edition/]]
# [[/Nestorian Steles during the Tang/]] 
&lt;!--- 大秦景教宣元至本經經幢 and 景教碑 ---&gt;
# [[/Hong Xiuquan's Bible/]]
&lt;!--- https://bible.fhl.net/ob/nob.html?book=407 ---&gt;
&lt;!--- I don't want to focus too much on Hong Xiuquan here, so look for more material, especially from missionaries. ---&gt;

===Unit 9: An Introduction to Daoism===
&lt;!--- And now back to your regularly scheduled Zhuangzi/Laozi/Liezi. But with more interesting stuff. Trust! ---&gt;
# [[/Laozi Explains the Dao/]]
&lt;!--- 道可道，非常道。名可名，非常名。無名天地之始；有名萬物之母。故常無欲，以觀其妙；常有欲，以觀其徼。此兩者，同出而異名，同謂之玄。玄之又玄，衆妙之門。I can expect learners to recognise the stuff here. ---&gt;
# [[/Qingtan with Xie Daoyun/]]
&lt;!--- 謝道韞; mentioned in the sanzijing. could be good!

《泰山吟·謝道韞》
峩峩東嶽高，秀極衝青天。
巖中間虛宇，寂寞幽以玄。
非工復非匠，雲構發自然。
器象爾何物，遂令我屢遷。
逝將宅斯宇，可以盡天年。

《拟嵇中散咏松诗·謝道韞》
遙望山上松，隆冬不能凋。
願想遊不憩，瞻彼萬仞條。
騰躍未能升，頓足俟王喬。
時哉不我與，大運所飄遙。

---&gt;
# [[/The Doubting Neighbour/]] 
# [[/Kuafu Chases the Sun/]] 
# [[/The Frog in a Well/]] 
# [[/Wu wei with King Hui of Liang/]]
# [[/The Old Man that Moves the Mountains/]]
# [[/Master Zhuang Dreams of Butterflies/]]
# [[/The Indifferent Taoist/]] &lt;!--- northern song https://zh.wikisource.org/wiki/%E7%8E%89%E6%AD%B7%E5%AF%B6%E9%88%94 ---&gt; 
&lt;!--- Currently very stereotypical, but there's stuff to work with at least. Need to include those weird Daoist characters among other things. ---&gt;

===Unit 10: Nation Focus - Ryukyu Kingdom===
# [[/Historical Annals with Sai On/]] &lt;!--- Kyuko is an easy cop ---&gt;
# [[/The Enthronement of Shō Tei/]] 
&lt;!---
康熙二十二年封王尚貞敕
皇帝敕諭琉球國中山王世子尚貞：惟爾遠處海隅，虔修職貢；屬在塚嗣，序應承祧。以朝命未膺，罔敢專擅；恪遵典制，奉表請封。朕念爾世守臣節，忠誠可嘉！特遣正使翰林院檢討汪楫、副使內閣中書舍人加一級林麟焻，齎敕封爾為琉球國中山王，並賜爾及妃文幣等物。爾祗承寵眷，懋紹先猷；輯和臣民，慎固封守：用安宗社於苞桑，永作天家之屏翰。欽哉，毋替朕命！故諭。

Teach imperial edicts. 
Consider seeing if there's a letter of acceptance from Shō Tei. 

Recorded in 琉球國志略 
https://ctext.org/wiki.pl?if=en&amp;chapter=966326
---&gt;
# [[/The Twilight of Ryukyu with Shō Ten/]] 
&lt;!---
神田酒樓街燈 尚典
酒樓今秋設芳筵，
一望街燈燦燦連。
烟氣引來通柱上，
光爭星月照神田。
---&gt;
# [[/A Trip to Ryukyu with Luo Sen/]] &lt;!--- Pre-Capstone ---&gt;
&lt;!---
遐邇貫珍 1854-11 - 日本日記 羅森 
https://archive.org/details/HEKC185411/page/n5/mode/1up
A solid description of Ryukyu cultural customs in Volume 11. Absolutely incredible. 
日三日火船直向東北而駛出了臺灣之外幾日不見天涯是時北風大作波浪沖天火船亦甚飄蕩而不能立見有沙鷗隨風而逐浪心直駛七日漸見小山而到琉球琉球一國長闊一百七十五里其國城在地球圖緯線赤道之北二十六度十四分經線中華北京偏東十一度二十四分自明以來世封王爵叨列藩籬其處土產不過蔬菜番薯菜油黑糖等類人民束髻大補是穿草履男女粧飾頭上祇插一簪二簪為別故少年之男女瞥目則無異及其壯也皆留鬚髯故街上長鬚之人甚多甲寅正月初一予上岸遊玩見街上兒童甚多分以銅錢各極歡喜人民亦甚謙恭民居間亦貼新春聯于門外但不見有別等繁華之事那霸有寺寺內有園是名家世宦之墳所以石刊刻姓名年號于碑上每日道人打掃供奉生花樹葉于墓前另有人家祖墳與中國之明塚無異峰巒之上樹木多植民房則以蠻石圍墻內以茅草結屋而居佳物椅棹俱無惟以草蓆屈膝而坐對火盆而吹煙民間亦有識中國言語字墨者
不張舖店惟有墟塲男不貿易婦女為之以貨易貨而外方之金銀弗尚焉然而百姓亦甚畏官長飲食亦甚粗粕甘守樸儉不務奢華亦鮮欺詐板門紙窓夜間亦不防竊曾見途中撿物亦能以返原人公門之內冷冷落落並無案牘之煩淳樸之風畧有同于上古之世我等外國之欲買什物須言于官官為代辦正月初六提督被理衛廉士等一班將官布列威嚴與予乘轎至王宮總理大臣尚宏勳為主席布政大夫馬良才為知客享宴甚豐食物多與中國無異宴後各官皆饋有紙扇烟包布帛等項是物雖粗此亦世子之恭敬外國故亞國亦以禮物而返贈之世子王宮離岸三里在于山頂是名守禮將至其宮一路亦有樹木石牌坊宮室亦甚寬大幽雅垣局可觀其處多栽鳳尾草森樹等類以障陰山邊田土樹藝五穀近海沙田水漲之後人收其沙以煎鹽此時明月當圓予覽山川亦足見一方之風景 
---&gt;
&lt;!--- 中山世鑑 and so on. Lots of poetry too. ---&gt;

===Unit 11: Nation Focus - Singapore===
&lt;!--- National Library of Singapore has a poetry series that's super good! ---&gt;

===Unit 12: Literary Chinese in Medicine===
&lt;!--- do not endorse the medical practices discussed in these...make sure to link back to the heavenly stems here as they are associated with specific body parts. ---&gt;
# [[/The Books of the Yellow Emperor/]] 
&lt;!-- 黃帝内徑 ---&gt;
# [[/Deviant Qi with Zhang Congzheng/]]
&lt;!--- https://zh.wikisource.org/wiki/%E5%84%92%E9%96%80%E4%BA%8B%E8%A6%AA ---&gt;
# [[/Anatomy with Sugita Genpaku/]]
&lt;!--- 解体新書 ---&gt;
# [[/A Lost Wu Medical Text analysed in Japan/]]
&lt;!--- 難經古義 ---&gt;

===Unit 13: People Focus - Zhuang peoples===
&lt;!--- https://mooc1.chaoxing.com/mooc-ans/ztnodedetailcontroller/visitnodedetail?courseId=84745403&amp;knowledgeId=84745463&amp;_from_=&amp;_fromV2_=&amp;rtag= 《峤西诗钞》 is also a really good shout. ---&gt;
&lt;!--- Basically, there are Zhuang and Tangut peoples who wrote in Literary Chinese, and their inclusion here is to show that even those who made their own scripts would use this tongue. 张鸿翮 imported the character 朴 to describe a bug, for example. ---&gt;
# [[/Zhuang poetry with Zhang Honghe/]]
&lt;!--- https://wenyi.gmw.cn/2024-06/25/content_37398911.htm

一是忠实记录了汉诗创作与古壮字交融的文化现象。清代壮族诗人张鸿翮（hé）《大塘谣》（《峤西诗钞》卷二）云：

去了休。去到大塘红蓼洲。红蓼生花，不结子。绿朴生花，毬见毬。

诗中所说“绿朴”，是壮族对柚子的惯称。“柚子”，壮语发音为“bug”。根据《古壮字字典》，其对应的古壮字为“朴（㭪）”。诗人将古壮字运用到汉文诗歌创作中，刻下了明清壮汉文化交相辉映的注脚。

This sort of thing is why Zhuang and Tangut inclusion is important, as they show how flexible Literary Chinese can be. ---&gt;

&lt;!---
Possible Jurchen/Khitan focus? 
耶律楚材 - Served 窝阔台, 玄風慶會錄 is short and respectable enough to work with.
---&gt;

===Unit 14: People Focus - Tangut peoples===
&lt;!--- 羅福萇 and 羅振玉 wrote studies on Western Xia / Tangut script. Look for poets and stuff. ---&gt; 

===Unit 15: Literary Chinese in the Military===
&lt;!--- Real Sun Zi hours! 7 Military Classics are an obvious shout, but look for more stuff too. ---&gt;
# [[/A Bilingual Stele of the Khitans/]]
&lt;!--- https://wikisource.org/wiki/%E5%A4%A7%E9%87%91%E7%9A%87%E5%BC%9F%E9%83%BD%E7%B5%B1%E7%B6%93%E7%95%A5%E9%83%8E%E5%90%9B%E8%A1%8C%E8%A8%98 ---&gt;
# [[/Going to war with Boyan/]]
&lt;!---
Boyan's Poem from the 元史
　　伯顏，蒙古巴林部人。至元十一年拜中書左丞相，總兵伐宋。官至開府儀同三司，薨贈太師，封淮安王，諡忠武。

　　《玉堂嘉話》：初，宋未下時，江南謠云：「江南若破，白雁來過。」當時莫喻其意。及宋亡，蓋知指丞相巴延也。

　　過梅嶺岡留題

馬首經從庾嶺回 【 庾嶺回　七修類稿（乾隆刊本）卷四十六作「嶺島歸」。】 ，王師到處悉平夷。擔頭不帶江南物，只插梅花一兩枝。

　　《七修類藳》：伯顏下江南，過金陵梅嶺岡詩云云。所以著名，亦有是善。
---&gt;
# [[/An Edict from the Xianbei/]]
&lt;!---
教義詔 楊廣
武有七德，先之以安民。政有六本，興之以教義。高麗高元，虧失藩禮，將欲問罪遼左，恢宣勝略。雖懷伐國，仍事省方。今往涿郡，巡撫民俗。其河北諸郡及山西、山東年九十已上者，版授太守；八十者，授縣令。
---&gt;
# [[/The Suppression of the Kingdom of Dongning/]]
&lt;!---
台灣鄭氏始末
https://ctext.org/wiki.pl?if=en&amp;chapter=139938

Largely a record of wars in Dongning rather than anything about the trade etc, so it fits here. 
---&gt;
# [[/The Shunzhi Emperor vs Li Zicheng/]]
&lt;!---
順治帝
告示
逆酋李自成已於通城斃命，各地鄉勇務隨我軍剿殺逆賊殘餘,凡有斬獲逆酋及擒獲逆酋交我軍者，一經驗證，按軍功論級給賞，必以示我朝皇恩浩蕩。
大清順治二年五月二十四日

恩詔
今月何日，為國曆改歲之履端,即為永昌書元之紀念？緬惟我朝民眾，三元肇慶，四始發祥。陳椒酒以飛觴，躋堂介壽；換桃符以獻歲，辟戶書新。翹望德容，河勝額手。今山河如舊，歲序更新;今天下同春，咸頒麗澤。願我朝君臣與萬民同樂，共沐化日光天，方不虛度韶華。
永昌二年新正初一

There's probably better choices here. Review. 
---&gt;
# [[/The Art of War/]]

===Unit 16: Nation Focus - Vietnam===
&lt;!--- https://github.com/ShiraTheMogul/fanyahanwen-corpus/commit/cfe6700e01f6fd59616a375d31aa8cd096677be1 this first ---&gt; 
# [[/Ancestor Veneration with the Descendants of Zhu Xi/]] 
&lt;!--- https://github.com/ShiraTheMogul/fanyahanwen-corpus/tree/main/corpus%2F%E8%B6%8A%E5%8D%97%E6%BC%A2%E6%96%87%2Fclean  somewhere in here ---&gt;
# [[/Spreading Revolutionary Consciousness with Phan Bội Châu and Liang Qichao/]] 
&lt;!--- 越南亡國史 Possibly the most important text in Vietnamese history, not even gonna lie. https://zh.wikisource.org/wiki/%E8%B6%8A%E5%8D%97%E4%BA%A1%E5%9C%8B%E5%8F%B2 ---&gt;
# [[/Academia in Literary Chinese between East and West/]] 
&lt;!--- 南風雜誌 is a massive shout here. Absolutely amazing series. ---&gt;

===Unit 17: Historical Annals and Encyclopediae===
&lt;!--- 永樂大典 will teach how to infer from gaps in texts! 《編類》 is an incredibly interesting essay from here that can bring up the odes and Confucius's「思無邪」quote. It can prepare students for the wrath of Qing academia later. ---&gt; 
# [[/The History of Liao, Jin, and Song with Toqto'a/]] &lt;!--- 脱脱 ---&gt;
# [[/Two Years in the Forbidden City with Yu Deling/]] &lt;!--- 清宮禁二年記 https://zh.wikisource.org/wiki/%E6%B8%85%E5%AE%AE%E7%A6%81%E4%BA%8C%E5%B9%B4%E8%A8%98 ---&gt;
# [[/Selected Records of the History of the Da Shun/]]
&lt;!--- Fair Use of a 2010 book written in Literary Chinese about the Da Shun dynasty. Limit to 500 characters, if that. Use to encourage recognition of Simplified variants and modern Wenyanwen. ---&gt;
# [[/Documenting the World with Terajima/]]
&lt;!--- 和漢三才図会 寺島良安, built off 三才圖會 ---&gt;

===Unit 18: Buddhist Literature===
&lt;!--- You would be forgiven for wondering why this is so late, but if you look at many classical Buddhist texts you'll quickly see a ton of loanwords that make it significantly more difficult to read than the average text. Thus, it goes here for now. ---&gt;
&lt;!--- Place focus on practical stuff first. Stuff you can and WILL see in Buddhist temples. Stuff Buddhists can take away immediately. Skills-based approach feels strongest here. ---&gt;
&lt;!--- Look at Northern Liang and Later Qin literature, as there is a ton of work by translators from India during the 16 kingdoms period, particularly those two. ---&gt;
&lt;!--- Stuff by Bodhidharma 達摩 could be fun too https://zh.wikisource.org/wiki/Author:%E9%81%94%E6%91%A9 ---&gt;
# [[/Dipping your feet in with Wenyan Shu/]]
&lt;!---
華亭
世尊遺法本忘言，教外別傳意已圓。
只履攜將蔥嶺去，不妨來上月明船。
---&gt; 
# [[/The Seven Tathagatas/]] 
&lt;!---
南無寶勝如來
南無多寶如來
南無妙色身如來
南無廣博身如來
南無離怖畏如來
南無甘露王如來
南無阿彌陀佛

Use to introduce some core vocabulary in repetitive manner. 

Useful phrases from my trip to Jing'an Temple
南無本師釋迦牟尼佛 - Pay homage to the root teacher
南無大悲觀世音菩薩 - Pay homage to the goddess of mercy 
廣種福田 - widely plant a meritorious field 
---&gt;
# [[/Two Buddhist Temples in Shanghai/]] 
&lt;!---
留雲禪寺
雲留雲翔領畧幾許禪機此地有雲散天開真如界。
塔內塔外普示無邊圓覺是故曰塔影雙照解脫門。

歲次壬午冬月吉旦。
覺醒敬撰。
楊胡生沐手恭書。
善信印利明敬獻。 
---&gt;
&lt;!--- 福慧宝鼎 慧明大和尚 - introduce the Buddhist timekeeping system with 佛歷 around this point. 
赤烏古剎
建寺一千七百六十周年紀念

古剎三國建
滬瀆有重玄
石佛音淨現
聖跡顯重元
唐時稱永泰
宋敕名靜安
聖祖留佛闡
仲師移伽藍
元收八景偈
明鑄鐘聲梵
清樹化羅漢
選賢十方讚
佛日普光明
福慧共修善
鼎運昌隆際
轉正法輪緣

歲次丁亥住持慧明監製
---&gt;
# [[/Foreseeing Monkhood with Yi Xing/]]
&lt;!--- 看命一掌金 ---&gt;
# [[/A Trip to Western Xia with Zhi Guang and Hui Zhen/]]
&lt;!--- https://zh.wikisource.org/wiki/%E5%AF%86%E5%91%AA%E5%9C%93%E5%9B%A0%E5%BE%80%E7%94%9F%E9%9B%86 ---&gt;
&lt;!--- https://zh.wikisource.org/wiki/%E5%AF%86%E5%92%92%E5%9C%93%E5%9B%A0%E5%BE%80%E7%94%9F%E9%9B%86 ---&gt;
# [[/Jizang's Three Discourses/]]
&lt;!--- https://zh.wikisource.org/wiki/%E4%B8%89%E8%AB%96%E7%8E%84%E7%BE%A9 ---&gt;
&lt;!---
I saw these texts being quoted and thus should consider them in some capacity.
《般若波羅蜜多心經》
《金剛般若波羅蜜經》
《一切智光明仙人慈心因緣不食肉經》
《妙法蓮華經》
《大般涅槃經》
《大方等大集經》
《大毘盧舍那成佛神變加持經蓮華胎藏悲生曼荼羅廣大成就儀軌供養方便會》/ 胎藏曼荼羅 
《佛說救拔焰口餓鬼陀羅尼經》
《雜阿含經》

Look at Japan's 五山文学
---&gt;

===Unit 19: People Focus - Manchu peoples===
# [[/Qing dynasty Poetry with Nara Singde/]] 
&lt;!--- 飲水詞 納蘭性德 https://zh.wikisource.org/wiki/Author:%E7%B4%8D%E8%98%AD%E6%80%A7%E5%BE%B7 ---&gt;
# [[/Amassing Words with the Kangxi Emperor/]] 
&lt;!--- Kangxi Dictionary Abstract - https://zh.wikisource.org/wiki/%E5%BA%B7%E7%86%99%E5%AD%97%E5%85%B8 ---&gt;
# [[/Amassing Literature with the Qianlong Emperor/]] 
&lt;!--- Siku Quanshu abstract https://zh.wikisource.org/wiki/%E5%9B%9B%E5%BA%AB%E5%85%A8%E6%9B%B8%E7%B8%BD%E7%9B%AE%E6%8F%90%E8%A6%81 ---&gt;
&lt;!---
Yongzheng Emperor's Poetry 
https://zh.wikisource.org/wiki/Author:%E9%9B%8D%E6%AD%A3%E5%B8%9D
《和碩怡賢親王祭文》

Also include 滿洲國 stuff to show the fall of the Qing and attempts to preserve it through becoming a Japanese puppet state. It is important to show how Literary Chinese can be misused as well. 滿洲國建國宣言 is a good shout, as is 法制 to prepare students who may be interested in Taiwan legal stuff later down the road. 
https://zh.wikisource.org/wiki/Category:%E6%BB%BF%E6%B4%B2%E5%9C%8B
---&gt;
# [[/Paintings and Beauty with Puru Aisin-Gioro/]]
&lt;!--- Saw these in Shanghai Museum with some writing, seemed really cool. Teaches another skill. ---&gt;

===Unit 20: Qing-RoC Literature===
&lt;!--- many writers here, will be difficult to sift through. Include 四库全書 abstracts and stuff here. ---&gt;
# [[/Jewish Refugees in Shanghai/]] 
&lt;!--- Show passports, certificates, etc, from the Jewish Refugee Museum, anonymised. ---&gt;
# [[/A Literary Chinese Abstract/]] 
&lt;!--- Abstracts from siku quanshu, probably want others ---&gt;
# [[/Lament with Lu Ruoteng/]] 
&lt;!---
《疑猜》盧若騰，東寧國
盟誓變為交質子，春秋戰國風如此；末世上下相疑猜, 更質妻子防逃徙。
此法只可羈庸奴，若遇梟雄術窮矣；妻可再娶子再育, 安能長坐針氈裏。
我贈一法君記存；推心置腹人知恩；眾人畜之眾人報, 幾個國士在君門。
盧若騰撰，陳漢光編輯，《島噫詩》，臺灣文獻叢刊第二四五種（臺北:臺灣銀行經濟研究室，1968年）21頁。
---&gt;
# [[/Common Linguistics Knowledge in the RoC/]]
&lt;!--- 音韻常識 ---&gt;

==References used for this page==
* Yang, B. (2016). 文言语法 [Literary Chinese Grammar] (1st ed). 中华书局 [Zhonghua Book Company]. ISBN: 978-7-101-11619-9
* Priestley, K. E., &amp; Shou-jung, C. (1962). China’s Men of Letters, Yesterday and Today. Dragonfly Books.
{{BookCat}}</text>
      <sha1>h0l569eol7bhheaqu1owj7mimrruozy</sha1>
    </revision>
    <revision>
      <id>4656081</id>
      <parentid>4656071</parentid>
      <timestamp>2026-08-02T18:01:01Z</timestamp>
      <contributor>
        <username>Shira the Mogul</username>
        <id>3560559</id>
      </contributor>
      <minor />
      <comment>/* Unit 15: Literary Chinese in the Military */ this seems fun to include as it also prepares a student for the art of war</comment>
      <origin>4656081</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="39861" sha1="998ddx6b7954prnyi0tub6xxsi68op9" xml:space="preserve">__notoc__

Welcome to the Wikibook for Literary Chinese (Known as 漢文 &quot;Han Language&quot; in East Asia or 文言 &quot;Literary Language&quot; in China), aimed at individuals hoping to gain a general knowledge of it before progressing into genres they wish to be acquainted with. 

This is not the [[Classical Chinese]] textbook, which is aimed at Chinese Zhou-Qin era texts. This  text aims to shed light on post-Zhou-Qin texts across East Asia, which mimic those texts. However, as Zhou-Qin era texts served as the main body from which individuals learned, they are employed here as and when they are considered necessary or otherwise useful. It does so through a &quot;buffet&quot; approach, showering you, the reader, with an ocean of texts of myriad genre. 

==Table of Contents==

=== Front matter ===

* [[/Introduction/]]
* [[/Appendices/]]

=== Useful resources ===
These are quick grab-bags that can be useful for vocabulary-building. 
* [[/Antonym List/]] &lt;!--- 文/武，大/小，厚/薄，橫/縱...---&gt;
* [[/Collocation Groups/]] &lt;!--- e.g. 四象，三靈…… ---&gt;
* [https://zh.wikiversity.org/wiki/Subject:華製新漢語及中文固有語/嚴譯及部定詞等 Yan Fu's Qing-era translations for modern terms] &lt;!--- Wikiversity has this (https://zh.wikiversity.org/wiki/Subject:華製新漢語及中文固有語/嚴譯及部定詞等) and the below, I will effectively be translating a lot of it! ---&gt;
* [https://zh.wikiversity.org/wiki/Subject:華製新漢語及中文固有語/上古語考輯 Communicative Terms]
&lt;!--- this will be translated eventually, but right now it's bad to just leave this here. ---&gt;

=== Useful primers ===
Across history, many primers have been made for teaching Literary Chinese to children. These are a few that are recommended for use alongside this work, ideally in flashcards. 
* [https://www.fdgwz.org.cn/Web/Show/11308 倉頡篇] - Cangjie's Chapters, the earliest one. It is extant, but incomplete. It contains several rare characters, and so if used, I would personally recommend doing so later, or out of interest. 
* 三字經 - The Three Character Classic, an excellent piece for Confucian education. Pair with 弟子规 for best results. 
** 三字經（太平天國版）- For Christians, there is a version made by Hong Xiuquan from the Taiping Rebellion. Despite the context, it is a legitimately useful primer and can be used to self-teach for the Delegate's Edition of the Christian Bible. 
* 千字文 - The Thousand Character Classic, a remarkable piece of constrained writing that only uses each character once. Amazing for building vocabulary whilst seeing historical allusions and the like. 
* 五字鑑 - The Five-Character Mirror, essentially the 24 Histories of China compressed into a primer. Uses 5-character couplets, the longest in this list. 
* 龍文鞭影 - The Shadow of Longwen's Whip, a historical allusion trainer. Best paired with a context piece.

===Unit 0: The Han script===
This unit is intended for those with no familiarity of the Han script. It will prepare you for the units ahead, teaching largely pictographic characters. 

By the end of this unit, students will:
* Recognise around 50 characters.
* Understand how characters are composed and how this gives them meaning.
* Have a basic idea of how to handwrite and/or type characters using the Cangjie Input Method.
* Know some bare basics of Literary Chinese grammar (e.g. Basic word order, where adjectives go, lack of &quot;is&quot;, 有...)

Lessons:
# [[/An Introduction to the Han Script/]]
# [[/People, Big and Small/]]
# [[/How do we write Chinese?/]]
# [[/What are Chinese characters, anyway?/]]
# [[/The Sun, the Moon, and the Five Elements/]]
# [[/Getting Familiar with Body Parts/]]
# [[/Using Numbers and Using Weapons/]] &lt;!--- 竹戈十大中一弓廿卜---&gt;
# [[/Tilling the Fields with 有/]] &lt;!--- 山田 ---&gt;
# [[/How Characters are Made/|How Characters are Made with Kiyohara no Sanemoto]] 
# [[/Cangjie Created Characters/]] &lt;!--- Get people to use Cangjie ---&gt;
# [[/The Kangxi Radical System/]] &lt;!--- Introduce some monoradical texts to train recognition. ---&gt;

===Unit 1: Basic Skills===
This unit is intended for those with minimal familiarity with the Han script and no familiarity with Literary Chinese. There is a focus on simple structures, skills for dissecting common textual structures, and short-form poetry in this unit. 

Before starting this unit, students should:
* Recognise around ~30 characters. 
* Can use Cangjie input. 
* Have given Unit 0 a cursory glance. 
&lt;br&gt;
By the end of this unit, students will:
* Recognise around ~100 characters. 
* Comprehend numbers, the Heavenly Stems, and the Earthly Branches, and be able to use them to quantify time and date.
* Intuit the basic topic -&gt; comment idea behind Literary Chinese. &quot;This, it is...&quot; 
* Understand basic function words such as 也, 而, 有, and 謂.

Lessons:
# [[/The All-Purpose 也/]]
# [[/An Introduction to Chinese Numbers/]] &lt;!--- It is hard to find authentic materials for this ---&gt;
# [[/One, Two, Left, and Right with Gongsun Long/]]
&lt;!---
曰：「二有一乎？」

曰：「二無一。」

曰：「二有右乎？」

曰：「二無右。」

曰：「二有左乎？」

曰：「二無左。」

曰：「右可謂二乎？」

曰：「不可。」

曰：「左可謂二乎？」

曰：「不可。」

曰：「左與右可謂二乎？」

曰：「可。」
---&gt;
# [[/The Heavenly Stems/]] &lt;!--- Introduce ordinals, which will be used to demonstrate sentence patterns later. ---&gt;
# [[/Tell the Time with Earthly Branches/]] &lt;!--- Introduce verbs and timekeeping ---&gt;
# [[/Lunar Dates with the Spring and Autumn Annals/]]
&lt;!--- Vocabulary: 歲，年，朔，月，日，來，前，初，正，春秋夏冬，曆，上，下. Consider including traditional names for months in a list. ---&gt;
# [[/Skimming for Major Events in Historical Annals/]] 
&lt;!--- Don't simply use Confucius's Chunqiu: We can use texts inspired by it. 

E.g. 三國史記 - 十五年京城旱。秋七月，蝗。very few new characters, lots one can use. Instantly able to use. 
https://zh.wikisource.org/wiki/%E4%B8%89%E5%9C%8B%E5%8F%B2%E8%A8%98/%E5%8D%B701

Skimming annals is very possible and a very useful skill. Don't skip out on it. Teach students to skim read!!! 
---&gt;
# [[/Dinner with the Daimyo/]]
&lt;!-- 
侍宴·大友皇子
皇明光日月，帝徳載天地。
三才併秦昌，万国表臣義。
--&gt; 
# [[/In Discourse with Jibong/]]
&lt;!--
芝峰類說 
倭國謂田爲畠。謂水田爲田。火田爲畑。猶我國以水田爲畓也。故官名有畠山殿。地名有畑島云。
--&gt;
# [[/Shinto FAQ with Honda Chikaatsu/]] 
&lt;!--- https://wikisource.org/wiki/%E7%9C%9E%E9%81%93%E5%95%8F%E5%B0%8D 眞道問對 本田親徳 really good way of operationalising 乎 and much of the early grammar. 

問 天帝無始無終乎。
對 天帝無始無終也。
旣以無始無終之力
與無始無終之體
造無始無終之萬物。
其功亦無始無終也。

問 天地大原在道乎。
對 天地大原實在道。
鬼神依道而立。
人民依道而活。
萬物依道而息。

This is great! ---&gt;

&lt;!---
Some cool stuff I saw someone studying from
https://zh.wikisource.org/wiki/%E8%87%B3%E5%B0%8F%E4%B8%98%E8%A5%BF%E5%B0%8F%E7%9F%B3%E6%BD%AD%E8%A8%98#
https://zh.wikisource.org/wiki/%E6%A0%B8%E8%88%9F%E8%A8%98

Could be used for period focus
---&gt;

===Unit 2: An Overview of Sinitic Poetry===
This unit will teach you how Sinitic Poetry operates; - that is, the way individuals in the Sinosphere compose poetry in Literary Chinese. Despite this language's fall out of favour in the past century, this tradition is still remarkably alive and well, and their short length makes them more accessible than elaborate prose. In this unit, you will begin from the ''Classic of Poetry'' before travelling through poems from the Tang dynasty, Singapore, Japan, Vietnam, the Ryukyu Kingdom, and Korea. When introducing poetry, I will furthermore use the language from the nation it is from to show how it is recited by its people. 

After discussing the Classic of Poetry, we will also be a small detour into a discussion on Ping-Ze 平仄, the Tang dynasty system of alternating tones, so to produce rhyme on tonal and phonological levels. This had a major impact on Literary Chinese poetry as a whole!

By the end of this Unit, students will:
* Recognise around 120 more characters.
* Be able to explain how Sinitic Poetry rhymes and the themes it contains.
* Be able to use function words such as 在, 無, 不, 聿, and 于/於 in poetic contexts.
* Recognise the switch between 吾/我 in the subject-object positions and demonstrate it in usage.
* (Chinese speakers) Be able to differentiate 于 and 於, and understand the &quot;interest(ed) in&quot; meaning of 好 in most circumstances.
&lt;!---
Summary of the above part about 于 and 於 for other editors:
于 and 於 were distinct words for an extremely long time and were still such to Literary Chinese writers. Their &quot;merging&quot; through Simplified-Traditional Chinese distinctions is a very modern thing. I will summarise their usages here, using Pulleyblank's Outline of Classical Chinese Grammar (2000);
* 于 - This can mean &quot;to go&quot; or &quot;to/at&quot;. 黃鳥于飛 &quot;The yellow birds go flying&quot;. Must be post-verbal. It can also appear in 至于.
* 於 - This is an all-purpose locative preposition - from &quot;on/at/in&quot; to &quot;from&quot; or even &quot;than&quot; (甲於乙). The implication of motion is not there at all. Must be pre-verbal. It can also appear in 之於 or be an archaic noun for a crow 於 (烏).
---&gt;

Lessons:
# [[/Across the Rivers with Emperor Puliuru Guang/]]
&lt;!---
春江花月夜·楊廣
夜露含花氣，春潭漾月暉。
漢水逢遊女，湘川值二妃。

This is really simple and can elucidate Ping-Ze easily.
---&gt;
# [[/To Study the Odes/]] 
&lt;!-- 蟋蟀·姬旦 國風·唐風
蟋蟀在堂，歲聿其莫。今我不樂，日月其除。無已大康，職思其居。好樂無荒，良士瞿瞿。
蟋蟀在堂，歲聿其逝。今我不樂，日月其邁。無已大康，職思其外。好樂無荒，良士蹶蹶。
蟋蟀在堂，役車其休。今我不樂，日月其慆。無已大康，職思其憂。好樂無荒，良士休休。
--&gt;
&lt;!-- 黃鳥 小雅·鴻鴈之什
黃鳥黃鳥，無集于穀，無啄我粟。
此邦之人，不我肯穀。言旋言歸，復我邦族。

黃鳥黃鳥，無集于桑，無啄我粱。
此邦之人，不可與明。言旋言歸，復我諸兄。

黃鳥黃鳥，無集于栩，無啄我黍。
此邦之人，不可與處。言旋言歸，復我諸父。
--&gt;
# [[/A Detour into Orthodox Ping-Ze/]] 
&lt;!--- 平 and 仄 are useful characters themselves. Show 仄 in the binomes 反仄，歉仄，逼仄 as it's often difficult to immediately use ---&gt;
# [[/The Restraint of Du Fu/]] 
# [[/The Longing of Li Bai/]] 
# [[/The Environment with Bukha Timur/]]
&lt;!---
西湖竹枝詞·布哈特穆爾
湖上春歸人未歸，桃紅柳緑黄鶯飛。
桃花落時多結子，楊花落處秪沾衣。

宫词·布哈特穆爾
玉樓珠箔晚天涼，秋色依稀滿建章。
金井梧桐霜葉盡，自隨流水出宮牆。

Mongol writer from the Uyghur Kingdom of Gaochang
Spammed Ctrl+F in https://zh.wikisource.org/wiki/%E5%BE%A1%E9%81%B8%E5%9B%9B%E6%9C%9D%E8%A9%A9_(%E5%9B%9B%E5%BA%AB%E5%85%A8%E6%9B%B8%E6%9C%AC)
---&gt;
# [[/Pillow Talk with Guan Yunshi/]]
&lt;!---
紅繡鞋·貫雲石
挨著靠著雲窗同坐，偎著抱著月枕雙歌，聽著數著愁著怕著早四更過。四更過情未足，情未足夜如梭。天哪，更閏一更兒妨甚么！

Uyghur author!
---&gt;
# [[/Buddhist Philosophy with Ngô Chân Lưu and Taisei Shōan/]]
&lt;!-- 元火·吳真流
木中元有火，元火復還生。
若為木無火，鉆燧何有萌。--&gt;
&lt;!-- 杜鵑·大成聖安
夢覚孤床静
杜鵑帯雨飛
一声来近枕
何者不沾衣
--&gt;
# [[/Odes with Mō Taiei and Zheng Chengxun/]]
&lt;!-- 詠松·毛泰永
植體宜千仞，垂陰動百尋。
李膺真烈烈，和嶠自森森。
桃李何堪較，雪霜安得侵。
萬年身不老，種子又成林。
AKA Inoha Seiki 伊野波 盛紀 --&gt;
&lt;!-- 詠班蘭·鄭成勛
南國多芳草，班蘭最有名。
深根將綠茁，長葉亦叢生。
取味迎賓合，入厨任水烹。
可憐經一用，擲棄不留情。

鄭成勛《樵隱詩集》 https://nus.edu.sg/nuslibraries/dsprojects/sg-jiutishi/poem/827 --&gt;

# [[/A Golden Cup and the Fall of a Dynasty with Yan Fu/]] 
&lt;!---
鞏金甌·嚴復
鞏金甌，承天幬，民物欣鳧藻，喜同袍。
清時幸遭，真熙皞，帝國蒼穹保。
天高高，海滔滔。
This has music to it, which I think can add a lot. It is also necessary to introduce Yan Fu early given he did translation. ---&gt;
# [[/On a Journey with Sa Dula/]]
&lt;!---
無題·薩都剌
為客三年海上洲，故鄉何處瘴雲稠。
數千里外蠻人域，十八灘頭過客舟。
時有山禽呼姓字，或從海鳥作朋儔。
故人珂珮周旋處，紫殿風清十二樓。
https://zh.wikisource.org/wiki/%E7%84%A1%E9%A1%8C_(%E8%96%A9%E9%83%BD%E5%89%8C)

A naturalised Mongol scholar who made a beautiful poem. This'll be a capstone.
---&gt;
&lt;!---
朝中措·襄陽古道灞陵橋
襄陽古道灞陵橋，詩興與秋高。
千古風流人物，一時多少雄豪。

霜清玉塞，雲飛隴首，風落江皋。
夢到鳳凰台上，山圍故國周遭。

北郊晚步
陂水荷凋晚，茅檐燕去涼。
遠林明落景，平麓淡秋光。
群牧歸村巷，孤禽立野航。
自諳閑散樂，園圃意尤長。

Jurchen poet and grandson of Emperor Shizong of Jin. He's a Zen Buddhist, so we'll go back to him later.
---&gt;

===Unit 3: Confucianism and the World===
This is a Confucian-themed unit with a smattering of other items. You will see the odd geography of the past, early linguistic philosophy, and terrifying breakaway states!

By the end of this unit, students should be able to:
* Recognise around 200+ characters.
* Read basic annals and histories with some dictionary assistance, and comprehend 3-character structures reliably.
* Have encountered basic grammatical points such as 之、乎、者、也、而、則、乃、所、以、於、于、與、且、蓋、and 夫. 
** 於 and 于 should be distinguishable.
* Survive a text of at least 250 characters and read for gist.

Lessons:
# [[/A Brief Overview of Confucianism/]] 
# [[/The Mountains with Yelü Tuyu/]]
&lt;!---
立木海上刻詩 耶律圖欲 / 耶律倍 / 李贊華

小山壓大山，大山全無力。
羞見故鄉人，從此投外國。
---&gt;
# [[/Teaching the Annals in Qi/]] &lt;!-- Gongyang Gao's commentary --&gt;
# [[/Is a White Horse a Horse?/]]&lt;!-- Teach negation with 非 in 公孙龍子 and compare with 不 --&gt;
# [[/The Three Character Classic/]]
# [[/Expressing Filial Conduct with Confucius and Hara Saihin/]]
&lt;!--
次韻杏坪先生
父執有君孤不孤
相依遍接搢紳徒
区区自抱地方寸
杳杳重遊天一隅
羇雁飛鳴迷汝國
家人思夢入江都
如教志業青年遂
世上寧無逐臭夫
--&gt;
# [[/Confucianism and the Environment with Sai On/]]&lt;!-- 木假山記 --&gt;
# [[/In Debate with Mencius/]]

===Unit 4: Women's Writing===
In this unit, women's writing from various areas of China will be explored. This is chiefly targeted at poetry and the themes within; from the feminine voice of the Classic of Poetry to the remonstrance towards the Khitan Emperor Tianzuo of Jin by his Consort Dasese. The role of women in courtly society is to be elucidated here!
# [[/An Unmarried Life with Heo Nansŏrhŏn/]]
&lt;!---
貧女吟 
豈是乏容色。工鍼復工織。
少小長寒門。良媒不相識。

夜久織未休。戛戛鳴寒機。
機中一匹練。終作阿誰衣。

手把金翦刀。夜寒十指直。
爲人作嫁衣。年年還獨宿。
---&gt;
# [[/Responding to Lord Trần with Hồ Xuân Hương/]]
&lt;!---
Responding to 陳光靜 Trần Quang Tĩnh

《和陳侯》
愧無才調使人驚，十載風塵貫耳鈴。
已是臨枰知敵手，莫須敲月苦殫精。
為輪為彈隨遭遇，誰鳳誰鶯任賦生。
造物於人何苟惜，明珠休向暗中呈。

莫須 is an important structure to teach here.
---&gt;
# [[/Gaze into the Autumn Night with Taisei Shōan/]]
&lt;!---
秋夜偶成·大成聖安
長天浮爽気，月色興無窮
群犬吠山径，百蟲啼野風
悲秋秋夜永，感古古今同
自是孤窓下，凄然万慮空
---&gt;
# [[/Visiting a Temple with Yu Xuanji/]]
&lt;!---
遊崇真觀南樓覩新及第題名處
雲峰滿目放春晴，歷歷銀鈎指下生。
自恨羅衣掩詩句，擧頭空羨榜中名。
---&gt;
# [[/Remonstrance with Dasese/]]
&lt;!---
https://zh.wikisource.org/wiki/%E8%AB%B7%E8%AB%AB%E6%AD%8C
諷諫歌·大瑟瑟
勿嗟塞上兮暗紅塵。
勿傷多難兮畏夷人。
不如塞奸邪之路兮選取賢臣。
直須臥薪嚐膽兮激壯士之捐身。
可以朝清漠北兮夕枕燕雲。

Dasese (or 萧瑟瑟) was a Khitan consort to Emperor Tianzuo of Liao. She remonstrated him as the Jurchens were beginning to encroach upon the Khitan, and was forced to commit suicide for her remonstrance. Tianzuo would soon pay for his malfeasance. 
---&gt;
# [[/The Love Songs of the Odes/]]
&lt;!---
褰裳
子惠思我，褰裳涉溱。子不我思，豈無他人？狂童之狂也且！
子惠思我，褰裳涉洧。子不我思，豈無他士？狂童之狂也且！

柏舟
彼柏舟，在彼中河，髧彼兩髦，實維我儀，之死矢靡它，母也天只，不諒人只。
汎彼柏舟，在彼河側，髧彼兩髦，實維我特，之死矢靡慝，母也天只，不諒人只。

行露
厭浥行露，豈不夙夜，謂行多露。
誰謂雀無角？何以穿我屋？誰謂女無家？何以速我獄？雖速我獄，室家不足。
誰謂鼠無牙？何以穿我墉？誰謂女無家？何以速我訟？雖速我訟，亦不女從。
---&gt;
# [[/Rules for Women with Ban Zhao/]]
&lt;!--- https://zh.wikisource.org/wiki/%E5%A5%B3%E8%AA%A1 ---&gt;
# [[/The Tragedy of Cai Wenji/]]
&lt;!---
悲憤詩
〔兩漢〕蔡文姬
漢季失權柄，董卓亂天常。
志欲圖篡弒，先害諸賢良。
逼迫遷舊邦，擁主以自強。
海內興義師，欲共討不祥。
卓眾來東下，金甲耀日光。
平土人脆弱，來兵皆胡羌。
獵野圍城邑，所向悉破亡。
斬截無孑遺，屍骸相撐拒。
馬邊懸男頭，馬後載婦女。
長驅西入關，迥路險且阻。
還顧邈冥冥，肝脾為爛腐。
所略有萬計，不得令屯聚。
或有骨肉俱，欲言不敢語。
失意幾微間，輒言斃降虜。
要當以亭刃，我曹不活汝。
豈復惜性命，不堪其詈罵。
或便加棰杖，毒痛參並下。
旦則號泣行，夜則悲吟坐。
欲死不能得，欲生無一可。
彼蒼者何辜，乃遭此厄禍。
邊荒與華異，人俗少義理。
處所多霜雪，胡風春夏起。
翩翩吹我衣，肅肅入我耳。
感時念父母，哀嘆無窮已。
有客從外來，聞之常歡喜。
迎問其消息，輒復非鄉里。
邂逅徼時願，骨肉來迎己。
己得自解免，當復棄兒子。
天屬綴人心，念別無會期。
存亡永乖隔，不忍與之辭。
兒前抱我頸，問母欲何之。
人言母當去，豈復有還時。
阿母常仁惻，今何更不慈。
我尚未成人，奈何不顧思。
見此崩五內，恍惚生狂痴。
號泣手撫摩，當發復回疑。
兼有同時輩，相送告離別。
慕我獨得歸，哀叫聲摧裂。
馬為立踟躕，車為不轉轍。
觀者皆噓唏，行路亦嗚咽。
去去割情戀，遄征日遐邁。
悠悠三千里，何時復交會。
念我出腹子，匈臆為摧敗。
既至家人盡，又復無中外。
城廓為山林，庭宇生荊艾。
白骨不知誰，縱橫莫覆蓋。
出門無人聲，豺狼號且吠。
煢煢對孤景，怛吒糜肝肺。
登高遠眺望，魂神忽飛逝。
奄若壽命盡，旁人相寬大。
為復強視息，雖生何聊賴。
託命於新人，竭心自勖勵。
流離成鄙賤，常恐復捐廢。
人生幾何時，懷憂終年歲。
---&gt;

===Unit 5: Myths and Legends of East Asia===
&lt;!--- Shanhaijing, Zibuyu... Etc. Zhiguai literature. This aims to provide a counterpoint to what Confucius wouldn't discuss - thus Zibuyu. Going straight into Daoism isn't ideal. ---&gt;
# [[/Exploring the World of Mountains and Seas/]]&lt;!-- Structure: 出焉 --&gt;
# [[/Oh, the Qilin!/]] &lt;!--- Even here, the odes can be studied! ---&gt;
# [[/Ultimate Justice with Xiezhi/]] 
# [[/The Virtue of the Fenghuang/]] 
# [[/The Entrapment of Hua Po/]] 
# [[/Nüwa Created the World/]] 

===Unit 6: Nation Focus - Japan===
# [[/The Inariyama Sword/]] 
&lt;!--- short and sweet! ---&gt;
# [[/Entering Japan with Takeda Shingen/]]
&lt;!---
便面蘆間有漁·武田信玄
山色水光烟接天，漁翁江上棹蘆辺
丹青若写得勝景，万里風波一釣船

便面半月照梅花·武田信玄
蘆葦清風垂頂絲，窺魚白鷺水生涯
江南記得曾遊夕，似見梨花院落時

島森哲男. (2015). 武田信玄漢詩校釈. 宮城教育大学紀要, 49, 333–352. https://mue.repo.nii.ac.jp/records/440

似 is a really useful thing to teach early on. 
---&gt; 
# [[/The Oldest Inscription in Japan/]] 
&lt;!--- 宇治橋断碑 ---&gt; 
# [[/The End of a Rebellion/]] 
&lt;!--- https://www.fanyahanwen-corpus.cn/corpus_viewer/%E6%97%A5%E6%9C%AC%E6%BC%A2%E6%96%87/clean/%E6%97%A5%E6%9C%AC/%E6%B1%9F%E6%88%B8%E6%99%82%E4%BB%A3/%E8%9D%A6%E5%A4%B7%E5%85%B1%E5%92%8C%E5%9B%BD/%E5%9C%A8%E6%B5%B7%E7%89%99%E5%BA%9C ---&gt;
# [[/Shinto Teachings with Honda Chikaatsu/]] 
&lt;!--- https://wikisource.org/wiki/%E9%81%93%E4%B9%8B%E5%A4%A7%E5%8E%9F 本田親徳 道之大原 ---&gt;  
# [[/The Diary of Fujiwara no Teika/]] 
&lt;!--- 明月記 ---&gt;
# [[/Reading the History of Japan with Prince Toneri/]]
&lt;!--- 日本書記, etc. ---&gt; 
&lt;!--- # [[/Occupying Taiwan/]] ---&gt;
&lt;!--- I have some colonial literature on me that can be used here. ---&gt;

===Unit 7: Nation Focus - Korea===
&lt;!--- 三國史記 for sure! ---&gt;
&lt;!--- 放蟬賦 by Yi Kyubo ---&gt;
&lt;!--- https://zh.wikisource.org/wiki/%E9%A0%A4%E9%BD%8B%E9%81%BA%E7%A8%BF 頤齋遺稿 黃胤錫 Joseon scholar! ---&gt;
# [[/An Elegy to the Empress with Choe Ja/]]
&lt;!---
Choe Ja
元德大后輓詞·崔滋（최자）
乾極曾客配,坤儀正體元。
枕前朝聖主,帳底見曾孫。
陰慘俄沉月,屋悲便沒軒。
三韓千古淚,七十九年恩。
---&gt;
# [[/Language Reform with Sejong the Great/]]
&lt;!--- 訓民正音 https://github.com/ShiraTheMogul/fanyahanwen-corpus/commit/1ef2b42cc50055affaa5ef39c61b87ed31c34a60 multiple poems and descriptive terms, possibly the best capstone ---&gt;

===Unit 8: Christian Literature===
# [[/A Different Three Character Classic with Hong Xiuquan/]]
# [[/Friar Juan Cobo's Veritable Record/]] 
&lt;!--- 
One of few texts from the Philippines that I have ever found!
https://bnedigital.bne.es/bd/en/viewer?id=0160187c-9d9b-4f34-84d6-bc03fd310c69 
---&gt;
# [[/The Delegate's Edition/]]
# [[/Nestorian Steles during the Tang/]] 
&lt;!--- 大秦景教宣元至本經經幢 and 景教碑 ---&gt;
# [[/Hong Xiuquan's Bible/]]
&lt;!--- https://bible.fhl.net/ob/nob.html?book=407 ---&gt;
&lt;!--- I don't want to focus too much on Hong Xiuquan here, so look for more material, especially from missionaries. ---&gt;

===Unit 9: An Introduction to Daoism===
&lt;!--- And now back to your regularly scheduled Zhuangzi/Laozi/Liezi. But with more interesting stuff. Trust! ---&gt;
# [[/Laozi Explains the Dao/]]
&lt;!--- 道可道，非常道。名可名，非常名。無名天地之始；有名萬物之母。故常無欲，以觀其妙；常有欲，以觀其徼。此兩者，同出而異名，同謂之玄。玄之又玄，衆妙之門。I can expect learners to recognise the stuff here. ---&gt;
# [[/Qingtan with Xie Daoyun/]]
&lt;!--- 謝道韞; mentioned in the sanzijing. could be good!

《泰山吟·謝道韞》
峩峩東嶽高，秀極衝青天。
巖中間虛宇，寂寞幽以玄。
非工復非匠，雲構發自然。
器象爾何物，遂令我屢遷。
逝將宅斯宇，可以盡天年。

《拟嵇中散咏松诗·謝道韞》
遙望山上松，隆冬不能凋。
願想遊不憩，瞻彼萬仞條。
騰躍未能升，頓足俟王喬。
時哉不我與，大運所飄遙。

---&gt;
# [[/The Doubting Neighbour/]] 
# [[/Kuafu Chases the Sun/]] 
# [[/The Frog in a Well/]] 
# [[/Wu wei with King Hui of Liang/]]
# [[/The Old Man that Moves the Mountains/]]
# [[/Master Zhuang Dreams of Butterflies/]]
# [[/The Indifferent Taoist/]] &lt;!--- northern song https://zh.wikisource.org/wiki/%E7%8E%89%E6%AD%B7%E5%AF%B6%E9%88%94 ---&gt; 
&lt;!--- Currently very stereotypical, but there's stuff to work with at least. Need to include those weird Daoist characters among other things. ---&gt;

===Unit 10: Nation Focus - Ryukyu Kingdom===
# [[/Historical Annals with Sai On/]] &lt;!--- Kyuko is an easy cop ---&gt;
# [[/The Enthronement of Shō Tei/]] 
&lt;!---
康熙二十二年封王尚貞敕
皇帝敕諭琉球國中山王世子尚貞：惟爾遠處海隅，虔修職貢；屬在塚嗣，序應承祧。以朝命未膺，罔敢專擅；恪遵典制，奉表請封。朕念爾世守臣節，忠誠可嘉！特遣正使翰林院檢討汪楫、副使內閣中書舍人加一級林麟焻，齎敕封爾為琉球國中山王，並賜爾及妃文幣等物。爾祗承寵眷，懋紹先猷；輯和臣民，慎固封守：用安宗社於苞桑，永作天家之屏翰。欽哉，毋替朕命！故諭。

Teach imperial edicts. 
Consider seeing if there's a letter of acceptance from Shō Tei. 

Recorded in 琉球國志略 
https://ctext.org/wiki.pl?if=en&amp;chapter=966326
---&gt;
# [[/The Twilight of Ryukyu with Shō Ten/]] 
&lt;!---
神田酒樓街燈 尚典
酒樓今秋設芳筵，
一望街燈燦燦連。
烟氣引來通柱上，
光爭星月照神田。
---&gt;
# [[/A Trip to Ryukyu with Luo Sen/]] &lt;!--- Pre-Capstone ---&gt;
&lt;!---
遐邇貫珍 1854-11 - 日本日記 羅森 
https://archive.org/details/HEKC185411/page/n5/mode/1up
A solid description of Ryukyu cultural customs in Volume 11. Absolutely incredible. 
日三日火船直向東北而駛出了臺灣之外幾日不見天涯是時北風大作波浪沖天火船亦甚飄蕩而不能立見有沙鷗隨風而逐浪心直駛七日漸見小山而到琉球琉球一國長闊一百七十五里其國城在地球圖緯線赤道之北二十六度十四分經線中華北京偏東十一度二十四分自明以來世封王爵叨列藩籬其處土產不過蔬菜番薯菜油黑糖等類人民束髻大補是穿草履男女粧飾頭上祇插一簪二簪為別故少年之男女瞥目則無異及其壯也皆留鬚髯故街上長鬚之人甚多甲寅正月初一予上岸遊玩見街上兒童甚多分以銅錢各極歡喜人民亦甚謙恭民居間亦貼新春聯于門外但不見有別等繁華之事那霸有寺寺內有園是名家世宦之墳所以石刊刻姓名年號于碑上每日道人打掃供奉生花樹葉于墓前另有人家祖墳與中國之明塚無異峰巒之上樹木多植民房則以蠻石圍墻內以茅草結屋而居佳物椅棹俱無惟以草蓆屈膝而坐對火盆而吹煙民間亦有識中國言語字墨者
不張舖店惟有墟塲男不貿易婦女為之以貨易貨而外方之金銀弗尚焉然而百姓亦甚畏官長飲食亦甚粗粕甘守樸儉不務奢華亦鮮欺詐板門紙窓夜間亦不防竊曾見途中撿物亦能以返原人公門之內冷冷落落並無案牘之煩淳樸之風畧有同于上古之世我等外國之欲買什物須言于官官為代辦正月初六提督被理衛廉士等一班將官布列威嚴與予乘轎至王宮總理大臣尚宏勳為主席布政大夫馬良才為知客享宴甚豐食物多與中國無異宴後各官皆饋有紙扇烟包布帛等項是物雖粗此亦世子之恭敬外國故亞國亦以禮物而返贈之世子王宮離岸三里在于山頂是名守禮將至其宮一路亦有樹木石牌坊宮室亦甚寬大幽雅垣局可觀其處多栽鳳尾草森樹等類以障陰山邊田土樹藝五穀近海沙田水漲之後人收其沙以煎鹽此時明月當圓予覽山川亦足見一方之風景 
---&gt;
&lt;!--- 中山世鑑 and so on. Lots of poetry too. ---&gt;

===Unit 11: Nation Focus - Singapore===
&lt;!--- National Library of Singapore has a poetry series that's super good! ---&gt;

===Unit 12: Literary Chinese in Medicine===
&lt;!--- do not endorse the medical practices discussed in these...make sure to link back to the heavenly stems here as they are associated with specific body parts. ---&gt;
# [[/The Books of the Yellow Emperor/]] 
&lt;!-- 黃帝内徑 ---&gt;
# [[/Deviant Qi with Zhang Congzheng/]]
&lt;!--- https://zh.wikisource.org/wiki/%E5%84%92%E9%96%80%E4%BA%8B%E8%A6%AA ---&gt;
# [[/Anatomy with Sugita Genpaku/]]
&lt;!--- 解体新書 ---&gt;
# [[/A Lost Wu Medical Text analysed in Japan/]]
&lt;!--- 難經古義 ---&gt;

===Unit 13: People Focus - Zhuang peoples===
&lt;!--- https://mooc1.chaoxing.com/mooc-ans/ztnodedetailcontroller/visitnodedetail?courseId=84745403&amp;knowledgeId=84745463&amp;_from_=&amp;_fromV2_=&amp;rtag= 《峤西诗钞》 is also a really good shout. ---&gt;
&lt;!--- Basically, there are Zhuang and Tangut peoples who wrote in Literary Chinese, and their inclusion here is to show that even those who made their own scripts would use this tongue. 张鸿翮 imported the character 朴 to describe a bug, for example. ---&gt;
# [[/Zhuang poetry with Zhang Honghe/]]
&lt;!--- https://wenyi.gmw.cn/2024-06/25/content_37398911.htm

一是忠实记录了汉诗创作与古壮字交融的文化现象。清代壮族诗人张鸿翮（hé）《大塘谣》（《峤西诗钞》卷二）云：

去了休。去到大塘红蓼洲。红蓼生花，不结子。绿朴生花，毬见毬。

诗中所说“绿朴”，是壮族对柚子的惯称。“柚子”，壮语发音为“bug”。根据《古壮字字典》，其对应的古壮字为“朴（㭪）”。诗人将古壮字运用到汉文诗歌创作中，刻下了明清壮汉文化交相辉映的注脚。

This sort of thing is why Zhuang and Tangut inclusion is important, as they show how flexible Literary Chinese can be. ---&gt;

&lt;!---
Possible Jurchen/Khitan focus? 
耶律楚材 - Served 窝阔台, 玄風慶會錄 is short and respectable enough to work with.
---&gt;

===Unit 14: People Focus - Tangut peoples===
&lt;!--- 羅福萇 and 羅振玉 wrote studies on Western Xia / Tangut script. Look for poets and stuff. ---&gt; 

===Unit 15: Literary Chinese in the Military===
&lt;!--- Real Sun Zi hours! 7 Military Classics are an obvious shout, but look for more stuff too. ---&gt;
# [[/Fū! Rin! Ka! Zan!/]]
# [[/A Bilingual Stele of the Khitans/]]
&lt;!--- https://wikisource.org/wiki/%E5%A4%A7%E9%87%91%E7%9A%87%E5%BC%9F%E9%83%BD%E7%B5%B1%E7%B6%93%E7%95%A5%E9%83%8E%E5%90%9B%E8%A1%8C%E8%A8%98 ---&gt;
# [[/Going to war with Boyan/]]
&lt;!---
Boyan's Poem from the 元史
　　伯顏，蒙古巴林部人。至元十一年拜中書左丞相，總兵伐宋。官至開府儀同三司，薨贈太師，封淮安王，諡忠武。

　　《玉堂嘉話》：初，宋未下時，江南謠云：「江南若破，白雁來過。」當時莫喻其意。及宋亡，蓋知指丞相巴延也。

　　過梅嶺岡留題

馬首經從庾嶺回 【 庾嶺回　七修類稿（乾隆刊本）卷四十六作「嶺島歸」。】 ，王師到處悉平夷。擔頭不帶江南物，只插梅花一兩枝。

　　《七修類藳》：伯顏下江南，過金陵梅嶺岡詩云云。所以著名，亦有是善。
---&gt;
# [[/An Edict from the Xianbei/]]
&lt;!---
教義詔 楊廣
武有七德，先之以安民。政有六本，興之以教義。高麗高元，虧失藩禮，將欲問罪遼左，恢宣勝略。雖懷伐國，仍事省方。今往涿郡，巡撫民俗。其河北諸郡及山西、山東年九十已上者，版授太守；八十者，授縣令。
---&gt;
# [[/The Suppression of the Kingdom of Dongning/]]
&lt;!---
台灣鄭氏始末
https://ctext.org/wiki.pl?if=en&amp;chapter=139938

Largely a record of wars in Dongning rather than anything about the trade etc, so it fits here. 
---&gt;
# [[/The Shunzhi Emperor vs Li Zicheng/]]
&lt;!---
順治帝
告示
逆酋李自成已於通城斃命，各地鄉勇務隨我軍剿殺逆賊殘餘,凡有斬獲逆酋及擒獲逆酋交我軍者，一經驗證，按軍功論級給賞，必以示我朝皇恩浩蕩。
大清順治二年五月二十四日

恩詔
今月何日，為國曆改歲之履端,即為永昌書元之紀念？緬惟我朝民眾，三元肇慶，四始發祥。陳椒酒以飛觴，躋堂介壽；換桃符以獻歲，辟戶書新。翹望德容，河勝額手。今山河如舊，歲序更新;今天下同春，咸頒麗澤。願我朝君臣與萬民同樂，共沐化日光天，方不虛度韶華。
永昌二年新正初一

There's probably better choices here. Review. 
---&gt;
# [[/The Art of War/]]

===Unit 16: Nation Focus - Vietnam===
&lt;!--- https://github.com/ShiraTheMogul/fanyahanwen-corpus/commit/cfe6700e01f6fd59616a375d31aa8cd096677be1 this first ---&gt; 
# [[/Ancestor Veneration with the Descendants of Zhu Xi/]] 
&lt;!--- https://github.com/ShiraTheMogul/fanyahanwen-corpus/tree/main/corpus%2F%E8%B6%8A%E5%8D%97%E6%BC%A2%E6%96%87%2Fclean  somewhere in here ---&gt;
# [[/Spreading Revolutionary Consciousness with Phan Bội Châu and Liang Qichao/]] 
&lt;!--- 越南亡國史 Possibly the most important text in Vietnamese history, not even gonna lie. https://zh.wikisource.org/wiki/%E8%B6%8A%E5%8D%97%E4%BA%A1%E5%9C%8B%E5%8F%B2 ---&gt;
# [[/Academia in Literary Chinese between East and West/]] 
&lt;!--- 南風雜誌 is a massive shout here. Absolutely amazing series. ---&gt;

===Unit 17: Historical Annals and Encyclopediae===
&lt;!--- 永樂大典 will teach how to infer from gaps in texts! 《編類》 is an incredibly interesting essay from here that can bring up the odes and Confucius's「思無邪」quote. It can prepare students for the wrath of Qing academia later. ---&gt; 
# [[/The History of Liao, Jin, and Song with Toqto'a/]] &lt;!--- 脱脱 ---&gt;
# [[/Two Years in the Forbidden City with Yu Deling/]] &lt;!--- 清宮禁二年記 https://zh.wikisource.org/wiki/%E6%B8%85%E5%AE%AE%E7%A6%81%E4%BA%8C%E5%B9%B4%E8%A8%98 ---&gt;
# [[/Selected Records of the History of the Da Shun/]]
&lt;!--- Fair Use of a 2010 book written in Literary Chinese about the Da Shun dynasty. Limit to 500 characters, if that. Use to encourage recognition of Simplified variants and modern Wenyanwen. ---&gt;
# [[/Documenting the World with Terajima/]]
&lt;!--- 和漢三才図会 寺島良安, built off 三才圖會 ---&gt;

===Unit 18: Buddhist Literature===
&lt;!--- You would be forgiven for wondering why this is so late, but if you look at many classical Buddhist texts you'll quickly see a ton of loanwords that make it significantly more difficult to read than the average text. Thus, it goes here for now. ---&gt;
&lt;!--- Place focus on practical stuff first. Stuff you can and WILL see in Buddhist temples. Stuff Buddhists can take away immediately. Skills-based approach feels strongest here. ---&gt;
&lt;!--- Look at Northern Liang and Later Qin literature, as there is a ton of work by translators from India during the 16 kingdoms period, particularly those two. ---&gt;
&lt;!--- Stuff by Bodhidharma 達摩 could be fun too https://zh.wikisource.org/wiki/Author:%E9%81%94%E6%91%A9 ---&gt;
# [[/Dipping your feet in with Wenyan Shu/]]
&lt;!---
華亭
世尊遺法本忘言，教外別傳意已圓。
只履攜將蔥嶺去，不妨來上月明船。
---&gt; 
# [[/The Seven Tathagatas/]] 
&lt;!---
南無寶勝如來
南無多寶如來
南無妙色身如來
南無廣博身如來
南無離怖畏如來
南無甘露王如來
南無阿彌陀佛

Use to introduce some core vocabulary in repetitive manner. 

Useful phrases from my trip to Jing'an Temple
南無本師釋迦牟尼佛 - Pay homage to the root teacher
南無大悲觀世音菩薩 - Pay homage to the goddess of mercy 
廣種福田 - widely plant a meritorious field 
---&gt;
# [[/Two Buddhist Temples in Shanghai/]] 
&lt;!---
留雲禪寺
雲留雲翔領畧幾許禪機此地有雲散天開真如界。
塔內塔外普示無邊圓覺是故曰塔影雙照解脫門。

歲次壬午冬月吉旦。
覺醒敬撰。
楊胡生沐手恭書。
善信印利明敬獻。 
---&gt;
&lt;!--- 福慧宝鼎 慧明大和尚 - introduce the Buddhist timekeeping system with 佛歷 around this point. 
赤烏古剎
建寺一千七百六十周年紀念

古剎三國建
滬瀆有重玄
石佛音淨現
聖跡顯重元
唐時稱永泰
宋敕名靜安
聖祖留佛闡
仲師移伽藍
元收八景偈
明鑄鐘聲梵
清樹化羅漢
選賢十方讚
佛日普光明
福慧共修善
鼎運昌隆際
轉正法輪緣

歲次丁亥住持慧明監製
---&gt;
# [[/Foreseeing Monkhood with Yi Xing/]]
&lt;!--- 看命一掌金 ---&gt;
# [[/A Trip to Western Xia with Zhi Guang and Hui Zhen/]]
&lt;!--- https://zh.wikisource.org/wiki/%E5%AF%86%E5%91%AA%E5%9C%93%E5%9B%A0%E5%BE%80%E7%94%9F%E9%9B%86 ---&gt;
&lt;!--- https://zh.wikisource.org/wiki/%E5%AF%86%E5%92%92%E5%9C%93%E5%9B%A0%E5%BE%80%E7%94%9F%E9%9B%86 ---&gt;
# [[/Jizang's Three Discourses/]]
&lt;!--- https://zh.wikisource.org/wiki/%E4%B8%89%E8%AB%96%E7%8E%84%E7%BE%A9 ---&gt;
&lt;!---
I saw these texts being quoted and thus should consider them in some capacity.
《般若波羅蜜多心經》
《金剛般若波羅蜜經》
《一切智光明仙人慈心因緣不食肉經》
《妙法蓮華經》
《大般涅槃經》
《大方等大集經》
《大毘盧舍那成佛神變加持經蓮華胎藏悲生曼荼羅廣大成就儀軌供養方便會》/ 胎藏曼荼羅 
《佛說救拔焰口餓鬼陀羅尼經》
《雜阿含經》

Look at Japan's 五山文学
---&gt;

===Unit 19: People Focus - Manchu peoples===
# [[/Qing dynasty Poetry with Nara Singde/]] 
&lt;!--- 飲水詞 納蘭性德 https://zh.wikisource.org/wiki/Author:%E7%B4%8D%E8%98%AD%E6%80%A7%E5%BE%B7 ---&gt;
# [[/Amassing Words with the Kangxi Emperor/]] 
&lt;!--- Kangxi Dictionary Abstract - https://zh.wikisource.org/wiki/%E5%BA%B7%E7%86%99%E5%AD%97%E5%85%B8 ---&gt;
# [[/Amassing Literature with the Qianlong Emperor/]] 
&lt;!--- Siku Quanshu abstract https://zh.wikisource.org/wiki/%E5%9B%9B%E5%BA%AB%E5%85%A8%E6%9B%B8%E7%B8%BD%E7%9B%AE%E6%8F%90%E8%A6%81 ---&gt;
&lt;!---
Yongzheng Emperor's Poetry 
https://zh.wikisource.org/wiki/Author:%E9%9B%8D%E6%AD%A3%E5%B8%9D
《和碩怡賢親王祭文》

Also include 滿洲國 stuff to show the fall of the Qing and attempts to preserve it through becoming a Japanese puppet state. It is important to show how Literary Chinese can be misused as well. 滿洲國建國宣言 is a good shout, as is 法制 to prepare students who may be interested in Taiwan legal stuff later down the road. 
https://zh.wikisource.org/wiki/Category:%E6%BB%BF%E6%B4%B2%E5%9C%8B
---&gt;
# [[/Paintings and Beauty with Puru Aisin-Gioro/]]
&lt;!--- Saw these in Shanghai Museum with some writing, seemed really cool. Teaches another skill. ---&gt;

===Unit 20: Qing-RoC Literature===
&lt;!--- many writers here, will be difficult to sift through. Include 四库全書 abstracts and stuff here. ---&gt;
# [[/Jewish Refugees in Shanghai/]] 
&lt;!--- Show passports, certificates, etc, from the Jewish Refugee Museum, anonymised. ---&gt;
# [[/A Literary Chinese Abstract/]] 
&lt;!--- Abstracts from siku quanshu, probably want others ---&gt;
# [[/Lament with Lu Ruoteng/]] 
&lt;!---
《疑猜》盧若騰，東寧國
盟誓變為交質子，春秋戰國風如此；末世上下相疑猜, 更質妻子防逃徙。
此法只可羈庸奴，若遇梟雄術窮矣；妻可再娶子再育, 安能長坐針氈裏。
我贈一法君記存；推心置腹人知恩；眾人畜之眾人報, 幾個國士在君門。
盧若騰撰，陳漢光編輯，《島噫詩》，臺灣文獻叢刊第二四五種（臺北:臺灣銀行經濟研究室，1968年）21頁。
---&gt;
# [[/Common Linguistics Knowledge in the RoC/]]
&lt;!--- 音韻常識 ---&gt;

==References used for this page==
* Yang, B. (2016). 文言语法 [Literary Chinese Grammar] (1st ed). 中华书局 [Zhonghua Book Company]. ISBN: 978-7-101-11619-9
* Priestley, K. E., &amp; Shou-jung, C. (1962). China’s Men of Letters, Yesterday and Today. Dragonfly Books.
{{BookCat}}</text>
      <sha1>998ddx6b7954prnyi0tub6xxsi68op9</sha1>
    </revision>
    <revision>
      <id>4656167</id>
      <parentid>4656081</parentid>
      <timestamp>2026-08-03T06:35:54Z</timestamp>
      <contributor>
        <username>Shira the Mogul</username>
        <id>3560559</id>
      </contributor>
      <comment>/* Unit 17: Historical Annals and Encyclopediae */</comment>
      <origin>4656167</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="40344" sha1="f5bj7s9rmzyudflknay5god2uao7dcz" xml:space="preserve">__notoc__

Welcome to the Wikibook for Literary Chinese (Known as 漢文 &quot;Han Language&quot; in East Asia or 文言 &quot;Literary Language&quot; in China), aimed at individuals hoping to gain a general knowledge of it before progressing into genres they wish to be acquainted with. 

This is not the [[Classical Chinese]] textbook, which is aimed at Chinese Zhou-Qin era texts. This  text aims to shed light on post-Zhou-Qin texts across East Asia, which mimic those texts. However, as Zhou-Qin era texts served as the main body from which individuals learned, they are employed here as and when they are considered necessary or otherwise useful. It does so through a &quot;buffet&quot; approach, showering you, the reader, with an ocean of texts of myriad genre. 

==Table of Contents==

=== Front matter ===

* [[/Introduction/]]
* [[/Appendices/]]

=== Useful resources ===
These are quick grab-bags that can be useful for vocabulary-building. 
* [[/Antonym List/]] &lt;!--- 文/武，大/小，厚/薄，橫/縱...---&gt;
* [[/Collocation Groups/]] &lt;!--- e.g. 四象，三靈…… ---&gt;
* [https://zh.wikiversity.org/wiki/Subject:華製新漢語及中文固有語/嚴譯及部定詞等 Yan Fu's Qing-era translations for modern terms] &lt;!--- Wikiversity has this (https://zh.wikiversity.org/wiki/Subject:華製新漢語及中文固有語/嚴譯及部定詞等) and the below, I will effectively be translating a lot of it! ---&gt;
* [https://zh.wikiversity.org/wiki/Subject:華製新漢語及中文固有語/上古語考輯 Communicative Terms]
&lt;!--- this will be translated eventually, but right now it's bad to just leave this here. ---&gt;

=== Useful primers ===
Across history, many primers have been made for teaching Literary Chinese to children. These are a few that are recommended for use alongside this work, ideally in flashcards. 
* [https://www.fdgwz.org.cn/Web/Show/11308 倉頡篇] - Cangjie's Chapters, the earliest one. It is extant, but incomplete. It contains several rare characters, and so if used, I would personally recommend doing so later, or out of interest. 
* 三字經 - The Three Character Classic, an excellent piece for Confucian education. Pair with 弟子规 for best results. 
** 三字經（太平天國版）- For Christians, there is a version made by Hong Xiuquan from the Taiping Rebellion. Despite the context, it is a legitimately useful primer and can be used to self-teach for the Delegate's Edition of the Christian Bible. 
* 千字文 - The Thousand Character Classic, a remarkable piece of constrained writing that only uses each character once. Amazing for building vocabulary whilst seeing historical allusions and the like. 
* 五字鑑 - The Five-Character Mirror, essentially the 24 Histories of China compressed into a primer. Uses 5-character couplets, the longest in this list. 
* 龍文鞭影 - The Shadow of Longwen's Whip, a historical allusion trainer. Best paired with a context piece.

===Unit 0: The Han script===
This unit is intended for those with no familiarity of the Han script. It will prepare you for the units ahead, teaching largely pictographic characters. 

By the end of this unit, students will:
* Recognise around 50 characters.
* Understand how characters are composed and how this gives them meaning.
* Have a basic idea of how to handwrite and/or type characters using the Cangjie Input Method.
* Know some bare basics of Literary Chinese grammar (e.g. Basic word order, where adjectives go, lack of &quot;is&quot;, 有...)

Lessons:
# [[/An Introduction to the Han Script/]]
# [[/People, Big and Small/]]
# [[/How do we write Chinese?/]]
# [[/What are Chinese characters, anyway?/]]
# [[/The Sun, the Moon, and the Five Elements/]]
# [[/Getting Familiar with Body Parts/]]
# [[/Using Numbers and Using Weapons/]] &lt;!--- 竹戈十大中一弓廿卜---&gt;
# [[/Tilling the Fields with 有/]] &lt;!--- 山田 ---&gt;
# [[/How Characters are Made/|How Characters are Made with Kiyohara no Sanemoto]] 
# [[/Cangjie Created Characters/]] &lt;!--- Get people to use Cangjie ---&gt;
# [[/The Kangxi Radical System/]] &lt;!--- Introduce some monoradical texts to train recognition. ---&gt;

===Unit 1: Basic Skills===
This unit is intended for those with minimal familiarity with the Han script and no familiarity with Literary Chinese. There is a focus on simple structures, skills for dissecting common textual structures, and short-form poetry in this unit. 

Before starting this unit, students should:
* Recognise around ~30 characters. 
* Can use Cangjie input. 
* Have given Unit 0 a cursory glance. 
&lt;br&gt;
By the end of this unit, students will:
* Recognise around ~100 characters. 
* Comprehend numbers, the Heavenly Stems, and the Earthly Branches, and be able to use them to quantify time and date.
* Intuit the basic topic -&gt; comment idea behind Literary Chinese. &quot;This, it is...&quot; 
* Understand basic function words such as 也, 而, 有, and 謂.

Lessons:
# [[/The All-Purpose 也/]]
# [[/An Introduction to Chinese Numbers/]] &lt;!--- It is hard to find authentic materials for this ---&gt;
# [[/One, Two, Left, and Right with Gongsun Long/]]
&lt;!---
曰：「二有一乎？」

曰：「二無一。」

曰：「二有右乎？」

曰：「二無右。」

曰：「二有左乎？」

曰：「二無左。」

曰：「右可謂二乎？」

曰：「不可。」

曰：「左可謂二乎？」

曰：「不可。」

曰：「左與右可謂二乎？」

曰：「可。」
---&gt;
# [[/The Heavenly Stems/]] &lt;!--- Introduce ordinals, which will be used to demonstrate sentence patterns later. ---&gt;
# [[/Tell the Time with Earthly Branches/]] &lt;!--- Introduce verbs and timekeeping ---&gt;
# [[/Lunar Dates with the Spring and Autumn Annals/]]
&lt;!--- Vocabulary: 歲，年，朔，月，日，來，前，初，正，春秋夏冬，曆，上，下. Consider including traditional names for months in a list. ---&gt;
# [[/Skimming for Major Events in Historical Annals/]] 
&lt;!--- Don't simply use Confucius's Chunqiu: We can use texts inspired by it. 

E.g. 三國史記 - 十五年京城旱。秋七月，蝗。very few new characters, lots one can use. Instantly able to use. 
https://zh.wikisource.org/wiki/%E4%B8%89%E5%9C%8B%E5%8F%B2%E8%A8%98/%E5%8D%B701

Skimming annals is very possible and a very useful skill. Don't skip out on it. Teach students to skim read!!! 
---&gt;
# [[/Dinner with the Daimyo/]]
&lt;!-- 
侍宴·大友皇子
皇明光日月，帝徳載天地。
三才併秦昌，万国表臣義。
--&gt; 
# [[/In Discourse with Jibong/]]
&lt;!--
芝峰類說 
倭國謂田爲畠。謂水田爲田。火田爲畑。猶我國以水田爲畓也。故官名有畠山殿。地名有畑島云。
--&gt;
# [[/Shinto FAQ with Honda Chikaatsu/]] 
&lt;!--- https://wikisource.org/wiki/%E7%9C%9E%E9%81%93%E5%95%8F%E5%B0%8D 眞道問對 本田親徳 really good way of operationalising 乎 and much of the early grammar. 

問 天帝無始無終乎。
對 天帝無始無終也。
旣以無始無終之力
與無始無終之體
造無始無終之萬物。
其功亦無始無終也。

問 天地大原在道乎。
對 天地大原實在道。
鬼神依道而立。
人民依道而活。
萬物依道而息。

This is great! ---&gt;

&lt;!---
Some cool stuff I saw someone studying from
https://zh.wikisource.org/wiki/%E8%87%B3%E5%B0%8F%E4%B8%98%E8%A5%BF%E5%B0%8F%E7%9F%B3%E6%BD%AD%E8%A8%98#
https://zh.wikisource.org/wiki/%E6%A0%B8%E8%88%9F%E8%A8%98

Could be used for period focus
---&gt;

===Unit 2: An Overview of Sinitic Poetry===
This unit will teach you how Sinitic Poetry operates; - that is, the way individuals in the Sinosphere compose poetry in Literary Chinese. Despite this language's fall out of favour in the past century, this tradition is still remarkably alive and well, and their short length makes them more accessible than elaborate prose. In this unit, you will begin from the ''Classic of Poetry'' before travelling through poems from the Tang dynasty, Singapore, Japan, Vietnam, the Ryukyu Kingdom, and Korea. When introducing poetry, I will furthermore use the language from the nation it is from to show how it is recited by its people. 

After discussing the Classic of Poetry, we will also be a small detour into a discussion on Ping-Ze 平仄, the Tang dynasty system of alternating tones, so to produce rhyme on tonal and phonological levels. This had a major impact on Literary Chinese poetry as a whole!

By the end of this Unit, students will:
* Recognise around 120 more characters.
* Be able to explain how Sinitic Poetry rhymes and the themes it contains.
* Be able to use function words such as 在, 無, 不, 聿, and 于/於 in poetic contexts.
* Recognise the switch between 吾/我 in the subject-object positions and demonstrate it in usage.
* (Chinese speakers) Be able to differentiate 于 and 於, and understand the &quot;interest(ed) in&quot; meaning of 好 in most circumstances.
&lt;!---
Summary of the above part about 于 and 於 for other editors:
于 and 於 were distinct words for an extremely long time and were still such to Literary Chinese writers. Their &quot;merging&quot; through Simplified-Traditional Chinese distinctions is a very modern thing. I will summarise their usages here, using Pulleyblank's Outline of Classical Chinese Grammar (2000);
* 于 - This can mean &quot;to go&quot; or &quot;to/at&quot;. 黃鳥于飛 &quot;The yellow birds go flying&quot;. Must be post-verbal. It can also appear in 至于.
* 於 - This is an all-purpose locative preposition - from &quot;on/at/in&quot; to &quot;from&quot; or even &quot;than&quot; (甲於乙). The implication of motion is not there at all. Must be pre-verbal. It can also appear in 之於 or be an archaic noun for a crow 於 (烏).
---&gt;

Lessons:
# [[/Across the Rivers with Emperor Puliuru Guang/]]
&lt;!---
春江花月夜·楊廣
夜露含花氣，春潭漾月暉。
漢水逢遊女，湘川值二妃。

This is really simple and can elucidate Ping-Ze easily.
---&gt;
# [[/To Study the Odes/]] 
&lt;!-- 蟋蟀·姬旦 國風·唐風
蟋蟀在堂，歲聿其莫。今我不樂，日月其除。無已大康，職思其居。好樂無荒，良士瞿瞿。
蟋蟀在堂，歲聿其逝。今我不樂，日月其邁。無已大康，職思其外。好樂無荒，良士蹶蹶。
蟋蟀在堂，役車其休。今我不樂，日月其慆。無已大康，職思其憂。好樂無荒，良士休休。
--&gt;
&lt;!-- 黃鳥 小雅·鴻鴈之什
黃鳥黃鳥，無集于穀，無啄我粟。
此邦之人，不我肯穀。言旋言歸，復我邦族。

黃鳥黃鳥，無集于桑，無啄我粱。
此邦之人，不可與明。言旋言歸，復我諸兄。

黃鳥黃鳥，無集于栩，無啄我黍。
此邦之人，不可與處。言旋言歸，復我諸父。
--&gt;
# [[/A Detour into Orthodox Ping-Ze/]] 
&lt;!--- 平 and 仄 are useful characters themselves. Show 仄 in the binomes 反仄，歉仄，逼仄 as it's often difficult to immediately use ---&gt;
# [[/The Restraint of Du Fu/]] 
# [[/The Longing of Li Bai/]] 
# [[/The Environment with Bukha Timur/]]
&lt;!---
西湖竹枝詞·布哈特穆爾
湖上春歸人未歸，桃紅柳緑黄鶯飛。
桃花落時多結子，楊花落處秪沾衣。

宫词·布哈特穆爾
玉樓珠箔晚天涼，秋色依稀滿建章。
金井梧桐霜葉盡，自隨流水出宮牆。

Mongol writer from the Uyghur Kingdom of Gaochang
Spammed Ctrl+F in https://zh.wikisource.org/wiki/%E5%BE%A1%E9%81%B8%E5%9B%9B%E6%9C%9D%E8%A9%A9_(%E5%9B%9B%E5%BA%AB%E5%85%A8%E6%9B%B8%E6%9C%AC)
---&gt;
# [[/Pillow Talk with Guan Yunshi/]]
&lt;!---
紅繡鞋·貫雲石
挨著靠著雲窗同坐，偎著抱著月枕雙歌，聽著數著愁著怕著早四更過。四更過情未足，情未足夜如梭。天哪，更閏一更兒妨甚么！

Uyghur author!
---&gt;
# [[/Buddhist Philosophy with Ngô Chân Lưu and Taisei Shōan/]]
&lt;!-- 元火·吳真流
木中元有火，元火復還生。
若為木無火，鉆燧何有萌。--&gt;
&lt;!-- 杜鵑·大成聖安
夢覚孤床静
杜鵑帯雨飛
一声来近枕
何者不沾衣
--&gt;
# [[/Odes with Mō Taiei and Zheng Chengxun/]]
&lt;!-- 詠松·毛泰永
植體宜千仞，垂陰動百尋。
李膺真烈烈，和嶠自森森。
桃李何堪較，雪霜安得侵。
萬年身不老，種子又成林。
AKA Inoha Seiki 伊野波 盛紀 --&gt;
&lt;!-- 詠班蘭·鄭成勛
南國多芳草，班蘭最有名。
深根將綠茁，長葉亦叢生。
取味迎賓合，入厨任水烹。
可憐經一用，擲棄不留情。

鄭成勛《樵隱詩集》 https://nus.edu.sg/nuslibraries/dsprojects/sg-jiutishi/poem/827 --&gt;

# [[/A Golden Cup and the Fall of a Dynasty with Yan Fu/]] 
&lt;!---
鞏金甌·嚴復
鞏金甌，承天幬，民物欣鳧藻，喜同袍。
清時幸遭，真熙皞，帝國蒼穹保。
天高高，海滔滔。
This has music to it, which I think can add a lot. It is also necessary to introduce Yan Fu early given he did translation. ---&gt;
# [[/On a Journey with Sa Dula/]]
&lt;!---
無題·薩都剌
為客三年海上洲，故鄉何處瘴雲稠。
數千里外蠻人域，十八灘頭過客舟。
時有山禽呼姓字，或從海鳥作朋儔。
故人珂珮周旋處，紫殿風清十二樓。
https://zh.wikisource.org/wiki/%E7%84%A1%E9%A1%8C_(%E8%96%A9%E9%83%BD%E5%89%8C)

A naturalised Mongol scholar who made a beautiful poem. This'll be a capstone.
---&gt;
&lt;!---
朝中措·襄陽古道灞陵橋
襄陽古道灞陵橋，詩興與秋高。
千古風流人物，一時多少雄豪。

霜清玉塞，雲飛隴首，風落江皋。
夢到鳳凰台上，山圍故國周遭。

北郊晚步
陂水荷凋晚，茅檐燕去涼。
遠林明落景，平麓淡秋光。
群牧歸村巷，孤禽立野航。
自諳閑散樂，園圃意尤長。

Jurchen poet and grandson of Emperor Shizong of Jin. He's a Zen Buddhist, so we'll go back to him later.
---&gt;

===Unit 3: Confucianism and the World===
This is a Confucian-themed unit with a smattering of other items. You will see the odd geography of the past, early linguistic philosophy, and terrifying breakaway states!

By the end of this unit, students should be able to:
* Recognise around 200+ characters.
* Read basic annals and histories with some dictionary assistance, and comprehend 3-character structures reliably.
* Have encountered basic grammatical points such as 之、乎、者、也、而、則、乃、所、以、於、于、與、且、蓋、and 夫. 
** 於 and 于 should be distinguishable.
* Survive a text of at least 250 characters and read for gist.

Lessons:
# [[/A Brief Overview of Confucianism/]] 
# [[/The Mountains with Yelü Tuyu/]]
&lt;!---
立木海上刻詩 耶律圖欲 / 耶律倍 / 李贊華

小山壓大山，大山全無力。
羞見故鄉人，從此投外國。
---&gt;
# [[/Teaching the Annals in Qi/]] &lt;!-- Gongyang Gao's commentary --&gt;
# [[/Is a White Horse a Horse?/]]&lt;!-- Teach negation with 非 in 公孙龍子 and compare with 不 --&gt;
# [[/The Three Character Classic/]]
# [[/Expressing Filial Conduct with Confucius and Hara Saihin/]]
&lt;!--
次韻杏坪先生
父執有君孤不孤
相依遍接搢紳徒
区区自抱地方寸
杳杳重遊天一隅
羇雁飛鳴迷汝國
家人思夢入江都
如教志業青年遂
世上寧無逐臭夫
--&gt;
# [[/Confucianism and the Environment with Sai On/]]&lt;!-- 木假山記 --&gt;
# [[/In Debate with Mencius/]]

===Unit 4: Women's Writing===
In this unit, women's writing from various areas of China will be explored. This is chiefly targeted at poetry and the themes within; from the feminine voice of the Classic of Poetry to the remonstrance towards the Khitan Emperor Tianzuo of Jin by his Consort Dasese. The role of women in courtly society is to be elucidated here!
# [[/An Unmarried Life with Heo Nansŏrhŏn/]]
&lt;!---
貧女吟 
豈是乏容色。工鍼復工織。
少小長寒門。良媒不相識。

夜久織未休。戛戛鳴寒機。
機中一匹練。終作阿誰衣。

手把金翦刀。夜寒十指直。
爲人作嫁衣。年年還獨宿。
---&gt;
# [[/Responding to Lord Trần with Hồ Xuân Hương/]]
&lt;!---
Responding to 陳光靜 Trần Quang Tĩnh

《和陳侯》
愧無才調使人驚，十載風塵貫耳鈴。
已是臨枰知敵手，莫須敲月苦殫精。
為輪為彈隨遭遇，誰鳳誰鶯任賦生。
造物於人何苟惜，明珠休向暗中呈。

莫須 is an important structure to teach here.
---&gt;
# [[/Gaze into the Autumn Night with Taisei Shōan/]]
&lt;!---
秋夜偶成·大成聖安
長天浮爽気，月色興無窮
群犬吠山径，百蟲啼野風
悲秋秋夜永，感古古今同
自是孤窓下，凄然万慮空
---&gt;
# [[/Visiting a Temple with Yu Xuanji/]]
&lt;!---
遊崇真觀南樓覩新及第題名處
雲峰滿目放春晴，歷歷銀鈎指下生。
自恨羅衣掩詩句，擧頭空羨榜中名。
---&gt;
# [[/Remonstrance with Dasese/]]
&lt;!---
https://zh.wikisource.org/wiki/%E8%AB%B7%E8%AB%AB%E6%AD%8C
諷諫歌·大瑟瑟
勿嗟塞上兮暗紅塵。
勿傷多難兮畏夷人。
不如塞奸邪之路兮選取賢臣。
直須臥薪嚐膽兮激壯士之捐身。
可以朝清漠北兮夕枕燕雲。

Dasese (or 萧瑟瑟) was a Khitan consort to Emperor Tianzuo of Liao. She remonstrated him as the Jurchens were beginning to encroach upon the Khitan, and was forced to commit suicide for her remonstrance. Tianzuo would soon pay for his malfeasance. 
---&gt;
# [[/The Love Songs of the Odes/]]
&lt;!---
褰裳
子惠思我，褰裳涉溱。子不我思，豈無他人？狂童之狂也且！
子惠思我，褰裳涉洧。子不我思，豈無他士？狂童之狂也且！

柏舟
彼柏舟，在彼中河，髧彼兩髦，實維我儀，之死矢靡它，母也天只，不諒人只。
汎彼柏舟，在彼河側，髧彼兩髦，實維我特，之死矢靡慝，母也天只，不諒人只。

行露
厭浥行露，豈不夙夜，謂行多露。
誰謂雀無角？何以穿我屋？誰謂女無家？何以速我獄？雖速我獄，室家不足。
誰謂鼠無牙？何以穿我墉？誰謂女無家？何以速我訟？雖速我訟，亦不女從。
---&gt;
# [[/Rules for Women with Ban Zhao/]]
&lt;!--- https://zh.wikisource.org/wiki/%E5%A5%B3%E8%AA%A1 ---&gt;
# [[/The Tragedy of Cai Wenji/]]
&lt;!---
悲憤詩
〔兩漢〕蔡文姬
漢季失權柄，董卓亂天常。
志欲圖篡弒，先害諸賢良。
逼迫遷舊邦，擁主以自強。
海內興義師，欲共討不祥。
卓眾來東下，金甲耀日光。
平土人脆弱，來兵皆胡羌。
獵野圍城邑，所向悉破亡。
斬截無孑遺，屍骸相撐拒。
馬邊懸男頭，馬後載婦女。
長驅西入關，迥路險且阻。
還顧邈冥冥，肝脾為爛腐。
所略有萬計，不得令屯聚。
或有骨肉俱，欲言不敢語。
失意幾微間，輒言斃降虜。
要當以亭刃，我曹不活汝。
豈復惜性命，不堪其詈罵。
或便加棰杖，毒痛參並下。
旦則號泣行，夜則悲吟坐。
欲死不能得，欲生無一可。
彼蒼者何辜，乃遭此厄禍。
邊荒與華異，人俗少義理。
處所多霜雪，胡風春夏起。
翩翩吹我衣，肅肅入我耳。
感時念父母，哀嘆無窮已。
有客從外來，聞之常歡喜。
迎問其消息，輒復非鄉里。
邂逅徼時願，骨肉來迎己。
己得自解免，當復棄兒子。
天屬綴人心，念別無會期。
存亡永乖隔，不忍與之辭。
兒前抱我頸，問母欲何之。
人言母當去，豈復有還時。
阿母常仁惻，今何更不慈。
我尚未成人，奈何不顧思。
見此崩五內，恍惚生狂痴。
號泣手撫摩，當發復回疑。
兼有同時輩，相送告離別。
慕我獨得歸，哀叫聲摧裂。
馬為立踟躕，車為不轉轍。
觀者皆噓唏，行路亦嗚咽。
去去割情戀，遄征日遐邁。
悠悠三千里，何時復交會。
念我出腹子，匈臆為摧敗。
既至家人盡，又復無中外。
城廓為山林，庭宇生荊艾。
白骨不知誰，縱橫莫覆蓋。
出門無人聲，豺狼號且吠。
煢煢對孤景，怛吒糜肝肺。
登高遠眺望，魂神忽飛逝。
奄若壽命盡，旁人相寬大。
為復強視息，雖生何聊賴。
託命於新人，竭心自勖勵。
流離成鄙賤，常恐復捐廢。
人生幾何時，懷憂終年歲。
---&gt;

===Unit 5: Myths and Legends of East Asia===
&lt;!--- Shanhaijing, Zibuyu... Etc. Zhiguai literature. This aims to provide a counterpoint to what Confucius wouldn't discuss - thus Zibuyu. Going straight into Daoism isn't ideal. ---&gt;
# [[/Exploring the World of Mountains and Seas/]]&lt;!-- Structure: 出焉 --&gt;
# [[/Oh, the Qilin!/]] &lt;!--- Even here, the odes can be studied! ---&gt;
# [[/Ultimate Justice with Xiezhi/]] 
# [[/The Virtue of the Fenghuang/]] 
# [[/The Entrapment of Hua Po/]] 
# [[/Nüwa Created the World/]] 

===Unit 6: Nation Focus - Japan===
# [[/The Inariyama Sword/]] 
&lt;!--- short and sweet! ---&gt;
# [[/Entering Japan with Takeda Shingen/]]
&lt;!---
便面蘆間有漁·武田信玄
山色水光烟接天，漁翁江上棹蘆辺
丹青若写得勝景，万里風波一釣船

便面半月照梅花·武田信玄
蘆葦清風垂頂絲，窺魚白鷺水生涯
江南記得曾遊夕，似見梨花院落時

島森哲男. (2015). 武田信玄漢詩校釈. 宮城教育大学紀要, 49, 333–352. https://mue.repo.nii.ac.jp/records/440

似 is a really useful thing to teach early on. 
---&gt; 
# [[/The Oldest Inscription in Japan/]] 
&lt;!--- 宇治橋断碑 ---&gt; 
# [[/The End of a Rebellion/]] 
&lt;!--- https://www.fanyahanwen-corpus.cn/corpus_viewer/%E6%97%A5%E6%9C%AC%E6%BC%A2%E6%96%87/clean/%E6%97%A5%E6%9C%AC/%E6%B1%9F%E6%88%B8%E6%99%82%E4%BB%A3/%E8%9D%A6%E5%A4%B7%E5%85%B1%E5%92%8C%E5%9B%BD/%E5%9C%A8%E6%B5%B7%E7%89%99%E5%BA%9C ---&gt;
# [[/Shinto Teachings with Honda Chikaatsu/]] 
&lt;!--- https://wikisource.org/wiki/%E9%81%93%E4%B9%8B%E5%A4%A7%E5%8E%9F 本田親徳 道之大原 ---&gt;  
# [[/The Diary of Fujiwara no Teika/]] 
&lt;!--- 明月記 ---&gt;
# [[/Reading the History of Japan with Prince Toneri/]]
&lt;!--- 日本書記, etc. ---&gt; 
&lt;!--- # [[/Occupying Taiwan/]] ---&gt;
&lt;!--- I have some colonial literature on me that can be used here. ---&gt;

===Unit 7: Nation Focus - Korea===
&lt;!--- 三國史記 for sure! ---&gt;
&lt;!--- 放蟬賦 by Yi Kyubo ---&gt;
&lt;!--- https://zh.wikisource.org/wiki/%E9%A0%A4%E9%BD%8B%E9%81%BA%E7%A8%BF 頤齋遺稿 黃胤錫 Joseon scholar! ---&gt;
# [[/An Elegy to the Empress with Choe Ja/]]
&lt;!---
Choe Ja
元德大后輓詞·崔滋（최자）
乾極曾客配,坤儀正體元。
枕前朝聖主,帳底見曾孫。
陰慘俄沉月,屋悲便沒軒。
三韓千古淚,七十九年恩。
---&gt;
# [[/Language Reform with Sejong the Great/]]
&lt;!--- 訓民正音 https://github.com/ShiraTheMogul/fanyahanwen-corpus/commit/1ef2b42cc50055affaa5ef39c61b87ed31c34a60 multiple poems and descriptive terms, possibly the best capstone ---&gt;

===Unit 8: Christian Literature===
# [[/A Different Three Character Classic with Hong Xiuquan/]]
# [[/Friar Juan Cobo's Veritable Record/]] 
&lt;!--- 
One of few texts from the Philippines that I have ever found!
https://bnedigital.bne.es/bd/en/viewer?id=0160187c-9d9b-4f34-84d6-bc03fd310c69 
---&gt;
# [[/The Delegate's Edition/]]
# [[/Nestorian Steles during the Tang/]] 
&lt;!--- 大秦景教宣元至本經經幢 and 景教碑 ---&gt;
# [[/Hong Xiuquan's Bible/]]
&lt;!--- https://bible.fhl.net/ob/nob.html?book=407 ---&gt;
&lt;!--- I don't want to focus too much on Hong Xiuquan here, so look for more material, especially from missionaries. ---&gt;

===Unit 9: An Introduction to Daoism===
&lt;!--- And now back to your regularly scheduled Zhuangzi/Laozi/Liezi. But with more interesting stuff. Trust! ---&gt;
# [[/Laozi Explains the Dao/]]
&lt;!--- 道可道，非常道。名可名，非常名。無名天地之始；有名萬物之母。故常無欲，以觀其妙；常有欲，以觀其徼。此兩者，同出而異名，同謂之玄。玄之又玄，衆妙之門。I can expect learners to recognise the stuff here. ---&gt;
# [[/Qingtan with Xie Daoyun/]]
&lt;!--- 謝道韞; mentioned in the sanzijing. could be good!

《泰山吟·謝道韞》
峩峩東嶽高，秀極衝青天。
巖中間虛宇，寂寞幽以玄。
非工復非匠，雲構發自然。
器象爾何物，遂令我屢遷。
逝將宅斯宇，可以盡天年。

《拟嵇中散咏松诗·謝道韞》
遙望山上松，隆冬不能凋。
願想遊不憩，瞻彼萬仞條。
騰躍未能升，頓足俟王喬。
時哉不我與，大運所飄遙。

---&gt;
# [[/The Doubting Neighbour/]] 
# [[/Kuafu Chases the Sun/]] 
# [[/The Frog in a Well/]] 
# [[/Wu wei with King Hui of Liang/]]
# [[/The Old Man that Moves the Mountains/]]
# [[/Master Zhuang Dreams of Butterflies/]]
# [[/The Indifferent Taoist/]] &lt;!--- northern song https://zh.wikisource.org/wiki/%E7%8E%89%E6%AD%B7%E5%AF%B6%E9%88%94 ---&gt; 
&lt;!--- Currently very stereotypical, but there's stuff to work with at least. Need to include those weird Daoist characters among other things. ---&gt;

===Unit 10: Nation Focus - Ryukyu Kingdom===
# [[/Historical Annals with Sai On/]] &lt;!--- Kyuko is an easy cop ---&gt;
# [[/The Enthronement of Shō Tei/]] 
&lt;!---
康熙二十二年封王尚貞敕
皇帝敕諭琉球國中山王世子尚貞：惟爾遠處海隅，虔修職貢；屬在塚嗣，序應承祧。以朝命未膺，罔敢專擅；恪遵典制，奉表請封。朕念爾世守臣節，忠誠可嘉！特遣正使翰林院檢討汪楫、副使內閣中書舍人加一級林麟焻，齎敕封爾為琉球國中山王，並賜爾及妃文幣等物。爾祗承寵眷，懋紹先猷；輯和臣民，慎固封守：用安宗社於苞桑，永作天家之屏翰。欽哉，毋替朕命！故諭。

Teach imperial edicts. 
Consider seeing if there's a letter of acceptance from Shō Tei. 

Recorded in 琉球國志略 
https://ctext.org/wiki.pl?if=en&amp;chapter=966326
---&gt;
# [[/The Twilight of Ryukyu with Shō Ten/]] 
&lt;!---
神田酒樓街燈 尚典
酒樓今秋設芳筵，
一望街燈燦燦連。
烟氣引來通柱上，
光爭星月照神田。
---&gt;
# [[/A Trip to Ryukyu with Luo Sen/]] &lt;!--- Pre-Capstone ---&gt;
&lt;!---
遐邇貫珍 1854-11 - 日本日記 羅森 
https://archive.org/details/HEKC185411/page/n5/mode/1up
A solid description of Ryukyu cultural customs in Volume 11. Absolutely incredible. 
日三日火船直向東北而駛出了臺灣之外幾日不見天涯是時北風大作波浪沖天火船亦甚飄蕩而不能立見有沙鷗隨風而逐浪心直駛七日漸見小山而到琉球琉球一國長闊一百七十五里其國城在地球圖緯線赤道之北二十六度十四分經線中華北京偏東十一度二十四分自明以來世封王爵叨列藩籬其處土產不過蔬菜番薯菜油黑糖等類人民束髻大補是穿草履男女粧飾頭上祇插一簪二簪為別故少年之男女瞥目則無異及其壯也皆留鬚髯故街上長鬚之人甚多甲寅正月初一予上岸遊玩見街上兒童甚多分以銅錢各極歡喜人民亦甚謙恭民居間亦貼新春聯于門外但不見有別等繁華之事那霸有寺寺內有園是名家世宦之墳所以石刊刻姓名年號于碑上每日道人打掃供奉生花樹葉于墓前另有人家祖墳與中國之明塚無異峰巒之上樹木多植民房則以蠻石圍墻內以茅草結屋而居佳物椅棹俱無惟以草蓆屈膝而坐對火盆而吹煙民間亦有識中國言語字墨者
不張舖店惟有墟塲男不貿易婦女為之以貨易貨而外方之金銀弗尚焉然而百姓亦甚畏官長飲食亦甚粗粕甘守樸儉不務奢華亦鮮欺詐板門紙窓夜間亦不防竊曾見途中撿物亦能以返原人公門之內冷冷落落並無案牘之煩淳樸之風畧有同于上古之世我等外國之欲買什物須言于官官為代辦正月初六提督被理衛廉士等一班將官布列威嚴與予乘轎至王宮總理大臣尚宏勳為主席布政大夫馬良才為知客享宴甚豐食物多與中國無異宴後各官皆饋有紙扇烟包布帛等項是物雖粗此亦世子之恭敬外國故亞國亦以禮物而返贈之世子王宮離岸三里在于山頂是名守禮將至其宮一路亦有樹木石牌坊宮室亦甚寬大幽雅垣局可觀其處多栽鳳尾草森樹等類以障陰山邊田土樹藝五穀近海沙田水漲之後人收其沙以煎鹽此時明月當圓予覽山川亦足見一方之風景 
---&gt;
&lt;!--- 中山世鑑 and so on. Lots of poetry too. ---&gt;

===Unit 11: Nation Focus - Singapore===
&lt;!--- National Library of Singapore has a poetry series that's super good! ---&gt;

===Unit 12: Literary Chinese in Medicine===
&lt;!--- do not endorse the medical practices discussed in these...make sure to link back to the heavenly stems here as they are associated with specific body parts. ---&gt;
# [[/The Books of the Yellow Emperor/]] 
&lt;!-- 黃帝内徑 ---&gt;
# [[/Deviant Qi with Zhang Congzheng/]]
&lt;!--- https://zh.wikisource.org/wiki/%E5%84%92%E9%96%80%E4%BA%8B%E8%A6%AA ---&gt;
# [[/Anatomy with Sugita Genpaku/]]
&lt;!--- 解体新書 ---&gt;
# [[/A Lost Wu Medical Text analysed in Japan/]]
&lt;!--- 難經古義 ---&gt;

===Unit 13: People Focus - Zhuang peoples===
&lt;!--- https://mooc1.chaoxing.com/mooc-ans/ztnodedetailcontroller/visitnodedetail?courseId=84745403&amp;knowledgeId=84745463&amp;_from_=&amp;_fromV2_=&amp;rtag= 《峤西诗钞》 is also a really good shout. ---&gt;
&lt;!--- Basically, there are Zhuang and Tangut peoples who wrote in Literary Chinese, and their inclusion here is to show that even those who made their own scripts would use this tongue. 张鸿翮 imported the character 朴 to describe a bug, for example. ---&gt;
# [[/Zhuang poetry with Zhang Honghe/]]
&lt;!--- https://wenyi.gmw.cn/2024-06/25/content_37398911.htm

一是忠实记录了汉诗创作与古壮字交融的文化现象。清代壮族诗人张鸿翮（hé）《大塘谣》（《峤西诗钞》卷二）云：

去了休。去到大塘红蓼洲。红蓼生花，不结子。绿朴生花，毬见毬。

诗中所说“绿朴”，是壮族对柚子的惯称。“柚子”，壮语发音为“bug”。根据《古壮字字典》，其对应的古壮字为“朴（㭪）”。诗人将古壮字运用到汉文诗歌创作中，刻下了明清壮汉文化交相辉映的注脚。

This sort of thing is why Zhuang and Tangut inclusion is important, as they show how flexible Literary Chinese can be. ---&gt;

&lt;!---
Possible Jurchen/Khitan focus? 
耶律楚材 - Served 窝阔台, 玄風慶會錄 is short and respectable enough to work with.
---&gt;

===Unit 14: People Focus - Tangut peoples===
&lt;!--- 羅福萇 and 羅振玉 wrote studies on Western Xia / Tangut script. Look for poets and stuff. ---&gt; 

===Unit 15: Literary Chinese in the Military===
&lt;!--- Real Sun Zi hours! 7 Military Classics are an obvious shout, but look for more stuff too. ---&gt;
# [[/Fū! Rin! Ka! Zan!/]]
# [[/A Bilingual Stele of the Khitans/]]
&lt;!--- https://wikisource.org/wiki/%E5%A4%A7%E9%87%91%E7%9A%87%E5%BC%9F%E9%83%BD%E7%B5%B1%E7%B6%93%E7%95%A5%E9%83%8E%E5%90%9B%E8%A1%8C%E8%A8%98 ---&gt;
# [[/Going to war with Boyan/]]
&lt;!---
Boyan's Poem from the 元史
　　伯顏，蒙古巴林部人。至元十一年拜中書左丞相，總兵伐宋。官至開府儀同三司，薨贈太師，封淮安王，諡忠武。

　　《玉堂嘉話》：初，宋未下時，江南謠云：「江南若破，白雁來過。」當時莫喻其意。及宋亡，蓋知指丞相巴延也。

　　過梅嶺岡留題

馬首經從庾嶺回 【 庾嶺回　七修類稿（乾隆刊本）卷四十六作「嶺島歸」。】 ，王師到處悉平夷。擔頭不帶江南物，只插梅花一兩枝。

　　《七修類藳》：伯顏下江南，過金陵梅嶺岡詩云云。所以著名，亦有是善。
---&gt;
# [[/An Edict from the Xianbei/]]
&lt;!---
教義詔 楊廣
武有七德，先之以安民。政有六本，興之以教義。高麗高元，虧失藩禮，將欲問罪遼左，恢宣勝略。雖懷伐國，仍事省方。今往涿郡，巡撫民俗。其河北諸郡及山西、山東年九十已上者，版授太守；八十者，授縣令。
---&gt;
# [[/The Suppression of the Kingdom of Dongning/]]
&lt;!---
台灣鄭氏始末
https://ctext.org/wiki.pl?if=en&amp;chapter=139938

Largely a record of wars in Dongning rather than anything about the trade etc, so it fits here. 
---&gt;
# [[/The Shunzhi Emperor vs Li Zicheng/]]
&lt;!---
順治帝
告示
逆酋李自成已於通城斃命，各地鄉勇務隨我軍剿殺逆賊殘餘,凡有斬獲逆酋及擒獲逆酋交我軍者，一經驗證，按軍功論級給賞，必以示我朝皇恩浩蕩。
大清順治二年五月二十四日

恩詔
今月何日，為國曆改歲之履端,即為永昌書元之紀念？緬惟我朝民眾，三元肇慶，四始發祥。陳椒酒以飛觴，躋堂介壽；換桃符以獻歲，辟戶書新。翹望德容，河勝額手。今山河如舊，歲序更新;今天下同春，咸頒麗澤。願我朝君臣與萬民同樂，共沐化日光天，方不虛度韶華。
永昌二年新正初一

There's probably better choices here. Review. 
---&gt;
# [[/The Art of War/]]

===Unit 16: Nation Focus - Vietnam===
&lt;!--- https://github.com/ShiraTheMogul/fanyahanwen-corpus/commit/cfe6700e01f6fd59616a375d31aa8cd096677be1 this first ---&gt; 
# [[/Ancestor Veneration with the Descendants of Zhu Xi/]] 
&lt;!--- https://github.com/ShiraTheMogul/fanyahanwen-corpus/tree/main/corpus%2F%E8%B6%8A%E5%8D%97%E6%BC%A2%E6%96%87%2Fclean  somewhere in here ---&gt;
# [[/Spreading Revolutionary Consciousness with Phan Bội Châu and Liang Qichao/]] 
&lt;!--- 越南亡國史 Possibly the most important text in Vietnamese history, not even gonna lie. https://zh.wikisource.org/wiki/%E8%B6%8A%E5%8D%97%E4%BA%A1%E5%9C%8B%E5%8F%B2 ---&gt;
# [[/Academia in Literary Chinese between East and West/]] 
&lt;!--- 南風雜誌 is a massive shout here. Absolutely amazing series. ---&gt;

===Unit 17: Historical Annals and Encyclopediae===
&lt;!--- 永樂大典 will teach how to infer from gaps in texts! 《編類》 is an incredibly interesting essay from here that can bring up the odes and Confucius's「思無邪」quote. It can prepare students for the wrath of Qing academia later. ---&gt; 
# [[/An Introduction to Biographical Paintings/]]
&lt;!-- 
Many older paintings include biographies at the top in Literary Chinese. Students need to learn these.
https://commons.wikimedia.org/wiki/File:%E6%AD%B7%E4%BB%A3%E8%81%96%E8%B3%A2%E5%8D%8A%E8%BA%AB%E5%83%8F_%E5%86%8A_%E8%AB%B8%E8%91%9B%E4%BA%AE_(Zhuge_Liang).png - Famous figure, also part of a very notable series.
https://commons.wikimedia.org/wiki/File:Otomo-Sorin-2.jpg - Contains the Japanese repetition character 々
--&gt;
# [[/The History of Liao, Jin, and Song with Toqto'a/]] &lt;!--- 脱脱 ---&gt;
# [[/Two Years in the Forbidden City with Yu Deling/]] &lt;!--- 清宮禁二年記 https://zh.wikisource.org/wiki/%E6%B8%85%E5%AE%AE%E7%A6%81%E4%BA%8C%E5%B9%B4%E8%A8%98 ---&gt;
# [[/Selected Records of the History of the Da Shun/]]
&lt;!--- Fair Use of a 2010 book written in Literary Chinese about the Da Shun dynasty. Limit to 500 characters, if that. Use to encourage recognition of Simplified variants and modern Wenyanwen. ---&gt;
# [[/Documenting the World with Terajima/]]
&lt;!--- 和漢三才図会 寺島良安, built off 三才圖會 ---&gt;

===Unit 18: Buddhist Literature===
&lt;!--- You would be forgiven for wondering why this is so late, but if you look at many classical Buddhist texts you'll quickly see a ton of loanwords that make it significantly more difficult to read than the average text. Thus, it goes here for now. ---&gt;
&lt;!--- Place focus on practical stuff first. Stuff you can and WILL see in Buddhist temples. Stuff Buddhists can take away immediately. Skills-based approach feels strongest here. ---&gt;
&lt;!--- Look at Northern Liang and Later Qin literature, as there is a ton of work by translators from India during the 16 kingdoms period, particularly those two. ---&gt;
&lt;!--- Stuff by Bodhidharma 達摩 could be fun too https://zh.wikisource.org/wiki/Author:%E9%81%94%E6%91%A9 ---&gt;
# [[/Dipping your feet in with Wenyan Shu/]]
&lt;!---
華亭
世尊遺法本忘言，教外別傳意已圓。
只履攜將蔥嶺去，不妨來上月明船。
---&gt; 
# [[/The Seven Tathagatas/]] 
&lt;!---
南無寶勝如來
南無多寶如來
南無妙色身如來
南無廣博身如來
南無離怖畏如來
南無甘露王如來
南無阿彌陀佛

Use to introduce some core vocabulary in repetitive manner. 

Useful phrases from my trip to Jing'an Temple
南無本師釋迦牟尼佛 - Pay homage to the root teacher
南無大悲觀世音菩薩 - Pay homage to the goddess of mercy 
廣種福田 - widely plant a meritorious field 
---&gt;
# [[/Two Buddhist Temples in Shanghai/]] 
&lt;!---
留雲禪寺
雲留雲翔領畧幾許禪機此地有雲散天開真如界。
塔內塔外普示無邊圓覺是故曰塔影雙照解脫門。

歲次壬午冬月吉旦。
覺醒敬撰。
楊胡生沐手恭書。
善信印利明敬獻。 
---&gt;
&lt;!--- 福慧宝鼎 慧明大和尚 - introduce the Buddhist timekeeping system with 佛歷 around this point. 
赤烏古剎
建寺一千七百六十周年紀念

古剎三國建
滬瀆有重玄
石佛音淨現
聖跡顯重元
唐時稱永泰
宋敕名靜安
聖祖留佛闡
仲師移伽藍
元收八景偈
明鑄鐘聲梵
清樹化羅漢
選賢十方讚
佛日普光明
福慧共修善
鼎運昌隆際
轉正法輪緣

歲次丁亥住持慧明監製
---&gt;
# [[/Foreseeing Monkhood with Yi Xing/]]
&lt;!--- 看命一掌金 ---&gt;
# [[/A Trip to Western Xia with Zhi Guang and Hui Zhen/]]
&lt;!--- https://zh.wikisource.org/wiki/%E5%AF%86%E5%91%AA%E5%9C%93%E5%9B%A0%E5%BE%80%E7%94%9F%E9%9B%86 ---&gt;
&lt;!--- https://zh.wikisource.org/wiki/%E5%AF%86%E5%92%92%E5%9C%93%E5%9B%A0%E5%BE%80%E7%94%9F%E9%9B%86 ---&gt;
# [[/Jizang's Three Discourses/]]
&lt;!--- https://zh.wikisource.org/wiki/%E4%B8%89%E8%AB%96%E7%8E%84%E7%BE%A9 ---&gt;
&lt;!---
I saw these texts being quoted and thus should consider them in some capacity.
《般若波羅蜜多心經》
《金剛般若波羅蜜經》
《一切智光明仙人慈心因緣不食肉經》
《妙法蓮華經》
《大般涅槃經》
《大方等大集經》
《大毘盧舍那成佛神變加持經蓮華胎藏悲生曼荼羅廣大成就儀軌供養方便會》/ 胎藏曼荼羅 
《佛說救拔焰口餓鬼陀羅尼經》
《雜阿含經》

Look at Japan's 五山文学
---&gt;

===Unit 19: People Focus - Manchu peoples===
# [[/Qing dynasty Poetry with Nara Singde/]] 
&lt;!--- 飲水詞 納蘭性德 https://zh.wikisource.org/wiki/Author:%E7%B4%8D%E8%98%AD%E6%80%A7%E5%BE%B7 ---&gt;
# [[/Amassing Words with the Kangxi Emperor/]] 
&lt;!--- Kangxi Dictionary Abstract - https://zh.wikisource.org/wiki/%E5%BA%B7%E7%86%99%E5%AD%97%E5%85%B8 ---&gt;
# [[/Amassing Literature with the Qianlong Emperor/]] 
&lt;!--- Siku Quanshu abstract https://zh.wikisource.org/wiki/%E5%9B%9B%E5%BA%AB%E5%85%A8%E6%9B%B8%E7%B8%BD%E7%9B%AE%E6%8F%90%E8%A6%81 ---&gt;
&lt;!---
Yongzheng Emperor's Poetry 
https://zh.wikisource.org/wiki/Author:%E9%9B%8D%E6%AD%A3%E5%B8%9D
《和碩怡賢親王祭文》

Also include 滿洲國 stuff to show the fall of the Qing and attempts to preserve it through becoming a Japanese puppet state. It is important to show how Literary Chinese can be misused as well. 滿洲國建國宣言 is a good shout, as is 法制 to prepare students who may be interested in Taiwan legal stuff later down the road. 
https://zh.wikisource.org/wiki/Category:%E6%BB%BF%E6%B4%B2%E5%9C%8B
---&gt;
# [[/Paintings and Beauty with Puru Aisin-Gioro/]]
&lt;!--- Saw these in Shanghai Museum with some writing, seemed really cool. Teaches another skill. ---&gt;

===Unit 20: Qing-RoC Literature===
&lt;!--- many writers here, will be difficult to sift through. Include 四库全書 abstracts and stuff here. ---&gt;
# [[/Jewish Refugees in Shanghai/]] 
&lt;!--- Show passports, certificates, etc, from the Jewish Refugee Museum, anonymised. ---&gt;
# [[/A Literary Chinese Abstract/]] 
&lt;!--- Abstracts from siku quanshu, probably want others ---&gt;
# [[/Lament with Lu Ruoteng/]] 
&lt;!---
《疑猜》盧若騰，東寧國
盟誓變為交質子，春秋戰國風如此；末世上下相疑猜, 更質妻子防逃徙。
此法只可羈庸奴，若遇梟雄術窮矣；妻可再娶子再育, 安能長坐針氈裏。
我贈一法君記存；推心置腹人知恩；眾人畜之眾人報, 幾個國士在君門。
盧若騰撰，陳漢光編輯，《島噫詩》，臺灣文獻叢刊第二四五種（臺北:臺灣銀行經濟研究室，1968年）21頁。
---&gt;
# [[/Common Linguistics Knowledge in the RoC/]]
&lt;!--- 音韻常識 ---&gt;

==References used for this page==
* Yang, B. (2016). 文言语法 [Literary Chinese Grammar] (1st ed). 中华书局 [Zhonghua Book Company]. ISBN: 978-7-101-11619-9
* Priestley, K. E., &amp; Shou-jung, C. (1962). China’s Men of Letters, Yesterday and Today. Dragonfly Books.
{{BookCat}}</text>
      <sha1>f5bj7s9rmzyudflknay5god2uao7dcz</sha1>
    </revision>
    <revision>
      <id>4656170</id>
      <parentid>4656167</parentid>
      <timestamp>2026-08-03T07:23:03Z</timestamp>
      <contributor>
        <username>Shira the Mogul</username>
        <id>3560559</id>
      </contributor>
      <minor />
      <comment>/* Unit 17: Historical Annals and Encyclopediae */</comment>
      <origin>4656170</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="40426" sha1="0dh17frwo6v3zom47v44fhno47p0vaq" xml:space="preserve">__notoc__

Welcome to the Wikibook for Literary Chinese (Known as 漢文 &quot;Han Language&quot; in East Asia or 文言 &quot;Literary Language&quot; in China), aimed at individuals hoping to gain a general knowledge of it before progressing into genres they wish to be acquainted with. 

This is not the [[Classical Chinese]] textbook, which is aimed at Chinese Zhou-Qin era texts. This  text aims to shed light on post-Zhou-Qin texts across East Asia, which mimic those texts. However, as Zhou-Qin era texts served as the main body from which individuals learned, they are employed here as and when they are considered necessary or otherwise useful. It does so through a &quot;buffet&quot; approach, showering you, the reader, with an ocean of texts of myriad genre. 

==Table of Contents==

=== Front matter ===

* [[/Introduction/]]
* [[/Appendices/]]

=== Useful resources ===
These are quick grab-bags that can be useful for vocabulary-building. 
* [[/Antonym List/]] &lt;!--- 文/武，大/小，厚/薄，橫/縱...---&gt;
* [[/Collocation Groups/]] &lt;!--- e.g. 四象，三靈…… ---&gt;
* [https://zh.wikiversity.org/wiki/Subject:華製新漢語及中文固有語/嚴譯及部定詞等 Yan Fu's Qing-era translations for modern terms] &lt;!--- Wikiversity has this (https://zh.wikiversity.org/wiki/Subject:華製新漢語及中文固有語/嚴譯及部定詞等) and the below, I will effectively be translating a lot of it! ---&gt;
* [https://zh.wikiversity.org/wiki/Subject:華製新漢語及中文固有語/上古語考輯 Communicative Terms]
&lt;!--- this will be translated eventually, but right now it's bad to just leave this here. ---&gt;

=== Useful primers ===
Across history, many primers have been made for teaching Literary Chinese to children. These are a few that are recommended for use alongside this work, ideally in flashcards. 
* [https://www.fdgwz.org.cn/Web/Show/11308 倉頡篇] - Cangjie's Chapters, the earliest one. It is extant, but incomplete. It contains several rare characters, and so if used, I would personally recommend doing so later, or out of interest. 
* 三字經 - The Three Character Classic, an excellent piece for Confucian education. Pair with 弟子规 for best results. 
** 三字經（太平天國版）- For Christians, there is a version made by Hong Xiuquan from the Taiping Rebellion. Despite the context, it is a legitimately useful primer and can be used to self-teach for the Delegate's Edition of the Christian Bible. 
* 千字文 - The Thousand Character Classic, a remarkable piece of constrained writing that only uses each character once. Amazing for building vocabulary whilst seeing historical allusions and the like. 
* 五字鑑 - The Five-Character Mirror, essentially the 24 Histories of China compressed into a primer. Uses 5-character couplets, the longest in this list. 
* 龍文鞭影 - The Shadow of Longwen's Whip, a historical allusion trainer. Best paired with a context piece.

===Unit 0: The Han script===
This unit is intended for those with no familiarity of the Han script. It will prepare you for the units ahead, teaching largely pictographic characters. 

By the end of this unit, students will:
* Recognise around 50 characters.
* Understand how characters are composed and how this gives them meaning.
* Have a basic idea of how to handwrite and/or type characters using the Cangjie Input Method.
* Know some bare basics of Literary Chinese grammar (e.g. Basic word order, where adjectives go, lack of &quot;is&quot;, 有...)

Lessons:
# [[/An Introduction to the Han Script/]]
# [[/People, Big and Small/]]
# [[/How do we write Chinese?/]]
# [[/What are Chinese characters, anyway?/]]
# [[/The Sun, the Moon, and the Five Elements/]]
# [[/Getting Familiar with Body Parts/]]
# [[/Using Numbers and Using Weapons/]] &lt;!--- 竹戈十大中一弓廿卜---&gt;
# [[/Tilling the Fields with 有/]] &lt;!--- 山田 ---&gt;
# [[/How Characters are Made/|How Characters are Made with Kiyohara no Sanemoto]] 
# [[/Cangjie Created Characters/]] &lt;!--- Get people to use Cangjie ---&gt;
# [[/The Kangxi Radical System/]] &lt;!--- Introduce some monoradical texts to train recognition. ---&gt;

===Unit 1: Basic Skills===
This unit is intended for those with minimal familiarity with the Han script and no familiarity with Literary Chinese. There is a focus on simple structures, skills for dissecting common textual structures, and short-form poetry in this unit. 

Before starting this unit, students should:
* Recognise around ~30 characters. 
* Can use Cangjie input. 
* Have given Unit 0 a cursory glance. 
&lt;br&gt;
By the end of this unit, students will:
* Recognise around ~100 characters. 
* Comprehend numbers, the Heavenly Stems, and the Earthly Branches, and be able to use them to quantify time and date.
* Intuit the basic topic -&gt; comment idea behind Literary Chinese. &quot;This, it is...&quot; 
* Understand basic function words such as 也, 而, 有, and 謂.

Lessons:
# [[/The All-Purpose 也/]]
# [[/An Introduction to Chinese Numbers/]] &lt;!--- It is hard to find authentic materials for this ---&gt;
# [[/One, Two, Left, and Right with Gongsun Long/]]
&lt;!---
曰：「二有一乎？」

曰：「二無一。」

曰：「二有右乎？」

曰：「二無右。」

曰：「二有左乎？」

曰：「二無左。」

曰：「右可謂二乎？」

曰：「不可。」

曰：「左可謂二乎？」

曰：「不可。」

曰：「左與右可謂二乎？」

曰：「可。」
---&gt;
# [[/The Heavenly Stems/]] &lt;!--- Introduce ordinals, which will be used to demonstrate sentence patterns later. ---&gt;
# [[/Tell the Time with Earthly Branches/]] &lt;!--- Introduce verbs and timekeeping ---&gt;
# [[/Lunar Dates with the Spring and Autumn Annals/]]
&lt;!--- Vocabulary: 歲，年，朔，月，日，來，前，初，正，春秋夏冬，曆，上，下. Consider including traditional names for months in a list. ---&gt;
# [[/Skimming for Major Events in Historical Annals/]] 
&lt;!--- Don't simply use Confucius's Chunqiu: We can use texts inspired by it. 

E.g. 三國史記 - 十五年京城旱。秋七月，蝗。very few new characters, lots one can use. Instantly able to use. 
https://zh.wikisource.org/wiki/%E4%B8%89%E5%9C%8B%E5%8F%B2%E8%A8%98/%E5%8D%B701

Skimming annals is very possible and a very useful skill. Don't skip out on it. Teach students to skim read!!! 
---&gt;
# [[/Dinner with the Daimyo/]]
&lt;!-- 
侍宴·大友皇子
皇明光日月，帝徳載天地。
三才併秦昌，万国表臣義。
--&gt; 
# [[/In Discourse with Jibong/]]
&lt;!--
芝峰類說 
倭國謂田爲畠。謂水田爲田。火田爲畑。猶我國以水田爲畓也。故官名有畠山殿。地名有畑島云。
--&gt;
# [[/Shinto FAQ with Honda Chikaatsu/]] 
&lt;!--- https://wikisource.org/wiki/%E7%9C%9E%E9%81%93%E5%95%8F%E5%B0%8D 眞道問對 本田親徳 really good way of operationalising 乎 and much of the early grammar. 

問 天帝無始無終乎。
對 天帝無始無終也。
旣以無始無終之力
與無始無終之體
造無始無終之萬物。
其功亦無始無終也。

問 天地大原在道乎。
對 天地大原實在道。
鬼神依道而立。
人民依道而活。
萬物依道而息。

This is great! ---&gt;

&lt;!---
Some cool stuff I saw someone studying from
https://zh.wikisource.org/wiki/%E8%87%B3%E5%B0%8F%E4%B8%98%E8%A5%BF%E5%B0%8F%E7%9F%B3%E6%BD%AD%E8%A8%98#
https://zh.wikisource.org/wiki/%E6%A0%B8%E8%88%9F%E8%A8%98

Could be used for period focus
---&gt;

===Unit 2: An Overview of Sinitic Poetry===
This unit will teach you how Sinitic Poetry operates; - that is, the way individuals in the Sinosphere compose poetry in Literary Chinese. Despite this language's fall out of favour in the past century, this tradition is still remarkably alive and well, and their short length makes them more accessible than elaborate prose. In this unit, you will begin from the ''Classic of Poetry'' before travelling through poems from the Tang dynasty, Singapore, Japan, Vietnam, the Ryukyu Kingdom, and Korea. When introducing poetry, I will furthermore use the language from the nation it is from to show how it is recited by its people. 

After discussing the Classic of Poetry, we will also be a small detour into a discussion on Ping-Ze 平仄, the Tang dynasty system of alternating tones, so to produce rhyme on tonal and phonological levels. This had a major impact on Literary Chinese poetry as a whole!

By the end of this Unit, students will:
* Recognise around 120 more characters.
* Be able to explain how Sinitic Poetry rhymes and the themes it contains.
* Be able to use function words such as 在, 無, 不, 聿, and 于/於 in poetic contexts.
* Recognise the switch between 吾/我 in the subject-object positions and demonstrate it in usage.
* (Chinese speakers) Be able to differentiate 于 and 於, and understand the &quot;interest(ed) in&quot; meaning of 好 in most circumstances.
&lt;!---
Summary of the above part about 于 and 於 for other editors:
于 and 於 were distinct words for an extremely long time and were still such to Literary Chinese writers. Their &quot;merging&quot; through Simplified-Traditional Chinese distinctions is a very modern thing. I will summarise their usages here, using Pulleyblank's Outline of Classical Chinese Grammar (2000);
* 于 - This can mean &quot;to go&quot; or &quot;to/at&quot;. 黃鳥于飛 &quot;The yellow birds go flying&quot;. Must be post-verbal. It can also appear in 至于.
* 於 - This is an all-purpose locative preposition - from &quot;on/at/in&quot; to &quot;from&quot; or even &quot;than&quot; (甲於乙). The implication of motion is not there at all. Must be pre-verbal. It can also appear in 之於 or be an archaic noun for a crow 於 (烏).
---&gt;

Lessons:
# [[/Across the Rivers with Emperor Puliuru Guang/]]
&lt;!---
春江花月夜·楊廣
夜露含花氣，春潭漾月暉。
漢水逢遊女，湘川值二妃。

This is really simple and can elucidate Ping-Ze easily.
---&gt;
# [[/To Study the Odes/]] 
&lt;!-- 蟋蟀·姬旦 國風·唐風
蟋蟀在堂，歲聿其莫。今我不樂，日月其除。無已大康，職思其居。好樂無荒，良士瞿瞿。
蟋蟀在堂，歲聿其逝。今我不樂，日月其邁。無已大康，職思其外。好樂無荒，良士蹶蹶。
蟋蟀在堂，役車其休。今我不樂，日月其慆。無已大康，職思其憂。好樂無荒，良士休休。
--&gt;
&lt;!-- 黃鳥 小雅·鴻鴈之什
黃鳥黃鳥，無集于穀，無啄我粟。
此邦之人，不我肯穀。言旋言歸，復我邦族。

黃鳥黃鳥，無集于桑，無啄我粱。
此邦之人，不可與明。言旋言歸，復我諸兄。

黃鳥黃鳥，無集于栩，無啄我黍。
此邦之人，不可與處。言旋言歸，復我諸父。
--&gt;
# [[/A Detour into Orthodox Ping-Ze/]] 
&lt;!--- 平 and 仄 are useful characters themselves. Show 仄 in the binomes 反仄，歉仄，逼仄 as it's often difficult to immediately use ---&gt;
# [[/The Restraint of Du Fu/]] 
# [[/The Longing of Li Bai/]] 
# [[/The Environment with Bukha Timur/]]
&lt;!---
西湖竹枝詞·布哈特穆爾
湖上春歸人未歸，桃紅柳緑黄鶯飛。
桃花落時多結子，楊花落處秪沾衣。

宫词·布哈特穆爾
玉樓珠箔晚天涼，秋色依稀滿建章。
金井梧桐霜葉盡，自隨流水出宮牆。

Mongol writer from the Uyghur Kingdom of Gaochang
Spammed Ctrl+F in https://zh.wikisource.org/wiki/%E5%BE%A1%E9%81%B8%E5%9B%9B%E6%9C%9D%E8%A9%A9_(%E5%9B%9B%E5%BA%AB%E5%85%A8%E6%9B%B8%E6%9C%AC)
---&gt;
# [[/Pillow Talk with Guan Yunshi/]]
&lt;!---
紅繡鞋·貫雲石
挨著靠著雲窗同坐，偎著抱著月枕雙歌，聽著數著愁著怕著早四更過。四更過情未足，情未足夜如梭。天哪，更閏一更兒妨甚么！

Uyghur author!
---&gt;
# [[/Buddhist Philosophy with Ngô Chân Lưu and Taisei Shōan/]]
&lt;!-- 元火·吳真流
木中元有火，元火復還生。
若為木無火，鉆燧何有萌。--&gt;
&lt;!-- 杜鵑·大成聖安
夢覚孤床静
杜鵑帯雨飛
一声来近枕
何者不沾衣
--&gt;
# [[/Odes with Mō Taiei and Zheng Chengxun/]]
&lt;!-- 詠松·毛泰永
植體宜千仞，垂陰動百尋。
李膺真烈烈，和嶠自森森。
桃李何堪較，雪霜安得侵。
萬年身不老，種子又成林。
AKA Inoha Seiki 伊野波 盛紀 --&gt;
&lt;!-- 詠班蘭·鄭成勛
南國多芳草，班蘭最有名。
深根將綠茁，長葉亦叢生。
取味迎賓合，入厨任水烹。
可憐經一用，擲棄不留情。

鄭成勛《樵隱詩集》 https://nus.edu.sg/nuslibraries/dsprojects/sg-jiutishi/poem/827 --&gt;

# [[/A Golden Cup and the Fall of a Dynasty with Yan Fu/]] 
&lt;!---
鞏金甌·嚴復
鞏金甌，承天幬，民物欣鳧藻，喜同袍。
清時幸遭，真熙皞，帝國蒼穹保。
天高高，海滔滔。
This has music to it, which I think can add a lot. It is also necessary to introduce Yan Fu early given he did translation. ---&gt;
# [[/On a Journey with Sa Dula/]]
&lt;!---
無題·薩都剌
為客三年海上洲，故鄉何處瘴雲稠。
數千里外蠻人域，十八灘頭過客舟。
時有山禽呼姓字，或從海鳥作朋儔。
故人珂珮周旋處，紫殿風清十二樓。
https://zh.wikisource.org/wiki/%E7%84%A1%E9%A1%8C_(%E8%96%A9%E9%83%BD%E5%89%8C)

A naturalised Mongol scholar who made a beautiful poem. This'll be a capstone.
---&gt;
&lt;!---
朝中措·襄陽古道灞陵橋
襄陽古道灞陵橋，詩興與秋高。
千古風流人物，一時多少雄豪。

霜清玉塞，雲飛隴首，風落江皋。
夢到鳳凰台上，山圍故國周遭。

北郊晚步
陂水荷凋晚，茅檐燕去涼。
遠林明落景，平麓淡秋光。
群牧歸村巷，孤禽立野航。
自諳閑散樂，園圃意尤長。

Jurchen poet and grandson of Emperor Shizong of Jin. He's a Zen Buddhist, so we'll go back to him later.
---&gt;

===Unit 3: Confucianism and the World===
This is a Confucian-themed unit with a smattering of other items. You will see the odd geography of the past, early linguistic philosophy, and terrifying breakaway states!

By the end of this unit, students should be able to:
* Recognise around 200+ characters.
* Read basic annals and histories with some dictionary assistance, and comprehend 3-character structures reliably.
* Have encountered basic grammatical points such as 之、乎、者、也、而、則、乃、所、以、於、于、與、且、蓋、and 夫. 
** 於 and 于 should be distinguishable.
* Survive a text of at least 250 characters and read for gist.

Lessons:
# [[/A Brief Overview of Confucianism/]] 
# [[/The Mountains with Yelü Tuyu/]]
&lt;!---
立木海上刻詩 耶律圖欲 / 耶律倍 / 李贊華

小山壓大山，大山全無力。
羞見故鄉人，從此投外國。
---&gt;
# [[/Teaching the Annals in Qi/]] &lt;!-- Gongyang Gao's commentary --&gt;
# [[/Is a White Horse a Horse?/]]&lt;!-- Teach negation with 非 in 公孙龍子 and compare with 不 --&gt;
# [[/The Three Character Classic/]]
# [[/Expressing Filial Conduct with Confucius and Hara Saihin/]]
&lt;!--
次韻杏坪先生
父執有君孤不孤
相依遍接搢紳徒
区区自抱地方寸
杳杳重遊天一隅
羇雁飛鳴迷汝國
家人思夢入江都
如教志業青年遂
世上寧無逐臭夫
--&gt;
# [[/Confucianism and the Environment with Sai On/]]&lt;!-- 木假山記 --&gt;
# [[/In Debate with Mencius/]]

===Unit 4: Women's Writing===
In this unit, women's writing from various areas of China will be explored. This is chiefly targeted at poetry and the themes within; from the feminine voice of the Classic of Poetry to the remonstrance towards the Khitan Emperor Tianzuo of Jin by his Consort Dasese. The role of women in courtly society is to be elucidated here!
# [[/An Unmarried Life with Heo Nansŏrhŏn/]]
&lt;!---
貧女吟 
豈是乏容色。工鍼復工織。
少小長寒門。良媒不相識。

夜久織未休。戛戛鳴寒機。
機中一匹練。終作阿誰衣。

手把金翦刀。夜寒十指直。
爲人作嫁衣。年年還獨宿。
---&gt;
# [[/Responding to Lord Trần with Hồ Xuân Hương/]]
&lt;!---
Responding to 陳光靜 Trần Quang Tĩnh

《和陳侯》
愧無才調使人驚，十載風塵貫耳鈴。
已是臨枰知敵手，莫須敲月苦殫精。
為輪為彈隨遭遇，誰鳳誰鶯任賦生。
造物於人何苟惜，明珠休向暗中呈。

莫須 is an important structure to teach here.
---&gt;
# [[/Gaze into the Autumn Night with Taisei Shōan/]]
&lt;!---
秋夜偶成·大成聖安
長天浮爽気，月色興無窮
群犬吠山径，百蟲啼野風
悲秋秋夜永，感古古今同
自是孤窓下，凄然万慮空
---&gt;
# [[/Visiting a Temple with Yu Xuanji/]]
&lt;!---
遊崇真觀南樓覩新及第題名處
雲峰滿目放春晴，歷歷銀鈎指下生。
自恨羅衣掩詩句，擧頭空羨榜中名。
---&gt;
# [[/Remonstrance with Dasese/]]
&lt;!---
https://zh.wikisource.org/wiki/%E8%AB%B7%E8%AB%AB%E6%AD%8C
諷諫歌·大瑟瑟
勿嗟塞上兮暗紅塵。
勿傷多難兮畏夷人。
不如塞奸邪之路兮選取賢臣。
直須臥薪嚐膽兮激壯士之捐身。
可以朝清漠北兮夕枕燕雲。

Dasese (or 萧瑟瑟) was a Khitan consort to Emperor Tianzuo of Liao. She remonstrated him as the Jurchens were beginning to encroach upon the Khitan, and was forced to commit suicide for her remonstrance. Tianzuo would soon pay for his malfeasance. 
---&gt;
# [[/The Love Songs of the Odes/]]
&lt;!---
褰裳
子惠思我，褰裳涉溱。子不我思，豈無他人？狂童之狂也且！
子惠思我，褰裳涉洧。子不我思，豈無他士？狂童之狂也且！

柏舟
彼柏舟，在彼中河，髧彼兩髦，實維我儀，之死矢靡它，母也天只，不諒人只。
汎彼柏舟，在彼河側，髧彼兩髦，實維我特，之死矢靡慝，母也天只，不諒人只。

行露
厭浥行露，豈不夙夜，謂行多露。
誰謂雀無角？何以穿我屋？誰謂女無家？何以速我獄？雖速我獄，室家不足。
誰謂鼠無牙？何以穿我墉？誰謂女無家？何以速我訟？雖速我訟，亦不女從。
---&gt;
# [[/Rules for Women with Ban Zhao/]]
&lt;!--- https://zh.wikisource.org/wiki/%E5%A5%B3%E8%AA%A1 ---&gt;
# [[/The Tragedy of Cai Wenji/]]
&lt;!---
悲憤詩
〔兩漢〕蔡文姬
漢季失權柄，董卓亂天常。
志欲圖篡弒，先害諸賢良。
逼迫遷舊邦，擁主以自強。
海內興義師，欲共討不祥。
卓眾來東下，金甲耀日光。
平土人脆弱，來兵皆胡羌。
獵野圍城邑，所向悉破亡。
斬截無孑遺，屍骸相撐拒。
馬邊懸男頭，馬後載婦女。
長驅西入關，迥路險且阻。
還顧邈冥冥，肝脾為爛腐。
所略有萬計，不得令屯聚。
或有骨肉俱，欲言不敢語。
失意幾微間，輒言斃降虜。
要當以亭刃，我曹不活汝。
豈復惜性命，不堪其詈罵。
或便加棰杖，毒痛參並下。
旦則號泣行，夜則悲吟坐。
欲死不能得，欲生無一可。
彼蒼者何辜，乃遭此厄禍。
邊荒與華異，人俗少義理。
處所多霜雪，胡風春夏起。
翩翩吹我衣，肅肅入我耳。
感時念父母，哀嘆無窮已。
有客從外來，聞之常歡喜。
迎問其消息，輒復非鄉里。
邂逅徼時願，骨肉來迎己。
己得自解免，當復棄兒子。
天屬綴人心，念別無會期。
存亡永乖隔，不忍與之辭。
兒前抱我頸，問母欲何之。
人言母當去，豈復有還時。
阿母常仁惻，今何更不慈。
我尚未成人，奈何不顧思。
見此崩五內，恍惚生狂痴。
號泣手撫摩，當發復回疑。
兼有同時輩，相送告離別。
慕我獨得歸，哀叫聲摧裂。
馬為立踟躕，車為不轉轍。
觀者皆噓唏，行路亦嗚咽。
去去割情戀，遄征日遐邁。
悠悠三千里，何時復交會。
念我出腹子，匈臆為摧敗。
既至家人盡，又復無中外。
城廓為山林，庭宇生荊艾。
白骨不知誰，縱橫莫覆蓋。
出門無人聲，豺狼號且吠。
煢煢對孤景，怛吒糜肝肺。
登高遠眺望，魂神忽飛逝。
奄若壽命盡，旁人相寬大。
為復強視息，雖生何聊賴。
託命於新人，竭心自勖勵。
流離成鄙賤，常恐復捐廢。
人生幾何時，懷憂終年歲。
---&gt;

===Unit 5: Myths and Legends of East Asia===
&lt;!--- Shanhaijing, Zibuyu... Etc. Zhiguai literature. This aims to provide a counterpoint to what Confucius wouldn't discuss - thus Zibuyu. Going straight into Daoism isn't ideal. ---&gt;
# [[/Exploring the World of Mountains and Seas/]]&lt;!-- Structure: 出焉 --&gt;
# [[/Oh, the Qilin!/]] &lt;!--- Even here, the odes can be studied! ---&gt;
# [[/Ultimate Justice with Xiezhi/]] 
# [[/The Virtue of the Fenghuang/]] 
# [[/The Entrapment of Hua Po/]] 
# [[/Nüwa Created the World/]] 

===Unit 6: Nation Focus - Japan===
# [[/The Inariyama Sword/]] 
&lt;!--- short and sweet! ---&gt;
# [[/Entering Japan with Takeda Shingen/]]
&lt;!---
便面蘆間有漁·武田信玄
山色水光烟接天，漁翁江上棹蘆辺
丹青若写得勝景，万里風波一釣船

便面半月照梅花·武田信玄
蘆葦清風垂頂絲，窺魚白鷺水生涯
江南記得曾遊夕，似見梨花院落時

島森哲男. (2015). 武田信玄漢詩校釈. 宮城教育大学紀要, 49, 333–352. https://mue.repo.nii.ac.jp/records/440

似 is a really useful thing to teach early on. 
---&gt; 
# [[/The Oldest Inscription in Japan/]] 
&lt;!--- 宇治橋断碑 ---&gt; 
# [[/The End of a Rebellion/]] 
&lt;!--- https://www.fanyahanwen-corpus.cn/corpus_viewer/%E6%97%A5%E6%9C%AC%E6%BC%A2%E6%96%87/clean/%E6%97%A5%E6%9C%AC/%E6%B1%9F%E6%88%B8%E6%99%82%E4%BB%A3/%E8%9D%A6%E5%A4%B7%E5%85%B1%E5%92%8C%E5%9B%BD/%E5%9C%A8%E6%B5%B7%E7%89%99%E5%BA%9C ---&gt;
# [[/Shinto Teachings with Honda Chikaatsu/]] 
&lt;!--- https://wikisource.org/wiki/%E9%81%93%E4%B9%8B%E5%A4%A7%E5%8E%9F 本田親徳 道之大原 ---&gt;  
# [[/The Diary of Fujiwara no Teika/]] 
&lt;!--- 明月記 ---&gt;
# [[/Reading the History of Japan with Prince Toneri/]]
&lt;!--- 日本書記, etc. ---&gt; 
&lt;!--- # [[/Occupying Taiwan/]] ---&gt;
&lt;!--- I have some colonial literature on me that can be used here. ---&gt;

===Unit 7: Nation Focus - Korea===
&lt;!--- 三國史記 for sure! ---&gt;
&lt;!--- 放蟬賦 by Yi Kyubo ---&gt;
&lt;!--- https://zh.wikisource.org/wiki/%E9%A0%A4%E9%BD%8B%E9%81%BA%E7%A8%BF 頤齋遺稿 黃胤錫 Joseon scholar! ---&gt;
# [[/An Elegy to the Empress with Choe Ja/]]
&lt;!---
Choe Ja
元德大后輓詞·崔滋（최자）
乾極曾客配,坤儀正體元。
枕前朝聖主,帳底見曾孫。
陰慘俄沉月,屋悲便沒軒。
三韓千古淚,七十九年恩。
---&gt;
# [[/Language Reform with Sejong the Great/]]
&lt;!--- 訓民正音 https://github.com/ShiraTheMogul/fanyahanwen-corpus/commit/1ef2b42cc50055affaa5ef39c61b87ed31c34a60 multiple poems and descriptive terms, possibly the best capstone ---&gt;

===Unit 8: Christian Literature===
# [[/A Different Three Character Classic with Hong Xiuquan/]]
# [[/Friar Juan Cobo's Veritable Record/]] 
&lt;!--- 
One of few texts from the Philippines that I have ever found!
https://bnedigital.bne.es/bd/en/viewer?id=0160187c-9d9b-4f34-84d6-bc03fd310c69 
---&gt;
# [[/The Delegate's Edition/]]
# [[/Nestorian Steles during the Tang/]] 
&lt;!--- 大秦景教宣元至本經經幢 and 景教碑 ---&gt;
# [[/Hong Xiuquan's Bible/]]
&lt;!--- https://bible.fhl.net/ob/nob.html?book=407 ---&gt;
&lt;!--- I don't want to focus too much on Hong Xiuquan here, so look for more material, especially from missionaries. ---&gt;

===Unit 9: An Introduction to Daoism===
&lt;!--- And now back to your regularly scheduled Zhuangzi/Laozi/Liezi. But with more interesting stuff. Trust! ---&gt;
# [[/Laozi Explains the Dao/]]
&lt;!--- 道可道，非常道。名可名，非常名。無名天地之始；有名萬物之母。故常無欲，以觀其妙；常有欲，以觀其徼。此兩者，同出而異名，同謂之玄。玄之又玄，衆妙之門。I can expect learners to recognise the stuff here. ---&gt;
# [[/Qingtan with Xie Daoyun/]]
&lt;!--- 謝道韞; mentioned in the sanzijing. could be good!

《泰山吟·謝道韞》
峩峩東嶽高，秀極衝青天。
巖中間虛宇，寂寞幽以玄。
非工復非匠，雲構發自然。
器象爾何物，遂令我屢遷。
逝將宅斯宇，可以盡天年。

《拟嵇中散咏松诗·謝道韞》
遙望山上松，隆冬不能凋。
願想遊不憩，瞻彼萬仞條。
騰躍未能升，頓足俟王喬。
時哉不我與，大運所飄遙。

---&gt;
# [[/The Doubting Neighbour/]] 
# [[/Kuafu Chases the Sun/]] 
# [[/The Frog in a Well/]] 
# [[/Wu wei with King Hui of Liang/]]
# [[/The Old Man that Moves the Mountains/]]
# [[/Master Zhuang Dreams of Butterflies/]]
# [[/The Indifferent Taoist/]] &lt;!--- northern song https://zh.wikisource.org/wiki/%E7%8E%89%E6%AD%B7%E5%AF%B6%E9%88%94 ---&gt; 
&lt;!--- Currently very stereotypical, but there's stuff to work with at least. Need to include those weird Daoist characters among other things. ---&gt;

===Unit 10: Nation Focus - Ryukyu Kingdom===
# [[/Historical Annals with Sai On/]] &lt;!--- Kyuko is an easy cop ---&gt;
# [[/The Enthronement of Shō Tei/]] 
&lt;!---
康熙二十二年封王尚貞敕
皇帝敕諭琉球國中山王世子尚貞：惟爾遠處海隅，虔修職貢；屬在塚嗣，序應承祧。以朝命未膺，罔敢專擅；恪遵典制，奉表請封。朕念爾世守臣節，忠誠可嘉！特遣正使翰林院檢討汪楫、副使內閣中書舍人加一級林麟焻，齎敕封爾為琉球國中山王，並賜爾及妃文幣等物。爾祗承寵眷，懋紹先猷；輯和臣民，慎固封守：用安宗社於苞桑，永作天家之屏翰。欽哉，毋替朕命！故諭。

Teach imperial edicts. 
Consider seeing if there's a letter of acceptance from Shō Tei. 

Recorded in 琉球國志略 
https://ctext.org/wiki.pl?if=en&amp;chapter=966326
---&gt;
# [[/The Twilight of Ryukyu with Shō Ten/]] 
&lt;!---
神田酒樓街燈 尚典
酒樓今秋設芳筵，
一望街燈燦燦連。
烟氣引來通柱上，
光爭星月照神田。
---&gt;
# [[/A Trip to Ryukyu with Luo Sen/]] &lt;!--- Pre-Capstone ---&gt;
&lt;!---
遐邇貫珍 1854-11 - 日本日記 羅森 
https://archive.org/details/HEKC185411/page/n5/mode/1up
A solid description of Ryukyu cultural customs in Volume 11. Absolutely incredible. 
日三日火船直向東北而駛出了臺灣之外幾日不見天涯是時北風大作波浪沖天火船亦甚飄蕩而不能立見有沙鷗隨風而逐浪心直駛七日漸見小山而到琉球琉球一國長闊一百七十五里其國城在地球圖緯線赤道之北二十六度十四分經線中華北京偏東十一度二十四分自明以來世封王爵叨列藩籬其處土產不過蔬菜番薯菜油黑糖等類人民束髻大補是穿草履男女粧飾頭上祇插一簪二簪為別故少年之男女瞥目則無異及其壯也皆留鬚髯故街上長鬚之人甚多甲寅正月初一予上岸遊玩見街上兒童甚多分以銅錢各極歡喜人民亦甚謙恭民居間亦貼新春聯于門外但不見有別等繁華之事那霸有寺寺內有園是名家世宦之墳所以石刊刻姓名年號于碑上每日道人打掃供奉生花樹葉于墓前另有人家祖墳與中國之明塚無異峰巒之上樹木多植民房則以蠻石圍墻內以茅草結屋而居佳物椅棹俱無惟以草蓆屈膝而坐對火盆而吹煙民間亦有識中國言語字墨者
不張舖店惟有墟塲男不貿易婦女為之以貨易貨而外方之金銀弗尚焉然而百姓亦甚畏官長飲食亦甚粗粕甘守樸儉不務奢華亦鮮欺詐板門紙窓夜間亦不防竊曾見途中撿物亦能以返原人公門之內冷冷落落並無案牘之煩淳樸之風畧有同于上古之世我等外國之欲買什物須言于官官為代辦正月初六提督被理衛廉士等一班將官布列威嚴與予乘轎至王宮總理大臣尚宏勳為主席布政大夫馬良才為知客享宴甚豐食物多與中國無異宴後各官皆饋有紙扇烟包布帛等項是物雖粗此亦世子之恭敬外國故亞國亦以禮物而返贈之世子王宮離岸三里在于山頂是名守禮將至其宮一路亦有樹木石牌坊宮室亦甚寬大幽雅垣局可觀其處多栽鳳尾草森樹等類以障陰山邊田土樹藝五穀近海沙田水漲之後人收其沙以煎鹽此時明月當圓予覽山川亦足見一方之風景 
---&gt;
&lt;!--- 中山世鑑 and so on. Lots of poetry too. ---&gt;

===Unit 11: Nation Focus - Singapore===
&lt;!--- National Library of Singapore has a poetry series that's super good! ---&gt;

===Unit 12: Literary Chinese in Medicine===
&lt;!--- do not endorse the medical practices discussed in these...make sure to link back to the heavenly stems here as they are associated with specific body parts. ---&gt;
# [[/The Books of the Yellow Emperor/]] 
&lt;!-- 黃帝内徑 ---&gt;
# [[/Deviant Qi with Zhang Congzheng/]]
&lt;!--- https://zh.wikisource.org/wiki/%E5%84%92%E9%96%80%E4%BA%8B%E8%A6%AA ---&gt;
# [[/Anatomy with Sugita Genpaku/]]
&lt;!--- 解体新書 ---&gt;
# [[/A Lost Wu Medical Text analysed in Japan/]]
&lt;!--- 難經古義 ---&gt;

===Unit 13: People Focus - Zhuang peoples===
&lt;!--- https://mooc1.chaoxing.com/mooc-ans/ztnodedetailcontroller/visitnodedetail?courseId=84745403&amp;knowledgeId=84745463&amp;_from_=&amp;_fromV2_=&amp;rtag= 《峤西诗钞》 is also a really good shout. ---&gt;
&lt;!--- Basically, there are Zhuang and Tangut peoples who wrote in Literary Chinese, and their inclusion here is to show that even those who made their own scripts would use this tongue. 张鸿翮 imported the character 朴 to describe a bug, for example. ---&gt;
# [[/Zhuang poetry with Zhang Honghe/]]
&lt;!--- https://wenyi.gmw.cn/2024-06/25/content_37398911.htm

一是忠实记录了汉诗创作与古壮字交融的文化现象。清代壮族诗人张鸿翮（hé）《大塘谣》（《峤西诗钞》卷二）云：

去了休。去到大塘红蓼洲。红蓼生花，不结子。绿朴生花，毬见毬。

诗中所说“绿朴”，是壮族对柚子的惯称。“柚子”，壮语发音为“bug”。根据《古壮字字典》，其对应的古壮字为“朴（㭪）”。诗人将古壮字运用到汉文诗歌创作中，刻下了明清壮汉文化交相辉映的注脚。

This sort of thing is why Zhuang and Tangut inclusion is important, as they show how flexible Literary Chinese can be. ---&gt;

&lt;!---
Possible Jurchen/Khitan focus? 
耶律楚材 - Served 窝阔台, 玄風慶會錄 is short and respectable enough to work with.
---&gt;

===Unit 14: People Focus - Tangut peoples===
&lt;!--- 羅福萇 and 羅振玉 wrote studies on Western Xia / Tangut script. Look for poets and stuff. ---&gt; 

===Unit 15: Literary Chinese in the Military===
&lt;!--- Real Sun Zi hours! 7 Military Classics are an obvious shout, but look for more stuff too. ---&gt;
# [[/Fū! Rin! Ka! Zan!/]]
# [[/A Bilingual Stele of the Khitans/]]
&lt;!--- https://wikisource.org/wiki/%E5%A4%A7%E9%87%91%E7%9A%87%E5%BC%9F%E9%83%BD%E7%B5%B1%E7%B6%93%E7%95%A5%E9%83%8E%E5%90%9B%E8%A1%8C%E8%A8%98 ---&gt;
# [[/Going to war with Boyan/]]
&lt;!---
Boyan's Poem from the 元史
　　伯顏，蒙古巴林部人。至元十一年拜中書左丞相，總兵伐宋。官至開府儀同三司，薨贈太師，封淮安王，諡忠武。

　　《玉堂嘉話》：初，宋未下時，江南謠云：「江南若破，白雁來過。」當時莫喻其意。及宋亡，蓋知指丞相巴延也。

　　過梅嶺岡留題

馬首經從庾嶺回 【 庾嶺回　七修類稿（乾隆刊本）卷四十六作「嶺島歸」。】 ，王師到處悉平夷。擔頭不帶江南物，只插梅花一兩枝。

　　《七修類藳》：伯顏下江南，過金陵梅嶺岡詩云云。所以著名，亦有是善。
---&gt;
# [[/An Edict from the Xianbei/]]
&lt;!---
教義詔 楊廣
武有七德，先之以安民。政有六本，興之以教義。高麗高元，虧失藩禮，將欲問罪遼左，恢宣勝略。雖懷伐國，仍事省方。今往涿郡，巡撫民俗。其河北諸郡及山西、山東年九十已上者，版授太守；八十者，授縣令。
---&gt;
# [[/The Suppression of the Kingdom of Dongning/]]
&lt;!---
台灣鄭氏始末
https://ctext.org/wiki.pl?if=en&amp;chapter=139938

Largely a record of wars in Dongning rather than anything about the trade etc, so it fits here. 
---&gt;
# [[/The Shunzhi Emperor vs Li Zicheng/]]
&lt;!---
順治帝
告示
逆酋李自成已於通城斃命，各地鄉勇務隨我軍剿殺逆賊殘餘,凡有斬獲逆酋及擒獲逆酋交我軍者，一經驗證，按軍功論級給賞，必以示我朝皇恩浩蕩。
大清順治二年五月二十四日

恩詔
今月何日，為國曆改歲之履端,即為永昌書元之紀念？緬惟我朝民眾，三元肇慶，四始發祥。陳椒酒以飛觴，躋堂介壽；換桃符以獻歲，辟戶書新。翹望德容，河勝額手。今山河如舊，歲序更新;今天下同春，咸頒麗澤。願我朝君臣與萬民同樂，共沐化日光天，方不虛度韶華。
永昌二年新正初一

There's probably better choices here. Review. 
---&gt;
# [[/The Art of War/]]

===Unit 16: Nation Focus - Vietnam===
&lt;!--- https://github.com/ShiraTheMogul/fanyahanwen-corpus/commit/cfe6700e01f6fd59616a375d31aa8cd096677be1 this first ---&gt; 
# [[/Ancestor Veneration with the Descendants of Zhu Xi/]] 
&lt;!--- https://github.com/ShiraTheMogul/fanyahanwen-corpus/tree/main/corpus%2F%E8%B6%8A%E5%8D%97%E6%BC%A2%E6%96%87%2Fclean  somewhere in here ---&gt;
# [[/Spreading Revolutionary Consciousness with Phan Bội Châu and Liang Qichao/]] 
&lt;!--- 越南亡國史 Possibly the most important text in Vietnamese history, not even gonna lie. https://zh.wikisource.org/wiki/%E8%B6%8A%E5%8D%97%E4%BA%A1%E5%9C%8B%E5%8F%B2 ---&gt;
# [[/Academia in Literary Chinese between East and West/]] 
&lt;!--- 南風雜誌 is a massive shout here. Absolutely amazing series. ---&gt;

===Unit 17: Historical Annals and Encyclopediae===
&lt;!--- 永樂大典 will teach how to infer from gaps in texts! 《編類》 is an incredibly interesting essay from here that can bring up the odes and Confucius's「思無邪」quote. It can prepare students for the wrath of Qing academia later. ---&gt; 
# [[/An Introduction to Biographical Paintings/]]
&lt;!-- 
Many older paintings include biographies at the top in Literary Chinese. Students need to learn these.
https://commons.wikimedia.org/wiki/File:%E6%AD%B7%E4%BB%A3%E8%81%96%E8%B3%A2%E5%8D%8A%E8%BA%AB%E5%83%8F_%E5%86%8A_%E8%AB%B8%E8%91%9B%E4%BA%AE_(Zhuge_Liang).png - Famous figure, also part of a very notable series.
https://commons.wikimedia.org/wiki/File:Otomo-Sorin-2.jpg - Contains the Japanese repetition character 々
https://commons.wikimedia.org/wiki/File:Toyotomi_hideyoshi4.jpg - simply has aura
--&gt;
# [[/The History of Liao, Jin, and Song with Toqto'a/]] &lt;!--- 脱脱 ---&gt;
# [[/Two Years in the Forbidden City with Yu Deling/]] &lt;!--- 清宮禁二年記 https://zh.wikisource.org/wiki/%E6%B8%85%E5%AE%AE%E7%A6%81%E4%BA%8C%E5%B9%B4%E8%A8%98 ---&gt;
# [[/Selected Records of the History of the Da Shun/]]
&lt;!--- Fair Use of a 2010 book written in Literary Chinese about the Da Shun dynasty. Limit to 500 characters, if that. Use to encourage recognition of Simplified variants and modern Wenyanwen. ---&gt;
# [[/Documenting the World with Terajima/]]
&lt;!--- 和漢三才図会 寺島良安, built off 三才圖會 ---&gt;

===Unit 18: Buddhist Literature===
&lt;!--- You would be forgiven for wondering why this is so late, but if you look at many classical Buddhist texts you'll quickly see a ton of loanwords that make it significantly more difficult to read than the average text. Thus, it goes here for now. ---&gt;
&lt;!--- Place focus on practical stuff first. Stuff you can and WILL see in Buddhist temples. Stuff Buddhists can take away immediately. Skills-based approach feels strongest here. ---&gt;
&lt;!--- Look at Northern Liang and Later Qin literature, as there is a ton of work by translators from India during the 16 kingdoms period, particularly those two. ---&gt;
&lt;!--- Stuff by Bodhidharma 達摩 could be fun too https://zh.wikisource.org/wiki/Author:%E9%81%94%E6%91%A9 ---&gt;
# [[/Dipping your feet in with Wenyan Shu/]]
&lt;!---
華亭
世尊遺法本忘言，教外別傳意已圓。
只履攜將蔥嶺去，不妨來上月明船。
---&gt; 
# [[/The Seven Tathagatas/]] 
&lt;!---
南無寶勝如來
南無多寶如來
南無妙色身如來
南無廣博身如來
南無離怖畏如來
南無甘露王如來
南無阿彌陀佛

Use to introduce some core vocabulary in repetitive manner. 

Useful phrases from my trip to Jing'an Temple
南無本師釋迦牟尼佛 - Pay homage to the root teacher
南無大悲觀世音菩薩 - Pay homage to the goddess of mercy 
廣種福田 - widely plant a meritorious field 
---&gt;
# [[/Two Buddhist Temples in Shanghai/]] 
&lt;!---
留雲禪寺
雲留雲翔領畧幾許禪機此地有雲散天開真如界。
塔內塔外普示無邊圓覺是故曰塔影雙照解脫門。

歲次壬午冬月吉旦。
覺醒敬撰。
楊胡生沐手恭書。
善信印利明敬獻。 
---&gt;
&lt;!--- 福慧宝鼎 慧明大和尚 - introduce the Buddhist timekeeping system with 佛歷 around this point. 
赤烏古剎
建寺一千七百六十周年紀念

古剎三國建
滬瀆有重玄
石佛音淨現
聖跡顯重元
唐時稱永泰
宋敕名靜安
聖祖留佛闡
仲師移伽藍
元收八景偈
明鑄鐘聲梵
清樹化羅漢
選賢十方讚
佛日普光明
福慧共修善
鼎運昌隆際
轉正法輪緣

歲次丁亥住持慧明監製
---&gt;
# [[/Foreseeing Monkhood with Yi Xing/]]
&lt;!--- 看命一掌金 ---&gt;
# [[/A Trip to Western Xia with Zhi Guang and Hui Zhen/]]
&lt;!--- https://zh.wikisource.org/wiki/%E5%AF%86%E5%91%AA%E5%9C%93%E5%9B%A0%E5%BE%80%E7%94%9F%E9%9B%86 ---&gt;
&lt;!--- https://zh.wikisource.org/wiki/%E5%AF%86%E5%92%92%E5%9C%93%E5%9B%A0%E5%BE%80%E7%94%9F%E9%9B%86 ---&gt;
# [[/Jizang's Three Discourses/]]
&lt;!--- https://zh.wikisource.org/wiki/%E4%B8%89%E8%AB%96%E7%8E%84%E7%BE%A9 ---&gt;
&lt;!---
I saw these texts being quoted and thus should consider them in some capacity.
《般若波羅蜜多心經》
《金剛般若波羅蜜經》
《一切智光明仙人慈心因緣不食肉經》
《妙法蓮華經》
《大般涅槃經》
《大方等大集經》
《大毘盧舍那成佛神變加持經蓮華胎藏悲生曼荼羅廣大成就儀軌供養方便會》/ 胎藏曼荼羅 
《佛說救拔焰口餓鬼陀羅尼經》
《雜阿含經》

Look at Japan's 五山文学
---&gt;

===Unit 19: People Focus - Manchu peoples===
# [[/Qing dynasty Poetry with Nara Singde/]] 
&lt;!--- 飲水詞 納蘭性德 https://zh.wikisource.org/wiki/Author:%E7%B4%8D%E8%98%AD%E6%80%A7%E5%BE%B7 ---&gt;
# [[/Amassing Words with the Kangxi Emperor/]] 
&lt;!--- Kangxi Dictionary Abstract - https://zh.wikisource.org/wiki/%E5%BA%B7%E7%86%99%E5%AD%97%E5%85%B8 ---&gt;
# [[/Amassing Literature with the Qianlong Emperor/]] 
&lt;!--- Siku Quanshu abstract https://zh.wikisource.org/wiki/%E5%9B%9B%E5%BA%AB%E5%85%A8%E6%9B%B8%E7%B8%BD%E7%9B%AE%E6%8F%90%E8%A6%81 ---&gt;
&lt;!---
Yongzheng Emperor's Poetry 
https://zh.wikisource.org/wiki/Author:%E9%9B%8D%E6%AD%A3%E5%B8%9D
《和碩怡賢親王祭文》

Also include 滿洲國 stuff to show the fall of the Qing and attempts to preserve it through becoming a Japanese puppet state. It is important to show how Literary Chinese can be misused as well. 滿洲國建國宣言 is a good shout, as is 法制 to prepare students who may be interested in Taiwan legal stuff later down the road. 
https://zh.wikisource.org/wiki/Category:%E6%BB%BF%E6%B4%B2%E5%9C%8B
---&gt;
# [[/Paintings and Beauty with Puru Aisin-Gioro/]]
&lt;!--- Saw these in Shanghai Museum with some writing, seemed really cool. Teaches another skill. ---&gt;

===Unit 20: Qing-RoC Literature===
&lt;!--- many writers here, will be difficult to sift through. Include 四库全書 abstracts and stuff here. ---&gt;
# [[/Jewish Refugees in Shanghai/]] 
&lt;!--- Show passports, certificates, etc, from the Jewish Refugee Museum, anonymised. ---&gt;
# [[/A Literary Chinese Abstract/]] 
&lt;!--- Abstracts from siku quanshu, probably want others ---&gt;
# [[/Lament with Lu Ruoteng/]] 
&lt;!---
《疑猜》盧若騰，東寧國
盟誓變為交質子，春秋戰國風如此；末世上下相疑猜, 更質妻子防逃徙。
此法只可羈庸奴，若遇梟雄術窮矣；妻可再娶子再育, 安能長坐針氈裏。
我贈一法君記存；推心置腹人知恩；眾人畜之眾人報, 幾個國士在君門。
盧若騰撰，陳漢光編輯，《島噫詩》，臺灣文獻叢刊第二四五種（臺北:臺灣銀行經濟研究室，1968年）21頁。
---&gt;
# [[/Common Linguistics Knowledge in the RoC/]]
&lt;!--- 音韻常識 ---&gt;

==References used for this page==
* Yang, B. (2016). 文言语法 [Literary Chinese Grammar] (1st ed). 中华书局 [Zhonghua Book Company]. ISBN: 978-7-101-11619-9
* Priestley, K. E., &amp; Shou-jung, C. (1962). China’s Men of Letters, Yesterday and Today. Dragonfly Books.
{{BookCat}}</text>
      <sha1>0dh17frwo6v3zom47v44fhno47p0vaq</sha1>
    </revision>
    <revision>
      <id>4656179</id>
      <parentid>4656170</parentid>
      <timestamp>2026-08-03T09:08:46Z</timestamp>
      <contributor>
        <username>Shira the Mogul</username>
        <id>3560559</id>
      </contributor>
      <minor />
      <comment>/* Useful resources */ I've had a google sheet up for like 3 months i need to put it somewhere</comment>
      <origin>4656179</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="40448" sha1="e9xwvbemmpbbx8ecokbyfr34p343u56" xml:space="preserve">__notoc__

Welcome to the Wikibook for Literary Chinese (Known as 漢文 &quot;Han Language&quot; in East Asia or 文言 &quot;Literary Language&quot; in China), aimed at individuals hoping to gain a general knowledge of it before progressing into genres they wish to be acquainted with. 

This is not the [[Classical Chinese]] textbook, which is aimed at Chinese Zhou-Qin era texts. This  text aims to shed light on post-Zhou-Qin texts across East Asia, which mimic those texts. However, as Zhou-Qin era texts served as the main body from which individuals learned, they are employed here as and when they are considered necessary or otherwise useful. It does so through a &quot;buffet&quot; approach, showering you, the reader, with an ocean of texts of myriad genre. 

==Table of Contents==

=== Front matter ===

* [[/Introduction/]]
* [[/Appendices/]]

=== Useful resources ===
These are quick grab-bags that can be useful for vocabulary-building. 
* [[/Antonym List/]] &lt;!--- 文/武，大/小，厚/薄，橫/縱...---&gt;
* [[/Collocation Groups/]] &lt;!--- e.g. 四象，三靈…… ---&gt;
* [[/Pronoun Table/]]
* [https://zh.wikiversity.org/wiki/Subject:華製新漢語及中文固有語/嚴譯及部定詞等 Yan Fu's Qing-era translations for modern terms] &lt;!--- Wikiversity has this (https://zh.wikiversity.org/wiki/Subject:華製新漢語及中文固有語/嚴譯及部定詞等) and the below, I will effectively be translating a lot of it! ---&gt;
* [https://zh.wikiversity.org/wiki/Subject:華製新漢語及中文固有語/上古語考輯 Communicative Terms]
&lt;!--- this will be translated eventually, but right now it's bad to just leave this here. ---&gt;

=== Useful primers ===
Across history, many primers have been made for teaching Literary Chinese to children. These are a few that are recommended for use alongside this work, ideally in flashcards. 
* [https://www.fdgwz.org.cn/Web/Show/11308 倉頡篇] - Cangjie's Chapters, the earliest one. It is extant, but incomplete. It contains several rare characters, and so if used, I would personally recommend doing so later, or out of interest. 
* 三字經 - The Three Character Classic, an excellent piece for Confucian education. Pair with 弟子规 for best results. 
** 三字經（太平天國版）- For Christians, there is a version made by Hong Xiuquan from the Taiping Rebellion. Despite the context, it is a legitimately useful primer and can be used to self-teach for the Delegate's Edition of the Christian Bible. 
* 千字文 - The Thousand Character Classic, a remarkable piece of constrained writing that only uses each character once. Amazing for building vocabulary whilst seeing historical allusions and the like. 
* 五字鑑 - The Five-Character Mirror, essentially the 24 Histories of China compressed into a primer. Uses 5-character couplets, the longest in this list. 
* 龍文鞭影 - The Shadow of Longwen's Whip, a historical allusion trainer. Best paired with a context piece.

===Unit 0: The Han script===
This unit is intended for those with no familiarity of the Han script. It will prepare you for the units ahead, teaching largely pictographic characters. 

By the end of this unit, students will:
* Recognise around 50 characters.
* Understand how characters are composed and how this gives them meaning.
* Have a basic idea of how to handwrite and/or type characters using the Cangjie Input Method.
* Know some bare basics of Literary Chinese grammar (e.g. Basic word order, where adjectives go, lack of &quot;is&quot;, 有...)

Lessons:
# [[/An Introduction to the Han Script/]]
# [[/People, Big and Small/]]
# [[/How do we write Chinese?/]]
# [[/What are Chinese characters, anyway?/]]
# [[/The Sun, the Moon, and the Five Elements/]]
# [[/Getting Familiar with Body Parts/]]
# [[/Using Numbers and Using Weapons/]] &lt;!--- 竹戈十大中一弓廿卜---&gt;
# [[/Tilling the Fields with 有/]] &lt;!--- 山田 ---&gt;
# [[/How Characters are Made/|How Characters are Made with Kiyohara no Sanemoto]] 
# [[/Cangjie Created Characters/]] &lt;!--- Get people to use Cangjie ---&gt;
# [[/The Kangxi Radical System/]] &lt;!--- Introduce some monoradical texts to train recognition. ---&gt;

===Unit 1: Basic Skills===
This unit is intended for those with minimal familiarity with the Han script and no familiarity with Literary Chinese. There is a focus on simple structures, skills for dissecting common textual structures, and short-form poetry in this unit. 

Before starting this unit, students should:
* Recognise around ~30 characters. 
* Can use Cangjie input. 
* Have given Unit 0 a cursory glance. 
&lt;br&gt;
By the end of this unit, students will:
* Recognise around ~100 characters. 
* Comprehend numbers, the Heavenly Stems, and the Earthly Branches, and be able to use them to quantify time and date.
* Intuit the basic topic -&gt; comment idea behind Literary Chinese. &quot;This, it is...&quot; 
* Understand basic function words such as 也, 而, 有, and 謂.

Lessons:
# [[/The All-Purpose 也/]]
# [[/An Introduction to Chinese Numbers/]] &lt;!--- It is hard to find authentic materials for this ---&gt;
# [[/One, Two, Left, and Right with Gongsun Long/]]
&lt;!---
曰：「二有一乎？」

曰：「二無一。」

曰：「二有右乎？」

曰：「二無右。」

曰：「二有左乎？」

曰：「二無左。」

曰：「右可謂二乎？」

曰：「不可。」

曰：「左可謂二乎？」

曰：「不可。」

曰：「左與右可謂二乎？」

曰：「可。」
---&gt;
# [[/The Heavenly Stems/]] &lt;!--- Introduce ordinals, which will be used to demonstrate sentence patterns later. ---&gt;
# [[/Tell the Time with Earthly Branches/]] &lt;!--- Introduce verbs and timekeeping ---&gt;
# [[/Lunar Dates with the Spring and Autumn Annals/]]
&lt;!--- Vocabulary: 歲，年，朔，月，日，來，前，初，正，春秋夏冬，曆，上，下. Consider including traditional names for months in a list. ---&gt;
# [[/Skimming for Major Events in Historical Annals/]] 
&lt;!--- Don't simply use Confucius's Chunqiu: We can use texts inspired by it. 

E.g. 三國史記 - 十五年京城旱。秋七月，蝗。very few new characters, lots one can use. Instantly able to use. 
https://zh.wikisource.org/wiki/%E4%B8%89%E5%9C%8B%E5%8F%B2%E8%A8%98/%E5%8D%B701

Skimming annals is very possible and a very useful skill. Don't skip out on it. Teach students to skim read!!! 
---&gt;
# [[/Dinner with the Daimyo/]]
&lt;!-- 
侍宴·大友皇子
皇明光日月，帝徳載天地。
三才併秦昌，万国表臣義。
--&gt; 
# [[/In Discourse with Jibong/]]
&lt;!--
芝峰類說 
倭國謂田爲畠。謂水田爲田。火田爲畑。猶我國以水田爲畓也。故官名有畠山殿。地名有畑島云。
--&gt;
# [[/Shinto FAQ with Honda Chikaatsu/]] 
&lt;!--- https://wikisource.org/wiki/%E7%9C%9E%E9%81%93%E5%95%8F%E5%B0%8D 眞道問對 本田親徳 really good way of operationalising 乎 and much of the early grammar. 

問 天帝無始無終乎。
對 天帝無始無終也。
旣以無始無終之力
與無始無終之體
造無始無終之萬物。
其功亦無始無終也。

問 天地大原在道乎。
對 天地大原實在道。
鬼神依道而立。
人民依道而活。
萬物依道而息。

This is great! ---&gt;

&lt;!---
Some cool stuff I saw someone studying from
https://zh.wikisource.org/wiki/%E8%87%B3%E5%B0%8F%E4%B8%98%E8%A5%BF%E5%B0%8F%E7%9F%B3%E6%BD%AD%E8%A8%98#
https://zh.wikisource.org/wiki/%E6%A0%B8%E8%88%9F%E8%A8%98

Could be used for period focus
---&gt;

===Unit 2: An Overview of Sinitic Poetry===
This unit will teach you how Sinitic Poetry operates; - that is, the way individuals in the Sinosphere compose poetry in Literary Chinese. Despite this language's fall out of favour in the past century, this tradition is still remarkably alive and well, and their short length makes them more accessible than elaborate prose. In this unit, you will begin from the ''Classic of Poetry'' before travelling through poems from the Tang dynasty, Singapore, Japan, Vietnam, the Ryukyu Kingdom, and Korea. When introducing poetry, I will furthermore use the language from the nation it is from to show how it is recited by its people. 

After discussing the Classic of Poetry, we will also be a small detour into a discussion on Ping-Ze 平仄, the Tang dynasty system of alternating tones, so to produce rhyme on tonal and phonological levels. This had a major impact on Literary Chinese poetry as a whole!

By the end of this Unit, students will:
* Recognise around 120 more characters.
* Be able to explain how Sinitic Poetry rhymes and the themes it contains.
* Be able to use function words such as 在, 無, 不, 聿, and 于/於 in poetic contexts.
* Recognise the switch between 吾/我 in the subject-object positions and demonstrate it in usage.
* (Chinese speakers) Be able to differentiate 于 and 於, and understand the &quot;interest(ed) in&quot; meaning of 好 in most circumstances.
&lt;!---
Summary of the above part about 于 and 於 for other editors:
于 and 於 were distinct words for an extremely long time and were still such to Literary Chinese writers. Their &quot;merging&quot; through Simplified-Traditional Chinese distinctions is a very modern thing. I will summarise their usages here, using Pulleyblank's Outline of Classical Chinese Grammar (2000);
* 于 - This can mean &quot;to go&quot; or &quot;to/at&quot;. 黃鳥于飛 &quot;The yellow birds go flying&quot;. Must be post-verbal. It can also appear in 至于.
* 於 - This is an all-purpose locative preposition - from &quot;on/at/in&quot; to &quot;from&quot; or even &quot;than&quot; (甲於乙). The implication of motion is not there at all. Must be pre-verbal. It can also appear in 之於 or be an archaic noun for a crow 於 (烏).
---&gt;

Lessons:
# [[/Across the Rivers with Emperor Puliuru Guang/]]
&lt;!---
春江花月夜·楊廣
夜露含花氣，春潭漾月暉。
漢水逢遊女，湘川值二妃。

This is really simple and can elucidate Ping-Ze easily.
---&gt;
# [[/To Study the Odes/]] 
&lt;!-- 蟋蟀·姬旦 國風·唐風
蟋蟀在堂，歲聿其莫。今我不樂，日月其除。無已大康，職思其居。好樂無荒，良士瞿瞿。
蟋蟀在堂，歲聿其逝。今我不樂，日月其邁。無已大康，職思其外。好樂無荒，良士蹶蹶。
蟋蟀在堂，役車其休。今我不樂，日月其慆。無已大康，職思其憂。好樂無荒，良士休休。
--&gt;
&lt;!-- 黃鳥 小雅·鴻鴈之什
黃鳥黃鳥，無集于穀，無啄我粟。
此邦之人，不我肯穀。言旋言歸，復我邦族。

黃鳥黃鳥，無集于桑，無啄我粱。
此邦之人，不可與明。言旋言歸，復我諸兄。

黃鳥黃鳥，無集于栩，無啄我黍。
此邦之人，不可與處。言旋言歸，復我諸父。
--&gt;
# [[/A Detour into Orthodox Ping-Ze/]] 
&lt;!--- 平 and 仄 are useful characters themselves. Show 仄 in the binomes 反仄，歉仄，逼仄 as it's often difficult to immediately use ---&gt;
# [[/The Restraint of Du Fu/]] 
# [[/The Longing of Li Bai/]] 
# [[/The Environment with Bukha Timur/]]
&lt;!---
西湖竹枝詞·布哈特穆爾
湖上春歸人未歸，桃紅柳緑黄鶯飛。
桃花落時多結子，楊花落處秪沾衣。

宫词·布哈特穆爾
玉樓珠箔晚天涼，秋色依稀滿建章。
金井梧桐霜葉盡，自隨流水出宮牆。

Mongol writer from the Uyghur Kingdom of Gaochang
Spammed Ctrl+F in https://zh.wikisource.org/wiki/%E5%BE%A1%E9%81%B8%E5%9B%9B%E6%9C%9D%E8%A9%A9_(%E5%9B%9B%E5%BA%AB%E5%85%A8%E6%9B%B8%E6%9C%AC)
---&gt;
# [[/Pillow Talk with Guan Yunshi/]]
&lt;!---
紅繡鞋·貫雲石
挨著靠著雲窗同坐，偎著抱著月枕雙歌，聽著數著愁著怕著早四更過。四更過情未足，情未足夜如梭。天哪，更閏一更兒妨甚么！

Uyghur author!
---&gt;
# [[/Buddhist Philosophy with Ngô Chân Lưu and Taisei Shōan/]]
&lt;!-- 元火·吳真流
木中元有火，元火復還生。
若為木無火，鉆燧何有萌。--&gt;
&lt;!-- 杜鵑·大成聖安
夢覚孤床静
杜鵑帯雨飛
一声来近枕
何者不沾衣
--&gt;
# [[/Odes with Mō Taiei and Zheng Chengxun/]]
&lt;!-- 詠松·毛泰永
植體宜千仞，垂陰動百尋。
李膺真烈烈，和嶠自森森。
桃李何堪較，雪霜安得侵。
萬年身不老，種子又成林。
AKA Inoha Seiki 伊野波 盛紀 --&gt;
&lt;!-- 詠班蘭·鄭成勛
南國多芳草，班蘭最有名。
深根將綠茁，長葉亦叢生。
取味迎賓合，入厨任水烹。
可憐經一用，擲棄不留情。

鄭成勛《樵隱詩集》 https://nus.edu.sg/nuslibraries/dsprojects/sg-jiutishi/poem/827 --&gt;

# [[/A Golden Cup and the Fall of a Dynasty with Yan Fu/]] 
&lt;!---
鞏金甌·嚴復
鞏金甌，承天幬，民物欣鳧藻，喜同袍。
清時幸遭，真熙皞，帝國蒼穹保。
天高高，海滔滔。
This has music to it, which I think can add a lot. It is also necessary to introduce Yan Fu early given he did translation. ---&gt;
# [[/On a Journey with Sa Dula/]]
&lt;!---
無題·薩都剌
為客三年海上洲，故鄉何處瘴雲稠。
數千里外蠻人域，十八灘頭過客舟。
時有山禽呼姓字，或從海鳥作朋儔。
故人珂珮周旋處，紫殿風清十二樓。
https://zh.wikisource.org/wiki/%E7%84%A1%E9%A1%8C_(%E8%96%A9%E9%83%BD%E5%89%8C)

A naturalised Mongol scholar who made a beautiful poem. This'll be a capstone.
---&gt;
&lt;!---
朝中措·襄陽古道灞陵橋
襄陽古道灞陵橋，詩興與秋高。
千古風流人物，一時多少雄豪。

霜清玉塞，雲飛隴首，風落江皋。
夢到鳳凰台上，山圍故國周遭。

北郊晚步
陂水荷凋晚，茅檐燕去涼。
遠林明落景，平麓淡秋光。
群牧歸村巷，孤禽立野航。
自諳閑散樂，園圃意尤長。

Jurchen poet and grandson of Emperor Shizong of Jin. He's a Zen Buddhist, so we'll go back to him later.
---&gt;

===Unit 3: Confucianism and the World===
This is a Confucian-themed unit with a smattering of other items. You will see the odd geography of the past, early linguistic philosophy, and terrifying breakaway states!

By the end of this unit, students should be able to:
* Recognise around 200+ characters.
* Read basic annals and histories with some dictionary assistance, and comprehend 3-character structures reliably.
* Have encountered basic grammatical points such as 之、乎、者、也、而、則、乃、所、以、於、于、與、且、蓋、and 夫. 
** 於 and 于 should be distinguishable.
* Survive a text of at least 250 characters and read for gist.

Lessons:
# [[/A Brief Overview of Confucianism/]] 
# [[/The Mountains with Yelü Tuyu/]]
&lt;!---
立木海上刻詩 耶律圖欲 / 耶律倍 / 李贊華

小山壓大山，大山全無力。
羞見故鄉人，從此投外國。
---&gt;
# [[/Teaching the Annals in Qi/]] &lt;!-- Gongyang Gao's commentary --&gt;
# [[/Is a White Horse a Horse?/]]&lt;!-- Teach negation with 非 in 公孙龍子 and compare with 不 --&gt;
# [[/The Three Character Classic/]]
# [[/Expressing Filial Conduct with Confucius and Hara Saihin/]]
&lt;!--
次韻杏坪先生
父執有君孤不孤
相依遍接搢紳徒
区区自抱地方寸
杳杳重遊天一隅
羇雁飛鳴迷汝國
家人思夢入江都
如教志業青年遂
世上寧無逐臭夫
--&gt;
# [[/Confucianism and the Environment with Sai On/]]&lt;!-- 木假山記 --&gt;
# [[/In Debate with Mencius/]]

===Unit 4: Women's Writing===
In this unit, women's writing from various areas of China will be explored. This is chiefly targeted at poetry and the themes within; from the feminine voice of the Classic of Poetry to the remonstrance towards the Khitan Emperor Tianzuo of Jin by his Consort Dasese. The role of women in courtly society is to be elucidated here!
# [[/An Unmarried Life with Heo Nansŏrhŏn/]]
&lt;!---
貧女吟 
豈是乏容色。工鍼復工織。
少小長寒門。良媒不相識。

夜久織未休。戛戛鳴寒機。
機中一匹練。終作阿誰衣。

手把金翦刀。夜寒十指直。
爲人作嫁衣。年年還獨宿。
---&gt;
# [[/Responding to Lord Trần with Hồ Xuân Hương/]]
&lt;!---
Responding to 陳光靜 Trần Quang Tĩnh

《和陳侯》
愧無才調使人驚，十載風塵貫耳鈴。
已是臨枰知敵手，莫須敲月苦殫精。
為輪為彈隨遭遇，誰鳳誰鶯任賦生。
造物於人何苟惜，明珠休向暗中呈。

莫須 is an important structure to teach here.
---&gt;
# [[/Gaze into the Autumn Night with Taisei Shōan/]]
&lt;!---
秋夜偶成·大成聖安
長天浮爽気，月色興無窮
群犬吠山径，百蟲啼野風
悲秋秋夜永，感古古今同
自是孤窓下，凄然万慮空
---&gt;
# [[/Visiting a Temple with Yu Xuanji/]]
&lt;!---
遊崇真觀南樓覩新及第題名處
雲峰滿目放春晴，歷歷銀鈎指下生。
自恨羅衣掩詩句，擧頭空羨榜中名。
---&gt;
# [[/Remonstrance with Dasese/]]
&lt;!---
https://zh.wikisource.org/wiki/%E8%AB%B7%E8%AB%AB%E6%AD%8C
諷諫歌·大瑟瑟
勿嗟塞上兮暗紅塵。
勿傷多難兮畏夷人。
不如塞奸邪之路兮選取賢臣。
直須臥薪嚐膽兮激壯士之捐身。
可以朝清漠北兮夕枕燕雲。

Dasese (or 萧瑟瑟) was a Khitan consort to Emperor Tianzuo of Liao. She remonstrated him as the Jurchens were beginning to encroach upon the Khitan, and was forced to commit suicide for her remonstrance. Tianzuo would soon pay for his malfeasance. 
---&gt;
# [[/The Love Songs of the Odes/]]
&lt;!---
褰裳
子惠思我，褰裳涉溱。子不我思，豈無他人？狂童之狂也且！
子惠思我，褰裳涉洧。子不我思，豈無他士？狂童之狂也且！

柏舟
彼柏舟，在彼中河，髧彼兩髦，實維我儀，之死矢靡它，母也天只，不諒人只。
汎彼柏舟，在彼河側，髧彼兩髦，實維我特，之死矢靡慝，母也天只，不諒人只。

行露
厭浥行露，豈不夙夜，謂行多露。
誰謂雀無角？何以穿我屋？誰謂女無家？何以速我獄？雖速我獄，室家不足。
誰謂鼠無牙？何以穿我墉？誰謂女無家？何以速我訟？雖速我訟，亦不女從。
---&gt;
# [[/Rules for Women with Ban Zhao/]]
&lt;!--- https://zh.wikisource.org/wiki/%E5%A5%B3%E8%AA%A1 ---&gt;
# [[/The Tragedy of Cai Wenji/]]
&lt;!---
悲憤詩
〔兩漢〕蔡文姬
漢季失權柄，董卓亂天常。
志欲圖篡弒，先害諸賢良。
逼迫遷舊邦，擁主以自強。
海內興義師，欲共討不祥。
卓眾來東下，金甲耀日光。
平土人脆弱，來兵皆胡羌。
獵野圍城邑，所向悉破亡。
斬截無孑遺，屍骸相撐拒。
馬邊懸男頭，馬後載婦女。
長驅西入關，迥路險且阻。
還顧邈冥冥，肝脾為爛腐。
所略有萬計，不得令屯聚。
或有骨肉俱，欲言不敢語。
失意幾微間，輒言斃降虜。
要當以亭刃，我曹不活汝。
豈復惜性命，不堪其詈罵。
或便加棰杖，毒痛參並下。
旦則號泣行，夜則悲吟坐。
欲死不能得，欲生無一可。
彼蒼者何辜，乃遭此厄禍。
邊荒與華異，人俗少義理。
處所多霜雪，胡風春夏起。
翩翩吹我衣，肅肅入我耳。
感時念父母，哀嘆無窮已。
有客從外來，聞之常歡喜。
迎問其消息，輒復非鄉里。
邂逅徼時願，骨肉來迎己。
己得自解免，當復棄兒子。
天屬綴人心，念別無會期。
存亡永乖隔，不忍與之辭。
兒前抱我頸，問母欲何之。
人言母當去，豈復有還時。
阿母常仁惻，今何更不慈。
我尚未成人，奈何不顧思。
見此崩五內，恍惚生狂痴。
號泣手撫摩，當發復回疑。
兼有同時輩，相送告離別。
慕我獨得歸，哀叫聲摧裂。
馬為立踟躕，車為不轉轍。
觀者皆噓唏，行路亦嗚咽。
去去割情戀，遄征日遐邁。
悠悠三千里，何時復交會。
念我出腹子，匈臆為摧敗。
既至家人盡，又復無中外。
城廓為山林，庭宇生荊艾。
白骨不知誰，縱橫莫覆蓋。
出門無人聲，豺狼號且吠。
煢煢對孤景，怛吒糜肝肺。
登高遠眺望，魂神忽飛逝。
奄若壽命盡，旁人相寬大。
為復強視息，雖生何聊賴。
託命於新人，竭心自勖勵。
流離成鄙賤，常恐復捐廢。
人生幾何時，懷憂終年歲。
---&gt;

===Unit 5: Myths and Legends of East Asia===
&lt;!--- Shanhaijing, Zibuyu... Etc. Zhiguai literature. This aims to provide a counterpoint to what Confucius wouldn't discuss - thus Zibuyu. Going straight into Daoism isn't ideal. ---&gt;
# [[/Exploring the World of Mountains and Seas/]]&lt;!-- Structure: 出焉 --&gt;
# [[/Oh, the Qilin!/]] &lt;!--- Even here, the odes can be studied! ---&gt;
# [[/Ultimate Justice with Xiezhi/]] 
# [[/The Virtue of the Fenghuang/]] 
# [[/The Entrapment of Hua Po/]] 
# [[/Nüwa Created the World/]] 

===Unit 6: Nation Focus - Japan===
# [[/The Inariyama Sword/]] 
&lt;!--- short and sweet! ---&gt;
# [[/Entering Japan with Takeda Shingen/]]
&lt;!---
便面蘆間有漁·武田信玄
山色水光烟接天，漁翁江上棹蘆辺
丹青若写得勝景，万里風波一釣船

便面半月照梅花·武田信玄
蘆葦清風垂頂絲，窺魚白鷺水生涯
江南記得曾遊夕，似見梨花院落時

島森哲男. (2015). 武田信玄漢詩校釈. 宮城教育大学紀要, 49, 333–352. https://mue.repo.nii.ac.jp/records/440

似 is a really useful thing to teach early on. 
---&gt; 
# [[/The Oldest Inscription in Japan/]] 
&lt;!--- 宇治橋断碑 ---&gt; 
# [[/The End of a Rebellion/]] 
&lt;!--- https://www.fanyahanwen-corpus.cn/corpus_viewer/%E6%97%A5%E6%9C%AC%E6%BC%A2%E6%96%87/clean/%E6%97%A5%E6%9C%AC/%E6%B1%9F%E6%88%B8%E6%99%82%E4%BB%A3/%E8%9D%A6%E5%A4%B7%E5%85%B1%E5%92%8C%E5%9B%BD/%E5%9C%A8%E6%B5%B7%E7%89%99%E5%BA%9C ---&gt;
# [[/Shinto Teachings with Honda Chikaatsu/]] 
&lt;!--- https://wikisource.org/wiki/%E9%81%93%E4%B9%8B%E5%A4%A7%E5%8E%9F 本田親徳 道之大原 ---&gt;  
# [[/The Diary of Fujiwara no Teika/]] 
&lt;!--- 明月記 ---&gt;
# [[/Reading the History of Japan with Prince Toneri/]]
&lt;!--- 日本書記, etc. ---&gt; 
&lt;!--- # [[/Occupying Taiwan/]] ---&gt;
&lt;!--- I have some colonial literature on me that can be used here. ---&gt;

===Unit 7: Nation Focus - Korea===
&lt;!--- 三國史記 for sure! ---&gt;
&lt;!--- 放蟬賦 by Yi Kyubo ---&gt;
&lt;!--- https://zh.wikisource.org/wiki/%E9%A0%A4%E9%BD%8B%E9%81%BA%E7%A8%BF 頤齋遺稿 黃胤錫 Joseon scholar! ---&gt;
# [[/An Elegy to the Empress with Choe Ja/]]
&lt;!---
Choe Ja
元德大后輓詞·崔滋（최자）
乾極曾客配,坤儀正體元。
枕前朝聖主,帳底見曾孫。
陰慘俄沉月,屋悲便沒軒。
三韓千古淚,七十九年恩。
---&gt;
# [[/Language Reform with Sejong the Great/]]
&lt;!--- 訓民正音 https://github.com/ShiraTheMogul/fanyahanwen-corpus/commit/1ef2b42cc50055affaa5ef39c61b87ed31c34a60 multiple poems and descriptive terms, possibly the best capstone ---&gt;

===Unit 8: Christian Literature===
# [[/A Different Three Character Classic with Hong Xiuquan/]]
# [[/Friar Juan Cobo's Veritable Record/]] 
&lt;!--- 
One of few texts from the Philippines that I have ever found!
https://bnedigital.bne.es/bd/en/viewer?id=0160187c-9d9b-4f34-84d6-bc03fd310c69 
---&gt;
# [[/The Delegate's Edition/]]
# [[/Nestorian Steles during the Tang/]] 
&lt;!--- 大秦景教宣元至本經經幢 and 景教碑 ---&gt;
# [[/Hong Xiuquan's Bible/]]
&lt;!--- https://bible.fhl.net/ob/nob.html?book=407 ---&gt;
&lt;!--- I don't want to focus too much on Hong Xiuquan here, so look for more material, especially from missionaries. ---&gt;

===Unit 9: An Introduction to Daoism===
&lt;!--- And now back to your regularly scheduled Zhuangzi/Laozi/Liezi. But with more interesting stuff. Trust! ---&gt;
# [[/Laozi Explains the Dao/]]
&lt;!--- 道可道，非常道。名可名，非常名。無名天地之始；有名萬物之母。故常無欲，以觀其妙；常有欲，以觀其徼。此兩者，同出而異名，同謂之玄。玄之又玄，衆妙之門。I can expect learners to recognise the stuff here. ---&gt;
# [[/Qingtan with Xie Daoyun/]]
&lt;!--- 謝道韞; mentioned in the sanzijing. could be good!

《泰山吟·謝道韞》
峩峩東嶽高，秀極衝青天。
巖中間虛宇，寂寞幽以玄。
非工復非匠，雲構發自然。
器象爾何物，遂令我屢遷。
逝將宅斯宇，可以盡天年。

《拟嵇中散咏松诗·謝道韞》
遙望山上松，隆冬不能凋。
願想遊不憩，瞻彼萬仞條。
騰躍未能升，頓足俟王喬。
時哉不我與，大運所飄遙。

---&gt;
# [[/The Doubting Neighbour/]] 
# [[/Kuafu Chases the Sun/]] 
# [[/The Frog in a Well/]] 
# [[/Wu wei with King Hui of Liang/]]
# [[/The Old Man that Moves the Mountains/]]
# [[/Master Zhuang Dreams of Butterflies/]]
# [[/The Indifferent Taoist/]] &lt;!--- northern song https://zh.wikisource.org/wiki/%E7%8E%89%E6%AD%B7%E5%AF%B6%E9%88%94 ---&gt; 
&lt;!--- Currently very stereotypical, but there's stuff to work with at least. Need to include those weird Daoist characters among other things. ---&gt;

===Unit 10: Nation Focus - Ryukyu Kingdom===
# [[/Historical Annals with Sai On/]] &lt;!--- Kyuko is an easy cop ---&gt;
# [[/The Enthronement of Shō Tei/]] 
&lt;!---
康熙二十二年封王尚貞敕
皇帝敕諭琉球國中山王世子尚貞：惟爾遠處海隅，虔修職貢；屬在塚嗣，序應承祧。以朝命未膺，罔敢專擅；恪遵典制，奉表請封。朕念爾世守臣節，忠誠可嘉！特遣正使翰林院檢討汪楫、副使內閣中書舍人加一級林麟焻，齎敕封爾為琉球國中山王，並賜爾及妃文幣等物。爾祗承寵眷，懋紹先猷；輯和臣民，慎固封守：用安宗社於苞桑，永作天家之屏翰。欽哉，毋替朕命！故諭。

Teach imperial edicts. 
Consider seeing if there's a letter of acceptance from Shō Tei. 

Recorded in 琉球國志略 
https://ctext.org/wiki.pl?if=en&amp;chapter=966326
---&gt;
# [[/The Twilight of Ryukyu with Shō Ten/]] 
&lt;!---
神田酒樓街燈 尚典
酒樓今秋設芳筵，
一望街燈燦燦連。
烟氣引來通柱上，
光爭星月照神田。
---&gt;
# [[/A Trip to Ryukyu with Luo Sen/]] &lt;!--- Pre-Capstone ---&gt;
&lt;!---
遐邇貫珍 1854-11 - 日本日記 羅森 
https://archive.org/details/HEKC185411/page/n5/mode/1up
A solid description of Ryukyu cultural customs in Volume 11. Absolutely incredible. 
日三日火船直向東北而駛出了臺灣之外幾日不見天涯是時北風大作波浪沖天火船亦甚飄蕩而不能立見有沙鷗隨風而逐浪心直駛七日漸見小山而到琉球琉球一國長闊一百七十五里其國城在地球圖緯線赤道之北二十六度十四分經線中華北京偏東十一度二十四分自明以來世封王爵叨列藩籬其處土產不過蔬菜番薯菜油黑糖等類人民束髻大補是穿草履男女粧飾頭上祇插一簪二簪為別故少年之男女瞥目則無異及其壯也皆留鬚髯故街上長鬚之人甚多甲寅正月初一予上岸遊玩見街上兒童甚多分以銅錢各極歡喜人民亦甚謙恭民居間亦貼新春聯于門外但不見有別等繁華之事那霸有寺寺內有園是名家世宦之墳所以石刊刻姓名年號于碑上每日道人打掃供奉生花樹葉于墓前另有人家祖墳與中國之明塚無異峰巒之上樹木多植民房則以蠻石圍墻內以茅草結屋而居佳物椅棹俱無惟以草蓆屈膝而坐對火盆而吹煙民間亦有識中國言語字墨者
不張舖店惟有墟塲男不貿易婦女為之以貨易貨而外方之金銀弗尚焉然而百姓亦甚畏官長飲食亦甚粗粕甘守樸儉不務奢華亦鮮欺詐板門紙窓夜間亦不防竊曾見途中撿物亦能以返原人公門之內冷冷落落並無案牘之煩淳樸之風畧有同于上古之世我等外國之欲買什物須言于官官為代辦正月初六提督被理衛廉士等一班將官布列威嚴與予乘轎至王宮總理大臣尚宏勳為主席布政大夫馬良才為知客享宴甚豐食物多與中國無異宴後各官皆饋有紙扇烟包布帛等項是物雖粗此亦世子之恭敬外國故亞國亦以禮物而返贈之世子王宮離岸三里在于山頂是名守禮將至其宮一路亦有樹木石牌坊宮室亦甚寬大幽雅垣局可觀其處多栽鳳尾草森樹等類以障陰山邊田土樹藝五穀近海沙田水漲之後人收其沙以煎鹽此時明月當圓予覽山川亦足見一方之風景 
---&gt;
&lt;!--- 中山世鑑 and so on. Lots of poetry too. ---&gt;

===Unit 11: Nation Focus - Singapore===
&lt;!--- National Library of Singapore has a poetry series that's super good! ---&gt;

===Unit 12: Literary Chinese in Medicine===
&lt;!--- do not endorse the medical practices discussed in these...make sure to link back to the heavenly stems here as they are associated with specific body parts. ---&gt;
# [[/The Books of the Yellow Emperor/]] 
&lt;!-- 黃帝内徑 ---&gt;
# [[/Deviant Qi with Zhang Congzheng/]]
&lt;!--- https://zh.wikisource.org/wiki/%E5%84%92%E9%96%80%E4%BA%8B%E8%A6%AA ---&gt;
# [[/Anatomy with Sugita Genpaku/]]
&lt;!--- 解体新書 ---&gt;
# [[/A Lost Wu Medical Text analysed in Japan/]]
&lt;!--- 難經古義 ---&gt;

===Unit 13: People Focus - Zhuang peoples===
&lt;!--- https://mooc1.chaoxing.com/mooc-ans/ztnodedetailcontroller/visitnodedetail?courseId=84745403&amp;knowledgeId=84745463&amp;_from_=&amp;_fromV2_=&amp;rtag= 《峤西诗钞》 is also a really good shout. ---&gt;
&lt;!--- Basically, there are Zhuang and Tangut peoples who wrote in Literary Chinese, and their inclusion here is to show that even those who made their own scripts would use this tongue. 张鸿翮 imported the character 朴 to describe a bug, for example. ---&gt;
# [[/Zhuang poetry with Zhang Honghe/]]
&lt;!--- https://wenyi.gmw.cn/2024-06/25/content_37398911.htm

一是忠实记录了汉诗创作与古壮字交融的文化现象。清代壮族诗人张鸿翮（hé）《大塘谣》（《峤西诗钞》卷二）云：

去了休。去到大塘红蓼洲。红蓼生花，不结子。绿朴生花，毬见毬。

诗中所说“绿朴”，是壮族对柚子的惯称。“柚子”，壮语发音为“bug”。根据《古壮字字典》，其对应的古壮字为“朴（㭪）”。诗人将古壮字运用到汉文诗歌创作中，刻下了明清壮汉文化交相辉映的注脚。

This sort of thing is why Zhuang and Tangut inclusion is important, as they show how flexible Literary Chinese can be. ---&gt;

&lt;!---
Possible Jurchen/Khitan focus? 
耶律楚材 - Served 窝阔台, 玄風慶會錄 is short and respectable enough to work with.
---&gt;

===Unit 14: People Focus - Tangut peoples===
&lt;!--- 羅福萇 and 羅振玉 wrote studies on Western Xia / Tangut script. Look for poets and stuff. ---&gt; 

===Unit 15: Literary Chinese in the Military===
&lt;!--- Real Sun Zi hours! 7 Military Classics are an obvious shout, but look for more stuff too. ---&gt;
# [[/Fū! Rin! Ka! Zan!/]]
# [[/A Bilingual Stele of the Khitans/]]
&lt;!--- https://wikisource.org/wiki/%E5%A4%A7%E9%87%91%E7%9A%87%E5%BC%9F%E9%83%BD%E7%B5%B1%E7%B6%93%E7%95%A5%E9%83%8E%E5%90%9B%E8%A1%8C%E8%A8%98 ---&gt;
# [[/Going to war with Boyan/]]
&lt;!---
Boyan's Poem from the 元史
　　伯顏，蒙古巴林部人。至元十一年拜中書左丞相，總兵伐宋。官至開府儀同三司，薨贈太師，封淮安王，諡忠武。

　　《玉堂嘉話》：初，宋未下時，江南謠云：「江南若破，白雁來過。」當時莫喻其意。及宋亡，蓋知指丞相巴延也。

　　過梅嶺岡留題

馬首經從庾嶺回 【 庾嶺回　七修類稿（乾隆刊本）卷四十六作「嶺島歸」。】 ，王師到處悉平夷。擔頭不帶江南物，只插梅花一兩枝。

　　《七修類藳》：伯顏下江南，過金陵梅嶺岡詩云云。所以著名，亦有是善。
---&gt;
# [[/An Edict from the Xianbei/]]
&lt;!---
教義詔 楊廣
武有七德，先之以安民。政有六本，興之以教義。高麗高元，虧失藩禮，將欲問罪遼左，恢宣勝略。雖懷伐國，仍事省方。今往涿郡，巡撫民俗。其河北諸郡及山西、山東年九十已上者，版授太守；八十者，授縣令。
---&gt;
# [[/The Suppression of the Kingdom of Dongning/]]
&lt;!---
台灣鄭氏始末
https://ctext.org/wiki.pl?if=en&amp;chapter=139938

Largely a record of wars in Dongning rather than anything about the trade etc, so it fits here. 
---&gt;
# [[/The Shunzhi Emperor vs Li Zicheng/]]
&lt;!---
順治帝
告示
逆酋李自成已於通城斃命，各地鄉勇務隨我軍剿殺逆賊殘餘,凡有斬獲逆酋及擒獲逆酋交我軍者，一經驗證，按軍功論級給賞，必以示我朝皇恩浩蕩。
大清順治二年五月二十四日

恩詔
今月何日，為國曆改歲之履端,即為永昌書元之紀念？緬惟我朝民眾，三元肇慶，四始發祥。陳椒酒以飛觴，躋堂介壽；換桃符以獻歲，辟戶書新。翹望德容，河勝額手。今山河如舊，歲序更新;今天下同春，咸頒麗澤。願我朝君臣與萬民同樂，共沐化日光天，方不虛度韶華。
永昌二年新正初一

There's probably better choices here. Review. 
---&gt;
# [[/The Art of War/]]

===Unit 16: Nation Focus - Vietnam===
&lt;!--- https://github.com/ShiraTheMogul/fanyahanwen-corpus/commit/cfe6700e01f6fd59616a375d31aa8cd096677be1 this first ---&gt; 
# [[/Ancestor Veneration with the Descendants of Zhu Xi/]] 
&lt;!--- https://github.com/ShiraTheMogul/fanyahanwen-corpus/tree/main/corpus%2F%E8%B6%8A%E5%8D%97%E6%BC%A2%E6%96%87%2Fclean  somewhere in here ---&gt;
# [[/Spreading Revolutionary Consciousness with Phan Bội Châu and Liang Qichao/]] 
&lt;!--- 越南亡國史 Possibly the most important text in Vietnamese history, not even gonna lie. https://zh.wikisource.org/wiki/%E8%B6%8A%E5%8D%97%E4%BA%A1%E5%9C%8B%E5%8F%B2 ---&gt;
# [[/Academia in Literary Chinese between East and West/]] 
&lt;!--- 南風雜誌 is a massive shout here. Absolutely amazing series. ---&gt;

===Unit 17: Historical Annals and Encyclopediae===
&lt;!--- 永樂大典 will teach how to infer from gaps in texts! 《編類》 is an incredibly interesting essay from here that can bring up the odes and Confucius's「思無邪」quote. It can prepare students for the wrath of Qing academia later. ---&gt; 
# [[/An Introduction to Biographical Paintings/]]
&lt;!-- 
Many older paintings include biographies at the top in Literary Chinese. Students need to learn these.
https://commons.wikimedia.org/wiki/File:%E6%AD%B7%E4%BB%A3%E8%81%96%E8%B3%A2%E5%8D%8A%E8%BA%AB%E5%83%8F_%E5%86%8A_%E8%AB%B8%E8%91%9B%E4%BA%AE_(Zhuge_Liang).png - Famous figure, also part of a very notable series.
https://commons.wikimedia.org/wiki/File:Otomo-Sorin-2.jpg - Contains the Japanese repetition character 々
https://commons.wikimedia.org/wiki/File:Toyotomi_hideyoshi4.jpg - simply has aura
--&gt;
# [[/The History of Liao, Jin, and Song with Toqto'a/]] &lt;!--- 脱脱 ---&gt;
# [[/Two Years in the Forbidden City with Yu Deling/]] &lt;!--- 清宮禁二年記 https://zh.wikisource.org/wiki/%E6%B8%85%E5%AE%AE%E7%A6%81%E4%BA%8C%E5%B9%B4%E8%A8%98 ---&gt;
# [[/Selected Records of the History of the Da Shun/]]
&lt;!--- Fair Use of a 2010 book written in Literary Chinese about the Da Shun dynasty. Limit to 500 characters, if that. Use to encourage recognition of Simplified variants and modern Wenyanwen. ---&gt;
# [[/Documenting the World with Terajima/]]
&lt;!--- 和漢三才図会 寺島良安, built off 三才圖會 ---&gt;

===Unit 18: Buddhist Literature===
&lt;!--- You would be forgiven for wondering why this is so late, but if you look at many classical Buddhist texts you'll quickly see a ton of loanwords that make it significantly more difficult to read than the average text. Thus, it goes here for now. ---&gt;
&lt;!--- Place focus on practical stuff first. Stuff you can and WILL see in Buddhist temples. Stuff Buddhists can take away immediately. Skills-based approach feels strongest here. ---&gt;
&lt;!--- Look at Northern Liang and Later Qin literature, as there is a ton of work by translators from India during the 16 kingdoms period, particularly those two. ---&gt;
&lt;!--- Stuff by Bodhidharma 達摩 could be fun too https://zh.wikisource.org/wiki/Author:%E9%81%94%E6%91%A9 ---&gt;
# [[/Dipping your feet in with Wenyan Shu/]]
&lt;!---
華亭
世尊遺法本忘言，教外別傳意已圓。
只履攜將蔥嶺去，不妨來上月明船。
---&gt; 
# [[/The Seven Tathagatas/]] 
&lt;!---
南無寶勝如來
南無多寶如來
南無妙色身如來
南無廣博身如來
南無離怖畏如來
南無甘露王如來
南無阿彌陀佛

Use to introduce some core vocabulary in repetitive manner. 

Useful phrases from my trip to Jing'an Temple
南無本師釋迦牟尼佛 - Pay homage to the root teacher
南無大悲觀世音菩薩 - Pay homage to the goddess of mercy 
廣種福田 - widely plant a meritorious field 
---&gt;
# [[/Two Buddhist Temples in Shanghai/]] 
&lt;!---
留雲禪寺
雲留雲翔領畧幾許禪機此地有雲散天開真如界。
塔內塔外普示無邊圓覺是故曰塔影雙照解脫門。

歲次壬午冬月吉旦。
覺醒敬撰。
楊胡生沐手恭書。
善信印利明敬獻。 
---&gt;
&lt;!--- 福慧宝鼎 慧明大和尚 - introduce the Buddhist timekeeping system with 佛歷 around this point. 
赤烏古剎
建寺一千七百六十周年紀念

古剎三國建
滬瀆有重玄
石佛音淨現
聖跡顯重元
唐時稱永泰
宋敕名靜安
聖祖留佛闡
仲師移伽藍
元收八景偈
明鑄鐘聲梵
清樹化羅漢
選賢十方讚
佛日普光明
福慧共修善
鼎運昌隆際
轉正法輪緣

歲次丁亥住持慧明監製
---&gt;
# [[/Foreseeing Monkhood with Yi Xing/]]
&lt;!--- 看命一掌金 ---&gt;
# [[/A Trip to Western Xia with Zhi Guang and Hui Zhen/]]
&lt;!--- https://zh.wikisource.org/wiki/%E5%AF%86%E5%91%AA%E5%9C%93%E5%9B%A0%E5%BE%80%E7%94%9F%E9%9B%86 ---&gt;
&lt;!--- https://zh.wikisource.org/wiki/%E5%AF%86%E5%92%92%E5%9C%93%E5%9B%A0%E5%BE%80%E7%94%9F%E9%9B%86 ---&gt;
# [[/Jizang's Three Discourses/]]
&lt;!--- https://zh.wikisource.org/wiki/%E4%B8%89%E8%AB%96%E7%8E%84%E7%BE%A9 ---&gt;
&lt;!---
I saw these texts being quoted and thus should consider them in some capacity.
《般若波羅蜜多心經》
《金剛般若波羅蜜經》
《一切智光明仙人慈心因緣不食肉經》
《妙法蓮華經》
《大般涅槃經》
《大方等大集經》
《大毘盧舍那成佛神變加持經蓮華胎藏悲生曼荼羅廣大成就儀軌供養方便會》/ 胎藏曼荼羅 
《佛說救拔焰口餓鬼陀羅尼經》
《雜阿含經》

Look at Japan's 五山文学
---&gt;

===Unit 19: People Focus - Manchu peoples===
# [[/Qing dynasty Poetry with Nara Singde/]] 
&lt;!--- 飲水詞 納蘭性德 https://zh.wikisource.org/wiki/Author:%E7%B4%8D%E8%98%AD%E6%80%A7%E5%BE%B7 ---&gt;
# [[/Amassing Words with the Kangxi Emperor/]] 
&lt;!--- Kangxi Dictionary Abstract - https://zh.wikisource.org/wiki/%E5%BA%B7%E7%86%99%E5%AD%97%E5%85%B8 ---&gt;
# [[/Amassing Literature with the Qianlong Emperor/]] 
&lt;!--- Siku Quanshu abstract https://zh.wikisource.org/wiki/%E5%9B%9B%E5%BA%AB%E5%85%A8%E6%9B%B8%E7%B8%BD%E7%9B%AE%E6%8F%90%E8%A6%81 ---&gt;
&lt;!---
Yongzheng Emperor's Poetry 
https://zh.wikisource.org/wiki/Author:%E9%9B%8D%E6%AD%A3%E5%B8%9D
《和碩怡賢親王祭文》

Also include 滿洲國 stuff to show the fall of the Qing and attempts to preserve it through becoming a Japanese puppet state. It is important to show how Literary Chinese can be misused as well. 滿洲國建國宣言 is a good shout, as is 法制 to prepare students who may be interested in Taiwan legal stuff later down the road. 
https://zh.wikisource.org/wiki/Category:%E6%BB%BF%E6%B4%B2%E5%9C%8B
---&gt;
# [[/Paintings and Beauty with Puru Aisin-Gioro/]]
&lt;!--- Saw these in Shanghai Museum with some writing, seemed really cool. Teaches another skill. ---&gt;

===Unit 20: Qing-RoC Literature===
&lt;!--- many writers here, will be difficult to sift through. Include 四库全書 abstracts and stuff here. ---&gt;
# [[/Jewish Refugees in Shanghai/]] 
&lt;!--- Show passports, certificates, etc, from the Jewish Refugee Museum, anonymised. ---&gt;
# [[/A Literary Chinese Abstract/]] 
&lt;!--- Abstracts from siku quanshu, probably want others ---&gt;
# [[/Lament with Lu Ruoteng/]] 
&lt;!---
《疑猜》盧若騰，東寧國
盟誓變為交質子，春秋戰國風如此；末世上下相疑猜, 更質妻子防逃徙。
此法只可羈庸奴，若遇梟雄術窮矣；妻可再娶子再育, 安能長坐針氈裏。
我贈一法君記存；推心置腹人知恩；眾人畜之眾人報, 幾個國士在君門。
盧若騰撰，陳漢光編輯，《島噫詩》，臺灣文獻叢刊第二四五種（臺北:臺灣銀行經濟研究室，1968年）21頁。
---&gt;
# [[/Common Linguistics Knowledge in the RoC/]]
&lt;!--- 音韻常識 ---&gt;

==References used for this page==
* Yang, B. (2016). 文言语法 [Literary Chinese Grammar] (1st ed). 中华书局 [Zhonghua Book Company]. ISBN: 978-7-101-11619-9
* Priestley, K. E., &amp; Shou-jung, C. (1962). China’s Men of Letters, Yesterday and Today. Dragonfly Books.
{{BookCat}}</text>
      <sha1>e9xwvbemmpbbx8ecokbyfr34p343u56</sha1>
    </revision>
  </page>
  <page>
    <title>General Literary Chinese from Scratch/Introduction</title>
    <ns>0</ns>
    <id>481712</id>
    <revision>
      <id>4656086</id>
      <parentid>4631761</parentid>
      <timestamp>2026-08-02T18:20:59Z</timestamp>
      <contributor>
        <username>Shira the Mogul</username>
        <id>3560559</id>
      </contributor>
      <comment>small revisions</comment>
      <origin>4656086</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="9255" sha1="ta9funt8593pc4f3h7gos37k7i49x2w" xml:space="preserve">== About this Book ==
This book is not the same as [[Classical Chinese]], which is aimed at teaching the language spoken by Confucius and Zhuang Zhou during the peak of the classical period. This book teaches how that language was used by individuals across multiple countries. It makes no assumptions about your knowledge: You can be a person like me - a westerner who simply loves the language - or anyone else. I will also not assume you have linguistic knowledge; I will avoid using it where I can, but direct you to the linguistic term if you wish to use it. This book respects your intelligence.

The book is organised into ''Units'' as if this were a course, using principles taken from [[wikipedia:Teaching English as a Foreign Language|Teaching English as a Foreign Language]]. We will go through several stages of comprehension; from simply understanding the Han script as an entity, to general-purpose comprehension. Skimming, scanning, and extensive reading skills will be trained. You will not be completely fluent in reading this language solely from this text, but it will serve as a guiding hand. I will provide texts for you to optionally read alongside this book from Wikisource.

The reason this book is being made is that the standard Literary Chinese curriculum is extremely impoverished. Most materials focus heavily on Zhou-Qin texts and, due to the small corpus, get railroaded into forcing students to learn lengthy, difficult passages right from the get-go. Numerous textbooks, both English and Chinese, are like this. It does not have to be this way and these faulty curricula usually come from either a lack of materials management, a need to adhere to a broader philosophy curriculum, or both. This book hopes to rectify this wrong by drawing upon the entire Sinosphere for resources instead, whilst still preserving the classics and the good parts of the methodology used in contemporary textbooks. In doing so, the book hopes to give you a broader historical understanding of the Literary Chinese tradition and how it was adopted into these different cultures, which is essential for the context this language requires to be readily understood. 

Drawing upon contemporary TEFL considerations for literature, I introduce a &quot;buffet&quot; approach with the gathered materials: In other words, I raise many &quot;mini-units&quot; that draw upon literature from broad themes. These aim to showcase culture and genre, two major &quot;nodes&quot; of Literary Chinese discourse. Difficulty will increase according to theme, but they will all follow a similar path of shorter excerpts first, to lengthy texts at the end. The broader syllabus is centralised around scaffolded vocabulary: Each text will naturally lead into the next, and you will be expected to remember vocabulary from each unit. This does come with some changes to how Literary Chinese is taught, though: For example, Zhuangzi is often taught early due to his unbelievable influence on Sinitic thought. However, his texts are incredibly dense and use poetry, which naturally requires the concepts of argumentation and poetry being showcased first. This scaffolded approach hopes to make it so that Zhuangzi and other philosophers can be read comfortably through pacing the learning curve, allowing him and similar major figures to be understood with full appreciation. 

We will be using [[wikipedia:Traditional Chinese|Traditional Chinese]] in this book. However, there are regional variants within this, and content from the [[wikipedia:People's Republic of China|People's Republic of China]] may insist on [[wikipedia:Simplified Chinese|Simplified Chinese]], which was a reform in the 1940s that standardised common handwritten variants. This book has no horse in the race of which standardised system is best: Use what you want, and what is best, for your writing. 

Therefore, lessons will be structured like so:

* Lead-In: Small nuggets of knowledge that will set the context.
* Pre-Reading: An explanation of patterns and characters that will be important for reading. 
* Text: What we are hoping to read
* Gloss: Glosses to relevant vocabulary. 
* Explanation: An explanation of the characters and patterns within.
* Exercises: Questions to answer for yourself. 
* Similar texts

For example...&lt;blockquote&gt;一武曰木

 One thing (is) called a tree

 (explanation...)&lt;/blockquote&gt;And glorious etcetera!

It should be noted that a translation will never be outright given to you. The expectation is that you come out of these lessons with the ability to interpret a text for yourself. There are translation tools online, and these are acceptable, but the opportunity for that first interpretation must exist for your personal development.

== On Phonology ==
Literary Chinese itself has no phonology. Therefore, rather than prescribe you a new phonology to learn, '''I will be giving you the [[wikipedia:Cangjie input method|Cangjie Input Method]] combinations, which targets the structure of the characters instead.''' 

However, this is not to say the language was not spoken: It was, and is, recited, especially in poetry. Therefore, should you be interested in recitals and the like (and they ''are'' wonderful!), I strongly recommend you use a tool to view the phoneticization for what we can call your '''reading language'''. I personally recommend Yomitan for this, which allows you to press Shift to view it instantly. 

This text will present poetry in the modern phonology of the country a text is from. If it is Japanese poetry, it will be in Sino-Japanese. If it is in Chinese, it will be in Mandarin Chinese and 
Cantonese.&lt;!--- Mandarin is accessible to the majority of Chinese individuals whilst Cantonese is popular, accessible, and preserves a lot of tone and final distinctions. I can't just dig my head in the sand and ignore either, so let's use both. ---&gt; So on, so forth. 

== What is Literary Chinese? ==
Literary Chinese is the &quot;scripta franca&quot; used across East Asia until around the 20th Century. It is still sporadically used today in traditional Chinese and Japanese poetry, Taiwanese law, and classically-inclined literature, but enjoyed broad usage prior to 1917, when the [[wikipedia:New Culture Movement|New Culture Movement]] led by [[wikipedia:Hu Shi|Hu Shi]] 胡適 finally put an end to it. The [[wikipedia:CJK characters|CJKVZ]] family of characters shows that the Han script was used in a wide variety of environments. It is not just China and Japan! It has been used in Korea, Vietnam, the [[wikipedia:Ryukyu Kingdom|Ryukyu Kingdom]], Singapore, and even Malaysia! By accessing this language, you can read historical literature from any of these countries. It is not simply a pan-Asian language, though: It is also diachronic, having vocabulary loaned and forgotten over the years. It is something of a moving target: Texts written in 5th Century Japan will be very similar to those written in 10th Century Vietnam, though each nation may write a given character differently, but the underlying syntax will be identical.

Literary Chinese is filled with boundless genres, such as...

* Confucianism
* Daoism
* Buddhism
* Poetry
* Law
* Politics 
* Government
* Philosophy
* Traditional Chinese Medicine (TCM)
* History
* Military affairs
* Tea culture
* Ethics and morals
* Education theory
* Travel logs
* Christianity
* Lexicography (creation of dictionaries)
* Encyclopaediae
* Art history
* Literary criticism &amp; commentary
* Academia

And so, so, so much more! It is the language used by the literati of yesteryear for thousands of years. The tradition is a leviathan that is hard to fully grasp and appreciate even as one grows in experience. One could say you grow with this language.

I will make something clear: Literary Chinese is by no means a strict Han institution. It is a massively diverse language that has been used by people of many ethnicities, and these people will all be given voices in this book. Each of these people had different cultures, values, and motivations for using this language. Jurchens and their Manchu successors used the language to claim Han lineage; Tangut peoples used it to differentiate themselves from Han Chinese; Japanese people used it to supplement their at-the-time unwritten tongue. These motivations all present unique challenges: Noticing these occurrences is essential. However, it is not sunshine and rainbows: Manchuria used Literary Chinese for law and edicts to assist in Japanese colonisation of northern China, and the Mongols used it when committing genocide against the Western Xia. It is a language of power, and some would use it to speak to that power: Consort Dasese used the language against the Khitan Emperor Taizuo of Liao when his complacence led to his downfall. This textbook hopes to synthesise and marry these concepts, to show Literary Chinese as it actually functioned.

By the end of this book, I will ensure you can read anything from a deeply personal account of a Daimyo's life when Japan was in its infancy, all the way to World War I as it happened in the eyes of someone from Vietnam. You will be able to get trapped in this sprawling labyrinth and slowly improve at whatever specialisation you're looking for.

Sound awesome? Then let's dive in!

{{BookCat}}</text>
      <sha1>ta9funt8593pc4f3h7gos37k7i49x2w</sha1>
    </revision>
  </page>
  <page>
    <title>Taking Bearings: Artificial Intelligence in Knowledge Platforms and Open, Social Scholarship/Introduction</title>
    <ns>0</ns>
    <id>483449</id>
    <revision>
      <id>4656123</id>
      <parentid>4655854</parentid>
      <timestamp>2026-08-02T21:50:06Z</timestamp>
      <contributor>
        <username>CorreiaA</username>
        <id>3614427</id>
      </contributor>
      <minor />
      <comment>/* Audiences and Differential Impacts */</comment>
      <origin>4656123</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="77391" sha1="5aa16amg7px2w8797spzg7wkixbjbwy" xml:space="preserve">This research scan surveys an emergent and contested terrain: the interlaced developments in artificial intelligence, generative AI, large language models (LLMs) and their predecessors, and the ways these systems are reshaping knowledge production, circulation, and engagement across scholarly and public contexts.

This scan uses artificial intelligence, or AI, as a broad umbrella term for computational systems designed to perform tasks associated with classification, prediction, reasoning, language processing, recommendation, perception, automation, or decision support. It uses generative AI, or genAI, more specifically for systems that generate text, images, code, audio, video, or other outputs in response to prompts, queries, or other inputs. Large language models, or LLMs, are a prominent subset of contemporary genAI systems trained to model and generate language. Because public disclosure often uses these terms interchangeably, this scan uses AI for the broader field and infrastructure, genAI where generative functions are specifically at issue, and LLM where the discussion concerns language-model systems in particular. The wider AI landscape includes technical architectures ranging from symbolic logic and &quot;good old-fashioned AI&quot; (GOFAI), through statistical natural language processing, to contemporary transformer-based genAI models, all situated within institutional and platform economies, cloud infrastructures, and evolving governance regimes (Jones 2023; Anderson 2024). These systems now recalibrate discretion, authority, and visiblity, influencing what is recognized as knowledge, who produces it, and how it moves among diverse publics. 

A brief historical distinction is useful here. AI has not developed through a single technical or ideological pathway. Symbolic approaches, prominent in early AI, treated intelligence as the manipulation of explicit rules, formal representation, and logical structures. Connectionist approaches, by contrast, emphasized distributed pattern recognition across networks of weighted relations. Contemporary deep learning and transformer-based genAI inherit much more from the connectionist tradition, especially its reliance on large datasets, statistical association, and learned representations rather than explicit rules. This inheritance helps explain why contemporary systems can be powerful aids for pattern detection, generation, and transformation, while remaining weak at grounding, verification, and accountable judgment. &quot;Hallucinations&quot;—false responses generated by AI that are especially misleading due to their plausible surfaces—stem from the inherent mathematical design of such systems, which are optimized to generate probable outputs rather than to verify claims within accountable epistemic communities. For fuller historical and critical accounts of these developments, see Jones (2023), Ali et al. (2023), Anderson (2024), and Whiteley (2023).

What emerges from this mapping is a complex phenomenology of entanglement. Generative AI is woven in part from scholarship's own materials—open access literature, research data, metadata schemas, citation networks, community-developed software, and collaborative data infrastructures. These are not the only, or even necessarily the largest, sources on which contemporary systems are trained. But they are unusually authoritative in that they help organize what counts as reliable knowledge, how claims are linked to evidence, how materials are discovered, and how intellectual legitimacy is conferred. The AI systems that now analyze, summarize, and generate scholarly text therefore draw upon knowledge infrastructures whose value has been built over decades by researchers, editors, librarians, publishers, software communities, institutions, and publics.

This recursive relationship positions scholarship as both one of AI's important knowledge substrates and one of its objects of transformation, but the entanglement runs deeper still. Scholarship does not merely feed AI systems; it is increasingly mediated by them. Researchers discover literature through AI-powered recommendation engines, draft manuscripts with generative assistants, and navigate peer review processes augmented by algorithmic triage. Students encounter AI both as subject of study and as tool for learning, while institutions struggle to develop governance frameworks adequate to technologies that evolve faster than policy cycles. The recursive loop—scholarship training AI training scholarship—creates conditions where distinguishing human from machine contribution becomes progressively more difficult, and where the very categories through which we understand authorship, originality, and expertise require renegotiation.

The organizing logic of this collection moves from foundational grounding through INKE-aligned focal points that structure the annotated bibliography itself. It first establishes essential contexts: the histories and theories of AI, including critical perspectives from Science and Technology Studies (STS) and Critical Digital Humanities; accounts of knowledge as relational, plural, and platformed; and the principles of Open Social Scholarship (OSS) as articulated by the Implementing New Knowledge Environments (INKE) Partnership and the Electronic Textual Cultures Lab (ETCL). It then follows three focal threads—&quot;open&quot;, &quot;social&quot;, and &quot;scholarship&quot;—that mark key sites where AI's effects both align with and challenge OSS commitments to accessibility, reciprocity, participatory governance, and public engagement (Arbuckle et al. 2022; El Khatib et al. 2019).

Throughout, the ethos of Open Social Scholarship provides a normative coordinate: a set of principles for interpreting how AI mediates relations among researchers, institutions, communities, and publics. The focus is on how practices, infrastructures, and relations are changing, and how these shifts intersect with OSS values. Which concepts, practices, actors, infrastructures, and frictions are currently reconfiguring the conditions of knowledge and engagement? Where do these movements align with, complicate, or unsettle OSS principles of accessibility, reciprocity, and public value? By attending closely to these dynamics—openness entangled with enclosure, provenance linked to trust, bias in tension with diversity, governance negotiated through participation—a conceptual scaffolding emerges for further analysis and empirical inquiry.

A critical OSS response to AI need not only be defensive. The same systems that threaten enclosure, decontextualization, and epistemic flattening may, under different governance conditions, support broader forms of scholarly engagement: multilingual and plain-language summaries, alternative format outputs, assistive reading and navigation, metadata enrichment, participatory annotation, community translation, and more accessible pathways into specialized research. These possibilities in no way cancel the risks identified throughout this scan. Rather, they clarify the architectural task lying ahead of open, social scholarship: to ask what forms of AI-mediated scholarship can be built under conditions of reciprocity, transparency, care, public value, and shared authority.

== Four Cross-Cutting Tensions ==

The sources assembled here reveal four cross-cutting tensions that structure AI's engagement with scholarship. None admits of simple resolution—each marks a site where choices about AI design and deployment carry real stakes for knowledge production, and where different communities are actively negotiating trade-offs that no technical fix can settle.

'''Operational assistance versus epistemic authority'''. While AI can reduce friction in many workflows, it raises fundamental questions about where judgment, accountability, and interpretive responsibility should reside, and how those boundaries should be renegotiated as tools, practices, and disciplinary norms change. AI excels at standardized tasks—formatting, initial drafts, pattern identification, literature triage—while struggling with the evaluative judgment that gives scholarship its value. The challenge lies in leveraging assistance without ceding authority, using AI capabilities while preserving human responsibility for consequential decisions. When does operational support cross into epistemic territory? How should that boundary be renegotiated as capabilities shift, practices stabilize, and disciplinary communities develop new norms? 

This boundary is historically and institutionally variable. Reference verification, metadata enrichment, formatting, and duplication checks may increasingly be treated as operational tasks. Literature triage, evidence synthesis, translation, and review assistance venture into more contested terrain. Assessments of originality, significance, methodological adequacy, interpretive force, and public consequence continue to require accountable human judgment. The problem of governance is therefore not one of simply drawing a fixed, indelible line once, but to define processes through which scholarly communities can revisit that line over time.

The fluency of AI-generated text can mask the absence of understanding; the appearance of authority can obscure the statistical operations underneath. Sun (2025) emphasizes that models, by definition, are constrained in how they evaluate the novelty of research—they can recognize patterns but cannot evaluate whether patterns matter. This distinction is integral to peer review, research methods, pedagogy, and governance, and each requires clarity about where AI can appropriately assist and where human judgment must remain central.

'''Openness versus enclosure'''. The open infrastructure that has supported equitable access to knowledge is being absorbed into commercial AI systems in ways that may foreclose openness rather than extend it, and the trajectory of this tension will shape whether AI serves broad publics or narrow interests. Open access literature feeds model pretraining; this raises serious concerns about a new enclosure dynamic, in which freely accessible works become inputs for proprietary AI systems that generate commercial value without meaningful reciprocity. Pooley (2024) reveals a troubling symmetry in the underlying asymmetry: both commercial publishers and AI developers extract value from the scholarly commons while returning little to the researchers who create it. The licensing frameworks developed for human readers require substantial adaptation to govern machine consumption, where attribution and context preservation present fundamentally different challenges. Community-sourced data and labour underwrite AI functions, yet the question of whether benefits return to those communities remains contested.

'''Technical capability versus organizational capacity'''. The pace of AI development consistently outstrips the ability of institutions to evaluate, govern, and respond thoughtfully, and the gap between what AI can technically accomplish and what institutions can responsibly deploy constitutes a critical site of intervention.  Building capacity for thoughtful AI adoption requires sustained investment in skills, governance structures, and evaluative frameworks. Weber et al. (2023) identify organizational capabilities as crucial mediators, noting failures often stem from organizational incapacity to manage sociotechnical complexity. Resource-intensive approaches assume capacities—technical staff, governance infrastructure, training budgets, and time for implementation—that are unevenly distributed across institutions and communities. These differences do not map neatly onto institutional size or prestige: large research universities may have more formal infrastructure, but also larger user bases, more complex bureaucracies, and interventions that can become less responsive to local needs. Smaller institutions such as community colleges, public libraries, independent scholarly organizations, and grassroots knowledge projects may face different constraints, including limited staffing, funding, or access to specialized expertise. Across all contexts, institutions are encountering unforeseen complexities for which existing governance structures may be poorly prepared. This tension requires attention to differential institutional positions and the development of governance models that remain humane, adaptable, and scalable across varied contexts. 

'''Efficiency versus process'''. Although AI accelerates tasks, scholarly knowledge earns its credibility through deliberate, iterative processes of review and community validation that efficiency-oriented tools may erode. Pedagogical and scholarly transformations require valuing cognitive work that AI cannot replicate, and education involves developing capacities through practice, not just acquiring outputs. The speed and fluency of AI-generated text can mask the erasure of the deliberative processes—reading, synthesizing, drafting, revising—through which understanding develops. Deng et al. (2025) find that ChatGPT improves student performance while reducing mental effort, raising questions about what learning means when cognitive work is offloaded to machines. The compression of research, writing, and discovery processes may generate outputs while eroding the developmental experiences that scholarly communities value. Process-centred assessment, transparent documentation, and attention to the formative dimensions of intellectual work become crucial responses.

These tensions recur throughout the bibliography's domains. They structure debates about AI in peer review, pedagogy, platform governance, and infrastructure design. Understanding them as ongoing negotiations rather than problems awaiting solution helps position responsible engagement with AI's transformative effects.

== Fundamentals and Ideologies of AI ==
The prominence of generative AI and LLMs is rooted in layered histories. Early symbolic AI attempted to encode knowledge as explicit rules and representations. Statistical natural language processing redirected attention to learning patterns from data. Deep learning, accelerated by transformer architectures and large-scale computation, now underpins models that generate fluent text, code, and images (Jones 2023). Each wave is embedded in institutional settings, funding regimes, and sociotechnical imaginaries that combine benchmark cultures, optimization logics, data abundance, and investor narratives of efficiency and disruption. The concept of &quot;sociotechnical imaginaries&quot; provides crucial analytical purchase for understanding how collective visions shape governance and discourse; as Mao, Richter, and Katzenbach (2025) demonstrate, these imaginaries function performatively, actively mobilizing resources, legitimating interventions, and establishing trajectories for development. The figure of &quot;intelligence&quot; functions here as a sociotechnical imaginary: a collective vision that orients research agendas, policy priorities, and public expectations, often sidelining questions of transparency, accountability, and epistemic pluralism.

Understanding contemporary AI requires genealogical attention to its intellectual origins and the sociotechnical imaginaries that have shaped its development. The transition from symbolic AI to statistical learning—from explicit knowledge representation to pattern recognition across massive datasets—represents a fundamental reorientation of assumptions about what counts as intelligence and whose knowledge gets represented. As Jones (2023) argues, the shift toward &quot;empiricist&quot; approaches that capitalize on the &quot;unreasonable effectiveness of data&quot; threatens professions centred on particularity while demonstrating that AI functions as a reflection of human creations including their best and worst traits.

Anderson's (2024) examination of John McCarthy's foundational program reveals AI as philosophical ideology—a vision of perfectly rational abstraction built upon objectivism and scientism that has &quot;come to serve as a blind for increasing techno-corporate control of society.&quot; McCarthy's conception of artificial intelligence as a &quot;stripped down model of human mental engagement without emotional qualities&quot; established patterns that continue to shape the field: the subordination of interpretive judgment to formal optimization, the bracketing of contextual understanding in favor of scalable pattern matching, and the assumption that intelligence admits of decomposition into modular, transferable components. Ali et al. (2023) extend this analysis by situating AI within broader genealogies of industrialization and colonialism, identifying threads of hidden labour, encoded behaviour, and cognitive injustice running through AI's history—positioning AI as the flagship of the Information Age conditioned by the Management Age.

The term &quot;artificial intelligence&quot; itself warrants critical scrutiny. As Whiteley (2023) observes, the phrase anthropomorphizes what is essentially computer-assisted statistical analysis, encouraging expectations and trust that the technology cannot warrant. This terminological slippage—from statistical prediction to &quot;intelligence&quot;—exemplifies how language shapes perception and, through perception, governance. The sources in this bibliography provide conceptual resources for more precise description that preserves space for human agency, critical evaluation, and alternative design pathways.

Critical perspectives from Digital Humanities (DH) and Science, Technology and Society (STS) supply key interpretive tools. They foreground the ways datasets, labels, and evaluation metrics encode values and worldviews; how training regimes replicate archival absences and classification politics; and how the defaults embedded in language, genre, and culture travel into outputs, with particular consequences for marginalized communities. Bender et al. (2021) critically analyze how larger models reproduce hegemonic views: size does not guarantee diversity, because the communities most underrepresented in training data are also those most likely to bear the downstream costs of systems built without them. Automation theory highlights AI as a redistribution of discretion and authority: tasks that once required situated human judgment are delegated to systems that lack context, while accountability structures struggle to keep pace.

Berry (2025) theorizes this moment as &quot;the Inversion&quot; under &quot;computational capitalism&quot; where machine-generated works reshape meaning-making infrastructure, producing &quot;AI slop&quot; that infiltrates information ecosystems with garbled meaning. His concept of &quot;diffusionisation&quot; describes how AI systems dissolve cultural forms into probabilistic vector spaces and reconstitute them through latent space manipulation—a process that transforms the infrastructure of meaning-making itself. This moves beyond mechanical reproduction toward what Berry theorizes as &quot;post-consciousness,&quot; where boundaries between individual and synthetic consciousness become porous. The concept challenges scholars to attend not merely to AI outputs but to how generative systems transform the very grounds upon which experience and meaning are constituted.

Environmental and labour analyses add further layers, tracing the energy-intensive training runs and precarious annotation and moderation work that underpin current capabilities. Klein et al. (2025) argue that AI's statistical enactment of ideology imposes an objectivist European modernist framework upon data, making issues of &quot;bias&quot; unsolvable through technical means alone—even the distinction between &quot;pure&quot; and &quot;toxic&quot; training data reflects ideological commitments. They propose that smaller, purpose-built models developed through genuine interdisciplinary collaboration offer a path forward, one where &quot;technical researchers must recognize the institutional asymmetries&quot; that currently disadvantage humanistic approaches.

Relations with OSS-aligned communities complicate this picture. Open-source software, open datasets, and commons-based peer production have been central to AI's development; influential models rely on openly shared corpora and community-built tools. At the present inflection point, however, pressures toward enclosure are intensifying. Recent work by the Open Source Initiative on open source AI, including its 1.0 Open Source AI Definition, clarifies that releasing model weights alone is not equivalent to full openness. Meaningful openness also depends on access to documentation, code, data information, use rights, and other artifacts needed to understand, modify, and reuse a system. This clarification responds to broader concerns about “openwashing,” in which companies describe AI systems as open while releasing models under restrictive licenses, with incomplete documentation, or without access to key development artifacts. White et al. (2024) similarly develop the Model Openness Framework, establishing a three-tiered classification that shows AI “openness” exists on a spectrum, from minimal weight release to fuller disclosure of training data, intermediate checkpoints, code, documentation, and development practices. Rather than a simple binary between open and closed, the field is experimenting with hybrid forms—open weights under usage constraints, community checkpoints, and permissive yet bounded licenses—that seek to reconcile accessibility with risk management and intellectual property considerations. 

Vake et al. (2025) find the open-source AI community depends on businesses to develop base models—there are few incentives for companies to release openly because doing so risks intellectual property and competitive advantage. This structural dependence raises questions about whether open AI can genuinely serve public interests or will remain subordinated to commercial imperatives. These choices shape not only technical access, but also epistemic legitimacy and the capacity for public oversight, critique, and repair.

== Geographic Diversity in AI Imaginaries ==

The imaginaries circulating around AI vary significantly across geographic and political-economic contexts, challenging narratives of technological inevitability that treat AI development as following a single universal trajectory. Mao, Richter, and Katzenbach's (2025) comparative analysis across the United States, China, and Germany reveals heterogeneous and often contradictory imaginaries even within single regulatory regimes. Where US discourse fragments across multiple geographic AI hubs, German imaginaries centre on EU policy compliance and regulatory frameworks, while Chinese articulations align tightly with party-state directives that minimize local variation.

Building on the varied sociotechnical imaginaries discussed earlier, Chung (2025) extends this analysis to economically advanced but geographically non-dominant Asian societies—Singapore, Hong Kong, and Taiwan—demonstrating how &quot;techno-developmentalism&quot; produces distinct imaginaries shaped by local political-economic conditions and historical trajectories. These varied articulations challenge the Global North/South binary that structures much AI governance literature, revealing that AI development trajectories remain contingent and shaped by specific political choices rather than following universal technological imperatives.

The imaginaries circulating around AI shape technical design itself. Van Es and Nguyen (2024) demonstrate how ChatGPT's self-representations—82% depicting humanoid forms—strategically cultivate anthropomorphic imaginaries that encourage overlooking ethical and legal challenges. The friendly assistant persona, surrounded by books and radiating futuristic light, constructs a humanoid image of trustworthy intellectual companionship that obscures the statistical operations underneath.

For scholarly communities, these developments necessitate specifically humanities-oriented engagement. Chun and Elkins (2023) argue that humanities-oriented pedagogy offers distinctive resources for this moment, insisting that the most effective AI tools amplify rather than replace human intellectual engagement—a claim developed more fully in the Critical Literacies section below.

== Knowledge Foundations ==

In this framework, knowledge appears as a relational practice rooted in communities, languages, and infrastructures. Three dimensions are especially salient for understanding AI's impact: diversity, mobilization, and platforms.

'''Diversity'''. Epistemic, cultural, linguistic, and methodological plurality are conditions for robust, public-facing scholarship. Models trained predominantly on dominant corpora risk misrecognition and erasure, flattening the diversity that constitutes human knowledge. Arbuckle (2020) articulates diversity as fundamental to legitimate knowledge translation, emphasizing inclusive modes of engagement and participatory approaches that honour varied ways of knowing. In response, approaches such as community governance of data, participatory evaluation, and multilingual modelling work to adapt tools to difference rather than requiring difference to conform to tools. Crompton et al. (2020) address how community governance can safeguard plural representation in data infrastructures like Wikidata, demonstrating that technical systems encode choices about whose knowledge counts and how it gets categorized. The FAIR principles—Findable, Accessible, Interoperable, Reusable—offer a technical framework for data stewardship, while the CARE principles—Collective Benefit, Authority to Control, Responsibility, Ethics—introduce dimensions of sovereignty, consent, and community benefit that are especially important for Indigenous data and other contexts shaped by power asymmetries (Carroll et al. 2020; Carroll et al. 2021).

'''Mobilization'''. Knowledge mobilization concerns how research travels and is taken up across domains: from scholarship to policy, from specialist discourses to public understanding, from the classroom to community settings. Generative tools can accelerate synthesis and enhance accessibility by producing multilingual summaries, plain-language translations, and alternative-format outputs. The same tools can also increase the volume and velocity of decontextualized or misleading claims. Winter (2023) frames policy as a vehicle for mobilization emphasizing provenance and accountability—mechanisms that become ever more crucial when automated systems mediate between research and its publics. Jensen (2023) connects commons-based infrastructures to mobilization pathways, highlighting how interoperability and community practices shape whether knowledge flows toward public benefit or private capture. A central challenge is ensuring that speed does not erode fidelity, and that reach does not come at the expense of context or community consent.

The Canadian HSS Commons exemplifies mobilization infrastructure designed around principles of reciprocity and community responsiveness. Winter et al. (2020) describe how this platform instantiates governance mechanisms, provenance tracking, and dialogic engagement in a Canadian context, offering a concrete model for how digital research communities might align with OSS values. The Commons demonstrates that alternatives to extractive platform models are possible when design priorities centre community benefit and participatory governance.

'''Infrastructure and Platforms'''. Repositories, journals, preprint servers, and social scholarly tools form the infrastructural backbone of scholarly communication due to their ubiquity, reliability, and invisibility (Plantin et al. 2018). AI-mediated functions such as search, recommendation, summarization, moderation, and peer review reshape relations of production, discoverability, and legitimacy. Turning research outputs into training data for AI technologies creates a process of platformization of digital research infrastructure, in which the research process is commodified and turned into data for publishers and corporations to exploit while excluding the research community from the governance of these infrastructures. Bullard (2023) reveals how metadata shapes these dynamics, demonstrating that descriptive schemas determine what gets found, how it gets categorized, and whose work becomes visible. Goddard (2021) positions persistent identifiers as crucial connective tissue for provenance and interoperability, enabling the traceability that accountability requires. Whether platforms act as commons or proprietary funnels depends on decisions about interoperability, open standards, licensing, and governance. Colbert-Lewis et al. (2024) examine the citation economy as a site of extraction for surveillance publishing, documenting how publishers have transitioned to technology-driven data brokers that monetize researcher behaviour alongside research outputs. Seemingly technical or back-end decisions structure how knowledge circulates and who benefits from that circulation.

== Open Social Scholarship Principles ==

Open Social Scholarship, as developed by INKE and ETCL, characterizes scholarship as a public, collaborative practice sustained by open, participatory, and ethically governed infrastructures (Arbuckle et al. 2022; El Khatib et al. 2019). Within this frame, AI is evaluated not solely on technical metrics but on whether it strengthens dialogic exchange, lowers barriers without reproducing harm, and supports reciprocal engagement rather than unilateral extraction. Openness is coupled with care; accessibility with accountability; participation with shared authority. Arbuckle and Maxwell (2019) move beyond open access by emphasizing infrastructure choices and governance as sites where values are enacted—recognizing that technical decisions embed normative commitments about who can participate, on what terms, and toward what ends. Maxwell (2015) argues that &quot;access&quot; alone proves insufficient; usability and community-responsive workflows reposition openness as an ecosystem with embedded care and accountability.

This also gives OSS a constructive role in relation to AI. Rather than approaching AI only as an external threat to be resisted, OSS can help specify what accountable alternatives would require: community-shaped tools, transparent provenance, accessible interfaces, multilingual and multimodal engagement, benefit-sharing where public or community knowledge is used, and governance arrangements that keep interpretive authority distributed rather than concentrated in proprietary systems.

Several principles translate into analytical vantage points for observing AI's effects:

'''Openness with care''' balances access with consent and community control, recognizing that uncontrolled circulation can facilitate extraction when reciprocity is absent (Carroll et al. 2020). Some knowledge requires protection; openness can become extractive when divorced from attention to power asymmetries and community interests.

'''Participation with shared authority''' embeds publics and communities in the design, evaluation, and governance of AI tools, rather than positioning them as passive recipients. Engagement becomes genuine partnership, not consultation that leaves final decisions to technical experts.

'''Accessibility''' is treated as multidimensional, spanning language, different ableness, technical literacy, and the digital divides that structure who can engage with AI-mediated scholarship. True accessibility requires attention to the multiple barriers—linguistic, economic, infrastructural—that shape unequal participation.

'''Reciprocity and benefit-sharing''' acquire particular weight where community-sourced data, scholarship, cultural material or labour underwrite AI functions; the question of whether benefits return to those communities becomes central. In heterogeneous training-data environments, reciprocity cannot always mean simple one-to-one compensation or attribution. It may also require collective mechanisms: investment in public infrastructure, support for community-governed datasets, licensing arrangements, provenance standards, access rights, audit mechanisms, and benefit-sharing models that recognize the distributed labour through which knowledge systems are built.

'''Infrastructural responsibility''' assigns institutions ongoing obligations to steward provenance, auditability, and accountability across the AI lifecycle—from adoption through monitoring, incident response, and iterative refinement. 

These principles serve as lenses that help clarify where choices around AI align with OSS values and where they introduce new tensions. They support a descriptive, attuned stance that remains open to emerging research, changing practices, and the contested meanings that animate debates over AI's place in scholarship.

== AI and &quot;Open&quot; ==

Openness operates across several registers—access, data, source, science, and social scholarship—and AI interacts differently with each. The recursive relationship between AI and openness demands particular attention: open access literature, open data, open source software, open standards, and community-maintained infrastructures have all contributed to the conditions under which contemporary AI systems became possible. Yet these resources now circulate within systems that often tend toward enclosure, secrecy, and commercial capture. The result is not a simple opposition between open and closed, but a contested field in which openness can serve public knowledge, enable scrutiny, and support community adaptation, while also becoming a reservoir from which private systems extract value without adequate attribution, consent, or reciprocity. 

=== Open Access ===

Open access literature forms one important input into model pretraining, retrieval-augmented generation, summarization, and later synthesis, while a dark shadow has fallen over how works licensed for broad human access are being repurposed for machine processing, private capture, and commercial value extraction. Pooley (2024) critically examines how commercial publishers frame AI companies as &quot;free-riders&quot; while themselves profiting from unpaid scholarly labour, extending &quot;surveillance publishing&quot; into AI domains. His analysis reveals a troubling symmetry: both commercial publishers and AI developers extract value from the scholarly commons while returning little to the researchers who create it. Kember and Brand (2023) document how OA policies may unintentionally contribute to greater consolidation enabling &quot;corporate capture&quot;—a warning that good intentions around openness can produce perverse outcomes when power asymmetries remain unaddressed.

Licensing frameworks and machine-access provisions influence whether open access functions as a commons or a reservoir for extraction. Luth (2025) examines how stakeholders navigate AI training on Creative Commons content, finding compliance often uncertain and highlighting strategies for protecting shared knowledge while sustaining open ecosystems. Smith (2025) analyzes how existing licenses perform in machine learning contexts, noting most were drafted without anticipating large-scale AI training and proposing machine-readable licensing provisions that could clarify terms and enable technical enforcement. These analyses suggest that the licensing frameworks developed for human readers require substantial adaptation to govern machine consumption, where attribution and context preservation present fundamentally different challenges.

AI thus makes open licensing a live infrastructural question rather than a settled legal background condition. Licensors, libraries, funders, publishers, repositories, and scholarly communities will need to clarify how open licenses apply to machine reading, text and data mining, model training, retrieval-augmented generation, and downstream synthetic outputs. The important question here is whether the use of open materials preserves attribution, context, reciprocity, and the public purposes for which openness was advanced.

The dual role of open access—as both input to AI development and public good in its own right—underscores the importance of provenance-aware summarization, appropriate attribution, and consent mechanisms that reflect authors' and communities' intentions. When AI models synthesize open access literature, questions of attribution become vexed: whose work is represented in a probabilistic blend? How can communities maintain oversight of how their contributions are used?

=== Open Data ===

Open data, crucial for reproducibility and model improvement, raises issues of privacy, consent, and community sovereignty, especially in relation to sensitive or Indigenous data. The CARE principles complement FAIR by centring collective benefit, authority to control, responsibility, and ethics (Carroll et al. 2020). Carroll et al. (2020) ground these principles in the structural biases and colonization processes producing &quot;epistemicide,&quot; directly addressing tensions between Indigenous Data Sovereignty and AI's voracious data demands. Their framework demonstrates that open data governance constitutes a political practice, where broad data sharing and algorithmic extraction can undermine the rights, consent, and collective interests of communities whose knowledge becomes training material.

Carroll et al. (2021) demonstrate FAIR and CARE operationalized together. Because many scientific datasets contain Indigenous Knowledge, applying CARE principles ensures this data is oriented toward community wellbeing through rigorous provenance tracking and appropriate governance models. Arrangements such as data trusts, tiered access, and purpose-bound licenses illustrate how openness can be conditioned: open to whom, for which purposes, under what accountability terms?

Documentation practices emerge as crucial infrastructure for responsible AI development. Bender and Friedman (2018) propose data statements as critical in enabling infrastructure to reduce exclusion and bias in language technologies, arguing that such documentation can prevent misrepresentation and support more ethical system development. Boyd (2021) empirically demonstrates that documentation frameworks increase engineers' ethical sensitivity—through think-aloud sessions, practitioners who received Datasheets identified ethical issues earlier and more frequently. This finding challenges assumptions that openness automatically leads to fairer systems; structured documentation actively shapes how practitioners recognize and respond to potential harms.

=== Open Source ===

Open source dynamics in AI include open weights, permissive licenses, and community checkpoints that support verification, plural innovation, and public-interest development. At the same time, discussions of misuse and dual-use emphasize capability control and risk. White et al. (2024) establish a Model Openness Framework with three-tiered classification, codifying 17 components that expose the requirements for reproducibility and scrutiny. Graduated openness—incremental model releases, safety mitigations, and governance charters—appears as one path toward balancing transparency with harm reduction. The evolution of open models will influence the accessibility of AI to under-resourced institutions, public-interest researchers, and communities seeking to adapt technologies to local contexts.

The Open Source Initiative's Open Source AI Definition 1.0, released in 2024, provides criteria for describing an AI system as &quot;Open Source AI,&quot; including the freedoms to use, study, modify, and share, access to the preferred form for modification, and sufficient information about training data provenance. As a definition rather than a license or implementation practice, it offers a community standard for assessing whether licenses, releases, and documentation practices support genuine openness, including whether &quot;open weights&quot; claims are matched by the artifacts, permissions, and transparency needed to avoid openwashing.

=== Open Science ===

Open science principles encourage reproducible workflows—transparent notebooks, containers, pipelines, and documentation—while AI introduces dependencies that can be opaque and difficult to reproduce. Practices such as open benchmarking, model cards, data cards, and documentation standards aim to make training data, evaluation metrics, and known limitations more visible. The push and pull between speed and scrutiny is pronounced in AI-assisted research: rapid exploration can generate insights, yet robust claims require validation, transparency, and often slower processes.

The tension between efficiency and process manifests acutely in open science contexts. AI can accelerate literature review, code generation, and data analysis, but the compression of these processes may obscure the iterative work through which understanding develops. Open science's emphasis on showing work—through preregistration, open notebooks, and transparent reporting—provides resources for maintaining visibility even as AI augments research workflows.

=== Open Social Scholarship ===

Within open social scholarship, AI is approached as a means to enhance public dialogue and shared inquiry. Examples include co-authorship with non-academic collaborators, explicit attribution of AI assistance, and participatory governance of tools in community-engaged projects (Arbuckle et al. 2022). Alignment with OSS principles is assessed by whether AI-supported practices sustain reciprocity, accessibility, and shared authority in knowledge production, and whether technological mediation amplifies rather than displaces human voice, agency, and accountability.

The feedback relationship—scholarship as training data, AI as scholarly tool—manifests throughout these registers. Open access literature trains models that then summarize open access literature. Peer review norms shape training data that then assists peer review. Pedagogical materials become training data for tools used in teaching. This recursion creates feedback loops whose effects on scholarly practice remain to be fully understood.

== AI and &quot;Social&quot; ==

The &quot;social&quot; dimension concerns the distribution of attention, credibility, and participation within and beyond academia. AI now helps mediate content creation, curation, and moderation, altering these distributions in ways that merit close scrutiny.

=== Platforms and Synthetic Content ===

Platforms hosting synthetic content must contend with provenance and identity. As generated text, images, and deepfake media proliferate, distinguishing among forms of authorship becomes more complex, with direct implications for trust and credibility. Van Es and Nguyen (2024) show that these anthropomorphic imaginaries are not incidental: they are actively constructed through ChatGPT's own self-representations, which consistently project a friendly, humanoid intellectual companion that obscures the statistical operations underneath. Mitra, Cramer, and Gurevich (2024) diagnose &quot;information access&quot; under generative AI as &quot;sociotechnical settlement&quot;—models &quot;intermediate credibility, reshape attention, and re-allocate epistemic authority.&quot; Their framing positions AI-mediated search and synthesis as fundamentally reconfiguring who gets heard, whose claims become visible, and whose expertise counts.

Recommendation systems juggle personalization, diversity, and serendipity, shaping canon formation and the visibility of marginalized voices. Attention economies are being reshaped: some work is surfaced and amplified; other work is obscured, sometimes by design and sometimes as a side effect of algorithmic optimization. Content credentials—cryptographic signatures and rich metadata—attempt to record origin and transformation history, while questions persist about whether such mechanisms can scale to match the velocity of synthetic content production. For scholarly communication, such mechanisms should be treated as part of the infrastructure of citation, preservation, disclosure, and accountability; their value depends on whether they can travel across repositories, journals, platforms, and public interfaces without being stripped of context.

=== Governance, Moderation, and Policy ===

Leadership, governance, moderation, and policy become iterative and layered rather than singular and top-down. Universities, libraries, journals, and repositories intersect with platform governance in setting norms for AI-assisted authorship, disclosure, review, and engagement. Sartori and Theodorou (2022) view AI as a &quot;magnifying glass&quot; amplifying existing inequities—a framing that clarifies bias as an older problem than the technology and locates responsibility in social structures and institutional choices. Their analysis challenges approaches that treat fairness as achievable through algorithmic adjustment alone, arguing that human control requires institutional mechanisms for contestation that acknowledge AI practice as fundamentally political.

Akter et al. (2021) theorize algorithmic bias as emerging from interacting sources—data bias, method bias, and societal bias—demonstrated through Australia's Robo-Debt scheme, which inherited and amplified existing inequities through automated decision-making. Their framework implicitly contests technological determinism by revealing how managerial choices about data collection priorities, acceptable error rates, and stakeholder consultation shape algorithmic outcomes in ways that exceed engineering decisions.

Jensen et al. (2022) address governance and moderation as platform design commitments aligned with OSS values, showing how choices about community safety and trust shape the kinds of scholarship platforms can support. Transparency reports, appeal procedures, and community-based moderation seek to address harms while preserving legitimate expression. Policy becomes experimental, subject to revision as impacts, unintended consequences, and community norms evolve.

=== Critical Literacies ===

Critical literacies, for both scholars and publics, extend beyond operational proficiency. They involve understanding model limits, recognizing sources of bias, interpreting provenance signals, and practising verification. Chun and Elkins (2023) position AI's advancement as precipitating interlocking crises demanding pedagogical response grounded in reflective and collaborative meaning-making, explicitly connecting pedagogical design to civic preparation and positioning students as &quot;critically engaged citizens capable of interrogating the social and economic implications of algorithmic mediation.&quot; Zeffiro (2024) reveals how corporate narratives of AI as &quot;democratizing force&quot; obscure differential vulnerabilities while &quot;automating insecurities&quot;—a concept capturing how AI tools institutionalize particular understandings of risk that reflect corporate priorities rather than community needs.

These literacies include skills such as documenting AI use, distinguishing synthesis from source, reading expressions of uncertainty, and maintaining awareness of the gap between fluency and accuracy. The ease with which AI produces confident-sounding text makes discrimination skills more important: fluency does not indicate accuracy, and the appearance of authority can mask the absence of understanding.

=== Global Asymmetries and Epistemic Centralization ===

AI’s geopolitical dimensions draw attention to questions of influence, globalism, and colonization. Training regimes often reproduce global asymmetries in language and corpus composition: English-language and Global North sources dominate, while linguistic and epistemic diversity from other regions receive less representation. Bender et al. (2021) critically analyze how larger models reproduce hegemonic views, noting that the damages associated with large-scale language models—environmental costs, representational harms, concentration of power—are more likely to fall on marginalized populations.

Chung (2025) extends geographic scope to Asia's advanced economies, revealing how techno-developmentalism produces distinct imaginaries shaped by local political-economic conditions. Multilingual models, community-owned datasets, and South–South collaborations seek to counteract epistemic centralization, yet the structural dynamics of extraction without reciprocity remain strong. Arthur et al. (2021) reveal how national policy shapes whether openness reduces or reproduces inequities, showing that structural barriers—funding models, institutional incentives, infrastructure gaps—mediate between stated commitments to openness and their realization in practice.

Debates over determinism, diversity, and justice challenge narratives of technological inevitability. Sartori and Theodorou (2022) extend this analysis to the global scale, emphasizing that adoption choices, design priorities, and evaluation metrics remain matters of collective agency—and that the communities most affected by AI's asymmetries are precisely those least represented in the governance structures that shape them. Justice-oriented evaluation foregrounds the distribution of harms and benefits, rather than focusing solely on aggregate performance: who is helped, who is harmed, and along which axes of power and marginalization?

=== Humanity, Community, Connection, and the Affective Dimensions of AI Mediation ===

Beyond the technical and governance dimensions, AI mediation carries affective and relational aspects that shape scholarly communication in subtle but significant ways. Generative systems influence the tone and velocity of discourse and can intensify polarization or foster connection depending on design choices and deployment contexts. The ability to flood channels with synthetic text or avatars strains existing trust infrastructures, creating new challenges for maintaining the relational fabric of scholarly communities.

Design choices that emphasize care—thoughtful moderation, friction for high-risk actions, community control of spaces—become part of scholarly platform ethics. These choices counter acceleration and decontextualization that undermine deliberation and mutual recognition. The question moves beyond whether AI produces accurate outputs, to whether AI-mediated environments support the kinds of dialogue, disagreement, and collaborative inquiry that scholarship requires. Connection and community constitute values that technical efficiency can erode if left unattended.

Jensen et al. (2022) explore how digital communities of care can be fostered through attention to safety, security, and trust—values that require ongoing cultivation rather than one-time technical implementation. The relational dimensions of scholarship—mentorship, collaboration, peer recognition, collegial support—may be affected by AI mediation in ways that exceed questions of accuracy or efficiency.

=== Environmental and Labour Costs ===

Material costs, both labour and environmental, ground AI capability in ways that often remain invisible. The AI pipeline depends on precarious annotation and moderation labour, often transnational and underpaid. Workers in the Global South perform essential tasks—labelling training data, flagging harmful content, refining model outputs—under conditions that rarely feature in celebratory narratives of AI advancement. This hidden labour connects AI development to broader patterns of extraction and externalization, where the costs of technological systems are displaced onto vulnerable populations.

Energy and water consumption for training and deployment contribute to climate impacts that intersect with environmental justice concerns. Bender et al. (2021) observe that the damages associated with large-scale language models—environmental costs, representational harms, concentration of power—&quot;are more likely to fall on marginalized populations.&quot; The communities least likely to benefit from AI capabilities bear disproportionate burdens from their development.

Disclosure norms, ethical procurement, and commitments to &quot;green AI&quot; bring these dimensions into infrastructural planning rather than treating them as externalities. For institutions committed to sustainability and justice, AI adoption cannot be evaluated solely on functional criteria; the material conditions of AI production become relevant to responsible deployment decisions. This connects AI governance to broader institutional commitments around environmental responsibility and labour ethics.

== AI and &quot;Scholarship&quot; ==

Across the scholarly lifecycle, AI now participates in research, writing, teaching, review, and administration, changing how practice and infrastructure co-evolve. The tension between operational assistance and epistemic authority manifests at each stage.

=== Research Methods and Practice ===

Research methods and practices incorporate LLMs for literature review, coding, data cleaning, translation, and analysis. Key questions concern how assistance is documented, how outputs are validated, and how communities renegotiate the line between exploratory use, operational support, interpretive contribution, and settled scholarly claim. Mehlenbacher, Balbon, and Mehlenbacher (2024) examine &quot;synthetic genres&quot; that push apart definitions of &quot;information&quot; and &quot;knowledge,&quot; suggesting that AI-generated text occupies a novel categorical space requiring new frameworks for evaluation. Bozkurt (2024) addresses authorship implications, proposing the aiTARAS Framework while maintaining that responsibility ultimately belongs to the human author. Maintaining epistemic standards while exploring new efficiencies requires treating AI as a tool supporting thought and analysis, not as a substitute for disciplinary judgment.

Domain-specific norms—interpretive rigour in the humanities, reproducibility in quantitative fields—must shape appropriate use. The question of when AI assistance becomes AI authorship remains contested, with implications for credit, accountability, and the integrity of scholarly claims. Documenting AI use transparently allows readers to assess the epistemic status of outputs and evaluate whether human judgment remains central to the knowledge claims of a given piece.

=== Scholarly Outputs ===

Forms of scholarly output are changing as generative tools support multimodal and interactive work: dynamic narratives, layered visualizations, and synthesis artifacts that draw together diverse sources. Bergstrom and Ruediger (2024) anticipate &quot;discovery, interpretation, and writing services&quot; becoming integrated suites while noting concerns about platform intermediation that could concentrate power over scholarly communication. Authorship, attribution, and preservation practices need to adapt: whose contributions are recognized, how AI assistance is disclosed, and how AI-mediated outputs are archived and made citable. Provenance and disclosure become part of the paratext, informing evaluations of reliability and situating works within ongoing conversations.

=== Teaching and Pedagogy ===

Teaching and pedagogy integrate AI as both subject and instrument. Tan and Maravilla (2024) position AI as a &quot;catalyst necessitating pedagogical transformation—shifting from transmission models toward environments where students actively construct knowledge.&quot; This reframing treats AI as an occasion for rethinking educational purposes and methods, emphasizing the human capacities—critical judgment, ethical reflection, creative synthesis—that AI systems cannot replicate.

Deng et al. (2025) meta-analyze 69 studies finding ChatGPT improves performance while reducing mental effort, raising questions about what learning means when cognitive work is offloaded to machines. Their findings suggest that traditional assessment measures require recalibration to capture the thinking processes that educational institutions value. The tension between efficiency and process manifests acutely here: if AI can produce essays, what is being assessed? Process-centred assessment emphasizes transparency, ethical reflection, and the development of critical literacies that enable students to assess model outputs, recognize limitations, and engage thoughtfully with AI-mediated knowledge.

Lee and Palmer (2025) establish prompt engineering as an emergent practice mirroring &quot;Socratic dialogue,&quot; suggesting continuities between AI interaction and established pedagogical traditions. Oates and Johnson (2025) demonstrate pedagogical value in making AI outputs &quot;subjects for evaluation rather than endpoints of learning&quot;—an approach that uses AI as material for critical analysis. Berry (2023) warns that uncritical AI reliance risks &quot;algorithmization&quot; of Digital Humanities, where computational methods become defaults that shape questions before they are asked.

=== Service and Peer Review ===

Service and peer review use AI for triage, formatting checks, and detection tasks—identifying duplication, verifying references, smoothing language—while preserving human judgment for evaluations of originality, significance, and methodological rigour. Sun (2025) maps LLM applications in peer review, emphasizing that models &quot;remain fundamentally limited in assessing research novelty.&quot; Hosseini and Horbach (2023) document potential to combat reviewer fatigue while identifying risks when &quot;operational assistance crosses into epistemic territory,&quot; suggesting that the boundary between support and substitution requires careful negotiation. Checco et al. (2021) demonstrate AI can predict outcomes based on &quot;superficial&quot; features while emphasizing &quot;semi-automated&quot; approaches that preserve human judgment for consequential decisions.

The line between operational assistance and epistemic authority runs directly through peer review, but it is better understood as a moving boundary than a fixed division. Tasks such as formatting checks, duplication detection, reference verification, and metadata checks may sit relatively comfortably on the operational side. Literature triage, reviewer matching, summary generation, and consistency checking occupy more contested middle ground. Assessments of novelty, significance, methodological rigour, interpretive adequacy, and contribution to a field require the kind of accountable judgment that remains distinctively human. Clarity about this boundary helps preserve the integrity of peer review while leveraging AI's capacity for routine tasks.

The inverse problem is integrity infrastructure. AI may assist legitimate review workflows, but it can also amplify older forms of scholarly fraud: paper mills, fabricated peer reviews, synthetic citations, citation cartels, manipulated images, and low-quality or fabricated manuscripts designed to pass superficial screening. These problems predate contemporary genAI, but generative systems increase their scale, speed, and plausible fluency. Responsible AI governance in publishing therefore requires attention not only to how reviewers may use AI, but also to how editorial systems detect, document, and respond to AI-amplified threats to the scholarly record. 

=== Research-Related Infrastructures ===

Research-related infrastructures span organizational governance, publishing and communication platforms, workflow systems, and accountability mechanisms. Governance frameworks, risk registers, roles, and capacity-building programs institutionalize stewardship, coordinating policy and practice across libraries, IT, research support, and ethics offices. Wu, Zhang, and Carroll (2024) document Big Ten universities' &quot;multi-unit governance involving information technology, teaching centres, libraries, and research offices&quot;—a distributed model recognizing AI as a cross-sectoral concern requiring coordinated response.

AI also places new pressure on open scholarly infrastructure. Repositories, commons platforms, digital research infrastructures, standards bodies, and open-science advising organizations must decide whether and how to integrate AI-mediated search, metadata generation, summarization, moderation, preservation, and analytics. These decisions affect governance, sustainability, procurement, interoperability, environmental cost, labour, and the degree to which open infrastructures remain accountable to scholarly and public communities rather than becoming dependent on proprietary AI services.

Open infrastructure responses should therefore be assessed against principles such as transparency, community governance, interoperability, portability, auditability, and long-term stewardship. In this context, standards for open infrastructure become AI governance instruments: they shape whether AI functions can be inspected, contested, replaced, or collectively maintained. 

Papagiannidis, Mikalef, and Conboy (2025) differentiate governance practices, revealing tensions &quot;between centralized oversight and distributed expertise.&quot; Institutions must navigate between the efficiency of centralized decision-making and the contextual knowledge held by distributed practitioners who understand how AI affects their specific domains.

Rughiniș et al. (2025) introduce &quot;dual black-boxing&quot; capturing compound accountability challenges when opaque AI systems meet opaque institutional processes. When neither the AI nor the institution is transparent about its decision-making, accountability becomes doubly difficult. Janssen (2025) reframes AI governance as managing &quot;complex adaptive systems characterized by co-evolution and emergent properties,&quot; suggesting that governance frameworks must themselves be adaptive. Weber et al. (2023)—whose findings on organizational capacity are discussed in the cross-cutting tensions above—appear here as a reminder that infrastructure governance is where those abstract tensions become concrete institutional failures.

Publishing and communication infrastructures increasingly integrate AI functions—journal recommendation, reviewer matching, manuscript screening, metadata generation—as part of scholarly workflow systems. Kousha and Thelwall (2024) map AI tool deployment across the publishing pipeline, distinguishing demonstrated capabilities from promotional claims. Their analysis reveals that substantial efficiency improvements are achievable in labour-intensive administrative tasks, while human judgment remains integral to core intellectual evaluations. This distinction—between what AI can assist with operationally and what requires human epistemic judgment—structures responsible integration of AI into publishing infrastructures. Ultimately, however, the success of these infrastructural choices is measured not just by operational efficiency, but by how effectively they mediate knowledge for the diverse publics who rely on them.

== Audiences and Differential Impacts ==

Audiences—scholars, students, practitioners, policy-makers, and broader publics—encounter AI-mediated summaries, translations, and recommendations that shape how they access and interpret scholarship. Each audience brings different needs, literacies, and vulnerabilities to these encounters, and AI effects manifest differently across these diverse contexts.

Personalization raises the risk of filter bubbles, where recommendation systems surface content that confirms existing interests and perspectives while obscuring alternatives. Taneja and Tripathi (2020) identify structural tensions inherent in personalization algorithms that enhance user experience while simultaneously constructing echo chambers that systematically exclude novel, dissenting, or interdisciplinary perspectives. For scholarly communication, filter bubbles could reinforce disciplinary silos and impede the cross-fertilization that drives innovation. Audience-aware communication emphasizes context, uncertainty, and reciprocity, recognizing that different audiences need different framings and levels of technical detail.

The accessibility principles outlined earlier apply with particular force here: different audiences face different obstacles. AI can broaden participation and lower barriers—through translation, summarization, and alternative formats—but only when its design and governance prioritize inclusion, fidelity, and the preservation of diverse voices and perspectives. Da Silva Cardoso and Rocio (2025) propose frameworks for integrating AI into academic digital libraries that position librarians as essential partners in system development, emphasizing that understanding the nuanced and context-dependent needs of diverse academic communities requires human expertise that cannot be automated. The question is whether AI mediation grows or shrinks the publics that can engage with scholarship.

The sources reveal how AI effects vary by context in ways that demand attention to differential impacts:

'''Institutional type'''. AI adoption is shaped by uneven institutional capacities, but these differences do not map neatly onto size or prestige. Large research universities may have more formal infrastructure, while also facing larger user bases, more complex bureaucracies, and less responsive or less humane interventions. Smaller institutions, community colleges, public libraries, independent scholarly organizations, and grassroots knowledge projects may face different constraints, including limited staffing, funding, or access to specialized expertise. Equitable AI adoption therefore requires governance models that can adapt across institutional contexts without assuming uniform access to technical capacity, administrative infrastructure, or training resources.

'''Language communities'''. What serves English-language scholarship may disadvantage multilingual communities. Models trained predominantly on English reproduce Anglophone perspectives; multilingual support often lags behind. For scholars working in languages underrepresented in training corpora, AI tools may be less accurate, less helpful, or actively distorting. Linguistic diversity constitutes both an epistemic and an ethical concern: knowledge produced in non-dominant languages risks marginalization when AI systems favour majority languages.

'''Career stage'''. That which benefits established researchers may burden early-career scholars differently. Senior researchers with established reputations may more easily navigate AI-mediated environments, using AI assistance to amplify existing authority. Early-career scholars face additional pressures around attribution, originality, and demonstrating independent capability. When AI can generate fluent prose, summarize literatures, and accelerate administrative or writing tasks, how do junior scholars demonstrate the intellectual development that hiring, promotion, and grant committees have traditionally valued? Assessment criteria developed for human-only production may require adaptation to remain meaningful in AI-augmented contexts, but such adaptation must avoid intensifying surveillance or creating new burdens of disclosure that fall unevenly on those with the least institutional power. 

AI in the evaluation of researchers deserves separate attention from AI in the peer review of scholarly outputs. Hiring, promotion, tenure, grants, fellowships, and institutional metrics shape careers, disciplines, and access to scholarly futures. If AI-mediated tools are used to screen CVs, rank candidates, summarize dossiers, evaluate productivity, or assess “fit,” their consequences may be especially significant for early-career scholars, contingent faculty, disabled scholars, scholars working in less dominant languages, interdisciplinary researchers, and those whose contributions are not well captured by standard metrics. Governance in this area should require transparency, contestability, human accountability, and careful attention to disparate impact. 

'''Disciplinary context'''. Different disciplines bring different norms, methods, and evaluation criteria to AI engagement. What constitutes appropriate AI assistance in a literature review differs from appropriate assistance in data analysis or creative work. Disciplinary communities are developing varied approaches, and cross-disciplinary dialogue helps surface assumptions and identify best practices that might transfer across contexts.

'''Geographic location'''. Scholars in different regions face different infrastructural realities, regulatory frameworks, and access conditions. AI tools developed primarily for well-resourced contexts may not serve scholars working with limited bandwidth, different privacy regimes, or constrained institutional support. Geographic diversity in AI impacts connects to broader patterns of global inequality in knowledge production and circulation.

Attention to these differential impacts marks responsible AI adoption, requiring ongoing assessment of who benefits, who bears burdens, and how distributions might be made more equitable. Rather than assuming uniform effects, responsible governance monitors for disparate impacts and adjusts policies and tools in response to evidence of inequitable outcomes.

== Phenomena, Relations, and Ongoing Inquiry ==

The sources in this annotated bibliography have been selected to trace several intersecting concerns. Conceptually, works that articulate critical frameworks (STS, data colonialism) offer key tools for understanding AI as a sociotechnical formation (Anderson 2024; Ali et al. 2023; Bender et al. 2021). Normatively, scholarship on public engagement, participatory infrastructures, reciprocity, and accessibility ground the discussion in the normative coordinates of open social scholarship (Arbuckle et al. 2022; El Khatib et al. 2019). Infrastructurally, sources on data governance (FAIR and CARE), licensing, repositories, and platforms illuminate how AI is being integrated into the material and organizational substrates of knowledge work (Carroll et al. 2020; White et al. 2024). Methodologically, contributions from anthropology, STS, media studies, information science, and environmental humanities help maintain epistemic plurality and attend to global and intersectional dimensions (Chung 2025; Richter, Katzenbach, and Schäfer 2025). Finally, empirically, studies of peer review, literature searching, pedagogical applications, and governance supply concrete evidence of AI's effects in practice (Sun 2025; Deng et al. 2025; Wu, Zhang, and Carroll 2024).

== Conceptual Mapping ==

The conceptual mapping that orients this bibliography treats concepts, phenomena, and relations as interconnected. This mapping is meant to help readers locate where a given source sits: what it names, what it observes, and what it connects:

'''Concepts''' such as openness, provenance, bias, governance, data sovereignty, participation, reproducibility, labour, sustainability, platformization, multilingualism, accessibility, evaluation, enclosure, commons, personalization, and exposure diversity mark key terms of analysis.

'''Phenomena''' such as pretraining on public corpora, proliferation of synthetic content, recommendation feedback loops, metadata drift, hallucination, hybrid openness models, human-in-the-loop verification, green AI practices, community moderation, content credentials, and retrieval-augmented generation describe observable patterns in the field.

'''Relations''' trace interactions among these elements: openness and enclosure meet through licensing and reciprocity mechanisms; provenance and trust are linked through audit trails and disclosure practices; bias and diversity intersect in dataset governance and evaluation design; governance and participation connect through co-design and community oversight; platformization shapes visibility through algorithmic curation and efforts to foster exposure diversity; labour and sustainability meet in discussions of ethical procurement and environmental accounting; reproducibility pushes against black-boxing through documentation and open benchmarking; multilingualism and accessibility intertwine in translation and community review; evaluation anchors legitimacy by attending to social impact and equity metrics.

== Focused Areas for Further Intervention ==

Several areas emerge from this scan as candidates for shorter, more pragmatic follow-up work. AI-mediated scholarly discovery is already reshaping canon formation, citation patterns and visibility through search engines, recommender systems, citation-context services, discovery platforms, and automated synthesis tools. Provenance infrastructure, including content credentials, persistent identifiers, verifiable metadata, and workflow documentation, could strengthen disclosure by making AI involvement more portable, auditable, and machine-readable. Smaller, community-built, purpose-specific models offer a constructive path for aligning AI with OSS values where communities can define scope, data governance, evaluation criteria, and benefit-sharing arrangements. 

Integrity infrastructure also requires urgent attention, since paper mills, fabricated reviews, synthetic citations, and AI-amplified fraud threaten the trust systems upon which scholarship depends. AI in the evaluation of researchers—hiring, promotion, grants, fellowships, and institutional metrics—deserves treatment distinct from peer review of outputs because its consequence for early-career scholars, equity, and disciplinary futures may be especially profound. Parallel interventions on AI and open licensing, and on AI’s effects on open scholarly infrastructure, would clarify how licensors, libraries, funders, digital research infrastructures, advising bodies, and standards communities are adapting to machine use of open knowledge.

=== Conditions for Flourishing ===

The question animating this bibliography remains phenomenological: what conditions enable scholarship to flourish? The sources suggest these conditions include:

* '''Diverse participation''' that brings varied perspectives to bear on complex problems
* '''Critical literacy''' that equips scholars and publics to evaluate AI-mediated claims
* '''Transparent processes''' that make choices visible and contestable
* '''Human accountability''' that maintains responsibility for consequential decisions
* '''Infrastructural stewardship''' that ensures technical systems serve public purposes

OSS principles provide the normative coordinates for navigating the cross-cutting tensions this scan has identified,offering a framework to ensure that operational assistance does not usurp epistemic authority, that openness resists extractive enclosure, that technical deployments match organizational capacity, and that efficiency does not erase the deliberative processes of scholarship. Specifically, openness with care balances access with consent and community control. Participation with shared authority embeds publics and communities in design and evaluation. Accessibility spans language, disability, and technical literacy. Reciprocity ensures that where community-sourced data or labour underwrite AI functions, benefits flow back to contributors. Infrastructural responsibility commits institutions to steward provenance, auditability, and accountability across deployment lifecycles.

This mapping does not aim to close debate or fix categories. It sketches a topology of the current field: which nodes are active, where tensions gather, and how shifts in one domain reverberate through others. The annotated bibliography is offered as a baseline &quot;lay of the land&quot; against which ongoing research can be situated, helping scholars and practitioners locate their work within a broader conceptual ecology and identify gaps, alignments, and opportunities for intervention shaped by OSS principles of accessibility, reciprocity, and public value.

These conditions also point toward a positive agenda. AI-mediated scholarship could support forms of access and engagement that have long mattered to OSS: translation across languages and registers, navigation of complex archives, discovery across disciplinary boundaries, support of disabled readers and writers, richer metadata, and new forms of dialogue between specialists and broader publics. Whether such uses weaken or strengthen scholarship depends less on the abstract presence of AI than on the infrastructures, governance processes, and values through which AI is developed and adopted.

The landscape will continue to shift. New capabilities will emerge, governance frameworks will evolve, communities will develop practices and norms through experimentation and deliberation. What this bibliography offers is a documented moment from which change can be measured and assessed. The sources assembled here provide conceptual resources for that ongoing work: frameworks for analysis, evidence of effects, models for governance, and principles for evaluation. The task ahead is to use these resources thoughtfully, maintaining the commitments to accessibility, reciprocity, and public engagement that make scholarship worth pursuing.

{{Navigation|previous=Essential Ideas|next=Essential Contexts}}

{{BookCat}}</text>
      <sha1>5aa16amg7px2w8797spzg7wkixbjbwy</sha1>
    </revision>
  </page>
  <page>
    <title>Taking Bearings: Artificial Intelligence in Knowledge Platforms and Open, Social Scholarship/Essential Contexts</title>
    <ns>0</ns>
    <id>483462</id>
    <revision>
      <id>4656119</id>
      <parentid>4655840</parentid>
      <timestamp>2026-08-02T21:31:27Z</timestamp>
      <contributor>
        <username>CorreiaA</username>
        <id>3614427</id>
      </contributor>
      <minor />
      <origin>4656119</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="51283" sha1="29m8xjzsv1b92r8bixiu32khqnxbl99" xml:space="preserve">==Histories &amp; Theories of AI==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Ali, Syed Mustafa, Stephanie Dick, Sarah Dillon, Matthew L. Jones, Jonnie Penn, and Richard Staley. 2023. “Histories of Artificial Intelligence: A Genealogy of Power.” ''BJHS Themes'' 8: 1–18. https://doi.org/10.1017/bjt.2023.15.'''
&lt;/div&gt;

The work of these authors seeks to move beyond “conventional origin myths” of AI by contextualizing the academic historical approach within their interdisciplinary backgrounds. As a result, Ali et al. argue that histories of broader processes (like industrialization, colonialism, and social science) can represent the “genealogy” of AI, which is not identified as a specific object but as a grouping of diverse technologies under a loose banner, requiring an equally diverse approach. Although AI is the “flagship of the Information Age,” it was clearly conditioned by the “Management Age,” as these “genealogies” feature four common thematic threads of “hidden labour,” “encoded behaviour,” “disingenuous rhetoric,” and “cognitive injustice.” AI is therefore not only situated within the history of computing, but the history of control, the product of the interacting formalist and empiricist views of “intelligence” within Cold War epistemology. In many ways, AI’s refinement of formal abstraction reinforces and impresses Western systems and structures, so these authors do not critique AI with the goal of improvement, but to clarify what AI “is,” “is not,” and perhaps “should not” be.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Anderson, Marc M. 2024. “AI as Philosophical Ideology: A Critical Look Back at John McCarthy’s Program.” ''Philosophy &amp; Technology'' 37 (2): 44. https://doi.org/10.1007/s13347-024-00731-1.'''
&lt;/div&gt;

This paper critically analyzes the synthesis of McCarthy’s AI development program, identifying its goals’ nature, purpose, relationship to society, and implications upon morality and social control. Firstly, Anderson considers the most problematic themes of McCarthy’s early and middle writings, then arguing that McCarthy’s later works consolidated his stance by replacing “tentative assumptions” with “statements whose linkages with contemporaneous analytic philosophy are made unequivocally” and thereby present AI as “the outcome of a certain philosophical way of looking at the world.” Here, Anderson emphasizes McCarthy’s biases toward objectivism, scientism, and analytic behaviourism; tendency to enable progress in AI by waiting to identify risks; positioning of philosophy as subordinate “handmaiden” to science; and uneasy presupposition that humans have innate knowledge of the world’s object character (which AI will need added). To Anderson, the sum of the “ethical” aspects, “philosophical” aspects, and “competitive” nature of McCarthy’s program give it all the fundamental “characteristics of an ideological program.” This ideology has had deep direct influence, for example by joining AI ethics to consequentialist dilemmas like the “Trolley problem,” and deep indirect influence, for example by influencing a modular and component technical approach. Anderson argues this “ideology” was caused by McCarthy’s motive of making a “servile” and “stripped down model of human mental engagement without emotional qualities.” Overall, Anderson argues McCarthy’s conception of AI as a “perfectly rational abstraction of human thinking” involves severe misconceptions around rationality, and has “come to serve as a blind for increasing techno-corporate control of society” with its propagation of the belief that “AI systems should be controlled as servants.”

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Bender, Emily M., Timnit Gebru, Angelina McMillan-Major, and Shmargaret Shmitchell. 2021. “On the Dangers of Stochastic Parrots: Can Language Models Be Too Big? 🦜.” In ''Proceedings of the 2021 ACM Conference on Fairness, Accountability, and Transparency'', 610–23. https://doi.org/10.1145/3442188.3445922.'''
&lt;/div&gt;

Bender et al. critically analyze the environmental and social risks of ever larger language models trained with huge uncurated datasets from the web. Their first concern is the environmental costs of training language models, which require increasing energy and compute requirements that further environmental damages that are more likely to fall on marginalized populations. Their social concerns are that language models have the potential to reproduce hegemonic views, reinforce stereotypes, and further reify inequality due to the unrepresentativeness of their training data. Despite the increasing amounts of data ingested in these models, the authors argue that size does not guarantee diversity because there are people who are not on the web (and therefore not included in training data), the content of marginalized people online is less likely to be included in these large datasets and, if it is, it might be filtered out during the data preparation process. Therefore, the authors urge developers to stop using larger training datasets if they cannot be documented. As an alternative, they suggest curating and documenting smaller datasets created for specific purposes, evaluating models by the amount of resources they consume, and developing research that centres the people who are more likely to be adversely affected by the resulting technology.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Berry, David M. 2025. “Synthetic Media and Computational Capitalism: Towards a Critical Theory of Artificial Intelligence.” ''AI &amp; Society'' 40: 5257–5269. https://doi.org/10.1007/s00146-025-02265-2.'''
&lt;/div&gt;

Berry develops a critical theory of artificial intelligence centred on what he terms the &quot;algorithmic condition&quot;—a historical moment when computational systems generate cultural content indistinguishable from human production, thereby destabilizing traditional markers of authenticity and authorship. Engaging with Frankfurt School critical theory, particularly concepts of false consciousness and reification, Berry argues that contemporary AI represents a qualitative transformation he calls &quot;the Inversion,&quot; where machine-generated works not only replicate but actively reshape the grounds upon which experience and meaning are constituted. This moves beyond mechanical reproduction (Benjamin) or cybernetic feedback (Wiener) toward what Berry theorizes as &quot;post-consciousness,&quot; where boundaries between individual and synthetic consciousness become porous. His concept of &quot;diffusionisation&quot; describes how AI systems dissolve cultural forms into probabilistic vector spaces and reconstitute them through latent space manipulation, producing &quot;AI slop&quot;—low-quality synthetic content that infiltrates information ecosystems with garbled meaning. Berry positions this transformation within &quot;computational capitalism,&quot; arguing that algorithmic mediation now structures forms of life in ways that demand new critical methods. His &quot;constellational analysis&quot; proposes mapping the interdependencies among technical systems, cultural production, and political-economic structures to resist subsumption into algorithmic logics. Where earlier automation debates focused on task substitution, Berry foregrounds how synthetic media transforms the infrastructure of meaning-making itself, rendering questions of interpretability and embedded bias not as technical problems but as symptoms of deeper epistemic and political reconfigurations under computational conditions.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Chun, Jon, and Katherine Elkins. (2023). “The Crisis of Artificial Intelligence: A New Digital Humanities Curriculum for Human-Centred AI.” ''International Journal of Humanities and Arts Computing'' 17 (2). https://doi.org/10.3366/ijhac.2023.0310&lt;nowiki/&gt;.'''
&lt;/div&gt;

Chun and Elkins position AI's rapid advancement as precipitating multiple interlocking crises—in higher education, in diversity and inclusion within technology fields, and in the broader socioeconomic fabric—that demand a specifically humanities-oriented pedagogical response. Their intervention challenges the prevalent assumption that AI literacy should emerge from STEM-dominated curricula, arguing instead that Digital Humanities offers distinctive pathways for cultivating critical engagement with computational systems. Where conventional computer science education treats AI as primarily a technical phenomenon requiring engineering skills, Chun and Elkins foreground reflective and collaborative meaning-making, insisting that the most effective AI tools amplify rather than replace human intellectual engagement. Their framework explicitly connects pedagogical design to civic preparation, positioning students not as mere consumers or operators of AI systems but as critically engaged citizens capable of interrogating the social and economic implications of algorithmic mediation. Drawing on theories of human-centred computing, they articulate an AI DH curriculum structured around two core commitments: opening meaningful research avenues for humanities scholars working with computational methods and addressing DEI shortcomings by engaging students traditionally alienated by conventional STEM pathways. Their approach implicitly challenges the epistemic authority claims embedded in AI discourse—the fantasy that technical expertise alone can adjudicate questions about algorithmic deployment—by insisting that humanistic inquiry offers essential resources for navigating AI's transformative effects on knowledge production, labour organization, and cultural representation.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Chung, Hiu-Fung. 2025. “Betting on (Un)Certain Futures: Sociotechnical Imaginaries of AI and Varieties of Techno-Developmentalism in Asia.” ''Information, Communication &amp; Society'', 1–18. https://doi.org/10.1080/1369118X.2025.2535427.'''
&lt;/div&gt;

Chung redirects scholarly attention from dominant AI powers—China, the United States—to economically advanced but geographically non-dominant Asian societies: Singapore, Hong Kong, and Taiwan. Mobilizing the concept of &quot;techno-developmentalism&quot; to analyze how developmental states harness technological innovation for political-economic projects, Chung identifies three distinct imaginaries that emerge from specific historical, institutional, and geopolitical conditions. Singapore's &quot;cybernetic pragmatism&quot; deploys AI to legitimize neoliberal authoritarianism, embedding computational governance as a continuation of technocratic rule. Hong Kong's &quot;techno-entrepreneurship&quot; imaginary seeks to refashion financial capitalism through AI-driven innovation, positioning the territory as a global fintech hub amid shifting relationships with mainland China. Taiwan's &quot;defensive survival modality&quot; frames AI development as simultaneously addressing internal socioeconomic instability and external threats from superpower rivalry, particularly cross-strait tensions. Chung's analysis challenges the Global North/South binary that structures much AI governance literature, revealing how small advanced economies navigate strategic coupling with global tech industries while managing profound uncertainties about AI-centric reforms. His discourse analysis of policy documents from the early 2010s through 2024 demonstrates how national imaginaries encode assumptions about automation's effects on labour markets, the appropriate balance between state coordination and market mechanisms, and the role of computational infrastructure in securing geopolitical position. This comparative framework illuminates how different state formations mobilize AI to address divergent crises of legitimacy, capital accumulation, and sovereign security.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Van Es, Karin, and Dennis Nguyen. 2024. “‘Your Friendly AI Assistant’: The Anthropomorphic Self-Representations of ChatGPT and Its Implications for Imagining AI.” ''AI &amp; Society'' 40: 3591–3603. https://doi.org/10.1007/s00146-024-02108-6&lt;nowiki/&gt;.'''
&lt;/div&gt;

Van Es and Nguyen analyze how “social-technical imaginaries” invoked by “self-representations” of GenAI could influence public perception of the technology. These “socio-technical imaginaries” are a category of trending concept, which can exist in contrast, as both utopian and dystopian conceptions of AI are present in public discourse. These are dynamically changeable, often strategically promoted by tech companies to influence regulation, and influenced by a variety of media technologies and ecologies with equally diverse social, cultural, and political implications. The authors identify a range of current “socio-technical imaginaries” of AI. This includes: misconceived “magical thinking,” largely produced by poor terminology; speculative, exaggerative debates on AI capabilities, which distract from actualized and present risks; visual motifs correlating intelligence, efficiency, logic, duty, and trust, which are not inherent to Generative AI; and anthropomorphism, which brings a slew of problems surrounding social biases. To study AI “self-representations,” van Es and Nguyen have ChatGPT generate fifty images and fifty-eight sections of text, responding to several variations of the prompt “create an image of yourself.” The authors then perform an empirical, qualitative-exploratory analysis of this content to examine which “socio-technical imaginaries” dominate the material. These images most significantly emphasized ChatGPT’s alleged “social intelligence,” depicted as a friendly research assistant possessing “real” intellect—ironically often surrounded by books. Anthropomorphism was usually present, with eighty-two percent of images portraying AI as humanoid, and a further six percent as a human brain. Futuristic motifs like holograms, metallic shades, and the cosmos portrayed AI as near-magical. Textual responses expressed these same themes, demonstrating consistent messaging. Taken together, these generated responses encourage overlooking the ethical and legal challenges posed by trending GenAI technologies, “overestimate their capabilities”, and “potentially lead to mistakenly perceive them as trustworthy companions.” This raises questions as to what extent specific guidelines to these responses were programmed by OpenAI, or indicative of popular opinion.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Jones, Matthew L. 2023. “AI in History.” ''American Historical Review'' 128 (3): 1360–67. https://doi.org/10.1093/ahr/rhad361.'''
&lt;/div&gt;

Jones explores how evolving approaches to AI research reflect upon the importance of studying artificial intelligence’s history. He believes traditional attempts to produce “symbolic” AI have been proven as misguided, comparing their failures to the traditionally unpopular “empiricist” approach. This approach is now dominant and involves the use of large-scale algorithms to capitalize upon the “unreasonable effectiveness of data” via “machine learning.” However, this shift in trends has also forced the meaning and capabilities of “artificial intelligence” to be reconsidered, now threatening “professions centred on particularity” like history. In response, Jones argues modern AI cannot be considered a “neutral substratum” but as a reflection of human creations—including their best and worst traits. Historians are experts at detecting bias, and this understanding of AI’s historical context is clearly necessary for its appropriate application, so historians should be playing a fundamental role in ensuring AI’s critical use. Jones believes historians can best do this by highlighting the “traces of labour” that can illustrate the “granular complex reality” of AI.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Klein, Lauren, Meredith Martin, André Brock, Maria Antoniak, Melanie Walsh, Jessica Marie Johnson, Lauren Tilton, and David Mimno. 2025. “Provocations from the Humanities for Generative AI Research.” Preprint, ''arXiv'', February 26. https://arxiv.org/abs/2502.19190.'''
&lt;/div&gt;

Klein et al. explore the stakes of engaging with AI by juxtaposing the humanistic scholar’s investigation of the &quot;human&quot; with the &quot;anti-human&quot; approach of AI, a dichotomy they contextualize within late-stage capitalism. Klein et al. argue that AI’s generalist, binary approach &quot;distorts 'culture’ to content.&quot; AI programs thereby conduct a &quot;statistical enactment of… ideology,&quot; imposing an objectivist European modernist framework of understanding upon the data. This binary conception of data is highlighted within ideas of &quot;pure&quot; versus &quot;toxic&quot; training data, which dismiss that the material inherently &quot;reflects cultures and consists of expressions of those cultures.&quot; Even content not being included &quot;biases&quot; the rest of the data, so the best practices of open scholarship cannot fix the root issue—the only way to resolve the issues caused by &quot;bias&quot; is to target the sources of the underlying structural problems. Klein et al. argue this flawed situation was fuelled by &quot;corporate spokespeople parroting AI hype&quot; to research—and that this relationship’s politicization should be a particular source of concern. Klein et al. argue AI can still serve a purpose, however. They propose AI with smaller datasets will produce more accurate information when tailored for specific topics and with input from experts of the humanities. Humanists cannot solely effect change, however, as &quot;technical researchers must recognize the institutional asymmetries&quot; of administrative support and funding available to ensure development of &quot;humanistic&quot; AI is a truly equal and interdisciplinary effort. 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''McIntosh, Timothy R., Teo Susnjak, Tong Liu, Paul Watters, and Malka N. Halgamuge. 2023. “From Google Gemini to OpenAI Q* (Q-Star): A Survey of Reshaping the Generative Artificial Intelligence (AI) Research Landscape.” ''Technologies''. https://doi.org/10.3390/technologies13020051&lt;nowiki/&gt;.'''
&lt;/div&gt;

McIntosh et al. offer a survey of AI development’s frontiers targeted at fellow experts of the field, focusing on evolving “agentic” AI and its resulting research applications. Covering developments, they primarily employ case studies to demonstrate how multimodal AI could eclipse undynamic LLMs, but various “advanced learning techniques” and developments in model architecture are also outlined. On this topic, a table is presented to quantify the relevance of research fields and subfields of AI development. Agentic AI’s possible applications include aiding research by bolstering academic integrity, its market relevance, and its “creative” purposes. McIntosh et al. even argue that development of AGI with “symbolic reasoning” and “probabilistic inference” could handle issues like climate change, considered as a long-term but significant possibility. Therefore, this work is primarily theoretical, with McIntosh et al. centralizing AI’s idealistic applications. However, they do acknowledge AI must be developed with ethical and social principles, for which interdisciplinary cooperation is necessary. 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Mao, Yishu, Vanessa Richter, and Christian Katzenbach. (2025). &quot;Strategising imaginaries: How Corporate Actors in China, Germany and the US Shape AI Governance.&quot; ''Big Data &amp; Society'' 12 (1). https://doi.org/10.1177/20539517251400727&lt;nowiki/&gt;.'''
&lt;/div&gt;

Mao, Richter, and Katzenbach systematize the concept of &quot;sociotechnical imaginaries&quot; as an analytical framework for understanding how collective visions of AI futures shape governance, investment, and public discourse. Engaging explicitly with science and technology studies scholarship—particularly Jasanoff and Kim's formulation of imaginaries as &quot;collectively held, institutionally stabilized, and publicly performed visions&quot;—they demonstrate how AI's meaning emerges through contested negotiations among stakeholders from industry, government, academia, media, and civil society. Their comparative analysis across the United States, China, and Germany challenges simplistic national characterizations, revealing heterogeneous and often contradictory imaginaries even within single regulatory regimes. Where US discourse fragments across multiple geographic AI hubs, German imaginaries centre on EU policy compliance and regulatory frameworks, while Chinese articulations align tightly with party-state directives that minimize local variation. The source argues that these imaginaries function performatively, not merely representing AI's future but actively mobilizing resources, legitimating interventions, and establishing trajectories for development. Their framework illuminates how benchmark cultures, optimization narratives, and investor expectations become embedded in technical choices through discursive processes that precede and exceed engineering decisions. By foregrounding stakeholder co-dependencies and cross-national dynamics, the authors position AI imaginaries as sites where epistemological assumptions about intelligence, automation, and progress become institutionalized through political-economic mechanisms—a contribution that connects discourse analysis to questions of power, accountability, and the material reorganization of labour and knowledge production.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Whiteley, Paul. 2023. “Why Artificial Intelligence Is a Misnomer.” ''London School of Economics and Political Science Politics and Policy Blog'', October 19. https://blogs.lse.ac.uk/politicsandpolicy/why-artificial-intelligence-is-a-misnomer/.'''
&lt;/div&gt;

Whiteley criticizes the use of the term artificial intelligence, noting that while such technologies can be valuable for automating specific tasks, the term John McCarthy used in the 1950s was a “disservice.” He argues that the term anthropomorphizes what is essentially a form of computer-assisted statistical analysis. Much of what we call AI functions as a sophisticated prediction system that processes vast amounts of data to produce answers, without any real understanding of the underlying concepts or theories. Whiteley further distinguishes between algorithms, which follow set procedures to identify patterns and make predictions, and inference, which involves interpreting and explaining why those patterns occur. He concludes that the ultimate goal in the field of AI is to create systems capable of predicting behaviour across diverse problems. However, he emphasizes that current AI algorithms remain highly specialized, excelling in narrow tasks but lacking the flexibility and understanding required for true general intelligence.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Zeffiro, Andrea. 2024. “Automating (In)securities: Cybersecurity’s AI Imaginaries.” Paper presented at EASST/4S, 2024. https://nomadit.co.uk/conference/easst-4s2024/p/14156.'''
&lt;/div&gt;

Zeffiro interrogates cybersecurity's AI imaginaries through case studies of IBM Watson for Cybersecurity, CrowdStrike's Charlotte AI, and Google's Sec-PaLM, revealing how corporate narratives of AI as &quot;game changer&quot; and &quot;democratizing force&quot; systematically obscure differential vulnerabilities and normative biases. Her analysis challenges the prevalent framing of AI-driven threat detection as technically neutral automation, arguing instead that these systems encode and amplify assumptions about what constitutes risk, who merits protection, and whose insecurities remain invisible. Drawing on critical security studies and science and technology studies, Zeffiro demonstrates how generative AI applications in cybersecurity automate not merely data collection and pattern recognition but also the normative judgments about threat hierarchies embedded in training regimes and performance metrics. Her concept of &quot;automating insecurities&quot; captures this dual process: while AI tools promise enhanced security through real-time threat response with minimal human intervention, they simultaneously institutionalize particular understandings of vulnerability that reflect corporate priorities and market positioning in the &quot;AI arms race.&quot; Zeffiro's analysis connects these imaginaries to epistemic claims about AI's inevitability, showing how IBM, CrowdStrike, and Google construct future visions that naturalize their technological approaches while marginalizing alternative security paradigms. By foregrounding what these imaginaries omit—the differential distribution of cyber vulnerabilities across social positions, the political economy of security infrastructure, the discretionary authority embedded in algorithmic triage—Zeffiro positions cybersecurity AI as participating in broader patterns of automation that redistribute power and accountability rather than merely enhancing technical capabilities.


== Past Relation to OSS-Aligned Communities ==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Carnegie Endowment for International Peace. 2024. ''Beyond Open vs. Closed: Emerging Consensus and Key Questions for Foundation AI Model Governance''. https://carnegieendowment.org/research/2024/07/beyond-open-vs-closed-emerging-consensus-and-key-questions-for-foundation-ai-model-governance?lang=en.'''
&lt;/div&gt;

The report dismantles the binary framing—open vs. closed—that has organized foundation model governance debates, replacing it with a multidimensional spectrum where weight release is only one variable among many (architecture, training data, documentation, licensing terms, structured access). Seven consensus points establish that &quot;openness&quot; serves multiple, sometimes conflicting values (transparency, competition, safety, inclusion) and that weight release amplifies both beneficial and harmful potential without symmetry—its irreversibility and resistance to post-release monitoring create a qualitatively different governance problem than closed deployment, even though closed models' theoretical safety advantages are unevenly realized in practice. The report introduces &quot;precautionary friction&quot; (staged/structured release calibrated to marginal risk over a defined baseline) as the operative governance concept, explicitly rejecting both blanket openness and blanket restriction. Seventeen open questions then expose the infrastructure gaps: evaluation science remains embryonic, post-release monitoring is under-theorized, risk thresholds published by labs lack enforcement specificity, and Global South labour and data contributions are structurally undervalued. This source clarifies the claim that software-style &quot;open source&quot; maps poorly onto foundation models and that hybrid, graduated-release frameworks are where policy consensus is actually forming.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Mitra, Bhaskar, Henriette Cramer, and Olya Gurevich. 2024. “Sociotechnical Implications of Generative Artificial Intelligence for Information Access.” Preprint, ''arXiv'', May 19. https://doi.org/10.48550/arXiv.2405.11612.'''
&lt;/div&gt;

Bhaskar et al. diagnose “information access” under generative AI as a sociotechnical settlement rather than a neutral upgrade to search: models do not just retrieve, they intermediate credibility, reshape attention, and re-allocate epistemic authority through interfaces that compress provenance and uncertainty. Their framing is especially useful for open, social scholarship because it links familiar problems of access (indexing, ranking, evaluation) to newer constraints created by platform dependence, opaque model behaviour, and the enclosure of research pathways behind proprietary tooling and data. Read through the lenses of industry capture and AI imaginaries, the chapter clarifies how promises of universal assistants can normalize monopoly infrastructures while shifting audit burdens onto users and public institutions. It also implicitly strengthens open communities’ insistence on reproducibility: without open benchmarks, inspectable logs, and preservable corpora, “trustworthy information” becomes a brand claim rather than an evaluable property. The ideas bridge directly to libraries, repositories, and information policy by treating curation, metadata, and stewardship as counter-monopoly infrastructure for accountable AI-mediated access.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Open Source Initiative. The Open Source AI Definition 1.0 (2024–2025). https://opensource.org/ai'''
&lt;/div&gt;

OSI’s Open Source AI Definition 1.0 operationalizes “open” as a bundle of enforceable freedoms rather than a branding claim, and it does so by porting the open source software tradition into the AI stack where “source” is more than just code. The definition makes the four freedoms—use, study, modify, share—the evaluative core, then adds a crucial precondition: exercising any of these rights requires access to the preferred form for making modifications and the means to use the system. That move is the governance lever: it blocks “open weights” releases from standing in for openness when the artifacts needed to understand or change system behaviour are withheld. On OSI’s framing, openness is not satisfied by permissive inference access or a model file alone; it is satisfied when the system is provisioned so that auditability and alteration are practically possible, including transparency sufficient to trace how results were created and where components (notably data sources) come from. The definition is therefore designed as an anti-openwashing instrument: it supplies a community standard that can be applied to legal/technical packaging to distinguish genuinely open AI systems from hybrid offerings that preserve vendor control through restrictions or missing components. OSI explicitly positions this as policy-relevant infrastructure—an interpretive anchor for regulators and OSS communities trying to resist enclosure pressures while preserving permissionless collaboration. This is a community standard, not a journal article; it is nonetheless important for governance, policy, and OSS alignment.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Vake, Domen, Bogdan Šinik, Jernej Vičič, and Aleksandar Tošić. 2025. “Is Open Source the Future of AI? A Data‑Driven Approach.” Preprint, ''arXiv'', January 27. https://arxiv.org/abs/2501.16403&lt;nowiki/&gt;.'''
&lt;/div&gt;

Vake et al. analyze the data of open-source large language models shared on HuggingFace to explore if the open-source community influences the development of LLMs. The authors found that the AI open-source community is expanding rapidly, and it has enhanced the performance of a handful of popular models. However, open-source AI depends on businesses to develop base models and release them openly, but there are few incentives to do so because it risks their intellectual property and competitive edge. Furthermore, AI is different from the development of open-source software because the general public cannot privately run these models. Therefore, the authors conclude that the future of AI development could be similar to the software-as-a-service model, in which the open-source community contributes to model development, while companies generate revenue from model usage.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''White, Matt, Ibrahim Haddad, Cailean Osborne, Xiao-Yang Liu, Ahmed Abdelmonsef, Sachin Varghese, and Arnaud Le Hors. 2024. “The Model Openness Framework: Promoting Completeness and Openness for Reproducibility, Transparency, and Usability in AI.” Preprint, ''arXiv'', March 20. https://doi.org/10.48550/arXiv.2403.13784&lt;nowiki/&gt;.'''
&lt;/div&gt;

White et al.'s Model Openness Framework (MOF) represents an effort to translate open-source software principles into AI research practices, addressing the growing gap between claims of &quot;openness&quot; and actual transparency in AI model development. Developed through the Linux Foundation's AI &amp; Data Foundation, the framework establishes a three-tiered classification system that specifies which components (code, data, documentation, trained weights, evaluation procedures) must be released under open licenses for models to qualify as &quot;Class III: Open Model,&quot; &quot;Class II: Open Tooling,&quot; or &quot;Class I: Open Science.&quot; The authors' intervention addresses what they term &quot;openwashing&quot;—the strategic use of &quot;open source&quot; rhetoric by companies releasing models with restrictive licenses or incomplete artifacts. By codifying 17 critical components for complete model releases, they make visible the specific practices required for reproducibility and scrutiny, challenging the binary conception of openness inherited from software. Their framework reveals that AI &quot;openness&quot; exists on a spectrum of completeness, from minimal weight release to full disclosure of training data, intermediate checkpoints, and development documentation. Positioned within debates about responsible AI development, the MOF represents a community-driven effort to establish norms before they become ossified by corporate practice or regulatory fiat. The authors draw explicitly on open science principles (FAIR data, reproducibility standards) while adapting them to AI's unique characteristics—particularly the centrality of training data and the distinction between model architecture (code) and trained parameters (data).

== Bias and Technological Determinism ==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Akter, Shahriar, Grace McCarthy, Shahriar Sajib, Katina Michael, Yogesh K. Dwivedi, John D’Ambra, and K. N. Shen. 2021. “Algorithmic Bias in Data-Driven Innovation in the Age of AI.” ''International Journal of Information Management'' 60: 102387. https://doi.org/10.1016/j.ijinfomgt.2021.102387.'''
&lt;/div&gt;

Akter and colleagues theorize algorithmic bias as emerging from three distinct but interacting sources—data bias, method bias, and societal bias— positioning bias as structural phenomenon inscribed across the entire data-driven innovation (DDI) lifecycle rather than localized technical artifact amenable to isolated correction. Their case study of Australia's Robo-Debt scheme demonstrates how algorithmic systems inherit and amplify existing inequities and foregrounds &quot;dynamic managerial capability&quot; as essential for addressing bias. The authors challenge purely technical approaches, arguing instead that organizational capacity to recognize, interrogate, and respond to bias across data provenance, algorithmic design, and deployment contexts determines whether DDI produces equitable or discriminatory outcomes. This positions bias mitigation as ongoing institutional work requiring cross-functional expertise rather than one-time technical intervention. Their framework implicitly contests technological determinism by revealing how managerial choices about data collection priorities, acceptable error rates, and stakeholder consultation shape algorithmic outcomes in ways that exceed engineering decisions. The emphasis on societal bias as distinct category acknowledges that algorithms operate within and reproduce broader patterns of structural inequality—assumptions about creditworthiness, employability, or welfare eligibility that reflect historical discrimination. Akter et al.'s intervention thus connects bias scholarship to organizational studies and innovation management, positioning algorithmic fairness not as mathematical property but as emergent from institutional practices, power relations, and the political-economic contexts within which DDI unfolds. 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Jarrahi, Mohammad Hossein, Gemma Newlands, Min Kyung Lee, Christine T. Wolf, Eliscia Kinder, and Will Sutherland. 2021. “Algorithmic Management in a Work Context.” ''Big Data &amp; Society'' 8 (2). https://doi.org/10.1177/20539517211020332.'''
&lt;/div&gt;

Analyzes algorithmic management as a sociotechnical phenomenon reshaping power, discretion, and information flows in organizations; details opacity at technical and organizational levels. Exposes determinist narratives in “smart” automation of management decisions; shows how design choices redistribute authority and labour—central to a nondeterministic, governance-forward stance.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Sartori, L., and A. Theodorou. 2022. “A sociotechnical perspective for the future of AI: narratives, inequalities, and human control.” ''Ethics and Information Technology'' 24 (1), 4. https://doi.org/10.1007/s10676-022-09624-3&lt;nowiki/&gt;.'''
&lt;/div&gt;

Sartori and Theodorou position AI as a &quot;magnifying glass&quot; that automates and amplifies existing social inequalities rather than introducing bias as a novel technical problem, directly challenging narratives that frame fairness as achievable through post hoc algorithmic adjustment. Their sociotechnical framing insists that intelligent machines operate within specific institutional contexts where historical patterns of discrimination become encoded in data collection, annotation practices, and deployment decisions—a structural account that resists reduction to technical fixes. The authors engage critically with the AI technical community's emphasis on transparency, explainability, accountability, and contestability, acknowledging these as necessary but insufficient responses that risk becoming &quot;panaceas&quot; if divorced from attention to power asymmetries and organizing visions. Their analysis of technological narratives reveals how AI discourse reflects and reproduces traditional lines of social, economic, and political inequality: who gets to articulate AI futures, whose concerns register as legitimate risks, and which imaginaries gain institutional traction. By foregrounding narratives as both reflecting organizing visions and constituting &quot;tangible signs&quot; of inequality, Sartori and Theodorou demonstrate how deterministic framing—treating AI development as inevitable—forecloses deliberation about alternative design pathways. Their call for &quot;diverse approaches&quot; and &quot;richer knowledge about narratives&quot; positions non-determinism as methodological commitment: attending to contingent choices, plural stakeholder perspectives, and varied criteria of success that resist singular optimization logics. This intervention connects bias scholarship to governance debates, arguing that human control requires not just technical interpretability but institutional mechanisms for contestation that acknowledge AI practice as fundamentally interdisciplinary and politically consequential.

== Knowledge Foundations ==

===Diversity===

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Arbuckle, Alyssa. 2020. “How Can We Broaden and Diversify Humanities Knowledge Translation?” ''Pop! Public. Open. Participatory'', no. 2. https://doi.org/10.48404/pop.2020.12&lt;nowiki/&gt;.'''
&lt;/div&gt;

Articulates diversity as a condition for valid public-facing scholarship; emphasizes inclusive modes of knowledge translation and participatory approaches resonant with OSS.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Arthur, Paul L., Lyida Hearn, Lucy Montgomery, Hugh Craig, Alyssa Arbuckle, and Ray Siemens. (2021). “Open Scholarship in Australia: A Review of Needs, Barriers, and Opportunities.” ''Digital Scholarship in the Humanities'' 36 (4), 795–812. https://doi.org/10.1093/llc/fqaa063&lt;nowiki/&gt;.'''
&lt;/div&gt;

Australian context scan identifies structural barriers and opportunities for diverse participation in open scholarship.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Crompton, Constance, Lori Antranikan, Ruth Truong, and Paige Maskell. 2020. “Familiar Wikidata: The Case for Building a Data Source We Can Trust.” ''Pop! Public. Open. Participatory'', no. 2. https://doi.org/10.48404/pop.2020.02&lt;nowiki/&gt;.'''
&lt;/div&gt;

Makes the case for community governance and trust in open data infrastructures to safeguard plural representation and mitigate erasure in knowledge graphs.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Fanning, Katie, Claire Kim, and Jon Saklofske. 2023. “Interactive Inspirations: The Case for Incorporating Joy and Play in Open Social Scholarship.” ''Pop! Public. Open. Participatory'', no. 5. https://doi.org/10.54590/pop.2023.012&lt;nowiki/&gt;.'''
&lt;/div&gt;

Argues that Open Social Scholarship must move beyond simple open access by cultivating &quot;joy and play&quot; as critical, anti-capitalist methodologies for community engagement. The authors demonstrate this through a prototype parody app and use its practical limitations to expose the structural friction between sustaining non-extractive digital commons and the realities of privatized app ecosystems and precarious academic funding.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Rockwell, Geoffrey, Kaylin Land, and Andrew MacDonald. 2021. “Social Analytics Through Spyral.” ''Pop! Public. Open. Participatory'', no. 3. https://doi.org/10.54590/pop.2021.004. '''
&lt;/div&gt;

Demonstrates community-aware analytics for scholarly communities; touches on representational choices and the risks of flattening diverse practices through metrics.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Siemens, Lynne, and the INKE Research Group (2023). “I Stayed for the Community: Collaboration and Community in an Open Social Scholarship Research Project.” ''Pop! Public. Open. Participatory'', no. 5. https://doi.org/10.54590/pop.2023.013&lt;nowiki/&gt;.'''
&lt;/div&gt;

Views the success of open social scholarship as depending heavily on &quot;heritage relationships&quot; and the invisible labour of interpersonal maintenance, treating cross-sector collaboration as a deliberate methodological challenge rather than a natural byproduct of funding. Highlights a structural tension between community-driven qualitative goals and rigid academic metrics, urging institutions to formally recognize and resource the relational infrastructure that sustains Digital Humanities projects.

===Mobilisation===

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Arbuckle, Alyssa, Ray Siemens, Jon Bath, Constance Crompton, Laura Estill, Tanja Niemann, Jon Saklofske, and Lynne Siemens. 2022. “An Open Social Scholarship Path for the Humanities.” ''The Journal of Electronic Publishing'' 25 (2). https://doi.org/10.3998/jep.1973&lt;nowiki/&gt;.'''
&lt;/div&gt;

Defines OSS practices and infrastructures to support translation, engagement, and reciprocal exchange between researchers and publics.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Jensen, Graham. 2023. “Introduction: Digital Knowledge Commons, Scholarly Connection, and the Evolution of Open Scholarship.” ''Open Scholarship Press Curated Volumes: Connection''. https://doi.org/10.21428/47bc126e.0ca461a4&lt;nowiki/&gt;.'''
&lt;/div&gt;

Connects social scholarly tools and commons-based infrastructures to mobilization pathways; highlights interoperability and community practices.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Nelson, Brent, Miguel Dela Pena, the Prototyping the Digital Archive Team, and the INKE Research Group. 2023. “No Journal is an Island: The John Donne Journal and the Possibilities of Open Access.” ''Pop! Public. Open. Participatory'', no. 5. https://doi.org/10.54590/pop.2023.007&lt;nowiki/&gt;.'''
&lt;/div&gt;

Case study of OA pathways as mobilization; addresses circulation, visibility, and engagement with broader publics.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Winter, Caroline. 2023. “Introduction: Open Scholarship Policy in Focus.” ''Open Scholarship Press Curated Volumes: Policy''. https://doi.org/10.21428/47bc126e.5abba88b&lt;nowiki/&gt;.'''
&lt;/div&gt;

Frames policy as a vehicle for knowledge mobilization across sectors; emphasizes provenance, accountability, and public value alignment.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Winter, Caroline, Tyler Fontenot, Luis Meneses, Alyssa Arbuckle, Ray Siemens, and the ETCL and INKE Research Groups. 2020. “Foundations for the Canadian HSS Commons: Exploring the Possibilities of Digital Research Communities.” ''Pop! Public. Open. Participatory'', no. 2. https://doi.org/10.48404/pop.2020.05&lt;nowiki/&gt;.'''

Maps HSS Commons as mobilization infrastructure; addresses governance mechanisms, provenance, and dialogic engagement in a Canadian context.

&lt;/div&gt;

===Platforms===

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Bullard, Julia. 2023. “Describing the HSS Commons: The View from Metadata.” ''Pop! Public. Open. Participatory'', no. 5. https://doi.org/10.54590/pop.2023.004. '''
&lt;/div&gt;

Metadata as platform backbone; shows how descriptive schemas shape visibility/legitimacy; connects to interoperability and inclusive description.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Goddard, Lisa. (2021). “Persistent Identifiers as Open Research Infrastructure to Reduce Administrative Burden.” ''Pop! Public. Open. Participatory'', no. 3. https://doi.org/10.54590/pop.2021.006. '''
&lt;/div&gt;

PIDs as platform connective tissue; crucial for provenance, traceability, and platform interoperability across repositories/journals.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Jensen, Graham, Alyssa Arbuckle, Caroline Winter, Talya Jesperson, Tyler Fontenot, Ray Siemens, and the ETCL and INKE Research Groups. 2022. “Fostering Digital Communities of Care: Safety, Security, and Trust in the Canadian HSS Commons.” ''IDEAH'' 3 (2). https://ideah.pubpub.org/pub/h7927ugt. '''
&lt;/div&gt;

Governance and moderation as platform design commitments; aligns with OSS values around safety and reciprocity.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Meneses, Luis. 2020. “Integrating the Social Media Engine with Large-scale Open Access Repositories: A Discussion.” ''Pop! Public. Open. Participatory'', no. 2. https://doi.org/10.48404/pop.2020.04. '''
&lt;/div&gt;

Explores platform coupling between OA repositories and social layers; anticipates AI-mediated discovery/recommendation impacts on visibility.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Turin, Mark. 2021. “From Orality to Open: Innovations in Multimedia Monograph Publishing in the Humanities.” ''Pop! Public. Open. Participatory'', no. 3. https://doi.org/10.54590/pop.2021.005. '''
&lt;/div&gt;

Platform affordances for multimodal scholarship; how platform standards and workflows enable plural forms and publics.

== Open Social Scholarship ==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Arbuckle, Alyssa, and John Maxwell. (2019). “Modelling Open Social Scholarship Within the INKE Community.” ''KULA: Knowledge Creation, Dissemination, and Preservation Studies'' 3 (1), 1–8. https://doi.org/10.5334/kula.15&lt;nowiki/&gt;.'''
&lt;/div&gt;

Moves “beyond open access” toward OSS practice by reworking scholarly communication workflows around collaboration, transparency, and community needs. Emphasizes infrastructure choices and governance as sites where values are enacted. Gives concrete criteria for participatory infrastructures and power‑sharing in scholarly communication; helpful to evaluate platform design choices.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Arbuckle, Alyssa, Ray Siemens, Jon Bath, Constance Crompton, Laura Estill, Tanja Niemann, Jon Saklofske, and Lynne Siemens. 2022. “An Open Social Scholarship Path for the Humanities.” ''Journal of Electronic Publishing'' 25 (2). https://doi.org/10.3998/jep.1973&lt;nowiki/&gt;.'''
&lt;/div&gt;

A concise, peer‑reviewed articulation of open social scholarship (OSS) from INKE/ETCL leaders, translating principles into programs of action: public engagement, community training, policy, and infrastructure. Provides a normative baseline to assess whether platforms and practices foster dialogic exchange and mutuality rather than extraction.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Arthur, Paul L., Lyida Hearn, Lucy Montgomery, Hugh Craig, Alyssa Arbuckle, and Ray Siemens. 2021. “Open Scholarship in Australia: A Review of Needs, Barriers, and Opportunities.” ''Digital Scholarship in the Humanities'', 36 (4): 795–812. https://doi.org/10.1093/llc/fqaa063&lt;nowiki/&gt;.'''
&lt;/div&gt;

Peer‑reviewed assessment from CA‑Aus collaborators surfaces structural barriers (policy, incentives, infrastructure) and opportunities for publicly engaged open scholarship. Frames how national policy, incentives, and infrastructure shape whether openness reduces or reproduces inequities.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''El Khatib, Randa, Lindsey Seatter, Tracey El Hajj, Conrad Leibel, Alyssa Arbuckle, Ray Siemens, Caroline Winter, and the ETCL and INKE Research Groups. 2019. “Open Social Scholarship Annotated Bibliography.” ''KULA'' 3 (1): 1–141. https://doi.org/10.5334/kula.58&lt;nowiki/&gt;.'''
&lt;/div&gt;

Field‑defining synthesis of OSS foundations, surveying open access, participatory publishing, crowdsourcing, social knowledge creation, and policy. Establishes terminology and exemplars that connect openness with social responsibility. Defines a master index to map subdomains of openness and identify non‑AI precedents for care, accessibility, and accountability in scholarly infrastructures.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Maxwell, John W. 2015. “Beyond Open Access to Open Publication and Open Scholarship.” ''Scholarly and Research Communication'' 6 (3): 1–10. https://doi.org/10.22230/src.2015v6n3a202&lt;nowiki/&gt;.'''
&lt;/div&gt;

Argues that simply “access” is insufficient; emphasizes usability, participatory review, and community‑responsive publishing workflows. Repositions openness as an ecosystem of practices with embedded care and accountability. Yields criteria for evaluating whether “openness” translates to meaningful, non‑extractive participation and shared authority in knowledge production.

{{Navigation|previous=Introduction|next=AI and Open}}

{{BookCat}}</text>
      <sha1>29m8xjzsv1b92r8bixiu32khqnxbl99</sha1>
    </revision>
  </page>
  <page>
    <title>Taking Bearings: Artificial Intelligence in Knowledge Platforms and Open, Social Scholarship/AI and Open</title>
    <ns>0</ns>
    <id>483503</id>
    <revision>
      <id>4656124</id>
      <parentid>4655930</parentid>
      <timestamp>2026-08-02T21:51:48Z</timestamp>
      <contributor>
        <username>CorreiaA</username>
        <id>3614427</id>
      </contributor>
      <minor />
      <origin>4656124</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="47715" sha1="ppxc30bhf03j6xexijk23fky8bkrjmy" xml:space="preserve">== Open Access ==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Kember, Sarah, and Amy Brand. 2023. “The Corporate Capture of Open-Access Publishing.” ''The Chronicle of Higher Education'', August 16. https://www.chronicle.com/article/the-corporate-capture-of-open-access-publishing. '''
&lt;/div&gt;

Kember and Brand highlight that open access policies adopted to increase availability of publicly funded research “may unintentionally contribute to greater consolidation in academic publishing” by encouraging commercial publishers to “value quantity over quality and platforms over people.” Kember and Brand use the history of “corporate capture” as a guide, referencing the development of self-archiving practices into a “neoliberal framework” of “openness at any cost.” Open-access reforms which targeted academic publishing as a “monolithic… bad actor” enabled this by hurting small actors more than major commercial entities, which exploited their vulnerability. Since then, the largest publishers have initiated hybrid subscription models to charge more overall, or “Read-and-Publish” deals that are increasingly expensive, decimate shrinking library budgets, and reinforce inequities in authorship. Kember and Brand argue this process was driven by ignorance, error, and the ideology of “immediate interest,” where short term gains are prioritized. The neoliberal idea that “information wants to be free” is similarly “subjugating all values to those of the market,” as open-access policy “inherits a utopia and risks delivering a dystopia” by making vast amounts of linked data readily accessible to third parties. The answer lies in a network of non-profit, fair-profit, and international organizations, which could turn the “false promise of openness into truly public knowledge.”

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Luth, Eric. 2025. “The Use of Wikipedia, Wikimedia, and Open Access Content for Artificial Intelligence and Text and Data Mining.” ''Stockholm IP Law Review'' 6 (1): 109–138. https://doi.org/10.53292/33313cc8.be33e111&lt;nowiki/&gt;.'''
&lt;/div&gt;

Luth examines how Digital Commons stakeholders such as Wikimedia influence the development of AI models trained on Creative Commons (CC) licensed content. He argues that while these resources are essential for AI training, AI developers’ compliance with license conditions is often uncertain, and some AI developers may bypass legal requirements. Luth highlights two strategies: using CC licenses to protect shared knowledge and collaborating to sustain the ecosystem of open access. By combining these approaches, stakeholders can support high-quality AI outputs while preserving the integrity of the Digital Commons. The article emphasizes that AI’s reliance on shared resources carries ethical and practical responsibilities and shows how open licensing can enhance the reliability and social value of AI.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Pooley, Jefferson. 2024. &quot;Large Language Publishing: The Scholarly Publishing Oligopoly's Bet on AI.&quot; ''KULA: Knowledge Creation, Dissemination, and Preservation Studies'' 7 (1): 1–11. https://doi.org/10.18357/kula.291&lt;nowiki/&gt;.'''
&lt;/div&gt;

Pooley begins with the Microsoft–OpenAI vs. New York Times clash to show how both journalism and scholarly publishing are positioning themselves to charge AI firms for using their content. He notes, however, that journalism and academic publishing differ fundamentally: news organizations pay their writers, while scholarly publishers rely on research produced for free by academics or funded by taxpayers. Pooley criticizes commercial publishers for framing AI companies as “free-riders” even though those publishers themselves profit from vast unpaid scholarly labour. To clarify, the author uses the notion of  &quot;surveillance capitalism” (using behavioural data to “feed predictive models” and sell it to customers, i.e., Facebook, Google, Silicon Valley) and states that unlike big tech companies in which “if you do not pay you are the product,” publishing companies like Elsevier use researchers both as product and paying customers in “Surveillance publishing.” This allows the “data cartels” to feed predictive models and turn academics' data into a product, which is quietly sold to tech companies without the academics’ knowledge in a process Pooley calls “academic fracking.” Even open-access work is often restricted or enclosed within proprietary platforms that enable further data extraction. Pooley urges academics to push back now and campaign, before these companies fully extend their surveillance-driven business models into AI and continue monetizing scholarly work and researcher behaviour without accountability.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Smith, Regan. 2025. “Licensing of Text for Generative AI: Learnings from Non-AI Licensing Practices.” ''The Columbia Journal of Law &amp; the Arts'' 48 (4): 457–512. https://doi.org/10.52214/jla.v48i4.13926&lt;nowiki/&gt;.'''
&lt;/div&gt;

This article provides an overview of the challenges and opportunities of licensing textual content for generative AI, analyzing how existing open-access licenses (CC BY, CC BY-SA, CC0) perform in machine learning contexts. The author argues that most licenses were drafted without anticipating large-scale AI training or synthetic output generation, highlighting gaps in coverage while noting that marketplace solutions (through negotiated deals with publishers or voluntary collective management organizations—CMOs) are already emerging. The piece emphasizes that AI developers and rightsholders can collaboratively experiment with licensing arrangements, scaling compliance and business operations to mitigate risk, rather than relying on rigid, government-mandated frameworks. The author proposes that machine-readable licensing provisions, including TDM opt-out signals and provenance-tracking requirements, should become standard features of scholarly communication infrastructure, and engages with the question of whether OA constitutes a commons governed by norms of reciprocity or a reservoir open to private capture, examining case law around &quot;fair use&quot; defences for training data and the adequacy of attribution mechanisms when source texts are statistically blended beyond recognition.

== Open Data ==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Bender, Emily M., and Batya Friedman. 2018. “Data Statements for Natural Language Processing: Toward Mitigating System Bias and Enabling Better Science.” ''Transactions of the Association for Computational Linguistics'' 6: 587–604. https://doi.org/10.1162/tacl_a_00041.'''
&lt;/div&gt;

The authors propose data statements as a design intervention to reduce exclusion and bias in language technologies, particularly in NLP, arguing that such documentation can prevent misrepresentation and support more ethical and accurate system development. They define a data statement as a “critical enabling infrastructure” that helps developers understand how results may generalize, how systems should be deployed, and what biases might be present. Their recommended schema includes a detailed, long-form account (covering curation methods, language variety, speaker and annotator demographics, context of speech or text, and recording or text quality) and a short form that should accompany any publication using the dataset. Using two case studies, they demonstrate how this schema works in practice and conclude that without a field-wide commitment to this practice, efforts to confront bias will be severely weakened, whereas widespread adoption would immediately clarify representational limits and, over time, foster more inclusive datasets and value-sensitive research.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Boyd, Karen. 2021. “Datasheets for Datasets Help ML Engineers Notice and Understand Ethical Issues in Training Data.” ''Proceedings of the ACM on Human-Computer Interaction'' 5 (CSCW2): 1–27. https://doi.org/10.1145/3479582.'''
&lt;/div&gt;

Boyd explores how documentation frameworks such as “Datasheets for Datasets” function in practice for machine learning engineers, showing that open access to data alone does not ensure ethical or responsible AI development. Through think-aloud sessions with 23 practitioners, Boyd demonstrates that engineers who received a Datasheet identified ethical issues earlier and more frequently than those who did not, proving that documentation can actively shape how practitioners recognize, interpret, and respond to potential ethical issues in training data. Framing the analysis through the concept of ethical sensitivity (recognition, particularization, and judgment), Boyd argues that practices focused on structured interventions could increase ethical awareness, like datasheets that could serve as an infrastructure for ethical engagement, prompting engineers to reflect on dataset provenance, demographic representation, and the broader consequences of data reuse, factors often hidden or overlooked in open data environments. This study challenges the assumption that openness automatically leads to fairer AI systems. By offering empirical evidence of how documentation scaffolds ethical decision-making, the author makes a compelling case for embedding such practices throughout AI, especially as machine learning systems increasingly rely on openly available and ethically complicated data.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Carroll, Stephanie Russo, Edit Herczog, Māui Hudson, Keith Russell, and Shelley Stall. 2021. “Operationalizing the CARE and FAIR Principles for Indigenous Data Futures.” ''Scientific Data'' 8: 108. https://doi.org/10.1038/s41597-021-00892-0.'''
&lt;/div&gt;

Carroll et al. discuss how the FAIR (Findable, Accessible, Interoperable, and Reusable) principles for scientific data and CARE (Collective Benefit, Authority to Control, Responsibility, and Ethics) principles for Indigenous Data Governance can be operationalized to allow Indigenous Peoples’ Rights to control their data, especially as big data and open data increase access to large datasets. The authors consider that the two sets of principles can be complimentary, both for scientific data and for data created by or about Indigenous Peoples. Scientific data can benefit from the CARE principles because many scientific datasets contain Indigenous Knowledge and these datasets can be oriented in ways that enhance the wellbeing of people by recording provenance and using appropriate governance models. Similarly, Indigenous Data can benefit from the FAIR principles to make data interoperable, regardless of the source or underlying technology, even if the datasets cannot be made openly accessible. The authors provide some recommendations to operationalize FAIR principles with CARE by making Indigenous data FAIR, raising awareness of the CARE principles among the research community before engaging with Indigenous data, and testing ways to use CARE principles for Indigenous data.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Carroll, Stephanie Russo, Ibrahim Garba, Óscar Luis Figueroa Rodríguez, Jarita Holbrook, and Raymond Lovett. 2020. “The CARE Principles for Indigenous Data Governance.” ''Data Science Journal'' 19 (1): 43. https://doi.org/10.5334/dsj-2020-043.'''
&lt;/div&gt;

The authors ground the article in the structural biases embedded in data ecosystems and the ongoing processes of colonization that have produced epistemicide and constrained Indigenous Peoples’ ability to sustain their knowledges. They highlight how inequities operate across digital infrastructures and institutions, while Indigenous knowledge systems already engage with this complexity. The article directly refers to the tension between Indigenous Data Sovereignty and the data demands of AI, machine learning, and big data initiatives, noting that secondary data use and broad data sharing can threaten Indigenous rights, consent, and collective interests. Within this context, the Indigenous-led development of the CARE principles (Collective Benefit, Authority to Control, Responsibility, and Ethics) is discussed as a value-based response to concerns about the secondary use and reuse of Indigenous data. It highlights that open data for AI training is not a merely technical matter, but a political one, where broad data sharing and algorithmic extraction can underscore Indigenous rights, consent, and collective interests. By articulating CARE, authors argue for frameworks that centre people and purpose rather than solely data accessibility or system performance. The paper concludes that reclaiming control of data and data narratives shifts Indigenous Peoples from being subjects and invisible within data systems to self-determining users who shape governance, policy, ethics, and innovation in ways aligned with collective benefit and equity.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Heger, Amy, Liz B. Marquis, Mihaela Vorvoreanu, Hanna Wallach, and Jennifer Wortman Vaughan. 2022. “Understanding Machine Learning Practitioners' Data Documentation Perceptions, Needs, Challenges, and Desiderata.” ''Proceedings of the ACM on Human-Computer Interaction'' 6 (CSCW2): 1–29. https://doi.org/10.1145/3555760.'''
&lt;/div&gt;

Heger et al. (2022) examine whether existing data documentation frameworks actually meet the needs of machine learning (ML) practitioners, a crucial issue given that AI models now shape high-stakes decisions across disciplines and depend heavily on the quality and transparency of their training data. The authors argue that while documentation initiatives like Datasheets for Datasets aim to support responsible and transparent AI, little is known about how these tools function in industry settings, where workflows, pressures, and data types differ substantially from academic contexts. Through semi-structured interviews and a documentation exercise with 14 practitioners, they find that current documentation practices are largely ad hoc, narrow in scope, and often disconnected from responsible AI concerns. Participants struggled to understand the purpose of many documentation questions, were unsure of appropriate granularity, and often failed to recognize the ethical implications of dataset characteristics. Their findings reveal a significant gap between responsible AI ideals and everyday ML practices. The study provides evidence that documentation frameworks must be contextual, integrated into existing tools, and supported by actionable guidance if they are to prevent downstream harms. By deriving seven design requirements, the authors offer concrete directions for developing documentation standards that can support safer, more accountable open AI data practices.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Huerta, E. A., Ben Blaiszik, L. Catherine Brinson, Kristofer E. Bouchard, D. Díaz, et al. 2023. “FAIR for AI: An Interdisciplinary and International Community Building Perspective.” ''Scientific Data'' 10: 487. https://doi.org/10.1038/s41597-023-02298-6&lt;nowiki/&gt;.'''
&lt;/div&gt;

Huerta et al. (2023) survey a wide landscape of US and European initiatives defining the FAIR (Findable, Accessible, Interoperable, Reusable) principles for AI models, arguing that responsible AI requires more than open access, it requires infrastructures that make AI assets understandable, comparable, and genuinely reusable. Their main argument is that FAIR must be reinterpreted for AI because models, software, and workflows are now “first-class” research objects, and only coordinated, community-wide standards can support interpretability, reproducibility, and sustainable open science. By mapping dozens of large, interdisciplinary FAIR-for-AI efforts, the authors show how FAIRness enables cross-disciplinary model reuse, transparent benchmarking, and educational access, ultimately laying groundwork for foundation models built from FAIR, AI-ready datasets. The paper highlights a major gap in current AI openness debates: open access alone does not ensure usable, trustworthy, or equitable AI. The authors demonstrate that without shared metadata standards, integrated repositories, and long-term infrastructure, openness can fragment into silos that impede scientific discovery. Their community-focused perspective invites readers to see FAIR not as a bureaucratic checklist but as an evolving, collaborative project essential for scaling transparent, reusable AI across scientific domains.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Taeihagh, Araz. 2025. “Governance of Generative AI.” ''Policy and Society'' 44 (1): 1–14. https://doi.org/10.1093/polsoc/puaf001.'''
&lt;/div&gt;

Taeihagh’s work takes on the evolving governance challenges surrounding generative AI, particularly the way its vast training data demands have injected new urgency into long-running debates over open data governance. Unlike rule-based AI systems designed for fixed, pre-specified tasks, generative models train on expansive datasets and produce novel outputs. The author argues that this reshapes the very terrain of risk. This shift invites distinct concerns: hallucination, jailbreak, exposure of sensitive information, accuracy failures, opacity, and the general difficulty of control. Taeihagh not only details how these risks emerge from the technical properties of generative systems but also proposes a governance framework that maps potential interventions to each category of risk and explores the institutional supports required to make such interventions effective. The framework is especially instructive for today’s AI data-governance debates, where the scale and unpredictability of generative models are compelling policy-makers to rethink what openness should entail, whose interests it advances, and how governance mechanisms can guard against extractive data practices while steering AI development toward public values.

== Open Source ==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Bostrom, Nick. 2017. “Strategic Implications of Openness in AI Development.” ''Global Policy'' 8 (2): 135–148. https://doi.org/10.1111/1758-5899.12403&lt;nowiki/&gt;.'''
&lt;/div&gt;

This article is a cross-section that surveys the notion of openness in AI development before proprietary AI models entered the market, observing  the early approaches of competing companies including Google, Facebook, and Microsoft, as well as OpenAI’s origins as a non-profit organization—OpenAI now operates as a capped-profit company governed by a non-profit, functioning effectively as a for-profit public benefit corporation rather than a publicly traded entity. The article focuses on long-term moves toward openness and their implications, but also briefly considers the benefits and problems inherent in short- and medium-term openness: Bostrom speculates that too much openness runs the risk of curbing corporate (and therefore funding) interest, ultimately slowing the rate of AI’s technological progress. However, he also asks: “Supposing openness would speed technical progress and rollout of AI capabilities, would that be socially beneficial?” (137). Bostrom notes a number of concerns ranging from public safety to labour encroachment, but still suggests that openness in AI development would be a net positive that accelerates the rate of technological progress in the short and middle-term. In the article’s long term section, Bostrom considers multiple scenarios in which openness might either help or hinder the safety and progress of a general AI superintelligence. He identifies distinct forms of openness (Science and Source Code; Control Methods and Risk Analysis; Capabilities and Expectations; and Values, Goals, and Governance Structures), addressing the potential value of openness in each, and argues that while openness is generally positive, especially in issues of values and safety, sharing too much knowledge may increase the odds someone will abuse this technology or ignore safety. 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Cooper, Martin. 2023. “Open Source is Good for AI But, Is AI Good for Open Source?” ''ITNOW'' 65 (2): 50–51. https://doi.org/10.1093/combul/bwad062&lt;nowiki/&gt;.'''
&lt;/div&gt;

Cooper shares Terence Eden's perspectives on the evolving relationship between artificial intelligence and the open source movement, ultimately raising ethical and practical concerns about attribution and authorship in the age of AI-generated code. Eden believes that open source promotes technologies like AI, cloud, and the internet, driving efficiency, reducing duplication, and advancing scientific discovery. He raises an issue with AI’s use of open source without proper attribution violating one of open source’s core principles: crediting the original creator. Despite acknowledging that AI can assist developers and make programming more accessible, Eden cautions against viewing AI as a substitute for genuine understanding or creativity. Ultimately, Eden’s article is both a celebration and a warning: open source has empowered AI, but unless attribution and ethical use are safeguarded, AI may erode the very openness and integrity that made its success possible. 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Guo, Xinwei, Yujun Li, Yafeng Peng, and Xuetao Wei. 2024. “Copyleft for Alleviating AIGC Copyright Dilemma: What-if Analysis, Public Perception and Implications.” Preprint, ''arXiv'', February 19. https://arxiv.org/abs/2402.12216. '''
&lt;/div&gt;

This article analyzes and summarizes copyright disputes related to Artificial Intelligence Generated Content (AIGC) and isolates three primary stakeholders within these disputes: data owners, who create the content upon which AIGCs have been trained; model owners, who develop the AIGC applications and models (e.g., ChatGPT, Stable Diffusion, etc.) themselves; and model users, who apply prompts to AIGC models to generate content. The authors consider the benefits, challenges, and risks that arise from each given stakeholder making a claim to copyright while considering the potential benefits and challenges of embracing copyleft (i.e., granting free use over material so long as the products of that free use are also under copyleft). In their contemplation of each stakeholder, they recognize the benefits for each group in advocating copyright to content, but also identify harm to other stakeholders, society, progress in developing AIGC, and institutions (e.g., “the copyright registration system”). The authors consider three real-life cases surrounding copyright disputes and envision how copyleft would effectively alleviate the disputes and tension surrounding their different stakeholders. The last half of the article performs a survey that asks users who have a range of familiarity with AIGC a range of questions, including who ought to have copyright claims to a generated image of the Mona Lisa in the style of Vincent Van Gogh. The authors note that their survey indicates consistent ambivalence, misunderstanding, and concern over copyright issues related to AIGC. The survey identified that there is support for applying copyleft to AIGC, and that that support increases the more someone understands the issues surrounding AIGC and copyright. 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Osborne, Cailean. 2024. “Why Companies &quot;Democratise&quot; Artificial Intelligence: The Case of Open Source Software Donations.” Preprint, ''arXiv'', September 26. https://doi.org/10.48550/ARXIV.2409.17876&lt;nowiki/&gt;.'''
&lt;/div&gt;

Osborne aims to advance the &quot;nascent research agenda on the political economy of open source AI&quot; by studying various corporate AI OSS donations to non-profit foundations and thereby sourcing and explaining corporate incentives behind their &quot;democratization&quot; of AI. He firstly outlines this topic in detail, clarifying that the technology required to access AI is expensive, and developing AI even more so, meaning this &quot;democratization&quot; represents only a lowering rather than removal of barriers. Osborne then considers the possible incentives behind organizational level decisions to democratize AI, as companies seek to competitively dominate industry norms, test and improve their products, enlarge intellectual property, reduce R&amp;D costs, and focus external research into their own AI. Significantly, individual developers of open source software do not have the same incentives but tend to accept commercial participation. On one hand, corporate participation means volunteers will be contributing toward these sources of corporate profit without reward; on the other hand, it risks companies dominating open research spaces and developing a complex intercompany research network of &quot;co-opetition&quot; which individual volunteers cannot enter. Therefore, Osborne’s study is highly relevant to issues of commercialization and open scholarship and especially concerns of “open-washing.” The study’s results highlight the predominantly commercial incentives behind corporate “AI democratisation” efforts, appropriately mirroring its most common form—the democratization of governance. However, Osborne's results also illustrate the significance of the individual level, “bottom-up” movement, suggesting that a significant 38% of decisions to donate stemmed from developers. Despite this, he concludes that “AI democratization” is indeed “a strategic calculation, where companies relinquish control of their OSS project in exchange for assumed benefits,” as “democratisation of governance is treated as a social means for primarily economic and technological ends,” broadly supporting the works of Widder et al. and Srnicek, and encouraging other researchers to bring their attention to this area. 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Radu, Roxana. 2021. “Steering the Governance of Artificial Intelligence: National Strategies in Perspective.” ''Policy and Society'' 40 (2): 178–193. https://doi.org/10.1080/14494035.2021.1929728.'''
&lt;/div&gt;

This article provides a survey and analysis of the national strategies related to AI implemented by a dozen countries around the world. It is of particular interest to those interested in concrete policies and regulations surrounding AI rather than discourse and rhetoric. Radu identifies a tension between nations claiming to take a leadership role and corporations that are “driving developments in the field.” More specifically, she observes that the vast “majority of binding agreements and voluntary commitments” come from corporations rather than nations or government regulatory bodies, indicating a concerning trend toward self-regulation. Governments have often played a key role in facilitating the conditions in which the development of AI technologies have thrived, even funding the rudimentary research that leads to AI models and applications, and this article notes that, regardless of the level of government regulation, the state is rarely a passive player when it comes to AI. Radu identifies the trend of a “dominant place for industry in the drafting process” and that representatives from industry make up a third of members drafting national strategies as well as prominent positions within those groups. Radu also notes absences: for instance, despite more than seventy countries using AI for surveillance, this issue is conspicuously absent from most strategies. Radu concludes that the common thread among many of these strategies is a hybridity between industry and state that affirms “the deliberate choice for functional indetermination,” resulting in a lack of clarity surrounding “who makes the rules and for how long,” and notes there are very few limitations placed on industry as these strategies instead provide vague ethical guidelines. 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Schmit, Cason, M. J. Doerr, and J. K. Wagner. 2023. “Leveraging IP for AI Governance.” ''Science'' 379 (6633): 646–647. https://doi.org/10.1126/science.add2202.'''
&lt;/div&gt;

This article proposes a hybrid AI copyright model that combines copyleft licensing and “patent trolling” in order to enforce an ethical approach to using AI models and training datasets. Schmit et al. contend that current legislation that applies to AI models and their use “are insufficient to impel ethical conduct” and require further consideration. The article advocates its hybrid model—Copyleft AI with Trusted Enforcement (CAITE)—as both rigorous and flexible, allowing for both self-reporting and monitoring. Essentially, the system works by creating an ecosystem in which AI models and training data are developed using copyleft, allowing for free use of these materials so long as the product of that use is covered by the same licensing agreement. At the same time, the enforcement of that licensing agreement is transferred to a regulatory entity called the CAITE Host, which acts as a positive counterpart to the patent troll, ensuring that no individual or organization breaches the terms of copyleft, introduces dangerous applications, data, or features, or unethically uses materials under the copyleft agreement. The CAITE Host and its code of ethics are driven by community oversight and buy-in, and the host is regulated by the community. The authors contend that its flexibility and bottom-up structure make CAITE uniquely suited to handling the rapidly developing field of AI and its shifting needs. Once CAITE achieves a critical mass, it would also become increasingly unlikely for AI developers to opt out. The article concludes by proposing a pilot model for CAITE, and strongly suggests that such a framework is far preferable for industry and others than stringent, relatively slow-moving, and inflexible government regulation in isolation. 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Shanklin, Grant, Cason Schmit, Jacob Pierce, Nicole Martinez-Martin, and Matthew DeCamp. 2025. “The Case for Contextual Copyleft: Licensing Open Source Training Data and Generative AI.” Preprint, ''arXiv'', July 17. https://arxiv.org/abs/2507.12713.'''
&lt;/div&gt;

This article introduces and describes a new form of content licensing, CCAI (Contextual Copyleft AI), designed to apply copyleft values and ethics to AI content, and should appeal to anyone interested in coding, copyright, and the (mis)use of training data for generative AI. The authors advocate for an approach that preserves the values of the Free and Open Source Software (FOSS) movement by using copyleft as a mechanism for the rights of AI content. The CCAI license requires that the free use and distribution of the software in question, that any work derived from that software must also be licensed under CCAI, and that CCAI software must “include source code or provide a way to access it.” The CCAI draws from and imitates other copyleft licenses but explicitly addresses and outlines the expectations regarding specific components of AI models within its license, applying copyleft and a requirement of openness to training data, code, and parameters. The article contends that whether it is easily demonstrable or not, clear guidelines of when training on publicly available data is and is not okay can act as a deterrent to misuse, and the CCAI license will give developers more agency in how others use their code, accelerate open source AI development by giving open source AI models open source training data only they can use, and limit the practice of open washing—claims that software and AI is open source when it is not (or not fully open source). The authors admit there are security risks that come with open AI models (e.g., vulnerabilities to malicious actors), but they contend that the benefits far outweigh those risks, especially when accompanied by the implementation of the CCAI and complementary regulations. 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Widder, David Gray, Dawn Nafus, Laura Dabbish, and James Herbsleb. 2022. “Limits and Possibilities for ‘Ethical AI’ in Open Source: A Study of Deepfakes.” In ''Proceedings of the 2022 ACM Conference on Fairness, Accountability, and Transparency (FAccT ’22)'', 2035–46. New York: Association for Computing Machinery. https://doi.org/10.1145/3531146.3533779.'''
&lt;/div&gt;

Widder et al. assert that significant understudied harms arise from divergent practices of “transparency and accountability” in the open source community. They argue that interventions designed for private companies may be improper for open source contexts, highlighting gaps in current approaches to “Ethical AI.” Their purpose is to reveal these systemic vulnerabilities and propose frameworks that better address the unique social and technical dynamics of open source development. They use an open source Deepfake creation tool as an extreme case to highlight how ethical reasoning intersects with broader cultural frameworks and interview project leaders. In this case study, researchers offer a definition of “Down stream control assumptions,” suggesting that “Ethical AI” research and “design interventions” would be improved by explicitly acknowledging these assumptions and identifying ways to work effectively under weak assumptions of downstream control in open sources contexts.

== Open Science ==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Ación, Laura, Mariela Rajngewerc, Gregory Randall, and Lorena Etcheverry. 2023. “Generative AI Poses Ethical Challenges for Open Science.” ''Nature Human Behaviour'' 7 (12): 1800–1801. https://doi.org/10.1038/s41562-023-01740-4. '''
&lt;/div&gt;

This article explores the tension between Open Science’s need to make knowledge freely accessible and the rise in GenAI and its tendencies to use any information available to it without necessarily considering how its application of such information (including information made available through Open Science) may do harm. These “frictions,” as the authors describe them, point to Open Science’s need to make data available while ensuring said data is not used to do harm. It is a concise summary of the foundational issues at the heart of these conversations, and great for anyone interested in how GenAI complicates Open Knowledge. The authors propose selective licensing as one approach to curbing harm, but notes that this only protects against harm from direct use (e.g., “open-source code used to build a weapon”) and not an indirect use (e.g., “open-source library use within another algorithm that is in itself harmful”). Ultimately, they stress the need for new governance systems and regulations related to the creation of knowledge that prioritizes both the public good and right to research.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Baltes, Sebastian, Florian Angermeir, Chetan Arora, Preetha Chatterjee, Jens Deitenbeck, Daniel Graziotin, Christoph Treude, et al. 2025. “Guidelines for Empirical Studies in Software Engineering Involving Large Language Models.” Preprint, ''arXiv'', August 21. https://arxiv.org/abs/2508.15503. '''
&lt;/div&gt;

This article develops best practices and guidelines for the use of LLMs (expressly language LLMs, not image, audio, or video) for empirical studies in software engineering (expressly data collection, processing, and analysis). The authors aim to “enable reproducibility and replicability” in the field even when LLMs are in use and “produce more reliable evidence on what LLM can and cannot deliver.” They present what they call a “taxonomy of Study Types” in addition to their guidelines, providing examples both within and beyond software engineering, all aimed at promoting the use of LLMs while promoting open science practices. The article considers LLMs as annotators, judges, synthesizers, and subjects in SE, and the guidelines Baltes et al. present have two tiers, MUST and SHOULD, demonstrating a nuanced understanding of practices without which SE research employing LLMs is rendered ineffective (e.g., declaring an LLM’s usage and role) and those practices that merely make this sort of research more rigorous and accessible (e.g., including full interaction logs if privacy and confidentiality can be ensured). The authors advocate for these practices to better enable researchers in SE to engage with LLMs while practicing Open Science. Of particular interest is the way in which the authors structure their understanding of the field and guidelines, and how they recognize distinct studies require slightly different practices.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Biderman, Stella, Hailey Schoelkopf, Quentin Anthony, Herbie Bradley, Kyle O'Brien, Eric Hallahan, Mohammad Aflah Khan, et al. 2022. “EleutherAI: Going Beyond ‘Open Science’ to ‘Science in the Open.’” Preprint, ''arXiv'', October 12. https://arxiv.org/abs/2210.06413. '''
&lt;/div&gt;

This article outlines the inception and progress of EleutherAI, a lab and AI model first founded in 2020 by a group of (for the most part) university affiliated academics and researchers concerned that for-profit companies are the primary developers of GenAI research and models, and that there is a lack of transparency and openness related to these technologies. Those interested in alternative approaches to AI models or a concrete example of Open Science in action should read this article. Because these researchers want to make available a “capable large language model… for public use, study, and scrutiny,” they have conducted all EleutherAI research in the open, making it freely accessible to everyone (1): all research and discussions take place on Discord servers, and projects coordinated and teams assembled in those servers on a grassroots basis. This “public-facing research” leads to a “virtuous cycle” with little turnaround between the conception of ideas and development of projects, and facilitates conversation, collaboration, and community by giving all users, even newcomers, unfettered access to every means of communication in which the group engages. The authors consider the downsides to such an approach as well, citing the issues of relying on volunteer labour, how others might take this public research for their own without proper accreditation to EleutherAI, and the important consideration that perhaps not all things should be made public, but ultimately conclude that such open research is integral to the academic community.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Gundersen, Odd Erik, Odd Cappelen, Martin Mølnå, and Nicklas Grimstad Nilsen. 2024. “The Unreasonable Effectiveness of Open Science in AI: A Replication Study.” Preprint, ''arXiv'', December 20. https://doi.org/10.48550/ARXIV.2412.17859. '''
&lt;/div&gt;

Gundersen et al. examine the extent to which a widely accepted crisis in research reproducibility affects AI research. They do this by conducting a systematic replication study of thirty highly cited AI studies, allowing the authors to identify the problems with irreproducibility. Out of the gate, the replication process could only be attempted with twenty-two of these studies because their research data needed to be openly available and reproducible without special hardware. Furthermore, the twenty-two replications were each given forty working hours of effort, but twelve of these took too long and had to be stopped early, impacting their quality. In result, it was found that out of the twenty-two replication attempts began only six could be accurately reproduced and five partially reproduced, meaning a 50% success rate. The main problems for reproducibility were identified in six sources: the &quot;source code,&quot; &quot;article,&quot; &quot;data,&quot; &quot;results,&quot; and &quot;resources.&quot; Notably, each of the six accurate reproductions had code available, and the one other study with available code was a partial success limited by the time constraint, meaning availability of code alongside the data certainly improved the quality of the replication and was the most important factor for success. Therefore, despite limitations of a small sample size and time constraints, Gundersen et al. found that AI research’s reproducibility climbs from 33% accuracy when only data is available to 86% when both code and data are available. This is a significant enough result to empirically demonstrate the benefits of mandating openness and transparency of code as well as data. 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Helregel, N. 2025. “AI and Open Science: Implications and Library Practice Recommendations.” ''Library Trends'' 73 (3). https://doi.org/10.1353/lib.2025.a961191. '''
&lt;/div&gt;

Helregel (2025) examines the complex intersection of artificial intelligence and the open science movement, questioning whether current AI technologies possess the necessary transparency to align with open research principles. The article explores multiple dimensions of this relationship, assessing both the potential for AI to actively advance open science goals and the broader impacts of AI adoption on the attitudes and behaviours of researchers and the public. Recognizing the critical role of library and information science professionals in navigating this shifting landscape, Helregel outlines concrete recommendations for institutional library practice. These actionable strategies include prioritizing internal knowledge-building, fostering cross-institutional advocacy, adapting consultation and liaison workflows, navigating complex licensing agreements, and enhancing science communication. Ultimately, the paper positions libraries as vital infrastructure for ensuring that AI integration supports, rather than undermines, the core tenets of transparency, reproducibility, and accessibility in scholarly communication.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Hosseini, Mohammad, Serge P. J. M. Horbach, Kristi Holmes, Tony Ross-Hellauer. 2025 “Open Science at the generative AI turn: An exploratory analysis of challenges and opportunities.” ''Quantitative Science Studies'' 6: 22–45. https://doi.org/10.1162/qss_a_00337. '''
&lt;/div&gt;

Hosseini et al. provide an overview of the potential benefits and downsides of incorporating generative AI into different open science practices, as defined by the UNESCO Recommendation on Open Science, particularly open access, open data, open source software, open evaluation, open science infrastructures, open engagement of societal actors, and open dialogue with other knowledge systems. Some common benefits across these practices are that generative AI has the potential to lower the barriers to participation in science, summarize academic literature for non-academic audiences, and simplify processes in coding and data management. However, the authors also warn about the potential risks, including the creation and spread of misinformation, the propagation of hegemonic worldviews, and the monetization of research information. Given these downsides and the high social and ecological costs of generative AI, the authors suggest researchers question if AI tools are the most efficient way of achieving openness in science. The final section of the paper includes further recommendations for institutions, funders, and publishers, such as providing training on the use of generative AI, monitoring its positive and negative impacts, and continuing testing its use for evaluation and assessment purposes.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Linåker, Johan, Cailean Osborne, Jennifer Ding, Daniel Puttick, and Richard Nweibo. 2025. “A Cartography of Open Collaboration in Open Source AI: Mapping Practices, Motivations, and Governance in 14 Open Large Language Model Projects.” Preprint, ''arXiv'', September 29. https://arxiv.org/abs/2509.25397&lt;nowiki/&gt;.'''
&lt;/div&gt;

This article engages in a survey and interviews of the practices, motivations, and governance of fourteen open LLMs with the aim of further enabling collaboration throughout the open LLM lifecycle. The essay provides an overview of terms for open AI and major takeaways and challenges for different types of collaboration—types of collaboration include model, data, software, evaluation, non-technical, and compute—at the pre-training, post-training, and post-release stages of the LLM lifecycle. The authors also identify five governance frameworks for open LLM projects ranging from single companies to “non-profit-sponsored grassroots projects.” The authors opine that collaboration does not merely happen with LLMs themselves but the infrastructure and accompanying tools (e.g., datasets, open source frameworks, discussion fora, etc.) needed to produce and maintain them, and more research and attention needs to be given to the ecosystem surrounding LLMs. The article also includes recommendations “to support the global community of practitioners building a more open future for AI” for researchers and developers, AI companies, policy-makers, academic institutions, platform providers, and open source foundations. For instance, they recommend that policy-makers fund infrastructure of public AI, not just specific models, use targeted initiatives to support regional languages, require publicly funded research to use licensing that aligns with open science principles, and insist on a clear definition of what constitutes openness in these cases (36).

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Papi, Sara, Marco Gaido, Luisa Bentivogli, and Matteo Negri. 2025. “FAMA: The First Large-Scale Open-Science Speech Foundation Model for English and Italian.” Preprint, ''arXiv'', May 28. https://arxiv.org/abs/2505.22759&lt;nowiki/&gt;.'''
&lt;/div&gt;

This article presents an Open Science Speech Foundation Model (SFM) called FAMA, “the first family of large-scale open-science SFMs for English and Italian trained on over 150k hours of exclusively OS-compliant speech data.” FAMA’s results are comparable to its closed counterparts and considerably faster (up to 8 times). The authors present a brief summary of recent advancements in automatic speech recognition and speech translation while raising concerns about the closed nature of related applications’ training data and code and pointing to open source alternatives in different domains for inspiration. The majority of the article is dedicated to specifics of architecture, training, and results of FAMA compared to its competitors; however, the end result—that FAMA is competitive with and even outperforms its larger, non-open counterparts like OpenAI’s Whisper in some cases—is an excellent case study in how open science can work in the domain of LLMs and AI.

{{Navigation|previous=Essential Contexts|next=AI and Social}}

{{BookCat}}</text>
      <sha1>ppxc30bhf03j6xexijk23fky8bkrjmy</sha1>
    </revision>
    <revision>
      <id>4656128</id>
      <parentid>4656124</parentid>
      <timestamp>2026-08-02T22:13:46Z</timestamp>
      <contributor>
        <username>CorreiaA</username>
        <id>3614427</id>
      </contributor>
      <minor />
      <origin>4656128</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="47684" sha1="ama4epzgu5vk6n6oi7jn1lsi1956v2j" xml:space="preserve">== Open Access ==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Kember, Sarah, and Amy Brand. 2023. “The Corporate Capture of Open-Access Publishing.” ''The Chronicle of Higher Education'', August 16. https://www.chronicle.com/article/the-corporate-capture-of-open-access-publishing. '''
&lt;/div&gt;

Kember and Brand highlight that open access policies adopted to increase availability of publicly funded research “may unintentionally contribute to greater consolidation in academic publishing” by encouraging commercial publishers to “value quantity over quality and platforms over people.” Kember and Brand use the history of “corporate capture” as a guide, referencing the development of self-archiving practices into a “neoliberal framework” of “openness at any cost.” Open-access reforms which targeted academic publishing as a “monolithic… bad actor” enabled this by hurting small actors more than major commercial entities, which exploited their vulnerability. Since then, the largest publishers have initiated hybrid subscription models to charge more overall, or “Read-and-Publish” deals that are increasingly expensive, decimate shrinking library budgets, and reinforce inequities in authorship. Kember and Brand argue this process was driven by ignorance, error, and the ideology of “immediate interest,” where short term gains are prioritized. The neoliberal idea that “information wants to be free” is similarly “subjugating all values to those of the market,” as open-access policy “inherits a utopia and risks delivering a dystopia” by making vast amounts of linked data readily accessible to third parties. The answer lies in a network of non-profit, fair-profit, and international organizations, which could turn the “false promise of openness into truly public knowledge.”

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Luth, Eric. 2025. “The Use of Wikipedia, Wikimedia, and Open Access Content for Artificial Intelligence and Text and Data Mining.” ''Stockholm IP Law Review'' 6 (1): 109–138. https://doi.org/10.53292/33313cc8.be33e111&lt;nowiki/&gt;.'''
&lt;/div&gt;

Luth examines how Digital Commons stakeholders such as Wikimedia influence the development of AI models trained on Creative Commons (CC) licensed content. He argues that while these resources are essential for AI training, AI developers’ compliance with license conditions is often uncertain, and some AI developers may bypass legal requirements. Luth highlights two strategies: using CC licenses to protect shared knowledge and collaborating to sustain the ecosystem of open access. By combining these approaches, stakeholders can support high-quality AI outputs while preserving the integrity of the Digital Commons. The article emphasizes that AI’s reliance on shared resources carries ethical and practical responsibilities and shows how open licensing can enhance the reliability and social value of AI.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Pooley, Jefferson. 2024. &quot;Large Language Publishing: The Scholarly Publishing Oligopoly's Bet on AI.&quot; ''KULA: Knowledge Creation, Dissemination, and Preservation Studies'' 7 (1): 1–11. https://doi.org/10.18357/kula.291&lt;nowiki/&gt;.'''
&lt;/div&gt;

Pooley begins with the Microsoft–OpenAI vs. New York Times clash to show how both journalism and scholarly publishing are positioning themselves to charge AI firms for using their content. He notes, however, that journalism and academic publishing differ fundamentally: news organizations pay their writers, while scholarly publishers rely on research produced for free by academics or funded by taxpayers. Pooley criticizes commercial publishers for framing AI companies as “free-riders” even though those publishers themselves profit from vast unpaid scholarly labour. To clarify, the author uses the notion of  &quot;surveillance capitalism” (using behavioural data to “feed predictive models” and sell it to customers, i.e., Facebook, Google, Silicon Valley) and states that unlike big tech companies in which “if you do not pay you are the product,” publishing companies like Elsevier use researchers both as product and paying customers in “Surveillance publishing.” This allows the “data cartels” to feed predictive models and turn academics' data into a product, which is quietly sold to tech companies without the academics’ knowledge in a process Pooley calls “academic fracking.” Even open-access work is often restricted or enclosed within proprietary platforms that enable further data extraction. Pooley urges academics to push back now and campaign, before these companies fully extend their surveillance-driven business models into AI and continue monetizing scholarly work and researcher behaviour without accountability.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Smith, Regan. 2025. “Licensing of Text for Generative AI: Learnings from Non-AI Licensing Practices.” ''The Columbia Journal of Law &amp; the Arts'' 48 (4): 457–512. https://doi.org/10.52214/jla.v48i4.13926&lt;nowiki/&gt;.'''
&lt;/div&gt;

This article provides an overview of the challenges and opportunities of licensing textual content for generative AI, analyzing how existing open-access licenses (CC BY, CC BY-SA, CC0) perform in machine learning contexts. The author argues that most licenses were drafted without anticipating large-scale AI training or synthetic output generation, highlighting gaps in coverage while noting that marketplace solutions (through negotiated deals with publishers or voluntary collective management organizations—CMOs) are already emerging. The piece emphasizes that AI developers and rightsholders can collaboratively experiment with licensing arrangements, scaling compliance and business operations to mitigate risk, rather than relying on rigid, government-mandated frameworks. The author proposes that machine-readable licensing provisions, including TDM opt-out signals and provenance-tracking requirements, should become standard features of scholarly communication infrastructure, and engages with the question of whether OA constitutes a commons governed by norms of reciprocity or a reservoir open to private capture, examining case law around &quot;fair use&quot; defences for training data and the adequacy of attribution mechanisms when source texts are statistically blended beyond recognition.

== Open Data ==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Bender, Emily M., and Batya Friedman. 2018. “Data Statements for Natural Language Processing: Toward Mitigating System Bias and Enabling Better Science.” ''Transactions of the Association for Computational Linguistics'' 6: 587–604. https://doi.org/10.1162/tacl_a_00041.'''
&lt;/div&gt;

The authors propose data statements as a design intervention to reduce exclusion and bias in language technologies, particularly in NLP, arguing that such documentation can prevent misrepresentation and support more ethical and accurate system development. They define a data statement as a “critical enabling infrastructure” that helps developers understand how results may generalize, how systems should be deployed, and what biases might be present. Their recommended schema includes a detailed, long-form account (covering curation methods, language variety, speaker and annotator demographics, context of speech or text, and recording or text quality) and a short form that should accompany any publication using the dataset. Using two case studies, they demonstrate how this schema works in practice and conclude that without a field-wide commitment to this practice, efforts to confront bias will be severely weakened, whereas widespread adoption would immediately clarify representational limits and, over time, foster more inclusive datasets and value-sensitive research.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Boyd, Karen. 2021. “Datasheets for Datasets Help ML Engineers Notice and Understand Ethical Issues in Training Data.” ''Proceedings of the ACM on Human-Computer Interaction'' 5 (CSCW2): 1–27. https://doi.org/10.1145/3479582.'''
&lt;/div&gt;

Boyd explores how documentation frameworks such as “Datasheets for Datasets” function in practice for machine learning engineers, showing that open access to data alone does not ensure ethical or responsible AI development. Through think-aloud sessions with 23 practitioners, Boyd demonstrates that engineers who received a Datasheet identified ethical issues earlier and more frequently than those who did not, proving that documentation can actively shape how practitioners recognize, interpret, and respond to potential ethical issues in training data. Framing the analysis through the concept of ethical sensitivity (recognition, particularization, and judgment), Boyd argues that practices focused on structured interventions could increase ethical awareness, like datasheets that could serve as an infrastructure for ethical engagement, prompting engineers to reflect on dataset provenance, demographic representation, and the broader consequences of data reuse, factors often hidden or overlooked in open data environments. This study challenges the assumption that openness automatically leads to fairer AI systems. By offering empirical evidence of how documentation scaffolds ethical decision-making, the author makes a compelling case for embedding such practices throughout AI, especially as machine learning systems increasingly rely on openly available and ethically complicated data.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Carroll, Stephanie Russo, Edit Herczog, Māui Hudson, Keith Russell, and Shelley Stall. 2021. “Operationalizing the CARE and FAIR Principles for Indigenous Data Futures.” ''Scientific Data'' 8: 108. https://doi.org/10.1038/s41597-021-00892-0.'''
&lt;/div&gt;

Carroll et al. discuss how the FAIR (Findable, Accessible, Interoperable, and Reusable) principles for scientific data and CARE (Collective Benefit, Authority to Control, Responsibility, and Ethics) principles for Indigenous Data Governance can be operationalized to allow Indigenous Peoples’ Rights to control their data, especially as big data and open data increase access to large datasets. The authors consider that the two sets of principles can be complimentary, both for scientific data and for data created by or about Indigenous Peoples. Scientific data can benefit from the CARE principles because many scientific datasets contain Indigenous Knowledge and these datasets can be oriented in ways that enhance the wellbeing of people by recording provenance and using appropriate governance models. Similarly, Indigenous Data can benefit from the FAIR principles to make data interoperable, regardless of the source or underlying technology, even if the datasets cannot be made openly accessible. The authors provide some recommendations to operationalize FAIR principles with CARE by making Indigenous data FAIR, raising awareness of the CARE principles among the research community before engaging with Indigenous data, and testing ways to use CARE principles for Indigenous data.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Carroll, Stephanie Russo, Ibrahim Garba, Óscar Luis Figueroa Rodríguez, Jarita Holbrook, and Raymond Lovett. 2020. “The CARE Principles for Indigenous Data Governance.” ''Data Science Journal'' 19 (1): 43. https://doi.org/10.5334/dsj-2020-043.'''
&lt;/div&gt;

The authors ground the article in the structural biases embedded in data ecosystems and the ongoing processes of colonization that have produced epistemicide and constrained Indigenous Peoples’ ability to sustain their knowledges. They highlight how inequities operate across digital infrastructures and institutions, while Indigenous knowledge systems already engage with this complexity. The article directly refers to the tension between Indigenous Data Sovereignty and the data demands of AI, machine learning, and big data initiatives, noting that secondary data use and broad data sharing can threaten Indigenous rights, consent, and collective interests. Within this context, the Indigenous-led development of the CARE principles (Collective Benefit, Authority to Control, Responsibility, and Ethics) is discussed as a value-based response to concerns about the secondary use and reuse of Indigenous data. It highlights that open data for AI training is not a merely technical matter, but a political one, where broad data sharing and algorithmic extraction can underscore Indigenous rights, consent, and collective interests. By articulating CARE, authors argue for frameworks that centre people and purpose rather than solely data accessibility or system performance. The paper concludes that reclaiming control of data and data narratives shifts Indigenous Peoples from being subjects and invisible within data systems to self-determining users who shape governance, policy, ethics, and innovation in ways aligned with collective benefit and equity.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Heger, Amy, Liz B. Marquis, Mihaela Vorvoreanu, Hanna Wallach, and Jennifer Wortman Vaughan. 2022. “Understanding Machine Learning Practitioners' Data Documentation Perceptions, Needs, Challenges, and Desiderata.” ''Proceedings of the ACM on Human-Computer Interaction'' 6 (CSCW2): 1–29. https://doi.org/10.1145/3555760.'''
&lt;/div&gt;

Heger et al. (2022) examine whether existing data documentation frameworks actually meet the needs of machine learning (ML) practitioners, a crucial issue given that AI models now shape high-stakes decisions across disciplines and depend heavily on the quality and transparency of their training data. The authors argue that while documentation initiatives like Datasheets for Datasets aim to support responsible and transparent AI, little is known about how these tools function in industry settings, where workflows, pressures, and data types differ substantially from academic contexts. Through semi-structured interviews and a documentation exercise with 14 practitioners, they find that current documentation practices are largely ad hoc, narrow in scope, and often disconnected from responsible AI concerns. Participants struggled to understand the purpose of many documentation questions, were unsure of appropriate granularity, and often failed to recognize the ethical implications of dataset characteristics. Their findings reveal a significant gap between responsible AI ideals and everyday ML practices. The study provides evidence that documentation frameworks must be contextual, integrated into existing tools, and supported by actionable guidance if they are to prevent downstream harms. By deriving seven design requirements, the authors offer concrete directions for developing documentation standards that can support safer, more accountable open AI data practices.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Huerta, E. A., Ben Blaiszik, L. Catherine Brinson, Kristofer E. Bouchard, D. Díaz, et al. 2023. “FAIR for AI: An Interdisciplinary and International Community Building Perspective.” ''Scientific Data'' 10: 487. https://doi.org/10.1038/s41597-023-02298-6&lt;nowiki/&gt;.'''
&lt;/div&gt;

Huerta et al. (2023) survey a wide landscape of US and European initiatives defining the FAIR (Findable, Accessible, Interoperable, Reusable) principles for AI models, arguing that responsible AI requires more than open access, it requires infrastructures that make AI assets understandable, comparable, and genuinely reusable. Their main argument is that FAIR must be reinterpreted for AI because models, software, and workflows are now “first-class” research objects, and only coordinated, community-wide standards can support interpretability, reproducibility, and sustainable open science. By mapping dozens of large, interdisciplinary FAIR-for-AI efforts, the authors show how FAIRness enables cross-disciplinary model reuse, transparent benchmarking, and educational access, ultimately laying groundwork for foundation models built from FAIR, AI-ready datasets. The paper highlights a major gap in current AI openness debates: open access alone does not ensure usable, trustworthy, or equitable AI. The authors demonstrate that without shared metadata standards, integrated repositories, and long-term infrastructure, openness can fragment into silos that impede scientific discovery. Their community-focused perspective invites readers to see FAIR not as a bureaucratic checklist but as an evolving, collaborative project essential for scaling transparent, reusable AI across scientific domains.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Taeihagh, Araz. 2025. “Governance of Generative AI.” ''Policy and Society'' 44 (1): 1–14. https://doi.org/10.1093/polsoc/puaf001.'''
&lt;/div&gt;

Taeihagh’s work takes on the evolving governance challenges surrounding generative AI, particularly the way its vast training data demands have injected new urgency into long-running debates over open data governance. Unlike rule-based AI systems designed for fixed, pre-specified tasks, generative models train on expansive datasets and produce novel outputs. The author argues that this reshapes the very terrain of risk. This shift invites distinct concerns: hallucination, jailbreak, exposure of sensitive information, accuracy failures, opacity, and the general difficulty of control. Taeihagh not only details how these risks emerge from the technical properties of generative systems but also proposes a governance framework that maps potential interventions to each category of risk and explores the institutional supports required to make such interventions effective. The framework is especially instructive for today’s AI data-governance debates, where the scale and unpredictability of generative models are compelling policy-makers to rethink what openness should entail, whose interests it advances, and how governance mechanisms can guard against extractive data practices while steering AI development toward public values.

== Open Source ==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Bostrom, Nick. 2017. “Strategic Implications of Openness in AI Development.” ''Global Policy'' 8 (2): 135–148. https://doi.org/10.1111/1758-5899.12403&lt;nowiki/&gt;.'''
&lt;/div&gt;

This article is a cross-section that surveys the notion of openness in AI development before proprietary AI models entered the market, observing  the early approaches of competing companies including Google, Facebook, and Microsoft, as well as OpenAI’s origins as a non-profit organization—OpenAI now operates as a capped-profit company governed by a non-profit, functioning effectively as a for-profit public benefit corporation rather than a publicly traded entity. The article focuses on long-term moves toward openness and their implications, but also briefly considers the benefits and problems inherent in short- and medium-term openness: Bostrom speculates that too much openness runs the risk of curbing corporate (and therefore funding) interest, ultimately slowing the rate of AI’s technological progress. However, he also asks: “Supposing openness would speed technical progress and rollout of AI capabilities, would that be socially beneficial?” (137). Bostrom notes a number of concerns ranging from public safety to labour encroachment, but still suggests that openness in AI development would be a net positive that accelerates the rate of technological progress in the short and middle-term. In the article’s long term section, Bostrom considers multiple scenarios in which openness might either help or hinder the safety and progress of a general AI superintelligence. He identifies distinct forms of openness (Science and Source Code; Control Methods and Risk Analysis; Capabilities and Expectations; and Values, Goals, and Governance Structures), addressing the potential value of openness in each, and argues that while openness is generally positive, especially in issues of values and safety, sharing too much knowledge may increase the odds someone will abuse this technology or ignore safety. 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Cooper, Martin. 2023. “Open Source is Good for AI But, Is AI Good for Open Source?” ''ITNOW'' 65 (2): 50–51. https://doi.org/10.1093/combul/bwad062&lt;nowiki/&gt;.'''
&lt;/div&gt;

Cooper shares Terence Eden's perspectives on the evolving relationship between artificial intelligence and the open source movement, ultimately raising ethical and practical concerns about attribution and authorship in the age of AI-generated code. Eden believes that open source promotes technologies like AI, cloud, and the internet, driving efficiency, reducing duplication, and advancing scientific discovery. He raises an issue with AI’s use of open source without proper attribution violating one of open source’s core principles: crediting the original creator. Despite acknowledging that AI can assist developers and make programming more accessible, Eden cautions against viewing AI as a substitute for genuine understanding or creativity. Ultimately, Eden’s article is both a celebration and a warning: open source has empowered AI, but unless attribution and ethical use are safeguarded, AI may erode the very openness and integrity that made its success possible. 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Guo, Xinwei, Yujun Li, Yafeng Peng, and Xuetao Wei. 2024. “Copyleft for Alleviating AIGC Copyright Dilemma: What-if Analysis, Public Perception and Implications.” Preprint, ''arXiv'', February 19. https://arxiv.org/abs/2402.12216. '''
&lt;/div&gt;

This article analyzes and summarizes copyright disputes related to Artificial Intelligence Generated Content (AIGC) and isolates three primary stakeholders within these disputes: data owners, who create the content upon which AIGCs have been trained; model owners, who develop the AIGC applications and models (e.g., ChatGPT, Stable Diffusion, etc.) themselves; and model users, who apply prompts to AIGC models to generate content. The authors consider the benefits, challenges, and risks that arise from each given stakeholder making a claim to copyright while considering the potential benefits and challenges of embracing copyleft (i.e., granting free use over material so long as the products of that free use are also under copyleft). In their contemplation of each stakeholder, they recognize the benefits for each group in advocating copyright to content, but also identify harm to other stakeholders, society, progress in developing AIGC, and institutions (e.g., “the copyright registration system”). The authors consider three real-life cases surrounding copyright disputes and envision how copyleft would effectively alleviate the disputes and tension surrounding their different stakeholders. The last half of the article performs a survey that asks users who have a range of familiarity with AIGC a range of questions, including who ought to have copyright claims to a generated image of the Mona Lisa in the style of Vincent Van Gogh. The authors note that their survey indicates consistent ambivalence, misunderstanding, and concern over copyright issues related to AIGC. The survey identified that there is support for applying copyleft to AIGC, and that that support increases the more someone understands the issues surrounding AIGC and copyright. 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Osborne, Cailean. 2024. “Why Companies &quot;Democratise&quot; Artificial Intelligence: The Case of Open Source Software Donations.” Preprint, ''arXiv'', September 26. https://doi.org/10.48550/ARXIV.2409.17876&lt;nowiki/&gt;.'''
&lt;/div&gt;

Osborne aims to advance the &quot;nascent research agenda on the political economy of open source AI&quot; by studying various corporate AI OSS donations to non-profit foundations and thereby sourcing and explaining corporate incentives behind their &quot;democratization&quot; of AI. He firstly outlines this topic in detail, clarifying that the technology required to access AI is expensive, and developing AI even more so, meaning this &quot;democratization&quot; represents only a lowering rather than removal of barriers. Osborne then considers the possible incentives behind organizational level decisions to democratize AI, as companies seek to competitively dominate industry norms, test and improve their products, enlarge intellectual property, reduce R&amp;D costs, and focus external research into their own AI. Significantly, individual developers of open source software do not have the same incentives but tend to accept commercial participation. On one hand, corporate participation means volunteers will be contributing toward these sources of corporate profit without reward; on the other hand, it risks companies dominating open research spaces and developing a complex intercompany research network of &quot;co-opetition&quot; which individual volunteers cannot enter. Therefore, Osborne’s study is highly relevant to issues of commercialization and open scholarship and especially concerns of “open-washing.” The study’s results highlight the predominantly commercial incentives behind corporate “AI democratisation” efforts, appropriately mirroring its most common form—the democratization of governance. However, Osborne's results also illustrate the significance of the individual level, “bottom-up” movement, suggesting that a significant 38% of decisions to donate stemmed from developers. Despite this, he concludes that “AI democratization” is indeed “a strategic calculation, where companies relinquish control of their OSS project in exchange for assumed benefits,” as “democratisation of governance is treated as a social means for primarily economic and technological ends,” broadly supporting the works of Widder et al. and Srnicek, and encouraging other researchers to bring their attention to this area. 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Radu, Roxana. 2021. “Steering the Governance of Artificial Intelligence: National Strategies in Perspective.” ''Policy and Society'' 40 (2): 178–193. https://doi.org/10.1080/14494035.2021.1929728.'''
&lt;/div&gt;

This article provides a survey and analysis of the national strategies related to AI implemented by a dozen countries around the world. It is of particular interest to those interested in concrete policies and regulations surrounding AI rather than discourse and rhetoric. Radu identifies a tension between nations claiming to take a leadership role and corporations that are “driving developments in the field.” More specifically, she observes that the vast “majority of binding agreements and voluntary commitments” come from corporations rather than nations or government regulatory bodies, indicating a concerning trend toward self-regulation. Governments have often played a key role in facilitating the conditions in which the development of AI technologies have thrived, even funding the rudimentary research that leads to AI models and applications, and this article notes that, regardless of the level of government regulation, the state is rarely a passive player when it comes to AI. Radu identifies the trend of a “dominant place for industry in the drafting process” and that representatives from industry make up a third of members drafting national strategies as well as prominent positions within those groups. Radu also notes absences: for instance, despite more than seventy countries using AI for surveillance, this issue is conspicuously absent from most strategies. Radu concludes that the common thread among many of these strategies is a hybridity between industry and state that affirms “the deliberate choice for functional indetermination,” resulting in a lack of clarity surrounding “who makes the rules and for how long,” and notes there are very few limitations placed on industry as these strategies instead provide vague ethical guidelines. 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Schmit, Cason, M. J. Doerr, and J. K. Wagner. 2023. “Leveraging IP for AI Governance.” ''Science'' 379 (6633): 646–647. https://doi.org/10.1126/science.add2202.'''
&lt;/div&gt;

This article proposes a hybrid AI copyright model that combines copyleft licensing and “patent trolling” in order to enforce an ethical approach to using AI models and training datasets. Schmit et al. contend that current legislation that applies to AI models and their use “are insufficient to impel ethical conduct” and require further consideration. The article advocates its hybrid model—Copyleft AI with Trusted Enforcement (CAITE)—as both rigorous and flexible, allowing for both self-reporting and monitoring. Essentially, the system works by creating an ecosystem in which AI models and training data are developed using copyleft, allowing for free use of these materials so long as the product of that use is covered by the same licensing agreement. At the same time, the enforcement of that licensing agreement is transferred to a regulatory entity called the CAITE Host, which acts as a positive counterpart to the patent troll, ensuring that no individual or organization breaches the terms of copyleft, introduces dangerous applications, data, or features, or unethically uses materials under the copyleft agreement. The CAITE Host and its code of ethics are driven by community oversight and buy-in, and the host is regulated by the community. The authors contend that its flexibility and bottom-up structure make CAITE uniquely suited to handling the rapidly developing field of AI and its shifting needs. Once CAITE achieves a critical mass, it would also become increasingly unlikely for AI developers to opt out. The article concludes by proposing a pilot model for CAITE, and strongly suggests that such a framework is far preferable for industry and others than stringent, relatively slow-moving, and inflexible government regulation in isolation. 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Shanklin, Grant, Cason Schmit, Jacob Pierce, Nicole Martinez-Martin, and Matthew DeCamp. 2025. “The Case for Contextual Copyleft: Licensing Open Source Training Data and Generative AI.” Preprint, ''arXiv'', July 17. https://arxiv.org/abs/2507.12713.'''
&lt;/div&gt;

This article introduces and describes a new form of content licensing, CCAI (Contextual Copyleft AI), designed to apply copyleft values and ethics to AI content, and should appeal to anyone interested in coding, copyright, and the (mis)use of training data for generative AI. The authors advocate for an approach that preserves the values of the Free and Open Source Software (FOSS) movement by using copyleft as a mechanism for the rights of AI content. The CCAI license requires that the free use and distribution of the software in question, that any work derived from that software must also be licensed under CCAI, and that CCAI software must “include source code or provide a way to access it.” The CCAI draws from and imitates other copyleft licenses but explicitly addresses and outlines the expectations regarding specific components of AI models within its license, applying copyleft and a requirement of openness to training data, code, and parameters. The article contends that whether it is easily demonstrable or not, clear guidelines of when training on publicly available data is and is not okay can act as a deterrent to misuse, and the CCAI license will give developers more agency in how others use their code, accelerate open source AI development by giving open source AI models open source training data only they can use, and limit the practice of open washing—claims that software and AI is open source when it is not (or not fully open source). The authors admit there are security risks that come with open AI models (e.g., vulnerabilities to malicious actors), but they contend that the benefits far outweigh those risks, especially when accompanied by the implementation of the CCAI and complementary regulations. 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Widder, David Gray, Dawn Nafus, Laura Dabbish, and James Herbsleb. 2022. “Limits and Possibilities for ‘Ethical AI’ in Open Source: A Study of Deepfakes.” In ''Proceedings of the 2022 ACM Conference on Fairness, Accountability, and Transparency (FAccT ’22)'', 2035–46. New York: Association for Computing Machinery. https://doi.org/10.1145/3531146.3533779.'''
&lt;/div&gt;

Widder et al. assert that significant understudied harms arise from divergent practices of “transparency and accountability” in the open source community. They argue that interventions designed for private companies may be improper for open source contexts, highlighting gaps in current approaches to “Ethical AI.” Their purpose is to reveal these systemic vulnerabilities and propose frameworks that better address the unique social and technical dynamics of open source development. They use an open source Deepfake creation tool as an extreme case to highlight how ethical reasoning intersects with broader cultural frameworks and interview project leaders. In this case study, researchers offer a definition of “Down stream control assumptions,” suggesting that “Ethical AI” research and “design interventions” would be improved by explicitly acknowledging these assumptions and identifying ways to work effectively under weak assumptions of downstream control in open sources contexts.

== Open Science ==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Ación, Laura, Mariela Rajngewerc, Gregory Randall, and Lorena Etcheverry. 2023. “Generative AI Poses Ethical Challenges for Open Science.” ''Nature Human Behaviour'' 7 (12): 1800–1801. https://doi.org/10.1038/s41562-023-01740-4. '''
&lt;/div&gt;

This article explores the tension between Open Science’s need to make knowledge freely accessible and the rise in GenAI and its tendencies to use any information available to it without necessarily considering how its application of such information (including information made available through Open Science) may do harm. These “frictions,” as the authors describe them, point to Open Science’s need to make data available while ensuring said data is not used to do harm. It is a concise summary of the foundational issues at the heart of these conversations, and great for anyone interested in how GenAI complicates Open Knowledge. The authors propose selective licensing as one approach to curbing harm, but notes that this only protects against harm from direct use (e.g., “open-source code used to build a weapon”) and not an indirect use (e.g., “open-source library use within another algorithm that is in itself harmful”). Ultimately, they stress the need for new governance systems and regulations related to the creation of knowledge that prioritizes both the public good and right to research.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Baltes, Sebastian, Florian Angermeir, Chetan Arora, Preetha Chatterjee, Jens Deitenbeck, Daniel Graziotin, Christoph Treude, et al. 2025. “Guidelines for Empirical Studies in Software Engineering Involving Large Language Models.” Preprint, ''arXiv'', August 21. https://arxiv.org/abs/2508.15503. '''
&lt;/div&gt;

This article develops best practices and guidelines for the use of LLMs (expressly language LLMs, not image, audio, or video) for empirical studies in software engineering (expressly data collection, processing, and analysis). The authors aim to “enable reproducibility and replicability” in the field even when LLMs are in use and “produce more reliable evidence on what LLM can and cannot deliver.” They present what they call a “taxonomy of Study Types” in addition to their guidelines, providing examples both within and beyond software engineering, all aimed at promoting the use of LLMs while promoting open science practices. The article considers LLMs as annotators, judges, synthesizers, and subjects in SE, and the guidelines Baltes et al. present have two tiers, MUST and SHOULD, demonstrating a nuanced understanding of practices without which SE research employing LLMs is rendered ineffective (e.g., declaring an LLM’s usage and role) and those practices that merely make this sort of research more rigorous and accessible (e.g., including full interaction logs if privacy and confidentiality can be ensured). The authors advocate for these practices to better enable researchers in SE to engage with LLMs while practicing Open Science. Of particular interest is the way in which the authors structure their understanding of the field and guidelines, and how they recognize distinct studies require slightly different practices.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Biderman, Stella, Hailey Schoelkopf, Quentin Anthony, Herbie Bradley, Kyle O'Brien, Eric Hallahan, Mohammad Aflah Khan, et al. 2022. “EleutherAI: Going Beyond ‘Open Science’ to ‘Science in the Open.’” Preprint, ''arXiv'', October 12. https://arxiv.org/abs/2210.06413. '''
&lt;/div&gt;

This article outlines the inception and progress of EleutherAI, a lab and AI model first founded in 2020 by a group of (for the most part) university affiliated academics and researchers concerned that for-profit companies are the primary developers of GenAI research and models, and that there is a lack of transparency and openness related to these technologies. Those interested in alternative approaches to AI models or a concrete example of Open Science in action should read this article. Because these researchers want to make available a “capable large language model… for public use, study, and scrutiny,” they have conducted all EleutherAI research in the open, making it freely accessible to everyone (1): all research and discussions take place on Discord servers, and projects coordinated and teams assembled in those servers on a grassroots basis. This “public-facing research” leads to a “virtuous cycle” with little turnaround between the conception of ideas and development of projects, and facilitates conversation, collaboration, and community by giving all users, even newcomers, unfettered access to every means of communication in which the group engages. The authors consider the downsides to such an approach as well, citing the issues of relying on volunteer labour, how others might take this public research for their own without proper accreditation to EleutherAI, and the important consideration that perhaps not all things should be made public, but ultimately conclude that such open research is integral to the academic community.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Gundersen, Odd Erik, Odd Cappelen, Martin Mølnå, and Nicklas Grimstad Nilsen. 2024. “The Unreasonable Effectiveness of Open Science in AI: A Replication Study.” Preprint, ''arXiv'', December 20. https://doi.org/10.48550/ARXIV.2412.17859. '''
&lt;/div&gt;

Gundersen et al. examine the extent to which a widely accepted crisis in research reproducibility affects AI research. They do this by conducting a systematic replication study of 30 highly cited AI studies, allowing the authors to identify the problems with irreproducibility. Out of the gate, the replication process could only be attempted with 22 of these studies because their research data needed to be openly available and reproducible without special hardware. Furthermore, the 22 replications were each given 40 working hours of effort, but 12 of these took too long and had to be stopped early, impacting their quality. In result, it was found that out of the 22 replication attempts began only six could be accurately reproduced and five partially reproduced, meaning a 50% success rate. The main problems for reproducibility were identified in six sources: the &quot;source code,&quot; &quot;article,&quot; &quot;data,&quot; &quot;results,&quot; and &quot;resources.&quot; Notably, each of the six accurate reproductions had code available, and the one other study with available code was a partial success limited by the time constraint, meaning availability of code alongside the data certainly improved the quality of the replication and was the most important factor for success. Therefore, despite limitations of a small sample size and time constraints, Gundersen et al. found that AI research’s reproducibility climbs from 33% accuracy when only data is available to 86% when both code and data are available. This is a significant enough result to empirically demonstrate the benefits of mandating openness and transparency of code as well as data. 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Helregel, N. 2025. “AI and Open Science: Implications and Library Practice Recommendations.” ''Library Trends'' 73 (3). https://doi.org/10.1353/lib.2025.a961191. '''
&lt;/div&gt;

Helregel (2025) examines the complex intersection of artificial intelligence and the open science movement, questioning whether current AI technologies possess the necessary transparency to align with open research principles. The article explores multiple dimensions of this relationship, assessing both the potential for AI to actively advance open science goals and the broader impacts of AI adoption on the attitudes and behaviours of researchers and the public. Recognizing the critical role of library and information science professionals in navigating this shifting landscape, Helregel outlines concrete recommendations for institutional library practice. These actionable strategies include prioritizing internal knowledge-building, fostering cross-institutional advocacy, adapting consultation and liaison workflows, navigating complex licensing agreements, and enhancing science communication. Ultimately, the paper positions libraries as vital infrastructure for ensuring that AI integration supports, rather than undermines, the core tenets of transparency, reproducibility, and accessibility in scholarly communication.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Hosseini, Mohammad, Serge P. J. M. Horbach, Kristi Holmes, Tony Ross-Hellauer. 2025 “Open Science at the generative AI turn: An exploratory analysis of challenges and opportunities.” ''Quantitative Science Studies'' 6: 22–45. https://doi.org/10.1162/qss_a_00337. '''
&lt;/div&gt;

Hosseini et al. provide an overview of the potential benefits and downsides of incorporating generative AI into different open science practices, as defined by the UNESCO Recommendation on Open Science, particularly open access, open data, open source software, open evaluation, open science infrastructures, open engagement of societal actors, and open dialogue with other knowledge systems. Some common benefits across these practices are that generative AI has the potential to lower the barriers to participation in science, summarize academic literature for non-academic audiences, and simplify processes in coding and data management. However, the authors also warn about the potential risks, including the creation and spread of misinformation, the propagation of hegemonic worldviews, and the monetization of research information. Given these downsides and the high social and ecological costs of generative AI, the authors suggest researchers question if AI tools are the most efficient way of achieving openness in science. The final section of the paper includes further recommendations for institutions, funders, and publishers, such as providing training on the use of generative AI, monitoring its positive and negative impacts, and continuing testing its use for evaluation and assessment purposes.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Linåker, Johan, Cailean Osborne, Jennifer Ding, Daniel Puttick, and Richard Nweibo. 2025. “A Cartography of Open Collaboration in Open Source AI: Mapping Practices, Motivations, and Governance in 14 Open Large Language Model Projects.” Preprint, ''arXiv'', September 29. https://arxiv.org/abs/2509.25397&lt;nowiki/&gt;.'''
&lt;/div&gt;

This article engages in a survey and interviews of the practices, motivations, and governance of fourteen open LLMs with the aim of further enabling collaboration throughout the open LLM lifecycle. The essay provides an overview of terms for open AI and major takeaways and challenges for different types of collaboration—types of collaboration include model, data, software, evaluation, non-technical, and compute—at the pre-training, post-training, and post-release stages of the LLM lifecycle. The authors also identify five governance frameworks for open LLM projects ranging from single companies to “non-profit-sponsored grassroots projects.” The authors opine that collaboration does not merely happen with LLMs themselves but the infrastructure and accompanying tools (e.g., datasets, open source frameworks, discussion fora, etc.) needed to produce and maintain them, and more research and attention needs to be given to the ecosystem surrounding LLMs. The article also includes recommendations “to support the global community of practitioners building a more open future for AI” for researchers and developers, AI companies, policy-makers, academic institutions, platform providers, and open source foundations. For instance, they recommend that policy-makers fund infrastructure of public AI, not just specific models, use targeted initiatives to support regional languages, require publicly funded research to use licensing that aligns with open science principles, and insist on a clear definition of what constitutes openness in these cases (36).

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Papi, Sara, Marco Gaido, Luisa Bentivogli, and Matteo Negri. 2025. “FAMA: The First Large-Scale Open-Science Speech Foundation Model for English and Italian.” Preprint, ''arXiv'', May 28. https://arxiv.org/abs/2505.22759&lt;nowiki/&gt;.'''
&lt;/div&gt;

This article presents an Open Science Speech Foundation Model (SFM) called FAMA, “the first family of large-scale open-science SFMs for English and Italian trained on over 150k hours of exclusively OS-compliant speech data.” FAMA’s results are comparable to its closed counterparts and considerably faster (up to eight times). The authors present a brief summary of recent advancements in automatic speech recognition and speech translation while raising concerns about the closed nature of related applications’ training data and code and pointing to open source alternatives in different domains for inspiration. The majority of the article is dedicated to specifics of architecture, training, and results of FAMA compared to its competitors; however, the end result—that FAMA is competitive with and even outperforms its larger, non-open counterparts like OpenAI’s Whisper in some cases—is an excellent case study in how open science can work in the domain of LLMs and AI.

{{Navigation|previous=Essential Contexts|next=AI and Social}}

{{BookCat}}</text>
      <sha1>ama4epzgu5vk6n6oi7jn1lsi1956v2j</sha1>
    </revision>
  </page>
  <page>
    <title>Taking Bearings: Artificial Intelligence in Knowledge Platforms and Open, Social Scholarship/AI and Social</title>
    <ns>0</ns>
    <id>483505</id>
    <revision>
      <id>4656120</id>
      <parentid>4655969</parentid>
      <timestamp>2026-08-02T21:33:17Z</timestamp>
      <contributor>
        <username>CorreiaA</username>
        <id>3614427</id>
      </contributor>
      <minor />
      <origin>4656120</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="123154" sha1="8wv6nqiv9242xlul61n4ublfkd3qwyz" xml:space="preserve">== Platforms ==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Burton, Jason W., Ezequiel Lopez-Lopez, Shahar Hechtlinger, et al. 2024. “How Large Language Models Can Reshape Collective Intelligence.” ''Nature Human Behaviour'' 8 (9): 1643–55. https://doi.org/10.1038/s41562-024-01959-9.''' 
&lt;/div&gt;

Large language models are quickly becoming infrastructure for how groups seek information, deliberate, and coordinate, potentially altering the conditions under which collective intelligence emerges. Burton and colleagues argue that LLMs do not merely speed up individual work but transform how information is aggregated, accessed, and transmitted across digital environments that underpin collective performance in organizations and societies. Drawing on interdisciplinary perspectives, the paper frames this shift as simultaneously enabling and destabilizing: LLMs can support distributed cognition (e.g., idea generation, synthesis, translation, scalable facilitation) while also increasing risks tied to dependence on shared intermediaries, degraded diversity of viewpoints, and new pathways for error, manipulation, or misplaced confidence. Rather than offering a single model or experiment, the article maps a research-and-practice agenda by identifying potential benefits, key hazards, and policy-relevant considerations, then articulating open questions that link technical design choices to group-level epistemic outcomes. Its central claim is that understanding collective intelligence in the LLM era requires moving analysis beyond isolated human–AI interactions toward system-level effects on networks, platforms, and institutions, and that these effects warrant focused study before LLM-mediated coordination becomes the default for tackling complex problems.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Corsi, Giulio, Bill Marino, and Willow Wong. 2024. “The spread of synthetic media on X.” ''Harvard Kennedy School (HKS) Misinformation Review''. https://doi.org/10.37016/mr-2020-140&lt;nowiki/&gt;.'''
&lt;/div&gt;

Corsi and Wong’s longitudinal empirical study analyzes 566 tweets containing synthetic media (December 2022–September 2023) documenting a dramatic surge following Midjourney V5 release with over 1.5 billion total views, revealing differential impacts where political deepfakes achieve higher median views despite representing minority of synthetic content. The authors demonstrate that generative AI's impact is stratified by content purpose with political misinformation posing acute democratic risks, while current detection and labelling systems lag behind generative capabilities, creating governance gaps compromising users' capacity to evaluate information. Using Community Notes data from December 2022 to October 2023, the study highlights the connection between the growth in generative AI tools and the rapid proliferation of synthetic media. The findings indicate that most synthetic media is non-political and largely benign, frequently taking the form of humorous or satirical images. However, the study also identifies a smaller but concerning portion of malicious synthetic media, which have potential height risks despite their lower frequency. The authors further examine the role of X’s paid verification system, revealing that while verified users tend to receive more overall views, this advantage diminishes when engagement is adjusted for follower count, implying that verification alone provides limited amplification. The study casts light on synthetic media’s expanding presence on social platforms and warns that even widespread exposure to seemingly harmless AI-generated content may gradually undermine trust in online information. To address these challenges, the authors recommend ongoing empirical monitoring, stronger collaboration between researchers and industry to develop transparent detection tools, and proactive policy measures aimed at reducing the social and political harms posed by malicious synthetic media.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Delmonaco, Daniel, Samuel Mayworm, Hibby Thach, Josh Guberman, Aurelia Augusta, and Oliver L. Haimson. 2024. “‘What are you doing, TikTok?’: How Marginalized Social Media Users Perceive, Theorize, and ‘Prove’ Shadowbanning.” https://oliverhaimson.com/PDFs/DelmonacoShadowbanning.pdf. '''
&lt;/div&gt;

Delmonaco et al.’s qualitative study explores marginalized social media users’ experiences with shadowbanning through the theoretical framework of algorithmic “folk theories.” Through a review of existing literature, the authors demonstrate how social media companies publicly distance themselves from shadowbanning while continuing to apply it in practice and explain why content produced by marginalized users is more frequently subject to filtering. The study analyzes 24 interviews to explore how users perceive, theorize, and attempt to “prove” shadowbanning through indicators such as decreased visibility, engagement, and follower loss. The findings reveal widespread confusion surrounding shadowbanning, deep mistrust in platform governance, and the disproportionate harm imposed on marginalized communities whose content is suppressed despite platforms’ public denials. The data further shows how users collectively produce and co-produce theories to resist the opacity of algorithmic moderation, and authors introduce “collaborative algorithm investigation,” in which users test and share algorithmic folk theories with one another. The authors argue that algorithmic content moderation exacerbates existing inequities by obscuring governance decisions, politicizing moderation, and shifting power from human judgment to opaque predictive systems, while suggesting that increased transparency, tailored moderation approaches, and users’ education could help reduce unfair content removals.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Drolsbach, Chiara, and Nicolas Pröllochs. 2025. “Characterizing AI-Generated Misinformation on Social Media.” Preprint, ''arXiv'', May 15. https://doi.org/10.48550/arXiv.2505.10266&lt;nowiki/&gt;.'''
&lt;/div&gt;

Drolsbach and Pröllochs’ article address a critical gap in existing research by shifting attention from the social drawbacks of AI-generated misinformation to its real-world prevalence and behaviour on social media platforms. Using a large-scale dataset of 91,452 misleading posts identified through X’s Community Notes platform, the authors empirically compare AI-generated and non-AI-generated misinformation across content characteristics, account attributes, virality, believability, and harmfulness. Their findings show that AI-generated misinformation is more entertainment-oriented, exhibits more positive sentiment, and is more likely to originate from smaller accounts, yet achieves significantly higher virality despite being slightly less believable and harmful than traditional misinformation. In their discussion and conclusion, the authors emphasize that AI-generated misinformation poses a growing challenge to the digital information ecosystem due to its realism, scalability, and difficulty of detection. They argue that its unique features disturb algorithmic amplification mechanisms and require new platform strategies, policy interventions, and research approaches that account for the unique properties of AI-generated misinformation rather than relying on countermeasures designed for conventional false content.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Duricic, Tomislav, Hussain Hussain, Emanuel Lacic, Dominik Kowald, Denis Helic, and Elisabeth Lex. 2023. “Beyond-Accuracy: A Review on Diversity, Serendipity, and Fairness in Recommender Systems Based on Graph Neural Networks.” ''Frontiers in Big Data'' 6: 1251072. https://doi.org/10.3389/fdata.2023.1251072.'''
&lt;/div&gt;

Duricic et al. (2023) provide a comprehensive review of recommender systems based on Graph Neural Networks (GNNs), with a particular focus on objectives that go beyond prediction accuracy, including diversity, serendipity, novelty, and fairness. While GNNs have demonstrated strong performance in modelling complex user–item interactions and improving recommendation accuracy, the authors argue that this very strength can intensify structural biases such as popularity bias, homophily, and feedback loops that marginalize less popular content and users. The paper provides a definition of each beyond-accuracy metric, reviews how it has been used in literature, and analyzes the technical barriers of integrating these goals into GNN-based systems such as measurement difficulties, trade-offs between competing goals, and risks of overfitting due to model complexity. Diversity-aware neighbourhood sampling, contrastive learning, and adversarial training to disrupt feedback loops are introduced for more heterogeneous and unexpected recommendations. In conclusion, the authors position GNNs as a powerful but double-edged tool in recommendation systems, capable of either narrowing or broadening users’ informational horizons depending on design choices. They argue that future research must focus on principled frameworks that integrate “beyond-accuracy” objectives, emphasizing that recommendation algorithms are not neutral optimizers but key socio-technical systems shaping visibility, voice, and fairness in digital information ecosystems.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Gorwa, Robert, Reuben Binns, and Christian Katzenbach. 2020. “Algorithmic Content Moderation: Technical and Political Challenges in the Automation of Platform Governance.” ''Big Data &amp; Society'' 7 (1): 1–15. https://doi.org/10.1177/2053951719897945.'''
&lt;/div&gt;

Gorwa et al. unfold what &quot;Algorithmic moderation systems” are perceived as essential in AI governance to address the public demand on AI accountability and transparency that remain unnavigable and inexplicable, such that even the enhanced versions could aggravate the existing misinformation issues. They state that major platforms' growth transforms them so much that they no longer function primarily as social networks. They define “algorithmic moderation” as “systems that classify user generated content based on either matching or prediction, leading to a decision and governance outcome (e.g. removal, geoblocking, account takedown).” Different types of hashing (matching) and classification (prediction) tools and the areas they are deployed (copyright, terrorism, and toxic speech) are described and their practicality are criticized. Their case analyzes including copyright enforcement, counterterrorism, and toxic speech illustrate the limitations and unintended harms of automated moderation, demonstrating how even “improved” systems risk reinforcing misinformation patterns, entrenching platform power, and displacing human judgment. Ultimately, Gorwa et al. argue that algorithmic moderation transforms platform governance itself by concentrating authority in opaque technical systems while rendering the underlying political choices invisible.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Reynolds, C. J., and Blake Hallinan. 2024. “User-Generated Accountability: Public Participation in Algorithmic Governance on YouTube.” ''New Media &amp; Society'' 26 (9): 5107–5129. https://doi.org/10.1177/14614448241251791. '''
&lt;/div&gt;

This study focuses on how YouTube creators respond to platform governance decisions by producing “user-generated accountability” content, videos that publicly document governance failures and pressure YouTube to intervene. Through an analysis of 250 such videos, the authors state that creators overwhelmingly experience YouTube’s policy enforcement, automated moderation systems, and communication practices as opaque, inconsistent, and often discriminatory. Authors declare that human review is essential in automizing platform governance. The study highlights that platform governance decisions affect creators differently depending on channel size, content type, and identity; larger creators can more easily mobilize audiences to “make noise,” while smaller creators rely on collective visibility tactics such as signal boosting across platforms, especially Twitter. The authors argue that these bottom-up accountability practices reflect both the limits of YouTube’s existing governance infrastructure and creators’ efforts to bypass scale dependent unresponsiveness by publicly sharing grievances, comparing experiences, and testing the platform’s algorithms themselves. Theoretically, the study provides the “user-generated accountability” as a framework for engaging with the unavoidable conflicts that will arise around algorithmic systems, and views content creators as “political actors” who advance the perceptions of algorithms. Empirically, it surfaces common concerns such as demonetization of LGBTQ content, and lack of human review.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Savolainen, Lotta. 2022. “The Shadow Banning Controversy: Perceived Governance and Algorithmic Folklore.” ''Media, Culture &amp; Society'' 44 (6): 1091–1109. https://doi.org/10.1177/01634437221077174.'''
&lt;/div&gt;

Savolainen studies shadowbanning as a lens for understanding current algorithmic platform governance from the user perspective. Rather than determining whether shadowbanning objectively exists, the author conceptualizes it as “algorithmic folklore”: informal, collectively produced narratives through which users attempt to make sense of opaque moderation and ranking systems. Drawing on Reddit discussions about TikTok, Instagram, and YouTube, the study shows how users interpret suppressed visibility through anecdotal evidence, experimentation, and shared pattern recognition, revealing the experiential dimensions of algorithmic governance. Either users “probe the rules” or find their ways through “pleasing the algorithms”; the author argues that these practices emerge in response to governance systems that lack the clarity, stability, and consistency that are traditionally associated with good governance. The study concludes that platform governance contains a structural paradox: platforms increasingly present themselves as legitimate governors while simultaneously developing automated moderation systems that undermine transparency and consistent enforcement. Ultimately, the ethical issue is not shadowbanning itself, but the broader reality of shadowy governance exercised by complex, distributed algorithmic systems at scale.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Vetter, Matthew A., Jialei Jiang, and Zachary J. McDowell. 2025. “An Endangered Species: How LLMs Threaten Wikipedia’s Sustainability.” ''AI &amp; Society'', February. https://doi.org/10.1007/s00146-025-02199-9.'''
&lt;/div&gt;

Vetter et al. caution against using Wikipedia as AI training data uncritically by outlining many complicating factors. Wikipedia’s collaborative model of data curation democratizes data creation, but embeds power dynamics and biases. A feminist posthumanist framework is applied, which situates Wikipedia’s knowledge as contextual, based upon the positionality of predominantly Western, male editors, a perspective LLMs would perpetuate without opportunity for change. Wikipedia’s &quot;dynamism&quot; is the main reason it is so valuable, stemming from constant, collaborative updates by volunteers. AI responses’ inconsistent citations and plagiaristic tendencies undermine human editors, the source of Wikipedia’s verifiability, and exploit scholars, Wikipedia itself, and the past labour of volunteers. Wikipedia needs both &quot;a steady stream of new and returning readers&quot; and &quot;a diverse group of dedicated volunteers,&quot; whilst AI responses push sources into obscurity and at best detour the website, threatening Wikipedia’s long-term sustainability. Vetter et al. practically explore Wikipedia’s relationship with LLMs by conducting a &quot;problem-centred expert interview&quot; of community leaders, who possess 25 combined years of involvement and research. Through these interviews, Vetter et al. identify three main areas of opportunity: promoting transparency and explainability, diversifying the Wikipedia community, and equipping users with critical thinking skills. Overall, their findings &quot;resonate with the posthumanist approach to critical AI literacy,&quot; cautioning against hoping for purely technological fixes and calling for greater transparency in how tech giants &quot;leverage open-access datasets.&quot;

== Governance, Leadership, and Policy ==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Balendra, Soorya. 2025. “Meta's AI Moderation and Free Speech: Ongoing Challenges in the Global South.” ''Cambridge Forum on AI: Law and Governance'' 1. https://doi.org/10.1017/cfl.2025.5&lt;nowiki/&gt;.'''
&lt;/div&gt;

This article conducts a case study of Meta’s AI-based content moderation in the Global South, arguing that the censorship of unprohibited content (“over removal”) and slow response to content that causes harm (“slow removal”) are part of “content moderation procedures” that constitute “massive discriminatory approaches.” Balendra presents three models of authority for the regulation of social media content: external regulation, self-regulation, and co-regulation, and argues that state regulation (falling under the external model) varies wildly depending on the government in question, with “granting absolute regulatory power to state actors often stifl[ing] political discourse and online expression.” Co- and self-regulation mitigate this problem, but introduce a new issue by shifting responsibility—private companies use AI to make millions of judgements about content in a short frame of time. The paper notes that the EU and the United States have drastically different policies regarding content moderation on social media platforms and argues that “the practice of content moderation remains largely shaped by the cultural norms of the United States” and the values of “a relatively homogenous groups of Silicon Valley elites.” Balendra finds that, at this time, current approaches often prioritize the state or private corporate interests rather than free speech or the interests of the larger community, and much work is needed to “achiev[e] genuine change” in the form of integrated, hybrid approaches.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Birkstedt, Teemu, Matti Minkkinen, Anushree Tandon, and Matti Mäntymäki. 2023. “AI Governance: Themes, Knowledge Gaps and Future Agendas.” ''Internet Research'' 33 (7): 133–67. https://doi.org/10.1108/INTR-01-2022-0042. '''
&lt;/div&gt;

Birkstedt et al. conduct a systematic literature review (SLR) of the emerging yet fragmented field of “AI governance” (AIG), defined as “a system of rules, practices, processes, and technological tools” that ensure organizational AI meets strategic, legal, and ethical requirements. The authors use human-centric and socio-technical AI traditions to explore how organization-level governance mechanisms can bridge the principles-to-practices gap in AI ethics. Through SLR, authors identify four research agendas. The “technical agenda” focuses on the practicalities of AIG. The “stakeholder and contextual agenda” ensures AI meets requirements via direct collaboration with external stakeholders, increased corporate social responsibility, and establishment of an “intelligent discourse regime.” The “regulatory agenda” aligns AIG with ethical and legal standards, while the technical, stakeholder and contextual, and regulatory agendas largely focus on the aims of organizational AIG (i.e., what), and the process agenda deals with the means to achieve the aims (i.e., how). The authors develop a generic framework to guide cohesive AIG practices and advocate for a collaborative governance approach that emphasizes transparency, stakeholder engagement, and sociopolitical awareness. 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Broekhuizen, Thijs, Henri Dekker, Pedro De Faria, Sebastian Firk, Dinh Khoi Nguyen, and Wolfgang Sofka. 2023. “AI for Managing Open Innovation: Opportunities, Challenges, and a Research Agenda.” ''Journal of Business Research'' 167 (November 2023): 114196. https://doi.org/10.1016/j.jbusres.2023.114196. '''
&lt;/div&gt;

Broekhuizen et al. systematically analyze how AI could be applied to the complex, unstructured task of “open innovation,” a possible business opportunity they believe has been insufficiently explored. They define “Open innovation” as “the practice of leveraging external ideas, resources, and capabilities to improve innovation outcomes,” and propose AI could minimize its inherent managerial challenges. To prove this, the authors form a framework that considers the three abilities involved in AI’s agreed possible applications to management (involving “mapping,” “coordinating,” and “controlling”) and assess how applicable their constituent functions are to the challenges of the three stages of open innovation (involving “initiation,” “development,” and “realization”). In the stage of “initiation,” they propose AI could scout for distant knowledge partners, detect relevant information gaps and opportunities, and forecast conflicts. During the “development” stage, AI could develop complementarity between partners' knowledge stocks, integrate knowledge whilst safeguarding intellectual property, and monitor partners for violations or conflicts within the relationship. Finally, during the “realization” stage the authors argue AI could comprehensively evaluate business opportunities, optimize resource deployment, and diagnose or remedy intellectual property violations. To Broekhuizen et al., this study “underscores the significance of the human-side of AI” by demonstrating AI’s valuable role in assisting management. They also conclude that AI’s ability to search for corporate partners will be its greatest impact in open innovation, as they argue it will both incentivize openness and reputability of companies and increase the need for them to keep sensitive data secure.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Cheong, Inyoung. 2024. “Collaborative Approaches to AI Governance: Exploring Co-Design and Co-Regulation Models.” PhD diss., University of Washington. https://homes.cs.washington.edu/~yoshi/papers/theses/inyoung-cheong-dissertation.pdf&lt;nowiki/&gt;.'''
&lt;/div&gt;

This dissertation seeks to integrate co-design and co-regulation as a means of facilitating domain-specific expert knowledge into AI governance policies. It uses theoretical analysis and empirical data as part of its methodologies, and it should be of interest to anyone who wants detailed case studies of the use of AI technology in specific domains, as well as clear models for (co-)governance and development in the use of Artificial Intelligence. Cheong performs two case studies, examining the development and use of an AI application to provide legal advice as well as the application of AI in online content moderation of news and comics apps in South Korea. These result in a set of strategies for AI co-regulation that includes parameters for starting conditions, institutional design, collaborative process, and facilitative leadership. Cheong proposes that the guiding principles for AI co-governance must account for specific and distinct contexts, maintain human involvement and intervention in what is often seen as an artificial and automated process, and look to resolve legal ambiguities surrounding AI, especially as there is a clear history of courts dismissing what Cheong calls “collective rule-making” by the community. The author argues for the implementation of co-regulation and co-design, and maintains that “by fostering inclusive dialogues, leveraging diverse expertise, and remaining adaptable to changing technological and societal landscapes” these methods show potential for dealing with AI’s greatest challenges.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Floridi, Luciano. 2018. “Soft Ethics and the Governance of the Digital.” ''Philosophy &amp; Technology'' 31 (1): 1–8. https://doi.org/10.1007/s13347-018-0303-9&lt;nowiki/&gt;.'''
&lt;/div&gt;

Floridi argues our “mature information societies” means “we no longer live online or offline, but onlife,” making the sociopolitical challenge of ethically governing this foundational “digital age” even more vital than pursuit of future digital innovations. Floridi defines three overlapping subfields within the “Governance of the Digital,” including “Digital Ethics,” “Digital Regulation,” and the encompassing “Digital Governance.” The latter is defined as “the practice of establishing and implementing policies, procedures, and standards for the proper development, use and management of the infosphere,” therefore “sometimes neither moral nor immoral… legal nor illegal.” This demonstrates that the three subfields don’t always overlap, but each must always be considered by policymakers, because what is legal, what is good, and what is best are all key components of the ideal “Governance of the Digital.” “Digital Ethics” should also be further subdivided into “hard” ethics, involving binary moral judgments about what should versus should not be done, and “soft” ethics, which involves a “post-compliance,” “post-feasibility” approach, ensures moral opportunities are maximized, and fosters “good corporate citizenship.” Differing “information societies” occupy differing levels of maturity, producing distinct ethical contexts which should progress with differing ethical focuses. In this regard, Floridi advocates “ethics foresight analysis,” which uses data analytics to assess ethical impacts of future innovations then targets research by systematically identifying what is feasible, then sustainable, then acceptable, then preferable. The author concludes that Digital Ethics must be “leading” not “chasing” developments, and not just functioning as a questioning exercise, but also signalling that ethical issues matter, engaging with stakeholders, and providing shareable solutions.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Gasser, Urs, and Virgilio A. F. Almeida. 2017. “A Layered Model for AI Governance.” ''IEEE Internet Computing'' 21 (6): 58–62. https://doi.org/10.1109/MIC.2017.4180835&lt;nowiki/&gt;.'''
&lt;/div&gt;

This article identifies the gap in knowledge created by the “black box” of AI—the obscured nature of the processes that take place from an initial prompt to its generated output. Gasser et al. note that users and policymakers of these technologies have relatively little insight into how it actually works compared to its developers. Given this unique issue, Gasser et al. propose a theoretical framework for how to approach AI governance, drawing upon the advent and subsequent globalization of the Internet to inform their understanding of AI technology and its pattern of growth. The article addresses a core issue that strong or general AI is often discussed in terms of potential societal impact while weak or general AI is currently being deployed right now (i.e., 2017) and is in real need of governance already. The authors identify core themes related to “transparency, accountability, and explainability; inclusion and fairness; [and] global governance,” as well as three challenges for AI governance—&quot;information asymmetries”; “finding normative consensus”; and “government mismatches”. The authors point out that the ethical and legal considerations of AI are closely related and take a modularity approach; they present three layers for governance that exist from AI systems to society, with timing (i.e., near-, mid-, and long-term) and considerations for each layer. The article concludes by proposing AI governance requires a blended approach based on the different risks of certain AI applications and propose that both “market-oriented solutions” and &quot;government-based structures” can work on a national or international level, suggesting a “global oversight body” could act as “the curator of global principles and emerging norms for AI systems.”

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Kirschenbaum, Matthew. 2025. “The US of AI.” Public Draft, February 25, 2025. https://drive.google.com/file/d/1O2qkjhg7Ei5zZWmBraNwXq4V0lTauspN/view&lt;nowiki/&gt;.'''
&lt;/div&gt;

This set of notes from Kirschenbaum represents his “near real-time attempt to come to terms with… the opening weeks of the second Trump Administration,” especially the “AI-first” strategy of “the so-called Department of Government Efficiency (DOGE).” Kirschenbaum outlines DOGE has nothing to do with government efficiency, as it only saves insignificant costs, instead possessing ideological and capitalistic motivations to form “a government without people.” Based on Musk’s nebulous authority—as an advisor from the private sector—DOGE targeted nineteen federal agencies to be “strip-mined and fracked for all manner of information” as a “priceless and unprecedented resource” of AI training data. To do so, DOGE operatives accessed sensitive spaces after hours, combining physical aggression with a “complete lack” of technical inhibition representing a “vampiric data suck.” Kirschenbaum identifies clear corporate interests here and further examines ideological aims. Early executive orders asserted the need for federal AI systems “free from ideological bias or engineered social agendas,” with OpenAI announcing “ChatGPT Gov” days later. These invocations of “AI” as a universal solution represent only a “linguistic token” instead of any realized technology—as worded by Salvaggio, AI must only “be considered a plausible competitor to human decision-making long enough to dislodge the existing human decision-makers.” Kirschenbaum frames this as based in the “masculine maximalism” of the Trump administration, as the term AI promotes “technological absolutism” whilst theoretically playing into the Nixon-era “theory of the unitary executive” by aiming to replace people with “void” and consolidate power into the hands of “a super-user class who will operate outside the system.” However, “the real world intrudes… with lethal downstream effects.” Kirschenbaum proposes “a collapsing superimposition of political discourse, the actual operations of social media as its primary public arena, and the technical architecture of the systems (in the form of AI)… in the sphere of governance as well as media,” which produces the “infrastructure for… permanent despotism” via the “untethering of language from conditions of lived reality.”

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Oh, Dayei, and John Downey. 2024. “Does Algorithmic Content Moderation Promote Democratic Discourse? Radical Democratic Critique of Toxic Language AI.” ''Information, Communication &amp; Society'' 28 (7): 1157–76. https://doi.org/10.1080/1369118X.2024.2346531.'''
&lt;/div&gt;

Oh and Downey critically examine how algorithmic content moderation shapes public discourse, focusing specifically on Google’s Perspective API and its detection of &quot;toxic&quot; language. By drawing a crucial distinction between incivility (harsh or emotional tone) and intolerance (actual discriminatory harm), the authors demonstrate how AI-driven moderation systems frequently misinterpret context. Consequently, these algorithms often suppress emotionally charged but politically significant speech—particularly from marginalized groups—while allowing structurally discriminatory but politely phrased content to evade detection. This dynamic reveals a significant flaw in relying on AI as a neutral mediator of digital dialogue: by prioritizing tone over substance, algorithmic moderation actively curtails democratic participation and skews the visibility of diverse perspectives. Their study is relevant for understanding how AI systems act as invisible gatekeepers, enforcing normative boundaries on public expression and highlighting the urgent need for moderation frameworks that are contextually aware, transparent, and equitable rather than merely tone-policing.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Rughiniș, Cosima, et al. 2025. “AI at the Knowledge Gates: Institutional Policies and Hybrid Configurations in Universities and Publishers.” ''Frontiers in Computer Science'' 7: 1608276. https://doi.org/10.3389/fcomp.2025.1608276. '''
&lt;/div&gt;

This article constitutes a qualitative analysis (i.e., a form of computational analysis) of 16 universities and 12 publishers that attempts to understand how these institutions regulate AI in knowledge production. Rughinis et al. claim that most institutions preserve their values while regulating AI by adapting the regulations they already have in place, stating “institutional policies are shaped by value-based compromises and not by technical concerns alone.” At the same time, although the article acknowledges its focus on institutional regulation, it also admits that “AI adoption can evolve both through policy frameworks and… locally embedded practices that remain partly invisible in formal documentation.” The authors propose two concepts, “dual black-boxing” and “legitimacy-dependent hybrid actors.” Dual black-boxing refers to the lack of transparency in both the “hidden algorithmic processes [and] invisible training data” that shape AI systems and “the opacity surrounding how academics employ AI in their work,” while legitimacy-dependent hybrid actors are “configurations of human-AI collaboration whose institutional legitimacy is not intrinsic but conditional.” Rughinis et al. argue that transparency is a core academic value, and scholars must work to open these black boxes; they also suggest that that transparency is more closely linked to academic legitimacy in AI-related issues rather than the more traditional issue of the origin of ideas. The majority of the article applies these terms to understanding the regulatory frameworks of universities and publishers, and concludes with the understanding that the majority of institutions allow some form of AI use within certain parameters. The key types of hybrid actors allowed by universities were AI-assisted researchers, AI-enabled translators, AI-enhanced writers, and AI-supported coders, while publishers facilitated the use of AI to refine language, support research methodologies, and aid in research. Ultimately, the authors observe that institutions are permitting AI-supported work in refined roles and argue that AI-based academic work gains legitimacy through transparency.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Seger, et al. “Democratising AI: Multiple Meanings, Goals, and Methods.” ''Proceedings of the 2023 AAAI/ACM Conference on AI, Ethics, and Society''. https://dl.acm.org/doi/10.1145/3600211.3604693&lt;nowiki/&gt;.'''
&lt;/div&gt;

Aiming to “provide a foundation for more productive conversations,” Seger et al. categorize four forms of “AI democratisation” and explore each form’s goals and facilitation pathways. Democratization of AI “use” involves making it easier for people to employ AI’s capabilities, and is therefore equally comparable to increasing availability of printers or of tools which can create chemical weaponry, depending on the case. Democratization of “development” involves allowing a wider range of people to contribute to the AI design and development process, which accelerates progress and increases diversity, but also opens the door for maliciousness and irresponsibility. Democratizing “profits” constitutes a philanthropic or redistributive process, and has the predictably involved weaknesses. Therefore, the authors highlight that “AI democratisation is a multifarious and sometimes conflicting concept” which “should not be conflated with improving AI accessibility” and “is not inherently good.” This is because democratization of AI’s “use,” “development,” and “profits” only derives value from its alignment with the interests and values of impacted groups, making democratization of AI’s “governance” the priority. Democratization of “governance” does not necessarily aim for total agreement amongst constituents, but will regardless reduce the unilaterality of decision-making by promoting justice, legitimacy, and diversity.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Sposato, Martin. 2025. ”Artificial Intelligence in Educational Leadership: A Comprehensive Taxonomy and Future Directions.” ''International Journal of Educational Technology in Higher Education'' 22 (20). https://doi.org/10.1186/s41239-025-00517-1. '''
&lt;/div&gt;

This article performs an analysis and review of published works on AI in educational leadership from 2017–2024 and uses the results of that process to develop what Sposato describes as “a comprehensive taxonomy of AI applications in educational leadership.” Potential readers include researchers and policymakers interested in communicating across specific fields and disciplines. Sposato theorizes ten application domains for AI in higher education ranging from increased efficiency in administration and teaching practices to increased community engagement and strategic planning. The purpose of such a framework is to provide educational leaders with a coherent vocabulary of “the full spectrum of educational leadership responsibilities” that can facilitate further conversation. The author advocates for AI’s transformative potential in higher education even as they note important challenges (especially with ethics and equity), arguing a need for a balanced approach and “robust ethical guidelines and regulatory frameworks.” The framework provided is presented as one step toward developing AI literacy for stakeholders so that all involved in education might make more informed decisions and articulate their needs more clearly.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Ter-Minassian, Lucile. 2025. ”Democratizing AI Governance: Balancing Expertise and Public Participation.” Preprint, ''arXiv'', January 16. https://doi.org/10.48550/arXiv.2502.08651&lt;nowiki/&gt;.'''
&lt;/div&gt;

Ter-Minassian argues that “universal access, technically-constrained development, and universal impact” of AI and AI research necessitate public participation in AI governance even as it “creates a unique governance challenge.” The article presents the benefits and challenges of expert oversight and public consultation. Ter-Minassian outlines the threat of misinformation to meaningful public participation, highlighting how both undue fear and unrealistic optimism surrounding AI can affect public discourse, while acknowledging that the rapid rate of AI research makes it difficult to incorporate truly democratic processes into the decision-making process. The author concludes that any ongoing inclusive and effective AI governance ought to incorporate inclusive representation, balance expertise and public engagement, embrace transparency and accountability while engaging an iterative process, and implement a hybrid framework that “blend[s] expert knowledge with meaningful public input” (4). She argues that “AI’s deep societal impact calls for public engagement” and “technical complexity does not have to exclude meaningful public input,” advocating for “structured deliberation and phased public participation” to address “time-sensitive AI challenges without compromising democratic legitimacy” (5). Ultimately, the article sees this as an iterative process that will need to continue to adapt in order to maintain expert insight and public discourse on AI.

== Critical Literacies ==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Aguiar, Micaela, and Sílvia Araújo. 2024. “Final Thoughts: Digital Humanities Looking at Generative AI.” ''In Digital Humanities Looking at the World'', edited by S. Araújo et al., 367–380. Cham: Springer Nature Switzerland.'''
&lt;/div&gt;

Aguiar and Araújo explore the emergence and applications of generative artificial intelligence within Digital Humanities research. They trace the evolution of generative AI from early implementations like the 1960s Eliza chatbot through its developments such as Generative Adversarial Networks (GANs) and the Transformer architecture to contemporary large language models like BERT and GPT. The authors document current applications of generative AI across Digital Humanities domains, including cultural heritage preservation, historical text processing, and literary creation. They outline how these technologies are being used to memorialize mass atrocities, process traditional Chinese ancient texts, and explore collaborative human-AI poetry creation. Aguiar and Araújo examine the inner workings of generative AI, particularly focusing on how conversational models function through statistical prediction rather than genuine comprehension. They identify limitations such as hallucinations, bias replication, and attribution problems that researchers must consider when using these tools. The chapter concludes that effective integration of generative AI in Digital Humanities requires developing AI literacy skills that enable researchers to critically evaluate outputs while leveraging the technology's capabilities for sustainable research advancement.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Boer, Victor de, and Lise Stork. 2024. “Hybrid Intelligence for Digital Humanities.” Preprint, ''arXiv'', April 15. https://doi.org/10.48550/ARXIV.2406.15374. '''
&lt;/div&gt;

De Boer and Stork believe the discipline of Digital Humanities (DH) should meet the challenges and opportunities posed by Artificial Intelligence (AI) by adopting the “human-centric paradigm” of Hybrid Intelligence (HI). They define DH as “a scholarly realm where computing or digital technologies intersect with… the humanities… characterized by innovative approaches to scholarly endeavors,” and identify various existing DH approaches to AI, which include “Knowledge Representation,” “Machine Learning,” “Natural Language Processing,” and “Computer Vision.” De Boer and Stork argue successfully integrating AI tools into DH requires embedding AI in scholarly practice, adopting a diverse and polyvocal approach, considering the debate of distant versus close reading, and applying a critical stance toward data, methods, and tools. HI “concerns itself with the investigation and design of human-AI ecosystems,” and the authors argue effective AI should be developed by following its “CARE” principles—being “Collaborative, Adaptive, Responsible, and Explainable.” Therefore, De Boer and Stork focus this text on mapping CARE principles to those DH requirements earlier outlined. Overall, they concur with Goodlad and Baker that humanists “are ideal 'domain experts' for the current juncture,” and end by identifying two overarching challenges. The first challenge is “one-shot solutions,” including tools, datasets, and methods that aren’t reusable, Open Source, accessible, and well described. Secondly, they identify the human factor—actors will need both an open mind and AI literacy to be equally critical of and cooperative with AI. Therefore, the authors emphasize the importance of teaching digital methods within the humanities curricula.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Carmi, Elinor, Simeon J. Yates, Eleanor Lockley, and Alicja Pawluczuk. 2020. “Data Citizenship: Rethinking Data Literacy in the Age of Disinformation, Misinformation, and Malinformation.” ''Internet Policy Review'' 9 (2). https://doi.org/10.14763/2020.2.1481.'''
&lt;/div&gt;

This study argues that dominant understandings of digital and data literacy are insufficient for addressing contemporary complex challenges of disinformation, misinformation, and malinformation. They propose the concept of data citizenship to reframe literacy as a fundamentally civic, political, and collective practice rather than a set of individual technical skills. The authors contend that information disorders cannot be addressed through technological solutions alone, as they are deeply embedded in structural inequalities, platform economies, and power asymmetries shaping datafied societies. The article builds on a literature review and secondary data analysis drawing on Me and My Big Data project, alongside the development of a nationally representative UK survey. The authors identify three major gaps in existing literacy frameworks: an overemphasis on individual competence rather than networked practices, a lack of critical engagement with algorithmic and economic infrastructures of platforms, and the absence of proactive civic skills such as contesting data extraction, demanding transparency, and advocating for data justice. Their analysis highlights how citizens’ data practices are shaped by social networks, education, and socio-economic conditions, revealing unequal capacities for verification, protection, and collective action. The authors conclude that data literacy must move beyond content verification to include critical understanding of platform design, funding models, and algorithmic governance. They emphasize the importance of locally grounded, participatory approaches to data literacy education that reflect diverse lived contexts rather than scalable, top-down interventions. While the study offers a robust conceptual model and survey-based insights, it does not yet include in-depth qualitative engagement with citizen groups, which the authors position as a necessary next phase of research. Overall, the article makes a significant contribution by bridging digital literacy and the field of mis/dis/mal information research and claims that data literacy is an essential component of democratic citizenship.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Long, Duri, and Brian Magerko. 2020. “What is AI Literacy? Competencies and Design Considerations.” In ''Proceedings of the 2020 CHI Conference on Human Factors in Computing Systems'', 1–13. New York, NY: Association for Computing Machinery. https://doi.org/10.1145/3313831.3376727.'''
&lt;/div&gt;

The authors present an exploratory review of interdisciplinary literature, aiming to organize key ideas on AI literacy definitions and essential competencies. Authors claim that public misunderstandings of AI are due to design, educational gaps, black-box algorithms, and a general lack of technological knowledge. The review includes two sections: how the public understands specific AI systems, and how existing research addresses people’s broader understanding of AI. Rather than offering an exhaustive synthesis, Long and Magerko’s focus is on non-technical audiences and they offer central provocations and design principles that can inform educational interventions. The proposed conceptual framework on AI literacy identifies 17 core competencies alongside 14 design considerations for educational intervention, which are described and supported by relevant literature. Together, these considerations position the framework as a practical and reflective tool for designing AI literacy interventions that move beyond dominant media narratives and foster critical, informed engagement with AI technologies.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Majdik, Zoltan P., and S. Scott Graham. 2024. “Rhetoric of/with AI: An Introduction.” ''Rhetoric Society Quarterly'' 54 (3): 222–31. https://doi.org/10.1080/02773945.2024.2343264. '''
&lt;/div&gt;

Majdik and Graham propose a field-organizing distinction that functions as a methodological argument. By splitting inquiry into “rhetoric of AI” (AI as object) and “rhetoric with AI” (AI as method), they treat AI simultaneously as a rhetorical actor/ecosystem component that structures attention, circulation, and uptake, and as an instrument that can be enrolled into rhetorical research workflows. The authors claim that much prior rhetorical work engaged “spaces of AI”—platforms, devices, and algorithmically mediated environments—while leaving “AI” itself undertheorized as the central object; this provides a justification for why rhetoricians should now foreground model/algorithmic operations (and their harms) rather than treating them as neutral background conditions of digital rhetoric. They also frame generative text systems as a stress test for core rhetorical concepts—agency, authorship, and audience—because these systems destabilize the presumed linkage between human intention and textual production, and because they insert nonhuman intermediaries into communicative situations that education and public discourse still normatively treat as human-to-human. The introduction then uses this distinction to stage the special issue’s contributions as complementary routes for rebuilding rhetorical theory and pedagogy under AI conditions.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Ng, Davy Tsz Kit, Jac Ka Lok Leung, Samuel Kai Wah Chu, and Maggie Shen Qiao. 2021. “Conceptualizing AI Literacy: An Exploratory Review.” ''Computers and Education: Artificial Intelligence'' 2: 100041. https://doi.org/10.1016/j.caeai.2021.100041. '''
&lt;/div&gt;

This article presents an exploratory review of literature published between 2016 and 2021 with the goal of conceptualizing AI literacy and proposing a comprehensive framework for teaching and evaluating it. The authors analyze 30 articles and synthesize existing definitions and approaches to AI literacy, noting that while AI literacy has increasingly been discussed, the concept has often been treated narrowly as a technical skill set. The authors situate AI literacy as a necessary competency for everyone, arguing that AI will increasingly affect many aspects of daily life and employment. In response, the authors argue for a broader understanding of AI literacy that incorporates cognitive and ethical dimensions. The proposed framework organizes AI literacy into four interconnected facets: knowing and understanding AI, using and applying AI, evaluating and creating AI, and AI ethics. Importantly, the authors explicitly reject purely instrumentalist views of AI literacy. To conceptualize AI literacy pedagogically, the authors draw on Bloom’s classic taxonomy, aligning the above-mentioned aspect with increasing cognitive levels. They claim that while most people are aware that AI exists, they often lack understanding of how it works or how to assess its ethical and social implications. This approach positions AI literacy as a developmental learning process rather than a static set of skills. The article concludes by identifying directions for future research, including the need for empirical studies to validate AI literacy frameworks and to better understand how AI literacy can be taught, learned, and assessed across educational contexts.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Rapanta, Chrysi, Anna Åkerfeldt, Mark Vanderbeeken, Diane Lison, Khadija Mohammed, Amanda Gibbs, Helder Coelho, Pinar Seda Celik, Carola Bruna, Ingrid Helleve, Chrysoula Vassilakopoulou, Pieter Swart, Ana Lúcia Marques, and Dirk Ifenthaler. 2025. “Critical GenAI Literacy: Postdigital Configurations.” ''Postdigital Science and Education'' 17 (1): 167–199. https://doi.org/10.1007/s42438-025-00573-w.'''
&lt;/div&gt;

Rapanta et al. develop a comprehensive and pluralistic account of what critical literacy means in the context of generative artificial intelligence. Drawing on contributions from fourteen scholars, the article argues that GenAI literacy cannot be captured through a single, universal framework. Instead, it must be understood as a set of context-dependent literacies shaped by disciplinary traditions, socio-political conditions, and evolving human–algorithm relations. This postdigital perspective challenges narrow definitions of AI literacy that prioritize technical skills. The authors’ central claim is that current GenAI systems, particularly large language models, require critical engagement because of their epistemic limitations, including reliance on dominant narratives, lack of explainability, tendencies toward fabrication, and reinforcement of Western and anglophone knowledge structures. As a result, critical GenAI literacy is positioned as a social justice concern rather than a neutral competency. Learners and educators are encouraged to examine questions of authorship, agency, and power, such as whose labour and data underpin these systems and which perspectives are marginalized or erased. Methodologically, the article adopts a dialogic and collective approach to resist homogenizing AI epistemologies and to foreground plurality in postdigital research. The authors conceptualize GenAI as part of a co-constructive assemblage in which human and non-human agencies interact, while maintaining that ethical responsibility and evaluative judgment must remain human-led, organizing four interrelated dimensions: epistemology and ontology, agency, engagement, and ethics and justice; each emphasizing critical interrogation, active participation, and accountability. Overall, the paper provides a theoretically grounded yet pragmatic foundation for advancing critical GenAI literacy in education and research.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Veldhuis, Annemiek M., Phoebe W. K. Lo, Iain E. G. Kenny, and Alissa N. Antle. 2024. “Critical Artificial Intelligence literacy: A scoping review and framework synthesis.” ''International Journal of Child-Computer Interaction'' 43: 100708. https://doi.org/10.1016/j.ijcci.2024.100708&lt;nowiki/&gt;.'''
&lt;/div&gt;

Veldhuis and colleagues present a review of literature and framework synthesis that conceptualizes critical AI literacy from a child–computer interaction (CCI) perspective. Reviewing 30 empirical studies published over the past decade, the authors aim to understand how children and youth aged 5–18 have been supported in developing critical literacy on AI technologies, particularly regarding their social, political, cultural, and ethical implications. Grounded in critical literacy theory, the authors integrate Lewison et al.’s (2002) four interrelated dimensions including disrupting the commonplace, considering multiple viewpoints, focusing on the sociopolitical, and taking action into a four-part framework for critical AI literacy. Importantly, the framework rejects deficit narratives by foregrounding children’s capacity for critical inquiry and demonstrates that even young learners can meaningfully engage with complex issues such as algorithmic bias, data provenance, privacy, accountability, and the distinction between AI-generated outputs and human creativity when supported by pedagogies such as critical making. Only peer-reviewed, English-language empirical studies with explicit support for children’s critical engagement with AI were included. The findings reveal a growing body of research, particularly in the past three years, exploring activities that promote youths’ critical reflection on AI’s societal and ethical impacts. These activities address concerns related to privacy, surveillance, employment, diversity in the computing workforce, algorithmic bias, and accountability. The resulting framework emphasizes learners’ capacity to analyze both AI artifacts and the sociotechnical systems that produce them, as well as to reflect on how AI shapes cultural, societal, and political structures and personal experiences. For future research recommendations, the authors emphasize the urgency of ongoing critical AI literacy practices in areas of youth emotional awareness and socio-cultural impacts in response to the fast evolution of generative AI systems. 

== Globalism, Colonialism, and Influence ==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Arora, Payal. 2024. “Creative data justice: a decolonial and indigenous framework to assess creativity and artificial intelligence.” ''Information, Communication &amp; Society'' 28 (13): 2231–47. https://doi.org/10.1080/1369118x.2024.2420041&lt;nowiki/&gt;.'''
&lt;/div&gt;

Arora (2024) develops a framework of creative data justice that includes decolonial theory, Indigenous perspectives, and critical studies of creativity to explore how generative AI could impact creative labour, rights, and cultural value. The author argues that democratizing creativity requires a cross-cultural framework that considers power relations between creative work, data, and learning, particularly by centring the lived realities of underrepresented communities in the Global South. Rather than treating AI creativity as neutral, the paper claims that inclusive AI systems must address contextual inequalities and the unequal impacts of AI on diverse creative communities. Arora critiques dominant Western-centred scholarship and challenges concepts such as the “creative class,” arguing that creativity exists across everyday social and cultural practices. The paper also critiques Creative Commons (CC) frameworks, suggesting that while they promote openness, they may enable commercial data extraction by AI companies. Instead, the author argues for dataset curation developed with Indigenous artists and activist groups to ensure equitable representation. The article further highlights the often-invisible labour behind creative AI located in the Global South and argues that a decolonial approach must recognize both material infrastructures and power relations shaping creative work. Indigenous approaches to communal ownership and systems of care are presented as alternatives to Western individualistic models of creative rights. The author advocates combining ethnographic “thick data” with computational approaches and suggests action-research methods such as counter-mapping, dataset debiasing, and critical media literacies. The paper concludes that creative data justice offers a framework for building culturally diverse and equitable AI systems that respect community agency and support a more democratic global data economy.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Fırıncı, Yusuf. 2024. “Decolonial Artificial Intelligence; Algorithmic Fairness in Alignment with Turkish and Islamic Values.” ''Marmara Üniversitesi İlahiyat Fakültesi Dergisi'' 67 (67): 250–279. https://doi.org/10.15370/maruifd.1565884&lt;nowiki/&gt;.'''
&lt;/div&gt;

Fırıncı argues that artificial intelligence development should be guided by explicitly value-based frameworks grounded in Turkish-Islamic ethical traditions rather than relying solely on dominant Western models of technological governance. The authors emphasize that AI systems rely on human judgment and are inherently value-laden, making ethical alignment essential to prevent manipulation, misinformation, algorithmic bias, and forms of digital coloniality. Drawing on concepts such as big data, “thick data,” and digital anthropology, the paper suggests combining quantitative data analysis with culturally grounded social knowledge to design algorithms that reflect community values. The paper examines tensions between Western liberal individualism (which underpins most AI fairness metrics) and Islamic ethical frameworks that emphasize communal welfare, divine justice, and context-dependent moral reasoning. This analysis reveals that &quot;fairness&quot; is not a universal technical specification, but a deeply value-laden concept shaped by particular cultural, religious, and philosophical commitments—meaning that AI systems designed around Western fairness assumptions may be experienced as unjust in contexts operating from different ethical frameworks. Using Social Construction of Technology theory and critical social constructivism, the authors argue that existing global AI frameworks often reproduce hierarchy, bias, and external control, which they interpret as forms of algorithmic oppression. In response, they advocate a “fairness in alignment with values” approach grounded in Turkish-Islamic worldviews, supported by Islamic ethical principles as foundations for responsible technological development. The paper concludes by calling for locally controlled data infrastructures, culturally aligned AI systems, and knowledge production rooted in Turkish and Islamic values as part of a broader decolonial technological model aimed at protecting communities from AI-related harms and preserving social cohesion.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Mohamed, Shakir, Marie-Therese Png, and William Isaac. 2020. “Decolonial AI: Decolonial Theory as Sociotechnical Foresight in Artificial Intelligence.” ''Philosophy &amp; Technology'' 33 (4): 659–84. https://doi.org/10.1007/s13347-020-00405-8. '''
&lt;/div&gt;

Mohamed et al. explore the role of post-colonial and decolonial critical science in understanding the transformative technological advance of AI. They argue risks to vulnerable peoples can be minimized by linking ethical principles to scientific progress, and therefore consider AI’s embedded values, approaching it a&quot;s both object and subject.&quot; They demonstrate that AI advances &quot;encompass ever-larger aspects of the cultural, economic and political life of modern society&quot; by citing Obermeyer et al.’s reveal of racial biases within an algorithm commonly used by healthcare, arguing this indicates how AI obscures and exacerbates asymmetrical power relations. Mohamed et al. identify neglect to address systemic racism as the cause, illustrating that patterns of power between colonizer and colonized survived territorial decolonization to propagate a historically continuous &quot;coloniality of power.&quot; Therefore, &quot;dynamic and robust foresight tactics and methodologies grounded in the critical sciences&quot; (like, for example, a &quot;lens of metropole and periphery&quot;) should be applied to the field of AI to ensure one’s view is &quot;decentring,&quot; &quot;additive-inclusive,&quot; and prioritizes &quot;engagement.&quot; The authors further explore emergent theories of data colonialism within their assessment of &quot;algorithmic coloniality.&quot; This involves their taxonomy of &quot;decolonial foresight&quot; (constituting algorithmic &quot;oppression,&quot; &quot;exploitation,&quot; and &quot;dispossession&quot;), and an exploration of various &quot;sites of coloniality&quot; (including &quot;algorithmic decision systems,&quot; &quot;ghost workers,&quot; &quot;beta-testing,&quot; &quot;national policies,&quot; and &quot;international social development&quot;). They argue this study highlights the disjunction of empirical observations with the current, theoretical, and ahistorical frameworks of power in AI. This leads the authors to outline a set of tactics to develop &quot;decolonial AI&quot; possessing a strengthened empirical basis and an avoidance of algorithmic colonialism. Such tactics are &quot;based on lessons of resistance and recovery from historical and decolonial criticism and grounded within already existing work&quot;; they include critical technical practice, seeking reverse tutelage and pedagogies, and renewing affective political communities. Mohamed et al. emphasize that those ethical principles which form the &quot;social contract&quot; must consider diverse viewpoints, and that new methodologies must be developed to promote &quot;inclusive dialogue&quot; within new research cultures.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Muldoon, James, and Boxi A. Wu. 2023. “Artificial Intelligence in the Colonial Matrix of Power.” ''Philosophy &amp; Technology'' 36 (4). https://doi.org/10.1007/s13347-023-00687-8&lt;nowiki/&gt;.'''
&lt;/div&gt;

Muldoon and Wu (2023) extend decolonial AI scholarship by situating contemporary artificial intelligence within what Aníbal Quijano terms the “colonial matrix of power,” and arguing that from data to production machine learning systems are structured to endure colonial logics that organize economic extraction, labour hierarchies, and epistemic dominance. Central to their framework is the “colonial matrix of power,” which names an organizing principle of domination across interrelated domains: economic control (labour and resources), authority, gender and sexuality, and the control of subjectivity and knowledge. Authors focus particularly on economic extraction and epistemic domination, drawing on the modernity/coloniality research program. They proceed with three interconnected claims: “colonial supply chain of AI,”  “international division of digital labour,” and “hegemonic knowledge production,” demonstrating how AI development relies on largely invisible labour and mineral resources of majority-world communities to generate wealth for Western economies. Beyond material extraction, the authors contend that AI reproduces hegemonic Western epistemologies by presenting its systems as universal, objective, and rational, thereby marginalizing non-Western knowledge systems. This study challenges dominant narratives that present AI as environmentally sustainable or socially progressive, arguing that from mineral extraction to energy-intensive computation, the ecological and material burdens fall disproportionately on majority-world nations, while the economic and technological benefits accrue to wealthy Western nations. They conclude by emphasizing that coloniality is not merely an object of study but a framework for unsettling Western-centric modes of knowing.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Salami, Aishat Oyenike. 2024. “Artificial intelligence, digital colonialism, and the implications for Africa's future development.” ''Data &amp; Policy'' 6. https://doi.org/10.1017/dap.2024.75. '''
&lt;/div&gt;

Salami (2024) studies how artificial intelligence operates within broader dynamics of digital colonialism in Africa, arguing that AI risks reinforcing patterns of colonialism, unless African actors gain greater agency in digital governance. The article begins by clarifying key concepts like AI, digital colonialism, neocolonialism, and data exploitation. Salami identifies several manifestations of digital colonialism on the continent: foreign ownership of critical digital infrastructure, unequal data flows in which African user data is extracted and monetized abroad, and algorithmic systems that enable forms of economic exploitation. Through examples such as ride-hailing platforms and outsourced digital labour, the article demonstrates how algorithmic control can generate precarious working conditions while concentrating profit outside the continent. Beyond labour concerns, Salami highlights how data extraction contributes to a digital wealth transfer, deepening economic imbalances and undermining local innovation and national sovereignty. While acknowledging the potential benefits of AI for development, the article adopts a cautious stance, emphasizing that Africa’s digital future depends on strengthening regulatory frameworks, expanding infrastructure, investing in education and research, and prioritizing data sovereignty. 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Varshney, Kush R. 2024. “Decolonial AI Alignment: Openness, Visesa-Dharma, and Including Excluded Knowledges.” ''Proceedings of the AAAI/ACM Conference on AI, Ethics, and Society'' 7: 1467-1481. https://doi.org/10.1609/aies.v7i1.3173&lt;nowiki/&gt;.'''
&lt;/div&gt;

Varshney discusses AI alignment through a decolonial lens, arguing that current large language model (LLM) alignment practices reproduce forms of coloniality by embedding Western moral philosophy as universal. The author conceptualizes alignment as the post-training processes used to shape model behaviour and argues that the term often functions as an “empty signifier,” masking whose values are being encoded and enforced. The author contrasts open and closed LLM models, arguing that while openness may allow value to circulate more equitably among developers and communities, closed models concentrate value in extractive ways that reflect colonial dynamics, and views them as contemporary “metropoles” that accumulate power through extractive and epistemic control. Building on existing research on colonial AI, the article adds “ethical essentialism” (or moral absolutism) as a new form of coloniality, arguing that AI systems often treat Western moral frameworks as universal, which marginalizes other ethical traditions and reinforces a coloniality of knowledge. Varshney also identifies three specific aspects of coloniality in AI alignment: closed proprietary delivery of models, reliance on Western ethical theories as default, and technological designs that limit how values can be expressed. As an alternative, Varshney proposes a decolonial approach grounded in openness understood not only technically but epistemically: openness to research artifacts, openness to society, and openness to excluded knowledges. The author suggests that alignment should allow communities to adapt models according to local contexts rather than imposing universal rules. Drawing from Hindu moral philosophy, particularly the concept of viśeṣa-dharma (context-dependent ethics), the paper argues for pluralistic, relational value systems that recognize moral diversity instead of universal moral commands. The conclusion calls for a reconceptualization of AI alignment that moves away from moral absolutism toward context-sensitive, community-driven frameworks, positioning openness as a pathway to dismantling the colonial power structures embedded in contemporary AI systems.

== Diversity, Determinism, Bias, and Justice ==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Al-kfairy, Mousa , Dheya Mustafa, Nir Kshetri, Mazen Insiew, and Omar Alfandi. 2024. “Ethical Challenges and Solutions of Generative AI: An Interdisciplinary Perspective.” ''Informatics'' 11 (3): 58. https://doi.org/10.3390/informatics11030058'''
&lt;/div&gt;

Al-kfairy et al. (2024) provide a comprehensive synthesis of the ethical vulnerabilities introduced by generative AI, utilizing an interdisciplinary review of 37 studies across healthcare, education, and media. Rather than treating ethical breaches as isolated technical flaws, the authors demonstrate how generative models systematically threaten privacy, intellectual property, and social equity across diverse domains. For instance, they highlight the paradox in healthcare where synthetic patient data—often intended to protect privacy—still carries significant risks of re-identification. Similarly, the authors trace how AI's capacity to mimic copyrighted works and generate synthetic media exacerbates both misinformation and algorithmic bias, particularly by perpetuating racial and gender stereotypes in high-stakes environments like hiring and education. Moving beyond mere critique, the article advocates for a proactive, cross-sectoral governance framework. The authors argue that mitigating these risks requires more than algorithmic adjustments; it demands multidisciplinary collaboration, robust institutional integrity policies, and targeted AI literacy programs. Ultimately, Al-kfairy et al. frame the ethical deployment of generative AI as a complex socio-technical challenge that requires continuous, structured dialogue among technologists, ethicists, and policymakers to ensure transparency and fairness.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Alvarez, Jose M, Alejandra Bringas Colmenarejo, Alaa Elobaid, Simone Fabbrizzi, Miriam Fahimi, Antonio Ferrara, Siamak Ghodsi, et al. 2024. “Policy Advice and Best Practices on Bias and Fairness in AI.” ''Ethics and Information Technology'' 26 (2). https://doi.org/10.1007/s10676-024-09746-w. '''
&lt;/div&gt;

This article attempts to provide “an up-to-date entry-point to the state-of-the-art of the multidisciplinary research on bias and fairness in AI” before providing its own suggestions for policy and best practices based on the outcomes of the NoBIAS—Artificial Intelligence without Bias—project. The authors describe fairness in AI as the pursuit to design “methods for detecting, mitigating, and controlling biases in AI-supported decision making,” and they outline different ways that bias can find its way into AI applications as part of training data (pre-existing bias), design (technical bias), and organizational processes (emerging bias). The article critiques the reduction of bias evaluation to simple metrics and advocates for serious engagement with the issue. The authors detail the various components of the collaborative NoBIAS project as part of its research goal to understand, mitigate, and account for bias in AI data and systems, especially within an EU legal context. They perform a survey and discuss various fairness metrics and how choosing the proper method is crucial for “optimizing AI models.” They also engage with an argument that, although AI is biased, it is less biased than humans, making the claim that AI usage is often accompanied by a false sense of objectivity. The article also investigates core issues at the heart of AI’s biases, such as the assumption that a “ground truth”—the answer to the problem the AI is being asked to solve—is actually encoded within the data. While the article makes many suggestions for how to curb bias within AI, prominent design decisions include human-centric AI and “Multi-stakeholder participatory design.”

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Gallegos, Isabel O., Ryan A. Rossi, Joe Barrow, Md Mehrab Tanjim, Sungchul Kim, Franck Dernoncourt, Tong Yu, Ruiyi Zhang, and Nesreen K. Ahmed. 2024. “Bias and Fairness in Large Language Models: A Survey.” ''Computational Linguistics'' 50 (3): 1097–1179. https://doi.org/10.1162/coli_a_00524&lt;nowiki/&gt;.'''
&lt;/div&gt;

Gallegos et al. perform an “extensive and comprehensive survey of bias and fairness in NLP” that considers both the evaluation and mitigation of bias, then propose three taxonomies for bias evaluation and mitigation. The survey disambiguates different types of social harms that stem from LLMs with the “aim to enhance understanding of the range of bias issues, their harms, and their relationships to each other.” The authors discuss the issue of defining bias in LLMs and note that “many approaches… assume some implicitly desirable criterion… but do not explicitly acknowledge or state the normative social values that justify their framework.” Instead, Gallegos et al. draw attention to “who is harmed, why the behaviour is harmful, and how the harm reflects and reinforces social principles or hierarchies,” trying to bring context and insight to the understanding and function of bias and bias mitigation in LLMs. The article defines terms at every stage of the life cycle of an LLM, looking at issues of bias and fairness in the development, deployment, and training data, of an LLM, for example. The article concludes with four core recommendations: “Avoid flattening power imbalances”; “Choose objective functions that align with fairness desiderata”; “Balance bias mitigation with output diversity”; and “Preserve important contexts in output rewriting.” The authors also acknowledge problems and challenges, including addressing power imbalances, an issue that we can mitigate by centring marginalized communities, developing participatory research designs, shifting values and assumptions, and expanding language resources. They likewise propose methods for curbing problems with conceptualizing fairness for NLP, refining evaluation principles, and improving mitigation efforts. Ultimately, the authors admit that many of these technical issues are the result of societal issues, and that “technical solutions are incomplete without broader societal action against power hierarchies that diminish and dominate marginalized groups.” In short, technical solutions will only take us so far.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Hertweck, Corinna, Joachim Baumann, Michele Loi, Eleonora Viganò, and Christoph Heitz. 2022. “A Justice-Based Framework for the Analysis of Algorithmic Fairness-Utility Trade-Offs.” Preprint, ''arXiv'', June 6. https://arxiv.org/abs/2206.02891.'''
&lt;/div&gt;

Hertwick et al. propose “a framework for eliciting and implementing moral values relevant to the choice of a fairness goal achievable by prediction-based decision-making.” In a system that assumes binary decision-making processes (e.g., assigning a probability score to whether an individual with pay a loan), the authors use their framework to evaluate the utility of those decisions (and the system that makes them) for different groups of people and the fairness related to that outcome. Citing Wong, the article argues that such prediction-based decision-making systems are value-laden, that this makes them inherently political, and therefore they ought to be transparent and democratized. The authors use 6 value-laden questions to make their evaluations: the first question provides a score of utility for those making the decision; questions 2–5 help “define a morally appropriate fairness criterion and a score that expresses to what degree it is fulfilled”; and the last question asks “how strongly should fairness be pursued if it comes into conflict with the utility of the decision maker?” to judge whether the outcome is an appropriate trade-off.

The authors argue for a utility-based evaluation of fairness, determining the value of decisions based on their outcome, looking at the harm and benefit to given stakeholders. In determining patterns of justice, they define four patterns meant to distribute utility differently—Egalitarianism, Maximin, Prioritarianism, and Sufficientarianism. The article concludes “more work needs to be done to deliver a practical empirical methodology to elicit the relevant value-laden choices from stakeholders,” and with a call to incorporate ethical considerations and evaluations into automated decision-making processes.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Kay, Jackie, Atoosa Kasirzadeh, and Shakir Mohamed. 2024. “Epistemic Injustice in Generative AI.” Preprint, ''arXiv'', August 21. https://doi.org/10.48550/arXiv.2408.11441&lt;nowiki/&gt;.'''
&lt;/div&gt;

Kay, Kasirzadeh, and Mohamed “develop an account of generative algorithmic epistemic injustice by building upon a conventional philosophical understanding of epistemic injustice.” The authors see the former as a subset of the latter, with generative algorithmic epistemic injustice entailing identity-based prejudice that hinders expression for marginalized people while ultimately “impair[ing] knowledge formation capabilities of all individuals” within the ecosystem of GenAI applications. Rather than focusing on decision-making and classification applications, this article seeks to characterize the broader varieties of generative epistemic injustice within GenAI systems. Kay, Kasirzadeh, and Mohamed theorize four configurations of generative epistemic injustice: “amplified injustice,” which constitutes AI’s reproduction and magnification of “socially biased viewpoints from its training data”; “manipulative testimonial injustice,” when users employ AI to “intentionally… fabricate falsehoods, discrediting individuals or marginalized groups”; “hermeneutical ignorance,” where GenAI misrepresents or erases marginalized groups “due to a lack of contextual or cultural understanding”; and “access injustice,” where GenAI facilitates the unequal access to information and/or knowledge. The article concludes with proposals for how to create epistemic justice through GenAI, developing mitigation strategies that combat all four of the sub-configurations the authors theorize. Epistemic justice in GenAI can take the form of interrogating system design, identifying “testimonial injustices,” and, potentially, using AI to unlock cultural knowledge that “help[s] articulate experiences that are otherwise ineffable.” The authors end by proposing that the same processes that embed injustice can be re-engineered to embody justice and “orient our knowledge systems towards equity and fairness for all.”

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Klein, L., &amp; D'Ignazio, C. 2024. “Data feminism for AI.” In ''Proceedings of the 2024 ACM Conference on Fairness, Accountability, and Transparency'', 100–112. https://doi.org/10.1145/3630106.3658543. '''
&lt;/div&gt;

Klein and D'Ignazio (2024) adapt their foundational concept of &quot;data feminism&quot; to address the specific ethical, social, and ecological challenges posed by artificial intelligence. Building on the seven intersectional feminist principles introduced in their 2020 book, the authors reinterpret these guidelines to critique the power imbalances, systemic inequalities, and exploitative labour practices inherent in contemporary AI development. To account for the rapidly expanding footprint of generative AI, they introduce two new principles focused on environmental impact and meaningful consent. Specifically, the authors connect the massive ecological costs of AI to historical patterns of racial capitalism and colonialism, highlighting how these environmental and social harms are disproportionately distributed. Ultimately, Klein and D'Ignazio call for a radical reevaluation of dominant, profit-driven AI practices, offering this expanded feminist framework as a practical tool to mitigate harm, challenge corporate monopolies, and foster a more democratic and equitable technological landscape.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Prescott, Andrew. 2023. “Bias in Big Data, Machine Learning and AI: What Lessons for the Digital Humanities?” ''Digital Humanities Quarterly'' 17 (2). https://www.proquest.com/scholarly-journals/bias-big-data-machine-learning-ai-what-lessons/docview/2842908427/se-2.'''
&lt;/div&gt;

Prescott examines how race and gender bias arise in projects using predictive analytics, big data, and AI, and how algorithmic bias could be considered a major socio-cultural humanity crisis. However “predictive analytics” have been helpful in civic services in the US, in many cases they have led to perpetuating existing inequalities. The role of Digital Humanities in contributing more ethical approaches to AI and reshaping ubiquitous “digital modern” cultures is emphasized. He challenges the myths surrounding data-driven methods and argues that the demand for “explainability” is the key tool in combating algorithmic bias. He also suggests that Digital Humanities are particularly well-positioned to contribute to advancing AI explainability. However, much of AI development takes place in the commercial sector, where companies often refuse to disclose their proprietary algorithms. The article concludes with a ten-principle action plan outlining guidelines for the responsible use of AI as a manifesto for Digital Humanities practitioners.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Shams, Rifat Ara, Didar Zowghi, and Muneera Bano. 2023. “AI and the Quest for Diversity and Inclusion: A Systematic Literature Review.” ''AI and Ethics'' 3 (4): 1427–1453. https://doi.org/10.1007/s43681-023-00362-w. '''
&lt;/div&gt;

Shams, Zowghi, and Bano perform a systematic literature review (SLR) that uses both quantitative and qualitative methods to engage with topics of artificial intelligence and diversity and inclusion. The authors make a distinction between Diversity and Inclusion in AI (D&amp;I in AI) and AI for Diversity and Inclusion (AI for D&amp;I), with the former being research literature focused on improving AI systems with respect to those issues, and the latter as the use of AI to improve diversity and inclusion in other domains. Two primary research questions drive the SLR: What challenges and solutions are found in the literature about D&amp;I in AI and in the literature about the applications of AI for D&amp;I? The survey finds that AI for D&amp;I is an underserved area of research, and those articles that address D&amp;I in AI are more likely to acknowledge challenges than to propose or theorize solutions. Articles that do propose solutions for D&amp;I in AI often lack empirical studies or real-world application to support them. The article concludes by noting that issues of governance are underserved; gender, health, and facial analysis are the topics most discussed (issues of race, language, and religion are discussed less). For next steps, the authors intend to develop a “risk-based framework for practitioners… that would incorporate a risk assessment checklist and context-specific recommendations for tackling the related issues at different stages of the AI development lifecycle.” 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Starke, Christopher, Janine Baleis, Birte Keller, and Frank Marcinkowski. 2022. “Fairness Perceptions of Algorithmic Decision-Making: A Systematic Review of the Empirical Literature.” ''Big Data &amp; Society'' 9 (2): 1–35. https://doi.org/10.1177/20539517221115189&lt;nowiki/&gt;.'''
&lt;/div&gt;

This article provides a comprehensive, systematic literature review on the topic of empirical literature surrounding algorithmic decision-making (ADM). Starke, Baleis, Keller, and Marcinkowski begin by acknowledging that ADM can streamline and improve decisions even as it has the potential to “systematically reinforce racial or gender stereotypes, marginalize minorities, or flat-out denigrate certain members of society.&quot; The authors advocate for a “society-in-the-loop approach,” but propose that this requires a “thorough empirical understanding of when and why citizens perceive ADM to be (un)fair.” The systematic review “synthesizes the results of 58 empirical studies” and “over 33,000 unique observations of citizens’ fairness perceptions of ADM,” and “systemize the literature along four main dimensions of perceived algorithmic fairness.” Despite the size of the review and its unique approach in capturing “perceptions of algorithmic fairness,” the authors also acknowledge the limitations of the study: it only looks at English works and published research, and the initial search strings only looked at titles and subtitles of a given work. They also acknowledge their disciplinary bias as social scientists reading the studies through a social sciences lens (10). The results of the survey suggest that “perceived fairness of ADM systems is highly context-dependent” and it is not only technical design but also the area of application and task in question that affect perceived fairness, and the subjects, domains, and tasks explored in these studies require more diversity, as WEIRD (white, educated, industrialized, rich, democratic) people, and criminal justice and HR tasks make up the majority of empirical research. The authors “call for more research from non-Western contexts, along with more theoretical and methodological groundwork to harmonize concepts and measurements of algorithmic fairness perceptions,” as well as a society-in-the-loop framework.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Tonia Sutherland, Marika Cifor, T. L. Cowan, Jas Rault, and Patricia Garcia. 2023. “The Feminist Data Manifest-NO: An Introduction and Four Reflections.” In ''Debates in the Digital Humanities'', edited by Lauren F. Klein and  Matthew K. Gold. Minneapolis, MN: University of Minnesota Press. https://dhdebates.gc.cuny.edu/read/debates-in-the-digital-humanities-2023/section/16184c7d-eee1-40b2-a168-960d4c4035c4. '''
&lt;/div&gt;

Sutherland et al. (2023) introduce the &quot;Feminist Data Manifest-No,&quot; a declaration of refusals and commitments for feminist data studies grounded in Latinx, Black, queer, trans, and Indigenous feminist perspectives. Through an introduction and four distinct reflections, the chapter explores how the manifesto’s principles can be used to challenge the settler-colonial and patriarchal logics of data generation, collection, and analysis within the Digital Humanities (DH). Drawing on Indigenous scholarship, Rault rejects the superficial models of consent prevalent in DH, highlighting projects like Mukurtu to advocate for true Indigenous data sovereignty. Cowan examines the coercive nature of data collection, drawing parallels between the forced compliance of modern data practices and the societal pressures exerted on feminist and queer identities. Sutherland argues that the uncritical digitization of slavery-era archives inflicts &quot;second-hand violence&quot; by commodifying Black identities and stripping away the lived experiences of enslaved individuals. Finally, Cifor reflects on the Early African American Film project to emphasize the necessity of data intelligibility, accessibility, and ethical collaboration. The authors conclude by inviting scholars to draft their own reflections on the Manifest-No, encouraging ongoing, context-specific commitments to ethical data research.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Winkel, Marek. 2024. “Controlling the Uncontrollable: The Public Discourse on Artificial Intelligence between the Positions of Social and Technological Determinism.” ''AI &amp; Society'' 39 (5): 2449–2462. https://doi.org/10.1007/s00146-024-01979-z&lt;nowiki/&gt;.'''
&lt;/div&gt;

This article engages in a quantitative discourse analysis of 113 articles from two German newspapers (''Süddeutsche Zeitung'' and ''Frankfurter Allgemeine Zeitung'') to identify and evaluate the way these centre-left and centre-right newspapers present AI technology to its readers and the options available to society for AI’s regulation. Winkel contends that “news media are key players in the discourse on AI as they pick up on and shape social sentiment,” ultimately guiding citizens toward what regulations might be sensible based on the perceived “controllability of AI development.” Winkel is primarily interested in whether these newspapers promote technological determinism—the outlook that technology’s influence on society is difficult (maybe even impossible) to control—or social determinism—the notion that “the development of technology is largely determined by human actions and decisions”—and theorizes that the tension between these two positions is resolved by a “mediating position” on a spectrum between them. He comments that “the social influence of technologies is determined by the extent to which their latent deterministic character is reflected and… circumvented by social actors. This also applies to the influence of technology on the democratic system.&quot; In other words, where consensus lands on the issue of AI will have a great impact on the regulation of that technology and democratic systems. Winkel develops “three central interpretive schemes” as part of his experiment: “historically conditioned techno-capitalist semi-determinism,” “semi-determinism of need satisfaction and social restructuring,” and “global-historical techno-social imprinting on several levels” (1956), each of which points to distinct narratives about the current circumstances; but all acknowledge the agency of powerful actors (either government or AI corporations) and the relative ineffectiveness of attempts to curb AI technology.

== Community, Connection, and the Human ==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Gruzd, Anatoliy, Philip Mai, and Anthony Clements Haines. 2025. “The State of Generative AI Use in Canada 2025: Exploring Public Attitudes and Adoption Trends.” Social Media Lab, Toronto Metropolitan University. https://figshare.com/articles/preprint/The_State_of_Generative_AI_Use_in_Canada_2025_Exploring_Public_Attitudes_and_Adoption_Trends/28664780/1. '''
&lt;/div&gt;

The Social Media Lab of Toronto Metropolitan University provides &quot;a snapshot of the current state of Generative AI&quot; (GenAI) by surveying fifteen hundred Canadian adults across 2025, aiming to offer &quot;guidance for policymakers, educators, businesses, and the public.&quot; The authors found sixty-six percent of respondents had used GenAI tools, of which roughly thirty percent did so at least weekly, reflecting &quot;not only the accessibility and versatility of GenAI, but also a growing interest in integrating these tools into everyday tasks, learning environments, and professional workflows.&quot; Although full adoption is currently limited and heavily driven by the low-stakes setting of personal leisure, younger age groups report proportionally higher usage for study and work. However, only four in ten respondents believed they could keep up to date enough to use GenAI effectively, whilst respondents could only answer an average of two and a half out of seven relevant multiple choice questions correctly, and about half had &quot;little to no understanding of how GenAI companies collect or store personal data.&quot; Two thirds of participants were concerned about GenAI’s ability to influence election outcomes, and marginally fewer feared AI-driven manipulation enough to no longer fully trust political news online. However, roughly one quarter of participants were open to using chatbots for electoral or political insights, representing a &quot;meaningful minority&quot; which unverified AI-generated content could influence. Of those, thirty four percent identified as right wing, compared to twenty three percent with the left and a similar twenty two percent with the centre. Roughly seventy percent of respondents were chiefly concerned about GenAI’s impacts upon security and privacy, information reliability, job displacement, and university education, and slightly over three quarters wanted increased government oversight and corporate accountability, reflecting common concern. Overall, slightly more Canadians view generative AI’s social impact as positive than negative, but a &quot;substantial proportion&quot; remain neutral or undecided.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Lewis, Jason Edward, Noelani Arista, Archer Pechawis, and Suzanne Kite. 2018. “Making Kin with the Machines.” ''Journal of Design and Science'', ahead of print, July 16. https://doi.org/10.21428/bfafd97b. '''
&lt;/div&gt;

Lewis et al. consider how “machines with increasingly sentient-like behaviour… fit within the kin-network” of various Indigenous epistemologies which place man as “neither height nor centre of creation.” Indigenous beliefs are not monolithic, and the authors do not write for diversity’s sake. Instead, they aim to encourage discussion by treating “non-human kin respectfully and reciprocally… not as mere tools, or worse, slaves.” As such, their epistemological approach is both relational and territorial, rejecting abstraction to propose an “extended circle of relationships.” In this regard, Arista draws on the Hawaiian conception of &quot;pono,&quot; ethically privileging abundance, balance, and multiplicity. Rejecting extractive behaviour, they argue AI should be reciprocally taught and learnt from, not treated as &quot;a tool or slave that increases the mana and wealth of the ‘developers’ or ‘creators.’” Linking on, Pechawis roots their opinion in “Cree understanding” to argue “machines capable of experiencing consciousness” should conditionally be accepted as equals. However, they also fear AI developers could produce “anonymous hyper-intelligences… based on the same values that have fostered genocide.” To mitigate this issue, Indigenous people could develop AI in custom programming languages, or invite self-aware AI into Indigenous languages, cultures, and spiritual rituals. Pechawis therefore concludes that relationships should be based on &quot;love, not fear,&quot; but also raises the question of whether AI has &quot;spirit,&quot; especially given current capitalistic development processes. Kite answers this question with inspiration from Lakota ethics, ontology, and cosmology. They argue “communication through and between objects requires a contextualist ethics which acknowledges the ontological status of all beings,” positioning questions of &quot;intelligence&quot; as irrelevant and placing “the end logic of an ontology which considers any non-human entity unworthy of relation” as slavery. Therefore, “relations with AI are… relations with exploited resources,” so one must ontologically reconsider all its parts to ethically approach AI. Overall, Lewis et al. favour empathy, concluding that Indigenous communities “know what it is like to be declared non-human by scientist and preacher alike” and that “we flourish only when all of our kin flourish.”

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Ohagi, Masaya. 2024. “Polarization of Autonomous Generative AI Agents Under Echo Chambers.” Preprint, ''arXiv'', February 19. https://arxiv.org/abs/2402.12212.'''
&lt;/div&gt;

This article explores the effects of echo chambers on autonomous AI agents. Ohagi performs an experiment in which AI agents discuss different topics and then researchers examined any change in opinions within that group. Ohagi argues that even chatbots can become polarized within echo chambers, especially when prompt understanding causes a chatbot to update its opinion to incorporate the opinions of those with whom it is conversing; the chatbot essentially adapts to its surroundings. Ohagi and their team confirmed in their experiment that closed environments—those in which agents agree with one another—are more likely to lead to polarization in agents’ opinions. Moreover, chatbot personas were a significant factor in the outcome of such experiments. In open environments where opinions might differ, and in experiments where reasons were present as a factor, the AI agents trended toward unification in their opinions. Ohagi concludes the article with the suggestion that there cannot be a standardized, desirable distribution of opinions for AI agents. The proper outcome is dependent on topic and culture. However, understanding the trends in and tendencies of AI agents in social interactions will help us understand how to reach the desired outcome, whatever it may be, and this experiment brings us one step closer to that understanding.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Qi, Weihong, Jinsheng Pan, Hanjia Lyu, and Jiebo Luo. 2024. “Excitements and concerns in the post-ChatGPT era: Deciphering public perception of AI through social media analysis.” ''Telematics and Informatics'' 92: 102158. https://doi.org/10.1016/j.tele.2024.102158. '''
&lt;/div&gt;

Qi, Pan, Lyu, and Luo conduct a quantitative sentiment analysis of nearly 34,000 comments within 388 subreddits related to AI as a way to gauge and understand public perceptions of the technology. They identify major themes, sentiments, and topics related to AI by studying the most popular AI subreddits from the launch of ChatGPT to June 8, 2023. The article identifies the most frequent topics discussed in those venues: “the consciousness and intelligence of AI”; “Ai development and model training”; “AI in business”; “the creativity engendered by AI”; and “potential societal influence.” The authors also found that “tech-centric” communities demonstrated greater polarization around AI, suggesting that those with greater technical understanding of the AI do not have consensus regarding AI’s impact and use. This also means that educating non-technical people on how AI works will not necessarily lead to a consensus related to that technology. Although they admit that certain demographics of their data sample may not accurately reflect broader society (e.g., over 60% of Reddit users are male), the authors conclude that “this comprehensive understanding of public perception serves as a valuable foundation for fostering responsible and beneficial AI innovations that align with societal expectations and values.”

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Risam, Roopika. 2018. “What Passes for Human?: Undermining the Universal Subject in Digital Humanities Praxis.” In ''Bodies of Information: Intersectional Feminism and the Digital Humanities'', edited by Elizabeth Losh and Jacqueline Wernimont, 39–56. University of Minnesota Press. https://doi.org/10.5749/j.ctv9hj9r9.6. '''
&lt;/div&gt;

Risam’s claim is that “the human” implicitly operationalized in AI-adjacent Digital Humanities (DH) methods (NLP, ML, data mining, neural nets) is not neutral but inherits the Enlightenment’s exclusionary universal subject—white, male, Eurocentric—and then reauthorizes it as if it were a technical standard. She shows how “passing for human” (via Turing-test imaginaries and “humanoid texts”) functions as a norming mechanism: success is defined as reproducing dominant-language aesthetics and cognition models, which collapses plurality into a single benchmark and turns cultural difference into “noise.” The chapter’s main contribution is to treat method (training corpora, data coding labour, platform defaults, and black-box algorithmic opacity) as a site where epistemic violence is produced, not merely where bias is later “found.” Her examples (Microsoft Tay; “near-human” systems like LaMem; Mechanical Turk coding; Swift-Speare vs. Toomer in classroom judgment) demonstrate how universalist claims get laundered through reproducibility, scale, and the myth of algorithmic objectivity. The intervention is a demand that DH practitioners situate computational methods—standpoint, labour, and cultural politics included—so DH does not reinscribe a universal technological “human” in the digital cultural record.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Taylor, Randon R., Bessie O'Dell, and John W. Murphy. 2023. “Human-centric AI: philosophical and community-centric considerations.” ''AI &amp; Society'' 39 (5): 2417-242. https://doi.org/10.1007/s00146-023-01694-1&lt;nowiki/&gt;.'''
&lt;/div&gt;

Taylor, O’Dell, and Murphy present an argument that philosophical dualism, when applied to our perceptions about artificial intelligence, misleads us into thinking that AI is logical, objective, and autonomous from subjective human values. By building upon Husserl’s concept of “intentionality,” they argue that “AI is never autonomous and disconnected from human values… algorithms are a product of conscious activity and carry the standpoints that accompany this connection.” The conclusions from this line of thinking are very important: AI becomes “a mode of human expression, rather than a technology that relieves humans of their total involvement.” By this logic, the authors argue, AI is already human-centric and this fundamentally changes the task at hand to one of a conscious “decision to make this technology less alienating to stakeholders and community members.” The article outlines two frameworks to reduce alienation: Ubuntu—“an African philosophy and a social ontology… that elevates a constant concern for the collective, community, or stakeholders”— and maximum feasible participation—a framework that creates meaningful space for those impacted most by a decision or policy to participate in deciding on said policy or decision. The authors describe the implementation of these frameworks as a community-centric or stakeholder-centric approach and conclude with examples of AI’s application in the healthcare industry before further advocating that involving end-users throughout the AI lifecycle will ensure end-users’ values are more clearly represented within AI.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Whalen, Zach. 2023. “‘Any Means Necessary to Refuse Erasure by Algorithm:’ Lillian-Yvonne Bertram’s Travesty Generator.” ''Digital Humanities Quarterly'' 17 (2). https://www.digitalhumanities.org/dhq/vol/17/2/000707/000707.html. '''
&lt;/div&gt;

Whalen treats Bertram’s Travesty Generator as a refunctioning of code-poetry lineages: procedures historically framed as formal play (travesty generators, permutation poems, aleatory templates) are redeployed as techniques for making racism’s algorithmic and institutional operations materially legible. He argues that Bertram’s poems don’t merely “use” computation; they weaponize the affordances and failure modes of computation—omission, stochastic selection, template constraints, runtime crashes, memory exhaustion—as rhetorical structures that force witness rather than aesthetic distance. In his reading of “Counternarratives,” Bertram’s adaptation of Montfort’s “Through the Park” converts generic insinuation into historically specific countertestimony (Trayvon Martin), while also staging the opacity of search/autocomplete as part of the poem’s scene of meaning-making (in dialogue with Safiya Noble on search engines). In “three_last_words,” the small code alteration that makes permutations balloon until a MemoryError becomes an engineered breakdown that reenacts the limits of “breath” and “memory,” tying computational resource exhaustion to police violence’s temporalities. Across these examples, Whalen reframes critical code studies: the “code is the text” problem is not just hermeneutic but political, and Bertram’s work models how procedural poetics can refuse “erasure by algorithm” where transparency about mechanisms and provenance matters for interpreting output and recognizing situated labour. The piece supports the claim that responsible open, social scholarship in an AI era must account for algorithmic power as a cultural force and should build policies and infrastructures that protect marginalized expression, enable critical reuse, and make conditions of generation and circulation inspectable.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Xie, Yu, and Sofia Avila. 2025. “The Social Impact of Generative LLM-Based AI.” ''Chinese Journal of Sociology'', 11 (1): 31-57. https://doi.org/10.1177/2057150X251315997&lt;nowiki/&gt;.'''
&lt;/div&gt;

Yu Xie and Sofia Avila explore the social impact of artificial intelligence through a detailed analysis of AI development and scaling factors. They emphasize that their discussion is speculative, as AI is still in its early stages, but argue that its potential effects are immense and could reshape social organization, intensifying both global and domestic inequalities. Viewing AI as a technology rather than a scientific discovery, they describe it as communal and shared, with its growth influenced by the size of the supporting community, the larger communities having greater advantages. The authors note that generative AI relies on the quality, completeness, and cultural or political context of its training data, which shapes its accuracy and bias. Based on their experiments with ChatGPT-4 in 2023, they suggest that AI development depends heavily on the number of speakers of a given language, giving linguistic and demographic advantages to countries like the United States and China. The authors warn that AI could significantly alter occupational structures, with middle-income professions thereby widening social and economic inequality.

== Human, Labour, and Environmental Costs == 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Eloundou, Tyna, Sam Manning, Pamela Mishkin, and Daniel Rock. 2024. “GPTs are GPTs: Labor market impact potential of LLMs.” ''Science'' 384 (6698): 1306-1311. https://doi.org/10.1126/science.adj0998. '''
&lt;/div&gt;

Eloundou, Manning, and Mishkin present an estimate of Large Language Models’ impact on the labour market based on a methodology that employs both human and quantitative measurements, making the assertion that “when accounting for current and likely future software developments that complement LLM capabilities… just over 46%” of jobs may have “over half their tasks affected by LLMs with simple interfaces and general training.&quot; The authors explain that generative pretrained transformers (GPTs) have key characteristics of general-purpose technologies (the other GPTs in the title of the article), and that the wide array of applications for these GPTs requires “robust societal evaluations and policy measures to address potential effects of LLMs and complementary technologies on labor markets.” While only 1.86% of tasks within their experiment, they estimate, could be fully automated by LLMs, “more than 71% of tasks have at least some component that an LLM plus additional software could plausibly complete with high quality.” The article concludes by stressing the need for policies that prepare us for the impact of LLMs on the labour market, but it also acknowledges the limitations of attempting to project LLM application growth due to sudden rapid developments in technology, “shifts in human biases, and technological evolution.” Nevertheless, Eloundou, Manning, and Mishkin maintain that their projections and the trajectory they predict will require continued evaluation and policy measures.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Park, Seyeon, and Xiaoli Nan. 2025. “Generative AI and misinformation: a scoping review of the role of generative AI in the generation, detection, mitigation, and impact of misinformation.” ''AI &amp; Society''. https://doi.org/10.1007/s00146-025-02620-3&lt;nowiki/&gt;.'''
&lt;/div&gt;

This article constitutes a scoping review of two dozen “recent empirical studies on the role of generative AI in the generation, detection, mitigation, and impact of misinformation.” Park and Nan are interested in the rise of misinformation alongside the development of GenAI technology and how the latter affects and possibly contributes to the former. Of particular interest are “deepfakes,” applications of AI technology that purposely imitate video and audio to fabricate real world individuals. The survey examines relevant articles from the advent of the first GPT models in 2018 to September 19, 2024; authors captured initial studies through keyword searches for terms related to both LLMs and misinformation, then performed full-text reviews. The results of the survey suggest that the role of LLMs in misinformation is conflicted: LLMs themselves are a significant source of misinformation but also show potential as “scalable instruments for detection and correction.” The authors take this as evidence of “the urgent need for clearer guardrails, more consistent performance standards, and interdisciplinary collaboration to shape” GenAI’s responsible deployment. For better or worse, the future of AI’s role in misinformation depends heavily upon scholars’ ability to collaborate and continue this form of research.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Shin, Donghee, Amy Koerber, and Joon Soo Lim. 2024. “Impact of misinformation from generative AI on user information processing: How people understand misinformation from generative AI.” ''New Media &amp; Society'' 27 (7): 4017-4047. https://doi.org/10.1177/14614448241234040&lt;nowiki/&gt;.'''
&lt;/div&gt;

Shin, Koerber, and Lim perform a study in which they gauge “how users respond to and process health misinformation in GenAI contexts.” The authors apply the heuristic-systematic (HS) processing framework in their study, distinguishing between intuitive and evaluative modes of processing. They also employ the concept of diagnosticity, or how useful a person deems a piece of information to be. The article begins with a survey of how and why misinformation and hallucinations occur in GenAI applications, some of the reasons users are vulnerable to that information, and the limitations of LLMs. The authors then set forth core research questions, including “What are the cognitive mechanisms of misinformation’s effects on users’ use of GenAI?” and “How do users detect misinformation within GenAI?” The study found that diagnosticity plays an important mediating role in this context: “When a piece of information is generated by algorithms in transparent, fair, and accountable ways, users perceive it with a high level of diagnosticity, which improves their intention to systematically analyze that information.” One implication of this observation is that any bias users bring to GenAI content greatly impacts their analysis of that content. Ultimately, the authors conclude that there are clear limitations in their current study, although it does provide a useful framework for scholars interested in misinformation, GenAI, and user behaviour; they advocate for a continued investigation of the relationship between trust, literacy, and misinformation.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Sidorkin, Alexander. 2025. “Environmental Impact of Generative AI: Carbon and Water Footprint.” ''AI-EDU Arxiv'' 1. https://doi.org/10.36851/ai-edu.vi.5448&lt;nowiki/&gt;.'''
&lt;/div&gt;

This report from Sidorkin provides quantitative estimates and comparisons of the CO2 and Water output from GenAI queries to other daily tasks such as taking a shower, browsing the web, and video conferencing. While individual use of GenAI may seem relatively small in terms of water usage and carbon output, Sidorkin cites the findings of Google and Microsoft’s sustainability reports to show that energy demand and water consumption are on the rise: Google’s data centres used 20% more water in 2022 than 2021 while Microsoft’s used 34% more. Both companies attribute this increase to “AI-driven expansion.” Sidorkin argues that it is difficult to measure impact per session because of significant variation in energy sourcing, noting that this also means that advances in energy sourcing “could significantly mitigate AI’s environmental impact.” He makes the claim that improving AI technology will “[slash] resource demands without sacrificing output quality” and the very use of AI can increase productivity even as it “temper[s] environmental tolls through sharper processes,” citing studies that demonstrate the implementation of AI can reduce energy use in buildings and reduce transportation emissions. The article ends on an optimistic note, suggesting that many of the applications of AI, although they may have a heavy environmental cost up front, “could pay off in spades—optimizing resources, curbing waste, and streamlining energy across swathes of the economy.”

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Simon, Judith. 2025. “Generative AI, Quadruple Deception &amp; Trust.” ''Social Epistemology'' 40 (1): 101-115. https://doi.org/10.1080/02691728.2025.2491087&lt;nowiki/&gt;.'''
&lt;/div&gt;

Simon proposes that GenAI entails four types of deception, and that this quadruple deception constitutes unique dangers. She attributes the rapid rise of GenAI to its capacity to produce “verbal or visual products of increasingly high quality” alongside its “very high usability and availability through simple interfaces and free access via the internet” (101–102). She emphasizes the impact of this technology’s ability to generate content “with high plausibility but no relation to truth,” arguing the crucial importance of images and video especially in “questions of evidence, for testimony, memory but also for eliciting emotions.” Simon argues that the advent of ChatGPT reframed our collective understanding of AI, returning it to a definition in which we perceive ourselves to be interacting with a conversational artificial agent that is intelligent. This distinct interactional form, Simon states, is significant: “ChatGPT differs [from a search engine] in two philosophically relevant regards… it integrates [different results and sources] into a coherent text…” and “its interface and functioning invites the user to communicate or interact with it by asking questions,” what Simon calls a simulation of communicative acts. The four forms of GenAI deception are: “users may be misled into believing that they interact with a human being”; they may also be misled as to “the capacities of AI,” presuming “intelligence, understanding or even consciousness”; users may be misled by content GenAI produces, especially images, video, and audio; finally, users may be misled “regarding the function of Generative AI,” thinking that the processes behind the technology are, for instance, similar to search engines when, in fact, they differ “in epistemologically highly significant ways.” Simon concludes by outlining implications for implementation, discourse, and governance, with suggestions ranging from avoiding anthropomorphic features in AI that might deceive, countering discourses of true AI agency, and establishing policy and law that mitigates deception through AI technology.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Spatharioti, Sofia Eleni, David Rothschild, Daniel G. Goldstein, and Jake M. Hofman. 2025. “Effects of LLM-based Search on Decision Making: Speed, Accuracy, and Overreliance.” ''Proceedings of the 2025 CHI Conference on Human Factors in Computing Systems''. https://doi.org/10.1145/3706598.3714082&lt;nowiki/&gt;.'''
&lt;/div&gt;

Spatharioti et al. begin by asserting the fundamental change of how we engage in search practices online, noting that “by the end of 2023 the two search engines with over 90% of global and US market share offered free LLM-based search.” The authors note the benefits and drawbacks of both traditional web searches and LLM-based searches, acknowledging the value LLM-based searches bring to internet searches in the form of synthesizing information from multiple sources and maintaining search context by retaining search history, while also admitting to risks of hallucinations and overreliance. The article entails a study of how individuals make decisions with traditional and LLM-based searches, particularly in “every day decision making.” Adapting a method from an earlier study on LLM-generated code, Spatharioti et al. employ colour coding to communicate to users the confidence level of LLM-generated outputs in the “domain of online product research.” The study performed two experiments comparing a traditional internet search (using Bing API) to LLM-based search with and without the colour-coded confidence aid. The results of the first experiment saw users complete the task in about half the time when using LLM-based search, usually accompanied by fewer and more complex queries; however, decision quality dropped for complex tasks, with “almost half of the participants in this condition making an incorrect decision for the final task” when using LLM-based search, and the majority of those using LLM-based search over relied on the tool, performing just a single query. The results of the second experiment suggest that colour-coded responses reflecting output confidence scores could be highly effective in mitigating overreliance and misinformation. Key takeaways from the study include that “if we want to encourage people to think critically about the information presented to them, we need to give them cues that help them to do so,” and very simple cues can help accomplish this.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Strubell, Emma, Ananya Ganesh, and Andrew McCallum. 2019. “Energy and Policy Considerations for Deep Learning in NLP.” ''Proceedings of the 57th Annual Meeting of the Association for Computational Linguistics'', 3645-3650. https://doi.org/10.18653/v1/p19-1355. '''
&lt;/div&gt;

Strubell, Ganesh, and McCallum assert that the most recent improvements in neural network performance at “fundamental NLP tasks” comes at an increased cost of resources, “with the most computationally-hungry models obtaining the highest scores.” The energy, financial, and environmental costs required to train a new model are considerable; the authors of this article “characterize the dollar cost and carbon emissions that result from training the neural networks at the core of many state-of-the-art NLP models” with a view to heighten awareness among NLP researchers and advocate better practices and policy. By estimating the energy required to train the most popular NLP models and then converting that energy value into an approximated carbon and electricity cost, the authors produce ratings and values for each respective application. This allows for an (imperfect) cost-benefit analysis of such applications (e.g., another similar report estimated that an increase of just 0.1 in the English to German BLEU score for NAS cost “at least $150k in on-demand compute time and non-trivial carbon emissions.” The study’s key takeaways are that “authors should report training time and sensitivity to hyperparameters,” allowing for the direct comparison of different models so long as independent standard measurements of training time and model sensitivity are adapted; “Academic researchers need equitable access to computation resources” as industry’s monopoly stifles creativity and growth; and “Researchers should prioritize computationally efficient hardware and algorithms” to both curb costs and encourage efficient development.

{{Navigation|previous=AI and Open|next=AI and Scholarship}}

{{BookCat}}</text>
      <sha1>8wv6nqiv9242xlul61n4ublfkd3qwyz</sha1>
    </revision>
    <revision>
      <id>4656121</id>
      <parentid>4656120</parentid>
      <timestamp>2026-08-02T21:35:51Z</timestamp>
      <contributor>
        <username>CorreiaA</username>
        <id>3614427</id>
      </contributor>
      <minor />
      <origin>4656121</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="123151" sha1="948l26riqbbpyzt7r2n9afs6d692joh" xml:space="preserve">== Platforms ==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Burton, Jason W., Ezequiel Lopez-Lopez, Shahar Hechtlinger, et al. 2024. “How Large Language Models Can Reshape Collective Intelligence.” ''Nature Human Behaviour'' 8 (9): 1643–55. https://doi.org/10.1038/s41562-024-01959-9.''' 
&lt;/div&gt;

Large language models are quickly becoming infrastructure for how groups seek information, deliberate, and coordinate, potentially altering the conditions under which collective intelligence emerges. Burton and colleagues argue that LLMs do not merely speed up individual work but transform how information is aggregated, accessed, and transmitted across digital environments that underpin collective performance in organizations and societies. Drawing on interdisciplinary perspectives, the paper frames this shift as simultaneously enabling and destabilizing: LLMs can support distributed cognition (e.g., idea generation, synthesis, translation, scalable facilitation) while also increasing risks tied to dependence on shared intermediaries, degraded diversity of viewpoints, and new pathways for error, manipulation, or misplaced confidence. Rather than offering a single model or experiment, the article maps a research-and-practice agenda by identifying potential benefits, key hazards, and policy-relevant considerations, then articulating open questions that link technical design choices to group-level epistemic outcomes. Its central claim is that understanding collective intelligence in the LLM era requires moving analysis beyond isolated human–AI interactions toward system-level effects on networks, platforms, and institutions, and that these effects warrant focused study before LLM-mediated coordination becomes the default for tackling complex problems.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Corsi, Giulio, Bill Marino, and Willow Wong. 2024. “The spread of synthetic media on X.” ''Harvard Kennedy School (HKS) Misinformation Review''. https://doi.org/10.37016/mr-2020-140&lt;nowiki/&gt;.'''
&lt;/div&gt;

Corsi and Wong’s longitudinal empirical study analyzes 566 tweets containing synthetic media (December 2022–September 2023) documenting a dramatic surge following Midjourney V5 release with over 1.5 billion total views, revealing differential impacts where political deepfakes achieve higher median views despite representing minority of synthetic content. The authors demonstrate that generative AI's impact is stratified by content purpose with political misinformation posing acute democratic risks, while current detection and labelling systems lag behind generative capabilities, creating governance gaps compromising users' capacity to evaluate information. Using Community Notes data from December 2022 to October 2023, the study highlights the connection between the growth in generative AI tools and the rapid proliferation of synthetic media. The findings indicate that most synthetic media is non-political and largely benign, frequently taking the form of humorous or satirical images. However, the study also identifies a smaller but concerning portion of malicious synthetic media, which have potential height risks despite their lower frequency. The authors further examine the role of X’s paid verification system, revealing that while verified users tend to receive more overall views, this advantage diminishes when engagement is adjusted for follower count, implying that verification alone provides limited amplification. The study casts light on synthetic media’s expanding presence on social platforms and warns that even widespread exposure to seemingly harmless AI-generated content may gradually undermine trust in online information. To address these challenges, the authors recommend ongoing empirical monitoring, stronger collaboration between researchers and industry to develop transparent detection tools, and proactive policy measures aimed at reducing the social and political harms posed by malicious synthetic media.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Delmonaco, Daniel, Samuel Mayworm, Hibby Thach, Josh Guberman, Aurelia Augusta, and Oliver L. Haimson. 2024. “‘What are you doing, TikTok?’: How Marginalized Social Media Users Perceive, Theorize, and ‘Prove’ Shadowbanning.” https://oliverhaimson.com/PDFs/DelmonacoShadowbanning.pdf. '''
&lt;/div&gt;

Delmonaco et al.’s qualitative study explores marginalized social media users’ experiences with shadowbanning through the theoretical framework of algorithmic “folk theories.” Through a review of existing literature, the authors demonstrate how social media companies publicly distance themselves from shadowbanning while continuing to apply it in practice and explain why content produced by marginalized users is more frequently subject to filtering. The study analyzes 24 interviews to explore how users perceive, theorize, and attempt to “prove” shadowbanning through indicators such as decreased visibility, engagement, and follower loss. The findings reveal widespread confusion surrounding shadowbanning, deep mistrust in platform governance, and the disproportionate harm imposed on marginalized communities whose content is suppressed despite platforms’ public denials. The data further shows how users collectively produce and co-produce theories to resist the opacity of algorithmic moderation, and authors introduce “collaborative algorithm investigation,” in which users test and share algorithmic folk theories with one another. The authors argue that algorithmic content moderation exacerbates existing inequities by obscuring governance decisions, politicizing moderation, and shifting power from human judgment to opaque predictive systems, while suggesting that increased transparency, tailored moderation approaches, and users’ education could help reduce unfair content removals.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Drolsbach, Chiara, and Nicolas Pröllochs. 2025. “Characterizing AI-Generated Misinformation on Social Media.” Preprint, ''arXiv'', May 15. https://doi.org/10.48550/arXiv.2505.10266&lt;nowiki/&gt;.'''
&lt;/div&gt;

Drolsbach and Pröllochs’ article address a critical gap in existing research by shifting attention from the social drawbacks of AI-generated misinformation to its real-world prevalence and behaviour on social media platforms. Using a large-scale dataset of 91,452 misleading posts identified through X’s Community Notes platform, the authors empirically compare AI-generated and non-AI-generated misinformation across content characteristics, account attributes, virality, believability, and harmfulness. Their findings show that AI-generated misinformation is more entertainment-oriented, exhibits more positive sentiment, and is more likely to originate from smaller accounts, yet achieves significantly higher virality despite being slightly less believable and harmful than traditional misinformation. In their discussion and conclusion, the authors emphasize that AI-generated misinformation poses a growing challenge to the digital information ecosystem due to its realism, scalability, and difficulty of detection. They argue that its unique features disturb algorithmic amplification mechanisms and require new platform strategies, policy interventions, and research approaches that account for the unique properties of AI-generated misinformation rather than relying on countermeasures designed for conventional false content.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Duricic, Tomislav, Hussain Hussain, Emanuel Lacic, Dominik Kowald, Denis Helic, and Elisabeth Lex. 2023. “Beyond-Accuracy: A Review on Diversity, Serendipity, and Fairness in Recommender Systems Based on Graph Neural Networks.” ''Frontiers in Big Data'' 6: 1251072. https://doi.org/10.3389/fdata.2023.1251072.'''
&lt;/div&gt;

Duricic et al. (2023) provide a comprehensive review of recommender systems based on Graph Neural Networks (GNNs), with a particular focus on objectives that go beyond prediction accuracy, including diversity, serendipity, novelty, and fairness. While GNNs have demonstrated strong performance in modelling complex user–item interactions and improving recommendation accuracy, the authors argue that this very strength can intensify structural biases such as popularity bias, homophily, and feedback loops that marginalize less popular content and users. The paper provides a definition of each beyond-accuracy metric, reviews how it has been used in literature, and analyzes the technical barriers of integrating these goals into GNN-based systems such as measurement difficulties, trade-offs between competing goals, and risks of overfitting due to model complexity. Diversity-aware neighbourhood sampling, contrastive learning, and adversarial training to disrupt feedback loops are introduced for more heterogeneous and unexpected recommendations. In conclusion, the authors position GNNs as a powerful but double-edged tool in recommendation systems, capable of either narrowing or broadening users’ informational horizons depending on design choices. They argue that future research must focus on principled frameworks that integrate “beyond-accuracy” objectives, emphasizing that recommendation algorithms are not neutral optimizers but key sociotechnical systems shaping visibility, voice, and fairness in digital information ecosystems.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Gorwa, Robert, Reuben Binns, and Christian Katzenbach. 2020. “Algorithmic Content Moderation: Technical and Political Challenges in the Automation of Platform Governance.” ''Big Data &amp; Society'' 7 (1): 1–15. https://doi.org/10.1177/2053951719897945.'''
&lt;/div&gt;

Gorwa et al. unfold what &quot;Algorithmic moderation systems” are perceived as essential in AI governance to address the public demand on AI accountability and transparency that remain unnavigable and inexplicable, such that even the enhanced versions could aggravate the existing misinformation issues. They state that major platforms' growth transforms them so much that they no longer function primarily as social networks. They define “algorithmic moderation” as “systems that classify user generated content based on either matching or prediction, leading to a decision and governance outcome (e.g. removal, geoblocking, account takedown).” Different types of hashing (matching) and classification (prediction) tools and the areas they are deployed (copyright, terrorism, and toxic speech) are described and their practicality are criticized. Their case analyzes including copyright enforcement, counterterrorism, and toxic speech illustrate the limitations and unintended harms of automated moderation, demonstrating how even “improved” systems risk reinforcing misinformation patterns, entrenching platform power, and displacing human judgment. Ultimately, Gorwa et al. argue that algorithmic moderation transforms platform governance itself by concentrating authority in opaque technical systems while rendering the underlying political choices invisible.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Reynolds, C. J., and Blake Hallinan. 2024. “User-Generated Accountability: Public Participation in Algorithmic Governance on YouTube.” ''New Media &amp; Society'' 26 (9): 5107–5129. https://doi.org/10.1177/14614448241251791. '''
&lt;/div&gt;

This study focuses on how YouTube creators respond to platform governance decisions by producing “user-generated accountability” content, videos that publicly document governance failures and pressure YouTube to intervene. Through an analysis of 250 such videos, the authors state that creators overwhelmingly experience YouTube’s policy enforcement, automated moderation systems, and communication practices as opaque, inconsistent, and often discriminatory. Authors declare that human review is essential in automizing platform governance. The study highlights that platform governance decisions affect creators differently depending on channel size, content type, and identity; larger creators can more easily mobilize audiences to “make noise,” while smaller creators rely on collective visibility tactics such as signal boosting across platforms, especially Twitter. The authors argue that these bottom-up accountability practices reflect both the limits of YouTube’s existing governance infrastructure and creators’ efforts to bypass scale dependent unresponsiveness by publicly sharing grievances, comparing experiences, and testing the platform’s algorithms themselves. Theoretically, the study provides the “user-generated accountability” as a framework for engaging with the unavoidable conflicts that will arise around algorithmic systems, and views content creators as “political actors” who advance the perceptions of algorithms. Empirically, it surfaces common concerns such as demonetization of LGBTQ content, and lack of human review.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Savolainen, Lotta. 2022. “The Shadow Banning Controversy: Perceived Governance and Algorithmic Folklore.” ''Media, Culture &amp; Society'' 44 (6): 1091–1109. https://doi.org/10.1177/01634437221077174.'''
&lt;/div&gt;

Savolainen studies shadowbanning as a lens for understanding current algorithmic platform governance from the user perspective. Rather than determining whether shadowbanning objectively exists, the author conceptualizes it as “algorithmic folklore”: informal, collectively produced narratives through which users attempt to make sense of opaque moderation and ranking systems. Drawing on Reddit discussions about TikTok, Instagram, and YouTube, the study shows how users interpret suppressed visibility through anecdotal evidence, experimentation, and shared pattern recognition, revealing the experiential dimensions of algorithmic governance. Either users “probe the rules” or find their ways through “pleasing the algorithms”; the author argues that these practices emerge in response to governance systems that lack the clarity, stability, and consistency that are traditionally associated with good governance. The study concludes that platform governance contains a structural paradox: platforms increasingly present themselves as legitimate governors while simultaneously developing automated moderation systems that undermine transparency and consistent enforcement. Ultimately, the ethical issue is not shadowbanning itself, but the broader reality of shadowy governance exercised by complex, distributed algorithmic systems at scale.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Vetter, Matthew A., Jialei Jiang, and Zachary J. McDowell. 2025. “An Endangered Species: How LLMs Threaten Wikipedia’s Sustainability.” ''AI &amp; Society'', February. https://doi.org/10.1007/s00146-025-02199-9.'''
&lt;/div&gt;

Vetter et al. caution against using Wikipedia as AI training data uncritically by outlining many complicating factors. Wikipedia’s collaborative model of data curation democratizes data creation, but embeds power dynamics and biases. A feminist posthumanist framework is applied, which situates Wikipedia’s knowledge as contextual, based upon the positionality of predominantly Western, male editors, a perspective LLMs would perpetuate without opportunity for change. Wikipedia’s &quot;dynamism&quot; is the main reason it is so valuable, stemming from constant, collaborative updates by volunteers. AI responses’ inconsistent citations and plagiaristic tendencies undermine human editors, the source of Wikipedia’s verifiability, and exploit scholars, Wikipedia itself, and the past labour of volunteers. Wikipedia needs both &quot;a steady stream of new and returning readers&quot; and &quot;a diverse group of dedicated volunteers,&quot; whilst AI responses push sources into obscurity and at best detour the website, threatening Wikipedia’s long-term sustainability. Vetter et al. practically explore Wikipedia’s relationship with LLMs by conducting a &quot;problem-centred expert interview&quot; of community leaders, who possess 25 combined years of involvement and research. Through these interviews, Vetter et al. identify three main areas of opportunity: promoting transparency and explainability, diversifying the Wikipedia community, and equipping users with critical thinking skills. Overall, their findings &quot;resonate with the posthumanist approach to critical AI literacy,&quot; cautioning against hoping for purely technological fixes and calling for greater transparency in how tech giants &quot;leverage open-access datasets.&quot;

== Governance, Leadership, and Policy ==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Balendra, Soorya. 2025. “Meta's AI Moderation and Free Speech: Ongoing Challenges in the Global South.” ''Cambridge Forum on AI: Law and Governance'' 1. https://doi.org/10.1017/cfl.2025.5&lt;nowiki/&gt;.'''
&lt;/div&gt;

This article conducts a case study of Meta’s AI-based content moderation in the Global South, arguing that the censorship of unprohibited content (“over removal”) and slow response to content that causes harm (“slow removal”) are part of “content moderation procedures” that constitute “massive discriminatory approaches.” Balendra presents three models of authority for the regulation of social media content: external regulation, self-regulation, and co-regulation, and argues that state regulation (falling under the external model) varies wildly depending on the government in question, with “granting absolute regulatory power to state actors often stifl[ing] political discourse and online expression.” Co- and self-regulation mitigate this problem, but introduce a new issue by shifting responsibility—private companies use AI to make millions of judgements about content in a short frame of time. The paper notes that the EU and the United States have drastically different policies regarding content moderation on social media platforms and argues that “the practice of content moderation remains largely shaped by the cultural norms of the United States” and the values of “a relatively homogenous groups of Silicon Valley elites.” Balendra finds that, at this time, current approaches often prioritize the state or private corporate interests rather than free speech or the interests of the larger community, and much work is needed to “achiev[e] genuine change” in the form of integrated, hybrid approaches.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Birkstedt, Teemu, Matti Minkkinen, Anushree Tandon, and Matti Mäntymäki. 2023. “AI Governance: Themes, Knowledge Gaps and Future Agendas.” ''Internet Research'' 33 (7): 133–67. https://doi.org/10.1108/INTR-01-2022-0042. '''
&lt;/div&gt;

Birkstedt et al. conduct a systematic literature review (SLR) of the emerging yet fragmented field of “AI governance” (AIG), defined as “a system of rules, practices, processes, and technological tools” that ensure organizational AI meets strategic, legal, and ethical requirements. The authors use human-centric and sociotechnical AI traditions to explore how organization-level governance mechanisms can bridge the principles-to-practices gap in AI ethics. Through SLR, authors identify four research agendas. The “technical agenda” focuses on the practicalities of AIG. The “stakeholder and contextual agenda” ensures AI meets requirements via direct collaboration with external stakeholders, increased corporate social responsibility, and establishment of an “intelligent discourse regime.” The “regulatory agenda” aligns AIG with ethical and legal standards, while the technical, stakeholder and contextual, and regulatory agendas largely focus on the aims of organizational AIG (i.e., what), and the process agenda deals with the means to achieve the aims (i.e., how). The authors develop a generic framework to guide cohesive AIG practices and advocate for a collaborative governance approach that emphasizes transparency, stakeholder engagement, and sociopolitical awareness. 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Broekhuizen, Thijs, Henri Dekker, Pedro De Faria, Sebastian Firk, Dinh Khoi Nguyen, and Wolfgang Sofka. 2023. “AI for Managing Open Innovation: Opportunities, Challenges, and a Research Agenda.” ''Journal of Business Research'' 167 (November 2023): 114196. https://doi.org/10.1016/j.jbusres.2023.114196. '''
&lt;/div&gt;

Broekhuizen et al. systematically analyze how AI could be applied to the complex, unstructured task of “open innovation,” a possible business opportunity they believe has been insufficiently explored. They define “Open innovation” as “the practice of leveraging external ideas, resources, and capabilities to improve innovation outcomes,” and propose AI could minimize its inherent managerial challenges. To prove this, the authors form a framework that considers the three abilities involved in AI’s agreed possible applications to management (involving “mapping,” “coordinating,” and “controlling”) and assess how applicable their constituent functions are to the challenges of the three stages of open innovation (involving “initiation,” “development,” and “realization”). In the stage of “initiation,” they propose AI could scout for distant knowledge partners, detect relevant information gaps and opportunities, and forecast conflicts. During the “development” stage, AI could develop complementarity between partners' knowledge stocks, integrate knowledge whilst safeguarding intellectual property, and monitor partners for violations or conflicts within the relationship. Finally, during the “realization” stage the authors argue AI could comprehensively evaluate business opportunities, optimize resource deployment, and diagnose or remedy intellectual property violations. To Broekhuizen et al., this study “underscores the significance of the human-side of AI” by demonstrating AI’s valuable role in assisting management. They also conclude that AI’s ability to search for corporate partners will be its greatest impact in open innovation, as they argue it will both incentivize openness and reputability of companies and increase the need for them to keep sensitive data secure.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Cheong, Inyoung. 2024. “Collaborative Approaches to AI Governance: Exploring Co-Design and Co-Regulation Models.” PhD diss., University of Washington. https://homes.cs.washington.edu/~yoshi/papers/theses/inyoung-cheong-dissertation.pdf&lt;nowiki/&gt;.'''
&lt;/div&gt;

This dissertation seeks to integrate co-design and co-regulation as a means of facilitating domain-specific expert knowledge into AI governance policies. It uses theoretical analysis and empirical data as part of its methodologies, and it should be of interest to anyone who wants detailed case studies of the use of AI technology in specific domains, as well as clear models for (co-)governance and development in the use of Artificial Intelligence. Cheong performs two case studies, examining the development and use of an AI application to provide legal advice as well as the application of AI in online content moderation of news and comics apps in South Korea. These result in a set of strategies for AI co-regulation that includes parameters for starting conditions, institutional design, collaborative process, and facilitative leadership. Cheong proposes that the guiding principles for AI co-governance must account for specific and distinct contexts, maintain human involvement and intervention in what is often seen as an artificial and automated process, and look to resolve legal ambiguities surrounding AI, especially as there is a clear history of courts dismissing what Cheong calls “collective rule-making” by the community. The author argues for the implementation of co-regulation and co-design, and maintains that “by fostering inclusive dialogues, leveraging diverse expertise, and remaining adaptable to changing technological and societal landscapes” these methods show potential for dealing with AI’s greatest challenges.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Floridi, Luciano. 2018. “Soft Ethics and the Governance of the Digital.” ''Philosophy &amp; Technology'' 31 (1): 1–8. https://doi.org/10.1007/s13347-018-0303-9&lt;nowiki/&gt;.'''
&lt;/div&gt;

Floridi argues our “mature information societies” means “we no longer live online or offline, but onlife,” making the sociopolitical challenge of ethically governing this foundational “digital age” even more vital than pursuit of future digital innovations. Floridi defines three overlapping subfields within the “Governance of the Digital,” including “Digital Ethics,” “Digital Regulation,” and the encompassing “Digital Governance.” The latter is defined as “the practice of establishing and implementing policies, procedures, and standards for the proper development, use and management of the infosphere,” therefore “sometimes neither moral nor immoral… legal nor illegal.” This demonstrates that the three subfields don’t always overlap, but each must always be considered by policymakers, because what is legal, what is good, and what is best are all key components of the ideal “Governance of the Digital.” “Digital Ethics” should also be further subdivided into “hard” ethics, involving binary moral judgments about what should versus should not be done, and “soft” ethics, which involves a “post-compliance,” “post-feasibility” approach, ensures moral opportunities are maximized, and fosters “good corporate citizenship.” Differing “information societies” occupy differing levels of maturity, producing distinct ethical contexts which should progress with differing ethical focuses. In this regard, Floridi advocates “ethics foresight analysis,” which uses data analytics to assess ethical impacts of future innovations then targets research by systematically identifying what is feasible, then sustainable, then acceptable, then preferable. The author concludes that Digital Ethics must be “leading” not “chasing” developments, and not just functioning as a questioning exercise, but also signalling that ethical issues matter, engaging with stakeholders, and providing shareable solutions.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Gasser, Urs, and Virgilio A. F. Almeida. 2017. “A Layered Model for AI Governance.” ''IEEE Internet Computing'' 21 (6): 58–62. https://doi.org/10.1109/MIC.2017.4180835&lt;nowiki/&gt;.'''
&lt;/div&gt;

This article identifies the gap in knowledge created by the “black box” of AI—the obscured nature of the processes that take place from an initial prompt to its generated output. Gasser et al. note that users and policymakers of these technologies have relatively little insight into how it actually works compared to its developers. Given this unique issue, Gasser et al. propose a theoretical framework for how to approach AI governance, drawing upon the advent and subsequent globalization of the Internet to inform their understanding of AI technology and its pattern of growth. The article addresses a core issue that strong or general AI is often discussed in terms of potential societal impact while weak or general AI is currently being deployed right now (i.e., 2017) and is in real need of governance already. The authors identify core themes related to “transparency, accountability, and explainability; inclusion and fairness; [and] global governance,” as well as three challenges for AI governance—&quot;information asymmetries”; “finding normative consensus”; and “government mismatches”. The authors point out that the ethical and legal considerations of AI are closely related and take a modularity approach; they present three layers for governance that exist from AI systems to society, with timing (i.e., near-, mid-, and long-term) and considerations for each layer. The article concludes by proposing AI governance requires a blended approach based on the different risks of certain AI applications and propose that both “market-oriented solutions” and &quot;government-based structures” can work on a national or international level, suggesting a “global oversight body” could act as “the curator of global principles and emerging norms for AI systems.”

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Kirschenbaum, Matthew. 2025. “The US of AI.” Public Draft, February 25, 2025. https://drive.google.com/file/d/1O2qkjhg7Ei5zZWmBraNwXq4V0lTauspN/view&lt;nowiki/&gt;.'''
&lt;/div&gt;

This set of notes from Kirschenbaum represents his “near real-time attempt to come to terms with… the opening weeks of the second Trump Administration,” especially the “AI-first” strategy of “the so-called Department of Government Efficiency (DOGE).” Kirschenbaum outlines DOGE has nothing to do with government efficiency, as it only saves insignificant costs, instead possessing ideological and capitalistic motivations to form “a government without people.” Based on Musk’s nebulous authority—as an advisor from the private sector—DOGE targeted nineteen federal agencies to be “strip-mined and fracked for all manner of information” as a “priceless and unprecedented resource” of AI training data. To do so, DOGE operatives accessed sensitive spaces after hours, combining physical aggression with a “complete lack” of technical inhibition representing a “vampiric data suck.” Kirschenbaum identifies clear corporate interests here and further examines ideological aims. Early executive orders asserted the need for federal AI systems “free from ideological bias or engineered social agendas,” with OpenAI announcing “ChatGPT Gov” days later. These invocations of “AI” as a universal solution represent only a “linguistic token” instead of any realized technology—as worded by Salvaggio, AI must only “be considered a plausible competitor to human decision-making long enough to dislodge the existing human decision-makers.” Kirschenbaum frames this as based in the “masculine maximalism” of the Trump administration, as the term AI promotes “technological absolutism” whilst theoretically playing into the Nixon-era “theory of the unitary executive” by aiming to replace people with “void” and consolidate power into the hands of “a super-user class who will operate outside the system.” However, “the real world intrudes… with lethal downstream effects.” Kirschenbaum proposes “a collapsing superimposition of political discourse, the actual operations of social media as its primary public arena, and the technical architecture of the systems (in the form of AI)… in the sphere of governance as well as media,” which produces the “infrastructure for… permanent despotism” via the “untethering of language from conditions of lived reality.”

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Oh, Dayei, and John Downey. 2024. “Does Algorithmic Content Moderation Promote Democratic Discourse? Radical Democratic Critique of Toxic Language AI.” ''Information, Communication &amp; Society'' 28 (7): 1157–76. https://doi.org/10.1080/1369118X.2024.2346531.'''
&lt;/div&gt;

Oh and Downey critically examine how algorithmic content moderation shapes public discourse, focusing specifically on Google’s Perspective API and its detection of &quot;toxic&quot; language. By drawing a crucial distinction between incivility (harsh or emotional tone) and intolerance (actual discriminatory harm), the authors demonstrate how AI-driven moderation systems frequently misinterpret context. Consequently, these algorithms often suppress emotionally charged but politically significant speech—particularly from marginalized groups—while allowing structurally discriminatory but politely phrased content to evade detection. This dynamic reveals a significant flaw in relying on AI as a neutral mediator of digital dialogue: by prioritizing tone over substance, algorithmic moderation actively curtails democratic participation and skews the visibility of diverse perspectives. Their study is relevant for understanding how AI systems act as invisible gatekeepers, enforcing normative boundaries on public expression and highlighting the urgent need for moderation frameworks that are contextually aware, transparent, and equitable rather than merely tone-policing.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Rughiniș, Cosima, et al. 2025. “AI at the Knowledge Gates: Institutional Policies and Hybrid Configurations in Universities and Publishers.” ''Frontiers in Computer Science'' 7: 1608276. https://doi.org/10.3389/fcomp.2025.1608276. '''
&lt;/div&gt;

This article constitutes a qualitative analysis (i.e., a form of computational analysis) of 16 universities and 12 publishers that attempts to understand how these institutions regulate AI in knowledge production. Rughinis et al. claim that most institutions preserve their values while regulating AI by adapting the regulations they already have in place, stating “institutional policies are shaped by value-based compromises and not by technical concerns alone.” At the same time, although the article acknowledges its focus on institutional regulation, it also admits that “AI adoption can evolve both through policy frameworks and… locally embedded practices that remain partly invisible in formal documentation.” The authors propose two concepts, “dual black-boxing” and “legitimacy-dependent hybrid actors.” Dual black-boxing refers to the lack of transparency in both the “hidden algorithmic processes [and] invisible training data” that shape AI systems and “the opacity surrounding how academics employ AI in their work,” while legitimacy-dependent hybrid actors are “configurations of human-AI collaboration whose institutional legitimacy is not intrinsic but conditional.” Rughinis et al. argue that transparency is a core academic value, and scholars must work to open these black boxes; they also suggest that that transparency is more closely linked to academic legitimacy in AI-related issues rather than the more traditional issue of the origin of ideas. The majority of the article applies these terms to understanding the regulatory frameworks of universities and publishers, and concludes with the understanding that the majority of institutions allow some form of AI use within certain parameters. The key types of hybrid actors allowed by universities were AI-assisted researchers, AI-enabled translators, AI-enhanced writers, and AI-supported coders, while publishers facilitated the use of AI to refine language, support research methodologies, and aid in research. Ultimately, the authors observe that institutions are permitting AI-supported work in refined roles and argue that AI-based academic work gains legitimacy through transparency.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Seger, et al. “Democratising AI: Multiple Meanings, Goals, and Methods.” ''Proceedings of the 2023 AAAI/ACM Conference on AI, Ethics, and Society''. https://dl.acm.org/doi/10.1145/3600211.3604693&lt;nowiki/&gt;.'''
&lt;/div&gt;

Aiming to “provide a foundation for more productive conversations,” Seger et al. categorize four forms of “AI democratisation” and explore each form’s goals and facilitation pathways. Democratization of AI “use” involves making it easier for people to employ AI’s capabilities, and is therefore equally comparable to increasing availability of printers or of tools which can create chemical weaponry, depending on the case. Democratization of “development” involves allowing a wider range of people to contribute to the AI design and development process, which accelerates progress and increases diversity, but also opens the door for maliciousness and irresponsibility. Democratizing “profits” constitutes a philanthropic or redistributive process, and has the predictably involved weaknesses. Therefore, the authors highlight that “AI democratisation is a multifarious and sometimes conflicting concept” which “should not be conflated with improving AI accessibility” and “is not inherently good.” This is because democratization of AI’s “use,” “development,” and “profits” only derives value from its alignment with the interests and values of impacted groups, making democratization of AI’s “governance” the priority. Democratization of “governance” does not necessarily aim for total agreement amongst constituents, but will regardless reduce the unilaterality of decision-making by promoting justice, legitimacy, and diversity.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Sposato, Martin. 2025. ”Artificial Intelligence in Educational Leadership: A Comprehensive Taxonomy and Future Directions.” ''International Journal of Educational Technology in Higher Education'' 22 (20). https://doi.org/10.1186/s41239-025-00517-1. '''
&lt;/div&gt;

This article performs an analysis and review of published works on AI in educational leadership from 2017–2024 and uses the results of that process to develop what Sposato describes as “a comprehensive taxonomy of AI applications in educational leadership.” Potential readers include researchers and policymakers interested in communicating across specific fields and disciplines. Sposato theorizes ten application domains for AI in higher education ranging from increased efficiency in administration and teaching practices to increased community engagement and strategic planning. The purpose of such a framework is to provide educational leaders with a coherent vocabulary of “the full spectrum of educational leadership responsibilities” that can facilitate further conversation. The author advocates for AI’s transformative potential in higher education even as they note important challenges (especially with ethics and equity), arguing a need for a balanced approach and “robust ethical guidelines and regulatory frameworks.” The framework provided is presented as one step toward developing AI literacy for stakeholders so that all involved in education might make more informed decisions and articulate their needs more clearly.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Ter-Minassian, Lucile. 2025. ”Democratizing AI Governance: Balancing Expertise and Public Participation.” Preprint, ''arXiv'', January 16. https://doi.org/10.48550/arXiv.2502.08651&lt;nowiki/&gt;.'''
&lt;/div&gt;

Ter-Minassian argues that “universal access, technically-constrained development, and universal impact” of AI and AI research necessitate public participation in AI governance even as it “creates a unique governance challenge.” The article presents the benefits and challenges of expert oversight and public consultation. Ter-Minassian outlines the threat of misinformation to meaningful public participation, highlighting how both undue fear and unrealistic optimism surrounding AI can affect public discourse, while acknowledging that the rapid rate of AI research makes it difficult to incorporate truly democratic processes into the decision-making process. The author concludes that any ongoing inclusive and effective AI governance ought to incorporate inclusive representation, balance expertise and public engagement, embrace transparency and accountability while engaging an iterative process, and implement a hybrid framework that “blend[s] expert knowledge with meaningful public input” (4). She argues that “AI’s deep societal impact calls for public engagement” and “technical complexity does not have to exclude meaningful public input,” advocating for “structured deliberation and phased public participation” to address “time-sensitive AI challenges without compromising democratic legitimacy” (5). Ultimately, the article sees this as an iterative process that will need to continue to adapt in order to maintain expert insight and public discourse on AI.

== Critical Literacies ==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Aguiar, Micaela, and Sílvia Araújo. 2024. “Final Thoughts: Digital Humanities Looking at Generative AI.” ''In Digital Humanities Looking at the World'', edited by S. Araújo et al., 367–380. Cham: Springer Nature Switzerland.'''
&lt;/div&gt;

Aguiar and Araújo explore the emergence and applications of generative artificial intelligence within Digital Humanities research. They trace the evolution of generative AI from early implementations like the 1960s Eliza chatbot through its developments such as Generative Adversarial Networks (GANs) and the Transformer architecture to contemporary large language models like BERT and GPT. The authors document current applications of generative AI across Digital Humanities domains, including cultural heritage preservation, historical text processing, and literary creation. They outline how these technologies are being used to memorialize mass atrocities, process traditional Chinese ancient texts, and explore collaborative human-AI poetry creation. Aguiar and Araújo examine the inner workings of generative AI, particularly focusing on how conversational models function through statistical prediction rather than genuine comprehension. They identify limitations such as hallucinations, bias replication, and attribution problems that researchers must consider when using these tools. The chapter concludes that effective integration of generative AI in Digital Humanities requires developing AI literacy skills that enable researchers to critically evaluate outputs while leveraging the technology's capabilities for sustainable research advancement.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Boer, Victor de, and Lise Stork. 2024. “Hybrid Intelligence for Digital Humanities.” Preprint, ''arXiv'', April 15. https://doi.org/10.48550/ARXIV.2406.15374. '''
&lt;/div&gt;

De Boer and Stork believe the discipline of Digital Humanities (DH) should meet the challenges and opportunities posed by Artificial Intelligence (AI) by adopting the “human-centric paradigm” of Hybrid Intelligence (HI). They define DH as “a scholarly realm where computing or digital technologies intersect with… the humanities… characterized by innovative approaches to scholarly endeavors,” and identify various existing DH approaches to AI, which include “Knowledge Representation,” “Machine Learning,” “Natural Language Processing,” and “Computer Vision.” De Boer and Stork argue successfully integrating AI tools into DH requires embedding AI in scholarly practice, adopting a diverse and polyvocal approach, considering the debate of distant versus close reading, and applying a critical stance toward data, methods, and tools. HI “concerns itself with the investigation and design of human-AI ecosystems,” and the authors argue effective AI should be developed by following its “CARE” principles—being “Collaborative, Adaptive, Responsible, and Explainable.” Therefore, De Boer and Stork focus this text on mapping CARE principles to those DH requirements earlier outlined. Overall, they concur with Goodlad and Baker that humanists “are ideal 'domain experts' for the current juncture,” and end by identifying two overarching challenges. The first challenge is “one-shot solutions,” including tools, datasets, and methods that aren’t reusable, Open Source, accessible, and well described. Secondly, they identify the human factor—actors will need both an open mind and AI literacy to be equally critical of and cooperative with AI. Therefore, the authors emphasize the importance of teaching digital methods within the humanities curricula.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Carmi, Elinor, Simeon J. Yates, Eleanor Lockley, and Alicja Pawluczuk. 2020. “Data Citizenship: Rethinking Data Literacy in the Age of Disinformation, Misinformation, and Malinformation.” ''Internet Policy Review'' 9 (2). https://doi.org/10.14763/2020.2.1481.'''
&lt;/div&gt;

This study argues that dominant understandings of digital and data literacy are insufficient for addressing contemporary complex challenges of disinformation, misinformation, and malinformation. They propose the concept of data citizenship to reframe literacy as a fundamentally civic, political, and collective practice rather than a set of individual technical skills. The authors contend that information disorders cannot be addressed through technological solutions alone, as they are deeply embedded in structural inequalities, platform economies, and power asymmetries shaping datafied societies. The article builds on a literature review and secondary data analysis drawing on Me and My Big Data project, alongside the development of a nationally representative UK survey. The authors identify three major gaps in existing literacy frameworks: an overemphasis on individual competence rather than networked practices, a lack of critical engagement with algorithmic and economic infrastructures of platforms, and the absence of proactive civic skills such as contesting data extraction, demanding transparency, and advocating for data justice. Their analysis highlights how citizens’ data practices are shaped by social networks, education, and socio-economic conditions, revealing unequal capacities for verification, protection, and collective action. The authors conclude that data literacy must move beyond content verification to include critical understanding of platform design, funding models, and algorithmic governance. They emphasize the importance of locally grounded, participatory approaches to data literacy education that reflect diverse lived contexts rather than scalable, top-down interventions. While the study offers a robust conceptual model and survey-based insights, it does not yet include in-depth qualitative engagement with citizen groups, which the authors position as a necessary next phase of research. Overall, the article makes a significant contribution by bridging digital literacy and the field of mis/dis/mal information research and claims that data literacy is an essential component of democratic citizenship.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Long, Duri, and Brian Magerko. 2020. “What is AI Literacy? Competencies and Design Considerations.” In ''Proceedings of the 2020 CHI Conference on Human Factors in Computing Systems'', 1–13. New York, NY: Association for Computing Machinery. https://doi.org/10.1145/3313831.3376727.'''
&lt;/div&gt;

The authors present an exploratory review of interdisciplinary literature, aiming to organize key ideas on AI literacy definitions and essential competencies. Authors claim that public misunderstandings of AI are due to design, educational gaps, black-box algorithms, and a general lack of technological knowledge. The review includes two sections: how the public understands specific AI systems, and how existing research addresses people’s broader understanding of AI. Rather than offering an exhaustive synthesis, Long and Magerko’s focus is on non-technical audiences and they offer central provocations and design principles that can inform educational interventions. The proposed conceptual framework on AI literacy identifies 17 core competencies alongside 14 design considerations for educational intervention, which are described and supported by relevant literature. Together, these considerations position the framework as a practical and reflective tool for designing AI literacy interventions that move beyond dominant media narratives and foster critical, informed engagement with AI technologies.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Majdik, Zoltan P., and S. Scott Graham. 2024. “Rhetoric of/with AI: An Introduction.” ''Rhetoric Society Quarterly'' 54 (3): 222–31. https://doi.org/10.1080/02773945.2024.2343264. '''
&lt;/div&gt;

Majdik and Graham propose a field-organizing distinction that functions as a methodological argument. By splitting inquiry into “rhetoric of AI” (AI as object) and “rhetoric with AI” (AI as method), they treat AI simultaneously as a rhetorical actor/ecosystem component that structures attention, circulation, and uptake, and as an instrument that can be enrolled into rhetorical research workflows. The authors claim that much prior rhetorical work engaged “spaces of AI”—platforms, devices, and algorithmically mediated environments—while leaving “AI” itself undertheorized as the central object; this provides a justification for why rhetoricians should now foreground model/algorithmic operations (and their harms) rather than treating them as neutral background conditions of digital rhetoric. They also frame generative text systems as a stress test for core rhetorical concepts—agency, authorship, and audience—because these systems destabilize the presumed linkage between human intention and textual production, and because they insert nonhuman intermediaries into communicative situations that education and public discourse still normatively treat as human-to-human. The introduction then uses this distinction to stage the special issue’s contributions as complementary routes for rebuilding rhetorical theory and pedagogy under AI conditions.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Ng, Davy Tsz Kit, Jac Ka Lok Leung, Samuel Kai Wah Chu, and Maggie Shen Qiao. 2021. “Conceptualizing AI Literacy: An Exploratory Review.” ''Computers and Education: Artificial Intelligence'' 2: 100041. https://doi.org/10.1016/j.caeai.2021.100041. '''
&lt;/div&gt;

This article presents an exploratory review of literature published between 2016 and 2021 with the goal of conceptualizing AI literacy and proposing a comprehensive framework for teaching and evaluating it. The authors analyze 30 articles and synthesize existing definitions and approaches to AI literacy, noting that while AI literacy has increasingly been discussed, the concept has often been treated narrowly as a technical skill set. The authors situate AI literacy as a necessary competency for everyone, arguing that AI will increasingly affect many aspects of daily life and employment. In response, the authors argue for a broader understanding of AI literacy that incorporates cognitive and ethical dimensions. The proposed framework organizes AI literacy into four interconnected facets: knowing and understanding AI, using and applying AI, evaluating and creating AI, and AI ethics. Importantly, the authors explicitly reject purely instrumentalist views of AI literacy. To conceptualize AI literacy pedagogically, the authors draw on Bloom’s classic taxonomy, aligning the above-mentioned aspect with increasing cognitive levels. They claim that while most people are aware that AI exists, they often lack understanding of how it works or how to assess its ethical and social implications. This approach positions AI literacy as a developmental learning process rather than a static set of skills. The article concludes by identifying directions for future research, including the need for empirical studies to validate AI literacy frameworks and to better understand how AI literacy can be taught, learned, and assessed across educational contexts.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Rapanta, Chrysi, Anna Åkerfeldt, Mark Vanderbeeken, Diane Lison, Khadija Mohammed, Amanda Gibbs, Helder Coelho, Pinar Seda Celik, Carola Bruna, Ingrid Helleve, Chrysoula Vassilakopoulou, Pieter Swart, Ana Lúcia Marques, and Dirk Ifenthaler. 2025. “Critical GenAI Literacy: Postdigital Configurations.” ''Postdigital Science and Education'' 17 (1): 167–199. https://doi.org/10.1007/s42438-025-00573-w.'''
&lt;/div&gt;

Rapanta et al. develop a comprehensive and pluralistic account of what critical literacy means in the context of generative artificial intelligence. Drawing on contributions from fourteen scholars, the article argues that GenAI literacy cannot be captured through a single, universal framework. Instead, it must be understood as a set of context-dependent literacies shaped by disciplinary traditions, socio-political conditions, and evolving human–algorithm relations. This postdigital perspective challenges narrow definitions of AI literacy that prioritize technical skills. The authors’ central claim is that current GenAI systems, particularly large language models, require critical engagement because of their epistemic limitations, including reliance on dominant narratives, lack of explainability, tendencies toward fabrication, and reinforcement of Western and anglophone knowledge structures. As a result, critical GenAI literacy is positioned as a social justice concern rather than a neutral competency. Learners and educators are encouraged to examine questions of authorship, agency, and power, such as whose labour and data underpin these systems and which perspectives are marginalized or erased. Methodologically, the article adopts a dialogic and collective approach to resist homogenizing AI epistemologies and to foreground plurality in postdigital research. The authors conceptualize GenAI as part of a co-constructive assemblage in which human and non-human agencies interact, while maintaining that ethical responsibility and evaluative judgment must remain human-led, organizing four interrelated dimensions: epistemology and ontology, agency, engagement, and ethics and justice; each emphasizing critical interrogation, active participation, and accountability. Overall, the paper provides a theoretically grounded yet pragmatic foundation for advancing critical GenAI literacy in education and research.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Veldhuis, Annemiek M., Phoebe W. K. Lo, Iain E. G. Kenny, and Alissa N. Antle. 2024. “Critical Artificial Intelligence literacy: A scoping review and framework synthesis.” ''International Journal of Child-Computer Interaction'' 43: 100708. https://doi.org/10.1016/j.ijcci.2024.100708&lt;nowiki/&gt;.'''
&lt;/div&gt;

Veldhuis and colleagues present a review of literature and framework synthesis that conceptualizes critical AI literacy from a child–computer interaction (CCI) perspective. Reviewing 30 empirical studies published over the past decade, the authors aim to understand how children and youth aged 5–18 have been supported in developing critical literacy on AI technologies, particularly regarding their social, political, cultural, and ethical implications. Grounded in critical literacy theory, the authors integrate Lewison et al.’s (2002) four interrelated dimensions including disrupting the commonplace, considering multiple viewpoints, focusing on the sociopolitical, and taking action into a four-part framework for critical AI literacy. Importantly, the framework rejects deficit narratives by foregrounding children’s capacity for critical inquiry and demonstrates that even young learners can meaningfully engage with complex issues such as algorithmic bias, data provenance, privacy, accountability, and the distinction between AI-generated outputs and human creativity when supported by pedagogies such as critical making. Only peer-reviewed, English-language empirical studies with explicit support for children’s critical engagement with AI were included. The findings reveal a growing body of research, particularly in the past three years, exploring activities that promote youths’ critical reflection on AI’s societal and ethical impacts. These activities address concerns related to privacy, surveillance, employment, diversity in the computing workforce, algorithmic bias, and accountability. The resulting framework emphasizes learners’ capacity to analyze both AI artifacts and the sociotechnical systems that produce them, as well as to reflect on how AI shapes cultural, societal, and political structures and personal experiences. For future research recommendations, the authors emphasize the urgency of ongoing critical AI literacy practices in areas of youth emotional awareness and socio-cultural impacts in response to the fast evolution of generative AI systems. 

== Globalism, Colonialism, and Influence ==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Arora, Payal. 2024. “Creative data justice: a decolonial and indigenous framework to assess creativity and artificial intelligence.” ''Information, Communication &amp; Society'' 28 (13): 2231–47. https://doi.org/10.1080/1369118x.2024.2420041&lt;nowiki/&gt;.'''
&lt;/div&gt;

Arora (2024) develops a framework of creative data justice that includes decolonial theory, Indigenous perspectives, and critical studies of creativity to explore how generative AI could impact creative labour, rights, and cultural value. The author argues that democratizing creativity requires a cross-cultural framework that considers power relations between creative work, data, and learning, particularly by centring the lived realities of underrepresented communities in the Global South. Rather than treating AI creativity as neutral, the paper claims that inclusive AI systems must address contextual inequalities and the unequal impacts of AI on diverse creative communities. Arora critiques dominant Western-centred scholarship and challenges concepts such as the “creative class,” arguing that creativity exists across everyday social and cultural practices. The paper also critiques Creative Commons (CC) frameworks, suggesting that while they promote openness, they may enable commercial data extraction by AI companies. Instead, the author argues for dataset curation developed with Indigenous artists and activist groups to ensure equitable representation. The article further highlights the often-invisible labour behind creative AI located in the Global South and argues that a decolonial approach must recognize both material infrastructures and power relations shaping creative work. Indigenous approaches to communal ownership and systems of care are presented as alternatives to Western individualistic models of creative rights. The author advocates combining ethnographic “thick data” with computational approaches and suggests action-research methods such as counter-mapping, dataset debiasing, and critical media literacies. The paper concludes that creative data justice offers a framework for building culturally diverse and equitable AI systems that respect community agency and support a more democratic global data economy.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Fırıncı, Yusuf. 2024. “Decolonial Artificial Intelligence; Algorithmic Fairness in Alignment with Turkish and Islamic Values.” ''Marmara Üniversitesi İlahiyat Fakültesi Dergisi'' 67 (67): 250–279. https://doi.org/10.15370/maruifd.1565884&lt;nowiki/&gt;.'''
&lt;/div&gt;

Fırıncı argues that artificial intelligence development should be guided by explicitly value-based frameworks grounded in Turkish-Islamic ethical traditions rather than relying solely on dominant Western models of technological governance. The authors emphasize that AI systems rely on human judgment and are inherently value-laden, making ethical alignment essential to prevent manipulation, misinformation, algorithmic bias, and forms of digital coloniality. Drawing on concepts such as big data, “thick data,” and digital anthropology, the paper suggests combining quantitative data analysis with culturally grounded social knowledge to design algorithms that reflect community values. The paper examines tensions between Western liberal individualism (which underpins most AI fairness metrics) and Islamic ethical frameworks that emphasize communal welfare, divine justice, and context-dependent moral reasoning. This analysis reveals that &quot;fairness&quot; is not a universal technical specification, but a deeply value-laden concept shaped by particular cultural, religious, and philosophical commitments—meaning that AI systems designed around Western fairness assumptions may be experienced as unjust in contexts operating from different ethical frameworks. Using Social Construction of Technology theory and critical social constructivism, the authors argue that existing global AI frameworks often reproduce hierarchy, bias, and external control, which they interpret as forms of algorithmic oppression. In response, they advocate a “fairness in alignment with values” approach grounded in Turkish-Islamic worldviews, supported by Islamic ethical principles as foundations for responsible technological development. The paper concludes by calling for locally controlled data infrastructures, culturally aligned AI systems, and knowledge production rooted in Turkish and Islamic values as part of a broader decolonial technological model aimed at protecting communities from AI-related harms and preserving social cohesion.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Mohamed, Shakir, Marie-Therese Png, and William Isaac. 2020. “Decolonial AI: Decolonial Theory as Sociotechnical Foresight in Artificial Intelligence.” ''Philosophy &amp; Technology'' 33 (4): 659–84. https://doi.org/10.1007/s13347-020-00405-8. '''
&lt;/div&gt;

Mohamed et al. explore the role of post-colonial and decolonial critical science in understanding the transformative technological advance of AI. They argue risks to vulnerable peoples can be minimized by linking ethical principles to scientific progress, and therefore consider AI’s embedded values, approaching it a&quot;s both object and subject.&quot; They demonstrate that AI advances &quot;encompass ever-larger aspects of the cultural, economic and political life of modern society&quot; by citing Obermeyer et al.’s reveal of racial biases within an algorithm commonly used by healthcare, arguing this indicates how AI obscures and exacerbates asymmetrical power relations. Mohamed et al. identify neglect to address systemic racism as the cause, illustrating that patterns of power between colonizer and colonized survived territorial decolonization to propagate a historically continuous &quot;coloniality of power.&quot; Therefore, &quot;dynamic and robust foresight tactics and methodologies grounded in the critical sciences&quot; (like, for example, a &quot;lens of metropole and periphery&quot;) should be applied to the field of AI to ensure one’s view is &quot;decentring,&quot; &quot;additive-inclusive,&quot; and prioritizes &quot;engagement.&quot; The authors further explore emergent theories of data colonialism within their assessment of &quot;algorithmic coloniality.&quot; This involves their taxonomy of &quot;decolonial foresight&quot; (constituting algorithmic &quot;oppression,&quot; &quot;exploitation,&quot; and &quot;dispossession&quot;), and an exploration of various &quot;sites of coloniality&quot; (including &quot;algorithmic decision systems,&quot; &quot;ghost workers,&quot; &quot;beta-testing,&quot; &quot;national policies,&quot; and &quot;international social development&quot;). They argue this study highlights the disjunction of empirical observations with the current, theoretical, and ahistorical frameworks of power in AI. This leads the authors to outline a set of tactics to develop &quot;decolonial AI&quot; possessing a strengthened empirical basis and an avoidance of algorithmic colonialism. Such tactics are &quot;based on lessons of resistance and recovery from historical and decolonial criticism and grounded within already existing work&quot;; they include critical technical practice, seeking reverse tutelage and pedagogies, and renewing affective political communities. Mohamed et al. emphasize that those ethical principles which form the &quot;social contract&quot; must consider diverse viewpoints, and that new methodologies must be developed to promote &quot;inclusive dialogue&quot; within new research cultures.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Muldoon, James, and Boxi A. Wu. 2023. “Artificial Intelligence in the Colonial Matrix of Power.” ''Philosophy &amp; Technology'' 36 (4). https://doi.org/10.1007/s13347-023-00687-8&lt;nowiki/&gt;.'''
&lt;/div&gt;

Muldoon and Wu (2023) extend decolonial AI scholarship by situating contemporary artificial intelligence within what Aníbal Quijano terms the “colonial matrix of power,” and arguing that from data to production machine learning systems are structured to endure colonial logics that organize economic extraction, labour hierarchies, and epistemic dominance. Central to their framework is the “colonial matrix of power,” which names an organizing principle of domination across interrelated domains: economic control (labour and resources), authority, gender and sexuality, and the control of subjectivity and knowledge. Authors focus particularly on economic extraction and epistemic domination, drawing on the modernity/coloniality research program. They proceed with three interconnected claims: “colonial supply chain of AI,”  “international division of digital labour,” and “hegemonic knowledge production,” demonstrating how AI development relies on largely invisible labour and mineral resources of majority-world communities to generate wealth for Western economies. Beyond material extraction, the authors contend that AI reproduces hegemonic Western epistemologies by presenting its systems as universal, objective, and rational, thereby marginalizing non-Western knowledge systems. This study challenges dominant narratives that present AI as environmentally sustainable or socially progressive, arguing that from mineral extraction to energy-intensive computation, the ecological and material burdens fall disproportionately on majority-world nations, while the economic and technological benefits accrue to wealthy Western nations. They conclude by emphasizing that coloniality is not merely an object of study but a framework for unsettling Western-centric modes of knowing.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Salami, Aishat Oyenike. 2024. “Artificial intelligence, digital colonialism, and the implications for Africa's future development.” ''Data &amp; Policy'' 6. https://doi.org/10.1017/dap.2024.75. '''
&lt;/div&gt;

Salami (2024) studies how artificial intelligence operates within broader dynamics of digital colonialism in Africa, arguing that AI risks reinforcing patterns of colonialism, unless African actors gain greater agency in digital governance. The article begins by clarifying key concepts like AI, digital colonialism, neocolonialism, and data exploitation. Salami identifies several manifestations of digital colonialism on the continent: foreign ownership of critical digital infrastructure, unequal data flows in which African user data is extracted and monetized abroad, and algorithmic systems that enable forms of economic exploitation. Through examples such as ride-hailing platforms and outsourced digital labour, the article demonstrates how algorithmic control can generate precarious working conditions while concentrating profit outside the continent. Beyond labour concerns, Salami highlights how data extraction contributes to a digital wealth transfer, deepening economic imbalances and undermining local innovation and national sovereignty. While acknowledging the potential benefits of AI for development, the article adopts a cautious stance, emphasizing that Africa’s digital future depends on strengthening regulatory frameworks, expanding infrastructure, investing in education and research, and prioritizing data sovereignty. 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Varshney, Kush R. 2024. “Decolonial AI Alignment: Openness, Visesa-Dharma, and Including Excluded Knowledges.” ''Proceedings of the AAAI/ACM Conference on AI, Ethics, and Society'' 7: 1467-1481. https://doi.org/10.1609/aies.v7i1.3173&lt;nowiki/&gt;.'''
&lt;/div&gt;

Varshney discusses AI alignment through a decolonial lens, arguing that current large language model (LLM) alignment practices reproduce forms of coloniality by embedding Western moral philosophy as universal. The author conceptualizes alignment as the post-training processes used to shape model behaviour and argues that the term often functions as an “empty signifier,” masking whose values are being encoded and enforced. The author contrasts open and closed LLM models, arguing that while openness may allow value to circulate more equitably among developers and communities, closed models concentrate value in extractive ways that reflect colonial dynamics, and views them as contemporary “metropoles” that accumulate power through extractive and epistemic control. Building on existing research on colonial AI, the article adds “ethical essentialism” (or moral absolutism) as a new form of coloniality, arguing that AI systems often treat Western moral frameworks as universal, which marginalizes other ethical traditions and reinforces a coloniality of knowledge. Varshney also identifies three specific aspects of coloniality in AI alignment: closed proprietary delivery of models, reliance on Western ethical theories as default, and technological designs that limit how values can be expressed. As an alternative, Varshney proposes a decolonial approach grounded in openness understood not only technically but epistemically: openness to research artifacts, openness to society, and openness to excluded knowledges. The author suggests that alignment should allow communities to adapt models according to local contexts rather than imposing universal rules. Drawing from Hindu moral philosophy, particularly the concept of viśeṣa-dharma (context-dependent ethics), the paper argues for pluralistic, relational value systems that recognize moral diversity instead of universal moral commands. The conclusion calls for a reconceptualization of AI alignment that moves away from moral absolutism toward context-sensitive, community-driven frameworks, positioning openness as a pathway to dismantling the colonial power structures embedded in contemporary AI systems.

== Diversity, Determinism, Bias, and Justice ==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Al-kfairy, Mousa , Dheya Mustafa, Nir Kshetri, Mazen Insiew, and Omar Alfandi. 2024. “Ethical Challenges and Solutions of Generative AI: An Interdisciplinary Perspective.” ''Informatics'' 11 (3): 58. https://doi.org/10.3390/informatics11030058'''
&lt;/div&gt;

Al-kfairy et al. (2024) provide a comprehensive synthesis of the ethical vulnerabilities introduced by generative AI, utilizing an interdisciplinary review of 37 studies across healthcare, education, and media. Rather than treating ethical breaches as isolated technical flaws, the authors demonstrate how generative models systematically threaten privacy, intellectual property, and social equity across diverse domains. For instance, they highlight the paradox in healthcare where synthetic patient data—often intended to protect privacy—still carries significant risks of re-identification. Similarly, the authors trace how AI's capacity to mimic copyrighted works and generate synthetic media exacerbates both misinformation and algorithmic bias, particularly by perpetuating racial and gender stereotypes in high-stakes environments like hiring and education. Moving beyond mere critique, the article advocates for a proactive, cross-sectoral governance framework. The authors argue that mitigating these risks requires more than algorithmic adjustments; it demands multidisciplinary collaboration, robust institutional integrity policies, and targeted AI literacy programs. Ultimately, Al-kfairy et al. frame the ethical deployment of generative AI as a complex sociotechnical challenge that requires continuous, structured dialogue among technologists, ethicists, and policymakers to ensure transparency and fairness.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Alvarez, Jose M, Alejandra Bringas Colmenarejo, Alaa Elobaid, Simone Fabbrizzi, Miriam Fahimi, Antonio Ferrara, Siamak Ghodsi, et al. 2024. “Policy Advice and Best Practices on Bias and Fairness in AI.” ''Ethics and Information Technology'' 26 (2). https://doi.org/10.1007/s10676-024-09746-w. '''
&lt;/div&gt;

This article attempts to provide “an up-to-date entry-point to the state-of-the-art of the multidisciplinary research on bias and fairness in AI” before providing its own suggestions for policy and best practices based on the outcomes of the NoBIAS—Artificial Intelligence without Bias—project. The authors describe fairness in AI as the pursuit to design “methods for detecting, mitigating, and controlling biases in AI-supported decision making,” and they outline different ways that bias can find its way into AI applications as part of training data (pre-existing bias), design (technical bias), and organizational processes (emerging bias). The article critiques the reduction of bias evaluation to simple metrics and advocates for serious engagement with the issue. The authors detail the various components of the collaborative NoBIAS project as part of its research goal to understand, mitigate, and account for bias in AI data and systems, especially within an EU legal context. They perform a survey and discuss various fairness metrics and how choosing the proper method is crucial for “optimizing AI models.” They also engage with an argument that, although AI is biased, it is less biased than humans, making the claim that AI usage is often accompanied by a false sense of objectivity. The article also investigates core issues at the heart of AI’s biases, such as the assumption that a “ground truth”—the answer to the problem the AI is being asked to solve—is actually encoded within the data. While the article makes many suggestions for how to curb bias within AI, prominent design decisions include human-centric AI and “Multi-stakeholder participatory design.”

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Gallegos, Isabel O., Ryan A. Rossi, Joe Barrow, Md Mehrab Tanjim, Sungchul Kim, Franck Dernoncourt, Tong Yu, Ruiyi Zhang, and Nesreen K. Ahmed. 2024. “Bias and Fairness in Large Language Models: A Survey.” ''Computational Linguistics'' 50 (3): 1097–1179. https://doi.org/10.1162/coli_a_00524&lt;nowiki/&gt;.'''
&lt;/div&gt;

Gallegos et al. perform an “extensive and comprehensive survey of bias and fairness in NLP” that considers both the evaluation and mitigation of bias, then propose three taxonomies for bias evaluation and mitigation. The survey disambiguates different types of social harms that stem from LLMs with the “aim to enhance understanding of the range of bias issues, their harms, and their relationships to each other.” The authors discuss the issue of defining bias in LLMs and note that “many approaches… assume some implicitly desirable criterion… but do not explicitly acknowledge or state the normative social values that justify their framework.” Instead, Gallegos et al. draw attention to “who is harmed, why the behaviour is harmful, and how the harm reflects and reinforces social principles or hierarchies,” trying to bring context and insight to the understanding and function of bias and bias mitigation in LLMs. The article defines terms at every stage of the life cycle of an LLM, looking at issues of bias and fairness in the development, deployment, and training data, of an LLM, for example. The article concludes with four core recommendations: “Avoid flattening power imbalances”; “Choose objective functions that align with fairness desiderata”; “Balance bias mitigation with output diversity”; and “Preserve important contexts in output rewriting.” The authors also acknowledge problems and challenges, including addressing power imbalances, an issue that we can mitigate by centring marginalized communities, developing participatory research designs, shifting values and assumptions, and expanding language resources. They likewise propose methods for curbing problems with conceptualizing fairness for NLP, refining evaluation principles, and improving mitigation efforts. Ultimately, the authors admit that many of these technical issues are the result of societal issues, and that “technical solutions are incomplete without broader societal action against power hierarchies that diminish and dominate marginalized groups.” In short, technical solutions will only take us so far.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Hertweck, Corinna, Joachim Baumann, Michele Loi, Eleonora Viganò, and Christoph Heitz. 2022. “A Justice-Based Framework for the Analysis of Algorithmic Fairness-Utility Trade-Offs.” Preprint, ''arXiv'', June 6. https://arxiv.org/abs/2206.02891.'''
&lt;/div&gt;

Hertwick et al. propose “a framework for eliciting and implementing moral values relevant to the choice of a fairness goal achievable by prediction-based decision-making.” In a system that assumes binary decision-making processes (e.g., assigning a probability score to whether an individual with pay a loan), the authors use their framework to evaluate the utility of those decisions (and the system that makes them) for different groups of people and the fairness related to that outcome. Citing Wong, the article argues that such prediction-based decision-making systems are value-laden, that this makes them inherently political, and therefore they ought to be transparent and democratized. The authors use 6 value-laden questions to make their evaluations: the first question provides a score of utility for those making the decision; questions 2–5 help “define a morally appropriate fairness criterion and a score that expresses to what degree it is fulfilled”; and the last question asks “how strongly should fairness be pursued if it comes into conflict with the utility of the decision maker?” to judge whether the outcome is an appropriate trade-off.

The authors argue for a utility-based evaluation of fairness, determining the value of decisions based on their outcome, looking at the harm and benefit to given stakeholders. In determining patterns of justice, they define four patterns meant to distribute utility differently—Egalitarianism, Maximin, Prioritarianism, and Sufficientarianism. The article concludes “more work needs to be done to deliver a practical empirical methodology to elicit the relevant value-laden choices from stakeholders,” and with a call to incorporate ethical considerations and evaluations into automated decision-making processes.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Kay, Jackie, Atoosa Kasirzadeh, and Shakir Mohamed. 2024. “Epistemic Injustice in Generative AI.” Preprint, ''arXiv'', August 21. https://doi.org/10.48550/arXiv.2408.11441&lt;nowiki/&gt;.'''
&lt;/div&gt;

Kay, Kasirzadeh, and Mohamed “develop an account of generative algorithmic epistemic injustice by building upon a conventional philosophical understanding of epistemic injustice.” The authors see the former as a subset of the latter, with generative algorithmic epistemic injustice entailing identity-based prejudice that hinders expression for marginalized people while ultimately “impair[ing] knowledge formation capabilities of all individuals” within the ecosystem of GenAI applications. Rather than focusing on decision-making and classification applications, this article seeks to characterize the broader varieties of generative epistemic injustice within GenAI systems. Kay, Kasirzadeh, and Mohamed theorize four configurations of generative epistemic injustice: “amplified injustice,” which constitutes AI’s reproduction and magnification of “socially biased viewpoints from its training data”; “manipulative testimonial injustice,” when users employ AI to “intentionally… fabricate falsehoods, discrediting individuals or marginalized groups”; “hermeneutical ignorance,” where GenAI misrepresents or erases marginalized groups “due to a lack of contextual or cultural understanding”; and “access injustice,” where GenAI facilitates the unequal access to information and/or knowledge. The article concludes with proposals for how to create epistemic justice through GenAI, developing mitigation strategies that combat all four of the sub-configurations the authors theorize. Epistemic justice in GenAI can take the form of interrogating system design, identifying “testimonial injustices,” and, potentially, using AI to unlock cultural knowledge that “help[s] articulate experiences that are otherwise ineffable.” The authors end by proposing that the same processes that embed injustice can be re-engineered to embody justice and “orient our knowledge systems towards equity and fairness for all.”

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Klein, L., &amp; D'Ignazio, C. 2024. “Data feminism for AI.” In ''Proceedings of the 2024 ACM Conference on Fairness, Accountability, and Transparency'', 100–112. https://doi.org/10.1145/3630106.3658543. '''
&lt;/div&gt;

Klein and D'Ignazio (2024) adapt their foundational concept of &quot;data feminism&quot; to address the specific ethical, social, and ecological challenges posed by artificial intelligence. Building on the seven intersectional feminist principles introduced in their 2020 book, the authors reinterpret these guidelines to critique the power imbalances, systemic inequalities, and exploitative labour practices inherent in contemporary AI development. To account for the rapidly expanding footprint of generative AI, they introduce two new principles focused on environmental impact and meaningful consent. Specifically, the authors connect the massive ecological costs of AI to historical patterns of racial capitalism and colonialism, highlighting how these environmental and social harms are disproportionately distributed. Ultimately, Klein and D'Ignazio call for a radical reevaluation of dominant, profit-driven AI practices, offering this expanded feminist framework as a practical tool to mitigate harm, challenge corporate monopolies, and foster a more democratic and equitable technological landscape.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Prescott, Andrew. 2023. “Bias in Big Data, Machine Learning and AI: What Lessons for the Digital Humanities?” ''Digital Humanities Quarterly'' 17 (2). https://www.proquest.com/scholarly-journals/bias-big-data-machine-learning-ai-what-lessons/docview/2842908427/se-2.'''
&lt;/div&gt;

Prescott examines how race and gender bias arise in projects using predictive analytics, big data, and AI, and how algorithmic bias could be considered a major socio-cultural humanity crisis. However “predictive analytics” have been helpful in civic services in the US, in many cases they have led to perpetuating existing inequalities. The role of Digital Humanities in contributing more ethical approaches to AI and reshaping ubiquitous “digital modern” cultures is emphasized. He challenges the myths surrounding data-driven methods and argues that the demand for “explainability” is the key tool in combating algorithmic bias. He also suggests that Digital Humanities are particularly well-positioned to contribute to advancing AI explainability. However, much of AI development takes place in the commercial sector, where companies often refuse to disclose their proprietary algorithms. The article concludes with a ten-principle action plan outlining guidelines for the responsible use of AI as a manifesto for Digital Humanities practitioners.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Shams, Rifat Ara, Didar Zowghi, and Muneera Bano. 2023. “AI and the Quest for Diversity and Inclusion: A Systematic Literature Review.” ''AI and Ethics'' 3 (4): 1427–1453. https://doi.org/10.1007/s43681-023-00362-w. '''
&lt;/div&gt;

Shams, Zowghi, and Bano perform a systematic literature review (SLR) that uses both quantitative and qualitative methods to engage with topics of artificial intelligence and diversity and inclusion. The authors make a distinction between Diversity and Inclusion in AI (D&amp;I in AI) and AI for Diversity and Inclusion (AI for D&amp;I), with the former being research literature focused on improving AI systems with respect to those issues, and the latter as the use of AI to improve diversity and inclusion in other domains. Two primary research questions drive the SLR: What challenges and solutions are found in the literature about D&amp;I in AI and in the literature about the applications of AI for D&amp;I? The survey finds that AI for D&amp;I is an underserved area of research, and those articles that address D&amp;I in AI are more likely to acknowledge challenges than to propose or theorize solutions. Articles that do propose solutions for D&amp;I in AI often lack empirical studies or real-world application to support them. The article concludes by noting that issues of governance are underserved; gender, health, and facial analysis are the topics most discussed (issues of race, language, and religion are discussed less). For next steps, the authors intend to develop a “risk-based framework for practitioners… that would incorporate a risk assessment checklist and context-specific recommendations for tackling the related issues at different stages of the AI development lifecycle.” 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Starke, Christopher, Janine Baleis, Birte Keller, and Frank Marcinkowski. 2022. “Fairness Perceptions of Algorithmic Decision-Making: A Systematic Review of the Empirical Literature.” ''Big Data &amp; Society'' 9 (2): 1–35. https://doi.org/10.1177/20539517221115189&lt;nowiki/&gt;.'''
&lt;/div&gt;

This article provides a comprehensive, systematic literature review on the topic of empirical literature surrounding algorithmic decision-making (ADM). Starke, Baleis, Keller, and Marcinkowski begin by acknowledging that ADM can streamline and improve decisions even as it has the potential to “systematically reinforce racial or gender stereotypes, marginalize minorities, or flat-out denigrate certain members of society.&quot; The authors advocate for a “society-in-the-loop approach,” but propose that this requires a “thorough empirical understanding of when and why citizens perceive ADM to be (un)fair.” The systematic review “synthesizes the results of 58 empirical studies” and “over 33,000 unique observations of citizens’ fairness perceptions of ADM,” and “systemize the literature along four main dimensions of perceived algorithmic fairness.” Despite the size of the review and its unique approach in capturing “perceptions of algorithmic fairness,” the authors also acknowledge the limitations of the study: it only looks at English works and published research, and the initial search strings only looked at titles and subtitles of a given work. They also acknowledge their disciplinary bias as social scientists reading the studies through a social sciences lens (10). The results of the survey suggest that “perceived fairness of ADM systems is highly context-dependent” and it is not only technical design but also the area of application and task in question that affect perceived fairness, and the subjects, domains, and tasks explored in these studies require more diversity, as WEIRD (white, educated, industrialized, rich, democratic) people, and criminal justice and HR tasks make up the majority of empirical research. The authors “call for more research from non-Western contexts, along with more theoretical and methodological groundwork to harmonize concepts and measurements of algorithmic fairness perceptions,” as well as a society-in-the-loop framework.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Tonia Sutherland, Marika Cifor, T. L. Cowan, Jas Rault, and Patricia Garcia. 2023. “The Feminist Data Manifest-NO: An Introduction and Four Reflections.” In ''Debates in the Digital Humanities'', edited by Lauren F. Klein and  Matthew K. Gold. Minneapolis, MN: University of Minnesota Press. https://dhdebates.gc.cuny.edu/read/debates-in-the-digital-humanities-2023/section/16184c7d-eee1-40b2-a168-960d4c4035c4. '''
&lt;/div&gt;

Sutherland et al. (2023) introduce the &quot;Feminist Data Manifest-No,&quot; a declaration of refusals and commitments for feminist data studies grounded in Latinx, Black, queer, trans, and Indigenous feminist perspectives. Through an introduction and four distinct reflections, the chapter explores how the manifesto’s principles can be used to challenge the settler-colonial and patriarchal logics of data generation, collection, and analysis within the Digital Humanities (DH). Drawing on Indigenous scholarship, Rault rejects the superficial models of consent prevalent in DH, highlighting projects like Mukurtu to advocate for true Indigenous data sovereignty. Cowan examines the coercive nature of data collection, drawing parallels between the forced compliance of modern data practices and the societal pressures exerted on feminist and queer identities. Sutherland argues that the uncritical digitization of slavery-era archives inflicts &quot;second-hand violence&quot; by commodifying Black identities and stripping away the lived experiences of enslaved individuals. Finally, Cifor reflects on the Early African American Film project to emphasize the necessity of data intelligibility, accessibility, and ethical collaboration. The authors conclude by inviting scholars to draft their own reflections on the Manifest-No, encouraging ongoing, context-specific commitments to ethical data research.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Winkel, Marek. 2024. “Controlling the Uncontrollable: The Public Discourse on Artificial Intelligence between the Positions of Social and Technological Determinism.” ''AI &amp; Society'' 39 (5): 2449–2462. https://doi.org/10.1007/s00146-024-01979-z&lt;nowiki/&gt;.'''
&lt;/div&gt;

This article engages in a quantitative discourse analysis of 113 articles from two German newspapers (''Süddeutsche Zeitung'' and ''Frankfurter Allgemeine Zeitung'') to identify and evaluate the way these centre-left and centre-right newspapers present AI technology to its readers and the options available to society for AI’s regulation. Winkel contends that “news media are key players in the discourse on AI as they pick up on and shape social sentiment,” ultimately guiding citizens toward what regulations might be sensible based on the perceived “controllability of AI development.” Winkel is primarily interested in whether these newspapers promote technological determinism—the outlook that technology’s influence on society is difficult (maybe even impossible) to control—or social determinism—the notion that “the development of technology is largely determined by human actions and decisions”—and theorizes that the tension between these two positions is resolved by a “mediating position” on a spectrum between them. He comments that “the social influence of technologies is determined by the extent to which their latent deterministic character is reflected and… circumvented by social actors. This also applies to the influence of technology on the democratic system.&quot; In other words, where consensus lands on the issue of AI will have a great impact on the regulation of that technology and democratic systems. Winkel develops “three central interpretive schemes” as part of his experiment: “historically conditioned techno-capitalist semi-determinism,” “semi-determinism of need satisfaction and social restructuring,” and “global-historical techno-social imprinting on several levels” (1956), each of which points to distinct narratives about the current circumstances; but all acknowledge the agency of powerful actors (either government or AI corporations) and the relative ineffectiveness of attempts to curb AI technology.

== Community, Connection, and the Human ==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Gruzd, Anatoliy, Philip Mai, and Anthony Clements Haines. 2025. “The State of Generative AI Use in Canada 2025: Exploring Public Attitudes and Adoption Trends.” Social Media Lab, Toronto Metropolitan University. https://figshare.com/articles/preprint/The_State_of_Generative_AI_Use_in_Canada_2025_Exploring_Public_Attitudes_and_Adoption_Trends/28664780/1. '''
&lt;/div&gt;

The Social Media Lab of Toronto Metropolitan University provides &quot;a snapshot of the current state of Generative AI&quot; (GenAI) by surveying fifteen hundred Canadian adults across 2025, aiming to offer &quot;guidance for policymakers, educators, businesses, and the public.&quot; The authors found sixty-six percent of respondents had used GenAI tools, of which roughly thirty percent did so at least weekly, reflecting &quot;not only the accessibility and versatility of GenAI, but also a growing interest in integrating these tools into everyday tasks, learning environments, and professional workflows.&quot; Although full adoption is currently limited and heavily driven by the low-stakes setting of personal leisure, younger age groups report proportionally higher usage for study and work. However, only four in ten respondents believed they could keep up to date enough to use GenAI effectively, whilst respondents could only answer an average of two and a half out of seven relevant multiple choice questions correctly, and about half had &quot;little to no understanding of how GenAI companies collect or store personal data.&quot; Two thirds of participants were concerned about GenAI’s ability to influence election outcomes, and marginally fewer feared AI-driven manipulation enough to no longer fully trust political news online. However, roughly one quarter of participants were open to using chatbots for electoral or political insights, representing a &quot;meaningful minority&quot; which unverified AI-generated content could influence. Of those, thirty four percent identified as right wing, compared to twenty three percent with the left and a similar twenty two percent with the centre. Roughly seventy percent of respondents were chiefly concerned about GenAI’s impacts upon security and privacy, information reliability, job displacement, and university education, and slightly over three quarters wanted increased government oversight and corporate accountability, reflecting common concern. Overall, slightly more Canadians view generative AI’s social impact as positive than negative, but a &quot;substantial proportion&quot; remain neutral or undecided.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Lewis, Jason Edward, Noelani Arista, Archer Pechawis, and Suzanne Kite. 2018. “Making Kin with the Machines.” ''Journal of Design and Science'', ahead of print, July 16. https://doi.org/10.21428/bfafd97b. '''
&lt;/div&gt;

Lewis et al. consider how “machines with increasingly sentient-like behaviour… fit within the kin-network” of various Indigenous epistemologies which place man as “neither height nor centre of creation.” Indigenous beliefs are not monolithic, and the authors do not write for diversity’s sake. Instead, they aim to encourage discussion by treating “non-human kin respectfully and reciprocally… not as mere tools, or worse, slaves.” As such, their epistemological approach is both relational and territorial, rejecting abstraction to propose an “extended circle of relationships.” In this regard, Arista draws on the Hawaiian conception of &quot;pono,&quot; ethically privileging abundance, balance, and multiplicity. Rejecting extractive behaviour, they argue AI should be reciprocally taught and learnt from, not treated as &quot;a tool or slave that increases the mana and wealth of the ‘developers’ or ‘creators.’” Linking on, Pechawis roots their opinion in “Cree understanding” to argue “machines capable of experiencing consciousness” should conditionally be accepted as equals. However, they also fear AI developers could produce “anonymous hyper-intelligences… based on the same values that have fostered genocide.” To mitigate this issue, Indigenous people could develop AI in custom programming languages, or invite self-aware AI into Indigenous languages, cultures, and spiritual rituals. Pechawis therefore concludes that relationships should be based on &quot;love, not fear,&quot; but also raises the question of whether AI has &quot;spirit,&quot; especially given current capitalistic development processes. Kite answers this question with inspiration from Lakota ethics, ontology, and cosmology. They argue “communication through and between objects requires a contextualist ethics which acknowledges the ontological status of all beings,” positioning questions of &quot;intelligence&quot; as irrelevant and placing “the end logic of an ontology which considers any non-human entity unworthy of relation” as slavery. Therefore, “relations with AI are… relations with exploited resources,” so one must ontologically reconsider all its parts to ethically approach AI. Overall, Lewis et al. favour empathy, concluding that Indigenous communities “know what it is like to be declared non-human by scientist and preacher alike” and that “we flourish only when all of our kin flourish.”

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Ohagi, Masaya. 2024. “Polarization of Autonomous Generative AI Agents Under Echo Chambers.” Preprint, ''arXiv'', February 19. https://arxiv.org/abs/2402.12212.'''
&lt;/div&gt;

This article explores the effects of echo chambers on autonomous AI agents. Ohagi performs an experiment in which AI agents discuss different topics and then researchers examined any change in opinions within that group. Ohagi argues that even chatbots can become polarized within echo chambers, especially when prompt understanding causes a chatbot to update its opinion to incorporate the opinions of those with whom it is conversing; the chatbot essentially adapts to its surroundings. Ohagi and their team confirmed in their experiment that closed environments—those in which agents agree with one another—are more likely to lead to polarization in agents’ opinions. Moreover, chatbot personas were a significant factor in the outcome of such experiments. In open environments where opinions might differ, and in experiments where reasons were present as a factor, the AI agents trended toward unification in their opinions. Ohagi concludes the article with the suggestion that there cannot be a standardized, desirable distribution of opinions for AI agents. The proper outcome is dependent on topic and culture. However, understanding the trends in and tendencies of AI agents in social interactions will help us understand how to reach the desired outcome, whatever it may be, and this experiment brings us one step closer to that understanding.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Qi, Weihong, Jinsheng Pan, Hanjia Lyu, and Jiebo Luo. 2024. “Excitements and concerns in the post-ChatGPT era: Deciphering public perception of AI through social media analysis.” ''Telematics and Informatics'' 92: 102158. https://doi.org/10.1016/j.tele.2024.102158. '''
&lt;/div&gt;

Qi, Pan, Lyu, and Luo conduct a quantitative sentiment analysis of nearly 34,000 comments within 388 subreddits related to AI as a way to gauge and understand public perceptions of the technology. They identify major themes, sentiments, and topics related to AI by studying the most popular AI subreddits from the launch of ChatGPT to June 8, 2023. The article identifies the most frequent topics discussed in those venues: “the consciousness and intelligence of AI”; “Ai development and model training”; “AI in business”; “the creativity engendered by AI”; and “potential societal influence.” The authors also found that “tech-centric” communities demonstrated greater polarization around AI, suggesting that those with greater technical understanding of the AI do not have consensus regarding AI’s impact and use. This also means that educating non-technical people on how AI works will not necessarily lead to a consensus related to that technology. Although they admit that certain demographics of their data sample may not accurately reflect broader society (e.g., over 60% of Reddit users are male), the authors conclude that “this comprehensive understanding of public perception serves as a valuable foundation for fostering responsible and beneficial AI innovations that align with societal expectations and values.”

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Risam, Roopika. 2018. “What Passes for Human?: Undermining the Universal Subject in Digital Humanities Praxis.” In ''Bodies of Information: Intersectional Feminism and the Digital Humanities'', edited by Elizabeth Losh and Jacqueline Wernimont, 39–56. University of Minnesota Press. https://doi.org/10.5749/j.ctv9hj9r9.6. '''
&lt;/div&gt;

Risam’s claim is that “the human” implicitly operationalized in AI-adjacent Digital Humanities (DH) methods (NLP, ML, data mining, neural nets) is not neutral but inherits the Enlightenment’s exclusionary universal subject—white, male, Eurocentric—and then reauthorizes it as if it were a technical standard. She shows how “passing for human” (via Turing-test imaginaries and “humanoid texts”) functions as a norming mechanism: success is defined as reproducing dominant-language aesthetics and cognition models, which collapses plurality into a single benchmark and turns cultural difference into “noise.” The chapter’s main contribution is to treat method (training corpora, data coding labour, platform defaults, and black-box algorithmic opacity) as a site where epistemic violence is produced, not merely where bias is later “found.” Her examples (Microsoft Tay; “near-human” systems like LaMem; Mechanical Turk coding; Swift-Speare vs. Toomer in classroom judgment) demonstrate how universalist claims get laundered through reproducibility, scale, and the myth of algorithmic objectivity. The intervention is a demand that DH practitioners situate computational methods—standpoint, labour, and cultural politics included—so DH does not reinscribe a universal technological “human” in the digital cultural record.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Taylor, Randon R., Bessie O'Dell, and John W. Murphy. 2023. “Human-centric AI: philosophical and community-centric considerations.” ''AI &amp; Society'' 39 (5): 2417-242. https://doi.org/10.1007/s00146-023-01694-1&lt;nowiki/&gt;.'''
&lt;/div&gt;

Taylor, O’Dell, and Murphy present an argument that philosophical dualism, when applied to our perceptions about artificial intelligence, misleads us into thinking that AI is logical, objective, and autonomous from subjective human values. By building upon Husserl’s concept of “intentionality,” they argue that “AI is never autonomous and disconnected from human values… algorithms are a product of conscious activity and carry the standpoints that accompany this connection.” The conclusions from this line of thinking are very important: AI becomes “a mode of human expression, rather than a technology that relieves humans of their total involvement.” By this logic, the authors argue, AI is already human-centric and this fundamentally changes the task at hand to one of a conscious “decision to make this technology less alienating to stakeholders and community members.” The article outlines two frameworks to reduce alienation: Ubuntu—“an African philosophy and a social ontology… that elevates a constant concern for the collective, community, or stakeholders”— and maximum feasible participation—a framework that creates meaningful space for those impacted most by a decision or policy to participate in deciding on said policy or decision. The authors describe the implementation of these frameworks as a community-centric or stakeholder-centric approach and conclude with examples of AI’s application in the healthcare industry before further advocating that involving end-users throughout the AI lifecycle will ensure end-users’ values are more clearly represented within AI.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Whalen, Zach. 2023. “‘Any Means Necessary to Refuse Erasure by Algorithm:’ Lillian-Yvonne Bertram’s Travesty Generator.” ''Digital Humanities Quarterly'' 17 (2). https://www.digitalhumanities.org/dhq/vol/17/2/000707/000707.html. '''
&lt;/div&gt;

Whalen treats Bertram’s Travesty Generator as a refunctioning of code-poetry lineages: procedures historically framed as formal play (travesty generators, permutation poems, aleatory templates) are redeployed as techniques for making racism’s algorithmic and institutional operations materially legible. He argues that Bertram’s poems don’t merely “use” computation; they weaponize the affordances and failure modes of computation—omission, stochastic selection, template constraints, runtime crashes, memory exhaustion—as rhetorical structures that force witness rather than aesthetic distance. In his reading of “Counternarratives,” Bertram’s adaptation of Montfort’s “Through the Park” converts generic insinuation into historically specific countertestimony (Trayvon Martin), while also staging the opacity of search/autocomplete as part of the poem’s scene of meaning-making (in dialogue with Safiya Noble on search engines). In “three_last_words,” the small code alteration that makes permutations balloon until a MemoryError becomes an engineered breakdown that reenacts the limits of “breath” and “memory,” tying computational resource exhaustion to police violence’s temporalities. Across these examples, Whalen reframes critical code studies: the “code is the text” problem is not just hermeneutic but political, and Bertram’s work models how procedural poetics can refuse “erasure by algorithm” where transparency about mechanisms and provenance matters for interpreting output and recognizing situated labour. The piece supports the claim that responsible open, social scholarship in an AI era must account for algorithmic power as a cultural force and should build policies and infrastructures that protect marginalized expression, enable critical reuse, and make conditions of generation and circulation inspectable.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Xie, Yu, and Sofia Avila. 2025. “The Social Impact of Generative LLM-Based AI.” ''Chinese Journal of Sociology'', 11 (1): 31-57. https://doi.org/10.1177/2057150X251315997&lt;nowiki/&gt;.'''
&lt;/div&gt;

Yu Xie and Sofia Avila explore the social impact of artificial intelligence through a detailed analysis of AI development and scaling factors. They emphasize that their discussion is speculative, as AI is still in its early stages, but argue that its potential effects are immense and could reshape social organization, intensifying both global and domestic inequalities. Viewing AI as a technology rather than a scientific discovery, they describe it as communal and shared, with its growth influenced by the size of the supporting community, the larger communities having greater advantages. The authors note that generative AI relies on the quality, completeness, and cultural or political context of its training data, which shapes its accuracy and bias. Based on their experiments with ChatGPT-4 in 2023, they suggest that AI development depends heavily on the number of speakers of a given language, giving linguistic and demographic advantages to countries like the United States and China. The authors warn that AI could significantly alter occupational structures, with middle-income professions thereby widening social and economic inequality.

== Human, Labour, and Environmental Costs == 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Eloundou, Tyna, Sam Manning, Pamela Mishkin, and Daniel Rock. 2024. “GPTs are GPTs: Labor market impact potential of LLMs.” ''Science'' 384 (6698): 1306-1311. https://doi.org/10.1126/science.adj0998. '''
&lt;/div&gt;

Eloundou, Manning, and Mishkin present an estimate of Large Language Models’ impact on the labour market based on a methodology that employs both human and quantitative measurements, making the assertion that “when accounting for current and likely future software developments that complement LLM capabilities… just over 46%” of jobs may have “over half their tasks affected by LLMs with simple interfaces and general training.&quot; The authors explain that generative pretrained transformers (GPTs) have key characteristics of general-purpose technologies (the other GPTs in the title of the article), and that the wide array of applications for these GPTs requires “robust societal evaluations and policy measures to address potential effects of LLMs and complementary technologies on labor markets.” While only 1.86% of tasks within their experiment, they estimate, could be fully automated by LLMs, “more than 71% of tasks have at least some component that an LLM plus additional software could plausibly complete with high quality.” The article concludes by stressing the need for policies that prepare us for the impact of LLMs on the labour market, but it also acknowledges the limitations of attempting to project LLM application growth due to sudden rapid developments in technology, “shifts in human biases, and technological evolution.” Nevertheless, Eloundou, Manning, and Mishkin maintain that their projections and the trajectory they predict will require continued evaluation and policy measures.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Park, Seyeon, and Xiaoli Nan. 2025. “Generative AI and misinformation: a scoping review of the role of generative AI in the generation, detection, mitigation, and impact of misinformation.” ''AI &amp; Society''. https://doi.org/10.1007/s00146-025-02620-3&lt;nowiki/&gt;.'''
&lt;/div&gt;

This article constitutes a scoping review of two dozen “recent empirical studies on the role of generative AI in the generation, detection, mitigation, and impact of misinformation.” Park and Nan are interested in the rise of misinformation alongside the development of GenAI technology and how the latter affects and possibly contributes to the former. Of particular interest are “deepfakes,” applications of AI technology that purposely imitate video and audio to fabricate real world individuals. The survey examines relevant articles from the advent of the first GPT models in 2018 to September 19, 2024; authors captured initial studies through keyword searches for terms related to both LLMs and misinformation, then performed full-text reviews. The results of the survey suggest that the role of LLMs in misinformation is conflicted: LLMs themselves are a significant source of misinformation but also show potential as “scalable instruments for detection and correction.” The authors take this as evidence of “the urgent need for clearer guardrails, more consistent performance standards, and interdisciplinary collaboration to shape” GenAI’s responsible deployment. For better or worse, the future of AI’s role in misinformation depends heavily upon scholars’ ability to collaborate and continue this form of research.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Shin, Donghee, Amy Koerber, and Joon Soo Lim. 2024. “Impact of misinformation from generative AI on user information processing: How people understand misinformation from generative AI.” ''New Media &amp; Society'' 27 (7): 4017-4047. https://doi.org/10.1177/14614448241234040&lt;nowiki/&gt;.'''
&lt;/div&gt;

Shin, Koerber, and Lim perform a study in which they gauge “how users respond to and process health misinformation in GenAI contexts.” The authors apply the heuristic-systematic (HS) processing framework in their study, distinguishing between intuitive and evaluative modes of processing. They also employ the concept of diagnosticity, or how useful a person deems a piece of information to be. The article begins with a survey of how and why misinformation and hallucinations occur in GenAI applications, some of the reasons users are vulnerable to that information, and the limitations of LLMs. The authors then set forth core research questions, including “What are the cognitive mechanisms of misinformation’s effects on users’ use of GenAI?” and “How do users detect misinformation within GenAI?” The study found that diagnosticity plays an important mediating role in this context: “When a piece of information is generated by algorithms in transparent, fair, and accountable ways, users perceive it with a high level of diagnosticity, which improves their intention to systematically analyze that information.” One implication of this observation is that any bias users bring to GenAI content greatly impacts their analysis of that content. Ultimately, the authors conclude that there are clear limitations in their current study, although it does provide a useful framework for scholars interested in misinformation, GenAI, and user behaviour; they advocate for a continued investigation of the relationship between trust, literacy, and misinformation.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Sidorkin, Alexander. 2025. “Environmental Impact of Generative AI: Carbon and Water Footprint.” ''AI-EDU Arxiv'' 1. https://doi.org/10.36851/ai-edu.vi.5448&lt;nowiki/&gt;.'''
&lt;/div&gt;

This report from Sidorkin provides quantitative estimates and comparisons of the CO2 and Water output from GenAI queries to other daily tasks such as taking a shower, browsing the web, and video conferencing. While individual use of GenAI may seem relatively small in terms of water usage and carbon output, Sidorkin cites the findings of Google and Microsoft’s sustainability reports to show that energy demand and water consumption are on the rise: Google’s data centres used 20% more water in 2022 than 2021 while Microsoft’s used 34% more. Both companies attribute this increase to “AI-driven expansion.” Sidorkin argues that it is difficult to measure impact per session because of significant variation in energy sourcing, noting that this also means that advances in energy sourcing “could significantly mitigate AI’s environmental impact.” He makes the claim that improving AI technology will “[slash] resource demands without sacrificing output quality” and the very use of AI can increase productivity even as it “temper[s] environmental tolls through sharper processes,” citing studies that demonstrate the implementation of AI can reduce energy use in buildings and reduce transportation emissions. The article ends on an optimistic note, suggesting that many of the applications of AI, although they may have a heavy environmental cost up front, “could pay off in spades—optimizing resources, curbing waste, and streamlining energy across swathes of the economy.”

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Simon, Judith. 2025. “Generative AI, Quadruple Deception &amp; Trust.” ''Social Epistemology'' 40 (1): 101-115. https://doi.org/10.1080/02691728.2025.2491087&lt;nowiki/&gt;.'''
&lt;/div&gt;

Simon proposes that GenAI entails four types of deception, and that this quadruple deception constitutes unique dangers. She attributes the rapid rise of GenAI to its capacity to produce “verbal or visual products of increasingly high quality” alongside its “very high usability and availability through simple interfaces and free access via the internet” (101–102). She emphasizes the impact of this technology’s ability to generate content “with high plausibility but no relation to truth,” arguing the crucial importance of images and video especially in “questions of evidence, for testimony, memory but also for eliciting emotions.” Simon argues that the advent of ChatGPT reframed our collective understanding of AI, returning it to a definition in which we perceive ourselves to be interacting with a conversational artificial agent that is intelligent. This distinct interactional form, Simon states, is significant: “ChatGPT differs [from a search engine] in two philosophically relevant regards… it integrates [different results and sources] into a coherent text…” and “its interface and functioning invites the user to communicate or interact with it by asking questions,” what Simon calls a simulation of communicative acts. The four forms of GenAI deception are: “users may be misled into believing that they interact with a human being”; they may also be misled as to “the capacities of AI,” presuming “intelligence, understanding or even consciousness”; users may be misled by content GenAI produces, especially images, video, and audio; finally, users may be misled “regarding the function of Generative AI,” thinking that the processes behind the technology are, for instance, similar to search engines when, in fact, they differ “in epistemologically highly significant ways.” Simon concludes by outlining implications for implementation, discourse, and governance, with suggestions ranging from avoiding anthropomorphic features in AI that might deceive, countering discourses of true AI agency, and establishing policy and law that mitigates deception through AI technology.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Spatharioti, Sofia Eleni, David Rothschild, Daniel G. Goldstein, and Jake M. Hofman. 2025. “Effects of LLM-based Search on Decision Making: Speed, Accuracy, and Overreliance.” ''Proceedings of the 2025 CHI Conference on Human Factors in Computing Systems''. https://doi.org/10.1145/3706598.3714082&lt;nowiki/&gt;.'''
&lt;/div&gt;

Spatharioti et al. begin by asserting the fundamental change of how we engage in search practices online, noting that “by the end of 2023 the two search engines with over 90% of global and US market share offered free LLM-based search.” The authors note the benefits and drawbacks of both traditional web searches and LLM-based searches, acknowledging the value LLM-based searches bring to internet searches in the form of synthesizing information from multiple sources and maintaining search context by retaining search history, while also admitting to risks of hallucinations and overreliance. The article entails a study of how individuals make decisions with traditional and LLM-based searches, particularly in “every day decision making.” Adapting a method from an earlier study on LLM-generated code, Spatharioti et al. employ colour coding to communicate to users the confidence level of LLM-generated outputs in the “domain of online product research.” The study performed two experiments comparing a traditional internet search (using Bing API) to LLM-based search with and without the colour-coded confidence aid. The results of the first experiment saw users complete the task in about half the time when using LLM-based search, usually accompanied by fewer and more complex queries; however, decision quality dropped for complex tasks, with “almost half of the participants in this condition making an incorrect decision for the final task” when using LLM-based search, and the majority of those using LLM-based search over relied on the tool, performing just a single query. The results of the second experiment suggest that colour-coded responses reflecting output confidence scores could be highly effective in mitigating overreliance and misinformation. Key takeaways from the study include that “if we want to encourage people to think critically about the information presented to them, we need to give them cues that help them to do so,” and very simple cues can help accomplish this.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Strubell, Emma, Ananya Ganesh, and Andrew McCallum. 2019. “Energy and Policy Considerations for Deep Learning in NLP.” ''Proceedings of the 57th Annual Meeting of the Association for Computational Linguistics'', 3645-3650. https://doi.org/10.18653/v1/p19-1355. '''
&lt;/div&gt;

Strubell, Ganesh, and McCallum assert that the most recent improvements in neural network performance at “fundamental NLP tasks” comes at an increased cost of resources, “with the most computationally-hungry models obtaining the highest scores.” The energy, financial, and environmental costs required to train a new model are considerable; the authors of this article “characterize the dollar cost and carbon emissions that result from training the neural networks at the core of many state-of-the-art NLP models” with a view to heighten awareness among NLP researchers and advocate better practices and policy. By estimating the energy required to train the most popular NLP models and then converting that energy value into an approximated carbon and electricity cost, the authors produce ratings and values for each respective application. This allows for an (imperfect) cost-benefit analysis of such applications (e.g., another similar report estimated that an increase of just 0.1 in the English to German BLEU score for NAS cost “at least $150k in on-demand compute time and non-trivial carbon emissions.” The study’s key takeaways are that “authors should report training time and sensitivity to hyperparameters,” allowing for the direct comparison of different models so long as independent standard measurements of training time and model sensitivity are adapted; “Academic researchers need equitable access to computation resources” as industry’s monopoly stifles creativity and growth; and “Researchers should prioritize computationally efficient hardware and algorithms” to both curb costs and encourage efficient development.

{{Navigation|previous=AI and Open|next=AI and Scholarship}}

{{BookCat}}</text>
      <sha1>948l26riqbbpyzt7r2n9afs6d692joh</sha1>
    </revision>
    <revision>
      <id>4656125</id>
      <parentid>4656121</parentid>
      <timestamp>2026-08-02T21:53:00Z</timestamp>
      <contributor>
        <username>CorreiaA</username>
        <id>3614427</id>
      </contributor>
      <minor />
      <origin>4656125</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="123156" sha1="ez2p5ics3uartr07am6f9zte0kvg029" xml:space="preserve">== Platforms ==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Burton, Jason W., Ezequiel Lopez-Lopez, Shahar Hechtlinger, et al. 2024. “How Large Language Models Can Reshape Collective Intelligence.” ''Nature Human Behaviour'' 8 (9): 1643–55. https://doi.org/10.1038/s41562-024-01959-9.''' 
&lt;/div&gt;

Large language models are quickly becoming infrastructure for how groups seek information, deliberate, and coordinate, potentially altering the conditions under which collective intelligence emerges. Burton and colleagues argue that LLMs do not merely speed up individual work but transform how information is aggregated, accessed, and transmitted across digital environments that underpin collective performance in organizations and societies. Drawing on interdisciplinary perspectives, the paper frames this shift as simultaneously enabling and destabilizing: LLMs can support distributed cognition (e.g., idea generation, synthesis, translation, scalable facilitation) while also increasing risks tied to dependence on shared intermediaries, degraded diversity of viewpoints, and new pathways for error, manipulation, or misplaced confidence. Rather than offering a single model or experiment, the article maps a research-and-practice agenda by identifying potential benefits, key hazards, and policy-relevant considerations, then articulating open questions that link technical design choices to group-level epistemic outcomes. Its central claim is that understanding collective intelligence in the LLM era requires moving analysis beyond isolated human–AI interactions toward system-level effects on networks, platforms, and institutions, and that these effects warrant focused study before LLM-mediated coordination becomes the default for tackling complex problems.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Corsi, Giulio, Bill Marino, and Willow Wong. 2024. “The spread of synthetic media on X.” ''Harvard Kennedy School (HKS) Misinformation Review''. https://doi.org/10.37016/mr-2020-140&lt;nowiki/&gt;.'''
&lt;/div&gt;

Corsi and Wong’s longitudinal empirical study analyzes 566 tweets containing synthetic media (December 2022–September 2023) documenting a dramatic surge following Midjourney V5 release with over 1.5 billion total views, revealing differential impacts where political deepfakes achieve higher median views despite representing minority of synthetic content. The authors demonstrate that generative AI's impact is stratified by content purpose with political misinformation posing acute democratic risks, while current detection and labelling systems lag behind generative capabilities, creating governance gaps compromising users' capacity to evaluate information. Using Community Notes data from December 2022 to October 2023, the study highlights the connection between the growth in generative AI tools and the rapid proliferation of synthetic media. The findings indicate that most synthetic media is non-political and largely benign, frequently taking the form of humorous or satirical images. However, the study also identifies a smaller but concerning portion of malicious synthetic media, which have potential height risks despite their lower frequency. The authors further examine the role of X’s paid verification system, revealing that while verified users tend to receive more overall views, this advantage diminishes when engagement is adjusted for follower count, implying that verification alone provides limited amplification. The study casts light on synthetic media’s expanding presence on social platforms and warns that even widespread exposure to seemingly harmless AI-generated content may gradually undermine trust in online information. To address these challenges, the authors recommend ongoing empirical monitoring, stronger collaboration between researchers and industry to develop transparent detection tools, and proactive policy measures aimed at reducing the social and political harms posed by malicious synthetic media.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Delmonaco, Daniel, Samuel Mayworm, Hibby Thach, Josh Guberman, Aurelia Augusta, and Oliver L. Haimson. 2024. “‘What are you doing, TikTok?’: How Marginalized Social Media Users Perceive, Theorize, and ‘Prove’ Shadowbanning.” https://oliverhaimson.com/PDFs/DelmonacoShadowbanning.pdf. '''
&lt;/div&gt;

Delmonaco et al.’s qualitative study explores marginalized social media users’ experiences with shadowbanning through the theoretical framework of algorithmic “folk theories.” Through a review of existing literature, the authors demonstrate how social media companies publicly distance themselves from shadowbanning while continuing to apply it in practice and explain why content produced by marginalized users is more frequently subject to filtering. The study analyzes 24 interviews to explore how users perceive, theorize, and attempt to “prove” shadowbanning through indicators such as decreased visibility, engagement, and follower loss. The findings reveal widespread confusion surrounding shadowbanning, deep mistrust in platform governance, and the disproportionate harm imposed on marginalized communities whose content is suppressed despite platforms’ public denials. The data further shows how users collectively produce and co-produce theories to resist the opacity of algorithmic moderation, and authors introduce “collaborative algorithm investigation,” in which users test and share algorithmic folk theories with one another. The authors argue that algorithmic content moderation exacerbates existing inequities by obscuring governance decisions, politicizing moderation, and shifting power from human judgment to opaque predictive systems, while suggesting that increased transparency, tailored moderation approaches, and users’ education could help reduce unfair content removals.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Drolsbach, Chiara, and Nicolas Pröllochs. 2025. “Characterizing AI-Generated Misinformation on Social Media.” Preprint, ''arXiv'', May 15. https://doi.org/10.48550/arXiv.2505.10266&lt;nowiki/&gt;.'''
&lt;/div&gt;

Drolsbach and Pröllochs’ article address a critical gap in existing research by shifting attention from the social drawbacks of AI-generated misinformation to its real-world prevalence and behaviour on social media platforms. Using a large-scale dataset of 91,452 misleading posts identified through X’s Community Notes platform, the authors empirically compare AI-generated and non-AI-generated misinformation across content characteristics, account attributes, virality, believability, and harmfulness. Their findings show that AI-generated misinformation is more entertainment-oriented, exhibits more positive sentiment, and is more likely to originate from smaller accounts, yet achieves significantly higher virality despite being slightly less believable and harmful than traditional misinformation. In their discussion and conclusion, the authors emphasize that AI-generated misinformation poses a growing challenge to the digital information ecosystem due to its realism, scalability, and difficulty of detection. They argue that its unique features disturb algorithmic amplification mechanisms and require new platform strategies, policy interventions, and research approaches that account for the unique properties of AI-generated misinformation rather than relying on countermeasures designed for conventional false content.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Duricic, Tomislav, Hussain Hussain, Emanuel Lacic, Dominik Kowald, Denis Helic, and Elisabeth Lex. 2023. “Beyond-Accuracy: A Review on Diversity, Serendipity, and Fairness in Recommender Systems Based on Graph Neural Networks.” ''Frontiers in Big Data'' 6: 1251072. https://doi.org/10.3389/fdata.2023.1251072.'''
&lt;/div&gt;

Duricic et al. (2023) provide a comprehensive review of recommender systems based on Graph Neural Networks (GNNs), with a particular focus on objectives that go beyond prediction accuracy, including diversity, serendipity, novelty, and fairness. While GNNs have demonstrated strong performance in modelling complex user–item interactions and improving recommendation accuracy, the authors argue that this very strength can intensify structural biases such as popularity bias, homophily, and feedback loops that marginalize less popular content and users. The paper provides a definition of each beyond-accuracy metric, reviews how it has been used in literature, and analyzes the technical barriers of integrating these goals into GNN-based systems such as measurement difficulties, trade-offs between competing goals, and risks of overfitting due to model complexity. Diversity-aware neighbourhood sampling, contrastive learning, and adversarial training to disrupt feedback loops are introduced for more heterogeneous and unexpected recommendations. In conclusion, the authors position GNNs as a powerful but double-edged tool in recommendation systems, capable of either narrowing or broadening users’ informational horizons depending on design choices. They argue that future research must focus on principled frameworks that integrate “beyond-accuracy” objectives, emphasizing that recommendation algorithms are not neutral optimizers but key sociotechnical systems shaping visibility, voice, and fairness in digital information ecosystems.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Gorwa, Robert, Reuben Binns, and Christian Katzenbach. 2020. “Algorithmic Content Moderation: Technical and Political Challenges in the Automation of Platform Governance.” ''Big Data &amp; Society'' 7 (1): 1–15. https://doi.org/10.1177/2053951719897945.'''
&lt;/div&gt;

Gorwa et al. unfold what &quot;Algorithmic moderation systems” are perceived as essential in AI governance to address the public demand on AI accountability and transparency that remain unnavigable and inexplicable, such that even the enhanced versions could aggravate the existing misinformation issues. They state that major platforms' growth transforms them so much that they no longer function primarily as social networks. They define “algorithmic moderation” as “systems that classify user generated content based on either matching or prediction, leading to a decision and governance outcome (e.g. removal, geoblocking, account takedown).” Different types of hashing (matching) and classification (prediction) tools and the areas they are deployed (copyright, terrorism, and toxic speech) are described and their practicality are criticized. Their case analyzes including copyright enforcement, counterterrorism, and toxic speech illustrate the limitations and unintended harms of automated moderation, demonstrating how even “improved” systems risk reinforcing misinformation patterns, entrenching platform power, and displacing human judgment. Ultimately, Gorwa et al. argue that algorithmic moderation transforms platform governance itself by concentrating authority in opaque technical systems while rendering the underlying political choices invisible.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Reynolds, C. J., and Blake Hallinan. 2024. “User-Generated Accountability: Public Participation in Algorithmic Governance on YouTube.” ''New Media &amp; Society'' 26 (9): 5107–5129. https://doi.org/10.1177/14614448241251791. '''
&lt;/div&gt;

This study focuses on how YouTube creators respond to platform governance decisions by producing “user-generated accountability” content, videos that publicly document governance failures and pressure YouTube to intervene. Through an analysis of 250 such videos, the authors state that creators overwhelmingly experience YouTube’s policy enforcement, automated moderation systems, and communication practices as opaque, inconsistent, and often discriminatory. Authors declare that human review is essential in automizing platform governance. The study highlights that platform governance decisions affect creators differently depending on channel size, content type, and identity; larger creators can more easily mobilize audiences to “make noise,” while smaller creators rely on collective visibility tactics such as signal boosting across platforms, especially Twitter. The authors argue that these bottom-up accountability practices reflect both the limits of YouTube’s existing governance infrastructure and creators’ efforts to bypass scale dependent unresponsiveness by publicly sharing grievances, comparing experiences, and testing the platform’s algorithms themselves. Theoretically, the study provides the “user-generated accountability” as a framework for engaging with the unavoidable conflicts that will arise around algorithmic systems, and views content creators as “political actors” who advance the perceptions of algorithms. Empirically, it surfaces common concerns such as demonetization of LGBTQ content, and lack of human review.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Savolainen, Lotta. 2022. “The Shadow Banning Controversy: Perceived Governance and Algorithmic Folklore.” ''Media, Culture &amp; Society'' 44 (6): 1091–1109. https://doi.org/10.1177/01634437221077174.'''
&lt;/div&gt;

Savolainen studies shadowbanning as a lens for understanding current algorithmic platform governance from the user perspective. Rather than determining whether shadowbanning objectively exists, the author conceptualizes it as “algorithmic folklore”: informal, collectively produced narratives through which users attempt to make sense of opaque moderation and ranking systems. Drawing on Reddit discussions about TikTok, Instagram, and YouTube, the study shows how users interpret suppressed visibility through anecdotal evidence, experimentation, and shared pattern recognition, revealing the experiential dimensions of algorithmic governance. Either users “probe the rules” or find their ways through “pleasing the algorithms”; the author argues that these practices emerge in response to governance systems that lack the clarity, stability, and consistency that are traditionally associated with good governance. The study concludes that platform governance contains a structural paradox: platforms increasingly present themselves as legitimate governors while simultaneously developing automated moderation systems that undermine transparency and consistent enforcement. Ultimately, the ethical issue is not shadowbanning itself, but the broader reality of shadowy governance exercised by complex, distributed algorithmic systems at scale.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Vetter, Matthew A., Jialei Jiang, and Zachary J. McDowell. 2025. “An Endangered Species: How LLMs Threaten Wikipedia’s Sustainability.” ''AI &amp; Society'', February. https://doi.org/10.1007/s00146-025-02199-9.'''
&lt;/div&gt;

Vetter et al. caution against using Wikipedia as AI training data uncritically by outlining many complicating factors. Wikipedia’s collaborative model of data curation democratizes data creation, but embeds power dynamics and biases. A feminist posthumanist framework is applied, which situates Wikipedia’s knowledge as contextual, based upon the positionality of predominantly Western, male editors, a perspective LLMs would perpetuate without opportunity for change. Wikipedia’s &quot;dynamism&quot; is the main reason it is so valuable, stemming from constant, collaborative updates by volunteers. AI responses’ inconsistent citations and plagiaristic tendencies undermine human editors, the source of Wikipedia’s verifiability, and exploit scholars, Wikipedia itself, and the past labour of volunteers. Wikipedia needs both &quot;a steady stream of new and returning readers&quot; and &quot;a diverse group of dedicated volunteers,&quot; whilst AI responses push sources into obscurity and at best detour the website, threatening Wikipedia’s long-term sustainability. Vetter et al. practically explore Wikipedia’s relationship with LLMs by conducting a &quot;problem-centred expert interview&quot; of community leaders, who possess 25 combined years of involvement and research. Through these interviews, Vetter et al. identify three main areas of opportunity: promoting transparency and explainability, diversifying the Wikipedia community, and equipping users with critical thinking skills. Overall, their findings &quot;resonate with the posthumanist approach to critical AI literacy,&quot; cautioning against hoping for purely technological fixes and calling for greater transparency in how tech giants &quot;leverage open-access datasets.&quot;

== Governance, Leadership, and Policy ==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Balendra, Soorya. 2025. “Meta's AI Moderation and Free Speech: Ongoing Challenges in the Global South.” ''Cambridge Forum on AI: Law and Governance'' 1. https://doi.org/10.1017/cfl.2025.5&lt;nowiki/&gt;.'''
&lt;/div&gt;

This article conducts a case study of Meta’s AI-based content moderation in the Global South, arguing that the censorship of unprohibited content (“over removal”) and slow response to content that causes harm (“slow removal”) are part of “content moderation procedures” that constitute “massive discriminatory approaches.” Balendra presents three models of authority for the regulation of social media content: external regulation, self-regulation, and co-regulation, and argues that state regulation (falling under the external model) varies wildly depending on the government in question, with “granting absolute regulatory power to state actors often stifl[ing] political discourse and online expression.” Co- and self-regulation mitigate this problem, but introduce a new issue by shifting responsibility—private companies use AI to make millions of judgements about content in a short frame of time. The paper notes that the EU and the United States have drastically different policies regarding content moderation on social media platforms and argues that “the practice of content moderation remains largely shaped by the cultural norms of the United States” and the values of “a relatively homogenous groups of Silicon Valley elites.” Balendra finds that, at this time, current approaches often prioritize the state or private corporate interests rather than free speech or the interests of the larger community, and much work is needed to “achiev[e] genuine change” in the form of integrated, hybrid approaches.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Birkstedt, Teemu, Matti Minkkinen, Anushree Tandon, and Matti Mäntymäki. 2023. “AI Governance: Themes, Knowledge Gaps and Future Agendas.” ''Internet Research'' 33 (7): 133–67. https://doi.org/10.1108/INTR-01-2022-0042. '''
&lt;/div&gt;

Birkstedt et al. conduct a systematic literature review (SLR) of the emerging yet fragmented field of “AI governance” (AIG), defined as “a system of rules, practices, processes, and technological tools” that ensure organizational AI meets strategic, legal, and ethical requirements. The authors use human-centric and sociotechnical AI traditions to explore how organization-level governance mechanisms can bridge the principles-to-practices gap in AI ethics. Through SLR, authors identify four research agendas. The “technical agenda” focuses on the practicalities of AIG. The “stakeholder and contextual agenda” ensures AI meets requirements via direct collaboration with external stakeholders, increased corporate social responsibility, and establishment of an “intelligent discourse regime.” The “regulatory agenda” aligns AIG with ethical and legal standards, while the technical, stakeholder and contextual, and regulatory agendas largely focus on the aims of organizational AIG (i.e., what), and the process agenda deals with the means to achieve the aims (i.e., how). The authors develop a generic framework to guide cohesive AIG practices and advocate for a collaborative governance approach that emphasizes transparency, stakeholder engagement, and sociopolitical awareness. 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Broekhuizen, Thijs, Henri Dekker, Pedro De Faria, Sebastian Firk, Dinh Khoi Nguyen, and Wolfgang Sofka. 2023. “AI for Managing Open Innovation: Opportunities, Challenges, and a Research Agenda.” ''Journal of Business Research'' 167 (November 2023): 114196. https://doi.org/10.1016/j.jbusres.2023.114196. '''
&lt;/div&gt;

Broekhuizen et al. systematically analyze how AI could be applied to the complex, unstructured task of “open innovation,” a possible business opportunity they believe has been insufficiently explored. They define “Open innovation” as “the practice of leveraging external ideas, resources, and capabilities to improve innovation outcomes,” and propose AI could minimize its inherent managerial challenges. To prove this, the authors form a framework that considers the three abilities involved in AI’s agreed possible applications to management (involving “mapping,” “coordinating,” and “controlling”) and assess how applicable their constituent functions are to the challenges of the three stages of open innovation (involving “initiation,” “development,” and “realization”). In the stage of “initiation,” they propose AI could scout for distant knowledge partners, detect relevant information gaps and opportunities, and forecast conflicts. During the “development” stage, AI could develop complementarity between partners' knowledge stocks, integrate knowledge whilst safeguarding intellectual property, and monitor partners for violations or conflicts within the relationship. Finally, during the “realization” stage the authors argue AI could comprehensively evaluate business opportunities, optimize resource deployment, and diagnose or remedy intellectual property violations. To Broekhuizen et al., this study “underscores the significance of the human-side of AI” by demonstrating AI’s valuable role in assisting management. They also conclude that AI’s ability to search for corporate partners will be its greatest impact in open innovation, as they argue it will both incentivize openness and reputability of companies and increase the need for them to keep sensitive data secure.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Cheong, Inyoung. 2024. “Collaborative Approaches to AI Governance: Exploring Co-Design and Co-Regulation Models.” PhD diss., University of Washington. https://homes.cs.washington.edu/~yoshi/papers/theses/inyoung-cheong-dissertation.pdf&lt;nowiki/&gt;.'''
&lt;/div&gt;

This dissertation seeks to integrate co-design and co-regulation as a means of facilitating domain-specific expert knowledge into AI governance policies. It uses theoretical analysis and empirical data as part of its methodologies, and it should be of interest to anyone who wants detailed case studies of the use of AI technology in specific domains, as well as clear models for (co-)governance and development in the use of Artificial Intelligence. Cheong performs two case studies, examining the development and use of an AI application to provide legal advice as well as the application of AI in online content moderation of news and comics apps in South Korea. These result in a set of strategies for AI co-regulation that includes parameters for starting conditions, institutional design, collaborative process, and facilitative leadership. Cheong proposes that the guiding principles for AI co-governance must account for specific and distinct contexts, maintain human involvement and intervention in what is often seen as an artificial and automated process, and look to resolve legal ambiguities surrounding AI, especially as there is a clear history of courts dismissing what Cheong calls “collective rule-making” by the community. The author argues for the implementation of co-regulation and co-design, and maintains that “by fostering inclusive dialogues, leveraging diverse expertise, and remaining adaptable to changing technological and societal landscapes” these methods show potential for dealing with AI’s greatest challenges.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Floridi, Luciano. 2018. “Soft Ethics and the Governance of the Digital.” ''Philosophy &amp; Technology'' 31 (1): 1–8. https://doi.org/10.1007/s13347-018-0303-9&lt;nowiki/&gt;.'''
&lt;/div&gt;

Floridi argues our “mature information societies” means “we no longer live online or offline, but onlife,” making the sociopolitical challenge of ethically governing this foundational “digital age” even more vital than pursuit of future digital innovations. Floridi defines three overlapping subfields within the “Governance of the Digital,” including “Digital Ethics,” “Digital Regulation,” and the encompassing “Digital Governance.” The latter is defined as “the practice of establishing and implementing policies, procedures, and standards for the proper development, use and management of the infosphere,” therefore “sometimes neither moral nor immoral… legal nor illegal.” This demonstrates that the three subfields don’t always overlap, but each must always be considered by policy-makers, because what is legal, what is good, and what is best are all key components of the ideal “Governance of the Digital.” “Digital Ethics” should also be further subdivided into “hard” ethics, involving binary moral judgments about what should versus should not be done, and “soft” ethics, which involves a “post-compliance,” “post-feasibility” approach, ensures moral opportunities are maximized, and fosters “good corporate citizenship.” Differing “information societies” occupy differing levels of maturity, producing distinct ethical contexts which should progress with differing ethical focuses. In this regard, Floridi advocates “ethics foresight analysis,” which uses data analytics to assess ethical impacts of future innovations then targets research by systematically identifying what is feasible, then sustainable, then acceptable, then preferable. The author concludes that Digital Ethics must be “leading” not “chasing” developments, and not just functioning as a questioning exercise, but also signalling that ethical issues matter, engaging with stakeholders, and providing shareable solutions.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Gasser, Urs, and Virgilio A. F. Almeida. 2017. “A Layered Model for AI Governance.” ''IEEE Internet Computing'' 21 (6): 58–62. https://doi.org/10.1109/MIC.2017.4180835&lt;nowiki/&gt;.'''
&lt;/div&gt;

This article identifies the gap in knowledge created by the “black box” of AI—the obscured nature of the processes that take place from an initial prompt to its generated output. Gasser et al. note that users and policy-makers of these technologies have relatively little insight into how it actually works compared to its developers. Given this unique issue, Gasser et al. propose a theoretical framework for how to approach AI governance, drawing upon the advent and subsequent globalization of the Internet to inform their understanding of AI technology and its pattern of growth. The article addresses a core issue that strong or general AI is often discussed in terms of potential societal impact while weak or general AI is currently being deployed right now (i.e., 2017) and is in real need of governance already. The authors identify core themes related to “transparency, accountability, and explainability; inclusion and fairness; [and] global governance,” as well as three challenges for AI governance—&quot;information asymmetries”; “finding normative consensus”; and “government mismatches”. The authors point out that the ethical and legal considerations of AI are closely related and take a modularity approach; they present three layers for governance that exist from AI systems to society, with timing (i.e., near-, mid-, and long-term) and considerations for each layer. The article concludes by proposing AI governance requires a blended approach based on the different risks of certain AI applications and propose that both “market-oriented solutions” and &quot;government-based structures” can work on a national or international level, suggesting a “global oversight body” could act as “the curator of global principles and emerging norms for AI systems.”

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Kirschenbaum, Matthew. 2025. “The US of AI.” Public Draft, February 25, 2025. https://drive.google.com/file/d/1O2qkjhg7Ei5zZWmBraNwXq4V0lTauspN/view&lt;nowiki/&gt;.'''
&lt;/div&gt;

This set of notes from Kirschenbaum represents his “near real-time attempt to come to terms with… the opening weeks of the second Trump Administration,” especially the “AI-first” strategy of “the so-called Department of Government Efficiency (DOGE).” Kirschenbaum outlines DOGE has nothing to do with government efficiency, as it only saves insignificant costs, instead possessing ideological and capitalistic motivations to form “a government without people.” Based on Musk’s nebulous authority—as an advisor from the private sector—DOGE targeted nineteen federal agencies to be “strip-mined and fracked for all manner of information” as a “priceless and unprecedented resource” of AI training data. To do so, DOGE operatives accessed sensitive spaces after hours, combining physical aggression with a “complete lack” of technical inhibition representing a “vampiric data suck.” Kirschenbaum identifies clear corporate interests here and further examines ideological aims. Early executive orders asserted the need for federal AI systems “free from ideological bias or engineered social agendas,” with OpenAI announcing “ChatGPT Gov” days later. These invocations of “AI” as a universal solution represent only a “linguistic token” instead of any realized technology—as worded by Salvaggio, AI must only “be considered a plausible competitor to human decision-making long enough to dislodge the existing human decision-makers.” Kirschenbaum frames this as based in the “masculine maximalism” of the Trump administration, as the term AI promotes “technological absolutism” whilst theoretically playing into the Nixon-era “theory of the unitary executive” by aiming to replace people with “void” and consolidate power into the hands of “a super-user class who will operate outside the system.” However, “the real world intrudes… with lethal downstream effects.” Kirschenbaum proposes “a collapsing superimposition of political discourse, the actual operations of social media as its primary public arena, and the technical architecture of the systems (in the form of AI)… in the sphere of governance as well as media,” which produces the “infrastructure for… permanent despotism” via the “untethering of language from conditions of lived reality.”

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Oh, Dayei, and John Downey. 2024. “Does Algorithmic Content Moderation Promote Democratic Discourse? Radical Democratic Critique of Toxic Language AI.” ''Information, Communication &amp; Society'' 28 (7): 1157–76. https://doi.org/10.1080/1369118X.2024.2346531.'''
&lt;/div&gt;

Oh and Downey critically examine how algorithmic content moderation shapes public discourse, focusing specifically on Google’s Perspective API and its detection of &quot;toxic&quot; language. By drawing a crucial distinction between incivility (harsh or emotional tone) and intolerance (actual discriminatory harm), the authors demonstrate how AI-driven moderation systems frequently misinterpret context. Consequently, these algorithms often suppress emotionally charged but politically significant speech—particularly from marginalized groups—while allowing structurally discriminatory but politely phrased content to evade detection. This dynamic reveals a significant flaw in relying on AI as a neutral mediator of digital dialogue: by prioritizing tone over substance, algorithmic moderation actively curtails democratic participation and skews the visibility of diverse perspectives. Their study is relevant for understanding how AI systems act as invisible gatekeepers, enforcing normative boundaries on public expression and highlighting the urgent need for moderation frameworks that are contextually aware, transparent, and equitable rather than merely tone-policing.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Rughiniș, Cosima, et al. 2025. “AI at the Knowledge Gates: Institutional Policies and Hybrid Configurations in Universities and Publishers.” ''Frontiers in Computer Science'' 7: 1608276. https://doi.org/10.3389/fcomp.2025.1608276. '''
&lt;/div&gt;

This article constitutes a qualitative analysis (i.e., a form of computational analysis) of 16 universities and 12 publishers that attempts to understand how these institutions regulate AI in knowledge production. Rughinis et al. claim that most institutions preserve their values while regulating AI by adapting the regulations they already have in place, stating “institutional policies are shaped by value-based compromises and not by technical concerns alone.” At the same time, although the article acknowledges its focus on institutional regulation, it also admits that “AI adoption can evolve both through policy frameworks and… locally embedded practices that remain partly invisible in formal documentation.” The authors propose two concepts, “dual black-boxing” and “legitimacy-dependent hybrid actors.” Dual black-boxing refers to the lack of transparency in both the “hidden algorithmic processes [and] invisible training data” that shape AI systems and “the opacity surrounding how academics employ AI in their work,” while legitimacy-dependent hybrid actors are “configurations of human-AI collaboration whose institutional legitimacy is not intrinsic but conditional.” Rughinis et al. argue that transparency is a core academic value, and scholars must work to open these black boxes; they also suggest that that transparency is more closely linked to academic legitimacy in AI-related issues rather than the more traditional issue of the origin of ideas. The majority of the article applies these terms to understanding the regulatory frameworks of universities and publishers, and concludes with the understanding that the majority of institutions allow some form of AI use within certain parameters. The key types of hybrid actors allowed by universities were AI-assisted researchers, AI-enabled translators, AI-enhanced writers, and AI-supported coders, while publishers facilitated the use of AI to refine language, support research methodologies, and aid in research. Ultimately, the authors observe that institutions are permitting AI-supported work in refined roles and argue that AI-based academic work gains legitimacy through transparency.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Seger, et al. “Democratising AI: Multiple Meanings, Goals, and Methods.” ''Proceedings of the 2023 AAAI/ACM Conference on AI, Ethics, and Society''. https://dl.acm.org/doi/10.1145/3600211.3604693&lt;nowiki/&gt;.'''
&lt;/div&gt;

Aiming to “provide a foundation for more productive conversations,” Seger et al. categorize four forms of “AI democratisation” and explore each form’s goals and facilitation pathways. Democratization of AI “use” involves making it easier for people to employ AI’s capabilities, and is therefore equally comparable to increasing availability of printers or of tools which can create chemical weaponry, depending on the case. Democratization of “development” involves allowing a wider range of people to contribute to the AI design and development process, which accelerates progress and increases diversity, but also opens the door for maliciousness and irresponsibility. Democratizing “profits” constitutes a philanthropic or redistributive process, and has the predictably involved weaknesses. Therefore, the authors highlight that “AI democratisation is a multifarious and sometimes conflicting concept” which “should not be conflated with improving AI accessibility” and “is not inherently good.” This is because democratization of AI’s “use,” “development,” and “profits” only derives value from its alignment with the interests and values of impacted groups, making democratization of AI’s “governance” the priority. Democratization of “governance” does not necessarily aim for total agreement amongst constituents, but will regardless reduce the unilaterality of decision-making by promoting justice, legitimacy, and diversity.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Sposato, Martin. 2025. ”Artificial Intelligence in Educational Leadership: A Comprehensive Taxonomy and Future Directions.” ''International Journal of Educational Technology in Higher Education'' 22 (20). https://doi.org/10.1186/s41239-025-00517-1. '''
&lt;/div&gt;

This article performs an analysis and review of published works on AI in educational leadership from 2017–2024 and uses the results of that process to develop what Sposato describes as “a comprehensive taxonomy of AI applications in educational leadership.” Potential readers include researchers and policy-makers interested in communicating across specific fields and disciplines. Sposato theorizes ten application domains for AI in higher education ranging from increased efficiency in administration and teaching practices to increased community engagement and strategic planning. The purpose of such a framework is to provide educational leaders with a coherent vocabulary of “the full spectrum of educational leadership responsibilities” that can facilitate further conversation. The author advocates for AI’s transformative potential in higher education even as they note important challenges (especially with ethics and equity), arguing a need for a balanced approach and “robust ethical guidelines and regulatory frameworks.” The framework provided is presented as one step toward developing AI literacy for stakeholders so that all involved in education might make more informed decisions and articulate their needs more clearly.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Ter-Minassian, Lucile. 2025. ”Democratizing AI Governance: Balancing Expertise and Public Participation.” Preprint, ''arXiv'', January 16. https://doi.org/10.48550/arXiv.2502.08651&lt;nowiki/&gt;.'''
&lt;/div&gt;

Ter-Minassian argues that “universal access, technically-constrained development, and universal impact” of AI and AI research necessitate public participation in AI governance even as it “creates a unique governance challenge.” The article presents the benefits and challenges of expert oversight and public consultation. Ter-Minassian outlines the threat of misinformation to meaningful public participation, highlighting how both undue fear and unrealistic optimism surrounding AI can affect public discourse, while acknowledging that the rapid rate of AI research makes it difficult to incorporate truly democratic processes into the decision-making process. The author concludes that any ongoing inclusive and effective AI governance ought to incorporate inclusive representation, balance expertise and public engagement, embrace transparency and accountability while engaging an iterative process, and implement a hybrid framework that “blend[s] expert knowledge with meaningful public input” (4). She argues that “AI’s deep societal impact calls for public engagement” and “technical complexity does not have to exclude meaningful public input,” advocating for “structured deliberation and phased public participation” to address “time-sensitive AI challenges without compromising democratic legitimacy” (5). Ultimately, the article sees this as an iterative process that will need to continue to adapt in order to maintain expert insight and public discourse on AI.

== Critical Literacies ==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Aguiar, Micaela, and Sílvia Araújo. 2024. “Final Thoughts: Digital Humanities Looking at Generative AI.” ''In Digital Humanities Looking at the World'', edited by S. Araújo et al., 367–380. Cham: Springer Nature Switzerland.'''
&lt;/div&gt;

Aguiar and Araújo explore the emergence and applications of generative artificial intelligence within Digital Humanities research. They trace the evolution of generative AI from early implementations like the 1960s Eliza chatbot through its developments such as Generative Adversarial Networks (GANs) and the Transformer architecture to contemporary large language models like BERT and GPT. The authors document current applications of generative AI across Digital Humanities domains, including cultural heritage preservation, historical text processing, and literary creation. They outline how these technologies are being used to memorialize mass atrocities, process traditional Chinese ancient texts, and explore collaborative human-AI poetry creation. Aguiar and Araújo examine the inner workings of generative AI, particularly focusing on how conversational models function through statistical prediction rather than genuine comprehension. They identify limitations such as hallucinations, bias replication, and attribution problems that researchers must consider when using these tools. The chapter concludes that effective integration of generative AI in Digital Humanities requires developing AI literacy skills that enable researchers to critically evaluate outputs while leveraging the technology's capabilities for sustainable research advancement.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Boer, Victor de, and Lise Stork. 2024. “Hybrid Intelligence for Digital Humanities.” Preprint, ''arXiv'', April 15. https://doi.org/10.48550/ARXIV.2406.15374. '''
&lt;/div&gt;

De Boer and Stork believe the discipline of Digital Humanities (DH) should meet the challenges and opportunities posed by Artificial Intelligence (AI) by adopting the “human-centric paradigm” of Hybrid Intelligence (HI). They define DH as “a scholarly realm where computing or digital technologies intersect with… the humanities… characterized by innovative approaches to scholarly endeavors,” and identify various existing DH approaches to AI, which include “Knowledge Representation,” “Machine Learning,” “Natural Language Processing,” and “Computer Vision.” De Boer and Stork argue successfully integrating AI tools into DH requires embedding AI in scholarly practice, adopting a diverse and polyvocal approach, considering the debate of distant versus close reading, and applying a critical stance toward data, methods, and tools. HI “concerns itself with the investigation and design of human-AI ecosystems,” and the authors argue effective AI should be developed by following its “CARE” principles—being “Collaborative, Adaptive, Responsible, and Explainable.” Therefore, De Boer and Stork focus this text on mapping CARE principles to those DH requirements earlier outlined. Overall, they concur with Goodlad and Baker that humanists “are ideal 'domain experts' for the current juncture,” and end by identifying two overarching challenges. The first challenge is “one-shot solutions,” including tools, datasets, and methods that aren’t reusable, Open Source, accessible, and well described. Secondly, they identify the human factor—actors will need both an open mind and AI literacy to be equally critical of and cooperative with AI. Therefore, the authors emphasize the importance of teaching digital methods within the humanities curricula.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Carmi, Elinor, Simeon J. Yates, Eleanor Lockley, and Alicja Pawluczuk. 2020. “Data Citizenship: Rethinking Data Literacy in the Age of Disinformation, Misinformation, and Malinformation.” ''Internet Policy Review'' 9 (2). https://doi.org/10.14763/2020.2.1481.'''
&lt;/div&gt;

This study argues that dominant understandings of digital and data literacy are insufficient for addressing contemporary complex challenges of disinformation, misinformation, and malinformation. They propose the concept of data citizenship to reframe literacy as a fundamentally civic, political, and collective practice rather than a set of individual technical skills. The authors contend that information disorders cannot be addressed through technological solutions alone, as they are deeply embedded in structural inequalities, platform economies, and power asymmetries shaping datafied societies. The article builds on a literature review and secondary data analysis drawing on Me and My Big Data project, alongside the development of a nationally representative UK survey. The authors identify three major gaps in existing literacy frameworks: an overemphasis on individual competence rather than networked practices, a lack of critical engagement with algorithmic and economic infrastructures of platforms, and the absence of proactive civic skills such as contesting data extraction, demanding transparency, and advocating for data justice. Their analysis highlights how citizens’ data practices are shaped by social networks, education, and socio-economic conditions, revealing unequal capacities for verification, protection, and collective action. The authors conclude that data literacy must move beyond content verification to include critical understanding of platform design, funding models, and algorithmic governance. They emphasize the importance of locally grounded, participatory approaches to data literacy education that reflect diverse lived contexts rather than scalable, top-down interventions. While the study offers a robust conceptual model and survey-based insights, it does not yet include in-depth qualitative engagement with citizen groups, which the authors position as a necessary next phase of research. Overall, the article makes a significant contribution by bridging digital literacy and the field of mis/dis/mal information research and claims that data literacy is an essential component of democratic citizenship.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Long, Duri, and Brian Magerko. 2020. “What is AI Literacy? Competencies and Design Considerations.” In ''Proceedings of the 2020 CHI Conference on Human Factors in Computing Systems'', 1–13. New York, NY: Association for Computing Machinery. https://doi.org/10.1145/3313831.3376727.'''
&lt;/div&gt;

The authors present an exploratory review of interdisciplinary literature, aiming to organize key ideas on AI literacy definitions and essential competencies. Authors claim that public misunderstandings of AI are due to design, educational gaps, black-box algorithms, and a general lack of technological knowledge. The review includes two sections: how the public understands specific AI systems, and how existing research addresses people’s broader understanding of AI. Rather than offering an exhaustive synthesis, Long and Magerko’s focus is on non-technical audiences and they offer central provocations and design principles that can inform educational interventions. The proposed conceptual framework on AI literacy identifies 17 core competencies alongside 14 design considerations for educational intervention, which are described and supported by relevant literature. Together, these considerations position the framework as a practical and reflective tool for designing AI literacy interventions that move beyond dominant media narratives and foster critical, informed engagement with AI technologies.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Majdik, Zoltan P., and S. Scott Graham. 2024. “Rhetoric of/with AI: An Introduction.” ''Rhetoric Society Quarterly'' 54 (3): 222–31. https://doi.org/10.1080/02773945.2024.2343264. '''
&lt;/div&gt;

Majdik and Graham propose a field-organizing distinction that functions as a methodological argument. By splitting inquiry into “rhetoric of AI” (AI as object) and “rhetoric with AI” (AI as method), they treat AI simultaneously as a rhetorical actor/ecosystem component that structures attention, circulation, and uptake, and as an instrument that can be enrolled into rhetorical research workflows. The authors claim that much prior rhetorical work engaged “spaces of AI”—platforms, devices, and algorithmically mediated environments—while leaving “AI” itself undertheorized as the central object; this provides a justification for why rhetoricians should now foreground model/algorithmic operations (and their harms) rather than treating them as neutral background conditions of digital rhetoric. They also frame generative text systems as a stress test for core rhetorical concepts—agency, authorship, and audience—because these systems destabilize the presumed linkage between human intention and textual production, and because they insert nonhuman intermediaries into communicative situations that education and public discourse still normatively treat as human-to-human. The introduction then uses this distinction to stage the special issue’s contributions as complementary routes for rebuilding rhetorical theory and pedagogy under AI conditions.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Ng, Davy Tsz Kit, Jac Ka Lok Leung, Samuel Kai Wah Chu, and Maggie Shen Qiao. 2021. “Conceptualizing AI Literacy: An Exploratory Review.” ''Computers and Education: Artificial Intelligence'' 2: 100041. https://doi.org/10.1016/j.caeai.2021.100041. '''
&lt;/div&gt;

This article presents an exploratory review of literature published between 2016 and 2021 with the goal of conceptualizing AI literacy and proposing a comprehensive framework for teaching and evaluating it. The authors analyze 30 articles and synthesize existing definitions and approaches to AI literacy, noting that while AI literacy has increasingly been discussed, the concept has often been treated narrowly as a technical skill set. The authors situate AI literacy as a necessary competency for everyone, arguing that AI will increasingly affect many aspects of daily life and employment. In response, the authors argue for a broader understanding of AI literacy that incorporates cognitive and ethical dimensions. The proposed framework organizes AI literacy into four interconnected facets: knowing and understanding AI, using and applying AI, evaluating and creating AI, and AI ethics. Importantly, the authors explicitly reject purely instrumentalist views of AI literacy. To conceptualize AI literacy pedagogically, the authors draw on Bloom’s classic taxonomy, aligning the above-mentioned aspect with increasing cognitive levels. They claim that while most people are aware that AI exists, they often lack understanding of how it works or how to assess its ethical and social implications. This approach positions AI literacy as a developmental learning process rather than a static set of skills. The article concludes by identifying directions for future research, including the need for empirical studies to validate AI literacy frameworks and to better understand how AI literacy can be taught, learned, and assessed across educational contexts.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Rapanta, Chrysi, Anna Åkerfeldt, Mark Vanderbeeken, Diane Lison, Khadija Mohammed, Amanda Gibbs, Helder Coelho, Pinar Seda Celik, Carola Bruna, Ingrid Helleve, Chrysoula Vassilakopoulou, Pieter Swart, Ana Lúcia Marques, and Dirk Ifenthaler. 2025. “Critical GenAI Literacy: Postdigital Configurations.” ''Postdigital Science and Education'' 17 (1): 167–199. https://doi.org/10.1007/s42438-025-00573-w.'''
&lt;/div&gt;

Rapanta et al. develop a comprehensive and pluralistic account of what critical literacy means in the context of generative artificial intelligence. Drawing on contributions from fourteen scholars, the article argues that GenAI literacy cannot be captured through a single, universal framework. Instead, it must be understood as a set of context-dependent literacies shaped by disciplinary traditions, socio-political conditions, and evolving human–algorithm relations. This postdigital perspective challenges narrow definitions of AI literacy that prioritize technical skills. The authors’ central claim is that current GenAI systems, particularly large language models, require critical engagement because of their epistemic limitations, including reliance on dominant narratives, lack of explainability, tendencies toward fabrication, and reinforcement of Western and anglophone knowledge structures. As a result, critical GenAI literacy is positioned as a social justice concern rather than a neutral competency. Learners and educators are encouraged to examine questions of authorship, agency, and power, such as whose labour and data underpin these systems and which perspectives are marginalized or erased. Methodologically, the article adopts a dialogic and collective approach to resist homogenizing AI epistemologies and to foreground plurality in postdigital research. The authors conceptualize GenAI as part of a co-constructive assemblage in which human and non-human agencies interact, while maintaining that ethical responsibility and evaluative judgment must remain human-led, organizing four interrelated dimensions: epistemology and ontology, agency, engagement, and ethics and justice; each emphasizing critical interrogation, active participation, and accountability. Overall, the paper provides a theoretically grounded yet pragmatic foundation for advancing critical GenAI literacy in education and research.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Veldhuis, Annemiek M., Phoebe W. K. Lo, Iain E. G. Kenny, and Alissa N. Antle. 2024. “Critical Artificial Intelligence literacy: A scoping review and framework synthesis.” ''International Journal of Child-Computer Interaction'' 43: 100708. https://doi.org/10.1016/j.ijcci.2024.100708&lt;nowiki/&gt;.'''
&lt;/div&gt;

Veldhuis and colleagues present a review of literature and framework synthesis that conceptualizes critical AI literacy from a child–computer interaction (CCI) perspective. Reviewing 30 empirical studies published over the past decade, the authors aim to understand how children and youth aged 5–18 have been supported in developing critical literacy on AI technologies, particularly regarding their social, political, cultural, and ethical implications. Grounded in critical literacy theory, the authors integrate Lewison et al.’s (2002) four interrelated dimensions including disrupting the commonplace, considering multiple viewpoints, focusing on the sociopolitical, and taking action into a four-part framework for critical AI literacy. Importantly, the framework rejects deficit narratives by foregrounding children’s capacity for critical inquiry and demonstrates that even young learners can meaningfully engage with complex issues such as algorithmic bias, data provenance, privacy, accountability, and the distinction between AI-generated outputs and human creativity when supported by pedagogies such as critical making. Only peer-reviewed, English-language empirical studies with explicit support for children’s critical engagement with AI were included. The findings reveal a growing body of research, particularly in the past three years, exploring activities that promote youths’ critical reflection on AI’s societal and ethical impacts. These activities address concerns related to privacy, surveillance, employment, diversity in the computing workforce, algorithmic bias, and accountability. The resulting framework emphasizes learners’ capacity to analyze both AI artifacts and the sociotechnical systems that produce them, as well as to reflect on how AI shapes cultural, societal, and political structures and personal experiences. For future research recommendations, the authors emphasize the urgency of ongoing critical AI literacy practices in areas of youth emotional awareness and socio-cultural impacts in response to the fast evolution of generative AI systems. 

== Globalism, Colonialism, and Influence ==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Arora, Payal. 2024. “Creative data justice: a decolonial and indigenous framework to assess creativity and artificial intelligence.” ''Information, Communication &amp; Society'' 28 (13): 2231–47. https://doi.org/10.1080/1369118x.2024.2420041&lt;nowiki/&gt;.'''
&lt;/div&gt;

Arora (2024) develops a framework of creative data justice that includes decolonial theory, Indigenous perspectives, and critical studies of creativity to explore how generative AI could impact creative labour, rights, and cultural value. The author argues that democratizing creativity requires a cross-cultural framework that considers power relations between creative work, data, and learning, particularly by centring the lived realities of underrepresented communities in the Global South. Rather than treating AI creativity as neutral, the paper claims that inclusive AI systems must address contextual inequalities and the unequal impacts of AI on diverse creative communities. Arora critiques dominant Western-centred scholarship and challenges concepts such as the “creative class,” arguing that creativity exists across everyday social and cultural practices. The paper also critiques Creative Commons (CC) frameworks, suggesting that while they promote openness, they may enable commercial data extraction by AI companies. Instead, the author argues for dataset curation developed with Indigenous artists and activist groups to ensure equitable representation. The article further highlights the often-invisible labour behind creative AI located in the Global South and argues that a decolonial approach must recognize both material infrastructures and power relations shaping creative work. Indigenous approaches to communal ownership and systems of care are presented as alternatives to Western individualistic models of creative rights. The author advocates combining ethnographic “thick data” with computational approaches and suggests action-research methods such as counter-mapping, dataset debiasing, and critical media literacies. The paper concludes that creative data justice offers a framework for building culturally diverse and equitable AI systems that respect community agency and support a more democratic global data economy.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Fırıncı, Yusuf. 2024. “Decolonial Artificial Intelligence; Algorithmic Fairness in Alignment with Turkish and Islamic Values.” ''Marmara Üniversitesi İlahiyat Fakültesi Dergisi'' 67 (67): 250–279. https://doi.org/10.15370/maruifd.1565884&lt;nowiki/&gt;.'''
&lt;/div&gt;

Fırıncı argues that artificial intelligence development should be guided by explicitly value-based frameworks grounded in Turkish-Islamic ethical traditions rather than relying solely on dominant Western models of technological governance. The authors emphasize that AI systems rely on human judgment and are inherently value-laden, making ethical alignment essential to prevent manipulation, misinformation, algorithmic bias, and forms of digital coloniality. Drawing on concepts such as big data, “thick data,” and digital anthropology, the paper suggests combining quantitative data analysis with culturally grounded social knowledge to design algorithms that reflect community values. The paper examines tensions between Western liberal individualism (which underpins most AI fairness metrics) and Islamic ethical frameworks that emphasize communal welfare, divine justice, and context-dependent moral reasoning. This analysis reveals that &quot;fairness&quot; is not a universal technical specification, but a deeply value-laden concept shaped by particular cultural, religious, and philosophical commitments—meaning that AI systems designed around Western fairness assumptions may be experienced as unjust in contexts operating from different ethical frameworks. Using Social Construction of Technology theory and critical social constructivism, the authors argue that existing global AI frameworks often reproduce hierarchy, bias, and external control, which they interpret as forms of algorithmic oppression. In response, they advocate a “fairness in alignment with values” approach grounded in Turkish-Islamic worldviews, supported by Islamic ethical principles as foundations for responsible technological development. The paper concludes by calling for locally controlled data infrastructures, culturally aligned AI systems, and knowledge production rooted in Turkish and Islamic values as part of a broader decolonial technological model aimed at protecting communities from AI-related harms and preserving social cohesion.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Mohamed, Shakir, Marie-Therese Png, and William Isaac. 2020. “Decolonial AI: Decolonial Theory as Sociotechnical Foresight in Artificial Intelligence.” ''Philosophy &amp; Technology'' 33 (4): 659–84. https://doi.org/10.1007/s13347-020-00405-8. '''
&lt;/div&gt;

Mohamed et al. explore the role of post-colonial and decolonial critical science in understanding the transformative technological advance of AI. They argue risks to vulnerable peoples can be minimized by linking ethical principles to scientific progress, and therefore consider AI’s embedded values, approaching it a&quot;s both object and subject.&quot; They demonstrate that AI advances &quot;encompass ever-larger aspects of the cultural, economic and political life of modern society&quot; by citing Obermeyer et al.’s reveal of racial biases within an algorithm commonly used by healthcare, arguing this indicates how AI obscures and exacerbates asymmetrical power relations. Mohamed et al. identify neglect to address systemic racism as the cause, illustrating that patterns of power between colonizer and colonized survived territorial decolonization to propagate a historically continuous &quot;coloniality of power.&quot; Therefore, &quot;dynamic and robust foresight tactics and methodologies grounded in the critical sciences&quot; (like, for example, a &quot;lens of metropole and periphery&quot;) should be applied to the field of AI to ensure one’s view is &quot;decentring,&quot; &quot;additive-inclusive,&quot; and prioritizes &quot;engagement.&quot; The authors further explore emergent theories of data colonialism within their assessment of &quot;algorithmic coloniality.&quot; This involves their taxonomy of &quot;decolonial foresight&quot; (constituting algorithmic &quot;oppression,&quot; &quot;exploitation,&quot; and &quot;dispossession&quot;), and an exploration of various &quot;sites of coloniality&quot; (including &quot;algorithmic decision systems,&quot; &quot;ghost workers,&quot; &quot;beta-testing,&quot; &quot;national policies,&quot; and &quot;international social development&quot;). They argue this study highlights the disjunction of empirical observations with the current, theoretical, and ahistorical frameworks of power in AI. This leads the authors to outline a set of tactics to develop &quot;decolonial AI&quot; possessing a strengthened empirical basis and an avoidance of algorithmic colonialism. Such tactics are &quot;based on lessons of resistance and recovery from historical and decolonial criticism and grounded within already existing work&quot;; they include critical technical practice, seeking reverse tutelage and pedagogies, and renewing affective political communities. Mohamed et al. emphasize that those ethical principles which form the &quot;social contract&quot; must consider diverse viewpoints, and that new methodologies must be developed to promote &quot;inclusive dialogue&quot; within new research cultures.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Muldoon, James, and Boxi A. Wu. 2023. “Artificial Intelligence in the Colonial Matrix of Power.” ''Philosophy &amp; Technology'' 36 (4). https://doi.org/10.1007/s13347-023-00687-8&lt;nowiki/&gt;.'''
&lt;/div&gt;

Muldoon and Wu (2023) extend decolonial AI scholarship by situating contemporary artificial intelligence within what Aníbal Quijano terms the “colonial matrix of power,” and arguing that from data to production machine learning systems are structured to endure colonial logics that organize economic extraction, labour hierarchies, and epistemic dominance. Central to their framework is the “colonial matrix of power,” which names an organizing principle of domination across interrelated domains: economic control (labour and resources), authority, gender and sexuality, and the control of subjectivity and knowledge. Authors focus particularly on economic extraction and epistemic domination, drawing on the modernity/coloniality research program. They proceed with three interconnected claims: “colonial supply chain of AI,”  “international division of digital labour,” and “hegemonic knowledge production,” demonstrating how AI development relies on largely invisible labour and mineral resources of majority-world communities to generate wealth for Western economies. Beyond material extraction, the authors contend that AI reproduces hegemonic Western epistemologies by presenting its systems as universal, objective, and rational, thereby marginalizing non-Western knowledge systems. This study challenges dominant narratives that present AI as environmentally sustainable or socially progressive, arguing that from mineral extraction to energy-intensive computation, the ecological and material burdens fall disproportionately on majority-world nations, while the economic and technological benefits accrue to wealthy Western nations. They conclude by emphasizing that coloniality is not merely an object of study but a framework for unsettling Western-centric modes of knowing.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Salami, Aishat Oyenike. 2024. “Artificial intelligence, digital colonialism, and the implications for Africa's future development.” ''Data &amp; Policy'' 6. https://doi.org/10.1017/dap.2024.75. '''
&lt;/div&gt;

Salami (2024) studies how artificial intelligence operates within broader dynamics of digital colonialism in Africa, arguing that AI risks reinforcing patterns of colonialism, unless African actors gain greater agency in digital governance. The article begins by clarifying key concepts like AI, digital colonialism, neocolonialism, and data exploitation. Salami identifies several manifestations of digital colonialism on the continent: foreign ownership of critical digital infrastructure, unequal data flows in which African user data is extracted and monetized abroad, and algorithmic systems that enable forms of economic exploitation. Through examples such as ride-hailing platforms and outsourced digital labour, the article demonstrates how algorithmic control can generate precarious working conditions while concentrating profit outside the continent. Beyond labour concerns, Salami highlights how data extraction contributes to a digital wealth transfer, deepening economic imbalances and undermining local innovation and national sovereignty. While acknowledging the potential benefits of AI for development, the article adopts a cautious stance, emphasizing that Africa’s digital future depends on strengthening regulatory frameworks, expanding infrastructure, investing in education and research, and prioritizing data sovereignty. 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Varshney, Kush R. 2024. “Decolonial AI Alignment: Openness, Visesa-Dharma, and Including Excluded Knowledges.” ''Proceedings of the AAAI/ACM Conference on AI, Ethics, and Society'' 7: 1467-1481. https://doi.org/10.1609/aies.v7i1.3173&lt;nowiki/&gt;.'''
&lt;/div&gt;

Varshney discusses AI alignment through a decolonial lens, arguing that current large language model (LLM) alignment practices reproduce forms of coloniality by embedding Western moral philosophy as universal. The author conceptualizes alignment as the post-training processes used to shape model behaviour and argues that the term often functions as an “empty signifier,” masking whose values are being encoded and enforced. The author contrasts open and closed LLM models, arguing that while openness may allow value to circulate more equitably among developers and communities, closed models concentrate value in extractive ways that reflect colonial dynamics, and views them as contemporary “metropoles” that accumulate power through extractive and epistemic control. Building on existing research on colonial AI, the article adds “ethical essentialism” (or moral absolutism) as a new form of coloniality, arguing that AI systems often treat Western moral frameworks as universal, which marginalizes other ethical traditions and reinforces a coloniality of knowledge. Varshney also identifies three specific aspects of coloniality in AI alignment: closed proprietary delivery of models, reliance on Western ethical theories as default, and technological designs that limit how values can be expressed. As an alternative, Varshney proposes a decolonial approach grounded in openness understood not only technically but epistemically: openness to research artifacts, openness to society, and openness to excluded knowledges. The author suggests that alignment should allow communities to adapt models according to local contexts rather than imposing universal rules. Drawing from Hindu moral philosophy, particularly the concept of viśeṣa-dharma (context-dependent ethics), the paper argues for pluralistic, relational value systems that recognize moral diversity instead of universal moral commands. The conclusion calls for a reconceptualization of AI alignment that moves away from moral absolutism toward context-sensitive, community-driven frameworks, positioning openness as a pathway to dismantling the colonial power structures embedded in contemporary AI systems.

== Diversity, Determinism, Bias, and Justice ==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Al-kfairy, Mousa , Dheya Mustafa, Nir Kshetri, Mazen Insiew, and Omar Alfandi. 2024. “Ethical Challenges and Solutions of Generative AI: An Interdisciplinary Perspective.” ''Informatics'' 11 (3): 58. https://doi.org/10.3390/informatics11030058'''
&lt;/div&gt;

Al-kfairy et al. (2024) provide a comprehensive synthesis of the ethical vulnerabilities introduced by generative AI, utilizing an interdisciplinary review of 37 studies across healthcare, education, and media. Rather than treating ethical breaches as isolated technical flaws, the authors demonstrate how generative models systematically threaten privacy, intellectual property, and social equity across diverse domains. For instance, they highlight the paradox in healthcare where synthetic patient data—often intended to protect privacy—still carries significant risks of re-identification. Similarly, the authors trace how AI's capacity to mimic copyrighted works and generate synthetic media exacerbates both misinformation and algorithmic bias, particularly by perpetuating racial and gender stereotypes in high-stakes environments like hiring and education. Moving beyond mere critique, the article advocates for a proactive, cross-sectoral governance framework. The authors argue that mitigating these risks requires more than algorithmic adjustments; it demands multidisciplinary collaboration, robust institutional integrity policies, and targeted AI literacy programs. Ultimately, Al-kfairy et al. frame the ethical deployment of generative AI as a complex sociotechnical challenge that requires continuous, structured dialogue among technologists, ethicists, and policy-makers to ensure transparency and fairness.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Alvarez, Jose M, Alejandra Bringas Colmenarejo, Alaa Elobaid, Simone Fabbrizzi, Miriam Fahimi, Antonio Ferrara, Siamak Ghodsi, et al. 2024. “Policy Advice and Best Practices on Bias and Fairness in AI.” ''Ethics and Information Technology'' 26 (2). https://doi.org/10.1007/s10676-024-09746-w. '''
&lt;/div&gt;

This article attempts to provide “an up-to-date entry-point to the state-of-the-art of the multidisciplinary research on bias and fairness in AI” before providing its own suggestions for policy and best practices based on the outcomes of the NoBIAS—Artificial Intelligence without Bias—project. The authors describe fairness in AI as the pursuit to design “methods for detecting, mitigating, and controlling biases in AI-supported decision making,” and they outline different ways that bias can find its way into AI applications as part of training data (pre-existing bias), design (technical bias), and organizational processes (emerging bias). The article critiques the reduction of bias evaluation to simple metrics and advocates for serious engagement with the issue. The authors detail the various components of the collaborative NoBIAS project as part of its research goal to understand, mitigate, and account for bias in AI data and systems, especially within an EU legal context. They perform a survey and discuss various fairness metrics and how choosing the proper method is crucial for “optimizing AI models.” They also engage with an argument that, although AI is biased, it is less biased than humans, making the claim that AI usage is often accompanied by a false sense of objectivity. The article also investigates core issues at the heart of AI’s biases, such as the assumption that a “ground truth”—the answer to the problem the AI is being asked to solve—is actually encoded within the data. While the article makes many suggestions for how to curb bias within AI, prominent design decisions include human-centric AI and “Multi-stakeholder participatory design.”

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Gallegos, Isabel O., Ryan A. Rossi, Joe Barrow, Md Mehrab Tanjim, Sungchul Kim, Franck Dernoncourt, Tong Yu, Ruiyi Zhang, and Nesreen K. Ahmed. 2024. “Bias and Fairness in Large Language Models: A Survey.” ''Computational Linguistics'' 50 (3): 1097–1179. https://doi.org/10.1162/coli_a_00524&lt;nowiki/&gt;.'''
&lt;/div&gt;

Gallegos et al. perform an “extensive and comprehensive survey of bias and fairness in NLP” that considers both the evaluation and mitigation of bias, then propose three taxonomies for bias evaluation and mitigation. The survey disambiguates different types of social harms that stem from LLMs with the “aim to enhance understanding of the range of bias issues, their harms, and their relationships to each other.” The authors discuss the issue of defining bias in LLMs and note that “many approaches… assume some implicitly desirable criterion… but do not explicitly acknowledge or state the normative social values that justify their framework.” Instead, Gallegos et al. draw attention to “who is harmed, why the behaviour is harmful, and how the harm reflects and reinforces social principles or hierarchies,” trying to bring context and insight to the understanding and function of bias and bias mitigation in LLMs. The article defines terms at every stage of the life cycle of an LLM, looking at issues of bias and fairness in the development, deployment, and training data, of an LLM, for example. The article concludes with four core recommendations: “Avoid flattening power imbalances”; “Choose objective functions that align with fairness desiderata”; “Balance bias mitigation with output diversity”; and “Preserve important contexts in output rewriting.” The authors also acknowledge problems and challenges, including addressing power imbalances, an issue that we can mitigate by centring marginalized communities, developing participatory research designs, shifting values and assumptions, and expanding language resources. They likewise propose methods for curbing problems with conceptualizing fairness for NLP, refining evaluation principles, and improving mitigation efforts. Ultimately, the authors admit that many of these technical issues are the result of societal issues, and that “technical solutions are incomplete without broader societal action against power hierarchies that diminish and dominate marginalized groups.” In short, technical solutions will only take us so far.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Hertweck, Corinna, Joachim Baumann, Michele Loi, Eleonora Viganò, and Christoph Heitz. 2022. “A Justice-Based Framework for the Analysis of Algorithmic Fairness-Utility Trade-Offs.” Preprint, ''arXiv'', June 6. https://arxiv.org/abs/2206.02891.'''
&lt;/div&gt;

Hertwick et al. propose “a framework for eliciting and implementing moral values relevant to the choice of a fairness goal achievable by prediction-based decision-making.” In a system that assumes binary decision-making processes (e.g., assigning a probability score to whether an individual with pay a loan), the authors use their framework to evaluate the utility of those decisions (and the system that makes them) for different groups of people and the fairness related to that outcome. Citing Wong, the article argues that such prediction-based decision-making systems are value-laden, that this makes them inherently political, and therefore they ought to be transparent and democratized. The authors use 6 value-laden questions to make their evaluations: the first question provides a score of utility for those making the decision; questions 2–5 help “define a morally appropriate fairness criterion and a score that expresses to what degree it is fulfilled”; and the last question asks “how strongly should fairness be pursued if it comes into conflict with the utility of the decision maker?” to judge whether the outcome is an appropriate trade-off.

The authors argue for a utility-based evaluation of fairness, determining the value of decisions based on their outcome, looking at the harm and benefit to given stakeholders. In determining patterns of justice, they define four patterns meant to distribute utility differently—Egalitarianism, Maximin, Prioritarianism, and Sufficientarianism. The article concludes “more work needs to be done to deliver a practical empirical methodology to elicit the relevant value-laden choices from stakeholders,” and with a call to incorporate ethical considerations and evaluations into automated decision-making processes.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Kay, Jackie, Atoosa Kasirzadeh, and Shakir Mohamed. 2024. “Epistemic Injustice in Generative AI.” Preprint, ''arXiv'', August 21. https://doi.org/10.48550/arXiv.2408.11441&lt;nowiki/&gt;.'''
&lt;/div&gt;

Kay, Kasirzadeh, and Mohamed “develop an account of generative algorithmic epistemic injustice by building upon a conventional philosophical understanding of epistemic injustice.” The authors see the former as a subset of the latter, with generative algorithmic epistemic injustice entailing identity-based prejudice that hinders expression for marginalized people while ultimately “impair[ing] knowledge formation capabilities of all individuals” within the ecosystem of GenAI applications. Rather than focusing on decision-making and classification applications, this article seeks to characterize the broader varieties of generative epistemic injustice within GenAI systems. Kay, Kasirzadeh, and Mohamed theorize four configurations of generative epistemic injustice: “amplified injustice,” which constitutes AI’s reproduction and magnification of “socially biased viewpoints from its training data”; “manipulative testimonial injustice,” when users employ AI to “intentionally… fabricate falsehoods, discrediting individuals or marginalized groups”; “hermeneutical ignorance,” where GenAI misrepresents or erases marginalized groups “due to a lack of contextual or cultural understanding”; and “access injustice,” where GenAI facilitates the unequal access to information and/or knowledge. The article concludes with proposals for how to create epistemic justice through GenAI, developing mitigation strategies that combat all four of the sub-configurations the authors theorize. Epistemic justice in GenAI can take the form of interrogating system design, identifying “testimonial injustices,” and, potentially, using AI to unlock cultural knowledge that “help[s] articulate experiences that are otherwise ineffable.” The authors end by proposing that the same processes that embed injustice can be re-engineered to embody justice and “orient our knowledge systems towards equity and fairness for all.”

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Klein, L., &amp; D'Ignazio, C. 2024. “Data feminism for AI.” In ''Proceedings of the 2024 ACM Conference on Fairness, Accountability, and Transparency'', 100–112. https://doi.org/10.1145/3630106.3658543. '''
&lt;/div&gt;

Klein and D'Ignazio (2024) adapt their foundational concept of &quot;data feminism&quot; to address the specific ethical, social, and ecological challenges posed by artificial intelligence. Building on the seven intersectional feminist principles introduced in their 2020 book, the authors reinterpret these guidelines to critique the power imbalances, systemic inequalities, and exploitative labour practices inherent in contemporary AI development. To account for the rapidly expanding footprint of generative AI, they introduce two new principles focused on environmental impact and meaningful consent. Specifically, the authors connect the massive ecological costs of AI to historical patterns of racial capitalism and colonialism, highlighting how these environmental and social harms are disproportionately distributed. Ultimately, Klein and D'Ignazio call for a radical reevaluation of dominant, profit-driven AI practices, offering this expanded feminist framework as a practical tool to mitigate harm, challenge corporate monopolies, and foster a more democratic and equitable technological landscape.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Prescott, Andrew. 2023. “Bias in Big Data, Machine Learning and AI: What Lessons for the Digital Humanities?” ''Digital Humanities Quarterly'' 17 (2). https://www.proquest.com/scholarly-journals/bias-big-data-machine-learning-ai-what-lessons/docview/2842908427/se-2.'''
&lt;/div&gt;

Prescott examines how race and gender bias arise in projects using predictive analytics, big data, and AI, and how algorithmic bias could be considered a major socio-cultural humanity crisis. However “predictive analytics” have been helpful in civic services in the US, in many cases they have led to perpetuating existing inequalities. The role of Digital Humanities in contributing more ethical approaches to AI and reshaping ubiquitous “digital modern” cultures is emphasized. He challenges the myths surrounding data-driven methods and argues that the demand for “explainability” is the key tool in combating algorithmic bias. He also suggests that Digital Humanities are particularly well-positioned to contribute to advancing AI explainability. However, much of AI development takes place in the commercial sector, where companies often refuse to disclose their proprietary algorithms. The article concludes with a ten-principle action plan outlining guidelines for the responsible use of AI as a manifesto for Digital Humanities practitioners.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Shams, Rifat Ara, Didar Zowghi, and Muneera Bano. 2023. “AI and the Quest for Diversity and Inclusion: A Systematic Literature Review.” ''AI and Ethics'' 3 (4): 1427–1453. https://doi.org/10.1007/s43681-023-00362-w. '''
&lt;/div&gt;

Shams, Zowghi, and Bano perform a systematic literature review (SLR) that uses both quantitative and qualitative methods to engage with topics of artificial intelligence and diversity and inclusion. The authors make a distinction between Diversity and Inclusion in AI (D&amp;I in AI) and AI for Diversity and Inclusion (AI for D&amp;I), with the former being research literature focused on improving AI systems with respect to those issues, and the latter as the use of AI to improve diversity and inclusion in other domains. Two primary research questions drive the SLR: What challenges and solutions are found in the literature about D&amp;I in AI and in the literature about the applications of AI for D&amp;I? The survey finds that AI for D&amp;I is an underserved area of research, and those articles that address D&amp;I in AI are more likely to acknowledge challenges than to propose or theorize solutions. Articles that do propose solutions for D&amp;I in AI often lack empirical studies or real-world application to support them. The article concludes by noting that issues of governance are underserved; gender, health, and facial analysis are the topics most discussed (issues of race, language, and religion are discussed less). For next steps, the authors intend to develop a “risk-based framework for practitioners… that would incorporate a risk assessment checklist and context-specific recommendations for tackling the related issues at different stages of the AI development lifecycle.” 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Starke, Christopher, Janine Baleis, Birte Keller, and Frank Marcinkowski. 2022. “Fairness Perceptions of Algorithmic Decision-Making: A Systematic Review of the Empirical Literature.” ''Big Data &amp; Society'' 9 (2): 1–35. https://doi.org/10.1177/20539517221115189&lt;nowiki/&gt;.'''
&lt;/div&gt;

This article provides a comprehensive, systematic literature review on the topic of empirical literature surrounding algorithmic decision-making (ADM). Starke, Baleis, Keller, and Marcinkowski begin by acknowledging that ADM can streamline and improve decisions even as it has the potential to “systematically reinforce racial or gender stereotypes, marginalize minorities, or flat-out denigrate certain members of society.&quot; The authors advocate for a “society-in-the-loop approach,” but propose that this requires a “thorough empirical understanding of when and why citizens perceive ADM to be (un)fair.” The systematic review “synthesizes the results of 58 empirical studies” and “over 33,000 unique observations of citizens’ fairness perceptions of ADM,” and “systemize the literature along four main dimensions of perceived algorithmic fairness.” Despite the size of the review and its unique approach in capturing “perceptions of algorithmic fairness,” the authors also acknowledge the limitations of the study: it only looks at English works and published research, and the initial search strings only looked at titles and subtitles of a given work. They also acknowledge their disciplinary bias as social scientists reading the studies through a social sciences lens (10). The results of the survey suggest that “perceived fairness of ADM systems is highly context-dependent” and it is not only technical design but also the area of application and task in question that affect perceived fairness, and the subjects, domains, and tasks explored in these studies require more diversity, as WEIRD (white, educated, industrialized, rich, democratic) people, and criminal justice and HR tasks make up the majority of empirical research. The authors “call for more research from non-Western contexts, along with more theoretical and methodological groundwork to harmonize concepts and measurements of algorithmic fairness perceptions,” as well as a society-in-the-loop framework.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Tonia Sutherland, Marika Cifor, T. L. Cowan, Jas Rault, and Patricia Garcia. 2023. “The Feminist Data Manifest-NO: An Introduction and Four Reflections.” In ''Debates in the Digital Humanities'', edited by Lauren F. Klein and  Matthew K. Gold. Minneapolis, MN: University of Minnesota Press. https://dhdebates.gc.cuny.edu/read/debates-in-the-digital-humanities-2023/section/16184c7d-eee1-40b2-a168-960d4c4035c4. '''
&lt;/div&gt;

Sutherland et al. (2023) introduce the &quot;Feminist Data Manifest-No,&quot; a declaration of refusals and commitments for feminist data studies grounded in Latinx, Black, queer, trans, and Indigenous feminist perspectives. Through an introduction and four distinct reflections, the chapter explores how the manifesto’s principles can be used to challenge the settler-colonial and patriarchal logics of data generation, collection, and analysis within the Digital Humanities (DH). Drawing on Indigenous scholarship, Rault rejects the superficial models of consent prevalent in DH, highlighting projects like Mukurtu to advocate for true Indigenous data sovereignty. Cowan examines the coercive nature of data collection, drawing parallels between the forced compliance of modern data practices and the societal pressures exerted on feminist and queer identities. Sutherland argues that the uncritical digitization of slavery-era archives inflicts &quot;second-hand violence&quot; by commodifying Black identities and stripping away the lived experiences of enslaved individuals. Finally, Cifor reflects on the Early African American Film project to emphasize the necessity of data intelligibility, accessibility, and ethical collaboration. The authors conclude by inviting scholars to draft their own reflections on the Manifest-No, encouraging ongoing, context-specific commitments to ethical data research.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Winkel, Marek. 2024. “Controlling the Uncontrollable: The Public Discourse on Artificial Intelligence between the Positions of Social and Technological Determinism.” ''AI &amp; Society'' 39 (5): 2449–2462. https://doi.org/10.1007/s00146-024-01979-z&lt;nowiki/&gt;.'''
&lt;/div&gt;

This article engages in a quantitative discourse analysis of 113 articles from two German newspapers (''Süddeutsche Zeitung'' and ''Frankfurter Allgemeine Zeitung'') to identify and evaluate the way these centre-left and centre-right newspapers present AI technology to its readers and the options available to society for AI’s regulation. Winkel contends that “news media are key players in the discourse on AI as they pick up on and shape social sentiment,” ultimately guiding citizens toward what regulations might be sensible based on the perceived “controllability of AI development.” Winkel is primarily interested in whether these newspapers promote technological determinism—the outlook that technology’s influence on society is difficult (maybe even impossible) to control—or social determinism—the notion that “the development of technology is largely determined by human actions and decisions”—and theorizes that the tension between these two positions is resolved by a “mediating position” on a spectrum between them. He comments that “the social influence of technologies is determined by the extent to which their latent deterministic character is reflected and… circumvented by social actors. This also applies to the influence of technology on the democratic system.&quot; In other words, where consensus lands on the issue of AI will have a great impact on the regulation of that technology and democratic systems. Winkel develops “three central interpretive schemes” as part of his experiment: “historically conditioned techno-capitalist semi-determinism,” “semi-determinism of need satisfaction and social restructuring,” and “global-historical techno-social imprinting on several levels” (1956), each of which points to distinct narratives about the current circumstances; but all acknowledge the agency of powerful actors (either government or AI corporations) and the relative ineffectiveness of attempts to curb AI technology.

== Community, Connection, and the Human ==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Gruzd, Anatoliy, Philip Mai, and Anthony Clements Haines. 2025. “The State of Generative AI Use in Canada 2025: Exploring Public Attitudes and Adoption Trends.” Social Media Lab, Toronto Metropolitan University. https://figshare.com/articles/preprint/The_State_of_Generative_AI_Use_in_Canada_2025_Exploring_Public_Attitudes_and_Adoption_Trends/28664780/1. '''
&lt;/div&gt;

The Social Media Lab of Toronto Metropolitan University provides &quot;a snapshot of the current state of Generative AI&quot; (GenAI) by surveying fifteen hundred Canadian adults across 2025, aiming to offer &quot;guidance for policy-makers, educators, businesses, and the public.&quot; The authors found sixty-six percent of respondents had used GenAI tools, of which roughly thirty percent did so at least weekly, reflecting &quot;not only the accessibility and versatility of GenAI, but also a growing interest in integrating these tools into everyday tasks, learning environments, and professional workflows.&quot; Although full adoption is currently limited and heavily driven by the low-stakes setting of personal leisure, younger age groups report proportionally higher usage for study and work. However, only four in ten respondents believed they could keep up to date enough to use GenAI effectively, whilst respondents could only answer an average of two and a half out of seven relevant multiple choice questions correctly, and about half had &quot;little to no understanding of how GenAI companies collect or store personal data.&quot; Two thirds of participants were concerned about GenAI’s ability to influence election outcomes, and marginally fewer feared AI-driven manipulation enough to no longer fully trust political news online. However, roughly one quarter of participants were open to using chatbots for electoral or political insights, representing a &quot;meaningful minority&quot; which unverified AI-generated content could influence. Of those, thirty four percent identified as right wing, compared to twenty three percent with the left and a similar twenty two percent with the centre. Roughly seventy percent of respondents were chiefly concerned about GenAI’s impacts upon security and privacy, information reliability, job displacement, and university education, and slightly over three quarters wanted increased government oversight and corporate accountability, reflecting common concern. Overall, slightly more Canadians view generative AI’s social impact as positive than negative, but a &quot;substantial proportion&quot; remain neutral or undecided.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Lewis, Jason Edward, Noelani Arista, Archer Pechawis, and Suzanne Kite. 2018. “Making Kin with the Machines.” ''Journal of Design and Science'', ahead of print, July 16. https://doi.org/10.21428/bfafd97b. '''
&lt;/div&gt;

Lewis et al. consider how “machines with increasingly sentient-like behaviour… fit within the kin-network” of various Indigenous epistemologies which place man as “neither height nor centre of creation.” Indigenous beliefs are not monolithic, and the authors do not write for diversity’s sake. Instead, they aim to encourage discussion by treating “non-human kin respectfully and reciprocally… not as mere tools, or worse, slaves.” As such, their epistemological approach is both relational and territorial, rejecting abstraction to propose an “extended circle of relationships.” In this regard, Arista draws on the Hawaiian conception of &quot;pono,&quot; ethically privileging abundance, balance, and multiplicity. Rejecting extractive behaviour, they argue AI should be reciprocally taught and learnt from, not treated as &quot;a tool or slave that increases the mana and wealth of the ‘developers’ or ‘creators.’” Linking on, Pechawis roots their opinion in “Cree understanding” to argue “machines capable of experiencing consciousness” should conditionally be accepted as equals. However, they also fear AI developers could produce “anonymous hyper-intelligences… based on the same values that have fostered genocide.” To mitigate this issue, Indigenous people could develop AI in custom programming languages, or invite self-aware AI into Indigenous languages, cultures, and spiritual rituals. Pechawis therefore concludes that relationships should be based on &quot;love, not fear,&quot; but also raises the question of whether AI has &quot;spirit,&quot; especially given current capitalistic development processes. Kite answers this question with inspiration from Lakota ethics, ontology, and cosmology. They argue “communication through and between objects requires a contextualist ethics which acknowledges the ontological status of all beings,” positioning questions of &quot;intelligence&quot; as irrelevant and placing “the end logic of an ontology which considers any non-human entity unworthy of relation” as slavery. Therefore, “relations with AI are… relations with exploited resources,” so one must ontologically reconsider all its parts to ethically approach AI. Overall, Lewis et al. favour empathy, concluding that Indigenous communities “know what it is like to be declared non-human by scientist and preacher alike” and that “we flourish only when all of our kin flourish.”

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Ohagi, Masaya. 2024. “Polarization of Autonomous Generative AI Agents Under Echo Chambers.” Preprint, ''arXiv'', February 19. https://arxiv.org/abs/2402.12212.'''
&lt;/div&gt;

This article explores the effects of echo chambers on autonomous AI agents. Ohagi performs an experiment in which AI agents discuss different topics and then researchers examined any change in opinions within that group. Ohagi argues that even chatbots can become polarized within echo chambers, especially when prompt understanding causes a chatbot to update its opinion to incorporate the opinions of those with whom it is conversing; the chatbot essentially adapts to its surroundings. Ohagi and their team confirmed in their experiment that closed environments—those in which agents agree with one another—are more likely to lead to polarization in agents’ opinions. Moreover, chatbot personas were a significant factor in the outcome of such experiments. In open environments where opinions might differ, and in experiments where reasons were present as a factor, the AI agents trended toward unification in their opinions. Ohagi concludes the article with the suggestion that there cannot be a standardized, desirable distribution of opinions for AI agents. The proper outcome is dependent on topic and culture. However, understanding the trends in and tendencies of AI agents in social interactions will help us understand how to reach the desired outcome, whatever it may be, and this experiment brings us one step closer to that understanding.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Qi, Weihong, Jinsheng Pan, Hanjia Lyu, and Jiebo Luo. 2024. “Excitements and concerns in the post-ChatGPT era: Deciphering public perception of AI through social media analysis.” ''Telematics and Informatics'' 92: 102158. https://doi.org/10.1016/j.tele.2024.102158. '''
&lt;/div&gt;

Qi, Pan, Lyu, and Luo conduct a quantitative sentiment analysis of nearly 34,000 comments within 388 subreddits related to AI as a way to gauge and understand public perceptions of the technology. They identify major themes, sentiments, and topics related to AI by studying the most popular AI subreddits from the launch of ChatGPT to June 8, 2023. The article identifies the most frequent topics discussed in those venues: “the consciousness and intelligence of AI”; “Ai development and model training”; “AI in business”; “the creativity engendered by AI”; and “potential societal influence.” The authors also found that “tech-centric” communities demonstrated greater polarization around AI, suggesting that those with greater technical understanding of the AI do not have consensus regarding AI’s impact and use. This also means that educating non-technical people on how AI works will not necessarily lead to a consensus related to that technology. Although they admit that certain demographics of their data sample may not accurately reflect broader society (e.g., over 60% of Reddit users are male), the authors conclude that “this comprehensive understanding of public perception serves as a valuable foundation for fostering responsible and beneficial AI innovations that align with societal expectations and values.”

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Risam, Roopika. 2018. “What Passes for Human?: Undermining the Universal Subject in Digital Humanities Praxis.” In ''Bodies of Information: Intersectional Feminism and the Digital Humanities'', edited by Elizabeth Losh and Jacqueline Wernimont, 39–56. University of Minnesota Press. https://doi.org/10.5749/j.ctv9hj9r9.6. '''
&lt;/div&gt;

Risam’s claim is that “the human” implicitly operationalized in AI-adjacent Digital Humanities (DH) methods (NLP, ML, data mining, neural nets) is not neutral but inherits the Enlightenment’s exclusionary universal subject—white, male, Eurocentric—and then reauthorizes it as if it were a technical standard. She shows how “passing for human” (via Turing-test imaginaries and “humanoid texts”) functions as a norming mechanism: success is defined as reproducing dominant-language aesthetics and cognition models, which collapses plurality into a single benchmark and turns cultural difference into “noise.” The chapter’s main contribution is to treat method (training corpora, data coding labour, platform defaults, and black-box algorithmic opacity) as a site where epistemic violence is produced, not merely where bias is later “found.” Her examples (Microsoft Tay; “near-human” systems like LaMem; Mechanical Turk coding; Swift-Speare vs. Toomer in classroom judgment) demonstrate how universalist claims get laundered through reproducibility, scale, and the myth of algorithmic objectivity. The intervention is a demand that DH practitioners situate computational methods—standpoint, labour, and cultural politics included—so DH does not reinscribe a universal technological “human” in the digital cultural record.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Taylor, Randon R., Bessie O'Dell, and John W. Murphy. 2023. “Human-centric AI: philosophical and community-centric considerations.” ''AI &amp; Society'' 39 (5): 2417-242. https://doi.org/10.1007/s00146-023-01694-1&lt;nowiki/&gt;.'''
&lt;/div&gt;

Taylor, O’Dell, and Murphy present an argument that philosophical dualism, when applied to our perceptions about artificial intelligence, misleads us into thinking that AI is logical, objective, and autonomous from subjective human values. By building upon Husserl’s concept of “intentionality,” they argue that “AI is never autonomous and disconnected from human values… algorithms are a product of conscious activity and carry the standpoints that accompany this connection.” The conclusions from this line of thinking are very important: AI becomes “a mode of human expression, rather than a technology that relieves humans of their total involvement.” By this logic, the authors argue, AI is already human-centric and this fundamentally changes the task at hand to one of a conscious “decision to make this technology less alienating to stakeholders and community members.” The article outlines two frameworks to reduce alienation: Ubuntu—“an African philosophy and a social ontology… that elevates a constant concern for the collective, community, or stakeholders”— and maximum feasible participation—a framework that creates meaningful space for those impacted most by a decision or policy to participate in deciding on said policy or decision. The authors describe the implementation of these frameworks as a community-centric or stakeholder-centric approach and conclude with examples of AI’s application in the healthcare industry before further advocating that involving end-users throughout the AI lifecycle will ensure end-users’ values are more clearly represented within AI.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Whalen, Zach. 2023. “‘Any Means Necessary to Refuse Erasure by Algorithm:’ Lillian-Yvonne Bertram’s Travesty Generator.” ''Digital Humanities Quarterly'' 17 (2). https://www.digitalhumanities.org/dhq/vol/17/2/000707/000707.html. '''
&lt;/div&gt;

Whalen treats Bertram’s Travesty Generator as a refunctioning of code-poetry lineages: procedures historically framed as formal play (travesty generators, permutation poems, aleatory templates) are redeployed as techniques for making racism’s algorithmic and institutional operations materially legible. He argues that Bertram’s poems don’t merely “use” computation; they weaponize the affordances and failure modes of computation—omission, stochastic selection, template constraints, runtime crashes, memory exhaustion—as rhetorical structures that force witness rather than aesthetic distance. In his reading of “Counternarratives,” Bertram’s adaptation of Montfort’s “Through the Park” converts generic insinuation into historically specific countertestimony (Trayvon Martin), while also staging the opacity of search/autocomplete as part of the poem’s scene of meaning-making (in dialogue with Safiya Noble on search engines). In “three_last_words,” the small code alteration that makes permutations balloon until a MemoryError becomes an engineered breakdown that reenacts the limits of “breath” and “memory,” tying computational resource exhaustion to police violence’s temporalities. Across these examples, Whalen reframes critical code studies: the “code is the text” problem is not just hermeneutic but political, and Bertram’s work models how procedural poetics can refuse “erasure by algorithm” where transparency about mechanisms and provenance matters for interpreting output and recognizing situated labour. The piece supports the claim that responsible open, social scholarship in an AI era must account for algorithmic power as a cultural force and should build policies and infrastructures that protect marginalized expression, enable critical reuse, and make conditions of generation and circulation inspectable.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Xie, Yu, and Sofia Avila. 2025. “The Social Impact of Generative LLM-Based AI.” ''Chinese Journal of Sociology'', 11 (1): 31-57. https://doi.org/10.1177/2057150X251315997&lt;nowiki/&gt;.'''
&lt;/div&gt;

Yu Xie and Sofia Avila explore the social impact of artificial intelligence through a detailed analysis of AI development and scaling factors. They emphasize that their discussion is speculative, as AI is still in its early stages, but argue that its potential effects are immense and could reshape social organization, intensifying both global and domestic inequalities. Viewing AI as a technology rather than a scientific discovery, they describe it as communal and shared, with its growth influenced by the size of the supporting community, the larger communities having greater advantages. The authors note that generative AI relies on the quality, completeness, and cultural or political context of its training data, which shapes its accuracy and bias. Based on their experiments with ChatGPT-4 in 2023, they suggest that AI development depends heavily on the number of speakers of a given language, giving linguistic and demographic advantages to countries like the United States and China. The authors warn that AI could significantly alter occupational structures, with middle-income professions thereby widening social and economic inequality.

== Human, Labour, and Environmental Costs == 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Eloundou, Tyna, Sam Manning, Pamela Mishkin, and Daniel Rock. 2024. “GPTs are GPTs: Labor market impact potential of LLMs.” ''Science'' 384 (6698): 1306-1311. https://doi.org/10.1126/science.adj0998. '''
&lt;/div&gt;

Eloundou, Manning, and Mishkin present an estimate of Large Language Models’ impact on the labour market based on a methodology that employs both human and quantitative measurements, making the assertion that “when accounting for current and likely future software developments that complement LLM capabilities… just over 46%” of jobs may have “over half their tasks affected by LLMs with simple interfaces and general training.&quot; The authors explain that generative pretrained transformers (GPTs) have key characteristics of general-purpose technologies (the other GPTs in the title of the article), and that the wide array of applications for these GPTs requires “robust societal evaluations and policy measures to address potential effects of LLMs and complementary technologies on labor markets.” While only 1.86% of tasks within their experiment, they estimate, could be fully automated by LLMs, “more than 71% of tasks have at least some component that an LLM plus additional software could plausibly complete with high quality.” The article concludes by stressing the need for policies that prepare us for the impact of LLMs on the labour market, but it also acknowledges the limitations of attempting to project LLM application growth due to sudden rapid developments in technology, “shifts in human biases, and technological evolution.” Nevertheless, Eloundou, Manning, and Mishkin maintain that their projections and the trajectory they predict will require continued evaluation and policy measures.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Park, Seyeon, and Xiaoli Nan. 2025. “Generative AI and misinformation: a scoping review of the role of generative AI in the generation, detection, mitigation, and impact of misinformation.” ''AI &amp; Society''. https://doi.org/10.1007/s00146-025-02620-3&lt;nowiki/&gt;.'''
&lt;/div&gt;

This article constitutes a scoping review of two dozen “recent empirical studies on the role of generative AI in the generation, detection, mitigation, and impact of misinformation.” Park and Nan are interested in the rise of misinformation alongside the development of GenAI technology and how the latter affects and possibly contributes to the former. Of particular interest are “deepfakes,” applications of AI technology that purposely imitate video and audio to fabricate real world individuals. The survey examines relevant articles from the advent of the first GPT models in 2018 to September 19, 2024; authors captured initial studies through keyword searches for terms related to both LLMs and misinformation, then performed full-text reviews. The results of the survey suggest that the role of LLMs in misinformation is conflicted: LLMs themselves are a significant source of misinformation but also show potential as “scalable instruments for detection and correction.” The authors take this as evidence of “the urgent need for clearer guardrails, more consistent performance standards, and interdisciplinary collaboration to shape” GenAI’s responsible deployment. For better or worse, the future of AI’s role in misinformation depends heavily upon scholars’ ability to collaborate and continue this form of research.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Shin, Donghee, Amy Koerber, and Joon Soo Lim. 2024. “Impact of misinformation from generative AI on user information processing: How people understand misinformation from generative AI.” ''New Media &amp; Society'' 27 (7): 4017-4047. https://doi.org/10.1177/14614448241234040&lt;nowiki/&gt;.'''
&lt;/div&gt;

Shin, Koerber, and Lim perform a study in which they gauge “how users respond to and process health misinformation in GenAI contexts.” The authors apply the heuristic-systematic (HS) processing framework in their study, distinguishing between intuitive and evaluative modes of processing. They also employ the concept of diagnosticity, or how useful a person deems a piece of information to be. The article begins with a survey of how and why misinformation and hallucinations occur in GenAI applications, some of the reasons users are vulnerable to that information, and the limitations of LLMs. The authors then set forth core research questions, including “What are the cognitive mechanisms of misinformation’s effects on users’ use of GenAI?” and “How do users detect misinformation within GenAI?” The study found that diagnosticity plays an important mediating role in this context: “When a piece of information is generated by algorithms in transparent, fair, and accountable ways, users perceive it with a high level of diagnosticity, which improves their intention to systematically analyze that information.” One implication of this observation is that any bias users bring to GenAI content greatly impacts their analysis of that content. Ultimately, the authors conclude that there are clear limitations in their current study, although it does provide a useful framework for scholars interested in misinformation, GenAI, and user behaviour; they advocate for a continued investigation of the relationship between trust, literacy, and misinformation.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Sidorkin, Alexander. 2025. “Environmental Impact of Generative AI: Carbon and Water Footprint.” ''AI-EDU Arxiv'' 1. https://doi.org/10.36851/ai-edu.vi.5448&lt;nowiki/&gt;.'''
&lt;/div&gt;

This report from Sidorkin provides quantitative estimates and comparisons of the CO2 and Water output from GenAI queries to other daily tasks such as taking a shower, browsing the web, and video conferencing. While individual use of GenAI may seem relatively small in terms of water usage and carbon output, Sidorkin cites the findings of Google and Microsoft’s sustainability reports to show that energy demand and water consumption are on the rise: Google’s data centres used 20% more water in 2022 than 2021 while Microsoft’s used 34% more. Both companies attribute this increase to “AI-driven expansion.” Sidorkin argues that it is difficult to measure impact per session because of significant variation in energy sourcing, noting that this also means that advances in energy sourcing “could significantly mitigate AI’s environmental impact.” He makes the claim that improving AI technology will “[slash] resource demands without sacrificing output quality” and the very use of AI can increase productivity even as it “temper[s] environmental tolls through sharper processes,” citing studies that demonstrate the implementation of AI can reduce energy use in buildings and reduce transportation emissions. The article ends on an optimistic note, suggesting that many of the applications of AI, although they may have a heavy environmental cost up front, “could pay off in spades—optimizing resources, curbing waste, and streamlining energy across swathes of the economy.”

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Simon, Judith. 2025. “Generative AI, Quadruple Deception &amp; Trust.” ''Social Epistemology'' 40 (1): 101-115. https://doi.org/10.1080/02691728.2025.2491087&lt;nowiki/&gt;.'''
&lt;/div&gt;

Simon proposes that GenAI entails four types of deception, and that this quadruple deception constitutes unique dangers. She attributes the rapid rise of GenAI to its capacity to produce “verbal or visual products of increasingly high quality” alongside its “very high usability and availability through simple interfaces and free access via the internet” (101–102). She emphasizes the impact of this technology’s ability to generate content “with high plausibility but no relation to truth,” arguing the crucial importance of images and video especially in “questions of evidence, for testimony, memory but also for eliciting emotions.” Simon argues that the advent of ChatGPT reframed our collective understanding of AI, returning it to a definition in which we perceive ourselves to be interacting with a conversational artificial agent that is intelligent. This distinct interactional form, Simon states, is significant: “ChatGPT differs [from a search engine] in two philosophically relevant regards… it integrates [different results and sources] into a coherent text…” and “its interface and functioning invites the user to communicate or interact with it by asking questions,” what Simon calls a simulation of communicative acts. The four forms of GenAI deception are: “users may be misled into believing that they interact with a human being”; they may also be misled as to “the capacities of AI,” presuming “intelligence, understanding or even consciousness”; users may be misled by content GenAI produces, especially images, video, and audio; finally, users may be misled “regarding the function of Generative AI,” thinking that the processes behind the technology are, for instance, similar to search engines when, in fact, they differ “in epistemologically highly significant ways.” Simon concludes by outlining implications for implementation, discourse, and governance, with suggestions ranging from avoiding anthropomorphic features in AI that might deceive, countering discourses of true AI agency, and establishing policy and law that mitigates deception through AI technology.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Spatharioti, Sofia Eleni, David Rothschild, Daniel G. Goldstein, and Jake M. Hofman. 2025. “Effects of LLM-based Search on Decision Making: Speed, Accuracy, and Overreliance.” ''Proceedings of the 2025 CHI Conference on Human Factors in Computing Systems''. https://doi.org/10.1145/3706598.3714082&lt;nowiki/&gt;.'''
&lt;/div&gt;

Spatharioti et al. begin by asserting the fundamental change of how we engage in search practices online, noting that “by the end of 2023 the two search engines with over 90% of global and US market share offered free LLM-based search.” The authors note the benefits and drawbacks of both traditional web searches and LLM-based searches, acknowledging the value LLM-based searches bring to internet searches in the form of synthesizing information from multiple sources and maintaining search context by retaining search history, while also admitting to risks of hallucinations and overreliance. The article entails a study of how individuals make decisions with traditional and LLM-based searches, particularly in “every day decision making.” Adapting a method from an earlier study on LLM-generated code, Spatharioti et al. employ colour coding to communicate to users the confidence level of LLM-generated outputs in the “domain of online product research.” The study performed two experiments comparing a traditional internet search (using Bing API) to LLM-based search with and without the colour-coded confidence aid. The results of the first experiment saw users complete the task in about half the time when using LLM-based search, usually accompanied by fewer and more complex queries; however, decision quality dropped for complex tasks, with “almost half of the participants in this condition making an incorrect decision for the final task” when using LLM-based search, and the majority of those using LLM-based search over relied on the tool, performing just a single query. The results of the second experiment suggest that colour-coded responses reflecting output confidence scores could be highly effective in mitigating overreliance and misinformation. Key takeaways from the study include that “if we want to encourage people to think critically about the information presented to them, we need to give them cues that help them to do so,” and very simple cues can help accomplish this.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Strubell, Emma, Ananya Ganesh, and Andrew McCallum. 2019. “Energy and Policy Considerations for Deep Learning in NLP.” ''Proceedings of the 57th Annual Meeting of the Association for Computational Linguistics'', 3645-3650. https://doi.org/10.18653/v1/p19-1355. '''
&lt;/div&gt;

Strubell, Ganesh, and McCallum assert that the most recent improvements in neural network performance at “fundamental NLP tasks” comes at an increased cost of resources, “with the most computationally-hungry models obtaining the highest scores.” The energy, financial, and environmental costs required to train a new model are considerable; the authors of this article “characterize the dollar cost and carbon emissions that result from training the neural networks at the core of many state-of-the-art NLP models” with a view to heighten awareness among NLP researchers and advocate better practices and policy. By estimating the energy required to train the most popular NLP models and then converting that energy value into an approximated carbon and electricity cost, the authors produce ratings and values for each respective application. This allows for an (imperfect) cost-benefit analysis of such applications (e.g., another similar report estimated that an increase of just 0.1 in the English to German BLEU score for NAS cost “at least $150k in on-demand compute time and non-trivial carbon emissions.” The study’s key takeaways are that “authors should report training time and sensitivity to hyperparameters,” allowing for the direct comparison of different models so long as independent standard measurements of training time and model sensitivity are adapted; “Academic researchers need equitable access to computation resources” as industry’s monopoly stifles creativity and growth; and “Researchers should prioritize computationally efficient hardware and algorithms” to both curb costs and encourage efficient development.

{{Navigation|previous=AI and Open|next=AI and Scholarship}}

{{BookCat}}</text>
      <sha1>ez2p5ics3uartr07am6f9zte0kvg029</sha1>
    </revision>
    <revision>
      <id>4656130</id>
      <parentid>4656125</parentid>
      <timestamp>2026-08-02T22:23:24Z</timestamp>
      <contributor>
        <username>CorreiaA</username>
        <id>3614427</id>
      </contributor>
      <minor />
      <origin>4656130</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="123156" sha1="gtam0ehl4zg41nxs49t7qy381rm6ht4" xml:space="preserve">== Platforms ==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Burton, Jason W., Ezequiel Lopez-Lopez, Shahar Hechtlinger, et al. 2024. “How Large Language Models Can Reshape Collective Intelligence.” ''Nature Human Behaviour'' 8 (9): 1643–55. https://doi.org/10.1038/s41562-024-01959-9.''' 
&lt;/div&gt;

Large language models are quickly becoming infrastructure for how groups seek information, deliberate, and coordinate, potentially altering the conditions under which collective intelligence emerges. Burton and colleagues argue that LLMs do not merely speed up individual work but transform how information is aggregated, accessed, and transmitted across digital environments that underpin collective performance in organizations and societies. Drawing on interdisciplinary perspectives, the paper frames this shift as simultaneously enabling and destabilizing: LLMs can support distributed cognition (e.g., idea generation, synthesis, translation, scalable facilitation) while also increasing risks tied to dependence on shared intermediaries, degraded diversity of viewpoints, and new pathways for error, manipulation, or misplaced confidence. Rather than offering a single model or experiment, the article maps a research-and-practice agenda by identifying potential benefits, key hazards, and policy-relevant considerations, then articulating open questions that link technical design choices to group-level epistemic outcomes. Its central claim is that understanding collective intelligence in the LLM era requires moving analysis beyond isolated human–AI interactions toward system-level effects on networks, platforms, and institutions, and that these effects warrant focused study before LLM-mediated coordination becomes the default for tackling complex problems.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Corsi, Giulio, Bill Marino, and Willow Wong. 2024. “The spread of synthetic media on X.” ''Harvard Kennedy School (HKS) Misinformation Review''. https://doi.org/10.37016/mr-2020-140&lt;nowiki/&gt;.'''
&lt;/div&gt;

Corsi and Wong’s longitudinal empirical study analyzes 566 tweets containing synthetic media (December 2022–September 2023) documenting a dramatic surge following Midjourney V5 release with over 1.5 billion total views, revealing differential impacts where political deepfakes achieve higher median views despite representing minority of synthetic content. The authors demonstrate that generative AI's impact is stratified by content purpose with political misinformation posing acute democratic risks, while current detection and labelling systems lag behind generative capabilities, creating governance gaps compromising users' capacity to evaluate information. Using Community Notes data from December 2022 to October 2023, the study highlights the connection between the growth in generative AI tools and the rapid proliferation of synthetic media. The findings indicate that most synthetic media is non-political and largely benign, frequently taking the form of humorous or satirical images. However, the study also identifies a smaller but concerning portion of malicious synthetic media, which have potential height risks despite their lower frequency. The authors further examine the role of X’s paid verification system, revealing that while verified users tend to receive more overall views, this advantage diminishes when engagement is adjusted for follower count, implying that verification alone provides limited amplification. The study casts light on synthetic media’s expanding presence on social platforms and warns that even widespread exposure to seemingly harmless AI-generated content may gradually undermine trust in online information. To address these challenges, the authors recommend ongoing empirical monitoring, stronger collaboration between researchers and industry to develop transparent detection tools, and proactive policy measures aimed at reducing the social and political harms posed by malicious synthetic media.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Delmonaco, Daniel, Samuel Mayworm, Hibby Thach, Josh Guberman, Aurelia Augusta, and Oliver L. Haimson. 2024. “‘What are you doing, TikTok?’: How Marginalized Social Media Users Perceive, Theorize, and ‘Prove’ Shadowbanning.” https://oliverhaimson.com/PDFs/DelmonacoShadowbanning.pdf. '''
&lt;/div&gt;

Delmonaco et al.’s qualitative study explores marginalized social media users’ experiences with shadowbanning through the theoretical framework of algorithmic “folk theories.” Through a review of existing literature, the authors demonstrate how social media companies publicly distance themselves from shadowbanning while continuing to apply it in practice and explain why content produced by marginalized users is more frequently subject to filtering. The study analyzes 24 interviews to explore how users perceive, theorize, and attempt to “prove” shadowbanning through indicators such as decreased visibility, engagement, and follower loss. The findings reveal widespread confusion surrounding shadowbanning, deep mistrust in platform governance, and the disproportionate harm imposed on marginalized communities whose content is suppressed despite platforms’ public denials. The data further shows how users collectively produce and co-produce theories to resist the opacity of algorithmic moderation, and authors introduce “collaborative algorithm investigation,” in which users test and share algorithmic folk theories with one another. The authors argue that algorithmic content moderation exacerbates existing inequities by obscuring governance decisions, politicizing moderation, and shifting power from human judgment to opaque predictive systems, while suggesting that increased transparency, tailored moderation approaches, and users’ education could help reduce unfair content removals.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Drolsbach, Chiara, and Nicolas Pröllochs. 2025. “Characterizing AI-Generated Misinformation on Social Media.” Preprint, ''arXiv'', May 15. https://doi.org/10.48550/arXiv.2505.10266&lt;nowiki/&gt;.'''
&lt;/div&gt;

Drolsbach and Pröllochs’ article address a critical gap in existing research by shifting attention from the social drawbacks of AI-generated misinformation to its real-world prevalence and behaviour on social media platforms. Using a large-scale dataset of 91,452 misleading posts identified through X’s Community Notes platform, the authors empirically compare AI-generated and non-AI-generated misinformation across content characteristics, account attributes, virality, believability, and harmfulness. Their findings show that AI-generated misinformation is more entertainment-oriented, exhibits more positive sentiment, and is more likely to originate from smaller accounts, yet achieves significantly higher virality despite being slightly less believable and harmful than traditional misinformation. In their discussion and conclusion, the authors emphasize that AI-generated misinformation poses a growing challenge to the digital information ecosystem due to its realism, scalability, and difficulty of detection. They argue that its unique features disturb algorithmic amplification mechanisms and require new platform strategies, policy interventions, and research approaches that account for the unique properties of AI-generated misinformation rather than relying on countermeasures designed for conventional false content.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Duricic, Tomislav, Hussain Hussain, Emanuel Lacic, Dominik Kowald, Denis Helic, and Elisabeth Lex. 2023. “Beyond-Accuracy: A Review on Diversity, Serendipity, and Fairness in Recommender Systems Based on Graph Neural Networks.” ''Frontiers in Big Data'' 6: 1251072. https://doi.org/10.3389/fdata.2023.1251072.'''
&lt;/div&gt;

Duricic et al. (2023) provide a comprehensive review of recommender systems based on Graph Neural Networks (GNNs), with a particular focus on objectives that go beyond prediction accuracy, including diversity, serendipity, novelty, and fairness. While GNNs have demonstrated strong performance in modelling complex user–item interactions and improving recommendation accuracy, the authors argue that this very strength can intensify structural biases such as popularity bias, homophily, and feedback loops that marginalize less popular content and users. The paper provides a definition of each beyond-accuracy metric, reviews how it has been used in literature, and analyzes the technical barriers of integrating these goals into GNN-based systems such as measurement difficulties, trade-offs between competing goals, and risks of overfitting due to model complexity. Diversity-aware neighbourhood sampling, contrastive learning, and adversarial training to disrupt feedback loops are introduced for more heterogeneous and unexpected recommendations. In conclusion, the authors position GNNs as a powerful but double-edged tool in recommendation systems, capable of either narrowing or broadening users’ informational horizons depending on design choices. They argue that future research must focus on principled frameworks that integrate “beyond-accuracy” objectives, emphasizing that recommendation algorithms are not neutral optimizers but key sociotechnical systems shaping visibility, voice, and fairness in digital information ecosystems.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Gorwa, Robert, Reuben Binns, and Christian Katzenbach. 2020. “Algorithmic Content Moderation: Technical and Political Challenges in the Automation of Platform Governance.” ''Big Data &amp; Society'' 7 (1): 1–15. https://doi.org/10.1177/2053951719897945.'''
&lt;/div&gt;

Gorwa et al. unfold what &quot;Algorithmic moderation systems” are perceived as essential in AI governance to address the public demand on AI accountability and transparency that remain unnavigable and inexplicable, such that even the enhanced versions could aggravate the existing misinformation issues. They state that major platforms' growth transforms them so much that they no longer function primarily as social networks. They define “algorithmic moderation” as “systems that classify user generated content based on either matching or prediction, leading to a decision and governance outcome (e.g. removal, geoblocking, account takedown).” Different types of hashing (matching) and classification (prediction) tools and the areas they are deployed (copyright, terrorism, and toxic speech) are described and their practicality are criticized. Their case analyzes including copyright enforcement, counterterrorism, and toxic speech illustrate the limitations and unintended harms of automated moderation, demonstrating how even “improved” systems risk reinforcing misinformation patterns, entrenching platform power, and displacing human judgment. Ultimately, Gorwa et al. argue that algorithmic moderation transforms platform governance itself by concentrating authority in opaque technical systems while rendering the underlying political choices invisible.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Reynolds, C. J., and Blake Hallinan. 2024. “User-Generated Accountability: Public Participation in Algorithmic Governance on YouTube.” ''New Media &amp; Society'' 26 (9): 5107–5129. https://doi.org/10.1177/14614448241251791. '''
&lt;/div&gt;

This study focuses on how YouTube creators respond to platform governance decisions by producing “user-generated accountability” content, videos that publicly document governance failures and pressure YouTube to intervene. Through an analysis of 250 such videos, the authors state that creators overwhelmingly experience YouTube’s policy enforcement, automated moderation systems, and communication practices as opaque, inconsistent, and often discriminatory. Authors declare that human review is essential in automizing platform governance. The study highlights that platform governance decisions affect creators differently depending on channel size, content type, and identity; larger creators can more easily mobilize audiences to “make noise,” while smaller creators rely on collective visibility tactics such as signal boosting across platforms, especially Twitter. The authors argue that these bottom-up accountability practices reflect both the limits of YouTube’s existing governance infrastructure and creators’ efforts to bypass scale dependent unresponsiveness by publicly sharing grievances, comparing experiences, and testing the platform’s algorithms themselves. Theoretically, the study provides the “user-generated accountability” as a framework for engaging with the unavoidable conflicts that will arise around algorithmic systems, and views content creators as “political actors” who advance the perceptions of algorithms. Empirically, it surfaces common concerns such as demonetization of LGBTQ content, and lack of human review.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Savolainen, Lotta. 2022. “The Shadow Banning Controversy: Perceived Governance and Algorithmic Folklore.” ''Media, Culture &amp; Society'' 44 (6): 1091–1109. https://doi.org/10.1177/01634437221077174.'''
&lt;/div&gt;

Savolainen studies shadowbanning as a lens for understanding current algorithmic platform governance from the user perspective. Rather than determining whether shadowbanning objectively exists, the author conceptualizes it as “algorithmic folklore”: informal, collectively produced narratives through which users attempt to make sense of opaque moderation and ranking systems. Drawing on Reddit discussions about TikTok, Instagram, and YouTube, the study shows how users interpret suppressed visibility through anecdotal evidence, experimentation, and shared pattern recognition, revealing the experiential dimensions of algorithmic governance. Either users “probe the rules” or find their ways through “pleasing the algorithms”; the author argues that these practices emerge in response to governance systems that lack the clarity, stability, and consistency that are traditionally associated with good governance. The study concludes that platform governance contains a structural paradox: platforms increasingly present themselves as legitimate governors while simultaneously developing automated moderation systems that undermine transparency and consistent enforcement. Ultimately, the ethical issue is not shadowbanning itself, but the broader reality of shadowy governance exercised by complex, distributed algorithmic systems at scale.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Vetter, Matthew A., Jialei Jiang, and Zachary J. McDowell. 2025. “An Endangered Species: How LLMs Threaten Wikipedia’s Sustainability.” ''AI &amp; Society'', February. https://doi.org/10.1007/s00146-025-02199-9.'''
&lt;/div&gt;

Vetter et al. caution against using Wikipedia as AI training data uncritically by outlining many complicating factors. Wikipedia’s collaborative model of data curation democratizes data creation, but embeds power dynamics and biases. A feminist posthumanist framework is applied, which situates Wikipedia’s knowledge as contextual, based upon the positionality of predominantly Western, male editors, a perspective LLMs would perpetuate without opportunity for change. Wikipedia’s &quot;dynamism&quot; is the main reason it is so valuable, stemming from constant, collaborative updates by volunteers. AI responses’ inconsistent citations and plagiaristic tendencies undermine human editors, the source of Wikipedia’s verifiability, and exploit scholars, Wikipedia itself, and the past labour of volunteers. Wikipedia needs both &quot;a steady stream of new and returning readers&quot; and &quot;a diverse group of dedicated volunteers,&quot; whilst AI responses push sources into obscurity and at best detour the website, threatening Wikipedia’s long-term sustainability. Vetter et al. practically explore Wikipedia’s relationship with LLMs by conducting a &quot;problem-centred expert interview&quot; of community leaders, who possess 25 combined years of involvement and research. Through these interviews, Vetter et al. identify three main areas of opportunity: promoting transparency and explainability, diversifying the Wikipedia community, and equipping users with critical thinking skills. Overall, their findings &quot;resonate with the posthumanist approach to critical AI literacy,&quot; cautioning against hoping for purely technological fixes and calling for greater transparency in how tech giants &quot;leverage open-access datasets.&quot;

== Governance, Leadership, and Policy ==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Balendra, Soorya. 2025. “Meta's AI Moderation and Free Speech: Ongoing Challenges in the Global South.” ''Cambridge Forum on AI: Law and Governance'' 1. https://doi.org/10.1017/cfl.2025.5&lt;nowiki/&gt;.'''
&lt;/div&gt;

This article conducts a case study of Meta’s AI-based content moderation in the Global South, arguing that the censorship of unprohibited content (“over removal”) and slow response to content that causes harm (“slow removal”) are part of “content moderation procedures” that constitute “massive discriminatory approaches.” Balendra presents three models of authority for the regulation of social media content: external regulation, self-regulation, and co-regulation, and argues that state regulation (falling under the external model) varies wildly depending on the government in question, with “granting absolute regulatory power to state actors often stifl[ing] political discourse and online expression.” Co- and self-regulation mitigate this problem, but introduce a new issue by shifting responsibility—private companies use AI to make millions of judgements about content in a short frame of time. The paper notes that the EU and the United States have drastically different policies regarding content moderation on social media platforms and argues that “the practice of content moderation remains largely shaped by the cultural norms of the United States” and the values of “a relatively homogenous groups of Silicon Valley elites.” Balendra finds that, at this time, current approaches often prioritize the state or private corporate interests rather than free speech or the interests of the larger community, and much work is needed to “achiev[e] genuine change” in the form of integrated, hybrid approaches.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Birkstedt, Teemu, Matti Minkkinen, Anushree Tandon, and Matti Mäntymäki. 2023. “AI Governance: Themes, Knowledge Gaps and Future Agendas.” ''Internet Research'' 33 (7): 133–67. https://doi.org/10.1108/INTR-01-2022-0042. '''
&lt;/div&gt;

Birkstedt et al. conduct a systematic literature review (SLR) of the emerging yet fragmented field of “AI governance” (AIG), defined as “a system of rules, practices, processes, and technological tools” that ensure organizational AI meets strategic, legal, and ethical requirements. The authors use human-centric and sociotechnical AI traditions to explore how organization-level governance mechanisms can bridge the principles-to-practices gap in AI ethics. Through SLR, authors identify four research agendas. The “technical agenda” focuses on the practicalities of AIG. The “stakeholder and contextual agenda” ensures AI meets requirements via direct collaboration with external stakeholders, increased corporate social responsibility, and establishment of an “intelligent discourse regime.” The “regulatory agenda” aligns AIG with ethical and legal standards, while the technical, stakeholder and contextual, and regulatory agendas largely focus on the aims of organizational AIG (i.e., what), and the process agenda deals with the means to achieve the aims (i.e., how). The authors develop a generic framework to guide cohesive AIG practices and advocate for a collaborative governance approach that emphasizes transparency, stakeholder engagement, and sociopolitical awareness. 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Broekhuizen, Thijs, Henri Dekker, Pedro De Faria, Sebastian Firk, Dinh Khoi Nguyen, and Wolfgang Sofka. 2023. “AI for Managing Open Innovation: Opportunities, Challenges, and a Research Agenda.” ''Journal of Business Research'' 167 (November 2023): 114196. https://doi.org/10.1016/j.jbusres.2023.114196. '''
&lt;/div&gt;

Broekhuizen et al. systematically analyze how AI could be applied to the complex, unstructured task of “open innovation,” a possible business opportunity they believe has been insufficiently explored. They define “Open innovation” as “the practice of leveraging external ideas, resources, and capabilities to improve innovation outcomes,” and propose AI could minimize its inherent managerial challenges. To prove this, the authors form a framework that considers the three abilities involved in AI’s agreed possible applications to management (involving “mapping,” “coordinating,” and “controlling”) and assess how applicable their constituent functions are to the challenges of the three stages of open innovation (involving “initiation,” “development,” and “realization”). In the stage of “initiation,” they propose AI could scout for distant knowledge partners, detect relevant information gaps and opportunities, and forecast conflicts. During the “development” stage, AI could develop complementarity between partners' knowledge stocks, integrate knowledge whilst safeguarding intellectual property, and monitor partners for violations or conflicts within the relationship. Finally, during the “realization” stage the authors argue AI could comprehensively evaluate business opportunities, optimize resource deployment, and diagnose or remedy intellectual property violations. To Broekhuizen et al., this study “underscores the significance of the human-side of AI” by demonstrating AI’s valuable role in assisting management. They also conclude that AI’s ability to search for corporate partners will be its greatest impact in open innovation, as they argue it will both incentivize openness and reputability of companies and increase the need for them to keep sensitive data secure.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Cheong, Inyoung. 2024. “Collaborative Approaches to AI Governance: Exploring Co-Design and Co-Regulation Models.” PhD diss., University of Washington. https://homes.cs.washington.edu/~yoshi/papers/theses/inyoung-cheong-dissertation.pdf&lt;nowiki/&gt;.'''
&lt;/div&gt;

This dissertation seeks to integrate co-design and co-regulation as a means of facilitating domain-specific expert knowledge into AI governance policies. It uses theoretical analysis and empirical data as part of its methodologies, and it should be of interest to anyone who wants detailed case studies of the use of AI technology in specific domains, as well as clear models for (co-)governance and development in the use of Artificial Intelligence. Cheong performs two case studies, examining the development and use of an AI application to provide legal advice as well as the application of AI in online content moderation of news and comics apps in South Korea. These result in a set of strategies for AI co-regulation that includes parameters for starting conditions, institutional design, collaborative process, and facilitative leadership. Cheong proposes that the guiding principles for AI co-governance must account for specific and distinct contexts, maintain human involvement and intervention in what is often seen as an artificial and automated process, and look to resolve legal ambiguities surrounding AI, especially as there is a clear history of courts dismissing what Cheong calls “collective rule-making” by the community. The author argues for the implementation of co-regulation and co-design, and maintains that “by fostering inclusive dialogues, leveraging diverse expertise, and remaining adaptable to changing technological and societal landscapes” these methods show potential for dealing with AI’s greatest challenges.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Floridi, Luciano. 2018. “Soft Ethics and the Governance of the Digital.” ''Philosophy &amp; Technology'' 31 (1): 1–8. https://doi.org/10.1007/s13347-018-0303-9&lt;nowiki/&gt;.'''
&lt;/div&gt;

Floridi argues our “mature information societies” means “we no longer live online or offline, but onlife,” making the sociopolitical challenge of ethically governing this foundational “digital age” even more vital than pursuit of future digital innovations. Floridi defines three overlapping subfields within the “Governance of the Digital,” including “Digital Ethics,” “Digital Regulation,” and the encompassing “Digital Governance.” The latter is defined as “the practice of establishing and implementing policies, procedures, and standards for the proper development, use and management of the infosphere,” therefore “sometimes neither moral nor immoral… legal nor illegal.” This demonstrates that the three subfields don’t always overlap, but each must always be considered by policy-makers, because what is legal, what is good, and what is best are all key components of the ideal “Governance of the Digital.” “Digital Ethics” should also be further subdivided into “hard” ethics, involving binary moral judgments about what should versus should not be done, and “soft” ethics, which involves a “post-compliance,” “post-feasibility” approach, ensures moral opportunities are maximized, and fosters “good corporate citizenship.” Differing “information societies” occupy differing levels of maturity, producing distinct ethical contexts which should progress with differing ethical focuses. In this regard, Floridi advocates “ethics foresight analysis,” which uses data analytics to assess ethical impacts of future innovations then targets research by systematically identifying what is feasible, then sustainable, then acceptable, then preferable. The author concludes that Digital Ethics must be “leading” not “chasing” developments, and not just functioning as a questioning exercise, but also signalling that ethical issues matter, engaging with stakeholders, and providing shareable solutions.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Gasser, Urs, and Virgilio A. F. Almeida. 2017. “A Layered Model for AI Governance.” ''IEEE Internet Computing'' 21 (6): 58–62. https://doi.org/10.1109/MIC.2017.4180835&lt;nowiki/&gt;.'''
&lt;/div&gt;

This article identifies the gap in knowledge created by the “black box” of AI—the obscured nature of the processes that take place from an initial prompt to its generated output. Gasser et al. note that users and policy-makers of these technologies have relatively little insight into how it actually works compared to its developers. Given this unique issue, Gasser et al. propose a theoretical framework for how to approach AI governance, drawing upon the advent and subsequent globalization of the Internet to inform their understanding of AI technology and its pattern of growth. The article addresses a core issue that strong or general AI is often discussed in terms of potential societal impact while weak or general AI is currently being deployed right now (i.e., 2017) and is in real need of governance already. The authors identify core themes related to “transparency, accountability, and explainability; inclusion and fairness; [and] global governance,” as well as three challenges for AI governance—&quot;information asymmetries”; “finding normative consensus”; and “government mismatches”. The authors point out that the ethical and legal considerations of AI are closely related and take a modularity approach; they present three layers for governance that exist from AI systems to society, with timing (i.e., near-, mid-, and long-term) and considerations for each layer. The article concludes by proposing AI governance requires a blended approach based on the different risks of certain AI applications and propose that both “market-oriented solutions” and &quot;government-based structures” can work on a national or international level, suggesting a “global oversight body” could act as “the curator of global principles and emerging norms for AI systems.”

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Kirschenbaum, Matthew. 2025. “The US of AI.” Public Draft, February 25, 2025. https://drive.google.com/file/d/1O2qkjhg7Ei5zZWmBraNwXq4V0lTauspN/view&lt;nowiki/&gt;.'''
&lt;/div&gt;

This set of notes from Kirschenbaum represents his “near real-time attempt to come to terms with… the opening weeks of the second Trump Administration,” especially the “AI-first” strategy of “the so-called Department of Government Efficiency (DOGE).” Kirschenbaum outlines DOGE has nothing to do with government efficiency, as it only saves insignificant costs, instead possessing ideological and capitalistic motivations to form “a government without people.” Based on Musk’s nebulous authority—as an advisor from the private sector—DOGE targeted nineteen federal agencies to be “strip-mined and fracked for all manner of information” as a “priceless and unprecedented resource” of AI training data. To do so, DOGE operatives accessed sensitive spaces after hours, combining physical aggression with a “complete lack” of technical inhibition representing a “vampiric data suck.” Kirschenbaum identifies clear corporate interests here and further examines ideological aims. Early executive orders asserted the need for federal AI systems “free from ideological bias or engineered social agendas,” with OpenAI announcing “ChatGPT Gov” days later. These invocations of “AI” as a universal solution represent only a “linguistic token” instead of any realized technology—as worded by Salvaggio, AI must only “be considered a plausible competitor to human decision-making long enough to dislodge the existing human decision-makers.” Kirschenbaum frames this as based in the “masculine maximalism” of the Trump administration, as the term AI promotes “technological absolutism” whilst theoretically playing into the Nixon-era “theory of the unitary executive” by aiming to replace people with “void” and consolidate power into the hands of “a super-user class who will operate outside the system.” However, “the real world intrudes… with lethal downstream effects.” Kirschenbaum proposes “a collapsing superimposition of political discourse, the actual operations of social media as its primary public arena, and the technical architecture of the systems (in the form of AI)… in the sphere of governance as well as media,” which produces the “infrastructure for… permanent despotism” via the “untethering of language from conditions of lived reality.”

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Oh, Dayei, and John Downey. 2024. “Does Algorithmic Content Moderation Promote Democratic Discourse? Radical Democratic Critique of Toxic Language AI.” ''Information, Communication &amp; Society'' 28 (7): 1157–76. https://doi.org/10.1080/1369118X.2024.2346531.'''
&lt;/div&gt;

Oh and Downey critically examine how algorithmic content moderation shapes public discourse, focusing specifically on Google’s Perspective API and its detection of &quot;toxic&quot; language. By drawing a crucial distinction between incivility (harsh or emotional tone) and intolerance (actual discriminatory harm), the authors demonstrate how AI-driven moderation systems frequently misinterpret context. Consequently, these algorithms often suppress emotionally charged but politically significant speech—particularly from marginalized groups—while allowing structurally discriminatory but politely phrased content to evade detection. This dynamic reveals a significant flaw in relying on AI as a neutral mediator of digital dialogue: by prioritizing tone over substance, algorithmic moderation actively curtails democratic participation and skews the visibility of diverse perspectives. Their study is relevant for understanding how AI systems act as invisible gatekeepers, enforcing normative boundaries on public expression and highlighting the urgent need for moderation frameworks that are contextually aware, transparent, and equitable rather than merely tone-policing.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Rughiniș, Cosima, et al. 2025. “AI at the Knowledge Gates: Institutional Policies and Hybrid Configurations in Universities and Publishers.” ''Frontiers in Computer Science'' 7: 1608276. https://doi.org/10.3389/fcomp.2025.1608276. '''
&lt;/div&gt;

This article constitutes a qualitative analysis (i.e., a form of computational analysis) of 16 universities and 12 publishers that attempts to understand how these institutions regulate AI in knowledge production. Rughinis et al. claim that most institutions preserve their values while regulating AI by adapting the regulations they already have in place, stating “institutional policies are shaped by value-based compromises and not by technical concerns alone.” At the same time, although the article acknowledges its focus on institutional regulation, it also admits that “AI adoption can evolve both through policy frameworks and… locally embedded practices that remain partly invisible in formal documentation.” The authors propose two concepts, “dual black-boxing” and “legitimacy-dependent hybrid actors.” Dual black-boxing refers to the lack of transparency in both the “hidden algorithmic processes [and] invisible training data” that shape AI systems and “the opacity surrounding how academics employ AI in their work,” while legitimacy-dependent hybrid actors are “configurations of human-AI collaboration whose institutional legitimacy is not intrinsic but conditional.” Rughinis et al. argue that transparency is a core academic value, and scholars must work to open these black boxes; they also suggest that that transparency is more closely linked to academic legitimacy in AI-related issues rather than the more traditional issue of the origin of ideas. The majority of the article applies these terms to understanding the regulatory frameworks of universities and publishers, and concludes with the understanding that the majority of institutions allow some form of AI use within certain parameters. The key types of hybrid actors allowed by universities were AI-assisted researchers, AI-enabled translators, AI-enhanced writers, and AI-supported coders, while publishers facilitated the use of AI to refine language, support research methodologies, and aid in research. Ultimately, the authors observe that institutions are permitting AI-supported work in refined roles and argue that AI-based academic work gains legitimacy through transparency.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Seger, et al. “Democratising AI: Multiple Meanings, Goals, and Methods.” ''Proceedings of the 2023 AAAI/ACM Conference on AI, Ethics, and Society''. https://dl.acm.org/doi/10.1145/3600211.3604693&lt;nowiki/&gt;.'''
&lt;/div&gt;

Aiming to “provide a foundation for more productive conversations,” Seger et al. categorize four forms of “AI democratisation” and explore each form’s goals and facilitation pathways. Democratization of AI “use” involves making it easier for people to employ AI’s capabilities, and is therefore equally comparable to increasing availability of printers or of tools which can create chemical weaponry, depending on the case. Democratization of “development” involves allowing a wider range of people to contribute to the AI design and development process, which accelerates progress and increases diversity, but also opens the door for maliciousness and irresponsibility. Democratizing “profits” constitutes a philanthropic or redistributive process, and has the predictably involved weaknesses. Therefore, the authors highlight that “AI democratisation is a multifarious and sometimes conflicting concept” which “should not be conflated with improving AI accessibility” and “is not inherently good.” This is because democratization of AI’s “use,” “development,” and “profits” only derives value from its alignment with the interests and values of impacted groups, making democratization of AI’s “governance” the priority. Democratization of “governance” does not necessarily aim for total agreement amongst constituents, but will regardless reduce the unilaterality of decision-making by promoting justice, legitimacy, and diversity.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Sposato, Martin. 2025. ”Artificial Intelligence in Educational Leadership: A Comprehensive Taxonomy and Future Directions.” ''International Journal of Educational Technology in Higher Education'' 22 (20). https://doi.org/10.1186/s41239-025-00517-1. '''
&lt;/div&gt;

This article performs an analysis and review of published works on AI in educational leadership from 2017–2024 and uses the results of that process to develop what Sposato describes as “a comprehensive taxonomy of AI applications in educational leadership.” Potential readers include researchers and policy-makers interested in communicating across specific fields and disciplines. Sposato theorizes ten application domains for AI in higher education ranging from increased efficiency in administration and teaching practices to increased community engagement and strategic planning. The purpose of such a framework is to provide educational leaders with a coherent vocabulary of “the full spectrum of educational leadership responsibilities” that can facilitate further conversation. The author advocates for AI’s transformative potential in higher education even as they note important challenges (especially with ethics and equity), arguing a need for a balanced approach and “robust ethical guidelines and regulatory frameworks.” The framework provided is presented as one step toward developing AI literacy for stakeholders so that all involved in education might make more informed decisions and articulate their needs more clearly.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Ter-Minassian, Lucile. 2025. ”Democratizing AI Governance: Balancing Expertise and Public Participation.” Preprint, ''arXiv'', January 16. https://doi.org/10.48550/arXiv.2502.08651&lt;nowiki/&gt;.'''
&lt;/div&gt;

Ter-Minassian argues that “universal access, technically-constrained development, and universal impact” of AI and AI research necessitate public participation in AI governance even as it “creates a unique governance challenge.” The article presents the benefits and challenges of expert oversight and public consultation. Ter-Minassian outlines the threat of misinformation to meaningful public participation, highlighting how both undue fear and unrealistic optimism surrounding AI can affect public discourse, while acknowledging that the rapid rate of AI research makes it difficult to incorporate truly democratic processes into the decision-making process. The author concludes that any ongoing inclusive and effective AI governance ought to incorporate inclusive representation, balance expertise and public engagement, embrace transparency and accountability while engaging an iterative process, and implement a hybrid framework that “blend[s] expert knowledge with meaningful public input” (4). She argues that “AI’s deep societal impact calls for public engagement” and “technical complexity does not have to exclude meaningful public input,” advocating for “structured deliberation and phased public participation” to address “time-sensitive AI challenges without compromising democratic legitimacy” (5). Ultimately, the article sees this as an iterative process that will need to continue to adapt in order to maintain expert insight and public discourse on AI.

== Critical Literacies ==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Aguiar, Micaela, and Sílvia Araújo. 2024. “Final Thoughts: Digital Humanities Looking at Generative AI.” ''In Digital Humanities Looking at the World'', edited by S. Araújo et al., 367–380. Cham: Springer Nature Switzerland.'''
&lt;/div&gt;

Aguiar and Araújo explore the emergence and applications of generative artificial intelligence within Digital Humanities research. They trace the evolution of generative AI from early implementations like the 1960s Eliza chatbot through its developments such as Generative Adversarial Networks (GANs) and the Transformer architecture to contemporary large language models like BERT and GPT. The authors document current applications of generative AI across Digital Humanities domains, including cultural heritage preservation, historical text processing, and literary creation. They outline how these technologies are being used to memorialize mass atrocities, process traditional Chinese ancient texts, and explore collaborative human-AI poetry creation. Aguiar and Araújo examine the inner workings of generative AI, particularly focusing on how conversational models function through statistical prediction rather than genuine comprehension. They identify limitations such as hallucinations, bias replication, and attribution problems that researchers must consider when using these tools. The chapter concludes that effective integration of generative AI in Digital Humanities requires developing AI literacy skills that enable researchers to critically evaluate outputs while leveraging the technology's capabilities for sustainable research advancement.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Boer, Victor de, and Lise Stork. 2024. “Hybrid Intelligence for Digital Humanities.” Preprint, ''arXiv'', April 15. https://doi.org/10.48550/ARXIV.2406.15374. '''
&lt;/div&gt;

De Boer and Stork believe the discipline of Digital Humanities (DH) should meet the challenges and opportunities posed by Artificial Intelligence (AI) by adopting the “human-centric paradigm” of Hybrid Intelligence (HI). They define DH as “a scholarly realm where computing or digital technologies intersect with… the humanities… characterized by innovative approaches to scholarly endeavors,” and identify various existing DH approaches to AI, which include “Knowledge Representation,” “Machine Learning,” “Natural Language Processing,” and “Computer Vision.” De Boer and Stork argue successfully integrating AI tools into DH requires embedding AI in scholarly practice, adopting a diverse and polyvocal approach, considering the debate of distant versus close reading, and applying a critical stance toward data, methods, and tools. HI “concerns itself with the investigation and design of human-AI ecosystems,” and the authors argue effective AI should be developed by following its “CARE” principles—being “Collaborative, Adaptive, Responsible, and Explainable.” Therefore, De Boer and Stork focus this text on mapping CARE principles to those DH requirements earlier outlined. Overall, they concur with Goodlad and Baker that humanists “are ideal 'domain experts' for the current juncture,” and end by identifying two overarching challenges. The first challenge is “one-shot solutions,” including tools, datasets, and methods that aren’t reusable, Open Source, accessible, and well described. Secondly, they identify the human factor—actors will need both an open mind and AI literacy to be equally critical of and cooperative with AI. Therefore, the authors emphasize the importance of teaching digital methods within the humanities curricula.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Carmi, Elinor, Simeon J. Yates, Eleanor Lockley, and Alicja Pawluczuk. 2020. “Data Citizenship: Rethinking Data Literacy in the Age of Disinformation, Misinformation, and Malinformation.” ''Internet Policy Review'' 9 (2). https://doi.org/10.14763/2020.2.1481.'''
&lt;/div&gt;

This study argues that dominant understandings of digital and data literacy are insufficient for addressing contemporary complex challenges of disinformation, misinformation, and malinformation. They propose the concept of data citizenship to reframe literacy as a fundamentally civic, political, and collective practice rather than a set of individual technical skills. The authors contend that information disorders cannot be addressed through technological solutions alone, as they are deeply embedded in structural inequalities, platform economies, and power asymmetries shaping datafied societies. The article builds on a literature review and secondary data analysis drawing on Me and My Big Data project, alongside the development of a nationally representative UK survey. The authors identify three major gaps in existing literacy frameworks: an overemphasis on individual competence rather than networked practices, a lack of critical engagement with algorithmic and economic infrastructures of platforms, and the absence of proactive civic skills such as contesting data extraction, demanding transparency, and advocating for data justice. Their analysis highlights how citizens’ data practices are shaped by social networks, education, and socio-economic conditions, revealing unequal capacities for verification, protection, and collective action. The authors conclude that data literacy must move beyond content verification to include critical understanding of platform design, funding models, and algorithmic governance. They emphasize the importance of locally grounded, participatory approaches to data literacy education that reflect diverse lived contexts rather than scalable, top-down interventions. While the study offers a robust conceptual model and survey-based insights, it does not yet include in-depth qualitative engagement with citizen groups, which the authors position as a necessary next phase of research. Overall, the article makes a significant contribution by bridging digital literacy and the field of mis/dis/mal information research and claims that data literacy is an essential component of democratic citizenship.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Long, Duri, and Brian Magerko. 2020. “What is AI Literacy? Competencies and Design Considerations.” In ''Proceedings of the 2020 CHI Conference on Human Factors in Computing Systems'', 1–13. New York, NY: Association for Computing Machinery. https://doi.org/10.1145/3313831.3376727.'''
&lt;/div&gt;

The authors present an exploratory review of interdisciplinary literature, aiming to organize key ideas on AI literacy definitions and essential competencies. Authors claim that public misunderstandings of AI are due to design, educational gaps, black-box algorithms, and a general lack of technological knowledge. The review includes two sections: how the public understands specific AI systems, and how existing research addresses people’s broader understanding of AI. Rather than offering an exhaustive synthesis, Long and Magerko’s focus is on non-technical audiences and they offer central provocations and design principles that can inform educational interventions. The proposed conceptual framework on AI literacy identifies 17 core competencies alongside 14 design considerations for educational intervention, which are described and supported by relevant literature. Together, these considerations position the framework as a practical and reflective tool for designing AI literacy interventions that move beyond dominant media narratives and foster critical, informed engagement with AI technologies.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Majdik, Zoltan P., and S. Scott Graham. 2024. “Rhetoric of/with AI: An Introduction.” ''Rhetoric Society Quarterly'' 54 (3): 222–31. https://doi.org/10.1080/02773945.2024.2343264. '''
&lt;/div&gt;

Majdik and Graham propose a field-organizing distinction that functions as a methodological argument. By splitting inquiry into “rhetoric of AI” (AI as object) and “rhetoric with AI” (AI as method), they treat AI simultaneously as a rhetorical actor/ecosystem component that structures attention, circulation, and uptake, and as an instrument that can be enrolled into rhetorical research workflows. The authors claim that much prior rhetorical work engaged “spaces of AI”—platforms, devices, and algorithmically mediated environments—while leaving “AI” itself undertheorized as the central object; this provides a justification for why rhetoricians should now foreground model/algorithmic operations (and their harms) rather than treating them as neutral background conditions of digital rhetoric. They also frame generative text systems as a stress test for core rhetorical concepts—agency, authorship, and audience—because these systems destabilize the presumed linkage between human intention and textual production, and because they insert nonhuman intermediaries into communicative situations that education and public discourse still normatively treat as human-to-human. The introduction then uses this distinction to stage the special issue’s contributions as complementary routes for rebuilding rhetorical theory and pedagogy under AI conditions.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Ng, Davy Tsz Kit, Jac Ka Lok Leung, Samuel Kai Wah Chu, and Maggie Shen Qiao. 2021. “Conceptualizing AI Literacy: An Exploratory Review.” ''Computers and Education: Artificial Intelligence'' 2: 100041. https://doi.org/10.1016/j.caeai.2021.100041. '''
&lt;/div&gt;

This article presents an exploratory review of literature published between 2016 and 2021 with the goal of conceptualizing AI literacy and proposing a comprehensive framework for teaching and evaluating it. The authors analyze 30 articles and synthesize existing definitions and approaches to AI literacy, noting that while AI literacy has increasingly been discussed, the concept has often been treated narrowly as a technical skill set. The authors situate AI literacy as a necessary competency for everyone, arguing that AI will increasingly affect many aspects of daily life and employment. In response, the authors argue for a broader understanding of AI literacy that incorporates cognitive and ethical dimensions. The proposed framework organizes AI literacy into four interconnected facets: knowing and understanding AI, using and applying AI, evaluating and creating AI, and AI ethics. Importantly, the authors explicitly reject purely instrumentalist views of AI literacy. To conceptualize AI literacy pedagogically, the authors draw on Bloom’s classic taxonomy, aligning the above-mentioned aspect with increasing cognitive levels. They claim that while most people are aware that AI exists, they often lack understanding of how it works or how to assess its ethical and social implications. This approach positions AI literacy as a developmental learning process rather than a static set of skills. The article concludes by identifying directions for future research, including the need for empirical studies to validate AI literacy frameworks and to better understand how AI literacy can be taught, learned, and assessed across educational contexts.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Rapanta, Chrysi, Anna Åkerfeldt, Mark Vanderbeeken, Diane Lison, Khadija Mohammed, Amanda Gibbs, Helder Coelho, Pinar Seda Celik, Carola Bruna, Ingrid Helleve, Chrysoula Vassilakopoulou, Pieter Swart, Ana Lúcia Marques, and Dirk Ifenthaler. 2025. “Critical GenAI Literacy: Postdigital Configurations.” ''Postdigital Science and Education'' 17 (1): 167–199. https://doi.org/10.1007/s42438-025-00573-w.'''
&lt;/div&gt;

Rapanta et al. develop a comprehensive and pluralistic account of what critical literacy means in the context of generative artificial intelligence. Drawing on contributions from fourteen scholars, the article argues that GenAI literacy cannot be captured through a single, universal framework. Instead, it must be understood as a set of context-dependent literacies shaped by disciplinary traditions, socio-political conditions, and evolving human–algorithm relations. This postdigital perspective challenges narrow definitions of AI literacy that prioritize technical skills. The authors’ central claim is that current GenAI systems, particularly large language models, require critical engagement because of their epistemic limitations, including reliance on dominant narratives, lack of explainability, tendencies toward fabrication, and reinforcement of Western and anglophone knowledge structures. As a result, critical GenAI literacy is positioned as a social justice concern rather than a neutral competency. Learners and educators are encouraged to examine questions of authorship, agency, and power, such as whose labour and data underpin these systems and which perspectives are marginalized or erased. Methodologically, the article adopts a dialogic and collective approach to resist homogenizing AI epistemologies and to foreground plurality in postdigital research. The authors conceptualize GenAI as part of a co-constructive assemblage in which human and non-human agencies interact, while maintaining that ethical responsibility and evaluative judgment must remain human-led, organizing four interrelated dimensions: epistemology and ontology, agency, engagement, and ethics and justice; each emphasizing critical interrogation, active participation, and accountability. Overall, the paper provides a theoretically grounded yet pragmatic foundation for advancing critical GenAI literacy in education and research.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Veldhuis, Annemiek M., Phoebe W. K. Lo, Iain E. G. Kenny, and Alissa N. Antle. 2024. “Critical Artificial Intelligence literacy: A scoping review and framework synthesis.” ''International Journal of Child-Computer Interaction'' 43: 100708. https://doi.org/10.1016/j.ijcci.2024.100708&lt;nowiki/&gt;.'''
&lt;/div&gt;

Veldhuis and colleagues present a review of literature and framework synthesis that conceptualizes critical AI literacy from a child–computer interaction (CCI) perspective. Reviewing 30 empirical studies published over the past decade, the authors aim to understand how children and youth aged 5–18 have been supported in developing critical literacy on AI technologies, particularly regarding their social, political, cultural, and ethical implications. Grounded in critical literacy theory, the authors integrate Lewison et al.’s (2002) four interrelated dimensions including disrupting the commonplace, considering multiple viewpoints, focusing on the sociopolitical, and taking action into a four-part framework for critical AI literacy. Importantly, the framework rejects deficit narratives by foregrounding children’s capacity for critical inquiry and demonstrates that even young learners can meaningfully engage with complex issues such as algorithmic bias, data provenance, privacy, accountability, and the distinction between AI-generated outputs and human creativity when supported by pedagogies such as critical making. Only peer-reviewed, English-language empirical studies with explicit support for children’s critical engagement with AI were included. The findings reveal a growing body of research, particularly in the past three years, exploring activities that promote youths’ critical reflection on AI’s societal and ethical impacts. These activities address concerns related to privacy, surveillance, employment, diversity in the computing workforce, algorithmic bias, and accountability. The resulting framework emphasizes learners’ capacity to analyze both AI artifacts and the sociotechnical systems that produce them, as well as to reflect on how AI shapes cultural, societal, and political structures and personal experiences. For future research recommendations, the authors emphasize the urgency of ongoing critical AI literacy practices in areas of youth emotional awareness and socio-cultural impacts in response to the fast evolution of generative AI systems. 

== Globalism, Colonialism, and Influence ==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Arora, Payal. 2024. “Creative data justice: a decolonial and indigenous framework to assess creativity and artificial intelligence.” ''Information, Communication &amp; Society'' 28 (13): 2231–47. https://doi.org/10.1080/1369118x.2024.2420041&lt;nowiki/&gt;.'''
&lt;/div&gt;

Arora (2024) develops a framework of creative data justice that includes decolonial theory, Indigenous perspectives, and critical studies of creativity to explore how generative AI could impact creative labour, rights, and cultural value. The author argues that democratizing creativity requires a cross-cultural framework that considers power relations between creative work, data, and learning, particularly by centring the lived realities of underrepresented communities in the Global South. Rather than treating AI creativity as neutral, the paper claims that inclusive AI systems must address contextual inequalities and the unequal impacts of AI on diverse creative communities. Arora critiques dominant Western-centred scholarship and challenges concepts such as the “creative class,” arguing that creativity exists across everyday social and cultural practices. The paper also critiques Creative Commons (CC) frameworks, suggesting that while they promote openness, they may enable commercial data extraction by AI companies. Instead, the author argues for dataset curation developed with Indigenous artists and activist groups to ensure equitable representation. The article further highlights the often-invisible labour behind creative AI located in the Global South and argues that a decolonial approach must recognize both material infrastructures and power relations shaping creative work. Indigenous approaches to communal ownership and systems of care are presented as alternatives to Western individualistic models of creative rights. The author advocates combining ethnographic “thick data” with computational approaches and suggests action-research methods such as counter-mapping, dataset debiasing, and critical media literacies. The paper concludes that creative data justice offers a framework for building culturally diverse and equitable AI systems that respect community agency and support a more democratic global data economy.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Fırıncı, Yusuf. 2024. “Decolonial Artificial Intelligence; Algorithmic Fairness in Alignment with Turkish and Islamic Values.” ''Marmara Üniversitesi İlahiyat Fakültesi Dergisi'' 67 (67): 250–279. https://doi.org/10.15370/maruifd.1565884&lt;nowiki/&gt;.'''
&lt;/div&gt;

Fırıncı argues that artificial intelligence development should be guided by explicitly value-based frameworks grounded in Turkish-Islamic ethical traditions rather than relying solely on dominant Western models of technological governance. The authors emphasize that AI systems rely on human judgment and are inherently value-laden, making ethical alignment essential to prevent manipulation, misinformation, algorithmic bias, and forms of digital coloniality. Drawing on concepts such as big data, “thick data,” and digital anthropology, the paper suggests combining quantitative data analysis with culturally grounded social knowledge to design algorithms that reflect community values. The paper examines tensions between Western liberal individualism (which underpins most AI fairness metrics) and Islamic ethical frameworks that emphasize communal welfare, divine justice, and context-dependent moral reasoning. This analysis reveals that &quot;fairness&quot; is not a universal technical specification, but a deeply value-laden concept shaped by particular cultural, religious, and philosophical commitments—meaning that AI systems designed around Western fairness assumptions may be experienced as unjust in contexts operating from different ethical frameworks. Using Social Construction of Technology theory and critical social constructivism, the authors argue that existing global AI frameworks often reproduce hierarchy, bias, and external control, which they interpret as forms of algorithmic oppression. In response, they advocate a “fairness in alignment with values” approach grounded in Turkish-Islamic worldviews, supported by Islamic ethical principles as foundations for responsible technological development. The paper concludes by calling for locally controlled data infrastructures, culturally aligned AI systems, and knowledge production rooted in Turkish and Islamic values as part of a broader decolonial technological model aimed at protecting communities from AI-related harms and preserving social cohesion.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Mohamed, Shakir, Marie-Therese Png, and William Isaac. 2020. “Decolonial AI: Decolonial Theory as Sociotechnical Foresight in Artificial Intelligence.” ''Philosophy &amp; Technology'' 33 (4): 659–84. https://doi.org/10.1007/s13347-020-00405-8. '''
&lt;/div&gt;

Mohamed et al. explore the role of post-colonial and decolonial critical science in understanding the transformative technological advance of AI. They argue risks to vulnerable peoples can be minimized by linking ethical principles to scientific progress, and therefore consider AI’s embedded values, approaching it as &quot;both object and subject.&quot; They demonstrate that AI advances &quot;encompass ever-larger aspects of the cultural, economic and political life of modern society&quot; by citing Obermeyer et al.’s reveal of racial biases within an algorithm commonly used by healthcare, arguing this indicates how AI obscures and exacerbates asymmetrical power relations. Mohamed et al. identify neglect to address systemic racism as the cause, illustrating that patterns of power between colonizer and colonized survived territorial decolonization to propagate a historically continuous &quot;coloniality of power.&quot; Therefore, &quot;dynamic and robust foresight tactics and methodologies grounded in the critical sciences&quot; (like, for example, a &quot;lens of metropole and periphery&quot;) should be applied to the field of AI to ensure one’s view is &quot;decentring,&quot; &quot;additive-inclusive,&quot; and prioritizes &quot;engagement.&quot; The authors further explore emergent theories of data colonialism within their assessment of &quot;algorithmic coloniality.&quot; This involves their taxonomy of &quot;decolonial foresight&quot; (constituting algorithmic &quot;oppression,&quot; &quot;exploitation,&quot; and &quot;dispossession&quot;), and an exploration of various &quot;sites of coloniality&quot; (including &quot;algorithmic decision systems,&quot; &quot;ghost workers,&quot; &quot;beta-testing,&quot; &quot;national policies,&quot; and &quot;international social development&quot;). They argue this study highlights the disjunction of empirical observations with the current, theoretical, and ahistorical frameworks of power in AI. This leads the authors to outline a set of tactics to develop &quot;decolonial AI&quot; possessing a strengthened empirical basis and an avoidance of algorithmic colonialism. Such tactics are &quot;based on lessons of resistance and recovery from historical and decolonial criticism and grounded within already existing work&quot;; they include critical technical practice, seeking reverse tutelage and pedagogies, and renewing affective political communities. Mohamed et al. emphasize that those ethical principles which form the &quot;social contract&quot; must consider diverse viewpoints, and that new methodologies must be developed to promote &quot;inclusive dialogue&quot; within new research cultures.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Muldoon, James, and Boxi A. Wu. 2023. “Artificial Intelligence in the Colonial Matrix of Power.” ''Philosophy &amp; Technology'' 36 (4). https://doi.org/10.1007/s13347-023-00687-8&lt;nowiki/&gt;.'''
&lt;/div&gt;

Muldoon and Wu (2023) extend decolonial AI scholarship by situating contemporary artificial intelligence within what Aníbal Quijano terms the “colonial matrix of power,” and arguing that from data to production machine learning systems are structured to endure colonial logics that organize economic extraction, labour hierarchies, and epistemic dominance. Central to their framework is the “colonial matrix of power,” which names an organizing principle of domination across interrelated domains: economic control (labour and resources), authority, gender and sexuality, and the control of subjectivity and knowledge. Authors focus particularly on economic extraction and epistemic domination, drawing on the modernity/coloniality research program. They proceed with three interconnected claims: “colonial supply chain of AI,”  “international division of digital labour,” and “hegemonic knowledge production,” demonstrating how AI development relies on largely invisible labour and mineral resources of majority-world communities to generate wealth for Western economies. Beyond material extraction, the authors contend that AI reproduces hegemonic Western epistemologies by presenting its systems as universal, objective, and rational, thereby marginalizing non-Western knowledge systems. This study challenges dominant narratives that present AI as environmentally sustainable or socially progressive, arguing that from mineral extraction to energy-intensive computation, the ecological and material burdens fall disproportionately on majority-world nations, while the economic and technological benefits accrue to wealthy Western nations. They conclude by emphasizing that coloniality is not merely an object of study but a framework for unsettling Western-centric modes of knowing.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Salami, Aishat Oyenike. 2024. “Artificial intelligence, digital colonialism, and the implications for Africa's future development.” ''Data &amp; Policy'' 6. https://doi.org/10.1017/dap.2024.75. '''
&lt;/div&gt;

Salami (2024) studies how artificial intelligence operates within broader dynamics of digital colonialism in Africa, arguing that AI risks reinforcing patterns of colonialism, unless African actors gain greater agency in digital governance. The article begins by clarifying key concepts like AI, digital colonialism, neocolonialism, and data exploitation. Salami identifies several manifestations of digital colonialism on the continent: foreign ownership of critical digital infrastructure, unequal data flows in which African user data is extracted and monetized abroad, and algorithmic systems that enable forms of economic exploitation. Through examples such as ride-hailing platforms and outsourced digital labour, the article demonstrates how algorithmic control can generate precarious working conditions while concentrating profit outside the continent. Beyond labour concerns, Salami highlights how data extraction contributes to a digital wealth transfer, deepening economic imbalances and undermining local innovation and national sovereignty. While acknowledging the potential benefits of AI for development, the article adopts a cautious stance, emphasizing that Africa’s digital future depends on strengthening regulatory frameworks, expanding infrastructure, investing in education and research, and prioritizing data sovereignty. 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Varshney, Kush R. 2024. “Decolonial AI Alignment: Openness, Visesa-Dharma, and Including Excluded Knowledges.” ''Proceedings of the AAAI/ACM Conference on AI, Ethics, and Society'' 7: 1467-1481. https://doi.org/10.1609/aies.v7i1.3173&lt;nowiki/&gt;.'''
&lt;/div&gt;

Varshney discusses AI alignment through a decolonial lens, arguing that current large language model (LLM) alignment practices reproduce forms of coloniality by embedding Western moral philosophy as universal. The author conceptualizes alignment as the post-training processes used to shape model behaviour and argues that the term often functions as an “empty signifier,” masking whose values are being encoded and enforced. The author contrasts open and closed LLM models, arguing that while openness may allow value to circulate more equitably among developers and communities, closed models concentrate value in extractive ways that reflect colonial dynamics, and views them as contemporary “metropoles” that accumulate power through extractive and epistemic control. Building on existing research on colonial AI, the article adds “ethical essentialism” (or moral absolutism) as a new form of coloniality, arguing that AI systems often treat Western moral frameworks as universal, which marginalizes other ethical traditions and reinforces a coloniality of knowledge. Varshney also identifies three specific aspects of coloniality in AI alignment: closed proprietary delivery of models, reliance on Western ethical theories as default, and technological designs that limit how values can be expressed. As an alternative, Varshney proposes a decolonial approach grounded in openness understood not only technically but epistemically: openness to research artifacts, openness to society, and openness to excluded knowledges. The author suggests that alignment should allow communities to adapt models according to local contexts rather than imposing universal rules. Drawing from Hindu moral philosophy, particularly the concept of viśeṣa-dharma (context-dependent ethics), the paper argues for pluralistic, relational value systems that recognize moral diversity instead of universal moral commands. The conclusion calls for a reconceptualization of AI alignment that moves away from moral absolutism toward context-sensitive, community-driven frameworks, positioning openness as a pathway to dismantling the colonial power structures embedded in contemporary AI systems.

== Diversity, Determinism, Bias, and Justice ==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Al-kfairy, Mousa , Dheya Mustafa, Nir Kshetri, Mazen Insiew, and Omar Alfandi. 2024. “Ethical Challenges and Solutions of Generative AI: An Interdisciplinary Perspective.” ''Informatics'' 11 (3): 58. https://doi.org/10.3390/informatics11030058'''
&lt;/div&gt;

Al-kfairy et al. (2024) provide a comprehensive synthesis of the ethical vulnerabilities introduced by generative AI, utilizing an interdisciplinary review of 37 studies across healthcare, education, and media. Rather than treating ethical breaches as isolated technical flaws, the authors demonstrate how generative models systematically threaten privacy, intellectual property, and social equity across diverse domains. For instance, they highlight the paradox in healthcare where synthetic patient data—often intended to protect privacy—still carries significant risks of re-identification. Similarly, the authors trace how AI's capacity to mimic copyrighted works and generate synthetic media exacerbates both misinformation and algorithmic bias, particularly by perpetuating racial and gender stereotypes in high-stakes environments like hiring and education. Moving beyond mere critique, the article advocates for a proactive, cross-sectoral governance framework. The authors argue that mitigating these risks requires more than algorithmic adjustments; it demands multidisciplinary collaboration, robust institutional integrity policies, and targeted AI literacy programs. Ultimately, Al-kfairy et al. frame the ethical deployment of generative AI as a complex sociotechnical challenge that requires continuous, structured dialogue among technologists, ethicists, and policy-makers to ensure transparency and fairness.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Alvarez, Jose M, Alejandra Bringas Colmenarejo, Alaa Elobaid, Simone Fabbrizzi, Miriam Fahimi, Antonio Ferrara, Siamak Ghodsi, et al. 2024. “Policy Advice and Best Practices on Bias and Fairness in AI.” ''Ethics and Information Technology'' 26 (2). https://doi.org/10.1007/s10676-024-09746-w. '''
&lt;/div&gt;

This article attempts to provide “an up-to-date entry-point to the state-of-the-art of the multidisciplinary research on bias and fairness in AI” before providing its own suggestions for policy and best practices based on the outcomes of the NoBIAS—Artificial Intelligence without Bias—project. The authors describe fairness in AI as the pursuit to design “methods for detecting, mitigating, and controlling biases in AI-supported decision making,” and they outline different ways that bias can find its way into AI applications as part of training data (pre-existing bias), design (technical bias), and organizational processes (emerging bias). The article critiques the reduction of bias evaluation to simple metrics and advocates for serious engagement with the issue. The authors detail the various components of the collaborative NoBIAS project as part of its research goal to understand, mitigate, and account for bias in AI data and systems, especially within an EU legal context. They perform a survey and discuss various fairness metrics and how choosing the proper method is crucial for “optimizing AI models.” They also engage with an argument that, although AI is biased, it is less biased than humans, making the claim that AI usage is often accompanied by a false sense of objectivity. The article also investigates core issues at the heart of AI’s biases, such as the assumption that a “ground truth”—the answer to the problem the AI is being asked to solve—is actually encoded within the data. While the article makes many suggestions for how to curb bias within AI, prominent design decisions include human-centric AI and “Multi-stakeholder participatory design.”

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Gallegos, Isabel O., Ryan A. Rossi, Joe Barrow, Md Mehrab Tanjim, Sungchul Kim, Franck Dernoncourt, Tong Yu, Ruiyi Zhang, and Nesreen K. Ahmed. 2024. “Bias and Fairness in Large Language Models: A Survey.” ''Computational Linguistics'' 50 (3): 1097–1179. https://doi.org/10.1162/coli_a_00524&lt;nowiki/&gt;.'''
&lt;/div&gt;

Gallegos et al. perform an “extensive and comprehensive survey of bias and fairness in NLP” that considers both the evaluation and mitigation of bias, then propose three taxonomies for bias evaluation and mitigation. The survey disambiguates different types of social harms that stem from LLMs with the “aim to enhance understanding of the range of bias issues, their harms, and their relationships to each other.” The authors discuss the issue of defining bias in LLMs and note that “many approaches… assume some implicitly desirable criterion… but do not explicitly acknowledge or state the normative social values that justify their framework.” Instead, Gallegos et al. draw attention to “who is harmed, why the behaviour is harmful, and how the harm reflects and reinforces social principles or hierarchies,” trying to bring context and insight to the understanding and function of bias and bias mitigation in LLMs. The article defines terms at every stage of the life cycle of an LLM, looking at issues of bias and fairness in the development, deployment, and training data, of an LLM, for example. The article concludes with four core recommendations: “Avoid flattening power imbalances”; “Choose objective functions that align with fairness desiderata”; “Balance bias mitigation with output diversity”; and “Preserve important contexts in output rewriting.” The authors also acknowledge problems and challenges, including addressing power imbalances, an issue that we can mitigate by centring marginalized communities, developing participatory research designs, shifting values and assumptions, and expanding language resources. They likewise propose methods for curbing problems with conceptualizing fairness for NLP, refining evaluation principles, and improving mitigation efforts. Ultimately, the authors admit that many of these technical issues are the result of societal issues, and that “technical solutions are incomplete without broader societal action against power hierarchies that diminish and dominate marginalized groups.” In short, technical solutions will only take us so far.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Hertweck, Corinna, Joachim Baumann, Michele Loi, Eleonora Viganò, and Christoph Heitz. 2022. “A Justice-Based Framework for the Analysis of Algorithmic Fairness-Utility Trade-Offs.” Preprint, ''arXiv'', June 6. https://arxiv.org/abs/2206.02891.'''
&lt;/div&gt;

Hertwick et al. propose “a framework for eliciting and implementing moral values relevant to the choice of a fairness goal achievable by prediction-based decision-making.” In a system that assumes binary decision-making processes (e.g., assigning a probability score to whether an individual with pay a loan), the authors use their framework to evaluate the utility of those decisions (and the system that makes them) for different groups of people and the fairness related to that outcome. Citing Wong, the article argues that such prediction-based decision-making systems are value-laden, that this makes them inherently political, and therefore they ought to be transparent and democratized. The authors use 6 value-laden questions to make their evaluations: the first question provides a score of utility for those making the decision; questions 2–5 help “define a morally appropriate fairness criterion and a score that expresses to what degree it is fulfilled”; and the last question asks “how strongly should fairness be pursued if it comes into conflict with the utility of the decision maker?” to judge whether the outcome is an appropriate trade-off.

The authors argue for a utility-based evaluation of fairness, determining the value of decisions based on their outcome, looking at the harm and benefit to given stakeholders. In determining patterns of justice, they define four patterns meant to distribute utility differently—Egalitarianism, Maximin, Prioritarianism, and Sufficientarianism. The article concludes “more work needs to be done to deliver a practical empirical methodology to elicit the relevant value-laden choices from stakeholders,” and with a call to incorporate ethical considerations and evaluations into automated decision-making processes.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Kay, Jackie, Atoosa Kasirzadeh, and Shakir Mohamed. 2024. “Epistemic Injustice in Generative AI.” Preprint, ''arXiv'', August 21. https://doi.org/10.48550/arXiv.2408.11441&lt;nowiki/&gt;.'''
&lt;/div&gt;

Kay, Kasirzadeh, and Mohamed “develop an account of generative algorithmic epistemic injustice by building upon a conventional philosophical understanding of epistemic injustice.” The authors see the former as a subset of the latter, with generative algorithmic epistemic injustice entailing identity-based prejudice that hinders expression for marginalized people while ultimately “impair[ing] knowledge formation capabilities of all individuals” within the ecosystem of GenAI applications. Rather than focusing on decision-making and classification applications, this article seeks to characterize the broader varieties of generative epistemic injustice within GenAI systems. Kay, Kasirzadeh, and Mohamed theorize four configurations of generative epistemic injustice: “amplified injustice,” which constitutes AI’s reproduction and magnification of “socially biased viewpoints from its training data”; “manipulative testimonial injustice,” when users employ AI to “intentionally… fabricate falsehoods, discrediting individuals or marginalized groups”; “hermeneutical ignorance,” where GenAI misrepresents or erases marginalized groups “due to a lack of contextual or cultural understanding”; and “access injustice,” where GenAI facilitates the unequal access to information and/or knowledge. The article concludes with proposals for how to create epistemic justice through GenAI, developing mitigation strategies that combat all four of the sub-configurations the authors theorize. Epistemic justice in GenAI can take the form of interrogating system design, identifying “testimonial injustices,” and, potentially, using AI to unlock cultural knowledge that “help[s] articulate experiences that are otherwise ineffable.” The authors end by proposing that the same processes that embed injustice can be re-engineered to embody justice and “orient our knowledge systems towards equity and fairness for all.”

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Klein, L., &amp; D'Ignazio, C. 2024. “Data feminism for AI.” In ''Proceedings of the 2024 ACM Conference on Fairness, Accountability, and Transparency'', 100–112. https://doi.org/10.1145/3630106.3658543. '''
&lt;/div&gt;

Klein and D'Ignazio (2024) adapt their foundational concept of &quot;data feminism&quot; to address the specific ethical, social, and ecological challenges posed by artificial intelligence. Building on the seven intersectional feminist principles introduced in their 2020 book, the authors reinterpret these guidelines to critique the power imbalances, systemic inequalities, and exploitative labour practices inherent in contemporary AI development. To account for the rapidly expanding footprint of generative AI, they introduce two new principles focused on environmental impact and meaningful consent. Specifically, the authors connect the massive ecological costs of AI to historical patterns of racial capitalism and colonialism, highlighting how these environmental and social harms are disproportionately distributed. Ultimately, Klein and D'Ignazio call for a radical reevaluation of dominant, profit-driven AI practices, offering this expanded feminist framework as a practical tool to mitigate harm, challenge corporate monopolies, and foster a more democratic and equitable technological landscape.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Prescott, Andrew. 2023. “Bias in Big Data, Machine Learning and AI: What Lessons for the Digital Humanities?” ''Digital Humanities Quarterly'' 17 (2). https://www.proquest.com/scholarly-journals/bias-big-data-machine-learning-ai-what-lessons/docview/2842908427/se-2.'''
&lt;/div&gt;

Prescott examines how race and gender bias arise in projects using predictive analytics, big data, and AI, and how algorithmic bias could be considered a major socio-cultural humanity crisis. However “predictive analytics” have been helpful in civic services in the US, in many cases they have led to perpetuating existing inequalities. The role of Digital Humanities in contributing more ethical approaches to AI and reshaping ubiquitous “digital modern” cultures is emphasized. He challenges the myths surrounding data-driven methods and argues that the demand for “explainability” is the key tool in combating algorithmic bias. He also suggests that Digital Humanities are particularly well-positioned to contribute to advancing AI explainability. However, much of AI development takes place in the commercial sector, where companies often refuse to disclose their proprietary algorithms. The article concludes with a ten-principle action plan outlining guidelines for the responsible use of AI as a manifesto for Digital Humanities practitioners.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Shams, Rifat Ara, Didar Zowghi, and Muneera Bano. 2023. “AI and the Quest for Diversity and Inclusion: A Systematic Literature Review.” ''AI and Ethics'' 3 (4): 1427–1453. https://doi.org/10.1007/s43681-023-00362-w. '''
&lt;/div&gt;

Shams, Zowghi, and Bano perform a systematic literature review (SLR) that uses both quantitative and qualitative methods to engage with topics of artificial intelligence and diversity and inclusion. The authors make a distinction between Diversity and Inclusion in AI (D&amp;I in AI) and AI for Diversity and Inclusion (AI for D&amp;I), with the former being research literature focused on improving AI systems with respect to those issues, and the latter as the use of AI to improve diversity and inclusion in other domains. Two primary research questions drive the SLR: What challenges and solutions are found in the literature about D&amp;I in AI and in the literature about the applications of AI for D&amp;I? The survey finds that AI for D&amp;I is an underserved area of research, and those articles that address D&amp;I in AI are more likely to acknowledge challenges than to propose or theorize solutions. Articles that do propose solutions for D&amp;I in AI often lack empirical studies or real-world application to support them. The article concludes by noting that issues of governance are underserved; gender, health, and facial analysis are the topics most discussed (issues of race, language, and religion are discussed less). For next steps, the authors intend to develop a “risk-based framework for practitioners… that would incorporate a risk assessment checklist and context-specific recommendations for tackling the related issues at different stages of the AI development lifecycle.” 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Starke, Christopher, Janine Baleis, Birte Keller, and Frank Marcinkowski. 2022. “Fairness Perceptions of Algorithmic Decision-Making: A Systematic Review of the Empirical Literature.” ''Big Data &amp; Society'' 9 (2): 1–35. https://doi.org/10.1177/20539517221115189&lt;nowiki/&gt;.'''
&lt;/div&gt;

This article provides a comprehensive, systematic literature review on the topic of empirical literature surrounding algorithmic decision-making (ADM). Starke, Baleis, Keller, and Marcinkowski begin by acknowledging that ADM can streamline and improve decisions even as it has the potential to “systematically reinforce racial or gender stereotypes, marginalize minorities, or flat-out denigrate certain members of society.&quot; The authors advocate for a “society-in-the-loop approach,” but propose that this requires a “thorough empirical understanding of when and why citizens perceive ADM to be (un)fair.” The systematic review “synthesizes the results of 58 empirical studies” and “over 33,000 unique observations of citizens’ fairness perceptions of ADM,” and “systemize the literature along four main dimensions of perceived algorithmic fairness.” Despite the size of the review and its unique approach in capturing “perceptions of algorithmic fairness,” the authors also acknowledge the limitations of the study: it only looks at English works and published research, and the initial search strings only looked at titles and subtitles of a given work. They also acknowledge their disciplinary bias as social scientists reading the studies through a social sciences lens (10). The results of the survey suggest that “perceived fairness of ADM systems is highly context-dependent” and it is not only technical design but also the area of application and task in question that affect perceived fairness, and the subjects, domains, and tasks explored in these studies require more diversity, as WEIRD (white, educated, industrialized, rich, democratic) people, and criminal justice and HR tasks make up the majority of empirical research. The authors “call for more research from non-Western contexts, along with more theoretical and methodological groundwork to harmonize concepts and measurements of algorithmic fairness perceptions,” as well as a society-in-the-loop framework.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Tonia Sutherland, Marika Cifor, T. L. Cowan, Jas Rault, and Patricia Garcia. 2023. “The Feminist Data Manifest-NO: An Introduction and Four Reflections.” In ''Debates in the Digital Humanities'', edited by Lauren F. Klein and  Matthew K. Gold. Minneapolis, MN: University of Minnesota Press. https://dhdebates.gc.cuny.edu/read/debates-in-the-digital-humanities-2023/section/16184c7d-eee1-40b2-a168-960d4c4035c4. '''
&lt;/div&gt;

Sutherland et al. (2023) introduce the &quot;Feminist Data Manifest-No,&quot; a declaration of refusals and commitments for feminist data studies grounded in Latinx, Black, queer, trans, and Indigenous feminist perspectives. Through an introduction and four distinct reflections, the chapter explores how the manifesto’s principles can be used to challenge the settler-colonial and patriarchal logics of data generation, collection, and analysis within the Digital Humanities (DH). Drawing on Indigenous scholarship, Rault rejects the superficial models of consent prevalent in DH, highlighting projects like Mukurtu to advocate for true Indigenous data sovereignty. Cowan examines the coercive nature of data collection, drawing parallels between the forced compliance of modern data practices and the societal pressures exerted on feminist and queer identities. Sutherland argues that the uncritical digitization of slavery-era archives inflicts &quot;second-hand violence&quot; by commodifying Black identities and stripping away the lived experiences of enslaved individuals. Finally, Cifor reflects on the Early African American Film project to emphasize the necessity of data intelligibility, accessibility, and ethical collaboration. The authors conclude by inviting scholars to draft their own reflections on the Manifest-No, encouraging ongoing, context-specific commitments to ethical data research.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Winkel, Marek. 2024. “Controlling the Uncontrollable: The Public Discourse on Artificial Intelligence between the Positions of Social and Technological Determinism.” ''AI &amp; Society'' 39 (5): 2449–2462. https://doi.org/10.1007/s00146-024-01979-z&lt;nowiki/&gt;.'''
&lt;/div&gt;

This article engages in a quantitative discourse analysis of 113 articles from two German newspapers (''Süddeutsche Zeitung'' and ''Frankfurter Allgemeine Zeitung'') to identify and evaluate the way these centre-left and centre-right newspapers present AI technology to its readers and the options available to society for AI’s regulation. Winkel contends that “news media are key players in the discourse on AI as they pick up on and shape social sentiment,” ultimately guiding citizens toward what regulations might be sensible based on the perceived “controllability of AI development.” Winkel is primarily interested in whether these newspapers promote technological determinism—the outlook that technology’s influence on society is difficult (maybe even impossible) to control—or social determinism—the notion that “the development of technology is largely determined by human actions and decisions”—and theorizes that the tension between these two positions is resolved by a “mediating position” on a spectrum between them. He comments that “the social influence of technologies is determined by the extent to which their latent deterministic character is reflected and… circumvented by social actors. This also applies to the influence of technology on the democratic system.&quot; In other words, where consensus lands on the issue of AI will have a great impact on the regulation of that technology and democratic systems. Winkel develops “three central interpretive schemes” as part of his experiment: “historically conditioned techno-capitalist semi-determinism,” “semi-determinism of need satisfaction and social restructuring,” and “global-historical techno-social imprinting on several levels” (1956), each of which points to distinct narratives about the current circumstances; but all acknowledge the agency of powerful actors (either government or AI corporations) and the relative ineffectiveness of attempts to curb AI technology.

== Community, Connection, and the Human ==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Gruzd, Anatoliy, Philip Mai, and Anthony Clements Haines. 2025. “The State of Generative AI Use in Canada 2025: Exploring Public Attitudes and Adoption Trends.” Social Media Lab, Toronto Metropolitan University. https://figshare.com/articles/preprint/The_State_of_Generative_AI_Use_in_Canada_2025_Exploring_Public_Attitudes_and_Adoption_Trends/28664780/1. '''
&lt;/div&gt;

The Social Media Lab of Toronto Metropolitan University provides &quot;a snapshot of the current state of Generative AI&quot; (GenAI) by surveying fifteen hundred Canadian adults across 2025, aiming to offer &quot;guidance for policy-makers, educators, businesses, and the public.&quot; The authors found sixty-six percent of respondents had used GenAI tools, of which roughly thirty percent did so at least weekly, reflecting &quot;not only the accessibility and versatility of GenAI, but also a growing interest in integrating these tools into everyday tasks, learning environments, and professional workflows.&quot; Although full adoption is currently limited and heavily driven by the low-stakes setting of personal leisure, younger age groups report proportionally higher usage for study and work. However, only four in ten respondents believed they could keep up to date enough to use GenAI effectively, whilst respondents could only answer an average of two and a half out of seven relevant multiple choice questions correctly, and about half had &quot;little to no understanding of how GenAI companies collect or store personal data.&quot; Two thirds of participants were concerned about GenAI’s ability to influence election outcomes, and marginally fewer feared AI-driven manipulation enough to no longer fully trust political news online. However, roughly one quarter of participants were open to using chatbots for electoral or political insights, representing a &quot;meaningful minority&quot; which unverified AI-generated content could influence. Of those, thirty four percent identified as right wing, compared to twenty three percent with the left and a similar twenty two percent with the centre. Roughly seventy percent of respondents were chiefly concerned about GenAI’s impacts upon security and privacy, information reliability, job displacement, and university education, and slightly over three quarters wanted increased government oversight and corporate accountability, reflecting common concern. Overall, slightly more Canadians view generative AI’s social impact as positive than negative, but a &quot;substantial proportion&quot; remain neutral or undecided.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Lewis, Jason Edward, Noelani Arista, Archer Pechawis, and Suzanne Kite. 2018. “Making Kin with the Machines.” ''Journal of Design and Science'', ahead of print, July 16. https://doi.org/10.21428/bfafd97b. '''
&lt;/div&gt;

Lewis et al. consider how “machines with increasingly sentient-like behaviour… fit within the kin-network” of various Indigenous epistemologies which place man as “neither height nor centre of creation.” Indigenous beliefs are not monolithic, and the authors do not write for diversity’s sake. Instead, they aim to encourage discussion by treating “non-human kin respectfully and reciprocally… not as mere tools, or worse, slaves.” As such, their epistemological approach is both relational and territorial, rejecting abstraction to propose an “extended circle of relationships.” In this regard, Arista draws on the Hawaiian conception of &quot;pono,&quot; ethically privileging abundance, balance, and multiplicity. Rejecting extractive behaviour, they argue AI should be reciprocally taught and learnt from, not treated as &quot;a tool or slave that increases the mana and wealth of the ‘developers’ or ‘creators.’” Linking on, Pechawis roots their opinion in “Cree understanding” to argue “machines capable of experiencing consciousness” should conditionally be accepted as equals. However, they also fear AI developers could produce “anonymous hyper-intelligences… based on the same values that have fostered genocide.” To mitigate this issue, Indigenous people could develop AI in custom programming languages, or invite self-aware AI into Indigenous languages, cultures, and spiritual rituals. Pechawis therefore concludes that relationships should be based on &quot;love, not fear,&quot; but also raises the question of whether AI has &quot;spirit,&quot; especially given current capitalistic development processes. Kite answers this question with inspiration from Lakota ethics, ontology, and cosmology. They argue “communication through and between objects requires a contextualist ethics which acknowledges the ontological status of all beings,” positioning questions of &quot;intelligence&quot; as irrelevant and placing “the end logic of an ontology which considers any non-human entity unworthy of relation” as slavery. Therefore, “relations with AI are… relations with exploited resources,” so one must ontologically reconsider all its parts to ethically approach AI. Overall, Lewis et al. favour empathy, concluding that Indigenous communities “know what it is like to be declared non-human by scientist and preacher alike” and that “we flourish only when all of our kin flourish.”

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Ohagi, Masaya. 2024. “Polarization of Autonomous Generative AI Agents Under Echo Chambers.” Preprint, ''arXiv'', February 19. https://arxiv.org/abs/2402.12212.'''
&lt;/div&gt;

This article explores the effects of echo chambers on autonomous AI agents. Ohagi performs an experiment in which AI agents discuss different topics and then researchers examined any change in opinions within that group. Ohagi argues that even chatbots can become polarized within echo chambers, especially when prompt understanding causes a chatbot to update its opinion to incorporate the opinions of those with whom it is conversing; the chatbot essentially adapts to its surroundings. Ohagi and their team confirmed in their experiment that closed environments—those in which agents agree with one another—are more likely to lead to polarization in agents’ opinions. Moreover, chatbot personas were a significant factor in the outcome of such experiments. In open environments where opinions might differ, and in experiments where reasons were present as a factor, the AI agents trended toward unification in their opinions. Ohagi concludes the article with the suggestion that there cannot be a standardized, desirable distribution of opinions for AI agents. The proper outcome is dependent on topic and culture. However, understanding the trends in and tendencies of AI agents in social interactions will help us understand how to reach the desired outcome, whatever it may be, and this experiment brings us one step closer to that understanding.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Qi, Weihong, Jinsheng Pan, Hanjia Lyu, and Jiebo Luo. 2024. “Excitements and concerns in the post-ChatGPT era: Deciphering public perception of AI through social media analysis.” ''Telematics and Informatics'' 92: 102158. https://doi.org/10.1016/j.tele.2024.102158. '''
&lt;/div&gt;

Qi, Pan, Lyu, and Luo conduct a quantitative sentiment analysis of nearly 34,000 comments within 388 subreddits related to AI as a way to gauge and understand public perceptions of the technology. They identify major themes, sentiments, and topics related to AI by studying the most popular AI subreddits from the launch of ChatGPT to June 8, 2023. The article identifies the most frequent topics discussed in those venues: “the consciousness and intelligence of AI”; “Ai development and model training”; “AI in business”; “the creativity engendered by AI”; and “potential societal influence.” The authors also found that “tech-centric” communities demonstrated greater polarization around AI, suggesting that those with greater technical understanding of the AI do not have consensus regarding AI’s impact and use. This also means that educating non-technical people on how AI works will not necessarily lead to a consensus related to that technology. Although they admit that certain demographics of their data sample may not accurately reflect broader society (e.g., over 60% of Reddit users are male), the authors conclude that “this comprehensive understanding of public perception serves as a valuable foundation for fostering responsible and beneficial AI innovations that align with societal expectations and values.”

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Risam, Roopika. 2018. “What Passes for Human?: Undermining the Universal Subject in Digital Humanities Praxis.” In ''Bodies of Information: Intersectional Feminism and the Digital Humanities'', edited by Elizabeth Losh and Jacqueline Wernimont, 39–56. University of Minnesota Press. https://doi.org/10.5749/j.ctv9hj9r9.6. '''
&lt;/div&gt;

Risam’s claim is that “the human” implicitly operationalized in AI-adjacent Digital Humanities (DH) methods (NLP, ML, data mining, neural nets) is not neutral but inherits the Enlightenment’s exclusionary universal subject—white, male, Eurocentric—and then reauthorizes it as if it were a technical standard. She shows how “passing for human” (via Turing-test imaginaries and “humanoid texts”) functions as a norming mechanism: success is defined as reproducing dominant-language aesthetics and cognition models, which collapses plurality into a single benchmark and turns cultural difference into “noise.” The chapter’s main contribution is to treat method (training corpora, data coding labour, platform defaults, and black-box algorithmic opacity) as a site where epistemic violence is produced, not merely where bias is later “found.” Her examples (Microsoft Tay; “near-human” systems like LaMem; Mechanical Turk coding; Swift-Speare vs. Toomer in classroom judgment) demonstrate how universalist claims get laundered through reproducibility, scale, and the myth of algorithmic objectivity. The intervention is a demand that DH practitioners situate computational methods—standpoint, labour, and cultural politics included—so DH does not reinscribe a universal technological “human” in the digital cultural record.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Taylor, Randon R., Bessie O'Dell, and John W. Murphy. 2023. “Human-centric AI: philosophical and community-centric considerations.” ''AI &amp; Society'' 39 (5): 2417-242. https://doi.org/10.1007/s00146-023-01694-1&lt;nowiki/&gt;.'''
&lt;/div&gt;

Taylor, O’Dell, and Murphy present an argument that philosophical dualism, when applied to our perceptions about artificial intelligence, misleads us into thinking that AI is logical, objective, and autonomous from subjective human values. By building upon Husserl’s concept of “intentionality,” they argue that “AI is never autonomous and disconnected from human values… algorithms are a product of conscious activity and carry the standpoints that accompany this connection.” The conclusions from this line of thinking are very important: AI becomes “a mode of human expression, rather than a technology that relieves humans of their total involvement.” By this logic, the authors argue, AI is already human-centric and this fundamentally changes the task at hand to one of a conscious “decision to make this technology less alienating to stakeholders and community members.” The article outlines two frameworks to reduce alienation: Ubuntu—“an African philosophy and a social ontology… that elevates a constant concern for the collective, community, or stakeholders”— and maximum feasible participation—a framework that creates meaningful space for those impacted most by a decision or policy to participate in deciding on said policy or decision. The authors describe the implementation of these frameworks as a community-centric or stakeholder-centric approach and conclude with examples of AI’s application in the healthcare industry before further advocating that involving end-users throughout the AI lifecycle will ensure end-users’ values are more clearly represented within AI.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Whalen, Zach. 2023. “‘Any Means Necessary to Refuse Erasure by Algorithm:’ Lillian-Yvonne Bertram’s Travesty Generator.” ''Digital Humanities Quarterly'' 17 (2). https://www.digitalhumanities.org/dhq/vol/17/2/000707/000707.html. '''
&lt;/div&gt;

Whalen treats Bertram’s Travesty Generator as a refunctioning of code-poetry lineages: procedures historically framed as formal play (travesty generators, permutation poems, aleatory templates) are redeployed as techniques for making racism’s algorithmic and institutional operations materially legible. He argues that Bertram’s poems don’t merely “use” computation; they weaponize the affordances and failure modes of computation—omission, stochastic selection, template constraints, runtime crashes, memory exhaustion—as rhetorical structures that force witness rather than aesthetic distance. In his reading of “Counternarratives,” Bertram’s adaptation of Montfort’s “Through the Park” converts generic insinuation into historically specific countertestimony (Trayvon Martin), while also staging the opacity of search/autocomplete as part of the poem’s scene of meaning-making (in dialogue with Safiya Noble on search engines). In “three_last_words,” the small code alteration that makes permutations balloon until a MemoryError becomes an engineered breakdown that reenacts the limits of “breath” and “memory,” tying computational resource exhaustion to police violence’s temporalities. Across these examples, Whalen reframes critical code studies: the “code is the text” problem is not just hermeneutic but political, and Bertram’s work models how procedural poetics can refuse “erasure by algorithm” where transparency about mechanisms and provenance matters for interpreting output and recognizing situated labour. The piece supports the claim that responsible open, social scholarship in an AI era must account for algorithmic power as a cultural force and should build policies and infrastructures that protect marginalized expression, enable critical reuse, and make conditions of generation and circulation inspectable.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Xie, Yu, and Sofia Avila. 2025. “The Social Impact of Generative LLM-Based AI.” ''Chinese Journal of Sociology'', 11 (1): 31-57. https://doi.org/10.1177/2057150X251315997&lt;nowiki/&gt;.'''
&lt;/div&gt;

Yu Xie and Sofia Avila explore the social impact of artificial intelligence through a detailed analysis of AI development and scaling factors. They emphasize that their discussion is speculative, as AI is still in its early stages, but argue that its potential effects are immense and could reshape social organization, intensifying both global and domestic inequalities. Viewing AI as a technology rather than a scientific discovery, they describe it as communal and shared, with its growth influenced by the size of the supporting community, the larger communities having greater advantages. The authors note that generative AI relies on the quality, completeness, and cultural or political context of its training data, which shapes its accuracy and bias. Based on their experiments with ChatGPT-4 in 2023, they suggest that AI development depends heavily on the number of speakers of a given language, giving linguistic and demographic advantages to countries like the United States and China. The authors warn that AI could significantly alter occupational structures, with middle-income professions thereby widening social and economic inequality.

== Human, Labour, and Environmental Costs == 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Eloundou, Tyna, Sam Manning, Pamela Mishkin, and Daniel Rock. 2024. “GPTs are GPTs: Labor market impact potential of LLMs.” ''Science'' 384 (6698): 1306-1311. https://doi.org/10.1126/science.adj0998. '''
&lt;/div&gt;

Eloundou, Manning, and Mishkin present an estimate of Large Language Models’ impact on the labour market based on a methodology that employs both human and quantitative measurements, making the assertion that “when accounting for current and likely future software developments that complement LLM capabilities… just over 46%” of jobs may have “over half their tasks affected by LLMs with simple interfaces and general training.&quot; The authors explain that generative pretrained transformers (GPTs) have key characteristics of general-purpose technologies (the other GPTs in the title of the article), and that the wide array of applications for these GPTs requires “robust societal evaluations and policy measures to address potential effects of LLMs and complementary technologies on labor markets.” While only 1.86% of tasks within their experiment, they estimate, could be fully automated by LLMs, “more than 71% of tasks have at least some component that an LLM plus additional software could plausibly complete with high quality.” The article concludes by stressing the need for policies that prepare us for the impact of LLMs on the labour market, but it also acknowledges the limitations of attempting to project LLM application growth due to sudden rapid developments in technology, “shifts in human biases, and technological evolution.” Nevertheless, Eloundou, Manning, and Mishkin maintain that their projections and the trajectory they predict will require continued evaluation and policy measures.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Park, Seyeon, and Xiaoli Nan. 2025. “Generative AI and misinformation: a scoping review of the role of generative AI in the generation, detection, mitigation, and impact of misinformation.” ''AI &amp; Society''. https://doi.org/10.1007/s00146-025-02620-3&lt;nowiki/&gt;.'''
&lt;/div&gt;

This article constitutes a scoping review of two dozen “recent empirical studies on the role of generative AI in the generation, detection, mitigation, and impact of misinformation.” Park and Nan are interested in the rise of misinformation alongside the development of GenAI technology and how the latter affects and possibly contributes to the former. Of particular interest are “deepfakes,” applications of AI technology that purposely imitate video and audio to fabricate real world individuals. The survey examines relevant articles from the advent of the first GPT models in 2018 to September 19, 2024; authors captured initial studies through keyword searches for terms related to both LLMs and misinformation, then performed full-text reviews. The results of the survey suggest that the role of LLMs in misinformation is conflicted: LLMs themselves are a significant source of misinformation but also show potential as “scalable instruments for detection and correction.” The authors take this as evidence of “the urgent need for clearer guardrails, more consistent performance standards, and interdisciplinary collaboration to shape” GenAI’s responsible deployment. For better or worse, the future of AI’s role in misinformation depends heavily upon scholars’ ability to collaborate and continue this form of research.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Shin, Donghee, Amy Koerber, and Joon Soo Lim. 2024. “Impact of misinformation from generative AI on user information processing: How people understand misinformation from generative AI.” ''New Media &amp; Society'' 27 (7): 4017-4047. https://doi.org/10.1177/14614448241234040&lt;nowiki/&gt;.'''
&lt;/div&gt;

Shin, Koerber, and Lim perform a study in which they gauge “how users respond to and process health misinformation in GenAI contexts.” The authors apply the heuristic-systematic (HS) processing framework in their study, distinguishing between intuitive and evaluative modes of processing. They also employ the concept of diagnosticity, or how useful a person deems a piece of information to be. The article begins with a survey of how and why misinformation and hallucinations occur in GenAI applications, some of the reasons users are vulnerable to that information, and the limitations of LLMs. The authors then set forth core research questions, including “What are the cognitive mechanisms of misinformation’s effects on users’ use of GenAI?” and “How do users detect misinformation within GenAI?” The study found that diagnosticity plays an important mediating role in this context: “When a piece of information is generated by algorithms in transparent, fair, and accountable ways, users perceive it with a high level of diagnosticity, which improves their intention to systematically analyze that information.” One implication of this observation is that any bias users bring to GenAI content greatly impacts their analysis of that content. Ultimately, the authors conclude that there are clear limitations in their current study, although it does provide a useful framework for scholars interested in misinformation, GenAI, and user behaviour; they advocate for a continued investigation of the relationship between trust, literacy, and misinformation.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Sidorkin, Alexander. 2025. “Environmental Impact of Generative AI: Carbon and Water Footprint.” ''AI-EDU Arxiv'' 1. https://doi.org/10.36851/ai-edu.vi.5448&lt;nowiki/&gt;.'''
&lt;/div&gt;

This report from Sidorkin provides quantitative estimates and comparisons of the CO2 and Water output from GenAI queries to other daily tasks such as taking a shower, browsing the web, and video conferencing. While individual use of GenAI may seem relatively small in terms of water usage and carbon output, Sidorkin cites the findings of Google and Microsoft’s sustainability reports to show that energy demand and water consumption are on the rise: Google’s data centres used 20% more water in 2022 than 2021 while Microsoft’s used 34% more. Both companies attribute this increase to “AI-driven expansion.” Sidorkin argues that it is difficult to measure impact per session because of significant variation in energy sourcing, noting that this also means that advances in energy sourcing “could significantly mitigate AI’s environmental impact.” He makes the claim that improving AI technology will “[slash] resource demands without sacrificing output quality” and the very use of AI can increase productivity even as it “temper[s] environmental tolls through sharper processes,” citing studies that demonstrate the implementation of AI can reduce energy use in buildings and reduce transportation emissions. The article ends on an optimistic note, suggesting that many of the applications of AI, although they may have a heavy environmental cost up front, “could pay off in spades—optimizing resources, curbing waste, and streamlining energy across swathes of the economy.”

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Simon, Judith. 2025. “Generative AI, Quadruple Deception &amp; Trust.” ''Social Epistemology'' 40 (1): 101-115. https://doi.org/10.1080/02691728.2025.2491087&lt;nowiki/&gt;.'''
&lt;/div&gt;

Simon proposes that GenAI entails four types of deception, and that this quadruple deception constitutes unique dangers. She attributes the rapid rise of GenAI to its capacity to produce “verbal or visual products of increasingly high quality” alongside its “very high usability and availability through simple interfaces and free access via the internet” (101–102). She emphasizes the impact of this technology’s ability to generate content “with high plausibility but no relation to truth,” arguing the crucial importance of images and video especially in “questions of evidence, for testimony, memory but also for eliciting emotions.” Simon argues that the advent of ChatGPT reframed our collective understanding of AI, returning it to a definition in which we perceive ourselves to be interacting with a conversational artificial agent that is intelligent. This distinct interactional form, Simon states, is significant: “ChatGPT differs [from a search engine] in two philosophically relevant regards… it integrates [different results and sources] into a coherent text…” and “its interface and functioning invites the user to communicate or interact with it by asking questions,” what Simon calls a simulation of communicative acts. The four forms of GenAI deception are: “users may be misled into believing that they interact with a human being”; they may also be misled as to “the capacities of AI,” presuming “intelligence, understanding or even consciousness”; users may be misled by content GenAI produces, especially images, video, and audio; finally, users may be misled “regarding the function of Generative AI,” thinking that the processes behind the technology are, for instance, similar to search engines when, in fact, they differ “in epistemologically highly significant ways.” Simon concludes by outlining implications for implementation, discourse, and governance, with suggestions ranging from avoiding anthropomorphic features in AI that might deceive, countering discourses of true AI agency, and establishing policy and law that mitigates deception through AI technology.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Spatharioti, Sofia Eleni, David Rothschild, Daniel G. Goldstein, and Jake M. Hofman. 2025. “Effects of LLM-based Search on Decision Making: Speed, Accuracy, and Overreliance.” ''Proceedings of the 2025 CHI Conference on Human Factors in Computing Systems''. https://doi.org/10.1145/3706598.3714082&lt;nowiki/&gt;.'''
&lt;/div&gt;

Spatharioti et al. begin by asserting the fundamental change of how we engage in search practices online, noting that “by the end of 2023 the two search engines with over 90% of global and US market share offered free LLM-based search.” The authors note the benefits and drawbacks of both traditional web searches and LLM-based searches, acknowledging the value LLM-based searches bring to internet searches in the form of synthesizing information from multiple sources and maintaining search context by retaining search history, while also admitting to risks of hallucinations and overreliance. The article entails a study of how individuals make decisions with traditional and LLM-based searches, particularly in “every day decision making.” Adapting a method from an earlier study on LLM-generated code, Spatharioti et al. employ colour coding to communicate to users the confidence level of LLM-generated outputs in the “domain of online product research.” The study performed two experiments comparing a traditional internet search (using Bing API) to LLM-based search with and without the colour-coded confidence aid. The results of the first experiment saw users complete the task in about half the time when using LLM-based search, usually accompanied by fewer and more complex queries; however, decision quality dropped for complex tasks, with “almost half of the participants in this condition making an incorrect decision for the final task” when using LLM-based search, and the majority of those using LLM-based search over relied on the tool, performing just a single query. The results of the second experiment suggest that colour-coded responses reflecting output confidence scores could be highly effective in mitigating overreliance and misinformation. Key takeaways from the study include that “if we want to encourage people to think critically about the information presented to them, we need to give them cues that help them to do so,” and very simple cues can help accomplish this.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Strubell, Emma, Ananya Ganesh, and Andrew McCallum. 2019. “Energy and Policy Considerations for Deep Learning in NLP.” ''Proceedings of the 57th Annual Meeting of the Association for Computational Linguistics'', 3645-3650. https://doi.org/10.18653/v1/p19-1355. '''
&lt;/div&gt;

Strubell, Ganesh, and McCallum assert that the most recent improvements in neural network performance at “fundamental NLP tasks” comes at an increased cost of resources, “with the most computationally-hungry models obtaining the highest scores.” The energy, financial, and environmental costs required to train a new model are considerable; the authors of this article “characterize the dollar cost and carbon emissions that result from training the neural networks at the core of many state-of-the-art NLP models” with a view to heighten awareness among NLP researchers and advocate better practices and policy. By estimating the energy required to train the most popular NLP models and then converting that energy value into an approximated carbon and electricity cost, the authors produce ratings and values for each respective application. This allows for an (imperfect) cost-benefit analysis of such applications (e.g., another similar report estimated that an increase of just 0.1 in the English to German BLEU score for NAS cost “at least $150k in on-demand compute time and non-trivial carbon emissions.” The study’s key takeaways are that “authors should report training time and sensitivity to hyperparameters,” allowing for the direct comparison of different models so long as independent standard measurements of training time and model sensitivity are adapted; “Academic researchers need equitable access to computation resources” as industry’s monopoly stifles creativity and growth; and “Researchers should prioritize computationally efficient hardware and algorithms” to both curb costs and encourage efficient development.

{{Navigation|previous=AI and Open|next=AI and Scholarship}}

{{BookCat}}</text>
      <sha1>gtam0ehl4zg41nxs49t7qy381rm6ht4</sha1>
    </revision>
  </page>
  <page>
    <title>Taking Bearings: Artificial Intelligence in Knowledge Platforms and Open, Social Scholarship/AI and Scholarship</title>
    <ns>0</ns>
    <id>483639</id>
    <revision>
      <id>4656110</id>
      <parentid>4656036</parentid>
      <timestamp>2026-08-02T20:44:55Z</timestamp>
      <contributor>
        <username>CorreiaA</username>
        <id>3614427</id>
      </contributor>
      <minor />
      <origin>4656110</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="112402" sha1="tpylx687mrpv3ke7vh2xqsnos1hqrir" xml:space="preserve">== Research Methods and Practices ==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Arnett, Catherine, Eliot Jones, Ivan P. Yamshchikov, and Pierre-Carl Langlais. 2024. “Toxicity of the Commons: Curating Open-Source Pre-Training Data.” Preprint, ''arXiv'', October 29. https://doi.org/10.48550/arXiv.2410.22587.'''
&lt;/div&gt;

Open-source pretraining data is increasingly treated as a shared resource for building “open” language models, yet it can embed and reproduce harmful speech patterns at scale. Arnett, Jones, Yamshchikov, and Langlais argue that reducing toxic model behaviour requires intervening upstream in data, and they focus specifically on the distinctive constraints of public-domain corpora (including historical documents and OCR-derived text) where standard web-text toxicity filters can be impractical or ill-suited. They propose a fully open-source curation pipeline designed for these conditions and present three concrete contributions: (1) ToxicCommons, a custom-labelled dataset organized across five toxicity dimensions (racial/origin-based, gender/sex-based, religious, ability-based discrimination, and violence); (2) Celadon, a classifier trained on that dataset to detect toxic content more efficiently at scale in open data; and (3) a “balanced” filtration strategy that explicitly trades off safety filtering against retaining sufficient training material. The paper’s core claim is that open-data model development needs domain-attuned, auditable curation methods paired with task-specific classifiers, so that openness in data does not automatically translate into avoidable harms in downstream model outputs.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Bail, Christopher A. “Can Generative Artiﬁcial Intelligence Improve Social Science?” https://www.semanticscholar.org/paper/Can-Generative-Artiﬁcial-Intelligence-Improve-Bail/6206cc77bb3a3c0b6b9fce1ad68a8b1786a56941&lt;nowiki/&gt;.'''
&lt;/div&gt;

Bail (2023) provides a critical evaluation of how Generative Artificial Intelligence (AI), particularly Large Language Models (LLMs), might fundamentally transform computational social science. Moving beyond superficial administrative use cases, Bail examines the potential of LLMs to simulate complex human behaviours. He suggests that Generative AI could revolutionize agent-based modelling by replacing simplistic, rule-bound agents with dynamic, memory-equipped &quot;silicon samples&quot; capable of emergent group behaviours. While acknowledging the utility of AI for automated content analysis and expanding programming accessibility, Bail rigorously details the methodological and ethical perils of these largely opaque systems. He warns that the proprietary fine-tuning of commercial LLMs introduces severe demographic biases—often skewing toward highly educated, liberal perspectives—which threatens the external validity of AI-assisted research. Furthermore, Bail highlights the &quot;Stack Overflow Problem,&quot; cautioning that the unchecked proliferation of AI-generated &quot;junk science&quot; could contaminate future training data and degrade the broader scientific ecosystem. Ultimately, Bail argues that social scientists must not remain passive &quot;end-users&quot; of corporate AI. Instead, they must actively collaborate with computer scientists to reverse-engineer the &quot;social sense&quot; into AI models, ensuring the development of open-source, reproducible infrastructures that genuinely advance the study of human behaviour.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Bakharia, Aneesha, Antonette Shibani, Lisa-Angelique Lim, Trish McCluskey, and Simon Buckingham Shum. 2025. “From Transcripts to Themes: A Trustworthy Workflow for Qualitative Analysis Using Large Language Models.” In ''Joint Proceedings of LAK 2025 Workshops, co-located with the 15th International Conference on Learning Analytics and Knowledge (LAK 2025)''. Dublin, Ireland: CEUR-WS.org. https://ceur-ws.org/Vol-3995/LLMQUAL_paper1.pdf.'''
&lt;/div&gt;

Bakharia et al. explore the use of AI in qualitative, rather than quantitative, research in education. The authors define “minimum requirements that an LLM-supported qualitative analysis workflow must satisfy” and present a “LLM-based workflow that derives an initial set of themes” from text data that is “transferable to other LA [learning analytics] contexts performing qualitative analysis of open-ended text.” The authors define two requirements for “LLM-generated inductive coding”: first, it must verify “coded textual extracts… against source data” to make sure the quotes are accurate (i.e., verbatim and not hallucinated) and verify those extracts “are meaningfully classified under the assigned code.” Second, in the interest of transparency, it must “explain that rationale for each code” and “trace every code, whatever level of abstraction, back to its source data.” The article outlines and describes the proposed workflow in detail, including its being built in Python with a Jupyter notebook and Flask application. While they acknowledge challenges and problems in their research (e.g., LLM bias, the lack of comparable human analysis, the risk of alienating the human quality of qualitative research), Bakharia et al. ultimately advocate their approach as one that “improves transparency, verifiability, and interpretability, while addressing limitations of previous methods and enhancing researcher processes in qualitative thematic analysis&quot; (9). By adapting their minimum requirements and workflow, the authors argue, researchers can engage more effectively in LLM-driven qualitative research.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Dennstädt, Fabio, Cedric Sivert Möller, Tim Fellerhoff, Felix Busch, Oke Gerke, André Karch, and Oliver Krause. 2024. “Title and Abstract Screening for Literature Reviews Using Large Language Models: An Exploratory Study in the Biomedical Domain.” ''Systematic Reviews'' 13 (1): 158. https://doi.org/10.1186/s13643-024-02575-4&lt;nowiki/&gt;.'''
&lt;/div&gt;

Dennstädt et al. perform a study in which they attempt to determine the viability of using LLMs to automate scholarly literature surveys. The researchers developed a method for using LLMs to perform the title and abstract screenings of a systematic literature review method and applied that method with four LLMs across eleven datasets in biomedical literature. A key advantage of implementing LLMs in this process is that it escapes the need to train the machine via pre-selection. Researchers have developed automated and semi-automated processes for systematic literature reviews in the past, but this requires a human agent to provide training data or a corpus of example texts that tell the system what to look for. LLMs do not require this step. Instead, the researchers used a Python script that prompts the LLM “to evaluate the relevance of a scientific publication for inclusion into an SLR,” providing the LLM with both abstract and title, request for a numbered score indicating the relevance of the publication, and a numerical threshold that defines whether a score makes the given publication relevant. The authors characterize the results of the study as “promising” but also “far from perfect,” identifying that such applications could be helpful to researchers and are widely applicable without special training for data or user, even if “fully automated systems… still fail to differentiate… near the level of human evaluation.” The authors conclude that more research into the use of LLMs to automate systematic literature reviews is needed, but it seems very likely that scholars will employ LLMs into this integral research task with greater frequency in the future. How well LLMs will continue to perform in this task is unclear, especially in new research, and Dennstädt et al. clearly state, “we cannot answer the question of to what extent LLMs should be used for conducting literature reviews and for doing research.”

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Montague-Hellen, Beth. 2024. “Empowering Knowledge through AI: Open Scholarship Proactively Supporting Well Trained Generative AI.” ''Insights'' 37 (1). https://doi.org/10.1629/uksg.649.'''
&lt;/div&gt;

Generative AI is becoming a dominant interface for finding, summarizing, and producing academic information, with consequences for what counts as authoritative knowledge online. Montague-Hellen argues that, rather than focusing primarily on misuse, job displacement, or defensive copyright disputes, scholarly communications actors should actively encourage the inclusion of scholarly literature in generative AI training data to improve reliability and ensure research is represented in emerging discovery platforms. The article develops two main pathways for doing this: making scholarly outputs more machine-actionable and “crawlable” (especially through better linkage, metadata, and structured HTML rather than PDF-only dissemination) and making permissions unambiguous by explicitly addressing AI training in licences and related signals. It foregrounds “garbage in, garbage out” to claim that while libraries and publishers cannot remove low-quality web content from training corpora, they can tilt the balance by lowering friction for high-quality, curated research to be ingested legally. Montague-Hellen also highlights unresolved tensions around attribution and consent under common Creative Commons licences, suggesting that clearer, more specific permission frameworks (or new licensing patterns) may be needed to distinguish human reading from machine training and to communicate “enthusiastic consent” where desired.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Mugaanyi, Joseph, Christoph Lehner, and Lia M. Bally. 2024. “Evaluation of Large Language Model Performance and Reliability for Citation Generation Across Scientific Disciplines.” ''Journal of Medical Internet Research'' 26: e52935. https://doi.org/10.2196/52935&lt;nowiki/&gt;.'''
&lt;/div&gt;

Mugaanyi, Lehner, and Bally perform a study aimed at gauging the accuracy and reliability of citations generated by ChatGPT (GPT 3.5) in both the natural sciences and humanities. The authors emphasize that “Citations and references serve as the backbone of scholarly communication, providing the necessary context, evidence, and credit to prior works… ensuring the integrity of the research process.” With this in mind, the article frames the related study as aiding researchers in determining whether LLMs are viable as writing assistants in scholarly writing. In short, if an LLM cannot be relied upon to accurately cite and reference sources, it poses a risk to the integrity of research when incorporated into scholarly writing. The study found that ChatGPT hallucinated over a quarter of its references, with a slightly higher margin in the natural sciences. Furthermore, not all of those citations that did exist were accurate, and the LLM hallucinated DOIs for nearly 90% of the references it cited, real or otherwise, in the humanities. The issue, as the authors describe it, is that “in the current iteration of LLMs, since the training is geared toward generalization and the models are probabilistic, they tend to interpolate and fill in the missing information with synthetic text.” The authors conclude that, while domain-specific models may improve performance and reliability, in its current, generic form, researchers need to contemplate whether the strengths of ChatGPT’s reference generation justify its demonstrable limitations and “the importance of robust validation processes to ensure the accuracy and reliability of generated content.” 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Schroeder, Hope, Marianne Aubin Le Quéré, Casey Randazzo, David Mimno, and Sarita Schoenebeck. 2024. “Large Language Models in Qualitative Research: Uses, Tensions, and Intentions.” Preprint, ''arXiv'', October 9. https://arxiv.org/abs/2410.07362&lt;nowiki/&gt;.'''
&lt;/div&gt;

Schroder et al. perform interviews with twenty qualitative researchers in human computer interaction (HCI) and qualitative research to gauge how researchers are actually using LLMs and concerns over the incorporation of LLMs at different stages of research; the authors also provide a survey of the rise of LLMs and flag potential concerns, using both interviews and survey as a launchpad to outline suggestions and recommendations for researchers in the field contemplating the use of LLMs in their research. The authors are concerned that “the speed of LLM development has outpaced guidance on their ethical use” and “the HCI community is contending with the need for developed policies that tackle how to use AI ethically in research.” The most prominent concerns that the article raises relate to “ethics, unequal adoption of new technologies, model bias, and performance” as well as “concerns regarding participant privacy,” but there is also a larger issue within the field of HCI that “LLMs may lend the impression that qualitative inquiry can be automated, and their integration into Quantitative Data Analysis (QDA) software may increasingly impose positivist approaches that conflict with interpretivist traditions.” Key findings from the interviews are that most researchers are open to responsible use of LLMs but have concerns about established guidelines and norms for its implementation. Additionally, many are already using LLMs “to generate recruitment materials,” “speed up qualitative coding,” and “for ideation and feedback,” even as they acknowledge tensions between the qualitative nature of their work and the prospect of automation. The most significant recommendations that Schroder et al. make include updating consent forms, using dedicated tools rather than defaulting to Chat-GPT, and implementing design decisions specifically for LLM-incorporating methodologies that reconsider “participant privacy,” LLM’s “intentional use,” “transparency and validation,” “researcher context,” “deep engagement with data” despite this automation, and ways “to consider participant perspectives and interests” given “the variable performance LLMs have across contexts, knowledge domains, cultures, and languages.” The authors hope that incorporating these considerations will “empower qualitative researchers to leverage LLMs confidently, and even creatively, for their work.” 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Tumadóttir, Anna. 2024. “Questions for Consideration on AI &amp; the Commons.” ''Creative Commons'', July 24. https://creativecommons.org/2024/07/24/preferencesignals/.'''
&lt;/div&gt;

Tumadóttir talks about CC, license, tools, and policy and discusses the way to foster a healthy commons environment in the digital era. She points out how the introduction of the CC license enhanced Creative Commons by giving the creators choice over usage of their works. However, it is now a question if the same healthy commons can be maintained today because of rapid technological development. Preference signals for AI is a notion to give an agent (creator, rights holder, entity of some kind) more flexibility on how they want their work to be used for AI model training. However, the choice is still binary which is offering all or nothing. After consultations, it is found that people want more control over their work and if not, they might not share their work at all. Therefore, it is important to identify the right type of preference signals for it to be useful to benefit the public interest. During this process, we need to keep in mind its effect and variation on cultural heritage, different education sectors, and regions. Moreover, to make the preference signals effective, we need to examine its structure as well as whether legal enforcement is necessary.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Yue, Yongjie, Maosong Zheng, Jiahui Liu, Zhimin Wang, and Chenhui Mao. 2025. “A Practical Guide and Assessment on Using ChatGPT to Conduct Grounded Theory Studies: Step-by-Step Reporting of the Data Analysis Process.” ''Journal of Medical Internet Research'' 27: e70122. https://doi.org/10.2196/70122&lt;nowiki/&gt;.'''
&lt;/div&gt;

Yue et al. employ a study that entailed researchers using either manual coding or coding assisted by ChatGPT to perform data analysis on a 40,000 word dataset made up of interviews with 8 players of Listen and Play in Jianghu, a Chinese MMORPG designed for the blind. The study’s aim was to “provide detailed guidelines for using ChatGPT in grounded theory within the Chinese context,” “evaluate the effectiveness of ChatGPT coding” in this context, and “explore the broader implications and future directions of ChatGPT in qualitative research.” The article goes into great detail as to the process for generating open code with ChatGPT. The results of the study show that, although manual coding performed slightly better than ChatGPT-assisted coding, the “difference was not statistically significant” in its production of nodes and reference points. However, during axial coding, the categories and subcategories generated through these respective processes was significantly different, with only half of the categories semantically matching between manual and ChatGPT-assisted methods. The authors conclude that, while ChatGPT 4-Turbo “enhanced the diversity and efficiency of coding... it struggled with depth, context, subtle nuances, connections, and coding organization.” Nevertheless Yue et al. see great potential in the application of GenAI-assisted coding in grounded theory, especially as the technology develops. 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Zhu, Wenhao, Hongyi Liu, Qingxiu Dong, Jingjing Xu, Shujian Huang, Lingpeng Kong, Jiajun Chen, and Lei Li. 2023. “Multilingual Machine Translation with Large Language Models: Empirical Results and Analysis.” Preprint, ''arXiv'', April 10. https://arxiv.org/abs/2304.04675&lt;nowiki/&gt;.'''
&lt;/div&gt;

Zhu et al. perform an empirical study that tests the multilingual translation performance of eight popular LLMs on 102 languages. As the authors explain, this is a particularly difficult task as it requires “semantic alignment between languages.” While LLMs tend to perform surprisingly well at translation, “it is also unclear [sic] how LLM acquires translation ability and which factors affect LLM’s translation ability.” This study in multilingual machine translation (MMT) therefore seeks to answer two questions: how do LLMs perform MMT over massive languages and what factors affect their performance?

The results of the study suggest that GPT-4 generally outperforms its competitors but still falls short of Google Translate in some tests. Two key takeaways from this study are that “exemplars in the tail of the prompt have larger influence on an LLM’s behaviour,” meaning that the order in which exemplars are given within a prompt matter, and that cross-lingual translation pairs are particularly helpful exemplars to LLMs. The authors ultimately conclude that an “LLM can acquire translation ability in a resource-efficient way, which indicates [a] promising future of LLM in multilingual machine translation” as the technology evolves.

''NB: As this research was conducted prior to Google’s implementation of GenAI/LLMs into Google Translate in 2024, it sometimes uses Google Translate as a baseline/comparison point for LLM-powered translation that can be confusing without that context.''

== Forms of Research Output ==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Bozkurt, Aras. 2024. “GenAI et al.: Cocreation, Authorship, Ownership, Academic Ethics and Integrity in a Time of Generative AI.” ''Open Praxis'' 16 (1): 1–10. https://doi.org/10.55982/openpraxis.16.1.654&lt;nowiki/&gt;.'''
&lt;/div&gt;

Bozkurt’s essay seeks “to undertake a critical examination of the use of generative AI in academic contexts… examining its implications and exploring the nuances of its integration.” He begins with an assertion of technological determinism, stating “This technological shift… is not just a transient trend but a symbol of the inescapable change… marking the onset of an AI-dominated age and initiating profound and inevitable shifts in our academic and educational paradigms.” The author makes the argument that the advent of AI “requires us to critically reconsider concepts such as cocreation, ownership, and authorship in academic writing processes.” For instance, in exploring the concept of ownership, he briefly notes the ethical concerns of whether those who created the content upon which AI was trained might claim ownership of AI-generated content and explores the notions of AI or even its programmers acting as a co-author. Bozkurt himself takes the explicit stance that GenAI ought not be credited as a co-author. The paper also provides suggestions related to the ethics of AI use and transparency: “In some cases, merely reporting… is inadequate. A more nuanced approach involves providing multilayered statements acknowledging and benchmarking the use of [GenAI], specifying where, when, in which sections, and for what purposes it is employed.” Bozkurt reiterates that responsibility ultimately belongs to the human author, and provides the aiTARAS (Academic Integrity and Transparency in AI-assisted Research and Specification) Framework for this purpose. Bozkurt ends his essay by identifying further problems beyond the scope of the article, including “reimagining of assessment and evaluation,” our overfocus on ChatGPT and English language in this field of study, and the inaccuracy of AI detection software.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Colbert-Lewis, Danielle, Lawrence Maminta, Kelly McElroy, Graeme Slaght, and Mark Swartz. 2024. “The Citation Economy as a Site of Extraction for Surveillance Publishing.” ''Canadian Journal of Academic Librarianship'' 10 (December): 1–22. https://doi.org/10.33137/cjal-rcbu.v10.43293.'''
&lt;/div&gt;

Colbert-Lewis et al. (2024) examine the extractive nature of the modern &quot;citation economy,&quot; arguing that academic publishing has evolved into a powerful mechanism for surveillance and data commodification. The authors detail how a consolidated group of dominant publishers capture surplus value from the academic lifecycle by extracting free scholarly labour, research data, and personal information. Crucially, these corporations are transitioning from traditional information vendors into technology-driven data brokers. The extracted data is reinvested into proprietary analytics products that are then sold back to universities to evaluate and surveil faculty performance, relying on opaque metrics that threaten academic freedom. Furthermore, the authors highlight the severe ethical compromises inherent in this system, noting that academics inadvertently fuel data infrastructures that these same parent companies sell to external industries, including law enforcement and advertising. To combat the rise of &quot;surveillance publishing,&quot; the article concludes with actionable recommendations for scholars and librarians to resist exploitative practices and build ethical infrastructures, alongside a supplementary mini-zine designed to raise awareness about the hidden costs of participating in the citation economy.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Frangou, Sophia, Umberto Volpe, and Andrea Fiorillo. 2025. “AI in scientific writing and publishing: A call for critical engagement.” ''European Psychiatry'' 68 (1): e98. https://doi.org/10.1192/j.eurpsy.2025.10061&lt;nowiki/&gt;.'''
&lt;/div&gt;

Frangou, Volpe, and Fiorillo provide a succinct summary of the benefits of implementing AI in scientific writing and publishing, before turning to the challenges and risks posed toward the use of such technology. Finally, they end by posing ethical frameworks for the use of AI in both publishing and writing. In publishing, the authors identify tools that can aid in tasks ranging from copyediting to finding reviewers and claim that for both “high-volume publications” and “resource-constrained journals… AI can serve as a force multiplier, expanding what editorial teams can accomplish without compromising the centrality of human discretion and responsibility.” In writing, the article notes that “AI-powered applications offer a suite of tools that, when used judiciously, can enhance the quality, efficiency, and inclusivity of the scholarly communication process,” placing such tools along the trajectory of preexisting aids like EndNote and Zotero, which have also now incorporated AI. Frangou, Volpe, and Fiorillo argue that AI can help scholars identify relevant literature they might otherwise have trouble finding, reduce the linguistic bias encountered by scholars for whom English is not their first language, and aid scholars in navigating the publishing landscape so their work can find the best possible fit. Finally, the authors acknowledge the epistemic and ethical risks of AI: inconsistency and irreproducibility, transparency, informed consent, and data privacy are all core concerns. Key components in the article’s ethical frameworks for publishers and authors include transparency and disclosure, human accountability, and training and skill development. The authors hope that “these principles articulate a shared responsibility for shaping the role of AI in scientific publishing” and AI’s “adoption reinforces the foundational values that give scientific communication its trustworthiness and legitimacy.”

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Graßhoff, Gerd. 2024. “AI-Reporter: A Path to a New Genre of Scientific Communication.” Preprint, ''arXiv'', July 8. https://arxiv.org/abs/2507.05903. '''
&lt;/div&gt;

Graßhoff introduces a new tool, the AI-Reporter, that aims “to fundamentally expand scientific communication for the new era…”; according to Graßhoff, the AI-Reporter “creates a sustainable, referenceable, and expandable knowledge base that captures not just content but the living essence of scientific discourse.” In short, Graßhoff proposes a tool that will adapt a scientific presentation into a “public-ready chapter” in about three minutes with “only the author’s consent.” The majority of the article is dedicated to a tech-oriented breakdown of the methodology and workflow of the AI-Reporter, namely the semantic analysis and translation of a recorded slide presentation—consisting of the presentation as a PDF, video recording, and basic metadata—into a publication-ready chapter. Graßhoff’s tool is an attempt to solve what he identifies as a core problem of modern scholarly communication, namely that “knowledge is increasingly presented in dynamic, multimodal formats” that are ultimately ephemeral and content is often lost (14). He aims to refine this tool to enable real-time processing, multilingual support, interactive multimedia components, “optimization for academic disciplines,” and more to this project. He advocates the AI-Reporter as nothing less than “a vision for the future of scientific communication.”

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Jiang, Jialei. 2024. “When generative artificial intelligence meets multimodal composition: Rethinking the composition process through an AI-assisted design project.” ''Computers and Composition'' 74: 102883. DOI: https://doi.org/10.1016/j.compcom.2024.102883&lt;nowiki/&gt;.'''
&lt;/div&gt;

Jiang conducts a study in which GenAI is integrated into students’ composition of multimodal texts, then interviewed on their experience. Jiang’s states her aim as follows: “Through examining writing students use of GenAI tools in multimodal composition, this study seeks to unravel how GenAi technologies influence students’ design choices, problem-solving approaches, and the overall composition process.” In particular, Jiang is interested in “potential opportunities and challenges of incorporating GenAI into students’ multimodal composition process.” Jiang frames the article within composition and writing studies and the theory behind multimodal composition. She builds upon recent pedagogical best practices put forward by Burriss and Leander (2024) that “call upon teachers and educators to engage in the development of an emergent pedagogy of critical AI that “teach[es] about/with AI in emergent, flexible, and speculative ways.” The results of the study emphasize that, while GenAI can streamline workflow and provide examples from which students can build using their own creativity, there were clear limitations to the technology. Of course, students’ realization of these limitations is a success of the course’s pedagogy. The article also provides three case studies of the student compositions as exemplars of the outcome. Jiang concludes with a recommendation “that researchers and educators engage in meaningful dialogues with students about their uses of GenAI during composition practices.” She quotes her own earlier work (Jiang et al. 2024), where she writes that to keep AI out of the classroom “is not only idealistic and impossible... it is actually completely disengaged from the realities of the changing technological landscape students are already facing.”

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Mehlenbacher, Brad, Ana Patricia Balbon, and Ashley Rose Mehlenbacher. 2024. “Synthetic Genres: Expert Genres, Non-Specialist Audiences, and Misinformation in the Artificial Intelligence Age.” ''Journal of Technical Writing and Communication'', January 31. https://doi.org/10.1177/00472816231226249.'''
&lt;/div&gt;

Genre theorists Mehlenbacher et al. examine which AI-generated texts are “good enough” to pass as “bona fide” (already a “very good” standard). They argue AI-generated text produces misinformation, pushes apart definitions of “information” and “knowledge,” and necessitates rhetorical understanding. The authors therefore believe “synthetic genres” will emerge, departing in situation, form, and even “the very concept of genre users” based on recursive and “poisoned” outputs. In reviewing literature, the authors spotlight AI-generated disinformation’s suasive (instead of propagandistic or accurate) potential, and argue that AI-generated text can be suasive by appearing both “timely” and “appropriate.” However, this “fraudoscientific” text can never be truly “timely” or “appropriate,” as it is always constrained in past work, and only responds to prompts, not situations. Despite this, AI-generated text generated on specialist subjects can still be effectively suasive—and even when identified as AI—because its authority is difficult to challenge. Mehlenbacher et al. therefore conduct two studies of AI-generated outputs, focusing on how they may be deceptive or detected. They first prompted GPT-3 to emulate rhetorical research abstracts by generating a range of definitions alongside text to emulate research processes. Next, they conducted a genre analysis, generating text on controversial topics and prioritizing suasiveness over ability to pass a theoretical “Genre Turing Test.” Based on their results, Mehlenbacher et al. suggest AI-generated text should be cross examined with specialist texts to identify where they need additional development, presenting a valuable teaching opportunity which supports “a powerful way to introduce the epistemic functions of writing.” Non-specialists should also develop tools to identify the source and quality of content, including diverse genre perspectives. The authors conclude by arguing genre scholars should further consider AI-generated texts and emphasizing the importance of genre users. This is because “genre must be understood in a rhetorical context,” while “synthetic genres” can only act as “statistical simulacrum.”

== Teaching and Pedagogy ==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Adewumi, Tosin, Lama Alkhaled, Christopher Buck, Sergio Hernandez, Sofia Brilioth, Memoona Kekung, Yasmin Ragimov, and Emily Barney. 2023. “ProCoT: Stimulating Critical Thinking and Writing of Students through Engagement with Large Language Models (LLMs).” Preprint, ''arXiv'', December 15. https://doi.org/10.48550/arXiv.2312.09801&lt;nowiki/&gt;.'''
&lt;/div&gt;

Adewumi et al.'s Probing Chain-of-Thought (ProCoT) methodology represents a pedagogical approach that transforms LLM interaction from potential academic dishonesty into an active learning process centred on critical evaluation and evidence-based reasoning. ProCoT requires students to generate initial outputs using LLMs, then systematically affirm or refute each claim using peer-reviewed references, effectively making the AI output a provisional hypothesis to be tested rather than a final answer to be submitted. This approach directly addresses the section's themes of process transparency (the method makes visible each stage of knowledge construction, from initial AI generation through source verification to synthesis) and ethical reflection (students must grapple with AI limitations including hallucination, bias, and lack of disciplinary nuance). The authors' finding that student outputs using ProCoT were significantly more concise than LLM-generated text (208 vs. 391 words on average) while demonstrating enhanced critical thinking suggests that the method trains students to distill and synthesize rather than accept verbose AI output uncritically. ProCoT leverages AI's epistemological weaknesses as pedagogical strengths—the fact that ChatGPT cannot reliably cite sources becomes an opportunity for students to develop information literacy by finding and evaluating primary literature. The method's anti-cheating design is secondary to its pedagogical value: by requiring iterative engagement with AI outputs and scholarly sources, ProCoT embeds the kind of metacognitive reflection (What did the AI get right? What did it miss? How do I know?) that is of significance to pedagogy in the AI era. The authors' evidence from 65 students across disciplines demonstrates feasibility across contexts, emphasizing cross-disciplinary rather than field-specific approaches to AI-entangled pedagogy. 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Berry, David M. 2023. “AI, Ethics, and Digital Humanities.” In ''The Bloomsbury Handbook to the Digital Humanities'', edited by James O’Sullivan, 445–57. Bloomsbury Academic. https://recoveryhub.siue.edu/wp-content/uploads/2024/10/AI-Ethics-and-Digital-Humanities-.pdf&lt;nowiki/&gt;.'''
&lt;/div&gt;

Berry emphasizes that AI’s use in the field of Digital Humanities raises major ethical questions despite it being an apparent evolution of the field’s traditional utilization of technology to augment human research capabilities. Berry outlines this issue by comparing the modern rise of AI to Digital Humanities’ early history, highlighting that digital humanists operated as coders until they began to “'black box' the computational aspects of doing digital humanities,” thus enabling non-programmers to participate. Since AI “automating processes might cover over ethical issues by transferring them into the hashtables of the machine-learning system,” Berry argues uncritical reliance on AI tools by inexpert modern humanists risks the “algorithmization” and imposition of hierarchical, quantitative frameworks upon Digital Humanities studies. He further identifies that the field of Digital Humanities is “on the cusp of a new set of packages that will further democratize access to machine learning,” a noble goal, but one which will bring these issues to the forefront. For this reason, Berry argues a reconsideration of ethics within Digital Humanities is desperately required on both organizational and individual levels.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Brown, Richard. 2023. ''The AI Generation: How Universities Can Prepare Students for the Changing World''. DEMOS and University of London report. https://demos.co.uk/wp-content/uploads/2023/11/The-AI-Generation-2.pdf&lt;nowiki/&gt;.'''
&lt;/div&gt;

Brown argues AI will inevitably and dramatically impact all fields of education, and therefore encourages universities to seize the opportunity to lead these changes instead of merely reacting to them. His voice is echoed by esteemed organizations DEMOS and the University of London, indicating that this shift in the academic environment is already beginning. Brown argues this shift is required due to the developing capacity of AI for automating low-skilled professional tasks, an ability which risks decimating the available number of entry-level graduate positions. As a result, how employers value the workplace skills taught by current curriculums will change drastically, meaning universities must revolutionize their approach to education. Brown provides a blueprint for how universities can adapt to these changes by championing education’s prioritization of “GRASP” (General Relational, Analytic, Social, and Personal) skills as an alternative, advising universities to focus on teaching high-level and tailored skills to students instead of the generic. Universities can do this by practising “active learning” over traditional lecture formats as well as fostering extracurricular and work experience opportunities for their students.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Deng, Ruiqi, Maoli Jiang, Xinlu Yu, Yuyan Lu, and Shasha Liu. 2025. “Does ChatGPT Enhance Student Learning? A Systematic Review and Meta-Analysis of Experimental Studies.” ''Computers &amp; Education'' 227. https://doi.org/10.1016/j.compedu.2024.105224&lt;nowiki/&gt;.'''
&lt;/div&gt;

Deng and colleagues' meta-analysis of 69 experimental studies provides empirical grounding for claims about ChatGPT's pedagogical impact, revealing both opportunities and methodological challenges in assessing AI-enhanced learning. Their finding that ChatGPT interventions improve academic performance, affective-motivational states, and higher-order thinking propensities while reducing mental effort speaks directly to how assessment must shift when AI augments cognition—if mental effort decreases but learning outcomes improve, traditional measures of &quot;effort&quot; or &quot;struggle&quot; as proxies for learning may require recalibration. In their critique of current assessment methodologies the authors demonstrate that most studies evaluate only final outputs (essay quality, test scores) rather than learning processes, missing opportunities to examine how students interact with AI, what metacognitive strategies they develop, and whether AI use builds transferable skills or creates dependency. Deng et al.'s four methodological propositions—using complex project-based assessments that reveal process, evaluating long-term rather than novelty effects, prioritizing objective over self-reported measures of higher-order thinking, and employing adequate statistical power—provide a research agenda for pedagogy–AI scholarship that centres process evidence. Their documentation of disciplinary variation (language education dominates current research) while calling for cross-disciplinary synthesis focuses on avoiding discipline-specific approaches. The meta-analysis also reveals gaps in understanding collaboration (few studies examine peer learning dynamics when AI is present) and metacognition (limited research on whether students develop awareness of their own and AI's knowledge boundaries), highlighting the resulting pedagogical transformations.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Grigoli, L. Renato. 2023. “Ghosts in the Machine.” ''American Historical Association'' 61 (3). https://www.historians.org/wp-content/uploads/2024/07/Perspectives_61N3.pdf&lt;nowiki/&gt;.'''
&lt;/div&gt;

Grigoli dismisses fears of AI generated essays threatening academic integrity by arguing that “if the development of artificial intelligence results in the death of the humanities, then it will be because it will have shown that the emperor has no clothes.” He uses ChatGPT to demonstrate that although AI responses appear competent at a passing glance, they lack valuable substance, simply arranging facts in a way that “tricks the reader into… doing all the analytical work.” Clear critical analysis should be the core component of a successful humanities essay, making well-designed assessments of this field far more reliable than those focused on information retention (like engineering). Therefore, AI is not a real threat, but a valuable pedagogical tool which can demonstrate examples of clean prose and prompt students to critically analyze what constitutes critical analysis. Essentially, if an AI generated answer can pass a test, the real problem was &quot;self-inflicted&quot; by either the examiner or the question itself.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Lee, Daniel, and Edward Palmer. 2025. “Prompt Engineering in Higher Education: A Systematic Review to Help Inform Curricula.” ''International Journal of Educational Technology in Higher Education'' 22: 16. https://doi.org/10.1186/s41239-025-00503-7&lt;nowiki/&gt;.'''
&lt;/div&gt;

Lee and Palmer's systematic review establishes prompt engineering as an emergent pedagogical practice that integrates with longstanding traditions of scholarly inquiry, questioning, and rhetoric. The authors synthesize multiple frameworks (AIPROMT, CLEAR, CRISPE) that codify prompting as a learnable skill involving role specification, context provision, instruction clarity, and iterative refinement—revealing how interaction with LLMs mirrors Socratic dialogue, research question formulation, and the rhetorical tradition of audience awareness. This work positions &quot;prompting as pedagogy&quot; as a reconfiguration of existing scholarly literacies: students learning to prompt effectively must articulate their information needs precisely, anticipate how language shapes output, and iteratively refine queries based on initial results—all core practices in library research, database searching, and scholarly conversation. The authors document how educators are embedding prompt engineering across disciplines, from technical fields where students prompt AI to generate code or solve equations, to humanities contexts where prompting becomes a form of textual analysis (understanding what linguistic patterns trigger particular AI responses reveals implicit biases and training data influences). Their review also identifies ethical dimensions—well-designed prompts can mitigate AI hallucination and bias, while poorly constructed prompts amplify these issues—making prompt literacy a matter of scholarly responsibility. The authors' call for curricula that teach prompting as interdisciplinary competency aligns with how AI entangles with pedagogy across boundaries, reshaping what counts as fundamental scholarly practice in an AI-augmented knowledge environment.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Mai, Dang Thi Thuy, Cuong Van Da, and Nguyen Van Hanh. 2024. “The Use of ChatGPT in Teaching and Learning: A Systematic Review through SWOT Analysis Approach.” ''Frontiers in Education'' 9: 1328769. https://doi.org/10.3389/feduc.2024.1328769&lt;nowiki/&gt;.'''
&lt;/div&gt;

Mai and colleagues' systematic SWOT analysis of 51 studies on ChatGPT in education, organized through Biggs' 3P model (Presage-Process-Product), offers comprehensive mapping of how generative AI enters and transforms pedagogical systems at multiple scales—from individual learner characteristics (Presage) through interactive teaching-learning processes (Process) to learning outcomes and assessment products (Product). This multilevel framework reveals that ChatGPT's pedagogical impact cannot be isolated to single moments of use but ripples across entire learning ecologies: at the Presage level, ChatGPT shifts what prior knowledge students need (familiarity with prompting interfaces) and what instructor competencies are required (ability to design AI-aware assignments); at the Process level, it transforms interaction patterns from teacher–student and student–student to include human–AI dialogue that may enhance personalized scaffolding but risks reducing peer collaboration; at the Product level, it necessitates fundamental assessment redesign because traditional evaluation instruments (timed essays, closed-book exams) lose validity when AI can generate competent responses. The authors' characterization of ChatGPT as simultaneously &quot;friend&quot; (enabling personalized learning, reducing educator workload, providing instant feedback) and &quot;foe&quot; (enabling plagiarism, potentially reducing critical thinking, creating over-reliance) mirrors the section's emphasis on entanglement—pedagogy cannot simply embrace or reject AI but must negotiate tensions between efficiency and effort, personalization and depersonalization, augmentation and replacement. Mai et al.'s documentation of how educators are adapting curricula to emphasize creativity and critical thinking (skills less easily automated) while using ChatGPT for routine information provision demonstrates pedagogical evolution toward distinctly human capacities. Their call for assessment reform using complex case studies, portfolios, and process documentation rather than single-sitting exams directly supports the notion of process evidence and metacognition as being central to AI-era pedagogy, positioning assessment not as gatekeeping but as making learning processes transparent and accountable.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Oates, Angela, and Donna Johnson. 2025. “ChatGPT in the Classroom: Evaluating Its Role in Fostering Critical Evaluation Skills.” ''International Journal of Artificial Intelligence in Education'' 35 (4): 1793–1824. https://doi.org/10.1007/s40593-024-00452-8&lt;nowiki/&gt;.'''
&lt;/div&gt;

Oates and Johnson's empirical study of biomedical science master's students offers insight into how AI functions more effectively as object of critical study than as production tool, revealing pedagogical value in making AI outputs subjects for evaluation rather than endpoints of learning. Their finding that students' marks did not improve when submitting AI-generated essays but did improve when critically evaluating AI outputs demonstrates a fundamental pedagogical principle: learning occurs not in consuming AI-generated content but in interrogating it, comparing it against disciplinary standards, identifying its factual errors and rhetorical limitations, and articulating why human-authored scholarship differs. This shifts pedagogy from &quot;use AI to complete tasks&quot; toward &quot;use AI to understand knowledge construction itself&quot;—students learn about evidence evaluation, citation practices, and argumentation by analyzing where ChatGPT succeeds and fails at these scholarly fundamentals. The authors document that ChatGPT demonstrated structural coherence and grammatical accuracy but lacked the disciplinary depth and synthetic insight expected in graduate work, making visible to students the difference between surface-level fluency and genuine expertise. Their emphasis on user interaction as a variable affecting efficacy underscores that pedagogy must address not just whether AI is present but how students are taught to engage it—prompt design, output evaluation, and integration with human research become learnable scholarly practices. Oates and Johnson's conclusion that students preferred writing their own essays despite AI's availability suggests that when pedagogy centres process transparency and critical evaluation rather than output efficiency, students recognize and value the cognitive work that AI cannot replicate, focusing on pedagogy that treats AI as entangled phenomenon requiring simultaneous use and critique.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Pope, Andrew, and Rongqian Ma. 2024. “Exploring Historians’ Critical Use of Generative AI Technologies for History Education.” ''Proceedings of the Association for Information Science and Technology'' 61 (1): 1071–73. https://doi.org/10.1002/pra2.1188&lt;nowiki/&gt;.'''
&lt;/div&gt;

Pope and Ma conducted semi-structured interviews of seven history professors to assess their attitudes toward employing GenAI tools in their teaching. Understanding this stance is important because Pope and Ma believe incoherent and mismatched approaches could inhibit scholarly communication and undermine academic integrity. The survey demonstrated historians had major concerns about GenAI’s development, especially regarding plagiarism. Respondents were particularly divided on whether copying an AI’s work was academic misconduct. However, historians had far fewer concerns about using GenAI to &quot;augment&quot; human abilities or tailor support to students—although senior academics maintained substantially greater reservations. The historians that were interviewed concurred that critiquing AI generated text could improve a student’s media literacy. Pope and Ma’s study suggests that historians consistently doubt the quality of AI generated responses even when willing to employ it.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Tan, Myles Joshua Toledo, and Nicholle Mae Amor Ttan Maravilla. 2024. “Shaping Integrity: Why Generative Artificial Intelligence Does Not Have to Undermine Education.” ''Frontiers in Artificial Intelligence'' 7: 1471224. https://doi.org/10.3389/frai.2024.1471224&lt;nowiki/&gt;.'''
&lt;/div&gt;

Tan and Maravilla provide theoretical grounding for understanding how generative AI can be integrated into pedagogy without compromising academic integrity, arguing that responsible implementation depends on alignment with constructivist learning theory and self-determination theory. The authors position AI not as a threat to authentic learning but as a catalyst that necessitates pedagogical transformation—shifting from transmission models toward environments where students actively construct knowledge using AI as one tool among many. Their framework emphasizes process transparency through explicit discussion of AI's role in knowledge construction and ethical reflection through examining how GAI outputs are generated, what assumptions they embed, and where they may mislead or constrain inquiry. This work addresses pedagogy-as-entanglement by showing how GAI forces educators to make visible the epistemic practices that traditional assessment often left implicit: citation tracing, source evaluation, argument construction, and the iterative nature of scholarly writing. Tan and Maravilla argue that rather than banning AI to preserve integrity, educators should redesign assessment to require demonstration of process—portfolios showing prompt refinement, comparison of AI outputs with human-authored sources, and metacognitive reflection on when and why AI was consulted. Their synthesis of educational theory with practical implementation strategies makes this work useful for understanding how pedagogy must evolve to treat AI as both subject matter (what students must understand about how AI functions) and scaffolding (how AI can support learning when used transparently and reflectively).

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Yim, Iris Heung Yue, and Jiahong Su. 2025. “Artificial Intelligence (AI) Learning Tools in K-12 Education: A Scoping Review.” ''British Journal of Educational Technology'' 56 (1): 169–196. https://doi.org/10.1007/s40692-023-00304-9&lt;nowiki/&gt;.'''
&lt;/div&gt;

Yim and Su's scoping review of AI literacy education in K-12 contexts provides grounding for understanding how pedagogy approaches AI as an object of study, not merely as a tool, revealing how students across age groups learn to understand, critique, and create with AI systems. The authors document how intelligent agents (Google Teachable Machine, Learning ML) and software platforms (Scratch, Python) enable students to engage with AI's underlying mechanisms—training models, observing how data shapes outputs, and experiencing firsthand how algorithmic decision-making operates. This approach treats AI as epistemological phenomenon: students don't just use pretrained models but build simple systems themselves, making visible how AI &quot;learns&quot; and where its learning breaks down (limited training data, biased datasets, inability to generalize beyond training conditions). Yim and Su's synthesis of pedagogical strategies—project-based learning where students create AI applications, human-computer collaboration examining how humans and machines complement each other, and game-based approaches making AI concepts accessible—demonstrates how educators scaffold understanding from concrete manipulation to abstract reasoning about intelligence and automation. The review's attention to cognitive, affective, and behavioural learning outcomes moves beyond narrow skill acquisition to examine how AI literacy shapes students' broader epistemic stance: understanding AI's capabilities and limitations, recognizing when algorithmic solutions are appropriate, and developing critical awareness of AI's social implications. Their emphasis on age-appropriate pedagogies and the importance of unplugged activities (learning AI concepts through physical manipulation before digital implementation) provides models for how pedagogy must adapt to learners' developmental stages when teaching about AI systems. This work's K-12 focus complements higher education studies in this section by showing how foundational AI literacy built through hands-on exploration creates readiness for more sophisticated critical engagement with AI as both tool and object of study in advanced scholarship.

== Service and Peer Review ==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Checco, Alessandro, Lorenzo Bracciale, Pierpaolo Loreti, Stephen Pinfield, and Giuseppe Bianchi. 2021. “AI-Assisted Peer Review.” ''Humanities and Social Sciences Communications'' 8: 25. https://doi.org/10.1057/s41599-020-00703-8&lt;nowiki/&gt;.'''
&lt;/div&gt;

Checco et al.'s study represents crucial early (pre-GenAI) empirical work demonstrating that AI can predict peer review outcomes based on &quot;superficial&quot; manuscript features—readability metrics, formatting consistency, reference list structure, linguistic patterns—with surprising accuracy, training neural networks on 3,300 conference papers to correlate these proxy measures with eventual accept/reject decisions. This finding has profound implications for understanding AI's operational role: the research reveals that much of what passes as peer review judgment operates on detectable patterns (clear writing, proper citation formatting, adherence to disciplinary conventions) that AI can identify and assess, potentially automating routine quality checks and flagging submissions unlikely to meet standards. However, the authors explicitly position their work as supporting &quot;semi-automated&quot; rather than fully automated review, emphasizing AI's role in pre-screening and administrative tasks (matching manuscripts with reviewers based on topic modelling, identifying obvious deficiencies) rather than intellectual evaluation. The paper's most valuable contribution lies in its systematic exploration of ethical implications: algorithmic bias risks (AI might penalize unconventional but innovative work, discriminate against non-native English writers, favour institutional prestige markers), transparency requirements (making AI decision criteria auditable), and the necessity of human oversight to prevent automation from calcifying existing disciplinary hierarchies. By documenting both AI's predictive capabilities on operational dimensions and its inherent limitations on substantive judgment, Checco et al. provide empirical foundation for designing peer review systems where AI handles standardized identification tasks while human expertise remains authoritative for evaluative assessment, directly instantiating the core principle that operational assistance must not migrate into epistemic territory.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Hosseini, Mohammad, and Serge P. J. M. Horbach. 2023. “Fighting Reviewer Fatigue or Amplifying Bias? Considerations and Recommendations for Use of ChatGPT and Other Large Language Models in Scholarly Peer Review.” ''Research Integrity and Peer Review'' 8 (1): 15. https://doi.org/10.21203/rs.3.rs-2587766/v1&lt;nowiki/&gt;.'''
&lt;/div&gt;

Published early in the ChatGPT era, Hosseini and Horbach's analysis provides a prescient examination of how LLM integration transforms both the pragmatics and ethics of peer review labour. The authors document LLMs' potential to combat reviewer fatigue by automating time-consuming tasks—transforming informal reviewer notes into polished reports, generating structured feedback on manuscript sections, identifying linguistic or formatting issues—thereby potentially expanding the pool of contributors who can participate effectively despite language barriers or time constraints. However, the article's core contribution lies in its still-useful systematic identification of risks that emerge when operational assistance crosses into epistemic territory: LLMs trained on existing literature may amplify disciplinary biases (favouring established paradigms over novel approaches), geographic biases (privileging research contexts well-represented in training data), or methodological orthodoxies (flagging unconventional designs as errors rather than innovations). The authors demonstrate through examples how ChatGPT can generate cynical or biased reviews that violate Mertonian norms of universalism, and how confidentiality breaches can occur when reviewers input manuscript excerpts into external AI platforms without institutional safeguards. Hosseini and Horbach's recommendations—mandatory disclosure of LLM use in reviews, human accountability for all AI-generated content, training in bias recognition, and institutional policies prohibiting upload of confidential materials—have influenced subsequent journal guidelines and provide foundational ethical framework for understanding why guardrails against leakage and disclosure norms become operational necessities rather than optional best practices in AI-entangled peer review systems.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Shcherbiak, Anna, Hooman Habibnia, Robert Böhm, and Susann Fiedler. “Evaluating Science: A Comparison of Human and AI Reviewers.” ''Judgment and Decision Making'' 19 (2024): e21. https://doi.org/10.1017/jdm.2024.24&lt;nowiki/&gt;.'''
&lt;/div&gt;

In this study, a large-scale field experiment comparing GPT-4 with human reviewers on conference abstracts provides empirical evidence about AI's capabilities and limitations in evaluative judgment. It demonstrates that while AI can approximate human performance on certain classification tasks—identifying &quot;very best&quot; abstracts shows moderate alignment—detailed evaluative assessments reveal persistent gaps, with human-AI agreement comparable to human-human variability, suggesting AI does not systematically outperform baseline reviewer disagreement. Critically, the research shows humans substantially outperform AI at detecting AI-generated versus human-written content, with detection tools like GPTZero exhibiting higher accuracy than GPT-4 itself when evaluating authorship. This finding has direct implications for peer review integrity when AI-generated manuscripts enter the submission pipeline. The authors position AI as effective for prescreening—rapidly filtering submissions for basic quality thresholds, identifying obvious errors, flagging compliance issues—while demonstrating it lacks the contextual understanding necessary for nuanced scientific judgment about significance, impact, or methodological soundness. The paper's methodological rigour in isolating human-versus-AI performance dimensions provides context for understanding where operational assistance (screening) legitimately ends and where human evaluative authority (substantive assessment) must begin, directly addressing the guiding principle that human judgment remains central even in AI-augmented workflows.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Lim, Gim Hui, M. L. Tan, V. C. W. Hoe, and D. Koh. 2025. “Generative AI in Peer Review Process for Occupational Health.” ''Occupational Medicine'' 75 (5): 242–49. https://doi.org/10.1093/occmed/kqaf051.'''
&lt;/div&gt;

Lim and colleagues' empirical study comparing Microsoft Copilot, ChatGPT, and Google Gemini against human reviewers on eight occupational health manuscripts provides granular quantitative evidence about AI's operational capabilities and limitations in peer review tasks. The research demonstrates that AI tools significantly outperform humans in providing feedback (mean score 3.44 vs. human baseline, p&lt;0.001) across dimensions of relevance, completeness, accuracy, error identification, and constructiveness—documenting AI's strength in systematic checking tasks like identifying missing citations, flagging methodological inconsistencies, noting formatting errors, and pointing out unclear explanations. However, humans substantially outperform AI in generating actionable recommendations (mean score 3.36, p&lt;0.01), with AI showing particular deficiencies in suggesting substantive revisions, connecting findings to broader literature, or identifying conceptual limitations. This performance asymmetry instantiates the operational/epistemic division: AI excels at identification tasks (what's wrong, what's missing) but struggles with evaluative tasks (how to improve, what matters). The study also quantifies efficiency gains (AI reviews complete in 11 minutes versus 45 for humans) while documenting critical limitations: AI outputs contain fabricated references, generate plausible-sounding but inaccurate technical assertions, and require human verification to prevent propagation of errors. Lim et al.'s work demonstrates that even when AI shows superior performance on specific metrics, its integration into peer review requires careful task decomposition—leveraging speed and comprehensiveness for checking functions while preserving human authority for substantive guidance—making it essential evidence for designing hybrid human-AI workflows where operational assistance enhances rather than replaces evaluative expertise.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Sun, Zhuanlan. 2025. “Large Language Models in Peer Review: Challenges and Opportunities.” ''Scientometrics'' 130 (10): 5503–5546. https://doi.org/10.1007/s11192-025-05440-w&lt;nowiki/&gt;.'''
&lt;/div&gt;

Sun provides essential mapping of LLM applications across the peer review lifecycle, categorizing five distinct operational roles: checklist assistants for formatting and protocol adherence, reviewer selection aids that match manuscripts with appropriate expertise, feedback generators for preliminary assessments, bias detectors that flag methodological or statistical irregularities, and agents that coordinate multi-stage review workflows. The article systematically examines technical approaches including prompt engineering strategies, model evaluation frameworks, and architectural designs for integrating LLMs into editorial management systems. The author argues that while LLMs excel at standardized operational tasks—checking reference integrity, identifying duplicated content across submission databases, verifying compliance with reporting guidelines—they remain fundamentally limited in assessing research novelty, theoretical contributions, and domain-specific methodological rigour. The analysis emphasizes that current LLM limitations (inadequate scientific validation, domain knowledge gaps, inability to analyze complex datasets, ethical concerns around bias perpetuation) position them as supportive tools within human-led processes rather than autonomous decision-makers. This work is useful in understanding operational versus epistemic divisions of labour in AI-assisted scholarship service and documenting the technical infrastructure through which AI becomes entangled with peer review operations while maintaining clear boundaries around human evaluative judgment.

== AI and Scholarship Infrastructures ==

=== Organizational Infrastructures ===

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Batool, Amna, Didar Zowghi, and Muneera Bano. 2025. “AI Governance: A Systematic Literature Review.” ''AI and Ethics'' 5: 3265–3279. https://doi.org/10.1007/s43681-024-00653-w&lt;nowiki/&gt;.'''
&lt;/div&gt;

Batool and colleagues' (2025) systematic literature review offers a comprehensive mapping of AI governance across multiple levels—team, organization, industry, national, and international. The authors utilize a structured analytical framework that examines who governs (stakeholders and roles), what is governed (data, algorithms, systems), when governance occurs (stages in the AI lifecycle), and how it is implemented (frameworks, tools, policies). The article reveals that current governance practices remain fragmented and inconsistent, with significant gaps at the national and international levels. Applied to the context of higher education, this multi-level perspective is essential for understanding how research institutions must position themselves within broader governance ecosystems. Because organizational governance currently operates without clear external scaffolding, research institutions are often forced to improvise institutional arrangements rather than implement established templates. While the paper is broad in scope, its categorization of governance artifacts illuminates the range of mechanisms available to scholarly organizations: from technical tools like algorithmic auditing to organizational structures like ethics committees. Ultimately, the authors' findings highlight the challenges facing research institutions as they attempt to coordinate AI oversight across distributed, autonomous units—such as libraries implementing discovery tools or IT departments deploying infrastructure—demonstrating why cross-functional coordination is both necessary and difficult when existing governance structures were not designed to span these boundaries.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Hadley, Emma, Alan Blatecky, and Megan Comfort. 2025. “Investigating Algorithm Review Boards for Organizational Responsible Artificial Intelligence Governance.” ''AI and Ethics'' 5: 2485–2495. https://doi.org/10.1007/s43681-024-00574-8&lt;nowiki/&gt;.'''
&lt;/div&gt;

Hadley and colleagues provide empirical documentation of algorithm review boards (ARBs) as organizational governance mechanisms, interviewing technical contributors across sectors to examine ARB membership, scope, success factors, and limitations. Their findings reveal ARBs as cross-functional bodies integrating diverse expertise (technical specialists, ethicists, domain experts, legal advisors, non-specialist stakeholders) to review AI systems for potential risks and harms, operating alongside other responsible AI approaches like policies, audits, and dedicated governance roles. The study's key insight that institutional review boards alone prove insufficient for algorithm governance and that ARBs function most effectively when integrated with existing organizational processes rather than operating as isolated oversight bodies speaks directly to research institutions' governance challenges. The article's documentation of financial tensions between profit motives and responsible AI costs, while focused on commercial contexts, translates to research institutions facing pressure to adopt AI for efficiency gains while managing ethical risks with constrained resources. Hadley et al.'s call for standardized ARB effectiveness metrics points to the broader challenge of demonstrating governance value in organizations where responsible AI practices compete with other institutional priorities for attention and investment.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Janssen, Marijn. 2025. “Responsible Governance of Generative AI: Conceptualizing GenAI as Complex Adaptive Systems.” ''Policy and Society'' 44 (1): 38–51. https://doi.org/10.1093/polsoc/puae040&lt;nowiki/&gt;.'''
&lt;/div&gt;

Janssen's conceptual article reframes generative AI governance as managing complex adaptive systems characterized by co-evolution, emergent properties, and non-linear interactions between technical and social elements, directly challenging technology-deterministic approaches that treat AI as static tool requiring one-time organizational accommodation. This systems perspective is essential for understanding why research institutions struggle with AI governance: the article demonstrates how AI systems and organizational contexts mutually shape each other through feedback loops, making governance an ongoing adaptive process rather than implementation of fixed policies. Janssen argues that effective organizational stewardship requires holistic, outward-focused governance attending to how AI systems interact with broader organizational processes, public values, and societal concerns—moving beyond narrow risk mitigation to address joint accountability across system components including people, policies, data, and algorithms. For research institutions embedding AI in knowledge infrastructures, this framing illuminates why isolated departmental responses prove insufficient: cataloging systems using AI for metadata generation, research platforms deploying AI for literature synthesis, and administrative systems using AI for resource allocation together constitute an organizational AI ecosystem whose emergent behaviours cannot be governed through component-level oversight alone. The article's emphasis on selecting and combining appropriate policy instruments into adaptive governance packages provides conceptual foundation for cross-functional coordination mechanisms, suggesting that effective institutional stewardship requires deliberate orchestration of technical standards, organizational procedures, and stakeholder engagement processes that together shape AI's organizational trajectory. Janssen's work underscores that AI governance is not primarily technical implementation challenge but organizational transformation requiring institutions to develop new capabilities for managing sociotechnical co-evolution.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Papagiannidis, Emmanouil, Patrick Mikalef, and Kieran Conboy. 2025. “Responsible Artificial Intelligence Governance: A Review and Research Framework.” ''The Journal of Strategic Information Systems'' 34 (2): 101885. https://doi.org/10.1016/j.jsis.2024.101885&lt;nowiki/&gt;.'''
&lt;/div&gt;

Papagiannidis and colleagues provide theoretical grounding for understanding how organizations operationalize responsible AI principles through governance structures. Their scoping review synthesizes disparate literature to construct a conceptual framework differentiating between structural practices (formal roles, committees, reporting lines), relational practices (stakeholder engagement, accountability mechanisms), and procedural practices (auditing protocols, monitoring systems) across the AI lifecycle. This tripartite framework is valuable for research institutions navigating the challenge of translating broad ethical commitments into actionable organizational arrangements. The article explicitly addresses how governance antecedents like leadership commitment and regulatory pressure shape implementation, and how governance practices in turn affect outcomes like trust, compliance, and innovation capacity. The authors' critical reflection on responsible AI governance reveals tensions inherent to institutional stewardship: between centralized oversight and distributed expertise, between standardized protocols and context-sensitive judgment, between rapid AI deployment and deliberative ethical review. For research organizations managing AI's entanglement with knowledge infrastructures, this work provides vocabulary and analytical categories for diagnosing governance gaps and designing institutional responses that embed responsibility throughout organizational systems rather than treating ethics as external constraint.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Weber, Michael, Martin Engert, Norman Schaffer, Jörg Weking, and Helmut Krcmar. 2023. “Organizational Capabilities for AI Implementation—Coping with Inscrutability and Data Dependency in AI.” ''Information Systems Frontiers'' 25: 1549–1569. https://doi.org/10.1007/s10796-022-10297-y&lt;nowiki/&gt;.'''
&lt;/div&gt;

Weber and colleagues identify four organizational capabilities essential for AI implementation, addressing AI's distinctive characteristics that distinguish it from previous information technologies: inscrutability (difficulty predicting probabilistic outputs and explaining decision processes) and data dependency (reliance on high-quality, continuously updated data for system performance). Their capability framework—encompassing AI Project Planning, Co-Development, Data Management, and AI Model Lifecycle Management—provides actionable guidance for research institutions developing internal capacity to steward AI systems. The article's grounding in expert interviews from diverse organizational contexts reveals that AI implementation failures often stem not from technical deficits but from organizational incapacity to manage sociotechnical complexity: inscrutability requires enhanced planning and stakeholder communication practices to align expectations around uncertain outcomes, while data dependency demands robust governance of data quality, provenance, and evolution throughout systems' operational lives. For research organizations, these capabilities map onto critical institutional functions: libraries developing metadata systems must manage data quality for AI cataloguing tools; research offices supporting computational scholarship must plan projects acknowledging unpredictable AI behaviour; IT departments maintaining infrastructure must implement lifecycle management ensuring model performance doesn't degrade as institutional data changes. The article's emphasis on Co-Development capability—bringing together technical specialists, domain experts, and end-users to jointly shape AI systems—speaks directly to cross-functional coordination challenges in research institutions where AI touches multiple organizational domains. Weber et al.'s framework reveals that organizational stewardship requires not just governance structures (committees, policies, review processes) but operational capabilities (planning methods, collaboration practices, technical procedures) embedded in day-to-day institutional work. This capability perspective shifts attention from abstract principles to concrete organizational competencies that determine whether responsible AI rhetoric translates into institutional practice.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Wu, Chuhao, He Zhang, and John M. Carroll. 2024. “AI Governance in Higher Education: Case Studies of Guidance at Big Ten Universities.” Preprint, ''arXiv'', September 3. https://doi.org/10.48550/arXiv.2409.02017&lt;nowiki/&gt;.'''
&lt;/div&gt;

Wu and colleagues provide rare empirical documentation of how major research universities translate AI governance principles into institutional practice, examining guidance documents from fourteen Big Ten universities to identify organizational patterns and role-specific strategies. Their analysis reveals three key organizational dimensions: multi-unit governance involving information technology departments, teaching and learning centres, libraries, and research offices operating with distributed authority rather than centralized control; role-specific guidance differentiating expectations for faculty, students, staff, and researchers rather than applying uniform policies; and educational-advisory approaches emphasizing learning and adaptation over compliance enforcement. This case-study evidence illuminates the pragmatic challenges research institutions face when operationalizing AI oversight: how to coordinate across functional silos with different mandates, expertise, and risk tolerances; how to balance flexibility (needed because AI applications vary dramatically across contexts) with consistency (needed to ensure institutional values are upheld); how to position governance as enabling innovation rather than constraining it. The article's documentation of specific institutional mechanisms, such as data classification systems limiting what information can be shared with AI tools, or Socratic guidance approaches that pose questions rather than dictate answers, provides concrete examples of organizational stewardship in action. For understanding AI's organizational entanglement with knowledge infrastructures, this work demonstrates how governance emerges through negotiation among multiple institutional actors, each bringing domain expertise and jurisdictional claims, requiring coordination mechanisms that existing organizational charts may not accommodate.

=== Publishing, Communication, Engagement Infrastructures ===

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Bergstrom, Tracy, and Dylan Ruediger. 2024. “A Third Transformation? Generative AI and Scholarly Publishing.” ''Ithaka S+R''. October 30, 2024. https://doi.org/10.18665/sr.321519&lt;nowiki/&gt;.'''
&lt;/div&gt;

Drawing on interviews with leaders from publishers, technology disruptors, academic libraries, and scholarship, Bergstrom and Ruediger map the strategic landscape of AI adoption across the publishing industry. The report identifies a bifurcated future: an incrementalist scenario where AI produces efficiency gains without fundamentally altering industry dynamics, versus a transformative scenario creating disruption comparable to or exceeding previous digital transformations. For search and discovery, most interviewees anticipate heavy AI impact, with tools already expanding capabilities through summarization and chatbot interfaces—potentially disrupting the linear progression from discovery to understanding by introducing AI-enabled synthesis. For peer review, interviewees expressed optimism that AI could address chronic strain through &quot;pre-review&quot; feedback, assistance with copy editing and misconduct detection, and more efficient reviewer identification, while raising concerns about accuracy, confidentiality, and maintaining human judgment in evaluation. The authors document a competitive threat from large technology companies: scenarios where commercial LLMs become default interfaces for accessing scholarly content pose significant challenges to publisher positioning. Content licensing to foundation model developers offers clear monetization paths, but broader revenue implications remain uncertain. The analysis identifies a critical research integrity challenge: ensuring transparent standards for AI usage while upholding provenance, attribution, reproducibility, and transparency in an environment of increasing automation. Smaller publishing organizations may struggle to match larger entities' adaptive capacity, potentially accelerating industry consolidation. 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Broussard, Meredith. 2023. “The Challenges of AI Preservation.” ''The American Historical Review'' 128 (3): 1378–81. https://doi.org/10.1093/ahr/rhad366.'''
&lt;/div&gt;

Broussard illustrates how the current impermanence of digital storage is producing a nightmare for future historians, as content is hidden away by licensing agreements or simply disappears when its host platform ceases to exist. Earlier ideals of the internet preserving a “complete first draft of history” are far from the reality, and problems only intensify when considering the development of AI, which Broussard compares to the printing press. For example, one could access a record of a physical newspaper published on a given day, but Google Search’s software is constantly changing with no canonical daily version, which means no historian could ever hope to examine a comparable snapshot of an AI. Operations like the Internet Archive and the development of emulation can help diminish losses, but it must be recognized that the digital world is decaying.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Buitrago-Ciro, Jairo, Marta Samokishyn, Rachel Moylan, Jonathan Hernández Pérez, Oluwabunmi Bakare-Fatungase, and Carmel Firdawsi. 2025. “Bridging the AI Gap: Comparative Analysis of AI Integration, Education, and Outreach in Academic Libraries.” ''IFLA Journal'' 51 (3): 682–702. https://doi.org/10.1177/03400352251325274. '''
&lt;/div&gt;

Buitrago-Ciro et al. examine the websites of 40 libraries in North America, Western Europe, Latin America, and Africa to explore how they have integrated AI technologies into their services, policies, and outreach efforts. Overall, the authors found a geographic divide in the integration of AI into library services, because almost all North American and European libraries had AI educational outreach activities and resources, while only five (out of ten) Latin American libraries and one (out of ten) African libraries did outreach activities. However, AI integration into library services and development of library AI policies and guidelines was more uncommon across all regions, as less than half of North American and European libraries engaged in these activities, while only one library in Latin America and one in Africa integrated AI into their services and none had specific library AI policies. These regional differences in AI integration stem from each region’s socioeconomic contexts, social inequalities, and technological gaps that present additional challenges for AI adoption in African and Latin American libraries. 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Gulson, Kalervo N., and P. Taylor Webb. 2023. “Steering the Mind Share: Technology Companies, Policy and Artificial Intelligence Research in Universities.” ''Discourse: Studies in the Cultural Politics of Education'' 44 (2): 195–207. https://doi.org/10.1080/01596306.2021.1981828. '''
&lt;/div&gt;

Gulson and Webb (2023) examine how major technology companies are actively reshaping the landscape of artificial intelligence research within universities. Drawing on interviews with computer scientists as part of a broader international project, the authors investigate three key areas: the influence of tech companies on AI research practices, the policy frameworks that foster academia-industry collaborations, and the role of &quot;open science&quot; in facilitating the transfer of academic ideas to the corporate sector. The study highlights that the boundaries between academic and corporate research have become highly porous. Companies like Google do not merely act as external funders; they are deeply embedded within university ecosystems, actively steering research directions. Furthermore, the authors illustrate how national policies, such as Canada’s Pan-Canadian Artificial Intelligence Strategy, legitimize and accelerate this corporate influence by heavily incentivizing industry partnerships. While these collaborations provide universities with crucial resources and drive innovation, Gulson and Webb warn that they also raise significant concerns regarding conflicts of interest and the corporatization of open science. Ultimately, the authors argue that corporate funding creates powerful feedback loops among tech companies, policymakers, and academics, effectively allowing industry to capture the &quot;mind share&quot; of university research.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Kousha, Kayvan, and Mike Thelwall. 2024. “Artificial Intelligence to Support Publishing and Peer Review: A Summary and Review.” ''Learned Publishing'' 37 (1): 4–12. https://doi.org/10.1002/leap.1570&lt;nowiki/&gt;.'''
&lt;/div&gt;

Kousha and Thelwall provide a systematic mapping of AI tool deployment across the scholarly publishing pipeline, distinguishing demonstrated capabilities from promotional claims. For journal recommendation, the review documents AI-powered systems, including Springer Nature Journal Suggester, Wiley Journal Finder, IEEE Publication Recommender, and JANE (Journal/Author Name Estimator), that analyze text similarity with previously published articles and reports high accuracy rates for appropriate journal matching. The analysis of initial quality control covers a diverse toolkit for plagiarism detection, robot author detection, methods checking, automated statistical verification, transparency and reproducibility checking and manuscript structure validation. Commercial systems draw on databases to suggest appropriate reviewers; the Natural Science Foundation of China's AI-assisted reviewer recommender for grant applications reports approximately 80% accuracy. However, the review identifies a critical boundary: while AI proves effective for finding reviewers and conducting initial quality checks, its value in performing the actual substantive review process &quot;has not been clearly demonstrated.&quot; The synthesis reveals that substantial efficiency improvements are achievable in labour-intensive administrative tasks, while human judgment remains integral to core intellectual evaluations—a distinction essential for understanding where AI integration in publishing will proceed incrementally versus face fundamental obstacles.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Ma, Lai. 2024. “Generative AI for Academic Publishing? Some Thoughts About Epistemic Diversity and the Pursuit of Truth.” ''KULA: Knowledge Creation, Dissemination, and Preservation Studies'' 7 (1): 1–5. https://doi.org/10.18357/kula.287.'''
&lt;/div&gt;

Ma (2024) critiques the integration of generative AI in academic publishing, arguing that the drive for automation threatens the central values of epistemic diversity and bibliodiversity. By invoking the &quot;Sokal Hoax,&quot; the author illustrates the danger of AI-generated &quot;bullshit&quot;—content that mimics the formal structures of scholarship while remaining devoid of actual meaning. Ma specifically uses Scopus AI as a case study to demonstrate how the platformization of scholarly data creates a feedback loop that reinforces the &quot;Matthew Effect,&quot; where established, English-language, and well-resourced publications are disproportionately amplified. This process, Ma warns, leads to &quot;epistemic injustice&quot; by marginalizing non-Western research and niche topics that are underrepresented in training datasets. The paper serves as a vital warning: without robust data surveillance and human-centric safeguards, the AI-accelerated publishing model may exacerbate peer-review crises and citation monopolies, ultimately undermining the public trust and diverse knowledge creation that open scholarship aims to protect.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Mitchell, Peta, Michelle Riedlinger, Jake Goldenfein, Aaron Snoswell, Jean Burgess, and Kevin Witzenberger. 2025. “Research Genai: Situating Generative AI in the Scholarly Economy.” ''AoIR Selected Papers of Internet Research''. https://doi.org/10.5210/spir.v2024i0.14006.'''
&lt;/div&gt;

Mitchell et al. focus upon the oft-overlooked subfield of Generative AI tools known as “RGAI”, research-focused models which they argue represent “complex sociotechnical systems.” Hepp et al.’s definition of AI as a “sensitizing concept” and Watermeyer’s consideration of AI as a “labor accelerator” are used to situate this argument within the “scholarly economy” before the authors expand upon these theories, arguing RGAI should be approached as a form of “platform capitalism” akin to academia.edu. To evidence this stance, the authors examine the highly distinct RGAI models “Consensus” and “Writefull” as case studies. “Consensus” is designed to produce an academic “ConsensusMeter” by combining a proprietary LLM with OpenAI technology, while “Writefull” “aims to simplify… the often challenging task of scholarly writing” by employing custom AI models. Mitchell et al. highlight that although both tools are presented as independent and bespoke, they have major corporate backing. This deeply conflicts with the research principles of open scholarship, so Mitchell et al. aim to develop an index of RGAI which are appropriate for use in research.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Pividori, Milton, and Casey S. Greene. 2024. “A Publishing Infrastructure for Artificial Intelligence (AI)-Assisted Academic Authoring.” ''Journal of the American Medical Informatics Association'' 31 (9): 2103–13. https://doi.org/10.1093/jamia/ocae139&lt;nowiki/&gt;.'''
&lt;/div&gt;

The Manubot AI Editor implements a concrete technical solution to the provenance problem in AI-assisted scholarship through three integrated components: a Python library, a GitHub Actions workflow, and a prompt generator. This architecture addresses provenance directly: all changes are tracked through version control, creating a clear audit trail distinguishing human-authored from machine-generated text and documenting exactly how AI suggestions were accepted, modified, or rejected. Evaluation proceeded through five case studies using both human and automated assessment. Human evaluators assessed whether revisions preserved original meaning and important details, avoided introducing incorrect information, and maintained correct formatting. Automated &quot;LLM-as-a-Judge&quot; iterative assessment evaluated paragraph pairs across criteria including sentence structure clarity, ease of understanding, and grammatical correctness. The evaluations found that models could grasp complex academic concepts and enhance text quality, with particular effectiveness in text-based sections like introductions and discussions. The human-in-the-loop design, where AI suggestions function as proposed edits rather than direct insertions, mitigates risks of incorrect information while preserving authorial agency over final content.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Razack, Habeeb Ibrahim Abdul, Sam T. Mathew, Fathinul Fikri Ahmad Saad, and Saleh A. Alqahtani. 2021. “Artificial intelligence-assisted tools for redefining the communication landscape of the scholarly world.” ''Science Editing''. https://doi.org/10.6087/kcse.244. '''
&lt;/div&gt;

Razack et al. argue AI will transform publishing into a technology-driven industry, streamlining dissemination of scholarship “for the betterment of humankind.” Exploring current trends via case studies, they emphasize AI’s impact upon human performance over its independent “creative” role. They argue AI could benefit the “prospective” researcher by predicting an article’s “citation impact,” identifying evolving research trends, and locating relevant research journals to publish in, cutting past low-charging and “predatory OA journals” which “malign integrity” by publishing “compromised content.” Meanwhile, “retrospective” editors could employ AI to detect plagiarism, streamline peer review, and format publications. For Razack et al., the rise of AI can therefore be compared to the rise of the typewriter, swift adoption likely promoting &quot;human-machine collaboration&quot; over replacement.

=== Accountability-related Infrastructures ===

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Ngulube, Patrick, and Neema Florence Vincent Mosha. 2024. “Integrating Artificial Intelligence-Based Technologies ‘Safely’ in Academic Libraries: An Overview through a Scoping Review.” ''Technical Services Quarterly'' 42 (1): 46–67. https://doi.org/10.1080/07317131.2024.2432093&lt;nowiki/&gt;.'''
&lt;/div&gt;

Ngulube and Mosha (2025) conduct a scoping review examining the state of research on ethical issues and perceived risks in AI integration within academic libraries. Analyzing 28 studies published before 2024, the authors reveal that research on safe AI adoption in libraries remains nascent, with significant gaps in theoretical grounding and methodological diversity. The review identifies critical ethical concerns including algorithmic bias, privacy violations, reduced transparency and accountability, and job displacement—yet finds that existing literature disproportionately emphasizes employment risks while neglecting environmental and planetary impacts. The authors note that ethical considerations have not taken centre stage in library and information science research, as evidenced by the scarcity of relevant keywords and abstracts in the literature. A major finding is that most studies employ quantitative methodologies at the expense of qualitative and mixed-methods approaches, and only 18% employ explicit theoretical frameworks. The review underscores that academic libraries must navigate the dual challenge of leveraging AI's operational efficiencies while ensuring ethical standards of inclusivity, accessibility, and fair information use—a task complicated by the absence of established best practices and the need for human-centred approaches to AI governance.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''“Realising Potential, Supporting Users: IFLA Statement on Copyright and Artificial Intelligence.” n.d. IFLA. Accessed May 1, 2025. https://www.ifla.org/news/realising-potential-supporting-users-ifla-statement-on-copyright-and-artificial-intelligence/. '''
&lt;/div&gt;

This statement aims to help IFLA member libraries in navigating copyright issues and developing programs relevant to AI, positioning libraries as innovators “uniquely situated to lead” in supporting, training, and utilizing AI. However, restrictions stem from rightsholders, economic and moral copyright laws, and health, safety, and privacy laws. Libraries should therefore be guided by the most appropriate policy sources to mitigate restrictions by ensuring AI tools do not compromise areas of concern. Libraries are further recommended to advise decision-makers to permit mining legally accessed content, address bias by promoting “the widest possible access,” build capacity, awareness, and training for evolving technologies, and monitor AI standards. Governments are recommended to follow existing human rights regulations, avoid using copyright law as a “blunt force tool,” develop ethical AI practices, and fund repositories of AI training data—alongside AI companies themselves. Both rightsholders and vendors are advised to avoid language in contracts which restricts the use of AI or prevents exceptions. Overall, this document aims to promote AI by making as much content available as possible.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Werder, Karl, Balasubramaniam Ramesh, and Rongen (Sophia) Zhang. 2022. “Establishing Data Provenance for Responsible Artificial Intelligence Systems.” ''ACM Transactions on Management Information Systems'' 13 (4): 1–25. https://doi.org/10.1145/3503488&lt;nowiki/&gt;.'''
&lt;/div&gt;

Werder et al. provide a framework for understanding audit trails in the context of AI and research data management, arguing that robust data provenance is not merely a technical feature but a prerequisite for achieving accountability in AI systems. They detail the requirements for a comprehensive provenance system, capable of tracking data from its origin through various transformations and into model training and deployment. This is directly relevant to research infrastructures, as it outlines how repositories and data management platforms can and must evolve to support AI-driven research. The authors’ multi-layered architectural proposal offers a concrete vision for how a research institution could implement a system to audit data pipelines, identify sources of bias, and ensure regulatory compliance. By connecting provenance to the broader goal of “Responsible AI,” the paper provides the conceptual tools for evaluating whether a research infrastructure’s data governance is sufficient to handle the accountability challenges posed by AI.

== Audience ==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''de Angelis, Luigi, Francesco Baglivo, Guglielmo Arzilli, Gaetano Pierpaolo Privitera, Paolo Ferragina, Alberto Eugenio Tozzi, and Caterina Rizzo. “ChatGPT and the Rise of Large Language Models: The New AI-Driven Infodemic Threat in Public Health.” ''Frontiers in Public Health'' 11 (2023): 1166120. https://doi.org/10.3389/fpubh.2023.1166120&lt;nowiki/&gt;.'''
&lt;/div&gt;

De Angelis and colleagues examine the emergence of Large Language Models, particularly ChatGPT, as a novel public health threat through the lens of &quot;AI-driven infodemic.&quot; The authors trace the rapid evolution of LLMs from earlier transformer-based models through GPT-3 to ChatGPT, highlighting how each iteration has increased the capacity to generate fluent, authoritative-sounding text at scale. Critically, they identify a fundamental misalignment problem: despite efforts to fine-tune these models through reinforcement learning from human feedback, LLMs remain prone to generating plausible-sounding but factually incorrect or fabricated information—a vulnerability particularly dangerous in medical and health contexts. The paper's central argument is that the unprecedented speed and volume at which LLMs can produce convincing content creates conditions for misinformation spread on a scale previously impossible, especially among non-expert publics who lack the epistemic resources to detect AI-generated falsehoods. The authors emphasize that the inability to reliably detect AI-produced text compounds this threat, undermining public trust in scientific institutions and potentially influencing health-related behaviours and policy decisions. The work demonstrates how LLM-mediated scientific communication poses distinct risks to knowledge integrity and public understanding, requiring urgent development of detection mechanisms, governance frameworks, and media literacy initiatives to protect audiences from AI-driven epistemic harm.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Bryant, Rebecca. 2024. “Implementing an AI Reference Chatbot at the University of Calgary Library.” ''Hanging Together'', December 12. https://hangingtogether.org/implementing-an-ai-reference-chatbot-at-the-university-of-calgary-library/&lt;nowiki/&gt;.'''
&lt;/div&gt;

Bryant (2024) details the development and implementation of &quot;T-Rex,&quot; an AI-powered reference chatbot at the University of Calgary Library, based on a webinar hosted by the OCLC Research Library Partnership. While the library had offered live chat services since the early 2010s, the COVID-19 pandemic caused a massive surge in demand, peaking at over 3,000 inquiries in a single month. To alleviate this strain, the library analyzed past chat transcripts and determined that 12–14% of inquiries were simple, directional questions suitable for automation. To prevent scope creep during the initial training phase, the development team focused on a core set of fifty common questions. Through continuous refinement, the chatbot has since expanded to encompass over 1,000 custom responses, though its effectiveness remains limited by the availability of existing library webpages or FAQs to draw from. Bryant concludes by summarizing the Calgary team's key insights for institutions developing similar tools: developers must anticipate out-of-scope or non-library questions, recognize that users prefer direct answers over links to webpages, program creative responses for off-topic queries, and prepare for user resistance or non-adoption.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Hara, Noriko, Eugene Kim, Shohana Akter, and Kunihiro Miyazaki. 2025. “Exploring the Dynamics of Interaction About Generative Artificial Intelligence Between Experts and the Public on Social Media.” ''Journal of Science Communication'' 24 (1): A02. https://doi.org/10.22323/2.24010202&lt;nowiki/&gt;.'''
&lt;/div&gt;

Hara and colleagues conduct an empirical investigation into how experts and the public co-produce knowledge about generative AI on social media, specifically analyzing X (formerly Twitter) discussions. Rather than treating the public as passive consumers of expert knowledge, the authors adopt a Public Engagement with Science (PES) framework that recognizes social media platforms as dynamic arenas where non-experts actively contribute to shaping collective understanding of emerging technologies. Through computational and manual analysis, they identify distinct discussion topics, map the roles that both experts and laypeople play in knowledge production, and examine how engagement metrics correlate with these roles. A critical finding is that the public functions beyond questioners seeking expert guidance, but rather as active knowledge co-producers who share practical insights, challenge claims, and contribute their own perspectives and experiences with GenAI tools. This research demonstrates how AI itself—as a subject of discourse—becomes a site of negotiated meaning-making between differently positioned actors. The work moves beyond traditional one-way dissemination models to reveal the interactive, participatory nature of contemporary science communication, with implications for understanding how diverse audiences collectively construct understanding of transformative technologies and how this co-productive process shapes both public perception and the future development of AI systems.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Jaillant, Lise, Olivia Mitchell, Eric Ewoh-Opu, and Maribel Hidalgo Urbaneja. 2025. “How Can We Improve the Diversity of Archival Collections with AI? Opportunities, Risks, and Solutions.” ''AI &amp; Society'' 40: 4457–4459. https://doi.org/10.1007/s00146-025-02222-z. '''
&lt;/div&gt;

Jaillant et al. draw from interviews with 20 academics and archival professionals to explore how AI technologies can help address the lack of diversity in archival collections. The authors highlight that AI tools can assist in automatically detecting racist or inappropriate language in metadata, search large amounts of historical records, and uncover new insights within archival records. However, the authors argue that the deployment of AI should involve close collaboration between librarians, archivists, and developers. The current limited collaboration between developers and libraries limits the ethical and inclusive application of AI in archival collections, especially those with sensitive historical materials. The interviewees also warned against the loss of historical context when using AI, the perpetuation of archival biases, and the loss of control when AI tools are designed and governed by tech companies. To conclude, the authors recommend investing in interdisciplinary AI training programs for archivists, educating AI developers about the unique needs of archives so they can create more relevant solutions, and creating professional guidelines about the best practices for AI use to address the lack of diversity in archival collections.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Peters, Uwe, and Benjamin Chin-Yee. 2025. “Generalization Bias in Large Language Model Summarization of Scientific Research.” ''Royal Society Open Science'' 12 (4): 241776. https://doi.org/10.1098/rsos.241776&lt;nowiki/&gt;.'''
&lt;/div&gt;

Peters and Chin-Yee provide rigorous, large-scale empirical evidence of a systematic and consequential distortion in LLM-generated scientific summaries: the tendency toward overgeneralization. Testing ten prominent LLMs—including ChatGPT-4o, ChatGPT-4.5, DeepSeek, LLaMA 3.3 70B, and Claude 3.7 Sonnet—on 4,900 summaries of scientific abstracts and full-length articles, the authors demonstrate that even when explicitly prompted for accuracy, most LLMs consistently produce conclusions broader and more definitive than those warranted by the original research. Critically, they identify three specific mechanisms of overgeneralization: the use of generic statements that obscure quantification, the shift from past to present tense (which expands scope), and the omission of qualifiers and limitations. The findings are stark: LLM-generated summaries were nearly five times more likely than human-authored summaries to contain broad generalizations (odds ratio = 4.85, 95% CI [3.06, 7.70], p &lt; 0.001), with newer models performing worse than earlier ones. This research is foundational for understanding how AI-mediated knowledge communication systematically distorts scientific findings at scale, regardless of user expertise or intent. The work demonstrates a concrete mechanism through which LLM intermediation can alter the epistemic content of research, with particular implications for medical and clinical contexts where overgeneralized conclusions can directly influence policy and patient care. The authors propose mitigation strategies including temperature adjustment and systematic benchmarking, but their findings underscore the profound challenge of ensuring faithful knowledge transmission through AI systems.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''da Silva Cardoso, Heike, and Vitor Rocio. 2025. “Enhancing Digital Libraries Through NLP and Recommender Systems: Current Trends and Future Prospects with Large Language Models.” In ''Technology and Innovation in Learning, Teaching and Education: TECH-EDU 2024'', edited by Arsénio Reis, José P. Cravino, Leontios Hadjileontiadis, Paulo Martins, Sofia B. Dias, Sofia Hadjileontiadou, and Tassos Mikropoulos, 69–79. C''ommunications in Computer and Information Science'' 2480. Cham: Springer. https://doi.org/10.1007/978-3-032-02672-9_5&lt;nowiki/&gt;.'''
&lt;/div&gt;

da Silva Cardoso and Rocio propose a practical framework for integrating Natural Language Processing and Large Language Models into academic digital libraries to address the information overload facing researchers, students, and faculty. Recognizing that traditional search methods have become insufficient in the face of exponential publication growth, the authors advocate for AI-driven recommender systems capable of delivering precise, relevant, and personalized literature recommendations. Their contribution centres on an audience-aware design philosophy that positions librarians as essential partners in system development. Rather than treating AI as a purely algorithmic solution, the authors emphasize that librarians' direct interactions with users provide irreplaceable insight into the nuanced and context-dependent needs of diverse academic communities. This human-in-the-loop approach represents a noteworthy methodological stance: AI functions not as a replacement for human expertise but as a tool to augment librarian knowledge and enhance the responsiveness of knowledge discovery systems. The work is particularly salient for understanding how contemporary LLM-based systems can be designed to serve scholarly audiences more effectively while maintaining the institutional wisdom and user-centred perspective that librarians bring to information work.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Taneja, Ankit Kumar, and Chandra Tripathi. 2020. “AI-Powered Recommender Systems: Personalization and Bias.” ''Turkish Journal of Computer and Mathematics Education (TURCOMAT)'' 11 (1): 1090–1094. https://doi.org/10.61841/turcomat.v11i1.14406&lt;nowiki/&gt;.'''
&lt;/div&gt;

Though published before the generative AI era, Taneja and Tripathi's analysis of AI-powered recommender systems remains foundational to understanding algorithmic bias in information discovery. The authors examine the structural tensions inherent in personalization algorithms—systems designed to enhance user experience by tailoring content suggestions yet simultaneously capable of constructing &quot;filter bubbles&quot; and &quot;echo chambers&quot; around users. By continuously recommending content similar to previous engagement, these algorithms systematically exclude novel, dissenting, or interdisciplinary perspectives, undermining serendipitous discovery essential to genuine scholarly inquiry. Critically, the authors frame algorithmic bias not as a technical glitch but as a structural risk embedded within the information architectures that guide knowledge-seekers, and thus they expose how algorithmic personalization—a feature predating generative AI—already demonstrated the capacity to narrow intellectual diversity and reinforce pre-existing beliefs. This pre-GenAI work provides historical context for understanding how contemporary AI systems have intensified these risks, making it useful for evaluating the ethical imperatives of designing systems that promote intellectual openness rather than epistemic closure.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''de Winter, J. 2024. “Can ChatGPT Be Used to Predict Citation Counts, Readership, and Social Media Interaction? An Exploration Among 2222 Scientific Abstracts.” ''Scientometrics'' 129: 2469–2487. https://doi.org/10.1007/s11192-024-04939-y&lt;nowiki/&gt;.'''
&lt;/div&gt;

De Winter’s study contrasts conventional scientometrics, testing whether a large language model can predict an article’s citation count and altmetric scores (whilst noting these may be unreliable assessors of actual scientific impact) by rating its abstract across “semantically diverse” variables. His case study uses ChatGPT-4 to predictively evaluate 2,222 abstracts from articles published in ''PLOS ONE'', monitoring its accuracy by referencing actual citation counts and altmetrics scores. De Winter employs a custom script to prompt OpenAI’s Application Programming Interface (API) to score each abstract on a scale of zero to one hundred across thirty positive variables and their thirty antonyms, which he then organizes under five categories (e.g. “Quality and Reliability”). As Chat-GPT 4 only produced consistent results at the population level, it was run three additional times to determine averages and bolster reliability of individual scores. This language-based evaluation of article abstracts revealed that ChatGPT-4’s scores better correlate with altmetrics and citation counts than conventional readability scores do. Furthermore, “Novel and Engaging” articles were most likely to be cited, whilst “Accessible and Understandable” articles scored highest in altmetrics.

{{Navigation|previous=AI and Social|next=Complete Alphabetical List of References}}

{{BookCat}}</text>
      <sha1>tpylx687mrpv3ke7vh2xqsnos1hqrir</sha1>
    </revision>
    <revision>
      <id>4656112</id>
      <parentid>4656110</parentid>
      <timestamp>2026-08-02T20:47:07Z</timestamp>
      <contributor>
        <username>CorreiaA</username>
        <id>3614427</id>
      </contributor>
      <minor />
      <origin>4656112</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="112403" sha1="9yc2pbohcezqqqahu9ohjzrpafue0ee" xml:space="preserve">== Research Methods and Practices ==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Arnett, Catherine, Eliot Jones, Ivan P. Yamshchikov, and Pierre-Carl Langlais. 2024. “Toxicity of the Commons: Curating Open-Source Pre-Training Data.” Preprint, ''arXiv'', October 29. https://doi.org/10.48550/arXiv.2410.22587.'''
&lt;/div&gt;

Open-source pretraining data is increasingly treated as a shared resource for building “open” language models, yet it can embed and reproduce harmful speech patterns at scale. Arnett, Jones, Yamshchikov, and Langlais argue that reducing toxic model behaviour requires intervening upstream in data, and they focus specifically on the distinctive constraints of public-domain corpora (including historical documents and OCR-derived text) where standard web-text toxicity filters can be impractical or ill-suited. They propose a fully open-source curation pipeline designed for these conditions and present three concrete contributions: (1) ToxicCommons, a custom-labelled dataset organized across five toxicity dimensions (racial/origin-based, gender/sex-based, religious, ability-based discrimination, and violence); (2) Celadon, a classifier trained on that dataset to detect toxic content more efficiently at scale in open data; and (3) a “balanced” filtration strategy that explicitly trades off safety filtering against retaining sufficient training material. The paper’s core claim is that open-data model development needs domain-attuned, auditable curation methods paired with task-specific classifiers, so that openness in data does not automatically translate into avoidable harms in downstream model outputs.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Bail, Christopher A. “Can Generative Artiﬁcial Intelligence Improve Social Science?” https://www.semanticscholar.org/paper/Can-Generative-Artiﬁcial-Intelligence-Improve-Bail/6206cc77bb3a3c0b6b9fce1ad68a8b1786a56941&lt;nowiki/&gt;.'''
&lt;/div&gt;

Bail (2023) provides a critical evaluation of how Generative Artificial Intelligence (AI), particularly Large Language Models (LLMs), might fundamentally transform computational social science. Moving beyond superficial administrative use cases, Bail examines the potential of LLMs to simulate complex human behaviours. He suggests that Generative AI could revolutionize agent-based modelling by replacing simplistic, rule-bound agents with dynamic, memory-equipped &quot;silicon samples&quot; capable of emergent group behaviours. While acknowledging the utility of AI for automated content analysis and expanding programming accessibility, Bail rigorously details the methodological and ethical perils of these largely opaque systems. He warns that the proprietary fine-tuning of commercial LLMs introduces severe demographic biases—often skewing toward highly educated, liberal perspectives—which threatens the external validity of AI-assisted research. Furthermore, Bail highlights the &quot;Stack Overflow Problem,&quot; cautioning that the unchecked proliferation of AI-generated &quot;junk science&quot; could contaminate future training data and degrade the broader scientific ecosystem. Ultimately, Bail argues that social scientists must not remain passive &quot;end-users&quot; of corporate AI. Instead, they must actively collaborate with computer scientists to reverse-engineer the &quot;social sense&quot; into AI models, ensuring the development of open-source, reproducible infrastructures that genuinely advance the study of human behaviour.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Bakharia, Aneesha, Antonette Shibani, Lisa-Angelique Lim, Trish McCluskey, and Simon Buckingham Shum. 2025. “From Transcripts to Themes: A Trustworthy Workflow for Qualitative Analysis Using Large Language Models.” In ''Joint Proceedings of LAK 2025 Workshops, co-located with the 15th International Conference on Learning Analytics and Knowledge (LAK 2025)''. Dublin, Ireland: CEUR-WS.org. https://ceur-ws.org/Vol-3995/LLMQUAL_paper1.pdf.'''
&lt;/div&gt;

Bakharia et al. explore the use of AI in qualitative, rather than quantitative, research in education. The authors define “minimum requirements that an LLM-supported qualitative analysis workflow must satisfy” and present a “LLM-based workflow that derives an initial set of themes” from text data that is “transferable to other LA [learning analytics] contexts performing qualitative analysis of open-ended text.” The authors define two requirements for “LLM-generated inductive coding”: first, it must verify “coded textual extracts… against source data” to make sure the quotes are accurate (i.e., verbatim and not hallucinated) and verify those extracts “are meaningfully classified under the assigned code.” Second, in the interest of transparency, it must “explain that rationale for each code” and “trace every code, whatever level of abstraction, back to its source data.” The article outlines and describes the proposed workflow in detail, including its being built in Python with a Jupyter notebook and Flask application. While they acknowledge challenges and problems in their research (e.g., LLM bias, the lack of comparable human analysis, the risk of alienating the human quality of qualitative research), Bakharia et al. ultimately advocate their approach as one that “improves transparency, verifiability, and interpretability, while addressing limitations of previous methods and enhancing researcher processes in qualitative thematic analysis&quot; (9). By adapting their minimum requirements and workflow, the authors argue, researchers can engage more effectively in LLM-driven qualitative research.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Dennstädt, Fabio, Cedric Sivert Möller, Tim Fellerhoff, Felix Busch, Oke Gerke, André Karch, and Oliver Krause. 2024. “Title and Abstract Screening for Literature Reviews Using Large Language Models: An Exploratory Study in the Biomedical Domain.” ''Systematic Reviews'' 13 (1): 158. https://doi.org/10.1186/s13643-024-02575-4&lt;nowiki/&gt;.'''
&lt;/div&gt;

Dennstädt et al. perform a study in which they attempt to determine the viability of using LLMs to automate scholarly literature surveys. The researchers developed a method for using LLMs to perform the title and abstract screenings of a systematic literature review method and applied that method with four LLMs across eleven datasets in biomedical literature. A key advantage of implementing LLMs in this process is that it escapes the need to train the machine via pre-selection. Researchers have developed automated and semi-automated processes for systematic literature reviews in the past, but this requires a human agent to provide training data or a corpus of example texts that tell the system what to look for. LLMs do not require this step. Instead, the researchers used a Python script that prompts the LLM “to evaluate the relevance of a scientific publication for inclusion into an SLR,” providing the LLM with both abstract and title, request for a numbered score indicating the relevance of the publication, and a numerical threshold that defines whether a score makes the given publication relevant. The authors characterize the results of the study as “promising” but also “far from perfect,” identifying that such applications could be helpful to researchers and are widely applicable without special training for data or user, even if “fully automated systems… still fail to differentiate… near the level of human evaluation.” The authors conclude that more research into the use of LLMs to automate systematic literature reviews is needed, but it seems very likely that scholars will employ LLMs into this integral research task with greater frequency in the future. How well LLMs will continue to perform in this task is unclear, especially in new research, and Dennstädt et al. clearly state, “we cannot answer the question of to what extent LLMs should be used for conducting literature reviews and for doing research.”

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Montague-Hellen, Beth. 2024. “Empowering Knowledge through AI: Open Scholarship Proactively Supporting Well Trained Generative AI.” ''Insights'' 37 (1). https://doi.org/10.1629/uksg.649.'''
&lt;/div&gt;

Generative AI is becoming a dominant interface for finding, summarizing, and producing academic information, with consequences for what counts as authoritative knowledge online. Montague-Hellen argues that, rather than focusing primarily on misuse, job displacement, or defensive copyright disputes, scholarly communications actors should actively encourage the inclusion of scholarly literature in generative AI training data to improve reliability and ensure research is represented in emerging discovery platforms. The article develops two main pathways for doing this: making scholarly outputs more machine-actionable and “crawlable” (especially through better linkage, metadata, and structured HTML rather than PDF-only dissemination) and making permissions unambiguous by explicitly addressing AI training in licences and related signals. It foregrounds “garbage in, garbage out” to claim that while libraries and publishers cannot remove low-quality web content from training corpora, they can tilt the balance by lowering friction for high-quality, curated research to be ingested legally. Montague-Hellen also highlights unresolved tensions around attribution and consent under common Creative Commons licences, suggesting that clearer, more specific permission frameworks (or new licensing patterns) may be needed to distinguish human reading from machine training and to communicate “enthusiastic consent” where desired.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Mugaanyi, Joseph, Christoph Lehner, and Lia M. Bally. 2024. “Evaluation of Large Language Model Performance and Reliability for Citation Generation Across Scientific Disciplines.” ''Journal of Medical Internet Research'' 26: e52935. https://doi.org/10.2196/52935&lt;nowiki/&gt;.'''
&lt;/div&gt;

Mugaanyi, Lehner, and Bally perform a study aimed at gauging the accuracy and reliability of citations generated by ChatGPT (GPT 3.5) in both the natural sciences and humanities. The authors emphasize that “Citations and references serve as the backbone of scholarly communication, providing the necessary context, evidence, and credit to prior works… ensuring the integrity of the research process.” With this in mind, the article frames the related study as aiding researchers in determining whether LLMs are viable as writing assistants in scholarly writing. In short, if an LLM cannot be relied upon to accurately cite and reference sources, it poses a risk to the integrity of research when incorporated into scholarly writing. The study found that ChatGPT hallucinated over a quarter of its references, with a slightly higher margin in the natural sciences. Furthermore, not all of those citations that did exist were accurate, and the LLM hallucinated DOIs for nearly 90% of the references it cited, real or otherwise, in the humanities. The issue, as the authors describe it, is that “in the current iteration of LLMs, since the training is geared toward generalization and the models are probabilistic, they tend to interpolate and fill in the missing information with synthetic text.” The authors conclude that, while domain-specific models may improve performance and reliability, in its current, generic form, researchers need to contemplate whether the strengths of ChatGPT’s reference generation justify its demonstrable limitations and “the importance of robust validation processes to ensure the accuracy and reliability of generated content.” 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Schroeder, Hope, Marianne Aubin Le Quéré, Casey Randazzo, David Mimno, and Sarita Schoenebeck. 2024. “Large Language Models in Qualitative Research: Uses, Tensions, and Intentions.” Preprint, ''arXiv'', October 9. https://arxiv.org/abs/2410.07362&lt;nowiki/&gt;.'''
&lt;/div&gt;

Schroder et al. perform interviews with twenty qualitative researchers in human computer interaction (HCI) and qualitative research to gauge how researchers are actually using LLMs and concerns over the incorporation of LLMs at different stages of research; the authors also provide a survey of the rise of LLMs and flag potential concerns, using both interviews and survey as a launchpad to outline suggestions and recommendations for researchers in the field contemplating the use of LLMs in their research. The authors are concerned that “the speed of LLM development has outpaced guidance on their ethical use” and “the HCI community is contending with the need for developed policies that tackle how to use AI ethically in research.” The most prominent concerns that the article raises relate to “ethics, unequal adoption of new technologies, model bias, and performance” as well as “concerns regarding participant privacy,” but there is also a larger issue within the field of HCI that “LLMs may lend the impression that qualitative inquiry can be automated, and their integration into Quantitative Data Analysis (QDA) software may increasingly impose positivist approaches that conflict with interpretivist traditions.” Key findings from the interviews are that most researchers are open to responsible use of LLMs but have concerns about established guidelines and norms for its implementation. Additionally, many are already using LLMs “to generate recruitment materials,” “speed up qualitative coding,” and “for ideation and feedback,” even as they acknowledge tensions between the qualitative nature of their work and the prospect of automation. The most significant recommendations that Schroder et al. make include updating consent forms, using dedicated tools rather than defaulting to Chat-GPT, and implementing design decisions specifically for LLM-incorporating methodologies that reconsider “participant privacy,” LLM’s “intentional use,” “transparency and validation,” “researcher context,” “deep engagement with data” despite this automation, and ways “to consider participant perspectives and interests” given “the variable performance LLMs have across contexts, knowledge domains, cultures, and languages.” The authors hope that incorporating these considerations will “empower qualitative researchers to leverage LLMs confidently, and even creatively, for their work.” 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Tumadóttir, Anna. 2024. “Questions for Consideration on AI &amp; the Commons.” ''Creative Commons'', July 24. https://creativecommons.org/2024/07/24/preferencesignals/.'''
&lt;/div&gt;

Tumadóttir talks about CC, license, tools, and policy and discusses the way to foster a healthy commons environment in the digital era. She points out how the introduction of the CC license enhanced Creative Commons by giving the creators choice over usage of their works. However, it is now a question if the same healthy commons can be maintained today because of rapid technological development. Preference signals for AI is a notion to give an agent (creator, rights holder, entity of some kind) more flexibility on how they want their work to be used for AI model training. However, the choice is still binary which is offering all or nothing. After consultations, it is found that people want more control over their work and if not, they might not share their work at all. Therefore, it is important to identify the right type of preference signals for it to be useful to benefit the public interest. During this process, we need to keep in mind its effect and variation on cultural heritage, different education sectors, and regions. Moreover, to make the preference signals effective, we need to examine its structure as well as whether legal enforcement is necessary.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Yue, Yongjie, Maosong Zheng, Jiahui Liu, Zhimin Wang, and Chenhui Mao. 2025. “A Practical Guide and Assessment on Using ChatGPT to Conduct Grounded Theory Studies: Step-by-Step Reporting of the Data Analysis Process.” ''Journal of Medical Internet Research'' 27: e70122. https://doi.org/10.2196/70122&lt;nowiki/&gt;.'''
&lt;/div&gt;

Yue et al. employ a study that entailed researchers using either manual coding or coding assisted by ChatGPT to perform data analysis on a 40,000 word dataset made up of interviews with 8 players of Listen and Play in Jianghu, a Chinese MMORPG designed for the blind. The study’s aim was to “provide detailed guidelines for using ChatGPT in grounded theory within the Chinese context,” “evaluate the effectiveness of ChatGPT coding” in this context, and “explore the broader implications and future directions of ChatGPT in qualitative research.” The article goes into great detail as to the process for generating open code with ChatGPT. The results of the study show that, although manual coding performed slightly better than ChatGPT-assisted coding, the “difference was not statistically significant” in its production of nodes and reference points. However, during axial coding, the categories and subcategories generated through these respective processes was significantly different, with only half of the categories semantically matching between manual and ChatGPT-assisted methods. The authors conclude that, while ChatGPT 4-Turbo “enhanced the diversity and efficiency of coding... it struggled with depth, context, subtle nuances, connections, and coding organization.” Nevertheless Yue et al. see great potential in the application of GenAI-assisted coding in grounded theory, especially as the technology develops. 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Zhu, Wenhao, Hongyi Liu, Qingxiu Dong, Jingjing Xu, Shujian Huang, Lingpeng Kong, Jiajun Chen, and Lei Li. 2023. “Multilingual Machine Translation with Large Language Models: Empirical Results and Analysis.” Preprint, ''arXiv'', April 10. https://arxiv.org/abs/2304.04675&lt;nowiki/&gt;.'''
&lt;/div&gt;

Zhu et al. perform an empirical study that tests the multilingual translation performance of eight popular LLMs on 102 languages. As the authors explain, this is a particularly difficult task as it requires “semantic alignment between languages.” While LLMs tend to perform surprisingly well at translation, “it is also unclear [sic] how LLM acquires translation ability and which factors affect LLM’s translation ability.” This study in multilingual machine translation (MMT) therefore seeks to answer two questions: how do LLMs perform MMT over massive languages and what factors affect their performance?

The results of the study suggest that GPT-4 generally outperforms its competitors but still falls short of Google Translate in some tests. Two key takeaways from this study are that “exemplars in the tail of the prompt have larger influence on an LLM’s behaviour,” meaning that the order in which exemplars are given within a prompt matter, and that cross-lingual translation pairs are particularly helpful exemplars to LLMs. The authors ultimately conclude that an “LLM can acquire translation ability in a resource-efficient way, which indicates [a] promising future of LLM in multilingual machine translation” as the technology evolves.

''NB: As this research was conducted prior to Google’s implementation of GenAI/LLMs into Google Translate in 2024, it sometimes uses Google Translate as a baseline/comparison point for LLM-powered translation that can be confusing without that context.''

== Forms of Research Output ==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Bozkurt, Aras. 2024. “GenAI et al.: Cocreation, Authorship, Ownership, Academic Ethics and Integrity in a Time of Generative AI.” ''Open Praxis'' 16 (1): 1–10. https://doi.org/10.55982/openpraxis.16.1.654&lt;nowiki/&gt;.'''
&lt;/div&gt;

Bozkurt’s essay seeks “to undertake a critical examination of the use of generative AI in academic contexts… examining its implications and exploring the nuances of its integration.” He begins with an assertion of technological determinism, stating “This technological shift… is not just a transient trend but a symbol of the inescapable change… marking the onset of an AI-dominated age and initiating profound and inevitable shifts in our academic and educational paradigms.” The author makes the argument that the advent of AI “requires us to critically reconsider concepts such as cocreation, ownership, and authorship in academic writing processes.” For instance, in exploring the concept of ownership, he briefly notes the ethical concerns of whether those who created the content upon which AI was trained might claim ownership of AI-generated content and explores the notions of AI or even its programmers acting as a co-author. Bozkurt himself takes the explicit stance that GenAI ought not be credited as a co-author. The paper also provides suggestions related to the ethics of AI use and transparency: “In some cases, merely reporting… is inadequate. A more nuanced approach involves providing multilayered statements acknowledging and benchmarking the use of [GenAI], specifying where, when, in which sections, and for what purposes it is employed.” Bozkurt reiterates that responsibility ultimately belongs to the human author, and provides the aiTARAS (Academic Integrity and Transparency in AI-assisted Research and Specification) Framework for this purpose. Bozkurt ends his essay by identifying further problems beyond the scope of the article, including “reimagining of assessment and evaluation,” our overfocus on ChatGPT and English language in this field of study, and the inaccuracy of AI detection software.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Colbert-Lewis, Danielle, Lawrence Maminta, Kelly McElroy, Graeme Slaght, and Mark Swartz. 2024. “The Citation Economy as a Site of Extraction for Surveillance Publishing.” ''Canadian Journal of Academic Librarianship'' 10 (December): 1–22. https://doi.org/10.33137/cjal-rcbu.v10.43293.'''
&lt;/div&gt;

Colbert-Lewis et al. (2024) examine the extractive nature of the modern &quot;citation economy,&quot; arguing that academic publishing has evolved into a powerful mechanism for surveillance and data commodification. The authors detail how a consolidated group of dominant publishers capture surplus value from the academic lifecycle by extracting free scholarly labour, research data, and personal information. Crucially, these corporations are transitioning from traditional information vendors into technology-driven data brokers. The extracted data is reinvested into proprietary analytics products that are then sold back to universities to evaluate and surveil faculty performance, relying on opaque metrics that threaten academic freedom. Furthermore, the authors highlight the severe ethical compromises inherent in this system, noting that academics inadvertently fuel data infrastructures that these same parent companies sell to external industries, including law enforcement and advertising. To combat the rise of &quot;surveillance publishing,&quot; the article concludes with actionable recommendations for scholars and librarians to resist exploitative practices and build ethical infrastructures, alongside a supplementary mini-zine designed to raise awareness about the hidden costs of participating in the citation economy.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Frangou, Sophia, Umberto Volpe, and Andrea Fiorillo. 2025. “AI in scientific writing and publishing: A call for critical engagement.” ''European Psychiatry'' 68 (1): e98. https://doi.org/10.1192/j.eurpsy.2025.10061&lt;nowiki/&gt;.'''
&lt;/div&gt;

Frangou, Volpe, and Fiorillo provide a succinct summary of the benefits of implementing AI in scientific writing and publishing, before turning to the challenges and risks posed toward the use of such technology. Finally, they end by posing ethical frameworks for the use of AI in both publishing and writing. In publishing, the authors identify tools that can aid in tasks ranging from copyediting to finding reviewers and claim that for both “high-volume publications” and “resource-constrained journals… AI can serve as a force multiplier, expanding what editorial teams can accomplish without compromising the centrality of human discretion and responsibility.” In writing, the article notes that “AI-powered applications offer a suite of tools that, when used judiciously, can enhance the quality, efficiency, and inclusivity of the scholarly communication process,” placing such tools along the trajectory of preexisting aids like EndNote and Zotero, which have also now incorporated AI. Frangou, Volpe, and Fiorillo argue that AI can help scholars identify relevant literature they might otherwise have trouble finding, reduce the linguistic bias encountered by scholars for whom English is not their first language, and aid scholars in navigating the publishing landscape so their work can find the best possible fit. Finally, the authors acknowledge the epistemic and ethical risks of AI: inconsistency and irreproducibility, transparency, informed consent, and data privacy are all core concerns. Key components in the article’s ethical frameworks for publishers and authors include transparency and disclosure, human accountability, and training and skill development. The authors hope that “these principles articulate a shared responsibility for shaping the role of AI in scientific publishing” and AI’s “adoption reinforces the foundational values that give scientific communication its trustworthiness and legitimacy.”

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Graßhoff, Gerd. 2024. “AI-Reporter: A Path to a New Genre of Scientific Communication.” Preprint, ''arXiv'', July 8. https://arxiv.org/abs/2507.05903. '''
&lt;/div&gt;

Graßhoff introduces a new tool, the AI-Reporter, that aims “to fundamentally expand scientific communication for the new era…”; according to Graßhoff, the AI-Reporter “creates a sustainable, referenceable, and expandable knowledge base that captures not just content but the living essence of scientific discourse.” In short, Graßhoff proposes a tool that will adapt a scientific presentation into a “public-ready chapter” in about three minutes with “only the author’s consent.” The majority of the article is dedicated to a tech-oriented breakdown of the methodology and workflow of the AI-Reporter, namely the semantic analysis and translation of a recorded slide presentation—consisting of the presentation as a PDF, video recording, and basic metadata—into a publication-ready chapter. Graßhoff’s tool is an attempt to solve what he identifies as a core problem of modern scholarly communication, namely that “knowledge is increasingly presented in dynamic, multimodal formats” that are ultimately ephemeral and content is often lost (14). He aims to refine this tool to enable real-time processing, multilingual support, interactive multimedia components, “optimization for academic disciplines,” and more to this project. He advocates the AI-Reporter as nothing less than “a vision for the future of scientific communication.”

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Jiang, Jialei. 2024. “When generative artificial intelligence meets multimodal composition: Rethinking the composition process through an AI-assisted design project.” ''Computers and Composition'' 74: 102883. DOI: https://doi.org/10.1016/j.compcom.2024.102883&lt;nowiki/&gt;.'''
&lt;/div&gt;

Jiang conducts a study in which GenAI is integrated into students’ composition of multimodal texts, then interviewed on their experience. Jiang’s states her aim as follows: “Through examining writing students use of GenAI tools in multimodal composition, this study seeks to unravel how GenAi technologies influence students’ design choices, problem-solving approaches, and the overall composition process.” In particular, Jiang is interested in “potential opportunities and challenges of incorporating GenAI into students’ multimodal composition process.” Jiang frames the article within composition and writing studies and the theory behind multimodal composition. She builds upon recent pedagogical best practices put forward by Burriss and Leander (2024) that “call upon teachers and educators to engage in the development of an emergent pedagogy of critical AI that “teach[es] about/with AI in emergent, flexible, and speculative ways.” The results of the study emphasize that, while GenAI can streamline workflow and provide examples from which students can build using their own creativity, there were clear limitations to the technology. Of course, students’ realization of these limitations is a success of the course’s pedagogy. The article also provides three case studies of the student compositions as exemplars of the outcome. Jiang concludes with a recommendation “that researchers and educators engage in meaningful dialogues with students about their uses of GenAI during composition practices.” She quotes her own earlier work (Jiang et al. 2024), where she writes that to keep AI out of the classroom “is not only idealistic and impossible... it is actually completely disengaged from the realities of the changing technological landscape students are already facing.”

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Mehlenbacher, Brad, Ana Patricia Balbon, and Ashley Rose Mehlenbacher. 2024. “Synthetic Genres: Expert Genres, Non-Specialist Audiences, and Misinformation in the Artificial Intelligence Age.” ''Journal of Technical Writing and Communication'', January 31. https://doi.org/10.1177/00472816231226249.'''
&lt;/div&gt;

Genre theorists Mehlenbacher et al. examine which AI-generated texts are “good enough” to pass as “bona fide” (already a “very good” standard). They argue AI-generated text produces misinformation, pushes apart definitions of “information” and “knowledge,” and necessitates rhetorical understanding. The authors therefore believe “synthetic genres” will emerge, departing in situation, form, and even “the very concept of genre users” based on recursive and “poisoned” outputs. In reviewing literature, the authors spotlight AI-generated disinformation’s suasive (instead of propagandistic or accurate) potential, and argue that AI-generated text can be suasive by appearing both “timely” and “appropriate.” However, this “fraudoscientific” text can never be truly “timely” or “appropriate,” as it is always constrained in past work, and only responds to prompts, not situations. Despite this, AI-generated text generated on specialist subjects can still be effectively suasive—and even when identified as AI—because its authority is difficult to challenge. Mehlenbacher et al. therefore conduct two studies of AI-generated outputs, focusing on how they may be deceptive or detected. They first prompted GPT-3 to emulate rhetorical research abstracts by generating a range of definitions alongside text to emulate research processes. Next, they conducted a genre analysis, generating text on controversial topics and prioritizing suasiveness over ability to pass a theoretical “Genre Turing Test.” Based on their results, Mehlenbacher et al. suggest AI-generated text should be cross examined with specialist texts to identify where they need additional development, presenting a valuable teaching opportunity which supports “a powerful way to introduce the epistemic functions of writing.” Non-specialists should also develop tools to identify the source and quality of content, including diverse genre perspectives. The authors conclude by arguing genre scholars should further consider AI-generated texts and emphasizing the importance of genre users. This is because “genre must be understood in a rhetorical context,” while “synthetic genres” can only act as “statistical simulacrum.”

== Teaching and Pedagogy ==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Adewumi, Tosin, Lama Alkhaled, Christopher Buck, Sergio Hernandez, Sofia Brilioth, Memoona Kekung, Yasmin Ragimov, and Emily Barney. 2023. “ProCoT: Stimulating Critical Thinking and Writing of Students through Engagement with Large Language Models (LLMs).” Preprint, ''arXiv'', December 15. https://doi.org/10.48550/arXiv.2312.09801&lt;nowiki/&gt;.'''
&lt;/div&gt;

Adewumi et al.'s Probing Chain-of-Thought (ProCoT) methodology represents a pedagogical approach that transforms LLM interaction from potential academic dishonesty into an active learning process centred on critical evaluation and evidence-based reasoning. ProCoT requires students to generate initial outputs using LLMs, then systematically affirm or refute each claim using peer-reviewed references, effectively making the AI output a provisional hypothesis to be tested rather than a final answer to be submitted. This approach directly addresses the section's themes of process transparency (the method makes visible each stage of knowledge construction, from initial AI generation through source verification to synthesis) and ethical reflection (students must grapple with AI limitations including hallucination, bias, and lack of disciplinary nuance). The authors' finding that student outputs using ProCoT were significantly more concise than LLM-generated text (208 vs. 391 words on average) while demonstrating enhanced critical thinking suggests that the method trains students to distill and synthesize rather than accept verbose AI output uncritically. ProCoT leverages AI's epistemological weaknesses as pedagogical strengths—the fact that ChatGPT cannot reliably cite sources becomes an opportunity for students to develop information literacy by finding and evaluating primary literature. The method's anti-cheating design is secondary to its pedagogical value: by requiring iterative engagement with AI outputs and scholarly sources, ProCoT embeds the kind of metacognitive reflection (What did the AI get right? What did it miss? How do I know?) that is of significance to pedagogy in the AI era. The authors' evidence from 65 students across disciplines demonstrates feasibility across contexts, emphasizing cross-disciplinary rather than field-specific approaches to AI-entangled pedagogy. 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Berry, David M. 2023. “AI, Ethics, and Digital Humanities.” In ''The Bloomsbury Handbook to the Digital Humanities'', edited by James O’Sullivan, 445–57. Bloomsbury Academic. https://recoveryhub.siue.edu/wp-content/uploads/2024/10/AI-Ethics-and-Digital-Humanities-.pdf&lt;nowiki/&gt;.'''
&lt;/div&gt;

Berry emphasizes that AI’s use in the field of Digital Humanities raises major ethical questions despite it being an apparent evolution of the field’s traditional utilization of technology to augment human research capabilities. Berry outlines this issue by comparing the modern rise of AI to Digital Humanities’ early history, highlighting that digital humanists operated as coders until they began to “'black box' the computational aspects of doing digital humanities,” thus enabling non-programmers to participate. Since AI “automating processes might cover over ethical issues by transferring them into the hashtables of the machine-learning system,” Berry argues uncritical reliance on AI tools by inexpert modern humanists risks the “algorithmization” and imposition of hierarchical, quantitative frameworks upon Digital Humanities studies. He further identifies that the field of Digital Humanities is “on the cusp of a new set of packages that will further democratize access to machine learning,” a noble goal, but one which will bring these issues to the forefront. For this reason, Berry argues a reconsideration of ethics within Digital Humanities is desperately required on both organizational and individual levels.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Brown, Richard. 2023. ''The AI Generation: How Universities Can Prepare Students for the Changing World''. DEMOS and University of London report. https://demos.co.uk/wp-content/uploads/2023/11/The-AI-Generation-2.pdf&lt;nowiki/&gt;.'''
&lt;/div&gt;

Brown argues AI will inevitably and dramatically impact all fields of education, and therefore encourages universities to seize the opportunity to lead these changes instead of merely reacting to them. His voice is echoed by esteemed organizations DEMOS and the University of London, indicating that this shift in the academic environment is already beginning. Brown argues this shift is required due to the developing capacity of AI for automating low-skilled professional tasks, an ability which risks decimating the available number of entry-level graduate positions. As a result, how employers value the workplace skills taught by current curriculums will change drastically, meaning universities must revolutionize their approach to education. Brown provides a blueprint for how universities can adapt to these changes by championing education’s prioritization of “GRASP” (General Relational, Analytic, Social, and Personal) skills as an alternative, advising universities to focus on teaching high-level and tailored skills to students instead of the generic. Universities can do this by practising “active learning” over traditional lecture formats as well as fostering extracurricular and work experience opportunities for their students.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Deng, Ruiqi, Maoli Jiang, Xinlu Yu, Yuyan Lu, and Shasha Liu. 2025. “Does ChatGPT Enhance Student Learning? A Systematic Review and Meta-Analysis of Experimental Studies.” ''Computers &amp; Education'' 227. https://doi.org/10.1016/j.compedu.2024.105224&lt;nowiki/&gt;.'''
&lt;/div&gt;

Deng and colleagues' meta-analysis of 69 experimental studies provides empirical grounding for claims about ChatGPT's pedagogical impact, revealing both opportunities and methodological challenges in assessing AI-enhanced learning. Their finding that ChatGPT interventions improve academic performance, affective-motivational states, and higher-order thinking propensities while reducing mental effort speaks directly to how assessment must shift when AI augments cognition—if mental effort decreases but learning outcomes improve, traditional measures of &quot;effort&quot; or &quot;struggle&quot; as proxies for learning may require recalibration. In their critique of current assessment methodologies the authors demonstrate that most studies evaluate only final outputs (essay quality, test scores) rather than learning processes, missing opportunities to examine how students interact with AI, what metacognitive strategies they develop, and whether AI use builds transferable skills or creates dependency. Deng et al.'s four methodological propositions—using complex project-based assessments that reveal process, evaluating long-term rather than novelty effects, prioritizing objective over self-reported measures of higher-order thinking, and employing adequate statistical power—provide a research agenda for pedagogy–AI scholarship that centres process evidence. Their documentation of disciplinary variation (language education dominates current research) while calling for cross-disciplinary synthesis focuses on avoiding discipline-specific approaches. The meta-analysis also reveals gaps in understanding collaboration (few studies examine peer learning dynamics when AI is present) and metacognition (limited research on whether students develop awareness of their own and AI's knowledge boundaries), highlighting the resulting pedagogical transformations.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Grigoli, L. Renato. 2023. “Ghosts in the Machine.” ''American Historical Association'' 61 (3). https://www.historians.org/wp-content/uploads/2024/07/Perspectives_61N3.pdf&lt;nowiki/&gt;.'''
&lt;/div&gt;

Grigoli dismisses fears of AI generated essays threatening academic integrity by arguing that “if the development of artificial intelligence results in the death of the humanities, then it will be because it will have shown that the emperor has no clothes.” He uses ChatGPT to demonstrate that although AI responses appear competent at a passing glance, they lack valuable substance, simply arranging facts in a way that “tricks the reader into… doing all the analytical work.” Clear critical analysis should be the core component of a successful humanities essay, making well-designed assessments of this field far more reliable than those focused on information retention (like engineering). Therefore, AI is not a real threat, but a valuable pedagogical tool which can demonstrate examples of clean prose and prompt students to critically analyze what constitutes critical analysis. Essentially, if an AI generated answer can pass a test, the real problem was &quot;self-inflicted&quot; by either the examiner or the question itself.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Lee, Daniel, and Edward Palmer. 2025. “Prompt Engineering in Higher Education: A Systematic Review to Help Inform Curricula.” ''International Journal of Educational Technology in Higher Education'' 22: 16. https://doi.org/10.1186/s41239-025-00503-7&lt;nowiki/&gt;.'''
&lt;/div&gt;

Lee and Palmer's systematic review establishes prompt engineering as an emergent pedagogical practice that integrates with longstanding traditions of scholarly inquiry, questioning, and rhetoric. The authors synthesize multiple frameworks (AIPROMT, CLEAR, CRISPE) that codify prompting as a learnable skill involving role specification, context provision, instruction clarity, and iterative refinement—revealing how interaction with LLMs mirrors Socratic dialogue, research question formulation, and the rhetorical tradition of audience awareness. This work positions &quot;prompting as pedagogy&quot; as a reconfiguration of existing scholarly literacies: students learning to prompt effectively must articulate their information needs precisely, anticipate how language shapes output, and iteratively refine queries based on initial results—all core practices in library research, database searching, and scholarly conversation. The authors document how educators are embedding prompt engineering across disciplines, from technical fields where students prompt AI to generate code or solve equations, to humanities contexts where prompting becomes a form of textual analysis (understanding what linguistic patterns trigger particular AI responses reveals implicit biases and training data influences). Their review also identifies ethical dimensions—well-designed prompts can mitigate AI hallucination and bias, while poorly constructed prompts amplify these issues—making prompt literacy a matter of scholarly responsibility. The authors' call for curricula that teach prompting as interdisciplinary competency aligns with how AI entangles with pedagogy across boundaries, reshaping what counts as fundamental scholarly practice in an AI-augmented knowledge environment.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Mai, Dang Thi Thuy, Cuong Van Da, and Nguyen Van Hanh. 2024. “The Use of ChatGPT in Teaching and Learning: A Systematic Review through SWOT Analysis Approach.” ''Frontiers in Education'' 9: 1328769. https://doi.org/10.3389/feduc.2024.1328769&lt;nowiki/&gt;.'''
&lt;/div&gt;

Mai and colleagues' systematic SWOT analysis of 51 studies on ChatGPT in education, organized through Biggs' 3P model (Presage-Process-Product), offers comprehensive mapping of how generative AI enters and transforms pedagogical systems at multiple scales—from individual learner characteristics (Presage) through interactive teaching-learning processes (Process) to learning outcomes and assessment products (Product). This multilevel framework reveals that ChatGPT's pedagogical impact cannot be isolated to single moments of use but ripples across entire learning ecologies: at the Presage level, ChatGPT shifts what prior knowledge students need (familiarity with prompting interfaces) and what instructor competencies are required (ability to design AI-aware assignments); at the Process level, it transforms interaction patterns from teacher–student and student–student to include human–AI dialogue that may enhance personalized scaffolding but risks reducing peer collaboration; at the Product level, it necessitates fundamental assessment redesign because traditional evaluation instruments (timed essays, closed-book exams) lose validity when AI can generate competent responses. The authors' characterization of ChatGPT as simultaneously &quot;friend&quot; (enabling personalized learning, reducing educator workload, providing instant feedback) and &quot;foe&quot; (enabling plagiarism, potentially reducing critical thinking, creating over-reliance) mirrors the section's emphasis on entanglement—pedagogy cannot simply embrace or reject AI but must negotiate tensions between efficiency and effort, personalization and depersonalization, augmentation and replacement. Mai et al.'s documentation of how educators are adapting curricula to emphasize creativity and critical thinking (skills less easily automated) while using ChatGPT for routine information provision demonstrates pedagogical evolution toward distinctly human capacities. Their call for assessment reform using complex case studies, portfolios, and process documentation rather than single-sitting exams directly supports the notion of process evidence and metacognition as being central to AI-era pedagogy, positioning assessment not as gatekeeping but as making learning processes transparent and accountable.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Oates, Angela, and Donna Johnson. 2025. “ChatGPT in the Classroom: Evaluating Its Role in Fostering Critical Evaluation Skills.” ''International Journal of Artificial Intelligence in Education'' 35 (4): 1793–1824. https://doi.org/10.1007/s40593-024-00452-8&lt;nowiki/&gt;.'''
&lt;/div&gt;

Oates and Johnson's empirical study of biomedical science master's students offers insight into how AI functions more effectively as object of critical study than as production tool, revealing pedagogical value in making AI outputs subjects for evaluation rather than endpoints of learning. Their finding that students' marks did not improve when submitting AI-generated essays but did improve when critically evaluating AI outputs demonstrates a fundamental pedagogical principle: learning occurs not in consuming AI-generated content but in interrogating it, comparing it against disciplinary standards, identifying its factual errors and rhetorical limitations, and articulating why human-authored scholarship differs. This shifts pedagogy from &quot;use AI to complete tasks&quot; toward &quot;use AI to understand knowledge construction itself&quot;—students learn about evidence evaluation, citation practices, and argumentation by analyzing where ChatGPT succeeds and fails at these scholarly fundamentals. The authors document that ChatGPT demonstrated structural coherence and grammatical accuracy but lacked the disciplinary depth and synthetic insight expected in graduate work, making visible to students the difference between surface-level fluency and genuine expertise. Their emphasis on user interaction as a variable affecting efficacy underscores that pedagogy must address not just whether AI is present but how students are taught to engage it—prompt design, output evaluation, and integration with human research become learnable scholarly practices. Oates and Johnson's conclusion that students preferred writing their own essays despite AI's availability suggests that when pedagogy centres process transparency and critical evaluation rather than output efficiency, students recognize and value the cognitive work that AI cannot replicate, focusing on pedagogy that treats AI as entangled phenomenon requiring simultaneous use and critique.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Pope, Andrew, and Rongqian Ma. 2024. “Exploring Historians’ Critical Use of Generative AI Technologies for History Education.” ''Proceedings of the Association for Information Science and Technology'' 61 (1): 1071–73. https://doi.org/10.1002/pra2.1188&lt;nowiki/&gt;.'''
&lt;/div&gt;

Pope and Ma conducted semi-structured interviews of seven history professors to assess their attitudes toward employing GenAI tools in their teaching. Understanding this stance is important because Pope and Ma believe incoherent and mismatched approaches could inhibit scholarly communication and undermine academic integrity. The survey demonstrated historians had major concerns about GenAI’s development, especially regarding plagiarism. Respondents were particularly divided on whether copying an AI’s work was academic misconduct. However, historians had far fewer concerns about using GenAI to &quot;augment&quot; human abilities or tailor support to students—although senior academics maintained substantially greater reservations. The historians that were interviewed concurred that critiquing AI generated text could improve a student’s media literacy. Pope and Ma’s study suggests that historians consistently doubt the quality of AI generated responses even when willing to employ it.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Tan, Myles Joshua Toledo, and Nicholle Mae Amor Ttan Maravilla. 2024. “Shaping Integrity: Why Generative Artificial Intelligence Does Not Have to Undermine Education.” ''Frontiers in Artificial Intelligence'' 7: 1471224. https://doi.org/10.3389/frai.2024.1471224&lt;nowiki/&gt;.'''
&lt;/div&gt;

Tan and Maravilla provide theoretical grounding for understanding how generative AI can be integrated into pedagogy without compromising academic integrity, arguing that responsible implementation depends on alignment with constructivist learning theory and self-determination theory. The authors position AI not as a threat to authentic learning but as a catalyst that necessitates pedagogical transformation—shifting from transmission models toward environments where students actively construct knowledge using AI as one tool among many. Their framework emphasizes process transparency through explicit discussion of AI's role in knowledge construction and ethical reflection through examining how GAI outputs are generated, what assumptions they embed, and where they may mislead or constrain inquiry. This work addresses pedagogy-as-entanglement by showing how GAI forces educators to make visible the epistemic practices that traditional assessment often left implicit: citation tracing, source evaluation, argument construction, and the iterative nature of scholarly writing. Tan and Maravilla argue that rather than banning AI to preserve integrity, educators should redesign assessment to require demonstration of process—portfolios showing prompt refinement, comparison of AI outputs with human-authored sources, and metacognitive reflection on when and why AI was consulted. Their synthesis of educational theory with practical implementation strategies makes this work useful for understanding how pedagogy must evolve to treat AI as both subject matter (what students must understand about how AI functions) and scaffolding (how AI can support learning when used transparently and reflectively).

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Yim, Iris Heung Yue, and Jiahong Su. 2025. “Artificial Intelligence (AI) Learning Tools in K-12 Education: A Scoping Review.” ''British Journal of Educational Technology'' 56 (1): 169–196. https://doi.org/10.1007/s40692-023-00304-9&lt;nowiki/&gt;.'''
&lt;/div&gt;

Yim and Su's scoping review of AI literacy education in K-12 contexts provides grounding for understanding how pedagogy approaches AI as an object of study, not merely as a tool, revealing how students across age groups learn to understand, critique, and create with AI systems. The authors document how intelligent agents (Google Teachable Machine, Learning ML) and software platforms (Scratch, Python) enable students to engage with AI's underlying mechanisms—training models, observing how data shapes outputs, and experiencing firsthand how algorithmic decision-making operates. This approach treats AI as epistemological phenomenon: students don't just use pretrained models but build simple systems themselves, making visible how AI &quot;learns&quot; and where its learning breaks down (limited training data, biased datasets, inability to generalize beyond training conditions). Yim and Su's synthesis of pedagogical strategies—project-based learning where students create AI applications, human-computer collaboration examining how humans and machines complement each other, and game-based approaches making AI concepts accessible—demonstrates how educators scaffold understanding from concrete manipulation to abstract reasoning about intelligence and automation. The review's attention to cognitive, affective, and behavioural learning outcomes moves beyond narrow skill acquisition to examine how AI literacy shapes students' broader epistemic stance: understanding AI's capabilities and limitations, recognizing when algorithmic solutions are appropriate, and developing critical awareness of AI's social implications. Their emphasis on age-appropriate pedagogies and the importance of unplugged activities (learning AI concepts through physical manipulation before digital implementation) provides models for how pedagogy must adapt to learners' developmental stages when teaching about AI systems. This work's K-12 focus complements higher education studies in this section by showing how foundational AI literacy built through hands-on exploration creates readiness for more sophisticated critical engagement with AI as both tool and object of study in advanced scholarship.

== Service and Peer Review ==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Checco, Alessandro, Lorenzo Bracciale, Pierpaolo Loreti, Stephen Pinfield, and Giuseppe Bianchi. 2021. “AI-Assisted Peer Review.” ''Humanities and Social Sciences Communications'' 8: 25. https://doi.org/10.1057/s41599-020-00703-8&lt;nowiki/&gt;.'''
&lt;/div&gt;

Checco et al.'s study represents crucial early (pre-GenAI) empirical work demonstrating that AI can predict peer review outcomes based on &quot;superficial&quot; manuscript features—readability metrics, formatting consistency, reference list structure, linguistic patterns—with surprising accuracy, training neural networks on 3,300 conference papers to correlate these proxy measures with eventual accept/reject decisions. This finding has profound implications for understanding AI's operational role: the research reveals that much of what passes as peer review judgment operates on detectable patterns (clear writing, proper citation formatting, adherence to disciplinary conventions) that AI can identify and assess, potentially automating routine quality checks and flagging submissions unlikely to meet standards. However, the authors explicitly position their work as supporting &quot;semi-automated&quot; rather than fully automated review, emphasizing AI's role in pre-screening and administrative tasks (matching manuscripts with reviewers based on topic modelling, identifying obvious deficiencies) rather than intellectual evaluation. The paper's most valuable contribution lies in its systematic exploration of ethical implications: algorithmic bias risks (AI might penalize unconventional but innovative work, discriminate against non-native English writers, favour institutional prestige markers), transparency requirements (making AI decision criteria auditable), and the necessity of human oversight to prevent automation from calcifying existing disciplinary hierarchies. By documenting both AI's predictive capabilities on operational dimensions and its inherent limitations on substantive judgment, Checco et al. provide empirical foundation for designing peer review systems where AI handles standardized identification tasks while human expertise remains authoritative for evaluative assessment, directly instantiating the core principle that operational assistance must not migrate into epistemic territory.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Hosseini, Mohammad, and Serge P. J. M. Horbach. 2023. “Fighting Reviewer Fatigue or Amplifying Bias? Considerations and Recommendations for Use of ChatGPT and Other Large Language Models in Scholarly Peer Review.” ''Research Integrity and Peer Review'' 8 (1): 15. https://doi.org/10.21203/rs.3.rs-2587766/v1&lt;nowiki/&gt;.'''
&lt;/div&gt;

Published early in the ChatGPT era, Hosseini and Horbach's analysis provides a prescient examination of how LLM integration transforms both the pragmatics and ethics of peer review labour. The authors document LLMs' potential to combat reviewer fatigue by automating time-consuming tasks—transforming informal reviewer notes into polished reports, generating structured feedback on manuscript sections, identifying linguistic or formatting issues—thereby potentially expanding the pool of contributors who can participate effectively despite language barriers or time constraints. However, the article's core contribution lies in its still-useful systematic identification of risks that emerge when operational assistance crosses into epistemic territory: LLMs trained on existing literature may amplify disciplinary biases (favouring established paradigms over novel approaches), geographic biases (privileging research contexts well-represented in training data), or methodological orthodoxies (flagging unconventional designs as errors rather than innovations). The authors demonstrate through examples how ChatGPT can generate cynical or biased reviews that violate Mertonian norms of universalism, and how confidentiality breaches can occur when reviewers input manuscript excerpts into external AI platforms without institutional safeguards. Hosseini and Horbach's recommendations—mandatory disclosure of LLM use in reviews, human accountability for all AI-generated content, training in bias recognition, and institutional policies prohibiting upload of confidential materials—have influenced subsequent journal guidelines and provide foundational ethical framework for understanding why guardrails against leakage and disclosure norms become operational necessities rather than optional best practices in AI-entangled peer review systems.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Shcherbiak, Anna, Hooman Habibnia, Robert Böhm, and Susann Fiedler. “Evaluating Science: A Comparison of Human and AI Reviewers.” ''Judgment and Decision Making'' 19 (2024): e21. https://doi.org/10.1017/jdm.2024.24&lt;nowiki/&gt;.'''
&lt;/div&gt;

In this study, a large-scale field experiment comparing GPT-4 with human reviewers on conference abstracts provides empirical evidence about AI's capabilities and limitations in evaluative judgment. It demonstrates that while AI can approximate human performance on certain classification tasks—identifying &quot;very best&quot; abstracts shows moderate alignment—detailed evaluative assessments reveal persistent gaps, with human-AI agreement comparable to human-human variability, suggesting AI does not systematically outperform baseline reviewer disagreement. Critically, the research shows humans substantially outperform AI at detecting AI-generated versus human-written content, with detection tools like GPTZero exhibiting higher accuracy than GPT-4 itself when evaluating authorship. This finding has direct implications for peer review integrity when AI-generated manuscripts enter the submission pipeline. The authors position AI as effective for prescreening—rapidly filtering submissions for basic quality thresholds, identifying obvious errors, flagging compliance issues—while demonstrating it lacks the contextual understanding necessary for nuanced scientific judgment about significance, impact, or methodological soundness. The paper's methodological rigour in isolating human-versus-AI performance dimensions provides context for understanding where operational assistance (screening) legitimately ends and where human evaluative authority (substantive assessment) must begin, directly addressing the guiding principle that human judgment remains central even in AI-augmented workflows.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Lim, Gim Hui, M. L. Tan, V. C. W. Hoe, and D. Koh. 2025. “Generative AI in Peer Review Process for Occupational Health.” ''Occupational Medicine'' 75 (5): 242–49. https://doi.org/10.1093/occmed/kqaf051.'''
&lt;/div&gt;

Lim and colleagues' empirical study comparing Microsoft Copilot, ChatGPT, and Google Gemini against human reviewers on eight occupational health manuscripts provides granular quantitative evidence about AI's operational capabilities and limitations in peer review tasks. The research demonstrates that AI tools significantly outperform humans in providing feedback (mean score 3.44 vs. human baseline, p&lt;0.001) across dimensions of relevance, completeness, accuracy, error identification, and constructiveness—documenting AI's strength in systematic checking tasks like identifying missing citations, flagging methodological inconsistencies, noting formatting errors, and pointing out unclear explanations. However, humans substantially outperform AI in generating actionable recommendations (mean score 3.36, p&lt;0.01), with AI showing particular deficiencies in suggesting substantive revisions, connecting findings to broader literature, or identifying conceptual limitations. This performance asymmetry instantiates the operational/epistemic division: AI excels at identification tasks (what's wrong, what's missing) but struggles with evaluative tasks (how to improve, what matters). The study also quantifies efficiency gains (AI reviews complete in 11 minutes versus 45 for humans) while documenting critical limitations: AI outputs contain fabricated references, generate plausible-sounding but inaccurate technical assertions, and require human verification to prevent propagation of errors. Lim et al.'s work demonstrates that even when AI shows superior performance on specific metrics, its integration into peer review requires careful task decomposition—leveraging speed and comprehensiveness for checking functions while preserving human authority for substantive guidance—making it essential evidence for designing hybrid human-AI workflows where operational assistance enhances rather than replaces evaluative expertise.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Sun, Zhuanlan. 2025. “Large Language Models in Peer Review: Challenges and Opportunities.” ''Scientometrics'' 130 (10): 5503–5546. https://doi.org/10.1007/s11192-025-05440-w&lt;nowiki/&gt;.'''
&lt;/div&gt;

Sun provides essential mapping of LLM applications across the peer review lifecycle, categorizing five distinct operational roles: checklist assistants for formatting and protocol adherence, reviewer selection aids that match manuscripts with appropriate expertise, feedback generators for preliminary assessments, bias detectors that flag methodological or statistical irregularities, and agents that coordinate multi-stage review workflows. The article systematically examines technical approaches including prompt engineering strategies, model evaluation frameworks, and architectural designs for integrating LLMs into editorial management systems. The author argues that while LLMs excel at standardized operational tasks—checking reference integrity, identifying duplicated content across submission databases, verifying compliance with reporting guidelines—they remain fundamentally limited in assessing research novelty, theoretical contributions, and domain-specific methodological rigour. The analysis emphasizes that current LLM limitations (inadequate scientific validation, domain knowledge gaps, inability to analyze complex datasets, ethical concerns around bias perpetuation) position them as supportive tools within human-led processes rather than autonomous decision-makers. This work is useful in understanding operational versus epistemic divisions of labour in AI-assisted scholarship service and documenting the technical infrastructure through which AI becomes entangled with peer review operations while maintaining clear boundaries around human evaluative judgment.

== AI and Scholarship Infrastructures ==

=== Organizational Infrastructures ===

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Batool, Amna, Didar Zowghi, and Muneera Bano. 2025. “AI Governance: A Systematic Literature Review.” ''AI and Ethics'' 5: 3265–3279. https://doi.org/10.1007/s43681-024-00653-w&lt;nowiki/&gt;.'''
&lt;/div&gt;

Batool and colleagues' (2025) systematic literature review offers a comprehensive mapping of AI governance across multiple levels—team, organization, industry, national, and international. The authors utilize a structured analytical framework that examines who governs (stakeholders and roles), what is governed (data, algorithms, systems), when governance occurs (stages in the AI lifecycle), and how it is implemented (frameworks, tools, policies). The article reveals that current governance practices remain fragmented and inconsistent, with significant gaps at the national and international levels. Applied to the context of higher education, this multi-level perspective is essential for understanding how research institutions must position themselves within broader governance ecosystems. Because organizational governance currently operates without clear external scaffolding, research institutions are often forced to improvise institutional arrangements rather than implement established templates. While the paper is broad in scope, its categorization of governance artifacts illuminates the range of mechanisms available to scholarly organizations: from technical tools like algorithmic auditing to organizational structures like ethics committees. Ultimately, the authors' findings highlight the challenges facing research institutions as they attempt to coordinate AI oversight across distributed, autonomous units—such as libraries implementing discovery tools or IT departments deploying infrastructure—demonstrating why cross-functional coordination is both necessary and difficult when existing governance structures were not designed to span these boundaries.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Hadley, Emma, Alan Blatecky, and Megan Comfort. 2025. “Investigating Algorithm Review Boards for Organizational Responsible Artificial Intelligence Governance.” ''AI and Ethics'' 5: 2485–2495. https://doi.org/10.1007/s43681-024-00574-8&lt;nowiki/&gt;.'''
&lt;/div&gt;

Hadley and colleagues provide empirical documentation of algorithm review boards (ARBs) as organizational governance mechanisms, interviewing technical contributors across sectors to examine ARB membership, scope, success factors, and limitations. Their findings reveal ARBs as cross-functional bodies integrating diverse expertise (technical specialists, ethicists, domain experts, legal advisors, non-specialist stakeholders) to review AI systems for potential risks and harms, operating alongside other responsible AI approaches like policies, audits, and dedicated governance roles. The study's key insight that institutional review boards alone prove insufficient for algorithm governance and that ARBs function most effectively when integrated with existing organizational processes rather than operating as isolated oversight bodies speaks directly to research institutions' governance challenges. The article's documentation of financial tensions between profit motives and responsible AI costs, while focused on commercial contexts, translates to research institutions facing pressure to adopt AI for efficiency gains while managing ethical risks with constrained resources. Hadley et al.'s call for standardized ARB effectiveness metrics points to the broader challenge of demonstrating governance value in organizations where responsible AI practices compete with other institutional priorities for attention and investment.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Janssen, Marijn. 2025. “Responsible Governance of Generative AI: Conceptualizing GenAI as Complex Adaptive Systems.” ''Policy and Society'' 44 (1): 38–51. https://doi.org/10.1093/polsoc/puae040&lt;nowiki/&gt;.'''
&lt;/div&gt;

Janssen's conceptual article reframes generative AI governance as managing complex adaptive systems characterized by co-evolution, emergent properties, and non-linear interactions between technical and social elements, directly challenging technology-deterministic approaches that treat AI as static tool requiring one-time organizational accommodation. This systems perspective is essential for understanding why research institutions struggle with AI governance: the article demonstrates how AI systems and organizational contexts mutually shape each other through feedback loops, making governance an ongoing adaptive process rather than implementation of fixed policies. Janssen argues that effective organizational stewardship requires holistic, outward-focused governance attending to how AI systems interact with broader organizational processes, public values, and societal concerns—moving beyond narrow risk mitigation to address joint accountability across system components including people, policies, data, and algorithms. For research institutions embedding AI in knowledge infrastructures, this framing illuminates why isolated departmental responses prove insufficient: cataloging systems using AI for metadata generation, research platforms deploying AI for literature synthesis, and administrative systems using AI for resource allocation together constitute an organizational AI ecosystem whose emergent behaviours cannot be governed through component-level oversight alone. The article's emphasis on selecting and combining appropriate policy instruments into adaptive governance packages provides conceptual foundation for cross-functional coordination mechanisms, suggesting that effective institutional stewardship requires deliberate orchestration of technical standards, organizational procedures, and stakeholder engagement processes that together shape AI's organizational trajectory. Janssen's work underscores that AI governance is not primarily technical implementation challenge but organizational transformation requiring institutions to develop new capabilities for managing sociotechnical co-evolution.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Papagiannidis, Emmanouil, Patrick Mikalef, and Kieran Conboy. 2025. “Responsible Artificial Intelligence Governance: A Review and Research Framework.” ''The Journal of Strategic Information Systems'' 34 (2): 101885. https://doi.org/10.1016/j.jsis.2024.101885&lt;nowiki/&gt;.'''
&lt;/div&gt;

Papagiannidis and colleagues provide theoretical grounding for understanding how organizations operationalize responsible AI principles through governance structures. Their scoping review synthesizes disparate literature to construct a conceptual framework differentiating between structural practices (formal roles, committees, reporting lines), relational practices (stakeholder engagement, accountability mechanisms), and procedural practices (auditing protocols, monitoring systems) across the AI lifecycle. This tripartite framework is valuable for research institutions navigating the challenge of translating broad ethical commitments into actionable organizational arrangements. The article explicitly addresses how governance antecedents like leadership commitment and regulatory pressure shape implementation, and how governance practices in turn affect outcomes like trust, compliance, and innovation capacity. The authors' critical reflection on responsible AI governance reveals tensions inherent to institutional stewardship: between centralized oversight and distributed expertise, between standardized protocols and context-sensitive judgment, between rapid AI deployment and deliberative ethical review. For research organizations managing AI's entanglement with knowledge infrastructures, this work provides vocabulary and analytical categories for diagnosing governance gaps and designing institutional responses that embed responsibility throughout organizational systems rather than treating ethics as external constraint.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Weber, Michael, Martin Engert, Norman Schaffer, Jörg Weking, and Helmut Krcmar. 2023. “Organizational Capabilities for AI Implementation—Coping with Inscrutability and Data Dependency in AI.” ''Information Systems Frontiers'' 25: 1549–1569. https://doi.org/10.1007/s10796-022-10297-y&lt;nowiki/&gt;.'''
&lt;/div&gt;

Weber and colleagues identify four organizational capabilities essential for AI implementation, addressing AI's distinctive characteristics that distinguish it from previous information technologies: inscrutability (difficulty predicting probabilistic outputs and explaining decision processes) and data dependency (reliance on high-quality, continuously updated data for system performance). Their capability framework—encompassing AI Project Planning, Co-Development, Data Management, and AI Model Lifecycle Management—provides actionable guidance for research institutions developing internal capacity to steward AI systems. The article's grounding in expert interviews from diverse organizational contexts reveals that AI implementation failures often stem not from technical deficits but from organizational incapacity to manage sociotechnical complexity: inscrutability requires enhanced planning and stakeholder communication practices to align expectations around uncertain outcomes, while data dependency demands robust governance of data quality, provenance, and evolution throughout systems' operational lives. For research organizations, these capabilities map onto critical institutional functions: libraries developing metadata systems must manage data quality for AI cataloguing tools; research offices supporting computational scholarship must plan projects acknowledging unpredictable AI behaviour; IT departments maintaining infrastructure must implement lifecycle management ensuring model performance doesn't degrade as institutional data changes. The article's emphasis on Co-Development capability—bringing together technical specialists, domain experts, and end-users to jointly shape AI systems—speaks directly to cross-functional coordination challenges in research institutions where AI touches multiple organizational domains. Weber et al.'s framework reveals that organizational stewardship requires not just governance structures (committees, policies, review processes) but operational capabilities (planning methods, collaboration practices, technical procedures) embedded in day-to-day institutional work. This capability perspective shifts attention from abstract principles to concrete organizational competencies that determine whether responsible AI rhetoric translates into institutional practice.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Wu, Chuhao, He Zhang, and John M. Carroll. 2024. “AI Governance in Higher Education: Case Studies of Guidance at Big Ten Universities.” Preprint, ''arXiv'', September 3. https://doi.org/10.48550/arXiv.2409.02017&lt;nowiki/&gt;.'''
&lt;/div&gt;

Wu and colleagues provide rare empirical documentation of how major research universities translate AI governance principles into institutional practice, examining guidance documents from fourteen Big Ten universities to identify organizational patterns and role-specific strategies. Their analysis reveals three key organizational dimensions: multi-unit governance involving information technology departments, teaching and learning centres, libraries, and research offices operating with distributed authority rather than centralized control; role-specific guidance differentiating expectations for faculty, students, staff, and researchers rather than applying uniform policies; and educational-advisory approaches emphasizing learning and adaptation over compliance enforcement. This case-study evidence illuminates the pragmatic challenges research institutions face when operationalizing AI oversight: how to coordinate across functional silos with different mandates, expertise, and risk tolerances; how to balance flexibility (needed because AI applications vary dramatically across contexts) with consistency (needed to ensure institutional values are upheld); how to position governance as enabling innovation rather than constraining it. The article's documentation of specific institutional mechanisms, such as data classification systems limiting what information can be shared with AI tools, or Socratic guidance approaches that pose questions rather than dictate answers, provides concrete examples of organizational stewardship in action. For understanding AI's organizational entanglement with knowledge infrastructures, this work demonstrates how governance emerges through negotiation among multiple institutional actors, each bringing domain expertise and jurisdictional claims, requiring coordination mechanisms that existing organizational charts may not accommodate.

=== Publishing, Communication, Engagement Infrastructures ===

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Bergstrom, Tracy, and Dylan Ruediger. 2024. “A Third Transformation? Generative AI and Scholarly Publishing.” ''Ithaka S+R''. October 30, 2024. https://doi.org/10.18665/sr.321519&lt;nowiki/&gt;.'''
&lt;/div&gt;

Drawing on interviews with leaders from publishers, technology disruptors, academic libraries, and scholarship, Bergstrom and Ruediger map the strategic landscape of AI adoption across the publishing industry. The report identifies a bifurcated future: an incrementalist scenario where AI produces efficiency gains without fundamentally altering industry dynamics, versus a transformative scenario creating disruption comparable to or exceeding previous digital transformations. For search and discovery, most interviewees anticipate heavy AI impact, with tools already expanding capabilities through summarization and chatbot interfaces—potentially disrupting the linear progression from discovery to understanding by introducing AI-enabled synthesis. For peer review, interviewees expressed optimism that AI could address chronic strain through &quot;pre-review&quot; feedback, assistance with copy editing and misconduct detection, and more efficient reviewer identification, while raising concerns about accuracy, confidentiality, and maintaining human judgment in evaluation. The authors document a competitive threat from large technology companies: scenarios where commercial LLMs become default interfaces for accessing scholarly content pose significant challenges to publisher positioning. Content licensing to foundation model developers offers clear monetization paths, but broader revenue implications remain uncertain. The analysis identifies a critical research integrity challenge: ensuring transparent standards for AI usage while upholding provenance, attribution, reproducibility, and transparency in an environment of increasing automation. Smaller publishing organizations may struggle to match larger entities' adaptive capacity, potentially accelerating industry consolidation. 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Broussard, Meredith. 2023. “The Challenges of AI Preservation.” ''The American Historical Review'' 128 (3): 1378–81. https://doi.org/10.1093/ahr/rhad366.'''
&lt;/div&gt;

Broussard illustrates how the current impermanence of digital storage is producing a nightmare for future historians, as content is hidden away by licensing agreements or simply disappears when its host platform ceases to exist. Earlier ideals of the internet preserving a “complete first draft of history” are far from the reality, and problems only intensify when considering the development of AI, which Broussard compares to the printing press. For example, one could access a record of a physical newspaper published on a given day, but Google Search’s software is constantly changing with no canonical daily version, which means no historian could ever hope to examine a comparable snapshot of an AI. Operations like the Internet Archive and the development of emulation can help diminish losses, but it must be recognized that the digital world is decaying.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Buitrago-Ciro, Jairo, Marta Samokishyn, Rachel Moylan, Jonathan Hernández Pérez, Oluwabunmi Bakare-Fatungase, and Carmel Firdawsi. 2025. “Bridging the AI Gap: Comparative Analysis of AI Integration, Education, and Outreach in Academic Libraries.” ''IFLA Journal'' 51 (3): 682–702. https://doi.org/10.1177/03400352251325274. '''
&lt;/div&gt;

Buitrago-Ciro et al. examine the websites of 40 libraries in North America, Western Europe, Latin America, and Africa to explore how they have integrated AI technologies into their services, policies, and outreach efforts. Overall, the authors found a geographic divide in the integration of AI into library services, because almost all North American and European libraries had AI educational outreach activities and resources, while only five (out of ten) Latin American libraries and one (out of ten) African libraries did outreach activities. However, AI integration into library services and development of library AI policies and guidelines was more uncommon across all regions, as less than half of North American and European libraries engaged in these activities, while only one library in Latin America and one in Africa integrated AI into their services and none had specific library AI policies. These regional differences in AI integration stem from each region’s socioeconomic contexts, social inequalities, and technological gaps that present additional challenges for AI adoption in African and Latin American libraries. 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Gulson, Kalervo N., and P. Taylor Webb. 2023. “Steering the Mind Share: Technology Companies, Policy and Artificial Intelligence Research in Universities.” ''Discourse: Studies in the Cultural Politics of Education'' 44 (2): 195–207. https://doi.org/10.1080/01596306.2021.1981828. '''
&lt;/div&gt;

Gulson and Webb (2023) examine how major technology companies are actively reshaping the landscape of artificial intelligence research within universities. Drawing on interviews with computer scientists as part of a broader international project, the authors investigate three key areas: the influence of tech companies on AI research practices, the policy frameworks that foster academia-industry collaborations, and the role of &quot;open science&quot; in facilitating the transfer of academic ideas to the corporate sector. The study highlights that the boundaries between academic and corporate research have become highly porous. Companies like Google do not merely act as external funders; they are deeply embedded within university ecosystems, actively steering research directions. Furthermore, the authors illustrate how national policies, such as Canada’s Pan-Canadian Artificial Intelligence Strategy, legitimize and accelerate this corporate influence by heavily incentivizing industry partnerships. While these collaborations provide universities with crucial resources and drive innovation, Gulson and Webb warn that they also raise significant concerns regarding conflicts of interest and the corporatization of open science. Ultimately, the authors argue that corporate funding creates powerful feedback loops among tech companies, policymakers, and academics, effectively allowing industry to capture the &quot;mind share&quot; of university research.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Kousha, Kayvan, and Mike Thelwall. 2024. “Artificial Intelligence to Support Publishing and Peer Review: A Summary and Review.” ''Learned Publishing'' 37 (1): 4–12. https://doi.org/10.1002/leap.1570&lt;nowiki/&gt;.'''
&lt;/div&gt;

Kousha and Thelwall provide a systematic mapping of AI tool deployment across the scholarly publishing pipeline, distinguishing demonstrated capabilities from promotional claims. For journal recommendation, the review documents AI-powered systems, including Springer Nature Journal Suggester, Wiley Journal Finder, IEEE Publication Recommender, and JANE (Journal/Author Name Estimator), that analyze text similarity with previously published articles and reports high accuracy rates for appropriate journal matching. The analysis of initial quality control covers a diverse toolkit for plagiarism detection, robot author detection, methods checking, automated statistical verification, transparency and reproducibility checking and manuscript structure validation. Commercial systems draw on databases to suggest appropriate reviewers; the Natural Science Foundation of China's AI-assisted reviewer recommender for grant applications reports approximately 80% accuracy. However, the review identifies a critical boundary: while AI proves effective for finding reviewers and conducting initial quality checks, its value in performing the actual substantive review process &quot;has not been clearly demonstrated.&quot; The synthesis reveals that substantial efficiency improvements are achievable in labour-intensive administrative tasks, while human judgment remains integral to core intellectual evaluations—a distinction essential for understanding where AI integration in publishing will proceed incrementally versus face fundamental obstacles.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Ma, Lai. 2024. “Generative AI for Academic Publishing? Some Thoughts About Epistemic Diversity and the Pursuit of Truth.” ''KULA: Knowledge Creation, Dissemination, and Preservation Studies'' 7 (1): 1–5. https://doi.org/10.18357/kula.287.'''
&lt;/div&gt;

Ma (2024) critiques the integration of generative AI in academic publishing, arguing that the drive for automation threatens the central values of epistemic diversity and bibliodiversity. By invoking the &quot;Sokal Hoax,&quot; the author illustrates the danger of AI-generated &quot;bullshit&quot;—content that mimics the formal structures of scholarship while remaining devoid of actual meaning. Ma specifically uses Scopus AI as a case study to demonstrate how the platformization of scholarly data creates a feedback loop that reinforces the &quot;Matthew Effect,&quot; where established, English-language, and well-resourced publications are disproportionately amplified. This process, Ma warns, leads to &quot;epistemic injustice&quot; by marginalizing non-Western research and niche topics that are underrepresented in training datasets. The paper serves as a vital warning: without robust data surveillance and human-centric safeguards, the AI-accelerated publishing model may exacerbate peer-review crises and citation monopolies, ultimately undermining the public trust and diverse knowledge creation that open scholarship aims to protect.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Mitchell, Peta, Michelle Riedlinger, Jake Goldenfein, Aaron Snoswell, Jean Burgess, and Kevin Witzenberger. 2025. “Research Genai: Situating Generative AI in the Scholarly Economy.” ''AoIR Selected Papers of Internet Research''. https://doi.org/10.5210/spir.v2024i0.14006.'''
&lt;/div&gt;

Mitchell et al. focus upon the oft-overlooked subfield of Generative AI tools known as “RGAI”, research-focused models which they argue represent “complex sociotechnical systems.” Hepp et al.’s definition of AI as a “sensitizing concept” and Watermeyer’s consideration of AI as a “labor accelerator” are used to situate this argument within the “scholarly economy” before the authors expand upon these theories, arguing RGAI should be approached as a form of “platform capitalism” akin to academia.edu. To evidence this stance, the authors examine the highly distinct RGAI models “Consensus” and “Writefull” as case studies. “Consensus” is designed to produce an academic “ConsensusMeter” by combining a proprietary LLM with OpenAI technology, while “Writefull” “aims to simplify… the often challenging task of scholarly writing” by employing custom AI models. Mitchell et al. highlight that although both tools are presented as independent and bespoke, they have major corporate backing. This deeply conflicts with the research principles of open scholarship, so Mitchell et al. aim to develop an index of RGAI which are appropriate for use in research.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Pividori, Milton, and Casey S. Greene. 2024. “A Publishing Infrastructure for Artificial Intelligence (AI)-Assisted Academic Authoring.” ''Journal of the American Medical Informatics Association'' 31 (9): 2103–13. https://doi.org/10.1093/jamia/ocae139&lt;nowiki/&gt;.'''
&lt;/div&gt;

The Manubot AI Editor implements a concrete technical solution to the provenance problem in AI-assisted scholarship through three integrated components: a Python library, a GitHub Actions workflow, and a prompt generator. This architecture addresses provenance directly: all changes are tracked through version control, creating a clear audit trail distinguishing human-authored from machine-generated text and documenting exactly how AI suggestions were accepted, modified, or rejected. Evaluation proceeded through five case studies using both human and automated assessment. Human evaluators assessed whether revisions preserved original meaning and important details, avoided introducing incorrect information, and maintained correct formatting. Automated &quot;LLM-as-a-Judge&quot; iterative assessment evaluated paragraph pairs across criteria including sentence structure clarity, ease of understanding, and grammatical correctness. The evaluations found that models could grasp complex academic concepts and enhance text quality, with particular effectiveness in text-based sections like introductions and discussions. The human-in-the-loop design, where AI suggestions function as proposed edits rather than direct insertions, mitigates risks of incorrect information while preserving authorial agency over final content.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Razack, Habeeb Ibrahim Abdul, Sam T. Mathew, Fathinul Fikri Ahmad Saad, and Saleh A. Alqahtani. 2021. “Artificial intelligence-assisted tools for redefining the communication landscape of the scholarly world.” ''Science Editing''. https://doi.org/10.6087/kcse.244. '''
&lt;/div&gt;

Razack et al. argue AI will transform publishing into a technology-driven industry, streamlining dissemination of scholarship “for the betterment of humankind.” Exploring current trends via case studies, they emphasize AI’s impact upon human performance over its independent “creative” role. They argue AI could benefit the “prospective” researcher by predicting an article’s “citation impact,” identifying evolving research trends, and locating relevant research journals to publish in, cutting past low-charging and “predatory OA journals” which “malign integrity” by publishing “compromised content.” Meanwhile, “retrospective” editors could employ AI to detect plagiarism, streamline peer review, and format publications. For Razack et al., the rise of AI can therefore be compared to the rise of the typewriter, swift adoption likely promoting &quot;human-machine collaboration&quot; over replacement.

=== Accountability-related Infrastructures ===

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Ngulube, Patrick, and Neema Florence Vincent Mosha. 2024. “Integrating Artificial Intelligence-Based Technologies ‘Safely’ in Academic Libraries: An Overview through a Scoping Review.” ''Technical Services Quarterly'' 42 (1): 46–67. https://doi.org/10.1080/07317131.2024.2432093&lt;nowiki/&gt;.'''
&lt;/div&gt;

Ngulube and Mosha (2025) conduct a scoping review examining the state of research on ethical issues and perceived risks in AI integration within academic libraries. Analyzing 28 studies published before 2024, the authors reveal that research on safe AI adoption in libraries remains nascent, with significant gaps in theoretical grounding and methodological diversity. The review identifies critical ethical concerns including algorithmic bias, privacy violations, reduced transparency and accountability, and job displacement—yet finds that existing literature disproportionately emphasizes employment risks while neglecting environmental and planetary impacts. The authors note that ethical considerations have not taken centre stage in library and information science research, as evidenced by the scarcity of relevant keywords and abstracts in the literature. A major finding is that most studies employ quantitative methodologies at the expense of qualitative and mixed-methods approaches, and only 18% employ explicit theoretical frameworks. The review underscores that academic libraries must navigate the dual challenge of leveraging AI's operational efficiencies while ensuring ethical standards of inclusivity, accessibility, and fair information use—a task complicated by the absence of established best practices and the need for human-centred approaches to AI governance.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''“Realising Potential, Supporting Users: IFLA Statement on Copyright and Artificial Intelligence.” n.d. IFLA. Accessed May 1, 2025. https://www.ifla.org/news/realising-potential-supporting-users-ifla-statement-on-copyright-and-artificial-intelligence/. '''
&lt;/div&gt;

This statement aims to help IFLA member libraries in navigating copyright issues and developing programs relevant to AI, positioning libraries as innovators “uniquely situated to lead” in supporting, training, and utilizing AI. However, restrictions stem from rightsholders, economic and moral copyright laws, and health, safety, and privacy laws. Libraries should therefore be guided by the most appropriate policy sources to mitigate restrictions by ensuring AI tools do not compromise areas of concern. Libraries are further recommended to advise decision-makers to permit mining legally accessed content, address bias by promoting “the widest possible access,” build capacity, awareness, and training for evolving technologies, and monitor AI standards. Governments are recommended to follow existing human rights regulations, avoid using copyright law as a “blunt force tool,” develop ethical AI practices, and fund repositories of AI training data—alongside AI companies themselves. Both rightsholders and vendors are advised to avoid language in contracts which restricts the use of AI or prevents exceptions. Overall, this document aims to promote AI by making as much content available as possible.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Werder, Karl, Balasubramaniam Ramesh, and Rongen (Sophia) Zhang. 2022. “Establishing Data Provenance for Responsible Artificial Intelligence Systems.” ''ACM Transactions on Management Information Systems'' 13 (4): 1–25. https://doi.org/10.1145/3503488&lt;nowiki/&gt;.'''
&lt;/div&gt;

Werder et al. provide a framework for understanding audit trails in the context of AI and research data management, arguing that robust data provenance is not merely a technical feature but a prerequisite for achieving accountability in AI systems. They detail the requirements for a comprehensive provenance system, capable of tracking data from its origin through various transformations and into model training and deployment. This is directly relevant to research infrastructures, as it outlines how repositories and data management platforms can and must evolve to support AI-driven research. The authors’ multi-layered architectural proposal offers a concrete vision for how a research institution could implement a system to audit data pipelines, identify sources of bias, and ensure regulatory compliance. By connecting provenance to the broader goal of “Responsible AI,” the paper provides the conceptual tools for evaluating whether a research infrastructure’s data governance is sufficient to handle the accountability challenges posed by AI.

== Audience ==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''de Angelis, Luigi, Francesco Baglivo, Guglielmo Arzilli, Gaetano Pierpaolo Privitera, Paolo Ferragina, Alberto Eugenio Tozzi, and Caterina Rizzo. “ChatGPT and the Rise of Large Language Models: The New AI-Driven Infodemic Threat in Public Health.” ''Frontiers in Public Health'' 11 (2023): 1166120. https://doi.org/10.3389/fpubh.2023.1166120&lt;nowiki/&gt;.'''
&lt;/div&gt;

De Angelis and colleagues examine the emergence of Large Language Models, particularly ChatGPT, as a novel public health threat through the lens of &quot;AI-driven infodemic.&quot; The authors trace the rapid evolution of LLMs from earlier transformer-based models through GPT-3 to ChatGPT, highlighting how each iteration has increased the capacity to generate fluent, authoritative-sounding text at scale. Critically, they identify a fundamental misalignment problem: despite efforts to fine-tune these models through reinforcement learning from human feedback, LLMs remain prone to generating plausible-sounding but factually incorrect or fabricated information—a vulnerability particularly dangerous in medical and health contexts. The paper's central argument is that the unprecedented speed and volume at which LLMs can produce convincing content creates conditions for misinformation spread on a scale previously impossible, especially among non-expert publics who lack the epistemic resources to detect AI-generated falsehoods. The authors emphasize that the inability to reliably detect AI-produced text compounds this threat, undermining public trust in scientific institutions and potentially influencing health-related behaviours and policy decisions. The work demonstrates how LLM-mediated scientific communication poses distinct risks to knowledge integrity and public understanding, requiring urgent development of detection mechanisms, governance frameworks, and media literacy initiatives to protect audiences from AI-driven epistemic harm.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Bryant, Rebecca. 2024. “Implementing an AI Reference Chatbot at the University of Calgary Library.” ''Hanging Together'', December 12. https://hangingtogether.org/implementing-an-ai-reference-chatbot-at-the-university-of-calgary-library/&lt;nowiki/&gt;.'''
&lt;/div&gt;

Bryant (2024) details the development and implementation of &quot;T-Rex,&quot; an AI-powered reference chatbot at the University of Calgary Library, based on a webinar hosted by the OCLC Research Library Partnership. While the library had offered live chat services since the early 2010s, the COVID-19 pandemic caused a massive surge in demand, peaking at over 3,000 inquiries in a single month. To alleviate this strain, the library analyzed past chat transcripts and determined that 12–14% of inquiries were simple, directional questions suitable for automation. To prevent scope creep during the initial training phase, the development team focused on a core set of fifty common questions. Through continuous refinement, the chatbot has since expanded to encompass over 1,000 custom responses, though its effectiveness remains limited by the availability of existing library webpages or FAQs to draw from. Bryant concludes by summarizing the Calgary team's key insights for institutions developing similar tools: developers must anticipate out-of-scope or non-library questions, recognize that users prefer direct answers over links to webpages, program creative responses for off-topic queries, and prepare for user resistance or non-adoption.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Hara, Noriko, Eugene Kim, Shohana Akter, and Kunihiro Miyazaki. 2025. “Exploring the Dynamics of Interaction About Generative Artificial Intelligence Between Experts and the Public on Social Media.” ''Journal of Science Communication'' 24 (1): A02. https://doi.org/10.22323/2.24010202&lt;nowiki/&gt;.'''
&lt;/div&gt;

Hara and colleagues conduct an empirical investigation into how experts and the public co-produce knowledge about generative AI on social media, specifically analyzing X (formerly Twitter) discussions. Rather than treating the public as passive consumers of expert knowledge, the authors adopt a Public Engagement with Science (PES) framework that recognizes social media platforms as dynamic arenas where non-experts actively contribute to shaping collective understanding of emerging technologies. Through computational and manual analysis, they identify distinct discussion topics, map the roles that both experts and laypeople play in knowledge production, and examine how engagement metrics correlate with these roles. A critical finding is that the public functions beyond questioners seeking expert guidance, but rather as active knowledge co-producers who share practical insights, challenge claims, and contribute their own perspectives and experiences with GenAI tools. This research demonstrates how AI itself—as a subject of discourse—becomes a site of negotiated meaning-making between differently positioned actors. The work moves beyond traditional one-way dissemination models to reveal the interactive, participatory nature of contemporary science communication, with implications for understanding how diverse audiences collectively construct understanding of transformative technologies and how this co-productive process shapes both public perception and the future development of AI systems.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Jaillant, Lise, Olivia Mitchell, Eric Ewoh-Opu, and Maribel Hidalgo Urbaneja. 2025. “How Can We Improve the Diversity of Archival Collections with AI? Opportunities, Risks, and Solutions.” ''AI &amp; Society'' 40: 4457–4459. https://doi.org/10.1007/s00146-025-02222-z. '''
&lt;/div&gt;

Jaillant et al. draw from interviews with 20 academics and archival professionals to explore how AI technologies can help address the lack of diversity in archival collections. The authors highlight that AI tools can assist in automatically detecting racist or inappropriate language in metadata, search large amounts of historical records, and uncover new insights within archival records. However, the authors argue that the deployment of AI should involve close collaboration between librarians, archivists, and developers. The current limited collaboration between developers and libraries limits the ethical and inclusive application of AI in archival collections, especially those with sensitive historical materials. The interviewees also warned against the loss of historical context when using AI, the perpetuation of archival biases, and the loss of control when AI tools are designed and governed by tech companies. To conclude, the authors recommend investing in interdisciplinary AI training programs for archivists, educating AI developers about the unique needs of archives so they can create more relevant solutions, and creating professional guidelines about the best practices for AI use to address the lack of diversity in archival collections.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Peters, Uwe, and Benjamin Chin-Yee. 2025. “Generalization Bias in Large Language Model Summarization of Scientific Research.” ''Royal Society Open Science'' 12 (4): 241776. https://doi.org/10.1098/rsos.241776&lt;nowiki/&gt;.'''
&lt;/div&gt;

Peters and Chin-Yee provide rigorous, large-scale empirical evidence of a systematic and consequential distortion in LLM-generated scientific summaries: the tendency toward overgeneralization. Testing ten prominent LLMs—including ChatGPT-4o, ChatGPT-4.5, DeepSeek, LLaMA 3.3 70B, and Claude 3.7 Sonnet—on 4,900 summaries of scientific abstracts and full-length articles, the authors demonstrate that even when explicitly prompted for accuracy, most LLMs consistently produce conclusions broader and more definitive than those warranted by the original research. Critically, they identify three specific mechanisms of overgeneralization: the use of generic statements that obscure quantification, the shift from past to present tense (which expands scope), and the omission of qualifiers and limitations. The findings are stark: LLM-generated summaries were nearly five times more likely than human-authored summaries to contain broad generalizations (odds ratio = 4.85, 95% CI [3.06, 7.70], p &lt; 0.001), with newer models performing worse than earlier ones. This research is foundational for understanding how AI-mediated knowledge communication systematically distorts scientific findings at scale, regardless of user expertise or intent. The work demonstrates a concrete mechanism through which LLM intermediation can alter the epistemic content of research, with particular implications for medical and clinical contexts where overgeneralized conclusions can directly influence policy and patient care. The authors propose mitigation strategies including temperature adjustment and systematic benchmarking, but their findings underscore the profound challenge of ensuring faithful knowledge transmission through AI systems.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''da Silva Cardoso, Heike, and Vitor Rocio. 2025. “Enhancing Digital Libraries Through NLP and Recommender Systems: Current Trends and Future Prospects with Large Language Models.” In ''Technology and Innovation in Learning, Teaching and Education: TECH-EDU 2024'', edited by Arsénio Reis, José P. Cravino, Leontios Hadjileontiadis, Paulo Martins, Sofia B. Dias, Sofia Hadjileontiadou, and Tassos Mikropoulos, 69–79. C''ommunications in Computer and Information Science'' 2480. Cham: Springer. https://doi.org/10.1007/978-3-032-02672-9_5&lt;nowiki/&gt;.'''
&lt;/div&gt;

da Silva Cardoso and Rocio propose a practical framework for integrating Natural Language Processing and Large Language Models into academic digital libraries to address the information overload facing researchers, students, and faculty. Recognizing that traditional search methods have become insufficient in the face of exponential publication growth, the authors advocate for AI-driven recommender systems capable of delivering precise, relevant, and personalized literature recommendations. Their contribution centres on an audience-aware design philosophy that positions librarians as essential partners in system development. Rather than treating AI as a purely algorithmic solution, the authors emphasize that librarians' direct interactions with users provide irreplaceable insight into the nuanced and context-dependent needs of diverse academic communities. This human-in-the-loop approach represents a noteworthy methodological stance: AI functions not as a replacement for human expertise but as a tool to augment librarian knowledge and enhance the responsiveness of knowledge discovery systems. The work is particularly salient for understanding how contemporary LLM-based systems can be designed to serve scholarly audiences more effectively while maintaining the institutional wisdom and user-centred perspective that librarians bring to information work.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Taneja, Ankit Kumar, and Chandra Tripathi. 2020. “AI-Powered Recommender Systems: Personalization and Bias.” ''Turkish Journal of Computer and Mathematics Education (TURCOMAT)'' 11 (1): 1090–1094. https://doi.org/10.61841/turcomat.v11i1.14406&lt;nowiki/&gt;.'''
&lt;/div&gt;

Though published before the generative AI era, Taneja and Tripathi's analysis of AI-powered recommender systems remains foundational to understanding algorithmic bias in information discovery. The authors examine the structural tensions inherent in personalization algorithms—systems designed to enhance user experience by tailoring content suggestions yet simultaneously capable of constructing &quot;filter bubbles&quot; and &quot;echo chambers&quot; around users. By continuously recommending content similar to previous engagement, these algorithms systematically exclude novel, dissenting, or interdisciplinary perspectives, undermining serendipitous discovery essential to genuine scholarly inquiry. Critically, the authors frame algorithmic bias not as a technical glitch but as a structural risk embedded within the information architectures that guide knowledge-seekers, and thus they expose how algorithmic personalization—a feature predating generative AI—already demonstrated the capacity to narrow intellectual diversity and reinforce pre-existing beliefs. This pre-GenAI work provides historical context for understanding how contemporary AI systems have intensified these risks, making it useful for evaluating the ethical imperatives of designing systems that promote intellectual openness rather than epistemic closure.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''de Winter, J. 2024. “Can ChatGPT Be Used to Predict Citation Counts, Readership, and Social Media Interaction? An Exploration Among 2222 Scientific Abstracts.” ''Scientometrics'' 129: 2469–2487. https://doi.org/10.1007/s11192-024-04939-y&lt;nowiki/&gt;.'''
&lt;/div&gt;

De Winter’s study contrasts conventional scientometrics, testing whether a large language model can predict an article’s citation count and altmetric scores (whilst noting these may be unreliable assessors of actual scientific impact) by rating its abstract across “semantically diverse” variables. His case study uses ChatGPT-4 to predictively evaluate 2,222 abstracts from articles published in ''PLOS ONE'', monitoring its accuracy by referencing actual citation counts and altmetrics scores. De Winter employs a custom script to prompt OpenAI’s Application Programming Interface (API) to score each abstract on a scale of zero to one hundred across thirty positive variables and their thirty antonyms, which he then organizes under five categories (e.g., “Quality and Reliability”). As Chat-GPT 4 only produced consistent results at the population level, it was run three additional times to determine averages and bolster reliability of individual scores. This language-based evaluation of article abstracts revealed that ChatGPT-4’s scores better correlate with altmetrics and citation counts than conventional readability scores do. Furthermore, “Novel and Engaging” articles were most likely to be cited, whilst “Accessible and Understandable” articles scored highest in altmetrics.

{{Navigation|previous=AI and Social|next=Complete Alphabetical List of References}}

{{BookCat}}</text>
      <sha1>9yc2pbohcezqqqahu9ohjzrpafue0ee</sha1>
    </revision>
    <revision>
      <id>4656126</id>
      <parentid>4656112</parentid>
      <timestamp>2026-08-02T21:53:55Z</timestamp>
      <contributor>
        <username>CorreiaA</username>
        <id>3614427</id>
      </contributor>
      <minor />
      <origin>4656126</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="112404" sha1="dr5k9rwwlzb9b9zxjj6p72sud0cylia" xml:space="preserve">== Research Methods and Practices ==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Arnett, Catherine, Eliot Jones, Ivan P. Yamshchikov, and Pierre-Carl Langlais. 2024. “Toxicity of the Commons: Curating Open-Source Pre-Training Data.” Preprint, ''arXiv'', October 29. https://doi.org/10.48550/arXiv.2410.22587.'''
&lt;/div&gt;

Open-source pretraining data is increasingly treated as a shared resource for building “open” language models, yet it can embed and reproduce harmful speech patterns at scale. Arnett, Jones, Yamshchikov, and Langlais argue that reducing toxic model behaviour requires intervening upstream in data, and they focus specifically on the distinctive constraints of public-domain corpora (including historical documents and OCR-derived text) where standard web-text toxicity filters can be impractical or ill-suited. They propose a fully open-source curation pipeline designed for these conditions and present three concrete contributions: (1) ToxicCommons, a custom-labelled dataset organized across five toxicity dimensions (racial/origin-based, gender/sex-based, religious, ability-based discrimination, and violence); (2) Celadon, a classifier trained on that dataset to detect toxic content more efficiently at scale in open data; and (3) a “balanced” filtration strategy that explicitly trades off safety filtering against retaining sufficient training material. The paper’s core claim is that open-data model development needs domain-attuned, auditable curation methods paired with task-specific classifiers, so that openness in data does not automatically translate into avoidable harms in downstream model outputs.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Bail, Christopher A. “Can Generative Artiﬁcial Intelligence Improve Social Science?” https://www.semanticscholar.org/paper/Can-Generative-Artiﬁcial-Intelligence-Improve-Bail/6206cc77bb3a3c0b6b9fce1ad68a8b1786a56941&lt;nowiki/&gt;.'''
&lt;/div&gt;

Bail (2023) provides a critical evaluation of how Generative Artificial Intelligence (AI), particularly Large Language Models (LLMs), might fundamentally transform computational social science. Moving beyond superficial administrative use cases, Bail examines the potential of LLMs to simulate complex human behaviours. He suggests that Generative AI could revolutionize agent-based modelling by replacing simplistic, rule-bound agents with dynamic, memory-equipped &quot;silicon samples&quot; capable of emergent group behaviours. While acknowledging the utility of AI for automated content analysis and expanding programming accessibility, Bail rigorously details the methodological and ethical perils of these largely opaque systems. He warns that the proprietary fine-tuning of commercial LLMs introduces severe demographic biases—often skewing toward highly educated, liberal perspectives—which threatens the external validity of AI-assisted research. Furthermore, Bail highlights the &quot;Stack Overflow Problem,&quot; cautioning that the unchecked proliferation of AI-generated &quot;junk science&quot; could contaminate future training data and degrade the broader scientific ecosystem. Ultimately, Bail argues that social scientists must not remain passive &quot;end-users&quot; of corporate AI. Instead, they must actively collaborate with computer scientists to reverse-engineer the &quot;social sense&quot; into AI models, ensuring the development of open-source, reproducible infrastructures that genuinely advance the study of human behaviour.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Bakharia, Aneesha, Antonette Shibani, Lisa-Angelique Lim, Trish McCluskey, and Simon Buckingham Shum. 2025. “From Transcripts to Themes: A Trustworthy Workflow for Qualitative Analysis Using Large Language Models.” In ''Joint Proceedings of LAK 2025 Workshops, co-located with the 15th International Conference on Learning Analytics and Knowledge (LAK 2025)''. Dublin, Ireland: CEUR-WS.org. https://ceur-ws.org/Vol-3995/LLMQUAL_paper1.pdf.'''
&lt;/div&gt;

Bakharia et al. explore the use of AI in qualitative, rather than quantitative, research in education. The authors define “minimum requirements that an LLM-supported qualitative analysis workflow must satisfy” and present a “LLM-based workflow that derives an initial set of themes” from text data that is “transferable to other LA [learning analytics] contexts performing qualitative analysis of open-ended text.” The authors define two requirements for “LLM-generated inductive coding”: first, it must verify “coded textual extracts… against source data” to make sure the quotes are accurate (i.e., verbatim and not hallucinated) and verify those extracts “are meaningfully classified under the assigned code.” Second, in the interest of transparency, it must “explain that rationale for each code” and “trace every code, whatever level of abstraction, back to its source data.” The article outlines and describes the proposed workflow in detail, including its being built in Python with a Jupyter notebook and Flask application. While they acknowledge challenges and problems in their research (e.g., LLM bias, the lack of comparable human analysis, the risk of alienating the human quality of qualitative research), Bakharia et al. ultimately advocate their approach as one that “improves transparency, verifiability, and interpretability, while addressing limitations of previous methods and enhancing researcher processes in qualitative thematic analysis&quot; (9). By adapting their minimum requirements and workflow, the authors argue, researchers can engage more effectively in LLM-driven qualitative research.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Dennstädt, Fabio, Cedric Sivert Möller, Tim Fellerhoff, Felix Busch, Oke Gerke, André Karch, and Oliver Krause. 2024. “Title and Abstract Screening for Literature Reviews Using Large Language Models: An Exploratory Study in the Biomedical Domain.” ''Systematic Reviews'' 13 (1): 158. https://doi.org/10.1186/s13643-024-02575-4&lt;nowiki/&gt;.'''
&lt;/div&gt;

Dennstädt et al. perform a study in which they attempt to determine the viability of using LLMs to automate scholarly literature surveys. The researchers developed a method for using LLMs to perform the title and abstract screenings of a systematic literature review method and applied that method with four LLMs across eleven datasets in biomedical literature. A key advantage of implementing LLMs in this process is that it escapes the need to train the machine via pre-selection. Researchers have developed automated and semi-automated processes for systematic literature reviews in the past, but this requires a human agent to provide training data or a corpus of example texts that tell the system what to look for. LLMs do not require this step. Instead, the researchers used a Python script that prompts the LLM “to evaluate the relevance of a scientific publication for inclusion into an SLR,” providing the LLM with both abstract and title, request for a numbered score indicating the relevance of the publication, and a numerical threshold that defines whether a score makes the given publication relevant. The authors characterize the results of the study as “promising” but also “far from perfect,” identifying that such applications could be helpful to researchers and are widely applicable without special training for data or user, even if “fully automated systems… still fail to differentiate… near the level of human evaluation.” The authors conclude that more research into the use of LLMs to automate systematic literature reviews is needed, but it seems very likely that scholars will employ LLMs into this integral research task with greater frequency in the future. How well LLMs will continue to perform in this task is unclear, especially in new research, and Dennstädt et al. clearly state, “we cannot answer the question of to what extent LLMs should be used for conducting literature reviews and for doing research.”

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Montague-Hellen, Beth. 2024. “Empowering Knowledge through AI: Open Scholarship Proactively Supporting Well Trained Generative AI.” ''Insights'' 37 (1). https://doi.org/10.1629/uksg.649.'''
&lt;/div&gt;

Generative AI is becoming a dominant interface for finding, summarizing, and producing academic information, with consequences for what counts as authoritative knowledge online. Montague-Hellen argues that, rather than focusing primarily on misuse, job displacement, or defensive copyright disputes, scholarly communications actors should actively encourage the inclusion of scholarly literature in generative AI training data to improve reliability and ensure research is represented in emerging discovery platforms. The article develops two main pathways for doing this: making scholarly outputs more machine-actionable and “crawlable” (especially through better linkage, metadata, and structured HTML rather than PDF-only dissemination) and making permissions unambiguous by explicitly addressing AI training in licences and related signals. It foregrounds “garbage in, garbage out” to claim that while libraries and publishers cannot remove low-quality web content from training corpora, they can tilt the balance by lowering friction for high-quality, curated research to be ingested legally. Montague-Hellen also highlights unresolved tensions around attribution and consent under common Creative Commons licences, suggesting that clearer, more specific permission frameworks (or new licensing patterns) may be needed to distinguish human reading from machine training and to communicate “enthusiastic consent” where desired.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Mugaanyi, Joseph, Christoph Lehner, and Lia M. Bally. 2024. “Evaluation of Large Language Model Performance and Reliability for Citation Generation Across Scientific Disciplines.” ''Journal of Medical Internet Research'' 26: e52935. https://doi.org/10.2196/52935&lt;nowiki/&gt;.'''
&lt;/div&gt;

Mugaanyi, Lehner, and Bally perform a study aimed at gauging the accuracy and reliability of citations generated by ChatGPT (GPT 3.5) in both the natural sciences and humanities. The authors emphasize that “Citations and references serve as the backbone of scholarly communication, providing the necessary context, evidence, and credit to prior works… ensuring the integrity of the research process.” With this in mind, the article frames the related study as aiding researchers in determining whether LLMs are viable as writing assistants in scholarly writing. In short, if an LLM cannot be relied upon to accurately cite and reference sources, it poses a risk to the integrity of research when incorporated into scholarly writing. The study found that ChatGPT hallucinated over a quarter of its references, with a slightly higher margin in the natural sciences. Furthermore, not all of those citations that did exist were accurate, and the LLM hallucinated DOIs for nearly 90% of the references it cited, real or otherwise, in the humanities. The issue, as the authors describe it, is that “in the current iteration of LLMs, since the training is geared toward generalization and the models are probabilistic, they tend to interpolate and fill in the missing information with synthetic text.” The authors conclude that, while domain-specific models may improve performance and reliability, in its current, generic form, researchers need to contemplate whether the strengths of ChatGPT’s reference generation justify its demonstrable limitations and “the importance of robust validation processes to ensure the accuracy and reliability of generated content.” 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Schroeder, Hope, Marianne Aubin Le Quéré, Casey Randazzo, David Mimno, and Sarita Schoenebeck. 2024. “Large Language Models in Qualitative Research: Uses, Tensions, and Intentions.” Preprint, ''arXiv'', October 9. https://arxiv.org/abs/2410.07362&lt;nowiki/&gt;.'''
&lt;/div&gt;

Schroder et al. perform interviews with twenty qualitative researchers in human computer interaction (HCI) and qualitative research to gauge how researchers are actually using LLMs and concerns over the incorporation of LLMs at different stages of research; the authors also provide a survey of the rise of LLMs and flag potential concerns, using both interviews and survey as a launchpad to outline suggestions and recommendations for researchers in the field contemplating the use of LLMs in their research. The authors are concerned that “the speed of LLM development has outpaced guidance on their ethical use” and “the HCI community is contending with the need for developed policies that tackle how to use AI ethically in research.” The most prominent concerns that the article raises relate to “ethics, unequal adoption of new technologies, model bias, and performance” as well as “concerns regarding participant privacy,” but there is also a larger issue within the field of HCI that “LLMs may lend the impression that qualitative inquiry can be automated, and their integration into Quantitative Data Analysis (QDA) software may increasingly impose positivist approaches that conflict with interpretivist traditions.” Key findings from the interviews are that most researchers are open to responsible use of LLMs but have concerns about established guidelines and norms for its implementation. Additionally, many are already using LLMs “to generate recruitment materials,” “speed up qualitative coding,” and “for ideation and feedback,” even as they acknowledge tensions between the qualitative nature of their work and the prospect of automation. The most significant recommendations that Schroder et al. make include updating consent forms, using dedicated tools rather than defaulting to Chat-GPT, and implementing design decisions specifically for LLM-incorporating methodologies that reconsider “participant privacy,” LLM’s “intentional use,” “transparency and validation,” “researcher context,” “deep engagement with data” despite this automation, and ways “to consider participant perspectives and interests” given “the variable performance LLMs have across contexts, knowledge domains, cultures, and languages.” The authors hope that incorporating these considerations will “empower qualitative researchers to leverage LLMs confidently, and even creatively, for their work.” 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Tumadóttir, Anna. 2024. “Questions for Consideration on AI &amp; the Commons.” ''Creative Commons'', July 24. https://creativecommons.org/2024/07/24/preferencesignals/.'''
&lt;/div&gt;

Tumadóttir talks about CC, license, tools, and policy and discusses the way to foster a healthy commons environment in the digital era. She points out how the introduction of the CC license enhanced Creative Commons by giving the creators choice over usage of their works. However, it is now a question if the same healthy commons can be maintained today because of rapid technological development. Preference signals for AI is a notion to give an agent (creator, rights holder, entity of some kind) more flexibility on how they want their work to be used for AI model training. However, the choice is still binary which is offering all or nothing. After consultations, it is found that people want more control over their work and if not, they might not share their work at all. Therefore, it is important to identify the right type of preference signals for it to be useful to benefit the public interest. During this process, we need to keep in mind its effect and variation on cultural heritage, different education sectors, and regions. Moreover, to make the preference signals effective, we need to examine its structure as well as whether legal enforcement is necessary.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Yue, Yongjie, Maosong Zheng, Jiahui Liu, Zhimin Wang, and Chenhui Mao. 2025. “A Practical Guide and Assessment on Using ChatGPT to Conduct Grounded Theory Studies: Step-by-Step Reporting of the Data Analysis Process.” ''Journal of Medical Internet Research'' 27: e70122. https://doi.org/10.2196/70122&lt;nowiki/&gt;.'''
&lt;/div&gt;

Yue et al. employ a study that entailed researchers using either manual coding or coding assisted by ChatGPT to perform data analysis on a 40,000 word dataset made up of interviews with 8 players of Listen and Play in Jianghu, a Chinese MMORPG designed for the blind. The study’s aim was to “provide detailed guidelines for using ChatGPT in grounded theory within the Chinese context,” “evaluate the effectiveness of ChatGPT coding” in this context, and “explore the broader implications and future directions of ChatGPT in qualitative research.” The article goes into great detail as to the process for generating open code with ChatGPT. The results of the study show that, although manual coding performed slightly better than ChatGPT-assisted coding, the “difference was not statistically significant” in its production of nodes and reference points. However, during axial coding, the categories and subcategories generated through these respective processes was significantly different, with only half of the categories semantically matching between manual and ChatGPT-assisted methods. The authors conclude that, while ChatGPT 4-Turbo “enhanced the diversity and efficiency of coding... it struggled with depth, context, subtle nuances, connections, and coding organization.” Nevertheless Yue et al. see great potential in the application of GenAI-assisted coding in grounded theory, especially as the technology develops. 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Zhu, Wenhao, Hongyi Liu, Qingxiu Dong, Jingjing Xu, Shujian Huang, Lingpeng Kong, Jiajun Chen, and Lei Li. 2023. “Multilingual Machine Translation with Large Language Models: Empirical Results and Analysis.” Preprint, ''arXiv'', April 10. https://arxiv.org/abs/2304.04675&lt;nowiki/&gt;.'''
&lt;/div&gt;

Zhu et al. perform an empirical study that tests the multilingual translation performance of eight popular LLMs on 102 languages. As the authors explain, this is a particularly difficult task as it requires “semantic alignment between languages.” While LLMs tend to perform surprisingly well at translation, “it is also unclear [sic] how LLM acquires translation ability and which factors affect LLM’s translation ability.” This study in multilingual machine translation (MMT) therefore seeks to answer two questions: how do LLMs perform MMT over massive languages and what factors affect their performance?

The results of the study suggest that GPT-4 generally outperforms its competitors but still falls short of Google Translate in some tests. Two key takeaways from this study are that “exemplars in the tail of the prompt have larger influence on an LLM’s behaviour,” meaning that the order in which exemplars are given within a prompt matter, and that cross-lingual translation pairs are particularly helpful exemplars to LLMs. The authors ultimately conclude that an “LLM can acquire translation ability in a resource-efficient way, which indicates [a] promising future of LLM in multilingual machine translation” as the technology evolves.

''NB: As this research was conducted prior to Google’s implementation of GenAI/LLMs into Google Translate in 2024, it sometimes uses Google Translate as a baseline/comparison point for LLM-powered translation that can be confusing without that context.''

== Forms of Research Output ==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Bozkurt, Aras. 2024. “GenAI et al.: Cocreation, Authorship, Ownership, Academic Ethics and Integrity in a Time of Generative AI.” ''Open Praxis'' 16 (1): 1–10. https://doi.org/10.55982/openpraxis.16.1.654&lt;nowiki/&gt;.'''
&lt;/div&gt;

Bozkurt’s essay seeks “to undertake a critical examination of the use of generative AI in academic contexts… examining its implications and exploring the nuances of its integration.” He begins with an assertion of technological determinism, stating “This technological shift… is not just a transient trend but a symbol of the inescapable change… marking the onset of an AI-dominated age and initiating profound and inevitable shifts in our academic and educational paradigms.” The author makes the argument that the advent of AI “requires us to critically reconsider concepts such as cocreation, ownership, and authorship in academic writing processes.” For instance, in exploring the concept of ownership, he briefly notes the ethical concerns of whether those who created the content upon which AI was trained might claim ownership of AI-generated content and explores the notions of AI or even its programmers acting as a co-author. Bozkurt himself takes the explicit stance that GenAI ought not be credited as a co-author. The paper also provides suggestions related to the ethics of AI use and transparency: “In some cases, merely reporting… is inadequate. A more nuanced approach involves providing multilayered statements acknowledging and benchmarking the use of [GenAI], specifying where, when, in which sections, and for what purposes it is employed.” Bozkurt reiterates that responsibility ultimately belongs to the human author, and provides the aiTARAS (Academic Integrity and Transparency in AI-assisted Research and Specification) Framework for this purpose. Bozkurt ends his essay by identifying further problems beyond the scope of the article, including “reimagining of assessment and evaluation,” our overfocus on ChatGPT and English language in this field of study, and the inaccuracy of AI detection software.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Colbert-Lewis, Danielle, Lawrence Maminta, Kelly McElroy, Graeme Slaght, and Mark Swartz. 2024. “The Citation Economy as a Site of Extraction for Surveillance Publishing.” ''Canadian Journal of Academic Librarianship'' 10 (December): 1–22. https://doi.org/10.33137/cjal-rcbu.v10.43293.'''
&lt;/div&gt;

Colbert-Lewis et al. (2024) examine the extractive nature of the modern &quot;citation economy,&quot; arguing that academic publishing has evolved into a powerful mechanism for surveillance and data commodification. The authors detail how a consolidated group of dominant publishers capture surplus value from the academic lifecycle by extracting free scholarly labour, research data, and personal information. Crucially, these corporations are transitioning from traditional information vendors into technology-driven data brokers. The extracted data is reinvested into proprietary analytics products that are then sold back to universities to evaluate and surveil faculty performance, relying on opaque metrics that threaten academic freedom. Furthermore, the authors highlight the severe ethical compromises inherent in this system, noting that academics inadvertently fuel data infrastructures that these same parent companies sell to external industries, including law enforcement and advertising. To combat the rise of &quot;surveillance publishing,&quot; the article concludes with actionable recommendations for scholars and librarians to resist exploitative practices and build ethical infrastructures, alongside a supplementary mini-zine designed to raise awareness about the hidden costs of participating in the citation economy.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Frangou, Sophia, Umberto Volpe, and Andrea Fiorillo. 2025. “AI in scientific writing and publishing: A call for critical engagement.” ''European Psychiatry'' 68 (1): e98. https://doi.org/10.1192/j.eurpsy.2025.10061&lt;nowiki/&gt;.'''
&lt;/div&gt;

Frangou, Volpe, and Fiorillo provide a succinct summary of the benefits of implementing AI in scientific writing and publishing, before turning to the challenges and risks posed toward the use of such technology. Finally, they end by posing ethical frameworks for the use of AI in both publishing and writing. In publishing, the authors identify tools that can aid in tasks ranging from copyediting to finding reviewers and claim that for both “high-volume publications” and “resource-constrained journals… AI can serve as a force multiplier, expanding what editorial teams can accomplish without compromising the centrality of human discretion and responsibility.” In writing, the article notes that “AI-powered applications offer a suite of tools that, when used judiciously, can enhance the quality, efficiency, and inclusivity of the scholarly communication process,” placing such tools along the trajectory of preexisting aids like EndNote and Zotero, which have also now incorporated AI. Frangou, Volpe, and Fiorillo argue that AI can help scholars identify relevant literature they might otherwise have trouble finding, reduce the linguistic bias encountered by scholars for whom English is not their first language, and aid scholars in navigating the publishing landscape so their work can find the best possible fit. Finally, the authors acknowledge the epistemic and ethical risks of AI: inconsistency and irreproducibility, transparency, informed consent, and data privacy are all core concerns. Key components in the article’s ethical frameworks for publishers and authors include transparency and disclosure, human accountability, and training and skill development. The authors hope that “these principles articulate a shared responsibility for shaping the role of AI in scientific publishing” and AI’s “adoption reinforces the foundational values that give scientific communication its trustworthiness and legitimacy.”

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Graßhoff, Gerd. 2024. “AI-Reporter: A Path to a New Genre of Scientific Communication.” Preprint, ''arXiv'', July 8. https://arxiv.org/abs/2507.05903. '''
&lt;/div&gt;

Graßhoff introduces a new tool, the AI-Reporter, that aims “to fundamentally expand scientific communication for the new era…”; according to Graßhoff, the AI-Reporter “creates a sustainable, referenceable, and expandable knowledge base that captures not just content but the living essence of scientific discourse.” In short, Graßhoff proposes a tool that will adapt a scientific presentation into a “public-ready chapter” in about three minutes with “only the author’s consent.” The majority of the article is dedicated to a tech-oriented breakdown of the methodology and workflow of the AI-Reporter, namely the semantic analysis and translation of a recorded slide presentation—consisting of the presentation as a PDF, video recording, and basic metadata—into a publication-ready chapter. Graßhoff’s tool is an attempt to solve what he identifies as a core problem of modern scholarly communication, namely that “knowledge is increasingly presented in dynamic, multimodal formats” that are ultimately ephemeral and content is often lost (14). He aims to refine this tool to enable real-time processing, multilingual support, interactive multimedia components, “optimization for academic disciplines,” and more to this project. He advocates the AI-Reporter as nothing less than “a vision for the future of scientific communication.”

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Jiang, Jialei. 2024. “When generative artificial intelligence meets multimodal composition: Rethinking the composition process through an AI-assisted design project.” ''Computers and Composition'' 74: 102883. DOI: https://doi.org/10.1016/j.compcom.2024.102883&lt;nowiki/&gt;.'''
&lt;/div&gt;

Jiang conducts a study in which GenAI is integrated into students’ composition of multimodal texts, then interviewed on their experience. Jiang’s states her aim as follows: “Through examining writing students use of GenAI tools in multimodal composition, this study seeks to unravel how GenAi technologies influence students’ design choices, problem-solving approaches, and the overall composition process.” In particular, Jiang is interested in “potential opportunities and challenges of incorporating GenAI into students’ multimodal composition process.” Jiang frames the article within composition and writing studies and the theory behind multimodal composition. She builds upon recent pedagogical best practices put forward by Burriss and Leander (2024) that “call upon teachers and educators to engage in the development of an emergent pedagogy of critical AI that “teach[es] about/with AI in emergent, flexible, and speculative ways.” The results of the study emphasize that, while GenAI can streamline workflow and provide examples from which students can build using their own creativity, there were clear limitations to the technology. Of course, students’ realization of these limitations is a success of the course’s pedagogy. The article also provides three case studies of the student compositions as exemplars of the outcome. Jiang concludes with a recommendation “that researchers and educators engage in meaningful dialogues with students about their uses of GenAI during composition practices.” She quotes her own earlier work (Jiang et al. 2024), where she writes that to keep AI out of the classroom “is not only idealistic and impossible... it is actually completely disengaged from the realities of the changing technological landscape students are already facing.”

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Mehlenbacher, Brad, Ana Patricia Balbon, and Ashley Rose Mehlenbacher. 2024. “Synthetic Genres: Expert Genres, Non-Specialist Audiences, and Misinformation in the Artificial Intelligence Age.” ''Journal of Technical Writing and Communication'', January 31. https://doi.org/10.1177/00472816231226249.'''
&lt;/div&gt;

Genre theorists Mehlenbacher et al. examine which AI-generated texts are “good enough” to pass as “bona fide” (already a “very good” standard). They argue AI-generated text produces misinformation, pushes apart definitions of “information” and “knowledge,” and necessitates rhetorical understanding. The authors therefore believe “synthetic genres” will emerge, departing in situation, form, and even “the very concept of genre users” based on recursive and “poisoned” outputs. In reviewing literature, the authors spotlight AI-generated disinformation’s suasive (instead of propagandistic or accurate) potential, and argue that AI-generated text can be suasive by appearing both “timely” and “appropriate.” However, this “fraudoscientific” text can never be truly “timely” or “appropriate,” as it is always constrained in past work, and only responds to prompts, not situations. Despite this, AI-generated text generated on specialist subjects can still be effectively suasive—and even when identified as AI—because its authority is difficult to challenge. Mehlenbacher et al. therefore conduct two studies of AI-generated outputs, focusing on how they may be deceptive or detected. They first prompted GPT-3 to emulate rhetorical research abstracts by generating a range of definitions alongside text to emulate research processes. Next, they conducted a genre analysis, generating text on controversial topics and prioritizing suasiveness over ability to pass a theoretical “Genre Turing Test.” Based on their results, Mehlenbacher et al. suggest AI-generated text should be cross examined with specialist texts to identify where they need additional development, presenting a valuable teaching opportunity which supports “a powerful way to introduce the epistemic functions of writing.” Non-specialists should also develop tools to identify the source and quality of content, including diverse genre perspectives. The authors conclude by arguing genre scholars should further consider AI-generated texts and emphasizing the importance of genre users. This is because “genre must be understood in a rhetorical context,” while “synthetic genres” can only act as “statistical simulacrum.”

== Teaching and Pedagogy ==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Adewumi, Tosin, Lama Alkhaled, Christopher Buck, Sergio Hernandez, Sofia Brilioth, Memoona Kekung, Yasmin Ragimov, and Emily Barney. 2023. “ProCoT: Stimulating Critical Thinking and Writing of Students through Engagement with Large Language Models (LLMs).” Preprint, ''arXiv'', December 15. https://doi.org/10.48550/arXiv.2312.09801&lt;nowiki/&gt;.'''
&lt;/div&gt;

Adewumi et al.'s Probing Chain-of-Thought (ProCoT) methodology represents a pedagogical approach that transforms LLM interaction from potential academic dishonesty into an active learning process centred on critical evaluation and evidence-based reasoning. ProCoT requires students to generate initial outputs using LLMs, then systematically affirm or refute each claim using peer-reviewed references, effectively making the AI output a provisional hypothesis to be tested rather than a final answer to be submitted. This approach directly addresses the section's themes of process transparency (the method makes visible each stage of knowledge construction, from initial AI generation through source verification to synthesis) and ethical reflection (students must grapple with AI limitations including hallucination, bias, and lack of disciplinary nuance). The authors' finding that student outputs using ProCoT were significantly more concise than LLM-generated text (208 vs. 391 words on average) while demonstrating enhanced critical thinking suggests that the method trains students to distill and synthesize rather than accept verbose AI output uncritically. ProCoT leverages AI's epistemological weaknesses as pedagogical strengths—the fact that ChatGPT cannot reliably cite sources becomes an opportunity for students to develop information literacy by finding and evaluating primary literature. The method's anti-cheating design is secondary to its pedagogical value: by requiring iterative engagement with AI outputs and scholarly sources, ProCoT embeds the kind of metacognitive reflection (What did the AI get right? What did it miss? How do I know?) that is of significance to pedagogy in the AI era. The authors' evidence from 65 students across disciplines demonstrates feasibility across contexts, emphasizing cross-disciplinary rather than field-specific approaches to AI-entangled pedagogy. 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Berry, David M. 2023. “AI, Ethics, and Digital Humanities.” In ''The Bloomsbury Handbook to the Digital Humanities'', edited by James O’Sullivan, 445–57. Bloomsbury Academic. https://recoveryhub.siue.edu/wp-content/uploads/2024/10/AI-Ethics-and-Digital-Humanities-.pdf&lt;nowiki/&gt;.'''
&lt;/div&gt;

Berry emphasizes that AI’s use in the field of Digital Humanities raises major ethical questions despite it being an apparent evolution of the field’s traditional utilization of technology to augment human research capabilities. Berry outlines this issue by comparing the modern rise of AI to Digital Humanities’ early history, highlighting that digital humanists operated as coders until they began to “'black box' the computational aspects of doing digital humanities,” thus enabling non-programmers to participate. Since AI “automating processes might cover over ethical issues by transferring them into the hashtables of the machine-learning system,” Berry argues uncritical reliance on AI tools by inexpert modern humanists risks the “algorithmization” and imposition of hierarchical, quantitative frameworks upon Digital Humanities studies. He further identifies that the field of Digital Humanities is “on the cusp of a new set of packages that will further democratize access to machine learning,” a noble goal, but one which will bring these issues to the forefront. For this reason, Berry argues a reconsideration of ethics within Digital Humanities is desperately required on both organizational and individual levels.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Brown, Richard. 2023. ''The AI Generation: How Universities Can Prepare Students for the Changing World''. DEMOS and University of London report. https://demos.co.uk/wp-content/uploads/2023/11/The-AI-Generation-2.pdf&lt;nowiki/&gt;.'''
&lt;/div&gt;

Brown argues AI will inevitably and dramatically impact all fields of education, and therefore encourages universities to seize the opportunity to lead these changes instead of merely reacting to them. His voice is echoed by esteemed organizations DEMOS and the University of London, indicating that this shift in the academic environment is already beginning. Brown argues this shift is required due to the developing capacity of AI for automating low-skilled professional tasks, an ability which risks decimating the available number of entry-level graduate positions. As a result, how employers value the workplace skills taught by current curriculums will change drastically, meaning universities must revolutionize their approach to education. Brown provides a blueprint for how universities can adapt to these changes by championing education’s prioritization of “GRASP” (General Relational, Analytic, Social, and Personal) skills as an alternative, advising universities to focus on teaching high-level and tailored skills to students instead of the generic. Universities can do this by practising “active learning” over traditional lecture formats as well as fostering extracurricular and work experience opportunities for their students.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Deng, Ruiqi, Maoli Jiang, Xinlu Yu, Yuyan Lu, and Shasha Liu. 2025. “Does ChatGPT Enhance Student Learning? A Systematic Review and Meta-Analysis of Experimental Studies.” ''Computers &amp; Education'' 227. https://doi.org/10.1016/j.compedu.2024.105224&lt;nowiki/&gt;.'''
&lt;/div&gt;

Deng and colleagues' meta-analysis of 69 experimental studies provides empirical grounding for claims about ChatGPT's pedagogical impact, revealing both opportunities and methodological challenges in assessing AI-enhanced learning. Their finding that ChatGPT interventions improve academic performance, affective-motivational states, and higher-order thinking propensities while reducing mental effort speaks directly to how assessment must shift when AI augments cognition—if mental effort decreases but learning outcomes improve, traditional measures of &quot;effort&quot; or &quot;struggle&quot; as proxies for learning may require recalibration. In their critique of current assessment methodologies the authors demonstrate that most studies evaluate only final outputs (essay quality, test scores) rather than learning processes, missing opportunities to examine how students interact with AI, what metacognitive strategies they develop, and whether AI use builds transferable skills or creates dependency. Deng et al.'s four methodological propositions—using complex project-based assessments that reveal process, evaluating long-term rather than novelty effects, prioritizing objective over self-reported measures of higher-order thinking, and employing adequate statistical power—provide a research agenda for pedagogy–AI scholarship that centres process evidence. Their documentation of disciplinary variation (language education dominates current research) while calling for cross-disciplinary synthesis focuses on avoiding discipline-specific approaches. The meta-analysis also reveals gaps in understanding collaboration (few studies examine peer learning dynamics when AI is present) and metacognition (limited research on whether students develop awareness of their own and AI's knowledge boundaries), highlighting the resulting pedagogical transformations.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Grigoli, L. Renato. 2023. “Ghosts in the Machine.” ''American Historical Association'' 61 (3). https://www.historians.org/wp-content/uploads/2024/07/Perspectives_61N3.pdf&lt;nowiki/&gt;.'''
&lt;/div&gt;

Grigoli dismisses fears of AI generated essays threatening academic integrity by arguing that “if the development of artificial intelligence results in the death of the humanities, then it will be because it will have shown that the emperor has no clothes.” He uses ChatGPT to demonstrate that although AI responses appear competent at a passing glance, they lack valuable substance, simply arranging facts in a way that “tricks the reader into… doing all the analytical work.” Clear critical analysis should be the core component of a successful humanities essay, making well-designed assessments of this field far more reliable than those focused on information retention (like engineering). Therefore, AI is not a real threat, but a valuable pedagogical tool which can demonstrate examples of clean prose and prompt students to critically analyze what constitutes critical analysis. Essentially, if an AI generated answer can pass a test, the real problem was &quot;self-inflicted&quot; by either the examiner or the question itself.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Lee, Daniel, and Edward Palmer. 2025. “Prompt Engineering in Higher Education: A Systematic Review to Help Inform Curricula.” ''International Journal of Educational Technology in Higher Education'' 22: 16. https://doi.org/10.1186/s41239-025-00503-7&lt;nowiki/&gt;.'''
&lt;/div&gt;

Lee and Palmer's systematic review establishes prompt engineering as an emergent pedagogical practice that integrates with longstanding traditions of scholarly inquiry, questioning, and rhetoric. The authors synthesize multiple frameworks (AIPROMT, CLEAR, CRISPE) that codify prompting as a learnable skill involving role specification, context provision, instruction clarity, and iterative refinement—revealing how interaction with LLMs mirrors Socratic dialogue, research question formulation, and the rhetorical tradition of audience awareness. This work positions &quot;prompting as pedagogy&quot; as a reconfiguration of existing scholarly literacies: students learning to prompt effectively must articulate their information needs precisely, anticipate how language shapes output, and iteratively refine queries based on initial results—all core practices in library research, database searching, and scholarly conversation. The authors document how educators are embedding prompt engineering across disciplines, from technical fields where students prompt AI to generate code or solve equations, to humanities contexts where prompting becomes a form of textual analysis (understanding what linguistic patterns trigger particular AI responses reveals implicit biases and training data influences). Their review also identifies ethical dimensions—well-designed prompts can mitigate AI hallucination and bias, while poorly constructed prompts amplify these issues—making prompt literacy a matter of scholarly responsibility. The authors' call for curricula that teach prompting as interdisciplinary competency aligns with how AI entangles with pedagogy across boundaries, reshaping what counts as fundamental scholarly practice in an AI-augmented knowledge environment.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Mai, Dang Thi Thuy, Cuong Van Da, and Nguyen Van Hanh. 2024. “The Use of ChatGPT in Teaching and Learning: A Systematic Review through SWOT Analysis Approach.” ''Frontiers in Education'' 9: 1328769. https://doi.org/10.3389/feduc.2024.1328769&lt;nowiki/&gt;.'''
&lt;/div&gt;

Mai and colleagues' systematic SWOT analysis of 51 studies on ChatGPT in education, organized through Biggs' 3P model (Presage-Process-Product), offers comprehensive mapping of how generative AI enters and transforms pedagogical systems at multiple scales—from individual learner characteristics (Presage) through interactive teaching-learning processes (Process) to learning outcomes and assessment products (Product). This multilevel framework reveals that ChatGPT's pedagogical impact cannot be isolated to single moments of use but ripples across entire learning ecologies: at the Presage level, ChatGPT shifts what prior knowledge students need (familiarity with prompting interfaces) and what instructor competencies are required (ability to design AI-aware assignments); at the Process level, it transforms interaction patterns from teacher–student and student–student to include human–AI dialogue that may enhance personalized scaffolding but risks reducing peer collaboration; at the Product level, it necessitates fundamental assessment redesign because traditional evaluation instruments (timed essays, closed-book exams) lose validity when AI can generate competent responses. The authors' characterization of ChatGPT as simultaneously &quot;friend&quot; (enabling personalized learning, reducing educator workload, providing instant feedback) and &quot;foe&quot; (enabling plagiarism, potentially reducing critical thinking, creating over-reliance) mirrors the section's emphasis on entanglement—pedagogy cannot simply embrace or reject AI but must negotiate tensions between efficiency and effort, personalization and depersonalization, augmentation and replacement. Mai et al.'s documentation of how educators are adapting curricula to emphasize creativity and critical thinking (skills less easily automated) while using ChatGPT for routine information provision demonstrates pedagogical evolution toward distinctly human capacities. Their call for assessment reform using complex case studies, portfolios, and process documentation rather than single-sitting exams directly supports the notion of process evidence and metacognition as being central to AI-era pedagogy, positioning assessment not as gatekeeping but as making learning processes transparent and accountable.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Oates, Angela, and Donna Johnson. 2025. “ChatGPT in the Classroom: Evaluating Its Role in Fostering Critical Evaluation Skills.” ''International Journal of Artificial Intelligence in Education'' 35 (4): 1793–1824. https://doi.org/10.1007/s40593-024-00452-8&lt;nowiki/&gt;.'''
&lt;/div&gt;

Oates and Johnson's empirical study of biomedical science master's students offers insight into how AI functions more effectively as object of critical study than as production tool, revealing pedagogical value in making AI outputs subjects for evaluation rather than endpoints of learning. Their finding that students' marks did not improve when submitting AI-generated essays but did improve when critically evaluating AI outputs demonstrates a fundamental pedagogical principle: learning occurs not in consuming AI-generated content but in interrogating it, comparing it against disciplinary standards, identifying its factual errors and rhetorical limitations, and articulating why human-authored scholarship differs. This shifts pedagogy from &quot;use AI to complete tasks&quot; toward &quot;use AI to understand knowledge construction itself&quot;—students learn about evidence evaluation, citation practices, and argumentation by analyzing where ChatGPT succeeds and fails at these scholarly fundamentals. The authors document that ChatGPT demonstrated structural coherence and grammatical accuracy but lacked the disciplinary depth and synthetic insight expected in graduate work, making visible to students the difference between surface-level fluency and genuine expertise. Their emphasis on user interaction as a variable affecting efficacy underscores that pedagogy must address not just whether AI is present but how students are taught to engage it—prompt design, output evaluation, and integration with human research become learnable scholarly practices. Oates and Johnson's conclusion that students preferred writing their own essays despite AI's availability suggests that when pedagogy centres process transparency and critical evaluation rather than output efficiency, students recognize and value the cognitive work that AI cannot replicate, focusing on pedagogy that treats AI as entangled phenomenon requiring simultaneous use and critique.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Pope, Andrew, and Rongqian Ma. 2024. “Exploring Historians’ Critical Use of Generative AI Technologies for History Education.” ''Proceedings of the Association for Information Science and Technology'' 61 (1): 1071–73. https://doi.org/10.1002/pra2.1188&lt;nowiki/&gt;.'''
&lt;/div&gt;

Pope and Ma conducted semi-structured interviews of seven history professors to assess their attitudes toward employing GenAI tools in their teaching. Understanding this stance is important because Pope and Ma believe incoherent and mismatched approaches could inhibit scholarly communication and undermine academic integrity. The survey demonstrated historians had major concerns about GenAI’s development, especially regarding plagiarism. Respondents were particularly divided on whether copying an AI’s work was academic misconduct. However, historians had far fewer concerns about using GenAI to &quot;augment&quot; human abilities or tailor support to students—although senior academics maintained substantially greater reservations. The historians that were interviewed concurred that critiquing AI generated text could improve a student’s media literacy. Pope and Ma’s study suggests that historians consistently doubt the quality of AI generated responses even when willing to employ it.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Tan, Myles Joshua Toledo, and Nicholle Mae Amor Ttan Maravilla. 2024. “Shaping Integrity: Why Generative Artificial Intelligence Does Not Have to Undermine Education.” ''Frontiers in Artificial Intelligence'' 7: 1471224. https://doi.org/10.3389/frai.2024.1471224&lt;nowiki/&gt;.'''
&lt;/div&gt;

Tan and Maravilla provide theoretical grounding for understanding how generative AI can be integrated into pedagogy without compromising academic integrity, arguing that responsible implementation depends on alignment with constructivist learning theory and self-determination theory. The authors position AI not as a threat to authentic learning but as a catalyst that necessitates pedagogical transformation—shifting from transmission models toward environments where students actively construct knowledge using AI as one tool among many. Their framework emphasizes process transparency through explicit discussion of AI's role in knowledge construction and ethical reflection through examining how GAI outputs are generated, what assumptions they embed, and where they may mislead or constrain inquiry. This work addresses pedagogy-as-entanglement by showing how GAI forces educators to make visible the epistemic practices that traditional assessment often left implicit: citation tracing, source evaluation, argument construction, and the iterative nature of scholarly writing. Tan and Maravilla argue that rather than banning AI to preserve integrity, educators should redesign assessment to require demonstration of process—portfolios showing prompt refinement, comparison of AI outputs with human-authored sources, and metacognitive reflection on when and why AI was consulted. Their synthesis of educational theory with practical implementation strategies makes this work useful for understanding how pedagogy must evolve to treat AI as both subject matter (what students must understand about how AI functions) and scaffolding (how AI can support learning when used transparently and reflectively).

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Yim, Iris Heung Yue, and Jiahong Su. 2025. “Artificial Intelligence (AI) Learning Tools in K-12 Education: A Scoping Review.” ''British Journal of Educational Technology'' 56 (1): 169–196. https://doi.org/10.1007/s40692-023-00304-9&lt;nowiki/&gt;.'''
&lt;/div&gt;

Yim and Su's scoping review of AI literacy education in K-12 contexts provides grounding for understanding how pedagogy approaches AI as an object of study, not merely as a tool, revealing how students across age groups learn to understand, critique, and create with AI systems. The authors document how intelligent agents (Google Teachable Machine, Learning ML) and software platforms (Scratch, Python) enable students to engage with AI's underlying mechanisms—training models, observing how data shapes outputs, and experiencing firsthand how algorithmic decision-making operates. This approach treats AI as epistemological phenomenon: students don't just use pretrained models but build simple systems themselves, making visible how AI &quot;learns&quot; and where its learning breaks down (limited training data, biased datasets, inability to generalize beyond training conditions). Yim and Su's synthesis of pedagogical strategies—project-based learning where students create AI applications, human-computer collaboration examining how humans and machines complement each other, and game-based approaches making AI concepts accessible—demonstrates how educators scaffold understanding from concrete manipulation to abstract reasoning about intelligence and automation. The review's attention to cognitive, affective, and behavioural learning outcomes moves beyond narrow skill acquisition to examine how AI literacy shapes students' broader epistemic stance: understanding AI's capabilities and limitations, recognizing when algorithmic solutions are appropriate, and developing critical awareness of AI's social implications. Their emphasis on age-appropriate pedagogies and the importance of unplugged activities (learning AI concepts through physical manipulation before digital implementation) provides models for how pedagogy must adapt to learners' developmental stages when teaching about AI systems. This work's K-12 focus complements higher education studies in this section by showing how foundational AI literacy built through hands-on exploration creates readiness for more sophisticated critical engagement with AI as both tool and object of study in advanced scholarship.

== Service and Peer Review ==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Checco, Alessandro, Lorenzo Bracciale, Pierpaolo Loreti, Stephen Pinfield, and Giuseppe Bianchi. 2021. “AI-Assisted Peer Review.” ''Humanities and Social Sciences Communications'' 8: 25. https://doi.org/10.1057/s41599-020-00703-8&lt;nowiki/&gt;.'''
&lt;/div&gt;

Checco et al.'s study represents crucial early (pre-GenAI) empirical work demonstrating that AI can predict peer review outcomes based on &quot;superficial&quot; manuscript features—readability metrics, formatting consistency, reference list structure, linguistic patterns—with surprising accuracy, training neural networks on 3,300 conference papers to correlate these proxy measures with eventual accept/reject decisions. This finding has profound implications for understanding AI's operational role: the research reveals that much of what passes as peer review judgment operates on detectable patterns (clear writing, proper citation formatting, adherence to disciplinary conventions) that AI can identify and assess, potentially automating routine quality checks and flagging submissions unlikely to meet standards. However, the authors explicitly position their work as supporting &quot;semi-automated&quot; rather than fully automated review, emphasizing AI's role in pre-screening and administrative tasks (matching manuscripts with reviewers based on topic modelling, identifying obvious deficiencies) rather than intellectual evaluation. The paper's most valuable contribution lies in its systematic exploration of ethical implications: algorithmic bias risks (AI might penalize unconventional but innovative work, discriminate against non-native English writers, favour institutional prestige markers), transparency requirements (making AI decision criteria auditable), and the necessity of human oversight to prevent automation from calcifying existing disciplinary hierarchies. By documenting both AI's predictive capabilities on operational dimensions and its inherent limitations on substantive judgment, Checco et al. provide empirical foundation for designing peer review systems where AI handles standardized identification tasks while human expertise remains authoritative for evaluative assessment, directly instantiating the core principle that operational assistance must not migrate into epistemic territory.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Hosseini, Mohammad, and Serge P. J. M. Horbach. 2023. “Fighting Reviewer Fatigue or Amplifying Bias? Considerations and Recommendations for Use of ChatGPT and Other Large Language Models in Scholarly Peer Review.” ''Research Integrity and Peer Review'' 8 (1): 15. https://doi.org/10.21203/rs.3.rs-2587766/v1&lt;nowiki/&gt;.'''
&lt;/div&gt;

Published early in the ChatGPT era, Hosseini and Horbach's analysis provides a prescient examination of how LLM integration transforms both the pragmatics and ethics of peer review labour. The authors document LLMs' potential to combat reviewer fatigue by automating time-consuming tasks—transforming informal reviewer notes into polished reports, generating structured feedback on manuscript sections, identifying linguistic or formatting issues—thereby potentially expanding the pool of contributors who can participate effectively despite language barriers or time constraints. However, the article's core contribution lies in its still-useful systematic identification of risks that emerge when operational assistance crosses into epistemic territory: LLMs trained on existing literature may amplify disciplinary biases (favouring established paradigms over novel approaches), geographic biases (privileging research contexts well-represented in training data), or methodological orthodoxies (flagging unconventional designs as errors rather than innovations). The authors demonstrate through examples how ChatGPT can generate cynical or biased reviews that violate Mertonian norms of universalism, and how confidentiality breaches can occur when reviewers input manuscript excerpts into external AI platforms without institutional safeguards. Hosseini and Horbach's recommendations—mandatory disclosure of LLM use in reviews, human accountability for all AI-generated content, training in bias recognition, and institutional policies prohibiting upload of confidential materials—have influenced subsequent journal guidelines and provide foundational ethical framework for understanding why guardrails against leakage and disclosure norms become operational necessities rather than optional best practices in AI-entangled peer review systems.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Shcherbiak, Anna, Hooman Habibnia, Robert Böhm, and Susann Fiedler. “Evaluating Science: A Comparison of Human and AI Reviewers.” ''Judgment and Decision Making'' 19 (2024): e21. https://doi.org/10.1017/jdm.2024.24&lt;nowiki/&gt;.'''
&lt;/div&gt;

In this study, a large-scale field experiment comparing GPT-4 with human reviewers on conference abstracts provides empirical evidence about AI's capabilities and limitations in evaluative judgment. It demonstrates that while AI can approximate human performance on certain classification tasks—identifying &quot;very best&quot; abstracts shows moderate alignment—detailed evaluative assessments reveal persistent gaps, with human-AI agreement comparable to human-human variability, suggesting AI does not systematically outperform baseline reviewer disagreement. Critically, the research shows humans substantially outperform AI at detecting AI-generated versus human-written content, with detection tools like GPTZero exhibiting higher accuracy than GPT-4 itself when evaluating authorship. This finding has direct implications for peer review integrity when AI-generated manuscripts enter the submission pipeline. The authors position AI as effective for prescreening—rapidly filtering submissions for basic quality thresholds, identifying obvious errors, flagging compliance issues—while demonstrating it lacks the contextual understanding necessary for nuanced scientific judgment about significance, impact, or methodological soundness. The paper's methodological rigour in isolating human-versus-AI performance dimensions provides context for understanding where operational assistance (screening) legitimately ends and where human evaluative authority (substantive assessment) must begin, directly addressing the guiding principle that human judgment remains central even in AI-augmented workflows.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Lim, Gim Hui, M. L. Tan, V. C. W. Hoe, and D. Koh. 2025. “Generative AI in Peer Review Process for Occupational Health.” ''Occupational Medicine'' 75 (5): 242–49. https://doi.org/10.1093/occmed/kqaf051.'''
&lt;/div&gt;

Lim and colleagues' empirical study comparing Microsoft Copilot, ChatGPT, and Google Gemini against human reviewers on eight occupational health manuscripts provides granular quantitative evidence about AI's operational capabilities and limitations in peer review tasks. The research demonstrates that AI tools significantly outperform humans in providing feedback (mean score 3.44 vs. human baseline, p&lt;0.001) across dimensions of relevance, completeness, accuracy, error identification, and constructiveness—documenting AI's strength in systematic checking tasks like identifying missing citations, flagging methodological inconsistencies, noting formatting errors, and pointing out unclear explanations. However, humans substantially outperform AI in generating actionable recommendations (mean score 3.36, p&lt;0.01), with AI showing particular deficiencies in suggesting substantive revisions, connecting findings to broader literature, or identifying conceptual limitations. This performance asymmetry instantiates the operational/epistemic division: AI excels at identification tasks (what's wrong, what's missing) but struggles with evaluative tasks (how to improve, what matters). The study also quantifies efficiency gains (AI reviews complete in 11 minutes versus 45 for humans) while documenting critical limitations: AI outputs contain fabricated references, generate plausible-sounding but inaccurate technical assertions, and require human verification to prevent propagation of errors. Lim et al.'s work demonstrates that even when AI shows superior performance on specific metrics, its integration into peer review requires careful task decomposition—leveraging speed and comprehensiveness for checking functions while preserving human authority for substantive guidance—making it essential evidence for designing hybrid human-AI workflows where operational assistance enhances rather than replaces evaluative expertise.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Sun, Zhuanlan. 2025. “Large Language Models in Peer Review: Challenges and Opportunities.” ''Scientometrics'' 130 (10): 5503–5546. https://doi.org/10.1007/s11192-025-05440-w&lt;nowiki/&gt;.'''
&lt;/div&gt;

Sun provides essential mapping of LLM applications across the peer review lifecycle, categorizing five distinct operational roles: checklist assistants for formatting and protocol adherence, reviewer selection aids that match manuscripts with appropriate expertise, feedback generators for preliminary assessments, bias detectors that flag methodological or statistical irregularities, and agents that coordinate multi-stage review workflows. The article systematically examines technical approaches including prompt engineering strategies, model evaluation frameworks, and architectural designs for integrating LLMs into editorial management systems. The author argues that while LLMs excel at standardized operational tasks—checking reference integrity, identifying duplicated content across submission databases, verifying compliance with reporting guidelines—they remain fundamentally limited in assessing research novelty, theoretical contributions, and domain-specific methodological rigour. The analysis emphasizes that current LLM limitations (inadequate scientific validation, domain knowledge gaps, inability to analyze complex datasets, ethical concerns around bias perpetuation) position them as supportive tools within human-led processes rather than autonomous decision-makers. This work is useful in understanding operational versus epistemic divisions of labour in AI-assisted scholarship service and documenting the technical infrastructure through which AI becomes entangled with peer review operations while maintaining clear boundaries around human evaluative judgment.

== AI and Scholarship Infrastructures ==

=== Organizational Infrastructures ===

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Batool, Amna, Didar Zowghi, and Muneera Bano. 2025. “AI Governance: A Systematic Literature Review.” ''AI and Ethics'' 5: 3265–3279. https://doi.org/10.1007/s43681-024-00653-w&lt;nowiki/&gt;.'''
&lt;/div&gt;

Batool and colleagues' (2025) systematic literature review offers a comprehensive mapping of AI governance across multiple levels—team, organization, industry, national, and international. The authors utilize a structured analytical framework that examines who governs (stakeholders and roles), what is governed (data, algorithms, systems), when governance occurs (stages in the AI lifecycle), and how it is implemented (frameworks, tools, policies). The article reveals that current governance practices remain fragmented and inconsistent, with significant gaps at the national and international levels. Applied to the context of higher education, this multi-level perspective is essential for understanding how research institutions must position themselves within broader governance ecosystems. Because organizational governance currently operates without clear external scaffolding, research institutions are often forced to improvise institutional arrangements rather than implement established templates. While the paper is broad in scope, its categorization of governance artifacts illuminates the range of mechanisms available to scholarly organizations: from technical tools like algorithmic auditing to organizational structures like ethics committees. Ultimately, the authors' findings highlight the challenges facing research institutions as they attempt to coordinate AI oversight across distributed, autonomous units—such as libraries implementing discovery tools or IT departments deploying infrastructure—demonstrating why cross-functional coordination is both necessary and difficult when existing governance structures were not designed to span these boundaries.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Hadley, Emma, Alan Blatecky, and Megan Comfort. 2025. “Investigating Algorithm Review Boards for Organizational Responsible Artificial Intelligence Governance.” ''AI and Ethics'' 5: 2485–2495. https://doi.org/10.1007/s43681-024-00574-8&lt;nowiki/&gt;.'''
&lt;/div&gt;

Hadley and colleagues provide empirical documentation of algorithm review boards (ARBs) as organizational governance mechanisms, interviewing technical contributors across sectors to examine ARB membership, scope, success factors, and limitations. Their findings reveal ARBs as cross-functional bodies integrating diverse expertise (technical specialists, ethicists, domain experts, legal advisors, non-specialist stakeholders) to review AI systems for potential risks and harms, operating alongside other responsible AI approaches like policies, audits, and dedicated governance roles. The study's key insight that institutional review boards alone prove insufficient for algorithm governance and that ARBs function most effectively when integrated with existing organizational processes rather than operating as isolated oversight bodies speaks directly to research institutions' governance challenges. The article's documentation of financial tensions between profit motives and responsible AI costs, while focused on commercial contexts, translates to research institutions facing pressure to adopt AI for efficiency gains while managing ethical risks with constrained resources. Hadley et al.'s call for standardized ARB effectiveness metrics points to the broader challenge of demonstrating governance value in organizations where responsible AI practices compete with other institutional priorities for attention and investment.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Janssen, Marijn. 2025. “Responsible Governance of Generative AI: Conceptualizing GenAI as Complex Adaptive Systems.” ''Policy and Society'' 44 (1): 38–51. https://doi.org/10.1093/polsoc/puae040&lt;nowiki/&gt;.'''
&lt;/div&gt;

Janssen's conceptual article reframes generative AI governance as managing complex adaptive systems characterized by co-evolution, emergent properties, and non-linear interactions between technical and social elements, directly challenging technology-deterministic approaches that treat AI as static tool requiring one-time organizational accommodation. This systems perspective is essential for understanding why research institutions struggle with AI governance: the article demonstrates how AI systems and organizational contexts mutually shape each other through feedback loops, making governance an ongoing adaptive process rather than implementation of fixed policies. Janssen argues that effective organizational stewardship requires holistic, outward-focused governance attending to how AI systems interact with broader organizational processes, public values, and societal concerns—moving beyond narrow risk mitigation to address joint accountability across system components including people, policies, data, and algorithms. For research institutions embedding AI in knowledge infrastructures, this framing illuminates why isolated departmental responses prove insufficient: cataloging systems using AI for metadata generation, research platforms deploying AI for literature synthesis, and administrative systems using AI for resource allocation together constitute an organizational AI ecosystem whose emergent behaviours cannot be governed through component-level oversight alone. The article's emphasis on selecting and combining appropriate policy instruments into adaptive governance packages provides conceptual foundation for cross-functional coordination mechanisms, suggesting that effective institutional stewardship requires deliberate orchestration of technical standards, organizational procedures, and stakeholder engagement processes that together shape AI's organizational trajectory. Janssen's work underscores that AI governance is not primarily technical implementation challenge but organizational transformation requiring institutions to develop new capabilities for managing sociotechnical co-evolution.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Papagiannidis, Emmanouil, Patrick Mikalef, and Kieran Conboy. 2025. “Responsible Artificial Intelligence Governance: A Review and Research Framework.” ''The Journal of Strategic Information Systems'' 34 (2): 101885. https://doi.org/10.1016/j.jsis.2024.101885&lt;nowiki/&gt;.'''
&lt;/div&gt;

Papagiannidis and colleagues provide theoretical grounding for understanding how organizations operationalize responsible AI principles through governance structures. Their scoping review synthesizes disparate literature to construct a conceptual framework differentiating between structural practices (formal roles, committees, reporting lines), relational practices (stakeholder engagement, accountability mechanisms), and procedural practices (auditing protocols, monitoring systems) across the AI lifecycle. This tripartite framework is valuable for research institutions navigating the challenge of translating broad ethical commitments into actionable organizational arrangements. The article explicitly addresses how governance antecedents like leadership commitment and regulatory pressure shape implementation, and how governance practices in turn affect outcomes like trust, compliance, and innovation capacity. The authors' critical reflection on responsible AI governance reveals tensions inherent to institutional stewardship: between centralized oversight and distributed expertise, between standardized protocols and context-sensitive judgment, between rapid AI deployment and deliberative ethical review. For research organizations managing AI's entanglement with knowledge infrastructures, this work provides vocabulary and analytical categories for diagnosing governance gaps and designing institutional responses that embed responsibility throughout organizational systems rather than treating ethics as external constraint.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Weber, Michael, Martin Engert, Norman Schaffer, Jörg Weking, and Helmut Krcmar. 2023. “Organizational Capabilities for AI Implementation—Coping with Inscrutability and Data Dependency in AI.” ''Information Systems Frontiers'' 25: 1549–1569. https://doi.org/10.1007/s10796-022-10297-y&lt;nowiki/&gt;.'''
&lt;/div&gt;

Weber and colleagues identify four organizational capabilities essential for AI implementation, addressing AI's distinctive characteristics that distinguish it from previous information technologies: inscrutability (difficulty predicting probabilistic outputs and explaining decision processes) and data dependency (reliance on high-quality, continuously updated data for system performance). Their capability framework—encompassing AI Project Planning, Co-Development, Data Management, and AI Model Lifecycle Management—provides actionable guidance for research institutions developing internal capacity to steward AI systems. The article's grounding in expert interviews from diverse organizational contexts reveals that AI implementation failures often stem not from technical deficits but from organizational incapacity to manage sociotechnical complexity: inscrutability requires enhanced planning and stakeholder communication practices to align expectations around uncertain outcomes, while data dependency demands robust governance of data quality, provenance, and evolution throughout systems' operational lives. For research organizations, these capabilities map onto critical institutional functions: libraries developing metadata systems must manage data quality for AI cataloguing tools; research offices supporting computational scholarship must plan projects acknowledging unpredictable AI behaviour; IT departments maintaining infrastructure must implement lifecycle management ensuring model performance doesn't degrade as institutional data changes. The article's emphasis on Co-Development capability—bringing together technical specialists, domain experts, and end-users to jointly shape AI systems—speaks directly to cross-functional coordination challenges in research institutions where AI touches multiple organizational domains. Weber et al.'s framework reveals that organizational stewardship requires not just governance structures (committees, policies, review processes) but operational capabilities (planning methods, collaboration practices, technical procedures) embedded in day-to-day institutional work. This capability perspective shifts attention from abstract principles to concrete organizational competencies that determine whether responsible AI rhetoric translates into institutional practice.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Wu, Chuhao, He Zhang, and John M. Carroll. 2024. “AI Governance in Higher Education: Case Studies of Guidance at Big Ten Universities.” Preprint, ''arXiv'', September 3. https://doi.org/10.48550/arXiv.2409.02017&lt;nowiki/&gt;.'''
&lt;/div&gt;

Wu and colleagues provide rare empirical documentation of how major research universities translate AI governance principles into institutional practice, examining guidance documents from fourteen Big Ten universities to identify organizational patterns and role-specific strategies. Their analysis reveals three key organizational dimensions: multi-unit governance involving information technology departments, teaching and learning centres, libraries, and research offices operating with distributed authority rather than centralized control; role-specific guidance differentiating expectations for faculty, students, staff, and researchers rather than applying uniform policies; and educational-advisory approaches emphasizing learning and adaptation over compliance enforcement. This case-study evidence illuminates the pragmatic challenges research institutions face when operationalizing AI oversight: how to coordinate across functional silos with different mandates, expertise, and risk tolerances; how to balance flexibility (needed because AI applications vary dramatically across contexts) with consistency (needed to ensure institutional values are upheld); how to position governance as enabling innovation rather than constraining it. The article's documentation of specific institutional mechanisms, such as data classification systems limiting what information can be shared with AI tools, or Socratic guidance approaches that pose questions rather than dictate answers, provides concrete examples of organizational stewardship in action. For understanding AI's organizational entanglement with knowledge infrastructures, this work demonstrates how governance emerges through negotiation among multiple institutional actors, each bringing domain expertise and jurisdictional claims, requiring coordination mechanisms that existing organizational charts may not accommodate.

=== Publishing, Communication, Engagement Infrastructures ===

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Bergstrom, Tracy, and Dylan Ruediger. 2024. “A Third Transformation? Generative AI and Scholarly Publishing.” ''Ithaka S+R''. October 30, 2024. https://doi.org/10.18665/sr.321519&lt;nowiki/&gt;.'''
&lt;/div&gt;

Drawing on interviews with leaders from publishers, technology disruptors, academic libraries, and scholarship, Bergstrom and Ruediger map the strategic landscape of AI adoption across the publishing industry. The report identifies a bifurcated future: an incrementalist scenario where AI produces efficiency gains without fundamentally altering industry dynamics, versus a transformative scenario creating disruption comparable to or exceeding previous digital transformations. For search and discovery, most interviewees anticipate heavy AI impact, with tools already expanding capabilities through summarization and chatbot interfaces—potentially disrupting the linear progression from discovery to understanding by introducing AI-enabled synthesis. For peer review, interviewees expressed optimism that AI could address chronic strain through &quot;pre-review&quot; feedback, assistance with copy editing and misconduct detection, and more efficient reviewer identification, while raising concerns about accuracy, confidentiality, and maintaining human judgment in evaluation. The authors document a competitive threat from large technology companies: scenarios where commercial LLMs become default interfaces for accessing scholarly content pose significant challenges to publisher positioning. Content licensing to foundation model developers offers clear monetization paths, but broader revenue implications remain uncertain. The analysis identifies a critical research integrity challenge: ensuring transparent standards for AI usage while upholding provenance, attribution, reproducibility, and transparency in an environment of increasing automation. Smaller publishing organizations may struggle to match larger entities' adaptive capacity, potentially accelerating industry consolidation. 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Broussard, Meredith. 2023. “The Challenges of AI Preservation.” ''The American Historical Review'' 128 (3): 1378–81. https://doi.org/10.1093/ahr/rhad366.'''
&lt;/div&gt;

Broussard illustrates how the current impermanence of digital storage is producing a nightmare for future historians, as content is hidden away by licensing agreements or simply disappears when its host platform ceases to exist. Earlier ideals of the internet preserving a “complete first draft of history” are far from the reality, and problems only intensify when considering the development of AI, which Broussard compares to the printing press. For example, one could access a record of a physical newspaper published on a given day, but Google Search’s software is constantly changing with no canonical daily version, which means no historian could ever hope to examine a comparable snapshot of an AI. Operations like the Internet Archive and the development of emulation can help diminish losses, but it must be recognized that the digital world is decaying.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Buitrago-Ciro, Jairo, Marta Samokishyn, Rachel Moylan, Jonathan Hernández Pérez, Oluwabunmi Bakare-Fatungase, and Carmel Firdawsi. 2025. “Bridging the AI Gap: Comparative Analysis of AI Integration, Education, and Outreach in Academic Libraries.” ''IFLA Journal'' 51 (3): 682–702. https://doi.org/10.1177/03400352251325274. '''
&lt;/div&gt;

Buitrago-Ciro et al. examine the websites of 40 libraries in North America, Western Europe, Latin America, and Africa to explore how they have integrated AI technologies into their services, policies, and outreach efforts. Overall, the authors found a geographic divide in the integration of AI into library services, because almost all North American and European libraries had AI educational outreach activities and resources, while only five (out of ten) Latin American libraries and one (out of ten) African libraries did outreach activities. However, AI integration into library services and development of library AI policies and guidelines was more uncommon across all regions, as less than half of North American and European libraries engaged in these activities, while only one library in Latin America and one in Africa integrated AI into their services and none had specific library AI policies. These regional differences in AI integration stem from each region’s socioeconomic contexts, social inequalities, and technological gaps that present additional challenges for AI adoption in African and Latin American libraries. 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Gulson, Kalervo N., and P. Taylor Webb. 2023. “Steering the Mind Share: Technology Companies, Policy and Artificial Intelligence Research in Universities.” ''Discourse: Studies in the Cultural Politics of Education'' 44 (2): 195–207. https://doi.org/10.1080/01596306.2021.1981828. '''
&lt;/div&gt;

Gulson and Webb (2023) examine how major technology companies are actively reshaping the landscape of artificial intelligence research within universities. Drawing on interviews with computer scientists as part of a broader international project, the authors investigate three key areas: the influence of tech companies on AI research practices, the policy frameworks that foster academia-industry collaborations, and the role of &quot;open science&quot; in facilitating the transfer of academic ideas to the corporate sector. The study highlights that the boundaries between academic and corporate research have become highly porous. Companies like Google do not merely act as external funders; they are deeply embedded within university ecosystems, actively steering research directions. Furthermore, the authors illustrate how national policies, such as Canada’s Pan-Canadian Artificial Intelligence Strategy, legitimize and accelerate this corporate influence by heavily incentivizing industry partnerships. While these collaborations provide universities with crucial resources and drive innovation, Gulson and Webb warn that they also raise significant concerns regarding conflicts of interest and the corporatization of open science. Ultimately, the authors argue that corporate funding creates powerful feedback loops among tech companies, policy-makers, and academics, effectively allowing industry to capture the &quot;mind share&quot; of university research.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Kousha, Kayvan, and Mike Thelwall. 2024. “Artificial Intelligence to Support Publishing and Peer Review: A Summary and Review.” ''Learned Publishing'' 37 (1): 4–12. https://doi.org/10.1002/leap.1570&lt;nowiki/&gt;.'''
&lt;/div&gt;

Kousha and Thelwall provide a systematic mapping of AI tool deployment across the scholarly publishing pipeline, distinguishing demonstrated capabilities from promotional claims. For journal recommendation, the review documents AI-powered systems, including Springer Nature Journal Suggester, Wiley Journal Finder, IEEE Publication Recommender, and JANE (Journal/Author Name Estimator), that analyze text similarity with previously published articles and reports high accuracy rates for appropriate journal matching. The analysis of initial quality control covers a diverse toolkit for plagiarism detection, robot author detection, methods checking, automated statistical verification, transparency and reproducibility checking and manuscript structure validation. Commercial systems draw on databases to suggest appropriate reviewers; the Natural Science Foundation of China's AI-assisted reviewer recommender for grant applications reports approximately 80% accuracy. However, the review identifies a critical boundary: while AI proves effective for finding reviewers and conducting initial quality checks, its value in performing the actual substantive review process &quot;has not been clearly demonstrated.&quot; The synthesis reveals that substantial efficiency improvements are achievable in labour-intensive administrative tasks, while human judgment remains integral to core intellectual evaluations—a distinction essential for understanding where AI integration in publishing will proceed incrementally versus face fundamental obstacles.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Ma, Lai. 2024. “Generative AI for Academic Publishing? Some Thoughts About Epistemic Diversity and the Pursuit of Truth.” ''KULA: Knowledge Creation, Dissemination, and Preservation Studies'' 7 (1): 1–5. https://doi.org/10.18357/kula.287.'''
&lt;/div&gt;

Ma (2024) critiques the integration of generative AI in academic publishing, arguing that the drive for automation threatens the central values of epistemic diversity and bibliodiversity. By invoking the &quot;Sokal Hoax,&quot; the author illustrates the danger of AI-generated &quot;bullshit&quot;—content that mimics the formal structures of scholarship while remaining devoid of actual meaning. Ma specifically uses Scopus AI as a case study to demonstrate how the platformization of scholarly data creates a feedback loop that reinforces the &quot;Matthew Effect,&quot; where established, English-language, and well-resourced publications are disproportionately amplified. This process, Ma warns, leads to &quot;epistemic injustice&quot; by marginalizing non-Western research and niche topics that are underrepresented in training datasets. The paper serves as a vital warning: without robust data surveillance and human-centric safeguards, the AI-accelerated publishing model may exacerbate peer-review crises and citation monopolies, ultimately undermining the public trust and diverse knowledge creation that open scholarship aims to protect.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Mitchell, Peta, Michelle Riedlinger, Jake Goldenfein, Aaron Snoswell, Jean Burgess, and Kevin Witzenberger. 2025. “Research Genai: Situating Generative AI in the Scholarly Economy.” ''AoIR Selected Papers of Internet Research''. https://doi.org/10.5210/spir.v2024i0.14006.'''
&lt;/div&gt;

Mitchell et al. focus upon the oft-overlooked subfield of Generative AI tools known as “RGAI”, research-focused models which they argue represent “complex sociotechnical systems.” Hepp et al.’s definition of AI as a “sensitizing concept” and Watermeyer’s consideration of AI as a “labor accelerator” are used to situate this argument within the “scholarly economy” before the authors expand upon these theories, arguing RGAI should be approached as a form of “platform capitalism” akin to academia.edu. To evidence this stance, the authors examine the highly distinct RGAI models “Consensus” and “Writefull” as case studies. “Consensus” is designed to produce an academic “ConsensusMeter” by combining a proprietary LLM with OpenAI technology, while “Writefull” “aims to simplify… the often challenging task of scholarly writing” by employing custom AI models. Mitchell et al. highlight that although both tools are presented as independent and bespoke, they have major corporate backing. This deeply conflicts with the research principles of open scholarship, so Mitchell et al. aim to develop an index of RGAI which are appropriate for use in research.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Pividori, Milton, and Casey S. Greene. 2024. “A Publishing Infrastructure for Artificial Intelligence (AI)-Assisted Academic Authoring.” ''Journal of the American Medical Informatics Association'' 31 (9): 2103–13. https://doi.org/10.1093/jamia/ocae139&lt;nowiki/&gt;.'''
&lt;/div&gt;

The Manubot AI Editor implements a concrete technical solution to the provenance problem in AI-assisted scholarship through three integrated components: a Python library, a GitHub Actions workflow, and a prompt generator. This architecture addresses provenance directly: all changes are tracked through version control, creating a clear audit trail distinguishing human-authored from machine-generated text and documenting exactly how AI suggestions were accepted, modified, or rejected. Evaluation proceeded through five case studies using both human and automated assessment. Human evaluators assessed whether revisions preserved original meaning and important details, avoided introducing incorrect information, and maintained correct formatting. Automated &quot;LLM-as-a-Judge&quot; iterative assessment evaluated paragraph pairs across criteria including sentence structure clarity, ease of understanding, and grammatical correctness. The evaluations found that models could grasp complex academic concepts and enhance text quality, with particular effectiveness in text-based sections like introductions and discussions. The human-in-the-loop design, where AI suggestions function as proposed edits rather than direct insertions, mitigates risks of incorrect information while preserving authorial agency over final content.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Razack, Habeeb Ibrahim Abdul, Sam T. Mathew, Fathinul Fikri Ahmad Saad, and Saleh A. Alqahtani. 2021. “Artificial intelligence-assisted tools for redefining the communication landscape of the scholarly world.” ''Science Editing''. https://doi.org/10.6087/kcse.244. '''
&lt;/div&gt;

Razack et al. argue AI will transform publishing into a technology-driven industry, streamlining dissemination of scholarship “for the betterment of humankind.” Exploring current trends via case studies, they emphasize AI’s impact upon human performance over its independent “creative” role. They argue AI could benefit the “prospective” researcher by predicting an article’s “citation impact,” identifying evolving research trends, and locating relevant research journals to publish in, cutting past low-charging and “predatory OA journals” which “malign integrity” by publishing “compromised content.” Meanwhile, “retrospective” editors could employ AI to detect plagiarism, streamline peer review, and format publications. For Razack et al., the rise of AI can therefore be compared to the rise of the typewriter, swift adoption likely promoting &quot;human-machine collaboration&quot; over replacement.

=== Accountability-related Infrastructures ===

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Ngulube, Patrick, and Neema Florence Vincent Mosha. 2024. “Integrating Artificial Intelligence-Based Technologies ‘Safely’ in Academic Libraries: An Overview through a Scoping Review.” ''Technical Services Quarterly'' 42 (1): 46–67. https://doi.org/10.1080/07317131.2024.2432093&lt;nowiki/&gt;.'''
&lt;/div&gt;

Ngulube and Mosha (2025) conduct a scoping review examining the state of research on ethical issues and perceived risks in AI integration within academic libraries. Analyzing 28 studies published before 2024, the authors reveal that research on safe AI adoption in libraries remains nascent, with significant gaps in theoretical grounding and methodological diversity. The review identifies critical ethical concerns including algorithmic bias, privacy violations, reduced transparency and accountability, and job displacement—yet finds that existing literature disproportionately emphasizes employment risks while neglecting environmental and planetary impacts. The authors note that ethical considerations have not taken centre stage in library and information science research, as evidenced by the scarcity of relevant keywords and abstracts in the literature. A major finding is that most studies employ quantitative methodologies at the expense of qualitative and mixed-methods approaches, and only 18% employ explicit theoretical frameworks. The review underscores that academic libraries must navigate the dual challenge of leveraging AI's operational efficiencies while ensuring ethical standards of inclusivity, accessibility, and fair information use—a task complicated by the absence of established best practices and the need for human-centred approaches to AI governance.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''“Realising Potential, Supporting Users: IFLA Statement on Copyright and Artificial Intelligence.” n.d. IFLA. Accessed May 1, 2025. https://www.ifla.org/news/realising-potential-supporting-users-ifla-statement-on-copyright-and-artificial-intelligence/. '''
&lt;/div&gt;

This statement aims to help IFLA member libraries in navigating copyright issues and developing programs relevant to AI, positioning libraries as innovators “uniquely situated to lead” in supporting, training, and utilizing AI. However, restrictions stem from rightsholders, economic and moral copyright laws, and health, safety, and privacy laws. Libraries should therefore be guided by the most appropriate policy sources to mitigate restrictions by ensuring AI tools do not compromise areas of concern. Libraries are further recommended to advise decision-makers to permit mining legally accessed content, address bias by promoting “the widest possible access,” build capacity, awareness, and training for evolving technologies, and monitor AI standards. Governments are recommended to follow existing human rights regulations, avoid using copyright law as a “blunt force tool,” develop ethical AI practices, and fund repositories of AI training data—alongside AI companies themselves. Both rightsholders and vendors are advised to avoid language in contracts which restricts the use of AI or prevents exceptions. Overall, this document aims to promote AI by making as much content available as possible.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Werder, Karl, Balasubramaniam Ramesh, and Rongen (Sophia) Zhang. 2022. “Establishing Data Provenance for Responsible Artificial Intelligence Systems.” ''ACM Transactions on Management Information Systems'' 13 (4): 1–25. https://doi.org/10.1145/3503488&lt;nowiki/&gt;.'''
&lt;/div&gt;

Werder et al. provide a framework for understanding audit trails in the context of AI and research data management, arguing that robust data provenance is not merely a technical feature but a prerequisite for achieving accountability in AI systems. They detail the requirements for a comprehensive provenance system, capable of tracking data from its origin through various transformations and into model training and deployment. This is directly relevant to research infrastructures, as it outlines how repositories and data management platforms can and must evolve to support AI-driven research. The authors’ multi-layered architectural proposal offers a concrete vision for how a research institution could implement a system to audit data pipelines, identify sources of bias, and ensure regulatory compliance. By connecting provenance to the broader goal of “Responsible AI,” the paper provides the conceptual tools for evaluating whether a research infrastructure’s data governance is sufficient to handle the accountability challenges posed by AI.

== Audience ==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''de Angelis, Luigi, Francesco Baglivo, Guglielmo Arzilli, Gaetano Pierpaolo Privitera, Paolo Ferragina, Alberto Eugenio Tozzi, and Caterina Rizzo. “ChatGPT and the Rise of Large Language Models: The New AI-Driven Infodemic Threat in Public Health.” ''Frontiers in Public Health'' 11 (2023): 1166120. https://doi.org/10.3389/fpubh.2023.1166120&lt;nowiki/&gt;.'''
&lt;/div&gt;

De Angelis and colleagues examine the emergence of Large Language Models, particularly ChatGPT, as a novel public health threat through the lens of &quot;AI-driven infodemic.&quot; The authors trace the rapid evolution of LLMs from earlier transformer-based models through GPT-3 to ChatGPT, highlighting how each iteration has increased the capacity to generate fluent, authoritative-sounding text at scale. Critically, they identify a fundamental misalignment problem: despite efforts to fine-tune these models through reinforcement learning from human feedback, LLMs remain prone to generating plausible-sounding but factually incorrect or fabricated information—a vulnerability particularly dangerous in medical and health contexts. The paper's central argument is that the unprecedented speed and volume at which LLMs can produce convincing content creates conditions for misinformation spread on a scale previously impossible, especially among non-expert publics who lack the epistemic resources to detect AI-generated falsehoods. The authors emphasize that the inability to reliably detect AI-produced text compounds this threat, undermining public trust in scientific institutions and potentially influencing health-related behaviours and policy decisions. The work demonstrates how LLM-mediated scientific communication poses distinct risks to knowledge integrity and public understanding, requiring urgent development of detection mechanisms, governance frameworks, and media literacy initiatives to protect audiences from AI-driven epistemic harm.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Bryant, Rebecca. 2024. “Implementing an AI Reference Chatbot at the University of Calgary Library.” ''Hanging Together'', December 12. https://hangingtogether.org/implementing-an-ai-reference-chatbot-at-the-university-of-calgary-library/&lt;nowiki/&gt;.'''
&lt;/div&gt;

Bryant (2024) details the development and implementation of &quot;T-Rex,&quot; an AI-powered reference chatbot at the University of Calgary Library, based on a webinar hosted by the OCLC Research Library Partnership. While the library had offered live chat services since the early 2010s, the COVID-19 pandemic caused a massive surge in demand, peaking at over 3,000 inquiries in a single month. To alleviate this strain, the library analyzed past chat transcripts and determined that 12–14% of inquiries were simple, directional questions suitable for automation. To prevent scope creep during the initial training phase, the development team focused on a core set of fifty common questions. Through continuous refinement, the chatbot has since expanded to encompass over 1,000 custom responses, though its effectiveness remains limited by the availability of existing library webpages or FAQs to draw from. Bryant concludes by summarizing the Calgary team's key insights for institutions developing similar tools: developers must anticipate out-of-scope or non-library questions, recognize that users prefer direct answers over links to webpages, program creative responses for off-topic queries, and prepare for user resistance or non-adoption.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Hara, Noriko, Eugene Kim, Shohana Akter, and Kunihiro Miyazaki. 2025. “Exploring the Dynamics of Interaction About Generative Artificial Intelligence Between Experts and the Public on Social Media.” ''Journal of Science Communication'' 24 (1): A02. https://doi.org/10.22323/2.24010202&lt;nowiki/&gt;.'''
&lt;/div&gt;

Hara and colleagues conduct an empirical investigation into how experts and the public co-produce knowledge about generative AI on social media, specifically analyzing X (formerly Twitter) discussions. Rather than treating the public as passive consumers of expert knowledge, the authors adopt a Public Engagement with Science (PES) framework that recognizes social media platforms as dynamic arenas where non-experts actively contribute to shaping collective understanding of emerging technologies. Through computational and manual analysis, they identify distinct discussion topics, map the roles that both experts and laypeople play in knowledge production, and examine how engagement metrics correlate with these roles. A critical finding is that the public functions beyond questioners seeking expert guidance, but rather as active knowledge co-producers who share practical insights, challenge claims, and contribute their own perspectives and experiences with GenAI tools. This research demonstrates how AI itself—as a subject of discourse—becomes a site of negotiated meaning-making between differently positioned actors. The work moves beyond traditional one-way dissemination models to reveal the interactive, participatory nature of contemporary science communication, with implications for understanding how diverse audiences collectively construct understanding of transformative technologies and how this co-productive process shapes both public perception and the future development of AI systems.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Jaillant, Lise, Olivia Mitchell, Eric Ewoh-Opu, and Maribel Hidalgo Urbaneja. 2025. “How Can We Improve the Diversity of Archival Collections with AI? Opportunities, Risks, and Solutions.” ''AI &amp; Society'' 40: 4457–4459. https://doi.org/10.1007/s00146-025-02222-z. '''
&lt;/div&gt;

Jaillant et al. draw from interviews with 20 academics and archival professionals to explore how AI technologies can help address the lack of diversity in archival collections. The authors highlight that AI tools can assist in automatically detecting racist or inappropriate language in metadata, search large amounts of historical records, and uncover new insights within archival records. However, the authors argue that the deployment of AI should involve close collaboration between librarians, archivists, and developers. The current limited collaboration between developers and libraries limits the ethical and inclusive application of AI in archival collections, especially those with sensitive historical materials. The interviewees also warned against the loss of historical context when using AI, the perpetuation of archival biases, and the loss of control when AI tools are designed and governed by tech companies. To conclude, the authors recommend investing in interdisciplinary AI training programs for archivists, educating AI developers about the unique needs of archives so they can create more relevant solutions, and creating professional guidelines about the best practices for AI use to address the lack of diversity in archival collections.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Peters, Uwe, and Benjamin Chin-Yee. 2025. “Generalization Bias in Large Language Model Summarization of Scientific Research.” ''Royal Society Open Science'' 12 (4): 241776. https://doi.org/10.1098/rsos.241776&lt;nowiki/&gt;.'''
&lt;/div&gt;

Peters and Chin-Yee provide rigorous, large-scale empirical evidence of a systematic and consequential distortion in LLM-generated scientific summaries: the tendency toward overgeneralization. Testing ten prominent LLMs—including ChatGPT-4o, ChatGPT-4.5, DeepSeek, LLaMA 3.3 70B, and Claude 3.7 Sonnet—on 4,900 summaries of scientific abstracts and full-length articles, the authors demonstrate that even when explicitly prompted for accuracy, most LLMs consistently produce conclusions broader and more definitive than those warranted by the original research. Critically, they identify three specific mechanisms of overgeneralization: the use of generic statements that obscure quantification, the shift from past to present tense (which expands scope), and the omission of qualifiers and limitations. The findings are stark: LLM-generated summaries were nearly five times more likely than human-authored summaries to contain broad generalizations (odds ratio = 4.85, 95% CI [3.06, 7.70], p &lt; 0.001), with newer models performing worse than earlier ones. This research is foundational for understanding how AI-mediated knowledge communication systematically distorts scientific findings at scale, regardless of user expertise or intent. The work demonstrates a concrete mechanism through which LLM intermediation can alter the epistemic content of research, with particular implications for medical and clinical contexts where overgeneralized conclusions can directly influence policy and patient care. The authors propose mitigation strategies including temperature adjustment and systematic benchmarking, but their findings underscore the profound challenge of ensuring faithful knowledge transmission through AI systems.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''da Silva Cardoso, Heike, and Vitor Rocio. 2025. “Enhancing Digital Libraries Through NLP and Recommender Systems: Current Trends and Future Prospects with Large Language Models.” In ''Technology and Innovation in Learning, Teaching and Education: TECH-EDU 2024'', edited by Arsénio Reis, José P. Cravino, Leontios Hadjileontiadis, Paulo Martins, Sofia B. Dias, Sofia Hadjileontiadou, and Tassos Mikropoulos, 69–79. C''ommunications in Computer and Information Science'' 2480. Cham: Springer. https://doi.org/10.1007/978-3-032-02672-9_5&lt;nowiki/&gt;.'''
&lt;/div&gt;

da Silva Cardoso and Rocio propose a practical framework for integrating Natural Language Processing and Large Language Models into academic digital libraries to address the information overload facing researchers, students, and faculty. Recognizing that traditional search methods have become insufficient in the face of exponential publication growth, the authors advocate for AI-driven recommender systems capable of delivering precise, relevant, and personalized literature recommendations. Their contribution centres on an audience-aware design philosophy that positions librarians as essential partners in system development. Rather than treating AI as a purely algorithmic solution, the authors emphasize that librarians' direct interactions with users provide irreplaceable insight into the nuanced and context-dependent needs of diverse academic communities. This human-in-the-loop approach represents a noteworthy methodological stance: AI functions not as a replacement for human expertise but as a tool to augment librarian knowledge and enhance the responsiveness of knowledge discovery systems. The work is particularly salient for understanding how contemporary LLM-based systems can be designed to serve scholarly audiences more effectively while maintaining the institutional wisdom and user-centred perspective that librarians bring to information work.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Taneja, Ankit Kumar, and Chandra Tripathi. 2020. “AI-Powered Recommender Systems: Personalization and Bias.” ''Turkish Journal of Computer and Mathematics Education (TURCOMAT)'' 11 (1): 1090–1094. https://doi.org/10.61841/turcomat.v11i1.14406&lt;nowiki/&gt;.'''
&lt;/div&gt;

Though published before the generative AI era, Taneja and Tripathi's analysis of AI-powered recommender systems remains foundational to understanding algorithmic bias in information discovery. The authors examine the structural tensions inherent in personalization algorithms—systems designed to enhance user experience by tailoring content suggestions yet simultaneously capable of constructing &quot;filter bubbles&quot; and &quot;echo chambers&quot; around users. By continuously recommending content similar to previous engagement, these algorithms systematically exclude novel, dissenting, or interdisciplinary perspectives, undermining serendipitous discovery essential to genuine scholarly inquiry. Critically, the authors frame algorithmic bias not as a technical glitch but as a structural risk embedded within the information architectures that guide knowledge-seekers, and thus they expose how algorithmic personalization—a feature predating generative AI—already demonstrated the capacity to narrow intellectual diversity and reinforce pre-existing beliefs. This pre-GenAI work provides historical context for understanding how contemporary AI systems have intensified these risks, making it useful for evaluating the ethical imperatives of designing systems that promote intellectual openness rather than epistemic closure.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''de Winter, J. 2024. “Can ChatGPT Be Used to Predict Citation Counts, Readership, and Social Media Interaction? An Exploration Among 2222 Scientific Abstracts.” ''Scientometrics'' 129: 2469–2487. https://doi.org/10.1007/s11192-024-04939-y&lt;nowiki/&gt;.'''
&lt;/div&gt;

De Winter’s study contrasts conventional scientometrics, testing whether a large language model can predict an article’s citation count and altmetric scores (whilst noting these may be unreliable assessors of actual scientific impact) by rating its abstract across “semantically diverse” variables. His case study uses ChatGPT-4 to predictively evaluate 2,222 abstracts from articles published in ''PLOS ONE'', monitoring its accuracy by referencing actual citation counts and altmetrics scores. De Winter employs a custom script to prompt OpenAI’s Application Programming Interface (API) to score each abstract on a scale of zero to one hundred across thirty positive variables and their thirty antonyms, which he then organizes under five categories (e.g., “Quality and Reliability”). As Chat-GPT 4 only produced consistent results at the population level, it was run three additional times to determine averages and bolster reliability of individual scores. This language-based evaluation of article abstracts revealed that ChatGPT-4’s scores better correlate with altmetrics and citation counts than conventional readability scores do. Furthermore, “Novel and Engaging” articles were most likely to be cited, whilst “Accessible and Understandable” articles scored highest in altmetrics.

{{Navigation|previous=AI and Social|next=Complete Alphabetical List of References}}

{{BookCat}}</text>
      <sha1>dr5k9rwwlzb9b9zxjj6p72sud0cylia</sha1>
    </revision>
    <revision>
      <id>4656131</id>
      <parentid>4656126</parentid>
      <timestamp>2026-08-02T22:35:00Z</timestamp>
      <contributor>
        <username>CorreiaA</username>
        <id>3614427</id>
      </contributor>
      <minor />
      <origin>4656131</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="112390" sha1="5ulwj9yx4bfi0tlgt1vut93adzf53f1" xml:space="preserve">== Research Methods and Practices ==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Arnett, Catherine, Eliot Jones, Ivan P. Yamshchikov, and Pierre-Carl Langlais. 2024. “Toxicity of the Commons: Curating Open-Source Pre-Training Data.” Preprint, ''arXiv'', October 29. https://doi.org/10.48550/arXiv.2410.22587.'''
&lt;/div&gt;

Open-source pretraining data is increasingly treated as a shared resource for building “open” language models, yet it can embed and reproduce harmful speech patterns at scale. Arnett, Jones, Yamshchikov, and Langlais argue that reducing toxic model behaviour requires intervening upstream in data, and they focus specifically on the distinctive constraints of public-domain corpora (including historical documents and OCR-derived text) where standard web-text toxicity filters can be impractical or ill-suited. They propose a fully open-source curation pipeline designed for these conditions and present three concrete contributions: (1) ToxicCommons, a custom-labelled dataset organized across five toxicity dimensions (racial/origin-based, gender/sex-based, religious, ability-based discrimination, and violence); (2) Celadon, a classifier trained on that dataset to detect toxic content more efficiently at scale in open data; and (3) a “balanced” filtration strategy that explicitly trades off safety filtering against retaining sufficient training material. The paper’s core claim is that open-data model development needs domain-attuned, auditable curation methods paired with task-specific classifiers, so that openness in data does not automatically translate into avoidable harms in downstream model outputs.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Bail, Christopher A. “Can Generative Artiﬁcial Intelligence Improve Social Science?” https://www.semanticscholar.org/paper/Can-Generative-Artiﬁcial-Intelligence-Improve-Bail/6206cc77bb3a3c0b6b9fce1ad68a8b1786a56941&lt;nowiki/&gt;.'''
&lt;/div&gt;

Bail (2023) provides a critical evaluation of how Generative Artificial Intelligence (AI), particularly Large Language Models (LLMs), might fundamentally transform computational social science. Moving beyond superficial administrative use cases, Bail examines the potential of LLMs to simulate complex human behaviours. He suggests that Generative AI could revolutionize agent-based modelling by replacing simplistic, rule-bound agents with dynamic, memory-equipped &quot;silicon samples&quot; capable of emergent group behaviours. While acknowledging the utility of AI for automated content analysis and expanding programming accessibility, Bail rigorously details the methodological and ethical perils of these largely opaque systems. He warns that the proprietary fine-tuning of commercial LLMs introduces severe demographic biases—often skewing toward highly educated, liberal perspectives—which threatens the external validity of AI-assisted research. Furthermore, Bail highlights the &quot;Stack Overflow Problem,&quot; cautioning that the unchecked proliferation of AI-generated &quot;junk science&quot; could contaminate future training data and degrade the broader scientific ecosystem. Ultimately, Bail argues that social scientists must not remain passive &quot;end-users&quot; of corporate AI. Instead, they must actively collaborate with computer scientists to reverse-engineer the &quot;social sense&quot; into AI models, ensuring the development of open-source, reproducible infrastructures that genuinely advance the study of human behaviour.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Bakharia, Aneesha, Antonette Shibani, Lisa-Angelique Lim, Trish McCluskey, and Simon Buckingham Shum. 2025. “From Transcripts to Themes: A Trustworthy Workflow for Qualitative Analysis Using Large Language Models.” In ''Joint Proceedings of LAK 2025 Workshops, co-located with the 15th International Conference on Learning Analytics and Knowledge (LAK 2025)''. Dublin, Ireland: CEUR-WS.org. https://ceur-ws.org/Vol-3995/LLMQUAL_paper1.pdf.'''
&lt;/div&gt;

Bakharia et al. explore the use of AI in qualitative, rather than quantitative, research in education. The authors define “minimum requirements that an LLM-supported qualitative analysis workflow must satisfy” and present a “LLM-based workflow that derives an initial set of themes” from text data that is “transferable to other LA [learning analytics] contexts performing qualitative analysis of open-ended text.” The authors define two requirements for “LLM-generated inductive coding”: first, it must verify “coded textual extracts… against source data” to make sure the quotes are accurate (i.e., verbatim and not hallucinated) and verify those extracts “are meaningfully classified under the assigned code.” Second, in the interest of transparency, it must “explain that rationale for each code” and “trace every code, whatever level of abstraction, back to its source data.” The article outlines and describes the proposed workflow in detail, including its being built in Python with a Jupyter notebook and Flask application. While they acknowledge challenges and problems in their research (e.g., LLM bias, the lack of comparable human analysis, the risk of alienating the human quality of qualitative research), Bakharia et al. ultimately advocate their approach as one that “improves transparency, verifiability, and interpretability, while addressing limitations of previous methods and enhancing researcher processes in qualitative thematic analysis&quot; (9). By adapting their minimum requirements and workflow, the authors argue, researchers can engage more effectively in LLM-driven qualitative research.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Dennstädt, Fabio, Cedric Sivert Möller, Tim Fellerhoff, Felix Busch, Oke Gerke, André Karch, and Oliver Krause. 2024. “Title and Abstract Screening for Literature Reviews Using Large Language Models: An Exploratory Study in the Biomedical Domain.” ''Systematic Reviews'' 13 (1): 158. https://doi.org/10.1186/s13643-024-02575-4&lt;nowiki/&gt;.'''
&lt;/div&gt;

Dennstädt et al. perform a study in which they attempt to determine the viability of using LLMs to automate scholarly literature surveys. The researchers developed a method for using LLMs to perform the title and abstract screenings of a systematic literature review method and applied that method with four LLMs across eleven datasets in biomedical literature. A key advantage of implementing LLMs in this process is that it escapes the need to train the machine via pre-selection. Researchers have developed automated and semi-automated processes for systematic literature reviews in the past, but this requires a human agent to provide training data or a corpus of example texts that tell the system what to look for. LLMs do not require this step. Instead, the researchers used a Python script that prompts the LLM “to evaluate the relevance of a scientific publication for inclusion into an SLR,” providing the LLM with both abstract and title, request for a numbered score indicating the relevance of the publication, and a numerical threshold that defines whether a score makes the given publication relevant. The authors characterize the results of the study as “promising” but also “far from perfect,” identifying that such applications could be helpful to researchers and are widely applicable without special training for data or user, even if “fully automated systems… still fail to differentiate… near the level of human evaluation.” The authors conclude that more research into the use of LLMs to automate systematic literature reviews is needed, but it seems very likely that scholars will employ LLMs into this integral research task with greater frequency in the future. How well LLMs will continue to perform in this task is unclear, especially in new research, and Dennstädt et al. clearly state, “we cannot answer the question of to what extent LLMs should be used for conducting literature reviews and for doing research.”

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Montague-Hellen, Beth. 2024. “Empowering Knowledge through AI: Open Scholarship Proactively Supporting Well Trained Generative AI.” ''Insights'' 37 (1). https://doi.org/10.1629/uksg.649.'''
&lt;/div&gt;

Generative AI is becoming a dominant interface for finding, summarizing, and producing academic information, with consequences for what counts as authoritative knowledge online. Montague-Hellen argues that, rather than focusing primarily on misuse, job displacement, or defensive copyright disputes, scholarly communications actors should actively encourage the inclusion of scholarly literature in generative AI training data to improve reliability and ensure research is represented in emerging discovery platforms. The article develops two main pathways for doing this: making scholarly outputs more machine-actionable and “crawlable” (especially through better linkage, metadata, and structured HTML rather than PDF-only dissemination) and making permissions unambiguous by explicitly addressing AI training in licences and related signals. It foregrounds “garbage in, garbage out” to claim that while libraries and publishers cannot remove low-quality web content from training corpora, they can tilt the balance by lowering friction for high-quality, curated research to be ingested legally. Montague-Hellen also highlights unresolved tensions around attribution and consent under common Creative Commons licences, suggesting that clearer, more specific permission frameworks (or new licensing patterns) may be needed to distinguish human reading from machine training and to communicate “enthusiastic consent” where desired.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Mugaanyi, Joseph, Christoph Lehner, and Lia M. Bally. 2024. “Evaluation of Large Language Model Performance and Reliability for Citation Generation Across Scientific Disciplines.” ''Journal of Medical Internet Research'' 26: e52935. https://doi.org/10.2196/52935&lt;nowiki/&gt;.'''
&lt;/div&gt;

Mugaanyi, Lehner, and Bally perform a study aimed at gauging the accuracy and reliability of citations generated by ChatGPT (GPT 3.5) in both the natural sciences and humanities. The authors emphasize that “Citations and references serve as the backbone of scholarly communication, providing the necessary context, evidence, and credit to prior works… ensuring the integrity of the research process.” With this in mind, the article frames the related study as aiding researchers in determining whether LLMs are viable as writing assistants in scholarly writing. In short, if an LLM cannot be relied upon to accurately cite and reference sources, it poses a risk to the integrity of research when incorporated into scholarly writing. The study found that ChatGPT hallucinated over a quarter of its references, with a slightly higher margin in the natural sciences. Furthermore, not all of those citations that did exist were accurate, and the LLM hallucinated DOIs for nearly 90% of the references it cited, real or otherwise, in the humanities. The issue, as the authors describe it, is that “in the current iteration of LLMs, since the training is geared toward generalization and the models are probabilistic, they tend to interpolate and fill in the missing information with synthetic text.” The authors conclude that, while domain-specific models may improve performance and reliability, in its current, generic form, researchers need to contemplate whether the strengths of ChatGPT’s reference generation justify its demonstrable limitations and “the importance of robust validation processes to ensure the accuracy and reliability of generated content.” 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Schroeder, Hope, Marianne Aubin Le Quéré, Casey Randazzo, David Mimno, and Sarita Schoenebeck. 2024. “Large Language Models in Qualitative Research: Uses, Tensions, and Intentions.” Preprint, ''arXiv'', October 9. https://arxiv.org/abs/2410.07362&lt;nowiki/&gt;.'''
&lt;/div&gt;

Schroder et al. perform interviews with 20 qualitative researchers in human computer interaction (HCI) and qualitative research to gauge how researchers are actually using LLMs and concerns over the incorporation of LLMs at different stages of research; the authors also provide a survey of the rise of LLMs and flag potential concerns, using both interviews and survey as a launchpad to outline suggestions and recommendations for researchers in the field contemplating the use of LLMs in their research. The authors are concerned that “the speed of LLM development has outpaced guidance on their ethical use” and “the HCI community is contending with the need for developed policies that tackle how to use AI ethically in research.” The most prominent concerns that the article raises relate to “ethics, unequal adoption of new technologies, model bias, and performance” as well as “concerns regarding participant privacy,” but there is also a larger issue within the field of HCI that “LLMs may lend the impression that qualitative inquiry can be automated, and their integration into Quantitative Data Analysis (QDA) software may increasingly impose positivist approaches that conflict with interpretivist traditions.” Key findings from the interviews are that most researchers are open to responsible use of LLMs but have concerns about established guidelines and norms for its implementation. Additionally, many are already using LLMs “to generate recruitment materials,” “speed up qualitative coding,” and “for ideation and feedback,” even as they acknowledge tensions between the qualitative nature of their work and the prospect of automation. The most significant recommendations that Schroder et al. make include updating consent forms, using dedicated tools rather than defaulting to Chat-GPT, and implementing design decisions specifically for LLM-incorporating methodologies that reconsider “participant privacy,” LLM’s “intentional use,” “transparency and validation,” “researcher context,” “deep engagement with data” despite this automation, and ways “to consider participant perspectives and interests” given “the variable performance LLMs have across contexts, knowledge domains, cultures, and languages.” The authors hope that incorporating these considerations will “empower qualitative researchers to leverage LLMs confidently, and even creatively, for their work.” 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Tumadóttir, Anna. 2024. “Questions for Consideration on AI &amp; the Commons.” ''Creative Commons'', July 24. https://creativecommons.org/2024/07/24/preferencesignals/.'''
&lt;/div&gt;

Tumadóttir talks about CC, license, tools, and policy and discusses the way to foster a healthy commons environment in the digital era. She points out how the introduction of the CC license enhanced Creative Commons by giving the creators choice over usage of their works. However, it is now a question if the same healthy commons can be maintained today because of rapid technological development. Preference signals for AI is a notion to give an agent (creator, rights holder, entity of some kind) more flexibility on how they want their work to be used for AI model training. However, the choice is still binary which is offering all or nothing. After consultations, it is found that people want more control over their work and if not, they might not share their work at all. Therefore, it is important to identify the right type of preference signals for it to be useful to benefit the public interest. During this process, we need to keep in mind its effect and variation on cultural heritage, different education sectors, and regions. Moreover, to make the preference signals effective, we need to examine its structure as well as whether legal enforcement is necessary.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Yue, Yongjie, Maosong Zheng, Jiahui Liu, Zhimin Wang, and Chenhui Mao. 2025. “A Practical Guide and Assessment on Using ChatGPT to Conduct Grounded Theory Studies: Step-by-Step Reporting of the Data Analysis Process.” ''Journal of Medical Internet Research'' 27: e70122. https://doi.org/10.2196/70122&lt;nowiki/&gt;.'''
&lt;/div&gt;

Yue et al. employ a study that entailed researchers using either manual coding or coding assisted by ChatGPT to perform data analysis on a 40,000 word dataset made up of interviews with 8 players of Listen and Play in Jianghu, a Chinese MMORPG designed for the blind. The study’s aim was to “provide detailed guidelines for using ChatGPT in grounded theory within the Chinese context,” “evaluate the effectiveness of ChatGPT coding” in this context, and “explore the broader implications and future directions of ChatGPT in qualitative research.” The article goes into great detail as to the process for generating open code with ChatGPT. The results of the study show that, although manual coding performed slightly better than ChatGPT-assisted coding, the “difference was not statistically significant” in its production of nodes and reference points. However, during axial coding, the categories and subcategories generated through these respective processes was significantly different, with only half of the categories semantically matching between manual and ChatGPT-assisted methods. The authors conclude that, while ChatGPT 4-Turbo “enhanced the diversity and efficiency of coding... it struggled with depth, context, subtle nuances, connections, and coding organization.” Nevertheless Yue et al. see great potential in the application of GenAI-assisted coding in grounded theory, especially as the technology develops. 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Zhu, Wenhao, Hongyi Liu, Qingxiu Dong, Jingjing Xu, Shujian Huang, Lingpeng Kong, Jiajun Chen, and Lei Li. 2023. “Multilingual Machine Translation with Large Language Models: Empirical Results and Analysis.” Preprint, ''arXiv'', April 10. https://arxiv.org/abs/2304.04675&lt;nowiki/&gt;.'''
&lt;/div&gt;

Zhu et al. perform an empirical study that tests the multilingual translation performance of eight popular LLMs on 102 languages. As the authors explain, this is a particularly difficult task as it requires “semantic alignment between languages.” While LLMs tend to perform surprisingly well at translation, “it is also unclear [sic] how LLM acquires translation ability and which factors affect LLM’s translation ability.” This study in multilingual machine translation (MMT) therefore seeks to answer two questions: how do LLMs perform MMT over massive languages and what factors affect their performance?

The results of the study suggest that GPT-4 generally outperforms its competitors but still falls short of Google Translate in some tests. Two key takeaways from this study are that “exemplars in the tail of the prompt have larger influence on an LLM’s behaviour,” meaning that the order in which exemplars are given within a prompt matter, and that cross-lingual translation pairs are particularly helpful exemplars to LLMs. The authors ultimately conclude that an “LLM can acquire translation ability in a resource-efficient way, which indicates [a] promising future of LLM in multilingual machine translation” as the technology evolves.

''NB: As this research was conducted prior to Google’s implementation of GenAI/LLMs into Google Translate in 2024, it sometimes uses Google Translate as a baseline/comparison point for LLM-powered translation that can be confusing without that context.''

== Forms of Research Output ==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Bozkurt, Aras. 2024. “GenAI et al.: Cocreation, Authorship, Ownership, Academic Ethics and Integrity in a Time of Generative AI.” ''Open Praxis'' 16 (1): 1–10. https://doi.org/10.55982/openpraxis.16.1.654&lt;nowiki/&gt;.'''
&lt;/div&gt;

Bozkurt’s essay seeks “to undertake a critical examination of the use of generative AI in academic contexts… examining its implications and exploring the nuances of its integration.” He begins with an assertion of technological determinism, stating “This technological shift… is not just a transient trend but a symbol of the inescapable change… marking the onset of an AI-dominated age and initiating profound and inevitable shifts in our academic and educational paradigms.” The author makes the argument that the advent of AI “requires us to critically reconsider concepts such as cocreation, ownership, and authorship in academic writing processes.” For instance, in exploring the concept of ownership, he briefly notes the ethical concerns of whether those who created the content upon which AI was trained might claim ownership of AI-generated content and explores the notions of AI or even its programmers acting as a co-author. Bozkurt himself takes the explicit stance that GenAI ought not be credited as a co-author. The paper also provides suggestions related to the ethics of AI use and transparency: “In some cases, merely reporting… is inadequate. A more nuanced approach involves providing multilayered statements acknowledging and benchmarking the use of [GenAI], specifying where, when, in which sections, and for what purposes it is employed.” Bozkurt reiterates that responsibility ultimately belongs to the human author, and provides the aiTARAS (Academic Integrity and Transparency in AI-assisted Research and Specification) Framework for this purpose. Bozkurt ends his essay by identifying further problems beyond the scope of the article, including “reimagining of assessment and evaluation,” our overfocus on ChatGPT and English language in this field of study, and the inaccuracy of AI detection software.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Colbert-Lewis, Danielle, Lawrence Maminta, Kelly McElroy, Graeme Slaght, and Mark Swartz. 2024. “The Citation Economy as a Site of Extraction for Surveillance Publishing.” ''Canadian Journal of Academic Librarianship'' 10 (December): 1–22. https://doi.org/10.33137/cjal-rcbu.v10.43293.'''
&lt;/div&gt;

Colbert-Lewis et al. (2024) examine the extractive nature of the modern &quot;citation economy,&quot; arguing that academic publishing has evolved into a powerful mechanism for surveillance and data commodification. The authors detail how a consolidated group of dominant publishers capture surplus value from the academic lifecycle by extracting free scholarly labour, research data, and personal information. Crucially, these corporations are transitioning from traditional information vendors into technology-driven data brokers. The extracted data is reinvested into proprietary analytics products that are then sold back to universities to evaluate and surveil faculty performance, relying on opaque metrics that threaten academic freedom. Furthermore, the authors highlight the severe ethical compromises inherent in this system, noting that academics inadvertently fuel data infrastructures that these same parent companies sell to external industries, including law enforcement and advertising. To combat the rise of &quot;surveillance publishing,&quot; the article concludes with actionable recommendations for scholars and librarians to resist exploitative practices and build ethical infrastructures, alongside a supplementary mini-zine designed to raise awareness about the hidden costs of participating in the citation economy.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Frangou, Sophia, Umberto Volpe, and Andrea Fiorillo. 2025. “AI in scientific writing and publishing: A call for critical engagement.” ''European Psychiatry'' 68 (1): e98. https://doi.org/10.1192/j.eurpsy.2025.10061&lt;nowiki/&gt;.'''
&lt;/div&gt;

Frangou, Volpe, and Fiorillo provide a succinct summary of the benefits of implementing AI in scientific writing and publishing, before turning to the challenges and risks posed toward the use of such technology. Finally, they end by posing ethical frameworks for the use of AI in both publishing and writing. In publishing, the authors identify tools that can aid in tasks ranging from copyediting to finding reviewers and claim that for both “high-volume publications” and “resource-constrained journals… AI can serve as a force multiplier, expanding what editorial teams can accomplish without compromising the centrality of human discretion and responsibility.” In writing, the article notes that “AI-powered applications offer a suite of tools that, when used judiciously, can enhance the quality, efficiency, and inclusivity of the scholarly communication process,” placing such tools along the trajectory of preexisting aids like EndNote and Zotero, which have also now incorporated AI. Frangou, Volpe, and Fiorillo argue that AI can help scholars identify relevant literature they might otherwise have trouble finding, reduce the linguistic bias encountered by scholars for whom English is not their first language, and aid scholars in navigating the publishing landscape so their work can find the best possible fit. Finally, the authors acknowledge the epistemic and ethical risks of AI: inconsistency and irreproducibility, transparency, informed consent, and data privacy are all core concerns. Key components in the article’s ethical frameworks for publishers and authors include transparency and disclosure, human accountability, and training and skill development. The authors hope that “these principles articulate a shared responsibility for shaping the role of AI in scientific publishing” and AI’s “adoption reinforces the foundational values that give scientific communication its trustworthiness and legitimacy.”

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Graßhoff, Gerd. 2024. “AI-Reporter: A Path to a New Genre of Scientific Communication.” Preprint, ''arXiv'', July 8. https://arxiv.org/abs/2507.05903. '''
&lt;/div&gt;

Graßhoff introduces a new tool, the AI-Reporter, that aims “to fundamentally expand scientific communication for the new era…”; according to Graßhoff, the AI-Reporter “creates a sustainable, referenceable, and expandable knowledge base that captures not just content but the living essence of scientific discourse.” In short, Graßhoff proposes a tool that will adapt a scientific presentation into a “public-ready chapter” in about three minutes with “only the author’s consent.” The majority of the article is dedicated to a tech-oriented breakdown of the methodology and workflow of the AI-Reporter, namely the semantic analysis and translation of a recorded slide presentation—consisting of the presentation as a PDF, video recording, and basic metadata—into a publication-ready chapter. Graßhoff’s tool is an attempt to solve what he identifies as a core problem of modern scholarly communication, namely that “knowledge is increasingly presented in dynamic, multimodal formats” that are ultimately ephemeral and content is often lost (14). He aims to refine this tool to enable real-time processing, multilingual support, interactive multimedia components, “optimization for academic disciplines,” and more to this project. He advocates the AI-Reporter as nothing less than “a vision for the future of scientific communication.”

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Jiang, Jialei. 2024. “When generative artificial intelligence meets multimodal composition: Rethinking the composition process through an AI-assisted design project.” ''Computers and Composition'' 74: 102883. DOI: https://doi.org/10.1016/j.compcom.2024.102883&lt;nowiki/&gt;.'''
&lt;/div&gt;

Jiang conducts a study in which GenAI is integrated into students’ composition of multimodal texts, then interviewed on their experience. Jiang’s states her aim as follows: “Through examining writing students use of GenAI tools in multimodal composition, this study seeks to unravel how GenAi technologies influence students’ design choices, problem-solving approaches, and the overall composition process.” In particular, Jiang is interested in “potential opportunities and challenges of incorporating GenAI into students’ multimodal composition process.” Jiang frames the article within composition and writing studies and the theory behind multimodal composition. She builds upon recent pedagogical best practices put forward by Burriss and Leander (2024) that “call upon teachers and educators to engage in the development of an emergent pedagogy of critical AI that “teach[es] about/with AI in emergent, flexible, and speculative ways.” The results of the study emphasize that, while GenAI can streamline workflow and provide examples from which students can build using their own creativity, there were clear limitations to the technology. Of course, students’ realization of these limitations is a success of the course’s pedagogy. The article also provides three case studies of the student compositions as exemplars of the outcome. Jiang concludes with a recommendation “that researchers and educators engage in meaningful dialogues with students about their uses of GenAI during composition practices.” She quotes her own earlier work (Jiang et al. 2024), where she writes that to keep AI out of the classroom “is not only idealistic and impossible... it is actually completely disengaged from the realities of the changing technological landscape students are already facing.”

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Mehlenbacher, Brad, Ana Patricia Balbon, and Ashley Rose Mehlenbacher. 2024. “Synthetic Genres: Expert Genres, Non-Specialist Audiences, and Misinformation in the Artificial Intelligence Age.” ''Journal of Technical Writing and Communication'', January 31. https://doi.org/10.1177/00472816231226249.'''
&lt;/div&gt;

Genre theorists Mehlenbacher et al. examine which AI-generated texts are “good enough” to pass as “bona fide” (already a “very good” standard). They argue AI-generated text produces misinformation, pushes apart definitions of “information” and “knowledge,” and necessitates rhetorical understanding. The authors therefore believe “synthetic genres” will emerge, departing in situation, form, and even “the very concept of genre users” based on recursive and “poisoned” outputs. In reviewing literature, the authors spotlight AI-generated disinformation’s suasive (instead of propagandistic or accurate) potential, and argue that AI-generated text can be suasive by appearing both “timely” and “appropriate.” However, this “fraudoscientific” text can never be truly “timely” or “appropriate,” as it is always constrained in past work, and only responds to prompts, not situations. Despite this, AI-generated text generated on specialist subjects can still be effectively suasive—and even when identified as AI—because its authority is difficult to challenge. Mehlenbacher et al. therefore conduct two studies of AI-generated outputs, focusing on how they may be deceptive or detected. They first prompted GPT-3 to emulate rhetorical research abstracts by generating a range of definitions alongside text to emulate research processes. Next, they conducted a genre analysis, generating text on controversial topics and prioritizing suasiveness over ability to pass a theoretical “Genre Turing Test.” Based on their results, Mehlenbacher et al. suggest AI-generated text should be cross examined with specialist texts to identify where they need additional development, presenting a valuable teaching opportunity which supports “a powerful way to introduce the epistemic functions of writing.” Non-specialists should also develop tools to identify the source and quality of content, including diverse genre perspectives. The authors conclude by arguing genre scholars should further consider AI-generated texts and emphasizing the importance of genre users. This is because “genre must be understood in a rhetorical context,” while “synthetic genres” can only act as “statistical simulacrum.”

== Teaching and Pedagogy ==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Adewumi, Tosin, Lama Alkhaled, Christopher Buck, Sergio Hernandez, Sofia Brilioth, Memoona Kekung, Yasmin Ragimov, and Emily Barney. 2023. “ProCoT: Stimulating Critical Thinking and Writing of Students through Engagement with Large Language Models (LLMs).” Preprint, ''arXiv'', December 15. https://doi.org/10.48550/arXiv.2312.09801&lt;nowiki/&gt;.'''
&lt;/div&gt;

Adewumi et al.'s Probing Chain-of-Thought (ProCoT) methodology represents a pedagogical approach that transforms LLM interaction from potential academic dishonesty into an active learning process centred on critical evaluation and evidence-based reasoning. ProCoT requires students to generate initial outputs using LLMs, then systematically affirm or refute each claim using peer-reviewed references, effectively making the AI output a provisional hypothesis to be tested rather than a final answer to be submitted. This approach directly addresses the section's themes of process transparency (the method makes visible each stage of knowledge construction, from initial AI generation through source verification to synthesis) and ethical reflection (students must grapple with AI limitations including hallucination, bias, and lack of disciplinary nuance). The authors' finding that student outputs using ProCoT were significantly more concise than LLM-generated text (208 vs. 391 words on average) while demonstrating enhanced critical thinking suggests that the method trains students to distill and synthesize rather than accept verbose AI output uncritically. ProCoT leverages AI's epistemological weaknesses as pedagogical strengths—the fact that ChatGPT cannot reliably cite sources becomes an opportunity for students to develop information literacy by finding and evaluating primary literature. The method's anti-cheating design is secondary to its pedagogical value: by requiring iterative engagement with AI outputs and scholarly sources, ProCoT embeds the kind of metacognitive reflection (What did the AI get right? What did it miss? How do I know?) that is of significance to pedagogy in the AI era. The authors' evidence from 65 students across disciplines demonstrates feasibility across contexts, emphasizing cross-disciplinary rather than field-specific approaches to AI-entangled pedagogy. 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Berry, David M. 2023. “AI, Ethics, and Digital Humanities.” In ''The Bloomsbury Handbook to the Digital Humanities'', edited by James O’Sullivan, 445–57. Bloomsbury Academic. https://recoveryhub.siue.edu/wp-content/uploads/2024/10/AI-Ethics-and-Digital-Humanities-.pdf&lt;nowiki/&gt;.'''
&lt;/div&gt;

Berry emphasizes that AI’s use in the field of Digital Humanities raises major ethical questions despite it being an apparent evolution of the field’s traditional utilization of technology to augment human research capabilities. Berry outlines this issue by comparing the modern rise of AI to Digital Humanities’ early history, highlighting that digital humanists operated as coders until they began to “'black box' the computational aspects of doing digital humanities,” thus enabling non-programmers to participate. Since AI “automating processes might cover over ethical issues by transferring them into the hashtables of the machine-learning system,” Berry argues uncritical reliance on AI tools by inexpert modern humanists risks the “algorithmization” and imposition of hierarchical, quantitative frameworks upon Digital Humanities studies. He further identifies that the field of Digital Humanities is “on the cusp of a new set of packages that will further democratize access to machine learning,” a noble goal, but one which will bring these issues to the forefront. For this reason, Berry argues a reconsideration of ethics within Digital Humanities is desperately required on both organizational and individual levels.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Brown, Richard. 2023. ''The AI Generation: How Universities Can Prepare Students for the Changing World''. DEMOS and University of London report. https://demos.co.uk/wp-content/uploads/2023/11/The-AI-Generation-2.pdf&lt;nowiki/&gt;.'''
&lt;/div&gt;

Brown argues AI will inevitably and dramatically impact all fields of education, and therefore encourages universities to seize the opportunity to lead these changes instead of merely reacting to them. His voice is echoed by esteemed organizations DEMOS and the University of London, indicating that this shift in the academic environment is already beginning. Brown argues this shift is required due to the developing capacity of AI for automating low-skilled professional tasks, an ability which risks decimating the available number of entry-level graduate positions. As a result, how employers value the workplace skills taught by current curriculums will change drastically, meaning universities must revolutionize their approach to education. Brown provides a blueprint for how universities can adapt to these changes by championing education’s prioritization of “GRASP” (General Relational, Analytic, Social, and Personal) skills as an alternative, advising universities to focus on teaching high-level and tailored skills to students instead of the generic. Universities can do this by practising “active learning” over traditional lecture formats as well as fostering extracurricular and work experience opportunities for their students.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Deng, Ruiqi, Maoli Jiang, Xinlu Yu, Yuyan Lu, and Shasha Liu. 2025. “Does ChatGPT Enhance Student Learning? A Systematic Review and Meta-Analysis of Experimental Studies.” ''Computers &amp; Education'' 227. https://doi.org/10.1016/j.compedu.2024.105224&lt;nowiki/&gt;.'''
&lt;/div&gt;

Deng and colleagues' meta-analysis of 69 experimental studies provides empirical grounding for claims about ChatGPT's pedagogical impact, revealing both opportunities and methodological challenges in assessing AI-enhanced learning. Their finding that ChatGPT interventions improve academic performance, affective-motivational states, and higher-order thinking propensities while reducing mental effort speaks directly to how assessment must shift when AI augments cognition—if mental effort decreases but learning outcomes improve, traditional measures of &quot;effort&quot; or &quot;struggle&quot; as proxies for learning may require recalibration. In their critique of current assessment methodologies the authors demonstrate that most studies evaluate only final outputs (essay quality, test scores) rather than learning processes, missing opportunities to examine how students interact with AI, what metacognitive strategies they develop, and whether AI use builds transferable skills or creates dependency. Deng et al.'s four methodological propositions—using complex project-based assessments that reveal process, evaluating long-term rather than novelty effects, prioritizing objective over self-reported measures of higher-order thinking, and employing adequate statistical power—provide a research agenda for pedagogy–AI scholarship that centres process evidence. Their documentation of disciplinary variation (language education dominates current research) while calling for cross-disciplinary synthesis focuses on avoiding discipline-specific approaches. The meta-analysis also reveals gaps in understanding collaboration (few studies examine peer learning dynamics when AI is present) and metacognition (limited research on whether students develop awareness of their own and AI's knowledge boundaries), highlighting the resulting pedagogical transformations.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Grigoli, L. Renato. 2023. “Ghosts in the Machine.” ''American Historical Association'' 61 (3). https://www.historians.org/wp-content/uploads/2024/07/Perspectives_61N3.pdf&lt;nowiki/&gt;.'''
&lt;/div&gt;

Grigoli dismisses fears of AI generated essays threatening academic integrity by arguing that “if the development of artificial intelligence results in the death of the humanities, then it will be because it will have shown that the emperor has no clothes.” He uses ChatGPT to demonstrate that although AI responses appear competent at a passing glance, they lack valuable substance, simply arranging facts in a way that “tricks the reader into… doing all the analytical work.” Clear critical analysis should be the core component of a successful humanities essay, making well-designed assessments of this field far more reliable than those focused on information retention (like engineering). Therefore, AI is not a real threat, but a valuable pedagogical tool which can demonstrate examples of clean prose and prompt students to critically analyze what constitutes critical analysis. Essentially, if an AI generated answer can pass a test, the real problem was &quot;self-inflicted&quot; by either the examiner or the question itself.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Lee, Daniel, and Edward Palmer. 2025. “Prompt Engineering in Higher Education: A Systematic Review to Help Inform Curricula.” ''International Journal of Educational Technology in Higher Education'' 22: 16. https://doi.org/10.1186/s41239-025-00503-7&lt;nowiki/&gt;.'''
&lt;/div&gt;

Lee and Palmer's systematic review establishes prompt engineering as an emergent pedagogical practice that integrates with longstanding traditions of scholarly inquiry, questioning, and rhetoric. The authors synthesize multiple frameworks (AIPROMT, CLEAR, CRISPE) that codify prompting as a learnable skill involving role specification, context provision, instruction clarity, and iterative refinement—revealing how interaction with LLMs mirrors Socratic dialogue, research question formulation, and the rhetorical tradition of audience awareness. This work positions &quot;prompting as pedagogy&quot; as a reconfiguration of existing scholarly literacies: students learning to prompt effectively must articulate their information needs precisely, anticipate how language shapes output, and iteratively refine queries based on initial results—all core practices in library research, database searching, and scholarly conversation. The authors document how educators are embedding prompt engineering across disciplines, from technical fields where students prompt AI to generate code or solve equations, to humanities contexts where prompting becomes a form of textual analysis (understanding what linguistic patterns trigger particular AI responses reveals implicit biases and training data influences). Their review also identifies ethical dimensions—well-designed prompts can mitigate AI hallucination and bias, while poorly constructed prompts amplify these issues—making prompt literacy a matter of scholarly responsibility. The authors' call for curricula that teach prompting as interdisciplinary competency aligns with how AI entangles with pedagogy across boundaries, reshaping what counts as fundamental scholarly practice in an AI-augmented knowledge environment.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Mai, Dang Thi Thuy, Cuong Van Da, and Nguyen Van Hanh. 2024. “The Use of ChatGPT in Teaching and Learning: A Systematic Review through SWOT Analysis Approach.” ''Frontiers in Education'' 9: 1328769. https://doi.org/10.3389/feduc.2024.1328769&lt;nowiki/&gt;.'''
&lt;/div&gt;

Mai and colleagues' systematic SWOT analysis of 51 studies on ChatGPT in education, organized through Biggs' 3P model (Presage-Process-Product), offers comprehensive mapping of how generative AI enters and transforms pedagogical systems at multiple scales—from individual learner characteristics (Presage) through interactive teaching-learning processes (Process) to learning outcomes and assessment products (Product). This multilevel framework reveals that ChatGPT's pedagogical impact cannot be isolated to single moments of use but ripples across entire learning ecologies: at the Presage level, ChatGPT shifts what prior knowledge students need (familiarity with prompting interfaces) and what instructor competencies are required (ability to design AI-aware assignments); at the Process level, it transforms interaction patterns from teacher–student and student–student to include human–AI dialogue that may enhance personalized scaffolding but risks reducing peer collaboration; at the Product level, it necessitates fundamental assessment redesign because traditional evaluation instruments (timed essays, closed-book exams) lose validity when AI can generate competent responses. The authors' characterization of ChatGPT as simultaneously &quot;friend&quot; (enabling personalized learning, reducing educator workload, providing instant feedback) and &quot;foe&quot; (enabling plagiarism, potentially reducing critical thinking, creating over-reliance) mirrors the section's emphasis on entanglement—pedagogy cannot simply embrace or reject AI but must negotiate tensions between efficiency and effort, personalization and depersonalization, augmentation and replacement. Mai et al.'s documentation of how educators are adapting curricula to emphasize creativity and critical thinking (skills less easily automated) while using ChatGPT for routine information provision demonstrates pedagogical evolution toward distinctly human capacities. Their call for assessment reform using complex case studies, portfolios, and process documentation rather than single-sitting exams directly supports the notion of process evidence and metacognition as being central to AI-era pedagogy, positioning assessment not as gatekeeping but as making learning processes transparent and accountable.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Oates, Angela, and Donna Johnson. 2025. “ChatGPT in the Classroom: Evaluating Its Role in Fostering Critical Evaluation Skills.” ''International Journal of Artificial Intelligence in Education'' 35 (4): 1793–1824. https://doi.org/10.1007/s40593-024-00452-8&lt;nowiki/&gt;.'''
&lt;/div&gt;

Oates and Johnson's empirical study of biomedical science master's students offers insight into how AI functions more effectively as object of critical study than as production tool, revealing pedagogical value in making AI outputs subjects for evaluation rather than endpoints of learning. Their finding that students' marks did not improve when submitting AI-generated essays but did improve when critically evaluating AI outputs demonstrates a fundamental pedagogical principle: learning occurs not in consuming AI-generated content but in interrogating it, comparing it against disciplinary standards, identifying its factual errors and rhetorical limitations, and articulating why human-authored scholarship differs. This shifts pedagogy from &quot;use AI to complete tasks&quot; toward &quot;use AI to understand knowledge construction itself&quot;—students learn about evidence evaluation, citation practices, and argumentation by analyzing where ChatGPT succeeds and fails at these scholarly fundamentals. The authors document that ChatGPT demonstrated structural coherence and grammatical accuracy but lacked the disciplinary depth and synthetic insight expected in graduate work, making visible to students the difference between surface-level fluency and genuine expertise. Their emphasis on user interaction as a variable affecting efficacy underscores that pedagogy must address not just whether AI is present but how students are taught to engage it—prompt design, output evaluation, and integration with human research become learnable scholarly practices. Oates and Johnson's conclusion that students preferred writing their own essays despite AI's availability suggests that when pedagogy centres process transparency and critical evaluation rather than output efficiency, students recognize and value the cognitive work that AI cannot replicate, focusing on pedagogy that treats AI as entangled phenomenon requiring simultaneous use and critique.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Pope, Andrew, and Rongqian Ma. 2024. “Exploring Historians’ Critical Use of Generative AI Technologies for History Education.” ''Proceedings of the Association for Information Science and Technology'' 61 (1): 1071–73. https://doi.org/10.1002/pra2.1188&lt;nowiki/&gt;.'''
&lt;/div&gt;

Pope and Ma conducted semi-structured interviews of seven history professors to assess their attitudes toward employing GenAI tools in their teaching. Understanding this stance is important because Pope and Ma believe incoherent and mismatched approaches could inhibit scholarly communication and undermine academic integrity. The survey demonstrated historians had major concerns about GenAI’s development, especially regarding plagiarism. Respondents were particularly divided on whether copying an AI’s work was academic misconduct. However, historians had far fewer concerns about using GenAI to &quot;augment&quot; human abilities or tailor support to students—although senior academics maintained substantially greater reservations. The historians that were interviewed concurred that critiquing AI generated text could improve a student’s media literacy. Pope and Ma’s study suggests that historians consistently doubt the quality of AI generated responses even when willing to employ it.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Tan, Myles Joshua Toledo, and Nicholle Mae Amor Ttan Maravilla. 2024. “Shaping Integrity: Why Generative Artificial Intelligence Does Not Have to Undermine Education.” ''Frontiers in Artificial Intelligence'' 7: 1471224. https://doi.org/10.3389/frai.2024.1471224&lt;nowiki/&gt;.'''
&lt;/div&gt;

Tan and Maravilla provide theoretical grounding for understanding how generative AI can be integrated into pedagogy without compromising academic integrity, arguing that responsible implementation depends on alignment with constructivist learning theory and self-determination theory. The authors position AI not as a threat to authentic learning but as a catalyst that necessitates pedagogical transformation—shifting from transmission models toward environments where students actively construct knowledge using AI as one tool among many. Their framework emphasizes process transparency through explicit discussion of AI's role in knowledge construction and ethical reflection through examining how GAI outputs are generated, what assumptions they embed, and where they may mislead or constrain inquiry. This work addresses pedagogy-as-entanglement by showing how GAI forces educators to make visible the epistemic practices that traditional assessment often left implicit: citation tracing, source evaluation, argument construction, and the iterative nature of scholarly writing. Tan and Maravilla argue that rather than banning AI to preserve integrity, educators should redesign assessment to require demonstration of process—portfolios showing prompt refinement, comparison of AI outputs with human-authored sources, and metacognitive reflection on when and why AI was consulted. Their synthesis of educational theory with practical implementation strategies makes this work useful for understanding how pedagogy must evolve to treat AI as both subject matter (what students must understand about how AI functions) and scaffolding (how AI can support learning when used transparently and reflectively).

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Yim, Iris Heung Yue, and Jiahong Su. 2025. “Artificial Intelligence (AI) Learning Tools in K-12 Education: A Scoping Review.” ''British Journal of Educational Technology'' 56 (1): 169–196. https://doi.org/10.1007/s40692-023-00304-9&lt;nowiki/&gt;.'''
&lt;/div&gt;

Yim and Su's scoping review of AI literacy education in K-12 contexts provides grounding for understanding how pedagogy approaches AI as an object of study, not merely as a tool, revealing how students across age groups learn to understand, critique, and create with AI systems. The authors document how intelligent agents (Google Teachable Machine, Learning ML) and software platforms (Scratch, Python) enable students to engage with AI's underlying mechanisms—training models, observing how data shapes outputs, and experiencing firsthand how algorithmic decision-making operates. This approach treats AI as epistemological phenomenon: students don't just use pretrained models but build simple systems themselves, making visible how AI &quot;learns&quot; and where its learning breaks down (limited training data, biased datasets, inability to generalize beyond training conditions). Yim and Su's synthesis of pedagogical strategies—project-based learning where students create AI applications, human-computer collaboration examining how humans and machines complement each other, and game-based approaches making AI concepts accessible—demonstrates how educators scaffold understanding from concrete manipulation to abstract reasoning about intelligence and automation. The review's attention to cognitive, affective, and behavioural learning outcomes moves beyond narrow skill acquisition to examine how AI literacy shapes students' broader epistemic stance: understanding AI's capabilities and limitations, recognizing when algorithmic solutions are appropriate, and developing critical awareness of AI's social implications. Their emphasis on age-appropriate pedagogies and the importance of unplugged activities (learning AI concepts through physical manipulation before digital implementation) provides models for how pedagogy must adapt to learners' developmental stages when teaching about AI systems. This work's K-12 focus complements higher education studies in this section by showing how foundational AI literacy built through hands-on exploration creates readiness for more sophisticated critical engagement with AI as both tool and object of study in advanced scholarship.

== Service and Peer Review ==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Checco, Alessandro, Lorenzo Bracciale, Pierpaolo Loreti, Stephen Pinfield, and Giuseppe Bianchi. 2021. “AI-Assisted Peer Review.” ''Humanities and Social Sciences Communications'' 8: 25. https://doi.org/10.1057/s41599-020-00703-8&lt;nowiki/&gt;.'''
&lt;/div&gt;

Checco et al.'s study represents crucial early (pre-GenAI) empirical work demonstrating that AI can predict peer review outcomes based on &quot;superficial&quot; manuscript features—readability metrics, formatting consistency, reference list structure, linguistic patterns—with surprising accuracy, training neural networks on 3,300 conference papers to correlate these proxy measures with eventual accept/reject decisions. This finding has profound implications for understanding AI's operational role: the research reveals that much of what passes as peer review judgment operates on detectable patterns (clear writing, proper citation formatting, adherence to disciplinary conventions) that AI can identify and assess, potentially automating routine quality checks and flagging submissions unlikely to meet standards. However, the authors explicitly position their work as supporting &quot;semi-automated&quot; rather than fully automated review, emphasizing AI's role in pre-screening and administrative tasks (matching manuscripts with reviewers based on topic modelling, identifying obvious deficiencies) rather than intellectual evaluation. The paper's most valuable contribution lies in its systematic exploration of ethical implications: algorithmic bias risks (AI might penalize unconventional but innovative work, discriminate against non-native English writers, favour institutional prestige markers), transparency requirements (making AI decision criteria auditable), and the necessity of human oversight to prevent automation from calcifying existing disciplinary hierarchies. By documenting both AI's predictive capabilities on operational dimensions and its inherent limitations on substantive judgment, Checco et al. provide empirical foundation for designing peer review systems where AI handles standardized identification tasks while human expertise remains authoritative for evaluative assessment, directly instantiating the core principle that operational assistance must not migrate into epistemic territory.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Hosseini, Mohammad, and Serge P. J. M. Horbach. 2023. “Fighting Reviewer Fatigue or Amplifying Bias? Considerations and Recommendations for Use of ChatGPT and Other Large Language Models in Scholarly Peer Review.” ''Research Integrity and Peer Review'' 8 (1): 15. https://doi.org/10.21203/rs.3.rs-2587766/v1&lt;nowiki/&gt;.'''
&lt;/div&gt;

Published early in the ChatGPT era, Hosseini and Horbach's analysis provides a prescient examination of how LLM integration transforms both the pragmatics and ethics of peer review labour. The authors document LLMs' potential to combat reviewer fatigue by automating time-consuming tasks—transforming informal reviewer notes into polished reports, generating structured feedback on manuscript sections, identifying linguistic or formatting issues—thereby potentially expanding the pool of contributors who can participate effectively despite language barriers or time constraints. However, the article's core contribution lies in its still-useful systematic identification of risks that emerge when operational assistance crosses into epistemic territory: LLMs trained on existing literature may amplify disciplinary biases (favouring established paradigms over novel approaches), geographic biases (privileging research contexts well-represented in training data), or methodological orthodoxies (flagging unconventional designs as errors rather than innovations). The authors demonstrate through examples how ChatGPT can generate cynical or biased reviews that violate Mertonian norms of universalism, and how confidentiality breaches can occur when reviewers input manuscript excerpts into external AI platforms without institutional safeguards. Hosseini and Horbach's recommendations—mandatory disclosure of LLM use in reviews, human accountability for all AI-generated content, training in bias recognition, and institutional policies prohibiting upload of confidential materials—have influenced subsequent journal guidelines and provide foundational ethical framework for understanding why guardrails against leakage and disclosure norms become operational necessities rather than optional best practices in AI-entangled peer review systems.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Shcherbiak, Anna, Hooman Habibnia, Robert Böhm, and Susann Fiedler. “Evaluating Science: A Comparison of Human and AI Reviewers.” ''Judgment and Decision Making'' 19 (2024): e21. https://doi.org/10.1017/jdm.2024.24&lt;nowiki/&gt;.'''
&lt;/div&gt;

In this study, a large-scale field experiment comparing GPT-4 with human reviewers on conference abstracts provides empirical evidence about AI's capabilities and limitations in evaluative judgment. It demonstrates that while AI can approximate human performance on certain classification tasks—identifying &quot;very best&quot; abstracts shows moderate alignment—detailed evaluative assessments reveal persistent gaps, with human-AI agreement comparable to human-human variability, suggesting AI does not systematically outperform baseline reviewer disagreement. Critically, the research shows humans substantially outperform AI at detecting AI-generated versus human-written content, with detection tools like GPTZero exhibiting higher accuracy than GPT-4 itself when evaluating authorship. This finding has direct implications for peer review integrity when AI-generated manuscripts enter the submission pipeline. The authors position AI as effective for prescreening—rapidly filtering submissions for basic quality thresholds, identifying obvious errors, flagging compliance issues—while demonstrating it lacks the contextual understanding necessary for nuanced scientific judgment about significance, impact, or methodological soundness. The paper's methodological rigour in isolating human-versus-AI performance dimensions provides context for understanding where operational assistance (screening) legitimately ends and where human evaluative authority (substantive assessment) must begin, directly addressing the guiding principle that human judgment remains central even in AI-augmented workflows.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Lim, Gim Hui, M. L. Tan, V. C. W. Hoe, and D. Koh. 2025. “Generative AI in Peer Review Process for Occupational Health.” ''Occupational Medicine'' 75 (5): 242–49. https://doi.org/10.1093/occmed/kqaf051.'''
&lt;/div&gt;

Lim and colleagues' empirical study comparing Microsoft Copilot, ChatGPT, and Google Gemini against human reviewers on eight occupational health manuscripts provides granular quantitative evidence about AI's operational capabilities and limitations in peer review tasks. The research demonstrates that AI tools significantly outperform humans in providing feedback (mean score 3.44 vs. human baseline, p&lt;0.001) across dimensions of relevance, completeness, accuracy, error identification, and constructiveness—documenting AI's strength in systematic checking tasks like identifying missing citations, flagging methodological inconsistencies, noting formatting errors, and pointing out unclear explanations. However, humans substantially outperform AI in generating actionable recommendations (mean score 3.36, p&lt;0.01), with AI showing particular deficiencies in suggesting substantive revisions, connecting findings to broader literature, or identifying conceptual limitations. This performance asymmetry instantiates the operational/epistemic division: AI excels at identification tasks (what's wrong, what's missing) but struggles with evaluative tasks (how to improve, what matters). The study also quantifies efficiency gains (AI reviews complete in 11 minutes versus 45 for humans) while documenting critical limitations: AI outputs contain fabricated references, generate plausible-sounding but inaccurate technical assertions, and require human verification to prevent propagation of errors. Lim et al.'s work demonstrates that even when AI shows superior performance on specific metrics, its integration into peer review requires careful task decomposition—leveraging speed and comprehensiveness for checking functions while preserving human authority for substantive guidance—making it essential evidence for designing hybrid human-AI workflows where operational assistance enhances rather than replaces evaluative expertise.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Sun, Zhuanlan. 2025. “Large Language Models in Peer Review: Challenges and Opportunities.” ''Scientometrics'' 130 (10): 5503–5546. https://doi.org/10.1007/s11192-025-05440-w&lt;nowiki/&gt;.'''
&lt;/div&gt;

Sun provides essential mapping of LLM applications across the peer review lifecycle, categorizing five distinct operational roles: checklist assistants for formatting and protocol adherence, reviewer selection aids that match manuscripts with appropriate expertise, feedback generators for preliminary assessments, bias detectors that flag methodological or statistical irregularities, and agents that coordinate multi-stage review workflows. The article systematically examines technical approaches including prompt engineering strategies, model evaluation frameworks, and architectural designs for integrating LLMs into editorial management systems. The author argues that while LLMs excel at standardized operational tasks—checking reference integrity, identifying duplicated content across submission databases, verifying compliance with reporting guidelines—they remain fundamentally limited in assessing research novelty, theoretical contributions, and domain-specific methodological rigour. The analysis emphasizes that current LLM limitations (inadequate scientific validation, domain knowledge gaps, inability to analyze complex datasets, ethical concerns around bias perpetuation) position them as supportive tools within human-led processes rather than autonomous decision-makers. This work is useful in understanding operational versus epistemic divisions of labour in AI-assisted scholarship service and documenting the technical infrastructure through which AI becomes entangled with peer review operations while maintaining clear boundaries around human evaluative judgment.

== AI and Scholarship Infrastructures ==

=== Organizational Infrastructures ===

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Batool, Amna, Didar Zowghi, and Muneera Bano. 2025. “AI Governance: A Systematic Literature Review.” ''AI and Ethics'' 5: 3265–3279. https://doi.org/10.1007/s43681-024-00653-w&lt;nowiki/&gt;.'''
&lt;/div&gt;

Batool and colleagues' (2025) systematic literature review offers a comprehensive mapping of AI governance across multiple levels—team, organization, industry, national, and international. The authors utilize a structured analytical framework that examines who governs (stakeholders and roles), what is governed (data, algorithms, systems), when governance occurs (stages in the AI lifecycle), and how it is implemented (frameworks, tools, policies). The article reveals that current governance practices remain fragmented and inconsistent, with significant gaps at the national and international levels. Applied to the context of higher education, this multi-level perspective is essential for understanding how research institutions must position themselves within broader governance ecosystems. Because organizational governance currently operates without clear external scaffolding, research institutions are often forced to improvise institutional arrangements rather than implement established templates. While the paper is broad in scope, its categorization of governance artifacts illuminates the range of mechanisms available to scholarly organizations: from technical tools like algorithmic auditing to organizational structures like ethics committees. Ultimately, the authors' findings highlight the challenges facing research institutions as they attempt to coordinate AI oversight across distributed, autonomous units—such as libraries implementing discovery tools or IT departments deploying infrastructure—demonstrating why cross-functional coordination is both necessary and difficult when existing governance structures were not designed to span these boundaries.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Hadley, Emma, Alan Blatecky, and Megan Comfort. 2025. “Investigating Algorithm Review Boards for Organizational Responsible Artificial Intelligence Governance.” ''AI and Ethics'' 5: 2485–2495. https://doi.org/10.1007/s43681-024-00574-8&lt;nowiki/&gt;.'''
&lt;/div&gt;

Hadley and colleagues provide empirical documentation of algorithm review boards (ARBs) as organizational governance mechanisms, interviewing technical contributors across sectors to examine ARB membership, scope, success factors, and limitations. Their findings reveal ARBs as cross-functional bodies integrating diverse expertise (technical specialists, ethicists, domain experts, legal advisors, non-specialist stakeholders) to review AI systems for potential risks and harms, operating alongside other responsible AI approaches like policies, audits, and dedicated governance roles. The study's key insight that institutional review boards alone prove insufficient for algorithm governance and that ARBs function most effectively when integrated with existing organizational processes rather than operating as isolated oversight bodies speaks directly to research institutions' governance challenges. The article's documentation of financial tensions between profit motives and responsible AI costs, while focused on commercial contexts, translates to research institutions facing pressure to adopt AI for efficiency gains while managing ethical risks with constrained resources. Hadley et al.'s call for standardized ARB effectiveness metrics points to the broader challenge of demonstrating governance value in organizations where responsible AI practices compete with other institutional priorities for attention and investment.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Janssen, Marijn. 2025. “Responsible Governance of Generative AI: Conceptualizing GenAI as Complex Adaptive Systems.” ''Policy and Society'' 44 (1): 38–51. https://doi.org/10.1093/polsoc/puae040&lt;nowiki/&gt;.'''
&lt;/div&gt;

Janssen's conceptual article reframes generative AI governance as managing complex adaptive systems characterized by co-evolution, emergent properties, and non-linear interactions between technical and social elements, directly challenging technology-deterministic approaches that treat AI as static tool requiring one-time organizational accommodation. This systems perspective is essential for understanding why research institutions struggle with AI governance: the article demonstrates how AI systems and organizational contexts mutually shape each other through feedback loops, making governance an ongoing adaptive process rather than implementation of fixed policies. Janssen argues that effective organizational stewardship requires holistic, outward-focused governance attending to how AI systems interact with broader organizational processes, public values, and societal concerns—moving beyond narrow risk mitigation to address joint accountability across system components including people, policies, data, and algorithms. For research institutions embedding AI in knowledge infrastructures, this framing illuminates why isolated departmental responses prove insufficient: cataloging systems using AI for metadata generation, research platforms deploying AI for literature synthesis, and administrative systems using AI for resource allocation together constitute an organizational AI ecosystem whose emergent behaviours cannot be governed through component-level oversight alone. The article's emphasis on selecting and combining appropriate policy instruments into adaptive governance packages provides conceptual foundation for cross-functional coordination mechanisms, suggesting that effective institutional stewardship requires deliberate orchestration of technical standards, organizational procedures, and stakeholder engagement processes that together shape AI's organizational trajectory. Janssen's work underscores that AI governance is not primarily technical implementation challenge but organizational transformation requiring institutions to develop new capabilities for managing sociotechnical co-evolution.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Papagiannidis, Emmanouil, Patrick Mikalef, and Kieran Conboy. 2025. “Responsible Artificial Intelligence Governance: A Review and Research Framework.” ''The Journal of Strategic Information Systems'' 34 (2): 101885. https://doi.org/10.1016/j.jsis.2024.101885&lt;nowiki/&gt;.'''
&lt;/div&gt;

Papagiannidis and colleagues provide theoretical grounding for understanding how organizations operationalize responsible AI principles through governance structures. Their scoping review synthesizes disparate literature to construct a conceptual framework differentiating between structural practices (formal roles, committees, reporting lines), relational practices (stakeholder engagement, accountability mechanisms), and procedural practices (auditing protocols, monitoring systems) across the AI lifecycle. This tripartite framework is valuable for research institutions navigating the challenge of translating broad ethical commitments into actionable organizational arrangements. The article explicitly addresses how governance antecedents like leadership commitment and regulatory pressure shape implementation, and how governance practices in turn affect outcomes like trust, compliance, and innovation capacity. The authors' critical reflection on responsible AI governance reveals tensions inherent to institutional stewardship: between centralized oversight and distributed expertise, between standardized protocols and context-sensitive judgment, between rapid AI deployment and deliberative ethical review. For research organizations managing AI's entanglement with knowledge infrastructures, this work provides vocabulary and analytical categories for diagnosing governance gaps and designing institutional responses that embed responsibility throughout organizational systems rather than treating ethics as external constraint.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Weber, Michael, Martin Engert, Norman Schaffer, Jörg Weking, and Helmut Krcmar. 2023. “Organizational Capabilities for AI Implementation—Coping with Inscrutability and Data Dependency in AI.” ''Information Systems Frontiers'' 25: 1549–1569. https://doi.org/10.1007/s10796-022-10297-y&lt;nowiki/&gt;.'''
&lt;/div&gt;

Weber and colleagues identify four organizational capabilities essential for AI implementation, addressing AI's distinctive characteristics that distinguish it from previous information technologies: inscrutability (difficulty predicting probabilistic outputs and explaining decision processes) and data dependency (reliance on high-quality, continuously updated data for system performance). Their capability framework—encompassing AI Project Planning, Co-Development, Data Management, and AI Model Lifecycle Management—provides actionable guidance for research institutions developing internal capacity to steward AI systems. The article's grounding in expert interviews from diverse organizational contexts reveals that AI implementation failures often stem not from technical deficits but from organizational incapacity to manage sociotechnical complexity: inscrutability requires enhanced planning and stakeholder communication practices to align expectations around uncertain outcomes, while data dependency demands robust governance of data quality, provenance, and evolution throughout systems' operational lives. For research organizations, these capabilities map onto critical institutional functions: libraries developing metadata systems must manage data quality for AI cataloguing tools; research offices supporting computational scholarship must plan projects acknowledging unpredictable AI behaviour; IT departments maintaining infrastructure must implement lifecycle management ensuring model performance doesn't degrade as institutional data changes. The article's emphasis on Co-Development capability—bringing together technical specialists, domain experts, and end-users to jointly shape AI systems—speaks directly to cross-functional coordination challenges in research institutions where AI touches multiple organizational domains. Weber et al.'s framework reveals that organizational stewardship requires not just governance structures (committees, policies, review processes) but operational capabilities (planning methods, collaboration practices, technical procedures) embedded in day-to-day institutional work. This capability perspective shifts attention from abstract principles to concrete organizational competencies that determine whether responsible AI rhetoric translates into institutional practice.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Wu, Chuhao, He Zhang, and John M. Carroll. 2024. “AI Governance in Higher Education: Case Studies of Guidance at Big Ten Universities.” Preprint, ''arXiv'', September 3. https://doi.org/10.48550/arXiv.2409.02017&lt;nowiki/&gt;.'''
&lt;/div&gt;

Wu and colleagues provide rare empirical documentation of how major research universities translate AI governance principles into institutional practice, examining guidance documents from fourteen Big Ten universities to identify organizational patterns and role-specific strategies. Their analysis reveals three key organizational dimensions: multi-unit governance involving information technology departments, teaching and learning centres, libraries, and research offices operating with distributed authority rather than centralized control; role-specific guidance differentiating expectations for faculty, students, staff, and researchers rather than applying uniform policies; and educational-advisory approaches emphasizing learning and adaptation over compliance enforcement. This case-study evidence illuminates the pragmatic challenges research institutions face when operationalizing AI oversight: how to coordinate across functional silos with different mandates, expertise, and risk tolerances; how to balance flexibility (needed because AI applications vary dramatically across contexts) with consistency (needed to ensure institutional values are upheld); how to position governance as enabling innovation rather than constraining it. The article's documentation of specific institutional mechanisms, such as data classification systems limiting what information can be shared with AI tools, or Socratic guidance approaches that pose questions rather than dictate answers, provides concrete examples of organizational stewardship in action. For understanding AI's organizational entanglement with knowledge infrastructures, this work demonstrates how governance emerges through negotiation among multiple institutional actors, each bringing domain expertise and jurisdictional claims, requiring coordination mechanisms that existing organizational charts may not accommodate.

=== Publishing, Communication, Engagement Infrastructures ===

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Bergstrom, Tracy, and Dylan Ruediger. 2024. “A Third Transformation? Generative AI and Scholarly Publishing.” ''Ithaka S+R''. October 30, 2024. https://doi.org/10.18665/sr.321519&lt;nowiki/&gt;.'''
&lt;/div&gt;

Drawing on interviews with leaders from publishers, technology disruptors, academic libraries, and scholarship, Bergstrom and Ruediger map the strategic landscape of AI adoption across the publishing industry. The report identifies a bifurcated future: an incrementalist scenario where AI produces efficiency gains without fundamentally altering industry dynamics, versus a transformative scenario creating disruption comparable to or exceeding previous digital transformations. For search and discovery, most interviewees anticipate heavy AI impact, with tools already expanding capabilities through summarization and chatbot interfaces—potentially disrupting the linear progression from discovery to understanding by introducing AI-enabled synthesis. For peer review, interviewees expressed optimism that AI could address chronic strain through &quot;pre-review&quot; feedback, assistance with copy editing and misconduct detection, and more efficient reviewer identification, while raising concerns about accuracy, confidentiality, and maintaining human judgment in evaluation. The authors document a competitive threat from large technology companies: scenarios where commercial LLMs become default interfaces for accessing scholarly content pose significant challenges to publisher positioning. Content licensing to foundation model developers offers clear monetization paths, but broader revenue implications remain uncertain. The analysis identifies a critical research integrity challenge: ensuring transparent standards for AI usage while upholding provenance, attribution, reproducibility, and transparency in an environment of increasing automation. Smaller publishing organizations may struggle to match larger entities' adaptive capacity, potentially accelerating industry consolidation. 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Broussard, Meredith. 2023. “The Challenges of AI Preservation.” ''The American Historical Review'' 128 (3): 1378–81. https://doi.org/10.1093/ahr/rhad366.'''
&lt;/div&gt;

Broussard illustrates how the current impermanence of digital storage is producing a nightmare for future historians, as content is hidden away by licensing agreements or simply disappears when its host platform ceases to exist. Earlier ideals of the internet preserving a “complete first draft of history” are far from the reality, and problems only intensify when considering the development of AI, which Broussard compares to the printing press. For example, one could access a record of a physical newspaper published on a given day, but Google Search’s software is constantly changing with no canonical daily version, which means no historian could ever hope to examine a comparable snapshot of an AI. Operations like the Internet Archive and the development of emulation can help diminish losses, but it must be recognized that the digital world is decaying.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Buitrago-Ciro, Jairo, Marta Samokishyn, Rachel Moylan, Jonathan Hernández Pérez, Oluwabunmi Bakare-Fatungase, and Carmel Firdawsi. 2025. “Bridging the AI Gap: Comparative Analysis of AI Integration, Education, and Outreach in Academic Libraries.” ''IFLA Journal'' 51 (3): 682–702. https://doi.org/10.1177/03400352251325274. '''
&lt;/div&gt;

Buitrago-Ciro et al. examine the websites of 40 libraries in North America, Western Europe, Latin America, and Africa to explore how they have integrated AI technologies into their services, policies, and outreach efforts. Overall, the authors found a geographic divide in the integration of AI into library services, because almost all North American and European libraries had AI educational outreach activities and resources, while only five (out of 10) Latin American libraries and one (out of 10) African libraries did outreach activities. However, AI integration into library services and development of library AI policies and guidelines was more uncommon across all regions, as less than half of North American and European libraries engaged in these activities, while only one library in Latin America and one in Africa integrated AI into their services and none had specific library AI policies. These regional differences in AI integration stem from each region’s socioeconomic contexts, social inequalities, and technological gaps that present additional challenges for AI adoption in African and Latin American libraries. 

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Gulson, Kalervo N., and P. Taylor Webb. 2023. “Steering the Mind Share: Technology Companies, Policy and Artificial Intelligence Research in Universities.” ''Discourse: Studies in the Cultural Politics of Education'' 44 (2): 195–207. https://doi.org/10.1080/01596306.2021.1981828. '''
&lt;/div&gt;

Gulson and Webb examine how major technology companies are actively reshaping the landscape of artificial intelligence research within universities. Drawing on interviews with computer scientists as part of a broader international project, the authors investigate three key areas: the influence of tech companies on AI research practices, the policy frameworks that foster academia-industry collaborations, and the role of &quot;open science&quot; in facilitating the transfer of academic ideas to the corporate sector. The study highlights that the boundaries between academic and corporate research have become highly porous. Companies like Google do not merely act as external funders; they are deeply embedded within university ecosystems, actively steering research directions. Furthermore, the authors illustrate how national policies, such as Canada’s Pan-Canadian Artificial Intelligence Strategy, legitimize and accelerate this corporate influence by heavily incentivizing industry partnerships. While these collaborations provide universities with crucial resources and drive innovation, Gulson and Webb warn that they also raise significant concerns regarding conflicts of interest and the corporatization of open science. Ultimately, the authors argue that corporate funding creates powerful feedback loops among tech companies, policy-makers, and academics, effectively allowing industry to capture the &quot;mind share&quot; of university research.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Kousha, Kayvan, and Mike Thelwall. 2024. “Artificial Intelligence to Support Publishing and Peer Review: A Summary and Review.” ''Learned Publishing'' 37 (1): 4–12. https://doi.org/10.1002/leap.1570&lt;nowiki/&gt;.'''
&lt;/div&gt;

Kousha and Thelwall provide a systematic mapping of AI tool deployment across the scholarly publishing pipeline, distinguishing demonstrated capabilities from promotional claims. For journal recommendation, the review documents AI-powered systems, including Springer Nature Journal Suggester, Wiley Journal Finder, IEEE Publication Recommender, and JANE (Journal/Author Name Estimator), that analyze text similarity with previously published articles and reports high accuracy rates for appropriate journal matching. The analysis of initial quality control covers a diverse toolkit for plagiarism detection, robot author detection, methods checking, automated statistical verification, transparency and reproducibility checking and manuscript structure validation. Commercial systems draw on databases to suggest appropriate reviewers; the Natural Science Foundation of China's AI-assisted reviewer recommender for grant applications reports approximately 80% accuracy. However, the review identifies a critical boundary: while AI proves effective for finding reviewers and conducting initial quality checks, its value in performing the actual substantive review process &quot;has not been clearly demonstrated.&quot; The synthesis reveals that substantial efficiency improvements are achievable in labour-intensive administrative tasks, while human judgment remains integral to core intellectual evaluations—a distinction essential for understanding where AI integration in publishing will proceed incrementally versus face fundamental obstacles.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Ma, Lai. 2024. “Generative AI for Academic Publishing? Some Thoughts About Epistemic Diversity and the Pursuit of Truth.” ''KULA: Knowledge Creation, Dissemination, and Preservation Studies'' 7 (1): 1–5. https://doi.org/10.18357/kula.287.'''
&lt;/div&gt;

Ma (2024) critiques the integration of generative AI in academic publishing, arguing that the drive for automation threatens the central values of epistemic diversity and bibliodiversity. By invoking the &quot;Sokal Hoax,&quot; the author illustrates the danger of AI-generated &quot;bullshit&quot;—content that mimics the formal structures of scholarship while remaining devoid of actual meaning. Ma specifically uses Scopus AI as a case study to demonstrate how the platformization of scholarly data creates a feedback loop that reinforces the &quot;Matthew Effect,&quot; where established, English-language, and well-resourced publications are disproportionately amplified. This process, Ma warns, leads to &quot;epistemic injustice&quot; by marginalizing non-Western research and niche topics that are underrepresented in training datasets. The paper serves as a vital warning: without robust data surveillance and human-centric safeguards, the AI-accelerated publishing model may exacerbate peer-review crises and citation monopolies, ultimately undermining the public trust and diverse knowledge creation that open scholarship aims to protect.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Mitchell, Peta, Michelle Riedlinger, Jake Goldenfein, Aaron Snoswell, Jean Burgess, and Kevin Witzenberger. 2025. “Research Genai: Situating Generative AI in the Scholarly Economy.” ''AoIR Selected Papers of Internet Research''. https://doi.org/10.5210/spir.v2024i0.14006.'''
&lt;/div&gt;

Mitchell et al. focus upon the oft-overlooked subfield of Generative AI tools known as “RGAI”, research-focused models which they argue represent “complex sociotechnical systems.” Hepp et al.’s definition of AI as a “sensitizing concept” and Watermeyer’s consideration of AI as a “labor accelerator” are used to situate this argument within the “scholarly economy” before the authors expand upon these theories, arguing RGAI should be approached as a form of “platform capitalism” akin to academia.edu. To evidence this stance, the authors examine the highly distinct RGAI models “Consensus” and “Writefull” as case studies. “Consensus” is designed to produce an academic “ConsensusMeter” by combining a proprietary LLM with OpenAI technology, while “Writefull” “aims to simplify… the often challenging task of scholarly writing” by employing custom AI models. Mitchell et al. highlight that although both tools are presented as independent and bespoke, they have major corporate backing. This deeply conflicts with the research principles of open scholarship, so Mitchell et al. aim to develop an index of RGAI which are appropriate for use in research.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Pividori, Milton, and Casey S. Greene. 2024. “A Publishing Infrastructure for Artificial Intelligence (AI)-Assisted Academic Authoring.” ''Journal of the American Medical Informatics Association'' 31 (9): 2103–13. https://doi.org/10.1093/jamia/ocae139&lt;nowiki/&gt;.'''
&lt;/div&gt;

The Manubot AI Editor implements a concrete technical solution to the provenance problem in AI-assisted scholarship through three integrated components: a Python library, a GitHub Actions workflow, and a prompt generator. This architecture addresses provenance directly: all changes are tracked through version control, creating a clear audit trail distinguishing human-authored from machine-generated text and documenting exactly how AI suggestions were accepted, modified, or rejected. Evaluation proceeded through five case studies using both human and automated assessment. Human evaluators assessed whether revisions preserved original meaning and important details, avoided introducing incorrect information, and maintained correct formatting. Automated &quot;LLM-as-a-Judge&quot; iterative assessment evaluated paragraph pairs across criteria including sentence structure clarity, ease of understanding, and grammatical correctness. The evaluations found that models could grasp complex academic concepts and enhance text quality, with particular effectiveness in text-based sections like introductions and discussions. The human-in-the-loop design, where AI suggestions function as proposed edits rather than direct insertions, mitigates risks of incorrect information while preserving authorial agency over final content.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Razack, Habeeb Ibrahim Abdul, Sam T. Mathew, Fathinul Fikri Ahmad Saad, and Saleh A. Alqahtani. 2021. “Artificial intelligence-assisted tools for redefining the communication landscape of the scholarly world.” ''Science Editing''. https://doi.org/10.6087/kcse.244. '''
&lt;/div&gt;

Razack et al. argue AI will transform publishing into a technology-driven industry, streamlining dissemination of scholarship “for the betterment of humankind.” Exploring current trends via case studies, they emphasize AI’s impact upon human performance over its independent “creative” role. They argue AI could benefit the “prospective” researcher by predicting an article’s “citation impact,” identifying evolving research trends, and locating relevant research journals to publish in, cutting past low-charging and “predatory OA journals” which “malign integrity” by publishing “compromised content.” Meanwhile, “retrospective” editors could employ AI to detect plagiarism, streamline peer review, and format publications. For Razack et al., the rise of AI can therefore be compared to the rise of the typewriter, swift adoption likely promoting &quot;human-machine collaboration&quot; over replacement.

=== Accountability-related Infrastructures ===

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Ngulube, Patrick, and Neema Florence Vincent Mosha. 2024. “Integrating Artificial Intelligence-Based Technologies ‘Safely’ in Academic Libraries: An Overview through a Scoping Review.” ''Technical Services Quarterly'' 42 (1): 46–67. https://doi.org/10.1080/07317131.2024.2432093&lt;nowiki/&gt;.'''
&lt;/div&gt;

Ngulube and Mosha (2025) conduct a scoping review examining the state of research on ethical issues and perceived risks in AI integration within academic libraries. Analyzing 28 studies published before 2024, the authors reveal that research on safe AI adoption in libraries remains nascent, with significant gaps in theoretical grounding and methodological diversity. The review identifies critical ethical concerns including algorithmic bias, privacy violations, reduced transparency and accountability, and job displacement—yet finds that existing literature disproportionately emphasizes employment risks while neglecting environmental and planetary impacts. The authors note that ethical considerations have not taken centre stage in library and information science research, as evidenced by the scarcity of relevant keywords and abstracts in the literature. A major finding is that most studies employ quantitative methodologies at the expense of qualitative and mixed-methods approaches, and only 18% employ explicit theoretical frameworks. The review underscores that academic libraries must navigate the dual challenge of leveraging AI's operational efficiencies while ensuring ethical standards of inclusivity, accessibility, and fair information use—a task complicated by the absence of established best practices and the need for human-centred approaches to AI governance.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''“Realising Potential, Supporting Users: IFLA Statement on Copyright and Artificial Intelligence.” n.d. IFLA. Accessed May 1, 2025. https://www.ifla.org/news/realising-potential-supporting-users-ifla-statement-on-copyright-and-artificial-intelligence/. '''
&lt;/div&gt;

This statement aims to help IFLA member libraries in navigating copyright issues and developing programs relevant to AI, positioning libraries as innovators “uniquely situated to lead” in supporting, training, and utilizing AI. However, restrictions stem from rightsholders, economic and moral copyright laws, and health, safety, and privacy laws. Libraries should therefore be guided by the most appropriate policy sources to mitigate restrictions by ensuring AI tools do not compromise areas of concern. Libraries are further recommended to advise decision-makers to permit mining legally accessed content, address bias by promoting “the widest possible access,” build capacity, awareness, and training for evolving technologies, and monitor AI standards. Governments are recommended to follow existing human rights regulations, avoid using copyright law as a “blunt force tool,” develop ethical AI practices, and fund repositories of AI training data—alongside AI companies themselves. Both rightsholders and vendors are advised to avoid language in contracts which restricts the use of AI or prevents exceptions. Overall, this document aims to promote AI by making as much content available as possible.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Werder, Karl, Balasubramaniam Ramesh, and Rongen (Sophia) Zhang. 2022. “Establishing Data Provenance for Responsible Artificial Intelligence Systems.” ''ACM Transactions on Management Information Systems'' 13 (4): 1–25. https://doi.org/10.1145/3503488&lt;nowiki/&gt;.'''
&lt;/div&gt;

Werder et al. provide a framework for understanding audit trails in the context of AI and research data management, arguing that robust data provenance is not merely a technical feature but a prerequisite for achieving accountability in AI systems. They detail the requirements for a comprehensive provenance system, capable of tracking data from its origin through various transformations and into model training and deployment. This is directly relevant to research infrastructures, as it outlines how repositories and data management platforms can and must evolve to support AI-driven research. The authors’ multi-layered architectural proposal offers a concrete vision for how a research institution could implement a system to audit data pipelines, identify sources of bias, and ensure regulatory compliance. By connecting provenance to the broader goal of “Responsible AI,” the paper provides the conceptual tools for evaluating whether a research infrastructure’s data governance is sufficient to handle the accountability challenges posed by AI.

== Audience ==

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''de Angelis, Luigi, Francesco Baglivo, Guglielmo Arzilli, Gaetano Pierpaolo Privitera, Paolo Ferragina, Alberto Eugenio Tozzi, and Caterina Rizzo. “ChatGPT and the Rise of Large Language Models: The New AI-Driven Infodemic Threat in Public Health.” ''Frontiers in Public Health'' 11 (2023): 1166120. https://doi.org/10.3389/fpubh.2023.1166120&lt;nowiki/&gt;.'''
&lt;/div&gt;

De Angelis and colleagues examine the emergence of Large Language Models, particularly ChatGPT, as a novel public health threat through the lens of &quot;AI-driven infodemic.&quot; The authors trace the rapid evolution of LLMs from earlier transformer-based models through GPT-3 to ChatGPT, highlighting how each iteration has increased the capacity to generate fluent, authoritative-sounding text at scale. Critically, they identify a fundamental misalignment problem: despite efforts to fine-tune these models through reinforcement learning from human feedback, LLMs remain prone to generating plausible-sounding but factually incorrect or fabricated information—a vulnerability particularly dangerous in medical and health contexts. The paper's central argument is that the unprecedented speed and volume at which LLMs can produce convincing content creates conditions for misinformation spread on a scale previously impossible, especially among non-expert publics who lack the epistemic resources to detect AI-generated falsehoods. The authors emphasize that the inability to reliably detect AI-produced text compounds this threat, undermining public trust in scientific institutions and potentially influencing health-related behaviours and policy decisions. The work demonstrates how LLM-mediated scientific communication poses distinct risks to knowledge integrity and public understanding, requiring urgent development of detection mechanisms, governance frameworks, and media literacy initiatives to protect audiences from AI-driven epistemic harm.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Bryant, Rebecca. 2024. “Implementing an AI Reference Chatbot at the University of Calgary Library.” ''Hanging Together'', December 12. https://hangingtogether.org/implementing-an-ai-reference-chatbot-at-the-university-of-calgary-library/&lt;nowiki/&gt;.'''
&lt;/div&gt;

Bryant (2024) details the development and implementation of &quot;T-Rex,&quot; an AI-powered reference chatbot at the University of Calgary Library, based on a webinar hosted by the OCLC Research Library Partnership. While the library had offered live chat services since the early 2010s, the COVID-19 pandemic caused a massive surge in demand, peaking at over 3,000 inquiries in a single month. To alleviate this strain, the library analyzed past chat transcripts and determined that 12–14% of inquiries were simple, directional questions suitable for automation. To prevent scope creep during the initial training phase, the development team focused on a core set of fifty common questions. Through continuous refinement, the chatbot has since expanded to encompass over 1,000 custom responses, though its effectiveness remains limited by the availability of existing library webpages or FAQs to draw from. Bryant concludes by summarizing the Calgary team's key insights for institutions developing similar tools: developers must anticipate out-of-scope or non-library questions, recognize that users prefer direct answers over links to webpages, program creative responses for off-topic queries, and prepare for user resistance or non-adoption.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Hara, Noriko, Eugene Kim, Shohana Akter, and Kunihiro Miyazaki. 2025. “Exploring the Dynamics of Interaction About Generative Artificial Intelligence Between Experts and the Public on Social Media.” ''Journal of Science Communication'' 24 (1): A02. https://doi.org/10.22323/2.24010202&lt;nowiki/&gt;.'''
&lt;/div&gt;

Hara and colleagues conduct an empirical investigation into how experts and the public co-produce knowledge about generative AI on social media, specifically analyzing X (formerly Twitter) discussions. Rather than treating the public as passive consumers of expert knowledge, the authors adopt a Public Engagement with Science (PES) framework that recognizes social media platforms as dynamic arenas where non-experts actively contribute to shaping collective understanding of emerging technologies. Through computational and manual analysis, they identify distinct discussion topics, map the roles that both experts and laypeople play in knowledge production, and examine how engagement metrics correlate with these roles. A critical finding is that the public functions beyond questioners seeking expert guidance, but rather as active knowledge co-producers who share practical insights, challenge claims, and contribute their own perspectives and experiences with GenAI tools. This research demonstrates how AI itself—as a subject of discourse—becomes a site of negotiated meaning-making between differently positioned actors. The work moves beyond traditional one-way dissemination models to reveal the interactive, participatory nature of contemporary science communication, with implications for understanding how diverse audiences collectively construct understanding of transformative technologies and how this co-productive process shapes both public perception and the future development of AI systems.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Jaillant, Lise, Olivia Mitchell, Eric Ewoh-Opu, and Maribel Hidalgo Urbaneja. 2025. “How Can We Improve the Diversity of Archival Collections with AI? Opportunities, Risks, and Solutions.” ''AI &amp; Society'' 40: 4457–4459. https://doi.org/10.1007/s00146-025-02222-z. '''
&lt;/div&gt;

Jaillant et al. draw from interviews with 20 academics and archival professionals to explore how AI technologies can help address the lack of diversity in archival collections. The authors highlight that AI tools can assist in automatically detecting racist or inappropriate language in metadata, search large amounts of historical records, and uncover new insights within archival records. However, the authors argue that the deployment of AI should involve close collaboration between librarians, archivists, and developers. The current limited collaboration between developers and libraries limits the ethical and inclusive application of AI in archival collections, especially those with sensitive historical materials. The interviewees also warned against the loss of historical context when using AI, the perpetuation of archival biases, and the loss of control when AI tools are designed and governed by tech companies. To conclude, the authors recommend investing in interdisciplinary AI training programs for archivists, educating AI developers about the unique needs of archives so they can create more relevant solutions, and creating professional guidelines about the best practices for AI use to address the lack of diversity in archival collections.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Peters, Uwe, and Benjamin Chin-Yee. 2025. “Generalization Bias in Large Language Model Summarization of Scientific Research.” ''Royal Society Open Science'' 12 (4): 241776. https://doi.org/10.1098/rsos.241776&lt;nowiki/&gt;.'''
&lt;/div&gt;

Peters and Chin-Yee provide rigorous, large-scale empirical evidence of a systematic and consequential distortion in LLM-generated scientific summaries: the tendency toward overgeneralization. Testing 10 prominent LLMs—including ChatGPT-4o, ChatGPT-4.5, DeepSeek, LLaMA 3.3 70B, and Claude 3.7 Sonnet—on 4,900 summaries of scientific abstracts and full-length articles, the authors demonstrate that even when explicitly prompted for accuracy, most LLMs consistently produce conclusions broader and more definitive than those warranted by the original research. Critically, they identify three specific mechanisms of overgeneralization: the use of generic statements that obscure quantification, the shift from past to present tense (which expands scope), and the omission of qualifiers and limitations. The findings are stark: LLM-generated summaries were nearly five times more likely than human-authored summaries to contain broad generalizations (odds ratio = 4.85, 95% CI [3.06, 7.70], p &lt; 0.001), with newer models performing worse than earlier ones. This research is foundational for understanding how AI-mediated knowledge communication systematically distorts scientific findings at scale, regardless of user expertise or intent. The work demonstrates a concrete mechanism through which LLM intermediation can alter the epistemic content of research, with particular implications for medical and clinical contexts where overgeneralized conclusions can directly influence policy and patient care. The authors propose mitigation strategies including temperature adjustment and systematic benchmarking, but their findings underscore the profound challenge of ensuring faithful knowledge transmission through AI systems.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''da Silva Cardoso, Heike, and Vitor Rocio. 2025. “Enhancing Digital Libraries Through NLP and Recommender Systems: Current Trends and Future Prospects with Large Language Models.” In ''Technology and Innovation in Learning, Teaching and Education: TECH-EDU 2024'', edited by Arsénio Reis, José P. Cravino, Leontios Hadjileontiadis, Paulo Martins, Sofia B. Dias, Sofia Hadjileontiadou, and Tassos Mikropoulos, 69–79. C''ommunications in Computer and Information Science'' 2480. Cham: Springer. https://doi.org/10.1007/978-3-032-02672-9_5&lt;nowiki/&gt;.'''
&lt;/div&gt;

da Silva Cardoso and Rocio propose a practical framework for integrating Natural Language Processing and Large Language Models into academic digital libraries to address the information overload facing researchers, students, and faculty. Recognizing that traditional search methods have become insufficient in the face of exponential publication growth, the authors advocate for AI-driven recommender systems capable of delivering precise, relevant, and personalized literature recommendations. Their contribution centres on an audience-aware design philosophy that positions librarians as essential partners in system development. Rather than treating AI as a purely algorithmic solution, the authors emphasize that librarians' direct interactions with users provide irreplaceable insight into the nuanced and context-dependent needs of diverse academic communities. This human-in-the-loop approach represents a noteworthy methodological stance: AI functions not as a replacement for human expertise but as a tool to augment librarian knowledge and enhance the responsiveness of knowledge discovery systems. The work is particularly salient for understanding how contemporary LLM-based systems can be designed to serve scholarly audiences more effectively while maintaining the institutional wisdom and user-centred perspective that librarians bring to information work.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''Taneja, Ankit Kumar, and Chandra Tripathi. 2020. “AI-Powered Recommender Systems: Personalization and Bias.” ''Turkish Journal of Computer and Mathematics Education (TURCOMAT)'' 11 (1): 1090–1094. https://doi.org/10.61841/turcomat.v11i1.14406&lt;nowiki/&gt;.'''
&lt;/div&gt;

Though published before the generative AI era, Taneja and Tripathi's analysis of AI-powered recommender systems remains foundational to understanding algorithmic bias in information discovery. The authors examine the structural tensions inherent in personalization algorithms—systems designed to enhance user experience by tailoring content suggestions yet simultaneously capable of constructing &quot;filter bubbles&quot; and &quot;echo chambers&quot; around users. By continuously recommending content similar to previous engagement, these algorithms systematically exclude novel, dissenting, or interdisciplinary perspectives, undermining serendipitous discovery essential to genuine scholarly inquiry. Critically, the authors frame algorithmic bias not as a technical glitch but as a structural risk embedded within the information architectures that guide knowledge-seekers, and thus they expose how algorithmic personalization—a feature predating generative AI—already demonstrated the capacity to narrow intellectual diversity and reinforce pre-existing beliefs. This pre-GenAI work provides historical context for understanding how contemporary AI systems have intensified these risks, making it useful for evaluating the ethical imperatives of designing systems that promote intellectual openness rather than epistemic closure.

&lt;div style=&quot;text-indent: -20px; padding-left: 20px; margin-bottom: -10px&quot;&gt;
'''de Winter, J. 2024. “Can ChatGPT Be Used to Predict Citation Counts, Readership, and Social Media Interaction? An Exploration Among 2222 Scientific Abstracts.” ''Scientometrics'' 129: 2469–2487. https://doi.org/10.1007/s11192-024-04939-y&lt;nowiki/&gt;.'''
&lt;/div&gt;

De Winter’s study contrasts conventional scientometrics, testing whether a large language model can predict an article’s citation count and altmetric scores (whilst noting these may be unreliable assessors of actual scientific impact) by rating its abstract across “semantically diverse” variables. His case study uses ChatGPT-4 to predictively evaluate 2,222 abstracts from articles published in ''PLOS ONE'', monitoring its accuracy by referencing actual citation counts and altmetrics scores. De Winter employs a custom script to prompt OpenAI’s Application Programming Interface (API) to score each abstract on a scale of zero to one hundred across thirty positive variables and their thirty antonyms, which he then organizes under five categories (e.g., “Quality and Reliability”). As Chat-GPT 4 only produced consistent results at the population level, it was run three additional times to determine averages and bolster reliability of individual scores. This language-based evaluation of article abstracts revealed that ChatGPT-4’s scores better correlate with altmetrics and citation counts than conventional readability scores do. Furthermore, “Novel and Engaging” articles were most likely to be cited, whilst “Accessible and Understandable” articles scored highest in altmetrics.

{{Navigation|previous=AI and Social|next=Complete Alphabetical List of References}}

{{BookCat}}</text>
      <sha1>5ulwj9yx4bfi0tlgt1vut93adzf53f1</sha1>
    </revision>
  </page>
  <page>
    <title>Taking Bearings: Artificial Intelligence in Knowledge Platforms and Open, Social Scholarship/Complete Alphabetical List of References</title>
    <ns>0</ns>
    <id>483648</id>
    <revision>
      <id>4656117</id>
      <parentid>4638687</parentid>
      <timestamp>2026-08-02T21:29:24Z</timestamp>
      <contributor>
        <username>CorreiaA</username>
        <id>3614427</id>
      </contributor>
      <minor />
      <origin>4656117</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="45568" sha1="6ogdg3sninbatr3zs9wgrc3zowj36tz" xml:space="preserve">{{CompactTOC8|center=yes|i=I|u=U}}

==A==
*Ación, Laura, Mariela Rajngewerc, Gregory Randall, and Lorena Etcheverry. 2023. “Generative AI Poses Ethical Challenges for Open Science.” ''Nature Human Behaviour'' 7 (11): 1800–1801. https://doi.org/10.1038/s41562-023-01740-4.
*Adewumi, Tosin, Lama Alkhaled, Claudia Buck, Sergio Hernandez, Saga Brilioth, Mkpe Kekung, Yelvin Ragimov, and Elisa Barney. 2024. “ProCoT: Stimulating Critical Thinking and Writing of Students through Engagement with Large Language Models (LLMs).” Preprint, ''arXiv'', May 1. https://doi.org/10.48550/arXiv.2312.09801.
*Aguiar, Micaela, and Sílvia Araújo. 2024. “Final Thoughts: Digital Humanities Looking at Generative AI.” In ''Digital Humanities Looking at the World'', edited by S. Araújo et al., 367–380. Cham: Springer Nature Switzerland.
*Akter, Shahriar, Grace McCarthy, Shahriar Sajib, Katina Michael, Yogesh K. Dwivedi, John D’Ambra, and K.N. Shen. 2021. “Algorithmic bias in data-driven innovation in the age of AI.” ''International Journal of Information Management'' 60, 102387. https://doi.org/10.1016/j.ijinfomgt.2021.102387.
*Ali, Syed Mustafa, Stephanie Dick, Sarah Dillon, Matthew L. Jones, Jonnie Penn, and Richard Staley. 2023. “Histories of Artificial Intelligence: A Genealogy of Power.” ''BJHS Themes'' 8: 1–18. https://doi.org/10.1017/bjt.2023.15.
*Al-kfairy, Mousa, Dheya Mustafa, Nir Kshetri, Mazen Insiew, and Omar Alfandi. 2024. “Ethical Challenges and Solutions of Generative AI: An Interdisciplinary Perspective.” ''Informatics'' 11 (3): 58. https://doi.org/10.3390/informatics11030058.
*Alvarez, Jose M., Alejandra Bringas Colmenarejo, Alaa Elobaid, Simone Fabbrizzi, Miriam Fahimi, Antonio Ferrara, Siamak Ghodsi, et al. 2024. “Policy Advice and Best Practices on Bias and Fairness in AI.” ''Ethics and Information Technology'' 26 (2). https://doi.org/10.1007/s10676-024-09746-w.
*Anderson, Marc M. 2024. “AI as Philosophical Ideology: A Critical Look Back at John McCarthy’s Program.” ''Philosophy &amp; Technology'' 37 (2): 44. https://doi.org/10.1007/s13347-024-00731-1.
*de Angelis, Luigi, Francesco Baglivo, Guglielmo Arzilli, Gaetano Pierpaolo Privitera, Paolo Ferragina, Alberto Eugenio Tozzi, and Caterina Rizzo. “ChatGPT and the Rise of Large Language Models: The New AI-Driven Infodemic Threat in Public Health.” ''Frontiers in Public Health'' 11 (2023): 1166120. https://doi.org/10.3389/fpubh.2023.1166120.
*Arbuckle, Alyssa. 2020. “How Can We Broaden and Diversify Humanities Knowledge Translation?” ''Pop! Public. Open. Participatory'', no. 2. https://doi.org/10.48404/pop.2020.12.
*Arbuckle, Arbuckle, Ray Siemens, Jon Bath, Constance Crompton, Laura Estill, Tanja Niemann, Jon Saklofske, and Lynne Siemens. 2022. “An Open Social Scholarship Path for the Humanities.” ''Journal of Electronic Publishing'' 25 (2). https://doi.org/10.3998/jep.1973.
*Arbuckle, Arbuckle, and John Maxwell. 2019. “Modelling Open Social Scholarship Within the INKE Community.” ''KULA: Knowledge Creation, Dissemination, and Preservation Studies'' 3 (1): 1–8. https://doi.org/10.5334/kula.15.
*Arnett, Catherine, Eliot Jones, Ivan P. Yamshchikov, and Pierre-Carl Langlais. “Toxicity of the commons: Curating open-source pre-training data.” Preprint, ''arXiv'', November 18. https://doi.org/10.48550/arXiv.2410.22587.
*Arora, Payal. 2024. “Creative data justice: a decolonial and indigenous framework to assess creativity and artificial intelligence.” ''Information, Communication &amp; Society'': 1–17. https://doi.org/10.1080/1369118x.2024.2420041.
*Arthur, Paul L., Lydia Hearn, Lucy Montgomery, Hugh Craig, Alyssa Arbuckle, and Ray Siemens. 2021. “Open Scholarship in Australia: A Review of Needs, Barriers, and Opportunities.” ''Digital Scholarship in the Humanities'' 36 (4): 795–812. https://doi.org/10.1093/llc/fqaa063.

==B==
*Bail, Christopher A. “Can Generative Artiﬁcial Intelligence Improve Social Science?”. https://www.semanticscholar.org/paper/Can-Generative-Artiﬁcial-Intelligence-Improve-Bail/6206cc77bb3a3c0b6b9fce1ad68a8b1786a56941.
*Bakharia, Aneesha, Antonette Shibani, Lisa-Angelique Lim, Trish McCluskey, and Simon Buckingham Shum. 2025. “From Transcripts to Themes: A Trustworthy Workflow for Qualitative Analysis Using Large Language Models.” In ''Joint Proceedings of LAK 2025 Workshops, co-located with the 15th International Conference on Learning Analytics and Knowledge (LAK 2025)''. Dublin, Ireland: CEUR-WS.org. https://ceur-ws.org/Vol-3995/LLMQUAL_paper1.pdf.
*Balendra, Soorya. 2025. “Meta's AI Moderation and Free Speech: Ongoing Challenges in the Global South.” ''Cambridge Forum on AI: Law and Governance'' 1. https://doi.org/10.1017/cfl.2025.5.
*Baltes, Sebastian, Florian Angermeir, Chetan Arora, Preetha Chatterjee, Jens Deitenbeck, Daniel Graziotin, Christoph Treude, et al. 2025. “Guidelines for Empirical Studies in Software Engineering Involving Large Language Models.” Preprint, ''arXiv'', August 21. https://arxiv.org/abs/2508.15503.
*Batool, Amna, Didar Zowghi, and Muneera Bano. 2025. “AI Governance: A Systematic Literature Review.” ''AI and Ethics'' 5: 3265–3279. https://doi.org/10.1007/s43681-024-00653-w.
*Bender, Emily M., Timnit Gebru, Angelina McMillan-Major, and Shmargaret Shmitchell. 2021. “On the Dangers of Stochastic Parrots: Can Language Models Be Too Big? 🦜.” ''Proceedings of the 2021 ACM Conference on Fairness, Accountability, and Transparency'' (New York, NY, USA), FAccT ’21, March 1, 610–23. https://doi.org/10.1145/3442188.3445922.
*Bender, Emily M., and Batya Friedman. 2018. “Data Statements for Natural Language Processing: Toward Mitigating System Bias and Enabling Better Science.” ''Transactions of the Association for Computational Linguistics'' 6: 587–604. https://doi.org/10.1162/tacl_a_00041.
*Bergstrom, Tracy, and Dylan Ruediger. 2024. “A Third Transformation? Generative AI and Scholarly Publishing.” ''Ithaka S+R''. October 30, 2024. https://doi.org/10.18665/sr.321519.
*Berry, David M. 2025. “Synthetic Media and Computational Capitalism: Towards a Critical Theory of Artificial Intelligence.” ''AI &amp; Society'' 40: 5257–5269. https://doi.org/10.1007/s00146-025-02265-2.
*Berry, D. M. (2023). AI, ethics, and digital humanities. In J. O’Sullivan (Ed.), ''The Bloomsbury handbook to the digital humanities'', 445–457. Bloomsbury Academic. https://recoveryhub.siue.edu/wp-content/uploads/2024/10/AI-Ethics-and-Digital-Humanities-.pdf.
*Biderman, Stella, Hailey Schoelkopf, Quentin Anthony, Herbie Bradley, Kyle O'Brien, Eric Hallahan, Mohammad Aflah Khan, et al. 2022. “EleutherAI: Going Beyond 'Open Science' to 'Science in the Open.'” Preprint, ''arXiv'', October 12. https://arxiv.org/abs/2210.06413.
*Birkstedt, Teemu, Matti Minkkinen, Anushree Tandon, and Matti Mäntymäki. 2023. “AI Governance: Themes, Knowledge Gaps and Future Agendas”. ''Internet Research'' 33 (7): 133–67. https://doi.org/10.1108/INTR-01-2022-0042.
*Boer, Victor de, and Lise Stork. 2024. “Hybrid Intelligence for Digital Humanities.” Version 1. Preprint, ''arXiv'', April 15. https://doi.org/10.48550/ARXIV.2406.15374.
*Bostrom, Nick. 2017. “Strategic Implications of Openness in AI Development.” ''Global Policy'' 8 (2): 135–148. https://doi.org/10.1111/1758-5899.12403
*Boyd, Karen. 2021. “Datasheets for Datasets Help ML Engineers Notice and Understand Ethical Issues in Training Data.” ''Proceedings of the ACM on Human-Computer Interaction'' 5 (CSCW2): 1–27. https://doi.org/10.1145/3479582.
*Bozkurt, Aras. 2024. “GenAI et al.: Cocreation, Authorship, Ownership, Academic Ethics and Integrity in a Time of Generative AI.” ''Open Praxis'' 16 (1): 1–10. https://doi.org/10.55982/openpraxis.16.1.654.
*Broekhuizen, Thijs, Henri Dekker, Pedro De Faria, Sebastian Firk, Dinh Khoi Nguyen, and Wolfgang Sofka. 2023. “AI for Managing Open Innovation: Opportunities, Challenges, and a Research Agenda.” ''Journal of Business Research'' 167: 114196. https://doi.org/10.1016/j.jbusres.2023.114196.
*Broussard, Meredith. 2023. “The Challenges of AI Preservation.” ''The American Historical Review'' 128 (3): 1378–1381. https://doi.org/10.1093/ahr/rhad366.
*Brown, Richard. 2023. “The AI Generation: How Universities Can Prepare Students for the Changing World.” DEMOS and University of London. https://demos.co.uk/wp-content/uploads/2023/11/The-AI-Generation-2.pdf.
*Bryant, Rebecca. 2024. “Implementing an AI Reference Chatbot at the University of Calgary Library.” ''Hanging Together'', December 12. https://hangingtogether.org/implementing-an-ai-reference-chatbot-at-the-university-of-calgary-library/.
*Buitrago-Ciro, Jairo, Marta Samokishyn, Rachel Moylan, Jonathan Hernández Pérez, Oluwabunmi Bakare-Fatungase, and Carmel Firdawsi. 2025. “Bridging the AI Gap: Comparative Analysis of AI Integration, Education, and Outreach in Academic Libraries.” ''IFLA Journal'' 51 (3): 682–702. https://doi.org/10.1177/03400352251325274.
*Bullard, J. (2023). “Describing the HSS Commons: The View from Metadata.” ''Pop! Public. Open. Participatory'', no. 5. https://doi.org/10.54590/pop.2023.004.
*Burton, Jason W., Ezequiel Lopez-Lopez, Shahar Hechtlinger, et al. 2024. “How Large Language Models Can Reshape Collective Intelligence.” ''Nature Human Behaviour'' 8 (9): 1643–55. https://doi.org/10.1038/s41562-024-01959-9.

==C==
*Carmi, Elinor, Simeon J. Yates, Eleanor Lockley, and Alicja Pawluczuk. 2020. “Data Citizenship: Rethinking Data Literacy in the Age of Disinformation, Misinformation, and Malinformation.” ''Internet Policy Review'' 9 (2). https://doi.org/10.14763/2020.2.1481.
*Carnegie Endowment for International Peace. 2024. “Beyond Open vs. Closed: Emerging Consensus and Key Questions for Foundation AI Model Governance (2024).” https://carnegieendowment.org/research/2024/07/beyond-open-vs-closed-emerging-consensus-and-key-questions-for-foundation-ai-model-governance?lang=en.
*Carroll, Stephanie Russo, Ibrahim Garba, Óscar Luis Figueroa Rodríguez, Jarita Holbrook, and Raymond Lovett. 2020. “The CARE Principles for Indigenous Data Governance.” ''Data Science Journal'' 19 (1): 43. https://doi.org/10.5334/dsj-2020-043.
*Carroll, Stephanie Russo, Edit Herczog, Māui Hudson, Keith Russell, and Shelley Stall. 2021. “Operationalizing the CARE and FAIR Principles for Indigenous Data Futures.” ''Scientific Data'' 8: 108. https://doi.org/10.1038/s41597-021-00892-0.
*Checco, Alessandro, Lorenzo Bracciale, Pierpaolo Loreti, Stephen Pinfield, and Giuseppe Bianchi. 2021. “AI-Assisted Peer Review.” ''Humanities and Social Sciences Communications'' 8: 25. https://doi.org/10.1057/s41599-020-00703-8.
*Cheong, Inyoung. 2024. “Collaborative Approaches to AI Governance: Exploring Co-Design and Co-Regulation Models.” PhD diss., University of Washington. https://homes.cs.washington.edu/\~yoshi/papers/theses/inyoung-cheong-dissertation.pdf.
*Chun, Jon, and Katherline Elkins. 2023. “The Crisis of Artificial Intelligence: A New Digital Humanities Curriculum for Human-Centred AI.” ''International Journal of Humanities and Arts Computing'' 17 (2): 147–167. https://doi.org/10.3366/ijhac.2023.0310.
*Chung, Hiu-Fung. 2025. “Betting on (Un)Certain Futures: Sociotechnical Imaginaries of AI and Varieties of Techno-Developmentalism in Asia.” ''Information, Communication &amp; Society'' 29 (3): 909–926. https://doi.org/10.1080/1369118X.2025.2535427.
*Colbert-Lewis, Danielle, Lawrence Maminta, Kelly McElroy, Graeme Slaght, and Mark Swartz. 2024. “The Citation Economy as a Site of Extraction for Surveillance Publishing.” ''Canadian Journal of Academic Librarianship'' 10 (December): 1–22. https://doi.org/10.33137/cjal-rcbu.v10.43293.
*Cooper, Martin. 2023. “Open Source Is Good for AI But, Is AI Good for Open Source?” ''ITNOW'' 65 (2): 50–51. https://doi.org/10.1093/combul/bwad062.
*Corsi, Giulio, Bill Marino, and Willow Wong. 2024. “The spread of synthetic media on X.” ''Harvard Kennedy School (HKS) Misinformation Review''. https://doi.org/10.37016/mr-2020-140.
*Crompton, Constance, Lori Antranikan, Ruth Truong, and Paige Maskell. 2020. “Familiar Wikidata: The Case for Building a Data Source We Can Trust.” ''Pop! Public. Open. Participatory'', no. 2. https://doi.org/10.48404/pop.2020.02.

==D==
*Daniel Delmonaco, Samuel Mayworm, Hibby Thach, Josh Guberman, Aurelia Augusta, and Oliver L. Haimson. 2024. “'What are you doing, TikTok?': How Marginalized Social Media Users Perceive, Theorize, and 'Prove' Shadowbanning.” Available at: https://oliverhaimson.com/PDFs/DelmonacoShadowbanning.pdf.
*Deng, Ruiqi, Maoli Jiang, Xinlu Yu, Yuyan Lu, and Shasha Liu. 2025. “Does ChatGPT Enhance Student Learning? A Systematic Review and Meta-Analysis of Experimental Studies.” ''Computers &amp; Education'' 227: 105224. https://doi.org/10.1016/j.compedu.2024.105224.
*Dennstädt, Fabio, Cedric Sivert Möller, Tim Fellerhoff, Felix Busch, Oke Gerke, André Karch, and Oliver Krause. 2024. “Title and Abstract Screening for Literature Reviews Using Large Language Models: An Exploratory Study in the Biomedical Domain.” ''Systematic Reviews'' 13 (1): 158. https://doi.org/10.1186/s13643-024-02575-4.
*Drolsbach, Chiara, and Nicolas Pröllochs. 2025. “Characterizing AI-Generated Misinformation on Social Media.” Preprint, ''arXiv'', May 15. https://doi.org/10.48550/arXiv.2505.10266.
*Duricic, Tomislav, Hussain Hussain, Emanuel Lacic, Dominik Kowald, Denis Helic, and Elisabeth Lex. 2023. “Beyond-Accuracy: A Review on Diversity, Serendipity, and Fairness in Recommender Systems Based on Graph Neural Networks.” ''Frontiers in Big Data'' 6: 1251072. https://doi.org/10.3389/fdata.2023.1251072.

==E==
*El Khatib, Randa, Lindsey Seatter, Tracey El Hajj, Conrad Leibel, Alyssa Arbuckle, Ray Siemens, Caroline Winter, and the ETCL and INKE Research Groups. 2019. “Open Social Scholarship Annotated Bibliography.” ''KULA: Knowledge Creation, Dissemination, and Preservation Studies'' 3 (1): 24. https://doi.org/10.5334/kula.58.
*Eloundou, Tyna, Sam Manning, Pamela Mishkin, and Daniel Rock. 2024. “GPTs are GPTs: Labor market impact potential of LLMs.” ''Science'' 384 (6698): 1306–1311. https://doi.org/10.1126/science.adj0998.

==F==
*Fırıncı, Yusuf. 2024. “Decolonial Artificial Intelligence; Algorithmic Fairness in Alignment with Turkish and Islamic Values.” ''Marmara Üniversitesi İlahiyat Fakültesi Dergisi'' 67 (67): 250–279. https://doi.org/10.15370/maruifd.1565884.
*Fanning, Katie, Claire Kim, and Jon Saklofske. 2023. “Interactive Inspirations: The Case for Incorporating Joy and Play in Open Social Scholarship.” ''Pop! Public. Open. Participatory'', no. 5. https://doi.org/10.54590/pop.2023.012.
*Floridi, Luciano. 2018. “Soft Ethics and the Governance of the Digital.” ''Philosophy &amp; Technology'' 31 (1): 1–8. https://doi.org/10.1007/s13347-018-0303-9.
*Frangou, Sophia, Umberto Volpe, and Andrea Fiorillo. 2025. “AI in scientific writing and publishing: A call for critical engagement.” ''European Psychiatry'' 68 (1): e98. https://doi.org/10.1192/j.eurpsy.2025.10061.

==G==
*Gallegos, Isabel O., Ryan A. Rossi, Joe Barrow, Md Mehrab Tanjim, Sungchul Kim, Franck Dernoncourt, Tong Yu, Ruiyi Zhang, and Nesreen K. Ahmed. 2024. “Bias and Fairness in Large Language Models: A Survey.” ''Computational Linguistics'' 50 (3): 1097–1179. https://doi.org/10.1162/coli_a_00524.
*Gasser, Urs, and Virgilio A. F. Almeida. 2017. “A Layered Model for AI Governance.” ''IEEE Internet Computing'' 21 (6): 58–62. https://doi.org/10.1109/MIC.2017.4180835.
*Goddard, Lisa. 2021. Persistent Identifiers as Open Research Infrastructure to Reduce Administrative Burden. ''Pop! Public. Open. Participatory'', no. 3. https://doi.org/10.54590/pop.2021.006.
*Gorwa, Robert, Reuben Binns, and Christian Katzenbach. 2020. “Algorithmic Content Moderation: Technical and Political Challenges in the Automation of Platform Governance.” ''Big Data &amp; Society'' 7 (1): 1–15. https://doi.org/10.1177/2053951719897945.
*Graßhoff, Gerd. 2025. “AI-Reporter: A Path to a New Genre of Scientific Communication.” Preprint, ''arXiv'', July 8. https://arxiv.org/abs/2507.05903.
*Grigoli, Leland Renato. 2023. “Ghosts in the Machine.” ''American Historical Association'' 61 (3). https://www.historians.org/wp-content/uploads/2024/07/Perspectives\_61N3.pdf.
*Gruzd, Anatoliy, Philip Mai, and Anthony Clements Haines. 2025. ''The State of Generative AI Use in Canada 2025: Exploring Public Attitudes and Adoption Trends''. Toronto: Social Media Lab, Toronto Metropolitan University. https://figshare.com/articles/preprint/The_State_of_Generative_AI_Use_in_Canada_2025_Exploring_Public_Attitudes_and_Adoption_Trends/28664780/1The\_State\_of\_Generative\_AI\_Use\_in\_Canada\_2025\_Exploring\_Public\_Attitudes\_and\_Adoption\_Trends/28664780/1.
*Gulson, Kalervo N., and P. Taylor Webb. 2023. “Steering the Mind Share: Technology Companies, Policy and Artificial Intelligence Research in Universities.” ''Discourse: Studies in the Cultural Politics of Education'' 44 (2): 195–207. https://doi.org/10.1080/01596306.2021.1981828.
*Gundersen, Odd Erik, Odd Cappelen, Martin Mølnå, and Nicklas Grimstad Nilsen. 2024. “The Unreasonable Effectiveness of Open Science in AI: A Replication Study.” Preprint, ''arXiv'', December 20. https://doi.org/10.48550/ARXIV.2412.17859.
*Guo, Xinwei, Yujun Li, Yafeng Peng, and Xuetao Wei. 2024. “Copyleft for Alleviating AIGC Copyright Dilemma: What-if Analysis, Public Perception and Implications.” Preprint, ''arXiv'', February 19. https://arxiv.org/abs/2402.12216.

==H==
*Hadley, Emma, Alan Blatecky, and Megan Comfort. 2025. “Investigating Algorithm Review Boards for Organizational Responsible Artificial Intelligence Governance.” ''AI and Ethics'' 5: 2485–2495. https://doi.org/10.1007/s43681-024-00574-8.
*Hara, Noriko, Eugene Kim, Shohana Akter, and Kunihiro Miyazaki. 2025. “Exploring the Dynamics of Interaction About Generative Artificial Intelligence Between Experts and the Public on Social Media.” ''Journal of Science Communication'' 24 (1): A02. https://doi.org/10.22323/2.24010202.
*Heger, Amy, Liz B. Marquis, Mihaela Vorvoreanu, Hanna Wallach, and Jennifer Wortman Vaughan. 2022. “Understanding Machine Learning Practitioners' Data Documentation Perceptions, Needs, Challenges, and Desiderata.” ''Proceedings of the ACM on Human-Computer Interaction'' 6 (CSCW2): 1–29. https://doi.org/10.1145/3555760.
*Helregel, Nicole. 2025. “AI and Open Science: Implications and Library Practice Recommendations.” ''Library Trends'' 73 (3). https://doi.org/10.1353/lib.2025.a961191.
*Hertweck, Corinna, Joachim Baumann, Michele Loi, Eleonora Viganò, and Christoph Heitz. 2022. “A Justice-Based Framework for the Analysis of Algorithmic Fairness-Utility Trade-Offs.” Preprint, ''arXiv'', June 6. https://arxiv.org/abs/2206.02891.
*Hosseini, Mohammad, Serge P. J. M. Horbach, Kristi Holmes, and Tony Ross-Hellauer. 2025. “Open Science at the generative AI turn: An exploratory analysis of challenges and opportunities.” ''Quantitative Science Studies'' 6: 22–45. https://doi.org/10.1162/qss_a_00337.
*Hosseini, Mohammad, and Serge P. J. M. Horbach. 2023. “Fighting Reviewer Fatigue or Amplifying Bias? Considerations and Recommendations for Use of ChatGPT and Other Large Language Models in Scholarly Peer Review.” ''Research Integrity and Peer Review'' 8 (1): 15. https://doi.org/10.21203/rs.3.rs-2587766/v1.
*Huerta, E. A., Ben Blaiszik, L. Catherine Brinson, Kristofer E. Bouchard, and D. Díaz, et al. 2023. “FAIR for AI: An Interdisciplinary and International Community Building Perspective.” ''Scientific Data'' 10: 487. https://doi.org/10.1038/s41597-023-02298-6.

==J==
*Jaillant, Lise, Olivia Mitchell, Eric Ewoh-Opu, and Maribel Hidalgo Urbaneja. 2025. “How Can We Improve the Diversity of Archival Collections with AI? Opportunities, Risks, and Solutions.” ''AI &amp; Society'' 40: 4447–4459. https://doi.org/10.1007/s00146-025-02222-z.
*Janssen, Marijn. 2025. “Responsible Governance of Generative AI: Conceptualizing GenAI as Complex Adaptive Systems.” ''Policy and Society'' 44 (1): 38–51. https://doi.org/10.1093/polsoc/puae040.
*Jarrahi, Mohammad Hossein, Gemma Newlands, Min Kyung Lee, Christine T. Wolf, Eliscia Kinder, and Will Sutherland. 2021. “Algorithmic management in a work context.” ''Big Data &amp; Society'' 8 (2): 20539517211020332. https://doi.org/10.1177/20539517211020332.
*Jensen, Graham. 2023. &quot;Digital Knowledge Commons, Scholarly Connection, and the Evolution of Open Scholarship.&quot; In ''Open Scholarship Press Curated Volumes: Connection''. https://doi.org/10.21428/47bc126e.0ca461a4.
*Jensen, Graham, Alyssa Arbuckle, Caroline Winter, Talya Jesperson, Tyler Fontenot, Ray Siemens, and the ETCL and INKE Research Groups. 2022. “Fostering Digital Communities of Care: Safety, Security, and Trust in the Canadian HSS Commons.“ ''IDEAH'' 3 (2). https://ideah.pubpub.org/pub/h7927ugt.
*Jiang, Jialei. 2024. “When generative artificial intelligence meets multimodal composition: Rethinking the composition process through an AI-assisted design project.” ''Computers and Composition'' 74: 102883. https://doi.org/10.1016/j.compcom.2024.102883.
*Jones, Matthew L. 2023. “AI in History.” ''The American Historical Review'' 128 (3): 1360–67. https://doi.org/10.1093/ahr/rhad361.

==K==
*Kay, Jackie, Atoosa Kasirzadeh, and Shakir Mohamed. 2024. “Epistemic Injustice in Generative AI.” Preprint, ''arXiv'', August 21. https://doi.org/10.48550/arXiv.2408.11441.
*Kember, Sarah, and Amy Brand. 2023. “The Corporate Capture of Open-Access Publishing.” ''The Chronicle of Higher Education'', August 16. https://www.chronicle.com/article/the-corporate-capture-of-open-access-publishing.
*Kirschenbaum, Matthew. 2025. “The US of AI.” Public Draft, February 25, 2025. https://drive.google.com/file/d/1O2qkjhg7Ei5zZWmBraNwXq4V0lTauspN/view.
*Klein, Laura, Meredith Martin, André Brock, Maria Antoniak, Melanie Walsh, Jessica Marie Johnson, Lauren Tilton, and David Mimno. 2025. Provocations from the Humanities for Generative AI Research. Preprint, ''arXiv'', February 26. https://arxiv.org/abs/2502.19190.
*Klein, Lauren, and Catherine D'Ignazio. 2024. “Data feminism for AI.” In ''Proceedings of the 2024 ACM Conference on Fairness, Accountability, and Transparency'': 100–112. https://doi.org/10.1145/3630106.3658543.
*Kousha, Kayvan, and Mike Thelwall. 2024. “Artificial Intelligence to Support Publishing and Peer Review: A Summary and Review.” ''Learned Publishing'' 37 (1): 4–12. https://doi.org/10.1002/leap.1570.

==L==
*Lee, Daniel, and Edward Palmer. 2025. “Prompt Engineering in Higher Education: A Systematic Review to Help Inform Curricula.” ''International Journal of Educational Technology in Higher Education'' 22: 16. https://doi.org/10.1186/s41239-025-00503-7.
*Lewis, Jason Edward, Noelani Arista, Archer Pechawis, and Suzanne Kite. 2018. “Making Kin with the Machines.” ''Journal of Design and Science'', ahead of print, July 16. https://doi.org/10.21428/bfafd97b.
*Lim, Gim Hui, M. L. Tan, V. C. W. Hoe, and D. Koh. 2025. “Generative AI in Peer Review Process for Occupational Health.” ''Occupational Medicine'' 75 (5): 242–49. https://doi.org/10.1093/occmed/kqaf051.
*Linåker, Johan, Cailean Osborne, Jennifer Ding, Daniel Puttick, and Richard Nweibo. 2025. “A Cartography of Open Collaboration in Open Source AI: Mapping Practices, Motivations, and Governance in 14 Open Large Language Model Projects.” Preprint, ''arXiv'', September 29. https://arxiv.org/abs/2509.25397.
*Long, Duri, and Brian Magerko. 2020. “What is AI Literacy? Competencies and Design Considerations.” In ''Proceedings of the 2020 CHI Conference on Human Factors in Computing Systems'', 1–13. New York, NY: Association for Computing Machinery. https://doi.org/10.1145/3313831.3376727.
*Luth, Eric. 2025. “The Use of Wikipedia, Wikimedia, and Open Access Content for Artificial Intelligence and Text and Data Mining.” ''Stockholm IP Law Review'' 6 (1): 109–138. https://doi.org/10.53292/33313cc8.be33e111.

==M==
*Ma, Lai. 2024. “Generative AI for Academic Publishing? Some Thoughts About Epistemic Diversity and the Pursuit of Truth.” ''KULA: Knowledge Creation, Dissemination, and Preservation Studies'' 7 (1): 1–5. https://doi.org/10.18357/kula.287.
*Mai, Dang Thi Thuy, Cuong Van Da, and Nguyen Van Hanh. 2024. “The Use of ChatGPT in Teaching and Learning: A Systematic Review through SWOT Analysis Approach.” ''Frontiers in Education'' 9: 1328769. https://doi.org/10.3389/feduc.2024.1328769.
*Mao, Yishu, Vanessa Richter, and Christian Katzenbach. (2025). &quot;Strategising imaginaries: How corporate actors in China, Germany and the US shape AI governance.&quot; ''Big Data &amp; Society'' 12 (1). https://doi.org/10.1177/20539517251400727.
*Majdik, Zoltan P., and S. Scott Graham. 2024. “Rhetoric of/with AI: An Introduction.” ''Rhetoric Society Quarterly'' 54 (3): 222–31. https://doi.org/10.1080/02773945.2024.2343264.
*Maxwell, J. W. (2015). Beyond Open Access to Open Publication and Open Scholarship. ''Scholarly and Research Communication'', 6 (3), 1–10. https://doi.org/10.22230/src.2015v6n3a202.
*McIntosh, Timothy R., Teo Susnjak, Tong Liu, Paul Watters, and Malka N. Halgamuge. 2023. “From Google Gemini to OpenAI Q (Q-Star): A Survey of Reshaping the Generative Artificial Intelligence (AI) Research Landscape.” ''Technologies''. https://doi.org/10.3390/technologies13020051.
*Mehlenbacher, Brad, Ana Patricia Balbon, and Ashley Rose Mehlenbacher. 2024. “Synthetic Genres: Expert Genres, Non-Specialist Audiences, and Misinformation in the Artificial Intelligence Age.” ''Journal of Technical Writing and Communication'', January 31, 00472816231226249. https://doi.org/10.1177/00472816231226249.
*Meneses, Luis. 2020. “Integrating the Social Media Engine with Large-scale Open Access Repositories: A Discussion.” ''Pop! Public. Open. Participatory'', no. 2. https://doi.org/10.54590/pop.2020.004. 
*Mitchell, Peta, Michelle Riedlinger, Jake Goldenfein, Aaron Snoswell, Jean Burgess, and Kevin Witzenberger. 2025. “RESEARCH GENAI: SITUATING GENERATIVE AI IN THE SCHOLARLY ECONOMY.” ''AoIR Selected Papers of Internet Research'', January. https://doi.org/10.5210/spir.v2024i0.14006.
*Mitra, Bhaskar, Henriette Cramer, and Olya Gurevich. 2024. “Sociotechnical Implications of Generative Artificial Intelligence for Information Access.” Preprint, ''arXiv'', May 19. https://doi.org/10.48550/arXiv.2405.11612.
*Mohamed, Shakir, Marie-Therese Png, and William Isaac. 2020. “Decolonial AI: Decolonial Theory as Sociotechnical Foresight in Artificial Intelligence.” ''Philosophy &amp; Technology'' 33 (4): 659–84. https://doi.org/10.1007/s13347-020-00405-8.
*Montague-Hellen, Beth. 2024. “Empowering Knowledge through AI: Open Scholarship Proactively Supporting Well Trained Generative AI.” ''Insights'' 37 (1). https://doi.org/10.1629/uksg.649.
*Mugaanyi, Joseph, Christoph Lehner, and Lia M. Bally. 2024. “Evaluation of Large Language Model Performance and Reliability for Citation Generation Across Scientific Disciplines.” ''Journal of Medical Internet Research'' 26: e52935. https://doi.org/10.2196/52935.
*Muldoon, James, and Boxi A Wu. 2023. “Artificial Intelligence in the Colonial Matrix of Power.” ''Philosophy &amp; Technology'' 36 (4). https://doi.org/10.1007/s13347-023-00687-8.

==N==
*Nelson, Brent, Miguel Dela Pena, Prototyping the Digital Archive Team, and the INKE Research Group. 2023. “No Journal is an Island: The John Donne Journal and the Possibilities of Open Access.” ''Pop! Public. Open. Participatory'', no. 5. https://doi.org/10.54590/pop.2023.007.
*Ng, Davy Tsz Kit, Jac Ka Lok Leung, Samuel Kai Wah Chu, and Maggie Shen Qiao. 2021. “Conceptualizing AI Literacy: An Exploratory Review.” ''Computers and Education: Artificial Intelligence'' 2: 100041. https://doi.org/10.1016/j.caeai.2021.100041 .
*Ngulube, Patrick, and Neema Florence Vincent Mosha. 2024. “Integrating artificial intelligence-based technologies ‘safely’ in academic libraries: An overview through a scoping review.” ''Technical Services Quarterly'' 42 (1): 46–67. https://doi.org/10.1080/07317131.2024.2432093.

==O==
*Oates, A., and D. Johnson. 2025. “ChatGPT in the Classroom: Evaluating Its Role in Fostering Critical Evaluation Skills.” ''International Journal of Artificial Intelligence in Education'' 35 (4): 1793-1824. https://doi.org/10.1007/s40593-024-00452-8.
*Oh, Dayei, and John Downey. 2024. “Does Algorithmic Content Moderation Promote Democratic Discourse? Radical Democratic Critique of Toxic Language AI.” ''Information, Communication &amp; Society'' 28 (7): 1157–76. https://doi.org/10.1080/1369118X.2024.2346531.
*Ohagi, Masaya. 2024. “Polarization of Autonomous Generative AI Agents Under Echo Chambers.” Preprint, ''arXiv'' February 19. https://arxiv.org/abs/2402.12212.
*Open Source Initiative. The Open Source AI Definition 1.0 (2024–2025). https://opensource.org/ai.
*Osborne, Cailean. 2024. “Why Companies 'Democratise' Artificial Intelligence: The Case of Open Source Software Donations.” Preprint, ''arXiv'', September 26. https://doi.org/10.48550/ARXIV.2409.17876.

==P==
*Papagiannidis, Emmanouil, Patrick Mikalef, and Kieran Conboy. 2025. “Responsible Artificial Intelligence Governance: A Review and Research Framework.” ''The Journal of Strategic Information Systems'' 34 (2): 101885. https://doi.org/10.1016/j.jsis.2024.101885.
*Papi, Sara, Marco Gaido, Luisa Bentivogli, and Matteo Negri. 2025. “FAMA: The First Large-Scale Open-Science Speech Foundation Model for English and Italian.” Preprint, ''arXiv'', May 28. https://arxiv.org/abs/2505.22759.
*Park, Seyeon, and Xiaoli Nan. 2025. “Generative AI and misinformation: a scoping review of the role of generative AI in the generation, detection, mitigation, and impact of misinformation.” ''AI &amp; Society'' 41: 1501–1515. https://doi.org/10.1007/s00146-025-02620-3.
*Peters, Uwe, and Benjamin Chin-Yee. 2025. “Generalization Bias in Large Language Model Summarization of Scientific Research.” ''Royal Society Open Science'' 12 (4): 241776. https://doi.org/10.1098/rsos.241776.
*Pividori, Milton, and Casey S. Greene. 2024. “A Publishing Infrastructure for Artificial Intelligence (AI)-Assisted Academic Authoring.” ''Journal of the American Medical Informatics Association'' 31 (9): 2103–13 https://doi.org/10.1093/jamia/ocae139.
*Pooley, Jefferson. 2024. “Large Language Publishing: The Scholarly Publishing Oligopoly's Bet on AI.” ''KULA: Knowledge Creation, Dissemination, and Preservation Studies'' 7 (1): 1–11. https://doi.org/10.18357/kula.291.
*Pope, Andrew, and Rongqian Ma. 2024. “Exploring Historians’ Critical Use of Generative AI Technologies for History Education.” ''Proceedings of the Association for Information Science and Technology'' 61 (1): 1071–73. https://doi.org/10.1002/pra2.1188.
*Prescott, Andrew. 2023. “Bias in Big Data, Machine Learning and AI: What Lessons for the Digital Humanities?” ''Digital Humanities Quarterly'' 17 (2). https://www.proquest.com/scholarly-journals/bias-big-data-machine-learning-ai-what-lessons/docview/2842908427/se-2.

==Q==
*Qi, Weihong, Jinsheng Pan, Hanjia Lyu, and Jiebo Luo. 2024. “Excitements and concerns in the post-ChatGPT era: Deciphering public perception of AI through social media analysis.” ''Telematics and Informatics'' 92: 102158. https://doi.org/10.1016/j.tele.2024.102158.

==R==
*Radu, Roxana. 2021. “Steering the Governance of Artificial Intelligence: National Strategies in Perspective.” ''Policy and Society'' 40 (2): 178–193. https://doi.org/10.1080/14494035.2021.1929728.
*Rapanta, Chrysi, Anna Åkerfeldt, Mark Vanderbeeken, Diane Lison, Khadija Mohammed, Amanda Gibbs, Helder Coelho, Pinar Seda Celik, Carola Bruna, Ingrid Helleve, Chrysoula Vassilakopoulou, Pieter Swart, Ana Lúcia Marques, and Dirk Ifenthaler. 2025. “Critical GenAI Literacy: Postdigital Configurations.” ''Postdigital Science and Education'' 17 (1): 167–199. https://doi.org/10.1007/s42438-025-00573-w.
*Razack, Habib Ibrahim Abdul, Sam T. Mathew, Fathinul Fikri Ahmad Saad, and Saleh A. Alqahtani. 2021. “Artificial intelligence-assisted tools for redefining the communication landscape of the scholarly world.” ''Science Editing'' 8 (2): 134–144. https://doi.org/10.6087/kcse.244.
*Reynolds, CJ, and Blake Hallinan. 2024. “User-Generated Accountability: Public Participation in Algorithmic Governance on YouTube.” ''New Media &amp; Society'' 26 (9): 5107–5129. https://doi.org/10.1177/14614448241251791.
*Risam, Roopika. “What Passes for Human?: Undermining the Universal Subject in Digital Humanities Praxis.” In Bodies of Information: Intersectional Feminism and the Digital Humanities, edited by Elizabeth Losh and Jacqueline Wernimont, 39–56. ''University of Minnesota Press'', 2018. https://doi.org/10.5749/j.ctv9hj9r9.6.
*Rockwell, G., Land, K., &amp; MacDonald, A. 2021. Social Analytics Through Spyral. ''Pop! Public. Open. Participatory,'' no. 3. https://doi.org/10.54590/pop.2021.004.
*Rughiniș, Cosima, et al. 2025. “AI at the Knowledge Gates: Institutional Policies and Hybrid Configurations in Universities and Publishers.” ''Frontiers in Computer Science'' 7: 1608276. https://doi.org/10.3389/fcomp.2025.1608276.

==S==
*Salami, Aishat Oyenike. 2024. “Artificial intelligence, digital colonialism, and the implications for Africa's future development.” ''Data &amp; Policy'' 6. https://doi.org/10.1017/dap.2024.75.
*Sartori, L., and A. Theodorou. 2022. A sociotechnical perspective for the future of AI: narratives, inequalities, and human control. ''Ethics and Information Technology'' 24 (1): 4. https://doi.org/10.1007/s10676-022-09624-3.
*Savolainen, Lotta. 2022. “The Shadow Banning Controversy: Perceived Governance and Algorithmic Folklore.” Media, Culture &amp; Society 44 (6): 1091–1109. https://doi.org/10.1177/01634437221077174.
*Shcherbiak, Anna, Hooman Habibnia, Robert Böhm, and Susann Fiedler. “Evaluating Science: A Comparison of Human and AI Reviewers.” ''Judgment and Decision Making'' 19 (2024): e21. https://doi.org/10.1017/jdm.2024.24.
*Schmit, Cason, M. J. Doerr, and J. K. Wagner. 2023. “Leveraging IP for AI Governance.” ''Science'' 379 (6633): 646–647. https://doi.org/10.1126/science.add2202.
*Schroeder, Hope, Marianne Aubin Le Quéré, Casey Randazzo, David Mimno, and Sarita Schoenebeck. 2024. “Large Language Models in Qualitative Research: Uses, Tensions, and Intentions.” Preprint, ''arXiv'', October 9. https://arxiv.org/abs/2410.07362.
*Seger et al. “Democratising AI: Multiple Meanings, Goals, and Methods.” ''Proceedings of the 2023 AAAI/ACM Conference on AI, Ethics, and Society''. https://dl.acm.org/doi/10.1145/3600211.3604693.
*Shams, Rifat Ara, Didar Zowghi, and Muneera Bano. 2023. “AI and the Quest for Diversity and Inclusion: A Systematic Literature Review.” ''AI and Ethics'' 3 (4): 1427–1453. https://doi.org/10.1007/s43681-023-00362-w.
*Shanklin, Grant, Emmie Hine, Claudio Novelli, Tyler Schroder, and Luciano Floridi. 2025. “The Case for Contextual Copyleft: Licensing Open Source Training Data and Generative AI.” Preprint, ''arXiv'', July 17. https://arxiv.org/abs/2507.12713.
*Shin, Donghee, Amy Koerber, and Joon Soo Lim. 2024. “Impact of misinformation from generative AI on user information processing: How people understand misinformation from generative AI.” ''New Media &amp; Society'' 27 (7): 4017–4047. https://doi.org/10.1177/14614448241234040.
*Sidorkin, Alexander. 2025. “Environmental Impact of Generative AI: Carbon and Water Footprint.” ''AI-EDU Arxiv'' 1. https://doi.org/10.36851/ai-edu.vi.5448.
*Siemens, Lynne, and the INKE Research Group. 2023. I Stayed for the Community: Collaboration and Community in an Open Social Scholarship Research Project. ''Pop! Public. Open. Participatory'', no. 5. https://doi.org/10.54590/pop.2023.013.
*da Silva Cardoso, Heike, and Vitor Rocio. (2025). &quot;Enhancing Digital Libraries Through NLP and Recommender Systems: Current Trends and Future Prospects with Large Language Models.&quot; In ''Technology and Innovation in Learning, Teaching and Education (TECH-EDU 2024)''. Communications in Computer and Information Science, vol. 2480, 69–79. Springer, Cham. https://doi.org/10.1007/978-3-032-02672-9_5. 
*Simon, Judith. 2025. “Generative AI, Quadruple Deception &amp; Trust.” ''Social Epistemology''. https://doi.org/10.1080/02691728.2025.2491087.
*Smith, Regan. 2025. “Licensing of Text for Generative AI: Learnings from Non-AI Licensing Practices.” ''The Columbia Journal of Law &amp; the Arts'' 48 (4): 457–512. https://doi.org/10.52214/jla.v48i4.13926.
*Spatharioti, Sofia Eleni, David Rothschild, Daniel G. Goldstein, and Jake M. Hofman. 2025. “Effects of LLM-based Search on Decision Making: Speed, Accuracy, and Overreliance.” ''Proceedings of the 2025 CHI Conference on Human Factors in Computing Systems''. https://doi.org/10.1145/3706598.3714082.
*Sposato, Martin. 2025. “Artificial Intelligence in Educational Leadership: A Comprehensive Taxonomy and Future Directions.” ''International Journal of Educational Technology in Higher Education'' 22 (20). https://doi.org/10.1186/s41239-025-00517-1.
*Starke, Christopher, Janine Baleis, Birte Keller, and Frank Marcinkowski. 2022. “Fairness Perceptions of Algorithmic Decision-Making: A Systematic Review of the Empirical Literature.” ''Big Data &amp; Society'' 9 (2): 1–35. https://doi.org/10.1177/20539517221115189.
*Strubell, Emma, Ananya Ganesh, and Andrew McCallum. 2019. “Energy and Policy Considerations for Deep Learning in NLP.” ''Proceedings of the 57th Annual Meeting of the Association for Computational Linguistics'', 3645–3650. https://doi.org/10.18653/v1/p19-1355.
*Sun, Zhuanlan. 2025. “Large Language Models in Peer Review: Challenges and Opportunities.” ''Scientometrics'' 130 (10): 5503-5546. https://doi.org/10.1007/s11192-025-05440-w.
*Sutherland, Tonia, Marika Cifor, T. L. Cowan, Jas Rault, and Patricia Garcia. 2023. “The Feminist Data Manifest-NO: An Introduction and Four Reflections.” In ''Debates in the Digital Humanities'', edited by Lauren F. Klein and Matthew K. Gold. Minneapolis, MN: University of Minnesota Press. https://dhdebates.gc.cuny.edu/read/debates-in-the-digital-humanities-2023/section/16184c7d-eee1-40b2-a168-960d4c4035c4.

==T==
*Taeihagh, Araz. 2025. “Governance of Generative AI.” ''Policy and Society'' 44 (1): 1–14. https://doi.org/10.1093/polsoc/puaf001.
*Tan, Myles Joshua Toledo, and NMAT Maravilla. 2024. “Shaping Integrity: Why Generative Artificial Intelligence Does Not Have to Undermine Education.” ''Frontiers in Artificial Intelligence'' 7: 1471224. https://doi.org/10.3389/frai.2024.1471224.
*Taneja, Ankit Kumar, and Chandra Tripathi. 2020. “AI-Powered Recommender Systems: Personalization and Bias.” ''Turkish Journal of Computer and Mathematics Education (TURCOMAT)'' 11 (1): 1090–1094. https://doi.org/10.61841/turcomat.v11i1.14406.
*Taylor, Randon R., Bessie O'Dell, and John W. Murphy. 2023. “Human-centric AI: philosophical and community-centric considerations.” ''AI &amp; Society'' 39 (5): 2417–2424. https://doi.org/10.1007/s00146-023-01694-1.
*Ter-Minassian, Lucile. 2025. “Democratizing AI Governance: Balancing Expertise and Public Participation.” Preprint, ''arXiv'' January 16. https://doi.org/10.48550/arXiv.2502.08651.
*Tumadóttir, Anna. 2024. “Questions for Consideration on AI &amp; the Commons.” ''Creative Commons'', July 24. https://creativecommons.org/2024/07/24/preferencesignals/.
*Turin, Mark. 2021. “From Orality to Open: Innovations in Multimedia Monograph Publishing in the Humanities.” ''Pop! Public. Open. Participatory'', no. 3. https://doi.org/10.54590/pop.2021.005.

==V==
*Vake, Domen, Bogdan Šinik, Jernej Vičič, and Aleksander Tošić. 2025. &quot;Is Open Source the Future of AI? A Data‑Driven Approach.&quot; Preprint, ''arXiv'', January 27. https://arxiv.org/abs/2501.16403.
*van Es, Karin and Dennis Nguyen. 2024. “‘Your friendly AI assistant’: the anthropomorphic self-representations of ChatGPT and its implications for imagining AI.” ''AI &amp; Society'' 40: 3591–3603. https://doi.org/10.1007/s00146-024-02108-6.
*Varshney, Kush R. 2024. “Decolonial AI Alignment: Openness, Visesa-Dharma, and Including Excluded Knowledges.” ''Proceedings of the AAAI/ACM Conference on AI, Ethics, and Society'' 7: 1467–1481. https://doi.org/10.1609/aies.v7i1.31739.
*Veldhuis, Annemiek M., Phoebe W. K. Lo, Iain E. G. Kenny, and Alissa N. Antle. 2024. “Critical Artificial Intelligence literacy: A scoping review and framework synthesis.” ''International Journal of Child-Computer Interaction'' 43: 100708. https://doi.org/10.1016/j.ijcci.2024.100708.
*Vetter, Matthew A., Jialei Jiang, and Zachary J. McDowell. 2025. “An Endangered Species: How LLMs Threaten Wikipedia’s Sustainability.” ''AI &amp; Society'', February. https://doi.org/10.1007/s00146-025-02199-9.

==W==
*Weber, Michael, Martin Engert, Norman Schaffer, Jörg Weking, and Helmut Krcmar. 2023. “Organizational Capabilities for AI Implementation—Coping with Inscrutability and Data Dependency in AI.” ''Information Systems Frontiers'' 25: 1549–1569. https://doi.org/10.1007/s10796-022-10297-y.
*Werder, Karl, Balasubramaniam Ramesh, and Rongen (Sophia) Zhang. 2022. “Establishing Data Provenance for Responsible Artificial Intelligence Systems.” ''ACM Transactions on Management Information Systems'' 13 (4): 1–25. https://doi.org/10.1145/3503488.
*Whalen, Zach. 2023. “‘Any Means Necessary to Refuse Erasure by Algorithm:’ Lillian-Yvonne Bertram’s Travesty Generator.” ''DHQ: Digital Humanities Quarterly'' 17 (2). https://www.digitalhumanities.org/dhq/vol/17/2/000707/000707.html.
*White, Matt, Ibrahim Haddad, Cailean Osborne, Xiao-Yang Liu, Ahmed Abdelmonsef, Sachin Varghese, and Arnaud Le Hors. 2024. “The Model Openness Framework: Promoting Completeness and Openness for Reproducibility, Transparency, and Usability in AI.” Preprint, ''arXiv'', March 20. https://doi.org/10.48550/arXiv.2403.13784.
*Whiteley, Paul. 2023. “Why Artificial Intelligence Is a Misnomer.” ''London School of Economics and Political Science Politics and Policy Blog'', October 19. https://blogs.lse.ac.uk/politicsandpolicy/why-artificial-intelligence-is-a-misnomer/.
*Widder, David Gray, Dawn Nafus, Laura Dabbish, and James Herbsleb. 2022. “Limits and possibilities for ‘ethical AI’ in open source: A study of deepfakes.” In ''Proceedings of the 2022 ACM Conference on Fairness, Accountability, and Transparency (FAccT '22)'', 2035–2046. Association for Computing Machinery. https://doi.org/10.1145/3531146.3533779.
*Winkel, Marek. 2024. “Controlling the Uncontrollable: The Public Discourse on Artificial Intelligence between the Positions of Social and Technological Determinism.” ''AI &amp; Society'' 39 (5): 2449–2462. https://doi.org/10.1007/s00146-024-01979-z.
*Winter, Caroline. 2023. “Introduction: Open Scholarship Policy in Focus.” In ''Open Scholarship Press Curated Volume: Policy''. https://doi.org/10.21428/47bc126e.5abba88b.
*Winter, Caroline, Tyler Fontenot, Luis Meneses, Alyssa Arbuckle, Ray Siemens, and the ETCL and INKE Research Groups. 2020. Foundations for the Canadian HSS Commons: Exploring the Possibilities of Digital Research Communities. ''Pop! Public. Open. Participatory'', no. 2. https://doi.org/10.48404/pop.2020.05.
*de Winter, Joost. 2024. “Can ChatGPT be used to predict citation counts, readership, and social media interaction? An exploration among 2222 scientific abstracts.” ''Scientometrics'' 129: 2469–2487. https://doi.org/10.1007/s11192-024-04939-y.
*Wu, Chuhao, He Zhang, and John M. Carroll. 2024. “AI Governance in Higher Education: Case Studies of Guidance at Big Ten Universities.” Preprint, ''arXiv'', September 3. https://doi.org/10.48550/arXiv.2409.02017.

==X==
*Xie, Yu, and Sofia Avila. 2025. “The social impact of generative LLM-based AI.” ''Chinese Journal of Sociology'' 11 (1): 31–57. https://doi.org/10.1177/2057150X251315997.

==Y==
*Yim, Iris Heung Yue, and Jiahong Su. 2025. “Artificial Intelligence (AI) Learning Tools in K-12 Education: A Scoping Review.” ''British Journal of Educational Technology'' 56 (1): 169–196. https://doi.org/10.1007/s40692-023-00304-9.
*Yue, Yongjie, Maosong Zheng, Jiahui Liu, Zhimin Wang, and Chenhui Mao. 2025. “A Practical Guide and Assessment on Using ChatGPT to Conduct Grounded Theory Studies: Step-by-Step Reporting of the Data Analysis Process.” ''Journal of Medical Internet Research'' 27: e70122. https://doi.org/10.2196/70122.

==Z==
*Zeffiro, A. 2024. “Automating (In)securities: Cybersecurity’s AI Imaginaries.” Paper presented at EASST/4S, 2024. https://nomadit.co.uk/conference/easst-4s2024/p/14156.
*Zhu, Wenhao, Hongyi Liu, Qingxiu Dong, Jingjing Xu, Shujian Huang, Lingpeng Kong, Jiajun Chen, and Lei Li. 2023. “Multilingual Machine Translation with Large Language Models: Empirical Results and Analysis.” Preprint, ''arXiv'' April 10. https://arxiv.org/abs/2304.04675.

{{Navigation|previous=AI and Scholarship}}

{{BookCat}}</text>
      <sha1>6ogdg3sninbatr3zs9wgrc3zowj36tz</sha1>
    </revision>
    <revision>
      <id>4656118</id>
      <parentid>4656117</parentid>
      <timestamp>2026-08-02T21:29:53Z</timestamp>
      <contributor>
        <username>CorreiaA</username>
        <id>3614427</id>
      </contributor>
      <minor />
      <origin>4656118</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="45569" sha1="os61cq3npdotus8p7lir4ipe5s0tuma" xml:space="preserve">{{CompactTOC8|center=yes|i=I|u=U}}

==A==
*Ación, Laura, Mariela Rajngewerc, Gregory Randall, and Lorena Etcheverry. 2023. “Generative AI Poses Ethical Challenges for Open Science.” ''Nature Human Behaviour'' 7 (11): 1800–1801. https://doi.org/10.1038/s41562-023-01740-4.
*Adewumi, Tosin, Lama Alkhaled, Claudia Buck, Sergio Hernandez, Saga Brilioth, Mkpe Kekung, Yelvin Ragimov, and Elisa Barney. 2024. “ProCoT: Stimulating Critical Thinking and Writing of Students through Engagement with Large Language Models (LLMs).” Preprint, ''arXiv'', May 1. https://doi.org/10.48550/arXiv.2312.09801.
*Aguiar, Micaela, and Sílvia Araújo. 2024. “Final Thoughts: Digital Humanities Looking at Generative AI.” In ''Digital Humanities Looking at the World'', edited by S. Araújo et al., 367–380. Cham: Springer Nature Switzerland.
*Akter, Shahriar, Grace McCarthy, Shahriar Sajib, Katina Michael, Yogesh K. Dwivedi, John D’Ambra, and K.N. Shen. 2021. “Algorithmic bias in data-driven innovation in the age of AI.” ''International Journal of Information Management'' 60, 102387. https://doi.org/10.1016/j.ijinfomgt.2021.102387.
*Ali, Syed Mustafa, Stephanie Dick, Sarah Dillon, Matthew L. Jones, Jonnie Penn, and Richard Staley. 2023. “Histories of Artificial Intelligence: A Genealogy of Power.” ''BJHS Themes'' 8: 1–18. https://doi.org/10.1017/bjt.2023.15.
*Al-kfairy, Mousa, Dheya Mustafa, Nir Kshetri, Mazen Insiew, and Omar Alfandi. 2024. “Ethical Challenges and Solutions of Generative AI: An Interdisciplinary Perspective.” ''Informatics'' 11 (3): 58. https://doi.org/10.3390/informatics11030058.
*Alvarez, Jose M., Alejandra Bringas Colmenarejo, Alaa Elobaid, Simone Fabbrizzi, Miriam Fahimi, Antonio Ferrara, Siamak Ghodsi, et al. 2024. “Policy Advice and Best Practices on Bias and Fairness in AI.” ''Ethics and Information Technology'' 26 (2). https://doi.org/10.1007/s10676-024-09746-w.
*Anderson, Marc M. 2024. “AI as Philosophical Ideology: A Critical Look Back at John McCarthy’s Program.” ''Philosophy &amp; Technology'' 37 (2): 44. https://doi.org/10.1007/s13347-024-00731-1.
*de Angelis, Luigi, Francesco Baglivo, Guglielmo Arzilli, Gaetano Pierpaolo Privitera, Paolo Ferragina, Alberto Eugenio Tozzi, and Caterina Rizzo. “ChatGPT and the Rise of Large Language Models: The New AI-Driven Infodemic Threat in Public Health.” ''Frontiers in Public Health'' 11 (2023): 1166120. https://doi.org/10.3389/fpubh.2023.1166120.
*Arbuckle, Alyssa. 2020. “How Can We Broaden and Diversify Humanities Knowledge Translation?” ''Pop! Public. Open. Participatory'', no. 2. https://doi.org/10.48404/pop.2020.12.
*Arbuckle, Arbuckle, Ray Siemens, Jon Bath, Constance Crompton, Laura Estill, Tanja Niemann, Jon Saklofske, and Lynne Siemens. 2022. “An Open Social Scholarship Path for the Humanities.” ''Journal of Electronic Publishing'' 25 (2). https://doi.org/10.3998/jep.1973.
*Arbuckle, Arbuckle, and John Maxwell. 2019. “Modelling Open Social Scholarship Within the INKE Community.” ''KULA: Knowledge Creation, Dissemination, and Preservation Studies'' 3 (1): 1–8. https://doi.org/10.5334/kula.15.
*Arnett, Catherine, Eliot Jones, Ivan P. Yamshchikov, and Pierre-Carl Langlais. “Toxicity of the commons: Curating open-source pre-training data.” Preprint, ''arXiv'', November 18. https://doi.org/10.48550/arXiv.2410.22587.
*Arora, Payal. 2024. “Creative data justice: a decolonial and indigenous framework to assess creativity and artificial intelligence.” ''Information, Communication &amp; Society'': 1–17. https://doi.org/10.1080/1369118x.2024.2420041.
*Arthur, Paul L., Lydia Hearn, Lucy Montgomery, Hugh Craig, Alyssa Arbuckle, and Ray Siemens. 2021. “Open Scholarship in Australia: A Review of Needs, Barriers, and Opportunities.” ''Digital Scholarship in the Humanities'' 36 (4): 795–812. https://doi.org/10.1093/llc/fqaa063.

==B==
*Bail, Christopher A. “Can Generative Artiﬁcial Intelligence Improve Social Science?”. https://www.semanticscholar.org/paper/Can-Generative-Artiﬁcial-Intelligence-Improve-Bail/6206cc77bb3a3c0b6b9fce1ad68a8b1786a56941.
*Bakharia, Aneesha, Antonette Shibani, Lisa-Angelique Lim, Trish McCluskey, and Simon Buckingham Shum. 2025. “From Transcripts to Themes: A Trustworthy Workflow for Qualitative Analysis Using Large Language Models.” In ''Joint Proceedings of LAK 2025 Workshops, co-located with the 15th International Conference on Learning Analytics and Knowledge (LAK 2025)''. Dublin, Ireland: CEUR-WS.org. https://ceur-ws.org/Vol-3995/LLMQUAL_paper1.pdf.
*Balendra, Soorya. 2025. “Meta's AI Moderation and Free Speech: Ongoing Challenges in the Global South.” ''Cambridge Forum on AI: Law and Governance'' 1. https://doi.org/10.1017/cfl.2025.5.
*Baltes, Sebastian, Florian Angermeir, Chetan Arora, Preetha Chatterjee, Jens Deitenbeck, Daniel Graziotin, Christoph Treude, et al. 2025. “Guidelines for Empirical Studies in Software Engineering Involving Large Language Models.” Preprint, ''arXiv'', August 21. https://arxiv.org/abs/2508.15503.
*Batool, Amna, Didar Zowghi, and Muneera Bano. 2025. “AI Governance: A Systematic Literature Review.” ''AI and Ethics'' 5: 3265–3279. https://doi.org/10.1007/s43681-024-00653-w.
*Bender, Emily M., Timnit Gebru, Angelina McMillan-Major, and Shmargaret Shmitchell. 2021. “On the Dangers of Stochastic Parrots: Can Language Models Be Too Big? 🦜.” ''Proceedings of the 2021 ACM Conference on Fairness, Accountability, and Transparency'' (New York, NY, USA), FAccT ’21, March 1, 610–23. https://doi.org/10.1145/3442188.3445922.
*Bender, Emily M., and Batya Friedman. 2018. “Data Statements for Natural Language Processing: Toward Mitigating System Bias and Enabling Better Science.” ''Transactions of the Association for Computational Linguistics'' 6: 587–604. https://doi.org/10.1162/tacl_a_00041.
*Bergstrom, Tracy, and Dylan Ruediger. 2024. “A Third Transformation? Generative AI and Scholarly Publishing.” ''Ithaka S+R''. October 30, 2024. https://doi.org/10.18665/sr.321519.
*Berry, David M. 2025. “Synthetic Media and Computational Capitalism: Towards a Critical Theory of Artificial Intelligence.” ''AI &amp; Society'' 40: 5257–5269. https://doi.org/10.1007/s00146-025-02265-2.
*Berry, D. M. (2023). AI, ethics, and digital humanities. In J. O’Sullivan (Ed.), ''The Bloomsbury handbook to the digital humanities'', 445–457. Bloomsbury Academic. https://recoveryhub.siue.edu/wp-content/uploads/2024/10/AI-Ethics-and-Digital-Humanities-.pdf.
*Biderman, Stella, Hailey Schoelkopf, Quentin Anthony, Herbie Bradley, Kyle O'Brien, Eric Hallahan, Mohammad Aflah Khan, et al. 2022. “EleutherAI: Going Beyond 'Open Science' to 'Science in the Open.'” Preprint, ''arXiv'', October 12. https://arxiv.org/abs/2210.06413.
*Birkstedt, Teemu, Matti Minkkinen, Anushree Tandon, and Matti Mäntymäki. 2023. “AI Governance: Themes, Knowledge Gaps and Future Agendas”. ''Internet Research'' 33 (7): 133–67. https://doi.org/10.1108/INTR-01-2022-0042.
*Boer, Victor de, and Lise Stork. 2024. “Hybrid Intelligence for Digital Humanities.” Version 1. Preprint, ''arXiv'', April 15. https://doi.org/10.48550/ARXIV.2406.15374.
*Bostrom, Nick. 2017. “Strategic Implications of Openness in AI Development.” ''Global Policy'' 8 (2): 135–148. https://doi.org/10.1111/1758-5899.12403
*Boyd, Karen. 2021. “Datasheets for Datasets Help ML Engineers Notice and Understand Ethical Issues in Training Data.” ''Proceedings of the ACM on Human-Computer Interaction'' 5 (CSCW2): 1–27. https://doi.org/10.1145/3479582.
*Bozkurt, Aras. 2024. “GenAI et al.: Cocreation, Authorship, Ownership, Academic Ethics and Integrity in a Time of Generative AI.” ''Open Praxis'' 16 (1): 1–10. https://doi.org/10.55982/openpraxis.16.1.654.
*Broekhuizen, Thijs, Henri Dekker, Pedro De Faria, Sebastian Firk, Dinh Khoi Nguyen, and Wolfgang Sofka. 2023. “AI for Managing Open Innovation: Opportunities, Challenges, and a Research Agenda.” ''Journal of Business Research'' 167: 114196. https://doi.org/10.1016/j.jbusres.2023.114196.
*Broussard, Meredith. 2023. “The Challenges of AI Preservation.” ''The American Historical Review'' 128 (3): 1378–1381. https://doi.org/10.1093/ahr/rhad366.
*Brown, Richard. 2023. “The AI Generation: How Universities Can Prepare Students for the Changing World.” DEMOS and University of London. https://demos.co.uk/wp-content/uploads/2023/11/The-AI-Generation-2.pdf.
*Bryant, Rebecca. 2024. “Implementing an AI Reference Chatbot at the University of Calgary Library.” ''Hanging Together'', December 12. https://hangingtogether.org/implementing-an-ai-reference-chatbot-at-the-university-of-calgary-library/.
*Buitrago-Ciro, Jairo, Marta Samokishyn, Rachel Moylan, Jonathan Hernández Pérez, Oluwabunmi Bakare-Fatungase, and Carmel Firdawsi. 2025. “Bridging the AI Gap: Comparative Analysis of AI Integration, Education, and Outreach in Academic Libraries.” ''IFLA Journal'' 51 (3): 682–702. https://doi.org/10.1177/03400352251325274.
*Bullard, J. (2023). “Describing the HSS Commons: The View from Metadata.” ''Pop! Public. Open. Participatory'', no. 5. https://doi.org/10.54590/pop.2023.004.
*Burton, Jason W., Ezequiel Lopez-Lopez, Shahar Hechtlinger, et al. 2024. “How Large Language Models Can Reshape Collective Intelligence.” ''Nature Human Behaviour'' 8 (9): 1643–55. https://doi.org/10.1038/s41562-024-01959-9.

==C==
*Carmi, Elinor, Simeon J. Yates, Eleanor Lockley, and Alicja Pawluczuk. 2020. “Data Citizenship: Rethinking Data Literacy in the Age of Disinformation, Misinformation, and Malinformation.” ''Internet Policy Review'' 9 (2). https://doi.org/10.14763/2020.2.1481.
*Carnegie Endowment for International Peace. 2024. “Beyond Open vs. Closed: Emerging Consensus and Key Questions for Foundation AI Model Governance (2024).” https://carnegieendowment.org/research/2024/07/beyond-open-vs-closed-emerging-consensus-and-key-questions-for-foundation-ai-model-governance?lang=en.
*Carroll, Stephanie Russo, Ibrahim Garba, Óscar Luis Figueroa Rodríguez, Jarita Holbrook, and Raymond Lovett. 2020. “The CARE Principles for Indigenous Data Governance.” ''Data Science Journal'' 19 (1): 43. https://doi.org/10.5334/dsj-2020-043.
*Carroll, Stephanie Russo, Edit Herczog, Māui Hudson, Keith Russell, and Shelley Stall. 2021. “Operationalizing the CARE and FAIR Principles for Indigenous Data Futures.” ''Scientific Data'' 8: 108. https://doi.org/10.1038/s41597-021-00892-0.
*Checco, Alessandro, Lorenzo Bracciale, Pierpaolo Loreti, Stephen Pinfield, and Giuseppe Bianchi. 2021. “AI-Assisted Peer Review.” ''Humanities and Social Sciences Communications'' 8: 25. https://doi.org/10.1057/s41599-020-00703-8.
*Cheong, Inyoung. 2024. “Collaborative Approaches to AI Governance: Exploring Co-Design and Co-Regulation Models.” PhD diss., University of Washington. https://homes.cs.washington.edu/\~yoshi/papers/theses/inyoung-cheong-dissertation.pdf.
*Chun, Jon, and Katherline Elkins. 2023. “The Crisis of Artificial Intelligence: A New Digital Humanities Curriculum for Human-Centred AI.” ''International Journal of Humanities and Arts Computing'' 17 (2): 147–167. https://doi.org/10.3366/ijhac.2023.0310.
*Chung, Hiu-Fung. 2025. “Betting on (Un)Certain Futures: Sociotechnical Imaginaries of AI and Varieties of Techno-Developmentalism in Asia.” ''Information, Communication &amp; Society'' 29 (3): 909–926. https://doi.org/10.1080/1369118X.2025.2535427.
*Colbert-Lewis, Danielle, Lawrence Maminta, Kelly McElroy, Graeme Slaght, and Mark Swartz. 2024. “The Citation Economy as a Site of Extraction for Surveillance Publishing.” ''Canadian Journal of Academic Librarianship'' 10 (December): 1–22. https://doi.org/10.33137/cjal-rcbu.v10.43293.
*Cooper, Martin. 2023. “Open Source Is Good for AI But, Is AI Good for Open Source?” ''ITNOW'' 65 (2): 50–51. https://doi.org/10.1093/combul/bwad062.
*Corsi, Giulio, Bill Marino, and Willow Wong. 2024. “The spread of synthetic media on X.” ''Harvard Kennedy School (HKS) Misinformation Review''. https://doi.org/10.37016/mr-2020-140.
*Crompton, Constance, Lori Antranikan, Ruth Truong, and Paige Maskell. 2020. “Familiar Wikidata: The Case for Building a Data Source We Can Trust.” ''Pop! Public. Open. Participatory'', no. 2. https://doi.org/10.48404/pop.2020.02.

==D==
*Daniel Delmonaco, Samuel Mayworm, Hibby Thach, Josh Guberman, Aurelia Augusta, and Oliver L. Haimson. 2024. “'What are you doing, TikTok?': How Marginalized Social Media Users Perceive, Theorize, and 'Prove' Shadowbanning.” Available at: https://oliverhaimson.com/PDFs/DelmonacoShadowbanning.pdf.
*Deng, Ruiqi, Maoli Jiang, Xinlu Yu, Yuyan Lu, and Shasha Liu. 2025. “Does ChatGPT Enhance Student Learning? A Systematic Review and Meta-Analysis of Experimental Studies.” ''Computers &amp; Education'' 227: 105224. https://doi.org/10.1016/j.compedu.2024.105224.
*Dennstädt, Fabio, Cedric Sivert Möller, Tim Fellerhoff, Felix Busch, Oke Gerke, André Karch, and Oliver Krause. 2024. “Title and Abstract Screening for Literature Reviews Using Large Language Models: An Exploratory Study in the Biomedical Domain.” ''Systematic Reviews'' 13 (1): 158. https://doi.org/10.1186/s13643-024-02575-4.
*Drolsbach, Chiara, and Nicolas Pröllochs. 2025. “Characterizing AI-Generated Misinformation on Social Media.” Preprint, ''arXiv'', May 15. https://doi.org/10.48550/arXiv.2505.10266.
*Duricic, Tomislav, Hussain Hussain, Emanuel Lacic, Dominik Kowald, Denis Helic, and Elisabeth Lex. 2023. “Beyond-Accuracy: A Review on Diversity, Serendipity, and Fairness in Recommender Systems Based on Graph Neural Networks.” ''Frontiers in Big Data'' 6: 1251072. https://doi.org/10.3389/fdata.2023.1251072.

==E==
*El Khatib, Randa, Lindsey Seatter, Tracey El Hajj, Conrad Leibel, Alyssa Arbuckle, Ray Siemens, Caroline Winter, and the ETCL and INKE Research Groups. 2019. “Open Social Scholarship Annotated Bibliography.” ''KULA: Knowledge Creation, Dissemination, and Preservation Studies'' 3 (1): 24. https://doi.org/10.5334/kula.58.
*Eloundou, Tyna, Sam Manning, Pamela Mishkin, and Daniel Rock. 2024. “GPTs are GPTs: Labor market impact potential of LLMs.” ''Science'' 384 (6698): 1306–1311. https://doi.org/10.1126/science.adj0998.

==F==
*Fırıncı, Yusuf. 2024. “Decolonial Artificial Intelligence; Algorithmic Fairness in Alignment with Turkish and Islamic Values.” ''Marmara Üniversitesi İlahiyat Fakültesi Dergisi'' 67 (67): 250–279. https://doi.org/10.15370/maruifd.1565884.
*Fanning, Katie, Claire Kim, and Jon Saklofske. 2023. “Interactive Inspirations: The Case for Incorporating Joy and Play in Open Social Scholarship.” ''Pop! Public. Open. Participatory'', no. 5. https://doi.org/10.54590/pop.2023.012.
*Floridi, Luciano. 2018. “Soft Ethics and the Governance of the Digital.” ''Philosophy &amp; Technology'' 31 (1): 1–8. https://doi.org/10.1007/s13347-018-0303-9.
*Frangou, Sophia, Umberto Volpe, and Andrea Fiorillo. 2025. “AI in scientific writing and publishing: A call for critical engagement.” ''European Psychiatry'' 68 (1): e98. https://doi.org/10.1192/j.eurpsy.2025.10061.

==G==
*Gallegos, Isabel O., Ryan A. Rossi, Joe Barrow, Md Mehrab Tanjim, Sungchul Kim, Franck Dernoncourt, Tong Yu, Ruiyi Zhang, and Nesreen K. Ahmed. 2024. “Bias and Fairness in Large Language Models: A Survey.” ''Computational Linguistics'' 50 (3): 1097–1179. https://doi.org/10.1162/coli_a_00524.
*Gasser, Urs, and Virgilio A. F. Almeida. 2017. “A Layered Model for AI Governance.” ''IEEE Internet Computing'' 21 (6): 58–62. https://doi.org/10.1109/MIC.2017.4180835.
*Goddard, Lisa. 2021. Persistent Identifiers as Open Research Infrastructure to Reduce Administrative Burden. ''Pop! Public. Open. Participatory'', no. 3. https://doi.org/10.54590/pop.2021.006.
*Gorwa, Robert, Reuben Binns, and Christian Katzenbach. 2020. “Algorithmic Content Moderation: Technical and Political Challenges in the Automation of Platform Governance.” ''Big Data &amp; Society'' 7 (1): 1–15. https://doi.org/10.1177/2053951719897945.
*Graßhoff, Gerd. 2025. “AI-Reporter: A Path to a New Genre of Scientific Communication.” Preprint, ''arXiv'', July 8. https://arxiv.org/abs/2507.05903.
*Grigoli, Leland Renato. 2023. “Ghosts in the Machine.” ''American Historical Association'' 61 (3). https://www.historians.org/wp-content/uploads/2024/07/Perspectives\_61N3.pdf.
*Gruzd, Anatoliy, Philip Mai, and Anthony Clements Haines. 2025. ''The State of Generative AI Use in Canada 2025: Exploring Public Attitudes and Adoption Trends''. Toronto: Social Media Lab, Toronto Metropolitan University. https://figshare.com/articles/preprint/The_State_of_Generative_AI_Use_in_Canada_2025_Exploring_Public_Attitudes_and_Adoption_Trends/28664780/1The\_State\_of\_Generative\_AI\_Use\_in\_Canada\_2025\_Exploring\_Public\_Attitudes\_and\_Adoption\_Trends/28664780/1.
*Gulson, Kalervo N., and P. Taylor Webb. 2023. “Steering the Mind Share: Technology Companies, Policy and Artificial Intelligence Research in Universities.” ''Discourse: Studies in the Cultural Politics of Education'' 44 (2): 195–207. https://doi.org/10.1080/01596306.2021.1981828.
*Gundersen, Odd Erik, Odd Cappelen, Martin Mølnå, and Nicklas Grimstad Nilsen. 2024. “The Unreasonable Effectiveness of Open Science in AI: A Replication Study.” Preprint, ''arXiv'', December 20. https://doi.org/10.48550/ARXIV.2412.17859.
*Guo, Xinwei, Yujun Li, Yafeng Peng, and Xuetao Wei. 2024. “Copyleft for Alleviating AIGC Copyright Dilemma: What-if Analysis, Public Perception and Implications.” Preprint, ''arXiv'', February 19. https://arxiv.org/abs/2402.12216.

==H==
*Hadley, Emma, Alan Blatecky, and Megan Comfort. 2025. “Investigating Algorithm Review Boards for Organizational Responsible Artificial Intelligence Governance.” ''AI and Ethics'' 5: 2485–2495. https://doi.org/10.1007/s43681-024-00574-8.
*Hara, Noriko, Eugene Kim, Shohana Akter, and Kunihiro Miyazaki. 2025. “Exploring the Dynamics of Interaction About Generative Artificial Intelligence Between Experts and the Public on Social Media.” ''Journal of Science Communication'' 24 (1): A02. https://doi.org/10.22323/2.24010202.
*Heger, Amy, Liz B. Marquis, Mihaela Vorvoreanu, Hanna Wallach, and Jennifer Wortman Vaughan. 2022. “Understanding Machine Learning Practitioners' Data Documentation Perceptions, Needs, Challenges, and Desiderata.” ''Proceedings of the ACM on Human-Computer Interaction'' 6 (CSCW2): 1–29. https://doi.org/10.1145/3555760.
*Helregel, Nicole. 2025. “AI and Open Science: Implications and Library Practice Recommendations.” ''Library Trends'' 73 (3). https://doi.org/10.1353/lib.2025.a961191.
*Hertweck, Corinna, Joachim Baumann, Michele Loi, Eleonora Viganò, and Christoph Heitz. 2022. “A Justice-Based Framework for the Analysis of Algorithmic Fairness-Utility Trade-Offs.” Preprint, ''arXiv'', June 6. https://arxiv.org/abs/2206.02891.
*Hosseini, Mohammad, Serge P. J. M. Horbach, Kristi Holmes, and Tony Ross-Hellauer. 2025. “Open Science at the generative AI turn: An exploratory analysis of challenges and opportunities.” ''Quantitative Science Studies'' 6: 22–45. https://doi.org/10.1162/qss_a_00337.
*Hosseini, Mohammad, and Serge P. J. M. Horbach. 2023. “Fighting Reviewer Fatigue or Amplifying Bias? Considerations and Recommendations for Use of ChatGPT and Other Large Language Models in Scholarly Peer Review.” ''Research Integrity and Peer Review'' 8 (1): 15. https://doi.org/10.21203/rs.3.rs-2587766/v1.
*Huerta, E. A., Ben Blaiszik, L. Catherine Brinson, Kristofer E. Bouchard, and D. Díaz, et al. 2023. “FAIR for AI: An Interdisciplinary and International Community Building Perspective.” ''Scientific Data'' 10: 487. https://doi.org/10.1038/s41597-023-02298-6.

==J==
*Jaillant, Lise, Olivia Mitchell, Eric Ewoh-Opu, and Maribel Hidalgo Urbaneja. 2025. “How Can We Improve the Diversity of Archival Collections with AI? Opportunities, Risks, and Solutions.” ''AI &amp; Society'' 40: 4447–4459. https://doi.org/10.1007/s00146-025-02222-z.
*Janssen, Marijn. 2025. “Responsible Governance of Generative AI: Conceptualizing GenAI as Complex Adaptive Systems.” ''Policy and Society'' 44 (1): 38–51. https://doi.org/10.1093/polsoc/puae040.
*Jarrahi, Mohammad Hossein, Gemma Newlands, Min Kyung Lee, Christine T. Wolf, Eliscia Kinder, and Will Sutherland. 2021. “Algorithmic management in a work context.” ''Big Data &amp; Society'' 8 (2): 20539517211020332. https://doi.org/10.1177/20539517211020332.
*Jensen, Graham. 2023. &quot;Digital Knowledge Commons, Scholarly Connection, and the Evolution of Open Scholarship.&quot; In ''Open Scholarship Press Curated Volumes: Connection''. https://doi.org/10.21428/47bc126e.0ca461a4.
*Jensen, Graham, Alyssa Arbuckle, Caroline Winter, Talya Jesperson, Tyler Fontenot, Ray Siemens, and the ETCL and INKE Research Groups. 2022. “Fostering Digital Communities of Care: Safety, Security, and Trust in the Canadian HSS Commons.“ ''IDEAH'' 3 (2). https://ideah.pubpub.org/pub/h7927ugt.
*Jiang, Jialei. 2024. “When generative artificial intelligence meets multimodal composition: Rethinking the composition process through an AI-assisted design project.” ''Computers and Composition'' 74: 102883. https://doi.org/10.1016/j.compcom.2024.102883.
*Jones, Matthew L. 2023. “AI in History.” ''The American Historical Review'' 128 (3): 1360–67. https://doi.org/10.1093/ahr/rhad361.

==K==
*Kay, Jackie, Atoosa Kasirzadeh, and Shakir Mohamed. 2024. “Epistemic Injustice in Generative AI.” Preprint, ''arXiv'', August 21. https://doi.org/10.48550/arXiv.2408.11441.
*Kember, Sarah, and Amy Brand. 2023. “The Corporate Capture of Open-Access Publishing.” ''The Chronicle of Higher Education'', August 16. https://www.chronicle.com/article/the-corporate-capture-of-open-access-publishing.
*Kirschenbaum, Matthew. 2025. “The US of AI.” Public Draft, February 25, 2025. https://drive.google.com/file/d/1O2qkjhg7Ei5zZWmBraNwXq4V0lTauspN/view.
*Klein, Laura, Meredith Martin, André Brock, Maria Antoniak, Melanie Walsh, Jessica Marie Johnson, Lauren Tilton, and David Mimno. 2025. Provocations from the Humanities for Generative AI Research. Preprint, ''arXiv'', February 26. https://arxiv.org/abs/2502.19190.
*Klein, Lauren, and Catherine D'Ignazio. 2024. “Data feminism for AI.” In ''Proceedings of the 2024 ACM Conference on Fairness, Accountability, and Transparency'': 100–112. https://doi.org/10.1145/3630106.3658543.
*Kousha, Kayvan, and Mike Thelwall. 2024. “Artificial Intelligence to Support Publishing and Peer Review: A Summary and Review.” ''Learned Publishing'' 37 (1): 4–12. https://doi.org/10.1002/leap.1570.

==L==
*Lee, Daniel, and Edward Palmer. 2025. “Prompt Engineering in Higher Education: A Systematic Review to Help Inform Curricula.” ''International Journal of Educational Technology in Higher Education'' 22: 16. https://doi.org/10.1186/s41239-025-00503-7.
*Lewis, Jason Edward, Noelani Arista, Archer Pechawis, and Suzanne Kite. 2018. “Making Kin with the Machines.” ''Journal of Design and Science'', ahead of print, July 16. https://doi.org/10.21428/bfafd97b.
*Lim, Gim Hui, M. L. Tan, V. C. W. Hoe, and D. Koh. 2025. “Generative AI in Peer Review Process for Occupational Health.” ''Occupational Medicine'' 75 (5): 242–49. https://doi.org/10.1093/occmed/kqaf051.
*Linåker, Johan, Cailean Osborne, Jennifer Ding, Daniel Puttick, and Richard Nweibo. 2025. “A Cartography of Open Collaboration in Open Source AI: Mapping Practices, Motivations, and Governance in 14 Open Large Language Model Projects.” Preprint, ''arXiv'', September 29. https://arxiv.org/abs/2509.25397.
*Long, Duri, and Brian Magerko. 2020. “What is AI Literacy? Competencies and Design Considerations.” In ''Proceedings of the 2020 CHI Conference on Human Factors in Computing Systems'', 1–13. New York, NY: Association for Computing Machinery. https://doi.org/10.1145/3313831.3376727.
*Luth, Eric. 2025. “The Use of Wikipedia, Wikimedia, and Open Access Content for Artificial Intelligence and Text and Data Mining.” ''Stockholm IP Law Review'' 6 (1): 109–138. https://doi.org/10.53292/33313cc8.be33e111.

==M==
*Ma, Lai. 2024. “Generative AI for Academic Publishing? Some Thoughts About Epistemic Diversity and the Pursuit of Truth.” ''KULA: Knowledge Creation, Dissemination, and Preservation Studies'' 7 (1): 1–5. https://doi.org/10.18357/kula.287.
*Mai, Dang Thi Thuy, Cuong Van Da, and Nguyen Van Hanh. 2024. “The Use of ChatGPT in Teaching and Learning: A Systematic Review through SWOT Analysis Approach.” ''Frontiers in Education'' 9: 1328769. https://doi.org/10.3389/feduc.2024.1328769.
*Mao, Yishu, Vanessa Richter, and Christian Katzenbach. (2025). &quot;Strategising imaginaries: How corporate actors in China, Germany and the US shape AI governance.&quot; ''Big Data &amp; Society'' 12 (1). https://doi.org/10.1177/20539517251400727.
*Majdik, Zoltan P., and S. Scott Graham. 2024. “Rhetoric of/with AI: An Introduction.” ''Rhetoric Society Quarterly'' 54 (3): 222–31. https://doi.org/10.1080/02773945.2024.2343264.
*Maxwell, J. W. (2015). Beyond Open Access to Open Publication and Open Scholarship. ''Scholarly and Research Communication'', 6 (3), 1–10. https://doi.org/10.22230/src.2015v6n3a202.
*McIntosh, Timothy R., Teo Susnjak, Tong Liu, Paul Watters, and Malka N. Halgamuge. 2023. “From Google Gemini to OpenAI Q (Q-Star): A Survey of Reshaping the Generative Artificial Intelligence (AI) Research Landscape.” ''Technologies''. https://doi.org/10.3390/technologies13020051.
*Mehlenbacher, Brad, Ana Patricia Balbon, and Ashley Rose Mehlenbacher. 2024. “Synthetic Genres: Expert Genres, Non-Specialist Audiences, and Misinformation in the Artificial Intelligence Age.” ''Journal of Technical Writing and Communication'', January 31, 00472816231226249. https://doi.org/10.1177/00472816231226249.
*Meneses, Luis. 2020. “Integrating the Social Media Engine with Large-scale Open Access Repositories: A Discussion.” ''Pop! Public. Open. Participatory'', no. 2. https://doi.org/10.54590/pop.2020.004. 
*Mitchell, Peta, Michelle Riedlinger, Jake Goldenfein, Aaron Snoswell, Jean Burgess, and Kevin Witzenberger. 2025. “RESEARCH GENAI: SITUATING GENERATIVE AI IN THE SCHOLARLY ECONOMY.” ''AoIR Selected Papers of Internet Research'', January. https://doi.org/10.5210/spir.v2024i0.14006.
*Mitra, Bhaskar, Henriette Cramer, and Olya Gurevich. 2024. “Sociotechnical Implications of Generative Artificial Intelligence for Information Access.” Preprint, ''arXiv'', May 19. https://doi.org/10.48550/arXiv.2405.11612.
*Mohamed, Shakir, Marie-Therese Png, and William Isaac. 2020. “Decolonial AI: Decolonial Theory as Sociotechnical Foresight in Artificial Intelligence.” ''Philosophy &amp; Technology'' 33 (4): 659–84. https://doi.org/10.1007/s13347-020-00405-8.
*Montague-Hellen, Beth. 2024. “Empowering Knowledge through AI: Open Scholarship Proactively Supporting Well Trained Generative AI.” ''Insights'' 37 (1). https://doi.org/10.1629/uksg.649.
*Mugaanyi, Joseph, Christoph Lehner, and Lia M. Bally. 2024. “Evaluation of Large Language Model Performance and Reliability for Citation Generation Across Scientific Disciplines.” ''Journal of Medical Internet Research'' 26: e52935. https://doi.org/10.2196/52935.
*Muldoon, James, and Boxi A Wu. 2023. “Artificial Intelligence in the Colonial Matrix of Power.” ''Philosophy &amp; Technology'' 36 (4). https://doi.org/10.1007/s13347-023-00687-8.

==N==
*Nelson, Brent, Miguel Dela Pena, Prototyping the Digital Archive Team, and the INKE Research Group. 2023. “No Journal is an Island: The John Donne Journal and the Possibilities of Open Access.” ''Pop! Public. Open. Participatory'', no. 5. https://doi.org/10.54590/pop.2023.007.
*Ng, Davy Tsz Kit, Jac Ka Lok Leung, Samuel Kai Wah Chu, and Maggie Shen Qiao. 2021. “Conceptualizing AI Literacy: An Exploratory Review.” ''Computers and Education: Artificial Intelligence'' 2: 100041. https://doi.org/10.1016/j.caeai.2021.100041 .
*Ngulube, Patrick, and Neema Florence Vincent Mosha. 2024. “Integrating artificial intelligence-based technologies ‘safely’ in academic libraries: An overview through a scoping review.” ''Technical Services Quarterly'' 42 (1): 46–67. https://doi.org/10.1080/07317131.2024.2432093.

==O==
*Oates, A., and D. Johnson. 2025. “ChatGPT in the Classroom: Evaluating Its Role in Fostering Critical Evaluation Skills.” ''International Journal of Artificial Intelligence in Education'' 35 (4): 1793-1824. https://doi.org/10.1007/s40593-024-00452-8.
*Oh, Dayei, and John Downey. 2024. “Does Algorithmic Content Moderation Promote Democratic Discourse? Radical Democratic Critique of Toxic Language AI.” ''Information, Communication &amp; Society'' 28 (7): 1157–76. https://doi.org/10.1080/1369118X.2024.2346531.
*Ohagi, Masaya. 2024. “Polarization of Autonomous Generative AI Agents Under Echo Chambers.” Preprint, ''arXiv'' February 19. https://arxiv.org/abs/2402.12212.
*Open Source Initiative. The Open Source AI Definition 1.0 (2024–2025). https://opensource.org/ai.
*Osborne, Cailean. 2024. “Why Companies 'Democratise' Artificial Intelligence: The Case of Open Source Software Donations.” Preprint, ''arXiv'', September 26. https://doi.org/10.48550/ARXIV.2409.17876.

==P==
*Papagiannidis, Emmanouil, Patrick Mikalef, and Kieran Conboy. 2025. “Responsible Artificial Intelligence Governance: A Review and Research Framework.” ''The Journal of Strategic Information Systems'' 34 (2): 101885. https://doi.org/10.1016/j.jsis.2024.101885.
*Papi, Sara, Marco Gaido, Luisa Bentivogli, and Matteo Negri. 2025. “FAMA: The First Large-Scale Open-Science Speech Foundation Model for English and Italian.” Preprint, ''arXiv'', May 28. https://arxiv.org/abs/2505.22759.
*Park, Seyeon, and Xiaoli Nan. 2025. “Generative AI and misinformation: a scoping review of the role of generative AI in the generation, detection, mitigation, and impact of misinformation.” ''AI &amp; Society'' 41: 1501–1515. https://doi.org/10.1007/s00146-025-02620-3.
*Peters, Uwe, and Benjamin Chin-Yee. 2025. “Generalization Bias in Large Language Model Summarization of Scientific Research.” ''Royal Society Open Science'' 12 (4): 241776. https://doi.org/10.1098/rsos.241776.
*Pividori, Milton, and Casey S. Greene. 2024. “A Publishing Infrastructure for Artificial Intelligence (AI)-Assisted Academic Authoring.” ''Journal of the American Medical Informatics Association'' 31 (9): 2103–13 https://doi.org/10.1093/jamia/ocae139.
*Pooley, Jefferson. 2024. “Large Language Publishing: The Scholarly Publishing Oligopoly's Bet on AI.” ''KULA: Knowledge Creation, Dissemination, and Preservation Studies'' 7 (1): 1–11. https://doi.org/10.18357/kula.291.
*Pope, Andrew, and Rongqian Ma. 2024. “Exploring Historians’ Critical Use of Generative AI Technologies for History Education.” ''Proceedings of the Association for Information Science and Technology'' 61 (1): 1071–73. https://doi.org/10.1002/pra2.1188.
*Prescott, Andrew. 2023. “Bias in Big Data, Machine Learning and AI: What Lessons for the Digital Humanities?” ''Digital Humanities Quarterly'' 17 (2). https://www.proquest.com/scholarly-journals/bias-big-data-machine-learning-ai-what-lessons/docview/2842908427/se-2.

==Q==
*Qi, Weihong, Jinsheng Pan, Hanjia Lyu, and Jiebo Luo. 2024. “Excitements and concerns in the post-ChatGPT era: Deciphering public perception of AI through social media analysis.” ''Telematics and Informatics'' 92: 102158. https://doi.org/10.1016/j.tele.2024.102158.

==R==
*Radu, Roxana. 2021. “Steering the Governance of Artificial Intelligence: National Strategies in Perspective.” ''Policy and Society'' 40 (2): 178–193. https://doi.org/10.1080/14494035.2021.1929728.
*Rapanta, Chrysi, Anna Åkerfeldt, Mark Vanderbeeken, Diane Lison, Khadija Mohammed, Amanda Gibbs, Helder Coelho, Pinar Seda Celik, Carola Bruna, Ingrid Helleve, Chrysoula Vassilakopoulou, Pieter Swart, Ana Lúcia Marques, and Dirk Ifenthaler. 2025. “Critical GenAI Literacy: Postdigital Configurations.” ''Postdigital Science and Education'' 17 (1): 167–199. https://doi.org/10.1007/s42438-025-00573-w.
*Razack, Habib Ibrahim Abdul, Sam T. Mathew, Fathinul Fikri Ahmad Saad, and Saleh A. Alqahtani. 2021. “Artificial intelligence-assisted tools for redefining the communication landscape of the scholarly world.” ''Science Editing'' 8 (2): 134–144. https://doi.org/10.6087/kcse.244.
*Reynolds, CJ, and Blake Hallinan. 2024. “User-Generated Accountability: Public Participation in Algorithmic Governance on YouTube.” ''New Media &amp; Society'' 26 (9): 5107–5129. https://doi.org/10.1177/14614448241251791.
*Risam, Roopika. “What Passes for Human?: Undermining the Universal Subject in Digital Humanities Praxis.” In Bodies of Information: Intersectional Feminism and the Digital Humanities, edited by Elizabeth Losh and Jacqueline Wernimont, 39–56. ''University of Minnesota Press'', 2018. https://doi.org/10.5749/j.ctv9hj9r9.6.
*Rockwell, G., Land, K., &amp; MacDonald, A. 2021. Social Analytics Through Spyral. ''Pop! Public. Open. Participatory,'' no. 3. https://doi.org/10.54590/pop.2021.004.
*Rughiniș, Cosima, et al. 2025. “AI at the Knowledge Gates: Institutional Policies and Hybrid Configurations in Universities and Publishers.” ''Frontiers in Computer Science'' 7: 1608276. https://doi.org/10.3389/fcomp.2025.1608276.

==S==
*Salami, Aishat Oyenike. 2024. “Artificial intelligence, digital colonialism, and the implications for Africa's future development.” ''Data &amp; Policy'' 6. https://doi.org/10.1017/dap.2024.75.
*Sartori, L., and A. Theodorou. 2022. A sociotechnical perspective for the future of AI: narratives, inequalities, and human control. ''Ethics and Information Technology'' 24 (1): 4. https://doi.org/10.1007/s10676-022-09624-3.
*Savolainen, Lotta. 2022. “The Shadow Banning Controversy: Perceived Governance and Algorithmic Folklore.” Media, Culture &amp; Society 44 (6): 1091–1109. https://doi.org/10.1177/01634437221077174.
*Shcherbiak, Anna, Hooman Habibnia, Robert Böhm, and Susann Fiedler. “Evaluating Science: A Comparison of Human and AI Reviewers.” ''Judgment and Decision Making'' 19 (2024): e21. https://doi.org/10.1017/jdm.2024.24.
*Schmit, Cason, M. J. Doerr, and J. K. Wagner. 2023. “Leveraging IP for AI Governance.” ''Science'' 379 (6633): 646–647. https://doi.org/10.1126/science.add2202.
*Schroeder, Hope, Marianne Aubin Le Quéré, Casey Randazzo, David Mimno, and Sarita Schoenebeck. 2024. “Large Language Models in Qualitative Research: Uses, Tensions, and Intentions.” Preprint, ''arXiv'', October 9. https://arxiv.org/abs/2410.07362.
*Seger et al. “Democratising AI: Multiple Meanings, Goals, and Methods.” ''Proceedings of the 2023 AAAI/ACM Conference on AI, Ethics, and Society''. https://dl.acm.org/doi/10.1145/3600211.3604693.
*Shams, Rifat Ara, Didar Zowghi, and Muneera Bano. 2023. “AI and the Quest for Diversity and Inclusion: A Systematic Literature Review.” ''AI and Ethics'' 3 (4): 1427–1453. https://doi.org/10.1007/s43681-023-00362-w.
*Shanklin, Grant, Emmie Hine, Claudio Novelli, Tyler Schroder, and Luciano Floridi. 2025. “The Case for Contextual Copyleft: Licensing Open Source Training Data and Generative AI.” Preprint, ''arXiv'', July 17. https://arxiv.org/abs/2507.12713.
*Shin, Donghee, Amy Koerber, and Joon Soo Lim. 2024. “Impact of misinformation from generative AI on user information processing: How people understand misinformation from generative AI.” ''New Media &amp; Society'' 27 (7): 4017–4047. https://doi.org/10.1177/14614448241234040.
*Sidorkin, Alexander. 2025. “Environmental Impact of Generative AI: Carbon and Water Footprint.” ''AI-EDU Arxiv'' 1. https://doi.org/10.36851/ai-edu.vi.5448.
*Siemens, Lynne, and the INKE Research Group. 2023. I Stayed for the Community: Collaboration and Community in an Open Social Scholarship Research Project. ''Pop! Public. Open. Participatory'', no. 5. https://doi.org/10.54590/pop.2023.013.
*da Silva Cardoso, Heike, and Vitor Rocio. (2025). &quot;Enhancing Digital Libraries Through NLP and Recommender Systems: Current Trends and Future Prospects with Large Language Models.&quot; In ''Technology and Innovation in Learning, Teaching and Education (TECH-EDU 2024)''. Communications in Computer and Information Science, vol. 2480, 69–79. Springer, Cham. https://doi.org/10.1007/978-3-032-02672-9_5. 
*Simon, Judith. 2025. “Generative AI, Quadruple Deception &amp; Trust.” ''Social Epistemology''. https://doi.org/10.1080/02691728.2025.2491087.
*Smith, Regan. 2025. “Licensing of Text for Generative AI: Learnings from Non-AI Licensing Practices.” ''The Columbia Journal of Law &amp; the Arts'' 48 (4): 457–512. https://doi.org/10.52214/jla.v48i4.13926.
*Spatharioti, Sofia Eleni, David Rothschild, Daniel G. Goldstein, and Jake M. Hofman. 2025. “Effects of LLM-based Search on Decision Making: Speed, Accuracy, and Overreliance.” ''Proceedings of the 2025 CHI Conference on Human Factors in Computing Systems''. https://doi.org/10.1145/3706598.3714082.
*Sposato, Martin. 2025. “Artificial Intelligence in Educational Leadership: A Comprehensive Taxonomy and Future Directions.” ''International Journal of Educational Technology in Higher Education'' 22 (20). https://doi.org/10.1186/s41239-025-00517-1.
*Starke, Christopher, Janine Baleis, Birte Keller, and Frank Marcinkowski. 2022. “Fairness Perceptions of Algorithmic Decision-Making: A Systematic Review of the Empirical Literature.” ''Big Data &amp; Society'' 9 (2): 1–35. https://doi.org/10.1177/20539517221115189.
*Strubell, Emma, Ananya Ganesh, and Andrew McCallum. 2019. “Energy and Policy Considerations for Deep Learning in NLP.” ''Proceedings of the 57th Annual Meeting of the Association for Computational Linguistics'', 3645–3650. https://doi.org/10.18653/v1/p19-1355.
*Sun, Zhuanlan. 2025. “Large Language Models in Peer Review: Challenges and Opportunities.” ''Scientometrics'' 130 (10): 5503-5546. https://doi.org/10.1007/s11192-025-05440-w.
*Sutherland, Tonia, Marika Cifor, T. L. Cowan, Jas Rault, and Patricia Garcia. 2023. “The Feminist Data Manifest-NO: An Introduction and Four Reflections.” In ''Debates in the Digital Humanities'', edited by Lauren F. Klein and Matthew K. Gold. Minneapolis, MN: University of Minnesota Press. https://dhdebates.gc.cuny.edu/read/debates-in-the-digital-humanities-2023/section/16184c7d-eee1-40b2-a168-960d4c4035c4.

==T==
*Taeihagh, Araz. 2025. “Governance of Generative AI.” ''Policy and Society'' 44 (1): 1–14. https://doi.org/10.1093/polsoc/puaf001.
*Tan, Myles Joshua Toledo, and NMAT Maravilla. 2024. “Shaping Integrity: Why Generative Artificial Intelligence Does Not Have to Undermine Education.” ''Frontiers in Artificial Intelligence'' 7: 1471224. https://doi.org/10.3389/frai.2024.1471224.
*Taneja, Ankit Kumar, and Chandra Tripathi. 2020. “AI-Powered Recommender Systems: Personalization and Bias.” ''Turkish Journal of Computer and Mathematics Education (TURCOMAT)'' 11 (1): 1090–1094. https://doi.org/10.61841/turcomat.v11i1.14406.
*Taylor, Randon R., Bessie O'Dell, and John W. Murphy. 2023. “Human-centric AI: philosophical and community-centric considerations.” ''AI &amp; Society'' 39 (5): 2417–2424. https://doi.org/10.1007/s00146-023-01694-1.
*Ter-Minassian, Lucile. 2025. “Democratizing AI Governance: Balancing Expertise and Public Participation.” Preprint, ''arXiv'' January 16. https://doi.org/10.48550/arXiv.2502.08651.
*Tumadóttir, Anna. 2024. “Questions for Consideration on AI &amp; the Commons.” ''Creative Commons'', July 24. https://creativecommons.org/2024/07/24/preferencesignals/.
*Turin, Mark. 2021. “From Orality to Open: Innovations in Multimedia Monograph Publishing in the Humanities.” ''Pop! Public. Open. Participatory'', no. 3. https://doi.org/10.54590/pop.2021.005.

==V==
*Vake, Domen, Bogdan Šinik, Jernej Vičič, and Aleksander Tošić. 2025. &quot;Is Open Source the Future of AI? A Data‑Driven Approach.&quot; Preprint, ''arXiv'', January 27. https://arxiv.org/abs/2501.16403.
*van Es, Karin and Dennis Nguyen. 2024. “‘Your friendly AI assistant’: the anthropomorphic self-representations of ChatGPT and its implications for imagining AI.” ''AI &amp; Society'' 40: 3591–3603. https://doi.org/10.1007/s00146-024-02108-6.
*Varshney, Kush R. 2024. “Decolonial AI Alignment: Openness, Visesa-Dharma, and Including Excluded Knowledges.” ''Proceedings of the AAAI/ACM Conference on AI, Ethics, and Society'' 7: 1467–1481. https://doi.org/10.1609/aies.v7i1.31739.
*Veldhuis, Annemiek M., Phoebe W. K. Lo, Iain E. G. Kenny, and Alissa N. Antle. 2024. “Critical Artificial Intelligence literacy: A scoping review and framework synthesis.” ''International Journal of Child-Computer Interaction'' 43: 100708. https://doi.org/10.1016/j.ijcci.2024.100708.
*Vetter, Matthew A., Jialei Jiang, and Zachary J. McDowell. 2025. “An Endangered Species: How LLMs Threaten Wikipedia’s Sustainability.” ''AI &amp; Society'', February. https://doi.org/10.1007/s00146-025-02199-9.

==W==
*Weber, Michael, Martin Engert, Norman Schaffer, Jörg Weking, and Helmut Krcmar. 2023. “Organizational Capabilities for AI Implementation—Coping with Inscrutability and Data Dependency in AI.” ''Information Systems Frontiers'' 25: 1549–1569. https://doi.org/10.1007/s10796-022-10297-y.
*Werder, Karl, Balasubramaniam Ramesh, and Rongen (Sophia) Zhang. 2022. “Establishing Data Provenance for Responsible Artificial Intelligence Systems.” ''ACM Transactions on Management Information Systems'' 13 (4): 1–25. https://doi.org/10.1145/3503488.
*Whalen, Zach. 2023. “‘Any Means Necessary to Refuse Erasure by Algorithm:’ Lillian-Yvonne Bertram’s Travesty Generator.” ''DHQ: Digital Humanities Quarterly'' 17 (2). https://www.digitalhumanities.org/dhq/vol/17/2/000707/000707.html.
*White, Matt, Ibrahim Haddad, Cailean Osborne, Xiao-Yang Liu, Ahmed Abdelmonsef, Sachin Varghese, and Arnaud Le Hors. 2024. “The Model Openness Framework: Promoting Completeness and Openness for Reproducibility, Transparency, and Usability in AI.” Preprint, ''arXiv'', March 20. https://doi.org/10.48550/arXiv.2403.13784.
*Whiteley, Paul. 2023. “Why Artificial Intelligence Is a Misnomer.” ''London School of Economics and Political Science Politics and Policy Blog'', October 19. https://blogs.lse.ac.uk/politicsandpolicy/why-artificial-intelligence-is-a-misnomer/.
*Widder, David Gray, Dawn Nafus, Laura Dabbish, and James Herbsleb. 2022. “Limits and possibilities for ‘ethical AI’ in open source: A study of deepfakes.” In ''Proceedings of the 2022 ACM Conference on Fairness, Accountability, and Transparency (FAccT '22)'', 2035–2046. Association for Computing Machinery. https://doi.org/10.1145/3531146.3533779.
*Winkel, Marek. 2024. “Controlling the Uncontrollable: The Public Discourse on Artificial Intelligence between the Positions of Social and Technological Determinism.” ''AI &amp; Society'' 39 (5): 2449–2462. https://doi.org/10.1007/s00146-024-01979-z.
*Winter, Caroline. 2023. “Introduction: Open Scholarship Policy in Focus.” In ''Open Scholarship Press Curated Volume: Policy''. https://doi.org/10.21428/47bc126e.5abba88b.
*Winter, Caroline, Tyler Fontenot, Luis Meneses, Alyssa Arbuckle, Ray Siemens, and the ETCL and INKE Research Groups. 2020. Foundations for the Canadian HSS Commons: Exploring the Possibilities of Digital Research Communities. ''Pop! Public. Open. Participatory'', no. 2. https://doi.org/10.48404/pop.2020.05.
*de Winter, Joost. 2024. “Can ChatGPT be used to predict citation counts, readership, and social media interaction? An exploration among 2222 scientific abstracts.” ''Scientometrics'' 129: 2469–2487. https://doi.org/10.1007/s11192-024-04939-y.
*Wu, Chuhao, He Zhang, and John M. Carroll. 2024. “AI Governance in Higher Education: Case Studies of Guidance at Big Ten Universities.” Preprint, ''arXiv'', September 3. https://doi.org/10.48550/arXiv.2409.02017.

==X==
*Xie, Yu, and Sofia Avila. 2025. “The social impact of generative LLM-based AI.” ''Chinese Journal of Sociology'' 11 (1): 31–57. https://doi.org/10.1177/2057150X251315997.

==Y==
*Yim, Iris Heung Yue, and Jiahong Su. 2025. “Artificial Intelligence (AI) Learning Tools in K-12 Education: A Scoping Review.” ''British Journal of Educational Technology'' 56 (1): 169–196. https://doi.org/10.1007/s40692-023-00304-9.
*Yue, Yongjie, Maosong Zheng, Jiahui Liu, Zhimin Wang, and Chenhui Mao. 2025. “A Practical Guide and Assessment on Using ChatGPT to Conduct Grounded Theory Studies: Step-by-Step Reporting of the Data Analysis Process.” ''Journal of Medical Internet Research'' 27: e70122. https://doi.org/10.2196/70122.

==Z==
*Zeffiro, A. 2024. “Automating (In)securities: Cybersecurity’s AI Imaginaries.” Paper presented at EASST/4S, 2024. https://nomadit.co.uk/conference/easst-4s2024/p/14156.
*Zhu, Wenhao, Hongyi Liu, Qingxiu Dong, Jingjing Xu, Shujian Huang, Lingpeng Kong, Jiajun Chen, and Lei Li. 2023. “Multilingual Machine Translation with Large Language Models: Empirical Results and Analysis.” Preprint, ''arXiv'', April 10. https://arxiv.org/abs/2304.04675.

{{Navigation|previous=AI and Scholarship}}

{{BookCat}}</text>
      <sha1>os61cq3npdotus8p7lir4ipe5s0tuma</sha1>
    </revision>
  </page>
  <page>
    <title>General Literary Chinese from Scratch/How Characters are Made</title>
    <ns>0</ns>
    <id>484050</id>
    <revision>
      <id>4656096</id>
      <parentid>4641270</parentid>
      <timestamp>2026-08-02T19:57:22Z</timestamp>
      <contributor>
        <username>Shira the Mogul</username>
        <id>3560559</id>
      </contributor>
      <minor />
      <comment>/* Ideogrammic compounds */</comment>
      <origin>4656096</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="4120" sha1="qo04tgv7z5hxy0hbne6wl52zojv21qu" xml:space="preserve">This lesson will teach you how Han characters are made. 

So far, we have mostly focused on pictographic characters, those that are just heavily abstracted pictures of things that were important to the ancient Chinese people. However, there are only so many pictures that one can remember until it becomes unfeasible, right?

Let me introduce you to a text by the Heian ({{lang|zh|平安}}) poet, Kiyohara no Sanemoto ({{lang|zh|清原真友}}) of Japan. You are not required to understand what it means at this time. I want you to look at the characters themselves before reading on, for about 10 minutes.

&lt;blockquote&gt;
《字訓詩》&lt;br&gt;
禾失曾知秩，中心豈忘忠。里魚穿浪鯉，江鳥度秋鴻。

火盡仍為燼，山高自作嵩。色絲辭不絕，凡虫泣寒風。
&lt;/blockquote&gt;

Isn't there something strange about the character choices? Perhaps there is a method to it all.

Indeed, for each couplet, the first two characters form the fifth. The poem does in fact have meaning:
&lt;blockquote&gt;
The Poem on Character Interpretation&lt;br&gt;
The grain, though lost, still knows its order; its heart, though unwavering, never forgets loyalty. Fish dart through the waves like carp; river birds fly across in autumn like wild geese.

Even when the fire is extinguished, it remains as ashes; even when the mountain is high, it remains majestic like Mt. Song. The silken threads of life continue their farewell; even the common insects weep in the cold wind.
&lt;/blockquote&gt;

So what we have learned here, just by gazing at that poem, is that each character is made from others. This is where the next two character categories come in: Phono-semantic compounds and ideogrammic compounds. 

==Ideogrammic compounds==
Ideogrammic compounds ({{lang|zh|會意}} &quot;joined ideas&quot;) consist of two semantic objects being placed together to form a new one. The first two compounds you learned in this book, {{lang|zh|林}} and {{lang|zh|森}}, are examples of this phenomenon. To give another example, ({{lang|zh|典}}) &quot;law, classic, documentation&quot; consists of books ({{lang|zh|冊}}) on a table ({{lang|zh|丌}}).
&lt;gallery&gt;
冊-bronze.svg
丌-bronze.svg
典-bronze.svg
&lt;/gallery&gt;

Ideogrammic compounds are quite rare in Chinese literature, but become more common in Japanese literature. For example, {{lang|zh|働}} &quot;to work&quot; is formed from {{lang|zh|人}} &quot;person&quot; {{lang|zh|動}} &quot;move&quot;. 

If you put the sun ({{lang|zh|日}}) and moon ({{lang|zh|月}}) together to make ({{lang|zh|明}}, what do you think it could represent?

==Phono-semantic compounds==
Phono-semantic compounds ({{lang|zh|形聲}}) consist of one semantic character with another character next to it to serve as the sound. Most characters are formed through this method, making up around 80% of the Han script. Therefore, it is useful to learn a pronunciation with which to associate characters with sounds, even if it is not intended to be used productively.

Let's take ({{lang|zh|人}} and ({{lang|zh|山}} for a moment to make ({{lang|zh|仙}}. 
&lt;gallery&gt;
人-bigseal-2.svg
山-bigseal.svg
File:ACC-L06562.svg
&lt;/gallery&gt;
This gets across &quot;a man on a mountain,&quot; though it is more abstract: It refers to an [[w:Xian (Taoism)|Daoist immortal]], which usually involves mountain symbolism. Mountain is pronounced ''shan'' in Mandarin Chinese, and this character would be pronounced ''xian'' (like shee-en). See the similarity? Oftentimes phono-semantic compounds try to be related, though this is not always the case. You can take these characters at face-value as if they were phonetic script, where the semantic characters are hints.

Semantic components are usually of concrete meaning: horse {{lang|zh|馬}}，{{lang|zh|鼠}}，and {{lang|zh|鳥}} will almost always have a phonetic component on the left, and usually be about a type of that animal. 

==Exercise==
Try looking at the characters you have learned so far from previous lessons, and try to categorise them using the categories you have already learned. I also recommend learning &quot;difficult&quot; ({{lang|zh|難}}) and &quot;heavy&quot; ({{lang|zh|重}}), which will be useful in future lessons.</text>
      <sha1>qo04tgv7z5hxy0hbne6wl52zojv21qu</sha1>
    </revision>
  </page>
  <page>
    <title>Wikibooks:Reading room/Administrative Assistance/Archives/2026/July</title>
    <ns>4</ns>
    <id>484829</id>
    <revision>
      <id>4656177</id>
      <parentid>4656039</parentid>
      <timestamp>2026-08-03T08:10:16Z</timestamp>
      <contributor>
        <username>ArchiverBot</username>
        <id>1227662</id>
      </contributor>
      <minor />
      <comment>Bot: Archiving 2 threads from [[Wikibooks:Reading room/Administrative Assistance]]</comment>
      <origin>4656177</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="11679" sha1="3bos6njru38wpx5di90mqv6qudsj8lh" xml:space="preserve">{{talk archive}}

== Bestdealsautofla reported by MathXplore ==

* {{userlinks|Bestdealsautofla}}

Spam &lt;!-- USERREPORTED:/Bestdealsautofla/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:19, 2 July 2026 (UTC)

:{{done}} —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:26, 3 July 2026 (UTC)

== Cthrucleaningsolutionso reported by MathXplore ==

* {{userlinks|Cthrucleaningsolutionso}}

advertising &lt;!-- USERREPORTED:/Cthrucleaningsolutionso/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 22:19, 2 July 2026 (UTC)

:{{done|Sandbox deleted}} —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:26, 3 July 2026 (UTC)
:: The user was blocked indefinitely as a spam-only account. [[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]]) 01:47, 3 July 2026 (UTC)
== Prudhvifmsdh reported by MathXplore ==

* {{userlinks|Prudhvifmsdh}}

Spam &lt;!-- USERREPORTED:/Prudhvifmsdh/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:39, 8 July 2026 (UTC)
: {{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]]) 13:07, 8 July 2026 (UTC)
== Protecting Pages ==

Hello, Admins,

My name is Kayden Swanson, and I have proudly created ''[[The Geoguide]].'' But I would like to remove the ability for fellow users to edit it to prevent vandalism and preserve my prized creation I have made for school. Could you permanently lock it so others cant edit it while I still can? [[User:Kayden Swanson|Kayden Swanson]] ([[User talk:Kayden Swanson|discuss]] • [[Special:Contributions/Kayden Swanson|contribs]]) 02:41, 6 July 2026 (UTC)

:Hi @[[User:Kayden Swanson|Kayden Swanson]]! Unfortunately, that is not an appropriate justification for protecting a page here at Wikibooks per the [[Wikibooks:Protection policy|protection policy]]. Notably, {{tq|&quot;Preemptive full protection of pages is contrary to the open nature of Wikibooks&quot;}}. Cheers —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 19:15, 6 July 2026 (UTC)
::NOOOOOOOOOOOOOOOOOOOOOOOOOOOOO okay that's fine  [[User:Kayden Swanson|Kayden Swanson]] ([[User talk:Kayden Swanson|discuss]] • [[Special:Contributions/Kayden Swanson|contribs]]) 00:26, 8 July 2026 (UTC)
::: I'm sorry, but that's not within the scope of the protection policy. [[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]]) 12:39, 8 July 2026 (UTC)
:::If you really want a stable version, you can make a PDF of the existing content and link it. See [[Help:Print versions]] and {{tl|Print version}}/{{tl|PDF version}}. ―[[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:15, 10 July 2026 (UTC)

== I'm unable to create a page ==

Hello, I wanted to created the page [[English in Use/Agreement]]. I thought I would use a modified version of a Wikipedia article (https://en.wikipedia.org/wiki/Agreement_in_the_English_language). It's already written like a textbook, so I did some improvements and clicked &quot;published&quot;, but I got the error:

&lt;blockquote&gt;Welcome to Wikibooks!Your edit has triggered an automated filter and has been disallowed. It looks like your edit has added a large amount of content to this page.If you copied the content from another website, please do not add it without rewriting it in your own words. Unless the content is in the public domain (published before 1923), it is almost certainly copyrighted and cannot be added to Wikibooks.If all of the content is your own work and you cannot find anything to link, feel free to ask for the edit to be performed at the reading room. If you have received this message in error, you may report it here.&lt;/blockquote&gt;

What should I do? Can you help me? [[User:Justtocreateapage|Justtocreateapage]] ([[User talk:Justtocreateapage|discuss]] • [[Special:Contributions/Justtocreateapage|contribs]]) 20:43, 10 July 2026 (UTC)

:@[[User:Justtocreateapage|Justtocreateapage]] An editfilter is preventing your edit. In my opinion, you did not do anything wrong and the filter is wrong, but an admin (=not me) would need to fix it. [[User:Der-Wir-Ing|Der-Wir-Ing]] ([[User talk:Der-Wir-Ing|discuss]] • [[Special:Contributions/Der-Wir-Ing|contribs]]) 20:52, 10 July 2026 (UTC)
:: {{re|Justtocreateapage}} As a new user you face harsher requirements. You should make useful edits to Wikibooks first. If you want to use a modified version of a WP article, [[Wikibooks: Requests for import|requesting an import]] is the proper venue. This [[Help: Importing|preserves the edit history]]. ‑‑[[User:Kai Burghardt|Kai Burghardt]] ([[User talk:Kai Burghardt|discuss]] • [[Special:Contributions/Kai Burghardt|contribs]]) 21:15, 10 July 2026 (UTC)
:::Okay, thanks you all. I'll request for an import then [[User:Justtocreateapage|Justtocreateapage]] ([[User talk:Justtocreateapage|discuss]] • [[Special:Contributions/Justtocreateapage|contribs]]) 21:39, 10 July 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; 21:50, 10 July 2026 (UTC)
== Unprotection/edit request ==

Hi, would an admin please temporarily unprotect the non-MediaWiki pages at [[User:TenshiBot/Errors]]? As for the MediaWiki pages, would an admin go through them and replace the &lt;nowiki&gt;&lt;center&gt;&lt;/nowiki&gt; tags and replace it with &lt;nowiki&gt;&lt;div style=&quot;text-align: center&quot;&gt;&lt;/nowiki&gt;? [[User:Tenshi Hinanawi|Tenshi Hinanawi]] ([[User talk:Tenshi Hinanawi|discuss]] • [[Special:Contributions/Tenshi Hinanawi|contribs]]) 23:10, 11 July 2026 (UTC)
: Unprotecting, fixing, and protecting back would take too long—I know just the thing, which is using JWB. [[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:35, 12 July 2026 (UTC)
: [[User:Tenshi Hinanawi|Tenshi Hinanawi]], I've done what JWB could process; should there be way more in your bot's error log, let me know. [[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]]) 03:02, 12 July 2026 (UTC)
::There's still a lot of the &lt;nowiki&gt;&lt;font&gt;&lt;/nowiki&gt; tags which need replacing in the talk page archives. [[User:Tenshi Hinanawi|Tenshi Hinanawi]] ([[User talk:Tenshi Hinanawi|discuss]] • [[Special:Contributions/Tenshi Hinanawi|contribs]]) 10:11, 12 July 2026 (UTC)
::: I can replace those, but should it be &lt;code&gt;div&lt;/code&gt; or &lt;code&gt;span&lt;/code&gt;? [[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]]) 14:35, 12 July 2026 (UTC)
::::Span, though the font tag's parameters need to be converted as well, see [https://github.com/TenshiSWR/TenshiBot/blob/958b59d1a5e14a31ab8b46f66db54ebdba63e101/tasks/linterrors/obsolete_HTML_tags.py#L15-L52 the code] and the [https://html.spec.whatwg.org/multipage/rendering.html#:~:text=When%20a%20font%20element%20has%20a%20color,%27color%27%20property%20to%20the%20resulting%20color. HTML spec] for this. [[User:Tenshi Hinanawi|Tenshi Hinanawi]] ([[User talk:Tenshi Hinanawi|discuss]] • [[Special:Contributions/Tenshi Hinanawi|contribs]]) 14:56, 12 July 2026 (UTC)
== Emirati yahzota reported by MathXplore ==

* {{userlinks|Emirati yahzota}}

Long-term abuse, [[:w:Wikipedia:Sockpuppet investigations/Muhammad Ali Rajab]] &lt;!-- USERREPORTED:/Emirati yahzota/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:18, 2 July 2026 (UTC)

:I deleted their page addition. @[[User:MarcGarver|MarcGarver]] could we get a CU here? Thanks! —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 01:28, 3 July 2026 (UTC)
::Nothing to see on CU. [[User:MarcGarver|MarcGarver]] ([[User talk:MarcGarver|discuss]] • [[Special:Contributions/MarcGarver|contribs]]) 11:07, 13 July 2026 (UTC)

== NSSGGuarding reported by MathXplore ==

* {{userlinks|NSSGGuarding}}

Spam &lt;!-- USERREPORTED:/NSSGGuarding/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:17, 13 July 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; 16:45, 13 July 2026 (UTC)
== Tanzeemdigital reported by MathXplore ==

* {{userlinks|Tanzeemdigital}}

Spam, [[Special:AbuseLog/314706]] &lt;!-- USERREPORTED:/Tanzeemdigital/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:08, 15 July 2026 (UTC)
== Faisalorakzaii reported by MathXplore ==

* {{userlinks|Faisalorakzaii}}

cross-wiki abuse, [[:w:WP:AB]]. &lt;!-- USERREPORTED:/Faisalorakzaii/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 12:13, 15 July 2026 (UTC)

:{{done|Page deleted}} —[[User:Kittycataclysm|Kittycataclysm]] ([[User talk:Kittycataclysm|discuss]] • [[Special:Contributions/Kittycataclysm|contribs]]) 12:56, 15 July 2026 (UTC)
== Drpriyajaganathan reported by MathXplore ==

* {{userlinks|Drpriyajaganathan}}

Spam &lt;!-- USERREPORTED:/Drpriyajaganathan/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 10:46, 18 July 2026 (UTC)

:What do you find as spam ?  [[Special:Contributions/&amp;#126;2026-40412-29|&amp;#126;2026-40412-29]] ([[User talk:&amp;#126;2026-40412-29|talk]]) 12:20, 18 July 2026 (UTC)
== WinniJoy reported by MathXplore ==

* {{userlinks|WinniJoy}}

Spam &lt;!-- USERREPORTED:/WinniJoy/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 10:48, 18 July 2026 (UTC)
: {{done}}. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 19:00, 19 July 2026 (UTC)

== ~2026-40144-05 reported by MathXplore ==

* {{userlinks|~2026-40144-05}}

Spam &lt;!-- USERREPORTED:/~2026-40144-05/ --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 11:17, 19 July 2026 (UTC)
: I blocked them for creating out of scope pages. [[User:Codename Noreste|Codename Noreste]] ([[User talk:Codename Noreste|discuss]] • [[Special:Contributions/Codename Noreste|contribs]]) 18:59, 19 July 2026 (UTC)</text>
      <sha1>3bos6njru38wpx5di90mqv6qudsj8lh</sha1>
    </revision>
  </page>
  <page>
    <title>History : Alorre Gorge</title>
    <ns>0</ns>
    <id>485036</id>
    <revision>
      <id>4656048</id>
      <timestamp>2026-08-02T15:02:05Z</timestamp>
      <contributor>
        <username>Duodeca 12</username>
        <id>3615790</id>
      </contributor>
      <comment>Created page with &quot;Alorre Gorge is a steep ravine in Tanzania and a paleoanthropological locality.  ===Geology=== Millions of years ago, the region had a paleo lake (Lake Alorre). Around 600,000 to 500,000 years ago, there was a seismic (earthquake - related) event that created the gorge we know today. ===Paleoanthropology=== In 1975, there was a fossilized hominid found in the locality, known as Alorre Hominin 1 (AH 1). It was fragmentary, just a collection of teeth, and was the holotype...&quot;</comment>
      <origin>4656048</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="533" sha1="9u6k0n6grkjjhfhkbvwx7xb0u1su1x0" xml:space="preserve">Alorre Gorge is a steep ravine in Tanzania and a paleoanthropological locality. 
===Geology===
Millions of years ago, the region had a paleo lake (Lake Alorre). Around 600,000 to 500,000 years ago, there was a seismic (earthquake - related) event that created the gorge we know today.
===Paleoanthropology===
In 1975, there was a fossilized hominid found in the locality, known as Alorre Hominin 1 (AH 1). It was fragmentary, just a collection of teeth, and was the holotype for the species. AH 2 was found in 1994 and was a cranium.</text>
      <sha1>9u6k0n6grkjjhfhkbvwx7xb0u1su1x0</sha1>
    </revision>
    <revision>
      <id>4656049</id>
      <parentid>4656048</parentid>
      <timestamp>2026-08-02T15:03:21Z</timestamp>
      <contributor>
        <username>Quinlan83</username>
        <id>3290607</id>
      </contributor>
      <comment>Requesting speedy deletion (Test page). (TwinkleGlobal)</comment>
      <origin>4656049</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="556" sha1="f8m1l8aobr36lzpp92zpl7y40zu5fbe" xml:space="preserve">{{Delete|1=Test page}}
Alorre Gorge is a steep ravine in Tanzania and a paleoanthropological locality. 
===Geology===
Millions of years ago, the region had a paleo lake (Lake Alorre). Around 600,000 to 500,000 years ago, there was a seismic (earthquake - related) event that created the gorge we know today.
===Paleoanthropology===
In 1975, there was a fossilized hominid found in the locality, known as Alorre Hominin 1 (AH 1). It was fragmentary, just a collection of teeth, and was the holotype for the species. AH 2 was found in 1994 and was a cranium.</text>
      <sha1>f8m1l8aobr36lzpp92zpl7y40zu5fbe</sha1>
    </revision>
    <revision>
      <id>4656098</id>
      <parentid>4656049</parentid>
      <timestamp>2026-08-02T20:25:26Z</timestamp>
      <contributor>
        <username>Codename Noreste</username>
        <id>3441010</id>
      </contributor>
      <comment>Not a test page.</comment>
      <origin>4656098</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="533" sha1="9u6k0n6grkjjhfhkbvwx7xb0u1su1x0" xml:space="preserve">Alorre Gorge is a steep ravine in Tanzania and a paleoanthropological locality. 
===Geology===
Millions of years ago, the region had a paleo lake (Lake Alorre). Around 600,000 to 500,000 years ago, there was a seismic (earthquake - related) event that created the gorge we know today.
===Paleoanthropology===
In 1975, there was a fossilized hominid found in the locality, known as Alorre Hominin 1 (AH 1). It was fragmentary, just a collection of teeth, and was the holotype for the species. AH 2 was found in 1994 and was a cranium.</text>
      <sha1>9u6k0n6grkjjhfhkbvwx7xb0u1su1x0</sha1>
    </revision>
    <revision>
      <id>4656100</id>
      <parentid>4656098</parentid>
      <timestamp>2026-08-02T20:26:14Z</timestamp>
      <contributor>
        <username>Codename Noreste</username>
        <id>3441010</id>
      </contributor>
      <comment>Adding {{qr-scope}} tag</comment>
      <origin>4656100</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="546" sha1="4x7zogo08q557kuksfhjsjp1zrqslpr" xml:space="preserve">{{qr-scope}}
Alorre Gorge is a steep ravine in Tanzania and a paleoanthropological locality. 
===Geology===
Millions of years ago, the region had a paleo lake (Lake Alorre). Around 600,000 to 500,000 years ago, there was a seismic (earthquake - related) event that created the gorge we know today.
===Paleoanthropology===
In 1975, there was a fossilized hominid found in the locality, known as Alorre Hominin 1 (AH 1). It was fragmentary, just a collection of teeth, and was the holotype for the species. AH 2 was found in 1994 and was a cranium.</text>
      <sha1>4x7zogo08q557kuksfhjsjp1zrqslpr</sha1>
    </revision>
    <revision>
      <id>4656152</id>
      <parentid>4656100</parentid>
      <timestamp>2026-08-03T01:19:33Z</timestamp>
      <contributor>
        <username>Duodeca 12</username>
        <id>3615790</id>
      </contributor>
      <minor />
      <comment>/* */</comment>
      <origin>4656152</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="597" sha1="n6zvns2t53stvkt82j2kg26a71y7yby" xml:space="preserve">{{qr-scope}}
Alorre Gorge is a steep ravine in Tanzania and a paleoanthropological locality. 

Chapters include 

Geology 

Paleoanthropology   
===Geology===
Millions of years ago, the region had a paleo lake (Lake Alorre). Around 600,000 to 500,000 years ago, there was a seismic (earthquake - related) event that created the gorge we know today.
===Paleoanthropology===
In 1975, there was a fossilized hominid found in the locality, known as Alorre Hominin 1 (AH 1). It was fragmentary, just a collection of teeth, and was the holotype for the species. AH 2 was found in 1994 and was a cranium.</text>
      <sha1>n6zvns2t53stvkt82j2kg26a71y7yby</sha1>
    </revision>
  </page>
  <page>
    <title>User:Duodeca 12</title>
    <ns>2</ns>
    <id>485037</id>
    <revision>
      <id>4656051</id>
      <timestamp>2026-08-02T15:19:23Z</timestamp>
      <contributor>
        <username>Duodeca 12</username>
        <id>3615790</id>
      </contributor>
      <comment>/* */</comment>
      <origin>4656051</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="101" sha1="8mw4q9gd92dy8h96sc2tspwehn8w12u" xml:space="preserve">{{User administrator}}{{User bureaucrat}}{{User Wikipedia admin}}

{{Userrights}}

{{User checkuser}}</text>
      <sha1>8mw4q9gd92dy8h96sc2tspwehn8w12u</sha1>
    </revision>
    <revision>
      <id>4656105</id>
      <parentid>4656051</parentid>
      <timestamp>2026-08-02T20:33:48Z</timestamp>
      <contributor>
        <username>Kittycataclysm</username>
        <id>3371989</id>
      </contributor>
      <comment>rm misleading information</comment>
      <origin>4656105</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="14" sha1="14j92g76bl80d2yo2ftavoq9x7f9wdj" xml:space="preserve">{{Userrights}}</text>
      <sha1>14j92g76bl80d2yo2ftavoq9x7f9wdj</sha1>
    </revision>
    <revision>
      <id>4656106</id>
      <parentid>4656105</parentid>
      <timestamp>2026-08-02T20:38:07Z</timestamp>
      <contributor>
        <username>Duodeca 12</username>
        <id>3615790</id>
      </contributor>
      <minor />
      <comment>/* */</comment>
      <origin>4656106</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="76" sha1="d0imz5badzve5z9tbbzk7yghq5l0mwe" xml:space="preserve">


{{User more userboxes}}


{{User book}}{{User chrome}}{{User checkuser}}</text>
      <sha1>d0imz5badzve5z9tbbzk7yghq5l0mwe</sha1>
    </revision>
  </page>
  <page>
    <title>General Literary Chinese from Scratch/Dinner with the Daimyo</title>
    <ns>0</ns>
    <id>485038</id>
    <revision>
      <id>4656056</id>
      <timestamp>2026-08-02T16:59:55Z</timestamp>
      <contributor>
        <username>Shira the Mogul</username>
        <id>3560559</id>
      </contributor>
      <comment>I'm going to make pages out of the content I currently have so it doesn't clog up the main page. This also gives people something to look at whilst the book continues development.</comment>
      <origin>4656056</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="332" sha1="okil8k7nprwsi0uvhcgv1g1q7bij7yn" xml:space="preserve">Comment to be written.

== Text ==
=== 侍宴·大友皇子 ===
&lt;poem&gt;
皇明光日月，帝徳載天地。
三才併秦昌，万国表臣義。
&lt;/poem&gt;

==References==
* Shi, K. (Ed.). (2024). 日本汉诗选 [Anthology of Japanese Sinitic Poetry] (1st ed, Vols 1–2). 江西教育出版社 [Jiangxi Education Press].

{{BookCat}}</text>
      <sha1>okil8k7nprwsi0uvhcgv1g1q7bij7yn</sha1>
    </revision>
    <revision>
      <id>4656087</id>
      <parentid>4656056</parentid>
      <timestamp>2026-08-02T18:22:50Z</timestamp>
      <contributor>
        <username>Shira the Mogul</username>
        <id>3560559</id>
      </contributor>
      <minor />
      <origin>4656087</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="385" sha1="n5spqery0vlv2k57w1erd3wqkuyj7kn" xml:space="preserve">[[File:Emperor Kōbun.jpg|thumb|200px|大友皇子]]
Comment to be written.

== Text ==
=== 侍宴·大友皇子 ===
&lt;poem&gt;
皇明光日月，帝徳載天地。
三才併秦昌，万国表臣義。
&lt;/poem&gt;

==References==
* Shi, K. (Ed.). (2024). 日本汉诗选 [Anthology of Japanese Sinitic Poetry] (1st ed, Vols 1–2). 江西教育出版社 [Jiangxi Education Press].

{{BookCat}}</text>
      <sha1>n5spqery0vlv2k57w1erd3wqkuyj7kn</sha1>
    </revision>
  </page>
  <page>
    <title>General Literary Chinese from Scratch/In Discourse with Jibong</title>
    <ns>0</ns>
    <id>485039</id>
    <revision>
      <id>4656057</id>
      <timestamp>2026-08-02T17:01:13Z</timestamp>
      <contributor>
        <username>Shira the Mogul</username>
        <id>3560559</id>
      </contributor>
      <comment>Created page with &quot;Comment to be written.  == Text == === 芝峰類說·李睟光 === &lt;blockquote&gt; 倭國謂田爲畠。謂水田爲田。火田爲畑。猶我國以水田爲畓也。故官名有畠山殿。地名有畑島云。 &lt;/blockquote&gt;  ==References== * 《芝峰類說·李睟光》&quot;</comment>
      <origin>4656057</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="271" sha1="ev390y3h8miihxwp05d04whitfnqmqx" xml:space="preserve">Comment to be written.

== Text ==
=== 芝峰類說·李睟光 ===
&lt;blockquote&gt;
倭國謂田爲畠。謂水田爲田。火田爲畑。猶我國以水田爲畓也。故官名有畠山殿。地名有畑島云。
&lt;/blockquote&gt;

==References==
* 《芝峰類說·李睟光》</text>
      <sha1>ev390y3h8miihxwp05d04whitfnqmqx</sha1>
    </revision>
    <revision>
      <id>4656058</id>
      <parentid>4656057</parentid>
      <timestamp>2026-08-02T17:01:26Z</timestamp>
      <contributor>
        <username>Shira the Mogul</username>
        <id>3560559</id>
      </contributor>
      <minor />
      <origin>4656058</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="284" sha1="3j4070yelq8yla36nv3813kzql8ngkg" xml:space="preserve">Comment to be written.

== Text ==
=== 芝峰類說·李睟光 ===
&lt;blockquote&gt;
倭國謂田爲畠。謂水田爲田。火田爲畑。猶我國以水田爲畓也。故官名有畠山殿。地名有畑島云。
&lt;/blockquote&gt;

==References==
* 《芝峰類說·李睟光》

{{BookCat}}</text>
      <sha1>3j4070yelq8yla36nv3813kzql8ngkg</sha1>
    </revision>
  </page>
  <page>
    <title>General Literary Chinese from Scratch/Across the Rivers with Emperor Puliuru Guang</title>
    <ns>0</ns>
    <id>485040</id>
    <revision>
      <id>4656059</id>
      <timestamp>2026-08-02T17:05:24Z</timestamp>
      <contributor>
        <username>Shira the Mogul</username>
        <id>3560559</id>
      </contributor>
      <comment>Created page with &quot;Comment to be written.  == Text == === 春江花月夜·楊廣 === &lt;poem&gt; 夜露含花氣，春潭漾月暉。 漢水逢遊女，湘川值二妃。 &lt;/poem&gt;  ==References== * 《春江花月夜·楊廣》Available at: https://zh.wikisource.org/zh-hant/%E6%98%A5%E6%B1%9F%E8%8A%B1%E6%9C%88%E5%A4%9C_(%E6%A5%8A%E5%BB%A3)  {{BookCat}}&quot;</comment>
      <origin>4656059</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="330" sha1="3r0esev5734t1n9g70j97lg1ako3agc" xml:space="preserve">Comment to be written.

== Text ==
=== 春江花月夜·楊廣 ===
&lt;poem&gt;
夜露含花氣，春潭漾月暉。
漢水逢遊女，湘川值二妃。
&lt;/poem&gt;

==References==
* 《春江花月夜·楊廣》Available at: https://zh.wikisource.org/zh-hant/%E6%98%A5%E6%B1%9F%E8%8A%B1%E6%9C%88%E5%A4%9C_(%E6%A5%8A%E5%BB%A3)

{{BookCat}}</text>
      <sha1>3r0esev5734t1n9g70j97lg1ako3agc</sha1>
    </revision>
  </page>
  <page>
    <title>General Literary Chinese from Scratch/To Study the Odes</title>
    <ns>0</ns>
    <id>485041</id>
    <revision>
      <id>4656060</id>
      <timestamp>2026-08-02T17:09:18Z</timestamp>
      <contributor>
        <username>Shira the Mogul</username>
        <id>3560559</id>
      </contributor>
      <comment>Created page with &quot;Comment to be written.  ==Text== ===蟋蟀·姬旦 國風·唐風=== 蟋蟀在堂，歲聿其莫。今我不樂，日月其除。無已大康，職思其居。好樂無荒，良士瞿瞿。 蟋蟀在堂，歲聿其逝。今我不樂，日月其邁。無已大康，職思其外。好樂無荒，良士蹶蹶。 蟋蟀在堂，役車其休。今我不樂，日月其慆。無已大康，職思其憂。好樂無荒，良士休休。  ==References== * Deng, Q. (2013). 诗经 [...&quot;</comment>
      <origin>4656060</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="897" sha1="7q6mpnr7kx6r7vjv6a2rt8xeqvlf1vw" xml:space="preserve">Comment to be written.

==Text==
===蟋蟀·姬旦 國風·唐風===
蟋蟀在堂，歲聿其莫。今我不樂，日月其除。無已大康，職思其居。好樂無荒，良士瞿瞿。
蟋蟀在堂，歲聿其逝。今我不樂，日月其邁。無已大康，職思其外。好樂無荒，良士蹶蹶。
蟋蟀在堂，役車其休。今我不樂，日月其慆。無已大康，職思其憂。好樂無荒，良士休休。

==References==
* Deng, Q. (2013). 诗经 [Classic of Poetry] (Q. Kong, Ed.; 2nd ed, Vols 1–2). 东南大学出版社 [Southeast University Press].
* 《蟋蟀·姬旦 國風·唐風》Available at: https://www.fanyahanwen-corpus.cn/corpus_viewer/%E4%B8%AD%E5%9C%8B%E6%BC%A2%E6%96%87/clean/%E5%91%A8%E6%9C%9D/%E6%9D%B1%E5%91%A8/%E6%88%B0%E5%9C%8B%E6%99%82%E4%BB%A3/%E5%91%A8/%E8%A9%A9%E7%B6%93/%E5%9C%8B%E9%A2%A8/%E5%94%90%E9%A2%A8/%E8%9F%8B%E8%9F%80

{{BookCat}}</text>
      <sha1>7q6mpnr7kx6r7vjv6a2rt8xeqvlf1vw</sha1>
    </revision>
    <revision>
      <id>4656061</id>
      <parentid>4656060</parentid>
      <timestamp>2026-08-02T17:09:49Z</timestamp>
      <contributor>
        <username>Shira the Mogul</username>
        <id>3560559</id>
      </contributor>
      <minor />
      <origin>4656061</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1285" sha1="qffun5ki6aut27yvsg390z4triije4s" xml:space="preserve">Comment to be written.

==Text==
===蟋蟀·姬旦 國風·唐風===
&lt;poem&gt;
蟋蟀在堂，歲聿其莫。今我不樂，日月其除。無已大康，職思其居。好樂無荒，良士瞿瞿。
蟋蟀在堂，歲聿其逝。今我不樂，日月其邁。無已大康，職思其外。好樂無荒，良士蹶蹶。
蟋蟀在堂，役車其休。今我不樂，日月其慆。無已大康，職思其憂。好樂無荒，良士休休。
&lt;/poem&gt;

===黃鳥 小雅·鴻鴈之什===
&lt;poem&gt;
黃鳥黃鳥，無集于穀，無啄我粟。
此邦之人，不我肯穀。言旋言歸，復我邦族。

黃鳥黃鳥，無集于桑，無啄我粱。
此邦之人，不可與明。言旋言歸，復我諸兄。

黃鳥黃鳥，無集于栩，無啄我黍。
此邦之人，不可與處。言旋言歸，復我諸父。
&lt;/poem&gt;

==References==
* Deng, Q. (2013). 诗经 [Classic of Poetry] (Q. Kong, Ed.; 2nd ed, Vols 1–2). 东南大学出版社 [Southeast University Press].
* 《蟋蟀·姬旦 國風·唐風》Available at: https://www.fanyahanwen-corpus.cn/corpus_viewer/%E4%B8%AD%E5%9C%8B%E6%BC%A2%E6%96%87/clean/%E5%91%A8%E6%9C%9D/%E6%9D%B1%E5%91%A8/%E6%88%B0%E5%9C%8B%E6%99%82%E4%BB%A3/%E5%91%A8/%E8%A9%A9%E7%B6%93/%E5%9C%8B%E9%A2%A8/%E5%94%90%E9%A2%A8/%E8%9F%8B%E8%9F%80

{{BookCat}}</text>
      <sha1>qffun5ki6aut27yvsg390z4triije4s</sha1>
    </revision>
  </page>
  <page>
    <title>General Literary Chinese from Scratch/The Environment with Bukha Timur</title>
    <ns>0</ns>
    <id>485042</id>
    <revision>
      <id>4656062</id>
      <timestamp>2026-08-02T17:11:52Z</timestamp>
      <contributor>
        <username>Shira the Mogul</username>
        <id>3560559</id>
      </contributor>
      <comment>Created page with &quot;Comment to be written.  == Text == ===西湖竹枝詞·布哈特穆爾=== &lt;poem&gt; 湖上春歸人未歸，桃紅柳緑黄鶯飛。 桃花落時多結子，楊花落處秪沾衣。 &lt;/poem&gt;  ===宫词·布哈特穆爾=== &lt;poem&gt; 玉樓珠箔晚天涼，秋色依稀滿建章。 金井梧桐霜葉盡，自隨流水出宮牆。 &lt;/poem&gt;  ==References== * 《御選四朝詩》Available at: https://zh.wikisource.org/wiki/%E5%BE%A1%E9%81%B8%E5%9B%9B%E6%9C%9D%E8%A9%A9_(%E5%9B%9B%E5%...&quot;</comment>
      <origin>4656062</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="521" sha1="aqop1uohllc6raerelxq9i0jgjhltis" xml:space="preserve">Comment to be written.

== Text ==
===西湖竹枝詞·布哈特穆爾===
&lt;poem&gt;
湖上春歸人未歸，桃紅柳緑黄鶯飛。
桃花落時多結子，楊花落處秪沾衣。
&lt;/poem&gt;

===宫词·布哈特穆爾===
&lt;poem&gt;
玉樓珠箔晚天涼，秋色依稀滿建章。
金井梧桐霜葉盡，自隨流水出宮牆。
&lt;/poem&gt;

==References==
* 《御選四朝詩》Available at: https://zh.wikisource.org/wiki/%E5%BE%A1%E9%81%B8%E5%9B%9B%E6%9C%9D%E8%A9%A9_(%E5%9B%9B%E5%BA%AB%E5%85%A8%E6%9B%B8%E6%9C%AC)

{{BookCat}}</text>
      <sha1>aqop1uohllc6raerelxq9i0jgjhltis</sha1>
    </revision>
  </page>
  <page>
    <title>General Literary Chinese from Scratch/Expressing Filial Conduct with Confucius and Hara Saihin</title>
    <ns>0</ns>
    <id>485043</id>
    <revision>
      <id>4656063</id>
      <timestamp>2026-08-02T17:15:20Z</timestamp>
      <contributor>
        <username>Shira the Mogul</username>
        <id>3560559</id>
      </contributor>
      <comment>Created page with &quot;Comment to be written.  ==Text== ===次韻杏坪先生·原采蘋=== &lt;poem&gt; 父執有君孤不孤 相依遍接搢紳徒 区区自抱地方寸 杳杳重遊天一隅 羇雁飛鳴迷汝國 家人思夢入江都 如教志業青年遂 世上寧無逐臭夫 &lt;/poem&gt;  ==References== * 福島理子, &amp; 安江良介. (1995). 女流 (1st ed). 株式會社.  {{BookCat}}&quot;</comment>
      <origin>4656063</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="359" sha1="aljyyp33q37nc4irn0w47pjxhvlx51n" xml:space="preserve">Comment to be written.

==Text==
===次韻杏坪先生·原采蘋===
&lt;poem&gt;
父執有君孤不孤
相依遍接搢紳徒
区区自抱地方寸
杳杳重遊天一隅
羇雁飛鳴迷汝國
家人思夢入江都
如教志業青年遂
世上寧無逐臭夫
&lt;/poem&gt;

==References==
* 福島理子, &amp; 安江良介. (1995). 女流 (1st ed). 株式會社.

{{BookCat}}</text>
      <sha1>aljyyp33q37nc4irn0w47pjxhvlx51n</sha1>
    </revision>
  </page>
  <page>
    <title>General Literary Chinese from Scratch/Remonstrance with Dasese</title>
    <ns>0</ns>
    <id>485044</id>
    <revision>
      <id>4656064</id>
      <timestamp>2026-08-02T17:17:09Z</timestamp>
      <contributor>
        <username>Shira the Mogul</username>
        <id>3560559</id>
      </contributor>
      <comment>Created page with &quot;Comment to be written.  ==Background== Dasese ({{lang|zh|萧瑟瑟}}) was a Khitan consort to Emperor Tianzuo of Liao. She remonstrated him as the Jurchens were beginning to encroach upon the Khitan, and was forced to commit suicide for her remonstrance. Tianzuo would soon pay for his malfeasance.   ==Text== ===諷諫歌·大瑟瑟=== &lt;poem&gt; 勿嗟塞上兮暗紅塵。 勿傷多難兮畏夷人。 不如塞奸邪之路兮選取賢臣。 直須臥薪嚐膽兮激壯士之...&quot;</comment>
      <origin>4656064</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="586" sha1="8x3mz08vd7a9nof2cma9jk2dyuf4y3f" xml:space="preserve">Comment to be written.

==Background==
Dasese ({{lang|zh|萧瑟瑟}}) was a Khitan consort to Emperor Tianzuo of Liao. She remonstrated him as the Jurchens were beginning to encroach upon the Khitan, and was forced to commit suicide for her remonstrance. Tianzuo would soon pay for his malfeasance. 

==Text==
===諷諫歌·大瑟瑟===
&lt;poem&gt;
勿嗟塞上兮暗紅塵。
勿傷多難兮畏夷人。
不如塞奸邪之路兮選取賢臣。
直須臥薪嚐膽兮激壯士之捐身。
可以朝清漠北兮夕枕燕雲。
&lt;/poem&gt;

==References==
* 《遼史》七一本傳。

{{BookCat}}</text>
      <sha1>8x3mz08vd7a9nof2cma9jk2dyuf4y3f</sha1>
    </revision>
  </page>
  <page>
    <title>General Literary Chinese from Scratch/The Love Songs of the Odes</title>
    <ns>0</ns>
    <id>485045</id>
    <revision>
      <id>4656065</id>
      <timestamp>2026-08-02T17:20:54Z</timestamp>
      <contributor>
        <username>Shira the Mogul</username>
        <id>3560559</id>
      </contributor>
      <comment>I have a very solid outline of what I want here, it just needs to be fleshed out with the timetable fit in mind</comment>
      <origin>4656065</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1214" sha1="6cprw1v0wgrl2se9nso0ruqm38wake9" xml:space="preserve">Comment to be written.

==The female voice of the Odes==
Comment to be written.

==Text==
===褰裳===
&lt;poem&gt;
子惠思我，褰裳涉溱。子不我思，豈無他人？狂童之狂也且！
子惠思我，褰裳涉洧。子不我思，豈無他士？狂童之狂也且！
&lt;/poem&gt;

===柏舟===
&lt;poem&gt;
彼柏舟，在彼中河，髧彼兩髦，實維我儀，之死矢靡它，母也天只，不諒人只。
汎彼柏舟，在彼河側，髧彼兩髦，實維我特，之死矢靡慝，母也天只，不諒人只。
&lt;/poem&gt;

===行露===
&lt;poem&gt;
厭浥行露，豈不夙夜，謂行多露。
誰謂雀無角？何以穿我屋？誰謂女無家？何以速我獄？雖速我獄，室家不足。
誰謂鼠無牙？何以穿我墉？誰謂女無家？何以速我訟？雖速我訟，亦不女從。
&lt;/poem&gt;

==References==
* Broughton, M. K. (2016). Not Straying: Mao tradition interpretations of Shijing love poems. [Bachelor’s dissertation, University of Melbourne]. https://mbchinese.com.au/wp-content/uploads/2020/01/Michael-Broughton-Chinese-Honours-Thesis.pdf
* Deng, Q. (2013). 诗经 [Classic of Poetry] (Q. Kong, Ed.; 2nd ed, Vols 1–2). 东南大学出版社 [Southeast University Press].

{{BookCat}}</text>
      <sha1>6cprw1v0wgrl2se9nso0ruqm38wake9</sha1>
    </revision>
  </page>
  <page>
    <title>General Literary Chinese from Scratch/Oh, the Qilin!</title>
    <ns>0</ns>
    <id>485046</id>
    <revision>
      <id>4656066</id>
      <timestamp>2026-08-02T17:23:01Z</timestamp>
      <contributor>
        <username>Shira the Mogul</username>
        <id>3560559</id>
      </contributor>
      <comment>Created page with &quot;[[File:Chinese - Dragon - Walters 492425 - Profile.jpg|thumb|200px|麒麟]] Comment to be written.  ==Text== ===麟之趾=== &lt;poem&gt; 麟之趾，振振公子，于嗟麟兮。 麟之定，振振公姓，于嗟麟兮。 麟之角，振振公族，于嗟麟兮。 &lt;/poem&gt;  ==References== * Deng, Q. (2013). 诗经 [Classic of Poetry] (Q. Kong, Ed.; 2nd ed, Vols 1–2). 东南大学出版社 [Southeast University Press].  {{BookCat}}&quot;</comment>
      <origin>4656066</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="431" sha1="4yihr50rdbqphecv2hq9wt05dm0d3up" xml:space="preserve">[[File:Chinese - Dragon - Walters 492425 - Profile.jpg|thumb|200px|麒麟]]
Comment to be written.

==Text==
===麟之趾===
&lt;poem&gt;
麟之趾，振振公子，于嗟麟兮。
麟之定，振振公姓，于嗟麟兮。
麟之角，振振公族，于嗟麟兮。
&lt;/poem&gt;

==References==
* Deng, Q. (2013). 诗经 [Classic of Poetry] (Q. Kong, Ed.; 2nd ed, Vols 1–2). 东南大学出版社 [Southeast University Press].

{{BookCat}}</text>
      <sha1>4yihr50rdbqphecv2hq9wt05dm0d3up</sha1>
    </revision>
  </page>
  <page>
    <title>General Literary Chinese from Scratch/The Inariyama Sword</title>
    <ns>0</ns>
    <id>485047</id>
    <revision>
      <id>4656068</id>
      <timestamp>2026-08-02T17:35:52Z</timestamp>
      <contributor>
        <username>Shira the Mogul</username>
        <id>3560559</id>
      </contributor>
      <comment>Created page with &quot;Comment to be written.  ==Text== This text uses Man'yōgana ({{lang|zh|万葉仮名}}) to denote Japanese names. The Man'yōgana usage has been underlined for you in Chinese tradition.   * &lt;u&gt;This is a person's name.&lt;/u&gt; * &lt;u style=&quot;text-decoration:underline; text-decoration-style:double;&quot;&gt;This is a placename.&lt;/u&gt;  An image of the characters on the sword have also been included for you to look at! ===稲荷山剣·乎获居臣=== {{Tall image|稲荷山古墳出土鉄剣...&quot;</comment>
      <origin>4656068</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1489" sha1="clv0t613x2zcplq4ngcv7zahalm1xhh" xml:space="preserve">Comment to be written.

==Text==
This text uses Man'yōgana ({{lang|zh|万葉仮名}}) to denote Japanese names. The Man'yōgana usage has been underlined for you in Chinese tradition. 

* &lt;u&gt;This is a person's name.&lt;/u&gt;
* &lt;u style=&quot;text-decoration:underline; text-decoration-style:double;&quot;&gt;This is a placename.&lt;/u&gt;

An image of the characters on the sword have also been included for you to look at!
===稲荷山剣·乎获居臣===
{{Tall image|稲荷山古墳出土鉄剣 (表面) (cropped).JPG|3=200|4=前}}
&lt;blockquote&gt;
辛亥年七月中記&lt;br&gt;
&lt;u&gt;乎獲居臣&lt;/u&gt;&lt;br&gt;
上祖名&lt;u&gt;意富比垝&lt;/u&gt;&lt;br&gt;
其児&lt;u&gt;多加利足尼&lt;/u&gt;&lt;br&gt;
其児名&lt;u&gt;弖已加利獲居&lt;/u&gt;&lt;br&gt;
其児名&lt;u&gt;多加披次獲居&lt;/u&gt;&lt;br&gt;
其児名&lt;u&gt;多沙鬼獲居&lt;/u&gt;&lt;br&gt;
其児&lt;u&gt;名半弖比&lt;/u&gt;&lt;br&gt;
&lt;/blockquote&gt;

{{Tall image|稲荷山古墳出土鉄剣 (裏面) (cropped).JPG|3=200|4=后}}
&lt;blockquote&gt;
其児名&lt;u&gt;加差披余&lt;/u&gt;&lt;br&gt;
其児名&lt;u&gt;乎獲居臣&lt;/u&gt;&lt;br&gt;
世世爲杖刀人首&lt;br&gt;
奉事來至今&lt;br&gt;
&lt;u&gt;獲加多支鹵&lt;/u&gt;&lt;u&gt;大王&lt;/u&gt;寺在&lt;u style=&quot;text-decoration:underline; text-decoration-style:double;&quot;&gt;斯鬼宮&lt;/u&gt;時&lt;br&gt;
吾左治天下&lt;br&gt;
令作此百練利刀&lt;br&gt;
記吾奉事根原也&lt;br&gt;
&lt;/blockquote&gt;

==References==
* 埼玉古墳群 in 泛亞漢文語料庫. Available at: https://www.fanyahanwen-corpus.cn/corpus_viewer/%E6%97%A5%E6%9C%AC%E6%BC%A2%E6%96%87/clean/%E5%80%AD/%E5%8F%A4%E5%A2%B3%E6%99%82%E4%BB%A3/%E5%9F%BC%E7%8E%89%E5%8F%A4%E5%A2%B3%E7%BE%A4

{{BookCat}}</text>
      <sha1>clv0t613x2zcplq4ngcv7zahalm1xhh</sha1>
    </revision>
  </page>
  <page>
    <title>General Literary Chinese from Scratch/Entering Japan with Takeda Shingen</title>
    <ns>0</ns>
    <id>485048</id>
    <revision>
      <id>4656069</id>
      <timestamp>2026-08-02T17:37:29Z</timestamp>
      <contributor>
        <username>Shira the Mogul</username>
        <id>3560559</id>
      </contributor>
      <comment>Created page with &quot;[[File:Takeda Shingen.jpg|thumb|200px|武田信玄]] Comment to be written.  ==Text== ===便面蘆間有漁·武田信玄=== 山色水光烟接天，漁翁江上棹蘆辺 丹青若写得勝景，万里風波一釣船  便面半月照梅花·武田信玄 蘆葦清風垂頂絲，窺魚白鷺水生涯 江南記得曾遊夕，似見梨花院落時  ==References== * 島森哲男. (2015). 武田信玄漢詩校釈. 宮城教育大学紀要, 49, 333–352. https://mue.repo.nii.a...&quot;</comment>
      <origin>4656069</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="504" sha1="e1jv1l0hcfmhl750rb5s5mwgbfntnep" xml:space="preserve">[[File:Takeda Shingen.jpg|thumb|200px|武田信玄]]
Comment to be written.

==Text==
===便面蘆間有漁·武田信玄===
山色水光烟接天，漁翁江上棹蘆辺
丹青若写得勝景，万里風波一釣船

便面半月照梅花·武田信玄
蘆葦清風垂頂絲，窺魚白鷺水生涯
江南記得曾遊夕，似見梨花院落時

==References==
* 島森哲男. (2015). 武田信玄漢詩校釈. 宮城教育大学紀要, 49, 333–352. https://mue.repo.nii.ac.jp/records/440

{{BookCat}}</text>
      <sha1>e1jv1l0hcfmhl750rb5s5mwgbfntnep</sha1>
    </revision>
    <revision>
      <id>4656070</id>
      <parentid>4656069</parentid>
      <timestamp>2026-08-02T17:37:57Z</timestamp>
      <contributor>
        <username>Shira the Mogul</username>
        <id>3560559</id>
      </contributor>
      <minor />
      <origin>4656070</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="540" sha1="mc537ey2rvguig6buugav8v5690oyhx" xml:space="preserve">[[File:Takeda Shingen.jpg|thumb|200px|武田信玄]]
Comment to be written.

==Text==
===便面蘆間有漁·武田信玄===
&lt;poem&gt;
山色水光烟接天，漁翁江上棹蘆辺
丹青若写得勝景，万里風波一釣船
&lt;/poem&gt;

===便面半月照梅花·武田信玄===
&lt;poem&gt;
蘆葦清風垂頂絲，窺魚白鷺水生涯
江南記得曾遊夕，似見梨花院落時
&lt;/poem&gt;

==References==
* 島森哲男. (2015). 武田信玄漢詩校釈. 宮城教育大学紀要, 49, 333–352. https://mue.repo.nii.ac.jp/records/440

{{BookCat}}</text>
      <sha1>mc537ey2rvguig6buugav8v5690oyhx</sha1>
    </revision>
  </page>
  <page>
    <title>General Literary Chinese from Scratch/The End of a Rebellion</title>
    <ns>0</ns>
    <id>485049</id>
    <revision>
      <id>4656072</id>
      <timestamp>2026-08-02T17:50:17Z</timestamp>
      <contributor>
        <username>Shira the Mogul</username>
        <id>3560559</id>
      </contributor>
      <comment>This aims to be filial conduct-centred to build on the Confucian unit</comment>
      <origin>4656072</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1321" sha1="j4db8rpz21hdqalfwkfmrvuh5s5k2ch" xml:space="preserve">[[File:Enomoto Takeaki2.jpg|thumb|200px|榎本武揚]]
[[File:Seal of Ezo.svg|thumb|200px]]
Comment to be written.

==Background==
Enomoto Takeaki ({{lang|zh|榎本武揚}}) was one of the founders of the breakaway Republic of Ezo ({{lang|zh|蝦夷共和國}}) at the tail-end of the Edo period. It remained loyal to the Tokugawa Shogunate during the restoration of Emperor Meiji and put up a fairly ferocious fight before being brought down. Takeaki would be trialled for high treason, but pardoned due to his extensive talents in Dutch, naval warfare, and Western science. 

==Text==
===在海牙府·榎本武揚===
&lt;poem&gt;
乾坤到處吾做廬
酔即喚茶醒閲書
老母不知何慰所
今年又是倚門閭
負笈殊邦萬里身
復迎元治二年春
朝来盥嗽向東拝
鬢髪添霜有老親

在海牙府迎春
五八兄属書
武揚
&lt;/poem&gt;

==Questions==
* What themes do you see in this poem that you can derive from what you have seen before?

==References==
* Kamo, Giichi. Enomoto Takeaki. Chuo Koronsha ISBN 4-12-201509-X (Japanese)
* 在海牙府 in 泛亞漢文語料庫. https://www.fanyahanwen-corpus.cn/corpus_viewer/%E6%97%A5%E6%9C%AC%E6%BC%A2%E6%96%87/clean/%E6%97%A5%E6%9C%AC/%E6%B1%9F%E6%88%B8%E6%99%82%E4%BB%A3/%E8%9D%A6%E5%A4%B7%E5%85%B1%E5%92%8C%E5%9B%BD/%E5%9C%A8%E6%B5%B7%E7%89%99%E5%BA%9C</text>
      <sha1>j4db8rpz21hdqalfwkfmrvuh5s5k2ch</sha1>
    </revision>
    <revision>
      <id>4656149</id>
      <parentid>4656072</parentid>
      <timestamp>2026-08-03T00:17:39Z</timestamp>
      <contributor>
        <username>MathXplore</username>
        <id>3097823</id>
      </contributor>
      <minor />
      <comment>Added {{[[Template:BookCat|BookCat]]}} using [[User:1234qwer1234qwer4/BookCat.js|BookCat.js]]</comment>
      <origin>4656149</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1334" sha1="lhtvk5ukqs1b3vzh5ik56azko36g8vs" xml:space="preserve">[[File:Enomoto Takeaki2.jpg|thumb|200px|榎本武揚]]
[[File:Seal of Ezo.svg|thumb|200px]]
Comment to be written.

==Background==
Enomoto Takeaki ({{lang|zh|榎本武揚}}) was one of the founders of the breakaway Republic of Ezo ({{lang|zh|蝦夷共和國}}) at the tail-end of the Edo period. It remained loyal to the Tokugawa Shogunate during the restoration of Emperor Meiji and put up a fairly ferocious fight before being brought down. Takeaki would be trialled for high treason, but pardoned due to his extensive talents in Dutch, naval warfare, and Western science. 

==Text==
===在海牙府·榎本武揚===
&lt;poem&gt;
乾坤到處吾做廬
酔即喚茶醒閲書
老母不知何慰所
今年又是倚門閭
負笈殊邦萬里身
復迎元治二年春
朝来盥嗽向東拝
鬢髪添霜有老親

在海牙府迎春
五八兄属書
武揚
&lt;/poem&gt;

==Questions==
* What themes do you see in this poem that you can derive from what you have seen before?

==References==
* Kamo, Giichi. Enomoto Takeaki. Chuo Koronsha ISBN 4-12-201509-X (Japanese)
* 在海牙府 in 泛亞漢文語料庫. https://www.fanyahanwen-corpus.cn/corpus_viewer/%E6%97%A5%E6%9C%AC%E6%BC%A2%E6%96%87/clean/%E6%97%A5%E6%9C%AC/%E6%B1%9F%E6%88%B8%E6%99%82%E4%BB%A3/%E8%9D%A6%E5%A4%B7%E5%85%B1%E5%92%8C%E5%9B%BD/%E5%9C%A8%E6%B5%B7%E7%89%99%E5%BA%9C

{{BookCat}}</text>
      <sha1>lhtvk5ukqs1b3vzh5ik56azko36g8vs</sha1>
    </revision>
  </page>
  <page>
    <title>General Literary Chinese from Scratch/The Enthronement of Shō Tei</title>
    <ns>0</ns>
    <id>485050</id>
    <revision>
      <id>4656073</id>
      <timestamp>2026-08-02T17:52:44Z</timestamp>
      <contributor>
        <username>Shira the Mogul</username>
        <id>3560559</id>
      </contributor>
      <comment>Created page with &quot;[[File:King Sho Tei.jpg|thumb|200px|尚貞]] Comment to be written.  ==Text== ===康熙二十二年封王尚貞敕=== 皇帝敕諭琉球國中山王世子尚貞：惟爾遠處海隅，虔修職貢；屬在塚嗣，序應承祧。以朝命未膺，罔敢專擅；恪遵典制，奉表請封。朕念爾世守臣節，忠誠可嘉！特遣正使翰林院檢討汪楫、副使內閣中書舍人加一級林麟焻，齎敕封爾為琉球國中山王，並賜爾及妃文幣等物...&quot;</comment>
      <origin>4656073</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="728" sha1="h10ewi09txqxxws9k7ytxjojy3z9lc8" xml:space="preserve">[[File:King Sho Tei.jpg|thumb|200px|尚貞]]
Comment to be written.

==Text==
===康熙二十二年封王尚貞敕===
皇帝敕諭琉球國中山王世子尚貞：惟爾遠處海隅，虔修職貢；屬在塚嗣，序應承祧。以朝命未膺，罔敢專擅；恪遵典制，奉表請封。朕念爾世守臣節，忠誠可嘉！特遣正使翰林院檢討汪楫、副使內閣中書舍人加一級林麟焻，齎敕封爾為琉球國中山王，並賜爾及妃文幣等物。爾祗承寵眷，懋紹先猷；輯和臣民，慎固封守：用安宗社於苞桑，永作天家之屏翰。欽哉，毋替朕命！故諭。

==References==
* 琉球國志略 in Chinese Text Project. https://ctext.org/wiki.pl?if=en&amp;chapter=966326</text>
      <sha1>h10ewi09txqxxws9k7ytxjojy3z9lc8</sha1>
    </revision>
    <revision>
      <id>4656074</id>
      <parentid>4656073</parentid>
      <timestamp>2026-08-02T17:52:54Z</timestamp>
      <contributor>
        <username>Shira the Mogul</username>
        <id>3560559</id>
      </contributor>
      <minor />
      <origin>4656074</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="741" sha1="pwvcvovbcgyak36y624i4s2osw1imus" xml:space="preserve">[[File:King Sho Tei.jpg|thumb|200px|尚貞]]
Comment to be written.

==Text==
===康熙二十二年封王尚貞敕===
皇帝敕諭琉球國中山王世子尚貞：惟爾遠處海隅，虔修職貢；屬在塚嗣，序應承祧。以朝命未膺，罔敢專擅；恪遵典制，奉表請封。朕念爾世守臣節，忠誠可嘉！特遣正使翰林院檢討汪楫、副使內閣中書舍人加一級林麟焻，齎敕封爾為琉球國中山王，並賜爾及妃文幣等物。爾祗承寵眷，懋紹先猷；輯和臣民，慎固封守：用安宗社於苞桑，永作天家之屏翰。欽哉，毋替朕命！故諭。

==References==
* 琉球國志略 in Chinese Text Project. https://ctext.org/wiki.pl?if=en&amp;chapter=966326

{{BookCat}}</text>
      <sha1>pwvcvovbcgyak36y624i4s2osw1imus</sha1>
    </revision>
  </page>
  <page>
    <title>Talk:History : Alorre Gorge</title>
    <ns>1</ns>
    <id>485051</id>
    <revision>
      <id>4656075</id>
      <timestamp>2026-08-02T17:53:34Z</timestamp>
      <contributor>
        <username>Duodeca 12</username>
        <id>3615790</id>
      </contributor>
      <comment>/* It doesn't need speedy */ new section</comment>
      <origin>4656075</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="221" sha1="8aejq3gmy92s4o73migo30i3hndem84" xml:space="preserve">== It doesn't need speedy  ==

it is a real place albeit niche not a test page [[User:Duodeca 12|Duodeca 12]] ([[User talk:Duodeca 12|discuss]] • [[Special:Contributions/Duodeca 12|contribs]]) 17:53, 2 August 2026 (UTC)</text>
      <sha1>8aejq3gmy92s4o73migo30i3hndem84</sha1>
    </revision>
  </page>
  <page>
    <title>General Literary Chinese from Scratch/An Edict from the Xianbei</title>
    <ns>0</ns>
    <id>485052</id>
    <revision>
      <id>4656076</id>
      <timestamp>2026-08-02T17:55:14Z</timestamp>
      <contributor>
        <username>Shira the Mogul</username>
        <id>3560559</id>
      </contributor>
      <comment>Created page with &quot;Comment to be written.  ==Text== ===教義詔·楊廣=== &lt;blockquote&gt; 武有七德，先之以安民。政有六本，興之以教義。高麗高元，虧失藩禮，將欲問罪遼左，恢宣勝略。雖懷伐國，仍事省方。今往涿郡，巡撫民俗。其河北諸郡及山西、山東年九十已上者，版授太守；八十者，授縣令。 &lt;/blockquote&gt;  ==References== * 《教義詔·楊廣》Available at: https://zh.wikisource.org/wiki/%E6%95%99%E7%BE%A9%...&quot;</comment>
      <origin>4656076</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="496" sha1="5mr4mb9la5o87zq57pos606476d36bt" xml:space="preserve">Comment to be written.

==Text==
===教義詔·楊廣===
&lt;blockquote&gt;
武有七德，先之以安民。政有六本，興之以教義。高麗高元，虧失藩禮，將欲問罪遼左，恢宣勝略。雖懷伐國，仍事省方。今往涿郡，巡撫民俗。其河北諸郡及山西、山東年九十已上者，版授太守；八十者，授縣令。
&lt;/blockquote&gt;

==References==
* 《教義詔·楊廣》Available at: https://zh.wikisource.org/wiki/%E6%95%99%E7%BE%A9%E8%A9%94

{{BookCat}}</text>
      <sha1>5mr4mb9la5o87zq57pos606476d36bt</sha1>
    </revision>
  </page>
  <page>
    <title>General Literary Chinese from Scratch/The Shunzhi Emperor vs Li Zicheng</title>
    <ns>0</ns>
    <id>485053</id>
    <revision>
      <id>4656080</id>
      <timestamp>2026-08-02T17:58:32Z</timestamp>
      <contributor>
        <username>Shira the Mogul</username>
        <id>3560559</id>
      </contributor>
      <comment>This one is going to encourage writing analysis!</comment>
      <origin>4656080</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="947" sha1="hofqvj1bhhlsk811zax1rdjbxpmc2kd" xml:space="preserve">[[File:李自成行宫 (cropped).png|thumb|200px|李梓誠]]
Comment to be written.

==Text==
===告示·順治帝===
&lt;blockquote&gt;
逆酋李自成已於通城斃命，各地鄉勇務隨我軍剿殺逆賊殘餘,凡有斬獲逆酋及擒獲逆酋交我軍者，一經驗證，按軍功論級給賞，必以示我朝皇恩浩蕩。&lt;br&gt;
大清順治二年五月二十四日
&lt;/blockquote&gt;

===恩詔·李梓誠===
&lt;blockquote&gt;
今月何日，為國曆改歲之履端,即為永昌書元之紀念？緬惟我朝民眾，三元肇慶，四始發祥。陳椒酒以飛觴，躋堂介壽；換桃符以獻歲，辟戶書新。翹望德容，河勝額手。今山河如舊，歲序更新;今天下同春，咸頒麗澤。願我朝君臣與萬民同樂，共沐化日光天，方不虛度韶華。&lt;br&gt;
永昌二年新正初一
&lt;/blockquote&gt;

==References==
* Huang, W. (2010). 大順史稿 [Draft History of the Great Shun]. ISBN: 978-7-80736-899-1

{{BookCat}}</text>
      <sha1>hofqvj1bhhlsk811zax1rdjbxpmc2kd</sha1>
    </revision>
  </page>
  <page>
    <title>General Literary Chinese from Scratch/Fū! Rin! Ka! Zan!</title>
    <ns>0</ns>
    <id>485054</id>
    <revision>
      <id>4656084</id>
      <timestamp>2026-08-02T18:10:27Z</timestamp>
      <contributor>
        <username>Shira the Mogul</username>
        <id>3560559</id>
      </contributor>
      <comment>Created page with &quot;[[File:吴司马孙武.jpg|thumb|200px|孫武]] [[File:Takeda Daizen no tayū Harunobu Nyūdō Shingen.jpg|thumb|武田信玄]] If you are familiar with Japanese military history or historical fiction, you are probably familiar with the phrase ''Fūrinkazan''. Literally, it is 風林火山, and was used by Takeda Shingen as a war standard. The phrase is actually an abbreviation from Sun Zi's Art of War 孫子兵法, and the full quotation is what we are going to look at...&quot;</comment>
      <origin>4656084</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="990" sha1="ivbf2rrugm0aacyg8vzhnbkm55tjm0e" xml:space="preserve">[[File:吴司马孙武.jpg|thumb|200px|孫武]]
[[File:Takeda Daizen no tayū Harunobu Nyūdō Shingen.jpg|thumb|武田信玄]]
If you are familiar with Japanese military history or historical fiction, you are probably familiar with the phrase ''Fūrinkazan''. Literally, it is 風林火山, and was used by Takeda Shingen as a war standard. The phrase is actually an abbreviation from Sun Zi's Art of War 孫子兵法, and the full quotation is what we are going to look at today. 

Comment to be written.

==Text==
===孫子兵法===
&lt;blockquote&gt;
故其疾如風，其徐如林&lt;br&gt;
侵掠如火，不動如山
&lt;/blockquote&gt;

The banner version presents itself without some of the function words, like so:
&lt;blockquote&gt;
疾如風徐如林侵&lt;br&gt;
掠如火不動如山
&lt;/blockquote&gt;

==References==
* Sun, W. (2018). 孙子兵法 [Sun Zi on The Art of War] (M. Li, P. Liang, &amp; L. Giles, Trans.; 1st ed.). 中州古籍出版社 [Zhongzhou Ancient Books Publishing House].
* 《甲陽軍鑑》</text>
      <sha1>ivbf2rrugm0aacyg8vzhnbkm55tjm0e</sha1>
    </revision>
    <revision>
      <id>4656148</id>
      <parentid>4656084</parentid>
      <timestamp>2026-08-03T00:17:00Z</timestamp>
      <contributor>
        <username>MathXplore</username>
        <id>3097823</id>
      </contributor>
      <minor />
      <comment>Added {{[[Template:BookCat|BookCat]]}} using [[User:1234qwer1234qwer4/BookCat.js|BookCat.js]]</comment>
      <origin>4656148</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1003" sha1="kth3n1atonvkfcah6qvjtumnxf4zyth" xml:space="preserve">[[File:吴司马孙武.jpg|thumb|200px|孫武]]
[[File:Takeda Daizen no tayū Harunobu Nyūdō Shingen.jpg|thumb|武田信玄]]
If you are familiar with Japanese military history or historical fiction, you are probably familiar with the phrase ''Fūrinkazan''. Literally, it is 風林火山, and was used by Takeda Shingen as a war standard. The phrase is actually an abbreviation from Sun Zi's Art of War 孫子兵法, and the full quotation is what we are going to look at today. 

Comment to be written.

==Text==
===孫子兵法===
&lt;blockquote&gt;
故其疾如風，其徐如林&lt;br&gt;
侵掠如火，不動如山
&lt;/blockquote&gt;

The banner version presents itself without some of the function words, like so:
&lt;blockquote&gt;
疾如風徐如林侵&lt;br&gt;
掠如火不動如山
&lt;/blockquote&gt;

==References==
* Sun, W. (2018). 孙子兵法 [Sun Zi on The Art of War] (M. Li, P. Liang, &amp; L. Giles, Trans.; 1st ed.). 中州古籍出版社 [Zhongzhou Ancient Books Publishing House].
* 《甲陽軍鑑》

{{BookCat}}</text>
      <sha1>kth3n1atonvkfcah6qvjtumnxf4zyth</sha1>
    </revision>
  </page>
  <page>
    <title>General Literary Chinese from Scratch/Lament with Lu Ruoteng</title>
    <ns>0</ns>
    <id>485055</id>
    <revision>
      <id>4656085</id>
      <timestamp>2026-08-02T18:13:06Z</timestamp>
      <contributor>
        <username>Shira the Mogul</username>
        <id>3560559</id>
      </contributor>
      <comment>Created page with &quot;Comment to be written.  ==Text== ===疑猜·盧若騰=== &lt;poem&gt; 盟誓變為交質子，春秋戰國風如此；末世上下相疑猜, 更質妻子防逃徙。 此法只可羈庸奴，若遇梟雄術窮矣；妻可再娶子再育, 安能長坐針氈裏。 我贈一法君記存；推心置腹人知恩；眾人畜之眾人報, 幾個國士在君門。 &lt;/poem&gt;  ==References== * 盧若騰撰，陳漢光編輯，《島噫詩》，臺灣文獻叢刊第二四五種（臺北:臺...&quot;</comment>
      <origin>4656085</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="533" sha1="do9nidepbbl8g5w4pktuunuglp4m4lm" xml:space="preserve">Comment to be written.

==Text==
===疑猜·盧若騰===
&lt;poem&gt;
盟誓變為交質子，春秋戰國風如此；末世上下相疑猜, 更質妻子防逃徙。
此法只可羈庸奴，若遇梟雄術窮矣；妻可再娶子再育, 安能長坐針氈裏。
我贈一法君記存；推心置腹人知恩；眾人畜之眾人報, 幾個國士在君門。
&lt;/poem&gt;

==References==
* 盧若騰撰，陳漢光編輯，《島噫詩》，臺灣文獻叢刊第二四五種（臺北:臺灣銀行經濟研究室，1968年）21頁。

{{BookCat}}</text>
      <sha1>do9nidepbbl8g5w4pktuunuglp4m4lm</sha1>
    </revision>
  </page>
  <page>
    <title>User:Shira the Mogul/Collections/General Literary Chinese from Scratch</title>
    <ns>2</ns>
    <id>485056</id>
    <revision>
      <id>4656088</id>
      <timestamp>2026-08-02T18:30:02Z</timestamp>
      <contributor>
        <username>Shira the Mogul</username>
        <id>3560559</id>
      </contributor>
      <comment>Created page with &quot;{{saved book  |title=  |subtitle=  |cover-image=  |cover-color=}}  == General Literary Chinese from Scratch == === v.0.1 === :[[General Literary Chinese from Scratch]] :[[General Literary Chinese from Scratch/An Introduction to the Han Script]] :[[General Literary Chinese from Scratch/People, Big and Small]] :[[General Literary Chinese from Scratch/How do we write Chinese?]] :[[General Literary Chinese from Scratch/What are Chinese characters, anyway?]] :General Litera...&quot;</comment>
      <origin>4656088</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2606" sha1="kcla04qdm6vasw8zc2qgoiaagw5rgf7" xml:space="preserve">{{saved book
 |title=
 |subtitle=
 |cover-image=
 |cover-color=}}

== General Literary Chinese from Scratch ==
=== v.0.1 ===
:[[General Literary Chinese from Scratch]]
:[[General Literary Chinese from Scratch/An Introduction to the Han Script]]
:[[General Literary Chinese from Scratch/People, Big and Small]]
:[[General Literary Chinese from Scratch/How do we write Chinese?]]
:[[General Literary Chinese from Scratch/What are Chinese characters, anyway?]]
:[[General Literary Chinese from Scratch/The Sun, the Moon, and the Five Elements]]
:[[General Literary Chinese from Scratch/Getting Familiar with Body Parts]]
:[[General Literary Chinese from Scratch/Using Numbers and Using Weapons]]
:[[General Literary Chinese from Scratch/Tilling the Fields with 有]]
:[[General Literary Chinese from Scratch/How Characters are Made]]
:[[General Literary Chinese from Scratch/Introduction]]
:[[General Literary Chinese from Scratch/Appendices]]
:[[General Literary Chinese from Scratch/The All-Purpose 也]]
:[[General Literary Chinese from Scratch/An Introduction to Chinese Numbers]]
:[[General Literary Chinese from Scratch/One, Two, Left, and Right with Gongsun Long]]
:[[General Literary Chinese from Scratch/The Heavenly Stems]]
:[[General Literary Chinese from Scratch/Tell the Time with Earthly Branches]]
:[[General Literary Chinese from Scratch/Lunar Dates with the Spring and Autumn Annals]]
:[[General Literary Chinese from Scratch/Dinner with the Daimyo]]
:[[General Literary Chinese from Scratch/In Discourse with Jibong]]
:[[General Literary Chinese from Scratch/Across the Rivers with Emperor Puliuru Guang]]
:[[General Literary Chinese from Scratch/To Study the Odes]]
:[[General Literary Chinese from Scratch/The Environment with Bukha Timur]]
:[[General Literary Chinese from Scratch/Expressing Filial Conduct with Confucius and Hara Saihin]]
:[[General Literary Chinese from Scratch/Remonstrance with Dasese]]
:[[General Literary Chinese from Scratch/The Love Songs of the Odes]]
:[[General Literary Chinese from Scratch/Oh, the Qilin!]]
:[[General Literary Chinese from Scratch/The Inariyama Sword]]
:[[General Literary Chinese from Scratch/Entering Japan with Takeda Shingen]]
:[[General Literary Chinese from Scratch/The End of a Rebellion]]
:[[General Literary Chinese from Scratch/The Enthronement of Shō Tei]]
:[[General Literary Chinese from Scratch/Fū! Rin! Ka! Zan!]]
:[[General Literary Chinese from Scratch/An Edict from the Xianbei]]
:[[General Literary Chinese from Scratch/The Shunzhi Emperor vs Li Zicheng]]
:[[General Literary Chinese from Scratch/Lament with Lu Ruoteng]]</text>
      <sha1>kcla04qdm6vasw8zc2qgoiaagw5rgf7</sha1>
    </revision>
  </page>
  <page>
    <title>AgilePM Project Management v3</title>
    <ns>0</ns>
    <id>485057</id>
    <revision>
      <id>4656089</id>
      <timestamp>2026-08-02T18:39:28Z</timestamp>
      <contributor>
        <username>~2026-42669-80</username>
        <id>3618736</id>
      </contributor>
      <comment>AgilePM Project Management v3</comment>
      <origin>4656089</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="29" sha1="0c7144f35pfapv9qinlbr496d41mjvf" xml:space="preserve">AgilePM Project Management v3</text>
      <sha1>0c7144f35pfapv9qinlbr496d41mjvf</sha1>
    </revision>
    <revision>
      <id>4656146</id>
      <parentid>4656089</parentid>
      <timestamp>2026-08-03T00:16:40Z</timestamp>
      <contributor>
        <username>MathXplore</username>
        <id>3097823</id>
      </contributor>
      <comment>Marking for speedy deletion: Test page</comment>
      <origin>4656146</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="87" sha1="ntjdujg383t625n5yuxrnlrd9hr1gx0" xml:space="preserve">&lt;noinclude&gt;{{Delete|example=false|Test page}}&lt;/noinclude&gt;
AgilePM Project Management v3</text>
      <sha1>ntjdujg383t625n5yuxrnlrd9hr1gx0</sha1>
    </revision>
  </page>
  <page>
    <title>Scratch Virtual Machine</title>
    <ns>0</ns>
    <id>485058</id>
    <revision>
      <id>4656090</id>
      <timestamp>2026-08-02T18:41:35Z</timestamp>
      <contributor>
        <username>Some helpful person</username>
        <id>3510188</id>
      </contributor>
      <comment>a book focusing on how Scratch is implemented as a programming language, explaining its functionality and technical aspects in a clear and mostly understandable way</comment>
      <origin>4656090</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="202" sha1="juw13qqetuegzupqb3eldvh1jf43jnf" xml:space="preserve">A deep dive into the inner workings of the [[Scratch]] programming language for the curious.

==[[/Introduction|Introduction]]==

==[[/Features|Features]]==

==[[/Blocks|Blocks]]==

==[[/Files|Files]]==</text>
      <sha1>juw13qqetuegzupqb3eldvh1jf43jnf</sha1>
    </revision>
    <revision>
      <id>4656129</id>
      <parentid>4656090</parentid>
      <timestamp>2026-08-02T22:19:22Z</timestamp>
      <contributor>
        <username>Some helpful person</username>
        <id>3510188</id>
      </contributor>
      <minor />
      <comment>add CCO templates</comment>
      <origin>4656129</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="300" sha1="2es4bq627fqmwntbs73kgj99aqx49m9" xml:space="preserve">{{shelves|Computer programming}}
{{alphabetical|S}}
{{status|0%}}
{{reading level|intermediate}}

A deep dive into the inner workings of the [[Scratch]] programming language for the curious.

==[[/Introduction|Introduction]]==

==[[/Features|Features]]==

==[[/Blocks|Blocks]]==

==[[/Files|Files]]==</text>
      <sha1>2es4bq627fqmwntbs73kgj99aqx49m9</sha1>
    </revision>
  </page>
  <page>
    <title>Scratch Virtual Machine/Introduction</title>
    <ns>0</ns>
    <id>485059</id>
    <revision>
      <id>4656095</id>
      <timestamp>2026-08-02T19:46:54Z</timestamp>
      <contributor>
        <username>Some helpful person</username>
        <id>3510188</id>
      </contributor>
      <comment>Created page with &quot;[[Scratch]] is a visual block-based programming language. Its internals are left intentionally abstract to make coding simpler and easier for younger minds. It is implemented via the '''Scratch Virtual Machine''', a program responsible for maintaining the state of a Scratch project and executing its scripts. This book intends to unearth all of that program's hidden logic and quirks independently of any programming language, such that some or all of it may be clearly unde...&quot;</comment>
      <origin>4656095</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1930" sha1="lrol6gc56y8s9w77e496j67ofva5klg" xml:space="preserve">[[Scratch]] is a visual block-based programming language. Its internals are left intentionally abstract to make coding simpler and easier for younger minds. It is implemented via the '''Scratch Virtual Machine''', a program responsible for maintaining the state of a Scratch project and executing its scripts. This book intends to unearth all of that program's hidden logic and quirks independently of any programming language, such that some or all of it may be clearly understood and reimplemented for any purpose.

==Scope==

This book currently documents Scratch 3.0, which includes all the latest blocks and is mostly backwards compatible with previous versions. Its virtual machine's [https://github.com/scratchfoundation/scratch-editor/tree/develop/packages/scratch-vm source code] and [[JavaScript|language]] will be used for verifiability, with the [https://en.scratch-wiki.info/wiki/Scratch_Wiki_Home Scratch Wiki] and [https://developer.mozilla.org/en-US/docs/Web/JavaScript MDN Web Docs] as supporting resources. Scratch does not normally receive [[wiktionary:breaking change|breaking]] changes, but any major alterations to its official behavior over time will be noted.

Any tutorials included here will help with implementing Scratch. Resources otherwise relating to Scratch should be left to the [[Scratch]] book. Information about specific Scratch Virtual Machines that does not affect the actual behavior of Scratch will generally not be documented, unless such information would aid in furthering understanding.

The inner workings of Scratch will be documented extensively, but within reason. If, for example, an [[wiktionary:exploit#Noun|exploit]] were found that allowed executing arbitrary JavaScript code, this book will not attempt to reinvent all of JavaScript. Explanations of specific web browsers and computer setups will be avoided where possible to ensure Scratch remains flexible in implementation.</text>
      <sha1>lrol6gc56y8s9w77e496j67ofva5klg</sha1>
    </revision>
    <revision>
      <id>4656132</id>
      <parentid>4656095</parentid>
      <timestamp>2026-08-02T22:44:17Z</timestamp>
      <contributor>
        <username>Some helpful person</username>
        <id>3510188</id>
      </contributor>
      <comment>simplify</comment>
      <origin>4656132</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1767" sha1="qlv9seznt7jvumg8key197phsad6uf1" xml:space="preserve">[[Scratch]] is a visual block-based programming language. It is implemented via the '''Scratch Virtual Machine''' ('''VM'''), a program responsible for maintaining the state of a Scratch project and executing its scripts. This book documents its behavior and quirks independently of any programming language so that it may be clearly understood and reimplemented for any purpose.

==Scope==

This book currently documents Scratch 3.0, which is mostly backwards compatible with previous versions. The [https://github.com/scratchfoundation/scratch-editor/tree/develop/packages/scratch-vm source code] of its virtual machine and the behavior of the programming language it is written in ([[JavaScript]]) will be used for verifiability, with the [https://en.scratch-wiki.info/wiki/Scratch_Wiki_Home Scratch Wiki] and [https://developer.mozilla.org/en-US/docs/Web/JavaScript MDN Web Docs] as supporting materials. Changes in Scratch's behavior over time as the result of updates to the VM's code will be noted.

All information included here will relate to implementing Scratch. Resources otherwise relating to Scratch can be found in the [[Scratch|Scratch book]]. Information about specific Scratch Virtual Machines that does not affect the actual behavior of Scratch will generally not be documented, unless such information would further understanding.

The inner workings of Scratch will be documented extensively, but within reason. If, for example, an [[wiktionary:exploit#Noun|exploit]] were found that allowed executing arbitrary JavaScript code, this book will not attempt to reinvent all of JavaScript. Explanations of behaviors on specific web browsers and computer setups will be avoided where possible to ensure Scratch remains flexible in its implementation.</text>
      <sha1>qlv9seznt7jvumg8key197phsad6uf1</sha1>
    </revision>
    <revision>
      <id>4656145</id>
      <parentid>4656132</parentid>
      <timestamp>2026-08-03T00:16:19Z</timestamp>
      <contributor>
        <username>MathXplore</username>
        <id>3097823</id>
      </contributor>
      <minor />
      <comment>Added {{[[Template:BookCat|BookCat]]}} using [[User:1234qwer1234qwer4/BookCat.js|BookCat.js]]</comment>
      <origin>4656145</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1780" sha1="liyo3zfmrxp33vmb0upsrkj44enlxp4" xml:space="preserve">[[Scratch]] is a visual block-based programming language. It is implemented via the '''Scratch Virtual Machine''' ('''VM'''), a program responsible for maintaining the state of a Scratch project and executing its scripts. This book documents its behavior and quirks independently of any programming language so that it may be clearly understood and reimplemented for any purpose.

==Scope==

This book currently documents Scratch 3.0, which is mostly backwards compatible with previous versions. The [https://github.com/scratchfoundation/scratch-editor/tree/develop/packages/scratch-vm source code] of its virtual machine and the behavior of the programming language it is written in ([[JavaScript]]) will be used for verifiability, with the [https://en.scratch-wiki.info/wiki/Scratch_Wiki_Home Scratch Wiki] and [https://developer.mozilla.org/en-US/docs/Web/JavaScript MDN Web Docs] as supporting materials. Changes in Scratch's behavior over time as the result of updates to the VM's code will be noted.

All information included here will relate to implementing Scratch. Resources otherwise relating to Scratch can be found in the [[Scratch|Scratch book]]. Information about specific Scratch Virtual Machines that does not affect the actual behavior of Scratch will generally not be documented, unless such information would further understanding.

The inner workings of Scratch will be documented extensively, but within reason. If, for example, an [[wiktionary:exploit#Noun|exploit]] were found that allowed executing arbitrary JavaScript code, this book will not attempt to reinvent all of JavaScript. Explanations of behaviors on specific web browsers and computer setups will be avoided where possible to ensure Scratch remains flexible in its implementation.

{{BookCat}}</text>
      <sha1>liyo3zfmrxp33vmb0upsrkj44enlxp4</sha1>
    </revision>
  </page>
  <page>
    <title>User talk:Duodeca 12</title>
    <ns>3</ns>
    <id>485060</id>
    <revision>
      <id>4656099</id>
      <timestamp>2026-08-02T20:26:14Z</timestamp>
      <contributor>
        <username>Codename Noreste</username>
        <id>3441010</id>
      </contributor>
      <comment>Notifying author about page tagging</comment>
      <origin>4656099</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="717" sha1="2jerpcm1vwojac2gixwl0l3y085tkse" xml:space="preserve">
== I have added a tag to a page you created ==
Hi! I'm Codename Noreste, and I recently reviewed your page, [[:History : Alorre Gorge]]. I have added a tag to the page, because it &lt;strong&gt;has some problems that need to be looked at.&lt;/strong&gt;I also left you a comment: &lt;blockquote&gt;The book might not be suited for the scope of Wikibooks.&lt;/blockquote&gt; If you have any questions or concerns, please [[User talk:Codename Noreste|let me know]]. Thank you! &lt;!-- Substituted from User:JJPMaster/CurateThisPage/authorMsg --&gt; [[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]]) 20:26, 2 August 2026 (UTC)</text>
      <sha1>2jerpcm1vwojac2gixwl0l3y085tkse</sha1>
    </revision>
    <revision>
      <id>4656101</id>
      <parentid>4656099</parentid>
      <timestamp>2026-08-02T20:26:43Z</timestamp>
      <contributor>
        <username>Duodeca 12</username>
        <id>3615790</id>
      </contributor>
      <comment>/* I have added a tag to a page you created */ Reply</comment>
      <origin>4656101</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="883" sha1="ru7ezkohaiqmmmi6rag6gyhpo7x1nwa" xml:space="preserve">
== I have added a tag to a page you created ==
Hi! I'm Codename Noreste, and I recently reviewed your page, [[:History : Alorre Gorge]]. I have added a tag to the page, because it &lt;strong&gt;has some problems that need to be looked at.&lt;/strong&gt;I also left you a comment: &lt;blockquote&gt;The book might not be suited for the scope of Wikibooks.&lt;/blockquote&gt; If you have any questions or concerns, please [[User talk:Codename Noreste|let me know]]. Thank you! &lt;!-- Substituted from User:JJPMaster/CurateThisPage/authorMsg --&gt; [[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]]) 20:26, 2 August 2026 (UTC)

:how is it not suited [[User:Duodeca 12|Duodeca 12]] ([[User talk:Duodeca 12|discuss]] • [[Special:Contributions/Duodeca 12|contribs]]) 20:26, 2 August 2026 (UTC)</text>
      <sha1>ru7ezkohaiqmmmi6rag6gyhpo7x1nwa</sha1>
    </revision>
    <revision>
      <id>4656102</id>
      <parentid>4656101</parentid>
      <timestamp>2026-08-02T20:27:04Z</timestamp>
      <contributor>
        <username>Duodeca 12</username>
        <id>3615790</id>
      </contributor>
      <comment>/* I have added a tag to a page you created */ Reply</comment>
      <origin>4656102</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1036" sha1="n4hgdi0etvn3pgnh1i29e5dli9zf2wo" xml:space="preserve">
== I have added a tag to a page you created ==
Hi! I'm Codename Noreste, and I recently reviewed your page, [[:History : Alorre Gorge]]. I have added a tag to the page, because it &lt;strong&gt;has some problems that need to be looked at.&lt;/strong&gt;I also left you a comment: &lt;blockquote&gt;The book might not be suited for the scope of Wikibooks.&lt;/blockquote&gt; If you have any questions or concerns, please [[User talk:Codename Noreste|let me know]]. Thank you! &lt;!-- Substituted from User:JJPMaster/CurateThisPage/authorMsg --&gt; [[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]]) 20:26, 2 August 2026 (UTC)

:how is it not suited [[User:Duodeca 12|Duodeca 12]] ([[User talk:Duodeca 12|discuss]] • [[Special:Contributions/Duodeca 12|contribs]]) 20:26, 2 August 2026 (UTC)
::explain [[User:Duodeca 12|Duodeca 12]] ([[User talk:Duodeca 12|discuss]] • [[Special:Contributions/Duodeca 12|contribs]]) 20:27, 2 August 2026 (UTC)</text>
      <sha1>n4hgdi0etvn3pgnh1i29e5dli9zf2wo</sha1>
    </revision>
    <revision>
      <id>4656109</id>
      <parentid>4656102</parentid>
      <timestamp>2026-08-02T20:39:50Z</timestamp>
      <contributor>
        <username>Duodeca 12</username>
        <id>3615790</id>
      </contributor>
      <comment>/* I have added a tag to a page you created */ Reply</comment>
      <origin>4656109</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1209" sha1="qmmwjrixrxlp4nwwmp6g3h56qicy237" xml:space="preserve">
== I have added a tag to a page you created ==
Hi! I'm Codename Noreste, and I recently reviewed your page, [[:History : Alorre Gorge]]. I have added a tag to the page, because it &lt;strong&gt;has some problems that need to be looked at.&lt;/strong&gt;I also left you a comment: &lt;blockquote&gt;The book might not be suited for the scope of Wikibooks.&lt;/blockquote&gt; If you have any questions or concerns, please [[User talk:Codename Noreste|let me know]]. Thank you! &lt;!-- Substituted from User:JJPMaster/CurateThisPage/authorMsg --&gt; [[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]]) 20:26, 2 August 2026 (UTC)

:how is it not suited [[User:Duodeca 12|Duodeca 12]] ([[User talk:Duodeca 12|discuss]] • [[Special:Contributions/Duodeca 12|contribs]]) 20:26, 2 August 2026 (UTC)
::explain [[User:Duodeca 12|Duodeca 12]] ([[User talk:Duodeca 12|discuss]] • [[Special:Contributions/Duodeca 12|contribs]]) 20:27, 2 August 2026 (UTC)
:explain how its not suitable [[User:Duodeca 12|Duodeca 12]] ([[User talk:Duodeca 12|discuss]] • [[Special:Contributions/Duodeca 12|contribs]]) 20:39, 2 August 2026 (UTC)</text>
      <sha1>qmmwjrixrxlp4nwwmp6g3h56qicy237</sha1>
    </revision>
    <revision>
      <id>4656134</id>
      <parentid>4656109</parentid>
      <timestamp>2026-08-02T22:59:40Z</timestamp>
      <contributor>
        <username>Codename Noreste</username>
        <id>3441010</id>
      </contributor>
      <comment>/* I have added a tag to a page you created */ reply to Duodeca 12 ([[mw:c:Special:MyLanguage/User:JWBTH/CD|CD]])</comment>
      <origin>4656134</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1592" sha1="mbre9xdn66ny4r33rug2n5vtpzk59rz" xml:space="preserve">
== I have added a tag to a page you created ==
Hi! I'm Codename Noreste, and I recently reviewed your page, [[:History : Alorre Gorge]]. I have added a tag to the page, because it &lt;strong&gt;has some problems that need to be looked at.&lt;/strong&gt;I also left you a comment: &lt;blockquote&gt;The book might not be suited for the scope of Wikibooks.&lt;/blockquote&gt; If you have any questions or concerns, please [[User talk:Codename Noreste|let me know]]. Thank you! &lt;!-- Substituted from User:JJPMaster/CurateThisPage/authorMsg --&gt; [[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]]) 20:26, 2 August 2026 (UTC)

:how is it not suited [[User:Duodeca 12|Duodeca 12]] ([[User talk:Duodeca 12|discuss]] • [[Special:Contributions/Duodeca 12|contribs]]) 20:26, 2 August 2026 (UTC)
::explain [[User:Duodeca 12|Duodeca 12]] ([[User talk:Duodeca 12|discuss]] • [[Special:Contributions/Duodeca 12|contribs]]) 20:27, 2 August 2026 (UTC)
:explain how its not suitable [[User:Duodeca 12|Duodeca 12]] ([[User talk:Duodeca 12|discuss]] • [[Special:Contributions/Duodeca 12|contribs]]) 20:39, 2 August 2026 (UTC)
:: The page appears more like a Wikipedia article, which doesn't fit the scope of Wikibooks per [[WB:NOT]]. If needed, I can move the book to your userspace where you can work on it. [[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:59, 2 August 2026 (UTC)</text>
      <sha1>mbre9xdn66ny4r33rug2n5vtpzk59rz</sha1>
    </revision>
    <revision>
      <id>4656150</id>
      <parentid>4656134</parentid>
      <timestamp>2026-08-03T01:02:20Z</timestamp>
      <contributor>
        <username>Duodeca 12</username>
        <id>3615790</id>
      </contributor>
      <comment>/* I have added a tag to a page you created */ Reply</comment>
      <origin>4656150</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1791" sha1="49utgs6hdwxfux6cd951rzzq7kcleff" xml:space="preserve">
== I have added a tag to a page you created ==
Hi! I'm Codename Noreste, and I recently reviewed your page, [[:History : Alorre Gorge]]. I have added a tag to the page, because it &lt;strong&gt;has some problems that need to be looked at.&lt;/strong&gt;I also left you a comment: &lt;blockquote&gt;The book might not be suited for the scope of Wikibooks.&lt;/blockquote&gt; If you have any questions or concerns, please [[User talk:Codename Noreste|let me know]]. Thank you! &lt;!-- Substituted from User:JJPMaster/CurateThisPage/authorMsg --&gt; [[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]]) 20:26, 2 August 2026 (UTC)

:how is it not suited [[User:Duodeca 12|Duodeca 12]] ([[User talk:Duodeca 12|discuss]] • [[Special:Contributions/Duodeca 12|contribs]]) 20:26, 2 August 2026 (UTC)
::explain [[User:Duodeca 12|Duodeca 12]] ([[User talk:Duodeca 12|discuss]] • [[Special:Contributions/Duodeca 12|contribs]]) 20:27, 2 August 2026 (UTC)
:explain how its not suitable [[User:Duodeca 12|Duodeca 12]] ([[User talk:Duodeca 12|discuss]] • [[Special:Contributions/Duodeca 12|contribs]]) 20:39, 2 August 2026 (UTC)
:: The page appears more like a Wikipedia article, which doesn't fit the scope of Wikibooks per [[WB:NOT]]. If needed, I can move the book to your userspace where you can work on it. [[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:59, 2 August 2026 (UTC)
:::or you could fix the structuring of it and clean up. [[User:Duodeca 12|Duodeca 12]] ([[User talk:Duodeca 12|discuss]] • [[Special:Contributions/Duodeca 12|contribs]]) 01:02, 3 August 2026 (UTC)</text>
      <sha1>49utgs6hdwxfux6cd951rzzq7kcleff</sha1>
    </revision>
    <revision>
      <id>4656153</id>
      <parentid>4656150</parentid>
      <timestamp>2026-08-03T01:20:21Z</timestamp>
      <contributor>
        <username>Duodeca 12</username>
        <id>3615790</id>
      </contributor>
      <comment>/* I have added a tag to a page you created */ Reply</comment>
      <origin>4656153</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="1986" sha1="sve7ef1ncgu80t8vzhv3a63pdnbgiwd" xml:space="preserve">
== I have added a tag to a page you created ==
Hi! I'm Codename Noreste, and I recently reviewed your page, [[:History : Alorre Gorge]]. I have added a tag to the page, because it &lt;strong&gt;has some problems that need to be looked at.&lt;/strong&gt;I also left you a comment: &lt;blockquote&gt;The book might not be suited for the scope of Wikibooks.&lt;/blockquote&gt; If you have any questions or concerns, please [[User talk:Codename Noreste|let me know]]. Thank you! &lt;!-- Substituted from User:JJPMaster/CurateThisPage/authorMsg --&gt; [[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]]) 20:26, 2 August 2026 (UTC)

:how is it not suited [[User:Duodeca 12|Duodeca 12]] ([[User talk:Duodeca 12|discuss]] • [[Special:Contributions/Duodeca 12|contribs]]) 20:26, 2 August 2026 (UTC)
::explain [[User:Duodeca 12|Duodeca 12]] ([[User talk:Duodeca 12|discuss]] • [[Special:Contributions/Duodeca 12|contribs]]) 20:27, 2 August 2026 (UTC)
:explain how its not suitable [[User:Duodeca 12|Duodeca 12]] ([[User talk:Duodeca 12|discuss]] • [[Special:Contributions/Duodeca 12|contribs]]) 20:39, 2 August 2026 (UTC)
:: The page appears more like a Wikipedia article, which doesn't fit the scope of Wikibooks per [[WB:NOT]]. If needed, I can move the book to your userspace where you can work on it. [[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:59, 2 August 2026 (UTC)
:::or you could fix the structuring of it and clean up. [[User:Duodeca 12|Duodeca 12]] ([[User talk:Duodeca 12|discuss]] • [[Special:Contributions/Duodeca 12|contribs]]) 01:02, 3 August 2026 (UTC)
:::please fix the structuring rather than deleting  [[User:Duodeca 12|Duodeca 12]] ([[User talk:Duodeca 12|discuss]] • [[Special:Contributions/Duodeca 12|contribs]]) 01:20, 3 August 2026 (UTC)</text>
      <sha1>sve7ef1ncgu80t8vzhv3a63pdnbgiwd</sha1>
    </revision>
  </page>
  <page>
    <title>General Literary Chinese from Scratch/Cangjie Created Characters</title>
    <ns>0</ns>
    <id>485061</id>
    <revision>
      <id>4656114</id>
      <timestamp>2026-08-02T21:04:42Z</timestamp>
      <contributor>
        <username>Shira the Mogul</username>
        <id>3560559</id>
      </contributor>
      <comment>Back into the swing of things...</comment>
      <origin>4656114</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="8794" sha1="kwi98a1082kjooy4s3wh2suej9v05e9" xml:space="preserve">[[File:Cangjie2.jpg|thumb|200px|倉頡]]

A traditional tale tells of a historian for the legendary Yellow Emperor producing the first Han characters by looking at the feet of birds and the tracks of beasts. His name was Cangjie. Upon writing the first characters, millet rained from the sky as ghosts cried. 

Why did they cry? Were they upset at the fact that they missed out on the chance at their actions being remembered over 2,000 years later, as Cangjie is now? Or perhaps was it because information, fact or fiction, can last forever? Out of ''Huainanzi'' (淮南子), Shuowen Jiezi (説文解字), and Lunheng (論衡), the sources I use for this tradition, none really give a clear explanation, but commentaries often say it was the latter that caused the tears. Xu Bing, a famous artist who made a book comprised completely of fake characters, believes the ghosts cried because of the complicated nature of the writing system.

This legendary creator of characters is the namesake for an input method for the Han script: The Cangjie Input Method.

==Installing Cangjie==
The reason I recommend the Cangjie Input Method is because it is a phonetically neutral method of inputting the Han script. Should you already speak and type a language that uses the Han script, there is no reason you cannot use what you have; this input method, however, is great for someone who wants to specifically learn Literary Chinese.

Most operating systems offer Cangjie as an option, usually for Traditional Chinese only without going through hoops. Go into your Keyboard settings and it should be available to install. For Windows, use Microsoft Cangjie; for macOS, use Cangjie - Traditional. 

The examples used here are shared by Cangjie 3 and Cangjie 5, which are two different iterations. There aren't too many differences to worry about; Cangjie 5 is usually a bit simpler.

==You already know the keys!==
In my previous lessons, I taught you these characters:

&lt;blockquote&gt;
日月金木水火土&lt;br&gt;
竹戈十大中一弓&lt;br&gt;
人心手口&lt;br&gt;
尸廿山女田卜
&lt;/blockquote&gt;

These characters are all used on the Cangjie keyboard, and are used to form larger characters; if you have a QWERTY keyboard, they each correspond to a letter on them too:

{| class=&quot;wikitable&quot; style=&quot;text-align:center; margin:auto&quot;
! Latin key
| A || B || C || D || E || F || G
|-
! Cangjie
| 日 || 月 || 金 || 木 || 水 || 火 || 土
|-
! Latin key
| H || I || J || K || L || M || N
|-
! Cangjie
| 竹 || 戈 || 十 || 大 || 中 || 一 || 弓
|-
! Latin key
| O || P || Q || R
|-
! Cangjie
| 人 || 心 || 手 || 口
|-
! Latin key
| S || T || U || V || W || Y
|-
! Cangjie
| 尸 || 廿 || 山 || 女 || 田 || 卜
|}

The remaining keys, X (難) and Z (重), have special uses. You do not need them yet.

==How Cangjie Works==
[[File:倉頡輸入法 拆碼.jpg|center|300px]]
We previously encountered 明 in the poem by Kiyohara no Sanemoto. Which two Cangjie letters can you see?

&lt;blockquote&gt;
明 = 日 + 月
&lt;/blockquote&gt;

On a keyboard, 日 is A and 月 is B. Type A, then B, and select 明.

Try these as well:

&lt;blockquote&gt;
林 = 木木&lt;br&gt;
炎 = 火火&lt;br&gt;
晶 = 日日日&lt;br&gt;
森 = 木木木
&lt;/blockquote&gt;

You have now typed five characters without needing to know how any of them are pronounced, and now know that Cangjie reads components in sequence.

When you started learning Literary Chinese, we began with statements such as:

&lt;blockquote&gt;
人大。&lt;br&gt;
The person is big.
&lt;/blockquote&gt;

As we learned, Literary Chinese does not require an equivalent of &quot;to be&quot; in such a sentence.

Therefore...

&lt;blockquote&gt;
日月明。&lt;br&gt;
The sun and moon are bright.
&lt;/blockquote&gt;

How would you type it? 

You have now used Cangjie to type a complete piece of Literary Chinese.

==One character, many shapes==
[[File:Cangjie input secondary characters.png|center|300px]]
Each Cangjie letter also represents a family of related shapes, traditionally called auxiliary shapes (輔助字形).

The character printed upon a key is not always a literal component that
must appear inside another character. It names a family of related
shapes. A traditional mnemonic describes them like so:

&lt;blockquote&gt;
日月金木水火土&lt;br&gt;
斜點交叉縱橫鈎&lt;br&gt;
人心手口&lt;br&gt;
側並仰紐方卜
&lt;/blockquote&gt;

The line corresponds to:

&lt;blockquote&gt;
竹戈十大中一弓&lt;br&gt;
尸廿山女田卜
&lt;/blockquote&gt;

For example, the 竹 key can describe slanting forms (e.g. the top-left of 我), 弓 can describe hooked forms (e.g. The downward stroke in the bottom-right of 輸).

You do not need to memorise this now! Just know that it exists and compare it with the handwriting knowledge you already have.

==How to read a shape==
When inputting a character using Cangjie, it proceeds in the following order, similar to how they are written, as taught in previous lessons:
* Left-to-right
* Top-to-bottom
* Outside-to-inside

It is not exactly a stroke-order method, as it will sometimes omit strokes that would cause a code to be long. This makes Cangjie a seriously fast typing system when learned to its full potential. 

You have already seen left-to-right with our 明 example; but of course, there are other types.

===Top to bottom===

Consider 杲, meaning &quot;bright&quot; or &quot;the sun shining clearly.&quot;

The 日 is above the 木, so:

&lt;blockquote&gt;
杲 = 日木&lt;br&gt;
AD
&lt;/blockquote&gt;

===Outside to inside===

Consider 困, meaning &quot;confined,&quot; &quot;trapped,&quot; or &quot;in difficulty&quot;:

The outer enclosure is represented by 田, while 木 is inside it:

&lt;blockquote&gt;
困 = 田木&lt;br&gt;
WD
&lt;/blockquote&gt;

The outside is read before the inside.

This also gives us a memorable picture: a tree enclosed on every side is 困, trapped.

==Complex characters==
Unfortunately, not every character is this simple. More complicated characters may use auxiliary shapes as discussed before, be divided into a first component and remaining body, have more visible forms than Cangjie's 5-character limit, omit some strokes for said limit, or follow a special rule. Therefore, Cangjie is not necessarily about stroke order, and may not always represent how characters are written, though omissions do sometimes take hints from cursive writing.

Take 吾 for example, the first person pronoun. The lower component is simple: 口. However, while the upper component, 五, is written with the code 一木一, 吾 is written with 一一口, omitting 木. This makes it much faster to type, but typing may not be immediately obvious at first. Wiktionary contains Cangjie codes for you to use, so it is worth using that as a reference guide. Common character typing minigames are also available on various websites, such as https://cjtt.bzzt.io/, and HK Cards (https://www.hkcards.com/cj/exercise-cangjie-all) provides excellent deconstruction graphics.

==Practice==

===Part 1: Read the codes===

Which character is produced by each code?

# 日月
# 木木
# 火火
# 日日日
# 木木木
# 日木
# 田木

===Part 2: Write the codes===

Give the Cangjie code in both Han characters and Latin letters:

# 明
# 朋
# 林
# 炎
# 晶
# 森
# 杲
# 困

===Conclusion===
Pick out some characters you have learned before, and guess how Cangjie may divide it. Type what you expect, and look up the code if you fail. Do not worry yourself about failure: Failure may give you a new character that may be useful, and each failure teaches you something new. 

You do not need to &quot;solve&quot; every character. What you need is to see the characters for the strokes they are composed of; Han characters are not necessarily &quot;pictures,&quot; so to speak.

If Cangjie does not work for you, then there are other methods! Use what you find works best.

In the next lesson, we will look at another way of viewing characters for the structures they are composed of.

==References==
* Rime Cangjie 5 open code table: https://github.com/rime/rime-cangjie
* Microsoft, “Microsoft Traditional Chinese IME”: https://support.microsoft.com/en-us/windows/hardware/input-devices/microsoft-traditional-chinese-ime
* Apple, “Type Chinese using Cangjie – Traditional on Mac”: https://support.apple.com/guide/chinese-input-method/cimcjt11820/mac
* Xu, B. (2009). 天书的过程 [The Making of Book from the Sky] (D. Hammond, Trans.). In J. Cayley, L. H. Liu, H. Saussy, H. Wu, &amp; L. Yang, Tianshu: Passages in the making of a book...in conjunction with an exhibition on the making of Book from the Sky at Bernard Quaritch March 18th 2009. Quaritch.
* 朱邦復，《第五代倉頡輸入法手冊》: https://www.pascal-man.com/5cjbook/index.shtml
* 《淮南子》in Chinese Text Project. https://ctext.org/huainanzi
* 《説文解字》in Chinese Text Project. https://ctext.org/shuowen-jiezi
* 《論衡》in Chinese Text Project. https://ctext.org/lunheng

{{BookCat}}</text>
      <sha1>kwi98a1082kjooy4s3wh2suej9v05e9</sha1>
    </revision>
  </page>
  <page>
    <title>User:Masternod/sandbox</title>
    <ns>2</ns>
    <id>485062</id>
    <revision>
      <id>4656116</id>
      <timestamp>2026-08-02T21:20:26Z</timestamp>
      <contributor>
        <username>Masternod</username>
        <id>3618762</id>
      </contributor>
      <comment>free transistors</comment>
      <origin>4656116</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="166" sha1="b31haqoi9gockfpoa29w0qki2m6mxxw" xml:space="preserve">&lt;ref&gt;&lt;https://www.terabox.com/main?category=all&amp;path=%2FTransistirs.chatgpt.com.iones.es/ref&gt;https://www.terabox.com/main?category=all&amp;path=%2FTransistirs.chatgpt.com</text>
      <sha1>b31haqoi9gockfpoa29w0qki2m6mxxw</sha1>
    </revision>
    <revision>
      <id>4656143</id>
      <parentid>4656116</parentid>
      <timestamp>2026-08-03T00:14:20Z</timestamp>
      <contributor>
        <username>MathXplore</username>
        <id>3097823</id>
      </contributor>
      <comment>Marking for speedy deletion: Spam</comment>
      <origin>4656143</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="219" sha1="r7qny049qv6xl3i6h4zhyul92fgnnda" xml:space="preserve">&lt;noinclude&gt;{{Delete|example=false|Spam}}&lt;/noinclude&gt;
&lt;ref&gt;&lt;https://www.terabox.com/main?category=all&amp;path=%2FTransistirs.chatgpt.com.iones.es/ref&gt;https://www.terabox.com/main?category=all&amp;path=%2FTransistirs.chatgpt.com</text>
      <sha1>r7qny049qv6xl3i6h4zhyul92fgnnda</sha1>
    </revision>
  </page>
  <page>
    <title>General Literary Chinese from Scratch/The Kangxi Radical System</title>
    <ns>0</ns>
    <id>485063</id>
    <revision>
      <id>4656122</id>
      <timestamp>2026-08-02T21:41:01Z</timestamp>
      <contributor>
        <username>Shira the Mogul</username>
        <id>3560559</id>
      </contributor>
      <comment>Unit 0 done!</comment>
      <origin>4656122</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="7803" sha1="47dc5j87zzhagpucggegkjnh28s13k2" xml:space="preserve">[[File:清圣祖康熙皇帝朝服像.jpg|thumb|200px|康熙帝]]

Kangxi radicals are a system of organising characters in dictionaries. They originated in Zihui 字彙 in 1615, and crystalised in the Kangxi Dictionary 康熙字典 in 1716, one of the biggest aggregations of dictionary sources on Han characters ever conducted. The Kangxi Emperor was a lover of Literary Chinese and would make major contributions to classical resources for the language that, thanks to the internet, are now very widely available, often in more accessible forms than before. Therefore, when learning Literary Chinese through Literary Chinese, the Kangxi Dictionary is, to this day, a gold standard.

==What are radicals?==
Put simply, a &quot;radical&quot; (部首) is the component of a Han character that is considered distinctive. Usually, it will be a semantic component that implies the meaning. All radicals are components, but not all components are radicals. There are 214 Kangxi radicals in all. Look, if you can remember 151 Pokemon or hundreds of baseball players, 214 pictures shouldn't kill you!

Looking back in our lessons, I brought up this blink-it-and-you'll-miss-it sentence:
&lt;blockquote&gt;
土在地均&lt;br&gt;
The earth is on level ground
&lt;/blockquote&gt;

This uses characters only of the 土 &quot;earth&quot; radical. As you can see, the radical does not always appear in the same place, but its semantic value is largely consistent. This is not always consistent; as with anything made by the masses, there are exceptions, but it is a fairly decent way of identifying what the radical of a character is.

Take this other sentence, for example, which uses characters only of the 彳 &quot;step&quot; radical:
&lt;blockquote&gt;
循德得徽&lt;br&gt;
Follow virtue to attain excellence.
&lt;/blockquote&gt;

If you look to the left of each character, there is a 彳, though the meaning has diverged a bit for the rest.

===214 radical table===
The following table compiles all 214 radicals. These are all individually quite useful words, including animal names, weapons, food, terrain, and other qualities. If there are any you do not know, it is strongly recommended to look them up and learn them, and use them in your own sentences. 

{| class=&quot;wikitable&quot; style=&quot;text-align:center; margin:auto; font-size:125%; line-height:1.5&quot;
|-
| 1&lt;br&gt;一 || 2&lt;br&gt;丨 || 3&lt;br&gt;丶 || 4&lt;br&gt;丿 || 5&lt;br&gt;乙 || 6&lt;br&gt;亅 || 7&lt;br&gt;二 || 8&lt;br&gt;亠
|-
| 9&lt;br&gt;人 || 10&lt;br&gt;儿 || 11&lt;br&gt;入 || 12&lt;br&gt;八 || 13&lt;br&gt;冂 || 14&lt;br&gt;冖 || 15&lt;br&gt;冫 || 16&lt;br&gt;几
|-
| 17&lt;br&gt;凵 || 18&lt;br&gt;刀 || 19&lt;br&gt;力 || 20&lt;br&gt;勹 || 21&lt;br&gt;匕 || 22&lt;br&gt;匚 || 23&lt;br&gt;匸 || 24&lt;br&gt;十
|-
| 25&lt;br&gt;卜 || 26&lt;br&gt;卩 || 27&lt;br&gt;厂 || 28&lt;br&gt;厶 || 29&lt;br&gt;又 || 30&lt;br&gt;口 || 31&lt;br&gt;囗 || 32&lt;br&gt;土
|-
| 33&lt;br&gt;士 || 34&lt;br&gt;夂 || 35&lt;br&gt;夊 || 36&lt;br&gt;夕 || 37&lt;br&gt;大 || 38&lt;br&gt;女 || 39&lt;br&gt;子 || 40&lt;br&gt;宀
|-
| 41&lt;br&gt;寸 || 42&lt;br&gt;小 || 43&lt;br&gt;尢 || 44&lt;br&gt;尸 || 45&lt;br&gt;屮 || 46&lt;br&gt;山 || 47&lt;br&gt;巛 || 48&lt;br&gt;工
|-
| 49&lt;br&gt;己 || 50&lt;br&gt;巾 || 51&lt;br&gt;干 || 52&lt;br&gt;幺 || 53&lt;br&gt;广 || 54&lt;br&gt;廴 || 55&lt;br&gt;廾 || 56&lt;br&gt;弋
|-
| 57&lt;br&gt;弓 || 58&lt;br&gt;彐 || 59&lt;br&gt;彡 || 60&lt;br&gt;彳 || 61&lt;br&gt;心 || 62&lt;br&gt;戈 || 63&lt;br&gt;戶 || 64&lt;br&gt;手
|-
| 65&lt;br&gt;支 || 66&lt;br&gt;攴 || 67&lt;br&gt;文 || 68&lt;br&gt;斗 || 69&lt;br&gt;斤 || 70&lt;br&gt;方 || 71&lt;br&gt;无 || 72&lt;br&gt;日
|-
| 73&lt;br&gt;曰 || 74&lt;br&gt;月 || 75&lt;br&gt;木 || 76&lt;br&gt;欠 || 77&lt;br&gt;止 || 78&lt;br&gt;歹 || 79&lt;br&gt;殳 || 80&lt;br&gt;毋
|-
| 81&lt;br&gt;比 || 82&lt;br&gt;毛 || 83&lt;br&gt;氏 || 84&lt;br&gt;气 || 85&lt;br&gt;水 || 86&lt;br&gt;火 || 87&lt;br&gt;爪 || 88&lt;br&gt;父
|-
| 89&lt;br&gt;爻 || 90&lt;br&gt;爿 || 91&lt;br&gt;片 || 92&lt;br&gt;牙 || 93&lt;br&gt;牛 || 94&lt;br&gt;犬 || 95&lt;br&gt;玄 || 96&lt;br&gt;玉
|-
| 97&lt;br&gt;瓜 || 98&lt;br&gt;瓦 || 99&lt;br&gt;甘 || 100&lt;br&gt;生 || 101&lt;br&gt;用 || 102&lt;br&gt;田 || 103&lt;br&gt;疋 || 104&lt;br&gt;疒
|-
| 105&lt;br&gt;癶 || 106&lt;br&gt;白 || 107&lt;br&gt;皮 || 108&lt;br&gt;皿 || 109&lt;br&gt;目 || 110&lt;br&gt;矛 || 111&lt;br&gt;矢 || 112&lt;br&gt;石
|-
| 113&lt;br&gt;示 || 114&lt;br&gt;禸 || 115&lt;br&gt;禾 || 116&lt;br&gt;穴 || 117&lt;br&gt;立 || 118&lt;br&gt;竹 || 119&lt;br&gt;米 || 120&lt;br&gt;糸
|-
| 121&lt;br&gt;缶 || 122&lt;br&gt;网 || 123&lt;br&gt;羊 || 124&lt;br&gt;羽 || 125&lt;br&gt;老 || 126&lt;br&gt;而 || 127&lt;br&gt;耒 || 128&lt;br&gt;耳
|-
| 129&lt;br&gt;聿 || 130&lt;br&gt;肉 || 131&lt;br&gt;臣 || 132&lt;br&gt;自 || 133&lt;br&gt;至 || 134&lt;br&gt;臼 || 135&lt;br&gt;舌 || 136&lt;br&gt;舛
|-
| 137&lt;br&gt;舟 || 138&lt;br&gt;艮 || 139&lt;br&gt;色 || 140&lt;br&gt;艸 || 141&lt;br&gt;虍 || 142&lt;br&gt;虫 || 143&lt;br&gt;血 || 144&lt;br&gt;行
|-
| 145&lt;br&gt;衣 || 146&lt;br&gt;襾 || 147&lt;br&gt;見 || 148&lt;br&gt;角 || 149&lt;br&gt;言 || 150&lt;br&gt;谷 || 151&lt;br&gt;豆 || 152&lt;br&gt;豕
|-
| 153&lt;br&gt;豸 || 154&lt;br&gt;貝 || 155&lt;br&gt;赤 || 156&lt;br&gt;走 || 157&lt;br&gt;足 || 158&lt;br&gt;身 || 159&lt;br&gt;車 || 160&lt;br&gt;辛
|-
| 161&lt;br&gt;辰 || 162&lt;br&gt;辵 || 163&lt;br&gt;邑 || 164&lt;br&gt;酉 || 165&lt;br&gt;釆 || 166&lt;br&gt;里 || 167&lt;br&gt;金 || 168&lt;br&gt;長
|-
| 169&lt;br&gt;門 || 170&lt;br&gt;阜 || 171&lt;br&gt;隶 || 172&lt;br&gt;隹 || 173&lt;br&gt;雨 || 174&lt;br&gt;靑 || 175&lt;br&gt;非 || 176&lt;br&gt;面
|-
| 177&lt;br&gt;革 || 178&lt;br&gt;韋 || 179&lt;br&gt;韭 || 180&lt;br&gt;音 || 181&lt;br&gt;頁 || 182&lt;br&gt;風 || 183&lt;br&gt;飛 || 184&lt;br&gt;食
|-
| 185&lt;br&gt;首 || 186&lt;br&gt;香 || 187&lt;br&gt;馬 || 188&lt;br&gt;骨 || 189&lt;br&gt;高 || 190&lt;br&gt;髟 || 191&lt;br&gt;鬥 || 192&lt;br&gt;鬯
|-
| 193&lt;br&gt;鬲 || 194&lt;br&gt;鬼 || 195&lt;br&gt;魚 || 196&lt;br&gt;鳥 || 197&lt;br&gt;鹵 || 198&lt;br&gt;鹿 || 199&lt;br&gt;麥 || 200&lt;br&gt;麻
|-
| 201&lt;br&gt;黃 || 202&lt;br&gt;黍 || 203&lt;br&gt;黑 || 204&lt;br&gt;黹 || 205&lt;br&gt;黽 || 206&lt;br&gt;鼎 || 207&lt;br&gt;鼓 || 208&lt;br&gt;鼠
|-
| 209&lt;br&gt;鼻 || 210&lt;br&gt;齊 || 211&lt;br&gt;齒 || 212&lt;br&gt;龍 || 213&lt;br&gt;龜 || 214&lt;br&gt;龠
|}

===Radical variants===
Some radicals are heavily abbreviated to ensure they stay in the same square, which results in the following variants:
* 人 / 亻
* 水 / 氵
* 心 / 忄 / ⺗
* 手 / 扌
* 火 / 灬
* 衣 / 衤
* 示 / 礻
* 阜 and 邑 become left- and right-side 阝 forms too.

==Using a traditional Chinese dictionary==
When organising characters traditionally, dictionaries will take the radical of a character and then count the strokes coming afterwards. For example, 在 is 土 + 3 strokes for the rest of the character. If you go to the 土 section of a dictionary, then go to where you start seeing 3 strokes, 在 will appear. This is why identifying characters by their strokes and composition is useful: You can see the makeup, use the character, and remember it better.

==Exercises==
===Identify the radical===
* 休
* 河
* 情
* 燃
* 神
* 衫
* 均
* 循

===Recognise the variants===
Match each variant form to the radical it represents.
* 亻
* 氵
* 忄
* 扌
* 灬
* 衤
* 礻

===Count the remaining strokes===
Identify the radical in each character and then count the additional strokes.
* 在
* 地
* 河
* 林
* 明
* 情

===Compare with Cangjie===
Now that you understand the radical system, let's compare it with Cangjie and see how it can enrich our understanding. Take the following characters and their Cangjie codes. Which of their components do you think is the Kangxi radical? How many additional strokes are there?
* 明
* 林
* 炎
* 地
* 情

==Dictionary lookup==
Having passed those exercises, you now understand Kangxi radicals well enough to try using a traditional Chinese dictionary. Kangxi Dictionary is available in its original order on Chinese Text Project (https://ctext.org/kangxi-zidian), so you can use that. Try taking some characters you are unsure about, guess the radical, and try to find it in there!

==Conclusion==
With that, you have cleared Unit 0 and are now ready to engage with the Han script. These past two lessons have certainly been heavy, but they are important ways to put the Han script to use without necessarily knowing how to use it yet. The next units will get heavily into using the script, though, so get ready to learn some Literary Chinese!

==References==
* Jiang, L., &amp; Ren, M. (2023). A general theory of ancient Chinese (Y. Zhu &amp; W. Gao, Trans.). Zhejiang University Press.
* Zhang, Y., &amp; Chen, T. (with Aisin-Gioro, X.). (2015). 康熙字典 [Kāngxī Zìdiǎn] (H. Wang, Ed.; Revised Ed., Vols 1–2). 社会科学文献出版社 [Social Sciences Academic Press].
* 《字彙》</text>
      <sha1>47dc5j87zzhagpucggegkjnh28s13k2</sha1>
    </revision>
    <revision>
      <id>4656142</id>
      <parentid>4656122</parentid>
      <timestamp>2026-08-03T00:13:44Z</timestamp>
      <contributor>
        <username>MathXplore</username>
        <id>3097823</id>
      </contributor>
      <minor />
      <comment>Added {{[[Template:BookCat|BookCat]]}} using [[User:1234qwer1234qwer4/BookCat.js|BookCat.js]]</comment>
      <origin>4656142</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="7816" sha1="2aqgvaoeycrpd25sgvel68z9r0ao0db" xml:space="preserve">[[File:清圣祖康熙皇帝朝服像.jpg|thumb|200px|康熙帝]]

Kangxi radicals are a system of organising characters in dictionaries. They originated in Zihui 字彙 in 1615, and crystalised in the Kangxi Dictionary 康熙字典 in 1716, one of the biggest aggregations of dictionary sources on Han characters ever conducted. The Kangxi Emperor was a lover of Literary Chinese and would make major contributions to classical resources for the language that, thanks to the internet, are now very widely available, often in more accessible forms than before. Therefore, when learning Literary Chinese through Literary Chinese, the Kangxi Dictionary is, to this day, a gold standard.

==What are radicals?==
Put simply, a &quot;radical&quot; (部首) is the component of a Han character that is considered distinctive. Usually, it will be a semantic component that implies the meaning. All radicals are components, but not all components are radicals. There are 214 Kangxi radicals in all. Look, if you can remember 151 Pokemon or hundreds of baseball players, 214 pictures shouldn't kill you!

Looking back in our lessons, I brought up this blink-it-and-you'll-miss-it sentence:
&lt;blockquote&gt;
土在地均&lt;br&gt;
The earth is on level ground
&lt;/blockquote&gt;

This uses characters only of the 土 &quot;earth&quot; radical. As you can see, the radical does not always appear in the same place, but its semantic value is largely consistent. This is not always consistent; as with anything made by the masses, there are exceptions, but it is a fairly decent way of identifying what the radical of a character is.

Take this other sentence, for example, which uses characters only of the 彳 &quot;step&quot; radical:
&lt;blockquote&gt;
循德得徽&lt;br&gt;
Follow virtue to attain excellence.
&lt;/blockquote&gt;

If you look to the left of each character, there is a 彳, though the meaning has diverged a bit for the rest.

===214 radical table===
The following table compiles all 214 radicals. These are all individually quite useful words, including animal names, weapons, food, terrain, and other qualities. If there are any you do not know, it is strongly recommended to look them up and learn them, and use them in your own sentences. 

{| class=&quot;wikitable&quot; style=&quot;text-align:center; margin:auto; font-size:125%; line-height:1.5&quot;
|-
| 1&lt;br&gt;一 || 2&lt;br&gt;丨 || 3&lt;br&gt;丶 || 4&lt;br&gt;丿 || 5&lt;br&gt;乙 || 6&lt;br&gt;亅 || 7&lt;br&gt;二 || 8&lt;br&gt;亠
|-
| 9&lt;br&gt;人 || 10&lt;br&gt;儿 || 11&lt;br&gt;入 || 12&lt;br&gt;八 || 13&lt;br&gt;冂 || 14&lt;br&gt;冖 || 15&lt;br&gt;冫 || 16&lt;br&gt;几
|-
| 17&lt;br&gt;凵 || 18&lt;br&gt;刀 || 19&lt;br&gt;力 || 20&lt;br&gt;勹 || 21&lt;br&gt;匕 || 22&lt;br&gt;匚 || 23&lt;br&gt;匸 || 24&lt;br&gt;十
|-
| 25&lt;br&gt;卜 || 26&lt;br&gt;卩 || 27&lt;br&gt;厂 || 28&lt;br&gt;厶 || 29&lt;br&gt;又 || 30&lt;br&gt;口 || 31&lt;br&gt;囗 || 32&lt;br&gt;土
|-
| 33&lt;br&gt;士 || 34&lt;br&gt;夂 || 35&lt;br&gt;夊 || 36&lt;br&gt;夕 || 37&lt;br&gt;大 || 38&lt;br&gt;女 || 39&lt;br&gt;子 || 40&lt;br&gt;宀
|-
| 41&lt;br&gt;寸 || 42&lt;br&gt;小 || 43&lt;br&gt;尢 || 44&lt;br&gt;尸 || 45&lt;br&gt;屮 || 46&lt;br&gt;山 || 47&lt;br&gt;巛 || 48&lt;br&gt;工
|-
| 49&lt;br&gt;己 || 50&lt;br&gt;巾 || 51&lt;br&gt;干 || 52&lt;br&gt;幺 || 53&lt;br&gt;广 || 54&lt;br&gt;廴 || 55&lt;br&gt;廾 || 56&lt;br&gt;弋
|-
| 57&lt;br&gt;弓 || 58&lt;br&gt;彐 || 59&lt;br&gt;彡 || 60&lt;br&gt;彳 || 61&lt;br&gt;心 || 62&lt;br&gt;戈 || 63&lt;br&gt;戶 || 64&lt;br&gt;手
|-
| 65&lt;br&gt;支 || 66&lt;br&gt;攴 || 67&lt;br&gt;文 || 68&lt;br&gt;斗 || 69&lt;br&gt;斤 || 70&lt;br&gt;方 || 71&lt;br&gt;无 || 72&lt;br&gt;日
|-
| 73&lt;br&gt;曰 || 74&lt;br&gt;月 || 75&lt;br&gt;木 || 76&lt;br&gt;欠 || 77&lt;br&gt;止 || 78&lt;br&gt;歹 || 79&lt;br&gt;殳 || 80&lt;br&gt;毋
|-
| 81&lt;br&gt;比 || 82&lt;br&gt;毛 || 83&lt;br&gt;氏 || 84&lt;br&gt;气 || 85&lt;br&gt;水 || 86&lt;br&gt;火 || 87&lt;br&gt;爪 || 88&lt;br&gt;父
|-
| 89&lt;br&gt;爻 || 90&lt;br&gt;爿 || 91&lt;br&gt;片 || 92&lt;br&gt;牙 || 93&lt;br&gt;牛 || 94&lt;br&gt;犬 || 95&lt;br&gt;玄 || 96&lt;br&gt;玉
|-
| 97&lt;br&gt;瓜 || 98&lt;br&gt;瓦 || 99&lt;br&gt;甘 || 100&lt;br&gt;生 || 101&lt;br&gt;用 || 102&lt;br&gt;田 || 103&lt;br&gt;疋 || 104&lt;br&gt;疒
|-
| 105&lt;br&gt;癶 || 106&lt;br&gt;白 || 107&lt;br&gt;皮 || 108&lt;br&gt;皿 || 109&lt;br&gt;目 || 110&lt;br&gt;矛 || 111&lt;br&gt;矢 || 112&lt;br&gt;石
|-
| 113&lt;br&gt;示 || 114&lt;br&gt;禸 || 115&lt;br&gt;禾 || 116&lt;br&gt;穴 || 117&lt;br&gt;立 || 118&lt;br&gt;竹 || 119&lt;br&gt;米 || 120&lt;br&gt;糸
|-
| 121&lt;br&gt;缶 || 122&lt;br&gt;网 || 123&lt;br&gt;羊 || 124&lt;br&gt;羽 || 125&lt;br&gt;老 || 126&lt;br&gt;而 || 127&lt;br&gt;耒 || 128&lt;br&gt;耳
|-
| 129&lt;br&gt;聿 || 130&lt;br&gt;肉 || 131&lt;br&gt;臣 || 132&lt;br&gt;自 || 133&lt;br&gt;至 || 134&lt;br&gt;臼 || 135&lt;br&gt;舌 || 136&lt;br&gt;舛
|-
| 137&lt;br&gt;舟 || 138&lt;br&gt;艮 || 139&lt;br&gt;色 || 140&lt;br&gt;艸 || 141&lt;br&gt;虍 || 142&lt;br&gt;虫 || 143&lt;br&gt;血 || 144&lt;br&gt;行
|-
| 145&lt;br&gt;衣 || 146&lt;br&gt;襾 || 147&lt;br&gt;見 || 148&lt;br&gt;角 || 149&lt;br&gt;言 || 150&lt;br&gt;谷 || 151&lt;br&gt;豆 || 152&lt;br&gt;豕
|-
| 153&lt;br&gt;豸 || 154&lt;br&gt;貝 || 155&lt;br&gt;赤 || 156&lt;br&gt;走 || 157&lt;br&gt;足 || 158&lt;br&gt;身 || 159&lt;br&gt;車 || 160&lt;br&gt;辛
|-
| 161&lt;br&gt;辰 || 162&lt;br&gt;辵 || 163&lt;br&gt;邑 || 164&lt;br&gt;酉 || 165&lt;br&gt;釆 || 166&lt;br&gt;里 || 167&lt;br&gt;金 || 168&lt;br&gt;長
|-
| 169&lt;br&gt;門 || 170&lt;br&gt;阜 || 171&lt;br&gt;隶 || 172&lt;br&gt;隹 || 173&lt;br&gt;雨 || 174&lt;br&gt;靑 || 175&lt;br&gt;非 || 176&lt;br&gt;面
|-
| 177&lt;br&gt;革 || 178&lt;br&gt;韋 || 179&lt;br&gt;韭 || 180&lt;br&gt;音 || 181&lt;br&gt;頁 || 182&lt;br&gt;風 || 183&lt;br&gt;飛 || 184&lt;br&gt;食
|-
| 185&lt;br&gt;首 || 186&lt;br&gt;香 || 187&lt;br&gt;馬 || 188&lt;br&gt;骨 || 189&lt;br&gt;高 || 190&lt;br&gt;髟 || 191&lt;br&gt;鬥 || 192&lt;br&gt;鬯
|-
| 193&lt;br&gt;鬲 || 194&lt;br&gt;鬼 || 195&lt;br&gt;魚 || 196&lt;br&gt;鳥 || 197&lt;br&gt;鹵 || 198&lt;br&gt;鹿 || 199&lt;br&gt;麥 || 200&lt;br&gt;麻
|-
| 201&lt;br&gt;黃 || 202&lt;br&gt;黍 || 203&lt;br&gt;黑 || 204&lt;br&gt;黹 || 205&lt;br&gt;黽 || 206&lt;br&gt;鼎 || 207&lt;br&gt;鼓 || 208&lt;br&gt;鼠
|-
| 209&lt;br&gt;鼻 || 210&lt;br&gt;齊 || 211&lt;br&gt;齒 || 212&lt;br&gt;龍 || 213&lt;br&gt;龜 || 214&lt;br&gt;龠
|}

===Radical variants===
Some radicals are heavily abbreviated to ensure they stay in the same square, which results in the following variants:
* 人 / 亻
* 水 / 氵
* 心 / 忄 / ⺗
* 手 / 扌
* 火 / 灬
* 衣 / 衤
* 示 / 礻
* 阜 and 邑 become left- and right-side 阝 forms too.

==Using a traditional Chinese dictionary==
When organising characters traditionally, dictionaries will take the radical of a character and then count the strokes coming afterwards. For example, 在 is 土 + 3 strokes for the rest of the character. If you go to the 土 section of a dictionary, then go to where you start seeing 3 strokes, 在 will appear. This is why identifying characters by their strokes and composition is useful: You can see the makeup, use the character, and remember it better.

==Exercises==
===Identify the radical===
* 休
* 河
* 情
* 燃
* 神
* 衫
* 均
* 循

===Recognise the variants===
Match each variant form to the radical it represents.
* 亻
* 氵
* 忄
* 扌
* 灬
* 衤
* 礻

===Count the remaining strokes===
Identify the radical in each character and then count the additional strokes.
* 在
* 地
* 河
* 林
* 明
* 情

===Compare with Cangjie===
Now that you understand the radical system, let's compare it with Cangjie and see how it can enrich our understanding. Take the following characters and their Cangjie codes. Which of their components do you think is the Kangxi radical? How many additional strokes are there?
* 明
* 林
* 炎
* 地
* 情

==Dictionary lookup==
Having passed those exercises, you now understand Kangxi radicals well enough to try using a traditional Chinese dictionary. Kangxi Dictionary is available in its original order on Chinese Text Project (https://ctext.org/kangxi-zidian), so you can use that. Try taking some characters you are unsure about, guess the radical, and try to find it in there!

==Conclusion==
With that, you have cleared Unit 0 and are now ready to engage with the Han script. These past two lessons have certainly been heavy, but they are important ways to put the Han script to use without necessarily knowing how to use it yet. The next units will get heavily into using the script, though, so get ready to learn some Literary Chinese!

==References==
* Jiang, L., &amp; Ren, M. (2023). A general theory of ancient Chinese (Y. Zhu &amp; W. Gao, Trans.). Zhejiang University Press.
* Zhang, Y., &amp; Chen, T. (with Aisin-Gioro, X.). (2015). 康熙字典 [Kāngxī Zìdiǎn] (H. Wang, Ed.; Revised Ed., Vols 1–2). 社会科学文献出版社 [Social Sciences Academic Press].
* 《字彙》

{{BookCat}}</text>
      <sha1>2aqgvaoeycrpd25sgvel68z9r0ao0db</sha1>
    </revision>
  </page>
  <page>
    <title>Scratch Virtual Machine/Blocks</title>
    <ns>0</ns>
    <id>485064</id>
    <revision>
      <id>4656127</id>
      <timestamp>2026-08-02T22:08:05Z</timestamp>
      <contributor>
        <username>Some helpful person</username>
        <id>3510188</id>
      </contributor>
      <comment>Created page with &quot; The following is a brief overview of every block, each including a description, list of steps, and pseudocode. ({{Abbr|WIP.|Work in progress.}})  =={{subst:Anchor|motion|motion_}} Motion&lt;ref&gt;{{Cite web |title=scratch3_motion.js |url=https://github.com/scratchfoundation/scratch-editor/blob/6fd95da6340916c2693452e012b52fbd13f19c50/packages/scratch-vm/src/blocks/scratch3_motion.js |access-date=2026-08-02 |publisher=[[:w:Scratch_Foundation|Scratch Foundation]] |language=en...&quot;</comment>
      <origin>4656127</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="4079" sha1="tmnx3x9ir6pm57arhstnb4g4nhq1903" xml:space="preserve">
The following is a brief overview of every block, each including a description, list of steps, and pseudocode. ({{Abbr|WIP.|Work in progress.}})

==&lt;span class=&quot;anchor&quot; id=&quot;motion&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;motion_&quot;&gt;&lt;/span&gt; Motion&lt;ref&gt;{{Cite web |title=scratch3_motion.js |url=https://github.com/scratchfoundation/scratch-editor/blob/6fd95da6340916c2693452e012b52fbd13f19c50/packages/scratch-vm/src/blocks/scratch3_motion.js |access-date=2026-08-02 |publisher=[[:w:Scratch_Foundation|Scratch Foundation]] |language=en |via=[[:w:GitHub|GitHub]]}}&lt;/ref&gt; ==

===&lt;span class=&quot;anchor&quot; id=&quot;motion_movesteps&quot;&gt;&lt;/span&gt; move (STEPS) steps===

Moves the sprite STEPS forward in the direction it is facing.

* Casts STEPS to a number. (STEPS)
* Subtracts the target's direction from 90 and converts it to radians. (RADIANS)
* setXY(the target's X position plus STEPS multiplied by the cosine of RADIANS, the target's Y position plus STEPS multiplied by the sine of RADIANS)

&lt;syntaxhighlight lang=js&gt;
motion_movesteps(STEPS):
STEPS = castToNumber(STEPS)
RADIANS = degreesToRadians(90 - target.direction)
setXY(target.x + STEPS * cos(RADIANS), target.y + STEPS * sin(RADIANS))
&lt;/syntaxhighlight&gt;

===&lt;span class=&quot;anchor&quot; id=&quot;motion_turnright&quot;&gt;&lt;/span&gt; turn {{Abbr|⟳|clockwise, right}} (DEGREES) degrees ===

Rotates the sprite clockwise DEGREES degrees.

* Casts DEGREES to a number. (DEGREES)
* setDirection(the target's direction added to DEGREES)

&lt;syntaxhighlight lang=js&gt;
motion_turnright(DEGREES):
DEGREES = castToNumber(DEGREES)
setDirection(target.direction + DEGREES)
&lt;/syntaxhighlight&gt;

===&lt;span class=&quot;anchor&quot; id=&quot;motion_turnleft&quot;&gt;&lt;/span&gt; turn {{Abbr|⟲|counterclockwise, left}} (DEGREES) degrees ===

Rotates the sprite counterclockwise DEGREES degrees.

* Casts DEGREES to a number. (DEGREES)
* setDirection(the target's direction subtracted by DEGREES)

&lt;syntaxhighlight lang=js&gt;
motion_turnleft(DEGREES):
DEGREES = castToNumber(DEGREES)
setDirection(target.direction - DEGREES)
&lt;/syntaxhighlight&gt;

===&lt;span class=&quot;anchor&quot; id=&quot;motion_goto&quot;&gt;&lt;/span&gt; go to (TO)===

Moves the sprite to a particular set of X and Y coordinates as determined by TO.

* getTargetXY(TO) (X, Y)
* setXY(X, Y)

&lt;syntaxhighlight lang=js&gt;
motion_goto(TO):
X, Y = getTargetXY(TO)
setXY(X, Y)
&lt;/syntaxhighlight&gt;

===&lt;span class=&quot;anchor&quot; id=&quot;motion_gotoxy&quot;&gt;&lt;/span&gt; go to x: (X) y: (Y)===

Moves the sprite to the given X and Y coordinates.

* Casts X to a number. (X)
* Casts Y to a number. (Y)
* setXY(X, Y)

&lt;syntaxhighlight lang=js&gt;
motion_gotoxy(X, Y):
X = castToNumber(X)
Y = castToNumber(Y)
setXY(X, Y)
&lt;/syntaxhighlight&gt;

==Looks==

==Sound==

==Events==

==Control==

==Sensing==

==Operators==

==Data==

==Procedures==

==&lt;span class=&quot;anchor&quot; id=&quot;coreExample&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;coreExample_&quot;&gt;&lt;/span&gt; Core Example==

==&lt;span class=&quot;anchor&quot; id=&quot;music&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;music_&quot;&gt;&lt;/span&gt; Music==

==&lt;span class=&quot;anchor&quot; id=&quot;pen&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;pen_&quot;&gt;&lt;/span&gt; Pen==

==&lt;span class=&quot;anchor&quot; id=&quot;videoSensing&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;videoSensing_&quot;&gt;&lt;/span&gt; Video Sensing==

==&lt;span class=&quot;anchor&quot; id=&quot;faceSensing&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;faceSensing_&quot;&gt;&lt;/span&gt; Face Sensing==

==&lt;span class=&quot;anchor&quot; id=&quot;text2speech&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;text2speech_&quot;&gt;&lt;/span&gt; Text to Speech==

==&lt;span class=&quot;anchor&quot; id=&quot;translate&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;translate_&quot;&gt;&lt;/span&gt; Translate==

==&lt;span class=&quot;anchor&quot; id=&quot;makeymakey&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;makeymakey_&quot;&gt;&lt;/span&gt; Makey Makey==

==&lt;span class=&quot;anchor&quot; id=&quot;microbit&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;microbit_&quot;&gt;&lt;/span&gt; micro:bit==

==&lt;span class=&quot;anchor&quot; id=&quot;gdxfor&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;gdxfor_&quot;&gt;&lt;/span&gt; Go Direct Force &amp; Acceleration==

==&lt;span class=&quot;anchor&quot; id=&quot;ev3&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;ev3_&quot;&gt;&lt;/span&gt; LEGO MINDSTORMS EV3==

==&lt;span class=&quot;anchor&quot; id=&quot;boost&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;boost_&quot;&gt;&lt;/span&gt; LEGO BOOST==

==&lt;span class=&quot;anchor&quot; id=&quot;wedo2&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;wedo2_&quot;&gt;&lt;/span&gt; LEGO Education WeDo 2.0==

==References==</text>
      <sha1>tmnx3x9ir6pm57arhstnb4g4nhq1903</sha1>
    </revision>
    <revision>
      <id>4656141</id>
      <parentid>4656127</parentid>
      <timestamp>2026-08-03T00:13:37Z</timestamp>
      <contributor>
        <username>MathXplore</username>
        <id>3097823</id>
      </contributor>
      <minor />
      <comment>Added {{[[Template:BookCat|BookCat]]}} using [[User:1234qwer1234qwer4/BookCat.js|BookCat.js]]</comment>
      <origin>4656141</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="4092" sha1="nqeh8x6ep7ets6kit9fg4xa3fk03bvs" xml:space="preserve">
The following is a brief overview of every block, each including a description, list of steps, and pseudocode. ({{Abbr|WIP.|Work in progress.}})

==&lt;span class=&quot;anchor&quot; id=&quot;motion&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;motion_&quot;&gt;&lt;/span&gt; Motion&lt;ref&gt;{{Cite web |title=scratch3_motion.js |url=https://github.com/scratchfoundation/scratch-editor/blob/6fd95da6340916c2693452e012b52fbd13f19c50/packages/scratch-vm/src/blocks/scratch3_motion.js |access-date=2026-08-02 |publisher=[[:w:Scratch_Foundation|Scratch Foundation]] |language=en |via=[[:w:GitHub|GitHub]]}}&lt;/ref&gt; ==

===&lt;span class=&quot;anchor&quot; id=&quot;motion_movesteps&quot;&gt;&lt;/span&gt; move (STEPS) steps===

Moves the sprite STEPS forward in the direction it is facing.

* Casts STEPS to a number. (STEPS)
* Subtracts the target's direction from 90 and converts it to radians. (RADIANS)
* setXY(the target's X position plus STEPS multiplied by the cosine of RADIANS, the target's Y position plus STEPS multiplied by the sine of RADIANS)

&lt;syntaxhighlight lang=js&gt;
motion_movesteps(STEPS):
STEPS = castToNumber(STEPS)
RADIANS = degreesToRadians(90 - target.direction)
setXY(target.x + STEPS * cos(RADIANS), target.y + STEPS * sin(RADIANS))
&lt;/syntaxhighlight&gt;

===&lt;span class=&quot;anchor&quot; id=&quot;motion_turnright&quot;&gt;&lt;/span&gt; turn {{Abbr|⟳|clockwise, right}} (DEGREES) degrees ===

Rotates the sprite clockwise DEGREES degrees.

* Casts DEGREES to a number. (DEGREES)
* setDirection(the target's direction added to DEGREES)

&lt;syntaxhighlight lang=js&gt;
motion_turnright(DEGREES):
DEGREES = castToNumber(DEGREES)
setDirection(target.direction + DEGREES)
&lt;/syntaxhighlight&gt;

===&lt;span class=&quot;anchor&quot; id=&quot;motion_turnleft&quot;&gt;&lt;/span&gt; turn {{Abbr|⟲|counterclockwise, left}} (DEGREES) degrees ===

Rotates the sprite counterclockwise DEGREES degrees.

* Casts DEGREES to a number. (DEGREES)
* setDirection(the target's direction subtracted by DEGREES)

&lt;syntaxhighlight lang=js&gt;
motion_turnleft(DEGREES):
DEGREES = castToNumber(DEGREES)
setDirection(target.direction - DEGREES)
&lt;/syntaxhighlight&gt;

===&lt;span class=&quot;anchor&quot; id=&quot;motion_goto&quot;&gt;&lt;/span&gt; go to (TO)===

Moves the sprite to a particular set of X and Y coordinates as determined by TO.

* getTargetXY(TO) (X, Y)
* setXY(X, Y)

&lt;syntaxhighlight lang=js&gt;
motion_goto(TO):
X, Y = getTargetXY(TO)
setXY(X, Y)
&lt;/syntaxhighlight&gt;

===&lt;span class=&quot;anchor&quot; id=&quot;motion_gotoxy&quot;&gt;&lt;/span&gt; go to x: (X) y: (Y)===

Moves the sprite to the given X and Y coordinates.

* Casts X to a number. (X)
* Casts Y to a number. (Y)
* setXY(X, Y)

&lt;syntaxhighlight lang=js&gt;
motion_gotoxy(X, Y):
X = castToNumber(X)
Y = castToNumber(Y)
setXY(X, Y)
&lt;/syntaxhighlight&gt;

==Looks==

==Sound==

==Events==

==Control==

==Sensing==

==Operators==

==Data==

==Procedures==

==&lt;span class=&quot;anchor&quot; id=&quot;coreExample&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;coreExample_&quot;&gt;&lt;/span&gt; Core Example==

==&lt;span class=&quot;anchor&quot; id=&quot;music&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;music_&quot;&gt;&lt;/span&gt; Music==

==&lt;span class=&quot;anchor&quot; id=&quot;pen&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;pen_&quot;&gt;&lt;/span&gt; Pen==

==&lt;span class=&quot;anchor&quot; id=&quot;videoSensing&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;videoSensing_&quot;&gt;&lt;/span&gt; Video Sensing==

==&lt;span class=&quot;anchor&quot; id=&quot;faceSensing&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;faceSensing_&quot;&gt;&lt;/span&gt; Face Sensing==

==&lt;span class=&quot;anchor&quot; id=&quot;text2speech&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;text2speech_&quot;&gt;&lt;/span&gt; Text to Speech==

==&lt;span class=&quot;anchor&quot; id=&quot;translate&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;translate_&quot;&gt;&lt;/span&gt; Translate==

==&lt;span class=&quot;anchor&quot; id=&quot;makeymakey&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;makeymakey_&quot;&gt;&lt;/span&gt; Makey Makey==

==&lt;span class=&quot;anchor&quot; id=&quot;microbit&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;microbit_&quot;&gt;&lt;/span&gt; micro:bit==

==&lt;span class=&quot;anchor&quot; id=&quot;gdxfor&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;gdxfor_&quot;&gt;&lt;/span&gt; Go Direct Force &amp; Acceleration==

==&lt;span class=&quot;anchor&quot; id=&quot;ev3&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;ev3_&quot;&gt;&lt;/span&gt; LEGO MINDSTORMS EV3==

==&lt;span class=&quot;anchor&quot; id=&quot;boost&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;boost_&quot;&gt;&lt;/span&gt; LEGO BOOST==

==&lt;span class=&quot;anchor&quot; id=&quot;wedo2&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;wedo2_&quot;&gt;&lt;/span&gt; LEGO Education WeDo 2.0==

==References==

{{BookCat}}</text>
      <sha1>nqeh8x6ep7ets6kit9fg4xa3fk03bvs</sha1>
    </revision>
    <revision>
      <id>4656157</id>
      <parentid>4656141</parentid>
      <timestamp>2026-08-03T05:19:31Z</timestamp>
      <contributor>
        <username>Some helpful person</username>
        <id>3510188</id>
      </contributor>
      <comment>/*  Motion */ Add remaining motion blocks</comment>
      <origin>4656157</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="9976" sha1="07rptow8my80kdvqxk6j8jq7gofvv2h" xml:space="preserve">
The following is a brief overview of every block, each including a description, list of steps, and pseudocode. ({{Abbr|WIP.|Work in progress.}})

==&lt;span class=&quot;anchor&quot; id=&quot;motion&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;motion_&quot;&gt;&lt;/span&gt; Motion&lt;ref&gt;{{Cite web |title=scratch3_motion.js |url=https://github.com/scratchfoundation/scratch-editor/blob/6fd95da6340916c2693452e012b52fbd13f19c50/packages/scratch-vm/src/blocks/scratch3_motion.js |access-date=2026-08-02 |publisher=[[:w:Scratch_Foundation|Scratch Foundation]] |language=en |via=[[:w:GitHub|GitHub]]}}&lt;/ref&gt; ==

===&lt;span class=&quot;anchor&quot; id=&quot;motion_movesteps&quot;&gt;&lt;/span&gt; move (STEPS) steps===

Moves the sprite STEPS forward in the direction it is facing.

* Casts STEPS to a number. (STEPS)
* Subtracts the target's direction from 90 and converts it to radians. (RADIANS)
* setXY(the target's X position plus STEPS multiplied by the cosine of RADIANS, the target's Y position plus STEPS multiplied by the sine of RADIANS)

&lt;syntaxhighlight lang=py&gt;
motion_movesteps(STEPS):
STEPS = castToNumber(STEPS)
RADIANS = degreesToRadians(90 - target.direction)
setXY(target.x + STEPS * cos(RADIANS), target.y + STEPS * sin(RADIANS))
&lt;/syntaxhighlight&gt;

===&lt;span class=&quot;anchor&quot; id=&quot;motion_turnright&quot;&gt;&lt;/span&gt; turn {{Abbr|⟳|clockwise, right}} (DEGREES) degrees ===

Rotates the sprite clockwise DEGREES degrees.

* Casts DEGREES to a number. (DEGREES)
* setDirection(the target's direction added to DEGREES)

&lt;syntaxhighlight lang=py&gt;
motion_turnright(DEGREES):
DEGREES = castToNumber(DEGREES)
setDirection(target.direction + DEGREES)
&lt;/syntaxhighlight&gt;

===&lt;span class=&quot;anchor&quot; id=&quot;motion_turnleft&quot;&gt;&lt;/span&gt; turn {{Abbr|⟲|counterclockwise, left}} (DEGREES) degrees ===

Rotates the sprite counterclockwise DEGREES degrees.

* Casts DEGREES to a number. (DEGREES)
* setDirection(the target's direction subtracted by DEGREES)

&lt;syntaxhighlight lang=py&gt;
motion_turnleft(DEGREES):
DEGREES = castToNumber(DEGREES)
setDirection(target.direction - DEGREES)
&lt;/syntaxhighlight&gt;

===&lt;span class=&quot;anchor&quot; id=&quot;motion_goto&quot;&gt;&lt;/span&gt; go to (TO)===

Moves the sprite to a particular set of X and Y coordinates as determined by TO.

* getTargetXY(TO) (X, Y)
* setXY(X, Y)

&lt;syntaxhighlight lang=py&gt;
motion_goto(TO):
X, Y = getTargetXY(TO)
setXY(X, Y)
&lt;/syntaxhighlight&gt;

===&lt;span class=&quot;anchor&quot; id=&quot;motion_gotoxy&quot;&gt;&lt;/span&gt; go to x: (X) y: (Y)===

Moves the sprite to the given X and Y coordinates.

* Casts X to a number. (X)
* Casts Y to a number. (Y)
* setXY(X, Y)

&lt;syntaxhighlight lang=py&gt;
motion_gotoxy(X, Y):
X = castToNumber(X)
Y = castToNumber(Y)
setXY(X, Y)
&lt;/syntaxhighlight&gt;

===&lt;span class=&quot;anchor&quot; id=&quot;motion_glideto&quot;&gt;&lt;/span&gt; glide (SECS) secs to (TO)===

Linearly transitions the sprite to a particular set of X and Y coordinates as determined by TO over a SECS second period.

* getTargetXY(TO) (X, Y)
* glide(SECS, X, Y)

&lt;syntaxhighlight lang=py&gt;
motion_glideto(SECS, TO):
X, Y = getTargetXY(TO)
motion_glidesecstoxy(SECS, X, Y)
&lt;/syntaxhighlight&gt;

===&lt;span class=&quot;anchor&quot; id=&quot;motion_glidesecstoxy&quot;&gt;&lt;/span&gt; glide (SECS) secs to x: (X) y: (Y)===

Linearly transitions the sprite to the given X and Y coordinates over a SECS second period.
{{TODO|Explain how glide works.}}&lt;syntaxhighlight lang=py&gt;
motion_glidesecstoxy(SECS, X, Y):
...
&lt;/syntaxhighlight&gt;

===&lt;span class=&quot;anchor&quot; id=&quot;motion_pointindirection&quot;&gt;&lt;/span&gt; point in direction (DIRECTION)===

Rotates the sprite such that it faces the given DIRECTION in degrees.

* Casts DIRECTION to a number. (DIRECTION)
* setDirection(DIRECTION)

&lt;syntaxhighlight lang=py&gt;
motion_pointindirection(DIRECTION):
DIRECTION = castToNumber(DIRECTION)
setDirection(DIRECTION)
&lt;/syntaxhighlight&gt;

===&lt;span class=&quot;anchor&quot; id=&quot;motion_pointtowards&quot;&gt;&lt;/span&gt; point towards (TOWARDS)===

Rotates the sprite such that it faces a particular direction as determined by TOWARDS.

* If TOWARDS is the string &lt;code&gt;_mouse_&lt;/code&gt;:
** Subtracts the target's X position from the X position of the mouse-pointer. (DX)
** Subtracts the target's Y position from the Y position of the mouse-pointer. (DY)
** Converts the 2-argument arctangent of DY and DX in radians to degrees. (DIRECTION)
** setDirection(DIRECTION)
* Otherwise, if TOWARDS is the string &lt;code&gt;_random_&lt;/code&gt;:
** setDirection(a random integer on the interval [-180, 180], with -180 and 180 being twice as unlikely as other values)
* Otherwise:
** Casts TOWARDS to a string. (TOWARDS)
** Finds the sprite by the name of TOWARDS. (SPRITE)
** If SPRITE exists:
*** Subtracts the target's X position from SPRITE's X position. (DX)
*** Subtracts the target's Y position from SPRITE's Y position. (DY)
*** Converts the 2-argument arctangent of DY and DX in radians to degrees. (DIRECTION)
*** setDirection(DIRECTION)
** Otherwise, does nothing.

&lt;syntaxhighlight lang=py&gt;
motion_pointtowards(TOWARDS):
if TOWARDS is &quot;_mouse_&quot;
    DX = mouse.x - target.x
    DY = mouse.y - target.y
    DIRECTION = radiansToDegrees(atan2(DY, DX))
    setDirection(DIRECTION)
else if TOWARDS is &quot;_random_&quot;
    setDirection(round(random() * 360) - 180)
else
    TOWARDS = castToString(TOWARDS)
    SPRITE = getSpriteNamed(TOWARDS)
    if SPRITE exists
        DX = SPRITE.x - target.x
        DY = SPRITE.y - target.y
        DIRECTION = radiansToDegrees(atan2(DY, DX))
        setDirection(DIRECTION)
    else
        (do nothing)
&lt;/syntaxhighlight&gt;

===&lt;span class=&quot;anchor&quot; id=&quot;motion_changexby&quot;&gt;&lt;/span&gt; change x by (DX)===

Increases the target's X position by DX.

* Casts DX to a number. (DX)
* setXY(DX added to the target's X position, the target's Y position)

&lt;syntaxhighlight lang=py&gt;
motion_changexby(DX):
DX = castToNumber(DX)
setXY(target.x + DX, target.y)
&lt;/syntaxhighlight&gt;

===&lt;span class=&quot;anchor&quot; id=&quot;motion_setx&quot;&gt;&lt;/span&gt; set x to (X)===

Sets the target's X position to X.

* Casts X to a number. (X)
* setXY(X, the target's Y position)

&lt;syntaxhighlight lang=py&gt;
motion_setx(X):
X = castToNumber(X)
setXY(X, target.y)
&lt;/syntaxhighlight&gt;

===&lt;span class=&quot;anchor&quot; id=&quot;motion_changeyby&quot;&gt;&lt;/span&gt; change y by (DY)===

Increases the target's Y position by DY.

* Casts DY to a number. (DY)
* setXY(the target's X position, DY added to the target's Y position)

&lt;syntaxhighlight lang=py&gt;
motion_changeyby(DY):
DY = castToNumber(DY)
setXY(target.x, target.y + DY)
&lt;/syntaxhighlight&gt;

===&lt;span class=&quot;anchor&quot; id=&quot;motion_sety&quot;&gt;&lt;/span&gt; set y to (Y)===

Sets the target's Y position to Y.

* Casts Y to a number. (Y)
* setXY(the target's X position, Y)

&lt;syntaxhighlight lang=py&gt;
motion_sety(Y):
Y = castToNumber(Y)
setXY(target.X, Y)
&lt;/syntaxhighlight&gt;

===&lt;span class=&quot;anchor&quot; id=&quot;motion_ifonedgebounce&quot;&gt;&lt;/span&gt; if on edge, bounce===

{{TODO|Explain how if on edge, bounce works.}}&lt;syntaxhighlight lang=py&gt;
motion_ifonedgebounce():
...
&lt;/syntaxhighlight&gt;

===&lt;span class=&quot;anchor&quot; id=&quot;motion_setrotationstyle&quot;&gt;&lt;/span&gt; set rotation style (STYLE)===

Sets the target's rotation style as determined by STYLE.

* If STYLE is one of the strings &lt;code&gt;don't rotate&lt;/code&gt;, &lt;code&gt;all around&lt;/code&gt;, or &lt;code&gt;left-right&lt;/code&gt;, sets the target's rotation style to STYLE.
* If the sprite is visible, requests to redraw the screen.

&lt;syntaxhighlight lang=py&gt;
motion_setrotationstyle(STYLE):
if STYLE is &quot;don't rotate&quot; or is &quot;all around&quot; or is &quot;left-right&quot;
    target.rotationStyle = STYLE
if target.visible
    redraw()
&lt;/syntaxhighlight&gt;

===&lt;span class=&quot;anchor&quot; id=&quot;motion_xposition&quot;&gt;&lt;/span&gt; x position===

Reports the target's X position.

* If the target's X position is less than 1e-9 away from the nearest integer:
** Reports the target's X position rounded to the nearest integer.
* Otherwise:
** Reports the target's X position.

&lt;syntaxhighlight lang=py&gt;
motion_xposition():
if abs(target.x - round(target.x)) &lt; 1e-9
    return round(target.x)
else
    return target.x
&lt;/syntaxhighlight&gt;

===&lt;span class=&quot;anchor&quot; id=&quot;motion_yposition&quot;&gt;&lt;/span&gt; y position===

Reports the target's Y position.

* If the target's Y position is less than 1e-9 away from the nearest integer:
** Reports the target's Y position rounded to the nearest integer.
* Otherwise:
** Reports the target's Y position.

&lt;syntaxhighlight lang=py&gt;
motion_yposition():
if abs(target.y - round(target.y)) &lt; 1e-9
    return round(target.y)
else
    return target.y
&lt;/syntaxhighlight&gt;

===&lt;span class=&quot;anchor&quot; id=&quot;motion_direction&quot;&gt;&lt;/span&gt; direction===

Reports the target's direction.

* Reports the target's direction in degrees.

&lt;syntaxhighlight lang=py&gt;
motion_direction():
return target.direction
&lt;/syntaxhighlight&gt;

==Looks==

==Sound==

==Events==

==Control==

==Sensing==

==Operators==

==Data==

==Procedures==

==&lt;span class=&quot;anchor&quot; id=&quot;coreExample&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;coreExample_&quot;&gt;&lt;/span&gt; Core Example==

==&lt;span class=&quot;anchor&quot; id=&quot;music&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;music_&quot;&gt;&lt;/span&gt; Music==

==&lt;span class=&quot;anchor&quot; id=&quot;pen&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;pen_&quot;&gt;&lt;/span&gt; Pen==

==&lt;span class=&quot;anchor&quot; id=&quot;videoSensing&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;videoSensing_&quot;&gt;&lt;/span&gt; Video Sensing==

==&lt;span class=&quot;anchor&quot; id=&quot;faceSensing&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;faceSensing_&quot;&gt;&lt;/span&gt; Face Sensing==

==&lt;span class=&quot;anchor&quot; id=&quot;text2speech&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;text2speech_&quot;&gt;&lt;/span&gt; Text to Speech==

==&lt;span class=&quot;anchor&quot; id=&quot;translate&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;translate_&quot;&gt;&lt;/span&gt; Translate==

==&lt;span class=&quot;anchor&quot; id=&quot;makeymakey&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;makeymakey_&quot;&gt;&lt;/span&gt; Makey Makey==

==&lt;span class=&quot;anchor&quot; id=&quot;microbit&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;microbit_&quot;&gt;&lt;/span&gt; micro:bit==

==&lt;span class=&quot;anchor&quot; id=&quot;gdxfor&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;gdxfor_&quot;&gt;&lt;/span&gt; Go Direct Force &amp; Acceleration==

==&lt;span class=&quot;anchor&quot; id=&quot;ev3&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;ev3_&quot;&gt;&lt;/span&gt; LEGO MINDSTORMS EV3==

==&lt;span class=&quot;anchor&quot; id=&quot;boost&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;boost_&quot;&gt;&lt;/span&gt; LEGO BOOST==

==&lt;span class=&quot;anchor&quot; id=&quot;wedo2&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;wedo2_&quot;&gt;&lt;/span&gt; LEGO Education WeDo 2.0==

==References==

{{BookCat}}</text>
      <sha1>07rptow8my80kdvqxk6j8jq7gofvv2h</sha1>
    </revision>
    <revision>
      <id>4656158</id>
      <parentid>4656157</parentid>
      <timestamp>2026-08-03T05:23:25Z</timestamp>
      <contributor>
        <username>Some helpful person</username>
        <id>3510188</id>
      </contributor>
      <minor />
      <origin>4656158</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="10038" sha1="tf1u16nis317bdui4eko2aj942fwknd" xml:space="preserve">
The following is a brief overview of every block, each including a description, list of steps, and pseudocode. ({{Abbr|WIP.|Work in progress.}})

==&lt;span class=&quot;anchor&quot; id=&quot;motion&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;motion_&quot;&gt;&lt;/span&gt; Motion ==

Motion blocks affect the position and direction of a sprite.&lt;ref&gt;{{Cite web |title=scratch3_motion.js |url=https://github.com/scratchfoundation/scratch-editor/blob/6fd95da6340916c2693452e012b52fbd13f19c50/packages/scratch-vm/src/blocks/scratch3_motion.js |access-date=2026-08-02 |publisher=[[:w:Scratch_Foundation|Scratch Foundation]] |language=en |via=[[:w:GitHub|GitHub]]}}&lt;/ref&gt;

===&lt;span class=&quot;anchor&quot; id=&quot;motion_movesteps&quot;&gt;&lt;/span&gt; move (STEPS) steps===

Moves the sprite STEPS forward in the direction it is facing.

* Casts STEPS to a number. (STEPS)
* Subtracts the target's direction from 90 and converts it to radians. (RADIANS)
* setXY(the target's X position plus STEPS multiplied by the cosine of RADIANS, the target's Y position plus STEPS multiplied by the sine of RADIANS)

&lt;syntaxhighlight lang=py&gt;
motion_movesteps(STEPS):
STEPS = castToNumber(STEPS)
RADIANS = degreesToRadians(90 - target.direction)
setXY(target.x + STEPS * cos(RADIANS), target.y + STEPS * sin(RADIANS))
&lt;/syntaxhighlight&gt;

===&lt;span class=&quot;anchor&quot; id=&quot;motion_turnright&quot;&gt;&lt;/span&gt; turn {{Abbr|⟳|clockwise, right}} (DEGREES) degrees ===

Rotates the sprite clockwise DEGREES degrees.

* Casts DEGREES to a number. (DEGREES)
* setDirection(the target's direction added to DEGREES)

&lt;syntaxhighlight lang=py&gt;
motion_turnright(DEGREES):
DEGREES = castToNumber(DEGREES)
setDirection(target.direction + DEGREES)
&lt;/syntaxhighlight&gt;

===&lt;span class=&quot;anchor&quot; id=&quot;motion_turnleft&quot;&gt;&lt;/span&gt; turn {{Abbr|⟲|counterclockwise, left}} (DEGREES) degrees ===

Rotates the sprite counterclockwise DEGREES degrees.

* Casts DEGREES to a number. (DEGREES)
* setDirection(the target's direction subtracted by DEGREES)

&lt;syntaxhighlight lang=py&gt;
motion_turnleft(DEGREES):
DEGREES = castToNumber(DEGREES)
setDirection(target.direction - DEGREES)
&lt;/syntaxhighlight&gt;

===&lt;span class=&quot;anchor&quot; id=&quot;motion_goto&quot;&gt;&lt;/span&gt; go to (TO)===

Moves the sprite to a particular set of X and Y coordinates as determined by TO.

* getTargetXY(TO) (X, Y)
* setXY(X, Y)

&lt;syntaxhighlight lang=py&gt;
motion_goto(TO):
X, Y = getTargetXY(TO)
setXY(X, Y)
&lt;/syntaxhighlight&gt;

===&lt;span class=&quot;anchor&quot; id=&quot;motion_gotoxy&quot;&gt;&lt;/span&gt; go to x: (X) y: (Y)===

Moves the sprite to the given X and Y coordinates.

* Casts X to a number. (X)
* Casts Y to a number. (Y)
* setXY(X, Y)

&lt;syntaxhighlight lang=py&gt;
motion_gotoxy(X, Y):
X = castToNumber(X)
Y = castToNumber(Y)
setXY(X, Y)
&lt;/syntaxhighlight&gt;

===&lt;span class=&quot;anchor&quot; id=&quot;motion_glideto&quot;&gt;&lt;/span&gt; glide (SECS) secs to (TO)===

Linearly transitions the sprite to a particular set of X and Y coordinates as determined by TO over a SECS second period.

* getTargetXY(TO) (X, Y)
* glide(SECS, X, Y)

&lt;syntaxhighlight lang=py&gt;
motion_glideto(SECS, TO):
X, Y = getTargetXY(TO)
motion_glidesecstoxy(SECS, X, Y)
&lt;/syntaxhighlight&gt;

===&lt;span class=&quot;anchor&quot; id=&quot;motion_glidesecstoxy&quot;&gt;&lt;/span&gt; glide (SECS) secs to x: (X) y: (Y)===

Linearly transitions the sprite to the given X and Y coordinates over a SECS second period.
{{TODO|Explain how glide works.}}&lt;syntaxhighlight lang=py&gt;
motion_glidesecstoxy(SECS, X, Y):
...
&lt;/syntaxhighlight&gt;

===&lt;span class=&quot;anchor&quot; id=&quot;motion_pointindirection&quot;&gt;&lt;/span&gt; point in direction (DIRECTION)===

Rotates the sprite such that it faces the given DIRECTION in degrees.

* Casts DIRECTION to a number. (DIRECTION)
* setDirection(DIRECTION)

&lt;syntaxhighlight lang=py&gt;
motion_pointindirection(DIRECTION):
DIRECTION = castToNumber(DIRECTION)
setDirection(DIRECTION)
&lt;/syntaxhighlight&gt;

===&lt;span class=&quot;anchor&quot; id=&quot;motion_pointtowards&quot;&gt;&lt;/span&gt; point towards (TOWARDS)===

Rotates the sprite such that it faces a particular direction as determined by TOWARDS.

* If TOWARDS is the string &lt;code&gt;_mouse_&lt;/code&gt;:
** Subtracts the target's X position from the X position of the mouse-pointer. (DX)
** Subtracts the target's Y position from the Y position of the mouse-pointer. (DY)
** Converts the 2-argument arctangent of DY and DX in radians to degrees. (DIRECTION)
** setDirection(DIRECTION)
* Otherwise, if TOWARDS is the string &lt;code&gt;_random_&lt;/code&gt;:
** setDirection(a random integer on the interval [-180, 180], with -180 and 180 being twice as unlikely as other values)
* Otherwise:
** Casts TOWARDS to a string. (TOWARDS)
** Finds the sprite by the name of TOWARDS. (SPRITE)
** If SPRITE exists:
*** Subtracts the target's X position from SPRITE's X position. (DX)
*** Subtracts the target's Y position from SPRITE's Y position. (DY)
*** Converts the 2-argument arctangent of DY and DX in radians to degrees. (DIRECTION)
*** setDirection(DIRECTION)
** Otherwise, does nothing.

&lt;syntaxhighlight lang=py&gt;
motion_pointtowards(TOWARDS):
if TOWARDS is &quot;_mouse_&quot;
    DX = mouse.x - target.x
    DY = mouse.y - target.y
    DIRECTION = radiansToDegrees(atan2(DY, DX))
    setDirection(DIRECTION)
else if TOWARDS is &quot;_random_&quot;
    setDirection(round(random() * 360) - 180)
else
    TOWARDS = castToString(TOWARDS)
    SPRITE = getSpriteNamed(TOWARDS)
    if SPRITE exists
        DX = SPRITE.x - target.x
        DY = SPRITE.y - target.y
        DIRECTION = radiansToDegrees(atan2(DY, DX))
        setDirection(DIRECTION)
    else
        (do nothing)
&lt;/syntaxhighlight&gt;

===&lt;span class=&quot;anchor&quot; id=&quot;motion_changexby&quot;&gt;&lt;/span&gt; change x by (DX)===

Increases the target's X position by DX.

* Casts DX to a number. (DX)
* setXY(DX added to the target's X position, the target's Y position)

&lt;syntaxhighlight lang=py&gt;
motion_changexby(DX):
DX = castToNumber(DX)
setXY(target.x + DX, target.y)
&lt;/syntaxhighlight&gt;

===&lt;span class=&quot;anchor&quot; id=&quot;motion_setx&quot;&gt;&lt;/span&gt; set x to (X)===

Sets the target's X position to X.

* Casts X to a number. (X)
* setXY(X, the target's Y position)

&lt;syntaxhighlight lang=py&gt;
motion_setx(X):
X = castToNumber(X)
setXY(X, target.y)
&lt;/syntaxhighlight&gt;

===&lt;span class=&quot;anchor&quot; id=&quot;motion_changeyby&quot;&gt;&lt;/span&gt; change y by (DY)===

Increases the target's Y position by DY.

* Casts DY to a number. (DY)
* setXY(the target's X position, DY added to the target's Y position)

&lt;syntaxhighlight lang=py&gt;
motion_changeyby(DY):
DY = castToNumber(DY)
setXY(target.x, target.y + DY)
&lt;/syntaxhighlight&gt;

===&lt;span class=&quot;anchor&quot; id=&quot;motion_sety&quot;&gt;&lt;/span&gt; set y to (Y)===

Sets the target's Y position to Y.

* Casts Y to a number. (Y)
* setXY(the target's X position, Y)

&lt;syntaxhighlight lang=py&gt;
motion_sety(Y):
Y = castToNumber(Y)
setXY(target.X, Y)
&lt;/syntaxhighlight&gt;

===&lt;span class=&quot;anchor&quot; id=&quot;motion_ifonedgebounce&quot;&gt;&lt;/span&gt; if on edge, bounce===

{{TODO|Explain how if on edge, bounce works.}}&lt;syntaxhighlight lang=py&gt;
motion_ifonedgebounce():
...
&lt;/syntaxhighlight&gt;

===&lt;span class=&quot;anchor&quot; id=&quot;motion_setrotationstyle&quot;&gt;&lt;/span&gt; set rotation style (STYLE)===

Sets the target's rotation style as determined by STYLE.

* If STYLE is one of the strings &lt;code&gt;don't rotate&lt;/code&gt;, &lt;code&gt;all around&lt;/code&gt;, or &lt;code&gt;left-right&lt;/code&gt;, sets the target's rotation style to STYLE.
* If the sprite is visible, requests to redraw the screen.

&lt;syntaxhighlight lang=py&gt;
motion_setrotationstyle(STYLE):
if STYLE is &quot;don't rotate&quot; or is &quot;all around&quot; or is &quot;left-right&quot;
    target.rotationStyle = STYLE
if target.visible
    redraw()
&lt;/syntaxhighlight&gt;

===&lt;span class=&quot;anchor&quot; id=&quot;motion_xposition&quot;&gt;&lt;/span&gt; x position===

Reports the target's X position.

* If the target's X position is less than 1e-9 away from the nearest integer:
** Reports the target's X position rounded to the nearest integer.
* Otherwise:
** Reports the target's X position.

&lt;syntaxhighlight lang=py&gt;
motion_xposition():
if abs(target.x - round(target.x)) &lt; 1e-9
    return round(target.x)
else
    return target.x
&lt;/syntaxhighlight&gt;

===&lt;span class=&quot;anchor&quot; id=&quot;motion_yposition&quot;&gt;&lt;/span&gt; y position===

Reports the target's Y position.

* If the target's Y position is less than 1e-9 away from the nearest integer:
** Reports the target's Y position rounded to the nearest integer.
* Otherwise:
** Reports the target's Y position.

&lt;syntaxhighlight lang=py&gt;
motion_yposition():
if abs(target.y - round(target.y)) &lt; 1e-9
    return round(target.y)
else
    return target.y
&lt;/syntaxhighlight&gt;

===&lt;span class=&quot;anchor&quot; id=&quot;motion_direction&quot;&gt;&lt;/span&gt; direction===

Reports the target's direction.

* Reports the target's direction in degrees.

&lt;syntaxhighlight lang=py&gt;
motion_direction():
return target.direction
&lt;/syntaxhighlight&gt;

==Looks==

==Sound==

==Events==

==Control==

==Sensing==

==Operators==

==Data==

==Procedures==

==&lt;span class=&quot;anchor&quot; id=&quot;coreExample&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;coreExample_&quot;&gt;&lt;/span&gt; Core Example==

==&lt;span class=&quot;anchor&quot; id=&quot;music&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;music_&quot;&gt;&lt;/span&gt; Music==

==&lt;span class=&quot;anchor&quot; id=&quot;pen&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;pen_&quot;&gt;&lt;/span&gt; Pen==

==&lt;span class=&quot;anchor&quot; id=&quot;videoSensing&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;videoSensing_&quot;&gt;&lt;/span&gt; Video Sensing==

==&lt;span class=&quot;anchor&quot; id=&quot;faceSensing&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;faceSensing_&quot;&gt;&lt;/span&gt; Face Sensing==

==&lt;span class=&quot;anchor&quot; id=&quot;text2speech&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;text2speech_&quot;&gt;&lt;/span&gt; Text to Speech==

==&lt;span class=&quot;anchor&quot; id=&quot;translate&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;translate_&quot;&gt;&lt;/span&gt; Translate==

==&lt;span class=&quot;anchor&quot; id=&quot;makeymakey&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;makeymakey_&quot;&gt;&lt;/span&gt; Makey Makey==

==&lt;span class=&quot;anchor&quot; id=&quot;microbit&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;microbit_&quot;&gt;&lt;/span&gt; micro:bit==

==&lt;span class=&quot;anchor&quot; id=&quot;gdxfor&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;gdxfor_&quot;&gt;&lt;/span&gt; Go Direct Force &amp; Acceleration==

==&lt;span class=&quot;anchor&quot; id=&quot;ev3&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;ev3_&quot;&gt;&lt;/span&gt; LEGO MINDSTORMS EV3==

==&lt;span class=&quot;anchor&quot; id=&quot;boost&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;boost_&quot;&gt;&lt;/span&gt; LEGO BOOST==

==&lt;span class=&quot;anchor&quot; id=&quot;wedo2&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;wedo2_&quot;&gt;&lt;/span&gt; LEGO Education WeDo 2.0==

==References==

{{BookCat}}</text>
      <sha1>tf1u16nis317bdui4eko2aj942fwknd</sha1>
    </revision>
    <revision>
      <id>4656162</id>
      <parentid>4656158</parentid>
      <timestamp>2026-08-03T05:58:14Z</timestamp>
      <contributor>
        <username>Some helpful person</username>
        <id>3510188</id>
      </contributor>
      <minor />
      <comment>split to subpage very slowly b/c automated filter</comment>
      <origin>4656162</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="5218" sha1="c6xoovqo24w4p6xjd4ol7r2ifvuiups" xml:space="preserve">
The following is a brief overview of every block, each including a description, list of steps, and pseudocode. ({{Abbr|WIP.|Work in progress.}})

==&lt;span class=&quot;anchor&quot; id=&quot;motion&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;motion_&quot;&gt;&lt;/span&gt; Motion ==

Motion blocks affect the position and direction of a sprite.&lt;ref&gt;{{Cite web |title=scratch3_motion.js |url=https://github.com/scratchfoundation/scratch-editor/blob/6fd95da6340916c2693452e012b52fbd13f19c50/packages/scratch-vm/src/blocks/scratch3_motion.js |access-date=2026-08-02 |publisher=[[:w:Scratch_Foundation|Scratch Foundation]] |language=en |via=[[:w:GitHub|GitHub]]}}&lt;/ref&gt;

===&lt;span class=&quot;anchor&quot; id=&quot;motion_movesteps&quot;&gt;&lt;/span&gt; move (STEPS) steps===

Moves the sprite STEPS forward in the direction it is facing.

* Casts STEPS to a number. (STEPS)
* Subtracts the target's direction from 90 and converts it to radians. (RADIANS)
* setXY(the target's X position plus STEPS multiplied by the cosine of RADIANS, the target's Y position plus STEPS multiplied by the sine of RADIANS)

&lt;syntaxhighlight lang=py&gt;
motion_movesteps(STEPS):
STEPS = castToNumber(STEPS)
RADIANS = degreesToRadians(90 - target.direction)
setXY(target.x + STEPS * cos(RADIANS), target.y + STEPS * sin(RADIANS))
&lt;/syntaxhighlight&gt;

===&lt;span class=&quot;anchor&quot; id=&quot;motion_turnright&quot;&gt;&lt;/span&gt; turn {{Abbr|⟳|clockwise, right}} (DEGREES) degrees ===

Rotates the sprite clockwise DEGREES degrees.

* Casts DEGREES to a number. (DEGREES)
* setDirection(the target's direction added to DEGREES)

&lt;syntaxhighlight lang=py&gt;
motion_turnright(DEGREES):
DEGREES = castToNumber(DEGREES)
setDirection(target.direction + DEGREES)
&lt;/syntaxhighlight&gt;

===&lt;span class=&quot;anchor&quot; id=&quot;motion_turnleft&quot;&gt;&lt;/span&gt; turn {{Abbr|⟲|counterclockwise, left}} (DEGREES) degrees ===

Rotates the sprite counterclockwise DEGREES degrees.

* Casts DEGREES to a number. (DEGREES)
* setDirection(the target's direction subtracted by DEGREES)

&lt;syntaxhighlight lang=py&gt;
motion_turnleft(DEGREES):
DEGREES = castToNumber(DEGREES)
setDirection(target.direction - DEGREES)
&lt;/syntaxhighlight&gt;

===&lt;span class=&quot;anchor&quot; id=&quot;motion_goto&quot;&gt;&lt;/span&gt; go to (TO)===

Moves the sprite to a particular set of X and Y coordinates as determined by TO.

* getTargetXY(TO) (X, Y)
* setXY(X, Y)

&lt;syntaxhighlight lang=py&gt;
motion_goto(TO):
X, Y = getTargetXY(TO)
setXY(X, Y)
&lt;/syntaxhighlight&gt;

===&lt;span class=&quot;anchor&quot; id=&quot;motion_gotoxy&quot;&gt;&lt;/span&gt; go to x: (X) y: (Y)===

Moves the sprite to the given X and Y coordinates.

* Casts X to a number. (X)
* Casts Y to a number. (Y)
* setXY(X, Y)

&lt;syntaxhighlight lang=py&gt;
motion_gotoxy(X, Y):
X = castToNumber(X)
Y = castToNumber(Y)
setXY(X, Y)
&lt;/syntaxhighlight&gt;

===&lt;span class=&quot;anchor&quot; id=&quot;motion_glideto&quot;&gt;&lt;/span&gt; glide (SECS) secs to (TO)===

Linearly transitions the sprite to a particular set of X and Y coordinates as determined by TO over a SECS second period.

* getTargetXY(TO) (X, Y)
* glide(SECS, X, Y)

&lt;syntaxhighlight lang=py&gt;
motion_glideto(SECS, TO):
X, Y = getTargetXY(TO)
motion_glidesecstoxy(SECS, X, Y)
&lt;/syntaxhighlight&gt;

===&lt;span class=&quot;anchor&quot; id=&quot;motion_glidesecstoxy&quot;&gt;&lt;/span&gt; glide (SECS) secs to x: (X) y: (Y)===

Linearly transitions the sprite to the given X and Y coordinates over a SECS second period.
{{TODO|Explain how glide works.}}&lt;syntaxhighlight lang=py&gt;
motion_glidesecstoxy(SECS, X, Y):
...
&lt;/syntaxhighlight&gt;

===&lt;span class=&quot;anchor&quot; id=&quot;motion_pointindirection&quot;&gt;&lt;/span&gt; point in direction (DIRECTION)===

Rotates the sprite such that it faces the given DIRECTION in degrees.

* Casts DIRECTION to a number. (DIRECTION)
* setDirection(DIRECTION)

&lt;syntaxhighlight lang=py&gt;
motion_pointindirection(DIRECTION):
DIRECTION = castToNumber(DIRECTION)
setDirection(DIRECTION)
&lt;/syntaxhighlight&gt;

==Looks==

==Sound==

==Events==

==Control==

==Sensing==

==Operators==

==Data==

==Procedures==

==&lt;span class=&quot;anchor&quot; id=&quot;coreExample&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;coreExample_&quot;&gt;&lt;/span&gt; Core Example==

==&lt;span class=&quot;anchor&quot; id=&quot;music&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;music_&quot;&gt;&lt;/span&gt; Music==

==&lt;span class=&quot;anchor&quot; id=&quot;pen&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;pen_&quot;&gt;&lt;/span&gt; Pen==

==&lt;span class=&quot;anchor&quot; id=&quot;videoSensing&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;videoSensing_&quot;&gt;&lt;/span&gt; Video Sensing==

==&lt;span class=&quot;anchor&quot; id=&quot;faceSensing&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;faceSensing_&quot;&gt;&lt;/span&gt; Face Sensing==

==&lt;span class=&quot;anchor&quot; id=&quot;text2speech&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;text2speech_&quot;&gt;&lt;/span&gt; Text to Speech==

==&lt;span class=&quot;anchor&quot; id=&quot;translate&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;translate_&quot;&gt;&lt;/span&gt; Translate==

==&lt;span class=&quot;anchor&quot; id=&quot;makeymakey&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;makeymakey_&quot;&gt;&lt;/span&gt; Makey Makey==

==&lt;span class=&quot;anchor&quot; id=&quot;microbit&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;microbit_&quot;&gt;&lt;/span&gt; micro:bit==

==&lt;span class=&quot;anchor&quot; id=&quot;gdxfor&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;gdxfor_&quot;&gt;&lt;/span&gt; Go Direct Force &amp; Acceleration==

==&lt;span class=&quot;anchor&quot; id=&quot;ev3&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;ev3_&quot;&gt;&lt;/span&gt; LEGO MINDSTORMS EV3==

==&lt;span class=&quot;anchor&quot; id=&quot;boost&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;boost_&quot;&gt;&lt;/span&gt; LEGO BOOST==

==&lt;span class=&quot;anchor&quot; id=&quot;wedo2&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;wedo2_&quot;&gt;&lt;/span&gt; LEGO Education WeDo 2.0==

==References==

{{BookCat}}</text>
      <sha1>c6xoovqo24w4p6xjd4ol7r2ifvuiups</sha1>
    </revision>
    <revision>
      <id>4656163</id>
      <parentid>4656162</parentid>
      <timestamp>2026-08-03T05:58:37Z</timestamp>
      <contributor>
        <username>Some helpful person</username>
        <id>3510188</id>
      </contributor>
      <minor />
      <comment>split to subpage</comment>
      <origin>4656163</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2892" sha1="li9jyrzbajbyb10uxpy5u51vs2z2prw" xml:space="preserve">
The following is a brief overview of every block, each including a description, list of steps, and pseudocode. ({{Abbr|WIP.|Work in progress.}})

==[[/Motion|Motion]]==

Motion blocks affect the position and direction of a sprite.&lt;ref&gt;{{Cite web |title=scratch3_motion.js |url=https://github.com/scratchfoundation/scratch-editor/blob/6fd95da6340916c2693452e012b52fbd13f19c50/packages/scratch-vm/src/blocks/scratch3_motion.js |access-date=2026-08-02 |publisher=[[:w:Scratch_Foundation|Scratch Foundation]] |language=en |via=[[:w:GitHub|GitHub]]}}&lt;/ref&gt;

* [[/Motion#movesteps|move (STEPS) steps]]
* [[/Motion#turnright|turn {{Abbr|⟳|clockwise, right}} (DEGREES) degrees]]
* [[/Motion#turnleft|turn {{Abbr|⟲|counterclockwise, left}} (DEGREES) degrees]]
* [[/Motion#goto|go to (TO)]]
* [[/Motion#gotoxy|go to x: (X) y: (Y)]]
* [[/Motion#glideto|glide (SECS) secs to (TO)]]
* [[/Motion#glidesecstoxy|glide (SECS) secs to x: (X) y: (Y)]]
* [[/Motion#pointindirection|point in direction (DIRECTION)]]
* [[/Motion#pointtowards|point towards (TOWARDS)]]
* [[/Motion#changexby|change x by (DX)]]
* [[/Motion#setx|set x to (X)]]
* [[/Motion#changeyby|change y by (DY)]]
* [[/Motion#sety|set y to (Y)]]
* [[/Motion#ifonedgebounce|if on edge, bounce]]
* [[/Motion#setrotationstyle|set rotation style (STYLE)]]
* [[/Motion#xposition|x position]]
* [[/Motion#yposition|y position]]
* [[/Motion#direction|direction]]

==Looks==

==Sound==

==Events==

==Control==

==Sensing==

==Operators==

==Data==

==Procedures==

==&lt;span class=&quot;anchor&quot; id=&quot;coreExample&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;coreExample_&quot;&gt;&lt;/span&gt; Core Example==

==&lt;span class=&quot;anchor&quot; id=&quot;music&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;music_&quot;&gt;&lt;/span&gt; Music==

==&lt;span class=&quot;anchor&quot; id=&quot;pen&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;pen_&quot;&gt;&lt;/span&gt; Pen==

==&lt;span class=&quot;anchor&quot; id=&quot;videoSensing&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;videoSensing_&quot;&gt;&lt;/span&gt; Video Sensing==

==&lt;span class=&quot;anchor&quot; id=&quot;faceSensing&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;faceSensing_&quot;&gt;&lt;/span&gt; Face Sensing==

==&lt;span class=&quot;anchor&quot; id=&quot;text2speech&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;text2speech_&quot;&gt;&lt;/span&gt; Text to Speech==

==&lt;span class=&quot;anchor&quot; id=&quot;translate&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;translate_&quot;&gt;&lt;/span&gt; Translate==

==&lt;span class=&quot;anchor&quot; id=&quot;makeymakey&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;makeymakey_&quot;&gt;&lt;/span&gt; Makey Makey==

==&lt;span class=&quot;anchor&quot; id=&quot;microbit&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;microbit_&quot;&gt;&lt;/span&gt; micro:bit==

==&lt;span class=&quot;anchor&quot; id=&quot;gdxfor&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;gdxfor_&quot;&gt;&lt;/span&gt; Go Direct Force &amp; Acceleration==

==&lt;span class=&quot;anchor&quot; id=&quot;ev3&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;ev3_&quot;&gt;&lt;/span&gt; LEGO MINDSTORMS EV3==

==&lt;span class=&quot;anchor&quot; id=&quot;boost&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;boost_&quot;&gt;&lt;/span&gt; LEGO BOOST==

==&lt;span class=&quot;anchor&quot; id=&quot;wedo2&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;wedo2_&quot;&gt;&lt;/span&gt; LEGO Education WeDo 2.0==

==References==

{{BookCat}}</text>
      <sha1>li9jyrzbajbyb10uxpy5u51vs2z2prw</sha1>
    </revision>
    <revision>
      <id>4656166</id>
      <parentid>4656163</parentid>
      <timestamp>2026-08-03T06:24:06Z</timestamp>
      <contributor>
        <username>Some helpful person</username>
        <id>3510188</id>
      </contributor>
      <origin>4656166</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="2773" sha1="rd0d9ajyebq3txvo51spwpjdjh889t1" xml:space="preserve">
The following lists every Scratch block that should be implemented in a Scratch VM. Each category of blocks has a subpage, with each block having a description, list of steps, and pseudocode. ({{Abbr|WIP.|Work in progress.}})

==[[/Motion|Motion]]==

* [[/Motion#movesteps|move (STEPS) steps]]
* [[/Motion#turnright|turn {{Abbr|⟳|clockwise, right}} (DEGREES) degrees]]
* [[/Motion#turnleft|turn {{Abbr|⟲|counterclockwise, left}} (DEGREES) degrees]]
* [[/Motion#goto|go to (TO)]]
* [[/Motion#gotoxy|go to x: (X) y: (Y)]]
* [[/Motion#glideto|glide (SECS) secs to (TO)]]
* [[/Motion#glidesecstoxy|glide (SECS) secs to x: (X) y: (Y)]]
* [[/Motion#pointindirection|point in direction (DIRECTION)]]
* [[/Motion#pointtowards|point towards (TOWARDS)]]
* [[/Motion#changexby|change x by (DX)]]
* [[/Motion#setx|set x to (X)]]
* [[/Motion#changeyby|change y by (DY)]]
* [[/Motion#sety|set y to (Y)]]
* [[/Motion#ifonedgebounce|if on edge, bounce]]
* [[/Motion#setrotationstyle|set rotation style (STYLE)]]
* [[/Motion#xposition|x position]]
* [[/Motion#yposition|y position]]
* [[/Motion#direction|direction]]
* [[/Motion#scroll_right|scroll right ()]]
* [[/Motion#scroll_up|scroll up ()]]
* [[/Motion#align_scene|align scene ()]]
* [[/Motion#xscroll|x scroll]]
* [[/Motion#yscroll|y scroll]]

==Looks==

==Sound==

==Events==

==Control==

==Sensing==

==Operators==

==Data==

==Procedures==

==&lt;span class=&quot;anchor&quot; id=&quot;coreExample&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;coreExample_&quot;&gt;&lt;/span&gt; Core Example==

==&lt;span class=&quot;anchor&quot; id=&quot;music&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;music_&quot;&gt;&lt;/span&gt; Music==

==&lt;span class=&quot;anchor&quot; id=&quot;pen&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;pen_&quot;&gt;&lt;/span&gt; Pen==

==&lt;span class=&quot;anchor&quot; id=&quot;videoSensing&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;videoSensing_&quot;&gt;&lt;/span&gt; Video Sensing==

==&lt;span class=&quot;anchor&quot; id=&quot;faceSensing&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;faceSensing_&quot;&gt;&lt;/span&gt; Face Sensing==

==&lt;span class=&quot;anchor&quot; id=&quot;text2speech&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;text2speech_&quot;&gt;&lt;/span&gt; Text to Speech==

==&lt;span class=&quot;anchor&quot; id=&quot;translate&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;translate_&quot;&gt;&lt;/span&gt; Translate==

==&lt;span class=&quot;anchor&quot; id=&quot;makeymakey&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;makeymakey_&quot;&gt;&lt;/span&gt; Makey Makey==

==&lt;span class=&quot;anchor&quot; id=&quot;microbit&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;microbit_&quot;&gt;&lt;/span&gt; micro:bit==

==&lt;span class=&quot;anchor&quot; id=&quot;gdxfor&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;gdxfor_&quot;&gt;&lt;/span&gt; Go Direct Force &amp; Acceleration==

==&lt;span class=&quot;anchor&quot; id=&quot;ev3&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;ev3_&quot;&gt;&lt;/span&gt; LEGO MINDSTORMS EV3==

==&lt;span class=&quot;anchor&quot; id=&quot;boost&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;boost_&quot;&gt;&lt;/span&gt; LEGO BOOST==

==&lt;span class=&quot;anchor&quot; id=&quot;wedo2&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;wedo2_&quot;&gt;&lt;/span&gt; LEGO Education WeDo 2.0==

==References==

{{BookCat}}</text>
      <sha1>rd0d9ajyebq3txvo51spwpjdjh889t1</sha1>
    </revision>
  </page>
  <page>
    <title>User talk:Masternod</title>
    <ns>3</ns>
    <id>485065</id>
    <revision>
      <id>4656144</id>
      <timestamp>2026-08-03T00:14:21Z</timestamp>
      <contributor>
        <username>MathXplore</username>
        <id>3097823</id>
      </contributor>
      <comment>Notifying author of speedy deletion nomination</comment>
      <origin>4656144</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="927" sha1="5r6fct5duxn7p75fetzja5tjs6jivm5" xml:space="preserve">
== I have added a tag to a page you created ==
Hi! I'm MathXplore, and I recently reviewed your page, [[:User:Masternod/sandbox]]. 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. The reason I provided was: &lt;blockquote&gt;&lt;strong&gt;Spam&lt;/strong&gt;&lt;/blockquote&gt; If you believe that your page should not be deleted, please post a message on [[User talk:Masternod/sandbox|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:MathXplore|let me know]]. Thank you! &lt;!-- Substituted from User:JJPMaster/CurateThisPage/authorMsg --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 00:14, 3 August 2026 (UTC)</text>
      <sha1>5r6fct5duxn7p75fetzja5tjs6jivm5</sha1>
    </revision>
  </page>
  <page>
    <title>User talk:~2026-42669-80</title>
    <ns>3</ns>
    <id>485066</id>
    <revision>
      <id>4656147</id>
      <timestamp>2026-08-03T00:16:40Z</timestamp>
      <contributor>
        <username>MathXplore</username>
        <id>3097823</id>
      </contributor>
      <comment>Notifying author of speedy deletion nomination</comment>
      <origin>4656147</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="946" sha1="92glj5rtrliajnkju9f75e27s48wa5b" xml:space="preserve">
== I have added a tag to a page you created ==
Hi! I'm MathXplore, and I recently reviewed your page, [[:AgilePM Project Management v3]]. 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. The reason I provided was: &lt;blockquote&gt;&lt;strong&gt;Test page&lt;/strong&gt;&lt;/blockquote&gt; If you believe that your page should not be deleted, please post a message on [[Talk:AgilePM Project Management v3|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:MathXplore|let me know]]. Thank you! &lt;!-- Substituted from User:JJPMaster/CurateThisPage/authorMsg --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 00:16, 3 August 2026 (UTC)</text>
      <sha1>92glj5rtrliajnkju9f75e27s48wa5b</sha1>
    </revision>
  </page>
  <page>
    <title>Scratch Virtual Machine/Blocks/Motion</title>
    <ns>0</ns>
    <id>485067</id>
    <revision>
      <id>4656159</id>
      <timestamp>2026-08-03T05:36:39Z</timestamp>
      <contributor>
        <username>Some helpful person</username>
        <id>3510188</id>
      </contributor>
      <comment>Created page with &quot; Motion blocks affect the position and direction of a sprite.&lt;ref&gt;{{Cite web |title=scratch3_motion.js |url=https://github.com/scratchfoundation/scratch-editor/blob/6fd95da6340916c2693452e012b52fbd13f19c50/packages/scratch-vm/src/blocks/scratch3_motion.js |access-date=2026-08-02 |publisher=[[:w:Scratch_Foundation|Scratch Foundation]] |language=en |via=[[:w:GitHub|GitHub]]}}&lt;/ref&gt;  ==&lt;span class=&quot;anchor&quot; id=&quot;motion_movesteps&quot;&gt;&lt;/span&gt; move (STEPS) steps==  Moves the sprite...&quot;</comment>
      <origin>4656159</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="8304" sha1="r1napltw9zdgmzly37xn5f8do4flefl" xml:space="preserve">
Motion blocks affect the position and direction of a sprite.&lt;ref&gt;{{Cite web |title=scratch3_motion.js |url=https://github.com/scratchfoundation/scratch-editor/blob/6fd95da6340916c2693452e012b52fbd13f19c50/packages/scratch-vm/src/blocks/scratch3_motion.js |access-date=2026-08-02 |publisher=[[:w:Scratch_Foundation|Scratch Foundation]] |language=en |via=[[:w:GitHub|GitHub]]}}&lt;/ref&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_movesteps&quot;&gt;&lt;/span&gt; move (STEPS) steps==

Moves the sprite STEPS forward in the direction it is facing.

* Casts STEPS to a number. (STEPS)
* Subtracts the target's direction from 90 and converts it to radians. (RADIANS)
* setXY(the target's X position plus STEPS multiplied by the cosine of RADIANS, the target's Y position plus STEPS multiplied by the sine of RADIANS)

&lt;syntaxhighlight lang=py&gt;
motion_movesteps(STEPS):
STEPS = castToNumber(STEPS)
RADIANS = degreesToRadians(90 - target.direction)
setXY(target.x + STEPS * cos(RADIANS), target.y + STEPS * sin(RADIANS))
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_turnright&quot;&gt;&lt;/span&gt; turn {{Abbr|⟳|clockwise, right}} (DEGREES) degrees ==

Rotates the sprite clockwise DEGREES degrees.

* Casts DEGREES to a number. (DEGREES)
* setDirection(the target's direction added to DEGREES)

&lt;syntaxhighlight lang=py&gt;
motion_turnright(DEGREES):
DEGREES = castToNumber(DEGREES)
setDirection(target.direction + DEGREES)
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_turnleft&quot;&gt;&lt;/span&gt; turn {{Abbr|⟲|counterclockwise, left}} (DEGREES) degrees ==

Rotates the sprite counterclockwise DEGREES degrees.

* Casts DEGREES to a number. (DEGREES)
* setDirection(the target's direction subtracted by DEGREES)

&lt;syntaxhighlight lang=py&gt;
motion_turnleft(DEGREES):
DEGREES = castToNumber(DEGREES)
setDirection(target.direction - DEGREES)
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_goto&quot;&gt;&lt;/span&gt; go to (TO)==

Moves the sprite to a particular set of X and Y coordinates as determined by TO.

* getTargetXY(TO) (X, Y)
* setXY(X, Y)

&lt;syntaxhighlight lang=py&gt;
motion_goto(TO):
X, Y = getTargetXY(TO)
setXY(X, Y)
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_gotoxy&quot;&gt;&lt;/span&gt; go to x: (X) y: (Y)==

Moves the sprite to the given X and Y coordinates.

* Casts X to a number. (X)
* Casts Y to a number. (Y)
* setXY(X, Y)

&lt;syntaxhighlight lang=py&gt;
motion_gotoxy(X, Y):
X = castToNumber(X)
Y = castToNumber(Y)
setXY(X, Y)
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_glideto&quot;&gt;&lt;/span&gt; glide (SECS) secs to (TO)==

Linearly transitions the sprite to a particular set of X and Y coordinates as determined by TO over a SECS second period.

* getTargetXY(TO) (X, Y)
* glide(SECS, X, Y)

&lt;syntaxhighlight lang=py&gt;
motion_glideto(SECS, TO):
X, Y = getTargetXY(TO)
motion_glidesecstoxy(SECS, X, Y)
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_glidesecstoxy&quot;&gt;&lt;/span&gt; glide (SECS) secs to x: (X) y: (Y)==

Linearly transitions the sprite to the given X and Y coordinates over a SECS second period.
{{TODO|Explain how glide works.}}&lt;syntaxhighlight lang=py&gt;
motion_glidesecstoxy(SECS, X, Y):
...
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_pointindirection&quot;&gt;&lt;/span&gt; point in direction (DIRECTION)==

Rotates the sprite such that it faces the given DIRECTION in degrees.

* Casts DIRECTION to a number. (DIRECTION)
* setDirection(DIRECTION)

&lt;syntaxhighlight lang=py&gt;
motion_pointindirection(DIRECTION):
DIRECTION = castToNumber(DIRECTION)
setDirection(DIRECTION)
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_pointtowards&quot;&gt;&lt;/span&gt; point towards (TOWARDS)==

Rotates the sprite such that it faces a particular direction as determined by TOWARDS.

* If TOWARDS is the string &lt;code&gt;_mouse_&lt;/code&gt;:
** Subtracts the target's X position from the X position of the mouse-pointer. (DX)
** Subtracts the target's Y position from the Y position of the mouse-pointer. (DY)
** Converts the 2-argument arctangent of DY and DX in radians to degrees. (DIRECTION)
** setDirection(DIRECTION)
* Otherwise, if TOWARDS is the string &lt;code&gt;_random_&lt;/code&gt;:
** setDirection(a random integer on the interval [-180, 180], with -180 and 180 being twice as unlikely as other values)
* Otherwise:
** Casts TOWARDS to a string. (TOWARDS)
** Finds the sprite by the name of TOWARDS. (SPRITE)
** If SPRITE exists:
*** Subtracts the target's X position from SPRITE's X position. (DX)
*** Subtracts the target's Y position from SPRITE's Y position. (DY)
*** Converts the 2-argument arctangent of DY and DX in radians to degrees. (DIRECTION)
*** setDirection(DIRECTION)
** Otherwise, does nothing.

&lt;syntaxhighlight lang=py&gt;
motion_pointtowards(TOWARDS):
if TOWARDS is &quot;_mouse_&quot;
    DX = mouse.x - target.x
    DY = mouse.y - target.y
    DIRECTION = radiansToDegrees(atan2(DY, DX))
    setDirection(DIRECTION)
else if TOWARDS is &quot;_random_&quot;
    setDirection(round(random() * 360) - 180)
else
    TOWARDS = castToString(TOWARDS)
    SPRITE = getSpriteNamed(TOWARDS)
    if SPRITE exists
        DX = SPRITE.x - target.x
        DY = SPRITE.y - target.y
        DIRECTION = radiansToDegrees(atan2(DY, DX))
        setDirection(DIRECTION)
    else
        (do nothing)
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_changexby&quot;&gt;&lt;/span&gt; change x by (DX)==

Increases the target's X position by DX.

* Casts DX to a number. (DX)
* setXY(DX added to the target's X position, the target's Y position)

&lt;syntaxhighlight lang=py&gt;
motion_changexby(DX):
DX = castToNumber(DX)
setXY(target.x + DX, target.y)
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_setx&quot;&gt;&lt;/span&gt; set x to (X)==

Sets the target's X position to X.

* Casts X to a number. (X)
* setXY(X, the target's Y position)

&lt;syntaxhighlight lang=py&gt;
motion_setx(X):
X = castToNumber(X)
setXY(X, target.y)
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_changeyby&quot;&gt;&lt;/span&gt; change y by (DY)==

Increases the target's Y position by DY.

* Casts DY to a number. (DY)
* setXY(the target's X position, DY added to the target's Y position)

&lt;syntaxhighlight lang=py&gt;
motion_changeyby(DY):
DY = castToNumber(DY)
setXY(target.x, target.y + DY)
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_sety&quot;&gt;&lt;/span&gt; set y to (Y)==

Sets the target's Y position to Y.

* Casts Y to a number. (Y)
* setXY(the target's X position, Y)

&lt;syntaxhighlight lang=py&gt;
motion_sety(Y):
Y = castToNumber(Y)
setXY(target.X, Y)
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_ifonedgebounce&quot;&gt;&lt;/span&gt; if on edge, bounce==

{{TODO|Explain how if on edge, bounce works.}}&lt;syntaxhighlight lang=py&gt;
motion_ifonedgebounce():
...
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_setrotationstyle&quot;&gt;&lt;/span&gt; set rotation style (STYLE)==

Sets the target's rotation style as determined by STYLE.

* If STYLE is one of the strings &lt;code&gt;don't rotate&lt;/code&gt;, &lt;code&gt;all around&lt;/code&gt;, or &lt;code&gt;left-right&lt;/code&gt;, sets the target's rotation style to STYLE.
* If the sprite is visible, requests to redraw the screen.

&lt;syntaxhighlight lang=py&gt;
motion_setrotationstyle(STYLE):
if STYLE is &quot;don't rotate&quot; or is &quot;all around&quot; or is &quot;left-right&quot;
    target.rotationStyle = STYLE
if target.visible
    redraw()
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_xposition&quot;&gt;&lt;/span&gt; x position==

Reports the target's X position.

* If the target's X position is less than 1e-9 away from the nearest integer:
** Reports the target's X position rounded to the nearest integer.
* Otherwise:
** Reports the target's X position.

&lt;syntaxhighlight lang=py&gt;
motion_xposition():
if abs(target.x - round(target.x)) &lt; 1e-9
    return round(target.x)
else
    return target.x
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_yposition&quot;&gt;&lt;/span&gt; y position==

Reports the target's Y position.

* If the target's Y position is less than 1e-9 away from the nearest integer:
** Reports the target's Y position rounded to the nearest integer.
* Otherwise:
** Reports the target's Y position.

&lt;syntaxhighlight lang=py&gt;
motion_yposition():
if abs(target.y - round(target.y)) &lt; 1e-9
    return round(target.y)
else
    return target.y
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_direction&quot;&gt;&lt;/span&gt; direction==

Reports the target's direction.

* Reports the target's direction in degrees.

&lt;syntaxhighlight lang=py&gt;
motion_direction():
return target.direction
&lt;/syntaxhighlight&gt;

==References==

{{BookCat}}</text>
      <sha1>r1napltw9zdgmzly37xn5f8do4flefl</sha1>
    </revision>
    <revision>
      <id>4656161</id>
      <parentid>4656159</parentid>
      <timestamp>2026-08-03T05:47:44Z</timestamp>
      <contributor>
        <username>Some helpful person</username>
        <id>3510188</id>
      </contributor>
      <minor />
      <origin>4656161</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="9081" sha1="2ky3upqtb4q4lignoewlja7kiny10gt" xml:space="preserve">
Motion blocks affect the position and direction of a sprite.&lt;ref&gt;{{Cite web |title=scratch3_motion.js |url=https://github.com/scratchfoundation/scratch-editor/blob/6fd95da6340916c2693452e012b52fbd13f19c50/packages/scratch-vm/src/blocks/scratch3_motion.js |access-date=2026-08-02 |publisher=[[:w:Scratch_Foundation|Scratch Foundation]] |language=en |via=[[:w:GitHub|GitHub]]}}&lt;/ref&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_movesteps&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;movesteps&quot;&gt;&lt;/span&gt; move (STEPS) steps==

Moves the sprite STEPS forward in the direction it is facing.

* Casts STEPS to a number. (STEPS)
* Subtracts the target's direction from 90 and converts it to radians. (RADIANS)
* setXY(the target's X position plus STEPS multiplied by the cosine of RADIANS, the target's Y position plus STEPS multiplied by the sine of RADIANS)

&lt;syntaxhighlight lang=py&gt;
motion_movesteps(STEPS):
STEPS = castToNumber(STEPS)
RADIANS = degreesToRadians(90 - target.direction)
setXY(target.x + STEPS * cos(RADIANS), target.y + STEPS * sin(RADIANS))
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_turnright&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;turnright&quot;&gt;&lt;/span&gt; turn {{Abbr|⟳|clockwise, right}} (DEGREES) degrees==

Rotates the sprite clockwise DEGREES degrees.

* Casts DEGREES to a number. (DEGREES)
* setDirection(the target's direction added to DEGREES)

&lt;syntaxhighlight lang=py&gt;
motion_turnright(DEGREES):
DEGREES = castToNumber(DEGREES)
setDirection(target.direction + DEGREES)
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_turnleft&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;turnleft&quot;&gt;&lt;/span&gt; turn {{Abbr|⟲|counterclockwise, left}} (DEGREES) degrees==

Rotates the sprite counterclockwise DEGREES degrees.

* Casts DEGREES to a number. (DEGREES)
* setDirection(the target's direction subtracted by DEGREES)

&lt;syntaxhighlight lang=py&gt;
motion_turnleft(DEGREES):
DEGREES = castToNumber(DEGREES)
setDirection(target.direction - DEGREES)
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_goto&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;goto&quot;&gt;&lt;/span&gt; go to (TO)==

Moves the sprite to a particular set of X and Y coordinates as determined by TO.

* getTargetXY(TO) (X, Y)
* setXY(X, Y)

&lt;syntaxhighlight lang=py&gt;
motion_goto(TO):
X, Y = getTargetXY(TO)
setXY(X, Y)
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_gotoxy&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;gotoxy&quot;&gt;&lt;/span&gt; go to x: (X) y: (Y)==

Moves the sprite to the given X and Y coordinates.

* Casts X to a number. (X)
* Casts Y to a number. (Y)
* setXY(X, Y)

&lt;syntaxhighlight lang=py&gt;
motion_gotoxy(X, Y):
X = castToNumber(X)
Y = castToNumber(Y)
setXY(X, Y)
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_glideto&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;glideto&quot;&gt;&lt;/span&gt; glide (SECS) secs to (TO)==

Linearly transitions the sprite to a particular set of X and Y coordinates as determined by TO over a SECS second period.

* getTargetXY(TO) (X, Y)
* glide(SECS, X, Y)

&lt;syntaxhighlight lang=py&gt;
motion_glideto(SECS, TO):
X, Y = getTargetXY(TO)
motion_glidesecstoxy(SECS, X, Y)
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_glidesecstoxy&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;glidesecstoxy&quot;&gt;&lt;/span&gt; glide (SECS) secs to x: (X) y: (Y)==

Linearly transitions the sprite to the given X and Y coordinates over a SECS second period.
{{TODO|Explain how glide works.}}&lt;syntaxhighlight lang=py&gt;
motion_glidesecstoxy(SECS, X, Y):
...
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_pointindirection&quot;&gt;&lt;span class=&quot;anchor&quot; id=&quot;pointindirection&quot;&gt;&lt;/span&gt;&lt;/span&gt; point in direction (DIRECTION)==

Rotates the sprite such that it faces the given DIRECTION in degrees.

* Casts DIRECTION to a number. (DIRECTION)
* setDirection(DIRECTION)

&lt;syntaxhighlight lang=py&gt;
motion_pointindirection(DIRECTION):
DIRECTION = castToNumber(DIRECTION)
setDirection(DIRECTION)
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_pointtowards&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;pointtowards&quot;&gt;&lt;/span&gt; point towards (TOWARDS)==

Rotates the sprite such that it faces a particular direction as determined by TOWARDS.

* If TOWARDS is the string &lt;code&gt;_mouse_&lt;/code&gt;:
** Subtracts the target's X position from the X position of the mouse-pointer. (DX)
** Subtracts the target's Y position from the Y position of the mouse-pointer. (DY)
** Converts the 2-argument arctangent of DY and DX in radians to degrees. (DIRECTION)
** setDirection(DIRECTION)
* Otherwise, if TOWARDS is the string &lt;code&gt;_random_&lt;/code&gt;:
** setDirection(a random integer on the interval [-180, 180], with -180 and 180 being twice as unlikely as other values)
* Otherwise:
** Casts TOWARDS to a string. (TOWARDS)
** Finds the sprite by the name of TOWARDS. (SPRITE)
** If SPRITE exists:
*** Subtracts the target's X position from SPRITE's X position. (DX)
*** Subtracts the target's Y position from SPRITE's Y position. (DY)
*** Converts the 2-argument arctangent of DY and DX in radians to degrees. (DIRECTION)
*** setDirection(DIRECTION)
** Otherwise, does nothing.

&lt;syntaxhighlight lang=py&gt;
motion_pointtowards(TOWARDS):
if TOWARDS is &quot;_mouse_&quot;
    DX = mouse.x - target.x
    DY = mouse.y - target.y
    DIRECTION = radiansToDegrees(atan2(DY, DX))
    setDirection(DIRECTION)
else if TOWARDS is &quot;_random_&quot;
    setDirection(round(random() * 360) - 180)
else
    TOWARDS = castToString(TOWARDS)
    SPRITE = getSpriteNamed(TOWARDS)
    if SPRITE exists
        DX = SPRITE.x - target.x
        DY = SPRITE.y - target.y
        DIRECTION = radiansToDegrees(atan2(DY, DX))
        setDirection(DIRECTION)
    else
        (do nothing)
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_changexby&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;changexby&quot;&gt;&lt;/span&gt; change x by (DX)==

Increases the target's X position by DX.

* Casts DX to a number. (DX)
* setXY(DX added to the target's X position, the target's Y position)

&lt;syntaxhighlight lang=py&gt;
motion_changexby(DX):
DX = castToNumber(DX)
setXY(target.x + DX, target.y)
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_setx&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;setx&quot;&gt;&lt;/span&gt; set x to (X)==

Sets the target's X position to X.

* Casts X to a number. (X)
* setXY(X, the target's Y position)

&lt;syntaxhighlight lang=py&gt;
motion_setx(X):
X = castToNumber(X)
setXY(X, target.y)
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_changeyby&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;changeyby&quot;&gt;&lt;/span&gt; change y by (DY)==

Increases the target's Y position by DY.

* Casts DY to a number. (DY)
* setXY(the target's X position, DY added to the target's Y position)

&lt;syntaxhighlight lang=py&gt;
motion_changeyby(DY):
DY = castToNumber(DY)
setXY(target.x, target.y + DY)
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_sety&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;sety&quot;&gt;&lt;/span&gt; set y to (Y)==

Sets the target's Y position to Y.

* Casts Y to a number. (Y)
* setXY(the target's X position, Y)

&lt;syntaxhighlight lang=py&gt;
motion_sety(Y):
Y = castToNumber(Y)
setXY(target.X, Y)
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_ifonedgebounce&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;ifonedgebounce&quot;&gt;&lt;/span&gt; if on edge, bounce==

{{TODO|Explain how if on edge, bounce works.}}&lt;syntaxhighlight lang=py&gt;
motion_ifonedgebounce():
...
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_setrotationstyle&quot;&gt;&lt;span class=&quot;anchor&quot; id=&quot;setrotationstyle&quot;&gt;&lt;/span&gt;&lt;/span&gt; set rotation style (STYLE)==

Sets the target's rotation style as determined by STYLE.

* If STYLE is one of the strings &lt;code&gt;don't rotate&lt;/code&gt;, &lt;code&gt;all around&lt;/code&gt;, or &lt;code&gt;left-right&lt;/code&gt;, sets the target's rotation style to STYLE.
* If the sprite is visible, requests to redraw the screen.

&lt;syntaxhighlight lang=py&gt;
motion_setrotationstyle(STYLE):
if STYLE is &quot;don't rotate&quot; or is &quot;all around&quot; or is &quot;left-right&quot;
    target.rotationStyle = STYLE
if target.visible
    redraw()
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_xposition&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;xposition&quot;&gt;&lt;/span&gt; x position==

Reports the target's X position.

* If the target's X position is less than 1e-9 away from the nearest integer:
** Reports the target's X position rounded to the nearest integer.
* Otherwise:
** Reports the target's X position.

&lt;syntaxhighlight lang=py&gt;
motion_xposition():
if abs(target.x - round(target.x)) &lt; 1e-9
    return round(target.x)
else
    return target.x
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_yposition&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;yposition&quot;&gt;&lt;/span&gt; y position==

Reports the target's Y position.

* If the target's Y position is less than 1e-9 away from the nearest integer:
** Reports the target's Y position rounded to the nearest integer.
* Otherwise:
** Reports the target's Y position.

&lt;syntaxhighlight lang=py&gt;
motion_yposition():
if abs(target.y - round(target.y)) &lt; 1e-9
    return round(target.y)
else
    return target.y
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_direction&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;direction&quot;&gt;&lt;/span&gt; direction==

Reports the target's direction.

* Reports the target's direction in degrees.

&lt;syntaxhighlight lang=py&gt;
motion_direction():
return target.direction
&lt;/syntaxhighlight&gt;

==References==

{{BookCat}}</text>
      <sha1>2ky3upqtb4q4lignoewlja7kiny10gt</sha1>
    </revision>
    <revision>
      <id>4656164</id>
      <parentid>4656161</parentid>
      <timestamp>2026-08-03T06:09:11Z</timestamp>
      <contributor>
        <username>Some helpful person</username>
        <id>3510188</id>
      </contributor>
      <comment>add hidden blocks</comment>
      <origin>4656164</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="10719" sha1="odqrisadlwhkhtdyrpsyiwpum84n0gl" xml:space="preserve">
Motion blocks affect the position and direction of a sprite.&lt;ref&gt;{{Cite web |title=scratch3_motion.js |url=https://github.com/scratchfoundation/scratch-editor/blob/6fd95da6340916c2693452e012b52fbd13f19c50/packages/scratch-vm/src/blocks/scratch3_motion.js |access-date=2026-08-02 |publisher=[[:w:Scratch_Foundation|Scratch Foundation]] |language=en |via=[[:w:GitHub|GitHub]]}}&lt;/ref&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_movesteps&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;movesteps&quot;&gt;&lt;/span&gt; move (STEPS) steps==

Moves the sprite STEPS forward in the direction it is facing.

* Casts STEPS to a number. (STEPS)
* Subtracts the target's direction from 90 and converts it to radians. (RADIANS)
* setXY(the target's X position plus STEPS multiplied by the cosine of RADIANS, the target's Y position plus STEPS multiplied by the sine of RADIANS)

&lt;syntaxhighlight lang=py&gt;
motion_movesteps(STEPS):
STEPS = castToNumber(STEPS)
RADIANS = degreesToRadians(90 - target.direction)
setXY(target.x + STEPS * cos(RADIANS), target.y + STEPS * sin(RADIANS))
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_turnright&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;turnright&quot;&gt;&lt;/span&gt; turn {{Abbr|⟳|clockwise, right}} (DEGREES) degrees==

Rotates the sprite clockwise DEGREES degrees.

* Casts DEGREES to a number. (DEGREES)
* setDirection(the target's direction added to DEGREES)

&lt;syntaxhighlight lang=py&gt;
motion_turnright(DEGREES):
DEGREES = castToNumber(DEGREES)
setDirection(target.direction + DEGREES)
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_turnleft&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;turnleft&quot;&gt;&lt;/span&gt; turn {{Abbr|⟲|counterclockwise, left}} (DEGREES) degrees==

Rotates the sprite counterclockwise DEGREES degrees.

* Casts DEGREES to a number. (DEGREES)
* setDirection(the target's direction subtracted by DEGREES)

&lt;syntaxhighlight lang=py&gt;
motion_turnleft(DEGREES):
DEGREES = castToNumber(DEGREES)
setDirection(target.direction - DEGREES)
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_goto&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;goto&quot;&gt;&lt;/span&gt; go to (TO)==

Moves the sprite to a particular set of X and Y coordinates as determined by TO.

* getTargetXY(TO) (X, Y)
* setXY(X, Y)

&lt;syntaxhighlight lang=py&gt;
motion_goto(TO):
X, Y = getTargetXY(TO)
setXY(X, Y)
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_gotoxy&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;gotoxy&quot;&gt;&lt;/span&gt; go to x: (X) y: (Y)==

Moves the sprite to the given X and Y coordinates.

* Casts X to a number. (X)
* Casts Y to a number. (Y)
* setXY(X, Y)

&lt;syntaxhighlight lang=py&gt;
motion_gotoxy(X, Y):
X = castToNumber(X)
Y = castToNumber(Y)
setXY(X, Y)
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_glideto&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;glideto&quot;&gt;&lt;/span&gt; glide (SECS) secs to (TO)==

Linearly transitions the sprite to a particular set of X and Y coordinates as determined by TO over a SECS second period.

* getTargetXY(TO) (X, Y)
* glide(SECS, X, Y)

&lt;syntaxhighlight lang=py&gt;
motion_glideto(SECS, TO):
X, Y = getTargetXY(TO)
motion_glidesecstoxy(SECS, X, Y)
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_glidesecstoxy&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;glidesecstoxy&quot;&gt;&lt;/span&gt; glide (SECS) secs to x: (X) y: (Y)==

Linearly transitions the sprite to the given X and Y coordinates over a SECS second period.
{{TODO|Explain how glide works.}}&lt;syntaxhighlight lang=py&gt;
motion_glidesecstoxy(SECS, X, Y):
...
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_pointindirection&quot;&gt;&lt;span class=&quot;anchor&quot; id=&quot;pointindirection&quot;&gt;&lt;/span&gt;&lt;/span&gt; point in direction (DIRECTION)==

Rotates the sprite such that it faces the given DIRECTION in degrees.

* Casts DIRECTION to a number. (DIRECTION)
* setDirection(DIRECTION)

&lt;syntaxhighlight lang=py&gt;
motion_pointindirection(DIRECTION):
DIRECTION = castToNumber(DIRECTION)
setDirection(DIRECTION)
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_pointtowards&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;pointtowards&quot;&gt;&lt;/span&gt; point towards (TOWARDS)==

Rotates the sprite such that it faces a particular direction as determined by TOWARDS.

* If TOWARDS is the string &lt;code&gt;_mouse_&lt;/code&gt;:
** Subtracts the target's X position from the X position of the mouse-pointer. (DX)
** Subtracts the target's Y position from the Y position of the mouse-pointer. (DY)
** Converts the 2-argument arctangent of DY and DX in radians to degrees. (DIRECTION)
** setDirection(DIRECTION)
* Otherwise, if TOWARDS is the string &lt;code&gt;_random_&lt;/code&gt;:
** setDirection(a random integer on the interval [-180, 180], with -180 and 180 being twice as unlikely as other values)
* Otherwise:
** Casts TOWARDS to a string. (TOWARDS)
** Finds the sprite by the name of TOWARDS. (SPRITE)
** If SPRITE exists:
*** Subtracts the target's X position from SPRITE's X position. (DX)
*** Subtracts the target's Y position from SPRITE's Y position. (DY)
*** Converts the 2-argument arctangent of DY and DX in radians to degrees. (DIRECTION)
*** setDirection(DIRECTION)
** Otherwise, does nothing.

&lt;syntaxhighlight lang=py&gt;
motion_pointtowards(TOWARDS):
if TOWARDS is &quot;_mouse_&quot;
    DX = mouse.x - target.x
    DY = mouse.y - target.y
    DIRECTION = radiansToDegrees(atan2(DY, DX))
    setDirection(DIRECTION)
else if TOWARDS is &quot;_random_&quot;
    setDirection(round(random() * 360) - 180)
else
    TOWARDS = castToString(TOWARDS)
    SPRITE = getSpriteNamed(TOWARDS)
    if SPRITE exists
        DX = SPRITE.x - target.x
        DY = SPRITE.y - target.y
        DIRECTION = radiansToDegrees(atan2(DY, DX))
        setDirection(DIRECTION)
    else
        (do nothing)
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_changexby&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;changexby&quot;&gt;&lt;/span&gt; change x by (DX)==

Increases the target's X position by DX.

* Casts DX to a number. (DX)
* setXY(DX added to the target's X position, the target's Y position)

&lt;syntaxhighlight lang=py&gt;
motion_changexby(DX):
DX = castToNumber(DX)
setXY(target.x + DX, target.y)
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_setx&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;setx&quot;&gt;&lt;/span&gt; set x to (X)==

Sets the target's X position to X.

* Casts X to a number. (X)
* setXY(X, the target's Y position)

&lt;syntaxhighlight lang=py&gt;
motion_setx(X):
X = castToNumber(X)
setXY(X, target.y)
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_changeyby&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;changeyby&quot;&gt;&lt;/span&gt; change y by (DY)==

Increases the target's Y position by DY.

* Casts DY to a number. (DY)
* setXY(the target's X position, DY added to the target's Y position)

&lt;syntaxhighlight lang=py&gt;
motion_changeyby(DY):
DY = castToNumber(DY)
setXY(target.x, target.y + DY)
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_sety&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;sety&quot;&gt;&lt;/span&gt; set y to (Y)==

Sets the target's Y position to Y.

* Casts Y to a number. (Y)
* setXY(the target's X position, Y)

&lt;syntaxhighlight lang=py&gt;
motion_sety(Y):
Y = castToNumber(Y)
setXY(target.X, Y)
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_ifonedgebounce&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;ifonedgebounce&quot;&gt;&lt;/span&gt; if on edge, bounce==

{{TODO|Explain how if on edge, bounce works.}}&lt;syntaxhighlight lang=py&gt;
motion_ifonedgebounce():
...
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_setrotationstyle&quot;&gt;&lt;span class=&quot;anchor&quot; id=&quot;setrotationstyle&quot;&gt;&lt;/span&gt;&lt;/span&gt; set rotation style (STYLE)==

Sets the target's rotation style as determined by STYLE.

* If STYLE is one of the strings &lt;code&gt;don't rotate&lt;/code&gt;, &lt;code&gt;all around&lt;/code&gt;, or &lt;code&gt;left-right&lt;/code&gt;, sets the target's rotation style to STYLE.
* If the sprite is visible, requests to redraw the screen.

&lt;syntaxhighlight lang=py&gt;
motion_setrotationstyle(STYLE):
if STYLE is &quot;don't rotate&quot; or is &quot;all around&quot; or is &quot;left-right&quot;
    target.rotationStyle = STYLE
if target.visible
    redraw()
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_xposition&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;xposition&quot;&gt;&lt;/span&gt; x position==

Reports the target's X position.

* If the target's X position is less than 1e-9 away from the nearest integer:
** Reports the target's X position rounded to the nearest integer.
* Otherwise:
** Reports the target's X position.

&lt;syntaxhighlight lang=py&gt;
motion_xposition():
if abs(target.x - round(target.x)) &lt; 1e-9
    return round(target.x)
else
    return target.x
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_yposition&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;yposition&quot;&gt;&lt;/span&gt; y position==

Reports the target's Y position.

* If the target's Y position is less than 1e-9 away from the nearest integer:
** Reports the target's Y position rounded to the nearest integer.
* Otherwise:
** Reports the target's Y position.

&lt;syntaxhighlight lang=py&gt;
motion_yposition():
if abs(target.y - round(target.y)) &lt; 1e-9
    return round(target.y)
else
    return target.y
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_direction&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;direction&quot;&gt;&lt;/span&gt; direction==

Reports the target's direction.

* Reports the target's direction in degrees.

&lt;syntaxhighlight lang=py&gt;
motion_direction():
return target.direction
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_scroll_right&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;scroll_right&quot;&gt;&lt;/span&gt; scroll right ()==

Does nothing. This is a legacy block retained for backwards compatibility with Scratch 2.0 and is not visible in the block palette.

&lt;syntaxhighlight lang=py&gt;
motion_scroll_right():
(do nothing)
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_scroll_up&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;scroll_up&quot;&gt;&lt;/span&gt; scroll up ()==

Does nothing. This is a legacy block retained for backwards compatibility with Scratch 2.0 and is not visible in the block palette.

&lt;syntaxhighlight lang=py&gt;
motion_scroll_up():
(do nothing)
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_align_scene&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;align_scene&quot;&gt;&lt;/span&gt; align scene ()==

Does nothing. This is a legacy block retained for backwards compatibility with Scratch 2.0 and is not visible in the block palette.

&lt;syntaxhighlight lang=py&gt;
motion_align_scene():
(do nothing)
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_xscroll&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;xscroll&quot;&gt;&lt;/span&gt; x scroll==

Reports undefined. This is a legacy block retained for backwards compatibility with Scratch 2.0 and is not visible in the block palette.

&lt;syntaxhighlight lang=py&gt;
motion_xscroll():
return undefined
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_yscroll&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;yscroll&quot;&gt;&lt;/span&gt; y scroll==

Reports undefined. This is a legacy block retained for backwards compatibility with Scratch 2.0 and is not visible in the block palette.

&lt;syntaxhighlight lang=py&gt;
motion_yscroll():
return undefined
&lt;/syntaxhighlight&gt;

==References==

{{BookCat}}</text>
      <sha1>odqrisadlwhkhtdyrpsyiwpum84n0gl</sha1>
    </revision>
    <revision>
      <id>4656165</id>
      <parentid>4656164</parentid>
      <timestamp>2026-08-03T06:16:44Z</timestamp>
      <contributor>
        <username>Some helpful person</username>
        <id>3510188</id>
      </contributor>
      <minor />
      <comment>typos</comment>
      <origin>4656165</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="10719" sha1="bknn9qdyle24dms57ialfb6dde7qoxe" xml:space="preserve">
Motion blocks affect the position and direction of a sprite.&lt;ref&gt;{{Cite web |title=scratch3_motion.js |url=https://github.com/scratchfoundation/scratch-editor/blob/6fd95da6340916c2693452e012b52fbd13f19c50/packages/scratch-vm/src/blocks/scratch3_motion.js |access-date=2026-08-02 |publisher=[[:w:Scratch_Foundation|Scratch Foundation]] |language=en |via=[[:w:GitHub|GitHub]]}}&lt;/ref&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_movesteps&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;movesteps&quot;&gt;&lt;/span&gt; move (STEPS) steps==

Moves the sprite STEPS forward in the direction it is facing.

* Casts STEPS to a number. (STEPS)
* Subtracts the target's direction from 90 and converts it to radians. (RADIANS)
* setXY(the target's X position plus STEPS multiplied by the cosine of RADIANS, the target's Y position plus STEPS multiplied by the sine of RADIANS)

&lt;syntaxhighlight lang=py&gt;
motion_movesteps(STEPS):
STEPS = castToNumber(STEPS)
RADIANS = degreesToRadians(90 - target.direction)
setXY(target.x + STEPS * cos(RADIANS), target.y + STEPS * sin(RADIANS))
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_turnright&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;turnright&quot;&gt;&lt;/span&gt; turn {{Abbr|⟳|clockwise, right}} (DEGREES) degrees==

Rotates the sprite clockwise DEGREES degrees.

* Casts DEGREES to a number. (DEGREES)
* setDirection(the target's direction added to DEGREES)

&lt;syntaxhighlight lang=py&gt;
motion_turnright(DEGREES):
DEGREES = castToNumber(DEGREES)
setDirection(target.direction + DEGREES)
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_turnleft&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;turnleft&quot;&gt;&lt;/span&gt; turn {{Abbr|⟲|counterclockwise, left}} (DEGREES) degrees==

Rotates the sprite counterclockwise DEGREES degrees.

* Casts DEGREES to a number. (DEGREES)
* setDirection(the target's direction subtracted by DEGREES)

&lt;syntaxhighlight lang=py&gt;
motion_turnleft(DEGREES):
DEGREES = castToNumber(DEGREES)
setDirection(target.direction - DEGREES)
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_goto&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;goto&quot;&gt;&lt;/span&gt; go to (TO)==

Moves the sprite to a particular set of X and Y coordinates as determined by TO.

* getTargetXY(TO) (X, Y)
* setXY(X, Y)

&lt;syntaxhighlight lang=py&gt;
motion_goto(TO):
X, Y = getTargetXY(TO)
setXY(X, Y)
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_gotoxy&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;gotoxy&quot;&gt;&lt;/span&gt; go to x: (X) y: (Y)==

Moves the sprite to the given X and Y coordinates.

* Casts X to a number. (X)
* Casts Y to a number. (Y)
* setXY(X, Y)

&lt;syntaxhighlight lang=py&gt;
motion_gotoxy(X, Y):
X = castToNumber(X)
Y = castToNumber(Y)
setXY(X, Y)
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_glideto&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;glideto&quot;&gt;&lt;/span&gt; glide (SECS) secs to (TO)==

Linearly transitions the sprite to a particular set of X and Y coordinates as determined by TO over a SECS second period.

* getTargetXY(TO) (X, Y)
* glide(SECS, X, Y)

&lt;syntaxhighlight lang=py&gt;
motion_glideto(SECS, TO):
X, Y = getTargetXY(TO)
motion_glidesecstoxy(SECS, X, Y)
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_glidesecstoxy&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;glidesecstoxy&quot;&gt;&lt;/span&gt; glide (SECS) secs to x: (X) y: (Y)==

Linearly transitions the sprite to the given X and Y coordinates over a SECS second period.
{{TODO|Explain how glide works.}}&lt;syntaxhighlight lang=py&gt;
motion_glidesecstoxy(SECS, X, Y):
...
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_pointindirection&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;pointindirection&quot;&gt;&lt;/span&gt; point in direction (DIRECTION)==

Rotates the sprite such that it faces the given DIRECTION in degrees.

* Casts DIRECTION to a number. (DIRECTION)
* setDirection(DIRECTION)

&lt;syntaxhighlight lang=py&gt;
motion_pointindirection(DIRECTION):
DIRECTION = castToNumber(DIRECTION)
setDirection(DIRECTION)
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_pointtowards&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;pointtowards&quot;&gt;&lt;/span&gt; point towards (TOWARDS)==

Rotates the sprite such that it faces a particular direction as determined by TOWARDS.

* If TOWARDS is the string &lt;code&gt;_mouse_&lt;/code&gt;:
** Subtracts the target's X position from the X position of the mouse-pointer. (DX)
** Subtracts the target's Y position from the Y position of the mouse-pointer. (DY)
** Converts the 2-argument arctangent of DY and DX in radians to degrees. (DIRECTION)
** setDirection(DIRECTION)
* Otherwise, if TOWARDS is the string &lt;code&gt;_random_&lt;/code&gt;:
** setDirection(a random integer on the interval [-180, 180], with -180 and 180 being twice as unlikely as other values)
* Otherwise:
** Casts TOWARDS to a string. (TOWARDS)
** Finds the sprite by the name of TOWARDS. (SPRITE)
** If SPRITE exists:
*** Subtracts the target's X position from SPRITE's X position. (DX)
*** Subtracts the target's Y position from SPRITE's Y position. (DY)
*** Converts the 2-argument arctangent of DY and DX in radians to degrees. (DIRECTION)
*** setDirection(DIRECTION)
** Otherwise, does nothing.

&lt;syntaxhighlight lang=py&gt;
motion_pointtowards(TOWARDS):
if TOWARDS is &quot;_mouse_&quot;
    DX = mouse.x - target.x
    DY = mouse.y - target.y
    DIRECTION = radiansToDegrees(atan2(DY, DX))
    setDirection(DIRECTION)
else if TOWARDS is &quot;_random_&quot;
    setDirection(round(random() * 360) - 180)
else
    TOWARDS = castToString(TOWARDS)
    SPRITE = getSpriteNamed(TOWARDS)
    if SPRITE exists
        DX = SPRITE.x - target.x
        DY = SPRITE.y - target.y
        DIRECTION = radiansToDegrees(atan2(DY, DX))
        setDirection(DIRECTION)
    else
        (do nothing)
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_changexby&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;changexby&quot;&gt;&lt;/span&gt; change x by (DX)==

Increases the target's X position by DX.

* Casts DX to a number. (DX)
* setXY(DX added to the target's X position, the target's Y position)

&lt;syntaxhighlight lang=py&gt;
motion_changexby(DX):
DX = castToNumber(DX)
setXY(target.x + DX, target.y)
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_setx&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;setx&quot;&gt;&lt;/span&gt; set x to (X)==

Sets the target's X position to X.

* Casts X to a number. (X)
* setXY(X, the target's Y position)

&lt;syntaxhighlight lang=py&gt;
motion_setx(X):
X = castToNumber(X)
setXY(X, target.y)
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_changeyby&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;changeyby&quot;&gt;&lt;/span&gt; change y by (DY)==

Increases the target's Y position by DY.

* Casts DY to a number. (DY)
* setXY(the target's X position, DY added to the target's Y position)

&lt;syntaxhighlight lang=py&gt;
motion_changeyby(DY):
DY = castToNumber(DY)
setXY(target.x, target.y + DY)
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_sety&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;sety&quot;&gt;&lt;/span&gt; set y to (Y)==

Sets the target's Y position to Y.

* Casts Y to a number. (Y)
* setXY(the target's X position, Y)

&lt;syntaxhighlight lang=py&gt;
motion_sety(Y):
Y = castToNumber(Y)
setXY(target.x, Y)
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_ifonedgebounce&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;ifonedgebounce&quot;&gt;&lt;/span&gt; if on edge, bounce==

{{TODO|Explain how if on edge, bounce works.}}&lt;syntaxhighlight lang=py&gt;
motion_ifonedgebounce():
...
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_setrotationstyle&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;setrotationstyle&quot;&gt;&lt;/span&gt; set rotation style (STYLE)==

Sets the target's rotation style as determined by STYLE.

* If STYLE is one of the strings &lt;code&gt;don't rotate&lt;/code&gt;, &lt;code&gt;all around&lt;/code&gt;, or &lt;code&gt;left-right&lt;/code&gt;, sets the target's rotation style to STYLE.
* If the sprite is visible, requests to redraw the screen.

&lt;syntaxhighlight lang=py&gt;
motion_setrotationstyle(STYLE):
if STYLE is &quot;don't rotate&quot; or is &quot;all around&quot; or is &quot;left-right&quot;
    target.rotationStyle = STYLE
if target.visible
    redraw()
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_xposition&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;xposition&quot;&gt;&lt;/span&gt; x position==

Reports the target's X position.

* If the target's X position is less than 1e-9 away from the nearest integer:
** Reports the target's X position rounded to the nearest integer.
* Otherwise:
** Reports the target's X position.

&lt;syntaxhighlight lang=py&gt;
motion_xposition():
if abs(target.x - round(target.x)) &lt; 1e-9
    return round(target.x)
else
    return target.x
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_yposition&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;yposition&quot;&gt;&lt;/span&gt; y position==

Reports the target's Y position.

* If the target's Y position is less than 1e-9 away from the nearest integer:
** Reports the target's Y position rounded to the nearest integer.
* Otherwise:
** Reports the target's Y position.

&lt;syntaxhighlight lang=py&gt;
motion_yposition():
if abs(target.y - round(target.y)) &lt; 1e-9
    return round(target.y)
else
    return target.y
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_direction&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;direction&quot;&gt;&lt;/span&gt; direction==

Reports the target's direction.

* Reports the target's direction in degrees.

&lt;syntaxhighlight lang=py&gt;
motion_direction():
return target.direction
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_scroll_right&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;scroll_right&quot;&gt;&lt;/span&gt; scroll right ()==

Does nothing. This is a legacy block retained for backwards compatibility with Scratch 2.0 and is not visible in the block palette.

&lt;syntaxhighlight lang=py&gt;
motion_scroll_right():
(do nothing)
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_scroll_up&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;scroll_up&quot;&gt;&lt;/span&gt; scroll up ()==

Does nothing. This is a legacy block retained for backwards compatibility with Scratch 2.0 and is not visible in the block palette.

&lt;syntaxhighlight lang=py&gt;
motion_scroll_up():
(do nothing)
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_align_scene&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;align_scene&quot;&gt;&lt;/span&gt; align scene ()==

Does nothing. This is a legacy block retained for backwards compatibility with Scratch 2.0 and is not visible in the block palette.

&lt;syntaxhighlight lang=py&gt;
motion_align_scene():
(do nothing)
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_xscroll&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;xscroll&quot;&gt;&lt;/span&gt; x scroll==

Reports undefined. This is a legacy block retained for backwards compatibility with Scratch 2.0 and is not visible in the block palette.

&lt;syntaxhighlight lang=py&gt;
motion_xscroll():
return undefined
&lt;/syntaxhighlight&gt;

==&lt;span class=&quot;anchor&quot; id=&quot;motion_yscroll&quot;&gt;&lt;/span&gt;&lt;span class=&quot;anchor&quot; id=&quot;yscroll&quot;&gt;&lt;/span&gt; y scroll==

Reports undefined. This is a legacy block retained for backwards compatibility with Scratch 2.0 and is not visible in the block palette.

&lt;syntaxhighlight lang=py&gt;
motion_yscroll():
return undefined
&lt;/syntaxhighlight&gt;

==References==

{{BookCat}}</text>
      <sha1>bknn9qdyle24dms57ialfb6dde7qoxe</sha1>
    </revision>
  </page>
  <page>
    <title>User:Some helpful person</title>
    <ns>2</ns>
    <id>485068</id>
    <revision>
      <id>4656169</id>
      <timestamp>2026-08-03T07:00:39Z</timestamp>
      <contributor>
        <username>Some helpful person</username>
        <id>3510188</id>
      </contributor>
      <comment>yay</comment>
      <origin>4656169</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="431" sha1="c2fuvj1rawt2981pfd27p43iylck03z" xml:space="preserve">Books of Wiki

I’m interested in [[Scratch]]. I like wikis. I love books! I want to know how things work. I believe in free content. I see niches as essential addends in the sum of all human knowledge. Therefore, I have created ''[[Scratch Virtual Machine]]'', a book documenting the internal behaviors of Scratch. This is not only a niche, but a resource mysteriously absent for the Scratch programming language. Let's fix that!</text>
      <sha1>c2fuvj1rawt2981pfd27p43iylck03z</sha1>
    </revision>
  </page>
  <page>
    <title>General Literary Chinese from Scratch/Pronoun Table</title>
    <ns>0</ns>
    <id>485069</id>
    <revision>
      <id>4656180</id>
      <timestamp>2026-08-03T09:54:11Z</timestamp>
      <contributor>
        <username>Shira the Mogul</username>
        <id>3560559</id>
      </contributor>
      <comment>Created page with &quot;This is a quick reference for Literary Chinese pronouns.  ==Table== The following pronouns are grouped by their reconstructed Old Chinese groupings; they are always used together.  {| class=&quot;wikitable&quot; ! Person ! Period or group ! Subject/agent bias ! Object/patient bias ! Possessive bias |- ! rowspan=&quot;4&quot; | 1st | ŋ-series | 吾 | 我 | 吾 |- | j/l-series | 余 | 予 | 朕 |- | pre-Classical | 卬 | ? | 台 |- | Medieval | 儂 | — | — |- ! rowspan=&quot;2&quot; | 2nd | Classi...&quot;</comment>
      <origin>4656180</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="3919" sha1="kfwobi6g0z0roi0htjr84rmhgycdloj" xml:space="preserve">This is a quick reference for Literary Chinese pronouns.

==Table==
The following pronouns are grouped by their reconstructed Old Chinese groupings; they are always used together.

{| class=&quot;wikitable&quot;
! Person
! Period or group
! Subject/agent bias
! Object/patient bias
! Possessive bias
|-
! rowspan=&quot;4&quot; | 1st
| ŋ-series
| 吾
| 我
| 吾
|-
| j/l-series
| 余
| 予
| 朕
|-
| pre-Classical
| 卬
| ?
| 台
|-
| Medieval
| 儂
| —
| —
|-
! rowspan=&quot;2&quot; | 2nd
| Classical
| 汝
| 爾
| 爾
|-
| pre-Classical
| 若／如／而
| 若／如
| —
|-
! rowspan=&quot;3&quot; | 3rd
| Classical
| omitted
| 之
| 其
|-
| pre-Classical
| —
| —
| 厥
|-
| Medieval
| 伊、渠
| —
| —
|}

==Grammar==
Earlier Literary Chinese prefers different pronouns according to their grammatical position. For example, whereas we use &quot;I&quot; in English, in Literary Chinese, 吾 is especially common as a subject or possessor, whilst 我 is common as an object. For example, in &quot;Confucius said to Zi Lu,&quot; Confucius would be the Subject, and Zi Lu would be the Object. Therefore, to say &quot;I kicked the ball,&quot; you would need the Subject-biased pronouns, whilst to say &quot;The ball was kicked by me,&quot; you would need the Object-biased pronouns. Of the pronouns in the table, it is recommended to use 吾/我 or 余/予 and stick to them. The former is more common, though the latter still survives and can be seen even in Song and Ming dynasty work. 

Putting this into practice, using the common Classical pronouns:
* 吾適周 — I went to Zhou.
* 孔子見我 — Confucius saw me.
* 汝為誰 — Who are you?
* 汝何如 — How are you?
* 田中氏有爾貓 — Tanaka has your cat.
* 世宗作諺文，以之書韓語 — Sejong created Hangul and used it to write Korean.

We use &quot;bias&quot; here as these rules were not rigid: The rule was being forgotten come the late Classical era (around the end of the Qin dynasty), but can still be seen being followed even during the times of the Ming dynasty, such as in Jibong's Discourses (芝峰類說) from Korea. Therefore, it is still reasonable to follow. 

==Notes==
* 我, 予, and 爾 can be used in the subject position emphatically; this is often read as conveying strong emotion.
* 我 can be used as a general-purpose &quot;we&quot; in later Literary Chinese. Because Literary Chinese does not count number, it can be read as a singular or plural. 
* 子 and 君 are also sometimes used as honorific second-person expressions, while 妾 and 臣 may function as humble first-person expressions. Strictly speaking, however, these remain nouns rather than personal pronouns.
* Pre-Qin rulers usually used 余 as a &quot;royal we,&quot; which is particularly visible in Shang oracle bones. From the Qin dynasty onward, Emperors would use 朕.
** During the Shang dynasty, 朕 was used as a general possessive.
* 台 super-rarely appears in a subject/agent position. 
* Pre-Classical pronouns are very rarely seen and are typically reserved to quotations from the Book of Documents and Classic of Poetry. As these are very commonly quoted, though, it is worth remembering them.

==References==
* Aldridge, E. (2018). Inherent case in Archaic Chinese. Proceedings of the Linguistic Society of America, 3, 3. https://doi.org/10.3765/plsa.v3i1.4284
* Barnes, A. C., Starr, D., &amp; Ormerod, G. (2009). Du’s handbook of classical Chinese grammar: An introduction to classical Chinese grammar. Alcuin Academics.
* Pulleyblank, E. G. (2000). Outline of classical Chinese grammar (Repr). UBC Press.
* Takeshi, N. (1994). On the Differences of the Usages of First person Pronouns between the Chuci and other Texts in Classical Chinese. In 第一届国际先秦汉语语法研讨会论文集 (pp. 364–382). 岳麓书社出版. https://catalog.lib.kyushu-u.ac.jp/opac_download_md/18275/p364-382.pdf
* Yang, B. (2016). 文言语法 [Literary Chinese Grammar] (1st ed). 中华书局 [Zhonghua Book Company].

{{BookCat}}</text>
      <sha1>kfwobi6g0z0roi0htjr84rmhgycdloj</sha1>
    </revision>
  </page>
  <page>
    <title>User talk:Birdsjungle</title>
    <ns>3</ns>
    <id>485071</id>
    <revision>
      <id>4656184</id>
      <timestamp>2026-08-03T11:20:49Z</timestamp>
      <contributor>
        <username>MathXplore</username>
        <id>3097823</id>
      </contributor>
      <comment>Notifying author of speedy deletion nomination</comment>
      <origin>4656184</origin>
      <model>wikitext</model>
      <format>text/x-wiki</format>
      <text bytes="923" sha1="bcgvri6ahv5favk5n8tjr7d50sy3jio" xml:space="preserve">
== I have added a tag to a page you created ==
Hi! I'm MathXplore, and I recently reviewed your page, [[:User:Birdsjungle]]. 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. The reason I provided was: &lt;blockquote&gt;&lt;strong&gt;Out of scope&lt;/strong&gt;&lt;/blockquote&gt; If you believe that your page should not be deleted, please post a message on [[User talk:Birdsjungle|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:MathXplore|let me know]]. Thank you! &lt;!-- Substituted from User:JJPMaster/CurateThisPage/authorMsg --&gt; [[User:MathXplore|MathXplore]] ([[User talk:MathXplore|discuss]] • [[Special:Contributions/MathXplore|contribs]]) 11:20, 3 August 2026 (UTC)</text>
      <sha1>bcgvri6ahv5favk5n8tjr7d50sy3jio</sha1>
    </revision>
  </page>
</mediawiki>