Enter the matrix how to#

For example, at Cozењњloud, we have a Matrix room thatвЂ™s bridged to our public IRC channel, meaning that every message sent to the Matrix room will get in the IRC channel as well, and vice-versa. Matrix also distances itself from the вЂњyet another comms thingвЂќ argument with its philosophy: itвЂ™s not another standard for communications, but one that aims at binding all communications services together, using bridges, integration et al. Despite that, however, itвЂ™s currently mainly used for instant messaging, especially through the Riot client (which is also developed by New Vector). Some people are also experimenting with using Matrix for blogs, RSS reader, and other stuff thatвЂ™s quite far from what youвЂ™d expect to see with such a project. ItвЂ™s based on RESTful HTTP/JSON APIs, documented in open specifications, and is designed to be usable for anything that requires real-time-ish communications, from instant messaging to IoT. Matrix is a protocol for decentralised, federated and secure communications, created and maintained by New Vector, a company split between London, UK and Rennes, France (which I joined for an internship in London during the last summer). LetвЂ™s get things straight first, IвЂ™m talking about neither the science-fiction franchise, nor the nightclub in Berlin. Today I want to tell you about one of my favorite decentralised free software projects right now: Matrix.

Enter the matrix how to#

Doing so forces one to change their way of designing a system entirely, since most of the Internet now consists of centralised services, which leads people to only learn how to design and engineer these. I love free software because it matches the philosophy I want to live by, and decentralisation because it enlarges a userвЂ™s freedom and individuality, and I find working on decentralised systems fascinating.

As you might know if youвЂ™ve been following me on Twitter for some time (or if you know me in real life), IвЂ™m very fond of free software and decentralisation.