mirror of
https://github.com/privacyguides/i18n.git
synced 2026-06-08 02:09:11 +00:00
New Crowdin translations by GitHub Action
This commit is contained in:
Crowdin Bot
@@ -17,7 +17,7 @@ title: 通用标准
|
||||
我们在考虑新的建议时采用这些优先事项。
|
||||
|
||||
- **安全**：工具应该在适用的地方遵循安全的最佳做法。
|
||||
- **来源的可用性**: 开放源码项目通常比同等的专有替代品更受欢迎。
|
||||
- **Source Availability**: Open-source projects are generally preferred over equivalent proprietary alternatives.
|
||||
- **跨平台**：我们通常倾向于建议跨平台，以避免厂商锁定。
|
||||
- **积极开发**：我们推荐的工具应该积极开发，未维护的项目在大多数情况下会被删除。
|
||||
- **可用性**：工具应该是大多数计算机用户可以使用的，不应该要求有过度的技术背景。
|
||||
|
||||
@@ -81,7 +81,7 @@ So far in 2023 we've launched international translations of our website in [Fren
|
||||
- [:simple-github: GitHub](https://github.com/hook9 "@hook9")
|
||||
- [:simple-mastodon: Mastodon](https://mastodon.neat.computer/@oliviablob "@oliviablob@neat.computer"){rel=me}
|
||||
|
||||
Additionally, [many people](https://github.com/privacyguides/privacyguides.org/graphs/contributors) have made contributions to the project. You can too, we're open sourced on GitHub, and accepting translation suggestions on [Crowdin](https://crowdin.com/project/privacyguides).
|
||||
Additionally, [many people](https://github.com/privacyguides/privacyguides.org/graphs/contributors) have made contributions to the project. You can too, we're open source on GitHub, and accepting translation suggestions on [Crowdin](https://crowdin.com/project/privacyguides).
|
||||
|
||||
Our team members review all changes made to the website and handle administrative duties such as web hosting and financials, however they do not personally profit from any contributions made to this site. Our financials are transparently hosted by the Open Collective Foundation 501(c)(3) at [opencollective.com/privacyguides](https://opencollective.com/privacyguides). Donations to Privacy Guides are generally tax-deductible in the United States.
|
||||
|
||||
|
||||
@@ -8,7 +8,7 @@ title: "Notices and Disclaimers"
|
||||
|
||||
与任何人类努力一样，运行此网站都涉及不确定性和权衡。 我们希望这个网站有所帮助，但它可能包含错误，无法解决所有问题。 如果您对自己的情况有任何疑问，我们建议您自己进行研究，寻求其他专家，并与隐私指南社区进行讨论。 如果您有任何法律问题，请先咨询您自己的法律顾问，然后再继续。
|
||||
|
||||
隐私指南是一个开放源码项目，根据许可证做出贡献，其中包括为了保护网站及其贡献者，明确规定隐私指南项目和网站可“按原样”提供，不提供保证，并且不对使用网站或网站中的任何建议所造成的损害承担责任。 此外， 隐私指南不保证、不代表使用本网站、或其他与资料相关，或任何关联本网站的其他网站上资料的准确性，可能导致的结果或可靠性。
|
||||
Privacy Guides is an open-source project contributed to under licenses that include terms that, for the protection of the website and its contributors, make clear that the Privacy Guides project and website is offered "as-is", without warranty, and disclaiming liability for damages resulting from using the website or any recommendations contained within. 此外， 隐私指南不保证、不代表使用本网站、或其他与资料相关，或任何关联本网站的其他网站上资料的准确性，可能导致的结果或可靠性。
|
||||
|
||||
此外，隐私指南不保证本网站将始终可用或完全可用。
|
||||
|
||||
|
||||
@@ -90,7 +90,7 @@ BurungHantu还在Twitter上发了一篇 [的帖子](https://twitter.com/privacyt
|
||||
|
||||
截至2022年9月25日，我们看到BurungHantu的整体计划在privacytools.io上实现，而这正是我们今天决定创建这个解释页的原因。 他运营的网站似乎是该网站的SEO优化版本，该网站推荐工具以换取经济补偿。 [最近，IVPN和Mullvad这两个VPN供应商几乎被隐私社区普遍推荐为](../vpn.md) ，并因其反对联盟计划的立场而备受关注，被从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 has become exactly the type of site we [warned against](https://web.archive.org/web/20210729205249/https://blog.privacytools.io/the-trouble-with-vpn-and-privacy-reviews/) on the PrivacyTools blog in 2019.**== We've tried to keep our distance from PrivacyTools since the transition, but their continued harassment towards our project and now their absurd abuse of the credibility their brand gained over 6 years of open-source contributions is extremely troubling to us. 我们这些真正为隐私而战的人并不是在相互斗争，也不是从出价最高的人那里得到我们的建议。
|
||||
|
||||
|
||||
|
||||
|
||||
+1
-1
@@ -180,7 +180,7 @@ Google Pixel phones are the **only** devices we recommend for purchase. Pixel ph
|
||||
|
||||
Secure Elements like the Titan M2 are more limited than the processor's Trusted Execution Environment used by most other phones as they are only used for secrets storage, hardware attestation, and rate limiting, not for running "trusted" programs. Phones without a Secure Element have to use the TEE for *all* of those functions, resulting in a larger attack surface.
|
||||
|
||||
Google Pixel phones use a TEE OS called Trusty which is [open-source](https://source.android.com/security/trusty#whyTrusty), unlike many other phones.
|
||||
Google Pixel phones use a TEE OS called Trusty which is [open source](https://source.android.com/security/trusty#whyTrusty), unlike many other phones.
|
||||
|
||||
The installation of GrapheneOS on a Pixel phone is easy with their [web installer](https://grapheneos.org/install/web). If you don't feel comfortable doing it yourself and are willing to spend a bit of extra money, check out the [NitroPhone](https://shop.nitrokey.com/shop) as they come preloaded with GrapheneOS from the reputable [Nitrokey](https://www.nitrokey.com/about) company.
|
||||
|
||||
|
||||
@@ -9,7 +9,7 @@ schema:
|
||||
mainEntity:
|
||||
-
|
||||
"@type": Question
|
||||
name: 开源软件一定安全吗？
|
||||
name: Is open-source software inherently secure?
|
||||
acceptedAnswer:
|
||||
"@type": Answer
|
||||
text: |
|
||||
|
||||
+1
-1
@@ -92,7 +92,7 @@ They have also received the Digital Trust Label, a certification from the [Swiss
|
||||
|
||||
Our best-case criteria represents what we would like to see from the perfect project in this category. Our recommendations may not include any or all of this functionality, but those which do may rank higher than others on this page.
|
||||
|
||||
- 客户端应是开源的。
|
||||
- Clients should be open source.
|
||||
- 客户端应由独立的第三方对其进行全面的审计。
|
||||
- 应提供Linux、Android、Windows、macOS和iOS的本地客户端。
|
||||
- 这些客户端应该与云存储供应商的本地操作系统工具集成，如iOS上的Files应用集成，或Android上的DocumentsProvider功能。
|
||||
|
||||
@@ -55,19 +55,19 @@ cover: data-redaction.webp
|
||||
|
||||
被删除的元数据取决于图像的文件类型。
|
||||
|
||||
* **JPEG**: ICC Profile、Exif、Photoshop Image Resources和XMP/ExtendedXMP元数据如果存在，将被删除。
|
||||
* **PNG**：ICC Profile、Exif和XMP元数据如果存在，将被删除。
|
||||
* **WebP**：ICC Profile、Exif和XMP元数据如果存在，将被删除。
|
||||
- **JPEG**: ICC Profile、Exif、Photoshop Image Resources和XMP/ExtendedXMP元数据如果存在，将被删除。
|
||||
- **PNG**：ICC Profile、Exif和XMP元数据如果存在，将被删除。
|
||||
- **WebP**：ICC Profile、Exif和XMP元数据如果存在，将被删除。
|
||||
|
||||
在处理完图像后，ExifEraser会向你提供一份完整的报告，说明每张图像中到底有哪些被删除。
|
||||
|
||||
该应用程序提供多种方法来消除图像中的元数据。 名称：
|
||||
|
||||
* 你可以用ExifEraser分享另一个应用程序的图像。
|
||||
* 通过应用程序本身，你可以选择一张图片，一次选择多张图片，甚至是整个目录。
|
||||
* 它有一个 "相机 "选项，它使用你的操作系统的相机应用程序来拍摄照片，然后它将元数据从照片中删除。
|
||||
* 它允许你将照片从另一个应用程序拖入ExifEraser，当它们都以分屏模式打开时。
|
||||
* 最后，它允许你从剪贴板上粘贴图片。
|
||||
- 你可以用ExifEraser分享另一个应用程序的图像。
|
||||
- 通过应用程序本身，你可以选择一张图片，一次选择多张图片，甚至是整个目录。
|
||||
- 它有一个 "相机 "选项，它使用你的操作系统的相机应用程序来拍摄照片，然后它将元数据从照片中删除。
|
||||
- 它允许你将照片从另一个应用程序拖入ExifEraser，当它们都以分屏模式打开时。
|
||||
- 最后，它允许你从剪贴板上粘贴图片。
|
||||
|
||||
### Metapho (iOS)
|
||||
|
||||
@@ -143,5 +143,5 @@ cover: data-redaction.webp
|
||||
|
||||
We are working on establishing defined criteria for every section of our site, and this may be subject to change. If you have any questions about our criteria, please [ask on our forum](https://discuss.privacyguides.net/latest) and don't assume we didn't consider something when making our recommendations if it is not listed here. There are many factors considered and discussed when we recommend a project, and documenting every single one is a work-in-progress.
|
||||
|
||||
- 为开源操作系统开发的应用程序必须是开源的。
|
||||
- Apps developed for open-source operating systems must be open source.
|
||||
- 应用程序必须是免费的，不应包括广告或其他限制。
|
||||
|
||||
+1
-1
@@ -185,7 +185,7 @@ While we [recommend against](os/linux-overview.md#release-cycle) "perpetually ou
|
||||
|
||||
Choosing a Linux distro that is right for you will come down to a huge variety of personal preferences, and this page is **not** meant to be an exhaustive list of every viable distribution. Our Linux overview page has some advice on [choosing a distro](os/linux-overview.md#choosing-your-distribution) in more detail. The distros on *this* page do all generally follow the guidelines we covered there, and all meet these standards:
|
||||
|
||||
- Free and open-source.
|
||||
- Free and open source.
|
||||
- Receives regular software and kernel updates.
|
||||
- [Avoids X11](os/linux-overview.md#wayland).
|
||||
- The notable exception here is Qubes, but the isolation issues which X11 typically has are avoided by virtualization. This isolation only applies to apps *running in different qubes* (virtual machines), apps running in the *same* qube are not protected from each other.
|
||||
|
||||
@@ -226,7 +226,7 @@ Canary Mail is closed-source. We recommend it due to the few choices there are f
|
||||
|
||||
### Minimum Qualifications
|
||||
|
||||
- 为开源操作系统开发的应用程序必须是开源的。
|
||||
- Apps developed for open-source operating systems must be open source.
|
||||
- Must not collect telemetry, or have an easy way to disable all telemetry.
|
||||
- Must support OpenPGP message encryption.
|
||||
|
||||
@@ -234,7 +234,7 @@ Canary Mail is closed-source. We recommend it due to the few choices there are f
|
||||
|
||||
Our best-case criteria represents what we would like to see from the perfect project in this category. Our recommendations may not include any or all of this functionality, but those which do may rank higher than others on this page.
|
||||
|
||||
- Should be open-source.
|
||||
- Should be open source.
|
||||
- Should be cross-platform.
|
||||
- Should not collect any telemetry by default.
|
||||
- Should support OpenPGP natively, i.e. without extensions.
|
||||
|
||||
@@ -345,7 +345,7 @@ When encrypting with PGP, you have the option to configure different options in
|
||||
|
||||
### Minimum Qualifications
|
||||
|
||||
- Cross-platform encryption apps must be open-source.
|
||||
- Cross-platform encryption apps must be open source.
|
||||
- File encryption apps must support decryption on Linux, macOS, and Windows.
|
||||
- External disk encryption apps must support decryption on Linux, macOS, and Windows.
|
||||
- Internal (OS) disk encryption apps must be cross-platform or built in to the operating system natively.
|
||||
|
||||
@@ -41,7 +41,7 @@ When you are using an instance run by someone else, make sure to read the privac
|
||||
|
||||
{ align=right }
|
||||
|
||||
**ProxiTok** is an open source frontend to the [TikTok](https://www.tiktok.com) website that is also self-hostable.
|
||||
**ProxiTok** is an open-source frontend to the [TikTok](https://www.tiktok.com) website that is also self-hostable.
|
||||
|
||||
There are a number of public instances, with some instances having [Tor](https://www.torproject.org) onion services support.
|
||||
|
||||
|
||||
@@ -23,12 +23,12 @@ cover: multi-factor-authentication.webp
|
||||
|
||||
The [comparison table](https://www.yubico.com/store/compare/) shows the features and how the YubiKeys compare. We highly recommend that you select keys from the YubiKey 5 Series.
|
||||
|
||||
YubiKeys can be programmed using the [YubiKey Manager](https://www.yubico.com/support/download/yubikey-manager/) or [YubiKey Personalization Tools](https://www.yubico.com/support/download/yubikey-personalization-tools/). For managing TOTP codes, you can use the [Yubico Authenticator](https://www.yubico.com/products/yubico-authenticator/). All of Yubico's clients are open-source.
|
||||
YubiKeys can be programmed using the [YubiKey Manager](https://www.yubico.com/support/download/yubikey-manager/) or [YubiKey Personalization Tools](https://www.yubico.com/support/download/yubikey-personalization-tools/). For managing TOTP codes, you can use the [Yubico Authenticator](https://www.yubico.com/products/yubico-authenticator/). All of Yubico's clients are open source.
|
||||
|
||||
For models which support HOTP and TOTP, there are 2 slots in the OTP interface which could be used for HOTP and 32 slots to store TOTP secrets. These secrets are stored encrypted on the key and never expose them to the devices they are plugged into. Once a seed (shared secret) is given to the Yubico Authenticator, it will only give out the six-digit codes, but never the seed. This security model helps limit what an attacker can do if they compromise one of the devices running the Yubico Authenticator and make the YubiKey resistant to a physical attacker.
|
||||
|
||||
!!! warning
|
||||
The firmware of YubiKey is not open-source and is not updatable. If you want features in newer firmware versions, or if there is a vulnerability in the firmware version you are using, you would need to purchase a new key.
|
||||
The firmware of YubiKey is not open source and is not updatable. If you want features in newer firmware versions, or if there is a vulnerability in the firmware version you are using, you would need to purchase a new key.
|
||||
|
||||
### Nitrokey
|
||||
|
||||
@@ -58,7 +58,7 @@ For the models which support HOTP and TOTP, there are 3 slots for HOTP and 15 fo
|
||||
|
||||
The Nitrokey Pro 2, Nitrokey Storage 2, and the upcoming Nitrokey 3 supports system integrity verification for laptops with the [Coreboot](https://www.coreboot.org/) + [Heads](https://osresearch.net/) firmware.
|
||||
|
||||
Nitrokey's firmware is open-source, unlike the YubiKey. The firmware on modern NitroKey models (except the **NitroKey Pro 2**) is updatable.
|
||||
Nitrokey's firmware is open source, unlike the YubiKey. The firmware on modern NitroKey models (except the **NitroKey Pro 2**) is updatable.
|
||||
|
||||
### Criteria
|
||||
|
||||
|
||||
@@ -132,7 +132,7 @@ Cryptee offers 100MB of storage for free, with paid options if you need more. Si
|
||||
|
||||
We are working on establishing defined criteria for every section of our site, and this may be subject to change. If you have any questions about our criteria, please [ask on our forum](https://discuss.privacyguides.net/latest) and don't assume we didn't consider something when making our recommendations if it is not listed here. There are many factors considered and discussed when we recommend a project, and documenting every single one is a work-in-progress.
|
||||
|
||||
- Clients must be open-source.
|
||||
- Clients must be open source.
|
||||
- Any cloud sync functionality must be E2EE.
|
||||
- Must support exporting documents into a standard format.
|
||||
|
||||
|
||||
@@ -12,7 +12,7 @@ The **Android Open Source Project** is a secure mobile operating system featurin
|
||||
|
||||
### 挑选安卓 ROM
|
||||
|
||||
你买到的安卓手机多半已经预装了能侵犯隐私的应用与服务，而这些服务并不属于 [AOSP](https://source.android.com/)。 例如 Google Play 服务：它有权访问你的文件、联系人、通话记录、短信、定位、相机、麦克风、硬件身份码等。且这些权限无法收回。 这类应用与服务扩大了你的设备的攻击面，也是安卓系统的各种隐私问题的源头。
|
||||
When you buy an Android phone, the device's default operating system often comes with invasive integration with apps and services that are not part of the [Android Open Source Project](https://source.android.com/). 例如 Google Play 服务：它有权访问你的文件、联系人、通话记录、短信、定位、相机、麦克风、硬件身份码等。且这些权限无法收回。 这类应用与服务扩大了你的设备的攻击面，也是安卓系统的各种隐私问题的源头。
|
||||
|
||||
换用一个不预装这类软件的安卓 ROM 可以解决这个问题。 不巧，很多安卓 ROM 不支持 AVB、回滚保护、系统更新、等这些关键的安全功能，破坏了安卓的安全模型。 某些 ROM 发布的版本属于 [`userdebug`](https://source.android.com/setup/build/building#choose-a-target) 构建版本。这个版本通过 [ADB](https://developer.android.com/studio/command-line/adb) 来提供 root 访问，并且为了支持调试，[放宽](https://github.com/LineageOS/android_system_sepolicy/search?q=userdebug&type=code)了 SELinux 规则。这进一步扩大了攻击面，弱化了安全模型。
|
||||
|
||||
|
||||
@@ -18,7 +18,7 @@ There are some notable privacy concerns with Linux which you should be aware of.
|
||||
- 保持 [软件自由](https://www.gnu.org/philosophy/free-sw.en.html#four-freedoms)
|
||||
- Use privacy focused systems such as [Whonix](https://www.whonix.org) or [Tails](https://tails.boum.org/)
|
||||
|
||||
### Open Source Security
|
||||
### Open-Source Security
|
||||
|
||||
It is a [common misconception](../basics/common-misconceptions.md#open-source-software-is-always-secure-or-proprietary-software-is-more-secure) that Linux and other open-source software is inherently secure simply because the source code is available. There is an expectation that community verification occurs regularly, but this isn’t always [the case](https://seirdy.one/posts/2022/02/02/floss-security/).
|
||||
|
||||
|
||||
@@ -161,7 +161,7 @@ Bitwarden also features [Bitwarden Send](https://bitwarden.com/products/send/),
|
||||
|
||||
You need the [Premium Plan](https://bitwarden.com/help/about-bitwarden-plans/#compare-personal-plans) to be able to share files. The free plan only allows text sharing.
|
||||
|
||||
Bitwarden's server-side code is [open-source](https://github.com/bitwarden/server), so if you don't want to use the Bitwarden cloud, you can easily host your own Bitwarden sync server.
|
||||
Bitwarden's server-side code is [open source](https://github.com/bitwarden/server), so if you don't want to use the Bitwarden cloud, you can easily host your own Bitwarden sync server.
|
||||
|
||||
**Vaultwarden** is an alternative implementation of Bitwarden's sync server written in Rust and compatible with official Bitwarden clients, perfect for self-hosted deployment where running the official resource-heavy service might not be ideal. If you are looking to self-host Bitwarden on your own server, you almost certainly want to use Vaultwarden over Bitwarden's official server code.
|
||||
|
||||
@@ -239,7 +239,7 @@ Psono provides extensive documentation for their product. The web-client for Pso
|
||||
Our best-case criteria represents what we would like to see from the perfect project in this category. Our recommendations may not include any or all of this functionality, but those which do may rank higher than others on this page.
|
||||
|
||||
- Telemetry should be opt-in (disabled by default) or not collected at all.
|
||||
- Should be open-source and reasonably self-hostable.
|
||||
- Should be open source and reasonably self-hostable.
|
||||
|
||||
## Local Storage
|
||||
|
||||
|
||||
@@ -60,7 +60,7 @@ Most online office suites do not support E2EE, meaning the cloud provider has ac
|
||||
|
||||
In general, we define collaboration platforms as full-fledged suites which could reasonably act as a replacement to collaboration platforms like Google Drive.
|
||||
|
||||
- 开源
|
||||
- Open source.
|
||||
- Makes files accessible via WebDAV unless it is impossible due to E2EE.
|
||||
- Has sync clients for Linux, macOS, and Windows.
|
||||
- Supports document and spreadsheet editing.
|
||||
@@ -162,11 +162,10 @@ In general, we define office suites as applications which could reasonably act a
|
||||
|
||||
#### Minimum Requirements
|
||||
|
||||
- 必须是开源的。
|
||||
- Must be open source.
|
||||
- Must implement "zero-trust" end-to-end encryption.
|
||||
- Must support password-protected files.
|
||||
|
||||
|
||||
#### Best-Case
|
||||
|
||||
Our best-case criteria represents what we would like to see from the perfect project in this category. Our recommendations may not include any or all of this functionality, but those which do may rank higher than others on this page.
|
||||
|
||||
+1
-1
@@ -29,7 +29,7 @@ You can consult OpenWrt's [table of hardware](https://openwrt.org/toh/start) to
|
||||
|
||||
{ align=right }
|
||||
|
||||
**OPNsense** is an open source, FreeBSD-based firewall and routing platform which incorporates many advanced features such as traffic shaping, load balancing, and VPN capabilities, with many more features available in the form of plugins. OPNsense is commonly deployed as a perimeter firewall, router, wireless access point, DHCP server, DNS server, and VPN endpoint.
|
||||
**OPNsense** is an open-source, FreeBSD-based firewall and routing platform which incorporates many advanced features such as traffic shaping, load balancing, and VPN capabilities, with many more features available in the form of plugins. OPNsense is commonly deployed as a perimeter firewall, router, wireless access point, DHCP server, DNS server, and VPN endpoint.
|
||||
|
||||
[:octicons-home-16: Homepage](https://opnsense.org/){ .md-button .md-button--primary }
|
||||
[:octicons-info-16:](https://docs.opnsense.org/index.html){ .card-link title=Documentation}
|
||||
|
||||
+2
-2
@@ -128,7 +128,7 @@ IVPN has undergone a [no-logging audit from Cure53](https://cure53.de/audit-repo
|
||||
|
||||
#### :material-check:{ .pg-green } Open-Source Clients
|
||||
|
||||
As of February 2020 [IVPN applications are now open-source](https://www.ivpn.net/blog/ivpn-applications-are-now-open-source). Source code can be obtained from their [GitHub organization](https://github.com/ivpn).
|
||||
As of February 2020 [IVPN applications are now open source](https://www.ivpn.net/blog/ivpn-applications-are-now-open-source). Source code can be obtained from their [GitHub organization](https://github.com/ivpn).
|
||||
|
||||
#### :material-check:{ .pg-green } Accepts Cash and Monero
|
||||
|
||||
@@ -237,7 +237,7 @@ Mullvad is very transparent about which nodes they [own or rent](https://mullvad
|
||||
- 支持强大的协议，如WireGuard & OpenVPN。
|
||||
- 客户端内置的杀毒软件。
|
||||
- 多跳支持。 多重跳转对于在单个节点受损的情况下保持数据的私密性非常重要。
|
||||
- 如果提供VPN客户端，它们应该是 [开源的](https://en.wikipedia.org/wiki/Open_source)，就像它们一般内置的VPN软件。 我们相信， [源代码](https://en.wikipedia.org/wiki/Source_code) 的可用性提供了更大的透明度，了解你的设备实际上在做什么。
|
||||
- If VPN clients are provided, they should be [open source](https://en.wikipedia.org/wiki/Open_source), like the VPN software they generally have built into them. 我们相信， [源代码](https://en.wikipedia.org/wiki/Source_code) 的可用性提供了更大的透明度，了解你的设备实际上在做什么。
|
||||
|
||||
**Best Case:**
|
||||
|
||||
|
||||
Reference in New Issue
Block a user