Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

XMPP vs. Matrix

news.ycombinator.com

Post reply on HN
Print view View original

91–92 of 92 posts

Re: XMPP vs. Matrix

#91

Post by tcfhgj »

xmpp-enjoyer wrote: post #89
Tmpod wrote: post #57

Earlier quoted context omitted.

Could you elaborate your points? I'm particularly interested in "Matrix isn't really decentralized" and on which XMPP client you're using on Linux. Thanks!

I'm not the parent, but I use both XMPP and Matrix, and have some thoughts to both of these. > Matrix isn't really decentralized I think most of the concerns stem from the majority of the development in the ecosystem being driven by a single company. This manifests in a few ways: matrix.org is by far the biggest server. Element is by far the most popular client. Both were (until recently) maintained by the same compa…

Care to explain what information is leaked via the matrix.to link and how it could be improved?

Re: XMPP vs. Matrix

#92

Post by Arathorn »

tcfhgj wrote: post #91
xmpp-enjoyer wrote: post #89

Earlier quoted context omitted.

I'm not the parent, but I use both XMPP and Matrix, and have some thoughts to both of these. > Matrix isn't really decentralized I think most of the concerns stem from the majority of the development in the ecosystem being driven by a single company. This manifests in a few ways: matrix.org is by far the biggest server. Element is by far the most popular client. Both were (until recently) maintained by the same compa…

Care to explain what information is leaked via the matrix.to link and how it could be improved?

using matrix.to means:

* the webserver hosting matrix.to can see your browser’s IP and user agent as it connects to it. (this could be improved by connecting to matrix.to via an overlay network of some kind, or simply using matrix URIs instead)

* it cannot see the room/user being linked to, as this is deliberately hidden in a url fragment from the server

* it cannot see details about the room/user being linked to (eg the icon or room name); it optionally lets the client chose to grab this from a given homeserver, but the service itself never sees this data.

In other words, it was written with privacy in mind.

Post reply on HN