News for hackers. Stuff that matters.
Re:Cross-signing and end-to-end encryption by default by rattray on Thursday May 07, 2020 @04:40PM (#23108029)
Folks who have tried Matrix/Riot and Slack – how does the product quality compare?

Slack has many issues (little bugs, latency, notification issues, the shitshow markdown editor) but overall delivers a smooth product experience IME. When you self-host Matrix, do you typically get great perf without much effort? Is the product experience of the Riot client smooth and complete?

Re:Cross-signing and end-to-end encryption by default by Arathorn on Thursday May 07, 2020 @04:53PM (#23108166)
Historically, Riot's UI hasn't been as smooth as Slack's - for many years we didn't have any professional UX/UI designers contributing to the project, and we built up a lot design debt along the way.

Over the last year or so we've been progressively working through fixing it, and as of Monday we now have three(!) professional designers working full time on the problem. Having turned on E2EE by default, our next big project and single biggest priority is First Time User Experience - making sure that the app is at least as smooth as Slack and Discord, particularly on first impressions. https://blog.riot.im/e2e-encryption-by-default-cross-signing... has more details - and the sections before it show some of the UI/UX work which has been landing in the last few months.

Re:Cross-signing and end-to-end encryption by default by ssivark on Thursday May 07, 2020 @08:52PM (#23110203)
First off, let me start with thanks :-) As an end user I lack an appreciation for what goes into this; but as someone who writes software, I know the amount of effort that goes into kicking out a polished piece for others to gawk at and comment on. So kudos, definitely.

Further, it is definitely worth taking inspiration from Discord. Newbies seem able to pick it up very quickly. Some Discord rooms feel about as alive as happening IRC channels from back in the day, and the interface+culture seems to do a great job of supporting that.

Fairly subtle, but important things like where the names are placed relative to the messages, and the size of the avatar/image, etc keeps the interface from becoming crowded (in comparison with the Riot desktop interface, for example). The Riot iOS interface gets several of these things right, btw :-)

It also seems to be fairly easy to customize “Discord servers“ with different levels of organization — scaling from few users to 1000+ users. Not just the backend, but the interface also scales very well. From a pure usability standpoint (apart from privacy issues, centralized, etc the user experience in Discord is fantastic.

Re:Cross-signing and end-to-end encryption by default by kixiQu on Thursday May 07, 2020 @09:49PM (#23110543)
Let me just note that my beloved boomer parents did not find Discord easy to pick up quickly when the family tried to video chat. (My sainted mother installed Riot because I asked her to, and it's worked so far)
Re:Cross-signing and end-to-end encryption by default by godelski on Thursday May 07, 2020 @05:17PM (#23108468)
I just played around with Riot for the first time. Can you directly reply to a comment in a chat room like you can in Slack (like the sub chat thing, I'm not sure what to call it)? I actually find this an extremely useful feature that allows rooms to to be uncluttered with side conversations (which as room sizes grow, this becomes a HUGE benefit). I may be missing this or I can't do it in a room of only me?
Re:Cross-signing and end-to-end encryption by default by Arathorn on Thursday May 07, 2020 @05:25PM (#23108558)
We have 'replies' (which lets you post a message into the main timeline which refers to an existing message in the timeline), but we don't yet have 'threads' (which lets you branch the conversation into a sidebar).

The protocol actually has support for label-based threading (i.e. "hide all messages tagged #gif" or "only show messages/conversations in this room tagged #work") already, as per https://github.com/matrix-org/matrix-doc/blob/matthew/msc232.... But we haven't had a chance to hook this up into Riot yet, thanks to all the work spent on E2EE by default.

Proper threads will come in time however.

Re:Cross-signing and end-to-end encryption by default by 0az on Thursday May 07, 2020 @10:15PM (#23110694)
Hot take: slack-style threads are bad for long-form discussion. They encourage forking, when what you really want is everyone to be on the same page. Traditional forum-style threads, or "channels" on a chat app, is optimal for discourse, as it encourages continuous convergence and integration rather than splintering. Hiding tangents serves to lower the quality of conversation.

Optimal within the constraints of real time chat IMHO is slow-mode (5 to 15 seconds, or possibly greater) in a single channel.

Re:Cross-signing and end-to-end encryption by default by godelski on Friday May 08, 2020 @12:39AM (#23111442)
IME tangents, while possibly fruitful, just lead people to skip the 30+ messages and so doesn't become helpful.

Hot take: make threading an option. If you don't want them, don't use them. If you want them, then they are available. This is clearly a personal difference with no right or wrong answer. So the solution is options.

Re:Cross-signing and end-to-end encryption by default by godelski on Thursday May 07, 2020 @05:31PM (#23108612)
Thanks for the reply! Yes, threads. That's what I'm thinking of. I find these super useful. I know some people don't like them, but they can just not use them if that's their preferred style. I would really just like threading a comment rather than having to label everything. I'll be honest, I'll just get lazy and not label. I doubt I'm the only one too, or in the minority.

> Proper threads will come in time however.

Awesome, this was really the only thing that makes me hesitant to switch. I can stand an ugly UI if I can get good conversational flow.

Re:Cross-signing and end-to-end encryption by default by the_duke on Friday May 08, 2020 @06:39AM (#23113276)
I find Zulips threading/topics UI brilliant for certain kinds of channels and discussions.

I hope that Riot will implement something similar, potentially as an individual or per-channel setting.

Re:Cross-signing and end-to-end encryption by default by j-james on Thursday May 07, 2020 @05:24PM (#23108539)
No, it looks like threads aren't (yet) supported in either Riot or the Matrix spec.

https://github.com/matrix-org/synapse/issues/2329

https://github.com/vector-im/riot-web/issues/2349

Re:Cross-signing and end-to-end encryption by default by ShamelessC on Thursday May 07, 2020 @05:24PM (#23108540)
I believe those are threads and while I have no opinion on the subject because I don't really use slack anymore, I remember them being pretty controversial here.
Re:Cross-signing and end-to-end encryption by default by x3haloed on Thursday May 07, 2020 @05:14PM (#23108434)
In my experience, Matrix and Riot are great. I love the protocol and concepts around it, and Riot was much higher quality than I expected it would be. Since trying it out for a while a few months ago, I have since abandoned it, however, because operating my own Synapse server was just too much work.

Specific pain points were:

- setting up SSL - getting Let’s Encrypt certs onto a server without a web server was a pain, and keeping them up to date was even worse. I would love to see ACMEv2 support integrated into Synapse for painless SSL setup.

- TURN server - if you want to use voice chat, you need to set up a separate TURN server, which has its own set of challenges. Again, I would love to see a solution integrated into Synapse.

- Video chat - Even with a TURN server in place, video chat requires a separate plugin to work. Jitsi is recommended, I believe. Yet again, I want this integrated into Synapse and Riot.

- Federation - Federation is part of what makes the Matrix protocol so great, but it was a huge pain to configure in Synapse. I spent hours to get it working, and it still had quirks about matrix.mydomain.tld vs mydomain.tld. I would like to see this simplified.

Probably the thing I was happiest about is that a ton of administrative settings are easy to work with in the Riot web client.

Keep it up, guys! I hope Matrix takes over the world, and I hope to come back some day.

Re:Cross-signing and end-to-end encryption by default by Arathorn on Thursday May 07, 2020 @05:23PM (#23108526)
Sorry to hear that :( There are two things we've tried to do to fix it:

1) Running Synapse really isn't that hard if you follow best practices... but I think we've done a bad job of communicating those best practices; instead Synapse's INSTALL.md lays out tonnes of different options and expects folks to pick their poison. I tried to fix this a few weeks ago by sitting down and recorded a dorky video to try to steer folks through best practices for setting up Synapse + certbot + Jitsi: https://matrix.org/blog/2020/04/06/running-your-own-secure-c.... (I need to extend it to coturn, but again, coturn should be straightforward. I don't think we should be baking TURN into Synapse though!). You could also shove everything in Docker and forget about it.

2) Peer-to-peer Matrix will let you get up and running without even needing a server. This is progressing alarmingly rapidly at the moment - https://p2p.riot.im is a version of Riot/Web which installs a homeserver (Dendrite) in your browser as a WASM service worker. It's alpha, but it mostly works pretty well, and is hopefully the shape of things to come - to let people have autonomy over their comms without ever needing to understand SSL, TURN, etc.

Re:Cross-signing and end-to-end encryption by default by x3haloed on Thursday May 07, 2020 @05:35PM (#23108653)
Thanks for the reply! I understand not wanting to re-implement entire servers within Synapse. Maybe an installer util would go a long way towards making setup more manageable. A step to automatically download and configure coturn, for example, could be very helpful.

I also understand that making things too turn-key (no pun intended) can be extremely difficult to do well and can also impede advanced configuration. But there is somewhat of an incongruity between the Matrix philosophy of keeping private servers vs. the expertise required to actually get that done.

P2P sounds really cool! I’ll try it out.

Re:Cross-signing and end-to-end encryption by default by x3haloed on Friday May 08, 2020 @11:43AM (#23116036)
I’m getting the following error when using the P2P instructions. Is this likely an from an outage?

https://photos.app.goo.gl/myGNh77ukXWgqaVX9

Re:Cross-signing and end-to-end encryption by default by Arathorn on Friday May 08, 2020 @02:18PM (#23117782)
https://p2p.riot.im is a webapp and runs in browser.
Re:Cross-signing and end-to-end encryption by default by xamlhacker on Thursday May 07, 2020 @06:27PM (#23109098)
For the SSL part , I have been looking at Caddy as it seems to have pretty simple reverse proxy over SSL setup.
Re:Cross-signing and end-to-end encryption by default by infogulch on Thursday May 07, 2020 @07:44PM (#23109712)
Reverse proxy with Caddy to get mindless automatic TLS is incredibly easier than any other setup for something you want to just work. I wish more projects supported reverse proxy setups better.
Re:Cross-signing and end-to-end encryption by default by lifty on Thursday May 07, 2020 @05:19PM (#23108488)
Synapse is a beast. I am looking forward to a more compact server to become viable. Matrix is working on Dendrite (https://github.com/matrix-org/dendrite) and there is Conduit (https://conduit.rs) as well.
Re:Cross-signing and end-to-end encryption by default by Arathorn on Thursday May 07, 2020 @05:30PM (#23108608)
Dendrite is rapidly approaching the point where it could be considered beta rather than alpha. However, it doesn't have any of the richness of Synapse yet, and it'll be a while before it can be used as a Synapse replacement. Meanwhile, Synapse keeps shrinking and is getting a lot of performance love - so personally I'd give keep giving Synapse a go for now. It's a smaller cuter beast these days :)
Re:Cross-signing and end-to-end encryption by default by drdaeman on Thursday May 07, 2020 @06:02PM (#23108884)
I've just tried it again a week ago (last time was ~2 years ago).

While there's definitely lots of improvement, it's still painfully slow and eats lots (like, 40% of 1 core) of CPU time. Took me a two attempts and a couple minutes (!) to join a relatively crowded room at #synapse:matrix.org on a freshly installed Synapse. I get it that there are over 12k people in there, but I haven't seen any other platforms having similar issues.

And this just doesn't feel right, design-wise. It could take a long while loading user pictures, presence states, ancient chat history and extra fluff. But seeing the most recent messages* and having an impression of joining the room should be nearly instantaneous.

Still a huge improvement over what it used to be. I remember waiting for no less than 10 minutes in a similar scenario, and it used to consume nearly 100% of CPU available.

*) For some reason, previews never worked for me. Despite being able to join, when just trying to peek I always get either the never-ending "loading" spinner or "this room can't be previewed" message.

Re:Cross-signing and end-to-end encryption by default by Arathorn on Thursday May 07, 2020 @06:15PM (#23108982)
So the problem is that if you join a room with lots of different servers, your server has to go handshake with each one to check its signing key in order to verify the events the server has emitted. #synapse:matrix.org is almost by definition one of the worst rooms for this, given most people in there are joining from their own server.

Solving this is an interesting challenge - one option could be to opportunistically trust events. Another could be to opportunistically fetch server signing keys. A better one would be to implement MSC1228, which switches all our IDs for public keys, which should make verification much easier and less burdensome.

In terms of peeking rooms over federation - sadly this still isn't implemented yet. https://github.com/matrix-org/matrix-doc/blob/matthew/msc244... is the proposal to fix that however.

Re:Cross-signing and end-to-end encryption by default by drdaeman on Thursday May 07, 2020 @06:29PM (#23109119)
Ah, so the server that hosts the room is not fully authoritative and messages from participants are all signed by their respective server owners?

This makes sense. Thank you for explaining!

Re:Cross-signing and end-to-end encryption by default by Arathorn on Thursday May 07, 2020 @06:33PM (#23109142)
Yup, precisely. In Matrix, rooms are not hosted by any single server - instead, they're replicated over all participating servers, much like git. But you need to check the provenance of the original messages to stop spoofing, hence needing to go check signatures the first time you interact with messages from a given server. Once you're joined, things should be fast however.
Re:Cross-signing and end-to-end encryption by default by smichel17 on Thursday May 07, 2020 @10:51PM (#23110922)
Food for your UI folks' thought:

Basically it sounds like you can download the messages relatively quickly from any old server, but the first-time process of verifying takes awhile. Maybe there's a way to show that visually, so you can get the messages up on screen earlier, even if the content isn't trusted yet?

It also seems like there might be gains from prioritizing connections with servers whose members chatted more recently.

Re:Cross-signing and end-to-end encryption by default by MayeulC on Thursday May 07, 2020 @06:08PM (#23108935)
Oh, and there is construct as well, not to be forgotten (C++ homeserver). It federates, and works with most clients, though it lacks a few features (link previews, a couple others). I've interacted with a few of its users over federation, though I haven't tried it myself.

Compared to synapse's resource use, it seems completely anemic (I've read that the lead developer makes it run on a 800 MHz pentium, though that could have been a joke).

https://github.com/matrix-construct/construct

https://matrix.org/docs/projects/server/construct

Re:Cross-signing and end-to-end encryption by default by x3haloed on Thursday May 07, 2020 @05:37PM (#23108667)
Thanks for sharing! I’ll give them a look. As an aside, another protocol I would really love to see a simple implementation for is LDAP. Through my research, it seems that every LDAP controller server out there is just monstrous. I would love a cross-platform, turn-key solution that provides just the basics: user management, authentication, and replication. There has to be a better way to manage identities across internal networks.
Re:Cross-signing and end-to-end encryption by default by rakoo on Thursday May 07, 2020 @04:55PM (#23108196)
Been self-hosting for a few weeks, and it's working exactly as expected. I find Slack to be slightly more reactive but not by much (I'm comparing a company-wide workspace of ~10 actually active people, vs a little channel of ~5 actually active people).

Personally though I can't stand the conversation view in Riot, the spacing between the nickname, the avatar and the text feels just wrong and I can't see in a glance who is talking and says what (yes, even with the compact view). It's minor, but it's the one I have under my eyes at all times so it's there. For now I'm using another snappier client (https://neo.pixie.town/) because of this issue.

Apart from this client-specific issue that doesn't say anything about the protocol itself, everything is fine.

The one thing I'm waiting for is rooms where participants are hidden, so that you actually get closer to a pubsub system. I have some ideas I want to try and play with, but this is needed if you want to keep some privacy

Re:Cross-signing and end-to-end encryption by default by Arathorn on Thursday May 07, 2020 @04:59PM (#23108251)
> Personally though I can't stand the conversation view in Riot, the spacing between the nickname, the avatar and the text feels just wrong

Does https://github.com/matrix-org/matrix-react-sdk/pull/4531 look any better? O:-)

> The one thing I'm waiting for is rooms where participants are hidden, so that you actually get closer to a pubsub system.

This is surprisingly hard (if you don't know what users are in a room, how do you know what servers to send messages to?) but we can provide at least a cosmetic solution (have the server filter out members below a given power level when relaying to the client). https://github.com/vector-im/riot-web/issues/6417 is the bug to upvote :)

Re:Cross-signing and end-to-end encryption by default by rakoo on Thursday May 07, 2020 @05:37PM (#23108668)
> Does https://github.com/matrix-org/matrix-react-sdk/pull/4531 look any better? O:-)

Hey that's actually kinda sexy ! I'm not looking specifically for IRC-style <timestamp/nick/message>, I do like it when it takes a bit more space for the user, but I find this rendering nice to the eyes.

In the quote though, why is the user cast away on the right ? Would be more consistent to put it right next to the timestamp of the quoted text

Also, the nick is chopped at the end without any indicator that it is (like a [...] at the end or something)

All nitpicking, I know, I'll try this as soon as it lands because I already like it :)

> https://github.com/vector-im/riot-web/issues/6417 is the bug to upvote :)

I'm following it closely ! I can't wait to experiment around that, Matrix.org can be and needs to be much more than just a messaging protocol, there's everything needed to get rid of centralized silos of (micro-)blogging, status- or photo-based social networks, ...

BTW thank you for doing this and thank you for leading it all the way to it is today and to where it's gonna be tomorrow, there's a reason protocols fail or succeed and it's often not in the technical intricacies but definitely in the leadership that spearheads its spread. Matrix seems to be the one that has the biggest momentum for now :)

Re:Cross-signing and end-to-end encryption by default by Arathorn on Thursday May 07, 2020 @05:53PM (#23108794)
> In the quote though, why is the user cast away on the right ?

> Also, the nick is chopped at the end without any indicator that it is (like a [...] at the end or something)

These were just bugs in the first cut. I'll spin up a dev client and grab a screenshot of the final version (i think dev finished on it today!)

> BTW thank you for doing this

np. I just hope we realise the full potential of the project :) For what it's worth, I hope that Matrix can be to Slack/Discord what Linux was to Solaris/AIX. So, we just need to not screw up...

Re:Cross-signing and end-to-end encryption by default by opan on Friday May 08, 2020 @12:24AM (#23111367)
That looks a lot better, but I'd also like to be able to have timestamps and nicks on every line, like when the same person says 3 things in a row. This way if the first message were bumped off the screen, you don't have to scroll around to see who said it. (like irssi, hexchat, etc.)
Re:Cross-signing and end-to-end encryption by default by bhauer on Thursday May 07, 2020 @05:40PM (#23108688)
> Does https://github.com/matrix-org/matrix-react-sdk/pull/4531 look any better? O:-)

Substantially better than the default Riot layout. I hope this gets merged and I get to switch to this soon.

That said, I'd still like a more compact version of the same that further reduces the spacing/padding to make more information fit on a single screen.

Re:Cross-signing and end-to-end encryption by default by a1369209993 on Thursday May 07, 2020 @08:37PM (#23110073)
> > The one thing I'm waiting for is rooms where participants are hidden, so that you actually get closer to a pubsub system.

> This is surprisingly hard (if you don't know what users are in a room, how do you know what servers to send messages to?)

Can you expand on what your threat model is in this case? Because I assumed rakoo was just talking about a cosmetic change (possibly coupled with allowing pseudonymous users with low (read-only) permission levels, but you'd have to go out of your way to break that).

Re:Cross-signing and end-to-end encryption by default by godelski on Thursday May 07, 2020 @05:27PM (#23108576)
Not the parent, but I do think that looks better. I do think their client looks better than that, though. I'm a big fan of dark themes.
Re:Cross-signing and end-to-end encryption by default by rpm91 on Thursday May 07, 2020 @06:00PM (#23108865)
For the client experience, it's not even close: Slack's product experience is far superior. I love the idea of Riot as a decentralized e2ee group chat client, but the implementation is so buggy and far from being production-ready that any attempt to use it seriously is an exercise in frustration. In comparison, Slack is mildly annoying at worst, and usually just works.

If it were one or two little things, I'd file some bugs or even try to fix the issues myself in the Android app, but my experience has been that I have at least one experience-breaking bug or UX issue at least every other time I interact with the client. Especially if you have encryption enabled.

Re:Cross-signing and end-to-end encryption by default by rattray on Thursday May 07, 2020 @08:22PM (#23109960)
Thanks, that's helpful. When was the last time you used Matrix/Riot?
Re:Cross-signing and end-to-end encryption by default by rpm91 on Friday May 08, 2020 @10:57PM (#23121813)
Today. I have a friend who insists on using either that or Snapchat, and Snapchat doesn't have a web client, so Riot wins for that reason alone.

True to form, I experienced yet another bug with the encryption moments ago: on web, search appears to be completely broken in e2ee rooms. It just says "No results", even for words that were said in literally the last message (and messages not far back in history from the previous day, so unlikely to be a caching issue).

Re:Cross-signing and end-to-end encryption by default by Arathorn on Saturday May 09, 2020 @06:11AM (#23123498)
E2EE search only works on Desktop currently. We need to spell that out in the UI.
Re:Cross-signing and end-to-end encryption by default by rattray on Saturday May 09, 2020 @12:08AM (#23122236)
Wow!
Re:Cross-signing and end-to-end encryption by default by doublerabbit on Thursday May 07, 2020 @08:04PM (#23109841)
I don’t like slack having to use it for work. And riot/matrix has been slightly disappointing. At one point t I had everything flowing nicely; working fine until now the latest upgrade.

The verification within the client is confusing. The e2e cross signing has been an absolute headache. Meaning losing some encrypted messages because using your recovery key it throws an error (when it’s valid).

The potential is there but It does need work. My first impressions are that it feels like it’s all stringed together.

For example why have a button in the IOS app for resetting bootstrap only to display a message of “this button doesn’t work but will work in future”.

The default home server can be terribly slow. I get it, running your own server but still, I don’t want to do that right now.

It’s works when it wants to work. And when it does, it’s pleasurable and smooth.

https://github.com/vector-im/riot-web/issues/13519 expresses my frustration.

Re:Cross-signing and end-to-end encryption by default by Arathorn on Thursday May 07, 2020 @08:12PM (#23109889)
I think you hit the matrix.org server being completely overloaded immediately after we enabled cross-signing (https://twitter.com/matrixdotorg/status/1257695491497897988) - now fixed. You hit other teething bugs too where it didn't recover sufficiently from the overloaded server. Apologies :( The bug is open and on our radar, as you can see.
Re:Cross-signing and end-to-end encryption by default by doublerabbit on Thursday May 07, 2020 @08:27PM (#23109992)
Any idea to when it might be fixed? I still can't verify any devices and using the Use Recovery Passphrase or Key method still responds with nothing.

If the whole premise of matrix is encrypted chat, and I can't verify myself, I'm hesitant in using the app. Luckily I am only using it to talk to a single friend so it's not a too big deal at the moment.

Re:Cross-signing and end-to-end encryption by default by bwindels on Friday May 08, 2020 @04:23AM (#23112603)
Sorry for this inconvenience. We're working on it, see linked issues to your issue.
Re:Cross-signing and end-to-end encryption by default by tryptophan on Thursday May 07, 2020 @08:41PM (#23110101)
I find Riot/Matrix to be very feature-poor compared to Discord and Slack, and not nearly as polished as Signal/WhatsApp for just pure chat purposes. Its best at nothing.

I find the lack of ability to group chat rooms, into discord "server" type things or Slack "workspaces" or whatever they're called, to be particularly deathknelling for Matrix's usefulness.

The matrix answer, "communities", are in the works, but who knows how good it will be.

Re:Cross-signing and end-to-end encryption by default by f38zf5vdt on Thursday May 07, 2020 @05:09PM (#23108367)
I use it. It's extremely easy to setup your own server and I got mine running in about 30 minutes following their instructions. Aside from issues around key exchange in earlier versions, it's been great and on par with Discord or Slack, and with similar reliability.

I've been told the apps (Android/iOS) aren't as good as the Desktop version by coworkers.

Re:Cross-signing and end-to-end encryption by default by Arathorn on Thursday May 07, 2020 @05:15PM (#23108438)
Interesting - Riot is actually four entirely different codebases: Riot Web/Desktop (JS/TS/React), Riot iOS (ObjC/Swift), RiotX Android (Kotlin) and Riot Android (obsolete, Java).

Riot iOS has been a bit under resourced over the last few years, but other than some jank it's a decent native app, albeit trailing behind Desktop a bit. RiotX meanwhile is of very similar quality to Desktop, albeit beta (but exiting next month, hopefully). Finally, Riot Android is abandoned now and we'll replace it with RiotX when RiotX is ready. Many folks' bad impression of Riot on mobile is due to Riot Android having been abandoned in favour of RiotX or the last year - such is the cost of a rewrite :/

Re:Cross-signing and end-to-end encryption by default by rpm91 on Thursday May 07, 2020 @07:04PM (#23109415)
Do you know why the decision was made to rewrite rather than do an incremental migration, given the increased pain to users? I have some guesses from looking at the codebase, but I'd love to know the actual answer.
Re:Cross-signing and end-to-end encryption by default by Arathorn on Friday May 08, 2020 @04:51AM (#23112765)
The old app had bad layering, and no explicit storage layer. We wanted to experiment with different storage layers, use rx for data flow, switch from java to kotlin, and use all the latest androidx/jetpack best practices. This amounted to a whole new app, and it was easier to start from scratch, despite the disruption to users.
Re:Cross-signing and end-to-end encryption by default by cycomanic on Saturday May 09, 2020 @01:41AM (#23122584)
I have to say riotx is miles ahead of riot android. If only it could do voice and video yet. For desktop I have to say riot has been really on and off. In particular voice/video calls are hit and miss. Sometimes it rings but one can't pick up, sometimes it just does not ring. I actually have been experimenting with some of the alternative clients (I particularly like nheko reborn) unfortunately non do voice video yet.
Re:Cross-signing and end-to-end encryption by default by Arathorn on Saturday May 09, 2020 @06:13AM (#23123508)
the 1:1 voip in Matrix has never been properly fleshed out. we’re planning to fix this over the next few months however.
Re:Cross-signing and end-to-end encryption by default by badrabbit on Thursday May 07, 2020 @06:52PM (#23109318)
Usable for technical people,but as they note at the end of the blog post, they have ways to go with respect to first time user experience.

I tried getting a team of tech savvy people to use it for backup encrypted comms, the UX was horrid, the key verification just didn't work at the time. Hopefully this is fixed.

I am hoping a commercial product comes out of this,so they have proper QA and UAT. The FOSS approach of filing an issue/bug when basic things fail does not translate well to a generic audience. The protocol and Riot are actually decent,but I think the UX has yet to catch up with the rich feature set.

Both Signal and Slack just worked. Slack has great UX, Signal is mediocre but from a security perspective, many things are non-obvious which to me feels like a dark pattern of insecurity,Riot maybe more painful but fails in more obvious ways.

Re:Cross-signing and end-to-end encryption by default by Arathorn on Thursday May 07, 2020 @08:13PM (#23109898)
> the UX was horrid, the key verification just didn't work at the time. Hopefully this is fixed.

This is what we've tried to fix in this release :) Meanwhile, as you note, first time user experience is our single biggest project now e2ee-by-default is shipped.

Re:Cross-signing and end-to-end encryption by default by baby on Thursday May 07, 2020 @09:45PM (#23110517)
I've been trying it these days, I'd say Slack is much slicker, but the differences are bridgeable.

One thing I don't like is that your message shows in grey for a few secs in Matrix. What does it mean? I don't know. But what does it feel like? Like it's lagging.