Emojery vs Synkie

A conversation is not a measurement

20 people chatting over a video tells you those 20 were there and in what mood. It does not tell you how the video landed, because the loudest participants write most of the messages and nobody counts the silent ones. A reaction is the opposite trade: it says almost nothing individually, and it aggregates into something you can read at a glance.

Neither replaces the other. They answer different questions about the same page, which is why running both is a reasonable thing to do.

What each one has to store to do its job

This is a design consequence rather than an accusation. A chat product has to hold messages, and Synkie's messages can carry images, files and voice notes, plus comments kept for visitors who arrive later. A reaction product does not: Emojery never receives text, so there is no message store, no attachment store, and nothing to hand over if somebody asks.

What Emojery does send is listed on privacy, and it is short for the same reason. Both extensions declare on their store cards that they do not sell user data to third parties.

One is counted, the other is witnessed

Emojery's whole architecture exists to make a number checkable: admission rules written down, every accepted reaction appended to a public log, totals re-derivable by a program we do not control the output of. None of that applies to a chat layer, and nobody should want it to: messages are content, and content does not need a Merkle tree.

Scope is the honest trade

Synkie works on any page. Emojery works on 14 sites, because a reaction has to attach to a stable, public identity for an item, and deriving that identity is per-site work. That is a real limitation, and the roadmap is the list of sites it has not reached yet. The upside is that a reaction on a repository means the same thing as a reaction on a product page.