Repository navigation
Tags: trending tags surface (GET /api/tags/trending) #30
Description
Part of #27 — Tags: tagging posts, autocomplete, trending and tag-filtered feeds
- Surface the most-used tags across public messages within the trailing window the endpoint
reports. - Place it where it is actually discoverable on a phone — a section in the feed or a discovery
entry point — rather than a hidden screen. - Each trending tag opens the tag-filtered feed.
Tests: parse the trending payload (including the window metadata); tap → tag 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 the PR above (branch
issue/30-trending-tags). Closing here — review and any follow-up happens on the PR.This issue's premise about the window is wrong, and worth correcting in the record:
windowis a request parameter (day|week|month, defaultweek), and the response reports nothing about the period — it is a bare{"tags":[{"tag","count","lastUsedAt"}]}. So there was no window metadata to surface.Worse, the server silently falls back to
weekfor an unrecognisedwindow—?window=bogusreturned byte-identical results to?window=weekwith no error. That is the third endpoint found with accept-and-quietly-rewrite behaviour, after saved-viewconfig.mode(#51) andtheme(#36). The app therefore sends the window explicitly and labels the rail from what it requested, not from what the API claims.With this, all three sub-issues of #27 are done.
merge: #30 trending tags rail (PR #129)