UnifierHQ Blog
  • Main Page
  • 🔧Technical
    • We're moving to Nextcord
    • Introducing Unifier Installer
    • Discontinuing Reaction Images
    • We're removing the identifier
    • We made Unifier 20x faster
    • Unifier evolved to (experimentally) support Guilded!
    • Unifier, meet Revolt!
    • Test the new Revolt Support extension
    • The story of Unifier/UniChat
  • 📦Releases
    • Unifier 3.9.0 (and 3.8.0) is here!
    • Now entering: Unifier v3
    • Unifier is open source now.
    • Unifier Micro: a light and open source global chat bot
    • Open sourcing our first version
  • ⛑️Safety
    • Followup: May 7 raid threats
    • The May 7 HYP raid threats
    • Our first security vulnerability
    • March 26: The first raid on UniChat, which we prevented
  • 💬Opinion
    • Our stance on Discord adding advertisements
Powered by GitBook
On this page
  • Why we removed it
  • Low usage
  • Too gimmicky
  • Bridge v2 incompatibility
  1. 🔧Technical

Discontinuing Reaction Images

We're saying goodbye to Reaction Images.

Reaction Images was a feature we released last month with v0.4.0. It allowed users to easily generate reaction memes on messages, such as the clueless meme and Omniman think meme.

Today, we've taken the unfortunate decision to discontinue this feature.

Why we removed it

There are many reasons why we've decided to remove Reaction Images from Unifier.

Low usage

To begin, Reaction Images were barely being used, not even by the developers and moderators. When it was first released, we used it for a week or two, then we didn't use them at all, like they never existed. We barely saw that green message content button appear on UniChat channels on Discord, only blurple (Discord), red (Revolt), and gray (Guilded).

Too gimmicky

We made Reaction Images as a way to further improve the chatting experience, but as we used it more, we realized that this was more of a gimmick, rather than a useful feature that positively contributes to the experience. This was not in like with what we wanted to do for Unifier: we wanted to create features, not gimmicks, unlike my last bot which is just too full of gimmicks that pretty much nobody uses those features.

Bridge v2 incompatibility

When Bridge v2 came around, sending messages became centralized to one send function under a UnifierBridge object. And to send a message through the Bridge, a discord.Message, revolt.Message, or guilded.Message object would be required. This was done to reduce the number of parameters, as well as enable the Bridge to automatically identify the source of the message.

We made Reaction Images when Unifier still used Bridge v1, which didn't use a discord.Message object to send a message. To make Reaction Images use Bridge v2, we would need to modify the Bridge by quite a bit, and we didn't want to do that for a mere gimmick that pretty much nobody uses.


To those that enjoyed Reaction Images, we are deeply sorry for any inconveniences caused by the removal of this feature.

PreviousIntroducing Unifier InstallerNextWe're removing the identifier
Page cover image