New Crowdin translations by GitHub Action

i18n/zh-Hant/basics/account-creation.md

@@ -53,17 +53,21 @@ OAuth 是一種驗證協定可在註冊服務時無須對供應商分享註冊
 
 主要優勢是：
 
-- **安全性**：沒有涉及 [資料外洩](https://en.wikipedia.org/wiki/Data_breach) 的風險，因為網站沒有儲存您的憑證。
+- **Security**: you don't have to trust the security practices of the service you're logging into when it comes to storing your login credentials, because they are stored with the external OAuth provider, which when it comes to services like Apple and Google typically follow the best security practices, continuously audit their authentication systems, and don't store credentials inappropriately (such as in plain text).
 - **易用性**：多個帳戶由單一登入管理。
 
 但也有一些缺陷：
 
 - **隱私**: OAuth 讓您利用已註冊的服務作登入新服務。
-- **集中化**: 如果您使用的 OAuth 帳戶被駭或是無法利用它登入，與之連結的其它帳戶也會受到影響。
+- **Centralization**: if the account you use for OAuth is compromised, or you aren't able to log in to it, all other accounts connected to it are affected.
 
-OAuth 在那些服務之間深度整合情況下，可以特別有用。 我們建議將 OAuth 限制在需要的地方，用 [MFA](multi-factor-authentication.md)來保護主帳戶。
+OAuth can be especially useful in those situations where you could benefit from deeper integration between services. 我們建議將 OAuth 限制在需要的地方，用 [MFA](multi-factor-authentication.md)來保護主帳戶。
 
-所有使用 OAuth 的服務都將與您的基礎提供商帳戶一樣安全。 例如，想用硬體密鑰保護某個帳戶，但該服務不支持硬體密鑰，則可用硬體密鑰保護您的 OAuth 帳戶，現在您所有帳戶基本上都有硬體 MFA。 但值得注意的是，OAuth 帳戶的弱認證意味著與該登入方式相關的其它帳戶也會很弱。
+All the services that use OAuth will be as secure as your underlying OAuth provider's account. 例如，想用硬體密鑰保護某個帳戶，但該服務不支持硬體密鑰，則可用硬體密鑰保護您的 OAuth 帳戶，現在您所有帳戶基本上都有硬體 MFA。 但值得注意的是，OAuth 帳戶的弱認證意味著與該登入方式相關的其它帳戶也會很弱。
+
+There is an additional danger when using *Sign in with Google*, *Facebook*, or another service, which is that typically the OAuth process allows for *bidirectional* data sharing. For example, logging in to a forum with your Twitter account could grant that forum access to do things on your Twitter account such as post, read your messages, or access other personal data. OAuth providers will typically present you with a list of things you are granting the external service access to, and you should always ensure that you read through that list and don't inadvertently grant the external service access to anything it doesn't require.
+
+Malicious applications, particularly on mobile devices where the application has access to the WebView session used for logging in to the OAuth provider, can also abuse this process by hijacking your session with the OAuth provider and gaining access to your OAuth account through those means. Using the *Sign in with* option with any provider should usually be considered a matter of convenience that you only use with services you trust to not be actively malicious.
 
 ### 電話號碼