Spectrum 2 VS matterbridge

This is the point where I lose everyone and a big reason for this is that people don't understand how libpurple works with Pidgin, Finch, Adium, bitlbee, spectrum2, telepathy-haze, and maybe others I'm not aware of or forgetting. So that's what we're going to try and tackle today.

> and supports bridging to other types of networks which aren't matrix-based

https://sr.ht/~nicoco/slidge/

Turn any XMPP client into that fancy multiprotocol chat app that every cool kid want.

> Signal, Telegram, Discord, Steam, Mattermost, Facebook, Skype

https://spectrum.im/

Spectrum is an open source instant messaging transport. It allows users to chat together even when they are using different IM networks.

https://github.com/louiz/biboumi

Biboumi is an XMPP gateway that connects to IRC servers and translates between the two protocols. It can be used to access IRC channels using any XMPP client as if these channels were XMPP MUCs.

------

I'm using all of those daily to connect to all my other accounts, Slidge is the most modern one and is having lots of features ported to the modern XMPP extensions.

It's actually closer to spectrum2 in how it behaves. I hope slidge will get as rock-solid as biboumi is!

https://spectrum.im/

I want this to take off. I'm tired of having to follow trends: IRC to ICQ to MSN to Skype to Google Talk to Facebook Messenger to Whatsapp to Signal.

Pidgin is good (I also miss the ancient Trillian, even though it was closed source), but limited to a local device.

There are XMPP Transports as well for these (see https://git.eta.st/eta/whatsxmpp , https://gitlab.com/nicocool84/spectrum2_signald , but sadly https://spectrum.im/ is surprisingly finicky to set up.)

There are at least hundreds of implementations of XMPP that are interoperable (at 5-6 actively developed server implementations, many more libraries and many client applications). There are at least hundreds of thousands deployed XMPP services.

In addition XMPP can be linked with other protocols/networks via bridges/gateways. Some examples:

- Spectrum: XMPP gateway project based on libpurple (support for many protocols): https://spectrum.im/

- WhatsApp bridge: https://git.eta.st/eta/whatsxmpp

- Telegram bridge: https://github.com/codingteam/emulsion

- Signal bridge: https://gitlab.com/nicocool84/slidge/ (replacement of https://gitlab.com/nicocool84/spectrum2_signald/ )

Given such a diverse ecosystem of open-source and proprietary implementations, I'd say XMPP is one of the best examples of widespread protocol interoperability that there is.

Nope, the project is almost dead (as most XMPP projects), but there are some recent commits at https://github.com/SpectrumIM/spectrum2

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.