The wpDiscuz Emoticons add-on adds an emoji picker to the wpDiscuz commenting experience. Each insertion lives in the standard comment_content column in wp_comments, alongside the per-comment vote tallies the parent wpDiscuz plugin stores in commentmeta. The default thread view renders this inline as decoration, which is fine for the reader and unhelpful for moderation or editorial review.

SleekView reads the same wp_comments rows, joins the wpdiscuz_* vote meta and derives an emoticon_count column plus a dominant_emoticon bucket from comment_content. The result is a per-row grid where status, post, upvotes, emoticon count, sentiment bucket and author live as typed columns. Filter to comments with three-plus emoticons on a controversial post, sort by upvotes to find badge candidates, or scope to negative-sentiment rows to triage backlash before it spreads.

Because the table reads what the add-on already writes (and derives the rest at query time), no second tracking layer is introduced. Moderation flows continue to go through wpDiscuz's UI; the table is a row-level audit surface for the data the thread view treats as decoration.

wpDiscuz Emoticons enriches comments with reaction signal that the default thread view treats as decoration. The data is real: each insertion sits in comment_content, the parent plugin's vote tallies sit in commentmeta and timestamps come straight from wp_comments. SleekView reads the same rows and adds a derived sentiment column at query time.

Moderators stop scrolling for frowns and start filtering for them; editorial surfaces the comments worth quoting; community managers find badge candidates without exporting to a spreadsheet. Same comment rows, same emoticon usage, completely different posture toward sentiment. The grid renders what the add-on already writes (and what the thread view leaves implicit) as queryable columns, which is the difference between watching emoji scroll past and using them as moderation signal.