Matrix (protocol)

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

Lua error in package.lua at line 80: module 'strict' not found.

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

For other uses, see Matrix (disambiguation).
Matrix
Communications protocol
220px
Purpose Federated messaging and data synchronization
Developer(s) The Matrix.org Foundation
Introduced September 2014; 9 years ago (2014-09)[1]
Based on HTTP, WebRTC
OSI layer Application layer

Matrix is an open standard and lightweight protocol for real-time communication. It is designed to allow users with accounts at one communications service provider to communicate with users of a different service provider via online chat, voice over IP, and videotelephony. That is, it aims to make real-time communication work seamlessly between different service providers, just like standard Simple Mail Transfer Protocol email does now for store-and-forward email service.

From a technical perspective, it is an application layer communication protocol for federated real-time communication. It provides HTTP APIs and open source reference implementations for securely distributing and persisting messages in JSON format over an open federation of servers.[2][3] It can integrate with standard web services via WebRTC, facilitating browser-to-browser applications.

History

The initial project was created inside Amdocs, while building a chat tool called "Amdocs Unified Communications"[4], by Matthew Hodgson and Amandine Le Pape. Amdocs then funded most of the development work from 2014 to October 2017.[5]

Matrix was the winner of the Innovation award at WebRTC 2014 Conference & Expo,[6] and of the "Best in Show" award at WebRTC World in 2015.[7]

The protocol received praise mixed with some cautionary notes after it launched in 2014. Reviewers noted that other attempts at defining an open instant messaging or multimedia signalling protocol of this type had difficulties becoming widely adopted—e.g. XMPP and IRCv3—and have highlighted the challenges involved, both technological and political.[8] Some were unclear if there was enough demand among users for services which interoperate among providers.[9][10]

In 2015 a subsidiary of Amdocs was created, named "Vector Creations Limited", and the Matrix Staff was moved there.[11]

In July 2017 the funding by Amdocs was announced to be cut and in the following weeks the core team created their own UK-based company, "New Vector"[12], which was mainly built to support Matrix and Riot development.[13] During this time period, there were multiple calls for support to the community and companies that build on Matrix[14], to help pay for the wages of at least part of the core team. Patreon and Liberapay crowdfunding accounts were created[15], and the core team started a video podcast, called Matrix "Live" to keep the contributors up to speed with ongoing developments.[16] This was expanded by a weekly blog format, called "This Week in Matrix", where interested community members could read, or submit their own, Matrix-related news.[17]

The company was created with the goal of offering consultancy services for Matrix and paid hosting of Matrix servers (as a platform called modular.im) to generate income.[18][19]

In the early weeks after its creation, there the Matrix team and the company Purism published plans to collaborate in the creation of the Librem 5 phone.[20] The Librem 5 was intended to be a Matrix native phone, where the default pre-installed messaging and caller app should use Matrix for audio and video calls and instant messaging.[21]

In 2017, KDE announced it was working on including support for the protocol in its IRC client Konversation.[22]

In late January 2018 the company received an investment of US$ 5 million from status[23][24], an  Ethereum based startup.

In April 2018 the French Government announced plans to create their own instant messaging tool[25], which was later confirmed, by the Matrix team, to be based on Riot and Matrix.[26] New Vector is said to provide some support to the government in this endeavour.

In October 2018 a private company limited by guarantee called "the Matrix.org foundation"[27] was incorporated, to serve as a neutral legal entity for further development of the standard.[28]

In February 2019, the KDE community announced to adopt Matrix for its internal communications needs, as a decentralized alternative to other modern tools like Telegram, Slack, and Discord, and operate its own server instance.[29]

In April 2019, Matrix.org suffered a security breach in which the production servers were compromised.[30] This breach was not an issue with the Matrix protocol and did not directly affect homeservers other than matrix.org.

In June 2019, the Matrix protocol is out of beta with the version 1.0 across all APIs (and Synapse, at the time the reference homeserver), and the Matrix foundation is officially launched.[31][32]

Protocol

Matrix targets use cases like voice over IP, Internet of Things and instant messaging, including group communication, along with a longer-term goal to be a generic messaging and data synchronization system for the web. The protocol supports security and replication, maintaining full conversation history, with no single points of control or failure. Existing communication services can integrate with the Matrix ecosystem.[2]

Client software is available for open-federated Instant Messaging (IM), voice over IP (VoIP) and Internet of Things (IoT) communication.

