I might have missed something, but the page is very simplistic and assumes you know what Matrix is and how to use this; a lot of time is spent on the installation through different means, but none how to use the server itself, either by use of a client?
I think conduit's page is doing the right thing. It doesn't really assume you know what matrix is, but rather assumes you're smart enough to click on a link if you don't know.
I agree with the grandparent -- while trying to determine what this was, I looked at other links to try and find the answer and went down the wrong path.
> Users from every Matrix homeserver can chat with users from all other Matrix servers.
This statement lead me to assumed the "matrix specification" discussed was about server-to-server communication... I'm not interested in digging into the underpinnings of this server-to-server communication (right now) just like I'm not terribly interested in how blockchains keep in sync across nodes... But I am interested in how this whole stack works, and I was lost with this page as the starting point.
So I think it's safe to add an extra sentence to explain the relationship while still keeping the page simplistic and focused.
Hard disagree. One of the worst landing pages I've ever seen. What exactly is it? Just a backend? Client? Don't waste my whole screen with the logo and a wannabe catchy phrase. Just tell me the gist
The landing page is pretty good if you are familiar with Matrix.org, and I'm assuming that it's aimed at Matrix developers. Personally I appreciated the brevity, simple declaration of the problem it's trying to solve, and a quick link to the real call to action (the Git repo).
EDIT: realizing that the landing page may have been updated with new content itself since your original post.
Matrix is an open network for secure and decentralized communication. Users from every Matrix homeserver can chat with users from all other Matrix servers. You can even use bridges to communicate with users outside of Matrix, like a community on Discord.
You're not understanding. The parent commenter said that the link was showing lots of installation options, but the link does not show that. I know there are installation instructions elsewhere, but I was just responding to what the parent was claiming about this link.
Matrix is a chat protocol. It works like chatting over GIT (distributed databases) and is more like a team messenger like Mattermost or Zulip. Conduit is a server software and not for end users.
And that is my point. While I use Matrix, it is confusing by itself as you need the client, which was hosted as riot.im, now element, etc. For a newcomer this page is just as confusing whle it could be a great entry as it being so lightweight compared to the actual Matrix server. Some additional notes will help a lot.
I also lost contact with a Matrix user during the riot.im -> element.io switch, so I empathize. But I think the flexibility and interoperability of Matrix is worth the additional complexity. Allowing different clients can be a major boon to accessibility, as blind or sight impaired users can use their own specialized client. Not to mention adapting to device form factor. Traditional workstation, tablet, phone all have different needs.
