Olm support

[ZWindL]

Will this client support olm?

[mujx]

Eventually yes, that's the plan at least.

[ZWindL]

wow! good, thanks.

[mujx]

It's too early to be thinking about Olm though. There are lots of basic features that need to be implemented first.

[Qualitymix]

On the contrary, I think one of the primary reasons anyone would choose to use Matrix as a service is the end to end encryption it provides. It's the only reason I'm still forced to use the Riot client. I would think that this feature would be far more important than animated GIFs or other features.

[MTRNord]

@Qualitymix i think it is the hardest Feature too at the same time ;) that's why it isn't added early

[mujx]

@Qualitymix Currently my focus is on providing a stable base, so you won't have to log into Riot to use Matrix. Vital features like joining a room and accepting an invite are missing. After this goal is achieved I would definitely look into encryption (and yes, encryption is more important than gifs 😛).
Of course any contributions towards that direction are really welcome.

[r3k2]

Dude every channel I get invited uses encryption.. this is VERY Important.. is one of the top 10 usabily things.. almost no channel is open now a days.. at least not the important ones.. so please make this a priority im so tired of electron is not even funny. :P

[mujx]

@ReK2Fernandez Yeah, I guess it's time to at least start looking into e2e because the basic features are already there.

[r3k2]

@mujx thanks for the reply, hehe I think im not the only one tired of electron and looking for a decent desktop app :) any ideas when development will start? I am so eager I wont mind alpha/beta testing
https://matrix.org/docs/guides/e2e_implementation.html

[qazip]

I'm also definitely tired of that other bloatware, so much that I wont be using matrix until there's a proper client with E2EE (This is a feature I absolutely need).

@mujx, do you've any sort of ETA for E2EE?

[mujx]

@qazip There isn't an ETA because there hasn't been any progress yet, mainly due to the lack of time from my side. I will definitely start working on this after the v0.2.0 release.

[mujx]

Just an update on the roadmap for e2ee.

There is a new repo (https://github.com/mujx/mtxclient) for a client library for matrix, which will have all the encryption related parts & it will replace the current ad-hoc matrix client implementation on nheko. This was done so we can improve the test-ability (very important for the crypto implementation) of the library and decouple it from qt, so it could be used on non-qt applications.

The first step is implement the endpoints currently in use in nheko (1 - 2 weeks), so we can make the switch & then we can start working towards the e2ee functionality.

[MTRNord]

@albjeremias out of interest: is there some actual Suggestion about the Integration or is your comments pure "flaming"? The reason of having Integrations is exactly to have third-Party Software in riot. (and if you just dont like it because scalar is closed source: there is also Dimension by TravisR)

[albjeremias]

Hi sorry.. I didn't meant to be rude... i am just concerned user with my privacy, security and be free as in freedom from companies which make profit from my data. It's very sad to see the comment deleted and I'm sorry if it sounded like flame, i would like people to join on making great software for privacy and security, in the style of tails.. it could also be optional of course..

[MTRNord]

@albjeremias about the Integrations: none of them get any Information about you until you activate them manualy. But that's not a discussion for this issue

[mujx]

@albjeremias I deleted the comment because most of its contents were not meant for this issue or project, but for Riot's issue tracker, so in this context it looked like spam/rant (e.g nheko doesn't use javascript, so there is no point discussing XSS).

The only relevant comments were about the read receipts for which there is an issue already (#261) & the UI/UX of the unverified devices for which you can open a separate issue.

This issue is used primarily to track the status of e2ee in nheko. So far we don't have anything implemented. Please don't take this the wrong way, you're of course very much welcome to help nheko & matrix in general but please try to keep things on topic.

[mujx]

An not so extensive checklist towards e2ee https://github.com/mujx/mtxclient/issues/24

[qazip]

Am I reading this right? Does nheko support E2EE now? If so, this is game changer!

[mujx]

@qazip Yes the core is there. There are some things left to be implemented and make it more robust.

[lbeltrame]

Would bug reports be already welcome, or is it too soon? (As I just built this from source and played a bit with it) - Also I assume reports (if wanted) should go to mtxclient rather than nheko?

[mujx]

@lbeltrame Reports are most certainly welcome. If you're using nheko open an issue here.