mirror of
https://github.com/privacyguides/i18n.git
synced 2025-06-16 07:51:13 +00:00
New Crowdin translations by GitHub Action
This commit is contained in:
Crowdin Bot
parent
22939f70d2
commit
6a7f2be4ae
@ -72,6 +72,10 @@ We have sometimes found that the syntax for inserting an image like above was mi
|
||||
|
||||
For examples like the above admonitions, quotation marks, e.g.: `" "` must be used to specify string text. MkDocs will not correctly interpret other symbols i.e., `「 」` or `« »`. Other punctuation marks are fine for marking regular quotations within the text otherwise.
|
||||
|
||||
## Brackets
|
||||
## Fullwidth alternatives and Markdown syntax
|
||||
|
||||
Markdown links must use brackets i.e. `[Example link](https://example.com)`. CJK style brackets such as `（ ）` will not work for links. Crowdin will often handle links automatically, but you may encounter these links inside admonitions and other customized blocks of text.
|
||||
CJK writing systems tend to use alternative "fullwidth" variants of common symbols. These are different characters and cannot be used for markdown syntax.
|
||||
|
||||
- Links must use regular parenthesis ie `(` (Left Parenthesis U+0028) and `)` (Right Parenthesis U+0029) and not `（` (Fullwidth Left Parenthesis U+FF08) or `）` (Fullwidth Right Parenthesis U+FF09)
|
||||
- Indented quoted text must use `:` (Colon U+003A) and not `：` (Fullwidth Colon U+FF1A)
|
||||
- Pictures must use `!` (Exclamation Mark U+0021) and not `！` (Fullwidth Exclamation Mark U+FF01)
|
||||
|
||||
@ -72,6 +72,10 @@ We have sometimes found that the syntax for inserting an image like above was mi
|
||||
|
||||
For examples like the above admonitions, quotation marks, e.g.: `" "` must be used to specify string text. MkDocs will not correctly interpret other symbols i.e., `「 」` or `« »`. Other punctuation marks are fine for marking regular quotations within the text otherwise.
|
||||
|
||||
## Brackets
|
||||
## Fullwidth alternatives and Markdown syntax
|
||||
|
||||
Markdown links must use brackets i.e. `[Example link](https://example.com)`. CJK style brackets such as `（ ）` will not work for links. Crowdin will often handle links automatically, but you may encounter these links inside admonitions and other customized blocks of text.
|
||||
CJK writing systems tend to use alternative "fullwidth" variants of common symbols. These are different characters and cannot be used for markdown syntax.
|
||||
|
||||
- Links must use regular parenthesis ie `(` (Left Parenthesis U+0028) and `)` (Right Parenthesis U+0029) and not `（` (Fullwidth Left Parenthesis U+FF08) or `）` (Fullwidth Right Parenthesis U+FF09)
|
||||
- Indented quoted text must use `:` (Colon U+003A) and not `：` (Fullwidth Colon U+FF1A)
|
||||
- Pictures must use `!` (Exclamation Mark U+0021) and not `！` (Fullwidth Exclamation Mark U+FF01)
|
||||
|
||||
@ -72,6 +72,10 @@ We have sometimes found that the syntax for inserting an image like above was mi
|
||||
|
||||
For examples like the above admonitions, quotation marks, e.g.: `" "` must be used to specify string text. MkDocs will not correctly interpret other symbols i.e., `「 」` or `« »`. Other punctuation marks are fine for marking regular quotations within the text otherwise.
|
||||
|
||||
## Brackets
|
||||
## Fullwidth alternatives and Markdown syntax
|
||||
|
||||
Markdown links must use brackets i.e. `[Example link](https://example.com)`. CJK style brackets such as `（ ）` will not work for links. Crowdin will often handle links automatically, but you may encounter these links inside admonitions and other customized blocks of text.
|
||||
CJK writing systems tend to use alternative "fullwidth" variants of common symbols. These are different characters and cannot be used for markdown syntax.
|
||||
|
||||
- Links must use regular parenthesis ie `(` (Left Parenthesis U+0028) and `)` (Right Parenthesis U+0029) and not `（` (Fullwidth Left Parenthesis U+FF08) or `）` (Fullwidth Right Parenthesis U+FF09)
|
||||
- Indented quoted text must use `:` (Colon U+003A) and not `：` (Fullwidth Colon U+FF1A)
|
||||
- Pictures must use `!` (Exclamation Mark U+0021) and not `！` (Fullwidth Exclamation Mark U+FF01)
|
||||
|
||||
@ -12,9 +12,9 @@ Wenn du eine Website besuchst, wird eine numerische Adresse zurückgegeben. Wenn
|
||||
|
||||
DNS gibt es schon seit den [Anfängen des Internets](https://de.wikipedia.org/wiki/Domain_Name_System#%C3%9Cberblick). DNS-Anfragen an und von DNS-Servern werden im Allgemeinen **nicht** verschlüsselt. In einer privaten Umgebung erhält der Kunde die Server vom Internetanbieter über [DHCP](https://de.wikipedia.org/wiki/Dynamic_Host_Configuration_Protocol).
|
||||
|
||||
Unverschlüsselte DNS-Anfragen können während der Übertragung leicht **überwacht** und **verändert** werden. In some parts of the world, ISPs are ordered to do primitive [DNS filtering](https://en.wikipedia.org/wiki/DNS_blocking). Wenn du die IP-Adresse einer gesperrten Domain anforderst, kann es sein, dass der Server nicht oder mit einer anderen IP-Adresse antwortet. Da das DNS-Protokoll nicht verschlüsselt ist, kann der Internetanbieter (oder jeder andere Netzbetreiber) [DPI](https://de.wikipedia.org/wiki/Deep_Packet_Inspection) einsetzen, um Anfragen zu überwachen. Internetanbieter können Anfragen auch auf der Grundlage gemeinsamer Merkmale blockieren, unabhängig davon, welcher DNS-Server verwendet wird. Beim unverschlüsselten DNS wird immer [Port](https://de.wikipedia.org/wiki/Port_(Protokoll)) 53 und UDP verwendet.
|
||||
Unverschlüsselte DNS-Anfragen können während der Übertragung leicht **überwacht** und **verändert** werden. In einigen Teilen der Welt werden Internetanbieter angewiesen, primitive [DNS-Filterung](https://en.wikipedia.org/wiki/DNS_blocking)durchzuführen. Wenn du die IP-Adresse einer gesperrten Domain anforderst, kann es sein, dass der Server nicht oder mit einer anderen IP-Adresse antwortet. Da das DNS-Protokoll nicht verschlüsselt ist, kann der Internetanbieter (oder jeder andere Netzbetreiber) [DPI](https://de.wikipedia.org/wiki/Deep_Packet_Inspection) einsetzen, um Anfragen zu überwachen. Internetanbieter können Anfragen auch auf der Grundlage gemeinsamer Merkmale blockieren, unabhängig davon, welcher DNS-Server verwendet wird. Beim unverschlüsselten DNS wird immer [Port](https://de.wikipedia.org/wiki/Port_(Protokoll)) 53 und UDP verwendet.
|
||||
|
||||
Below, we discuss and provide a tutorial to prove what an outside observer may see using regular unencrypted DNS and [encrypted DNS](#what-is-encrypted-dns).
|
||||
Im Folgenden erörtern wir, was ein außenstehender Beobachter mit Hilfe von normalem unverschlüsseltem DNS und [verschlüsseltem DNS](#what-is-encrypted-dns)sehen kann, und stellen eine Anleitung dazu zur Verfügung.
|
||||
|
||||
### Unverschlüsselter DNS
|
||||
|
||||
@ -24,7 +24,7 @@ Below, we discuss and provide a tutorial to prove what an outside observer may s
|
||||
tshark -w /tmp/dns.pcap udp port 53 and host 1.1.1.1 or host 8.8.8.8
|
||||
```
|
||||
|
||||
2. We can then use [`dig`](https://en.wikipedia.org/wiki/Dig_(command)) (Linux, MacOS, etc.) or [`nslookup`](https://en.wikipedia.org/wiki/Nslookup) (Windows) to send the DNS lookup to both servers. Software such as web browsers do these lookups automatically, unless they are configured to use encrypted DNS.
|
||||
2. Wir können dann [`dig`](https://en.wikipedia.org/wiki/Dig_(command)) (Linux, MacOS, etc.) oder [`nslookup`](https://en.wikipedia.org/wiki/Nslookup) (Windows) verwenden, um den DNS-Lookup an beide Server zu senden. Software wie Webbrowser führen diese Nachschläge automatisch durch, sofern sie nicht für die Verwendung von verschlüsseltem DNS konfiguriert sind.
|
||||
|
||||
=== "Linux, macOS"
|
||||
|
||||
@ -39,7 +39,7 @@ Below, we discuss and provide a tutorial to prove what an outside observer may s
|
||||
nslookup privacyguides.org 8.8.8.8
|
||||
```
|
||||
|
||||
3. Next, we want to [analyse](https://www.wireshark.org/docs/wsug_html_chunked/ChapterIntroduction.html#ChIntroWhatIs) the results:
|
||||
3. Als Nächstes wollen wir die Ergebnisse [analysieren](https://www.wireshark.org/docs/wsug_html_chunked/ChapterIntroduction.html#ChIntroWhatIs):
|
||||
|
||||
=== "Wireshark"
|
||||
|
||||
@ -53,24 +53,24 @@ Below, we discuss and provide a tutorial to prove what an outside observer may s
|
||||
tshark -r /tmp/dns.pcap
|
||||
```
|
||||
|
||||
If you run the Wireshark command above, the top pane shows the "[frames](https://en.wikipedia.org/wiki/Ethernet_frame)", and the bottom pane shows all the data about the selected frame. Enterprise filtering and monitoring solutions (such as those purchased by governments) can do the process automatically, without human interaction, and can aggregate those frames to produce statistical data useful to the network observer.
|
||||
Wenn Sie den obigen Wireshark-Befehl ausführen, zeigt das obere Fenster die "[frames](https://en.wikipedia.org/wiki/Ethernet_frame)", und das untere Fenster zeigt alle Daten über den ausgewählten Frame. Filter- und Überwachungslösungen für Unternehmen (z. B. solche, die von Regierungen gekauft werden) können den Prozess automatisch und ohne menschliche Interaktion durchführen und diese Frames zusammenfassen, um statistische Daten zu erzeugen, die für den Netzwerkbeobachter nützlich sind.
|
||||
|
||||
| No. | Time | Source | Destination | Protocol | Length | Info |
|
||||
| --- | -------- | --------- | ----------- | -------- | ------ | ---------------------------------------------------------------------- |
|
||||
| 1 | 0.000000 | 192.0.2.1 | 1.1.1.1 | DNS | 104 | Standard query 0x58ba A privacyguides.org OPT |
|
||||
| 2 | 0.293395 | 1.1.1.1 | 192.0.2.1 | DNS | 108 | Standard query response 0x58ba A privacyguides.org A 198.98.54.105 OPT |
|
||||
| 3 | 1.682109 | 192.0.2.1 | 8.8.8.8 | DNS | 104 | Standard query 0xf1a9 A privacyguides.org OPT |
|
||||
| 4 | 2.154698 | 8.8.8.8 | 192.0.2.1 | DNS | 108 | Standard query response 0xf1a9 A privacyguides.org A 198.98.54.105 OPT |
|
||||
| Nr. | Zeit | Quelle | Ziel | Protokoll | Größe | Info |
|
||||
| --- | -------- | --------- | --------- | --------- | ----- | ---------------------------------------------------------------------- |
|
||||
| 1 | 0.000000 | 192.0.2.1 | 1.1.1.1 | DNS | 104 | Standardabfrage 0x58ba A privacyguides.org OPT |
|
||||
| 2 | 0.293395 | 1.1.1.1 | 192.0.2.1 | DNS | 108 | Standard-Abfrageantwort 0x58ba A privacyguides.org A 198.98.54.105 OPT |
|
||||
| 3 | 1.682109 | 192.0.2.1 | 8.8.8.8 | DNS | 104 | Standardabfrage 0xf1a9 A privacyguides.org OPT |
|
||||
| 4 | 2.154698 | 8.8.8.8 | 192.0.2.1 | DNS | 108 | Standard-Abfrageantwort 0xf1a9 A privacyguides.org A 198.98.54.105 OPT |
|
||||
|
||||
An observer could modify any of these packets.
|
||||
Ein Beobachter könnte jedes dieser Pakete verändern.
|
||||
|
||||
## What is "encrypted DNS"?
|
||||
## Was ist ein "verschlüsseltes DNS"?
|
||||
|
||||
Encrypted DNS can refer to one of a number of protocols, the most common ones being:
|
||||
Verschlüsseltes DNS kann sich auf eine Reihe von Protokollen beziehen, von denen die gängigsten sind:
|
||||
|
||||
### DNSCrypt
|
||||
|
||||
[**DNSCrypt**](https://en.wikipedia.org/wiki/DNSCrypt) was one of the first methods of encrypting DNS queries. DNSCrypt operates on port 443 and works with both the TCP or UDP transport protocols. DNSCrypt has never been submitted to the [Internet Engineering Task Force (IETF)](https://en.wikipedia.org/wiki/Internet_Engineering_Task_Force) nor has it gone through the [Request for Comments (RFC)](https://en.wikipedia.org/wiki/Request_for_Comments) process, so it has not been used widely outside of a few [implementations](https://dnscrypt.info/implementations). As a result, it has been largely replaced by the more popular [DNS over HTTPS](#dns-over-https-doh).
|
||||
[**DNSCrypt**](https://en.wikipedia.org/wiki/DNSCrypt) war eine der ersten Methoden zur Verschlüsselung von DNS-Anfragen. DNSCrypt arbeitet auf Port 443 und funktioniert mit den Transportprotokollen TCP und UDP. DNSCrypt has never been submitted to the [Internet Engineering Task Force (IETF)](https://en.wikipedia.org/wiki/Internet_Engineering_Task_Force) nor has it gone through the [Request for Comments (RFC)](https://en.wikipedia.org/wiki/Request_for_Comments) process, so it has not been used widely outside of a few [implementations](https://dnscrypt.info/implementations). As a result, it has been largely replaced by the more popular [DNS over HTTPS](#dns-over-https-doh).
|
||||
|
||||
### DNS over TLS (DoT)
|
||||
|
||||
|
||||
@ -72,6 +72,10 @@ We have sometimes found that the syntax for inserting an image like above was mi
|
||||
|
||||
For examples like the above admonitions, quotation marks, e.g.: `" "` must be used to specify string text. MkDocs will not correctly interpret other symbols i.e., `「 」` or `« »`. Other punctuation marks are fine for marking regular quotations within the text otherwise.
|
||||
|
||||
## Brackets
|
||||
## Fullwidth alternatives and Markdown syntax
|
||||
|
||||
Markdown links must use brackets i.e. `[Example link](https://example.com)`. CJK style brackets such as `（ ）` will not work for links. Crowdin will often handle links automatically, but you may encounter these links inside admonitions and other customized blocks of text.
|
||||
CJK writing systems tend to use alternative "fullwidth" variants of common symbols. These are different characters and cannot be used for markdown syntax.
|
||||
|
||||
- Links must use regular parenthesis ie `(` (Left Parenthesis U+0028) and `)` (Right Parenthesis U+0029) and not `（` (Fullwidth Left Parenthesis U+FF08) or `）` (Fullwidth Right Parenthesis U+FF09)
|
||||
- Indented quoted text must use `:` (Colon U+003A) and not `：` (Fullwidth Colon U+FF1A)
|
||||
- Pictures must use `!` (Exclamation Mark U+0021) and not `！` (Fullwidth Exclamation Mark U+FF01)
|
||||
|
||||
@ -72,6 +72,10 @@ We have sometimes found that the syntax for inserting an image like above was mi
|
||||
|
||||
For examples like the above admonitions, quotation marks, e.g.: `" "` must be used to specify string text. MkDocs will not correctly interpret other symbols i.e., `「 」` or `« »`. Other punctuation marks are fine for marking regular quotations within the text otherwise.
|
||||
|
||||
## Brackets
|
||||
## Fullwidth alternatives and Markdown syntax
|
||||
|
||||
Markdown links must use brackets i.e. `[Example link](https://example.com)`. CJK style brackets such as `（ ）` will not work for links. Crowdin will often handle links automatically, but you may encounter these links inside admonitions and other customized blocks of text.
|
||||
CJK writing systems tend to use alternative "fullwidth" variants of common symbols. These are different characters and cannot be used for markdown syntax.
|
||||
|
||||
- Links must use regular parenthesis ie `(` (Left Parenthesis U+0028) and `)` (Right Parenthesis U+0029) and not `（` (Fullwidth Left Parenthesis U+FF08) or `）` (Fullwidth Right Parenthesis U+FF09)
|
||||
- Indented quoted text must use `:` (Colon U+003A) and not `：` (Fullwidth Colon U+FF1A)
|
||||
- Pictures must use `!` (Exclamation Mark U+0021) and not `！` (Fullwidth Exclamation Mark U+FF01)
|
||||
|
||||
@ -72,6 +72,10 @@ We have sometimes found that the syntax for inserting an image like above was mi
|
||||
|
||||
For examples like the above admonitions, quotation marks, e.g.: `" "` must be used to specify string text. MkDocs will not correctly interpret other symbols i.e., `「 」` or `« »`. Other punctuation marks are fine for marking regular quotations within the text otherwise.
|
||||
|
||||
## Brackets
|
||||
## Fullwidth alternatives and Markdown syntax
|
||||
|
||||
Markdown links must use brackets i.e. `[Example link](https://example.com)`. CJK style brackets such as `（ ）` will not work for links. Crowdin will often handle links automatically, but you may encounter these links inside admonitions and other customized blocks of text.
|
||||
CJK writing systems tend to use alternative "fullwidth" variants of common symbols. These are different characters and cannot be used for markdown syntax.
|
||||
|
||||
- Links must use regular parenthesis ie `(` (Left Parenthesis U+0028) and `)` (Right Parenthesis U+0029) and not `（` (Fullwidth Left Parenthesis U+FF08) or `）` (Fullwidth Right Parenthesis U+FF09)
|
||||
- Indented quoted text must use `:` (Colon U+003A) and not `：` (Fullwidth Colon U+FF1A)
|
||||
- Pictures must use `!` (Exclamation Mark U+0021) and not `！` (Fullwidth Exclamation Mark U+FF01)
|
||||
|
||||
@ -72,6 +72,10 @@ We have sometimes found that the syntax for inserting an image like above was mi
|
||||
|
||||
For examples like the above admonitions, quotation marks, e.g.: `" "` must be used to specify string text. MkDocs will not correctly interpret other symbols i.e., `「 」` or `« »`. Other punctuation marks are fine for marking regular quotations within the text otherwise.
|
||||
|
||||
## Brackets
|
||||
## Fullwidth alternatives and Markdown syntax
|
||||
|
||||
Markdown links must use brackets i.e. `[Example link](https://example.com)`. CJK style brackets such as `（ ）` will not work for links. Crowdin will often handle links automatically, but you may encounter these links inside admonitions and other customized blocks of text.
|
||||
CJK writing systems tend to use alternative "fullwidth" variants of common symbols. These are different characters and cannot be used for markdown syntax.
|
||||
|
||||
- Links must use regular parenthesis ie `(` (Left Parenthesis U+0028) and `)` (Right Parenthesis U+0029) and not `（` (Fullwidth Left Parenthesis U+FF08) or `）` (Fullwidth Right Parenthesis U+FF09)
|
||||
- Indented quoted text must use `:` (Colon U+003A) and not `：` (Fullwidth Colon U+FF1A)
|
||||
- Pictures must use `!` (Exclamation Mark U+0021) and not `！` (Fullwidth Exclamation Mark U+FF01)
|
||||
|
||||
@ -6,7 +6,7 @@ description: An overview of several network architectures commonly used by insta
|
||||
|
||||
There are several network architectures commonly used to relay messages between people. These networks can provide different privacy guarantees, which is why it's worth considering your [threat model](../basics/threat-modeling.md) when deciding which app to use.
|
||||
|
||||
[Recommended Instant Messengers](../real-time-communication.md ""){.md-button}
|
||||
[پیامرسانهای توصیه شده](../real-time-communication.md ""){.md-button}
|
||||
|
||||
## Centralized Networks
|
||||
|
||||
|
||||
@ -1,25 +1,25 @@
|
||||
---
|
||||
meta_title: "Encrypted Private Email Recommendations - Privacy Guides"
|
||||
title: "Email Services"
|
||||
meta_title: "توصیه های ایمیل خصوصی رمزگذاری شده - Privacy Guides"
|
||||
title: "سرویسهای ایمیل"
|
||||
icon: material/email
|
||||
description: These email providers offer a great place to store your emails securely, and many offer interoperable OpenPGP encryption with other providers.
|
||||
description: این ارائه دهندگان ایمیل فضایی عالی برای ذخیره ایمن ایمیلهای شما ارائه می دهند، و بسیاری از آنها رمزگذاری OpenPGP با سایر ارائه دهندگان ایمیل را ارائه می دهند.
|
||||
cover: email.png
|
||||
---
|
||||
|
||||
Email is practically a necessity for using any online service, however we do not recommend it for person-to-person conversations. Rather than using email to contact other people, consider using an instant messaging medium that supports forward secrecy.
|
||||
ایمیل عملاً برای استفاده از هر سرویس آنلاین ضروری است، اما ما آن را برای مکالمات فرد به فرد توصیه نمی کنیم. به جای استفاده از ایمیل برای تماس با افراد دیگر، از یک پیامرسان استفاده کنید که از محرمانگی رو به جلو (forward secrecy) پشتیبانی میکند.
|
||||
|
||||
[Recommended Instant Messengers](real-time-communication.md ""){.md-button}
|
||||
[پیامرسانهای توصیه شده](real-time-communication.md ""){.md-button}
|
||||
|
||||
For everything else, we recommend a variety of email providers based on sustainable business models and built-in security and privacy features.
|
||||
برای هر چیز دیگری، ما انواع ارائه دهندگان ایمیل را بر اساس مدلهای تجاری پایدار و ویژگیهای امنیتی و حریم خصوصی توصیه میکنیم.
|
||||
|
||||
- [OpenPGP-Compatible Email Providers :material-arrow-right-drop-circle:](#openpgp-compatible-services)
|
||||
- [Other Encrypted Providers :material-arrow-right-drop-circle:](#more-providers)
|
||||
- [Email Aliasing Services :material-arrow-right-drop-circle:](#email-aliasing-services)
|
||||
- [Self-Hosted Options :material-arrow-right-drop-circle:](#self-hosting-email)
|
||||
- [ارائه دهندگان ایمیل سازگار با OpenPGP :material-arrow-right-drop-circle:](#openpgp-compatible-services)
|
||||
- [سایر ارائه دهندگان ایمیل رمزگذاری شده :material-arrow-right-drop-circle:](#more-providers)
|
||||
- [سرویس های نام مستعار ایمیل (Email Aliasing) :material-arrow-right-drop-circle:](#email-aliasing-services)
|
||||
- [گزینه های خود میزبانی (Self-Hosted) :material-arrow-right-drop-circle:](#self-hosting-email)
|
||||
|
||||
## OpenPGP Compatible Services
|
||||
## سرویسهای سازگار با OpenPGP
|
||||
|
||||
These providers natively support OpenPGP encryption/decryption and the Web Key Directory (WKD) standard, allowing for provider-agnostic E2EE emails. For example, a Proton Mail user could send an E2EE message to a Mailbox.org user, or you could receive OpenPGP-encrypted notifications from internet services which support it.
|
||||
این ارائه دهندگان به طور بومی از رمزگذاری/رمزگشایی OpenPGP و استاندارد Web Key Directory (WKD) پشتیبانی میکنند، که امکان ارسال ایمیلهای E2EE بین سرویسی را فراهم میکند. به عنوان مثال، یک کاربر Proton Mail می تواند یک پیام E2EE را به یک کاربر Mailbox.org ارسال کند، یا می توانید اعلان های رمزگذاری شده با OpenPGP را از سرویس های اینترنتی که از آن پشتیبانی می کنند دریافت کنید.
|
||||
|
||||
<div class="grid cards" markdown>
|
||||
|
||||
@ -28,11 +28,11 @@ These providers natively support OpenPGP encryption/decryption and the Web Key D
|
||||
|
||||
</div>
|
||||
|
||||
!!! warning
|
||||
!!! هشدار
|
||||
|
||||
When using E2EE technology like OpenPGP, email will still have some metadata that is not encrypted in the header of the email. Read more about [email metadata](basics/email-security.md#email-metadata-overview).
|
||||
هنگام استفاده از فناوری E2EE مانند OpenPGP، ایمیل همچنان دارای برخی فراداده است که در header ایمیل رمزگذاری نشده است. بیشتر بخوانید در مورد [فراداده ایمیل](basics/email-security.md#email-metadata-overview).
|
||||
|
||||
OpenPGP also does not support Forward secrecy, which means if either your or the recipient's private key is ever stolen, all previous messages encrypted with it will be exposed. [How do I protect my private keys?](basics/email-security.md#how-do-i-protect-my-private-keys)
|
||||
OpenPGP همچنین از Forward secrecy پشتیبانی نمی کند، به این معنی که اگر کلید خصوصی شما یا گیرنده به سرقت رفته باشد، همه پیام های قبلی رمزگذاری شده با آن قابل بازگشایی خواهد بود. [چگونه از کلید خصوصی خود محافظت کنم؟](basics/email-security.md#how-do-i-protect-my-private-keys)
|
||||
|
||||
### Proton Mail
|
||||
|
||||
|
||||
@ -36,21 +36,21 @@ schema:
|
||||
---
|
||||
|
||||
<!-- markdownlint-disable-next-line -->
|
||||
## Why should I care?
|
||||
## چرا باید برای من مهم باشد؟
|
||||
|
||||
##### “I have nothing to hide. Why should I care about my privacy?”
|
||||
##### "من چیزی برای مخفی کردن ندارم. چرا باید به حریم خصوصی اهمیت بدهم؟"
|
||||
|
||||
Much like the right to interracial marriage, woman's suffrage, freedom of speech, and many others, our right to privacy hasn't always been upheld. In several dictatorships, it still isn't. Generations before ours fought for our right to privacy. ==Privacy is a human right, inherent to all of us,== that we are entitled to (without discrimination).
|
||||
تمام حقوقی که اکنون برای ما طبیعی به نظر میرسند، به عنوان انسانها برای ما در طول تاریخ تضمین نشده بودهاند. حق ازدواج مختلط، حق رأی زنان، آزادی بیان و بسیاری از حقوق دیگر در برابر سرکوب و نقض قرار گرفتهاند. در چندین دیکتاتوری، هنوز هم این امر صادق نیست. نسلهای قبل از ما برای حق حریم خصوصی ما مبارزه کردند. حریم خصوصی یک حق انسانی است که درونی برای همهٔ ما وجود دارد و ما به آن (بدون تبعیض) حق داریم.
|
||||
|
||||
You shouldn't confuse privacy with secrecy. We know what happens in the bathroom, but you still close the door. That's because you want privacy, not secrecy. **Everyone** has something to protect. Privacy is something that makes us human.
|
||||
شما نباید حریم خصوصی را با امنیت اشتباه بگیرید. ما میدانیم که در حمام چه اتفاقاتی میافتد، اما همچنان در را میبندید. That's because you want privacy, not secrecy. **Everyone** has something to protect. Privacy is something that makes us human.
|
||||
|
||||
[:material-book-outline: Why Privacy Matters](basics/why-privacy-matters.md){ class="md-button md-button--primary" }
|
||||
|
||||
## What should I do?
|
||||
## چه کاری باید انجام بدهم؟
|
||||
|
||||
##### First, you need to make a plan
|
||||
|
||||
Trying to protect all your data from everyone all the time is impractical, expensive, and exhausting. But don't worry! Security is a process, and, by thinking ahead, you can put together a plan that's right for you. Security isn't just about the tools you use or the software you download. Rather, it begins by understanding the unique threats you face, and how you can mitigate them.
|
||||
Trying to protect all your data from everyone all the time is impractical, expensive, and exhausting. ولی نگران نباشید! Security is a process, and, by thinking ahead, you can put together a plan that's right for you. Security isn't just about the tools you use or the software you download. Rather, it begins by understanding the unique threats you face, and how you can mitigate them.
|
||||
|
||||
==This process of identifying threats and defining countermeasures is called **threat modeling**==, and it forms the basis of every good security and privacy plan.
|
||||
|
||||
@ -58,7 +58,7 @@ Trying to protect all your data from everyone all the time is impractical, expen
|
||||
|
||||
---
|
||||
|
||||
## We need you! Here's how to get involved:
|
||||
## ما به کمک شما نیاز داریم! Here's how to get involved:
|
||||
|
||||
[:simple-discourse:](https://discuss.privacyguides.net/){ title="Join our Forum" }
|
||||
[:simple-mastodon:](https://mastodon.neat.computer/@privacyguides){ rel=me title="Follow us on Mastodon" }
|
||||
|
||||
@ -72,6 +72,10 @@ We have sometimes found that the syntax for inserting an image like above was mi
|
||||
|
||||
For examples like the above admonitions, quotation marks, e.g.: `" "` must be used to specify string text. MkDocs will not correctly interpret other symbols i.e., `「 」` or `« »`. Other punctuation marks are fine for marking regular quotations within the text otherwise.
|
||||
|
||||
## Brackets
|
||||
## تبدیل کامل عرض و نحوهٔ استفاده از Markdown
|
||||
|
||||
Markdown links must use brackets i.e. `[Example link](https://example.com)`. CJK style brackets such as `（ ）` will not work for links. Crowdin will often handle links automatically, but you may encounter these links inside admonitions and other customized blocks of text.
|
||||
سیستمهای نگارش CJK (چینی، ژاپنی، کرهای) به طور معمول از نسخههای جایگزین "عرض کامل" نمادهای متداول استفاده میکنند. تبدیلهای تمامعرض و نحوهٔ استفاده از نشانهها در Markdown.
|
||||
|
||||
- Links must use regular parenthesis ie `(` (Left Parenthesis U+0028) and `)` (Right Parenthesis U+0029) and not `（` (Fullwidth Left Parenthesis U+FF08) or `）` (Fullwidth Right Parenthesis U+FF09)
|
||||
- Indented quoted text must use `:` (Colon U+003A) and not `：` (Fullwidth Colon U+FF1A)
|
||||
- Pictures must use `!` (Exclamation Mark U+0021) and not `！` (Fullwidth Exclamation Mark U+FF01)
|
||||
|
||||
@ -72,6 +72,10 @@ Nous avons parfois constaté que la syntaxe pour l'insertion d'une image comme c
|
||||
|
||||
Pour des exemples tels que les admonitions ci-dessus, les guillemets, par exemple : `" "` doivent être utilisés pour spécifier un texte sous forme de chaîne. MkDocs n'interprète pas correctement les autres symboles, par exemple `「 」` ou `« »`. Les autres signes de ponctuation conviennent pour marquer les citations régulières dans le texte.
|
||||
|
||||
## Crochets et parenthèses
|
||||
## Alternatives en pleine largeur et syntaxe Markdown
|
||||
|
||||
Les liens Markdown doivent être placés entre crochets et parenthèses, par exemple : `[Exemple de lien](https://example.com)`. Les parenthèses de style CJK telles que `（ ）` ne fonctionneront pas pour les liens. Crowdin gère souvent les liens automatiquement, mais vous pouvez rencontrer ces liens dans les admonitions et autres blocs de texte personnalisés.
|
||||
Les systèmes d'écriture CJK ont tendance à utiliser des variantes "pleine largeur" des symboles courants. Il s'agit de caractères différents qui ne peuvent pas être utilisés pour la syntaxe Markdown.
|
||||
|
||||
- Les liens doivent utiliser des parenthèses normales, c'est-à-dire `(` (parenthèse gauche U+0028) et `)` (parenthèse droite U+0029) et non `（` (parenthèse gauche pleine largeur U+FF08) ou `）` (parenthèse droite pleine largeur U+FF09)
|
||||
- Le texte cité et en retrait doit utiliser `:` (deux-points U+003A) et non `：` (deux-points pleine largeur U+FF1A)
|
||||
- Les images doivent utiliser `!` (point d'exclamation U+0021) et non `！` (point d'exclamation pleine largeur U+FF01)
|
||||
|
||||
@ -72,6 +72,10 @@ We have sometimes found that the syntax for inserting an image like above was mi
|
||||
|
||||
For examples like the above admonitions, quotation marks, e.g.: `" "` must be used to specify string text. MkDocs will not correctly interpret other symbols i.e., `「 」` or `« »`. Other punctuation marks are fine for marking regular quotations within the text otherwise.
|
||||
|
||||
## Brackets
|
||||
## Fullwidth alternatives and Markdown syntax
|
||||
|
||||
Markdown links must use brackets i.e. `[Example link](https://example.com)`. CJK style brackets such as `（ ）` will not work for links. Crowdin will often handle links automatically, but you may encounter these links inside admonitions and other customized blocks of text.
|
||||
CJK writing systems tend to use alternative "fullwidth" variants of common symbols. These are different characters and cannot be used for markdown syntax.
|
||||
|
||||
- Links must use regular parenthesis ie `(` (Left Parenthesis U+0028) and `)` (Right Parenthesis U+0029) and not `（` (Fullwidth Left Parenthesis U+FF08) or `）` (Fullwidth Right Parenthesis U+FF09)
|
||||
- Indented quoted text must use `:` (Colon U+003A) and not `：` (Fullwidth Colon U+FF1A)
|
||||
- Pictures must use `!` (Exclamation Mark U+0021) and not `！` (Fullwidth Exclamation Mark U+FF01)
|
||||
|
||||
@ -72,6 +72,10 @@ We have sometimes found that the syntax for inserting an image like above was mi
|
||||
|
||||
For examples like the above admonitions, quotation marks, e.g.: `" "` must be used to specify string text. MkDocs will not correctly interpret other symbols i.e., `「 」` or `« »`. Other punctuation marks are fine for marking regular quotations within the text otherwise.
|
||||
|
||||
## Brackets
|
||||
## Fullwidth alternatives and Markdown syntax
|
||||
|
||||
Markdown links must use brackets i.e. `[Example link](https://example.com)`. CJK style brackets such as `（ ）` will not work for links. Crowdin will often handle links automatically, but you may encounter these links inside admonitions and other customized blocks of text.
|
||||
CJK writing systems tend to use alternative "fullwidth" variants of common symbols. These are different characters and cannot be used for markdown syntax.
|
||||
|
||||
- Links must use regular parenthesis ie `(` (Left Parenthesis U+0028) and `)` (Right Parenthesis U+0029) and not `（` (Fullwidth Left Parenthesis U+FF08) or `）` (Fullwidth Right Parenthesis U+FF09)
|
||||
- Indented quoted text must use `:` (Colon U+003A) and not `：` (Fullwidth Colon U+FF1A)
|
||||
- Pictures must use `!` (Exclamation Mark U+0021) and not `！` (Fullwidth Exclamation Mark U+FF01)
|
||||
|
||||
@ -72,6 +72,10 @@ We have sometimes found that the syntax for inserting an image like above was mi
|
||||
|
||||
For examples like the above admonitions, quotation marks, e.g.: `" "` must be used to specify string text. MkDocs will not correctly interpret other symbols i.e., `「 」` or `« »`. Other punctuation marks are fine for marking regular quotations within the text otherwise.
|
||||
|
||||
## Brackets
|
||||
## Fullwidth alternatives and Markdown syntax
|
||||
|
||||
Markdown links must use brackets i.e. `[Example link](https://example.com)`. CJK style brackets such as `（ ）` will not work for links. Crowdin will often handle links automatically, but you may encounter these links inside admonitions and other customized blocks of text.
|
||||
CJK writing systems tend to use alternative "fullwidth" variants of common symbols. These are different characters and cannot be used for markdown syntax.
|
||||
|
||||
- Links must use regular parenthesis ie `(` (Left Parenthesis U+0028) and `)` (Right Parenthesis U+0029) and not `（` (Fullwidth Left Parenthesis U+FF08) or `）` (Fullwidth Right Parenthesis U+FF09)
|
||||
- Indented quoted text must use `:` (Colon U+003A) and not `：` (Fullwidth Colon U+FF1A)
|
||||
- Pictures must use `!` (Exclamation Mark U+0021) and not `！` (Fullwidth Exclamation Mark U+FF01)
|
||||
|
||||
@ -72,6 +72,10 @@ We have sometimes found that the syntax for inserting an image like above was mi
|
||||
|
||||
For examples like the above admonitions, quotation marks, e.g.: `" "` must be used to specify string text. MkDocs will not correctly interpret other symbols i.e., `「 」` or `« »`. Other punctuation marks are fine for marking regular quotations within the text otherwise.
|
||||
|
||||
## Brackets
|
||||
## Fullwidth alternatives and Markdown syntax
|
||||
|
||||
Markdown links must use brackets i.e. `[Example link](https://example.com)`. CJK style brackets such as `（ ）` will not work for links. Crowdin will often handle links automatically, but you may encounter these links inside admonitions and other customized blocks of text.
|
||||
CJK writing systems tend to use alternative "fullwidth" variants of common symbols. These are different characters and cannot be used for markdown syntax.
|
||||
|
||||
- Links must use regular parenthesis ie `(` (Left Parenthesis U+0028) and `)` (Right Parenthesis U+0029) and not `（` (Fullwidth Left Parenthesis U+FF08) or `）` (Fullwidth Right Parenthesis U+FF09)
|
||||
- Indented quoted text must use `:` (Colon U+003A) and not `：` (Fullwidth Colon U+FF1A)
|
||||
- Pictures must use `!` (Exclamation Mark U+0021) and not `！` (Fullwidth Exclamation Mark U+FF01)
|
||||
|
||||
@ -72,6 +72,10 @@ Talvolta, ci siamo resi conto che la sintassi per inserire un'immagine come la p
|
||||
|
||||
Per gli esempi come gli ammonimenti precedenti, le virgolette, es.: `" "` devono essere utilizzate per specificare il testo della stringa. MkDocs non interpreterà correttamente altri simboli, cioè, `「 」` o `« »`. Altri segni di punteggiatura vanno bene per contrassegnare regolari citazioni all'interno del testo.
|
||||
|
||||
## Parentesi
|
||||
## Alternative a larghezza intera e sintassi di Markdown
|
||||
|
||||
I link in Markdown devono utilizzare le parentesi, come ad esempio, `[Link di esempio](https://esempio.it)`. Le parentesi in stile CJK, come `（ ）` non funzioneranno con i collegamenti. Crowdin, spesso, gestirà automaticamente i collegamenti, ma li incontrerai negli ammonimenti e in altri blocchi personalizzati di testo.
|
||||
Sistemi di scrittura CJK tendono a utilizzare varianti alternative "a larghezza intera" di simboli comuni. Si tratta di caratteri differenti e non utilizzabili per la sintassi di Markdown.
|
||||
|
||||
- I link devono utilizzare le parentesi regolari, cioè `(` (Parentesi Sinistra U+0028) e `)` (Parentesi Destra U+0029) ee non `（` (Parentesi Sinistra a Larghezza Intera U+FF08) o `）` (Parentesi Destra a Larghezza Intera U+FF09)
|
||||
- Il testo tra virgolette rientrato deve utilizzare `:` (Due punti U+003A) e non `：` (Due Punti a Larghezza Intera U+FF1A)
|
||||
- Le immagini devono utilizzare `!` (Punto Esclamativo U+0021) e non `！` (Punto Esclamativo a Larghezza Intera U+FF01)
|
||||
|
||||
@ -72,6 +72,10 @@ We have sometimes found that the syntax for inserting an image like above was mi
|
||||
|
||||
For examples like the above admonitions, quotation marks, e.g.: `" "` must be used to specify string text. MkDocs will not correctly interpret other symbols i.e., `「 」` or `« »`. Other punctuation marks are fine for marking regular quotations within the text otherwise.
|
||||
|
||||
## Brackets
|
||||
## Fullwidth alternatives and Markdown syntax
|
||||
|
||||
Markdown links must use brackets i.e. `[Example link](https://example.com)`. CJK style brackets such as `（ ）` will not work for links. Crowdin will often handle links automatically, but you may encounter these links inside admonitions and other customized blocks of text.
|
||||
CJK writing systems tend to use alternative "fullwidth" variants of common symbols. These are different characters and cannot be used for markdown syntax.
|
||||
|
||||
- Links must use regular parenthesis ie `(` (Left Parenthesis U+0028) and `)` (Right Parenthesis U+0029) and not `（` (Fullwidth Left Parenthesis U+FF08) or `）` (Fullwidth Right Parenthesis U+FF09)
|
||||
- Indented quoted text must use `:` (Colon U+003A) and not `：` (Fullwidth Colon U+FF1A)
|
||||
- Pictures must use `!` (Exclamation Mark U+0021) and not `！` (Fullwidth Exclamation Mark U+FF01)
|
||||
|
||||
@ -72,6 +72,10 @@ We have sometimes found that the syntax for inserting an image like above was mi
|
||||
|
||||
For examples like the above admonitions, quotation marks, e.g.: `" "` must be used to specify string text. MkDocs will not correctly interpret other symbols i.e., `「 」` or `« »`. Other punctuation marks are fine for marking regular quotations within the text otherwise.
|
||||
|
||||
## Brackets
|
||||
## Fullwidth alternatives and Markdown syntax
|
||||
|
||||
Markdown links must use brackets i.e. `[Example link](https://example.com)`. CJK style brackets such as `（ ）` will not work for links. Crowdin will often handle links automatically, but you may encounter these links inside admonitions and other customized blocks of text.
|
||||
CJK writing systems tend to use alternative "fullwidth" variants of common symbols. These are different characters and cannot be used for markdown syntax.
|
||||
|
||||
- Links must use regular parenthesis ie `(` (Left Parenthesis U+0028) and `)` (Right Parenthesis U+0029) and not `（` (Fullwidth Left Parenthesis U+FF08) or `）` (Fullwidth Right Parenthesis U+FF09)
|
||||
- Indented quoted text must use `:` (Colon U+003A) and not `：` (Fullwidth Colon U+FF1A)
|
||||
- Pictures must use `!` (Exclamation Mark U+0021) and not `！` (Fullwidth Exclamation Mark U+FF01)
|
||||
|
||||
@ -4,25 +4,25 @@ icon: simple/linux
|
||||
description: Linux is an open-source, privacy-focused desktop operating system alternative, but not all distribitions are created equal.
|
||||
---
|
||||
|
||||
It is often believed that [open-source](https://en.wikipedia.org/wiki/Open-source_software) software is inherently secure because the source code is available. There is an expectation that community verification occurs regularly; however, this isn’t always [the case](https://seirdy.one/posts/2022/02/02/floss-security/). It does depend on a number of factors, such as project activity, developer experience, level of rigor applied to [code reviews](https://en.wikipedia.org/wiki/Code_review), and how often attention is given to specific parts of the [codebase](https://en.wikipedia.org/wiki/Codebase) that may go untouched for years.
|
||||
대부분의 사람들은 [오픈소스 소프트웨어](https://en.wikipedia.org/wiki/Open-source_software)는 소스가 공개되어 있어 근본적으로 안전하다고 생각합니다. 커뮤니티가 코드를 주기적으로 검증할 것이라고 생각하지만, [꼭 그렇지 않습니다](https://seirdy.one/posts/2022/02/02/floss-security/). 실제 보안은 프로젝트 활동량, 개발자들의 경험, [코드 리뷰](https://en.wikipedia.org/wiki/Code_review)를 얼마나 엄격하게 하는지, [코드베이스](https://en.wikipedia.org/wiki/Codebase)의 다양한 부분에 얼마나 주의를 기울이는지 등과 같은 다양한 요인에 따라 달라집니다.
|
||||
|
||||
At the moment, desktop Linux does have some areas that could be better improved when compared to their proprietary counterparts, e.g.:
|
||||
|
||||
- A verified boot chain, like Apple’s [Secure Boot](https://support.apple.com/guide/security/startup-security-utility-secc7b34e5b5/web) (with [Secure Enclave](https://support.apple.com/guide/security/secure-enclave-sec59b0b31ff/1/web/1)), Android’s [Verified Boot](https://source.android.com/security/verifiedboot), ChromeOS' [Verified boot](https://www.chromium.org/chromium-os/chromiumos-design-docs/security-overview/#verified-boot), or Microsoft Windows’s [boot process](https://docs.microsoft.com/en-us/windows/security/information-protection/secure-the-windows-10-boot-process) with [TPM](https://docs.microsoft.com/en-us/windows/security/information-protection/tpm/how-windows-uses-the-tpm). These features and hardware technologies can all help prevent persistent tampering by malware or [evil maid attacks](https://en.wikipedia.org/wiki/Evil_Maid_attack)
|
||||
- A strong sandboxing solution such as that found in [macOS](https://developer.apple.com/library/archive/documentation/Security/Conceptual/AppSandboxDesignGuide/AboutAppSandbox/AboutAppSandbox.html), [ChromeOS](https://chromium.googlesource.com/chromiumos/docs/+/HEAD/sandboxing.md), and [Android](https://source.android.com/security/app-sandbox). Commonly used Linux sandboxing solutions such as [Flatpak](https://docs.flatpak.org/en/latest/sandbox-permissions.html) and [Firejail](https://firejail.wordpress.com/) still have a long way to go
|
||||
- A verified boot chain, like Apple’s [Secure Boot](https://support.apple.com/guide/security/startup-security-utility-secc7b34e5b5/web) (with [Secure Enclave](https://support.apple.com/guide/security/secure-enclave-sec59b0b31ff/1/web/1)), Android’s [Verified Boot](https://source.android.com/security/verifiedboot), ChromeOS' [Verified boot](https://www.chromium.org/chromium-os/chromiumos-design-docs/security-overview/#verified-boot), or Microsoft Windows’s [boot process](https://docs.microsoft.com/en-us/windows/security/information-protection/secure-the-windows-10-boot-process) with [TPM](https://docs.microsoft.com/en-us/windows/security/information-protection/tpm/how-windows-uses-the-tpm). 이러한 기능과 기술들은 [evil maid 공격](https://en.wikipedia.org/wiki/Evil_Maid_attack)이나 멀웨어로 인한 변조를 막는데 도움을 줍니다.
|
||||
- [macOS](https://developer.apple.com/library/archive/documentation/Security/Conceptual/AppSandboxDesignGuide/AboutAppSandbox/AboutAppSandbox.html), [ChromeOS](https://chromium.googlesource.com/chromiumos/docs/+/HEAD/sandboxing.md), [안드로이드](https://source.android.com/security/app-sandbox)와 같은 운영체제에 탑재된 샌드박스 기술 Linux에서 자주 사용되는 [Flatpak](https://docs.flatpak.org/en/latest/sandbox-permissions.html)과 [Firejail](https://firejail.wordpress.com/) 샌드박스 기술은 아직 발전중입니다.
|
||||
- Strong [exploit mitigations](https://madaidans-insecurities.github.io/linux.html#exploit-mitigations)
|
||||
|
||||
Despite these drawbacks, desktop Linux distributions are great if you want to:
|
||||
이런 단점에도 불구하고 다음과 같은 경우에는 Linux를 사용하는 것을 권장합니다:
|
||||
|
||||
- Avoid telemetry that often comes with proprietary operating systems
|
||||
- Maintain [software freedom](https://www.gnu.org/philosophy/free-sw.en.html#four-freedoms)
|
||||
- Have privacy focused systems such as [Whonix](https://www.whonix.org) or [Tails](https://tails.boum.org/)
|
||||
- 독점 소프트웨어에 자주 따라오는 데이터 수집을 피하고 싶을 때
|
||||
- [자유 소프트웨어](https://www.gnu.org/philosophy/free-sw.en.html#four-freedoms)를 사용하고 싶은 경우
|
||||
- [Whonix](https://www.whonix.org)나 [Tails](https://tails.boum.org/)와 같은 프라이버시를 중요시하는 운영체제를 사용하고 싶은 경우
|
||||
|
||||
Our website generally uses the term “Linux” to describe desktop Linux distributions. Other operating systems which also use the Linux kernel such as ChromeOS, Android, and Qubes OS are not discussed here.
|
||||
이 웹사이트에서 사용하는 "Linux"는 주로 데스크탑 Linux 배포판을 가리킵니다. Linux 커널을 사용하지만 ChromeOS, Android, Qubes OS와 같은 타 운영체제는 해당 페이지에서 소개하지 않습니다.
|
||||
|
||||
[Our Linux Recommendations :material-arrow-right-drop-circle:](../desktop.md ""){.md-button}
|
||||
[권장하는 Linux 배포판 :material-arrow-right-drop-circle:](../desktop.md ""){.md-button}
|
||||
|
||||
## Choosing your distribution
|
||||
## 배포판 선택하기
|
||||
|
||||
Not all Linux distributions are created equal. While our Linux recommendation page is not meant to be an authoritative source on which distribution you should use, there are a few things you should keep in mind when choosing which distribution to use.
|
||||
|
||||
|
||||
@ -72,6 +72,10 @@ We have sometimes found that the syntax for inserting an image like above was mi
|
||||
|
||||
For examples like the above admonitions, quotation marks, e.g.: `" "` must be used to specify string text. MkDocs will not correctly interpret other symbols i.e., `「 」` or `« »`. Other punctuation marks are fine for marking regular quotations within the text otherwise.
|
||||
|
||||
## Brackets
|
||||
## Fullwidth alternatives and Markdown syntax
|
||||
|
||||
Markdown links must use brackets i.e. `[Example link](https://example.com)`. CJK style brackets such as `（ ）` will not work for links. Crowdin will often handle links automatically, but you may encounter these links inside admonitions and other customized blocks of text.
|
||||
CJK writing systems tend to use alternative "fullwidth" variants of common symbols. These are different characters and cannot be used for markdown syntax.
|
||||
|
||||
- Links must use regular parenthesis ie `(` (Left Parenthesis U+0028) and `)` (Right Parenthesis U+0029) and not `（` (Fullwidth Left Parenthesis U+FF08) or `）` (Fullwidth Right Parenthesis U+FF09)
|
||||
- Indented quoted text must use `:` (Colon U+003A) and not `：` (Fullwidth Colon U+FF1A)
|
||||
- Pictures must use `!` (Exclamation Mark U+0021) and not `！` (Fullwidth Exclamation Mark U+FF01)
|
||||
|
||||
@ -72,6 +72,10 @@ We have sometimes found that the syntax for inserting an image like above was mi
|
||||
|
||||
For examples like the above admonitions, quotation marks, e.g.: `" "` must be used to specify string text. MkDocs will not correctly interpret other symbols i.e., `「 」` or `« »`. Other punctuation marks are fine for marking regular quotations within the text otherwise.
|
||||
|
||||
## Brackets
|
||||
## Fullwidth alternatives and Markdown syntax
|
||||
|
||||
Markdown links must use brackets i.e. `[Example link](https://example.com)`. CJK style brackets such as `（ ）` will not work for links. Crowdin will often handle links automatically, but you may encounter these links inside admonitions and other customized blocks of text.
|
||||
CJK writing systems tend to use alternative "fullwidth" variants of common symbols. These are different characters and cannot be used for markdown syntax.
|
||||
|
||||
- Links must use regular parenthesis ie `(` (Left Parenthesis U+0028) and `)` (Right Parenthesis U+0029) and not `（` (Fullwidth Left Parenthesis U+FF08) or `）` (Fullwidth Right Parenthesis U+FF09)
|
||||
- Indented quoted text must use `:` (Colon U+003A) and not `：` (Fullwidth Colon U+FF1A)
|
||||
- Pictures must use `!` (Exclamation Mark U+0021) and not `！` (Fullwidth Exclamation Mark U+FF01)
|
||||
|
||||
@ -72,6 +72,10 @@ We have sometimes found that the syntax for inserting an image like above was mi
|
||||
|
||||
For examples like the above admonitions, quotation marks, e.g.: `" "` must be used to specify string text. MkDocs will not correctly interpret other symbols i.e., `「 」` or `« »`. Other punctuation marks are fine for marking regular quotations within the text otherwise.
|
||||
|
||||
## Brackets
|
||||
## Fullwidth alternatives and Markdown syntax
|
||||
|
||||
Markdown links must use brackets i.e. `[Example link](https://example.com)`. CJK style brackets such as `（ ）` will not work for links. Crowdin will often handle links automatically, but you may encounter these links inside admonitions and other customized blocks of text.
|
||||
CJK writing systems tend to use alternative "fullwidth" variants of common symbols. These are different characters and cannot be used for markdown syntax.
|
||||
|
||||
- Links must use regular parenthesis ie `(` (Left Parenthesis U+0028) and `)` (Right Parenthesis U+0029) and not `（` (Fullwidth Left Parenthesis U+FF08) or `）` (Fullwidth Right Parenthesis U+FF09)
|
||||
- Indented quoted text must use `:` (Colon U+003A) and not `：` (Fullwidth Colon U+FF1A)
|
||||
- Pictures must use `!` (Exclamation Mark U+0021) and not `！` (Fullwidth Exclamation Mark U+FF01)
|
||||
|
||||
@ -72,6 +72,10 @@ We have sometimes found that the syntax for inserting an image like above was mi
|
||||
|
||||
For examples like the above admonitions, quotation marks, e.g.: `" "` must be used to specify string text. MkDocs will not correctly interpret other symbols i.e., `「 」` or `« »`. Other punctuation marks are fine for marking regular quotations within the text otherwise.
|
||||
|
||||
## Brackets
|
||||
## Fullwidth alternatives and Markdown syntax
|
||||
|
||||
Markdown links must use brackets i.e. `[Example link](https://example.com)`. CJK style brackets such as `（ ）` will not work for links. Crowdin will often handle links automatically, but you may encounter these links inside admonitions and other customized blocks of text.
|
||||
CJK writing systems tend to use alternative "fullwidth" variants of common symbols. These are different characters and cannot be used for markdown syntax.
|
||||
|
||||
- Links must use regular parenthesis ie `(` (Left Parenthesis U+0028) and `)` (Right Parenthesis U+0029) and not `（` (Fullwidth Left Parenthesis U+FF08) or `）` (Fullwidth Right Parenthesis U+FF09)
|
||||
- Indented quoted text must use `:` (Colon U+003A) and not `：` (Fullwidth Colon U+FF1A)
|
||||
- Pictures must use `!` (Exclamation Mark U+0021) and not `！` (Fullwidth Exclamation Mark U+FF01)
|
||||
|
||||
@ -74,6 +74,10 @@ We have sometimes found that the syntax for inserting an image like above was mi
|
||||
|
||||
For examples like the above admonitions, quotation marks, e.g.: `" "` must be used to specify string text. MkDocs will not correctly interpret other symbols i.e., `「 」` or `« »`. Other punctuation marks are fine for marking regular quotations within the text otherwise.
|
||||
|
||||
## Brackets
|
||||
## Fullwidth alternatives and Markdown syntax
|
||||
|
||||
Markdown links must use brackets i.e. `[Example link](https://example.com)`. CJK style brackets such as `（ ）` will not work for links. Crowdin will often handle links automatically, but you may encounter these links inside admonitions and other customized blocks of text.
|
||||
CJK writing systems tend to use alternative "fullwidth" variants of common symbols. These are different characters and cannot be used for markdown syntax.
|
||||
|
||||
- Links must use regular parenthesis ie `(` (Left Parenthesis U+0028) and `)` (Right Parenthesis U+0029) and not `（` (Fullwidth Left Parenthesis U+FF08) or `）` (Fullwidth Right Parenthesis U+FF09)
|
||||
- Indented quoted text must use `:` (Colon U+003A) and not `：` (Fullwidth Colon U+FF1A)
|
||||
- Pictures must use `!` (Exclamation Mark U+0021) and not `！` (Fullwidth Exclamation Mark U+FF01)
|
||||
|
||||
@ -72,6 +72,10 @@ We have sometimes found that the syntax for inserting an image like above was mi
|
||||
|
||||
For examples like the above admonitions, quotation marks, e.g.: `" "` must be used to specify string text. MkDocs will not correctly interpret other symbols i.e., `「 」` or `« »`. Other punctuation marks are fine for marking regular quotations within the text otherwise.
|
||||
|
||||
## Brackets
|
||||
## Fullwidth alternatives and Markdown syntax
|
||||
|
||||
Markdown links must use brackets i.e. `[Example link](https://example.com)`. CJK style brackets such as `（ ）` will not work for links. Crowdin will often handle links automatically, but you may encounter these links inside admonitions and other customized blocks of text.
|
||||
CJK writing systems tend to use alternative "fullwidth" variants of common symbols. These are different characters and cannot be used for markdown syntax.
|
||||
|
||||
- Links must use regular parenthesis ie `(` (Left Parenthesis U+0028) and `)` (Right Parenthesis U+0029) and not `（` (Fullwidth Left Parenthesis U+FF08) or `）` (Fullwidth Right Parenthesis U+FF09)
|
||||
- Indented quoted text must use `:` (Colon U+003A) and not `：` (Fullwidth Colon U+FF1A)
|
||||
- Pictures must use `!` (Exclamation Mark U+0021) and not `！` (Fullwidth Exclamation Mark U+FF01)
|
||||
|
||||
@ -72,6 +72,10 @@ We have sometimes found that the syntax for inserting an image like above was mi
|
||||
|
||||
For examples like the above admonitions, quotation marks, e.g.: `" "` must be used to specify string text. MkDocs will not correctly interpret other symbols i.e., `「 」` or `« »`. Other punctuation marks are fine for marking regular quotations within the text otherwise.
|
||||
|
||||
## Brackets
|
||||
## Fullwidth alternatives and Markdown syntax
|
||||
|
||||
Markdown links must use brackets i.e. `[Example link](https://example.com)`. CJK style brackets such as `（ ）` will not work for links. Crowdin will often handle links automatically, but you may encounter these links inside admonitions and other customized blocks of text.
|
||||
CJK writing systems tend to use alternative "fullwidth" variants of common symbols. These are different characters and cannot be used for markdown syntax.
|
||||
|
||||
- Links must use regular parenthesis ie `(` (Left Parenthesis U+0028) and `)` (Right Parenthesis U+0029) and not `（` (Fullwidth Left Parenthesis U+FF08) or `）` (Fullwidth Right Parenthesis U+FF09)
|
||||
- Indented quoted text must use `:` (Colon U+003A) and not `：` (Fullwidth Colon U+FF1A)
|
||||
- Pictures must use `!` (Exclamation Mark U+0021) and not `！` (Fullwidth Exclamation Mark U+FF01)
|
||||
|
||||
@ -72,6 +72,10 @@ We have sometimes found that the syntax for inserting an image like above was mi
|
||||
|
||||
For examples like the above admonitions, quotation marks, e.g.: `" "` must be used to specify string text. MkDocs will not correctly interpret other symbols i.e., `「 」` or `« »`. Other punctuation marks are fine for marking regular quotations within the text otherwise.
|
||||
|
||||
## Brackets
|
||||
## Fullwidth alternatives and Markdown syntax
|
||||
|
||||
Markdown links must use brackets i.e. `[Example link](https://example.com)`. CJK style brackets such as `（ ）` will not work for links. Crowdin will often handle links automatically, but you may encounter these links inside admonitions and other customized blocks of text.
|
||||
CJK writing systems tend to use alternative "fullwidth" variants of common symbols. These are different characters and cannot be used for markdown syntax.
|
||||
|
||||
- Links must use regular parenthesis ie `(` (Left Parenthesis U+0028) and `)` (Right Parenthesis U+0029) and not `（` (Fullwidth Left Parenthesis U+FF08) or `）` (Fullwidth Right Parenthesis U+FF09)
|
||||
- Indented quoted text must use `:` (Colon U+003A) and not `：` (Fullwidth Colon U+FF1A)
|
||||
- Pictures must use `!` (Exclamation Mark U+0021) and not `！` (Fullwidth Exclamation Mark U+FF01)
|
||||
|
||||
@ -72,6 +72,10 @@ We have sometimes found that the syntax for inserting an image like above was mi
|
||||
|
||||
For examples like the above admonitions, quotation marks, e.g.: `" "` must be used to specify string text. MkDocs will not correctly interpret other symbols i.e., `「 」` or `« »`. Other punctuation marks are fine for marking regular quotations within the text otherwise.
|
||||
|
||||
## Brackets
|
||||
## Fullwidth alternatives and Markdown syntax
|
||||
|
||||
Markdown links must use brackets i.e. `[Example link](https://example.com)`. CJK style brackets such as `（ ）` will not work for links. Crowdin will often handle links automatically, but you may encounter these links inside admonitions and other customized blocks of text.
|
||||
CJK writing systems tend to use alternative "fullwidth" variants of common symbols. These are different characters and cannot be used for markdown syntax.
|
||||
|
||||
- Links must use regular parenthesis ie `(` (Left Parenthesis U+0028) and `)` (Right Parenthesis U+0029) and not `（` (Fullwidth Left Parenthesis U+FF08) or `）` (Fullwidth Right Parenthesis U+FF09)
|
||||
- Indented quoted text must use `:` (Colon U+003A) and not `：` (Fullwidth Colon U+FF1A)
|
||||
- Pictures must use `!` (Exclamation Mark U+0021) and not `！` (Fullwidth Exclamation Mark U+FF01)
|
||||
|
||||
@ -72,6 +72,10 @@ We have sometimes found that the syntax for inserting an image like above was mi
|
||||
|
||||
For examples like the above admonitions, quotation marks, e.g.: `" "` must be used to specify string text. MkDocs will not correctly interpret other symbols i.e., `「 」` or `« »`. Other punctuation marks are fine for marking regular quotations within the text otherwise.
|
||||
|
||||
## Brackets
|
||||
## Fullwidth alternatives and Markdown syntax
|
||||
|
||||
Markdown links must use brackets i.e. `[Example link](https://example.com)`. CJK style brackets such as `（ ）` will not work for links. Crowdin will often handle links automatically, but you may encounter these links inside admonitions and other customized blocks of text.
|
||||
CJK writing systems tend to use alternative "fullwidth" variants of common symbols. These are different characters and cannot be used for markdown syntax.
|
||||
|
||||
- Links must use regular parenthesis ie `(` (Left Parenthesis U+0028) and `)` (Right Parenthesis U+0029) and not `（` (Fullwidth Left Parenthesis U+FF08) or `）` (Fullwidth Right Parenthesis U+FF09)
|
||||
- Indented quoted text must use `:` (Colon U+003A) and not `：` (Fullwidth Colon U+FF1A)
|
||||
- Pictures must use `!` (Exclamation Mark U+0021) and not `！` (Fullwidth Exclamation Mark U+FF01)
|
||||
|
||||
@ -20,7 +20,7 @@ PrivacyTools 由 BurungHantu 於 2015年創建，在斯諾登洩密事件後，
|
||||
|
||||
2020年， BurungHantu的缺席更加明顯。 有一次，我們要求將網域的名稱伺服器更改為由系統管理員控制的名稱伺服器，以避免未來中斷，但在提出請求後一個多月後都未能完成此更改。 他在 Matrix 公開聊天室和私人團隊聊天室中消失幾個月，偶爾會突然進來提供一些小反饋或承諾，然後再次消失。
|
||||
|
||||
2020 年10月， PrivacyTools 系統管理員 (Jonah) 因為這些困難，[離開](https://web.archive.org/web/20210729190742/https://blog.privacytools.io/blacklight447-taking-over/) 本專案，將控制權移交給其它長期投入者。 Jonah 經營幾乎所有的 PrivacyTools 服務，並在 BurungHantu 缺席時擔任網站開發的 *實質* 項目負責人，因此他的離開對該組織來說是一個重大變化。 由於這些重大的組織變化， BurungHantu 當時向留下的團隊承諾他將回來接管接下來的專案。 == 在接下來的幾個月裡， PrivacyTools 團隊通過幾種溝通方式聯繫，但沒有收到任何回應。
|
||||
2020 年10月， PrivacyTools 系統管理員 (Jonah) 因為這些困難，[離開](https://web.archive.org/web/20210729190742/https://blog.privacytools.io/blacklight447-taking-over/) 本專案，將控制權移交給其它長期投入者。 Jonah 經營幾乎所有的 PrivacyTools 服務，並在 BurungHantu 缺席時擔任網站開發的 *實質* 項目負責人，因此他的離開對該組織來說是一個重大變化。 由於這些重大的組織變化， BurungHantu 當時向留下的團隊承諾他將回來接管接下來的專案。 ==在接下來的幾個月裡， PrivacyTools 團隊通過幾種溝通方式聯繫，但沒有收到任何回應。==
|
||||
|
||||
## 域名可靠性
|
||||
|
||||
@ -34,7 +34,7 @@ PrivacyTools 由 BurungHantu 於 2015年創建，在斯諾登洩密事件後，
|
||||
|
||||
## 社區行動呼籲
|
||||
|
||||
2021年7月底，我們 <a href="https://web.archive.org/web/20210729184422/https://blog.privacytools.io/the-future-of-privacytools/>通知</a> PrivacyTools 社區打算搬移到新域名繼續專案，並於[2022 年8月2日選出新域名](https://web.archive.org/web/20210729190935/https://aragon.cloud/apps/forms/cMPxG9KyopapBbcw)。 最後選中 Privacy Guides ， Jonah 從2020年開始擁有`privacyguides.org` 網域原打算作為未開發的副項目。
|
||||
2021年7月底，我們 [通知](https://web.archive.org/web/20210729184422/https://blog.privacytools.io/the-future-of-privacytools/) PrivacyTools 社區打算搬移到新域名繼續專案，並於[2022 年8月2日選出新域名](https://web.archive.org/web/20210729190935/https://aragon.cloud/apps/forms/cMPxG9KyopapBbcw)。 最後選中 Privacy Guides ， Jonah 從2020年開始擁有`privacyguides.org` 網域原打算作為未開發的副項目。
|
||||
|
||||
## 控制r/privacytoolsIO
|
||||
|
||||
@ -77,7 +77,7 @@ BurungHantu 還發布一篇 [推特帖子](https://twitter.com/privacytoolsIO/st
|
||||
|
||||
截至 2022年9月25日，我們看到 BurungHantu 全部的打算都出現在privacytools.io ，因此我們決定創建這個解釋頁面。 他經營的網站似乎是重度 SEO 優化版本，以推薦工具來換取經濟補償。 最近 IVPN 和 Mullvad，這兩家受到隱私社群近乎一致[推薦](../vpn.md)的 VPN 供應商，因長期反對推薦人優惠回扣而受瞩目，卻遭到 PrivacyTools 的刪除。 在他们的位置上？ NordVPN、Surfshark、ExpressVPN 和 hide.me ；不值得信任的平臺和商業實踐的巨型 VPN 公司，以積極的營銷和推廣折扣而臭名昭著。
|
||||
|
||||
==**PrivacyTools 已成為我們 [過去在2019年 PrivacyTools 部落格所警告](https://web.archive.org/web/20210729205249/https://blog.privacytools.io/the-trouble-with-vpn-and-privacy-reviews/) 的網站類型。**= = 自過渡以來一直試圖與 PrivacyTools 保持距離，但他們對我們項目持續騷擾，現在他們荒謬地濫用原品牌在6年來獲得的可信度開源貢獻，這實在非常令人不安。 我們這些為隱私而戰的人並不是在互相爭鬥，也沒有從出價最高者那裡取得建議。
|
||||
==**PrivacyTools 已成為我們 [過去在2019年 PrivacyTools 部落格所警告](https://web.archive.org/web/20210729205249/https://blog.privacytools.io/the-trouble-with-vpn-and-privacy-reviews/) 的網站類型。**== 自過渡以來一直試圖與 PrivacyTools 保持距離，但他們對我們項目持續騷擾，現在他們荒謬地濫用原品牌在6年來獲得的可信度開源貢獻，這實在非常令人不安。 我們這些為隱私而戰的人並不是在互相爭鬥，也沒有從出價最高者那裡取得建議。
|
||||
|
||||
## r/privacytoolsIO Now
|
||||
|
||||
|
||||
@ -233,14 +233,14 @@ Shields 可以選擇根據需要依各網站情況降級，但我們建議預設
|
||||
|
||||
<div class="annotate" markdown>
|
||||
|
||||
- [x] 選擇* *防止網站根據語言偏好進行指紋辨識* *
|
||||
- [x] 在追蹤器和廣告封鎖下選擇* *侵略性* *
|
||||
- [x] 選擇 **防止網站根據語言偏好進行指紋辨識**
|
||||
- [x] 在追蹤器和廣告封鎖下選擇 **侵略性**
|
||||
|
||||
??? warning "使用預設過濾器列表"
|
||||
Brave允許您在內部`brave://adblock`頁面中選擇其他內容過濾器。 我們建議您不要使用此功能；請保留預設的篩選條件清單。 使用額外清單將使您在一般 Brave 用戶中被突顯出來，如果Brave有漏洞，並將惡意規則添加到您使用的清單中，也可能會增加攻擊面。
|
||||
|
||||
- [x] (可選) Select * * Block Scripts * * (1)
|
||||
- [x] Select * * Strict, may break sites * * under Block fingerprinting
|
||||
- [x] (可選) Select **Block Scripts** (1)
|
||||
- [x] Select **Strict, may break sites** under Block fingerprinting
|
||||
|
||||
</div>
|
||||
|
||||
@ -260,9 +260,11 @@ Shields 可以選擇根據需要依各網站情況降級，但我們建議預設
|
||||
- [ ] 取消勾選 **自動向 Brave 發送每日使用情况 **
|
||||
- [ ] 取消勾選 **自動發送診斷報告**
|
||||
- [x] 勾選 **安全** 選單**一直維持安全連接**
|
||||
- [ ] 取消勾選 **使用 Tor 的私密視窗** (1) 提示「關閉時進行消毒」
|
||||
- [ ] 取消勾選 **使用 Tor 的私密視窗** (1)
|
||||
|
||||
- [x] 選擇 在 **Cookies 和其他網站資料*選單中**關閉所有視窗時清除 cookies 和網站資料**
|
||||
!!! tip "關閉時進行消毒"
|
||||
|
||||
- [x] 選擇 在 **Cookies 和其他網站資料**選單中**關閉所有視窗時清除 cookies 和網站資料**
|
||||
|
||||
如果希望繼續登入經常訪問的特定網站，可以在*自訂行為*處根據每個網站設定例外情況。
|
||||
|
||||
|
||||
@ -84,7 +84,7 @@ Apple不提供用於建立加密DNS設定檔的原生介面。 [Secure DNS profi
|
||||
|
||||
**dnscrypt-proxy** 是 DNS 代理，支持 [DNSCrypt](advanced/dns-overview.md#dnscrypt)、 [DNS-over-HTTPS](advanced/dns-overview.md#dns-over-https-doh)和[Anonymized DNS](https://github.com/DNSCrypt/dnscrypt-proxy/wiki/Anonymized-DNS)。
|
||||
|
||||
!!! warning "匿名化 DNS 功能[**不會**](advanced/dns-overview.md#why-shouldnt-i-use-encrypted-dns) 匿名化其他網路流量。
|
||||
!!! warning "匿名化 DNS 功能[**不會**](advanced/dns-overview.md#why-shouldnt-i-use-encrypted-dns) 匿名化其他網路流量。"
|
||||
|
||||
[:octicons-repo-16: Repository](https://github.com/DNSCrypt/dnscrypt-proxy){ .md-button .md-button--primary }
|
||||
[:octicons-info-16:](https://github.com/DNSCrypt/dnscrypt-proxy/wiki){ .card-link title=Documentation}
|
||||
|
||||
@ -9,7 +9,7 @@ cover: email-clients.png
|
||||
|
||||
??? warning "電子郵件不提供前向保密"
|
||||
|
||||
當使用端到端加密（ E2EE ）技術（如OpenPGP ）時，電子郵件仍然會有一些未在電子郵件標頭中加密的[一些中繼數據] （ email.md#email-metadata-overview ）。
|
||||
當使用端到端加密（ E2EE ）技術（如OpenPGP ）時，電子郵件仍然會有一些未在電子郵件標頭中加密的[一些中繼數據](email.md#email-metadata-overview)。
|
||||
|
||||
OpenPGP 也不支援 [前向保密](https://en.wikipedia.org/wiki/Forward_secrecy) ，這意味著如果你或收件人的私鑰被盜，所有以前用它加密的訊息都會被曝光： [如何保護我的私鑰？](basics/email-security.md)考慮使用提供前向保密的媒介：
|
||||
|
||||
@ -45,12 +45,12 @@ cover: email-clients.png
|
||||
|
||||
##### 網頁內容
|
||||
|
||||
- [ ]取消勾選 **記住我訪問過的網站和連結**
|
||||
- [ ]取消勾選 **接受來自網站的cookie**
|
||||
- [ ] 取消勾選 **記住我訪問過的網站和連結**
|
||||
- [ ] 取消勾選 **接受來自網站的cookie**
|
||||
|
||||
##### 遙測
|
||||
|
||||
- [ ]取消勾選 **允許Thunderbird 向Mozilla**發送技術和互動資訊。
|
||||
- [ ] 取消勾選 **允許Thunderbird 向Mozilla**發送技術和互動資訊。
|
||||
|
||||
#### Thunderbird-user.js （進階）
|
||||
|
||||
|
||||
@ -115,7 +115,7 @@ cover: frontends.png
|
||||
!!! recommendation
|
||||
|
||||
{ align=right }
|
||||
{ align = right }
|
||||
{ align=right }
|
||||
|
||||
**LibreTube** 是一款免費的 [YouTube](https://youtube.com)開源Android應用程序，使用 [Piped](# piped) API。
|
||||
|
||||
|
||||
@ -52,13 +52,13 @@ schema:
|
||||
|
||||
冀望您所有的資料完全免受任何人的侵害是不實際、昂貴且耗神的。 但別擔心 安全是一種過程，向前思考以製定出一個適合您的正確計劃。 安全性不是只限於您使用的工具或下載的軟件。 相反，它始於了解您面臨的獨特威脅，以及如何減輕它們。
|
||||
|
||||
==這個識別威脅和定義對策的過程稱為 **威脅模型**= = ，它構成了完整安全和隱私計劃的基礎。
|
||||
==這個識別威脅和定義對策的過程稱為 **威脅模型**== ，它構成了完整安全和隱私計劃的基礎。
|
||||
|
||||
[:material-book-outline: 了解更多關於威脅建模](basics/threat-modeling.md){class = "md-button md-button--primary"}
|
||||
|
||||
---
|
||||
|
||||
## ## 我们需要你！ 參與方式如下：
|
||||
## 我们需要你！ 參與方式如下：
|
||||
|
||||
[:simple-discourse:](https://discuss.privacyguides.net/){title = "加入我們的論壇"}
|
||||
[:simple-mastodon:](https://mastodon.neat.computer/@privacyguides){rel = me title = "關注我們的Mastodon"}
|
||||
|
||||
@ -72,6 +72,10 @@ We have sometimes found that the syntax for inserting an image like above was mi
|
||||
|
||||
For examples like the above admonitions, quotation marks, e.g.: `" "` must be used to specify string text. MkDocs will not correctly interpret other symbols i.e., `「 」` or `« »`. Other punctuation marks are fine for marking regular quotations within the text otherwise.
|
||||
|
||||
## Brackets
|
||||
## Fullwidth alternatives and Markdown syntax
|
||||
|
||||
Markdown links must use brackets i.e. `[Example link](https://example.com)`. CJK style brackets such as `（ ）` will not work for links. Crowdin will often handle links automatically, but you may encounter these links inside admonitions and other customized blocks of text.
|
||||
CJK writing systems tend to use alternative "fullwidth" variants of common symbols. These are different characters and cannot be used for markdown syntax.
|
||||
|
||||
- Links must use regular parenthesis ie `(` (Left Parenthesis U+0028) and `)` (Right Parenthesis U+0029) and not `（` (Fullwidth Left Parenthesis U+FF08) or `）` (Fullwidth Right Parenthesis U+FF09)
|
||||
- Indented quoted text must use `:` (Colon U+003A) and not `：` (Fullwidth Colon U+FF1A)
|
||||
- Pictures must use `!` (Exclamation Mark U+0021) and not `！` (Fullwidth Exclamation Mark U+FF01)
|
||||
|
||||
@ -47,11 +47,11 @@ cover: vpn.png
|
||||
|
||||
??? downloads "下載"
|
||||
|
||||
- [:simple-googleplay: Google Play] (https://play.google.com/store/apps/details?id=ch.protonvpn.android)
|
||||
- [:simple-appstore: App Store] (https://apps.apple.com/app/apple-store/id1437005085)
|
||||
- [:simple-github: GitHub] (https://github.com/ProtonVPN/android-app/releases)
|
||||
- [:simple-windows11: Windows] (https://protonvpn.com/download-windows)
|
||||
- [:simple-linux: Linux] (https://protonvpn.com/support/linux-vpn-setup/)
|
||||
- [:simple-googleplay: Google Play](https://play.google.com/store/apps/details?id=ch.protonvpn.android)
|
||||
- [:simple-appstore: App Store](https://apps.apple.com/app/apple-store/id1437005085)
|
||||
- [:simple-github: GitHub](https://github.com/ProtonVPN/android-app/releases)
|
||||
- [:simple-windows11: Windows](https://protonvpn.com/download-windows)
|
||||
- [:simple-linux: Linux](https://protonvpn.com/support/linux-vpn-setup/)
|
||||
|
||||
#### :material-check:{ .pg-green } 67個國家
|
||||
|
||||
@ -194,7 +194,7 @@ IVPN 客戶端支援雙因素驗證（Mullvad 客戶端不支援）。 IVPN 有"
|
||||
- [:simple-github: GitHub](https://github.com/mullvad/mullvadvpn-app/releases)
|
||||
- [:simple-windows11: Windows](https://mullvad.net/en/download/windows/)
|
||||
- [:simple-apple: macOS](https://mullvad.net/en/download/macos/)
|
||||
- [:simple-linux:](https://mullvad.net/en/download/linux/)
|
||||
- [:simple-linux: Linux](https://mullvad.net/en/download/linux/)
|
||||
|
||||
|
||||
|
||||
|
||||
@ -72,6 +72,10 @@ We have sometimes found that the syntax for inserting an image like above was mi
|
||||
|
||||
For examples like the above admonitions, quotation marks, e.g.: `" "` must be used to specify string text. MkDocs will not correctly interpret other symbols i.e., `「 」` or `« »`. Other punctuation marks are fine for marking regular quotations within the text otherwise.
|
||||
|
||||
## Brackets
|
||||
## Fullwidth alternatives and Markdown syntax
|
||||
|
||||
Markdown links must use brackets i.e. `[Example link](https://example.com)`. CJK style brackets such as `（ ）` will not work for links. Crowdin will often handle links automatically, but you may encounter these links inside admonitions and other customized blocks of text.
|
||||
CJK writing systems tend to use alternative "fullwidth" variants of common symbols. These are different characters and cannot be used for markdown syntax.
|
||||
|
||||
- Links must use regular parenthesis ie `(` (Left Parenthesis U+0028) and `)` (Right Parenthesis U+0029) and not `（` (Fullwidth Left Parenthesis U+FF08) or `）` (Fullwidth Right Parenthesis U+FF09)
|
||||
- Indented quoted text must use `:` (Colon U+003A) and not `：` (Fullwidth Colon U+FF1A)
|
||||
- Pictures must use `!` (Exclamation Mark U+0021) and not `！` (Fullwidth Exclamation Mark U+FF01)
|
||||
|
||||
@ -5,47 +5,47 @@ config:
|
||||
copyright:
|
||||
-
|
||||
1: |
|
||||
Privacy Guides is a non-profit, socially motivated website that provides information for protecting your data security and privacy.
|
||||
Privacy Guides یک وبسایت غیرانتفاعی و با هدف اجتماعی است که اطلاعاتی را درباره حفاظت از امنیت و حریم خصوصی دادههای شما ارائه میدهد.
|
||||
-
|
||||
2: |
|
||||
We do not make money from recommending certain products, and we do not use affiliate links.
|
||||
ما از توصیه محصولات خاصی به منظور کسب درآمد استفاده نمیکنیم و از پیوندهای همکاری (Affiliate) نیز استفاده نمیکنیم.
|
||||
-
|
||||
3: |
|
||||
Privacy Guides and contributors.
|
||||
راهنماهای حریم خصوصی و همکاران.
|
||||
-
|
||||
4: |
|
||||
Content licensed under CC BY-ND 4.0.
|
||||
محتوا تحت مجوز CC BY-ND 4.0 منتشر شده است.
|
||||
feedback:
|
||||
question: Was this page helpful?
|
||||
yes: This page was helpful
|
||||
yes-note: Thanks for your feedback!
|
||||
no: This page could be improved
|
||||
question: آیا محتوای این صفحه مفید بود؟
|
||||
yes: محتوای این صفحه مفید بود
|
||||
yes-note: از بازخوردتان سپاس گزاریم!
|
||||
no: محتوای این صفحه میتواند بهتر شود
|
||||
no-note: |
|
||||
Thanks for your feedback! Help us improve this page by opening a discussion on our forum.
|
||||
از بازخورد شما سپاسگزاریم! با باز کردن یک بحث جدید در انجمن به بهبودن محتوای این صفحه کمک کنید.
|
||||
theme:
|
||||
dark: Switch to dark mode
|
||||
light: Switch to light mode
|
||||
system: Switch to system theme
|
||||
dark: تغییر به حالت تاریک
|
||||
light: تغییر به حالت روشن
|
||||
system: تغییر به تم سیستم
|
||||
nav:
|
||||
Home: خانه
|
||||
Knowledge Base: پایگاه دانش
|
||||
Technology Essentials: Technology Essentials
|
||||
Technology Essentials: ضرورتهای فناوری
|
||||
Operating Systems: سیستم عامل
|
||||
Advanced Topics: Advanced Topics
|
||||
Recommendations: Recommendations
|
||||
Internet Browsing: Internet Browsing
|
||||
Providers: Providers
|
||||
Software: Software
|
||||
About: About
|
||||
Community: Community
|
||||
Online Services: Online Services
|
||||
Code of Conduct: Code of Conduct
|
||||
Contributing: Contributing
|
||||
Writing Guide: Writing Guide
|
||||
Technical Guides: Technical Guides
|
||||
Changelog: Changelog
|
||||
Forum: Forum
|
||||
Blog: Blog
|
||||
Advanced Topics: مباحث پیشرفته
|
||||
Recommendations: پیشنهادات
|
||||
Internet Browsing: گشت و گزار در اینترنت
|
||||
Providers: تامینکنندهگان
|
||||
Software: نرم افزار
|
||||
About: درباره ما
|
||||
Community: انجمن
|
||||
Online Services: خدمات آنلاین
|
||||
Code of Conduct: منشور اخلاقی
|
||||
Contributing: مشارکت
|
||||
Writing Guide: راهنمای نوشتن
|
||||
Technical Guides: راهنمای فنی
|
||||
Changelog: لیست تغییرات
|
||||
Forum: تالار گفتگو
|
||||
Blog: بلاگ
|
||||
site:
|
||||
translation: |
|
||||
You're viewing the English copy of Privacy Guides, translated by our fantastic language team on Crowdin. If you notice an error, or see any untranslated sections on this page, please consider helping out! For more information and tips see our translation guide.
|
||||
شما در حال مشاهده نسخهٔ فارسی از راهنمای حریم خصوصی هستید که توسط تیم زبان فوقالعاده ما در پلتفرم Crowdin ترجمه شده است. اگر هر گونه خطا را مشاهده کردید یا بخشهایی از این صفحه را به صورت ترجمه نشده مشاهده کردید، لطفاً به ما کمک کنید! برای اطلاعات بیشتر و راهنماییها، راهنمای ترجمه ما را مشاهده کنید.
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user