Cookiemonsters

Imported from the pre-Redmine CookieMonsters TODO during the 2026-08-29 migration.

Original priority: P1 — Community experience and polish

• Standardize one shared reaction system across the whole CookieMonsters community instead of implementing a different Like button on every feature:
  • initial reaction set must be exactly the same wherever reactions are offered: Like 👍, Love ❤️, Agree ✅, Hugs 🤗, Happy 😊, Sad 😢;
  • use this same reaction picker and backend model for Profile Wall/News Feed posts, forum posts and replies, Gallery photos, Screenshots, Show Room entries and future normal community content; comments/replies can use the same set too when reactions are enabled on them;
  • keep the reaction names translation-ready in the site language files while preserving the same semantic choices across languages;
  • one member has at most one active reaction per content item at a time; selecting another reaction changes their reaction, and selecting/removing the active reaction should let them clear it cleanly;
  • show compact counts per reaction and allow viewers to inspect who reacted when the underlying content/privacy rules permit it;
  • reaction identity and counts must obey the content's effective access, blocks, NSFW/SFW state and any surface-specific privacy rules; in particular, Gallery's existing Hide my identity from other viewers option must continue to work for any of these reaction types, while the photo owner still sees the real actor as already specified;
  • do not leak a hidden/private reactor through APIs, notifications, hover text, feed activity or copied URLs when that surface says their identity is hidden;
  • create one reusable UI/backend reaction component/data model so adding Love/Agree/Hugs/Happy/Sad does not result in slightly different implementations across Forum, Wall, Gallery and Screenshots;
  • notifications should use the actual reaction when useful, e.g. Someone sent Hugs to your post or Someone loved your post, but must still obey actor-identity privacy and content access at read time.

CM-TODO-ID:5b1368dd3bdca454c857

Future notes, acceptance criteria and status changes belong in this Redmine issue.