Wonkpedia - User contributions [en]

Glocom

2022-11-16T23:14:15Z

Bmueller:

Glocom is a brand of North Korean radios.<ref>https://armscontrolwonk.libsyn.com/glocom-and-dprk-fronts</ref><ref>https://www.armscontrolwonk.com/archive/1205992/not-your-usual-game-of-whack-a-mole/</ref> They have been spotted in use by the Ethiopian military.<ref>https://mobile.twitter.com/GreatPoppo/status/1592851184691605505</ref>

== References ==
[[Category:DPRK]]

Glocom

2022-11-16T23:14:00Z

Bmueller: Create stub

Nov 15 Przewodow explosion

2022-11-16T21:34:01Z

Bmueller: Add analysis section

This case study is intended as a example of how there is great confusion in the direct aftermath of an event, and that the "direct aftermath" in the OSINT world doesn't start until things show up online

== Analysis ==
Initially, the explosion was interpreted as an attack on Poland by Russia, and initial steps were taken to meet and discuss a potential invocation of [[NATO Article 4]].<ref>https://twitter.com/shashj/status/1592808775991246848?s=20&t=7xDcm3G_1-RoqLXCQEnvkg</ref> While these steps were withdrawn, it's a good reminder that these kinds of interactions can easily spiral out of control.

== Timeline ==

=== November 15 ===
* At 15:40 local time (CET, GMT+1) an explosion was reported to national authorities in Przewodow<ref>https://twitter.com/phildstewart/status/1592654792144584705</ref>
* Seemingly at 17:54 local time, public radio publishes its first news about the explosion<ref>https://radio.lublin.pl/2022/11/wybuch-ciagnika-w-miejscowosci-przewodow-nie-zyja-dwie-osoby/</ref>, reporting two dead. Photos from the site of the explosions taken at 16:14 are also found at this site, possible already in the first update.
* At 18:28 local time, a journalist at the national commercial radio station Radio Zet tweeted<ref>https://twitter.com/MariuszGierszew/status/1592570215443070976</ref> the story that two missiles fell in Przewodow
* At 18:28 local time, Warsawa tabloid daily publishes a story<ref>https://www.fakt.pl/polityka/premier-zwoluje-komitet-rady-ministrow-do-spraw-bezpieczenstwa-narodowego/3x8peeg?utm_source=www.fakt.pl_viasg_fakt&utm_medium=referal&utm_campaign=leo_automatic&srcc=ucs&utm_v=2#slide-1</ref> that the national crisis group will convene, and vaguely references information that the meeting is related to the explosion in Przewodow. The story also states AP has reported that Russian missiles might have hit Poland.
* At 18:34 local time, public radio publishes<ref>https://radio.lublin.pl/2022/11/premier-zwolal-w-trybie-pilnym-komitet-rady-ministrow-do-spraw-bezpieczenstwa-narodowego-i-spraw-obronnych/</ref> a story that the national crisis group will convene, but no concrete cause is reported
* Seemingly at 18:42 local time, public radio publishes<ref>https://archive.ph/vesrJ</ref> that the governor went to Przewodow.
* At 18:54 local time, a Radio Zet station published online<ref>http://archive.today/2022.11.15-182649/https://wiadomosci.radiozet.pl/Polska/rakiety-spadly-na-polske-sa-ofiary-smiertelne</ref> a report from the site of the explosion. It was mostly second hand accounts, sourcing pictures from an online site covering actions by the fire fighers<ref>https://remiza.com.pl/wybuch-w-przewodowie/</ref> and a central quote from public radio <ref>https://radio.lublin.pl/2022/11/wybuch-ciagnika-w-miejscowosci-przewodow-nie-zyja-dwie-osoby/</ref>. It also referenced "unofficial sources" stating that the explosion was caused by two stray missiles. It did not state the time of the explosion.
* At 19:04 local time, (norwegian?) twitter account Faytuks News highlights<ref>https://twitter.com/Faytuks/status/1592580008505401344</ref> the Radio Zet story on his feed. At 19:13 local time the tweet is posted on the ACW slack
* At 19:43 local time, American journalist Jim La Porta references<ref>http://archive.today/2022.11.15-201848/https://twitter.com/JimLaPorta/status/1592589217623789568</ref> "a senior U.S. intelligence official" stating that there were two missiles and that they were Russian. It gets posted on the ACW slack at 19:44
* At 20:11 local time, American journalist Laura Kelly reports<ref>https://twitter.com/HelloLauraKelly/status/1592596264478470145</ref> that the Pentagon cannot corroborate that two Russian missiles struck Przewodow. Journalist Idrees Ali reports the same thing at the same time, which is posted on the ACW slack at 20:20

By this point there is a speculation bonanza on twitter and on the slack, but then US president Biden spoils things slightly around 3:00 local time saying it is unlikely the missiles were fired from Russia. An at 6:04 local time US government officials are saying it was a Ukrainian missile. This gets posted to the slack at 6:04 local time.

=== November 16 ===

===== Timeline for "Russian made" =====
* At 00:04 local time (on the 16th) American journalist Phil Stewart reports that Polish MFA has stated that "Russian produced rocket fell on [...] Przewodow" at the time the explosion happened. It was posted on the ACW slack at 00:10 local time (on the 16th)
* At 00:15 local time (on the 16th) public radio published<ref>https://radio.lublin.pl/2022/11/msz-na-terenie-przewodowa-spadl-spadl-pocisk-produkcji-rosyjskiej-ambasador-rosji-wezwany-do-msz/</ref> a report that the Polish MFA had issued a press release<ref>https://www.gov.pl/web/dyplomacja/komunikat-w-zwiazku-z-wezwaniem-ambasadora-federacji-rosyjskiej-do-msz</ref> where the MFA described the explosion in Przewodow as being a "Russian made missile", and stated they had called the Russian ambassador to give an explanation.
* At 2:31 local time (on the 16th) Reuters posted<ref>https://twitter.com/Reuters/status/1592691774908252161</ref> a message on twitter stating that "No concrete evidence on who fired missile, Poland's Duda says". It was posted on the ACW slack at 2:41 local time (on the 16th).

===== Timeline for Zelensky comments =====

* Around 19:12 local time, Zelensky stated "I have no doubt that it was not our missile or our missile strike. We have to participate in the investigation."<ref>https://twitter.com/ChristopherJM/status/1592928556635471873</ref> However, both Ukraine and the US agree that ultimate responsibility for the explosion falls on Russia.<ref>https://twitter.com/vmsalama/status/1592932638230446081?s=20&t=EJHZ88AppH7WrxF25u8TAw</ref>

== References ==
<references />
[[Category:Ukraine]]
[[Category:Russo-Ukrainian War]]
[[Category:Case Studies]]

Nov 15 Przewodow explosion

2022-11-16T21:28:29Z

Bmueller: /* Timeline */

This case study is intended as a example of how there is great confusion in the direct aftermath of an event, and that the "direct aftermath" in the OSINT world doesn't start until things show up online

== Timeline ==

=== November 15 ===
* At 15:40 local time (CET, GMT+1) an explosion was reported to national authorities in Przewodow<ref>https://twitter.com/phildstewart/status/1592654792144584705</ref>
* Seemingly at 17:54 local time, public radio publishes its first news about the explosion<ref>https://radio.lublin.pl/2022/11/wybuch-ciagnika-w-miejscowosci-przewodow-nie-zyja-dwie-osoby/</ref>, reporting two dead. Photos from the site of the explosions taken at 16:14 are also found at this site, possible already in the first update.
* At 18:28 local time, a journalist at the national commercial radio station Radio Zet tweeted<ref>https://twitter.com/MariuszGierszew/status/1592570215443070976</ref> the story that two missiles fell in Przewodow
* At 18:28 local time, Warsawa tabloid daily publishes a story<ref>https://www.fakt.pl/polityka/premier-zwoluje-komitet-rady-ministrow-do-spraw-bezpieczenstwa-narodowego/3x8peeg?utm_source=www.fakt.pl_viasg_fakt&utm_medium=referal&utm_campaign=leo_automatic&srcc=ucs&utm_v=2#slide-1</ref> that the national crisis group will convene, and vaguely references information that the meeting is related to the explosion in Przewodow. The story also states AP has reported that Russian missiles might have hit Poland.
* At 18:34 local time, public radio publishes<ref>https://radio.lublin.pl/2022/11/premier-zwolal-w-trybie-pilnym-komitet-rady-ministrow-do-spraw-bezpieczenstwa-narodowego-i-spraw-obronnych/</ref> a story that the national crisis group will convene, but no concrete cause is reported
* Seemingly at 18:42 local time, public radio publishes<ref>https://archive.ph/vesrJ</ref> that the governor went to Przewodow.
* At 18:54 local time, a Radio Zet station published online<ref>http://archive.today/2022.11.15-182649/https://wiadomosci.radiozet.pl/Polska/rakiety-spadly-na-polske-sa-ofiary-smiertelne</ref> a report from the site of the explosion. It was mostly second hand accounts, sourcing pictures from an online site covering actions by the fire fighers<ref>https://remiza.com.pl/wybuch-w-przewodowie/</ref> and a central quote from public radio <ref>https://radio.lublin.pl/2022/11/wybuch-ciagnika-w-miejscowosci-przewodow-nie-zyja-dwie-osoby/</ref>. It also referenced "unofficial sources" stating that the explosion was caused by two stray missiles. It did not state the time of the explosion.
* At 19:04 local time, (norwegian?) twitter account Faytuks News highlights<ref>https://twitter.com/Faytuks/status/1592580008505401344</ref> the Radio Zet story on his feed. At 19:13 local time the tweet is posted on the ACW slack
* At 19:43 local time, American journalist Jim La Porta references<ref>http://archive.today/2022.11.15-201848/https://twitter.com/JimLaPorta/status/1592589217623789568</ref> "a senior U.S. intelligence official" stating that there were two missiles and that they were Russian. It gets posted on the ACW slack at 19:44
* At 20:11 local time, American journalist Laura Kelly reports<ref>https://twitter.com/HelloLauraKelly/status/1592596264478470145</ref> that the Pentagon cannot corroborate that two Russian missiles struck Przewodow. Journalist Idrees Ali reports the same thing at the same time, which is posted on the ACW slack at 20:20

By this point there is a speculation bonanza on twitter and on the slack, but then US president Biden spoils things slightly around 3:00 local time saying it is unlikely the missiles were fired from Russia. An at 6:04 local time US government officials are saying it was a Ukrainian missile. This gets posted to the slack at 6:04 local time.

=== November 16 ===

===== Timeline for "Russian made" =====
* At 00:04 local time (on the 16th) American journalist Phil Stewart reports that Polish MFA has stated that "Russian produced rocket fell on [...] Przewodow" at the time the explosion happened. It was posted on the ACW slack at 00:10 local time (on the 16th)
* At 00:15 local time (on the 16th) public radio published<ref>https://radio.lublin.pl/2022/11/msz-na-terenie-przewodowa-spadl-spadl-pocisk-produkcji-rosyjskiej-ambasador-rosji-wezwany-do-msz/</ref> a report that the Polish MFA had issued a press release<ref>https://www.gov.pl/web/dyplomacja/komunikat-w-zwiazku-z-wezwaniem-ambasadora-federacji-rosyjskiej-do-msz</ref> where the MFA described the explosion in Przewodow as being a "Russian made missile", and stated they had called the Russian ambassador to give an explanation.
* At 2:31 local time (on the 16th) Reuters posted<ref>https://twitter.com/Reuters/status/1592691774908252161</ref> a message on twitter stating that "No concrete evidence on who fired missile, Poland's Duda says". It was posted on the ACW slack at 2:41 local time (on the 16th).

===== Timeline for Zelensky comments =====

* Around 19:12 local time, Zelensky stated "I have no doubt that it was not our missile or our missile strike. We have to participate in the investigation."<ref>https://twitter.com/ChristopherJM/status/1592928556635471873</ref> However, both Ukraine and the US agree that ultimate responsibility for the explosion falls on Russia.<ref>https://twitter.com/vmsalama/status/1592932638230446081?s=20&t=EJHZ88AppH7WrxF25u8TAw</ref>

== References ==
<references />
[[Category:Ukraine]]
[[Category:Russo-Ukrainian War]]
[[Category:Case Studies]]

Category:Case Studies

2022-11-16T21:22:11Z

Bmueller: Created blank page

Nov 15 Przewodow explosion

2022-11-16T21:22:04Z

Bmueller:

This case study is intended as a example of how there is great confusion in the direct aftermath of an event, and that the "direct aftermath" in the OSINT world doesn't start until things show up online

== Timeline ==
* At 15:40 local time (CET, GMT+1) an explosion was reported to national authorities in Przewodow<ref>https://twitter.com/phildstewart/status/1592654792144584705</ref>
* Seemingly at 17:54 local time, public radio publishes its first news about the explosion<ref>https://radio.lublin.pl/2022/11/wybuch-ciagnika-w-miejscowosci-przewodow-nie-zyja-dwie-osoby/</ref>, reporting two dead. Photos from the site of the explosions taken at 16:14 are also found at this site, possible already in the first update.
* At 18:28 local time, a journalist at the national commercial radio station Radio Zet tweeted<ref>https://twitter.com/MariuszGierszew/status/1592570215443070976</ref> the story that two missiles fell in Przewodow
* At 18:28 local time, Warsawa tabloid daily publishes a story<ref>https://www.fakt.pl/polityka/premier-zwoluje-komitet-rady-ministrow-do-spraw-bezpieczenstwa-narodowego/3x8peeg?utm_source=www.fakt.pl_viasg_fakt&utm_medium=referal&utm_campaign=leo_automatic&srcc=ucs&utm_v=2#slide-1</ref> that the national crisis group will convene, and vaguely references information that the meeting is related to the explosion in Przewodow. The story also states AP has reported that Russian missiles might have hit Poland.
* At 18:34 local time, public radio publishes<ref>https://radio.lublin.pl/2022/11/premier-zwolal-w-trybie-pilnym-komitet-rady-ministrow-do-spraw-bezpieczenstwa-narodowego-i-spraw-obronnych/</ref> a story that the national crisis group will convene, but no concrete cause is reported
* Seemingly at 18:42 local time, public radio publishes<ref>https://archive.ph/vesrJ</ref> that the governor went to Przewodow.
* At 18:54 local time, a Radio Zet station published online<ref>http://archive.today/2022.11.15-182649/https://wiadomosci.radiozet.pl/Polska/rakiety-spadly-na-polske-sa-ofiary-smiertelne</ref> a report from the site of the explosion. It was mostly second hand accounts, sourcing pictures from an online site covering actions by the fire fighers<ref>https://remiza.com.pl/wybuch-w-przewodowie/</ref> and a central quote from public radio <ref>https://radio.lublin.pl/2022/11/wybuch-ciagnika-w-miejscowosci-przewodow-nie-zyja-dwie-osoby/</ref>. It also referenced "unofficial sources" stating that the explosion was caused by two stray missiles. It did not state the time of the explosion.
* At 19:04 local time, (norwegian?) twitter account Faytuks News highlights<ref>https://twitter.com/Faytuks/status/1592580008505401344</ref> the Radio Zet story on his feed. At 19:13 local time the tweet is posted on the ACW slack
* At 19:43 local time, American journalist Jim La Porta references<ref>http://archive.today/2022.11.15-201848/https://twitter.com/JimLaPorta/status/1592589217623789568</ref> "a senior U.S. intelligence official" stating that there were two missiles and that they were Russian. It gets posted on the ACW slack at 19:44
* At 20:11 local time, American journalist Laura Kelly reports<ref>https://twitter.com/HelloLauraKelly/status/1592596264478470145</ref> that the Pentagon cannot corroborate that two Russian missiles struck Przewodow. Journalist Idrees Ali reports the same thing at the same time, which is posted on the ACW slack at 20:20

