Auto-update Tech namespace pages 2024-09-19 21:27:31.087816

miraheze · Sep 19, 2024 · 26a25c2 · 26a25c2
1 parent ab55969
commit 26a25c2
Show file tree

Hide file tree

Showing 186 changed files with 406 additions and 25 deletions.
diff --git a/content/tech-docs/Tech:2018_Infrastructure_Assessment.md b/content/tech-docs/Tech:2018_Infrastructure_Assessment.md
@@ -26,5 +26,7 @@ This is a page designed to be a working ground for analysing the infrastructure
 | [lizardfs2](https://meta.miraheze.org/wiki/Tech:lizardfs2) | Static | lizardfs, salt-minion, bacula-client | 2x2.30GHz | 150G | 512MB | $4.85 |
 | [test1](https://meta.miraheze.org/wiki/Tech:test1) | Testing | mediawiki, salt-minion | CPU: 1x2.40GHz | 40G | 1GB | $3.50 |
 
+
+
 ----
 **[Go to Source &rarr;](https://meta.miraheze.org/wiki/Tech:2018_Infrastructure_Assessment)**
diff --git a/content/tech-docs/Tech:Adding_a_new_extension.md b/content/tech-docs/Tech:Adding_a_new_extension.md
@@ -29,5 +29,7 @@ It should be noted that it is a good idea to add any configuration variable the
 * [Category:Guides](https://meta.miraheze.org/wiki/Category:Guides)
 * [Category:Technology guidelines and guides](https://meta.miraheze.org/wiki/Category:Technology_guidelines_and_guides)
 
+
+
 ----
 **[Go to Source &rarr;](https://meta.miraheze.org/wiki/Tech:Adding_a_new_extension)**
diff --git a/content/tech-docs/Tech:Appointment_and_revocation_policy.md b/content/tech-docs/Tech:Appointment_and_revocation_policy.md
@@ -63,5 +63,7 @@ If you already have a shell account and want to get extra privileges (or are req
 
 * [Category:Tech](https://meta.miraheze.org/wiki/Category:Tech)
 
+
+
 ----
 **[Go to Source &rarr;](https://meta.miraheze.org/wiki/Tech:Appointment_and_revocation_policy)**
diff --git a/content/tech-docs/Tech:Bast161.md b/content/tech-docs/Tech:Bast161.md
@@ -22,5 +22,7 @@ title: Tech:Bast161
 
 **bast161** is a FiberState server in Salt Lake City, Utah running Debian Bookworm.
 
+
+
 ----
 **[Go to Source &rarr;](https://meta.miraheze.org/wiki/Tech:Bast161)**
diff --git a/content/tech-docs/Tech:Bast181.md b/content/tech-docs/Tech:Bast181.md
@@ -22,5 +22,7 @@ title: Tech:Bast181
 
 **bast181** is a FiberState server in Salt Lake City, Utah running Debian Bookworm.
 
+
+
 ----
 **[Go to Source &rarr;](https://meta.miraheze.org/wiki/Tech:Bast181)**
diff --git a/content/tech-docs/Tech:CSP_Policy.md b/content/tech-docs/Tech:CSP_Policy.md
@@ -34,5 +34,7 @@ In the event of a dispute or situation not covered by this policy, the Director
 
 * [Category:Tech policy](https://meta.miraheze.org/wiki/Category:Tech_policy)
 
+
+
 ----
 **[Go to Source &rarr;](https://meta.miraheze.org/wiki/Tech:CSP_Policy)**
diff --git a/content/tech-docs/Tech:Cloud15.md b/content/tech-docs/Tech:Cloud15.md
@@ -21,5 +21,7 @@ title: Tech:Cloud15
 
 **cloud15** is a FiberState bare metal dedicated server in Salt Lake City, Utah running Debian Bookworm. It is a [virtualization host server](/tech-docs/techproxmox).
 
+
+
 ----
 **[Go to Source &rarr;](https://meta.miraheze.org/wiki/Tech:Cloud15)**
diff --git a/content/tech-docs/Tech:Cloud16.md b/content/tech-docs/Tech:Cloud16.md
@@ -21,5 +21,7 @@ title: Tech:Cloud16
 
 **cloud16** is a FiberState bare metal dedicated server in Salt Lake City, Utah running Debian Bookworm. It is a [virtualization host server](/tech-docs/techproxmox).
 
+
+
 ----
 **[Go to Source &rarr;](https://meta.miraheze.org/wiki/Tech:Cloud16)**
diff --git a/content/tech-docs/Tech:Cloud17.md b/content/tech-docs/Tech:Cloud17.md
@@ -21,5 +21,7 @@ title: Tech:Cloud17
 
 **cloud17** is a FiberState bare metal dedicated server in Salt Lake City, Utah running Debian Bookworm. It is a [virtualization host server](/tech-docs/techproxmox).
 
+
+
 ----
 **[Go to Source &rarr;](https://meta.miraheze.org/wiki/Tech:Cloud17)**
diff --git a/content/tech-docs/Tech:Cloud18.md b/content/tech-docs/Tech:Cloud18.md
@@ -21,5 +21,7 @@ title: Tech:Cloud18
 
 **cloud18** is a FiberState bare metal dedicated server in Salt Lake City, Utah running Debian Bookworm. It is a [virtualization host server](/tech-docs/techproxmox).
 
+
+
 ----
 **[Go to Source &rarr;](https://meta.miraheze.org/wiki/Tech:Cloud18)**
diff --git a/content/tech-docs/Tech:Cloud_Server_Comparison.md b/content/tech-docs/Tech:Cloud_Server_Comparison.md
@@ -31,5 +31,7 @@ This is as a good as direct comparsion but is expected to show the reasonable eq
 | [test1](https://meta.miraheze.org/wiki/Tech:test1) | test2 | cloud2 | Paladox | `{{ {{done | migrated}} }}` |
 | [lizardfs6](https://meta.miraheze.org/wiki/Tech:lizardfs6) | gluster1 | cloud2 | Paladox | `{{ {{done}} }}` |
 
+
+
 ----
 **[Go to Source &rarr;](https://meta.miraheze.org/wiki/Tech:Cloud_Server_Comparison)**
diff --git a/content/tech-docs/Tech:Cloudflare.md b/content/tech-docs/Tech:Cloudflare.md
@@ -21,5 +21,7 @@ Keep in mind that this check is done over HTTPS and that Cloudflare is verifying
 * Go to the end of the endpoints section, and click "Add Endpoint". Input the server name, public IPv6 address and a weight of 1, **unless** you have a reason to give it a separate weight value.
 * Click save at the bottom of the page and you're done.
 
+
+
 ----
 **[Go to Source &rarr;](https://meta.miraheze.org/wiki/Tech:Cloudflare)**
diff --git a/content/tech-docs/Tech:Communication.md b/content/tech-docs/Tech:Communication.md
@@ -33,5 +33,7 @@ Not all channels are made the same. Some, like on-wiki sitenotices, are very int
 
 For example, while sitenotices are intrusive, you ensure that everyone on a Miraheze wiki at that time knows what's going on. Therefore, these are better reserved for farm-wide issues in the case of global sitenotices, or for extensions disabled due to security issues, in the case of targeted sitenotices.
 
+
+
 ----
 **[Go to Source &rarr;](https://meta.miraheze.org/wiki/Tech:Communication)**
diff --git a/content/tech-docs/Tech:Compromised_Handling.md b/content/tech-docs/Tech:Compromised_Handling.md
@@ -94,5 +94,7 @@ Under EU law, we're required to notify all European users in the event of a brea
 * [Category:Tech](https://meta.miraheze.org/wiki/Category:Tech)
 * [Category:Technology guidelines and guides](https://meta.miraheze.org/wiki/Category:Technology_guidelines_and_guides)
 
+
+
 ----
 **[Go to Source &rarr;](https://meta.miraheze.org/wiki/Tech:Compromised_Handling)**
diff --git a/content/tech-docs/Tech:Conduct_Policy.md b/content/tech-docs/Tech:Conduct_Policy.md
@@ -37,5 +37,7 @@ Failure to adhere to this conduct policy may result in disciplinary action, up t
 * [Category:Tech](https://meta.miraheze.org/wiki/Category:Tech)
 * [Category:Tech policy](https://meta.miraheze.org/wiki/Category:Tech_policy)
 
+
+
 ----
 **[Go to Source &rarr;](https://meta.miraheze.org/wiki/Tech:Conduct_Policy)**
diff --git a/content/tech-docs/Tech:DNS.md b/content/tech-docs/Tech:DNS.md
@@ -26,5 +26,7 @@ The system should be moved to manual at some point, though there is not enough r
 
 * [Category:Services](https://meta.miraheze.org/wiki/Category:Services)
 
+
+
 ----
 **[Go to Source &rarr;](https://meta.miraheze.org/wiki/Tech:DNS)**
diff --git a/content/tech-docs/Tech:Data_Processing_Inventory.md b/content/tech-docs/Tech:Data_Processing_Inventory.md
@@ -19,7 +19,7 @@ At the [Board meeting of October 23, 2020](https://meta.miraheze.org/wiki/Board/
 | Data type | Subjects | Legal basis | Retention date | Processors |
 | --- | --- | --- | --- | --- |
 | IP address | Editors, readers | Anonymous editors: consent<br />CheckUser (registered editor): legitimate interests | Anonymous editing: indefinite (attribution mandatory by licensing)<br />CheckUser (registered editor): up to 90 days | DigitalOcean, OVH, RamNode |
-| Usernames | Registered editors | Consent (account may not be required <sub>(*reference:* Communities may require registration prior to reading and editing, but Miraheze Limited commits to information access without prior registration.)</sub>) | Indefinite (until account has been renamed or deleted by user or per GDPR request <sub>(*reference:* Due to attribution requirements by licensing, user accounts will not be erased, but accounts will be renamed to apply [pseudonymisation](https://en.wikipedia.org/wiki/Pseudonymization).)</sub>) | DigitalOcean, OVH, RamNode |
+| Usernames | Registered editors | Consent (account may not be required [^3]) | Indefinite (until account has been renamed or deleted by user or per GDPR request [^4]) | DigitalOcean, OVH, RamNode |
 | Password | Registered users | Legitimate interests (account security) | Indefinite (until changed or removed by user or per GDPR request) | DigitalOcean, OVH, RamNode |
 | Email address | Registered users | Consent (not required upon registration), legitimate interests (account security / password reset) | Indefinite (until removed or changed by user or per GDPR request) | DigitalOcean, OVH, RamNode |
 | Optional user information (e.g. a user page, real name) | Editors | Consent | Indefinite (until edited or removed by user or per GDPR request) | DigitalOcean, OVH, RamNode |
@@ -34,9 +34,16 @@ At the [Board meeting of October 23, 2020](https://meta.miraheze.org/wiki/Board/
 
 * Anonymous: user without an account
 * Registered: user with an account
-* Editors: anonymous or registered users, editing wiki content <sub>(*reference:* All editors are readers, but not all readers are editors.)</sub>
+* Editors: anonymous or registered users, editing wiki content [^5]
 * Readers: anonymous or registered users, reading wiki content
 
 
+[^1]: Communities may require registration prior to reading and editing, but Miraheze Limited commits to information access without prior registration.
+[^2]: Due to attribution requirements by licensing, user accounts will not be erased, but accounts will be renamed to apply [pseudonymisation](https://en.wikipedia.org/wiki/Pseudonymization).
+[^3]: Communities may require registration prior to reading and editing, but Miraheze Limited commits to information access without prior registration.
+[^4]: Due to attribution requirements by licensing, user accounts will not be erased, but accounts will be renamed to apply [pseudonymisation](https://en.wikipedia.org/wiki/Pseudonymization).
+[^5]: All editors are readers, but not all readers are editors.
+
+
 ----
 **[Go to Source &rarr;](https://meta.miraheze.org/wiki/Tech:Data_Processing_Inventory)**
diff --git a/content/tech-docs/Tech:Db151.md b/content/tech-docs/Tech:Db151.md
@@ -22,5 +22,7 @@ title: Tech:Db151
 
 **db151** is a FiberState server in Salt Lake City, Utah running Debian Bookworm. It is a Database server running [MariaDB](/tech-docs/techmariadb).
 
+
+
 ----
 **[Go to Source &rarr;](https://meta.miraheze.org/wiki/Tech:Db151)**
diff --git a/content/tech-docs/Tech:Db161.md b/content/tech-docs/Tech:Db161.md
@@ -22,5 +22,7 @@ title: Tech:Db161
 
 **db161** is a FiberState server in Salt Lake City, Utah running Debian Bookworm. It is a Database server running [MariaDB](/tech-docs/techmariadb).
 
+
+
 ----
 **[Go to Source &rarr;](https://meta.miraheze.org/wiki/Tech:Db161)**
diff --git a/content/tech-docs/Tech:Db171.md b/content/tech-docs/Tech:Db171.md
@@ -22,5 +22,7 @@ title: Tech:Db171
 
 **db171** is a FiberState server in Salt Lake City, Utah running Debian Bookworm. It is a Database server running [MariaDB](/tech-docs/techmariadb).
 
+
+
 ----
 **[Go to Source &rarr;](https://meta.miraheze.org/wiki/Tech:Db171)**
diff --git a/content/tech-docs/Tech:Db181.md b/content/tech-docs/Tech:Db181.md
@@ -22,5 +22,7 @@ title: Tech:Db181
 
 **db181** is a FiberState server in Salt Lake City, Utah running Debian Bookworm. It is a Database server running [MariaDB](/tech-docs/techmariadb).
 
+
+
 ----
 **[Go to Source &rarr;](https://meta.miraheze.org/wiki/Tech:Db181)**
diff --git a/content/tech-docs/Tech:Db182.md b/content/tech-docs/Tech:Db182.md
@@ -22,5 +22,7 @@ title: Tech:Db182
 
 **db182** is a FiberState server in Salt Lake City, Utah running Debian Bookworm. It is a Database server running [MariaDB](/tech-docs/techmariadb). It currently only hosts non-MediaWiki databases.
 
+
+
 ----
 **[Go to Source &rarr;](https://meta.miraheze.org/wiki/Tech:Db182)**
diff --git a/content/tech-docs/Tech:Delete_a_wiki.md b/content/tech-docs/Tech:Delete_a_wiki.md
@@ -21,5 +21,7 @@ Performing the deletion if 14 days have **not** passed:
 
 * [Category:Technology guidelines and guides](https://meta.miraheze.org/wiki/Category:Technology_guidelines_and_guides)
 
+
+
 ----
 **[Go to Source &rarr;](https://meta.miraheze.org/wiki/Tech:Delete_a_wiki)**
diff --git a/content/tech-docs/Tech:Deleting_Echo_notifications.md b/content/tech-docs/Tech:Deleting_Echo_notifications.md
@@ -13,5 +13,7 @@ While quite a rare occurrence, it sometimes happens that a user is left with glo
 
 * [Category:Technology guidelines and guides](https://meta.miraheze.org/wiki/Category:Technology_guidelines_and_guides)
 
+
+
 ----
 **[Go to Source &rarr;](https://meta.miraheze.org/wiki/Tech:Deleting_Echo_notifications)**
diff --git a/content/tech-docs/Tech:Deleting_and_moving_batches_of_pages_on_a_wiki.md b/content/tech-docs/Tech:Deleting_and_moving_batches_of_pages_on_a_wiki.md
@@ -16,5 +16,7 @@ To delete or move large batches of pages on a wiki, execute the following comman
 
 * [Category:Technology guidelines and guides](https://meta.miraheze.org/wiki/Category:Technology_guidelines_and_guides)
 
+
+
 ----
 **[Go to Source &rarr;](https://meta.miraheze.org/wiki/Tech:Deleting_and_moving_batches_of_pages_on_a_wiki)**
diff --git a/content/tech-docs/Tech:Deployment_Policy.md b/content/tech-docs/Tech:Deployment_Policy.md
@@ -36,5 +36,7 @@ The final say with any deployment rests with the deployer. It is perfectly accep
 
 Press space to (un)select and enter to run.
 
+
+
 ----
 **[Go to Source &rarr;](https://meta.miraheze.org/wiki/Tech:Deployment_Policy)**
diff --git a/content/tech-docs/Tech:Experimental_Wikis.md b/content/tech-docs/Tech:Experimental_Wikis.md
@@ -18,5 +18,7 @@ The following features are enabled on experimental wikis:
 * [Parser Media Structure changes](https://www.mediawiki.org/wiki/Parsing/Media_structure)
 * [JQuery Migrate](https://github.com/jquery/jquery-migrate) (now disabled)
 
+
+
 ----
 **[Go to Source &rarr;](https://meta.miraheze.org/wiki/Tech:Experimental_Wikis)**
diff --git a/content/tech-docs/Tech:FIDO2_SSH.md b/content/tech-docs/Tech:FIDO2_SSH.md
@@ -38,5 +38,7 @@ Ignore this warning at your own peril: If your key stops working, it could becom
    * Miraheze: WebAuthn is available as one of the two possible second factors.
 * [Pisces's guide to get it working on Windows](https://meta.miraheze.org/wiki/User:Pisces/FIDO2_SSH_on_Windows)
 
+
+
 ----
 **[Go to Source &rarr;](https://meta.miraheze.org/wiki/Tech:FIDO2_SSH)**
diff --git a/content/tech-docs/Tech:Fixing_slot_roles_and_content_models.md b/content/tech-docs/Tech:Fixing_slot_roles_and_content_models.md
@@ -37,5 +37,7 @@ After running that make sure you exit shell.php or sql.php (if using) and rerun
 * [Category:Tech](https://meta.miraheze.org/wiki/Category:Tech)
 * [Category:Technology guidelines and guides](https://meta.miraheze.org/wiki/Category:Technology_guidelines_and_guides)
 
+
+
 ----
 **[Go to Source &rarr;](https://meta.miraheze.org/wiki/Tech:Fixing_slot_roles_and_content_models)**
diff --git a/content/tech-docs/Tech:GHSA-Written_Security_Disclosure_Template.md b/content/tech-docs/Tech:GHSA-Written_Security_Disclosure_Template.md
@@ -32,5 +32,7 @@ title: Tech:GHSA/Written Security Disclosure Template
 
 Any further questions that a user wishes to keep private can be sent to sre `{{ {{@}} }}`miraheze.org and we will respond in due course.
 
+
+
 ----
 **[Go to Source &rarr;](https://meta.miraheze.org/wiki/Tech:GHSA/Written_Security_Disclosure_Template)**
diff --git a/content/tech-docs/Tech:GHSA.md b/content/tech-docs/Tech:GHSA.md
@@ -81,5 +81,7 @@ If you need to create an advisory, follow the steps below:
 
 * [Category:Technology guidelines and guides](https://meta.miraheze.org/wiki/Category:Technology_guidelines_and_guides)
 
+
+
 ----
 **[Go to Source &rarr;](https://meta.miraheze.org/wiki/Tech:GHSA)**
Original file line number	Diff line number	Diff line change
Expand Up		@@ -63,5 +63,7 @@ If you already have a shell account and want to get extra privileges (or are req

		* [Category:Tech](https://meta.miraheze.org/wiki/Category:Tech)



		----
		[Go to Source →](https://meta.miraheze.org/wiki/Tech:Appointment_and_revocation_policy)
Original file line number	Diff line number	Diff line change
Expand Up		@@ -22,5 +22,7 @@ title: Tech:Bast161

		bast161 is a FiberState server in Salt Lake City, Utah running Debian Bookworm.



		----
		[Go to Source →](https://meta.miraheze.org/wiki/Tech:Bast161)
Original file line number	Diff line number	Diff line change
Expand Up		@@ -22,5 +22,7 @@ title: Tech:Bast181

		bast181 is a FiberState server in Salt Lake City, Utah running Debian Bookworm.



		----
		[Go to Source →](https://meta.miraheze.org/wiki/Tech:Bast181)
Original file line number	Diff line number	Diff line change
Expand Up		@@ -34,5 +34,7 @@ In the event of a dispute or situation not covered by this policy, the Director

		* [Category:Tech policy](https://meta.miraheze.org/wiki/Category:Tech_policy)



		----
		[Go to Source →](https://meta.miraheze.org/wiki/Tech:CSP_Policy)
Original file line number	Diff line number	Diff line change
Expand Up		@@ -21,5 +21,7 @@ title: Tech:Cloud15

		cloud15 is a FiberState bare metal dedicated server in Salt Lake City, Utah running Debian Bookworm. It is a [virtualization host server](/tech-docs/techproxmox).



		----
		[Go to Source →](https://meta.miraheze.org/wiki/Tech:Cloud15)
Original file line number	Diff line number	Diff line change
Expand Up		@@ -21,5 +21,7 @@ title: Tech:Cloud16

		cloud16 is a FiberState bare metal dedicated server in Salt Lake City, Utah running Debian Bookworm. It is a [virtualization host server](/tech-docs/techproxmox).



		----
		[Go to Source →](https://meta.miraheze.org/wiki/Tech:Cloud16)
Original file line number	Diff line number	Diff line change
Expand Up		@@ -21,5 +21,7 @@ title: Tech:Cloud17

		cloud17 is a FiberState bare metal dedicated server in Salt Lake City, Utah running Debian Bookworm. It is a [virtualization host server](/tech-docs/techproxmox).



		----
		[Go to Source →](https://meta.miraheze.org/wiki/Tech:Cloud17)
Original file line number	Diff line number	Diff line change
Expand Up		@@ -21,5 +21,7 @@ title: Tech:Cloud18

		cloud18 is a FiberState bare metal dedicated server in Salt Lake City, Utah running Debian Bookworm. It is a [virtualization host server](/tech-docs/techproxmox).



		----
		[Go to Source →](https://meta.miraheze.org/wiki/Tech:Cloud18)
Original file line number	Diff line number	Diff line change
Expand Up		@@ -33,5 +33,7 @@ Not all channels are made the same. Some, like on-wiki sitenotices, are very int

		For example, while sitenotices are intrusive, you ensure that everyone on a Miraheze wiki at that time knows what's going on. Therefore, these are better reserved for farm-wide issues in the case of global sitenotices, or for extensions disabled due to security issues, in the case of targeted sitenotices.



		----
		[Go to Source →](https://meta.miraheze.org/wiki/Tech:Communication)
Original file line number	Diff line number	Diff line change
Expand Up		@@ -26,5 +26,7 @@ The system should be moved to manual at some point, though there is not enough r

		* [Category:Services](https://meta.miraheze.org/wiki/Category:Services)



		----
		[Go to Source →](https://meta.miraheze.org/wiki/Tech:DNS)