matterbridge VS Element

All of them. :)

https://github.com/42wim/matterbridge

We use matterbridge to bridge IRC to matrix at https://tetaneutral.net

https://github.com/42wim/matterbridge

It's a chat bridge for different platforms. https://github.com/42wim/matterbridge

https://github.com/42wim/matterbridge perhaps?

Hi, I'm looking for an easy to use automation tool for my company. There are tons of projects out there and I find it hard to pick one among them. I found : - hugging - n8n - beehive - flogo - metterbridge - node-red

As for the use case op hopes for -- the matterbridge project might be relevant. Ideally, you could migrate the history to a Mattermost server and set up the bridge. The Mattermost server will log all future communications automatically. The benefit of this over a pure archive (HTML or PDF type) is that the archive itself is a full-featured workspace ready to be used standalone at any time, should any issues arise from Slack.

Oh, interesting! It seems like an alternative to MatterBridge but for 1 to 1 bridging.

Well the good thing about nyxt is it's super extensible so a PoC doesn't require proper "reception" on their side.

Do you maybe have a gateway/bridge to a libre network such as IRC/XMPP/Matrix? I find HTMX pretty interesting but i wouldn't touch discord with a 10-foot pole, if only because my limited computing resources won't allow for such a resource-hungry app to run in the background.

It seems like matterbridge supports discord backend but i don't have a discord account to try it with. If you're not willing to host matterbridge, i'm already hosting one and i would just need credentials to try and connect it to Discord. If you're willing to give that a try, feel free to mail me at my username @ thunix.net.

https://github.com/42wim/matterbridge

irc client of choice+znc+matterbridge for all the new stuff

I was about to ask, "Can you explain a bit more? Matterbridge, from what I understand, bridges an existing Mattermost install with other chat services." , and then I read the About on the page I linked, and yep, it clearly says there, at the end, _Mattermost not needed_. Another page lists some config examples which clearly show a connection between Discord and Gitter (https://github.com/42wim/matterbridge/wiki/How-to-create-your-config). I suggested installing Mattermost because it is the only self-hostable option that I would recommend installing (some of the others shown are resource-hungry, or just complicated... but that's just me). Thus, using the mobile client for Mattermost would allow OP to have a mobile solution. Since it can work with Telegram and WhatsApp too, if they have those existing apps then I guess, once more, Mattermost isn't needed.

Element is an open-source instant messaging client built on the Matrix protocol, offering users features such as end-to-end encryption, file sharing, and voice/video calls. The self-hosted version accommodates up to 200 users at no charge, providing a budget-saving secure and collaborative communication platform. perthguppy describes it as a "slack style team chat."

Sounds like you’re talking about Element Web or Desktop here. On Mobile, we just rewrote the app as Element X and it addresses almost all your concerns (other than per-room nicks, although ironically Element Web does have that today - try the /roomnick command, from memory).

Having got Element X out the door, my attention at least is going to swing back to Element Web. In terms of encryption disasters, we are about to switch Element Web’s crypto to the same rust implementation as Element X, hopefully next week - you can track the progress at https://github.com/vector-im/element-web/issues/21972#issuec.... Hopefully this will make a much-needed massive improvement on encryption, while also speeding it up 5x or so. On Element X, encryption failures are almost unheard of (other than when talking to Element Web).

The main remaining Nebuchadnezzar issue is mitigating server-controlled group membership. The first step has been to kill off the 1st gen E2EE implementations, which were responsible for the implementation vulns found by RHUL - and we should hopefully conclude that next week by moving everything into the matrix-rust-sdk crypto create implmentation: https://github.com/vector-im/element-web/issues/21972#issuec... is the tracker.

Then, we can address the harder server-controlled group membership issue in one place. First step will be to improve device verification & trust so that trust is the default, not the exception, to make it easier to spot and warn about unexpected devices in the room. The full solution is then either MSC3917 (https://github.com/matrix-org/matrix-spec-proposals/blob/fay...) - or potentially to switch everything to MLS.

We're working on MLS anyway in parallel to RHUL mitigation work; you can see the progress at https://arewemlsyet.com, and it's looking good.

I'm guessing you're not interested in doing a podcast on "yay we converged our crypto implementations on a single robust Rust implementation so we can fix the remaining bugs in one place", but as soon as the server-controlled group membership thing is solved we'll be in touch. Work has also gone much slower than hoped on this, thanks to the joys of funding open source.

- Various GUI instability bugs: chats that are suddenly empty, text suddenly randomly overlaid on other text

1: https://github.com/vector-im/element-web/issues/24392

Why don't you mean Matrix? This is precisely what Element is, built on Matrix: https://element.io