3 ms·
Thanks! Beeper looks amazing. > Our desktop client is closed source, but you can use Element (or any open source Matrix client) if you prefer. I see most brid
by ignoramous 6y ago
Thanks! Beeper looks amazing.
> Our desktop client is closed source, but you can use Element (or any open source Matrix client) if you prefer.
I see most bridges are licensed AGPLv3 [0]: Aren't you required to AGPLv3 the desktop client, too?
[0] For ex: https://gitlab.com/nova/whatsapp/-/blob/master/LICENSE https://gitlab.com/nova/whatsapp/-/blob/master/LICENSE
- erohead 6y agoThe bridges do not run inside the client, they either run on your own self-hosted server or our cloud.
- KitDuncan 6y agoI already have a Matrix server with the bridges I need running. Can I still use your desktop client? It looks sick!
- nextaccountic 6y ago> Then aren't you required to AGPLv3 the desktop client, too? Only if the desktop client is legally a derivative work of the bridges.
- deleted 6y ago[deleted]
- rkangel 6y agoThe "network connection" provision of AGPL doesn't require you to open source anything you use to talk to it, just modifications of it. To make it clearer: Client <--> Server. The server is AGPL licenced. I can write a client to talk to the server and I don't have any licence restrictions. For example - if I write a web client to talk to an AGPL web server, I don't have to open source the client. If I modify the AGPL server, and then put that modified server on the internet then the AGPL terms require me to make available the modified source code. I am not a lawyer, but this is my understanding of this: https://choosealicense.com/licenses/agpl-3.0/ https://choosealicense.com/licenses/agpl-3.0/