Update: Add Mactrix client

[awtj8o81ryywg793]

Description

Add Mactrix client.

Related issues

Closes #3152.

Role

Individual not affiliated with any project relevant to this PR.

Timeline

There’s no immediate deadline, so feel free to review this PR whenever you can.

Signoff

Please sign off your individual commits or whole pull request.

[awtj8o81ryywg793]

In regard to 010c717, I have confirmed that Mactrix currently supports E2EE for text messages. However, I was later informed that this support is limited to text messages and does not extend to images. See 08cf3fc.

[HarHarLinks]

looks good, I'm just not sure about the maturity. README says "early development". We still haven't clear criteria for judging maturity though.

[awtj8o81ryywg793]

Quoted from a previous comment:

looks good, I'm just not sure about the maturity. README says "early development". We still haven't clear criteria for judging maturity though.

I'm also not 100% sure about choosing "Beta" for the client's stability. I chose it because, even though it is early in its development, it doesn't seem that users will lose data by using the client. But I could be wrong about that. I'd appreciate insight from its maintainer(s).

I would welcome clarification on the criteria for project maturity.

[viktorstrate]

Hi creator of Mactrix here.

It is definitely meant to support encryption, it supports creating, joining and viewing existing encrypted rooms. Further it supports device emoji verification. Only images are not working yet, but this should be fixed quickly. So I think it's misleading to state that it doesn't support encryption.

As for maturity level, I don't know how that is determined generally, but the client utilises the matrix-rust-sdk, which is one of the most stable and featurefull implementations of the Matrix client spec. Although not all features of the sdk is implemented in the client (yet), it does mean that the client is quite stable and for sure useable for everyday use in its current state. That being said the project is for sure still young.

[HarHarLinks]

My conclusion for now would be to call it alpha. I also think the expectation for a client supporting e2ee is to actually encrypt attachment, hence the call @awtj8o81ryywg793 made is correct imo.

@viktorstrate naturally if as its maintainer you would like to not add it to the website before being more mature or having certain features, we are happy to put this PR back into draft!

[viktorstrate]

@HarHarLinks I completely understand your reasoning. I think it's fair to mark it as alpha. However, I'd really prefer if E2EE was marked as supported before adding it to the website.

This pull request viktorstrate/mactrix#13 just fixed images not working in E2EE rooms. Please let me know what else is missing before we can mark E2EE as supported?

[awtj8o81ryywg793]

Quoted from a previous comment:

This pull request viktorstrate/mactrix#13 just fixed images not working in E2EE rooms. Please let me know what else is missing before we can mark E2EE as supported?

Since media was the only thing missing from the client's E2EE support, I've noted that the client supports E2EE. See 8451e3d.

[viktorstrate]

Alright, this PR looks good to me now! Thank you for taking the initiative to add it 😄

[HarHarLinks]

Alright, this PR looks good to me now! Thank you for taking the initiative to add it 😄

Please feel free to PR updates whenever you have them! 🚀

[HarHarLinks]

Thanks all involved!