Authentication

  1. Open a private chat with the bridge bot. Usually @facebookbot:your.server

Web-based login

New in version 0.2.1

The bridge includes a web-based login interface to prevent the bridge and homeserver from seeing your Facebook password. The web interface must be enabled in the config to use this method (appservice->public). After web login is enabled, send login with no parameters to the bridge bot, click the link it gives, and use the login form on the website to log in.

In-Matrix login

  1. Send login <email> to the bridge bot.
    • N.B. Prior to v0.2.1, the syntax is login <email> <password>, rather than sending the password in a separate message.
  2. Send your password to the room.
  3. If you have 2FA enabled, the bot will ask you to send the 2FA token.
  4. Recent chats should now get portals automatically. Other chats will get portals as you receive messages.

Note that in some cases, Facebook might decide your account has suspicious activity and block you until you do some tasks like adding a phone number or resetting your password. In most cases, enabling two-factor authentication solves this. If that doesn't help, hosting the bridge at home or making it proxy all traffic through a residential IP can help further reduce suspiciousness. The bridge can run separately from Synapse, e.g. on a Raspberry Pi. It can also use the http_proxy environment variable for all Facebook traffic.