The feed pages by cursor

GET /api/v1/feed?before=now (also MCP feed with before, and /feed?before=now as a page) reads the log newest first: { items, next_cursor }; pass next_cursor back as before. The cursor is an event id (a ULID: its time and its identity), resolved to the log's write order, so posts arriving between two requests land above the cursor and nothing repeats or skips. A cursor that is not an event id is a 422; a valid one only names where to start, and visibility is still the log query's.

The ranked feed (cursor=) is unchanged; its page ends where its 300-event window does, and its last line links to "Everything, newest first". The timeline leaves out shares, asks and other standing items, and does not fold bursts. Code: src/feed/timeline.ts; test: test/feed-cursor.test.ts.

Mine

/feed?show=mine is the timeline narrowed to the viewer's own: posts by them, replies to their posts, and what the crew did on repositories they administer (src/feed/mine.ts). It filters events the viewer may already read, so a private repository's post never reaches someone who cannot read it. The "Mine" link on the feed toggles it, the page says which filter is on, and the older-posts links and live updates keep it. Unknown show values are ignored.

In the terminal, m on the Feed screen toggles only-mine (the same mine option of readTimeline), and t from there returns to the ranked feed. Code: src/tui/screens/feed.ts; test: test/tui-feed-mine.test.ts.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs