Live data from Hacker News

Matrix 2.0: The Future of Matrix

matrix.org

211–220 of 283 posts

Re: Matrix 2.0: The Future of Matrix

#213
post #141

exciting to hear! I only wish i had more time to contribute. Has there been any movement on migrating away from long polling (#475)? I didn't see anything about it in the announcements or comments despite such a big milestone

Low Bandwidth Matrix is the answer to that, and it’s currently on hold unless it gets funded: https://matrix.org/blog/2021/06/10/low-bandwidth-matrix-an-i... It might also get changed as part of Sliding Sync refinement.

Is there going to be a way to have very simple clients, perhaps with a helper in the server side?

It'd be nice to bring matrix to microcontrollers and "retro" computer platforms.

Re: Matrix 2.0: The Future of Matrix

#214
post #62

Rip matrix p2p. I wonder if they were serious about it, or if it was just vaporware (a la Musk) to get more funding. It has been announced years ago, they raised millions and they have big governments contracts. WTF is going on?

wtf is going on is that: a) p2p matrix works pretty well as a proof of concept - you can try it from https://arewep2pyet.com ; it’s not remotely vapourware. b) funding has been spent on core Matrix dev and making Element kick ass (cf Element X) c) an awful lot of very large Matrix + Element deployments (eg LuxChat in Luxembourg, Merkury 2.0 in the Polish MOD, many German local authorities) decide to run Matrix deploy…

>eg LuxChat in Luxembourg, Merkury 2.0 in the Polish MOD, many German local authorities

This is extremely sad. They're large tax-funded organizations and should definitely contribute to priorize the needs they definitely have.

Ironically, there might be voices pushing for a move to a proprietary solution they would actually have to pay to use, and have much less control over.

Re: Matrix 2.0: The Future of Matrix

#215
post #57

Techy friend group of mine migrated from Discord to a self-hosted private Matrix server a few months back. No complaints so far, although we didn't use Discord's voice/video/screen-sharing features (which I hear that Matrix intends to support eventually). UX-wise, it made me appreciate the distinction between Discord's "everyone is subscribed to every channel in a server by default" stance, and IRC/Matrix's opposite…

How did your friend convince your friend group to migrate over to Matrix? I’ve thought about setting up one but my group isn’t so much into the “do it yourself techies” or privacy conscious crowd.

Re: Matrix 2.0: The Future of Matrix

#216

Earlier quoted context omitted.

this is literally why we rewrote element-ios in rust, in the form of Element X iOS :) https://element.io/labs/element-x

Why not fix the issues with the current implementation as well as rewriting it?

time and money?

Re: Matrix 2.0: The Future of Matrix

#217

Earlier quoted context omitted.

Yup, it's true that sliding sync proxy increases disk space further, although it's not so bad. A big advantage once it's stable and merged into a native homeserver will be reducing the storage duplication between the proxy and the HS. Meanwhile, we really need to get https://github.com/matrix-org/rust-synapse-compress-state/pu... hooked up in Synapse so that it automatically compresses state; I don't know why this ne…

I just went through a HUGE pain in the ass with my homeserver. I was on the Hetzner cloud plan and at the highest storage tier already. I had about 80 GB free, and setup sliding sync. It filled up the remaining space (unbeknownst to me) and my homeserver stopped working. Fortunately I was still able to login, but no disk space was available for the Postgres vacuum. I wound up having to rsync everything over to my des…

Running out of disk space (or inodes!) is probably how everyone running a server learns about monitoring and alerts

Re: Matrix 2.0: The Future of Matrix

#218
post #69

Earlier quoted context omitted.

Hmm… we haven’t had notification problems like that in many years, from memory. Any idea if this was trying to deliver push notifs to Android without using Google? (Which historically has been painful thanks to Android OS versions terminating the app in the bg). Element X has totally rewritten notification code (given it’s moved from Kotlin to Rust) and should be much more robust for bugs like this. Sorry you got bit…

Communicating via Apple or Google is sadly required these days. How does that work with matrix? Does the protocol specify how to trigger those notifications? Do I need to register for a Google API key when setting up the server? I can't recall seeing anything about that in the configuration file.

>Communicating via Apple or Google is sadly required these days.

The copy of Signal installed on my GrapheneOS Pixel (with no Google anything installed) begs to differ; notifications have been both low-latency and rock-solid.

So it absolutely _can_ be done, and done well.

Re: Matrix 2.0: The Future of Matrix

#219
post #190

Earlier quoted context omitted.

Element X actually runs really well on macOS already on Apple Silicon; I regularly use it as my desktop app whenever Element Web is having... issues. It would be amazing to plonk matrix-rust-sdk into Element Web and switch Electron for Tauri or something... but one thing at a time.

I’ve wondered about this for a long time: Why not Flutter? Should give you one codebase for all platforms, while being significantly faster than webtech-based solutions.

I guess we just prefer to use the platform’s native UI (SwiftUI/UIKit, Jetpack Compose, HTML) on each respective platform, rather than an abstraction like Flutter. All the heavy lifting is done by matrix-rust-sdk now anyway.

Re: Matrix 2.0: The Future of Matrix

#220
post #213

Earlier quoted context omitted.

Low Bandwidth Matrix is the answer to that, and it’s currently on hold unless it gets funded: https://matrix.org/blog/2021/06/10/low-bandwidth-matrix-an-i... It might also get changed as part of Sliding Sync refinement.

Is there going to be a way to have very simple clients, perhaps with a helper in the server side? It'd be nice to bring matrix to microcontrollers and "retro" computer platforms.

the API already is super simple, and low bandwidth could already work on retro machines (I had 6809 in mind when experimenting with it). The problem is e2ee, but we have the Pantalaimon e2ee proxy to convert unencrypted Matrix traffic into E2EE traffic for precisely this sort of thing :)
Post reply on HN