zulip/zulip-flutter

Support individual_emoji_changes client capability

Closed

#2,278 opened on Apr 15, 2026

View on GitHub
 (0 comments) (0 reactions) (1 assignee)Dart (456 forks)github user discovery
a-apihelp wantedserver-12

Repository metrics

Stars
 (454 stars)
PR merge metrics
 (Avg merge 25d 15h) (22 merged PRs in 30d)

Description

The server is adding a new client capability individual_emoji_changes. We should add support for the new API that it controls, and start sending the capability.

This will involve supporting two new event types RealmEmojiAddEvent and RealmEmojiUpdateOneEvent.

This is useful because the old API is subject to accidental DDoS when a realm adds a large number of custom emoji. Moreover, once we have a mobile release out that supports the new API, the clock starts on being able to later remove the old API from the server.

References

Contributor guide

Research direction
Study the server PR #38787 to understand the new event types RealmEmojiAddEvent and RealmEmojiUpdateOneEvent. Then implement support in the Flutter client by subscribing to these events and updating the client capability flag. Start by adding the new event models and handler.
Tech stack
dartflutter
Domain
mobile
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
FlutterDart
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60