element-hq / element-hq/element-meta
Device dehydration: state explicitly on UI that recovery enables/disables dehydration
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 112
- Forks
- 26
- Avg merge
- 6h 6m
- Merged PRs (30d)
- 4
Description
Dehydration is currently only enabled (e.g. dehydrated device is created) when user has set up recovery (since there is a dependency that dehydration key gets stored in the server). Also, dehydration without recovery key is not useful as you can't rehydrate without it.
Therefore we should make clear both on our UI (where you set up or disable recovery) as FAQ that recovery is (also) needed to get offline messages. Whoever needs/wants that then knows that and whoever is more paranoid about security, can keep it off.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or entry point is named. Start by locating the UI for setting up or disabling recovery and the relevant FAQ, then confirm how dehydration and offline messages depend on recovery. Done means both places clearly state that recovery is needed to receive offline messages.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100