Auto-update Tech namespace pages 2024-09-16 09:07:38.199208

miraheze · Sep 16, 2024 · 1677610 · 1677610
1 parent 3d31683
commit 1677610
Show file tree

Hide file tree

Showing 15 changed files with 21 additions and 21 deletions.
diff --git a/content/tech-docs/Tech:Data_Processing_Inventory.md b/content/tech-docs/Tech:Data_Processing_Inventory.md
@@ -18,7 +18,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 |
+| 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 |
 | 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 |

diff --git a/content/tech-docs/Tech:MediaWiki-Compatibility-hi.md b/content/tech-docs/Tech:MediaWiki-Compatibility-hi.md
@@ -5,11 +5,11 @@ title: Tech:MediaWiki/Compatibility/hi
  `{{ {{MediaWiki navigation|compatibility|header=MediaWiki compatibility|description=Miraheze supports a variety of browsers which meet the latest web standards. Their support is fully dependent on upstream support by MediaWiki. Learn more on Miraheze Meta.|keywords=miraheze mediawiki compatibility}} }}` `{{ {{Shortcut|Old}} }}`
 Miraheze उन सभी ब्राउज़रों को समर्थित करता है जो मीडियाविकि के उस संस्करण द्वारा समर्थित है जिसपर Miraheze वर्तमान में चल रहा है (इस समय मीडियाविकि `{{ {{CURRENTVERSION}} }}`)।
 
-Miraheze ब्राउज़रों को तीन श्रेणियों में बाँटता है: ' **क' वर्ग** (आधुनिक ब्राउज़र, पूर्ण समर्थन), ' **ख' वर्ग** (बुनियादी समर्थन), और ' **ग' वर्ग** (अनजान):
+Miraheze ब्राउज़रों को तीन श्रेणियों में बाँटता है: '**क' वर्ग** (आधुनिक ब्राउज़र, पूर्ण समर्थन), '**ख' वर्ग** (बुनियादी समर्थन), और '**ग' वर्ग** (अनजान):
 
