100% done by contributors
Massive help from
Easy way to know how much of the conversation you have missed.
Easy way to find messages that you have been mentioned
Also known as Rocket.Cat
Stars on GitHub
There have been several attempts including SIP, XMP, RCS.
All of these have had some level of success, but many different technological, usability, economic factors have ended up limiting their success.
Unfortunately, we've not ended up in a world where everyone has a SIP URI or Jabber ID on their business card or a phone that actually uses RCS.
XMPP is more of a message passing protocol
We got to HTTP version 1.1 in 1997, and have been stuck there until now. Likewise, SMTP, IRC, DNS, XMPP, are all similarly frozen in time circa the late 1990s.
Once you federate your protocol, it becomes very difficult to make changes
It’s what Slack did with IRC, what Facebook did with email, and what WhatsApp has done with XMPP.
In each case, the federated service is stuck in time, while the centralized service is able to iterate into the modern world and beyond.
Here come the Matrix.org
End-to-End encryption, with no decryption or reading performed on the server.
Matrix user IDs (MXID) are unique user IDs.
Third-party IDs (3PIDs)
IDs from other systems or contexts, such as email addresses, social network accounts and phone numbers.
The whole area of XMPP vs Matrix vs Rocket.Chat is quite subjective. Rather than fighting over which open interoperable communication standard works the best, we should just collaborate and bridge everything together.
The more federation and interoperability the better.
So let's be friends
A Service record (SRV record) is a specification of data in the Domain Name System defining the location, i.e. the hostname and port number, of servers for specified services.
# _service._proto.name. TTL class SRV priority weight port target. _chat._tcp.example.com. 86400 IN SRV 10 60 3000 chat.example.com. _chat._tcp.example.com. 86400 IN SRV 10 20 3000 chat1.example.com.
more details at