Native buttons vs Web Reactions

Native buttons are useful, but every website defines them differently. One site gives you a Star, another hides dislikes, another counts only upvotes, and another makes every signal feed its own ranking system. Web Reactions adds one independent reaction layer across supported pages.

Native buttons do not mean one thing

Every platform chooses a different contract

A Like on Facebook, a Star on GitHub, an upvote on Reddit, a hidden dislike on YouTube, and a product rating on Amazon are not interchangeable. They look similar because they are small buttons near content, but each one has a different meaning, a different visibility model, and a different relationship to the platform's ranking, profile, notification, or recommendation systems.

That inconsistency is the problem Web Reactions is designed around. People already react to the web all day. The web just does not give them one clear, portable way to leave a lightweight public signal. Reddit is a sharp example: sometimes you want a reaction without pressing native upvote or downvote.

Native reactions vs Web Reactions

Question Native reactions Web Reactions
Palette A handful of approved icons chosen by the platform The full searchable emoji palette with labels in 28 languages
Coverage One platform at a time, with platform-specific meaning One consistent layer across supported site families
Counts Stored in private systems you usually cannot audit Backed by a public, append-only log anyone can recompute
Account Usually requires that platform's account Free to browse; one email verification when you want to react
Your history Owned and shaped by the platform Kept on your device, in the extension popup
Tracking and ads Often part of the platform's broader business model No ads, no social feed, no public profile of reactions
Source Usually closed Open source, GPL-3.0-or-later
Leaving Data usually stays with the platform Delete your Web Reactions account and reactions at any time

A generic reaction contract for the web

One target, one current reaction

Web Reactions treats a public item as a target: a repo, post, video, product, or other supported page object. A verified account can have one current reaction for that target. Changing your mind updates the reaction; removing it takes it out of the count.

Same interaction model across sites

The page layout still belongs to the site, but the reaction model stays familiar. Open the picker, choose an emoji, see aggregate counts, and use the same account model across supported websites. That is the "generic web contract" Web Reactions is aiming for: not a formal standard, but a clear user-facing rule that does not reset every time a platform changes its own buttons.

Verifiable counts, not another black box

The count is only useful if it means something. Web Reactions backs counts with a public, append-only log and an open-source verifier that can recompute totals. The public API plan is built around the same principle: expose aggregate reaction data without turning it into a user lookup service.

What Web Reactions does not replace

Native actions still have their place

A GitHub Star can still bookmark a repo. A Facebook Like can still be the native Facebook action. A YouTube Like can still train YouTube's own interface. Web Reactions is not trying to pretend those controls have no value. It adds a second, independent signal when the native button is too limited or too platform-specific for what you want to express.

Comments and reviews still matter

An emoji cannot explain a bug report, a product defect, a legal concern, or a thoughtful review. It is a quick signal, not a replacement for writing. The advantage is speed: a reaction can say something useful in one second without dragging every page into another comment system.

Use the site's buttons when they fit. Use Web Reactions when they do not.

Install the extension and keep the web's native controls available by default. When a Like, Star, or upvote is too narrow, choose the reaction you actually mean.