10 ms·

Is there going to be more muscle put into polishing up the various bridges? Matrix has an amazing opportunity to be the glue protocol between various communicat

Is there going to be more muscle put into polishing up the various bridges? Matrix has an amazing opportunity to be the glue protocol between various communication silos, but there's a few things I've encountered that have been preventing me from using it further. One issue I hit is this: https://github.com/matrix-org/matrix-appservice-slack/issues/627 https://github.com/matrix-org/matrix-appservice-slack/issues... I tried pinging the people that were committing to the repo on the matrix channel for that bridge, but never got a response and now I'm just stuck with a room with a dead bridge. It's not a huge deal since the Matrix side of things still works, but having some way to reach out for stuff like that would be really helpful. The other thing is this issue: https://github.com/matrix-org/matrix-appservice-discord/issues/738 https://github.com/matrix-org/matrix-appservice-discord/issu... It's not a showstopper since the bridge still works, but it's a lot of management to sync all of the rooms initially, and keep them in sync with any changes. I'm going to wait before that's implemented before suggesting that we try bridging Discord and Matrix for my friend group that's stuck on Discord. Hopefully this doesn't come across as negative, I still use and love Matrix myself. All I want for Christmas though is to have one communication app in my life that talks to everyone everywhere effortlessly :)

distantsounds 4y ago
there's no money to be made in interoperability. did you RTFM? they clearly state they are not getting support on the core services while third parties just build out bridges where they see it beneficial to them.
Arathorn 4y ago
The problem with maintaining bridges is that there are loads of them, and by definition they are a moving target to track the destination systems. So while there's a three person full-time bridge team, they don't have bandwidth to jump on each and every bug as it comes in - and supplying more muscle there is not going to happen unless the funding issues mentioned in the blog post get resolved. So either the wider open source community will need to step up to contribute fixes, or the bugs will get resolved when they get to the top of the todo list. All I want for Christmas is to figure out a way to locate more $ to more people to work fulltime on stuff like the bridge backlog! P.S. I think the sibling reply has this wrong: there absolutely is money to be made in interoperability, including bridging. However, there's no incentive for that money to flow back to the upstream project, other than long-term thinking or good will.

distantsounds 4y ago

there's no money to be made in interoperability. did you RTFM? they clearly state they are not getting support on the core services while third parties just build out bridges where they see it beneficial to them.

Arathorn 4y ago

The problem with maintaining bridges is that there are loads of them, and by definition they are a moving target to track the destination systems. So while there's a three person full-time bridge team, they don't have bandwidth to jump on each and every bug as it comes in - and supplying more muscle there is not going to happen unless the funding issues mentioned in the blog post get resolved. So either the wider open source community will need to step up to contribute fixes, or the bugs will get resolved when they get to the top of the todo list. All I want for Christmas is to figure out a way to locate more $ to more people to work fulltime on stuff like the bridge backlog! P.S. I think the sibling reply has this wrong: there absolutely is money to be made in interoperability, including bridging. However, there's no incentive for that money to flow back to the upstream project, other than long-term thinking or good will.