#464 Explore filters your own and starred timelines, in place of their own lists

[Anonymous]

Originally created by: athanclark

The dashboard's Your timelines and Your favorites sections are gone. Explore's filters now cover what they did.

Explore's filters, signed in:

• Search in: The whole library or My timelines, as before.
• Only timelines I starred (new): a switch, starred=1 in the address.
• Visibility (new): public, private or both, visibility=…. It replaces what only the old Your timelines list could do.

Both new filters apply to timelines and to their events. A guest's are ignored.

Server:

• POST /api/timelines/search takes starred: true in any scope; mine with starred gives your own starred timelines. The starred scope still works and is visible with starred on.
• POST /api/timelines/entities/search takes starred and visibility.
• Both need sign-in for starred (401 signed out). The OpenAPI schemas are updated.
• Browsing with Only starred or a visibility searches every timeline you may read (visible), not the public library's browse list, which shows only established accounts' timelines. That way newcomers' and private timelines you starred are listed.

Page:

• ＋ New timeline and Your public profile move beside the Timelines heading.
• Your timelines in the account menu and on the landing page opens Explore with My timelines chosen (?within=mine#explore). The account menu now shows it with the landing page off too.
• The mine… and favorite… query parameters are gone. Profiles keep their own Public favorites (favorite…).

Tests:

• Unit: timeline-lists.test.mjs covers the filters' state, addresses and searches.
• PostgreSQL:
• stars-postgres covers starred in the mine, visible and public scopes and the 401;
• library-search-postgres covers starred and visibility on events;
• next-postgres replaces its old dashboard list checks with Explore's filters, without JavaScript.
• Browser: library-search-live-postgres flips the starred switch. timeline-browser-live-postgres uses Explore's Visibility in place of the old list's.
• Run locally: unit tests, stars-postgres, library-search-postgres and next-postgres pass. contents.test.mjs fails here on main too, because git's file listing overflows its buffer in this checkout.
• Not run locally: the browser tests, because Chromium wouldn't download on this machine, so CI's run is the first.

🤖 Generated with Claude Code

https://claude.ai/code/session_011fFY8eruEi1xAkkMBni13B

[Anonymous]

Ticket changed by: athanclark

• status: open --> closed