Under the hood
Useful1 Signal1
Resume, rewind, restore and summarize moved onto a session controller with identical behaviour.
What's wrong with this entry?
Anonymous. No account, no email.
What
These operations are now methods on the session controller object rather than closures created inside the main screen's render, and conversation identity after a rewind or summarize is advanced by an explicit call instead of an inline reset. Ordering aside, behaviour is unchanged and the rewind telemetry payload is identical.
Evidence
restoreMessageSync
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.224
Loop file can come from stored state instead of disk
Both mention loop
-
v2.1.248
Loop keepalive is on by default
Both mention loop
-
v2.1.248
Self-pacing /loop wakeups no longer blocked by a runtime switch
Both mention loop