News for hackers. Stuff that matters.
Re:Interoperability without sacrificing privacy: Matrix and ... by paxys on Friday March 25, 2022 @06:13PM (#30807512)
The biggest question mark in this entire DMA ruling is identity federation. If I am using a messaging app, and want to connect with someone who may be on any other service, is there going to be a reliable way to broker this initial exchange or will I have to specify an explicit (service, user identifier) pair, with each service managing their set of users on their own?
Re:Interoperability without sacrificing privacy: Matrix and ... by Arathorn on Friday March 25, 2022 @06:24PM (#30807582)
Yeah. this is the elephant in the corner of the room. One solution could be to use logically centralised but physically decentralised identity mapping servers (a bit like DNS root servers, or X.509 root CAs) - like the ones Matrix already runs: https://matrix.org/legal/identity-server-privacy-notice-1#2-... - but these end up being a massive toxic stash of personal data. On the other hand, it's not much worse than the current identity databases that Facebook etc maintain.

Another bet could be to let the owner of the identifier (your phone provider, in the instance of a phone number) track what service that identifier points to - like ENUM DNS. But that falls foul of political problems (and risks becoming centralised too).

Federated/decentralised identity is a problem we're actively working on at Matrix, and the DMA will only act to speed up the process, as it's indeed an important piece for this to work well in practice.

Re:Interoperability without sacrificing privacy: Matrix and ... by 3np on Saturday March 26, 2022 @08:58AM (#30811431)
> Federated/decentralised identity is a problem we're actively working on at Matrix

Is there a good place to follow this?

Re:Interoperability without sacrificing privacy: Matrix and ... by grishka on Saturday March 26, 2022 @02:46AM (#30809817)
No? Why? Identity is as non-issue as it gets. Of course you will have to specify a service and user identifier pair. Why on earth would anyone ever want it any other way?

Decentralized identities are messy. They only work in cryptobros' dreams. You can't rely on an average person to store a private key. In real life, account recovery is a hard requirement for an identity system, as is the ability to revoke access for someone who has broken into an account.

Re:Interoperability without sacrificing privacy: Matrix and ... by genewitch on Saturday March 26, 2022 @01:30AM (#30809490)
It's like an email address. I've used pidgin, trillion, meebo. I had to know what service a friend was on, generally they'd ask if I had whatever client they originally used to talk to people online with, and went from there.

I may have misread your intent, but honestly I don't see how "user directory" and "privacy" interoperate. What matrix does is maybe prove that you're talking to someone who has access to the same hardware, if not the same person, when you message the same user.

I don't shill for matrix, but I also try to use mastodon to have regular human conversations and I couldn't tell you what service everyone is on...

Re:Interoperability without sacrificing privacy: Matrix and ... by 2Gkashmiri on Saturday March 26, 2022 @07:15AM (#30810869)
imagine if we were discussing email today. "how can you know beforehand the email id exists and is owned by the intended person" ? then we would be forced to set up a "to contact with this person, click this link to confirm the secure channel" and other shenanigans