Degauss your screens, Discourse Rewind 2025 is here 💾

Moin · December 12, 2025, 7:58am

I think this was fixed a few hours ago

github.com/discourse/discourse

FEATURE: Store rewind dismiss state in database instead of localStorage

main ← store-rewind-dismiss-state-in-db

merged 05:16AM - 12 Dec 25 UTC

ZogStriP

+210 -40

Users were seeing repeated rewind notifications across different devices and bro…wsers because the dismiss state was stored in localStorage, which is per-browser and easily cleared. Move the dismiss state to a new `discourse_rewind_dismissed_at` column in the `user_options` table. This allows the dismiss to sync across all devices and persist through browser data clears. The timestamp is compared using "rewind year" logic - dismissing in January 2025 (for rewind 2024) won't block the notification for rewind 2025 in December 2025. - Add `discourse_rewind_dismissed_at` datetime column to user_options - Add POST /rewinds/dismiss endpoint - Add `discourse_rewind_dismissed` to user_option serializers - Extract `DiscourseRewind.rewind_year` helper for year calculation - Update frontend service to read from server state instead of localStorage

Topic		Replies	Views
Discourse Rewind Plugin official , included-in-core , rewind	24	427	December 16, 2025
Discourse Rewind 2024 Community rewind	17	751	April 18, 2025
Add a preference to opt out of Discourse Rewind Feature rewind	4	114	December 7, 2025
Rework with the discourse review UX rewind	8	83	December 15, 2025
Daily Summary Feedback Site feedback feedback	237	6525	November 27, 2025

Degauss your screens, Discourse Rewind 2025 is here 💾

Related topics