By this point there is a speculation bonanza on twitter and on the slack, but then US president Biden spoils things slightly around 3:00 local time saying it is unlikely the missiles were fired from Russia. An at 6:04 local time US government officials are saying it was a Ukrainian missile. This gets posted to the slack at 6:04 local time.

===== Timeline for "Russian made" =====
* At 00:04 local time (on the 16th) american journalist Phil Stewart reports that Polish MFA has stated that "Russian produced rocket fell on [...] Przewodow" at the time the explosion happened. It was posted on the ACW slack at 00:10 local time (on the 16th)
* At 00:15 local time (on the 16th) public radio published<ref>https://radio.lublin.pl/2022/11/msz-na-terenie-przewodowa-spadl-spadl-pocisk-produkcji-rosyjskiej-ambasador-rosji-wezwany-do-msz/</ref> a report that the Polish MFA had issued a press release<ref>https://www.gov.pl/web/dyplomacja/komunikat-w-zwiazku-z-wezwaniem-ambasadora-federacji-rosyjskiej-do-msz</ref> where the MFA described the explosion in Przewodow as being a "Russian made missile", and stated they had called the Russian ambassador to give an explanation.
* At 2:31 local time (on the 16th) Reuters posted<ref>https://twitter.com/Reuters/status/1592691774908252161</ref> a message on twitter stating that "No concrete evidence on who fired missile, Poland's Duda says". It was posted on the ACW slack at 2:41 local time (on the 16th).

== References ==
<references />
[[Category:Ukraine]]
[[Category:Russo-Ukrainian War]]
[[Category:Case Studies]]

Category:Russo-Ukrainian War

2022-11-16T21:21:41Z

Bmueller: Created blank page

Category:Ukraine

2022-11-16T21:21:30Z

Bmueller: Created blank page

Nov 15 Przewodow explosion

2022-11-16T21:21:22Z

Bmueller: Add tags

This case study is intended as a example of how there is great confusion in the direct aftermath of an event, and that the "direct aftermath" in the OSINT world doesn't start until things show up online

== Timeline ==
* At 15:40 local time (CET, GMT+1) an explosion was reported to national authorities in Przewodow<ref>https://twitter.com/phildstewart/status/1592654792144584705</ref>
* Seemingly at 17:54 local time, public radio publishes its first news about the explosion<ref>https://radio.lublin.pl/2022/11/wybuch-ciagnika-w-miejscowosci-przewodow-nie-zyja-dwie-osoby/</ref>, reporting two dead. Photos from the site of the explosions taken at 16:14 are also found at this site, possible already in the first update.
* At 18:28 local time, a journalist at the national commercial radio station Radio Zet tweeted<ref>https://twitter.com/MariuszGierszew/status/1592570215443070976</ref> the story that two missiles fell in Przewodow
* At 18:28 local time, Warsawa tabloid daily publishes a story<ref>https://www.fakt.pl/polityka/premier-zwoluje-komitet-rady-ministrow-do-spraw-bezpieczenstwa-narodowego/3x8peeg?utm_source=www.fakt.pl_viasg_fakt&utm_medium=referal&utm_campaign=leo_automatic&srcc=ucs&utm_v=2#slide-1</ref> that the national crisis group will convene, and vaguely references information that the meeting is related to the explosion in Przewodow. The story also states AP has reported that Russian missiles might have hit Poland.
* At 18:34 local time, public radio publishes<ref>https://radio.lublin.pl/2022/11/premier-zwolal-w-trybie-pilnym-komitet-rady-ministrow-do-spraw-bezpieczenstwa-narodowego-i-spraw-obronnych/</ref> a story that the national crisis group will convene, but no concrete cause is reported
* Seemingly at 18:42 local time, public radio publishes<ref>https://archive.ph/vesrJ</ref> that the governor went to Przewodow.
* At 18:54 local time, a Radio Zet station published online<ref>http://archive.today/2022.11.15-182649/https://wiadomosci.radiozet.pl/Polska/rakiety-spadly-na-polske-sa-ofiary-smiertelne</ref> a report from the site of the explosion. It was mostly second hand accounts, sourcing pictures from an online site covering actions by the fire fighers<ref>https://remiza.com.pl/wybuch-w-przewodowie/</ref> and a central quote from public radio <ref>https://radio.lublin.pl/2022/11/wybuch-ciagnika-w-miejscowosci-przewodow-nie-zyja-dwie-osoby/</ref>. It also referenced "unofficial sources" stating that the explosion was caused by two stray missiles. It did not state the time of the explosion.
* At 19:04 local time, (norwegian?) twitter account Faytuks News highlights<ref>https://twitter.com/Faytuks/status/1592580008505401344</ref> the Radio Zet story on his feed. At 19:13 local time the tweet is posted on the ACW slack
* At 19:43 local time, American journalist Jim La Porta references<ref>http://archive.today/2022.11.15-201848/https://twitter.com/JimLaPorta/status/1592589217623789568</ref> "a senior U.S. intelligence official" stating that there were two missiles and that they were Russian. It gets posted on the ACW slack at 19:44
* At 20:11 local time, American journalist Laura Kelly reports<ref>https://twitter.com/HelloLauraKelly/status/1592596264478470145</ref> that the Pentagon cannot corroborate that two Russian missiles struck Przewodow. Journalist Idrees Ali reports the same thing at the same time, which is posted on the ACW slack at 20:20

By this point there is a speculation bonanza on twitter and on the slack, but then US president Biden spoils things slightly around 3:00 local time saying it is unlikely the missiles were fired from Russia. An at 6:04 local time US government officials are saying it was a Ukrainian missile. This gets posted to the slack at 6:04 local time.

===== Timeline for "Russian made" =====
* At 00:04 local time (on the 16th) american journalist Phil Stewart reports that Polish MFA has stated that "Russian produced rocket fell on [...] Przewodow" at the time the explosion happened. It was posted on the ACW slack at 00:10 local time (on the 16th)
* At 00:15 local time (on the 16th) public radio published<ref>https://radio.lublin.pl/2022/11/msz-na-terenie-przewodowa-spadl-spadl-pocisk-produkcji-rosyjskiej-ambasador-rosji-wezwany-do-msz/</ref> a report that the Polish MFA had issued a press release<ref>https://www.gov.pl/web/dyplomacja/komunikat-w-zwiazku-z-wezwaniem-ambasadora-federacji-rosyjskiej-do-msz</ref> where the MFA described the explosion in Przewodow as being a "Russian made missile", and stated they had called the Russian ambassador to give an explanation.
* At 2:31 local time (on the 16th) Reuters posted<ref>https://twitter.com/Reuters/status/1592691774908252161</ref> a message on twitter stating that "No concrete evidence on who fired missile, Poland's Duda says". It was posted on the ACW slack at 2:41 local time (on the 16th).

== References ==
<references />
[[Category:Ukraine]]
[[Category:Russo-Ukrainian War]]
[[Category:Case Study]]

Punggye-Ri

2022-10-24T20:45:38Z

Bmueller: Undo revision 2426 by Bmueller (talk)

Punggye-Ri is the primary site where North Korea tests nuclear weapons in underground tunnels.

