Difference between revisions of "Matrix"

From Technologia Incognita
Jump to: navigation, search
(Add link to Matrix space)
Line 1: Line 1:
Join the TechInc Matrix space at [https://matrix.to/#/#chat:techinc.nl #chat:techinc.nl].
+
= How to join =
 +
You can join the TechInc Matrix space at [https://matrix.to/#/#chat:techinc.nl #chat:techinc.nl] using a Matrix [https://matrix.org/ecosystem/clients/ client of choice].
  
 
= Motivation =
 
= Motivation =
  
The TechInc community is using a bunch of different protocols and platforms to communicate with each other, such as IRC, Telegram, Discord, Signal, email, etc. Unfortunately, this leads to fragmentation, as not everybody is able to participate in the conversations that people are having within the community. It would be nice if people can to talk to each other, but without them being peer pressured onto platforms that they don't want to use.
+
The TechInc community is using a bunch of different protocols and platforms to communicate with each other, such as IRC, Telegram, Discord, Signal, email, etc. Unfortunately, this leads to fragmentation, as not everybody is able to participate in the conversations that people are having within the community. It would be nice if people can to talk to each other, but without them being peer pressured onto platforms and/or clients that they don't want to use.
  
 
[[File:Chat systems.png|upright=1.0|https://xkcd.com/1810/|alt=I'm one of the few Instagram users who connects solely through the Unix 'talk' gateway. ]]
 
[[File:Chat systems.png|upright=1.0|https://xkcd.com/1810/|alt=I'm one of the few Instagram users who connects solely through the Unix 'talk' gateway. ]]
Line 16: Line 17:
  
 
= Bridging communication silos with Matrix =
 
= Bridging communication silos with Matrix =
We would like to setup a Matrix instance. This will be hosted on space infrastructure.
+
We have setup a Matrix instance in such a way that it is bridged to the both the TechInc IRC channel, and the TechInc Telegram group.
There are several ways that we can setup a Matrix instance and the various bridges, each having their own upsides and downsides. Before deciding on what works best, we need a common understanding of the different options. The methods described below are just there to illustrate some of the different options. The exact details, such as the channel names, what platforms to bridge, and everything else, are of course open for discussion.
+
Messages sent on IRC or Telegram are visible in the Matrix channels as well.
  
== Method 1: Full bridging ==
+
Currently, the Matrix is bridged to the other communication silos like this
With full bridging, all channels are bridged to all other channels on all other platforms.
 
  
 
{| class="wikitable"
 
{| class="wikitable"
 
|-
 
|-
! Channel !! Matrix !! IRC !! Telegram
+
! Channel !! Matrix !! IRC !! Telegram topic
|-
 
| General || #general:techinc.nl || #techinc-general || #⃣ General
 
|-
 
| Updates || #updates:techinc.nl || #techinc-updates || ❗ Updates
 
|-
 
| Printing || #printing:techinc.nl || #techinc-printing || 🖨 Print Team
 
|-
 
| Electronics || #electronics:techinc.nl || #techinc-electronics || ⚡ Electronics
 
|-
 
| Networking || #networking:techinc.nl || #techinc-networking || 💻 Network Team
 
|-
 
| Food ordering ||  #foodordering:techinc.nl || #techinc-foodordering  || 🍕 Food Ordering
 
|}
 
 
 
=== Advantages ===
 
* Everybody can talk to everybody, regardless of the platform, client or protocol that they prefer to use. A message sent in a channel on one platform will be relayed to the corresponding channel on every other platform.
 
 
 
=== Disadvantages ===
 
* There is no opt-out. Sending a message in a bridged channel will broadcast it to every other platform.
 
* There might be a mismatch between the norms that each platform is currently accustomed to, and the norms that other platforms expect
 
 
 
== Method 2: Partial bridging ==
 
Everything is bridged to the TechInc-hosted Matrix instance, but the Matrix instance does not necessarily bridge other platforms together.
 
 
 
{| class="wikitable"
 
|-
 
! Channel !! Matrix !! IRC !! Telegram
 
 
|-
 
|-
 
| IRC || #irc:techinc.nl || #techinc ||
 
| IRC || #irc:techinc.nl || #techinc ||
 
|-
 
|-
| General || #general:techinc.nl || ||
+
| General || #general:techinc.nl || || #⃣ General
 
|-
 
|-
 
| Updates || #updates:techinc.nl || || ❗ Updates  
 
| Updates || #updates:techinc.nl || || ❗ Updates  
 
|-
 
|-
| Printing || #printing:techinc.nl || #techinc-printing || 🖨 Print Team  
+
| Print Team || #print-team:techinc.nl || || 🖨 Print Team  
 
|-
 
|-
| Electronics || #electronics:techinc.nl || #techinc-electronics ||  
+
| Electronics || #electronics:techinc.nl || || ⚡ Electronics
 
|-
 
|-
| Networking || #networking:techinc.nl || #techinc-networking || 💻 Network Team
+
| Network Team || #network-team:techinc.nl || || 💻 Network Team
 
|-
 
|-
| Food ordering || #foodordering:techinc.nl || ||  
+
| Music || #music:techinc.nl || || 🎵 Music
|}
 
 
 
=== Advantages ===
 
* Everything is bridged to the TechInc Matrix instance, so everybody can get access to all channels through the TechInc Matrix instance.
 
* Only certain channels are bridged to other platforms besides Matrix.
 
 
 
=== Disadvantages ===
 
* Might be difficult to distinguish a channel that is bridged to both Matrix and other platforms, from a channel that is just bridged to Matrix.
 
 
 
== Method 3: Single-channel bridge ==
 
{| class="wikitable"
 
 
|-
 
|-
! Channel !! Matrix !! IRC !! Telegram
+
| Laser Team || #laser-team:techinc.nl ||  || 💡 Laser Team
 
|-
 
|-
| Bridged || #bridged:techinc.nl || #techinc-bridged || 🌉 Bridged
+
| Food ordering || #food-ordering:techinc.nl || || 🍕 Food ordering
 
|}
 
|}
  
=== Advantages ===
+
= Privacy =
* Very explicit in showing that it is a bridged channel.
+
The bridge exposes the following details to the bridged instances:
 
 
=== Disadvantages ===
 
* People can only join conversations that happen in the bridged channel. Any conversation that happens in a different, non-bridged, channel is not accessible through Matrix.
 
* Unlikely that people will actually use this channel, which sort of defeats the purpose.
 
 
 
= What information is being sent over a bridge? =
 
Depending on the platform, a bridge sends the following information to the Matrix instance:
 
 
* Your nickname
 
* Your nickname
 
* The content of the messages that were sent
 
* The content of the messages that were sent
 
* When messages where sent
 
* When messages where sent
* Join/leave notifications, if available
+
 
* Typing notifications, if available
+
= Infrastructure =
 +
The Matrix server is hosted on TechInc infrastructure at [http://matrix.ti:8008/_matrix/static/ matrix.ti].

Revision as of 21:00, 20 November 2024

How to join

You can join the TechInc Matrix space at #chat:techinc.nl using a Matrix client of choice.

Motivation

The TechInc community is using a bunch of different protocols and platforms to communicate with each other, such as IRC, Telegram, Discord, Signal, email, etc. Unfortunately, this leads to fragmentation, as not everybody is able to participate in the conversations that people are having within the community. It would be nice if people can to talk to each other, but without them being peer pressured onto platforms and/or clients that they don't want to use.

I'm one of the few Instagram users who connects solely through the Unix 'talk' gateway.

This is one of the things that Matrix hopes to address

Matrix defines a set of open APIs for decentralised communication, suitable for securely publishing, persisting and subscribing to data over a global open federation of servers with no single point of control. Uses include Instant Messaging (IM), Voice over IP (VoIP) signalling, Internet of Things (IoT) communication, and bridging together existing communication silos - providing the basis of a new open real-time communication ecosystem.

With Matrix, it is possible for a Telegram user to talk to a user on Discord, and from a Signal user to talk to a user on IRC, all using Matrix as the underlying communication protocol.

Bridging communication silos with Matrix

We have setup a Matrix instance in such a way that it is bridged to the both the TechInc IRC channel, and the TechInc Telegram group. Messages sent on IRC or Telegram are visible in the Matrix channels as well.

Currently, the Matrix is bridged to the other communication silos like this

Channel Matrix IRC Telegram topic
IRC #irc:techinc.nl #techinc
General #general:techinc.nl #⃣ General
Updates #updates:techinc.nl ❗ Updates
Print Team #print-team:techinc.nl 🖨 Print Team
Electronics #electronics:techinc.nl ⚡ Electronics
Network Team #network-team:techinc.nl 💻 Network Team
Music #music:techinc.nl 🎵 Music
Laser Team #laser-team:techinc.nl 💡 Laser Team
Food ordering #food-ordering:techinc.nl 🍕 Food ordering

Privacy

The bridge exposes the following details to the bridged instances:

  • Your nickname
  • The content of the messages that were sent
  • When messages where sent

Infrastructure

The Matrix server is hosted on TechInc infrastructure at matrix.ti.