4 ms·
As someone also running FOSS projects on discord because it's a non-choice, hard agree. Boycotting proprietary platforms is a good end-goal, but it's about as f
by advael 3y ago
As someone also running FOSS projects on discord because it's a non-choice, hard agree. Boycotting proprietary platforms is a good end-goal, but it's about as feasible to convince people not to use dominant organizing tools like discord and github as it is to get them off the mobile duopoly right now.
- _dmn7 3y agoI maintain a semi-popular project [1] with a support chat which is bridged between Matrix, Telegram, and Discord. The decision to bridge it to Discord was made having thought long and hard about it some time after reading this post. My stance is that it is okay to use proprietary platforms as long as it does not negatively impact the users not willing to use them, i.e. all channels must be bridged to non-Discord, so that it does not "partition the community" in any way. Discord-specific features should be avoided to not affect the usability of users on Matrix. So far it works well and I get to basically have the cake and eat it too. 1. https://github.com/FreeLanguageTools/vocabsieve https://github.com/FreeLanguageTools/vocabsieve
- mxmlnkn 3y agoWhat are you using to bridge these three chat providers?
- _dmn7 3y agoAn Ansible playbook running on a relatively cheap hetzner box. In general bridges require you to self-host a homeserver. A federated homeserver will need 4GB of RAM at least and 8GB if you plan on joining large rooms. The playbook is controlled from a single config file and sets up all the bridges you need. https://github.com/spantaleev/matrix-docker-ansible-deploy https://github.com/spantaleev/matrix-docker-ansible-deploy