Skip to content

[Inline parity 2/6] Preserve channel identity, read state and workspaces - #2

Closed
salmonumbrella wants to merge 4 commits into
inline-chat:mainfrom
salmonumbrella:feat/inline-parity-foundation
Closed

salmonumbrella wants to merge 4 commits into
inline-chat:mainfrom
salmonumbrella:feat/inline-parity-foundation

Conversation

@salmonumbrella

@salmonumbrella salmonumbrella commented Nov 8, 2026 •

Copy link
Copy Markdown

What changed

  • Distinguish source-backed DMs, channels and separate reply children without changing portal/message identities.
  • Group accessible workspaces and repair navigation through durable, login-scoped journals. Temporary access-refresh failures retain the previous snapshot; unknown observations hold pending navigation changes.
  • Project only proven source-read prefixes, retaining pending work through delivery failures and restart.
  • Add protocol 5 ingress checks and preview/apply/rollback presentation migration. Automatic notification writes remain disabled when their origin cannot be proven.

Why

Channels previously appeared as group DMs, and cached metadata or read timestamps could change presentation or mark content read without enough evidence. This foundation keeps source facts, delivery and later user choices separate.

Usage

Matrix kicks and invite revocations are unsupported because direct participant removal may leave other source access.

Use inline-settings for degraded states and inline-channel-default muted|normal|default to record desired defaults. Automatic muting is unavailable on this transport; mute channels manually. Presentation migration is preview-first with explicitly selected portals; see docs/operations.md. Receipt reconciliation retains a conservative 20-page/10,000-event, five-second inspection limit; long timelines may delay the room lane or leave read projection pending.

Requires the client commit from Inline PR159, pinned in both workflows. Protocol 5 requires upgrading the Go bridge and adapter together. These drafts do not deploy or migrate a live bridge.

Stacks on inline-chat/inline#159

Refs #1.

@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