| 30 Nov 2023 |
 edgar.vincent | Just tried and it's still trying to build it here on nixos-unstable (and failing with a OOM error despite my 16GB of RAM ^^) | 09:06:30 |
 uep | hm, yeah, just tried a nix shell nixpkgs#fractal and it's pulling in 600 crates in anticipation of building | 09:59:07 |
| uep | when I ran it the other day, I was pulling from the nixos-unstable-small branch | 09:59:38 |
| uep | I guess something bumped in the meantime and it's no longer cached? | 10:00:46 |
 vcunat | Well, when you use the master branch, you may not have all binaries 🤷 | 10:19:09 |
| uep | this is (this time) from -unstable | 10:19:48 |
| uep | which is now past where -small was the other day | 10:20:13 |
| uep | so something has invalidated the cached binary it found then | 10:21:13 |
| vcunat | Redacted or Malformed Event | 10:22:04 |
| uep | it is for me:
❯ nix registry list | grep nixpkgs
system flake:nixpkgs path:/nix/store/mdl8yp9lzzzjla69qm42sk96p15vym7d-source?lastModified=1701068326&narHash=sha256-vmMceA%2Bq6hG1yrjb%2BMP8T0YFDQIrW3bl45e7z24IEts%3D&rev=8cfef6986adfb599ba379ae53c9f5631ecd2fd9c
global flake:nixpkgs github:NixOS/nixpkgs/nixpkgs-unstable
pinned to the rev used to build the system
| 10:23:33 |
| vcunat | Yes, my bad. | 10:23:48 |
| uep | heh | 10:23:49 |
| vcunat | There was a transient failure in one dependency and that caused fractal not getting built that time: https://hydra.nixos.org/job/nixpkgs/trunk/fractal.x86_64-linux | 10:24:16 |
| uep | anyway, it's still building.. not using all cores for some reason, but close to done | 10:24:32 |
| uep | built. happy to share the closure if anyone need | 10:52:04 |
| uep | * built. happy to share the closure if anyone needs
| 10:52:08 |
 @js:ukvly.org | uepthe build takes 40min-1h because they configured single threaded builds for releases
| 13:09:49 |
| @js:ukvly.org | but I really like fractal 5. feels more snappy than element. | 13:12:04 |
| @js:ukvly.org | it misses some features, but it's surprisingly solid for a non-element matrix client | 13:12:33 |
| edgar.vincent | It is good, and the recent changes in the UI have made it snappier. I still find it to be a bit slow, and some of the rooms I've joined always show as containing unread messages, regardless of the fact that they in fact have been read. | 18:00:15 |
 @adam:robins.wtf | yeah they definitely fixed some of the major performance issues. i switched back to element primarily because i was missing a keyboard shortcut to jump to unread rooms | 19:45:15 |
| @adam:robins.wtf | it was also difficult to discern whether a room was unread or read, but that may just be my theme/font | 19:45:47 |
| edgar.vincent | In reply to @adam:robins.wtf
it was also difficult to discern whether a room was unread or read, but that may just be my theme/font I think this issue does not depend on the current theme. | 19:53:32 |
| @adam:robins.wtf | the room title is bolded, but it just doesn't stand out enough | 19:54:04 |
| edgar.vincent | (Nix is still trying to build Fractal 5 on the unstable channel here) | 19:55:01 |
| @adam:robins.wtf | i don't really even understand how fractal 5 is sorting the rooms, because i would have random unreads not at the top of the list | 19:55:34 |
| edgar.vincent | Yeah, same thing here. | 19:55:55 |
| 1 Dec 2023 |
|  @lotte:chir.rs changed their profile picture. | 09:42:03 |
|  @berserkin:matrix.org left the room. | 14:10:11 |
| edgar.vincent | Redacted or Malformed Event | 20:14:26 |
