this post was submitted on 08 Nov 2024
26 points (100.0% liked)

Decentralization

146 readers
1 users here now

All things and everything about decentralization: news, announcements, proposals, and discussions about decentralized apps, protocols and communities.

Rules

  1. Be polite and follow the rules of our instance lemmy.world.
  2. "Follow a general principle of robustness: be conservative in what you do, be liberal in what you accept from others."
  3. With respect to peer-to-peer and file-sharing technologies, refrain from posting illegal content (piracy) or links to it.
  4. With respect to cryptocurrencies, refrain from
    1. posting initial coin offerings (ICOs) and giveaways
    2. posting referral and promo links/codes

founded 2 months ago
MODERATORS
 

Since the outset of Matrix, our aim has always been to provide a protocol that lets you build open, decentralised, secure communication apps which outperform the mainstream centralised alternatives. It’s been a twisty journey - first focusing on making Matrix work at all (back in 2014), and then getting it out of beta with Matrix 1.0 in 2019, and now focusing on making Matrix fast, usable and mainstream-ready with Matrix 2.0.

top 3 comments
sorted by: hot top controversial new old
[–] [email protected] 3 points 1 week ago* (last edited 1 week ago) (1 children)

Sadly the new ElementX client is completely unusable missing 80% of the necessary features. The only real progress here (that would call for a 2.0 celebration) is the actually very nice new call system. That only works on element-desktop and elementx however. So no calls are possible with mobile users unless they use the very much not ready for use elementx.

I know this is about the protocol and not the clients, but in the end what matters to users are visible improvements to the UX.

From what i can see they dont seem to have any intentions of improving feature richness of elementx significantly but they are planning on discontinuing the non x version. Im a little confused with their messaging recently.

The protocol supports lots of cool features but if the mobile client will only support a small fraction of those, then whats the point?

[–] boramalper 3 points 1 week ago (1 children)

I fully agree with you and I’m not saying this in their defence but Element is not owned by Matrix either right? It’s owned by another (for-profit?) party and in fact Matrix (Foundation) doesn’t maintain any clients whatsoever.

I guess it has something to do with “client neutrality” and the protocol not being defined by / tied to a “reference implementation” which I can get behind, but it’s hurting users in the end as you said.

Hopefully things should get a whole lot more stable with Matrix 2.0 and which may incentivise people to put in more effort into writing better and more polished clients.

[–] [email protected] 2 points 1 week ago

Yeah im aware that they split up into two somewhat separate companies, but the big names are involved in both at the same time. Element is always mentioned in matrix.org posts too, so its very clear that its developed alongside each other. They are doing good work tho, so i dont want to complain too much.

My main complaint is just about the way they communicate things. Matrix 2.0 is not an actual thing. Its just another release in a long chain of incremental releases. ElementX is in bare bones alpha stage but they pretend its not.

I just dont like this weird self congratulation. It invalidates the very real progress of the ecosystem that doesnt need big numbers and drastical changes. It looks like investor theater to me, to make the matrix ecosystem look fashionable.