| 27 Jun 2025 |
 raitobezarius | with "How do I use Nix on Fedora?" | 10:26:52 |
 emily | the two words every Fedora user loves to hear: "disable SELinux" | 10:28:13 |
 raboof | we'd like to have a simple static website for the NixNL community/meetup. could we serve that under i.e. nl.nixos.org or would it be better to put it somewhere else? having it on 'shared' infrastructure seems nice, so that it can be transferred when the current people go MIA (like happened with https://www.meetup.com/Amsterdam-Nix-Meetup/...) | 13:46:30 |
| 28 Jun 2025 |
 sterni | Another weird one: https://hydra.nixos.org/build/301060494/nixlog/1, remove-references-to is added to nativeBuildInputs unconditionally in haskellPackages. Can't reproduce this failure. | 09:57:34 |
| 30 Jun 2025 |
|  sinan changed their profile picture. | 02:11:25 |
|  atagen joined the room. | 03:05:47 |
| raitobezarius | hexa (signing key rotation when) could I bother you with a bump to the front with NixOS 25.05 for the new Lix bumps? | 12:25:16 |
 hexa (signing key rotation when) | smol? | 12:25:57 |
| raitobezarius | ye | 12:26:06 |
| hexa (signing key rotation when) | bumped | 12:26:44 |
| raitobezarius | <3 | 12:26:48 |
|  Roman Nefedov joined the room. | 20:18:38 |
| 1 Jul 2025 |
|  djacu joined the room. | 03:26:53 |
| djacu | Hey Infra Team
In case you haven't seen the recent post on discourse, the Marketing Team is preparing this year's community survey. I am reaching out to teams to see if there are any questions they would like to add to the survey to better serve the work you all do. More details in the post linked below.
https://discourse.nixos.org/t/community-feedback-requested-2025-nix-community-survey-planning/66155 | 03:27:21 |
 Jonas Chevalier | One question, but that's more of a personal one; would people be interested in being able to track their personal usage of the cache? We could introduce an optional API key system that would enable that type of accounting. | 08:44:10 |
| emily | to enable better analytics for decisionmaking or for consuming by yourself? | 09:06:42 |
| emily | for the former, I think there'd be more uptake if effort was put into doing it in a privacy-preserving way like the work done by Go and Divvi Up | 09:06:50 |
| emily | (actually, this might make no sense, since the cache already sees every request and who is making it, and totally-anonymized stats are already published) | 09:35:48 |
| emily | (but I can imagine cases where you might want to combine stats about requester with stats about requests. but privacy-preserving analytics ingestion stuff is probably not relevant here given the architecture of the cache. publication is another matter) | 09:36:22 |
 Emma [it/its] | wouldnt it make more sense to do this on the client side? | 09:36:33 |
| sinan changed their profile picture. | 12:07:52 |
| 2 Jul 2025 |
 Robert Hensing (roberth) | for organization-wide aggregation would be a useful feature if implemented centrally. Also the data could be more accurate, taking into account where the cost was made: CDN or backend, possibly including regional differences | 12:40:46 |
| Robert Hensing (roberth) | (not on my personal radar, but could be beneficial for the ecosystem) | 12:41:47 |
| emily | most organizations with that kind of need are probably using their own caching proxy if they're using the central cache at all, surely? | 12:42:03 |
| emily | (so already have a central point to collect data) | 12:42:13 |
| Robert Hensing (roberth) | depends. If we want to motivate businesses to contribute to the infra, we should make the info part as easy as possible | 12:43:59 |
| Robert Hensing (roberth) | otoh some vagueness about the actual use might be good. Ideally they'd pay for value, not cost | 12:44:46 |
| emily | I see, I didn't know the idea was to sell paid services | 12:45:42 |
| Robert Hensing (roberth) | not really. The cache is meant for everyone. As far as I'm concerned, contributions remain optional | 12:46:44 |
| Robert Hensing (roberth) | (and I don't think anyone disagrees with that) | 12:47:04 |
