Idea: one JSON export/import of the user's Lotus-side data so they can leave with it or restore after a wipe. Room history export already exists (Export Room History, txt/json/html) and is a different thing (messages, per room); this is account-level personal data.
Questions for Jared
Scope: settings (synced + device-local?), bookmarks, private user notes, custom room sections, thread-notification overrides, soundboard clips (binary — include as files or as mxc references?), avatar decoration, custom status. Which of these?
Where in the UI: Settings → Account (next to key export/import), or Settings → General → Sync (next to the new sync controls), or a new "Your data" section?
Import semantics: merge or replace? Warn before overwrite?
Encryption keys: keep the existing separate key export (passphrase-protected) or bundle it (dangerous — the JSON would then be secret)? Recommendation: keep separate.
Should a stale import be rejected by a version stamp, or migrated?
Idea: one JSON export/import of the user's Lotus-side data so they can leave with it or restore after a wipe. Room **history** export already exists (`Export Room History`, txt/json/html) and is a different thing (messages, per room); this is account-level personal data.
### Questions for Jared
1. **Scope:** settings (synced + device-local?), bookmarks, private user notes, custom room sections, thread-notification overrides, soundboard clips (binary — include as files or as mxc references?), avatar decoration, custom status. Which of these?
2. **Where in the UI:** Settings → Account (next to key export/import), or Settings → General → Sync (next to the new sync controls), or a new "Your data" section?
3. **Import semantics:** merge or replace? Warn before overwrite?
4. **Encryption keys:** keep the existing separate key export (passphrase-protected) or bundle it (dangerous — the JSON would then be secret)? Recommendation: keep separate.
5. Should a stale import be rejected by a version stamp, or migrated?
jared
added this to the Features 2026-Q4 milestone 2026-09-17 13:27:07 -04:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Idea: one JSON export/import of the user's Lotus-side data so they can leave with it or restore after a wipe. Room history export already exists (
Export Room History, txt/json/html) and is a different thing (messages, per room); this is account-level personal data.Questions for Jared