zulip/zulip-flutter

Use last_moved_timestamp instead of scanning edit_history

Open

#1,397 opened on Mar 11, 2025

View on GitHub
 (6 comments) (0 reactions) (0 assignees)Dart (456 forks)github user discovery
a-apihelp wantedserver-10

Repository metrics

Stars
 (454 stars)
PR merge metrics
 (PR metrics pending)

Description

The server will be introducing (probably in Zulip Server 10) a field last_moved_timestamp on message objects, as well as narrowing the meaning of last_edit_timestamp. Together these are intended to let the client skip scanning through edit_history to determine whether a message has been edited or moved.

We should start interpreting the new fields when present, instead of doing that scanning. This will be more efficient, and also a step toward the server being able to stop sending the full edit history in the future.

Implementation

On old servers, we'll continue scanning edit_history. Let's have that logic express its conclusion in the form of the same last_moved_timestamp and last_edit_timestamp information that new servers send.

Then the rest of the app can effectively use the new API, looking at those two fields, without caring about the existence of the old API.

References

Contributor guide

Research direction
Find the function that loops through edit history to determine if a message was edited or moved. Add logic to check last moved timestamp and last edit timestamp first; if present, use them directly. Otherwise, keep the scanning logic. Ensure the rest of the app reads these two fields instead of scanning.
Tech stack
dartflutter
Domain
mobile
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
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
DartFlutter
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70