Over the last few days we've had constant requests to respond to @moxie@twitter.com's 'The ecosystem is moving' blog post & recent 36c3 talk - we've tried to articulate Matrix's viewpoint over at matrix.org/blog/2020/01/02/on-.


It’s true that if you’re writing a messaging app optimised for privacy at any cost, Moxie’s approach is one way to do it. However, this ends up being a perversely closed world - a closed network, where unofficial clients are banned, with no platform to build on, no open standards, and you end up thoroughly putting all your eggs in one basket, trusting past, present & future Signal to retain its values, stay up and somehow dodge compromise & censorship… despite probably being the single highest value attack target on the ‘net.

This is exactly the issue I have with Signal, and of course the completely unacceptable policy of requiring a phone number as identification. Great response!

Keep up your great work!

@harald @matrix How can Marlinspike even call phone numbers "user-owned identifiers"?? If I want to port my phone number from one provider to another, I have to go buy a new SIM card, and then call both companies, and beg their customer service agents for permission to move. And if a bad actor clones my SIM, or just manages to convince a level-1 service rep that he's me, then he gets to steal my phone number forever.

Sign in to participate in the conversation

[Notice Regarding the Transfer of the mstdn.jp / mastodon.cloud Services] We have received several inquiries showing interest in a transfer following the announcement of the end of the mstdn.jp and mastodon.cloud services. As a result of subsequently evaluating the situation and making preparations, we have decided that the corresponding services will be transferred to a company in the United States on June 30. We will make an announcement regarding the name of the company that the services will be transferred to once preparations have been made. Thank you.