| 30 Jul 2025 |
 hexa | https://nvd.nist.gov/vuln/detail/CVE-2025-31243 | 22:03:13 |
| hexa |
An app may be able to gain root privileges.
| 22:03:17 |
| hexa | cool. | 22:03:18 |
 emily | usually you have to run Nix to get functionality like that | 22:10:19 |
| emily | are we getting Sherlocked? | 22:10:30 |
 Cobalt | Besides the point, but if apple were to create a reproducible build system similar to nix (maybe in swift?) It would probably only work on Darwin. I don't think they would go the extra mild for various Linux architectures. | 22:31:51 |
| Cobalt | It would probably spark a lot of excitement for build systems though | 22:32:16 |
| emily | (they have in fact already published several cross-platform open source build systems) | 23:28:17 |
| 31 Jul 2025 |
 Mic92 | Do what degree were you able to test that? | 05:32:53 |
 Matthew Kenigsberg | I wasn't sure exactly how to test so haven't tested it. Anything I can do to test it? | 15:23:42 |
| 1 Aug 2025 |
|  @paperdigits:matrix.org joined the room. | 15:41:40 |
| 2 Aug 2025 |
 K900 | Started a new unstable-small to pick up the kernel bumps | 04:47:06 |
|  sinan changed their profile picture. | 06:58:39 |
| sinan | 06:58:46 |
| 3 Aug 2025 |
| sinan changed their profile picture. | 15:07:47 |
| 4 Aug 2025 |
 djacu | Hey all
Was already talking to Jeremy Fleischman (jfly) about this and I believe @avocadoom pinged hexa (signing key rotation when) about this as well. Bringing the conversation here now. The marketing team would like infra's help with ideas and possibly roll out for hosting the new branding assets.
I have this PR open for creating a branding page and that shows the guide and logos. But as @avocadoom reminded me, we don't want the website to be the single source of truth for branding assets going forward.
Two options discussed so far are hosting the assets on GH Pages or S3 + Fastly.
I had concerns about every new release inflating the repo over time. Jeremy Fleischman (jfly) pointed out we could force push every new release into a single commit which seems fine. Another concerns I have is if these would cause any issues with rate limiting or misuse of GH pages. Maybe this concern is unfounded?
No concerns I could think of regarding S3 + Fastly. Would require more work from Infra though
Totally open to other ideas and options!
| 01:28:21 |
| djacu | * Hey all
Was already talking to Jeremy Fleischman (jfly) about this and I believe @avocadoom pinged hexa (signing key rotation when) about this as well. Bringing the conversation here now. The marketing team would like infra's help with ideas and possibly roll out for hosting the new branding assets.
I have this PR open for creating a branding page and that shows the guide and logos.But as @avocadoom reminded me, we don't want the website to be the single source of truth for branding assets going forward.
Two options discussed so far are hosting the assets on GH Pages or S3 + Fastly.
I had concerns about every new release inflating the repo over time. Jeremy Fleischman (jfly) pointed out we could force push every new release into a single commit which seems fine. Another concerns I have is if these would cause any issues with rate limiting or misuse of GH pages. Maybe this concern is unfounded?
No concerns I could think of regarding S3 + Fastly. Would require more work from Infra though
Totally open to other ideas and options!
| 01:35:27 |
| djacu | * Hey all
Was already talking to Jeremy Fleischman (jfly) about this and I believe @avocadoom pinged hexa (signing key rotation when) about this as well. Bringing the conversation here now. The marketing team would like infra's help with ideas and possibly roll out for hosting the new branding assets.
I have this PR open for creating a branding page and that shows the guide and logos.
https://github.com/NixOS/nixos-homepage/pull/1819
But as @avocadoom reminded me, we don't want the website to be the single source of truth for branding assets going forward.
Two options discussed so far are hosting the assets on GH Pages or S3 + Fastly.
I had concerns about every new release inflating the repo over time. Jeremy Fleischman (jfly) pointed out we could force push every new release into a single commit which seems fine. Another concerns I have is if these would cause any issues with rate limiting or misuse of GH pages. Maybe this concern is unfounded?
No concerns I could think of regarding S3 + Fastly. Would require more work from Infra though
Totally open to other ideas and options!
| 01:35:42 |
| djacu | Completely separate request. I am trying to create a new survey in LimeSurvey for the 2025 Community Survey, and when I try to create a new survey, it fails with "Access denied". | 01:45:12 |
| hexa | says you are an admin here | 01:47:34 |
| hexa | the limesurvey is usually managed by the folks in #survey:nixos.org. maybe they can help? | 01:48:38 |
 Jeremy Fleischman (jfly) | Re: hosting the branding assets. I'd vote for github pages, and if we run into issues, we can change things.
Do you know what the goal is re: url/domain name? I guess I'm trying to understand what "source of truth" means. I'd think in any universe, the git repo is still the source of truth.
Is it perhaps about who gates updating the website? Like the website team doesn't want to be a blocker for future updates to the branding?
| 01:50:52 |
