# 차단된 사용자는 팔로우 해제할 수 없습니다
**URL:** https://meta.discourse.org/t/banned-members-cannot-be-unfollowed/304256
**Category:** UX
**Tags:** follow
**Created:** [1월 10, 2024, 4:00오후 UTC](https://meta.discourse.org/t/banned-members-cannot-be-unfollowed/304256 "2024-01-10T16:00:54Z")
**Posts on this page:** 1
**Showing post:** 3
### Author:  [@zogstrip](https://meta.discourse.org/u/zogstrip)
#### Post date: [3월 30, 2026, 3:53오후 UTC](https://meta.discourse.org/t/banned-members-cannot-be-unfollowed/304256/3 "2026-03-30T15:53:57Z")
이렇게 하면 해결될 거예요 😉
>
>
> The follow button was completely hidden for suspended, staged, and bot users. Th…is meant that if a user followed someone who was later suspended, they had no way to unfollow them without an admin unsuspending and re-suspending the account.
>
> The root cause was that \`follow-button.gjs\` unconditionally hid the button based on the target user's state, with no distinction between the follow and unfollow actions. On top of that, the \`can\_follow\` serializer field only checked \`allow\_people\_to\_follow\_me\` and not the other states (suspended, staged, bot, self), so the client had to duplicate those checks.
>
> This commit introduces a \`Guardian#can\_follow?\` method as the single source of truth for follow permissions. The serializer delegates to it, and the client simply shows the button when the user is already followed OR can be followed. The \`Updater\` also uses the guardian as a first check, then determines the specific error reason on failure to provide meaningful error messages.
>
> Other cleanups:
> \- Replace manual \`raise if !current\_user\` checks with \`requires\_login\`
> \- Fix mismatched i18n keys (\`cannot\_follow\_\*\` → \`user\_cannot\_follow\_\*\`)
> \- Fix typo in locale ("suspend" → "suspended")
>
> https://meta.discourse.org/t/304256
---
_[View the full topic](https://meta.discourse.org/t/banned-members-cannot-be-unfollowed/304256)._