Skip to content

[Inline parity 3/6] Preserve rich entities and caption revisions - #3

Closed
salmonumbrella wants to merge 7 commits into
inline-chat:mainfrom
salmonumbrella:feat/inline-parity-rich
Closed

salmonumbrella wants to merge 7 commits into
inline-chat:mainfrom
salmonumbrella:feat/inline-parity-rich

Conversation

@salmonumbrella

@salmonumbrella salmonumbrella commented Nov 8, 2026 •

Copy link
Copy Markdown

What changed

  • Preserve supported formatting and checked UTF-16 entities in send, edit, upload, live and backfill paths.
  • Resolve typed user mentions within the current login; unsupported identities stay readable.
  • Persist revision and media identity so stale edits are ignored and caption edits retain existing Matrix media. Unchanged legacy plain replays use exact historical hashes; real text/entity changes and unhandled media still retry.
  • Reject file replacements, unproven legacy caption edits and foreign portal/receiver edit targets before source mutation.

Why

Text-only conversion lost formatting and mention identity. Replayed revisions could overwrite accepted content, while caption edits could transfer the same media again.

Usage

No configuration change. New supported formatting and caption edits use the existing message paths. Caption edits require the original media URI, filename, metadata and encryption envelope; clients that normalize attachment metadata can receive an explicit unsupported result. Broadcast mentions and file replacement through edits remain unsupported.

Stacks on #2

Refs #1.

@salmonumbrella
salmonumbrella force-pushed the feat/inline-parity-rich branch from a932561 to da5ff52 Compare November 8, 2026 12:08
@morajabi morajabi closed this Nov 14, 2026
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.

2 participants