Skip to content

fix: prevent scheduled posts from polluting feed and since filter#350

Merged
barrydeen merged 1 commit into
mainfrom
fix/scheduled-post-feed-pollution
Mar 28, 2026
Merged

fix: prevent scheduled posts from polluting feed and since filter#350
barrydeen merged 1 commit into
mainfrom
fix/scheduled-post-feed-pollution

Conversation

@barrydeen
Copy link
Copy Markdown
Owner

Summary

  • Future-dated notes fetched from the scheduler relay were being persisted to ObjectBox via cacheEvent(), then seeded into the feed on next boot by rebuildFeedFromCache() — causing scheduled posts to appear in the main feed
  • Their future created_at also poisoned latest_follows_feed_ts, pushing the since filter into the future so no new notes were ever fetched on subsequent boots
  • Skip persisting future-dated events in cacheEvent(), filter them out in rebuildFeedFromCache(), and cap the saved since timestamp at current time as a safety net

Test plan

  • Schedule a post for the future via the scheduler relay
  • View scheduled posts on the Drafts screen
  • Restart the app and verify the scheduled post does not appear in the main feed
  • Verify new notes load normally after restart (since filter is not stuck in the future)

Future-dated notes fetched from the scheduler relay were persisted to
ObjectBox via cacheEvent(), then seeded into the feed on next boot by
rebuildFeedFromCache(). Their future created_at also poisoned the
latest_follows_feed_ts preference, causing the since filter to sit in
the future so no new notes were ever fetched.

- Skip persisting future-dated events in cacheEvent()
- Filter out future-dated events in rebuildFeedFromCache()
- Cap saved latest_follows_feed_ts at current time as safety net
@barrydeen barrydeen merged commit 7f73196 into main Mar 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant