Open anaskaejdar opened 5 years ago
hi. thats the reason i deinstalled the bridge again after a short testing period. i am running a homeserver but i dont want to provide the server only for myself. i want to provide server for a group of people who know each other. I wanted to share the infrastructure to let multiple users pipe their discussions on facebook to synapse ecosystem. But the bridge only supports one user (myself).
I wouldn't expect to ever see this supported. It's very much the nature of a puppet bridge that you have 1 instance per user. You can read about limitations and implications of puppet bridges in the upstream library: https://github.com/matrix-hacks/matrix-puppet-bridge It will always be the case that the server owner will have access to the auth token used by any puppet-bridge
, so it's really not a good idea to use a puppet-bridge
hosted by someone else unless you really, really, really trust them.
But running 2 or 3 or 4 copies of the bridge really isn't a big deal. The bridge I'm running is only using about 4MB of RAM. It's really quite lightweight.
What this project could do is make it easier to run multiple instances at once. We need:
config.json
should include an option to specify the paths for appstate.json
, user-store.db
, and room-store.db
. Then they could be moved outside the application folder.index.js
needs to support a -c
/--config
option to specify the path for config.json
If the above 2 changes were made, then it would be reasonable to convert the systemd service file to a systemd template file.
I figured I'd try to bridge a second user by adding their access tokens to config.json as a second user. That didn't work. I don't want to set up a second bridge for a second user, since that would duplicate FB->Matrix puppets unnecessarily. It'd be great if this bridge supported multiple Matrix->FB bridges, and maybe the server owner can configure a default account to be used as bridgebot or whatever.