Skip to content

WIP: Support for profile updates over Sliding Sync (MSC4262) - #20003

Draft
jaywink wants to merge 14 commits into
anoa/msc4429from
jaywink/msc4262
Draft

WIP: Support for profile updates over Sliding Sync (MSC4262)#20003
jaywink wants to merge 14 commits into
anoa/msc4429from
jaywink/msc4262

Conversation

@jaywink

@jaywink jaywink commented Jul 25, 2026

Copy link
Copy Markdown
Member

This PR implements support for profile updates over Sliding Sync: matrix-org/matrix-spec-proposals#4262.

This PR depends heavily on anoa/msc4429 and is currently in WIP status due to various missing features.

Pull Request Checklist

  • Pull request is based on the develop branch
  • Pull request includes a changelog file. The entry should:
    • Be a short description of your change which makes sense to users. "Fixed a bug that prevented receiving messages from other servers." instead of "Moved X method from EventStore to EventWorkerStore.".
    • Use markdown where necessary, mostly for code blocks.
    • End with either a period (.) or an exclamation mark (!).
    • Start with a capital letter.
    • Feel free to credit yourself, by adding a sentence "Contributed by @github_username." or "Contributed by [Your Name]." to the end of the entry.
  • Code style is correct (run the linters)

jaywink added 14 commits July 15, 2026 14:53
Using the same `include_profile_updates_in_sync` config option as the legacy sync
If initial, return all fields. If incremental, return updates.
Also make `test_tracking_of_sent_fields_per_sliding_sync_connection` failing now.
If the user updates a field, then deletes it, and the sync runs, we'll need to ignore those fields as the profile doesn't have them anymore.

We would send down the delete, but that isn't implemented yet.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant