Skip to content

Track Inline bridge parity #1

Closed

Description

@salmonumbrella

The situation

Inline channels can appear as group DMs in Matrix. Workspace navigation, read state, formatting and child-chat context also need enough source data to survive refresh and restart without changing existing room or message IDs.

What works today, and why it is not enough

The bridge delivers messages and supports basic management. Flat dialog data cannot prove a channel's structure or current workspace access, and text-only request paths lose formatting. Reply children can have different access from their parents, so putting them in the same Matrix room can expose content.

Ask

Review the six draft contributions in order:

  1. Client structure, access and entities
  2. Channel identity, read state and workspaces
  3. Rich entities and caption revisions
  4. Accessible people and channel creation
  5. Separate reply-child context
  6. Bounded media transfers and fidelity

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions