1
0
mirror of https://github.com/privacyguides/i18n.git synced 2025-08-28 17:09:16 +00:00

New Crowdin translations by GitHub Action

This commit is contained in:
Crowdin Bot
2023-05-03 04:04:24 +00:00
parent 0f473b4b12
commit b4e22a299c
122 changed files with 1968 additions and 376 deletions

View File

@@ -1,53 +1,53 @@
# Community Code of Conduct
# 社區行為守則
**We pledge** to make our community a harassment-free experience for everyone.
**我們承諾** 打造一個沒有人受騷擾的社區。
**We strive** to create a positive environment, using welcoming and inclusive language, and being respectful of the viewpoints of others.
**我們致力於**打造正向環境、 使用歡迎包容語言、尊重接納別人的觀點。
**We do not allow** inappropriate or otherwise unacceptable behavior, such as sexualized language, trolling and insulting comments, or otherwise promoting intolerance or harassment.
**我們不允許**不適當的行為,例如性用語、捉弄與侮辱評論、鼓吹對立或騷擾。
## Community Standards
## 社區標準
What we expect from members of our communities:
我們對社區成員的期許:
1. **Don't spread misinformation**
1. **不要散佈不實消息**
We are creating an evidence-based educational community around information privacy and security, not a home for conspiracy theories. For example, when making a claim that a certain piece of software is malicious or that certain telemetry data is privacy invasive, explain in detail what is collected and how it collected. Claims of this nature must be backed by technical evidence.
我們欲打造一個以證據為基石的教育社區,用來討論資訊隱私與安全,而不是陰謀論的溫床。 例如,聲稱某個軟體是惡意軟體或某些遙測資訊侵犯隱私時,請詳細解釋收集的內容和收集方式。 宣稱的本質必須有技術證據支撐。
1. **Don't abuse our willingness to help**
1. **請勿濫用別人幫忙的善意**
Our community members are not your free tech support. We are happy to help you with specific steps on your privacy journey if you are willing to put in effort on your end. We are not willing to answer endlessly repeated questions about generic computer problems you could have answered yourself with a 30-second internet search. Don't be a [help vampire](https://slash7.com/2006/12/22/vampires/).
社區成員並不是免費的技術支援者 如果您願意為此付出努力,我們很樂意幫助您完成隱私之旅的具體步驟。 我們不願回答一再重複的電腦常見問題,它們只需花 30 秒網路搜尋即可找到答案。 不要 [助紂為虐](https://slash7.com/2006/12/22/vampires/)
1. **Behave in a positive and constructive manner**
1. **舉止要積極正向**
Examples of behavior that contributes to a positive environment for our community include:
有助於為社區創造積極環境的行為示例包括:
- Demonstrating empathy and kindness toward other people
- Being respectful of differing opinions, viewpoints, and experiences
- Giving and gracefully accepting constructive feedback
- Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
- Focusing on what is best not just for us as individuals, but for the overall community
- 表現出對他人的同情和友善
- 尊重各種不同的觀點和經驗
- 給予並優雅地接受建設性反饋
- 承擔責任並向因我們錯誤而受影響的人道歉,從經驗中吸取教訓
- 專注於不僅對個人也對整個社區最有利的事情
### Unacceptable Behavior
### 不允許的行為
The following behaviors are considered harassment and are unacceptable within our community:
以下行為被視為騷擾,本社區不認可這些行為:
- The use of sexualized language or imagery, and sexual attention or advances of any kind
- Trolling, insulting or derogatory comments, and personal or political attacks
- Public or private harassment
- Publishing others' private information, such as a physical or email address, without their explicit permission
- Other conduct which could reasonably be considered inappropriate in a professional setting
- 使用帶有性暗示的言語或圖像或不受歡迎的性關注
- 惡意破壞、貶損他人評論與人身攻擊
- 公開或私下場合騷擾他人
- 未經許可的公開其他人的個資,如住址、電郵
- 任何在一個專業的場合下被合理的認為不應出現的行為
## Scope
## 範圍
Our Code of Conduct applies within all project spaces, as well as when an individual is representing the Privacy Guides project in other communities.
我們的行為守則適用在專案的各個面向,也適用於在外代表 Privacy Guides 的個人。
We are responsible for clarifying the standards of our community, and have the right to remove or alter the comments of those participating within our community, as necessary and at our discretion.
我們有責任闡明社區標準,並有權在必要時自行決定刪除或更改社區參與者的評論。
### Contact
### 聯絡
If you observe a problem on a platform like Matrix or Reddit, please contact our moderators on that platform in chat, via DM, or through any designated "Modmail" system.
如果在 Matrix Reddit 等平台上發現問題請通過聊天、DM 或任何指定的“Modmail”系統聯繫我們在該平台上的版主。
If you have a problem elsewhere, or a problem our community moderators are unable to resolve, reach out to `jonah@privacyguides.org` and/or `dngray@privacyguides.org`.
如果您有其它問題或困難而本社區的版主管理員無法處理, 請聯絡: `jonah@privacyguides.org` `dngray@privacyguides.org`.
All community leaders are obligated to respect the privacy and security of the reporter of any incident.
所有社區領導人有義務尊重事件申報人的隱私與安全。

View File

@@ -222,7 +222,7 @@ Pixel 手機很容易安裝 GrapheneOS 只需依其 [網頁安裝程式](https:/
![Auditor logo](assets/img/android/auditor.svg#only-light){ align=right }
![Auditor logo](assets/img/android/auditor-dark.svg#only-dark){ align=right }
**Auditor** is an app which leverages hardware security features to provide device integrity monitoring by actively validating the identity of a device and the integrity of its operating system. Currently, it only works with GrapheneOS or the stock operating system for [supported devices](https://attestation.app/about#device-support).
**Auditor** 是一款利用硬體安全功能通過主動驗證設備身份及其作業系統的完整性來進行完整性監控的應用程式。 目前僅在 GrapheneOS 或 [支援設備](https://attestation.app/about#device-support)的庫存作業系統運行。
[:octicons-home-16: Homepage](https://attestation.app){ .md-button .md-button--primary }
[:octicons-eye-16:](https://attestation.app/privacy-policy){ .card-link title="Privacy Policy" }
@@ -238,9 +238,9 @@ Pixel 手機很容易安裝 GrapheneOS 只需依其 [網頁安裝程式](https:/
Auditor 通過下列方式鑑證和入侵檢測。
- Using a [Trust On First Use (TOFU)](https://en.wikipedia.org/wiki/Trust_on_first_use) model between an *auditor* and *auditee*, the pair establish a private key in the [hardware-backed keystore](https://source.android.com/security/keystore/) of the *Auditor*.
- The *auditor* can either be another instance of the Auditor app or the [Remote Attestation Service](https://attestation.app).
- The *auditor* records the current state and configuration of the *auditee*.
- *審計者 * 和 *被審計對象*之間使用 [首次使用信任(TOFU](https://en.wikipedia.org/wiki/Trust_on_first_use) 模式, Auditor *的硬體支援密鑰庫</a> 中對配建立私鑰。
- *審計者* 可以是 Auditor 應用程式的另一個實例,或是 [遠程認證服務](https://attestation.app)
- *審計者* 記錄 *審計對象*當前的狀態和配置。
- 如果在配對完成後發生篡改 *審計對象的作業系統* ,審計人員將意識到設備狀態和配置的變化。
- 您會被提醒注意此一變化。
@@ -255,7 +255,7 @@ Auditor 通過下列方式鑑證和入侵檢測。
![Secure camera logo](assets/img/android/secure_camera.svg#only-light){ align=right }
![Secure camera logo](assets/img/android/secure_camera-dark.svg#only-dark){ align=right }
**Secure Camera** is a camera app focused on privacy and security which can capture images, videos and QR codes. CameraX vendor extensions (Portrait, HDR, Night Sight, Face Retouch, and Auto) are also supported on available devices.
**Secure Camera** 專注於隱私和安全的相機應用,可以捕捉圖像、影片和二維碼。 CameraX 供應商擴展肖像、HDR、夜視、面部修飾和自動也支持可用設備。
[:octicons-repo-16: Repository](https://github.com/GrapheneOS/Camera){ .md-button .md-button--primary }
[:octicons-info-16:](https://grapheneos.org/usage#camera){ .card-link title=Documentation}
@@ -268,17 +268,17 @@ Auditor 通過下列方式鑑證和入侵檢測。
- [:simple-github: GitHub](https://github.com/GrapheneOS/Camera/releases)
- [:material-cube-outline: GrapheneOS App Store](https://github.com/GrapheneOS/Apps/releases)
Main privacy features include:
主要隱私功能包括:
- Auto removal of [Exif](https://en.wikipedia.org/wiki/Exif) metadata (enabled by default)
- Use of the new [Media](https://developer.android.com/training/data-storage/shared/media) API, therefore [storage permissions](https://developer.android.com/training/data-storage) are not required
- Microphone permission not required unless you want to record sound
- 自動移除 [Exif](https://en.wikipedia.org/wiki/Exif) 中繼資料 (設預啟用)
- 使用新的 [媒介](https://developer.android.com/training/data-storage/shared/media) API,因此不需要 [儲存權限](https://developer.android.com/training/data-storage)
- 除非需錄制聲音,否則無需麥克風權限。
!!! 備註
Metadata is not currently deleted from video files but that is planned.
目前影片沒有刪除中繼資料,未來計畫要刪除。
The image orientation metadata is not deleted. If you enable location (in Secure Camera) that **won't** be deleted either. If you want to delete that later you will need to use an external app such as [ExifEraser](data-redaction.md#exiferaser).
圖片方向的中繼資料未刪除。 如果 ( Secure Camera) 開啟定位, 也 **不會** 被不會偵測到。 如果之後想刪除,必須使用外部應用如[ExifEraser](data-redaction.md#exiferaser)
### 安全的 PDF 檢視器
@@ -287,7 +287,7 @@ Main privacy features include:
![Secure PDF Viewer logo](assets/img/android/secure_pdf_viewer.svg#only-light){ align=right }
![Secure PDF Viewer logo](assets/img/android/secure_pdf_viewer-dark.svg#only-dark){ align=right }
**Secure PDF Viewer** is a PDF viewer based on [pdf.js](https://en.wikipedia.org/wiki/PDF.js) that doesn't require any permissions. The PDF is fed into a [sandboxed](https://en.wikipedia.org/wiki/Sandbox_(software_development)) [webview](https://developer.android.com/guide/webapps/webview). This means that it doesn't require permission directly to access content or files.
**Secure PDF Viewer** 是基於 [pdf.js](https://en.wikipedia.org/wiki/PDF.js)的PDF 瀏覽器,無需任何權限。 此 PDF 被送入[sandboxed](https://en.wikipedia.org/wiki/Sandbox_(software_development))[webview](https://developer.android.com/guide/webapps/webview)。 這意味著它不需要權限就能直接存取內容或檔案。
[內容安全政策](https://en.wikipedia.org/wiki/Content_Security_Policy)用來強制要求 WebView 內的JavaScript 和造型屬性需全為靜態內容。
@@ -305,7 +305,7 @@ Main privacy features include:
### GrapheneOS App Store
GrapheneOS 應用商店可在 [GitHub](https://github.com/GrapheneOS/Apps/releases)找到。 It supports Android 12 and above and is capable of updating itself. The app store has standalone applications built by the GrapheneOS project such as the [Auditor](https://attestation.app/), [Camera](https://github.com/GrapheneOS/Camera), and [PDF Viewer](https://github.com/GrapheneOS/PdfViewer). If you are looking for these applications, we highly recommend that you get them from GrapheneOS's app store instead of the Play Store, as the apps on their store are signed by the GrapheneOS's project own signature that Google does not have access to.
GrapheneOS 應用商店可在 [GitHub](https://github.com/GrapheneOS/Apps/releases)找到。 它支持Android 12 以上版本,並且能夠自行更新。 該應用商店有 GrapheneOS 專案的獨立應用建制,如 [Auditor](https://attestation.app/)[Camera](https://github.com/GrapheneOS/Camera) [PDF Viewer](https://github.com/GrapheneOS/PdfViewer)。 如果正在尋找這些應用程式,強烈建議從 GrapheneOS 應用程式商店而不是 Google Play 商店獲得,因為 GrapheneOS 會對自家商店的應用程式簽署 Google 無法訪問的簽名。
### Aurora Store
@@ -315,7 +315,7 @@ Google Play商店需要登錄 Google 帳戶,這對隱私來說不是很好。
![Aurora Store logo](assets/img/android/aurora-store.webp){ align=right }
**Aurora Store** is a Google Play Store client which does not require a Google Account, Google Play Services, or microG to download apps.
**Aurora Store** Google Play Store 客戶端,其無須 Google 帳戶 或 microG 即可下戴應用。
[:octicons-home-16: Homepage](https://auroraoss.com/){ .md-button .md-button--primary }
[:octicons-code-16:](https://gitlab.com/AuroraOSS/AuroraStore){ .card-link title="Source Code" }
@@ -324,35 +324,35 @@ Google Play商店需要登錄 Google 帳戶,這對隱私來說不是很好。
- [:simple-gitlab: GitLab](https://gitlab.com/AuroraOSS/AuroraStore/-/releases)
Aurora Store不允許其匿名帳戶下載付費應用程式。 You can optionally log in with your Google account with Aurora Store to download apps you have purchased, which does give access to the list of apps you've installed to Google, however you still benefit from not requiring the full Google Play client and Google Play Services or microG on your device.
Aurora Store不允許其匿名帳戶下載付費應用程式。 您可以選擇使用 Google 帳戶登錄 Aurora Store 來下載所購買的應用程式,這確實可以訪問您的 Google 安裝應用程式列表,但是設備仍可無需完整的Google Play 客戶端、Google Play 服務或microG。
### Manually with RSS Notifications
### 手動使用 RSS 通知
For apps that are released on platforms like GitHub and GitLab, you may be able to add an RSS feed to your [news aggregator](/news-aggregators) that will help you keep track of new releases.
GitHubGitLab 等平台上發布的應用程式,也可在 [新聞聚合器](/news-aggregators) ,添加一個 RSS源有助於追踪新版本消息。
![RSS APK](./assets/img/android/rss-apk-light.png#only-light) ![RSS APK](./assets/img/android/rss-apk-dark.png#only-dark) ![APK Changes](./assets/img/android/rss-changes-light.png#only-light) ![APK Changes](./assets/img/android/rss-changes-dark.png#only-dark)
#### GitHub
On GitHub, using [Secure Camera](#secure-camera) as an example, you would navigate to its [releases page](https://github.com/GrapheneOS/Camera/releases) and append `.atom` to the URL:
GitHub,以 [Secure Camera](#secure-camera) 為例,可以導航到它的 [發布頁](https://github.com/GrapheneOS/Camera/releases) 並在URL 最後加 `.atom`
`https://github.com/GrapheneOS/Camera/releases.atom`
#### GitLab
On GitLab, using [Aurora Store](#aurora-store) as an example, you would navigate to its [project repository](https://gitlab.com/AuroraOSS/AuroraStore) and append `/-/tags?format=atom` to the URL:
GitLab ,以 [Aurora Store](#aurora-store) 為例,可以導航到其 [專案存取庫](https://gitlab.com/AuroraOSS/AuroraStore) 並在URL 最後加 `/-/tags?format=atom`
`https://gitlab.com/AuroraOSS/AuroraStore/-/tags?format=atom`
#### 查驗 APK 指紋碼
If you download APK files to install manually, you can verify their signature with the [`apksigner`](https://developer.android.com/studio/command-line/apksigner) tool, which is a part of Android [build-tools](https://developer.android.com/studio/releases/build-tools).
如果想下載 APK 檔案進行手動安裝,可用 [`apksigner`](https://developer.android.com/studio/command-line/apksigner) 工具驗證其簽名,這是 Android [build-tools](https://developer.android.com/studio/releases/build-tools)的一部分。
1. Install [Java JDK](https://www.oracle.com/java/technologies/downloads/).
1. 安裝 [Java JDK](https://www.oracle.com/java/technologies/downloads/)
2. Download the [Android Studio command line tools](https://developer.android.com/studio#command-tools).
2. 下載 [Android Studio 命令列工具](https://developer.android.com/studio#command-tools).
3. Extract the downloaded archive:
3. 解壓縮下載的存檔:
```bash
unzip commandlinetools-*.zip
@@ -360,13 +360,13 @@ If you download APK files to install manually, you can verify their signature wi
./bin/sdkmanager --sdk_root=./ "build-tools;29.0.3"
```
4. Run the signature verification command:
4. 執行簽名驗證指令:
```bash
./build-tools/29.0.3/apksigner verify --print-certs ../Camera-37.apk
```
5. The resulting hashes can then be compared with another source. Some developers such as Signal [show the fingerprints](https://signal.org/android/apk/) on their website.
5. 產生的雜湊結果可與另一個來源進行比對。 某些開發者例如 Signal 在會其官網顥示其[指紋碼](https://signal.org/android/apk/)
```bash
Signer #1 certificate DN: CN=GrapheneOS
@@ -379,13 +379,13 @@ If you download APK files to install manually, you can verify their signature wi
![F-Droid 圖標](assets/img/android/f-droid.svg){ align=right width=120px }
==We do **not** currently recommend F-Droid as a way to obtain apps.== F-Droid is often recommended as an alternative to Google Play, particularly in the privacy community. The option to add third-party repositories and not be confined to Google's walled garden has led to its popularity. F-Droid 另外還有 [可複制建構](https://f-droid.org/en/docs/Reproducible_Builds/) ,用於一些應用程式,並致力於自由和開源軟體。 然而官方F-Droid 有 [不少問題](https://privsec.dev/posts/android/f-droid-security-issues/)包括客戶端應用、 品質控制、建置方式、簽署和交付套件等等。
==我們 **目前不推薦** 用 F-Droid 來獲取應用程式。== F-Droid 經常被推薦為 Google Play 替代品,特別是隱私社區。 可添加第三方資源庫的選項與不被局限在 Google 圍牆花園,導致了它的流行。 F-Droid 另外還有 [可複制建構](https://f-droid.org/en/docs/Reproducible_Builds/) ,用於一些應用程式,並致力於自由和開源軟體。 然而官方F-Droid 有 [不少問題](https://privsec.dev/posts/android/f-droid-security-issues/)包括客戶端應用、 品質控制、建置方式、簽署和交付套件等等。
由於其構制應用程式的程序F-Droid 官方資源庫中的應用程式經常在更新上落後。 F-Droid 維護者在用自己的密鑰簽署應用程式時也會重複使用套件 ID此作法並不理想因為這給予 F-Droid 團隊終極信任。
其他流行的第三方資源庫,如 [IzzyOnDroid](https://apt.izzysoft.de/fdroid/) ,緩解一些擔憂。 IzzyOnDroid 存儲庫直接從 GitHub 拉取構建,是開發者自己存儲庫的下一個最好的東西。 然而,這不是我們所推薦的,當應用程式進入 F-droid 主倉庫時,通常 [就會從該倉庫刪除](https://github.com/vfsfitvnm/ViMusic/issues/240#issuecomment-1225564446)。 雖然可以理解(因為該特定倉庫的作用是應用程式在為 F-Droid 主倉庫接受之前託管工作),它可能會讓所安裝的應用程式不再收到更新。
That said, the [F-Droid](https://f-droid.org/en/packages/) and [IzzyOnDroid](https://apt.izzysoft.de/fdroid/) repositories are home to countless apps, so they can be a useful tool to search for and discover open-source apps that you can then download through Play Store, Aurora Store, or by getting the APK directly from the developer. 重要的是要記住,這些資源庫裏一些應用程式已多年未更新,可能依賴於不支援的程式庫等,構成潛在的安全風險。 使用這種方法尋找新的應用程式時,應該善用最佳判斷。
也就是說, [F-droid](https://f-droid.org/en/packages/) [IzzyOnDroid](https://apt.izzysoft.de/fdroid/) 存取庫有無數應用程式,所以它們成為搜索和發現開源應用程式的有用工具,然後通過 Play StoreAurora Store 或直接從開發者獲得 APK 下載。 重要的是要記住,這些資源庫裏一些應用程式已多年未更新,可能依賴於不支援的程式庫等,構成潛在的安全風險。 使用這種方法尋找新的應用程式時,應該善用最佳判斷。
!!! 備註
@@ -404,11 +404,11 @@ That said, the [F-Droid](https://f-droid.org/en/packages/) and [IzzyOnDroid](htt
- 必須是開源軟體。
- 必須支援 bootloader 鎖定與自定 AVB 密鑰支援。
- Android 主要系統發布後的 1個月內接受更新。
- Must receive Android feature updates (minor version) within 0-14 days of release.
- Must receive regular security patches within 0-5 days of release.
- Must **not** be "rooted" out of the box.
- Must **not** enable Google Play Services by default.
- Must **not** require system modification to support Google Play Services.
- 必须在发布后0-14天内收到安卓功能更新小版本
- 必須在發布後 5 天內收到定期安全補丁。
- 必須 **不可打破常規地** root 。
- 必須**不要**預設啟用 Google Play 服務。
- 必須 **不用** 系統調配以支援 Google Play 服務。
### 裝置

View File

@@ -0,0 +1,57 @@
---
title: "為什麼隱私很重要"
icon: 'material/shield-account'
---
在此數位資料被狠狠利用的時代,隱私從未如此重要,但許多人認為隱私早已失敗。 它不是 ==您的隱私將被奪取== 亟需關心它。 隱私關乎權力,更重要的是由誰來掌握此權力。
隱私最終關乎人類資訊,這很重要,因為人類資訊會賦予人們權力。 如果關心我們能成為真實、完整和自由人的能力,就必須在意你我資訊的適用規則。 現代社會的大部分內容都是圍繞**資訊**構建。 網上購物、閱讀新聞、查找資料、投票、找路或其他任何事情時,都在依賴資訊。 我們生活在資訊社會,我們的個人資訊很重要,隱私很重要。
## 什麼是隱私?
許多人常把 **隱私****安全**和 **匿名** 這幾個概念搞混。 例如,人們批評各種產品“不私密”,而實際上他們是指這些產品不提供匿名功能。 本網站涵蓋了這三個主題,但重要的是須了解它們之間的區別,以及每個主題何時發揮作用。
**隱私**
:
==隱私是保證您的資料只被你同意的查看者看到。== 例如在即時通訊的情況中,端到端加密所提供隱私讓消息只能被您與收件人看到。
**安全**
:
安全是信任所使用的應用程式——相關人士如他們所說的那樣——保證這些應用程式的安全。 又例如,在網頁瀏覽時 ,透過 HTTPS 憑證提供安全性。
憑證證明您直接與正在訪問的網站對話,防止網路攻擊者讀取或修改與網站之間交流通訊的資料。
**匿名**
:
匿名指沒有一個長期可識別的身份 您可以使用 [Tor](../tor.md) 達成此目的,它允許您使用隨機 IP 地址與網路連接與瀏覽網際網路而不是自己的 IP。
**假名** 是類似概念,它允許您擁有一個持久的識別符號,而無需將此符號與您的真實身份聯繫起來。 如果網上每個人都知道您是 `@GamerGuy12`,但沒有人知道您的真實姓名,那就是您的假名。
這些概念都有重疊,也有可能將這些概念任意組合。 對大多數人來說,最佳狀態是這三個概念都重疊的時候。 然而,實現起來比許多人原本想的更困難。 有時候必須在某些部份讓步,這也沒關係。 這就是**威脅建模**發揮作用之處,讓您可以就使用[軟體和服務](../tools.md) 做出明智決定 。
[:material-book-outline: 了解更多威脅模型](basics/threat-modeling.md ""){.md-button}
## 隱私 vs. 祕密
對隱私運動常見一個反駁論點是,如果一個人**“沒有什麼可隱藏的”,就不需要隱私。**這是危險的誤解,讓人覺得要求隱私的人一定是越軌、犯罪或錯誤。
==不應該混淆隱私和祕密。== 人人都知道浴室裡發生了什麼,但你還是會關上門。 這是因為您需要隱私,而不是保密。 總有一些關於我們的事實——比如,個人健康資訊或性行為——不想讓全世界都知道,這沒關係。 需要隱私是合理合法的,它讓人之所以為人。 隱私是賦予權利來決定自己的資訊,而不是為了隱藏祕密。
## 隱私關乎控制?
隱私一個常見定義是,*控制*誰有權訪問您的資料。 隱私是一個容易掉落的陷阱,事實上這是我們長期以來運營本網站的隱私定義。 聽起來不錯,能打動不少人,但實際上卻無效。
以 cookies 同意表格為例。 在訪問的各種網站,每天可能會遇到幾十次這樣的情況,它們有一系列不錯的複選框和滑塊,可讓您“調整”偏好以完全滿足您的需求。 但最後我們只是點擊了“我同意”按鈕,因為只是想閱讀文章或進行購買。 沒人想在所訪問的各個網站上完成個人隱私審計。 這是[選擇架構](https://en.wikipedia.org/wiki/Choice_architecture)中的練習,旨在讓您走簡單的路線,而不是鑽研配置選項卻是一個不存在迷宮。
==在大多數應用程式中控制隱私是一種幻想。== 它是一個閃亮的儀表板,您可以對自己的資料做出各種選擇,但很少有您正在尋找的選擇,比如“只使用我的資料來幫助我 ” 這種類型的控制旨在讓您對自己的選擇感到內疚,您“可以選擇”讓使用的應用程式更為私密,但您卻不這麼做。
隱私需要融入到默認使用的[軟體和服務](../tools.md),您不能將大多數應用程式變成自己的隱私。
## 來源
- [Why Privacy Matters](https://www.amazon.com/Why-Privacy-Matters-Neil-Richards/dp/0190939044) (2021) by Neil Richards
- [新石油l: 為何隱私 & 安全重要](https://thenewoil.org/en/guides/prologue/why/)
- [@Thorin-Oakenpants on GitHub](https://github.com/privacytools/privacytools.io/issues/1760#issuecomment-597497298)

View File

@@ -44,7 +44,7 @@ schema:
別再把隱私和祕密混為一談 人人都知道浴室裏發生了什麼,但你還是把門關上。 這是因為您需要隱私,而不是保密。 **每個人**都有要保護的東西 隱私讓我們之所以為人
[:material-target-account: 常見網際網路威脅](basics/common-threats.md){class = "md-button md-button--primary"}
[:material-book-outline: 為什麼隱私很重要](basics/why-privacy-matters.md){ class="md-button md-button--primary" }
## 我該怎麼辦

View File

@@ -1,44 +1,44 @@
---
title: Git Recommendations
title: Git 使用建議
---
If you make changes to this website on GitHub.com's web editor directly, you shouldn't have to worry about this. If you are developing locally and/or are a long-term website editor (who should probably be developing locally!), consider these recommendations.
如果想直接在 github.com 網頁編輯器對本站進行修改,則無須擔心此處的建議。 如您使用本地端開發或長期網站編編器(可能為本地端),請參考以下建議。
## Enable SSH Key Commit Signing
## 開啟 SSH 密鑰提交簽署
You can use an existing SSH key for signing, or [create a new one](https://docs.github.com/en/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent).
可使用現有的SSH 密鑰簽署或 [建立新密鑰one](https://docs.github.com/en/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)
1. Configure your Git client to sign commits and tags by default (remove `--global` to only sign by default for this repo):
1. 設置 Git 客戶端以預設簽署提交與標籤(移除 `--global` 以便只對此存取庫作簽署):
```
git config --global commit.gpgsign true
git config --global gpg.format ssh
git config --global tag.gpgSign true
```
2. Copy your SSH public key to your clipboard, for example:
2. 將 SSH 公鑰複製到剪貼板,例如:
```
pbcopy < ~/.ssh/id_ed25519.pub
# Copies the contents of the id_ed25519.pub file to your clipboard
```
3. Set your SSH key for signing in Git with the following command, replacing the last string in quotes with the public key in your clipboard:
3. 利用下方指令在 Git 底下設定 SSH 密鑰簽署,將最後字串置換成剪貼板中的公鑰且前後帶引號:
```
git config --global user.signingkey 'ssh-ed25519 AAAAC3(...) user@example.com'
```
Ensure you [add your SSH key to your GitHub account](https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account#adding-a-new-ssh-key-to-your-account) **as a Signing Key** (as opposed to or in addition to as an Authentication Key).
確認 [加入您 GitHub 帳戶中的 SSH 密鑰](https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account#adding-a-new-ssh-key-to-your-account) **簽署密鑰** (其不同於驗證密鑰)。
## Rebase on Git pull
Use `git pull --rebase` instead of `git pull` when pulling in changes from GitHub to your local machine. This way your local changes will always be "on top of" the latest changes on GitHub, and you avoid merge commits (which are disallowed in this repo).
使用 `git pull --rebase` 取代 `git pull` 以從 Github 把變動提取回本地端機器。 這種方式會使本地端的變動總在 Github 之上,而您可避免合併提交(本取存庫亦不允許)。
You can set this to be the default behavior:
可將它設為默認行為:
```
git config --global pull.rebase true
```
## Rebase from `main` before submitting a PR
## 發送提取請求前,先自 `main`重整。
If you are working on your own branch, run these commands before submitting a PR:
如果是在自建的旁支工作,提取請求前先執行這些指令:
```
git fetch origin