Like and burn interactions are not persisted — state resets on reload

[3m1n3nc3]

Description

In PostCard (components/post-card.tsx), the isBurned state is a local useState(false) variable. When a user burns a post, the counter increments in memory via the context burnPost action, but no request is sent to POST /api/posts/[id]/burn. On page reload, the burn count reverts, and the user can burn the same post again.

The same pattern applies to likes — there is no mechanism to track whether the current user has already liked or burned a post, so the UI cannot reflect the current state on load.

More info

• Working API: POST /api/posts/[id]/burn, DELETE /api/posts/[id]/burn, POST /api/posts/[id]/like, DELETE /api/posts/[id]/like.
• GET /api/posts/[id]/stats returns { likes, burns, entries } counts.
• The fix involves:
  1. Calling the appropriate API when a user clicks like/burn.
  2. Using the returned count from the API response to update UI.
  3. Fetching the user's own interactions on mount (or embedding them in the post response) so buttons show the correct active state.
• The burnPost context action can remain for optimistic UI but must be backed by an API call.

[LaahAbba]

@LaahAbba has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

I'm a full stack develop I'll like to work on this issue because It picks my interest and Ive got experience with similar projects I'll have it solved in 24 hours or less

ℹ️ Repo Maintainers: To accept this application, review their application or assign @LaahAbba to this issue.

[drips-wave]

Congratulations, @LaahAbba! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on March 30, 2026.

🧑‍💻 @LaahAbba: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