Repository navigation
Settings: private account toggle (isPrivateAccount) #34
Description
Part of #31 — Settings & preferences parity — most of PATCH /api/user/update is unreachable from Android
Web behaviour (/help/people, /help/account): an account can be private, which turns
follows into follow requests the owner approves or rejects.
:feature:profile already implements the request side (send/approve/reject) but the account
itself cannot be made private from Android — the setting only exists on the web.
- Add the toggle, sending
isPrivateAccount. - Explain the consequence in-line (existing followers keep access; new follows need approval).
Tests: PATCH round-trip; UI reflects the current state after a refresh.
Filed from the parity review of feature/parity-wip @ 14d7795 against interlinedlist.com (OpenAPI /api/openapi.json, 233 paths) and the public help centre.
Activity
PATCH /api/user/updateis unreachable from Android #31Adron commentedon Sep 16, 2026
Implemented in the PR above (branch
issue/34-settings-private-account). Closing here — review and any follow-up happens on the PR.Placement was taken from the docs rather than guessed:
/help/settings,/help/accountand/help/peopleall put this under Settings → Permissions, so that is where it went, named "Private account" as on the web. The consequence copy is lifted from/help/people→ Private accounts and cited in KDoc.The web's other Permissions item, "Email visibility", was deliberately not built — there is no corresponding field on
GET /api/userorPATCH /api/user/update, so it is not implementable from the API as it stands. Worth confirming whether that is an API gap or a web-only concept.Also checked, since the issue asked: the follow-requests screen is already reachable from the Account tab, so no nav change was needed. It does not show a pending count though, and
GET /api/follow/{userId}/countsreturnspendingRequests— a badge there would be a small, genuine improvement.merge: #34 private account toggle (PR)