Cookiemonsters

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

Original priority: P1 — Community experience and polish

• Build a first-class member Profile Wall (Facebook-wall-style concept, but CookieMonsters' own visual/interaction design):
  • every member profile should have a personal Wall where the member can publish their own normal social posts and visitors can see the posts they currently have permission to view;
  • the initial Wall model is owner-posts-to-own-wall: the profile owner creates posts on their Wall, while other members interact through comments/reactions; posting directly onto somebody else's Wall can be considered later rather than creating a moderation/privacy problem in the first version;
  • Wall posts can contain text, one or more photos/images, and links; links should render a safe compact preview when possible without letting arbitrary embeds/scripts escape CookieMonsters;
  • allow combining text + images + link in the same post when useful instead of forcing separate post types;
  • use a friendly composer such as What's on your mind? rather than a form-like editor;
  • enable the same Emoji and GIF creation tools for Wall/News Feed posting that members expect from chat: the Emoji button must open a real emoji picker and insert the selected emoji at the current composer cursor/selection rather than being decorative, and the GIF button must open a real searchable GIF picker instead of showing Coming later / GIF picker is next placeholder copy;
  • GIF selection should attach/insert the chosen GIF into the pending Wall post with an in-composer preview and a remove action before publishing; members should be able to combine normal text + emoji + GIF where useful;
  • reuse one shared emoji/GIF picker component/service with chat wherever practical so search behaviour, accessibility, mobile layout, provider/safety handling and future improvements do not diverge into separate implementations;
  • published GIFs are part of the Wall post and must follow exactly the same audience, block, SFW/NSFW, edit/delete, feed and notification visibility rules as the post itself; a private/hidden post must never leak its GIF URL/thumbnail through feed previews or APIs;
  • if external GIF-provider media is used, proxy/cache or otherwise integrate it in a privacy/security-conscious way and prevent arbitrary embed/script content; keep attribution/provider requirements compliant without sending unnecessary CookieMonsters member data to the GIF provider;
  • make the Emoji/GIF controls work consistently in both the profile Wall composer and the News Feed What's on your mind? composer because they create the same underlying post type;
  • Wall posts are real backend objects with author, timestamps, edit/delete state, audience, SFW/NSFW classification and attached protected media;
  • let the author edit their own Wall post and delete it everywhere it appears; deleting it removes it from the profile Wall, News Feed and direct links/activity surfaces rather than leaving stale copies;
  • add comments to Wall posts and use the shared CookieMonsters reaction system below for both Wall posts and, where appropriate, their comments;
  • Wall posts should use the same familiar visibility model as other member content: GLOBAL / SITE / FRIENDS / COMMUNITY / PEOPLE / LIST / ME ONLY, reusing owner-created lists such as My Best Friends instead of inventing a second privacy system;
  • if a Wall post references a COMMUNITY, PEOPLE or LIST audience, only those effective viewers may discover the post; unauthorized viewers must not see a placeholder, preview, reaction count or notification that reveals the hidden post exists;
  • new Wall posts are SFW by default;
  • if and only if the author is age-eligible and has explicitly enabled the account-level 18+ / NSFW preference, show a clear optional composer control such as Mark as NSFW / 18+ when creating or editing a Wall post;
  • the Mark as NSFW option must be off by default for every new post and must not be shown/actionable for members who are not currently NSFW-enabled;
  • the same NSFW-marking control must be available whether the underlying Wall post is created from the member's Profile Wall composer or from the News Feed What's on your mind? composer, because both create the same post type;
  • enforce NSFW-post creation/editing server-side too: a crafted request must not let an under-18, age-unverified or NSFW-opted-out account set the post's NSFW flag;
  • an NSFW Wall post must obey the existing age gate, account NSFW setting and quick-SFW switch across the post body, images, link preview, feed card, comments/reactions, notifications, search/direct links and any future resharing surface;
  • blocks are stronger than Wall permissions: a blocked member must not discover the blocker's Wall posts through profile view, News Feed, direct URL, reaction list, comments or notifications;
  • show the Wall naturally on the public member profile without turning the profile into an endless feed; use pagination/load-more and keep identity/profile information easy to reach above it.

CM-TODO-ID:8eb1d71476961aa1d484

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