Show HN: Beeper – All Your Chats in One App

Re:Show HN: Beeper – All Your Chats in One App by ignoramous on Wednesday January 20, 2021 @01:12PM (#25849773)

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

[ Parent | on HN ]

Re:Show HN: Beeper – All Your Chats in One App by erohead on Wednesday January 20, 2021 @01:26PM (#25849983)

The bridges do not run inside the client, they either run on your own self-hosted server or our cloud.

[ Parent | on HN ]

Re:Show HN: Beeper – All Your Chats in One App by KitDuncan on Thursday January 21, 2021 @09:45AM (#25859314)

I already have a Matrix server with the bridges I need running. Can I still use your desktop client? It looks sick!

[ Parent | on HN ]

Re:Show HN: Beeper – All Your Chats in One App by nextaccountic on Wednesday January 20, 2021 @01:27PM (#25849994)

> Then aren't you required to AGPLv3 the desktop client, too?

Only if the desktop client is legally a derivative work of the bridges.

[ Parent | on HN ]

Re:Show HN: Beeper – All Your Chats in One App by rkangel on Thursday January 21, 2021 @08:35AM (#25858625)

The "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/

[ Parent | on HN ]