[ds-boyce]

Got this exactly backwards.

[github-actions]

Old size	New size	Diff
7.76 MB	7.76 MB	2 B (0.00%)

---

[mozzius]

I think that's right now. @claude please confirm

[linear-code]

APP-2393

[claude]

Claude finished @mozzius's task in 32s —— View job

---

Confirmation ✅

I reviewed both changes against the followedByOwner join rule logic, and the fix is correct.

The reasoning:

The join rule is followedByOwner — meaning the chat owner must follow you in order for you to join (gate at Root.tsx:124 and GroupChatJoinDialog.tsx:303):

} else if (preview.joinRule === 'followedByOwner' && !isFollowing) {
  // "Only people the chat owner follows can join"
}

On owner.viewer, the two fields mean:

• following → you follow the owner
• followedBy → the owner follows you

Since the rule is "people the chat owner follows", the correct field is followedBy. The previous following had it exactly backwards, as the PR title says. ✅

Both call sites (ChatInvite/Root.tsx:84 and GroupChatJoinDialog.tsx:288) are updated consistently.

Minor nit (non-blocking): the variable is still named isFollowing, which now reads slightly misleadingly since it actually represents "is followed by the owner." Renaming to something like isFollowedByOwner would make the intent clearer, but it's purely cosmetic and not necessary for this fix.
• d/chat-followed-by