Technology

37708 readers

347 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago

MODERATORS

[email protected]

250

Matrix 2.0: The Future of Matrix (matrix.org)

submitted 1 year ago by [email protected] to c/[email protected]

94 comments fedilink hide all child comments

Highlights include Sliding Sync (instant login/launch/sync), Native OIDC (industry-standard authentication), Native Group VoIP (end-to-end encrypted large-scale voice & video conferencing) and Faster Joins (lazy-loading room state when your server joins a room).

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago) (1 children)

Is their shift key broken?

Furthermore, this blog post has outdated information and many of their problems with Matrix are fundamental for federated protocols. Good luck removing an email sent to another server, for example. JSON form is very well defined.

I can agree with the problem of DAG complexity building up, sure, but that is a tradeoff.

[–] [email protected] 1 points 1 year ago

Is their shift key broken?

Could be the result of repetitive strain injury, I'm not judging

Furthermore, this blog post has outdated information and many of their problems with Matrix are fundamental for federated protocols. Good luck removing an email sent to another server, for example.

Yup, I don't think that's the main argument, more a warning like "well if you normal folks were expecting anything else, that's how it is and can't be changed"

JSON form is very well defined.

Though that's flawed/incomplete, and an essential reason for incompatibility between implementations

I can agree with the problem of DAG complexity building up, sure, but that is a tradeoff.

That's my main issue, really. Basically, there's no end in sight to the problem of inconsistent messages that can take minutes/hours/days to be delivered: Matrix just isn't dependable for instant communications, by design. This rules it out of a ton of very significant and practical real world use cases and expectations. That's not a system you can think typical modern users (used to their messages being either delivered instantly or not at all) to trust and to like once faced with these issues, not just once, but repeatedly. It is us, the world, being told again "Blockchain will solve all problems of centralization", with a crowd of enthusiasts blinded by the hype embarking (taking hostage) their less savvy peers while the people being the steering wheel have no idea how to bring the car home. And worse, those people behind the steering wheel being in denial (or malicious, or incompetent), will keep telling you to just trust them, and that the problem is solved already while the evidence points in the other direction.