WaveNote is a full social overlay for the web. Web Reactions is intentionally not that: it is a small reaction layer with a stronger count story.
WaveNote's Chrome Web Store card describes a shared social layer on any webpage: page-specific comments, replies, likes, dislikes, trust, distrust, flags, pins, notifications, direct messages, files, voice messages, and cloud sync.
That breadth makes WaveNote a social product. Web Reactions is narrower by design. It does not try to be a messenger or a comment network; it adds verified emoji reaction counts where a quick public signal is more useful than a full conversation.
| Web Reactions | WaveNote | |
|---|---|---|
| Primary job | Emoji reaction counts on supported content | Social comments, messaging, and engagement on any webpage |
| Participation model | Pick one reaction for a target | Comment, reply, react, follow, message, attach media |
| Signal vocabulary | Full emoji palette | Likes, dislikes, trust, distrust, flags, pins, and reactions |
| Sites covered | Supported-site adapters placed in the page context | Any webpage, per the Chrome Web Store description |
| Data disclosed by store card | No web history or personal communications collection | Personally identifiable information, authentication information, personal communications, user activity, and website content |
| Source code | Public on GitHub, GPL-3 | No public repository linked from the store card |
| Last public update | Continuous project updates | May 18, 2026 on the Chrome Web Store card |
WaveNote brings the whole social stack into the browser: conversations, notifications, following, direct messages, and attachments. That can be powerful, but it also changes browsing into another inbox.
Web Reactions is meant to stay out of the way. You see a count, leave a reaction if you want, and keep browsing. There is no thread to moderate and no message stream competing for attention.
WaveNote's own store disclosure includes personal communications and user activity. That is expected for a tool with messages, notifications, and cloud sync, but it is a much broader data category than a reaction counter needs.
Web Reactions does have server-side state because aggregate counts require it, but the product does not need to store messages, attachments, follows, or private conversations.
In WaveNote, reactions are one feature inside a larger social layer. In Web Reactions, the reaction count is the core contract. That is why the project puts so much weight on account verification, local history, and public verification of aggregate counts.
Any extension that can attach UI to pages asks for trust. Web Reactions makes the extension code public, so users and reviewers can inspect what runs in the page context. WaveNote's public store listing does not link a public source repository.
Pick WaveNote if you want a full social sidebar with comments, notifications, direct messages, and media.
Pick Web Reactions if you want a quieter reaction layer whose main job is trustworthy aggregate emoji counts.
Leaning toward switching? The WaveNote alternative guide covers the move itself.
