#199 Create a native matrix fedora-telegram bridged room for matrix users
Closed: stale a month ago by jflory7. Opened 5 years ago by akarshanbiswas.

The room will be bridged to telegram. It will enable existing matrix users to access and interact with the members of the Fedora telegram group.

Things todo:

  • Create a room in matrix [done] [matrix id: #fedoramatrix:matrix.org]
  • Host a matrix <--> telegram bridge [todo]
  • Add the bridge bot to the fedora-telegram group to get the chat id[todo].
  • Add the bridge bot to fedora matrix to feed it with the chat id to initiate the bridge[todo].

The bot on telegram should have access to messages since it can detect when a message is been deleted and sync it with the matrix room(In case of spam).

Future: Maybe add matrix<-----> discord bridge? {later}


Why is a native room better than using the in-built Freenode connection in Matrix?

@bex To use the in built Freenode connection in Matrix, one need to register to Freenode otherwise appservice-irc bot will kick the user out at the point of joining. Not everyone wants to register to freenode.
Secondly it is not possible to follow the discussion using the current implementation in matrix. Matrix has various features that are absent in IRC. So spam when deleted from #fedora-telegram channel stays forever in the matrix room(which is bridged to #fedora-telegram IRC channel) as well. Matrix allows message redact/deletion. Also mentioning/replying users is a bit difficult.

@akarshanbiswas I understand. However, your proposal seems to want to split the conversation into two spaces. One is #fedora-commops + Telegram Channel (a) and the other is now Matrix + Telegram Channel (b). We should, imho, have one space.

I understand your desire to see spam cleaned up. This should be the job of the Matrix admin, just as it is the job of the Telegram admin and the IRC admin.

@akarshanbiswas I think this is the best place for this conversation. I am sharing my opinion, one of several in commops. I look forward to hearing others.

@bex Ah sorry I misunderstood.

I understand your desire to see spam cleaned up. This should be the job of the Matrix admin, just as it is the job of the Telegram admin and the IRC admin.

There are no matrix fedora-telegram rooms. Only IRC channel #fedora-telegram. I am actually asking for a matrix room too. Also messages in IRC can't be deleted.

I'm concerned that we're going to split the conversation. Will the IRC<->Telegram bridge continue to exist? With the Telegram<->Matrix bridge, will we have a IRC<->Matrix bridge by virtue of Telegram?

The Fedora Council has expressed that teams can use the communication mechanisms that work best for them, so long as they follow the rules around Code of Conduct, trademark guidelines, etc. Given that, I'd rather see one chat platform used by CommOps and not worry about bridges at all.

@bcotton

I'm concerned that we're going to split the conversation. Will the IRC<->Telegram bridge continue to exist? With the Telegram<->Matrix bridge, will we have a IRC<->Matrix bridge by virtue of Telegram?

My wish is to let the current IRC<-> telegram bridge left untouched as it is. However I would like to hear opinions of others as well in this regard.

The current setup looks something like this:

Screenshot_from_2019-04-17_20-27-52.png

@akarshanbiswas I am confused. Are you proposing just creating a matrix room and then having it connect to telegram via a bot?

Hi @bex @bcotton, I asked @akarshanbiswas to open this ticket after we discussed in #fedora-telegram about adding better integration for Matrix users to the Fedora Telegram group chat. I asked him to open this ticket here because infrastructure is required to host a bridge / integration between Matrix and Telegram, and I wanted to better understand how the bridge works. This isn't related to CommOps channels.

The bridge is currently like this:

Telegram <=> IRC <=> Matrix

I understand this request to split it this way:

Telegram <=> Matrix <=> IRC

Metadata Update from @jflory7:
- Issue priority set to: needs review (was: awaiting triage)
- Issue tagged with: needs info, team - infra, type - internal organization

5 years ago

On Wednesday, April 17, 2019 11:25:10 AM EDT Justin W. Flory wrote:

jflory7 added a new comment to an issue you are following:
` Hi @bex @bcotton, I asked @akarshanbiswas to open this ticket after we discussed in#fedora-telegram` about adding better integration for Matrix
users to the Fedora Telegram group chat. I asked him to open this ticket
here because infrastructure is required to host a bridge / integration
between Matrix and Telegram, and I wanted to better understand how the
bridge works. This isn't related to CommOps channels.

The bridge is currently like this:

Telegram <=> IRC <=> Matrix

I understand this request to split it this way:

Telegram <=> Matrix <=> IRC
``

To reply, visit the link below or just reply to this email
https://pagure.io/fedora-commops/issue/199

It seems this would require moving the official channel to Matrix. Is that
what is being suggested here?

--
John M. Harris, Jr. johnmh@splentity.com
Splentity
https://splentity.com/

@jflory7 thanks for the update. I think this could be solved like this:

Matrix <=> Telegram <=> IRC

This is subtle, but I think it lets the Matrix room get what it wants (no reg, cleaned up telegram spam) and requires no change other than a Telegram/Matix bot.

@akarshanbiswas did I get that right?

@johnmh

It seems this would require moving the official channel to Matrix. Is that
what is being suggested here?

I don't read it this way based on the latest comments

@akarshanbiswas did I get that right?

@bex yes.

If we move the official channel to matrix which is awesome in my opinion because matrix is open source decentralised communication, this would require the matrix users to have a free-node account in order to take part in a conversation on it which is not the goal here at the moment.

On Wednesday, April 17, 2019 12:30:04 PM EDT Akarshan Biswas wrote:

akarshanbiswas added a new comment to an issue you are following:
``

@akarshanbiswas did I get that right?

@bex yes.

If we move the official channel to matrix which is awesome in my opinion
because matrix is open source decentralised communication, this would
require the matrix users to have a free-node account in order to take part
in a conversation on it which is not the goal here at the moment. ``

To reply, visit the link below or just reply to this email
https://pagure.io/fedora-commops/issue/199

Err, so you do want to make the Matrix channel the official one? Also, Matrix
is Federated, just like IRC or XMPP, not decentralized.

--
John M. Harris, Jr. johnmh@splentity.com
Splentity
https://splentity.com/

@johnmh

On Wednesday, April 17, 2019 12:30:04 PM EDT Akarshan Biswas wrote:

akarshanbiswas added a new comment to an issue you are following:
``

@akarshanbiswas did I get that right?

@bex yes.
If we move the official channel to matrix which is awesome in my opinion
because matrix is open source decentralised communication, this would
require the matrix users to have a free-node account in order to take part
in a conversation on it which is not the goal here at the moment. ``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-commops/issue/199

Err, so you do want to make the Matrix channel the official one? Also, Matrix
is Federated, just like IRC or XMPP, not decentralized.

The text you quote reads to me like moving the official channel off of IRC is NOT a goal here.

On Wednesday, April 17, 2019 1:10:27 PM EDT Akarshan Biswas wrote:

akarshanbiswas added a new comment to an issue you are following:
``

Also, Matrix

is Federated, just like IRC or XMPP, not decentralized.

No matrix is not federated. It is decentralised. Refer:
https://github.com/matrix-org/synapse ``

To reply, visit the link below or just reply to this email
https://pagure.io/fedora-commops/issue/199

This is federation, not decentralization. XMPP is federated in exactly the
same manner, and IRC is federated in that you choose specific servers to
connect to, none of which have to be connected to a central network. With
XMPP, just as Matrix, anyone can run a service. With IRC, anyone can run a
server, though it will not necessarily allow connectivity to the network of
servers you wish to communicate with users on.

--
John M. Harris, Jr. johnmh@splentity.com
Splentity
https://splentity.com/

@jflory7 thanks for the update. I think this could be solved like this:
Matrix <=> Telegram <=> IRC
This is subtle, but I think it lets the Matrix room get what it wants (no reg, cleaned up telegram spam) and requires no change other than a Telegram/Matix bot.

This makes sense. +1.

@akarshanbiswas If I understand, you are looking for infrastructure? If you there is a place to run a mautrix-telegram bridge, are you interested/able to set up and deploy the service?

The text you quote reads to me like moving the official channel off of IRC is NOT a goal here.

Moving off of IRC is not a goal. The official channel for the Fedora Telegram community is Telegram. Bridges are offered as a convenience to connect different comms platforms in a single place. This change does not impact IRC users as I understand and improves quality-of-life for Matrix users.

If I understand, you are looking for infrastructure? If you there is a place to run a mautrix-telegram bridge, are you interested/able to set up and deploy the service

@jflory7 Sure. :) But since I'm not in telegram, someone from telegram needs to add the bridge bot to get the chat id.

edit: I think I can manage that.

@jflory7 I have asked Tobias Wolfshappen to do with hosting the bridge since I am not getting enough time. Also he has a custom synapse server which belongs to one of his friends so if the main one cuts off for some reason, it won't effect the bridge..

I am closing this issue as stale. A lot of time has passed and many things have changed too. We are now Matrix-first and the IRC-Matrix bridges no longer exist for LiberaChat. The main contributor traffic is no longer on Telegram, although some regional groups still use it predominantly.

Metadata Update from @jflory7:
- Issue close_status updated to: stale
- Issue status updated to: Closed (was: Open)

a month ago

Login to comment on this ticket.

Metadata