Phanpy

Reduce timeline density by restructuring boosts and threads

When a fetched page contains enough boosts, Boosts Carousel groups them so original posts occupy more of the main flow. For threads, Phanpy follows inReplyToId toward the root with up to three extra API requests and shows a Thread 1/X-style badge when it can determine the index. Hashtag-heavy paragraphs collapse, while filtered posts use warnings, hover previews, and long-press peeking for graduated disclosure.

Sources: [1]

Use multiple accounts and view modes in one static app

Features include multiple accounts, a detachable compose window, light, dark, and automatic themes, grouped notifications, nested replies, and recovery of unsent drafts. Shortcuts provide views such as multi-column and tab bar, alongside multi-hashtag timelines. Translation uses gettext .po catalogs and Crowdin, with internationalization details including right-to-left layout support.

Sources: [1]

For people who choose reading flow and a clear UI point of view over metrics

Reply, boost, favourite, and similar actions stay hidden until an individual post is opened, and timeline video or GIF content does not autoplay. It fits people who want to try a client that intentionally removes common engagement prompts. Because it is a pure static app, communities can also build it with their own default instance, language, and privacy-policy settings.

Sources: [1]

Account for accessibility, external services, and maintainer capacity

The README says accessibility is not complete and the app is not intended as a comprehensive replacement for Mastodon's existing front end. The official deployment is a static site on Cloudflare Pages, but each connected Mastodon server has its own privacy policy and translations use the external TransLang API by default. Anonymous usage statistics use Cloudflare Web Analytics, and only the development site sends error logs to Rollbar.

Self-hosting recommends a custom build from the production branch with Node.js 22 or newer; prebuilt release archives are explicitly not recommended. Only the latest production release receives security updates, and OAuth tokens must be treated like passwords. The policy also warns that this free-time solo maintainer may need weeks or longer to respond, so operators should plan timely upgrades and a fallback for urgent issues.

Sources: [1][2][3]