| 21 Oct 2025 |
 piegames | In reply to @522_:catgirl.cloud
is git.lix.systems known to be down atm? Down for me | 14:37:45 |
 Chris | Same here | 14:38:17 |
| Chris set a profile picture. | 14:39:17 |
|  @mrtz_:matrix.org left the room. | 14:55:29 |
 raitobezarius | I am obviously out of home, will take a look asap | 15:01:20 |
| raitobezarius | I suspect this is induced by LLM scraping | 15:01:29 |
| raitobezarius | ~~it's AWS outage~~ | 15:01:43 |
| raitobezarius | no, it's more interesting: billing card expired and the cloud provider suspended all the infra :-) — this is getting fixed | 15:19:51 |
| raitobezarius | The VMs are rebooting atm | 15:26:01 |
 522 it/its ⛯ΘΔ | back up for me | 15:26:28 |
| 522 it/its ⛯ΘΔ | (web is, anyways) | 15:26:45 |
| 522 it/its ⛯ΘΔ | * (web and git is) | 15:26:58 |
| raitobezarius | awesome | 15:28:43 |
|  Niclas Overby Ⓝ joined the room. | 18:19:50 |
 Arian | Is the json serialization of derivations stable? Or only ATerms? | 19:40:04 |
 emily | Nix just changed it | 20:24:57 |
| emily | dunno if Lix considers the interface stable | 20:25:08 |
| emily | AIUI the plan is to only change such output formats in the presence of an explicit versioning system for them | 20:25:20 |
| emily | so I'd assume Lix won't adopt the Nix change | 20:25:35 |
 Jassuko | I hope Nix gets properly stable & supported Nix <-> JSON implementation some day. -_- | 20:34:29 |
| Jassuko | I’d so much prefer writing Nix over JSON any day, but last time I checked (way over a year ago) that was not supported use case. | 20:36:16 |
 mra | oh, is a new serialization for derivations being considered? | 20:36:35 |
| Jassuko | JSON is (very) far from perfect as a serialization format as soon as you have more than one implementation having to handle de-serialization. Especially so, if it’s used in anything where security matters, or encryption is involved. 😅 | 20:39:36 |
| mra | Jassuko: yeah, makes sense. i've been wondering if we should adopt a new serialization for derivations in the Guix daemon when we get around to rewriting it | 20:41:05 |
| Jassuko | If I had to define a security critical JSON serialization now, I’d write the normative spec around SQLite JSON serialization with proper boundary tests included. That one is available to use on any platform and has easy enough interfaces to all possible languages… so if someone wants to implement their thing, they could just use SQLite library to validate IO whenever JSON is involved. :p | 20:45:50 |
| raitobezarius | none are stable to us for now | 21:04:05 |
| raitobezarius | ATerms are obviously stable, we will try hard not to change them | 21:04:16 |
| raitobezarius | but we might not always expose ATerms in the future | 21:04:20 |
| raitobezarius | do not rely on the ATerm, it's an impl detail for now | 21:04:27 |
| 22 Oct 2025 |
 lillecarl | Why not?! I depend on builtins.fromJSON and builtins.toJSON for several usecases | 00:57:03 |
