| 10 Oct 2023 |
 June | I guess writing in here caused the reviews and merge. Thank you! | 23:30:14 |
| 11 Oct 2023 |
|  @fantasycookie17:artemislena.eu changed their profile picture. | 00:08:12 |
| 12 Oct 2023 |
| @fantasycookie17:artemislena.eu changed their profile picture. | 11:36:49 |
| @fantasycookie17:artemislena.eu changed their profile picture. | 11:38:30 |
| @fantasycookie17:artemislena.eu changed their profile picture. | 11:42:49 |
| 18 Oct 2023 |
 hexa | https://pktz.fr/matrix/security/2023-synapse-acl-cache/ | 19:37:18 |
| 2 Nov 2023 |
 Sumner Evans | We (Beeper) are rewriting the Signal bridge in Go. It requires compiling the libsignal Rust library and then we use cgo to link against the C bindings of libsignal.
We are also using Go workspaces because cgo only really works well for root packages.
I'm looking into how we should package it in Nixpkgs, but I am having a hard time dealing with the workspaces, and also trying to figure out how to compile and then link against the Rust code. Any tips would be greatly appreciated.
| 04:34:09 |
| 6 Nov 2023 |
 @me:indeednotjames.com | https://matrix.org/blog/2023/11/06/future-of-synapse-dendrite/ | 13:39:00 |
 @piegames:matrix.org | Brace for even more chaos in their issue trackers | 13:49:14 |
| hexa | uh, what is the tl;dr? | 15:42:19 |
| Sumner Evans | tl;dr is that Element has historically donated a lot of dev time to maintaining Synapse and Dendrite as Apace-licensed Matrix Foundation projects. That is coming to an end, and Element will be forking Synapse and Dendrite from the foundation and all future contributions they make to the projects will be CLAd and under AGPL.
Reason is that Element is hemorrhaging cash, and they are hoping that this will force people who fork Synapse and make proprietary modifications will either have to open source those changes or pay them for an alternative license. | 15:46:42 |
 miloignis | I've been out of the Matrix development rooms for a while - are there any significant proprietary modifications to synapse out there? | 15:49:32 |
 problems | this worries me | 15:55:42 |
 @delroth:delroth.net | In reply to @miloignis:synapse.room409.xyz
I've been out of the Matrix development rooms for a while - are there any significant proprietary modifications to synapse out there? AFAICT several companies and public entities / governments run large private deployments of Matrix, and have basically decided that they wouldn't fund any of it | 16:09:59 |
| @delroth:delroth.net | likely these private deployments come with proprietary modifications, and I expect that this is the Matrix Foundation's way to tell these people to negotiate a contract with them to keep their changes proprietary | 16:10:56 |
 Dandellion | it's element's way of saying it anyhow | 16:13:34 |
| Dandellion | the foundation isn't stoked about it | 16:13:41 |
| Dandellion | * the foundation isn't stoked about it, and is not getting anything out of it | 16:13:51 |
| Dandellion | (other than elements continued existance and synapse being maintained, even if outside of the foundation's control) | 16:14:23 |
| Dandellion | * (other than element's continued existance and synapse being maintained, even if outside of the foundation's control) | 16:14:30 |
| Sumner Evans | In reply to @kity:kity.wtf
this worries me as long as you aren't making proprietary modifications to Synapse, I think nothing will change functionally | 20:13:23 |
| @delroth:delroth.net | as long as you aren't making any modifications to Synapse* | 20:36:23 |
| @delroth:delroth.net | if you're making a modification, you need to also change your modified Synapse to provide a prominent notice of the source code of your modified Synapse to anyone who interacts with it over the network, and nobody has any clue what that means because the AGPLv3 has never been tested in courts to actually figure out what the legal system thinks "prominent notice" means or what "interacts with it over the network" means | 20:37:27 |
| @delroth:delroth.net | the very few things we have to clarify the interpretation of that clause in the AGPLv3 is the (non-binding) FAQ from the FSF, which gives examples such as "if you modify an HTTP proxy that is licensed under the AGPLv3, you should insert an interstitial page or a banner into the proxied content so that users of your proxy (over the network) can know where to find the source code" | 20:39:06 |
| @delroth:delroth.net | (https://www.gnu.org/licenses/gpl-faq.en.html#AGPLProxy) | 20:39:28 |
| @delroth:delroth.net | * (https://www.gnu.org/licenses/gpl-faq.en.html#AGPLProxy "When users initially start using the proxy, you can direct them to a page with the offer of source along with any other information you choose to provide." is the exact wording) | 20:39:41 |
| @delroth:delroth.net | * the very few things we have to clarify the interpretation of that clause in the AGPLv3 are in the (non-binding) FAQ from the FSF, which gives examples such as "if you modify an HTTP proxy that is licensed under the AGPLv3, you should insert an interstitial page or a banner into the proxied content so that users of your proxy (over the network) can know where to find the source code" | 20:43:12 |
| 14 Nov 2023 |
| June changed their display name from Julian to June. | 02:19:37 |
| 15 Nov 2023 |
|  @grahamc:nixos.org removed their profile picture. | 16:38:42 |
| @grahamc:nixos.org removed their display name grahamc (he/him). | 16:39:02 |
