Issue #2318
openSwitch to more simple IRC bridge
0%
Updated by Denis 'GNUtoo' Carikli over 2 years ago
There is some discussions going on on potentially forbidding software of unknown licenses in the free software distribution guidelines (FSDG).
This affects our infrastructure as matterbridge has too much dependencies and they are all bundled inside matterbridge source code1.
So without reviewing all the dependencies, it's hard to know if the licenses are all free or if there is some incompatible licenses somewhere.
So it would probably be better to have an IRC bridge that has less dependencies and that can more easily be packaged in various distributions like Trisquel or Guix.
Updated by Denis 'GNUtoo' Carikli over 2 years ago
- Type of work Wiki editions added
There is also another IRC bridge based on libpurple1.
So for promising IRC bridges, we could:- Review it, review its dependencies, and add the review in the wiki.
- If it's good we could package it in Guix or Trisquel
- And we could finally update the deployment code2 to use this new IRC bridge
The biggest constraints here is security: this bridge runs on the same VM than the Replicant source code, so we need security to really work. With matterbridge we did reuse Parabola's systemd service unit [3] that also sandboxes matterbridge. So the same thing would need to be done with the new IRC bridge.
Apart from security we also need the IRC bridge to support various features needed to properly connect to networks (SASL, etc) [4] and we also need Tor support in case we need to switch to Tor due to issues with our bridge IP address.
1 https://git.parabola.nu/~bill-auger/bridgin.git/
2 https://git.replicant.us/infrastructure/matterbridge/tree/
3 https://git.replicant.us/infrastructure/matterbridge/tree/matterbridge.service
4 https://git.replicant.us/infrastructure/matterbridge/tree/matterbridge.toml.example