Skip Navigation

Does anybody have experiences with element bridging services

element.io /features/matrix-bridging-services

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.

5
5 comments
  • 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.

  • I have no idea about the internals, but I use IRC and Slack bridges, and they seem to work fine.

  • 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.