sipb / uplink

SIPB's integrated chatroom project
GNU Affero General Public License v3.0
6 stars 1 forks source link

Are room presets/behaviors sane? #89

Closed gabrc52 closed 1 year ago

gabrc52 commented 1 year ago

Let's test last minute

Quasi-duplicate of #85

gabrc52 commented 1 year ago

First if we ignore spaces:

Private, no e2e

image

This gives a warning, so E2EE is expected for "privtae chats"

I think group DMs use the trusted private preset

Public:

image

For now let's ignore rooms in a space but we have confirmed that the default configuration is entirely delegated to the homeserver so we can configure it from the Synapse side

gabrc52 commented 1 year ago

Related to #85

gabrc52 commented 1 year ago

image

This could force end-to-end encryption, maybe even with email invites. But it could lead to lost messages? We would need some testing, so that's not a right now thing but a in a week or two thing.

image

We can customize the power level override specifically.

Bad news

This is all Synapse lets us customize. So uh. Yeah. I think it's fine for launch but pls it's important before launching to more people. It would really suck if people end up with missing messages and ask for help and I will have no way to help them because this can't be changed retroactively.

gabrc52 commented 1 year ago

Okay so with testing it did retroactively import messages

Okay so UI-wise

image

Plus a general "add" button

image

History visibility does default to "shared"

image

Which is exactly what we want:

image

gabrc52 commented 1 year ago

Yeah so for rooms not in a space it's fine, which is what we need for now. Even in end-to-end encrypted rooms you can see past messages, which is superior to Signal!

Now let's test spaces:

There's public and private spaces:

image

For private spaces, a valid and encouraged use is as a folder to categorize your own stuff.

image

If you select "just me":

image

It still acts as a normal space, since you have to explicitly "Add new room":

image

If you select "me and my team-mates":

image

If you get a public space, it shows this:

image

If you ask for a public room it forces you to set an alias, which is not true for the rooms created via the wizard above:

image

Also the wizard marks the rooms as "suggested":

image

Now the issue is that if you make a room in a space that is either visible to space members only or private the history visibility is set to invited

I think something that is very distinct about Element is that the people section is group chats and the rooms section is for your rooms, and they do insist on that, even in spaces. Since everything is a room in Matrix, it's hard for me to see it now, but I mean it makes sense. Discord has DMs and Slack has DMs, so the people section aims to recreate that, and "rooms" in the GUI mean like, channels.

gabrc52 commented 1 year ago

Well, I assume by FPOP people are not gonna create spaces yet, probably just rooms

gabrc52 commented 1 year ago

On Android, if you "start chat", "Banana made future room history visible to all room members."

On Android, if you make it for space members only:

image

"Banana made future room history visible to all room members."

the Element-Android behavior is inconsistent with Element-web

As for private rooms in a space, it's the same thing.

gabrc52 commented 1 year ago

iOS:

Group DM: shared

Create new private room: supposedly shared but not in practice

image

HUH there is not even consistency on whether shared means you can see old end-to-end encrypted messages

image

In spaces:

HUH encryption is suggested by iOS for PUBLIC rooms