31–40 of 217 posts
Ok, now do XMPP. Or Signal, but with the added requirement that you want to run your own server.
Earlier quoted context omitted.
The fact that the official Matrix Mastodon account as well as the "Matrix Director of Program Development" agree with his assessment with the Mastodon account agreeing that it is a "trashfire" makes me sceptical of your suggestion that he was manufacturing these issues.
I mean, Element and Matrix are 2 separate entities, which is kind of the key problem with all these efforts - there have been plenty of posts about how hard it was to join a Mastodon instance, or creating 2 accounts etc. That said, the Element/Element X migration is a mess. But if he'd just gone to the Element website and clicked "get started", it would have just worked.
> my recommendation is to avoid Matrix for at least two years
which seems arbitrary. Why wait 2 years and not one or just a couple months? The french administration is already using it now https://www.tchap.gouv.fr/
In federated protocols it's always harder for the user to choose an instance for them. Not sure if the responsibility for that should be on the protocol managing party.
Earlier quoted context omitted.
The fact that the official Matrix Mastodon account as well as the "Matrix Director of Program Development" agree with his assessment with the Mastodon account agreeing that it is a "trashfire" makes me sceptical of your suggestion that he was manufacturing these issues.
I mean, Element and Matrix are 2 separate entities, which is kind of the key problem with all these efforts - there have been plenty of posts about how hard it was to join a Mastodon instance, or creating 2 accounts etc. That said, the Element/Element X migration is a mess. But if he'd just gone to the Element website and clicked "get started", it would have just worked.
No it wouldn't.
element.io -> get started gives this:
> Get started.
> Setup a self-hosted or cloud deployment, with powerful enterprise capabilities.
edit - expanding.
The element site is entirely about getting something for your business. It has a pricing page that tells me it'll be free for up to 200 users but I have to self host. Nothing on the front page of it tells me it's a free app I can use elsewhere. I have to go to "product" (!) and choose the app.
Developers could also do these processes. And they probably do, often. But they usually have their heads so far up their asses that they don't see how inscrutable this onboarding process is even for very technical users. It's like when you use one of those Linux phones and your reaction all along is "ew". Do developers not notice how bad this is? No, they don't. Some of them haven't used a good UI ever. They can't fa…
I gotta say, he nails it. I so wanted to love Matrix. I tried it for a year and it just had too many sharp edges.
I was on IRC when ircII and BitchX were common clients along with huge scripts on both for "irc wars" and shit. I can deal with jank. But the Matrix UI/UX still grates me on how bad it is. Just stop pretending, copy what Discord does and be done with it.
Earlier quoted context omitted.
I mean, Element and Matrix are 2 separate entities, which is kind of the key problem with all these efforts - there have been plenty of posts about how hard it was to join a Mastodon instance, or creating 2 accounts etc. That said, the Element/Element X migration is a mess. But if he'd just gone to the Element website and clicked "get started", it would have just worked.
> But if he'd just gone to the Element website and clicked "get started", it would have just worked. No it wouldn't. element.io -> get started gives this: > Get started. > Setup a self-hosted or cloud deployment, with powerful enterprise capabilities. edit - expanding. The element site is entirely about getting something for your business. It has a pricing page that tells me it'll be free for up to 200 users but I ha…
Earlier quoted context omitted.
The fact that the official Matrix Mastodon account as well as the "Matrix Director of Program Development" agree with his assessment with the Mastodon account agreeing that it is a "trashfire" makes me sceptical of your suggestion that he was manufacturing these issues.
I mean, Element and Matrix are 2 separate entities, which is kind of the key problem with all these efforts - there have been plenty of posts about how hard it was to join a Mastodon instance, or creating 2 accounts etc. That said, the Element/Element X migration is a mess. But if he'd just gone to the Element website and clicked "get started", it would have just worked.
Going to element.io and clicking "get started" takes you to a form to submit some kind of enterprise inquiry, asking what the name and size of your company is...
Ok, now do XMPP. Or Signal, but with the added requirement that you want to run your own server.
Neither seems to provide any sort of conceptual framework to allow the user to react in a reasonable way when something goes wrong with the identity stuff...
OMEMO running over XMPP is pretty terrible for identity stuff, at least for the clients I have encountered.
Earlier quoted context omitted.
I mean, Element and Matrix are 2 separate entities, which is kind of the key problem with all these efforts - there have been plenty of posts about how hard it was to join a Mastodon instance, or creating 2 accounts etc. That said, the Element/Element X migration is a mess. But if he'd just gone to the Element website and clicked "get started", it would have just worked.
agree, the author mainly complained about UX issues in the client, but then only tried one client it seems. Article should have been titled "The Element Trashfire" > my recommendation is to avoid Matrix for at least two years which seems arbitrary. Why wait 2 years and not one or just a couple months? The french administration is already using it now https://www.tchap.gouv.fr/ In federated protocols it's always harde…