It is a serious and fundamental problem with multiple alternative of alternatives of system components to test and the problem may still happen deeper in the desktop stack and looking for the root cause is like finding a silver needle in the sky and would require a mixture or part time / full time devs to test or debug literally everything that is in the stack to reproduce or actually find it. The Linux Desktop however is eternally plagued with these issues and the support and testing is very expensive. It works fine on macOS as mentioned in that thread, especially with 4000 rooms on both Firefox and Chrome and supporting that is simple with a predictable desktop stack. It has been more than 20 years and the same fragmentation and inconsistency issues are still here. ![]() That is the problem with defining Linux Desktop support as I have said this many times before. The common factors that consistently exhibits this behavior seems to be Linux, element-desktop, account with large amount of rooms. This, too, only for those particular high-room accounts and only on element-desktop)įor a while we believed it could have been the same cause as this issue but alas, 1.11.0 with Electron 19 has not resolved it. (The slowness seems to be all or mostly locally in Element - even when in a mostly empty room, it can take a very long time expanding/collapsing/navigating the People/Rooms sidebar. This is also the case on an otherwise idle 8-core Ryzen3 with 64GB of RAM and fast NVMe drive sitting close to its homeserver on a 1GBps link. It gets more annoying by the fact that even under normal operations it's slow enough to start up that it can take some time to tell if this time it'll eventually resolve by waiting or if it needs to be force-killed and restarted. The same issue does not appear on Element iOS/Android, or with other accounts on the same client. Signing in to a fresh profile seems to improve this, for a while, until it starts happening again Other accounts in the exact same environment do not have this issue. This makes element-desktop practically unusable for that account. The common denominator seems to be that the account with many (thousands) of rooms (almost all of which fully historical/archived with no ongoing activity apart from participants presence) consistently gets Element freeze, hang, be extremely slow. In particular, multiple accounts on the same Linux installation of element-desktop. * Multiple Linux distros, desktop environments, window managers, X11/Wayland, CPU architectures (x86_64, aarch64) To emphasize, we have for the past couple of years used Matrix routinely on: Getting the same behavior across distros and installations. Not the person you're replying to but following up on an identical past thread: I recommend giving the platform another quick try using which to me feels very Discord-like in terms of snappiness. Latency also doesn't help, the protocol requires loads of round trips for the JSON payloads to go back and forth, so if you're not near your homeserver you're going to see some annoying problems. Performance is getting improved all the time, especially in terms of quickly joining a room. When joining huge chat rooms like some of those on the homeserver, it can take a bit for the clients to sync up and get going. On the desktop, Nheko is incredibly fast, being written in a native language and being optimized for performance and all, but I don't use it because I just can't get used to the design. On the other hand, Element is ahead in terms of features and protocol support (like the (live) location sharing feature), but Fluffychat has the superior mobile app in terms of general look and feel IMO. Picking the right client is very important, though Element isn't always the fastest, and I find Cinny's UX to be much better for general chat, which is clearly very much… inspired by Discord. I'm running it on my own server and performance is quite acceptable. ![]() Maybe this isn't useful when I'm submitting tickets to wandb, but I can see this being very helpful when I'm talking to my bank. Or politicians who want to track your period. Data companies that extract every bit of information they can. A hacker (who may be interested in your bank or health care). The risk isn't your service provider spying on you, it is anyone that you aren't intending to talk to. I mean, they use these two examples in the post. Is there really any information that you want open? Are you violating HIPPA and privacy laws just by talking? Your health is of no concern to anyone but you and your health provider. You're likely talking about specific sums of money. Is there really any information that you want open? They're going to ask you security questions to confirm your identity. What is the benefit of end to end encryption in this scenario?
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |