| 13 Feb 2022 |
 hexa | https://github.com/NixOS/nixpkgs/pull/159867 | 17:20:12 |
| hexa | So, anybody up for further reviews of https://github.com/NixOS/nixpkgs/pull/158605 or can I consider it good to merge? 😛 | 23:13:03 |
| 14 Feb 2022 |
 Dandellion | I was hoping to take a look at it tomorrow, quick overview looked pretty good though, so if you're comfortable feel free | 00:08:25 |
| hexa | I'm obviously poking the dragon 😛 | 00:24:31 |
| hexa | can't have this go stale | 00:24:45 |
| Dandellion | reviewd' | 19:04:22 |
| Dandellion | I still think we should have a services.matrix thing that could be more opinionated around using nginx and getting a setup that should "just work" with minimal configuration | 19:05:51 |
| hexa | thank you! | 19:05:51 |
| hexa | I agree, but this PR is not that step, it is a precursor to get further changes in. | 19:06:41 |
| Dandellion | yep | 19:06:48 |
| hexa | I responded to everything I believe. | 19:41:49 |
| hexa | Specifically secret handling can be built on top of this and I wouldn't add it to the scope of this PR. It is big enough as it is. | 19:42:18 |
| hexa | Sure, at the same time we're asking people to move their secrets from toplevel into settings, this is part of the bulk change nature of this PR | 19:42:54 |
| hexa | * Sure, at the same time we're asking people to move their secrets from toplevel into settings, this is part of the bulk change nature of this PR. | 19:42:55 |
| hexa | If something isn't a regression I'm hesitant to make behavioral changes, like adding further arbitrary trust anchors. | 19:44:43 |
| hexa | * If something isn't a regression, I'm not inclined to fix it. I'm hesitant to make behavioral changes, like adding further arbitrary trust anchors. | 19:45:06 |
| hexa | That warnings has its place, and people should be mindful about it. Shutting it up doesn't really serve our users imo. | 19:46:11 |
| hexa | * That warnings has its place, and people should be mindful about it. Adding another server just to shut it up doesn't really serve our users imo. | 19:46:22 |
| hexa | (except of course if you trust me) | 19:46:45 |
| hexa | How can I enable labs on element-desktop? | 22:09:44 |
 Sumner Evans | In reply to @hexa:lossy.network
How can I enable labs on element-desktop? you have to create a file in ~/.config/Element/config.json. | 23:57:29 |
| hexa | ok, looking into that, thanks | 23:59:05 |
| 17 Feb 2022 |
 @grahamc:nixos.org | Hey folks, hexa just noted that this room is in the space but doesn't have mjolnir set up. Could I get Admin in here to get Mjolnir setup? | 01:52:50 |
|  f0x joined the room. | 20:59:27 |
| f0x | I've been working on adding Synapse workers support to the existing matrix-synapse module. It's messy and probably not ideal since I just started with Nix, but would there be interest in getting this upstreamed? https://git.pixie.town/f0x/nixos/src/branch/synapse-workers/common/modules/synapse | 21:00:57 |
| Dandellion | The current state of getting workers is using some custom config based on https://github.com/dali99/nixos-matrix-modules | 21:02:23 |
| f0x | mine is a bit more opinionated I think, also setting up nginx to get specific routes to the right workers | 21:04:20 |
| Dandellion | you have some cool ideas with how you handle routes and things in your module, but I don't think the synapse module will be handling nginx options directly for a while. And we'll definetly need to use the https://github.com/NixOS/nixpkgs/pull/158605 rfc42 way of setting settings | 21:04:42 |
| Dandellion | * you have some cool ideas with how you handle routes and things in your module, but I don't think the synapse module will be handling nginx options directly for a while. And we'll definetly need to use the https://github.com/NixOS/nixpkgs/pull/158605 rfc42 way of generating the config | 21:04:55 |
| f0x | yeah unfortunate I only learned of that PR just now | 21:05:12 |
