| 31 Oct 2025 |
 Charles | 
Download image.png | 17:59:39 |
 Dee | I was able to send in it, but now I can't bring it up again | 17:59:46 |
| Charles | if you enable devtools in element-desktop you can view the space's room timeline to see the messages | 17:59:53 |
 raitobezarius | I'm on nheko right now | 18:00:01 |
| Charles | should really just disable talking perms in the space | 18:00:09 |
| Dee | I don't think that's mentions, I think that's the default notification level notifying on everything | 18:00:14 |
| Dee | and there's never been anything to notify on there before | 18:00:24 |
| Charles | 
Download image.png | 18:01:35 |
| Charles | fwiw these are the current messages there | 18:01:40 |
| raitobezarius | :') | 18:02:12 |
 QuadRadical (Ping) | i didnt even know you can type in spaces | 18:02:21 |
| QuadRadical (Ping) | you cant normally, right? | 18:02:25 |
| Charles | spaces are implemented on top of rooms | 18:02:35 |
| Charles | so there's no reason you can't | 18:02:40 |
| QuadRadical (Ping) | so far as i can see theres not even an option in cinny | 18:02:38 |
| QuadRadical (Ping) | yes, but normally theres no message permission? | 18:02:46 |
| QuadRadical (Ping) | like, by default, right? | 18:02:53 |
| Charles | i think it depends on a handful of factors | 18:03:06 |
| Dee | I got a notification in Android Schildichat, and I tapped on it, which led me to the room view of the room | 18:03:24 |
|  @lilahexe:matrix.lilahexe.top left the room. | 18:16:41 |
|  Alexandra Østermark joined the room. | 18:17:09 |
 tc424 (Steve D) | Hmm, I've had a permanent unread count of ~2 in Fluffychat for the Lix space for ages, but I assumed that was a FC bug | 18:24:39 |
| QuadRadical (Ping) | * so far as i can see theres not even an option in cinny EDIT: Nevermind found it | 18:26:53 |
 rosssmyth | Issues I had:
- Does not set NIX_PATH so you need to manually configure it so that nix-command stuff works|
- I really don't like the fact that it has a "global" default nixpkgs instance, then you can override per-machine. It makes the hive attrset really anoyying to make modular
- Cross-compilation is not first-class even though it definitely could be
- When applying locally the output is just worse than nom which I don't like
| 18:30:35 |
| rosssmyth | * Issues I had:
- Does not set NIX_PATH so you need to manually configure it so that nix-command stuff works|
- I really don't like the fact that it has a "global" default nixpkgs instance, then you can override per-machine. It makes the hive attrset really annoying to make modular
- Cross-compilation is not first-class even though it definitely could be
- When applying locally the output is just worse than nom which I don't like
| 18:30:55 |
 @dawnofmidnight:catgirl.cloud | you can at least work around 4 a little bit by having colmena set up the eval and then using nom directly, though you then have to colmena apply afterwards (which evals again). we just have a default.nix with
let
pins = import ./npins;
eval = import "${pins.colmena}/src/nix/hive/eval.nix" { rawHive = import ./hive.nix; };
in
eval.toplevel
| 18:46:13 |
| @dawnofmidnight:catgirl.cloud | * you can at least work around 4 a little bit by having colmena set up the eval and then using nom directly, though you then have to colmena apply afterwards (which evals again). we just have a default.nix with (below, and then use nom build -f . [system name]
let
pins = import ./npins;
eval = import "${pins.colmena}/src/nix/hive/eval.nix" { rawHive = import ./hive.nix; };
in
eval.toplevel
| 18:46:33 |
| @dawnofmidnight:catgirl.cloud | * you can at least work around 4 a little bit by having colmena set up the eval and then using nom directly, though you then have to colmena apply afterwards (which evals again). we just have a default.nix with (below), and then use nom build -f . [system name]
let
pins = import ./npins;
eval = import "${pins.colmena}/src/nix/hive/eval.nix" { rawHive = import ./hive.nix; };
in
eval.toplevel
| 18:46:54 |
| @dawnofmidnight:catgirl.cloud | * you can at least work around 4 a little bit by having colmena set up the eval and then using nom directly, though you then have to colmena apply afterwards (which evals again). we just have a default.nix with (below, for a non-flake setup), and then use nom build -f . [system name]
let
pins = import ./npins;
eval = import "${pins.colmena}/src/nix/hive/eval.nix" { rawHive = import ./hive.nix; };
in
eval.toplevel
| 18:47:46 |
|  @dominic_:matrix.org left the room. | 19:14:09 |
