Live data from Hacker News

Self-hosting a Matrix server for 5 years

yaky.dev

21–30 of 159 posts

Re: Self-hosting a Matrix server for 5 years

#21
post #17

And I thought that XMPP felt broken...

XMPP felt great when compared to Matrix. Matrix was in a bad state some years ago when I hosted it for a while, and seems like it still is the same messy state. I avoid it as much as possible but for some reason there are communities using it. At this point it should just die so people would be motivated to replace it with something better.

People are motivated to replace it with something better, it's called Matrix 2.0.

Re: Self-hosting a Matrix server for 5 years

#23
post #18

Earlier quoted context omitted.

Yeah I thought this was a weird take too. Too often people take privacy for "I can do what I like". IMO deleting something you've sent to someone else is not a privacy concern at all.

I don't agree with it myself, but there are people who seem to want to frame "the right to be forgotten" as a privacy issue.

Even if it were a privacy issue, it would be impossible to enforce it technologically via FOSS software, because, by definition, the user at the other end could run a forked version with remote deletion disabled.

Re: Self-hosting a Matrix server for 5 years

#24

>this also creates a situation where anything said across federation cannot be unsaid, which is an ironic situation for a protocol/system that often comes up when talking about privacy. How is it ironic? No protocol in the world can force anyone to delete anything from their own device. Chat apps that implement this function are either proprietary (so you cannot control what they can do) or, if OSS, do it on a pinky-…

Yeah I thought this was a weird take too. Too often people take privacy for "I can do what I like". IMO deleting something you've sent to someone else is not a privacy concern at all.

IIRC it is possible to have some clever encryption so that the person you sent your message to can prove to their own satisfaction that it came from you, but they cannot prove to anyone else that it came from you. Which gives you plausible deniability; you can always claim that your contact forged the message.

Can't remember what the algorithm is called.

Re: Self-hosting a Matrix server for 5 years

#25

>this also creates a situation where anything said across federation cannot be unsaid, which is an ironic situation for a protocol/system that often comes up when talking about privacy. How is it ironic? No protocol in the world can force anyone to delete anything from their own device. Chat apps that implement this function are either proprietary (so you cannot control what they can do) or, if OSS, do it on a pinky-…

> No protocol in the world can force anyone to delete anything from their own device.

But they either do not sign the messages or allow repudiating the signatures. Matrix signs all events forever.

Matrix also makes the entire event history (minus message content depending on room configuration) available to servers on join, even if that server's users are not allowed to see it.

Re: Self-hosting a Matrix server for 5 years

#26
post #21
post #17

Earlier quoted context omitted.

XMPP felt great when compared to Matrix. Matrix was in a bad state some years ago when I hosted it for a while, and seems like it still is the same messy state. I avoid it as much as possible but for some reason there are communities using it. At this point it should just die so people would be motivated to replace it with something better.

People are motivated to replace it with something better, it's called Matrix 2.0.

Do they plan to fix the fundamental issues of Matrix in 2.0 or should I wait for 3.0?

Re: Self-hosting a Matrix server for 5 years

#27

>this also creates a situation where anything said across federation cannot be unsaid, which is an ironic situation for a protocol/system that often comes up when talking about privacy. How is it ironic? No protocol in the world can force anyone to delete anything from their own device. Chat apps that implement this function are either proprietary (so you cannot control what they can do) or, if OSS, do it on a pinky-…

A protocol can mandate forced deletion. A particular client implementation may ignore it, or some users may circumvent it, so it would be a weaker kind of feature, but still a feature. And depending on circumstances it can be quite useful.

Re: Self-hosting a Matrix server for 5 years

#28

>this also creates a situation where anything said across federation cannot be unsaid, which is an ironic situation for a protocol/system that often comes up when talking about privacy. How is it ironic? No protocol in the world can force anyone to delete anything from their own device. Chat apps that implement this function are either proprietary (so you cannot control what they can do) or, if OSS, do it on a pinky-…

> How is it ironic? No protocol in the world can force anyone to delete anything from their own device.

You may have noticed the constant pushing to remove the user's access to their "own" device.

Forcing people to delete things from their own device is the whole concept of the Snapchat protocol, for example. Snapchat fortunately doesn't offer an OS and can't meaningfully be part of this push, but they make a convenient illustration.

You can check out Snapchat's bug bounty policy here: https://hackerone.com/snapchat . On the list of ineligible vulnerabilities is "screenshot detection avoidance". That's not a bug (because there's nothing they can do about it), even though it is their product's selling point.

Sometimes stronger companies want similar things, and they try to do something about it.

Re: Self-hosting a Matrix server for 5 years

#29

>this also creates a situation where anything said across federation cannot be unsaid, which is an ironic situation for a protocol/system that often comes up when talking about privacy. How is it ironic? No protocol in the world can force anyone to delete anything from their own device. Chat apps that implement this function are either proprietary (so you cannot control what they can do) or, if OSS, do it on a pinky-…

A protocol can mandate forced deletion. A particular client implementation may ignore it, or some users may circumvent it, so it would be a weaker kind of feature, but still a feature. And depending on circumstances it can be quite useful.

A protocol can only support, never mandate. If I send you "DELETE MSG #4829" and you do nothing and reply with "200 OK; DELETE MSG #4829", nobody observing the protocol's messages will ever know what happened. Sure, an omniscent being could say "but he internally broke protocol, he didn't delete the message!", but by definition if something cannot be verified inside the protocol, it is outside of protocol.
Post reply on HN