This is an amazing step in the right direction. I host a small conduit server for a friend group and I can't wait for the improvements this will bring as a whole!
Good work.
Matrix 2.0: The Future of Matrix
121–130 of 283 posts
Re: Matrix 2.0: The Future of Matrix
#122Oh wow congrats to the entire team for this amazing achievement!
And the cake under the cherry is… Element X is open-source as well[1][2]!
I really can't wait for Beeper[3] to rebuild their fork on top of Element X (it's currently based on Element, formerly called Riot). When this happens it will be an absolute game-changer for the messaging ecosystem.
————
[1] https://github.com/vector-im/element-x-ios
Re: Matrix 2.0: The Future of Matrix
#123Earlier quoted context omitted.
Element X also is geared up for powerusers (e.g. as project lead, I consider myself a poweruser) and i've been absolutely loving it as my daily driver for the last few months on mobile. For instance, my account is in around 4,000 chatrooms, and Element iOS was taking ~10s to launch and sync, and could easily take minutes to sync in the morning (heaven forbid the app was offline for more than overnight). Meanwhile, El…
Ok, I understand... one last thing I ask every year - custom emojis when? :) And thank you for your the hard work!
But we just entirely rewrote both mobile clients to get out of having to implement custom emojis! :D Joking aside, it's easily one of the biggest features missing from Element/Element X, and I for one can't wait for it to land. Unfortunately we also don't have any paying Element customers asking for it, though, which is why it keeps getting deprioritised in favour of other stuff.
Re: Matrix 2.0: The Future of Matrix
#124Synapse already eats up lots of space, adding sliding sync will boost it up and will be difficult to self-host it.
Re: Matrix 2.0: The Future of Matrix
#125Matrix is great but when is the tech industry going to deal with the fact that many, if not all, bridges are against the respective services' ToS and subsequently put the developers of those bridges under legal risk? Whatsapp has already sent legal threats to multiple bridge-component level project maintainers without any recourse.
The EU just designated Whatsapp as a gatekeeper under the Digital Markets Act: https://ec.europa.eu/commission/presscorner/detail/en/ip_23_... following the "full list of do's and don'ts" link on that page: > Gatekeeper platforms will have to: > - allow third parties to inter-operate with the gatekeeper’s own services in certain specific situations > - allow their business users to access the data that they generate…
I'm aware of DMAs regs but it forces Whatsapp within 6 months to start enabling interoperability. However it doesn't provide protection for these existing bridge projects.
open-wa, Baileys, invidious devs are all in the dark as to whether or not they're Scott free from their respective C&Ds due to this legislation.
Re: Matrix 2.0: The Future of Matrix
#126Once more, Kudos to Arathorn/Matthew (the head of Matrix/Element) taking the time to answer most Hacker News comments, as he mostly does for all Matrix-related HN threads. It's really nice to see him answer in a calm and mostly objective tone while people are blaming him for shortcomings and problems of all the different Matrix-related software projects. Admitting to failures and problems that Matrix definitely has,…
thanks :) sorry for monopolising the thread, but it's too tempting when I have the answers to hand, for better or worse...
Re: Matrix 2.0: The Future of Matrix
#127Synapse already eats up lots of space, adding sliding sync will boost it up and will be difficult to self-host it.
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 never landed when it was written in in 2021 :(
Re: Matrix 2.0: The Future of Matrix
#128Oh wow congrats to the entire team for this amazing achievement! And the cake under the cherry is… Element X is open-source as well[1][2]! I really can't wait for Beeper[3] to rebuild their fork on top of Element X (it's currently based on Element, formerly called Riot). When this happens it will be an absolute game-changer for the messaging ecosystem. ———— [1] https://github.com/vector-im/element-x-ios [2] https://g…
Beeper don't seem to like Sliding Sync, for whatever reason, so I wouldn't hold your breath on it ;)
Re: Matrix 2.0: The Future of Matrix
#129There's no web version of element X though? It's what I use most of the time. I'll try the Android app anyway, I've been having a really annoying bug with the normal one anyway that hasn't been fixed for a year. So perhaps X doesn't have it.
Re: Matrix 2.0: The Future of Matrix
#130Earlier quoted context omitted.
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.
https://thomask.sdf.org/blog/2016/12/11/riots-magical-push-n... is a great blog (back when Element was called Riot) explaining how it works :)
The gist of it seems to be that Synapse/Dendrite calls home to the Matrix Company, which in turn pays Google to send a notification. That's awfully nice of them, but does not really leave any room for success. I take it larger clients with security requirements roll their own clients, and this is part of the business case?