• 16 Posts
  • 37 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle

  • ono@lemmy.catoPrivacy@lemmy.ml*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    9 months ago

    Whether to use encryption is a per-room setting, not per-server. It’s controlled by the person who creates the room, not the server admin. It’s on by default, and cannot be switched off later.

    Rooms can be created without it because that makes sense for large public rooms, like those migrating from IRC, where privacy would defeat the purpose.





  • Correcting some misconceptions…

    Element for Android doesn’t support searching in encrypted channels

    That’s true of regular Element for Android, but it’s being replaced with Element X (which is built with Rust). I would expect search to be added there if it isn’t already.

    and I think you can’t use E2EE in the browser at all(?)

    I have done it in Firefox, so that’s false. Perhaps you had trouble with a specific browser?

    plus basically every other client has even more drawbacks when it comes to E2EE.

    Nheko handles E2EE just fine, so that would seem to be false as well.

    Since you’re looking for recommendations, it would help if you said which clients you tried and what problems you had with them.

    In case you haven’t seen it, you can set a Features: E2EE filter on this list:
    https://matrix.org/ecosystem/clients/


  • Not really an answer to your question, but just to make you aware of some options:

    Have you considered using subkeys for each of your machines, signing things with those, and keeping their master key someplace safe? That would limit your exposure if one of those machines is compromised, since you could revoke only that machine’s key while the others remain useful (and the signatures they have issued remain valid).

    Are you setting expiration dates on your keys? That can bring some peace of mind when you lose your key/revocation data.