The Matrix standard specifies RESTful HTTP APIs for securely transmitting and replicating JSON data between Matrix-capable clients, servers and services. Clients send data by PUTing it to a ‘room’ on their server, which then replicates the data over all the Matrix servers participating in this ‘room’. This data is signed using a git-style signature to mitigate tampering, and the federated traffic is encrypted with HTTPS and signed with each server’s private key to avoid spoofing. Replication follows eventual consistency semantics, allowing servers to function even if offline or after data-loss by re-synchronizing missing history from other participating servers.

The Olm library provides for optional end-to-end encryption on a room-by-room basis via a Double Ratchet Algorithm implementation.[1] It can ensure that conversation data at rest is only readable by the room participants. With it configured, data transmitted over Matrix is only visible as ciphertext to the Matrix servers, and can be decrypted only by authorized participants in the room. The Olm and Megolm (an expansion of Olm to better suit the need for bigger rooms) libraries have been subject of a cryptographic review by NCC Group, whose findings are publicly available[33], and have been addressed by the Matrix team.[34] The review was sponsored by the Open Technology Fund.

Bridges

Matrix does support bridging messages from different chat applications into Matrix rooms. These bridges are programs that run on the server and communicate with the non-Matrix servers. Bridges can either be acting as puppets or relays, where in the former the individual users account is visibly posting the messages, and in the latter a bot posts the messages for non puppeteered user accounts.

Currently there are official bridges for:

The following bridges are maintained by the community:

Clients

Riot is the reference implementation of a client. Fractal is the official client of the GNOME desktop. Many other clients, bots, bridges, servers and other implementations of the Matrix protocol also exist.[43]

See also

References

  1. ↑ 1.0 1.1 Lua error in package.lua at line 80: module 'strict' not found.
  2. ↑ 2.0 2.1 Lua error in package.lua at line 80: module 'strict' not found.
  3. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  4. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  5. ↑ Lua error in package.lua at line 80: module 'strict' not found.[self-published source]
  6. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  7. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  8. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  9. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  10. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  11. ↑ Lua error in package.lua at line 80: module 'strict' not found.[self-published source]
  12. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  13. ↑ Lua error in package.lua at line 80: module 'strict' not found.[self-published source]
  14. ↑ Lua error in package.lua at line 80: module 'strict' not found.[self-published source]
  15. ↑ Lua error in package.lua at line 80: module 'strict' not found.[self-published source]
  16. ↑ Lua error in package.lua at line 80: module 'strict' not found.[self-published source]
  17. ↑ Lua error in package.lua at line 80: module 'strict' not found.[self-published source]
  18. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  19. ↑ Lua error in package.lua at line 80: module 'strict' not found.[self-published source]
  20. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  21. ↑ Lua error in package.lua at line 80: module 'strict' not found.[self-published source]
  22. ↑ https://blogs.kde.org/2017/09/05/konversation-2x-2018-new-user-interface-matrix-support-mobile-version[self-published source]
  23. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  24. ↑ Lua error in package.lua at line 80: module 'strict' not found.[self-published source]
  25. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  26. ↑ Lua error in package.lua at line 80: module 'strict' not found.[self-published source]
  27. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  28. ↑ Lua error in package.lua at line 80: module 'strict' not found.[self-published source]
  29. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  30. ↑ Lua error in package.lua at line 80: module 'strict' not found.[self-published source]
  31. ↑ https://matrix.org/blog/2019/06/11/introducing-matrix-1-0-and-the-matrix-org-foundation/
  32. ↑ https://matrix.org/blog/2019/06/11/synapse-1-0-0-released/
  33. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  34. ↑ Lua error in package.lua at line 80: module 'strict' not found.[self-published source]
  35. ↑ Lua error in package.lua at line 80: module 'strict' not found.[self-published source]
  36. ↑ Lua error in package.lua at line 80: module 'strict' not found.[self-published source]
  37. ↑ Lua error in package.lua at line 80: module 'strict' not found.[self-published source]
  38. ↑ Lua error in package.lua at line 80: module 'strict' not found.[self-published source]
  39. ↑ Lua error in package.lua at line 80: module 'strict' not found.[self-published source]
  40. ↑ Lua error in package.lua at line 80: module 'strict' not found.[self-published source]
  41. ↑ Lua error in package.lua at line 80: module 'strict' not found.[self-published source]
  42. ↑ Lua error in package.lua at line 80: module 'strict' not found.[self-published source]
  43. ↑ Lua error in package.lua at line 80: module 'strict' not found.[self-published source]

External links

Retrieved from "https://infogalactic.com/w/index.php?title=Matrix_(protocol)&oldid=726007455"