https://mattermost.com/marketplace/mattermost-matrix-connector/
This is what RocketChat were doing since about 2022. Although their documentation suggests they are working on full Matrix support inside the RC server itself, due sometime this month;
Post
https://mattermost.com/marketplace/mattermost-matrix-connector/
This is what RocketChat were doing since about 2022. Although their documentation suggests they are working on full Matrix support inside the RC server itself, due sometime this month;
@strypey the linked source code was last touched 2 years ago. Is it really new or even actually working? Seems a bit strange 🤔
@HarHarLinks
> the linked source code was last touched 2 years ago
It's a simple bit of sticky tape between a MM and Synapse server. Maybe doesn't need active development?
Also lack of updates fits my hypothesis that it's a stopgap, while they work on a full Matrix implementation in MM server itself.
> Is it really new
Only to me it seems : P
> even actually working?
Haven't tested, no idea. Any MM hosters in the house?
(1/?)
@controlfreak
> What's better than just one resource abyss?
The performance cost of Synapse has always been overstated. People would join dozens of high-traffic public rooms, and wonder why their homeserver was doing so much work. There were real technical chokepoints, but many of these have been progressively solved;
https://matrix.org/blog/2018/12/20/synapse-0-34-0-released/
https://matrix.org/blog/2020/11/03/how-we-fixed-synapse-s-scalability/
Matrix 2.0 brings further improvements, like Sliding Sync;
@strypey bad past experience aside, never keen to try again given their warm embracing stance to take money to gargle "law enforcement" and gubment spying.
(1/?)
@controlfreak
> their warm embracing stance to take money to gargle "law enforcement" and gubment spying
I doubt we're not going to agree on whether this is justifiable or not. But I'm happy to argue the toss if you're up for it.
(2/?)
But that aside, let's say we agree giving Element money is wrong. AFAIK Element forked Synapse for their own use under a different license, and Synapse itself is now being developed by the Matrix Foundation.
But even if I'm wrong and Synapse is still being developed by Element, why does that matter? It's Free Code software. If they started putting anything dodgy into the code - and there's no evidence that they have - it can be forked.
(3/3)
I was going to point out that you could use Matrix via a homeserver other than Synapse. But maybe that's what you're already doing.
FWIW there's a growing number of Free Code homeservers *not* developed by Element;
https://matrix.org/ecosystem/servers/
RC won't be one, even when they ship their Matrix implementation, due to the Source Available license on MongoDB.
But AFAIK eJabberd gives you XMPP *and* Matrix federation more or less out-of-the-box;
https://www.process-one.net/blog/matrix-gateway-setup-with-ejabberd/
@strypey not really a feels argument when when attend global military and law enforcement expos and have no problem contributng to militarised police and comms leading to war crimes.
@controlfreak
> attend global military and law enforcement expos
I'm not disputing the fact that Element have these customers. I'm disputing the idea that this is a good reason to boycott them.
Firstly, Element don't make drones. They make encrypted communications software. Who cares who their customers are?
Further, if military and law enforcement depend on the robustness of Matrix encryption to protect their own communications, they have a strong incentive to prevent it being compromised.
(2/?)
Having said all that, running Synapse alongside an existing chat silo server is always going to use more resources than using the protocol directly in the chat server. I'm guessing that as with RocketChat, the supported bridge is a stopgap to provide the UX of Matrix interoperation. While they work on implementing the protocol internally. Which is why I made the comparison : )
A space for Bonfire maintainers and contributors to communicate