Summary
Deleting a photo from the home page does not remove server-rendered initial cards from the visible feed. The code currently accepts this limitation, which leaves stale UI until refresh and can skew offset-based pagination after deletions.
Why this matters
- Users see photos that were already deleted
- The feed becomes inconsistent until a manual reload
- Offset pagination can skip or duplicate records after items are removed
Evidence
components/home-page-client.tsx:97-105components/home-page-client.tsx:222-223components/home-page-client.tsx:113-118
Suggested fix
Move the full feed into client state after hydration, or keep a hidden-deleted-ID set that filters the rendered initial cards as soon as deletion succeeds. Revisit pagination so it is resilient to mutation, ideally with cursor-based paging instead of count offsets.
Acceptance criteria
- A deleted photo disappears immediately from the home feed without a refresh
- Infinite scroll does not skip or repeat items after deletions
- Deletion behavior is consistent for uploaded, initial, and paged-in cards
Summary
Deleting a photo from the home page does not remove server-rendered initial cards from the visible feed. The code currently accepts this limitation, which leaves stale UI until refresh and can skew offset-based pagination after deletions.
Why this matters
Evidence
components/home-page-client.tsx:97-105components/home-page-client.tsx:222-223components/home-page-client.tsx:113-118Suggested fix
Move the full feed into client state after hydration, or keep a hidden-deleted-ID set that filters the rendered initial cards as soon as deletion succeeds. Revisit pagination so it is resilient to mutation, ideally with cursor-based paging instead of count offsets.
Acceptance criteria