star_cloud has quit [Remote host closed the connection]
star_cloud has joined #nixos-security
rajivr has quit [Quit: Connection closed for inactivity]
star_cloud has quit [Excess Flood]
star_cloud has joined #nixos-security
prusnak has quit [Read error: Connection reset by peer]
prusnak has joined #nixos-security
blitzclone[m] has quit [Ping timeout: 240 seconds]
Ox4A6F has quit [Ping timeout: 264 seconds]
jdnixx-M1 has quit [Ping timeout: 244 seconds]
danielrf[m] has quit [Ping timeout: 260 seconds]
colemickens has quit [Ping timeout: 260 seconds]
thefloweringash has quit [Ping timeout: 268 seconds]
bbigras has quit [Ping timeout: 268 seconds]
Yakulu[m] has quit [Ping timeout: 246 seconds]
aanderse has quit [Ping timeout: 268 seconds]
JJJollyjim has quit [Ping timeout: 244 seconds]
jdnixx-M1 has joined #nixos-security
blitzclone[m] has joined #nixos-security
Ox4A6F has joined #nixos-security
thefloweringash has joined #nixos-security
danielrf[m] has joined #nixos-security
bbigras has joined #nixos-security
colemickens has joined #nixos-security
Yakulu[m] has joined #nixos-security
aanderse has joined #nixos-security
<maljub01>
Sorry I missed your replies. tilpner, yes using allowInsecurePredicate is a good idea. Thanks for suggesting that. I think I'll do that for my particular case.
<maljub01>
red[evilred]: I'd love to write an RFC! :)
<maljub01>
I'm just wondering if this qualifies as good enough for an RFC vs just a regular issue/PR.. I have to admit I don't really know where the line is there.
<tilpner>
Try to sneak it in with a PR, then write an RFC if people complain the PR is too big c.c
<tilpner>
(Even trivial RFCs can take a very long time to land, and yours sounds like it has some bike-shedding potential, so that doesn't help)
<joepie91>
I wonder if anyone has built a neural network yet that can grade proposals on bikeshedding likelihood