element-hq / element-hq/element-web
Tails OS working installation method request
- Dominant language
- TypeScript
- Stars
- 13.5k
- Forks
- 2.8k
- PR merge metrics
- PR metrics pending
Description
**Is your suggestion related to a problem? Please describe.**
What is the best Tails OS Best Installation Method?
I have tried varied ways of using Element on Tails OS, from just logging in to the TOR Browser & restoring with a key, to installing the app & using an env in the .desktop to use a specified HOME in the Persistent folder & routing through the TOR proxy and/or using a source that syncs with the persistence.conf. Each time, some encrypted messages sent by others when offline can't be decrypted when logging into a new session. Anything sent while both online is ok. This is with backing up/cross-signing enabled for the account. These problems only occur for the Tails sessions, when logging into other non-Tails OS devices with the same account - all encrypted messages can be viewed.
**Describe the solution you'd like**
I do understand that this problem is specific to Tails, but as Tails OS is targeted for anonymity/privacy - Element is a perfect 'fit'. Could an 'official' or at least a working method be communicated in some way. If there was built-in way to use a proxy in the client & choose a config folder so that the Persistent Tails folder could be used more easily, that would probably make things easier.
**Describe alternatives you've considered**
If it is hard to achieve in Element then possibly another linux/debian compatible client could be used - but as far as I'm aware feature parity hasn't really been achieved yet on alternative clients
Contributor guide
Assessment
This issue has not been assessed yet.