https://redmine.replicant.us/https://redmine.replicant.us/favicon.ico?15984615062022-04-26T11:40:03ZReplicantReplicant infrastructure - Issue #2318: Switch to more simple IRC bridgehttps://redmine.replicant.us/issues/2318?journal_id=93532022-04-26T11:40:03ZDenis 'GNUtoo' CarikliGNUtoo@cyberdimension.org
<ul></ul><p>There is some discussions going on on potentially forbidding software of unknown licenses in the free software distribution guidelines (FSDG).</p>
<p>This affects our infrastructure as matterbridge has too much dependencies and they are all bundled inside matterbridge source code<sup><a href="#fn1">1</a></sup>.</p>
<p>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.</p>
<p>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.</p>
<p id="fn1" class="footnote"><sup>1</sup> <a class="external" href="https://git.replicant.us/contrib/GNUtoo/infrastructure/guix/tree/gnu/packages/matterbridge.scm?h=matterbridge-unvendor&id=3731c5a42485951f0eed183ed6d4817b1f897a5b">https://git.replicant.us/contrib/GNUtoo/infrastructure/guix/tree/gnu/packages/matterbridge.scm?h=matterbridge-unvendor&id=3731c5a42485951f0eed183ed6d4817b1f897a5b</a></p> Replicant infrastructure - Issue #2318: Switch to more simple IRC bridgehttps://redmine.replicant.us/issues/2318?journal_id=93542022-04-26T11:49:06ZDenis 'GNUtoo' CarikliGNUtoo@cyberdimension.org
<ul><li><strong>Type of work</strong> <i>Wiki editions</i> added</li></ul><p>There is also another IRC bridge based on libpurple<sup><a href="#fn1">1</a></sup>.</p>
So for promising IRC bridges, we could:
<ul>
<li>Review it, review its dependencies, and add the review in the wiki.</li>
<li>If it's good we could package it in Guix or Trisquel</li>
<li>And we could finally update the deployment code<sup><a href="#fn2">2</a></sup> to use this new IRC bridge</li>
</ul>
<p>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.</p>
<p>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.</p>
<p id="fn1" class="footnote"><sup>1</sup> <a class="external" href="https://git.parabola.nu/~bill-auger/bridgin.git/">https://git.parabola.nu/~bill-auger/bridgin.git/</a></p>
<p id="fn2" class="footnote"><sup>2</sup> <a class="external" href="https://git.replicant.us/infrastructure/matterbridge/tree/">https://git.replicant.us/infrastructure/matterbridge/tree/</a></p>
<p id="fn3" class="footnote"><sup>3</sup> <a class="external" href="https://git.replicant.us/infrastructure/matterbridge/tree/matterbridge.service">https://git.replicant.us/infrastructure/matterbridge/tree/matterbridge.service</a></p>
<p id="fn4" class="footnote"><sup>4</sup> <a class="external" href="https://git.replicant.us/infrastructure/matterbridge/tree/matterbridge.toml.example">https://git.replicant.us/infrastructure/matterbridge/tree/matterbridge.toml.example</a></p>