Ferdi VS matterbridge

It's subscription priced now...? Maybe try Ferdi instead...? Same App but without subscriptions. https://github.com/getferdi/ferdi

Suggesting this one must be cheating https://github.com/getferdi/ferdi

This probably was already a problem in Ferdi. There is/was an issue on github https://github.com/getferdi/ferdi/issues/1458

I use Ferdi to multiplex my messaging apps and have them all in one place. It's basically a glorified web browser that only opens iframes to specific pages (eg: discord). In this environment Discord has some interesting behavior where the menu bar at the top left is very slow to respond, and despite large window sizes (and refreshing at these large window sizes) the screen always seems to be in a single column layout, never showing the chat messages + channel list at the same time.

I just noticed the getferdi.com website is up again including a video, link to the code etc.

Then you can use https://github.com/getferdi/ferdi, which is a unrestricted Fork of Franz

Ferdi (Website, GitHub): Free fork of Franz. Announced on June 11, 2022 that "There will be no further updates to Ferdi. 🏄‍♂️" but that tweet is now deleted and the repo is updating again... But they've disabled the issue tracker behind a $9/month paywall.

I see that the repo is back (https://github.com/getferdi/ferdi)

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.