Recap

Recap is an add-on on one feed or phrase entry: a ranked, scheduled summary of that entry's own announces, sent into the group at fixed times of day, Eastern time only.

What recap is

Warning

Recap is refused on follow trackers: the dashboard rejects "Recap isn't available for follow trackers", and the bot itself never runs a recap phase for a follow-type entry either.

Every successful announce from that entry appends one record to the entry's hit list: the post's id, its author's handle, follower count, likes, replies, views, bookmarks, and its URL. The list keeps the most recent 100 hits.

Hits survive a pause and a bot restart. Changing the entry's own source — the handle for a feed, or the phrase and its follower/verified gates for a phrase — drops the accumulated hits.

Schedule and fields

Times are always read in America/New_York, regardless of the group's own locale or the bot host's clock.

Recap fields

The dashboard's Recap add-on switch reads "Recap on" / "Recap off". A frequency dropdown — "Once a day", "Twice a day", "3× a day" — sets how many time fields show.

Prep, send, and missed slots

5 minutes (300 s) before each scheduled slot, a one-shot task re-fetches every queued hit once — the post itself plus its author's current follower count, nothing else.

If that re-fetch is rate-limited, the bot waits 30 seconds and retries the same post once; if it still fails, the announce-time counts are kept as they were.

At the slot, the bot sends the ranked list. The send window is 15 minutes (900 s) after the slot — a slot the bot cannot reach inside that window is skipped outright. A missed recap is never sent late, and it is not owed on the next slot.

A slot with nothing queued sends nothing.

Recap sends to the entry's alerts topic when one is set (see 2.8), otherwise the group's General.

The row and header — the only runtime placeholders

Note

A feed or phrase entry's own message preset has no such system — see 2.9.

Row tokens

The header supports exactly one token: {count}, the number of ranked hits in that recap.

The built-in row template, rendered

@kindachic renders and links to its profile; "post" renders and links to the post itself.

Messages split at 4000 characters per part. A part never splits a row in half — if the next row would cross the limit, that row starts the next part instead; a single row longer than 4000 characters on its own is cut at the limit. The header appears once, at the top of the first part only — later parts carry rows only.