weechat-matrix VS matterbridge

I haven't had much occasion to use it (I dipped into a gaming group that used Matrix but quickly fell out of it) but https://github.com/poljar/weechat-matrix seems mostly adequate if you are a weechat user and just need the text chat features. Feels just like IRC.

I followed this description - weechat matrix github

For a nicely documented and clean Matrix client implementation in Python, see weechat-matrix[1] and the matrix-nio[2] library it's based on. There's also Mirage[3] which is also based on matrix-nio and is a GUI client.

[1]: https://github.com/poljar/weechat-matrix

[2]: https://github.com/poljar/matrix-nio

[3]: https://github.com/mirukana/mirage

The weechat plugin unfortunately cannot coexist with wee-slack (https://github.com/wee-slack/wee-slack/issues/812, https://github.com/poljar/weechat-matrix/issues/248), so if one wants to participate in the Haskell Foundation Slack, or any other Slack (e.g. for work), then Matrix is off limits. Yeah, it's just a bug that will eventually get fixed, but it does make things unnecessarily complicated. :-/

I have installed the weechat client with matrix (https://github.com/poljar/weechat-matrix) and it is running properly. However, I cannot figure out how to install scripts. Particularly, the upload and download files scripts mentioned in the github page, since they are not in the official list of scripts. How should I proceed?

All of them. :)

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

An involved alternative is to access whatsapp through a matrix bridge. It requires either paying for hosting or figuring out how to host a matrix server and the whatsapp bridge [1]; I do the latter and can attest it's not very hard if you have a technical background (and you're on hn, so you probably do), but YMMV. There's a lot of matrix clients, all of which open source; and the whatsapp bridge works really well nowadays, enough that I've been using it almost exclusively for my texting (no whatsapp calls tho).

In fact, I recently bought a non-smartphone running KaiOS, and use whatsapp through a matrix client, chooj - which, although in early alpha, works well for my use case of accessing whatsapp while outside the home without having to carry an addictive smartphone with me. KaiOS does have a native whatsapp app, but it does not support whatsapp web at all, and that is an absolute necessity for me, especially when typing requires (bad) T9.

My point is, matrix bridges afford A LOT of freedom with how to access whatsapp (and other closed-source communication apps), if you're willing to deal with some friction. And now they're stable and mature enough that they work pretty darn well - no doubt thanks in part to support from beeper [2], which funds development for several major bridges. Within the android ecosystem, beeper is probably the easiest way to gateway all your communications through matrix, though I have no experience with it. Sounds like paid matrix+bridge hosting, plus a generally much nicer and frictionless experience.

[1]: https://github.com/42wim/matterbridge

[2]: https://www.beeper.com/

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

I personally use matterbridge to bridge between specific IRC channels and specific discord server channels, and run it on a FreeBSD server. Packages are available for it on the BSDs and major Linux distributions. Follow the instructions for configuration and enable its service as appropriate on the OS.

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.