-* ' **क' वर्ग** के ब्राउज़रों को मीडियाविकि पूरी तरह से समर्थित करता है और परीक्षण से साबित हुआ है कि वे मीडियाविकि के सभी मूल सुविधाओं को समर्थित करते हैं।
-* ' **ख' वर्ग** के ब्राउज़रों पर कुछ वेब मानक समर्थित नहीं हैं जैसे पुराने ब्राउज़र। मीडियाविकि कुछ सुविधाओं को अक्षम कर देती है ताकि सामग्री को ठीक से प्रदर्शित किया जा सकते मगर उनके पास फिर भी पूर्ण समर्थन नहीं है।
-* ' **ग' वर्ग** के ब्राउज़र वे ब्राउज़र हैं जिनके पास अब समर्थन नहीं है या फिर जिनके उपयोगकर्ताओं की संख्या समर्थन के लिए काफी ज़्यादा कम है। 'ग' वर्ग के ब्राउज़र वे ब्राउज़र हैं जिन्हें 'क' वर्ग के ब्राउज़रों की तरह देखा जाता है यानी कि 'ख' वर्ग के ब्राउज़रों की तरह इनके लिए मीडियाविकि सुविधाओं को अक्षम नहीं करता। ऐसा इसलिए किया गया है ताकि बिना बड़े उपयोगकर्ता-समूह के ब्राउज़रों के उपयोगकर्ताएँ मीडियाविकि का पूरा इस्तेमाल कर पाए।
+* '**क' वर्ग** के ब्राउज़रों को मीडियाविकि पूरी तरह से समर्थित करता है और परीक्षण से साबित हुआ है कि वे मीडियाविकि के सभी मूल सुविधाओं को समर्थित करते हैं।
+* '**ख' वर्ग** के ब्राउज़रों पर कुछ वेब मानक समर्थित नहीं हैं जैसे पुराने ब्राउज़र। मीडियाविकि कुछ सुविधाओं को अक्षम कर देती है ताकि सामग्री को ठीक से प्रदर्शित किया जा सकते मगर उनके पास फिर भी पूर्ण समर्थन नहीं है।
+* '**ग' वर्ग** के ब्राउज़र वे ब्राउज़र हैं जिनके पास अब समर्थन नहीं है या फिर जिनके उपयोगकर्ताओं की संख्या समर्थन के लिए काफी ज़्यादा कम है। 'ग' वर्ग के ब्राउज़र वे ब्राउज़र हैं जिन्हें 'क' वर्ग के ब्राउज़रों की तरह देखा जाता है यानी कि 'ख' वर्ग के ब्राउज़रों की तरह इनके लिए मीडियाविकि सुविधाओं को अक्षम नहीं करता। ऐसा इसलिए किया गया है ताकि बिना बड़े उपयोगकर्ता-समूह के ब्राउज़रों के उपयोगकर्ताएँ मीडियाविकि का पूरा इस्तेमाल कर पाए।
 
 नीचे [MediaWiki.org](https://meta.miraheze.org/wiki/mw:) से एक टेबल है जिसमें लिखा है कि कौन-से ब्राउज़र किस श्रेणी में हैं। `{{ {{mw:Compatibility browser}} }}`
 

diff --git a/content/tech-docs/Tech:SSH_fingerprints.md b/content/tech-docs/Tech:SSH_fingerprints.md
@@ -10,7 +10,7 @@ If you are in doubt during the verification of a fingerprint, please contact a S
 
 This list was generated using `sudo salt-ssh '*' cmd.run '/usr/local/bin/gen_fingerprints'` on the Salt Master. Use Ctrl + F on this page to search for the right hostname.
 
-Date of update: `{{ {{REVISIONYEAR}} }}`- `{{ {{REVISIONMONTH1}} }}`- `{{ {{REVISIONDAY}} }}` <br />
+Date of update: `{{ {{REVISIONYEAR}} }}`- `{{ {{REVISIONMONTH1}} }}`- `{{ {{REVISIONDAY}} }}`<br />
 Updated by: `{{ {{REVISIONUSER}} }}`
 
 ```

diff --git a/content/tech-docs/Tech:Security.md b/content/tech-docs/Tech:Security.md
@@ -16,15 +16,15 @@ Since the creation of the Trust and Safety team in early 2021, the T&S team is p
 
 ### Active threat (Emergency) 
 
-There is an ' **active' threat** when there is evidence that there have recently been attempts (whether successful or not) from a third party to exploit a vulnerability or to attack Miraheze otherwise (DDoS/DoS, etc.).
+There is an '**active' threat** when there is evidence that there have recently been attempts (whether successful or not) from a third party to exploit a vulnerability or to attack Miraheze otherwise (DDoS/DoS, etc.).
 
 Due to their urgent nature, active threats may be dealt with by any SRE member without having to first consult T&S or the Engineering Manager of the relevant team (attempts to contact T&S should always be made first, but if there is no response action may be taken). Any action done by the SRE member should be *temporary* and after it is done the EM and the T&S team should be informed.
 
 **Examples of active threats**: Someone posting code that can be used to exploit something, an active DDoS/DoS attack taking place.
 
 ### Passive threat 
 
-There is a ' **passive' threat** when there is evidence of an existing vulnerability, but there is no evidence of any proof of concept or actual attempt (whether successful or not) to exploit that vulnerability recently. While these are still serious security issues, they are not as urgent as active threats, given the low probability that they will be exploited immediately.
+There is a '**passive' threat** when there is evidence of an existing vulnerability, but there is no evidence of any proof of concept or actual attempt (whether successful or not) to exploit that vulnerability recently. While these are still serious security issues, they are not as urgent as active threats, given the low probability that they will be exploited immediately.
 
 Due to their less urgent nature than active threats, SRE members should only deal with them after an EM or a T&S member (or both) have been consulted (attempts to contact T&S should always be made first, if there is no response the EM should be contacted). Any action done by the SRE member should be *temporary* (unless T&S agrees to a permanent solution) and after it is done the T&S team should be informed (if done on EM approval only).
 

diff --git a/content/tech-docs/Tech:Varnish.md b/content/tech-docs/Tech:Varnish.md
@@ -25,7 +25,7 @@ The [default.vcl](https://github.com/miraheze/puppet/blob/master/modules/varnish
 
 #### varnishadm 
 
-*Root privileges are required for this tool.* <br />
+*Root privileges are required for this tool.*<br />
 varnishadm is a tool that gives you an interactive (non-interactive is possible, but personally not preferred) shell prompt for managing the Varnish process. You can ban objects from the cache, show backends, view backend health, change backend health status and more.
 
 #### varnishlog 
@@ -63,7 +63,7 @@ Using the `X-Miraheze-Debug` header, you can force the request to be passed to a
 
 ## One-off purges (bans) 
 
-*Credit: [https://wikitech.wikimedia.org/wiki/Varnish](https://wikitech.wikimedia.org/wiki/Varnish)* <br />
+*Credit: [https://wikitech.wikimedia.org/wiki/Varnish](https://wikitech.wikimedia.org/wiki/Varnish)*<br />
 Normally, MediaWiki will purge cache objects with the PURGE protocol. However, sometimes you want to purge more than object (or you want an easier way to purge objects across the fleet without using MediaWiki). This can be done using the [banning](https://www.varnish-cache.org/docs/4.0/users-guide/purging.html#bans) feature in varnishadm. Despite its scary name, banning only ensures that all cached objects matching the given criteria (e.g. req.http.Host == meta.miraheze.org) won't be used anymore.
 
 Due to performance concerns, it's recommended that this feature is only used when needed. While Miraheze's appservers can handle the current amount of traffic (warning: this is a dangerous assumption), we should aim for the highest cache hit rate as possible.

diff --git a/content/tech-docs/Tech:Volunteers-bn.md b/content/tech-docs/Tech:Volunteers-bn.md
@@ -17,7 +17,7 @@ The team includes volunteers in technical and less-technical roles, including pr
 ! শেল
 ! গিটহাব
 ! ফোর্জ (অ্যাডমিন)
-! রামনোড <br />এবং <br /> ব্যাকআপসি
+! রামনোড <br />এবং<br /> ব্যাকআপসি
 ! Cloudflare
 ! ডোমেন নিবন্ধক
 ! গ্রাফানা (অ্যাডমিন)

diff --git a/content/tech-docs/Tech:Volunteers-es.md b/content/tech-docs/Tech:Volunteers-es.md
@@ -17,7 +17,7 @@ The team includes volunteers in technical and less-technical roles, including pr
 ! Cáscara
 ! GitHub
 ! Phabricator (admin)
-! RamNode <br />& <br /> OVH
+! RamNode <br />&<br /> OVH
 ! Cloudflare
 ! Registrador de dominios
 ! Grafana (Admin)

diff --git a/content/tech-docs/Tech:Volunteers-fi.md b/content/tech-docs/Tech:Volunteers-fi.md
@@ -17,7 +17,7 @@ The team includes volunteers in technical and less-technical roles, including pr
 ! Palvelimet
 ! GitHub
 ! Phabricator (ylläpitäjä)
-! RamNode <br />& <br /> Backupsy
+! RamNode <br />&<br /> Backupsy
 ! Cloudflare
 ! Verkkotunnuksen rekisteröinti
 ! Grafana (ylläpitäjä)

diff --git a/content/tech-docs/Tech:Volunteers-ja.md b/content/tech-docs/Tech:Volunteers-ja.md
@@ -12,7 +12,7 @@ title: Tech:Volunteers/ja
 |-
 ! class="unsortable"| [ `{{ {{fullurl:Tech:Volunteers/List|action=edit}} }}` +/-]
 ! 名前と権限
-! Libera Chatのニックネーム <br /> [IRC](https://meta.miraheze.org/wiki/Special:MyLanguage/IRC)
+! Libera Chatのニックネーム<br /> [IRC](https://meta.miraheze.org/wiki/Special:MyLanguage/IRC)
 ! メールアドレス
 ! シェル
 ! GitHub

diff --git a/content/tech-docs/Tech:Volunteers-pt-br.md b/content/tech-docs/Tech:Volunteers-pt-br.md
@@ -17,7 +17,7 @@ The team includes volunteers in technical and less-technical roles, including pr
 ! Concha
 ! GitHub
 ! Phabricator (admin)
-! RamNode <br />& <br /> OVH
+! RamNode <br />&<br /> OVH
 ! Cloudflare
 ! Domínio Registrar
 ! Grafana (Admin)

diff --git a/content/tech-docs/Tech:Volunteers-sv.md b/content/tech-docs/Tech:Volunteers-sv.md
@@ -17,7 +17,7 @@ The team includes volunteers in technical and less-technical roles, including pr
 ! Skal
 ! GitHub
 ! Phabricator (admin)
-! RamNode <br />& <br /> OVH
+! RamNode <br />&<br /> OVH
 ! Cloudflare
 ! Domänförvaltare
 ! Grafana (admin)

diff --git a/content/tech-docs/Tech:Volunteers-ur.md b/content/tech-docs/Tech:Volunteers-ur.md
@@ -17,7 +17,7 @@ The team includes volunteers in technical and less-technical roles, including pr
 ! شیل
 ! گٹ ہب
 ! پھبریکیٹر (منتظم)
-! RamNode <br />اور <br /> OVH
+! RamNode <br />اور<br /> OVH
 ! Cloudflare
 ! ڈومین رجسٹرار
 ! گرافانا (ایڈمن)

diff --git a/content/tech-docs/Tech:Volunteers-zh-hans.md b/content/tech-docs/Tech:Volunteers-zh-hans.md
@@ -12,7 +12,7 @@ The team includes volunteers in technical and less-technical roles, including pr
 |-
 ! class="unsortable"| [ `{{ {{fullurl:Tech:Volunteers/List|action=edit}} }}` +/-]
 ! 名称及职位
-! [IRC](https://meta.miraheze.org/wiki/Special:MyLanguage/IRC)上 <br />Libera Chat的昵称
+! [IRC](https://meta.miraheze.org/wiki/Special:MyLanguage/IRC)上<br />Libera Chat的昵称
 ! 电子邮件地址
 ! Shell
 ! GitHub

diff --git a/content/tech-docs/Tech:Volunteers-zh-hant.md b/content/tech-docs/Tech:Volunteers-zh-hant.md
@@ -12,7 +12,7 @@ The team includes volunteers in technical and less-technical roles, including pr
 |-
 ! class="unsortable"| [ `{{ {{fullurl:Tech:Volunteers/List|action=edit}} }}` +/-]
 ! 名稱及職位
-! [IRC](https://meta.miraheze.org/wiki/Special:MyLanguage/IRC)上 <br />Libera Chat的暱稱
+! [IRC](https://meta.miraheze.org/wiki/Special:MyLanguage/IRC)上<br />Libera Chat的暱稱
 ! 電子郵件地址
 ! Shell
 ! GitHub

diff --git a/content/tech-docs/Tech:Volunteers-zh-hk.md b/content/tech-docs/Tech:Volunteers-zh-hk.md
@@ -12,12 +12,12 @@ The team includes volunteers in technical and less-technical roles, including pr
 |-
 ! class="unsortable"| [ `{{ {{fullurl:Tech:Volunteers/List|action=edit}} }}` +/-]
 ! 名稱及職位
-! [IRC](https://meta.miraheze.org/wiki/Special:MyLanguage/IRC)上 <br />Libera Chat的暱稱
+! [IRC](https://meta.miraheze.org/wiki/Special:MyLanguage/IRC)上<br />Libera Chat的暱稱
 ! 電子郵件地址
 ! Shell
 ! GitHub
 ! Phabricator（管理員）
-! RamNode <br />和 <br />OVH
+! RamNode<br />和<br />OVH
 ! Cloudflare
 ! 域名註冊方
 ! Grafana（管理員）