jim 1c7b6a1e86 fix: start replies fetch from newest, ignore stale DB timestamp
The DB-derived MAX(N.timestamp)+1 for a post is unreliable - many notes
were stored with the same timestamp (likely crawl time, not the actual
note timestamp), so passing it as before_timestamp excluded all real
replies and returned an empty notes array. Diagnostics showed two
unrelated posts coming back with identical totals (1625/1021/603) and
zero notes.

Now we start with no before_timestamp (newest page) and let pagination
walk backward via each page's last-note timestamp.
2026-05-07 14:00:48 -05:00
2025-11-24 11:58:55 -06:00
.
2026-03-26 00:35:24 -05:00
2026-05-06 16:51:56 -05:00
.
2026-03-26 00:35:24 -05:00
.
2026-03-26 00:35:24 -05:00
.
2026-03-26 00:35:24 -05:00
.
2026-03-26 00:35:24 -05:00
.
2026-03-26 00:35:24 -05:00
2024-10-30 09:14:53 -05:00
2026-05-06 14:50:30 -05:00
S
Description
No description provided
136 MiB
Languages
C# 98.1%
PLpgSQL 1.9%