Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • G gajim-plugins
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 50
    • Issues 50
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 5
    • Merge requests 5
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gajim
  • gajim-plugins
  • Issues
  • #583

Closed
Open
Created Apr 04, 2022 by Joseph A@test4d

OMEMO: Conversations-like default settings

Please note by far the quickest way to get a new feature is to file a Merge Request.

Description of the new feature

Add the following options:

Always Encrypt | Gajim will always try to send messages encrypted with OMEMO.

On by Default | Gajim will always try to send messages encrypted with OMEMO, UNLESS the user has disabled OMEMO for that contact. This should be the default option on a fresh install of the plugin.

Off by Default | Gajim will not try to encrypt the message UNTIL the user has decided to use OMEMO for that contact.

(Always disabled) | not needed, the plugin already allows you to enable and disable accounts, and you can just not install the plugin if you don't want any encryption for any account.

if the user is trying to use OMEMO but their contact doesn't support it, don't send a message and tell them why

none of these options should apply to public MUCs (anonymous and/or open to all), OMEMO isn't even possible here because the users wouldn't be able to read each other's PEPs.

Why?

  • the current UI isn't very informative, its largely the difference of a single unassuming icon
  • For some non-technical users, they were coached by a technical user to use OMEMO. For non-technical folk, they may not understand what or why OMEMO should be used, but we should keep the system as simple as can be, because even the less savvy deserve privacy.
  • you must manually install and enable the plugin to even use OMEMO, by that action, the user clearly wants to use it, so it should be made easier/friendlier to do so

edit: i hate markdown lol

Edited Apr 04, 2022 by Joseph A
Assignee
Assign to
Time tracking