A developer frustrated with Google Meet's emoji reaction UI built a browser extension that adds instant search and personalization. Instead of fighting through obfuscated DOM elements, they discovered reactions are sent via a dedicated WebRTC DataChannel named "reactions." By intercepting the channel creation and decoding its protobuf format, the tool sends reactions programmatically and even injects them for the sender's view.

The technical approach required injecting a hook script before Meet's code loaded, using `runAt: 'document_start'` and `web_accessible_resource` to avoid race conditions. The extension parses the message format, builds custom protobufs, and uses gzip compression to simulate incoming reactions. This bypasses the official API entirely, demonstrating how client-side reverse engineering can enhance closed platforms.

While the tool only works for Google Workspace accounts with Extended Reactions, it highlights a common developer pain point: poor discoverability in enterprise apps. The creator open-sourced the method, inviting feedback on features like typo-tolerant search across 1900+ emoji. It's a practical example of improving UX by understanding underlying protocols rather than surface-level automation.