Live data from Hacker News

Notes on privacy and data collection of Matrix.org (2019)

gitlab.com

1–10 of 102 posts

Re: Notes on privacy and data collection of Matrix.org (2019)

#3
I'm of two minds when it comes to reports like this.

On the one hand, of course I love that people have the means to audit assumptions.

Both the ability to do so w.r.t the project being transparent and open, but also through time and technical ability.

I am, however, a little upset when people poke at minor issues (that they themselves see as minor) and speak at length about them. *not* because those issues should not be addressed, but because it gives ammunition for people who recommend closed platforms, or more opportunity for people to think of the community as being more divided than it really is.

The more uncertainty a thing is surrounded by: the more people are likely to just say "fuck it" and choose any option as long as it works, and guess what works? Closed platforms, especially those with coherent messaging like facebook or whatsapp.

So, with that in mind: Kudos for such an analysis, but be mindful that such a lengthy document that discusses minor issues can actually harm the matrix project.

Re: Notes on privacy and data collection of Matrix.org (2019)

#6
(Aug 2019)

A lot has happened in and around Matrix since. While this looks like an honest and thorough review, as it’s focusing on defaults and UX/expectations, I’m assuming several things to be outdated. Maybe some of the critique brought up here has even resulted in changes in docs, Element and Synapse already.

Haven’t yet read thoroughly enough to say what, will probably follow up here later.

Note that mxisd (the “only other identity server” referenced), from the paper authors, is now deprecated and part of their “Grid Server”. A community-maintained fork lives on as ma1sd. AFAIK this is the one identity server software to consider for self-hosters.

Also for those new to Matrix, “Riot” referenced is now rebranded as “Element Messenger”.

Re: Notes on privacy and data collection of Matrix.org (2019)

#7

And meanwhile people keep on ignoring Tox when not sh*ting on it.

I've never heard of Tox, but it doesn't even have an iOS client. That's a good reason to ignore it.

Is that like ignoring something because it doesn't have an AOL keyword?

Re: Notes on privacy and data collection of Matrix.org (2019)

#8
post #3

I'm of two minds when it comes to reports like this. On the one hand, of course I love that people have the means to audit assumptions. Both the ability to do so w.r.t the project being transparent and open, but also through time and technical ability. I am, however, a little upset when people poke at minor issues (that they themselves see as minor) and speak at length about them. *not* because those issues should no…

I know it is going to sound like an ad-hominem, but once I realized that this is from the same person behind the "Grid protocol", I immediately closed the tab. This guy seems to be on a quixotic vendetta against msxid. It is the third or fourth persona (first it was from a personal account, then from his company, now he has even a non-profit advocating for privacy) that he created to re-hash the same old, outdated and irrelevant argument.

And the pathetic thing is, if he had spent more time working on his "Grid protocol" instead of pointless nitpicking, maybe he would have a lot more credibility on the matter.

Re: Notes on privacy and data collection of Matrix.org (2019)

#9

And meanwhile people keep on ignoring Tox when not sh*ting on it.

I've never heard of Tox, but it doesn't even have an iOS client. That's a good reason to ignore it.

That's such a silly statement when you're a slave to Apple, which is closed source.

You could be using an open source, non-googled, android OS with an open source Tox or Briar client.

Post reply on HN