Settings & preferences parity — most of PATCH /api/user/update is unreachable from Android #31

Activity

1. Adron

   added

   epicA feature area tracked as a parent issueA feature area tracked as a parent issue

   parityClosing a gap against interlinedlist.comClosing a gap against interlinedlist.com

   P1Big hole in a shipped featureBig hole in a shipped feature

   area:settingsSettings & preferencesSettings & preferences

   on Sep 15, 2026
2. Adron

   added sub-issues on Sep 15, 2026

   • Settings: Message settings group (default visibility, max length, messages per page, advanced post settings) #32
   • Settings: View preferences (viewingPreference) and link previews (showPreviews) #33
   • Settings: private account toggle (isPrivateAccount) #34
   • Settings: notification tray limit (notificationTrayLimit) #35
   • Settings: theme preference synced to the account (theme) #36
   • Settings: profile location (latitude/longitude) with runtime permission #37
3. Adron commented on Sep 16, 2026

   

   Adron

   on Sep 16, 2026

   MemberAuthor

   More actions

   All six sub-issues are done, so closing this epic.

   • Settings: View preferences (viewingPreference) and link previews (showPreviews) #33 — Settings surface + view preferences and link previews → feat(profile): Settings surface + view preferences and link previews (#33) #93
   • Settings: Message settings group (default visibility, max length, messages per page, advanced post settings) #32 — Message settings group → feat(profile): Message settings group — visibility, length, page size, advanced options (#32) #99
   • Settings: private account toggle (isPrivateAccount) #34 — private account toggle → feat(profile): private account toggle under a Permissions group (#34) #105
   • Settings: notification tray limit (notificationTrayLimit) #35 — notification tray limit (and both consumers honour it) → feat: notification tray limit — setting plus both consumers (#35) #112
   • Settings: theme preference synced to the account (theme) #36 — theme synced to the account → feat(profile): sync the theme preference to the account, two-way (#36) #118
   • Settings: profile location (latitude/longitude) with runtime permission #37 — profile location → feat(profile): profile location — coarse capture, manual entry, and an honest non-clear (#37) #130

   All fifteen PATCH /api/user/update fields are now modelled, and every one that has a meaningful Android surface has one.

   Four things this epic established that are worth keeping:

   viewingPreference accepts only my_messages, all_messages, followers_only, following_only — confirmed from the server's own 400. The first implementation guessed all/mine/following/followers, which would have been rejected on every write.

   theme is not validated at all — "not-a-theme", "sepia", "SYSTEM" and "" were each accepted and stored verbatim with a 200. Any client can put an account into a theme no client can render, so Android is deliberately the conservative side.

   latitude/longitude cannot be unset — null, empty string and "null" all 400, and omission means "leave unchanged". That is an API gap; see #130.

   The spec's request-side types are a generator artifact. It types maxMessageLength, messagesPerPage, showPreviews etc. as string while typing isPrivateAccount as boolean, and the live response returns all of them as their natural JSON types. The app sends natural types, now asserted in tests.

   One item was not implementable: the web's Permissions section has an Email visibility setting with no corresponding field on GET /api/user or PATCH /api/user/update. Worth confirming whether that is an API gap or a web-only concept.

   Follow-up still open: #104 (consolidate the now-three readers/writers of account preferences behind one owner).
4. Adron

   closed this as completedon Sep 16, 2026