Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduction of a simplified room for conventional 1:1 messaging #1467

Open
Lalarian opened this issue Jan 26, 2021 · 2 comments
Open

Introduction of a simplified room for conventional 1:1 messaging #1467

Lalarian opened this issue Jan 26, 2021 · 2 comments
Labels
A-DMs A-Immutable-DMs O-Occasional Affects or can be seen by some users regularly or most users rarely S-Minor Impairs non-critical functionality or suitable workarounds exist T-Enhancement

Comments

@Lalarian
Copy link

Lalarian commented Jan 26, 2021

Is your suggestion related to a problem? Please describe.

Hello! I am just testing Element/Matrix with some friends, for it's adequacy as a future replacement for our current messenger (Signal). Matrix is and will be more and more important, with the EU courts having rules total surveillance of any type of online messaging.

But the room based concept of element makes it less suited for normal 1:1 chats than conventional messengers.
The general existence of features for opening a room towards others always leaves participants unsure about the room being actually secure, as:

  1. The room could be setup wrong, especially if it was setup by another person
  2. The room's settings can be changed anytime by a chat participant, unless you restrict him to user and keep yourself as admin
  3. As a workaround you always have to invite the others instead of having them invite you, so you at least have the necessary rights for degrading others to normal users and keep only yourself as admin. Of course this logically cannot work, as other conscious people prefer to be the inviting one with higher privileges, too.
  4. The above workaround requires you to patronize others, which isn't adequate in most situations. You don't want to invite your boss, or friend and degrade him to an user, while keeping only yourself as admin so you can be sure, that the chat will never be opened to public. It's just wrong. also you don't want to be at the mercy of anyone else in regards of security and privacy
  5. The room being a 'room' instead of a chat is stressful. The pure chance for the room being converted to public, no matter how much you trust for conversation partner, feels bad.
  6. Yes, there's a notification, when someone changes a room's settings- but when used as a messenger, it's not needed to ever change a room's settings, and just the very chance that someone, intentionally or by unawareness changes the room's settings is too much and just needless.

Describe the solution you'd like

Implement a new, special room type, which only has the two initial chat partners, with fixed settings, to never be opened for any other person or even public. Also change the UI to not show any room related options anymore for that room type, besides the room's deletion.** I think the easiest way to implement this could simply be to have both users start as unprivileged 'users' instead of 'admin' and set all invitation options to disabled/disallowed. This probably could be a pure client-side feature, unless a room's defaults are generally set by the server itself on creation. (web / Android..)

Describe alternatives you've considered

Go back to Signal? :(

Additional context

I think the suggested solution wouldn't need too much effort, as it's mostly based on blocking features instead of adding new ones. It would be great to see this change to Element, soon, as it just seems obligate to have a trustworthy 1:1 chat. Thanks! :)

@SimonBrandner
Copy link

@Lalarian Canonical DMs are on the roadmap

@Lalarian
Copy link
Author

Lalarian commented Jan 26, 2021

Great news, thank you!
Maybe my little idea of "abusing" the users permissions by setting both to unprivileged might be useful as a quick temporary workaround for the timespan until there's a better implentation.

@jryans jryans added the A-DMs label Jan 26, 2021
@MadLittleMods MadLittleMods added A-Immutable-DMs S-Minor Impairs non-critical functionality or suitable workarounds exist O-Occasional Affects or can be seen by some users regularly or most users rarely labels Sep 2, 2022
@t3chguy t3chguy transferred this issue from element-hq/element-web Apr 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-DMs A-Immutable-DMs O-Occasional Affects or can be seen by some users regularly or most users rarely S-Minor Impairs non-critical functionality or suitable workarounds exist T-Enhancement
Projects
None yet
Development

No branches or pull requests

4 participants