!vxTmkuJzhGPsMdkAOc:transformierende-gesellschaft.org

NixOS Matrix Subsystem

148 Members
Coordination and discussion about the matrix subsystem in NixOS - https://wiki.nixos.org/wiki/Matrix74 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
10 Oct 2023
@julian:nekover.se@julian:nekover.seHi, I made a small fix for the matrix synapse service (which is also my first ever PR). Do the right people automatically discover those PRs somehow?00:17:56
@fantasycookie17:artemislena.eu@fantasycookie17:artemislena.eu changed their profile picture.20:31:11
@julian:nekover.se@julian:nekover.seI guess writing in here caused the reviews and merge. Thank you!23:30:14
11 Oct 2023
@fantasycookie17:artemislena.eu@fantasycookie17:artemislena.eu changed their profile picture.00:08:12
12 Oct 2023
@fantasycookie17:artemislena.eu@fantasycookie17:artemislena.eu changed their profile picture.11:36:49
@fantasycookie17:artemislena.eu@fantasycookie17:artemislena.eu changed their profile picture.11:38:30
@fantasycookie17:artemislena.eu@fantasycookie17:artemislena.eu changed their profile picture.11:42:49
18 Oct 2023
@hexa:lossy.networkhexahttps://pktz.fr/matrix/security/2023-synapse-acl-cache/19:37:18
2 Nov 2023
@sumner:nevarro.spaceSumner 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.comemilyhttps://matrix.org/blog/2023/11/06/future-of-synapse-dendrite/13:39:00
@piegames:matrix.org@piegames:matrix.orgBrace for even more chaos in their issue trackers13:49:14
@hexa:lossy.networkhexauh, what is the tl;dr?15:42:19
@sumner:nevarro.spaceSumner Evanstl;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:synapse.room409.xyzmiloignisI've been out of the Matrix development rooms for a while - are there any significant proprietary modifications to synapse out there?15:49:32
@kity:kity.wtfproblemsthis worries me15:55:42
@delroth:delroth.net@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@delroth:delroth.netlikely 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 proprietary16:10:56
@dandellion:dodsorf.asDandellionit's element's way of saying it anyhow16:13:34
@dandellion:dodsorf.asDandellionthe foundation isn't stoked about it16:13:41
@dandellion:dodsorf.asDandellion * the foundation isn't stoked about it, and is not getting anything out of it16:13:51
@dandellion:dodsorf.asDandellion(other than elements continued existance and synapse being maintained, even if outside of the foundation's control)16:14:23

Show newer messages


Back to Room ListRoom Version: 4