Summary
When using Phanpy with a Hollo instance, content warnings appear to be permanently collapsed with no way to change this default. The likely cause is that GET /api/v1/preferences returns "reading:expand:spoilers": false as a hardcoded value, and Phanpy has no built-in UI to override it — it relies on the server preference.
Steps to reproduce
- Connect Phanpy to a Hollo instance
- Observe that all CW posts are collapsed by default
- Check that there is no setting in Phanpy to change this — Phanpy defers to the server preference
- Verify:
curl -H "Authorization: Bearer <token>" https://<hollo-instance>/api/v1/preferences returns "reading:expand:spoilers": false
Expected behavior
Users should be able to configure whether content warnings are expanded by default. If Hollo does not yet have a settings UI for this, changing the hardcoded value from false to true would at minimum be a safer default — unexpectedly hiding content is generally worse UX than showing it.
Notes
We haven't verified this exhaustively against the Phanpy source or other clients, so some details may be off. But the core issue — that reading:expand:spoilers appears hardcoded in the preferences endpoint with no way for the user to change it — seems clear from inspecting src/api/v1/index.ts, which appears to have a // TODO comment on the preferences handler.
References
Summary
When using Phanpy with a Hollo instance, content warnings appear to be permanently collapsed with no way to change this default. The likely cause is that
GET /api/v1/preferencesreturns"reading:expand:spoilers": falseas a hardcoded value, and Phanpy has no built-in UI to override it — it relies on the server preference.Steps to reproduce
curl -H "Authorization: Bearer <token>" https://<hollo-instance>/api/v1/preferencesreturns"reading:expand:spoilers": falseExpected behavior
Users should be able to configure whether content warnings are expanded by default. If Hollo does not yet have a settings UI for this, changing the hardcoded value from
falsetotruewould at minimum be a safer default — unexpectedly hiding content is generally worse UX than showing it.Notes
We haven't verified this exhaustively against the Phanpy source or other clients, so some details may be off. But the core issue — that
reading:expand:spoilersappears hardcoded in the preferences endpoint with no way for the user to change it — seems clear from inspectingsrc/api/v1/index.ts, which appears to have a// TODOcomment on the preferences handler.References