Hi,
we’re working on a solution for interoperability between different messaging platforms. Users are running a matrix server internal and want to get in contact by customers via whatsapp, signal and so on but want to stay with the privacy of matrix. Does anybody have an idea about what happens to metadata created by whatsapp etc. during bridging.
I did setup an instance for myself, using dendrite as the matrix server. Don’t do that if you have multiple users.
I had those bridges:
- heisenbridge (IRC)
- mautrix-telegram
- mautrix-whatsapp
- mautrix-discord
All these bridges require that a user “link” their account with the bridge, and then the bridge will create “fake” users to replicate the user’s contact on WhatsApp, telegram and discord. It means that all users connected to the server will see these contacts (I don’t think they can interact though), but it might leak crucial information about your contacts, like their name and phone number for instance.
I don’t know if synapse can work around that, but you should check it out.
Ah okay thanks! I will give it a try soon. My hope was that its not just basically connecting accounts but it could be a way to interact with whatsapp user while not havingan separate account
Thanks!
Dont
That’s exactly what it is. It works just like Whatsapp Web, so when you’re connected, you don’t need whatsapp to be running on your phone at all. It’s just that to be “linked” to your account, you need a cookie which is only valid for 15 days, so every now and then, you need to refresh it.
I have no idea about the internals, but I use IRC and Slack bridges, and they seem to work fine.
What do you mean by “metadata”?
I use bridges for WhatsApp, Telegram, and Discord.
They all access my accounts, then encrypt messages for matrix, meaning the matrix admin (me) can’t read the messages, only the intended recipients can.
