Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tracking: Message History #619

Closed
20 tasks done
tuddman opened this issue Apr 5, 2024 · 2 comments
Closed
20 tasks done

Tracking: Message History #619

tuddman opened this issue Apr 5, 2024 · 2 comments
Labels

Comments

@tuddman
Copy link
Contributor

tuddman commented Apr 5, 2024

  • Implement & Test a round trip for Message backup Request -> Response.
  • Implement & Test that the request has the correct fields.
  • Implement & Test that the response has the correct fields.
  • Implement & Test that a Sync group is properly created.
  • Implement & Test the polling of whether a request has been broadcast out.
  • Implement & Test that the request & response message(s) are of a custom content type.
  • Implement & Test the request storage lifecycle - including verifying origination of the request.
  • Implement & Test the generated PIN storage + sending + verification
  • Implement & Test encryption of the message-bundle.
  • Implement & Test serialization of the message-bundle.
  • Implement & Test uploading of the message-bundle
  • Implement & Test downloading of the message-bundle
  • Implement & Test decryption of the message-bundle.
  • Implement & Test deserialization of the message-bundle
  • Implement & Test insertion/storage of the message-bundle
  • Make a diagram explaining the flow
  • Implement & Test message-bundle responder adding message-bundle requester to all groups
  • Implement & Test the validation rules that prevent non-allowed parties from joining a Sync group.
  • FFI bindings: client::new().with_sync_options(url), allow_sync, send_history_request
  • Stand up a default message history server with adequate storage backing.
@tuddman tuddman converted this from a draft issue Apr 5, 2024
@tuddman tuddman changed the title Message History (backups) Tracking: Message History (backups) Apr 5, 2024
@tuddman tuddman self-assigned this Apr 5, 2024
@tuddman tuddman moved this from Todo to In Progress in MLS Work Apr 5, 2024
@tuddman tuddman changed the title Tracking: Message History (backups) Tracking: Message History Apr 9, 2024
@nplasterer
Copy link
Contributor

Just wanted to add a little context from our chat last week about what will be required on the SDK/binding side.

  • LIBXMTP Bindings
    • A function to initiate a request to upload messages
      • This uses a new topic to send a message with a pin for user validation
    • A function to trigger a upload of messages
  • SDK
    • A new topic for message history (only for handling in push notification)
    • Subscribe functionality for these new topics (subscribeToBackupRequest)
      • This listens for the new topic messages and if validated triggers an upload of messages
    • Send new topic for this event (sendBackupRequest)
      • Triggered on new installation logins

@tuddman
Copy link
Contributor Author

tuddman commented May 22, 2024

For anyone finding this tracking ticket: there is also this companion repo to handle the temporary storage and relaying of the message bundles.

@nplasterer nplasterer moved this to Todo in V3 Backlog Jun 20, 2024
@nplasterer nplasterer moved this from Todo to In Progress in V3 Backlog Jun 20, 2024
@tuddman tuddman removed their assignment Aug 2, 2024
@nplasterer nplasterer self-assigned this Aug 6, 2024
@github-project-automation github-project-automation bot moved this from In Progress to Done in MLS Work Aug 8, 2024
@github-project-automation github-project-automation bot moved this from In Progress to Done in V3 Backlog Aug 8, 2024
@nplasterer nplasterer removed their assignment Aug 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Done
Status: Done
Development

No branches or pull requests

4 participants
@tuddman @nplasterer @bwcDvorak and others