Repository navigation
Feed: view preferences (All / My / Following / Followers) and onlyMine #19
Description
Part of #17 — Message composer & feed parity gaps
Web behaviour (/help/messages → Viewing preferences): Settings → View Preferences
chooses what the Home feed shows —
- All Messages — the user's messages plus all public messages
- My Messages — only the user's own
- Following Only — people the user follows, plus their own
- Followers Only — people who follow the user, plus their own
Android has no feed filter at all; getMessages sends only limit/offset.
- Read the account's
viewingPreferenceand apply it to the feed query, usingonlyMinewhere
that is the server-side mechanism (confirm the exact query contract live for the
following/followers variants before building). - Offer an in-feed switcher as well as the Settings control, and persist the choice.
Tests: each preference produces the expected query; switching refreshes the feed.
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
Adron commentedon Sep 16, 2026
Implemented in #103 (branch
issue/19-feed-view-preferences). Closing here — review and any follow-up happens on the PR.The open question in this issue — "confirm the exact query contract live for the following/followers variants" — is answered: there is no such query parameter.
GET /api/messagestakes onlylimit,offset,onlyMineandtag./help/api/messagesstates that a signed-in token personalises the feed and that search is "scoped to your feed visibility (honors yourviewingPreference)", so the server applies the stored preference itself. The implementation therefore PATCHes the preference and reloads, withonlyMine=trueas the per-request mechanism for My Messages only.One thing to consolidate later:
:feature:profile'sSettingsRepository(#33) and the new:core:networkViewingPreferenceStoreare now two independent writers of the same field. Changing the view in Settings will not update an already-composed feed switcher until the feed is re-entered. Avoiding a feature→feature dependency was the right call, but these want one owner — most likely a shared account-preferences module — once both surfaces settle.merge: #19 feed view preferences (PR #103)