| 12 Sep 2025 |
 Jassuko | I would actually like mdns if it didn't have all those weird quirks on the implementations. -_- | 14:26:07 |
 toonn | It kinda feels like it was intentionally hamstrung to make it perpetually unpopular. | 14:27:46 |
 magic_rb | It does, going from a strict to lazy bytestring always incurs a copy unless the lazy bytestring is only one chunk i think. Then it may be able to do the conversion in place | 14:33:20 |
| toonn | magic_rb: I was thinking more that it might be read chunk by chunk, converted to the next however many Word8s and the same thing when packing, with fusion eliminating the intermediate list. | 14:34:55 |
| toonn | magic_rb: Also very possible I just didn't notice toStrict though. | 14:35:08 |
| magic_rb | https://hackage-content.haskell.org/package/bytestring-0.12.2.0/docs/src/Data.ByteString.Lazy.Internal.html#local-6989586621679118241 reading the impl here, it has a optimization for "just one chunk" | 14:36:13 |
| magic_rb | In that narrow case it should be O(1) and since you deal with up to 64 bytes, it should always be O(1) | 14:38:30 |
| magic_rb | Yeah the default chunk size is 32k - memory management overhead so your DNS packets fit as such lazy <-> strict is O(1) for you | 14:40:28 |
| toonn | Do you have a name on Codeberg? | 14:50:12 |
| toonn | For some Co-authored-by attribution ; ) | 14:50:51 |
| toonn | magic_rb: ^ | 16:12:49 |
| magic_rb | toonn: magic_rb magic_rb@redalder.org | 16:35:28 |
| magic_rb | * toonn: magic_rb <magic_rb@redalder.org> | 16:35:34 |
| toonn | Thanks : ) | 16:50:13 |
| 13 Sep 2025 |
|  Etherbloom [they/sie] {you&} 🐲🦊👿 changed their display name from Etherbloom [they/sie] {you&} 🐲🦊👿 to Etherbloom @MRMCD25 [they/sie] {you&} 🐲🦊👿. | 13:45:13 |
| Etherbloom [they/sie] {you&} 🐲🦊👿 changed their display name from Etherbloom @MRMCD25 [they/sie] {you&} 🐲🦊👿 to Etherbloom @MRMCD25 [📞3724] [they/sie] {you&} 🐲🦊👿. | 13:46:32 |
|  Donald joined the room. | 15:12:26 |
|  validitymaiden joined the room. | 17:19:26 |
| validitymaiden set a profile picture. | 17:31:46 |
| validitymaiden changed their profile picture. | 17:32:26 |
| 14 Sep 2025 |
|  zxfsee changed their profile picture. | 15:42:38 |
| Donald set a profile picture. | 20:44:21 |
| 17 Sep 2025 |
| Etherbloom [they/sie] {you&} 🐲🦊👿 changed their display name from Etherbloom @MRMCD25 [📞3724] [they/sie] {you&} 🐲🦊👿 to Etherbloom [they/sie] {you&} 🐲🦊👿. | 09:02:17 |
 clerie | I was poking around the ifstate module a little because I wondered how password files are solved for ifstate in NixOS found this
sed -i $'s|\'!include |!include \'|' $out
ifstate is using the yaml tag !include to specify if a string is used as a password or as a file containig a password. The NixOS module ist using toJSON and replacing every string startig with !include.
This feels very sketchy to me. Is there a better way to solve this in NixOS or is this state of the art?
https://github.com/NixOS/nixpkgs/blob/c23193b943c6c689d70ee98ce3128239ed9e32d1/nixos/modules/services/networking/ifstate.nix#L29 | 10:42:29 |
 hexa (clat on linux when) | sed -i -e "s/'\!\([a-z_]\+\) \(.*\)'/\!\1 \2/;s/^\!\!/\!/;" $out
| 10:45:56 |
| hexa (clat on linux when) | from elsewhere in nixpkgs | 10:45:59 |
| hexa (clat on linux when) | https://github.com/NixOS/nix/issues/4910 | 10:46:33 |
 emily | YAML would make a mess out of the language semantics :( | 13:21:44 |
| emily | TOML already has | 13:21:46 |
 Marcel | Idk, I am open for better suggestions | 16:58:10 |
