Improve chat backup and device migration

Open
#4 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Domain
backend, security

Research direction

The issue provides no files, tests, or entry points. Start by mapping the existing chat backup, device migration, encryption, and server-upload paths; done means encrypted backup files can be uploaded and restored during migration, with the relevant behavior verified.

Written by the indexing model from the issue text.

Description

Support chat backup file encryption and upload to our server.

Dominant language
No language data
Stars
2
Forks
0
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MixinNetwork/mips

All issues in MixinNetwork/mips

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.