== Location ==
{{#display_map:center=41.278902,129.085244 | label=Punggye-Ri|width=25%}}
{{#coordinates: 41.278902,129.085244|format=dd|directional=yes}}
[[Category:North Korea]]
[[Category:DPRK]]
[[Category:Nuclear Site]]
[[Category:Nuclear]]
[[Category:Nuclear Test Site]]

Parchin

2022-10-10T23:57:53Z

Bmueller:

Parchin is a nuclear facility? todo

<ref>https://twitter.com/TheGoodISIS/status/1083756896689901568</ref>

{{#display_map:center=35.5185364,51.7544115 | label=Parchin|width=25%}}
{{#display_map:image layers=Boroujerdi_January_2019_Figure_10_georeferenced.png | label=Parchin|width=25%}}
{{#coordinates: 35.5185364,51.7544115|format=dd|directional=yes}}

== References ==
<references />
[[Category:Iran]]

GeoJson:Parchin

2022-10-10T23:50:40Z

Bmueller: Created GeoJSON page

{
"type": "FeatureCollection",
"features": []
}

File:Boroujerdi January 2019 Figure 10 georeferenced.png

2022-10-10T23:40:16Z

Bmueller:

Parchin

2022-10-10T23:39:11Z

Bmueller:

Parchin is a nuclear facility? todo

<ref>https://twitter.com/TheGoodISIS/status/1083756896689901568</ref>

{{#display_map:center=35.5185364,51.7544115 | label=Parchin|width=25%}}
{{#coordinates: 35.5185364,51.7544115|format=dd|directional=yes}}

== References ==
<references />
[[Category:Iran]]

Punggye-Ri

2022-10-10T23:36:12Z

Bmueller:

Punggye-Ri is the primary site where North Korea tests nuclear weapons in underground tunnels.

== Location ==
{{#display_map:center=35.5185364,51.7544115 | label=Punggye-Ri|width=25%}}
{{#coordinates: 35.5185364,51.7544115|format=dd|directional=yes}}
[[Category:North Korea]]
[[Category:DPRK]]
[[Category:Nuclear Site]]
[[Category:Nuclear]]
[[Category:Nuclear Test Site]]

S-300 Footprint

2022-10-06T17:12:10Z

Bmueller: Create Stub

This page contains satellite footprints of the Russian S-300 batteries. Specifically, ''Russian'' S-300 batteries; S-300 deployments sold to other countries should look ''similar'' but might warrant their own page.

== Optical ==
todo

== SAR ==
todo
[[Category:S-300]]
[[Category:Footprint]]
[[Category:Russia]]

Alleged Ukraine Targeting List (2022)

2022-10-06T16:02:54Z

Bmueller:

In 2022, an alleged list of 100 Ukrainian targets in the Russo-Ukrainian war was claimed to have been leaked.<ref>https://twitter.com/shashj/status/1573250017061703680</ref> Targets included [[S-300]] and [[S-400]] sites, as well as other Russian military equipment. This article documents the OSINT work done by wonks to investigate the validity of the list through various methods.

== Background ==
Images linked in tweet:
NOTE: Alleged images may have classification markings. View at your own discretion: <nowiki>https://wonkpedia.org/mediawiki/index.php/Alleged_Ukraine_Targeting_List_(2022)/Images</nowiki>

If you prefer the plaintext: [[Alleged Ukraine Targeting List (2022)/Text]]

== Maps==
Link to any KMLs, shapefiles, etc. here- I'll go through and create proper pages for them with leaflet map integration - Madwonk

*list

==FIRMS ==
Upload and put some images of the FIRMS observations here

==Imagery==

===Optical===
todo

=== SAR===
todo

==Observations/Conclusions==
Todo: a basic summary here. Maybe upload/link/share the PDF documenting the work here? (Get permission first)

==References==
<references />

Alleged Ukraine Targeting List (2022)

2022-10-06T16:02:35Z

Bmueller: /* Background */

In 2022, an alleged list of 100 Ukrainian targets in the Russo-Ukrainian war was claimed to have been leaked.<ref>https://twitter.com/shashj/status/1573250017061703680</ref> Targets included [[S-300]] and [[S-400]] sites, as well as other Russian military equipment. This article documents the OSINT work done by wonks to investigate the validity of the list through various methods.

== Background ==
Images linked in tweet:
NOTE: Alleged images may have classification markings. View at your own discretion: <nowiki>https://wonkpedia.org/mediawiki/index.php/Alleged_Ukraine_Targeting_List_(2022)/Images</nowiki>

If you prefer the plaintext: [[Alleged Ukraine Targeting List (2022)/Text]]

== Maps==
Link to any KMLs, shapefiles, etc. here- I'll go through and create proper pages for them with leaflet map integration - Madwonk

*list

==FIRMS ==
Upload and put some images of the FIRMS observations here

==Imagery==

===Optical===
todo

=== SAR===
todo

==Observations/Conclusions==
Todo: a basic summary here. Maybe upload/link/share the PDF documenting the work here? (Get permission first)

==References==
<references />

Alleged Ukraine Targeting List (2022)/Images

2022-10-06T15:58:32Z

Bmueller: Created page with "Page 1alt=center"

Alleged Ukraine Targeting List (2022)

2022-10-06T14:51:48Z

Bmueller: Add some more basics

In 2022, an alleged list of 100 Ukrainian targets in the Russo-Ukrainian war was claimed to have been leaked.<ref>https://twitter.com/shashj/status/1573250017061703680</ref> Targets included [[S-300]] and [[S-400]] sites, as well as other Russian military equipment. This article documents the OSINT work done by wonks to investigate the validity of the list through various methods.

== Background ==
The 3 images of supposed sites are shown below.[[File:Samsites pg1.jpeg|left|thumb|Page 1]][[File:Samsites pg3.jpeg|thumb|Page 3|alt=]][[File:Samsites pg2.jpeg|thumb|Page 2|alt=|center]]

If you prefer the plaintext: [[Alleged Ukraine Targeting List (2022)/Text]]

== Maps ==
Link to any KMLs, shapefiles, etc. here- I'll go through and create proper pages for them with leaflet map integration - Madwonk

* list

== FIRMS ==
Upload and put some images of the FIRMS observations here

== Imagery ==

=== Optical ===
todo

=== SAR ===
todo

== Observations/Conclusions ==
Todo: a basic summary here. Maybe upload/link/share the PDF documenting the work here? (Get permission first)

== References ==
<references />

Alleged Ukraine Targeting List (2022)

2022-10-06T14:43:38Z

Bmueller: Move things around

Alleged Ukraine Targeting List (2022)/Text

2022-10-06T14:38:49Z

Bmueller: Create basic stub

{| class="wikitable"
|Latitude
|Longitude
|ID
|Date
|Liberated?
|Comments
|Additional maps
|-
|46.9611
|33.4453
|SA17
|2022-07-08 17:23:00Z
|No
|Empty fields 3km SSW of Kostyrka village, 73km ENE of Kherson, W bank of Dnipro
|
|-
|46.6844
|32.7167
|SA8
|2022-07-08 17:24:25Z
|No
|Residential area, E outskirts of Kherson, near E97/M17 highway
|1km north of Antonovskiy bridge
|-
|48.8997
|38.5794
|SA8
|2022-07-08 17:36:58Z
|No
|S of Severodonetsk
|
|-
|47.5172
|37.2522
|SA11B
|2022-07-08 17:39:30Z
|
|
|
|-
|48.5258
|38.3836
|SA22B
|2022-07-08 17:58:00Z
|
|
|
|-
|48.7889
|38.4356
|SA17
|2022-07-08 18:16:19Z
|
|
|Rescue unit of the Special Forces Rescue Squad of the State Emergency Service of Ukraine in the Luhansk region 2km north
|-
|48.5539
|38.8858
|SA15C
|2022-07-08 18:30:00Z
|
|
|
|-
|49.7025
|37.5292
|SA8
|2022-07-08 18:37:58Z
|Yes
|Empty fields 5km W of Kupyansk, between Sobolivka & Nechvolodivka
|
|-
|45.1453
|35.5025
|SA21B BIG BIRD E
|2022-07-08 19:37:00Z
|
|Known site, command post of the 50th anti-aircraft missile regiment
|
|-
|47.4919
|36.3819
|SA15C
|2022-07-08 19:38:51Z
|
|
|
|-
|48.6103
|39.2383
|SA12B
|2022-07-08 19:39:00Z
|
|
|Former Ukrainan P12 Spoon Rest & P14 Tall King radar site (А-0194)
|-
|46.6842
|33.0931
|SA23
|2022-07-08 20:09:0SZ
|No
|Empty grassland near north edge of Oleshky natural park, 38km E of Kherson
|
|-
|47.3147
|33.7267
|SA15E
|2022-07-08 20:17:00Z
|
|
|
|-
|46.6881
|32.5011
|SA22B
|2022-07-08 20:47:38Z
|
|
|Chornobaivka Helibase
|-
|48.9086
|38.3781
|SA8
|2022-07-08 21:07:32Z
|
|
|
|-
|47.4889
|36.4092
|SA15C
|2022-07-08 21:08:52Z
|
|
|
|-
|48.0181
|38.1994
|SA15C
|2022-07-08 21:11:00Z
|
|
|
|-
|47.1872
|35.7053
|SA15C
|2022-07-08 21:49:02Z
|
|
|
|-
|48.0644
|37.8431
|SA8
|2022-07-08 21:49:00Z
|No
|Edge of residential area 6km NNE of Donetsk, near mining site
|
|-
|48.5214
|39.1933
|SA22B
|2022-07-08 21:55:12Z
|
|
|Close to historical AD site just north
|-
|48.0347
|38.2656
|SA11B
|2022-07-08 21:55:18Z
|
|
|
|-
|49.2119
|37.3597
|SA15C
|2022-07-08 22:01:19Z
|
|
|
|-
|46.7906
|35.4217
|SA27B
|2022-07-08 22:04:00Z
|No
|Empty fields 8km SSE of Melitopol, S edge of Kostyantynivka settlement
|
|-
|47.9000
|37.8053
|SA8
|2022-07-08 22:08:00Z
|No
|Empty fields 13km S of Donetsk
|Next to historical AD site
|-
|49.7019
|37.5306
|SA8
|2022-07-08 22:37:29Z
|Yes
|Empty fields 5km W of Kupyansk, between Sobolivka & Nechvolodivka, next to line 9
|
|-
|46.7814
|33.3658
|SA22B
|2022-07-08 22:53:00Z
|
|
|Kakhovka dam
|-
|48.3350
|38.1472
|SA8
|2022-07-08 22:53:00Z
|
|
|
|-
|47.7081
|37.5125
|SA15C
|2022-07-08 22:59:00Z
|
|
|
|-
|49.2161
|37.3714
|SA27B
|2022-07-08 23:00:00Z
|
|
|
|-
|47.5078
|37.2361
|SA11B
|2022-07-08 23:07:40Z
|
|
|
|-
|48.0411
|37.8122
|SA8
|2022-07-08 23:08:46Z
|No
|Residential area 2km N or Donetsk, side of tailings mound
|
|-
|49.3303
|37.5872
|SA11A
|2022-07-08 23:10:18Z
|No
|SW edge of Pidlyman village, near E bank of Oskil river
|
|-
|45.3453
|32.5247
|SA20D BIG BIRD D
|2022-07-08 23:52:32Z
|
|Known site, 3rd Radio-Technical Regiment command post- Olenivka, 55Zh6ME Nebo. Possible Bastion-P site nearby
|
|-
|48.0075
|37.7089
|SA8
|2022-07-08 23:53:19Z
|No
|Edge of residential/industrial area 7km W of Donetsk, alongside local road
|
|-
|48.6300
|38.5231
|1L122-1E
|2022-07-09 00:00:00Z
|
|
|Unlikley as its in the middle of housing area
|-
|48.4628
|39.1222
|SA11B
|2022-07-09 00:01:14Z
|No
|Empty fields near river gorge 18km SW of Luhansk
|Historical SA-2 AD site 3km NW
|-
|48.4631
|39.1228
|SA11B
|2022-07-09 00:01:14Z
|No
|Empty fields near river gorge 18km SW of Luhansk, close to line 37
|
|-
|48.4631
|39.1228
|SA11B
|2022-07-09 00:01:14Z
|No
|Empty fields near river gorge 18km SW of Luhansk, same as line 38
|
|-
|48.4744
|39.3514
|SA12B
|2022-07-09 00:01:26Z
|
|Scrubland area on S edge of large forest 11km S of Luhansk
|
|-
|49.3594
|37.5861
|SA11A
|2022-07-09 00:02:27Z
|No
|Clearing in forest 3km SW of Borova, near E bank of Oskil river
|
|-
|48.4583
|39.3575
|SA12B
|2022-07-09 00:04:11Z
|
|
|
|-
|45.4319
|36.5731
|SA22B
|2022-07-09 00:04:48Z
|
|
|
|-
|49.4269
|37.6781
|SA11A
|2022-07-09 00:07:28Z
|
|
|
|-
|49.1339
|37.2803
|SA11B
|2022-07-09 00:54:00Z
|Yes
|
|
|-
|46.3364
|33.5053
|SA22B
|2022-07-09 01:02:34Z
|
|HQ at 46°20'53.57"N, 33°32'27.79"E?
|
|-
|46.3108
|32.5225
|SA22B
|2022-07-09 01:08:08Z
|No
|Empty fields 37km south of Kherson
|
|-
|46.6839
|33.0931
|SA23
|2022-07-09 01:08:17Z
|No
|Same as line 13
|
|-
|48.0194
|38.1989
|SA27B
|2022-07-09 01:28:00Z
|
|
|
|-
|48.4167
|38.9481
|SA27B
|2022-07-09 01:29:00Z
|
|
|
|-
|49.1989
|37.6822
|SA11A
|2022-07-09 01:30:21Z
|
|
|
|-
|45.4194
|32.5403
|SA20D CHEESE BOARD
|2022-07-09 01:32:00Z
|
|
|Historical S-300 site
|-
|46.7625
|35.2453
|SA27B
|2022-07-09 01:34:43Z
|
|
|
|-
|48.6217
|38.4553
|SA15C
|2022-07-09 01:44:12Z
|
|
|
|-
|46.6450
|32.4964
|SA17
|2022-07-09 01:51:00Z
|
|
|Historical SA-3 site just north
|-
|46.7631
|35.2392
|SA27B
|2022-07-09 01:51:08Z
|
|
|
|-
|48.6117
|39.2450
|SA12B
|2022-07-09 01:55:55Z
|
|
|Historical AD site
|-
|48.9778
|38.7533
|SA27B
|2022-07-09 01:56:40Z
|No
|NE of Severodonetsk
|
|-
|49.0975
|37.3556
|SA17
|2022-07-09 01:59:18Z
|Yes
|Empty fields on edge of woods, 14km SE of Izyum
|
|-
|48.5811
|39.2619
|SA22B
|2022-07-09 02:08:28Z
|No
|24km E of Luhansk, 4km W of RU border
|Former UA millitary base
|-
|45.6872
|34.4139
|SA21B CHEESE BOARD
|2022-07-09 02:37:00Z
|
|12th Anti-Aircraft Missile Regiment - Dzhankoi 500m west
|
|-
|47.0556
|32.9236
|SA15E
|2022-07-09 02:51:14Z
|
|
|
|-
|45.8475
|33.4778
|SA20D CHEESE BOARD
|2022-07-09 02:51:41Z
|
|
|
|-
|49.3594
|37.5869
|SA17 SNOW DRIFT MOD
|2022-07-09 02:51:46Z
|No
|Clearing in forest 3km SW of Borova, near E bank of Oskil river, close to line 34
|
|-
|45.6931
|34.4072
|SA22B
|2022-07-09 02:53:42Z
|
|
|
|-
|48.9019
|38.3664
|SA8
|2022-07-09 03:03:16Z
|
|
|
|-
|49.4689
|37.8794
|SA23
|2022-07-09 03:12:54Z
|
|
|
|-
|46.6839
|32.4950
|SA15E
|2022-07-09 03:16:25Z
|
|Kherson Heliport
|
|-
|48.0047
|38.2250
|SA27B
|2022-07-09 03:20:28Z
|
|
|
|-
|48.4908
|38.9461
|SA27B
|2022-07-09 03:20:34Z
|
|
|
|-
|46.6469
|32.4964
|SA17
|2022-07-09 03:22:00Z
|
|
|
|-
|47.1750
|35.6892
|SA27B
|2022-07-09 03:24:00Z
|
|
|
|-
|49.1231
|37.2211
|SA15C
|2022-07-09 03:24:00Z
|Yes
|
|
|-
|49.5464
|36.9144
|1L261E
|2022-07-09 03:26:15Z
|Yes
|Empty fields 10km N of Balakliya
|
|-
|49.4700
|36.8831
|SA15B
|2022-07-09 03:35:00Z
|Yes
|Undeveloped area N of Balakliya
|Next to arsenal
|-
|50.2750
|36.3686
|SA15C
|2022-07-09 03:38:00Z
|Yes
|Country road 1km W of Kharkiv dam lake, 1.5km S of RU border
|
|-
|46.9592
|33.4456
|SA17
|2022-07-09 03:38:39Z
|No
|Empty fields 3km SSW of Kostyrka village, 73km ENE of Kherson, W bank of Dnipro, close to line 1
|
|-
|48.5408
|38.7231
|SA27B
|2022-07-09 03:39:00Z
|
|
|
|-
|48.4447
|38.9661
|SA27B
|2022-07-09 03:39:00Z
|
|
|Next to historical AD site
|-
|49.4278
|37.6842
|SA15C
|2022-07-09 03:39:23Z
|?
|E bank of Oskil river
|
|-
|48.6614
|38.3231
|1L122-1E
|2022-07-09 03:40:00Z
|No
|Empty fields NW of Popasana
|
|-
|48.0206
|38.1933
|SA23
|2022-07-09 03:40:41Z
|No
|Major highway east of Donetsk city
|
|-
|47.0322
|32.7153
|SA15E
|2022-07-09 03:43:00Z
|?
|Empty fields west of Inhulets river, Kherson
|
|-
|49.2597
|37.6225
|SA15C
|2022-07-09 03:44:00Z
|No
|Empty fields on SE edge of Pisky-Radkivski village, near E bank of Oskil river
|
|-
|46.3219
|33.3089
|SA23
|2022-07-09 03:53:00Z
|No
|Empty fields 7km N of Kalanchak
|
|-
|48.4578
|38.9639
|SA27B
|2022-07-09 03:59:54Z
|No
|Empty fields 28km WSW of Luhansk
|
|-
|48.6975
|39.4492
|SA22B
|2022-07-09 04:02:00Z
|No
|Clusters of forests, 18km NE of Luhansk
|
|-
|45.3556
|36.5972
|SA22B
|2022-07-09 04:05:00Z
|No
|Small military staging area, no visible SAMs, Kerch strait
|
|-
|45.3883
|36.6011
|SA21B CHEESE BOARD
|2022-07-09 04:12:00Z
|No
|Raised highlands, Kerch strait
|
|-
|49.1339
|37.2636
|SA11B
|2022-07-09 04:12:00Z
|Yes
|Empty fields south of Izyum
|
|-
|46.1114
|32.9056
|SA22B
|2022-07-09 04:24:00Z
|No
|Skadovsk, centre of the city
|
|-
|49.4028
|37.6308
|SA17
|2022-07-09 04:25:00Z
|No
|Empty fields along train line 3km north of Borova, 35km south of Kupyansk, near E bank of Oskil river
|
|-
|49.1236
|37.2842
|1L261E
|2022-07-09 04:25:00Z
|Yes
|Empty fields south of Izyum
|
|-
|49.7000
|37.5419
|SA27B
|2022-07-09 04:25:00Z
|Yes
|Old, small runway near Kupyansk
|
|-
|48.7892
|38.4344
|SA17
|2022-07-09 04:25:00Z
|No
|Empty fields south of Lysychansk
|
|-
|50.2453
|36.4325
|ZOOPARK 1
|2022-07-09 04:25:ooZ
|Yes
|Empty fields NE of Kharkiv
|
|-
|46.8461
|35.2806
|SA15E
|2022-07-09 04:26:00Z
|No
|Empty field 6km W of Melitopol, 4km south of military airfield in Melitopol
|
|-
|48.4206
|39.3592
|SA15C
|2022-07-09 04:29:00Z
|No
|Airfield south of Luhansk. Seems abandoned in imagery this year
|
|-
|46.2089
|33.6678
|SA22A
|2022-07-09 04:30:00Z
|No
|Large chemical plant, possibly protected by SAMs
|
|-
|45.2192
|33.2600
|SA21A CHEESE BOARD
|2022-07-09 04:34:00Z
|No
|S300/400 site, 8 launchers, exact location
|
|-
|44.5217
|33.4847
|SA21A BIG BIRD
|2022-07-09 04:56:00Z
|No
|Large vehicle compound, no visible launchers
|Former 174th SAM brigade with SA5
|}

Alleged Ukraine Targeting List (2022)

2022-10-06T14:30:56Z

Bmueller: /* Background */

Alleged Ukraine Targeting List (2022)

2022-10-06T14:29:35Z

Bmueller: /* Background */

Alleged Ukraine Targeting List (2022)

2022-10-06T14:28:35Z

Bmueller: /* Background */

Alleged Ukraine Targeting List (2022)

2022-10-06T14:27:40Z

Bmueller: /* Background */

Alleged Ukraine Targeting List (2022)

2022-10-06T14:25:27Z

Bmueller: Create stub

File:Samsites pg3.jpeg

2022-10-06T14:24:21Z

Bmueller: Page 3 of the supposed Ukraine targeting sites

== Summary ==
Page 3 of the supposed Ukraine targeting sites
== Licensing ==
{{Remove this line and insert a license instead|year=2022|month=10|day=06}}

Template:Remove this line and insert a license instead

2022-10-06T14:24:08Z

Bmueller: /* Copyright unknown */

=== Copyright unknown ===
This file is from a country/region whose copyright is not applicable in your region (e.g. Iran or North Korea), or whose copyright is unknown but believed to fall under fair use. While you're allowed to upload such files, intentionally uploading copyrighted materials and claiming to be ignorant when it gets claimed would be frowned upon. At the very least, doing some due diligence to make sure you aren't uploading copyrighted material would be greatly appreciated by the mod team.

If you are a copyright owner or represent a copyright owner, and you believe that Wonkpedia is infringing your copyright, the quickest solution is to contact the admins directly through the official twitter, discord, github, wiki talk pages, or similar. If it is a clear violation then it should be removed promptly.

If you would rather not make such a post, or are unhappy with the outcome, a request for review should be sent to a [[Admins|site admin]]. Include the relevant URL for the content in dispute, and any information that may help in ascertaining that you are indeed the owner or represent the owner of the copyrighted work.

Before making any infringement claims please be aware that Wonkpedia regularly exercises a [[fair use]] right to copy portions of copyrighted works for the purposes of criticism, commentary, and research. While we take copyright concerns very seriously here, and will do our best to reach an amicable agreement for all parties, we will not be intimidated by false claims of copyright infringement made for the purpose of removing valid criticism from the site.

Template:Remove this line and insert a license instead

2022-10-06T14:23:45Z

Bmueller: /* Copyright */

=== Copyright unknown ===
This file is from a country/region whose copyright is not applicable in your region (e.g. Iran or North Korea), or whose copyright is unknown but believed to fall under fair use. While you're allowed to upload such files, intentionally uploading copyrighted materials and claiming to be ignorant when it gets claimed would be frowned upon. At the very least, do some due diligence to make sure you aren't uploading copyrighted material.

If you are a copyright owner or represent a copyright owner, and you believe that Wonkpedia is infringing your copyright, the quickest solution is to contact the admins directly through the official twitter, discord, github, wiki talk pages, or similar. If it is a clear violation then it should be removed promptly.

If you would rather not make such a post, or are unhappy with the outcome, a request for review should be sent to a [[Admins|site admin]]. Include the relevant URL for the content in dispute, and any information that may help in ascertaining that you are indeed the owner or represent the owner of the copyrighted work.

Before making any infringement claims please be aware that Wonkpedia regularly exercises a [[fair use]] right to copy portions of copyrighted works for the purposes of criticism, commentary, and research. While we take copyright concerns very seriously here, and will do our best to reach an amicable agreement for all parties, we will not be intimidated by false claims of copyright infringement made for the purpose of removing valid criticism from the site.

Template:Remove this line and insert a license instead

2022-10-06T14:22:21Z

Bmueller: /* Copyright */

=== Copyright ===
This file is from a country/region whose copyright is not applicable in your region (e.g. Iran or North Korea), or whose copyright is unknown but believed to fall under fair use.

If you are a copyright owner or represent a copyright owner, and you believe that Wonkpedia is infringing your copyright, the quickest solution is to contact the admins directly through the official twitter, discord, github, wiki talk pages, or similar. If it is a clear violation then it should be removed promptly.

If you would rather not make such a post, or are unhappy with the outcome, a request for review should be sent to a [[Admins|site admin]]. Include the relevant URL for the content in dispute, and any information that may help in ascertaining that you are indeed the owner or represent the owner of the copyrighted work.

Before making any infringement claims please be aware that Wonkpedia regularly exercises a [[fair use]] right to copy portions of copyrighted works for the purposes of criticism, commentary, and research. While we take copyright concerns very seriously here, and will do our best to reach an amicable agreement for all parties, we will not be intimidated by false claims of copyright infringement made for the purpose of removing valid criticism from the site.

File:Samsites pg2.jpeg

2022-10-06T14:21:52Z

Bmueller: Page 2 of the supposed Ukraine targeting sites

== Summary ==
Page 2 of the supposed Ukraine targeting sites
== Licensing ==
{{Remove this line and insert a license instead|year=2022|month=10|day=06}}

File:Samsites pg1.jpeg

2022-10-06T14:20:36Z

Bmueller: Page 1 of the supposed Ukraine targeting sites, 2022

== Summary ==
Page 1 of the supposed Ukraine targeting sites, 2022
== Licensing ==
{{Remove this line and insert a license instead|year=2022|month=10|day=06}}

Template:Remove this line and insert a license instead

2022-10-06T14:20:07Z

Bmueller: Created page with "== Copyright == This file is from a country/region whose copyright is not applicable in your region (e.g. Iran or North Korea), or whose copyright is unknown but believed to f..."

== Copyright ==
This file is from a country/region whose copyright is not applicable in your region (e.g. Iran or North Korea), or whose copyright is unknown but believed to fall under fair use.

If you are a copyright owner or represent a copyright owner, and you believe that Wonkpedia is infringing your copyright, the quickest solution is to contact the admins directly through the official twitter, discord, github, wiki talk pages, or similar. If it is a clear violation then it should be removed promptly.

If you would rather not make such a post, or are unhappy with the outcome, a request for review should be sent to a [[Admins|site admin]]. Include the relevant URL for the content in dispute, and any information that may help in ascertaining that you are indeed the owner or represent the owner of the copyrighted work.

Before making any infringement claims please be aware that Wonkpedia regularly exercises a [[fair use]] right to copy portions of copyrighted works for the purposes of criticism, commentary, and research. While we take copyright concerns very seriously here, and will do our best to reach an amicable agreement for all parties, we will not be intimidated by false claims of copyright infringement made for the purpose of removing valid criticism from the site.

Fun:List of Great Email Incidents

2022-08-31T20:39:12Z

Bmueller: /* August 31, 2022 */ Update

This page is a list of Great Email Incidents that have crippled entire sectors of military and/or government organizations. While we would like to think that large organizations have a minimum degree of competence, the existence of this list would indicate otherwise.

Obviously many more of these happen than are publicly discussed, so you ''know'' it's bad once it hits twitter.<ref>https://twitter.com/froggiemlm/status/1503394624966037512?s=20&t=J0Dp-A_cO_F8YQDVSb77wA</ref>

== August 31, 2022 ==
Seems to have impacted:

* Air Force
* DOD Contractors? ("[Non-DoD Source]" listed in email chain on Twitter screenshot)<ref>https://twitter.com/AaronMehta/status/1565060470897262593?s=20&t=-dk-FBvnc-ivuywEl5BVMg</ref>
According to a tweet (source unknown),<ref>https://twitter.com/mortibellum/status/1565060042960896000?s=20&t=-dk-FBvnc-ivuywEl5BVMg</ref> the email contents was as follows (some specifics redacted):<blockquote>We have a Logo appearing on our screen from Air Forces Cyber, xxxth Cyberspace Wing and xxxst Network Operations Sq. It states: "ATTENTION: This workspace will be quarantined <date>. Please contact your local CFP to upgrade this device to the latest OS Build (xxxxx or higher). We are here at <location> and have nothing to do with all those organizations. However, we are unable to get rid of that logo which of course is totally outdated. Perhaps some of you sent this over to us by mistake. Please remove this logo, as we are unable to do anything with this horrible green statement."</blockquote>(editor's note: perhaps they mean on-screen watermark and not logo?)

== References ==
<references />
[[Category:Fun]]
[[Category:Email]]
[[Category:Competence]]

Category:Competence

2022-08-31T20:31:52Z

Bmueller: Created page with "Articles listed here are about examples of only the greatest degree of competence exhibited by professionals"

Articles listed here are about examples of only the greatest degree of competence exhibited by professionals

Category:Email

2022-08-31T20:31:10Z

Bmueller: Created blank page

Category:Fun

2022-08-31T20:31:00Z

Bmueller: Created blank page

Fun:List of Great Email Incidents

2022-08-31T20:30:45Z

Bmueller: Create page stub

Rakwon

2022-08-25T22:55:39Z

Bmueller: Redirected page to Video Conferencing in North Korea

#REDIRECT [[Video Conferencing in North Korea]]

Video Conferencing in North Korea

2022-08-25T22:54:34Z

Bmueller: /* Rakwon */

Since North Korea's internet is heavily censored, usage of video conferencing is quite rare. However, there are several instances of North Korea using both Chinese and North Korean developed video conferencing technologies in recent years, especially during the Covid-19 pandemic. This page documents some of these examples.

== Rakwon ==
Rakwon is a North Korean videoconferencing software, used in universities for e-learning, for party meetings, weather center collaboration, and more.<ref>https://www.38north.org/2021/05/rakwon-north-koreas-video-conferencing-paradise/</ref><ref>https://www.northkoreatech.org/2022/01/12/north-koreas-online-it-exhibitions/</ref> On first glance, it appears to be designed based on Adobe Connect.

== Voov Meeting ==
Voov is a Chinese teleconferencing software made by Tencent. Some university professors have used it to collaborate internationally in the past.<ref>https://www.northkoreatech.org/2021/05/14/north-korean-university-links-with-foreign-lecturers-for-live-internet-seminars/</ref>

== References ==
<references />
[[Category:North Korea]]
[[Category:North Korea Tech]]
[[Category:Networking]]

Category:North Korea Tech

2022-08-25T22:53:03Z

Bmueller: Created blank page

Video Conferencing in North Korea

2022-08-25T22:52:49Z

Bmueller: Create stub

Since North Korea's internet is heavily censored, usage of video conferencing is quite rare. However, there are several instances of North Korea using both Chinese and North Korean developed video conferencing technologies in recent years, especially during the Covid-19 pandemic. This page documents some of these examples.

== Rakwon ==
Rakwon is a North Korean videoconferencing software, used in universities for e-learning, for party meetings, weather center collaboration, and more.<ref>https://www.38north.org/2021/05/rakwon-north-koreas-video-conferencing-paradise/</ref> On first glance, it appears to be designed based on Adobe Connect.

== Voov Meeting ==
Voov is a Chinese teleconferencing software made by Tencent. Some university professors have used it to collaborate internationally in the past.<ref>https://www.northkoreatech.org/2021/05/14/north-korean-university-links-with-foreign-lecturers-for-live-internet-seminars/</ref>

== References ==
<references />
[[Category:North Korea]]
[[Category:North Korea Tech]]
[[Category:Networking]]

Zaporizhzhia Nuclear Power Plant

2022-08-19T06:49:50Z

Bmueller:

{{Short description|Nuclear-power plant in Enerhodar, Ukraine}}
{{pp|small=yes}}
{{Use dmy dates|date=March 2022}}
{{Infobox power station
| name = Zaporizhzhia Nuclear Power Station
| name_official = Запорізька атомна електростанція
| image = Kernkraftwerk Saporischschja.JPG
| image_caption = Two cooling towers at left (one largely obscured by the other) and the six reactor buildings viewed from the [[Nikopol, Ukraine|Nikopol]] shore. The large building between the cooling towers and the reactors, and the two tall smokestacks, are at the [[Zaporizhzhia thermal power station]], beyond the nuclear plant.
| image_alt =
| coordinates = {{coord|47|30|30|N|34|35|04|E|region:UA-23_type:landmark|display=inline,title}}
| country = [[Ukraine]]
| location = [[Enerhodar]], [[Zaporizhzhia Oblast]]
| status = Operational
| construction_began = Unit 1: 1 April 1980 Unit 2: 1 January 1981 Unit 3: 1 April 1982 Unit 4: 1 April 1983 Unit 5: 1 November 1985 Unit 6: 1 June 1986
| commissioned = Unit 1: 25 December 1985 Unit 2: 15 February 1986 Unit 3: 5 March 1987 Unit 4: 14 April 1988 Unit 5: 27 October 1989 Unit 6: 17 September 1996
| decommissioned =
| cost =
| owner = [[Energoatom]]
| operator = Energoatom
| np_reactors = 6
| np_reactor_type = PWR
| np_reactor_supplier = [[Atomstroyexport]]
| np_fuel_type =
| np_fuel_supplier =
| ps_cogeneration =
| ps_cooling_source = [[Kakhovka Reservoir]]
| ps_cooling_towers = 2
| ps_units_operational = 6 × 950 MW
| ps_units_manu_model = 6 × [[VVER]]-1000/320
| ps_units_uc =
| ps_units_planned =
| ps_units_cancelled =
| ps_units_decommissioned =
| ps_thermal_capacity = 6 × 3000 MWth
| ps_heating_capacity =
| ps_electrical_capacity = 5700
| ps_electrical_cap_fac = 58.68%
| ps_storage_capacity =
| website = {{URL|https://www.npp.zp.ua/en}}{{dead link|date=March 2022}}
}}

The '''Zaporizhzhia Nuclear Power Station''' ({{lang-uk|Запорізька атомна електростанція|translit=Zaporizʹka atomna elektrostantsiya}}) in southeastern [[Ukraine]] is the largest [[nuclear power plant]] in Europe and [[list of largest power stations#Nuclear|among the 10 largest in the world]]. It was built by the [[Soviet Union]] near the city of [[Enerhodar]], on the southern shore of the [[Kakhovka Reservoir]] on the [[Dnieper]] river. It is operated by [[Energoatom]], who also operate Ukraine's other three nuclear power stations.

The plant has 6 [[VVER|VVER-1000]] [[pressurized water reactor|pressurized light water nuclear reactors]] (PWR), each fuelled with [[U235|{{sup|235}}U]] ([[Enriched uranium|LEU]])<ref name = "VVER_LEU">{{Citation|last1=Kosourov |first1=E. |last2=Pavlov |first2=V. |last3=Pavlovcev |first3=A. |last4=Spirkin |first4=E. |year=2003 |title=Improved VVER-1000 fuel cycle |publisher=RRC [[Kurchatov Institute]] |publication-place=[[Moscow]], [[Russia]] |url=https://inis.iaea.org/collection/NCLCollectionStore/_Public/38/059/38059185.pdf |accessdate=5 March 2022 }}</ref> and generating 950 [[MWe|MWe]], for a total power output of 5,700 MWe.<ref>{{cite web |url=http://www.industcards.com/nuclear-lt-ua.htm |title=Nuclear Power Plants in Lithuania & Ukraine |website=Industcards.com |access-date=31 August 2010 |archive-date=9 December 2012 |archive-url=https://archive.today/20121209092440/http://www.industcards.com/nuclear-lt-ua.htm |url-status=dead }}</ref> The first five were successively brought online between 1985 and 1989, and the sixth was added in 1995. The plant generates nearly half of the country's electricity derived from nuclear power,<ref name=wnn-20171107/> and more than a fifth of total [[Energy in Ukraine#Electricity|electricity generated in Ukraine]].<ref>{{cite web |url=https://www.energoatom.com.ua/en/about-6/separated-59/npp_zp-60 |title=SS "Zaporizhzhia NPP" |website=www.energoatom.com.ua |access-date=25 October 2020 |archive-date=27 October 2020 |archive-url=https://web.archive.org/web/20201027004706/https://www.energoatom.com.ua/en/about-6/separated-59/npp_zp-60 |url-status=live }}</ref> The [[Zaporizhzhia thermal power station]] is nearby.

On 4 March 2022, the nuclear and thermal power stations were both captured by [[Russia]]n forces during the [[Battle of Enerhodar]] of the [[2022 Russian invasion of Ukraine]].<ref name = "2022captureReuters">{{Cite news |last1=Polityuk |first1=Pavel |last2=Vasovic |first2=Aleksandar |last3=Irish |first3=John |date=2022-03-04 |title=Russian forces seize huge Ukrainian nuclear plant, fire extinguished |language=en |work=Reuters |url=https://www.reuters.com/markets/europe/top-wrap-1-europes-largest-nuclear-power-plant-fire-after-russian-attack-mayor-2022-03-04/ |access-date=2022-03-04 |archive-date=4 March 2022 |archive-url= https://web.archive.org/web/20220304100517/https://www.reuters.com/markets/europe/top-wrap-1-europes-largest-nuclear-power-plant-fire-after-russian-attack-mayor-2022-03-04/ |url-status=live }}</ref><ref name = "2022captureBloomberg">{{Cite web |last=Daniel Ten Kate |first=David Stringer |date=2022-03-04 |title=Russian Forces Occupy Site of Nuclear Plant as Fire Contained |url=https://www.bloomberg.com/news/articles/2022-03-04/russia-firing-on-zaporizhzhia-nuclear-plant-ukraine-says |url-status=live |archive-url= https://archive.today/20220304120723/https://www.bloomberg.com/news/articles/2022-03-04/russia-firing-on-zaporizhzhia-nuclear-plant-ukraine-says |archive-date=4 March 2022 |access-date=2022-03-04 |website=Bloomberg }}</ref><ref name="2022captureCA">{{cite news |last=Boynton |first=Sean |title=Russian troops capture Europe's largest power plant in Ukraine after intense battle |url=https://globalnews.ca/news/8658032/ukraine-russia-nuclear-plant-fire/ |newspaper=[[Global News]] |date=4 March 2022 |archive-date=4 March 2022 |archive-url=https://web.archive.org/web/20220304062939/https://globalnews.ca/news/8658032/ukraine-russia-nuclear-plant-fire/ |url-status=live}}</ref><ref name="2022captureNDTV1">{{Cite web |title=Russia Seizes Ukraine Nuclear Plant Hours After Attack: 10 Points |url=https://www.ndtv.com/world-news/russia-ukraine-war-vladimir-putin-biden-latest-developments-updates-on-kyiv-kharkiv-russian-invasion-2802607 |access-date=2022-03-04 |website=NDTV.com |archive-date=4 March 2022 |archive-url=https://web.archive.org/web/20220304130432/https://www.ndtv.com/world-news/russia-ukraine-war-vladimir-putin-biden-latest-developments-updates-on-kyiv-kharkiv-russian-invasion-2802607 |url-status=live }}</ref> {{As of|2022|3|12}} the plant is reportedly controlled by the Russian company [[Rosatom]].<ref name=Ukr_Pravda_20220312>{{Cite web |first=Roman |last=Petrenko |date= 12 March 2022 |title=Invaders seize Zaporizhzhia power plant and claims it is part of Rosatom |url= https://www.pravda.com.ua/eng/news/2022/03/12/7330624/ |access-date=2022-03-12 |website=[[Ukrayinska Pravda]] |language=en}}</ref> The plant continues to be operated by Ukrainian staff, under Russian control.<ref name=AP20220804/>

== Operational status ==

In 2017 modernization work was completed on unit 3, enabling a 10 year life-extension to 2027.<ref name=wnn-20171107>{{cite news |url=http://www.world-nuclear-news.org/RS-Zaporozhe-3-enters-next-10-years-of-operation-07111701.html |title=Zaporozhe 3 enters next 10 years of operation |publisher=World Nuclear News |date=7 November 2017 |access-date=8 November 2017 |archive-date=7 November 2017 |archive-url=https://web.archive.org/web/20171107183055/http://www.world-nuclear-news.org/RS-Zaporozhe-3-enters-next-10-years-of-operation-07111701.html |url-status=live }}</ref> In 2021 modernization work was completed on unit 5, enabling a 10 year life-extension.<ref name=nei-20210201>{{cite news |url=https://www.neimagazine.com/news/newsenergoatom-marks-life-extension-of-ukraines-zaporozhye-5-8484622 |title=Energoatom marks life extension of Ukraine's Zaporozhye 5 |publisher=Nuclear Engineering International |date=1 February 2021 |access-date=1 February 2021 |archive-date=19 October 2021 |archive-url=https://web.archive.org/web/20211019082930/https://www.neimagazine.com/news/newsenergoatom-marks-life-extension-of-ukraines-zaporozhye-5-8484622 |url-status=live }}</ref>

== Incidents ==
=== In 2014 ===
{{Main|2014 pro-Russian unrest in Ukraine|War in Donbas (2014–2022)}}
In May 2014, 40 armed members claiming to be representatives of [[Right Sector]] allegedly tried to gain access to the power plant area.<ref>{{cite news |url=http://www.ukrinform.ua/ukr/news/ohorona_zaes_zablokuvala_grupu_ozbroe_nih_osib_1939062 |script-title=uk:Охорона ЗАЕС заблокувала групу озброєних осіб |language=uk |trans-title=ZNPP security blocked a group of armed men |work=[[Ukrinform]] |access-date=26 June 2014 |archive-date=21 July 2014 |archive-url=https://web.archive.org/web/20140721080643/http://www.ukrinform.ua/ukr/news/ohorona_zaes_zablokuvala_grupu_ozbroe_nih_osib_1939062 |url-status=live }}</ref> The men were stopped by the Ukrainian police before entering into Enerhodar.

The Zaporizhzhia power plant is located around 200 km away from the [[War in Donbas (2014–2022)|War in Donbas]] combat zone, where fighting became very severe in 2014. On 31 August 2014, a [[Greenpeace]] member, Tobias Münchmeyer, expressed concerns the plant could be hit by heavy artillery from the fighting.

On 3 December 2014, [[Prime Minister of Ukraine|Prime Minister]] [[Arseny Yatseniuk]] announced the occurrence of an incident several days before at the Zaporizhzhia Nuclear Power Plant.<ref>{{cite news |url=http://www.huffingtonpost.com/2014/12/03/ukraine-nuclear-plant-accident_n_6260390.html |publisher=Huffington Post |title=Ukraine Reports Accident At Nuclear Power Plant, But Says Poses No Danger |date=3 December 2014 |access-date=3 December 2014 |archive-date=3 December 2014 |archive-url=https://web.archive.org/web/20141203184539/http://www.huffingtonpost.com/2014/12/03/ukraine-nuclear-plant-accident_n_6260390.html |url-status=live }}</ref> The cause of the incident was reported as a [[short circuit]] in the power outlet system and was not linked to the site's production.<ref>{{cite news |url=http://uk.reuters.com/article/uk-ukraine-crisis-power-idUKKCN0JH0ZZ20141203 |work=Reuters |title=Ukraine energy minister says 'no threat' from accident at nuclear plant |date=3 December 2014 |access-date=5 July 2021 |archive-date=30 June 2016 |archive-url=https://web.archive.org/web/20160630000455/http://uk.reuters.com/article/uk-ukraine-crisis-power-idUKKCN0JH0ZZ20141203 |url-status=live }}</ref> One of the six reactors of the plant was shut down twice in December 2014.<ref name=engycrisUD14/> This and [[Coal in Ukraine#Coal mining|lack of coal for Ukraine's coal-fired power stations]] led to rolling blackouts throughout the country from early until late December 2014.<ref name=engycrisUD14>[https://www.independent.co.uk/news/world/europe/ukraine-turns-off-reactor-at-nuclear-plant-after-accident-9947540.html Ukraine turns off reactor at its most powerful nuclear plant after 'accident'] {{Webarchive|url=https://web.archive.org/web/20171019042339/https://www.independent.co.uk/news/world/europe/ukraine-turns-off-reactor-at-nuclear-plant-after-accident-9947540.html |date=19 October 2017 }}, [[The Independent]] (28 December 2014) [https://www.nytimes.com/2014/12/25/world/europe/ukraine-briefly-cuts-power-to-crimea-amid-dispute-with-russia-over-nato.html?_r=0 Ukraine Briefly Cuts Power to Crimea Amid Feud With Russia Over NATO] {{Webarchive|url=https://web.archive.org/web/20160729102937/http://www.nytimes.com/2014/12/25/world/europe/ukraine-briefly-cuts-power-to-crimea-amid-dispute-with-russia-over-nato.html?_r=0 |date=29 July 2016 }}, [[New York Times]] (24 December 2014) [http://itar-tass.com/en/economy/770172 Coal import to help avoid rolling blackouts in Ukraine — energy minister] {{webarchive|url=https://web.archive.org/web/20150108051631/http://itar-tass.com/en/economy/770172 |date=8 January 2015 }}, [[ITAR-TASS]] (31 December 2014) [http://mashable.com/2014/12/03/ukraine-nuclear-plant-accident/ Rolling blackouts in Ukraine after nuclear plant accident] {{Webarchive|url=https://web.archive.org/web/20201031172322/https://mashable.com/2014/12/03/ukraine-nuclear-plant-accident/ |date=31 October 2020 }}, [[Mashable]] (3 December 2014) [https://www.bloomberg.com/news/2014-12-31/ukraine-to-import-coal-from-far-away-as-war-curtails-mines.html Ukraine to Import Coal From ‘Far Away’ as War Curtails Mines] {{Webarchive|url=https://web.archive.org/web/20150109121036/http://www.bloomberg.com/news/2014-12-31/ukraine-to-import-coal-from-far-away-as-war-curtails-mines.html |date=9 January 2015 }}, [[Bloomberg News]] (31 December 2014)</ref>

=== 2022 Russian invasion of Ukraine ===
{{float right clear none|{{Zaporizhzia_nuclear_power_plant_aerial.svg}} }}
{{See also|Battle of Enerhodar}}

After the [[2022 Russian invasion of Ukraine|Russian invasion of Ukraine]] began on 24 February 2022, [[Energoatom]] shut down Units 5 and 6 to reduce risk, keeping Units 1 to 4 in operation on 25 February 2022.<ref>{{cite web |last1=Kraev |first1=Kamen |date=25 February 2022 |title=Energoatom shuts down Zaporozhye-5 and −6 as rest of fleet remains safe and operational |url=https://www.nucnet.org/news/energoatom-shuts-down-zaporozhye-5-and-6-as-rest-of-fleet-remains-safe-and-operational-2-5-2022 |website=NucNet |access-date=25 February 2022 |archive-date=25 February 2022 |archive-url=https://web.archive.org/web/20220225203312/https://www.nucnet.org/news/energoatom-shuts-down-zaporozhye-5-and-6-as-rest-of-fleet-remains-safe-and-operational-2-5-2022 |url-status=live }}</ref>

At 11:28pm local time on 3 March 2022, a column of 10 Russian armored vehicles and two tanks approached the power plant.<ref name="NPR110322" /><ref>{{cite news |date=4 March 2022 |title=Security Council debates Russian strike on Ukraine nuclear power plant |work=UN News |url= https://news.un.org/en/story/2022/03/1113302 |access-date=6 March 2022}}</ref> Fighting commenced at 12:48am on 4 March when Ukraine forces fired [[anti-tank guided missile|anti-tank missiles]]. Russian forces responded with a variety of weapons, including [[rocket-propelled grenade]]s.<ref name="NPR110322" /> During approximately two hours of heavy combat, a fire broke out in a training facility outside the main complex, which was extinguished by 6:20am,<ref name="AlJ040322">{{cite news |title=Ukraine nuclear power plant attack: All you need to know |url= https://www.aljazeera.com/news/2022/3/4/zaporizhzhia-nuclear-power-plant-attack-all-you-need-to-know |access-date=3 April 2022 |publisher=Al Jazeera |date=4 March 2022}}</ref><ref>[https://www.ohchr.org/sites/default/files/2022-03/HRMMU_Update_2022-03-26_EN.pdf Update on the human rights situation in Ukraine (Reporting period: 24 February – 26 March)] ''United Nations Human Rights Monitoring Mission in Ukraine''</ref><ref name="Campbell">{{Cite magazine |last=Campbell |first=Charlie |date=21 April 2022 |title=As Putin threatens nuclear disaster, Europe learns to embrace nuclear energy again |url= https://time.com/6169164/ukraine-nuclear-energy-europe/ |access-date=2022-04-23 |magazine=Time |language=en}}</ref> though other sections surrounding the plant sustained damage.<ref name="NPR110322">{{cite news |title=Video analysis reveals Russian attack on Ukrainian nuclear plant veered near disaster |url=https://www.npr.org/2022/03/11/1085427380/ukraine-nuclear-power-plant-zaporizhzhia |access-date=1 April 2022 |publisher=NPR |date=11 March 2022}}</ref><ref name=IAEA_appeal>{{Cite web |title=IAEA appeal after shelling and fire at Zaporozhe |url=https://www.world-nuclear-news.org/Articles/IAEA-appeal-after-shelling-and-fire-at-Zaporozhe |date=4 March 2022 |access-date=2022-03-04 |website=World Nuclear News}}</ref> The fire did not impact reactor safety or any essential equipment.<ref name=IAEA_appeal/><ref>{{Cite web |date=2022-03-04 |title=IAEA Director General Grossi's initiative to travel to Ukraine |url=https://www.iaea.org/newscenter/pressreleases/iaea-director-general-grossis-initiative-to-travel-to-ukraine |access-date=2022-03-04 |website=www.iaea.org |language=en}}</ref><ref name="Campbell" /> The plant lost 1.3 GW of capacity.<ref>{{cite web|date=2022-03-04|title=TPP compensates for the shutdown of Zaporizhzhya NPP|url=https://energo.dtek.com/en/media-center/press/dtek-tpps-compensates-for-the-shutdown-of-units-of-zaporizhzhya-npp-due-to-attack-by-occupiers-/ |website=www.dtek.com|access-date=4 March 2022}}</ref>

''[[Ukrayinska Pravda]]'' reported on 12 March that the plant's management was told by Russian authorities that the plant now belonged to [[Rosatom]], Russia's state nuclear power company.<ref name=Ukr_Pravda_20220312/> It continued to operate and supply data, including from a remote monitoring system, to the [[IAEA]].<ref name=wnn-20220527>{{cite news |url=https://www.world-nuclear-news.org/Articles/Ukraine-says-any-IAEA-visit-to-occupied-Zaporizhyz |title=Ukraine says any IAEA visit to occupied Zaporizhzhia 'unacceptable' |publisher=World Nuclear News |date=27 May 2022 |access-date=31 May 2022}}</ref> It continued to be operated by Ukrainian staff, under Russian control.<ref name=AP20220804/>

On 5 July 2022, ''[[The Wall Street Journal]]'' reported that Russian forces arranged a military base in the complex by deploying heavy [[Self-propelled artillery|self-propelled]] [[multiple rocket launcher]] [[BM-30 Smerch]].<ref name="WSJ_RU_army_UA_nuc_plant">{{cite news |url=https://www.wsj.com/articles/russian-army-turns-ukraines-largest-nuclear-plant-into-a-military-base-11657035694 |title=Russian Army Turns Ukraine's Largest Nuclear Plant Into a Military Base |first1=Drew |last1=Hinshaw |first2=Joe |last2=Parkinson |newspaper=[[The Wall Street Journal]] |date=5 July 2022 |access-date=16 July 2022 |archive-date=5 July 2022 |archive-url=https://archive.today/20220705185932/https://www.wsj.com/amp/articles/russian-army-turns-ukraines-largest-nuclear-plant-into-a-military-base-11657035694 |url-status=live }}</ref> On 19 July 2022, three Ukrainian [[suicide drone]]s attacked Russian equipment and tents at the site. Ukraine's Ministry of Defense said that three Russian occupiers were killed and twelve injured.<ref>{{cite news |title=Ukrainian kamikaze drone hits Russian positions near Zaporizhia NPP |date=22 July 2022 |url= https://www.ukrinform.net/rubric-ato/3534841-ukrainian-kamikaze-drone-hits-russian-positions-near-zaporizhia-npp.html |newspaper=[[Ukrinform]] |access-date=22 July 2022}}</ref> The occupation administration was reported as saying that at least eleven employees were injured. An occupation official said the reactors were not damaged and it was unlikely they were the target.<ref name=telegraph-20220720>{{cite news |url=https://www.telegraph.co.uk/world-news/2022/07/20/ukrainian-kamikaze-drones-strike-russian-controlled-zaporizhzhia/ |title='Kamikaze drones' strike Russian-controlled Zaporizhzhia nuclear power plant |last=Vasilyeva |first=Nataliya |newspaper=The Daily Telegraph |url-access=limited |date=20 July 2022 |access-date=22 July 2022}}</ref>

On 3 August 2022, [[Rafael Grossi]], head of the IAEA, expressed grave concerns about the physical integrity of the plant, whether all necessary repairs and maintenance were being done, and the security of nuclear material.<ref name=AP20220804>{{cite news |title=UN nuclear chief: Ukraine nuclear plant is 'out of control' |first=Edith M. |last=Lederer |date=3 August 2022 |url= https://apnews.com/article/russia-ukraine-science-accidents-d2e0077af104f2692b76f737c58e1984 |newspaper=[[AP News]] |access-date=4 August 2022}}</ref> A mission to inspect the plant was being planned by the IAEA, waiting on approval by Ukrainian and Russian sides, as well as United Nations authorisation. Ukraine's state nuclear company [[Energoatom]] opposed an IAEA visit because "any visit would legitimise Russia's presence there". Occupation official [[Yevhen Balytskyi]] invited IAEA to visit to show how the Russians were guarding the facility while Ukrainians were attacking it.<ref>{{cite news |last1=Allen |first1=Claudia |last2=Jackson |first2=Patrick |title=Ukraine war: IAEA says Zaporizhzhia nuclear plant out of control |website=[[BBC News]] |language=en |date=3 August 2022 |publisher=[[BBC]] |url= https://www.bbc.com/news/world-europe-62412429 |access-date=4 August 2022}}</ref> By 6 August 2022 IAEA reported one of three reactors remaining in operation disconnected from the grid and triggered its emergency protection system as a result of shelling the previous day.<ref>{{cite web|url=https://www.iaea.org/newscenter/pressreleases/update-88-iaea-director-general-statement-on-situation-in-ukraine|title=Update 88 – IAEA Director General Statement on Situation in Ukraine|publisher=IAEA|date=August 6, 2022|accessdate=August 7, 2022}}</ref>

On 8 August 2022, damage was reported at the plant. Ukrainian authorities said that Russian shelling had damaged three radiation sensors and left a worker hospitalised; Ukrainian President [[Volodymyr Zelenskyy]] accused Russia of waging "nuclear terror". Local Russian-backed authorities said that Ukrainian forces had hit the site with a multiple rocket launcher, damaging administrative buildings and an area near a nuclear storage facility. UN secretary general [[António Guterres|Guterres]] said "any attack to a nuclear plant is a suicidal thing", calling for IAEA inspectors to be given access.<ref name=guardian-20220808>{{cite news |url=https://www.theguardian.com/world/2022/aug/08/ukraine-nuclear-plant-attack-suicidal-un-chief-zaporizhzhia-russia |title=Attack on Ukraine nuclear plant 'suicidal', says UN chief as he urges access to site |last=Koshiw |first=Isobel |newspaper=The Guardian |date=8 August 2022 |access-date=8 August 2022}}</ref> Ukraine's [[Energoatom]] called for a [[demilitarised zone]] around the plant with international peacekeepers deployed.<ref name=reuters-20220808>{{cite news |url=https://www.reuters.com/world/europe/un-chief-demands-international-access-ukraine-nuclear-plant-after-new-attack-2022-08-08/ |title=Ukraine calls for demilitarised zone around nuclear plant hit by shelling |last1=Zinets |first1=Natalia |last2=Hunder |first2=Max |publisher=Reuters |date=8 August 2022 |access-date=8 August 2022}}</ref>

On 9 August the head of [[Energoatom]] said that Russia plans to disconnect the station from the Ukrainian grid and connect it to the Russian grid.<ref>{{cite news |title=Russia to connect Zaporizhzhia NPP to Russian-controlled power grid in Crimea |url=https://www.pravda.com.ua/eng/news/2022/08/9/7362536/ |access-date=16 August 2022 |publisher=Ukrainska Pravda}}</ref>

On 11 August the complex was shelled several times, including near where radioactive materials were stored. Ukraine said that Russia did the shelling, while Russian officials said that Ukraine did it.<ref>{{cite news |title=Ukraine, Russia blame each other for shelling of nuclear plant |date=12 August 2022 |url= https://www.reuters.com/world/europe/ukraine-energoatom-says-zaporizhzhia-nuclear-power-plant-shelled-again-2022-08-11/ |newspaper=[[Reuters]] |access-date=15 August 2022}}</ref><ref>{{citeweb|url=https://www.pravda.com.ua/news/2022/08/11/7362846/index.amp|title=Росіяни 4 рази за день обстріляли ЗАЕС і околиці – Енергоатом|trans-title=The Russians shelled the ZNPP and its precinct 4 times in a day – Energoatom|date= 11 August 2022|publisher=Ukrayinska Pravda|lang=uk}}</ref>

On 14 August Zelenskyy accused Russia of stationing troops at the plant to fire at the cities of [[Nikopol, Ukraine|Nikopol]] and [[Marhanets]] across [[Kakhovka Reservoir]].<ref>{{Cite web |date=2022-08-14 |title=Live: Zelensky accuses Russian soldiers of staging attacks from Zaporizhzhia nuclear plant |url=https://www.france24.com/en/europe/20220814-live-ukraine-russia-accuse-each-other-of-nuclear-plant-strikes |access-date=2022-08-14 |website=France 24 |language=en}}</ref>

== Location ==
todo

== See also ==
{{Portal|Ukraine|Energy|Nuclear technology}}
* [[Energy in Ukraine]]
* [[Enerhodar Dnipro Powerline Crossing]]
* [[List of power stations in Ukraine]]
* [[Nuclear power in Ukraine]]

== References ==
{{Reflist|30em}}

== External links ==
{{Commons category}}
* {{Official website}}
* [https://www.energoatom.com.ua/en/about-6/separated-59/npp_zp-60 History of ZNPP]
* [https://web.archive.org/web/20100520050950/http://www.insc.anl.gov/neisb/neisb4/NEISB_3.3.A5.html Information about the plant from INSC website]

{{Nuclear power in Ukraine}}
{{Authority control}}

[[Category:Buildings and structures in Zaporizhzhia Oblast]]
[[Category:Energoatom]]
[[Category:Nuclear power stations built in the Soviet Union]]
[[Category:Nuclear power stations in Ukraine]]
[[Category:Nuclear power stations using VVER reactors]]

Module:Transclusion count/data/A

2022-08-18T22:32:33Z

Bmueller: 1 revision imported

return {
["A-Class"] = 6100,
["AARTalk"] = 8800,
["ACArt"] = 6200,
["AFB_game_box_end"] = 2400,
["AFB_game_box_start"] = 2400,
["AFC_comment"] = 14000,
["AFC_submission"] = 26000,
["AFC_submission_category_header"] = 4600,
["AFD_help"] = 86000,
["AFD_help/styles.css"] = 86000,
["AFI/Picture_box"] = 3400,
["AFI/Picture_box/show_picture"] = 3300,
["AFI_film"] = 6800,
["AFL_Car"] = 2500,
["AFL_Col"] = 2400,
["AFL_Ess"] = 2400,
["AFL_Gee"] = 2400,
["AFL_Haw"] = 2200,
["AFL_Mel"] = 2600,
["AFL_Nor"] = 2200,
["AFL_Ric"] = 2400,
["AFL_StK"] = 2800,
["AFL_Tables"] = 11000,
["AFL_Year"] = 2500,
["ALG"] = 2300,
["AMARB"] = 4700,
["AML"] = 4700,
["AMQ"] = 4800,
["AM_station_data"] = 4600,
["ARG"] = 6400,
["ASIN"] = 4000,
["ASN"] = 3400,
["ATP"] = 4600,
["AUS"] = 15000,
["AUT"] = 9100,
["AZE"] = 2400,
["A_note"] = 9500,
["A_or_an"] = 24000,
["Aan"] = 41000,
["Abbr"] = 729000,
["Abbrlink"] = 17000,
["Abot"] = 7400,
["About"] = 151000,
["Acad"] = 6400,
["Access_icon"] = 2500,
["According_to_whom"] = 4000,
["AchievementTable"] = 10000,
["Active_politician"] = 5300,
["AdSenseSummary"] = 3700,
["Added"] = 2300,
["Adjacent_communities"] = 26000,
["Adjacent_stations"] = 30000,
["Adjacent_stations/styles.css"] = 30000,
["Admin"] = 13000,
["Administrator_note"] = 6300,
["Adminnote"] = 3400,
["Advert"] = 20000,
["Aet"] = 4300,
["AfC_age_category"] = 2300,
["AfC_comment"] = 14000,
["AfC_date_category"] = 177000,
["AfC_status/age"] = 2300,
["AfC_status/backlog"] = 2800,
["AfC_submission"] = 38000,
["AfC_submission/comments"] = 25000,
["AfC_submission/declined"] = 25000,
["AfC_submission/declinedivbox"] = 25000,
["AfC_submission/draft"] = 11000,
["AfC_submission/helptools"] = 36000,
["AfC_submission/pending"] = 2300,
["AfC_submission/tools"] = 2300,
["AfC_submission_category_header"] = 5300,
["AfC_submission_category_header/day"] = 5100,
["AfC_submission_category_header/td"] = 5100,
["AfC_talk/C_percentage"] = 2200,
["AfC_topic"] = 24000,
["AfD_categories_horizontal_shortnames"] = 4000,
["AfD_count_link"] = 3800,
["Afd-merged-from"] = 7300,
["AfricaProject"] = 30000,
["Africa_topic"] = 6000,
["After_extra_time"] = 4300,
["Age"] = 35000,
["Age_in_days"] = 3900,
["Age_in_years"] = 3400,
["Age_in_years,_months,_weeks_and_days"] = 3700,
["Age_in_years,_months_and_days"] = 16000,
["Age_in_years_and_days"] = 3500,
["Age_in_years_and_days_nts"] = 2800,
["Ahnentafel"] = 8300,
["Ahnentafel/styles.css"] = 8300,
["Air_Force_Historical_Research_Agency"] = 4300,
["Air_force"] = 6700,
["Air_force/core"] = 6700,
["Aircontent"] = 9300,
["Aircraft_specs"] = 12000,
["Aircraft_specs/convert"] = 12000,
["Aircraft_specs/eng"] = 12000,
["Aircraft_specs/length"] = 12000,
["Aircraft_specs/range"] = 12000,
["Aircraft_specs/speed"] = 12000,
["Airport-dest-list"] = 3600,
["Airport_codes"] = 15000,
["Airport_destination_list"] = 4900,
["Al"] = 61000,
["Album"] = 204000,
["Album_chart"] = 26000,
["Album_chart/chartnote"] = 26000,
["Album_cover_fur"] = 52000,
["Album_label_category"] = 2100,
["Album_label_category/core"] = 2100,
["Album_ratings"] = 92000,
["Album_reviews"] = 6500,
["Albums"] = 7500,
["Albums_category"] = 23000,
["Albums_category/core"] = 23000,
["Albums_category/type/default"] = 23000,
["Align"] = 153000,
["Aligned_table"] = 11000,
["AllIrelandByCountyCatNav"] = 2200,
["AllMovie_name"] = 5500,
["AllMovie_title"] = 26000,
["AllMusic"] = 77000,
["Allcaps"] = 8000,
["Allcaps/styles.css"] = 8000,
["Allmovie"] = 4300,
["Allmovie_title"] = 2400,
["Allmusic"] = 18000,
["Allow_wrap"] = 36000,
["Alumni"] = 2100,
["Always_substitute"] = 6200,
["Ambox"] = 1430000,
["Ambox_globe"] = 32000,
["Ambox_globe_current_red"] = 30000,
["American_English"] = 14000,
["American_football_roster/Footer"] = 3000,
["American_football_roster/Header"] = 3000,
["American_football_roster/Player"] = 2900,
["Americanfootballbox"] = 2600,
["Amg_movie"] = 11000,
["Amg_name"] = 3200,
["Anarchism_announcements"] = 2900,
["Anarchism_announcements/shell"] = 2900,
["Anchor"] = 73000,
["Angbr_IPA"] = 2200,
["Angle_bracket"] = 2800,
["Anglican_navbox_titlestyle"] = 14000,
["Anglicise_rank"] = 547000,
["Animal_tasks"] = 17000,
["Anime_News_Network"] = 10000,
["Ann"] = 6200,
["Annotated_link"] = 6100,
["Annual_readership"] = 41000,
["Anon_block"] = 3600,
["Anonblock"] = 44000,
["Antonym_of_(dis)establish"] = 4900,
["ArbCom_Arab-Israeli_editnotice"] = 2000,
["ArbCom_Arab-Israeli_enforcement"] = 2900,
["Arbitration_Committee_candidate/data"] = 65000,
["Archive"] = 148000,
["Archive-nav"] = 5700,
["Archive_bottom"] = 39000,
["Archive_box"] = 18000,
["Archive_list"] = 60000,
["Archive_navigation"] = 7300,
["Archive_top"] = 22000,
["Archivebottom"] = 3500,
["Archivebox"] = 2500,
["Archives"] = 44000,
["Archivetop"] = 3500,
["Army"] = 15000,
["Army/core"] = 15000,
["Art_UK_bio"] = 2400,
["Art_UK_bio/plural"] = 2400,
["Article"] = 2900,
["ArticleHistory"] = 31000,
["Article_alerts_box"] = 3500,
["Article_history"] = 45000,
["Articles_by_Quality"] = 2200,
["Articles_by_Quality/down"] = 2300,
["Articles_by_Quality/total"] = 2300,
["Articles_by_Quality/up"] = 2300,
["As_of"] = 73000,
["Asbox"] = 2380000,
["Asbox/styles.css"] = 2380000,
["Asia_topic"] = 9600,
["Asof"] = 7200,
["Assessed-Class"] = 18000,
["Assignment"] = 5500,
["Assignment_milestones"] = 4800,
["AstDys"] = 2900,
["AthAbbr"] = 3600,
["Atnhead"] = 5900,
["Atop"] = 3800,
["Attached_KML"] = 12000,
["AuEduNewbie"] = 2500,
["Audio"] = 24000,
["Audio_sample"] = 3000,
["AustralianFootball"] = 7400,
["Australian_Dictionary_of_Biography"] = 2100,
["Australian_English"] = 2300,
["Australian_party_style"] = 5700,
["Australian_politics/name"] = 4000,
["Australian_politics/party_colours"] = 5800,
["Austria_metadata_Wikidata"] = 2100,
["Austria_population_Wikidata"] = 2100,
["Aut"] = 8300,
["Authority_control"] = 1980000,
["Authority_control_(arts)"] = 16000,
["Auto_link"] = 76000,
["Autobiography"] = 2100,
["Automated_tools"] = 78000,
["Automated_tools/core"] = 78000,
["Automatic_Taxobox"] = 2600,
["Automatic_archive_navigator"] = 118000,
["Automatic_taxobox"] = 68000,
["Aviation_accidents_and_incidents"] = 2100,
["Awaiting_admin"] = 2300,
["Awaitingadmin"] = 2200,
["Award2"] = 2400,
["Awards"] = 2300,
["Awards_table"] = 5200,
["Awards_table/styles.css"] = 5200,
["Ayd"] = 2600,
["Aye"] = 20000,
["Module:A_or_an"] = 24000,
["Module:A_or_an/words"] = 24000,
["Module:About"] = 151000,
["Module:Adjacent_stations"] = 68000,
["Module:Adjacent_stations/Amtrak"] = 2200,
["Module:Adjacent_stations/Indian_Railways"] = 2800,
["Module:Adjacent_stations/i18n"] = 68000,
["Module:AfC_submission_catcheck"] = 356000,
["Module:AfC_topic"] = 24000,
["Module:Age"] = 1130000,
["Module:Ahnentafel"] = 8300,
["Module:Airport_destination_list"] = 4900,
["Module:Album_ratings"] = 92000,
["Module:Aligned_table"] = 11000,
["Module:Anchor"] = 73000,
["Module:Ancient_Egypt_era"] = 2800,
["Module:Ancient_Egypt_era/data"] = 2800,
["Module:Ancient_Egypt_kings"] = 2800,
["Module:Ancient_Egypt_kings/data"] = 2800,
["Module:Ancient_Olympiads"] = 2800,
["Module:Ancient_Olympiads/data"] = 2800,
["Module:Archive_list"] = 62000,
["Module:Arguments"] = 30200000,
["Module:Armenian"] = 2800,
["Module:Article_history"] = 45000,
["Module:Article_history/Category"] = 45000,
["Module:Article_history/config"] = 45000,
["Module:Asbox"] = 2380000,
["Module:Asbox_stubtree"] = 36000,
["Module:Attached_KML"] = 12000,
["Module:Attached_KML/styles.css"] = 12000,
["Module:Australian_place_map"] = 16000,
["Module:Authority_control"] = 1980000,
["Module:Automated_taxobox"] = 327000,
["Module:Automatic_archive_navigator"] = 118000,
["Module:Automatic_archive_navigator/config"] = 118000,
["Module:Autotaxobox"] = 547000,
}

Module:Suppress categories

2022-08-18T22:32:33Z

Bmueller: 1 revision imported

-- This is a simple module to strip categories from wikitext. It does
-- not support nested links or magic words like __TOC__, etc. Even so,
-- it should still handle most categories.

local p = {}

-- Detects if a category link is valid or not. If it is valid,
-- the function returns the blank string. If not, the input
-- is returned with no changes.
local function processCategory( all, submatch )
local beforePipe = mw.ustring.match( submatch, '^(.-)[%s_]*|[%s_]*.-$' )
beforePipe = beforePipe or submatch
if mw.ustring.match( beforePipe, '[%[%]<>{}%c\n]' ) then
return all
else
return ''
end
end

-- Preprocess the content if we aren't being called from #invoke,
-- and pass it to gsub to remove valid category links.
local function suppress( content, isPreprocessed )
if not isPreprocessed then
content = mw.getCurrentFrame():preprocess( content )
end
content = mw.ustring.gsub(
content,
'(%[%[[%s_]*[cC][aA][tT][eE][gG][oO][rR][yY][%s_]*:[%s_]*(.-)[%s_]*%]%])',
processCategory
)
return content
end

-- Get the content to suppress categories from, and find
-- whether the content has already been preprocessed. (If the
-- module is called from #invoke, it has been preprocessed already.)
function p.main( frame )
local content, isPreprocessed
if frame == mw.getCurrentFrame() then
content = frame:getParent().args[1]
if frame.args[1] then
content = frame.args[1]
end
isPreprocessed = true
else
content = frame
isPreprocessed = false
end
return suppress( content, isPreprocessed )
end

return p

Module:Sidebar/styles.css

2022-08-18T22:32:33Z

Bmueller: 1 revision imported

/* {{pp-template}} */
/* TODO: Invert width design to be "mobile first" */
.sidebar {
/* TODO: Ask if we should have max-width 22em instead */
width: 22em;
/* @noflip */
float: right;
/* @noflip */
clear: right;
/* @noflip */
margin: 0.5em 0 1em 1em;
background: #f8f9fa;
border: 1px solid #aaa;
padding: 0.2em;
text-align: center;
line-height: 1.4em;
font-size: 88%;
border-collapse: collapse;
/* Timeless has display: none on .nomobile at mobile resolutions, so we
* unhide it with display: table and let precedence and proximity win.
*/
display: table;
}

/* Unfortunately, so does Minerva desktop, except Minerva drops an
* !important on the declaration. So we have to be mean for Minerva users.
* Mobile removes the element entirely with `wgMFRemovableClasses` in
* https://github.com/wikimedia/operations-mediawiki-config/blob/master/
wmf-config/InitialiseSettings.php#L16992
* which is why displaying it categorically with display: table works.
* We don't really want to expose the generic user in the wild on mobile to have
* to deal with sidebars. (Maybe the ones with collapsible lists, so that
* might be an improvement. That is blocked on [[:phab:T111565]].)
*/
body.skin-minerva .sidebar {
display: table !important;
/* also, minerva is way too aggressive about other stylings on tables.
* TODO remove when this template gets moved to a div. plans on talk page.
* We always float right on Minerva because that's a lot of extra CSS
* otherwise. */
float: right !important;
margin: 0.5em 0 1em 1em !important;
}

.sidebar-subgroup {
width: 100%;
margin: 0;
border-spacing: 0;
}

.sidebar-left {
/* @noflip */
float: left;
/* @noflip */
clear: left;
/* @noflip */
margin: 0.5em 1em 1em 0;
}

.sidebar-none {
float: none;
clear: both;
/* @noflip */
margin: 0.5em 1em 1em 0;
}

.sidebar-outer-title {
padding: 0 0.4em 0.2em;
font-size: 125%;
line-height: 1.2em;
font-weight: bold;
}

.sidebar-top-image {
padding: 0.4em;
}

.sidebar-top-caption,
.sidebar-pretitle-with-top-image,
.sidebar-caption {
padding: 0.2em 0.4em 0;
line-height: 1.2em;
}

.sidebar-pretitle {
padding: 0.4em 0.4em 0;
line-height: 1.2em;
}

.sidebar-title,
.sidebar-title-with-pretitle {
padding: 0.2em 0.8em;
font-size: 145%;
line-height: 1.2em;
}

.sidebar-title-with-pretitle {
padding: 0.1em 0.4em;
}

.sidebar-image {
padding: 0.2em 0.4em 0.4em;
}

.sidebar-heading {
padding: 0.1em 0.4em;
}

.sidebar-content {
padding: 0 0.5em 0.4em;
}

.sidebar-content-with-subgroup {
padding: 0.1em 0.4em 0.2em;
}

.sidebar-above,
.sidebar-below {
padding: 0.3em 0.8em;
font-weight: bold;
}

.sidebar-collapse .sidebar-above,
.sidebar-collapse .sidebar-below {
border-top: 1px solid #aaa;
border-bottom: 1px solid #aaa;
}

.sidebar-navbar {
text-align: right;
font-size: 115%;
padding: 0 0.4em 0.4em;
}

.sidebar-list-title {
padding: 0 0.4em;
text-align: left;
font-weight: bold;
line-height: 1.6em;
font-size: 105%;
}

/* centered text with mw-collapsible headers is finicky */
.sidebar-list-title-c {
padding: 0 0.4em;
text-align: center;
margin: 0 3.3em;
}

@media (max-width: 720px) {
/* users have wide latitude to set arbitrary width and margin :(
"Super-specific" selector to prevent overriding this appearance by
lower level sidebars too */
body.mediawiki .sidebar {
width: 100% !important;
clear: both;
float: none !important; /* Remove when we div based; Minerva is dumb */
margin-left: 0 !important;
margin-right: 0 !important;
}
/* TODO: We might consider making all links wrap at small resolutions and then
* only introduce nowrap at higher resolutions. Do when we invert the media
* query.
*/
}

Module:Sidebar/configuration

2022-08-18T22:32:32Z

Bmueller: 1 revision imported

return {
i18n = {
child_yes = 'yes',
float_none = 'none',
float_left = 'left',
wrap_true = 'true',
navbar_none = 'none',
navbar_off = 'off',
default_list_title = 'List',
title_not_to_add_navbar = 'Template:Sidebar',
collapse_title_not_to_add_navbar = 'Template:Sidebar with collapsible lists',
templatestyles = 'Module:Sidebar/styles.css',
category = {
child = '[[Category:Pages using sidebar with the child parameter]]',
conversion = '[[Category:Sidebars with styles needing conversion]]'
},
pattern = {
collapse_sandbox = '/sandbox$',
sandbox = '/sandbox$',
subgroup = 'sidebar%-subgroup',
style_conversion = 'style$',
uncategorized_conversion_titles = {
'/[Ss]andbox',
'/[Tt]estcases',
'/[Dd]oc$'
}
},
class = {
sidebar = 'sidebar',
subgroup = 'sidebar-subgroup',
collapse = 'sidebar-collapse',
float_none = 'sidebar-none',
float_left = 'sidebar-left',
wraplinks = 'nowraplinks',
outer_title = 'sidebar-outer-title',
top_image = 'sidebar-top-image',
top_caption = 'sidebar-top-caption',
pretitle = 'sidebar-pretitle',
pretitle_with_top_image = 'sidebar-pretitle-with-top-image',
title = 'sidebar-title',
title_with_pretitle = 'sidebar-title-with-pretitle',
image = 'sidebar-image',
caption = 'sidebar-caption',
above = 'sidebar-above',
heading = 'sidebar-heading',
content = 'sidebar-content',
content_with_subgroup = 'sidebar-content-with-subgroup',
below = 'sidebar-below',
navbar = 'sidebar-navbar',
list = 'sidebar-list',
list_title = 'sidebar-list-title',
list_title_centered = 'sidebar-list-title-c',
list_content = 'sidebar-list-content'
}
}
}

Module:Sidebar

2022-08-18T22:32:32Z

Bmueller: 1 revision imported

--
-- This module implements {{Sidebar}}
--
require('Module:No globals')
local cfg = mw.loadData('Module:Sidebar/configuration')

local p = {}

local getArgs = require('Module:Arguments').getArgs

--[[
Categorizes calling templates and modules with a 'style' parameter of any sort
for tracking to convert to TemplateStyles.

TODO after a long cleanup: Catch sidebars in other namespaces than Template and Module.
TODO would probably want to remove /log and /archive as CS1 does
]]
local function categorizeTemplatesWithInlineStyles(args)
local title = mw.title.getCurrentTitle()
if title.namespace ~= 10 and title.namespace ~= 828 then return '' end
for _, pattern in ipairs (cfg.i18n.pattern.uncategorized_conversion_titles) do
if title.text:match(pattern) then return '' end
end

for key, _ in pairs(args) do
if mw.ustring.find(key, cfg.i18n.pattern.style_conversion) or key == 'width' then
return cfg.i18n.category.conversion
end
end
end

--[[
For compatibility with the original {{sidebar with collapsible lists}}
implementation, which passed some parameters through {{#if}} to trim their
whitespace. This also triggered the automatic newline behavior.
]]
-- See ([[meta:Help:Newlines and spaces#Automatic newline]])
local function trimAndAddAutomaticNewline(s)
s = mw.ustring.gsub(s, "^%s*(.-)%s*$", "%1")
if mw.ustring.find(s, '^[#*:;]') or mw.ustring.find(s, '^{|') then
return '\n' .. s
else
return s
end
end

--[[
Finds whether a sidebar has a subgroup sidebar.
]]
local function hasSubgroup(s)
if mw.ustring.find(s, cfg.i18n.pattern.subgroup) then
return true
else
return false
end
end

--[[
Main sidebar function. Takes the frame, args, and an optional collapsibleClass.
The collapsibleClass is and should be used only for sidebars with collapsible
lists, as in p.collapsible.
]]
function p.sidebar(frame, args, collapsibleClass)
if not args then
args = getArgs(frame)
end
local root = mw.html.create()
local child = args.child and mw.text.trim(args.child) == cfg.i18n.child_yes

root = root:tag('table')
if not child then
root
:addClass(cfg.i18n.class.sidebar)
-- force collapsibleclass to be sidebar-collapse otherwise output nothing
:addClass(collapsibleClass == cfg.i18n.class.collapse and cfg.i18n.class.collapse or nil)
:addClass('nomobile')
:addClass(args.float == cfg.i18n.float_none and cfg.i18n.class.float_none or nil)
:addClass(args.float == cfg.i18n.float_left and cfg.i18n.class.float_left or nil)
:addClass(args.wraplinks ~= cfg.i18n.wrap_true and cfg.i18n.class.wraplinks or nil)
:addClass(args.bodyclass or args.class)
:css('width', args.width or nil)
:cssText(args.bodystyle or args.style)

if args.outertitle then
root
:tag('caption')
:addClass(cfg.i18n.class.outer_title)
:addClass(args.outertitleclass)
:cssText(args.outertitlestyle)
:wikitext(args.outertitle)
end

if args.topimage then
local imageCell = root:tag('tr'):tag('td')

imageCell
:addClass(cfg.i18n.class.top_image)
:addClass(args.topimageclass)
:cssText(args.topimagestyle)
:wikitext(args.topimage)

if args.topcaption then
imageCell
:tag('div')
:addClass(cfg.i18n.class.top_caption)
:cssText(args.topcaptionstyle)
:wikitext(args.topcaption)
end
end

if args.pretitle then
root
:tag('tr')
:tag('td')
:addClass(args.topimage and cfg.i18n.class.pretitle_with_top_image
or cfg.i18n.class.pretitle)
:addClass(args.pretitleclass)
:cssText(args.basestyle)
:cssText(args.pretitlestyle)
:wikitext(args.pretitle)
end
else
root
:addClass(cfg.i18n.class.subgroup)
:addClass(args.bodyclass or args.class)
:cssText(args.bodystyle or args.style)
end

if args.title then
if child then
root
:wikitext(args.title)
else
root
:tag('tr')
:tag('th')
:addClass(args.pretitle and cfg.i18n.class.title_with_pretitle
or cfg.i18n.class.title)
:addClass(args.titleclass)
:cssText(args.basestyle)
:cssText(args.titlestyle)
:wikitext(args.title)
end
end

if args.image then
local imageCell = root:tag('tr'):tag('td')

imageCell
:addClass(cfg.i18n.class.image)
:addClass(args.imageclass)
:cssText(args.imagestyle)
:wikitext(args.image)

if args.caption then
imageCell
:tag('div')
:addClass(cfg.i18n.class.caption)
:cssText(args.captionstyle)
:wikitext(args.caption)
end
end

if args.above then
root
:tag('tr')
:tag('td')
:addClass(cfg.i18n.class.above)
:addClass(args.aboveclass)
:cssText(args.abovestyle)
:newline() -- newline required for bullet-points to work
:wikitext(args.above)
end

local rowNums = {}
for k, v in pairs(args) do
k = '' .. k
local num = k:match('^heading(%d+)$') or k:match('^content(%d+)$')
if num then table.insert(rowNums, tonumber(num)) end
end
table.sort(rowNums)
-- remove duplicates from the list (e.g. 3 will be duplicated if both heading3
-- and content3 are specified)
for i = #rowNums, 1, -1 do
if rowNums[i] == rowNums[i - 1] then
table.remove(rowNums, i)
end
end

for i, num in ipairs(rowNums) do
local heading = args['heading' .. num]
if heading then
root
:tag('tr')
:tag('th')
:addClass(cfg.i18n.class.heading)
:addClass(args.headingclass)
:addClass(args['heading' .. num .. 'class'])
:cssText(args.basestyle)
:cssText(args.headingstyle)
:cssText(args['heading' .. num .. 'style'])
:newline()
:wikitext(heading)
end

local content = args['content' .. num]
if content then
root
:tag('tr')
:tag('td')
:addClass(hasSubgroup(content) and cfg.i18n.class.content_with_subgroup
or cfg.i18n.class.content)
:addClass(args.contentclass)
:addClass(args['content' .. num .. 'class'])
:cssText(args.contentstyle)
:cssText(args['content' .. num .. 'style'])
:newline()
:wikitext(content)
:done()
-- Without a linebreak after the </td>, a nested list like
-- "* {{hlist| ...}}" doesn't parse correctly.
:newline()
end
end

if args.below then
root
:tag('tr')
:tag('td')
:addClass(cfg.i18n.class.below)
:addClass(args.belowclass)
:cssText(args.belowstyle)
:newline()
:wikitext(args.below)
end

if not child then
if args.navbar ~= cfg.i18n.navbar_none and args.navbar ~= cfg.i18n.navbar_off and
(args.name or frame:getParent():getTitle():gsub(cfg.i18n.pattern.sandbox, '') ~=
cfg.i18n.title_not_to_add_navbar) then
root
:tag('tr')
:tag('td')
:addClass(cfg.i18n.class.navbar)
:cssText(args.navbarstyle)
:wikitext(require('Module:Navbar')._navbar{
args.name,
mini = 1,
fontstyle = args.navbarfontstyle
})
end
end

local base_templatestyles = frame:extensionTag{
name = 'templatestyles', args = { src = cfg.i18n.templatestyles }
}

local templatestyles = ''
if args['templatestyles'] and args['templatestyles'] ~= '' then
templatestyles = frame:extensionTag{
name = 'templatestyles', args = { src = args['templatestyles'] }
}
end

local child_templatestyles = ''
if args['child templatestyles'] and args['child templatestyles'] ~= '' then
child_templatestyles = frame:extensionTag{
name = 'templatestyles', args = { src = args['child templatestyles'] }
}
end

local grandchild_templatestyles = ''
if args['grandchild templatestyles'] and args['grandchild templatestyles'] ~= '' then
grandchild_templatestyles = frame:extensionTag{
name = 'templatestyles', args = { src = args['grandchild templatestyles'] }
}
end

return table.concat({
base_templatestyles,
templatestyles,
child_templatestyles,
grandchild_templatestyles,
tostring(root),
(child and cfg.i18n.category.child or ''),
categorizeTemplatesWithInlineStyles(args)
})
end

local function list_title(args, is_centered_list_titles, num)

local title_text = trimAndAddAutomaticNewline(args['list' .. num .. 'title']
or cfg.i18n.default_list_title)

local title
if is_centered_list_titles then
-- collapsible can be finicky, so provide some CSS/HTML to support
title = mw.html.create('div')
:addClass(cfg.i18n.class.list_title_centered)
:wikitext(title_text)
else
title = mw.html.create()
:wikitext(title_text)
end

local title_container = mw.html.create('div')
:addClass(cfg.i18n.class.list_title)
-- don't /need/ a listnumtitleclass because you can do
-- .templateclass .listnumclass .sidebar-list-title
:addClass(args.listtitleclass)
:cssText(args.basestyle)
:cssText(args.listtitlestyle)
:cssText(args['list' .. num .. 'titlestyle'])
:node(title)
:done()

return title_container
end

--[[
Main entry point for sidebar with collapsible lists.
Does the work of creating the collapsible lists themselves and including them
into the args.
]]
function p.collapsible(frame)
local args = getArgs(frame)
if not args.name and
frame:getParent():getTitle():gsub(cfg.i18n.pattern.collapse_sandbox, '') ==
cfg.i18n.collapse_title_not_to_add_navbar then
args.navbar = cfg.i18n.navbar_none
end

local contentArgs = {}

local is_centered_list_titles
if args['centered list titles'] and args['centered list titles'] ~= '' then
is_centered_list_titles = true
else
is_centered_list_titles = false
end

for k, v in pairs(args) do
local num = string.match(k, '^list(%d+)$')
if num then
local expand = args.expanded and
(args.expanded == 'all' or args.expanded == args['list' .. num .. 'name'])
local row = mw.html.create('div')
row
:addClass(cfg.i18n.class.list)
:addClass('mw-collapsible')
:addClass((not expand) and 'mw-collapsed' or nil)
:addClass(args['list' .. num .. 'class'])
:cssText(args.listframestyle)
:cssText(args['list' .. num .. 'framestyle'])
:node(list_title(args, is_centered_list_titles, num))
:tag('div')
:addClass(cfg.i18n.class.list_content)
:addClass('mw-collapsible-content')
-- don't /need/ a listnumstyleclass because you can do
-- .templatename .listnumclass .sidebar-list
:addClass(args.listclass)
:cssText(args.liststyle)
:cssText(args['list' .. num .. 'style'])
:wikitext(trimAndAddAutomaticNewline(args['list' .. num]))

contentArgs['content' .. num] = tostring(row)
end
end

for k, v in pairs(contentArgs) do
args[k] = v
end

return p.sidebar(frame, args, cfg.i18n.class.collapse)
end

return p

Module:Message box/ombox.css

2022-08-18T22:32:32Z

Bmueller: 1 revision imported

/* {{pp|small=y}} */
.ombox {
margin: 4px 0;
border-collapse: collapse;
border: 1px solid #a2a9b1; /* Default "notice" gray */
background-color: #f8f9fa;
box-sizing: border-box;
}

/* For the "small=yes" option. */
.ombox.mbox-small {
font-size: 88%;
line-height: 1.25em;
}

.ombox-speedy {
border: 2px solid #b32424; /* Red */
background-color: #fee7e6; /* Pink */
}

.ombox-delete {
border: 2px solid #b32424; /* Red */
}

.ombox-content {
border: 1px solid #f28500; /* Orange */
}

.ombox-style {
border: 1px solid #fc3; /* Yellow */
}

.ombox-move {
border: 1px solid #9932cc; /* Purple */
}

.ombox-protection {
border: 2px solid #a2a9b1; /* Gray-gold */
}

.ombox .mbox-text {
border: none;
/* @noflip */
padding: 0.25em 0.9em;
width: 100%;
}

.ombox .mbox-image {
border: none;
/* @noflip */
padding: 2px 0 2px 0.9em;
text-align: center;
}

.ombox .mbox-imageright {
border: none;
/* @noflip */
padding: 2px 0.9em 2px 0;
text-align: center;
}

/* An empty narrow cell */
.ombox .mbox-empty-cell {
border: none;
padding: 0;
width: 1px;
}

.ombox .mbox-invalid-type {
text-align: center;
}

@media (min-width: 720px) {
.ombox {
margin: 4px 10%;
}

.ombox.mbox-small {
/* @noflip */
clear: right;
/* @noflip */
float: right;
/* @noflip */
margin: 4px 0 4px 1em;
width: 238px;
}
}