Skip to content

Commit

Permalink
Update XIPs/xip-31-message-history.md
Browse files Browse the repository at this point in the history
Co-authored-by: J-Ha <[email protected]>
  • Loading branch information
rygine and jhaaaa authored Sep 9, 2024
1 parent b699aef commit c7de18f
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion XIPs/xip-31-message-history.md
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ It's also worth noting that there are many use cases for XMTP where message hist
1. Message history synchronization should be opt-in for developers.
1. It should be simple for developers to implement message history synchronization correctly. Implementation work should be focused on app-specific UX choices, with the SDK responsible for core transport and security decisions.
1. Compatibility between apps is expected. Apps should be able to share history irrespective of operating system, SDK version, or device type (web vs. mobile vs. server).
1. Even if developers of some popular apps choose to not support message history synchronization, it should be simple for users to opt enable themselves.
1. Even if developers of some popular apps choose to not support message history synchronization, it should be simple for users to opt-in to enable it for themselves.

## Specification

Expand Down

0 comments on commit c7de18f

Please sign in to comment.