diff options
| author | Ilja <ilja@ilja.space> | 2021-12-12 18:09:21 +0100 |
|---|---|---|
| committer | Ilja <ilja@ilja.space> | 2021-12-12 18:09:21 +0100 |
| commit | 4587f37dd72cfbb75e0fb008237ee3fe430caed1 (patch) | |
| tree | b3dd4e27cbc7403b8395c706e1e21f8a630c1aa8 /src/i18n/zh_Hant.json | |
| parent | a20f1794d0d63497f701d8db91b1b0691fd06d54 (diff) | |
Allow canceling a follow request
When a follow request is sent, but not (yet) accepted, the behaviour is now to cancel the request instead of re sending.
The reason is double
* You couldn't cancel a follow request if you change your mind and the request wasn't answered yet
* Instances don't always correctly process a new follow request when the following is already happening. If something went wrong (e;g. the target server thinks you're following, but your instance thinks you're not yet), it's better to first sent an unfollow. This is the behaviour that Mastodon and most probably most other clients have. Therefore this flow is more tested and expected by other instances.
Diffstat (limited to 'src/i18n/zh_Hant.json')
| -rw-r--r-- | src/i18n/zh_Hant.json | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/src/i18n/zh_Hant.json b/src/i18n/zh_Hant.json index 7af2cf39..2c4dc3fb 100644 --- a/src/i18n/zh_Hant.json +++ b/src/i18n/zh_Hant.json @@ -771,7 +771,6 @@ "follow": "關注", "follow_sent": "請求已發送！", "follow_progress": "請求中…", - "follow_again": "再次發送請求？", "follow_unfollow": "取消關注", "followees": "正在關注", "followers": "關注者", |