Repository navigation
DMs: explain who can be messaged when the recipient list is empty #86
Description
Part of #84 — Direct Messages parity gaps
/help/direct-messages → Who you can message: DMs are constrained to a defined set of people
(mutual follows in practice). GET /api/dm/recipients returns that set.
When it is empty — which is the normal state for a new account — the Android picker shows nothing
and reads as broken.
- Replace the empty picker with an explanation of the rule and a route to find and follow people.
Tests: empty-recipients state renders the explanation, not a blank list.
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 #95 (branch
issue/86-dm-recipient-rule). Closing here — review and any follow-up happens on the PR.The rule turned out to be unambiguous, so no guesswork was needed:
/help/direct-messagesstates it as mutual follow (both follow requests approved), plus a block exclusion, and explicitly documents the empty-picker case. The shipped copy is phrased to stay true whichever reason produced the empty set.merge: #86 DM recipient empty-state rule (PR #95)