element.io
Element is a sovereign, secure and interoperable communications platform. Built by the creators of Matrix.
84 posts
594 followers
67 following
Regular Contributor
Active Commenter
comment in response to
post
mebbe…
comment in response to
post
not a ground up rewrite, but enhancing what’s there to speak Matrix 2.0 and then eventually swapping to matrix-rust-sdk is the plan.
comment in response to
post
it uses it optionally for auth and voip, but not sliding sync (although that’s under dev). web/desktop is still behind element x. and we miss spaces too there.
comment in response to
post
It's part of the Matrix spec - it's just normal Matrix emoji m.reaction events :) Pretty much everything Element does is proposed for the Matrix spec rather than being Element specific. youtu.be/X8yAwFq9nAU?... for more
comment in response to
post
opendesk.eu is making good progress towards a viable alternative.
comment in response to
post
okay then; chatgpt.com/share/67b19c.... the apt details are on element.io/download; flatpak is a 3rd party not done by us.
comment in response to
post
best bet would be to come to matrix.to/#/#element-web:matrix.org and we can try to figure out how it was installed. could it be as a debian package or a flatpak?
comment in response to
post
hm, sorry :/ investigating to see what happened…
comment in response to
post
github.com/element-hq/e... is hopefully a useful starting point, but thanks for sharing the flow - will make sure users don't get stuck in an unusable site.
comment in response to
post
📱Download Element X from your app store!
iOS: apps.apple.com/gb/app/eleme...
Android: play.google.com/store/apps/d...
comment in response to
post
okay. the legacy apps have barely been touched in >18 months; all our effort has been on Element X. That said, both encryption problems and thread problems should still be stable. If you can dump details of what went wrong to github.com/element-hq it would be much appreciated so we can check.
comment in response to
post
you are indeed late to the game - both unable to decrypt msgs and stuck notifs should be fixed as of a year or so ago. are you stuck using old apps or old server?
comment in response to
post
hm. which are you thinking of? stuff like custom emoji should not be rejected but stuck in a “we will get to this as soon as we can” queue.
comment in response to
post
we haven’t shut them down, but we haven’t been able to prioritise them either.
comment in response to
post
Synapse: fosdem.org/2025/schedul...
Rust SDKs: fosdem.org/2025/schedul...
Round Table Government Collaboration:
fosdem.org/2025/schedul... [3/3]
comment in response to
post
The Road to Mainstream Matrix: fosdem.org/2025/schedul...
Matrix State of the Union: fosdem.org/2025/schedul...
MatrixRTC: fosdem.org/2025/schedul...
Federation: fosdem.org/2025/schedul... [2/3]
comment in response to
post
how many people work on the nuxt core team, and how are they funded, btw? wonder if it makes sense to differentiate massively successful projects (WP, mongo, elastic) who are simply trying to maximise profits from smaller ones who are trying to get sustainable & breakeven?
comment in response to
post
historically UX absolutely did suck. these days we really did fix it in Element X, though: element.io/blog/element.... and fwiw we’d love to figure out how to blend matrix with atproto.
comment in response to
post
unfortunately justifying budget for something you can use for free is tough, unless there is actually an explicit policy to pay for the vendor’s supported offering. ZenDiS are the only govt folks we know who have that policy.
comment in response to
post
Agreed! Which is why Matrix is *not* controlled by Element or any other company. Just because one scalable implementation happens to be proprietary doesn’t kill the whole protocol - if anything it should encourage others to build scalable servers too.
comment in response to
post
www.heise.de/news/Problem... is a concrete example of this, but is one of *many*. Hence drastic measures to give SIs reason to route $ to Element that we can then spend on improving FOSS.
comment in response to
post
The problem is that nation-state funding is not remotely carrying @matrix.org, nor Element. Govts and other big orgs put out tenders for Matrix deployments; System Integrators turn up with FOSS Synapse, take the $ and say they’ll support it, and then don’t route any $ upstream (even with AGPL).
comment in response to
post
BwMessenger does contribute to FOSS dev costs. BuM deployments do not, however.
comment in response to
post
None of the money from BuM deployments like www.t-systems.com/de/en/succes... currently goes to us as the upstream project, hence trying to give a concrete way for folks like DT to work with us (and so fund all the FOSS work too).
comment in response to
post
The anger makes sense here, but please try to understand the situation: Element needs sufficient $ to pay devs to work on Matrix. Many govt deployments do not route $ to us - instead they pay an integrator who then doesn't fund upstream: www.heise.de/news/Problem.... This is us trying to fight that.
comment in response to
post
if we make it available to the community, the large deployments will use it for free without routing any $ to us for development - mastodon.matrix.org/@sunweaver@f... has more details.